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!
hello.
I had a HTC One S, T-Online Germany branded, with s-on and the Viper rom(-> unlocked and rooted).
Then it ran out of batterie, (not the first time that happend after a long day) and when i plugged it in and turned it on again, the x-axis of the touchscreen was mirrored: The Display is normal but when I touch anywhere on the left side it acts like I touched at this spot on the right side.
I was hoping that it was some bug in the rom, and flashed it again.. while flashing I discovered that the same bug is in the recovery (twrp).
I reflashed the recovery and rom a cupple of times untill I lost hope.
Then I s-off'ed it and changed the cid (I wanted to do this since a while) and flashed some custom kernels to see if this would bring any change..
I have no idea what else I could try to solve this.. has anyone a good idea or do you believe it is an hardware bug?
sincerly, menessim
well I guess, no one can help here..
I'm hoping for some friendly advice - I have a Desire S which was rooted last year and I installed CM10 to try out JB. All has been working well )part from the occasional reboot) however couple of days ago the battery started draining quickly, the phone became very hot and the wifi stopped working. After various wiping of caches and rebooting I decided to try some other ROMs (Fallout Evolution V5, Miui, IceDS) and although they all installed OK I still have no wifi and now the mobile network won't work.
It worked on Fallout at first but when the wifi wasn't working I wiped and re-installed and it hasn't worked since. It does see the O2 network although the phone hd previously been unlocked to work with Vodafone, so I think I may have rolled back the radio somehow.
At this stage I'm not entirely sure if it is a software or hardware problem, and I din't know how to test the hardware.
The phone is currently as follows:
UNLOCKED
Saga PVT ship s-on RL
HBOOT -2.02.0002
Radio -3831.19.00.110
eMMC -BOOT
July 31 2012>15.41.32
Do I need to update the radio? If so, which version should I use? And do I need to s-off the phone first?
Any other help would be appreciated.
lesmorton said:
I'm hoping for some friendly advice - I have a Desire S which was rooted last year and I installed CM10 to try out JB. All has been working well )part from the occasional reboot) however couple of days ago the battery started draining quickly, the phone became very hot and the wifi stopped working. After various wiping of caches and rebooting I decided to try some other ROMs (Fallout Evolution V5, Miui, IceDS) and although they all installed OK I still have no wifi and now the mobile network won't work.
It worked on Fallout at first but when the wifi wasn't working I wiped and re-installed and it hasn't worked since. It does see the O2 network although the phone hd previously been unlocked to work with Vodafone, so I think I may have rolled back the radio somehow.
At this stage I'm not entirely sure if it is a software or hardware problem, and I din't know how to test the hardware.
The phone is currently as follows:
UNLOCKED
Saga PVT ship s-on RL
HBOOT -2.02.0002
Radio -3831.19.00.110
eMMC -BOOT
July 31 2012>15.41.32
Do I need to update the radio? If so, which version should I use? And do I need to s-off the phone first?
Any other help would be appreciated.
Click to expand...
Click to collapse
Did You tried installing stock rom again in your mobile
No I haven't. I assume this would re-install the correct radio?
Not sure where to get the stock ROM, or which one was shipped with the phone.
If I did get it can I flash it through recovery - I'm using 4EXT?
lesmorton said:
No I haven't. I assume this would re-install the correct radio?
Not sure where to get the stock ROM, or which one was shipped with the phone.
If I did get it can I flash it through recovery - I'm using 4EXT?
Click to expand...
Click to collapse
Boot into bootloader and run following command
fastboot get cid
Than you can know which ruu to flash. But don't forget to downgrade your misc version before fishing ruu
No ruu are flashed from PC
Sent from my HTC Desire S using xda app-developers app
OK, I have managed to get the phone back to it's stock ROM which is O2 in the UK.
I had previously unlocked the phone but it now won't accept anything other than an O2 SIM. When I scan for networks only O2 is seen. I still have the unlock code but when I put a Vodafone SIM in it doesn't prompt me for the unlock code. I'm just getting a Limited Service display.
Is there any way of forcing the unlock code prompt screen - say with keyboard numbers or via Fastboot?
lesmorton said:
OK, I have managed to get the phone back to it's stock ROM which is O2 in the UK.
I had previously unlocked the phone but it now won't accept anything other than an O2 SIM. When I scan for networks only O2 is seen. I still have the unlock code but when I put a Vodafone SIM in it doesn't prompt me for the unlock code. I'm just getting a Limited Service display.
Is there any way of forcing the unlock code prompt screen - say with keyboard numbers or via Fastboot?
Click to expand...
Click to collapse
do i understand things as they are?
do you intend to use simcards of another operator?,
well... that`s what branding stands for,
to make sure
you`ll not use any sim from different carrier...
is your phone simlocked as well,
or is it only a branded rom ?
..but why bothering to flash the phone with branded RUU,
(when there are quite a few generic ones, still floating around,..)
except, when one wants to claim a warranty..may be...
I flashed the O2 ROM as it was what was on the phone when I bought it and I was trying to get back to a radio that would work.
I have since managed to get the phone working OK with the Asda/Vodafone SIM but I am still having problems with the wifi (this is where it all started!). whenever I switch the wifi on it scans and then reports that it is unable to scan for networks, after 2-3 attempts the wifi switches itself off.
I'm still trying to find out if it is a software or hardware problem. Other than that all is working well on the Fallout v5 ROm I have flashed - although it does make the phone run hot.
lesmorton said:
I flashed the O2 ROM as it was what was on the phone when I bought it and I was trying to get back to a radio that would work.
I have since managed to get the phone working OK with the Asda/Vodafone SIM but I am still having problems with the wifi (this is where it all started!). whenever I switch the wifi on it scans and then reports that it is unable to scan for networks, after 2-3 attempts the wifi switches itself off.
I'm still trying to find out if it is a software or hardware problem. Other than that all is working well on the Fallout v5 ROm I have flashed - although it does make the phone run hot.
Click to expand...
Click to collapse
make backup (CWM)
try to find, and flash another kernel- custom,
..that may be a possible fix, for wifi issues,
as that is very often caused by,
not efficient, or completely missing drivers (0kb file size)....
...depending on the RUU version- flashed,
you might be interested in:
http://forum.xda-developers.com/showthread.php?t=1845039
otherwise, try to look for < unity > or < endymion > kernel.....
..Heat might be caused either
by battery,
or CPU - struggling with heavy flaw of graphics, (like < Google Earth >+< Browser >+<anything one prefers > )
or a nasty app ( or several ), constantly trying to consume, most of its resources...
..both quite simple to eliminate...
..and...undervolting, it helps to reduce heat - too...
asgardr said:
make backup (CWM)
try to find, and flash another kernel- custom,
..that may be a possible fix, for wifi issues,
as that is very often caused by,
not efficient, or completely missing drivers (0kb file size)....
...depending on the RUU version- flashed,
you might be interested in:
http://forum.xda-developers.com/showthread.php?t=1845039
otherwise, try to look for < unity > or < endymion > kernel.....
..Heat might be caused either
by battery,
or CPU - struggling with heavy flaw of graphics, (like < Google Earth >+< Browser >+<anything one prefers > )
or a nasty app ( or several ), constantly trying to consume, most of its resources...
..both quite simple to eliminate...
..and...undervolting, it helps to reduce heat - too...
Click to expand...
Click to collapse
I changed the ROM to IceDS v8 which seems to run cooler. I think part of the problem was with Titanium Backup running and the wifi kept searching for a network.
I am still having the wifi problem as it displays 'unable to scan for networks'. Having searched the internet extensively and tried a few different so called fixes I have come to the conclusion it is a hardware problem. When I get time I'll see if I can strip the phone and see if I can find the cause.
lesmorton said:
I changed the ROM to IceDS v8 which seems to run cooler. I think part of the problem was with Titanium Backup running and the wifi kept searching for a network.
I am still having the wifi problem as it displays 'unable to scan for networks'. Having searched the internet extensively and tried a few different so called fixes I have come to the conclusion it is a hardware problem. When I get time I'll see if I can strip the phone and see if I can find the cause.
Click to expand...
Click to collapse
Well I stripped the phone and checked what connections I could but still no wifi.
I have used the RUU to get back to stock ROM and everything is fine except the wifi not working. Does anyone know if the wifi hardware is on the PCB, and if so where it would be in the phone. As the phone is in excellent condition I am thinking of getting a cheap phone with broken screen and just cannibalising it with my phone and building one good phone. It's just knowing what part of the phone contains the wifi hardware.
Any help would be appreciated.
Hi
I was on Maximus, S-off, Unlocked, cid 1111111 and hboot 2.16
Then I flash with the new ruu 4.05.401.1
Before flashing I relocked and flash the stock recovery
The RUU process goes with no problem but after completion the bootloop begins, while sometimes a blackscreen with only a notification bar appears and sometimes a lock screen, but it reboots shortly after that.
I did try with RUU with both relock and unlock, no change.
Any suggestion ??
Same exact issue
Have you gotten anywhere with this? I have the same issue. I unlocked, got s-off with cid '11111111' , and tried a few different custom ROMs. I had problems with signal (voice and/or data) dropping. Tried various radio codes, but problem just got worse. I just want to go back to stock rom, where life is happy (I feel like Dozer in The Matrix. . . Just plug me back in and I don't care if the steak is not real. .. I don't *want* to know)!
Tried relocking and running RUU today, but having exact same issues as OP. I've tried 4 differnt RUUs I've found, all seem to complete successfully, then almost act like they will work, but then boot loop.
ANY SUGGESTIONS?
Thanks in advance!!!
(I have rooted 3 different phones with no issues)
My problem started a week after flashing cm11 to my HTC One S
First the battery would drop from 70% to 0%....a few days later from 100% to 0 just by opening a text message...
Now my battery says 100% and the second i remove it from charging it dies. When i get it back on, it still says 100%
Not only removing the charger but using any app will crash it randomly EVEN WHEN PLUGGED IN!
Currently my phone will not stay on unless plugged in and when i try to use it it crashes
Now (after month and a half of searching) i was finally able to unroot (simply had to lock the bootloader -_-) and run the RUU
Excitedly turned the phone on......and it died.
Cant even finish the initial setup like selecting a language....
Not sure if its the battery or the phone but im sure that ***relocked*** voids warranty so wont be expecting a free replacement
THIS IS A WARNING TO ANYONE ROOTING HTC ONE S....BEWARE OF CM11
but if anyone has any advice it would be much appreciated
I don't think CM11 has anything to do with it...the problem with our phone is that there are a lot of different versions of HBOOT/firmware and many other things so these little details can destroy your phone if you are not careful.
Official CM11, as far as I know, is only for hboot 2.15 (although there is an unofficial release for 2.16)
Which HBOOT are you on?
El Steve said:
(I have rooted 3 different phones with no issues)
My problem started a week after flashing cm11 to my HTC One S
First the battery would drop from 70% to 0%....a few days later from 100% to 0 just by opening a text message...
Now my battery says 100% and the second i remove it from charging it dies. When i get it back on, it still says 100%
Not only removing the charger but using any app will crash it randomly EVEN WHEN PLUGGED IN!
Currently my phone will not stay on unless plugged in and when i try to use it it crashes
Now (after month and a half of searching) i was finally able to unroot (simply had to lock the bootloader -_-) and run the RUU
Excitedly turned the phone on......and it died.
Cant even finish the initial setup like selecting a language....
Not sure if its the battery or the phone but im sure that ***relocked*** voids warranty so wont be expecting a free replacement
THIS IS A WARNING TO ANYONE ROOTING HTC ONE S....BEWARE OF CM11
but if anyone has any advice it would be much appreciated
Click to expand...
Click to collapse
I have run into the same issue. I was on the latest cm11 (on hboot2.16). Now I managed to do full revert to stock RUU. But when the device starts, I can use it for 10 seconds and then it says Android rebooting and it reboots. The phone is not usable anymore....
Currently I have:
S-OFF
CID: HTC__102,
HBOOT-1.13,
Radio 0.16.31501S.17_2
I took this RUU: RUU_Ville_U_HTC_Europe_1.78.401.2_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_258480_signed
First I was on Liberty Sense 6, but had problems with wifi there, so ich switched to CM11 from this thread: http://forum.xda-developers.com/showthread.php?t=2528113
It worked for exactly one day. I only noticed some battery drain. Suddenly after one day it rebooted constantely.
I think something on the hardware side got broken... because as I'm completely on stock now. Everything shudl work
Can someone suggest me something to try, please? I can access fastboot and flash something via ADB Sideload or RUU. But don't know what to try anymore....
UPDATE Ok i found out, that on connecting of the USB cable (PC or charger, different) it reboots. Does anybody know something about this?
Get the newest RUU.
You take the old one.