Hi all, first off, yes I have read quite a bit and I am completely stumped on this one.
A buddy from work dropped off his Nexus 4 and asked about the "bootloop" it is stuck in. Looking at it, this is not a boot loop as far as I can tell. He said he used the http://www.wugfresh.com/nrt/ to do a root, but it apparently went wrong (he said it reported successful completion).
What I have done thus far:
Download Google stock rom and flashed that following their instructions in the "flash-all.sh" file for Kit-Kat. Tried to go into recovery, but the recovery just gives the android with the red triangle above it and hangs. On boot the screen shows the "Google" logo with the unlocked symbol and then shows the kit-kat boot animation but just sits there and never finishes. I gave it about 30 minutes but no luck.
I can get into bootloader and then flash a recovery (CWM for Mako), which then allows me to get into CWM and either flash a custom ROM (tried latest PA beta) with the same hang on boot.
Tried to custom erase system, boot, recovery with the instructions below:
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
fastboot flash recovery recovery-clockwork-6.0.4.7-mako.img
boot to recovery
set up for sideload in CWM
adb sideload pa_mako-4.1-BETA2-20140310.zip
reboot
Same result, just hangs on reboot with animation for boot.
I tried flashing the radio and bootloader back to 4.3 and then flashing the stock rom for the Google ROM occam-jwr66y-factory-74b1deab.tgz which is where I am at now with it just sitting at animation if the X lighting up.
I just noticed that when I plug it in to my workstation it recognizes the device sort of and shows that it is mountable, but then just hangs and never loads the directory structure like normal.
Another thing to note, when I mount /system and /data in CWM and "adb shell" into the phone, the /sdcard/0 location shows empty, which as far as I know this should be populated with the usual sdcard user directories, maybe??
Any help would be appreciated. I noticed that if I hold both the volume up and volume down buttons it says it is in "Download" mode, didn't know that was a thing outside of Samsung devices.
Ouput from flashing with Google stock 4.4.2 ROM:
sudo ./flash-all.sh
[sudo] password for jscott:
sending 'bootloader' (2203 KB)...
OKAY [ 0.089s]
writing 'bootloader'...
OKAY [ 0.311s]
finished. total time: 0.401s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
sending 'radio' (45537 KB)...
OKAY [ 1.790s]
writing 'radio'...
OKAY [ 2.541s]
finished. total time: 4.332s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: MAKOZ30d
Baseband Version.....: M9615A-CEFWMAZM-2.0.1700.98
Serial Number........: 0221a297d9d67206
--------------------------------------------
checking product...
OKAY [ 0.002s]
checking version-bootloader...
OKAY [ 0.002s]
checking version-baseband...
OKAY [ 0.002s]
sending 'boot' (6340 KB)...
OKAY [ 0.253s]
writing 'boot'...
OKAY [ 0.356s]
sending 'recovery' (6888 KB)...
OKAY [ 0.287s]
writing 'recovery'...
OKAY [ 0.398s]
erasing 'system'...
OKAY [ 0.579s]
sending 'system' (713960 KB)...
OKAY [ 26.844s]
writing 'system'...
OKAY [ 40.883s]
rebooting...
finished. total time: 69.615s
Recovery was broken again.
Had to flash recovery again to get in but I can "adb shell" the phone no problems.
If more information is needed or someone has a sure fire way to fix this same problem please hit me up, but at this point I am at a loss.
Just found out that the phone may have died when the "wugfresh" script was running, but he said that it died afterwards, since I wasn't there I don't know for sure how this all played out.
Oops, I just posted the same problem a few minutes ago. In my defense to the moderators, your thread wasn't posted when I started writing mine.
Anyhow, have you tried flashing the 4.2.2 factory image? That is the only one I manage to boot, but my IMEI and network are gone...
MtG92 said:
Oops, I just posted the same problem a few minutes ago. In my defense to the moderators, your thread wasn't posted when I started writing mine.
Anyhow, have you tried flashing the 4.2.2 factory image? That is the only one I manage to boot, but my IMEI and network are gone...
Click to expand...
Click to collapse
Same thing on my side with the 4.2.2 ROM. Loads fine, but no IMEI or anything like that. Not sure what the deal is with it.
Allowed OTA update and now I get the android bot with the red triangle when trying to go into recovery, but it says "no command" under it. On boot the device just hangs at "starting apps." and doesn't move past that.
Sideloaded PA 3.99 mako for the phone and it just hangs on boot animation as it has done previously before successfully flashing the 4.2 factory image. Not sure what the deal is but a solution for this would be awesome as I am totally stumped.
I have been dealing with this for a few months, and what I have done to get it to work is let it sit for a few hours. Then give it a shot. About half the time my phone boots up. Once it's booted up everything works, but if I need to reboot for any reason your screwed for a few hours.
It started happening for me once the 4.4 update rolled out, and ever since it has been doing this. I asked on here a few time and got no responses.
Sent from my Nexus 4 using Tapatalk
NeCr0mStR said:
Same thing on my side with the 4.2.2 ROM. Loads fine, but no IMEI or anything like that. Not sure what the deal is with it.
Allowed OTA update and now I get the android bot with the red triangle when trying to go into recovery, but it says "no command" under it. On boot the device just hangs at "starting apps." and doesn't move past that.
Sideloaded PA 3.99 mako for the phone and it just hangs on boot animation as it has done previously before successfully flashing the 4.2 factory image. Not sure what the deal is but a solution for this would be awesome as I am totally stumped.
Click to expand...
Click to collapse
I met the same problem. My nexus 4 met this problem about 4 or 5 times. at first time, I tried restarting the phone and sometimes it might boot successfully, then everything works fine. Second time the reboot doesn't work any more, but flash stock with the newest factory ROM works fine(4.3 at that time), at this time I backup all my data. After I met this more, I found this problem arose only when the phone automatically shutting down because of the dead battery. Yesterday I met this problem again because of the dead battery, and at this time only reboot the phone with 4.2.0. I tried all other factory stocks from 4.2.0 to 4.4.2. Hope you can solve this early. And ask me any information you need.
NeCr0mStR said:
Hi all, first off, yes I have read quite a bit and I am completely stumped on this one.
A buddy from work dropped off his Nexus 4 and asked about the "bootloop" it is stuck in. Looking at it, this is not a boot loop as far as I can tell. He said he used the http://www.wugfresh.com/nrt/ to do a root, but it apparently went wrong (he said it reported successful completion).
What I have done thus far:
Download Google stock rom and flashed that following their instructions in the "flash-all.sh" file for Kit-Kat. Tried to go into recovery, but the recovery just gives the android with the red triangle above it and hangs. On boot the screen shows the "Google" logo with the unlocked symbol and then shows the kit-kat boot animation but just sits there and never finishes. I gave it about 30 minutes but no luck.
I can get into bootloader and then flash a recovery (CWM for Mako), which then allows me to get into CWM and either flash a custom ROM (tried latest PA beta) with the same hang on boot.
Tried to custom erase system, boot, recovery with the instructions below:
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
fastboot flash recovery recovery-clockwork-6.0.4.7-mako.img
boot to recovery
set up for sideload in CWM
adb sideload pa_mako-4.1-BETA2-20140310.zip
reboot
Same result, just hangs on reboot with animation for boot.
I tried flashing the radio and bootloader back to 4.3 and then flashing the stock rom for the Google ROM occam-jwr66y-factory-74b1deab.tgz which is where I am at now with it just sitting at animation if the X lighting up.
I just noticed that when I plug it in to my workstation it recognizes the device sort of and shows that it is mountable, but then just hangs and never loads the directory structure like normal.
Another thing to note, when I mount /system and /data in CWM and "adb shell" into the phone, the /sdcard/0 location shows empty, which as far as I know this should be populated with the usual sdcard user directories, maybe??
Any help would be appreciated. I noticed that if I hold both the volume up and volume down buttons it says it is in "Download" mode, didn't know that was a thing outside of Samsung devices.
Ouput from flashing with Google stock 4.4.2 ROM:
sudo ./flash-all.sh
[sudo] password for jscott:
sending 'bootloader' (2203 KB)...
OKAY [ 0.089s]
writing 'bootloader'...
OKAY [ 0.311s]
finished. total time: 0.401s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
sending 'radio' (45537 KB)...
OKAY [ 1.790s]
writing 'radio'...
OKAY [ 2.541s]
finished. total time: 4.332s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: MAKOZ30d
Baseband Version.....: M9615A-CEFWMAZM-2.0.1700.98
Serial Number........: 0221a297d9d67206
--------------------------------------------
checking product...
OKAY [ 0.002s]
checking version-bootloader...
OKAY [ 0.002s]
checking version-baseband...
OKAY [ 0.002s]
sending 'boot' (6340 KB)...
OKAY [ 0.253s]
writing 'boot'...
OKAY [ 0.356s]
sending 'recovery' (6888 KB)...
OKAY [ 0.287s]
writing 'recovery'...
OKAY [ 0.398s]
erasing 'system'...
OKAY [ 0.579s]
sending 'system' (713960 KB)...
OKAY [ 26.844s]
writing 'system'...
OKAY [ 40.883s]
rebooting...
finished. total time: 69.615s
Recovery was broken again.
Had to flash recovery again to get in but I can "adb shell" the phone no problems.
If more information is needed or someone has a sure fire way to fix this same problem please hit me up, but at this point I am at a loss.
Just found out that the phone may have died when the "wugfresh" script was running, but he said that it died afterwards, since I wasn't there I don't know for sure how this all played out.
Click to expand...
Click to collapse
You have to keep flashing the Stock ROM...that's what saved me
Sent from my Moto G
GameAware said:
You have to keep flashing the Stock ROM...that's what saved me
Sent from my Moto G
Click to expand...
Click to collapse
So you had the same problem and managed to solve it by flashing the stock rom multiple times? How many times did you have to do it, and have you had that problem since?
MtG92 said:
So you had the same problem and managed to solve it by flashing the stock rom multiple times? How many times did you have to do it, and have you had that problem since?
Click to expand...
Click to collapse
Yes I had the same problem and flashed the ROM the first time, but still nothing. I then flashed it again and it booted up as normal. No problems since.
Sent from my Moto G
Related
---------------------------------------------------------------------------
I HAVE CEASED UPDATING THIS THEAD.
The old information contained below will remain for posterity, but will no longer be updated. From this point forward, all updates to this information will be found at http://www.randomphantasmagoria.com/firmware/nexus-s
---------------------------------------------------------------------------
Below is a list of all available OTA and full ROM packages for the Nexus S, model M200.
THIS IS FOR M200 ONLY. IF YOU HAVE ANOTHER VARIANT, PLEASE FIND THE THREAD FOR YOUR VARIANT.
Typical disclaimer where I tell you that all of this stuff is at your own risk and I'm not responsible if you mess up your phone, yadda yadda.
These updates are 100% stock and are NOT rooted.
HOW TO FLASH
I'm not giving instructions on how to flash ZIP files. If you don't know how to do that, you probably shouldn't be looking for stuff in this thread. There are plenty of threads on how to flash zips through recovery. Do a little reading before proceeding.
The recovery-flashable full ROM packages will only flash if your phone has no ROM, any custom ROM, or a stock ROM that's older than the version you're trying to flash. For instance, the 2.3.4 full ROM package will flash over the stock 2.3.3 ROM, but not over the stock 2.3.6 ROM.
With fastboot images, you can flash any version over any other version.
WHAT HAPPENS IF I GET AN ERROR WHILE FLASHING?
If you get an error flashing a recovery-flashable full ROM package, it means that you are running a stock ROM that's newer than the version you're trying to flash. If you're trying to downgrade, then you must install ClockworkMod recovery, then wipe system, boot, data, cache, and Dalvik cache. You will then be able to flash the older version. Optionally, you can also flash fastboot images of a version older than the version you're trying to flash.
If you get an error flashing an incremental update, it means one of four things. Either you don't have an M200, you aren't running a stock ROM, you have changed something with your stock ROM (this includes build.prop changes, radio or bootloader changes as well), or you're running Android 4.X and trying to update manually. These incremental updates only work if you are running a completely, perfectly stock ROM exactly the way Google provides it, with the right radio and the right bootloader. There are no exceptions to this rule. Furthermore, Android 4.X ROMs can no longer be updated manually in stock recovery. See below.
A NOTE ABOUT ANDROID 4.X OTAs
Beginning with Ice Cream Sandwich, Google has made a change to stock recovery that prevents you from flashing future OTA updates manually. Instead you are now required to wait for the OTA notification on your phone and then tap "Reboot and Install."
If this pisses you off, you have the option of unlocking your bootloader, installing either a stock Gingerbread recovery or ClockworkMod recovery, and then flashing the OTA updates manually.
LATEST VERSION
The latest Android version available for M200 is Gingerbread version 2.3.6, build GRK39F.
BUILD REFERENCE
GRI54 - Android 2.3.3
GRJ22 - Android 2.3.4
GRK39F - Android 2.3.6
FULL ROMS
FASTBOOT IMAGES
If you're comfortable with fastboot, you can flash these images to return your phone back to raw stock.
Generally the best way to do this is to perform the following steps:
Put all six fastboot images in one folder, unlock your bootloader, perform the fastboot flashes, then lock the bootloader:
fastboot oem unlock
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
FLASHING FASTBOOT IMAGES WILL ERASE ALL OF YOUR PHONE'S DATA AND WILL RETURN YOU TO A FACTORY STOCK, UNROOTED STATE.
Android 2.3.6/GRK39F/KRKC1 Radio/KA3 Bootloader
Official factory fastboot images, must be flashed using fastboot on an unlocked bootloader. Contains recovery, radio, and bootloader.
THESE IMAGES MUST BE FLASHED USING BOOTLOADER VERSION I9020XXKA3
RECOVERY-FLASHABLE ROMS
Android 2.3.4/GRJ22/KRKC1 Radio/KA3 Bootloader
Official, signed, can flash with ClockworkMod or stock recovery. Contains recovery, radio and bootloader.
Still need ROMs for:
Android 2.3.3/GRI54/KRKB3 Radio/KA3 Bootloader
Android 2.3.6/GRK39F/KRKC1 Radio/KA3 Bootloader
INCREMENTAL UPDATES
The links provided here are to Google's official update package for each version. Sometimes Google provides a small incremental update package for upgrading between versions, other times they just provide full ROM packages for bigger version upgrades. For instance, Google pushed a small incremental update to upgrade from 2.3.4 to 2.3.6. If your phone was running 2.3.3, there is no 2.3.3 to 2.3.6 incremental update, so Google would push the 2.3.6 full ROM package.
Android 2.3.3 (Build GRI54/KRKB3 Radio/KA3 Bootloader)
2.3.3 -> 2.3.4
Android 2.3.4 (Build GRJ22/KRKC1 Radio/KA3 Bootloader)
2.3.4 -> 2.3.6
This does not mention ICS for the Korean Nexus S. Is that because it's not available or supported, yet? Are these only "official" ROMs?
I've been scanning these pages for an hour, and I cannot find a clear, simple answer to whether or not I can get ICS working on my Korean SHW-M200.
Frustrating.
Why doesn't XDA just offer upgrades as a service? Hell, I'll pay someone 10 bucks to just do it and get it over with, ffs.
abundantmind said:
This does not mention ICS for the Korean Nexus S. Is that because it's not available or supported, yet? Are these only "official" ROMs?
I've been scanning these pages for an hour, and I cannot find a clear, simple answer to whether or not I can get ICS working on my Korean SHW-M200.
Frustrating.
Why doesn't XDA just offer upgrades as a service? Hell, I'll pay someone 10 bucks to just do it and get it over with, ffs.
Click to expand...
Click to collapse
No. It isn't available yet.
Sent from my Xoom using Tapatalk
oldblue910 said:
No. It isn't available yet.
Click to expand...
Click to collapse
What I'm trying to find out is if there is an ics ROM that will work on my phone. If I have to wait for KT to issue an official version of ics OTA, then I'll be waiting for another year...possibly forever. Where's the fun in that?
Surely, somebody must be working on this.
abundantmind said:
What I'm trying to find out is if there is an ics ROM that will work on my phone. If I have to wait for KT to issue an official version of ics OTA, then I'll be waiting for another year...possibly forever. Where's the fun in that?
Surely, somebody must be working on this.
Click to expand...
Click to collapse
Dude, just use those ics roms in the Nexus S development section. Every rom and kernels work on M200 varient.
Sent from my Nexus S using Tapatalk
no they don't, E: signature verification fail everytime
edit: still on 2.3.4 can't get beyond it without having to flash cwm, which i dont want to do
rorio82 said:
no they don't, E: signature verification fail everytime
edit: still on 2.3.4 can't get beyond it without having to flash cwm, which i dont want to do
Click to expand...
Click to collapse
whats ur nexus s model?
I have updated the original post with some new notes and also added the 2.3.6/GRK39F fastboot images for M200.
Is is possible to flash another Stock ROM to get ICS?
Is there a tutorial for getting ICS to the M200? I just installed CyanogenMod 9 on my German Galaxy S and it was a piece of cake compared to the SHW-M200
I tried to follow this guide, but when I try to flash the herring.img (step 5), I just get an Android standing before a big warning sign.
Code:
$ ./fastboot flash recovery ~/Downloads/recovery-clockwork-herring.img
< waiting for device >
but unfortunately, you can use i9020/i9023 ICS package in M200 without any problems at all...
Well guys the Nexus S has been an amazing phone for me, but I have moved on to the Galaxy Nexus. I will still be keeping these stock images threads up to date for the remainder of the Nexus S' OTA life cycle. I know these threads have helped a lot of people so it's the least I can do to help a community of people who are so passionate about such a great device. Cheers!
Sent from my Xoom using Tapatalk
---------------------------------------------------------------------------
I HAVE CEASED UPDATING THIS THEAD.
The old information contained below will remain for posterity, but will no longer be updated. From this point forward, all updates to this information will be found at http://www.randomphantasmagoria.com/firmware/nexus-s
---------------------------------------------------------------------------
Your effort is really appreciated
oldblue910 said:
---------------------------------------------------------------------------
I HAVE CEASED UPDATING THIS THEAD.
The old information contained below will remain for posterity, but will no longer be updated. From this point forward, all updates to this information will be found at http://www.randomphantasmagoria.com/firmware/nexus-s
---------------------------------------------------------------------------
Click to expand...
Click to collapse
Thanks. The blogging at randomphantasmagoria is very useful.
I managed to locate all the official firmware for the Nexus S (M200). Cheers and enjoy your Galaxy Nexus
4.1.1 now dead
rorio82 said:
no they don't, E: signature verification fail everytime
edit: still on 2.3.4 can't get beyond it without having to flash cwm, which i dont want to do
Click to expand...
Click to collapse
I have update m200s with 4.1.1 sojuk-jro03e and now phone is dead. no sign of life.
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\ahmed soft>cd c:\
C:\>cd C:\android-sdk-windows\platform-tools
C:\android-sdk-windows\platform-tools>fastboot flash recovery touch-crespo.img
error: cannot load 'touch-crespo.img'
C:\android-sdk-windows\platform-tools>
C:\android-sdk-windows\platform-tools>fastboot flash recovery recovery-clockwork
-touch-5.8.0.2-crespo.img
< waiting for device >
sending 'recovery' (3464 KB)...
OKAY [ 0.438s]
writing 'recovery'...
OKAY [ 0.453s]
finished. total time: 0.891s
C:\android-sdk-windows\platform-tools>adb reboot bootloader
error: device not found
C:\android-sdk-windows\platform-tools>adb reboot bootloader
error: device not found
C:\android-sdk-windows\platform-tools>
C:\android-sdk-windows\platform-tools>fastboot flash bootloader bootloader-cresp
o-i9020xxlc2.img
sending 'bootloader' (1536 KB)...
OKAY [ 0.188s]
writing 'bootloader'...
OKAY [ 0.359s]
finished. total time: 0.547s
C:\android-sdk-windows\platform-tools>
C:\android-sdk-windows\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
C:\android-sdk-windows\platform-tools>
C:\android-sdk-windows\platform-tools>fastboot flash radio radio-crespo-m200krkc
1.img
sending 'radio' (12288 KB)...
OKAY [ 1.547s]
writing 'radio'...
OKAY [ 1.688s]
finished. total time: 3.234s
C:\android-sdk-windows\platform-tools>
C:\android-sdk-windows\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
C:\android-sdk-windows\platform-tools>fastboot -w update image-sojuk-jro03e.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: I9020XXLC2
Baseband Version.....: M200KRKC1
Serial Number........: 3435FC23CACE00EC
--------------------------------------------
checking product...
OKAY [ 0.016s]
checking version-bootloader...
OKAY [ 0.000s]
checking version-baseband...
OKAY [ 0.000s]
sending 'boot' (3964 KB)...
OKAY [ 0.500s]
writing 'boot'...
OKAY [ 0.500s]
sending 'recovery' (4308 KB)...
OKAY [ 0.547s]
writing 'recovery'...
OKAY [ 0.547s]
sending 'system' (294030 KB)...
OKAY [ 36.828s]
writing 'system'...
FAILED (remote: Write Fail)
finished. total time: 39.000s
C:\android-sdk-windows\platform-tools>adb reboot bootloader
At end says fail and now dead. on other version stop at startup. now need help.
Thanks
br, raja
raja16sep said:
I have update m200s with 4.1.1 sojuk-jro03e and now phone is dead. no sign of life.
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\ahmed soft>cd c:\
C:\>cd C:\android-sdk-windows\platform-tools
C:\android-sdk-windows\platform-tools>fastboot flash recovery touch-crespo.img
error: cannot load 'touch-crespo.img'
C:\android-sdk-windows\platform-tools>
C:\android-sdk-windows\platform-tools>fastboot flash recovery recovery-clockwork
-touch-5.8.0.2-crespo.img
< waiting for device >
sending 'recovery' (3464 KB)...
OKAY [ 0.438s]
writing 'recovery'...
OKAY [ 0.453s]
finished. total time: 0.891s
C:\android-sdk-windows\platform-tools>adb reboot bootloader
error: device not found
C:\android-sdk-windows\platform-tools>adb reboot bootloader
error: device not found
C:\android-sdk-windows\platform-tools>
C:\android-sdk-windows\platform-tools>fastboot flash bootloader bootloader-cresp
o-i9020xxlc2.img
sending 'bootloader' (1536 KB)...
OKAY [ 0.188s]
writing 'bootloader'...
OKAY [ 0.359s]
finished. total time: 0.547s
C:\android-sdk-windows\platform-tools>
C:\android-sdk-windows\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
C:\android-sdk-windows\platform-tools>
C:\android-sdk-windows\platform-tools>fastboot flash radio radio-crespo-m200krkc
1.img
sending 'radio' (12288 KB)...
OKAY [ 1.547s]
writing 'radio'...
OKAY [ 1.688s]
finished. total time: 3.234s
C:\android-sdk-windows\platform-tools>
C:\android-sdk-windows\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
C:\android-sdk-windows\platform-tools>fastboot -w update image-sojuk-jro03e.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: I9020XXLC2
Baseband Version.....: M200KRKC1
Serial Number........: 3435FC23CACE00EC
--------------------------------------------
checking product...
OKAY [ 0.016s]
checking version-bootloader...
OKAY [ 0.000s]
checking version-baseband...
OKAY [ 0.000s]
sending 'boot' (3964 KB)...
OKAY [ 0.500s]
writing 'boot'...
OKAY [ 0.500s]
sending 'recovery' (4308 KB)...
OKAY [ 0.547s]
writing 'recovery'...
OKAY [ 0.547s]
sending 'system' (294030 KB)...
OKAY [ 36.828s]
writing 'system'...
FAILED (remote: Write Fail)
finished. total time: 39.000s
C:\android-sdk-windows\platform-tools>adb reboot bootloader
At end says fail and now dead. on other version stop at startup. now need help.
Thanks
br, raja
Click to expand...
Click to collapse
Just unlock bootloader and execute ***.bat file.
Sent from my Nexus S using Tapatalk 2
But How Sir,
Articudos said:
Just unlock bootloader and execute ***.bat file.
Sent from my Nexus S using Tapatalk 2
Click to expand...
Click to collapse
Thanks for Answer but Phone has no sighn of life. its not powering on or not going in download mode,Nothing complete dead. Can not attach to computer. Even donot donot take Chargeing_________________ Which ***.bat file where it is?
Br, Raja
install drivers for your pnone first
open run and type
devmgmt.msc
you should see android adb interface or fastboot something,...
if u dont see them,.. please install drivers
raja16sep said:
Thanks for Answer but Phone has no sighn of life. its not powering on or not going in download mode,Nothing complete dead. Can not attach to computer. Even donot donot take Chargeing_________________ Which ***.bat file where it is?
Br, Raja
Click to expand...
Click to collapse
Maybe...As far as I remember, there is just one "bat" file. If you are running windows, just execute it.(4.1+)
(You have to run fastboot mode befor executing "bat" file)
Sent from my Nexus S using Tapatalk 2
Power Ic Problem.
Thanks for help. The phone was restarting before. After flash now there is problem in its Power Ic. Because its getting hot. Let repaired by Hardware then try other solutions.
thanks
Br, Raja
Can anyone pls upload M200 Sbl.bin.Thanks
Hi guys,
I need your help.
I rooted and unlocked my device using wug fresh toolkit 1.5.3.
After that I installed TWRP trough adb.
Next, I flashed Paranoid Android and everything was working fine.
By some stupid ideea that i had, because there was no space on my device
due to leftovers from the apps I had before, I tought I should go in TWRP and wipe everything,
than flash the Rom again.
I wiped cache, dalvik, restore factory settings and than I wiped sd card both internal and external.
Right now I cant flash the Rom again or restore a nandroid, because there is nothing on device.
Connecting to computer will not recognize it.
All I can do is, while conected to computer, use buttons and get into bootloader and from there on TWRP recovery.
Please help me with some instructions on how to make my Nexus 7 work again.
Thank you.
You can manually push ROM/Kernel/Gapps files to /sdcard using adb push from Android SDK.
I can't exactly recall if you can push the files from bootloader, or recovery, or both, but a push command would look like:
Code:
adb push FILE.zip /sdcard
adb push being the ADB command to push files from the computer to the device
FILE.zip being the name of the file you want to send to the device (for example, EOS-grouper-20120908-27.zip)
/sdcard being the place on the device you want the file to be placed in
In some cases, /sdcard may not work, but /data/media should work.
Another option is to restock using a factory image from Google and then start over with flashing CWM, and then copying over your ROM/Kernel/Gapps files.
adb push
espionage724 said:
You can manually push ROM/Kernel/Gapps files to /sdcard using adb push from Android SDK.
I can't exactly recall if you can push the files from bootloader, or recovery, or both, but a push command would look like:
Code:
adb push FILE.zip /sdcard
adb push being the ADB command to push files from the computer to the device
FILE.zip being the name of the file you want to send to the device (for example, EOS-grouper-20120908-27.zip)
/sdcard being the place on the device you want the file to be placed in
In some cases, /sdcard may not work, but /data/media should work.
Another option is to restock using a factory image from Google and then start over with flashing CWM, and then copying over your ROM/Kernel/Gapps files.
Click to expand...
Click to collapse
I cannot push as it says "device not found".
Ok, I had to restock and unroot. Now is working fine. I used also wug fresh toolkit.
Will have to root again and so on...
Thanks!
same as above
hey guys my nexus 2012 wifi running 4.3 rooted has TWERP and installed CM 10.1.3 for some dumb reason as the above mentioned i too wiped dalvik cache and sd via TWERP. Now im stuck on google logo with an unlock padlock logo I can still go to fastboot but cant open recovery when I open it I only get the green robot with red warning sign. Im desperate I used wugfresh toolkit 1.7.5 and use the FlashStock+Unroot everything is ok on the script exept for bootloader failed my device got 4.18 while it says the toolkit needs 4.2+ i dont remember anymore. now im still stuck on google logo with an unlock padlock logo. Hope you guys can help me its my daughter's tablet she'll be sad without it..:crying: well be very thankful for any help thank in advance.
heres the code
Flash Stock + Unroot...
------------------------------------------------------------------
erasing 'boot'...
OKAY [ 0.020s]
finished. total time: 0.023s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.039s]
finished. total time: 0.039s
erasing 'recovery'...
OKAY [ 0.020s]
finished. total time: 0.020s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.044s]
finished. total time: 0.045s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 0.977s]
finished. total time: 0.977s
sending 'bootloader' (2100 KB)...
OKAY [ 0.258s]
writing 'bootloader'...
OKAY [ 0.709s]
finished. total time: 0.968s
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.020s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 4.23
Baseband Version.....: N/A
Serial Number........: 015d257818580418
--------------------------------------------
checking product...
OKAY [ 0.030s]
checking version-bootloader...
OKAY [ 0.022s]
sending 'boot' (4896 KB)...
OKAY [ 0.584s]
writing 'boot'...
OKAY [ 0.179s]
sending 'recovery' (5432 KB)...
OKAY [ 0.653s]
writing 'recovery'...
OKAY [ 0.186s]
erasing 'system'...
OKAY [ 0.057s]
sending 'system' (529061 KB)...
FAILED (remote: (Nv3pBadReceiveLength))
finished. total time: 4.274s
Booting up your freshly flashed stock device...
------------------------------------------------------------------
Wait for your device to finish booting up...
- It may appear to be boot looping; just wait...
- It could take 5-10 minutes; please be patient...
When its finally booted back up, please remember
to re-enable USB debugging if you plan on using
the toolkit to perform other operations.
NOTE: If this process was too quick and your device
is still in bootloader mode, then flashing stock may
have failed or been incomplete. Simply check the
log above: if you notice it skipped steps because it
didn't meet certain requirements, like the bootloader
or baseband version, then consider enabling 'Force Flash'
mode in the toolkits options menu and trying the
'Flash Stock + Unroot' processs again. Cheers.
Press any key to exit...
Hi,
I just wanted to install a new ROM but I ended without any Bootloader and System.
What I did:
- Wiped everything
- Forgot to copy the .zip files - so thats the point where everything went wrong
- Tried to upload it via adb push - failed when I wanted to install the zip
- Startet the flash-all.sh to install the factory image - went wrong -> no system.ing etc found
So what can I do now?
Its a Nexus Wifi (2012).
Thanks!
hd21337 said:
Hi,
I just wanted to install a new ROM but I ended without any Bootloader and System.
What I did:
Wiped everything
forgot to copy the .zip files - so thats the point where everything went wrong
tried to upload it via adb push - failed when I wanted to install the zip
startet the flash-all.sh to install the factory image - went wrong -> no system.ing etc found
So what can I do now?
Its a Nexus Wifi (2012).
Thanks!
Click to expand...
Click to collapse
Hi, hd21337...
What happens when you (from a fully shut down state) press VOL-DOWN, hold.. whilst holding, press POWER-ON?
What do you see when you plug the Nexus 7 into the wall charger? Do you see the WHITE-ON-BLACK battery charging animation?
Have you tried pressing, and holding for 30 seconds, the POWER ON button? (Your tablet could just be stuck in APX mode).
Rgrds,
Ged.
hd21337 said:
Hi,
I just wanted to install a new ROM but I ended without any Bootloader and System.
What I did:
Wiped everything
forgot to copy the .zip files - so thats the point where everything went wrong
tried to upload it via adb push - failed when I wanted to install the zip
startet the flash-all.sh to install the factory image - went wrong -> no system.ing etc found
So what can I do now?
Its a Nexus Wifi (2012).
Thanks!
Click to expand...
Click to collapse
Blessed are the backup makers, for they hath made Nandroids.
Exasperations, 3:16
I didn't know you could wipe out the bootloader. You should still be able to push recovery from PC via adb - fastboot. Then if pc recognizes the device transfer the zips from the pc.
Other than that, just don't know atp.
Someone more knowledgeable than I will need to chime in.
Sent from my Hyperdriven Dev Edition Vzw SCH-I545 with KT kernel using Tapatalk 4
GedBlake said:
Hi, hd21337...
What happens when you (from a fully shut down state) press VOL-DOWN, hold.. whilst holding, press POWER-ON?
What do you see when you plug the Nexus 7 into the wall charger? Do you see the WHITE-ON-BLACK battery charging animation?
Have you tried pressing, and holding for 30 seconds, the POWER ON button? (Your tablet could just be stuck in APX mode).
Rgrds,
Ged.
Click to expand...
Click to collapse
VOL-DOWN + Power On = Bootload appears but when I click on "Recovery mode" I see the Google logo with a notification in the top (Booting failed) in red. The same notification appears when I click on "Start".
I see the charging animation and holding the power button for 30 second didnt help.
wtherrell said:
Blessed are the backup makers, for they hath made Nandroids.
Exasperations, 3:16
I didn't know you could wipe out the bootloader. You should still be able to push recovery from PC via adb - fastboot. Then if pc recognizes the device transfer the zips from the pc.
Other than that, just don't know atp.
Someone more knowledgeable than I will need to chime in.
Sent from my Hyperdriven Dev Edition Vzw SCH-I545 with KT kernel using Tapatalk 4
Click to expand...
Click to collapse
Nah I think that i corrupted/deleted it with the factory image script from google!
And when I enter the bootloader, I dont see my device via "adb devices" :>
Downloads/nakasi-jwr66y ยป sudo ./flash-all.sh
Password:
...
(bootloader) Bootloader is already unlocked
OKAY [ 0.020s]
finished. total time: 0.020s
erasing 'boot'...
OKAY [ 0.577s]
finished. total time: 0.577s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 1.026s]
finished. total time: 1.026s
erasing 'recovery'...
OKAY [ 0.852s]
finished. total time: 0.852s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.488s]
finished. total time: 0.488s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 6.493s]
finished. total time: 6.493s
sending 'bootloader' (2100 KB)...
OKAY [ 0.271s]
writing 'bootloader'...
FAILED (remote: (InvalidState))
finished. total time: 0.412s
rebooting into bootloader...
OKAY [ 0.019s]
finished. total time: 0.020s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 4.18
Baseband Version.....: N/A
Serial Number........: XXXXXXXXXXXXXXXX
--------------------------------------------
checking product...
OKAY [ 0.030s]
checking version-bootloader...
FAILED
Device version-bootloader is '4.18'.
Update requires '4.23'.
finished. total time: 0.139s
Click to expand...
Click to collapse
hd21337 said:
Nah I think that i corrupted/deleted it with the factory image script from google!
And when I enter the bootloader, I dont see my device via "adb devices" :>
Click to expand...
Click to collapse
Maybe not... the v4.23 bootloader from Jellybean 4.3 build JWR66Y is known to cause issues when fastboot flashing back to factory stock. For this reason, it is recommended you replace that version of the bootloader with the one from build JWR66V. It's still, ostensibly, the same bootloader, but seems to fastboot flash OK.
As build JWR66V is now no longer available on the Google Developers website, somebody has extracted and uploaded the old bootloader from build JWR66V here. (You might have to scroll down a little for the link).
Oh.... and ADB devices doesn't work when you're in the bootloader... it requires a fully booted Android OS to work.
The command I think you're looking for is fastboot devices
Rgrds,
Ged.
hd21337 said:
VOL-DOWN + Power On = Bootload appears but when I click on "Recovery mode" I see the Google logo with a notification in the top (Booting failed) in red. The same notification appears when I click on "Start".
Click to expand...
Click to collapse
You are in bootloader (fastboot ) mode so when you wiped everything except bootloader it is normal state. Now check if computer know your nexus (if not install driver ) and run from factory image flash-all.bat and wait for restart. That's all. Adb and fastboot are two different things...
jkkk88 said:
You are in bootloader (fastboot ) mode so when you wiped everything except bootloader it is normal state. Now check if computer know your nexus (if not install driver ) and run from factory image flash-all.bat and wait for restart. That's all. Adb and fastboot are two different things...
Click to expand...
Click to collapse
Erm... yeah... I think the OP has probably done this already.
It was his fastboot output...
writing bootloader...
FAILED (remote: (InvalidState))
finished. total time: 0.412s
rebooting into bootloader...
...that suggested to me, the known issue with the bootloader from build JWR66Y as detailed here (in red letters, at the very top of the first post in the thread), and discussed here... as being the likely cause of the problem.
So, to reiterate @hd21337... fastboot flash the bootloader from build JWR66V, instead of the one from build JWR66Y... and it just might get your Nexus 7 back up and running again.
Good luck.
Rgrds,
Ged.
GedBlake said:
Erm... yeah... I think the OP has probably done this already.
It was his fastboot output...
writing bootloader...
FAILED (remote: (InvalidState))
finished. total time: 0.412s
rebooting into bootloader...
...
So, to reiterate @hd21337... fastboot flash the bootloader from build JWR66V, instead of the one from build JWR66Y... and it just might get your Nexus 7 back up and running again.
Click to expand...
Click to collapse
My concern was that OP could not start (deleted ) recovery from bootloader menu. He should look into stickies. Nexus is still alive and should get new bootloader as you recommended from another build.
Hi guys (@GedBlake and @jkkk88),
sorry for the late answer.
I just tried to run the flash-all.sh with the other bootloader image... but its worse than before.
(bootloader) Bootloader is already unlocked
OKAY [ 0.020s]
finished. total time: 0.020s
erasing 'boot'...
OKAY [ 0.580s]
finished. total time: 0.580s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.769s]
finished. total time: 0.769s
erasing 'recovery'...
OKAY [ 0.854s]
finished. total time: 0.854s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.489s]
finished. total time: 0.489s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 6.494s]
finished. total time: 6.495s
sending 'bootloader' (2100 KB)...
OKAY [ 0.267s]
writing 'bootloader'...
OKAY [ 9.376s]
finished. total time: 9.643s
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.020s
< waiting for device >
Click to expand...
Click to collapse
So and at this point, he stuck for about 20 minutes - I aborted it because he didnt move on. And now the N7 is dead. No power charging icon and animation and I cant turn it on (30 seconds holding power button etc.).
So I think I just killed it
Any ideas if there is an another reset trick etc.?
Thanks!
Hi All,
I'm using Mac Terminal, have latest SDK, adb and fastboot installed. I have Nexus 7 (2012) Wifi - Nakasi
I followed the pinned post to upgrade my 4.3 (JWR66Y) to KitKat 4.4. I rebooted into fastboot and started ./flash-all.sh
Mid way through the process had stalled so I 'control C' out of the process.
$ ./flash-all.sh
...
(bootloader) Bootloader is already unlocked
OKAY [ 0.020s]
finished. total time: 0.020s
erasing 'boot'...
OKAY [ 0.993s]
finished. total time: 0.994s
erasing 'cache'...
OKAY [ 1.059s]
finished. total time: 1.059s
erasing 'recovery'...
OKAY [ 0.854s]
finished. total time: 0.855s
erasing 'system'...
OKAY [ 0.490s]
finished. total time: 0.490s
erasing 'userdata'...
OKAY [ 6.154s]
finished. total time: 6.154s
sending 'bootloader' (2100 KB)...
OKAY [ 0.302s]
writing 'bootloader'...
OKAY [ 9.666s]
finished. total time: 9.969s
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.020s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 4.23
Baseband Version.....: N/A
Serial Number........: 015d2d4226501005
--------------------------------------------
checking product...
OKAY [ 0.030s]
checking version-bootloader...
OKAY [ 0.024s]
sending 'boot' (4990 KB)...
OKAY [ 1.045s]
writing 'boot'...
OKAY [ 1.047s]
sending 'recovery' (5530 KB)...
OKAY [ 3.340s]
writing 'recovery'...
OKAY [ 1.381s]
sending 'system' (611878 KB)...
^C
Click to expand...
Click to collapse
I ran same process and it was hanging again at the same spot. I exited the same way. Now terminal cannot find device in adb devices. I can still boot into recovery mode.
$ ./adb devices
List of devices attached
Click to expand...
Click to collapse
$ ./flash-all.sh
< waiting for device >
Click to expand...
Click to collapse
I'm not sure what to do now!!! any help would be...helpful. Please.
You need to wait a but, because the system image us about 630MB, which may take round about two minutes to get transferred and flashed.
Sent from my Nexus 7 using xda app-developers app
AndDiSa said:
You need to wait a but, because the system image us about 630MB, which may take round about two minutes to get transferred and flashed.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I waited 20 minutes the first time and 15 minutes the second time.
I tried flashing using different method from fastboot (http://forum.xda-developers.com/showthread.php?t=2010312). Problems happen when flashing system.img (~600MB).
Has anyone else found out the checksums aren't working? I get an error "E:signature verification failed" when using "flash-all.sh" from recovery mode (different method i've tried)
Note: no problems updating my nexus 4
Just wanted to update you on a solution if anyone has a similar problem.
I erased the system image through fastboot.
./fastboot erase system
Click to expand...
Click to collapse
Flashed the system image for old stock 4.3
./fastboot flash system system.img
Click to expand...
Click to collapse
Ran the flash-all script
./flash-all.sh
Click to expand...
Click to collapse
System was updated and worked! I back-dated to android 4.3, then did a second flash-all script to update to the current version of android 4.4. I believe that the original factory image for 4.4 was not working. The factory image was updated a day later - this is the file i used.
Thanks to everyone in xda. The many posts I read - even not directly related to my problem - provided a solution.
I hope my next post isn't so noob
whitext said:
I waited 20 minutes the first time and 15 minutes the second time.
I tried flashing using different method from fastboot (http://forum.xda-developers.com/showthread.php?t=2010312). Problems happen when flashing system.img (~600MB).
Has anyone else found out the checksums aren't working? I get an error "E:signature verification failed" when using "flash-all.sh" from recovery mode (different method i've tried)
Note: no problems updating my nexus 4
Click to expand...
Click to collapse
Well,I got the similar problem the other day on my Nakasig when I was flashing factory images through Fastboot.
Not only did I try the "flash-all.bat" command, but I also manually inputted each command line one after another.
However, I still encountered the same issue and waited for more 30 minutes during the "sending system" process.
Even worse was that I unplugged my N7 and tried to boot it,which led me to be stuck with the Google logo.:crying:
After removing the battery and booting it into Fastboot again,this time I decided to use Wug's toolkit to flash it.:good:
And thankfully,it worked and I can grab the delicious Kitkat now.
BTW, my N7 still failed to pass Hashcheck while using Wug's automatic method, therefore I just downloaded the Factory images and used Wug's tool to navigate to the .tgz file and then flash it.It spent me around 2 minutes to complete the "sending system" process this time.
Hey guys/gals,
Need some help here. I've been rooting/loading custom roms for almost 7 or so years. I'm not a programmer but know my ways around software well enough..
My problem is my nexus 4 started to bootloop and couldn't ever get it to start up. I had been using one of the purity builds (was a stable kitkat build i think) for a few months. Then one day I started getting force close type errors for a specific app... can't remember which.. so decided to restart the phone just like i would when this usually happens.. after that it wouldn't start up...
I've tried using all available tips and drivers/software and can't get it to successfully restore it. Googled a lot and read many posts.. i keep getting errors... i took a picture of that error which happens..
This is the first time I've bricked a phone so hopefully someone has come across this with a fix or is it truly a bricked phone?
thanks
also.. tried another toolkit and this is the error I get..
"***************************************************************
One-Click Unroot to Stock 4.4 Kit Kat for LG Nexus 4!
Brought to you by AndroidRootz.com
***************************************************************
This script will: Unroot your Nexus 4 to Stock 4.4 & Lock your Bootloader
For more details go to AndroidRootz.com
***************************************************************
Warning! This will delete everything on your phone! BACKUP your phone!
First make sure your in FASTBOOT MODE!
Press enter to continue
sending 'bootloader' (2203 KB)...
OKAY [ 0.071s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 0.075s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
sending 'radio' (45537 KB)...
OKAY [ 1.436s]
writing 'radio'...
FAILED (remote: flash write failure)
finished. total time: 1.439s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: MAKOZ20i
Baseband Version.....: M9615A-CEFWMAZM-2.0.1700.98
Serial Number........: 0042c881549801cf
--------------------------------------------
checking product...
OKAY [ 0.002s]
checking version-bootloader...
FAILED
Device version-bootloader is 'MAKOZ20i'.
Update requires 'MAKOZ30d'."
I can't update the required bootloader as this toolkit suggests since I can't even access the system etc..
Also, I can get into recovery no problem... but can't mount USB storage or sdcard.. system and firmware seem to be able to be mounted.. but all together can't really do much..
thanks again for any help
Hi
I don't think it is you who bricked it. According to this thread, the phone dies on its own. I'm not sure if your problem is the same as theirs, but the symptoms surely look identical.
Out of all the 10+ cases in that thread, only 1 phone was fixed when the owner did a factory reset; others had to get a replacement.
I'm sorry for not providing an actual/helpful answer and being a bearer of bad news, but I just thought you should know what happened to similar devices. I hope you get it fixed.