[Q] Help - HTC Desire S Can't boot - HTC Desire S

Hello, I'd like to ask you for help, because I have following problem with my htc desire S (HBOOT 2.00.0002, RADIO_3822-10-08-04_M and S-on).
I unlocked bootloader according to htcdev and rooted by SuperOneClick 2.3.3. Than I installed 4EXT Recovery v 2.2.7 RC5 and prepared ROM files (Endymion_V3.1_base_release.zip and Endymion_V3.4_updater.zip) on my SDcard.
After that I entered Bootloader and 4Ext Recovery without any problem. And here is probably my fault. I have formated everything with SDcard exception - that means also /boot. Following installation of both prepared files (Endymion_3.1 + 3.4) from SDcard ended with "success".
BUT. When I rebooted phone, display remained white with green letters HTC only. To switch the phone off I had to remove battery. On the other hand
I am able to start bootloader (SD Checking: Load PG88DIAG.ZIP - No Image; Load PG88DIAG.nbh - No Image or wrong image) and 4Ext Recovery.
Let me know please, what to do and how to repait it.
Thank you.

rubep said:
Hello, I'd like to ask you for help, because I have following problem with my htc desire S (HBOOT 2.00.0002, RADIO_3822-10-08-04_M and S-on).
I unlocked bootloader according to htcdev and rooted by SuperOneClick 2.3.3. Than I installed 4EXT Recovery v 2.2.7 RC5 and prepared ROM files (Endymion_V3.1_base_release.zip and Endymion_V3.4_updater.zip) on my SDcard.
After that I entered Bootloader and 4Ext Recovery without any problem. And here is probably my fault. I have formated everything with SDcard exception - that means also /boot. Following installation of both prepared files (Endymion_3.1 + 3.4) from SDcard ended with "success".
BUT. When I rebooted phone, display remained white with green letters HTC only. To switch the phone off I had to remove battery. On the other hand
I am able to start bootloader (SD Checking: Load PG88DIAG.ZIP - No Image; Load PG88DIAG.nbh - No Image or wrong image) and 4Ext Recovery.
Let me know please, what to do and how to repait it.
Thank you.
Click to expand...
Click to collapse
You need to extract boot.img from the endymion zip file and flash it using fastboot.
The command you'll need to execute is:
fastboot flash boot boot.img
For details on how yo set up fastboot click on the link on my signature.
Beamed from the Dark Side using xda premium.

Download the rom again, extract boot.img from the zip and flash with fastboot

Thank you very much. After boot flash everything works again.

i hade the same problem last weak but after flashing boot,img it was not gone. then i have take out the sd card and ...TADA.. it boots.
Ok then i have shut down the phon ant put the card back in and same problem hangs on htc logo.
then i have put the card in my computer backedup the stuff i need and formated the carde new with fat 32 and put it back in the phone.
And it boots

Related

