Develop Bugs

2016 version (new fingerprint scanner, combined sim/sd)

Hey guys,
It seems more and more people are receiving the new version of the P8000:
- Stock Android 6
- New fingerprint scanner that is moved slightly higher and is able to unlock phone from screen-off (I confirm this is working)
- Sim 2 is combined with the micro-sd (I haven't tried whether you can have them both in at the same time)
- Somethings new about the display, since people are reporting errors with it after flashing older roms.
Warning: do NOT flash other roms. We have no way to unbrick the soft bricks yet!
---
Other topics that refer to this version:
http://forum.xda-developers.com/elephone-p8000/general/rom-p8000-t3431571
http://forum.xda-developers.com/elephone-p8000/help/stock-rom-p8000b-t3434477
http://forum.xda-developers.com/elephone-p8000/general/p8000-version-announced-t3346848
---
For development:
- The phone does not come pre-rooted. We have no way to flash custom recovery yet. Any tips for getting root? I've tried such tools as Kingo and vRoot, they don't work.
- We need the blocks file (scatter file) for SP Flash Tools. MTKDroidTools reports "unknown rom structure". Any help? Would love to start working on this.
Looking forward to hearing from others who have this version/who can help me with these questions.
Thanks!
Emile

Nice! Can you provide a dump from /system and /boot maybe?

BlueFlame4 said:
Nice! Can you provide a dump from /system and /boot maybe?
Click to expand...
Click to collapse
I would, if I knew how to. Any pointers?

Emileh said:
I would, if I knew how to. Any pointers?
Click to expand...
Click to collapse
Sure thing. On a rooted device, go into adb shell.
Then use "mount" command to check which partitions are mounted. One should be "/dev/block/platform/mtk-msdc.0/by-name/system" or similar. Use "dd if=/dev/block/platform/mtk-msdc.0/by-name/system of=/storage/emulated/0/system.img bs=1M" to dump the system to the internal sdcard to the file "system.img". If adb complains that bs=1M is an invalid option, try again without that one. A system dump can take some time where you will not get any feedback, so be patient there
Do the same for boot. So "/dev/block/platform/mtk-msdc.0/by-name/boot" should be the way to go for the path. I cannot tell the definite pathes on Android 6.0 but I am rather sure they are more or less like this.
If you run into troubles, just ask

BlueFlame4 said:
Sure thing. On a rooted device, go into adb shell.
Then use "mount" command to check which partitions are mounted. One should be "/dev/block/platform/mtk-msdc.0/by-name/system" or similar. Use "dd if=/dev/block/platform/mtk-msdc.0/by-name/system of=/storage/emulated/0/system.img bs=1M" to dump the system to the internal sdcard to the file "system.img". If adb complains that bs=1M is an invalid option, try again without that one. A system dump can take some time where you will not get any feedback, so be patient there
Do the same for boot. So "/dev/block/platform/mtk-msdc.0/by-name/boot" should be the way to go for the path. I cannot tell the definite pathes on Android 6.0 but I am rather sure they are more or less like this.
If you run into troubles, just ask
Click to expand...
Click to collapse
Thank you for your great instructions! The problem is that we've yet to achieve root on this device. We don't have a custom recovery for this version of the P8000 yet and other 'standard' methods of rooting don't work for me.
(I'm pretty solid in shell, so I'll do this afterwards, but I guess root is actually the first step).
// Edit to say: it does not come pre-rooted

Since the elephone support on facebook didn't realize there are two different versions of the P8000 available, I still need a ROM to unbrick my phone.

flo1k said:
Since the elephone support on facebook didn't realize there are two different versions of the P8000 available, I still need a ROM to unbrick my phone.
Click to expand...
Click to collapse
Ok, we know that, but doesn't really help us
Can you write them an e-mail?

I will do
Edit: OK, see if there will be an answer.

Thank you flo1k!

I have e-mailed as well, and would like to post on the Elephone forum, but don't seem to have access (because of minimum post count, I guess)
Anyone willing to ask for a ROM for the new P8000 on the forum there?

ROM Dump
@BlueFlame4
I can provide ROM dump in two versions:
1) a dump from adress 0000 0000 to 9d80 0000 (apr. 2.5 GB in one file)
2) a readback generated with the scatter.txt of the 'old' 5.1 stock ROM (apr. 2.8 GB seperated in 23 files)

FrauHofrat said:
@BlueFlame4
I can provide ROM dump in two versions:
1) a dump from adress 0000 0000 to 9d80 0000 (apr. 2.5 GB in one file)
2) a readback generated with the scatter.txt of the 'old' 5.1 stock ROM (apr. 2.8 GB seperated in 23 files)
Click to expand...
Click to collapse
The second choice looks promising

Maybe a stupid question
where shall I upload the files - any preferred webspace?
I'm uploading the files - because they contain my NVRAM I send the link as PM as soon as the upload is finished

FrauHofrat said:
Maybe a stupid question
where shall I upload the files - any preferred webspace?
I'm uploading the files - because they contain my NVRAM I send the link as PM as soon as the upload is finished
Click to expand...
Click to collapse
Are you sure we're talking about the same version of the P8000? Cause as far as I know there isn't 5.1 available for this version... Right?
Just checking thank you for your help in any case!! Really looking forward to it.
// edit: ah, you just used the old scatter file. But does that one work for this version?

Emileh said:
Are you sure we're talking about the same version of the P8000? Cause as far as I know there isn't 5.1 available for this version... Right?
Click to expand...
Click to collapse
No, there is only one Firmware available - the mysterious P8000_6.0_20160516.
Btw, this Phone contains a new mainboard model "K06TS-L-V2.0.3" - the 'old' mainboard is moder "K05T...."
// edit: ah, you just used the old scatter file. But does that one work for this version?
Click to expand...
Click to collapse
No, it doesn't work resp. the phone boots with this firmware, but the LCD-driver is the wrong one - the display only shows coloured lines and blurry spots. And there are probabely some more bugs ....

FrauHofrat said:
No, there is only one Firmware available - the mysterious P8000_6.0_20160516.
Btw, this Phone contains a new mainboard model "K06TS-L-V2.0.3" - the 'old' mainboard is moder "K05T...."
No, it doesn't work resp. the phone boots with this firmware, but the LCD-driver is the wrong one - the display only shows coloured lines and blurry spots. And there are probabely some more bugs ....
Click to expand...
Click to collapse
But if the phone boots with the firmware, doesnt that mean that the scatter file of the regular P8000 works? Since it flashes the firmware correctly.

The problem is that I was not able to flash the 'readback files' to the faulty phone.
When selecting 'Only Download' at SP-Flashtool I got the error "PMT... must be download"
When selecting 'Firmware Upgrade" I got some BROM error code
In both cases I used the same scatter,txt which I used to 'readback' the firmware from the working phone
Actually I have to correct my statement in post #15:
I flashed the faulty phone with the last 5.1 stock ROM (160711) - with this stock ROM the phone boots up but LCD (and probably more things) is not working.

