Develop Bugs

CUBOT GT72E (MT6572) BRICKED (Help Thread)

Hello, first than everything I'd like to thank you all in advance... Now to the problem in hand, I recently got 2 CUBOT GT72E Phones, one of them I flashed with was supposed to be a STOCK Firmware:
http://blog.geekbuying.com/index.ph...for-cubot-gt72-mtk6572-dual-core-smart-phone/
I used SP Flash Tool for this, the process went seamlessly and when I got to the final OK Green Circle and then disconnected and tried to turn on my phone, it wouldn't turn on or do anything at all, I inmediatly freaked out and tried to find out how to solve it... So after some reading and learning, trial and error, I have found out the phone is not fully bricked and that there might be a solution.
First I took the battery out, connected the phone and put on the battery again and managed to install "MTK USB Port" Driver, the computer successfully detects the device as it, though when trying to reflash the "STOCK" Firmware or some other Backups and previous "working" Firmwares I stumble on ERROR 4032 - ENABLE DRAM FAILED!
After some more reading I think the reason might be a wrong PRELOADER, or so it seems to be with many other devices of other people that had the same problem.
So then I had an idea, I considered myself an idiot for flashing a PRELOADER without backing up the previous Firmware beforehand, but I have another working phone, exact same one, came on same shipping, same stock ROM, so well I then decided hoping I wouldn't end up bricking the second one, to try and backup the Stock Firmware from my working phone, so after Rooting it I used MTK Droid Tools and successfully made a Backup that included what I'm almost entirely sure is a working PRELOADER.bin, I also downloaded some other Backups and Readbacks that meet the same criteria and that I assume work as well, or so they should.
Now... I feel I'm pretty close to REVIVING this bricked phone, just a few more issues and I'm running out of help online just by reading, I'm hoping someone can directly help my case.
After making the scatter file for my backup of the working phone using the firmware.info, and trying to load it into SP Flash Tools, it fails to load the PRELOADER (Fail to load ROM file: PRELOADER) and it apppears in red letters in list.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If I double click PRELOADER on list and pick the working file it keeps saying it fails, what can I do to avoid this, or is there any other tool, I have already tried MTK Flash Tools, I manage to load the PRELOADER.bin in it, but as I go ahead and "Download" it just gets stuck on the Download DA 100% Red Bar until it finally stumbles back on ENABLE DRAM FAILED!
I've tried mixing it up and using the other backups that should work as well, I have checked and they fill all the specifications and criteria for the specific phone, and what happens is that, even if I'm able to properly load the Scatter file with the PRELOADER and everything, when I try to flash it, it goes ahead and fills up the Red Bar and immediatly after that it does nothing and just stops, leaving the Format, Firmware Upgrade and Download Buttons enabled again, the Red Bar remains on the bottom but no change at all.
Now what I guess might be the missing piece would be to be able to fully load the backup I made from the working phone to flash it successfully and reviving the phone. I'm also considering I might have the wrong driver or somehow I'm not accessing the download mode on the phone needed to flash it properly. I've heard something about META mode, holding Volume UP and without battery, I've tried that, though PC identifies it with the same driver, so I'm not aware if I should be using another driver, and uninstalling and deleting the previous one first before trying...
So in conclusion I think I need some help with two specific things:
- Pinpoint the Driver needed for my CUBOT GT72E a MT6572 device.
- Find out how to load the backup from working phone into SP Flash Tool.
I'll also leave the detailed specifics of the phone (the working one) from MTK Droid Tools
Hardware : MT6572
Model : CUBOT GT72E
Build number : Z22D_CQ_E2_A_H1.00_V01_CUBOT
Build date UTC : 20131030-152620
Android v : 4.2.2
Baseband v: MOLY.WR8.W1315.MD.WG.MP.V1.P18, 2013/09/07 14:55
Kernel v : 3.4.5 (gcc version 4.6.x-google 20120106 (prerelease) (GCC) ) #1 SMP Wed Oct 30 23:22:42 CST 2013
Uboot build v : -----
LCD Driver IC : 1-HX8379A_wvga_vdo
I don't mean to be pushy but this sort of things tend to get me very anxious and worried, I'd love some help or even replies trying to contribute, I'm doing my best and even if I'm not an expert on Phones and Android Devices, I think I can handle myself with some advice, shouldn't be too hard so just give it a try, any advice or hint will do.
This seems like a good phone, the working one I've been using so far is doing great, it's the first cheap Dual Core device I've seen and I'm really looking forward to developing custom releases for this one, I mean to contribute to this community, but if I can even un-brick this one I don't think I'd be of much help, hurts my pride a bit, I think I can do it, I just need a little help, I'm not giving up just yet so please I'd appreciate you avoid comments like "You blew it" "It's hard bricked, just give it up" or "Return to supplier"
This is a thread that explains how to unbrick MT65XX devices, so before you refer me to it and just paste the link, I've read it and found it really helpful, quoting this thread (Added on Nov 23, 2012 - MT65xx is truly UNBRICKABLE) Please refrain from telling me to give up, I haven't seen a successfull post of Cubot GT72E Unbricking and I intend to be the first one, yet I've seen many posts on both Cubot Forums and other sites of people having bricked their phones by using this "STOCK" Firmware, finding a solution for me is allowing me to help others to solve this as well
http://forum.xda-developers.com/showthread.php?t=1943442
I'll try and contact "rua1" who has developed all this tools and seems like an expert to see if he can help me.
Again thanks for taking the time to read this thread, I look forward to your replies.

BUMP
BUMP (Perhaps I posted too late in the night)

Aedirus said:
BUMP (Perhaps I posted too late in the night)
Click to expand...
Click to collapse
If you have 2 phones then you are in luck.
Use the mktool and sp flash to make a full backup of the working phone and use the back up and to restore the soft bricked one.
Loads of guides on how to do it.
Use this guide to backup the working one forum.xda-developers.com/showthread.php?t=2438752

