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?
Related
I relocked my phone to update to the ICS firmware (fastboot oem lock), but I got an error in the terminal. INFOTZ_HTC_SVC_DISABLE ret = 134086000 (0x7FDFD70)
ERROR: usb_read failed with status e00002ed
FAILED (status read failed (No such file or directory))
My phone rebooted to fastboot, and it says:
Relocked
Security Warning
S-On RL
I haven't rebooted, and I haven't booted into the bootloader to let the PH98IMG.zip flash.
Any advice on what to do next?
Edit--is the security warning normal? The error in the terminal scared the **** out of me, and coming from a Thunderbolt security warnings are bad news.
tekhna said:
I relocked my phone to update to the ICS firmware (fastboot oem lock), but I got an error in the terminal. INFOTZ_HTC_SVC_DISABLE ret = 134086000 (0x7FDFD70)
ERROR: usb_read failed with status e00002ed
FAILED (status read failed (No such file or directory))
My phone rebooted to fastboot, and it says:
Relocked
Security Warning
S-On RL
I haven't rebooted, and I haven't booted into the bootloader to let the PH98IMG.zip flash.
Any advice on what to do next?
Edit--is the security warning normal? The error in the terminal scared the **** out of me, and coming from a Thunderbolt security warnings are bad news.
Click to expand...
Click to collapse
I saw this once too when flashing the OTA firmware over the original firmware via a PH98IMG.zip file. I just repeated the install process and it disappeared. Honestly, I don't think its a worry.
I'm like 80% positive I get this error message too when running that command.
andybones said:
I'm like 80% positive I get this error message too when running that command.
Click to expand...
Click to collapse
Cool, thanks guys. So just flash the zip and be on my way?
tekhna said:
Cool, thanks guys. So just flash the zip and be on my way?
Click to expand...
Click to collapse
yup, pretty much what I did. Mine's fine
a.mcdear said:
yup, pretty much what I did. Mine's fine
Click to expand...
Click to collapse
So uh.. my phone seems to have turned off while updating. It checked the package, was going through the update process, and now it just looks like it's shut off. I haven't touched it since it seems to have shut itself off.
Bricked?
Yeah that security warning comes up often and has meant nothing on every other phone I've seen or helped with.
Sent from my ADR6425LVW using xda premium
tekhna said:
So uh.. my phone seems to have turned off while updating. It checked the package, was going through the update process, and now it just looks like it's shut off. I haven't touched it since it seems to have shut itself off.
Bricked?
Click to expand...
Click to collapse
****, I seriously hope not!! I know for a fact I had the same security warning after re-locking to update firmware, and mine works just fine now. I would definitely power it back on, and hope to heaven that the hboot screen comes up ok...
What the hell is going on with my phone? The screen went totally black for a couple minutes during the update process, on its own it just rebooted to fastboot without me touching it, and now I have
Tampered
Relocked
Security Warning
What is going on? Reflash the package?
Edit--it seems to have at least updated Hboot, it's 2.21 now, not 2.11. Radios are .1118r and .12223r
tekhna said:
What the hell is going on with my phone? The screen went totally black for a couple minutes during the update process, on its own it just rebooted to fastboot without me touching it, and now I have
Tampered
Relocked
Security Warning
What is going on? Reflash the package?
Edit--it seems to have at least updated Hboot, it's 2.21 now, not 2.11.
Click to expand...
Click to collapse
OK, you had me scared I had you break your phone for a sec. Things are sounding better now.
On mine, going from 2.10 to 2.11, I got to that same point.. and then flashed the PH98IMG.zip file AGAIN, and security warning went away after the second time.
**edit**
looks like it updated Hboot, but not the radios. You're still on the GB OTA radios..
a.mcdear said:
OK, you had me scared I had you break your phone for a sec. Things are sounding better now.
On mine, going from 2.10 to 2.11, I got to that same point.. and then flashed the PH98IMG.zip file AGAIN, and security warning went away after the second time.
**edit**
looks like it updated Hboot, but not the radios. You're still on the GB OTA radios..
Click to expand...
Click to collapse
Yeah, things are sounding better, getting to fastboot is a darn good thing. It seems like the package didn't flash properly, but I'm afraid if I flash it again it's just going to fail again. I checked the md5, it checked out.
I'm no expert, but I've been doing this a while and I haven't seen my phone do anything like this before.
Edit-heh, nothing you did, would have been on me!
tekhna said:
Yeah, things are sounding better, getting to fastboot is a darn good thing. It seems like the package didn't flash properly, but I'm afraid if I flash it again it's just going to fail again. I checked the md5, it checked out.
I'm no expert, but I've been doing this a while and I haven't seen my phone do anything like this before.
Edit-heh, nothing you did, would have been on me!
Click to expand...
Click to collapse
No its been noted before that the leaked ICS build doesn't always install correctly the first time around and should be run a second time. Even if it does fail again, in exactly the same way, at least you know what to do about now...
a.mcdear said:
No its been noted before that the leaked ICS build doesn't always install correctly the first time around and should be run a second time. Even if it does fail again, in exactly the same way, at least you know what to do about now...
Click to expand...
Click to collapse
Trying again now... fingers crossed.
Edit: Crap, it keep unzipping and then updating and then updating and then unzipping system. Is that supposed to happen over and over again?
Edit 2: Phew, moved past system. I can't remember being this anxious even when I first rooted my very first phone! Gah.
Edit 3: ****. It shut down again. What the hell? I think it was towards the end of the update. My radios updated, but I have no idea if the whole package took or not. And I'm back in fastboot. Flash a third time?
tekhna said:
Trying again now... fingers crossed.
Edit: Crap, it keep unzipping and then updating and then updating and then unzipping system. Is that supposed to happen over and over again?
Click to expand...
Click to collapse
From what I remember reading after the most recent ICS leak came out was that the first time, basically only HBOOT got updated. When you run it again, it runs successfully and updates everything. It sounds to me like you're ok, but hopefully one of the people who actually ran the latest leak RUU will chime in with their experience.
It has ~10 items to update in the package. Let it sit and DO NOT touch it for the next 10-15mins.
Snuzzo said:
It has ~10 items to update in the package. Let it sit and DO NOT touch it for the next 10-15mins.
Click to expand...
Click to collapse
Yeah, I did. And then when I looked away it rebooted itself again. Dunno what to do. Is it possible it's a bad package despite the md5s checking out?
Edit--Tampered and security warnings are gone from fastboot.
Even 1 change in removing 1 of the updates will change the MD5. You are fine. All you have to do is run it twice and you're cooking.
EDIT:
Oh btw, that error you got. Perfectly normal.
Snuzzo said:
Even 1 change in removing 1 of the updates will change the MD5. You are fine. All you have to do is run it twice and you're cooking.
Click to expand...
Click to collapse
I ran it twice. It rebooted itself again during the second install.
tekhna said:
I ran it twice. It rebooted itself again during the second install.
Click to expand...
Click to collapse
Rebooted to hboot or normally to splash screen?
Snuzzo said:
Rebooted to hboot or normally to splash screen?
Click to expand...
Click to collapse
hboot
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 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
I posted this over in the Help & Troubleshooting section but figured I'd get some exposure here too..
Does anyone have a copy of the FULL RUU for 2.06.605.1 (the 800MB or 900MB file)? I know this isn't a usual request for these forums but I just want to simply reflash my DNA with the stock sw. I am only able to find 1.15 online through any searches I do however, you cannot downgrade unless you have s-off which I do not. I am 100% stock and just want to reflash to fix some irritating issues that a master reset didn't resolve.
jrg67 said:
I posted this over in the Help & Troubleshooting section but figured I'd get some exposure here too..
Does anyone have a copy of the FULL RUU for 2.06.605.1 (the 800MB or 900MB file)? I know this isn't a usual request for these forums but I just want to simply reflash my DNA with the stock sw. I am only able to find 1.15 online through any searches I do however, you cannot downgrade unless you have s-off which I do not. I am 100% stock and just want to reflash to fix some irritating issues that a master reset didn't resolve.
Click to expand...
Click to collapse
it's not leaked.
s-off. flash eng hboot. run 1.15 ruu. then you can take ota's if you choose.
beaups said:
it's not leaked.
s-off. flash eng hboot. run 1.15 ruu. then you can take ota's if you choose.
Click to expand...
Click to collapse
Hey beaups! Thanks for the reply. I am trying to your moonshine to achieve S-OFF but I'm having some trouble. First few times I kept getting a failederror try again and READ right in the beginning when it says its checking for updates... then it magically worked the 4th time, got all the way through where it said it was rebooting into bootloader (again), found the device in 8 seconds, but then it just continued to think and think and think while the phone was sitting on the fastboot screen. after 15 minutes, i selected to power off on the phone, made no difference on moonshine.. still just thinking. I closed out moonshine and tried it again but now I'm back to the failederror and it tells me to try and and READ right in the beginning. I've rebooted the phone several times, usb debugging is on, fastboot in the power menu is unchecked, everything is in the /downloads folder...
jrg67 said:
Hey beaups! Thanks for the reply. I am trying to your moonshine to achieve S-OFF but I'm having some trouble. First few times I kept getting a failederror try again and READ right in the beginning when it says its checking for updates... then it magically worked the 4th time, got all the way through where it said it was rebooting into bootloader (again), found the device in 8 seconds, but then it just continued to think and think and think while the phone was sitting on the fastboot screen. after 15 minutes, i selected to power off on the phone, made no difference on moonshine.. still just thinking. I closed out moonshine and tried it again but now I'm back to the failederror and it tells me to try and and READ right in the beginning. I've rebooted the phone several times, usb debugging is on, fastboot in the power menu is unchecked, everything is in the /downloads folder...
Click to expand...
Click to collapse
Ok so I just totally disabled my firewall just in case and now its back to thinking after rebooting into bootloader (again) and waiting for fastboot (8/60).. just putting up row after row of dots. Been running for 10 mins total now.
That's still a network issue. Av/security software may be blocking. If you are at work, corporate network could be blocking, etc.
Sent from my HTC6435LVW using Tapatalk 4 Beta
jrg67 said:
I posted this over in the Help & Troubleshooting section but figured I'd get some exposure here too..
Click to expand...
Click to collapse
that's against the rules
beaups said:
That's still a network issue. Av/security software may be blocking. If you are at work, corporate network could be blocking, etc.
Sent from my HTC6435LVW using Tapatalk 4 Beta
Click to expand...
Click to collapse
Thanks beaups! I will disable both AV and firewall to see if that resolves.
Glebun said:
that's against the rules
Click to expand...
Click to collapse
I have no idea what you're talking about.
jrg67 said:
I have no idea what you're talking about.
Click to expand...
Click to collapse
read them and you'll know
Glebun said:
read them and you'll know
Click to expand...
Click to collapse
Noted. However the rules do not explicitly say you cannot post the same question in 2 forums. With the way its worded, it sounds like they don't want you repeating in the same forum. If you don't get any answers in one section, why would think you cannot move to another section? Since no admins commented on this, I'm not really sure but thanks for the heads up. I will remove the other post when I get home.
Also, asking questions in General is against the rules anyway, that's what the QA section is for.
Please post only ONE thread about something in the correct forum, thanks.
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