Related
As the title says, I'd like to restore the backup it creates. I have a problem with my phone where it receives zero signal regardless of what rom installed. I have seen a different thread on this problem but there was no clear answer on how to solve it so I'm trying to backtrack my steps. I did the following all at the same time, htc unlock, s-off exploit with Juopunut, and sim unlock using config.dat. They all seemed to work perfectly until I got this problem. I'd ask for support at umlimited.io but when I did they insisted they didn't create the problem and if I persisted in asking how to restore their Juopunut backup I'd be kicked...which was kinda rude, but what are you going to do? Thanks in advance for any help.
what is your radio version? I'd suggest updating to latest radios. or maybe you did something wrong with the sim unlock
EM|NEM said:
what is your radio version? I'd suggest updating to latest radios. or maybe you did something wrong with the sim unlock
Click to expand...
Click to collapse
Didn't even know the radio version could be upgraded/ downgraded. I did a quick search for this but didn't find where to grab a download. Where can I find an update for this? The radio version is 11.25.3504.06_M Also note that this is a GSM phone. So if this is a different incompatible version let me know!
Edit: So, I managed to find some, but when the bootloader trys to flash it it'll give me the message "Model ID incorrect!" This is from the GSM thread...what's going on?
your CID is incompatible. I'd suggest you run an RUU with the latest radios. then flash recovery and then rom.
EM|NEM said:
your CID is incompatible. I'd suggest you run an RUU with the latest radios. then flash recovery and then rom.
Click to expand...
Click to collapse
It's not the CID, I just rewrote it to HTC__001, unless it's expecting something else? It was originally ROGER001 I think.
Edit: I just noticed something, when in fastboot mode the model name is SHOOTER_U, Is there always a underscore there?
hmm not sure about this. If you want to get back to stock you should run the Rogers ICS RUU. see if you get signals back
EM|NEM said:
hmm not sure about this. If you want to get back to stock you should run the Rogers ICS RUU. see if you get signals back
Click to expand...
Click to collapse
Alright, will do. Is there anything I have to do in preparation, relock bootloader, etc?
yes you do need to relock. sorry i forgot to mention that
Well, the RUU update software completely fails. It fails at trying to get the phone to boot into the bootloader and then just pops up a message saying unknown error 155. Anyone know what the hell is going on with my phone?
i think the problem may be your hboot. Try flashing this hboot
http://forum.xda-developers.com/showthread.php?t=1906172
then make sure its locked/relocked then run RUU
Finally got it to install, I had to extract the rom.zip from the .exe and then rename it so that hboot would detect it. Installed fine, but the problem still persists. I have no signal what so ever. Is there no fix for this?
you just installed the rom. u need the radio with it too. Any ways i think some1 else should post in here as im all out of ideas
Does your phone see your sim card? Have you set up your apn's? Can you find a wifi and connect?
Sent from my Evo 3D GSM using Tapatalk 2
Yes, wifi connects, bluetooth connects. I'm pretty sure that the rom.zip is actually everything, it ha s a check list when installing, one of those things was called radio...so I'm pretty sure it installed a new or reinstalled that version. ALso, APNs don't do anything. It's almost like a driver issue or something, the radio just won't get a signal, android doesn't even detect it. When in the options the mobile network toggle is greyed out.
Ok and what rom are you trying to use?
Sent from my Evo 3D GSM using Tapatalk 2
It's the stock ROGERS RUU, I had to extract the ROM.zip file from it because the .exe gave me a unknown error. renaming the .zip to PG86IMG.zip seemed to work. I'm now on stock. The previous roms were nonsense and coolsense. I should also note that originally I tried to install a cdma miui rom that obviously failed.
So your mobile data is still greyed out? Have you tried to find a network through the mobile data settings
Sent from my Evo 3D GSM using Tapatalk 2
---------- Post added at 03:27 PM ---------- Previous post was at 03:20 PM ----------
And count yourself lucky because you could have bricked your phone if you had flashed a cdma firmware package
Sent from my Evo 3D GSM using Tapatalk 2
Yes, it searches for a while, then find a few networks which I'm taking a as a good sign that it even did that, but will not connect at all. When I select one it trys to open a toast error but then is closed immediately after, so I can't even read the error. When I check the network info in the android phone identity it just shows nothing, zero for signal, no network, etc.
Could be sim unlock that did? But I am guessing
Sent from my Evo 3D GSM using Tapatalk 2
Alright, so I've made some progress. I found that this is actually model PG8631000 instead of PG8630000 which is why it failed checks. A quick edit of the android-info.txt in the zip files allows it to flash. No problems with that, flashed new hboots and radios. However, the problem is still there. So finally I found a radio fix program for linux. Booted it up and it appears that my phone won't give any MEID values, they were probably wiped or something. I can't progress because with the wrong values I can completely brick the phone. This makes sense that the phone doesn't have the right values, it feels like the radio works, but has the incorrect values (which is why it finds services but won't connect). Is there any way to restore the MEID?
Edit: Well I'm an idiot, MEID is for CDMA phones. My phone status shows values for the network so that isn't it either....I'm so lost.
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
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!!!?????!
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
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