I have actually gotten alot further
You have the use the scatter.txt from Android 6.0, which works perfectly fine. I have been able to extract boot.img, system.img and recovery.img that way (using Readback in SP Flash Tools)
Which ones do you need?
They probably flash fine (only thing I've flashed so far are custom recoveries, and although my ported PhilZ starts, I havent gotten it to mount anything.)
A little warning: don't use anything that has anything to do with Android 5.1. Those scatter files don't work

These are great news!
"Which ones do you need?"
Probably all of them

Ok this contains the scatter file, preloader, system.img, boot.img and stock recovery.img
https://ehaffmans.stackstorage.com/index.php/s/uKGKCir0BociydU
You need SP Flash Tools v5, select the scatter file first, then deselect everything, and only select these 4 and manually select the correct files.
Btw, the name of the preloader file is wrong, don't worry. It came from this phone
I am of course not responsible for anything!
Can you guys please confirm this doesn't contain anything personal? Like personal files or IMEI or something. Thanks!

BND-L24 missing updater APP

I have posted this question attached in other threads, but it has not gotten any attention. So I am starting a new thread.
Please help. I find myself missing the "honor" health apps(these don't bother me too much ) and the System Updater app.
After formatting /data in TWRP and flashing a modified boot.img, I find that I am missing some apps. I have re-flashed stock boot and recovery and performed reset, but the missing apps are nowhere to be found.
I am hoping someone will post there list of stock packages(apps), so I can see what I am missing.
Code to list installed packages
Code:
adb shell pm list packages -f > "C:\android\Honor 7x\packages-list.txt"

Reserved

Thanks to @johncro13 for his help . POST
I now know that formating /data HAS removed several apps that were in /data/hw_init
Full list is in the attached txt file.
This now brings up a new problem with this situation. /data is not permitted access without root. and in recovery /data is encrypted, so no access there too.
If someone who is rooted would be so kind as to pull the hw_init folder and share it , That would be fantastic.
Code:
mkdir %userprofile%\Desktop\hw_init
adb pull /data/hw_init %userprofile%\Desktop\hw_init

mrmazak said:
If someone who is rooted would be so kind as to pull the hw_init folder and share it , That would be fantastic.
Code:
mkdir %userprofile%\Desktop\hw_init
adb pull /data/hw_init %userprofile%\Desktop\hw_init
Click to expand...
Click to collapse
Try this.

johncro13 said:
Try this.
Click to expand...
Click to collapse
very helpfull.
Now i need to see how to use this. There is a file called dataversion.txt that does not match my version.
the b130 , then b140 both patch some of the files, so might need to root, push the files, then unroot and force a manual update of the data b130 and b140

By the way, I obtained that data promptly after factory reset - without root.

johncro13 said:
By the way, I obtained that data promptly after factory reset - without root.
Click to expand...
Click to collapse
The boot.img from mine (b140) must have higher selinux security. Cause I just got permission denied, both trying to "ls" and "adb pull" . Then same permission denied when "adb push".
..I ended up flashing twrp so adb shell had full permission to push files to /data, then I ran the /data patch from the 140 update.. maybe I should have done the patches in sequence ,(b130, then b140).
Well without the patch, the updater app is back and finds the newest b150 update but fails to install it. Then when I patched it with b140 it says there is no update. I can force the update with firmware finder and it also failed. Need to start over again and hopefully it works this time after patching in order.
**UPDATE**
Re-pushed the hw_init folder from b101 and then modified the update script for both b130 and b140 to run the patch.p on HwOUC.apk, that is in the "update_BND-L24_hw_usa.zip" did not need the rest of the update as I as starting with b140 to start with, I just needed to patch the b101 files added up to the rest on my system.
But It is still missing something. Because update fails.
considering using the no-check recovery used to force oreo update.
OR
just sitting back and waiting for the full stock package , that I have read multiple times is scheduled to be released "within a week or two". Even though I saw that posted every few weeks, going all the way back to December.
**UPDATE**
I tried to update using the "BDN-Recovery_NO-CHECK" and still had same, failed to update condition.

My complete bootloader unlock and root guide.

So I just got this phone just for fun, it was 75 USD, and went straight to XDA to root it so i can remove some bloat etc. but holy moly i ended up have 10 tabs with different guides open, i have compiled what I did to get this phone rooted.
I want to thank everyone who made different threads about rooting and installing Magisk on this phone, i have read so many guides now so i cant remember their names!.
BUT THANK YOU!.
Let's get to it
Here is what I did for to unlock the bootloader, install magisk and root my Huawei P20 Lite ANE-LX1
First you need to install HiSuite: https://consumer.huawei.com/minisite/HiSuite_en/
and then install ADB and Fastboot drivers: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
(extract the platform-tools folder to the root of your C: drive)
Plug in your phone and let it install drivers.
Then you need to downgrade your firmware to 146 using Dload method, as DCU Client can't read the bootloader unlock code on newer firmwares.
I used "Huawei P20 Lite ANE-L21 Anne-L21 8.0.0.146(C432) Firmware Android 8.0.0 EMUI 8.0.0 05014YXX androidhost.ru.zip" (https://androidhost.ru/6ti)
When finished downloading, open the zip file, open software and copy the folder "Dload" to the root of your EXTERNAL SD CARD, not internal storage!.
Now take your phone and "dial" *#*#2846579#*#* go to Software Upgrade -> SdCard Upgrade and click OK.
Your phone should now begin installing the old firmware, when the phone first boots up, dont set it up, turn it off and hold Volume up + Power and select Wipe Data/Factory Reset, Wipe Cache, and then reboot.
With the phone booted, enable USB Debugging (Settings > System > About Phone > version number > Tap it 7 times to become developer, AND click OEM-Unlock, then go to Settings > System > Developer Options > USB Debugging).
Now we need to buy 4 credits from DC-Unlocker (4 Euro) ( https://www.dc-unlocker.com/buy ) when you have 4 credits on your account, go and download https://hcu-client.com/download/hcu-client-v1-0-0-0287/ Password: hcu
extract the contents of the zip to a folder called HCU in the root of your C: drive
Open up HCU.exe, type in your username and password (check your mail, the info will be there).
Grab your phone and dial *#*#2846579#*#*, go to Background Settings -> USB Port Settings -> Manufacture Mode and press close.
Plug in your phone and let it install drivers.
Open up HCU client, select Unlock, and then Read Bootloader Code.
when you have the code, save it!
Turn off your phone
Hold volume down and power, now we are in fastboot mode.
Open CMD and write:
CD C:\platform-tools
fastboot oem unlock YOUR UNLOCK KEY HERE
Accept the stuff and unlock your bootloader, your phone will be factory reset, and all your data lost if you dont have a backup.
Turn the phone off and on again, set it up, and go to settings -> System -> System update, and update, mine was ANE-LX1 8.0.0.162(C432)
Now re-enable USB Debugging option in Developer Options.
install Magisk Manager (https://github.com/topjohnwu/Magisk/releases/download/v18.0/Magisk-v18.0.zip)
Download patched_ramdisk.img (https://mega.nz/#!GWp1ia6R!xUcg_T_17v1ktlFQPq-Ujo4DRKfAg8E4-_k2J2zLO60)
and place it in the root of your phones internal storage
Open up Magisk Manager, press install -> install -> Patch Boot Image File -> find the patched_ramdisk.img and click OK.
Now open CMD and write:
CD C:\platform-tools>
adb pull /storage/emulated/0/download/patched_boot.img
Now you should have the patched_boot.img in your platform tools folder.
Turn off your phone, hold volume down and power to get to fastboot mode.
in CMD write:
CD C:\platform-tools>
fastboot flash ramdisk patched_boot.img
reboot your phone and check if magisk was installed correctly and check if you have root.
Hope this works for you!

Great guide. Just a tip instead of using cd C:\platform-tools you can shift+right click on the adb folder and click "open powershell here". Saves some time

Thank you for this, but I have a question about this part:
Then you need to downgrade your firmware to 146 using Dload method, as DCU Client can't read the bootloader unlock code on newer firmwares.
Click to expand...
Click to collapse
Mine is ANE-LX3, what would be the equivalent to 146 so that DC-unlocker can read it?

Yes, you just need to find a firmware for LX3, i dont think flashing a 64gb firmware on a 32gb device is smart.

dcduartee said:
Great guide. Just a tip instead of using cd C:\platform-tools you can shift+right click on the adb folder and click "open powershell here". Saves some time
Click to expand...
Click to collapse
I have tried that and PowerShell doesnt Work on my pc(i have replaced shift click shortcut so its CMD indtraf) and i wanted a noob proof way to make this work
And thanks.

Where could i find the correct firmware of ANE-LX1

Just use the address bar
brugernavn said:
I have tried that and PowerShell doesnt Work on my pc(i have replaced shift click shortcut so its CMD indtraf) and i wanted a noob proof way to make this work
And thanks.
Click to expand...
Click to collapse
Maybe you already know but I learned that you can just clic the address bar in a Windo(w)s system and write 'cmd' which is exactly the same as 'open a command prompt that starts in this very specific folder'.
E.g. in attachments.
Now I just want to know what firmware to downgrade to :/

LLoTE said:
Where could i find the correct firmware of ANE-LX1
Click to expand...
Click to collapse
Use the link in my guide.
lalovzg said:
Maybe you already know but I learned that you can just clic the address bar in a Windo(w)s system and write 'cmd' which is exactly the same as 'open a command prompt that starts in this very specific folder'.
E.g. in attachments.
Now I just want to know what firmware to downgrade to :/
Click to expand...
Click to collapse
Sweet thanks!.
Try and use this firmware:.
https://androidhost.ru/9V2

Using that as a reference I found one for my region I think (C69) that says:
Integrates Google security patches released in Apr 2018 for improved system security.
Click to expand...
Click to collapse
Is this April FullOTA a safe security patch to work with DC-u?
ANE-LX3C69CUSTC69
An another one big question: I am in the believe that my P20 lite is Single-SIM. Does it matter if that FullOTA (or any ROM/Update.app/etc) says DUAL-SIM? Should I look for the oldest Single-SIM??? or a Dual-SIM file would work just fine?

lalovzg said:
Using that as a reference I found one for my region I think (C69) that says:
Is this April FullOTA a safe security patch to work with DC-u?
ANE-LX3C69CUSTC69
An another one big question: I am in the believe that my P20 lite is Single-SIM. Does it matter if that FullOTA (or any ROM/Update.app/etc) says DUAL-SIM? Should I look for the oldest Single-SIM??? or a Dual-SIM file would work just fine?
Click to expand...
Click to collapse
If its single sim, you need a single sim firmware and just use a firmware under 150, you should be okay

Would someone like to pay for me cuz I don't got a way to pay i don't have any credit cards..i know this is stupid but im just a teenager and my parents wouldn't pay for it so here i am lol

@brugernavn
Bro your instructions are super perfect tuttorial very very BIG thankx
would know exactly the firmware that would go without a bootloader unlock hunger everywhere this Huawei P20 Lite firmware ANE-L21 Anne-L21 8.0.0.166 (C432)
The only thing is that which one is right where the to sdcard firmware into the dload folder and installs without problems
because of what I was looking for and so I made a mistake to link to the Huawei P20 Lite ANE-L21 Anne-L21 8.0.0.166 (C432) in format like This post forum
what i found for dual sim so all su with unlocked bootloader hurts me
PLEASE REPLY will be glad

HEKER510 said:
@brugernavn
Bro your instructions are super perfect tuttorial very very BIG thankx
would know exactly the firmware that would go without a bootloader unlock hunger everywhere this Huawei P20 Lite firmware ANE-L21 Anne-L21 8.0.0.166 (C432)
The only thing is that which one is right where the dam to sdcard firmware into the dload folder and installs without problems
because of what I was looking for and so I made a mistake to link to the Huawei P20 Lite ANE-L21 Anne-L21 8.0.0.166 (C432) in format like aky maš na forum
what i found for dual sim so all su with unlocked bootloader hurts me
PLEASE REPLY will be glad
Click to expand...
Click to collapse
Im sorry, i dont understand what you are writing

brugernavn said:
Im sorry, i dont understand what you are writing
Click to expand...
Click to collapse
i flashnig for sdcard firmware 146 for you link
i have must firmware 166 for sdcard
you helping my for firmware 166 for huawei p20 lite dual firmware 166(c432) flashing install sdcard for servis menu upgrade
identic 146 for 166 firmware
you understand my brother ?

HEKER510 said:
i flashnig for sdcard firmware 146 for you link
i have must firmware 166 for sdcard
you helping my for firmware 166 for huawei p20 lite dual firmware 166(c432) flashing install sdcard for servis menu upgrade
identic 146 for 166 firmware
you understand my brother ?
Click to expand...
Click to collapse
You first flash 146 firmware with Service menu.
Then unlock bootloader
Then update via the settings menu

brugernavn said:
You first flash 146 firmware with Service menu.
Then unlock bootloader
Then update via the settings menu
Click to expand...
Click to collapse
Bro 166 firmware for servis menu yes ? thankx you very much

thank you very much for your guide, brugernavn.:good:
I arrived without problems at the point: "Turn the phone off and on again, set it up, and go to settings -> System -> System update, and update, mine was ANE-LX1 8.0.0.162(C432)"
but the phone can not find updates ... (i before was in 150) but this isn't a problem.
My doubt is on how to install Magisk Manager (https://github.com/topjohnwu/Magisk/...gisk-v18.0.zip) .... with TWRP ?
Thank you again

Hey, to root my p20, flashing magisk via recovery, don't need ramimage, all works fine

how to do it
how to flashing magisk via recovery? (whit TWRP or not??) you can explain the passage?

cirovi said:
thank you very much for your guide, brugernavn.:good:
I arrived without problems at the point: "Turn the phone off and on again, set it up, and go to settings -> System -> System update, and update, mine was ANE-LX1 8.0.0.162(C432)"
but the phone can not find updates ... (i before was in 150) but this isn't a problem.
My doubt is on how to install Magisk Manager (https://github.com/topjohnwu/Magisk/...gisk-v18.0.zip) .... with TWRP ?
Thank you again
Click to expand...
Click to collapse
what software are you running now?

no signal - a2lite 4gb

Hi,
I did something wrong with my A2 Lite, i've updated the Magisk boot file from the Magisk app. Caused my phone to stop booting Android.
So i tried reflashing it with Mi Flash in EDL mode. That worked but i don't have any signal when i put a SIM in.
It shows my provider in settings so it recognizes the SIM but doesn't do anything with it.
Tried 10.0.13.0 manually and via Mi Flash = no signal
Tried 10.0.2.0 via Mi Flash = no signal
Loaded TWRP, switch A/B = no effect
Does anyone have a clue what i can do now?
Looks like the IMEI numbers are 0.

terrorsource said:
Looks like the IMEI numbers are 0.
Click to expand...
Click to collapse
I don't know how you got here, but it looks like some important stuff was overwritten.
The mobile network is probably blocking you due to the invalid IMEI...
This is typically something that is stored only in the phone's flash. I'm not sure you'll be able to recover the phone.

a1291762 said:
I don't know how you got here, but it looks like some important stuff was overwritten.
The mobile network is probably blocking you due to the invalid IMEI...
This is typically something that is stored only in the phone's flash. I'm not sure you'll be able to recover the phone.
Click to expand...
Click to collapse
Is it possible to write back the IMEI's if i have them?

terrorsource said:
Is it possible to write back the IMEI's if i have them?
Click to expand...
Click to collapse
It might be. In theory. You'd need to know the format of whatever was overwritten.

You can't rewrite the IMEI, I've have that issue before and I created a guide on how to fix it
https://forum.xda-developers.com/mi...-to-fix-efs-corruption-sim-card-t3928910/amp/
Enjoy ?
You can download the latest rom and install it (ignore the rom that's in the guide it is outdated, but the rest of the guide stays the same).

Noam5651 said:
You can't rewrite the IMEI, I've have that issue before and I created a guide on how to fix it
https://forum.xda-developers.com/mi...-to-fix-efs-corruption-sim-card-t3928910/amp/
Enjoy
You can download the latest rom and install it (ignore the rom that's in the guide it is outdated, but the rest of the guide stays the same).
Click to expand...
Click to collapse
Thanks, will check it out the next couple of days.
I do see some websites/youtube video's of people/apps claiming it is possible by re-writing the QCN file...
I do know where i made a mistake, i tried to manually install all files in an image folder, including flashing a not-so-good QCN file...

terrorsource said:
Thanks, will check it out the next couple of days.
I do see some websites/youtube video's of people/apps claiming it is possible by re-writing the QCN file...
I do know where i made a mistake, i tried to manually install all files in an image folder, including flashing a not-so-good QCN file...
Click to expand...
Click to collapse
https://forum.xda-developers.com/mi-a2-lite/how-to/sim-network-solution-alternatively-t3914161
if this doesn't work ,pm me

nikoman1987 said:
https://forum.xda-developers.com/mi-a2-lite/how-to/sim-network-solution-alternatively-t3914161
if this doesn't work ,pm me
Click to expand...
Click to collapse
Works partially!
I cannot install the latest "QPST_2.7.453" due to "Installation errors".
If i try "QPST_2.7.422" i can restore the created QCN but i cannot select "Enable Multi-SIM" and it only restores IMEI-1

nikoman1987 said:
https://forum.xda-developers.com/mi-a2-lite/how-to/sim-network-solution-alternatively-t3914161
if this doesn't work ,pm me
Click to expand...
Click to collapse
Works now! both IMEI's are now shown in the settings.
IMEI SV is still at 0 though.
Your manual needs some work though.
Latest QFI: https://androidmtk.com/download-qualcomm-flash-image-loader-qfil
Enable Multi-SIM is not in all versions. I've used v2.0.1.9
Restoring QCN with this version can take a while. DO NOT USE PC until done!
8. daisy_sprout:/ $ su
/system/bin/sh: su: not found
127|daisy_sprout:/ $ setprop sys.usb.config rndis,diag,adb
setprop: failed to set property 'sys.usb.config' to 'rndis,diag,adb'
16. is not "QPST.exe" but "QFIL.exe"
20. 21. 22. not needed. directly went to 23 from 19.
stopped at 27, rebooted phone, IMEI's are back. Did not proceed with the manual any further.

terrorsource said:
Works now! both IMEI's are now shown in the settings.
IMEI SV is still at 0 though.
Your manual needs some work though.
Latest QFI: https://androidmtk.com/download-qualcomm-flash-image-loader-qfil
Enable Multi-SIM is not in all versions. I've used v2.0.1.9
Restoring QCN with this version can take a while. DO NOT USE PC until done!
8. daisy_sprout:/ $ su
/system/bin/sh: su: not found
127|daisy_sprout:/ $ setprop sys.usb.config rndis,diag,adb
setprop: failed to set property 'sys.usb.config' to 'rndis,diag,adb'
16. is not "QPST.exe" but "QFIL.exe"
20. 21. 22. not needed. directly went to 23 from 19.
stopped at 27, rebooted phone, IMEI's are back. Did not proceed with the manual any further.
Click to expand...
Click to collapse
We'll I have never had an issue with losing my IMEI , the manual is not mine ,I'm glad that it worked!

[Guide] Make the Korean Q Great Again [relocalise, volte, wowifi, debloat and more]

IF YOUR BOOTLOADER IS NOT ALREADY UNLOCKED, THIS GUIDE IS NOT FOR YOU.
READ EVERYTHING AT LEAST ONCE BEFORE PROCEEDING!
THIS GUIDE WORKED GREAT FOR AT LEAST 3 PERSONS, THIS DOESN'T MEAN IT WILL WORK ON YOUR PHONE.
This guide exist in case the ULM Q never released
This guide should do the following :
relocalize to your country (I'm only providing the files for canada, usa and eu)
Root and TWRP (useful if any custom roms get released)
debloating
volte/vowifi/vilte/viwifi
Very Good battery (see screenshots down below)
mute shutter camera
4k 60fps video recording (?some people said it wasn't available on the korean Q?)
wifi tethering
and more
WHAT'S NOT WORKING FOR ME :
lg smartworld : meaning no lg app update.. which can lead to the next problem
Drag down for search : working only if you do not update the google app
What you need:
1 to 2hrs of free time
Working QFIL with minimal knowledge
Working Fastboot on your pc (See spoilers)
I did NOT manage to make fastboot work on my amd ryzen pc (3600)
here's what I tried :
- multiple fastboot drivers
(fastboot was kinda working.. now it just never load any driver)
- plugged in a usb 3.0 hub
- FWUL : https://forum.xda-developers.com/an.../live-iso-adb-fastboot-driver-issues-t3526755
(the latest version as of 2020-11-25 couldn't even boot on this pc...)
- ubuntu
(crashed the phone to a gray screen)
- all my usb ports : 2, 3 and 3.1​ What I didn't try but could work for you:
- plugged in a usb 2.0 hub
- linux mint?​
Soo... what did I do? I went back to my good ol' intel pc running windows 10 worked like a charm.
Click to expand...
Click to collapse
Also, this guide assume you had working volte/vowifi on your phone at some point...
Because, you will need the carrier folder from the /oem/op/ folder.. should look like this : open_us, vrz_us, open_ca..
Or you will need to retrieve it from your working firmware...
I'll be providing :
- Android 10 - G7 - OPEN_CA (Canadian operator folder) (What I'm using on my phone right now)
- Android 9 - V35 - OPEN_US (ULM/GFi) (Confirmed working by @cmrntnnr)
- Android 10 - G7 - OPEN_EU (untested) (thanks @vlad48)
!!!!!! Before crossflashing to the korean kdz !!!!!!
------------------------------------------------------------------------
Crossflashing can break stuff sometime.. it is advised to do a full backup of your phone using https://github.com/bkerler/edl
if you're feeling lucky and do not want to do a full backup... you should still use qfil to atleast backup the following VITAL partitions : Fsg, modem, modemst1&2, ftm
STORE THOSE FILES PRECIOUSLY
------------------------------------------------------------------------
File you need to download :
To your phone SDCARD :​
OPEN_CA or OPEN_US or OPEN_EU (untested) (Decompress this file, delete the zip)
OPEN_CA is too big, I had to delete apks that weren't from my carrier. (Bell)
(open_ca/apps/ -> kept only bell apks)
debloated-priv-app-RENAME-ME.zip (Decompress this file, delete the zip)
debloated-app-RENAME-ME.zip (Decompress this file, delete the zip)
twrp-installer-v3.3.1-v35_a.zip
Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip
Magisk
(OPEN_EU only) : voenabler-v1.8.zip
​To your pc:​
vbmeta.img
30b_boot_magisk.img
30b_abl.bin (shouldn't be needed, but provided as backup)
Korean Q 30b (I went with LGU_KR since the other one weren't available back then)
The V35 engineering abl you got from here : https://forum.xda-developers.com/lg-v35/development/bootloader-unlock-root-instruction-t4052145
This file was renamed to engabl.bin in this guide​
You need to use SOLID EXPLORER, not esfile or any other since I can not guaranteed it will apply the correct permission to the files and folder.
LGUP > Flash V350N30b_00_LGU_KR_OP_1015.KDZ using partition DL, select everything except FTM
Let the phone boot for the first time and reach setup screen
LGUP > refurbish phone using the kdz (this should fix potential nt error when booting the phone, it did for me)
Let the phone boot for the first time and setup the phone quickly so you can install app. (no lock or fingerprint)
Patching vbmeta to edit the operator/carrier information & patching boot for magisk/root
QFIL > partition manager > abl_a > read, store that file and name it : needed_abl.bin
How to retrieve the file: WIN+R , %AppData%/Qualcomm/QFIL , enter, pick right folder, save and rename bin file​
QFIL > partition manager > abl_a > load > engabl.bin (for fastboot)
QFIL > partition manager > abl_b > load > engabl.bin (for fastboot) (Optional)
This is useful in case you need fastboot in the future, simply boot twrp then change slot from a to b and reboot.
To switch back from fastboot : fastboot --set-active=a​
reboot the phone using vol- + power
command :
Code:
fastboot --disable-verity --disable-verification flash vbmeta_a vbmeta.img
fastboot oem edl
QFIL > partition manager > abl_a > load > needed_abl.bin
QFIL > partition manager > boot_a > load > boot_magisk.img
reboot by holding vol- + power
[*]
Click to expand...
Click to collapse
Reboot to system, Install magisk manager and solid explorer
Start magisk manager and let it reboot your phone
magisk > modules > install from storage > twrp-installer-v3.3.1-v35_a.zip
SOLID EXPLORER > copy the carrier folder to the oem/op/ partition ('OPEN_CA' in my case)
SOLID EXPLORER > edit oem/op/cust_path_mapping.cfg and replace LGU_KR with OPEN_US ('OPEN_CA' in my case)
If you're still getting nt error at boot, you'll have to fix it in order to make the phone load open_us..
try adding a second line like this :
FFFFFF,84=/oem/OP/OPEN_US
If this doesnt do it, you'll have to share your nt error in the comment.
Click to expand...
Click to collapse
SOLID EXPLORER > Rename the folder /oem/op/LGU_KR to LGU_KRori (this will make your phone lag/glitch/freeze real quick.. proceed with the next step ASAP)
Quickly go in magisk and use the reboot menu to get to twrp. (reboot to recovery)
Format data
Reboot to TWRP/recovery
Flash Magisk-v21.1.zip, if it doesn't flash, reboot using the reboot menu to TWRP/recovery again until it works. (no red text)
Flash Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip
Reboot to system
if the vowifi toggle is not working for you
For OPEN_CA/OPEN_US :
SOLID EXPLORER > move debloated-priv-app-RENAME-ME to /oem/op/priv-app/
SOLID EXPLORER > Rename the new folder to OPEN_US or OPEN_CA
Reboot
Click to expand...
Click to collapse
FOR OPEN_EU : (these steps are from the v40 community telegram, Quote from Lucky)
magisk > modules > install from storage > voenabler-v1.8.zip
If you transplant the KR OP with OPEN_EU, and are based in EU, this module should add the props that enables the VoLTE and VoWifi options.
Only if this fails, do you need to tinker with the xml files.
Click to expand...
Click to collapse
Optional.
Adding back missing lg apps (I provide QMemo and LG Weather)
you can either install manually the apk from debloated-app-RENAME-ME
or
move the folder to oem/op/app/ and rename it OPEN_CA or OPEN_US
Click to expand...
Click to collapse
Enable LGMessage over Google message and add back LGFMRadio (you'll need to uninstall any sms app you might have installed.. like google message or fb messenger(if used for sms))
Solid Explorer
edit this file /oem/op/open_us/config/custom_apk_list.cfg
change the sign on the following lines (from - to + and + to -)
-com.lge.fmradio:/system/product/priv-app/LGFmRadio
-com.android.mms:/system/product/priv-app/LGMessage
-/system/app/SmartMessagingEngine
+com.google.android.apps.messaging:/system/app/Messages
Example
-/system/app/SmartMessagingEngine
to
+/system/app/SmartMessagingEngine
Reboot
Click to expand...
Click to collapse
Do not forget to enable developer option and adb AND
Plug you phone in computer, open adb shell and type su
on the phone, grant root.
It is useful to have a root shell in case the phone is stuck while booting (not boot looping)
you can also just reboot to twrp and undo your modification from there.
Click to expand...
Click to collapse
Thanks to everyone patient enough to answer my questions and who did provide most of the solution for this guide:
vlad48, Lucky, azitlies, xsavi, kaneorotar and many more..

Thanks for the guide

alonzo_ama26 said:
Thanks for the guide
Click to expand...
Click to collapse
No prob!
Added OPEN_EU files, but they are untested.. no clue if everything will work... Some people in the v40 community got it to work
Good luck everyone

I've completed all the steps (except for lg weather) and I didn't notice anything different in call features until I saw the description of the international roaming setting referenced "outside of US PR etc." instead of "outside of foreign territory or whatever" which indicates a success.
Then I Applied the vomaster.zip from somewhere else (prob the same thing as the OP's not sure) and flipped on wificalling on the settings and got the setup prompt for wificalling from my carrier and later a "wifi setup's been completed" notification, so I guess things are finally good again. Unfortunately RCS doesn't seem to want to cooperate either way =\
Not sure why I did it because korean q on its own was usable, but I did it it anyway and it is nice, performance feels better too but this could be because I went from LG firmware to open_us. Both the incoming and outgoing calls and texts feel much snappier as well and doesn't take 5 seconds to go anywhere. Also it doesn't ask me whether I want to listen to the call recording or not at the end of every phonecalls so that's nice. thank you
-edit
one question, is there any way I can use the korean AOD's? I liked the one that shows calendar and time.

issc said:
I've completed all the steps (except for lg weather) and I didn't notice anything different in call features until I saw the description of the international roaming setting referenced "outside of US PR etc." instead of "outside of foreign territory or whatever" which indicates a success.
Then I Applied the vomaster.zip from somewhere else (prob the same thing as the OP's not sure) and flipped on wificalling on the settings and got the setup prompt for wificalling from my carrier and later a "wifi setup's been completed" notification, so I guess things are finally good again. Unfortunately RCS doesn't seem to want to cooperate either way =\
Not sure why I did it because korean q on its own was usable, but I did it it anyway and it is nice, performance feels better too but this could be because I went from LG firmware to open_us. Both the incoming and outgoing calls and texts feel much snappier as well and doesn't take 5 seconds to go anywhere. Also it doesn't ask me whether I want to listen to the call recording or not at the end of every phonecalls so that's nice. thank you
-edit
one question, is there any way I can use the korean AOD's? I liked the one that shows calendar and time.
Click to expand...
Click to collapse
odd! you really shouldn't have to flash that vomaster.zip at all if you're located in the US.. honestly.. I don't even know if rcs is available in canada and I'm really not sure how to test this feature.. You might have to toggle wifi calling again if you got the wifi calling activation success notification.. it was the case on my friend phone..
Just to confirm...
volte/vowifi working?
ulm or awm?
carrier?
Looks like the calendar is available with the open_ca files... not sure for the open_us.. sorry..

[ATTACH

cloud1250000 said:
The V35 engineering abl you got from here : https://forum.xda-developers.com/lg-v35/development/bootloader-unlock-root-instruction-t4052145
This file was renamed to engabl.bin in this guide​
Click to expand...
Click to collapse
That file is a zip file with two different files in it, do you mean to rename this zip file to engabl.bin?

After step 5 I started to get some weird outputs.
fastboot.exe oem edl
FAILED (Status read failed (Too many links))
fastboot: error: Command failed
Click to expand...
Click to collapse
Seems like that output is normal because I have the rom rooted and twrped right now but I did have to change the active slot to B at this point because otherwise QFIL wasn't able to read the partitions afterwards. Oddly enough that was the only change I had to make, every other command worked as is referencing abl_a even though I changed the active slot to B (and when I flipped the steps to target slot B instead I just got bootlooped).
Everything's looking good so far. I had not been able to setup twrp on this phone so that's welcome. Hotspot wasn't working on Oreo either so that's another good improvement at least for me. Hopefully, this update ends up being a little bit more stable than Pie.

rpgdev said:
That file is a zip file with two different files in it, do you mean to rename this zip file to engabl.bin?
Click to expand...
Click to collapse
omg no, pick one of the 2 files and rename it to engabl.bin

Blad2301 said:
[ATTACH
Click to expand...
Click to collapse
??????

rpgdev said:
After step 5 I started to get some weird outputs.
Seems like that output is normal because I have the rom rooted and twrped right now but I did have to change the active slot to B at this point because otherwise QFIL wasn't able to read the partitions afterwards. Oddly enough that was the only change I had to make, every other command worked as is referencing abl_a even though I changed the active slot to B (and when I flipped the steps to target slot B instead I just got bootlooped).
Everything's looking good so far. I had not been able to setup twrp on this phone so that's welcome. Hotspot wasn't working on Oreo either so that's another good improvement at least for me. Hopefully, this update ends up being a little bit more stable than Pie.
Click to expand...
Click to collapse
sometime, with both fastboot and qfil/edl.. you need multiple try to get them working

cloud1250000 said:
omg no, pick one of the 2 files and rename it to engabl.bin
Click to expand...
Click to collapse
that's somewhat ambiguous, I ended up putting the abl_a in the a slot and the abl_b in the b slot. Not sure if they're interchangeable or if that's the reason why I experienced the issue I experienced. Shouldn't be but who knows.

I'm noticing that locking the screen takes a while using double tap. At least a second or more before the phone responds and actually locks the screen, is anyone else experiencing this?

rpgdev said:
I'm noticing that locking the screen takes a while using double tap. At least a second or more before the phone responds and actually locks the screen, is anyone else experiencing this?
Click to expand...
Click to collapse
that's odd mine is almost instantly..

cloud1250000 said:
that's odd mine is almost instantly..
Click to expand...
Click to collapse
Apparently it was due to my launcher, they're having some issues with that gesture on Android 10.
The Korean Q is solid, I'm surprised that it's performing better than Pie on this phone. Thanks for doing this guide. Anyways, I still get the camera shutter sound any idea as to why? Also, is there a way to disable the vibration for the fingerprint reader when the read is successful? I managed to do it for Oreo but haven't found a way to do it for Q

rpgdev said:
Apparently it was due to my launcher, they're having some issues with that gesture on Android 10.
The Korean Q is solid, I'm surprised that it's performing better than Pie on this phone. Thanks for doing this guide. Anyways, I still get the camera shutter sound any idea as to why? Also, is there a way to disable the vibration for the fingerprint reader when the read is successful? I managed to do it for Oreo but haven't found a way to do it for Q
Click to expand...
Click to collapse
shutter is muted when I'm on vibration mode

cloud1250000 said:
shutter is muted when I'm on vibration mode
Click to expand...
Click to collapse
Ah, I thought it disabled it on all modes. I didn't get it on vibration. Would be nice to disable it on every mode.

Right the thing with the korean firmware usually is.. it's not disabled even in silent mode lol

cloud1250000 said:
Right the thing with the korean firmware usually is.. it's not disabled even in silent mode lol
Click to expand...
Click to collapse
I see, do you happen to know where is the camera shutter sound now? It used to be \system\media\audio\ui\ but it seems that dir was removed on A10.

cloud1250000 said:
odd! you really shouldn't have to flash that vomaster.zip at all if you're located in the US.. honestly.. I don't even know if rcs is available in canada and I'm really not sure how to test this feature.. You might have to toggle wifi calling again if you got the wifi calling activation success notification.. it was the case on my friend phone..
Just to confirm...
volte/vowifi working?
ulm or awm?
carrier?
Looks like the calendar is available with the open_ca files... not sure for the open_us.. sorry..
Click to expand...
Click to collapse
I don't know how to check for volte working, but vowifi is def working at my work with ****ty at&t signals.
awm -> ulm -> korean q.
I get advanced chat features enabled but nothing works =/ maybe its fixable with googling but im reasonably happy with my phone atm, minus lgpay not being accessible for v35 and v30s outside of korea =\

Has anyone passed safetynet using this rom? Some pointers would be appreciated.