I am not a noob when it comes to android dev, but this has stomped me and I am asking for expert's help. I have a GSM version SGN that I flashed the official yakju ICL53F on it via fastboot. It has been working great for a month now. Suddenly today I felt it was vibrating in my pocket, took it out and discover it was stuck in boot loop--the google sign with the unlocked icon. I waited til I get home to put clockworkmod on it, but when I try to nandroid it first it gave me an error. Then I figure I would just fastboot the stock rom on it again, using fastboot mode like I did before. I even flashed the bootloader, radio, and system image. Still stuck on google icon with screen went blank, vibrate and repeat. Is there anything else I should try? odin mode is also available, but I am not seeing any instructions on it at the developer section so I am reluctuant to try it. I can still adb and fastboot to access my phone...help please?
well I am no noob but I am no expert either. Apparently you cannot
fastboot flash system XXXXstock_image.img, you have to use
fastboot update -w XXXstock_image.img instead.
still I am baffled by why this happened in the first place. I was ready to lock the bootloader back up and send it in for warranty...glad I didn't have to resort to that.
lettcco said:
well I am no noob but I am no expert either. Apparently you cannot
fastboot flash system XXXXstock_image.img, you have to use
fastboot update -w XXXstock_image.img instead.
still I am baffled by why this happened in the first place. I was ready to lock the bootloader back up and send it in for warranty...glad I didn't have to resort to that.
Click to expand...
Click to collapse
I think you are mixing some things up.
The "update" parameter of fastboot is used to flash a group of images inside a zip file to you device.
The "flash" parameter is used to flash a single image to your device.
The following two groups of commands do the same thing:
fastboot update -w image-yakju-icl513f.zip
or
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash userdata userdata.img
fastboot flash recovery recovery.img
fastboot erase cache
Hi,
Background issue: It experiences failures for OTA updates. Problem thread: http://forum.xda-developers.com/showthread.php?t=2380258
Then I decided to fully flash factory image according to this thread: http://forum.xda-developers.com/show...8#post44888268
During flashing it stucks on erasing system, or erasing userdata, or writing userdata, similar to this thread: http://forum.xda-developers.com/showthread.php?t=1593617&page=2
fastboot erase userdata, or fastboot -w did not work, all stuck. Also, relock and unlock bootloader did not solve this issue.
Please help! Thanks!
ly182549 said:
Hi,
Background issue: It experiences failures for OTA updates. Problem thread: http://forum.xda-developers.com/showthread.php?t=2380258
Then I decided to fully flash factory image according to this thread: http://forum.xda-developers.com/show...8#post44888268
During flashing it stucks on erasing system, or erasing userdata, or writing userdata, similar to this thread: http://forum.xda-developers.com/showthread.php?t=1593617&page=2
fastboot erase userdata, or fastboot -w did not work, all stuck. Also, relock and unlock bootloader did not solve this issue.
Please help! Thanks!
Click to expand...
Click to collapse
Finally solved!
Use another computer, fresh install all drivers...... weird
I would try it over again a few times.
There appears to be some units that may have corrupted eMMC which is probably responsible for the pause. Sometimes these can get blocked out automatically by the eMMC firmware.
sfhub said:
I would try it over again a few times.
There appears to be some units that may have corrupted eMMC which is probably responsible for the pause. Sometimes these can get blocked out automatically by the eMMC firmware.
Click to expand...
Click to collapse
Got a brand new Nexus 7 here, about 2 weeks old. I let it sit charging about a week with no use. Tried to start it, it wouldn't start. Held power and vol up to reboot it. Long story short, I have the exact same issue as the original poster. It will not unlock. I can get to the screen to unlock it. But when choosing unlock bootloader -> yes, it just hangs forever. I spent hours on this over the weekend with no success, various restore programs. At one point, it did manage to reboot to the Google startup screen with the unlocked padlock. Not sure if that means it's unlocked. But it then got stuck.
Also, I've seen all sorts of error messages referring to e:\ and missing folders.
Is this thing trashed?
So a couple nights ago everything was working just fine. Locked my Nexus 7 and went to sleep. The next morning I try to unlock it, but I just have a completely black screen. No backlight or anything. I force shut it off and try turning it back on. It gives me the TWRP loading screen and freezes there (I'm rooted with custom recovery but no custom rom). It does this twice, then booting gives me nothing. No Google logo, no boot animation, nothing. I boot into the bootloader and figure I'll re-flash my recovery and see if I can get to that. No commands will send via fastboot. I'm able to execute "fastboot reboot-bootloader", but nothing else works.
Now I'm familiar with switching USB ports and USB cables, but even after using two different cables (Nexus 7 2013 and Nexus 4) and about 6 different USB ports (both USB 3, and USB 2), nothing. I can't send a new recovery, new bootloader or anything.
So I figure I'll try re-locking the bootloader and then unlocking so it'll hopefully do a factory reset and might help. Well locking worked fine, however when I run "fastboot oem unlock" it brings me to the confirmation screen. I'm able to press the up volume button and press the power button to confirm, but after this it freezes and I have to do another force restart. I've reinstalled the USB drivers, reinstalled the Android SDK, and tried it on a different computer with no Android drivers at all. I've installed the offical Google USB drivers, used the Nexus Root Toolkit to install them, and used PDAnet to install drivers.
It's driving me crazy. It was literally working perfectly the night before, and the next morning it's like there's some catastrophic damage to the device.
Does anyone have any experience with this sort of extreme scenario?
Any help at all would be appreciated! Thank you!
Have you downloaded the factory Google image, then boot to the bootloader, and use fastboot commands to completely erase and reflash the stock image?
- Sent from my Galaxy S3
RMarkwald said:
Have you downloaded the factory Google image, then boot to the bootloader, and use fastboot commands to completely erase and reflash the stock image?
- Sent from my Galaxy S3
Click to expand...
Click to collapse
I was able to erase the boot image, recovery, user data, ect.. because I read to do that if you have intentions to reflash the factory images. However, this was still after my problem of not being able to unlock the bootloader. I think I may be able to flash the factory images if it weren't for the fact that every time I try to unlock the bootloader it freezes completely.
Did you let the tablet reboot after running "fastboot oem lock"?
---------- Post added at 02:46 PM ---------- Previous post was at 02:38 PM ----------
Did you flash the factory images after erasing them? After you run "fastboot oem lock", the device will reboot, but if you erased everything and didn't flash the images, nothing is there to boot to.
Download the Nexus 7 JSS15R OEM image.
Extract the compressed file to the folder where your fastboot.exe lives. Typically this is the platform-tools directory in the SDK.
Open a command prompt window where your fastboot.exe lives.
Type in the following commands and press enter after each one.
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader razor-jss15r/bootloader-flo-flo-03.14.img
fastboot reboot-bootloader
fastboot -w update razor-jss15r/image-razor-jss15r.zip
Wait for the image to flash. The tablet will automatically reboot, let it do so. Once done, rush through initial device setup, don't worry about Google credentials right now or anything. Once to the homescreen, reboot back into fastboot to run:
Code:
fastboot oem unlock
Then let the tablet reboot.
THESE INSTRUCTIONS ARE ASSUMING THIS IS THE WIFI VERSION ONLY. THEY'LL WORK FOR THE LTE, JUST REPLACE FOLDER AND FILE NAMES AS NEEDED.
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. =(
I have a Nexus 7 2013 which is apparently dead.
It boots to a google screen and hangs there. I can get to the bootloader menu OK but trying to launch recovery and it hangs again on the google screen.
I have tried a stock Nexus Rom, it looks OK but proceeds to ask for the bootloader to be unlocked, proceed to try and unlock, select yes and hit the power button and it hangs. The CMD window's last prompt shows it attempting to clear the userdata. I left this for about 8 hours . Have tried fastboot -w and got the same results.
using the nexus recovery tool and I can erase & format these partitions and sometimes they are successful, others they hang. Even when successful, going back to flash the rom and I get the same results.
any suggestions.
Hey
The same thing is happening to my tablet.
Please some help would be great