hell guys, I am trying to lock my bootloader completely and I have read the sticky of how to do it but every time i write the command: "fastboot oem writesecureflag 3" it says waiting for device. I then tried going into bootloader and then it says that its done but my bootloader is still relocked.
Please help me!
Thank you guys and have a great day
omiron said:
hell guys, I am trying to lock my bootloader completely and I have read the sticky of how to do it but every time i write the command: "fastboot oem writesecureflag 3" it says waiting for device. I then tried going into bootloader and then it says that its done but my bootloader is still relocked.
Please help me!
Thank you guys and have a great day
Click to expand...
Click to collapse
I just did it the other day and btw there are posts about this but u have asked so here it is.
Use a different usb port. Use a usb2.0 port if possible, 3.0 has problems with htc one.
Be in the fastboot menu and then let it work. Try again if unsuccessful.
Uninstall drivers for your device and reinstall them.
BTW did u restart your phone after locking so that is shows its locked. or did you read the line after it tried to lock it.
RaXxaa said:
I just did it the other day and btw there are posts about this but u have asked so here it is.
Use a different usb port. Use a usb2.0 port if possible, 3.0 has problems with htc one.
Be in the fastboot menu and then let it work. Try again if unsuccessful.
Uninstall drivers for your device and reinstall them.
BTW did u restart your phone after locking so that is shows its locked. or did you read the line after it tried to lock it.
Click to expand...
Click to collapse
I tried using usb 2.0 but no success. I'll try again and let you know if I can get it to work. Thanks though!
Let's begin from the start... What method did u use to unlock??
Sent from my HTC One using xda premium
Will-Survive said:
Let's begin from the start... What method did u use to unlock??
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Nevermind, I found how to do it. What I did is followed the step on this website: http://forum.xda-developers.com/showthread.php?t=2314582 to Lock my bootloader but to have it on S-off. Then I followed the steps on this website: http://forum.xda-developers.com/showthread.php?t=2358738 so I could S-on my bootloader. Now I am running stock sense 5 with bootloader locked and s-on! Thanks for trying to help me though
Related
( i admit i am a noob at this stuff) I bought this rezound from a guy, and i came home and downloaded the Rezound All-In-One kit, i installed the htc drivers registered at htcdev. I tried to get token ID.. didnt work, and i tried to do the ICS leak and followed the instructions exactly... didnt work.. well i looked at my phone while in bootloader and it said unlocked, i tried running the All-in-one kit "Relock Bootloader" command and it still doesnt work. in command prompt it says ( Rezound_All-In-One_Kit_v2.0\data>fastboot oem lock
< waiting for device >
and thats it.. doesnt do anything else.. can someone please help me re-lock this phone.
First, try doing the above again, only uninstall/disable HTC sync this time. Report back if it doesn't work. Also, why do you wish to relock?
rabidwookie said:
( i admit i am a noob at this stuff) I bought this rezound from a guy, and i came home and downloaded the Rezound All-In-One kit, i installed the htc drivers registered at htcdev. I tried to get token ID.. didnt work, and i tried to do the ICS leak and followed the instructions exactly... didnt work.. well i looked at my phone while in bootloader and it said unlocked, i tried running the All-in-one kit "Relock Bootloader" command and it still doesnt work. in command prompt it says ( Rezound_All-In-One_Kit_v2.0\data>fastboot oem lock
< waiting for device >
and thats it.. doesnt do anything else.. can someone please help me re-lock this phone.
Click to expand...
Click to collapse
Is your phone in HBOOT when you issue the command? If not, it should be. Fastboot commands only work in HBOOT.
Snuzzo said:
First, try doing the above again, only uninstall/disable HTC sync this time. Report back if it doesn't work. Also, why do you wish to relock?
Click to expand...
Click to collapse
MrSmith317 said:
Is your phone in HBOOT when you issue the command? If not, it should be. Fastboot commands only work in HBOOT.
Click to expand...
Click to collapse
Yeah you're right MrSmith. I looked at the .bat related to re-locking in the A-I-O toolkit and it doesn't invoke "adb reboot bootloader" command before attempting "fasboot oem lock".
I ran into this problem as well. Make sure usb debugging is on. Should work like a charm.
Sent from my ADR6425LVW using xda premium
Fergusonfox7 said:
I ran into this problem as well. Make sure usb debugging is on. Should work like a charm.
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
Again, its not a matter of having debugging enabled. See my post above.
Sent from my ADR6425LVW using XDA
Try rebooting into HBOOT then unplugging the phone and plugging it back in. Sometimes the device manager(on your PC) doesn't pickup the change in modes. The AIO could just be firing off commands instead of waiting for the phone to be ready as well. Try doing it manually.
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!!!
please delete
chazking said:
Did a boo boo and flashed a recovery to kernel got the phone back to working again just not working the right way cannot relock bootloader as when i try to it will just go into a reboot mode and just reboot into bootloader everytime tried flashing ruu will not take as i did the over the air and have those radios and bootloader tried doing ota and that will not go through either please help if you can am lost been trying for 5 days to get this fixed and just can't thank you for your help in advance
Click to expand...
Click to collapse
Dude, thats like the longest run on sentence I have seen in a LONG time. Can you slow down a bit add a few periods for us? Are you S-ON or S-OFF.
please delete
chazking said:
sorry hate typing i am s-on
Click to expand...
Click to collapse
to relock the bootloader just type this in when you are in the bootloader screen where it says fastboot usb
Code:
fastboot oem lock
then you can run the RUU then after the RUU is done flash you Unlock_code.bin and it will re-unlock the bootloader then you can take the OTA
please delete
chazking said:
won't work already tried that as i did over the air wont run ruu and bootloader will not relock as explained above thanks for the reply though
Click to expand...
Click to collapse
Well considering I couldn't understand half of the op because of how run on it was...
Sent from my HTC6435LVW using xda app-developers app
chazking said:
won't work already tried that as i did over the air wont run ruu and bootloader will not relock as explained above thanks for the reply though
Click to expand...
Click to collapse
the bootloader should still lock regardless of if you took the ota
please delete
please delete
It was ok man just giving ya a hard time. English is my one and only language and I suck at it so.. hope you get things working..
Not pointed at you zone23, you were trying to help
hey guys/gals, let me start off by saying that i knew better but as always i screwed up by letting my add get the best of me! i relocked bootloader to RUU to stock . problem is that i didnt load the correct splash1 first! now when i try to flash anything i get the signature error. im hoping that a work-around is available. i tried the htcdev but get an error 160 MID not allowed. tried the toolkit(s) available, NO ADB!!! soooo here i am hoping that you guys might have experienced a moment of dumbness as i did....i get a multitude of errors when trying to flash stuff (error 12 sig failure,wrong main version error)...was unlocked and rooted per rumrunner (THANKS BEAUPS!!!!!) prior to my screw up... heres what i have
s-on
hboot-1.33.0001
radio-1.01.1112
baseband-1.01.01.1112
version main-3.06.605.4
cid-VZW_001
bootloader-041a62aa
(lmk if any further info is needed)
like i stated before , i know i needed to flash splash1 BEFORE locking bootloader but in my defense i had my 11 week old son in my arms (multitasking FAIL) , so if you guys have ANY suggestion please feel free to lmk...THANKS IN ADVANCE as this is a new problem for me!
and btw, i spent yesterday sifting through threads to try to solve this ,to no avail....i didnt want to tie you guys up prematurely
i did try to re run rumrunner and moonshine (even though i knew moonshine wouldnt work) but as i said , i have no adb and usb debugging s questionable, although i can use fastboot to rebootRUU
stephenculkin6277 said:
i did try to re run rumrunner and moonshine (even though i knew moonshine wouldnt work) but as i said , i have no adb and usb debugging s questionable, although i can use fastboot to rebootRUU
Click to expand...
Click to collapse
Try this, access to fastboot first then connect usb to pc
http://forum.xda-developers.com/showpost.php?p=48680578&postcount=44
i get the error:remote not allowed....I had those files downloaded yesterday
i just tried in the rebootRUU status (blask screen with HTC logo and got error 43 main versio check fail?
i got firmware2 to run (both times) ... do i need to try to reset to stock from bootloader now?
or is the 2nd one no good without the 1st? im sorry , i just dont want to screw up anymore than i already have ya know
stephenculkin6277 said:
or is the 2nd one no good without the 1st? im sorry , i just dont want to screw up anymore than i already have ya know
Click to expand...
Click to collapse
Reboot bootloader, the second firmware is the new Hboot 1.54.0000 need it to run the new Ruu. hope it help
after reboot bootloader confirm that your hboot is the new. so you can go ahead with the ruu
k thanks, but I think the problem im having running the RUU is the image...whatever that is, I think the splash1 I forgot to load...I will try running the jb_50 RUU now though , thanks
finanandroid said:
Try this, access to fastboot first then connect usb to pc
http://forum.xda-developers.com/showpost.php?p=48680578&postcount=44
Click to expand...
Click to collapse
finanandroid said:
Reboot bootloader, the second firmware is the new Hboot 1.54.0000 need it to run the new Ruu. hope it help
after reboot bootloader confirm that your hboot is the new. so you can go ahead with the ruu
Click to expand...
Click to collapse
sorry , I spoke too soon...I just finished running RUU and you have solved the mystery!!! much gracias my friend!!! I cant thank you enough!!!
stephenculkin6277 said:
sorry , I spoke too soon...I just finished running RUU and you have solved the mystery!!! much gracias my friend!!! I cant thank you enough!!!
Click to expand...
Click to collapse
You're welcome! glad that you can back on business. :victory:
Instructions clearly said the splash image was only for custom splash images. It is not a necessary step.
Sent from my DLX using xda app-developers app
See that's the thing, I was running pro bam which had a non stock splash img so I assumed I had to, my bad
You may need to reinstall adb?
thayl0 said:
You may need to reinstall adb?
Click to expand...
Click to collapse
Yeah, I did as a precaution.... The firmware2 file let me run RUU after I flashed it... I still can't believe I made such a bone head mistake! Now I just wish I could get my Bootloader unlock token for future screw ups lol But I just get error 160 MID not allowed when I try, At least rumrunner worked for me!
stephenculkin6277 said:
Yeah, I did as a precaution.... The firmware2 file let me run RUU after I flashed it... I still can't believe I made such a bone head mistake! Now I just wish I could get my Bootloader unlock token for future screw ups lol But I just get error 160 MID not allowed when I try, At least rumrunner worked for me!
Click to expand...
Click to collapse
You can no longer do that any more.
That sucks donkey balls!
If you're s-off you can set cid to 22222222 and get an unlock token at htcdev
Thank you sir! I now have the token I have been needing!
Sent from my HTC6435LVW using xda app-developers app
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.