Database Info

Bircked Help?

I have anexus 5 that is stuch on the google logo or is stuck in a boot lopp than it gets frozen and when plugegd in the battery logo turns on. I can go into recovery (twrp), but everything on my phone ghas been erased so theres nothing to flash. I tried to use a Nexus 5 toolkit to stock flash but it always comes up with an error. When i try something on twrp it says unable to mount....and give like 5-6 different thinbgs that it cant mount to. Everytime i try to flaash a new bootloader or something from that toolkit the phone turns off and goes into the battery logo. When i use twrp and try to do anything the phone just restarts into recovery. Is there any way i could push factory images to the phone or something else.
BTW, i dont know mucgh in terms of doing stuff with adb and terminal and all that so please be simplistic with the answers. Thanks in advance,.

http://forum.xda-developers.com/showthread.php?t=2513701
[TUTORIAL] How to flash a factory image | Return to stock | Unroot/SAVE your Nexus 5
Sent from my Nexus 5

CRIME INC. said:
http://forum.xda-developers.com/showthread.php?t=2513701
[TUTORIAL] How to flash a factory image | Return to stock | Unroot/SAVE your Nexus 5
Sent from my Nexus 5
Click to expand...
Click to collapse
So i did this and it failes when at the bootloader and alos at the end it says failure. What to do now?

Irfdiddy said:
So i did this and it failes when at the bootloader and alos at the end it says failure. What to do now?
Click to expand...
Click to collapse
Go to twrp and factory reset it and see if it works..
Write failure means that the eMMC might have died which can only be solved by replacing the mobo.
- Sent from an IceCold Hammerhead!

Irfdiddy said:
So i did this and it failes when at the bootloader and alos at the end it says failure. What to do now?
Click to expand...
Click to collapse
You're being too vague for us to help you. What commands did you enter at the terminal? Word for word what was the error message(s) you received? Did you try flashing the factory image using both the primary and backup bootloader?

BirchBarlow said:
You're being too vague for us to help you. What commands did you enter at the terminal? Word for word what was the error message(s) you received? Did you try flashing the factory image using both the primary and backup bootloader?
Click to expand...
Click to collapse
So i followed the guide in the link posted above. This:
fastboot flash bootloader C:/image-hammerhead-krt16m/bootloader.img
fastboot reboot-bootloader
fastboot flash radio C:/image-hammerhead-krt16m/radio.img
fastboot reboot-bootloader
fastboot flash system C:/image-hammerhead-krt16m/system.img
fastboot flash userdata C:/image-hammerhead-krt16m/userdata.img
(Note: this command will wipe your device (including /sdcard), EVEN if your bootloader is already unlocked.)
fastboot flash boot C:/image-hammerhead-krt16m/boot.img
fastboot flash recovery C:/image-hammerhead-krt16m/recovery.img
fastboot erase cache
Now, i can flash the boot.img, the system.img, the radio, but it hangs up on some of the other ones and it says "erasing..." than i have to stop it casue it doesnt work. Also, when i go into recovery it shows a spinning android logo.
Edit: Ive gotten all the way to "fastboot flash system system.img", but it gets stuck on my phone and says "erasing..."

Irfdiddy said:
So i followed the guide in the link posted above. This:
fastboot flash bootloader C:/image-hammerhead-krt16m/bootloader.img
fastboot reboot-bootloader
fastboot flash radio C:/image-hammerhead-krt16m/radio.img
fastboot reboot-bootloader
fastboot flash system C:/image-hammerhead-krt16m/system.img
fastboot flash userdata C:/image-hammerhead-krt16m/userdata.img
(Note: this command will wipe your device (including /sdcard), EVEN if your bootloader is already unlocked.)
fastboot flash boot C:/image-hammerhead-krt16m/boot.img
fastboot flash recovery C:/image-hammerhead-krt16m/recovery.img
fastboot erase cache
Now, i can flash the boot.img, the system.img, the radio, but it hangs up on some of the other ones and it says "erasing..." than i have to stop it casue it doesnt work. Also, when i go into recovery it shows a spinning android logo.
Edit: Ive gotten all the way to "fastboot flash system system.img", but it gets stuck on my phone and says "erasing..."
Click to expand...
Click to collapse
It will take some minutes to cOmplete the process computer will also hang type of feeling or stop responding for couple of minutes let the program finish its task,...

