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.
Related
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:
I was on speed rom 7.5, but i liked the way cm10 looked so I wiped my data and all that and flashed it. My phone hasn't done anything but stay on the cyanogen rotating thing for like 15 minutes. Please help. (Ps. I was dumb and didnt make a nandroid backup -_-)
Ventus_zx said:
I was on speed rom 7.5, but i liked the way cm10 looked so I wiped my data and all that and flashed it. My phone hasn't done anything but stay on the cyanogen rotating thing for like 15 minutes. Please help. (Ps. I was dumb and didnt make a nandroid backup -_-)
Click to expand...
Click to collapse
Im not an expert, but did you create a backup? or try wiping twice over and re-installing.
Need a littlemore information. Are you s-off? What recovery are you using?
Sent from my HTC_Amaze_4G using xda app-developers app
xndabox said:
Need a littlemore information. Are you s-off? What recovery are you using?
Sent from my HTC_Amaze_4G using xda app-developers app
Click to expand...
Click to collapse
Im using 4EXT And I am not S-OFF
Wow it bootlooped all night ;(
Ventus_zx said:
Im using 4EXT And I am not S-OFF
Wow it bootlooped all night ;(
Click to expand...
Click to collapse
same thing happened to my phone with CM 10, so i ended up instaling the android revolution rom for the time being.
What recovery are you using? Use 4ext if you aren't, try again, if it loops more than once, you either forgot to wipe before install or you need to flash the kernel manually.
Sent from my SGH-T999 using xda app-developers app
I was on speed rom 7.5, but i liked the way cm10 looked so I wiped my data and all that and flashed it. My phone hasn't done anything but stay on the cyanogen rotating thing for like 15 minutes. Please help. (Ps. I was dumb and didnt make a nandroid backup -_-)
Click to expand...
Click to collapse
I also had a problem when I flashed Speedrom but with versions 6.5 which I had previously working perfectly but then decided to switch to SS3 and then switch back. Now I also had the bootloop issue thing where the thing would just keep spinning. So I re-flashed SS3 with the faux kernel and then just did the two things:
4EXT Recovery btw
Wipe data/factory reset
Clear dalvik cache
Then install the rom and once done, go back to menu and reboot from recovery. It should tell you that the previously used boot.img will be used (that is what I get when I flash my roms and they work perfectly).
+1 is this helped!
Thanks it worked! Though I switxhed back to speed rom lol
Sent from my HTC Ruby using xda premium
Nice! And no problem, just happy your phone's back to normal! =)
Hello,
I am fairly noobish when it comes to phones but I have had a rooted OG EVO and now i have had a rooted EVO LTE. When i first rooted my LTE i flashed the meanbean rom and then a few months after that i decided to try out other roms suchs as CM10, Paranoid, and maybe a few others that didn't last too long. I just tried to go back to meanbean and it loaded about 75% and was just stuck. I let it sit there for about 45 minutes and nothing ever happened. I forced a restart and restored to a previous backup. When my phone booted up I noticed that it was acting funny and I later found out that some how my internal storage device was messed up. I eventually mounted my phone to my computer in TWRP and reformated so it now works as it should. I went to try and flash meanbean and it again freezes at the same spot. When i try to flash another ROM my phone beings to flash it and then it will randomly restart back into recovery. I have no idea why it is doing this. I tried to run my phone's RUU but my computer wont find my phone connected to it. When i try to use HTC Sync it also will not find my phone.
Sorry for the wall of text but at this point I am wanting to just start over completely fresh bc i feel that all of this flashing, restoring, and reformatting has really messed up my phone. Currently my phone has issues with it's calls. I sound as though i am very far away and I have never had this problem before so i am not sure where that issue is coming from.
If anyone has any kind of advice on what I should do please please help me! I can post any kind of information or clarification that is needed.
Thanks a ton in advanced!
Are you on newest version of twrp??
Sent from my EVO using xda premium
mrlakadaddy said:
Are you on newest version of twrp??
Sent from my EVO using xda premium
Click to expand...
Click to collapse
I am not. When i try to flash the newest version from bootloader it says, "Current version is newer" (or something similar to that) and then it will just boot loop in bootloader until i delete the zip from the sdcard.
Download goomanager from the market and use option to install open recovery script
Sent from my EVO using xda premium
wow. didn't realize i could do that from goomanager! thanks a ton ill post back with results soon.
seems to be working perfectly! thank you so much.
You're welcome
Sent from my EVO using xda premium
Hello, so recently I tried to get S-OFF on my Evo through JuopunutBear. Something went wrong and I (mistakenly ) unlplugged the USB cable. Now my phone only boots up onto Bootloader. I can't access the recovery nor can I access adb. The only thing that works is fastboot. Can someone please help me? I have no idea what to do and after hours of searching, nothing like this has ever happened before I assume. I'm sort of a noob. I have adb installed and can use it but I don't know what commands to enter or what files to download or what. Is there any way I can reset my phone or get out of this bootloop? Thank You guys!
duscdragon said:
Hello, so recently I tried to get S-OFF on my Evo through JuopunutBear. Something went wrong and I (mistakenly ) unlplugged the USB cable. Now my phone only boots up onto Bootloader. I can't access the recovery nor can I access adb. The only thing that works is fastboot. Can someone please help me? I have no idea what to do and after hours of searching, nothing like this has ever happened before I assume. I'm sort of a noob. I have adb installed and can use it but I don't know what commands to enter or what files to download or what. Is there any way I can reset my phone or get out of this bootloop? Thank You guys!
Click to expand...
Click to collapse
Use fastboot to flash a recovery. From recovery flash a ROM. Try that.
Sent from my HTCEVOV4G using xda app-developers app
kevin130 said:
Use fastboot to flash a recovery. From recovery flash a ROM. Try that.
Sent from my HTCEVOV4G using xda app-developers app
Click to expand...
Click to collapse
Hey, Thanks for telling me that. But I'm kind of a noob. Can you show me a download link of 4EXT (or whatever one you think is best) and what command I should use?
http://androidforums.com/evo-v-4g-all-things-root/626186-easy-guide-get-out-bootloops.html
Sent from my Nexus 7 using xda app-developers app
OK. So I looked into the guide, One of the attachments had a broken link so I couldn't do it. I tried flashing a stock RUU but it gave me an error. I tried getting the rom.zip from the temp and flashing that. My bootloader gave me an error and said something about the version being older than the firmware or something like that. I have finally gotten to my recovery, but that did not help. I've cleared EVERYTHING. Now I'm stuck in a bootloop where when the phone boots up it goes straight into JBear phone image with the arrow. I've tried everything. I still have no idea how to fix it. I really need some help.
duscdragon said:
OK. So I looked into the guide, One of the attachments had a broken link so I couldn't do it. I tried flashing a stock RUU but it gave me an error. I tried getting the rom.zip from the temp and flashing that. My bootloader gave me an error and said something about the version being older than the firmware or something like that. I have finally gotten to my recovery, but that did not help. I've cleared EVERYTHING. Now I'm stuck in a bootloop where when the phone boots up it goes straight into JBear phone image with the arrow. I've tried everything. I still have no idea how to fix it. I really need some help.
Click to expand...
Click to collapse
Try doing the wire trick again,
Sent from my Nexus 7 using xda app-developers app
duscdragon said:
OK. So I looked into the guide, One of the attachments had a broken link so I couldn't do it. I tried flashing a stock RUU but it gave me an error. I tried getting the rom.zip from the temp and flashing that. My bootloader gave me an error and said something about the version being older than the firmware or something like that. I have finally gotten to my recovery, but that did not help. I've cleared EVERYTHING. Now I'm stuck in a bootloop where when the phone boots up it goes straight into JBear phone image with the arrow. I've tried everything. I still have no idea how to fix it. I really need some help.
Click to expand...
Click to collapse
Try again from begining. Read and be carefully. See here http://forum.xda-developers.com/showthread.php?t=1813818.
bilbaro said:
Try again from begining. Read and be carefully. See here link?t=1813818.
Click to expand...
Click to collapse
Thanx for the help guys! Well, I fixed the bootloop and screen by flashing the boot.img. That got me stuck in an HTC logo bootloop, but I WAS SO HAPPY. I HAVE NEVER BEEN HAPPIER SEEN A BOOTLOOP THAN THIS. Well, since I knew how to fix this, I just flashed a stock ROM, and from there installed TWRP recovery and from there flashed a custom ROM (rooted, deodexed, stock, since I still don't have S-OFF). Now I'm just restoring my apps from Carbon( Helium) and getting some new themes. Thanks Guys!:laugh::laugh::laugh::laugh:
Just a heads up. The Evo V 4G seems to operate better when 4EXT recovery is used!
Sent from my Evo 3D CDMA using xda premium