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
Related
Hi, I instilled TWRP 2.3.3.0, after wipe everything and tried to flash any custom rom i would get stuck on the boostscreen, Tried a different version of TWRP and the samething kept happening to me, big thanks if anyone could help!
One more thing, I could not flash any kernel as well, it would stuck at some % forever, i checked SuperSu everything rooted and unlock..Don't know why
Try this out?
http://forum.xda-developers.com/showthread.php?p=33303798
Hope it helps. Also make sure you have a Onex evita
Sent from my One X using xda premium
hboot
Are you on hboot 1.14? If so, the issue with not being able to flash kernels, etc. is normal. All you need to do is extract the boot.img from the rom or kernel you want to flash and flash it via fastboot or an app called "Flash Image GUI".
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
The dialer app is not working at all I can't receive calls nor can I make calls it says "Unfurtunately, the process com.android.htcdialer has stopped" and this just hapens on sense ROMS on every of them, the aosp ones work just great but I want sense right now (Magio ROM R3.6.1) Does anybody knows how to fix this?
remulacha said:
The dialer app is not working at all I can't receive calls nor can I make calls it says "Unfurtunately, the process com.android.htcdialer has stopped" and this just hapens on sense ROMS on every of them, the aosp ones work just great but I want sense right now (Magio ROM R3.6.1) Does anybody knows how to fix this?
Click to expand...
Click to collapse
are you wiping everything before flashing the sense rom?
Try fastboot command:
fastboot erase cache
Then wipe cache in TWRP.
Sent from my Evita
This is a bug from going from touch cwm to twrp
You can either reflash cwm and stay on it or reflash cwm then flash a non touch cwm then flash twrp. Using fastboot erase cache after every recovery flash.
Sent from my HTC One X using xda app-developers app
exad said:
This is a bug from going from touch cwm to twrp
You can either reflash cwm and stay on it or reflash cwm then flash a non touch cwm then flash twrp. Using fastboot erase cache after every recovery flash.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
I will try to flash cwm thanks
exad said:
This is a bug from going from touch cwm to twrp
You can either reflash cwm and stay on it or reflash cwm then flash a non touch cwm then flash twrp. Using fastboot erase cache after every recovery flash.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
I nkow this is an old post. I hit the thanks button; clearly not enough so I had to post to say it.
THANK YOU!!!!!!
I know it sounds dumb but I search for 2 days before I found this and it work 100%!!! My phone is 100% working again! I can't thank you enough; I was really worried I messed it up because I had tried a "german 4.2.2" on it. It seemed laggy slow* wonder if that would be the recovery. But I got the RUU from HTC for my phone (4.1.1) done that and poof nothing working(your fix worked). still debating on trying the 4.2.2 again. It is nice has some cool features. But I know 4.1.1 works great.
Sorry got of track. THANKS AGAIN!
Hi there,
I am currently installing Cyanogenmod 10.1 for my HTC Sensation. I'm stuck in the blue circle loading screen. (image below)
I don't know what should I do.
Help will be highly appriciated.
Sent from my HTC One using xda app-developers app
idomohr25 said:
Hi there,
I am currently installing Cyanogenmod 10.1 for my HTC Sensation. I'm stuck in the blue circle loading screen. (image below)
I don't know what should I do.
Help will be highly appriciated.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
probably you are on S-ON am i right?
if yes use 4ext recovery
enable smatflash from it
flash the rom
done
otherwise flash the boot.img of the rom via fastboot command
My device is S-OFF.
I am trying to flash firmware again, and clear cache and dalvik.
idomohr25 said:
My device is S-OFF.
I am trying to flash firmware again, and clear cache and dalvik.
Click to expand...
Click to collapse
Most of the time there is no need to re-flash firmware. Did you wipe data beforehand? maybe you can try another build (the from an earlier/later date). This might help.
Sometimes a complete wipe is needed...
Hi,
Sometimes when moving from one ROM to another a complete wipe and format of all partitions (except sdcard) is needed in order for it to work. Have you wiped and formatted all your partitions before flashing the ROM? I use Titanium pro to backup my apps before doing this.
You should be able to do this with any of the recovery programs. 4EXT is really good and easy to use for this. Also, if you don't already know this, you should flash the correct GAPPS for your ROM after you install the update. That way you will have everything you need on your first boot after your flash.
Good luck!
when i updated my firmware from 3.32 to 3.33 i got stuck at the same screen. Just booted to recovery and used 4EXT Recovery touch to wipe cache and dalvik, after that everything was fine
I currently can't use my usb port to receive data, so adb isn't an option.
I'm looking to flash the new PAC rom, and need to update my TWRP recovery from 2.6.0.0 to 2.7.0.8. I'm using HBOOT 2.19 if that makes a difference?
I want to use Flashify to do this as its my only option without using adb that I can see.
Has anyone here had experience using this? If it doesn't work I don't have any other way of restoring my recovery and my phone will dead weight.
Also will updating my recovery wipe the sdcard? I hope not as I need the rom file to survive to be able to bring my phone back to life, as sideload won't work for me.
Thank you for any help received on this.
Sent from my GT-I9000 using xda app-developers app
i could be wrong mate but I'm sure I've read you can get ADB to work over WiFi, think you have to enable it in developer options.. surely there is a tutorial kicking around someplace on XDA.
flashing new recovery.img shouldnt wipe. only Unlocking the bootloader, super wipe, flashing a ruu, factory reset - they all wipe the phone
ill have a look about and get back to you
**UPDATE**
Found this amongst many other tutorials, not sure if it will work but worth a try
http://forum.xda-developers.com/showthread.php?t=2570432 apparantly he has updated it to http://forum.xda-developers.com/showthread.php?t=2707556
there is also a twrp manager app (by jmz) on playstore, i think you can flash a new recovery direct fom the app ????
I had problems flashing a boot.img via flashify. Flashed successfully but got problems later. flashed via fastboot and everything was fine.
Many thanks for the input. Will try this when I get my phone back from HTC.
@Braddison
Can you flash recoveries thru the android os over adb? Thought you had to do that thru hboot.
@theodorius123
What exactly did you try to flash with Flashify?
Sent from my GT-I9000 using Xparent Red Tapatalk 2
no idea what it was exactly, only know that it was a boot.img - as i wrote before
Not sure, but check out jmz app on play store.... Twrp manager I think you can do it from that or try goo manager, also on play store. i'm sure you can flash new recoveries directly from within these apps?
Good luck
twrp = https://play.google.com/store/apps/details?id=com.jmz.soft.twrpmanager
goomanager = https://play.google.com/store/apps/details?id=com.s0up.goomanager
again not sure as i haven't tried them myself
Or this one: http://forum.xda-developers.com/showthread.php?t=2730305
Ah! Forgot about the aroma recovery installer. That's a great option. Then it should just be a matter of flashing rom. Are you s-off? If so shouldn't need to flash boot. Img afterward
I am s-off. Think the aroma installer is my best bet. But I may not bother just because its to much of a risk without being able to use fastboot to restore things in case something goes wrong...
Bloody HTC.
Sent from my GT-I9000 using Xparent Red Tapatalk 2