yashsingh1/xdaforums huggingface dataset:
[Droid Ultra General] hesam1373:
Droid Maxx

please help

C:\Python27>C:\Python27\python 8960_blankflash.py

Emergency download enumeration detected on port - com17

Starting qflash!

Executing command qflash.exe -com17 -ramload MPRG8960.hex -mbn 33 MSM8960_bootloader_singleimage.bin -v -o

Motorola qflash Utility version 1.3

COMPORT :COM17

RAMLOADER :MPRG8960.hex

type is 0x21

7 mbn file name MSM8960_bootloader_singleimage.bin type 33

verbose mode on

Motorola qflash dll version 1.6

RAMLOADER VERSION: PBL_DloadVER2.0

------------------------------------------------------

DEVICE INFORMATION:

------------------------------------------------------

Version : 0x8

Min Version : 0x1

Max Write Size: 0x600

Model : 0x90

Device Size : 0

Description : Intel 28F400BX-TL or Intel 28F400BV-TL

------------------------------------------------------

Using passed in packet size, changing from 0x600 -> 0x600

EXTENDED_LINEAR_ADDRESS_REC @ 0x2a000000

Write 65536 bytes @ 0x2a000000

100EXTENDED_LINEAR_ADDRESS_REC @ 0x2a010000

Write 11840 bytes @ 0x2a010000

100START_LINEAR_ADDRESS_REC @ 0x2a000000

EOF_REC

Sleeping for 3s

-----------------------------------------------------

RAM DOWNLOADER INFORMATION

-----------------------------------------------------

cmd : 0x2

description : QCOM fast download protocol targ

version_number : 0x7

compatible_version: 0x2

max_block_size : 0x400

flash_base_address: 0x0

flash_id_len : 0x4

flash id : eMMC

window_size : 0x1e

number_of_sectors : 0x80

-----------------------------------------------------

sdl_send_security_mode: secutiry mode 0x0

Flashing MSM8960_bootloader_singleimage.bin 1969664 bytes into device

Keeping the first packet (1024 bytes) as hostage

Will release it if all is flashed well

100

Hostage released!

done

Blank flashing successful

Device will now enumerate in fastboot mode

but nothing not turning on or fastboot mode please help
[Droid Ultra General] Daniyalahmed:
my device ultra mini xt1030... any solution to fix my device

C:\Python27>python qdload.py MPRG8960_MOTO.bin -ptf _ultra/partitions.txt

QDLoad utility version 1.2 (c) VBlack 2014

Found TTY port: com12

Sending MAGIC ...

QCOM fast download protocol targ:

Version: 7

Compatible version 2

Maximum block size 1024 (0x00000400)

Base address of Flash 0x00000000

Flash: eMMC

Window size: 30

Number of sectors: 128

First sector size: 2097152 (0x00200000)

Feature bits: 09

Sending SBL Reset...

LOG: Cannot reset before close

ERROR: 0x0000000f: Cannot reset before close

Done
[Droid Ultra General] VBlack:
You need to install python to be able to execute .py scripts
[Droid Ultra General] BUZZAPT:
i'm executing it in a folder with writable permission but i get it

./gpt_parser.py pt.bin > partitions.txt

/system/bin/sh: can't create partitions.txt: Read-only file system

i tried to change the permission to that file but it don't change

any idea?
[Droid Ultra General] VBlack:
Hm, you could try to specify full path to partitions.txt (like /home/<user>/partitions.txt). or try to add ./ before it like this:

./gpt_parser.py pt.bin > ./partitions.txt
[Droid Ultra General] joel_sinbad:
Any answer for me? Why I'm getting that error? Do I need extra files?
[Droid Ultra General] VBlack:
According to your log - everything going perfect, until we start transfer multiple images

. Currently I'm trying to find a way to transfer files in different way if multi fails...
[Droid Ultra General] VBlack:
Try this modified version of script:

http://pastebin.com/hPNaPp15
[Droid Ultra General] joel_sinbad:
What is this multi thing? Can you explain me the concept of what the script is doing?
[Droid Ultra General] VBlack:
There is qualcomm protocol to download images to empty (bricked) device, which shows as QDLOAD. There two stages. On first stage we upload MPRG file (signed by vendor) and execute it. This file implements qcom fast download protocol. Next we need to switch to secure mode, open multiple image transfer and start transfer.
[Droid Ultra General] joel_sinbad:
Ok, I got this:

