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?

[Q] CWM wipe s-on Brick

Long time listener, first time caller.
I have the latest hboot 1.45.0013, S-On, Unlocked with HTC Dev Tool.
I used the Hasoon2000 tool to install SU, CWM, and a recovery image. I then used the instructions in the thread (http://forum.xda-developers.com/showthread.php?t=1508556) to install ICS and obtain root installing pyr-o-ice sense 1.1.1 (http://forum.xda-developers.com/showthread.php?t=1469615) Everything worked, created nandroid backup and installed titanium.
Some buttons didn't work, so I looked for updates and found Virtuous ROMs. So, I used CWM to clear dalvic, flashed boot image of the Virtuous Inquisition then used CWM to install zip. Bootloop. ROM just hangs on black screen with white V for 15 to 20 minutes.
MT4GS thread stated that Primadonna and Inquisition were comparable, so I followed the same proceedure, flashed Primadonna boot image then installed ROM through CWM. This time there was tmobile splash screen, but the same system hang.
At this point I tried to restore a recovery, but CWM could not find one. Used Astro to delete all boot images from SD root, assuming this may be the problem, and flashed a Virtuous ROM again. Same problem.
Based on this thread, I thought it might be the kernal, and tried flashing the pyr-o-ice boot image that worked initially. (http://forum.xda-developers.com/archive/index.php/t-1628171.html). No dice. CWM could not install the ROM (error 1)
So, at this point, I used CWM factory reset and wipe all data. And of course that made things worse, because the SD card with recoveries was wiped. I used adb to push the recoveries from Hansoon's toolkit, but stock recovery was not available (red triangle screen hang) and cwm could not mount the SD card.
So, at this point I used CWM to format SD card (blank anyway), and at this point adb failed to recognize the decive and I could no longer fastboot into recovery or hboot through adb. (volume down + power stopped working with pyr-o-ice install)
if i remove the battery and hold power + volume while using an adb reboot hboot command i can get into hboot about every 10th attempt. adb doesn't recognize the device ("waiting on device", or adb devices yields a blank list); however the phone in hboot will transfer to usb fastboot when connected with a cable.
i looked at pushing a zip file through adb to the sd root, but that was ineffective (adb does have write access to the sd root, maybe because i am s-on?). i purchased a second sd card, and copied the recovery images from hansoons toolkit and rebooted into recovery. still went to tmobile splash, followed by V-screen bootloop.
i looked at placing a stock ruu on the sd and naming the file PG59IMG.zip, but because i'm S-on i can't flash radios, so that's out.
So, here we are. Iffy access to fastboot, 2 sd cards, a lot of determination, and a persistent bootloop.
Can someone, PLEASE help me?
Thanks!

AFAIK, you cannot flash the boot.img with CWM if you are S-ON, you *MUST* use Fastboot to flash that. So, before you messed it all up, if you had just extracted the boot.img from the ROM and flashed it using Fastboot, it likely would have worked just beautifully.
Try booting into recovery and doing a regular flash of the ROM, THEN a fastboot flash of the boot.img.

SOLVED!!
Thanks to the folks heading up the HTC Unbricking Project (http://forum.xda-developers.com/showthread.php?t=1627881) ESPECIALLY Dexter93!! who patiently unraveled this for me, and Blue6IX for the Restore to Stock instructions in the Developers Reference Guide (http://forum.xda-developers.com/showpost.php?p=17424340&postcount=24) I'm back to stock, and ready to try it all again!
Can someone send me an apk that automatically clicks the thanks button for selected developers at regular intervals?
Thanks again!

Solved???
Fuzi0719, thanks for your reply. I may have written this inappropriately, but what coded in the command prompt was "fastboot flash boot boot.img".
The ROM zip file was placed on the SD card, and I rebooted into recovery, and used CWM to install zip from SD. I'm new to this so I may have used the wrong term for installing the zip through CWM, the boot image file was always handled through the above command.
I'm back to "stock" at this point, but when I boot into the bootloader, the phone looks for PG59DIAG.zip and PG59DIAG.nbh before PG59IMG.zip.
It then asks if I want to install the update. (This is after I have already installed the "update", and the phone reset itself even with my old wallpaper.) When I got to the home screen there was a white circle in upper left corner of the status bar, with "check content" message. Each time the screen locked (default 30 seconds) unlocking it took me to the mytouch splash screen with the green circle and white background for about 10 seconds before resuming.
Each time I check to see if the phone registers requiring any updates. It doesn't. Two installs of the PG59IMG.zip. "recovery" eliminates the unlock splashscreen, and wiped any customizations. However, the phone will not manually boot into the bootloader; I have to use adb. Hboot reinstalls the PG59IMG.zip as an update every time.
If I accept it reboots within seconds like a fresh doubleshot. If I decline the "update" it reboots to the Tmobile MyTouch 4G Slide text splash screen, then moved to the green circle screen for a few minutes before I get to the homescreen.
Blue6IX was looking for help with these last month (http://forum.xda-developers.com/showthread.php?t=1580077), so maybe they are just extraction files that HTC sends with the OTA update that would prevent my phone from trying to install the "update" every time?
In any case, my question at this point is after coming from such an unstable point with my phone, is this what every relocked bootloader does? Or, is this a problem that means something else is still wrong with the system? Because taking it back to stock has not solved this.
Thanks.

Thanks for clarifying, you wouldn't believe the number of people who fail to follow that one simple step of fastboot flashing the boot.img, so that's why I stated that. So, now you have the phone relocked, and running a stock ROM (the 1.55?), but with CWM 5.0.2.7? Were you wanting to update to the 1.63 ROM? I'm unclear on what it is you want to do. For one thing, if you've already flashed the PG59IMG then I would delete it off the sd card so it doesn't keep trying to load it.

Yup.
It was just that simple.
Mainly I wanted to make sure that my phone was stable before I went back to unlock the bootloader, etc.
Went back to HTC, got a new token (just in case), and I'm creating a nandroid backup right now. Thanks.
I really appreciate it.
Hopefully the next time I get stuck, it's just as simple to fix, but far less embarrassing.

[Q] Flashed new kernel, won't boot

I used Hasoon2000's HTC All-In-One Kit to root my phone. That all worked.
The issue came when i flashed a new kernel. I placed the boot.img from King Kang's new ROM (http://forum.xda-developers.com/showthread.php?t=1959099)
Anyway, When i boot I get the HTC, quietly brilliant logo, and this in red letters "This build is for development purposes only. Do not distrubute... "
i can boot into recovery (pwr+ vol down)
And i get the ***TAMPERED*** AND ***unlocked*** tags at the top
I don't know where to go from here...
Thanks for the help.

Also, whenever i boot into recovery or factory reset, neither succeed.
This was probably known info, just wanted to add it.

ccamwilkins said:
Also, whenever i boot into recovery or factory reset, neither succeed.
This was probably known info, just wanted to add it.
Click to expand...
Click to collapse
You mentioned in your original post that you could boot into recovery, so is that not working now? Factory reset might've fubared the recovery piece, so you could do one of two things:
1) download the original RUU version for your phone, relock your phone, and flash the RUU and start over.
2) try reinstalling TWRP.
This whole thing sounds like trying to install a kernel or fastboot flash a boot.img without SuperSU correctly installed. This is what happened to me when I first unlocked my phone and tried to fastboot flash the CM10 boot.img after failing the flash from recovery twice. Without that super-user permission, bad things tend to happen. If you decide to continue on with reinstalling TWRP, make sure SuperSU.zip is flashed successfully from
TWRP, then try your rom/kernel combination again (or even a different combination if you're apprehensive).
BEWARE: sometimes partially flashing these things can corrupt your sd card. I had to reflash the original RUU to fix my phone BEFORE I rerooted and flashed a rom/kernel.

Have you fastbooted a SU to your phone after you rooted and unlocked? I'd imagine you did if you followed the toolkit.. So your on 2.20... Just download cleanrom 5.1 on your computer. Mount sdcard via recovery and drag cleanrom onto phone. Flash entire rom in recovery. I bet it works
Once your on a stable rom, download king kang from your phone. Download flashgui. Open flashgui app, navigate to king kang and let it find the boot img and flash it for you.. Once successful, immediately boot into recovery and flash entire rom through twrp.
Success
Sent from my One X using Tapatalk 2

PLEASE READ, Bricked, PLEASE HELP

i have a htc one s ive been using for over a year now, recently i decided to try to flash recovery using termnal instead of cwm or goomanager because the flash always failed. so i used the dd if something command in terminal and now when i rebooted it got stuck on the splash screen, i then tried to go into recovery via bootloader but then accidently pressed factory reset and everything went downhill, i flashed stock radio did the clear storage then reflashed cwm and flashed the cyansense rom, it went through quick and when i rebooted the same thing happened, stuck on splash screen. i tried erasing cache from fastboot and nothing, i tried flashing ruu and it goes to 3% then fails. i need my phone back to stock for work. i am s-off with custom splash screen and cid 111111111 i will post a picture later.i can access recovery and bootloader. i desperatley need help

If you can access bootloadee I don't see a reason for the RUU to fail.. Just connect your phone when on bootloader make sure it says fastboot usb, close all other programs and run the RUU as admin. If you cant do that try this: http://forum.xda-developers.com/showthread.php?t=2322755 and then factory reset and clear storage (DO NOT flash custom recovery yet just follow exactly the instructions) and after fact reseting and clearing storage flash custom recovery and flash rom. (I think the newest cwm doesn't work, neither in mine worked I don't know just flash twrp 2.6.3.0 or an older cwm 6.0.3.1 works fine for me.)

XZP Wont Boot after Flashing Standard Rom

Hi All,
I've been trying to install TWRP, Root etc on my XZP since yesterday. I've done something wrong at some point, and now my phone will not boot at all.
I had no troubles unlocking bootloader, installing TWRP etc initially. I then tried to install a custom rom from these forums and that's where things spiraled downwards for me.
As part of that procedure, I needed to flash the latest sony firmware first. That went fine.
However, now TWRP is not able to decrypt storage, so I'm not able to flash anything else. Perhaps this is because I booted into the new sony firmware and forgot change the pattern/fingerprint to pin/fingerprint.
So I'm not able to unlock the storage via TWRP by entering a password.
I tried to reflash the same firmware again using newflasher. But the phone won't boot at all. It turns off immediately after the Unlocked bootloader warning. It's not going into a boot loop. Just turns off.
I then tried to flash the TWRP recovery image using adb fastboot command, and the flash seemed to execute properly, but I still can not boot into recovery.
Is it possible the main storage is still encrypted, so nothing can flash to it? Bricked? If so, how do I proceed?
I read something about reformatting partitions? But I'm not able to get into TWRP recovery menu to do this.
*EDIT: I reflashed trwp recovery image, and am not able to boot into recovery. I still can not unlock (unencrypt) the main storage though.
*2nd EDIT: I followed the instructions here:https://forum.xda-developers.com/android/general/how-to-fix-unable-to-mount-data-t3830897
I was then able to flash the stock ROM back onto my device, and I'm able to boot my phone up. I'll look at installing a custom ROM at a later date.

Thread closed at OP request