Unbrick help / Need bin. files - Nexus 5X Q&A, Help & Troubleshooting

Hy nexus friends,
I need help from someone with a 791F 32GB. I dont know if a 790 or a 16gb version is identical.
It would be great if someone with a rooted device can make a backup for me of the bootloader bin files.
aboot, sbl1, rpm, tz, sdi, sbl1b, tzb, rpmb, abootb, misc, laf, persist.
I flashed the hammerhead bootloader and stuck at 9008 mode.
It will be ver great if someone could help me.
Some partition apps could make a backup or with the dd command.
If i fet a solution, i would post it here. At the moment i had the device and the tools that i flashed for test a nexus 5 sbl. So write is possible.
Thanks for help guys

Where can I see if my phone is 791F?

i have the US Nexus 5X 32GB. Tell me what to do and I'll get you what you need.

tacofromhell said:
Where can I see if my phone is 791F?
Click to expand...
Click to collapse
Model number on the phone box and I believe in the bootloader screen: turn off phone then hold volume down and power.
Sent from my Nexus 5X using Tapatalk

SlimSnoopOS said:
Model number on the phone box and I believe in the bootloader screen: turn off phone then hold volume down and power.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Ok. Just rebooted into bootloader and under "Variant" it says LGH791 but no F, sorry

Thx for your help.
You can backup the partitions with some partition backup apps or with dd.
If you look with a file explorer in /dev/block/platform/soc.0/f9824900.sdhci/by-name/XXXXX , XXXX there are the partiton names.
If you want to copy with adb, make adb shell, su, and then:
dd if= /dev/block/platform/soc.0/f9824900.sdhci/by-name/cmnlib of=sdcard/cmnlib.img
Around 36 partitons are in the MM build. System, cache, userdata are not needed..

konsolen said:
Thx for your help.
You can backup the partitions with some partition backup apps or with dd.
If you look with a file explorer in /dev/block/platform/soc.0/f9824900.sdhci/by-name/XXXXX , XXXX there are the partiton names.
If you want to copy with adb, make adb shell, su, and then:
dd if= /dev/block/platform/soc.0/f9824900.sdhci/by-name/cmnlib of=sdcard/cmnlib.img
Around 36 partitons are in the MM build. System, cache, userdata are not needed..
Click to expand...
Click to collapse
Have you found a solution to get booting again? Been searching and tried multiple methods to repair my boot image on the H791 I own.
I have worked with another XDAer who extracted and now have the bootimage files from several stock H791 files available. They include the GPT from the stock image MDA89E and the boot image files from bootloader-bullhead-bhz10i.img bootloader-bullhead-bhz10k.img and bootloader-bullhead-bhz10m.img. Let me know if you still need these. I see 11 files in the boot image. During some testing I flashed over the sbl1 on my device and lost the ability do anything but go into QUSB DL mode 9008 as well.
As I am writing this I am now wondering if there is a separate set of SBL etc. files for the International variant? We may need to extract from the 791 tot file available the needed files if we do not have another method of obtaining them. Let me know if you have found a workable way to flash the needed boot images in place. Thanks.

nate0 said:
Have you found a solution to get booting again? Been searching and tried multiple methods to repair my boot image on the H791 I own.
I have worked with another XDAer who extracted and now have the bootimage files from several stock H791 files available. They include the GPT from the stock image MDA89E and the boot image files from bootloader-bullhead-bhz10i.img bootloader-bullhead-bhz10k.img and bootloader-bullhead-bhz10m.img. Let me know if you still need these. I see 11 files in the boot image. During some testing I flashed over the sbl1 on my device and lost the ability do anything but go into QUSB DL mode 9008 as well.
As I am writing this I am now wondering if there is a separate set of SBL etc. files for the International variant? We may need to extract from the 791 tot file available the needed files if we do not have another method of obtaining them. Let me know if you have found a workable way to flash the needed boot images in place. Thanks.
Click to expand...
Click to collapse
I'm on the same boat , hope you have something to boot it up
It's been more than 3 weeks, my 5X just brick itself . And LG doesn't support 5X in my country . I'm very very hoping you will find solution.

Apayah said:
I'm on the same boat , hope you have something to boot it up
It's been more than 3 weeks, my 5X just brick itself . And LG doesn't support 5X in my country . I'm very very hoping you will find solution.
Click to expand...
Click to collapse
I think the only way from my perspective so far is to manually flash the needed QComm/boot image/boot loader files with something that can interface with the phone. I am pretty sure I know a method to manually do this but need the flash programmer that works with this device to accomplish. Or if there is a way to add MSM8992 support to the BoardDiag tool, that would work...I have not given up, just have not had a whole lot of time to work on this the past 2 days.

nate0 said:
I think the only way from my perspective so far is to manually flash the needed QComm/boot image/boot loader files with something that can interface with the phone. I am pretty sure I know a method to manually do this but need the flash programmer that works with this device to accomplish. Or if there is a way to add MSM8992 support to the BoardDiag tool, that would work...I have not given up, just have not had a whole lot of time to work on this the past 2 days.
Click to expand...
Click to collapse
I see boardiag for n5 , please don't give up ?.
And i see blank flash file for N6

Try to connect the usb cable with the pressed vol up button. Normaly the lg download screen should pop up.
Its possible then to flash a tot file with the lg up tool.
But i found only one tot file around the i net.
It will be flashed but hang in the bootscreen.
A org. tot or kdz file were great or a solution to create such a file.

konsolen said:
Try to connect the usb cable with the pressed vol up button. Normaly the lg download screen should pop up.
Its possible then to flash a tot file with the lg up tool.
But i found only one tot file around the i net.
It will be flashed but hang in the bootscreen.
A org. tot or kdz file were great or a solution to create such a file.
Click to expand...
Click to collapse
I can go to download mode but it can't hang , the screen turns to black Immediately. I'm just waiting for another way .

Apayah said:
I can go to download mode but it can't hang , the screen turns to black Immediately. I'm just waiting for another way .
Click to expand...
Click to collapse
Yes. The FW download screen is not an option here. Seems those of us currently needing a solution or method is do to the phone being in QC emergency mode only. I can see my phone in device manager only as with the QC HUSB 9008 drivers.

nate0 said:
Yes. The FW download screen is not an option here. Seems those of us currently needing a solution or method is do to the phone being in QC emergency mode only. I can see my phone in device manager only as with the QC HUSB 9008 drivers.
Click to expand...
Click to collapse
Yes it same , i got that to.
So what is blank flash? on N6 thread .

链接:https://pan.baidu.com/s/1TmQ9jmdAym2NYt_YGyt2Cg 引脚:g5cg

Related

[HELP] Unbrick Huawei GR3 (TANGO) - TAG-L23

