If you have problems re-unlocking your DNA here's what worked for me.probably explaining to much as most here already know how to get to fastboot every way possible, but here goes. posted this in a Q&A thread earlier , just thought I'd post it here to make it easier to see
I hold the power button to get the power off or restart prompt, choose power off...do not choose restart. once the phone is off. Hold the volume down and press and hold the power button....keep holding.... phone will boot normally except the buttons on the bottom of the phone will flash....Keep holding.. the screen will turn off for a few more seconds Keep holding...and then your in the bootloader. choose fastboot and then run the fastboot unlock command.Says unlocked every time. took 3 hours wed. night of running the unlock command only to find out it still said relocked. repeated till i found out about the completely turning off the phone thing in the one x forums. Tried it and no problems since. have done it about 20 times in the last 2 days.
Sorry for sounding stupid right now, but what exactly do you mean by re-unlocking? To me, it sounds like the phone was unlocked, then relocked, and now it's being locked again? Just curious
I've had no issues re-locking after the jcase unlock process ... I've used the all in one program to re-lock and unlock , I've done it a total of three times on two separate DNA's
From my DROID DNA
Some people have had issues of the unlock not taking after locking.
This has worked for me every time after i had issues the first time i locked.
Anyone aware of an online video showing this process?
I'm clicking over to YouTube now but I think it's too early in the release to find one.
Which process? Have you unlocked yet? If not, this here is not ment untill you have unlocked and then re- locked you bootloader.
Sent from my HTC6435LVW using xda app-developers app
does it work?
Powering off all the way, and then booting straight to the bootloader maya help.
I also a separate way to unlock if it is really stubborn.
jcase said:
Powering off all the way, and then booting straight to the bootloader maya help.
I also a separate way to unlock if it is really stubborn.
Click to expand...
Click to collapse
Jcase, One of my testers for kernel had to RUU. He could not unlock the first 3x times he tried with the SAME token he received after altering the CID with your tool. The fourth time the tester did the fastboot flash unlocktoken Unlock_code.bin the bootloader status changed to UNLOCKED.
just thought id let ya know
tyvm
cmay227 said:
If you have problems re-unlocking your DNA here's what worked for me.probably explaining to much as most here already know how to get to fastboot every way possible, but here goes. posted this in a Q&A thread earlier , just thought I'd post it here to make it easier to see
I hold the power button to get the power off or restart prompt, choose power off...do not choose restart. once the phone is off. Hold the volume down and press and hold the power button....keep holding.... phone will boot normally except the buttons on the bottom of the phone will flash....Keep holding.. the screen will turn off for a few more seconds Keep holding...and then your in the bootloader. choose fastboot and then run the fastboot unlock command.Says unlocked every time. took 3 hours wed. night of running the unlock command only to find out it still said relocked. repeated till i found out about the completely turning off the phone thing in the one x forums. Tried it and no problems since. have done it about 20 times in the last 2 days.
Click to expand...
Click to collapse
I have been wrestling with this problem for hours. after I had root, and installed 4.2 camera patch I kept have FC in video recorder. decided to go back to stock and re-root. but this re-unlock had me hung up.
I did exactly like you said, and it worked 1st try. thanks a lot.
jasonpascoe said:
I have been wrestling with this problem for hours. after I had root, and installed 4.2 camera patch I kept have FC in video recorder. decided to go back to stock and re-root. but this re-unlock had me hung up.
I did exactly like you said, and it worked 1st try. thanks a lot.
Click to expand...
Click to collapse
I'm glad it worked for you. I had the same issues.
I'm far from an expert, but in discussions with some experts over the weekend, there should be no reason to RUU and then re-unlock your phone. (I'm not knocking those that did this already, because I also re-unlocked, lol)
There is a thread in the Dev section that has a stock/rooted NAND TWRP backup that you can restore. Someone was nice enough to start with RUU, unlock, root and then back it up and share it with us.
Zarboz said:
Jcase, One of my testers for kernel had to RUU. He could not unlock the first 3x times he tried with the SAME token he received after altering the CID with your tool. The fourth time the tester did the fastboot flash unlocktoken Unlock_code.bin the bootloader status changed to UNLOCKED.
just thought id let ya know
Click to expand...
Click to collapse
yeah this happened to me too >_< haha. I just tried to re-unlock with my unlock_code.bin and it "appeared" to work but only to see it says "relocked" still, so I will try this method when I am out of class
WorldOfJohnboy said:
I'm far from an expert, but in discussions with some experts over the weekend, there should be no reason to RUU and then re-unlock your phone. (I'm not knocking those that did this already, because I also re-unlocked, lol)
There is a thread in the Dev section that has a stock/rooted NAND TWRP backup that you can restore. Someone was nice enough to start with RUU, unlock, root and then back it up and share it with us.
Click to expand...
Click to collapse
Oh trust me, Nandroids are not always the answer. Especially when your perfectly working one up and gives an md5 mismatch.
While you can recalc the md5, its not worth it IMO.
Related
EDIT: UPDATE .... i managed to get the phone rebooted .... held the force reboot buttons for literally over a min in desperation.... not i need to fully unroot and start from scratch but am having trouble with that still.... can anyone help me either (A) get s-off ... or (B) get it so that i am completely unrooted so i can start over from scratch to get s-off????
Ok folks, i am officially stuck.... its been quite awhile since i have really asked for help on here but i am stuck in a really bad way!!!
Here is how i got to where i am
Just bought my brand new EVO LTE today and went to root it using "[ROOT] RegawMOD EVO 4G LTE Rooter | Updated 06.13.12" from this section!
everything seemed to work great and it said everything rooted properly.... I love Clockwork mod recovery so i then flashed that and it worked properly to or so i thought! so i went to create an origional Nand but it would not work, so i decided to flash TWRP back instead and do that way. when going into the bootloader it said "Tampered" as expected, but it still said S-on so obviously not a proper and correct root.
So i ran RegaMOD again as it said in the instructions, but it would never get passed the HTCdev part, it would just say "sucessfully logged out" and sit there forever and do nothing. So after a few tries of that i decided to unroot and start over from scratch. I could not find an unroot method for RegaMOD so i then went to the other root method "How to Root HTC Evo 4G LTE! [Windows/Mac/Linux] - by Zedomax" in this section and saw it had an unroot method which i followed to the letter! did full unroot through SuperSU and then downloaded the stock RUU from that section for my phone with the proper version number.
everything seemed to be running fine went to the black "HTC" screen and everything was going smoothly.... then the update failed and my phone stayed on the black HTC screen. my computer prompted me to recover which i could not really do as you can't pull the battery on this phone. So i then tried to update the RUU again except this time it did not list a current software version, only the one i was updating too.... it failed again 2 more times!!
when plugged into the computer my phone displays the black "HTC" screen
when plugged into the charger it displays the following screen info (bootloader look)
*** TAMPERED ***
*** UNLOCKED ***
JEWEL PUT SHIP S-ON RL
HBOOT-1.12.0000
RADIO-1.02.12.0427
OpenDSP-v25.1.0.32.0405
eMMC-boot
Apr 26 2012,19:54:01
FASTBOOT AO <---- MIGHT BE FASTBOOT AC HARD TO TELL
Update Fail!
when un-plugged it says almost the same thing
*** TAMPERED ***
*** UNLOCKED ***
JEWEL PUT SHIP S-ON RL
HBOOT-1.12.0000
RADIO-1.02.12.0427
OpenDSP-v25.1.0.32.0405
eMMC-boot
Apr 26 2012,19:54:01
FASTBOOT <---- THIS IS THE ONLY CHANGE
Update Fail!
no buttons do anything at all, in any combination or holding pattern
PLEASE HELP ME!!!!! THANKS TO ALL IN ADVANCE!!!
just one thing, s-on or s-ff has nothing to do with root
did you relock your bootloader before running the RUU?
And now we see what happens when we blindly click stuff without an understanding of what we're doing. I hate to be a douche (and I'm not usually) but this is EXACTLY the kind of thing you should NOT do with a brand new phone without intensive study. While the one-click root methods are convenient as hell, their major shortcoming is that they don't allow people to learn what they're DOING when they click that batch file...which leads to problems like yours.
As mentioned above, you need to relock your bootloader before running the RUU.
Also as mentioned s-off and root are completely different...and frankly you don't need s-off with HTC's unlock anymore.
Get your phone back to the bootloader, plugged in via USB to your computer.
Install adb (you should already have it, I hope) and type fastboot oem lock from a dos prompt (command prompt).
That relocks your bootloader. reboot into bootloader and you should see 'relocked'.
THEN run the RUU and start over....and this time please read and understand what you're doing rather than just blindly doing the 'cool root thing'.
no, i did not re-lock the boot loader.... didnt know you needed to, not used to that on the OG EVO... how do you go about redoing that? I always thought S-OFF was an important part of root..... the main reason i looked and noticed it was since i flashed clockworkmod recovery and wanted to go back to TWRP i read on their page that "You must be S-OFF or have taken HTC's unlock to use a recovery on your device!" I guess that since i used HTC unlock i could flash, but either way, should i need to go back to stock for any reason, could you please tell me the proper steps?
Thanks a million!!!
smw6180 said:
And now we see what happens when we blindly click stuff without an understanding of what we're doing. I hate to be a douche (and I'm not usually) but this is EXACTLY the kind of thing you should NOT do with a brand new phone without intensive study. While the one-click root methods are convenient as hell, their major shortcoming is that they don't allow people to learn what they're DOING when they click that batch file...which leads to problems like yours.
As mentioned above, you need to relock your bootloader before running the RUU.
Also as mentioned s-off and root are completely different...and frankly you don't need s-off with HTC's unlock anymore.
Get your phone back to the bootloader, plugged in via USB to your computer.
Install adb (you should already have it, I hope) and type fastboot oem lock from a dos prompt (command prompt).
That relocks your bootloader. reboot into bootloader and you should see 'relocked'.
THEN run the RUU and start over....and this time please read and understand what you're doing rather than just blindly doing the 'cool root thing'.
Click to expand...
Click to collapse
Sorry I just got excited, I have run root on my last 2 phones (much more research on those) and just kinda fell into a super late night lazy not thinking groove... please dont be offended, the reason a rarely dont ask for help is i usually have not needed it.... no need to get hostile.... thankyou for the responce
smw6180 said:
And now we see what happens when we blindly click stuff without an understanding of what we're doing. I hate to be a douche (and I'm not usually) but this is EXACTLY the kind of thing you should NOT do with a brand new phone without intensive study. While the one-click root methods are convenient as hell, their major shortcoming is that they don't allow people to learn what they're DOING when they click that batch file...which leads to problems like yours.
As mentioned above, you need to relock your bootloader before running the RUU.
Also as mentioned s-off and root are completely different...and frankly you don't need s-off with HTC's unlock anymore.
Get your phone back to the bootloader, plugged in via USB to your computer.
Install adb (you should already have it, I hope) and type fastboot oem lock from a dos prompt (command prompt).
That relocks your bootloader. reboot into bootloader and you should see 'relocked'.
THEN run the RUU and start over....and this time please read and understand what you're doing rather than just blindly doing the 'cool root thing'.
Click to expand...
Click to collapse
+1
shootin4aces said:
Sorry I just got excited, I have run root on my last 2 phones (much more research on those) and just kinda fell into a super late night lazy not thinking groove... please dont be offended, the reason a rarely dont ask for help is i usually have not needed it.... no need to get hostile.... thankyou for the responce
Click to expand...
Click to collapse
Wasn't being hostile and I'm not offended. It's just there are entirely too many people who haven't been paying attention to what they're doing and get upset about it when it all blows up in their face.
And for the record every phone is different. I've rooted my last 4 Android phones, 3 evo's and the hero, and root was different on each one, with different potential problems. Being excited is great. But you need to take the time to learn what you're doing, first.
shootin4aces said:
no, i did not re-lock the boot loader.... didnt know you needed to, not used to that on the OG EVO... how do you go about redoing that? I always thought S-OFF was an important part of root..... the main reason i looked and noticed it was since i flashed clockworkmod recovery and wanted to go back to TWRP i read on their page that "You must be S-OFF or have taken HTC's unlock to use a recovery on your device!" I guess that since i used HTC unlock i could flash, but either way, should i need to go back to stock for any reason, could you please tell me the proper steps?
Thanks a million!!!
Click to expand...
Click to collapse
read the post above yours he did tell you how to do it..lol
Oh and before I forget: Don't use CWM. Unless they've fixed it in the last couple of days it breaks your /misc partition, which is quite probably what caused your issues in the first place.
Use TWRP. After you have root/unlocked you can download goomanager from the Play Store...it will install it for you.
smw6180 said:
Wasn't being hostile and I'm not offended. It's just there are entirely too many people who haven't been paying attention to what they're doing and get upset about it when it all blows up in their face.
And for the record every phone is different. I've rooted my last 4 Android phones, 3 evo's and the hero, and root was different on each one, with different potential problems. Being excited is great. But you need to take the time to learn what you're doing, first.
Click to expand...
Click to collapse
+1 and wrong section
This is the method I used on my 4lte without a problem. But you should read entire post before attempting cause it flashes TWRP recovery automatically along with SU. Clockwork still is buggy.
http://forum.xda-developers.com/showthread.php?p=26955832
from my "Beach Watcher" 4LTE
thankyou
all problems have been fixed, thankyou everyone for all your help
again, sry for posting in the wrong forum with this issue, and i am sorry if i came off as a noob! I'm really not, just completely jumped the gun and am very very tired as i have been up for almost 36 hours now
thankyou again for all the help, and as i normally do, i will perform all my research before my next venture.... a lot has changed between this phone and my last one that i rooted and modded, i will be more prepared in the future!
Selders, you're here now?! Good to see ya here
sent from a shining jewel 4g LTE
I cannot get into regular bootloader. It just either sits and stalls, goes to HTC screen, or just straight to recovery. This has happened on and off before but I was always able to get it after a few tries. I've been trying for 2 days since the new ICS was released by Sprint but it's been no go.
I believe I have 1.5 Hboot, but I can't tell for sure because I can't access it. I had to take the long route when I had to root with the HTC unlock thing, etc.
I've tried to get to HBoot using QuickBoot app and using the menu option within TWRP 1.1 and now 2.2 (thought that might be the problem, but guess not)...still just stalls and nothing happens after reset
I've been using only rooted OTA's on my phone and only rooted for bloatware removal and wifi tether. No custom roms. No ICS leak.
The buttons of course work. As soon as I take my finger off of the Down volume button, the phone will activate and boot up normal in some cases.
I don't know if this is causing other issues with my phone as it self reboots or freezes a few times a week. I was looking forward to ICS update because I was hoping it would fix the reboots and freezing. Everything else works fine with the phone.
Any help would be greatly appreciated.
try "adb reboot bootloader" and see if your phone gets into bootloader.
mnomaanw said:
try "adb reboot bootloader" and see if your phone gets into bootloader.
Click to expand...
Click to collapse
Don't you have to be in Bootloader to get the adb commands to work? I tried using fastboot to connect and no go.
brokenmouse said:
Don't you have to be in Bootloader to get the adb commands to work? I tried using fastboot to connect and no go.
Click to expand...
Click to collapse
Look under settings/battery or power saver and uncheck fastboot?
Then you can actually get into hboot.
AFAIK, adb commands work in android, fastboot commands work in bootloader.
just make sure USB DEBUGGING is checked in settings.
When that happens to me, I remove the battery for about a minute, put it back in, hold down volume down, then hold power. It will boot right to bootloader.
Save the Drama for your Mama with Tapatalk 2
coal686 said:
When that happens to me, I remove the battery for about a minute, put it back in, hold down volume down, then hold power. It will boot right to bootloader.
Click to expand...
Click to collapse
This caused a lot of trouble for me trying to flash MeanRom and Tribulattifather's ICS OTA with 4EXT because it kept trying to go into bootloader after the install to do the "smart install" or whatever. The phone would just black out upon reboot and sit there or if I tried doing bootloader manually, it would go straight to recovery again. I was up until 4 in the morning trying to get my phone to fully boot last night...never did.
Brought my phone to work today and left it off nearly all day. I thought I was seriously screwed and would have to do a RUU update/unbrick from work. Lo and behold it went into bootloader first try.
I'm restoring a backup now through TWRP 2.2 (because it doesn't have the smart install feature). We'll see if
What do you think is causing these problems? I don't want anything crazy...just a solid ICS rom or rooted OTA. Most ROMs I read suggest using 4EXT to flash, but I'm afraid of running into this again. Any suggestions or thoughts?
as mentioned above, installed the TWRP 2.2 from bootloader and restored a backup (that worked a long time ago). Now i'm having the same issue I had last night. It won't boot up at all except to recovery again.
For most people, being s-off is the best thing to do. S-on and ICS tend to bootloop. For some reason, 4ext and flash image GUI don't seem to work well in ICS either for some.
Have you tried flashing a GB ROM?
Save the Drama for your Mama with Tapatalk 2
I'm going to have to figure out how to get back to complete stock. Everytime I flash a rom...doesn't matter what it is, the phone will say the flash is done, then reboot to...NOTHING...just a black screen. I've let it sit and nothing happens.
Followed a guide on androidcentral that had a nice restore to stock guide. Did the RUU from my computer and now it's acting normal again. It must've been really messed up because when I had it talking to ADB and did the reboot reloader command (as someone stated), the screen was solid black, though the RUU still saw it.
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 read most of the unrooting issues and am very confused. I am new to rooting and oh so very green.
I tried to root my phone and ran into a problem. I manged to unlock but did not get access to SU. That is not even the issue anymore. I want to return the phone to lock. I assume I did not root since I do not have SU and all the root app said I do not have root access. I was weary of doing it in the first place and not I just want to go back. Not worth it for me. So I guess I need to know..
1 - How to lock it back. It has the "Tampered" "Unlocked" message when I boot to hboot (hope I am using the right terms).
2- I dont think I need to "unroot" cause I was not rooted in the first place and I did not of course add any ROMS.
I have read a lot of info but am a little intimidated but I do have pc skills so I am not TOTALLY dumb. Just dumb to rooting.
I guess I am stuck in limbo with the rooting issues and just want my phone back to norm. It's because I have now seen little stupid things going on with it. Like my volume keeps resetting itself from vibrate. I put it on vibrate and it goes into low loud volume by itself. Something in the root I guess.
Please Help...
Thanks!
BTW I am on ICS.
The only way to remove the "Tampered" would be to flash an RUU. But you have to have your boot loader relocked.
So, relock your boot loader, and then run the latest RUU.
Do you have a link for unrooting and relocking sprint galaxy s3? Please and Thank you
Sent from my GT-I9300 using xda app-developers app
corijs said:
Do you have a link for unrooting and relocking sprint galaxy s3? Please and Thank you
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Sprint GS3 Q&A section:
http://forum.xda-developers.com/forumdisplay.php?f=1715
GrayTheWolf said:
The only way to remove the "Tampered" would be to flash an RUU. But you have to have your boot loader relocked.
So, relock your boot loader, and then run the latest RUU.
Click to expand...
Click to collapse
Ok Thanks Graywolf... but I have a couple of questions. From what I have been reading:
1- How do I "relock" the phone. Also I have heard relocking may cause it to brick? I am still "s-on".
2- Will flashing the RUU cause it to brick? I understand through various forums that if I flash the wrong ruu and go back to before my ICS update i cannot get the ics update. Is there a way to flash to the ICS update we received last summer?
3 - Will doing all of this fix the little problems I now have? Like I stated above.. my "vibrate setting do not stay on vibrate. I think if I let the phone screen time out itself (without pushing the power button) when I wake it back up it's on low volume instead of vibrate. If I push the power button to make it sleep, it tends to stay on vibrate. ALSO I now notice that if my wifi is on for instance at home and I leave the house it used to automatically go to 4g. now my radio stays off and i have to turn it on in the settings.
I guess in a nut shell.. if reverting it back will brick it, then I will have to put up with these bugs until I get another later on this year... probably in Oct.
Let me know and thanks alot for your help.:good:
Also...
Will Hasoon's all in one kit fix it?
Anyone? Gray?
Sorry for not replying. Tapatalk has been unsubscribing me from threads and I have to manually go find them.
I will be home in a bit, I will get you links and stuff then.
Ok thanks sir... I do appreciate your help.
Sent from my HTC Rezound using Tapatalk 2
mrnyc01 said:
Ok Thanks Graywolf... but I have a couple of questions. From what I have been reading:
1- How do I "relock" the phone. Also I have heard relocking may cause it to brick? I am still "s-on".
2- Will flashing the RUU cause it to brick? I understand through various forums that if I flash the wrong ruu and go back to before my ICS update i cannot get the ics update. Is there a way to flash to the ICS update we received last summer?
3 - Will doing all of this fix the little problems I now have? Like I stated above.. my "vibrate setting do not stay on vibrate. I think if I let the phone screen time out itself (without pushing the power button) when I wake it back up it's on low volume instead of vibrate. If I push the power button to make it sleep, it tends to stay on vibrate. ALSO I now notice that if my wifi is on for instance at home and I leave the house it used to automatically go to 4g. now my radio stays off and i have to turn it on in the settings.
I guess in a nut shell.. if reverting it back will brick it, then I will have to put up with these bugs until I get another later on this year... probably in Oct.
Let me know and thanks alot for your help.:good:
Click to expand...
Click to collapse
First, BACKUP ANYTHING IMPORTANT!
1. To relock the bootloader just reboot to hboot, and select "fastboot". Plug it in to your computer and (I assume you know how you unlocked it with fastboot commands) type into command prompt "fastboot oem lock".
2. The RUU will not flash unless your bootloader is relocked. So do step 1 first and then flash the OTA from this website.
3. An RUU will return your phone to the factory state. This should fix many problems that you may have.
RUU should fix things, and if it doesn't, then you know it is a hardware issue.
GrayTheWolf said:
First, BACKUP ANYTHING IMPORTANT!
1. To relock the bootloader just reboot to hboot, and select "fastboot". Plug it in to your computer and (I assume you know how you unlocked it with fastboot commands) type into command prompt "fastboot oem lock".
2. The RUU will not flash unless your bootloader is relocked. So do step 1 first and then flash the OTA from this website.
3. An RUU will return your phone to the factory state. This should fix many problems that you may have.
RUU should fix things, and if it doesn't, then you know it is a hardware issue.
Click to expand...
Click to collapse
Very helpful thanks sir.
Last question...the fastboot oem file should already be in that folder on my pc?
mrnyc01 said:
Very helpful thanks sir.
Last question...the fastboot oem file should already be in that folder on my pc?
Click to expand...
Click to collapse
fastboot oem lock is not a file, it is a command.
Ok gotcha thanks. It just seemed I remember reading I had to download a file to that folder and then type the fast boot oem command. I will do it this weekend and report back how it went. Thanks!
Sent from my HTC Rezound using Tapatalk 2
GrayTheWolf said:
fastboot oem lock is not a file, it is a command.
Click to expand...
Click to collapse
Hey Gray... ok I was able to relock... however flashing to the RUU from the link you sent.. it didn't work. After I loaded the zip file onto the SD card.. it does nothing when I boot to bootloader... reads zip and comes back and says no image.
The question I have it since I never loaded a ROM or another RUU can I just wipe it from inside the menu and start from start?
mrnyc01 said:
Hey Gray... ok I was able to relock... however flashing to the RUU from the link you sent.. it didn't work. After I loaded the zip file onto the SD card.. it does nothing when I boot to bootloader... reads zip and comes back and says no image.
The question I have it since I never loaded a ROM or another RUU can I just wipe it from inside the menu and start from start?
Click to expand...
Click to collapse
Meant to quote, not thank.
Anyway, you could do a factory reset.
GrayTheWolf said:
Meant to quote, not thank.
Anyway, you could do a factory reset.
Click to expand...
Click to collapse
Well now that doesnt work. When I try to hard reset the message comes up that it is reseting.. then boots to hboot. It wont factory reset. I tried factory resetting from hboot and it does nothing.
The PH98IMG is not on my sd card... I actually took it out.
Can you reset from a command prompt? Hopefully that will work.
mrnyc01 said:
Well now that doesnt work. When I try to hard reset the message comes up that it is reseting.. then boots to hboot. It wont factory reset. I tried factory resetting from hboot and it does nothing.
The PH98IMG is not on my sd card... I actually took it out.
Can you reset from a command prompt? Hopefully that will work.
Click to expand...
Click to collapse
No.
Is your bootloader relocked?
Yes from hboot i have the "tampered relocked" message but it does say relocked. What command do you use to reset?
Sent from my HTC Rezound using Tapatalk 2
mrnyc01 said:
Yes from hboot i have the "tampered relocked" message but it does say relocked. What command do you use to reset?
Sent from my HTC Rezound using Tapatalk 2
Click to expand...
Click to collapse
You either have to flash an RUU or factory reset.
Try this RUU:
http://shipped-roms.com/download.ph....0424r_3622A_MR3_9K_release_270509_signed.exe
GrayTheWolf said:
You either have to flash an RUU or factory reset.
Try this RUU:
http://shipped-roms.com/download.ph....0424r_3622A_MR3_9K_release_270509_signed.exe
Click to expand...
Click to collapse
Ok and since this is an .exe file...do I do it the same way? Drop it on to the SD card? Do
i have to rename it? Actually I found that I just download it to computer and run it.. does it matter the location of the file?
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: