Database Info

[Q] Stuck in boot loop after wiping SD card

All,
Long time lurker, first time poster. I've been doing a bunch of reading for the past few hours, I think my phone isn't completely f***, I'm just missing something simple.
So basically, I started with a stock HTC One XL with Telstra. Updated to the latest firmware version (3.17) and bootloader 2.14.
1. I unlocked the bootloader using htcdev. Installed CM10.1 smoothly, booted into the ROM and realised the touch screen didnt work (now I realise that's the new firmware problem).
2. Booted back into recovery (TWRP 2.4.1) and accidently wiped my SD card along with everything else (including backups).
3. Mounted SD card, and formatted it with FAT32. Put Viper 3.2.7 on it and installed it via recovery ---> Stuck in a boot loop. Phone boots to the Viper screen, does a bit of loading, and then re-boots. (I have also tried this with various other sense based ROMs, with the same problem).
4. After a bit of reading, I tried to manually load the boot.img file via fastboot. I get the following error message: FAILED: <remote: signature verify fail>.
So now I turn to you for help! After 3 years with Android, I have never had trouble flashing new ROMs following the instructions on this awesome site. I hope you guys can help me out on this one. All my phone content is backed up on my PC, so my only concern is getting a working ROM again.
So in summary, what I am able to do is:
- Boot to bootloader (which is unlocked)
- I DO NOT have s-off
- I can boot to TWRP recovery and mount my SD to copy any file across
I have not tried running RUU yet, leaving that as a last resort.

brad.cap said:
All,
Long time lurker, first time poster. I've been doing a bunch of reading for the past few hours, I think my phone isn't completely f***, I'm just missing something simple.
So basically, I started with a stock HTC One XL with Telstra. Updated to the latest firmware version (3.17) and bootloader 2.14.
1. I unlocked the bootloader using htcdev. Installed CM10.1 smoothly, booted into the ROM and realised the touch screen didnt work (now I realise that's the new firmware problem).
2. Booted back into recovery (TWRP 2.4.1) and accidently wiped my SD card along with everything else (including backups).
3. Mounted SD card, and formatted it with FAT32. Put Viper 3.2.7 on it and installed it via recovery ---> Stuck in a boot loop. Phone boots to the Viper screen, does a bit of loading, and then re-boots. (I have also tried this with various other sense based ROMs, with the same problem).
4. After a bit of reading, I tried to manually load the boot.img file via fastboot. I get the following error message: FAILED: <remote: signature verify fail>.
So now I turn to you for help! After 3 years with Android, I have never had trouble flashing new ROMs following the instructions on this awesome site. I hope you guys can help me out on this one. All my phone content is backed up on my PC, so my only concern is getting a working ROM again.
So in summary, what I am able to do is:
- Boot to bootloader (which is unlocked)
- I DO NOT have s-off
- I can boot to TWRP recovery and mount my SD to copy any file across
I have not tried running RUU yet, leaving that as a last resort.
Click to expand...
Click to collapse
FAILED: <remote: signature verify fail> means your bootloader is locked.

exad said:
FAILED: <remote: signature verify fail> means your bootloader is locked.
Click to expand...
Click to collapse
But it says **** UNLOCKED **** (as well as **** TAMPERED ****) at the top of the bootloader?

brad.cap said:
But it says **** UNLOCKED **** (as well as **** TAMPERED ****) at the top of the bootloader?
Click to expand...
Click to collapse
what is the command you used to load the boot.img and where did the boot.img come from?
on an unrelated note. flash twrp 2.3.3.1 instead every version above has issues wiping leading to issues not unlike yours.
after flashing 2.3.3.1 dont forget to do fastboot erase cache.

exad said:
FAILED: <remote: signature verify fail> means your bootloader is locked.
Click to expand...
Click to collapse
exad said:
what is the command you used to load the boot.img and where did the boot.img come from?
on an unrelated note. flash twrp 2.3.3.1 instead every version above has issues wiping leading to issues not unlike yours.
after flashing 2.3.3.1 dont forget to do fastboot erase cache.
Click to expand...
Click to collapse
I use "fastboot flash flash boot.img", the boot.img is extracted from the zip of the Viper ROM that is installed on my phone.
Will do! Will this help with the situation at hand? I'd rather keep as many factors static as possible. I'll flash twrp 2.3.3.1 once everything is resolved (unless it can help now?)

brad.cap said:
I use "fastboot flash flash boot.img", the boot.img is extracted from the zip of the Viper ROM that is installed on my phone.
Will do! Will this help with the situation at hand? I'd rather keep as many factors static as possible. I'll flash twrp 2.3.3.1 once everything is resolved (unless it can help now?)
Click to expand...
Click to collapse
Flash it now then try flashing again after wiping everything on 2.3.3.1
Sent from my HTC One X using xda app-developers app

brad.cap said:
I use "fastboot flash flash boot.img", the boot.img is extracted from the zip of the Viper ROM that is installed on my phone.
Will do! Will this help with the situation at hand? I'd rather keep as many factors static as possible. I'll flash twrp 2.3.3.1 once everything is resolved (unless it can help now?)
Click to expand...
Click to collapse
the command is fastboot flash boot boot.img btw.
but yes flash 2.3.3.1 first then fastboot erase cache then the boot img.
if you experience bugs that are not discussed in the ROMs op do a fresh wipe everything and reflash the rom because wiping with 2.4 probably wasn[t a clean wipe.

exad said:
the command is fastboot flash boot boot.img btw.
but yes flash 2.3.3.1 first then fastboot erase cache then the boot img.
if you experience bugs that are not discussed in the ROMs op do a fresh wipe everything and reflash the rom because wiping with 2.4 probably wasn[t a clean wipe.
Click to expand...
Click to collapse
Thanks. Will try that now.
Edit: Yep. That worked. Viper booted up fine and everything is working!
I'm going to make a back-up of this working ROM now, and have another go at getting CM10.1 to work.
Thanks for your help guys, really appreciate it. Especially exad.

[Q] AT&T HTC One X Unable to get past hboot/fastboot

Hi - first time posting, but I've benefited from many a XDA thread in the past. I'm hopeful that someone can help me.
I tried to put CyanogenMod on my AT&T HTC One X, and was able to unlock the bootloader and put a new boot/recovery image on it. After that, I got into a boot loop and haven't been able to get into recovery since. I've tried flashing new boot.img, new recovery (CyanogenMod and TWRP) and even though I can pause the boot loop to get to the bootloader, it won't let me into recovery.
HBOOT is 2.14, and I can get fastboot connectivity from my computer.
Any ideas/help?

Try flashing TWRP recovery again via fastboot, then I've that's finished flashing give this command:
fastboot erase cache
Then:
fastboot reboot-bootloader
Now try to enter recovery.
Sent from my Evita

timmaaa said:
Try flashing TWRP recovery again via fastboot, then I've that's finished flashing give this command:
fastboot erase cache
Then:
fastboot reboot-bootloader
Now try to enter recovery.
Sent from my Evita
Click to expand...
Click to collapse
Just tried that, and no dice. Just keeps on rebooting. If I select the RECOVERY option, it just reboots again - never enters recovery.

You might need to RUU, are you s-off?
Also, where are you downloading TWRP from?
Sent from my Evita

timmaaa said:
You might need to RUU, are you s-off?
Sent from my Evita
Click to expand...
Click to collapse
No, not s-off. I tried that, but I can't get it to boot into Android (after I flash the RUU zip and try to boot, it shows "FAILED (status read failed (Too many links))".

jwallaceks said:
No, not s-off. I tried that, but I can't get it to boot into Android (after I flash the RUU zip and try to boot, it shows "FAILED (status read failed (Too many links))".
Click to expand...
Click to collapse
An RUU isn't a zip, it's an exe program. If you don't have s-off you shouldn't do it anyway.
Sent from my Evita

timmaaa said:
An RUU isn't a zip, it's an exe program. If you don't have s-off you shouldn't do it anyway.
Click to expand...
Click to collapse
Yes, if you are s-on and try to run the 3.18 RUU, you will brick. You can't run an older RUU, due to your hboot version (2.14) and s-on.

timmaaa said:
Also, where are you downloading TWRP from?
Sent from my Evita
Click to expand...
Click to collapse
So, I downloaded a fresh version of TWRP per the Evita guide on CyanogenMod, and was able to get into recovery. Thanks for the tip!
Problem is, now I'm unable to flash a ROM because I can't mount /sdcard. I've tried other recoveries, but none of them will mount it, either. Tips?

jwallaceks said:
So, I downloaded a fresh version of TWRP per the Evita guide on CyanogenMod, and was able to get into recovery. Thanks for the tip!
Problem is, now I'm unable to flash a ROM because I can't mount /sdcard. I've tried other recoveries, but none of them will mount it, either. Tips?
Click to expand...
Click to collapse
Did you do a factory reset from bootloader? If so, you've corrupted it and it'll need to be formatted. Go into TWRP recovery, connect to pc, select mount, then mount usb storage. Now you'll need to format it in Windows to fat32 format.
Sent from my Evita

timmaaa said:
Did you do a factory reset from bootloader? If so, you've corrupted it and it'll need to be formatted. Go into TWRP recovery, connect to pc, select mount, then mount usb storage. Now you'll need to format it in Windows to fat32 format.
Sent from my Evita
Click to expand...
Click to collapse
That did it! I'm up and running, now! Thanks for all your help!

Cool, no worries. Just remember never to do a factory reset from bootloader, only do that in recovery.
Sent from my Evita

Stuck in boot loop been working on it all day, please help

I have att one x evita. too long to explain everything i have tried but here is where i am
****UNLOCKED****
S-OFF
HBOOT 2.14
I currently have CLOCKWORK RECOVERY going on, I have wiped, installed from SD the CM10.2 nightly i want to install, installs with no errors, installed gapps again no errors.
unit bootloops on HTC screen, I tried again same thing only this time fastboot flashed the boot.img file, tried before and after the rom install.
Tried all the same steps from most current version TWRP.....Im lost, what should i try next.
Also i have no file structure if you mount the storage from recovery i was empty and said it need to be formatted to be used, put it in FAT32. Made it usable, copied the CM ROM directly to the root of mounted drive, since there were no folders or anything in it.
Would love some help please.....im pulling my hair out

ntilley52 said:
I have att one x evita. too long to explain everything i have tried but here is where i am
****UNLOCKED****
S-OFF
HBOOT 2.14
I currently have CLOCKWORK RECOVERY going on, I have wiped, installed from SD the CM10.2 nightly i want to install, installs with no errors, installed gapps again no errors.
unit bootloops on HTC screen, I tried again same thing only this time fastboot flashed the boot.img file, tried before and after the rom install.
Tried all the same steps from most current version TWRP.....Im lost, what should i try next.
Also i have no file structure if you mount the storage from recovery i was empty and said it need to be formatted to be used, put it in FAT32. Made it usable, copied the CM ROM directly to the root of mounted drive, since there were no folders or anything in it.
Would love some help please.....im pulling my hair out
Click to expand...
Click to collapse
Have you tried RUUing back to stock and re-rooting?

Mount usb storage in TWRP recovery and format (fat32) the sd in Windows. It looks as though you've done a factory reset in bootloader at some point which corrupts the sd card. Once you've done that I'd suggest trying to flash another ROM, if you still have problems you'll probably need to RUU as Rolltribe suggested.
Sent from my Evita

I tried mounting SD card and formating, using twrp and cwm. To try the RUU is that something that is done through fastboot USB?
timmaaa said:
Mount usb storage in TWRP recovery and format (fat32) the sd in Windows. It looks as though you've done a factory reset in bootloader at some point which corrupts the sd card. Once you've done that I'd suggest trying to flash another ROM, if you still have problems you'll probably need to RUU as Rolltribe suggested.
Sent from my Evita
Click to expand...
Click to collapse

And the format didn't work? An RUU is an exe program that's run through Windows while the phone is connected, usually in fastboot mode.
Sent from my Evita

timmaaa said:
And the format didn't work? An RUU is an exe program that's run through Windows while the phone is connected, usually in fastboot mode.
Sent from my Evita
Click to expand...
Click to collapse
no it didnt work i am trying downloading the RUU right now.
RUU_Evita_UL_ATT_US_1.44.502.1_Radio_0.15.3201.09_release_249105.exe
this ^ is the file i am downloading does it loot correct for an ATT HTC ONE X(Evita)

That is an at&t RUU but it's a very old one. Personally I'd use the latest which is the 3.18 RUU.
Sent from my Evita

timmaaa said:
That is an at&t RUU but it's a very old one. Personally I'd use the latest which is the *****
Sent from my Evita
Click to expand...
Click to collapse
Having about the same issue on my phone. I have TWRP 2.5 on there. Tried to re-install viperxl and it goes through the install OK and then just boot loops.
Tried to use the RUU listed above and it fails with an error code of "Error 159 image error"
The RUU is going from Image version 2.20.502.7 to image ver 3.18.502.6
I had a different error with another RUU image I downloaded from HTC but didn't take notes on error.
Any idea's?

TWRP 2.5 is your problem, it's full of bugs. Download TWRP 2.6 from here. Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Now you can enter recovery on your phone and flash again and you should be fine.
Sent from my Evita

timmaaa said:
TWRP 2.5 is your problem, it's full of bugs. Download TWRP 2.6 from *** Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Now you can enter recovery on your phone and flash again and you should be fine.
Sent from my Evita
Click to expand...
Click to collapse
Trying now. Thanks for the super fast reply. MUCH Appreciated.

HomeWorx said:
Trying now. Thanks for the super fast reply. MUCH Appreciated.
Click to expand...
Click to collapse
u can also try using twrp one click tool v2.6.0.0 per timmaaa suggestion on my signature link below.....
Swyped from BlueICESense_JBE

HomeWorx said:
Having about the same issue on my phone. I have TWRP 2.5 on there. Tried to re-install viperxl and it goes through the install OK and then just boot loops.
Tried to use the RUU listed above and it fails with an error code of "Error 159 image error"
The RUU is going from Image version 2.20.502.7 to image ver 3.18.502.6
I had a different error with another RUU image I downloaded from HTC but didn't take notes on error.
Any idea's?
Click to expand...
Click to collapse
RUU got me back up to stock, thanks for that, now trying to reinstall CM10

[Q] Help - Rooting gone wrong

So I got the HTC One s and try to root it with the following instruction: http://forum.xda-developers.com/showthread.php?t=1583427&__utma=248941774.997411949.1390324490.1394471756.1396118873.6&__utmb=248941774.2.10.1396118873&__utmc=248941774&__utmx=-&__utmz=248941774.1394471756.5.2.utmcsr=feedburner|utmccn=Feed:%20xda-developers/ShsH%20(xda-developers)|utmcmd=feed&__utmv=-&__utmk=25799614
As I thought that Step 3 was only there to install the Superuser.apk i just skipped it (mistake no. 1) and wiped the whole thing (without making a backup --> mistake no. 2) and tried to install the Maximus HD Rom which as I am still S-On of course didnt work. So I wiped again but really careless and made mistake no. 3: wiping the whole thing instead of just a few partitions like system, cache,....
So now I have my device S-On, theres really nothing on it exept TWRP but there (and in other recoverys I tried) the USB mout doesnt work so I cant get a new rom on it So I tried to push it through fastboot but I cant find a fitting command.
Any advice what I can do to either get the USB work in the recoverys or push it through fastboot and which rom works without S-Off?
If you need further infos Id like to give those!

Akkordinator said:
So I got the HTC One s and try to root it with the following instruction: http://forum.xda-developers.com/showthread.php?t=1583427&__utma=248941774.997411949.1390324490.1394471756.1396118873.6&__utmb=248941774.2.10.1396118873&__utmc=248941774&__utmx=-&__utmz=248941774.1394471756.5.2.utmcsr=feedburner|utmccn=Feed:%20xda-developers/ShsH%20(xda-developers)|utmcmd=feed&__utmv=-&__utmk=25799614
As I thought that Step 3 was only there to install the Superuser.apk i just skipped it (mistake no. 1) and wiped the whole thing (without making a backup --> mistake no. 2) and tried to install the Maximus HD Rom which as I am still S-On of course didnt work. So I wiped again but really careless and made mistake no. 3: wiping the whole thing instead of just a few partitions like system, cache,....
So now I have my device S-On, theres really nothing on it exept TWRP but there (and in other recoverys I tried) the USB mout doesnt work so I cant get a new rom on it So I tried to push it through fastboot but I cant find a fitting command.
Any advice what I can do to either get the USB work in the recoverys or push it through fastboot and which rom works without S-Off?
If you need further infos Id like to give those!
Click to expand...
Click to collapse
TWRP has ADB Sideload feature. Means you can flash zips using adb. Of course you can flash a roms this but keep in mind you have to flash the kernel (boot.img) manually immediately after flashing the rom.zip. When flashed Rom.zip by using ADB sideload method make SURE that you direct go into fastboot mode and flash the kernel (fastboot flash boot boot.img) (you can extract the boot.img from your rom.zip)
May be a compatible rom this time? But you're lucky -> Infact you already deleted everything you won't have to perform a wipe before flashing lol

LS.xD said:
Of course you can flash a roms
Click to expand...
Click to collapse
Ok, but I dont know with which command (fastboot flash what? or adb?)

You can use adb sideload as followed:
Start TWRP -> advanced -> ADB sideload + swipe to activate it. Connect your phone to the computer. Open "CMD Commandline" and type "adb sideload ROMNAME.zip"
Of course "ROMNAME" has to match the zip you want to flash. Thats it
In twrp go to "REBOOT" -> "fastboot"
When fastboot usb is ready use CMD commandline again and type "fastboot flash boot boot.img"
Then you can boot android

I whished I could. As I start ADB sideload it keeps doing nothing at all until I abort it. What I think is important to know is that it is then:
"E:Unable to mout '/internal_sd'
E:Unable to mount storage.", which I think is the problem.

Flash Stock recovery And perform "factory Reset + clear storage" that will fix your storage. Then flash twrp Version 2.7 again and do what I suggested to flash the Rom
Sent from my beloved HTC One S using (most time buggy) Tapatalk

Did the exact thing which removes the mounting error, but this has no effect on the sideload (or usb mount). Still not working.

Akkordinator said:
Did the exact thing which removes the mounting error, but this has no effect on the sideload (or usb mount). Still not working.
Click to expand...
Click to collapse
Can you acces your sdcard by twrp? Lot of poeple here has sd card bug yet and it was fixed everytime.
You're facing sdcard bug.
This is how to solve:
1. Flash stock recovery
2. reboot to bootloader and perform "factory reset + clear storage" (While in bootloader NOT in recovery)
3. Flash custom recovery again
4. Reboot recovery - mount usb storage - copy ROM.zip to sdcard // adb sideload rom
7. NOW boot android (Not at any time before! Even there is no system installed)
Please just repeat it.

LS.xD said:
Can you acces your sdcard by twrp? Lot of poeple here has sd card bug yet and it was fixed everytime.
Click to expand...
Click to collapse
I can acces it in TWRP (of course only a TWRP folder in it). Tried the repeating progress over and over but nothing changes. And USB-OTG isnt able to mount.
Thanks for your patient help!

Akkordinator said:
I can acces it in TWRP (of course only a TWRP folder in it). Tried the repeating progress over and over but nothing changes. And USB-OTG isnt able to mount.
Thanks for your patient help!
Click to expand...
Click to collapse
In case you can acces the storage in twrp its related to windows or drivers. What windows version you are running?

LS.xD said:
In case you can acces the storage in twrp its related to windows or drivers. What windows version you are running?
Click to expand...
Click to collapse
It was windows! Tried it on the other computer with win7 instead of 8.1 and I finally got a connection!
Thanks so much!!!

nexus 5 softbrick

Hey,
Hopefully you guys can give me some help with the problem ive been having,
My nexus 5 is stuck in bootloop, i can get into the bootloader and the lockstate is unlocked but no custom recovery is appearing like it used to. I tried flashing using ADB but my phone doesn't show up as a device on my pc.
i have tried to wipe the cache ect and it comes up with "E:failed to mount /cache (invalid argument)
I only really know the basics of this stuff (only ever used the basic stuff to root and flash my phone)

You must use fastboot commands while being into the bootloader, not adb.

mworley1991 said:
Hey,
Hopefully you guys can give me some help with the problem ive been having,
My nexus 5 is stuck in bootloop, i can get into the bootloader and the lockstate is unlocked but no custom recovery is appearing like it used to. I tried flashing using ADB but my phone doesn't show up as a device on my pc.
i have tried to wipe the cache ect and it comes up with "E:failed to mount /cache (invalid argument)
I only really know the basics of this stuff (only ever used the basic stuff to root and flash my phone)
Click to expand...
Click to collapse
Yeah, exactly what primokorn says...
Primokorn said:
You must use fastboot commands while being into the bootloader, not adb.
Click to expand...
Click to collapse
If you use the command "fastboot devices" and your phone with a code appears in the command prompt then there's no problem with your drivers.
Just reflash the factory image, you can use the automatic process if you run "flash all". You can also flash the images manually but if you go for that option make sure you don't forget to flash the cache image, that will fix your problem with mounting the cache partition.

ADB commands are used when the phone is booted into the ROM.
Flash the latest stock ROM from here to see if it solves the issue: https://developers.google.com/android/nexus/images
If the phone still bootloops, flash the userdata.img in fastboot. After flashing the userdata.img file in fastboot, boot directly into stock recovery using the power/volume buttons, perform a factory wipe, and reboot.