Guys: I need your understanding, experience, patience and HEEELP!!!
The history:
2 months ago, I bought a new HUAWEI GR3 (TANGO) TAG-L23. Processor = MT6753T
I tried to root it using KingoRoot. I Messed it up... Got a soft-brick: splash screen boot loop. At that moment, I still had access to Fastboot and Recovery mode (stock recovery).
After tons of days googling, found a TWRP recovery that someone claimed that worked in GR3.
I decided to flash it using fastboot commands from my PC. Result = OK. Flashed and worked like a charm.
Tired of searching a stock/custom firmware for GR3 TAG-L23, I decided to download and flash a GR3 TAG-L22 rom using TWRP.
Result = Messed it up again... this time worst... Hard-bricked I think: the phone didn't show any light, couldn't boot it again in any mode... Dead...
The only hope I had is that it is detected by Windows for about 10 seconds as MEDIATEK USB PORT (COMxx) where xx changes when I connect it from one USB port to another.
Since then, I tried almost every tutorial/video/solution/forum/website over the internet, tried almost every SP Flash tool version from v3.1224 to v5.1628, downloaded every scatter.txt for MT6753 processor, tried changing with/without battery option in SPFT, pressing every phone buttons combos, with no luck...
I always get the same error: S_FT_ENABLE_DRAM_FAIL (0xFC0)
Downloaded and installed almost every driver I found on internet: not overwritting them... I created a Virtual Machine, and test them separately using snapshots. Result = Same DRAM_FAIL error.
last week, got another HUAWEI GR3 TAG-L23, untouched, brand new...
I did the following with the new one:
Flashed TWRP recovery using fastboot commands = OK
Rooted it using SuperSU = OK
executed tons of ADB commands that found over the internet, to dump the partition table and stock rom using dd command = OK (I think... what I got is a bunch of files - system, lk, boot, logo, cache, frp, userdata, secro, recovery, nvdata, protect1 and 2, tee1 and 2, and so on).
Using the partition table information, edited one scatter.txt file for MT6753 and, one by one, adjusted the partition info (start and lenght). I did it because when using any downloaded scatter file, and selecting the files that I got from dd commands, SPFT showed error messages saying them were wrong. After editing it and loading the files that I got from the second phone, SPFT recognized them as good ones.
But.... I'm still getting the d...mn S_FT_ENABLE_DRAM_FAIL (0xFC0) error
Also tried to get a rom backup and scatter file from the second phone using MTK DROID ROOT & TOOLS v2.5.3 with no luck: it shows all phone information (except IMEIs), a green rectangle shows up, but... a weird message appears at right: "ERROR: TotalBytesPerChunk Not Found. Set Default Page/Spare=2048/64 !!!". Then I click on "BLOCKS MAP" button, a new window appears showing the partition info (that already got using adb command prompt) and "create scatter file" button is grayed out... And if I try to perform the backup, it starts fine, but ends with error, and no file is backed up...
Let me mention that I already read and googled the totalbytesperchunk error and the grayed out button stuff and tried all alternatives too, and nothing worked.
My work environment:
PC = Laptop With 8 GB RAM / Windows 10 pro x64
Virtual Machines: Windows 7 pro 32 bits, Windows XP 32 bits, Ubuntu 32 and 64 bits...
What else can I do?
How can I use the second, rooted and working phone to get a rom/firmware working dump? it is possible?
If someone decides to help me, let me know what do you need (dumped files, downloaded scatter.txt files, screenshots, whatever you need...)
COM## is a COM port. You can use a terminal program to directly interact with the device.
You are not completely bricked yet.
I do not have any further details to help you, but I can tell you there is still hope.
Connect the dead device to PC, load up a terminal app (if on windows, just load up the app named Terminal)
See where you can get with that.
good luck
Please Help cesarr4: my TAG-L23 bricked - Need your TWRP
I have a bricked GR3 after using Kingo Root. You mention in the post:
"After tons of days googling, found a TWRP recovery that someone claimed that worked in GR3. I decided to flash it using fastboot commands from my PC. Result = OK. Flashed and worked like a charm."
Please share this TWRP recovery, please.
antonioroa said:
I have a bricked GR3 after using Kingo Root. You mention in the post:
"After tons of days googling, found a TWRP recovery that someone claimed that worked in GR3. I decided to flash it using fastboot commands from my PC. Result = OK. Flashed and worked like a charm."
Please share this TWRP recovery, please.
Click to expand...
Click to collapse
I attached the recovery I'm currently using in the second GR3. I'm still looking forward the stock rom and a way to recover the first one... have u found a way to unbrick it?
Here you can find the recovery too: http://forum.xda-developers.com/android/development/recovery-twrp-3-0-2-0-huawei-tag-l01-p8-t3433520
I have the same problem with kingroot, and cannot find TAG-L23 rom.
I sent my phone to huawei support and they said it's a board problem and need to replace, the cost is near to the phone's original price.... No way!
In clangsm web page there's a stock rom but you need to pay for vip membership.
Please help with this issue.
I'm still trying to get a working rom image from the 2nd GR3 that I bought... No luck yet... I'm plenty sure that there is no need to do hardware replacement... can anyone point me to a tool/step-by-step guide to readback and save a flashable rom image from GR3 phone, and a SP tools that works with GR3 chipset/PCB?
Hi, i have a TAG-L01 and i got the same problem, i've tried a lot with no lucky, it seems sp flash tool don't support our device(or is huawei that don't want).
If you have some ideas please tell me, i will help(our devices are exactly the same, all TAG-Lxx are the same)
Hello
I have a TAG-L23. I was able to install the TRWP recovery mentioned in previous posts. But I do need the Stock ROM, since I am not able to start the phone. It is allways rebooting. any idea where to find the ROM? maybe cesarr4 can do a backup on TWRP from his second phone and we can load it. just make a backup in the recovery and Zip it, then you may share it.
srgg01 said:
Hello
I have a TAG-L23. I was able to install the TRWP recovery mentioned in previous posts. But I do need the Stock ROM, since I am not able to start the phone. It is allways rebooting. any idea where to find the ROM? maybe cesarr4 can do a backup on TWRP from his second phone and we can load it. just make a backup in the recovery and Zip it, then you may share it.
Click to expand...
Click to collapse
Done. Where can I share it for you?
cesarr4 said:
Done. Where can I share it for you?
Click to expand...
Click to collapse
please share your ROM in google drive. i've got same problem here.
Any link to the TAG-L23 ROM? please share as I believe mine is corrupted.

[Unbrick] How to revive H815 - no recovery/fastboot/download mode

Today something went wrong while flashing weekly LOS build and my LG G4 (H815 with v20P firmware) went into very fast bootloop: https://www.youtube.com/watch?v=9gm0dh6bLp4
In this state i wasn't able to enter recovery, nor fastboot, nor download mode. Only IMEI screen (Vol Up + Vol Down I believe) was accessible which was no use.
Here are the steps which got me out of troubles:
A) Verify that you have LGUP installed and have proper 8994.dll version for your device.
Different versions of FW use different libraries which results in errors during flashing.
Steps:
1) Install LGUP with this guide https://forum.xda-developers.com/g4/help/lgup-install-kdz-mm-lp-t3249803
2) Get the right DLL. You can try this one:
Abandoned War Place said:
FIX REFUBRISH/DOWNGRADE ETC STUCK AT 16% DOWNLOAD MODE UNABLE TO GET BACK TO STOCK
error 0x2000 invalid command response Has Been FixeD WITH THE LASTEST DLL FILE
FILE INCLUDE (DLL+PATCH_DLL+SETUP LGUP+DRIVER) package
Please Read The *READ ME FILE FOR THE RIGHT INSTALLATION WITHOUT GETTING ANY PROBLEM :
Link Easy To Download No Ads Bulllsh*t.................. :
https://drive.google.com/file/d/0B_yWw6RLoA-gdTMtZFczMUhQOHM/view?usp=sharing
Click to expand...
Click to collapse
...or extract it directly from KDZ file with extractor https://forum.xda-developers.com/showthread.php?t=2600575.
You need to extract it from FW version that your phone is already running, not from the one you are about to flash! (when flashing from v20d to v20p you need v20d version, but when reflashing v20p FW you need the v20p DLL)
3) Navigate to LGUP install folder (default "C:\Program Files (x86)\LG Electronics\LGUP")
4) Overwrite the old DLL located in "model\8994" folder version with new one in
I don't know the exact compatibility, or how many different DLL versions are out there. Hopefully it doesn't brick the device even more when wrong version is used, it just doesn't work.
B) Write h815 image to sdcard as mentioned here:
leptdre said:
Hi guys,
i came up with a temporary to unbrick LG G4 H815 , you just need a 32 GB SD card ( i used Sandisk 10 class) , the dump that i will link , and Win32 disk Imager, the SD card must low level formatted.
1- download this dump
http://www.4shared.com/rar/NzSqsBzib...230737_00.html
2- put the SD card in the PC and chose the dump file and write ( run as admin ):
Click to expand...
Click to collapse
It worked for me with just 8GB one. Be aware that the image written to SD have like 20 partitions so windows might go crazy.
C) Follow these steps:
jam1445 said:
3. One the Write Completes. Eject Card and insert in your LG G4 H811. Press Volume Up Button while connecting the USB Cable.
4. There you go, it will open the download mode.
Click to expand...
Click to collapse
D) At this moment my G4 finally entered Download mode
I was able to reflash KDZ using the usual procedure (select UPGRADE, find a KDZ file, restart LGUP, select REFURBRISH and START). Initially I got 0x2000 error at approximately 16% (boot displayed as status) that was caused by old version of 8994.dll library.
E) Back to stock
Now you should have stock H815 again so lets flash LOS back as usual
Kudos to OPs: @bullghost , @shakeyabooti , @leptdre , @jam1445 and other posters on G4 section of XDA!
Hope this helps someone!
Good job. If your using this and you're gonna buy a SDCard on purpose, be aware that this fix might not work on your device. Ehehe
@Jirrick im getting the same error on LGUP where do i find a newer version of the dll?
inso420 said:
@Jirrick im getting the same error on LGUP where do i find a newer version of the dll?
Click to expand...
Click to collapse
are these what you looking for.?
https://forum.xda-developers.com/showpost.php?p=73586554&postcount=921
VS986 Stuck on Download Mode
Jirrick said:
Today something went wrong while flashing weekly LOS build and my LG G4 (H815 with v20P firmware) went into very fast bootloop: https://www.youtube.com/watch?v=9gm0dh6bLp4
In this state i wasn't able to enter recovery, nor fastboot, nor download mode. Only IMEI screen (Vol Up + Vol Down I believe) was accessible which was no use.
Here are the steps which got me out of troubles:
A) Verify that you have LGUP installed and have proper 8994.dll version for your device.
Different versions of FW use different libraries which results in errors during flashing.
Steps:
1) Install LGUP with this guide https://forum.xda-developers.com/g4/help/lgup-install-kdz-mm-lp-t3249803
2) Get the right DLL. You can try this one:
...or extract it directly from KDZ file with extractor https://forum.xda-developers.com/showthread.php?t=2600575.
You need to extract it from FW version that your phone is already running, not from the one you are about to flash! (when flashing from v20d to v20p you need v20d version, but when reflashing v20p FW you need the v20p DLL)
3) Navigate to LGUP install folder (default "C:\Program Files (x86)\LG Electronics\LGUP")
4) Overwrite the old DLL located in "model\8994" folder version with new one in
I don't know the exact compatibility, or how many different DLL versions are out there. Hopefully it doesn't brick the device even more when wrong version is used, it just doesn't work.
B) Write h815 image to sdcard as mentioned here:
It worked for me with just 8GB one. Be aware that the image written to SD have like 20 partitions so windows might go crazy.
C) Follow these steps:
D) At this moment my G4 finally entered Download mode
I was able to reflash KDZ using the usual procedure (select UPGRADE, find a KDZ file, restart LGUP, select REFURBRISH and START). Initially I got 0x2000 error at approximately 16% (boot displayed as status) that was caused by old version of 8994.dll library.
E) Back to stock
Now you should have stock H815 again so lets flash LOS back as usual
Kudos to OPs: @bullghost , @shakeyabooti , @leptdre , @jam1445 and other posters on G4 section of XDA!
Hope this helps someone!
Click to expand...
Click to collapse
I just did all your steps for my VS986 , and I got 2 G4 Verizon's back up and working , Thank you so much.
---------- Post added at 10:54 AM ---------- Previous post was at 10:53 AM ----------
I just did all your steps for my VS986 , and I got 2 G4 Verizon's back up and working , Thank you so much.
I'm using a 16gb microsd, but however I try to image it (exfat, fat32 filesystems, different win32imager versions) also have tried different cables, but it still doesn't show any sign of life. I bricked it exactly the same way as OP did. Does anyone have anything else I could try to fix this? Also does the battery charge when its on 9008 mode?
inteLzzz said:
I'm using a 16gb microsd, but however I try to image it (exfat, fat32 filesystems, different win32imager versions) also have tried different cables, but it still doesn't show any sign of life. I bricked it exactly the same way as OP did. Does anyone have anything else I could try to fix this? Also does the battery charge when its on 9008 mode?
Click to expand...
Click to collapse
Can you get at least to the IMEI Display mode (Vol UP and then quickly Vol DOWN, keep both pressed until it shows up)?
Jirrick said:
Can you get at least to the IMEI Display mode (Vol UP and then quickly Vol DOWN, keep both pressed until it shows up)?
Click to expand...
Click to collapse
No could it be caused by low battery? I remember it being like 30% when I bricked it, and does it charge under 9008 mode?
Sorry to hear that. I'm afraid this is beyond my knowledge if it wont even enter the IMEI screen. I suppose you can leave it bootlooping in charger over night and then try in the morning?
Jirrick said:
Sorry to hear that. I'm afraid this is beyond my knowledge if it wont even enter the IMEI screen. I suppose you can leave it bootlooping in charger over night and then try in the morning?
Click to expand...
Click to collapse
It does not bootloop, straight up dead. Just shows 9008 forever on the pc, I left it for like 2 hours like that yesterday. I'll leave it overnight today and if not I'll hack up a direct 5v 1a charger to charge the battery directly. If both don't work i'll probably flash LS991 files in QFIL and use it as a tablet afterwards.. damn i got this phone not even 2 weeks ago perfect condition and all. Will not buy any more damn LG devices.
Oh, I thought your phone was rapidly bootlooping like mine did. Sounds like the person who sold it to you was aware that the phone is on last legs (probably even baked the phone so it runs for few days more) and screwed you over. My next phone wont be LG either.

Nuked LAF = No Download Mode,always without fastboot

Hello everyone, today I made a bull****, let's start from the beginning, my K10 2017 M250n had Android Oreo and I had come to know the exploit LGLAF, I tried, and did not work because I discovered that the flaw was patched on Android Oreo but I had the idea to downgrade to Nougat, after hours of problems due to drivers I can flashare nougat with LG UP in Download Mode, after doing the Downgrade, with the Dual-Boot to Linux on PC I used LGLAF on Linux, I made a backup of the LAF partition, I have the IMG file, a backup of the recovery, always an IMG I created, I did the wipe, I restarted and I tried to boot in fastboot, it does not boot, I tried to start in Download Mode, it does not work, all this to try to unlock the BootLoader, flash the TWRP and root.
Now how do I update and report the Download Mode?
I'm stuck without Fastboot, without Download Mode and with Android Nougat.
http://www.mediafire.com/file/y0d8sj4od5j3a34/laf.img/file
http://www.mediafire.com/file/179cr1b1y2d62cy/recovery.img/file
But you can boot it normally, I guess. Then hopefully Oreo ota update fixes it...
No, I can not find the updates anymore
XRed_CubeX said:
No, I can not find the updates anymore
Click to expand...
Click to collapse
i suggest that you try to update your phone via lg up by downloading the kdz of your exact phone model and without booting into download mode just by booting normal and i hope it solved
no warranty No promises... and no responsibility i take
abdoh01 said:
i suggest that you try to update your phone via lg up by downloading the kdz of your exact phone model and without booting into download mode just by booting normal and i hope it solved
no warranty No promises... and no responsibility i take
Click to expand...
Click to collapse
I tried and does not work, simply before Flash restarts you downloading and mode flash but I'm unloaded mode.
XRed_CubeX said:
No, I can not find the updates anymore
Click to expand...
Click to collapse
And you have done the factory reset? Then maybe laf is needed for the fota too??
At the end is the latest fota update, but no idea if it can be used similar way as before. [***]
https://forum.xda-developers.com/showpost.php?p=59103556&postcount=326
Now it probably should be named as dlpkgfile and placed in /data/fota/ or /cache/fota/ if smaller ...
But how to put it there, IDK... Also LGUP has some FOTA mode but haven't tested it.
LGM250nAT-V20b-EUR-XX-AUG-13-2018+0_fota.up
https://mega.nz/#!WpkERCgK!QiqndSPXG2aaaq7jqoG27IyBvhfd16bh6G2gNs7UoeA
edit: [***] hiddenmenu opens by calling *#546368#*250# and there you'll find that package select
mentioned in the first link. File in /storage/emulated/0/SoftwareUpdate/ shows but I don't want to update yet...
:good:
CXZa said:
And you have done the factory reset? Then maybe laf is needed for the fota too??
At the end is the latest fota update, but no idea if it can be used similar way as before. [***]
https://forum.xda-developers.com/showpost.php?p=59103556&postcount=326
Now it probably should be named as dlpkgfile and placed in /data/fota/ or /cache/fota/ if smaller ...
But how to put it there, IDK... Also LGUP has some FOTA mode but haven't tested it.
LGM250nAT-V20b-EUR-XX-AUG-13-2018+0_fota.up
https://mega.nz/#!WpkERCgK!QiqndSPXG2aaaq7jqoG27IyBvhfd16bh6G2gNs7UoeA
edit: [***] hiddenmenu opens by calling *#546368#*250# and there you'll find that package select
mentioned in the first link. File in /storage/emulated/0/SoftwareUpdate/ shows but I don't want to update yet...
:good:
Click to expand...
Click to collapse
Error RESULT_NOT_EXECUTED
XRed_CubeX said:
Error RESULT_NOT_EXECUTED
Click to expand...
Click to collapse
Pity... it then maybe use laf - although there is also fota tools on
the recovery. What about LGUP, is there fota option or have I dreamed it.
CXZa said:
Pity... it then maybe use laf - although there is also fota tools on
the recovery. What about LGUP, is there fota option or have I dreamed it.
Click to expand...
Click to collapse
The problem that I have formatted laf,i cant boot on download mode, how can I reboot in recovery mode?
XRed_CubeX said:
The problem that I have formatted laf,i cant boot on download mode, how can I reboot in recovery mode?
Click to expand...
Click to collapse
Some fota tools are there in the sbin, but I don't know how can they be activated.
Fota file must be in some default folder and recovery maybe booted having a
command somewhere....
You can reboot to recovery using adb, or in terminal "reboot recovery"
or "setprop sys.powerctl reboot,recovery"
I was thinking that maybe LGUP changes the mode like it does
before flashing kdz files. If in normal mode, that is.
And if it uses recovery mode with fota then it might work.
Just hoping not knowing...
CXZa said:
Some fota tools are there in the sbin, but I don't know how can they be activated.
Fota file must be in some default folder and recovery maybe booted having a
command somewhere....
You can reboot to recovery using adb, or in terminal "reboot recovery"
or "setprop sys.powerctl reboot,recovery"
I was thinking that maybe LGUP changes the mode like it does
before flashing kdz files. If in normal mode, that is.
And if it uses recovery mode with fota then it might work.
Just hoping not knowing...
Click to expand...
Click to collapse
The recovery mode says No Command.
XRed_CubeX said:
The recovery mode says No Command.
Click to expand...
Click to collapse
Press power and then vol up shortly. Same time that is.
CXZa said:
Press power and then vol up shortly. Same time that is.
Click to expand...
Click to collapse
When I try to do FOTA upgrade on LG UP it gives me the error "Error: 0x2000, Fail! MTP is not Running" but when in fact the device to recognize the port MUST be in MTP and I in MTP mode I have it put.
XRed_CubeX said:
When I try to do FOTA upgrade on LG UP it gives me the error "Error: 0x2000, Fail! MTP is not Running" but when in fact the device to recognize the port MUST be in MTP and I in MTP mode I have it put.
Click to expand...
Click to collapse
IDK. Are you using LGUP having a patched exe and the dll?
Is the dll our own? Does it matter if it's own or not? IDK.
Patching it is instructed somewhere...
edit: patching not needed as fota mode shows already.
edit22: have you the WPDAPI.exe in the LGUP\main\Common dir?
the LGUP_Common.dll might need it...
There is still that other way, using that "Activity Launcher" app,
or "am start -n com.lge.lgfota.permission/com.lge.lgfota.permission.DmcEzUpdateStart"
And what about a newer tool, LGBridge? I read somewhere at LGlaf github
that its or SupportTool's protocol data looks different compared to LGlaf.
https://github.com/Lekensteyn/lglaf/issues/7
What else is different...
CXZa said:
IDK. Are you using LGUP having a patched exe and the dll?
Is the dll our own? Does it matter if it's own or not? IDK.
Patching it is instructed somewhere...
edit: patching not needed as fota mode shows already.
edit22: have you the WPDAPI.exe in the LGUP\main\Common dir?
the LGUP_Common.dll might need it...
There is still that other way, using that "Activity Launcher" app,
or "am start -n com.lge.lgfota.permission/com.lge.lgfota.permission.DmcEzUpdateStart"
And what about a newer tool, LGBridge? I read somewhere at LGlaf github
that its or SupportTool's protocol data looks different compared to LGlaf.
https://github.com/Lekensteyn/lglaf/issues/7
What else is different...
Click to expand...
Click to collapse
How to get WPDAPI?
XRed_CubeX said:
How to get WPDAPI?
Click to expand...
Click to collapse
It's many times included in those hacked version packages.
I guess it was included with dll needed, but don't know for sure.
Here it's needed
https://forum.xda-developers.com/showpost.php?p=75677301&postcount=6
I don't when it will be needed in this long thread.
https://forum.xda-developers.com/lg-g5/how-to/unlocking-lgup-features-fun-profit-t3634650
Maybe it's said somewhere in it. The exe is mentioned in the dll though...
From where? See the attachment. The UI_Config.lgl in it gives more options.
No hacking and cracking needed. But is a hacked version better, IDK...
CXZa said:
It's many times included in those hacked version packages.
I guess it was included with dll needed, but don't know for sure.
Here it's needed
https://forum.xda-developers.com/showpost.php?p=75677301&postcount=6
I don't when it will be needed in this long thread.
https://forum.xda-developers.com/lg-g5/how-to/unlocking-lgup-features-fun-profit-t3634650
Maybe it's said somewhere in it. The exe is mentioned in the dll though...
From where? See the attachment. The UI_Config.lgl in it gives more options.
No hacking and cracking needed. But is a hacked version better, IDK...
Click to expand...
Click to collapse
Always the same error, but also the method of DmcEzUpdateStart remains with the words "FOTA EASY UPDATE" and then crash.
No solution?
There is a scatter file so you can flash it from SP Flash Tools??
XRed_CubeX said:
There is a scatter file so you can flash it from SP Flash Tools??
Click to expand...
Click to collapse
LG has made so much changes that I think that it doesn't work as mtk device anymore.
Anyway the MTK driver package IDs probably have to be changed... at least.
With LG drivers installed, the SP Flash Tool readback started, a text about
LG connection was shown, but it just failed - miserably...
If you uninstall the lg drivers and maybe mtk too. And then connect it
(without the battery?), you might see that it shows itself as MTK preloader
for a second or two. With lg drivers it shows as something else, I think...
When doing readback from a normal mtk device I think it is the preloader
which is used. When downloading a firmware, I don't remember does it
switch to another state that is used... serial or whatever the text says
in SP Flash Tool, but was it with or without the preloader text... ??? IDR...

