Database Develop

HELP! I can boot into DOWNLOAD mode only, how to re-flash to oero?

STORY: My TA-1004 autoupdate to Android Pie on 22Dec after I turn off my phone to charge battery.
and I follow this " https://forum.xda-developers.com/nokia-8/development/android-9-0-pie-patched-boot-img-t3875977 " to try flash "fastboot flash boot "NB-01-551-b05-Magisk-TWRP" for flash TWRP and magisk to my TA-1004 pie. and I stuck on "nokia logo" after flash, someone said "Factory reset" , I try to use "wipe>format data" in TWRP, until now, I can boot in to download mode only.
I also try this "https://forum.xda-developers.com/nokia-8/how-to/guide-restore-nokia-to-stock-t3867646 "
to restore to oreo and stuck on "Next is greyed out, click on "Edit Phone Information", you will get an error message after a while, clik on OK, BUT Next is still greyed" . Can anyone help me please?

Please check that you have the correct fastboot drivers installed. Open Windows Device manager, and check the properties of your Fastboot device. Do you see HMD Global as the manufacturer? If not, the drivers may not be correct and you should install the Nokia drivers.

singhnsk said:
Please check that you have the correct fastboot drivers installed. Open Windows Device manager, and check the properties of your Fastboot device. Do you see HMD Global as the manufacturer? If not, the drivers may not be correct and you should install the Nokia drivers.
Click to expand...
Click to collapse
thx for reply first,
I can check "Fastboot Device" in Windows Device manager , HMD Global as the manufacturer.
I can check "fastboot devices" by adb/fastboot.exe

kelvin31 said:
thx for reply first,
I can check "Fastboot Device" in Windows Device manager , HMD Global as the manufacturer.
I can check "fastboot devices" by adb/fastboot.exe
Click to expand...
Click to collapse
It should work in that case. Give a try to the NOST tool shared in the Nokia 8 forums itself.

singhnsk said:
It should work in that case. Give a try to the NOST tool shared in the Nokia 8 forums itself.
Click to expand...
Click to collapse
NOST is it means Nokia OST (Online Service Tool) latest version and I need download android pie rom first?

kelvin31 said:
NOST is it means Nokia OST (Online Service Tool) latest version and I need download android pie rom first?
Click to expand...
Click to collapse
NOST" - short for "No Service Tool"
https://forum.xda-developers.com/no...t-improved-version-ost-la-6-0-4-v0-4-t3875574
You should use the existing NB0 which you have for the Nokia 8. I think it is on Oreo only. I hope you do have it.

singhnsk said:
It should work in that case. Give a try to the NOST tool shared in the Nokia 8 forums itself.
Click to expand...
Click to collapse
singhnsk said:
NOST" - short for "No Service Tool"
https://forum.xda-developers.com/no...t-improved-version-ost-la-6-0-4-v0-4-t3875574
You should use the existing NB0 which you have for the Nokia 8. I think it is on Oreo only. I hope you do have it.
Click to expand...
Click to collapse
THx
let me study it first,
thank you very much

singhnsk said:
NOST" - short for "No Service Tool"
https://forum.xda-developers.com/no...t-improved-version-ost-la-6-0-4-v0-4-t3875574
You should use the existing NB0 which you have for the Nokia 8. I think it is on Oreo only. I hope you do have it.
Click to expand...
Click to collapse
hello, I m stuck on unlock_critical, do you have any idea?
{
"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"
}

kelvin31 said:
hello, I m stuck on unlock_critical, do you have any idea?
Click to expand...
Click to collapse
You need to be flashing the actual unlock.bin file you used to unlock the Nokia 8. As you see in your CMD window, the command did not work out.
Make sure you're CMDing in the directory of your unlock file. Then send the command
Code:
fastboot flash unlock UnlockFile.bin
Remember to replace UnlockFile.bin with the name of actual unlock file in your PC.

singhnsk said:
You need to be flashing the actual unlock.bin file you used to unlock the Nokia 8. As you see in your CMD window, the command did not work out.
Make sure you're CMDing in the directory of your unlock file. Then send the command
Code:
fastboot flash unlock UnlockFile.bin
Remember to replace UnlockFile.bin with the name of actual unlock file in your PC.
Click to expand...
Click to collapse
unlock.bin is it provide by HMD that one?
I have receive my nokia 8 unlock bootloader file before by HMD,
name called unlock.key
is it this one? should I rename it to unlock.bin ?
thank you

kelvin31 said:
You need to be flashing the actual unlock.bin file you used to unlock the Nokia 8. As you see in your CMD window, the command did not work out.
Make sure you're CMDing in the directory of your unlock file. Then send the command
unlock.bin is it provide by HMD that one?
I have receive my nokia 8 unlock bootloader file before by HMD,
name called unlock.key
is it this one? should I rename it to unlock.bin ?
thank you
Click to expand...
Click to collapse
Yes, that's the one. You don't have to rename it. Just pass it the way you did earlier.
fastboot flash unlock unlock.key
When it gets accepted, then run:
fastboot flashing unlock_critical

singhnsk said:
Yes, that's the one. You don't have to rename it. Just pass it the way you did earlier.
fastboot flash unlock unlock.key
When it gets accepted, then run:
fastboot flashing unlock_critical
Click to expand...
Click to collapse
its work,
I need to flash unlock.key again even I unlocked my bootloader in september.
but I need flash again after auto update..
I also fastboot flashing unlock_critical, work too.
but got another problem.....
NOST tool error code: 0xa24b
ERROR= BATTERY_VOLTAGE_TOO_LOW_FAIL (0xA24B).
I can't charge or very very slow maybe.
I charge it over 1 hour still lower than NOST tool requirement(30%)...
my TA-1004 can not power off since first flash fail....
I keep saw "download mode" over light and I can't power off...
I did try volup + power, it turn off 2 sec and auto start again boot into download mode...
how can I force power off it?
thank you