QDLoad utility version 1.2.2c (c) VBlack 2014

Found TTY port: com65

Requesting Params...

Params:

Version: 8

Min version: 1

Max write size: 1536 (0x00000600)

Model: 144

Device size: Invalid or unrecognized Flash device, or Flash device progr

amming not supported by this implementation

Device type: Intel 28F400BX-TL or Intel 28F400BV-TL

Requesting SoftwareVersion...

Version: PBL_DloadVER2.0

Requesting SerialNumber...

Serial number: 00,00,48,03

Requesting HW Id...

HW Id: 00,00,48,03,e1,10,7e,00

Requesting PublicKey...

PublicKey: 39,c4,ee,3e,b5,be,eb,87,8e,2f,e3,b8,53,4d,14,6f,91,ca,fd,bb,94,2a,0d

,aa,d0,1e,b0,87,62,d4,b9,b8

Uploading file 'MPRG8960_MOTO.bin' to addr 0x2a000000...

Executing...

Found TTY port: com65

Sending MAGIC ...

QCOM fast download protocol targ:

Version: 7

Compatible version 2

Maximum block size 1024 (0x00000400)

Base address of Flash 0x00000000

Flash: eMMC

Window size: 30

Number of sectors: 128

First sector size: 2097152 (0x00200000)

Feature bits: 09

Sending secureMode...

Sending openMulti ...

LOG: Open multi failed, unknown error

ERROR: 0x00000007: Open multi failed, unknown error

Trying without openMulti...

Uploading file2 'c:\unbrick\_mini/sbl1.mbn' to addr 0x6420000...

Traceback (most recent call last):

File "qdload2.py", line 943, in <module>

main()

File "qdload2.py", line 900, in main

res = doStage_SBL(tty, images)

File "qdload2.py", line 734, in doStage_SBL

if not uploadFile_SBL( tty, image ):

File "qdload2.py", line 615, in uploadFile_SBL

response = readPacket( tty, 5.0, PACKET_WRITE_CHUNK2[0]+1 )

NameError: global name 'PACKET_WRITE_CHUNK2' is not defined
[Droid Ultra General] VBlack:
Sorry, syntax error, try now:

http://pastebin.com/hPNaPp15
[Droid Ultra General] joel_sinbad:
Uploading file2 'c:\unbrick\_mini/sbl1.mbn' to addr 0x6420000...

Failed to read response.

Failed to receive ACK for 103 packets

Outstanding: 0x06437400

Outstanding: 0x06438000

Outstanding: 0x06430c00

Outstanding: 0x0642e800

Outstanding: 0x0642ac00

Outstanding: 0x0642b400

Outstanding: 0x06439800

Outstanding: 0x0642dc00

Outstanding: 0x06434400

Outstanding: 0x0642f800

Outstanding: 0x06432000

Outstanding: 0x06425c00

Outstanding: 0x06425800

Outstanding: 0x06428800

Outstanding: 0x06438800

Outstanding: 0x06422400

Outstanding: 0x0642e000

Outstanding: 0x06439000

Outstanding: 0x06425000

Outstanding: 0x06428000

Outstanding: 0x06421c00

Outstanding: 0x0642e400

Outstanding: 0x06427c00

Outstanding: 0x06420800

Outstanding: 0x06438c00

Outstanding: 0x06437800

Outstanding: 0x06426400

Outstanding: 0x06422c00

Outstanding: 0x06439400

Outstanding: 0x0642ec00

Outstanding: 0x06438400

Outstanding: 0x06434000

Outstanding: 0x0642f000

Outstanding: 0x06434c00

Outstanding: 0x06426000

Outstanding: 0x06436400

Outstanding: 0x06420400

Outstanding: 0x06431c00

Outstanding: 0x06431000

Outstanding: 0x06429400

Outstanding: 0x06426800

Outstanding: 0x06420000

Outstanding: 0x06428c00

Outstanding: 0x0642c400

Outstanding: 0x06431800

Outstanding: 0x06429000

Outstanding: 0x06423400

Outstanding: 0x06423c00

Outstanding: 0x06429800

Outstanding: 0x06421800

Outstanding: 0x0642c800

Outstanding: 0x06436800

Outstanding: 0x06431400

Outstanding: 0x06423800

Outstanding: 0x06420c00