can someone share the partition(s) that will get download mode working?

I deleted all the partitions on my g8 using qfil, now the phone has nothing but an edl mode. If someone could share a backup of the partitions that would get download mode working, I could flash a kdz I have with lgup.
Help would be appreciated
leopard_fist said:
I deleted all the partitions on my g8 using qfil, now the phone has nothing but an edl mode. If someone could share a backup of the partitions that would get download mode working, I could flash a kdz I have with lgup.
Help would be appreciated
Click to expand...
Click to collapse
So when u bring up 'manage partitions' in qfil, what do u see? Nothing? If that's the case u need the backed up partitions and the xml which has offsets etc of where to flash the images, not just the specific partitions.
cheers
AsItLies said:
So when u bring up 'manage partitions' in qfil, what do u see? Nothing? If that's the case u need the backed up partitions and the xml which has offsets etc of where to flash the images, not just the specific partitions.
cheers
Click to expand...
Click to collapse
there's nothin there in qfil, so I guess i'd need the xml also, anyone have this and could share?
i figure i can put a little work in before i throw in the cards and return the phone to amazon
leopard_fist said:
I deleted all the partitions on my g8 using qfil, now the phone has nothing but an edl mode. If someone could share a backup of the partitions that would get download mode working, I could flash a kdz I have with lgup.
Help would be appreciated
Click to expand...
Click to collapse
So I put together something that might help, but you'll probably have to make modifications to the xml to get it to work.
I don't know what the xml should look like for it to work with qfil. This is the xml generated by bkerler edl backup python scripts (with the bkerler scripts, you indicate, on the command line, where the bin files are, so it's not in the xml. But, I think the qfil interface needs that info to be in the xml. I could be wrong about that, you'll have to look at qfil and make changes to the xml if needed).
Also, the xml for luns 1 and 2 files are accurate, but not the xml for lun4. You would also need to edit out all the xml restore in rawprogram4 to only include the files for that lun (to get lgup - boot, abl, laf, and gpt*4).
Lastly, this is from a sprint backup, not sure that matters much except in that there is no kdz for sprint, so not sure how your device will respond in lgup if u use these and then try to lgup a vzw kdz (or any kdz), since there's no totc file to 'ID mismatch' with...
good luck
leopard_fist said:
there's nothin there in qfil, so I guess i'd need the xml also, anyone have this and could share?
i figure i can put a little work in before i throw in the cards and return the phone to amazon
Click to expand...
Click to collapse
wow, return the phone 'in the condition it was in when received' is usually a prerequisite right? In other words... not bricked?
good luck with that too.
AsItLies said:
wow, return the phone 'in the condition it was in when received' is usually a prerequisite right? In other words... not bricked?
good luck with that too.
Click to expand...
Click to collapse
thanks for your time - i'll give it a try when i get home from work this evening, even though it looks to be over my head maybe i can figure it out.
it's actually a sprint phone, though i know a way to crossflash anyway.
you figure i can't return the phone? i just spent 200 bucks on this phone a few days ago, i hope thats not the case
the thing is - my jobs getting ready to send me out of state for a new position. my present phones old, slow, and the screens cracked, so i thought id start things off by getting myself a decent phone and working on setting it up - at present though ive just got an unresponsive piece of plastic.
ive rooted many phones in my day, but this one got me, what can i say
leopard_fist said:
the thing is - my jobs getting ready to send me out of state for a new position. my present phones old, slow, and the screens cracked, so i thought id start things off by getting myself a decent phone and working on setting it up - at present though ive just got an unresponsive piece of plastic.
ive rooted many phones in my day, but this one got me, what can i say
Click to expand...
Click to collapse
Hey it's not my place to tell you what to do. But I can tell you, personally, if I screw up, I take responsibility for it.
leopard_fist said:
I deleted all the partitions on my g8 using qfil, now the phone has nothing but an edl mode. If someone could share a backup of the partitions that would get download mode working, I could flash a kdz I have with lgup.
Help would be appreciated
Click to expand...
Click to collapse
Just follow this thread.
netmsm said:
Just follow this thread.
Click to expand...
Click to collapse
netmsm, thanks for the reply - if I follow the instructions in the thread you linked, is it true that i'll have no imei and serial number on the phone after the process?
thanks again
leopard_fist said:
netmsm, thanks for the reply - if I follow the instructions in the thread you linked, is it true that i'll have no imei and serial number on the phone after the process?
thanks again
Click to expand...
Click to collapse
That's true. You lose IMEI when you erase all partitions. Except, you have crated a backup of Modemst(1 or 2) or FSG partitions so you can restore them, but after recovering from hard brick. So first recover phone following instructions then restore Modemst 1 and 2 or just the FSG.
If your phone is factory unlocked version and you have no backup maybe we can repair IMEI, maybe! Just recover the phone for now.
netmsm said:
That's true. You lose IMEI when you erase all partitions. Except, you have crated a backup of Modemst(1 or 2) or FSG partitions so you can restore them, but after recovering from hard brick. So first recover phone following instructions then restore Modemst 1 and 2 or just the FSG.
If your phone is factory unlocked version and you have no backup maybe we can repair IMEI, maybe! Just recover the phone for now.
Click to expand...
Click to collapse
I have backups of the following files - would the imei/serial info be contained in any of these?
thank you
ftm
modem_a
modem_b
op_a
op_b
sid_a
sid_b
abl_a
abl_b
boot_a
boot_b
leopard_fist said:
I have backups of the following files - would the imei/serial info be contained in any of these?
thank you
ftm
modem_a
modem_b
op_a
op_b
sid_a
sid_b
abl_a
abl_b
boot_a
boot_b
Click to expand...
Click to collapse
Nope, sorry to say. FTM keeps identity data as a temp place from which IMEI cannot be restored. However, you can find the original IMEI from FTM. You need a box to repair the IMEI. The only tool that can repair LG SDM855 phones' IMEI is Octopus. So, you know what to do, I guess ^_^

