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:
Related
Okay, so I purchased the htc rezound on ebay, the guy has a very high seller rating. Anyway, he FAILED to mention that the phone was "rooted/flashed" or what ever. My problem is that I want ORIGINAL FACTORY rom that would be on the phone from Verizon. I see links about how to get other roms, but what if I want to get back the original? As soon as turned the phone on, it went to the bootloader screen. I figured how to just boot into the regular boot up, then during the boot up you see the htc logo, then the an animation that says "clean rom". How do I switch from that back to the regular verizon factory? (Sorry for the long message).
refuse2bstopped said:
Okay, so I purchased the htc rezound on ebay, the guy has a very high seller rating. Anyway, he FAILED to mention that the phone was "rooted/flashed" or what ever. My problem is that I want ORIGINAL FACTORY rom that would be on the phone from Verizon. I see links about how to get other roms, but what if I want to get back the original? As soon as turned the phone on, it went to the bootloader screen. I figured how to just boot into the regular boot up, then during the boot up you see the htc logo, then the an animation that says "clean rom". How do I switch from that back to the regular verizon factory? (Sorry for the long message).
Click to expand...
Click to collapse
do a search for the stock RUU and flash that from hboot, i think you will have to relock hboot though first. problem is your bootloader will now say "relocked" so i think the seller screwed you over if you wanted a virgin phone.
Check what version hboot is and post it here and we can help you from there
Sent from my ADR6425LVW using Tapatalk 2
http://forum.xda-developers.com/showthread.php?t=1425091
that thread may be of use too.
mighty_markus12 said:
do a search for the stock RUU and flash that from hboot, i think you will have to relock hboot though first. problem is your bootloader will now say "relocked" so i think the seller screwed you over if you wanted a virgin phone.
Click to expand...
Click to collapse
I don't really care if it's a "non virgin" phone, I can live with that, I just as long as I can A stock rom with the original factory verizon apps. I mean seriously, this rom doesn't even have the MUSIC PLAYER!!!! lol
refuse2bstopped said:
I don't really care if it's a "non virgin" phone, I can live with that, I just as long as I can A stock rom with the original factory verizon apps. I mean seriously, this rom doesn't even have the MUSIC PLAYER!!!! lol
Click to expand...
Click to collapse
yup you just relock the bootloader and flash the stock RUU. that link i posted should help you out. i may be wrong but i think you can even run the ice cream ruu and stay stock.
mighty_markus12 said:
yup you just relock the bootloader and flash the stock RUU. that link i posted should help you out. i may be wrong but i think you can even run the ice cream ruu and stay stock.
Click to expand...
Click to collapse
Okay, now how do I get to the "hboot" screen or what ever? I'm totally lost, but I'm sure I can get this done because years ago I use to flash WM roms almost every other day. lol
refuse2bstopped said:
Okay, now how do I get to the "hboot" screen or what ever? I'm totally lost, but I'm sure I can get this done because years ago I use to flash WM roms almost every other day. lol
Click to expand...
Click to collapse
did you relock the device? to get to hboot power the device off and press power+volume down.
mighty_markus12 said:
did you relock the device? to get to hboot power the device off and press power+volume down.
Click to expand...
Click to collapse
I try that but it keeps on doing nothing, then when I finally let go of the buttons it just boots up the phone
Soooo.....
Does the fact that holding "power + volume down" and it just stays at the off screen until I finally let go and then just boots up into it's regular boot up mean I'll have to somehow "re-root" the phone? (if that makes any sense)
Honestly the Rezound is much better without the stock rom.
Sent from my ICS'd Rezound
refuse2bstopped said:
Does the fact that holding "power + volume down" and it just stays at the off screen until I finally let go and then just boots up into it's regular boot up mean I'll have to somehow "re-root" the phone? (if that makes any sense)
Click to expand...
Click to collapse
Nope...pull the battery, put it back in, then hold power and volume down. Hold them until it boots into hboot. It sometimes takes 15 seconds for mine. From there you can check if you need to relock.
uToTMeH8 said:
Nope...pull the battery, put it back in, then hold power and volume down. Hold them until it boots into hboot. It sometimes takes 15 seconds for mine. From there you can check if you need to relock.
Click to expand...
Click to collapse
Okay that worked, at the top it says ****tampered with**** then under it says ****relocked**** and it says HBOOT-2.21.0000
Well I've been able to get into that boot loader screen, but the thing is, how do I get one of the stock roms installed at that point? Where can I find one that will ACTUALLY DOWNLOAD?!!! I'm using a MAC btw, so I can't use any methods that require a windows based computer
refuse2bstopped said:
Well I've been able to get into that boot loader screen, but the thing is, how do I get one of the stock roms installed at that point? Where can I find one that will ACTUALLY DOWNLOAD?!!! I'm using a MAC btw, so I can't use any methods that require a windows based computer
Click to expand...
Click to collapse
You are on leaked ics so find the ics ruu and run that and you should be good
Sent from my ADR6425LVW using XDA
Someone installed the latest leak with the new hboot on it, you can't return to a stock GB rom without adding an SD Card fix.
And what's an "sd card fix"? Does that mean I have to reformat the card or something, or is it just something I have to boot from the sd card rather than it being initiated from the computer?
mjones73 said:
Someone installed the latest leak with the new hboot on it, you can't return to a stock GB rom without adding an SD Card fix.
Click to expand...
Click to collapse
Do you mean actually reformat my sd card, or is there just something I can put on it and then get to it in boot loader mode?
werdna87 said:
You are on leaked ics so find the ics ruu and run that and you should be good
Sent from my ADR6425LVW using XDA
Click to expand...
Click to collapse
The thing is how do I "RUN" it? What's the process? I've downloaded here on here but I don't know what to do next, other than how to get into boot loader mode. However, it says "relocked" at the top and again, I'm not sure where to run the ruu from. I know I can't do it from the computer because it's a MAC and so far all instructions have seemingly been PC based.
A leaked ICS is a .exe file that runs on Windows, I doubt it'll work on a MAC.
With limited knowledge on how to flash a ROM, your best option is to find a friend that has a PC, download the RUU executable file, boot your phone to the boot loader, and then run the file you downloaded.
Remember that those are leaked images so not being official means there is no support, so it seems you need to run the .exe RUU, which means you'll need to find a PC.
So I decided I would finally S-Off my device today, having been too busy recently due to school and life. I got past the point where you do the wire trick and I thought all was going well, but then it said something along the lines of Error: Still Sober. I exited ControlBear and figured I would just try again. At first, it was stuck at the black Juopunutbear screen, and after trying to turn it off via the power button, I decided to pull the battery and turn it back on. When I did this, it just booted up into the bootloader. I searched the forum and found it was possible to attempt it from the bootloader, so I did. It appeared to be working fine, but then my phone rebooted, and ControlBear just said "Connecting to device..." for a while, then said "Connect device and install drivers." Now, my phone only boots into bootloader, my laptop doesn't recognize that it's plugged in (though it will say fastboot USB on the phone), and ControlBear just tells me to "Connect device and install drivers." I don't know where to go from here. Help? Has anyone else had this issue?
Never mind that problem! I rebooted my computer, then it detected my phone just fine. I got the wire trick this time, but now I'm stuck at a point where it keeps rebooting my phone into amonra and ControlBear doesn't detect it?
and again...nevermind! simply powered down, then powered back up, and all was well. What's weird, though, is that it didn't wipe my SD card....all the information is still on it. I would think something went wrong, but when I go to my bootloader, it says S-Off...oh well! Not about to complain about a functional SD card!
Sorry, just read your posts. I experienced each of the same problems along the way But with trying and trying, finally got it. Congrats and welcome to the s-off club!
pmterp said:
Sorry, just read your posts. I experienced each of the same problems along the way But with trying and trying, finally got it. Congrats and welcome to the s-off club!
Click to expand...
Click to collapse
Yeah, I was a little freaked out at first. But I figured, it still does something, so at least I'm not bricked! haha. Thanks! It's good to be part of the club!
i to am stuck in the bootloader. i f-ed my phone up so i decided to relock and run the ruu and that failed.now it says relocked security warning none of my computers see my rezound, adb wont see it ether. i have tried a lot of stuff but no go.
anyone have any advice?
neckbonest said:
i to am stuck in the bootloader. i f-ed my phone up so i decided to relock and run the ruu and that failed.now it says relocked security warning none of my computers see my rezound, adb wont see it ether. i have tried a lot of stuff but no go.
anyone have any advice?
Click to expand...
Click to collapse
When you say it failed. What was the nature of the failure? What did the screen say?
Did you rename the RUU to PH98IMG? Hopefully you have a card reader. Take the SD card out and make sure the RUU is renamed properly. Put it back into your phone and reboot. When the phone goes into HBOOT does it look for and find the card? It should find the PH98IMG file for you to flash. Its been said that you should flash this twice.
topgun1953 said:
When you say it failed. What was the nature of the failure? What did the screen say?
Did you rename the RUU to PH98IMG? Hopefully you have a card reader. Take the SD card out and make sure the RUU is renamed properly. Put it back into your phone and reboot. When the phone goes into HBOOT does it look for and find the card? It should find the PH98IMG file for you to flash. Its been said that you should flash this twice.
Click to expand...
Click to collapse
i did rename it to ph98img and it found it but said checking ph98img and then nothing. i got it up and going anyway. i used the all in one toolkit and started from the beginning and did everything and it worked
I managed to get s-off, but my phone would not boot. I was stuck on a screen that said "JuopunutBear" with an arrow. I did the internal storage fix, now the phone is really screwed. I'm stuck on a white screen with "HTC". I can't boot to recovery and the PC won't recognize phone so ADB commands don't work. Any help would be appreciated.
lithium630 said:
I managed to get s-off, but my phone would not boot. I was stuck on a screen that said "JuopunutBear" with an arrow. I did the internal storage fix, now the phone is really screwed. I'm stuck on a white screen with "HTC". I can't boot to recovery and the PC won't recognize phone so ADB commands don't work. Any help would be appreciated.
Click to expand...
Click to collapse
Get one of the old GB RUU's and run it on your phone. Start again. If your phone was truly bricked, it wouldn't power on and you wouldn't get an LED light when it was plugged in.
lithium630 said:
I managed to get s-off, but my phone would not boot. I was stuck on a screen that said "JuopunutBear" with an arrow. I did the internal storage fix, now the phone is really screwed. I'm stuck on a white screen with "HTC". I can't boot to recovery and the PC won't recognize phone so ADB commands don't work. Any help would be appreciated.
Click to expand...
Click to collapse
This is an easy one, or would have been when you were on the black screen. Well the internal storage fix scares me, but hopefully that wont matter. Typically all you need to do is get the PH file from your rom and place on sd card, boot into hboot, and run the update I believe, then reboot.
This title needs to be edited as it's misleading.
lithium630 said:
I managed to get s-off, but my phone would not boot. I was stuck on a screen that said "JuopunutBear" with an arrow. I did the internal storage fix, now the phone is really screwed. I'm stuck on a white screen with "HTC". I can't boot to recovery and the PC won't recognize phone so ADB commands don't work. Any help would be appreciated.
Click to expand...
Click to collapse
Relax. The S-off process blows out your recovery. You didn't brick your phone.
Put a recovery image on your SD card, go into hboot (from a powered down state, power button and volume down) and let 'er reload recovery. If you can't get the file on your SD card through your phone, pop the SD card into a card reader attached to your PC and stick it on there that way.
Once that's done, remove the image file from your SD card, put your fav ROM on it, and install it from recovery.
You may need to fix your SD card's mount points. Within the thread on S-off, there's a link to the process.
None of the commands work because the phone is not recognized. I cannot boot to hboot. Uh oh.
I had the same screen. Pull the battery and reboot into hboot, volume down+power and run the s-off program again. Something didn't finish and it will pick up where it left off in my experience.
lithium630 said:
None of the commands work because the phone is not recognized. I cannot boot to hboot. Uh oh.
Click to expand...
Click to collapse
What happens when you press power+volume down?
Edit: Also, if you're phone turns on, you're not bricked. It's pretty hard to brick this phone.
tekhna said:
What happens when you press power+volume down?
Edit: Also, if you're phone turns on, you're not bricked. It's pretty hard to brick this phone.
Click to expand...
Click to collapse
Yeap just pull the battery and power on with power and volume down.
This kinda stuff you'll be fine with. Just don't get too creative with "repairs" that aren't posted in here.
tekhna said:
What happens when you press power+volume down?
Edit: Also, if you're phone turns on, you're not bricked. It's pretty hard to brick this phone.
Click to expand...
Click to collapse
As I understand it, the only way to brick a phone is to bork a radio installation.
Dude...pull your battery, put it back in, then power and volume down at the same time. If you can get to hboot, life is good.
After about 30 battery pulls I was able to get to hboot. I have no idea what the issue was. Finally got the phone booting now. I appreciate the replies.
lithium630 said:
After about 30 battery pulls I was able to get to hboot. I have no idea what the issue was. Finally got the phone booting now. I appreciate the replies.
Click to expand...
Click to collapse
Awesome, glad to hear. Did the s-off work?
tekhna said:
Awesome, glad to hear. Did the s-off work?
Click to expand...
Click to collapse
Sure did. Took me a little while to get the wire trick right. I just noticed the sd card is not recognized. I see the fix on the thread. That will be tomorrows project.
Constant reboots
I am able to install roms, but I get constant reboots, every few minutes at best. I tried a few different ICS ROMS. I am running the latest firmware. I BELIEVE with s-off I shouldn't have to flash PH98IMG.zip. I tried fixing permissions also but it has not helped.
How did you get the latest firmware and radios without running the PH98IMG.zip? The ics roms you are installing won't update your firmware.
Sent from my ADR6425LVW using Tapatalk 2
Chillerman said:
How did you get the latest firmware and radios without running the PH98IMG.zip? The ics roms you are installing won't update your firmware.
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
I relocked the phone and updated it a couple weeks ago. Maybe I need to try it again.
lithium630 said:
I relocked the phone and updated it a couple weeks ago. Maybe I need to try it again.
Click to expand...
Click to collapse
Well the newest leak came out 5/7 and the one before that 5/2 so only a week ago. I would download the newest from Android Police and follow the instructions they give to install, then flash a recovery and install a rooted Rom for this firmware like Scott's.
Sent from my ADR6425LVW using Tapatalk 2
lithium630 said:
I relocked the phone and updated it a couple weeks ago. Maybe I need to try it again.
Click to expand...
Click to collapse
I don't know why you relocked...I think there's a thread about not so good things happening to those who relock after S-off. I downloaded and installed the 5/5 leak as PH98IMG after I S-off'd and reflashed the recovery.
I'm pretty sure my hboot said "locked" straight out of the gate after I did the S-off deed.
douger1957 said:
I don't know why you relocked...I think there's a thread about not so good things happening to those who relock after S-off. I downloaded and installed the 5/5 leak as PH98IMG after I S-off'd and reflashed the recovery.
I'm pretty sure my hboot said "locked" straight out of the gate after I did the S-off deed.
Click to expand...
Click to collapse
Nothing bad happens, you just don't ever get back to "locked" without doing S-off again. You're just at "relocked" like the old days. S-on with an eng hboot on the other hand will brick your device.
That aside, there's no need to unlock if you're S-off. Either flash a patched hboot or just flash a PH98IMG.zip of AmonRa if you don't need fastboot commands (I did the latter).
I flashed the last firmware before S-off. I followed the instructions given. I flashed the latest firmware today and this damn thing still reboots constantly. I flashed the 5-7 firmware then the Venasaur Rom.
lithium630 said:
I flashed the last firmware before S-off. I followed the instructions given. I flashed the latest firmware today and this damn thing still reboots constantly. I flashed the 5-7 firmware then the Venasaur Rom.
Click to expand...
Click to collapse
You need to try installing the radio firmware or just install the complete RUU again. And install a clean copy of the rom, not a nandroid backup. Wipe data, cache, dalvic cache, and system before flashing the rom.
Send me a private message if you would like and I'll help you get it figured out on gtalk.
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.
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.