I'm new to this site, if I'm doing anything noob-esque, let me know.
So I got SunShine, really happy with the purchase on the license because now I can actually use my phone the way I want. That aside, I really wanted to put Android Revolution HD on it because of the HTC Sense-ness incorporated and it seemed like the ROM that would have best suited me. All day I've been tinkering with my phone to get it to work, but no avail. Everytime I reboot after flashing, it just stays on the "HTC One" logo screen. I know you're supposed to wait longer on the first boot, but after waiting several times (twice I waited an hour), it was easy to see something wasn't working. So now I have PAC ROM on there just so I can actually use my phone until I figure out how to do this. PAC ROM works just fine with flashing, so does Cyanogenmod. Even though they are great ROMs, I want ARHD most on my phone. Can anyone tell me what I've done wrong, because I'm not sure what I'm looking for. I was running stock 4.4.3 when I went to flash it. That's what it said to have on the guide, which is why I don't understand what the problem is. I tried ViperOne; the same thing happened - stayed on boot logo. But again, Cyanogenmod and PAC ROM flash no problem.
Related
I've searched the forums relentlessly with no luck. I rooted, installed some roms, tried to install Cyanogens latest rom, became stuck on the bootup screen for 30 minutes. Tried to wipe and reinstall and I get the same thing. Well now the boot screen comes up and the phone powers down automatically after about 5 seconds. I cant get to bootloader either. I'm worried it's really done now. Sorry in advance for being a dumb noob but if anyone could help i'd really appreciate it. Btw, I have a mytouch 3g.
Ok. I got to the bootloader and reinstalled the last working (hero) rom I had. It appears to be loading now. I still would like to change this rom as I really need bluetooth support but after that scare, I'm not sure what I did wrong. I was under the impression Cyanogen's ROMs were fairly simple to load. Sorry if this is not thread worthy but I've had this phone less than a week and if I brick it, my wife will kill me!
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
I have an HTC Sensation which i S-Off'ed , rooted, and installed vanilla CM9.1 on last Friday. And for the past 3 days, it's been having TERRIBLE random battery drainage, and even turns off on it's own (which is really annoying me). I've had these problems on and off when i was using the original Stock ROM, so i thought that installing CyanogenMod 9.1 would fix it, but NOPE, it just wouldn't let me go. I have ClockWorkMod Recovery (the latest version) and i have wiped the battery stats, wiped dalvik cache, formatted the system partition, reset the phone, heck i even re-downloaded and re-installed the WHOLE thing over and over again, and it STILL can't set itself straight.
Can anybody help meh?!
By the way, i don't keep Wi-Fi always on, and i have no Mobile Data plan, so that's not on, plus i really don't use the phone every-day, which negates the possibility that my usage is the fault. And i checked online for help, one way was to update the firmware, didn't work. Another way was to put cut a part of a business card or paper and just stick it above the battery to hold it in place, which didn't work when i was on stock so I'm not trying that again (Also, HTC, if you're reading this, you made a beautiful phone with the Sensation.... SO WHY U HEFF TO GIFF ME TRABBOL?)
Something else to be noted is that i used the SAME methods and files on my bro's phone and his is perfect, although my guess is that it might be something to do with the fact that my phone was a Vodafone UK branded one and his was completely unbranded one....
Also, I'm trying to get my hands on an Anker battery, but until I get it, I've only got you all, so help me...... pretty please? lol....
moanismk said:
I have an HTC Sensation which i S-Off'ed , rooted, and installed vanilla CM9.1 on last Friday. And for the past 3 days, it's been having TERRIBLE random battery drainage, and even turns off on it's own (which is really annoying me). I've had these problems on and off when i was using the original Stock ROM, so i thought that installing CyanogenMod 9.1 would fix it, but NOPE, it just wouldn't let me go. I have ClockWorkMod Recovery (the latest version) and i have wiped the battery stats, wiped dalvik cache, formatted the system partition, reset the phone, heck i even re-downloaded and re-installed the WHOLE thing over and over again, and it STILL can't set itself straight.
Can anybody help meh?!
By the way, i don't keep Wi-Fi always on, and i have no Mobile Data plan, so that's not on, plus i really don't use the phone every-day, which negates the possibility that my usage is the fault. And i checked online for help, one way was to update the firmware, didn't work. Another way was to put cut a part of a business card or paper and just stick it above the battery to hold it in place, which didn't work when i was on stock so I'm not trying that again (Also, HTC, if you're reading this, you made a beautiful phone with the Sensation.... SO WHY U HEFF TO GIFF ME TRABBOL?)
Something else to be noted is that i used the SAME methods and files on my bro's phone and his is perfect, although my guess is that it might be something to do with the fact that my phone was a Vodafone UK branded one and his was completely unbranded one....
Also, I'm trying to get my hands on an Anker battery, but until I get it, I've only got you all, so help me...... pretty please? lol....
Click to expand...
Click to collapse
LOL...CM 9??? You should give CM 10.1 or CM 10 a try, but you have to update the firmware first. Did you follow the directions here: http://forum.xda-developers.com/showthread.php?t=1459767
If you flash firmware 3.33 you can flash CM 10/10.1
If you want a super rock solid ROM i would try Bruce's CM 10 here: http://forum.xda-developers.com/showthread.php?t=1782009
CM 10.1 is here: http://forum.xda-developers.com/showthread.php?t=1782009
ARHD (ICS) is awesome also: http://forum.xda-developers.com/showthread.php?t=1098849
Although I've never tried CM 9, CM 10/10.1 should be a huge update. I think it should improve battery life as well.
Thanks for the help
AndroidSupporter318 said:
LOL...CM 9??? You should give CM 10.1 or CM 10 a try, but you have to update the firmware first. Did you follow the directions here: http://forum.xda-developers.com/showthread.php?t=1459767
If you flash firmware 3.33 you can flash CM 10/10.1
If you want a super rock solid ROM i would try Bruce's CM 10 here: http://forum.xda-developers.com/showthread.php?t=1782009
CM 10.1 is here: http://forum.xda-developers.com/showthread.php?t=1782009
ARHD (ICS) is awesome also: http://forum.xda-developers.com/showthread.php?t=1098849
Although I've never tried CM 9, CM 10/10.1 should be a huge update. I think it should improve battery life as well.
Click to expand...
Click to collapse
So, I've tried the CM10.1 ROM by albinoman887, and everything's perfect so far!
No random turn-off's, smooth as HELL, and a long battery life... (and did i mention Google Now? )
Thanks a lot bro......
If anything new comes up i'll be sure to share it on here...
I'm really glad you like it
Sent from my HTC Sensation
crazy touchscreen problem
After flashing a ROM my touchscreen x axis seems to have inverted itself, so right is left on the screen.
This problem happens during the recovery screen also
I have tried changing recovery's,Kernals,flashed ROM's that I know work
I have even returned the phone back to stock nothing fixed it.
I have even went as far as removing the motherboard and installing one out of a working phone and guess what it does the same thing.
So i ask all you knowledgeable people WTF wold cause this and how can I fix it ?
these are the last two ROM's I was trying out when all this happened
they both ran without a problem I just didn't like them
MokeeOS 44.2 24/12/2013 [UNOFFICIAL],
UNOFFICIAL AOKP][4.4.2] [S4] [12/26/13]
I'm in no way blaming the ROM developers for this issue I just need a little help
Strange problem. I think you should flash firmware, it is worth to try i guess
Sent from my One S using xda app-developers app
mines actually doing the same, and from what i've been reading, i believe it has to do with your hboot version and ics not being compatible with it. try flashing your original ruu if you can. that's what i'm trying to do as we speak. if i ever get my problem figured out, i'll let you know if it works.
HomieOneKinobi said:
mines actually doing the same, and from what i've been reading, i believe it has to do with your hboot version and ics not being compatible with it. try flashing your original ruu if you can. that's what i'm trying to do as we speak. if i ever get my problem figured out, i'll let you know if it works.
Click to expand...
Click to collapse
This was my test phone I had flashed just about everything you can think of before I would install it on the phone I use every day
I guess my luck ran out
I ended up flashing the phone back to the original firmware and OS version using the factory RUU without a problem
If I try to install anything over 4.04 it goes right back to the same crap
I tried different firmware, kernels, roms with sense/ no sense doesn't matter.
the phone is being sold as I type this and I'm leaving my other two One S phones alone for now on
Nobody should have to go through this much bull for newer OS version so I'm saving for a Nexus 5
Thank you for the suggestion
From the beginning.
Unlocked
EVITA PVT SHIP S-ON RL
HBoot 1.14.002
Radio 0.19as.32.09.11_2
OpenDSP v29.1.0.45.0622
eMMC-boot
June 11 2012, 14:36:28
Click to expand...
Click to collapse
I was running a ViperRom my camera light was staying on, I tried everything to get it to turn off. I decided it been a few month it was time to get a new ROM anyways. I tried installing Gummy Nightly's was having problem with the install read about getting a different version of TWRP so I updated to 2.6.3.0 I believe I had 2.1.0.0. Gummy still won't work, so I changed plans and want for the Viper XL Rom 4.2.0 this led to a bootloop not getting past the Viper splash screen. I thought I might as well just with one of my backup. So, i wiped and loaded a backup. This is the problem, it will load up the ROM for about 30 seconds before the icon all appear it will reboot. I've now been working on this for 2 days. I've went through each post and tried the advice each person was given, I've tried to Flash a different Rom, the Viper Rom I had when I had the Camera Light Issue, each time I get about 30 second into the Rom Load and reboot. (One of the ROMs would let me access the SDCARD0 but found a work around that.) I've let the phone sit charged for 2 hours looping. I've turn it off and let it sit charging. The next thing I'm going to try to to downgrade the TWRP. If anyone can give me some advice, something new and different to try that would be great. Thanks!
Cheers
xDrFirefly
talked to one of my buddy and said the downgrade would be pointless so, i'm trying to flash a stock rom at the moment.
When you changed to TWRP 2.6.3.0 was it the official version or the unofficial modified version?
Sent from my Evita
Recovery: Custom TWRP 2.6.3.0 w/selinux support
And what errors did it give you when trying to install Gummy?
Sent from my Evita
The install failed. I tried it multi times, and even d/l it again to see if that would make a difference. Nope.
Here is what i've done so far. I factory reset everything. Found a stock rom flashed it on. For the two hours I used it seemed to work fine. I then flashed CleanRom everytime I would open Ti Backup the phone would reboot. I flashed another ROM, was getting the signal drop snagged the Beastmode Kernel it keep failing everytime I tried to flash it. Factory Wiped EVERYTHING again. Flashed the Stock, then Flashed ViperXL (then went to bed) in the morning still had signal bars, so far had two reboots, one when I was uninstalling apps using Manage apps feature, and another time when I was in the Venom HUB app. But at the moment the phone seems to be working. The battery life is ****. In the 30 mins I've had the phone unplug i've down to 89% and all I did was delete a few apps, and move some stuff to the home screens. Hopefully it will get better with time.
Side Note: To anyone reading this. I got the AT&T HTC XL preorder. I doubt I will ever do that again. In all the years I've been flashing and messing with phone. ( My first phone I messed with was a Sidekick ) I've never had so much trouble as I had with this phone. ( HTC Tilt, Fuze and Tilt 2 never had this kinda problem ) a friend of mine whom waited a year to get the XL has never had any of the problem I've had. Just my thoughts. Thanks and I hope I won't have to be asking anymore question.
When, I have more time and such I'm going to try to flash Gummy. If I get the same error message for it or anything else I will post it here.
Cheers
-Dr FF
I get that it failed, I asked what error you got. Your battery life on Viper will improve, just let the ROM settle in for a few days. I've had this phone since just after release and I've never had a single problem with it, not one. There are quirks that come with any device but if you do the proper research and know what you're doing you shouldn't have issues.
Sent from my Evita
You might also want to try setting a fresh install up without restoring any apps or installing any social networking apps. Those are possibly the worst for fc's, random reboots, and bad battery life. At least for me that's how it is.
jacobas92 said:
You might also want to try setting a fresh install up without restoring any apps or installing any social networking apps. Those are possibly the worst for fc's, random reboots, and bad battery life. At least for me that's how it is.
Click to expand...
Click to collapse
I will try this. Sounds like a very logical plan.
timmaaa said:
I get that it failed, I asked what error you got. Your battery life on Viper will improve, just let the ROM settle in for a few days. I've had this phone since just after release and I've never had a single problem with it, not one. There are quirks that come with any device but if you do the proper research and know what you're doing you shouldn't have issues.
Sent from my Evita
Click to expand...
Click to collapse
Timmaaa I just get annoyed how easy this phone get caught in bootloops. That is really my main complaint. I know it's trivial. -- I really don't know what caused the fail when I tried to install Gummy. I wiped and tried it a few time and I keep getting failed. I normally try twice then find something else. To quote Little Britain "Computer says no".
xdrfirefly said:
Timmaaa I just get annoyed how easy this phone get caught in bootloops. That is really my main complaint. I know it's trivial. -- I really don't know what caused the fail when I tried to install Gummy. I wiped and tried it a few time and I keep getting failed. I normally try twice then find something else. To quote Little Britain "Computer says no".
Click to expand...
Click to collapse
Computer always says no for a reason. You need the right recovery installed to flash KitKat ROMs, you also need to check the md5 of every ROM you download before you flash it. What I'm saying is there's no reason Gummy wouldn't install if you have done everything correctly.