After initially trying the Android Revolution HD rom after rooting few days ago, I realized I wanted to go back to stock. I downloaded "https://dl.google.com/dl/android/aosp/mysid-icl53f-factory-65895fa8.tgz" off of http://groups.google.com/group/android-building/msg/2cd2b16ed56a7e84 for my Verizon LTE GN variant...
I extracted "image-mysid-icl53f.zip" and flashed it the usually way with CWM, ended up going into a boot loop. Luckily I had a Nandroid backup of my phone just after rooting so I was able to use that to restore back to stock...
Was there any reason that "image-mysid-icl53f.zip" didn't work? I read another unrelated (if I remember correctly) post on here about flashing the image with a modified script from Google, do I need to use the flash-all.sh or something when flashing this zip? Do I need the other files (bootloader-toro..., radio-cdma..., and radio-toro...)? Or did I just get unlucky and a reflash probably would have fixed it?
Thanks
You don't flash the zip with cwm. You need to do fastboot -w update blah.,ip command with it.
Search for the "convert yawuwhatever to yawublah" thread for the directions
Sent from my Galaxy Nexus
s1977 said:
Resetting the phone by taking out the battery shouldn't be a problem if you havent started flashing the new rom. I would try again after confirming that the fastboot and usb drivers can see the device before proceeding any further.
You can use fastboot devices to list attached devices. Only progress further once you can see your phone using the above command.
I did the same today a few hours ago and in my case, I started the phone in bootloader mode via Volume up + down + power button or via adb reboot bootloader. Then with fastboot, issue the fastboot oem unlock command to unlock the bootloader first. Once done, then you can flash the stock image (bootloader, radio and rom) with the following commands.
fastboot flash bootloader <bootloader image>
fastboot reboot-bootloader
fastboot flash radio <radio image>
fastboot reboot-bootloader
fastboot -w update <rom image>
Don't forget to lock the bootloader once done using fastboot oem lock
Just to clarify, depending on the version of the OS on your client PC/Mac/Linux, there are variants of fastboot. I use fastboot-mac from my mac.
Click to expand...
Click to collapse
Also try checking out this thread: How to? Change from yakjuxw to yakju
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
I have a GSM Galaxy nexus that boots into fastboot and odin but when ever i flash stock or go into recovery it gets stuck on that dreaded google bootlogo . I have literaly tried everything and that google logo is not leaving !!
Try reverting everything back to stock using [GNex TOOLKIT V6.1]
http://forum.xda-developers.com/showthread.php?t=1392310
eliasgkphoto said:
Try reverting everything back to stock using [GNex TOOLKIT V6.1]
http://forum.xda-developers.com/showthread.php?t=1392310
Click to expand...
Click to collapse
I've already tries reverting back to stock and after its done it just immediately goes to the google screen and stays that way
You should try to flash the stock images manually in fastboot if you haven't done so already. I'm not a fan of Toolkits.
Download the stock files: https://developers.google.com/android/nexus/images#yakju
You must extract the .tgz file first and then extract the .tar file inside.
Navigate the folder until you see the radio bootloader and factory image.
Put those three files in the folder on your computer where you have fastboot.exe
Boot into the bootloader.
Type fastboot devices - to make sure your phone is connected.
Then these commands.
Code:
fastboot flash bootloader bootloader-maguro-primela03.img
fastboot reboot bootloader
fastboot flash radio radio-maguro-i9250xxla02.img
fastboot reboot bootloader
fastboot -w update image-yakju-imm76i.zip
Hopefully it will boot
Still nothing
El Daddy said:
You should try to flash the stock images manually in fastboot if you haven't done so already. I'm not a fan of Toolkits.
Download the stock files: https://developers.google.com/android/nexus/images#yakju
You must extract the .tgz file first and then extract the .tar file inside.
Navigate the folder until you see the radio bootloader and factory image.
Put those three files in the folder on your computer where you have fastboot.exe
Boot into the bootloader.
Type fastboot devices - to make sure your phone is connected.
Then these commands.
Code:
fastboot flash bootloader bootloader-maguro-primela03.img
fastboot reboot bootloader
fastboot flash radio radio-maguro-i9250xxla02.img
fastboot reboot bootloader
fastboot -w update image-yakju-imm76i.zip
Hopefully it will boot
Click to expand...
Click to collapse
I tried it and it didn't work. I also noticed that on the bottom of the gnex it says "fastboot command read error -2147483647" any ideas? I am officially clueless. I am offering 20 dollars to anyone who can fix this
i have found ABSOLUTELY NOTHING regarding this "FASTBOOT COMMAND READ ERROR -2147483647" that can actually fix it. everything from flashing stock via odin, uninstall and reinstall sdk, differnt usb cables, ubuntu 12.04 and win7. seems to no fix...please help. this started after flashing koush JB update via rom manager
Same thing for me but its stuck at the boot animation and it just started
Ok so from this thread : http://forum.xda-developers.com/zenfone2/help/how-to-upgrade-cn-version-to-ww-t3101556
I saw this : fastboot flash fastboot droidboot.img - droidboot.img is fastboot, and if you somehow will flash corrupted image, you won't be able to boot to fastboot anymore. Thanks to sorg
Is there ANY way to fix that ? Mine is broken and I CAN NOT : root/update recovery/enter bootloader
Basically i am STUCK on the firmware I have and CAN NOT do anything on this phone other than factory reset it but thats just about it.
Search for flash_image. I used it to flash recovery from running system. I suppose it can be used to flash fastboot too.
maciek90 said:
Search for flash_image. I used it to flash recovery from running system. I suppose it can be used to flash fastboot too.
Click to expand...
Click to collapse
The phone HAS RECOVERY does NOT HAVE BOOTLOADER
Read entire message. I wrote that this tool probably can be used to flash fastboot too.
You can also try "dd" command from busybox. Check sticky section in Zenfone General forum how to use it.
xRanker said:
Ok so from this thread : http://forum.xda-developers.com/zenfone2/help/how-to-upgrade-cn-version-to-ww-t3101556
I saw this : fastboot flash fastboot droidboot.img - droidboot.img is fastboot, and if you somehow will flash corrupted image, you won't be able to boot to fastboot anymore. Thanks to sorg
Is there ANY way to fix that ? Mine is broken and I CAN NOT : root/update recovery/enter bootloader
Basically i am STUCK on the firmware I have and CAN NOT do anything on this phone other than factory reset it but thats just about it.
Click to expand...
Click to collapse
You shouldn't mess with stuff you don't understand
If you have recovery, can you get to recovery menu?
Droid on back with error underneath and where you have to hold power then up volume to get to recovery menu.
Ok, here is link to flash_image tool.
http://forum.xda-developers.com/showthread.php?t=902493
I used it to flash recovery on HTC Sensation, but it should work with fastboot on Zenfone too. The command should be "flash_image fastboot /path/to/droidboot.img"
I'm not sure if it will work, but you already have messed up fastboot so this shouldn't make it worse
The second option is "dd if=/path/to/droidboot.img of=/dev/block/by-name/fastboot" or "dd if=/path/to/droidboot.img of=/dev/block/mmcblk0p3" as fastboot is the third partition. You can execute this even in terminal emulator on phone. Of course I haven't check it, but it's listed in general section to flash recovery (fastboot is just another partition, so it should work too).
About going to recovery maybe you can type " reboot recovery" in terminal emulator or from pc "adb reboot recovery". I'm not sure if it uses fastboot to boot into recovery but it's worth trying.
xRanker said:
Ok so from this thread : http://forum.xda-developers.com/zenfone2/help/how-to-upgrade-cn-version-to-ww-t3101556
I saw this : fastboot flash fastboot droidboot.img - droidboot.img is fastboot, and if you somehow will flash corrupted image, you won't be able to boot to fastboot anymore. Thanks to sorg
Is there ANY way to fix that ? Mine is broken and I CAN NOT : root/update recovery/enter bootloader
Basically i am STUCK on the firmware I have and CAN NOT do anything on this phone other than factory reset it but thats just about it.
Click to expand...
Click to collapse
Find Your Solution Here
Hi, I am i dire straits. I have a pixel xl running pure nexus, rooted and on tmobile. I am trying to get back to completely stock. i tried followig the instructions but somewhere I messed up. Currently phone will just bootloop. I went into cmd, typed adb devices, nothing came up so stupid me, I continued anyways with flash-all.bat, something went wrong in command prompt, then i proceeded to reboot from fastboot, this is where i am now. I have attached pictures of the command prompt screens and of the folder in adb fastboot on my pc that I think contained all the files. I do't know where I went wrong. If you can help, it would be greatly appreciated. I can only correspond via pc. Please, I hope someone can help me.
If someone has the time to walk me through step by step, it would much appreciated.
Doesnt looked bricked to me
maybe your factory image is incomplete.
Flash the parts individually see what happens.
Commands i use. note you need to use your own paths or copy mine
) Execute fastboot commands
fastboot flash bootloader c:\_PIXEL_XL_\bootloader.img
fastboot reboot-bootloader
fastboot flash radio c:\_PIXEL_XL_\radio.img
fastboot reboot-bootloader
fastboot flash boot_a c:\_PIXEL_XL_\boot.img
fastboot flash boot_b c:\_PIXEL_XL_\boot.img
fastboot flash system c:\_PIXEL_XL_\system.img
fastboot flash system_b c:\_PIXEL_XL_\system_other.img
fastboot flash vendor c:\_PIXEL_XL_\vendor.img
fastboot flash modem c:\_PIXEL_XL_\modem.img
fastboot reboot-bootloader
fastboot boot c:\_PIXEL_XL_\twrp.img
In TWRP, install twrp.zip
Reboot into the installed recovery
In TWRP, install supersu.zip <--- if you want to root.
5 Still in twrp flash verifiedboot signer.zip
6 Reboot
parakleet said:
Doesnt looked bricked to me
maybe your factory image is incomplete.
Flash the parts individually see what happens.
Commands i use. note you need to use your own paths or copy mine
) Execute fastboot commands
fastboot flash bootloader c:\_PIXEL_XL_\bootloader.img
fastboot reboot-bootloader
fastboot flash radio c:\_PIXEL_XL_\radio.img
fastboot reboot-bootloader
fastboot flash boot_a c:\_PIXEL_XL_\boot.img
fastboot flash boot_b c:\_PIXEL_XL_\boot.img
fastboot flash system c:\_PIXEL_XL_\system.img
fastboot flash system_b c:\_PIXEL_XL_\system_other.img
fastboot flash vendor c:\_PIXEL_XL_\vendor.img
fastboot flash modem c:\_PIXEL_XL_\modem.img
fastboot reboot-bootloader
fastboot boot c:\_PIXEL_XL_\twrp.img
In TWRP, install twrp.zip
Reboot into the installed recovery
In TWRP, install supersu.zip <--- if you want to root.
5 Still in twrp flash verifiedboot signer.zip
6 Reboot
Click to expand...
Click to collapse
No offence but i am lost by what you said, I am trying to get back to completely stock. Is part of my issue the fact that command prompt didn't detect my device? or no?
I'm not exactly sure what to do with the information you shared, sorry
I the tutorial i found it says to make sure the command prompt sees your device but doesnt say what to do when it doesnt see it.
Also, I downloaded the may factory image, i believe it was version O
Am I suppose to use the O image or the L image (verizon). I am on tmobile. I used the O image when i ran into trouble
jreink01 said:
Am I suppose to use the O image or the L image (verizon). I am on tmobile. I used the O image when i ran into trouble
Click to expand...
Click to collapse
If you did not get your phone from Verizon use this
7.1.2 (N2G47O, May 2017)
Download the zip
unpack all the zip files some are nested so unzipping one creates more keep unzipping until there are no more then gather the following img files
bootloader.img
radio.img
boot.img
system.img
system_other.img
vendor.img
modem.img
Some of those names are cut down as i hate typing long strings, jsut rename them as such.
Create a folder on root of c:\_PIXEL_XL_
put all the files there.
You will use way less files than you unpacked
once you have done that run the following commands
copy and paste
fastboot flash bootloader c:\_PIXEL_XL_\bootloader.img
fastboot reboot-bootloader
fastboot flash radio c:\_PIXEL_XL_\radio.img
fastboot reboot-bootloader
fastboot flash boot_a c:\_PIXEL_XL_\boot.img
fastboot flash boot_b c:\_PIXEL_XL_\boot.img
fastboot flash system c:\_PIXEL_XL_\system.img
fastboot flash system_b c:\_PIXEL_XL_\system_other.img
fastboot flash vendor c:\_PIXEL_XL_\vendor.img
fastboot flash modem c:\_PIXEL_XL_\modem.img
fastboot reboot
After last reboot just wait and you will be back at stock
if that doesnt work
Download latest version of TWRP place it in C:\_PIXEL_XL_
rename it twrp.img, again i hate typing long strings
from bootloader run
fastboot boot c:\_PIXEL_XL_\twrp.img
This will take you into twrp
you might need to wipe system and cache and data,
From memory the fourth entry at bottom is internal memory or user data, in any event if you do not check that your data stays on the phone.
Once you have wiped the other 3 rerun the fastboot commands and you will be back at stock
add the twrp and supersu commands from earlier to add root.
dont forget the signatureverify.img if you are doing that.
good luck.
you arent bricked
you just need to find the correct combination of steps to get your phone where you want it to be
Thanks for the response. I am having a hard time with this, the zip file i downloaded from the google website, when i open it, there are only 6 files, 1 of which is a zip file (marlin). When I open marlin it shows a bunch of files, none of which you mentioned. I am confused, was wondering if you would be nice enough to walk me through this over the phone, i would be really grateful.
Is there anyone that can walk me through this this on the phone, the more i try to understand this, the more cofused i get. pLeASE!!!!
jreink01 said:
Is there anyone that can walk me through this this on the phone, the more i try to understand this, the more cofused i get. pLeASE!!!!
Click to expand...
Click to collapse
Yes, i sent you a PM.
HALV0RS3N said:
Yes, i sent you a PM.
Click to expand...
Click to collapse
thanks, sent you my #
Okay so I had the exact problem yesterday. To to the Google developers site and download the official Google pixel or xl 7.1.2 nougut ota update. Once that's downloaded, go to your phone, I had all the exact same screens on my phone so it should work. Hold down the power button until it completely shuts down. Then hold the power and volume down to go to recovery mode, if it goes back to the ext 4 screen, try it again until it goes to recovery mode, then on command prompt type, fastboot boot twrp.img then once it's in twrp, go to advanced-then adb sideload and click both boxed and then swipe to enter sideload. Then on your computer, type adb sideload "file name for Google update" and hit enter. That should do the trick. Like I said, I had the exact same problem yesterday
---------- Post added at 06:56 PM ---------- Previous post was at 06:50 PM ----------
Also, I forgot to mention, download the twrp image file from the Internet. Shouldn't be hard to find just make sure it's the latest. Put that file in the adb file on your computer same with the Google update for your phone. Do not unzip either file. That's very important. DO NOT UNZIP THE UPDATE File. When you type in the twrp.img make sure you type img. And when you flash the update, make sure at the end of the file name you put
.zip ex( marlinpixelxl7.1.2.zip)
jreink01 said:
Hi, I am i dire straits. I have a pixel xl running pure nexus, rooted and on tmobile. I am trying to get back to completely stock. i tried followig the instructions but somewhere I messed up. Currently phone will just bootloop. I went into cmd, typed adb devices, nothing came up so stupid me, I continued anyways with flash-all.bat, something went wrong in command prompt, then i proceeded to reboot from fastboot, this is where i am now. I have attached pictures of the command prompt screens and of the folder in adb fastboot on my pc that I think contained all the files. I do't know where I went wrong. If you can help, it would be greatly appreciated. I can only correspond via pc. Please, I hope someone can help me.
If someone has the time to walk me through step by step, it would much appreciated.
Click to expand...
Click to collapse
Looking at your screen shot you didn't let the file finish flashing. It sticks at the "does not contain" for a bit before it continues.
You were doing it right. You just didn't wait.
If it wasn't going to work it would eventually give you a failure and jump to the command prompt.
jreink01 said:
Hi, I am i dire straits. I have a pixel xl running pure nexus, rooted and on tmobile. I am trying to get back to completely stock. i tried followig the instructions but somewhere I messed up. Currently phone will just bootloop. I went into cmd, typed adb devices, nothing came up so stupid me, I continued anyways with flash-all.bat, something went wrong in command prompt, then i proceeded to reboot from fastboot, this is where i am now. I have attached pictures of the command prompt screens and of the folder in adb fastboot on my pc that I think contained all the files. I do't know where I went wrong. If you can help, it would be greatly appreciated. I can only correspond via pc. Please, I hope someone can help me.
If someone has the time to walk me through step by step, it would much appreciated.
Click to expand...
Click to collapse
i had the same issue and this worked
https://forum.xda-developers.com/showpost.php?p=70972735&postcount=3
dont follow it word for word as that its not the XL version in the post.
RedBlueGreen said:
i had the same issue and this worked
https://forum.xda-developers.com/showpost.php?p=70972735&postcount=3
dont follow it word for word as that its not the XL version in the post.
Click to expand...
Click to collapse
OP was flashing to stock. Didn't let it finish though.