[Q] Ugh - having problems installing cleanrom - AT&T, Rogers HTC One X, Telstra One XL

Background details. I have TWRP 2.4.4.0 installed, rooted, S-OFF. I had Viper XL installed, but wanted to try a stock JB rom. I downloaded CleanROM, booted into recovery. From here:
-wiped cache
-wiped dalvik cache
-System reset
-wiped system
From here, I go to install CleanROM. It runs aroma installer, I choose my options, and follow on screen prompts. It seems to flash too quickly (like it's not installing). It says successful, and gives me the option to go home, wipe cache/dalvik, or reboot. If I click reboot, it says No OS installed, are you sure you want to reboot?
I tried rebooting, and it stops in the white bootup screen. Not sure what step I am missing here. I didn't think that I needed to flash boot.img since I have S-OFF, but is that the case? Any help would be great - THANKS!

opto_isolator said:
Background details. I have TWRP 2.4.4.0 installed, rooted, S-OFF. I had Viper XL installed, but wanted to try a stock JB rom. I downloaded CleanROM, booted into recovery. From here:
-wiped cache
-wiped dalvik cache
-System reset
-wiped system
From here, I go to install CleanROM. It runs aroma installer, I choose my options, and follow on screen prompts. It seems to flash too quickly (like it's not installing). It says successful, and gives me the option to go home, wipe cache/dalvik, or reboot. If I click reboot, it says No OS installed, are you sure you want to reboot?
I tried rebooting, and it stops in the white bootup screen. Not sure what step I am missing here. I didn't think that I needed to flash boot.img since I have S-OFF, but is that the case? Any help would be great - THANKS!
Click to expand...
Click to collapse
Flash twrp 2.3.3.1 and reflash rom. Also verify md5 of Rom download. And if you want a great jb Rom give magio Rom a run. It's my daily driver and is amazing
Sent from my HTC One XL using xda premium

THANKS! That seemed to work. Why do some roms work with newer versions of TWRP, and some do not? That's odd. I installed Viper XL with 2.4.

opto_isolator said:
THANKS! That seemed to work. Why do some roms work with newer versions of TWRP, and some do not? That's odd. I installed Viper XL with 2.4.
Click to expand...
Click to collapse
All versions of twrp past 2.3.3.1 have issues. Be it wiping or flashing on the evita.
And if it helped just hit the thanks button
Sent from my HTC One XL using xda premium

31ken31 said:
All versions of twrp past 2.3.3.1 have issues. Be it wiping or flashing on the evita.
And if it helped just hit the thanks button
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
This.... Reflash 2.3.3.1 or previous. Had ypur issue months back, drove me balls crazy for a few weeks.
Sent from my HTC One XL using xda premium

Related

[Q] Why did I get stuck while trying to install Viper?

Earlier, I tried installing ViperXL 2.1.0 ROM, wiped the cache, system, and factory restored in TWRP.
When I was installing the ROM, it got stuck at 90%, so I just gave up. This is my first android phone in two years, so I am just
starting to get use to ROMs again.
visualizeit said:
Earlier, I tried installing ViperXL 2.1.0 ROM, wiped the cache, system, and factory restored in TWRP.
When I was installing the ROM, it got stuck at 90%, so I just gave up. This is my first android phone in two years, so I am just
starting to get use to ROMs again.
Click to expand...
Click to collapse
Do it again. I had that happen to me once.
Reboot into recovery, Wipe System/Factory reset and reflash.
If you rooted from 2.20 flash the boot.img first
Could also be a corrupt zip. Chrome used to do that to me.
Sent from my One X using xda premium
Just flashed again and this time it was successful.
Unchecked the exchange mail mod because that is what it froze at earlier.
Vioe does that to ne often. It hangs at 90%. Then I simply reboot to twrp and flash again and it works without modifying anything.. it's weird
sent from my venom injected, blazingly fast as f#&k OneXL via xda premium
The problem is either related to TWRP or Aroma. I'm pretty sure all ROMs that use Aroma experience this, although I don't think I've had it happen to me since installing TWRP 2.3.1.0 (at least, from what I remember)
Rebooting back into recovery and reflashing usually works, no matter what the selection is.

[Q] Cyanogen Mod 10 - Spinning Circle - Nothing Else

Just flashed CyanogenMod10 on my HTC ONE X Rogers and it's stuck on the spinning circle.
Anyone able to help with this?
So far I've:
Flashed the boot using Hasoon2000's tool.
Flashed the boot manually
Cleared cache
Re-tried to install the rom in recovery.
Wiped then tried.
nothing working.
Killustration said:
Just flashed CyanogenMod10 on my HTC ONE X Rogers and it's stuck on the spinning circle.
Anyone able to help with this?
So far I've:
Flashed the boot using Hasoon2000's tool.
Flashed the boot manually
Cleared cache
Re-tried to install the rom in recovery.
Wiped then tried.
nothing working.
Click to expand...
Click to collapse
Try taking the boot.IMG from the previous version and flashing via fastboot. Then do a clean install.
Sent from my One X using xda app-developers app
Its accepting it correctly with fast boot?
Sent from my Liquidy Smooth, blazingly fast as f#(k HTC OneXL.
Rogers Onex do not require the ROM boot being done separately, our hboot allows such.
Unless you have a hboot higher then mine at 1.11?
If so disregard my post.
WR
Sent from my HTC One X
Killustration said:
Just flashed CyanogenMod10 on my HTC ONE X Rogers and it's stuck on the spinning circle.
Anyone able to help with this?
So far I've:
Flashed the boot using Hasoon2000's tool.
Flashed the boot manually
Cleared cache
Re-tried to install the rom in recovery.
Wiped then tried.
nothing working.
Click to expand...
Click to collapse
Which CM10 ROM did you flash? If you flashed the stable ROM, then the boot.img from that ROM should work fine. If one of the nightlies from around the first week of November, you'd have to flash a boot.img from an older nightly like 10/27. Needless to say, you should be flashing the stable or one of the more recent nightlies.
If coming from a non-CM10 ROM, you should do a full wipe i.e. factory reset, cache, dalvik. Then flash boot.img. Then wipe dalvik and cache again, then flash ROM via recovery.
WarRaven said:
Rogers Onex do not require the ROM boot being done separately, our hboot allows such.
Unless you have a hboot higher then mine at 1.11?
If so disregard my post.
WR
Sent from my HTC One X
Click to expand...
Click to collapse
Not sure if hboot is different, but I know Rogers users don't need to flash kernel separately.
OP: How long did you let it sit at the spinning circle? I have seen up to 5 minutes on first boot
area51avenger said:
Not sure if hboot is different, but I know Rogers users don't need to flash kernel separately.
OP: How long did you let it sit at the spinning circle? I have seen up to 5 minutes on first boot
Click to expand...
Click to collapse
Sorry, guess I wasn't clear enough in my post, I am using a Rogers XL on Hboot 1.11.
I was just trying to get op to see, there's no image flash required unless he somehow had a newer hboot then mine which I'm pretty sure is not possible on our Rogers XLs.
WR
Sent from WR's OneXL

Aroma installer issue after s-off

After I obtained s-off I have been having a strange issue where anything using aroma that I flash comes up with a turquoise overlay the entire time and I get install failed each flash, but it seems to fail after everything finalizes and the roms or kernels appear to flash successfully, I haven't had any issues so far.
I guess the question would be, is there a way to clear anything related to aroma? I don't know if it stores something on the sd somewhere, but it remembers my options each time I flash something so it must be stored somewhere
Sent from my HTC One X using Tapatalk 2
probably not, with all the recovery changes and stock jb ota. i would say only use twrp 2.3.3.1 or official cwm. also if you have jb make sure to downgrade your touch panel firmware. anytime you change recovery make sure to "fastboot erase cache" then rewipe cache in recovery that can fix alot of recovery issues. also make sure to wipe everything when changing roms. what rom are you try to flash and what recovery are you using?
I flashed twrp 2.3.3.0 and all is good again. Thanks!
Sent from my HTC One X using Tapatalk 2

[Q] Sense ROM's break my dialer...

I've tried everything I can think of...
1. I have done a full format of the phone and tried both CWM, TWRP (2.3.3 and newest version).
2. I've tried using Calkulin's Format All and then reinstalling using TWRP.
3. I've tried every other tip I've read on this forum but, no matter what I do, every time I do a clean install of a Sense Rom (Hatka or Viper)...the dialer just does not work. I tried wiping the dialer's cache and installing after market dialers too. When I install an after market dialer...contacts crash instead of the dialer and I still cannot make a call.
Oh, and lastly, CM Rom's work fine.
Anything else I can try? Really frustrating.
THANK YOU!
Drew489 said:
I've tried everything I can think of...
1. I have done a full format of the phone and tried both CWM, TWRP (2.3.3 and newest version).
2. I've tried using Calkulin's Format All and then reinstalling using TWRP.
3. I've tried every other tip I've read on this forum but, no matter what I do, every time I do a clean install of a Sense Rom (Hatka or Viper)...the dialer just does not work. I tried wiping the dialer's cache and installing after market dialers too. When I install an after market dialer...contacts crash instead of the dialer and I still cannot make a call.
Oh, and lastly, CM Rom's work fine.
Anything else I can try? Really frustrating.
THANK YOU!
Click to expand...
Click to collapse
You did try "fastboot erase cache" while in fastboot, didn't you? The only other thing I did was erase my sdcard.
Yes I would do what was mentioned previously, stay on twrp 2.3.x and I would wipe cache, dalvik, system, and factory reset after fastboot erase cache.
Then reflash the rom. That should fix you up. Also if you're restoring apps, don't. Just in case you're restoring the dialer by mistake.
Sent from my One X using xda app-developers app
lol, had some spare time today so I tried again. Wiped EVERYthing, formatted card, fastboot cache wiped twice. installed again 3.2.6 again...dialer broken. I cannot figure this one out. :/
Drew489 said:
lol, had some spare time today so I tried again. Wiped EVERYthing, formatted card, fastboot cache wiped twice. installed again 3.2.6 again...dialer broken. I cannot figure this one out. :/
Click to expand...
Click to collapse
There has to be some variable your screwing up.. I've used both and have a very temperamental XL... No over or under clock or crash... But a dialer issue? Try a dirty flash? Redownload Rom?
Sent from my HTC One XL using xda app-developers app
I've done everything like that...I cannot figure it out. The ONLY variable I'm seeing is, no matter what wiping I do, with all the tools and things mentioned above...the elemental boot screen always comes up. Is there a way to really format even deeper using ADB?
S-off if you're not already and ruu. Let me know if it still happens
Sent from my One X using xda app-developers app
Ok fixed it...
Here's how.
Installed latest TWRP and Viper 3.2.6
Dialer broken.
Then installed ROM Manager and latest non touch CWM.
Installed Viper update 3.2.7
Profit.
Everything works fine now. No idea why though.
Sent from my HTC One X using Tapatalk 2
Drew489 said:
Ok fixed it...
Here's how.
Installed latest TWRP and Viper 3.2.6
Dialer broken.
Then installed ROM Manager and latest non touch CWM.
Installed Viper update 3.2.7
Profit.
Everything works fine now. No idea why though.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
Swipe navigation based CWM works also. It seems to be just the touch version that's tainted.

Trouble getting Miui to boot....again

Okay so Im trying to install miui v5 but im having isuues getting it to boot...again. ok so when v4 3.2.22 first came out I couldnt get it to boot. I would install the rom, then gapps and could not get it to boot past the optimizing apps screen. it would just stay at starting apps. I was told by another user to flash rohans kernel version b5 as that has worked for him on a different rom, and it worked for me. Now trying to install V5 its been a nightmare. when just installing the rom, then gapps I could not get it to boot past the splash screen. it would load it for a second then just go to a black screen. I then tried installing rohans kernel version b5 but now I get stuck at the starting apps screen I tried wiping cache and dalvik and that did nothing. tried installing different kernels and most I tried wouldnt let me get past the boot animaion Im using twrp 2.3.1.0, Im s-off and I even tried lowering my hboot from 1.14 to 1.09 just incase that might be it but nope. im no sure what else to do and help would be greatly appreciated
avery.0 said:
Okay so Im trying to install miui v5 but im having isuues getting it to boot...again. ok so when v4 3.2.22 first came out I couldnt get it to boot. I would install the rom, then gapps and could not get it to boot past the optimizing apps screen. it would just stay at starting apps. I was told by another user to flash rohans kernel version b5 as that has worked for him on a different rom, and it worked for me. Now trying to install V5 its been a nightmare. when just installing the rom, then gapps I could not get it to boot past the splash screen. it would load it for a second then just go to a black screen. I then tried installing rohans kernel version b5 but now I get stuck at the starting apps screen I tried wiping cache and dalvik and that did nothing. tried installing different kernels and most I tried wouldnt let me get past the boot animaion Im using twrp 2.3.1.0, Im s-off and I even tried lowering my hboot from 1.14 to 1.09 just incase that might be it but nope. im no sure what else to do and help would be greatly appreciated
Click to expand...
Click to collapse
Wipe everything. Install your rom only. Does it boot?
exad said:
Wipe everything. Install your rom only. Does it boot?
Click to expand...
Click to collapse
no. It loads the splash screen for a second then goes to a black screen.
You've verified the md5 right?
Boot to bootloader/fastboot and do fastboot erase cache in command prompt then wipe everything cache, dalvik, system, factory reset, then flash rom.
Does it boot?
Sent from my HTC One X using xda app-developers app
exad said:
You've verified the md5 right?
Boot to bootloader/fastboot and do fastboot erase cache in command prompt then wipe everything cache, dalvik, system, factory reset, then flash rom.
Does it boot?
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
redownloaded 3 times. erased cache. wiped everything and same problem as before loads splash screen then back screen
Redownloading != checking md5 you could Redownload 500 times and all 500 downloads could have corruption of some sort.
You did fastboot erase cache?
If you're positive your download is good and after fastboot erase cache and wiping everything isn't working. Your last step is to s-off if you're not already and ruu to the latest version then flash twrp then wipe everything then flash the rom.
Sent from my HTC One X using xda app-developers app
exad said:
Redownloading != checking md5 you could Redownload 500 times and all 500 downloads could have corruption of some sort.
You did fastboot erase cache?
If you're positive your download is good and after fastboot erase cache and wiping everything isn't working. Your last step is to s-off if you're not already and ruu to the latest version then flash twrp then wipe everything then flash the rom.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Just making sure since I have only researched slightly, since im s-off If i run the latest unrootable RUU Id still be able to unlock bootloader and regain root?
What other roms have you tried to flash? Is Mui the only ones giving you problems? Try other ones to see if it is not a bad twrp. It may not be wiping correctly.
Sent from my HTC One X using xda premium
Venomtester said:
What other roms have you tried to flash? Is Mui the only ones giving you problems? Try other ones to see if it is not a bad twrp. It may not be wiping correctly.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
every other rom ive flashed boots fine its only miui that gives me problems. It boots for other people fine so I dont think its the rom and I tried to install on CWM and still have issues
I had the same problem with Chameleon. Took four different downloads to get it. Avatar took a few too lol. Take above advice. Check sum. Might even try wiping cache in adb.
Sent from my HTC One X using xda premium
Venomtester said:
I had the same problem with Chameleon. Took four different downloads to get it. Avatar took a few too lol. Take above advice. Check sum. Might even try wiping cache in adb.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
noob question but how do I find the md5?
avery.0 said:
noob question but how do I find the md5?
Click to expand...
Click to collapse
Search MD5 Sum Checker. It's a program that is pretty self explanatory and will check it for you. The MD5 is attached to the download. You copy it from the site and past it in the checker.
And after you s-off you don't need to re lock to ruu so you won't lose bootloader unlock
Sent from my HTC One X using xda app-developers app
Running the 3.18 RUU fixed my problems. Thank you both for the help
Sent from my HTC One X using xda premium

Categories

Resources