Hi guys, please is there someone who knows how to extract .Kdz file then replace the file boot.img inside it then repack it again to have a new .kdz file to be flashed using Lgup? It would be very helpful if you can help me. I would like to try it because as you know LG blocked fastboot command on nougat so i can't flash boot.img file from fastboot. Or my phone got bootloop and there is no way but blocking the 2 big cores. Thank you
Sent from my SM-G965F using XDA Free mobile app
+1
No, it is not possible. Let me rephrase that. You can repack a Nougat KDZ which will be recognized by LG UP, but it won't flash. There is a signature payload in Nogat and later KDZs that is signed with an RSA cert. The public key is in lafd, the private key is locked up in LGs office. Without that SIGN payload, lafd won't flash via normal means.
-- Brian
Related
Good night!
This thread is a "2 questions", really.
I have a D685, know as LG G Pro Lite Dual. I want to try make a custom ROM, but, for now, this model don't have a recovery to flash ROMs, or CWM. It don't have bootloader (wich is locked) or fastboot mode. All it have is a stock recovery, which is nothing but and android opened (the keys do nothing), and a "download mode".
The only ways to flash a ROM into this phone is using LG Mobile Tools (the offline method) in download mode, or official LG Program. With the offline method, we flash a file with a KDZ extension.
I can extract it, it give me a CAB file. When extracted, I have 2 files: a DLL and a BIN file, instead a .DZ or .WDB file. I can't find a program/way/thread to extract the BIN file... anyway to do this?
The intention is get the system.img (or whatever) inside the BIN, cook it, and reflash it. Then, you ask: "How to reflash, if this device don't have a recovery?"
Well, this is my second question! If I can create the KDZ file, maybe I can "integrate" the system.img into the KDZ, and flash using the offline method!
By this way, maybe we can have a recovery and boot images, too... If the BIN file have them, maybe we can cook boot and recovery, too... maybe... All depends what is inside the BIN file, and of course, if we can create or recreate the KDZ and flash it.
Any tips for these questions?
Thanks!
EDIT: we have root, at least. Tried to get boot and recovery with MTK Droid Tools, but the phone don't boot. It gives a security error just after turns on..
Hi everyone,
I have an 10.8 inch wifi only tablet imported from China, non-pro, model CMR-W09C00 which was running firmware B123.
I was playing around trying to convert it to a global firmware and tried to flash it with the same firmware 123 but for CMR-W09C432 using Huawei Firmware Finder.
Turns out this was a pretty bad idea
Now the tablet is not booting and I can't figure out how to recover. Here's what I tried:
1. eRecovery is not working, it downloads the firmware completely and tries to install but fails. It did work fully once before I tried to flash the wrong firmware.
2. Wiping cache and data partition does nothing
3. I have access to fastboot and can unlock/lock the bootloader at will.
4. I have the full-OTA zip file for the original firmware CMR-W09C00B123 and have extracted all the img files contained in update.app
5. I'm trying / hoping to flash images to recover (with bootloader unlocked) but I'm a bit confused at this step.
All the instructions I found in my research mention mostly flashing just boot.img, system.img and recovery.img but I'm missing some of those files from the update.app or I guess they could be named differently. I don't have a boot.img, just a fastboot.img which I'm sure is not the same. I also don't have a recovery.img, just recovery_ramdis, recovery_vbmeta, recovery_vendor, erecovery_ramdis, erecovery_vendo, erecovery_vbmet and erecovery_kerne.
I was able to flash system.img successfully but that didn't help.
Also tried to use the unbrick feature from Huawei Multi-Tool but here again I seem to be missing image files. Multi-Tool says it needs system.img, ramdisk.img, cust.img, ramdisk_recovery.img and userdata.img.
Of those, I think I'm missing cust.img for sure, ramdisk_recovery I might have but it's named differently (recovery_ramdis) and userdata.img I don't think I really need.
I'm attaching a txt file with a list of all the img files I do have in case it can be useful or rings a bell for someone.
Oh yeah, I also tried flashboot update update.zip but it's only giving me this warning:
archive does not contain 'android-info.txt'
error: update package 'update.zip' has no android-info.txt
So...does anyone have any advice or suggestions? Is there a better method to recover that I missed?
Any help is appreciated!
Flash the ramdisk.img to ramdisk and report back please. I have an M3 that is in the same condition as yours, but I am on an extended deployment and won't be able to test this for at least another month :/
fargonaz said:
Flash the ramdisk.img to ramdisk and report back please. I have an M3 that is in the same condition as yours, but I am on an extended deployment and won't be able to test this for at least another month :/
Click to expand...
Click to collapse
Thanks for taking the time to the reply mate, sorry to hear about your M3.
I tried fastboot flash ramdisk ramdisk.img and it said flashed successfully but the device is still not booting. Nothing else seems to have changed either.
Let me know if I misunderstood what you wanted to try or if you have any other ideas.
Cheers
etheberge said:
Hi everyone,
I have an 10.8 inch wifi only tablet imported from China, non-pro, model CMR-W09C00 which was running firmware B123.
I was playing around trying to convert it to a global firmware and tried to flash it with the same firmware 123 but for CMR-W09C432 using Huawei Firmware Finder.
Turns out this was a pretty bad idea
Now the tablet is not booting and I can't figure out how to recover. Here's what I tried:
1. eRecovery is not working, it downloads the firmware completely and tries to install but fails. It did work fully once before I tried to flash the wrong firmware.
2. Wiping cache and data partition does nothing
3. I have access to fastboot and can unlock/lock the bootloader at will.
4. I have the full-OTA zip file for the original firmware CMR-W09C00B123 and have extracted all the img files contained in update.app
5. I'm trying / hoping to flash images to recover (with bootloader unlocked) but I'm a bit confused at this step.
All the instructions I found in my research mention mostly flashing just boot.img, system.img and recovery.img but I'm missing some of those files from the update.app or I guess they could be named differently. I don't have a boot.img, just a fastboot.img which I'm sure is not the same. I also don't have a recovery.img, just recovery_ramdis, recovery_vbmeta, recovery_vendor, erecovery_ramdis, erecovery_vendo, erecovery_vbmet and erecovery_kerne.
I was able to flash system.img successfully but that didn't help.
Also tried to use the unbrick feature from Huawei Multi-Tool but here again I seem to be missing image files. Multi-Tool says it needs system.img, ramdisk.img, cust.img, ramdisk_recovery.img and userdata.img.
Of those, I think I'm missing cust.img for sure, ramdisk_recovery I might have but it's named differently (recovery_ramdis) and userdata.img I don't think I really need.
I'm attaching a txt file with a list of all the img files I do have in case it can be useful or rings a bell for someone.
Oh yeah, I also tried flashboot update update.zip but it's only giving me this warning:
archive does not contain 'android-info.txt'
error: update package 'update.zip' has no android-info.txt
So...does anyone have any advice or suggestions? Is there a better method to recover that I missed?
Any help is appreciated!
Click to expand...
Click to collapse
I think I am in a similar spot. I went from a custom ROM back to stock, but now all attempts at installing full OTAs fail. Did you ever figure this out how to fix it?
Thanks
Hi,
I just got a V10 to play with from my relatives.
It is LG-H961AN which is a 32GB variant for Hong Kong area and has upgraded to nougat already (V30a-HKG-XX)
I want to root it but
1. the bootloader is locked. This version (961AN, not 961N) is not supported by LG's bootloader unlock service.
2. I tried to extract a boot.img from kdz file (downloaded somewhere in internet) in order to have it patched by Magisk Manager app and flash it in adb to root it. However, after converted to CAB from KDZ, no software in my PC (win10 default unzip/7zip/Peazip) can extract/unzip it in order to get .img file. I can't go further. I just wonder LG locked that cab or what.
Any suggestion how to root it or dump a boot.img file?
Thanks in advance.
All fix avilable (no network solved)
Watch it carefully do it step by step as showen in my video you will never brick if you follow my video
All required files are in the video description
This guide Tested on the firmware (20e ,20c,20d) (if you didn't see your firmware don't worry leave a command , I will help you ! )
How to check the frimware:
* Go to Settings - >System -> About phone -> sofware version ( eg: V20e-IND-XX so use 20e rootboot file)
All required files are in the video description
watch it in 720p only 40 mb
subscribe for more lg g8x content !!!
If any issue let me know i will help you with that
I've rooted with Magisk and root seems to be working. I then restored the abl_a back to abl_a and abl_b partition. Now I keep getting system UI crashes and the phone app freezes when I try to make a call.
cyr4n0 said:
I've rooted with Magisk and root seems to be working. I then restored the abl_a back to abl_a and abl_b partition. Now I keep getting system UI crashes and the phone app freezes when I try to make a call.
Click to expand...
Click to collapse
looks like your device is not a 20e firmware (audio not work,cant make a call ,ui crash) i will help you to root just share the boot_a img (stock)
[email protected] said:
looks like your device is not a 20e firmware (audio not work,cant make a call ,ui crash) i will help you to root just share the boot_a img (stock)
Click to expand...
Click to collapse
Hello,
I have the exact same issues. Didn't notice the Indian variant on Magisk in the Root guide, and ended up with an unusable phone.
You say boot_a image stock, do you mean from before the whole process? I unfortunately didn't back up this particular partition..
Boot.zip contains the boot.img file pulled from the kdz of the US G850 20b.I don't know if this is useful, but I got it...
ReadData_.ufs_Lun4_...... is the boot_a file pulled from my phone after I turned it into a buggy mess I also don't know if this helps, but I do need help getting my phone working again if you'd be so kind. This is NOT the boot_b flashed as boot_a like mentioned in the video.
rainbowtuba said:
Hello,
I have the exact same issues. Didn't notice the Indian variant on Magisk in the Root guide, and ended up with an unusable phone.
You say boot_a image stock, do you mean from before the whole process? I unfortunately didn't back up this particular partition..
Boot.zip contains the boot.img file pulled from the kdz of the US G850 20b.I don't know if this is useful, but I got it...
ReadData_.ufs_Lun4_...... is the boot_a file pulled from my phone after I turned it into a buggy mess I also don't know if this helps, but I do need help getting my phone working again if you'd be so kind. This is NOT the boot_b flashed as boot_a like mentioned in the video.
Click to expand...
Click to collapse
The one you provided was not help ,Give me the stock boot_a img (download the whole kdz and extract the boot_a.img)
rainbowtuba said:
Hello,
I have the exact same issues. Didn't notice the Indian variant on Magisk in the Root guide, and ended up with an unusable phone.
You say boot_a image stock, do you mean from before the whole process? I unfortunately didn't back up this particular partition..
Boot.zip contains the boot.img file pulled from the kdz of the US G850 20b.I don't know if this is useful, but I got it...
ReadData_.ufs_Lun4_...... is the boot_a file pulled from my phone after I turned it into a buggy mess I also don't know if this helps, but I do need help getting my phone working again if you'd be so kind. This is NOT the boot_b flashed as boot_a like mentioned in the video.
Click to expand...
Click to collapse
Or you can flash the kdz back (make sure you are using the correct KDz
How do I flash the KDZ? I have tried pushing it with LGUP but it hasn't been successful.
Also, I've extracted the kdz with LG Firmware Extract but I'm not seeing a boot_a.img. The closest thing I see is boot.img_257490
I think I'm stuck now. I tried to use LGUP but now I can't even boot into anything but fastboot. Now it fails the security check and goes into fastboot. Unlocking the bootloader doesn;t work now and it's stuck on locked...
BTW, I renamed the boot.img_257490 and tried to flash it via fastboot but the error was "sending boot_a - too large" so I think this IS the boot_a. Not that it may matter for me at this point lol
rainbowtuba said:
How do I flash the KDZ? I have tried pushing it with LGUP but it hasn't been successful.
Also, I've extracted the kdz with LG Firmware Extract but I'm not seeing a boot_a.img. The closest thing I see is boot.img_257490
I think I'm stuck now. I tried to use LGUP but now I can't even boot into anything but fastboot. Now it fails the security check and goes into fastboot. Unlocking the bootloader doesn;t work now and it's stuck on locked...
BTW, I renamed the boot.img_257490 and tried to flash it via fastboot but the error was "sending boot_a - too large" so I think this IS the boot_a. Not that it may matter for me at this point lol
Click to expand...
Click to collapse
wait ill share you my lg up and kdz extractor.
and are you sure you downloaded the correct one?
[email protected] said:
wait ill share you my lg up and kdz extractor.
and are you sure you downloaded the correct one?
Click to expand...
Click to collapse
Now that I'm trying it again, it's failing to pull it. The DZ seems to pull from the KDZ, but anything from the DZ fails with an incorrect header check error. It's a blank file. I'm sure you noticed that before I did.
rainbowtuba said:
Now that I'm trying it again, it's failing to pull it. The DZ seems to pull from the KDZ, but anything from the DZ fails with an incorrect header check error. It's a blank file. I'm sure you noticed that before I did.
Click to expand...
Click to collapse
KDZ Extractor LG
Download the Zip : http://www.mediafire.com/file/0a6iikrao70ma5s/KDZTools_20200305.7z/file Extract the file zip Copy the Downloaded KDZ into the KDZ Extractor folder Open "OneKeyExtraction.bat" It will Start to extract the file for you The...
forum.xda-developers.com
use this
[email protected] said:
KDZ Extractor LG
Download the Zip : http://www.mediafire.com/file/0a6iikrao70ma5s/KDZTools_20200305.7z/file Extract the file zip Copy the Downloaded KDZ into the KDZ Extractor folder Open "OneKeyExtraction.bat" It will Start to extract the file for you The...
forum.xda-developers.com
use this
Click to expand...
Click to collapse
Thank you, here is the boot_a.img
EDIT: I have potentially good news! I was completely stuck in a boot loop, but using the files from the KDZ (modem_a, modem_b, boot_a,boot_b, abl_a, and abl_b) and pushed them each with fastboot. The device restarted (with sound!) and it is resetting to stock now. We'll see what happens!
rainbowtuba said:
Thank you, here is the boot_a.img
Click to expand...
Click to collapse
How to restore download mode ?
can we root on 20f?
What about 20b
I own a LG G8x Sprint fw model with SW version g850um20f build qkq1.200216.002 with April Security patch. I unlocked the bootloader with this method after I sim unlocked it today. Interestingly I have now a T-mobile splash screen perhaps because I tested the sim unlock with my t-mobile sim? Either way it provisioned all the T-mobile operator software so it got rid of all the Sprint garbage and loaded volte wifi calling etc...I have yet to test all the features but it did it all for me after the factory reset happens when the boot loader unlocks. I did not load the original abl_a abl_b backup files back to the device. Was the patched abl file a US model dump?
Me gustaría saber si la versión 20j de sprint también se puede rootear
Anyone successful unlock the 20b (G8X Us variant)? Having a hard time finding any info on unlocking this version.
20b
Adminislayer said:
Anyone successful unlock the 20b (G8X Us variant)? Having a hard time finding any info on unlocking this version.
Click to expand...
Click to collapse
I did 20j sprint yesterday.
The hardest part was to get into EDL.
Where are you stuck?
BTW, does anyone have the twrp bin for these phones? I can't find a working link. I just want to boot into twrp temporary to do a system image.
..the vbmeta.img and boot_a from the unlocked variant? I tried flashing TWRP kind of half cocked, and yea... Anyhow, if someone has either\or or both of these files, hook a brother up!
Disregard. I was able to unbrick with the dre8t_10_O.05_210713.ops firmware floating around. It wouldnt let me flash via MSMDownloadTool, however I was able to decrypt/extract the ops file with the oppo_decrypt python script, then reflash the vbmeta and vbmeta_system partitions plus boot_a and userdata with the extracted files.
PHEW had me scared for a minute
the.real.p3y0t3 said:
..the vbmeta.img and boot_a from the unlocked variant? I tried flashing TWRP kind of half cocked, and yea... Anyhow, if someone has either\or or both of these files, hook a brother up!
Click to expand...
Click to collapse
For future reference:
For unlocked variant:
Download the latest OTA update from the OnePlus website and you can use any assortment of payload dumpers to obtain all of the raw image files.
My payload dumper of preference is Fastboot Enhanced/Payload Dumper. It can even install the full OTA via fastboot/fastbootd
For T-Mobile and Metro variants I would recommend the T-Mobile MSM tool and update from there.
The download link to "Incremental OTAs" can be scraped from the system logcat at time of download.
I haven't looked much into incremental OTA and how it is setup yet.
Thanks for the heads up. I actually already had the above mentioned OPS file when I bricked my device, I just hadn't been able to extract, then decrypt it. Had to download a obscure bzip2 binary for windows to extract the tar, etc etc.
A seller from ebay sent a t-mobile (2118) that was carrier unlocked, wasn't able to unlock the bootloader. Is there anything I can do?