So I'm one of the lucky few who got their phone unlocked and rooted before VZW and HTC put us all over a barrel buy taking the Inc4G off the supported devices list over at HTCDev. I've been happily plugging along until recently when the latest OTA update started getting pushed. Now every night my phone trys to run the update, which of course fails because I'm running a custom recovery instead of the stock one. It's annoying for a few reasons
It kills my battery if I don't leave it plugged in
I can't get messages or calls
It happens every friggin' night!
Is there any way to just permanently decline the upgrade? I can decline/defer it for a couple days at a time but then it just comes back. It's to the point where I'm debating getting rid of the phone and going back to my Nexus.
coffeedragon said:
So I'm one of the lucky few who got their phone unlocked and rooted before VZW and HTC put us all over a barrel buy taking the Inc4G off the supported devices list over at HTCDev. I've been happily plugging along until recently when the latest OTA update started getting pushed. Now every night my phone trys to run the update, which of course fails because I'm running a custom recovery instead of the stock one. It's annoying for a few reasons
It kills my battery if I don't leave it plugged in
I can't get messages or calls
It happens every friggin' night!
Is there any way to just permanently decline the upgrade? I can decline/defer it for a couple days at a time but then it just comes back. It's to the point where I'm debating getting rid of the phone and going back to my Nexus.
Click to expand...
Click to collapse
Using root explorer or another program like it, go to system/app/ and delete these two files:
1) HtcOMADM_SettingsPlugin_VZW.apk
2) HtcOMADM_VZW.apk
popup will never be seen again, and removes the annoying software update plugin in settings.apk
enjoy
You will want to delete the relatively large OTA package sitting in the /cache directory (possibly /cache/fota/ - but I can't check without root).
Also wouldn't hurt to rename the otacerts.zip file found in /etc/security by renaming it to otacerts.zip.bak
coffeedragon said:
So I'm one of the lucky few who got their phone unlocked and rooted before VZW and HTC put us all over a barrel buy taking the Inc4G off the supported devices list over at HTCDev. I've been happily plugging along until recently when the latest OTA update started getting pushed. Now every night my phone trys to run the update, which of course fails because I'm running a custom recovery instead of the stock one. It's annoying for a few reasons
It kills my battery if I don't leave it plugged in
I can't get messages or calls
It happens every friggin' night!
Is there any way to just permanently decline the upgrade? I can decline/defer it for a couple days at a time but then it just comes back. It's to the point where I'm debating getting rid of the phone and going back to my Nexus.
Click to expand...
Click to collapse
Why not upgrade to latest RUU and just reunlock the bootloader and reinstall the recovery to force SuperSU?
That's what I did.
EDIT: As long as you still have your unlock_code.bin file
articzap said:
Why not upgrade to latest RUU and just reunlock the bootloader and reinstall the recovery to force SuperSU?
That's what I did.
EDIT: As long as you still have your unlock_code.bin file
Click to expand...
Click to collapse
once you're unlocked you're unlocked, and can get the unlock_code.bin anytime on the site the way you did the first time by selecting other for phone.
andybones said:
once you're unlocked you're unlocked, and can get the unlock_code.bin anytime on the site the way you did the first time by selecting other for phone.
Click to expand...
Click to collapse
i think once you have an unlock code you can use it again to unlock after relock, i could be wrong since i never had one.
ok i misread you can't get an unlock code anymore, but if you have a code you can reuse it.
articzap said:
Why not upgrade to latest RUU and just reunlock the bootloader and reinstall the recovery to force SuperSU?
That's what I did.
EDIT: As long as you still have your unlock_code.bin file
Click to expand...
Click to collapse
@articzap - Can you explain the steps you took to do that?
mdimbler said:
@articzap - Can you explain the steps you took to do that?
Click to expand...
Click to collapse
I made a thread just for this...
http://forum.xda-developers.com/showthread.php?t=1947600
I uploaded the RUU.exe AND pulled the ROM.zip from the RUU and uploaded that to be able to put on SD-Card and install though bootloader. (my preferred method, much easier, and usually running the RUU through the computer an error will prevent you from upgrading. the ROM.zip through bootloader, will only fail if the download is corrupt, but I provided MD5 for that reason..)
IF you are unlocked with HTCdev unlock, u must lock the bootloader first, install the PJ53IMG.zip file, then unlock bootloader again.
you do this the same exact way you did when you first unlocked your phone..
unless of coarse you saved your unlock_code.bin.
but if you didn't you can always just get it back on the htcdev unlock site..
once your phone is unlocked, it is unlocked..
there is NO worry of locking your bootloader and then being un-able to unlock it again.
hope this clears it up guys...
Thanks guys! I got it done using these instructions.
Related
So I am trying to Un-Root my HTC DNA, and I was following these steps
http://forum.xda-developers.com/showthread.php?t=2017525
But when I'm running the RUU, i get an error 155: Unknown error.
Telling me to get the correct ROM Update Utility, but i can't find it anywhere but on that website.
Once the RUU Update has failed and I restart the phone,it goes straight into boot menu with ****TAMPERED*****. ******RELOCKED******, and *******Security Warning******* At the top and when I try to do a factory data reset on the phone, it goes into the fastboot menu, with the same notifications uptop.
Any idea what might be going on?
RUU_DLX_WL_JB_45_VERIZON_WWE_1.15.605.4_Radio_1.00.00.1023_3_NV_VZW_1.98_002_release_290923_signed
this is the name of the RUU u need. not sure about the errors. just google uroot and relock dna and it should be the top link. or just look in rootzwiki
it looks like you got the correct RUU, try a different usb port. How far does it go? does it even start. make sure your usb debugging and booted in fastboot.
cmay227 said:
RUU_DLX_WL_JB_45_VERIZON_WWE_1.15.605.4_Radio_1.00.00.1023_3_NV_VZW_1.98_002_release_290923_signed
this is the name of the RUU u need. not sure about the errors. just google uroot and relock dna and it should be the top link. or just look in rootzwiki
it looks like you got the correct RUU, try a different usb port. How far does it go? does it even start. make sure your usb debugging and booted in fastboot.
Click to expand...
Click to collapse
I have tired to do it in all three of my USB Ports.
All i can say is try starting the RUU.exe and have your phone booted normally. not in fastboot. it worked for me both ways. might be something to try. If it fails again try re-downloading the file, rinse and repeat.
cmay227 said:
RUU_DLX_WL_JB_45_VERIZON_WWE_1.15.605.4_Radio_1.00.00.1023_3_NV_VZW_1.98_002_release_290923_signed
this is the name of the RUU u need. not sure about the errors. just google uroot and relock dna and it should be the top link. or just look in rootzwiki
it looks like you got the correct RUU, try a different usb port. How far does it go? does it even start. make sure your usb debugging and booted in fastboot.
Click to expand...
Click to collapse
Pretty sure you can't relock unless you used htcdev.
As Adryn said if you used htcdev I'm pretty sure we can still "relock" but the exploit has permanatly changed the CID of all our phones. So fastboot oem lock still works and the ruu will revert the phone to its "stock" state as in factory shipped software and bloat but the bootloader will still reflect that it has been tampered with and the same token can be used to unlock again immediately afterward. So what I'm saying to all others is that the exploit is irreversible. There were a couple guys toying with it in the irc yesterday. But unless you absolutely have to do this theres really NO reason because you won't be able to cover the tracks of the hacking you've already done to your phone.
jonesin said:
As Adryn said if you used htcdev I'm pretty sure we can still "relock" but the exploit has permanatly changed the CID of all our phones. So fastboot oem lock still works and the ruu will revert the phone to its "stock" state as in factory shipped software and bloat but the bootloader will still reflect that it has been tampered with and the same token can be used to unlock again immediately afterward. So what I'm saying to all others is that the exploit is irreversible. There were a couple guys toying with it in the irc yesterday. But unless you absolutely have to do this theres really NO reason because you won't be able to cover the tracks of the hacking you've already done to your phone.
Click to expand...
Click to collapse
To me the main benefit of running the RUU was to get rid of the Tampered status in the boot loader screen. But your right it will say Relocked instead of locked. no way around that......so kinda pointless warranty wise.just removes root
Well I'm in the process of redownloading the RUU file.
I am still kind of curious, how come I can't reset to factory default through the boot loader or though the settings -> restore feature? Does it have to do with being rooted?
If you don't have a good reason to unroot, I would encourage you to wait. Those have have unrooted, and relocked, have had problems unlocking a second time.
I've locked and relocked many times and It was a pain in the ass to get unlocked status back. I would get the unlock prompt on the phone and choose yes but it ended up always still saying relocked. I finallly read to shut phone down completly before going into fasboot. I was just choosing restart. Have not had a issue unlocking since. Unlock code takes everytime.
Sent from my HTC6435LVW using xda app-developers app
OP, if you're attempting to get the 'locked' message on the bootloader back, you won't (as others have stated,) but if you're trying this to get your warranty back, the persons at Verizon won't look at this when you return the device. Neither will the people at the Verizon corporate office. All they will do is completely reflash the device including bootloader and that will be that.
Mazer
Sent from my rooted and debloated Droid DNA.
Mazer_R said:
OP, if you're attempting to get the 'locked' message on the bootloader back, you won't (as others have stated,) but if you're trying this to get your warranty back, the persons at Verizon won't look at this when you return the device. Neither will the people at the Verizon corporate office. All they will do is completely reflash the device including bootloader and that will be that.
Mazer
Sent from my rooted and debloated Droid DNA.
Click to expand...
Click to collapse
Thanks from the reply. I mainly wanted to un-root it to 1) Check for updates an 2) Restore to OEM to see if a problem I am/was having with my Aux jack could have been fixed that way.
I managed to get it to work...I think what the problem was, was that I had PDANET installed, so when the phone rebooted to flash the ruu, Pdanet started and caused the flash to fail. I disabled Pdanet and any other non-essential programs that were running in the background on my laptop, and the flashing worked.
I wasn't too worried about the root or the unlocked status because I'll be returning it under the 14 day guarantee.
I have a rooted Rezound running the OTA ICS. I also have Amon Ra recovery. The newest Firmware update keeps downloading. Once it does the phone shuts off and goes straight to Amon Ra which does not install new firmware. So I reboot the phone and the download process starts all over again. Is there any way to get this new firmware with having to factory reset? Thanks in advance!
xCOOLHWIPx said:
I have a rooted Rezound running the OTA ICS. I also have Amon Ra recovery. The newest Firmware update keeps downloading. Once it does the phone shuts off and goes straight to Amon Ra which does not install new firmware. So I reboot the phone and the download process starts all over again. Is there any way to get this new firmware with having to factory reset? Thanks in advance!
Click to expand...
Click to collapse
If you want the OTA to go you need to flash stock recovery.
- "Is it dark in there?"
drynyks said:
If you want the OTA to go you need to flash stock recovery.
- "Is it dark in there?"
Click to expand...
Click to collapse
Thanks. I was hoping that wouldn't be the case. Do you know of anyway of getting rid of the update? I would rather not have the update than flash back to stock. But my phone shutting off every few hours is pretty annoying. Thanks again.
xCOOLHWIPx said:
Thanks. I was hoping that wouldn't be the case. Do you know of anyway of getting rid of the update? I would rather not have the update than flash back to stock. But my phone shutting off every few hours is pretty annoying. Thanks again.
Click to expand...
Click to collapse
Remove otacerts... Don't remember the exact location and I'm on my phone, a search on that should turn it up.
Sent from my ADR6425LVW using Tapatalk 2
mjones73 said:
Remove otacerts... Don't remember the exact location and I'm on my phone, a search on that should turn it up.
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
\etc\security\otacerts.zip
same problem here
hgoldner said:
\etc\security\otacerts.zip
Click to expand...
Click to collapse
I cant seem to find the otacert on my htc resound. I have tried every way to update the new radios and nothing works. I have tried everything but a hard reset and relocking the bootloader. I would rather shut the stupid auto update off. My phone resets at 12:30 am and again at 4am. considering I need the alarm clock on my phone it renders it useless. Any help is appreciated. I am Rooted running stock OTA ICS with Amon Ra.
xander5680 said:
I cant seem to find the otacert on my htc resound. I have tried every way to update the new radios and nothing works. I have tried everything but a hard reset and relocking the bootloader. I would rather shut the stupid auto update off. My phone resets at 12:30 am and again at 4am. considering I need the alarm clock on my phone it renders it useless. Any help is appreciated. I am Rooted running stock OTA ICS with Amon Ra.
Click to expand...
Click to collapse
In confused why don't you just flash stock recovery and let the OTA go? Problem solved. Oh you'd have to relock also.
drynyks said:
In confused why don't you just flash stock recovery and let the OTA go? Problem solved. Oh you'd have to relock also.
Click to expand...
Click to collapse
I have relocked the bootloaderb and gone back to stock 605.12 now it won't download the ota updates. I'm a little stuck on this one
xander5680 said:
I have relocked the bootloaderb and gone back to stock 605.12 now it won't download the ota updates. I'm a little stuck on this one
Click to expand...
Click to collapse
Are you going to settings> software update> check new?
From 605.12 you should get a small OTA first then the big one after that one is done. I just did same procedure in the last week on my wife's phone.
Btw might want to be on WiFi if you aren't already for the download.
Having the same issue here as OP and been searching forums for days looking for help...
First, I'm on 605.13 already, stock ROM, rooted with Amon ra. I realize the steps I need to take but can't find any specifics.
Could someone please spell out the specifics of how to flash the stock recovery, and if I can use the 605.12 RUU to do this being on .13 already. I keep seeing others posting about just renaming a file to recovery.img and pushing using fastboot, but I'm not sure how to obtain the correct file.
Do you relock bootloader first or flash stock recovery first and the relock? BTW I'm s-on stil. Thanks in advance
drynyks said:
Are you going to settings> software update> check new?
From 605.12 you should get a small OTA first then the big one after that one is done. I just did same procedure in the last week on my wife's phone.
Btw might want to be on WiFi if you aren't already for the download.
Click to expand...
Click to collapse
I have tried your suggestions. It goes to download the small update and never downloads it. It says unable to download after about 3minutes.
fixed
xander5680 said:
I have tried your suggestions. It goes to download the small update and never downloads it. It says unable to download after about 3minutes.
Click to expand...
Click to collapse
For some apparent reason the 605.13 update downloaded this afternoon and the 605.14 updated. Its all set after a frustrating 2 weeks of digital torture. thanks to all that helped. I had to scour all these resources and forums to get this done but this is what worked for me. I relocked the bootloader then I used the 605.12 RRU.exe program. After about a day I checked for the updates and they downloaded and installed successfully.
Xander, since you just got this working, can you please confirm the process - I'm about to do this myself and want to verify the steps...
1) Reboot into hboot > fastboot and relock bootloader via fastboot oem lock
2) download 3.14.605.12 RUU.exe (I'm currently on 3.14.605.13)
3) Reboot phone into hboot > fastboot usb
4) run RUU.exe from PC
Is that it? Anything I'm missing here or am I on the right path?
mattman37 said:
Xander, since you just got this working, can you please confirm the process - I'm about to do this myself and want to verify the steps...
1) Reboot into hboot > fastboot and relock bootloader via fastboot oem lock
2) download 3.14.605.12 RUU.exe (I'm currently on 3.14.605.13)
3) Reboot phone into hboot > fastboot usb
4) run RUU.exe from PC
Is that it? Anything I'm missing here or am I on the right path?
Click to expand...
Click to collapse
U have step 1 and step 2 correct. Step 3 would be to connect the phone to the computer and run the 605.12 ruu.exe tool. After that u are now back to a stock phone. After the initial setup of adding your gmail account and contacts you can now go into system settings and check for update. As I stated before my phone would not download the update for some odd reason. I tried it a couple more times without success. Today on a whim I went to check for the update again and it started to download. After the small 6mb file was complete the next update for 605.14 downloaded without anny issues. Make sure you delete any zip files off your external SD card labeled ph98img.zip if u tried that method.
Step1 relock boot loader
Step2 run 3.14.605.12 ruu.exe
Step3 check for updates
Step4 unlock phone if you want to
I hope this helps anyone. Let me know if you have any questions.
Thanks.. Got it! And I got both the 13 and 14 updates almost immediately afterwards. I appreciate the confirmation about the process...
Sent from my ADR6425LVW using Tapatalk 2
xander5680 said:
U have step 1 and step 2 correct. Step 3 would be to connect the phone to the computer and run the 605.12 ruu.exe tool. After that u are now back to a stock phone. After the initial setup of adding your gmail account and contacts you can now go into system settings and check for update. As I stated before my phone would not download the update for some odd reason. I tried it a couple more times without success. Today on a whim I went to check for the update again and it started to download. After the small 6mb file was complete the next update for 605.14 downloaded without anny issues. Make sure you delete any zip files off your external SD card labeled ph98img.zip if u tried that method.
Step1 relock boot loader
Step2 run 3.14.605.12 ruu.exe
Step3 check for updates
Step4 unlock phone if you want to
I hope this helps anyone. Let me know if you have any questions.
Click to expand...
Click to collapse
Can anyone point me to where to find the 3.14.605.12 ruu.exe? I didn't want to spend all day flashing my phone, but ok, I guess I can to get rid of this annoying update.
digitalmofo said:
Can anyone point me to where to find the 3.14.605.12 ruu.exe? I didn't want to spend all day flashing my phone, but ok, I guess I can to get rid of this annoying update.
Click to expand...
Click to collapse
Check the march 10 2013 thread titled rezound in trouble please help. The download link is there. Its under the vigor section.
Here is the RUU I used without issues:
shipped-roms.com/index.php?category=android&model=Vigor
(http removed from link due to forum limitations)
3rd from the bottom...
Okay, guys, I apologize for what I'm about to ask, but I am now completely lost in the Global Update thread, so I needed to start fresh.
I was rooted and on stock 3.14.605.13. I kept getting annoying update messages from Verizon and tried several forum suggestions to turn them off. Finally I just decided to try to get the update. I was able to unroot and install an RUU back to 3.14.605.12, but now I'm completely stuck. :crying: I'm getting the same Service Unavailable message as others who try to get the small .13 update.
I have downloaded the 3.14.605.13 update zip but can't decipher how to get it installed since the Global Update Thread is now so jumbled.
If anyone has the time to helps us NOOBS (I think I saw several others in my situation), could you please give a step by step rundown of what we need to do? Please start from step 1. For example, do I need to root again now before I can get up to .13?
Finally, if I do get to .13, can I just unroot and get the new global update via Verizon?
hunteditor said:
Okay, guys, I apologize for what I'm about to ask, but I am now completely lost in the Global Update thread, so I needed to start fresh.
I was rooted and on stock 3.14.605.13. I kept getting annoying update messages from Verizon and tried several forum suggestions to turn them off. Finally I just decided to try to get the update. I was able to unroot and install an RUU back to 3.14.605.12, but now I'm completely stuck. :crying: I'm getting the same Service Unavailable message as others who try to get the small .13 update.
I have downloaded the 3.14.605.13 update zip but can't decipher how to get it installed since the Global Update Thread is now so jumbled.
If anyone has the time to helps us NOOBS (I think I saw several others in my situation), could you please give a step by step rundown of what we need to do? Please start from step 1. For example, do I need to root again now before I can get up to .13?
Finally, if I do get to .13, can I just unroot and get the new global update via Verizon?
Click to expand...
Click to collapse
going to need some more information:
1. Are you S-off or S-on
2. Are you dev unlocked, locked, or engineering hboot
3. What hboot are you currently on
Wow, that was fast.
synisterwolf said:
going to need some more information:
1. Are you S-off or S-on
2. Are you dev unlocked, locked, or engineering hboot
3. What hboot are you currently on
Click to expand...
Click to collapse
S-ON
***RELOCKED*** (I did the HTC unlock with a pin code when I originally rooted, but I "unrooted" via a one-click program, so I don't know the correct answer to the lock question). I relocked the bootloader via sdk if that helps.
hboot is 2.25
hunteditor said:
S-ON
***RELOCKED*** (I did the HTC unlock with a pin code when I originally rooted, but I "unrooted" via a one-click program, so I don't know the correct answer to the lock question). I relocked the bootloader via sdk if that helps.
hboot is 2.25
Click to expand...
Click to collapse
you should be good to do the update.
ruu using this zip http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/
(place on root of sd card, rename PH98IMG.zip)
it will run 2 times. once with be bootloader and recovery, second time will be the full rom.
this will get you to stock OTA should show up a little while after its all installed and connected to the network.
EDIT:
If updated doesnt show up in a day you should be able to update with this zip: http://forum.xda-developers.com/showpost.php?p=40768590&postcount=35
Okay, I think you're going to be able to get me there ... but ...
I downloaded the zip file and renamed it to PH98IMG.zip. I copied it to the root of both the internal and external cards since I wasn't sure which it needed to be on.
Now how do I execute the RUUx2s? The last one I did to get back to .12 was an .exe file, so that was easy.
I do have SKD and can open a command prompt, so you don't have to go that far back in instructions.
hunteditor said:
Okay, I think you're going to be able to get me there ... but ...
I downloaded the zip file and renamed it to PH98IMG.zip. I copied it to the root of both the internal and external cards since I wasn't sure which it needed to be on.
Now how do I execute the RUUx2s? The last one I did to get back to .12 was an .exe file, so that was easy.
I do have SKD and can open a command prompt, so you don't have to go that far back in instructions.
Click to expand...
Click to collapse
once on root of external sd card. reboot the phone into bootloader
power off device hold vol - and power till you see hboot
hboot will detect it and run for you.
make sure you have 70+ battery before trying this. and do not pull the battery or loose power or it will birck.
Worked like a charm. A million thanks to you.
Donation on the way!
Thanks again for being so patient!
hunteditor said:
Worked like a charm. A million thanks to you.
Donation on the way!
Thanks again for being so patient!
Click to expand...
Click to collapse
wow, thank you kindly. Any time you need help just ask, thats how we all learn.
Okay, hopefully last question.
I downloaded the OTA zip just in case.
If I need to end up doing that manually, do I rename it (and if so to what?) copy it to root and then run hboot?
hunteditor said:
Okay, hopefully last question.
I downloaded the OTA zip just in case.
If I need to end up doing that manually, do I rename it (and if so to what?) copy it to root and then run hboot?
Click to expand...
Click to collapse
just like the ruu rename it to PH98IMG.zip and flash in hboot. again make sure you have enough battery
Ok, so I've been rooted but for he most part stock. The last OTA kept failing to download so I relocked my bootloader, used the ruu update tool from android police, accepted the update, but had the genius idea to run my nandroid restore after. Since then I have not been able to boot up and my efforts to fix the problem have only made it worse. I can no longer get into recovery and when I try it gives me a security warning. I am at a loss and miss my phone, forced to use Iphone 4 as back up and I refuse to learn how to use it. Please give ideas on how to fix in noob language as I am obviously not an expert.
fivedezs said:
Ok, so I've been rooted but for he most part stock. The last OTA kept failing to download so I relocked my bootloader, used the ruu update tool from android police, accepted the update, but had the genius idea to run my nandroid restore after. Since then I have not been able to boot up and my efforts to fix the problem have only made it worse. I can no longer get into recovery and when I try it gives me a security warning. I am at a loss and miss my phone, forced to use Iphone 4 as back up and I refuse to learn how to use it. Please give ideas on how to fix in noob language as I am obviously not an expert.
Click to expand...
Click to collapse
just ruu again. make sure your bootloader is locked and start from square one.
place ruu on root of sd
reboot hboot
let it run twice.
synisterwolf said:
just ruu again. make sure your bootloader is locked and start from square one.
place ruu on root of sd
reboot hboot
let it run twice.
Click to expand...
Click to collapse
I could use help trying to find the RUU I need, my search has been fruitless. What I have is a tool that updates my RUU for me and it only works when my phone successfully boots. I tried using it from the bootloader menu and that gave me a security warning.
moonshine doesn't like xposed
fastboot oem lock
device modified
s-on
relocked
security warning
used 0PJAIMG.zip on sd card cuz ruu failed, and fastboot flash unlock token gave "no such partition" (or something) and flashing the clean system.emmc.win gave same error
it did it's thing with flashing opjaimg.zip and when finished it said press power button to complete and it now wont come back on.
plugged into charger i get no led
effen fantastic
i want my m7 back...........
moonshine was for the M7. They have no m9 varient. why would you do that?
94tbird said:
moonshine was for the M7. They have no m9 varient. why would you do that?
Click to expand...
Click to collapse
i ment sunshine. i was tired. the apk ran fine before i had exposed, got paid yesterday and was going to drop the $25 for s-off.
and all i did was relock bootloader and run ruu from sd card and it broke device
ahh ok makes more sense now, sorry.
jpwhre said:
i ment sunshine. i was tired. the apk ran fine before i had exposed, got paid yesterday and was going to drop the $25 for s-off.
and all i did was relock bootloader and run ruu from sd card and it broke device
Click to expand...
Click to collapse
was it the original .17 ruu zip?
Unlock your bootloader again by running the unlock file in download mode. *I had to do this twice, as it failed the first time after relocking*
Flash back to stock rooted.
Run RUU
I locked my bootloader thinking I would need to when running the RUU. Turned out that I couldn't do anything without unlocking again. I thought I was stuck too, but then the unlocked worked (luckily)
He said he couldn't power up. But I suspect he can.
Hold Vol Up & Down and Power all at once for a while.
mswlogo said:
He said he couldn't power up. But I suspect he can.
Hold Vol Up & Down and Power all at once for a while.
Click to expand...
Click to collapse
same thing happened to me when i was on .30 and accidentally flashed the .17 RUU... its bricked, sorry :/ it wont even power on. Mine didnt I just took it back to sprint and told them it was DOA when i got it.. they wont be able to power it on either so just take it back to them and play dumb. They will get you a new one.
OMJ said:
was it the original .17 ruu zip?
Click to expand...
Click to collapse
https://www.androidfilehost.com/?fid=95916177934554226
Harfainx said:
Unlock your bootloader again by running the unlock file in download mode. *I had to do this twice, as it failed the first time after relocking*
Flash back to stock rooted.
Run RUU
I locked my bootloader thinking I would need to when running the RUU. Turned out that I couldn't do anything without unlocking again. I thought I was stuck too, but then the unlocked worked (luckily)
Click to expand...
Click to collapse
Nope
mswlogo said:
He said he couldn't power up. But I suspect he can.
Hold Vol Up & Down and Power all at once for a while.
Click to expand...
Click to collapse
My fingers hurt
deakelem said:
same thing happened to me when i was on .30 and accidentally flashed the .17 RUU... its bricked, sorry :/ it wont even power on. Mine didnt I just took it back to sprint and told them it was DOA when i got it.. they wont be able to power it on either so just take it back to them and play dumb. They will get you a new one.
Click to expand...
Click to collapse
My girlfriend told me to do the same thing, after looking at me and asking what i did (and tells me to quit doing this sh!t, again)
When I fastboot oem lock, it rebooted into bootloader (not download) and gave me security warning and refuse to reboot to system.
I tried to flash unlock token back and it kept giving me errors of partition doesn't exist. Ran RUU and it put device into fastboot oem rebootRUU mode and then sat for 5 minutes waiting on bootloader. So i put above zip on sd and flashed in download mode. Finished successfully and then gave option to reboot, and it never came back on.
14 days to the day today. No questions asked, they just exchanged it.
Girlfriend asked me the dumbest question afterwords.. "You going to eff with this one too?" of course i am, duh
jpwhre said:
14 days to the day today. No questions asked, they just exchanged it.
Girlfriend asked me the dumbest question afterwords.. "You going to eff with this one too?" of course i am, duh
Click to expand...
Click to collapse
Boy, are you in the dog house lol
Congrats on getting a new one. Think twice, flash once.
I'm always Leary of EVER going backwards on firmware.
mswlogo said:
Boy, are you in the dog house lol
Congrats on getting a new one. Think twice, flash once.
I'm always Leary of EVER going backwards on firmware.
Click to expand...
Click to collapse
Well we've been together for 4.5 years and i've been doing this crap since 2007 so there is no way she'll get me to stop.
I didn't go backwards. I was on bone stock rooted .30 with xposed, and instead of going the the bizzilian files in recovery to delete, rename and uninstall the hard way, i figured oem lock and flashing stock sprint .30 and rooting again would be easier.
Found culprit though. Just settling down from school and store run, time to start over with new phone and do s-off before i do anything else, low and behold the usb port on laptop is failing. I keep all files/tools on 2 tb external hard drive connected to 3.0 port. One 2.0 usb port i knew failed last year, only left with 1 and it died. couldn't get phone to reboot with adb, or get adb to find device. Getting unlock token froze half way thru.
Copying fold to desktop to plug phone into 3.0 and go from there.
Thank you, thank you!
mswlogo said:
He said he couldn't power up. But I suspect he can.
Hold Vol Up & Down and Power all at once for a while.
Click to expand...
Click to collapse
I had bricked my phone for a couple of days before finding this little nugget of gold. So pleased to find that everything was as I had left it and no need to format. I'll NEVER format an SD card as internal again.
So very grateful that you posted this. :victory: