Hi,
I have bought a droid turbo 32GB red from ebay. It works, no problem. But I want to install custom rom.
So, the blue bootloader unlocked message is there when I start the phone. In fastboot mode device is locked, status code 2.
I have already used sunshine to unlock the bootloader again. Sunshine told me it was a success, but status code is always 2.
When I want to flash TWRP recovery via fastboot I get message (bootloader) preflash validation failed.
What can I do?
Thanks and greetings from germany.
Only one little tip, please.
Once a Droid Turbo XT1254 bootloader is unlocked, if the previous owner relocked it can not be unlocked again.
Status 2 means unlocked at one point and then relocked, yes?
I don`t know what it means...
It means someone unlocked it, relocked it, and now it cannot be unlocked again.
Polarisfff said:
Hi,
I have bought a droid turbo 32GB red from ebay. It works, no problem. But I want to install custom rom.
So, the blue bootloader unlocked message is there when I start the phone. In fastboot mode device is locked, status code 2.
I have already used sunshine to unlock the bootloader again. Sunshine told me it was a success, but status code is always 2.
When I want to flash TWRP recovery via fastboot I get message (bootloader) preflash validation failed.
What can I do?
Thanks and greetings from germany.
Click to expand...
Click to collapse
Try this I have never done it and have no idea how to the thred I grabbed this from is in this section of the forum under something like relocked bootloader bricked?? So if u need more guidance check that thread but here is the info.
Re Unlock
I did the same thing on my xt1254 this is what Beaups told me from sunshine and it worked for me. I did it from terminal emulated on the device and then was ablebto reflash twrp
Beaups (TheRootNinja Support)
Dec 29, 17:10
tested this on my device and it worked. Keep in mind we can't guarantee it will work for you and also can't guarantee it won't kill your device (but I don't see why it should). Copy paste this command, do NOT make any errors.
From a ROOT adb shell (if you don't have root you'll need to figure out how to get it, kingroot, etc):
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/sp bs=1 seek=8
It should hang for a few seconds and then you should see something like:
dd: /dev/block/platform/msm_sdcc.1/by-name/sp: No space left on device
1048569+0 records in
1048568+0 records out
1048568 bytes transferred in 7.203 secs (145573 bytes/sec)
At that point reboot to bootloader and hopefully your problem is solved. Do NOT relock that device again in the future.
--beaups
Grynch13 said:
Try this I have never done it and have no idea how to the thred I grabbed this from is in this section of the forum under something like relocked bootloader bricked?? So if u need more guidance check that thread but here is the info.
Re Unlock
I did the same thing on my xt1254 this is what Beaups told me from sunshine and it worked for me. I did it from terminal emulated on the device and then was ablebto reflash twrp
Beaups (TheRootNinja Support)
Dec 29, 17:10
tested this on my device and it worked. Keep in mind we can't guarantee it will work for you and also can't guarantee it won't kill your device (but I don't see why it should). Copy paste this command, do NOT make any errors.
From a ROOT adb shell (if you don't have root you'll need to figure out how to get it, kingroot, etc):
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/sp bs=1 seek=8
It should hang for a few seconds and then you should see something like:
dd: /dev/block/platform/msm_sdcc.1/by-name/sp: No space left on device
1048569+0 records in
1048568+0 records out
1048568 bytes transferred in 7.203 secs (145573 bytes/sec)
At that point reboot to bootloader and hopefully your problem is solved. Do NOT relock that device again in the future.
--beaups
Click to expand...
Click to collapse
Hi ok,
i will test this. Another Problem is actually that I didn`t get it rooted...
Polarisfff said:
Hi ok,
i will test this. Another Problem is actually that I didn`t get it rooted...
Click to expand...
Click to collapse
Makes sense, since your bootloader is still locked.
but "From a ROOT adb shell (if you don't have root you'll need to figure out how to get it, kingroot, etc)". So, kingroot rooted the device, but I get problems with closing apps etc...
So, I am sorry, but I dont not know how I get adb root access? Is it a terminal emulator which root king gave root access or is it a special ADB command when the phone is in fastboot mode? In fastboot mode there is also (Secure)...
puh! :-/
Polarisfff said:
but "From a ROOT adb shell (if you don't have root you'll need to figure out how to get it, kingroot, etc)". So, kingroot rooted the device, but I get problems with closing apps etc...
So, I am sorry, but I dont not know how I get adb root access? Is it a terminal emulator which root king gave root access or is it a special ADB command when the phone is in fastboot mode? In fastboot mode there is also (Secure)...
puh! :-/
Click to expand...
Click to collapse
If you can get root through king root even if its just temporary make sure all programs you can close are closed then use a terminal emulator on your phone and should be able to type in the command there I will do some more searching and see what else I can find out u may also want to go to rootninja website and ask them they could probably explain it better than me. Should have asked this first but I assume your on the latest version of lollipop if not that could be a problem and we will need to get u up to date on that first
Hi Grynch, yes, you nailed it. I will test it what you wrote. THX a lot!
Polarisfff said:
Hi Grynch, yes, you nailed it. I will test it what you wrote. THX a lot!
Click to expand...
Click to collapse
You can also use Sunshine to get root access. Just start it and follow the directions until it says that it has root access.
Grynch, your steps did work. Now I have flashed TWRP with success. Thank you all guys. You are saved my weekend!!!!!!!!!!
Great!
Polarisfff said:
Grynch, your steps did work. Now I have flashed TWRP with success. Thank you all guys. You are saved my weekend!!!!!!!!!!
Great!
Click to expand...
Click to collapse
Awesome good to know it works glad your unlocked enjoy your phone and if you haven't been there yet check out the moto maxx forum as well most of the ROMs are over there.
Grynch13 said:
Awesome good to know it works glad your unlocked enjoy your phone and if you haven't been there yet check out the moto maxx forum as well most of the ROMs are over there.
Click to expand...
Click to collapse
Was gonna link him the same tutorial.
Glad to see now three people succeed with this method.
Related
Okay guys and gals,
Today I'm gonna be giving you some directions on how to root the HTC Desire 510.
Steps:
1. What your gonna need is your phone, a usb, and a pc. (I used my xperia z as my pc)
2 Your gonna need to download [THIS]. This is the recovery image your gonna need. Just download that and put the file in a folder on your desktop or somewhere you'll remember.
3. Next your gonna want to reboot your phone into fastboot and connect it to your pc.
4. Next on your pc pull up cmd. (search cmd in the start menu) and type "fastboot devices" without the quotes and hit enter. If it shows your device your ready to move on.
5. Now your going to want to change your directory to where the image you downloaded is with a command similar to this "cd C:\users\xxx\desktop\recovery folder". Next rename the image to something simple like flash.img and type this into cmd "fastboot flash recovery flash.img" after doing that you should be able to boot into twrp from the hboot menu on your device.
6. Next on your computer download the su binary zip here. After downloading it reboot your device and copy it to your internal storage and reboot back to your recovery. Then in your recovery go find the supersu-v2.16.zip and flash it then reboot normally. Your device should now be rooted.
Thanks for all your help
cant unlock bootloader!!!! help!!!! please!!!
i know that to root the htc desire 510 first i need to unlock the bootloader, i followed the htc dev steps but when ever im submitting the unlock code nothing happens i just get the screen where i press yes or know but nothing else happens, my bootloader has been relocked yes i know i made a mistake can anyone help please!!!!
htnexx said:
i know that to root the htc desire 510 first i need to unlock the bootloader, i followed the htc dev steps but when ever im submitting the unlock code nothing happens i just get the screen where i press yes or know but nothing else happens, my bootloader has been relocked yes i know i made a mistake can anyone help please!!!!
Click to expand...
Click to collapse
same thing happened to me. does yours look like mine? http://forum.xda-developers.com/desire-510/help/qa-twrp-a11chl-a11ul-32-bit-t2951146 i have pictures posted of what it does when i try to unlock.
exactly!!!! i couldnt upload pics but is the same error mate, i hope somebody can help us...
I'm having problems with the recovery it won't unload the file I rename it recovery.img but still nothing
htnexx said:
exactly!!!! i couldnt upload pics but is the same error mate, i hope somebody can help us...
Click to expand...
Click to collapse
Did you make any progress? Any change?
LarryBoyG said:
Did you make any progress? Any change?
Click to expand...
Click to collapse
no change, im hoping somebody comes with a solution or ideas
Could anyone tell me why when I try to unlock my boot loader and go to get the token it tells me my token length is inccorrect. Is there any reason why this is happening?
oHaiiSquidd said:
Could anyone tell me why when I try to unlock my boot loader and go to get the token it tells me my token length is inccorrect. Is there any reason why this is happening?
Click to expand...
Click to collapse
make sure youre copying from " <<<TOKEN START>>>" to "<<<TOKEN END>>>" , arrows and all.
01keenan10 said:
make sure youre copying from " <<<TOKEN START>>>" to "<<<TOKEN END>>>" , arrows and all.
Click to expand...
Click to collapse
I did do that I tried multiple times. Also when I try to run the fastboot from HTC site it keeps telling me something about missingadbapi.dll
2858
Worked like a charm. Much appreciated
Many Thanks! Phone Rooted! but i had 1 question whats the difference between this recovery.img(10,594kb) and the one on twrp website which is 10,480kb in size. just wondering? thanks
This worked great for me, thanks! It was my first root ever, and I had some guidance along the way, but this thread as well as the one to unlock the bootloader were very useful. The only snag was HTC took forever to email me the key.
Thanks again!
-jason
is there a way to get s-off yet?
Works for HTC Desire with model # 0PCV1?
CurbThePain said:
Okay guys and gals,
Today I'm gonna be giving you some directions on how to root the HTC Desire 510. Basically what your gonna need is your phone, a usb, and a pc. (I used my xperia z as my pc) Over HERE is the recovery image your gonna need. Just look for the download. So download that file and put it in the root of your hard drive. Next your gonna want to reboot your phone into fastboot and connect it to your pc. Next on your pc pull up cmd. (search cmd in the start menu) and type "fastboot devices" without the quotes and hit enter. If it says its not a command or something like that head (here --> http://forum.xda-developers.com/showthread.php?t=2317790) and follow the directions. After that type fastboot devices again and hit enter. If it shows your device your ready to keep moving on. Your going to want to change your directory to where the image you downloaded is with a command similar to this "cd C:". Next rename the image to something simple like img.img and type this into cmd "fastboot flash recovery img.img" after doing that you should be able to boot into twrp from the hboot menu on your device. Next on your computer download the su binary zip here. After downloading it reboot your device and copy it to your internal storage and reboot back to your recovery. Then in your recovery go find the supersu-v2.16.zip and flash it then reboot normally. Your device should now be rooted.
Click to expand...
Click to collapse
I am reading that this seems to work on HTC Desire 510 devices however I know that Boost Mobile had its own little version of the HTC Desire 510 with the model number 0PCV1 and ive read a lot of threads stating that it was unable to be rooted. So before I started to touch anything I was wondering if this for sure will work with my HTC Desire 510 with model number 0PCV1. Thanks.
Have Boost HTC 510 OPCV1 and I'm unlocked and rooted. Only downside is the unlock threw it to s-on and it says tampered in hboot.
dipspit said:
Have Boost HTC 510 OPCV1 and I'm unlocked and rooted. Only downside is the unlock threw it to s-on and it says tampered in hboot.
Click to expand...
Click to collapse
Okay well its good to know rooting is possible. However the downside sounds iffy to me, I guess since Ive never rooted an android device yet. I have previously jailbreak'd an iPhone 5c on iOS 8.1
Does the s-on effect anything? And what about the hboot flagging as tampered?
The downsides is really nothin. I'm on the 510 right now so hope this explains it pretty well: htcdev.com/bootloader/about_unlock_process
dipspit said:
The downsides is really nothin. I'm on the 510 right now so hope this explains it pretty well: htcdev.com/bootloader/about_unlock_process
Click to expand...
Click to collapse
Okay that explains it pretty well to me. My final questions if your hanging around the thread, did you use this original posting to root your device?
I attempted to flash and unroot my Nexus 6 via Wugfresh's tool, and thought it was a success. I hit 'relock' and now the device is bootloader locked with no OS installed.
However, I can connect via fastboot so far, but I am not very good with it. I think I may also be able to push files, but when I attempted to flash SlimLP the device just reset.
TWRP is still present on the device, but I cannot unlock my bootloader without getting a ROM on there... So I am stuck...
I need to mail this phone back in tomorrow for cracked screen, so I am hoping someone can help me. Thank you.
SidedX said:
I attempted to flash and unroot my Nexus 6 via Wugfresh's tool, and thought it was a success. I hit 'relock' and now the device is bootloader locked with no OS installed.
However, I can connect via fastboot so far, but I am not very good with it. I think I may also be able to push files, but when I attempted to flash SlimLP the device just reset.
TWRP is still present on the device, but I cannot unlock my bootloader without getting a ROM on there... So I am stuck...
I need to mail this phone back in tomorrow for cracked screen, so I am hoping someone can help me. Thank you.
Click to expand...
Click to collapse
First check here... http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
Get the sdk tools and once set up, see if you can do adb devices and have the phone show up on the PC, if so, do adb push (name of rom file) then boot to twrp and install. If that doesn't work, check the same page above (since you don't have an OS not sure what would happen) try the unlock instructions for fastboot ( I would wait for someone else to comment before trying this). You might want to message this user http://forum.xda-developers.com/member.php?u=2872010 rootSU and see if he can give guidance, he has lots of experience.
Locked Bootloader
I still can't seem to get past the fact that my bootloader is locked...
Thanks though.
SidedX said:
I attempted to flash and unroot my Nexus 6 via Wugfresh's tool, and thought it was a success. I hit 'relock' and now the device is bootloader locked with no OS installed.
However, I can connect via fastboot so far, but I am not very good with it. I think I may also be able to push files, but when I attempted to flash SlimLP the device just reset.
TWRP is still present on the device, but I cannot unlock my bootloader without getting a ROM on there... So I am stuck...
I need to mail this phone back in tomorrow for cracked screen, so I am hoping someone can help me. Thank you.
Click to expand...
Click to collapse
Try this: Reboot to bootloader, select recovery mode, enter TWRP, mount MTP and push/sideload and flash a flashable image from here http://forum.xda-developers.com/nexu...tboot-t3066052.
Flashing
Hey, thanks for the tip.
The link you sent was dead, and can you help me understand the commands for flashing in ADB with a locked bootloader?
SidedX said:
Hey, thanks for the tip.
The link you sent was dead, and can you help me understand the commands for flashing in ADB with a locked bootloader?
Click to expand...
Click to collapse
Sorry my bad, here it is http://forum.xda-developers.com/nexus-6/development/fxz-nexus-6-recovery-flashable-fastboot-t3066052.
Follow the instructions as i posted, place the download rom in the /android-sdk/platform-tools/ folder and boot in bootloader and select recovery, select adb sideload there and type in cmd: adb sideload name.zip.
Unlocked Bootloader
The thread says they are for unlocked bootloader only.
I have TWRP installed, but for some reason at one point my bootloader was relocked.
So now I have No OS to 'enable oem unlock' to unlock my bootloader.
This is my issue.
SidedX said:
The thread says they are for unlocked bootloader only.
I have TWRP installed, but for some reason at one point my bootloader was relocked.
So now I have No OS to 'enable oem unlock' to unlock my bootloader.
This is my issue.
Click to expand...
Click to collapse
It worked for other users, but hey if you have a better option try that.
I don't understand, what do you mean it worked for other users? The thread specifically states the bootloader has to be unlocked, and unfortunately I do not have an unlocked bootloader.
So I cannot fix this issue unless I either get a rom to flash with a locked bootloader, or somehow force unlock the bootloader
SidedX said:
I don't understand, what do you mean it worked for other users? The thread specifically states the bootloader has to be unlocked, and unfortunately I do not have an unlocked bootloader.
So I cannot fix this issue unless I either get a rom to flash with a locked bootloader, or somehow force unlock the bootloader
Click to expand...
Click to collapse
Look in this thread http://forum.xda-developers.com/nex...bootloader-t3116744/post60931367#post60931367, he had the same problem as you (locked bootloader). I`m not a jehova witness trying to convince you to swap sides, i`am trying to help you here.
Thanks
I see, I was able to adb push /sdcard/. a factory image to get back in with a locked bootloader, thank you.
gee2012 said:
Look in this thread http://forum.xda-developers.com/nex...bootloader-t3116744/post60931367#post60931367, he had the same problem as you (locked bootloader). I`m not a jehova witness trying to convince you to swap sides, i`am trying to help you here.
Click to expand...
Click to collapse
hallelujah!
cam30era said:
hallelujah!
Click to expand...
Click to collapse
That covered the spiritual moment of the day
Relocked the bootloader on Droid Turbo/Moto Maxx and again try to unlock the bootloader
C:\adb>fastboot oem unlock
...
OKAY [ -0.000s]
finished. total time: -0.000s
Now this time there is no notification on the phone screen and phone reboots automatically. Now flashing the Android logo from last 5 minute.
Not able to boot in recovery mode. Only fastboot mode is working.
pedro_maciel said:
Relocked the bootloader on Droid Turbo/Moto Maxx and again try to unlock the bootloader
C:\adb>fastboot oem unlock
...
OKAY [ -0.000s]
finished. total time: -0.000s
Now this time there is no notification on the phone screen and phone reboots automatically. Now flashing the Android logo from last 5 minute.
Not able to boot in recovery mode. Only fastboot mode is working.
Click to expand...
Click to collapse
what happens if you do a factory reset from the bootloader? Also can you flash a factory image?
returns to the fastboot , and I can not flash factory image
Why did you relock the device in the first place? Not sure there is anything you can do at this point, I'm guessing you still had TWRP on the device which I believe would be the issue, but you can't remove that since your device is now locked and cannot be unlocked.
miketoasty said:
Why did you relock the device in the first place? Not sure there is anything you can do at this point, I'm guessing you still had TWRP on the device which I believe would be the issue, but you can't remove that since your device is now locked and cannot be unlocked.
Click to expand...
Click to collapse
Incorrect. With a locked bootloader, it's very possible to overwrite the recovery partition with the stock recovery menu. In fact, it's possible to flash all of the stock images with a locked bootloader. See section 0 of my guide: http://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684.
As for the OP's issue, I would say that if following section 0 of my guide does not solve the problem, you should probably consider your phone destroyed.
TheSt33v said:
Incorrect. With a locked bootloader, it's very possible to overwrite the recovery partition with the stock recovery menu. In fact, it's possible to to flash all of the stock images with a locked bootloader. See section 0 of my guide: http://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684.
As for the OP's issue, I would say that if following section 0 of my guide does not solve the problem, you should probably consider your phone destroyed.
Click to expand...
Click to collapse
Interesting, I didn't think that RSD would be able to modify the recovery partition on a locked device. Nonetheless if anything is going to work I believe what you have outlined is it St33v, best of luck to you OP.
miketoasty said:
Interesting, I didn't think that RSD would be able to modify the recovery partition on a locked device. Nonetheless if anything is going to work I believe what you have outlined is it St33v, best of luck to you OP.
Click to expand...
Click to collapse
Yep. As long as it passes the signature check, it flashes.
pedro_maciel said:
Relocked the bootloader on Droid Turbo/Moto Maxx and again try to unlock the bootloader
C:\adb>fastboot oem unlock
...
OKAY [ -0.000s]
finished. total time: -0.000s
Now this time there is no notification on the phone screen and phone reboots automatically. Now flashing the Android logo from last 5 minute.
Not able to boot in recovery mode. Only fastboot mode is working.
Click to expand...
Click to collapse
Let's be clear -- it was the Droid Turbo. Leave off the Moto Maxx part, OK?
You can lock/unlock a Moto Maxx (XT1225/XT1250) or even Moto Turbo (XT1225) all you want. In fact, the U.S. Moto Maxx XT1250 is IDENTICAL in every way to the Droid Turbo XT1254 -- radio bands, even the same FCC ID. Of all the Quarks, only Verizon's "Droid Turbo" has a carrier-locked down bootloader. All the others can be unlocked via the Motorola website. Whereas, the Droid Turbo bootloader unlock is a hack (Sunshine) that relies upon a vulnerability present in devices with Snapdragon 805.
miketoasty said:
Why did you relock the device in the first place? Not sure there is anything you can do at this point, I'm guessing you still had TWRP on the device which I believe would be the issue, but you can't remove that since your device is now locked and cannot be unlocked.
Click to expand...
Click to collapse
Yes, WHY would you do that? Devs went through all the trouble to find a vulnerability to UNlock the Droid Turbo, and you lock it back? Been posted MANY, MANY times with the Droid Turob it's a one-time unlock only, through Sunshine.
TheSt33v said:
Incorrect. With a locked bootloader, it's very possible to overwrite the recovery partition with the stock recovery menu. In fact, it's possible to to flash all of the stock images with a locked bootloader. See section 0 of my guide: http://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684.
As for the OP's issue, I would say that if following section 0 of my guide does not solve the problem, you should probably consider your phone destroyed.
Click to expand...
Click to collapse
While you can flash stock again with a locked bootloader and it can work, over in the Moto Maxx section many people did brick their phones because they refused to unlock their bootloaders first. They were more worried about their silly "warranty" than having a functioning device. We kept stressing, FIRST unlock your bootloader. If you mess up, it's an easy fix if a flash goes wrong. With a locked bootloader, a bad flash is a recipe for disaster.
Over in the Moto Maxx/Moto Turbo section was a write up about flashing images, similar to your write up:
http://forum.xda-developers.com/droid-turbo/help/tutorial-how-to-flash-official-firmware-t3074724
Usually people wanting to downgrade back to KitKat or flash a Quark image from another region (India Moto Turbo XT1225) got Lollipop first before Latin American Moto Maxx XT1225).
And people were able to do it with a locked bootloader -- but you have to do everything just right. In my case, first time I flashed from Moto Maxx image to Moto Turbo image, I messed up. I was looking at the example picture more than reading the instructions. But, since I had an unlocked bootloader, so what? Just did it again the correct way, the second time.
In the case of Moto Maxx brick people trying to flash to Moto Turbo, those people had to wait until Lollipop was released for their phones then try to re-flash an image made for their phones -- and HOPE it worked.
Re Unlock
I did the same thing on my xt1254 this is what Beaups told me from sunshine and it worked for me. I did it from terminal emulated on the device and then was ablebto reflash twrp
Beaups (TheRootNinja Support)
Dec 29, 17:10
tested this on my device and it worked. Keep in mind we can't guarantee it will work for you and also can't guarantee it won't kill your device (but I don't see why it should). Copy paste this command, do NOT make any errors.
From a ROOT adb shell (if you don't have root you'll need to figure out how to get it, kingroot, etc):
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/sp bs=1 seek=8
It should hang for a few seconds and then you should see something like:
dd: /dev/block/platform/msm_sdcc.1/by-name/sp: No space left on device
1048569+0 records in
1048568+0 records out
1048568 bytes transferred in 7.203 secs (145573 bytes/sec)
At that point reboot to bootloader and hopefully your problem is solved. Do NOT relock that device again in the future.
--beaups
I tried what you said and I could not, Recovery does not work
A failure occurred when the step system.img_sparsechunk
How did you re-lock your bootloader? What did you do?
pedro_maciel said:
Relocked the bootloader on Droid Turbo/Moto Maxx and again try to unlock the bootloader
C:\adb>fastboot oem unlock
...
OKAY [ -0.000s]
finished. total time: -0.000s
Now this time there is no notification on the phone screen and phone reboots automatically. Now flashing the Android logo from last 5 minute.
Not able to boot in recovery mode. Only fastboot mode is working.
Click to expand...
Click to collapse
tvlovers said:
How did you re-lock your bootloader? What did you do?
Click to expand...
Click to collapse
Before I answer this question, I have to make one thing clear: DON'T EVER DO THIS!
Verizon will still replace your phone under warranty with an unlocked bootloader as long as there is no physical damage. Motorola will do the same. Even if they do decide to get picky about bootloaders, re-locking your bootloader does not erase all traces of it ever being unlocked. Your bootloader will show status code 2, which indicates that it has been unlocked and re-locked again. If you lock it before you sell it to someone else, and they try to unlock it again, the phone will be ruined. There is absolutely no reason to do this.
With that out of the way, the command is "fastboot oem lock"
Don't ever use it.
Thank youfor the warning. I should make it clear before. The reason I was asking was to make sure that no one would accidentally do it as I see no reason to lock it again once unlocked.
Besides that fastboot command is there any other way to accidentally lock it? New VZW OTA software or OEM unlocking under developer options in settings?
Please advise.
TheSt33v said:
Before I answer this question, I have to make one thing clear: DON'T EVER DO THIS!
Verizon will still replace your phone under warranty with an unlocked bootloader as long as there is no physical damage. Motorola will do the same. Even if they do decide to get picky about bootloaders, re-locking your bootloader does not erase all traces of it ever being unlocked. Your bootloader will show status code 2, which indicates that it has been unlocked and re-locked again. If you lock it before you sell it to someone else, and they try to unlock it again, the phone will be ruined. There is absolutely no reason to do this.
With that out of the way, the command is "fastboot oem lock"
Don't ever use it.
Click to expand...
Click to collapse
tvlovers said:
Thank youfor the warning. I should make it clear before. The reason I was asking was to make sure that no one would accidentally do it as I see no reason to lock it again once unlocked.
Besides that fastboot command is there any other way to accidentally lock it? New VZW OTA software or OEM unlocking under developer options in settings?
Please advise.
Click to expand...
Click to collapse
A verizon OTA probably will not, but it's best to wait until someone here confirms that. In the past, they have not, but you never know what they'll try next. The OEM unlock setting in developer options does nothing on a Turbo. It's intended for true dev phones (or phones designed for carriers less tyrannical than Verizon) that can be unlocked and re-locked easily. It disables the "fastboot oem unlock" command that someone with a dev phone would normally use to easily unlock the bootloader. There are no other ways to lock the bootloader that I know of.
bubblesd306 said:
I did the same thing on my xt1254 this is what Beaups told me from sunshine and it worked for me. I did it from terminal emulated on the device and then was ablebto reflash twrp
Beaups (TheRootNinja Support)
Dec 29, 17:10
tested this on my device and it worked. Keep in mind we can't guarantee it will work for you and also can't guarantee it won't kill your device (but I don't see why it should). Copy paste this command, do NOT make any errors.
From a ROOT adb shell (if you don't have root you'll need to figure out how to get it, kingroot, etc):
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/sp bs=1 seek=8
It should hang for a few seconds and then you should see something like:
dd: /dev/block/platform/msm_sdcc.1/by-name/sp: No space left on device
1048569+0 records in
1048568+0 records out
1048568 bytes transferred in 7.203 secs (145573 bytes/sec)
At that point reboot to bootloader and hopefully your problem is solved. Do NOT relock that device again in the future.
--beaups
Click to expand...
Click to collapse
Has anyone that has unlocked using this method been able to flash CM or a CM-based ROM?
Sent from my XT1254 using Tapatalk
richii0207 said:
Has anyone that has unlocked using this method been able to flash CM or a CM-based ROM?
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
This isn't unlocking for a first time. This is unlocking for a second time.
Typically when you unlock a bootloader you can relock and unlock easily in adb.
For our device this is not the case and it should never be relocked.
A few have and have always succeeded with those commands.
Again this is only for a previously unlocked boot loader.
Sent from my DROID Turbo using XDA-Developers mobile app
mrkhigh said:
This isn't unlocking for a first time. This is unlocking for a second time.
Typically when you unlock a bootloader you can relock and unlock easily in adb.
For our device this is not the case and it should never be relocked.
A few have and have always succeeded with those commands.
Again this is only for a previously unlocked boot loader.
Sent from my DROID Turbo using XDA-Developers mobile app
Click to expand...
Click to collapse
Ya. I did unlock, relock, then unlock again. I am able to install TWRP, and use CF ROM with no issues but if I install CM, I get data but NO voice which is very odd.
Reflashing radios and messing with the network configurations did not help.
I've seen people that have unlocked twice and are able to run CM without any issues.
I've tried reflashing firmware, Reflashing SU38 and OTAing to 44 to no avail. I used to run CM before I relocked without a problem.
Although I do get errors flashing GPT partition, it says that it flashes backup GPT instead of primary.
Sent from my XT1254 using Tapatalk
richii0207 said:
Ya. I did unlock, relock, then unlock again. I am able to install TWRP, and use CF ROM with no issues but if I install CM, I get data but NO voice which is very odd.
Reflashing radios and messing with the network configurations did not help.
I've seen people that have unlocked twice and are able to run CM without any issues.
I've tried reflashing firmware, Reflashing SU38 and OTAing to 44 to no avail. I used to run CM before I relocked without a problem.
Although I do get errors flashing GPT partition, it says that it flashes backup GPT instead of primary.
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
Is it possible you're not doing a full wipe? What version of twrp are you flashing with?
Sent from my DROID Turbo using XDA-Developers mobile app
mrkhigh said:
Is it possible you're not doing a full wipe? What version of twrp are you flashing with?
Sent from my DROID Turbo using XDA-Developers mobile app
Click to expand...
Click to collapse
I realized that I can only make calls when VoLTE is enabled on stock. If I turn it off, I cannot make any phone calls but can access data still. I went into diagnostic mode and it showed " Phone ICCID compare with sim CCID error" with "UNKNOWN" under Phone ICCID. Hmmm..
Ive done searching and just basically see alll sorts of other stuff. Im very familiar with rooting and modding. Done it now on 6 different phones. way back to the OG Droid.,.. This one is through the Jump program...... Id like to remain pure stock but root yet still have the ability to drop root when turning in the phone to get my g5 or v20. Root is all i want. no recovery or os..... The root will allow me to do viper audio, titanium and camera mods........ its H811 Tmobile running 20q pure stock.. please help..
MorbidMonkey101 said:
Ive done searching and just basically see alll sorts of other stuff. Im very familiar with rooting and modding. Done it now on 6 different phones. way back to the OG Droid.,.. This one is through the Jump program...... Id like to remain pure stock but root yet still have the ability to drop root when turning in the phone to get my g5 or v20. Root is all i want. no recovery or os..... The root will allow me to do viper audio, titanium and camera mods........ its H811 Tmobile running 20q pure stock.. please help..
Click to expand...
Click to collapse
yes its pure stock. you need to unlock bootloader .. and when return you need to relock it.
here are the commands for locking and relocking, and placing twrp temporary root it and then you are all set.
i use this method
go to where it says
Bootloader OEM Unlock + Root:
http://forum.xda-developers.com/tmobile-g4/development/stock-h811-20i-images-kdz-flashable-t3308227
I was able to Lock the bootloader.
1. I connected the phone to my PC
2. Powered on the Phone (it took a few tried of pulling the battery and powering on)
3. Check the box for OEM Unlock in Dev. Option
4. Use Minimal ADB and Fastboot and type in
Quote:
adb devicecs
- you should see the phone listed as one of the devices in the command line window
Quote:
adb reboot bootloader
- phone should reboot and you shouold see 3 lines of text on top
Quote:
fastboot oem lock
- nothing will happen on the phone, but on in the commandline it should say that it is done
Quote:
fastboot reboot
Phone reboots and the boot screen does not show the unlocked bootloader message anymore
Going to try right now...actually better wait til after work tommorrow. Need it for alarm and tv time.. Just in case something happens.
raptorddd said:
yes its pure stock. you need to unlock bootloader .. and when return you need to relock it.
here are the commands for locking and relocking, and placing twrp temporary root it and then you are all set.
i use this method
go to where it says
Bootloader OEM Unlock + Root:
http://forum.xda-developers.com/tmobile-g4/development/stock-h811-20i-images-kdz-flashable-t3308227
I was able to Lock the bootloader.
1. I connected the phone to my PC
2. Powered on the Phone (it took a few tried of pulling the battery and powering on)
3. Check the box for OEM Unlock in Dev. Option
4. Use Minimal ADB and Fastboot and type in
Quote:
adb devicecs
- you should see the phone listed as one of the devices in the command line window
Quote:
adb reboot bootloader
- phone should reboot and you shouold see 3 lines of text on top
Quote:
fastboot oem lock
- nothing will happen on the phone, but on in the commandline it should say that it is done
Quote:
fastboot reboot
Phone reboots and the boot screen does not show the unlocked bootloader message anymore
Click to expand...
Click to collapse
To unlock first and add root i use this?
Bootloader OEM Unlock + Root:
http://forum.xda-developers.com/tmobile-g4/development/stock-h811-20i-images-kdz-flashable-t3308227
It wants me to downgrade and stuff. Is it possible to do it without downgrading? Also seems as alot of other posts say once your 20q you do not revert back to anything lower than 20o.. thats my concern.
Managed to get it unlocked.. Using that post.. Did not do the root part... So now.. Whats the next step? Install Recovery im sure. Then ROM... The plot thickens.
MorbidMonkey101 said:
To unlock first and add root i use this?
Bootloader OEM Unlock + Root:
http://forum.xda-developers.com/tmobile-g4/development/stock-h811-20i-images-kdz-flashable-t3308227
It wants me to downgrade and stuff. Is it possible to do it without downgrading? Also seems as alot of other posts say once your 20q you do not revert back to anything lower than 20o.. thats my concern.
Managed to get it unlocked.. Using that post.. Did not do the root part... So now.. Whats the next step? Install Recovery im sure. Then ROM... The plot thickens.
Click to expand...
Click to collapse
no dont downgrade i just used that post as reference the steps you need to use.. antirollback V3 (20o-20p-20q) (20i 10n this are V2.
yes install recovery use the same guide there..
use this recovery
https://dl.twrp.me/h811/
and rename it to twrp.img so the command should be renamed to twrp.img
have it on sd card. and hwen it boot you to twrp do install, then semlect botom right IMAGE and find the location the twrp is and select it and flash it , it will ask in a window select revocery .. and you are done with twrp installed permanent.
MorbidMonkey101 said:
To unlock first and add root i use this?
Bootloader OEM Unlock + Root:
http://forum.xda-developers.com/tmobile-g4/development/stock-h811-20i-images-kdz-flashable-t3308227
It wants me to downgrade and stuff. Is it possible to do it without downgrading? Also seems as alot of other posts say once your 20q you do not revert back to anything lower than 20o.. thats my concern.
Managed to get it unlocked.. Using that post.. Did not do the root part... So now.. Whats the next step? Install Recovery im sure. Then ROM... The plot thickens.
Click to expand...
Click to collapse
kk so i got it unlocked and rooted using that method.. but my phone reboots automatically every so often... what gives.. used adb to temp boot twrp...installed Su then rebooted...all done AFTER unlock
MorbidMonkey101 said:
kk so i got it unlocked and rooted using that method.. but my phone reboots automatically every so often... what gives.. used adb to temp boot twrp...installed Su then rebooted...all done AFTER unlock
Click to expand...
Click to collapse
Figured id say screw it.. I already unlocked and rooted.. might as well ROM it too.
im now running this mod. just unlocked and rooted using the method you told me.. then used twrp to install this ROM
https://forum.xda-developers.com/tmobile-g4/development/rom-g4-h811-xtreme-rom-v1-0-7-28-15-t3167667
With the Moto Z, after I returned the phone to stock (flashed stock firmware and locked the bootloader), I'd be able to flash stock firmware with the flashing locked.
Not so with the Motorola One Zoom. In other words, flashing stock and re-locking didn't return the phone to its pristine state. Even when flashing stock firmware over stock firmware, I have to unlock the bootloader.
Differences I observed: on the bootloader screen, when re-locked the Z would show "oem_locked" again. On the One Zoom, it shows "flashing_locked" instead. I'm pretty sure it showed "oem_locked" before unlocking.
WIth the Z, every time I wanted to unlock the bootloader, I had to issue "fastboot oem unlock" followed by the unlock code. The code isn't necessary with the re-locked One Zoom.
In other words, maybe it was a one-way trip. It seems that the phone won't return to its original state, it looks it's modified for good. And I'm afraid this means bye-bye to automatic updates.
Am I missing something here?
My bootloader is also unlocked and I dont have any problems with receiving and installing OTAs I also have Magisk and EdExposed installed - no problems at all.
rafikowy said:
My bootloader is also unlocked and I dont have any problems with receiving and installing OTAs I also have Magisk and EdExposed installed - no problems at all.
Click to expand...
Click to collapse
Phew! I'm glad I'll be able to install OTAs. Have you tried flashing it manually or via RSD Lite? Here it won't flash.
Whammamoosha said:
Phew! I'm glad I'll be able to install OTAs. Have you tried flashing it manually or via RSD Lite? Here it won't flash.
Click to expand...
Click to collapse
Hey, yes, flashing manually. I will provide you flashing scripts tomorrow.
rafikowy said:
Hey, yes, flashing manually. I will provide you flashing scripts tomorrow.
Click to expand...
Click to collapse
Don't bother, I have mine. Thanks.
I would like the flash script if someone would share it
Help with unlocking bootloader
I tried to unlock the bootloader and i am now in a menu with an android with his chest open. In the cmd on my pc i try to type fastboot flashing unlock but it just gives me an error.
I dont know if this is the correct place to post this but i have no idea where to post it and i dont want my phone get bricked.
Bodeman12345 said:
I tried to unlock the bootloader and i am now in a menu with an android with his chest open. In the cmd on my pc i try to type fastboot flashing unlock but it just gives me an error.
I dont know if this is the correct place to post this but i have no idea where to post it and i dont want my phone get bricked.
Click to expand...
Click to collapse
In the settings for developers you gave permission for Factory Unlock?
ilia3367 said:
In the settings for developers you gave permission for Factory Unlock?
Click to expand...
Click to collapse
I enabled the setting to unlock oem bootloader is that the same?
Bodeman12345 said:
I enabled the setting to unlock oem bootloader is that the same?
Click to expand...
Click to collapse
yes.
What instruction did you use to unlock the bootloader?
What region is your device manufactured for?
Does your PC see your device connected to the fastboot mod?
What does this command give you:
Code:
fastboot devices
If the device is detected, enter the command:
Code:
fastboot getvar all
And copy the result here.
ilia3367 said:
yes.
Click to expand...
Click to collapse
Yes I did that
Bodeman12345 said:
Yes I did that
Click to expand...
Click to collapse
Answer the other questions, please!
diculpe por que mi pc no ve el fastboot de mi one zoom?
ilia3367 said:
yes.
What instruction did you use to unlock the bootloader?
What region is your device manufactured for?
Does your PC see your device connected to the fastboot mod?
What does this command give you:
If the device is detected, enter the command:
And copy the result here.
Click to expand...
Click to collapse
I used this youtube video
I dont know where it is manifactured but I live in the netherlands.
I dont get the 3th question
I will do the commands in a couple minutes
Hey all,
I have the Moto One Zoom running on Android 9.
Also, It's Rooted with Magisk and have Riru EdXposed installed, can I install my OTA updates without bootloop or do I have to Uninstall Magisk, relock bootloader and factory reset/flash stock firmware to get latest OTA updates?
Any feedback is appreciated.
Thanks