I am unable to connect to verizon wireless network anymore! This started happening after I was trying to port MIUI onto the Dinc4G. Now, I have a small triangle over the signal bars. Somehow, I managed to get 3G data, but I am unable to place or receive calls. I am unable to activate phone via *228# either. I spent over 30-35 mins on the phone with VZW customer service and they were unable to fix it as well. And I also used the bootloader unlock tool to revert my CID to VZW__001 and it still doesn't work. I factory reset and deleted all data/dalvik/cache and system partition and reinstalled ViperLTE ROM and it still doesn't work.
A screen shot of the problem.
As you can see in the image, I have a triangle above the signal. Also, in the settings page, you can see that the phone number in the device is 0000000000! WHY?
Can anyone help me fix this??? Thanks
Try the ruu that's a worst case scenario but this sounds like that...
litetaker said:
I am unable to connect to verizon wireless network anymore! This started happening after I was trying to port MIUI onto the Dinc4G. Now, I have a small triangle over the signal bars. Somehow, I managed to get 3G data, but I am unable to place or receive calls. I am unable to activate phone via *228# either. I spent over 30-35 mins on the phone with VZW customer service and they were unable to fix it as well. And I also used the bootloader unlock tool to revert my CID to VZW__001 and it still doesn't work. I factory reset and deleted all data/dalvik/cache and system partition and reinstalled ViperLTE ROM and it still doesn't work.
A screen shot of the problem.
As you can see in the image, I have a triangle above the signal. Also, in the settings page, you can see that the phone number in the device is 0000000000! WHY?
Can anyone help me fix this??? Thanks
Click to expand...
Click to collapse
i think thats a roaming symbol, check your network settings and apn, just a quess.
This happened to a lot of us on the Dinc2, myself included, when we flashed a chinesse RUU. We ended up having to flash a stock RUU and needed to type a number combination to update the carrier settings. Sorry, I don't have the specifics, but you will be able to fix it. Has to do with flashing the wrong radio I think. You probably inadvertently flashed a foreign radio.
Sent from my Xoom using Tapatalk 2
slacka-vt said:
This happened to a lot of us on the Dinc2, myself included, when we flashed a chinesse RUU. We ended up having to flash a stock RUU and needed to type a number combination to update the carrier settings. Sorry, I don't have the specifics, but you will be able to fix it. Has to do with flashing the wrong radio I think. You probably inadvertently flashed a foreign radio.
Sent from my Xoom using Tapatalk 2
Click to expand...
Click to collapse
Ahh, I remember this issue. And a fellow Vermonter too! Also yes, the triangle over the signal bars mean you are roaming (Verizon has no idea where/what you are) If you can reflash the stock ruu and possibly specifically the stock radio, you should go back to normal.
Method320 said:
Ahh, I remember this issue. And a fellow Vermonter too! Also yes, the triangle over the signal bars mean you are roaming (Verizon has no idea where/what you are) If you can reflash the stock ruu and possibly specifically the stock radio, you should go back to normal.
Click to expand...
Click to collapse
I am unable to flash stock ruu. It is causing an error and quitting. However I didn't mess with the radio (I think) and I didn't do anything else other than flash system files while attempting to port MIUI... sad I am getting a CLNR from Verizon as they couldn't figure it out after 30 mins of trouble shooting on phone yesterday and some 30 mins of trouble shooting in a store today and after replacing the sim card either...
I think devs on this device should be careful while messing around as they may mess their phone like me and be unable to rectify it by flashing ruu... beware people...
Sent from my Transformer Prime TF201 using XDA Premium HD app
litetaker said:
I am unable to flash stock ruu. It is causing an error and quitting. However I didn't mess with the radio (I think) and I didn't do anything else other than flash system files while attempting to port MIUI... sad I am getting a CLNR from Verizon as they couldn't figure it out after 30 mins of trouble shooting on phone yesterday and some 30 mins of trouble shooting in a store today and after replacing the sim card either...
I think devs on this device should be careful while messing around as they may mess their phone like me and be unable to rectify it by flashing ruu... beware people...
Sent from my Transformer Prime TF201 using XDA Premium HD app
Click to expand...
Click to collapse
Try initiating ril manually
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
litetaker said:
I am unable to flash stock ruu. It is causing an error and quitting. However I didn't mess with the radio (I think) and I didn't do anything else other than flash system files while attempting to port MIUI... sad I am getting a CLNR from Verizon as they couldn't figure it out after 30 mins of trouble shooting on phone yesterday and some 30 mins of trouble shooting in a store today and after replacing the sim card either...
I think devs on this device should be careful while messing around as they may mess their phone like me and be unable to rectify it by flashing ruu... beware people...
Sent from my Transformer Prime TF201 using XDA Premium HD app
Click to expand...
Click to collapse
did you relock before flashing the RUU? if not, thats probably why its failing
Try what nits said the ruu is like a reserve parachute it should work in the boot loader
Linch89 said:
Try what nits said the ruu is like a reserve parachute it should work in the boot loader
Click to expand...
Click to collapse
I managed to install the RUU found at Team Unlimited IO's website. Yes, I forgot to relock.
It did not fix the issue immediately and I was bummed. I still had the same issue. I then attempted to boot into recovery only to realize the RUU wiped my TWRP recovery. Then I waited for my phone to reboot and it did and then somehow I got back access to the network!
Now, will I be guaranteed to recover access to the network the next time such an issue occurs? I dunno, because even after RUU I initially didn't get the network connection back but only after a reboot. If there was some other reason for this screw up I will be careful with my dev work. Else, if someone can verify that I can safely restore lost network connectivity with an RUU I can dev in peace.
At least you are back to stock and can soff now
Linch89 said:
At least you are back to stock and can soff now
Click to expand...
Click to collapse
I did S-OFF!
So it's your phone back to normal now? Did that sketch you out of devving? I wouldn't blame you...there's a lot that could go wrong and a several hundred dollar mistake isn't a good thing at all
Linch89 said:
So it's your phone back to normal now? Did that sketch you out of devving? I wouldn't blame you...there's a lot that could go wrong and a several hundred dollar mistake isn't a good thing at all
Click to expand...
Click to collapse
Yup.. Back to normal. I will continue to work on deving, but I will take precautions from now on. I still want to get to the bottom of this and find out exactly why it happened. In any case, as long as I can flash stock RUU to go back to defaults I will not shy away too much from deving..
litetaker said:
Yup.. Back to normal. I will continue to work on deving, but I will take precautions from now on. I still want to get to the bottom of this and find out exactly why it happened. In any case, as long as I can flash stock RUU to go back to defaults I will not shy away too much from deving..
Click to expand...
Click to collapse
glad to hear your back up and running.
Unable to flash recovery:
sending 'recovery' (7564 KB)...
OKAY [ 1.074s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.108s
My bootloader seems to be locked again after reflashing the RUU.. I am unable to unlock it using fastboot oem unlock!
Help! Damn I shouldn't be messing with MIUI.. I will be careful next time!
litetaker said:
Unable to flash recovery:
sending 'recovery' (7564 KB)...
OKAY [ 1.074s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.108s
My bootloader seems to be locked again after reflashing the RUU.. I am unable to unlock it using fastboot oem unlock!
Help! Damn I shouldn't be messing with MIUI.. I will be careful next time!
Click to expand...
Click to collapse
Need to get new unlock tocken
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
If you soff why do you need to unlock your boot loader???
Linch89 said:
If you soff why do you need to unlock your boot loader???
Click to expand...
Click to collapse
Forgot that detail
Sent from my ADR6410LVW using xda app-developers app
jose51197 said:
Forgot that detail
Sent from my ADR6410LVW using xda app-developers app
Click to expand...
Click to collapse
I don't know why but I had to re unlock the bootloader via htcdev as suggested by you even though I was already s-off.. confused but at least I am back to normal.
Sent from my ADR6410LVW using XDA Premium HD app
Related
So I need to send back my old Rezound with a dead screen, but I want to wipe my data off it first. The phone will turn on and boot up just fine, and ADB works fine as well... just can't see anything on the screen. So my question is simple: How do I erase everything on it via adb before I send it back? I need to clear out the data and cache partitions. Any ideas how to clear out the whole thing?
This should be in Q/A section. My bad.
a.mcdear said:
So I need to send back my old Rezound with a dead screen, but I want to wipe my data off it first. The phone will turn on and boot up just fine, and ADB works fine as well... just can't see anything on the screen. So my question is simple: How do I erase everything on it via adb before I send it back? I need to clear out the data and cache partitions. Any ideas how to clear out the whole thing?
This should be in Q/A section. My bad.
Click to expand...
Click to collapse
Best thing to do honestly if the bootloader is locked is to RUU. Run it off your computer. If your bootloader is unlocked then type fastboot OEM lock and then ruu. You shouldn't have to see anything on the screen to do this.
Sent from my ADR6425LVW using XDA App
nosympathy said:
Best thing to do honestly if the bootloader is locked is to RUU. Run it off your computer. If your bootloader is unlocked then type fastboot OEM lock and then ruu. You shouldn't have to see anything on the screen to do this.
Sent from my ADR6425LVW using XDA App
Click to expand...
Click to collapse
ok I was worried about having to confirm anything via the phone's screen. I'll give it a shot.
a.mcdear said:
ok I was worried about having to confirm anything via the phone's screen. I'll give it a shot.
Click to expand...
Click to collapse
Not to lock the bootloader. Unlocking it you have to change it to yes and hit power, when locking it just locks and your done, and then you can run the ruu while in hboot, booted up, etc.
Sent from my ADR6425LVW using XDA App
nosympathy said:
Not to lock the bootloader. Unlocking it you have to change it to yes and hit power, when locking it just locks and your done, and then you can run the ruu while in hboot, booted up, etc.
Sent from my ADR6425LVW using XDA App
Click to expand...
Click to collapse
yup got it done.
I also discovered that there are commands for that:
Code:
fastboot erase [partition-name]
but it seems that there's protection of some sort. When I tried "fastboot erase data" I got some error saying "access denied: remote" or something like that.
I also tried creating a blank filesystem with no data [blank.img] and tried to "flash" that over /data - didn't work either. Got the same access denied error. Weird...
Anyways, re-locked, ran RUU, packaged up for Verizon and sent it back. Thanks for the help!
a.mcdear said:
yup got it done.
I also discovered that there are commands for that:
Code:
fastboot erase [partition-name]
but it seems that there's protection of some sort. When I tried "fastboot erase data" I got some error saying "access denied: remote" or something like that.
I also tried creating a blank filesystem with no data [blank.img] and tried to "flash" that over /data - didn't work either. Got the same access denied error. Weird...
Anyways, re-locked, ran RUU, packaged up for Verizon and sent it back. Thanks for the help!
Click to expand...
Click to collapse
No problem, glad it worked out!
Sent from my ADR6425LVW using XDA App
The OEM lock (relock) and RUU are OK to use when sending back to Verizon?
Sent from my ADR6425LVW using xda premium
andrewp3481 said:
The OEM lock (relock) and RUU are OK to use when sending back to Verizon?
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
Yes. Ideal to use in fact. I ran RUU to get a nice clean fresh start with my phone and it comes out squeaky clean and factory fresh!
Cleans out all the old files/folders that flashing a custom ROM does not and gets it all back to stock.
Sent from my ADR6425LVW using Tapatalk
andrewp3481 said:
The OEM lock (relock) and RUU are OK to use when sending back to Verizon?
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
Yes, I certainly didn't want to send Verizon a phone with all my personal information still on the data partition. That seemed like a bad idea....
I honestly didn't care whether it was RUU'd back to stock or not.. I was originally just going to erase all the partitions leaving it bootable to HBOOT and send it back totally blank, but I figure this is easier for them to figure out.
My HTC G2 has the same problem, but I have rarely used ADB and the directions above are a bit over my head. Can anyone explain it a bit more? For instance, what is RUU? I am actually hoping that a factory restore will make it work again since the screen will magically start working at random, usually once or twice a day. The second the screen turns off I can;t get it back again until it magically fixes itself again.
loomism2 said:
My HTC G2 has the same problem, but I have rarely used ADB and the directions above are a bit over my head. Can anyone explain it a bit more? For instance, what is RUU? I am actually hoping that a factory restore will make it work again since the screen will magically start working at random, usually once or twice a day. The second the screen turns off I can;t get it back again until it magically fixes itself again.
Click to expand...
Click to collapse
An ruu is a complete software package released by HTC, it can contain many things they are trying to update. Radio, ROM, bootloader, etc... Installing an ruu is like installing an image on a hard drive it wipes the phone and installs the image. It will wipe everything data and all. so if you install one be prepared.
I rooted my evo 4g lte. I was having issues with data today and updating the profile. so I was going to unroot and try it stock. I relocked the bootlader, and somehow my rom image is gone!!!! i cant flash the ruu, it keeps failing error 155. someone please help me
Wrong thread. Need to be posted in q&a
sent from my EVO LTE with it's security flags down.
jrgalioto said:
I rooted my evo 4g lte. I was having issues with data today and updating the profile. so I was going to unroot and try it stock. I relocked the bootlader, and somehow my rom image is gone!!!! i cant flash the ruu, it keeps failing error 155. someone please help me
Click to expand...
Click to collapse
Similar thing happened to me. I have hboot 1.15. I relocked the the phone ran the RUU. Phone booted up normal with the everything stock. I then took the OTA and when it rebooted it was updating then it rebooted and the phone never turned on again. I sent it to HTC for warranty. They will get it tuesday. I'll see how this goes.
Okay guys... Enough with the flaming. If you can help, post! If not, don't. Grow up. It was posted in the wrong section. Use the report button in the upper-right corner of the post and report it.
Now, let me see if I can actually help you.
You're getting this error because you're trying to flash an older RUU on the phone than what's already on there. You'll need to flash the same RUU version or higher. If you took the latest OTA update, there may not be one available yet. I'd suggest you go through the HTCDev unlock again until that RUU makes it to the internet.
Team Nocturnal posted a couple of the older RUU versions.
http://www.androidfilehost.com/main/EVO_4G_LTE_Developers/Team.Nocturnal/RUU/
~co~
closeone said:
Okay guys... Enough with the flaming. If you can help, post! If not, don't. Grow up. It was posted in the wrong section. Use the report button in the upper-right corner of the post and report it.
Now, let me see if I can actually help you.
You're getting this error because you're trying to flash an older RUU on the phone than what's already on there. You'll need to flash the same RUU version or higher. If you took the latest OTA update, there may not be one available yet. I'd suggest you go through the HTCDev unlock again until that RUU makes it to the internet.
Team Nocturnal posted a couple of the older RUU versions.
http://www.androidfilehost.com/main/EVO_4G_LTE_Developers/Team.Nocturnal/RUU/
~co~
Click to expand...
Click to collapse
Here is the issue with that though. When i run the RUU, it says my current image is........nothing. i have tried to flash the newest and the oldest versions.
jrgalioto said:
Here is the issue with that though. When i run the RUU, it says my current image is........nothing. i have tried to flash the newest and the oldest versions.
Click to expand...
Click to collapse
Hi there jrgalioto. Can you do me a favor, and boot into your bootloader for me? I'd like you to check the green text.
What Radio version does it say you have?
Also, if you can connect the phone up to your computer and run the fastboot command (in FASTBOOT USB mode):
Code:
fastboot getvar mainver
What number comes back? (If you can't run the command, don't worry about it)
---
If I might ask, why did you relock the phone?
---
I'm looking into trying to get you a link to a current RUU. One has been posted, but I can't access it because of Filefactory's restrictions. Hopefully somebody will post a mirror to the download soon.
~co~
closeone said:
Hi there jrgalioto. Can you do me a favor, and boot into your bootloader for me? I'd like you to check the green text.
What Radio version does it say you have?
Also, if you can connect the phone up to your computer and run the fastboot command (in FASTBOOT USB mode):
Code:
fastboot getvar mainver
What number comes back? (If you can't run the command, don't worry about it)
---
If I might ask, why did you relock the phone?
---
I'm looking into trying to get you a link to a current RUU. One has been posted, but I can't access it because of Filefactory's restrictions. Hopefully somebody will post a mirror to the download soon.
~co~
Click to expand...
Click to collapse
I relocked because I needed to bring it back to Sprint for service, so I needed to unroot it, because I wasn't receiving data to it. But I got it figured out now. I was able to unlock the bootloader again and my recovery was still there. So i reflashed a custom ROM, so I at least had something on my phone. When I called Sprint, I told them it was not a phone issue, they updated my username in the system, then I was able to ##72786# to get the hands free activation to complete without error 1012. So I am now back in business. However, If I ever do have to unroot again, I will be in the same boat.
jrgalioto said:
I relocked because I needed to bring it back to Sprint for service, so I needed to unroot it, because I wasn't receiving data to it. But I got it figured out now. I was able to unlock the bootloader again and my recovery was still there. So i reflashed a custom ROM, so I at least had something on my phone. When I called Sprint, I told them it was not a phone issue, they updated my username in the system, then I was able to ##72786# to get the hands free activation to complete without error 1012. So I am now back in business. However, If I ever do have to unroot again, I will be in the same boat.
Click to expand...
Click to collapse
For future ref...sprints tep policy covers rooted phones
Of course the first variable that could be the issue in any given situation is the fact that a phone is rooted
Sent from my SPH-L710 using xda app-developers app
00mred00 said:
For future ref...sprints tep policy covers rooted phones
Of course the first variable that could be the issue in any given situation is the fact that a phone is rooted
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
That was the 1st thought I had. What if the root is causing the issue. It, however was not the case. and all is now right with the world, and I am no longer a brick...for now...
jrgalioto said:
That was the 1st thought I had. What if the root is causing the issue. It, however was not the case. and all is now right with the world, and I am no longer a brick...for now...
Click to expand...
Click to collapse
Hi jrgalioto,
I was able to get a link to the new RUU for you. This one should work fine for you.
~co~
Yep...... sprint doesnt care that you're rooted.
I frequently tell them mine is so they dont go messing with things they shouldnt be
OK I just cleaned this thread of a bunch of GARBAGE.
If you don't want to help, post on a blog.
The guy is looking for help.
Seriously .
il Duce said:
OK I just cleaned this thread of a bunch of GARBAGE.
If you don't want to help, post on a blog.
The guy is looking for help.
Seriously .
Click to expand...
Click to collapse
Sorry duce
Sent from the depths of hell
Hey I try to help and I have even written a guide with a ton of info, I even went so far as to write down troubleshooting stuff and they still post the exact same stuff over and over, some times its a bit frustrating. I even gave instructions on what they need to do should they completely ruin the file tree, when have you seen anyone completely destroy the internal memory lol
closeone said:
Hi there jrgalioto. Can you do me a favor, and boot into your bootloader for me? I'd like you to check the green text.
What Radio version does it say you have?
Also, if you can connect the phone up to your computer and run the fastboot command (in FASTBOOT USB mode):
Code:
fastboot getvar mainver
What number comes back? (If you can't run the command, don't worry about it)
---
If I might ask, why did you relock the phone?
---
I'm looking into trying to get you a link to a current RUU. One has been posted, but I can't access it because of Filefactory's restrictions. Hopefully somebody will post a mirror to the download soon.
~co~
Click to expand...
Click to collapse
Any luck on the mirror for the new RUU download? I'm using the latest one I can find and I am stuck and can't get my phone to reboot, shutdown or anything. I can't run fastboot either. all I see is ***Tampered*** unlocked*** ....RUU update fail!
My phone won't respond to the volume down and power button either.
any suggestions?
I flashed NOS 7 2.0.3 and i was put in to roaming. i went back to previous rom and still stuck in roaming. It is really bugging me. Does anyone know what to do. I am begging for help.
hello
Something similar happened to me when I flashed one of the aosp roms but I couldn't even get past the activation. What I did to fix it was to do a clean flash of the same rom, I think it was pac, start the phone up without the sim card in but connected to wifi, finish the activation, then go into the networks setting and change the cdma subscription to RUIM/SIM.
I'm not sure if this will help you but it's worth a shot I suppose.
Sent from my HTC6435LVW using Xparent Skyblue Tapatalk 2
I had the same thing happen twice flashing a cm10.1 rom. What I did to fix it was install stock hboot 1.15, and run the stock RUU to go all the way back to stock. Make sure you relock your boot loader before running RUU. Get back to stock, go into boot loader and do a factory reset. Fixed mine twice. Maybe the long way of doing things, but it worked. Then you'll have to unlock boot loader and install custom recovery. Hope that helps.
Sent from my HTC6435LVW using xda app-developers app
jgraves12 said:
Something similar happened to me when I flashed one of the aosp roms but I couldn't even get past the activation. What I did to fix it was to do a clean flash of the same rom, I think it was pac, start the phone up without the sim card in but connected to wifi, finish the activation, then go into the networks setting and change the cdma subscription to RUIM/SIM.
I'm not sure if this will help you but it's worth a shot I suppose.
Sent from my HTC6435LVW using Xparent Skyblue Tapatalk 2
Click to expand...
Click to collapse
I'm having the same issue. I just tried to flash carbon and bam.... Roaming. Went back to stock backup but it too was in roaming. Going to try or fix.
Sent from my Nexus 7 using xda app-developers app
Gr8Jeepin said:
I'm having the same issue. I just tried to flash carbon and bam.... Roaming. Went back to stock backup but it too was in roaming. Going to try or fix.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Right above you is how to fix it, lock up and ruu back to stock, its worked for quite a few users.
Tapatalked from my HTC DNA - Carbon
you don't need to relock bl if s-off
I just moonshined this morning. First time i tried to put a rom on and this. I hate to be a pain but is there a procedure for completing this? I followed your moonshine and it worked great on the first try. sorry for the noodness.
beaups said:
you don't need to relock bl if s-off
Click to expand...
Click to collapse
I thought the ruu wouldn't run against an unlocked boot loader? I had to lock mine to get it to run, may have been another issue that happened to clear up when I did it, too.
Tapatalked from my HTC DNA - Carbon
pio_masaki said:
I thought the ruu wouldn't run against an unlocked boot loader? I had to lock mine to get it to run, may have been another issue that happened to clear up when I did it, too.
Tapatalked from my HTC DNA - Carbon
Click to expand...
Click to collapse
If s-off you can ruu when unlocked. Doesn't matter, tho.
Sent from my HTC6435LVW using Tapatalk 4 Beta
beaups said:
If s-off you can ruu when unlocked. Doesn't matter, tho.
Sent from my HTC6435LVW using Tapatalk 4 Beta
Click to expand...
Click to collapse
Good info, saves an extra step or two.
Tapatalked from my HTC DNA - Carbon
Ok... Im at a lose. Im still roaming. Im at 2.04 firmware. In bootloader it says "unlocked" at the top and S-ON. I've trying to update to current OTA with no luck. I've heard of issues with the SIM. I havent had any speciffic SIM card faults. If thats the issue i'll just get another SIM.
Thanks again guys
Edit: the SIM has been verified to work in original phone (broken screen). So maybe I'll swap it back in new phone.
Edit 2 [solved] Factory reset from bootloader. Thanks to c0ruptiv3 for having the issue before me.
beaups said:
you don't need to relock bl if s-off
Click to expand...
Click to collapse
To ruu back to stock, if s-off, you just run the ruu as an administrator? Do you have to change the splash screen if custom?
Sent from my HTC6435LVW using Tapatalk 2
i would like to bring this thread back up because I am still having the same issue. i ruu'ed and everthing
ThatFool said:
i would like to bring this thread back up because I am still having the same issue. i ruu'ed and everthing
Click to expand...
Click to collapse
This happened to me a little while back. I flashed back to 1.15 hboot, ruu'd back, rebooted, skipped through the setup and let it sit for a little while, rebooted into recovery, did a factory reset, rebooted again and I was roam free!
did the same but tried booting into recovery there is no recovery installed. not even stock android
Stuck in roam
I am not able to get my computer to recognize my DNA therefor I cant do any of these steps any help would be awesome.
Try *#*#4636#*#* and Phone Information. If you are on Verizon it should be cdma/LTE. Also your phone should not be in Global Mode in Mobile Network settings. Last time I was stuck on roaming this was why.
planedoc said:
I had the same thing happen twice flashing a cm10.1 rom. What I did to fix it was install stock hboot 1.15, and run the stock RUU to go all the way back to stock. Make sure you relock your boot loader before running RUU. Get back to stock, go into boot loader and do a factory reset. Fixed mine twice. Maybe the long way of doing things, but it worked. Then you'll have to unlock boot loader and install custom recovery. Hope that helps.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Ditto! Had the same thing happen to me, this was the only way I could get out of roaming. Doing the factory reset from stock recovery was key for me. I did everything, relock everything, flashed the RUU and was still roaming, it was only after factory reset from stock recovery did it come out of roaming.
Sent from my HTC6435LVW using xda app-developers app
Factory reset from RUU is the way I fixed mine when it happened to me. I did not relock bootloader before RUU though. Maybe make sure you put the stock splash screen back on and go back to original hboot before RUU.
I rooted using this method: http://forum.xda-developers.com/showthread.php?p=36976137#post36976137 (I think it's referred to as CID 222222, though I think when I did it the first time it was 111111). I locked it, updated to 2.04.605.2, then was able to reroot it using the same method.
I want to get the OTA to 2.06 because I keep getting the PUK lock and no SIM found errors and the update popup is really starting to get annoying with how much it pops up.
I think I can get root and s-off using moonbeam if I upgrade to 2.06, but I'm not sure how to get it to that point.
andyd273 said:
I rooted using this method: http://forum.xda-developers.com/showthread.php?p=36976137#post36976137 (I think it's referred to as CID 222222, though I think when I did it the first time it was 111111). I locked it, updated to 2.04.605.2, then was able to reroot it using the same method.
I want to get the OTA to 2.06 because I keep getting the PUK lock and no SIM found errors and the update popup is really starting to get annoying with how much it pops up.
I think I can get root and s-off using moonbeam if I upgrade to 2.06, but I'm not sure how to get it to that point.
Click to expand...
Click to collapse
I'm on a custom rom right now, so I don't remember exactly. But it should be under Settings>About Phone> and somewhere in there there should be the option to "check for software update."
kxs783kms said:
I'm on a custom rom right now, so I don't remember exactly. But it should be under Settings>About Phone> and somewhere in there there should be the option to "check for software update."
Click to expand...
Click to collapse
Unfortunately because it's rooted it fails to update that way. Last time I think I had to restore a factory Rom or ruu or something then do the update and then restore from backup, but I'm not sure which room to use this time, or if there is a better way now.
andyd273 said:
Unfortunately because it's rooted it fails to update that way. Last time I think I had to restore a factory Rom or ruu or something then do the update and then restore from backup, but I'm not sure which room to use this time, or if there is a better way now.
Click to expand...
Click to collapse
I think you're going to have to RUU the 1.15 stock rom with directions from here
http://forum.xda-developers.com/showthread.php?t=2017525 and just let it accept all of the the updates up to the 2.06 update before you root it. That way you'll have the stock recovery, so you should definitely be able to accept the OTA's. There might be an easier, quicker way, but I couldn't find one.
kxs783kms said:
I think you're going to have to RUU the 1.15 stock rom with directions from here
http://forum.xda-developers.com/showthread.php?t=2017525 and just let it accept all of the the updates up to the 2.06 update before you root it. That way you'll have the stock recovery, so you should definitely be able to accept the OTA's. There might be an easier, quicker way, but I couldn't find one.
Click to expand...
Click to collapse
All right, that's fine at least.
So, once I take it down to 1.15, then back up to 2.06, I can do the moonbeam method to root and s-off instead of CID 222222, right?
Also, is there a better way to handle updates, so I don't have to keep going down to 1.15?
Thanks for the help.
I used the Revone method to root 2.06. I never used that one you mentioned because when I bought my DNA 2 weeks ago, it was on 2.06 and Revone and Moonshine were the only options I saw that worked for 2.06. It's in the development section.
Sent from my HTC6435LVW using Tapatalk 4
Check the moonshine thread op it has how to update to 2.06
Sent from my HTC6435LVW using XDA Premium HD app
.torrented said:
Check the moonshine thread op it has how to update to 2.06
Click to expand...
Click to collapse
Sorry, I read that whole thread and didn't see it. I see where he says to search the forum, but the only one I have seen is the one kxs783kms suggested: http://forum.xda-developers.com/showthread.php?t=2017525
I'm currently trying that one, but the RUU part failed the first time I tried... will try it again.
andyd273 said:
Sorry, I read that whole thread and didn't see it. I see where he says to search the forum, but the only one I have seen is the one kxs783kms suggested: http://forum.xda-developers.com/showthread.php?t=2017525
I'm currently trying that one, but the RUU part failed the first time I tried... will try it again.
Click to expand...
Click to collapse
Here you go. http://forum.xda-developers.com/showthread.php?t=2314771&nocache=1 Scroll down in the first post and it will tell you how to upgrade it to 2.06.
kxs783kms said:
Here you go. http://forum.xda-developers.com/showthread.php?t=2314771&nocache=1 Scroll down in the first post and it will tell you how to upgrade it to 2.06.
Click to expand...
Click to collapse
Gaa. I think I may have messed something up.
Phone is stuck on white HTC start screen. no other messages.
I started to do the downgrade to 1.15, it didn't work, but it did wipe everything out.
So then I saw how to just do the upgrade to 2.06, so I figured I would first do a restore through clockwork mod.
It got part way, and something happened, and when I looked at it next the white screen was up.
I can restart it by holding down the power button, but then it starts back up again.
Any way to save it?
Edit: ok, was able to get into fastboot/bootloader
Figuring out where to go from here...
andyd273 said:
Gaa. I think I may have messed something up.
Phone is stuck on white HTC start screen. no other messages.
I started to do the downgrade to 1.15, it didn't work, but it did wipe everything out.
So then I saw how to just do the upgrade to 2.06, so I figured I would first do a restore through clockwork mod.
It got part way, and something happened, and when I looked at it next the white screen was up.
I can restart it by holding down the power button, but then it starts back up again.
Any way to save it?
Edit: ok, was able to get into fastboot/bootloader
Figuring out where to go from here...
Click to expand...
Click to collapse
Need a little more info, are you unlocked? s-off'd? rooted? custom recovery? I mean what are these set to currently btw, not what you have done in the past.
jake.corey.jacobs said:
Need a little more info, are you unlocked? s-off'd? rooted? custom recovery?
Click to expand...
Click to collapse
I might have figured it out...
unlocked, rooted, not s-off'd, CWM recovery.
I had a NANDROID backup, but it wasn't letting me restore from it, said it couldn't restore system.
Thats when it failed out.
I did some reading and figured out that I needed to hold down the down volume button when the screen flickered black for a half second and that got me back into fastboot.
Back in CWM I factory reset, wiped the cache and davlik cache, formatted system, and tried restore and so far it looks like it's working. It was able to restore system, and is currently restoring data.
So hopefully I'm on my way back, though it was a scary couple minutes there.
I'm a noob, but slowly learning
andyd273 said:
I might have figured it out...
unlocked, rooted, not s-off'd, CWM recovery.
I had a NANDROID backup, but it wasn't letting me restore from it, said it couldn't restore system.
Thats when it failed out.
I did some reading and figured out that I needed to hold down the down volume button when the screen flickered black for a half second and that got me back into fastboot.
Back in CWM I factory reset, wiped the cache and davlik cache, formatted system, and tried restore and so far it looks like it's working. It was able to restore system, and is currently restoring data.
So hopefully I'm on my way back, though it was a scary couple minutes there.
I'm a noob, but slowly learning
Click to expand...
Click to collapse
Trust me you keep around these parts and you will learn a lot from just reading random threads. Glad you got it back working so far, let us know how it turns out sir.
jake.corey.jacobs said:
Trust me you keep around these parts and you will learn a lot from just reading random threads. Glad you got it back working so far, let us know how it turns out sir.
Click to expand...
Click to collapse
Will do.
I don't like that Verizon makes it so hard to do this stuff, locking things down, but I do feel some satisfaction when I am able to make it work despite them.
andyd273 said:
Will do.
I don't like that Verizon makes it so hard to do this stuff, locking things down, but I do feel some satisfaction when I am able to make it work despite them.
Click to expand...
Click to collapse
Yeah vzw is horrible on a lot of fronts, but I like my consistent bill every month, something I never had on att. My bill would be anywhere from 120-300 dollars for no reason, as I had 2 grandfathered unlimited plans. my bill should of been around 150 dollars, and never was.
jake.corey.jacobs said:
Yeah vzw is horrible on a lot of fronts, but I like my consistent bill every month, something I never had on att. My bill would be anywhere from 120-300 dollars for no reason, as I had 2 grandfathered unlimited plans. my bill should of been around 150 dollars, and never was.
Click to expand...
Click to collapse
Ok, restore worked successfully!
Trying to flash 2.06 firmware, but it's not working quite right:
C:\DeveloperAndroid\android-sdk-windows\platform-tools>adb reboot bootloader
C:\DeveloperAndroid\android-sdk-windows\platform-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.045s]
finished. total time: 0.047s
C:\DeveloperAndroid\android-sdk-windows\platform-tools>fastboot flash zip dna2.06firmware.zip
sending 'zip' (33119 KB)...
OKAY [ 2.616s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
FAILED (remote: 92 supercid! please flush image again immediately)
finished. total time: 2.688s
Click to expand...
Click to collapse
I Am hopefully missing something really simple?
I have an HTC rezound that was unlocked and rooted by HTC dev method. It has the 2.28.0000 hboot and every ruu I find and try to use tells me hboot failed because mine is to new. I have searched for 2 days on this subject and the reason I am returning to stock is because I can't get into diag mode to flash to cricket. When I enter ##diag it says no network. ##program does nothing either. If anyone could point me in the right direction it would be appreciated.
Sent from my Galaxy Nexus using xda app-developers app
jhr5474 said:
I have an HTC rezound that was unlocked and rooted by HTC dev method. It has the 2.28.0000 hboot and every ruu I find and try to use tells me hboot failed because mine is to new. I have searched for 2 days on this subject and the reason I am returning to stock is because I can't get into diag mode to flash to cricket. When I enter ##diag it says no network. ##program does nothing either. If anyone could point me in the right direction it would be appreciated.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
All ruu's posted here dont work....pm me...i have all the needed files...and i'll guide you through this....your big error that your doing is your going to need to relock the bootloader before doing anything...leaving it unlocked will cause a soft brick
I already relocked the bootloader and it still failed. I am not a total noob flashed lots of radios, hboots, built sense ROMs. This one has me stumped though.
Sent from my Galaxy Nexus using xda app-developers app
jhr5474 said:
I already relocked the bootloader and it still failed. I am not a total noob flashed lots of radios, hboots, built sense ROMs. This one has me stumped though.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
ok an ruu is an exe file not a zip....again i have the files if needed and can show you how...also what you may not be doing whille running the ruu is placing the phone in bootloader then press the fastboot tab...once it says fastboot usb then run the ruu.exe
He is S-ON guys.
jhr5474 said:
I already relocked the bootloader and it still failed. I am not a total noob flashed lots of radios, hboots, built sense ROMs. This one has me stumped though.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
and yes you must be s-off to do this thanks @Flyhalf205
REV3NT3CH said:
and yes you must be s-off to do this thanks @Flyhalf205
Click to expand...
Click to collapse
So, the OP cannot do the full RUU thing.
Can't he just do a factory reset and then boot to one of the custom recoveries and re-flash the latest OTA?
cheers,
john
No op's links have broken software...I have the needed files on my dropbox and media fire account...and no all factory reset does is wipe all data and setting for ROM...and may cause custom ROMs to not boot...ota is only achievable if on stock ROM and there is an update...however I have all those proper files too
Sent from my R3D D347H 4.3 using xda app-developers app
Got it.
One last question, though, since I'm not that savvy...
REV3NT3CH said:
ota is only achievable if on stock ROM and there is an update...
Click to expand...
Click to collapse
...I didn't upgrade to the latest OTA from a previous OTA---I was on the Global Leak---and I installed the ROM found here with absolutely no problems after manually upgrading the firmware to the latest, which is what the OP is on. Fwiw, that ROM still appears to be available via the link in Post 1 of that thread.
cheers,
john
jrredho said:
Got it.
One last question, though, since I'm not that savvy...
...I didn't upgrade to the latest OTA from a previous OTA---I was on the Global Leak---and I installed the ROM found here with absolutely no problems after manually upgrading the firmware to the latest, which is what the OP is on. Fwiw, that ROM still appears to be available via the link in Post 1 of that thread.
cheers,
john
Click to expand...
Click to collapse
that isnt a pure stock ota bud...thats a rom made with includes from it and rooted
This might sound stupid, but your objective here really is to get stockish, correct? With your HBoot you could use this ROM:
http://forum.xda-developers.com/showthread.php?t=2260154
Just make sure to flash boot.img afterwards via fastboot. This is as close to pure stock (only root added) as you can get without S-Off or other trickery. It should suffice for the requirements of the OP.
Sent from my Nexus 4 using XDA Premium 4 mobile app
I've been trying to deal with this problem over in the liquidsmooth thread, but it's clear now that my problems are not related specifically to the rom and that thread isn't really the place for it.
I've lost all cell connectivity. Calls, texts, data, everything. The liquid rom had been working for me for over a week. I've reverted to previous roms both with new flashes and using restore files. I've tried a different recovery. Every time, it acts like I don't have a sim card.
I was suspecting that my sim might be bad, but back on the liquidsmooth thread, it was suggested that I need to RUU back to stock and start over. I'd be willing to do that except the only way suggested was really complicated. I'm S-on and it included ubuntu and the wire trick to get s-off, which I'm hesitant to do. I searched and found another thread with instructions to run an RUU while still s-on, and it seems like it would have worked except that my hboot is newer than the RUU used, and I've been unable to find a newer one.
I tried flashing the stock rom above and flashing the stock recovery that I had from when I first rooted several months ago. It still thinks I don't have a sim card, but otherwise it booted fine until I re-locked to bootloader. Then it wouldn't boot anymore. I guess it still knows that those versions of hboot, the recovery, and the rom don't quite go together.
Is there an RUU that will work with hboot 2.28 to "un-root" my phone without downloading a second operating system and performing surgery on my phone? Are the correct stock rom and recovery out there that I can flash and re-lock? Is there a way to know if that is actually the problem if if it is just my sim card? Are there any other ideas to get my phone functioning again?
Please help!
vigor pvt ship s-on rl
hboot-2.28.0000
radio-2.23.10.0123r/2.23.1.124r
OpenDsp-v1.4.6.0.7708.00.0507
eMMC-boot
Sep 20 2012,17:40:22
There is no RUU for your hboot, need to s-off...
If your SIM is bad, get a new one from Verizon.
Also, is the battery cover on?
Sent from my ADR6425LVW using Tapatalk
mjones73 said:
There is no RUU for your hboot, need to s-off...
If your SIM is bad, get a new one from Verizon.
Also, is the battery cover on?
Sent from my ADR6425LVW using Tapatalk
Click to expand...
Click to collapse
On that note... Are using a stock battery cover? Some aftermarket ones are questionable at best. Also, try another SIM, Verizon will replace it free.
Sent from my Nexus 4 using XDA Premium 4 mobile app
acejavelin said:
On that note... Are using a stock battery cover? Some aftermarket ones are questionable at best. Also, try another SIM, Verizon will replace it free.
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I tried using a friend's good sim card and it didn't work. Yes, I'm using the stock battery cover. I guess I'll have to do s-off so I can RUU back to stock.
Ugh . . . This has become so much more than I ever intended to get myself into
amschmid said:
I tried using a friend's good sim card and it didn't work. Yes, I'm using the stock battery cover. I guess I'll have to do s-off so I can RUU back to stock.
Ugh . . . This has become so much more than I ever intended to get myself into
Click to expand...
Click to collapse
You didn't answer my question, is it on the phone while you're testing your connection. Dumb question I know, antenna's are in it though and I've caught people leaving it off and not getting a signal then wondering why...
mjones73 said:
You didn't answer my question, is it on the phone while you're testing your connection. Dumb question I know, antenna's are in it though and I've caught people leaving it off and not getting a signal then wondering why...
Click to expand...
Click to collapse
Sorry, I missed that part of the question. We did it pretty quick, but I think I did put the battery cover. Also, it's not just getting no signal, there is an icon in the notification bar and a big message on the lock screen says I have no sim card at all. That has never happened before, even with the battery cover off. As I look back I realize I failed to mention that important detail. I guess it still couldn't hurt to try a brand new sim card before taking the plunge into s-off. Even if that isn't the problem, at least I'll know for sure, and as you pointed out, its easy and free.