Irfdiddy said:
So i followed the guide in the link posted above. This:
fastboot flash bootloader C:/image-hammerhead-krt16m/bootloader.img
fastboot reboot-bootloader
fastboot flash radio C:/image-hammerhead-krt16m/radio.img
fastboot reboot-bootloader
fastboot flash system C:/image-hammerhead-krt16m/system.img
fastboot flash userdata C:/image-hammerhead-krt16m/userdata.img
(Note: this command will wipe your device (including /sdcard), EVEN if your bootloader is already unlocked.)
fastboot flash boot C:/image-hammerhead-krt16m/boot.img
fastboot flash recovery C:/image-hammerhead-krt16m/recovery.img
fastboot erase cache
Now, i can flash the boot.img, the system.img, the radio, but it hangs up on some of the other ones and it says "erasing..." than i have to stop it casue it doesnt work. Also, when i go into recovery it shows a spinning android logo.
Edit: Ive gotten all the way to "fastboot flash system system.img", but it gets stuck on my phone and says "erasing..."
Click to expand...
Click to collapse
You're not letting it finish. That's why you're having problems. It can take a long time. It also wouldn't hurt to use the flash-all.bat script instead of flashing each individually.

Nexus 5 Stuck On 'Formatting /Data' After Factory Image Flashing

Hi
I have Nexus 5 (Hammerhead) 16GB. After Marshmallow latest update my phone begun to restart randomly, So I tried to do factory reset. When I entered recovery mode It did not show android lying on its back with label "No command" , instead It showed standing android with some rotating cube (or gear) on its tummy. I tried to flash factory image in several ways, using nexus root toolkit and fastboot. I even tried different versions of android to flash but no result. My phone still shows Android with rotating gear on its tummy. Today I found this Thread and did everything that was told but no luck. :crying: If anyone could help I would be very grateful. Sorry for my bad English.

What is "everything that was told"? Did you erase everything then flash everything new? How long are you letting it sit with the rotating cube/gear thing?

exninja said:
What is "everything that was told"? Did you erase everything then flash everything new? How long are you letting it sit with the rotating cube/gear thing?
Click to expand...
Click to collapse
thank you for your reply.
I used this commands as it was described
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot flash bootloader "name of bootloader"
fastboot reboot-bootloader
fastboot flash radio "name of radio"
fastboot reboot-bootloader
astboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
every operation was successful.
I waited for this rotating gear more than 10 hours, nothing changed Still shows same
When I click power button + up volume key It says "Formatting /data"

Did you erase and reflash userdata img file?

audit13 said:
Did you erase and reflash userdata img file?
Click to expand...
Click to collapse
yes I did that, but still shows Android with rotating gears.
It does not matter whether I start my phone normally or boot a recovery mode It still shows this Android animation.

Does the phone's bootloader remain unlocked after rebooting?

Bootloop even after flashing stock firmware (XT1550)

I got an OTA update for marshmallow. At this stage phone was locked, unrooted and not tampered with.
After updating OTA phone went into a bootloop.
'Allow OEM Unlock' is disabled from developer options before even updating OTA so bootloader can't be unlocked.
After bootloop, from bootloader using fastboot (and mfastboot also tried) I flashed "XT1550_OSPREY_RETASIA_DS_2GB_6.0.1_MPI24.107........" this marshmallow firmware using standard commands for newer Moto devies. Even after flashing firmware, still bootloop happens.
Code:
fastboot flash bootloader O:\MotoG3\Firmwares\bootloader.img
fastboot flash logo O:\MotoG3\Firmwares\logo.bin
fastboot flash boot O:\MotoG3\Firmwares\boot.img
fastboot flash recovery O:\MotoG3\Firmwares\recovery.img
fastboot flash system O:\MotoG3\Firmwares\system.img_sparsechunk.0
fastboot flash system O:\MotoG3\Firmwares\system.img_sparsechunk.1
fastboot flash system O:\MotoG3\Firmwares\system.img_sparsechunk.2
fastboot flash system O:\MotoG3\Firmwares\system.img_sparsechunk.3
fastboot flash system O:\MotoG3\Firmwares\system.img_sparsechunk.4
fastboot flash system O:\MotoG3\Firmwares\system.img_sparsechunk.5
fastboot flash system O:\MotoG3\Firmwares\system.img_sparsechunk.6
fastboot flash system O:\MotoG3\Firmwares\system.img_sparsechunk.7
fastboot flash modem O:\MotoG3\Firmwares\NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg O:\MotoG3\Firmwares\fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
pause
At this stage, phone still goes into a bootloop. Clicking on recovery from bootloader also sends phone into a bootloop so can't even access stock recovery.
Also no way to erase system as bootloader is locked.
In bootloader some details are given:
baseband- M8916_2020617.29.03.21.45R OSPREY_APAC_CUST
product- osprey xt1550 16gb p2b
cpu- msm8916
device is locked. status code 0. software status official.
How do I get the phone back in working state?
Other bootloop guides were not useful as here even after flashing stock firmware phone still goes into a bootloop. ALso no stock recovery is accessible and BL is locked

Using the guide in http://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750, it is suposed to work (but you can't enter in stock recovery to do a factory reset, right?).
Try one more time, and confirme you flash all the system.img_sparechunk's files (some firmware images have less, and some have more).
In the first boot, the device can take a long period of time to boot (10-15 min in some cases).
If you can boot the recovery or the system, do a factory reset.

did you get it working?

