Database Develop

[Tutorial] Unbrick Optimus l3 e400 if you get bootloop after a kdz update

In normal circunstances, kdz update sould be the solution for bricked phones, but some (Very rare) times, it become the trouble itself.
It happened yesterday, i've flashed the kdz file on my l3 as usual, but instead of getting the stock rom, I got a bootloop.
This happened probably because I was using sdmerge before, and after flashing the stock kdz, the /data partition became corrupted in a way that nor stock rom or stock recovery was able to deal with the corrupted data, so the only thing i had access was the emergency mode.
In this case, the obvious solution is use cwm to wipe /data, but to flash cwm I need a working rom, and I didn't had any,
so in this tutorial we will flash cwm with kdz update to wipe /data and ressurect the phone.
the tutorial was originally posted here, but it's for optimus black, well, the process is almost the same here but i'll post it here because when this problem happened the first thing i did was to google "bootloop after kdz update e400", but i didn't found nothing and only founded that post some hours later.
you will need:
The cwm image
The KDZ file
Your prefered tool to flash the kdz
Cheat engine
CWMInject
The kdz file is encripted, so you can't simplely insert the cwm image on kdz, you must have the decrypted image to inject the cwm, well, the kdz is decrypted by the flashing tool before upload and the decrypted image is on the program's memory, so you will use cheatengine to find the memory adress of the stock recovery and use CWMInject to inject the cwm on the memory before the flashing tool reaches this adress, so you need to be fast!
1- open the task manager, the flashing tool, cwminject (don't forget to run it as administrator) and cheatengine.
2- on the flashing tool, prepare everything to the flash but DO NOT start the flashing process.
3- on cwminject, select the flash tool's process and the cwm image
4- on cheat engine, select the flash tool's process, set Value Type for String and scan Type for Search for text, on the text field type "ANDROID!".
5- Start the flashing process and keep the eye on the taskmanager, when the amount of memory used by the flasher grows you know that the kdz was decrypted, click on first scan on cheat engine, it sould find FOUR adresses with the word "ANDROID!", if it don't find the word or if it only find one it means that you have scanned to early and the image was not completely decrypted yet, in this case just click on new scan and then scan again until it find FOUR adresses with the word "ANDROID!", the last one is the adress that you need.
6- Now be fast to put the adress on the cwminject and click on write memory, the stock recovery will be overwritten with cwm.
7- Now just wait the flashing ends, your phone will continue with the bootloop, but now, you should have the cwm installed, so put back the battery and turn the phone on holding vol- and home to start the cwm recovery.
8- now you can wipe the /data partition and bring the phone back to life.
9- (OPTIONAL) flash the stock kdz without modifications, i recomend you to do that because we have used hacking methods do modify the flasher's memory, and we don't know all of the effects of this modification, your phone will not enter in the bootloop anymore because we have fixed the /data partition with cwm and the /data partition is not written when we flash a kdz.

It never happened with me, but thanks anyway!!!!:good::good::good::good::good:

thanks

Bricked LG L90 410: secure boot error in Download Mode

Hello,
I tried to install CWM and bricked the phone
Model: LG L90 D410
It appeared the error:
ERROR Boot Certification Verify, and Logo LG.
So I tried using the download mode to use KDZ,
when I enter the Download Mode, the error persists (see printscreen) and the screen turns off.
LGFlashTool and windows device manager does not recognize the phone, all drives have been updated.
plz help.
Additional information:
Hard reset works, but after doing the reset, the problem is the same. Boot error and Download Mode with Secure Boot Error (attached image) .
PC is still not recognizing the phone and nothing i can do.
Sorry my English

Read: http://forum.xda-developers.com/lg-l90/help/secure-boot-error-boot-certification-t2895538

F. Gacrux said:
Read: http://forum.xda-developers.com/lg-l90/help/secure-boot-error-boot-certification-t2895538
Click to expand...
Click to collapse
For me does not work because I can't flash KDZ, I do not have access to the Download Mode for this (see image).
And I can't do this http://forum.xda-developers.com/lg-l90/general/guide-fastboot-l90-d415-t2827825 because I don't have access to the phone (does not appear connected to PC).

Maybe this: http://forum.xda-developers.com/lg-l90/help/bricked-d410-t3094018/post61741908
Or this: http://forum.xda-developers.com/showthread.php?t=2582142
Make sure to use the right sbl1, aboot, rpm, tz and recoveryimages of your model. If you don't find those files, maybe someone can backup the partitions for you, I own a different model D410HN

F. Gacrux said:
Maybe this: http://forum.xda-developers.com/lg-l90/help/bricked-d410-t3094018/post61741908
Or this: http://forum.xda-developers.com/showthread.php?t=2582142
Make sure to use the right sbl1, aboot, rpm, tz and recoveryimages of your model. If you don't find those files, maybe someone can backup the partitions for you, I own a different model D410HN
Click to expand...
Click to collapse
Thanks for your attention! My phone is the same.
But as said, the computer (Linux or Windows) did not recognize the phone, COM, Modem, Unknown device, nothing...
Hard Disk Low Level Format Tool only appears my HD, so i am stuck in step 3.

niquelfer said:
Thanks for your attention! My phone is the same.
But as said, the computer (Linux or Windows) did not recognize the phone, COM, Modem, Unknown device, nothing...
Hard Disk Low Level Format Tool only appears my HD, so i am stuck in step 3.
Click to expand...
Click to collapse
In this case the right binaries can be retrieved from the dz inside the kdz with LG Firmware Extract.
Regard your device not being recognized, can you please run USBDeview (run as admin, download: http://www.nirsoft.net/utils/usb_devices_view.html), plug the USB cable in your device, refresh and see if something popup in the connected devices list? Your need the qhsusb_bulk to show up in device manager. Maybe removing not connected devices in usbdeview to clear drivers and rebooting your PC can work.

This Tutorial worked very well. Thanks all.
http://forum.xda-developers.com/lg-...ick-hard-bricked-l90-variants-t3173429/page15

D410
F. Gacrux said:
Maybe this: http://forum.xda-developers.com/lg-l90/help/bricked-d410-t3094018/post61741908
Or this: http://forum.xda-developers.com/showthread.php?t=2582142
Make sure to use the right sbl1, aboot, rpm, tz and recoveryimages of your model. If you don't find those files, maybe someone can backup the partitions for you, I own a different model D410HN
Click to expand...
Click to collapse
Hey. I need these img files sbl1, aboot, rpm, tz for my LG l90 dual D410. Please help

Jaimil said:
Hey. I need these img files sbl1, aboot, rpm, tz for my LG l90 dual D410. Please help
Click to expand...
Click to collapse
Extract from your KDZ file.

lg l90 405 is believed to be 410 dual sim

hi to all guys, I would like to draw your attention to what happened to me, and possibly know how to restore.
I am owner of a lg l90 model d405n, wanting to unlock the bootloader I used an application that I would have to just unlock the bootloader and install a modified recovery.
Actually 'cell after this hack is pretty much dead, he would not turn either.
I started looking for various tools and various programs in vain, the cell showed no signs of life.
Then, now giving it up for lost, I tried to go for broke, I low-level formatted, and then with an application (umbrick) I could flesciare boot and everything else. Now the cell was lit and was also in mode 'upgrade download.
I downloaded the firmware of KDZ 405 and I tried to use flash tool but the procedure is always blocked to 2%, giving an error.
With the tool of 'LG blatantly that I discovered the phone was identified as d410, exhausted by the various trials do not go into port I wanted to download the KDZ model 410d and, as if by magic, flash tool worked! I installed the latest version and the phone works wonders!
So now I have a cell phone with firmware that is not his (among other things the 410d is also dual sim).
I would like to restore its system orifginale, that of the 405, but I'm afraid to do other **** ....
I hope someone can help me out

sebasrul21 said:
hi to all guys, I would like to draw your attention to what happened to me, and possibly know how to restore.
I am owner of a lg l90 model d405n, wanting to unlock the bootloader I used an application that I would have to just unlock the bootloader and install a modified recovery.
Actually 'cell after this hack is pretty much dead, he would not turn either.
I started looking for various tools and various programs in vain, the cell showed no signs of life.
Then, now giving it up for lost, I tried to go for broke, I low-level formatted, and then with an application (umbrick) I could flesciare boot and everything else. Now the cell was lit and was also in mode 'upgrade download.
I downloaded the firmware of KDZ 405 and I tried to use flash tool but the procedure is always blocked to 2%, giving an error.
With the tool of 'LG blatantly that I discovered the phone was identified as d410, exhausted by the various trials do not go into port I wanted to download the KDZ model 410d and, as if by magic, flash tool worked! I installed the latest version and the phone works wonders!
So now I have a cell phone with firmware that is not his (among other things the 410d is also dual sim).
I would like to restore its system orifginale, that of the 405, but I'm afraid to do other **** ....
I hope someone can help me out
Click to expand...
Click to collapse
Did you still have your stock bootloader backup?

neverdies said:
Did you still have your stock bootloader backup?
Click to expand...
Click to collapse
unfortunately no

Stock bootloader (aboot and abootb) can be retrieved from your model KDZ. Every partition, except modemst1 & 2 can be re-flashed from the KDZ.
But the bootloader alone won't do anything, you must flash the entire bootstack of D405n, enter in Donwload Mode again and LG Flash Tool will allow you to flash the entire KDZ again in Emergency Mode without errors.
If you IMEI was lost or changed, it can be restored with other programs after.

F. Gacrux said:
Stock bootloader (aboot and abootb) can be retrieved from your model KDZ. Every partition, except modemst1 & 2 can be re-flashed from the KDZ.
But the bootloader alone won't do anything, you must flash the entire bootstack of D405n, enter in Donwload Mode again and LG Flash Tool will allow you to flash the entire KDZ again in Emergency Mode without errors.
If you IMEI was lost or changed, it can be restored with other programs after.
Click to expand...
Click to collapse
I thank you for the reply but unfortunately being very inexperienced I would need a guide more ' detailed . Excuse my English ( Google translation )

sebasrul21 said:
I thank you for the reply but unfortunately being very inexperienced I would need a guide more ' detailed . Excuse my English ( Google translation )
Click to expand...
Click to collapse
the premise that no sd card , I have to flash aboot ? adb push aboot.bin ? what are the steps for not briccarlo again ?

sebasrul21 said:
I thank you for the reply but unfortunately being very inexperienced I would need a guide more ' detailed . Excuse my English ( Google translation )
Click to expand...
Click to collapse
Answer so I can give you the proper response :
- Rooted?
- Unlocked bootloader?
- Custom recovery (twrp)?
- Variant model and country.
- Carrier model (if yes, which carrier)?

F. Gacrux said:
Answer so I can give you the proper response :
- Rooted?
- Unlocked bootloader?
- Custom recovery (twrp)?
- Variant model and country.
- Carrier model (if yes, which carrier)?
Click to expand...
Click to collapse
rooted yes
unlock bootloader I think not , how does a SEE?
custom recovery no
the phone is a lg d405n but now has become lg d410 dual sim version sw v20 - op1 - hq version Android 5.0.2 Italy no carrier

There is no way to know if the bootloader is unlocked, unless you make aboot partition image and hash check to compare with the original bootloader.
You have first to flash the hacked bootloader (aboot), since you don't know if it's unlocked, it won't hurt to flash again.
First enable USB debugging, at this point I assume you know how to do this.
Download the hacked aboot for D405n v20a:
http://www.mediafire.com/download/bn39rz7ojtosqm3/D405n_v20a_patched_aboot.zip (taken from this thread: http://forum.xda-developers.com/lg-l90/development/recovery-twrp2-7-1-0lgl90w7xxshoxx-t2826150)
Extract the zip and copy aboot.bin to the root of your sdcard. Open android terminal ou adb, take su permission and allow it on your phone screen, flash the hacked bootloader with:
If you copied to the external microSD: dd if=/storage/external_SD/aboot.bin of=/dev/block/platform/msm_sdcc.1/by-name/aboot
If you copied to the internal sd: dd if=/sdcard/aboot.bin of=/dev/block/platform/msm_sdcc.1/by-name/aboot
Now flash custom recovery. Download http://forum.xda-developers.com/devdb/project/dl/?id=13334 (taken from the same thread).
Copy TWRP_2.8.7.0_270615_L90.img to the root of your sdcard. To make things easier, rename it to recovery.img. Take su permission and flash with adb or android terminal with:
If you copied to the external microSD: dd if=/storage/external_SD/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
If you copied to the internal sd: dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
Now reboot into twrp custom recovery, you can either send reboot recovery command in adb shell or terminal, or with your phone off, hold VOL - and PWR button, when lg logo appears, release and hold PWR button again until a blank screen appears, select YES twice (navigate with VOL buttons and PWR to select). Since now you are on custom recovery, twrp will boot instead a factory reset routine.
Download your D405n bootstack: https://www.androidfilehost.com/?fid=24052804347759484 (taken from this thread: http://forum.xda-developers.com/lg-l90/development/bootstack-kk-l-l90-t3118632)
Copy to your sdcard (do not extract the file). In TWRP recovery, select INSTALL and flash the zip.
Download your italy D405n v20a lollipop kdz: http://csmgdl.lgmobile.com/dn/downloader.dev?fileKey=FW932KU032N9A1T29B55QPQ/D405n20a_00.kdz
Follow this thread to flash with LG Flash Tool (if you already have usb drivers installed, start at step 5): http://forum.xda-developers.com/lg-l90/general/guide-flash-stock-kdz-offline-lg-l90-t2803479
If you face force closes after the first boot, do a factory reset (VOL- and PWR button, like I described before, but since now you are all stock, factory reset will be applied).
Now you are 100% on your italy d405n v20a lollipop.

F. Gacrux said:
There is no way to know if the bootloader is unlocked, unless you make aboot partition image and hash check to compare with the original bootloader.
You have first to flash the hacked bootloader (aboot), since you don't know if it's unlocked, it won't hurt to flash again.
First enable USB debugging, at this point I assume you know how to do this.
Download the hacked aboot for D405n v20a:
http://www.mediafire.com/download/bn39rz7ojtosqm3/D405n_v20a_patched_aboot.zip (taken from this thread: http://forum.xda-developers.com/lg-l90/development/recovery-twrp2-7-1-0lgl90w7xxshoxx-t2826150)
Extract the zip and copy aboot.bin to the root of your sdcard. Open android terminal ou adb, take su permission and allow it on your phone screen, flash the hacked bootloader with:
If you copied to the external microSD: dd if=/storage/external_SD/aboot.bin of=/dev/block/platform/msm_sdcc.1/by-name/aboot
If you copied to the internal sd: dd if=/sdcard/aboot.bin of=/dev/block/platform/msm_sdcc.1/by-name/aboot
Now flash custom recovery. Download http://forum.xda-developers.com/devdb/project/dl/?id=13334 (taken from the same thread).
Copy TWRP_2.8.7.0_270615_L90.img to the root of your sdcard. To make things easier, rename it to recovery.img. Take su permission and flash with adb or android terminal with:
If you copied to the external microSD: dd if=/storage/external_SD/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
If you copied to the internal sd: dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
Now reboot into twrp custom recovery, you can either send reboot recovery command in adb shell or terminal, or with your phone off, hold VOL - and PWR button, when lg logo appears, release and hold PWR button again until a blank screen appears, select YES twice (navigate with VOL buttons and PWR to select). Since now you are on custom recovery, twrp will boot instead a factory reset routine.
Download your D405n bootstack: https://www.androidfilehost.com/?fid=24052804347759484 (taken from this thread: http://forum.xda-developers.com/lg-l90/development/bootstack-kk-l-l90-t3118632)
Copy to your sdcard (do not extract the file). In TWRP recovery, select INSTALL and flash the zip.
Download your italy D405n v20a lollipop kdz: http://csmgdl.lgmobile.com/dn/downloader.dev?fileKey=FW932KU032N9A1T29B55QPQ/D405n20a_00.kdz
Follow this thread to flash with LG Flash Tool (if you already have usb drivers installed, start at step 5): http://forum.xda-developers.com/lg-l90/general/guide-flash-stock-kdz-offline-lg-l90-t2803479
If you face force closes after the first boot, do a factory reset (VOL- and PWR button, like I described before, but since now you are all stock, factory reset will be applied).
Now you are 100% on your italy d405n v20a lollipop.
Click to expand...
Click to collapse
thank you so much I immediately start work hoping to do no harm

sebasrul21 said:
thank you so much I immediately start work hoping to do no harm
Click to expand...
Click to collapse
perdona un altra cosa, io in questo momento non uso schede microsd, come cambia questa: "if you copied to the external microSD: dd if=/storage/external_SD/aboot.bin of=/dev/block/platform/msm_sdcc.1/by-name/aboot
If you copied to the internal sd: dd if=/sdcard/aboot.bin of=/dev/block/platform/msm_sdcc.1/by-name/aboot"

sebasrul21 said:
perdona un altra cosa, io in questo momento non uso schede microsd, come cambia questa: "if you copied to the external microSD: dd if=/storage/external_SD/aboot.bin of=/dev/block/platform/msm_sdcc.1/by-name/aboot
If you copied to the internal sd: dd if=/sdcard/aboot.bin of=/dev/block/platform/msm_sdcc.1/by-name/aboot"
Click to expand...
Click to collapse
forgive one other thing , I do not at this time use cards microSD , as changes this

I gave you the two options, to copy the necessary files to microSD or internal memory, and what part you didn't understand?
If you don't use microSD, you must use the internal SD command (If you copied to the internal sd: dd if=/sdcard/... etc).
In android, both storage is called SD, the internal one that comes with the phone is the internal SD (sdcard0, media, sdcard, etc), the other one that you stick in the phone is the external SD (external_SD).

sebasrul21 said:
thank you so much I immediately start work hoping to do no harm
Click to expand...
Click to collapse
I run everything perfectly but in the end , When I go to run the flash tool gives me Error
"upgrade because of error ...
lg mobile support tool detects : sw : D41020A LG V500 version sw : V50020F are AVAILABLE agggiornamenti :crying:

sebasrul21 said:
I run everything perfectly but in the end , When I go to run the flash tool gives me Error
"upgrade because of error ...
lg mobile support tool detects : sw : D41020A LG V500 version sw : V50020F are AVAILABLE agggiornamenti :crying:
Click to expand...
Click to collapse
flash tool: Wait until software extraction is complete. stop

sebasrul21 said:
flash tool: Wait until software extraction is complete. stop
Click to expand...
Click to collapse
continues to be invecie 410 of 405

upgrade stopped due to an error

This is not possible. If you flashed D405n bootstack, there is no way LG Flash Tool recognize your phone as D410.
Are you running the LG Flash Tool mod or the official LG Mobile Support Tool? Are you using Download Mode set to Emergency?
On Read Phone Information, you don't need to run it (sometimes it hangs), and click on Clear phone Software update Registry on Select Country % Language Window.
Also check if the KDZ you downloaded is not corrupted. It's a common error the flash tool fail because the kdz is corrupted.

F. Gacrux said:
This is not possible. If you flashed D405n bootstack, there is no way LG Flash Tool recognize your phone as D410.
Are you running the LG Flash Tool mod or the official LG Mobile Support Tool? Are you using Download Mode set to Emergency?
On Read Phone Information, you don't need to run it (sometimes it hangs), and click on Clear phone Software update Registry on Select Country % Language Window.
Also check if the KDZ you downloaded is not corrupted. It's a common error the flash tool fail because the kdz is corrupted.
Click to expand...
Click to collapse
unfortunately so I assure you , I used the flash tool set to emergency and it always fails with the KDZ 405 , invecie loading the KDZ 410 installs easily

sebasrul21 said:
unfortunately so I assure you , I used the flash tool set to emergency and it always fails with the KDZ 405 , invecie loading the KDZ 410 installs easily
Click to expand...
Click to collapse
I followed step by step your guide, a KDZ files are not corrupt , I have tried several of the 405 does not work and no one , instead the KDZ 410 works .
The IMEI is zero

[Guide]Extracting Stock firmware files using Huawei Update Extractor/splitupdate

There seems to be a little confusion on how to do this and I've written down how to in many posts now so I figure I'd just write it down in a little guide.
What you need:
Firmware update.zip from http://pro-teammt.ru/firmware-database/
Windows only: Huawei Update Extractor
Linux/Mac(?)/(Windows too): splitupdate perl script (requires perl)
Direct link: https://mega.nz/#!4PBknJrK!iZQDI4ti6ERmQJC6afgUGTSvHHKcm9KFz9okmwwez3I
Source: https://github.com/marcominetti/split_updata.pl/tree/f5f415262be3487de28321b49dcb69d947897bf1
(Or my 'special' version https://mega.nz/#!NS4VnL7Q!5GMn-soCf_WMW6fZANd-TDzxjQkZW2LynEQtJ_TlUdU which extracts
to the same folder as 'splitupdate' instead of 'output/', and includes a mount script (Linux only, maybe Mac?) for extraction of files of the different images)
Archive extractor of your choice (7zip, winrar, winzip and so on.)
Firmware build
First you need to determine what your current firmware is, this can be done by going to 'Settings -> System -> About Phone' on your phone. Check 'Build Number'.
Mine says:
{
"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"
}
BLA-L29 8.0.0.132(C636) (Replace 8.0.0. with C636 and add a B infront of 132 )
This can be translated into BLA-L29C636B132.
Now we have our current firmware!
Info on Nougat -> Oreo
As of Oreo the partitions changed a little.
'Boot' partition was split into 'ramdisk' and 'kernel'.
'Recovery' partition was split into 'recovery_ramdisk', 'recovery_vendor' and 'recovery_vbmeta', and shares the 'kernel' partition with 'ramdisk'.
The one's you probably want to flash are 'ramdisk' and 'recovery_ramdisk'. (Ramdisk is where Magisk/SuperSU goes, recovery_ramdisk is where TWRP goes)
Firmware update.zip
In this example I will be using my firmware, BLA-L29C636B132.
First start by going to http://pro-teammt.ru/firmware-database/ and enter your full firmware in the 'Enter model', click on Find Model.
This is what it will look like after you have searched. Locate the row that says FullOTA-MF and click on the 'update' link in that row.
When it's downloaded, open update.zip in your choice of archive manager and extract UPDATE.app to your desktop or somewhere easy to find.
Huawei Update Extractor:
Download Huawei Update Extractor from the link above, it's attached to first post in that thread I linked to (v0.9.9.5).
Extract the zip to your desktop (Or Downloads folder).
Enter the newly created folder that should be named 'HuaweiUpdateExtractor_0.9.9.5', and run HuaweiUpdateExtractor.exe.
Start by going to the 'Settings' tab and uncheck 'Verify header checksum'.
(Something is wrong with the header of erecovery_ramdisk, also it's mispelled to erecovery_ramdis, or maybe character limit? The partition on phone is named correctly. This does not need to be unchecked on Nougat firmware)
Then go back to the 'Extract' tab and click on the button that says '...' and open your UPDATE.APP
Rightclick on the file you want to extract and click on 'Extract Selected', this will bring up a dialog where you choose where to extract to.
After this you can flash the file using fastboot. Take 'ramdisk' for example.
Make sure you have adb & fastboot installed (https://forum.xda-developers.com/showthread.php?t=2317790)
Open up a command prompt and connect phone, reboot to fastboot mode using: usb plugged in, power + vol down, release power when phone vibrates.
Or you can use the command 'adb reboot bootloader'.
Make sure phone is recognized in fastboot mode with the command: 'fastboot devices', it should show up as a fastboot device.
Next we can flash RAMDISK.img using: 'fastboot flash ramdisk RAMDISK.img'.
On Nougat you would extract 'BOOT' from UPDATE.APP and flash using:
'fastboot flash boot BOOT.img'
Linux/Mac(?)(and Windows with perl installed, I use Strawberry Perl)
First download the splitupdate zip from above.
Extract it and enter the extracted 'split' folder, open a terminal and:
'chmod +x splitupdate'
'chmod +x crc'
Now put your UPDATE.APP in the 'split' folder and open a terminal and use the following command:
'./splitupdate UPDATE.APP file_to_extract'. If you write 'file_to_extract' or anything that is or is not in the UPDATE.APP it will list all images in it.
Typing './splitupdate UPDATE.APP' will extract all files in UPDATE.APP
It will output files to the newly created 'output' folder. The filtering is not perfect. If you use './splitupdate UPDATE.APP RAMDISK', it will extract all images with RAMDISK in its name, so you will get RAMDISK.img and RECOVERY_RAMDISK.img. This is fine for me as the original script extracted everything, which takes long for the larger images.
And if you use the 'special' version:
'chmod +x simg2img'
'chmod +x mount.sh'
I edited the splitupdate script for the 'special' version just to make it easier for me as I like to check SYSTEM, VENDOR, PROCDUCT and those images for changes.
So it made it easier if it extracted directly to the root of 'split' folder instead of 'output', then I could run the mount.sh script directly.
To use mount.sh, first edit the script and replace YOUR_SUDO_PASSWORD_HERE with your password or remove 'echo YOUR_SUDO_PASSWORD_HERE | ' and input password manually when it asks.
Then simply extract SYSTEM.img (or Product, vendor, odm whichever you like) and './mount.sh SYSTEM' (yes, no extension).
This will convert SYSTEM.img to SYSTEM.raw and mount it to 'split_folder/SYSTEM/' as a loop device, it will also chmod 777 everything in SYSTEM/.
Linux ADB and Fastboot
Use google for this one. ADB usually works fine right away, Fastboot might get 'no permissions' and need to be run as sudo if it's missing udev permissions/entries.
You can make fastboot work without sudo but it's easier to google it as it might get lengthy and there are a lot of different distros of linux (I use Ubuntu)

Hi ante0, i have downloaded the bla a09 8.0.0.109 c567 which is the recent update for my US mate 10 pro version, i was using hisuite to update my phone which is failing but i was able to grab the update which it down loaded and it has the following files in it, bla-a09_hw_usa( which contains update_full_BLA-A09_hw_usa, public( which contains update_data_full_public), update.zip which contains update.app and other xml files, i have already bl unlocked and rooted with supersu but i wanted to install magisk and i installed twrp and tried sideloading magisk but it fails stating boot image already modified and advised flask stock boot, so which files do i need to flash and what are the fastboot commands to do so and i was also thinking about complete bl lock just to make it look like new phone and how do i do that, please direct me, thank you.

I think to update you'll need to:
A) Unroot your supersu.
B) Restore stock boot and restore your stock recovery with guide in OP and with the firmware files actually installed on your phone.
Then you could root oreo with magisk.

oslo83 said:
I think to update you'll need to:
A) Unroot your supersu.
B) Restore stock boot and restore your stock recovery with guide in OP and with the firmware files actually installed on your phone.
Then you could root oreo with magisk.
Click to expand...
Click to collapse
there lies my problem, i am trying to flash an updated stock firmware than the one that came with my phone, i have unrooted supersu and deleted supersu app and dont have root anymore confirmed by rootcheck apps, since my boot is already patched once magisk wont flash and advising me to flash stock boot image but i dont know which to flash as with oreo there seems to be different partitions and i dont know commands other than basic fastbbot commands to flash stuff.

ok so i was able to flash ramdisk, recovery and system and boot back to OS ( i have earlier erased system by mistake) and i have flashed system.img from updated firmware but version still shows old one, and i am trying to use funkyhuawei erecovery method to flash the updated firmware and when i boot to erecovery to update but the update button is missing and i just have rebbot, wipe date/fr and wipe cache, so what do i need to flash and commands for it in order to make erecovery work and i have update button enabled, thank you.

lingarajug said:
ok so i was able to flash ramdisk, recovery and system and boot back to OS ( i have earlier erased system by mistake) and i have flashed system.img from updated firmware but version still shows old one, and i am trying to use funkyhuawei erecovery method to flash the updated firmware and when i boot to erecovery to update but the update button is missing and i just have rebbot, wipe date/fr and wipe cache, so what do i need to flash and commands for it in order to make erecovery work and i have update button enabled, thank you.
Click to expand...
Click to collapse
If you can, use the HWOTA method instead. It's free and found: https://forum.xda-developers.com/mate-10/how-to/guide-mate-10-flash-oreo-update-package-t3716814
If you can't use HWOTA and have to use Funky:
You seem to be in normal Recovery. You should see a button that says 'Download latest firmware', the one you're describing is showing buttons that are in normal Recovery.
Are you booting using Usb plugged in + vol up + power?

For some reason my phone would only boot to revovery and not erecocery, anyway i used hisuite method and was able to flash new firmware. Thank you.

I've just unbricked my Mate 10 pro via this method. Thank you Sir.

Not sure if this is the right place but where can I find the original Huawei OS it was shipped with? I installed Lineage and want to go back to Factory.
I just want to .img file. I have only unlocked the bootloader not rooted the phone.
Lack of camera and other features means I need to get back.
Any ideas?

elviss0812345 said:
I've just unbricked my Mate 10 pro via this method. Thank you Sir.
Click to expand...
Click to collapse
You bricked your device because you don't know what you are doing,not because of this guide.Oh,and i thought KangRom was responsible for bricking you device....anyone else to blame ?

My phone was bricked because of Lineage OS, and i unbricked with this guide. Read my post first.
Pretoriano80 said:
You bricked your device because you don't know what you are doing,not because of this guide.Oh,and i thought KangRom was responsible for bricking you device....anyone else to blame ?
Click to expand...
Click to collapse

elviss0812345 said:
My phone was bricked because of Lineage OS, and i unbricked with this guide. Read my post first.
Click to expand...
Click to collapse
lol,i've read "bricked"... .I apologize for that!:good:

There is no way at least for the US version to find firmwares shipped with phone until now, i figured it out by connecting phone to hisuite on PC and it showed update available and i clicked update and waited until download part of update process completed and then i went to documents folder and hisuite and the app stores the download there and it will have 3 zip files, u can copy them to a different place because once the update completes those files are deleted. Might be the same for other models if supported by hisuite.

Here https://playstoreappinstall.com/play-store-for-huawei/ more info

@lingaraguj not already listed there :
http://pro-teammt.ru/firmware-database/?firmware_model=ALP
?

oslo83 said:
@lingaraguj not already listed there :
http://pro-teammt.ru/firmware-database/?firmware_model=ALP
?
Click to expand...
Click to collapse
US version firmware not listed, lots of international versions though.

can i flash everything in UPDATE.APP to go back to fully stock.
if i can what is the fastboot command for every one of them files like "fastboot flash ramdisk RAMDISK.img'?
ive mate 10 pro.

lex71 said:
Not sure if this is the right place but where can I find the original Huawei OS it was shipped with? I installed Lineage and want to go back to Factory.
I just want to .img file. I have only unlocked the bootloader not rooted the phone.
Lack of camera and other features means I need to get back.
Any ideas?
Click to expand...
Click to collapse
It should say your current firmware (besides Lineage) in Settings -> (System?) -> About.
dark3bod said:
can i flash everything in UPDATE.APP to go back to fully stock.
if i can what is the fastboot command for every one of them files like "fastboot flash ramdisk RAMDISK.img'?
ive mate 10 pro.
Click to expand...
Click to collapse
It's better to use:
https://forum.xda-developers.com/mate-10/how-to/guide-mate-10-flash-oreo-update-package-t3716814
I'm not sure if symlinks will be set up correctly if you flash images directly. And some partitions can't be flashed from fastboot (like the erecovery ones)

ante0 said:
It should say your current firmware (besides Lineage) in Settings -> (System?) -> About.
It's better to use:
https://forum.xda-developers.com/mate-10/how-to/guide-mate-10-flash-oreo-update-package-t3716814
I'm not sure if symlinks will be set up correctly if you flash images directly. And some partitions can't be flashed from fastboot (like the erecovery ones)
Click to expand...
Click to collapse
@ante0
This man is a legend.........
I would like to express my gratitude in you answering my pms and assisting to get the device up and running.
If ever am in Sweden:silly: ill definitely buy you beeeeeeeeeeeeeeeeeeeeeeers
Thanks for the patience and the help you bring to us noobs bricking these bloody Mate 9's

Im now on lineage os. I didnt flash twrp and magisk. Can i only flash stock system.img to get fully stock. Or i have to flash ramdisk and boot first before system.img

[Tutorial] Crossflash, Bypass OPID Mismatched Error

Hi there
Thanks to all other guys here who have made helpful development to tame this beautiful =)
To crossflash models other than LG G8 please read post 3.
Before asking any question please read the troubleshooting section at the bottom of the page.
If you still need some specific help I would appreciate if you bring it up just in the thread instead of sending direct messages.
LG has made things difficult in flashing custom and even stock roms by this new OPID thing! It prevents us from crossflashing but we have been able to use TWRP and change the system and some other partitions to have a different rom. We had to make some changes into OP partition using HxD editor.
But now, through this tutorial, we're able to flash any rom without the need to change OPID in OP partition. Also, there is no need to root or unlock boot-loader.
I was successful to do this on some G8 (LMG820UM) but I AM NOT RESPONSIBLE FOR ANY HARM TO YOUR PHONE!
By continuing to read the following instructions you are actually accepting the risk.
IMPORTANT!
first, MAKE A FULL BACKUP OF ALL PARTITIONS; and I mean it!!!
at least, for your sake, make a backup of "modemst1, modemst2, fsg, fsc, ftm" partitions, for emergency.
Requirements
QPST and Qualcomm USB Driver (get)
LGE SM8150 Firehose (get)
LGUP 1.16.0.3 (get)
LGUP_Common.dll (get)
UI_Config.lgl (get)
LG Mobile Driver 4.4.2 (get)
Preparation
1. Install QPST and Qualcomm USB Driver.
2. Install LGUP.
3. Find the folder named "model" in the installation directory of LGUP, then Create a folder named "common" in the "model" folder.
4. Move "LGUP_Common.dll" and "UI_Config.lgl" into "common" folder. Change the attribute of "UI_Config.lgl" to read only.
5. Install LG Mobile Driver 4.4.2.
Steps
A)
1. Open QFIL.
2. Change "Storage Type" to UFS.
3. Select "Flat Build".
4. Browse for "LGE SM8150 Firehose" and pick it.
5. Now, connect the phone to PC and boot into EDL mode.
6. Open "Select Port" and select the phone, press OK.
7. In "Tools" open the "Partition Manager".
B)
!!!BE CAREFUL TO DO EXACTLY AS THE INSTRUCTIONS SAY OR YOU WILL BRICK THE PHONE!!!
1. Make a backup of and erase these 7 partitions: FTM, Modem_A, Modem_B, SID_A, SID_B, OP_A, OP_B.
1.1. You have to left-click on a partition then right-click on it and select "Manage Partition Data".
1.2. In the pop-up window, you have 4 choices: I. Erase (to erase data on the partition), II. Read Data (to dump or back up the partition), III. Load Image (to restore the partition), IV. Close (to close the window).
1.3. First dump/back up the partition by choosing "Read Data" then Erase it.
2. Close the "Partition Manager" window.
3. Wait for 5 seconds then press Vol- and Power until it restarts.
3.1. Immediately after rebooting, Release the Vol- and Power buttons and press Vol+ to get into Download Mode.
Note: Do not let the phone to begin to boot! If it begins to boot, it may regenerate the SID and FTM partitions data and so you need to redo the whole step B.
C)
1. Open LGUP.
2. Pick your favorite KDZ.
3. Select "PARTITION DL".
4. Press Start. And a pop-up window will appear. In this window you can select which partitions to be flashed.
5. Here, uncheck these partitions: SID_A and SID_B. It will make it able to bypass the OPID Mismatched Error.
6. If you are in Sprint or other platforms you will get the message whether to change the model or not. Of course you know what to do =)
after completing the process it will boot up in some minutes and before starting the customization it will do one restart. just be patient.
ERRORS, QUESTIONS, TROUBLESHOOTING
1. Can I crossflash V50, V60, G8X or other LG devices using this method?
I did it on V50. Maybe it'll work on your devices maybe won't. There's one way to find out; make backup and give it a try.
2. SN is gone, zero, etc.
Restore your original FTM.
3. I can't get into recovery.
Restore the original FTM.
4. I got NT-Code error.
It's been discussed many times in the thread and some solutions have been presented (such as this one, thanks to @animo214 and this, thanks to @kt-Froggy as well as this one, thanks to @StvOchi ). However, you can ignore it if the phone got network.
Note: You need to disable verity on the phone in advance otherwise changes in cust_path_mapping.cfg won't be saved.
5. IMEI is lost, zero, null etc.
Restore LUN5 partitions. If you have no backup it should be repaired using Octopus box. Go to 16.
6. I got "permanently locked" error.
This is because of IMPL lock and you have to restore LUN5 partitions. In case of having no backup you should use Octopus box.
7. All partitions are deleted accidentally.
Follow this instructions.
8. I need to get into PDM mode.
Unzip and restore the attached PDM to FTM partition. Remember, you need to restore your FTM to get into OS.
9. Can I use another phone's LUN5 backup?
NO.
10. Can I use another phone's FTM backup?
Yes. All partitions can be restored from another phone's backup except LUN5 partitions.
11. My phone is stuck in boot-loop.
Restore the original FTM and if it doesn't help redo the whole crossflash process and use a different KDZ this time.
12. Which KDZ is the best (for any matter of use)?
I do not know.
13. Can I crossflash from any source variant to Korean variant or vice versa?
Yes it is possible but you may get error on opening stock camera application because of hardware differences. There are some methods to solve the issue which you can search and find them.
14. Can I downgrade using this method?
Yes.
15. I erased partitions (ftm, op_a, op_b, modem_a, modem_b, sid_a, sid_b) but it still does not let me to crossflash.
Redo the whole process and this time make backup of and erase these partitions too, on both sides A and B: vendor, product, system, boot and userdata. Do not make backup of userdata partition.
16. How can I write IMEI?
A) Dump modem_a and create a copy of it. Then open it in UltraISO and remove IMEIPROT files from image folder. Save and restore it in place of modem_a and modem_b partitions.
B) Make backup of FTM and then flash or restore the PDM file (attached) into your ftm partition. Restart the phone; you'll get into PDM mode.
C) Open Tutty (attached). Select "Serial" in protocol and the proper port of your phone's modem driver. Click open. To test if you have selected the proper port number type "at" and hit enter it should respond"ok". Type the code at%imei=# (replace # with your IMEI) and hit enter. It doesn't matter you get "error" or "ok" after that, just check if IMEI is written via this code at%imei=?. If IMEI is written so you'll have the right MEID and ESN too.
D) Restore the original ftm and modem_a in place of modem_a and modem_b. Restart the phone.
I've already tested this method on V30, V50 and G8. Remember, if the phone has IMPL lock it'll throw "perm. locked" error even if you have written the IMEI.
17. I have lost GPT files of my LG G8, G8X, G8S, V50, etc. and Qfil partition manager does not show anything in the list.
You need to flash GPT files to your device with fh_loader (see this, part C). For that matter use KDZ_Tools to Extract DZ from a KDZ of your device. Then extract the DZ using -c at the end of extracting command. For example: unkdz -f FILE_NAME.kdz -c. It will extract all files besides all GPTs.
18. Which are the LUN5 partitions?
SM8150 has 7 physical partitions known as LUNs which are numbered from 0 to 6. Each LUN is split into several partitions. In Qfil Partition Manager you can see all partitions except those of LUN3 and LUN6 which are hidden. The number of LUNs are shown under the first column named LUN. Therefore, all partitions in front of number 5 are LUN5 partitions.

Some pictures of flashing my LMG820UM, unlocked from Sprint, into OPEN_CA 20j. In normal mode you cannot flash SPR_US to OPEN_CA which is shown in the pictures. But using this thread instruction it allows to flash, even it asks to change the model from SPR_US to OPEN_CA
Until performing the instructions, it shows the "id: 2(SPR_US)" on the Download Mode screen, but after that it cannot recognize the phone model id and shows "id: 0()"
Have fun ^_^

LG K31 Crossflashing:
To crossflash LG K31 go to this guide. Thanks to @Wish39.
LG Stylo 6 Crossflashing:
To crossflash LG Stylo 6 using LG K71 Android 12 firmware see this. Thanks to @Wish39.
LG V50 Crossflashing:
I had two LG V50 (LMV450) to which I flashed Korean Andorid 12 using the method mentioned in the first post. I cannot guarantee that it will work on every V50. After corssflashing I found out that one of them had the problem of draining battery due to not getting into deep sleep mode. To overcome the issue, I reflashed it via "Chip Erase" this time, and then again reflashed it but in the same way mentioned for crossflashing in the first post. Of course, I had created backup and at the end I restored LUN5 partitions.

Hey nice! It's great to have options. I'm currently using us Open OP on my Sprint device (of course totc changed). It's working fine and not sure of any reason to change.
Although, if we do get a11 firmware available, that will change things for sure.
Thanks, nice work!

