Hello everyone!
I'm one of the unfortunate few with an S3 chip in my HTC One S.
Thanks to developers like torxx, at least we have a TrickDroid ROM specifically made for our VilleC2 devices.
I wanted to find out if it is possible to flash stock recovery after flashing a custom ROM?
My bootloader is unlocked and I used Paul's Superboot method to root my phone. Thereafter I flashed TWRP 2.2.2.1 and left it as is since there were essentially no custom ROMs available for the VilleC2 devices at the time.
After using the phone I noticed a recurring issue with the battery, it would go gray with the "!" mark on it and would jump from 10% to 50% when I reboot the phone. Battery calibration did not solve this issue.
I successfully flashed TrickDroid 1.0 but this did not fix the battery issue either.
So I relocked my bootloader today and reloaded the RUU. The battery issue seems to have gone away, didn't get a single gray "!" occurence for the past 4 hours (and keeping fingers crossed that it doesn't occur again!).
I surmised it could be TWRP causing my battery mis-calibration and so was wondering if it was possible for me to re-root, flash TWRP, flash TrickDroid, then flash stock recovery over TWRP.
I'm very new to all this, so any advice at all would help!
Thanks in advance!
Related
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!
Hey there,
I have an interesting problem, and it has completely stumped me for the past couple days. I recently S-Off'd my Sensation, put cwm recovery on it, and set my CID to 11111111.
I haven't had any problems with that (except that I had to change computers to do it, Revolution didn't want to run right on my laptop or set the CID, so I had to use my desktop).
Now the problem comes when I try to flash a custom ROM. The first one I tried flashing was CM7. When it booted, I got a bootloop problem of the CM7 mod logo over and over. I decided maybe it was a problem with CM7 still being in alpha. Then I tried flashing HyperSensation 1.8, and got the same error (bootloop) on the loading screen. After trying various other ROMS, I realized that it was a common problem with all custom ROMS. Luckily I had backed up the stock setup, and was able to get into that. So it's not a problem with the hardware. I have only tried flashing gingerbread ROMS. I know that ICS ROMS need a new firmware, but I dont want to mess with that unless I can actually get a gingerbread ROM working first...
Any ideas? There was a thread or two about this (on other phones) but didn't have any solutions listed..
Thanks for any ideas people can give me!
TheLastGringo said:
Hey there,
I have an interesting problem, and it has completely stumped me for the past couple days. I recently S-Off'd my Sensation, put cwm recovery on it, and set my CID to 11111111.
I haven't had any problems with that (except that I had to change computers to do it, Revolution didn't want to run right on my laptop or set the CID, so I had to use my desktop).
Now the problem comes when I try to flash a custom ROM. The first one I tried flashing was CM7. When it booted, I got a bootloop problem of the CM7 mod logo over and over. I decided maybe it was a problem with CM7 still being in alpha. Then I tried flashing HyperSensation 1.8, and got the same error (bootloop) on the loading screen. After trying various other ROMS, I realized that it was a common problem with all custom ROMS. Luckily I had backed up the stock setup, and was able to get into that. So it's not a problem with the hardware. I have only tried flashing gingerbread ROMS. I know that ICS ROMS need a new firmware, but I dont want to mess with that unless I can actually get a gingerbread ROM working first...
Any ideas? There was a thread or two about this (on other phones) but didn't have any solutions listed..
Thanks for any ideas people can give me!
Click to expand...
Click to collapse
Hi,
Did you root your phone?
Did you flash the superwipe zip first?
Also are you getting full reboots with HTC splash screen then animation or just the animation looping? Sometimes I have to let mine loop for 5 minutes after first boot of new rom before it settles.
Sent from my Sensation XE using XDA App
I guess I hadn't done everything.. I didn't factory reset before flashing the new ROM... As soon as I did that it boot right in. That's a bit odd to me, as I didn't have to do that with my last phone.
Anywho, solved.
Sent from my Sensation using XDA App
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!
So I have been running Slimbean 4.3 beta for the past couple days, it's been running pretty smooth except that when I accidentally let the battery die when it boots up the first time after a charge it locks up at boot at "Android is upgrading" and so I have decided to flash a couple custom kernels to see if it will help solve this problem. Although I heard mike is working on a solution for this? Hopefully haha..anyways. This is the first rom I have tried flashing a different kernel on this device. Anyways the first kernel I tried flashing was jriors Torch and it seemed to have booted up fine after the reboot from recovery but the boot animation was orange and after a while it locks up with a grey bar over it, with "Android is upgrading:" written on it in pink. I then proceeded to recovery clean wiped reflashed slimbean and tried flashing the one that came out last night I think...aznrice's evita boosted7 and I got the same result. So then I decided to try carbon and both kernels worked perfectly with it. So is this just a Slimbean problem? or am I missing something? I'm S-off, Hboot 2.14, TWRP 2.6.3
Sorry for the bulky post first time poster long,long,long time reader haha
Thanks
Those kernels aren't compatible with Slimbean, there currently aren't any custom kernels that are compatible with it.
Sent from my Evita