Managed to unbrick - lost imei & baseband
I managed to revive the phone using the "Stock" firmware, it's scatter file, but writting the preloader from my other phone, the ROM had no Developer Options to enable USB Debugging, I installed an update through recovery and it was now there, rooted it, but now I've lost IMEI and Baseband on it, I also had WARNING NVRAM = ERR 0x00 on Wifi, but managed to solve it by Hex Editting the WIFI file inside data\nvram\APCFG\APRDEB with the right MAC Address.
So far so good, but from all the methods I've seen and found to write IMEI into device, none have worked...
I assume there is a problem regarding "pttycmd1" and lot of files that are on the dev\radio folder of the working phone and that the unbricked one doesn't have, strangely though I can't seem to copy the "radio" folder or any of the files inside it with Root Explorer or any other root file explorer, it simply gets stuck on the first file, permissions on the folder and files are fine... So I don't know what the problem might be or how to sort it out...
Some threads I've seen online suggest flashing the SEC_RO.img from a backup (I'd use the one from the working phone). Yet I'm not sure if I should or could do it, strangely the only Scatter file that works is the one from the "Stock" firmware, should I try loading that scatter file, only ticking SEC_RO.img and loading the one from my backup into it and hit Download?
There should be no harm in it, but I wonder if it would cause both phones to have the same IMEI...
In conclusion and to make it clear, I have revived the phone but it seems somehow NVRAM got formatted and I lost IMEI, Baseband and pretty much everything you'd lose when you format NVRAM...
Any thoughts?

Aedirus said:
I managed to revive the phone using the "Stock" firmware, it's scatter file, but writting the preloader from my other phone, the ROM had no Developer Options to enable USB Debugging, I installed an update through recovery and it was now there, rooted it, but now I've lost IMEI and Baseband on it, I also had WARNING NVRAM = ERR 0x00 on Wifi, but managed to solve it by Hex Editting the WIFI file inside data\nvram\APCFG\APRDEB with the right MAC Address.
So far so good, but from all the methods I've seen and found to write IMEI into device, none have worked...
I assume there is a problem regarding "pttycmd1" and lot of files that are on the dev\radio folder of the working phone and that the unbricked one doesn't have, strangely though I can't seem to copy the "radio" folder or any of the files inside it with Root Explorer or any other root file explorer, it simply gets stuck on the first file, permissions on the folder and files are fine... So I don't know what the problem might be or how to sort it out...
Some threads I've seen online suggest flashing the SEC_RO.img from a backup (I'd use the one from the working phone). Yet I'm not sure if I should or could do it, strangely the only Scatter file that works is the one from the "Stock" firmware, should I try loading that scatter file, only ticking SEC_RO.img and loading the one from my backup into it and hit Download?
There should be no harm in it, but I wonder if it would cause both phones to have the same IMEI...
In conclusion and to make it clear, I have revived the phone but it seems somehow NVRAM got formatted and I lost IMEI, Baseband and pretty much everything you'd lose when you format NVRAM...
Any thoughts?
Click to expand...
Click to collapse
Should be fine, extract the recovery and sec ro from working phone and flash.

Tried it
Well I did it with the SEC_RO.bin, and even managed to flash the NVRAM.bin after some pretty annoying scatter file editting, the only scatter that works is quite more complex than your regular scatter, but I managed to do it, so I know have the same files in the "radio" folder and etc...
Still can't manage to recover IMEI or write it with any tools...
I didn't flash the Recovery.bin from the working phone, would it make any actual difference? Just asking... I'm still quite new to all of this...

Recover IMEI
Any clues or thoughts on how to recover my IMEI?

IMEI doesn't remain
I managed to Write the IMEI with this tool, check this screenshot:
However when I reboot the phone IMEI's remain "Invalid", I'm assuming the phone is rolling it back, when I had problems with the Wifi WARNING ERR 0x00 I had to not only Hex Edit the WIFI file with the correct MAC Address but also change it's permission to only read to prevent the phone from rolling back to wrong file, is there a way to prevent the IMEI not being stuck to the phone? Perhaps formatting the NVRAM before trying to write the IMEI?

HELP PLZ
C'mon people, I'm so close already, just one more push, read the post and help me out, I know I can solve this!

Aedirus said:
C'mon people, I'm so close already, just one more push, read the post and help me out, I know I can solve this!
Click to expand...
Click to collapse
Try this app http://d-h.st/xGU there is a option to write IMEI
http://www.youtube.com/watch?v=4gRAlf--D8E

Doesn't work...
I don't have CDS Information Option, it doesn't appear, I'm guessing it doesn't work for MT6572...

BUMP
BUMP! C'mon guys almost there, with two phones, there must be a way to backup and flash Baseband, NVRAM or w/e is needed from the working phone to the other one, I just haven't stumbled on the right one... MT6572, CUBOT GT72E, Thanks!

Re-BUMP
Re-BUMPING, I hope I'm not abusing it, I just would like for more people to try and give me some advice... Can't be that hard, again I have two phones, one of them is working with the stock firmware and has all the Baseband and IMEI info...

I had the same problem with my Huawei Y511, I can restore with the phone of my wife, this is the same phone! For restore the NVRAM you can use MTK DROID TOOLS the last version, support the MT6572...

spawn784 said:
I had the same problem with my Huawei Y511, I can restore with the phone of my wife, this is the same phone! For restore the NVRAM you can use MTK DROID TOOLS the last version, support the MT6572...
Click to expand...
Click to collapse
Somebody progress?

Of Course!!!
h3ct0r said:
Somebody progress?
Click to expand...
Click to collapse
Yeah Friend! Any question ask me! :good:

hello ! im in the same situation here... ive revived the phone but no imei and can't write it with any tool out there... can anybody give me a hand here?? please !!!
thanks in advance !!

i have finally find a solution to our problem !! i will open a new topic with all the info and the working ( modified ) ROM !!
http://forum.xda-developers.com/showthread.php?t=2656547 check my tutorial

Great to hear!
Next week I'll have the bricked GT72E again in my hands,
I read the url what was placed here to another topic but that file is made for another MTK6572.
Anyone who can supply me the correct file for the GT72E with a small tutorial.
Thnx in advance

BUMP @Aedirus
Can you send me a scatter file, I have the device here but with the tutorials that I found on this topic I can't come further.
Thnx in advance!

Hard bricked Xperia M - Help!