[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.

Help i think I bricked my phone

Hey Guys,
I tried pretty much everything and don't know what else to do. My phone just stays stuck on the android screen. I forget that the "SD card" in this phone is actually part of internal storage, I did a factory reset and lost everything.
I tried flashing different boot.img and getting nothing. I'm afraid I need to get a rom onto the sd card but how is that possible if I cant get my phone to boot up.
Any ideas?
Thanks!
volume down button+power button try this combination until u get in the bootloader then select recovery. once in recovery just restore a backup if you have one, you should have one
i dont have a backup and i have nothing on my "sd" to i can install. I have formatted the ROM and thats why it wont boot..
If you can get into Recovery (CWM) in the advanced settings if i remember, there's a "format sd card" to make it work with the installation of a custom ROM
I posted a tutorial for how to do this:
http://forum.xda-developers.com/showthread.php?t=1667929
brwetz said:
I posted a tutorial for how to do this:
http://forum.xda-developers.com/showthread.php?t=1667929
Click to expand...
Click to collapse
thanks for the guide but im getting error mounting /sdcard. and if i follow cannondale0815 solution for that problem when flashing the stock and cwm I cannot access recovery mode.
Clear Storage in fastboot and re-install CWM then try it. That's how I got mine to work
Ok if your bootloader is locked and you have a custom recovery first flash stock recovery then boot into fastboot and run "fastboot oem lock" After that restart your phone and boot back into fastboot. Then run the RUU for your model and cid. easy.
Follow the steps which might work
1, If you knows something about adb, you can just simply push a rom into the sdcard(You don't need to do this if there is already a flashable rom in the sdcard), flash the kernel in fastboot, go to the recovery, wipe and flash a new rom. Then everything(except your data) should be fine
2, If you are not able to use adb push, or you have never flashed a recovery/3rd-party rom/ or you have other issues:
Using the RUU updater might be safe and simple (of course everything except those in the sdcard will lost)
a, relock the hboot using "fastboot oem lock"(or the RUU will refuse to continue)
b, run the RUU updater, wait for ~10min, your phone will be "refreshed" to something like the 1st day you bought it, except the Hboot will say it is "RELOCKED s-on"(this should be LOCKED s-on at first)
c,unlock your phone again(if you have stored the .bin file for unlock, just push it to your phone in the fastboot mode which is enough already, it is not needed to do the whole process in HTCDEV again.)
IMPORTANT: the RUU updater and the phone must be the same area. for example an Europe's RUU can't be applid to an US's One S
This is also the only method to update the Radio software, unless the hboot is S-OFFed
Bure03 said:
Hey Guys,
I tried pretty much everything and don't know what else to do. My phone just stays stuck on the android screen. I forget that the "SD card" in this phone is actually part of internal storage, I did a factory reset and lost everything.
I tried flashing different boot.img and getting nothing. I'm afraid I need to get a rom onto the sd card but how is that possible if I cant get my phone to boot up.
Any ideas?
Thanks!
Click to expand...
Click to collapse

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] HTC one x stuck on htc logo

Hello, yesterday I've unlocked my phone - there was no problems at all. Then i wanted to put cm on. Downloaded one from this adres: http://get.cm/?type=RC, then i forgot to copy the files on my phone and flashed with rom extracted from the package. After that phone is stuck on htc logo. Cannot connect it to the pc as a storage. Tried to format Dalviks cache, factory format, recovery in clocwork all with no results. If anyone could help me i would be extrmly grateful. Thanks
waglik said:
Hello, yesterday I've unlocked my phone - there was no problems at all. Then i wanted to put cm on. Downloaded one from this adres: http://get.cm/?type=RC, then i forgot to copy the files on my phone and flashed with rom extracted from the package. After that phone is stuck on htc logo. Cannot connect it to the pc as a storage. Tried to format Dalviks cache, factory format, recovery in clocwork all with no results. If anyone could help me i would be extrmly grateful. Thanks
Click to expand...
Click to collapse
Evita download isn't even on that page -_- Are you using an evita htc one xl? If not, wrong forum. If so:
download a rom from this Forum section, if you like AOSP, there's a bunch to choose from in Original android development.
download twrp 2.3.3.1 do not use any version above 2.3.3.1
Check MD5 of your downloads, make sure it matches.
Reboot to bootloadrer
fastboot flash recovery twrp2.3.3.1filename.img
fastboot erase cache
fastboot reboot-bootloader
Select recovery from bootloader
Mount USB storage
Copy your rom over.
wipe cache, dalvik, system, factory reset
Flash your rom zip file
If you are S-OFF or your hboot < 1.14 reboot you're done.
If your hboot >= 1.14 and S-ON extract the boot.img from the rom you downloaded
reboot to bootloader/fastboot
fastboot flash boot boot.img (the one you just extracted from the rom)
I wasn't going to help you at first because this EXACT post is created at least once a day and is easily fixed by reading and understanding what you're doing. Hopefully this is a wakeup call that you should not be rooting your phone without knowing at least the basics.

Stuck in ClockworkMod Recovery v5.8.0.9

Hi
Tried to flash my HTC with cm-12.1-20151018-UNOFFICIAL-pyramid - now stuck in recovery mode
Had a backup of previous system, tried restore but it won't boot into original system, just ends up in recovery mode.
Have rooted phone, installed CWR, and copied the cm-12.1-20151018-UNOFFICIAL-pyramid.zip and the gapps-lp-20141109-signed.zip to the SD card. when trying to install it fails - seems it has some mount problems ?
Please help
OddE
oefiske said:
Hi
Tried to flash my HTC with cm-12.1-20151018-UNOFFICIAL-pyramid - now stuck in recovery mode
Had a backup of previous system, tried restore but it won't boot into original system, just ends up in recovery mode.
Have rooted phone, installed CWR, and copied the cm-12.1-20151018-UNOFFICIAL-pyramid.zip and the gapps-lp-20141109-signed.zip to the SD card. when trying to install it fails - seems it has some mount problems ?
Please help
OddE
Click to expand...
Click to collapse
change your recovery to 4ext
http://d-h.st/rG7
extract the recovery.img and flash it via fastboot
the command is fastboot flash recovery recovery.img
then from 4ext
format all partitions except sdcard
enable smartflash (only if you are on S-ON)
flash the rom
done
Screen flaw as well
rzr86 said:
change your recovery to 4ext
extract the recovery.img and flash it via fastboot
the command is fastboot flash recovery recovery.img
then from 4ext
format all partitions except sdcard
enable smartflash (only if you are on S-ON)
flash the rom
done
Click to expand...
Click to collapse
Thanks a lot !
Managed to flash the 4ext, and it's running well. But I ran into another problem that makes me wonder if I should discard the Sensation totally. I started this because I wanted to give it to a friend, I currently have a S4 active.
When I changed from HTC to Samsung it was mostly because I tought it was too slow, but in the end there was also a issue with the upper right corner of screen starting to be unresponsive. Seems the flaw have gotten bigger, and now it seems that a larger portion of the screen failing - I can't even manage to press install from SD card in 4ext - lol
**** happens !!
OddE

Categories

Resources