ROM Lg g8 thinq Extracting

Hello everyone, I'm new on the forum. Sorry to bother you, I've been reading most of the threads about the G8 thinq. My problem is that I can't extract LG's kdz firmware properly. I already tried with the Lg extract, with the CMD, with Power Shill. None manage to extract the '.DZ' Please share me a rom that is already extracted, thanks in advance.
CloudStrife97 said:
Hello everyone, I'm new on the forum. Sorry to bother you, I've been reading most of the threads about the G8 thinq. My problem is that I can't extract LG's kdz firmware properly. I already tried with the Lg extract, with the CMD, with Power Shill. None manage to extract the '.DZ' Please share me a rom that is already extracted, thanks in advance.
Click to expand...
Click to collapse
So a couple of things, the kdz extractor tools are plentiful, some work under windows and some under linux. I've used the linux version and it does work, no issues. The DZ file is basically the KDZ uncompressed. It's a large single file.
The DZ is then further broken down by the utility into various forms due to the command you use, you can get partition images and chunks of images etc etc.
2nd, you ask for a 'rom that is already extracted'? That's a lot of images, about 5 gig worth, what **exactly** are you trying to do? Maybe you only need a few files? Maybe you need files from a specific rom version? Maybe you need a kdz rom that doesn't even exist? Like at&t and sprint?
you might want to fill in some details for anyone to help.
AsItLies said:
So a couple of things, the kdz extractor tools are plentiful, some work under windows and some under linux. I've used the linux version and it does work, no issues. The DZ file is basically the KDZ uncompressed. It's a large single file.
The DZ is then further broken down by the utility into various forms due to the command you use, you can get partition images and chunks of images etc etc.
2nd, you ask for a 'rom that is already extracted'? That's a lot of images, about 5 gig worth, what **exactly** are you trying to do? Maybe you only need a few files? Maybe you need files from a specific rom version? Maybe you need a kdz rom that doesn't even exist? Like at&t and sprint?
you might want to fill in some details for anyone to help.
Click to expand...
Click to collapse
Hello, thanks for answering. I will begin to tell my story. I have an Lg G8 ThinQ Sprint with Android 10. It is network unlocked because I can use it here in Honduras. I did the Crossflash tutorial ( https://forum.xda-developers.com/t/tutorial-crossflash-bypass-opid-mismatched-error.4345963/ )
While using the QFIL I deleted flash from one of the 7 partitions the tutorial says. My phone no longer exits EDL mode ( Qualcomm HS-USB QDloader 9008 (COM5)) So I went to this tutorial: (https://forum.xda-developers.com/t/lg-g8-stuck-in-qualcomm-hs-usm-qdloader-9008.4050197/).
I followed the steps to load the ¨Lun¨, I did it in PowerShell, because in CMD it didn't work for me. Apparently the ¨Lun¨ were installed well. Now the problem is that I can't install the necessary partitions, because I can't unzip the .DZ ROM
Help, what do I do? My cell phone is only in Qualcomm HS-USB QDloader 9008 mode, it does not go to download mode
CloudStrife97 said:
Hello, thanks for answering. I will begin to tell my story. I have an Lg G8 ThinQ Sprint with Android 10. It is network unlocked because I can use it here in Honduras. I did the Crossflash tutorial ( https://forum.xda-developers.com/t/tutorial-crossflash-bypass-opid-mismatched-error.4345963/ )
While using the QFIL I deleted flash from one of the 7 partitions the tutorial says. My phone no longer exits EDL mode ( Qualcomm HS-USB QDloader 9008 (COM5)) So I went to this tutorial: (https://forum.xda-developers.com/t/lg-g8-stuck-in-qualcomm-hs-usm-qdloader-9008.4050197/).
I followed the steps to load the ¨Lun¨, I did it in PowerShell, because in CMD it didn't work for me. Apparently the ¨Lun¨ were installed well. Now the problem is that I can't install the necessary partitions, because I can't unzip the .DZ ROM
Help, what do I do? My cell phone is only in Qualcomm HS-USB QDloader 9008 mode, it does not go to download mode
Click to expand...
Click to collapse
So honestly I'm confused by where you are or what the situation is. But no matter.
This link is for the Lun4 partitions of sprint a10 backup. It has the rawprogram xml needed to flash it.
My understanding is that should be all you need to get LGUP to work. So flash that with qfil and then go directly to LGUP with the key combo.
Then, in lgup, do whatever you want, crossflash etc. Once you reinstall a kdz with lgup you should be back to the beginning and can start again.
good luck
AsItLies said:
So honestly I'm confused by where you are or what the situation is. But no matter.
This link is for the Lun4 partitions of sprint a10 backup. It has the rawprogram xml needed to flash it.
My understanding is that should be all you need to get LGUP to work. So flash that with qfil and then go directly to LGUP with the key combo.
Then, in lgup, do whatever you want, crossflash etc. Once you reinstall a kdz with lgup you should be back to the beginning and can start again.
good luck
Click to expand...
Click to collapse
Thanks for the files and information. I just did the flash in QFIL. look what it tells me.
What could be wrong with my cell phone? It no longer wants to enter power on or enter download mode.
The screenshots from 1 to 5 are those of the QFIL flash process.
Then see how is the partition manager. From screenshot 6 to 13.
Do you find any problem?
I still can access Download mode.
Thank you again for your dedication and availability to help me
Hmmm, wasn't sure if that would work or not. That rawprogram xml was created with bkerler edl utilities, I know it can be used to restore with those utilities but thought it would work with qfil, guess not.
seems your only other option would be to flash ea partition manually with qfil.
AsItLies said:
Hmmm, wasn't sure if that would work or not. That rawprogram xml was created with bkerler edl utilities, I know it can be used to restore with those utilities but thought it would work with qfil, guess not.
seems your only other option would be to flash ea partition manually with qfil.
Click to expand...
Click to collapse
ok i'll try it that way.
how can i use bkerler edl utilities to load the rawprogram xml ?
Hi, I also tried this tutorial:https://forum.xda-developers.com/t/tutorial-rescue-from-hard-brick.4351389/.
According to him, since my device is Sprint, I have to flash all partitions. You can successfully do part C. But I haven't been able to do part E yet because I don't have all those partitions.
AsItLies​share me the full firmware backup so I can restore mine, please
CloudStrife97 said:
AsItLies​share me the full firmware backup so I can restore mine, please
Click to expand...
Click to collapse
I don't have the full backup, sorry. Pretty sure if you look though someone has posted a link to it.
Keep in mind though, if you have chip erased your device, restoring a backup will not restore your imei, for that it will cost $ to pay someone with an octoplus box to do it.
AsItLies said:
So honestly I'm confused by where you are or what the situation is. But no matter.
This link is for the Lun4 partitions of sprint a10 backup. It has the rawprogram xml needed to flash it.
My understanding is that should be all you need to get LGUP to work. So flash that with qfil and then go directly to LGUP with the key combo.
Then, in lgup, do whatever you want, crossflash etc. Once you reinstall a kdz with lgup you should be back to the beginning and can start again.
good luck
Click to expand...
Click to collapse
Do you have an AT&T one?
PHANX0M said:
Do you have an AT&T one?
Click to expand...
Click to collapse
no
My device stuck in edl mode it's nothing show no download mode no restart no turn off only edl mode please help

Categories

Resources