Hello...today I wanted to root my ZTE Speed N9130. However, due to the fact it is a rather obscure device, I've been having problems finding anything on how to root it. I've tried all the common methods and they all failed. I've also tried kingroot, which also failed...what's the deal on why nothing is working...it's irritating me to no ends and I've gotten no good answers.
The difficulty high in this one is!
44trent5 said:
Hello...today I wanted to root my ZTE Speed N9130. However, due to the fact it is a rather obscure device, I've been having problems finding anything on how to root it. I've tried all the common methods and they all failed. I've also tried kingroot, which also failed...what's the deal on why nothing is working...it's irritating me to no ends and I've gotten no good answers.
Click to expand...
Click to collapse
Man I'm right there with you, I've had this Speed for a while and I'm finally getting around the resources to be able to try and root it. I haven't had a whole lot of luck with it entirely myself, I first tried to get it to root sometime last year I believe it was and tried all those same services myself to no avail. HOWEVER! This morning I did manage to get KingRoot to punch through and finally root myself, it failed several times at first and then I remembered seeing somewhere that someone said taking out the SD card if you have one in it would for some reason make a difference- so I tried that and between the app on android and the desktop download I managed to get it to it through in the first try or two.
Now the drawback so far with this is I haven't managed to get the root access to stay open, it's only been temp so far and therefore shuts off after cycling power for a reboot or anything, but at the same time this is the first time I've ever tried to personally root a device so I feel pretty good about getting that far right now within about an hours time. Hopefully this may offer some pointing in the right direction that will aid you. I'm sure someone has gotten farther than me though by a far distance considering this is my current lack of experience. Lol
I think you should consider rooting. It has pros and cos. Your phone can become a brick if it failed. Your software is also damaged. Be careful!
I had been using Kingoroot, and it kept failing. I think I used iRoot, and it seemed to work with a permanent root. I doesn't seem to support Xposed framework though...
Related
So recently bought the straight Talk ZTE Valet, and have been searching for a root for this device if anyone knows of any or is interested on trying to develop a root exploit. I'm willing to dump any and all files, as well as try any and all rooting methods. If there is already a root im sorry for making a duplicate post.
I'm also looking for a root process that might work on the ZTE Valet now available on Tracfone. Help please!
Any luck?
I am also looking for a root solution for this phone. Either of you had any luck?
I have tried many methods that have worked on other devices, but no luck yet.
I'm also interested, mainly to move more apps, data. The phone does move some apps to a micro SD but not all.
gberpa said:
I'm also interested, mainly to move more apps, data. The phone does move some apps to a micro SD but not all.
Click to expand...
Click to collapse
have you guys tried superone click? i have to ask is it gingerbread or what os android version is it?
It is JB 4.1. I haven't tried Superone but will check it out. My root experience has been limited with a Hisense tablet and methods specific to that.
Sent from my AT100 using Tapatalk
ZTE Valet - tried a few methods so far with no luck
mderuelle said:
have you guys tried superone click? i have to ask is it gingerbread or what os android version is it?
Click to expand...
Click to collapse
The ZTE Valet Z665 has JB (4.1.1).
So far, I've tried Bin4ry (v32), framaroot (1.6.1), and poot (current version). None worked. In looking at superoneclick, I might not be understanding things very well but it appears to require a CWM image which does not (yet) exist - is that right?
What other methods appear to be worth a try and what have people tried on the ZTE Valet? Anyone aware of a source for the stock ROM? Are there other phones sufficiently similar where the CWM recovery would function on the Valet?
BTW, I just picked up my ZTE Valet at Fred Meyer where it was on sale for $49.99 (Tracfone, no contract). It's a great buy for that price. The sale is over but if interested, keep an eye out for the ads.
Like others, thanks for any ideas.
Sent from my SPH-L720 using XDA Premium 4 mobile app
Tried superoneclick and z4root
mderuelle said:
Sent from my SPH-L720 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
OK - tried superoneclick and z4root. These in addition to Bin4ry, framaroot, and poot didn't work. I'm a novice at this and am nervous trying some of these options that seem to lack proper pedigree and openness. Also, since I don't have a backup, a more invasive technique also worries me. I'm hoping one of you brave souls will try something out and hopefully give some of us some specifics on what you did to get this phone rooted. It would also be helpful to know what you did actually try (details) that didn't work. Thanks.
Update: Also just tried the adb method which didn't work for me http://forum.xda-developers.com/showthread.php?t=1224774[/adb root guide].
Although I took care in trying each of the methods mentioned above and repeated them, I could have screwed up. So ... maybe someone else can report their results just to be sure. I would not re-try z4root but the others don't seem too harmful and my phone still works.http://forum.xda-developers.com/showthread.php?t=1224774
karmmisht said:
OK - tried superoneclick and z4root. These in addition to Bin4ry, framaroot, and poot didn't work. I'm a novice at this and am nervous trying some of these options that seem to lack proper pedigree and openness. Also, since I don't have a backup, a more invasive technique also worries me. I'm hoping one of you brave souls will try something out and hopefully give some of us some specifics on what you did to get this phone rooted. It would also be helpful to know what you did actually try (details) that didn't work. Thanks.
Update: Also just tried the adb method which didn't work for me http://forum.xda-developers.com/showthread.php?t=1224774[/adb root guide].
Although I took care in trying each of the methods mentioned above and repeated them, I could have screwed up. So ... maybe someone else can report their results just to be sure. I would not re-try z4root but the others don't seem too harmful and my phone still works.http://forum.xda-developers.com/showthread.php?t=1224774
Click to expand...
Click to collapse
Tried all of the above also z4root really seemed to take a toll on the device a question I was wondering is if we had an almost identical phone would the cwm for that work?
gberpa said:
I'm also interested, mainly to move more apps, data. The phone does move some apps to a micro SD but not all.
Click to expand...
Click to collapse
My ZTE turned out to be defective. Screen become unresponsive even after going to recovery, trying to wipe caches/reformatting and even finally attemting to restore to factory state. K-mart wouldn't accept it for an exchange since I bought it out of state. TracFone says they will'll replace it after I ship it to them on their dime. Up until this I liked the phone, except for sound clarity outgoing seemed poorer than mt LG290c from one test from a noisy place.
New phone received and checks out OK enuf to keep. WiFi OK at home but only fair with weak source. Doing this on my Hisense Sero 7 Pro which does better with less than strongest wifi. Screen slightly less crisp at lower brightness than original when it worked. Got 9x more min, text, MB than expected when transferred from old phone so definitely keeping.
Sent from my Nexus 7 using Tapatalk
I'm very sad to admit that I updated from 4.2.2 to 4.3 on my Verizon Galaxy S4 and lost root. I made the terrible assumption that someone would root 4.3 quickly after release, but didn't want to wait to see the updates. So far, the only two solutions are:
1. Root on 4.2.2 and upgrade through this method
2. Use VROOT to root stock 4.3
This thread and this article both make me VERY wary of using VROOT, but this seems to be the only option once you do the OTA update.
Has there been any additional investigation into VROOT? Is it safe to use again, or is it a lost cause?
As of right now, that is the only option that I am aware of. I am no dev, but I have been tinkering with my phones for quite some time. I personally have not encountered a single ill effect from using vroot. There is a script which completely wipes it off your phone and installs the supersu app. Ultimately, it is up to you...I did it and I'd do it again. No ill effects what so ever and it's been a few weeks-nothing wonky to report.
bjoostema said:
As of right now, that is the only option that I am aware of. I am no dev, but I have been tinkering with my phones for quite some time. I personally have not encountered a single ill effect from using vroot. There is a script which completely wipes it off your phone and installs the supersu app. Ultimately, it is up to you...I did it and I'd do it again. No ill effects what so ever and it's been a few weeks-nothing wonky to report.
Click to expand...
Click to collapse
I'm really on the fence... My fear is that I don't want to compromise my Google Account, since my whole life goes through that thing. Did you find that hidden app was installed after using VROOT?
Why is there yet another thread asking the SAME question about rooting MJ7??????
Read the other threads...
http://forum.xda-developers.com/showthread.php?p=47566483
http://forum.xda-developers.com/showthread.php?t=2535416
thethotbot said:
I'm really on the fence... My fear is that I don't want to compromise my Google Account, since my whole life goes through that thing. Did you find that hidden app was installed after using VROOT?
Click to expand...
Click to collapse
Not a single thing was different on my phone. There were even some folks who ran an md5 checksum on all apps and reported that nothing was altered what so ever on any system level. I understand your concern, it took me a couple weeks before finally doing it. I really weighed it out and decided that root was important to me. Also, a good dev on the forums did it with no ill effects. I have faith in him and thus far, nothing has happened. I don't want to push you into it though. I don't even worry about it anymore since the script wipes all traces of the chinese superuser app off the phone.
bjoostema said:
Not a single thing was different on my phone. There were even some folks who ran an md5 checksum on all apps and reported that nothing was altered what so ever on any system level. I understand your concern, it took me a couple weeks before finally doing it. I really weighed it out and decided that root was important to me. Also, a good dev on the forums did it with no ill effects. I have faith in him and thus far, nothing has happened. I don't want to push you into it though. I don't even worry about it anymore since the script wipes all traces of the chinese superuser app off the phone.
Click to expand...
Click to collapse
I did the same thing. My life runs through my google account and I was very weary. I dont see anything strange occurring and ran malware scans on both the PC and phone and didnt find any trojans. I am assuming it is safe with the removal script posted on Rootjunky.com
I'm going for it.
Alright.... I just did it. I used Sandboxie on my computer to temporarily install the Chinese program (just to be safe), and everything on my phone now looks like it's fine. I'll keep a close eye on my accounts, and have enabled Two Step Authorization on my Google Account. I'll still be super bummed out if it ends up VROOT is collecting personal data, but I just couldn't bring myself to wait for root any longer.
I'm curious to know if the developers of vroot have removed the data mining features from the more recent versions?
I want to know if there is way to root the new MAX+, I had the old one n9520. Now I want to root the new one but can't find a root for it anywhere.If someone could help that would awesome. Iv'e tried Towelroot Kingroot and Framaroot none have worked if anyone can find me a working root method it would be helpful.
Yoboywesley said:
I want to know if there is way to root the new MAX+, I had the old one n9520. Now I want to root the new one but can't find a root for it anywhere.If someone could help that would awesome. Iv'e tried Towelroot Kingroot and Framaroot none have worked if anyone can find me a working root method it would be helpful.
Click to expand...
Click to collapse
Did you have any luck achieving root on this device I've got one and have been working on it all day yesterday
No i havent had any luck with it
I have tried kingroot and kingroot.no go.this is with the PC and apk versions. I got up to 70% while using the latest kingroot 4.81.Hang in there and keep posting. So of the devs might pitch in and help us. Please!!!!!
Sent from my N9521 using Tapatalk
Hey guys can anyone help please???
Sent from my N9521 using Tapatalk
Help
Has anyone found a way to root this phone yet
I rooted mine with the latest Kingo Root pc version.Sadly the root doesn't survive reboot.If some nice developers would help we could succeed!!!!
Sent from my N9521 using Tapatalk
DIWE337 said:
Has anyone found a way to root this phone yet
Click to expand...
Click to collapse
I used kingo root pc version to get root.You may have to install the kingo root superuser apk first then use the pc version to get root.Let me know the results.
Sent from my N9521 using Tapatalk
Is anyone still trying???
Sent from my N9521 using Tapatalk
I believe this is a good phone, and think it would be a great phone if we could achieve root. I am not a Dev but I will be glad to help someone smarter than me to push this device in the right direction. Let's not let this one fall through the cracks.
Kingroot 4.95 causes brick.You have to go to recovery and do factory reset!!!
Thanks this is the only root I could get to work zte max N9521
It is a PC root from kingoroot if u can take out the super user app after u get it rooted u could try to install a different su binary file but I don't know how to do that yet so I'm stuck with a half rooted device....
Can anyone help???
Sent from my LGLS770 using Tapatalk
I agree and I'm really surprised this phone hasn't gotten much more attention considering how nice it is. For what is a prepaid phone for many (via Boost), I can lay it down on the table next to my nice Oneplus One and honestly it holds its own for day to day use. Plus, it even has the rare microSD!
But, these Boost and ZTE people apparently have created the only damned unrootable device I personally have ever experienced. I mean, even my darn Nook readers are rooted. And I say unrootable because unlike others (even IOS) that may not be "this version" so we "wait".......apparenlty there has yet to be ANY version of this phone's build that can be rooted.
I'm so confused as to why since the "Kingroot" can get an apparent temporary root, but then for some reason the partitions are "read only" and some other similar phones take a command (makes sense, I'm still following) to first change to R/W, then use the temp root and install perm root like I have on every other device using either TWRP, stock recovery (whoops this phone they removed it), or let SuperSU try it. But, from the many hours I"ve spent trying to force the temp root to get R/W or even get a recovery running on it, it seems to me that the hangup is there is some special sauce in the way that the filesystem is locked and that is the key.
So, for any gurus reading, is it just that this phone isn't "popular" enough, or that it's just not in use in the scene? It sure seems there is always some part of the xda scene that touches every one of these devices even a tad, heck even my ancient crappy 1st gen Nook tablet still get help if I ask LOL.
I'm wondering how many would donate a few bucks if a dev would dedicate some cycles to finding a way to free this really nice ZTE Max+ N9521...I know I would!
WyldWolf said:
I agree and I'm really surprised this phone hasn't gotten much more attention considering how nice it is. For what is a prepaid phone for many (via Boost), I can lay it down on the table next to my nice Oneplus One and honestly it holds its own for day to day use. Plus, it even has the rare microSD!
But, these Boost and ZTE people apparently have created the only damned unrootable device I personally have ever experienced. I mean, even my darn Nook readers are rooted. And I say unrootable because unlike others (even IOS) that may not be "this version" so we "wait".......apparenlty there has yet to be ANY version of this phone's build that can be rooted.
I'm so confused as to why since the "Kingroot" can get an apparent temporary root, but then for some reason the partitions are "read only" and some other similar phones take a command (makes sense, I'm still following) to first change to R/W, then use the temp root and install perm root like I have on every other device using either TWRP, stock recovery (whoops this phone they removed it), or let SuperSU try it. But, from the many hours I"ve spent trying to force the temp root to get R/W or even get a recovery running on it, it seems to me that the hangup is there is some special sauce in the way that the filesystem is locked and that is the key.
So, for any gurus reading, is it just that this phone isn't "popular" enough, or that it's just not in use in the scene? It sure seems there is always some part of the xda scene that touches every one of these devices even a tad, heck even my ancient crappy 1st gen Nook tablet still get help if I ask LOL.
I'm wondering how many would donate a few bucks if a dev would dedicate some cycles to finding a way to free this really nice ZTE Max+ N9521...I know I would!
Click to expand...
Click to collapse
I am willing to donate!Why so little dev interest in this phone????
Sent from my N9521 using Tapatalk
Bump. How do we perhaps set up a bounty for this phone? I see multiple people have already said they would donate so how do we set up a bounty for root?
Has anyone come up with any way to kill the read-only on the zmax to be able to hold root?
Greetings, all of you who know better than to do what I did . . .
I could use some advice from someone who's been around the block with the HDX 8.9 Apollo, 3rd Gen. Kindle. For my part, I'm usually adept enough to avoid problems that should be foreseen, but I was outclassed by whatever was going on here, and I unwittingly dug myself a hole. In a matter of days, I went from having a mostly-stock, rooted FireOS that played nice with Google, to a device with weird quirks, to soft-but-hardening brick. And yes, I've been all over here, reading all kinds of threads. What I usually find is that my situation applies partly, but not fully, to the problems that have already been addressed here.
Back when things were good, the status was:
Rooted with Kingroot, replaced with SU, proper Safestrap installed, XPosed Framework running with the HDX module, seamless integration with Google, disabled OTA according to the instructions provided in the thread on that topic, etc. I had one strange incident where various apps were saying I wasn't rooted, so I repeated the Kingroot/SU process and all was good for several months.
Then suddenly, after the device had sat on my dresser unused for a few days, I picked it up and it started doing some quirky stuff again. Sorry, I can't be more specific than that, because I don't remember--except for one thing: instead of getting a message plainly indicating that I wasn't rooted, anything that sought root access seemed to either hang or crash. I thought it was that same mysterious problem again, so I attempted to do another round of Kingroot/SU, but I kept getting hangs and crashes. At that point, I was still able to reboot into the OS with no difficulty. Until one day, that hung too. Then I was in the same boat as many people here, i.e., "Kindle stuck at boot screen."
I tried all kinds of stuff that's been explained around here. I still had Safestrap for a few boots, but not enough room for a backup. After following some instructions to attempt a fix using the ADB/Fastboot environments, though, Safestrap disappeared. In retrospect, I believe that if I had gone straight to getting the system mounted R/W, I might have saved myself some grief. But maybe not. By the time I got to attempting that, all I got was "permission denied" anyway. Finally, I tried some of the brick recovery/re-root solutions offered here, and I managed to get one of them to wipe my system out, only to be told that it had no permission to write anything in its place.
So here I am: ADB/Fastboot access still intact, but no system, which means no solutions that involve shell commands. (I can still push files, so I'm wondering if I could push a shell in there or something, but I'm definitely out of my depth at this point. My bootloader is locked and I appear to have no root access. (The command "adb root" actually disconnects the device from my computer, so I have to start-server after that, and I don't know if it comes back with root or not . . . but I think it's safe to say, not. I can't seem to do anything that requires special permissions.)
So . . . now that I've exposed myself as a complete turd, is there anyone out there who might have some advice that would lead me in the direction of reviving my Kindle?
I'll keep an eye out as often as I can--got some pre-holiday craziness with my work schedule, so I'll address any responses ASAP.
Thanks!
KT71
KilgoreTrout71 said:
Greetings, all of you who know better than to do what I did . . .
I could use some advice from someone who's been around the block with the HDX 8.9 Apollo, 3rd Gen. Kindle. For my part, I'm usually adept enough to avoid problems that should be foreseen, but I was outclassed by whatever was going on here, and I unwittingly dug myself a hole. In a matter of days, I went from having a mostly-stock, rooted FireOS that played nice with Google, to a device with weird quirks, to soft-but-hardening brick. And yes, I've been all over here, reading all kinds of threads. What I usually find is that my situation applies partly, but not fully, to the problems that have already been addressed here.
Back when things were good, the status was:
Rooted with Kingroot, replaced with SU, proper Safestrap installed, XPosed Framework running with the HDX module, seamless integration with Google, disabled OTA according to the instructions provided in the thread on that topic, etc. I had one strange incident where various apps were saying I wasn't rooted, so I repeated the Kingroot/SU process and all was good for several months.
Then suddenly, after the device had sat on my dresser unused for a few days, I picked it up and it started doing some quirky stuff again. Sorry, I can't be more specific than that, because I don't remember--except for one thing: instead of getting a message plainly indicating that I wasn't rooted, anything that sought root access seemed to either hang or crash. I thought it was that same mysterious problem again, so I attempted to do another round of Kingroot/SU, but I kept getting hangs and crashes. At that point, I was still able to reboot into the OS with no difficulty. Until one day, that hung too. Then I was in the same boat as many people here, i.e., "Kindle stuck at boot screen."
I tried all kinds of stuff that's been explained around here. I still had Safestrap for a few boots, but not enough room for a backup. After following some instructions to attempt a fix using the ADB/Fastboot environments, though, Safestrap disappeared. In retrospect, I believe that if I had gone straight to getting the system mounted R/W, I might have saved myself some grief. But maybe not. By the time I got to attempting that, all I got was "permission denied" anyway. Finally, I tried some of the brick recovery/re-root solutions offered here, and I managed to get one of them to wipe my system out, only to be told that it had no permission to write anything in its place.
So here I am: ADB/Fastboot access still intact, but no system, which means no solutions that involve shell commands. (I can still push files, so I'm wondering if I could push a shell in there or something, but I'm definitely out of my depth at this point. My bootloader is locked and I appear to have no root access. (The command "adb root" actually disconnects the device from my computer, so I have to start-server after that, and I don't know if it comes back with root or not . . . but I think it's safe to say, not. I can't seem to do anything that requires special permissions.)
So . . . now that I've exposed myself as a complete turd, is there anyone out there who might have some advice that would lead me in the direction of reviving my Kindle?
I'll keep an eye out as often as I can--got some pre-holiday craziness with my work schedule, so I'll address any responses ASAP.
Thanks!
KT71
Click to expand...
Click to collapse
Unfortunately, locked bootloader, no root access, missing/invalid permissions, non-operational rom and no recovery leaves few (effectively no) options short of board replacement on this device. Once could find a glimmer of hope using fastboot/factory cables on early generation Amazon devices; they have proven largely ineffective on 3rd gen and above. Wish there was a better answer.
Davey126 said:
Unfortunately, locked bootloader, no root access, missing/invalid permissions, non-operational rom and no recovery leaves few (effectively no) options short of board replacement on this device. Once could find a glimmer of hope using fastboot/factory cables on early generation Amazon devices; they have proven largely ineffective on 3rd gen and above. Wish there was a better answer.
Click to expand...
Click to collapse
Well, truth is better than endless, repeated frustration. Thanks for the answer. But don't get me wrong . . . I'd love a second opinion that proves you wrong somehow. I just won't get my hopes too high.
KT71
KilgoreTrout71 said:
Well, truth is better than endless, repeated frustration. Thanks for the answer. But don't get me wrong . . . I'd love a second opinion that proves you wrong somehow. I just won't get my hopes too high.
Click to expand...
Click to collapse
No worries mate; I welcome other opinions and would love to be proven dead wrong!! No faux pride here...if your device can be resurrected through shared knowledge (and perhaps a bit of luck) everyone wins.
I have spent literal hours trying to figure this out. I eventually found out that the most optimal way to do this is with Magisk, but the method that uses an APK requires rooting, since you need to be able to get the boot.img.
So...I need to root my device to be able to root my device? I've never been this frustrated while trying to do something like this before as with my Huawei phone I could do it easily with KingRoot (and it actually worked). On top of all of this, I have no idea what "flashing" is, let alone how to do it, and literally everything I've seen today that seems to properly work requires "flashing" at least one thing.
So has literally no one got an answer for this?