hi all,
I have Nexus S i9023 from Vodafone Australia.
my Nexus S stuck at boot animation after i updated my phone with ICS 4.0.4.
I will explain why this happened before i write the solution.
- Originally i rooted my phone and unlocked the bootloader a while back, then Vodafone released the ICS OTA update, which i installed, worked perfect, recently they release another update of Jelly Bean 4.1, which again i accepted, but, this time phone started, i touched the first key and phone responded in a reboot. after a reboot, i unlocked the screen, another reboot and a continuous loop of reboots.
-i thought this is happening bcoz of unlocked bootloader and superuser app sitting in the system. i followed up many forums to UNROOT, which i could not understand, finally i used "1 Click unroot for Nexus S 4G", obviously i knew that this is not for my nexus. but still i used it. it worked.
- later i updated with ICS OTA update, then Nexus S stuck at boot animation for one full day.
Now below are all actions i took to fix the problem.
- Installed PDANET drivers for this device
- Installed Java SE 32bit
- Installed SDK for Android which detects 32bit Java, and within SDK i installed android platform and google drivers.
- Copied and Replaced all files from "platform-tools" (folder within Android SDK installation) to "tools" folder.
- Downloaded "recovery-clockwork-5.0.2.0-crespo" and copied this file into "tools" folder (a folder within Android SDK installation)
- Downloaded this zip file - android.clients.google.com/packages/ota/google_crespo/1ada25375426.signed-soju-ota-189904.1ada2537.zip
- Connected my Nexus S in fastboot mode and ran the following commands in cmd
fastboot flash recovery recovery-clockwork-5.0.2.0-crespo
- then i went into clockwork recovery mod in my phone.
- i mounted my phone's USB SD card and copied the binary i downloaded as above.
- then i chose "install zip from SD card". Once installation finished. i ran the following command in cmd
fastboot oem lock
Now my phone is back to stock.
P.S. when my phone stuck at boot animation, i thought i bricked my phone. and spent a whole day searching for unbricking/resurrecting etc. But this symptom means NOT bricked yet.
below is the site for official binaries
sites.google.com/site/baroqueworksdevandroid/offcail-binary
I am a noob, so i thought this guide will help other noobs.
Thanks
I've seen something like that before, but different how it happen. I had stock NS4G with Gingerbread and had the ota update for ics come across so i did it. It did get stuck on the boot screen also and never would complete the boot. So i took it to an tech at sprint and they unlocked the phone and the did the update. Only to last a couple hours for another issues to come up with ICS. Whenever would click the home key on my phone it would keep opening up google earth, even after factory resets.
Why don't you guys just run custom roms? They run smoother than stock and the boot loop things are easy solvable.
Sent from my Nexus S using xda app-developers app
kwibis said:
Why don't you guys just run custom roms? They run smoother than stock and the boot loop things are easy solvable.
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
They might not want to run custom Roms. I don't but some people might prefer the"Stock" experience.
Bought a new Nexus 7 because my wife and I have them and love them. We had bought our daughter a cheap 'funtab' from walmart just so she could play a few games she loves and hopefully leave ours alone, the funtab was a complete POS so it was returned to WM and just bought her a N7 instead.
When booted, the tablet it immediately notified me of the update from 4.1.2 to 4.2.1. Each time it tried to update it would fail partially through, not sure why. So I thought I'd download and use the toolkit to force the update. After unlocking, rooting, installing busybox and so on. I choose the option to flash stock image. The update process started OK there but part way through gave an error, something about needing to be 'X' but is instead 'x' before going back to the home screen. Now the tablet is stuck in fastboot mode, and cant boot to either recovery or android. I think I may be in trouble here.... Any suggestions?
#1 reason why people shouldn't use tool kits to root. You have no idea what went wrong or where the problem occurred.
I'm assuming that your tablet is unlocked so you need to download a custom recovery and install it via fastboot.
Then download the Stock 4.2.1 ROM from the Android development section and flash it in the recovery.
This should give you an idea of how to do it.
http://www.androidcentral.com/how-unlock-bootloader-and-root-your-nexus-7
Sent from my Nexus 7
I've done more research and I'm currently working on getting the android sdk going. I've downloaded it, jdk, the proper factory image (i think I f'd up by accidentally downloading the factory image for the hspa model). My question now is can the factory image be flashed from what appears to be fastboot mode, or do i need to flash custom recovery first (via the sdk)? I can confirm that the bootloaded is unlocked.
Ok so I was able to flash the stock image using the instructions found at http://forum.xda-developers.com/showthread.php?t=1907796
This process went extremely well once I had all my ducks in a row. Thanks for the help.
Hello. 1 month ago i use Nexus 7 Toolkit for flash 4.2.1 stock firmware, because 4.2.2 don't wanna install without some default APK's.
So, I decided download at once 4.2.2, not 4.2.1, and i download it from developers.google.com and put archive in put_google_factory_image_here folder, run flash, and after flashing i get "Booting failed" message, i do not know what i must do, so i decided reboot nexus, power off and that's all. Nexus is a brick. Only crappy APX mode. I go to service center and today they fix it - change motherboard, lol.
And few mins ago i decided flash that 4.2.2 stock AGAIN, lol. Download from developers google com 4.2.2 archive, put it in special folder in nexus toolkit, and start flashing. AND AGAIN GOT "Booting failed" lol!
So, now i don't power off nexus, i put all files from firmware archive in fastboot folder, run flash-all.bat from stock firmware archive... and... ALL IS FINE!
If you download firmware from developers.google.com and when you flash it with nexus toolkit that's will brick your nexus. Why? I don't know. Flash-settings from google and from toolkit server are same. byte by byte.
That problem start only when 4.2.2 released. With flashing before 4.2.2 (when 4.2.1 will stable release) all will is fine.
Peka73Rus said:
Hello. 1 month ago i use Nexus 7 Toolkit for flash 4.2.1 stock firmware, because 4.2.2 don't wanna install without some default APK's.
So, I decided download at once 4.2.2, not 4.2.1, and i download it from developers.google.com and put archive in put_google_factory_image_here folder, run flash, and after flashing i get "Booting failed" message, i do not know what i must do, so i decided reboot nexus, power off and that's all. Nexus is a brick. Only crappy APX mode. I go to service center and today they fix it - change motherboard, lol.
And few mins ago i decided flash that 4.2.2 stock AGAIN, lol. Download from developers google com 4.2.2 archive, put it in special folder in nexus toolkit, and start flashing. AND AGAIN GOT "Booting failed" lol!
So, now i don't power off nexus, i put all files from firmware archive in fastboot folder, run flash-all.bat from stock firmware archive... and... ALL IS FINE!
If you download firmware from developers.google.com and when you flash it with nexus toolkit that's will brick your nexus. Why? I don't know. Flash-settings from google and from toolkit server are same. byte by byte.
That problem start only when 4.2.2 released. With flashing before 4.2.2 (when 4.2.1 will stable release) all will is fine.
Click to expand...
Click to collapse
Well.. I've never had any problems fastboot flashing 4.2.2 myself.
------
I would suggest you don't use toolkits...at all... period!
Learn FASTBOOT...
...and be extremely cautious when it comes to FLASHING the BOOTLOADER...
A corrupted BOOTLOADER flash will 'hardbrick' the device in a heartbeat - make sure you have a secure USB connection...
Test along these lines..
Code:
fastboot flash boot <a boot.img>
or
fastboot flash recovery <a recovery.img>
If these go across, the new BOOTLOADER probably will.
The worst that's going to happen (with these two) is a 'softbrick' - a headache at worst.
A headache you can get over...
Hardbrick is death - and nobody get's over that.
Rgrds,
Ged.
I know this. Thanks.
I flash 4.2.2 with fastboot. Because nexus 7 toolkit is buggy, when i upgrade android from 4.2.1 to 4.2.2 with toolkit i got brick. Just read my 1 post
I give link to this thread creator of toolkit, maybe he fix this bug. Maybe no, anyway, start from this day i will flash firmwares ONLY with fastboot.
Good decision, i never used this kind of tool for flashing something.
Its a very presumptuous statement to say the Toolkit will brick your device if you flash a stock image using it. The toolkit has been used many many thousands of time to flash stock images and I test it extensively on both my nexus 7 devices when there is a new image released. The toolkit also uses exactly the same routine as the batch file included with the image so I know there isn't any problem with the code but regardless of that I will look at it later and see if any extra safety protocols can be added to prevent mistakes.
It would have helped if you listed exactly what you did and if there were any errors displayed when the images were being flashed via the Toolkit.
Mark.
mskip said:
Its a very presumptuous statement to say the Toolkit will brick your device if you flash a stock image using it. The toolkit has been used many many thousands of time to flash stock images and I test it extensively on both my nexus 7 devices when there is a new image released. The toolkit also uses exactly the same routine as the batch file included with the image so I know there isn't any problem with the code but regardless of that I will look at it later and see if any extra safety protocols can be added to prevent mistakes.
It would have helped if you listed exactly what you did and if there were any errors displayed when the images were being flashed via the Toolkit.
Mark.
Click to expand...
Click to collapse
I can't give you list of "errors" etc, just because i don't wanna again "brick" my nexus :/
What i did:
1. I enter in toolkit
2. Choose version (4.2.1 or 4.2.2, don't matter, i got "brick" on both versions)
3. Choose "download and flash stock"
4. Download stock from toolkit, or from google developers site
5. Flash downloaded firmware
After this i got "Booting failed".
Then i flash stock 4.2.2 with FastBoot - and all is ok. But when i again try to flash stock 4.2.2 with toolkit - im again got Booting failed.
That's all.
Ofcourse i have last ver. of toolkit.
Current ToolKit [V4.3.7], Latest Available [V4.3.7]
Current Mods Section [V2.5.0], Latest Available [V2.5.0]
Click to expand...
Click to collapse
I'm getting this samething to happen to me except I can't even get manual fast boot to work either. Both are giving errors about no such device found or timeouts.
I used the toolkit to flash stock and all was fine for me... Weird.
Sent from my Nexus 7 using xda app-developers app
nexus 7 toolkit, works 100% on me and my sis tablet no errors at all..
walliester said:
nexus 7 toolkit, works 100% on me and my sis tablet no errors at all..
Click to expand...
Click to collapse
Hicksy994 said:
I used the toolkit to flash stock and all was fine for me... Weird.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Do you use toolkit for flashing stock 4.2.2?
Never, ever had a problem with Wug's toolkit, that thing is written brilliantly and it has saved my ass more times than I can care to count.
I was totally new to android development before I tried the nexus toolkit. Now I have a rooted n7 and prime, though I gotta say, rooting the prime took from me more time. I would suggest that you run the test-like driver check before attempting the one click magic.
Sent from my Nexus 7 using xda premium
The sequel of flashes you made is confusing for me but you should flash stock no matter the version 4.1 or 4.2 cuz you can get to latest by OTA updater.
Sent from my Nexus 7 using Tapatalk 2
In last update:
+Added MD5 hash checks before flashing for ALL stock images to avoid bad flashes
+Added selection to flash Radio images in the Flash Image section (gsm models)
Good, any1 can test?
No problem for me, I used last tookit to return stock rom 4.2.2 from cyanogenmod 10.0.1 with franco r65kernel.
I desired to return factory rom, because of low charging issue and fast battery drain.
Peka73Rus said:
Hello. 1 month ago i use Nexus 7 Toolkit for flash 4.2.1 stock firmware, because 4.2.2 don't wanna install without some default APK's.
So, I decided download at once 4.2.2, not 4.2.1, and i download it from developers.google.com and put archive in put_google_factory_image_here folder, run flash, and after flashing i get "Booting failed" message, i do not know what i must do, so i decided reboot nexus, power off and that's all. Nexus is a brick. Only crappy APX mode. I go to service center and today they fix it - change motherboard, lol.
And few mins ago i decided flash that 4.2.2 stock AGAIN, lol. Download from developers google com 4.2.2 archive, put it in special folder in nexus toolkit, and start flashing. AND AGAIN GOT "Booting failed" lol!
So, now i don't power off nexus, i put all files from firmware archive in fastboot folder, run flash-all.bat from stock firmware archive... and... ALL IS FINE!
If you download firmware from developers.google.com and when you flash it with nexus toolkit that's will brick your nexus. Why? I don't know. Flash-settings from google and from toolkit server are same. byte by byte.
That problem start only when 4.2.2 released. With flashing before 4.2.2 (when 4.2.1 will stable release) all will is fine.
Click to expand...
Click to collapse
Peka73Rus said:
Hello. 1 month ago i use Nexus 7 Toolkit for flash 4.2.1 stock firmware, because 4.2.2 don't wanna install without some default APK's.
So, I decided download at once 4.2.2, not 4.2.1, and i download it from developers.google.com and put archive in put_google_factory_image_here folder, run flash, and after flashing i get "Booting failed" message, i do not know what i must do, so i decided reboot nexus, power off and that's all. Nexus is a brick. Only crappy APX mode. I go to service center and today they fix it - change motherboard, lol.
And few mins ago i decided flash that 4.2.2 stock AGAIN, lol. Download from developers google com 4.2.2 archive, put it in special folder in nexus toolkit, and start flashing. AND AGAIN GOT "Booting failed" lol!
So, now i don't power off nexus, i put all files from firmware archive in fastboot folder, run flash-all.bat from stock firmware archive... and... ALL IS FINE!
If you download firmware from developers.google.com and when you flash it with nexus toolkit that's will brick your nexus. Why? I don't know. Flash-settings from google and from toolkit server are same. byte by byte.
That problem start only when 4.2.2 released. With flashing before 4.2.2 (when 4.2.1 will stable release) all will is fine.
Click to expand...
Click to collapse
I HAVE flashed stock using the toolkit multiple but no problem for me.....
More, I wanna tell you guys that battery so slow in charging issue is solved after flashed stockrom 4.2.2 from google server. B4 with Cm 10.1 and franco r65, I have to charge it more than 10 hours to full, but now only 5 and half hour with Stockrom 4.2.2 . Problem is relevant to custom rom and modded kernel as I think
hassam_tariq2003 said:
I HAVE flashed stock using the toolkit multiple but no problem for me.....
Click to expand...
Click to collapse
Nexus 7 Turn On Problem
mskip said:
Its a very presumptuous statement to say the Toolkit will brick your device if you flash a stock image using it. The toolkit has been used many many thousands of time to flash stock images and I test it extensively on both my nexus 7 devices when there is a new image released. The toolkit also uses exactly the same routine as the batch file included with the image so I know there isn't any problem with the code but regardless of that I will look at it later and see if any extra safety protocols can be added to prevent mistakes.
It would have helped if you listed exactly what you did and if there were any errors displayed when the images were being flashed via the Toolkit.
Mark.
Click to expand...
Click to collapse
Dear I am facing the same problem I tried to update it with Adnroid 4.3 official. First time it showed boot img failure. I again tried to flash it through Tool Kit and it gave me some error. I tried to restart bootloader and shut it down by pressing power button. After that nothing happens. Now when I connect it to my Computer it shows me unrecognized USB. Does this mean its not dead and there is any option to get it turn on?
It will be highly obliged if you could reply me with the solution. I am in Pakistan and we don't have any service center.
saqibyk said:
Dear I am facing the same problem I tried to update it with Adnroid 4.3 official. First time it showed boot img failure. I again tried to flash it through Tool Kit and it gave me some error. I tried to restart bootloader and shut it down by pressing power button. After that nothing happens. Now when I connect it to my Computer it shows me unrecognized USB. Does this mean its not dead and there is any option to get it turn on?
It will be highly obliged if you could reply me with the solution. I am in Pakistan and we don't have any service center.
Click to expand...
Click to collapse
I'm in the same boat exactly the same thing. i hope there is a fix for this.
ChrisHRocks said:
I'm in the same boat exactly the same thing. i hope there is a fix for this.
Click to expand...
Click to collapse
You should flash the stock bootloader, when connected, find this amongst the advanced utilities, and if the drivers are not working then use the driver diagnostic tool. You will not lose your apps doing this.
One other thing is that once your bootloader is returned to stock, you can use the Google Framework cache and data clearance mthod, described in other posts, to force the 4.3 Update. This really does work, and means that your apps and data remain intact.
There is nothing that I can find that pertains to problems with installing Kitkat factory image 4.4 on my nexus 4 so I will state my problem with the hope of some insight.
I have a Nexus 4 that I have decided to sell and as a precautionary measure had decided to flash a fresh copy of Android version 4.3 last week to ensure all files were deleted. I used Nexus root toolkit and all went smoothly.
As the phone has not yet sold, I decided that I would update the currently OS to the latest version 4.4 kitkat to make it more appealing to buyers so I went back to Nexus Root Toolkit and went through the standard procedure of selecting my device and OS, etc. The phone is unlocked. I had no backup and went ahead and told the software to write over version 4.3 with 4.4. I thought all was going well, but the install was too short and didn't work with a message telling my to try "Force Flash" mode. So I tried again using force flash mode and this time the install took longer and the phone rebooted multiple times, only this time the phone wouldn't fully boot. It only boot loops now.
-I can put the phone into fastboot mode.
-The computer can communicate with the phone via USB cable.
-All info such as product name, variant, HW version, etc. is showing in fastboot mode.
I am unable to use Nexus Root Toolkit to fix my phone with or without using Force Flash mode.
I can't mount the phone and the computer can not detect the ADB at all.
Can anyone please tell me what I can do to fix my phone? Are there any other alternatives to flashing a fully functioning version of 4.4 Kitkat?
I have been at this for hours and I can seem to get anywhere with it. Is the phone destroyed?
Any help would be greatly appreciated. Thank you in advance.
saber13 said:
There is nothing that I can find that pertains to problems with installing Kitkat factory image 4.4 on my nexus 4 so I will state my problem with the hope of some insight.
I have a Nexus 4 that I have decided to sell and as a precautionary measure had decided to flash a fresh copy of Android version 4.3 last week to ensure all files were deleted. I used Nexus root toolkit and all went smoothly.
As the phone has not yet sold, I decided that I would update the currently OS to the latest version 4.4 kitkat to make it more appealing to buyers so I went back to Nexus Root Toolkit and went through the standard procedure of selecting my device and OS, etc. The phone is unlocked. I had no backup and went ahead and told the software to write over version 4.3 with 4.4. I thought all was going well, but the install was too short and didn't work with a message telling my to try "Force Flash" mode. So I tried again using force flash mode and this time the install took longer and the phone rebooted multiple times, only this time the phone wouldn't fully boot. It only boot loops now.
-I can put the phone into fastboot mode.
-The computer can communicate with the phone via USB cable.
-All info such as product name, variant, HW version, etc. is showing in fastboot mode.
I am unable to use Nexus Root Toolkit to fix my phone with or without using Force Flash mode.
I can't mount the phone and the computer can not detect the ADB at all.
Can anyone please tell me what I can do to fix my phone? Are there any other alternatives to flashing a fully functioning version of 4.4 Kitkat?
I have been at this for hours and I can seem to get anywhere with it. Is the phone destroyed?
Any help would be greatly appreciated. Thank you in advance.
Click to expand...
Click to collapse
It would have saved you a lot of problems of you had of done it manually, without a toolkit
http://forum.xda-developers.com/showthread.php?t=2010312
Sent from my Nexus 4 using Tapatalk
Same problem !
saber13 said:
There is nothing that I can find that pertains to problems with installing Kitkat factory image 4.4 on my nexus 4 so I will state my problem with the hope of some insight.
I have a Nexus 4 that I have decided to sell and as a precautionary measure had decided to flash a fresh copy of Android version 4.3 last week to ensure all files were deleted. I used Nexus root toolkit and all went smoothly.
As the phone has not yet sold, I decided that I would update the currently OS to the latest version 4.4 kitkat to make it more appealing to buyers so I went back to Nexus Root Toolkit and went through the standard procedure of selecting my device and OS, etc. The phone is unlocked. I had no backup and went ahead and told the software to write over version 4.3 with 4.4. I thought all was going well, but the install was too short and didn't work with a message telling my to try "Force Flash" mode. So I tried again using force flash mode and this time the install took longer and the phone rebooted multiple times, only this time the phone wouldn't fully boot. It only boot loops now.
-I can put the phone into fastboot mode.
-The computer can communicate with the phone via USB cable.
-All info such as product name, variant, HW version, etc. is showing in fastboot mode.
I am unable to use Nexus Root Toolkit to fix my phone with or without using Force Flash mode.
I can't mount the phone and the computer can not detect the ADB at all.
Can anyone please tell me what I can do to fix my phone? Are there any other alternatives to flashing a fully functioning version of 4.4 Kitkat?
I have been at this for hours and I can seem to get anywhere with it. Is the phone destroyed?
Any help would be greatly appreciated. Thank you in advance.
Click to expand...
Click to collapse
I have the same problem ! I have tried everything as you mentioned above. Additionally using the ADB I installed everything using the flash-all.bat and everything went well, however my phone is still in bootloop. Have you find a solution ? Please share if you have ... Thank you so much for posting the issue !
---------- Post added at 01:19 PM ---------- Previous post was at 01:02 PM ----------
priyab said:
I have the same problem ! I have tried everything as you mentioned above. Additionally using the ADB I installed everything using the flash-all.bat and everything went well, however my phone is still in bootloop. Have you find a solution ? Please share if you have ... Thank you so much for posting the issue !
Click to expand...
Click to collapse
Hey the flash-all.bat worked !!!! .. I just waited for like 15 mins after the flash-all.bat was done and viola! its back
This is great find
Those who face this issue can go to safe mode and backup their data while on boot screen just keep pressing up and down volume button for some time phone will get into safe mode and can be backed up.
Yesterday I rebooted my Nexus 7 after it froze while transferring some files onto the NAND, and the OS failed to load. I went into recovery and attempted to reflash the ROM I've been using for a few months, only to have it fail. I tried to revert to stock with the Nexus Toolkit, which failed, so I attempted a fastboot flash bootloader bootloader-group 4.23.img as my first step toward getting it back to stock. I tried with the copy I had, and got "InvalidState", so I google'd and discovered there were two versions of the 4.23 bootloader. Trying with the one that everyone was reporting to work, I got "Unknown Error Code", followed by "BadParameter" and then "Invalid argument". I then "fastboot reboot-bootloader", to try again after a reboot as I was getting nowhere, only to get a black screen. In Device Manager, my tablet shows up as "Unknown USB Device (Device Descriptor Request Failed)".
Is there anything I can do to revive it? I'm up for breaking it open and replacing parts.
Bump
Up!
Bump
N140945296
Eckyx said:
Yesterday I rebooted my Nexus 7 after it froze while transferring some files onto the NAND, and the OS failed to load. I went into recovery and attempted to reflash the ROM I've been using for a few months, only to have it fail. I tried to revert to stock with the Nexus Toolkit, which failed, so I attempted a fastboot flash bootloader bootloader-group 4.23.img as my first step toward getting it back to stock. I tried with the copy I had, and got "InvalidState", so I google'd and discovered there were two versions of the 4.23 bootloader. Trying with the one that everyone was reporting to work, I got "Unknown Error Code", followed by "BadParameter" and then "Invalid argument". I then "fastboot reboot-bootloader", to try again after a reboot as I was getting nowhere, only to get a black screen. In Device Manager, my tablet shows up as "Unknown USB Device (Device Descriptor Request Failed)".
Is there anything I can do to revive it? I'm up for breaking it open and replacing parts.
Click to expand...
Click to collapse
Hello,
It sounds like your Nexus 7 may be hard bricked. If your Bootloader is no longer showing up you may need to send in your device to be repaired. At this time I do not know of a solution to the issue you are experiencing except to have it repaired. If you would like to proceed email me at [email protected]. Please place case number N140945296 in the subject line for reference.
[email protected] said:
Hello,
It sounds like your Nexus 7 may be hard bricked. If your Bootloader is no longer showing up you may need to send in your device to be repaired. At this time I do not know of a solution to the issue you are experiencing except to have it repaired. If you would like to proceed email me at [email protected]. Please place case number N140945296 in the subject line for reference.
Click to expand...
Click to collapse
Sent you an email about a week ago, hoping to hear back soon!
Eckyx said:
Sent you an email about a week ago, hoping to hear back soon!
Click to expand...
Click to collapse
Got any solution my N7 shows exact the same symptom..
//Mathias
Fastboot will help you get everything back. Don't have the steps but did it myself with my Nexus 10. Google the info like I did.
Sent from my Nexus 10 using XDA Free mobile app
striker59 said:
Fastboot will help you get everything back. Don't have the steps but did it myself with my Nexus 10. Google the info like I did.
Sent from my Nexus 10 using XDA Free mobile app
Click to expand...
Click to collapse
Striker there seems to be a case where the flash gets corrupt and gets write protected... Which seems to have happend to our nexus 7..
To bad ASUS havent released a APX tool to fix this.
/M