Hi All
Yep, there are a lot of posts about Desire's stuck on boot screens I know - and I've read them all but nothing seems to fins a solution to my problem sadly.
I'm having an issue running Oxygen 2.0.3 signed release on my HTC Desire, spec as follows:
Radio 5.14.05.17
HBoot 0.93
PVT4
S-ON
ClockworkMod Recovery v2.5.0.7
I did all the data, boot, and system wipes/formats recommended before installing new ROMs, and installed the zip from my SD card through ClockworkMod.
All is well on first boot - had it running happily for a couple of days. Then I turned the phone off and on again and it only boots as far as the white screen with the green HTC text, and progresses no further. When I go back to my Nandroid backup of the rooted stock ROM things appear to function as they should, if that makes any difference to a diagnosis.
I've tried reinstalling this ROM twice with the exact same result.
Can anyone help? I've had crashes with pretty much every ROM I've tried so far and, apart from this one considerable problem, Oxygen had been looking the most promising. I'm starting to wish I hadn't rooted at all - can't get a stable OS running at all since doing it, and getting really fed up
Thanks very much for any help.
Mark
I know this is an old treath, but I have exactly the same problem. Does someone knows what could be done to resolve this issue? I did the same thing as the topic starter.
Some info about my phone:
RAVO PVT1 SHIP S-ON
- Oxygen version 2.3.2
- HTC Desire GSM
- HBOOT version 0.93.0001
- RADIO version 5.11.05.27
Thanks in advance!
Related
Hi guys,
I've got a HTC Desire (Telstra) which I've used with a number of ROMs, most recently LeeDrOiD V3.0.8.2 GB Data++.
I was using the Bravo Oxygen HBOOT, note NOT the r2 version. I followed some guide around here on how to cut down the ROM at the time to fit on the smaller /system.
So anyway, this has all been working happily for a number of months. Yesterday I decided to upgrade to LeeDrOiD HD V3.3.3 Port R5 DATA++.
I downloaded the ROM to the SD card, did a full wipe + dalvik. Told it to install the ROM from the zip and that was all happy.
Reboot and the phone doesn't boot - just sits on the AlphaRev boot screen. I know you need to wait, I left it for a good half hour, but nothing.
I repeated the wiping + installing process two or three times without any luck.
Trying to work out what went wrong I came to the realization that I was using the non-v2 version of the Oxygen HBOOT so the thing was probably failing because of the different partition sizes.
I created a goldcard and flashed Oxygen r2 via a PB99IMG file which was successful.
Installed the ROM again (with wiping) but it's still doing the same thing - just sits on the Joker logo.
Anyone got any suggestions on how to proceed?
friendly bump
Hi Guys,
I literally feel sick to my stomach how dumb I've been.
I've basically fallen foul of the temptation to upgrade my HTC Desire S from the standard supplied gingerbread 2.3 to the hydrogen v1.9 saga v3 zip file (2.3.1.).
It’s crashed on me now all I have is the white HTC welcome screen.
I had installed the revolutionary.io s-off tool and rooted it. Everything seemed ok for about 3 weeks then I started to get intermittent phone call cut out and today it’s just frozen at the HTC logo on white background.
Today I have attempted to restore a backup file that I had made, to recovery it through the Revolutionary tool and it installed back to a low tech interface. I then tried to install over the hydrogen ROM again without success. Now it has 5 errors on the Rev tools’ opening page.
A mixture of;
Can’t mount/open recovery log/command/last log.
I don’t know what the hell to do any suggestions from you good altruistic folk?!!
Shall I try a factory reset?
I’d be very thankful of any suggestions. I just wished I’ waited for ICS, curiosity got the better of me
It sounds like an issue with your eMMc. The only way to recover is attempting to flash a stock ruu through hboot. If that doesn't work, it is likely nothing will. Stock RUU's can be found at this link http://forum.xda-developers.com/showthread.php?t=1002506 Good luck.
HI,
I am getting multiple installation errors when trying to clear/wipe/format cache/ system/ data etc.
I have tried installing Cyanogen ROM and installtion was aborted
I'm now trying to install a stock RUU as your suggestion. I don't know which one to choose the orange (I'm on Orange Network but no logo branding on phone) uk one I tried just wouldn't run and aborted and requexted an error mesaage. I'm now trying to install the RUU_Saga_S_HTC_Europe_2.10.401.5, one if thatg doesn't work any ideas which one I should go for?
Cheers
So I got the desire S for more then a year now and decided to flash it with 4.0.4.
Build date 24 june. From here.
Now the first week I didn't seem the have any problems but now it randomly reboots. Mostly it keeps rebooting till I plug it in the powersupply then it keeps working and I can take it out again. But after a while... during a call or just when it's in my pocket it reboots again. What can be the problem here? Anyone who got a anser for that?
More information please
ROM name? How did you root / unlock your DS? What other apps have you recently added that may have helped to cause this?
We aren't mind-readers - our balls are made of flesh and blood, not crystal :angel:
Yeah sorry.
http://forum.xda-developers.com/showthread.php?t=1429215
CyanogenMod 9 Alpha for HTC Desire S
That mod I installed. I only installed whatsapp and google maps.
Other then that didnt do anything else.
To unlock the phone I used the following software.
SuperOneClick 2.2
adb-fastboot-win
ClockworkMod Recovery
There were problems like this a while back with CM9, but they haven't happened for a while.
There were, also, some issues with using CMW but none with using 4EXT Touch.
So, my suggestion would be:
Install 4EXT Recovery Control and Touch Recovery (https://play.google.com/store/apps/details?id=ext.recovery.control)
Install the ROM again using a clean install - superwipe all partitions as 4ext (format, not to be confused with the name of the recovery tool)
I assume that if you are on hboot 2.00.0002 you know about http://forum.xda-developers.com/showthread.php?t=1525100
Hello guys, I've been having unusual problems with my recently purchased 2nd HTC Sensation 4g (it was supposedly brand new). I already have one HTC Sensation 4g running on Revolution HD for almost a year and regularly update it. Anyways, onto my issue with my new HTC Sensation...After I attempted to put on a new 3.33 firmware and the RevolutionHD 6.7.2 ROM, I was unable to boot it (stuck at the HTC quietly brilliant screen). I then tried to put on the latest T-Mobile RUU and again, it got stuck at the boot screen. I then superwiped again and repeatedly try out a bunch of the complete big ROMs (OrDroid 9.0, Elegancia Pegasus, etc) without any success. I was about to give up and figured my phone is bricked, but then decided to try out the more simple CM9 ROMs (Extreme Sensation Power-2) and was shocked it was able to boot and fully function! I then tried out similar ROMs and currently running Infinity's TouchCream 2.1.
I would appreciate if anyone have experienced similar issues and could give me some advice on how I could address it. I will have to do more experimenting to find out what's being going on. I have a feeling it could be a much more complicated problem than just simply mismatched/outdated ROM or Firmware. The reason why is because my 1st HTC Sensation (the control) was tested using the exact same configs without one single hiccup.
Reflash the newest firmware and then ARHD
I assume you are s-off with the latest 4EXT. If not, do that first.
I would download the latest 3.33 universal package: http://d-h.st/bCV, along with the latest ARHD 6.7.2: http://goo.gl/QDuTC
Run the firmware update through HBOOT (place PG58IMG.zip on root of the SD card, VOL DOWN + POWER, accept update), and then reboot into recovery.
4EXT should warn you that it is in safe mode due to a change in your HBOOT/partitions (if not, reboot recovery again, and if still not, you were already on 3.33 with revolutionary HBOOT ), so do a format of all partitions except SD card.
From there, reboot recovery again, and do a full wipe again to be safe, and install ARHD. Leave it for 5m to boot, should work.
Thanks for the advices guys. Unfortunately, none of the methods changed any of the results of my 2nd Sensation. It would still not boot the bigger ARHD or Elengancia ROMs (what appears to be Sense ROMs). However, it boots on CM9 ROMs (like TouchCream or Extreme Sensation). I have an identical phone that's a little older, which I've used as the "control" in my experiment. I've been using pretty much the exact same files and steps that you've mentioned, but my 2nd Sensation wouldn't go past the boot screen, even after 30m of waiting (meanwhile, my 1st Sensation has already finished its first boot within 5m). This happens every single time...frustrating! Please note that my 1st Sensation is also going through the exact same steps, just so I can eliminate obvious software or user errors. Anyways, I'm pretty happy at least I'm able to run TouchCream2.1 on this phone and enjoy pretty much all the functions that the HTC Sensation has to offer after I install the suitable apps & widgets. Thanks again!
Hello, thanks for your time to read in advance.
Background
I've had my first smartphone (HTC Desire HD) for about 3 year and decided it was getting old and slow even though it had Cyanogemod 7.2 successfully loaded on it. So recently I bought a new one online for about $150 from China. Looks identical, weighs the same however there are very small details that still make me doubt its authenticity. I'm 90% sure its legit even though the IMEI is fine. I ran the new one through the same process (AAHK) I did with the old one to install Cyanogenmod.
The HBOOT details:
ACE PVT ENG S-OFF RL
HBOOT - 0.85.2425
MICROP - 0438
RADIO - 26.03.02.26_M
eMMC - boot
Apr 12 2011,00:55:45
NO ROM LOADED
NO RECOVERY IMAGE (TeamWin originally)
The problem
Right now, this phone may be bricked (completely dead?), I am hoping its not. I have no ROM loaded on it so I cannot enable USB Debugging and now there is no recovery image either. When I am in HBOOT menu, I select the recovery option, phone does a reboot and shows this:
http://imgur.com/YsCGTSQ
What I did to break it
Initially I had CM 11 loaded and after a while it started to show errors. So I decided to go back and install CM 7.2 the more stable option.
Once I did this, the CM 7.2 ROM now somehow in the process of being loaded copied all the additional apps I had installed on the CM 11 ROM with it. Now I had CM 7.2 with apps that I should have manually had to install.
I tried several times to clear the cache and Dalvik cache through the TeamWin recovery. Then tried to reload CM 7.2. Same problem.
I then ran phone through AAHK (http://forum.xda-developers.com/showthread.php?t=2367322) again which I believe fried my phone. Or I could have also done a factory reset then ran the AAHK. Not exactly sure, it was a while ago when I was doing then.
What can I do to fix the phone?
Anyone with the time and patience please help. If you need any clarifications ask away.
TIA
ant-onov