so I relocked my bootloader with the "adb oem relock" command. is there an easy way to unlock it again now that it says "relocked"? some easy adb command that will unlock it again? or do I have to do the whole moonshine thing again?
welbinator said:
so I relocked my bootloader with the "adb oem relock" command. is there an easy way to unlock it again now that it says "relocked"? some easy adb command that will unlock it again? or do I have to do the whole moonshine thing again?
Click to expand...
Click to collapse
If
Code:
fastboot oem unlock
doesn't work, (which I do not believe it will) you will need to moonshine again.
Ya u half to do moonshine about because I changed my hbiit version and it relocked my phone with tampered..
Sent from my dlx using XDA Premium 4 mobile app
Of you have a custom recovery, just use the lock/unlock bootloader zips Scotty shared with us. I discussed this before. It works like a charm.
Sent from my DNA using my mind.
Uzephi said:
Of you have a custom recovery, just use the lock/unlock bootloader zips Scotty shared with us. I discussed this before. It works like a charm.
Sent from my DNA using my mind.
Click to expand...
Click to collapse
where can i find this files?
Related
So I couldn't get soff no matter what I did so iwanted to start fresh and relocked my bootloader and made it stock with an exe ruu. Now I can't unlock my bootloader again. Can anyone please help me.
raytraceme said:
So I couldn't get soff no matter what I did so iwanted to start fresh and relocked my bootloader and made it stock with an exe ruu. Now I can't unlock my bootloader again. Can anyone please help me.
Click to expand...
Click to collapse
keep trying to flash your token (maybe use a different usb port) make sure that the file is in the right location so fastboot can access it and its case sensitive and remember it might take several tries
Code:
fastboot flash unlocktoken Unlock_code.bin
thanks but I found an easier way. http://rootzwiki.com/topic/36898-stock-return-to-stock-1156054-for-verizon-htc-dna-re-unlock-device/
raytraceme said:
thanks but I found an easier way. http://rootzwiki.com/topic/36898-stock-return-to-stock-1156054-for-verizon-htc-dna-re-unlock-device/
Click to expand...
Click to collapse
You are still going to have to unlock your boot loader after the ruu which requires flashing then token just like I said in my last post
Sent from my Nexus 7 using XDA Premium HD app
oh yea i got that I used hasoon's dna tool and got everything done. Thanks for the help!!!
Okay so I used the SuperCID apk and it converted my CID to a bunch of Twos and then I used the HTC unlock method to unlock my phone. But after I select root my phone I'll void the warranty it boots into Android mode where I reboot it into recovery it says locked. It doesn't say relocked or unlocked it simply says locked like it never unlocked my phone even though it had just said it unlocked it maybe 2 minutes prior. Has anyone else had this problem? How do I fix it?
Can you try to explain what's happening a little bit better.
Sent from my HTC6435LVW using xda app-developers app
Did you flash the unlock_code.bin file?
Bigandrewgold said:
Can you try to explain what's happening a little bit better.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Okay so I ran the SuperCID from http://forum.xda-developers.com/showthread.php?p=36976137 and it changed my CID to 22222222.
I then do "fastboot flash unlocktoken Unlock_code.bin" that I got from HTC and then select Yes on the prompt.
It then boots into normal android mode and then it goes through the normal setup. I then enable the debuging mode and then do
"adb reboot-bootloader" it then reboots into bootloder locked.
Balask said:
Okay so I ran the SuperCID from http://forum.xda-developers.com/showthread.php?p=36976137 and it changed my CID to 22222222.
I then do "fastboot flash unlocktoken Unlock_code.bin" that I got from HTC and then select Yes on the prompt.
It then boots into normal android mode and then it goes through the normal setup. I then enable the debuging mode and then do
"adb reboot-bootloader" it then reboots into bootloder locked.
Click to expand...
Click to collapse
Is there a way for you to take a video of when you send the unlock token and click yes on your phone. Because I'm really not sure what's going wrong.
Sent from my HTC6435LVW using xda app-developers app
Balask said:
Okay so I ran the SuperCID from http://forum.xda-developers.com/showthread.php?p=36976137 and it changed my CID to 22222222.
I then do "fastboot flash unlocktoken Unlock_code.bin" that I got from HTC and then select Yes on the prompt.
It then boots into normal android mode and then it goes through the normal setup. I then enable the debuging mode and then do
"adb reboot-bootloader" it then reboots into bootloder locked.
Click to expand...
Click to collapse
Keep flashing it until it unlocks sometimes it takes 20 times
.torrented said:
Keep flashing it until it unlocks sometimes it takes 20 times
Click to expand...
Click to collapse
I've only heard of it taking multiple times if your trying to re unlock, not on the first unlock.
Sent from my HTC6435LVW using xda app-developers app
Bigandrewgold said:
I've only heard of it taking multiple times if your trying to re unlock, not on the first unlock.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
sccrgoalie1 said:
Worked for me as well but it seriously took 15 to 20 tries to reunlock. Thanks!
Click to expand...
Click to collapse
Just keep trying... some people get it first try other dont...
If you do a factory reset first from bootloader then unlock, it will work first time every time.......it'll wipe your SD tho. Once you have a custom recovery flashed don't use that method anymore tho
Sent from my SPH-L710 using Tapatalk 2
For me. I had to turn phone completely off. Then boot into HBOOT/Fastboot in order for the unlock to work. Make sure fast boot is unchecked in the power options before turning off.
In about three minutes this video should show a HTC DNA not unlocking even with SuperCID change and the correct file to unlock the phone with.
Code:
youtu.be/6P7mQ0rP-ms
Just keep at the command. Keep redoing it until it sticks. Took me 5 tries. Now I'm S-OFF & unlocked...with the OTA. Just keep doing it. It'll stick...eventually.
AW: [Q] Hboot won't unlock
Flyhalf205 said:
For me. I had to turn phone completely off. Then boot into HBOOT/Fastboot in order for the unlock to work. Make sure fast boot is unchecked in the power options before turning off.
Click to expand...
Click to collapse
Yep,same Problem,Power Completely off and it works for me.
Sent from my HTC6435LVW using xda app-developers app
Thanks a lot turning it completely off actually did the trick. Now my next question is since I had to put on a custom recovery to install Super User now do I install a stock recovery so that it can do over the air updates now that I have S-Off. If it updates my stock rom with OTA will I have to flash a custom rom to root it again or will SU still be there because its S-Off?
Balask said:
Thanks a lot turning it completely off actually did the trick. Now my next question is since I had to put on a custom recovery to install Super User now do I install a stock recovery so that it can do over the air updates now that I have S-Off. If it updates my stock rom with OTA will I have to flash a custom rom to root it again or will SU still be there because its S-Off?
Click to expand...
Click to collapse
I'm not sure why'd you want to take the ota, but yes, you'll need the stock recovery if you want to take it. Then you'll need to install a custom recovery and install a superuser package.
Having s off has nothing to do with superuser or the ota.
Sent from my GT-P7510 using xda app-developers app
Team,
I've searched and tried to relock the bootloader with fastboot oem lock on my MAC and windows through the command prompt and the command is not recognized. I need to reset this damn DNA tonight before I send it back in to Verizon. Please give me a little assistance here. I have the RUU on my desktop also, I just dont know wtf is wrong with the command fastboot oem lock...
Yes I am restarting and chosing fastboot with the phone plugged in..
OverrideJones said:
Team,
I've searched and tried to relock the bootloader with fastboot oem lock on my MAC and windows through the command prompt and the command is not recognized. I need to reset this damn DNA tonight before I send it back in to Verizon. Please give me a little assistance here. I have the RUU on my desktop also, I just dont know wtf is wrong with the command fastboot oem lock...
Yes I am restarting and chosing fastboot with the phone plugged in..
Click to expand...
Click to collapse
Any love?
OverrideJones said:
Any love?
Click to expand...
Click to collapse
there is a thread in the dna android deveolpement forum that has all the info u need.
mopartonyg said:
there is a thread in the dna android deveolpement forum that has all the info u need.
Click to expand...
Click to collapse
There are many threads that I have read through...
when I fastbooted and so forth... I typed in the command box fastboot oem lock and that did nothing.
From what I read, you need to flash the lock boot loader zip to lock it.. Fastboot oem lock command won't work apparently if you have S-offed.
Sent from my DNA
Uzephi said:
From what I read, you need to flash the lock boot loader zip to lock it.. Fastboot oem lock command won't work apparently if you have S-offed.
Sent from my DNA
Click to expand...
Click to collapse
Thanks a lot and where is the lockbootloader zip located at along with the other files?
OverrideJones said:
There are many threads that I have read through...
when I fastbooted and so forth... I typed in the command box fastboot oem lock and that did nothing.
Click to expand...
Click to collapse
Read through this entire guide before you start any of them to make sure you follow the proper one.
http://forum.xda-developers.com/showthread.php?t=2293919
Sent from my dlx using XDA Premium HD app
.torrented said:
Read through this entire guide before you start any of them to make sure you follow the proper one.
http://forum.xda-developers.com/showthread.php?t=2293919
Sent from my dlx using XDA Premium HD app
Click to expand...
Click to collapse
Read this...
what does this mean?
Copy the "lock bootloader zip" onto root of internal storage and flash in recovery of your choice
Whos internal storage? SD card on the phone?
OverrideJones said:
Read this...
what does this mean?
Copy the "lock bootloader zip" onto root of internal storage and flash in recovery of your choice
Whos internal storage? SD card on the phone?
Click to expand...
Click to collapse
Yes. Flash it in a custom recovery
Sent from my Rezound
Uzephi said:
Yes. Flash it in a custom recovery
Sent from my Rezound
Click to expand...
Click to collapse
Are there any places around maryland or northern va who can assist...? I would love to learn the terminology but it took me 4 days to learn how to code on a MAC to perform the dang root lol and not I cant image how long it would take to reverse it.
Uzephi said:
Yes. Flash it in a custom recovery
Sent from my Rezound
Click to expand...
Click to collapse
Which process did u use to achieve s-off and unlock?
Sent from my dlx using xda app-developers app
jaymazz13 said:
Which process did u use to achieve s-off and unlock?
Sent from my dlx using xda app-developers app
Click to expand...
Click to collapse
Mine got given to me s-off.
Sent from my Rezound
What does your hboot say when you boot into bootloader?
Phaded said:
What does your hboot say when you boot into bootloader?
Click to expand...
Click to collapse
It says S-OFF unlocked ...
I do not know the process... I need to be walked through it to be fair. Not to sound incompetent lol
Uzephi said:
Yes. Flash it in a custom recovery
Sent from my Rezound
Click to expand...
Click to collapse
Also, I am using clockwork mod...
What does the ENTIRE thing say?
Phaded said:
What does the ENTIRE thing say?
Click to expand...
Click to collapse
No worries now guys, I suppose now I have to give Verizon a damn good reason as to why my phone was rooted as hell. I have a decent alibi created.
Flash the lock boot loader zip as you would if flashing a ROM.
After that, do the RUU instructions, then s-on (fastboot OEM write secure flag 3). It is pretty simple.
Sent from my Rezound
Uzephi said:
Flash the lock boot loader zip as you would if flashing a ROM.
After that, do the RUU instructions, then s-on (fastboot OEM write secure flag 3). It is pretty simple.
Sent from my Rezound
Click to expand...
Click to collapse
Phone is gone now, however, what I did was...
restart phone, hold down volume blah...
boot loader fast boot and so forth, when fastboot USB popped up on phone on the windows computer open command up and type fastboot oem lock
some sort of error popped up.. so that is where I was. Pardon the english and grammar, had a few Jamesons'
OverrideJones said:
Phone is gone now, however, what I did was...
restart phone, hold down volume blah...
boot loader fast boot and so forth, when fastboot USB popped up on phone on the windows computer open command up and type fastboot oem lock
some sort of error popped up.. so that is where I was. Pardon the english and grammar, had a few Jamesons'
Click to expand...
Click to collapse
You can't lock the boot loader by fastboot commands, you needed to lock it by flashing the lock zip in recovery.
Sent from my Rezound
Hello all, I've just recently recovered my DNA back to stock from a botched ROM install on the 3.06 software. Prior to running the RUU, I used Rumrunner to unlock my bootloader to put CWM on as my recovery. Then I had to re-lock it to run the RUU. Now I'm stuck at re-unlocking it. The HTCdev site is giving me a MID not allowed error and I'm thinking it has something to do with the fact that I used Rumrunner? Call me stupid, the DNA is still relatively new to me. Thank you!!
You shouldn't need to relock it to RUU. The RUU will overwrite your recovery with stock but the bootloader should remain unlocked (and s-off if you did that as well). At this point you should be able to just run rumrunner again to unlock the bootloader and then you can flash a custom recovery and go from there.
Sent from my HTC6435LVW using xda app-developers app
iissmart said:
You shouldn't need to relock it to RUU. The RUU will overwrite your recovery with stock but the bootloader should remain unlocked (and s-off if you did that as well). At this point you should be able to just run rumrunner again to unlock the bootloader and then you can flash a custom recovery and go from there.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Tried doing Rumrunner again, Getting this error, "ERROR: run rumrunner again and READ (no adb connection to device. Debugging on?
Drivers?)" I've uninstalled the drivers via device manager, let windows 7 reinstall them and installed/uninstalled HTCsync with no luck.
Edit: Nevermind, tried a different cable. Hate it when that happens.
Edit 2: Rumrunner must have failed, device still relocked.
Hubblemuffin said:
Tried doing Rumrunner again, Getting this error, "ERROR: run rumrunner again and READ (no adb connection to device. Debugging on?
Drivers?)" I've uninstalled the drivers via device manager, let windows 7 reinstall them and installed/uninstalled HTCsync with no luck.
Click to expand...
Click to collapse
Does 'adb devices' show your serial number? Did you enable debugging in the developer options?
iissmart said:
Does 'adb devices' show your serial number? Did you enable debugging in the developer options?
Click to expand...
Click to collapse
I don't even see ADB devices in device manager. Just Android USB Devices.
Hubblemuffin said:
I don't even see ADB devices in device manager. Just Android USB Devices.
Click to expand...
Click to collapse
ADB Devices is a command issued from the command prompt. It should return the S/N of the device connected. If there is no response the drivers are not installed on the PC. If you are using Win 8 or 8.1 you will have issues
RLGL said:
ADB Devices is a command issued from the command prompt. It should return the S/N of the device connected. If there is no response the drivers are not installed on the PC. If you are using Win 8 or 8.1 you will have issues
Click to expand...
Click to collapse
Not too familiar with running that command. I'm new to the whole HTC scene. My Note 2 was significantly easier to work with in this respect.
Hubblemuffin said:
Not too familiar with running that command. I'm new to the whole HTC scene. My Note 2 was significantly easier to work with in this respect.
Click to expand...
Click to collapse
Hı, have you find out a solution to this one ?
I am struggling with a similar situation:
http://forum.xda-developers.com/showthread.php?p=51140962
I did, sorry for not posting it here. I went and got a new cable from tiger direct and tried again. For some reason, the bootloader still says relocked but I have root access. I don't feel confident enough to try and see if CWM or TWRP and I don't want to go through the RUU garbage again. Shoot me a PM and I'll tell you everything what not to do. LOL
Sent from my HTC6435LVW using xda app-developers app
Hubblemuffin said:
I did, sorry for not posting it here. I went and got a new cable from tiger direct and tried again. For some reason, the bootloader still says relocked but I have root access. I don't feel confident enough to try and see if CWM or TWRP and I don't want to go through the RUU garbage again. Shoot me a PM and I'll tell you everything what not to do. LOL
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
I have heard if you flash a new hboot the relocked text will go away, but I haven't had this issue myself so I can't personally confirm it. I do recommend updating your hboot and radio, though, for other reasons like better radio signal.
iissmart said:
I have heard if you flash a new hboot the relocked text will go away, but I haven't had this issue myself so I can't personally confirm it. I do recommend updating your hboot and radio, though, for other reasons like better radio signal.
Click to expand...
Click to collapse
Updating the hboot and radio seems a little daunting. Definitely something I want to look in to once I can figure out how to get a ROM on this without calling a mulligan and starting from scratch again.
Hubblemuffin said:
Not too familiar with running that command. I'm new to the whole HTC scene. My Note 2 was significantly easier to work with in this respect.
Click to expand...
Click to collapse
Adb is universal to all android devices, I highly recommend getting used to it if you plan on rooting future devices, the only thing native to HTC is the S-OFF portion of eMMC
Hubblemuffin said:
I did, sorry for not posting it here. I went and got a new cable from tiger direct and tried again. For some reason, the bootloader still says relocked but I have root access. I don't feel confident enough to try and see if CWM or TWRP and I don't want to go through the RUU garbage again. Shoot me a PM and I'll tell you everything what not to do. LOL
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Are you S-OFF? If so issue this command in fastboot:
fastboot oem writecid 22222222
Go to htcdev.com and then it will allow you to unlock the bootloader also make sure you have 8 2's in the command.
Is there a unlock command I can run in cmd. Previsously been unlocked but not by HTCDEV!
thayl0 said:
Is there a unlock command I can run in cmd. Previsously been unlocked but not by HTCDEV!
Click to expand...
Click to collapse
I have the same issue.
I did fastboot oem lock so I could take the ota, now I cant re-unlock.
I was able to flash twrp through rebootRUU by packing it and signing it. If you need that, I can link it to you.
rjd584 said:
I was able to flash twrp through rebootRUU by packing it and signing it. If you need that, I can link it to you.
Click to expand...
Click to collapse
did you make TWRP flashable through RUU on 4.09.605.5 or earlier?
http://forum.xda-developers.com/showthread.php?p=46301380
Requires root and s-off. Works on the DNA...
Sent from my HTC6500LVWBLU using XDA Free mobile app