My LTE took a dump the other day. Started overheating like crazy, despite no changes.
Was running cynagenmod 10.2 and it was working well. S-Off HBOOT 2.09.4444, Radio 1.12.11.1119
Then these overheats kept going all day until I turned it off. Then started bootlooping, would fully launch one out of 10 times.
So I wiped using TWRP and gave that a try, no luck, still overheating and bootlooping.
So I wiped and restored a TWRP backup, nothing... the stock rom is bootlooping even harder than before and never fully launches now.
It got to the point TWRP wouldn't launch until I had to put a fresh version on the SD card.
Tried to install the newest stable CM10.2 image and as before locking up at boot splash screen of the rom after HTC "quietly brilliant" and looping.
So now I am stuck, downloaded the stock RUU from HTC website, however the devices needs to be recognized to use their exe.
Is there an image I can throw on the SD card and use TWRP to try a flash from that? Any other recommendations?
TIA.
syl2us said:
My LTE took a dump the other day. Started overheating like crazy, despite no changes.
Was running cynagenmod 10.2 and it was working well. S-Off HBOOT 2.09.4444, Radio 1.12.11.1119
Then these overheats kept going all day until I turned it off. Then started bootlooping, would fully launch one out of 10 times.
So I wiped using TWRP and gave that a try, no luck, still overheating and bootlooping.
So I wiped and restored a TWRP backup, nothing... the stock rom is bootlooping even harder than before and never fully launches now.
It got to the point TWRP wouldn't launch until I had to put a fresh version on the SD card.
Tried to install the newest stable CM10.2 image and as before locking up at boot splash screen of the rom after HTC "quietly brilliant" and looping.
So now I am stuck, downloaded the stock RUU from HTC website, however the devices needs to be recognized to use their exe.
Is there an image I can throw on the SD card and use TWRP to try a flash from that? Any other recommendations?
TIA.
Click to expand...
Click to collapse
What are you trying to achieve? Do you need an alternative RUU flash or find a new ROM so you won't get bootloops and heating?
I suggest going on CM11 or resort to Meanbean for stock sense 4.
If you're running a RUU I suggest using this method here.
http://forum.xda-developers.com/showthread.php?p=50523371
But before that please read the first 4 posts of this thread (especially Q&A) to get you updated on what's going on with the newest RUU.
http://forum.xda-developers.com/showthread.php?t=2639180
More questions? Just ask me.
Sent from my EVO using Tapatalk
lreyes said:
What are you trying to achieve? Do you need an alternative RUU flash or find a new ROM so you won't get bootloops and heating?
I suggest going on CM11 or resort to Meanbean for stock sense 4.
If you're running a RUU I suggest using this method here.
http://forum.xda-developers.com/showthread.php?p=50523371
But before that please read the first 4 posts of this thread (especially Q&A) to get you updated on what's going on with the newest RUU.
http://forum.xda-developers.com/showthread.php?t=2639180
More questions? Just ask me.
Sent from my EVO using Tapatalk
Click to expand...
Click to collapse
I am trying to get this phone into any working order if I can. I have reason to believe the hardware has been affected by the overheating. I need to get it to fully launch before I can declare that, so anything to stop it from bootlooping is what I am trying to achieve. Occasionally, when it would fully launch, I noticed none of the radios worked, no mobile data, no WiFi and no Bluetooth which were previously functioning fine.
The links are down to the two files needed in the first post you're referencing.
I believe my partitions are out of whack and need to be fixed. Everything I am seeing to repair partitions is while the phone can boot, can someone point me to some info that shows how to fix partitions while only recovery is achievable? Maybe I am going about this wrong, search not returning the results needed.
TIA
You can RUU from the bootloader, without having to be booted to the OS. I can confirm this works on both the 3.17 RUU and the latest 4.13 RUU, which I have both used. Make sure you have HTC Sync involved and use a Windows 7 machine and you shouldn't have any issues.
Sent from my EVO LTE
FinZ28 said:
You can RUU from the bootloader, without having to be booted to the OS. I can confirm this works on both the 3.17 RUU and the latest 4.13 RUU, which I have both used. Make sure you have HTC Sync involved and use a Windows 7 machine and you shouldn't have any issues.
Sent from my EVO LTE
Click to expand...
Click to collapse
You're saying you were able to get it recognized during Bootloader USB? The RUU will not recognize the device for me this way.
Yep, worked just fine connected via Fastboot USB mode.
Sent from my EVO LTE
FinZ28 said:
Yep, worked just fine connected via Fastboot USB mode.
Sent from my EVO LTE
Click to expand...
Click to collapse
Hmm, tried this on Win8, I'll give 7 a shot, thanks for the heads up!
How do I ensure my partitions are in proper order? Often when in TWRP and trying to run common commands, I get SD card unmountable and noticed what seems like multiple SD card nomenclature.
Related
I have a new HTC Evo LTE and HBOOT 1.15.000 Radio 1.05.11.0606and do not have S-OFF.
I installed Fresh 5.2.1 and had problems, when back and did a wipe including system and installed 5.2.1 again and it didn't work. After doing that I went back, wiped system again, and then restored the backup I previously made. Now the backup sometimes loads, sometimes doesn't, but even when it does I have no radio. I am going to try to install a stock rom through recovery or fresh 5.1.1 and HOPE I get radio back.
Any other suggestions of what I could do?
jeggen said:
I have a new HTC Evo LTE and HBOOT 1.15.000 Radio 1.05.11.0606and do not have S-OFF.
I installed Fresh 5.2.1 and had problems, when back and did a wipe including system and installed 5.2.1 again and it didn't work. After doing that I went back, wiped system again, and then restored the backup I previously made. Now the backup sometimes loads, sometimes doesn't, but even when it does I have no radio. I am going to try to install a stock rom through recovery or fresh 5.1.1 and HOPE I get radio back.
Any other suggestions of what I could do?
Click to expand...
Click to collapse
So now I'm just in a boot loop. I relocked, installed stock recovery and ran RUU. When I did that I booted just long enough that I could almost slide the ring to unlock before I rebooted. Then the device just constantly reboots.
I unlocked again, installed TWRP 2.2.2.0 in case there was a bug causing flashing issues. Recovery boots just fine now. I flashed Stock Rooted DeOdexed 1.22.651.3 from here since that was the version I had before this whole fiasco. I'm going to try to restore backup again but don't know how to get out of this horrible mess. Worse part about it is that it's my wife's phone! Help please!
You might need to run a different RUU. I'm not too experienced with that kind of issue though.
"We're coming from a pure power source"
metalfan78 said:
You might need to run a different RUU. I'm not too experienced with that kind of issue though.
"We're coming from a pure power source"
Click to expand...
Click to collapse
I reflashed stock recovery, relocked bootloader (fastboot oem lock), ran RUU (RUU_JEWEL_CL_ICS_40_Sprint_WWE_1.22.651.3_Radio_1. 05.11.0606_NV_SPCS_2.45_003_release_268323_signed. exe), and still had the boot loop problem. RUU said it completed but the bootloader still said "relocked". Isn't RUU supposed to totally wipe and restore the entire device?
I recall on my old EVO there was a zip you could place in the SDcard that the bootloader automatically looked for and would use to reflash to factory everything. Is there a way to do this with the EVO 4g LTE?
Is it possible that radios/firmware somehow got borked even though I am on S-ON? Is there a way to reflash them from bootloader?
Just thinking through ideas I'd try next and something that could possibly help recover or at least put me in a position to go back to Sprint for help.
Could have been a bad download. I think there is info on re locking in the development sticky section. It might give you some more information on what to do next.
"We're coming from a pure power source"
Just an update. Flashed again a stock ROM and installed the boot.img from stock using fastboot to be sure it was in place. (fastboot flash boot boot.img). That didn't work, still had boot loop where the phone loads enough to show the background and then restarts.
Used the PJ75IMG.zip file and attempted to install automatically in bootloader (from here) <-- Didn't install says "Main Version is older! Update Fail!
I then installed stock recovery and locked bootloader. Bootloader now shows "*** TAMPERED*** and *** RELOCKED***.
Ran RUU <-- Have a hard time doing anything since it doesn't boot up long enough to connect. Eventually RUU will fail with a connection error. I haven't been able to run RUU from HBOOT either and without the device stable long enough I'm not sure how to get RUU to run on the phone.
Still only boot far enough to see the background screen (wallpaper) and then reboot.
I'll gladly give $20 to anyone who offers a workable solution, paid either to you, or dev/charity of your choice if you don't want it.
This all started when I installed Fresh 5.2.1. Not sure if it was the fresh install or using TWRP to wipe data/cache and I also wiped system. Was that a mistake?
I just don't understand why I can't flash back even to stock. Since I'm relocked and never had S-OFF I don't understand how I was able to do something that can't be undone by flashing. I've flashed phones dozens of times so am comfortable with the process and just can't understand what went wrong and how to recover.
Is there an updated version of the PJ75IMG.zip file I could use?
Would it work to flash CM10 & the boot.img using fastboot?
jeggen said:
Just an update. Flashed again a stock ROM and installed the boot.img from stock using fastboot to be sure it was in place. (fastboot flash boot boot.img). That didn't work, still had boot loop where the phone loads enough to show the background and then restarts.
Used the PJ75IMG.zip file and attempted to install automatically in bootloader (from here) <-- Didn't install says "Main Version is older! Update Fail!
I then installed stock recovery and locked bootloader. Bootloader now shows "*** TAMPERED*** and *** RELOCKED***.
Ran RUU <-- Have a hard time doing anything since it doesn't boot up long enough to connect. Eventually RUU will fail with a connection error. I haven't been able to run RUU from HBOOT either and without the device stable long enough I'm not sure how to get RUU to run on the phone.
Still only boot far enough to see the background screen (wallpaper) and then reboot.
I'll gladly give $20 to anyone who offers a workable solution, paid either to you, or dev/charity of your choice if you don't want it.
This all started when I installed Fresh 5.2.1. Not sure if it was the fresh install or using TWRP to wipe data/cache and I also wiped system. Was that a mistake?
I just don't understand why I can't flash back even to stock. Since I'm relocked and never had S-OFF I don't understand how I was able to do something that can't be undone by flashing. I've flashed phones dozens of times so am comfortable with the process and just can't understand what went wrong and how to recover.
Is there an updated version of the PJ75IMG.zip file I could use?
Would it work to flash CM10 & the boot.img using fastboot?
Click to expand...
Click to collapse
I sent you a PM
Sent from my EVO using xda premium
I'm back up and running. With a kind and helpful tech we ran RUU again (twice) and still had boot loop. I was going to give up on it but we went into the default recover and cleared data and factory reset and it seems to be back to normal again and working fine.
Sent from my MB855 using Tapatalk 2
jeggen said:
I'm back up and running. With a kind and helpful tech we ran RUU again (twice) and still had boot loop. I was going to give up on it but we went into the default recover and cleared data and factory reset and it seems to be back to normal again and working fine.
Sent from my MB855 using Tapatalk 2
Click to expand...
Click to collapse
Awesome glad you got it fixed.
Sent from my EVO using xda premium
So I have my phone rooted. s-off with the "wire trick".
ClockworkMod installed.
Trying to use CM10 (Gangnam style). No matter what I do, I get CONSTANT reboots.
I tried doing the all the wipes (data, cache, etc....)
I got it to boot up once, for about 5 minutes. In the middle of trying to figure out why I couldn't get any service (changing the APN from what I could figure out) the phone rebooted and got stuck in its boot loop again.
No matter what I do, boot loop. Basically gets to the CM10 loading screen, loads for about 2 seconds, reboots.
Restore to my backed up file, phone works perfect.
Any suggestions?
I realize I'm a n00b here, but I've successfully rooted and ran CM10 on my Acer Iconia A500 (CM9 then up to CM10) and my brothers HP tablet (CM9) without major issues I couldn't handle. For some reason it doesn't seem anyone else has had the reboot issue with at least this specific CM10.
Any help would be greatly appreciated. I hate the virgin mobile boot up screen and moreover I LOVE 4.1.2.
I also tried 4.2.2 WILD FOR THE NIGHT but I just get error Status 7. I even made sure to update my 4Ext recovery (was using clockwork recovery before), update to latest firmware. Updated to latest firmware, wiped everything but my SD card, still got Error Status 7 on 4.2.2 and constant reboot on 4.1.2. This is driving me nuts, I've searched the forum and did not find a solution so far (which is why I finally decided to sign up and become a member!!!)
By the way, im on JuopunutBear HBOOT 1.57.5757 with S-OFF.
The reason for the boot loops is your hboot version needs to be downgraded. Once thats done you'll be fine.
sent from my 1920 overclocked note 2 running jedi xp11
markbencze said:
The reason for the boot loops is your hboot version needs to be downgraded. Once thats done you'll be fine.
sent from my 1920 overclocked note 2 running jedi xp11
Click to expand...
Click to collapse
Downgraded to 1.4. Now I get a constant bootloop with no splash screen. Can't even do anything now because bootloader asks me every time if I want to update to the file on my SDcard
Used my old phone to take the file off the SDcard. Tried the WILD FOR THE NIGHT 4.2.2 again. Still not booting even to splash screen for CM10.
What version should I be using? So afraid I bricked my phone....
whoops!
Now I feel like a dumbass.
Downgraded to hBoot 1.4
Wiped everything.
Format everything (except SDcard).
Loaded 4.2.2.
Booted up! Thanks! Been fighting this for days!!!
http://forum.xda-developers.com/showthread.php?p=32032629
This is the version of hboot that works well for me. But if you got it working you're good. No need to change. Basically after you downgrade your hboot I booted into recovery and moved the hboot zip into a different folder on my sd card. If its in the root of 5he card bootloader will keep asking... then you can flash away and delete the file as you no longer need it. Glad I was able to help. I just actually figured this out last nigth when I was playing with my old evo. I tried to flash and it boot looped so I had to do some thinking and then it occurred to me that the hboot was likely to blame.
Enjoy
sent from my 1920 overclocked note 2 running jedi xp11
markbencze said:
This is the version of hboot that works well for me.
Click to expand...
Click to collapse
That's a GSM hboot and the OP is on Virgin Mobile USA which is CDMA so he wouldn't want to flash that version or he could damage his phone.
ramjet73
SOLVED!! Thanks to everyone, especially bigdaddy and FinZ! I will post something about what I did and what I used to get S-Off since it is actually really easy once put into easy to understands terms
Hey everyone,
Everything was going really as I was rooting my Evo 4G LTE this afternoon, until I realized I forgot to S-off. TWRP was installed and Superuser was flashed - Anyways, I got antsy and wiped the phone and flashed CM 10.1 and realized I forgot S-off - so of course, the phone wouldn't boot past the HTC screen.
I've been trying to flash stock roms to get into the superuser app, but none of them will load. They start to flash in TWRP, then the phone reboots to the HTC splash screen.
I am now unlocked, but still S-on. I can't flash any roms right now and was hoping someone might be able to help me out. I even tried the process all over again, but I get the same problem. So as of now, I can't get an OS on the phone.
Any ideas? Thanks.
Edit: I was running the latest OTA with HBOOT 2.09.
venkman21 said:
Hey everyone,
Everything was going really as I was rooting my Evo 4G LTE this afternoon, until I realized I forgot to S-off. TWRP was installed and Superuser was flashed - Anyways, I got antsy and wiped the phone and flashed CM 10.1 and realized I forgot S-off - so of course, the phone wouldn't boot past the HTC screen.
I've been trying to flash stock roms to get into the superuser app, but none of them will load. They start to flash in TWRP, then the phone reboots to the HTC splash screen.
I am now unlocked, but still S-on. I can't flash any roms right now and was hoping someone might be able to help me out. I even tried the process all over again, but I get the same problem. So as of now, I can't get an OS on the phone.
Any ideas? Thanks.
Edit: I was running the latest OTA with HBOOT 2.09.
Click to expand...
Click to collapse
Flash meanbean or viper rom, both have s-on kernel installer and you should be able to get s-off using dirty racun or moonshine... Sharkie rom is a stock rom too with a s-on installer... Good Luck!
Sent from my EVO using xda app-developers app
venkman21 said:
Hey everyone,
Everything was going really as I was rooting my Evo 4G LTE this afternoon, until I realized I forgot to S-off. TWRP was installed and Superuser was flashed - Anyways, I got antsy and wiped the phone and flashed CM 10.1 and realized I forgot S-off - so of course, the phone wouldn't boot past the HTC screen.
I've been trying to flash stock roms to get into the superuser app, but none of them will load. They start to flash in TWRP, then the phone reboots to the HTC splash screen.
I am now unlocked, but still S-on. I can't flash any roms right now and was hoping someone might be able to help me out. I even tried the process all over again, but I get the same problem. So as of now, I can't get an OS on the phone.
Any ideas? Thanks.
Edit: I was running the latest OTA with HBOOT 2.09.
Click to expand...
Click to collapse
Question... How did you install your recovery? Goo manager, pj75img.zip, or fastboot? I have had this same problem and the only solution was to fastboot flash a recovery... Dunno it was very weird and has only happened on my lte but it's been months.
Flowed from my Jewel using Tapatalk 2
gunfromsako said:
Question... How did you install your recovery? Goo manager, pj75img.zip, or fastboot? I have had this same problem and the only solution was to fastboot flash a recovery... Dunno it was very weird and has only happened on my lte but it's been months.
Flowed from my Jewel using Tapatalk 2
Click to expand...
Click to collapse
I installed it using fastboot. I'm going to try one of the ROMs suggested above and see if that works. I'll let you all know as soon as I do it.
I keep reading that Moonshine won't work with HBOOT 2.09 - and I haven't had any luck getting it to work; it still gives me connection issues saying it can't connect to the phone. It's weird... I can use the adb devices command in recovery mode and my device ID shows up, but when I go into fastboot USB and do adb devices, I can't get it to show up. If I could somehow get that to show up during fastboot, it would mean smooth sailing.
Update: I successfully installed Meanbean. However, I still cannot gain S-Off. Moonshine won't work and I do not know enough to use DirtyRacun since it must be used with Ubuntu. I'll post my Moonshine issues in that thread
Thanks for the help with this! It looks like it just needed a S-On ROM to be installed which I though I was doing before!
I've tried every single HTC driver available and I can't get anything to recognize the Evo when it's in fastboot. It only recognizes the device when the ROM is loaded and USB storage is enabled. Unfortunately, I can't get s-off (as far as I know) without being in the bootloader and using fastboot.
Anyone know how I can achieve this or how I can get everything to communicate with one another like they're supposed to?
Have you deleted all the HTC stuff on your PC rebooted it the plug you phone back in and it should load the drivers again
then boot into bootloader and it should load more drivers
also try updating your android-sdk
Make sure you have the most current HTC driver. At least one person that I know of had issues until he updated to the most recent driver, which can be found in the link below. Use the HTC driver from post #2.
http://forum.xda-developers.com/showthread.php?t=2179776
Also, like Bigdaddy said, make sure you have things like HTC Sync removed. Make sure you're using a USB 2.0 port, too. I don't know where you read Moonshine doesn't work with Hboot 2.09, because it does (specifically for the latest OTA).
Sent you a PM
Sent from my EVO using xda premium
Ok, I give up. I've tried everything I can think of, but I can't get 4G to stick on, and trying to run the 3.06 RUU gives me error 170.
Here's what happened. Yesterday I flashed Kickdroid 2.0 with the CDMA patch from: http://forum.xda-developers.com/showthread.php?t=2634126
- Everything seemed to install fine, and initially 4G was up. But within about a minute 4G disconnected and I no longer had any mobile data.
- So then I did a full complete wipe via TWRP - doing the factory reset, then using the advanced wipe on everything except internal storage - then restored my backup of BadSeed's Tranquil rom. It came up fine initially but then within about a minute 4G disconnected and I was put back at 3G.
- Re-wiped everything same as before, then flashed the Tranquil Rom from scratch. - Same problem. 4G connects initially then drops to 3G.
- Updated TWRP to the beta .6 version as suggested by the Kickdroid dev and re-flashed and did all those same steps again and still having same problem
- At one point last night I left the phone alone and after a long time with the kickdroid Rom re-flashed it asked me which carrier I had. I chose Verizon and then 4G stuck on for a while. Then, it lost it's connection again to 4G. This Rom never gave me any 'Service'. The lockscreen always said 'no service'
- This morning, I flashed the latest Viper and it too initially gives me 4G then about a minute later that drops and I'm stuck on 3G.
- I thought maybe it was my SIM card, so I put it in my rezound and it works just fine in that phone.
- I've been trying to RUU using the 3.06.605.4 RUU from: http://forum.xda-developers.com/showthread.php?t=2612740 but I keep getting error 170 saying that the device wasn't found and to plug in my usb cable.
I suspect that there is something in the CDMA patch that has done this. I say that in hopes to help narrow the problem down not to blame anyone, as I do accept the responsibility to what I have flashed on my phone, so please don't take it that way. I don't know what could remain after wiping and re-flashing but it seems as thought something has.
Anyhoo, I'm getting a little desperate at this point and hoping someone can help me out. Much appreciated...
Try flashing the recovery flashable radio?
Something could have borked the radio partition.
Sent from my DNA using my mind.
Uzephi said:
Try flashing the recovery flashable radio?
Something could have borked the radio partition.
Sent from my DNA using my mind.
Click to expand...
Click to collapse
Lol, of course the one thing I forgot to mention that I did. I flashed the radio from .torrented's thread as well.
I think at this point I'd like to just RUU it anyway. Could it be that my bootloader is still unlocked and I have TWPR as my recovery?
Thanks a lot guys...
badogg said:
Ok, I give up. I've tried everything I can think of, but I can't get 4G to stick on, and trying to run the 3.06 RUU gives me error 170.
Here's what happened. Yesterday I flashed Kickdroid 2.0 with the CDMA patch from: http://forum.xda-developers.com/showthread.php?t=2634126
- Everything seemed to install fine, and initially 4G was up. But within about a minute 4G disconnected and I no longer had any mobile data.
- So then I did a full complete wipe via TWRP - doing the factory reset, then using the advanced wipe on everything except internal storage - then restored my backup of BadSeed's Tranquil rom. It came up fine initially but then within about a minute 4G disconnected and I was put back at 3G.
- Re-wiped everything same as before, then flashed the Tranquil Rom from scratch. - Same problem. 4G connects initially then drops to 3G.
- Updated TWRP to the beta .6 version as suggested by the Kickdroid dev and re-flashed and did all those same steps again and still having same problem
- At one point last night I left the phone alone and after a long time with the kickdroid Rom re-flashed it asked me which carrier I had. I chose Verizon and then 4G stuck on for a while. Then, it lost it's connection again to 4G. This Rom never gave me any 'Service'. The lockscreen always said 'no service'
- This morning, I flashed the latest Viper and it too initially gives me 4G then about a minute later that drops and I'm stuck on 3G.
- I thought maybe it was my SIM card, so I put it in my rezound and it works just fine in that phone.
- I've been trying to RUU using the 3.06.605.4 RUU from: http://forum.xda-developers.com/showthread.php?t=2612740 but I keep getting error 170 saying that the device wasn't found and to plug in my usb cable.
I suspect that there is something in the CDMA patch that has done this. I say that in hopes to help narrow the problem down not to blame anyone, as I do accept the responsibility to what I have flashed on my phone, so please don't take it that way. I don't know what could remain after wiping and re-flashing but it seems as thought something has.
Anyhoo, I'm getting a little desperate at this point and hoping someone can help me out. Much appreciated...
Click to expand...
Click to collapse
Did you update HTC driver? then trying to RUU from bootloader, Fastboot usb, with the latest Hboot updated* (1.54.0000)= 3.06.605.4 version.
---------- Post added at 01:34 PM ---------- Previous post was at 01:23 PM ----------
badogg said:
Lol, of course the one thing I forgot to mention that I did. I flashed the radio from .torrented's thread as well.
I think at this point I'd like to just RUU it anyway. Could it be that my bootloader is still unlocked and I have TWPR as my recovery?
Thanks a lot guys...
Click to expand...
Click to collapse
Bootloader unlocked matter to RUU , TWRP nope.
finanandroid said:
Did you update HTC driver? then trying to RUU from bootloader, Fastboot usb, with the latest Hboot updated* (1.54.0000)= 3.06.605.4 version.
---------- Post added at 01:34 PM ---------- Previous post was at 01:23 PM ----------
Bootloader unlocked matter to RUU , TWRP nope.
Click to expand...
Click to collapse
I would expect a problem later on if it were the bootloader being locked still, not int he beginning and then saying that the device isn't found. Or am I totally wrong and should just re-lock the bootloader and try again?
badogg said:
I would expect a problem later on if it were the bootloader being locked still, not int he beginning and then saying that the device isn't found. Or am I totally wrong and should just re-lock the bootloader and try again?
Click to expand...
Click to collapse
Well you mention error 170, usually its HTC Driver outdated, thats the reason that I suggest Driver update.
thought first have a working ADB/fastboot to see your phone. usb 2
you need to lock the Bootloader in order to run Ruu 3.06.exe (no problem because after RUU is done, Rumrunner unlock and S-Off Thanks to beaups
you need to update the Stock Hboot version to 3.06. thanks to Torrented
Here the link updated thanks to Phaded http://forum.xda-developers.com/showthread.php?t=2293919&highlight=flash+radio
finanandroid said:
Well you mention error 170, usually its HTC Driver outdated, thats the reason that I suggest Driver update.
thought first have a working ADB/fastboot to see your phone. usb 2
you need to lock the Bootloader in order to run Ruu 3.06.exe (no problem because after RUU is done, Rumrunner unlock and S-Off
you need to update the Stock Hboot version to 3.06. thanks to Torrented
Here the link updated thanks to Phaded http://forum.xda-developers.com/showthread.php?t=2293919&highlight=flash+radio
Click to expand...
Click to collapse
I tried the updated drivers earlier and still get the error 170. I'm wondering if there is just something wonky with my work computer that isn't working right. I'll try locking bootloader and running RUU from a laptop and see what happens. Thanks for the assist! :highfive:
badogg said:
I tried the updated drivers earlier and still get the error 170. I'm wondering if there is just something wonky with my work computer that isn't working right. I'll try locking bootloader and running RUU from a laptop and see what happens. Thanks for the assist! :highfive:
Click to expand...
Click to collapse
a pleasure
Any other android devices hooked up to that PC? I had 170 error when having both Rezound and DNA plugged in. The program may be trying to look at the other device port instead of the DNA port.
Try with locked boot loader and stock recovery. After I got rid of error 170 I got an error in the 150's (not the one mentioned in the ruu thread). It was because of custom splash image and custom recovery.
Sent from my DNA using my mind.
Uzephi said:
Any other android devices hooked up to that PC? I had 170 error when having both Rezound and DNA plugged in. The program may be trying to look at the other device port instead of the DNA port.
Try with locked boot loader and stock recovery. After I got rid of error 170 I got an error in the 150's (not the one mentioned in the ruu thread). It was because of custom splash image and custom recovery.
Sent from my DNA using my mind.
Click to expand...
Click to collapse
Interesting, I don't have anything connected, but I'm sure I have drivers loaded for my nexus 7
Which drivers for HTC are you using? The ones from HTC sync or the ones from pdanet? I found the pdanet ones work better for everything but HTC sync (which, who honestly uses? Lol)
Sent from my DNA using my mind.
Well, I let htcsync update the usb drivers and now the RUU is updating the image now.
Ok, this persisted through the RUU. Rom booted up, got 4G initially, then went to 3G.
badogg said:
Ok, this persisted through the RUU. Rom booted up, got 4G initially, then went to 3G.
Click to expand...
Click to collapse
after Ruu you most do a factory reset* from stock recovery
All that is usually needed is to restore the NV partitions on the device.
To do this, flash a stock rom and stock recovery.
Perform a factory reset in stock recovery.
Your radio should then function normally again.
No need to RUU or any of that, just a stock rooted rom and stock recovery are sufficient.
The key factor is the factory reset in stock recovery.
So if you did the RUU already, and did not do the factory reset in stock recovery, then that's why you still have an issue.
finanandroid said:
after Ruu you most do a factory reset* from stock recovery
Click to expand...
Click to collapse
omg, duh!! I knew that, just forgot to do it.
That seems to have fixed it. +150,000 internets to you!!
badogg said:
omg, duh!! I knew that, just forgot to do it.
That seems to have fixed it. +150,000 internets to you!!
Click to expand...
Click to collapse
glad :good: you got it !
@santod040 which stock rom do I need to flash and what is stock recovery? Do I have to do this with adb comands or use twarp like normal flash so I can get my radio working correctly again and 4g back? Any one that can point me to what I need to do here is greatly appreciated. Thank you!
Sent from my HTC6435LVW using Tapatalk
Sutko82 said:
@santod040 which stock rom do I need to flash and what is stock recovery? Do I have to do this with adb comands or use twarp like normal flash so I can get my radio working correctly again and 4g back? Any one that can point me to what I need to do here is greatly appreciated. Thank you!
Sent from my HTC6435LVW using Tapatalk
Click to expand...
Click to collapse
My full odex stock Rom in the dev section is sufficient.
If there isn't a stock recovery posted anywhere I'll locate one for you.
Then you flash the Rom in your current recovery.
After you boot, reboot to hboot.
Then fastboot flash recovery nameoffile.img.
Then either factory reset from Recovery or from the roms settings option.
Sent from my HTC6500LVW using Tapatalk
Pls locate stock recovery as I am not sure which one to use. I am downloading your odexed stock rom as we speak. I appreciate this very much! @santod040
Sent from my HTC6435LVW using Tapatalk
---------- Post added at 11:48 PM ---------- Previous post was at 11:43 PM ----------
After boot type in command prompt reboot to hboot or can I just type adb devices and then flash recovery
Sent from my HTC6435LVW using Tapatalk
I´m new here and need help to install the official update I have a Htc one x+ Thanks
dragon1876 said:
I´m new here and need help to install the official update I have a Htc one x+ Thanks
Click to expand...
Click to collapse
http://www.htc.com/us/support/htc-one-x-plus-att/news/ = RUU link
Charge phone to 100%
Enter fastboot mode
Fastboot oem lock
Then, run the ruu
Guide here: http://androidforums.com/one-s-all-things-root/691874-guide-how-run-ruu-your-htc-one-s.html
(same process for one s and one x)
one x+
I follow that steps but doesn´t work
dragon1876 said:
I follow that steps but doesn´t work
Click to expand...
Click to collapse
Can you be more specific? What did not work?
Orvandi said:
Can you be more specific? What did not work?
Click to expand...
Click to collapse
Ok, yesterday I download the 4.2.2 update from HTC website, then proceeded to update by following the steps in the same web, everything was ok normal, finish updating and restart the phone, then when the phone turn on I noticed three situations the phone will not update and continues with 4.1.1 JB, the other is the wifi does not connect fails and the last the partition of the internal memory does not appear!!!!
dragon1876 said:
Ok, yesterday I download the 4.2.2 update from HTC website, then proceeded to update by following the steps in the same web, everything was ok normal, finish updating and restart the phone, then when the phone turn on I noticed three situations the phone will not update and continues with 4.1.1 JB, the other is the wifi does not connect fails and the last the partition of the internal memory does not appear!!!!
Click to expand...
Click to collapse
OK, are you sure you charged your phone? The RUU needs at least 30% battery. Also, select fastboot before you run the RUU.
After you click next, it should say that the RUU has recognized your device and it will run on its own.
one x+
Orvandi said:
OK, are you sure you charged your phone? The RUU needs at least 30% battery. Also, select fastboot before you run the RUU.
After you click next, it should say that the RUU has recognized your device and it will run on its own.
Click to expand...
Click to collapse
yes of course my friend the phone had 90% the charge but you say the update shuold be in mode bootloader?
RUU appears to work, but stuck on bootscreen logo
I also installed the OTA update, which did eventually get to 4.2.2, but after a few days went into bootloop. I applied the RUU with no luck. It appears to work, but then reboots to the htc screen and hangs.
I've also unlocked, installed custom recoveries. TWRP or CWM no touch for the HTC One X+ At&t. both report errors of unable to mount /anything. TWRP refuses to sideload or install a ROM after adb push (which I can get to work sometimes). CWM will install from sideload, but ROM install (Elegancia 6.2) stops at 13.07% and hangs.
I have tried all of the steps from multiple posts in these forums and what works for others seems never to work for my phone. What could the problem be? Permanently unable to see the partitions? Something corrupt in hboot 1.73? Since I can't access the phone to change the USB debugging setting (not sure if it was checked or not) and I can't change the fastboot mode in settings (last set to fastboot enabled), perhaps trying a factory reset caused the problem (one thread mentioned factory reset won't work if the settings say fastboot within the phone).
No clue, so any insight would be helpful. At this point, after weeks of trying to fix this phone, I'm nearly ready to give up. I'm stubborn, but now I suspect there's an unsolvable problem that I just don't have the expertise to see.
mrg209 said:
I also installed the OTA update, which did eventually get to 4.2.2, but after a few days went into bootloop. I applied the RUU with no luck. It appears to work, but then reboots to the htc screen and hangs.
I've also unlocked, installed custom recoveries. TWRP or CWM no touch for the HTC One X+ At&t. both report errors of unable to mount /anything. TWRP refuses to sideload or install a ROM after adb push (which I can get to work sometimes). CWM will install from sideload, but ROM install (Elegancia 6.2) stops at 13.07% and hangs.
I have tried all of the steps from multiple posts in these forums and what works for others seems never to work for my phone. What could the problem be? Permanently unable to see the partitions? Something corrupt in hboot 1.73? Since I can't access the phone to change the USB debugging setting (not sure if it was checked or not) and I can't change the fastboot mode in settings (last set to fastboot enabled), perhaps trying a factory reset caused the problem (one thread mentioned factory reset won't work if the settings say fastboot within the phone).
No clue, so any insight would be helpful. At this point, after weeks of trying to fix this phone, I'm nearly ready to give up. I'm stubborn, but now I suspect there's an unsolvable problem that I just don't have the expertise to see.
Click to expand...
Click to collapse
I don´t konw
Go here and follow the instructions
http://forum.xda-developers.com/showthread.php?p=46123016
Sent from my HTC One X+ using XDA Premium 4 mobile app
no luck
Najmus said:
Go here and follow the instructions
http://forum.xda-developers.com/showthread.php?p=46123016
Sent from my HTC One X+ using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks, but I had no success with that procedure (see my post on page 46 of that thread).
Everything went smoothly, but still stuck at HTC logo.
mrg209 said:
Thanks, but I had no success with that procedure (see my post on page 46 of that thread).
Everything went smoothly, but still stuck at HTC logo.
Click to expand...
Click to collapse
Do you have the boot.img file of your previous software? I mean of 4.1.1 ??
If yes then you should flash that boot.img. then it should work
Sent from my HTC One X+ using XDA Premium 4 mobile app
working on it
Najmus said:
Do you have the boot.img file of your previous software? I mean of 4.1.1 ??
If yes then you should flash that boot.img. then it should work
Sent from my HTC One X+ using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks, attempting to do this, but I'm unable to unzip the stock roms in the 1.19 or 1.15 RUU to get that boot.img. I can unzip the 2.15 RUU rom just fine. Not sure what the problem is. I tried just running the earlier RUUs in the past, but they failed because it was the "wrong version" for my phone. Now I wonder if those failures were due to an invalid rom zip. Got these RUUs from AndroidRUU.
**edit: I cannot extract the roms (7z) for the earlier RUUs, only for 2.15. So I do not have access to the boot.img of the previous 4.1.1. Running the RUUs results in an "image error".