Database Users

[GUIDE]Flash Android 2.3.4 with Windows x64/x86

Prerequisites
AT&T Atrix 4G with and UNLOCKED bootloader
Windows OS x64/x86
Motorola drivers installed
The .zip file listed below contains all the files you need.
Extract this to the root of you C drive and use the following commands in the listed order, one at a time :
Put your device in Fastboot mode by holding the volume down button while booting then volume up
Open up a command prompt and type( ONE AT A TIME )
cd C:\moto-fastboot
moto-fastboot flash boot atrix-2.3.4-hktw-boot.img
moto-fastboot flash system atrix-2.3.4-hktw-system.img
moto-fastboot -w
moto-fastboot reboot
If you followed the steps correctly you should have Gingerbread 2.3.4 on you AT&T Atrix.
Cheers!
Thanks to romracer for compiling the moto-fastboot-win32.
I made this user friendly guide and compiled the .zip with everything you need.
WARNING
The leaked build from Hong Kong / Taiwan was probably not built for a device that is exactly like ours. Test phones can have different hardware. Don't expect everything to work, it's super-duper beta and since we've all only been unlocked 24hrs no one really knows how usable it is! Flash at your own risk... (PS you can 'Skip' Motoblur just by hitting 'Menu' during setup. It won't connect anyway...)

Guide for ROOT

I'm gonna try that right now

Question how would i do this for windows xp 32bit

Can someone tell me what works / doesn't work when using HKTW 2.3.4? Also curious about the speed and stability of the Atrix when using the rom. Is it ready for daily use or should we wait on something else?

mudd_cat23 said:
Question how would i do this for windows xp 32bit
Click to expand...
Click to collapse
This guide should work, XP 32bit is x86.

dcarpenter85 said:
Can someone tell me what works / doesn't work when using HKTW 2.3.4? Also curious about the speed and stability of the Atrix when using the rom. Is it ready for daily use or should we wait on something else?
Click to expand...
Click to collapse
It can be used as a daily ROM
only the Webtop and Fingerprint read dont work, i believe however there's a fix for the Webtop.
Webtop Fix

XLR88 said:
It can be used as a daily ROM
only the Webtop and Fingerprint read dont work, i believe however there's a fix for the Webtop.
Webtop Fix
Click to expand...
Click to collapse
Thanks for the info, I will have to give it a try.

mudd_cat23 said:
Question how would i do this for windows xp 32bit
Click to expand...
Click to collapse
More than likely it should work on XP/Vista x64/x86 and I can confirm it works on Windows 7 x64/x86.

Sucks to be me, I guess.

Ok flashed and now need to go trough motoblur wizard
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\moto-fastboot-2.3.4\moto-fastboot>moto-fastboot flash boot atrix-2.3.4-hktw-boot.img
sending 'boot' (3358 KB)... OKAY [ 0.347s]
writing 'boot'... OKAY [ 0.704s]
C:\moto-fastboot-2.3.4\moto-fastboot>moto-fastboot flash system atrix-2.3.4-hktw-system.img
sending 'system' (262144 KB)... OKAY [ 27.876s]
writing 'system'... OKAY [ 13.985s]
sending 'system' (65410 KB)... OKAY [ 7.065s]
writing 'system'... OKAY [ 3.377s]
C:\moto-fastboot-2.3.4\moto-fastboot>moto-fastboot -w
erasing 'userdata'... OKAY [ 6.140s]
erasing 'cache'... OKAY [ 2.136s]
C:\moto-fastboot-2.3.4\moto-fastboot>
C:\moto-fastboot-2.3.4\moto-fastboot>moto-fastboot reboot
rebooting...
C:\moto-fastboot-2.3.4\moto-fastboot>

Hmm, what the hell could I be doing wrong?

Interesting.. can't login to moto blur..
It say's
Error signing into account
An error has occurred. Please try again..
I check username and pass several times..

jwhited said:
Sucks to be me, I guess.
Click to expand...
Click to collapse
Flash 1.83 SBF using RSDLite and then try again
Copy and paste the commands one at a time instead of typing to prevent errors.

