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
Related
I have successfully rooted my Verizon Nexus version 4.04 build IMM76K and tried to flash two different ROM’s one is "Vicious-TORO-JellyBean-V3-signed" and the other is "Team Liquid Vicious-Toro V3-JellyBean Fully 100% Functional Deodex". On both it seemed to install fine, no error messages. Then at reboot it booted past the Google logo to the ROM logo and never passed it. I waited for a minimum of 20 minutes until I pulled the Battery and flashed back to stock. Please help.
Did flashing back to stock solve the problem, is your device ok?
Before you flash a custom ROM, always try wiping the cache and wiping the dalvich cache. You then wipe data and do a factory reset. After that you THEN install the ROM, that might've caused the problem. Maybe, I am not sure.
Which clockworkmod did you use to try flashing the ROMs, please give us more detail!
I actually did exactly as you said. Wiped, factory reset, wipe cache and then dalvich. Pushed the ROM to the phone and then installed it.I have been useing Gnex Toolkit v1.7
And did it work or what?
Wiping user data/Factory reset is important after installing the Custom ROM.
There is a good way to fix all this, make sure you backup EVERYTHING, and when I say EVERYTHING I mean EVERYTHING (Photos, Videos, EVERYTHING).
USE FASTBOOT, I have mentioned this heaps of times, I have because it just WORKS. I bricked my device before, and I just used fastboot. Understand 2 things if you're going to use it...
1. It DELETES EVERYTHING
2. You need to have your STOCK ROM in fastboot format
If you're willing to use fastboot and have the proper stock files here's how to do it (From Nexus S post: http://forum.xda-developers.com/showthread.php?t=1445635):
I QUOTE: "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
"
Cheers
Oh by the way I am not sure if the oem lock and unlock bit applies to you, check a relative guide to Galaxy Nexus please , this was an example
Long story short I bricked my phone when trying to flash recovery using toolkit. Now my phone won't turn on and recovery is gone as well. Somehow my PC can recognize the phone in fastboot mode although there's nothing showing on the screen.
So I tried the method in this thread:
http://forum.xda-developers.com/oneplus-one/help/wrong-kernel-black-screen-fastboot-adb-t2835696
It shows I flashed everything and it shows green color in the tool but when I checked the partitions, boot.img, recovery.img, userdata.img, system.img, etc are still broken. At that time the bootloader was still unlocked.
Since my computer can still see the phone in fastboot so I tried to flash the original image in fastboot. Again everything went through with no error but the phone still wouldn't turn on and the partitions are still same broken/corrupted. However the bootloader became locked after this. So now I end up with no more solutions. Since bootloader says locked(although boot.img is actually corrupted) I can't flash or do anything in fastboot command.
So I guess I'm really SOL right now... My only hope right now is maybe there will be USB JTAG or Nand flasher but I don't know if anyone can repair that right now.
Any suggestions?
fastboot oem unlock
fastboot erase system
fastboot erase boot
fastboot erase userdata
fastboot erase recovery
Now use twrp or cwm or whatever
fastboot boot recovery nameofrecovery.img
If your phone boots to recovery you may consider running e2fsck against data and cache partitions through adb shell
Best of luck
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?
Hi,
Device is: Asus Zenfone 2, Z008
At some point I managed to brick it. Restored it using xFstk and some fastboot magic.
Now, the big issue is, I cannot boot to recovery.
I can load bootloader (do fastboot commands), chose "Recovery", but it will just boot normal into the OS. Droid with hazard doesn't appear, just normal boot.
Tried (not all at once)
fastboot erase cache
fastboot format cache
installing twrp
flashing stock recovery.img
No joy.
What am I missing?
Video on Youtube with the issue: https://www.youtube.com/watch?v=ESnxjGDKwWA
Hi !
A quick answer has been provided here https://forum.xda-developers.com/showpost.php?p=71063211&postcount=598
Try this command after placing this recovery img into the adb folder and boot into bootloader
fastboot devices
enter
(check if it is recognised) then
fastboot boot recovery.img
( where recovery.img should be the exact name of your recovery you want to boot into)
Keep an eye on that thread you already have posted , more users may have replied
Good luck !
I've got a BIG problem with my new Pixel 5. I've successfully rooted it and had it operating for a day.
I then decided to boot into recovery mode just to see what the new stock recovery looks like (I used to use TWRP.).
BIG MISTAKE!
All I got was the error icon that I've seen in the past meaning that no recovery image is available. OK, so I try to just try to do a simple reboot. I'm taken back to the same place.
Now I try to reload Android. No luck! I'm stuck on:
"Device product is 'unknown'"
Update requires 'bramble'.
HELP!!!!
In the file android-info.txt, what would happen if I patched the line
require board=bramble
to
require board=unknown
Did you figure this out? I'm facing the same issue with my Pixel 5.
Edit: I figured it out. If you are having an issue with the 'flash-all.bat' command like we were, you just need to manually push the individual files and it should boot you back up into stock.
Run these commands:
1. fastboot flash bootloader <bootloader image file>
2. fastboot reboot-bootloader
3. fastboot flash radio <radio image file>.img
4. fastboot reboot-bootloader
5. fastboot update <image zip file>.zip
6. fastboot reboot
All of the reboot-bootloader commands may be redundant but it worked for me. It booted me into stock, verified I was unrooted with Root Checker, then proceeded to reboot back into the bootloader and 'fastboot flashing lock' to re-lock my bootloader and wipe the device.