I rooted mah Prime (TY Viperboy and contributing dev's!) and finally installed Font Changer. After I selected the font I wanted, obviously I re-booted....and re-booted..and etc. My TFP won't get past the ASUS boot animation, the circle just keeps spinning and spinning. I tried wiping user data and still nothing. Does anyone have a similar experience or advice? I didn't change the density or anything else, just the font.
I also tried the reset button a few times just in case and still the same thing. Android Commander doesn't see it when I connect either, Windows tried to install drivers for it(which i've obviously already installed) and kept getting an error.
98 views...am I the only one who has used Font Changer on the TFP? Do any of you vets on here have an idea how I might be able to boot the device or at least completely revert it to all factory settings/apps? I apologize for having a one sided conversation, but I really would like to use mah Prime again. Thanks!
Sent from my SPH-M900 using XDA App
I use Font Changer and haven't had a problem yet.
Hmm...Well I opted to re-boot from Font Changer after I changed fonts. Did you do the same?
pappasquirrel said:
Hmm...Well I opted to re-boot from Font Changer after I changed fonts. Did you do the same?
Click to expand...
Click to collapse
Yes. I don't know what to tell you.
Anyone know if there is a file I could put on my sd card that the TFP would boot from, like how PG86IMG works w fastboot?
not sure, but i would suggest you to get the newest update from their site, then pop it on a micro sd, (or sd if you have the dock) and try holding power and vol up .... or maybe power vol down, dont remember..
now when you download the zip from asus site, make sure to unextract and copy the zip after you unextract. It's a zip in a zip.
Then try with the zip as its labeled, maybe it'll work or rename to update.zip.... that seems to be the norm on other devices.
good luck, i hope it works so we can have another solution for those that this happens to. Can't wait for unlocker tool, so we can get a recovery on this and if that ever happens we can just do a restore. good luck!
Good idea, thanks! I will give that a go and report back soon. I know I had this problem once or twice on my EVO3D and Moment, I would have to do something similar and try again. I'm hoping for good news to report
keep us updated, I am sort of in the same boat. Mine wont boot up after last firnware update and I have been searching to see if I can make it read the update file from SD
btw, try volume up with power, then hit volume down.... maybe it'll just do a recovery with the image it already has
damn i dont know if its volume up or down.... anyone ever tried this? i dont have my tab with me...to test
Its vol dwn+power for recovery. it will ask to press vol up within 5 sec to enter RCK, I've done that and "andy" just lays there on his back w an exclamation mark coming out of his chest.
If you wait, you get a screen with 10 seconds to select one of two options, User Data Wipe and linex cold boot. I've tried both with no avail. One more thing I found out is since my Prime just stays at the loading screen, everytime I hold power or reset button it would just reboot and hang there again. Aside from letting the battery die the only option I've found to shut down is hold vol up+power till it vibrates, keep em dwn for 2 more seconds and it will shut down.
Sent from my SPH-M900 using XDA App
Font Changer, now TFP won't boot.
My Asus Prime is in the same situation as yours. A rooted it and install Font Changer, after reboot my TFP won't get past the ASUS boot animation. I tryed all the things you do, but Android doesen´t start.
I install APX driver in Windows 7, and when i connect the USB cable, the device is reconized in Windows Device Manager, but a can not acess the tablet.
I don´t know a method the acess the Tablet from microSD, do you know ?
May be BOOTLOADER UNLOCK release from ASUS solve it.
Good luck for us.
Still nada. Windows will reconize that its plugged in, but I get a code 43 or code 10 and can't access the TFP in anyway (that I know of). I asked the same question over on Transformerforums.com and member leeshor has been really helpful. Most of the idea's I was given I had already tried or I could not get to work for my specific problem, but I'm sure that the info will be helpful for a lot of you guys. Here's a link to my thread, check leeshor's sig for some helpful tips. http://www.transformerforums.com/forum/transformer-prime-help/15428-font-changer-now-wont-boot.html
I'm still workin' on it and I'll post if I am able to make any progress, good luck!
Data wipe will definitely not work in this situation as it does nothing to the /System which is where the font's are stored. My best guess is that the font was changed but the permission was not correctly written, had this problem in the early days of my Desire HD.
The only solution that will work, is if you can get into an ADB shell and either put the original fonts back or change the permissions to the correct permissions.
Doktaphex said:
Data wipe will definitely not work in this situation as it does nothing to the /System which is where the font's are stored. My best guess is that the font was changed but the permission was not correctly written, had this problem in the early days of my Desire HD.
The only solution that will work, is if you can get into an ADB shell and either put the original fonts back or change the permissions to the correct permissions.
Click to expand...
Click to collapse
That's what I figured, I just can't get windows to recognize it. When I connect via USB and the device is off, windows sees it as an unknown device(obviously) and that the drivers are fine. After I power it up, windows will either recognize it as an MTP device and when I try to access the tab or re-install the drivers I get a code 10. Or it will still show up as an unknown device with an "!" giving me a code 43. Is there any other way I can gain root access?
It's been awhile (or seems so) and I still haven't had any success. Has anyone else made progress getting back to a usable device??
Ok, so before I send my prime in...do any of you smarty pants know (guess is fine) if this lil problem some of us are having will have a solution when ASUS unlocks the bootloader? Unless there is some kind of boot.zip err something that will load up from stock recovery, I don't think it will change anything. Thoughts? Advice? Bueller?? Thank you in advance
Sent from my SPH-M900 using XDA App
Unlock-bootloader.apk....I guess that answers my question to whether i'd be able to fix permissions from recovery :/ What am I not seeing? There has to be a way to get these Primes w no adb access and a stuck boot screen to fire up...?
Sent from my SPH-M900 using XDA App
Have you tried the blob file from SDcard trick. I believe you rename the update to EP201_SDUPDATE.zip and it should be able to run from the RCK. It has to be on a micro sdcard though otherwise it doesn't work apparently.
As outlined here:
http://forum.xda-developers.com/showpost.php?p=22743057&postcount=119
Related
I installed CM7 Alpha Final (SD card version) and was working on getting the interface back to how I had it on the previous version. I used CWM to install "transparent status bar icons.zip" from this thread...
http://forum.xda-developers.com/showthread.php?t=1471066
Upon installation I went to reboot and now I'm stuck on the CyanogenMod7 boot screen and looping endlessly.
If anyone has any idea how I can fix this, I'd really appreciate some help.
Thanks!
Retcon:
I just remembered that I did NOT have this installed on the previous version on CM7. On CM7 i had a standard theme dock, so I think I installed something that just wasn't compatible with CM7 at all. What do I do now?
Thanks.
Most likely that transparent icons xip was not built for cm7 and rather was built for stock firmware. They are not compatible. Reinstall cm7.
What method can I use to reinstall? Since I'm in a bootloop I can't get to CWM. Or is there some kind of "safe mode" I can boot into?
Sent from my T-Mobile G2 using xda premium
Turn the unit on, when you get to the n screen, hold the power button until it turns off. Repeat 8 times and you will be forced into CWM.
If you have adb installed on your pc, plug it in, turn it on and check devices. If you are listed, do an adb shell reboot recovery and that will put you into recovery instantly.
I tried the 8-boot method two different ways...
1. Pressed the power button and released. When I saw the N screen, I pressed again and held until the unit powered down.
2. Pressed and HELD the button through it powering on and not releasing until it shut back down again.
Does it matter which of the above ways I do it? I wasn't able to get it to work. Does it have to be exactly 8 times? I don't think I stopped short but I might've done it more than 8...
Regarding the ADB method, I went ahead and installed the SDK but I'm not seeing my devices in ADB DEVICES. Since this is a new computer, I think I just don't have the right drivers installed. I went to Indirect's root thread to get those drivers but his dropbox link is disabled due to high traffic. Is there somewhere else I could get the appropriate driver? And once I have the correct driver and can see my device in ADB DEVICES (I'm assuming I'll be able to see it even though I'm bootlooping the whole time?), what is the code/line to get it into recovery?
Thanks for your help thus far. I really appreciate someone taking the time the time to help me out.
Oh, and a correction to my original post - I used the internal root method, not SD.
I found a working link for the drivers.
http://www.mediafire.com/?w6y5ld1jeuh65i1
I installed them and I can access my tablet now. I can see my device and its responding to commands.
So all I need now is the command to get into CWM. I tried "adb reboot [bootloader:recovery]" which I saw in the cmd window, but it just gave me a standard reboot.
Thanks!
EDIT: I tried "adb reboot recovery" and that did it. I'm back in business! Thanks for the help, Know-Fear. Although in my n00bishness, step-by-step handholding would've been nice, your replies gave me enough for me to at least know what general direction to look in. I still couldn't get the 8-boot method to work, but maybe that's just a dexterity issue. The adb method worked perfectly once I stumbled my way to the command line.
Make sure when you reinstall you do a partition wipe.
Glad you got it working thus far. Hopefully no more problems will arise after the new install.
I have messed up my tablet, my tablet is rooted i went and replaced couple of the system apps by using root explorer and that completely made my system go crazy so i then did a system reset and now i keep getting unfortunately, setup wizard had stopped and i cant go anywhere from there. my boot loader is not unlocked. is there any way to reinstall the stock ROM like from adb or something. please any help is appreciated. I have also tried to reset the rom by holding down power and vol down and wipe data from there, and still the same thing. when i plug it in the computer i am still able to see the transformer so i can transfer files to and from the transformer i just cant get it passed the welcome screen.
thank you
spencerj2001 said:
I have messed up my tablet, my tablet is rooted i went and replaced couple of the system apps by using root explorer and that completely made my system go crazy so i then did a system reset and now i keep getting unfortunately, setup wizard had stopped and i cant go anywhere from there. my boot loader is not unlocked. is there any way to reinstall the stock ROM like from adb or something. please any help is appreciated. I have also tried to reset the rom by holding down power and vol down and wipe data from there, and still the same thing. when i plug it in the computer i am still able to see the transformer so i can transfer files to and from the transformer i just cant get it passed the welcome screen.
thank you
Click to expand...
Click to collapse
I'm not positive, but let's try some things.
Follow the link in my signature "HOW TO INSTALL ANY UPGRADE TO YOUR PRIME" and see if you can't appropriately rename an update file from ASUS so that the system will install it from recovery, it should do a kind of emergency upgrade. Do not use the "orBLOB" method as it's outdated and I don't think it would help you.
If that does not work, come on back and the community will certainly pipe up eventually or I may even think of something else.
thanks for the response, i went to your how to install any upgrade to your prime link, the file you want to rename is it the blob file or the actual zip file.
buxtahuda said:
I'm not positive, but let's try some things.
Follow the link in my signature "HOW TO INSTALL ANY UPGRADE TO YOUR PRIME" and see if you can't appropriately rename an update file from ASUS so that the system will install it from recovery, it should do a kind of emergency upgrade. Do not use the "orBLOB" method as it's outdated and I don't think it would help you.
If that does not work, come on back and the community will certainly pipe up eventually or I may even think of something else.
Click to expand...
Click to collapse
spencerj2001 said:
thanks for the response, i went to your how to install any upgrade to your prime link, the file you want to rename is it the blob file or the actual zip file.
Click to expand...
Click to collapse
The actual zip file I think. Just rename it to "EP201_SDUPDATE.zip" and put it directly on a microSD card (not in any folders or anything, that is in the root of the card). Put that card into the Prime, and proceed to turn off the Prime. Turn the Prime on and when it vibrates push the Volume- button until you see some text on the screen, then press the Volume+ button within 5 seconds or so. Some more text will show up, and after a bit your Prime will either show the update Android and go about its business, or it'll show you the sad dead Android with the exclamation mark.
If you get the exclamation mark, make sure the microSD card is in the Prime (I'm sure it is lol) and be sure you're using the most recent update from the ASUS site. (.21 is available)
ok will try that thanks again for your help
buxtahuda said:
The actual zip file I think. Just rename it to "EP201_SDUPDATE.zip" and put it directly on a microSD card (not in any folders or anything, that is in the root of the card). Put that card into the Prime, and proceed to turn off the Prime. Turn the Prime on and when it vibrates push the Volume- button until you see some text on the screen, then press the Volume+ button within 5 seconds or so. Some more text will show up, and after a bit your Prime will either show the update Android and go about its business, or it'll show you the sad dead Android with the exclamation mark.
If you get the exclamation mark, make sure the microSD card is in the Prime (I'm sure it is lol) and be sure you're using the most recent update from the ASUS site. (.21 is available)
Click to expand...
Click to collapse
i have tried everything and no success, i keep getting the red exclamation mark android, not sure what to do from here any other suggestions.
thanks again
buxtahuda said:
The actual zip file I think. Just rename it to "EP201_SDUPDATE.zip" and put it directly on a microSD card (not in any folders or anything, that is in the root of the card). Put that card into the Prime, and proceed to turn off the Prime. Turn the Prime on and when it vibrates push the Volume- button until you see some text on the screen, then press the Volume+ button within 5 seconds or so. Some more text will show up, and after a bit your Prime will either show the update Android and go about its business, or it'll show you the sad dead Android with the exclamation mark.
If you get the exclamation mark, make sure the microSD card is in the Prime (I'm sure it is lol) and be sure you're using the most recent update from the ASUS site. (.21 is available)
Click to expand...
Click to collapse
never mind i got it i had to use the .15 update not the .21 i cant thank you enough man thanks a million.
spencerj2001 said:
never mind i got it i had to use the .15 update not the .21 i cant thank you enough man thanks a million.
Click to expand...
Click to collapse
Good stuff! Glad it worked out, I was a bit skeptical it would
I guess maybe you can't upgrade with it either, although I thought that was the point? lol again, glad it got worked out regardless.
Sent from my Transformer Prime TF201 using XDA Premium HD via my tethered HTC Vision
OK, I recognize I might catch some crap on this, since you guys don't know me from Adam, but it's a crappy situation. My friend passed this on to me, because he is stumped. His brother died in a car wreck on Christmas night, and found among his possessions in the car was this Venue 8320. It's set up with a pattern lock, and of course we can't get past it.Don't have access to the email, because the guy is dead. His father tossed the cell phone that might have been linked to the email, so we can't get in the email that way. So, I'm trying to figure out how to either bypass the pattern lock, or barring that, reset it so that it's at least usable.
I've loaded the Intel Android drivers on my computer, and can get an ADB shell, or access the fastboot when booted into Droidboot, but without root access I'm still pretty limited in what I can do. Is there any way in to this thing, or is my friend SOL?
Rasilon said:
OK, I recognize I might catch some crap on this, since you guys don't know me from Adam, but it's a crappy situation. My friend passed this on to me, because he is stumped. His brother died in a car wreck on Christmas night, and found among his possessions in the car was this Venue 8320. It's set up with a pattern lock, and of course we can't get past it.Don't have access to the email, because the guy is dead. His father tossed the cell phone that might have been linked to the email, so we can't get in the email that way. So, I'm trying to figure out how to either bypass the pattern lock, or barring that, reset it so that it's at least usable.
I've loaded the Intel Android drivers on my computer, and can get an ADB shell, or access the fastboot when booted into Droidboot, but without root access I'm still pretty limited in what I can do. Is there any way in to this thing, or is my friend SOL?
Click to expand...
Click to collapse
factory reset clears all lock codes but also deletes all info.
power off, then power on while holding voume down button
you should select the option called recovery, on the recovery screen you should c da droid on his back when you are there press and hold power button and voolume up button for 2 or so seconds and you should enter recovery mode
chairsz said:
factory reset clears all lock codes but also deletes all info.
power off, then power on while holding voume down button
you should select the option called recovery, on the recovery screen you should c da droid on his back when you are there press and hold power button and voolume up button for 2 or so seconds and you should enter recovery mode
Click to expand...
Click to collapse
Hmm. When I go to Recovery, all I get is a picture of an android on it's side with a repair hatch open. There does not appear to be any way to do a reset from there, at least not that I can see.
I've been trying to root it, but SuperOneClick isn't working. I tried pushing the various included files manually and executing them, but they won't execute - the error message is "not executable: magic 7F45". I tracked down x86 versions of su, busybox, etc. and they will execute, so it looks like all I need now is an x86 binary for rageagainstthecage/psneuter/zergRush. Does anybody know where I would track one down? I haven't had any luck finding one so far.
When at then android hatch picture you can press power then vol+ same time, let go and u will have more options. Good luck.
Sent from my Venue 8 3830 using xda app-developers app
Rasilon said:
Hmm. When I go to Recovery, all I get is a picture of an android on it's side with a repair hatch open. There does not appear to be any way to do a reset from there, at least not that I can see.
I've been trying to root it, but SuperOneClick isn't working. I tried pushing the various included files manually and executing them, but they won't execute - the error message is "not executable: magic 7F45". I tracked down x86 versions of su, busybox, etc. and they will execute, so it looks like all I need now is an x86 binary for rageagainstthecage/psneuter/zergRush. Does anybody know where I would track one down? I haven't had any luck finding one so far.
Click to expand...
Click to collapse
there is a working method of rooting this tab is for the 4.2.2 version ( some 4.2.2's are not really working with root but others are) and if your tabby is the 4.3 update then that method to root exists somewhat but the creator of that method isnt releasing it till he deems its ready. so just look in this forum somewhere you'll find you root method if your on 4.2.2
also to enter recovery when at the droid on his back screen press and hold the volume up and power button simultaneously
there you can wipe stuff.
chairsz said:
there is a working method of rooting this tab is for the 4.2.2 version ( some 4.2.2's are not really working with root but others are) and if your tabby is the 4.3 update then that method to root exists somewhat but the creator of that method isnt releasing it till he deems its ready. so just look in this forum somewhere you'll find you root method if your on 4.2.2
also to enter recovery when at the droid on his back screen press and hold the volume up and power button simultaneously
there you can wipe stuff.
Click to expand...
Click to collapse
Yeah, thanks. I don't think it's 4.3, because it hasn't been on a network since 12/25, although perhaps that's why I haven't been able to root it. Kernel version is 3.4.34, which I see has been reported as present in a patched 4.2.2 version that is not vulnerable to standard 4.2.2 exploits. I guess that's what I haven't been able to get in. I'll tell my friend that he can either wait for a 4.3 root exploit to be released, or wipe it clean.
Thanks for the help chairsz.
Alright. I need some advice one last time, I swear... after this I'm not going to try to do anything.
Phone worked quite well for 2 days. I was enjoying this rom quite a bit. I decided to change the DPI down to 560. I saw that some others in this thread had done so quite easily... so I used this app to change it. Made the change to 560, granted supersu permission and rebooted. Only problem is that... the phone has yet to turn back on. At the moment the only thing I can get it to do is give me a screen that shows a large white empty battery with a cable leading up to it and a hazard exclamation mark in the bottom right when I am trying to put it in download mode. I have tried on multiple computers to restore back to stock following these directions. The best that happens is my computer recognizes an unrecognized device. No luck.
I would love to change the buildprop back or anything, but not even adb recognizes the device.
Otherwise, nothing. I can't get into recovery. I can't get the phone to start at all. All black screen. I can't get any reaction out of it. Any advice would be helpful, I'm on hour two of this. I realize that this is most likely not a problem with the rom, but wanted to see if anyone else had an issue and has advice/let anyone else who's thinking of changing the DPI and shared my troubles reconsider.
Thanks again!
The empty the battery logo is because the phone is dead try charging it for like 30 mins. Also it seems that app you used is 3 years old so it does not support lollipop or even kitkat. After charging it try get it into recovery and restore a backup. If you don't have a backup try wiping your data and cache.
1619415 said:
The empty the battery logo is because the phone is dead try charging it for like 30 mins. Also it seems that app you used is 3 years old so it does not support lollipop or even kitkat. After charging it try get it into recovery and restore a backup. If you don't have a backup try wiping your data and cache.
Click to expand...
Click to collapse
Thanks for the reply!
That emblem only shows up when the battery is removed and I'm trying to put the phone in download mode. So it makes sense. Any other ideas? The battery that I'm using is about 80% full. I still can't find a way to recovery mode.
What other information can I provide to help you out?
Well when your in download mode it does not take any commands can you get the lg powered by android screen? Or just nothing happens? If nothing at all happenes it is most likly bricked. If it boots to the lg screen it is most likly soft bricked.
Bricked- Phone is dead and very very hard to fix if there is a fix
Soft Brick- No OS so you have to reinstall a rom could also be, because of apps.
1619415 said:
Well when your in download mode it does not take any commands can you get the lg powered by android screen? Or just nothing happens? If nothing at all happenes it is most likly bricked. If it boots to the lg screen it is most likly soft bricked.
Bricked- Phone is dead and very very hard to fix if there is a fix
Soft Brick- No OS so you have to reinstall a rom could also be, because of apps.
Click to expand...
Click to collapse
No screen. For anything (other than described).
This is exactly what I was afraid of, but my phone has always been odd. This dead battery screen has always shown up in download mode... even when my phone worked, I've never had the firmware update screen. Which has always been weird to me.
However, the only time my phone shows anything is with the dead battery screen. During such it will show up as an unrecognized device when attached to a computer, again... it's always done this. I was just curious if there was something else or a suggestion that someone more experienced then myself might have.
No that I read it, it sounds like there maybe a very slim chance of getting your device to work. If you mange to get some drivers for the unreconized device driver you maybe able to send adb and fastboot commands. I found this one tool (will limk below) that is call cydia impactor I found in one of rootjunky's toolkit files. I used this one function that was able to make drivers for my sony smartwatch 3 and phone. I will link for the direct download make sure to extract the zip. Inside of the zip you will find another zip called "Impactor_0.9.14.zip" make sure to extract it to it's own folder. If you want you can delete the first folder juat save the impactor folder. Then run the program called "Impactor" can connect your phone to the computer and click on the tab called "USB" then click the button called "Driver Scan". Follow any on screen instructions. It should now generate a driver for your phone if all went well and it will be reconized. Then you should be able to run adb reboot recovery or fastboot reboot-bootloader. The fact that your computer is even seeing the phone tells me that it has so hope of being fixed because your computer see's it. Your device might be in a bootloop of some sort. You may just have no os installed and it may have just glitched.
Download: http://rootjunkysdl.com/getdownload.php?file=Tegra Note 7/ADB root.zip (will immeditly download it)
Worst case scenario, you may try this, or at least read it for general info. I don't think you'll have to go this far though
http://forum.xda-developers.com/showthread.php?t=2582142
[FIX] NO Recovery mode, No download mode, after OTA on rooted LG G2
i changed my dpi once and it bootlooped on me. i was lucky enough to get into recovery and then i restored the data partition from an older nandroid.
i agree with 16. it does sound like the drivers may not be loaded up properly if your computer recognizes a device. have you tried the official lg drivers?
What system are you guys running?
Well, I've found out that for whatever reason... on my phone I have to take out the battery for a period of ~5-10 mins on any change DPI, system rom update, anything. Otherwise, my phone will not turn on. So if someone else find this, give it a try.
Pls help me root my zte obsidian running android 5.1 Model NO. Z820
I need help too
I also have ZTE obsidian tmobile and really want to root it i cant do much because it only comes with 4gb of space and i cant move apps to the SD card till i root Please help find a root
yeah same issue here all say that it cant after like 10-15 mins its just like nope sry
have you used this
http://forum.xda-developers.com/cro...oolbox-android-one-toolkit-one-click-t3030165
Yes, I tried. Its not working.
Is there any other way. I am desperate. It doesnt allow to move the Apps to SD card. There is no way. Locked in 4GB
I have a z820 in need of root as well. I've tried everything, including the link up there, and so far.....nope. Nothing. No apps to SD for me either.
Zte can't root for ****!!!!
I'm so mad because I really tried everything even a computer won't let me tried everything there to like why would the make a zte that can't even move your games or pictures or music to your SD card knowing danm well everybody gone need like we only got 4g that's nothing so what are we so posted to do delete stuff that we like.to trade for the other that we really don't need **** I'm pissed right now I know y'all are to but if anybody finds something please send me the info or con me by [email protected] thank you:good:
Needs update
This Phone really needs an update, it reboots and sucks, we can't even get into fastboot or anything to try to unlock the bootloader someone needs to make this possible because who in the hell uses only 4gb of storage, apps are so big and you can only download like 3 apps then you have to get rid of something if you want another app and its dumb so please someone..HELP US :crying:
Throwing my post up here so I can follow. Need root bad on this thing. I am using lite versions of every app. Lol
Same problem w/ ZTE obsidian..tCan't move to SD card. Anybody figure somethcing out yet?
I've gotten Kingroot to attempt to root it once and the results varied. Usually got 16% but the highest was almost 30% but I can't even get kingroot to even root it anymore.
The phone is not going into fastboot at all. I think the bootloader is locked. The phone will never be rooted.
I might of found a way, but it's untested so, proceed at your own risk, I am not responsible if your phone becomes bricked.
Enable developer mode and tick "OEM Unlocking" in the developer menu
Download SuperSU update zip from Chainfire's site and put it on your sdcard (internal won't work)
Power off your phone and hold power and volume up
Select recovery, wait for the android with the lid open to show up
Hold power and volume up for a couple seconds and let go
A menu should pop up, if not try again until it does
Select "update from sdcard"
Select the SuperSU zip
Let it flash the zip (shouldn't take long)
Choose reboot
See if SuperSU is installed and test that it works
Again, this is untested and would need a couple of people testing it to make sure it works flawlessly, so if this worked, please post that it did.
Nope. Thank you though.
picsles said:
Nope. Thank you though.
Click to expand...
Click to collapse
Any type of error happen or did it not allow it to flash at all?
I can't even get to recovery. Gives me the choice then goes to dead android guy.
Sent from my LGL21G using Tapatalk
Musicmanmike said:
I can't even get to recovery. Gives me the choice then goes to dead android guy.
Sent from my LGL21G using Tapatalk
Click to expand...
Click to collapse
You have to hold down power and vol up for like 2 seconds when you get to the dead android, then you'll get the recovery menu.
When I try to install the update package, I get 'opening update package' followed after less than a second by 'installation aborted'.
I powered down from the Developer Options screen with OEM unlock turned on when trying to update - it appears to turn off during boot as it is off again on restart.
Any suggestions? I looked at the logs that are visible from the recovery screen but they did not seem to have anything useful. Are there logs I can retrieve via ADB to see what the issue is?
My phone has build B18.
Kurrelgyre said:
When I try to install the update package, I get 'opening update package' followed after less than a second by 'installation aborted'.
I powered down from the Developer Options screen with OEM unlock turned on when trying to update - it appears to turn off during boot as it is off again on restart.
Any suggestions? I looked at the logs that are visible from the recovery screen but they did not seem to have anything useful. Are there logs I can retrieve via ADB to see what the issue is?
My phone has build B18.
Click to expand...
Click to collapse
OEM Unlocking is always on for me even after restarts but I haven't tried to flash SuperSU yet. You might wanna get a logcat while doing it and post it here to see if anyone knows what the problem is. I have an older build of the phone (B03) but I dunno if it matters or not.
EDIT: Also every new Kingroot build allows you to attempt to root it for like 2 days and then it just can't for some reason but the thing with 18% still happens.
LUModder said:
You might wanna get a logcat while doing it and post it here to see if anyone knows what the problem is. I have an older build of the phone (B03) but I dunno if it matters or not.
Click to expand...
Click to collapse
The logcat I am familiar with is in ADB. The only way I can find to access the phone from recovery with ADB is to select the flash from ADB option, which puts the phone in sideload mode where you can't pull data off. I was unsure if trying to load the ZIP that way would brick the phone so I haven't tried it.
I also tried using Fastboot and it doesn't recognize the phone at any time.
Is there another way to capture what is happening with the update?
I tried selecting restart in bootloader from the recovery menu with the phone connected to the PC. It stayed at the ZTE splash screen for over 10 minutes but neither fastboot nor ADB was able to communicate with it. I tried various key combinations without effect and finally ended up pulling the battery. Maybe it just froze up during boot for some reason.
I have tried every one-touch root I can find, none of them work. All the manual guides start with unlocking the bootloader - which I can't find any info on for this model. Based on the partition info, it's definitely locked: it has 27 (!) partitions including names like seccfg and oemkeystore. Is this normal for a lollipop device?