zexbig said:
Interesting.. can't login to moto blur..
It say's
Error signing into account
An error has occurred. Please try again..
I check username and pass several times..
Click to expand...
Click to collapse
Press Menu->Skip
unless you really want MotoBlur. (and i am sure you are the only one in the world who wants blurrrrrrr). If thats the case, blurrr wont work on this build. Go back to 1.83 or some other official release

zexbig said:
Interesting.. can't login to moto blur..
It say's
Error signing into account
An error has occurred. Please try again..
I check username and pass several times..
Click to expand...
Click to collapse
Forgot to mention, Motoblur does not work......press menu and then select skip on the screen.

This was way to easy.
Thank you!!

Well.. there is new option.. during setup press menu button and select skip setup..
It will skip moto blur setup and disable locate my phone trough moto blur but that's about it

Where do we put the root commands?
/preinstall/dosu
/bin/mount -o remount,rw /system
cp /preinstall/su /system/bin/
PATH=/system/bin:$PATH pm install /preinstall/Superuser.apk
Click to expand...
Click to collapse

XLR88 said:
Flash 1.83 SBF using RSDLite and then try again
Copy and paste the commands one at a time instead of typing to prevent errors.
Click to expand...
Click to collapse
Hmm, I did start from a 1.83 SBF (from a different source, mine was a .7z file.. Worked just the same, though.) I'll try the one from your link, and go from there.
Should just need to flash SBF, unlock, and go, right?

[GUIDE] to enable DualSim on SingleSim Devices

WARNING: I am not responsible for damage to your phone through this guide, follow at your own risk.​
Its only tested on EU Singlesim devices!!!! ​
First of all, thanks to @ilovemeow and @tomparr ! :good:
We all know, it was on the Moto X Play easy to "unlock" the DualSim ability by flash a firmware with including a DSDS Baseband. But Moto changed the Firmware layout. On the Moto Z Play are all basebands in the /fsg folder and after a modem wipe (dualsim=true or false) loads the matching baseband to modemst1 and modemst2. The settings for dualsim=true and the software channel are not editable right now.
So the trick is to get the baseband for dualsim in to the modem. I found a easy but dirty way to get the DSDS baseband loaded.
You need a Moto Z Play SingleSim Device (Mine is from Germany with RETEU)
Now the step by step guide:
1. boot in to twrp open the terminal and type
Code:
setprop persist.radio.multisim.config dsds
(thx to @ilovemeow again )
2. boot and make sure you got the Dualsim options in the Settings. If yes goto 3. If not load a Terminal Emulator from playstore and type there the command from 1.
3. Got to the settings and look which baseband you use now! Its important to note that!!
3. Open the RootExplorer and navigate tot he fsg Folder. You will find there a bunch of im.gz files (like addison_2.img.gz and addison_dsds_2.img.gz and so on…)
4. You must make sure which file for your phone is the right one (For the EU Phones its Addison_ROW and addisson_2.img.gz) You will see that the numbered files are linked to the other file in the folder. See the Picture.
5. Now you have to delete the baseband your phone use normally. At the EU Devices addisson_2.img.gz and addisson_row.img.gz
6. Now comes the magic! xD Just rename the dsds files from addisson_dsds_2.img.gz to adisson_2.img.gz and addison_dsds_row.img to addison_row.img.gz.
7. Reboot to bootloader and enter
Code:
fastboot erase modemst1
fastboot erase modemst2
fastboot erase cache
fastboot reboot
now you can use both cards! :highfive: :victory:
NOTES:
1. there some bugs in the dialer! You cant save the settings that a specific number automatic called by sim1 or sim2
2. Second SIM Card/Modem only got IMEI 0! But works in German Networks without a problem.
3. You can loose your of sim1/modem IMEI if you do something wrong!
4. You got a bit more battary drain.
5. You can restore the default settings with just flashing the fsg.mbn file!
If you like my work give me adfree or buy me a beer

---- reserved -----

WOW
Thanks a lor for your work, bro.
I will to try today night.
Thanks again!

