Develop Bugs

Galaxy Nexus Does Not Boot Into Android - (Recovery/Download Mode works -Please Help)

Hey Guys. I don't think the phone is bricked (I have access to Bootloader, CWM Recovery and Download Mode).
I was running Android Revolution HD ROM and out of the blue, the phone rebooted. But from this moment, it does not boot into Android. It just reboots, shows Google Logo, show the Nexus Boot Animation and then hangs for a second and reboots.
I figured it's a boot loop. So I wiped data/factory reset through CWM, wiped Dalvik Cache and flashed Revolution ROM again. Same result. I flashed Modaco iR5 and same result.
What do I do from here? Any help offered would be greatly appreciated. Thank you in advance.
RESOLVED! Thank you to afliopou, enumBoss and zyo (batch file to restore stock images - http://forum.xda-developers.com/showthread.php?t=1373995)

ragflan said:
Hey Guys. I don't think the phone is bricked (I have access to Bootloader, CWM Recovery and Download Mode).
I was running Android Revolution HD ROM and out of the blue, the phone rebooted. But from this moment, it does not boot into Android. It just reboots, shows Google Logo, show the Nexus Boot Animation and then hangs for a second and reboots.
I figured it's a boot loop. So I wiped data/factory reset through CWM, wiped Dalvik Cache and flashed Revolution ROM again. Same result. I flashed Modaco iR5 and same result.
What do I do from here? Any help offered would be greatly appreciated. Thank you in advance.
Click to expand...
Click to collapse
Maybe trying flash back to stock with fastboot following instructions here?
http://forum.xda-developers.com/showthread.php?t=1373995
Edit: and as enumBoss correctly asked which version is?LTE or GSM?

ragflan said:
Hey Guys. I don't think the phone is bricked (I have access to Bootloader, CWM Recovery and Download Mode).
I was running Android Revolution HD ROM and out of the blue, the phone rebooted. But from this moment, it does not boot into Android. It just reboots, shows Google Logo, show the Nexus Boot Animation and then hangs for a second and reboots.
I figured it's a boot loop. So I wiped data/factory reset through CWM, wiped Dalvik Cache and flashed Revolution ROM again. Same result. I flashed Modaco iR5 and same result.
What do I do from here? Any help offered would be greatly appreciated. Thank you in advance.
Click to expand...
Click to collapse
Is this an LTE or GSM device?
If it's GSM, I recommend flashing a different ROM. Probably something more stable. And do the whole thing - not just the rom, but the boot.img, etc. You can find that here: http://code.google.com/android/nexus/images.html

enumBoss said:
Is this an LTE or GSM device?
If it's GSM, I recommend flashing a different ROM. Probably something more stable. And do the whole thing - not just the rom, but the boot.img, etc. You can find that here: http://code.google.com/android/nexus/images.html
Click to expand...
Click to collapse
Hi. It's a GSM Version. I've tried flashing both Android Revolution HD and Modaco Ir5. Same Result. I can try VillainROM but I doubt that will help. (I'm doing that right now. I've just pushed VillainROM using this command: adb push VillainROM_whatever.zip to /data/media. Will try flashing that and report back).
I just tried restoring my nandroid backup and CWM restored the boot image, system and then it says 'Error While Restoring /data'.
Does that mean something is wrong with my internal storage?

ragflan said:
Hi. It's a GSM Version. I've tried flashing both Android Revolution HD and Modaco Ir5. Same Result. I can try VillainROM but I doubt that will help.
I just tried restoring my nandroid backup and CWM restored the boot image, system and then it says 'Error While Restoring /data'.
Does that mean something is wrong with my internal storage?
Click to expand...
Click to collapse
Maybe something wrong with your backup.Try to flash stock rom

afilopou said:
Maybe something wrong with your backup.Try to flash stock rom
Click to expand...
Click to collapse
I'll do that now. Oddly adb doesn't find the device when it's in bootloader mode. It finds it fine when it's in recovery mode and I'll able to push and pull stuff.
I think I'm missing fastboot drivers or something. I'll try flashing stock stuff.

I'm unable to push another ROM so I have to flash stock images. the internal storage is in read-only mode.

ragflan said:
I'll do that now. Oddly adb doesn't find the device when it's in bootloader mode. It finds it fine when it's in recovery mode and I'll able to push and pull stuff.
I think I'm missing fastboot drivers or something. I'll try flashing stock stuff.
Click to expand...
Click to collapse
This is normal.ADB not working when you are in fastboot.Did you try the thread i post you? When you are in fastboot you must first go through cmd in the folder that conatains fastboot.exe and then type in cmd "fastboot devices" .
eg cd C:/root (root is the folder that conatains fastboot)
then type "fastboot devices"

afilopou said:
This is normal.ADB not working when you are in fastboot.Did you try the thread i post you? When you are in fastboot you must first go through cmd in the folder that conatains fastboot.exe and then type in cmd "fastboot devices" .
eg cd C:/root (root is the folder that conatains fastboot)
then type "fastboot devices"
Click to expand...
Click to collapse
Yeap. I read the thread you posted. Downloaded the zip file and extracted it. After which I rebooted into bootloader mode and ran the batch file from the extracted directory.
It flashed the stock images in bootloader mode and rebooted twice and I'm booted into Android now. Thank you very much, kind sir.
For my reference (and to learn), what could have gone wrong? The ROM was up and running fine and I titanium restored only user apps and didn't touch system apps at all. Everything was fine and a random reboot caused the phone not to boot into Android anymore. I've had 3 other Android devices before the Nexus (Galaxy S, SII and G1) and never had such an issue.

ragflan said:
Yeap. I read the thread you posted. Downloaded the zip file and extracted it. After which I booted into bootloader mode and ran the batch file.
I'm booted into Android now. Thank you very much.
For my reference (and to learn), what could have gone wrong? The ROM was up and running fine and I titanium restored only user apps and didn't touch system apps at all. Everything was fine and a random reboot caused the phone not to boot into Android anymore.
Click to expand...
Click to collapse
Who knows? Only the android god

afilopou said:
Who knows? Only the android god
Click to expand...
Click to collapse
Haha amen to that. With Galaxy S and SII, I just used ODIN to flash a firmware. With Nexus, I just have to use that post. Thanks again!

Did you flash a new kernel? If so, that could be (part of) the issue

EddyOS said:
Did you flash a new kernel? If so, that could be (part of) the issue
Click to expand...
Click to collapse
Nope. Well, it was part of the ROM (Modaco and Android Revolution HD). I didn't flash it separately.

EddyOS said:
Did you flash a new kernel? If so, that could be (part of) the issue
Click to expand...
Click to collapse
I've just experienced the exact same thing..
And the ONLY thing I've done today was install NFC Taginfo.
I noticed apps starting to crap out and figured I'd done something wrong and restarted.. got stuck in a boot loop..
went into CWM to restore an old back up and it failed with 'Error while restoring /data' (I'd gotten 'Error while backing up /data' when trying to back it up).
wiped everything (twice).. formatted everything (twice).. tried to restore and still no go.. interesting that it didn't seem to have any issue when formatting /data.
Am only running rooted stock (not even any MODs) so find this all rather peculiar.
Will try and push the stock ROM this evening when I get home.
EDIT: Used the method listed above to flash the original stock image which worked... although it did erase everything on my phone (kinda wish I'd known that before but what can you do). Would really like to know how I went from a seemingly normal phone to a not very useful paperweight!? Thankfully it's resolved.

I'm having the same issue. However, I can't flash stock, as my baseband is different. Can someone please advise? Here is my fastboot flash attempt. Thanks.
C:\itl41f>flash-windows.bat
C:\itl41f>fastboot-windows flash bootloader bootloader-maguro-primekj10.img
sending 'bootloader' (2308 KB)... OKAY
writing 'bootloader'... OKAY
C:\itl41f>fastboot-windows reboot-bootloader
rebooting into bootloader... OKAY
C:\itl41f>fastboot-windows flash radio radio-maguro-i9250xxkk1.img
sending 'radio' (12288 KB)... FAILED (command write failed (Too many links))
C:\itl41f>fastboot-windows reboot-bootloader
rebooting into bootloader... FAILED (command write failed (No such file or direc
tory))
C:\itl41f>fastboot-windows -w update image-yakju-itl41f.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
< waiting for device >
--------------------------------------------
Bootloader Version...: PRIMEKJ10
Baseband Version.....: I9250UGKK7
Serial Number........: 0146914C0C019006
--------------------------------------------
checking product... OKAY
checking version-bootloader... OKAY
checking version-baseband... FAILED
Device version-baseband is 'I9250UGKK7'.
Update requires 'I9250XXKK1'.
C:\itl41f>
Click to expand...
Click to collapse

[Q] Flashed EU HOX with AT&T stuff and BRICKED! Please help

I'm desparate, please help me!
I flashed the remove-3-dot for the AT&T HOX, but I have another one. Now I cannot go back, since the device doesn't completely boot.
It is stuck with the HTC figures showing up and halfway the music stops and the device hangs.
I can go to recovery, but since the Àll-In-One Kit from Hasoon2000 doesn't see the device when in recovery (CWM 5.8.2.7 Touch), I cannot even put anything to the SD card, so I cannot even flash anything else!
Please help me before the battery dies out!! (I cannot turn it off since lonng press of the power button only restarts the booting)

If you have CWM did you made a nondroid backup?

Bright.Light said:
I'm desparate, please help me!
I flashed the remove-3-dot for the AT&T HOX, but I have another one. Now I cannot go back, since the device doesn't completely boot.
It is stuck with the HTC figures showing up and halfway the music stops and the device hangs.
I can go to recovery, but since the Àll-In-One Kit from Hasoon2000 doesn't see the device when in recovery (CWM 5.8.2.7 Touch), I cannot even put anything to the SD card, so I cannot even flash anything else!
Please help me before the battery dies out!! (I cannot turn it off since lonng press of the power button only restarts the booting)
Click to expand...
Click to collapse
THIS will help you

@muamers: Thanks!!
I already found out how to turn the device off, not draining the battery anymore.
I also flashed the new CWM 5.8.3.1 so it should have some ability to charge.
I am currently downloading the latest stock 1.29.401.11 and will try to flash that one.
I did search, but it's difficult currently. However, I made a permanent link to the Wiki - it's more than useful (the reason it exists, I know...)
Oh - it wasn't bricked (because it still did some stuff)
@jeyml: No, I did not do that (didn't know it was possible)
Does that mean that I could recover with the rom exactly as it was put on the device? (including installed ZIP files)

Bright.Light said:
@muamers: Thanks!!
I already found out how to turn the device off, not draining the battery anymore.
I also flashed the new CWM 5.8.3.1 so it should have some ability to charge.
I am currently downloading the latest stock 1.29.401.11 and will try to flash that one.
I did search, but it's difficult currently. However, I made a permanent link to the Wiki - it's more than useful (the reason it exists, I know...)
Oh - it wasn't bricked (because it still did some stuff)
@jeyml: No, I did not do that (didn't know it was possible)
Does that mean that I could recover with the rom exactly as it was put on the device? (including installed ZIP files)
Click to expand...
Click to collapse
Yup.It is actualy quite simple,i always do a backup before i flash something or update my ROM and other stuff.You keep the volume down + power button.After that you enter recovery mode (you will need to have CWM) and you have an option there "backup and restore",enter there and make a backup.Next time if you have any problems just enter again in the CWM,go to "backup and restore" and restore the backup you've made.It saves everything you have (i mean the ROM setting and such.Apps and other stuff must be backed up with Titanium Backup).
The backups you made are saved in the SD card in the nandroid directory if i remember corectly,so if you update you're ROM to...1.29 for example and have a 1.28 backup just enter there and delete it and make a new backup of the 1.29 so you don't get confused in so many backups and if you ever have problems and restore a 1.28 backup on you'r 1.29..well...you realize that the phone isn't going to work anymore.So,be carefoul.

Didn't work... I downloaded this rom: RUU_ENDEAVOR_U_ICS_40_HTC_Europe_1.29.401.11_Radio_1.1204.105.14_release_260491_signed
did everything this page told us: http://forum.xda-developers.com/showthread.php?t=1609190
But I do not see anything change... It's still stuck in the boot process.
I don't know what I am doing wrong...
I also didn't find a clear guide for how to do things - it's all pieces which everyone has to put together, making it hard when there is a real problem.
If this can be solved, I will investigate the nand backup for certain!
For now I need my phone, but it does not work...
Oh - how does the charging with the new clockwork work? I don't see anything happen, so I am afraid the battery will be down soon.
edit: It was on power all night and when I looked it had the screen on. Unplugging and replugging and the gren light went on. Does that mean the battery is filled?
One important fact: the adb command cannot find the device and I don't know why!

How did you flash the RUU? You have to connect the phone in FASTBOOT to the PC and then run it (with a locked bootloader) and it replaces the entire system

EddyOS said:
How did you flash the RUU? You have to connect the phone in FASTBOOT to the PC and then run it (with a locked bootloader) and it replaces the entire system
Click to expand...
Click to collapse
with a LOCKED bootloader?
Mine is unlocked...
I will try to relock the boorloader (saw somewhere a snippet)

Tried with a locked one:
Code:
D:\One_X_All-In-One_Kit_v1.0\Data>fastboot oem lock
... INFOLock successfully...
OKAY [ 0.143s]
finished. total time: 0.143s
D:\One_X_All-In-One_Kit_v1.0\Data>fastboot flash boot boot_signed.img
sending 'boot' (4288 KB)... OKAY [ 0.667s]
writing 'boot'... FAILED (remote: not allowed)
finished. total time: 0.874s
D:\One_X_All-In-One_Kit_v1.0\Data>fastboot flash system system.img
sending 'system' (963584 KB)... FAILED (remote: (00000008))
finished. total time: -0.000s
The bootloader loocks relocked ok (as it shows on top of that screen)
But flashing is impossible and, of cause, I don't know why

Adb will work in recovery but only if you boot the recovery from fastboot.
Fastboot boot recovery recovery.img

ok, next approach:
- Booted to fastboot
- unlocked bootloader with the unlock .bin file
- fastboot boot Recoveries\CWM5.8.3.1.img
- adb push rom.zip /sdcard/
- waited 5 minutes until done
- in recovery: Install zip from sdcard
- manual selected the rom.zip (yes, it was actually on the SDcard, so adb did its job)
- got an error that the image was bad:
ClockworkMod Recovery v5.8.3.1
-- Installing: /sdcard/rom.zip
Finding update package...
Opening update package...
E:Can't open /sdcard/rom.zip
I think I will have to get another image, right?
This one was extracted from
RUU_ENDEAVOR_U_ICS_40_HTC_Europe_1.29.401.11_Radio_1.1204.105.14_release_260491_signed.exe
I started the program and searched for the rom.zip in my temp folder. Was this ok?

Run .11 RUU, wait until load all completely, now go to %temp% in your pc and find a folder that contain a ROM.ZIP file... Unzip the files and flash the boot_signed.img and the recovery_signed.img, then relock your phone fastboot oem lock) do a factory reset (with the new recovery) and then try to run the .11 RUU.
THAT SHOULD WORK
pd: sorry for my poor english.
Sent from my HTC One X using XDA

Bright.Light said:
ok, next approach:
- Booted to fastboot
- unlocked bootloader with the unlock .bin file
- fastboot boot Recoveries\CWM5.8.3.1.img
- adb push rom.zip /sdcard/
- waited 5 minutes until done
- in recovery: Install zip from sdcard
- manual selected the rom.zip (yes, it was actually on the SDcard, so adb did its job)
- got an error that the image was bad:
ClockworkMod Recovery v5.8.3.1
-- Installing: /sdcard/rom.zip
Finding update package...
Opening update package...
E:Can't open /sdcard/rom.zip
I think I will have to get another image, right?
This one was extracted from
RUU_ENDEAVOR_U_ICS_40_HTC_Europe_1.29.401.11_Radio_1.1204.105.14_release_260491_signed.exe
I started the program and searched for the rom.zip in my temp folder. Was this ok?
Click to expand...
Click to collapse
You haven't a clue have you?
You don't flash an RUU from CWM, it's a Windows application!
1. Boot phone into FASTBOOT
2. Connect to the PC
3. Lock the bootloader
4. Run the RUU
Job done

@wolfraim: Yes, the factory reset was the one culprit, it seems!
EddyOS: Tried that so many times, but finally wolfraim added a crucial point: Factory reset!
Now the RUU install from the PC is working... (Have to wait for some time ...)
* I have to go for now, right after the flash is done.
When I've got the time, I will try to make some more notes and maybe another step-by-step story on how to make the device work again.
Thank you very much for your patience and help!
This is why I love the xda-developers site so much!
(and all possible ways included on XDA to brick my device is the reason why I hate xda sometimes... )
edit: Flashing has succeeded! Software number: 1.29.401.11, so it seems I also have the latest ROM update now.
I'll make a recovery backup asap and will try the titanium backup too.
Oh, this one is SU-locked of cause, so I will have to install the SU zip file again... Much work is to be done yet. Maybe I should look for a good ROM in the Android development area.

[Q] endeavoru cannot flash recovery

I previously managed to flash clockwork and sentinel. Now my recovery is corrupt and I cannot flash the recovery (or boot) .img..
I get the error 0X3000 remote fail when I try fastboot flash recovery recovery.img (the name of my ROM).
I cured this on the first install by fastboot erase cache. this now gives the error failed remote err )x 1900000
fastboot devices gives me the device name.
So my recovery is corrupt, and I want to flash a new recovery and then a new ROM.
Thanks
Fish
Managed to get recovery working but could not mount usb no drive E: error.
No backup either, even though i did one, files missing.
Tried to install zip, but lots of directories missing.

fishdude1 said:
I previously managed to flash clockwork and sentinel. Now my recovery is corrupt and I cannot flash the recovery (or boot) .img..
I get the error 0X3000 remote fail when I try fastboot flash recovery recovery.img (the name of my ROM).
I cured this on the first install by fastboot erase cache. this now gives the error failed remote err )x 1900000
fastboot devices gives me the device name.
So my recovery is corrupt, and I want to flash a new recovery and then a new ROM.
Thanks
Fish
Managed to get recovery working but could not mount usb no drive E: error.
No backup either, even though i did one, files missing.
Tried to install zip, but lots of directories missing.
Click to expand...
Click to collapse
Hi there, Which recovery u have u flashed? and with which recovery the backup u mentioned was taken?

SOLVED
keertikumar_ws said:
Hi there, Which recovery u have u flashed? and with which recovery the backup u mentioned was taken?
Click to expand...
Click to collapse
Recovery was clockworkMod (the version with chargimng and full USB).
I eventually rebooted my PC and could then erase cache, flash recovery again, mount USB from recovery and reflah boot, now alls well.
(Except no keyboard
So looks like the errors were PC related.

Ha..ha..okie...glad that its finally resolved

Thread #4
Sent from my HTC One X using XDA Premium 4 mobile app

C1905 - "Error mounting /data"

Hey folks,
I've just unlocked my bootloader and flashed the newest PhilZ Recovery. I've been following THIS tutorial.
Fastboot didn't encounter any issues, so I thought everything went fine. But after flashing the recovery image, my phone got stuck while booting. The Sony logo shows up, the screen turns black and that's where it gets stuck.
Trying to erase userdata, factory reset etc didn't help. While resetting it shows up the following message
Code:
"Error mounting/formatting /data"
So I tried to mount it manually in the recovery, but it shows the same error. Seems like a permission problem?!
Since I don't have a ROM on my SD-card yet I tried to install one via fastboot.
Code:
fastboot update ArchiDroid_V3.0.1.1-nicki.zip
But..
Code:
Archive does not contain 'android-info.txt'
Archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
Now I'm stuck. I don't think installing a new ROM will work if I can't even mount /data. So first thing is to fix this and then I'll be able to install a new ROM. Am I right?
By the way : fastboot has no problem detecting my device, but adb can't find it?! D:
I appreciate any kind of help! Thanks in advice!
Gruß aus Deutschland,
furi ;D

furiify said:
Hey folks,
I've just unlocked my bootloader and flashed the newest PhilZ Recovery. I've been following THIS tutorial.
Fastboot didn't encounter any issues, so I thought everything went fine. But after flashing the recovery image, my phone got stuck while booting. The Sony logo shows up, the screen turns black and that's where it gets stuck.
Trying to erase userdata, factory reset etc didn't help. While resetting it shows up the following message
Code:
"Error mounting/formatting /data"
So I tried to mount it manually in the recovery, but it shows the same error. Seems like a permission problem?!
Since I don't have a ROM on my SD-card yet I tried to install one via fastboot.
Code:
fastboot update ArchiDroid_V3.0.1.1-nicki.zip
But..
Code:
Archive does not contain 'android-info.txt'
Archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
Now I'm stuck. I don't think installing a new ROM will work if I can't even mount /data. So first thing is to fix this and then I'll be able to install a new ROM. Am I right?
By the way : fastboot has no problem detecting my device, but adb can't find it?! D:
I appreciate any kind of help! Thanks in advice!
Gruß aus Deutschland,
furi ;D
Click to expand...
Click to collapse
have you try to flash any rom except that? because when i try to flash archidroid i've same problem like you can't mount but when i try to install any rom like cm my device can mount normally.

Nicklas Van Dam said:
have you try to flash any rom except that? because when i try to flash archidroid i've same problem like you can't mount but when i try to install any rom like cm my device can mount normally.
Click to expand...
Click to collapse
I did. Tried 3 different ROMs and everyone gave me the same outcome.
But it seems like I fixed it by returning to stock using FlashTool and a stock ROM. I went all over again and now it's installing the ROM. I hope it's working now.
E: Yup, it's working fine now. But thanks anyway!

Question lineage recovery factory reset failed

Hi folks,
I got a problem while flashing lineage OS on my brand new OnePlus 9 Pro (LE2120). I was using the installation guide of DroidWin but instead of using MS Windows I used Ubuntu (according to the installation guide from lineage the PC-OS doesn't matter). Well, everything worked fine so far until Step 5: I flashed the lineage-18.1-20211005-recovery-lemonadep.img and once I did the lineage recovery told me I must apply a factory reset. Than my phone freezed on the first attached screen....
In order to solve this problem I switched to TWRP recovery. From the TWRP recovey I sideloaded the copy-partitions-20210323_1922.zip file . This works, at the end the error 'Unable to find partition for path "/cache" ' occurs. In TWRP I switched to the manu 'wipe > format data > factory reset' and the phone crashed. Now my phone is detected by fastboot, but I cant' reach the recovery. Flashing TWRP again ends up with
Code:
fastboot boot TWRP-3.5.2-lemonadep-Nebrassy.img
downloading 'boot.img'...
OKAY [ 6.379s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 6.382s
so I stay at the last attached screen on my phone and I do not get further. From this screen the recovery doesn't start. Thanks a lot in adavance !

Try fixing the phone with MSMDownloadTool and try it again. After you successfully got it, set up OxygenOS. After that, try installing Lineage again.

Thanks a lot Martinez74,
Red Prez16 said:
Try fixing the phone with MSMDownloadTool and try it again. After you successfully got it, set up OxygenOS. After that, try installing Lineage again.
Click to expand...
Click to collapse
Thanks a lot Red Prez16,
I did it the way you recommended and it works !

hshl1968 said:
Thanks a lot Martinez74,
Thanks a lot Red Prez16,
I did it the way you recommended and it works !
Click to expand...
Click to collapse
Well, I'm glad it worked out! Yeah, it's weird like that. Like you can flash TWRP, but touch won't work until you setup OxygenOS again.