kelvin31 said:
its work,
I need to flash unlock.key again even I unlocked my bootloader in september.
but I need flash again after auto update..
I also fastboot flashing unlock_critical, work too.
but got another problem.....
NOST tool error code: 0xa24b
ERROR= BATTERY_VOLTAGE_TOO_LOW_FAIL (0xA24B).
I can't charge or very very slow maybe.
I charge it over 1 hour still lower than NOST tool requirement(30%)...
my TA-1004 can not power off since first flash fail....
I keep saw "download mode" over light and I can't power off...
I did try volup + power, it turn off 2 sec and auto start again boot into download mode...
how can I force power off it?
thank you
Click to expand...
Click to collapse
You can power off the phone from the stock recovery or TWRP. That is, if you are able to boot into any of them. If you have the stock recovery file, then flash it to the phone. After that force reboot it and continue to hold the keys and it should go into recovery mode. The phone will essentially start faster in recovery mode. Or you can also choose the "Power off" option in recovery to power off the phone.
If you cannot get into recovery, then you cannot power it off. And in that case you will have to bear this slow charge only. Just plug it into a wall charger and leave it for a few hours. You can then check the battery capacity after connecting to the PC and sending the following command:
Code:
fastboot oem battery getcapacity
Start NOST and flash the phone if it is higher than the required

singhnsk said:
You can power off the phone from the stock recovery or TWRP. That is, if you are able to boot into any of them. If you have the stock recovery file, then flash it to the phone. After that force reboot it and continue to hold the keys and it should go into recovery mode. The phone will essentially start faster in recovery mode. Or you can also choose the "Power off" option in recovery to power off the phone.
If you cannot get into recovery, then you cannot power it off. And in that case you will have to bear this slow charge only. Just plug it into a wall charger and leave it for a few hours. You can then check the battery capacity after connecting to the PC and sending the following command:
Code:
fastboot oem battery getcapacity
Start NOST and flash the phone if it is higher than the required
Click to expand...
Click to collapse
THanks for help.
I charge it over 10 hrs, I did, I can flash NB1-488B Oreo 8.1 back, I can use my phone right now, thank you very much

[Superseded] Crossflash US Unlocked Pie to your Bootloader Unlocked V40