Can you confirm the command in your first "code" box is actually supposed to be "steprop" and not SETPROP?
Thanks for figuring this out - if I ever decide to unlock, I'll be giving it a shot!

Arg wrong typo thx

Thank you. It worked!

hassanfarroq92 said:
Thank you. It worked!
Click to expand...
Click to collapse
What Software channel is your device?
@all If you got it working on your device, let us know!

-=MoRpH=- said:
What Software channel is your device?
@all If you got it working on your device, let us know!
Click to expand...
Click to collapse
Retgb

? thanks mate, actually thats was thr idea of someone in x play forum
btw I cant find any files in /fsg folder

ilovemeow said:
? thanks mate, actually thats was thr idea of someone in x play forum
btw I cant find any files in /fsg folder
Click to expand...
Click to collapse
Did u use the "RootExplorer? https://play.google.com/store/apps/details?id=com.speedsoftware.rootexplorer

Total Commander should work also and is free of cost and ads. You may want to try this one first.

tag68 said:
Total Commander should work also and is free of cost and ads. You may want to try this one first.
Click to expand...
Click to collapse
I didn't try totalcommander, because I had fear loosing the links between the files. If that happen, the baseband couldn't be loading right and you got no signal on both cards.

-=MoRpH=- said:
Did u use the "RootExplorer? https://play.google.com/store/apps/details?id=com.speedsoftware.rootexplorer
Click to expand...
Click to collapse
it's look ok now, it take 15sec to load those file
---------- Post added at 07:44 PM ---------- Previous post was at 07:43 PM ----------
trying to reboot now, let's see in 2mins
---------- Post added at 07:46 PM ---------- Previous post was at 07:44 PM ----------
all working thank mate,
so this trick needed to root

Anyone with build.prop from native dualsim device?

Only camera is giving issues reset is working as it should.
I'm getting restart error

How can the second phone line work without IMEI?

Many networks don't have IMEI Checks, so you can use it with a 0 IMEI.

-=MoRpH=- said:
Did u use the "RootExplorer? https://play.google.com/store/apps/details?id=com.speedsoftware.rootexplorer
Click to expand...
Click to collapse
yyp
and es explorer pro can do as well

left native dualsim, retapac
right reteu
and the 2nd pic, both sim lose imei, dont give a shxx as long as both sim work

ilovemeow said:
left native dualsim, retapac
right reteu
and the 2nd pic, both sim lose imei, dont give a shxx as long as both sim work
Click to expand...
Click to collapse
??
Did you loose the IMEI because of the dualsim mod?

dump moto g4 play

Anyone from xda who has this moto g4 play could backup this partition mmcblk0 from now thank you
adb shell su -c dd if=/dev/block/mmcblk0 of=storage/sdcard1/fulldump.img

mmcblk0 is not a partition. which are you looking for?
the partitions are labelled mmcblk0p1 through mmcblk0p41

Dump moto g4 play
So backup all partitions and send me a zip since thank you brother

There is no way I'm dumping my entire phone for you. That would include my ram, data, etc...all sorts of private, sensitive information, like my google login, persist partition, with my encryption....no way, no how!!!
You tell me what partitions you need, and I'll upload any you need that don't contain sensitive data.
You must be crazy, though, if you think I'm giving you a 100% complete dump!!

Dump moto g4 play
I'm sorry brother, I just want the partitions here.

I already told you, the persistent partition, among others you've selected, contain sensitive data. You should not be asking for those, and if you know how to work with the img files you are requesting, you should already know that. I'm not uploading anything for you, because you seem to be after stuff you shouldn't be.

hp420 said:
You must be crazy, though, if you think I'm giving you a 100% complete dump!!
Click to expand...
Click to collapse
For real!
What planet is he on?

Dump moto g4 play
And to unbrick cell phone that does not connect ta in qualcomm mode hs-USB qdloader 9008

http://www.droidsavvy.com/unbrick-qualcomm-mobiles/

