I am having some problems with ROM's. I can install them just fine, but everything except Fresh is buggy as heck. I am fully rooted with S-Off now but the ROM dates back to when I had S-On. I have tried Viper and a few from OMJ but everything end up being buggy. I even did the stock 4.1 that OMJ posted and the same thing. I've even been considering doing an RUU but keeping S-Off to see if that would help things. I would really like to upgrade to 4.1 but it just drives me nuts with how buggy and slow things become. Using Google Now on the ROM was painful because everything just took so long to open but when i disabled Google Now it was still slow just only slightly faster. I've upgraded to this phone about three months ago so it's fairly new still.
Can anyone help me with this?
TejasEric said:
I am having some problems with ROM's. I can install them just fine, but everything except Fresh is buggy as heck. I am fully rooted with S-Off now but the ROM dates back to when I had S-On. I have tried Viper and a few from OMJ but everything end up being buggy. I even did the stock 4.1 that OMJ posted and the same thing. I've even been considering doing an RUU but keeping S-Off to see if that would help things. I would really like to upgrade to 4.1 but it just drives me nuts with how buggy and slow things become. Using Google Now on the ROM was painful because everything just took so long to open but when i disabled Google Now it was still slow just only slightly faster. I've upgraded to this phone about three months ago so it's fairly new still.
Can anyone help me with this?
Click to expand...
Click to collapse
In recovery what is your wiping process?
Sent from my EVO using Tapatalk 2
thicklizard said:
In recovery what is your wiping process?
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
Recovery: Team Win Recovery Project v. 2.3.1.0
Wipe Cache, Davlik Cache, Factory Reset (figured it couldn't hurt?) System, and even wiped Android Secure (to see if it helped this situation)
What is your baseband? Have you updated firmware? If not that can be the culprit...and also how do you restore,? Use tibu for apps only or are you restoring system data?
Sent from my EVO using xda premium
I forgot to update those things I'll try that. Thanks. I use titanium only for apps not system data.
Appears to have worked. Thank you for reminding me of that. I always did that on my OG Evo but forgot on this phone.
Sent from my EVO
Upgrade your twrp also through goomanager
Sent from my EVO using xda premium
Related
I Was Testing Out A Rom And Decided To Just Restore A Backup Of MeanROM GB. Well The Restore Went Through Perfectly As It Would Many Of Times, But This Time When It Booted Up It Would Stop At The HTC Screen And Cut-Off And Repeat The Process. At First I Was Thinking It Was Just A Problem With The Backup So I Tried Installing A Rom And The Same Thing Happened, Now My Phone Wont Boot. Does Anyone Know Of A Fix For This?:crying:
1. Try taking out the battery for 30 seconds
2.try plugging it in.
If you can get into recovery try factory reset and clearing cache. Let me no what happens
Sent from my Droid using XDA
androidjtc said:
1. Try taking out the battery for 30 seconds
2.try plugging it in.
If you can get into recovery try factory reset and clearing cache. Let me no what happens
Sent from my Droid using XDA
Click to expand...
Click to collapse
Ive Tried And The Same Thing Is Happening
Hmmmm....I really can't think of anything else. I would suggest keep trying to mess around with it and see if you can get it to work. If not, try tomorrow. If you have warrenty and you still can't get your device to work, I would try asking them to send you a new one. But they most likley won't because you rooted it.
Sent from my Droid using XDA
androidjtc said:
Hmmmm....I really can't think of anything else. I would suggest keep trying to mess around with it and see if you can get it to work. If not, try tomorrow. If you have warrenty and you still can't get your device to work, I would try asking them to send you a new one. But they most likley won't because you rooted it.
Sent from my Droid using XDA
Click to expand...
Click to collapse
Thanks For The Help, Maybe I Can Try The RUU Or Un-Rooting Since I Can Get Into Recovery.
Yeah good idea. There's not much else I can think of. Try deleting dalvic cache to. Mess around with it. I hope you get your phone up and running!!!
Sent from my Droid using XDA
androidjtc said:
Yeah good idea. There's not much else I can think of. Try deleting dalvic cache to. Mess around with it. I hope you get your phone up and running!!!
Sent from my Droid using XDA
Click to expand...
Click to collapse
Thanks Im Gonna Try But I Have Insurance On It If Something Goes Wrong.
Alright atleast you have insurance...glad i could help!
Sent from my Droid using XDA
Hopefully I caught you in time before you used the ruu. Did you wipe before restoring your backup? It sounds like you have left over stuff causing issues. Before I restore a backup, I always do a Chad's super wipe first.
Sent from my ICS 3VO with Tapatalk 2
coal686 said:
Hopefully I caught you in time before you used the ruu. Did you wipe before restoring your backup? It sounds like you have left over stuff causing issues. Before I restore a backup, I always do a Chad's super wipe first.
Sent from my ICS 3VO with Tapatalk 2
Click to expand...
Click to collapse
You Did And Ive Tried Wiping x3 Before A Restore And Nothing
Did the new rom update your firmware? I've heard that people on the vm firmware sometimes have issues going back to GB.
Sent from my ICS 3VO with Tapatalk 2
Try a different recovery n flash a fresh ics Rom. I also tried to flash a older gb Rom after upgrading fw n it didn't boot. But I was able to restore my mikrunny backup from a couple months ago n worked.
Sent from my PG86100 using XDA
strive53 said:
Try a different recovery n flash a fresh ics Rom. I also tried to flash a older gb Rom after upgrading fw n it didn't boot. But I was able to restore my mikrunny backup from a couple months ago n worked.
Sent from my PG86100 using XDA
Click to expand...
Click to collapse
Ive Tried New Roms, Both ICS And GB, And None Work.
Upgrading the firmware might cause this try downgrading firmware to correct radio and version. As well as I can confirm that there are issues when trying to downgrade from ICS to GB. Did you try to reinstall the first ROM you were trying out?
I flashed midnight ROM. put the AOSP theme over it. Flashed the newest MAC Kernel, and that's when it started happening.
I decided to factory reset and flash the ROM again, tried to restart. same thing.
restored a backup (after factory restting), no dice.
Wiped boot/data/system, factory resetted, wiped both caches and reflashed midnight ROM. Still nothing.
Tried to flash CM9 (after factory resetting and stuff) and it still won't go past the HTC screen no matter how long I wait.
What's wrong? Am I half bricked?
I'm using the Evo V with S OFF on downgraded HBOOT.
You need to downgrade your radios as well to flash aosp roms. Run an older RUU, which will set you back to stock, flash your recovery and then flash midnight again
Sent from my PG86100 using xda app-developers app
beneath-a-burning-turtle said:
You need to downgrade your radios as well to flash aosp roms. Run an older RUU, which will set you back to stock, flash your recovery and then flash midnight again
Sent from my PG86100 using xda app-developers app
Click to expand...
Click to collapse
I've flashed all these ROMs with no problems before. I already have my radios upgraded (I basically turned my phone into a Evo 3D).
RedDeadDorito said:
I've flashed all these ROMs with no problems before. I already have my radios upgraded (I basically turned my phone into a Evo 3D).
Click to expand...
Click to collapse
Gotta go in the opposite direction with radios, downgrade. It'll make older roms compatible again.
Sent from my PG86100 using xda app-developers app
beneath-a-burning-turtle said:
Gotta go in the opposite direction with radios, downgrade. It'll make older roms compatible again.
Sent from my PG86100 using xda app-developers app
Click to expand...
Click to collapse
So basically, upgrade my HBOOT (since stock is on a upgraded one) again and flash a stock ROM then downgrade again?
I was thinking of doing this, but why did this problem come up in the first place?
I can't do it because I don't have an extra SD card around. If I put the hboot upgrade on my SD card, the bootloader won't start up because it gives you the option to install it or not install and either way, it turns the phone off.
Got it figured out. When I flashed a different kernel, it broke the other kernel or something. I had to flash the ROM's kernel separately. I don't know why.
I'm not sure why, but it did. Anyways, it seems to be working now!
RedDeadDorito said:
Got it figured out. When I flashed a different kernel, it broke the other kernel or something. I had to flash the ROM's kernel separately. I don't know why.
I'm not sure why, but it did. Anyways, it seems to be working now!
Click to expand...
Click to collapse
Glad that you got a solution and that you were also detailed in your response. Perhaps someone in the future that sets aside the time to research and read will be able to either get themselves out of a mess - or - possible avoid one. Cheers!
So, there is nothing magical about super wipe scripts, but this one seems to have had some serious thought put into it.
http://forum.xda-developers.com/showthread.php?t=834812
I usually wipe manually but was curious what you guys do...
Sent from my EVO using xda app-developers app
adma84 said:
So, there is nothing magical about super wipe scripts, but this one seems to have had some serious thought put into it.
http://forum.xda-developers.com/showthread.php?t=834812
I usually wipe manually but was curious what you guys do...
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
There is only one superwipe for our phone. There is nothing to compare it to, and no need as it works fine. The link you posted has nothing to do with our device.
http://forum.xda-developers.com/showthread.php?p=27166189
Ta da!
I've never understood super wipes. I just do it manually.
No need for a superwipe. Just Factory Reset and wipe System and you're ready to flash. That's never once given me a problem.
I use superwipe mod all the time after a manual wipe. Reason because TWRP does not have option to wipe/format the BOOT partition.
Sent from my EVO using xda premium
theoner1 said:
I use superwipe mod all the time after a manual wipe. Reason because TWRP does not have option to wipe/format the BOOT partition.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
You shouldn't have to wipe boot.
SoraX64 said:
You shouldn't have to wipe boot.
Click to expand...
Click to collapse
Exactly I never even heard of a Superwipe until the 3d came out. Never had to flash one since I had my g1 and i'm not going g to start now
Sent from my EVO using xda premium
SoraX64 said:
You shouldn't have to wipe boot.
Click to expand...
Click to collapse
Install any aosp rom, example deck cm10 8-31-12. The Rom have force close issue with the phone process at the beginning. Now if you want to go back to latest sense Rom, without wiping boot img, you will continue to have the same phone process force close issue even if you're on sense Rom. It just happen to me a couple nights ago. So wiping boot partition is my way of completely getting rid of previous issue on the last install Rom.
Sent from my EVO using xda premium
theoner1 said:
Install any aosp rom, example deck cm10 8-31-12. The Rom have force close issue with the phone process at the beginning. Now if you want to go back to latest sense Rom, without wiping boot img, you will continue to have the same phone process force close issue even if you're on sense Rom. It just happen to me a couple nights ago. So wiping boot partition is my way of completely getting rid of previous issue on the last install Rom.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
I can flash between CM and Sense all I want without the error persisting, maybe you're doing something else wrong?
SoraX64 said:
I can flash between CM and Sense all I want without the error persisting, maybe you're doing something else wrong?
Click to expand...
Click to collapse
I was doing something wrong at the time, I forgot to flash the superwipe. When I first booted into meanrom 3.6 the same phone process force close still there. After realizing I forgot to flash superwipe, went back to recovery, wipe completely manually follow by superwipe then install meanrom 3.6, which booted fine without phone process error. Every time I flash a New Rom I always wipe everything at least twice.
Sent from my EVO using xda premium
theoner1 said:
I was doing something wrong at the time, I forgot to flash the superwipe. When I first booted into meanrom 3.6 the same phone process force close still there. After realizing I forgot to flash superwipe, went back to recovery, wipe completely manually follow by superwipe then install meanrom 3.6, which booted fine without phone process error. Every time I flash a New Rom I always wipe everything at least twice.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Are you by any chance 1.15 S-ON?
Because not a week ago I left CM10 for Viper 4G because I needed the camera to work stably, and I did not receive the force close once.
SoraX64 said:
Are you by any chance 1.15 S-ON?
Because not a week ago I left CM10 for Viper 4G because I needed the camera to work stably, and I did not receive the force close once.
Click to expand...
Click to collapse
Nope orginal hboot 1.12 and s-off
Sent from my EVO using xda premium
theoner1 said:
Nope orginal hboot 1.12 and s-off
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Hmm, interesting because I have gone back and forth between CM10 and MeanRom. I have never had an issue. I love the speed and fluidity of CM10 but the Sense camera is just to good at this point.
I have then same issue...if I don't use sw I have issues bouncing between sense and cmx nands.. can't make calls on sense without it..with it I have no issues
firmbiz94 said:
I have then same issue...if I don't use sw I have issues bouncing between sense and cmx nands.. can't make calls on sense without it..with it I have no issues
Click to expand...
Click to collapse
See what I mean, I'm not the only with this issue. Superwipe work wonders for me too.
Sent from my EVO using xda premium
I think a lot of people got used to using these from the og evo. CWM was thought to have trouble wiping so most would wipe two or three times to make sure it didn't miss anything. I haven't heard of that being an issue for a long, long time though.
One thing that it may help with though is if the ROM doesn't format the system partition. I've spent hours trying to track down bugs only to realize leftover system files were wreaking havoc with the new ROM.
theoner1 said:
See what I mean, I'm not the only with this issue. Superwipe work wonders for me too.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Hmm that's interesting, i remember i flashed tranquility rom and was working great! then tested cmx and at the same time tranquility was updated and that error was still present on the new tranquility rom, but i thought it was the rom so i flashed another sense rom but, this time i used superwipe after manually wiping all and no error anymore, since then i didnt use tranquility thinking it was the new update. now i always use superwipe.
time to go back to tranquility :fingers-crossed::fingers-crossed:
Ok, I thought I knew what I was doing. Unfortunately, wine had a factor in my issue... I have a rooted Evo 4g LTE. S-on Hboot 1.15. I was using Clockwork Recovery. I probably should have been using TWRP, from what I've read. When I first got the phone, I was over zealous, and flashed a Mod before saving a recovery. I hated it. So I flashed back to Stock ROM (jewel 1.22.651.3). I wanted to try out a Jelly Bean ROM so I flashed codefireX CM10. It worked but when the phone loaded it kept saying "phone error" and wouldn't let me click okay. So I rebooted into recovery and flashed my previous rom. I was a little tipsy, so I tried it again... It still didnt work... Rebooted into revovery, and this time I cleared cache, cleared davaik cache, and did a factory reset... Then, It wouldn't recover my saved rom. I must have cleared everything again, that I remember, now it won't load into Clockwork. I've tried everything I can think. I tried RUU, No luck. I tried flashing through Fastboot, No luck. Tried Well, I really have researched everything I could think about Boot loops... I'm stuck .... Everything I try seems to have a step missing or issue with my phone because its S-on and I relocked it through abd because RUU needs to be lock on.. I read I may have to flash a new kernel. I'm in over my head. I had to revert to using my Palm Pre. (which I loved for many years, But I really miss my EVO!) PLEASE HELP. :crying:
Check out om4's guide in general, it will tell u all you need to know...good luck.
Sent from my EVO using xda premium
Your issue is that you need a different kernel for CM10, and it needs to pushed in before you flash the ROM(because you're S-on and hboot 1.15).
This will help: http://forum.xda-developers.com/showthread.php?t=1847860
I stopped reading once I read you was using clockwork.
Sent from my EVO using xda premium
shook187 said:
I stopped reading once I read you was using clockwork.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Yeah... I realize now after research... I installed it through ROM manager. Not again. Ugh
shook187 said:
I stopped reading once I read you was using clockwork.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Im now using TWRP. Everythings working again. Thank you.
So now on my evo, every rom i flash gets stuck in bootloop. Ive tried Meanrom,cm10.1,miui, and even the stock roms like JB 4.1. At first my backups would work, but that is no longer the case. Im not sure what else to include. Yes ive factory reset and wiped all cache. Yes i made sure the roms werent corrupt.
I tried using boot img flasher but that did not work.
I have no idea what else there is try.
Htc Evo 4g LTE
S-on RL
HBOOT- 1.19.0000
RADIO-1.12.11.0809
OpenDSP-v29.1.0.45.06.22
eMMC-boot
Rooted.
TWRP - 2.3.3.0
Maybe downgrade/upgrade your recovery. Some phones are having issues with newer or older twrp releases.
Good luck man
Edit....... Just saw your running 2.3.3.0
I would try upgrading to a newer version
Sent from my EVO using xda premium
Try a fresh install wipe cache/dalvik cache /factory reset/system then try to install the rom
Sent from my PoS MoPho
corcgaigh said:
Maybe downgrade/upgrade your recovery. Some phones are having issues with newer or older twrp releases.
Good luck man
Edit....... Just saw your running 2.3.3.0
I would try upgrading to a newer version
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Thanks for the reply, ill try this first thing in the morning
bigdaddy619 said:
Try a fresh install wipe cache/dalvik cache /factory reset/system then try to install the rom
Sent from my PoS MoPho
Click to expand...
Click to collapse
Sadly , as many times as ive tried this, it hasnt worked
I no longer have any recovery at all. While following the boot loader method of updating Twrp found here. Bah, im not allowed to post links.
I just dug myself deeper into the hole it seems, Last thing in the world i want to do right now is have to pay lots of money to fix my mess
EDIT: I was able to get TWRP working again. Phew. Still have a alot of progress to make
ANOTHER EDIT: Out of some miracle, wiping everyhting for the 034612093612903126th time and then flashing worked, Superjelly booted and everything... Oh my god im relieved.
Close thread/delete thread
Sukhol said:
I no longer have any recovery at all. While following the boot loader method of updating Twrp found here. Bah, im not allowed to post links.
I just dug myself deeper into the hole it seems, Last thing in the world i want to do right now is have to pay lots of money to fix my mess
EDIT: I was able to get TWRP working again. Phew. Still have a alot of progress to make
ANOTHER EDIT: Out of some miracle, wiping everyhting for the 034612093612903126th time and then flashing worked, Superjelly booted and everything... Oh my god im relieved.
Close thread/delete thread
Click to expand...
Click to collapse
I'm having basically the exact same issues you had. Do you mind shedding some light my way? I've been in a soft brick for a while now. Although I almost had a rom go through, until my touchscreen was unresponsive (i think due to my bootloader showing S-ON and not S-OFF). I can access the bootloader and TWRP. I have no backups (this is my first time rooting and flashing, in case you haven't noticed). I don't know how to take the S-OFF or recover the old Sense 4 stock os. At this point i really would just like to use my phone. Any guidance would be greatly appreciated!
JosephAndrew said:
I'm having basically the exact same issues you had. Do you mind shedding some light my way? I've been in a soft brick for a while now. Although I almost had a rom go through, until my touchscreen was unresponsive (i think due to my bootloader showing S-ON and not S-OFF). I can access the bootloader and TWRP. I have no backups (this is my first time rooting and flashing, in case you haven't noticed). I don't know how to take the S-OFF or recover the old Sense 4 stock os. At this point i really would just like to use my phone. Any guidance would be greatly appreciated!
Click to expand...
Click to collapse
Check PM