Related
Anybody here wants to downgrade their YU from the sweet candy rom (Lollipop) to the old chocolate bar (Kitkat), please use this procedure post in this THREAD.
Click to expand...
Click to collapse
So here is the guide to unbrick your YU from "Qualcomm HS-USB QDLoader 9008", I hope it works for you as I fried my YU's eMMC by attempting to brick and unbrick my YU for nearly 200 times in three days just to confirm that this guide is working. And here are some pics of my current YU (an expensive desktop charger). And all of this, because I love XDA, hahahahahahaha, just hope it worthed. For God sake, I have invested nearly US$200 for this thread (at least that is how much I bought my YU plus shipping), so this post has to work. And please, don't ask whether I am serious or not, you should know the answer already.
{
"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"
}
Please read this guide thoroughly. It took hours of my precious time to make this post, but I bet you that it will olny takes minutes to read it. So once again, please read this guide thoroughly.
Now the important part, this guide was tested by me with my Lenovo laptop that run Windows 7sp1 Ultimate edition, and this is my hardware specs:
1. ANALYZING THE PHONE PROBLEM
In qualcomm NEW firmware (not the HLOS part, but NON-Hlos, SBL1, TZ, HYP, RPM, and Aboot), especially ARMv8-A, Qualcomm diminished the famous "Qualcomm HS-USB Diagnostics 9006", and introduce two types of "Qualcomm HS-USB QDLoader 9008" (source: fybon article ). So, before we proceed with the guide, we should analyse the phone first, on which 9008 mode your phone is in. To do this, follow these steps below:
1.a SETTING UP WINDOWS
I know that some fellow YU's owners who have bricked their phone are "Senior Member" and highly experience user if it comes to Android and Qualcomm phone, but I just want to ask you to give some respect for my death YU by following each of the steps that need to be taken to setup Windows.
Please turn off internet connections.
Remove your YU from PC or Laptops.
Install the latest ".net Framework" for your Windows.
Uninstall all the driver related to YU, as well as any Qualcomm driver if you have install any. Uninstall them through Device Manager FIRST, then program manager. Here I used a software called "REVOUninstaller" to remove completely the driver softwares and Device Remover to completely remove installed unnecessary device.
Then run "CMD" or "Windows Terminal" as administrator and type:
Code:
bcdedit -set loadoptions DISABLE_INTEGRITY_CHECKS
bcdedit -set TESTSIGNING ON
Restart your PC or Laptops, and you should see this watermark at the bottom right of your desktop, just like the pic below"
Download QualcommDrv.zip from here, extract to an empty folder, then open the folder according to your Windows type (x64 or x86) and double click dpinst64.exe to install the Qualcomm driver.
Now it is safe to connect your YU to PC or laptop (I connected it in USB2 port). BUT BEFORE YOU CONNECT YOU YU, REMEMBER TO UNPLUG YOUR BATTERY FOR FIVE SECS, REPLUG IT, AND CONNECT YOUR YU WITHOUT PRESSING ANY OF ITS BUTTONS. Your phone should now being detected as "Qualcomm HS-USB QDLoader 9008" and the driver version 2.0.8.7 (please check it through Windows' "Device Manager")
1.b ANALYSING PROCESS
If you were just messing with system image, boot image, system's framework or other things that does not related to Qualcomm's stuff (modem-NON-HLOS.bin, aboot-emmc_appsboot.mbn, sbl1, hyp, tz, rpm partition, for example installing sound patch, etc, you possibly will enter the new 9008 mode, which is a combination of the old "Qualcomm HS-USB Diagnostics 9006" and "Qualcomm HS-USB QDLoader 9008". When you first brick the phone into this mode, you would experience such symptoms below:
The LED charging indicator near the phone speaker will light red.
Your phone will vibrate endlessly, and this vibration will end only if you disconnect your phone from your PC or laptop and unplug the battery.
If you open Windows' Device Manager, you'll see "Qualcomm HS-USB QDLoader 9008" under PORTS (COM & LPT) or "QHUSB_BULK" under Other devices, and "Qualcomm MMC Storage USB Device" under Disk drives, similar to the pics below (NOTICE THAT RED BOX IN PIC):
OR
However, if you messed with your YU's qualcomm's partition playing with NON-HLOS.bin, emmc_appsboot.mbn, sbl1.mbn, hyp.mbn, tz.mbn, rpm.mbn, or by other mean messing the whole Qualcomm's eMMC partition, such as by using this zip I made while your YU is in Fastboot, then you will most likely go into the OLD "Qualcomm HS-USB QDLoader 9008" mode. You will find symptoms similar to below:
The phone charging indicator would not light if you connect your YU with PC or Laptop.
Device Manager only listed "Qualcomm HS-USB QDLoader 9008" under PORTS (COM & LPT) or "QHUSB_BULK" under Other devices, but no "Qualcomm MMC Storage USB Device" under Disk drives, similar to pic below:
So, now you need to analyse your YU, whether it is in the OLD '9008" or NEW "9008" mode, as the procedure to revive your beloved YU will be different.
2. REVIVING YOUR YU BACK
2.a NEW "Qualcomm HS-USB QDLoader 9008" MODE
If you are that lucky person, who is stuck in the NEW "Qualcomm HS-USB QDLoader 9008" mode, to be honest, the steps to be taken are a lot easier. However, you need somebody in this forum to upload the complete YU's eMMC image for you. To get such image, you could ask your friend to do these steps (root the phone first):
Format your external MicroSD card with "exfat" system file, and the size of this SD card should be morethan 16 GB , which is the size of the whole partition.
Do a full factory reset, meaning wipe your cache, data, and internal storage using either CWM, TWRP, or PhillzTouch.
Insert the SD card to your phone and connect your YU with ADB, type:
Code:
adb shell
su
dd if=/dev/block/mmcblk0 of=/storage/sdcard1/backup.img bs=512 count=30535646
The size of the "backup.img" is around 16 GB, However, if you compressed it, it would be around 2 GB.
Now, if you have the backup.img in your hand, you can do these steps:
Download partition tools from the net, I recommend you to use "Minitool Partition Wizard".
Download "HDD Raw Copy Tool", it is a free tool that can copy your "backup.img" to you YU's eMMC sector per sector.
Now connect your phone, remember to UNPLUG YOUR BATTERY FOR FIVE SECS, REPLUG IT, AND CONNECT YOUR YU WITHOUT PRESSING ANY OF ITS BUTTONS.
FROM NOW ON DON'T YOU EVER DISCONNECT THE PHONE FROM YOUR PC OR LAPTOPS.
Open "Minitool" and you will see that your phone has 29 partitions in total, similar to the pic below (this pic was taken from Windows' "Disk Management Tool" just to describe Qualcomm's partitions):
Delete all 29 partitions and click apply (remember don't remove your phone while "Minitool" is completing the process).
If all process finished successfully, open "HDD Raw Copy Tool", and you'll see things similar to this (please note that because my phone is now death, the pics that describe how to use "HDD Raw Copy Tool" was taken from my friend websites using a different type of Qualcomm phone, however the process that needs to be taken is similar):
Choose your "backup.img" and click "Continue >>>>>>".
Put a highlight on "Qualcomm MMC Storage USB Device" and click "Continue >>>>>>".
Check every things and click "START".
However, if you can't find a good fellow member in this forum, who is willing to give you the "backup.img", then I'm afraid you have to do it the hard way, which is forcing your beloved YU to go to the OLD "Qualcomm HS-USB QDLoader 9008" mode. You can do this using "Minitool":
Open "Minitool" again.
Delete all 29 partitions.
Then choose "Create Partition" on the whole "Qualcomm MMC Storage USB Device" (making it one big 16 GB partition) as "Primary Partition" with an "ext4" file system. By the way, DON'T GIVE THE PARTITION A NAME.
Click APPLY.
When "Minitool" completed all the process, disconect your YU from PC or Laptop, UNPLUG YOUR BATTERY FOR FIVE SECS, REPLUG IT, AND CONNECT YOUR YU WITHOUT PRESSING ANY OF ITS BUTTONS.
And I have to greet you, "Welcome, now you are in the OLD 'Qualcomm HS-USB QDLoader 9008' mode".
2.b OLD "Qualcomm HS-USB QDLoader 9008" MODE
Download "QPST 2.7 build 422" from HERE and extract it to an empty folder. It has to be this version of "QPST". Install QPST by double clicking setup.exe, see pic below:
Download 8675_W00.zip attached with this post HERE, and extract it to an empty folder. You will get a folder called "8675_W00", just open it.
Download the official YU's firmware from CyanogenOS website HERE, and extract all the files inside the previous "8675_W00" folder, and now you'll get files like the pic below:
You can run QFil in two ways:
By using QFil UI
Open it from your "Start" menu, see pic below:
Insert all the necessary file needed by "QFil": (1)The programmer will be prog_emmc_firehose_8936.mbn found inside the "8675_W00" folder; (2)Use the rawprogram0.xml found inside the "8675_W00" folder; (3)Use the patch0.xml found inside the "8675_W00" folder; (3)Hit "Download" button. For details, see the pic below:
By using CMD's Command Line (intermediate to advance user
Open "CMD" inside QPST's "bin" folder, which can be found inside QPST install directory, see image for detail:
In the opened CMD, type:
Code:
qfil.exe -Mode=1 -COM="enter your comport number setting here" -SEARCHPATH="[COLOR="Red"]enter your complete path to [B]8675_W00[/B] folder[/COLOR]" -Sahara=true;"[COLOR="red"]enter your complete path to the [B]prog_emmc_FireHose_8936.mbn[/B][/COLOR]" -RawProgram=rawprogram0.xml -patch=patch0.xml -AckRawDataEveryNumPackets=TRUE;100 -DeviceTYPE="eMMC" -PlatForm="8x26" -MaxPayloadSizeToTargetInBytes="49152"
[B]Here are example to use it[/B]
qfil.exe -Mode=1 -COM=64 -SEARCHPATH="D:\CBW8600A01_A_T1701" -Sahara=true;"D:\CBW8600A01_A_T1701\prog_emmc_FireHose_8x26.mbn" -RawProgram=rawprogram_unsparse.xml,rawprogram2.xml -patch=patch0,patch2.xml -AckRawDataEveryNumPackets=TRUE;100 -DeviceTYPE="eMMC" -PlatForm="8x26" -MaxPayloadSizeToTargetInBytes="49152"
Or you can play with does commands, here are their descriptions:
If you run "QFil" through command line, you'll get a slightly different user interface, and perhaps by running it through command line we could overcome the "sahara: fail" problem.
If the process you did with "QFil" finished successfully, the phone will reboot by itself.
After the phone rebooted, it will suffer from an endless bootloop. Don't do anything, just disconnect it from your PC, and straight away put your phone into bootloader by pressing "volume-up" button while connecting your phone again to your PC.
Go to "8675_W00" folder again, and run FlashAll(AfterQFil).bat by double clicking it.
Your YU will reboot normally to stock CM.
3. REVIVING YOUR IMEIs
To be honest this is the easiest part of the guide, and here are the steps that need to be taken (REMEMBER TO REMOVE ALL SIM CARDS BEFORE YOU DO THESE STEPS BELOW):
First of all, please root again your just revived YU.
Next, download QXDM 3.13.714 from HERE, extract it and then install (there is no special treatment for "QXDM").
Download "boot.zip" from HERE, and extratct "boot.img" found inside the zip file within our beloved "8675_W00" folder (just replace the old "boot.img").
Connect your phone with your PC, and open ADB from our beloved "8675_W00" folder, and type these command:
Code:
adb shell
su
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p20
reboot
After the phone rebooted, open device manager in windows, and you should find that your phone is recognised as "Qualcom HS-USB Diagnostics 903A". Now you can connect to QPST, QXDM, ADB, and MTP at once, each time you phone rebooted.
Now open "QPST Configuration" and see whether your phone is listed there, see pic below:
Open "QXDM Professional", go to "Options", "Communications" and set "Target Port" to your phone.
Back to "QXDM" main window, in the "View" dropdown menu, select "NV Browser", put a check mark on "Dual SIM" option, select "ALL" in "Catagory Filter" dropdown menu, and go to "ID 00550", see pic for details:
Now choose "0" on "Subscription ID" dropdown menu. By the way here, "Subscription ID = 0" means your SIM1 and "Subscription ID = 1" means your SIM2. After choosing "0", click Read, fill your SIM1's IMEI in the Input Fields, and click Write. Do the same with SIM2's IMEI, which is listed as "Subscription ID = 1" .
AND HERE IS HOW YOU PUT YOUR IMEI:
Code:
If for instance, your IMEI for SIM1 was: 954091051099226, then the boxes would be in below order:
0x08 [COLOR="red"](The first hex is always 0x08)[/COLOR]
0x9A [COLOR="Red"](The second hex is always ends by "A" or "0x9A")[/COLOR]
0x45
0x90
0x01
0x15
0x90
0x29
0x62
YOUR YU IS OFFICIALLY REVIVE, YEEEE
3. PLAYING WITH COOLPAD CPB FILES
I guess Micromax's officials have to admit that YU YUREKA is indeed Coolpad 大神 F2 8675-XXX, and do you know that the chinese word "大神" mean "Great God" in english. Yup, I'm betting a US$100 here that our beloved motto of "YU Play God" comes from the word "大神" a.k.a "Great God". I'm also suspecting that W00 are the right replacement for the missing XXX in Coolpad 大神 F2 8675-XXX, and I finally confirmed my suspection through some hex comparison between the "GPT" (the MBR of an eMMC, I would thank Ekhasti in providing me YU's "GPT.bin") of the two phones, thus making me possible to make all of the above guide. Just for your info, "GPT" resides in sector 0 until before the start sector of NON-HLOS a.k.a the modem partition of our YU's eMMC. If you want to and eager to get YU's GPT partition, all you have to do is just connect your phone with ADB, and type:
Code:
adb shell
su
dd if=/dev/block/mmcblk0 of=/sdcard/gpt.bin bs=512 count=65535
And, you'll find your gpt.bin in your phone's internal storage.
Since, Coolpad 大神 F2 8675-W00 has similar GPT, at that time, I believed that I can flash directly coolpad's firmwares into our YU, and guess what, I was right. Although at first the phone experienced endless bootloop, it booted seamlessly after I "oem unlock" the bootloader via Fastboot. So, if somebody in this forum is eager enough to try the CoolUI of Coolpad 大神 F2 8675-W00, you can unpack its CPB's file by following all the steps below:
First, of course you have to download Coolpad 大神 F2 8675-W00's CPB files, and you can get it from Yulong (the name of the company that make Coolpad) official website HERE, the file is the one with 1.6 GB file size
Download my hack edition of Coolpad Download Assistant from HERE, and install it. See all the pics below on how to, as the language is in chinese:
Upon finishing installation, copy the "dProdRes.dll" found inside the "Hacked" folder of "CDA.zip" into Coolpad Download Assistant installation directory (just replace the old "dProdRes.dll", with the hacked version). See pic below:
Run "Coolpad Download Assistant", and do as depicted by pics below:
Wait until the progress bar reach 100%:
Don't close "Coolpad Download Assistant" first, just go to "downfile" folder inside "CDA" installation directory:
Copy "8675_W00" folder inside the folder where you keep adb.exe and fastboot.exe.
Now, to flash all those unpacks file to your, just do the following steps:
Connect your phone to your PC or Laptop in fastboot mode.
Type commands below:
Code:
fastboot -i 0x1ebf oem unlock
fastboot -i 0x1ebf erase modem
fastboot -i 0x1ebf erase sbl1
fastboot -i 0x1ebf erase sbl1bak
fastboot -i 0x1ebf erase aboot
fastboot -i 0x1ebf erase abootbak
fastboot -i 0x1ebf erase rpm
fastboot -i 0x1ebf erase rpmbak
fastboot -i 0x1ebf erase tz
fastboot -i 0x1ebf erase tzbak
fastboot -i 0x1ebf erase hyp
fastboot -i 0x1ebf erase hypbak
fastboot -i 0x1ebf erase misc
fastboot -i 0x1ebf erase DDR
fastboot -i 0x1ebf erase fsg
fastboot -i 0x1ebf erase boot
fastboot -i 0x1ebf erase params
fastboot -i 0x1ebf erase panic
fastboot -i 0x1ebf erase persist
fastboot -i 0x1ebf erase recovery
fastboot -i 0x1ebf format system
fastboot -i 0x1ebf format userdata
fastboot -i 0x1ebf format cache
fastboot -i 0x1ebf flash modem /8675_W00/NON-HLOS.bin
fastboot -i 0x1ebf flash sbl1 /8675_W00/sbl1.mbn
fastboot -i 0x1ebf flash sbl1bak /8675_W00/sbl1.mbn
fastboot -i 0x1ebf flash aboot /8675_W00/emmc_appsboot.mbn
fastboot -i 0x1ebf flash abootbak /8675_W00/emmc_appsboot.mbn
fastboot -i 0x1ebf flash rpm /8675_W00/rpm.mbn
fastboot -i 0x1ebf flash rpmbak /8675_W00/rpm.mbn
fastboot -i 0x1ebf flash tz /8675_W00/tz.mbn
fastboot -i 0x1ebf flash tzbak /8675_W00/tz.mbn
fastboot -i 0x1ebf flash hyp /8675_W00/hyp.mbn
fastboot -i 0x1ebf flash hypbak /8675_W00/hyp.mbn
fastboot -i 0x1ebf flash misc /8675_W00/MISC.img
fastboot -i 0x1ebf flash DDR /8675_W00/DDR.bin
fastboot -i 0x1ebf flash fsg /8675_W00/nv.tar.mbn
fastboot -i 0x1ebf flash boot /8675_W00/boot.img
fastboot -i 0x1ebf flash params /8675_W00/param.bin
fastboot -i 0x1ebf flash panic /8675_W00/panic.img
fastboot -i 0x1ebf flash persist /8675_W00/persist.img
fastboot -i 0x1ebf flash recovery /8675_W00/recovery.img
fastboot -i 0x1ebf flash system /8675_W00/system.img
fastboot -i 0x1ebf flash userdata /8675_W00/userdata.img
fastboot -i 0x1ebf flash cache /8675_W00/cache.img
fastboot -i 0x1ebf format userdata
fastboot -i 0x1ebf format cache
fastboot -i 0x1ebf reboot-bootloader
fastboot -i 0x1ebf oem unlock
fastboot -i 0x1ebf reboot
Here I also like to say thanks to:
darkspr1te and his thread for giving some insight about on how Qualcomm chips work.
quakze for supporting this project, and also for spending his precious time testing the guide (although the result is totally negative).
ekhasti for his kindness in giving the whole partition dump of his YU.
Furthermore, if somebody in this forum manage to unbrick her/his YU using this guide, please post a reply on how you did it, what changes or improvisation that you had undertaken, as it would help other members as well. And without your reply, this thread would be dead and has to be closed, because I myself doesn't own any YU anymore.
PS.
I will be very delighted to buy your bricked YU for half price of the new one and also pay the shipping fees, but under several conditions:
Windows could detect it minimum as "QHUSB_BULK"
Does not have stain, scratch, or any deform shape and all hardware should be functional before you bricked it.
Perhaps Rohan, Ayush, or Rahul could help me finding someone that willing to sell their bricked YU.
tirta.agung said:
I just wonder, does anyone in this forum know how to make our Yureka to enter Qualcomm download mode or Qualcomm HS-USB Diagnostics 9006 mode? It would be great if we could do so, as it would enable us to make raw copy of the whole Yu's eMMC using HDD Raw Copy Tools. Beside the rawprogram0.xml, patch0.xml, 8939_msimage.mbn, MPRG8939.hex, and MPRG8939.mbn, this raw image is also very important to recover our Yureka from hard bricked.
Click to expand...
Click to collapse
it will be in hs-usb qdloader 9008 first, we just need “8939_msimage.mbn” and “MPRG8939.mbn” to bring the phone to hs-usb diagnostics 9006 mode.
quakze said:
it will be in hs-usb qdloader 9008 first, we just need “8939_msimage.mbn” and “MPRG8939.mbn” to bring the phone to hs-usb diagnostics 9006 mode.
Click to expand...
Click to collapse
Yep, I know the order. I usually use QPST's eMMC Software Download Tool to get my phone from 9008 to 9006 mode, then after Windows detects all the phone's eMMC partitions, I use HDD Raw Copy Tools to restore all the files (here I really mean ALL) to get my phone working again. So, although you managed to enter 9006 from 9008 mode, without a RAW Image of your phone made by HDD Raw Copy Tools, everything will be useless. Just like the rawprogram0.xml, patch0.xml, msimage.mbn, MPRG.hex, and MPR.mb, somebody in this forum, whose phone is bricked (either soft-9006 mode brick or hard-9008 mode brick), could use anybody's YU's RAW Image made by HDD Raw Copy Tools to get their phone working again. All they have to do afterwards, is just changing their IMEIs to their own using QXDM .
So back to the thread question. I used to have several android phones powered by qualcomm chipset, the last one before the Yu was ZTE V5 Max, which is a snapdragon 410 (MSM8916) phone. Usually after connecting a qualcomm android phone in diag mode (by putting "persist.sys.usb.config=mtp,diag,adb" either in the build.prop or default.prop inside boot.img) with Qualcomm NV Tools found in EFS Professional Suite (EFSPS), I could restart the phone into 9006 mode to make a raw image of my phone's eMMC. I usually do this first each time i bought a new qualcomm phone, just incase if I hard bricked my phone into qualcomm 9008 mode. However, I can't get my Yu into the 9006 mode, instead it went to 9008 mode (the LED near the phone speaker turns red and the phone keeps on vibrating) after I select reboot into download mode in EFSPS.
By the way quakze, i think msm8939 use the same eMMC's enumeration properties as MSM8916. Perhaps we can use MSM8916 rawprogram0.xml, patch0.xml, msimage.mbn, MPRG.hex, and MPRG.mbn. All we need is just an already bricked phone to try, and I guarantee that it would not make the bricked phone any worser. You can find the necessary file here (please use chrome to auto translate the website). The file is a full service firmware for Lenovo K3 Music Lemon, a snapdragon 410 phone. Please keep me update if my hypothesis is true.
Anybody???
tirta.agung said:
Anybody???
Click to expand...
Click to collapse
better wait for the Xiaomi Ferrari. . .RBTL
Sir, we want to change LTE frequency
thru QPST
Need help
Check here and please help us
tirta.agung said:
I just wonder, does anyone in this forum know how to make our Yureka to enter Qualcomm download mode or Qualcomm HS-USB Diagnostics 9006 mode? It would be great if we could do so, as it would enable us to make raw copy of the whole Yu's eMMC using HDD Raw Copy Tools. Beside the rawprogram0.xml, patch0.xml, 8939_msimage.mbn, MPRG8939.hex, and MPRG8939.mbn, this raw image is also very important to recover our Yureka from hard bricked.
Click to expand...
Click to collapse
I have got rom of Huawei C199s (MSM8939), which has many file packed into UPDATE.APP.
I have unpacked it, but the file name and extensions are unknown.
At present I am trying to identify the msimage.mbm and mprg files.
The rom link is http://www.needrom.com/wp-content/uploads/2015/03/C199s-V100R001C92B260-Telecom.zip
Is it just the two of us?
quakze said:
I have got rom of Huawei C199s (MSM8939), which has many file packed into UPDATE.APP.
I have unpacked it, but the file name and extensions are unknown.
At present I am trying to identify the msimage.mbm and mprg files.
The rom link is http://www.needrom.com/wp-content/uploads/2015/03/C199s-V100R001C92B260-Telecom.zip
Click to expand...
Click to collapse
Hi there Quakze, I just wonder is it only the two of us who are interested in reviving death YUs? By the way, at last I hard bricked my Yu, and I think it is true that curiosity kills. Hahahaha, so yippee for me .
Ok, back to our business, I only know three major companies who always pack qualcomm's mbn files in their firmwares, they are Lenovo, Xiaomi, and Hisense. So, if you have time to wait you can hunt these phone firmwares when they released:
Hisense HS-H910 TD-LTE (expected release firmware June 2015)
Lenovo Vibe X2 PRO Dual SIM LTE (expected release firmware June 2015)
Lenovo Vibe Shot Dual SIM LTE (expected release firmware June 2015)
Xiaomi Ferrari (expected release firmware unknown)
However, if you are curious enough to find out by yourself on how to create qualcomm's mbn file for our YUs, then we can join hands in this thread.
And this is an update from me on my effort in reviving my death YU. When I did hex readings on some CPB files, I found out that each of those files contain at least one msimage.mbn. That is why, I spend my last weekend just to do some research on Coolpad Download Assistant (CDA) Software in order to hack it, and the good news is I managed to do it.
So with this post, I have attached the hacked version of our beloved CDA software. All you have to do is just download and unzip the zip file attached in this post, install the software and copy paste the "dProdRes.dll" into Coolpad Download Assistant installation directory. Afterwards, run the program as usual, put the right path of the CPB file you want to unpack and press "ok" (of course the language use by the software is in chinese). You will find the unpack CPB files inside "DownFiles" folder found in Coolpad Download Assistant installation directory.
Please post me a reply if you have succeeded in unpacking the CPB files, and tell me what do you think about the unpacked files, as I did find some strange stuff inside it .
ekhasti said:
Sir, we want to change LTE frequency
thru QPST
Need help
Check here and please help us
Click to expand...
Click to collapse
Just head on to this thread. If you have anymore question, just don't hesitate to ask me.
tirta.agung said:
Just head on to this thread. If you have anymore question, just don't hesitate to ask me.
Click to expand...
Click to collapse
Sir
I already try that but stuck on YU Diagnostics Driver
OPO drivers not working for me
From where I get that
How to revert this command (old USB setting)
setprop sys.usb.config diag,adb
tirta.agung said:
Just head on to this thread. If you have anymore question, just don't hesitate to ask me.
Click to expand...
Click to collapse
Go till step 8 (with force install drivers) successfully
when Open QPST Configuration, go to the Ports tab, Add New Port .....
QPST stop working...
Flash rmt_storage patch device go bootloop
Thank God I make orignal rmt_storage patch zip
now device working
but QPST still not working
Help me please
something wrong with QPST
tirta.agung said:
Just head on to this thread. If you have anymore question, just don't hesitate to ask me.
Click to expand...
Click to collapse
I follow this Thread
Do complete process successfully :good:
all done
recheck repeat step 1 to 13
digits also changed
but until now show H or H+
is there any way to know which band is active now??
@hem12
tirta.agung said:
Hi there Quakze, I just wonder is it only the two of us who are interested in reviving death YUs? By the way, at last I hard bricked my Yu, and I think it is true that curiosity kills. Hahahaha, so yippee for me .
Ok, back to our business, I only know three major companies who always pack qualcomm's mbn files in their firmwares, they are Lenovo, Xiaomi, and Hisense. So, if you have time to wait you can hunt these phone firmwares when they released:
Hisense HS-H910 TD-LTE (expected release firmware June 2015)
Lenovo Vibe X2 PRO Dual SIM LTE (expected release firmware June 2015)
Lenovo Vibe Shot Dual SIM LTE (expected release firmware June 2015)
Xiaomi Ferrari (expected release firmware unknown)
However, if you are curious enough to find out by yourself on how to create qualcomm's mbn file for our YUs, then we can join hands in this thread.
And this is an update from me on my effort in reviving my death YU. When I did hex readings on some CPB files, I found out that each of those files contain at least one msimage.mbn. That is why, I spend my last weekend just to do some research on Coolpad Download Assistant (CDA) Software in order to hack it, and the good news is I managed to do it.
So with this post, I have attached the hacked version of our beloved CDA software. All you have to do is just download and unzip the zip file attached in this post, install the software and copy paste the "dProdRes.dll" into Coolpad Download Assistant installation directory. Afterwards, run the program as usual, put the right path of the CPB file you want to unpack and press "ok" (of course the language use by the software is in chinese). You will find the unpack CPB files inside "DownFiles" folder found in Coolpad Download Assistant installation directory.
Please post me a reply if you have succeeded in unpacking the CPB files, and tell me what do you think about the unpacked files, as I did find some strange stuff inside it .
Click to expand...
Click to collapse
Succeeded in unpacking the CPB, and there much needed files. I tried with version 27, now I am downloading version 40.
Will start testing with these files, hope for success :good:
BTW, U did a great job in cracking the CDA, Thank You
Boot image, MTP, Diag, and ADB all at one
ekhasti said:
I follow this Thread
Do complete process successfully :good:
all done
recheck repeat step 1 to 13
digits also changed
but until now show H or H+
is there any way to know which band is active now??
@hem12
Click to expand...
Click to collapse
Congratulations my friend, but don't forget to say thanks to devilsshadow and Albirew for their tips.
As for the changes, did you do these things before you change all the parameter with QXDM:
Put out all your sim cards from the phone?
While in qxdm, did you put a check mark on the dual sim option and applied all changes to both sims (sim0 and sim1)?
Perhaps you could also try typing *#*#4636#*#* via your phone dialer, and I think there will be some debug menu, hahaha my phone is bricked remember. But, if you want to know for sure, put a different card that use a different frequencies.
Here, I would also like to share a different method, besides using "setprop" command, to connect our YU with QPST or QXDM:
Download and unzip the attach file. You will find a boot image and a qualcomm driver inside it.
Uninstall all drivers that you have installed previously, and then install the qualcomm driver according to the type of your Windows (x64 or x86).
Copy the boot image into your phone internal storage.
Open the build.prop inside your phone "/system" directory, and find this line "persist.sys.usb.config="
If you found that line, then erase the whole line, if you can't find it then proceed to the next step.
Connect your phone with your PC, and open ADB (here, I assume you have already root you YU).
type:
Code:
adb shell
su
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p20"
reboot
After the phone rebooted, open device manager in windows, and you should find that your phone is recognised as "Qualcom HS-USB Diagnostics 903A"
Now you can connect to QPST, QXDM, ADB, and MTP at one, every time you phone rebooted
By the way I recommend you to backup your fsc, fsg, modemst1, and modemst2 before you messed things up, by doing some steps below:
Connect your phone with ADB.
Type:
Code:
adb shell
su
dd if=/dev/block/mmcblk0p15 of=/sdcard/fsc.mbn
dd if=/dev/block/mmcblk0p22 of=/sdcard/fsg.mbn
dd if=/dev/block/mmcblk0p12 of=/sdcard/modemst1.mbn
dd if=/dev/block/mmcblk0p13 of=/sdcard/modemst2.img
You will find your backup files in your internal storege
quakze said:
Succeeded in unpacking the CPB, and there much needed files. I tried with version 27, now I am downloading version 40.
Will start testing with these files, hope for success :good:
BTW, U did a great job in cracking the CDA, Thank You
Click to expand...
Click to collapse
Did you find MPRG8639.hex or MPRG8639.mbn in your CPBs ? Do you notice that all the qualcomm files inside have 8936 marking, not 8939, which is the chipset code of our YU? Strange indeed, it makes me wonder whether MSM8936 (snapdragon 610) has the same enumeration with MSM8939 (snapdragon 615). By the way, I'm still stuck with all those files found in the CPBs. I have use QPST and QFIL, but nothing avail.
@tirta.agung
When I reboot device all settings gone
I search & found there is some lock with NV in CM
now all same as before
need that rmt_storage type trick (which you give me link of OPO) for unlock
is that boot.img which you share here work for this??
---------- Post added at 07:22 AM ---------- Previous post was at 07:12 AM ----------
As for the changes, did you do these things before you change all the parameter with QXDM:
Put out all your sim cards from the phone?
While in qxdm, did you put a check mark on the dual sim option and applied all changes to both sims (sim0 and sim1)?
Click to expand...
Click to collapse
No.. Don't mention any where so miss these both point.
Perhaps you could also try typing *#*#4636#*#* via your phone dialer, and I think there will be some debug menu, hahaha my phone is bricked remember. But, if you want to know for sure, put a different card that use a different frequencies.
Click to expand...
Click to collapse
Don't found any debug menu..
Here, I would also like to share a different method, besides using "setprop" command, to connect our YU with QPST or QXDM:
Download and unzip the attach file. You will find a boot image and a qualcomm driver inside it.
Uninstall all drivers that you have installed previously, and then install the qualcomm driver according to the type of your Windows (x64 or x86).
Copy the boot image into your phone internal storage.
Open the build.prop inside your phone "/system" directory, and find this line "persist.sys.usb.config="
If you found that line, then erase the whole line, if you can't find it then proceed to the next step.
Connect your phone with your PC, and open ADB (here, I assume you have already root you YU).
type:
Code:
adb shell
su
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p20"
reboot
After the phone rebooted, open device manager in windows, and you should find that your phone is recognised as "Qualcom HS-USB Diagnostics 903A"
Now you can connect to QPST, QXDM, ADB, and MTP at one, every time you phone rebooted
Click to expand...
Click to collapse
this portion is new for me :good:
This boot.img is modified? I think so..
Safe for YU?
By the way I recommend you to backup your fsc, fsg, modemst1, and modemst2 before you messed things up, by doing some steps below:
Connect your phone with ADB.
Type:
Code:
adb shell
su
dd if=/dev/block/mmcblk0p15 of=/sdcard/fsc.mbn
dd if=/dev/block/mmcblk0p22 of=/sdcard/fsg.mbn
dd if=/dev/block/mmcblk0p12 of=/sdcard/modemst1.mbn
dd if=/dev/block/mmcblk0p13 of=/sdcard/modemst2.img
You will find your backup files in your internal storege
Click to expand...
Click to collapse
That useful tip for me
Thanks a lot for all this
This QPST stuff use first time
so sorry if I ask some idiotic
and sorry for my horriable ENGLISH :silly:
tirta.agung said:
Did you find MPRG8639.hex or MPRG8639.mbn in your CPBs ? Do you notice that all the qualcomm files inside have 8936 marking, not 8939, which is the chipset code of our YU? Strange indeed, it makes me wonder whether MSM8936 (snapdragon 610) has the same enumeration with MSM8939 (snapdragon 615). By the way, I'm still stuck with all those files found in the CPBs. I have use QPST and QFIL, but nothing avail.
Click to expand...
Click to collapse
What U say is right happened with me also, so trying different CBP.
ekhasti said:
@tirta.agung
This boot.img is modified? I think so..
Safe for YU?
Click to expand...
Click to collapse
Yup, it is a modified YU original boot image, I just made some changes in the default.prop, so it is 100% safe as long you use stock CM. Hahaha, btw I'm an Indonesian and my English is terrible as well, hehehehehe:laugh:
YUs eMMC Raw image through ADB
quakze said:
What U say is right happened with me also, so trying different CBP.
Click to expand...
Click to collapse
Hi Quakze, I think I made some progress, but have to reconfirm the steps that I have done, so I will post those steps later. But in a mean time, do you have a life YU? If you do, could you upload a full raw image of your life YU's eMMC image?
Here is the how to:
Put a 32GB of empty Micro SD in your life YU
Do a factory reset of your YU, or you can go to recovery by formatting cache and data.
Format all the content of your internal storage
Connect your phone with adb.
Type:
Code:
adb shell
su
dd if=/dev/block/mmcblk0 of=/storage/sdcard1/backup.img bs=512 count=30535646
[B]THIS PROCESS WILL TAKE AROUND 45-60 minutes, SO ADB WILL FREEZE FOR THAT MOMENT[/B]
When the above process has finished, go to your external storage of your YU, copy the backup.img (the size will be around 16GB) to your computer.
Zip your backup.img with the best compression method, and now you will get around 2GB of zip file.
Could you upload that zip file to this thread. I'm sure it will be valuable not just for both of us, but also to other YU owners in this forum.
Huawei Honor 7
– Complete Guide For Beginners –
Optimized For (PLK-L01)
Updating | Rooting | Tweaking | Fixing
In this guide, you will learn the following:
Part I - How to install the latest full ROM for Huawei Honor (PLK-L01).
Part II - How to root Huawei Honor 7.
Part III - How to fix bootloops if things did not go as expected.
Part IV - The most used adb commands.
Part V - The most used fastboot commands.
Part VI - How to change the default boot animation.
Part VII - How to change the default splash screen.
Appendix A - Honor 7 Key Combinations Summary.
Appendix B - How to update Huawei Honor 7 from (B100) to (B180).
Appendix C - Available Custom ROM(s).
Appendix D - Extra Resources.
Appendix E - All Important Downloads.
Notes & Credits:
This guide is written for the absolute beginners who had hard times reading other tutorials on this forum that explains the same set of topics.
This guide is primary written for Microsoft Windows users. Many sections though can be applied to other operating systems.
There are other great guides on this forum that teaches the same stuff but not in a very detailed beginner-friendly way. Special credits go to @piskr for his guide on this topic.
Additional credits go to @DigiGoon and @sminki for their contribution on fixing and updating this guide.
Special credits go to @Ziolek67 and @Kostyan_nsk for their original posts on the splash screen topics.
Special thanks to the Labinator team for their support throughout this guide.
If you have something to add or improve on this guide, please reply to this post and we will be more than happy to update it.
Warning: No one is responsible for what happens to your device while attempting to follow the below guide. Create backups before every section and know the risks before starting out.
Part I - How To Install The Latest Full ROM For The Model (PLK-L01)
Step 1: Download the latest full ROM for Honor 7 from the below link:
http://www.modaco.com/forums/topic/375942-roms-honor-7-stock-rom-images/
Step 2: Extract the (.zip) file and copy the "UPDATE.app" file to your (dload) folder in your external SD card.
Step 3: Make sure the current recovery that is installed is the default stock one and not a custom recovery like TWRP. If you have TWRP installed, make sure to flash the stock recovery before you attempt the update process.
Step 4: Turn off your phone, then press both the Volume Up + Volume Down + Power Key. Then release the power key as soon as you see the initial splash screen.
Step 5: The Huawei eRecovery will start and will update your device from the "UPDATE.app" file that you had placed in your (dload) folder automatically.
Part II - How To Root Huawei Honor 7
Stage 1 – Unlock The Bootloader
Part 1.1 – Getting The Unlock Password
Step 1: Login by clicking here.
Step 2: Click on “Unlock Bootloader”.
Step 3: Accept the unlocking agreement.
Step 4: Fill up the unlock password form as follows:
Product: Smartphone.
Model: (e.g. PLK-L01)
Product Serial Number: Settings -> Status -> Serial Number - > (e.g. H8WDU15814000010)
Product IMEI/MEID (IMEI 1): Settings -> Status -> IMEI1 -> (e.g. 867898020305536)
Product ID: Open the dial up and type: *#*#1357946#*#* -> (e.g. 88429554)
Verification Code: Type the Captcha.
Step 5: Press submit and obtain the unlocking password in red (e.g. 1078018121593242).
Step 6: Store the code obtained in step 5 somewhere safe.
Part 1.2 – Preparations
Step 6: Download and install the latest version of the "15 Seconds ADB Installer”. You can find the download link at >
http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
Step 7: Download and install the latest version of “HiSuite – Android Smart Device Manager”.
You can find the download link at >
http://consumer.huawei.com/minisite/HiSuite_en/
Step 8: Enable the “Developer options” by going to:
Settings -> About Phone -> Build Number
Tap on the build number 10 times quickly. A message must appear alerting you that the developer mode has been enabled.
Go to the “Developer options” and enable “USB debugging”.
Part 1.3 – Booting into Fastboot Mode
Step 9: Power the phone off.
Step 10: Boot the phone into “fastboot mode” by pressing the below keys.
[Volume Down] + [Tap on Power Button]. You can release the power button as soon as you see the initial splash screen.
Note 1: You must enter the fastboot mode directly after pressing the above keys.
Note 2: In case (Step 10) did not work, then turn off your phone again then insert the USB cable and connect it with your computer. After that, press the same combination mentioned above for 10 seconds. Note 3: You can also boot into the fastboot mode using the following command >
Code:
adb reboot bootloader
Step 11: Connect your phone with your PC. Use a USB cable to connect your phone with your computer while your phone is in the fastboot mode.
Step 12: Open your “Command Prompt (cmd)” and type >
Code:
fastboot devices
Note: The second command must show that your device is in fastboot mode.
Part 1.4 – Perform The Unlock Command
Step 13: Perform the unlock command > fastboot oem unlock ***, where *** is the 16 characters unlock code.
Code:
fastboot oem unlock 1078018121593242
Note: You need of course to replace "1078018121593242" with your unique 16 characters unlock code.
Step 14: Wait for the phone to get unlocked. It will automatically restart if you have entered the correct code.
Step 15: Test if the phone is successfully unlocked by entering the following command >
Code:
fastboot oem get-bootinfo
Case 1: If you have got the message of “Bootloader Lock State: UNLOCKED”, then your phone has been successfully unlocked.
Case 2: If you have got the message of “Bootloader Lock State: LOCKED”, then your phone is still locked.
Note: if you want to re-lock the phone, please check this thread for more details on that. Thanks to @sminki for posting that up and highlighting this point.
Stage 2 – Install Custom Recovery
Step 16: Open your command prompt, and navigate to the right directory where your recovery image file is located. You can do that using this command:
Navigate to the right directory:
[“Directory Letter”]:
Examples: D:, C:, or E:
Navigate to the right folder:
cd [“Full Path Of Directory”]
Example: cd /Users/User1
Step 17: Test if your device is detected by typing the following command while you are in the bootloader mode:
Code:
fastboot devices
> If you got the right messages that your device is properly connected, then you can proceed to step 18.
Step 18: Type the following command to flash the recovery image (TWRP). The recovery image is in English and you can download it from this link. Make sure to download it and place it in the right directory before typing the below command line.
Code:
fastboot flash recovery recovery.img
After the completion of that, simply reboot your device using the following command >
Code:
fastboot reboot
Note: “recovery.img” is the name of the TWRP recovery image. You need to replace this name with the name of your recovery image (e.g. twrp-3.0.2-0-plank.img).
Stage 3 – Root The Device
Step 19: Download the latest SuperSU version from this link and place it on your hard disk then copy it to your phone. You can copy the file from your computer to your device using this command >
Code:
adb push SuperSU-vX.zip /sdcard/
Note 1: You must be in the right directory of the “SuperSU” file or else the above command will not work.
Note 2: You must replace "SuperSU-vX" with the right name of your SuperSU file (e.g. BETA-SuperSU-v2.71-20160331103524.zip)
Step 20: When the process of flashing the recovery is done, reboot your device into the recovery mode using the following command >
Code:
adb reboot recovery
Step 21: After finishing step 20 successfully, your phone would have been booted into the recovery mode. You will be able to see the TWRP home screen. From there, click on the “Install” option then navigate to your /sdcard/ directory where you have copied or pushed your "SuperSU-vX.zip" file.
Step 22: Find the "SuperSU-vX.zip" file and install it.
Step 23: Navigate back to the home page of TWRP then click on the “Reboot” button in order to boot into the system.
Step 24: Double check if your device has been rooted successfully by testing it using one of those root checker applications. There are many of them around the Google Play store.
Part III - Useful ADB Commands
Code:
adb devices
adb reboot
adb reboot bootloader
adb reboot recovery
adb push [source] [destination]
adb pull [source] [destination]
adb backup
adb shell
Part IV - Useful Fastboot Commands
Code:
fastboot devices
fastboot reboot
fastboot reboot-bootloader
fastboot boot recovery recovery.img
fastboot flash [Partition] [Image]
fastboot oem unlock [Unlock Code]
fastboot oem relock [Relock Code]
Note: Use your favorite search engine to search the above commands and learn more about them.
Part V - How To Fix Bootloops
Breaking out of bootloops depends on your device state and what kind of problem you are having. In this section, we are going to focus on the popular case where you can’t access neither the system nor the recovery partitions.
Step 1: Turn off the phone.
Step 2: Press the following buttons:
[Volume Down] + [Tap on Power Button]. You can release the power button as soon as you see the initial splash screen.
Step 3: Head to your computer and download and install the following tool:
http://forum.xda-developers.com/showthread.php?t=2433454
Step 4: Download the latest complete update file (B121) or (B330b) depending on which system you had installed before the bootloop problem. You can download it from:
http://www.modaco.com/forums/topic/375942-roms-honor-7-stock-rom-images-updates-121115-b140/
Then, extract it and get its UPDATE.app file.
Step 5: Use the Huawei Update Extractor to extract the (BOOT.img), (SYSTEM.img), (RECOVERY.img), (CACHE.img), (CUST.img), and (USERDATA.img) from the UPDATE.app file that you have extracted from Step 4.
Step 6: Open your command prompt, and navigate to the right directory where you have extracted the image files. Use the “cd” and “..” commands to do so.
Step 7: Type the following commands and execute them one by one >
Code:
fastboot flash boot BOOT.img
fastboot flash system SYSTEM.img
fastboot flash recovery RECOVERY.img
fastboot flash cache CACHE.img
fastboot flash cust CUST.img
Step 8: You can also erase the user data if you like by typing and executing the following >
Code:
fastboot flash userdata USERDATA.img
Step 9: Reboot your device using the following command >
Code:
fastboot reboot
Step 10: You must be able to boot successfully into the system.
Step 11: After booting successfully, apply again the steps mentioned in Part I.
Important Note 1: If the "fastboot flash" is reporting "FAILED <remote: command not allowed>", you need to unlock your device again even if the bootloader is stating that your device has already been unlocked.
Important Note 2: When breaking out of bootloops or frozen splash screens, you need always to flash the right partitions that match up with the previous partitions that you had installed on your system before the occurrence of the bootloop.
Part VI - How To Change The Boot Animation
Step 1: Root Your Device.
Step 2: Create a full Nandroid backup.
Step 3: Create your own animation or download one online. Note that you need the resolution to be (1080 x 1920 pixels). It should not last more than 10-12 seconds at most.
Step 5: Your animation files must be compressed and renamed as: “bootanimation.zip”.
Step 6: Change the permissions of your .zip file to (rw-r-r).
Step 7' - (In case you are running Android 5.x): Navigate to /Cust/Preinstalled/Public/Media and backup the original “bootanimation.zip” file somewhere safe on your hard drive or sdcard.
Step 7'' - (In case you are running Android 6.x): Navigate to /system/etc/media and backup the original “bootanimation.zip” file somewhere safe on your hard drive or sdcard.
Step 8' - (In case you are running Android 5.x): Copy your newly created bootanimation.zip file to the directory /Cust/Preinstalled/Public/Media and replace the original file.
Step 8'' - (In case you are running Android 6.x): Copy your newly created bootanimation.zip file to the directory /system/etc/media and replace the original file.
Step 9: Reboot and check up your new boot animation.
My original post of this section is available at: http://forum.xda-developers.com/showpost.php?p=63828825&postcount=2
Part VII - How To Change The Splash Screen
Requirements:
Your device must be rooted. Follow the steps in Part II in case you have not rooted your device yet.
You must have downloaded and installed the latest version of the "15 Seconds ADB Installer”.
You can find the download link at: http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
You need to make a complete backup or a nandroid backup before starting up. You can create a nandroid backup using the custom recovery of TWRP.
Steps:
Turn on your device and connect it to your computer then open the command prompt or your terminal as an administrator.
Make sure your computer can read the data on your phone and all the drivers are installed properly.
Make sure the following command is returning the name of your device:
Code:
adb devices
Save your "oeminfo" to your SDCard:
Code:
adb shell su -c "dd if=/dev/block/platform/hi_mci.0/by-name/oeminfo of=/sdcard/oeminfo"
Download this zip file and extract it to your desktop or any location of your choice.
From your opened command prompt, navigate to the extracted zip folder that you have downloaded in Step 5. Use the "cd" command to do that.
Create your new splash screen logo as follows:
Step 1: Open your Adobe Photoshop and create a new file that has the following parameters
Width: 1080 pixels
Height: 1920 pixels
Resolution: 72 pixels/inch
Color Mode: RGB Color, 8-bit
Step 2: After creating your new image, save it as follows:
Extension: *.bmp
From the "Advanced Options", select R5 G6 B5 from the 16-bit depth options.
Save your newly created image in Step 7, in the same folder that you have extracted in Step 5.
From your command prompt, type the following command:
Code:
OEM_logo.exe oeminfo your_logo.bmp
Replace "your_logo.bmp" with the name of your logo.
The above command will create a new oeminfo for you that has your new logo. It will also replace the old one in the same folder.
Copy your newly created oeminfo to your sdcard by typing the following command:
Code:
adb push oeminfo /sdcard/oeminfo
Copy your oeminfo from your sdcard to the right partition on your device:
Code:
adb shell su -c "dd bs=32768 if=/sdcard/oeminfo of=/dev/block/platform/hi_mci.0/by-name/oeminfo"
Reboot your device and check the new splash screen.
Note: The original post of this section can be found at this link.
Credits: Special credits goes to @DigiGoon, @sminki, @Ziolek67, and @Kostyan_nsk for their amazing contribution in writing, testing, and adjusting on the original post of this section of the guide.
Appendix A - Honor 7 Key Combinations Summary
[Without Plugging The Device]:
Volume Down + Tap Power Button -> Normal Boot.
Volume Up + Tap Power Button -> Recovery Mode (e.g. TWRP).
Both Volume Buttons + Tap Power Button -> Flash (dload) Image From External MicroSD Card.
[While Connecting The Device To Your Computer]
Volume Down + Power On -> Fastboot Mode - (Tip: You can exit from this mode with a long power button press).
Volume Up + Power On -> Huawei eRecovery.
Both Volume Buttons + Power On -> Flash Image via HiSuite.
Appendix B - How To Update From B100 to B180
For The Model (PLK-L01)
Important Note: Please update your device before rooting it. You will lose your root access if you attempt to update after rooting your device.
Step 1: Download the latest stock ROM for Honor 7 from the below link:
http://www.modaco.com/forums/topic/375942-roms-honor-7-stock-rom-images/
Step 2: Download the B121 EMUI 3.1 update package.
Step 3: Download the B180 incremental update package (B121 to B180).
Step 4: Extract the B121 update zip file and get the UPDATE.app file from it.
Step 5: Copy the UPDATE.app file from your computer to the /sdcard/dload/ directory.
Step 6: Launch your device and go to: Settings -> Updater -> Menu -> Local Update and choose the UPDATE.app file.
Step 7: Install the update and wait until it reboots again. Check if the update is working successfully.
Step 8: Copy the B180 (B121 to B180) incremental update zip file from your computer to the /sdcard/dload/ directory.
Step 9: Make sure the name of your update zip file is “update.zip”.
Step 10: Apply the update by going to: Settings -> Updater -> Menu -> Local Update and choosing the update.zip file.
Step 11: Install the update and wait until it reboots again. Check if the update is working successfully.
Step 12: Delete the update.zip file from your /sdcard/dload/ directory.
Appendix C - Available Custom ROM(s)
r3 - Custom Rom Starter Template: http://forum.xda-developers.com/honor-7/development/r1-custom-rom-starter-template-honor-7-t3337901
r2 - MoDaCo Custom Kernel: http://forum.xda-developers.com/honor-7/development/kernel-r1-modaco-custom-kernel-t3365909
MoDaCo Custom Rom: http://forum.xda-developers.com/honor-7/development/r1-custom-rom-starter-template-honor-7-t3337901
YodaRom: http://forum.xda-developers.com/honor-7/development/rom-6-0-x-yodarom-v1-0-mm-rooted-ads-t3338179
DigiRom: http://forum.xda-developers.com/honor-7/development/rom-digirom-gpe-v1-t3365391
H7T Rom: http://forum.xda-developers.com/honor-7/development/rom-codename-h7t-t3396002
You can view all available custom ROM(s) at: http://forum.xda-developers.com/honor-7/development
Appendix D - Extra Resources
How to build your own kernel for Honor 7: http://forum.xda-developers.com/honor-7/general/guide-how-to-build-kernel-honor-7-t3363894
Honor 7 Multi-Tool: http://forum.xda-developers.com/honor-7/general/honor-7-multi-tool-t3281176
Spectrum Pure Theme: http://forum.xda-developers.com/honor-7/themes-apps/theme-spectrum-pure-base-theme-t3321234
Appendix E - All Important Downloads
All Stock ROMs and OTA Updates: http://www.modaco.com/forums/topic/...ck-rom-images-updated-1st-april-2016-plk-l01/
The Latest Version Of "TWRP": https://dl.twrp.me/plank/
The Latest Version Of "SuperSU": https://download.chainfire.eu/supersu
The Latest Version Of "15 Seconds ADB Installer": http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
The Latest Version Of "Huawei Update Extractor": http://forum.xda-developers.com/showthread.php?t=2433454
Access the "Huawei Bootloader Unlocker": https://hwid5.vmall.com/oauth2/portal/cloud_login.jsp
Awesome and very helpful guide @kenshiwara
Thank you for this guide.
If I understand, we can update if twrp is installed?
Envoyé de mon Nexus 5
No offence but this is just @piskr 's thread re-typed with some serious errors added to it.
Did you try "fastboot oem relock"? I started a thread on that, it doesn't work.
Did you try any of the "fastboot erase" commands? As when I tried it wouldn't - "Command not allowed"
The Huawei extract tool doesn't get the names of the images on the current full ROMS (tested on B121 and a few of the Chinese ROMS) it doesn't have the mappings for these. However it has worked with incremental patches..
Extracting the files and only flashing a few like system will leave you with and inconsistent device (if from different versions). Those 20+ files have a reason - modem, sensorhub, trustfirmware, teeos (whatever that is!), etc.. There are actually something like 40 block devices on the H7 (/dev/block/platform/hi_mci.0/by-name/). To run an official update on that system would almost certainly result in failure. (I have tried)
..and flashing a whole system doesn't fix a boot-loop. That's flashing the whole system, it goes away because whatever was causing it has been deleted/wiped. If that's the idea, better off flashing Huawei's recovery and doing a full UPDATE.APP of B100 / B121 and moving up.
Oh and just one more minor thing - holding the power button isn't required, turn the phone on and hold either down (with usb data connected) for boot-loader, or up for recovery
Sorry... I know you mean well, however posting things in good faith is dangerous. Especially in a guide aimed at beginners.
sminki said:
No offence but this is just @piskr 's thread re-typed with some serious errors added to it.
Did you try "fastboot oem relock"? I started a thread on that, it doesn't work.
Did you try any of the "fastboot erase" commands? As when I tried it wouldn't - "Command not allowed"
The Huawei extract tool doesn't get the names of the images on the current full ROMS (tested on B121 and a few of the Chinese ROMS) it doesn't have the mappings for these. However it has worked with incremental patches..
Extracting the files and only flashing a few like system will leave you with and inconsistent device (if from different versions). Those 20+ files have a reason - modem, sensorhub, trustfirmware, teeos (whatever that is!), etc.. There are actually something like 40 block devices on the H7 (/dev/block/platform/hi_mci.0/by-name/). To run an official update on that system would almost certainly result in failure. (I have tried)
..and flashing a whole system doesn't fix a boot-loop. That's flashing the whole system, it goes away because whatever was causing it has been deleted/wiped. If that's the idea, better off flashing Huawei's recovery and doing a full UPDATE.APP of B100 / B121 and moving up.
Oh and just one more minor thing - holding the power button isn't required, turn the phone on and hold either down (with usb data connected) for boot-loader, or up for recovery
Sorry... I know you mean well, however posting things in good faith is dangerous. Especially in a guide aimed at beginners.
Click to expand...
Click to collapse
Thank you for your comments and notes. It is great to see your contribution up there.
This was actually my personal guide that i wrote to help myself around while operating on this device (PLK-L01). Based on your comments, there are several sections that require fixing. Would you mind taking the time to re-write those sections in a step-by-step fashion in order to update the guide?
You disagree with the section of "How to fix the bootloop when you can't access neither the system nor the recovery partitions". My solution - which worked for me - was to erase and flash the main partitions. Still though, if you have a better method, please share it with the whole community in a step-by-step fashion. Everyone will be grateful.
We mainly need the following:
1. How to re-lock the phone if the command of "fastboot oem relock" is not working on some models?
2. How to break out of bootloops if we can't access the system or the recovery partitions? (and flashing the main partitions from fastboot is not a stable solution in your opinion).
If you can provide a detailed step-by-step guides addressing the above two points, i would surely be more than happy to update them in the guide. Please note that the above guide is mostly tested on PLK-L01. Please, always mention your model number when writing your notes.
Thanks again for sharing your results with the community and hope you can send us a better version on the above sections based on your findings.
Freebob94 said:
Thank you for this guide.
If I understand, we can update if twrp is installed?
Click to expand...
Click to collapse
TWRP is not required at all if you are just updating. You should root your device after applying all the updates rather than before.
Thank you for comment!
sminki said:
Did you try "fastboot oem relock"? I started a thread on that, it doesn't work.
Did you try any of the "fastboot erase" commands? As when I tried it wouldn't - "Command not allowed"
Click to expand...
Click to collapse
Well me and @kenshiwara both tried it after stucking in bootloop and those commands worked like a charm
kenshiwara said:
Thank you for your comments and notes. It is great to see your contribution up there.
Thanks again for sharing your results with the community.
Click to expand...
Click to collapse
I'm glad you too my reply as intended and not just an angry rant!
DigiGoon said:
Well me and @kenshiwara both tried it after stucking in bootloop and those commands worked like a charm
Click to expand...
Click to collapse
Guessing by your location, you have the Indian single sim version?
sminki said:
I'm glad you too my reply as intended and not just an angry rant!
Guessing by your location, you have the Indian single sim version?
Click to expand...
Click to collapse
No, I have European model PLK-L01, thanks to @kenshiwara
---------- Post added at 07:48 PM ---------- Previous post was at 07:46 PM ----------
sminki said:
I'm glad you too my reply as intended and not just an angry rant!
Click to expand...
Click to collapse
LOL, yeah, some people or developers would have taken it as angry rant but we all are here to learn and help each other.
OK, well I also have an EU PLK-L01 with unlocked bootloader. I re-tested the following today to confirm my initial findings:
fastboot oem get-bootinfo
Code:
...
[COLOR="Green"][B](bootloader) unlocked[/B][/COLOR]
OKAY [ 0.000s]
finished. total time: 0.000s
fastboot erase system
Code:
erasing 'system'...
[COLOR="Red"][B]FAILED (remote: Command not allowed)[/B][/COLOR]
finished. total time: 0.000s
fastboot erase userdata
Code:
erasing 'userdata'...
[COLOR="Red"][B]FAILED (remote: Command not allowed)[/B][/COLOR]
finished. total time: 0.000s
fastboot -w
Code:
Erase successful, but not automatically formatting.
[B]Can't determine partition type.[/B]
[COLOR="Red"][B]FAILED (remote: Command not allowed)[/B][/COLOR]
Erase successful, but not automatically formatting.
[B]Can't determine partition type.[/B]
[COLOR="Red"][B]FAILED (remote: Command not allowed)[/B][/COLOR]
erasing 'userdata'...
[COLOR="Red"][B]FAILED (remote: Command not allowed)[/B][/COLOR]
finished. total time: 0.000s
This was the same for any of the B1xx firmwares.
DigiGoon said:
Well me and @kenshiwara both tried it after stucking in bootloop and those commands worked like a charm
Click to expand...
Click to collapse
You locked the bootloader to fix boot-loop? That's a bad idea!
sminki said:
You locked the bootloader to fix boot-loop? That's a bad idea!
Click to expand...
Click to collapse
Never locked it, just flashed SYSTEM.img by executing
Code:
fastboot flash system SYSTEM.IMG
and it worked.
DigiGoon said:
Never locked it, just flashed SYSTEM.img by executing
Code:
fastboot flash system SYSTEM.IMG
and it worked.
Click to expand...
Click to collapse
Well, in post #7 you wrote this:
------------------------------------------
{
"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"
}
------------------------------------------
However, your answer above says otherwise. Erase and flash are not the same thing
One of my main criticisms on the original post was that fastboot erase doesn't work, I went a long way to back this up in post #10
sminki said:
Well, in post #7 you wrote this:
------------------------------------------
------------------------------------------
However, your answer above says otherwise. Erase and flash are not the same thing
One of my main criticisms on the original post was that fastboot erase doesn't work, I went a long way to back this up in post #10
Click to expand...
Click to collapse
Sorry, that was my mistake but I never erased the partition, directly flashed it
DigiGoon said:
Sorry, that was my mistake but I never erased the partition, directly flashed it
Click to expand...
Click to collapse
Cool thanks. I can sleep easy now :highfive:
sminki said:
Cool thanks. I can sleep easy now :highfive:
Click to expand...
Click to collapse
I have updated the original thread highlighting your comments while fixing it according to our latest tests. Please read it up again and inform us if you have anything else to improve on it.
Out of 500 views, only you decided to take few minutes and help in improving this guide. Thank you for your time and know that your support will be appreciated by all the community of XDA-Developers.
Hi there beautiful people.
I'm getting some error updating after installing tw recovery.
Code:
Checking MD5 file...
Skipping MD5 check: no MD5 file found
file_getprop: failed to start
E:Error executing updater binary in zip '/external_sd/dload/update.zip
E:Error installing zip file '/external_sd/dload/update.zip
Now backupping, i'm going to try to flash the zip (i'ts a stupid thing?).
Edit: Did not work either. Cannot update using twrp; the update app reboots directly in the custom recovery.
Currently on B121, it already had it. PLK-L01 europe.
Also, do you really think Haweii will public codes? I'm not so optimistic.
Smokehrbar88 said:
Hi there beautiful people.
I'm getting some error updating after installing tw recovery.
Code:
Checking MD5 file...
Skipping MD5 check: no MD5 file found
file_getprop: failed to start
E:Error executing updater binary in zip '/external_sd/dload/update.zip
E:Error installing zip file '/external_sd/dload/update.zip
Now backupping, i'm going to try to flash the zip (i'ts a stupid thing?).
Currently on B121, it already had it. PLK-L01 europe.
Also, do you really think Haweii will public codes? I'm not so optimistic.
Click to expand...
Click to collapse
If that update.zip is from Huawei it won't work in TWRP.
You need Huawei recovery to install Huawei updates.
sminki said:
If that update.zip is from Huawei it won't work in TWRP.
You need Huawei recovery to install Huawei updates.
Click to expand...
Click to collapse
Indeed, it sounds pretty logic. So i should revert the stock recovery, update and then reinstall twrp.
Can I do it simply pushing trough adb? And where should I find the recovery.img?
Thanks for the help.
Smokehrbar88 said:
Indeed, it sounds pretty logic. So i should revert the stock recovery, update and then reinstall twrp.
Can I do it simply pushing trough adb? And where should I find the recovery.img?
Thanks for the help.
Click to expand...
Click to collapse
You have to extract them from the UPDATE.APP file!
I've done the work for you.. B121 recovery attached
Unizp, then
Code:
fastboot flash recovery B121_recovery.img
(like you did with twrp)
Then put TWRP back on.
I forgot to add - if the system partition is altered (su) then the official update may well fail..
sminki said:
I've done the work for you.. B121 recovery attached
Click to expand...
Click to collapse
I was downloading the full rom myself, but my internet speed is so slow. My savior, thank you. I hope to not bother you again with my low-tier noob problems.
Use it if you cannot flash with any flash tool (no root needed)
Note: Use this at your own risk! Use it as a last resort!
I'm not responsable for anything, this may not work with yours
Sorry for my poor english. I tested this method with MY bricked LG F320L, no root, no boot, no many partition pop up, partial
downloadMode (just download mode and can't see the USB logo nor S/W update) then can't flash with KDZ/TOT file,with adb mode
recovery when holding pwr and vol+ ( lucky ), with stock recovery but I have to write adb reboot recovery to get it
what you need (sorry, I'm too lazy to put a direct link, I found all of them in xda):
- Install driver for your device
- .kdz file of your model
- WindowsLGFirmwareExtract-1.2.5.0-Release
- Send_Command.exe and ports.bat (ports.bat is optional if you know the port where your device is plunged can be in LG_root.zip)
This methode needs that you can access to downloadmode or partial downloadmode like me (vol+ and plug USB cable)
1- Run WindowsLGFirmwareExtract
. browse your .kdz file with "Open" button
. click to "Extract KDZ" button and wait until finish
. browse the .dz file abd extract it with the appropriat button
. click to "Extract DZ" button and wait until finish
. select all system files and clic Merge system-bin (you will get system.img in another folder and you don't need all system****.bin)
. copy all files in same folder
2- change extension of all files .bin to .img and remove any numbers
example: aboot156.bin => aboot.img / 1-aboot.bin =>aboot.img
3- Push or copy all files to your device. You have to find also the laf.img of your device, sometime it's not in the KDZ file.
Maybe it's optional, but I'm not sure.
Remember the path, for this tuto I'm using adb and push all files to /data/local/tmp/
You can also copy all files with another method
4- Run Ports.bat
Double click ports.bat (This will give us the COM port in which our device is connected we are looking for the Diag port)
keep in mind the COM of \Device\LG*******DIAG*
5- Go to downloadMode
6- Run send_command.exe in command prompt
type: Send_Command.exe \\.\COM3 if COM3 is the port where your device is pluged
wait for #
flash all .img like this, replace NAME by the name of the file ex: aboot.img replace NAME by aboot
dd if=/data/local/tmp/{NAME}.img of=/dev/block/platform/msm_sdcc.1/by-name/{NAME}
ex: dd if=/data/local/tmp/aboot.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
Except for backupGPT.img, I don't know what is it. Maybe in this partition:
dd if=/data/local/tmp/backupGPT.img of=/dev/block/platform/msm_sdcc.1/by-name/gpt
personally , I have not flashed this one
If you have finished type: LEAVE
Flash completed
Thank you guy, your tuto saved my device
santatralalaina said:
Use it if you cannot flash with any flash tool (no root needed)
Note: Use this at your own risk! Use it as a last resort!
I'm not responsable for anything, this may not work with yours
Sorry for my poor english. I tested this method with MY bricked LG F320L, no root, no boot, no many partition pop up, partial
downloadMode (just download mode and can't see the USB logo nor S/W update) then can't flash with KDZ/TOT file,with adb mode
recovery when holding pwr and vol+ ( lucky ), with stock recovery but I have to write adb reboot recovery to get it
what you need (sorry, I'm too lazy to put a direct link, I found all of them in xda):
- Install driver for your device
- .kdz file of your model
- WindowsLGFirmwareExtract-1.2.5.0-Release
- Send_Command.exe and ports.bat (ports.bat is optional if you know the port where your device is plunged can be in LG_root.zip)
This methode needs that you can access to downloadmode or partial downloadmode like me (vol+ and plug USB cable)
1- Run WindowsLGFirmwareExtract
. browse your .kdz file with "Open" button
. click to "Extract KDZ" button and wait until finish
. browse the .dz file abd extract it with the appropriat button
. click to "Extract DZ" button and wait until finish
. select all system files and clic Merge system-bin (you will get system.img in another folder and you don't need all system****.bin)
. copy all files in same folder
2- change extension of all files .bin to .img and remove any numbers
example: aboot156.bin => aboot.img / 1-aboot.bin =>aboot.img
3- Push or copy all files to your device. You have to find also the laf.img of your device, sometime it's not in the KDZ file.
Maybe it's optional, but I'm not sure.
Remember the path, for this tuto I'm using adb and push all files to /data/local/tmp/
You can also copy all files with another method
4- Run Ports.bat
Double click ports.bat (This will give us the COM port in which our device is connected we are looking for the Diag port)
keep in mind the COM of \Device\LG*******DIAG*
5- Go to downloadMode
6- Run send_command.exe in command prompt
type: Send_Command.exe \\.\COM3 if COM3 is the port where your device is pluged
wait for #
flash all .img like this, replace NAME by the name of the file ex: aboot.img replace NAME by aboot
dd if=/data/local/tmp/{NAME}.img of=/dev/block/platform/msm_sdcc.1/by-name/{NAME}
ex: dd if=/data/local/tmp/aboot.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
Except for backupGPT.img, I don't know what is it. Maybe in this partition:
dd if=/data/local/tmp/backupGPT.img of=/dev/block/platform/msm_sdcc.1/by-name/gpt
personally , I have not flashed this one
If you have finished type: LEAVE
Flash completed
Click to expand...
Click to collapse
help please
santatralalaina said:
Use it if you cannot flash with any flash tool (no root needed)
Note: Use this at your own risk! Use it as a last resort!
I'm not responsable for anything, this may not work with yours
Sorry for my poor english. I tested this method with MY bricked LG F320L, no root, no boot, no many partition pop up, partial
downloadMode (just download mode and can't see the USB logo nor S/W update) then can't flash with KDZ/TOT file,with adb mode
recovery when holding pwr and vol+ ( lucky ), with stock recovery but I have to write adb reboot recovery to get it
what you need (sorry, I'm too lazy to put a direct link, I found all of them in xda):
- Install driver for your device
- .kdz file of your model
- WindowsLGFirmwareExtract-1.2.5.0-Release
- Send_Command.exe and ports.bat (ports.bat is optional if you know the port where your device is plunged can be in LG_root.zip)
This methode needs that you can access to downloadmode or partial downloadmode like me (vol+ and plug USB cable)
1- Run WindowsLGFirmwareExtract
. browse your .kdz file with "Open" button
. click to "Extract KDZ" button and wait until finish
. browse the .dz file abd extract it with the appropriat button
. click to "Extract DZ" button and wait until finish
. select all system files and clic Merge system-bin (you will get system.img in another folder and you don't need all system****.bin)
. copy all files in same folder
2- change extension of all files .bin to .img and remove any numbers
example: aboot156.bin => aboot.img / 1-aboot.bin =>aboot.img
3- Push or copy all files to your device. You have to find also the laf.img of your device, sometime it's not in the KDZ file.
Maybe it's optional, but I'm not sure.
Remember the path, for this tuto I'm using adb and push all files to /data/local/tmp/
You can also copy all files with another method
4- Run Ports.bat
Double click ports.bat (This will give us the COM port in which our device is connected we are looking for the Diag port)
keep in mind the COM of \Device\LG*******DIAG*
5- Go to downloadMode
6- Run send_command.exe in command prompt
type: Send_Command.exe \\.\COM3 if COM3 is the port where your device is pluged
wait for #
flash all .img like this, replace NAME by the name of the file ex: aboot.img replace NAME by aboot
dd if=/data/local/tmp/{NAME}.img of=/dev/block/platform/msm_sdcc.1/by-name/{NAME}
ex: dd if=/data/local/tmp/aboot.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
Except for backupGPT.img, I don't know what is it. Maybe in this partition:
dd if=/data/local/tmp/backupGPT.img of=/dev/block/platform/msm_sdcc.1/by-name/gpt
personally , I have not flashed this one
If you have finished type: LEAVE
Flash completed
Click to expand...
Click to collapse
@santatralalaina
I'm in a similar situation like you. No download, fastboot or recovery and phone is not detected by Windows. As u said PARTIAL Download mode only. I'm not very good with adb also. Could you please guide me about force pushing of the .img files please! Where can I get send command.exe and ports.bat? Could you please attach some screen shot of Step:6. Renaming the file and command is bit confusing for me.
sms473 said:
@santatralalaina
I'm in a similar situation like you. No download, fastboot or recovery and phone is not detected by Windows. As u said PARTIAL Download mode only. I'm not very good with adb also. Could you please guide me about force pushing of the .img files please! Where can I get send command.exe and ports.bat? Could you please attach some screen shot of Step:6. Renaming the file and command is bit confusing for me.
Click to expand...
Click to collapse
Hi, Don't panic! Take a deep breath.
Firstly: What is your phone model?
Secondly: What happen when you plug your phone to your PC?
Finaly: What you have did to try unbricking you phone?
santatralalaina said:
Hi, Don't panic! Take a deep breath.
Firstly: What is your phone model?
Secondly: What happen when you plug your phone to your PC?
Finaly: What you have did to try unbricking you phone?
Click to expand...
Click to collapse
Hi..thanks for the reply....My phone is G2 F320L..Korean version with removable battery and SD card....I tried to install a non compatible ROM..got bricked with only fastboot...Then I try to flash aboot.bin..boot.bin..laf.bin..etc files (which I have extracted from the kdz) through fastboot...during flashing my phone was disconnecting and connecting back again...thats where all the problem started I guess. Now I dont have fastboot also. If i connect my phone to PC.. LG logo comes on the phone screen...on PC it try to detect as LGE android MTP devices and try to install the driver of the same. But the driver installation fails eventually.... At windows device manager it show as LGE Android MTP devices with error code 10...and showing connected to port:COM3....If I try to get in to the download mode..it get stuck at the (.............) download page...it is not going to the page with big USB picture...
My thinking is...Since the device manager is showing that it is connected at COM3.....Can I force flash the boot.img, aboot.img, laf.img etc files with "Send command.exe?
At least I can try to force flash right? If it is possible..may be I will be able to enter in to the download mode:fingers-crossed: Right? Where can I get this "Send command.exe" and how it works?
sms473 said:
My thinking is...Since the device manager is showing that it is connected at COM3.....Can I force flash the boot.img, aboot.img, laf.img etc files with "Send command.exe?
At least I can try to force flash right? If it is possible..may be I will be able to enter in to the download mode:fingers-crossed: Right? Where can I get this "Send command.exe" and how it works?
Click to expand...
Click to collapse
Hello,
It was easy to unbrick the fastboot but now... ok, you are stuck in LG LOGO but after no black screen? can you charge you battery? And if you try to go to RecoveryMode, what's happen? do you have multiple partitions and QHSUSB_DLOAD trying to be instaled? It's also easy to unbrick the QHSUSB and if it is the case, don't use send_command to flash manualy your device.
Maybe, you can force flash. You have to find a solution to push all .img files to your device. If you cannot use ADB, try to put the img files to sdcard.
you can found send_command.exe and ports.bat in this zip file, it's an utilities for having root on LG G2 :
LG_Root.zip
you can use all root command with it!
Added to index thread
[INDEX][LG G2] ROMs, Kernels, Guides and more
can this fix demigod crash handler? it has a partial download mode (located in drivers, but LG Flash Tool gets stuck in 4%)
I have a f320k, and because it died (i await u to answer me and tell me if its possible that it will fix it(
i am currently using a nearly dead battery nexus 5.
reply in ur free time
Well, I need help. how do i copy these files to my device? my device is not located in adb. cant i just flash the files from there place in my pc?
hi - I have t mobile d801 .it has boot loop - show lg logo and then the android robot and then lg logo again.
it does enter download mode(but with the 4 blue dots - but in the device manager cant install the drivers.
when the phone is plugged in to computer normally without download mode' it shows lge phone and drivers in device manager.
I tried to flash kdz bit stuck on 60%. it shows on phone download mode - but not show the firmware update logo.
what should I do?? when I d.mode not the regular d.mode - device isn't detected in pc. so I think this is my main problem.
try with srk tools no luck. its says waiting for device..is there any solution? thanks!
foxyfoxyblah said:
can this fix demigod crash handler? it has a partial download mode (located in drivers, but LG Flash Tool gets stuck in 4%)
I have a f320k, and because it died (i await u to answer me and tell me if its possible that it will fix it(
i am currently using a nearly dead battery nexus 5.
reply in ur free time
Click to expand...
Click to collapse
Hi!
As I known, LG G2 is unbrickable
This method is for last resort because I havn't complete documentation about this!
I've tested it with my own LG F320L only
Try to flash with TOT files or LGUP
Try to repair the download mode http://forum.xda-developers.com/showthread.php?t=2706590
Try to force the QHS_USB to appear then use the appropriate tools http://forum.xda-developers.com/lg-g2/general/file-unbrick-qualcomm-9006-qhsusb-t3056800
Try send_commande before shorting testpoint (it's less dangerous IN MY OPINION)
santatralalaina said:
Hi!
As I known, LG G2 is unbrickable
This method is for last resort because I havn't complete documentation about this!
I've tested it with my own LG F320L only
Try to flash with TOT files or LGUP
Try to repair the download mode http://forum.xda-developers.com/showthread.php?t=2706590
Try to force the QHS_USB to appear then use the appropriate tools http://forum.xda-developers.com/lg-g2/general/file-unbrick-qualcomm-9006-qhsusb-t3056800
Try send_commande before shorting testpoint (it's less dangerous IN MY OPINION)
Click to expand...
Click to collapse
I don't have ADB, so most of these i cant do.
im scared of touching the motherboard....
so im not shorting test point.
santatralalaina said:
Use it if you cannot flash with any flash tool (no root needed)
Note: Use this at your own risk! Use it as a last resort!
I'm not responsable for anything, this may not work with yours
Sorry for my poor english. I tested this method with MY bricked LG F320L, no root, no boot, no many partition pop up, partial
downloadMode (just download mode and can't see the USB logo nor S/W update) then can't flash with KDZ/TOT file,with adb mode
recovery when holding pwr and vol+ ( lucky ), with stock recovery but I have to write adb reboot recovery to get it
what you need (sorry, I'm too lazy to put a direct link, I found all of them in xda):
- Install driver for your device
- .kdz file of your model
- WindowsLGFirmwareExtract-1.2.5.0-Release
- Send_Command.exe and ports.bat (ports.bat is optional if you know the port where your device is plunged can be in LG_root.zip)
This methode needs that you can access to downloadmode or partial downloadmode like me (vol+ and plug USB cable)
1- Run WindowsLGFirmwareExtract
. browse your .kdz file with "Open" button
. click to "Extract KDZ" button and wait until finish
. browse the .dz file abd extract it with the appropriat button
. click to "Extract DZ" button and wait until finish
. select all system files and clic Merge system-bin (you will get system.img in another folder and you don't need all system****.bin)
. copy all files in same folder
2- change extension of all files .bin to .img and remove any numbers
example: aboot156.bin => aboot.img / 1-aboot.bin =>aboot.img
3- Push or copy all files to your device. You have to find also the laf.img of your device, sometime it's not in the KDZ file.
Maybe it's optional, but I'm not sure.
Remember the path, for this tuto I'm using adb and push all files to /data/local/tmp/
You can also copy all files with another method
4- Run Ports.bat
Double click ports.bat (This will give us the COM port in which our device is connected we are looking for the Diag port)
keep in mind the COM of \Device\LG*******DIAG*
5- Go to downloadMode
6- Run send_command.exe in command prompt
type: Send_Command.exe \\.\COM3 if COM3 is the port where your device is pluged
wait for #
flash all .img like this, replace NAME by the name of the file ex: aboot.img replace NAME by aboot
dd if=/data/local/tmp/{NAME}.img of=/dev/block/platform/msm_sdcc.1/by-name/{NAME}
ex: dd if=/data/local/tmp/aboot.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
Except for backupGPT.img, I don't know what is it. Maybe in this partition:
dd if=/data/local/tmp/backupGPT.img of=/dev/block/platform/msm_sdcc.1/by-name/gpt
personally , I have not flashed this one
If you have finished type: LEAVE
Flash completed
Click to expand...
Click to collapse
i have flashed wrong firmware ..now my phone have same symptoms like urs with partial download mode and no recovery....but i m unable to push files via adb bcz adb debugging is not active and i m getting error that phone not found.....now what can i dooo...plz plz plzzzz help me
I just wrote and shared my experiences. Forcing the qshusb by shorting the right pins in the motherboard is the only solution if you cannot push the img files to your phone with adb, by sdcard, by MTP or something else
santatralalaina said:
I just wrote and shared my experiences. Forcing the qshusb by shorting the right pins in the motherboard is the only solution if you cannot push the img files to your phone with adb, by sdcard, by MTP or something else
Click to expand...
Click to collapse
and how to do that?
Thank you your topic was helped me to find a solution for my phone lg g3
Hi mates, today i come with the unique guide for unbrick our Huanor GR5X phones
THIS GUIDE IS FOR FULLY BRICKED HUAWEI GR5/5X HONOR, ALL MODEL/VARIANT
ATENTION!!!
Files rawprogram0.xml and patch0.xml from my packcage its ONLY for the Huawei GR5 KII-L23 16GB VARIANT!!!
In order to continue with the tutorial, you must create your rawprogram and patch0 xml files
(mini tutorial bellow)
Ready? GO
1) Download my packcage (link MEGA)
2) Install QFIL Software. From my packcage, extract and move the folder 'Firmware' to C:\Program Files\Qualcomm\QPST\bin
3) Download and extract this .IMG files from ANY 5.1 full firmware UPDATE.APP for your model/variant
(Note: for KII-L23 is not necessary GPT.img)
GPT.img
BOOT.img
CUST.img
SYSTEM.img
TZ.img
MODEM.img
Place all img files in C:\Program Files\Qualcomm\QPST\bin\Firmware
4) Install Qualcomm drivers, Connect phone to pc, open Device Manager. If you see under com port Qualcomm USB loader or something along those lines. your good.
5) In QFIL software, if qualcomm driver are found it will say on top of QFIL software Qualcom USB loader 9008 (if say 9006,900E, you must put your phone into EDL mode with EDL Cable or EDL TEST POINT, google it)
6) Once you get the Qualcom USB loader 9008 on QFIL, you can continue
6) Select Build Type: click Flat Build
7) Select Programmer: browse to C:\Program Files\Qualcomm\QPST\bin\Firmware\prog_emmc_firehose_8939.mbn and select
8) Load XML: browse to C:\Program Files\Qualcomm\QPST\bin\Firmware and select "rawprogram0.xml" file, then select "patch0.xml" file.
9) Go to Tools and click Partition Manager
10) You will see a list with all files from partition table
11) To flash, you need select Boot.img in the list first, a mini windows will open, click on Load image and select the Boot.img placed on C:\Program Files\Qualcomm\QPST\bin\Firmware
Do the same with the rest of img files in THIS order
BOOT.img
CUST.img
SYSTEM.img
TZ.img
MODEM.img
12) Once you finish, close the partition manager. A message will appear and phone will reboot. If not, reboot manually
That's all enjoy!
FOR GR5 KII-L2X AND HONOR 5X KIW-L2X MODEL/VARIANT, FOLLOW THIS TUTORIAL
1) Download my packcage and exctract it
2) Open a cmd windows in 'Phyton + GPT Tools' folder
3) Type: GPTAnalyzer.py (drag and drop the GPT.img file previously downloaded from 5.1 firmware) and click Enter
4) Copy all results in cmd, paste on notepad and save as 'Partition0.xml' (start with <?xml version... and finish on </configuration>)
5) Type GPTParseTool.py -x (drag and drop the partition0.xml created) and click enter
6) Go to phyton folder and move all created files to C:\Program Files\Qualcomm\QPST\bin\Firmware
7) Now you can continue with the guide
Thats all my friends, hope you get a new life for your Huanor GR5X
PLEASE IF I HELP YOU, BUY ME A COFFE HERE
Reserved
GOOD guide！someone will need it！
my question：does it work on the locked phone?
wsdyleon said:
GOOD guide！someone will need it！
my question：does it work on the locked phone?
Click to expand...
Click to collapse
Thanks!
Locked and unlocked devices.
My dear friend, there is no python tools folder in your package. i can't unbrick my phone with your xml files, its a KLL-L21.
Best of regards.
faabricjs said:
Thanks!
Locked and unlocked devices.
Click to expand...
Click to collapse
I cant find python + GPT tools
faabricjs said:
Thanks!
Locked and unlocked devices.
Click to expand...
Click to collapse
my device is not showing up I have removed the battery and connected the usb but nothing happens only the device vibrates and huawei logo apears but nothing on my pc
Ibrahim Tariq said:
I cant find python + GPT tools
Click to expand...
Click to collapse
Here you will find all files needed and instructions
You have to open the phone and put it in EDL mode
Search Google for that
https://forum.hovatek.com/thread-31505.html
snazzyman89 said:
My dear friend, there is no python tools folder in your package. i can't unbrick my phone with your xml files, its a KLL-L21.
Best of regards.
Click to expand...
Click to collapse
Ibrahim Tariq said:
my device is not showing up I have removed the battery and connected the usb but nothing happens only the device vibrates and huawei logo apears but nothing on my pc
Click to expand...
Click to collapse
See my reply in previous post #8
---------- Post added at 02:15 AM ---------- Previous post was at 02:06 AM ----------
Can't we use Huiye Download Tool to flash all the images ?
what if i dont have system.img in my firmeware ? what should i do ? i have firehose from b321 can this be compatible with b330?
EDIT : i found the sys.img for b321
friends help me out i have KiW L21 superbricked unable to charge battery and he dont show up in device manager as qloader 9008
Hi,
I would like install at the Samsung SM-A515F the Lineage OS and the TWRP. I found only TWRP for the SM-A50. And the flashing dose not work for this phone.
I has try it with Heimdall and Odin.
The recovery I had downloaed from this Page:
https://www.droidthunder.com/install-twrp-recovery-on-galaxy-a51/
Need help or better information, if there exist an TWRP and lineage for this device.
Regards tiptel170
No need to flash twrp,u can flash aosp rom or even gsi with the help of odin only.Go to s10 page
sankhauaa said:
No need to flash twrp,u can flash aosp rom or even gsi with the help of odin only.Go to s10 page
Click to expand...
Click to collapse
s 10 page? which one is that? can u please provide the link?
Go here for odin flash method without twrp
sankhauaa said:
No need to flash twrp,u can flash aosp rom or even gsi with the help of odin only.Go to s10 page
Click to expand...
Click to collapse
sankhauaa said:
Go here for odin flash method without twrp
Click to expand...
Click to collapse
so does this method work for lineage os on A515F too?
After the long searching in the web, I found this:
A515F-TWRP
Link: https://firmware.gem-flash.com
After paying, you can download this TRWP. No idea, if this works. Maybe some one, will be use it.
ibtsam3301 said:
so does this method work for lineage os on A515F too?
Click to expand...
Click to collapse
I m not tried. But someone in this a51 group tried.Its working. But not so easy .
---------- Post added at 09:11 AM ---------- Previous post was at 09:09 AM ----------
tiptel170 said:
After the long searching in the web, I found this:
A515F-TWRP
Link: https://firmware.gem-flash.com
After paying, you can download this TRWP. No idea, if this works. Maybe some one, will be use it.
Click to expand...
Click to collapse
Don't pay.Its fake
tiptel170 said:
After the long searching in the web, I found this:
A515F-TWRP
Link: https://firmware.gem-flash.com
After paying, you can download this TRWP. No idea, if this works. Maybe some one, will be use it.
Click to expand...
Click to collapse
of course it would be fake
How can I open the img-files in the Linux desktop?
Found here this link, for the Magisk in the A515F:
https://forum.xda-developers.com/ga...w-to-root-samsung-a51-sm-a515f-t4032389/page2
I'll found this:
1. https://www.androlite.com/2020/01/twrp-root-samsung-galaxy-a51.html
2. https://appslova.com/install-twrp-on-samsung-galaxy-a51/
This links look likes good, because, my phone will not start or the heimdall goes into the error (likes in de page one, the screenshots ).
I found this, and I used basic from this page: https://forum.xda-developers.com/showpost.php?p=82241115&postcount=70
My first steps to install the lineage os 17 on the SM-A515F
Lineage: https://sourceforge.net/projects/andyyan-gsi/
All commands in the linux terminal, the path please use your own paths you like it!
Unpack lineage****.xz:
unxz lineage*.xz
1) Extract the AP_file.tar.md5 from your firmware.zip file using 7zip
2) Extract the super.img.lz4 file from the AP_file.tar.md5 file using 7zip
3) Put super.img.lz4 file in LZ4 folder and run in CMD the command
lz4 -d super.img.lz4 superLZ4.img
4) Put superLZ4.img file in Simg2img folder and run in CMD the command
chmod 777 ~/bin/otatools/bin/simg2img
~/bin/otatools/bin/simg2img superLZ4.img superSIMG.img
In Linux OR Bash shell:
1) Put superSIMG.img in otatools/bin folder and extract it in Linux terminal using the command
chomd 777 ~/bin/otatools/bin/lpunpack
~/bin/otatools/bin/lpunpack --slot=0 superSIMG.img ~/1
2) Put, in the folder where you extracted superSIMG.img, the GSI file you downloaded and rename it to system.img. Now you should have odm.img, system.img, vendor.img and product.img files in the same folder.
You may also need to delete/remane the original system.img file before renaming the GSI file.
3) Now you’re going to make a brand new super.img file containing all 4 files of the previous step. This is a critical and tricky step. Run Linux terminal and type:
chomd 777 ~/bin/otatools/bin/lpmake
~/bin/otatools/bin/lpmake ~/bin/otatools/bin/lpmake --metadata-size 65536 --super-name super --metadata-slots 2 --device super:4294967296 --group main:4293513600 --partition system:readonly:1959841792:main --image system=./system.img --partition vendor:readonly:680239104:main --image vendor=./vendor.img --partition odm:readonly:4349952:main --image odm=./odm.img --sparse --output ./super.img
4) Make an tar file:
tar -H ustar -c super.img > lineageos17.1_SMA515F.tar
5) Goto Windows -> Odin -> AP, put the file lineageos17.1_SMA515F.tar in to the AP-slot -> Start
This is what I has done:
But, by the compiling, I got this error:
Code:
lpmake I 07-15 20:18:20 92568 92568 builder.cpp:1012] [liblp]Partition system will resize from 0 bytes to 1959841792 bytes
lpmake I 07-15 20:18:20 92568 92568 builder.cpp:1012] [liblp]Partition vendor will resize from 0 bytes to 680239104 bytes
lpmake I 07-15 20:18:20 92568 92568 builder.cpp:1012] [liblp]Partition odm will resize from 0 bytes to 4349952 bytes
Invalid sparse file format at header magic
Invalid sparse file format at header magic
And the phone is into the boot-loop, it will not starting the system.
Any help please...
Update:
System requirements:
- Fedora 32 with current kernel
- VirtualBox 6.1 with USB support
- Windows 7
- ODIN 3.14
Enable Root:
I) On mobile phone
1. carry out firmware update
1.1 Set up device, WITHOUT Google Accounts, WITHOUT security settings, set up WLAN only
1.2 Settings -> Phone info -> Software information -> Build number (press 7x )
1.3 Settings -> developer option -> enable OEM unlocking and USB debugging
2. copy the files from the root directory to the external SD card
2.1 Install MagiskManager
2.2 Starting MagiskManager
2.3 Installing Magisk Select
II) In the Fedora area
3. unpack the boot.img from the AP***.tar, on the PC
3.1 lz4 -d boot.img.lz4 boot.img
3.2 Copy the boot.img to the SD card from the phone
4. patching the boot.img in MagikMager
4.1 Select the boot.img, wait until "Done" appears.
4.2 Then copy the magisk_patch.img to the workstation (Fedora)
5.1 Rename the original boot.img to boot_original.img
5.2 renaming magisk_patch.img to boot.img
5.3 Transfer the new boot.img to the PC for the ODIN or HEIMDALL
5.4 Convert the boot.img to boot.tar: tar -H ustar -c boot.img > boot.tar (here for ODIN)
III) Virtual environment Win7
6.1 Copy the boot.tar from the Fedora workstation to the Odin directory of Win7
6.2 Open the boot.tar in the AP slot, Auto Reboot must be off
6.3 Press Vol + & Vol - simultaneously and plug in the USB cable (On SM-A515F), then click on "Start" in the ODIN.
IV) On the Mobile Phone
7.1 If ready, restart with Vol - & Hold PWR for more than 7 sec
7.2 Putting the device into recovery mode (switch off, press vol up and pwr simultaneously, Samsunglog appears, release pwr again)
7.3 Wipe your data: Wiped data/factury reset
Note: Device makes a boot loop for the first time - is normal. The first start takes quite long, be patient!
7.4 Settings -> Phone info -> Software information -> Build number (press 7x )
7.5 Settings -> Developer option -> Enable OEM unlock, USB debugging and system auto update to OFF
7.6 Installing and starting MagiskManger
The device will restart once!
Check it: Whether root is present
Fedora workstation:
Call Terminal, enter adb shell followed by su
If everything went well, the MagiskManager should answer the phone and ask for authorization.
These steps works well with the firmware: SM-A515F R58N60BLPAZ
Where are the exactly steps for installing the TWRP?
I has installed the TWRP-10.0(A51).zip with the heimdall and the phone will not booting. And I'm not entering the TWRP. And finally I has reinstalled the revcovery.img (heimdall) from the APxxxx.zip file, and the phone starting normally.
All things with the AOSP10 etc, I has tried and the other steps for an alternative system will not work on this phone.
Thanks God, the root is now working. And I have to work with the ugly Samsung system.
tiptel170 said:
Update:
System requirements:
- Fedora 32 with current kernel
- VirtualBox 6.1 with USB support
- Windows 7
- ODIN 3.14
Enable Root:
I) On mobile phone
1. carry out firmware update
1.1 Set up device, WITHOUT Google Accounts, WITHOUT security settings, set up WLAN only
1.2 Settings -> Phone info -> Software information -> Build number (press 7x )
1.3 Settings -> developer option -> enable OEM unlocking and USB debugging
2. copy the files from the root directory to the external SD card
2.1 Install MagiskManager
2.2 Starting MagiskManager
2.3 Installing Magisk Select
II) In the Fedora area
3. unpack the boot.img from the AP***.tar, on the PC
3.1 lz4 -d boot.img.lz4 boot.img
3.2 Copy the boot.img to the SD card from the phone
4. patching the boot.img in MagikMager
4.1 Select the boot.img, wait until "Done" appears.
4.2 Then copy the magisk_patch.img to the workstation (Fedora)
5.1 Rename the original boot.img to boot_original.img
5.2 renaming magisk_patch.img to boot.img
5.3 Transfer the new boot.img to the PC for the ODIN or HEIMDALL
5.4 Convert the boot.img to boot.tar: tar -H ustar -c boot.img > boot.tar (here for ODIN)
III) Virtual environment Win7
6.1 Copy the boot.tar from the Fedora workstation to the Odin directory of Win7
6.2 Open the boot.tar in the AP slot, Auto Reboot must be off
6.3 Press Vol + & Vol - simultaneously and plug in the USB cable (On SM-A515F), then click on "Start" in the ODIN.
IV) On the Mobile Phone
7.1 If ready, restart with Vol - & Hold PWR for more than 7 sec
7.2 Putting the device into recovery mode (switch off, press vol up and pwr simultaneously, Samsunglog appears, release pwr again)
7.3 Wipe your data: Wiped data/factury reset
Note: Device makes a boot loop for the first time - is normal. The first start takes quite long, be patient!
7.4 Settings -> Phone info -> Software information -> Build number (press 7x )
7.5 Settings -> Developer option -> Enable OEM unlock, USB debugging and system auto update to OFF
7.6 Installing and starting MagiskManger
The device will restart once!
Check it: Whether root is present
Fedora workstation:
Call Terminal, enter adb shell followed by su
If everything went well, the MagiskManager should answer the phone and ask for authorization.
These steps works well with the firmware: SM-A515F R58N60BLPAZ
Where are the exactly steps for installing the TWRP?
I has installed the TWRP-10.0(A51).zip with the heimdall and the phone will not booting. And I'm not entering the TWRP. And finally I has reinstalled the revcovery.img (heimdall) from the APxxxx.zip file, and the phone starting normally.
All things with the AOSP10 etc, I has tried and the other steps for an alternative system will not work on this phone.
Thanks God, the root is now working. And I have to work with the ugly Samsung system.
Click to expand...
Click to collapse
It is work ???
GreggBorowski said:
It is work ???
Click to expand...
Click to collapse
--------------------------------------------------------------------------------------
These steps works well with the firmware: SM-A515F R58N60BLPAZ
Where are the exactly steps for installing the TWRP?
I has installed the TWRP-10.0(A51).zip with the heimdall and the phone will not booting. And I'm not entering the TWRP. And finally I has reinstalled the revcovery.img (heimdall) from the APxxxx.zip file, and the phone starting normally.
All things with the AOSP10 etc, I has tried and the other steps for an alternative system will not work on this phone.
Thanks God, the root is now working. And I have to work with the ugly Samsung system.
sankhauaa said:
I m not tried. But someone in this a51 group tried.Its working. But not so easy .
---------- Post added at 09:11 AM ---------- Previous post was at 09:09 AM ----------
Don't pay.Its fake
Click to expand...
Click to collapse
sar please send me a51 group
Mehran` said:
sar please send me a51 group
Click to expand...
Click to collapse
Go to s10 page
sankhauaa said:
Go here for odin flash method without twrp
Click to expand...
Click to collapse
Not working. I has done step by step in this guide.
ibtsam3301 said:
so does this method work for lineage os on A515F too?
Click to expand...
Click to collapse
No. Withe manipulation from the vbmeta.img, the system is unwilling to start. It gos in to the bootloader, with error-codes. Like in first thread I describe. Olny the SAMSUNG original system works with the kernel modification for the MagiskManager.
I saw black for the future, there will be exist an custom rom for this device.
I have no idea, what can I do for this device. But I use and spend a lot of time for modification, without an good result. Has anyone an idea what can I do? But it look likes, it has an great secure system intern for not using an customer rom. This is my intention.