Develop Bugs

[How to] Rom cooking

Original post:
Hello,
I am new to android but not to linux. I used to tweak my winmo phone rom.
I have backed up my device with nandroid. I just need some explanations:
- why isn't the radio extracted?
- how can I "extract" does .img files to modify and then rebuild them?
I found some informations of what the .img files contain here: ROM Partitions it should be the same for Hero
I have found some informations on how to push updates to the rom by looking at modaco updates. It seems quite simple to delete/copy files on the hero rom using an update-sript file. I am however curious about the RSA cert and if some files need to be signed.
Any information welcomed.
Regards
Click to expand...
Click to collapse
How to
Extract NAND image files
To extract .img files, I have found unyaffs from http://code.google.com/p/unyaffs/ I have compiled it under ubuntu 64 (attached). Unyaffs works on system.img but on no other .img file
To extract boot.img use attached extract-kernel.pl and extract-ramdisk.pl
# extract-kernel.pl boot.img
# extract-ramdisk.pl boot.img
Should work for recovery.img but haven't tried as custom recovery images on the forum are great.
Rebuild system.img
Seems you just need "to loopback mount an image on your linux box and format it with YAFFS".
But it is useless as because Hero's SPL does not allow flashing system.img directly. You should use an update.zip package for that. (read below)
Rebuild boot.img
After extracting your boot.img using attached extract-*.pl and tweaking it, in same folder run:
# mkbootfs boot.img-ramdisk | gzip > ramdisk-boot
# mkbootimg --kernel boot.img-kernel --ramdisk ramdisk-boot --cmdline "no_console_suspend=1 console=null" -o newBoot.img --base 0x19200000
Creating an update.zip package
Creating an update.zip package is quite easy in fact. For example, to add a (valid) test.apk package to your rom:
- create an empty folder <workdir>
- create folder structure for test.apk (<workdir>/system/app) and copy the test.apk
- create folder structure for update-script (<workdir>/META-INF/com/google/android)
- edit <workdir>/META-INF/com/google/android/update-script
- put in it:
Code:
show_progress 0.1 0
copy_dir PACKAGE:system SYSTEM:
set_perm_recursive 0 0 0755 0644 SYSTEM:app
show_progress 0.1 10
- compress the <workdir> content to zip (not the <workdir> folder itself)
Now you are going to sign the zip file. Download attached testsign.zip and copy it in your <SDK>/tools folder. Extract it here. It should create a sign subfolder with a testsign.jar file in it.
Then, from <workdir> folder, do:
java -classpath <SDK>/tools/sign/testsign.jar" testsign file.zip file-signed.zip
Ok, now your zip file is ready to be deployed using cyanogen recovery image.
To find more command to use in update-script, look at other's.
Modify .apk package
Seems it is easy to uncompress an .apk package (zip) an to modify files in it and then compress it. But after all: you must sign it like update.zip packages.
ODEX files
- What are those Odex files? Answer.
- How to get rid of them?
Odex files depend on framework they are made for. To deodex an odex file use that how to
Then you may create a classes.dex file by executing the smali program on the "out" folder. You then rename it to classes.dex and add it to the .apk.
- How to create them?
Use dexopt-wrapper on device.
Porting an other device's rom
Well, that part is easy
- extract the system.img
- extract boot.img
- replace boot.img-kernel with the one from your stock Hero rom one.
- rebuild boot.img
- build update.zip package (look someone's hero custom rom to see how to do it)
- sign and flash
It should run place and make calls but probably won't have Wifi, BT, trackball support. If you make those work: tell me, but I think we should wait to be able to compile a 2.6.29 kernel to have those.
Tools
Androsign script (linux)
I wrote that androsign script to quick sign zip files. Just put it in your <SDK>/tools folder, then chmod +x. If you have put the tools folder in your PATH, you can call it directly like this:
androsign /dev/folder1/folder2/update.zip (or any zip/apk file)
It will output an update-signed.zip (or app-signed.apk etc) in the same folder than original file was in.
Notes
Note1: thanks
Thanks to every guy that helped me found all that.
Note1: sharing
I searched for hours, so I am more than happy to share it to save someone's time. I am just disappointed than some people here do not have that spirit: I could have use those hours for development instead of research...
Note3: corrections
So, if you found anything incorrect, would like to supply more informations or want to correct my bad english: just PM me.
To find
- how to dump radio from device
- how to build a custom hero kernel (waiting for HTC sources)
To come
How to prepare your own kitchen and useful scripts (linux)

gecka said:
I am new to android but not to linux.
Click to expand...
Click to collapse
Same here. I do lots of tweeking on my linux machine, so i know quite a lot of linux. If there would be anyone to answer those questions by gecka, I might start tweeking the rom (maybe someday cook one up)
Best regards

Hello,
First post edited, but still some ignorances... Please share if you know anything.
Best regards

unpack and pack boot.img and recovery.img
First you need utilities such as mkbootfs and mkbootimg. maybe you can find them online (i can upload them later compiled for linux x86-64) but i suggest you download android source (http://source.android.com) and do a generic make. In this way you have these and other utilities(tools to pack system.img too, but if you haven't an engineering bootloader you can't flash it directly) in /out/host/... (it's better if you add this in your PATH)
To unpack and pack boot and recovery, read here:
http://forum.xda-developers.com/showthread.php?t=443994
or here:
http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
...or...
(I have attached extract-kernel and extract-ramdisk scripts from JF build environment) :
to unpack (boot.img or recovery.img, i'm writing the commands with boot.img):
Code:
extract-kernel boot.img
extract-ramdisk boot.img
at this point you have
boot.img-kernel
boot.img-ramdisk
to repack (boot.img or recovery.img):
For hero you need to specify the base address because it's different (0x19200000). For more information: http://forum.xda-developers.com/showthread.php?t=541522.
Code:
mkbootfs boot.img-ramdisk | gzip > ramdisk-boot
mkbootimg --kernel boot.img-kernel --ramdisk ramdisk-boot --cmdline "no_console_suspend=1 console=null" -o newBoot.img --base 0x19200000
Useful resources for android modding are the dream forums (most of the concepts/hacks works for hero too):
http://forum.xda-developers.com/forumdisplay.php?f=448
(informative thread here: http://forum.xda-developers.com/showthread.php?t=519523)
note: mkbootimg with --base support is in donut and master (or find the patch on gerrit and apply it to cupcake)

First of all, the reason you cant unyaffs anything other than system.img is because they aren't YAFFS images. boot/recovery is kernel+initrd like in any normal linux bootimage scenario (see more below).
Tofind
- how to dump radio from device
Click to expand...
Click to collapse
Haven't gotten into that myself yet, but I know modaco posted an update.zip with radio image included on this very forum. Look for it.
- how to extract NAND images other than system.img
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=443994
- rebuild NAND images such as system.img
Click to expand...
Click to collapse
This isn't hard, just loopback mount an image on your linux box and format it with YAFFS.

Building a custom kernel and recovery binary
HTC hasn't yet released the changes they have made to the hero/dream/magic kernels, 32A board, so you can't just compile a kernel from the AOSP. I haven't tried it yet but this patch might work on hero too:
http://forum.xda-developers.com/showthread.php?t=548061
EDIT: HTC Sources for dream and magic at http://developer.htc.com
For building a custom recovery, it's better if you use cyanogen's recovery code, found in his git : github.com/cyanogen, because it already has menus for nandroid and other tools, but you can use the recovery code from AOSP too (cyanogen's one is a patched version with a lot more features, http://forum.xda-developers.com/showthread.php?t=523558). To make a custom recovery you need to change the recovery binary (because the press event of the hero trackball has a different keycode, 191), the kernel and the init scripts. Actually i don't remember what else I've changed to make cm's recovery working with hero (the recovery that we are actually using here), I'm at work now, but i'll check later and post more details, or you can just unpack the recovery and see the changes .

First post updated.

Nandroid only backs up the partitions in the main storage nand, but radio and spl are flashed to the radio's own nand flash. Whether it's possible to dump it or not I don't know, but honestly, I don't see why you'd want to. Radio images are available through RUU's and I don't think editing would be an easy task

jubeh said:
Nandroid only backs up the partitions in the main storage nand, but radio and spl are flashed to the radio's own nand flash. Whether it's possible to dump it or not I don't know, but honestly, I don't see why you'd want to. Radio images are available through RUU's and I don't think editing would be an easy task
Click to expand...
Click to collapse
Sometimes, new radio images appear on new phones. That is why I am looking on a way to extract it.

very useful thread.

Very nice tutorial, thank you!

could you please specify a bit more on how to clone from android's git and then build the mkbootimg and mkbootfs (just make, right)? I tried and I keep getting a "fatal:server dumped connection" error

Are we able to modify an official ROM (also for hero). Which shows up in RUU as INFOsignature checking... failed. Am I able to change the kernel and make it work?

jubeh said:
could you please specify a bit more on how to clone from android's git and then build the mkbootimg and mkbootfs (just make, right)? I tried and I keep getting a "fatal:server dumped connection" error
Click to expand...
Click to collapse
What command do you use?
In fact i won't be able to explain you better than that page: http://source.android.com/download
Following that how to, you'll be able to sync an android branch You can learn more about git, branches and more here (Repo and Git resources)
The sync is long (2.9Go). Then, to build mkbootimg and mkbootfs, you should do a generic build of android going to source folder and issuing the 'make' command.
All that will be part of my upcoming "How to prepare your own kitchen and useful scripts".
awsy44 said:
Are we able to modify an official ROM (also for hero). Which shows up in RUU as INFOsignature checking... failed. Am I able to change the kernel and make it work?
Click to expand...
Click to collapse
Well, to grep the system from a windows RUU exe file you should launch it and then look in your user temporary folder for a rom.zip file in a {uid} subfolder. It contains the system and boot img files.
You then need to make an update.zip package from them. Have a look to someone's hero custom rom and to it's update-script to see how it is achieved. My 'How to' gives you all you need to understand update.zip packages and to extract system.img.
If you are porting a Hero rom, no need to change the kernel.
Regards

Well, to grep the system from a windows RUU exe file you should launch it and then look in your user temporary folder for a rom.zip file in a {uid} subfolder. It contains the system and boot img files.
You then need to make an update.zip package from them. Have a look to someone's hero custom rom and to it's update-script to see how it is achieved. My 'How to' gives you all you need to understand update.zip packages and to extract system.img.
If you are porting a Hero rom, no need to change the kernel.
Regards
Click to expand...
Click to collapse
Thanks so much for this amazing information, however how do i stop getting hit with the infosignature failed error? is that the kernel or the hboot? it says 12 signature verify error.

Oh, I do have the source and I am running my own donut build on my dream with some of my spice, but the problem I was having was cloning that exact project (mkbootimg) from android.git.kernel.org using git, but when I read what you said, I remembered that when you make the build, it also compiles several tools and i overlooked checking the out folder for it, kind of dumb on my part since I had already pulled the fastboot tool from that build and added it to my own bin, i guess mkbootimg and mkbootfs should be there too, right?

i tried running androsign and got this error
Code:
[email protected]:~/android/dev/sdk/tools$ ./androsign META-INF.zip
Exception in thread "main" java.lang.NoClassDefFoundError: testsign
Failed!
[email protected]:~/android/dev/sdk/tools$

if i use a ROM of one device on an other different device, I think I must build a kernel on my own, is that correct?
but what config should I use? a config from my current running ROM? then I think I must make it suitable for new ROM, what options should I care about?
for example, if I want to run a AOSP 2.01 ROM ( system.img) on a Magic 32A device with SPL 1.76, and now I am running a SenseUI ROM which kernel is 2.6.27, I think I should build a 2.6.29 kernel from the git tree, and ensure it will work with camera/bt/wifi/trackball of my device properly first .
how can I make this step successful?
other hand, the dynamic lib files(.so) with the system.img can be incorrect. so, I may need to build them too for pairing with the kernel I built in previous step. I think applications will work properly because they only care about if the interfaces of kernel and lib is correct. for that, also there some config job (like build.prop, etc) to do, is there a list of all of these jobs? and what values can I refer to? the original ROM (Magic 32A SPL 1.76 working ROM here) ?
am I right? what should i do and what are in those steps? are there some doucments I can read from?

Thanks for the good summary. Just one question, where did testsign.jar come from? I'd like to get the source. Thanks!

JackZero said:
Thanks for the good summary. Just one question, where did testsign.jar come from? I'd like to get the source. Thanks!
Click to expand...
Click to collapse
Read this !
http://www.androiddevelopment.org/tag/apk/
;-)

[TOOLS] Command file install/check/repair

Hi!
I had several different files to automate and I decided to collect them into one.
I added the file to the message. The archive contains the latest version of Android SDK Tools pulled adb and fastboot and the batch file for automating the following tasks:
1) Flash stock firmware via Fastboot
2) Flash stock firmware via Fastboot with clearing the cache and user data
3) Flash custom recovery TWRP via Fastboot
4) Check /data partitions for errors
5) Check /data partitions for errors whis auto repair
6) Format /data partitions with fast check for bad blocks
7) Format /data partitions with full check for bad blocks
8) Full clear /data partitions (fill zero)
I created this file to not have to enter the commands manually. This archive should be unpacked in the root of drive C. Folder was adb-t.
In this folder, copy the file of custom recovery for your tablet model and its version of the Android, rename it to twrp.blob. And also copy to this folder the blob file of your stock firmware.
Then run the file Many_Task_en.cmd (or Many_Task_ru.cmd for Russian).
I hope that it will be useful to someone.