tecnologianet2 said:
http://www.droidsavvy.com/unbrick-qualcomm-mobiles/
Click to expand...
Click to collapse
you need to buy a new g4 play. then you can dump what you need and simply resell it. NO ONE should ever ask anyone else to dump all partitions from their device and upload them. And if anyone here does it for you, they are looking for trouble!!

Dump moto g4 play
The only file that can revive mobile phone and this most accurate blankflash from the singleimage file for the moto g4 play

and what's stopping you from buying a new one, dumping what you need, using that dump to revive your brick, then selling one of the two you own?? nothing.
now stop asking everyone for their sensitive, personal data! i have already reported this thread. you are in violation of site rules by asking for the stuff you have. now stop, and please don't ask again. no one is going to give you a full dump here.

ATTENTION:
If or when you copy ANYTHING from your device to give to another user, BE CERTAIN that you know exactly what you are doing, exactly what information you may be handing over, and exactly what personal data you may be exposing to exploitation.
You are solely responsible for what you do with your data, and/or your device.

How do I close this topic?

Closed per OP request

[GUIDE] Unbrick MOTO Z Play (not working yet)

work in progress! (not working yet)
Current status: does not work (but should!), exact reason unknown (to me).
If you managed to "brick" your MOTO Z Play it enters a fail-safe mode as a last resort provided by the chipset manufacturer (Qualcomm). There are packages out there called "blank-flash" that use this mode to restore a proper bootloader that in turn re-enables the use of the fastboot method to write the other flash files and restore full operation - provided the personalized partitions are still present and in good health (or you have a backup of them at hand).
Look at this thread and download the Nougat file. It contains "blank-flash" files. These "should work" but they don't (any more). As I don't have a Z Play, I cannot research the matter myself and instructing helpful others via email exchange is ... complicated.
The thing with failing updates/flash packages is that they usually fail because they do not allow downgrading - even if they allow downgrading of some sort (e.g. OS), they may limit downgrading the second stage bootloader, the signed GPT (partitioning table) etc. As I don't know if and what's the case with the Z Play, I just assumed that *if* it works, it may require the most recent files.
If you run the blank-flash files (qboot) with --debug=2 option you see that after the programmer code is sent to the phone it doesn't send a valid / expected response and ultimately causes the process to fail.
There are many programmer files out there. Most do not work, because they need to be digitally signed with the proper keys. Some are signed with Quallcomm-keys, some with Lenovo-, Motorola- and other with test-keys. And then again, they have to fit with the qboot program that's sending the data to be flashed.
A blankflash archive consists of the following files:
qboot, blank-flash.sh ; Linux
qboot.exe, qboot.dll, blank-flash.bat ; Windows
singleimage.bin ; Both
There are different versions of the qboot program. I've found the versions 2.4, 3.37 and 3.40.
The file "singleimage.bin" contains the flash files and directions crammed into a single file, thus the name:
cmnlib.mbn
cmnlib64.mbn
devcfg.mbn
emmc_appsboot.mbn
gpt_main0.bin
index.xml
keymaster.mbn
programmer.mbn
prov.mbn
rpm.mbn
sbl1.mbn
singleimage.default.xml
singleimage.pkg.xml
tz.mbn
The XML files contain the instructions (the 'recipe'):
index.xml:
Code:
<?xml version="1.0"?>
<index>
<board id="70" name="MSM8953" storage.type="eMMC"/>
<package compatible="cpu.name:MSM8953 protocol:qboot" filename="singleimage.pkg.xml"/>
</index>
singleimage.pkg.xml:
Code:
<?xml version="1.0"?>
<package>
<programmer filename="programmer.mbn"/>
<recipe filename="singleimage.default.xml"/>
</package>
singleimage.default.xml:
Code:
<?xml version="1.0" ?>
<recipe>
<configure MemoryName="eMMC"/>
<!-- Flash GPT -->
<print what="Flashing GPT..."/>
<flash partition="partition:0" filename="gpt_main0.bin" verbose="true"/>
<print what="Re-initializing storage..."/>
<storage operation="reinit"/>
<!-- Flash bootloader -->
<print what="Flashing bootloader..."/>
<flash partition="aboot" verbose="true" filename="emmc_appsboot.mbn"/>
<flash partition="rpm" verbose="true" filename="rpm.mbn"/>
<flash partition="tz" verbose="true" filename="tz.mbn"/>
<flash partition="devcfg" verbose="true" filename="devcfg.mbn"/>
<flash partition="cmnlib" verbose="true" filename="cmnlib.mbn"/>
<flash partition="cmnlib64" verbose="true" filename="cmnlib64.mbn"/>
<flash partition="keymaster" verbose="true" filename="keymaster.mbn"/>
<flash partition="prov" verbose="true" filename="prov.mbn"/>
<flash partition="sbl1" verbose="true" filename="sbl1.mbn"/>
</recipe>
These files usually do not need to be modified.
programmer.mbn is the flash application that is sent to the phone.
I've compiled the following package, including all the qboot executables:
http://frickelbude.net/moto/blankflash[addison][D61DC5C7][25.211.10][1.07][2017-04-13].zip
D61DC5C7: crc32-checksum of programmer.mbn file (original, motorola signed) (find others here)
25.211.10: firmare package origin of the bootloader files
1.07: bootloader version
2017-04-13: time stamp of bootloader file
This didn't work with recently bricked Z Play phones as some testers confirmed. We also tried all the different programmer executables linked above just to be sure but no luck.
Outlook: you may want to try out Qualcomms QFIL (part of QPST package) (look e.g. at the download section of androidbrick).
However, that requires some handywork - you need to build some XML files, provide the proper programmer file etc. Maybe grab a firmware package e.g. for a Xiaomi phone that has all these files and try and deduce a proper layout for your Z play... and hope, any of the programmer files will actually run and communicate with the pc end.
(Usually the blank-flash files operate in 'sahara' mode/protocol and send the programmer.mbn to the phone. Then it waits for a positive response from the phone to enter 'firehose' mode in order to send all the flash data...)
/update 2017-06-10 a
I've created a blank-flash package based on the files @lozada81 linked below:
bootloader files extracted from: OTA tester Android 7.1.1 BRASIL patch june - Blur_Version.26.1.22.addison.retail.en.US.zip
blank-flash package: http://frickelbude.net/moto/blankflash[addison][D61DC5C7][26.1.22][C1.12][2017-05-22].zip
(Bootloader version: C1.12, GPT layout version: 0x000A)
/update 2017-06-10 b
Same package as above, but with a different programmer.mbn, taken from an older blank-flash package that came with an Android 6.0.1 package @lozada81 linked below.
http://frickelbude.net/moto/blankflash[addison][C0A0D740][26.1.22][C1.12][2017-05-22].zip
Well, it either fails with the infamous io-error or it finally works.. please test & report back!

