I'm sure this is an annoying noob post but I'm going to instead post here before I brick yet another evo.
got a brand new evo in the mail from asurion.
*I unlocked through HTC dev.
*Rooted using This method
saw superuser on my stock untouched rom and was pleased.
proceeded to flash CM10 with no backup like an idiot.
cm10 animation bootloop..
found a thread saying Viper rom will flash because I'm still S-on.
Now stuck on Viper rom for 4 days with "1x" service when it used to be full bars 4G.
updated profile and prl on Viper rom. still no data when I am outside.
Tried Using the stock RUU.
Failed and told me to get the right version of the RUU.
tempted to keep trying things till it works again, but that's how I've ended up having to replace my phone in the past.
I am not good at rooting and need some help before I brick another phone..
while grabbing info I saw there was a system update for Viper Rom from 3.1.5 to 3.1.6
going to hold off as it will probably **** my kernel / radios even further..
Info:
Kernel 3.4.10-g19136fe [email protected] #1 SMP PREEMPT
baseband version: 1.12.11.1210
PRI version: 2.97_003
PRL version: 25015
Software version Viper4G 3.1.5
TWRP: 2.5.5.0
***tampered***
***unlocked***
JEWEL PVT SHIP S-ON RL
Hboot-2.09.0000
Radio-1.12.11.1210
OpenDSP-v31.1.0.45.0815
eMMC-boot
oct 18 2012
Any help or advice on what to do to get my phone working again would be super helpful.
Ideally I'd like to install a pure version of android, or cm10.1 with full service and no radio issues.
Click the link in my sig... Read the faqs on the bottom of post one... Follow the steps and report back.
Sent from my EVO
gunfromsako said:
Click the link in my sig... Read the faqs on the bottom of post one... Follow the steps and report back.
Sent from my EVO
Click to expand...
Click to collapse
I'm stuck at "hands free activation" at the end of step 3.
says "contacting network..." for about 5 minutes now.
Let it keep doing its thing. I have had it take forever and fail then work on the 2nd retry. Go through all 5 attempts and make sure you are in a good service area.
Edit: you will need to go on to step 4
Make a backup!
Sent from my EVO
gunfromsako said:
Let it keep doing its thing. I have had it take forever and fail then work on the 2nd retry. Go through all 5 attempts and make sure you are in a good service area.
Edit: you will need to go on to step 4
Make a backup!
Sent from my EVO
Click to expand...
Click to collapse
UPDATE: after step 3 it said ""your activation could not be completed. To try again, Chose "update profile" in the system updates area of settings if the problem persists, you may need to contact Customer Service: error code:1012
going to update profile and reboot, if no then I will backup and try the final solution.
Update profile probably won't work. Don't forget to nandriod and backup your internal sd...
Sent from my EVO
update
after step 4 while updating profile I got "data call failure" Error Code 131. Unable to establish wireless data connection. If the problem persists, please contact your mobile phone company. then after I pressed "dismiss" it showed "PRL Update complete"
full bars of 1x. back to square one, heh.
I'm pretty sure this is a radio mismatch issue but I'm too dumb to solve it.
I just can't seem to find the right RUU to get it back to how it was when I got it in the mail 4 days ago.
It should not update profile after step 4. It's should go through wireless activation, then check for prl update, then check for firmware update. So does it make it through wireless activation?
Sent from my EVO
---------- Post added at 09:26 PM ---------- Previous post was at 08:49 PM ----------
Also it looks like your firmware is up to date so I'm guessing your phone came with the 3.16 base already on it that's why cm 10.1 will not boot. The only way for you to run an aosp rom is to s off and downgrade your touch panel drivers. You have no radio mismatch issues as you are on the same radio/pri as me. Which are both up to date the only difference is I'm s off without the new tp.img. Also there is no RUU for 3.16 available only 3.15 which I'm guessing you tried and failed at. Roms Do Not mess with radios or pri, I would flash the stock rooted rom and try again.
Sent from my EVO
gunfromsako said:
It should not update profile after step 4. It's should go through wireless activation, then check for prl update, then check for firmware update. So does it make it through wireless activation?
Sent from my EVO
---------- Post added at 09:26 PM ---------- Previous post was at 08:49 PM ----------
Also it looks like your firmware is up to date so I'm guessing your phone came with the 3.16 base already on it that's why cm 10.1 will not boot. The only way for you to run an aosp rom is to s off and downgrade your touch panel drivers. You have no radio mismatch issues as you are on the same radio/pri as me. Which are both up to date the only difference is I'm s off without the new tp.img. Also there is no RUU for 3.16 available only 3.15 which I'm guessing you tried and failed at. Roms Do Not mess with radios or pri, I would flash the stock rooted rom and try again.
Sent from my EVO
Click to expand...
Click to collapse
Okay I'll give that a shot, thanks for your help.
If memory serves I was even lower than 3.16 when it first arrived.
I'll look for a rom like "stock with root"
time to give it another whirl.
t3chn0v1k1ng said:
Okay I'll give that a shot, thanks for your help.
If memory serves I was even lower than 3.16 when it first arrived.
I'll look for a rom like "stock with root"
time to give it another whirl.
Click to expand...
Click to collapse
Well your firmware is up to date so either it came with the 3.16 base or you updated your firmware via ota... Either way viper boy has a stock rooted rom in the Android development section.
Flowed from my Jewel using Tapatalk 2
gunfromsako said:
Well your firmware is up to date so either it came with the 3.16 base or you updated your firmware via ota... Either way viper boy has a stock rooted rom in the Android development section.
Flowed from my Jewel using Tapatalk 2
Click to expand...
Click to collapse
Tried flashing stock 3.15.651.16_Deodex.zip... here is a recreation of my TWRP screen:
checking md5 file .. no md5 found
***********************************************************
Stock 3.15.651.16 Jelly Bean Deodex by -viperboy-
************************************************************
Deleting Cache and Dalvik-cache...
Extracting FIles...
E: error executing updater binary in zip
Error flashing zip '/sdcard/Stock 3.15.651.16_Deodex.zip
updating partition details...
FAILED
could this be because I'm S-on?
Should I have some version of the "PJ7510 zip" on my sd card?
Sorry I'm so lost.
All replies are a huge help.
EDIT: I think I'm figuring it out. going to attempt RUU for 3.15
t3chn0v1k1ng said:
Tried flashing stock 3.15.651.16_Deodex.zip... here is a recreation of my TWRP screen:
checking md5 file .. no md5 found
***********************************************************
Stock 3.15.651.16 Jelly Bean Deodex by -viperboy-
************************************************************
Deleting Cache and Dalvik-cache...
Extracting FIles...
E: error executing updater binary in zip
Error flashing zip '/sdcard/Stock 3.15.651.16_Deodex.zip
updating partition details...
FAILED
could this be because I'm S-on?
Should I have some version of the "PJ7510 zip" on my sd card?
Sorry I'm so lost.
All replies are a huge help.
Click to expand...
Click to collapse
Downgrade to twrp 2.4.4, I believe and try again. Also make sure to check the md5 it may have been a bad DL. I have also had to move roms from internal to external, and vise versa, to get them to flash. I'm shooting from the hip here...
Sent from my EVO
gunfromsako said:
Downgrade to twrp 2.4.4, I believe and try again. Also make sure to check the md5 it may have been a bad DL. I have also had to move roms from internal to external, and vise versa, to get them to flash. I'm shooting from the hip here...
Sent from my EVO
Click to expand...
Click to collapse
yea I'm getting the feeling the refurbished phone they gave me has bad memory chips and usb controllers.
Usb error when trying the RUU.
I'll try moving the roms around.
t3chn0v1k1ng said:
yea I'm getting the feeling the refurbished phone they gave me has bad memory chips and usb controllers.
Usb error when trying the RUU.
I'll try moving the roms around.
Click to expand...
Click to collapse
I had a similar prob a few hours ago.
I just rooted new Evo LTE that arrived w/ 3.16.651 & 2.09 B.L.
I unlocked (still S-on) and flashed MeanBean w/NO PROBLEMS. All was good. Using WiFi tethering to watch Netflix in HD on 50" plasma kind of good.
Gained S-off this morning, re-flashed MeanBean (w/out running backup, of course). All was good again.
Then I noticed my radio, PRL, etc were not the most current, so I flashed the new PJ75IMG.zip. Radios were current but had near zero connectivity. 1x running at 2-4 kbs. No 4G LTE signal.
I tried the ##72786#, failed w/ error 1012.
Tried again, it failed no network detected...
Went to settings, updates, hit profile... Profile was updated!
Updated PRL... PRL was updated
Updated profile again.
##72786# then worked.
Went into recovery, fixed permissions & rebooted.
It's all now working flawlessly. 4G connects, WiFi tether rocks, through speeds are great.
Just keep plugging at reprovisioning (hands-free activation).
I don't know from AOSP ROMS, But if only for the short term, try to flash MeanBean. It might be able to get you out of the woods.
Definitely try different roms. I've had my data crap out for no reason and have to ##786# twice to get it back. Honestly you might have to call sprint. I have never had to but there are always those circumstances...
Sent from my EVO
tmwilsoniv said:
I had a similar prob a few hours ago.
I just rooted new Evo LTE that arrived w/ 3.16.651 & 2.09 B.L.
I unlocked (still S-on) and flashed MeanBean w/NO PROBLEMS. All was good. Using WiFi tethering to watch Netflix in HD on 50" plasma kind of good.
Gained S-off this morning, re-flashed MeanBean (w/out running backup, of course). All was good again.
Then I noticed my radio, PRL, etc were not the most current, so I flashed the new PJ75IMG.zip. Radios were current but had near zero connectivity. 1x running at 2-4 kbs. No 4G LTE signal.
I tried the ##72786#, failed w/ error 1012.
Tried again, it failed no network detected...
Went to settings, updates, hit profile... Profile was updated!
Updated PRL... PRL was updated
Updated profile again.
##72786# then worked.
Went into recovery, fixed permissions & rebooted.
It's all now working flawlessly. 4G connects, WiFi tether rocks, through speeds are great.
Just keep plugging at reprovisioning (hands-free activation).
I don't know from AOSP ROMS, But if only for the short term, try to flash MeanBean. It might be able to get you out of the woods.
Click to expand...
Click to collapse
Many thanks! I can't seem to get ANY roms to flash.
Mean bean it is.
Get S-off using the Moonshine method and save yourself a lot of headache. It'll give you way more options to anything you want. With S-Off everything is butta.
Sent from my EVO using xda app-developers app
gunfromsako said:
Definitely try different roms. I've had my data crap out for no reason and have to ##786# twice to get it back. Honestly you might have to call sprint. I have never had to but there are always those circumstances...
Sent from my EVO
Click to expand...
Click to collapse
UPDATE SOLVED:
after failing at flashing another stock Rom I recovered back to viper. I went about my errands and while driving out of the blue I had full 4g again.
I think maybe the towers had trouble doing a hands free activation twice in such a short duration from eachother out of the box.
Thanks again to all who offered help, no idea why it works now!
t3chn0v1k1ng said:
UPDATE SOLVED:
after failing at flashing another stock Rom I recovered back to viper. I went about my errands and while driving out of the blue I had full 4g again.
I think maybe the towers had trouble doing a hands free activation twice in such a short duration from eachother out of the box.
Thanks again to all who offered help, no idea why it works now!
Click to expand...
Click to collapse
Glad it's fixed man... Sprint can be a pain in the A
Flowed from my Jewel using Tapatalk 2
gunfromsako said:
Glad it's fixed man... Sprint can be a pain in the A
Flowed from my Jewel using Tapatalk 2
Click to expand...
Click to collapse
I can't believe it. made zero changes. back to 1x after 1 week of perfect 4g.
What have I done to anger the android GODS!!!?????!
Related
So I was driving down the road today and noticed that I could do an OTA...being extremely green to HTC, android, and rooting...I accepted. Then I noticed that things weren't working like they were before the update. Doh!
Came home...hopped on here and noticed that was very stupid. No more root.
So I have S-Off and bootloader unlocked (did when I got home) but no root. Is there a way for me to get it back?
Thanks in advance!
Nevermind, was useless.
roids87 said:
http://forum.xda-developers.com/showthread.php?t=1671577
That thread will help you out.
Click to expand...
Click to collapse
That method no longer works on the ota update.
If you're S-Off with bootloader unlocked all you have to do is grab a custom recovery and flash a superuser package. Since you're green here are some links.
http://forum.xda-developers.com/showthread.php?t=1675738 - recovery
http://forum.xda-developers.com/showthread.php?t=1538053 - superuser
OTA and new to root
I too am new to rooting my device. I rooted with RegawMod and love it but I can't get the OTA update to even work. I tried to download the jewel update from this website
http://forum.xda-developers.com/showthread.php?t=1766628
I couldn't figure out what to open to make it work. I am new to the rooting so I could use some help.
thanks
triscuit1983 said:
If you're S-Off with bootloader unlocked all you have to do is grab a custom recovery and flash a superuser package. Since you're green here are some links.
http://forum.xda-developers.com/showthread.php?t=1675738 - recovery
http://forum.xda-developers.com/showthread.php?t=1538053 - superuser
Click to expand...
Click to collapse
Thanks! This is great! Going to check it out now.
Same here. I am rooted running MeanRom and today when the ota started, I cancelled it thinking it might mess something up with my root. I went to do the update this evening because I read users were getting better 3g speeds and what not, but when I go to install, it just reboots into recovery and so I followed with a reboot system in twrp and when it fully reboots, I get nothing.
Sent from my EVO 4G LTE using XDA-Developer App
Same here. On fresh rom. Just goes to recovery and doesn't finish the update. Any ideas?
EVOMIKE025 said:
Same here. I am rooted running MeanRom and today when the ota started, I cancelled it thinking it might mess something up with my root. I went to do the update this evening because I read users were getting better 3g speeds and what not, but when I go to install, it just reboots into recovery and so I followed with a reboot system in twrp and when it fully reboots, I get nothing.
Sent from my EVO 4G LTE using XDA-Developer App
Click to expand...
Click to collapse
Sent from my EVO using xda app-developers app
I would say to just wait until the devs update the roms we are using with the ota. It seems as though I'm reading its doing something with the bootloader and installing a stock rom?
Sent from my EVO 4G LTE using XDA-Developer App
I'm thinking if I lock and unroot, I should be able to get update? I tried just going ahead with update but it keeps booting to twrp. I can reunlock and root after right? Im too novice to use s-off method.
Sent from my EVO using xda app-developers app
I'm actually not on S-OFF and its doing the same. I would say unroot and then try updating. Once you unroot, it should go back to stock automatically
Sent from my EVO 4G LTE using XDA-Developer App
S-Off is something you guys will want eventually and updating the Hboot will more than likely keep you away from that. Just sit tight and wait on the Rom of your choice to be updated or download the rooted update within the development forum.
That's what I was trying to suggest doing. I'm not really interested in the update as of right now.... Sitting tight! Lol
Sent from my EVO 4G LTE using XDA-Developer App
Not Happy....post 1.22.651.3
Guess this is what I get for not understanding the update before I installed it. Used Voodoo OTA RootKeeper, thought I was good to go. I should have known something was amiss when the update was a HTC software update and not a Firmware update. Not only did it nix my root, I can't even get to recovery, it blocked it.
My current configuration is:
TAMPERED
LOCKED
Jewel PVT SHIP S-ON RL
So I am thinking I am pretty much toast. Not real interested if flashing ROMs at this point, just wanted Root.
This totally s__ks. And 3 days before they light up LTE in my area, ugh.
i unrooted and relocked phone by installing ruu in order to get ota update. i received update just fine. problem is ive tried to root again using regaw root and the other root method. regaw got me unlocked and recovery but when it got to installing root files said error cannot mount system as rw. hope this helps cause i am one who di try it by goin back stock. and thanks to all you devs. this is the GREATEST place to learn anything about any android phone. i just hopw you guys come up with a way foe me to root my phone soon. and oh yeah my phgone did accept the twrp recovery, i was wonderin if i could install some type of zip file thru twrp to regain root. no i do not have su, never got it when i tried to root
---------- Post added at 04:01 AM ---------- Previous post was at 03:49 AM ----------
my data connection is worse with new radios. went from ave. of 500 kbs to 220. ive done everything ican to try to improve that. all the ## stuff to reactivating. nothin is helping. im in ohio. voice stayed the same 2 signal bars
---------- Post added at 04:15 AM ---------- Previous post was at 04:01 AM ----------
treIII said:
i unrooted and relocked phone by installing ruu in order to get ota update. i received update just fine. problem is ive tried to root again using regaw root and the other root method. regaw got me unlocked and recovery but when it got to installing root files said error cannot mount system as rw. hope this helps cause i am one who di try it by goin back stock. and thanks to all you devs. this is the GREATEST place to learn anything about any android phone. i just hopw you guys come up with a way foe me to root my phone soon. and oh yeah my phgone did accept the twrp recovery, i was wonderin if i could install some type of zip file thru twrp to regain root. no i do not have su, never got it when i tried to root
---------- Post added at 04:01 AM ---------- Previous post was at 03:49 AM ----------
my data connection is worse with new radios. went from ave. of 500 kbs to 220. ive done everything ican to try to improve that. all the ## stuff to reactivating. nothin is helping. im in ohio. voice stayed the same 2 signal bars
Click to expand...
Click to collapse
im also s-on
root
hey guys,
very similar situation -
my phone never got 'auto updates' turned off, so on saturday it accepted the update and installed over my rooted evo lte. i have no custom recovery or unlocked bootloader. the phone now does not receive calls/texts (can send/call out fine) i cannot get it to flash back tothe stock RUU b/c i keep getting 171 usb errors. Is there a way to reroot it on the 1.22 software? i figure if i can root it, i can then unlock the bootloader and install a previous version on it to get it back to OEM settings. if it doesnt fix my communication errors, i can at least take it to sprint to get a new unit.
thanks
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 all,
Recently I wanted to flash a new ROM since I had been on Newt's Sense 5 ROM forever. Tried to flash the 11/27 build of CM10.2 and it went through but I had to cellular service. Just LTE, GPS, and wifi. Couldn't make or receive calls. So I restored my nandroid of Sense 5. And it still doesn't work. I either have no signal bars, or I have signal bars, but it will say "NO SERVICE" when I try to make a call. Any help? I know a lot of people don't cal these days but for what I do calling is pretty important.
Thanks!
if you need more information I can deliver
FCO2011 said:
Hey all,
Recently I wanted to flash a new ROM since I had been on Newt's Sense 5 ROM forever. Tried to flash the 11/27 build of CM10.2 and it went through but I had to cellular service. Just LTE, GPS, and wifi. Couldn't make or receive calls. So I restored my nandroid of Sense 5. And it still doesn't work. I either have no signal bars, or I have signal bars, but it will say "NO SERVICE" when I try to make a call. Any help? I know a lot of people don't cal these days but for what I do calling is pretty important.
Thanks!
if you need more information I can deliver
Click to expand...
Click to collapse
I am having the exact same issue. I tried to flash 4.4 and no service so I went back to viper sense 5 and no service still. So I relocked flashed the old bootloader old radio and old recovery. Then I RUUd back to stock original and still nothing. I am seeing this problem everywhere I have read at least 5 different threads with same problem no solution! Somebody help us!!!!!!!!!!!!!!!!
FIXED
I went to bootloader after accepting the new verizon update from the stock rom originally on phone and went to bootloader then factory reset from there and voila! Service again. Here is the thread that gave me the idea http://forum.xda-developers.com/showthread.php?t=2335945&page=2
I had a similar issue. Make sure you do a factory reset after RUU. That did the trick for me.
Sent from my dlx using Tapatalk
I can't RUU, it won't let me, it just says "Problem encountered, the ROM cannot be updated. please use the correct RUU and try again." Or something along those lines. Does anybody else have any other solutions? I cannot get this fixed for the life of me and it's ****ing pissing me off.
Do not fear! This exact problem happened to me. The only solution is to go back to s-off, factory reset, and RUU. Unfortunately when I did it I only had the oldest RUU (1.15) so I had to HTC dev unlock my bootloader and now it says tampered. There are newer RUUs now so that shouldn't be a problem.
If there's anything you want me to clarify just ask.
Sent from my HTC6435LVW using xda app-developers app
---------- Post added at 06:27 AM ---------- Previous post was at 06:25 AM ----------
The reason RUU isn't working for you is because you have to flash hboot. There's a thread on it somewhere but If you can't find it I'll post the link tommorow. I think it's the s-on to s-off thread.
Edit:
This is the thread:
http://forum.xda-developers.com/showthread.php?t=2293919
[How-To] From S-OFF to 100% Stock S-ON [Facepalm/JTAG/RevOne/Moonshine]
This part fixes the RUU error:
FLASHING THE STOCK HBOOT:
*Credit to .torrented*
1. download 1.15 stock hboot: 1.15 stock hboot MD5: B4B8555C20724E12C3B9D33820746E50
2. Rename stock hboot file to : PL83IMG.zip and place in the folder that contains your fastboot.exe file (On your computer)
3. Flash hboot
Apparently there is an easier way to fix this. http://forum.xda-developers.com/showthread.php?t=2568696
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
This issue started when flashing from viper 1.3.5 to 4.1.0. My dl speeds are .2mb to 8mb down and upload .2mb to nothing. My mobile data is not always connected but it always shows 4g lte. My wife has 25mb down 22mb up next to me in her gs4 non rooted. I've flashed sense 4 RUU stock and sense 5 RUU. along with the alternate sense 5 flashable zips via fastboot. I have also relocked my phone and can't reunlock. I used to have a bad WiFi signal but somehow flashing stock ruu fixed my WiFi speeds. I have redownloaded bot sense 4 and 5ruu twice and have done them twice and factory reset before and after each flash with still no success of fixing my "corrupt radio" files. I have a droid razr that's rooted I was on and I also noticed horrible network speeds. I have followed all guides while rooting. I always do a clean flash. I'm not spending any extra money for a new phone. If this can't be fixed them I'm stuck with it for 2months till I get my upgrade and can get a new phone. If this may be a hardware issue how can I replace my radio? Sorry for the essay. Thanks in advance for any help.
severedevil said:
This issue started when flashing from viper 1.3.5 to 4.1.0. My dl speeds are .2mb to 8mb down and upload .2mb to nothing. My mobile data is not always connected but it always shows 4g lte. My wife has 25mb down 22mb up next to me in her gs4 non rooted. I've flashed sense 4 RUU stock and sense 5 RUU. along with the alternate sense 5 flashable zips via fastboot. I have also relocked my phone and can't reunlock. I used to have a bad WiFi signal but somehow flashing stock ruu fixed my WiFi speeds. I have redownloaded bot sense 4 and 5ruu twice and have done them twice and factory reset before and after each flash with still no success of fixing my "corrupt radio" files. I have a droid razr that's rooted I was on and I also noticed horrible network speeds. I have followed all guides while rooting. I always do a clean flash. I'm not spending any extra money for a new phone. If this can't be fixed them I'm stuck with it for 2months till I get my upgrade and can get a new phone. If this may be a hardware issue how can I replace my radio? Sorry for the essay. Thanks in advance for any help.
Click to expand...
Click to collapse
What firmware and baseband version does your phone say its on?
monarudo pvt ship s-off rh
cid-vzw_001
hboot- 1.57.0000
radio-1.02.01.0207
opendsp- v12.120.274.0909
os-4.09.605.1
emmc-boot 2048mb
severedevil said:
This issue started when flashing from viper 1.3.5 to 4.1.0. My dl speeds are .2mb to 8mb down and upload .2mb to nothing. My mobile data is not always connected but it always shows 4g lte. My wife has 25mb down 22mb up next to me in her gs4 non rooted. I've flashed sense 4 RUU stock and sense 5 RUU. along with the alternate sense 5 flashable zips via fastboot. I have also relocked my phone and can't reunlock. I used to have a bad WiFi signal but somehow flashing stock ruu fixed my WiFi speeds. I have redownloaded bot sense 4 and 5ruu twice and have done them twice and factory reset before and after each flash with still no success of fixing my "corrupt radio" files. I have a droid razr that's rooted I was on and I also noticed horrible network speeds. I have followed all guides while rooting. I always do a clean flash. I'm not spending any extra money for a new phone. If this can't be fixed them I'm stuck with it for 2months till I get my upgrade and can get a new phone. If this may be a hardware issue how can I replace my radio? Sorry for the essay. Thanks in advance for any help.
Click to expand...
Click to collapse
RUU back to stock or flash a stock based rom and hboot and radio firmware.
Sent from my HTC6435LVW using XDA Free mobile app
biggiesmalls657 said:
RUU back to stock or flash a stock based rom and hboot and radio firmware.
Sent from my HTC6435LVW using XDA Free mobile app
Click to expand...
Click to collapse
i have. didnt fix anything, i have tried both RUU sense 4 and RUU sense 5 and also alternate RUU sense 5. and yes i preformed factory reset after.
severedevil said:
i have. didnt fix anything, i have tried both RUU sense 4 and RUU sense 5 and also alternate RUU sense 5. and yes i preformed factory reset after.
Click to expand...
Click to collapse
I was experiencing similar issues. In short, Verizon ended up replacing my phone with a refurb that is working much better than the original.
You may want to try flashing a different radio - see d08speed3's post here http://forum.xda-developers.com/showthread.php?t=2740450
a little more than halfway down, It contains links for flashable radios (unfortunately this did not resolve my issue).
"NEVER flash the same radio on top of each other"