Database Info

[Q] Desire S boots into recovery mode automatically!!

hello, I have a problem with a desire s phone which keeps booting into recovery mode when i turn it on. here's my step by step of what I did that got me into this predicament.
the phone had a stock 1.48 asia rom 0.98.0002 bootloader locked, and unrooted. so first I ran revolutionary had no problems there, had a revolutionary logo on my bootloader afterwards and the bootloader version was now 6.98.0002 or something I forget. anyway the next thing i did was I downloaded the stock euro rom 2.10.401.9 and extracted the rom.zip then renamed it to PG88img.zip copied it to the memcard ran fastboot, then fastboot automatically installed the zip after installation restarted the phone, now the phone was stuck on the white htc screen, so I ran recovery press the power and vol up and did a factory reset, had no luck with it still stuck on htc screen, now after reading a lot of threads, downloaded the ENGpg88img bootloader flashed it using fastboot and it was successful, the revolutionary logo was gone and the bootloader was now 6.98.0000 ( PG880000) but now when I rebooted the phone it would go directly back to recovery!! So the next thing i did was ran the euro rom again from the memcard thru fastboot and it updated the bootloader to the newest version and had a "locked"on top of the screen, so i did a boot unlock using htcdev and now its unlocked, then downloaded the clockwork recovery for saga then flashed it using fastboot with no problems. so now when I turn on the phone it goes straight to clockwork recovery! So last thing I did which also failed was I downloaded a pre rooted stock rom euro 2.10, placed it on memcard installed the zip from clockwork recovery then wiped all the data, dalvik cached and all then rebooted. But it still went back to clockwork recovery now I'm stumped. Really need help on this one.

long story short, I can only use fastboot, and if I use clockwork mod recovery to mount system i can do some adb commands. i also tried putting it in fastboot and ran an official RUu but I always get error 150. any help would be greatly appreciated.

It seems that your chip is gone. I have the same problem (boot looping) and had to try reclamation by phone provider. Find thread with "boot looping", or "white screen". You will find some software for a searching of your chip. Finaly all depends on your mobile vendor

yeah i thought it was the chip, but after 3 days of tinkering with it and reading a lot of threads i finally got everything back to normal. thanks for replying though zdech

batmite said:
yeah i thought it was the chip, but after 3 days of tinkering with it and reading a lot of threads i finally got everything back to normal. thanks for replying though zdech
Click to expand...
Click to collapse
Could you tell us how you solved it?

batmite said:
yeah i thought it was the chip, but after 3 days of tinkering with it and reading a lot of threads i finally got everything back to normal. thanks for replying though zdech
Click to expand...
Click to collapse
Hi, I have the same problem with HTC Desire.
Could you tell how you solved this please?

I don't know if he did what he wrote, but a big mistake was the last step.
batmite said:
So last thing I did which also failed was I downloaded a pre rooted stock rom euro 2.10, placed it on memcard installed the zip from clockwork recovery then wiped all the data, dalvik cached and all then rebooted. But it still went back to clockwork recovery now I'm stumped. Really need help on this one.
Click to expand...
Click to collapse
he installed ROM and wiped afterwards. Of course it fails at booting ;-)
If you really are in the same situation like him, wiping first and install ROM afterwards should solve the problem ;-)
Sent by my fingers to your head.

eyahl said:
I don't know if he did what he wrote, but a big mistake was the last step.
he installed ROM and wiped afterwards. Of course it fails at booting ;-)
If you really are in the same situation like him, wiping first and install ROM afterwards should solve the problem ;-)
Click to expand...
Click to collapse
Have to disagree with you there, what he said was
installed ROM
wiped DATA
wiped CACHE
rebooted
The ROM ZIP would have been flashed into SYSTEM not DATA, so wipe shouldn't have caused a problem
question is did BOOT flash ok?

One S bricked beyond repair?

So, a friend came to me and gave me his newly acquired One S and asked whether or not I could get it back up and running..
Apparently, from what I understand, he got the phone, unlocked the bootloader, but then didnt know that he should install a custom recovery image before attempting to flash CM10, so he used the stock recovery to flash the .zip from the SD Card. After rebooting (I have no idea if the flashing was successful) the phone is stuck on the quietly brilliant screen.
So, I took the phone, rebooted into the bootloader and used fastboot to boot up into a clockwork .img. Everything good so far, however, the problem is that its seemingly impossible to mount the SD card. My friend told me he fiddled around and "tried stuff", so I suspect somehow he must have messed with the sd card partition.
Since the SD card partition isnt actually on a physical removable sd card, I am running out of ideas.
Anyone have any bright tips? All I need is to get the Sd card mounted so that I can flash a ROM properly.
Thanks!

Try running an RUU.
-MobileUS HTC One S running Stock Rooted 2.21.