Hello all, I have been a lurker for quite a while here. I own an Xperia M (Rooted, Unlocked BL running CM11). I was feeling adventurous and started messing with the partition table hoping to resize the system and data partitions using parted. I was unaware that the bootloader detects such modifications and ended up with a brick.
Just to clarify, this is a hard brick, since the Flashtool and fastboot modes do not work. I do not see the blue LED while trying to start the device in the fastboot mode using the volume rockers. My PC only detects a "QHSUSB_DLOAD" device for which I've installed the drivers and it is now "Qualcomm HS-UDB QDLoader 9008".
However, before I started to work with the partition table, I took a raw backup of the emmc i.e. mmcblk0. This should include the correct partition table and all the partitions (TA, userdata, system etc.). Theoretically (I believe so), if this is reflashed onto the device, an unbrick could be possible. However, so far, I haven't been able to figure out a way to push this image back to the device. I came across QPST and some linux bash scripts but haven't been able to use them successfully.
Has anyone come across such a scenario before? I looked for solutions in other threads but didn't find anything conclusive for Xperia devices. Can someone help me with this? thanks.

randallstevens said:
I was feeling adventurous and started messing with the partition table
Click to expand...
Click to collapse
Hi,
On other forum one user followed suggested by me same theory of remapping paritions as described here to shrink so large /system and increase /userdata
He gotta same brick because deleted 3 partitions and then they was cannot created by any commands, so seems this method not applicable to our phone.
Next he very early quited from recovery without restoring partition table from backup.
Surprisingly, in un-offical service center phone was quickly fixed, seems with JTAG-device.
QHSUSB_DLOAD – this is fall-back low-level mode of CPU that allow access to all partitions just like fastboot
Needed to repair / writing stock ROM at factory.
Can be enabled manually by connecting to PC with holding both volume buttons. How to exit – don't know.
QPST utility not useful because we not have dump in it's proper format. So only Linux our hope.
That user tried to manage with Ubuntu but phone was not recognized. Very likely he went into something wrong.
That's very great that you created backup of whole NAND.
Maybe will be enough restore GPT (partition table), I have one and own per-partitions dump too.
So plan very easy: connecting phone to PC with Ubuntu and restore dump via dd utility.
Partially follow this instruction with modifications because you have full dump.
Connect phone, find where it "attached" (whole nand, not partitions), restore file there.
Be careful with disk naming, you can damage data on HDD.

Bonoboo said:
So plan very easy: connecting phone to PC with Ubuntu and restore dump via dd utility.
Partially follow this instruction with modifications because you have full dump.
Connect phone, find where it "attached" (whole nand, not partitions), restore file there.
Be careful with disk naming, you can damage data on HDD.
Click to expand...
Click to collapse
Hi Bonoboo, thank you for replying.
Unfortunately, Ubuntu isn't able to detect the emmc and therefore, I'm unable to find the "/dev/sdX" node for the device. The phone is being detected only as "Qualcomm, Inc. Gobi Wireless Modem (QDL mode)".
I've seen some threads wherein QPST is first used to enable the partitions detection of emmc. However, as you mentioned, we do not have the necessary MSM8227 HEX file for this.
A windows app called "s1tool.exe" can be used to flash the bootloader files from the FTF, Link to thread. However, a testpoint combination is needed to access the emergency mode. I was unable to find a testpoint for Xperia M.
Is JTAG the only way forward here? Thanks again for the help.
EDIT: Looks like the s1tool I mentioned is device specific, may not work with XM.

randallstevens said:
I'm unable to find the "/dev/sdX" node for the device.
The phone is being detected only as "Qualcomm, Inc. Gobi Wireless Modem (QDL mode)".
Click to expand...
Click to collapse
Yeah, this is not good, same as was with that guy. 1, 2
But here under spoiler I found Perl-script that may open access to eMMC.
Here more info.
Maybe it device-specific too, but anyway try.
UPD: post
just connect your phone to PC (at this time your /var/log/kern.log should update and ttyUSB0 should be added), in terminal, cd to your download folder and run './qd.pl --check', or run 'perl ./qd.pl --check'.
Click to expand...
Click to collapse

Bonoboo said:
Yeah, this is not good, same as was with that guy. 1, 2
But here under spoiler I found Perl-script that may open access to eMMC.
Here more info.
Maybe it device-specific too, but anyway try.
UPD: post
Click to expand...
Click to collapse
Hello Bonoboo,
I've tried using the qd.pl script but I'm not sure which file needs to be sent to the device when using the "qd.pl --pfile X" and the other parameters. The script detects the Qualcomm modem. I've tried uploading the first 256 kilobytes of the dump which should include the partition table but this results in an "Invalid Response" error from the script. Tried uploading the TA and some other partitions, but received the same error. No eMMC access yet. What file do you think the script requires?

randallstevens said:
What file do you think the script requires?
Click to expand...
Click to collapse
Was mentioned some *.hex, that maybe relates with same from QPST.
In threads more info.
Very likely script just not compatible with M.
UPD: it's sounds weird, but try to connect phone in fastboot / flashmode with long holding volume key.
In some cases this really helpful due second "bootloader" (alt_s1sbl2 partition and other).

Bonoboo said:
UPD: it's sounds weird, but try to connect phone in fastboot / flashmode with long holding volume key.
In some cases this really helpful due second "bootloader" (alt_s1sbl2 partition and other).
Click to expand...
Click to collapse
Hi, I tried long-pressing the volume key, it does not seem to work. Thanks for the confirmation about the hex file. It looks like I'll need the right files for the handset, as using hex files of similar chipsets did not help. I'll keep working on it and write back with an update if I'm able to fix it.

I've got the same problem., but unfortunately I didn't make a dump of mmcblk0. There is a way I can get yours? Or a part of it with the interesting data with which I can try figuring out how the qdload.pl script works (maybe leave out userdata cause of its size and the private data).

fakier said:
I've got the same problem., but unfortunately I didn't make a dump of mmcblk0. There is a way I can get yours? Or a part of it with the interesting data with which I can try figuring out how the qdload.pl script works (maybe leave out userdata cause of its size and the private data).
Click to expand...
Click to collapse
Hi fakier, sorry to know you have the same problem. I've sent you a PM with a link to a compressed copy of the first 140 MBs of the raw eMMC dump I made earlier. This should contain all the important partitions besides system and userdata. Note that this also includes my TA partition which probably shouldn't be written to your device.

randallstevens said:
Hi fakier, sorry to know you have the same problem. I've sent you a PM with a link to a compressed copy of the first 140 MBs of the raw eMMC dump I made earlier. This should contain all the important partitions besides system and userdata. Note that this also includes my TA partition which probably shouldn't be written to your device.
Click to expand...
Click to collapse
Thanks, a backup of my TA partition I do have...

Update
Hello folks, after spending a lot of time trying to fix my device with qdloader and QPST, I gave up. Before getting it JTAGed, I wanted to try my luck (again) and approached Sony to claim warranty, since there was a month remaining before its expiry.
My warranty claim was accepted and they replaced the mainboard, though the bootloader was unlocked!! My Xperia is alive and kicking again! Will unlock it soon.
Trying to fix the phone was not a pleasant experience, but I think I learned much along the way. Hope nobody else screws-up the way I did.
Thanks XDA, see ya around! :good:

randallstevens said:
Hello folks, after spending a lot of time trying to fix my device with qdloader and QPST, I gave up. Before getting it JTAGed, I wanted to try my luck (again) and approached Sony to claim warranty, since there was a month remaining before its expiry.
My warranty claim was accepted and they replaced the mainboard, though the bootloader was unlocked!! My Xperia is alive and kicking again! Will unlock it soon.
Trying to fix the phone was not a pleasant experience, but I think I learned much along the way. Hope nobody else screws-up the way I did.
Thanks XDA, see ya around! :good:
Click to expand...
Click to collapse
Dude what was the point of this thread and when you tried to fix your phone did you re flash stock ROM?

Reply to Piravinthb's comment
Piravinthb said:
Dude what was the point of this thread..
Click to expand...
Click to collapse
The point of this thread, dude, was to see if the device could somehow be taken out of the "Qualcomm HS-USB QDLoader 9008" mode, a (very) low-level interface meant for vendors to flash bootloaders and system images on their devices.
..and when you tried to fix your phone did you re flash stock ROM?
Click to expand...
Click to collapse
Had you googled this, you'd know that this mode isn't the same as the Flashtool flash mode or fastboot. No rom, stock or CM, can be flashed before fixing the bootloader itself, which is needed to start the device.
Not much progress could be made here since the bootloader hex files for Qualcomm's OEM tools (QPST) would be needed to fix such a hard brick. Also, the QDloader scripts mentioned earlier were written for a different chipset from the one used in Xperia M.
Cheers, RS.

randallstevens said:
Hello all, I have been a lurker for quite a while here. I own an Xperia M (Rooted, Unlocked BL running CM11). I was feeling adventurous and started messing with the partition table hoping to resize the system and data partitions using parted. I was unaware that the bootloader detects such modifications and ended up with a brick.
Just to clarify, this is a hard brick, since the Flashtool and fastboot modes do not work. I do not see the blue LED while trying to start the device in the fastboot mode using the volume rockers. My PC only detects a "QHSUSB_DLOAD" device for which I've installed the drivers and it is now "Qualcomm HS-UDB QDLoader 9008".
However, before I started to work with the partition table, I took a raw backup of the emmc i.e. mmcblk0. This should include the correct partition table and all the partitions (TA, userdata, system etc.). Theoretically (I believe so), if this is reflashed onto the device, an unbrick could be possible. However, so far, I haven't been able to figure out a way to push this image back to the device. I came across QPST and some linux bash scripts but haven't been able to use them successfully.
Has anyone come across such a scenario before? I looked for solutions in other threads but didn't find anything conclusive for Xperia devices. Can someone help me with this? thanks.
Click to expand...
Click to collapse
hi i have same problem with same adventure , but i was using stock rom with customized kernel with cwm.
i think the solutions are 2
repair hard brick with JTAG or test point and s1tool what is not implemented for xperia m
see http://forum.xda-developers.com/showthread.php?t=2646405 for Z1

my handset will be in trash no free or paid solution or sony service . i'll buy another one
thx

rafik23 said:
my handset will be in trash no free or paid solution or sony service . i'll buy another one
thx
Click to expand...
Click to collapse
Buy a nexus 4 off amazon for 140€
It only takes 2 taps to thank somebody here.

I bricked my G4 H812. No download mode, nothing on screen, only QHSUSB__BULK.

So I messed up flashing the rooted system.img:
Code:
dd if=/data/media/0/system.rooted.img bs=8192 skip=65536 count=548352 of=/dev/block/mmcblk0
I used skip instead of seek
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
so I've wiped out the partition table and pretty much everything.
The good news is I have a backup of the entire /dev/block/mmcblk0 that I made before attempting to modify anything, so hopefully it's possible to recover, if I knew how...
When plugging the cable in, the phone appears as QHSUSB__BULK device in Windows, and "qcserial ttyUSB0: Qualcomm USB modem converter" in Linux. Otherwise, nothing happens. Whether I have battery/SD card inserted or not, holding volume up or any other buttons, there's no response at all. Blank screen, no LED, no vibrate, it does absolutely nothing. The only thing it will do is reconnect if I hold the power button for several seconds. fastboot.exe doesn't detect any devices. Windows device manager doesn't list any disks except the computer's actual hard drive.
I'm sure there must be some way to recover it using this QHSUSB__BULK mode, but I haven't found anything.

I'm in the same boat as you, but with H815. With proper drivers your device will be recognized as a Qualcomm 9008, I think. I have very heavily researched this, and unfortunately, there is no available way to recover. For G2 and G3, there was a tool called BoardDiag. Perhaps this will at some point be made compatible with G4.

I've heard about these drivers and BoardDiag but haven't found them. Maybe tomorrow I'll look for them more... otherwise I can probably take it to the shop under warranty, but I worry they'll give me back a new one with a new firmware and I'll have to wait for another root exploit... :|

Silly question that won't help you fix your problem but... Why did you type out that? Why not just copy paste?
Sent from my Nexus 7 using Tapatalk

Try this no promises
I did the same thing with my G2 and followed this guide to restoring it.. It may work for the G4 as well if you have or can get the image files for your device...
http://forum.xda-developers.com/showthread.php?t=2582142

tobesedated said:
I did the same thing with my G2 and followed this guide to restoring it.. It may work for the G4 as well if you have or can get the image files for your device...
http://forum.xda-developers.com/showthread.php?t=2582142
Click to expand...
Click to collapse
No good. I don't get any /dev/sd* when I plug it in. Only /dev/ttyUSB0. Unless that serial port somehow is actually a storage device, but that seems unlikely...
Copy/paste would have been a good idea!

