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
Related
Hboot 2.09
I've unlocked the bootloader and rooted my phone. I'm using the TWRP recovery, and am S-ON. I successfully flashed ViperMOD, but when I got to the start up screen, the touch screen and the haptic buttons would not respond. Thinking it was the ROM, I flashed CM10 only to find that I had the exact same problem there. I'm flashing the ROM first in TWRP and then the boot.img through fastboot. I know it is something software related because the touch functionality works in TWRP but not in any ROM.
Thanks in advance
Sent from my Galaxy Nexus using xda app-developers app
Bastakks said:
Hboot 2.09
I've unlocked the bootloader and rooted my phone. I'm using the TWRP recovery, and am S-ON. I successfully flashed ViperMOD, but when I got to the start up screen, the touch screen and the haptic buttons would not respond. Thinking it was the ROM, I flashed CM10 only to find that I had the exact same problem there. I'm flashing the ROM first in TWRP and then the boot.img through fastboot. I know it is something software related because the touch functionality works in TWRP but not in any ROM.
Thanks in advance
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Did you flash the full 3.16 OTA with the tp.img? tp.img works with TWRP 2.4.1.0 and any 3.16 based ROM but not any 3.15 ROM or AOSP rom. If you did, you have two choices. Either you can only use 3.16 roms, or you can try flashing this: http://themikmik.com/showthread.php?13192-FIRMWARE-S-OFF-1-12-HBOOT-ONLY-Jewel-Firmware-Collection-Latest-Radio-1-12-11-1210&p=286650&viewfull=1#post286650 That is the tp.img from 3.15 firmware and some have reported that it fixes this problem. You must flash this by renaming it to PJ75IMG.zip, putting it in the root of your external SD card, and going to bootloader. Upon request, accept the flash. Make sure you don't have another PJ75IMG.zip file in your external SD card. I'm not sure personally if this works but it's worth trying.
grizzlywan said:
Did you flash the full 3.16 OTA with the tp.img? tp.img works with TWRP 2.4.1.0 and any 3.16 based ROM but not any 3.15 ROM or AOSP rom. If you did, you have two choices. Either you can only use 3.16 roms, or you can try flashing this: http://themikmik.com/showthread.php?13192-FIRMWARE-S-OFF-1-12-HBOOT-ONLY-Jewel-Firmware-Collection-Latest-Radio-1-12-11-1210&p=286650&viewfull=1#post286650 That is the tp.img from 3.15 firmware and some have reported that it fixes this problem. You must flash this by renaming it to PJ75IMG.zip, putting it in the root of your external SD card, and going to bootloader. Upon request, accept the flash. Make sure you don't have another PJ75IMG.zip file in your external SD card. I'm not sure personally if this works but it's worth trying.
Click to expand...
Click to collapse
You have to be S-OFF to flash PJ75IMG.zip files in bootloader
If you have no way of flashing the 3.15 tp firmware, your only option is to flash a 3.16 rom.
My recommendation is in my signature below.
Sent from my MeanBean optimized and supercharged ElteVO.
I have done all of that. As the next post states, it doesn't work on S-ON devices. Looks like I'll be mucking about with a Linux live CD since I have 64windows and dirtyracun won't run on it.
Sent from my Galaxy Nexus using xda app-developers app
I am having exactly the same issue. I have successfully flashed several different roms (Charmeleon, UR Evo, Viper) and once loaded, I have no touchscreen response at all. At this point, I want to relock it, but when I attempt the RUU, the program doesn't see the phone (all drivers are installed). I can't get the phone to work so I had to buy a cheap tracfone to use in the mean time. Any suggestions? (I wish I'd saved a copy of the stock rom after unlocking but I thought it would work so I didn't)
Also, I have tried flashing MeanBean (which fails outright) and CyanogenMod, Avatar, and Evervolv (all of which hang out on the loading screen and never progress). I just want my phone back.
brinnanza said:
I am having exactly the same issue. I have successfully flashed several different roms (Charmeleon, UR Evo, Viper) and once loaded, I have no touchscreen response at all. At this point, I want to relock it, but when I attempt the RUU, the program doesn't see the phone (all drivers are installed). I can't get the phone to work so I had to buy a cheap tracfone to use in the mean time. Any suggestions? (I wish I'd saved a copy of the stock rom after unlocking but I thought it would work so I didn't)
Click to expand...
Click to collapse
Try going back and flashing a 3.15 based ROM. What version of TWRP are you on?
Sent from my EVO using xda premium
Same here... very frustrating.
I've have flashed Viper ROM which installs "apparently fine" until its time to touch the screen. Mean bean fails right out the box and wont install. TWRP works perfect with the touch panel. Also flashed Miklatte and the phone booted to a non responsive touch panel.:silly: I don,t care about S- OFF right now. I need this phone working. Any help is appreciated. thanks.
Im on Hboot 2.09 / 3.15.651.6 / unlocked S-ON.
lg31376 said:
I've have flashed Viper ROM which installs "apparently fine" until its time to touch the screen. Mean bean fails right out the box and wont install. TWRP works perfect with the touch panel. Also flashed Miklatte and the phone booted to a non responsive touch panel.:silly: I don,t care about S- OFF right now. I need this phone working. Any help is appreciated. thanks.
Im on Hboot 2.09 / 3.15.651.6 / unlocked S-ON.
Click to expand...
Click to collapse
What baseband (radio) are you on? If you're on the baseband ending in 1210, you can only run ROM's based on software version 3.16 and you must use TWRP 2.4 or newer.
Here is some info that might be useful:
http://forum.xda-developers.com/showthread.php?t=2256478
Also keep in mind that being S-on you essentially have to flash MeanBean twice-once to install the ROM, then again to install the kernel.
Sent from my EVO using xda premium
Save yourself time and the headache, just get S-Off. It's too easy now.
http://moonshine.io/
Enjoy.
FinZ28 said:
What baseband (radio) are you on? If you're on the baseband ending in 1210, you can only run ROM's based on software version 3.16 and you must use TWRP 2.4 or newer.
Here is some info that might be useful:
http://forum.xda-developers.com/showthread.php?t=2256478
Also keep in mind that being S-on you essentially have to flash MeanBean twice-once to install the ROM, then again to install the kernel.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
My radio : 1. 12. 11. 1119
TWRP v2.5.0.0
HBOOT: 2.09
Open DSP- v31.1.0.45.0815
Sorry guys I should explain my case further. I bought this phone from ebay. It was stuck on a soft brick which Bigdady619 helped me get out of. (Thanks again Bro!). So this is my current problem. Phone is unlocked S-ON. It was already on current HBOOT 2.09 and v 3.15.651.6. Now I need S-OFF but tried to do dirtyracun (on UBUNTU live CD) several times and ended with a "failed connection test error " at step14. went to IRC channel and they said is USB related issue. I have USB 2 and Good USB cable. Dont have HTC original but I dont understand why it has to be that one. I'm an audio and electronics engineer and know how USB works. Anyways thats whats keeping me from the holy grail! On the other side I cant flash touchpanel firmware cause Im not S-OFF. I've spent ****less hours on this forums and havent found an answer to the touch screen problem, other than flashing the firmware, which some people with the same problem have done and still no fix. At the moment I have a what seems to be a perfectly working Viper 4G 3.1.5 installed. Its the only ROM that would install correctly anyways. Touch panel works only on TWRP. I will try dirtyracun one more time and lets see what happens. thanks for paying attention to this aggravating problem.
***Update*** I just finished doing dirtyracun process. Problem: Step 14. Enable USB Debugging on your device. Once I flash the RUU ( step 11) The phone reboots to ROM (Viper 4G) with USB Debugging disabled. Due to touch panel issue I cant enable it and finish up the process! Apparently after burning Google down theres no way to enable USB Debug through adb or fastboot. Im stuck!
Update
***Update*** I just finished doing dirtyracun process. Problem: Step 14. Enable USB Debugging on your device. Once I flash the RUU ( step 11) The phone reboots to ROM (Viper 4G) with USB Debugging disabled. Due to touch panel issue I cant enable it and finish up the process! Apparently after burning Google down theres no way to enable USB Debug through adb or fastboot. Im stuck!
Yessssss!!!!
FINALLY S-OFF ACHOEVED through Facepalm!!!! thanx XDA! Now to deal with this touchpanel issue.
---------- Post added at 10:02 PM ---------- Previous post was at 09:24 PM ----------
Wooohoooo!! flashed the touchpanel firmware and BAM!! Evo LTE on DECK!! Thanx XDA U guys Rock!
lg31376 said:
FINALLY S-OFF ACHOEVED through Facepalm!!!! thanx XDA! Now to deal with this touchpanel issue.
---------- Post added at 10:02 PM ---------- Previous post was at 09:24 PM ----------
Wooohoooo!! flashed the touchpanel firmware and BAM!! Evo LTE on DECK!! Thanx XDA U guys Rock!
Click to expand...
Click to collapse
Sweet good job :thumbup::beer:
Sent from my HTCONE using xda app-developers app
can i use the older tp firmware to run 3.16 based roms also? or just on 3.15, cm and aosp?
Had the same issues after s off had to downgrade firmware to 3.15 but everything is sweet now captain throwback has a img you can flash by putting on root of sd and starting bootloader
Sent from my EVO using xda app-developers app
generalmofo said:
can i use the older tp firmware to run 3.16 based roms also? or just on 3.15, cm and aosp?
Click to expand...
Click to collapse
Yes. Old tp works with new roms, but new tp doesn't work with old roms/recovery.
______________________________
HTC Evo 4G LTE
~Asking for the 'best rom' is just like asking who's the best Pokémon. When you get it, sometimes you realize that its not all that great in your opinion. Try to flash 'em all! ~
aarsyl said:
Yes. Old tp works with new roms, but new tp doesn't work with old roms/recovery.
______________________________
HTC Evo 4G LTE
~Asking for the 'best rom' is just like asking who's the best Pokémon. When you get it, sometimes you realize that its not all that great in your opinion. Try to flash 'em all! ~
Click to expand...
Click to collapse
Thank you.
Hey guys,
I was running the latest Viper rom. Every great once in a while the phone would just turn off. I could get it back fine and this happened about 5-6 times. Today the phone got stuck in a boot loop. I figured something went wrong.
I attempted to restore the phone to stock using the RUU thread found here: http://forum.xda-developers.com/showthread.php?t=2152993
I restored it once fine, said it was good. Phone only rebooted over and over. The HTC logo came up 3-4 times then screen went blank. So I flashed again. Same thing, nothing.
Now I had been playing around and think I updated my radio. Now the RUU from that thread above says it cannot upgrade my phone. I can get to fastbook and lock and unlock the bootloader. I did install latest TWRP but it never enters recovery. I had hoped to just install a basic rom from the 2.04 update and be done. But I cannot get into recovery.
I'm stuck and don't know what else to do. Is there and RUU file like the one above for the new 2.04?
I still think something else is wrong with this phone. Somehow doubt VZW will take it back and exchange.
S-ON
Phone displays HBOOT-1.33.0001
RADIO-1.01.01.0110
Any ideas what I can do next please?
I think the radio got updated when I tried to do S-OFF. Instead of an error at step 3 it flashed. Now I've gone back and tried it again and though I get the proper errors is still shows S-ON. Maybe this isn't even needed. I think my days of tinkering with Android should be over. I can follow guides and such
When I try to enter recovery for TWRP I get a lot of colored lines. Going to try reflashing that and see what gives. I feel that if I could get into TWRP and get a rom file on the phone since I cannot get into Android I might have a chance.
Tersanyus said:
I think the radio got updated when I tried to do S-OFF. Instead of an error at step 3 it flashed. Now I've gone back and tried it again and though I get the proper errors is still shows S-ON. Maybe this isn't even needed. I think my days of tinkering with Android should be over. I can follow guides and such
When I try to enter recovery for TWRP I get a lot of colored lines. Going to try reflashing that and see what gives. I feel that if I could get into TWRP and get a rom file on the phone since I cannot get into Android I might have a chance.
Click to expand...
Click to collapse
Did you take the verizon update as you mentioned 2.04? If you did you will have to wait a bit yet to root again. Your only option would be stock verizon. Their software update basically closed the previously open window. If not...You HAVE updated radio per the # you posted, not sure if that really matters with regard to recovery. It seems like you have compounded many issues. I would try relocking bootloader and flash stock RUU again. Try to get back to stock verizon. If that's a no go, would try reflashing old radio and try stock ruu. How are you getting to try bootloader/recovery, turning on phone holding down vol button? Last ditch if it's says s-on and locked, I think you would be ok to try for a new phone.
I did not take the OTA from Verizon. I never got any prompt for an update. I did the updates for Viper that turned I think just turned that off.
Getting to bootloader is fine. I can lock it and unlock it fine. I know the RUU only loads if locked. I know recovery can only be installed if unlocked I believe. And yes I do that from vol down plus power button.
If I use newest TWRP recovery just gives a whole bunch of colored lines. If I try 2.4.0.0 I can see TWRP come up briefly then the phone reboots again.
The RUU exe file just now gives error 158. Basically it thinks it is not the correct ROM
I found the 1.15 radio but it won't flash. http://forum.xda-developers.com/showpost.php?p=38379254&postcount=19
Just gives error of FAILED remote: 92 supercid
Tersanyus said:
The RUU exe file just now gives error 158. Basically it thinks it is not the correct ROM
I found the 1.15 radio but it won't flash. http://forum.xda-developers.com/showpost.php?p=38379254&postcount=19
Just gives error of FAILED remote: 92 supercid
Click to expand...
Click to collapse
Is there a boot.img for the ruu? Maybe the previous boot image is still directing the process, a thought at least. Also that error 92 cid MAY be the issue, Do you have the newest one on (cid)? I had a lot of issues getting s-off and had to run supercid again to run the process after several error 92 messages. I would look at the whole s-off thread in original dev section maybe some answers in there or a direction to head in.
---------- Post added at 10:39 AM ---------- Previous post was at 09:48 AM ----------
rootntootn said:
Is there a boot.img for the ruu? Maybe the previous boot image is still directing the process, a thought at least. Also that error 92 cid MAY be the issue, Do you have the newest one on (cid)? I had a lot of issues getting s-off and had to run supercid again to run the process after several error 92 messages. I would look at the whole s-off thread in original dev section maybe some answers in there or a direction to head in.
Click to expand...
Click to collapse
Can you get to fastboot? adb can communicate with the phone? Says in red fastboot usb? Also how are you doing RUU, assuming your using executable from your pc? Forgot to ask..
Yes I can get to fastboot fine. I do a "fastboot devices" and it is read. adb doesn't seem to do anything though. The RUU is the .exe I found.
For the cid I did the old one so mine reads all 1's. I didn't think I could so the new cid as I cannot boot into Android at all.
Ok success!! Yes.
I did the S-OFF directions once. Nothing, no change.
Did it again this time it booted to factory rom.
I am S-OFF cid is all ones.
I got the prompt for the OTA update, took ot, phone rebooted to recovery, TWRP, then nothing.
Wifi not working, I know I read about that so looks like I have a little more work.
Tersanyus said:
Ok success!! Yes.
I did the S-OFF directions once. Nothing, no change.
Did it again this time it booted to factory rom.
I am S-OFF cid is all ones.
I got the prompt for the OTA update, took ot, phone rebooted to recovery, TWRP, then nothing.
Wifi not working, I know I read about that so looks like I have a little more work.
Click to expand...
Click to collapse
Not sure how you got there s-off should have all 2's....but it sounds like progress. If you are back to recovery and have a rom to flash in your phone that's great...but you'll need adb working to flash the image file that's associated with it, that will likely fix your wifi issue as well. Even with S-off most of the roms still need to have their respective image files flashed but I am unsure about stock RUU, someone with more experience may know that answer and can maybe steer you in the right direction...
Tersanyus said:
Ok success!! Yes.
I did the S-OFF directions once. Nothing, no change.
Did it again this time it booted to factory rom.
I am S-OFF cid is all ones.
I got the prompt for the OTA update, took ot, phone rebooted to recovery, TWRP, then nothing.
Wifi not working, I know I read about that so looks like I have a little more work.
Click to expand...
Click to collapse
If you have a custom recovery then you can't install the ota. If you want the ota stuff you can install the Rom kernel and radio from it.
As far as wifi not working, just flash a kernel, right now it sounds like you have the modules from one kernel and the boot.img from another.
Sent from my HTC6435LVW using xda app-developers app
---------- Post added at 09:43 PM ---------- Previous post was at 09:40 PM ----------
rootntootn said:
Not sure how you got there s-off should have all 2's....but it sounds like progress. If you are back to recovery and have a rom to flash in your phone that's great...but you'll need adb working to flash the image file that's associated with it, that will likely fix your wifi issue as well. Even with S-off most of the roms still need to have their respective image files flashed but I am unsure about stock RUU, someone with more experience may know that answer and can maybe steer you in the right direction...
Click to expand...
Click to collapse
You don't need all 2s to get s off, you can do it with all ones without a problem.
Sent from my HTC6435LVW using xda app-developers app
Bigandrewgold said:
If you have a custom recovery then you can't install the ota. If you want the ota stuff you can install the Rom kernel and radio from it.
As far as wifi not working, just flash a kernel, right now it sounds like you have the modules from one kernel and the boot.img from another.
Sent from my HTC6435LVW using xda app-developers app
---------- Post added at 09:43 PM ---------- Previous post was at 09:40 PM ----------
You don't need all 2s to get s off, you can do it with all ones without a problem.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
BTW There was nothing wrong with your phone, it's just that when you restored, you needed to flash the boot.img from your rom that you restored. It was most likely a kernel issue that we could correct with viper.
It sounds like you just need to install the matching rom and boot.img. If you're s off, just fastboot flash the boot.img for whatever rom you currently have installed. For the OTA update, you can install the radios without an RUU if you're s off.
I ran for several hours and several reboots on the RUU .exe file. When I downloaded a custom rom from http://forum.xda-developers.com/showthread.php?t=2150262 - That fan fine for an hour or so. Then boot loop over and over again. Thankfully I made a backup in twrp. I restored that and all is well.
I can't stand this factory rom, the part that really annoys me, besides the VZW bloat, is the recent apps button. For over a year with other HTC's I am used to making that the menu button. Had that in the custom rom.
So it looks like that rebooting loop just means I need to fastboot the boot.img?
I go back to the rom I linked about and fastboot the boot.img. I really liked viper rom but am going to stick to stock that is rooted and debloated.
My cid is all 1's since I did that before all this OTA came out. I did that about 3 weeks ago the day I got the phone.
Thanks for the tips. I'll let you know what happens when I go back to the rom above.
Bigandrewgold said:
If you have a custom recovery then you can't install the ota. If you want the ota stuff you can install the Rom kernel and radio from it.
As far as wifi not working, just flash a kernel, right now it sounds like you have the modules from one kernel and the boot.img from another.
Sent from my HTC6435LVW using xda app-developers app
---------- Post added at 09:43 PM ---------- Previous post was at 09:40 PM ----------
You don't need all 2s to get s off, you can do it with all ones without a problem.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Sorry about the 2's info but read that the older cid apk would no longer work (from thread below) and myself put on the new one which yields the all 2's. Bottom line, glad you made progress, hopefully problem resolved
http://forum.xda-developers.com/showthread.php?t=2109862
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
So I haven't really found anyone with as specific a situation I'm in so I figured I'd make a new thread.
I was running a CM10.1 build from late July, which still had some bugs but was bearable. I upgraded to CM10.2 to try it out, but it was buggier than the CM10.1 build. I saw that the bugs were fixed in the latest build of CM10.1 so I flashed that. Since then I've been stuck in Roaming and can't activate my phone.
Each time I flashed I restored my 100% stock backup (I have a nandroid from the day I got the phone). Every flash was a clean install wiping data/cache/dalvik. Was first roaming when I reverted back to CM10.1, but restoring my backup and even flashing CM10.2 again I'm roaming still.
Basically, once I was roaming, I haven't stopped regardless of ROM.
And I'm sure someone will ask, I have S-off.
How do I go about fixing this?
EDIT: I've tried a clean flash of the same ROM with the sim card removed and tried changing the subscription type after like I've seen in another thread, but this did not work.
Bartikus said:
So I haven't really found anyone with as specific a situation I'm in so I figured I'd make a new thread.
I was running a CM10.1 build from late July, which still had some bugs but was bearable. I upgraded to CM10.2 to try it out, but it was buggier than the CM10.1 build. I saw that the bugs were fixed in the latest build of CM10.1 so I flashed that. Since then I've been stuck in Roaming and can't activate my phone.
Each time I flashed I restored my 100% stock backup (I have a nandroid from the day I got the phone). Every flash was a clean install wiping data/cache/dalvik. Was first roaming when I reverted back to CM10.1, but restoring my backup and even flashing CM10.2 again I'm roaming still.
Basically, once I was roaming, I haven't stopped regardless of ROM.
And I'm sure someone will ask, I have S-off.
How do I go about fixing this?
EDIT: I've tried a clean flash of the same ROM with the sim card removed and tried changing the subscription type after like I've seen in another thread, but this did not work.
Click to expand...
Click to collapse
This happened to me randomly. Only thing that works is RUU back to stock and go through the motions. You won't lose S-OFF, so you can then come back.
hurrrtin said:
This happened to me randomly. Only thing that works is RUU back to stock and go through the motions. You won't lose S-OFF, so you can then come back.
Click to expand...
Click to collapse
I need to RUU all the down to 1.15 correct? Then will I need to Moonshine again?
Bartikus said:
I need to RUU all the down to 1.15 correct? Then will I need to Moonshine again?
Click to expand...
Click to collapse
If you are S-OFF, then yes- RUU back down to 1.15. You won't need to moonshine again.
---------- Post added at 12:18 PM ---------- Previous post was at 12:13 PM ----------
hurrrtin said:
If you are S-OFF, then yes- RUU back down to 1.15. You won't need to moonshine again.
Click to expand...
Click to collapse
It might take a little while for it to change from roaming back to normal. Just give it time after you RUU.
Bartikus said:
So I haven't really found anyone with as specific a situation I'm in so I figured I'd make a new thread.
I was running a CM10.1 build from late July, which still had some bugs but was bearable. I upgraded to CM10.2 to try it out, but it was buggier than the CM10.1 build. I saw that the bugs were fixed in the latest build of CM10.1 so I flashed that. Since then I've been stuck in Roaming and can't activate my phone.
Each time I flashed I restored my 100% stock backup (I have a nandroid from the day I got the phone). Every flash was a clean install wiping data/cache/dalvik. Was first roaming when I reverted back to CM10.1, but restoring my backup and even flashing CM10.2 again I'm roaming still.
Basically, once I was roaming, I haven't stopped regardless of ROM.
And I'm sure someone will ask, I have S-off.
How do I go about fixing this?
EDIT: I've tried a clean flash of the same ROM with the sim card removed and tried changing the subscription type after like I've seen in another thread, but this did not work.
Click to expand...
Click to collapse
I'm having the exact same issue after doing the same thing you did, not sure where to go with it at this point, nothing is working
PhantomApollyon said:
I'm having the exact same issue after doing the same thing you did, not sure where to go with it at this point, nothing is working
Click to expand...
Click to collapse
Did you try to RUU back to 1.15? I just tried running it and it crashed, not sure if it's my computer or what
hurrrtin said:
If you are S-OFF, then yes- RUU back down to 1.15. You won't need to moonshine again.
Click to expand...
Click to collapse
I tried running the RUU from here http://forum.xda-developers.com/showthread.php?t=2017525
I ignored the first part about relocking since I assumed since I have s-off I don't need to, and I immediately tried to run the .exe as admin and it crashed.
UPDATE: I've relocked it now but the RUU still crashes before doing anything.
Bartikus said:
I tried running the RUU from here http://forum.xda-developers.com/showthread.php?t=2017525
I ignored the first part about relocking since I assumed since I have s-off I don't need to, and I immediately tried to run the .exe as admin and it crashed.
UPDATE: I've relocked it now but the RUU still crashes before doing anything.
Click to expand...
Click to collapse
try grabbing the RUU from the blue link in my sig
.torrented said:
try grabbing the RUU from the blue link in my sig
Click to expand...
Click to collapse
Downloading the RUU now. I've also tried flashing the 1.15 hboot and recovery, but they don't seem to have done anything. I'm still on 2.06... I unlocked my phone originally with moonshine, so my bootloader used to say moonshine s-off. now it says tampered/locked so I think hboot worked, but the recovery doesn't seem to have done anything.
UPDATE: The RUU ran it's course. Seems like the file for the other link was just bad (I had downloaded it twice). The phone is attempting to activate now, but it still can't get a signal. I know the signal at my house is usually pretty bad, but leaving it on the window sill usually does the trick. If worse comes to worse, could I at this point return it to Verizon without them knowing what's up?
Bartikus said:
Downloading the RUU now. I've also tried flashing the 1.15 hboot and recovery, but they don't seem to have done anything. I'm still on 2.06... I unlocked my phone originally with moonshine, so my bootloader used to say moonshine s-off. now it says tampered/locked so I think hboot worked, but the recovery doesn't seem to have done anything.
UPDATE: The RUU ran it's course. Seems like the file for the other link was just bad (I had downloaded it twice). The phone is attempting to activate now, but it still can't get a signal. I know the signal at my house is usually pretty bad, but leaving it on the window sill usually does the trick. If worse comes to worse, could I at this point return it to Verizon without them knowing what's up?
Click to expand...
Click to collapse
the point of the 1.15 hboot is so the RUU works... if you want to return to stock to take to vzw I would follow the restore guide, i believe its posted in the regular dev section and not the original dev section
edit* this one right here: http://forum.xda-developers.com/showthread.php?t=2293919
.torrented said:
the point of the 1.15 hboot is so the RUU works... if you want to return to stock to take to vzw I would follow the restore guide, i believe its posted in the regular dev section and not the original dev section
edit* this one right here: http://forum.xda-developers.com/showthread.php?t=2293919
Click to expand...
Click to collapse
Yeah the RUU seemed to work, I just still can't get a signal. Phone says no service and I can't get past the activation screen. I say "seemed" to work because I can't check in settings because I can't get past the activation... but the bootloader looks like stock again, whereas it said tampered before the RUU.
Thank you for the help by the way, I appreciate it.
RUU worked, I'm on 1.15. However, it didn't solve my no service problem. Could this be as trivial as a SIM problem? Is there anything else it might be?
Reset the Phone
Bartikus said:
RUU worked, I'm on 1.15. However, it didn't solve my no service problem. Could this be as trivial as a SIM problem? Is there anything else it might be?
Click to expand...
Click to collapse
After RUU you must Reset the phone from STOCK recovery,
finanandroid said:
After RUU you must Reset the phone from STOCK recovery,
Click to expand...
Click to collapse
Worked like a charm, thanks!
Bartikus said:
Worked like a charm, thanks!
Click to expand...
Click to collapse
U welcome! Glad you finally back on business :good:
finanandroid said:
U welcome! Glad you finally back on business :good:
Click to expand...
Click to collapse
Where can I find the STOCK recovery? I've been going crazy with this stock on roam thing.
RUU to get back to Stock Recovery
chipymunk said:
Where can I find the STOCK recovery? I've been going crazy with this stock on roam thing.
Click to expand...
Click to collapse
In order to recovery or restore the original phone factory setting you have to do RUU and Reset Phone*** is the way to get back
Stock recovery(= reset phone) to work properly. Even if you are on a Stock Rom it has a custom recovery so doing factory reset wont
work to restore the original phone setting.
after RUU you must do a phone reset either from setting>back up & reset or from the bootloader factory reset is the same Stock Recovery.
I read somewhere that flashing this Rom Stock rooted fix a roaming thing so you can give it a shot http://forum.xda-developers.com/showthread.php?t=2471836
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.