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.
Related
Hope this is the correct place to ask, but quick question. So (short form) I relocked bootloader, reflashed the RUU, unlocked boot loader, installed ROM and it works great UNTILL I insert my SIM card, then it just keeps restarting. Why does this happen? What do I need to do, start all over and reflash everything? Please help!
Did you flash ruu twice.....it doesn't flash everything the first time through
Sent from my ADR6425LVW using XDA
This is gonna sound retarded, but I think so. The first time it installed the RUU, it was a blue status bar on the right, the 2nd time it was a brown status bar. But, I had already installed the ROM prior to seeing the brown bar...Does that make any since? I used to be decent at this, but it's been a while...
relock and reflash the ruu twice... then flash recovery and then flash a rom
Worst case flash the ruu again...watch it do each step successfully...that's what I would do. When I did the first flash using scoslers instructions I needed to do a battery pull since it was stuck at white htc screen...
Sent from my ADR6425LVW using XDA
ericsignals said:
Worst case flash the ruu again...watch it do each step successfully...that's what I would do. When I did the first flash using scoslers instructions I needed to do a battery pull since it was stuck at white htc screen...
Sent from my ADR6425LVW using XDA
Click to expand...
Click to collapse
Ok, we'll try and see what happens. I was hoping that it was something small. lol
It could be something else...but when I am not sure on something I start from scratch and try again lol
Sent from my ADR6425LVW using XDA
ok, so that did the trick for the SIM, but now I lost root and cant get it back...ugh! I've tried thru recovery and using Rezound_All-In-One_Kit_v2.0, but it dont work either. phone works for now though...so better than nothing. If yall got any ideas on how to get root back I would be thankful...yall know alot more about this than I do..haha
bskarpa said:
ok, so that did the trick for the SIM, but now I lost root and cant get it back...ugh! I've tried thru recovery and using Rezound_All-In-One_Kit_v2.0, but it dont work either. phone works for now though...so better than nothing. If yall got any ideas on how to get root back I would be thankful...yall know alot more about this than I do..haha
Click to expand...
Click to collapse
You need to HTC dev unlock again then flah amon ra
Sent from my Dinc... I mean Rezound
yojoe600 said:
You need to HTC dev unlock again then flah amon ra
Sent from my Dinc... I mean Rezound
Click to expand...
Click to collapse
+1 Its like starting all over again.
One more post for my ten
I purchased a Rezound from eBay and it's locked with a gesture lock. The seller told me to do a factory reset, which I did a couple of times, and it doesn't reset the phone to the new activation screen. It looks like he rooted the phone at one point. The recovery screen says "Tampered," "Relocked," and "VIGOR PVT SHIP S-ON RL."
My question is, how do I get past the gesture lock? Will rooting and flashing a different rom do the trick? I am obviously a newbie, and likely wouldn't have rooted it and installed a custom rom if I didn't have to, but it seems like I may have to at this point. Thanks!
willievee said:
I purchased a Rezound from eBay and it's locked with a gesture lock. The seller told me to do a factory reset, which I did a couple of times, and it doesn't reset the phone to the new activation screen. It looks like he rooted the phone at one point. The recovery screen says "Tampered," "Relocked," and "VIGOR PVT SHIP S-ON RL."
My question is, how do I get past the gesture lock? Will rooting and flashing a different rom do the trick? I am obviously a newbie, and likely wouldn't have rooted it and installed a custom rom if I didn't have to, but it seems like I may have to at this point. Thanks!
Click to expand...
Click to collapse
Flash a custom recovery and wipe if you want the stock Rom.rooted
Or you can just ruu to stock and it will wipe it
Sent from my ADR6425LVW using Tapatalk 2
Thanks for the advice. I used the Rezound All in One kit and got it working. I'll leave it rooted for now, maybe install ICS on it.
willievee said:
Thanks for the advice. I used the Rezound All in One kit and got it working. I'll leave it rooted for now, maybe install ICS on it.
Click to expand...
Click to collapse
Deff go for ICS, i'd even recommend stepping up to Sense 4 but you might prefer stock
Sense 4.0 still has a few bugs, but 3.6 is golden.
Sent from my Clean ROM DE 1.4 Rezound
willievee said:
I purchased a Rezound from eBay and it's locked with a gesture lock. The seller told me to do a factory reset, which I did a couple of times, and it doesn't reset the phone to the new activation screen. It looks like he rooted the phone at one point. The recovery screen says "Tampered," "Relocked," and "VIGOR PVT SHIP S-ON RL."
My question is, how do I get past the gesture lock? Will rooting and flashing a different rom do the trick? I am obviously a newbie, and likely wouldn't have rooted it and installed a custom rom if I didn't have to, but it seems like I may have to at this point. Thanks!
Click to expand...
Click to collapse
Obviously the first thing that comes to mind is if all it needed was to have a factory reset done why didn't the seller do just that and avoid the hassle? Kinda like when you look at a car and all it needs for the AC to work is a recharge..yeah I've been bit by that one before too.
Glad you got it working..youll enjoy being rooted
Looks like it isn't entirely right. I took it to Verizon to get it activated, and I have data connectivity but cannot call or text at all. The software version is 4.0.3 Android with 3.6 Sense. I am going to try to restore the factory version (from this thread http://forum.xda-developers.com/showthread.php?t=1338916) and hope that does the trick. Otherwise, I guess there's something wrong and I have to return the phone to the seller.
willievee said:
Looks like it isn't entirely right. I took it to Verizon to get it activated, and I have data connectivity but cannot call or text at all. The software version is 4.0.3 Android with 3.6 Sense. I am going to try to restore the factory version (from this thread http://forum.xda-developers.com/showthread.php?t=1338916) and hope that does the trick. Otherwise, I guess there's something wrong and I have to return the phone to the seller.
Click to expand...
Click to collapse
If you haven't done this yet, what is your baseband.
Sent from my ADR6425LVW using xda app-developers app
My baseband is 1.22.10.0421r.
I haven't done anything yet. Currently downloading the RUU.
willievee said:
My baseband is 1.22.10.0421r.
I haven't done anything yet. Currently downloading the RUU.
Click to expand...
Click to collapse
Are you downloading aan ICS ruin?
Sent from my ADR6425LVW using xda app-developers app
I want to restore it to stock, so I'm downloading an official RUU from this thread: http://forum.xda-developers.com/showthread.php?t=1338916&page=12.
(RUU_Vigor_VERIZON_WWE_2.01.605.11_Radio_RS_0.95.00.1123r_3161E_9K_QMR_release_233635_signed.exe)
willievee said:
I want to restore it to stock, so I'm downloading an official RUU from this thread: http://forum.xda-developers.com/showthread.php?t=1338916&page=12.
(RUU_Vigor_VERIZON_WWE_2.01.605.11_Radio_RS_0.95.00.1123r_3161E_9K_QMR_release_233635_signed.exe)
Click to expand...
Click to collapse
You wont be able to run that RUU. You are s-on and cannot go backwards in RUU you can only go forward. Either s-off or you'll need to flash the latest ICS RUU leak.
Sent from my ADR6425LVW using xda app-developers app
Gotcha. Thanks. I'll try to sort out how to download the newest ICS RUU and flash it. I tried to follow these directions: http://forum.xda-developers.com/showthread.php?t=1614366
and downloaded [ICS][2.25][STOCK][5-7]PH98IMG.zip but I wasn't able to flash it. I guess I have to figure out which ICS RUU to download and flash.
I still don't understand why I have data but no call or text capability.
willievee said:
Gotcha. Thanks. I'll try to sort out how to download the newest ICS RUU and flash it. I tried to follow these directions: http://forum.xda-developers.com/showthread.php?t=1614366
and downloaded [ICS][2.25][STOCK][5-7]PH98IMG.zip but I wasn't able to flash it. I guess I have to figure out which ICS RUU to download and flash.
I still don't understand why I have data but no call or text capability.
Click to expand...
Click to collapse
http://multiupload.biz/bdkjtkk1j4zw/PH98IMG_MultiUpload.biz.zip.html
Download that file, rename it PH98IMG.ZIP and make sure it isn't named PH98IMG.ZIP.ZIP and then put that on the root of the actual SD Card. Not the internal memory.
Reboot into hboot, and it will find that file and load it. You will have to chose volume + to accept. It will flash bootloader first, then the radios and rom and such. After this has flashed and booted, delete the PH98IMG.ZIP file from your sd card, and then reboot into hboot and chose factory reset. Let it do its thing, and try a phone call or text on reboot.
should be good to go after this.
I downloaded the file, put it in the root directory of the sd card, and booted into hboot. It says "Loading PH98IMG.zip" for a few minutes, then goes back to the hboot screen. I then powered down, removed SD card, and tried to factory reset. The phone entered the Android system recovery. I rebooted, and the phone seemed exactly the same. I'll retry, maybe I'm doing something wrong.
Update: I've retried a few times, and it just seems that hboot won't load PH98IMG.zip. Might it matter that I'm still at S-ON?
willievee said:
I downloaded the file, put it in the root directory of the sd card, and booted into hboot. It says "Loading PH98IMG.zip" for a few minutes, then goes back to the hboot screen. I then powered down, removed SD card, and tried to factory reset. The phone entered the Android system recovery. I rebooted, and the phone seemed exactly the same. I'll retry, maybe I'm doing something wrong.
Click to expand...
Click to collapse
Try redownloading again might have been a bad download. Remember once the file starts to flash it might shut off and turn on and continue doing its thing just make sure when it's all done every item says "ok" next to it if it does your good to go next just make sure you go into bootloader do a factory reset.
Sent from my Sense4 ICS Rezound
willievee said:
I downloaded the file, put it in the root directory of the sd card, and booted into hboot. It says "Loading PH98IMG.zip" for a few minutes, then goes back to the hboot screen. I then powered down, removed SD card, and tried to factory reset. The phone entered the Android system recovery. I rebooted, and the phone seemed exactly the same. I'll retry, maybe I'm doing something wrong.
Update: I've retried a few times, and it just seems that hboot won't load PH98IMG.zip. Might it matter that I'm still at S-ON?
Click to expand...
Click to collapse
No s-on wouldn't matter. Your bootloader is still locked right?
Sent from my ADR6425LVW using xda app-developers app
I unlocked the bootloader last night. Redownloading the file now.
willievee said:
I unlocked the bootloader last night. Redownloading the file now.
Click to expand...
Click to collapse
Relock the bootloader I believe when S-ON you have to lock it to run the RUU
Sent from my Sense4 ICS Rezound
LakerStar25 said:
Relock the bootloader I believe when S-ON you have to lock it to run the RUU
Sent from my Sense4 ICS Rezound
Click to expand...
Click to collapse
This. It won't run else wise. I didn't think to ask this as you said previously it was locked.
My bad.
Sent from my ADR6425LVW using xda app-developers app
Hi, ever since last night my wife's Amaze has been stuck in a boot loop. The white HTC logo screen comes up and then it reboots and the same thing happens over and over. It was running firmware 2.14.531.3. I was able to boot into hboot and re-lock the bootloader with fastboot to flash the RUU and I flashed the latest one which is RUBY_ICS_35_S_TMOUS_2.14.531.3_R2 but still the same thing happens I even flashed it a second time but no dice. I'm really not sure what to do here. Did some other things too like take out the battery put it back in after a few minutes, charged it while the phone was off. If anyone has any ideas please help. Thank you
So no one has any ideas?
Sent from my Nexus 7 using Tapatalk 2
rock7632 said:
So no one has any ideas?
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Try factory resetting in the stock recovery, then reloading the ruu via hboot.
(reboot into stock recovery from hboot, volume up and power button to bring the menu up so you can wipe the device)
Though reloading a stock ruu should wipe everything, are you getting any errors when reloading the stock ruu? And which one of the ruu files are you using to reload?
rock7632 said:
So no one has any ideas?
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
You don't flash the ruu.. you need to put the file in root of ur SD and rename it to ph85img or something like that and reboot in the bootloader
Sent from my HTC_Amaze_4G using xda app-developers app
Dark Nightmare said:
Try factory resetting in the stock recovery, then reloading the ruu via hboot.
(reboot into stock recovery from hboot, volume up and power button to bring the menu up so you can wipe the device)
Though reloading a stock ruu should wipe everything, are you getting any errors when reloading the stock ruu? And which one of the ruu files are you using to reload?
Click to expand...
Click to collapse
I can try that. and no I didn't get any errors when loading the ruu. the one I did was the latest one for T-Mobile us 2.14.531.3_R2.
Perry977 said:
You don't flash the ruu.. you need to put the file in root of ur SD and rename it to ph85img or something like that and reboot in the bootloader
Sent from my HTC_Amaze_4G using xda app-developers app
Click to expand...
Click to collapse
uhh yes that's what I did
Sent from my Galaxy Nexus using Tapatalk 2
rock7632 said:
I can try that. and no I didn't get any errors when loading the ruu. the one I did was the latest one for T-Mobile us 2.14.531.3_R2.
uhh yes that's what I did
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Did you try different kernel?
Sent from my HTC_Amaze_4G using xda app-developers app
Perry977 said:
Did you try different kernel?
Sent from my HTC_Amaze_4G using xda app-developers app
Click to expand...
Click to collapse
RUU flashed the stock kernel when he reloaded.
Dark Nightmare said:
RUU flashed the stock kernel when he reloaded.
Click to expand...
Click to collapse
yeah and even prior to that I had the stock kernel
Sent from my Nexus 7 using Tapatalk 2
rock7632 said:
yeah and even prior to that I had the stock kernel
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Do u still have the custom recovery?
Sent from my HTC_Amaze_4G using xda app-developers app
Are you s-off? SuperCID? you need to set both back to the original values and reflash stock ROM from bootloader.
Perry977 said:
Do u still have the custom recovery?
Sent from my HTC_Amaze_4G using xda app-developers app
Click to expand...
Click to collapse
no i flashed the stock recovery before i loaded the RUU.
olegy said:
Are you s-off? SuperCID? you need to set both back to the original values and reflash stock ROM from bootloader.
Click to expand...
Click to collapse
I'm s-on
Sent from my Nexus 7 using Tapatalk 2
rock7632 said:
no i flashed the stock recovery before i loaded the RUU.
I'm s-on
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Even if, you didn't need to reflash anything, apparently the fact that the ruu wipes and restores everything to stock still hasn't sunk in yet, anyways, we're missing some info here, what else happened before this issue that you're not telling me, since bootloop issues are easily resolved by a stock reload via hboot but yours seems to be on the same loop no matter what, are you giving it the time to boot after reloading via hboot? First boot takes a bit of time, patience is very vital.
Dark Nightmare said:
Even if, you didn't need to reflash anything, apparently the fact that the ruu wipes and restores everything to stock still hasn't sunk in yet, anyways, we're missing some info here, what else happened before this issue that you're not telling me, since bootloop issues are easily resolved by a stock reload via hboot but yours seems to be on the same loop no matter what, are you giving it the time to boot after reloading via hboot? First boot takes a bit of time, patience is very vital.
Click to expand...
Click to collapse
Ya like he^^ said, it does take a very long to boot up after flashing an ruu, could take a good 10 mins or maybe more...
Now if you did wait and it still just bootlooped after flashing the ruu, either the ruu is bad, or u did something wrong, OR u got some serious software problems going on
Due to the fact, atleast from reading your first post, it sounds like it was running fine then suddenly just started bootlooping. And then flashing an ruu didn't fix it. Sounds to me like ur phone has some serious issues
sent from my NRGized Amaze,
powered by faux kernel v.13
Dark Nightmare said:
Even if, you didn't need to reflash anything, apparently the fact that the ruu wipes and restores everything to stock still hasn't sunk in yet, anyways, we're missing some info here, what else happened before this issue that you're not telling me, since bootloop issues are easily resolved by a stock reload via hboot but yours seems to be on the same loop no matter what, are you giving it the time to boot after reloading via hboot? First boot takes a bit of time, patience is very vital.
Click to expand...
Click to collapse
That's just it, after loading the ruu via hboot the phone asks for a reboot and when I do it it barely takes 5 seconds on the HTC logo white screen then the phone reboots again and the same thing happens. And as far as anything happening before, nothing really happened. The battery died a couple of days ago and the when we charged it and tried to turn on the phone this started happening
Sent from my Galaxy Nexus using Tapatalk 2
I've tried everything I could think of. Loaded 2 different ruu's, manually wiped everything from recovery and nothing has worked, its still doing the exact same thing. I really don't understand how it can be bricked just out of nowhere
Sent from my Nexus 7 using Tapatalk 2
rock7632 said:
I've tried everything I could think of. Loaded 2 different ruu's, manually wiped everything from recovery and nothing has worked, its still doing the exact same thing. I really don't understand how it can be bricked just out of nowhere
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I think Im having an issue similar to yours. Is there any interaction after it begins to flash the RUU? I found a video for the thunderbolt where it asks you to approve the update before it finishes. My phone does the update then jumps back to the fastboot screen.
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.
I've had my Evo LTE since launch. Ran many many ROM's. Was on CM11 for quite some time and then all the sudden in my pocket it went into a bootloop. But, not a normal bootloop. It will boot all the way into android, I can unlock the screen sometimes even use it for a while then reboot. Many times it will get to the lockscreen only and then reboot, it will do his cycle indefinitely. I know this type of bootloop usually indicates a kernel/ROM mismatch, but all the ROM's I've been using since this started are the kernel included with the ROM and no customizations. I've done the ViperUU, I've re-flashed firmware. Wiped absolutely everything, except external sdcard. Sometimes it will run for a few hours before it starts again, and sometimes it start rebooting immediately. I'm at the end of my knowledge of what other steps to take. Those of you with mad skills, I petition your expertise please!
What version of cm were you using? Deck's build or nightlies?
Sent from my EVO
numel007 said:
What version of cm were you using? Deck's build or nightlies?
Sent from my EVO
Click to expand...
Click to collapse
Decks!
After it glitched I tried PA, Omni, and stock. Same issue on all.
wolfclan68 said:
Decks!
After it glitched I tried PA, Omni, and stock. Same issue on all.
Click to expand...
Click to collapse
You might want to try a RUU for your current firmware... It might be time for a refresh for your phone, then unlock, root and s-off again...
Sent from my SPH-L900 using Tapatalk
jocarog said:
You might want to try a RUU for your current firmware... It might be time for a refresh for your phone, then unlock, root and s-off again...
Sent from my SPH-L900 using Tapatalk
Click to expand...
Click to collapse
Agreed. I would RUU with the most recent OTA and go from there. If you're S-off you'll still be S-off once you run the RUU. Afterwards, I'd stay stock for a few days and see how the phone acts. If the issue persists you most likely have a hardware issue somewhere. If everything runs okay afterwards you can unlock your bootloader again, install a custom recovery and flash a ROM.
Here is the link to the 3.17 RUU:
http://www.htc.com/us/support/htc-evo-4g-lte-sprint/news/
Sent from my HTC EVO 4G LTE
jocarog said:
You might want to try a RUU for your current firmware... It might be time for a refresh for your phone, then unlock, root and s-off again...
Sent from my SPH-L900 using Tapatalk
Click to expand...
Click to collapse
FinZ28 said:
Agreed. I would RUU with the most recent OTA and go from there. If you're S-off you'll still be S-off once you run the RUU. Afterwards, I'd stay stock for a few days and see how the phone acts. If the issue persists you most likely have a hardware issue somewhere. If everything runs okay afterwards you can unlock your bootloader again, install a custom recovery and flash a ROM.
Here is the link to the 3.17 RUU:
http://www.htc.com/us/support/htc-evo-4g-lte-sprint/news/
Sent from my HTC EVO 4G LTE
Click to expand...
Click to collapse
I didn't realize the HTC RUU was available. I thought ViperUU was the only one. I will give that a shot. Thanks guys! I will report the results.
jocarog said:
You might want to try a RUU for your current firmware... It might be time for a refresh for your phone, then unlock, root and s-off again...
Sent from my SPH-L900 using Tapatalk
Click to expand...
Click to collapse
FinZ28 said:
Agreed. I would RUU with the most recent OTA and go from there. If you're S-off you'll still be S-off once you run the RUU. Afterwards, I'd stay stock for a few days and see how the phone acts. If the issue persists you most likely have a hardware issue somewhere. If everything runs okay afterwards you can unlock your bootloader again, install a custom recovery and flash a ROM.
Here is the link to the 3.17 RUU:
http://www.htc.com/us/support/htc-evo-4g-lte-sprint/news/
Sent from my HTC EVO 4G LTE
Click to expand...
Click to collapse
Posting results as promised. The HTC RUU seems to have fixed the problem, haven't had a reboot since the RUU 3 days now. However during this process I was without a phone for 6 days, I picked up an LG G2. This phone kicks. Got it at Best Buy out the door for $48, CRAZY cheap for such a phone. I guess I'll be getting rid of my EVO.
wolfclan68 said:
Posting results as promised. The HTC RUU seems to have fixed the problem, haven't had a reboot since the RUU 3 days now. However during this process I was without a phone for 6 days, I picked up an LG G2. This phone kicks. Got it at Best Buy out the door for $48, CRAZY cheap for such a phone. I guess I'll be getting rid of my EVO.
Click to expand...
Click to collapse
I'll take it, lol. I need a working test device.
I'd like to test and see if an older RUU works with the new Sense 5 ROM setup
Sent from my EVO LTE
FinZ28 said:
I'd like to test and see if an older RUU works with the new Sense 5 ROM setup
Sent from my EVO LTE
Click to expand...
Click to collapse
Of course that would be the first thing I'd test . Just can't do it on my everyday/work device.