RenaKunisaki said:
No good. I don't get any /dev/sd* when I plug it in. Only /dev/ttyUSB0. Unless that serial port somehow is actually a storage device, but that seems unlikely...
Copy/paste would have been a good idea!
Click to expand...
Click to collapse
Stupid question but you are using linux to try this right? I don't know that it will work in Windows

Yes, I'm using Linux, and I also have a Win7 box to play with.
Anyway I took it in for repair under warranty, so just have to hope there's no problem...

RenaKunisaki said:
Yes, I'm using Linux, and I also have a Win7 box to play with.
Anyway I took it in for repair under warranty, so just have to hope there's no problem...
Click to expand...
Click to collapse
lemme know how that goes, im sitting on a brick too. i just figured id wait a few weeks see if any fixes pop up before i send back to lg. i meant to zero out laf.img to access fastboot mode to try oem unlock on ls991, but im a dummy and got way in over my head and deleted aboot by accident. my windows xp netbook doesn't even see a qualcomm device. i havent tried on the raspberry pi yet. the only response i can get from the phone is a battery symbol with a ? , and onlyif i plug in usb from pc with no battery in the phone

Yeah, I heard some people wouldn't get the Qualcomm device popup, but would get the question mark battery icon. For me it was the opposite; the device shows up (as QHSUSB__BULK in Windows and ttyUSB0 in Linux) but absolutely nothing on the screen no matter what I do.
My guess is because some people only wiped out laf or aboot or a couple other things that are used later in the boot process (so it will boot, but fail quickly when it can't find them), whereas I wiped out the entire partition table, so the very first step fails; probably the hardware itself (the modem, CPU, or who knows), upon not finding a bootable partition, goes into some backup mode where it can be flashed over USB. (Just nobody seems to know how to flash it from there...) Or the very first sectors of the MMC contain the actual stage 1 bootloader (I noticed partition 1 starts at sector 32768, so some 16MB at the beginning is unaccounted for), and that code is responsible for disabling the QHSUSB__BULK mode, but having wiped out even that, it stays enabled. (Possibly another way for root/unlock if someone examined it closer...)

Yeah no easy way you need a direct flashing eMMC tool

I'm guessing no one managed to fix their brick? Same thing happened to me after attempting to revert to an earlier version bootstack.zip.
From my reading of G3 unbricking, the attempted-downgrade flag got tripped and so it's in the same 9008 state. Without access to the LG supplied .mbn files, there's no way to do any sort of fix. i.e. this problem could be easily fixable, just not by anyone without LG tech tools.

Contact @vn_mobile

Has a system image been posted? I'm kinda in the same boat...

dd if=/data/media/0/system.rooted.img bs=8192 skip=65536 count=548352 of=/dev/block/mmcblk0
Click to expand...
Click to collapse
mean 3955228672 byte (~ 3.9GB) of eMMC (mmblk0) is CLEAR
If can go to my country i can recovery for you or

Hi,
Read this web pages.
http://www.androidbrick.com/ultimate-qualcomm-snapdragon-unbrick-guide-snapdragons-are-unbrickable/
http://www.androidbrick.com/unbrick-recover-your-dead-lg-g3-g2-all-variants/
http://www.androidbrick.com/lg-g3-hs-usb-qdloader-9008-unbrick/
http://www.androidbrick.com/unbrick...oader-9008-if-you-have-the-right-kind-of-rom/

Looking at some of the other posts on here, I think the only thing to do at this point is hope you still have warranty.
(Not really sure how I'll fare though, I just got this one as a replacement for a bootlooping G4 yesterday)

I did the same thing to my g4... I still can't find any solutions to unbrick it. Luckily I found another one on craigslist for cheap so I went ahead and bought it... Not ****ing around with it though I learned my lesson the hard way ... At the mean time I'll probably end up selling my bricked one for parts on ebay

xxxwalo said:
I did the same thing to my g4... I still can't find any solutions to unbrick it. Luckily I found another one on craigslist for cheap so I went ahead and bought it... Not ****ing around with it though I learned my lesson the hard way ... At the mean time I'll probably end up selling my bricked one for parts on ebay
Click to expand...
Click to collapse
This phone isnt even a year old yet... why would you buy another instead of sending it off to LG for Warranty repair. There are a lot of these that have bricked from OTA update.

If someone simply post the AP Chipset driver for BoardDiag.exe to start, it will be solved....
I solve my G3 with BoardDiag.exe and flashing all original image partition extracted from TOT file.... But I can't find any AP CHipset that support G4 yet.

[GUIDE] LG G3 D851 Unbrick Qualcomm 9008 Fully Working... Unbrickable D851!

NOTE: Before we begin, let me tell you that from my experience the D851 does not require shorting at all. it will be identified as Qualcomm HS-USB in a brick state without any opening up, check your device manager!
Hello guys, I spent 2 weeks analyzing hex files in order to revive a D851 that I got my hands on. It was not an easy journey but I would like to share this with the devs or people who are looking at bring their bricks to life.
What I did was actually hack the Sahara programmer files that WillCracker (BoardDiag) programs use. This comes in the attached files. Seems like there was no site on the Internet sharing this unique files and thus not allowing us to unrbick the D851.
For a more detailed view of how I got these modified files created please look at this post
But with this uniquely created files we now have unbrickable D851's , I have revived one D851 phone that I had dead. Right now it already booted into download mode and it is loading the *.tot.
Instructions
Connect your D851 phone without battery via USB to a Windows Box.
Make sure you have installed the HS USB 9008 Drivers installed. If so you will find something called "Qualcomm HS-USB QDLoader 9008 (COMxx)" under device manager, make sure you check the COM Port number, as you will need this later on the next step.
Open up BoardDiag.exe (from the downloaded files here, as it includes modified files specific for D851) and select: B2 (MSM8974AC), and pick up your COM Port.
Under 'Image Extraction' select your bin which should be the *.tot file (I used LG_D851.10C_TOT&DLL.7z).
Hit the 'extract' button into a directory of your choice.
Pick under 'COM Port' the 'Target Dir' and select where you have extracted the *.tot. This will allow us to start flashing the partition files.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Select on the checkbox "AP check".
Check the box called "RESTORE BOOT IMG", in here start picking up the partitions, write each one of them (not system, userdata or cache -- those are worthless for now), and ONLY in the end flash LAF and then finally SBL*. After this you will see the phone boot up with the battery icon since you do not have a battery connected. This is when you can tell you have now the bootloader reflashed.
Unplug the USB cable, insert the battery into the phone and hold UP while hooking up the USB cable again. After doing this your phone will boot up in download mode and now you can go ahead and flash the correct firmware using a tool such as LGFlashTool.
Below you can see a screenshot of the dmesg showing that it is already in download mode (after being in QC HS USB 9008 mode)... I am so !"#$ happy
I flashed the partitions like in this other guide but please use the attached file or else it won't work.
NOTE: Do download the attached Willcracker Version I attached specific for the D851, this is a modified one and is the only type of program I managed to use to revive my phone. I cannot stop insisting that any other set of files will not work on our D851, which is what most people reported on the forums for some time.
EXTRA: Disable Windows driver update, updating the Qualcomm HS-USB driver can cause conflicts and problems on the process.
<< If you like my work here is my hat, please donate! >>​
​

hello please i ask for your help
thank you for the great work man
can you please help me in my phone has same problem now it is a month
the problem is that my phone is lg f460s
i have the tot file but because it is a different chip-set Apq8084 this app BoardDiag doesn't support it
can you please modify the app
i searched in so many Korean forums nothing there and Russian forums too
please i donate for you man if you could find .hex singleimage.bin
i gave my phone to some people here but all of them doesn't know how to solve this boot loader problem i knew it can be fixed only by medusa box or octubos box which no body have it here
i found some files which it can revive some other phones having the same processor qualcomm snapdragon 805 like Motorola turbo and nexus 6
like these images
these unbrick files can communicate with lg f460s but because it need a right singleimage and .hex files it cant fix it
please bro try to look for this model i tried for so many weeks now
and thank you again

it fully work
thank u so much
i found your port last night
and it isnt have instruction
so i do by my self with your tool

you are my hero , you saved me thank you sooo much bro , my phone booted in fastboot mode after this , i ll try to flash frimeware now , biiig thnaks to you man

Jyed said:
you are my hero , you saved me thank you sooo much bro , my phone booted in fastboot mode after this , i ll try to flash frimeware now , biiig thnaks to you man
Click to expand...
Click to collapse
No problem man. I am also so glad to have unrbicked that phone as I can now give it to my dad as his phone (a really old Samsung Galaxy S3 was dying of slowness). I hated to have a ~$200.00 brick :cyclops: not being used! And I am a big fan of this LG G3 phone.
Btw, what I did after unrbciking first after fastboot started was that I shutted down my phone by removing the battery, and disconnected the USB cable. Then I reinsrted the battery and put it in download mode by using the: 'Keep pressing up and insert the USB cable'... and after that re-flashed the *.tot using downloaded mode as it is way faster with LGFlashTool.

Amazing work man… my D851 is working now. Earlier it failed to boot in all other methods. Thank u so much

@Omar-Avelar , Man, today i've seen my pm box and checked your message and looked here, nothing to say just.
THANKS, YOU SAVED ME! THANKS A LOT.
I've set the phone in download mode now, but when it begin the d851 firmware flash says cross DL SWversion, thats because i have a frankenstain phone, thats what've caused me a brick, what i need to do to set the d851 firmware?
Look at the images
ERROR:
My phone in dload mode says that:
and my motherboard:
I suposse that it can be fixed, but what i need to do?.
THANKS AGAIN MASTER! IM SO HAPPY
Where can i donate to you? Sorry for my english haha.
Edit: i've saw your firm now i'll donate you.

adrianbravom said:
@Omar-Avelar , Man, today i've seen my pm box and checked your message and looked here, nothing to say just.
THANKS, YOU SAVED ME! THANKS A LOT.
I've set the phone in download mode now, but when it begin the d851 firmware flash says cross DL SWversion, thats because i have a frankenstain phone, thats what've caused me a brick, what i need to do to set the d851 firmware?
I suposse that it can be fixed, but what i need to do?.
THANKS AGAIN MASTER! IM SO HAPPY
Where can i donate to you? Sorry for my english haha.
Edit: i've saw your firm now i'll donate you.
Click to expand...
Click to collapse
I've faced the same fate as you because I flashed a D855 on a Phone that was a refurbished D851. Took me like a month to figure out how to unbrick it.
By the looks of it it seems that your phone still has the LAF partition of the D855 but you recovered the other bootloder partition files allowing you to boot into the download mode 'thinking' it is a D855.
I suggest you use the LGUP_8974.dll instead of the 'supposed' D851 *.dll in the *.tot files... I think that will flash the partitions regardless if it is a D855 or 851 and force enter the files.

Omar-Avelar said:
I've faced the same fate as you because I flashed a D855 on a Phone that was a refurbished D851. Took me like a month to figure out how to unbrick it.
By the looks of it it seems that your phone still has the LAF partition of the D855 but you recovered the other bootloder partition files allowing you to boot into the download mode 'thinking' it is a D855.
I suggest you use the LGUP_8974.dll instead of the 'supposed' D851 *.dll in the *.tot files... I think that will flash the partitions regardless if it is a D855 or 851 and force enter the files.
Click to expand...
Click to collapse
Well, that images posted before whas with lgup_8974.dll and gives me the errors, I think I need to modify the hex file to put it as a "d855" and makes the program recognizes it, me fear is that if I flash the d851 firmware maybe I can loose the imei a mobile information ( before the brick the phone has d855 software ) or it will not erase my efs partition ? What u recommend me ? Flash d855 or d851 tot?

adrianbravom said:
Well, that images posted before whas with lgup_8974.dll and gives me the errors, I think I need to modify the hex file to put it as a "d855" and makes the program recognizes it, me fear is that if I flash the d851 firmware maybe I can loose the imei a mobile information ( before the brick the phone has d855 software ) or it will not erase my efs partition ? What u recommend me ? Flash d855 or d851 tot?
Click to expand...
Click to collapse
If it is a D851 motherboard but seen as a D855 via firmware I would try using the *.dll of D855 and the *.tot file of D851.
Seems like while being in HS-USB 9008 mode one of the partitions was not flashed correctly and the downloader mode still sees it as D855. The other option would be to brick it again with D855 *.dll and *.tot if the first try does not work. And while being in HS-USB 9008 mode please make sure you do flash most of the partitions there (not system, nor userdata, not cache) but the rest and end up with LAF > SBL* partition. That will flash the correct *.tot files for D851 and hopefully you will see the D851 now as D851 in the downloader mode.
I believe IIRC that the LAF partition has the downloader, and that's the one I believe is still written from when you overwrote it as a D855. If you wrote SBL* before LAF it might have booted with the LAF partition of the D855.

All done! Phone works and is alive!, @Omar-Avelar i've did what i told you, i've used a hex editor in a linux distro and modified the first "D851" mention to "D855" and goodbye CrossDL error, flashed sucessly, now my phone it's a real D851 and its hardunbricked! thanks all to you, you are great!.

Thank you, sir. You are live saver.
I have bricked my phone (d851) and I had been looking for days and nothing works.
Fortunately, I went to this thread and had successfully unbrick my phone.
God bless you.
D851 unbrickable

Omar-Avelar said:
I've faced the same fate as you because I flashed a D855 on a Phone that was a refurbished D851. Took me like a month to figure out how to unbrick it.
By the looks of it it seems that your phone still has the LAF partition of the D855 but you recovered the other bootloder partition files allowing you to boot into the download mode 'thinking' it is a D855.
I suggest you use the LGUP_8974.dll instead of the 'supposed' D851 *.dll in the *.tot files... I think that will flash the partitions regardless if it is a D855 or 851 and force enter the files.
Click to expand...
Click to collapse
My case is almost similar. As per software info it was d855 before bricking. So I flashed mm kdz for d855 and bricked.then I opened the cover and found this has a d851 board. So ,as per this tutorial I flashed everything for d851.phone booted but booting into fastboot mode only no download mode. Then I followed some other tutorial and again flashed laf. Img .now it can enter in download mode. But have a big problem .As it was a real d851 rom it cant connect to 3g net work here in india(2g ok). Now I am so disappointed because such a good phone with 2g only.....
But how initially d855 rom was flashed on d851 board???? There may be a way..
Ofcourse only beacuse of thread my g3 is live now. Please help me to get full out put from that.
There are threads to manually add bands to qualcomm device.Can I go for that?

[Update; Duplicated post]

justinmartin111 said:
My case is almost similar. As per software info it was d855 before bricking. So I flashed mm kdz for d855 and bricked.then I opened the cover and found this has a d851 board. So ,as per this tutorial I flashed everything for d851.phone booted but booting into fastboot mode only no download mode. Then I followed some other tutorial and again flashed laf. Img .now it can enter in download mode. But have a big problem .As it was a real d851 rom it cant connect to 3g net work here in india(2g ok). Now I am so disappointed because such a good phone with 2g only.....
But how initially d855 rom was flashed on d851 board???? There may be a way..
Ofcourse only beacuse of thread my g3 is live now. Please help me to get full out put from that.
There are threads to manually add bands to qualcomm device.Can I go for that?
Click to expand...
Click to collapse
Yes, it is such a great feeling to be able to bring the phone back from the death.
BTW, I do believe also the phone bands can be changed using QPST since I have seen Argentinian D855 phones changed to D855P (Adding another LTE band).
You might need another phone reference (LG G3 that worka on the band you want) and using QPST might let you modify some specifics.
Go ahead and Google translate this post for analysis: http://www.grupoandroid.com/topic/112493-guia-habilitar-bandas-lte-para-argentina-en-d855-int/

Another success in reviving the dead lg g3
Omar-Avelar said:
NOTE: Do download the attached Willcracker Version I attached specific for the D851, this is a modified one and is the only type of program I managed to use to revive my phone. I cannot stop insisting that any other set of files will not work on our D851, which is what most people reported on the forums for some time.
Click to expand...
Click to collapse
Thank your thread was really helpful in getting somewhere, You are the champion :good::victory:
---------- Post added at 07:53 AM ---------- Previous post was at 07:52 AM ----------
adrianbravom said:
All done! Phone works and is alive!, @Omar-Avelar i've did what i told you, i've used a hex editor in a linux distro and modified the first "D851" mention to "D855" and goodbye CrossDL error, flashed sucessly, now my phone it's a real D851 and its hardunbricked! thanks all to you, you are great!.
Click to expand...
Click to collapse
Can you please direct me somewhere or guide by yourself on how to do this.

Hey , could anyone help me? i have a lg l40 d175f, and i have boarddiag ,the kdz files but i do not have the partition.txt, what do I have to do??? please save me, this is not a monster phone but i don't have money to buy another one

Omar-Avelar said:
[*]Open up BoardDiag.exe (from the downloaded files here, as it includes modified files specific for D851) and select: B2 (MSM8974AC), and pick up your COM Port.
Click to expand...
Click to collapse
Modified Files huh??
The miracle file is a file that has been around all along. It can be found in the Smartboot Diag Tool. Its called LGD851_ATMO_TMUS.mbn.
All you have to do is rename this file to 2nd_loader.hex and put it inside the Board DIag Tool > Model > B2(MSM8974AC) Folder. Replace this file with the old one.
Now start Board Diag tool and load and decompress your tot file, and flash away.
For other models, you could try renaming your devices mbn from the Smartboot Diag tool to 2nd_loader.hex

wow
mickeyasamoah said:
Modified Files huh??
The miracle file is a file that has been around all along. It can be found in the Smartboot Diag Tool. Its called LGD851_ATMO_TMUS.mbn.
All you have to do is rename this file to 2nd_loader.hex and put it inside the Board DIag Tool > Model > B2(MSM8974AC) Folder. Replace this file with the old one.
Now start Board Diag tool and load and decompress your tot file, and flash away.
For other models, you could try renaming your devices mbn from the Smartboot Diag tool to 2nd_loader.hex
Click to expand...
Click to collapse
can you provide same file for lg g3 f460s ? it has chipset apq8084 . thank you i advance

ExtraDemo said:
can you provide same file for lg g3 f460s ? it has chipset apq8084 . thank you i advance
Click to expand...
Click to collapse
I am currently in class. Will check when I get home.

Bootloader deleted, hard brick, need some help?

Hello guys,
I have cedric, bootloader unlocked, rooted, etc.. I used some SDcard format app and selected wrong storage to format emmcblk0, so i formated entire phone, now in device manager its detected as "Quectel QDLoader 9008
" cannot power it on as well i think bootloader is bricked, i tryed to flash but cant find anything related to this phone, also cant find blankflash.
Do you guys have any info on how to unbrick this hard-brick, or its just paper weight? I don't get how did moto/lenovo allow bootloader erase option from system, even with root...
Regards

Perhaps search for some driver that enables the transfer of the bootloader for "Quectel QDLoader 9008"?
I've found some results relating to unbricking this, and according to some of them it refers to a chipset, use this search perhaps https://www.google.co.uk/search?q=Q...rome..69i57.2111j0j7&sourceid=chrome&ie=UTF-8
---------- Post added at 11:30 PM ---------- Previous post was at 11:28 PM ----------
found this, it may help http://www.androidbrick.com/lenovo-zuk-phones-qfil-roms-unbrick-guide/

Tryed, not applicable for this mode, i need blankflash or some other method, i still have yet to try sdcard flash, but i am loosing hope here, might just accept that its totally bricked and thats it, oh well moving on i guess.

Guys i am trying to make unbrick method for Cedric, does anyone have 5 minutes of time to make loader.img, all you have to do is to be on firmware .93, bl unlocked and rooted.
Type in terminal emulator dd if=/dev/block/mmcblk0 of=/sdcard/Loader.img bs=1024 count=168960
And upload me that file, it will be around 160mb, i will try to test it and if it works upload the tutorial. The command above just reads your mmmcblk0 so there is no chance of bricking your device.

No one willing to give away five minutes to help? I will make it worthwhile since my phone is dead i am sure there is a change to fix it with this, and will make tutorial for community

magix01 said:
No one willing to give away five minutes to help? I will make it worthwhile since my phone is dead i am sure there is a change to fix it with this, and will make tutorial for community
Click to expand...
Click to collapse
Hey Mate i would help you if i could, but i'm on -72, if this would help you tell me, and i will upload the file asap.

@Cubico
We can try, but i don't think it will work tho. Please upload and we will see i guess

Ok guys new update, @Cubico provided me with Loader.img -73 firmware, so far tried nothing changed, device still showing no sign of life except Qualcomm 9008... not booting or anything, if someone have 93 bootloader Loader.img dump i can try that too, if not i will take it to shop to someone with JTAG and update you on status.

I have got a similar issue with an X4 that's hard bricked.
I know wrong forum, but I can't find anyone to help.
Trying to use QFIL I get "Download Fail: Switch To EDL Fail: Failed to Switch to Emergency Download mode"
ANY ideas? Thank you anyone that may be able to help!

Try installing this driver, then transfer/flash the bootloader, I can't help you with the actual img though.
http://www.androidbrick.com/download/qualcomm-qdloader-hs-9008-edl-usb-driver/#

magix01 said:
Ok guys new update, @Cubico provided me with Loader.img -73 firmware, so far tried nothing changed, device still showing no sign of life except Qualcomm 9008... not booting or anything, if someone have 93 bootloader Loader.img dump i can try that too, if not i will take it to shop to someone with JTAG and update you on status.
Click to expand...
Click to collapse
Hi, just saw this - I'm on NP25.137-93
Do you still need this dump?
Let me know and I'll get on it
Edit - aww crap!
Really sorry to get your hopes up! Just remembered, my phone's not unlocked or rooted! This is the first phone I've had in years that I've kept unrooted, so I didn't initially realise.
?

Np, i took the phone to service center for JTAG, hopefully they will manage to fix it somehow

Exanneon said:
Try installing this driver, then transfer/flash the bootloader, I can't help you with the actual img though.
http://www.androidbrick.com/download/qualcomm-qdloader-hs-9008-edl-usb-driver/#
Click to expand...
Click to collapse
This is not related to driver, bot Qualcomm and Quectel 9008 drivers work and allow communication with the phone, patch level is too high so blankflash files dont pass and dont allow bootloader to be flashed. Only solution is JTAG or motherboard replacement if patch level is higher than one in april 2017 i think.

Rip another cedric.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This has happened to me and I'm lucky had the assistance replaced the motherboard of the device. Your bootloader was not deleted, it was moved to a temporary partition that the boot script cannot find after pressing to start.
The problem with the manufacture is of the appliance was to have the bootloader on the same chip as the other partitions, causing the device to be easily hardbroken.
Solution? None so far.
I saw a guy who unbricked a potter (G5 Plus), but I've seen nothing from the G5.

Heh, another G5 killer here. A bad attempt at downgrading due to IMEI 0 left it as QLoader 9008. I guess I'll have to go back to my old Nexus 4.

Motorola sucks bad, Google and Xiaomi for instance have tools to recover dead bootloader eg. "Mi Flash", motorola gave developers easy bootloader unlock but no way to recover it, whats the point then, either make it recoverable or make it non erasable easily.

magix01 said:
Guys i am trying to make unbrick method for Cedric, does anyone have 5 minutes of time to make loader.img, all you have to do is to be on firmware .93, bl unlocked and rooted.
Type in terminal emulator dd if=/dev/block/mmcblk0 of=/sdcard/Loader.img bs=1024 count=168960
And upload me that file, it will be around 160mb, i will try to test it and if it works upload the tutorial. The command above just reads your mmmcblk0 so there is no chance of bricking your device.
Click to expand...
Click to collapse
https://drive.google.com/file/d/1H2Qkc1XKbr7Is46n5xdCFlgiuIH1m-vE/view?usp=sharing

abhimanyuk said:
https://drive.google.com/file/d/1H2Qkc1XKbr7Is46n5xdCFlgiuIH1m-vE/view?usp=sharing
Click to expand...
Click to collapse
It doesn't seem to work for me. It might be because I had the latest January update when I killed my Cedric.

These .img files should boot bootloader directly from SDCard but it seems thar Cedric does not support this feature, so only way is JTAG and non updated blank-flash file.

magix01 said:
These .img files should boot bootloader directly from SDCard but it seems thar Cedric does not support this feature, so only way is JTAG and non updated blank-flash file.
Click to expand...
Click to collapse
Yeah, I tried with two different SD*cards, but the device would only blink the notification light while being recognised as Qualcomm Loader.