Hey guys, I'm new but have been reading these forums for a while. I've rooted and unlocked 3 phones of mine with no problems but My HTC Evo LTE was ready for an upgrade so I tried to install a new rom, in the process I accidentally erased my back up. I have apps and system back up on titanium. I've read the don't panic thread, nothing helped. I've tried flashing the kernel and just about everything I know how to do.
So right now I have an unlocked device Jewel S-on, hboot 1.12, radio 1.02.12.0427 with TWRp Recovery installed. I have tried Vipers jellybean rom, Mean Rom ICS, and and a rooted stock rom.
All do the same thing, TWRP starts installing the rom and then it reboots real quick before the bar gets to 1/2, it reboots in the HTC quietly brilliant screen and the bar in the upper right goes up twice and then it just freezes and sits on the screen forever until i power it down and reboot into bootloader and nothing is installed. any ideas?
What version of twrp are you using?
You may not have the latest twrp recovery. Older versions will reboot or fail on install. There have been a few changes to the installers, especially with son users since hboots have become more restricted
bigdaddy619 said:
What version of twrp are you using?
Click to expand...
Click to collapse
Let's see, I'm running.....TWRP 2.4.1.0
mxbmx930 said:
Let's see, I'm running.....TWRP 2.4.1.0
Click to expand...
Click to collapse
download this and try 2.3.1.0 http://d-h.st/R9E
2.4.1.0 does not work properly unless you are using a 3.16 rom with updated binaries and you have the latest firmware installed
Glad I decided to hold off on updating twrp then
om4 said:
Glad I decided to hold off on updating twrp then
Click to expand...
Click to collapse
There is nothing wrong with the latest twrp, but the rom you are installing has to be compatible with it. The newest MeanBean is. It's kind of funny that the op has the most out of date phone firmware you can have but somehow updated his twrp to the newest available.
Sent from my icrap 2 using Tapatalk HD
bigdaddy619 said:
download this and try 2.3.1.0
2.4.1.0 does not work properly unless you are using a 3.16 rom with updated binaries and you have the latest firmware installed
Click to expand...
Click to collapse
Wow, so easy. I can't believe I spent all those hours frustrated trying to figure what I was doing wrong. I put 2.3.1 on and first try, installed fine. I have one more question, I downloaded titanium to reinstall everything and it's saying ERROR: I could not acquire root privileges, this app will not work. I installed Viperboys Stock Rooted 3.15.651.16 deodexed and SU is on there, I even updated it. Any ideas?
thanks a lot for the help so far.
cruise350 said:
There is nothing wrong with the latest twrp, but the rom you are installing has to be compatible with it. The newest MeanBean is. It's kind of funny that the op has the most out of date phone firmware you can have but somehow updated his twrp to the newest available.
Sent from my icrap 2 using Tapatalk HD
Click to expand...
Click to collapse
I usually wait at least a week to see if any problems come up
Related
Yesterday my phone started to act up so I restarted it and it won't boot ever again. I wasn't able to get to the recovery either. So I relocked and did a ruu and I updated to the latest version. I flashed amon recovery and started to flash different roms like dev CleanROM and rooted 4.03 stock(I did the root fix and flash the image) . After initial setup all I get was reboot. I then flashed CleanROM 3.7 that is in my sd card. It's working fine now. BTW all flashes were done before a full wipe not with the tool but in the amon recovery. I don't know what's causing the reboot problem. I don't see any topics related to this, there might be some posts related to this. But please link me to me if you can. And also the fix would be nice.
Thank you in advance
If this has been answered before sorry
About it
Sent from my ADR6425LVW using xda premium
pagereborn said:
Yesterday my phone started to act up so I restarted it and it won't boot ever again. I wasn't able to get to the recovery either. So I relocked and did a ruu and I updated to the latest version. I flashed amon recovery and started to flash different roms like dev CleanROM and rooted 4.03 stock(I did the root fix and flash the image) . After initial setup all I get was reboot. I then flashed CleanROM 3.7 that is in my sd card. It's working fine now. BTW all flashes were done before a full wipe not with the tool but in the amon recovery. I don't know what's causing the reboot problem. I don't see any topics related to this, there might be some posts related to this. But please link me to me if you can. And also the fix would be nice.
Thank you in advance
If this has been answered before sorry
About it
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
What did you have on your phone to begin with when this problem started?
Which RUU did you flash? Sounds like maybe you did GB which would explain why CR3.7 works, and not 4.1.
Something you can try if you want is try the patch that has been posted letting phones on the original firmware run ROMs dev'ed for the new one.
Also check your HBOOT and check those versions.
Also could be bunk downloads of the newer ROMs. Have you tried re-downloading. Might be a good idea after checking all the other things.
I have just recently received my replacement evo after smashing my old one. The phone was already fully upgraded to the latest JB software and hboot 2.09. The first thing i did was S-OFF using the DirtyRacun method all went well except for a few user errors but eventually achieved S-OFF. After that was done i installed TWRP recovery v2.3.3.0. After flashing Viper Rom my phone had random reboots spanning from minutes apart to a few hours apart. I redownloaded the same rom wiped everything again and the problem stayed consistent. so i decided to switch roms and tried PACman aokp rom and the same problem exist there also. is this a hardware issue or a result of an error during S-OFF? i have a couple logs from the app "Bootlog Uptime" if that may be of any assistance.
S-OFF using DirtyRacun
HBoot 2.09
TWRP v2.3.3.0
Roms Tried: Viper Rom and PACman aokp
Stock kernels
logs attached.
Try the latest TWRP?
... Sent from my 'Oops! Should've bought the S3!' via XDA-Developers App.
Delakit said:
Try the latest TWRP?
... Sent from my 'Oops! Should've bought the S3!' via XDA-Developers App.
Click to expand...
Click to collapse
I've heard nothing but bad things about the latest TWRP such as the touch screen not working so i decided it would be best to just stay away from it.
kcdre said:
I've heard nothing but bad things about the latest TWRP such as the touch screen not working so i decided it would be best to just stay away from it.
Click to expand...
Click to collapse
Try twrp 2.4.1.0 all my firmware including the touch panel drivers and have zero issues
Sent from my PoS MoPho
bigdaddy619 said:
Try twrp 2.4.1.0 all my firmware including the touch panel drivers and have zero issues
Sent from my PoS MoPho
Click to expand...
Click to collapse
I guess i could try updating the recovery and flashing again but ive never had this problem previously with 2.3.3.0. I just want to be sure its not hardware related before the return window closses for me to return this device for a new one.
I updated my recovery to the latest version and did a fresh install of viper rom and just had another random reboot. starting to think the problem is hardware related. ill have a log attached and hopefully someone will have a little insight on what's going on.
kcdre said:
I updated my recovery to the latest version and did a fresh install of viper rom and just had another random reboot. starting to think the problem is hardware related. ill have a log attached and hopefully someone will have a little insight on what's going on.
Click to expand...
Click to collapse
Post the log in the Viper thread, unless you've already done so. One of the devs will be able to take a look at it and hopefully be able to tell you what the problem is.
Sent from my EVO using xda premium
I'm running s-off and latest twrp recovery. haven't flashed anything in a while, thought I'd update rom ( superjelly) and power menu option for reboot to recovery simply reboots phone. choosing to reboot into boot loader works but recovery is no longer listed there. phone has been rooted with custom recovery for a long time, flashed many roms... kind of out of the blue issue. think hboot version is 1.12...
Therr have been a few issues with the latest twrp, not like this from what ive read tho. Try flashing an earlier version. Ive been running 2.3.3.0 for quite some time with no issues at all. Worth a shot.
*Information IS the most dangerous weapon of all*
When you reboot to the bootloader screen, what happens when you select the bootloader option? Does the recovery option appear, or what happens?
Sent from my EVO using xda premium
drlzanej said:
Therr have been a few issues with the latest twrp, not like this from what ive read tho. Try flashing an earlier version. Ive been running 2.3.3.0 for quite some time with no issues at all. Worth a shot.
*Information IS the most dangerous weapon of all*
Click to expand...
Click to collapse
This is a bad recommendation if you are on the latest firmware. You won't be able to use this twrp version. Download quickboot from the app store and use this to enter recovery if you can't get into it the traditional method.
cruise350 said:
This is a bad recommendation if you are on the latest firmware. You won't be able to use this twrp version. Download quickboot from the app store and use this to enter recovery if you can't get into it the traditional method.
Click to expand...
Click to collapse
??? Im on the latest firmware and useing it with no issues at all.
drlzanej said:
??? Im on the latest firmware and useing it with no issues at all.
Click to expand...
Click to collapse
Not the complete firmware, the touch panel drivers are not compatible with any version of twrp older than 2.4.0.
Sent from my icrap 2 using Tapatalk HD
I flashed an earlier version of twrp, 2.3.1.0 I think it was and works fine now. thanks for all the recommendations
Hello everyone,
So the One Max I got has got into boot loop after flashing a rom using TWRP 2.7.1.1, I'm not sure "why" this happened, I did everything correctly.
Stupid enough, I flashed TWRP 2.7.1.1 again to try and re flash rom using a new recovery, yet the boot loop didn't work, but my backups were gone, and the rom was gone.
i go the rom on my laptop.
HOWEVER, what I really want is stock RUU for the HTC One Max which supports arabic language.
- Tell me how to find which ruu this phone originally had
- I want everything back to stock.
- I want to know how to do that on my laptop.
- I need to make sure the fingerprint will be working, so will it work when i flash back stock RUU and relock?
PampaZiya said:
Hello everyone,
So the One Max I got has got into boot loop after flashing a rom using TWRP 2.7.1.1, I'm not sure "why" this happened, I did everything correctly.
Stupid enough, I flashed TWRP 2.7.1.1 again to try and re flash rom using a new recovery, yet the boot loop didn't work, but my backups were gone, and the rom was gone.
i go the rom on my laptop.
HOWEVER, what I really want is stock RUU for the HTC One Max which supports arabic language.
- Tell me how to find which ruu this phone originally had
- I want everything back to stock.
- I want to know how to do that on my laptop.
- I need to make sure the fingerprint will be working, so will it work when i flash back stock RUU and relock?
Click to expand...
Click to collapse
Are you Sprint or intl? Also, switch back to using 2.7.1 without the extra .1. That will prevent the bootloops.
dottat said:
Are you Sprint or intl? Also, switch back to using 2.7.1 without the extra .1. That will prevent the bootloops.
Click to expand...
Click to collapse
I tried flashing with 2.7 the NusenseSix rom but it kept "failed" and I'm an international HTC One Max
PampaZiya said:
I tried flashing with 2.7 the NusenseSix rom but it kept "failed" and I'm an international HTC One Max
Click to expand...
Click to collapse
Find and use 2.7.1 not 2.7.1.1
dottat said:
Find and use 2.7.1 not 2.7.1.1
Click to expand...
Click to collapse
sorry i meant 2.7.1 ,... 2.7.1 didnt work.. it kept saying failed
PampaZiya said:
sorry i meant 2.7.1 ,... 2.7.1 didnt work.. it kept saying failed
Click to expand...
Click to collapse
Well twrp 2.8 is now out to try...
I flashed demon dust Rom a couple weeks ago and wanted to reflash cm11. I got the status 7 in cwm and error executing binary script updater in TWRP. I have flashed RUU twice and tried different recovery versions but I keep getting the same errors... Any suggestions???
I switched to twrp and had the same issue, and when I switched back to clockwork mod everything was fine again. You might be having the reverse effect happening. I am on VZW as well.
Sjflowerhorn said:
I switched to twrp and had the same issue, and when I switched back to clockwork mod everything was fine again. You might be having the reverse effect happening. I am on VZW as well.
Click to expand...
Click to collapse
Thanks for replying, but i have been switching back and forth between recoveries and nothing is working
herzig.grant said:
Thanks for replying, but i have been switching back and forth between recoveries and nothing is working
Click to expand...
Click to collapse
I tried to look this up in Google and no one really has or had the same issue as me
if you have been trying the newest versions have you tried older versions or vice versa?
And are you flashing the recovery in adb using fastboot or using an app from the market? I finally had success using Rashr from the market since my laptop recently had the battery go and I still haven't unpacked my desktop since moving recently.
herzig.grant said:
I flashed demon dust Rom a couple weeks ago and wanted to reflash cm11. I got the status 7 in cwm and error executing binary script updater in TWRP. I have flashed RUU twice and tried different recovery versions but I keep getting the same errors... Any suggestions???
Click to expand...
Click to collapse
Were you using Fly's version of TWRP?
bfisch3r said:
Were you using Fly's version of TWRP?
Click to expand...
Click to collapse
I wasnt at the time.. But i figured out the problem yesterday. Guess i forgot to close this
herzig.grant said:
I wasnt at the time.. But i figured out the problem yesterday. Guess i forgot to close this
Click to expand...
Click to collapse
Ok, glad you got it figured out. Was the version of TWRP the issue?
bfisch3r said:
Ok, glad you got it figured out. Was the version of TWRP the issue?
Click to expand...
Click to collapse
Yeah i was using the non aosp friendly version.... Lol i can be such a n00b sometimes
Thread has been closed at OP's request.
Stephen