FORUMS
Remove All Ads from XDA

Relocked Bootloader... Bricked :(

10 posts
Thanks Meter: 4
 
By pedro_maciel, Junior Member on 1st February 2016, 03:59 PM
Post Reply Email Thread
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.
 
 
1st February 2016, 04:19 PM |#2  
BladeRunner's Avatar
Senior Member
Thanks Meter: 361
 
Donate to Me
More
Quote:
Originally Posted by 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.

what happens if you do a factory reset from the bootloader? Also can you flash a factory image?
1st February 2016, 04:37 PM |#3  
OP Junior Member
Thanks Meter: 4
 
More
returns to the fastboot , and I can not flash factory image
1st February 2016, 05:58 PM |#4  
Senior Member
Flag Pittsburgh
Thanks Meter: 489
 
More
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.
1st February 2016, 06:16 PM |#5  
TheSt33v's Avatar
Senior Member
Flag The Stupid Country
Thanks Meter: 1,059
 
More
Quote:
Originally Posted by 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.

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/droi...stall-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.
The Following 2 Users Say Thank You to TheSt33v For This Useful Post: [ View ] Gift TheSt33v Ad-Free
1st February 2016, 06:27 PM |#6  
Senior Member
Flag Pittsburgh
Thanks Meter: 489
 
More
Quote:
Originally Posted by TheSt33v

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/droi...stall-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.
1st February 2016, 06:31 PM |#7  
TheSt33v's Avatar
Senior Member
Flag The Stupid Country
Thanks Meter: 1,059
 
More
Quote:
Originally Posted by miketoasty

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.
2nd February 2016, 08:49 AM |#8  
ChazzMatt's Avatar
Senior Member
Flag Atlanta, Georgia
Thanks Meter: 3,815
 
More
Quote:
Originally Posted by 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.

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.

Quote:
Originally Posted by 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.

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.

Quote:
Originally Posted by TheSt33v

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/droi...stall-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://forum.xda-developers.com/droi...mware-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.
The Following 2 Users Say Thank You to ChazzMatt For This Useful Post: [ View ] Gift ChazzMatt Ad-Free
10th February 2016, 08:56 PM |#9  
bubblesd306's Avatar
Member
Thanks Meter: 14
 
More
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
The Following 3 Users Say Thank You to bubblesd306 For This Useful Post: [ View ] Gift bubblesd306 Ad-Free
23rd February 2016, 08:42 PM |#10  
OP Junior Member
Thanks Meter: 4
 
More
I tried what you said and I could not, Recovery does not work
23rd February 2016, 08:44 PM |#11  
OP Junior Member
Thanks Meter: 4
 
More
A failure occurred when the step system.img_sparsechunk
Post Reply Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes