Related
Hi everyone,
thanks for taking a look at this. I bought a Nexus used and I have spent hours trying to root it. I was able to successfully unlock it a few months ago but I cannot root it.
I boot into flashboot mode using the adb command:
adb reboot bootloader
then flash the recovery:
C:\nexus> fastboot flash recovery cwm.img
sending 'recovery' <6272 KB>...
OKAY [ 0.828s]
writing 'recovery'...
OKAY [ 0.953s]
finished. total time: 1.781s
I have SU in the root directory of the SD card. After flashing the recovery i volume down to recovery and select it. The black Google screen comes up with an unlocked padlock and that is as far as I can get. It will sit on that screen for days if I let it. I've tried other, similar methods as well and get the same result. What should I try now? I've re-installed the drivers several times but that does not seem to help. I have tried this process on my XP laptop and win 7 laptop.
Also, when i try to do a factory data reset on the phone in the system settings it does the same thing.
Also another strange note... when I follow the instructions and hold the vol up and down buttons to get into fastboot mode it does not work. I have to hold only the vol up botton and power button. I do not know if that is relevant but i'm putting it out there just in case.
Any help would be very much appreciated and rewarded!
Are u able to get beyond the screen of Google the if not theb download the nexus factory images Google it out and download and extract and put it in SDK folder where all the adb and fastboot are present the go into fastboot mode and unlock ur boot loader by fastboot oem unlock by opening up a cmd by shift and right click and open cmd here then fastboot reboot boot loader and search for nexus 4 tool by mskip on Google or xda and follow the thread and follow the toolkit to root ur phone
Sent from my XT910 using xda premium
Mohhamad,
I can get past the black Google screen if I just boot up normally.
I have the Toolkit from skip and have tried that process as well. It worked for unlocking but not rooting. I will attempt it again now and see how it goes. Thanks for you suggestion i will update this shortly.
So i tried to boot to my cwm.img file using the toolkit. It put my phone into fastboot mode, installed the image and now my phone is on the black Google screen with 'fastboot status - okay' at the bottom of the screen. I heard the phone disconnect from my PC but it does not reconnect and stays stuck on this screen until i pull the battery.
Relock and then unlock
fastboot oem lock
fastboot oem unlock
make sure you have the right recovery for your phone. You might also have a corrupted recovery partition.
I would try to flash a stock rom so it can put everything back to stock (including stock recovery) then try again.
I've noticed I can not get into Fastboot mode either with UP+DOWN+Power. I can do UP+Power for recovery, thats it. Might be a 4.3 thing.
I locked and then unlocked it, rebooted, and the phone is back to stock. Not sure how that happened... or maybe that was supposed to happen. I tried to to a factory wipe just to see what it would do, sits on the black google screen with the padlock. I think you are right about my recovery partition being corrupted. I am going to see if I can flash a stock ROM like you suggested. Thank you for your help so far!
http://www.wugfresh.com/nrt/ try this and tell me if it helps
Sent from my XT910 using xda premium
Tried it Mohhamad... it's not making any difference. I tried to flash a stock ROM using wugfresh but i get failure to write errors.
I have also tried to go into download mode and see if I could get ODIN to work. Hold the volume down and power button does not work. I'm at a loss I have no idea what to do now. Any other suggestions? What method can I use to flash a stock ROM?
I bought my Nexus 7 2013 shortly after they were available and it was a good device until the release of KitKat. After the KitKat OTA it's been a piece of junk.
After the KitKat OTA it developed a problem where the tablet was on but the touchscreen was unresponsive. The only way to fix it was to shut it down by holding the power button. Eventually it started being stubborn and I'd have to power cycle it several times before it would clear the Google screen. That gradually progressed to having to do a system reset before it would come back to life.
On December 15th it finally refused to go past the Google splash. Attempting to boot into recovery also left you stuck at the Google logo. At the time I tried the WUGFresh tools to do a stock recovery and while I was successful in unlocking no amount of flashing / formatting / erasing would give you a normal boot or a recovery screen.
I sent it off to ASUS on 12/17 and got it back this past Monday (1/13). It worked fine until Tuesday night when once again the screen was unresponsive and I had to shut it down by holding the power button. It's now stuck at the Google screen and no amount of flashing / formatting / erasing using FreshWug or fastboot directly via command line has brought it back.
Here's what I've done so far:
Spammed flash-all at least 6 times
fastboot format of /boot /system /userdata /cache multiple times
Multiple runs of WUGFresh
Flashed 4.4.2 and 4.3 images
What else is there I can do aside from sending it back to ASUS?
Does it boot to bootloader?
Sent from my Nexus 7 using Tapatalk
As Micheal said, can you get to the bootloader? Do all of these commands go successfully?
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
I don't use Wug's tool, preferring to do things from the command line so I know exactly what's being done and to see error messages.
Pandae said:
As Micheal said, can you get to the bootloader? Do all of these commands go successfully?
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
I don't use Wug's tool, preferring to do things from the command line so I know exactly what's being done and to see error messages.
Click to expand...
Click to collapse
This
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
Pandae said:
As Micheal said, can you get to the bootloader? Do all of these commands go successfully?
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
I don't use Wug's tool, preferring to do things from the command line so I know exactly what's being done and to see error messages.
Click to expand...
Click to collapse
Yes to all of those, I just did them again to verify. FYI WUG opens a command shell as it runs fastboot so you can see what it's up to.
Anywhoo I reflashed kot49h (manually) and got the same result, stuck at Google. If this thing wasn't still under warranty I'd snap it in half and light the two halves on fire.
Any other ideas?
What if you tried a custom recovery and custom ROM?
So I ran through the procedure once more last night and it worked! After about 20 minutes the tablet rebooted on it's own, displayed the working android and then booted up. I guess you just need to reflash 22 times?
buelldozer said:
So I ran through the procedure once more last night and it worked! After about 20 minutes the tablet rebooted on it's own, displayed the working android and then booted up. I guess you just need to reflash 22 times?
Click to expand...
Click to collapse
any updates? is it working fine now? any random reboots? god i hated that on my 1st nex7fhd, im on my 2nd one, its and perfect aside from the 'low speaker volume' stock
Might be an hardware issue, don't get stuck with software too much, send it again until they replace it.
I'd be interested in what ASUS did to it.
Did they include a list of parts replaced, etc?
I'm also curious.
As long as the flashes are done correctly it should boot fine.
However, I had a similar issue flashing stock.
The fix was to flash stock. Boot.
If it boot looped restart and wipe dalivik cache and cache and reboot. It should start then. just an FYI...
Sent from my Galaxy Nexus using xda app-developers app
If u get boot loops = lemon, it will develop those anno ying reboots
Via my NeXus™ 7 FHD on Tapatalk⁴ Pro
So it did it again but following the previous directions I was able to unloop it immediately the big story though is WHY it was looping.
I have a minisuit BT keyboard / case ( http://www.amazon.com/Minisuit-Blue...=UTF8&qid=1390433882&sr=8-3&keywords=minisuit ). The thing is dynamite and I love it and it worked great! The keyboard has a low power battery saver state so after you don't use it for a few minutes it basically goes to sleep until you tap a few buttons and wake it up.
I went a week with no issues but I wasn't using the keyboard. When I did finally use the keyboard I would stop typing and let it go to sleep as I always do. When I tapped a few keys it would wake up and then wake up the N7 and it's screen but the screen would -not- accept touch input. I had to hold the power button down and force the N7 to shut off. When I powered it back up...BAM...LOOPED.
It didn't do this before the Kit Kat upgrade. It's obvious that something is wrong with the BT stack in 4.4.2 and when a HID goes into a low power state it hoses the touch input. Since the touch input is hosed you can't shut it down correctly and the file system corrupts, likely the /system partition.
If I use the N7 without the keyboard it's perfectly fine.
userdelroot I couldn't clear dalvik on mine because I couldn't boot to recovery. All boot options lead to a Google Loop.
I have had exactly the same experience, basically. Just got mine back from ASUS, worked for about a day, and then BAM, back to the same DAMN thing! I think you may be on to something about the BT stack. If there is any common thread to both my breakdowns, its that my Nexus got screwed not long after i paired a BT headset with it. Its late and I'm frustrated as all hell so please forgive my short rant. So what to do? Do I send it back to ASUS and hope they actually replace it this time? (The invoice I got back from them was very strange incidentally. I couldn't tell what they did, except among four parts listed, they seemed to replace a "cracked, broken screen" which was not the way it was when I sent it to them???!) Or should I just keep reflashing and hope it takes, as it seemed to do for you? But then can I risk pairing my BT headset again?! This sux.
Update: Woke up this morning, turned it on, and it booted up! WTF? Not complaining I guess. Taking it easy this time, unlocked bootloader still of course, but holding off rooting, and not going to pair any BT with it for awhile. Although its kinda BS I should have to try it this way...
It's at it again but this time time I wasn't using my keyboard (I quit using it thinking that was the problem).I'm attempting to unloop it again using the same procedure as before. Use of the BT may aggravate the problem (it certainly took longer to glitch out this time) but it's not the whole problem.
I didn't have these problems before the 4.4 update so I'm rolling back to 4.3 for some testing.
buelldozer said:
It's at it again but this time time I wasn't using my keyboard (I quit using it thinking that was the problem).I'm attempting to unloop it again using the same procedure as before. Use of the BT may aggravate the problem (it certainly took longer to glitch out this time) but it's not the whole problem.
I didn't have these problems before the 4.4 update so I'm rolling back to 4.3 for some testing.
Click to expand...
Click to collapse
I have the same problem. Described it right here: http://forum.xda-developers.com/showthread.php?t=2653430
Nothing helps me =( Please, write down any solution, you are able to find.
You wrote, you was able to boot it normally. What did you do for that?
Demian87 said:
I have the same problem. Described it right here: http://forum.xda-developers.com/showthread.php?t=2653430
Nothing helps me =( Please, write down any solution, you are able to find.
You wrote, you was able to boot it normally. What did you do for that?
Click to expand...
Click to collapse
Perform these steps in this order:
fastboot format userdata
fastboot format cache
fastboot format system
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash-all.bat
Then wait at least a full hour before deciding it didn't work. Mine takes a very long time to 'recover' and boot up after that procedure. I'm beginning to suspect that the problem is actually in the /cache partition as it's one of the things that isn't addressed in the flash-all script and it appears to retain information between reboots. The next time this happens I'm going to format and erase just cache and see what happens.
I'm serious on waiting a full hour, and it may take two. I just started it on mine and am timing it now to see what it actually takes.
buelldozer said:
Perform these steps in this order:
fastboot format userdata
fastboot format cache
fastboot format system
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash-all.bat
Then wait at least a full hour before deciding it didn't work. Mine takes a very long time to 'recover' and boot up after that procedure. I'm beginning to suspect that the problem is actually in the /cache partition as it's one of the things that isn't addressed in the flash-all script and it appears to retain information between reboots. The next time this happens I'm going to format and erase just cache and see what happens.
I'm serious on waiting a full hour, and it may take two. I just started it on mine and am timing it now to see what it actually takes.
Click to expand...
Click to collapse
Thank you a lot! I'll try to leave it turned on for the whole night. I left it only for 45 minutes before that. Probably, that was not enough.
My tablet is now at 3.5 hours and still hasn't left the "Google" screen. "All Night" might be the correct time frame. I'll give it another 4 hours and see what that does.
buelldozer said:
My tablet is now at 3.5 hours and still hasn't left the "Google" screen. "All Night" might be the correct time frame. I'll give it another 4 hours and see what that does.
Click to expand...
Click to collapse
My tablet is now at 9:15 hours and still at Google logo. I'm guessing that the time is not the only matter for normal boot up.
---
Now after 11 hours I gave up. =(
Hi Guys, I had Nexus 7 2013 Mobile with Android 4.4.2 running. I tried to update it to recent release 5.0.2 from factory image. When I run command "flash-all.sh", it did not continue at "rebooting to bootloader...". I had to manually stop the process and it still can boot into 4.4.2. After that I tried flashing it manually by running fastboot commands. It then stucked at 'sending system'. I again had to manually stop it. That erase the OS and can boot only into bootloader. I once again tried the luck and run the "flash-all.sh" and it stucked again at the same "rebooting to bootloader..." stage and after manually stopped it, it will not let me boot into anything except Google logo. I can't switch off it, it auto reboot and stop at Google logo. ADB can't detect the device.
Can anyone help me?
How long did it stick? It can take several minutes to send System to the tablet.
Run the commands in the script manually. It should be pretty straightfoward, as long as your bootloader is up to date, if it is not, you'll have to find the last valid bootloader. It's NOT in the Nexus Images, Google has screwed that up repeatedly, although it's possible that the 2013 model is okay, I know the 2012 model has that issue. Anyway.
If you're okay with nuking the whole device, just manually flash recovery, system, and data with fastboot. Again, it's all in the batch file. If you just want to update, you can just flash system.
So here's the deal, I tried to format the cache partition of a stock, non-rooted and non-unlocked bootloader Zenfone 2 (Z00A) through recovery, and it somehow failed/got stuck. After about 1h, I shut down the phone via long-pressing the power button and now it won't boot.
Booting it just leads to an "error!' message and stay there. Trying to go back to recovery does the same thing, I can get to the initial fastboot screen, but selecting recovery mode and pressing power+vol up after the reboot doesn't lead to recovery at all. Instead, every 5 or 10 seconds, the screen clears to black for 1 sec and the same error message shows up.
I tried to get access to it through ADB, but it won't show up in the device list under either the fastboot screen or the Error! message screen on which it stays stuck. Also, the phone was setup so that it didn't allow USB debugging, but I doubt that matters, given that it can't even load Android at all.
Is there something I can do about it? Any tip is greatly appreciated, I looked around XDA and Reddit but didn't find anything that really helped.
When you get to the Error screen, hold power and press up volume button. It should get you to recovery...
You can also clear the cache in fastboot mode using the command "fastboot erase cache". It will ask if you want to format/erase cache, say yes and it should clear your cache in a few seconds...
ultramag69 said:
When you get to the Error screen, hold power and press up volume button. It should get you to recovery...
You can also clear the cache in fastboot mode using the command "fastboot erase cache". It will ask if you want to format/erase cache, say yes and it should clear your cache in a few seconds...
Click to expand...
Click to collapse
Thanks, I had tried various variations of that approach but the issue was a bit more complex than that. In the bootloader, the phone was detected by Windows and drivers from Asus installed properly. ADB wouldn't list the phone, but fastboot did. However, any operation by fastboot was denied access because USB debugging was not enabled prior to the phone going down. Otherwise, as you mentioned, fastboot erase cache would have worked fine.
In the end, I found another post on XDA by Theja which linked to a post in Spanish. The modified ADB and fastboot packet there contains a batch file that manages to bypass this issue and installs CWR, from which clearing the cache is possible. Upon reboot, Asus replaces CWR with the original recovery and things look back to normal.
Sweet, as long as you got it back up and running...
ultramag69 said:
Sweet, as long as you got it back up and running...
Click to expand...
Click to collapse
Hehe, thanks. I'm pretty happy indeed, was already considering the need for a new phone.
However, I must say that finding this toolset worries me a little bit. I thought the whole point of disabling USB debugging was to ensure that people can't perform low-level operations on the phone via fastboot/adb. In this case, this protection is somehow bypassed. I didn't have time to read through the entire batch file, nor am I proficient-enough in Android to make sense of it all, but I wonder how it was done...
In any case, I now have USB debugging left on. It increases convenience and the ability to recover things if problems occur, and it seems like the security benefits are not that strong anyways.
So before I get linked to a bunch of solutions, here's what I've tried so far as I do have fastboot access:
I've tried flashing the latest factory image from Google. Both manually from fastboot and with NRT, all to no avail. It shows the Google logo then reboots repeatedly. I've tried entering recovery to factory reset there after flashing, but the device won't get into recovery.
I've also tried this method, but I can't get the device to enter download mode. It shows that it's entering it for a moment when I plug it into my computer while holding volume up, but then reboots into the bootloop again.
There's one weird thing that should be noted that makes me think this is some weird software issue, and not a hardware failure. I let the device bootloop all night last night until the battery died. When I powered it on this morning it went all the way to the Android setup page where you select wifi, etc and go from there. However, when I plugged it in and kept going through setup, it rebooted and has been looping since. I've contacted Google and they're supposed to conference call me with LG to see what we can do. Do I have any options other than that? Thanks for any help.
From bootloader
fastboot erase cache
fastboot format cache
fastboot erase user
fastboot format user
BTW what exactly is happening when you say it doesn't enter recovery?
addisontodd said:
So before I get linked to a bunch of solutions, here's what I've tried so far as I do have fastboot access:
I've tried flashing the latest factory image from Google. Both manually from fastboot and with NRT, all to no avail. It shows the Google logo then reboots repeatedly. I've tried entering recovery to factory reset there after flashing, but the device won't get into recovery.
I've also tried this method, but I can't get the device to enter download mode. It shows that it's entering it for a moment when I plug it into my computer while holding volume up, but then reboots into the bootloop again.
There's one weird thing that should be noted that makes me think this is some weird software issue, and not a hardware failure. I let the device bootloop all night last night until the battery died. When I powered it on this morning it went all the way to the Android setup page where you select wifi, etc and go from there. However, when I plugged it in and kept going through setup, it rebooted and has been looping since. I've contacted Google and they're supposed to conference call me with LG to see what we can do. Do I have any options other than that? Thanks for any help.
Click to expand...
Click to collapse
it's seems like me , it's been a month i can't boot it up .
sfhub said:
From bootloader
fastboot erase cache
fastboot format cache
fastboot erase user
fastboot format user
BTW what exactly is happening when you say it doesn't enter recovery?
Click to expand...
Click to collapse
I choose reboot recovery from the fastboot menu and it just boot loops. It won't enter recovery.
addisontodd said:
I choose reboot recovery from the fastboot menu and it just boot loops. It won't enter recovery.
Click to expand...
Click to collapse
what if you try
fastboot boot twrp.img
I've bootlooped so many times I don't know where to start.
So you flashed the factory IMG from your bootloader correct.
Fastboot -w will wipe without wiping system.
Then reflash your whole system. I would redownload from the Google site through Skipsoft...the easiest way. When it asks to keep or flash new recovery you want to flash the stock recovery.
http://forum.xda-developers.com/nex...olkit-skipsoft-android-toolkit-nexus-t3230444
You'll have to reroot afterwards which you can also do through skipsoft.
Profit... Thank me if I helped.
It's a Hardware issue. Installing system again will not fix it. Send it to LG for a repair. My phone had the same issue.