Relocked Bootloader... Bricked :(

[pedro_maciel]

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.

 

[BladeRunner]

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.

what happens if you do a factory reset from the bootloader? Also can you flash a factory image?

 

[pedro_maciel]

returns to the fastboot , and I can not flash factory image

 

[miketoasty]

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.

 

[TheSt33v]

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.

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://xdaforums.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.

 

[miketoasty]

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://xdaforums.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.

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.

 

[TheSt33v]

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.

Yep. As long as it passes the signature check, it flashes.

 

[ChazzMatt]

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.

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.

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.

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.

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://xdaforums.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.

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://xdaforums.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.

 

[bubblesd306]

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

 

[pedro_maciel]

I tried what you said and I could not, Recovery does not work

 

[pedro_maciel]

A failure occurred when the step system.img_sparsechunk

 

[tvlovers]

How did you re-lock your bootloader? What did you do?

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.

 

[TheSt33v]

How did you re-lock your bootloader? What did you do?

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.

 

[tvlovers]

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.

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.

 

[TheSt33v]

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.

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.

 

[richii0207]

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

Has anyone that has unlocked using this method been able to flash CM or a CM-based ROM?

Sent from my XT1254 using Tapatalk

 

[mrkhigh]

Has anyone that has unlocked using this method been able to flash CM or a CM-based ROM?

Sent from my XT1254 using Tapatalk

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

 

[richii0207]

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

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

 

[mrkhigh]

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

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

 

[richii0207]

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

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..