Outstanding: 0x0642c000

Outstanding: 0x06436000

Outstanding: 0x06423000

Outstanding: 0x06433800

Outstanding: 0x06435c00

Outstanding: 0x06424000

Outstanding: 0x0642a400

Outstanding: 0x06435400

Outstanding: 0x06421400

Outstanding: 0x06433c00

Outstanding: 0x06427800

Outstanding: 0x0642a800

Outstanding: 0x06424c00

Outstanding: 0x06424400

Outstanding: 0x0642a000

Outstanding: 0x06435000

Outstanding: 0x06433400

Outstanding: 0x0642fc00

Outstanding: 0x06421000

Outstanding: 0x06436c00

Outstanding: 0x06435800

Outstanding: 0x06433000

Outstanding: 0x0642d000

Outstanding: 0x0642f400

Outstanding: 0x06432c00

Outstanding: 0x06430400

Outstanding: 0x06437c00

Outstanding: 0x06432800

Outstanding: 0x06424800

Outstanding: 0x0642cc00

Outstanding: 0x06429c00

Outstanding: 0x06430800

Outstanding: 0x0642bc00

Outstanding: 0x0642d400

Outstanding: 0x06427000

Outstanding: 0x06430000

Outstanding: 0x06426c00

Outstanding: 0x06437000

Outstanding: 0x06425400

Outstanding: 0x0642b000

Outstanding: 0x06432400

Outstanding: 0x06422000

Outstanding: 0x0642b800

Outstanding: 0x06427400

Outstanding: 0x06434800

Outstanding: 0x06428400

Outstanding: 0x06422800

Outstanding: 0x0642d800

Sending SBL Reset...

Done, with errors!!!
[Droid Ultra General] VBlack:
So It's won't go without opening multi transfer... I will try to find something else.
[Droid Ultra General] joel_sinbad:
It's strange, I know...
[Droid Ultra General] VBlack:
It is looks like your phone is not compatible with MPRG8960_MOTO.bin. You could try to find one from official moto flash pakage for your phone...
[Droid Ultra General] shutins:
moto x xt1053

where can I find aboot.mbn and partitions.mbn for moto x? I have other need files for this script...(sorry for my english)
[Droid Ultra General] takiulin@gmail..com:
Тут все файлы для MOTO X. Take it
[Droid Ultra General] shutins:
lol, it's my files and it wasn's true files) true files here) it's for 30.b7 bootloader
[Droid Ultra General] todarkness:
Here you can download the factory images for droid maxx/moto x

https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
[Droid Ultra General] sander.odessa:
Upload plizz partitions.mbn for moto x xt1056 boot loader 30.07.
[Droid Ultra General] shawnsingh:
Can someone post a droid RAZR m partion .txt
[Droid Ultra General] Johnny Wong:
Can I use this method to downgrade from 4.4.4 to 4.4 so I can unlock bootloader?
[Droid Ultra General] VBlack:
I didn't try by myself, but I don't see any problems from technical perspective. I could try on my spare droid Ultra in few days...
[Droid Ultra General] Johnny Wong:
That would be amazing news for those of us stuck with a locked boot loader!!! Thank you!!!
[Droid Ultra General] kilgil27:
How would one do this with a functional phone on 4.4.4? Would you just plug it in and run the commands? Should it be on or off?
[Droid Ultra General] Johnny Wong:
That is a great question since we have a functioning phone, the phone would not show up in Windows as QHSUSB_DLOAD mode. I hope there's a way to get into that mode without intentionally bricking the phone or shorting the board lol.
[Droid Ultra General] VBlack:
Yes, there is a way, but it need root... I upgrade my test ultra to 4.4.4, brick it, but when I trying to upload sbl* ... etc from 4.4 - it is still in QDL mode - it is store somewhere prev revision for sure. Right now I am not able to downgrade even with bricking phone. If I found a way I will let you know.
[Droid Ultra General] Johnny Wong:
Thank you for putting your phone at risk for the rest of us. I guess it is impossible to downgrade the bootloader even with the blank files.
[Droid Ultra General] shawnsingh:
Guys droid RAZR m files
[Droid Ultra General] :
Ok, guys; I wanna ask a question. How do I extract the bootloader partition from my working RAZR M, to revive the bootloader unlocked but bricked RAZR M?
[Droid Ultra General] :
By the way, Johnny Wong: correct. Bootloader has signatures in it (determined by trustzone file - tz.mbn) so if anyone tries to downgrade the bootloader on the locked phone, TZ chain of trust is compromised. That can also happen to the unlocked phones too, which I have been seeing on RAZR M threads often. And, there is definitely a backup copy on the separate partition - determined by looking at converted partition.txt file.
[Droid Ultra General] shawnsingh:
I have the files
[Droid Ultra General] :
shawnsingh, thanks.
[Droid Ultra General] chefberardi:
Did you find those xt907 recovery files? If so, would you mind sharing?
[Droid Ultra General] :
Still need to find a way to mount the GPT image and remove the unnecessary files and then reimage for distribution.
[Droid Ultra General] shawnsingh:
Check my Forum.
[Droid Ultra General] Wilmason686:
xt907