fmedrano1977 said:
Try running an RUU.
-MobileUS HTC One S running Stock Rooted 2.21.
Click to expand...
Click to collapse
Yeah, but I cant get the RUU on the device, since the SD Card partition is broken..

Untouchab1e said:
Yeah, but I cant get the RUU on the device, since the SD Card partition is broken..
Click to expand...
Click to collapse
Ruu is installed from a computer, flash standard recovery and lock the boot loader and then run the ruu.
Sent from my HTC One S using Tapatalk 2

RUU runs life an exe file on a PC, since your friend didn't install a custom recovery, just relock bootloader and run RUU while phone is plugged in to pc in fastboot mode.
T-MobileUS HTC One S running Stock Rooted 2.21.

Had a similar issue that you can't mount SD from clockworkmod, it mounts ok on TWRP, flash that recovery instead.

fmedrano1977 said:
RUU runs life an exe file on a PC, since your friend didn't install a custom recovery, just relock bootloader and run RUU while phone is plugged in to pc in fastboot mode.
T-MobileUS HTC One S running Stock Rooted 2.21.
Click to expand...
Click to collapse
Aha, right!
However, this still doesnt resolve the issue of a broken SD Card partition..

It probably isn't broken. I've never managed to mount SD through CWM. Try flash TWRP recovery and mount through there.

Dude just listen to everyone and download the ruu and run it only way to fix it I think
Sent from my HTC One S using xda premium

There is a sticky in Q&A on how to fix unmountable /sdcard. (Basically: Flash stock recovery through fastboot, then clear storage in bootloader, then flash your favorite custom recovery again.)
It would not surprise me if this is the same thing a RUU does (except for flashing your favorite custom recovery of course). If so, you don't need to fix your sdcard before running the RUU if you decide to go that route..
Beware that the RUU will also update your hboot, which you may not want.
If you don't want to re-lock, RUU, re-submit token, re-unlock, re-root, just manually fix the sdcard mounting issue. Once you can mount your sdcard in recovery, you can just adb push a rom to it, flash it, (wipe cache), boot it. (Depending on your ROM/hboot/recovery, you may have to flash the boot img through fastboot. The best time to do so is before booting into recovery.)
@djsubtronic: There is some misunderstanding about what 'mounting the sdcard' means.
If you can't mount it onto the root file system in recovery, you have a problem and it must be fixed. In this case you can't push/pull to your sdcard or select a zip from it for flashing. If you can't mount it on your computer over USB from recovery, that's not a problem and you don't really need it as you can still adb push/pull.

Try this
http://forum.xda-developers.com/showthread.php?t=1630459
Sent whit HTC ONE S

dave il barbaro said:
Try this
http://forum.xda-developers.com/showthread.php?t=1630459
Sent whit HTC ONE S
Click to expand...
Click to collapse
Thanks for all the feedback guys! Once my mate responds Ill give it a go!

Unfortunately, so far, no luck..
Booting into the bootloader and selecting "Clear Storage" seemingly did little other than boot up into the stock recovery. After going back to the bootloader and selecting factory reset (which also just booted up stock recovery), I made him do a data wipe/factory reset.. which seemingly ran okay, but the problem still persists.. sdcard partition doesnt mount in neither Clockwork nor TWRP, and the boot is stuck on the HTC quietly brilliant screen..
My next idae I guess is to try and install a RUU.. just need to set up a Windows VM as neither of us runs Windows

I had a situation similiar, when i went to flash, i had the recovery twrp, but something happened when i went to flash, and my sdcard got corrupted,
i cant remember if i formatted the sdcard thru windows, but i think i formatted it twrp, and then was up and running,
or in windows7 disk management i had to fix the partition then formatted...
this happened over a month ago took over an hour...
but i really really really dont think ur phone is bricked... i can be fixed...
get the ruu and go over a friends house who has windows.... hope it works...

Thanks, booted up a Win 7 VM and pushed in the RUU, partition table reconstructed and everything is back to normal.. Thats another One S now kicking CM10
Thanks for the advice everyone!

[Q] Stuck in CWM. Can't mount the sd card. Nothing is backed up.

I tried to install drumlock app and my phone restarted and went into the recovery. I can't mount the sd card either to flash the rom again. I dont have anything backed up. I am really lost and need someone's guidance.