Wow, thanks! I thing it will be very useful in the future!

Added in the Index for TF300
Good job

I found a small error - incorrectly pasted from the clipboard. File replaced.

Updated. Now all the files in the archive are from the Android SDK Platform-tools 18.0.1.
Added a new menu item.

Nice Job! Thanks!
BrateloSlava said:
Updated. Now all the files in the archive are from the Android SDK Platform-tools 18.0.1.
Added a new menu item.
Click to expand...
Click to collapse
Just used this to successfully update TWRP from 2.5.0.0 to 2.6.0.0 on the 4.1.1 JB bootloader via fastboot usb.
Not bothering with the 4.2.2 variants now that 4.3 is pending (and because the hdmi out doesn't work properly on any 4.2.2 ROM, including stock).

TWRP 2.7 boot.img?

Hi,
got my Z1C yesterday and running CM11 with CWM now.
On my DesireS i used TWRP and so i would like to replace CWM with TWRP, but i can't find a boot.img to flash?
Is there only the dualrecovery solution or i'm to blind to find the img?
Thanks,
Thomas

Ok, guess i got it: replaced CWM in the boot.img of CM11 with TWRP from dualrecovery via mkbootimg tool and reflashed it with fastboot.

LazyT said:
Ok, guess i got it: replaced CWM in the boot.img of CM11 with TWRP from dualrecovery via mkbootimg tool and reflashed it with fastboot.
Click to expand...
Click to collapse
Can you do the same thing with Philz Recovery from dualrecovery and share it here please?

Don't know if it's allowed to post the img here?
I made a little script so you can do it yourself on linux. On 64bit ia32-libs are required to run the tools.
Just download and put cm-11-<version>-amami.zip and Z1C*lockeddualrecovery<version>.installer.zip to the "org" directory, run the script and press t for twrp or p for philz to generate "boot.img".
In the "new" directory should now be a "boot.img" with the selected recovery.
Try it first with "fastboot boot boot.img" before flashing!

i'm looking inside your .sh file, but i'm not so good at scripting. can this be used for non-CM roms, assuming I rename the .zip file?
EDIT: tried it and it failed. i extracted the kernel.sin from a TFT file and then renamed to boot.img, then packed the new boot.img into a zip. the script fails on the "7. unpacking boot.img..." step :'-(

twrp cm11
LazyT said:
Don't know if it's allowed to post the img here?
I made a little script so you can do it yourself on linux. On 64bit ia32-libs are required to run the tools.
Just download and put cm-11-<version>-amami.zip and Z1C*lockeddualrecovery<version>.installer.zip to the "org" directory, run the script and press t for twrp or p for philz to generate "boot.img".
In the "new" directory should now be a "boot.img" with the selected recovery.
Try it first with "fastboot boot boot.img" before flashing!
Click to expand...
Click to collapse
here my terminal output;
select recovery: [t]wrp or [p]hilz - TWRP
1. checking for unzip... done ("/usr/bin/unzip")
2. checking for lzma... done ("/usr/bin/lzma")
3. checking for cm11 rom zip... done ("cm-11-20140708-SNAPSHOT-M8-amami.zip")
4. checking for recovery zip... done ("Z1C-lockeddualrecovery2.7.143-BETA.installer.zip")
5. extracting boot.img... done
6. extracting recovery... done
7. unpacking boot.img... done
8. repacking boot.img... fail
[email protected]:~/Downloads/create-boot-v1.1$
command used: [email protected]:~/Downloads/create-boot-v1.1$ sudo bash create-bootimg.sh

Could you also post the output of the "error.log"?

LazyT said:
Could you also post the output of the "error.log"?
Click to expand...
Click to collapse
where i find it, found only Syslog ?
sorry I'm stupid, here it is:
/home/chris/Downloads/create-boot-v1.1/mkbootimg_dtb: error while loading shared libraries: libstdc++.so.6: cannot open shared object file: No such file or directory
I'm using ubuntu gnome 14.04

In the same directory where the script is.

If you have 64bit you need to install ia32-libs.

LazyT said:
If you have 64bit you need to install ia32-libs.
Click to expand...
Click to collapse
seems the problem is here: the ia32-libs package is not available in the Ubuntu 13.10 and 14.04 repositories.

Yes, sorry. It was changed:
Package ia32-libs is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
However the following packages replace it:
lib32z1 lib32ncurses5 lib32bz2-1.0
Click to expand...
Click to collapse
Maybe it's the same on Ubuntu...

LazyT said:
Yes, sorry. It was changed:
Maybe it's the same on Ubuntu...
Click to expand...
Click to collapse
will search these packages.
available: lib32z1 lib32ncurses5 lib32bz2-1.0 will install
---------- Post added at 10:58 AM ---------- Previous post was at 10:42 AM ----------
paulle said:
will search these packages.
available: lib32z1 lib32ncurses5 lib32bz2-1.0 will install
Click to expand...
Click to collapse
with the new files installed I get the error log: /home/chris/Downloads/create-boot-v1.1/mkbootimg_dtb: error while loading shared libraries: libstdc++.so.6: cannot open shared object file: No such file or directory
Installed all from new, rebooted PC, but... the same as before. Step 8 (repacking bootimg) failed.

twrp cm11
LazyT said:
Yes, sorry. It was changed:
Maybe it's the same on Ubuntu...
Click to expand...
Click to collapse
What distribution you are using?

paulle said:
What distribution you are using?
Click to expand...
Click to collapse
Linux Mint Debian Edition.
PM me your mail address and i send you the script which runs on your phone. You can write german, I'm from Leipzig...

LazyT said:
Linux Mint Debian Edition.
PM me your mail address and i send you the script which runs on your phone. You can write german, I'm from Leipzig...
Click to expand...
Click to collapse
OK PMed you. Tomorrow or Thursday I will try it. Thank you

does this work on lollipop?

amadib said:
does this work on lollipop?
Click to expand...
Click to collapse
I've changed the script for cm12 and it runs sucessfully, but I don't have tested if the boot.img really works.
I use the fota-twrp since it came out and it works fine on lollipop...

on centos 6.6
sudo ./create-bootimg.sh
select recovery: [t]wrp or [p]hilz - TWRP
1. checking for unzip... done ("/usr/bin/unzip")
2. checking for lzma... done ("/usr/bin/lzma")
3. checking for cm12 rom zip... done ("cm-12-20150304-NIGHTLY-amami.zip")
4. checking for recovery zip... done ("Z1C-lockeddualrecovery2.8.2-RELEASE.installer.zip")
5. extracting boot.img... done
6. extracting recovery... done
7. unpacking boot.img... fail
in the /var/log/messages
Mar 6 13:33:50 mental automount[1717]: key ".directory" not found in map source(s).
Mar 6 13:33:50 mental automount[1717]: create_client: hostname lookup failed: Name or service not known
Mar 6 13:33:50 mental automount[1717]: create_client: hostname lookup failed: Name or service not known
Mar 6 13:33:50 mental automount[1717]: get_exports: lookup(hosts): exports lookup failed for .directory
Mar 6 13:33:50 mental automount[1717]: key ".directory" not found in map source(s)

mental_max said:
in the /var/log/messages
Click to expand...
Click to collapse
Look at the "error.log" in the same path like the script...

[TOOL] Tools for file extraction of system.img and TAR MD5 for ODIN flash

Here are the tools needed for file extraction of system.img and
TAR MD5 packing for ODIN flash, it means you could do your package with only the files to want to flash in ODIN, for me this tools are very useful.
ALL IS WORKING FLAWLESS WITH LOLLIPOP
http://www23.zippyshare.com/v/4v1wFBtL/file.html
Explanation:
------
For unpacking the system.img
NEWIMG2EXT2 system.img systemext2.img <- It converts ODIN images to EXT2 filesystem
Read the file systemext2.img with ext2explore and extract any file you want
NOTE: newimg2ext2 is renamed from the original file name SVAImgUnpack, credits to @svadev
-------
For packing files for ODIN, I made an example file that is named modem2tarmd5.bat, this pack modem.bin into modem.tar.md5 ready to be flashed with ODIN,
edit the .bat and use with the files you like.

Yes!! I have asked countless people and put a thread up but nobody answered. Thank you very much for this tool! I used to use EXT2EXPLORE on KitKat with my S4 Mini, now I can use it on my S6. Thank you!!

citytrader said:
Here are the tools needed for file extraction of system.img and
TAR MD5 packing for ODIN flash, it means you could do your package with only the files to want to flash in ODIN, for me this tools are very useful.
ALL IS WORKING FLAWLESS WITH LOLLIPOP
http://www23.zippyshare.com/v/4v1wFBtL/file.html
Explanation:
------
For unpacking the system.img
NEWIMG2EXT2 system.img systemext2.img <- It converts ODIN images to EXT2 filesystem
Read the file systemext2.img with ext2explore and extract any file you want
NOTE: newimg2ext2 is renamed from the original file name SVAImgUnpack, credits to @svadev
-------
For packing files for ODIN, I made an example file that is named modem2tarmd5.bat, this pack modem.bin into modem.tar.md5 ready to be flashed with ODIN,
edit the .bat and use with the files you like.
Click to expand...
Click to collapse
I'm FRP boot loop locked on my G928W8 and I can't fix it because stock firmware isn't available on sammobile yet. Can this tool be used by someone with the stock firmware to pull it off and fix my problem? Does it require root to make the image?
I need a stock firmware image before the battery runs down even while off. So if someone can extract their stock firmware then it could really save my phone. Is this something the tool could be used for, or would the md5 not be the same as the actual stock firmware so the FRP lock would stay?

thismonk said:
I'm FRP boot loop locked on my G928W8 and I can't fix it because stock firmware isn't available on sammobile yet. Can this tool be used by someone with the stock firmware to pull it off and fix my problem? Does it require root to make the image?
I need a stock firmware image before the battery runs down even while off. So if someone can extract their stock firmware then it could really save my phone. Is this something the tool could be used for, or would the md5 not be the same as the actual stock firmware so the FRP lock would stay?
Click to expand...
Click to collapse
You need someone that can dump the partitions of their phone and flash that partitions to your phone, you need to understand a bit the procedure before flashing with ODIN

citytrader said:
Here are the tools needed for file extraction of system.img and
TAR MD5 packing for ODIN flash, it means you could do your package with only the files to want to flash in ODIN, for me this tools are very useful.
ALL IS WORKING FLAWLESS WITH LOLLIPOP
http://www23.zippyshare.com/v/4v1wFBtL/file.html
Explanation:
------
For unpacking the system.img
NEWIMG2EXT2 system.img systemext2.img <- It converts ODIN images to EXT2 filesystem
Read the file systemext2.img with ext2explore and extract any file you want
NOTE: newimg2ext2 is renamed from the original file name SVAImgUnpack, credits to @svadev
-------
For packing files for ODIN, I made an example file that is named modem2tarmd5.bat, this pack modem.bin into modem.tar.md5 ready to be flashed with ODIN,
edit the .bat and use with the files you like.
Click to expand...
Click to collapse
How can we use it;;it gives wrong parameter if executed.needs editing;;the newimgext2 ??

citytrader said:
For unpacking the system.img
NEWIMG2EXT2 system.img systemext2.img <- It converts ODIN images to EXT2 filesystem
Read the file systemext2.img with ext2explore and extract any file you want
Click to expand...
Click to collapse
Works fine ! I tried a lot of methods to do the same thing, of firmware Lollipop Samsung Galaxy S6 and S5 neo. This method is the only one which works. Thanks !

Very good love it, works even on Nougat (S7).

LG V50 V450PM (Sprint) Android 9 full flash dump

Here's my dump from V450PM Android 9 not updated clean device. This may be useful for recovery and archiving purposes.
Dumped with QFIL, all partitions except userdata.
Mirror 1: mediafire.com (3.3 GiB)
Mirror 2: androidfilehost.com (3.3 GiB)

how to flash?

Also, using QFIL. I'll try, I'll post the result

vlad_trisha said:
Also, using QFIL. I'll try, I'll post the result
Click to expand...
Click to collapse
I don't see where in qfil to do it. I could flash them in partition manager but the file names dont say which file is which partition

I saved each section in QFIL. Then I compared, for example, my "ReadData_ufs_Lun5_0x620_Len32" with what is in the archive. I found it and renamed it, let's say in abl_a. And so with each file. As a result, I renamed all the files, flashed them, but in the end the download did not go beyond the splash screen. I had to go back to A 10.0

1maaax said:
the file names dont say which file is which partition
Click to expand...
Click to collapse
The names are in COM3_PartitionsList.xml.
<partition label="drm" physical_partition_number="0" start_sector="8198" num_partition_sectors="3584" type="89707CD8-2272-449B-A564-ED37238D240C" guid="2AB1C0BC-C6CF-0E8D-45CA-C20E224B082A" />
is
ReadData_ufs_Lun0_0x2006_Len3584_DT_23_01_2022_22_31_39.bin
start_sector is in hex in the file name.

I wrote a python script to dynamically rename the files but it has not been pushed to github yet. For this particular bin files, I also made a bash script to just rename the files. To use it, download and unzip the compressed file. Put this bash script in the same directory. Run the script with either ./rename_files.sh or bash rename_files.sh.

Hi, I flash manually all of the files but it not work, Anything I should know to do it correctly?