Thanks OP for putting this together. I hope someone can help get what we need (someone smarter than me ). I've had to go back to my Nexus 6P, but the battery life is just horrid. I ended up ordering another Moto Z Play online. This time I'm going to keep the bootloader locked, keep the stock software, etc. I might be done with the rooting/flashing part of my life.

Moto Z Play Brick
Good afternoon.
I am from Brazil and I have a Moto Z Play XT1635-02 and downgraded from Android 7 to 6 and until then, I did the bootloader, root and installed TWRP and followed dowgrade procedures.
The problem happened after the downgrade removed the root I reinstalled the original recovery and downloaded through the mobile the update of the android January 7 via ota and after downloading began the installation and when restarting the cell phone he died and did not call any more and when connecting On the computer only the message in the device manager "Qualcomm HS-USB QDLoader 9008" no solution for now to resuscitate the device?
If someone has the solution and can help, thank you.

giba_11 said:
Good afternoon.
I am from Brazil and I have a Moto Z Play XT1635-02 and downgraded from Android 7 to 6 and until then, I did the bootloader, root and installed TWRP and followed dowgrade procedures.
The problem happened after the downgrade removed the root I reinstalled the original recovery and downloaded through the mobile the update of the android January 7 via ota and after downloading began the installation and when restarting the cell phone he died and did not call any more and when connecting On the computer only the message in the device manager "Qualcomm HS-USB QDLoader 9008" no solution for now to resuscitate the device?
If someone has the solution and can help, thank you.
Click to expand...
Click to collapse
Same with my case

