Hey guys,
I'm not sure if I'm the only one having this problem, but I'd figure I'd shout it out here anyway.
So, to put it short, I have a rooted, NON-unlocked (i.e. still locked) Transformer Prime. I tried to update it to Jelly Bean via OTA, and it failed, okay, fine.
Thing is now though that when I reboot the tablet, it just gets stuck in a blank black screen (screen still backlit) after the Eee Pad Asus Logo on boot.
Anyone have any tips for me on how to go about getting out of this mess? :X
If you are against a wall here, you can hold volume down while turning the prime on to access the bootloader. You can do a data wipe from there which will solve your issue. You will, though, lose all your data on the device (sdcard is fine, though)
Just tried that, and I did a wipe, but I'm still faced with a black screen no matter what I do :<
Anything else I should try?
hamsteyr said:
Just tried that, and I did a wipe, but I'm still faced with a black screen no matter what I do :<
Anything else I should try?
Click to expand...
Click to collapse
Yikes. I think you can place the update .zip on the root of your sdcard and update that way. If you are getting by the initial ASUS screen and can access the recovery menu, then it is just a matter of reapplying the update. Safe to assume you are still locked?
Hmmm... I can try that, And yes, my bootloader is locked. I was going to unlock it, but never got down to it, and now I am thinking of ways to try and force CWM or something similar into it.
I'm trying to see if I can fastboot or something
hamsteyr said:
Hmmm... I can try that, And yes, my bootloader is locked. I was going to unlock it, but never got down to it, and now I am thinking of ways to try and force CWM or something similar into it.
I'm trying to see if I can fastboot or something
Click to expand...
Click to collapse
I was just reading through the failed update thread, and the procedure to go about it requires access to adb and the os, both of which aren't running [properly] for you. Putting the update on your sd card, though, won't hurt anything. Maybe we can discover something. If you let the tab sit at the black screen, do you eventually get adb access? Were you rooted before? In a perfect world you could get adb to /system rw and go at it from there... but i am sure that won't happen lol
Hmmm, I'm trying to see if I can somehow access ADB through recovery or something similar, though I'm not hitting much luck just yet.
Fastboot doesn't seem to look the same for me as it does for you guys as well I wonder if there's any way around this
hamsteyr said:
Hmmm, I'm trying to see if I can somehow access ADB through recovery or something similar, though I'm not hitting much luck just yet.
Fastboot doesn't seem to look the same for me as it does for you guys as well I wonder if there's any way around this
Click to expand...
Click to collapse
I tried to access adb from every menu (less wipe) there. I had a batch script going nuts with adb devices. I remember back in the day on an old htc a recovery loop is what got adb access with raised permission, but that is probably patched.
I read that using fastboot to flash a stock blob is certainly a brick.
If you find anything, please share!
Sure thing, I'm trying to enter fastboot mode, but it's being weird, very weird.
My transformer prime doesn't have the Fastboot option, only the Android Icon, and the Wipe Data icon, which I have tried and doesn't work.
God damn it OTA, why!
Related
I have yet to find an answer to this while searching for the past day, so I'm going to ask about it here.
My LG Optimus V's (just got it a few days ago as a birthday present) screen seems to be permanently blank... In case someone asks... yes, it is activated.
What Happened:
I rooted the phone using Gingerbreak 1.2, installed rom manager/clockwork recovery mod, then attempted to backup my phone in case something went wrong. However, when I started the backup, I noticed that the screen was completely blank. I was kinda freaking out, so I just took a shower while it did it's thing. When I came back, it was done creating the backup and it showed up in Rom Manager. After toying with some of the things I can do with it rooted (I only rooted it to see how much of a difference it would make without changing the kernel), I decided to recover that backup. When my phone restarted to recover the backup, the screen was blank once again. After waiting for over an hour, I concluded that it must have finished (since my HTC Hero would finish restoring and never reboot until I tell it to) and took out the battery. Afterwards, it would show the LG splash screen... then the blank screen.
What I Did:
I was thinking about the android screencast java application a few hours after my problem first developed. I plugged my phone into my computer, got adb working, and android screencast showed me that my phone was actually getting stuck at the clockwork recovery mod screen. I tried many things... I installed a CM7 rom, flashed 3 different recoveries, flashed an overclocked stock rom, etc. Eventually, I flashed the stock rom (no changes whatsoever) and stock recovery. Now I can hear my phone, but cannot see it. However, I should note that while using CM7 the same thing happened. The only difference being that I could use android screencast to see the screen (the phone was actually working) with CM7. Now with the stock rom, adb is disabled and I cannot see the screen or do... anything.
What I Think I Should Do:
I'm thinking about calling Virgin Mobile and telling them that my screen is defected. If they see the issue they'll probably think that it's a hardware issue (for all I know, it could be) and they'll probably give me a replacement. However, if anyone as had the same problem and fixed it, I would love to know.
I would love you hear your opinion on this and, if possible, a fix. Thanks in advance!
(JIC, if I posed in the wrong section, I'm sorry...)
you poor souls reporting the symptoms of getting the newer screen hardware from the optimus s in your v's don't number in the double digits yet, but it's getting closer.
I posted a fix on AndroidCentral, see it:
here
good luck! the fix has worked for everyone I pointed to it so far.
btw, the screencast idea is excellent!
crud. stock recovery, you may be SOL.
you'll probably have to boot into custom recovery to use screencast or adb now.
use the unplug phone -> pull&replace battery -> hold home+volume down -> keep holding, press and hold power until lg screen goes blank to enter recovery. maybe adb will work in stock recovery, I dunno.
Thank you very much for the reply!
Yeah, you're right, I'm probably SOL... I still have one option though! Theoretically, I should be able to turn on ADB without being able to see my screen. I know how to access the settings without seeing it, but navigating myself to the "Applications", "Development", "USB Debugging" may be a little hard. I will attempt to do so. I will report my progress in a bit.
However, if you (or somebody else) could provide screenshots of a step-by-step process to turn on USB Debugging in the stock rom (since it's kinda hard to do remember where everything is and screenshots of different phones is kinda different) then I would appreciate it VERY much!
I shall update this in an hour or so.
UPDATE (9/2/11 - 9 PM):
I'm going to take a break for now. Good thing I give everyone my Google Voice number, I doubt anyone will notice a change. I'm going to flash a stock rom onto my HTC Hero so I can figure out where things are on the LG Optimus V (Same screen size) in an hour or so. I'll update my progress in like 2 hours.
UPDATE (9/3/11 - 8:10 AM):
I have been unable to turn on USB Debugging and it seems to be because I don't know where the confirmation after turning it on is located. However, I should note that when I boot into (I think) recovery, "adb devices" states that the device is attached but offline. If there is a way to make it "online" from stock recovery then I would love to know. For now, I will try everything I can.
UPDATE (9/3/11 - 8:22 AM):
Ok. I plugged my phone into the back of my computer and now when I do "adb devices" it detects the device in recovery mode. However, when I try "adb shell" it says "- exec '/system/bin/sh' failed: No such file or directory <2> -". I'll try some more stuff, but does anyone have any idea of what I can do? Android Screencast doesn't work either, so that's not an option.
UPDATE (9/3/11 - 9:42 AM):
Crap... now it's indefinatly booting into recovery... I had something like this happen before, I'll report my status in an hour or so...
UPDATE (9/3/11 - 12:36 PM):
My friend finally got my phone booting out of recovery again! Now all I have to do is get "USB Debugging" on and it SHOULD work!
I <think> there's a key combination to power up into the bootloader. if you can find it with searching here and android central.
I haven't been able to track that down today. If you can get into the bootloader, you can fix it. Search for asadullah's fastboot root instructions here if you find a way to get into the blue screen (the bootloader, which fastboot talks to.)
otherwise, I'll be done taking the kids to the (ugh) pool in a few hours and I'll search more.
try pulling your battery for a few minutes and see if the reboot cyle stops that way, at least it might get into recovery or the rom.
glad you got back into recovery again, not too sure how to help at this stage though, since I can't find a way to get into the bootloader with a power-on key combo. just emergency mode (useless to the V since the firmware from LG is missing a file) and safe mode. boo.
there is a youtube video for enabling usb debugging on the v, maybe it'll help you find the right spots to press.
http://www.youtube.com/watch?v=nHal0hPNS6s
edit: you can also try to reboot into the bootloader with adb, even though it's missing the shell... it's worth a try, and if it works you can flash xionia recovery with fastboot and things would be a lot easier from that point.
Code:
adb reboot bootloader
if that works but you need more help, a battery pull is the only way to power off with the bootloader except "fastboot reboot" will try to boot your rom.
Awesome, thanks for the replies! I'm going to try your suggestions now. I'll let you know how things work out in a few hours. I would have replied earlier, but to my satisfaction there was a surprise party planned for me, lol. I will defiantly try these out now.
Once again, thank you very much. I honestly did not expect a reply for something that happens to such few people.
bigsupersquid said:
I <think> there's a key combination to power up into the bootloader. if you can find it with searching here and android central.
I haven't been able to track that down today. If you can get into the bootloader, you can fix it. Search for asadullah's fastboot root instructions here if you find a way to get into the blue screen (the bootloader, which fastboot talks to.)
otherwise, I'll be done taking the kids to the (ugh) pool in a few hours and I'll search more.
try pulling your battery for a few minutes and see if the reboot cyle stops that way, at least it might get into recovery or the rom.
Click to expand...
Click to collapse
I'm honestly not sure what my friend did, lol. She was just messing with it while it was, apparently, in recovery and it ended up rebooting and loading the rom. I, honestly, don't want to risk getting stuck in recovery anymore since taking out the battery for an hour didn't do anything... If I'm unable to get adb on using what I know from that video then I'll try booting into the bootloader. Like I said before, I'll report my status in a few hours. I really appreciate your help up to now!
EXTREMELY HAPPY UPDATE!!! (9/4/11 - 1:22 AM)
I was able to turn on ADB! I used what I learned from that video and how turning on ADB works on my HTC Hero to get it working and it's FINALLY ON! Now I can attempt to flash the recovery, kernel, and everything else in order to get it working! Thank you VERY much! I will let you know how everything turn out
Another Wonderful Update! (9/4/11 - 2:03 AM)
I have flashed the recovery.img (the Xionia CWMA one) and can see my screen in recovery! I haven't seen anything on my screen besides the LG splash screen so I'm overwhelmed with joy! I'm flashing a new ROM and the other stuff now!
Final Update! (9/4/11 - 2:09 AM)
2:05 AM - I see the rom's boot screen!
2:06 AM - I see the CM7 Mod boot screen!
2:08 AM - I see the UI on my screen and everything seems to be working! Thank you VERY much!
Quick question though... If I want to install a new ROM, do I need to flash the xionia anykernel one directly afterwards?
ah, excellent! glad it's working now.
you're the most persistent (and maybe technically apt) person I've helped with this so far.
I still think that using screencast was the best new idea I've seen yet.
yes, you'll need to flash the xionia kernel after flashing any rom or rom update.
roms come with their own kernel in the boot.img, and none of them currently out for the v have the video drivers from the newer sprint kernels.
right now, xionia kernel is the only thing that works.
and, you'll need to flash the key swap after changing roms, as well, but at least forgetting to do that won't take out your display.
now that you've got xionia recovery on your phone, it should be a lot easier next time.
Thank you for both the help and the compliment!
I don't like giving up when it's something I know I can do. I figured that if I was able to mount my SD card without being able to see the screen, I should be able to turn on USB Debugging as well. About the Android Screencast... I didn't actually think about it until it until I plugged in my phone while the screen was blank, ran "adb devices", and saw that my device was detected within recovery. I figured that I might as well give it a shot... and it worked.
Alright, that's what I figured. Hopefully someone realizes what's happening with refurbished Optimus V smartphones and ports the newer sprint kernels to the Optimus V. I feel like I got ripped-off though... I bought my phone "new" and got a refurbished one. I can't really do anything though, we're not technically supposed to be rooting our Virgin Mobile phones anyways, lol. I'll be sure to do that everytime now though. For now, I think I'm good with the Bumblebee rom.
Once again, thank you VERY much for your help! I know I would not have been able to fix my phone without your help.
EDIT:
Oh yeah, btw, if the Optimus V ever gets stuck in stock recovery, press the "back" button then "home" button to boot into the rom. Not sure why it works (I was never able to see the screen), but it worked.
There is a key combo!
First time caller long time listener... I bricked my own Optmus V with a bogus ROM. To boot into recovery without adb press (Home)+(Volume Down)+(Power) Now rocking CM7!
I recently bricked my tablet after having it rooted for a very long time...a Samsung-issued update apparently screwed with something crucial.
Anyway, I tried the nvflash recovery methods as mentioned in this thread: http://forum.xda-developers.com/showthread.php?t=1130574
However, it seems that I have what they called a "locked" tablet. I get the 0x4 error he mentions and absolutely nothing happens when I send the command in nvflash.
Is there any update on this recovery method with locked tabs? I tried seeking paid services where they hook up devices to a JTAG and whatnot, but I've only seen that for the original Galaxy and not the 10.1--if you have any information about that route, that would help too.
Thanks!
you can try flashing a old rom if you can thats what i did and it worked for me
samwest39 said:
you can try flashing a old rom if you can thats what i did and it worked for me
Click to expand...
Click to collapse
The thing is I can't flash to different ROMs or even get the Tablet to boot up into download mode...
go to recovery mode
I can't get into recovery mode too. All of the partitions are screwed, and the only way of reviving this device is by flash through the NVidia Recovery Console (nvflash). The thing is, my device is one of the lucky ones that are locked..Thus, it requires a special key to unlock it before I can do anything in nvflash.
I have no idea if this would work, but you could try it ...
A few months ago I was flashing a ROM on a friends phone and something went wrong, the phone wouldn't even boot up any more, the screen stayed blank all the time, no matter which combination of buttons I pressed of how long I held them down for. ODIN didn't recognise it being connected to the PC etc... nothing worked.
Then I tried hooking the phone to the PC again and tried to do something with adb. And somehow, the phone was connected on adb. Tried an adb restart-to-download command and after a minute or two, the phone booted up and I could flash through ODIN again.
I have no idea why it worked, but it did ... lucky me .
So while I doubt it will work, it might still be worth a try. And if adb connects in any way you could maybe figure what was wrong and somehow fix it?
I also heard about some phones being locked out in a similar way and a procedure in the lines of "take the battery out, hold down 3 buttons, slide the battery in WHILE STILL HOLDING the buttons" worked, maybe there's something similarly "hidden" on the tab?
I hope you find your answer!
My prime is stuck in a bootloop.
It starts up at the Asus screen with the powered by Nvidia in the bottom right corner, and "The Device is Unlocked." in the top left.
I can't seem to get to recovery.
I also can't get adb access.
I've tried t fastbooting, but I don't really know the proper method/time. So I'm not sure if I'm doing it right. Currently it just says waiting for device.
Any help is appreciated. Thanks!
Do you get the icons when holding volume down and power?
Before flashing did you backup the blobs with nv tool
TheArtiszan said:
Do you get the icons when holding volume down and power?
Before flashing did you backup the blobs with nv tool
Click to expand...
Click to collapse
Alas, I did not. Actually I bought this used on ebay, hoping to fix it. I'm not sure if it's nvflash enable or not. A bit knew to nvflashing. I'll look into it.
Yeah that would be about the only way you might be able to get it back up and running again.
Might want to check out the unbricking thread in the development section and read through that.
It should give you enough information about the tools and set them up and try a few different things.
If the fastboot works you might be able to flash the default blobs or something to get it back.
Another thing you can try first, if you can get fastboot working, is to just fastboot flash a recovery from TWRP or others and see if you can boot into that.
Thanks, I'll look into it.
Having glanced at the guide, I noticed that the button combination is Vol Up + Power. And that it leads to a blank screen. As it turns out, I originally thought that was the button combination for recovery. And that led to a blank screen. So, so far it's looking good.
Edit: As it turns out, I don't have my device's nvflash files. I'll keep looking into it.
Well no luck so far, may have to give up.
Hey ucenna,
Have you found a fix for your Prime? Mine is exactly like yours. And I don't know Asus machines. Think I may have to go to Samsung only.
Hi,
I recently unlocked and rooted my device. Asus Transformer Prime (TF201).
I tried to boot it into recovery, wouldn't boot the rom, kept freezing, hard reset it. Then it booted into the official android version, I was running 4.1.1, build # 10.4.2.18
Then I went into recovery, and I was like "oh yeah, I remember reading that it has to be a fresh install, that way there's no incompatibility". So I decided to press the down button until I got to erase everything in the menu, I did it. Erased it, device reset itself, and now it's stuck in the main loading screen, where it says Asus, this device is unlocked in the top left, and the nvidia symbol in the bottom right. The device wont boot into anything, not even recovery settings. Is there a fix? Or did I just make my tablet a paper weight?
I tried searching the web, I found all these articles, and frankly I'm very overwhelmed, and didn't know what to do or which one to read. I just got the tablet as a Valentines Day gift from my wife, and I would have to have ruined it. Please help me.
EDIT: I got my device to appear as "APX" in devices and printers, it's an unknown device. But I'm still lost.
Hi
Thanks for writing to us at XDA Assist. Please standby while we have your thread/question moved to the appropriate sub-forum for your device.
For future reference you can find your device sub-forum here (bookmark/subscribe this):
Asus Eee Pad Transformer Prime
Within that section you will find a dedicated q&a sub-forum (this is where your thread is going to be moved to):
Eee Pad Transformer Prime Q&A, Help & Troubleshooting
Good luck!
Bump, could really use some help...
GiordyWarner said:
Bump, could really use some help...
Click to expand...
Click to collapse
There is only hope, if you can manage to get into bootloader screen by pressing power + vol down.
APX mode would only help you, if you had pulled your nvflash files.
GiordyWarner said:
Hi,
I recently unlocked and rooted my device. Asus Transformer Prime (TF201).
I tried to boot it into recovery, wouldn't boot the rom, kept freezing, hard reset it. Then it booted into the official android version, I was running 4.1.1, build # 10.4.2.18
Then I went into recovery, and I was like "oh yeah, I remember reading that it has to be a fresh install, that way there's no incompatibility". So I decided to press the down button until I got to erase everything in the menu, I did it. Erased it, device reset itself, and now it's stuck in the main loading screen, where it says Asus, this device is unlocked in the top left, and the nvidia symbol in the bottom right. The device wont boot into anything, not even recovery settings. Is there a fix? Or did I just make my tablet a paper weight?
I tried searching the web, I found all these articles, and frankly I'm very overwhelmed, and didn't know what to do or which one to read. I just got the tablet as a Valentines Day gift from my wife, and I would have to have ruined it. Please help me.
EDIT: I got my device to appear as "APX" in devices and printers, it's an unknown device. But I'm still lost.
Click to expand...
Click to collapse
Hi, u can follow the steps listed in this blog. I just installed CM11 using the same steps over the weekend. U need to perform a factory reset and wipe the cache after u installed the ROM using the CWM recovery. If not, it will be struck in the boot screen with the arrow going in circle. Below is the blog address:
d3-media.blogspot.sg/2014/08/upgrading-asus-prime-tf201-to-android.html
Good luck flashing!!
gsanglan said:
Hi, u can follow the steps listed in this blog. I just installed CM11 using the same steps over the weekend. U need to perform a factory reset and wipe the cache after u installed the ROM using the CWM recovery. If not, it will be struck in the boot screen with the arrow going in circle. Below is the blog address:
d3-media.blogspot.sg/2014/08/upgrading-asus-prime-tf201-to-android.html
Good luck flashing!!
Click to expand...
Click to collapse
This has nothing to do with what he is asking.
flumpster said:
This has nothing to do with what he is asking.
Click to expand...
Click to collapse
Hi,
I've same problem!
I tried to flash to android 5.0. I tried many things via twrp and now, thats it:
My TF201 stucks also at bootscreen and the recovery menu (Power on + Vol.Down) won't work. That means I'm not able to get in fastboot mode or something like that. The only possiblity to switch the device off at the moment is to unplug the battery
I've searched for a solution in many boards, but unitl now i haven't found anything.
At the moment it seems that the only possibility we have, is to change mainboard, or to try to connect via an external programmer (for flashing the memory), but that would be for sure not the easiest way, or it could be also nearly impossible.
So at the moment I'm praying to god, that someone will have another solution and will post it here, because otherwise I can cast away my loved transformer prime :crying:
Looking forward to hear any news about that topic :fingers-crossed:
Jimboy00 said:
Hi,
I've same problem!
I tried to flash to android 5.0. I tried many things via twrp and now, thats it:
My TF201 stucks also at bootscreen and the recovery menu (Power on + Vol.Down) won't work. That means I'm not able to get in fastboot mode or something like that. The only possiblity to switch the device off at the moment is to unplug the battery
I've searched for a solution in many boards, but unitl now i haven't found anything.
At the moment it seems that the only possibility we have, is to change mainboard, or to try to connect via an external programmer (for flashing the memory), but that would be for sure not the easiest way, or it could be also nearly impossible.
So at the moment I'm praying to god, that someone will have another solution and will post it here, because otherwise I can cast away my loved transformer prime :crying:
Looking forward to hear any news about that topic :fingers-crossed:
Click to expand...
Click to collapse
You say this "My TF201 stucks also at bootscreen and the recovery menu". Does that mean you can still access recovery (TWRP)?
flumpster said:
You say this "My TF201 stucks also at bootscreen and the recovery menu". Does that mean you can still access recovery (TWRP)?
Click to expand...
Click to collapse
No, thats the problem, since yesterday it is not possible, because I tried to flash back to an older version of TWRP, and since that I can't access RCK and then I tried to wipe data, and since that, I even can't access to recovery console (Power on + Vol.Down).
That means I can't do anything at the moment, I see only the asus boot logo and that's it.
So I have no idea to communicate with the tablet at the moment.
The problem was, that I was not really careful, because my opinion was, that it's impossible to brick the whole tablet, but now it's gone!
Is that the end of the story, or do you know therefore a solution?
Regards,
Jim
Seems that you are in APX mode. Hope you have your blob + nvflash and wheelie to restore the bricksafe.img. (It saved my TF when i was in your position)
Good luck
Jimboy00 said:
No, thats the problem, since yesterday it is not possible, because I tried to flash back to an older version of TWRP, and since that I can't access RCK and then I tried to wipe data, and since that, I even can't access to recovery console (Power on + Vol.Down).
That means I can't do anything at the moment, I see only the asus boot logo and that's it.
So I have no idea to communicate with the tablet at the moment.
The problem was, that I was not really careful, because my opinion was, that it's impossible to brick the whole tablet, but now it's gone!
Is that the end of the story, or do you know therefore a solution?
Regards,
Jim
Click to expand...
Click to collapse
Unfortunately unless you have nvflash backups then you will have to get the board replaced. Forget contacting Asus as they would charge you more than the tablet is worth. Try and find one with a smashed screen on ebay etc cheap that still works that you can swap the board out from.
lemicp said:
Seems that you are in APX mode. Hope you have your blob + nvflash and wheelie to restore the bricksafe.img. (It saved my TF when i was in your position)
Good luck
Click to expand...
Click to collapse
Thanks for your feedback,
So I don't have these files :crying:
I found also another thread with same story, and it seems that I can search for a new MoBo....
http://forum.xda-developers.com/showthread.php?t=2143942
...or buy a new tablet, maybe the better solution...
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?