Hello guys,
Like many of you my Moto G XT1068 is dead because of downgrading from XT1069 MM 6.0 SOAK test Firmware to 4.4.4 and OTA update to 5.0.2 leaving it to "QualComm Emergency Download Mode" a.k.a Qualcomm Hs Usb Qdloader 9008 . For past several days I was experimenting with Blank-Flash Method available for Moto G (1st gen only). I am a full Linux/Ubuntu Guy. What I have found is that there are two files to construct, Programmer.mbn and Singleimage.bin for XT1068.
I am experimenting with possible replacement of SBL1 in Programmer.mbn and tz, rpm, DDR,and SBL1 partitions found in the singleimage.bin. But what I don't know as my device is hard-bricked is the full partition layout.
Is there anybody (rooted) willing enough to give the following info+dump of partition layout for XT1068 variant then I can try to integrate it those two files.
What you need to do is simple enough, just follow the instructions:
Requirements: Rooted XT1068
App: Partitions Backup & Restore
Instructions:
Start the app with root permission.
Backup All the partitions except SYSTEM (If you have enough space)
Upload the partitions to somewhere (If possible try Mega or Google Drive for faster speed)
Provide Screenshots of the partitions from that app screen.
You can also create 100mb of partitions dump. Click on the options in the app and click "Backup first partitions".
Please mention which Firmware you are using for instance 4.4.4 or 5.0.2 or 6.0, If possible give a Screenshot of Settings >> "About device".
If you know how to use adb then please provide the partition info, follow this wonderful instructions from this XDA thread [GUIDE] Making Dump Files Out of Android Device Partitions. Provide Screenshots like this post and if possible you can also provide me the dump data.
PS:
## I know the programmer.mbn and singleimage.bin is checksum protected, I will try to look into that later.
## Its quite impossible to accomplish what I am trying to do to help me and so many of other left there device as a paper weight, but you will never know if you don't try.
## Please don't raise your hope yet and please comment only technical info if you wanna help, so that moderator won't close this thread.
## This is my first post, so If I break any posting rules, forum moderator please let me know and If it is on wrong forum then move this thread to the right one.
I am looking forward to your help. Thanks in advance.
[Reserved]
I will post my findings related to blank-flash in future here.
UPDATE: 1
Creating singleimage.bin is easy enough. Its basically a gtp partition disk image with four patitions - Aboot, DDR, tz and rpm. If you have linux(ubuntu/Centos) editing this partition to include Aboot(emmc_appsboot), tz and rpm from OTA(4.4.4/5.0.2/6.0) update of Moto G 2014 is easy enough using gdisk tools in linux. I have already created that but the problem is that qboot utility doesn't pass to send singleimage.bin to phone. If anyone want I will give a full guide to create singleimage.bin.
Problem: The main problem is creating the programmer.mbn file. Recreating it is quite impossible if we don't get it from leak. I guess the existing programmer.mbn from Moto G (1st gen) is that it possibly check for bootloader, device id etc. There are a lot of posts about these topics in XDA, If anyone interested just search for the keywords singleimage.bin, mprg8226, Sahara protocol, PBL, Qualcomm qDloader 9008 commands etc.
Status:
with all the informations I gathered this week is that the unbricking a Hard-Brick Qualcomm device process is like follows:
flasher send the Flash Programmer (file) to phone in 9008 mode.
send signal to restart(possibly) phone and execute Flash Programmer (programmer.mbn in our case). It is a bootloader for rescuing phone to flash gpt partion containing second bootloader SBL1 and fastboot in aboot partition.
If you want to see what exactly is sent to your phone and the response the moto g gives after using qboot, use this command to execute qboot:
In Windows (Edit blank-flash.bat )
qboot.exe --debug=2 blank-flash
pause
In Ubuntu (from terminal)
./qboot --debug=2 blank-flash
you will see in the verbose debug output that phone stuck at executing programmer.mbn before accepting singleimage.bin.
Linux guy here too.
So, roughly you want to know every partition's size and content to make a new partition table? Dumping every partition with adb should be relatively easy. I'd like to help you, but I'm on Minimal OS 5.1.1, XT1063, with Lollipop bootloader. I don't know if the hardbrick problem is only related to XT1068 phones though, as I tried before to downgrade to kitkat's bootloader and nothing happened.
[HELP] Need Partition Layout Info+Dump of XT1068 for re-creating blank-flash
Hello
I have a blocked xt1068. And I want to participate, I start working with Qualcomm QPST.
I'm missing some information for a used wisely.
I am French. sorry for bad English.
DepressedDead said:
Linux guy here too.
So, roughly you want to know every partition's size and content to make a new partition table? Dumping every partition with adb should be relatively easy. I'd like to help you, but I'm on Minimal OS 5.1.1, XT1063, with Lollipop bootloader. I don't know if the hardbrick problem is only related to XT1068 phones though, as I tried before to downgrade to kitkat's bootloader and nothing happened.
Click to expand...
Click to collapse
hardbrick problem is not related to XT1068. It happened for Moto G(1st gen also) also for downgrading from Lolliop => Kitkat or MM => Kitkat then OTA update to Lollipop. I looked at the OTA, contains bootloader update and gpt partition. maybe updating a bootloader through OTA from a downgrade caused the problem though sounds silly.
previously I flashed XT1063 Lollipop SOAK test to my XT1068 and it worked like charm, though I didn't flash the bootloader. SO, I think it wouldn't be much problem to use XT1063's partition layout. I guess they wouldn't be much different.
If you have time please provide me your partition info + dump. At least I would get some idea about the gpt partition map
Finger Slensh said:
Hello
I have a blocked xt1068. And I want to participate, I start working with Qualcomm QPST.
I'm missing some information for a used wisely.
I am French. sorry for bad English.
Click to expand...
Click to collapse
QPST won't work I guess. LG, ONEPLUS, HTC have same mechanism but motorolla have different implementation of Qualcomm emergency download mode. Read these links are useful.
http://www.androidbrick.com/ultimate-qualcomm-snapdragon-unbrick-guide-snapdragons-are-unbrickable-qhsusb_dload/
and
http://www.androidbrick.com/unbrick-all-qualcomm-snapdragons-from-qualcomm-hs-usb-qdloader-9008-if-you-have-the-right-kind-of-rom-qhsusb_dload/
@kernelpanic.bd
There's some info about the partitions. I'll upload 34 (out of 39) images of almost every partition in a few hours, or maybe minutes. Except for recovery, userdata, system, boot, and cache. Ya' know, they're pretty useless since there are already images of those partitions, although if you want I could upload them (it would take me an eternity), or you could ask to someone else with better bandwith to dd those partitions since they're pretty large (500mb+).
Please hold on.
[EDIT]
What I've backed up: abootBackup, aboot, cid, clogo, ddr, deviceinfo, dhob, fsc, fsg, ftmlog, hob, kpan, logo, logs, misc, modem, modemst1, modemst2, padA, padB, pds, persist, rmp, rpmBackup, sbl1, sdi, sdiBackup, sp, ssd, tz, tzBackup, utags, utagsBackup, mmcblk0rpmb (this one isn't shown in parted).
What I didn't back up: boot, cache, recovery, system, userdata
Here's the link.
Please note that even if the .tar.gz is only around 25mb it'll be 130mb once you extract it. I've added detailed outputs in .txt files and a checksums.md5 file, so don't forget md5sum -c checksums.md5 to check all the files. As I don't know which extension should be used for every partition I left them all without extension, which I don't think that could be a big deal. If it is, then I'll be using FlashFire (I didn't use it because it only shows 20 partitions, when really there are more than 39 in our device).
If there's any corrupted dd'ed file please tell me.
More info: XT1063, Minimal OS 5.1.1, Lollipop bootloader.
DepressedDead said:
@kernelpanic.bd
There's some info about the partitions. I'll upload 34 (out of 39) images of almost every partition in a few hours, or maybe minutes. Except for recovery, userdata, system, boot, and cache. Ya' know, they're pretty useless since there are already images of those partitions, although if you want I could upload them (it would take me an eternity), or you could ask to someone else with better bandwith to dd those partitions since they're pretty large (500mb+).
Please hold on.
[EDIT]
What I've backed up: abootBackup, aboot, cid, clogo, ddr, deviceinfo, dhob, fsc, fsg, ftmlog, hob, kpan, logo, logs, misc, modem, modemst1, modemst2, padA, padB, pds, persist, rmp, rpmBackup, sbl1, sdi, sdiBackup, sp, ssd, tz, tzBackup, utags, utagsBackup, mmcblk0rpmb (this one isn't shown in parted).
What I didn't back up: boot, cache, recovery, system, userdata
Here's the link.
Please note that even if the .tar.gz is only around 25mb it'll be 130mb once you extract it. I've added detailed outputs in .txt files and a checksums.md5 file, so don't forget md5sum -c checksums.md5 to check all the files. As I don't know which extension should be used for every partition I left them all without extension, which I don't think that could be a big deal. If it is, then I'll be using FlashFire (I didn't use it because it only shows 20 partitions, when really there are more than 39 in our device).
If there's any corrupted dd'ed file please tell me.
More info: XT1063, Minimal OS 5.1.1, Lollipop bootloader.
Click to expand...
Click to collapse
You completely rock . Yes, I don't need cache, recovery, system, userdata but if possible please upload boot.img, motoboot.img and gpt.bin of the firmware you flashed and using now.
bro issue the parted command on mmcblk0
parted /dev/block/mmcblk0
then in the parted menu write "p" to print partition layout with size info and gimme an screenshot of that or the output in a text file. I will possibly update my post with my theory and screenshots of my findings maybe tomorrow or the next day. Thanks again, much appreciated.
If you guys get this right and fix all these bricked xt1068 phones I'll give you a million thanks here !!
@kernelpanic.bd
I used this to update my bootloader, then flashed again the whole stock 4.4.4 rom because there was no mobile signal. What's strange is that it didn't let me downgrade the bootloader and there was a warning about mismatched partitions (idk), but the bootloader was indeed updated.
https://mega.nz/#F!wtlQGQoK!bOrNQEpvYzIKmB68V3qPEg!58tSmQyI
boot (KK), motoboot (KK), gpt.bin (KK) from my stock 4.4.4 carrier rom used to recover mobile signal + current dde'ed boot image.
https://mega.nz/#!y9xCWYgL!6d8biMw1OXOjJqr-wyEgUI2P2grYJiEJX7rnx2bYEFY
Thanks. Downgrading to 4.4.4 doesn't create any issue. If you then upgrade to 5.0.2 through ota that's cause the hradbrick. Mine was fine flashing 4.4.4 from 6.0 xt1069 SOAK test fw. But when I update from 4.4.4 to 5.0.2 ota through the default recovery, it was hard bricked.I guess the bootloader and gpt.bin in the 5.0.2 OTA causes this issue.
kernelpanic.bd said:
Thanks. Downgrading to 4.4.4 doesn't create any issue. If you then upgrade to 5.0.2 through ota that's cause the hradbrick. Mine was fine flashing 4.4.4 from 6.0 xt1069 SOAK test fw. But when I update from 4.4.4 to 5.0.2 ota through the default recovery, it was hard bricked.I guess the bootloader and gpt.bin in the 5.0.2 OTA causes this issue.
Click to expand...
Click to collapse
I concur completely.. That's exactly what happen to my phone too.
same
garyben60 said:
I concur completely.. That's exactly what happen to my phone too.
Click to expand...
Click to collapse
I'm in the same case
I found files here ....but they are moto g 2013
https://mega.nz/#!rgoSGS7B!d2LKiBm29aSSy9dYxy-4aQutjcA5Vwy6bcAE9Sh3nLY https://mega.nz/#!rgoSGS7B!d2LKiBm29aSSy9dYxy-4aQutjcA5Vwy6bcAE9Sh3nLY
updated my findings in the second post.
kernelpanic.bd said:
updated my findings in the second post.
Click to expand...
Click to collapse
.. Sorry I saw one update on #2. Is there anything further? I Wish I knew more about this so I could also help
when you guys solve the problem . can tell me ? My gmail- [email protected] thank you...
no solution......
We still waiting :crying::crying::crying:
http://www.droidsavvy.com/unbrick-qualcomm-mobiles/
kernelpanic.bd said:
updated my findings in the second post.
Click to expand...
Click to collapse
plz check out this link bro.. is it working for xt1068 or not..?
and jst wanted to know that are u still working for the blankflash or started waiting for a superman to come with a solution jst like us
c_/\/\_k said:
plz check out this link bro.. is it working for xt1068 or not..?
and jst wanted to know that are u still working for the blankflash or started waiting for a superman to come with a solution jst like us
Click to expand...
Click to collapse
Not working for my moto g.
Good luck guys.
I hope they get a solution, my case was that too, to soak 6.0 4.4.4 downgrade.
Hi
I have been following the thread for the linage os in the View 10 forum.
Several people have reported it working on Honor 9 Lite which is treble compatible, before I try it out however I wanted to be sure I could go back to my current rom which is the official LLD-L31 for the UK honor 9 lite.
My current build number is LLD-L31 8.0.0.121(C432)
What options do I have to restore if I don't like the rom I flash?
So far I have managed to pull the System & ODM folders to my pc. all except the Vendor file due to a permissions error.
Is this enough? Can I simply push these folders back? and at which point do I attempt the push? When booted/in recovery etc?
Otherwise, Is there an official or unofficial Huawei/Honor restore tool? or maybe a full rom I can flash? HiSuite says it has this function, but my device isn't listed.
Sorry for all the questions, it's been a while since I flashed a rom & it was always via TWRP I understand treble roms are flashed via the stock recovery though
jusumgeezer said:
Hi
I have been following the thread for the linage os in the View 10 forum.
Several people have reported it working on Honor 9 Lite which is treble compatible, before I try it out however I wanted to be sure I could go back to my current rom which is the official LLD-L31 for the UK honor 9 lite.
My current build number is LLD-L31 8.0.0.121(C432)
What options do I have to restore if I don't like the rom I flash?
So far I have managed to pull the System & ODM folders to my pc. all except the Vendor file due to a permissions error.
Is this enough? Can I simply push these folders back? and at which point do I attempt the push? When booted/in recovery etc?
Otherwise, Is there an official or unofficial Huawei/Honor restore tool? or maybe a full rom I can flash? HiSuite says it has this function, but my device isn't listed.
Sorry for all the questions, it's been a while since I flashed a rom & it was always via TWRP I understand treble roms are flashed via the stock recovery though
Click to expand...
Click to collapse
Search for Huawei ERecovery you may find something useful..
jusumgeezer said:
Hi
I have been following the thread for the linage os in the View 10 forum.
Several people have reported it working on Honor 9 Lite which is treble compatible, before I try it out however I wanted to be sure I could go back to my current rom which is the official LLD-L31 for the UK honor 9 lite.
My current build number is LLD-L31 8.0.0.121(C432)
What options do I have to restore if I don't like the rom I flash?
So far I have managed to pull the System & ODM folders to my pc. all except the Vendor file due to a permissions error.
Is this enough? Can I simply push these folders back? and at which point do I attempt the push? When booted/in recovery etc?
Otherwise, Is there an official or unofficial Huawei/Honor restore tool? or maybe a full rom I can flash? HiSuite says it has this function, but my device isn't listed.
Sorry for all the questions, it's been a while since I flashed a rom & it was always via TWRP I understand treble roms are flashed via the stock recovery though
Click to expand...
Click to collapse
I have the same model and have also been following the thread. My understanding, and hopefully someone will correct if wrong, is that with project treble GSI you're only overwriting, via fastboot, system.img partition, therefore if you want to return to your original I suspect you can do the same thing again and fastboot original.img with a factory reset.
There is a utility called huawei firmware finder which allows you to look for firmware. I tried it but can only find the LLD-AL10 8.0.0.100(C675CUSTC675D4) which i think is for the 4/64GB veresion or may even be for the huawei P smart. Until honor make the firmware available not sure what other options exist.
BTW it would help if you report back with any success/failures if you try it. Also interested in what this version Lineage OS is missing/not working, I think the camera still has some issues last i checked the thread.
xzyk said:
I have the same model and have also been following the thread. My understanding, and hopefully someone will correct if wrong, is that with project treble GSI you're only overwriting, via fastboot, system.img partition, therefore if you want to return to your original I suspect you can do the same thing again and fastboot original.img with a factory reset.
There is a utility called huawei firmware finder which allows you to look for firmware. I tried it but can only find the LLD-AL10 8.0.0.100(C675CUSTC675D4) which i think is for the 4/64GB veresion or may even be for the huawei P smart. Until honor make the firmware available not sure what other options exist.
BTW it would help if you report back with any success/failures if you try it. Also interested in what this version Lineage OS is missing/not working, I think the camera still has some issues last i checked the thread.
Click to expand...
Click to collapse
Thanks for the reply, I suspected that's how it worked, just flash back the original system image.
I think I'm gonna hang fire for the time being until I know I have the correct firmware to go back if needed, hopefully the camera will be sorted by then too.
I flashed a firmware today and couldn't revert to stock because can't find it. Any ideas?
evolucja said:
I flashed a firmware today and couldn't revert to stock because can't find it. Any ideas?
Click to expand...
Click to collapse
When you unlocked your bootloader and before you overwrote your system partition you should have taken a backup of your stock system partition so you can restore it. Honor has not made the firmware available yet as far as I know.
xzyk said:
When you unlocked your bootloader and before you overwrote your system partition you should have taken a backup of your stock system partition so you can restore it. Honor has not made the firmware available yet as far as I know.
Click to expand...
Click to collapse
Just in case I decide to try this, how do I get a flashable file?
I pulled the contents of system + odm via ADB but just ended up with 2.3GB of folders.
Can I convert this to a flashable .img file? Or should I have done this another way?
jusumgeezer said:
Just in case I decide to try this, how do I get a flashable file?
I pulled the contents of system + odm via ADB but just ended up with 2.3GB of folders.
Can I convert this to a flashable .img file? Or should I have done this another way?
Click to expand...
Click to collapse
found description for how to do it for v10 on another site:
adb shell
su
dd if=/dev/block/bootdevice/by-name/system of=/storage/emulated/0/system.img
this implies root is required so I guess you would:
1. unlock bootloader
2. load TWRP.
3. load root (su).
4. reboot back into TWRP and save system.img.
However, you make it work you need to make sure system.img is saved before any changes are made.
xzyk said:
found description for how to do it for v10 on another site:
adb shell
su
dd if=/dev/block/bootdevice/by-name/system of=/storage/emulated/0/system.img
this implies root is required so I guess you would:
1. unlock bootloader
2. load TWRP.
3. load root (su).
4. reboot back into TWRP and save system.img.
However, you make it work you need to make sure system.img is saved before any changes are made.
Click to expand...
Click to collapse
I was thinking about this today & came to the same conclusion.
The idea is to pull a clean unmodified system image, but the only way to do that is by using root privileges SU, then via TWRP - Does that not make it a modified image?
Maybe I'm thinking about it too much:silly:
What Root method & TWRP versions have Honor 9 Lite users had success with? I'm keen to give this a go
jusumgeezer said:
I was thinking about this today & came to the same conclusion.
The idea is to pull a clean unmodified system image, but the only way to do that is by using root privileges SU, then via TWRP - Does that not make it a modified image?
Maybe I'm thinking about it too much:silly:
What Root method & TWRP versions have Honor 9 Lite users had success with? I'm keen to give this a go
Click to expand...
Click to collapse
Not TWRP as that is the recovery partition (recovery.img) not the system partition (system. Img). Not sure about root though as i believe that does add stuff in one, or more, of the system sub folders, maybe someone else can confirm, but if you're using superuser then unzipping that should tell you what's being added and where. However, if you think about it, this has always been a bit of an issue with any android. You cannot take a nandroid backup without some kind of custom recovery so how can you ever take a snapshot of the stock rom. Specialised tools can do it as they can dump the entire rom but how can any android be dumped in full straight out of the box without first changing something.?
You could try this:
https://9to5google.com/2017/11/04/how-to-backup-restore-android-device-data-android-basics/
but it never really worked properly for me.
jusumgeezer said:
I was thinking about this today & came to the same conclusion.
The idea is to pull a clean unmodified system image, but the only way to do that is by using root privileges SU, then via TWRP - Does that not make it a modified image?
Maybe I'm thinking about it too much:silly:
What Root method & TWRP versions have Honor 9 Lite users had success with? I'm keen to give this a go
Click to expand...
Click to collapse
xzyk said:
Not TWRP as that is the recovery partition (recovery.img) not the system partition (system. Img). Not sure about root though as i believe that does add stuff in one, or more, of the system sub folders, maybe someone else can confirm, but if you're using superuser then unzipping that should tell you what's being added and where. However, if you think about it, this has always been a bit of an issue with any android. You cannot take a nandroid backup without some kind of custom recovery so how can you ever take a snapshot of the stock rom. Specialised tools can do it as they can dump the entire rom but how can any android be dumped in full straight out of the box without first changing something.?
You could try this:
https://9to5google.com/2017/11/04/how-to-backup-restore-android-device-data-android-basics/
but it never really worked properly for me.
Click to expand...
Click to collapse
Guys TWRP Test Alpha build booted in Honor 9 Lite.
Tonight Stable build with all TWRP features is going to release in XDA i hope so.
Credits to @XePeleato - Team OpenKirin
VigneshS007 said:
Guys TWRP Test Alpha build booted in Honor 9 Lite.
Tonight Stable build with all TWRP features is going to release in XDA i hope so.
Credits to @XePeleato - Team OpenKirin
Click to expand...
Click to collapse
Great, that's good news. Please report back with a link so we can all share. Thanks.
Thanks for the replies everyone.
Great news about TWRP too, I look forward to trying it out.