OK, so here is the situation. My ZTE n9520 is/was rooted, however, it also had an update available for a while. I chose not to update it though due to the fact that it was not worth it at the time. I ended up changing devices and gave the ZTE to my other half to use since it was better than theirs. Without thinking, or asking, they did the OTA update and it seriously screwed up the device since it was rooted and thus the partitions were changed. Now it only boots to the system recovery screen due to the update and root conflicting. I hope everyone's with me so far. If I had a computer, I could connect it and go through the lovely process of fixing it that way. As luck would have it, I do not have a computer and it is no longer under warranty. Does anyone know of any way possible that I can fix this without a computer? I actually dropped the phone I am using and it broke, like into a thousand pieces and I have need of the ZTE. Please help me out, your my only hope my good people.
I see a lot of views, but nothing posted. Please help me out.
Any chance someone has an idea how to fix this?
I actually tried that already. A few times. Since it was rooted when the OTA update was performed, the partitions were changed and that is what caused all of this to happen. I appreciate your advice though.
Would anyone else possibly have an idea on how to fix this?
I take it I am SOL with this since no one else will reply?
Would it be possible to download the stock ROM for this onto an SD card and put it into the ZTE n9520 and go through the recovery that way?
So still no possible answer?
Would anyone have a possible answer to this?
I may get yelled at for this, but would getting a copy of the stock recovery or possible stock ROM for the ZTE possibly work? I am trying anything I can and am coming up short all around. I was hoping I would have gotten more information by this point. I know this thread is oldish, but I really don't have the money for a new one and am still without a computer at the moment.
Would anyone happen to know if there is a way to fix the partitions on the device without a computer?
Small question... Would it be possible to flash the partition without a computer? Or TWRP or CWM? I saw somewhere about an Android 4.1 partition flash and was wondering if there was a way to flash/fix the partition without a PC?
I just recently ran into this problem and was able to fix it.
I know this thread is old but better late than never. Perhaps you still need to fix your ZTE Max after all this time.
Here are two links that will fix your problem.
The first is to "unbrick" it. This is really just to install a custom recovery so that you can flash a working rom. It also allows you to flash some stuff that is supposed to fix the partitioning. (Though i dont think that is actually your problem. I think you are just in a bootloop, but for me flashing a normal stock rom through recovery failed.)
Unbrick:
HTML:
http://androidforums.com/threads/tool-alpha-zte-max-unbrick-tool-need-testers.836089/
Roms/Partition Fixes:
HTML:
http://androidforums.com/threads/zte-max-stock-b06-4-4-2-deodexed-custom-and-unmodified.896210/
The unbrick tool requires you to burn a file to a CD and boot your computer with it. I just tried it on my bricked ZTE Max and it works perfectly.
After that just download the rom/fixes you need, put em on an SD card, and flash em through the newly installed custom recovery.
Double post sorry
Related
I have just ported CWM for my tablet (Denver-TAC-70051) that is nowhere on the internet, although I hesitate to flash it, I have a question, If I where to screw up the recovery would android still boot up? and another thing, how could I back up my recovery into a .img, my block structure is quite weird, I will attach a screenshot with it, if anyone could help me I would appreciate i, thanks I
Hi, any progress on this? How did it turn out?
I'm thinking about making a ROM for the TAC70051 as well.. No need if you already got one working. Care to share?
PS: I've got the stock-rom from Denver, if you need that I can give you the link!
Ok I really did it this time. Here is what i stupidly did. my phone was on the 35b update so I used the tot method to take it back to 10b. I rooted and then used the ota updates to upgrade to 12b, and I believe to more times (of course after telling supersu to stay active thru the updates) until I got to the update that would take me over into lollipop. I downloaded the update, but then needed to charge my phone i noticed, so I told it to postphone the update. After I had a somewhat decent charge I told my g3 to update and it immediately went to twrp recovery. Thinking this odd I tried to reboot and it started to bootloop inside twrp. I tried getting it to do a recovery of a save that i had previously had downloaded to my ext sd before I lost root taking the 35b update and it went all the way thru and said success. But as soon as it rebooted into what should have been the system, It instead started bootlooping at the lg logo and hasnt stopped since. I not have got it to go to recovery but it is stock and twrp is now gone but every option results in simply restarting the bootloop. I plugged into my computer to try both tot and kdz only to have them both fail because now my computer no longer recognizes my device. During the stage that I was in recovery trying to use different predownloaded roms is when I realized that my imei has also been erased, which is why I assume my computer cant recognize it anymore. I know I probably have a list of mistakes that could have been avoided but I tried to do this myself and I admit i simply need the vast knowledge of the xda. Please someone guide me in the right direction to fix my phone. I don't have alot of money to spend to replace it and just really need to fix this one please.
ronnieshane1 said:
Ok I really did it this time. Here is what i stupidly did. my phone was on the 35b update so I used the tot method to take it back to 10b. I rooted and then used the ota updates to upgrade to 12b, and I believe to more times (of course after telling supersu to stay active thru the updates) until I got to the update that would take me over into lollipop. I downloaded the update, but then needed to charge my phone i noticed, so I told it to postphone the update. After I had a somewhat decent charge I told my g3 to update and it immediately went to twrp recovery. Thinking this odd I tried to reboot and it started to bootloop inside twrp. I tried getting it to do a recovery of a save that i had previously had downloaded to my ext sd before I lost root taking the 35b update and it went all the way thru and said success. But as soon as it rebooted into what should have been the system, It instead started bootlooping at the lg logo and hasnt stopped since. I not have got it to go to recovery but it is stock and twrp is now gone but every option results in simply restarting the bootloop. I plugged into my computer to try both tot and kdz only to have them both fail because now my computer no longer recognizes my device. During the stage that I was in recovery trying to use different predownloaded roms is when I realized that my imei has also been erased, which is why I assume my computer cant recognize it anymore. I know I probably have a list of mistakes that could have been avoided but I tried to do this myself and I admit i simply need the vast knowledge of the xda. Please someone guide me in the right direction to fix my phone. I don't have alot of money to spend to replace it and just really need to fix this one please.
Click to expand...
Click to collapse
im fairly knowledgeable with the g3, but im not sure i can help you
the consequences of the minor mistake you made (you cant take an ota with twrp on) are unusually severe.
we have a zip to flash that would have fixed it, but it needs to be flashed in twrp, and i dont believe i have ever seen twrp get removed while making this error.
im thinking the only fix is flashing stock. i would try different usb ports, re-install the drivers, and even try another pc, to get it recognized so you can flash it.
if there is some other fix im forgetting maybe someone else will suggest it, but in a bootloop with no twrp to flush the update, i believe your in a bad spot if you cant figure out how to get it to flash.
sorry
that is how my luck goes, thanks for looking into my problem.
bweN diorD said:
im fairly knowledgeable with the g3, but im not sure i can help you
the consequences of the minor mistake you made (you cant take an ota with twrp on) are unusually severe.
we have a zip to flash that would have fixed it, but it needs to be flashed in twrp, and i dont believe i have ever seen twrp get removed while making this error.
im thinking the only fix is flashing stock. i would try different usb ports, re-install the drivers, and even try another pc, to get it recognized so you can flash it.
if there is some other fix im forgetting maybe someone else will suggest it, but in a bootloop with no twrp to flush the update, i believe your in a bad spot if you cant figure out how to get it to flash.
sorry
Click to expand...
Click to collapse
got my computer to see it but now i cant flash back because I have no imei. Any fix I can do from download mode?
ronnieshane1 said:
got my computer to see it but now i cant flash back because I have no imei. Any fix I can do from download mode?
Click to expand...
Click to collapse
I don't know if trying LG Flash Tool 2014 with a 10B KDZ would work any better than the TOT method without an IMEI.
ronnieshane1 said:
got my computer to see it but now i cant flash back because I have no imei. Any fix I can do from download mode?
Click to expand...
Click to collapse
there is a thread here in help somewhere on how to fix your imei. you would have to look into that, i really dont know how its done or whats possible.
Hey all, I've tried to use various methods found here and elsewhere to root this tablet, with no luck.
I just got it from BB, and updated to the very latest (with Stagefright) ... now trying to use the Intel Flash Lite Tool with droidboot? FAIL Try using the Fastboot Tethered Recovery Launcher? FAIL
Did I screw myself by updating to the latest OS beforehand? Is there any way to get root now? Thanks all!
I had the exact same problem yesterday, and after a bunch of reading it's my understanding that there is no way at the moment to root an uprooted 7840 with the stage fright fix. Someone please correct me if I'm wrong.
Hopefully someone will be able to figure out how to root this soon. It's a nice little tablet.
Having (successfully) gone through the anxious moments of removing root, downgrading, then restoring 5.1 to install the Stagefright fix, I would recommend that you seriously reconsider whether or not you absolutely need root. It's highly likely that any future patches, or even a possible Android v6 (?) upgrade, will not install if your device is rooted - so you'll have to wait until some kind soul finds a possible way to unroot.
as we have the possibility to unlock the bootloader since 5.1, there might be a good chance that a permanent CWM recovery (and therefore installing/uninstalling root with a few clicks) is possible. I've never compiled CWM before, but as there are plently of good tutorials and even a CWM builder tool,i'll give it a try the next days. Let's see how far we get.
The old tethered boot method won't work because you'd have to reverse to 5.01 droidboot and system.img for rooting, which would most likely mess up your system.
So is the consensus here that we can not root on the latest 5.1? Running the Intel phone flasher all it does it attempt to detect the device and fail. I only really need to root so I can adjust left/right audio balance since my hearing is a bit messed up so anything anyone can give me here would be appreciated.
ziemas said:
I had the exact same problem yesterday, and after a bunch of reading it's my understanding that there is no way at the moment to root an uprooted 7840 with the stage fright fix. Someone please correct me if I'm wrong.
Hopefully someone will be able to figure out how to root this soon. It's a nice little tablet.
Click to expand...
Click to collapse
There is a means of doing it, but you do not truly have all the pieces of the sg update. If you're adventuresome, it's fine. I'm looking at a couple of issues already. They're not show stoppers, but they wouldn't have happened.
As systemless root grows, that may be a future possibility as well.
Okay, well i got this cheap phone for boost mobile, but the stock firmware takes 4gigs of already small amount of 8 gigs. I want a custom rom and I CANNNTTT find one at all! I saw some threads on how to root it, so I'm sure I wont have a problem there, but seriously there is nothing out there rom wise. Can anyone help me?
anyone know anything??
should i just give up?
rooting LG Volt 2
mobearpig said:
Okay, well i got this cheap phone for boost mobile, but the stock firmware takes 4gigs of already small amount of 8 gigs. I want a custom rom and I CANNNTTT find one at all! I saw some threads on how to root it, so I'm sure I wont have a problem there, but seriously there is nothing out there rom wise. Can anyone help me?
Click to expand...
Click to collapse
I'd be real careful about following the directions out there all the way to the end. a train phone technician informed me back simply using Philz recovery image which a number of those directions suggest that you do after you download kingroot Flashify could break your phone. I've got the same phone and the same problem there is nobody working on volt2 anything that I have found yet. I tried running super SU me which temporarily rooted my phone but it didn't last long after I removed it. you can't install TWRP recovery or ClockworkMod without having a recovery image to flash so I am busy working on creating a recovery image for the LG Volt 2 that's the missing piece of the puzzle. Otherwise I am pretty happy with kingroot and purify which allow you to shut down everything you don't want running and uninstall quite a bit. together you at least get root access for Battery Doctor and Ron toolbox Pro which will allow you a whole lot more control over what runs and what doesn't. I know my battery lasts a whole lot longer since I touched that combination of tools onto my phone and removed all of that bloatware... Be careful purify identifies symptoms of bloatware that you may not want to remove. please say something if you find a Volt 2 recovery image so that we can install TWRP or ClockworkMod recovery what you really want before you experiment with a new mod. Good luck
Possible LG LS751 Volt 2 Stock Recovery.img
I came across a possible stock recovery for the LG LS751 Volt 2. I am in no way able to verify if the file is legit or correct and complete. If this is still a file that you need, let me know and I'll get it to you. I also have a copy of one of the Updates that was pushed to device also.
I got this 13 inch tablet for displaying music PDF files.
It's got KitKat 4.4, and there's apparently no intention to update this from the manufacturer.
I'd like to run igigbook, but that app requires 5.0+. So I figure I can root this, then do the cm12 ...?
I've looked on compatible devices lists and can't find this device.
Anybody got a link or maybe just some advice?
Thx
jazaddict said:
I got this 13 inch tablet for displaying music PDF files.
It's got KitKat 4.4, and there's apparently no intention to update this from the manufacturer.
I'd like to run igigbook, but that app requires 5.0+. So I figure I can root this, then do the cm12 ...?
I've looked on compatible devices lists and can't find this device.
Anybody got a link or maybe just some advice?
Thx
Click to expand...
Click to collapse
I own one of these.
I found Kingo Root successfully roots it.
Unfortunately, no CM has been built for it.... yet. I plan to fix this.
Fair warning, though: do NOT remove anything child-mode-related yet, unless you have a backup of the system partition. It's basically an AOSP ROM, but they've tweakedwith the SYSTEMUI enough that straight-up removing it causes crach loops.
It's got an RK3188 chip, for the curious. Opened it to verify.
AmEv said:
I own one of these.
I found Kingo Root successfully roots it.
Unfortunately, no CM has been built for it.... yet. I plan to fix this.
Fair warning, though: do NOT remove anything child-mode-related yet, unless you have a backup of the system partition. It's basically an AOSP ROM, but they've tweakedwith the SYSTEMUI enough that straight-up removing it causes crach loops.
It's got an RK3188 chip, for the curious. Opened it to verify.
Click to expand...
Click to collapse
Great.
Ive learned the hard way! lol
Bit too late for me now, but i had a similar tab from smart telecom and i cant find any firmware for it, i rooted with kingroot and after removing all the child mode and disney crap, im having the same thing.
Ive started a thread, but im hoping i can find a patched firmware without all the bloatware and a newer android build if possible.
HI - Just came across this thread, pity I hadn't seen it earlier - I had/have rooted with King Root, which worked fine. Then set about deleting all the child-mode-related apps. Now I'm stuck with receiving "Unfortunately, the process com.android.systemui has stopped" nothing seems to fix it. Do you know where I might find the original ROM that I can restore, can't find anything on the manfactures website..
Any help, really appreciated.
Thanks
Wayne
waynez2016 said:
HI - Just came across this thread, pity I hadn't seen it earlier - I had/have rooted with King Root, which worked fine. Then set about deleting all the child-mode-related apps. Now I'm stuck with receiving "Unfortunately, the process com.android.systemui has stopped" nothing seems to fix it. Do you know where I might find the original ROM that I can restore, can't find anything on the manfactures website..
Any help, really appreciated.
Thanks
Wayne
Click to expand...
Click to collapse
Hi Wayne,
I contacted the supplier who was going to contact the manufacturer, still have not found anything.
Someone else started a thread some time back and did the same thing as us.
I think someone was going to create a ROM for me, i will direct them to this thread.
Thanks for the update.
I had some success last night in resolving my issues with "com.android.systemui" - I managed to get into play store and reinstalled "Net Nanny for Android" as soon as the install had completed the error message went away and hasn't returned. The other "Kids" apps that I had deleted have not reinstalled, appears Net Nanny must have removed/broken something when I deleted it.
Would be still good to get a copy of the original rom for next time, better still to get an upgrade from 4.4.4 to something a little newer at least.
Anyway hoe that help to get you going again.
Wayne
I am ordering one of these now. Let me know if there's anything I can do to try to help in terms of getting a copy of the ROM. (I haven't done android development before, but I am a software engineer so I am willing to give anything a shot)
claylong said:
I am ordering one of these now. Let me know if there's anything I can do to try to help in terms of getting a copy of the ROM. (I haven't done android development before, but I am a software engineer so I am willing to give anything a shot)
Click to expand...
Click to collapse
Let me know how you get on, as I am still after a ROM image if i can find one.
Going to start researching all the possible ways to get a ROM image (in addition to just asking the manufacturer). I will first do a search, and then maybe post in the forums somewhere, but I am starting here:
http://www.theandroidhow.com/2014/06/how-to-dump-backup-any-android-rom.html
Did some research, and actually found that the androidhow article I linked in my last post was the most relevant. I followed the romdump script process and believe I have the rom image files.
The question becomes, are the image files most usable in their current form, or as flashable images?
Has there been any developments in this, or anything close to a ROM or even an update?
Roach419 said:
Has there been any developments in this, or anything close to a ROM or even an update?
Click to expand...
Click to collapse
Not that im aware of, i just did what someone else suggested here and reinstalled netnanny off the app store.
At least its working again, but not terrific.
Oh, well I didn't have that problem. The guy I bought this streamachine off of already had it rooted and everything, i was just wondering if anything had been developed...4.4.4 is quite a bit outdated, and limited.
Clay,
Can you upload that ROM image that you made? I bought another ST13 and while I can get it into recovery mode, it still won't boot even after a factory data reset. My plan is to try recovering from the sdcard before I assume that what I have is a collection of spare parts.
My two others aren't rooted, and since we need them tonight, I don't dare mess with them right now.
Thanks,
Paul
can I get a copy?
I rooted my ST13 and now I'm having bluetooth problems. I'd like to restore back to the stock ROM. Can I have a copy of yours? Does it work?
THANKS!
claylong said:
Did some research, and actually found that the androidhow article I linked in my last post was the most relevant. I followed the romdump script process and believe I have the rom image files.
The question becomes, are the image files most usable in their current form, or as flashable images?
Click to expand...
Click to collapse
I am also interested in this thread, anyone know about the bootloader?
???
So still no DISK IMAGE or ROM? I successfully rooted St1316 but can't connect to wifi. I left natnanny alone, but it now doesn't connect to ANY wifi networks. Tries then switches to either "saved" or "disabled". I can push some apps to the device via bluetooth file transfer app but don't know what's missing. Could this be a permission issue? I'm lost and stressed. Tried factory wipe. No luck. Open to suggestions. Help guys. This thing kinda sucked before I lost wifi. Now it's just a glorified digital photo frame that plays sound WAY too softly.