Related
Your warranty is void. I'm not responsible if your device is hard bricked by using the procedure below. The method described below has been tested on 6039Y, 6039S, 6039H (with the archives for 6039Y) and 6039K (with the 6039S archive) and is confirmed that it works.
What to expect on successful completion:
- you will have access to the fastboot commands (removed by the latest upgrade).
- you should be able to check for OTA updates and to download them, but you will not be able to install them.
What's needed:
-------------------
1. I hate when I must say this ... but ... a Windows PC.
2. QPST version 2.7.422 (you can find it on the net as 2.7 build 422). This is a link to one such version (found through Google). If there are problems with this link please let me know. I will try to find another one (you can do it yourself too).
3. Drivers in order the device to be recognized when is in Download mode. Install Mobile Upgrade Q 4.8.7 the necessary drivers are installed with it. It can be downloaded from here.
4. The files from the archives below. Please use the archive which is especially for your device ... in theory if you use the archive for different device (e.g. the archive for 6039S on 6039Y (with the standard partitions)) you should have a repartitioned device at the end, and only the resize2fs command should be enough to start to utilize the whole memory chip ... but you will loose the possibility to sweat a little bit when do the repartitioning by following the guide for it .
- 6039Y (8GB stock partition sizes) (md5sum: 860789bedb63da5c5976c24825c29d47)
- 6039Y (repartitioned by following the repartitioning guide) (md5sum: c2f8ff3cfc683e46fbf5d797103de71b)
- 6039S (md5sum: dfd04067230b5709729c70cac61ffd52)
How to proceed:
--------------------
1. Install all the necessary software.
2. Unpack the downloaded archive for your device.
3. Power off the device. Connect it with the USB cable to the PC. Wait the battery symbol to disappear and hold both volume keys and the power button. You should see a red screen with a warning sign and a scheme. Then hold the volume up button. The display will stay lit but nothing will be shown on it from now on until the end of the procedure.
4. When the device is in Download mode under the windows device manager -> Ports (COM & LPT) you should see Android HS-USB QDLoader 9008 (COMXX)
5. Open the windows explorer and find the installation folder of QPST (mine is under Program Files (x86)\Qualcomm\QPST). From the bin sub-directory start QFIL as administrator.
6. In QFIL the COM port number as seen under the windows device manager should be selected automatically.
7. The rest must be done from QFIL:
- Programmer path: _____ - Click on the Browse button against it and from the extracted archive select prog_emmc_firehose_8916.mbn
- Search Path: _____ - if the path is not selected automatically after the programmer selection click on the Browse button against it and select the folder where the archive has been extracted.
- Load XML - click on it and first select rawprogram0.xml from the archive, then the patch0.xml file.
- Click on the Download button. The process should finish quickly (few seconds ... up to a minute). If everything is OK the phone will be restarted automatically and the fastboot commands will be available again.
(If you feel unsure to proceed or not but your device is already in download mode ... disconnect the USB cable and hold both volume keys and the power button to restart it).
Screenshots from QFIL is possible to be provided later ...
Reserved....
Alright I guess I'll be the guinea pig here.... Few questions beforehand:
I currently have the 6039Y version without having repartitioned... Using the repartitionned one would directly give me a repartitionned memory? Did I understand that correctly?
Did I dream about you saying that you might have a way to fix hard bricks? Because I might very well brick mine with my usual luck
About the updates... If there were any later OTA updates (I know it's unlikely) would there be a way to apply them still?
Rorshan said:
Alright I guess I'll be the guinea pig here.... Few questions beforehand:
I currently have the 6039Y version without having repartitioned... Using the repartitionned one would directly give me a repartitionned memory? Did I understand that correctly?
Did I dream about you saying that you might have a way to fix hard bricks? Because I might very well brick mine with my usual luck
Click to expand...
Click to collapse
In theory yes, but is untested. Yes, hard bricks should be fixable with these tools and with slightly different files. But as this requires a full copy of the memory chip and for the moment I have such copy only from my device, I can recover only my device (or others which will become the same as mine ... this means radio, languages, apps etc. ).
About the updates... If there were any later OTA updates (I know it's unlikely) would there be a way to apply them still?
Click to expand...
Click to collapse
Yes, but modified
Edit: What do I do here? I guess a missing font file shouldn't bother me, but still I'd like some advice here
Click to expand...
Click to collapse
No idea ... try with ignore. I didn't have have any problems with mobile upgrade q.
petrov.0 said:
In theory yes, but is untested. Yes, hard bricks should be fixable with these tools and with slightly different files. But as this requires a full copy of the memory chip and for the moment I have such copy only from my device, I can recover only my device (or others which will become the same as mine ... this means radio, languages, apps etc. ).
Yes, but modified
No idea ... try with ignore. I didn't have have any problems with mobile upgrade q.
Click to expand...
Click to collapse
Untested doesn't sound nice... I guess I'll go with the normal way and worry about the repartition afterwards.
I cancelled the install and reinstalled with no issue
I guess this is it. Either way I'll come here to cry, be it from joy or sadness/anger
---------- Post added at 07:46 PM ---------- Previous post was at 07:26 PM ----------
Well I'm done and my phone resetted just fine... I freaked for a minute when it took a bit longer than usual for my phone to pick up signal.
And......
fastboot -i 0x1bbb devices
48fee072 fastboot
Click to expand...
Click to collapse
I haven't tried TWRP yet since I don't really know what version I should be using... Any idea @petrov.0 ?
Rorshan said:
Untested doesn't sound nice... I guess I'll go with the normal way and worry about the repartition afterwards.
I cancelled the install and reinstalled with no issue
I guess this is it. Either way I'll come here to cry, be it from joy or sadness/anger
---------- Post added at 07:46 PM ---------- Previous post was at 07:26 PM ----------
Well I'm done and my phone resetted just fine... I freaked for a minute when it took a bit longer than usual for my phone to pick up signal.
And......
I haven't tried TWRP yet since I don't really know what version I should be using... Any idea @petrov.0 ?
Click to expand...
Click to collapse
For normal use (flashing) the latest from 12.09.2015. For the repartitioning boot with the one from the repartitioning thread.
Thanks! I will try it now!
EDIT:
It all works
petrov.0 said:
For normal use (flashing) the latest from 12.09.2015. For the repartitioning boot with the one from the repartitioning thread.
Click to expand...
Click to collapse
Alright TWRP seems to work fine, I'm doing backups at the moment. Thank you so much! You're such a lifesaver. Quick last question... I think I'm going to root and repartition. Does it matter at all which I do first?
Rorshan said:
Alright TWRP seems to work fine, I'm doing backups at the moment. Thank you so much! You're such a lifesaver. Quick last question... I think I'm going to root and repartition. Does it matter at all which I do first?
Click to expand...
Click to collapse
This question is for the other thread ... but no, it doesn't matter.
Do you feel its safe to test this on 6039s?
xStealth said:
Do you feel its safe to test this on 6039s?
Click to expand...
Click to collapse
Well good question. The files for the S have been generated only on the base of the partition numbers (not their names) and their sizes ... they look the same as those on the Y but ... I think it's safe.
xStealth said:
Do you feel its safe to test this on 6039s?
Click to expand...
Click to collapse
Can further confirm that this worked on my 6039S. No bricking, and fastboot works as promised!
A BIG thanks petrov.0!
Bradlee22 said:
Can further confirm that this worked on my 6039S. No bricking, and fastboot works as promised!
A BIG thanks petrov.0!
Click to expand...
Click to collapse
He already did this. Read the first line from the first post.
petrov.0 said:
He already did this. Read the first line from the first post.
Click to expand...
Click to collapse
Oh, right on. I wasn't sure who had confirmed it at that point. Thanks again for all your work on this!
Update
The link and the md5sum in the first post for the repartitioned 6039Y have been updated as one of the files was missing from the archive. Thanks @kkkk2222 for finding the error.
Worked a treat, fantastic work folks.
http://www.modaco.com/news/android/you-can-turn-your-8gb-idol-3-47-into-a-16gb-really-r1521/
Used Parallels on a Mac, no problem!
P
@petrov.0
For those who end up stuck in bootloops(on both 6039's and 6045's) with factory recovery is there a way this method could be used to either 1) flash twrp to the device or 2) force the device into bootloader?
If a user can get to bootloader (and has fastboot) then they could attempt to fix their own issue.
famewolf said:
@petrov.0
For those who end up stuck in bootloops(on both 6039's and 6045's) with factory recovery is there a way this method could be used to either 1) flash twrp to the device or 2) force the device into bootloader?
If a user can get to bootloader (and has fastboot) then they could attempt to fix their own issue.
Click to expand...
Click to collapse
1. Yes, it should be possible by using the same tools with different files. But if they flash their system image backup this will lead to a big mess ... they will have a partially upgraded device. Probably if they use the fix permissions option or force the reinstall of SuperSU from the recovery this will be the end of the bootloops (these are unconfirmed speculations though). I need the gpt table from the device (6045) to generate the necessary files.
Code:
dd if=/dev/mmcblk0 of=<path to the sd_card>/gpt.bin bs=512 count=34
2. No.
petrov.0, first of all - thx for your great work. I have a theoretical question about QFIL and partition flashing. Is it necessary to flash all of this partitions in rawprogram0.xml:
sbl1.mbn
rpm.mbn
tz.mbn
hyp.mbn
aboot.mbn
gpt_main0.bin
gpt_backup0.bin
For working fastboot we need only aboot (emmc_appsboot) from previous firmware version (or i'm wrong?), if we short rawprogram0.xml only for aboot and gpt, like this:
Code:
<?xml version="1.0" ?>
<data>
<!--NOTE: This is an ** Autogenerated file **-->
<!--NOTE: Sector size is 512bytes-->
<program SECTOR_SIZE_IN_BYTES="512" file_sector_offset="0" filename="aboot.mbn" label="aboot" num_partition_sectors="2048" physical_partition_number="0" size_in_KB="1024.0" sparse="false" start_byte_hex="0xc18c000" start_sector="396384"/>
<program SECTOR_SIZE_IN_BYTES="512" file_sector_offset="0" filename="aboot.mbn" label="abootbak" num_partition_sectors="2048" physical_partition_number="0" size_in_KB="1024.0" sparse="false" start_byte_hex="0xc28c000" start_sector="398432"/>
<program SECTOR_SIZE_IN_BYTES="512" file_sector_offset="0" filename="gpt_main0.bin" label="PrimaryGPT" num_partition_sectors="34" physical_partition_number="0" size_in_KB="17.0" sparse="false" start_byte_hex="0x0" start_sector="0"/>
<program SECTOR_SIZE_IN_BYTES="512" file_sector_offset="0" filename="gpt_backup0.bin" label="BackupGPT" num_partition_sectors="33" physical_partition_number="0" size_in_KB="16.5" sparse="false" start_byte_hex="(512*NUM_DISK_SECTORS)-16896." start_sector="NUM_DISK_SECTORS-33."/>
</data>
Phone doesn't brick after flashing?
p.s. And another one question. Do you know where the testpoint on 6039Y located? After several my experiments (not with your files, i was bricked it by myself i have bricked phone. There is no download mode (9008 com port not appears in my case), only turned on LED on front panel. Any actions with holding both volume buttons and power button doesn't get success, i think in this case testpoint will help. But i don't know where is it. If somebody need - i can attach photo of PCB.
petrov.0 said:
1. Yes, it should be possible by using the same tools with different files. But if they flash their system image backup this will lead to a big mess ... they will have a partially upgraded device. Probably if they use the fix permissions option or force the reinstall of SuperSU from the recovery this will be the end of the bootloops (these are unconfirmed speculations though). I need the gpt table from the device (6045) to generate the necessary files.
Code:
dd if=/dev/mmcblk0 of=<path to the sd_card>/gpt.bin bs=512 count=34
2. No.
Click to expand...
Click to collapse
Code:
/mmcblk0 of=/storage/sdcard1/gpt.bin bs=512 count=34 <
dd: /dev/mmcblk0: No such file or directory
Now a cat of /proc/partitions shows 179 0 15267840 mmcblk0 so I have no idea why it says it's not found. [I can confirm none of the mmc* are under /dev. I have a find running to see where it says it is.....ok..for us it's in /dev/block/mmcblk0 ]
Just drop .zip off the end of the name..it's not actually zipped but couldn't upload a .bin.
If you try this method, I nor anybody else is responsible for any further damage done to your phone.
Models Confirmed : V300L
We currently have firehose for V30.
Therefore, we can program UFS flash memory in 9008 mode.
It requires rawprogram?.xml(s) and patch?.xml(s) to program it.
It's easy to generate rawprogram?.xml(s) from kdz file, but generate patch?.xml(s) is not easy. (Unfortunately, I couldn't have time to generate patch?.xml(s)).
I have edited kdztools to generate rawprogram?.xml(s) easily (You can generate it by using "-r" argument. Currently, generate patch?.xml(s) is not supported. I'll add it soon).
I used patch?.xml(s) in post. it works well, but boot loop in the LG Logo.
However, it was possible to enter download mode.
------------------- GUIDE -------------------1. Download rawprogram?.xml patch?.xml with images from link. (It uses V300L30h000906.kdz)
2. Download firehose (prog_ufs_firehose_8998_lgev30.elf) from link.
<< Linux >>
3. Build qdl or download pre-built binary
4. Extract zip or tar.gz files 1, 2, 3 in any folder.
5. Run
Code:
$ ./qdl --storage ufs prog_ufs_firehose_8998_lgev30.elf rawprogram0.xml patch0.xml rawprogram1.xml patch1.xml rawprogram2.xml patch2.xml rawprogram3.xml patch3.xml rawprogram4.xml patch4.xml rawprogram5.xml patch5.xml rawprogram6.xml patch6.xml
in the terminal.
6. If LG logo shows, enter to the download mode.
<< Windows >>
3-6. You can program by QFIL similar as qdl.
7. Connect to any Windows PC with LGUP (must support Android Pie).
8. Flash kdz with ChipErase. (IMPORTANT)
9. If it boots successfully, your device has unbricked.
you can create rawprogramer and patch.xml with this program
I have already tried it on lg v10 kdz with successful.
after extract kdz :
1-open qualcomtool 2.4 and go to EMMC tabe.
2-clic browse and select primarygpt_0.bin
3- select all partitions and click exract partition
4- click extract firmware
you will find every things you need in extracted folder.
you can edid rowprogramer.xml with notepad ++ .
edit : tryed with lg v30 kdz not work
(gpt not present when select file)
Thank you for your work
download problem
quickwshell said:
If you try this method, I nor anybody else is responsible for any further damage done to your phone.
Models Confirmed : V300L
We currently have firehose for V30.
Therefore, we can program UFS flash memory in 9008 mode.
It requires rawprogram?.xml(s) and patch?.xml(s) to program it.
It's easy to generate rawprogram?.xml(s) from kdz file, but generate patch?.xml(s) is not easy. (Unfortunately, I couldn't have time to generate patch?.xml(s)).
I have edited kdztools to generate rawprogram?.xml(s) easily (You can generate it by using "-r" argument. Currently, generate patch?.xml(s) is not supported. I'll add it soon).
I used patch?.xml(s) in post. it works well, but boot loop in the LG Logo.
However, it was possible to enter download mode.
------------------- GUIDE -------------------1. Download rawprogram?.xml patch?.xml with images from link. (It uses V300L30h000906.kdz)
2. Download firehose (prog_ufs_firehose_8998_lgev30.elf) from link.
<< Linux >>
3. Build qdl or download pre-built binary
4. Extract zip or tar.gz files 1, 2, 3 in any folder.
5. Run
Code:
$ ./qdl --storage ufs prog_ufs_firehose_8998_lgev30.elf rawprogram0.xml patch0.xml rawprogram1.xml patch1.xml rawprogram2.xml patch2.xml rawprogram3.xml patch3.xml rawprogram4.xml patch4.xml rawprogram5.xml patch5.xml rawprogram6.xml patch6.xml
in the terminal.
6. If LG logo shows, enter to the download mode.
<< Windows >>
3-6. You can program by QFIL similar as qdl.
7. Connect to any Windows PC with LGUP (must support Android Pie).
8. Flash kdz with ChipErase. (IMPORTANT)
9. If it boots successfully, your device has unbricked.
Click to expand...
Click to collapse
thank you so much,but can't download zip from this website,if you can offer other download way,such as google,mega,onedrive,i will apreciate it so much,thanks for your work
Johoneycn said:
thank you so much,but can't download zip from this website,if you can offer other download way,such as google,mega,onedrive,i will apreciate it so much,thanks for your work
Click to expand...
Click to collapse
Sorry for the late reply
mega. nz/#!zCZBkC4D!Vxo9wrd1c9vsZgCfQIrLelcp3unTY7sJAqMXjANvzjQ is V30_UNBRICK.zip
and mega. nz/#!PLIBzQ6L!JKtfq_RH2iFgcQckkRi_LtZGt9u2zaO2YF6x8dtHL6A is a firehose.
It is a shame we resort to such lengths for this. Shame on vendors. It is like pure gold or diamonds when we come across a programmer...
Hi, @quickwshell, could you see this: Help! bootloop per 5 sec, cannot enter rec, download or fastboot. Does the problem I'm facing now is what your method targeting to?
@quickwshell
Thank you so much for sharing firehorse for v30 and this solution. I have LS998 bricked bootloop after interrupting upgrade as @zacox123. I tried your files posted but still phone cant get download mode. Now Im trying to create rawprogram.xml and patch.xml from specific firmware model ls998 but I want to know what partitions are necesary just for getting download mode and then try to upgrade for usb mode.
Could you please help me?
thanks in advance
Pulian said:
@quickwshell
Thank you so much for sharing firehorse for v30 and this solution. I have LS998 bricked bootloop after interrupting upgrade as @zacox123. I tried your files posted but still phone cant get download mode. Now Im trying to create rawprogram.xml and patch.xml from specific firmware model ls998 but I want to know what partitions are necesary just for getting download mode and then try to upgrade for usb mode.
Could you please help me?
thanks in advance
Click to expand...
Click to collapse
How did you do with your phone? Have you made your phone into 9008 mode? Did you use the correct tool?
I have not processed my problem yet. But I read some other posts introducing that, use qpst or miracle box or any similar tools with the edl file provided by @quickwshell to flash in twrp directly, instead of getting download mode back. Maybe you can have a trial.
I was converting my lg [email protected] for unlocking. I have tools for flashing and I did it before with others phones. Accidently flashing process was interrupted and phone got that condition, no download mode. Now I'm using testpoint connection and UMT (tool for repair Qualcomm Phones) for trying to recover download mode. I suppose you can use QFIL for programming after we have correct rawprogramer.xml and patch.xml. Let me finish my test and I'll post results.
Pd: bootloader is not unlocked and I don't know if I can write twrp and it'll work.
Could you share links referring this topic and phone? Thanks.
Well, it definitely worked :good:.
Partitions extracted from us998 firmware
. Now I'm flashing again.
Pd: sorry for inverted picture. I make it from cellphone without edition
Do we need any special process before the computer work, @quickwshell and @Pulian? Is any special cable or teardown work needed? I have never used 9008 before but see other brands like xiaomi cannot simply enter 9008 mode directly.
---------- Post added at 04:27 PM ---------- Previous post was at 04:08 PM ----------
Pulian said:
Well, it definitely worked :good:.
Partitions extracted from us998 firmware
. Now I'm flashing again.
Pd: sorry for inverted picture. I make it from cellphone without edition
Click to expand...
Click to collapse
I see octoplus in your pic. Could you please share your tools and detailed steps? I have never tried 9008, so I hope some extra hand-by-hand instructions. Thanks.
The post I read is from an Android community app, and I'm afraid I cannot provide a link to it. And the author of that post said he had not tested yet, just some common sense and rough idea. I'd hear more from you, afterwards you have succeeded.
Thanks again @quickwshell. Firehorse file is the most important think for starting.
1. I extracted files partitions from firmware KDZ using this software https://forum.xda-developers.com/showthread.php?t=2600575
2.. I used testpoint for getting EDL (QUALCOM 9008) connection. https://forum.xda-developers.com/showpost.php?p=78573920&postcount=2
3. I tried firmware posted here without success (Maybe it works on others). So I wrote critical partitions extracted from my specific firmware (US998) using UMT box and I didnt need to create .xml files because this tool can read and detect internal partitions.
4. I got download mode and just write firmware by USB using octoplusbox. Phone Alive!!
I think every step here can be replaced using diferent software. good luck!
nate0 said:
It is a shame we resort to such lengths for this. Shame on vendors. It is like pure gold or diamonds when we come across a programmer...
Click to expand...
Click to collapse
yes,i think so too, lg is too bad on the software
Pulian said:
Thanks again @quickwshell. Firehorse file is the most important think for starting.
1. I extracted files partitions from firmware KDZ using this software https://forum.xda-developers.com/showthread.php?t=2600575
2.. I used testpoint for getting EDL (QUALCOM 9008) connection. https://forum.xda-developers.com/showpost.php?p=78573920&postcount=2
3. I tried firmware posted here without success (Maybe it works on others). So I wrote critical partitions extracted from my specific firmware (US998) using UMT box and I didnt need to create .xml files because this tool can read and detect internal partitions.
4. I got download mode and just write firmware by USB using octoplusbox. Phone Alive!!
I think every step here can be replaced using diferent software. good luck!
Click to expand...
Click to collapse
After getting download mode back, do we need chiperase like @quickwshell mentioned? I don't know if octoplusbox did it before writing firmware and I suppose most people would still use LGUP for firmware writing. Did you lose s/n, imei, etc. after phone booting? If not, I guess partition dl should be OK.
I didnt touch imei and security partitions. My phone worked after flashing without problems.
Pulian said:
Thanks again @quickwshell. Firehorse file is the most important think for starting.
1. I extracted files partitions from firmware KDZ using this software https://forum.xda-developers.com/showthread.php?t=2600575
2.. I used testpoint for getting EDL (QUALCOM 9008) connection. https://forum.xda-developers.com/showpost.php?p=78573920&postcount=2
3. I tried firmware posted here without success (Maybe it works on others). So I wrote critical partitions extracted from my specific firmware (US998) using UMT box and I didnt need to create .xml files because this tool can read and detect internal partitions.
4. I got download mode and just write firmware by USB using octoplusbox. Phone Alive!!
I think every step here can be replaced using diferent software. good luck!
Click to expand...
Click to collapse
I searched a lot for UMT Box and it seems like one has to collect it with the dongle or else it's not gonna work. Getting frustrated here Are there any way other than umt? Can you or anyone suggest?
moyedchowdhury said:
I searched a lot for UMT Box and it seems like one has to collect it with the dongle or else it's not gonna work. Getting frustrated here Are there any way other than umt? Can you or anyone suggest?
Click to expand...
Click to collapse
use cracked miracle box
seloka180 said:
use cracked miracle box
Click to expand...
Click to collapse
THANKS FOR COMING BACK. Mine is a LS998 converted into US998.
I'm So disappointed right now. Past few days have been unbearable. Even my Blood pressure is getting high
I'll describe what happened so that the situation is understood and you could suggest accordingly.
*I unlocked bootloader by wtf method.
*Tried several roms.
*Decided to stay on LOS 17.1 Q [Nearly got f*****g everything]
*Flushed a module via magisk which offered pixel boot animation(actually was searching for smartpixel to turn off 50% pixels)
*Rebooted and the device stuck into bootloop
*Rebooted into fastboot mode and reinstalled twrp and reboot- No luck
*Used a guide to wipe different partitions via fastboot and then reinstall twrp. Success but still boot stuck.
*Tried to go into download mode by pressing volume up while connecting USB, went into the mode but "waiting for any connection..." showed and was not detected by device mgr.
*Thought relocking the bootloader might get me into download mode.(That's when I burnt my luck I guess...)
*Did lock the bootloader.
*Aaaand still not detected in device manager.
*Moreover, now showing that Your device has failed a routine security check and will not boot!
{
"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"
}
*Opened the back and test pointed motherboard, detected in 9008 mode
*Tried QFIL with V30_Unbrick.zip, sahara error.
*Tried a bunch of other tools most of them were so old that they didn't even have the firehose for this model.
Please someone help.
seloka180 said:
use cracked miracle box
Click to expand...
Click to collapse
Can't thank you enough mate! Used it and miracle did happen. I even tried to use it before but after you said it, I tried hard this time. Searched here and there, then took some risk and started to do things like this way -
I had V30_UNBRICK.zip unzipped in a folder with firehose and xml files.
*Disable defender or any other antivirus. (Normally not recommended, but it's the first thing I do when doing these things, also I have an extra laptop where I do all these which doesn't have any private or necessary files, never had any problem though).
*Also, disable driver signature enforcement on Windows(https://windowsreport.com/driver-signature-enforcement-windows-10/)
1. I searched and found Miracle box Thunder v2.93 with loader (No box needed)
2. Select Qualcomm, then flashing and Write Flash.
3. Untick the auto button beside firehose.
4. Under "write flash"
see this image
i. Select firehose, this doesn't recognize the .elf file so renamed it to .mbn (finger was crossed) and it worked!
ii. There are six rawprogram?.xml and patch?.xml (Here, ? = 1, 2, 3....6), I only used rawprogram0.xml and
iii. patch0.xml
5. Got everything ready and then detached the phone from cable.
6. Pressed the start button right after entering into Testpoint EDL Mode. The process starts and failed after a while due to missing files. Then I matched which files were present corresponding to the lines in the xml file, after that deleted all the extra lines(i. e. file was not present in the V30_UNBRICK.zip) from rawprogram0.xml and saved the file (patch0.xml was untouched). I used Notepad++ for editing.
7. Again detached the phone, detached battery, reattached battery, pressed the start button right after I shorted the edl test points, even before the device was detected in the device manager, no delay.
8. The process was completed, files flashed. These files were flashed so that we can now flash proper kdz with download mode. Do not turn on the phone. Or else you'll get into bootloop.
9. Detached the battery, shorted power button for a while(skip if you don't understand), reattached the battery.
10. Pressed volume up and inserted USB cable. Not detected first time. Detached and reattached with pressing volume up button hard this time.
11. witnessed one of the happiest moment seeing it was detected as an LG device in device manager. Wasn't 100% sure yet.
12. Flashed chiperase(important) with patched LGUP in dev mode. And it was done.
13. I will upload the XML file, you can use it with the existing files inside V30_UNBRICK.zip.
the xml file here
Before doing all that I spent five horrific days searching for a solution and almost ordered a motherboard from Aliexpress with a price tag of $100. I tried to be as elaborative as possible so that whoever next encounter the issue don't have to go through what I experienced past few days. If you're reading this and having a problem understanding anything, read again, repeat 10 times, then repeat more 10 times(worked for me), still no solution? knock me here (also: [email protected]). I could help you(with v 30, g6) remotely if I have time, no charges, donate if you will and if you don't I'll still be happy to help. Keep flashing, peace.
---------- Post added at 05:36 AM ---------- Previous post was at 04:57 AM ----------
quickwshell said:
If you try this method, I nor anybody else is responsible for any further damage done to your phone.
Models Confirmed : V300L
We currently have firehose for V30.
Therefore, we can program UFS flash memory in 9008 mode.
It requires rawprogram?.xml(s) and patch?.xml(s) to program it.
It's easy to generate rawprogram?.xml(s) from kdz file, but generate patch?.xml(s) is not easy. (Unfortunately, I couldn't have time to generate patch?.xml(s)).
I have edited kdztools to generate rawprogram?.xml(s) easily (You can generate it by using "-r" argument. Currently, generate patch?.xml(s) is not supported. I'll add it soon).
I used patch?.xml(s) in post. it works well, but boot loop in the LG Logo.
However, it was possible to enter download mode.
------------------- GUIDE -------------------1. Download rawprogram?.xml patch?.xml with images from link. (It uses V300L30h000906.kdz)
2. Download firehose (prog_ufs_firehose_8998_lgev30.elf) from link.
<< Linux >>
3. Build qdl or download pre-built binary
4. Extract zip or tar.gz files 1, 2, 3 in any folder.
5. Run
Code:
$ ./qdl --storage ufs prog_ufs_firehose_8998_lgev30.elf rawprogram0.xml patch0.xml rawprogram1.xml patch1.xml rawprogram2.xml patch2.xml rawprogram3.xml patch3.xml rawprogram4.xml patch4.xml rawprogram5.xml patch5.xml rawprogram6.xml patch6.xml
in the terminal.
6. If LG logo shows, enter to the download mode.
<< Windows >>
3-6. You can program by QFIL similar as qdl.
7. Connect to any Windows PC with LGUP (must support Android Pie).
8. Flash kdz with ChipErase. (IMPORTANT)
9. If it boots successfully, your device has unbricked.
Click to expand...
Click to collapse
Thank you, Your post helped me to understand a lot of things. Without whome I'd be having an expensive brick which can't even be used to build anything.
This is the way I recovered. So posting it here for people might get help.
seloka180 said:
use cracked miracle box
Click to expand...
Click to collapse
Can't thank you enough mate! Used it and miracle did happen. I even tried to use it before but after you said it, I tried hard this time. Searched here and there, then took some risk and started to do things like this way -
I had V30_UNBRICK.zip unzipped in a folder with firehose and xml files.
*Disable defender or any other antivirus. (Normally not recommended, but it's the first thing I do when doing these things, also I have an extra laptop where I do all these which doesn't have any private or necessary files, but never had any problems).
*Also, disable driver signature enforcement on Windows(https://windowsreport.com/driver-sig...nt-windows-10/)
1. I searched and found Miracle box Thunder v2.93 with loader (No box needed)
2. Select Qualcomm, then flashing and Write Flash.
3. Untick the auto button beside firehose.
4. Under "write flash"
see this image
i. Select firehose, this doesn't recognize the .elf file so renamed it to .mbn (finger was crossed) and it worked!
ii. There are six rawprogram?.xml and patch?.xml (Here, ? = 1, 2, 3....6), I only used rawprogram0.xml and
iii. patch0.xml
5. Got everything ready and then detached the phone from cable.
6. Pressed the start button right after entering into Testpoint EDL Mode. The process starts and failed after a while due to missing files. Then I matched which files were present corresponding to the lines in the xml file, after that deleted all the extra lines(i. e. file was not present in the V30_UNBRICK.zip) from rawprogram0.xml and saved the file (patch0.xml was untouched). I used Notepad++ for editing.
7. Again detached the phone, detached battery, reattached battery, pressed the start button right after I shorted the edl test points, even before the device was detected in the device manager, no delay.
8. The process was completed, files flashed. These files were flashed so that we can now flash proper kdz with download mode.
9. Detached the battery, shorted power button for a while(skip if you don't understand), reattached the battery.
10. Pressed volume up and inserted USB cable. Not detected first time. Detached and reattached with pressing volume button hard this time.
11. witnessed one of the happiest moment seeing it was detected as an LG device in device manager. Wasn't 100% sure yet.
12. Flashed chiperase(important) with patched LGUP in dev mode. And it was done.
13. I will upload the XML file, you can use it with the existing files inside V30_UNBRICK.zip.
the xml file here
Before doing all that I spent five horrific days searching for a solution and almost ordered a motherboard from Aliexpress with a price tag of $100. I tried to be as elaborative as possible so that whoever next encounter the issue don't have to go through what I experienced past few days. If you're reading this and having a problem understanding anything, read again, repeat 10 times, then repeat more 10 times(worked for me). Keep flashing, peace.
Pixel 6 Pro runs on a Google Tensor CPU which is in fact an Exynos CPU
This means that there is Exynos boot recovery in the CPU
You can repair the bootloader using the Samsung Exynos Tool
Nothing could be flashed from the mode, however it loads into the RAM the fastboot mode, from here reflash the bootloader image using fastboot
Unpack BL1, BL2 AP boot, ELR_EL3, BL etc from stock image (use your device and version)
[guide] repair hard bricked devices with deleted bootloader (sboot)
I'm writing this in android development section because this is only section for both models, i hope this is not a problem. Also i want to say thanks to sataccount from gsmhosting, he found working map at the end. This guide is for hard bricked...
forum.xda-developers.com
Set this up using windows 7 32 bit
use this config not the one he has included, but use his tutorial
DNW_STORE exynos down 200 20 bl1.bin
DNW_STORE exynos down 2000 20 bl2.bin
DNW_STORE exynos down 200 20 elr_el3.bin
DNW_STORE exynos down 200 20 lastly.bin
DNW_WAIT
;PIXEL ROM RECOVERY
DNW_STORE exynos down 20000 20 bl.bin
NOTE: this is EDL mode!!
If not working or you need help let me know
@pierre383
Have you recovered any Pixel 6/6 Pro unit in real life yet using this procedure? If so, then kindly post a more elaborate guide so that we can cover it for the portal.
===
AFAIK, a hard-bricked Google Silicon device (e.g. the Pixel 6/6 Pro) by default exposes a serial interface with vendor ID 18D1 (aka Google) and device ID 4F00.
SkandaH said:
@pierre383
Have you recovered any Pixel 6/6 Pro unit in real life yet using this procedure? If so, then kindly post a more elaborate guide so that we can cover it for the portal.
===
AFAIK, a hard-bricked Google Silicon device (e.g. the Pixel 6/6 Pro) by default exposes a serial interface with vendor ID 18D1 (aka Google) and device ID 4F00.
Click to expand...
Click to collapse
Hi sorry am making this fast, when you have it as a unverified device in device managment, install Exynos mode USB driver (USE 32BIT operationing system for the one in the post I linked), prepare the boot + cfg (just take mine), hold the power button and select in the software it should begin, if you have problems uncomment the DNW_WAIT or try another USB cable, the motherboard in your computer is the difference
if your computer say the driver is not compatible on 32bit computer, pick install anyway, install manually a driver for the selected device from a list of installed drivers on the computer (in device manager)
if you need more help or can help me make it better pls let me know
Linux will work also with different tool, but the DNW_WAIT can't be replicated :? so got stuck on pixel rom recovery line, fastboot did not load on the phone
after dnw_wait if phone is not recognized hold power button while DNW_WAIT sequence maybe
Unpack BL1, BL2 AP boot, ELR_EL3, BL etc from stock image (use your device and version)
Click to expand...
Click to collapse
it's amazing ! but how to unpack these bin files? stock image only has a bootloader.img
or could i use dd to copy it that from my phone filesystem in terminal ?
split bootloader as explained, it is inside bootloader.img if you need more guidence let me know and yes dd can copy bootloader.img however this assume that you phone can't turn on so you can't copy it from dd terminal in the phone because how can you do that in brick state... don't try and prepare for brick, rollback protection will assure that you can't boot a old bootloader from long time ago you prepared incase of brick you need new BL
iCassius said:
it's amazing ! but how to unpack these bin files? stock image only has a bootloader.img
or could i use dd to copy it that from my phone filesystem in terminal ?
Click to expand...
Click to collapse
oh I see it ! it means I need split bootloader.img to 4 bin files .
so it we can get 64bit drivers , it means newly computer and windows is useable?
iCassius said:
oh I see it ! it means I need split bootloader.img to 4 bin files .
so it we can get 64bit drivers , it means newly computer and windows is useable?
Click to expand...
Click to collapse
I recommend using a virtual machine with 32bit Windows 7 or XP or Vista, working with making the Linux work, Install Windows 32 bit on your laptop (you can use a 2nd partition maybe)
It is about fixing the phone that cost 600€, working 1 hour to make Windows 32bit work in 1 or another way is not a big deal
However there are 64 bit drivers around but they are not on XDA, so yes, theoretically it can work with modern 64bit windows
Could you please explain how to split the bootloader image or attach the files?
pierre383 said:
Linux will work also with different tool, but the DNW_WAIT can't be replicated :? so got stuck on pixel rom recovery line, fastboot did not load on the phone
Click to expand...
Click to collapse
Hi @pierre383 thanks for your guide. I have a bricked Pixel 6. But it only stays visible in Pixel ROM Recovery Mode for about 10s.
What linux tool is available? and where?
Thanks
speedpat said:
Hi @pierre383 thanks for your guide. I have a bricked Pixel 6. But it only stays visible in Pixel ROM Recovery Mode for about 10s.
What linux tool is available? and where?
Thanks
Click to expand...
Click to collapse
GitHub - frederic/exynos-usbdl: Unsigned code loader for Exynos BootROM
Unsigned code loader for Exynos BootROM. Contribute to frederic/exynos-usbdl development by creating an account on GitHub.
github.com
Look into building this, or dm me for discord or telegram and I can gladly guide you through building and using it
z3r0skull said:
Could you please explain how to split the bootloader image or attach the files?
Click to expand...
Click to collapse
I could post in the weekend
Hi @pierre383. You might want to change this thread type from "Question" to "How to guide". Just either edit the first post and you can then change the thread type there, or click the 3-dot menu in the upper right corner above the first post and choose "Edit thread" and you can change it there instead - either way.
pierre383 said:
I could post in the weekend
Click to expand...
Click to collapse
Thanks that would be nice.
Also my pixel is not recognized by the "multidownloader" tool mentioned in the other guide. Did you install any specific driver for it to work?
Thank you.
Hi! Any updates on where to get those files?
Also another thing: the driver is not picked up be the phone, it is still stays as USB Composite Device.
z3r0skull said:
Could you please explain how to split the bootloader image or attach the files?
Click to expand...
Click to collapse
@z3r0skull
you can extract the file with imjtool from the bootloader.img
on Linux that would be:
Code:
imjtool.ELF64 bootloader-oriole-slider-1.2-8085990.img extract
pierre383 said:
Pixel 6 Pro runs on a Google Tensor CPU which is in fact an Exynos CPU
This means that there is Exynos boot recovery in the CPU
You can repair the bootloader using the Samsung Exynos Tool
Nothing could be flashed from the mode, however it loads into the RAM the fastboot mode, from here reflash the bootloader image using fastboot
Unpack BL1, BL2 AP boot, ELR_EL3, BL etc from stock image (use your device and version)
[guide] repair hard bricked devices with deleted bootloader (sboot)
I'm writing this in android development section because this is only section for both models, i hope this is not a problem. Also i want to say thanks to sataccount from gsmhosting, he found working map at the end. This guide is for hard bricked...
forum.xda-developers.com
Set this up using windows 7 32 bit
use this config not the one he has included, but use his tutorial
DNW_STORE exynos down 200 20 bl1.bin
DNW_STORE exynos down 2000 20 bl2.bin
DNW_STORE exynos down 200 20 elr_el3.bin
DNW_STORE exynos down 200 20 lastly.bin
DNW_WAIT
;PIXEL ROM RECOVERY
DNW_STORE exynos down 20000 20 bl.bin
NOTE: this is EDL mode!!
If not working or you need help let me know
Click to expand...
Click to collapse
I extracted the bootloader but I don't see ELR_EL3, LASTLY or BL. Below is a list of the files that were extracted.
abl
bl1
bl2
bl31
gsa
ldfw
partition_0
partition_1
partition_2
partition_3
pbl
tzsw
ufs
ufsfwupdate
jac0b said:
I extracted the bootloader but I don't see ELR_EL3, LASTLY or BL. Below is a list of the files that were extracted.
abl
bl1
bl2
bl31
gsa
ldfw
partition_0
partition_1
partition_2
partition_3
pbl
tzsw
ufs
ufsfwupdate
Click to expand...
Click to collapse
Lastly is BL1 again, EL3 and BL31 is the same, BL is PBL (Short for primary BL)
I can't make the flashing work with the multidownloader
[COM3]Write thread Start##################
[COM3]Write Fail
[COM3]Write thread Exit##################
I'm using a Win7 32bit VM in VirtualBox
Did anyone actually recover a Pixel 6/pro device using this method?? I'm in the same position right now a serial interface with vendor ID bla bla.... cant go into bootloader nothing just dead device.
I hard bricked an LG G7 ThinQ G710EAW by flashing the wrong firmware (T-Mobile) onto it via LGUP. It now goes into EDL mode after shorting test points, but I'm unable to revive it by following this unbrick thread. Loading up the partition images via Partition Manager in QFIL "succeeds", but it doesn't revive my phone. Doesn't get me to fastboot. Still nothing on screen.
I also tried the rawprogram*.xml option using the XMLs in that thread, but QFIL keeps erroring out that the partition sizes defined in the XML are different from what it sees on the device.
The OP for the thread seems to not be active any longer.
Can someone here please help me understand how to recover my phone?
Anyone? Happy to donate for help as well.
Bumping up this thread.
If I had another EAW motherboard, would it help unbrick my motherboard? Wondering how I can fix my phone
So, I was able to finally figure this all out, recover my LG G710EAW and bring it back to life! It was a mix of information from many threads. No boxes, and no payment to anyone. All free.
The OP of this thread is active but has completely stopped responding to his thread and to his DMs - he's likely uninterested in a 4-5 year old phone at this point. In his first post he mentioned creating rawprogram* XMLs by hand, and it taking hour+ to do so. However, I'm unsure why it took him that long and in the end the files don't even work for QFIL since the sector size in the XMLs (512B) is different from device sector size (4096B). Nevertheless, I was able to flash these via command line 'edl' which ignored the sector size, but it didn't recover the device.
Generating rawprogram XMLs is easy if you can figure out how to run this Python program mentioned in this thread. However, the files attached there no longer work in 2022, the links are dead, and Python 2.7 is a dinosaur. Someone in that thread mentioned a different, fixed, repo but it didn't work with Python 2.7 for the 'undz' part. After a lot of head banging, I tried Python3 and 'undz' worked.
Here are the steps:
- Download the firmware for your model in KDZ format
- Install QPST
- Install Python3.x
- Run: pip3 install setuptools zstandard
- Download ZIP for kdztools from the repo: https://github.com/ErickG233/kdztools (or the attachment)
- Unzip kdztools and CD into that directory kdztools-master. This version is bug-fixed and also generates rawprogram files for us.
- Copy the firmware KDZ into kdztools-master directory
- Run: python3 unkdz.py -f G710EAW30e_00_0916.kdz -x. This creates a DZ file in a new `kdzextracted` folder
- Move the extracted DZ file from the kdzextracted folder back one level up, into kdztools-master dir
- Run: python3 undz.py -f G71030q_00_user-signed-ARB0_OPEN_ESA_DS_OP_0916.dz -c
- This creates a dzextracted folder here with all the files needed to recover your phone. Now all we need are the rawprogram XMLs.
- Run: python3 undz.py -f G71030q_00_user-signed-ARB0_OPEN_ESA_DS_OP_0916.dz -r. This will create all the rawprogram XMLs you need to flash. No patch files are created, but that is OK.
- In my case, QFIL complained it couldn't find file "PrimaryGPT_0.bin", so I copied file gpt_main0.bin_0 and renamed the copy gpt_main0.bin_0_copy > PrimaryGPT_0.bin
- Load your phone into EDL mode. If you want to use test points, see the image in this thread.
- Load QFIL. Use the ELF programmer file from any of the threads linked thus far. Select flat build. Load all rawprogram XMLs generated previously. Hit cancel when it asks for patch file XMLs.
- Hit Download.
This will recover your phone so it's able to boot and all. However, in my case, the phone had lost serial number and IMEI numbers (dual SIM) as well.
- To restore your IMEI numbers, you will need your QCN file or a backup of your FSG (fsg.img) partition from before bricking. In my case, I had flashed, via LGUP, T-Mobile firmware on my Indian phone. I then dumped all the partitions using command line EDL. I have not used QCN method since it seems to require a lot of steps to put the phone into diagnostics mode. I had a backup of the FSG partition, so I used that instead.
- If you have a backup of your FSG partition, load QFIL > Partition Manager. Erase modemst1 modemst2 and fsg partitions. Then, load the backup FSG.img file onto FSG partition. Restart phone.
- Now, if you have the serial number from your bill or box, see this thread to restore it. Pay extra attention to the Firehose configuration section, or else, it may create some issues. It's best to restore S/N after restoring IMEI in my experience, but this could just be some randomness or bad Firehose config during S/N restore.
This happiness was short-lived. When I was flashing all these KDZ via QFIL and LGUP trying to get my IMEIs back, I once saw "This phone is permanently locked and cannot be unlocked". That seems to have taken out my second SIM slot.
Now, after a fresh QFIL flash (with erase before download), my first SIM slot is also dead.
Neither of the SIM slots work now.
This has been so frustrating!
urover said:
This happiness was short-lived. When I was flashing all these KDZ via QFIL and LGUP trying to get my IMEIs back, I once saw "This phone is permanently locked and cannot be unlocked". That seems to have taken out my second SIM slot.
Now, after a fresh QFIL flash (with erase before download), my first SIM slot is also dead.
Neither of the SIM slots work now.
This has been so frustrating!
Click to expand...
Click to collapse
Any luck in recovering the phone ??
How do I make a full system backup including the currently installed firmware version? I would like to do this before I root the device. I have Global C61 and can’t find a full installer for reinstall of anything newer than C48. Thanks
I'm interested in this also....in addition, if you are on A11 with TWRP, when backing up do you select all partitions?
My choice (if you have the space) is to use EDL (or ROM bootloader on other devices) to do a complete save of your flash (as one file).
Ok, you might want to save all the partitions individually too, that will allow you to do rollbacks but keep the current userdata.
In the final analysis you can't do too much backing up (if you have the space).
TheGhost1951 said:
if you are on A11
Click to expand...
Click to collapse
I have A12, C61
Renate said:
use EDL
Click to expand...
Click to collapse
How do I do this?
Renate said:
save all the partitions individually
Click to expand...
Click to collapse
How do I do this?
Renate said:
if you have the space
Click to expand...
Click to collapse
You mean on my computer or on the phone? I have plenty of space in both locations, though
Just use Oneplus clone phone
I meant space on your desktop, flash drives, SD cards.
I'm not familiar with any specific OnePlus tools.
I just meant this as general advice for any device where you can get R/W access to the flash without actively using any of it at all.
That means EDL for Qualcomm devices, MTKClient for MediaTek devices, FEL mode for Allwinner devices...
DroidShift79 said:
Just use Oneplus clone phone
Click to expand...
Click to collapse
That's not what he wants. He's talking about NAND backup.
DroidShift79 said:
Just use Oneplus clone phone
Click to expand...
Click to collapse
Doesn't backup app data....
I can backup all partitions with MSM tool, just need fastboot script to "flash all" so that it doesn't have to be one img at a time.
Oh yeah, I got it wrong, sry.
SwiftBackup or titanium backup could help with apps and app data.
And if that's still not enough I would consider EDL/ MSM Tool
TheGhost1951 said:
I can backup all partitions with MSM tool, just need fastboot script to "flash all" so that it doesn't have to be one img at a time.
Click to expand...
Click to collapse
Restore OnePlus 9 to Stock via Fastboot Commands
This guide assumes you have the SDK Platform Tools installed and working, along with USB drivers for your device (if needed), and have your full update zip which you've already extracted the payload.bin from, and then dumped the images using...
forum.xda-developers.com
That could lead you in the right direction.
Saving the entire flash is the simplest, most bombproof and yes, least versatile way.
Of course you can save partitions individually also.
It's not even rocket science to make a script out of a partition listing.
You can also restore just fine with EDL, you don't particularly need fastboot.
Edit: See, I just backed up 32GB on my device:
Code:
C:\>edl /r /c61071327 nul:
Found EDL 9008
Configuring... Nope, configuring... Ok
Requesting read ... Ok, receiving 100% Ok
Now, where did that file go?
Renate said:
Saving the entire flash is the simplest, most bombproof and yes, least versatile way.
Of course you can save partitions individually also.
It's not even rocket science to make a script out of a partition listing.
You can also restore just fine with EDL, you don't particularly need fastboot.
Edit: See, I just backed up 32GB on my device:
Code:
C:\>edl /r /c61071327 nul:
Found EDL 9008
Configuring... Nope, configuring... Ok
Requesting read ... Ok, receiving 100% Ok
Now, where did that file go?
Click to expand...
Click to collapse
That's an approach i didn't know. Are you in the mood of writing a short step by step guide
The basics are getting into EDL mode and having your desktop EDL client.
The MSM tool is one client but as I've never used it, I'm not sure of its capabilities.
https://github.com/bkerler/edl is a Python imlementation.
Then there's my Windows implementation edl.exe that's in my sig.
On Windows I prefer using WinUSB directly instead of silly Qualcomm VCOM drivers.
Use https://zadig.akeo.ie/ and install WinUSB on 05c6/9008
You'll be needing a "loader" which is basically a replacement for SBL/XBL which does useful things.
A collection of loaders can be found here: https://github.com/bkerler/Loaders/
The correct one (if it exists) can be found automatically if you are using B. Kerler's client and you've downloaded everything.
If you're using my code the rest of this all deals with the specifics.
You can get the HWID and Hash and either manually look for a loader or ask me.
Code:
C:\>edl.exe /l
Found EDL 9008
Serial: 12345678
HWID: 000cc0e100000000, QC: 000cc0e1, OEM: 0000, Model: 0000
Hash: 7be49b72f9e43372-23ccb84d6eccca4e-61ce16e3602ac200-8cb18b75babe6d09
(That's a slash-ell up above.)
Then you look for something somewhere called 000cc0e100000000-7be49b72f9e43372
You download it and rename it something sane, like "phone.bin".
Code:
C:\>edl.exe /lphone.bin
...
Sending phone.bin 100% Ok
Waiting for Firehose... Ok
C:\>edl.exe /g
...
lots of partition listing
...
If that works, you have eMMC. If the /g part didn't work then you have UFS, in which case you can add /u to all commands: edl.exe /u /g
Look at the partition listing take the last partition and add the offset and count and you have the total number of sectors (either 512 eMMc or 4096 UFS).
Then just do the same command as up above.
Code:
C:\>edl.exe /r /c6107132 mybackup
You could also edl.exe /r /p1 partition1 or edl.exe /r /pboot boot.img.
And when you're done having fun edl.exe /z.
And if you have everything in one big 32, 64 or 128 GB chunk and you suddenly need to get a copy of the boot partition,
there are tools in Windows and Linux to chop that all up into partitions.
How do I properly exit EDL mode? I was stuck in it for a while, black screen no usb devices, but it eventually fixed itself.
Also I seem to be running into issues actually taking a backup: (Trying to back it up before trying lineage/crDroid, twrp fails to take an image as well)
Code:
K:\OnePlus9Pro>edl /l
Found EDL 9008
Serial: f709f1be
HWID: 001350e100514d67, QC: 001350e1, OEM: 0051, Model: 4d67
Hash: a26bc25799770106-f32c2856606a87ad-9c1e997d25b5e80f-f30b0e47e4c85e15
K:\OnePlus9Pro>edl /l9proloader.bin
Found EDL 9008
Resetting Sahara
Serial: f709f1be
HWID: 001350e100514d67, QC: 001350e1, OEM: 0051, Model: 4d67
Hash: a26bc25799770106-f32c2856606a87ad-9c1e997d25b5e80f-f30b0e47e4c85e15
Sending 9proloader.bin 100% Ok
Waiting for Firehose... Ok
K:\OnePlus9Pro>edl /g
Found EDL 9008
Configuring... Ok
Requesting GPT 0 header... Ok, receiving...
Could not read device
K:\OnePlus9Pro>edl /u /g
Could not find EDL device
K:\OnePlus9Pro>edl /l9proloader.bin
Could not find EDL device
K:\OnePlus9Pro>edl /l
Could not find EDL device
Next Session:
K:\OnePlus9Pro>edl /u /g
Found EDL 9008
Configuring... Ok
Requesting info...
<log value="ERROR: [ffu]FWversion:903." />
Ok
No LUNs found
K:\OnePlus9Pro>edl /r /u /l 9proloader.bin
Found EDL 9008
Resetting Sahara
Unknown cmd 6d783f3c in packet
K:\OnePlus9Pro>edl /g
Found EDL 9008
<log value="ERROR: Failed to run the last command -1" />
Configuring... Ok
Requesting GPT 0 header... No response
ajolly said:
How do I properly exit EDL mode? I was stuck in it for a while, black screen no usb devices, but it eventually fixed itself.
Also I seem to be running into issues actually taking a backup: (Trying to back it up before trying lineage/crDroid, twrp fails to take an image as well)
Code:
K:\OnePlus9Pro>edl /l
Found EDL 9008
Serial: f709f1be
HWID: 001350e100514d67, QC: 001350e1, OEM: 0051, Model: 4d67
Hash: a26bc25799770106-f32c2856606a87ad-9c1e997d25b5e80f-f30b0e47e4c85e15
K:\OnePlus9Pro>edl /l9proloader.bin
Found EDL 9008
Resetting Sahara
Serial: f709f1be
HWID: 001350e100514d67, QC: 001350e1, OEM: 0051, Model: 4d67
Hash: a26bc25799770106-f32c2856606a87ad-9c1e997d25b5e80f-f30b0e47e4c85e15
Sending 9proloader.bin 100% Ok
Waiting for Firehose... Ok
K:\OnePlus9Pro>edl /g
Found EDL 9008
Configuring... Ok
Requesting GPT 0 header... Ok, receiving...
Could not read device
K:\OnePlus9Pro>edl /u /g
Could not find EDL device
K:\OnePlus9Pro>edl /l9proloader.bin
Could not find EDL device
K:\OnePlus9Pro>edl /l
Could not find EDL device
Next Session:
K:\OnePlus9Pro>edl /u /g
Found EDL 9008
Configuring... Ok
Requesting info...
<log value="ERROR: [ffu]FWversion:903." />
Ok
No LUNs found
K:\OnePlus9Pro>edl /r /u /l 9proloader.bin
Found EDL 9008
Resetting Sahara
Unknown cmd 6d783f3c in packet
K:\OnePlus9Pro>edl /g
Found EDL 9008
<log value="ERROR: Failed to run the last command -1" />
Configuring... Ok
Requesting GPT 0 header... No response
Click to expand...
Click to collapse
I have yet to get twrp restore from backup to work properly. I just had to MSM my phone back to stock and start over from scratch cause TWRP restore messed things up....
TheGhost1951 said:
I have yet to get twrp restore from backup to work properly. I just had to MSM my phone back to stock and start over from scratch cause TWRP restore messed things up....
Click to expand...
Click to collapse
I've had success with older android versions, but not with 12. Annoyed that OnePlus updated the OS on me without warning, I thought I was just installing the latest security updates.
Just hoping to make a proper backup before flashing a new rom.
tk_xda said:
How do I make a full system backup including the currently installed firmware version? I would like to do this before I root the device. I have Global C61 and can’t find a full installer for reinstall of anything newer than C48. Thanks
Click to expand...
Click to collapse
Idk if this is what you're looking for but I love swiftbackup you can download it on the app store for free and move the file to your computer once it's complete or if you pay the fee you can back it up to whatever cloud storage you have it's only like 5 bucks for lifetime I believe, if you have root it'll also back up your app data so it restores all your apps as if you've just signed into them, they did put a warning recently of Google authenticator but mine still restored from a previous version
Renate said:
I meant space on your desktop, flash drives, SD cards.
I'm not familiar with any specific OnePlus tools.
I just meant this as general advice for any device where you can get R/W access to the flash without actively using any of it at all.
That means EDL for Qualcomm devices, MTKClient for MediaTek devices, FEL mode for Allwinner devices...
Click to expand...
Click to collapse
Hello dear i want to know
Are you in window 10? I mean which edl script you used is this in win10?
And is is there anyway to get rw in os12? In os11 its easy task
And about dump i try unpack ops and flash via dump command its take time and in the end get error
And device also not booted
I use this commamd
Edl py w extract