great, thank you

netmsm said:
Some pictures of flashing my LMG820UM, unlocked from Sprint, into OPEN_CA 20j. In normal mode you cannot flash SPR_US to OPEN_CA which is shown in the pictures. But using this thread instruction it allows to flash, even it asks to change the model from SPR_US to OPEN_CA
Until performing the instructions, it shows the "id: 2(SPR_US)" on the Download Mode screen, but after that it cannot recognize the phone model id and shows "id: 0()"
Have fun ^_^
Click to expand...
Click to collapse
Idk when i opened lgup it's only have 3 option refurbished, upgrade n fota update

Azs5165 said:
Idk when i opened lgup it's only have 3 option refurbished, upgrade n fota update
Click to expand...
Click to collapse
You didnt follow preparation correctly I guess?

netmsm said:
Some pictures of flashing my LMG820UM, unlocked from Sprint, into OPEN_CA 20j. In normal mode you cannot flash SPR_US to OPEN_CA which is shown in the pictures. But using this thread instruction it allows to flash, even it asks to change the model from SPR_US to OPEN_CA
Until performing the instructions, it shows the "id: 2(SPR_US)" on the Download Mode screen, but after that it cannot recognize the phone model id and shows "id: 0()"
Have fun ^_^
Click to expand...
Click to collapse
What OPID does it get assigned once you boot the device? OPEN_CA?

