Lost 4G, Can't RUU

[badogg]

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...

 

[Uzephi]

Try flashing the recovery flashable radio?

Something could have borked the radio partition.

Sent from my DNA using my mind.

 

[badogg]

Try flashing the recovery flashable radio?

Something could have borked the radio partition.

Sent from my DNA using my mind.

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...

 

[finanandroid]

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...

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 ----------

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...

Bootloader unlocked matter to RUU , TWRP nope.

 

[badogg]

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.

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?

 

[finanandroid]

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?

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

 

[badogg]

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

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:

 

[finanandroid]

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:

a pleasure

 

[Uzephi]

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.

 

[badogg]

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.

Interesting, I don't have anything connected, but I'm sure I have drivers loaded for my nexus 7

 

[Uzephi]

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.

 

[badogg]

Well, I let htcsync update the usb drivers and now the RUU is updating the image now.

 

[badogg]

Ok, this persisted through the RUU. Rom booted up, got 4G initially, then went to 3G.

 

[finanandroid]

Ok, this persisted through the RUU. Rom booted up, got 4G initially, then went to 3G.

after Ruu you most do a factory reset* from stock recovery

 

[santod040]

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.

 

[badogg]

after Ruu you most do a factory reset* from stock recovery

omg, duh!! I knew that, just forgot to do it.

That seems to have fixed it. +150,000 internets to you!!

 

[finanandroid]

omg, duh!! I knew that, just forgot to do it.

That seems to have fixed it. +150,000 internets to you!!

glad :good: you got it !

 

[Sutko82]

@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

 

[santod040]

@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

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

 

[Sutko82]

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