Nexus 5 - completely erased - bootloader access existent

Hello everyone,
this is about the Nexus 5 16gb.
It has been completely erased and no backup has been done by the previous owner :silly: and he asked for help. I am a complete noob myself and could only do the below listed things thanks to this forum.
It was completely empty when I received it (as far as I can tell), but I can access the bootloader. I put a costum recovery on it with the help of this forum. When in costum recovery mode my computer identifies it as the Nexus 5 with the help of the Google Drivers and the SDK-Android (I presume) I installed previously.
I went to Google and was able to put a factory image on it from their collection of "hammerhead" for Nexus 5 (GSM/LTE).
I tried the 6.0.1 (MOB31E) and installed it via the flash-all.bat via CMD since this version was, according to the owner, installed before. It worked, as far as I could tell - data got copied on the phone.
When I restart the phone, the Google Logo with an opened lock blinks very slowly. The swirly loading screen I have seen on some Youtube videos for this model's OS does not appear. I presume that the phone does not recognize the flashed factory image?
My question is:
Do I need to try all of the factory images from Google until one works? Or is something so fundamentally lost (maybe somewhere in the booting process), that the phone cannot be repaired since the swirly loading screen does not appear?
Do I need to copy something else on the phone besides the factory image for it to start the booting process for the OS that I have installed via the flash-all.bat?
I am very lost - if someone could point me toward the right direction or even just toward the right kind of tutorial, I'd be very grateful.

You can flash the factory image using the following fastboot commands (subtitute file names to match the file names from the unzipped factory image):
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot reboot-bootloader
fastboot flash userdata userdata.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash cache cache.img

Bootloader Image File Flashing with an Unlocked Bootloader

I am in the process of returning my old Pixel 3a back to the factory images and locking the bootloader. It was running the latest 3a factory image with a magisk patched boot image, so it was easy to revert back by simply flashing the factory boot image. Locking the bootloader seems simple enough using the fastboot command, but I noticed when I downloaded the factory image ZIP that there is a flash-all.bat file and a bootloader image file. The bat file preforms the following:
fastboot flash bootloader bootloader-sargo-b4s4-0.4-8048689.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash radio radio-sargo-g670-00145-220106-b-8048689.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot -w update image-sargo-sp2a.220505.006.zip
Click to expand...
Click to collapse
Im curious what happens if a factory bootloader image is flashed with an unlocked bootloader? Does the flash replace the bootloader with one that is locked? Is this an alternative to running the fastboot command to lock the bootloader? I believe that in my current state, everything would be redundant except for the bootloader flash. Is that true?
This is the first time I have messed with locking the bootloader and am trying to not brick the device!
Thanks for the help!
-Ryan

radensb said:
I am in the process of returning my old Pixel 3a back to the factory images and locking the bootloader. It was running the latest 3a factory image with a magisk patched boot image, so it was easy to revert back by simply flashing the factory boot image. Locking the bootloader seems simple enough using the fastboot command, but I noticed when I downloaded the factory image ZIP that there is a flash-all.bat file and a bootloader image file. The bat file preforms the following:
Im curious what happens if a factory bootloader image is flashed with an unlocked bootloader? Does the flash replace the bootloader with one that is locked? Is this an alternative to running the fastboot command to lock the bootloader? I believe that in my current state, everything would be redundant except for the bootloader flash. Is that true?
This is the first time I have messed with locking the bootloader and am trying to not brick the device!
Thanks for the help!
-Ryan
Click to expand...
Click to collapse
No, it does not lock the bootloader.
Actually you need to unlock the bootloader before you flash the factory image using fastboot.
The instruction section has become a bit confusing with the newer changes and options but..
Factory Images for Nexus and Pixel Devices - [developers.google] - Flashing instructions
To explain the flash-all.bat file.
fastboot flash bootloader bootloader-sargo-b4s4-0.4-8048689.img
- Flashes the new bootloader image to the bootloader partition.​
fastboot reboot-bootloader
- Reboot to bootloader.​
ping -n 5 127.0.0.1 >nul
- One way to do a 5 second delay while waiting for the device to reboot into fastboot.​
fastboot flash radio radio-sargo-g670-00145-220106-b-8048689.img
- Flashes the new radio image (the mobile/phone parts) to the radio partition.​
fastboot reboot-bootloader
- Reboot to bootloader.​
ping -n 5 127.0.0.1 >nul
- One way to do a 5 second delay while waiting for the device to reboot into fastboot.​
fastboot -w update image-sargo-sp2a.220505.006.zip
- Runs the fastboot update command on the rest of the image file(s).
- The -w is the wipe command and will erase/format userdata (all your files) and cache.​
The only thing I would recommend after flashing the full factory update would be to switch slots and flashing the full factory update again.
That way both slots are set back to factory stock.
Then make sure you can boot into the stock system, if you can then you should be safe to lock the bootloader.
Cheers.
B.