AsItLies said:
Hey nice! It's great to have options. I'm currently using us Open OP on my Sprint device (of course totc changed). It's working fine and not sure of any reason to change.
Although, if we do get a11 firmware available, that will change things for sure.
Thanks, nice work!
Click to expand...
Click to collapse
Like the a11 korean one?

cloud1250000 said:
You didnt follow preparation correctly I guess?
Click to expand...
Click to collapse
I had tried with my lmg850um9 sprint,i accidentally erase entire flash before but i successfull flash with other g8x em kdz but get opid missmatched

Azs5165 said:
Idk when i opened lgup it's only have 3 option refurbished, upgrade n fota update
Click to expand...
Click to collapse
i got the same problem, just 3 options

Just did this successfully, thanks OP. If yer only getting partial options on lgup, remember from the OP, you HAVE to change the UI file to be READ ONLY (do it in properties).
I didn't get the 'change model' pop up, but still worked, although device is still seen as 'um' not 'qm'. My serial # is missing (that's a simple edit in ftm), but the imei is there.
Definitely worked though, now have us op with april security patch.
Will take a few mins to get a root explorer to see what totc says... that should be interesting

AsItLies said:
Just did this successfully, thanks OP. If yer only getting partial options on lgup, remember from the OP, you HAVE to change the UI file to be READ ONLY (do it in properties).
I didn't get the 'change model' pop up, but still worked, although device is still seen as 'um' not 'qm'. My serial # is missing (that's a simple edit in ftm), but the imei is there.
Definitely worked though, now have us op with april security patch.
Will take a few mins to get a root explorer to see what totc says... that should be interesting
Click to expand...
Click to collapse
How to make it?srry i cant understand

