Hi all.
I followed this guide
Guide LG G8/G8x/v50 Bootloader Unlock and Magisk Root using Firehose
Disclaimer: I am not responsible for any problems from using this guide. Works for G8, G8s, G8x, and v50 Confirmed working on G8 and v50 Requirements: Android 10 QFIL...
forum.xda-developers.com
have been rooted for few months now. Received the OTA notification and did my research on how to apply it. Unfortunately I can't restore factory images in magisk as there is no stock backup found. I read somewhere that You can find the missing file and put it in manually. To do this I need to find and download official firmware file that the phone is running and extract it from there.
mine is here:
LG V500EM | LG V50 ThinQ 5G | Version: V500EM20g_00_0120 | Firmware for Region: EEE from UNITED KINGDOM - Lg-firmwares.com
LG V500EM Download the latest version of firmware | OS Version: Android 10 Q | Firmware version: V500EM20g_00_0120 | EEE - Fan club LG-firmwares
lg-firmwares.com
Now this is where I start facing issues. I got the right kdz file. Extracted the dz file. But by no means I cant get boot.img out of it.
Any help would be great and much appreciated.
What prevents you from extracting the image
It just won't work.
I found a guide and used
LG Firmware Extract Tool v1.2.6.1The file is there but cant be extracted
this the output of the program:
Progress extractDZFlle Done !!
Complete on extract DZ partition files
Exception on extract partition file Ionic.Zlib.ZlibException: Bad state (incorrect header check)
at Ionic.Zlib.InflateManager.Inflate(FlushType flush)
at Ionic.Zlib.ZlibCodec.Inflate(FlushType flush)
at Ionic.Zlib.ZlibBaseStream.finish()
at Ionic.Zlib.ZlibBaseStream.Close()
at Ionic.Zlib.ZlibStream.Dispose(Boolean disposing)
at System.IO.Stream.Close()
at WindowsLGFramwareExtract.Form1.DZExtractBackprocess.extractDZFlle(ArrayList contents) in L:\Working_PROJECT\WindowsLGFramwareExtract\WindowsLGFirmwareExtract\Form1.cs:line 464
boot.img_118538
byte read position 4
header 32-96-18-74
byte read position 0
DZ file C:\Users\dirt\Desktop\LG_Firmware_Extract_v1.2.6.1\LG_Firmware_Extract_v1.2.6.1\V50020m00EEOGBOP0120.dz
Could the program be outdated and LG have changed their way of packing their firmware? Is there any other way to get it out?
The same thing happens to me when I try to do this. All I get are some vendor .img files and the same 'exception error'. The kdz I used is like 4.2gb, the dz file output is 155mb.
I think the firmware extract program is too dated for these phones, it was used for the G2. This sucks
Hmm maybe the file is corrupt, try finding a new source or downloading it.
Actually the KDZ file is not corrupt but the software you are using to extract does not work with new LG firmwares files (since they use version 3 compression). You need to use Linux for extraction.
I could help you in getting the boot.img if you tell me which specific firmware you are seeking from.
Royaltiger said:
Actually the KDZ file is not corrupt but the software you are using to extract does not work with new LG firmwares files (since they use version 3 compression). You need to use Linux for extraction.
I could help you in getting the boot.img if you tell me which specific firmware you are seeking from.
Click to expand...
Click to collapse
EDIT: My issue was that i was running .bat and storing file on newtwork HD. I will leave this post up incase someone else runs into the issue.
There are really no windows programs to successfully extract the DZ from KDZ ??
I've been working on this issue for 3 days and can't get a boot image and other necessary files to come out of the DZ. Only way i read about that was successful was using OneKeyExtraction.bat (sourabh7625) but program cannot find the KDZ file like shown below. I'm working with LG G710VM on Win10 can only access EDL at this point.
{
"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"
}
Related
Droid-IMG v1.0
{
"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"
}
I'm new to the Android platform, only getting an Android Phone less than a week ago. I am however a developer and from reading up on Android and ROM's I noticed that there was little to nothing on the .IMG format, especially tools for windows.
With that in mind I started to develop a command line based tool to extract and compress .IMG files. It does rely on other tools to do this (hence the Tools folder included). My utility searches for the GZip Signature in the .IMG file and dumps the data. It then extracts it into a folder and from here you can modify the files and then re-compress them back into an .IMG file using my tool.
What I have found is some .IMG files that contain links/shortcuts will become corrupt upon extraction since they are only supported by the linux operating system.
Anyway, my program should be self explanatory when you run it. The screenshot above also shows the commands and parameters that should be used.
NOTE : [Base IMG] is your original unmodified .IMG File and [New IMG] is the file name of the .IMG file that will be created. Also, ignore the function not implemented errors.
Reserved.
P.S : Guess nobody knows what .IMG files are then...
Nice man! Thank you.
TheUnkn0wn said:
Droid-IMG v1.0
I'm new to the Android platform, only getting an Android Phone less than a week ago. I am however a developer and from reading up on Android and ROM's I noticed that there was little to nothing on the .IMG format, especially tools for windows.
With that in mind I started to develop a command line based tool to extract and compress .IMG files. It does rely on other tools to do this (hence the Tools folder included). My utility searches for the GZip Signature in the .IMG file and dumps the data. It then extracts it into a folder and from here you can modify the files and then re-compress them back into an .IMG file using my tool.
What I have found is some .IMG files that contain links/shortcuts will become corrupt upon extraction since they are only supported by the linux operating system.
Anyway, my program should be self explanatory when you run it. The screenshot above also shows the commands and parameters that should be used.
NOTE : [Base IMG] is your original unmodified .IMG File and [New IMG] is the file name of the .IMG file that will be created. Also, ignore the function not implemented errors.
Click to expand...
Click to collapse
These are some useful little tools, Considering lack of them for Windows users. Maybe nice one day to Polish it up with a nice GUI to make it easy for less experienced people.
But Good job I'll be using these.
Unpacking tool nb0 firmware files used my Infocus/Nokia (made by FIH mobile)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you want to repack nb0 image:
edit files "list" of unpacked nb0 image, remove .md5 file from list.
Not guarantee moded packed nb0 will work - OST may give an error. Some images work some require md5. Depending from mlf content.
05.04.18 v3.4
-fixed long filenames in nokia firmware
-added repacking (may not working for new images for OST 3.1.4 with md5 check permanent)
27.01.18 v3
-added unpacking for nokia firmwares
-supporting images up to 6 gb
Thank you for the tool. Took a lot of searching to find this topic for v2.
Unfortunately Nokia has changed something in the .nb0 format and the extracting fails mid process.
Can you take a look with nokia 8 firmware file? NB1-308B-0-00WW-B01_2 Nokia 8.rar from https://forum.xda-developers.com/no...ia-8-official-firmware-links-updated-t3678487
@heineken78 why it keeps on crashing with arithmetic problems?
wolfyapl said:
@heineken78 why it keeps on crashing with arithmetic problems?
Click to expand...
Click to collapse
tool is updated
Hello.
Tried using it, but the button for selecting file to pack back is not working (cannot click on it).
Tried with v2, but receive that arithmetic error.
Can you help me?
ktutza2006 said:
Hello.
Tried using it, but the button for selecting file to pack back is not working (cannot click on it).
Tried with v2, but receive that arithmetic error.
Can you help me?
Click to expand...
Click to collapse
Packing back is now in development. OST is using special table now for different files, so not 100% packing is ok.
But you dont need it! You can flash in OST by selecting of unpacked .mlf file
Yes, thanks, tried that, working.
I need now to figure a way to change the system.img, cause the md5 check is ruining that for me.
The version of firmware i have for okia 6 ta-1003 have no .mlf file, and if i try to take just the system.img file from it and put in ta-1000 extracted firmware(same hardware, different android customisation, 1000 is for china) i get a md5 error.
If i manually update the size and md5 checksum in md5 file, also crashed.
A bit offtopic here, but anyway, thanks for the tool, is very helpfull
@heineken78, Still have arthimetric error, and the password for emmc zip file is WLBGFIH123 if you care to add. Thank you!
my computer freezes in unpacking process, what to do?
EDIT: Nvm, i unpacked it successfully, tnx for tool
SkaboXD said:
my computer freezes in unpacking process, what to do?
EDIT: Nvm, i unpacked it successfully, tnx for tool
Click to expand...
Click to collapse
updated
can you please look if problem with unpacking this nb0 is with your tool or with rom file?
in unpack progress a get error about out of memory... more info here
thanks
SkaboXD said:
my computer freezes in unpacking process, what to do?
EDIT: Nvm, i unpacked it successfully, tnx for tool
Click to expand...
Click to collapse
I'm having the same issue, how did you fix it?
Loku_kika said:
I'm having the same issue, how did you fix it?
Click to expand...
Click to collapse
just wait for it to flash, it took around 5 minutes for me, when you see that is not responding just click on app and it will update unpacking status.
I found a scatter file after extracting. can I simply extract .nb0 file and flash with sp flash tools or there is something additional needed before flashing the extracted content through sp flash tools?
@heineken,
can you check nokia 3.1 nb0 file, looks like they changed something, again ...
ES2-042E-0-00WW-B02
b.r.
Whenever I try to unpack the NB0 (Nokia 7 plus TA-1046) file using the NB0 tool v3.4, it always gives me an error (see screenshot) and if I click on "Continue", it gets stuck in halfway.
@heineken I am trying to unpack the Nokia 2.1 firmware (nb0) and the tool is only able to read the first 2 files. Do you have any idea and can we expect an update to the tool?
@singhnsk
for E2M-021Q-0-00WW-B02.nb0 you can use nb0-utils.exe or nb0-utils.jar
regards
Now available on neon through qtapp.
Qtapp which is part of Neon can be downloaded from Neon Updater latest
Sometimes you must install vccred15 from microsoft
kenkitt said:
Now available on neon through qtapp.
Qtapp which is part of Neon can be downloaded from Neon Updater latest
Sometimes you must install vccred15 from microsoft
Click to expand...
Click to collapse
So it would seem now that a username and password is required. How do i get pass this if possible without sending an email
Never mind, i saw the application qtapp installed as well. Thanks.
Hello, I need your help as the title says, when flashing a kdz or tot ... it reaches 9% and I throw that error.
What is the reason for this error?
Rootie the cell a while ago and revert it back to the original firmware, lg up did not recognize the device, the typical "unknown deviced". What I did is install the LG Bridge and do it from there .. Error.
It flashed correctly but enter bootloop .. I had to heat the processor and I could make it work.
Lg up returned to recognize the model, perfect.
But I can not flash anything anymore .. if you could explain the reason for that error, why happened?
Is it the root?
Thank you very much and I await your answers and help.
PS: You can give the subject as solved, I already managed to solve this problem .. thank you anyway
{
"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"
}
how did you solved?
LG F500S 0x2000 Error Fix
If you are using LGUP utility for flashing .kdz ROM and decided to upgrade to Marshmallow or Nougat just extract your .kdz file by this tool WindowsLGFirmwareExtract-1.2.6.1-Release and then select the .dll file from the extracted files. Now rename this .dll file to LGUP_8994 and copy this .dll file into the LGUP model/8994 directory and viola!!!
IT WILL FLASH AND REBOOT!
justsomedude555 said:
how did you solved?
Click to expand...
Click to collapse
The only thing I did was change my computer
androhead said:
If you are using LGUP utility for flashing .kdz ROM and decided to upgrade to Marshmallow or Nougat just extract your .kdz file by this tool WindowsLGFirmwareExtract-1.2.6.1-Release and then select the .dll file from the extracted files. Now rename this .dll file to LGUP_8994 and copy this .dll file into the LGUP model/8994 directory and viola!!!
IT WILL FLASH AND REBOOT!
Click to expand...
Click to collapse
I tried one of the many options and the only one that turned out to me was changing computers.
androhead said:
If you are using LGUP utility for flashing .kdz ROM and decided to upgrade to Marshmallow or Nougat just extract your .kdz file by this tool WindowsLGFirmwareExtract-1.2.6.1-Release and then select the .dll file from the extracted files. Now rename this .dll file to LGUP_8994 and copy this .dll file into the LGUP model/8994 directory and viola!!!
IT WILL FLASH AND REBOOT!
Click to expand...
Click to collapse
Thanks for the tip. It worked on h815:good:
Delete old DLL from model folder in LGUP root folder
Install 0.0.4.0 dll for lg g4 ( 8994 )
Put in (model folder) in LGUP root folder
And this FIRMWARE H81520p_00_0314.kdz ( RECOMMENDED Download from LGFIRMWARES ) ( Actually it does not matter where you download it from )
H81520p_00_0314.kdz have some error in code (Actually it does not matter where you download it from)
this error fixing lg g4 IDK how but it start working
after that your phone refurbished ( wipe his data )
Now you can continue experimenting on this phone
DONT TRY it on OTHER MODELS!!!!!!!!!
this instruction for H815 ( H815EU, H815TR, H815L, H815P, too )
Hi,
I have Cubot KingKong Mini 2 (Android 10 smartphone) and the new version of the firmware is available on the official website of the manufacturer: https://cubot.net/Support/id/60/cid/16.html#hh
{
"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"
}
It contains "minor bug fixes". They also gave instructions on how to update firmware: via PC using SP Flash Tool.
Does the "standard" update from Android app settings (System > Advanced > System update) also include the same bug-fixes?
If so, then I guess that I don't have to do anything via PC & SP Flash Tool, I can just update from my phone (from Android system update) and it will include the same fixes, right?
Thanks in advance,
Sennee
Sennee said:
Hi,
I have Cubot KingKong Mini 2 (Android 10 smartphone) and the new version of the firmware is available on the official website of the manufacturer: https://cubot.net/Support/id/60/cid/16.html#hh
View attachment 5306259
It contains "minor bug fixes". They also gave instructions on how to update firmware: via PC using SP Flash Tool.
Does the "standard" update from Android app settings (System > Advanced > System update) also include the same bug-fixes?
If so, then I guess that I don't have to do anything via PC & SP Flash Tool, I can just update from my phone (from Android system update) and it will include the same fixes, right?
Thanks in advance,
Sennee
Click to expand...
Click to collapse
The .rar Archive on the Official website is a full Read-back/Backup of the Nand (including the Scatter file for the partitions), it is usually used when/if:
The OTA (Over The Air) update through system fails, rendering your device soft bricked (in a Bootloop).
For documentation's sake.
The OTA servers are no longer available. (Update servers cost money to host)
My advice would be to update through system update first, here's why:
The update could be an even newer Security patch/version than the one on the website.
Updating through recovery mode (what an OTA update essentially is) has the added benefit of verifying the Update file for corruption first and will abort if it is found as such.
The Provided SP flash tool ROM is a Factory backup without the imei, sometimes forcing you to re-write it to each individual sim slot manually if you select all partitions for flashing. (a reoccurring trap that beginners fall into)
Only use the SP flash tool method if you're stuck after the system update.
Thanks @Slim K !
I didn't know that on Android "firmware" is basically OS, I thought that they are completely separate things that can be updated in a separate (different) ways. I thought that through "System update" (OTA) you can only update software/OS, not firmware (and that I'll have to update firmware using their instructions (via PC using SP Flash Tool)).
need more Cubot forums
So been playing with GSIs.. though none are amazing.. so thinking about porting the Tab S7 to the S6 using the same method.. (Just flashing the system.img file using the Treble method).
I have downloaded the latest S7 ROM
SM-T870_XSA_T870XXU2DWB2
Extracted the AP, BL, CSC & HOME tar files.
Then extacted the super.img
Converted the super.img to raw and extracted that too.
I was expecting to see a 1,2,3 4.ext files which should translate to vendor.img, boot.img, system.img etc.
Though instead i got the full file structure. (pic below).. within this structure is a System folder.. though not sure how i get to a flashable system.img file?
Little help?
Super.img Extract:
{
"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"
}
And within that folder is the System Folder:
btw here the link to the ROM https://samfw.com/firmware/SM-T870/XSA/T870XXU2DWB2
Wish I could help since I would love one ui 5 on this one, I can only make a suggestion though, hopefully not stupid.
Take a look at the T866N firmware/rom, the device is almost identical except from SD855 vs the + variant and the inclusion of 5G, even if the lte/4g/5g modem is broken I think it would be worth it.
Also I'll mention some guy that did this on S21 to S20 successfully @LeeXDA18
Edit: My bad, thought the 5G variant got One UI 5 for some reason, still maybe lee has some clue on this.
its very strange.. i have just extracted the .tar file from the A12 S6 Firmware and i get what i expected..
Looks like the S7 uses a new method of firmware deployment..
I'll give it a try too, for the meanwhile hopefully this guy here has some insight @ShaDisNX255
no one can help on how to create a System.img from an Android 13 ROM for the Tab s7, s8 or s9?]
Just tried the M-X800_EUX_X800XXU3BWC1_f ROM.. though this one despite converts to RAW without issue. I then cannot extract the RAW file.. i am amazed that each of these Firmware's has a different structure!
just tried the S6 Lite ROM too.
SM-P610_XSA_P610XXU2FWC4_f
That RAW extracts without issue.
Though once again i am left with a full folder structure.. how do i get this structure into a flashable System.img?
so i extracted the super.img as above.. and from what i can see it's the same folder structure as a system.img..
so i have tried to flash it within TWRP to the System partition leaving other partitions intact. (treble method).
though now getting an error "Size of image is larger than the target device"
S6 AP is 6.9GB
S7 AP is 7.9GB
so am back to needing to be able to create a new system.img file.. looks like it may need a big debloat.. time to build a linux host..
I dont know if we would be able to shave 1gb of debloat.. this might be a lost cause without repartitioning the System partition on the device.. i dont have any experience with that..
the saga continues..
if anyone wants to play around with the super.img/system.img you can find the link below.
it's untouched from samsung's AP_T870XXU2DWB2_T870XXU2DWB2_MQB62030429_REV00_user_low_ship_MULTI_CERT_meta_OS13.tar.md5 file.
It needs to be extracted debloated and then compressed back into a system.img (in linux).
Or our device needs it's System Partition extended so it can be flashed as is..
easyupload.io
easyupload.io
easyupload.io
Link above.
No one able to help with this project?
would like to but im not able to help for now