SUPERSEDED: Go Here​
Prerequisites:
V35 Engineering Bootloader flashed to your device (Stock bootloader will NOT work for this)
USB 2.0 (USB 3.x does not work well with ADB or Fastboot)
The V40 Pie Conversion Tool
Be in fastboot mode before attempting this
Patience
ADB and Fastboot DRIVERS. Platform tools are already included in the archive
Windows. The tool is not designed for Linux.
This will NOT sim unlock your phone[/CENTER]
Note: I'm not responsible for any bricks that come about from using this tool. Once you crossflash, there's NO going back unless you have backups of your partitions, or a KDZ specifically for your device. I'm going to say this again, DO NOT use USB 3.x while attempting this. You will run into errors. You won't see anything for a little bit when it gets to flashing system_a and vendor_a because it has to load those images into ram.
Download the tool: Google Drive
1. Download the archive and unzip the tool.
2. Navigate to the folder you unzipped the tool to.
3. Enter the folder and inside the folder you should find "V40PIECONVERSION.cmd". Ignore the one with the "Stock Boot" at the end. All it does is flash the stock boot image instead of the TWRP that is required to do this.
4. Execute the batch file and follow the instructions. When the batch file is done, Pie will be flashed, but it will not boot due to encryption. We're going to disable that.
5. Boot TWRP by performing a master reset. To perform a master reset: Press and hold Vol- and Power. When you see the "V40 ThinQ" logo release the power button and quickly press back down. Keep holding Vol- and Power until you see a factory reset screen. Finally, follow the prompts (yes) and you should be in TWRP.
TWRP Instructions​
Head over to the wipe menu and format data (to remove encryption).
Next, head over to mount and mount vendor. Mount ONLY vendor.
Now, open a command prompt, navigate to the folder where you extracted the tool, and open a command prompt inside the folder (Type "CMD" in File Explorer's Address Bar)
{
"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"
}
Execute the adb command:
Code:
adb pull /vendor/etc/fstab.judypn
Edit the file (fstab.judypn) in your favorite text editor and on the /data mountpoint change "forceencrypt" to "encryptable".
Save and Close the file and push the file back with the command:
Code:
adb push fstab.judypn /vendor/etc
Now that encryption is disabled, you NEED to flash back the ORIGINAL boot image that's included with the tool. In order to do that, we need to get back into fastboot.
To get back into fastboot, we need to: Make sure USB is still plugged into the phone. Press and hold VOL+ (Or vol up). Power off the phone (Via TWRP reboot menu) while still holding vol+. Keep holding VOL+ until you see download mode flash for a brief second and you should be in fastboot. The fastboot you see now isn't the V35 Engineering Bootloader. It's the stock pie bootloader. Wiping the laf_a partition allows access to fastboot on devices that are locked (Nearly all US Carriers).
Finally, run the commands:
Code:
fastboot flash boot_a boot_a.image
and
Code:
fastboot format userdata
You should run into an "encryption unsuccessful" screen. Just hit reset phone. You may have to reboot once or twice to get to the setup screen.
For those of you that want root, here's a patched Magisk boot image: Google Drive
You can flash it by running the command:
Code:
fastboot flash boot_a magisk_patched.img
Make sure you open a command prompt in the directory you downloaded the image in. If you don't have adb and fastboot in your environment path, just place it in the V40PIEConversion folder and flash it from there.

How do you get the v35 bootloader on stock Att ?

Evilmonstertruck said:
How do you get the v35 bootloader on stock Att ?
Click to expand...
Click to collapse
Contact @vbenkovskyy on Telegram. He is an awesome guy. Of course, it isn't free, but his prices are better.

Confirmed working - thanks Xsavi for an excellent guide!

Would this method work on the T-Mobile variant? Is there a fee [anywhere]?
---------- Post added at 04:16 PM ---------- Previous post was at 04:12 PM ----------
Can someone comment on this?

avaie said:
Would this method work on the T-Mobile variant? Is there a fee [anywhere]?
---------- Post added at 04:16 PM ---------- Previous post was at 04:12 PM ----------
Can someone comment on this?
://youtu.be/nSeqIfQeWi4
Click to expand...
Click to collapse
No T-Mobile is not supported

avaie said:
Would this method work on the T-Mobile variant? Is there a fee [anywhere]?
---------- Post added at 04:16 PM ---------- Previous post was at 04:12 PM ----------
Can someone comment on this?
://youtu.be/nSeqIfQeWi4
Click to expand...
Click to collapse
Ainz is right. You'll end up with a brick if anything.

Confirmed working on my att variant. ? Thanks again for the great guide ?

pp342261 said:
Confirmed working on my att variant. Thanks again for the great guide
Click to expand...
Click to collapse
You are very welcome! Feel free to contact me if you run into any issues.
On the plus side, your b-slot is untouched throughout all of this, so you can use that to re-root or flash backups should something go wrong, or update. Enjoy the pie.

Xsavi said:
You are very welcome! Feel free to contact me if you run into any issues.
On the plus side, your b-slot is untouched throughout all of this, so you can use that to re-root or flash backups should something go wrong, or update. Enjoy the pie.
Click to expand...
Click to collapse
Will this work on the LG V40 International?

rmgibbs1861 said:
Will this work on the LG V40 International?
Click to expand...
Click to collapse
Yes it will.

rmgibbs1861 said:
Will this work on the LG V40 International?
Click to expand...
Click to collapse
One more question, How will further updates be done after cross flashing? Thank you!

rmgibbs1861 said:
One more question, How will further updates be done after cross flashing? Thank you!
Click to expand...
Click to collapse
By flashing System, Vendor, and boot.

Very confusing. Which variants of V40 this is going to work for?

How to get the v35 engineering bootloader on the phone the only method ive heard about is through octoplus jtag?

twoxa said:
Very confusing. Which variants of V40 this is going to work for?
Click to expand...
Click to collapse
Well it worked for all US Carriers except for T-Mobile

had my sprint v40 bootloader unlocked from octoplus and tried this cause i hate sprint SW (activation screen).it flashed everything from batch file fine but when i went to boot into twrp it booted into normal recovery with the rainbow circle "erasing" then rebooted into os but it was all korean and the android version was 8.1. wtf lol? trying it again now, yes im using "V40PIECONVERSION" not the stock one.

jass65 said:
had my sprint v40 bootloader unlocked from octoplus and tried this cause i hate sprint SW (activation screen).it flashed everything from batch file fine but when i went to boot into twrp it booted into normal recovery with the rainbow circle "erasing" then rebooted into os but it was all korean and the android version was 8.1. wtf lol? trying it again now, yes im using "V40PIECONVERSION" not the stock one.
Click to expand...
Click to collapse
Did you check to make sure you are on Slot A and not B? Becuase i remember when i had everything flashed the first time i tried to boot TWRP in Slot A and somehow ended up switching to Slot B

Ainz_Ooal_Gown said:
Did you check to make sure you are on Slot A and not B? Becuase i remember when i had everything flashed the first time i tried to boot TWRP in Slot A and somehow ended up switching to Slot B
Click to expand...
Click to collapse
thats what it ended up being. xSavi helped me out :good:

Hi guys,
I have a Sprint V40 bought off of Taobao that was rooted, sim unlocked, and crossflashed to US Cellular 11d but after I installed Pix3lify trying to get gestures on 8.1 I lost root. I don't seem to be able to get into fastboot, either with Vol- + cable or via adb, but I have an unlocked bootloader and I can get to download mode. Factory reset just reboots. Any tips as to how can I get root back, or upgrade to Pie? Can anybody please explain how to switch from slot a to slot b and vice versa?
Jeff

[GUIDE] Unlock your LG V40 via 9008 mode (Every Variant except T-Mobile)

This Guide will explain how to unlock your LG V40 (Every variant except T-Mobile)​
Unlock Prerequisites:
Make sure you have "Enable OEM Unlock" enabled in developer options, along with adb debugging. Very important. You'll be stuck with the red triangle otherwise. If you don't have the "Enable OEM Unlock" option in developer options, you'll have to flash frp with the v35 engineering bootloader. The frp image will be provided in the attachments section.
QPST Download:
It turns out the reason QFIL is failing is because it's missing quite a bit of stuff. I'm providing the zip to QPST (It's actually required) to install. QPST includes QFIL. My fault, I'm all over the place with this... Here it is (GDrive): QPST
Booting into EDL:
Note: This can be done while booted!
1. Plug in your Phone to your PC
2. Press and hold Power and Volume Down
3. As soon as your screen blanks, rapidly start pressing volume up.
4. If you've successfully booted into EDL, your screen will be completely blank and the device manager will show (Under COM Ports): Qualcomm HS-USB QDLoader 9008
{
"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"
}
Using QFIL to Unlock Your Bootloader
QPST should be installed, and your in 9008 plugged into your PC.
Setting up QFIL:
1. Launch QFIL and set your storage type to UFS. This is located at the bottom right corner of the window The LG V40 has UFS storage. The leaked loader is a loader for LG SD845 UFS devices. If you try to send the loader with your storage set to emmc, it will NOT work. By default, it is set to emmc.
2. Select the port. Click select port and select the one that says "Qualcomm HS-USB QDLoader 9008 (COM #)" That is your phone. After it is highlighted, press OK.
3. Under select programmer, click browse, find the loader and select it.
4. Your screen should now look like this (Minus the Flat Build Stuff, that is for total unbrick purposes):
QFIL is now all setup and ready for flashing.
Flashing the Engineering Bootloader
1. In the upper left hand corner of the Window, click on Tools > Partition Manager from the drop down menu
2. When the Partition Manager window comes up, find "abl_a" > click on it > right click and select Manage Partition Data.
3. When the "Raw Data Manager" window comes up, there are four options to choose from (I'll tell you what each of them does):
Erase: Wipes the specified partition clean
Read Data...: Backs up the partition. It will tell you where it saved it in the log output in the main window
Load Image: Flashes a .img file of your choice to the specified partition
Close: Brings you back to the Partition Manager
You'll be using the load image function to flash the V35 Engineering bootloader to your device.
4. Click load image then select the V35 engineering bootloader. It will flash the image to your device.
Unlocking Your Device:
Now that the V35 Engineering Bootloader has been flashed to your device:
1. Press and hold the Power and Volume Down buttons until your device reboots out of 9008. When you hear the disconnect sound, immediately hold volume down (only volume down) to enter fastboot right away (this is required for both methods, my apologies).
2. When you've entered fastboot, execute this command:
Code:
fastboot oem unlock
Userdata will be wiped as a security measure as with all android devices.
3. While you're still in the v35 engineering bootloader flash back the stock pie bootloader (If originally on pie firmware) with:
Code:
fastboot flash abl_a path/to/ablpiestock.img
The V35 Engineering bootloader is OREO only. Some people have managed to boot with this on pie firmware. But generally, you WON'T be able to boot with this flashed if you're on PIE firmware. If you're on Oreo firmware, you can leave this flashed
4. For devices without the "Enable OEM Unlock" option, you'll need to flash frp! You can do so with (While still in V35 Bootloader):
Code:
fastboot flash frp path/to/frp
4a. Reboot right back into fastboot (hold volume down after rebooting) and run:
Code:
fastboot oem unlock
The reason you can't unlock your T-Mobile device is because no other bootloader/firmware will work with T-Mobile devices. Only T-Mobile firmware will work on it. If you're looking for root, avoid V405TA (T-Mobile) phones. Any other model will work for this.

For some reason, the status says Download Fail:Fail to find QDLoader port after switch when I try to go to the partition manager.

Crap, I completely forgot an important detail. If you are using 9008 mode for the first time, you'll need to update the driver in Device Manager. Then select the port. My fault, I'll update that now.
It should say: Qualcomm HS-USB QDLoader 9008

Xsavi said:
Crap, I completely forgot an important detail. If you are using 9008 mode for the first time, you'll need to update the driver in Device Manager. Then select the port. My fault, I'll update that now.
It should say: Qualcomm HS-USB QDLoader 9008
Click to expand...
Click to collapse
That would do it???. I'll try doing that

@Xsavi This is Awesome! I might get a V40 later in the year
Btw a small point, the title says: Unlock your LG V40 (Via 9008) Root ONLY for T-Mobile variants.
while guide says: his Guide will explain how to unlock your LG V40 (Every variant except T-Mobile)
Title probably needs to be corrected

tech_infinity said:
@Xsavi This is Awesome! I might get a V40 later in the year
Btw a small point, the title says: Unlock your LG V40 (Via 9008) Root ONLY for T-Mobile variants.
while guide says: his Guide will explain how to unlock your LG V40 (Every variant except T-Mobile)
Title probably needs to be corrected
Click to expand...
Click to collapse
Title and guide has been corrected. Thank you for the much needed suggestion!

Also getting a Download Fail, but mine reads "Download Fail:Sahara Fail:QSaharaServer Failrocess fail". My port is showing as Qualcomm HS-USB QDLoader 9008 (COM7). I was sure to try to update the driver in device manager, and am prompted that "The best drivers for your device are already installed".

toddyskates said:
Also getting a Download Fail, but mine reads "Download Fail:Sahara Fail:QSaharaServer Failrocess fail". My port is showing as Qualcomm HS-USB QDLoader 9008 (COM7). I was sure to try to update the driver in device manager, and am prompted that "The best drivers for your device are already installed".
Click to expand...
Click to collapse
The culprit is QFIL being by itself instead of being installed with QPST.

Is that a full, permanent unlock V30-style? So that means that I could now go ahead and buy a North American LG V40 safely as long as it isn't T-Mobile?

WaseemAlkurdi said:
Is that a full, permanent unlock V30-style? So that means that I could now go ahead and buy a North American LG V40 safely as long as it isn't T-Mobile?
Click to expand...
Click to collapse
With 9008 and this firehose, you have complete access to your phone and can flash anything you want with no restrictions.
As long as it isn't T-Mobile, you're fine. The firehose works on those models, but any other firmware/bootloader won't work, so you can't really unlock on T-Mobile models.

How to enter edl mode?
I can't wait to try this!
I'm holding pwr & - vol until the phone resets. While holding pwr & - vol down, I am tapping + vol. I can't get to the blank screen, the phone just restarts normally. Any advice?

clutterking said:
I can't wait to try this!
I'm holding pwr & - vol until the phone resets. While holding pwr & - vol down, I am tapping + vol. I can't get to the blank screen, the phone just restarts normally. Any advice?
Click to expand...
Click to collapse
You have to start pressing volume up as soon as the screen blanks. It's an extremely small window. It'll take a few tries though. Plug in your device, and as soon as you hear the disconnect sound, start pressing volume up. It helps a little for me.

Confirmed working for Korean model LM-V490N!

Xsavi said:
With 9008 and this firehose, you have complete access to your phone and can flash anything you want with no restrictions.
As long as it isn't T-Mobile, you're fine. The firehose works on those models, but any other firmware/bootloader won't work, so you can't really unlock on T-Mobile models.
Click to expand...
Click to collapse
Awesome! You guys are brilliant!
So do we expect a kickstart in development (like the V30's dev scene) now that an unlock is available for everybody?
And one last question: does this mean that we can unlock a (network) locked phone this way? I know that the usual answer is 'no', but from what I've seen around here, there's something called 'cross-flashing' of US unlocked firmware. Perhaps that means an unlock?
If not, do online unlock services work? (I do not want any names - I just want to know whether any service at all works).
I do apologize if my questions are stupid - it's only that with the overwhelming amount of (sometimes contradictory) posts here, I just want to make sure I'm doing everything correctly! :laugh:

WaseemAlkurdi said:
Awesome! You guys are brilliant!
So do we expect a kickstart in development (like the V30's dev scene) now that an unlock is available for everybody?
And one last question: does this mean that we can unlock a (network) locked phone this way? I know that the usual answer is 'no', but from what I've seen around here, there's something called 'cross-flashing' of US unlocked firmware. Perhaps that means an unlock?
If not, do online unlock services work? (I do not want any names - I just want to know whether any service at all works).
I do apologize if my questions are stupid - it's only that with the overwhelming amount of (sometimes contradictory) posts here, I just want to make sure I'm doing everything correctly! :laugh:
Click to expand...
Click to collapse
Your questions aren't stupid.
Unfortunately, you can't sim unlock using this method. I'm hoping this will kickstart development for this device also, I already have a few ROMs made I have yet to release to XDA. Any 3rd party online unlock services are scams. Nowadays, everything is done server side when it comes to SIM unlocking your phone.
No problem dude! If you have any other questions, feel free to reach out to me. I'm super active in the V40 telegram group. I'm becoming more active here too (I need to. LoL).

Fantastic!!! Really appreciate all the hard work.
Sent from my LM-V405 using Tapatalk

TheLinuxMan02 said:
Note: If on Pie firmware, boot back into 9008 and flash the latest TWRP, along with the stock ABL so you can boot back into your firmware. With the engineering bootloader, you can't boot pie firmware. Only oreo.
Click to expand...
Click to collapse
Hey, thanks so much for this method. A damned shame we got to go through this just to get fastboot on these damn phones, but you're the all-stars we need to get it going.
Question. How are we flashing TWRP and ABL? Using fastboot or QFIL? Also, do you have a link to the latest TWRP? I know there's a thread in this forum for TWRP by SGCMarkus. Is that the TWRP version you recommend?

copota said:
Hey, thanks so much for this method. A damned shame we got to go through this just to get fastboot on these damn phones, but you're the all-stars we need to get it going.
Question. How are we flashing TWRP and ABL? Using fastboot or QFIL? Also, do you have a link to the latest TWRP? I know there's a thread in this forum for TWRP by SGCMarkus. Is that the TWRP version you recommend?
Click to expand...
Click to collapse
You can use either method to flash twrp and abl. If in QFIL, just follow the steps above but choose boot_a or boot_b for TWRP, and abl_a and abl_b for stock abl.

I can't get my phone into 9008 mode. Would it be because I crossflashed my phone? Here's my crossflashing history...
edit: Never mind, when I plugged my phone into a power source, then tried it, I was able to get into 9008 mode.

Is this something that could be blocked in a further update? Is there something LG could do to block it?
Thanks again

Guide LG G8/G8x/v50 Bootloader Unlock and Magisk Root using Firehose

Disclaimer: I am not responsible for any problems from using this guide.​Works for G8, G8s, G8x, and v50
Confirmed working on G8 and v50
Requirements: Android 10
QFIL: https://drive.google.com/file/d/1P7uGjIirqGRdkwlxgKf_idepDlv6_u-q/view?usp=sharing
QFIL Driver: https://drive.google.com/file/d/1sPJm1RuSoVX9JMEs-Gx8xNuEDadO6rpj/view?usp=sharing
LG Mobile Driver:
LG Mobile Phone - Drivers and Software Downloads | LG USA Support
LG Mobile Phone - Drivers and Software Downloads. Learn how to use, update, maintain and troubleshoot your LG devices and appliances.
www.lg.com
ADB: https://drive.google.com/file/d/1nvlwaicFpDN_4DGR0BZRWUDgwQwYzOhS/view?usp=sharing
Firehose: https://drive.google.com/file/d/1ekI_d2-P9GdoakkSgk2hK1WHbQLIPlTQ/view?usp=sharing
abl: https://drive.google.com/file/d/1sye4gXsDfD8JVF5qfAMG_GDxSLKY6J6Q/view?usp=sharing
Verizon LG G8 only frp: https://drive.google.com/file/d/1294cXerj2_EkeGw1p38CcVPuyRfdS9N5/view?usp=sharing
This Verizon FRP img was only tested on LG G8 Verizon and is not recommended to be used on other Verizon Variants as it will prevent the phone from booting.
Bootloader Unlock
Unlocking your bootloader will erase all data on your phone
First Install LG Mobile Driver, QFIL driver, and QFIL (Select first option, WWAN)
All Variants other than Verizon: Go to Settings, > System > About Phone > Software Info > Tap Build Number 7 Times.
Go back to Settings > System > Developer Options. Check Enable OEM Unlock
Spoiler: Enable OEM Unlock
{
"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"
}
Boot you phone into EDL
You can make sure that your phone is in EDL by plugging your phone to your pc and checking the Device Manager > Ports > Qualcom HS-USB QDLoader 9008 (COM#)
Spoiler: Device Manager
Hold Vol- and Power, when the phone screen turns off to restart begin quickly pressing the vol+ but keep holding vol- and power.
Here is a youtube video of how to boot to EDL:
Spoiler: How to enable EDL mode (Как включить режим EDL 9008) on LG G7 G8 V30 V35 V40 V50
Open QFIL, Select your Phone's Port, Select Flat Build under Select Build Type, Select the Firehose.elf file under Select Programmer, on the bottom right of QFIL select UFS as the Storage Type.
Spoiler: QFIL setup
Click Tools > Partition Manager.
Find Abl_a and right click on it and select Manage Partition Data. Click Read to backup your abl_a.
Spoiler: Right Click - Manage Partition Data
Go to Windows Explorer and go to C:\Users\Username\AppData\Roaming\Qualcomm\QFIL\COMPORT#
Rename your ReadData_ufs_Lun4.bin to abl_a.bin
Spoiler: Before Rename abl_a and abl_b
Do the same with abl_b, boot_a, and boot_b.
Boot_a and Boot_b is for Magisk Root. Skip if you only want Bootloader Unlock.
Spoiler: After Rename abl_a and abl_b
Close Partition Manager. Your phone will reboot to EDL on its own after pressing OK. Wait on that.
Go back to Partition Manager and right click on abl_a again then select Manage Partition Data, then Select Load and choose the abl engineering file.
Do the same for abl_b.
Close Partition Manager. Your phone will reboot to EDL on its own after pressing OK. Wait on that.
Reboot to Fastboot. Hold Vol- and Power then release power when reboot starts and keep holding vol-
If that doesn't work unplug and Power off your phone. Hold vol- and plug it in. It should go into fastboot.
Once your phone is in Fastboot it should say
Device State: Locked and Active A/B Slot - _a or _b
remember whichever slot your device says and stay on that slot, you may risk bricking if you change to the other slot. You also need this for Root later.
Spoiler: Bootloader Locked and Slot
Extract the ADB.zip
open a Command Prompt and change the directory to the adb folder you just extracted
cd C:\adb
run fastboot devices in that command prompt. it should show "LMG850UM fastboot"
Move the backed up abl_a.bin and abl_b.bin to the adb folder, also frp_verizon.img if you have the verizon LG G8.
Spoiler: Move abl_a.bin, abl_b.bin to ADB folder. frp_verizon.img as well for Verizon Variant
Verizon LG G8 only: Run fastboot flash frp frp_verizon.img then fastboot reboot-bootloader
Reboot to Fastboot. Hold Vol- and Power then release power when reboot starts and keep holding vol-
If that doesn't work unplug and Power off your phone. Hold vol- and plug it in. It should go into fastboot.
Run fastboot oem unlock
Select Unlock The Bootloader with your arrow keys and press the Power Button
Spoiler: Bootloader Unlock with Volume Keys
Reboot back to the Bootloader. Unplug your phone, Power off, Hold Vol-, then Plug it in.
Your phone should say Device State – unlocked now
Spoiler: Success Bootloader Unlock
Now fastboot flash abl_a abl_a.bin
and fastboot flash abl_b abl_b.bin
Finish with fastboot reboot
Your Phone Is now Bootloader Unlocked.
Magisk Root
Only do this after you have followed the above guide and have Unlocked your Bootloader.
Magisk
Xda Forum: https://forum.xda-developers.com/f/magisk.5903/
Xda Thread: https://forum.xda-developers.com/t/magisk-the-magic-mask-for-android.3473445/
Github Page: https://github.com/topjohnwu/Magisk
Find the slot you are on from the fastboot bootloader earlier
Go to Windows Explorer and go to C:\Users\Username\AppData\Roaming\Qualcomm\QFIL\COMPORT#
Transfer to your phone the boot_a.bin or boot_b.bin that you backed up in the COMPORT# folder.
Download and install Magisk Manager.
Open Magisk Manager and beside Magisk hit "Install" then "Select and Patch a File" and select the boot_a.bin or boot_b.bin.
After Magisk has patched your boot img you should have magisk_patched#####.img in your phones Download folder.
Transfer it to your PC.
Reboot to EDL
Open QFIL. Click Tools > Partition Manager.
Find the slot you are on from the fastboot bootloader earlier and right click on either boot_a or boot_b and select Manage Partition Data.
Click Load and select the magisk_patched#####.img file you transfered from your phone.
Wait for it to finish then Close Partition Manager. Your phone will reboot to EDL on its own after pressing OK. Wait on that.
Reboot to System by holding vol- and power till your phone reboots out of EDL then release both.
Your phone is now Bootloader Unlocked with Magisk Root.
Hopefully this helps.
This guide was written by me, but the information was provided by Cloud1250000.
If there are any errors let me know and I will fix.

Does this work on sprint lg g8x

It should since the abl used is from a g8x and it worked on my v50 sprint..

¿Alguien ya ha probado si es estable es root? ¿O se elimina después de cada reinicio?

RenardHCRc said:
¿Alguien ya ha probado si es estable es root? ¿O se elimina después de cada reinicio?
Click to expand...
Click to collapse
use google translator next time.
"
Has anyone already tested if root is stable? Or is it removed after every reboot?
"
yes it stays after reboot.. you basically root the normal way.. by patching boot.. because you unlock the bootloader before that.

cloud1250000 said:
use google translator next time.
"
Has anyone already tested if root is stable? Or is it removed after every reboot?
"
yes it stays after reboot.. you basically root the normal way.. by patching boot.. because you unlock the bootloader before that.
Click to expand...
Click to collapse
Okey Arigato

worked on korean v50 (v500n)
for qfil to work, I had to use windows server 2019. linux should work too. i had errors on both my main machine and my laptop, both of which are running win 10 pro
for fastboot to work, I had to enable testmode (requires you to turn off secure boot in your uefi)
thanks to cloud1250000 for helping me through the process

why my phone has lost touch
what can i do

anhtuan70000 said:
why my phone has lost touch
what can i do
Click to expand...
Click to collapse
Phone model? Firmware?
Did you restore the abl_a and abl_b with the backup you made?
It losts touch at what step in the guide?

cloud1250000 said:
Phone model? Firmware?
Did you restore the abl_a and abl_b with the backup you made?
It losts touch at what step in the guide?
Click to expand...
Click to collapse
thanks for reply
my devices: lg g8 sprint g820u21d
i think i solved it, just restore the abl_a and abl_b but my device doesnt have root. i follow magisk root step , try many time but no luck.
edit: Finally i dit it !!

anhtuan70000 said:
thanks for reply
my devices: lg g8 sprint g820u21d
i think i solved it, just restore the abl_a and abl_b but my device doesnt have root. i follow magisk root step , try many time but no luck.
edit: Finally i dit it !!
Click to expand...
Click to collapse
Yeah who would have thought it was important to follow all the steps...

Will this work with T-Mobile G8?

Hi!
I have an LG G8 from Amazon ( Open US?) .
I need root to update the VowiFi operators in the LG files to use VoWiFi in Europe.
I guess i need root and verity disabled?
It's still on Android 9 and i want it on Android 9.
It's there any way to use your guide and still be on Android 9?
Any tips about my goal would be appreciated!

I know it says that Android 10 is required but will this work with Android 9 on G8 G820UM? I have a AT&T G8 that is stuck on Android 9. I tried to manually flash a Android 10 KDZ via modified LG UP but it gets stuck on LG Logo so I flashed an Android 9 KDZ and the phone works fine (the serial # was wiped unfortunately :-(). It obviously doesn't get any OTA updates either. I am wondering if there is any that I can update the phone manually to Android 10.

memnon79 said:
Will this work with T-Mobile G8?
Click to expand...
Click to collapse
Should work

Great, excellent, wonderfull

wwechampian said:
I know it says that Android 10 is required but will this work with Android 9 on G8 G820UM? I have a AT&T G8 that is stuck on Android 9. I tried to manually flash a Android 10 KDZ via modified LG UP but it gets stuck on LG Logo so I flashed an Android 9 KDZ and the phone works fine (the serial # was wiped unfortunately :-(). It obviously doesn't get any OTA updates either. I am wondering if there is any that I can update the phone manually to Android 10.
Click to expand...
Click to collapse
It is upgradable to android 10

The Google Drive link for the LG Mobile Driver was taken down

I'm working with Sprint g8 Thinq LM-G820UMKIT on Android 10. Every time i go to Partition Manager it starts connecting to my phone and sits for about a minute then it come back with an error saying "DownloadFail:Sahara Fail:QSharaServerFailProcess fail".
Its on Flat build
Its has the right programmer path set to the firehose file
and it is set to ufs storage type
Any suggestions?

Tugboat Tony said:
I'm working with Sprint g8 Thinq LM-G820UMKIT on Android 10. Every time i go to Partition Manager it starts connecting to my phone and sits for about a minute then it come back with an error saying "DownloadFail:Sahara Fail:QSharaServerFailProcess fail".
Its on Flat build
Its has the right programmer path set to the firehose file
and it is set to ufs storage type
Any suggestions?
Click to expand...
Click to collapse
You need to unistall QFIL and instal other version until you can, what version of firmware have your phone?

How To Guide [GUIDE] [RUI3] Unlock bootloader on RealmeUI 3 with deep testing.

It is now possible to unlock bootloader using the in-depth deep testing app, however it will only work on Thailand firmware, so we are going to flash the Thailand firmware and use the in-depth app on it.
Links:
MTKClient: https://drive.google.com/file/d/13KohUUeuzVoGKxVWIuLDZx11PV8EeMBj/view?usp=sharing
SP Flash Tool: https://drive.google.com/file/d/1McZ11On8XbxGgE-hMA_nZqErHI_QwjQT/view?usp=sharing
MTK Drivers: https://drive.google.com/file/d/1UExJQxI1DmBGeDoYPul5YTXitOnsU6zx/view?usp=sharing
Thailand Firmware: https://drive.google.com/file/d/192KboBbW1eXzb6DWVlGAkGE-PEcgnHBJ/view?usp=sharing
Deep Testing APK: https://drive.google.com/file/d/1pESMmJef6Gm9YlJAE7OA_DDNnhFn3Jpz/view?usp=sharing
Libusb port filter: https://sourceforge.net/projects/li...ibusb-win32-devel-filter-1.2.6.0.exe/download
Flashing Thailand firmware:​We are going to flash this in SP flash tool, first, let's setup MTK authorization bypass (if you have already setup python and drivers then skip this)
Install python from https://www.python.org/downloads/ and make sure it's configured
Go to the Driver folder, right click cdc.acm.inf and install it.
{
"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"
}
Install libusb port filter, afterwards click Next and hold volume up and down button, then choose MediaTek USB Port.
Now click install, next install UsbDK from here: https://github.com/daynix/UsbDk/releases/
Once you have done that, open a CMD/Powershell in the directory of MTKClient, write pip3 install -r requirements.txt and python mtk payload, hold the volume up and down button and plug the device in
If everything went well, you should be seeing this:
Now open SP Flash tool, go to Options > Option
Now go to Connection and select UART, set the baud rate to 921600
Now, open the scatter file (MT6785_Android_scatter.txt) from the directory of the firmware, it should load the firmware
Unselect opporeserve2 and click the Download button, it should start flashing
Once it is done flashing, you should see this:
Don't forget to reboot the device into recovery mode (volume down + power) and format data.
Updating to RealmeUI 3:​Since it is not possible to use the deep testing app on RealmeUI 2, you must update to RealmeUI 3, simply update it from the update app in settings, if you do not get the update, we can't do anything about it.
No need, replaced firmware link with RealmeUI 3 Thailand firmware, just flash that and use the in-depth app in the guide!
Using the deep testing app and unlocking the bootloader:​Download and install the deep testing app, tap "Apply Now" and accept the agreement, you should be seeing this now:
Wait 3 to 5 minutes, close the app and reopen again, tap "Query verification status" and you should see this:
This means your device now has unlocked fastboot access, tap "Start deep testing" and the device will reboot to fastboot mode
If you see this, the device is now in fastboot mode, to unlock the bootloader plug the device into a PC and write fastboot flashing unlock in Fastboot/ADB directory, you should see this:
Press the volume up button, the bootloader is now unlocked, congratulations!
NOTE: you can return to any EEA/Indian firmware you were on before and still have the bootloader unlocked.
Credits:
@bkerler for MTKClient

I tried this method on my primary Realme 8 device (Bangladeshi varaint) and it did worked.

Nice tutorial!

Also a pro tip for recovery mode can't be accessed after changing firmware and device keep rebooting after every 5 mins while stuck in realme bootanimation
download latest platform tools from google's official developer website, go to fastboot mode, enter command "fastboot reboot recovery"
you will be in recovery mode
then format data
your device will boot to OS after that

Does it work on realme UI 3.0 C.09 (bootloader locked)?

AJ⁰⁰⁷ said:
Does it work on realme UI 3.0 C.09 (bootloader locked)?
Click to expand...
Click to collapse
It shouldn't matter which firmware you are on right now, as for updating to TH RUI3 firmware it dosen't matter which C.0x it is as long as it's RealmeUI 3.

plarfman said:
It shouldn't matter which firmware you are on right now, as for updating to TH RUI3 firmware it dosen't matter which C.0x it is as long as it's RealmeUI 3.
Click to expand...
Click to collapse
Thank You

AJ⁰⁰⁷ said:
Does it work on realme UI 3.0 C.09 (bootloader locked)?
Click to expand...
Click to collapse
No. It's not working on RUI3 c.09 version. I've tried on my Bangladeshi 8/128 GB variant. And it got bricked after flashing the Thailand firmware.

ShahriarX1 said:
No. It's not working on RUI3 c.09 version. I've tried on my Indian 8/128 variant. And it got bricked after flashing the Thailand firmware.
Click to expand...
Click to collapse
Ohhz that's bad @plarfman

plarfman said:
It shouldn't matter which firmware you are on right now, as for updating to TH RUI3 firmware it dosen't matter which C.0x it is as long as it's RealmeUI 3.
Click to expand...
Click to collapse
I think you misunderstood it. I was asking that can I flash it over my Indian C.09 firmware?

plarfman said:
It shouldn't matter which firmware you are on right now, as for updating to TH RUI3 firmware it dosen't matter which C.0x it is as long as it's RealmeUI 3.
Click to expand...
Click to collapse
Was the Thailand firmware you attached in the post official??
Cause I got an error while flashing it. It says the firmware is not official.

ShahriarX1 said:
Was the Thailand firmware you attached in the post official??
Cause I got an error while flashing it. It says the firmware is not official.
Click to expand...
Click to collapse
Show a screenshot.

ShahriarX1 said:
No. It's not working on RUI3 c.09 version. I've tried on my Bangladeshi 8/128 GB variant. And it got bricked after flashing the Thailand firmware.
Click to expand...
Click to collapse
Stuck on recovery mode text? Then you should erase userdata, metadata and md_udc using mtkclient
And yes, mine is also Bangladeshi 8/128 varaint.

I don't know why after unlocking, entering recovery mode gets difficult. I wish that can be accessed while pressing buttons.
It's like recovery combo turns into fastboot combo
Also Oppo/Realme stock recovery has a problem when magisk is installed. It will bootloop forever when reboot to recovery from magisk and it's pretty hard to get into fastboot mode that moment.
The real fix for that problem is restore stock boot and dm-verity image

plarfman said:
Show a screenshot.
Click to expand...
Click to collapse

AE_Fahim said:
Stuck on recovery mode text? Then you should erase userdata, metadata and md_udc using mtkclient
And yes, mine is also Bangladeshi 8/128 varaint.
Click to expand...
Click to collapse
Flash is not completing bro. Have a check on the Screenshot and suggest.

ShahriarX1 said:
Flash is not completing bro. Have a check on the Screenshot and suggest.
Click to expand...
Click to collapse
Looks like your file got somehow corrupted. You can try downloading ofp file, manually decrypting it and merging multiple super.img using simg2img (super 2 must be Thailand) and setting super download is true from scatter file.

all set! I went to fastboot mode using deeptest tool. But i don't know what to do after that to unlock the bootloder device. Kindly help me!

Yadhevdev66 said:
all set! I went to fastboot mode using deeptest tool. But i don't know what to do after that to unlock the bootloder device. Kindly help me!
Click to expand...
Click to collapse
in fastboot mode enter
Code:
fastboot flashing unlock

can you send the fastboot drivers?