alright, G8x Sprint succesfully crossflashed to OPEN CA

Azs5165 said:
Idk when i opened lgup it's only have 3 option refurbished, upgrade n fota update
Click to expand...
Click to collapse
Sebastian Thiago said:
i got the same problem, just 3 options
Click to expand...
Click to collapse
Azs5165 said:
How to make it?srry i cant understand
Click to expand...
Click to collapse
Follow preparation.
cloud1250000 said:
What OPID does it get assigned once you boot the device? OPEN_CA?
Click to expand...
Click to collapse
AsItLies said:
Will take a few mins to get a root explorer to see what totc says... that should be interesting
Click to expand...
Click to collapse
Actually it doesn't change OPID. By not flashing SID partitions we can bypass checking OPID and hence the error.
I checked it now it was OPEN_CA.
Azs5165 said:
I had tried with my lmg850um9 sprint,i accidentally erase entire flash before but i successfull flash with other g8x em kdz but get opid missmatched
Click to expand...
Click to collapse
Follow the steps in part C.

netmsm said:
Actually it doesn't change OPID. By not flashing SID partitions we can bypass checking OPID and hence the error.
I checked it now it was OPEN_CA.
Click to expand...
Click to collapse
curious how the sprint v50 will react to this.. I`ll try this guide when korean A11 gets release.. I'll let you know..
Also.. if it doesn`t change OPID you would get OPID mismatched error on boot.. so..

cloud1250000 said:
Also.. if it doesn`t change OPID you would get OPID mismatched error on boot.. so..
Click to expand...
Click to collapse
If SID partitions are flashed then yes it will throw OPID Mismatched Error. This is why we suggest using "Partition DL" flashing method, unchecking SID partitions.

netmsm said:
If SID partitions are flashed then yes it will throw OPID Mismatched Error. This is why we suggest using "Partition DL" flashing method, unchecking SID partitions.
Click to expand...
Click to collapse
yes but it has to generate new one with proper OPID no? when you load download mode now, does it still says id: 0? i doubt that

cloud1250000 said:
yes but it has to generate new one with proper OPID no? when you load download mode now, does it still says id: 0? i doubt that
Click to expand...
Click to collapse
That's right it generates the original OPID in download mode.
It is probable that some or all data related to OPID are stored in Modemsts partitions to which the SID partition bridges the OPID check function, in boot process. All that we do is to destroy the bridge.

netmsm said:
That's right it generates the original OPID in download mode.
It is probable that some or all data related to OPID are stored in Modemsts partitions to which the SID partition bridges the OPID check function, in boot process. All that we do is to destroy the bridge.
Click to expand...
Click to collapse
can you check which mcfg is used? (field test > mcfg status)