I have a rooted and soff EVO LTE and in wanting to up to 4.3 ROM I understand I need to update my bootloader. When I try loading a couple 4.3 roms my phone starts ups but reboots after displaying the HTC white logo screen.
I currently have hboot 1.19.0000 and if I understand correctly I need to update to 2.10 It also has Team Win Recovery 2.2.1 which I'm not sure if that needs updating or not.
It has been awhile since I rooted or updated anything and when I did in the past I followed instructions for the entire root process so I'm a little stuck in getting things patched up.
Can anyone offer me the path to proceed? I'm only messing with my old phone as I plan to reactivate it as I'm having terrible issues with my new HTX M8 in not having any data nor able to make calls (due to the Spark support in my local towers throwing chucks since Sprint doesn't have their towers upgraded yet.
Perhaps I should ask, am I on the right path in needing to update my hboot to update to 4.3?
eBoyDog said:
I have a rooted and soff EVO LTE and in wanting to up to 4.3 ROM I understand I need to update my bootloader. When I try loading a couple 4.3 roms my phone starts ups but reboots after displaying the HTC white logo screen.
I currently have hboot 1.19.0000 and if I understand correctly I need to update to 2.10 It also has Team Win Recovery 2.2.1 which I'm not sure if that needs updating or not.
It has been awhile since I rooted or updated anything and when I did in the past I followed instructions for the entire root process so I'm a little stuck in getting things patched up.
Can anyone offer me the path to proceed? I'm only messing with my old phone as I plan to reactivate it as I'm having terrible issues with my new HTX M8 in not having any data nor able to make calls (due to the Spark support in my local towers throwing chucks since Sprint doesn't have their towers upgraded yet.
Perhaps I should ask, am I on the right path in needing to update my hboot to update to 4.3?
Click to expand...
Click to collapse
I think never mind, after more reading I believe my problem is I don't have s off which appears to be required, let me get that done and I will see were I'm at......
You can run the RUU for the latest update (Android 4.3). That will get you the latest bootloader and put you on the new partition layout, also. You will only be able to flash ROM's based on the new layout. You'll need to update your recovery version, also. For the RUU click the top link in my sig and scroll down to the bottom of the first post. You'll need to relock your bootloader to run the RUU. Running the RUU does not require S-off and there are instructions in the post I mentioned that detail how to run the RUU.
You should also read the first several posts in the thread linked below:
http://forum.xda-developers.com/showthread.php?t=2639180
Sent from my HTC M8
Related
Just as the title asks. I have run into a problem with my Evo 4G LTE when installing CM10.
first i ended with no service and couldn't activate, then firmware hardbrick. WilI take the phone to the sprint store later today, but i'll still be attempting this when I get it fixed/replaced. took the following steps:
0. phone activated at store
1. Regaw unlock/recovery/root
-at this point assumed CM10 needed s-off due to being JB instead of ICS or something
-went to unlimited.io's lazypanda. says needs stockruu 1.13
2. stock 1.13 ruu
3. regaw unlock again
4. feedpanda
5. CM10
Either before or after CM10, i PJ75IMG.zip'd the most recent radio. i feel the biggest issues were cause by my installing new radio, which lost me service, then trying to roll back to the old radio which bricked my phone. I'm pretty sure my biggest fault was messing with firmware stuff to begin with but just to be sure I'd like anyone's opinion on anything I should be doing because I obviously have no idea what I'm doing. Thanks for any replies.
Flashing radios is the #1 way to brick your phone. Your best bet is to do some more homework on phone flashing. Read, read, read and ask questions before you dive in head first. Since the newest hboots can be s-off'd, just update the phone while it is stock that way the firmware will be the newest. When you get the phone back, see what h-boot and software version it has and go from there.
Hello all,
I am brand new to the android community, and have come accross a problem that I can't seem to get fixed. I previously rooted/rom'd my EVO lte with mean rom a while back. I started to have wireless issues so I decided to spend some time learning/fixing the problems that I'm sure my noobness created.
I relocked my phone and unrooted it back to factory 2.13.651.1. After doing that I updated my phone via Sprints OTA updater. I recieved an update that took me to 3.16.561.3. After that was completed I preceeded to unlock my bootloader again and installed TWRP 2.4.1.0. When I try to install any ROM it appears to go well in TWRP, but it reboots right after it says "updating kernel, this may take a while". When it reboots it sits at the HTC white startup screen, it doesnt even flash the red developer letters under the HTC logo like it normally does when continuing to boot into recovery or the old ROM.
I did some search and have found that others had issues with TWRP 2.4.1.0 (http://forum.xda-developers.com/showthread.php?t=2048229&page=573). They rolled back to 2.4.0.0. The problem is that with the OTA update the touch sence in TWRP is broken unless you run 2.4.1.0.
Anyone else run across ths issue?
The solution is probably staring me in the face but my noob aura is blocking it. :silly:
TWRP 2.4.1.0 broke something with flashing so you might have to relock and ruu to get back to normal. The problem is there is no ruu out for 3.16 and running the ruu for 3.15 may mess up your phone. I would try to flash the kernel separately by flashing with fastboot or flashgui and see if that allows it to boot into the rom. You may be able to run dirty racun and gain s-off since the hboot didn't change with the latest update.
Waterheeter said:
Hello all,
I am brand new to the android community, and have come accross a problem that I can't seem to get fixed. I previously rooted/rom'd my EVO lte with mean rom a while back. I started to have wireless issues so I decided to spend some time learning/fixing the problems that I'm sure my noobness created.
I relocked my phone and unrooted it back to factory 2.13.651.1. After doing that I updated my phone via Sprints OTA updater. I recieved an update that took me to 3.16.561.3. After that was completed I preceeded to unlock my bootloader again and installed TWRP 2.4.1.0. When I try to install any ROM it appears to go well in TWRP, but it reboots right after it says "updating kernel, this may take a while". When it reboots it sits at the HTC white startup screen, it doesnt even flash the red developer letters under the HTC logo like it normally does when continuing to boot into recovery or the old ROM.
I did some search and have found that others had issues with TWRP 2.4.1.0 (http://forum.xda-developers.com/showthread.php?t=2048229&page=573). They rolled back to 2.4.0.0. The problem is that with the OTA update the touch sence in TWRP is broken unless you run 2.4.1.0.
Anyone else run across ths issue?
The solution is probably staring me in the face but my noob aura is blocking it. :silly:
Click to expand...
Click to collapse
So u was on 3.16 and unlocked it? Did u use dirty racun? Did it work? Sorry I accepted ota and want s-off rooted if possible.
Sent from my EVO using xda app-developers app
polar2792 said:
So u was on 3.16 and unlocked it? Did u use dirty racun? Did it work? Sorry I accepted ota and want s-off rooted if possible.
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
I didnt use dirty racun to unlock, I used the fastboot method. I'm not developed enough in my knowledge to be s-off atm.
cruise350 said:
TWRP 2.4.1.0 broke something with flashing so you might have to relock and ruu to get back to normal. The problem is there is no ruu out for 3.16 and running the ruu for 3.15 may mess up your phone. I would try to flash the kernel separately by flashing with fastboot or flashgui and see if that allows it to boot into the rom. You may be able to run dirty racun and gain s-off since the hboot didn't change with the latest update.
Click to expand...
Click to collapse
On your notes I did some searching to learn what you were saying. First I tried to use the fastboot update 'meanbean-rom.zip' file but it produced errors:
archive does not contain 'android-info.txt
archive does not contain 'android-product.txt
error: update package has no android-info.txt or android-product.txt
I tried fastboot flash boot boot.img after extracting the boot.img from the .zip. After rebooting the phone stays on the white HTC logo screen but now populates the red dev notice. Looks like I'm going in the right direction
Thanks for your help so far.
I believe I have it figured out. I searched for an unofficial version of CWM recovery (all the XDA links for the evo lte have been removed for now due to bugs). I'll deal with those bugs as I was stuck without a phone until I got it figured out
Installed CWM 5.8.3.5 and flashed Meanbean Rom. Problem fixed
I'll put TWRP back on when they release a patch.
*Edit* spoke too soon. The touch interface doesnt work with meanbean due to the driver update (I'm guessing). Atlease I can see any missed calls now. lol
*Edit* Thanks to the D3rps I was able to get my phone up and going again. They had posted the stock 3.16 rom here: http://forum.xda-developers.com/showthread.php?t=2127947, with *Removed* recovery I was able to flash that rom. Now I just have to keep an eye out for the Meanbean update that will make it work with 3.16 touch.
**Edit** I removed the reference to the recovery I was using due to problems my noob self was not aware of. Thanks to Bigdaddy619 for his guidance, I now realize why no one is using it on the evo lte.
I have been working on this phone for hours, and hours. and it has been one of the most frustrating phones i have ever worked with.
Okay so i can flash and change roms fantastically!
Im currently switching from verizon to T-Mobile and i heard there was a GSM capability. So on i went with research, I have tried so many different rom's, rom's with GSM that come with it.Nothing worked. No signal no nothing. one rom realized there was a sim card in but it said the sim card was full, which is definitely not full. I never got a good instruction and right files for the S-off function so i never made it S-off nor do i know what kind of wire to use. the most disappointing is that it can't get a signal and i flashed the RUU 4.0..... something and it did nothing to the radio on my phone when in bootloader. If anyone has some idea of what i can do with easy to follow instructions. I that much of a noob. I had successfully rooted and unloacked (sim by myself) and unlocked and flashed roms for the HTC Rezound. It's just this one thing that has been bother the crap out of me... nothing worked.
Did you go under network settings and select preferred network then select GSM?
Sent from my ADR6425LVW using Tapatalk 2
ruskimaster said:
I have been working on this phone for hours, and hours. and it has been one of the most frustrating phones i have ever worked with.
Okay so i can flash and change roms fantastically!
Im currently switching from verizon to T-Mobile and i heard there was a GSM capability. So on i went with research, I have tried so many different rom's, rom's with GSM that come with it.Nothing worked. No signal no nothing. one rom realized there was a sim card in but it said the sim card was full, which is definitely not full. I never got a good instruction and right files for the S-off function so i never made it S-off nor do i know what kind of wire to use. the most disappointing is that it can't get a signal and i flashed the RUU 4.0..... something and it did nothing to the radio on my phone when in bootloader. If anyone has some idea of what i can do with easy to follow instructions. I that much of a noob. I had successfully rooted and unloacked (sim by myself) and unlocked and flashed roms for the HTC Rezound. It's just this one thing that has been bother the crap out of me... nothing worked.
Click to expand...
Click to collapse
When you did the ruu, the second time it runs through the ruu (after first reboot) it will update the radios and system. Did you make sure when you did the ruu that you had to start it twice from hboot ? what version radios do you see listed in hboot ?
dottat said:
When you did the ruu, the second time it runs through the ruu (after first reboot) it will update the radios and system. Did you make sure when you did the ruu that you had to start it twice from hboot ? what version radios do you see listed in hboot ?
Click to expand...
Click to collapse
my radio is 1.22 and hboot is 2.25. when it went through and flashed/installed the ruu file it didn't reboot automatically as i've herd it should
ruskimaster said:
my radio is 1.22 and hboot is 2.25. when it went through and flashed/installed the ruu file it didn't reboot automatically as i've herd it should
Click to expand...
Click to collapse
Then you don't have global firmware yet. You need to ruu to 605.12 and then take the 6mb ota that will take you to 605.13. Then take one more ota @207mb which will give you full global radios and firmware.
Globals hboot is also 2.28 so you know what to look for.
Sent from my Nexus 7 using Tapatalk HD
dottat said:
Then you don't have global firmware yet. You need to ruu to 605.12 and then take the 6mb ota that will take you to 605.13. Then take one more ota @207mb which will give you full global
Click to expand...
Click to collapse
An alternative would be to install the global leak RUU first. From there you can follow the process for first installing the global update firmware (in the general discussion forum), then installing the global update itself (in the original android development forum).
Unfortunately, neither of the paths available to you is going to be totally painless...
Good luck,
John
So yesterday I decided to go ahead and flash the OTA update to 4.4. After messing around with it for a little bit I decided I wanted to go back to 4.3. My device is rooted, unlocked and I do have S – off.
So I decided to try to run the RUU for 4.3 but it failed with error 155. Does anybody know if this has anything to do with the fact that HBOOT was updated to 1.56?
Also I have a decrypted 4.3 stock T-Mobile ROM but when I try to use fast boot to erase system I receive the message remote not allowed. Can anybody help me out here?
Mark112887 said:
So yesterday I decided to go ahead and flash the OTA update to 4.4. After messing around with it for a little bit I decided I wanted to go back to 4.3. My device is rooted, unlocked and I do have S – off.
So I decided to try to run the RUU for 4.3 but it failed with error 155. Does anybody know if this has anything to do with the fact that HBOOT was updated to 1.56?
Also I have a decrypted 4.3 stock T-Mobile ROM but when I try to use fast boot to erase system I receive the message remote not allowed. Can anybody help me out here?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1655832
Mikey said:
http://forum.xda-developers.com/showthread.php?t=1655832
Click to expand...
Click to collapse
Thank you very much for the link Mikey but it did not help. I ended up fixing the problem myself. As it turns out the problem was caused by the fact that my version of H boot was 1.56 and the version in the T-Mobile 4.3 RUU was 1.55, that was the reason I was unable to restore. Luckily I was able to find an OTA update zip for 4.3, once I found that I was able to extract the firmware.zip file and flash it to my device because I had S – off. Once I had the correct version of H boot that corresponded with the version that was in the RUU I was able to flash back to 100% stock with no issues whatsoever.
Nobody informed me that the 4.4 OTA contained an update to H boot because well I guess nobody knew but hopefully now that information can be passed around. The other piece of information that I would like people to know is that rumrunner still works on 1.56.
Anyway my issue is now solved so I will go ahead and mark the thread accordingly
Really I'm just looking to get my phone back to a "stock" condition. I'm not sure I understand which RUU is right for my situation. I haven't updated anything in about a year so my software is a bit outdated.
Here's what I'm working with:
Bootloader unlocked with HTC Dev
S-ON
HBOOT 2.09
TWRP 2.7.0.8
Two ROMs currently saved
(stock) 3.17.651.5 <-- just goes black after a long HTC screen
Cyanogenmod 10 (I think) <-- boots fine
It appears the latest on HTC's site is 3.17.651.9. Will that do the trick? Other guides here point the same page but specifically refer to 3.17.651.4. Is there a reason I would go with .4 over .9? Is there a some other option?
Thanks for your help!
Kintantee said:
Really I'm just looking to get my phone back to a "stock" condition. I'm not sure I understand which RUU is right for my situation. I haven't updated anything in about a year so my software is a bit outdated.
Here's what I'm working with:
Bootloader unlocked with HTC Dev
S-ON
HBOOT 2.09
TWRP 2.7.0.8
Two ROMs currently saved
(stock) 3.17.651.5 <-- just goes black after a long HTC screen
Cyanogenmod 10 (I think) <-- boots fine
It appears the latest on HTC's site is 3.17.651.9. Will that do the trick? Other guides here point the same page but specifically refer to 3.17.651.4. Is there a reason I would go with .4 over .9? Is there a some other option?
Thanks for your help!
Click to expand...
Click to collapse
If you're looking to get it back to "stock", any Jewel RUU ought to get you there. Though, I do recommend using the most up-to-date version you can find. Newer ones have updates included. The newest one is 4.13.651.4.