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
Related
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
Delete This Please!
Go here instead: https://forum.xda-developers.com/lg-v40/how-to/guide-lgup-root-t3967858
Can I Crossflash my LG V40 sprint to be used with an unlocked rom so it can be used in a different company with this method or just install android 9 but it will stay sim locked?
Michaeljror said:
Can I Crossflash my LG V40 sprint to be used with an unlocked rom so it can be used in a different company with this method or just install android 9 but it will stay sim locked?
Click to expand...
Click to collapse
No. Keep reading the forum.
If your device is sim locked by Sprint, the only way currently is to call Sprint and have them unlock it. No, this will not sim unlock your phone. I'm gonna put this in the OP.
Why not replace laf with the dd command?
AFAIK V40 on android 9 can be flashed with lgup by default, without any LAF manipulations.
Only android 8 is problem, need to be flashed to 9 with octoplus
Dump mode does not work.
Xsavi said:
Requirements:
Bootloader Unlocked V40 with V35 eng bootloader in slot B, or A if on Oreo
USB 2.0
Root (For wiping your LAF_a to access fastboot)
My laf Partition (Already Provided)
LGUP and Modded DLLs (Provided in attachment)
Notes: When you're finished with this, you'll be able to use LGUP 1.14 with no issues. For some odd reason, my V40 has a laf protocol version of 08, instead of 16. So that means LGUP works. This works on all V40s with the exception of T-Mobile's V40.
Okay, lets's get started.
Download The FIles: Google Drive
Installing LGUP:1. Extract the zip file anywhere on your computer
2. Install LGUP and replace the files located in the "FilesToReplace" folder.
LGUP.exe goes in:
Code:
C:\Program Files (x86)\LG Electronics\LGUP
LGUP_common.dll goes in (If common folder isn't there, create it):
Code:
C:\Program Files (x86)\LG Electronics\LGUP\model\common
Flashing my LAFOkay, now, you'll need to be in the V35 engineering fastboot for this part.
1.Put your phone in fastboot mode (Power off, vol up, plug in). If you need to access fastboot mode (assuming you're rooted), dd /dev/zero your LAF_a partition (dd if=/dev/zero of=/dev/block/sde16). If on oreo, just power off and hold vol down.
2. Within the extracted ZIP, go into the LGUPCompatibleLAF folder and open a command prompt there (Type CMD in the address bar). We need to get into the V35 Engineering bootloader, run this command:
Code:
fastboot.exe set_active b
{
"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"
}
3. Reboot, and it should boot straight into the v35 eng for pie users. For oreo users, power off, hold vol down, plug in. Run these commands to flash my laf:
Code:
fastboot.exe flash laf_a laf.img
Code:
fastboot.exe flash laf_b laf.img
4. Now, we need to get back to our A slot, run:
Code:
fastboot.exe set_active a
5. Unplug and power off your device. Then, press and hold vol up and plug in your device. You should be in download mode and LGUP will work.
Some Advice:
Do NOT refurbish your device with LGUP. You WILL lose root and your unlocked bootloader. If you ever want to switch firmwares, just use Partition DL. If you use Partition DL, deselect: laf_a, laf_b, abl_b.
You may now flash the KDZ of your choice as long as it's compatible with your V40. Again, I highly recommend using Partition DL when flashing KDZs
Bootloader Unlocking
If you need your bootloader unlocked, or need to recover from a brick, head over to @vbenkovskyy on Telegram. He's an amazing dude and goes above and beyond when unlocking/flashing your device. His prices are amazing too and he'll work with ya (Be reasonable though). The reason I'm putting this in here is because he really helped me out on making these things possible (I bricked several times).
Again, head over to @vbenkovskyy on Telegram if you want your bootloader unlocked.
Click to expand...
Click to collapse
This worked awesome, LGUP now works.:good:. Thank you. The only problem is not I can't get into FASTBOOT, only DOWNLOAD mode.
I followed this on my Sprint V40. After powering off and trying to enter download mode, I get "Your device has failed a routine safety check and will not boot."
Has anyone seen that before? After that, I get a green screen with black text that says "LGE Crash Handler : FIQ : NOC Error!"
Any ideas?
imekul said:
I followed this on my Sprint V40. After powering off and trying to enter download mode, I get "Your device has failed a routine safety check and will not boot."
Has anyone seen that before? After that, I get a green screen with black text that says "LGE Crash Handler : FIQ : NOC Error!"
Any ideas?
Click to expand...
Click to collapse
did the screen say Sahara?
Yeah, it said Sahara at the very bottom.
imekul said:
Yeah, it said Sahara at the very bottom.
Click to expand...
Click to collapse
I've gotten that a few times lol basically a few things aren't matching and it won't boot correctly, so therefore Sahara
Glad I'm not the only one!
Any idea how I can get out of it?
imekul said:
Glad I'm not the only one!
Any idea how I can get out of it?
Click to expand...
Click to collapse
You can try a few things
1st. fastboot mode and if it's v35 you can flash almost everything from Slot_b
2nd. try to enter download mode and see what happens if you enter Fastboot mode instead then you have the V40 Fastboot in that Slot.
3rd. wait for my Guide.
Ainz_Ooal_Gown said:
You can try a few things
1st. fastboot mode and if it's v35 you can flash almost everything from Slot_b
2nd. try to enter download mode and see what happens if you enter Fastboot mode instead then you have the V40 Fastboot in that Slot.
3rd. wait for my Guide.
Click to expand...
Click to collapse
For #1, do you mean use the fastboot.exe set_active b command and then try flashing with LG UP?
For #2, when I go to download mode it only stays at download for a few seconds before going to that screen with the green text and "Sahara" at the bottom. How do I enter fastboot from download mode?
I appreciate the suggestions!
imekul said:
For #1, do you mean use the fastboot.exe set_active b command and then try flashing with LG UP?
For #2, when I go to download mode it only stays at download for a few seconds before going to that screen with the green text and "Sahara" at the bottom. How do I enter fastboot from download mode?
I appreciate the suggestions!
Click to expand...
Click to collapse
If you have V35 Fastboot (Volume down and power when plugged in) then chances are you may have access to Download Mode, but V40 Fastboot Access so Pie actually boots up takes the place of download mode.
Ainz_Ooal_Gown said:
If you have V35 Fastboot (Volume down and power when plugged in) then chances are you may have access to Download Mode, but V40 Download Mode so that Pie actually boot up takes the place of download mode.
Click to expand...
Click to collapse
I do get the V35 fastboot when I do Vol Down + plug in cable. It says ACTIVE A/B Slot - _a.
Should I do the fastboot.exe set_active b command and then try rebooting into download mode and flashing from LG UP? I was a little confused what the next step would be if I could get the V40 into the V35 fastboot.
imekul said:
I do get the V35 fastboot when I do Vol Down + plug in cable. It says ACTIVE A/B Slot - _a.
Should I do the fastboot.exe set_active b command and then try rebooting into download mode and flashing from LG UP? I was a little confused what the next step would be if I could get the V40 into the V35 fastboot.
Click to expand...
Click to collapse
Yes that's exactly what you should do. I have a Sprint V40 and was bootlooping to the V40 fastboot. I followed this post . I uninstalled and deleted all LGUP and ADB programs and files, from previous attempts just to get a clean start. The three links in the post have everything you need except for firmware. Download the US unlocked PIE kdz. A link to the file can be found in the footer/signature of the OP. You're intuition is on point though, so just follow the directions and I'm sure you'll be fine.
thezachman said:
Yes that's exactly what you should do. I have a Sprint V40 and was bootlooping to the V40 fastboot. I followed this post . I uninstalled and deleted all LGUP and ADB programs and files, from previous attempts just to get a clean start. The three links in the post have everything you need except for firmware. Download the US unlocked PIE kdz. A link to the file can be found in the footer/signature of the OP. You're intuition is on point though, so just follow the directions and I'm sure you'll be fine.
Click to expand...
Click to collapse
Why thanks for clearing that up and pointing them in the right direction, cheers
Just info to maybe clear confusion for some who is in a whirlwind (like me)
I've been bouncing between forums for a good few hours. I'm confused on what this one is forum is for (international v40s?) as I was able to Use LGUP on my Sprint V40 that was running 8.1 and flashed it to US unlocked kdz 9.0 (Pie?) without having my bootloader unlocked and not rooted (well i was never able to get into bootloader/fastboot to OEM unlock it).
but i do have a question, from what i gathered between all the sources i read... I need to contact someone to obtain the 35v engineering bootloader and flash to my device, so i have a bootloader that i can boot into for fastboot?
Im just trying to get TWRP but i have no bootloader or does not load with adb, volume down + power when plug in cable methods.
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?
IT WILL ERASE ALL DATA ON YOUR PHONEAND KEEP YOUR BOOTLOADER UNLOCKED.YOUR WARRANTY WILL BE VOID AFTER IT.DO IT AT YOUR OWN RISK. DO IT CAREFULLY.(It won't erase your SD card, but I still recommend you remove SD card before it)Please read this thread carefully at least once before you modify your phone.
This thread is in order to give your X01AD a new life when it hard bricked.
First, Prepare the things you need :
-A Computer
Windows (10 is better) Platform. Tell me if you need Linux version.
-QPST
Download the file below. QPST included QFIL.
-Firmware
Download from here(vnrom.net). (find version "15.2016.1902.159" under ZB633KL)
-Unofficial unlock tool (Maybe you need)
Download from here(other thread). (download unlock.zip)
(Perhaps you don't need below stuffs, see note.)
-A flat screwdriver or anything can pry the backcover of your phone.
Download from reality
-A slice of paper
It is for separate battery cable and port.
-A USB Cable that have good quality.
The better the better.
Second, install QPST and Qualcomm USB driver, and then reboot.
Third, launch QFIL, choose "Flat Build",click "Configuration">"FireHose Configuration"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and set up like this:
click "OK" after you completed setting,
Next, Click "Browse...", navigate to the folder you unzip the firmware, select 'prog_emmc_firehose_8953_ddr.mbn'.
DON'T SELECT "validated_..." ONE, IT WILL LET FLASH FAIL.
Click "Load XML...", select 'rawprogram_unsparse.xml' in first window, select 'patch0.xml' in second window.
DON'T CLOSE WINDOW!
Fourth, enter EDL mode, try note1 first.
pry the back-cover of your phone.
Be careful, don't hurt your hand or screen, look carefully.
Remove battery cable cover, remove battery cable, put the paper between cable and port.
Next, connect your phone and computer.
Fifth, click "Select Port...", select 'Qualcomm......Port', click "OK".
Your "Download" button should available now. Click it.
And your phone will reboot automatically after flash completed.
Finally, your phone will boot into stock android 8 .
And if you get RED error, reboot into fastboot, run unofficial unlock. It should be resolve after that.
(Real relock bootloader method not found yet , it will get RED state after you lock the bootloader)
Note:
1 If you want enter EDL mode, "maybe" you can press VolUp+VolDown+Powerkey when power is off,
screen will be blank after a few seconds, and screen will not display anything during EDL mode.
Connect phone and computer to see whether QFIL detected device.
Long press Powerkey to exit EDL mode.
2 Serial number(string) will be erase, please follow this thread to recover that.
I tried but after rebooting I'm facing EIO warning after unlocking it did gone but I want to lock the Bootloader
Techgaming432 said:
I tried but after rebooting I'm facing EIO warning after unlocking it did gone but I want to lock the Bootloader
Click to expand...
Click to collapse
Is there blank screen after EIO warning?
dascrystal said:
Is there blank screen after EIO warning?
Click to expand...
Click to collapse
After EIO warning it goes to Asus splash screen then again EIO then again splash it loops
But
If i unlock the bootloader then the EIO state disappears
Techgaming432 said:
After EIO warning it goes to Asus splash screen then again EIO then again splash it loops
But
If i unlock the bootloader then the EIO state disappears
Click to expand...
Click to collapse
Sorry, I still can't find a method that can relock the bootloader,
but I think if anyone have a locked or not unlocked X01AD,
we maybe can pull the file in it (boot, persist, dtbo, etc.), that maybe can help.
By the way, I want to learn how to port or create a device specific rom, if you know any tutorial resource, tell me please.
dascrystal said:
Sorry, I still can't find a method that can relock the bootloader,
but I think if anyone have a locked or not unlocked X01AD,
we maybe can pull the file in it (boot, persist, dtbo, etc.), that maybe can help.
By the way, I want to learn how to port or create a device specific rom, if you know any tutorial resource, tell me please.
Click to expand...
Click to collapse
Join our official TG group so I can explain all these things
Techgaming432 said:
Join our official TG group so I can explain all these things
Click to expand...
Click to collapse
Where is the link?
dascrystal said:
Where is the link?
Click to expand...
Click to collapse
Search our device name in tg
Here I can't send link due to rules of XDA
Techgaming432 said:
Search our device name in tg
Here I can't send link due to rules of XDA
Click to expand...
Click to collapse
Is that ASUS Max M2 | X01AD | OFFICAL ?
Yes
dascrystal said:
Is that ASUS Max M2 | X01AD | OFFICAL ?
Click to expand...
Click to collapse
tag me there my name is @subhendu_mk
When i try to select the Programmer in Firmware folder, there is no file recognized as useful. Its empty from the QFIL point of view
Error Sahara protocol
Main 320: Uploading Image using Sahara protocol failed
Failed to open the device 1 slot 0 partition 0
It's all well explained, but firehose fail is a problem.
(X01AD) Valid Relocker for Bootloader
(X01AD) Valid Relocker for Bootloader
Dear forum users, I am glad to present you several guaranteed ways to lock the bootloader on Asus Zenfone Max M2 (ZB633KL, X01AD). This completely solves the "Red State" problem, allows you to return to stock with a successful SafetyNet...
forum.xda-developers.com
This is the method for "Real relocking", although I haven't tested yet, but someone said it works.
dascrystal said:
IT WILL ERASE ALL DATA ON YOUR PHONEAND KEEP YOUR BOOTLOADER UNLOCKED.YOUR WARRANTY WILL BE VOID AFTER IT.DO IT AT YOUR OWN RISK. DO IT CAREFULLY.(It won't erase your SD card, but I still recommend you remove SD card before it)Please read this thread carefully at least once before you modify your phone.
This thread is in order to give your X01AD a new life when it hard bricked.
First, Prepare the things you need :
-A Computer
Windows (10 is better) Platform. Tell me if you need Linux version.
-QPST
Download the file below. QPST included QFIL.
-Firmware
Download from here(vnrom.net). (find version "15.2016.1902.159" under ZB633KL)
-Unofficial unlock tool (Maybe you need)
Download from here(other thread). (download unlock.zip)
(Perhaps you don't need below stuffs, see note.)
-A flat screwdriver or anything can pry the backcover of your phone.
Download from reality
-A slice of paper
It is for separate battery cable and port.
-A USB Cable that have good quality.
The better the better.
Second, install QPST and Qualcomm USB driver, and then reboot.
Third, launch QFIL, choose "Flat Build",click "Configuration">"FireHose Configuration"
View attachment 5355831
and set up like this:
View attachment 5355701
click "OK" after you completed setting,
Next, Click "Browse...", navigate to the folder you unzip the firmware, select 'prog_emmc_firehose_8953_ddr.mbn'.
View attachment 5355697DON'T SELECT "validated_..." ONE, IT WILL LET FLASH FAIL.
Click "Load XML...", select 'rawprogram_unsparse.xml' in first window, select 'patch0.xml' in second window.View attachment 5355705
DON'T CLOSE WINDOW!
Fourth, enter EDL mode, try note1 first.
pry the back-cover of your phone.
Be careful, don't hurt your hand or screen, look carefully.
Remove battery cable cover, remove battery cable, put the paper between cable and port.
Next, connect your phone and computer.
Fifth, click "Select Port...", select 'Qualcomm......Port', click "OK".
Your "Download" button should available now. Click it.
And your phone will reboot automatically after flash completed.
Finally, your phone will boot into stock android 8 .
And if you get RED error, reboot into fastboot, run unofficial unlock. It should be resolve after that.
(Real relock bootloader method not found yet , it will get RED state after you lock the bootloader)
Note:
1 If you want enter EDL mode, "maybe" you can press VolUp+VolDown+Powerkey when power is off,
screen will be blank after a few seconds, and screen will not display anything during EDL mode.
Connect phone and computer to see whether QFIL detected device.
Long press Powerkey to exit EDL mode.
2 Serial number(string) will be erase, please follow this thread to recover that.
Click to expand...
Click to collapse
Ok. Post rom which works 100%
N3l3 said:
Ok. Post rom which works 100%
Click to expand...
Click to collapse
UnBrick (EDL) - ZQL1830_Factory_201812181515_ChangeFlash.zip
AzimBahar said:
UnBrick (EDL) - ZQL1830_Factory_201812181515_ChangeFlash.zip
Click to expand...
Click to collapse
Post again.
You can get it on ROMDevelopers.
They have huge collection
any one help me am get error cant got to edl mode
Today the A33 5G 128GB arrived, to flash twrp on it i had to enable oem unlock and usb debugging first in develeoper options.
To do that i had to complete the setup first, it's sick that the phone did NOT even let me complete the setup without connecting to the internet... this is out of control.
Now, i have oem unlock enabled aswell as usb debugging.
{
"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"
}
Next i connect the phone to PC and booted in download / odin mode.
Then i tried to flash this a33x_experimental_twrp.tar created by Zillion with odin, however as you can see on the next screenshot... the phone says "Custom Binary Blocked by OEM Lock"...
Why does the Phone say Custom Binary Blocked by OEM Lock even when i have it enabled in developer options??!
The Phone-Model is SM-A336B/DSN if that matters? I contacted my service provider from who i bought this phone and they told me that they are selling only this model.
Any help is welcome ...
My last hope is that someone from this forum can help me get twrp and lineage running, otherwise i'll have no choice but to return the phone within 14 days. No way i will use this device with the sick psycho spyware it contains.
PS: My only idea that might be worth a shot is booting twrp from adb terminal on pc, but i'm not sure how that works, how do i flash twrp permanently and how do i flash lineageos from adb, while i might be able to flash lineageos i'm not sure if that would work with the stock recovery..?
You have to unlock your bootloader to be able to flash custom images such as TWRP. When in download mode, hold Volume + until the unlock screen appears. This will wipe data.
After you've unlocked the bootloader, you will need to boot to Android, connect to the Internet, and verify that OEM Unlocking is still visible in Developer Options. If it isn't, Vaultkeeper is not yet disabled and flashing custom images will result in boot failure.
V0latyle said:
You have to unlock your bootloader to be able to flash custom images such as TWRP. When in download mode, hold Volume + until the unlock screen appears. This will wipe data.
After you've unlocked the bootloader, you will need to boot to Android, connect to the Internet, and verify that OEM Unlocking is still visible in Developer Options. If it isn't, Vaultkeeper is not yet disabled and flashing custom images will result in boot failure.
Click to expand...
Click to collapse
Thanks for the info, i tried doing as you told boot in downloadmode and hold volume up untill unlockscreen appears, i'f been holding volume up for over 20 seconds but nothing happens.
Not that i doubt your instructions but are you sure this has to be done in downloadmode and not recovery?
Or do i have to press another button instead? Vol + doesn't seem to do anything.
You can also use Adb ( Adb reboot download)
Privacydroid said:
Thanks for the info, i tried doing as you told boot in downloadmode and hold volume up untill unlockscreen appears, i'f been holding volume up for over 20 seconds but nothing happens.
Not that i doubt your instructions but are you sure this has to be done in downloadmode and not recovery?
Or do i have to press another button instead? Vol + doesn't seem to do anything.
Click to expand...
Click to collapse
Yes, I am sure, bootloader unlock is never done through recovery.
Turn your device off completely with USB disconnected. Leave it off for a minute or so. Then, hold both Volume buttons (DO NOT press Power) and plug in the USB cable from your computer.
This should start the device in Download mode.
Now, hold Volume Up until the bootloader unlock screen appears, which should have an instruction to either press or hold Volume Up to unlock the bootloader.
V0latyle said:
Yes, I am sure, bootloader unlock is never done through recovery.
Turn your device off completely with USB disconnected. Leave it off for a minute or so. Then, hold both Volume buttons (DO NOT press Power) and plug in the USB cable from your computer.
This should start the device in Download mode.
Now, hold Volume Up until the bootloader unlock screen appears, which should have an instruction to either press or hold Volume Up to unlock the bootloader.
Click to expand...
Click to collapse
Thank you Sir. i totally forgot about the bootloader, and i didn't know how it works on the newer models (android 12), thanks to your easy insturctions i was able to unlock the bootloader.
V0latyle said:
You have to unlock your bootloader to be able to flash custom images such as TWRP. When in download mode, hold Volume + until the unlock screen appears. This will wipe data.
After you've unlocked the bootloader, you will need to boot to Android, connect to the Internet, and verify that OEM Unlocking is still visible in Developer Options. If it isn't, Vaultkeeper is not yet disabled and flashing custom images will result in boot failure.
Click to expand...
Click to collapse
I think the bootloader was sucessfully unlocked, just want to mention that after doing that (and the phone was erased) i do not see the oem unlock option under develeoper settings, all other options seem to be listed as normal.
So you are saying i must take care of vaultkeeper before finally flashing lineageos?
How would i handle that?
Privacydroid said:
I think the bootloader was sucessfully unlocked, just want to mention that after doing that (and the phone was erased) i do not see the oem unlock option under develeoper settings, all other options seem to be listed as normal.
So you are saying i must take care of vaultkeeper before finally flashing lineageos?
How would i handle that?
Click to expand...
Click to collapse
See Magisk installation instructions:
Unlocking the bootloader on modern Samsung devices have some caveats. The newly introduced VaultKeeper service will make the bootloader reject any unofficial partitions in some circumstances.
Allow bootloader unlocking in Developer options → OEM unlocking
Reboot to download mode: power off your device and press the download mode key combo for your device
Long press volume up to unlock the bootloader. This will wipe your data and automatically reboot.
Go through the initial setup. Skip through all the steps since data will be wiped again in later steps. Connect the device to Internet during the setup.
Enable developer options, and confirm that the OEM unlocking option exists and is grayed out. This means the VaultKeeper service has unleashed the bootloader.
Your bootloader now accepts unofficial images in download mode
Click to expand...
Click to collapse
If OEM Unlocking is not visible, Vaultkeeper has not unleashed the bootloader yet and you must fix this before proceeding. Look for "KG STATUS" on the screen when your device is in download mode; if this says "PRENORMAL" you cannot flash a custom image. If it says "CHECKING" you should be fine to flash TWRP, and once you flash TWRP, you can install LineageOS.
V0latyle said:
See Magisk installation instructions:
If OEM Unlocking is not visible, Vaultkeeper has not unleashed the bootloader yet and you must fix this before proceeding. Look for "KG STATUS" on the screen when your device is in download mode; if this says "PRENORMAL" you cannot flash a custom image. If it says "CHECKING" you should be fine to flash TWRP, and once you flash TWRP, you can install LineageOS.
Click to expand...
Click to collapse
Well, i tried flashing twrp right now without using magsik, might have been a bad idea.. there's some error now.
Not really a surprise.. i never managed to brick a phone by all the idiotic things i'f done, no clue how to perceed now as the phone keep rebooting to the exact same screen with the exact same error message.
Did i damage the recovery?
You seem softbricked. You can always flash stock recovery. What happens when you try to boot to system? Is it just stuck in Odin mode?
Arealhooman said:
You seem softbricked. You can always flash stock recovery. What happens when you try to boot to system? Is it just stuck in Odin mode?
Click to expand...
Click to collapse
How do i boot to system? Just hold power button? Yes it keeps booting to odin mode, it does not even allow me to shutdown, keep booting to Odin.
Remember when you could simply unplug the battery...
Can i use Frija to download stock recovery or is it only for the "system os"?
Privacydroid said:
How do i boot to system? Just hold power button? Yes it keeps booting to odin mode, it does not even allow me to shutdown, keep booting to Odin.
Remember when you could simply unplug the battery...
Can i use Frija to download stock recovery or is it only for the "system os"?
View attachment 5790277
Click to expand...
Click to collapse
Yes.
Guide to Extract Stock Recovery:
First, download the preferred Samsung stock firmware for your device model.
Extract the firmware zip file on your computer within a folder.
Open the .tar.md5 file using 7Zip. (Download 7Zip)
You will find the ‘recovery.img’ file. This is the stock recovery file for your Samsung device. Select it and hit Extract.
Compress the recovery image file via 7Zip tool in “.tar” format.
Put your Samsung device in Odin Download mode, select ‘AP’ or ‘PDA’ in Odin tool and select the new recovery.tar file, then hit the Start button.
(credit to Getdroidtips)
Btw its in the AP file
Given that TWRP for this device is experimental, this is pretty unsurprising.
Unfortunately without TWRP you won't be able to install LineageOS, unless there's another way I'm not aware of
V0latyle said:
Given that TWRP for this device is experimental, this is pretty unsurprising.
Unfortunately without TWRP you won't be able to install LineageOS, unless there's another way I'm not aware of
Click to expand...
Click to collapse
After re-flashing the stock firmware i checked the KG-STATUS and it says "broken"
Indeed the twrp i tried to flash is experimental and made by @Zillion
Might sound like a stupid question, people like andy yan appear to provide GSI's (generic system images) just curious if the same would be possible with twrp? A generic twrp image that is compatible with any/most devices? Basically, if mr Zillions twrp does not function yet, what other twrp could i try?
Arealhooman said:
Yes.
Guide to Extract Stock Recovery:
First, download the preferred Samsung stock firmware for your device model.
Extract the firmware zip file on your computer within a folder.
Open the .tar.md5 file using 7Zip. (Download 7Zip)
You will find the ‘recovery.img’ file. This is the stock recovery file for your Samsung device. Select it and hit Extract.
Compress the recovery image file via 7Zip tool in “.tar” format.
Put your Samsung device in Odin Download mode, select ‘AP’ or ‘PDA’ in Odin tool and select the new recovery.tar file, then hit the Start button.
(credit to Getdroidtips)
Click to expand...
Click to collapse
Thanks, i managed to re-flash the stock firmware!
I actually didn't want to whole system (the os) the be re-flashed but only the recovery, however when i extract the AP file i do not get any recovery.img file.
`
Edit: i see recovery.img.lz4 (can i use that aswell to re-flash stock recovery, i never saw .lz4 whatever that is.
I tried flashing twrp with odin by placing it in the AP slot, so since that didn't work would it be worth a shot trying to flash it with adb via pc instead? Or is magisk a hard requirement now to bypass Vaultkeeper to be able and flash twrp?
V0latyle said:
Given that TWRP for this device is experimental, this is pretty unsurprising.
Unfortunately without TWRP you won't be able to install LineageOS, unless there's another way I'm not aware of
Click to expand...
Click to collapse
actually theres a way of repacking using lz4 images, but i dont really know how to do it
Privacydroid said:
After re-flashing the stock firmware i checked the KG-STATUS and it says "broken"
View attachment 5790319
Indeed the twrp i tried to flash is experimentla and made by @Zillion
Might sound like a stupid question, people like andy yan appear to provide GSI's (generic system images) just curious if the same would be possible with twrp? A generic twrp image that is compatible with any/most devices? Basically, if mr Zillions twrp does not function yet, what other twrp could i try?
Click to expand...
Click to collapse
Wich device is that
*A33 TWRP was never meant for final users
The latest build was just a testing one