• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[GUIDE][BOOTLOADER UNLOCKED][QUALCOMM] Bootloader is unlocked!

Search This thread

pvineeth97

Senior Member
Nov 1, 2015
1,251
933
St. Louis
Hi guys!

This thread is in the news! http://www.tudocelular.com/android/noticias/n88568/kg-k10-bootloader.html

You can donate to me here https://www.paypal.me/penvineeth and @cerg2010cerg2010 through paypal.
@cerg2010cerg2010 PAYPAL EMAIL: [email protected] OR QIWI: +79157840294

Disclaimer:

Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired. Please
* do some research if you have any concerns about features included in this Recovery
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/

Bootloader is unlocked in LG K420DS and LG K420N!

No more secure boot error! :D

I thank my friend @cerg2010cerg2010 for helping me out in patching the aboot.

-> Requirements:
(1) LG UP
(2) Device must be: LG K420DS OR LG K420N

-> Steps:

(1) Download this ROM: Click Here
(2) Flash it using LG UP. Choose the refurbish option.
(3) Root your device using KingORoot.
(4) Download this patched aboot file: https://yadi.sk/d/HLZy5fo33EEUcL
(5) Connect your phone to the computer. In command prompt, type "adb shell".
(6) Transfer the aboot file into /sdcard/ folder.
(7) Type "su" to enter the root shell. Then type "dd if=/sdcard/aboot_patched.img of=/dev/block/mmcblk0p7".
(8) Restart your phone by typing "reboot".

You have unlocked your bootloader!

Refer Notes for more information.

-> Booting into TWRP:


-> Notes:
1) The aboot_patched.img is the patched version of aboot partition of your device. Secure boot validation has been patched such that secure boot is always valid, so you can flash your own TWRP and Custom ROM.
2) Don't upgrade to any updated version of Android if you get any through OTA update. It might brick your device.
3) This version of aboot does'nt have fastboot. So don't try nuking LAF and check if fastboot exists. If you did, you bricked your device.
 
Last edited:

Professor Woland

Senior Member
Mar 10, 2016
353
55
Redmi Note 9 Pro
I think you were the one who was fighting against me on posting topics about LG K8. No questions answered for now. Enjoy the moment! See the video.

Wrong you have fighting aginst me because I posted k8 question, you are behaving like forum is your personal property, you have serious problem.. Why do you post something if you don't want to explain how you done that? How old are you, like 10?
 
  • Like
Reactions: ArcherEmiya

pvineeth97

Senior Member
Nov 1, 2015
1,251
933
St. Louis
Wrong you have fighting aginst me because I posted k8 question, you are behaving like forum is your personal property, you have serious problem.. Why do you post something if you don't want to explain how you done that? How old are you, like 10?

First understand. I did'nt post the complete guide because I am doing some more work on it. OK? Moreover, do you see how much time it would take to do all this? Did you unlock the bootloader?

I have no obligation to answer each and every question you ask me. I will answer when I want to.

I hope you can read English

 
Last edited:
  • Like
Reactions: Sands207

AngryUserLG

Senior Member
Oct 12, 2015
76
5
LG K10
LG V30
wait Kingroot? thought LG devices on M wasnt able to support one click root solutions from what i was told and root install was supposed to be hard plus i even used Kingroot on K10 it worked but ended with a boot verification fail the next day, so what happened with yours?
 

Professor Woland

Senior Member
Mar 10, 2016
353
55
Redmi Note 9 Pro
wait Kingroot? thought LG devices on M wasnt able to support one click root solutions from what i was told and root install was supposed to be hard plus i even used Kingroot on K10 it worked but ended with a boot verification fail the next day, so what happened with yours?

Well about "boot verification fail" :
Thats because of aboot, in first post you have patched version, when you flash it there won't be that error anymore. About king(o)root, I don't know I avoid one click roots ad much as possible, but if it's the only way than it should be considered.

@ OP
Well nice one.
What are the changes on patched aboot image, I'll need to know method so I can patch it for my device, that's why I ask..?
 

Fobos531

Retired Forum Moderator
Oct 6, 2014
1,029
440
/home/
First understand. I did'nt post the complete guide because I am doing some more work on it. OK? Moreover, do you see how much time it would take to do all this? Did you unlock the bootloader?

I have no obligation to answer each and every question you ask me. I will answer when I want to.

I hope you can read English

Let me get something straight.

The OP states that the bootloader is unlocked on the K420N variant. According to GSMArena, the K420N variant has the "Qualcomm MSM8916 Snapdragon 410" chipset. Please tell me, is it possible to unlock the bootloader for this specific variant (with Snapdragon 410 chipset) ?

If yes, can you please explain how did you unlock the bootloader? Did you get hold of a developer aboot? Or something else?
 
Last edited:

pvineeth97

Senior Member
Nov 1, 2015
1,251
933
St. Louis
Let me get something straight.

The OP states that the bootloader is unlocked on the K420N variant. According to GSMArena, the K420N variant has the "Qualcomm MSM8916 Snapdragon 410" chipset. Please tell me, is it possible to unlock the bootloader for this specific variant (with Snapdragon 410 chipset) ?

If yes, can you please explain how did you unlock the bootloader? Did you get hold of a developer aboot? Or something else?

K420N has the Qualcomm Snapdragon 410. Yes this is bootloader unlock is for this model. This is not a developer aboot. Patched it against secure boot validation so secure boot is always valid no matter what recovery or custom rom is installed.
 
Last edited:

pvineeth97

Senior Member
Nov 1, 2015
1,251
933
St. Louis
Well about "boot verification fail" :
Thats because of aboot, in first post you have patched version, when you flash it there won't be that error anymore. About king(o)root, I don't know I avoid one click roots ad much as possible, but if it's the only way than it should be considered.

@ OP
Well nice one.
What are the changes on patched aboot image, I'll need to know method so I can patch it for my device, that's why I ask..?

Changes? Well it depends on the aboot image. Well for our aboot image we had to find out the secure boot validation function and keep it valid always. Luckily our patched aboot worked or else the phone is a complete brick if you ever flashed a corrupt aboot. Send me your aboot image so I and my friend can patch it and enable fastboot and oem unlock.
 

Professor Woland

Senior Member
Mar 10, 2016
353
55
Redmi Note 9 Pro
Changes? Well it depends on the aboot image. Well for our aboot image we had to find out the secure boot validation function and keep it valid always. Luckily our patched aboot worked or else the phone is a complete brick if you ever flashed a corrupt aboot. Send me your aboot image so I and my friend can patch it and enable fastboot and oem unlock.

So if I screw something I brick phone completly? Ok I get it, with what software did you used to unpack aboot (does boot.img unpac/repack tools work)? Well I don't have aboot since device is mtk, on mmcblk0p7 is lk not aboot, so I would prefer to do it myself so if I screw I know it's my fault.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 15
    Hi guys!

    This thread is in the news! http://www.tudocelular.com/android/noticias/n88568/kg-k10-bootloader.html

    You can donate to me here https://www.paypal.me/penvineeth and @cerg2010cerg2010 through paypal.
    @cerg2010cerg2010 PAYPAL EMAIL: [email protected] OR QIWI: +79157840294

    Disclaimer:

    Code:
    /*
    * Your warranty is now void.
    *
    * I am not responsible for bricked devices, dead SD cards,
    * thermonuclear war, or you getting fired. Please
    * do some research if you have any concerns about features included in this Recovery
    * before flashing it! YOU are choosing to make these modifications, and if
    * you point the finger at me for messing up your device, I will laugh at you.
    */

    Bootloader is unlocked in LG K420DS and LG K420N!

    No more secure boot error! :D

    I thank my friend @cerg2010cerg2010 for helping me out in patching the aboot.

    -> Requirements:
    (1) LG UP
    (2) Device must be: LG K420DS OR LG K420N

    -> Steps:

    (1) Download this ROM: Click Here
    (2) Flash it using LG UP. Choose the refurbish option.
    (3) Root your device using KingORoot.
    (4) Download this patched aboot file: https://yadi.sk/d/HLZy5fo33EEUcL
    (5) Connect your phone to the computer. In command prompt, type "adb shell".
    (6) Transfer the aboot file into /sdcard/ folder.
    (7) Type "su" to enter the root shell. Then type "dd if=/sdcard/aboot_patched.img of=/dev/block/mmcblk0p7".
    (8) Restart your phone by typing "reboot".

    You have unlocked your bootloader!

    Refer Notes for more information.

    -> Booting into TWRP:


    -> Notes:
    1) The aboot_patched.img is the patched version of aboot partition of your device. Secure boot validation has been patched such that secure boot is always valid, so you can flash your own TWRP and Custom ROM.
    2) Don't upgrade to any updated version of Android if you get any through OTA update. It might brick your device.
    3) This version of aboot does'nt have fastboot. So don't try nuking LAF and check if fastboot exists. If you did, you bricked your device.
    8
    Thread Cleaned. Keep it to the discussion of the topic, slandering can be taken to those social media sites. Keep Development talk to just that....
    4
    I guess you can use this tool: https://technet.microsoft.com/en-us/sysinternals/bb897441

    EDIT: I just used it to check v10f aboot signature and the aboot seems to be unsigned. I may be completely wrong though.
    @pvineeth97 are there any news?

    Use IDA PRO Diassembler to check if your aboot is signed or not! I am kinda busy in publishing my project I will be back and send you the patched aboot.
    3
    How I switched to SuperSU.

    How did you replace Kingoroot with Supersu?

    I flashed this KDZ.
    Rooted it with KingoRoot.
    Flashed patched aboot.img, but like I think it's not required. I flashed it by typing "dd if=/sdcard/aboot_patched.img of=/dev/block/mmcblk0p7" command in Android Terminal Emulator App, I don't like to use PC.
    Then I downloaded ChainFire SuperSU from GooglePlay.
    On first application start it will ask to install su Binary, say Yes.
    Wait about 5 minutes or until it fails…
    If so, don't worry, be happy
    Reboot…
    Try again.
    It must ask for Root Authorization!
    Continue Rebooting and tying again and again, until you see su binary installed successfully!
    Now you can dance, you Switched to SuperSU ;)
    After that you can remove all KingoRoot sh**t and install SuperSU like System app in application options…
    I'm still experimenting with this rom, so I'm keeping KingRoot and SuperSU apps, for reroot my device if I will reflash KDZ.
    3
    Currently I have v20a(Marshmallow), but that doesn't matter since I can flash any v10x (Lolipop) firmware whenever I want.

    Both v10e and v10f firmwares are rootable and are based on Lolipop. Here's another aboot for you to try, this time from v10a firmware: https://www.dropbox.com/s/wd89nc77zh3kyz1/aboot_5120.bin?dl=0

    Please try all aboots and see if any of them can be safely patched. Thanks.

    Ok.