Has anybody been able to find out about getting this to work with the Razr m? really could use the help!!!

I have python and everything is detected with qualcomm drivers just need to the right files to flash!.
[Droid Ultra General] :
I am almost there. I had to collect few information, some seem to be helpful. Still have yet to get some bricked RAZR Ms to test it on - I have a working RAZR M I pulled some important bootloader partitions from.

As with any and all Motorola MSM8960 hardwares, it would be very hard (probably impossible) to recover a brick with locked bootloader, due to how the second stage BIOS (sbl2) works - if it's definitely unlocked (Status 3), you would have better chance of recovering it. As for RAZR HD, I'd rather have some owners of unlocked XT926 dd their bootloader partitions, and I'll include them in a toolkit to recover the hard bricks.
[Droid Ultra General] :
Getting further in the analysis of the bricked RAZR M motherboard I just received - it's going to be complicated due to the fact that there are various behaviors in the bricked Motorola MSM8960 devices; being cloaked as a HID, SSD GPT volumes being visible and/or DLOAD so there is not a "one size fits all" solution yet, but hopefully I can find out soon.
[Droid Ultra General] fabioalves357123:
I would like to have the files to relive my razr hd xt925 , please send picture manufactures and nescessarios files

feeling excited
[Droid Ultra General] twomeowmoewbeanz:
Hello guys, would this procedure work for bricked Moto G phones due to downgrading from lollipop?
[Droid Ultra General] shawnsingh:
We can't distrusted until there is success in this procedure you can read everything we have been doing.

---------- Post added at 05:54 PM ---------- Previous post was at 05:53 PM ----------

brick repair link

http://xdaforums.com/showthread.php?t=2934432

[Q] Droid Razr M hardbrick **FIX**
[Droid Ultra General] :
twomeowmoewbeanz, as long as the FXZ exists, it's possible - I am figuring out the most problematic things with bricked RAZR M, such as TZ signature failure. After I'm satisfied with the unbrick success, I'll either throw together the toolkit or the tutorial, depending on the differences between Motorola MSM8960 (I don't think Moto G is MSM8960 based, but probably a specific version of Moto G is - I'll look at that).
[Droid Ultra General] twomeowmoewbeanz:
rampich pand

Hi, and thanks!

I am not sure what FXZ stands for, could you elaborate please?

The recent bricking issues the Moto G faces were due to people upgrading to Lollipop GPE and then downgrading to Kitkat 4.4.2 and OTA-ing to 4.4.4. The problem is that the bootloader became corrupted or it doesn't allow flashing an older kernel, like the one used in Kitkat. The blankflash tools exist for versions 4.4.2 and 4.4.4 but not 5.0.1 and when trying to use them, they cannot be flashed. If you want, there is an excellent thread here.

Btw, the Moto G uses model 8226. I would be willing to try this thread's method to my bricked Moto G but I do not have the partitions file.
[Droid Ultra General] :
FXZ is Motorola's wording on the firmware package containing the bootloader - BIOS - images and the system disk image containing the Android operating system and apps).

I'd have to look at it also, since Moto G uses similar Snapdragon CPU family and I would need a good trail on discovering how to be able to successfully unbrick a several Motorola Snapdragon phones, and it's apparently much more difficult but I am not going to give up on it any time soon
[Droid Ultra General] carbonat87:
Droid mini hard brick

Hello guys. I've bricked my Droid mini with SU5-24 (Android 4.4.4) into qdload mode by blbrick and I didn't know blankflash from version 4.4.2 of official firmware wouldn't help to restore boot. So, I'm asking you for dumps (or backups) of sbl3, aboot, tz, rpm, sbl2, sbl1 partitions from your Droid Maxx/Ultra/Mini with working SU5-24 firmware.
[Droid Ultra General] fabioalves357123:
I would like to test this method to retrieve my razr hd xt925 will be that you would succeed ? please guide me where I could image files ?

gostaria de testar esse metodo para recuperar o meu razr hd xt925 sera que teria sucesso? por favor me orientem aonde eu conseguiria os arquivos
[Droid Ultra General] shawnsingh:
If you have it in qdload why not use qpst
[Droid Ultra General] carbonat87:
SU5-24 Qdload

I can't use QPST cause I don't have valid version of MSM8960.hex and mbn files. And I'm already using this method to upload files into phone. So, I just need valid version for sbl3, aboot, tz, rpm, sbl2, sbl1 partitions (SU5-24).
[Droid Ultra General] shawnsingh:
Ok then why don't you go and do load the firmware and extract it those files are in there.

---------- Post added at 05:13 PM ---------- Previous post was at 05:12 PM ----------

Also SamuriHL had publicly released that file MPRG8960.HEX but I don't know if it is device specific :)
[Droid Ultra General] carbonat87:
These files are not present in current motorola Droid Maxx/Ultra/Mini firmware version and I can't use older firmware files cause firmware downgrade is disallowed by Moto Droid specifications. MPRG8960.HEX is a programming file which is very specific for each device and firmware version.
[Droid Ultra General] shawnsingh:
Why don't you have someone That has a working Maxx mini or ultra generate a de brick img since it is a Qualcomm device it can boot up or ask SamuriHL or Dr.Mario how to get those files they would know.
[Droid Ultra General] carbonat87:
I found newer files for Moto Droid Maxx/Ultra/Mini (in Update to Blur 23.3.23) then files in the topic start.

https://drive.google.com/file/d/0Bz7RkJUhg5ghMmM5U1NnNXltNVk/view?usp=sharing

But it seems I have to use newer version of MPRG8960_MOTO.bin for unbricking.

How can I build it?
[Droid Ultra General] fabioalves357123:
please how do I get the image to the razr hd xt925 I need to test this methododo
[Droid Ultra General] shawnsingh:
Check my forum

---------- Post added at 11:06 PM ---------- Previous post was at 11:06 PM ----------

Might have help on how to build
[Droid Ultra General] RedLedLight:
Well looks like your phone is maxximaly bricked. (Sorry I had to do it).

Just bring it to a service center instead of risking further injury.

*blink*
[Droid Ultra General] buickman94:
How exactly do I run this? I have a 32bit Vista computer and it will not install the drivers given. Forgive me I do not use Python much. Do I need to extract all the files to one folder? If I click on qdload, I see an error, "Too few arguments". Please help.***** Never mind, phone will be sent back under warranty, this same thing happened during a official software update.
[Droid Ultra General] carbonat87:
UnBrick Droid Mini 4.4.4 (SU 5-24/SU 6-7)

Here you can find working files for unbricking Moto Droid Mini on later versions. These files provided via Crash][ from 4pda.ru
[Droid Ultra General] happysteve11c:
This is what I get when I run the code I am pretty sure it's good but how do I flash the stock image

c:\Python27>python qdload.py MPRG8960_MOTO.bin -ptf _maxx/partitions.txt

QDLoad utility version 1.2 (c) VBlack 2014

Found TTY port: com14

Requesting Params...

Params:

Version: 8

Min version: 1

Max write size: 1536 (0x00000600)

Model: 144

Device size: Invalid or unrecognized Flash device, or Flash device progr

amming not supported by this implementation

Device type: Intel 28F400BX-TL or Intel 28F400BV-TL

Requesting SoftwareVersion...

Version: PBL_DloadVER2.0

Requesting SerialNumber...

Serial number: 00,00,48,03

Requesting HW Id...

HW Id: 00,00,48,03,e1,10,7e,00

Requesting PublicKey...

PublicKey: 39,c4,ee,3e,b5,be,eb,87,8e,2f,e3,b8,53,4d,14,6f,91,ca,fd,bb,94,2a,0d

,aa,d0,1e,b0,87,62,d4,b9,b8

Uploading file 'MPRG8960_MOTO.bin' to addr 0x2a000000...

Executing...

Found TTY port: com14

Sending MAGIC ...

QCOM fast download protocol targ:

Version: 7

Compatible version 2

Maximum block size 1024 (0x00000400)

Base address of Flash 0x00000000

Flash: eMMC

Window size: 30

Number of sectors: 128

First sector size: 2097152 (0x00200000)

Feature bits: 09

Sending secureMode...

Sending openMulti ...

Uploading file2 'c:\Python27\_maxx/sbl1.mbn' to addr 0x6420000...

Uploading file2 'c:\Python27\_maxx/sbl2.mbn' to addr 0x6597000...

Uploading file2 'c:\Python27\_maxx/sbl3.mbn' to addr 0x670e000...

Uploading file2 'c:\Python27\_maxx/aboot.mbn' to addr 0x690e000...

Uploading file2 'c:\Python27\_maxx/rpm.mbn' to addr 0x6a85000...

Uploading file2 'c:\Python27\_maxx/tz.mbn' to addr 0x6b02000...

Sending CloseFlush...

Sending SBL Reset...

Done
[Droid Ultra General] carbonat87:
After this operation your Droid must turn into fastboot mode and you can flash only your current or greater version Rom (if your bootloader is locked and you have no root access). If it's still in QDLOAD-9008 mode, you have to provide unbricking package files for your current version firmware. Do you know what version there was before you used BLBROKE?
[Droid Ultra General] happysteve11c:
i reflashed back to 4.2.2 stock using house of moto and was taking an ota to bring it back to 4.4 thats when it happened so i'm assuming 4.2.2 still and i have a developer edition so i'm unlocked
[Droid Ultra General] mr_verystock:
PERFECT!!!

It seems like I have just found a way to downgrade bootloader to 5-24 for Droid Mini and perhaps other phones.

Steps:

1) Read this and follow only the 1-4 steps, which after running BLBROKE.bat, don't do anything.

http://xdaforums.com/showthread.php?t=2669404

2) Now, since you're bricked, run the SUx-xx for yourself, which in my case is SU6-7.zip, so unzip it and run "RUN.bat"

3) Let it run, in a minute or so it'll reboot. Shut your phone down and go to bootloader.

4) Flash the ROM corresponding to the update version. So for me, 5-24 I will download.

PROFIT!!!
[Droid Ultra General] pizmak:
I was thinking of the same exact thing, since we have the images of the boot partitions we could write them to a (intentionally or not) bricked device.

I am only wondering about this: how far back do we need to flash to have sunshine working? will it work with 5-24? Or do e need to go for su4-21?
[Droid Ultra General] carbonat87:
At first I must say that you can only downgrade SU6-7 to SU5-24 cause they have compatible bootloader versions. But you can't downgrade to SU4-21, which is required by Sunshine to work. As I said in the other thread, TrustZone certificates, required by Sunshine, are persistent in SU4-21 but they are gone in greater firmware versions.
[Droid Ultra General] pizmak:
Can You explain why I cannot downgrade to su4-21?

In the bricked state we have got access to the whole flash memory (I assume we do), so why can we not just write the whole bootloader stuff (sbl1-3, aboot, tz, rpm, boot....) from version 4-21 and then the system from su4-21?

The partition table looks identical in all these firmwares: su4-21, su5-24, su6-7
[Droid Ultra General] carbonat87:
Firmware structure is more difficult than you think. The problem is in Motorola signature which is every partition signed by. You can flash earlier version image in qdload mode but it won't run after bootloader check. Bootloader will notify you that firmware version downgrade is dissalowed. Seems version checks are linked to cid partition which is different on every phone model and changes with every upgrade. There's one person on 4pda known as Crash][ and he tried nearly all this things we talk about and continues investigation. He is the first who found downgrade SU6-7 to SU5-24 method.
[Droid Ultra General] pizmak:
Great thanks fro this explanation, it seems clearer to me now :)

for a moment I really thought we could go for su4-21 and unlock this god damn bootloader:crying:
[Droid Ultra General] shawnsingh:
Is there a process for this on the droid razr m
[Droid Ultra General] carbonat87:
Are you asking about unbricking process or unlocking bootloader? Anyway, this is not the thread about Razr M.
[Droid Ultra General] shawnsingh:
I was wondering if there is a unbricking process for the xt907 so it can help my forum.