Definitely going to be watching this thread. Thank you.
Sent from my SM-G955U using Tapatalk

AC
I also have my Z play stopped = (

Thanks for putting those info together, keep fingers crossed
Sent from my XT1650 using Tapatalk

Fingers crossed! Same thing with me!

I have this problem too, I'm refreshing that lenovo russian forum every 5 minutes, I'm desperate!

firmware android 7.0 update abril - compilation version NPNS25.137-24-1-9
https://www.androidfilehost.com/?fid=961840155545567726
OTA Blur_Version.25.231.4.addison.retail.en.US brasil patch may
http://motorola.erfanabdi.ir/index.....25.211.10.addison.retail.en.US&carrier=retbr
OTA tester Android 7.1.1 BRASIL patch june - Blur_Version.26.1.22.addison.retail.en.US.zip
https://drive.google.com/file/d/0B-9vIY9eZnVqY3BGM0NUdTdsclE/view
I hope util

lozada81 said:
OTA tester Android 7.1.1 BRASIL patch june - Blur_Version.26.1.22.addison.retail.en.US.zip
https://drive.google.com/file/d/0B-9vIY9eZnVqY3BGM0NUdTdsclE/view
Click to expand...
Click to collapse
I've compiled a new blank-flash package in case anyone would like to try it out (see update in 1st post).
However, I doubt it will work better than the other files. If it keeps on failing with:
Code:
FAILED: qb_flash_singleimage()->sahara_download()->IO error
then there's still something wrong with the communication between qboot and the programmer file. I.e. we would need a programmer file that works with more recent bootloader revisions.
(I assume that the blank-flash packages out there did actually work at some time in the past).

benzinerwin said:
I've compiled a new blank-flash package in case anyone would like to try it out (see update in 1st post).
However, I doubt it will work better than the other files. If it keeps on failing with:
then there's still something wrong with the communication between qboot and the programmer file. I.e. we would need a programmer file that works with more recent bootloader revisions.
(I assume that the blank-flash packages out there did actually work at some time in the past).
Click to expand...
Click to collapse
Where is the Download link ??

giri.shiva said:
Where is the Download link ??
Click to expand...
Click to collapse
People who can't read aren't supposed to download, sorry. It's too dangerous, they could flash something without knowing what it does.
Ok, I'll give you a hint: search for update and 1st post
Edit: no, not in the thread. Only in your quote.

giri.shiva said:
Where is the Download link ??
Click to expand...
Click to collapse
Ok, I'll give you a hint: search for update and 1st post

tag68 said:
People who can't read aren't supposed to download, sorry. It's too dangerous, they could flash something without knowing what it does.
Ok, I'll give you a hint: search for update and 1st post
Edit: no, not in the thread. Only in your quote.
Click to expand...
Click to collapse
I tried those already
I thought you had updated another blankflash file
No offense

benzinerwin said:
I've compiled a new blank-flash package in case anyone would like to try it out (see update in 1st post).
However, I doubt it will work better than the other files. If it keeps on failing with:
Code:
FAILED: qb_flash_singleimage()->sahara_download()->IO error
then there's still something wrong with the communication between qboot and the programmer file. I.e. we would need a programmer file that works with more recent bootloader revisions.
(I assume that the blank-flash packages out there did actually work at some time in the past).
Click to expand...
Click to collapse
in this pic, we see error do package, do recipe, do configure, buffer read , this with two firmware of lenovo.ru
https://www.mediafire.com/?eichzw02lsc9kyd
Master, firmware contain blankflash in mbm folder and work programmer until package error or work more that Previous
firmware Oficial XT1635-02_7.0_NPN25.137-24-1 - i n mbm folder blankflash file
https://cloud.mail.ru/public/HoLU/D1tHfMFQY
this two firmware contain blankflash in mbm folder and work programmer until package
firmware Oficial XT1635-02_7.0_NPN25.137-24-1
firmware XT1635-02_6.0.1_MPN24.104-44_47
http://lenovo-forums.ru/files/category/140-moto-z-play/

Thanks for the links. Actually, the older package...
lozada81 said:
firmware XT1635-02_6.0.1_MPN24.104-44_47
Click to expand...
Click to collapse
...did contain an old (duh..!) blank-flash package but also wrapped up with a different programmer.mbn, that I didn't know of before. Maybe you give this a try. I've repacked a blank-flash with this programmer.mbn and the most recent bootloader files (see update in 1st post)...

benzinerwin said:
Thanks for the links. Actually, the older package...
...did contain an old (duh..!) blank-flash package but also wrapped up with a different programmer.mbn, that I didn't know of before. Maybe you give this a try. I've repacked a blank-flash with this programmer.mbn and the most recent bootloader files (see update in 1st post)...
Click to expand...
Click to collapse
Very much to the cortrario, you are using your valuable time, your great knowledge and your ability to help us out of this huge bache called blankflash since update android 7.0 April update, unfortunately I leave my device at home and until late hours can test.
* But the other partners help them by testing and reporting their results to make it easier and faster the info required @benzinerwin

benzinerwin said:
Thanks for the links. Actually, the older package...
...did contain an old (duh..!) blank-flash package but also wrapped up with a different programmer.mbn, that I didn't know of before. Maybe you give this a try. I've repacked a blank-flash with this programmer.mbn and the most recent bootloader files (see update in 1st post)...
Click to expand...
Click to collapse
Thanks for your amazing work, Unfortunately, this package doens't work either. I get ERROR: do_package()->do_recipe()->do_configure()->buffer_read()->device_read()->IO error

hanks for your support
benzinerwin said:
Thanks for the links. Actually, the older package...
...did contain an old (duh..!) blank-flash package but also wrapped up with a different programmer.mbn, that I didn't know of before. Maybe you give this a try. I've repacked a blank-flash with this programmer.mbn and the most recent bootloader files (see update in 1st post)...
Click to expand...
Click to collapse
First of all I thank you for the help provided as well as your time, I commented that I have the 2 files that I uploaded today and in both I get the following
FAILED: qb_flash_singleimage()->do_package()->do_recipe()->do_configure()->buffer_read()->device_read()->IO error

[CLOSED] My BOOTLOADER is locked and I cannot flash firmware

Hi, recently I realized that my device has the bootloader locked and I cannot flash the firmware through Fastboot Flash Mode (Secure). When I try to unlock it taking in mind the Motorola site instructions and entering the fastboot oem get_unlock_data command it throws me this error:
(bootloader) Unlock data:
(bootloader) read datablock error
(bootloader) Failed
OKAY [ 0.040s]
finished. total time: 0.041s
I lost my IMEI and I don't know if that's interfering when trying to unlock bootloader. Can someone please tell me what's happening?
Thx for reading.

[CLOSED]
Caney said:
Hi, recently I realized that my device has the bootloader locked and I cannot flash the firmware through Fastboot Flash Mode (Secure). When I try to unlock it taking in mind the Motorola site instructions and entering the fastboot oem get_unlock_data command it throws me this error:
Click to expand...
Click to collapse
Please do NOT create duplicate threads.
Please read the Forum Rules.
This one applies here:
5. Create a thread topic or post a message only once, this includes external links & streaming media.
As a large forum, we don't need unnecessary clutter. You're free to edit your message as you like, so if you do not receive an answer, revisit your message and see if you can describe your problem better. Not everyone is online at the same time so it might take a while before you receive an answer.
You can bump your unanswered question once every 24 hours
Duplicate threads and posts will be removed
Always post in an existing thread if a topic already exists, before creating a new thread.
Use our search function to find the best forum for your device.
Links to an external source are only allowed if relevant to the topic in hand. A description must be included, no copy & pasting from the original source.
Self-promotion is forbidden, this includes blogs, social media and video channels etc. Random links will be removed.