I had the same issue one time what I did is I mounted the phone as a USB drive (don't know if it works with CWM, if not just flash TWRP recovery) and formated the SD card (when I mounted it Windows asked to format the SD card; Format in FAT32!). As you can imagine all data from the SD will be lost but your SD card is mounted again and you should be able to boot again. If booting still doesn't work try putting a ROM on the SD via mount as USB drive function and try to flash it. It should work.

worked but another problem happened :[
.TanTien said:
I had the same issue one time what I did is I mounted the phone as a USB drive (don't know if it works with CWM, if not just flash TWRP recovery) and formated the SD card (when I mounted it Windows asked to format the SD card; Format in FAT32!). As you can imagine all data from the SD will be lost but your SD card is mounted again and you should be able to boot again. If booting still doesn't work try putting a ROM on the SD via mount as USB drive function and try to flash it. It should work.
Click to expand...
Click to collapse
Thanks for that advice. Everything worked. I formatted the cd card and it is now seen in TWRP where I installed the viper one s rom. BUT! Now my phone just keeps on restarting - it shows the htc logo with a red banner under it and just restarts and does it all over again. I can get into boorloader mode If i get lucky pressing it before it restarts, yet the bootloader wont let me get into recovery. I am going to try other methods I guess but I am wondering if there is a way just to use RUU and restore it to stock?

vitality1 said:
Thanks for that advice. Everything worked. I formatted the cd card and it is now seen in TWRP where I installed the viper one s rom. BUT! Now my phone just keeps on restarting - it shows the htc logo with a red banner under it and just restarts and does it all over again. I can get into boorloader mode If i get lucky pressing it before it restarts, yet the bootloader wont let me get into recovery. I am going to try other methods I guess but I am wondering if there is a way just to use RUU and restore it to stock?
Click to expand...
Click to collapse
You must've done something to your recovery when you formatted your sdcard. Try flashing TWRP again. You can easily bring your device back to stock by running the RUU. Info can be found around the forum.

Relock bootloader and run a official HTC RUU (warning: itll update hboot).

what worked but now its stuck
farang4u said:
You must've done something to your recovery when you formatted your sdcard. Try flashing TWRP again. You can easily bring your device back to stock by running the RUU. Info can be found around the forum.
Click to expand...
Click to collapse
I tried that method and flashed utb rom and when i restarted it its stuck on the loading screen...so i tried the different viper one s rom and nothing either. After i locked it i tried the RUU but it gives me the error 150 ...Im on the right track I know...its probably something minor that I keep on overlooking.

gives me error 150
alexeius said:
Relock bootloader and run a official HTC RUU (warning: itll update hboot).
Click to expand...
Click to collapse
I also tried this method but it brings up the error 150. Could this be the recovery that is causing it ?

So you can't even get into recovery even if you flash it over fastboot?
Sent from my HTC Sensation

stuck on white HTC screen, S-off & can get into TWRP

Yesterday I downloaded the TWRP app and attempted to update TWRP via the app. It said the process failed. Later on in the day I rebooted my phone and on reboot I am stuck at the White screen with the HTC logo.
My phone is s-off and I have been running stock verizon KitKat ROM that has been rooted. I have text messages with information I cant afford to lose. I was able to pull my photos off the device using a USB cable, and I am able to get into TWRP and browse the data on the device.
Is there anyway I can flash an RUU or ROM that will NOT DELETE any of the data on my phone so that I can get the phone to boot again?
Any help is appreciated.
Thanks in advance!

ljx2k said:
Yesterday I downloaded the TWRP app and attempted to update TWRP via the app. It said the process failed. Later on in the day I rebooted my phone and on reboot I am stuck at the White screen with the HTC logo.
My phone is s-off and I have been running stock verizon KitKat ROM that has been rooted. I have text messages with information I cant afford to lose. I was able to pull my photos off the device using a USB cable, and I am able to get into TWRP and browse the data on the device.
Is there anyway I can flash an RUU or ROM that will NOT DELETE any of the data on my phone so that I can get the phone to boot again?
Any help is appreciated.
Thanks in advance!
Click to expand...
Click to collapse
Make a nandroid backup, It may boot later on. I've only flashed twrp using adb so I don't have any insight on what you did. If at a last resort you can run an ruu (after you saved said nandroid to a PC) then after the ruu add the nandroid back to the phone and flash it and see if it boots.
Another thing is to use twrp file manager and see if you can get a file like this one that hold the messages database, I found in a quick Google Search. /data/data/com.android.providers.telephony/databases/mmssms.db
You may be able to re-add it back to a ROM after ruu? Honestly not too sure
Wish I had more info,
Best of luck.

ljx2k said:
Yesterday I downloaded the TWRP app and attempted to update TWRP via the app. It said the process failed. Later on in the day I rebooted my phone and on reboot I am stuck at the White screen with the HTC logo.
My phone is s-off and I have been running stock verizon KitKat ROM that has been rooted. I have text messages with information I cant afford to lose. I was able to pull my photos off the device using a USB cable, and I am able to get into TWRP and browse the data on the device.
Is there anyway I can flash an RUU or ROM that will NOT DELETE any of the data on my phone so that I can get the phone to boot again?
Any help is appreciated.
Thanks in advance!
Click to expand...
Click to collapse
I'd recommend making a backup in twrp. Then you can ruu back to stock KitKat, reflash twrp WITH FASTBOOT, make sure it boots, then restore the data partition only and see what you get.

cntryby429 said:
I'd recommend making a backup in twrp. Then you can ruu back to stock KitKat, reflash twrp WITH FASTBOOT, make sure it boots, then restore the data partition only and see what you get.
Click to expand...
Click to collapse
Thanks for the suggestions everyone. I did make a nandroid backup in TWRP just in case i needed it. I reached out to DOTTAT and he suggested flashing his Android 6.0 RUU he had in one of his posts that did not overwrite data and he sent me a link to the file.
I downloaded it and flashed it using adb in fastboot and sure enough that got my phone to boot and simultaneously upgraded me which I was planning on doing soon anyway. On boot I was no longer rooted but since the phone is S-OFF I just installed TWRP using adb and then installed SuperSU and all is good.
Once again thanks everyone for the help!

HTC one A9 boot loop

So I decided I wanted to try to root my HTC One A9 today, I unlocked my bootloader, worked fine, installed TWRP, worked fine, attempted to install superSU, and now I'm stuck in a boot loop, I tried to do a reset through TWRP, that didn't work, still in loop, so I decided to install CWM recovery, but when I boot to recovery mode, i get red text that says "Failed to boot to recovery mode". So after that I decided to try to reinstall TWRP just to try that again, but now my phone isn't connected to my computer, but it's not because anything is corrupted, it's because I can't get past the boot screen to actually make my phone trust my computer. Any tips?

PHYN1X said:
So I decided I wanted to try to root my HTC One A9 today, I unlocked my bootloader, worked fine, installed TWRP, worked fine, attempted to install superSU, and now I'm stuck in a boot loop, I tried to do a reset through TWRP, that didn't work, still in loop, so I decided to install CWM recovery, but when I boot to recovery mode, i get red text that says "Failed to boot to recovery mode". So after that I decided to try to reinstall TWRP just to try that again, but now my phone isn't connected to my computer, but it's not because anything is corrupted, it's because I can't get past the boot screen to actually make my phone trust my computer. Any tips?
Click to expand...
Click to collapse
What version of SuperSU did you attempt to install? It sounds like you may have used a version that didn't patch dm verity and attempted to install to system, or something went wrong with the installation process.
I suggest you boot to download mode and flash the latest RUU for your version. You'd then have a clean slate to flash TWRP and the latest SuperSU to.

PHYN1X said:
So I decided I wanted to try to root my HTC One A9 today, I unlocked my bootloader, worked fine, installed TWRP, worked fine, attempted to install superSU, and now I'm stuck in a boot loop, I tried to do a reset through TWRP, that didn't work, still in loop, so I decided to install CWM recovery, but when I boot to recovery mode, i get red text that says "Failed to boot to recovery mode". So after that I decided to try to reinstall TWRP just to try that again, but now my phone isn't connected to my computer, but it's not because anything is corrupted, it's because I can't get past the boot screen to actually make my phone trust my computer. Any tips?
Click to expand...
Click to collapse
I would also suggest starting over with the RUU for your model. Once you get TWRP back however you may want to take a look at this thread http://forum.xda-developers.com/one-a9/development/rom-a9-base-roms-recovery-flashable-t3282335 for some pre-rooted stock ROMS. I'm running the Sprint one with Xposed/GravityBox right now and it's great.

CSnowRules said:
What version of SuperSU did you attempt to install? It sounds like you may have used a version that didn't patch dm verity and attempted to install to system, or something went wrong with the installation process.
I suggest you boot to download mode and flash the latest RUU for your version. You'd then have a clean slate to flash TWRP and the latest SuperSU to.
Click to expand...
Click to collapse
I used 2.46
I ordered a micro sd to usb stick so I'll be able to actually get the RUU file onto the sd card so it can flash it, I have to do it the SD card way because it isnt recignized by my computer because it doesnt trust it

Did you try re-installing drivers and flashing new recovery with fastboot?

PHYN1X said:
I used 2.46
I ordered a micro sd to usb stick so I'll be able to actually get the RUU file onto the sd card so it can flash it, I have to do it the SD card way because it isnt recignized by my computer because it doesnt trust it
Click to expand...
Click to collapse
I believe SuperSU 2.46 was your problem and that a RUU is not required to fix this. The older SuperSU broke the dm-verity for your system partition, which is enforced by your kernel. Flash SuperSU 2.76 (the latest stable release). This will automatically patch your boot partition. You will not be able to take an OTA until flashing the stock system image, though.
You just need to fastboot flash TWRP back to your device, first (fastboot flash recovery twrp.img) just like the first time from download mode--not the bootloader. Unlike ADB, your phone doesn't need to trust your computer.
If fastboot doesn't work, check what creusset said.
creusset said:
Did you try re-installing drivers and flashing new recovery with fastboot?
Click to expand...
Click to collapse