-
Notifications
You must be signed in to change notification settings - Fork 18
Not rooting still... #10
Comments
Yup, same thing im getting. |
Did you try the latest version?
|
Yeah im getting this now. ./roothandler prepare_kernel_cred=c00b14c8 Succeeded in getroot! |
Thanks for the info! I will look at his shell script (Tomorrow) to see if I
|
@elliot-labs Welcome! Any luck yet? Am about to try the new installsu.sh. |
So now im getting, ./roothandler prepare_kernel_cred=c00b14c8 Succeeded in getroot! |
Hmmm.... On Sun, Jun 1, 2014 at 3:38 PM, benjimt notifications@github.com wrote:
Elliot DISCLAIMER: If you have received it by mistake please let me know by reply and then If you as intended recipient have received this e-mail incorrectly, please |
I tried rooting by entering the commands from installsu.sh. It worked. I was able to use ES 3 and delete some bloatware. :D Ill do alittle research later and see what I can figure out for the installsu.sh file. |
OMG MG OMG OMG OMG!!!!! I (myself) have never goten the system to work. Can On Sun, Jun 1, 2014 at 4:29 PM, benjimt notifications@github.com wrote:
Elliot DISCLAIMER: If you have received it by mistake please let me know by reply and then If you as intended recipient have received this e-mail incorrectly, please |
Yes after reboot the su is gone.........still need to get something working with the installsu.sh though. |
Funny thing ~ all the suddon there is no su binary.....and I don't think I rebooted....maybe I did....... |
@elliot-labs what do you know about the verify.zip? If it is what I think it is it should be able to be edited with temp root to allow the su binary to be kept across reboots. Just an idea. |
I was asking if the bloatware was still removed after reboot... That might
|
oh, sorry. Yes, it is still gone. Only problem is now I cant get temp root any more. Its is saying that "/system/xbin" is a "read only file system." :( |
Hmmm... Have you tried running the steps from the beginning?
|
Yup like 20 times lol. |
Are there any files left over?
|
Could you tell me the list of commands so I can write them down? Thanks! |
I personally think that verify.zip if for signing the OS (or even updates if they release any). My personal thoughts are that the Firmware has an anti su bin remover in it. Android does not have anti su abilities out of the box. if you notice the files in verify.zip are certs. (like ssl) to say who made what. This proves that there are no symlinked partitions or "ghosted" partitions on the device because the bloatware is still removed after you reboot. |
All the rooting files are there if that's what you mean ~ roothandler, su, installsu.sh etc. I might try repushing them all. |
yes that is what I mean. Can you try that? thanks! On Mon, Jun 2, 2014 at 10:58 AM, benjimt notifications@github.com wrote:
Elliot DISCLAIMER: If you have received it by mistake please let me know by reply and then If you as intended recipient have received this e-mail incorrectly, please |
The commands that worked for me are as follows: Run through the roothandler procedure untell you get to the installsu.sh error. Then type busybox telnet 127.0.0.1 23 Then type the following hitting enter between them: busybox stty -echo Now maybe you will have root! I'll post proof later that I actually did have true root through superuser once lol. OK, I getcha about the verify.zip. that could be a problem if custom Roms ever becomes an option. |
Yes I will try that when I get to a computer! |
OK! thanks! I will try to do this to my phone. I have some really annoying On Mon, Jun 2, 2014 at 11:19 AM, benjimt notifications@github.com wrote:
Elliot DISCLAIMER: If you have received it by mistake please let me know by reply and then If you as intended recipient have received this e-mail incorrectly, please |
This is through ADB right? On Mon, Jun 2, 2014 at 11:21 AM, Elliot Huffman thelich2@gmail.com wrote:
Elliot DISCLAIMER: If you have received it by mistake please let me know by reply and then If you as intended recipient have received this e-mail incorrectly, please |
Correct. |
I have updated the Wiki for better understanding of the commands On Mon, Jun 2, 2014 at 11:21 AM, Elliot Huffman thelich2@gmail.com wrote:
Elliot DISCLAIMER: If you have received it by mistake please let me know by reply and then If you as intended recipient have received this e-mail incorrectly, please |
k On Mon, Jun 2, 2014 at 11:22 AM, benjimt notifications@github.com wrote:
Elliot DISCLAIMER: If you have received it by mistake please let me know by reply and then If you as intended recipient have received this e-mail incorrectly, please |
OK cool. Keep me posted! |
I just ran your commands and now have SU in the xbin and symlinked in the On Mon, Jun 2, 2014 at 11:23 AM, benjimt notifications@github.com wrote:
Elliot DISCLAIMER: If you have received it by mistake please let me know by reply and then If you as intended recipient have received this e-mail incorrectly, please |
I am using tracfone On Fri, Jul 11, 2014 at 5:27 AM, defraged notifications@github.com wrote:
Elliot DISCLAIMER: If you have received it by mistake please let me know by reply and then If you as intended recipient have received this e-mail incorrectly, please |
@defraged then It must be a net10... @elliot-labs nice! Did you all see mainefungi's latest post? Didnt thnk of that its a good try http://androidforums.com/valet-all-things-root/799676-ill-help-find-root-method-if-8.html#post6638759 |
I haven't been on the android forums lately (in more than a month) On Fri, Jul 11, 2014 at 10:35 AM, benjimt notifications@github.com wrote:
Elliot DISCLAIMER: If you have received it by mistake please let me know by reply and then If you as intended recipient have received this e-mail incorrectly, please |
Can you say "Good One!" for me? I don't have an account :-P On Fri, Jul 11, 2014 at 11:29 AM, Elliot Huffman thelich2@gmail.com wrote:
Elliot DISCLAIMER: If you have received it by mistake please let me know by reply and then If you as intended recipient have received this e-mail incorrectly, please |
@benjimt If GNU gets involved, ZTE is going to be screwed over into complying with the license. |
An update was released for the ZTE Valet: http://www.zteusa.com/zte-valet.html It's a fix for the heartbleed bug |
Wow an actual update!!!! now we can get our hands dirty!!!!!! On Mon, Jul 21, 2014 at 9:39 PM, jjfriede notifications@github.com wrote:
Elliot DISCLAIMER: If you have received it by mistake please let me know by reply and then If you as intended recipient have received this e-mail incorrectly, please |
Credit goes to Woolytwo for discovering this: http://androidforums.com/valet-all-things-root/799676-ill-help-find-root-method-if-9.html#post6653310 I am kind of surprised that ZTE actually came through with something like that :P |
Tell him thanks for me! I personally think that they were monitoring our
|
That could be. I wonder If they patched any of our current bugs. I updated my sister's phone but I didn't update mine just in case. And mainefungi posted an update about the GPL: http://androidforums.com/valet-all-things-root/799676-ill-help-find-root-method-if-8.html#post6647578. It sounds like we might get some help |
Now that is GOOD news!!! Thanks for the info! Tell mainefungi I said thanks
|
Great!! Just what we wanted.... :D anybody downloaded it and tried messing On Mon, Jul 21, 2014 at 8:06 PM, Elliot Huffman notifications@github.com
|
Good news indeed! cant wait to see how it turns out On Tue, Jul 22, 2014 at 11:46 AM, Ben Gibson benjimt99@gmail.com wrote:
|
It looks like the exploit we're using still works after the update. I tested it on my sister's phone. |
I'm no longer having the problem of having the su binary fail to copy. It has worked every time so far and I can even remount /system as ro and rw multiple times without anything screwing up or getting any "read-only filesystem" errors. It seems pretty safe to update as far as I know. |
That is good to hear! I just got my phone back and am planning on updating
|
since my sister's phone worked so nicely I just updated my phone but I'm still having problems with /system not mounting on my phone. I wonder why my phone is acting different than my sister's if they're exactly the same |
the source code was just released! http://androidforums.com/valet-all-things-root/799676-ill-help-find-root-method-if-9.html#post6661950 |
I do not see the post. Can you provide me with a link to the source code?
|
Sure thing! It's the first one on this page: http://opensource.ztedevices.com/ (the Z665C) |
Anything new?? I have not been working on it....and I might sell my phone.... |
It seems though that someone might try modifying the kernel again..... but fixing the issues that mainefungi thought might be wrong with what he did.... if it gets bricked, just call up tracfone. They will be eager to send you a new one lol. |
And maybe the kernel source will help. |
Anyone still here?? |
Yes
|
I'm still here. I'm a little more focused on whats going on at androidforums though. I generated a PEM file for stayboogy so I'm just waiting for his response. |
Just to let you all know, I sold my Valet on ebay a month or so ago (it was just too crappy for me), so if this ever gets worked on again, I will most likely not be able to help. If you do work on it again, then good luck! Goodbye! |
thx for the info On Wed, Oct 22, 2014 at 9:30 AM, benjimt notifications@github.com wrote:
Elliot DISCLAIMER: If you have received it by mistake please let me know by reply and then If you as intended recipient have received this e-mail incorrectly, please |
I know this thread is very old, but where can I get the actual root files? I found su, but I can't find roothandler. Is there anything else I need? Thanks! |
Here is a link to roothandler (it is included in the github lib/armabi I would check on the forum's progress as this project gives you only Thanks for your interest! On Thu, Apr 9, 2015 at 9:56 PM, Phil Sweeney notifications@github.com
Everybody talks about the weather but they do nothing about it - Mark Twain Elliot Huffman DISCLAIMER: If you have received it by mistake please let me know by reply and then If you as intended recipient have received this e-mail incorrectly, please |
Here is my error code and output:
The text was updated successfully, but these errors were encountered: