[BOOTLOADER UNLOCKED][H440N] LG Spirit

[pvineeth97]

Hi guys!

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

Disclaimer:

/*
* 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.
*/

No more secure boot error!

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

-> Steps:

(1) Downgrade to v10f version of Android.
(2) Root your device.
(3) Download this patched aboot file. Click Here
(4) Connect your phone to the computer. In command prompt, type "adb shell".
(5) Transfer the aboot file into /sdcard/ folder.
(6) Type "su" to enter the root shell. Then type "dd if=/sdcard/aboot_v10f.bin of=/dev/block/<your aboot partition>".
(7) Restart your phone by typing "reboot".

You have unlocked your bootloader!

If you get a black screen there is a problem with your recovery.

For more detailed guide. Follow this by @Korelev.

Refer Notes for more information.

-> Notes:
1) The aboot_v10f.bin 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.

 

[Korelev]

Hi guys!

Hi there! I tried your method an followed fobos explanation to found the required block (which is mmcblk0p5 in this case) but i'm still getting secure boot error when I try to get into TWRP, as far as I understand that shouldn't happen.

any ideas of what can I do to?

 

[pvineeth97]

Hi there! I tried your method an followed fobos explanation to found the required block (which is mmcblk0p5 in this case) but i'm still getting secure boot error when I try to get into TWRP, as far as I understand that shouldn't happen.

any ideas of what can I do to?

Did you downgrade your firmware as I told you in the guide?

 

[pvineeth97]

Hi there! I tried your method an followed fobos explanation to found the required block (which is mmcblk0p5 in this case) but i'm still getting secure boot error when I try to get into TWRP, as far as I understand that shouldn't happen.

any ideas of what can I do to?

First you have to flash the patched aboot and then flash TWRP. @Fobos needs to correct it.

After you finish flashing the TWRP. Run these commands on terminal/command line:

adb shell
su
cd /cache/recovery/
echo "--show_text" >> command
chmod 644 command
reboot recovery

I used the same method on my phone. It works!

 

[Korelev]

First you have to flash the patched aboot and then flash TWRP. @Fobos needs to correct it.

After you finish flashing the TWRP. Run these commands on terminal/command line:


I used the same method on my phone. It works!

yeah, I downgraded
Oh, ok. I'll reflash everything then report. Many thx

 

[pvineeth97]

yeah, I downgraded
Oh, ok. I'll reflash everything then report. Many thx

I edited the post. Refer to it again.

 

[Korelev]

I edited the post. Refer to it again.

done, I'm on it

---------- Post added at 08:54 PM ---------- Previous post was at 08:09 PM ----------

Did you downgrade your phone to v10f as mentioned in the guide?

First you have to flash the patched aboot and then flash TWRP. @Fobos needs to correct it.

After you finish flashing the TWRP. Run these commands on terminal/command line:

adb shell
su
cd /cache/recovery/
echo "--show_text" >> command
chmod 644 command
reboot recovery

I used the same method on my phone. It works!

No luck, the message remains, I'm able to get into stock recovery but as soon as I flash TWRP there's the verity message
Do I have to reboot after aboot is replaced in order to flash twrp?

 

[mayankjet]

Hi guys!

Disclaimer:


No more secure boot error!

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

-> Steps:

(1) Downgrade to v10f version of Android.
(2) Root your device.
(3) Download this patched aboot file. Click Here.
(4) Connect your phone to the computer. In command prompt, type "adb shell".
(5) Transfer the aboot file into /sdcard/ folder.
(6) Type "su" to enter the root shell. Then type "dd if=/sdcard/aboot_v10f.bin of=/dev/block/<your aboot partition>".
(7) Restart your phone by typing "reboot".

You have unlocked your bootloader!

For more detailed guide. Follow this by @Fobos531.

Refer Notes for more information.

-> Notes:
1) The aboot_v10f.bin 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.

Not working man. Still getting the secure boot error as i boot into twrp :crying:
Any suggestions?

 

[cerg2010cerg2010]

Not working man. Still getting the secure boot error as i boot into twrp :crying:
Any suggestions?

Please try this: https://yadi.sk/d/1Dw4_bod3EgUMU

 

[Korelev]

Please try this: https://yadi.sk/d/1Dw4_bod3EgUMU

I'll give it a try!

Edit: I think that might be it! I get a black screen but no secure error msg. I'll give it another try

Edit2: OMG it works! It seems to be an issue with TWRP, CWM actually boots! I'll update

 

[Fobos531]

Please try this: https://yadi.sk/d/1Dw4_bod3EgUMU

I'm trying this right now and seems to hang for me when I reboot into recovery.

edit: I'm able to boot into the system normally. Will try to reboot into recovery again.

edit 2: Multiple people have confirmed that, when using this aboot and rebooting into recovery, they only get a black screen and it stays like that. the secure boot error ISN't there.

 

[mayankjet]

I'll give it a try!

Edit: I think that might be it! I get a black screen but no secure error msg. I'll give it another try

Edit2: OMG it works! It seems to be an issue with TWRP, CWM actually boots! I'll update

Im also getting a black screen. How did you fix that, seems like an issue with twrp itself, right ?

 

[Korelev]

Im also getting a black screen. How did you fix that, seems like an issue with twrp itself, right ?

SEEMS to be so, I can't confirm because I just found out CWM boots, but probably since many people reported the same according to fobos

anyway, no secure boot error so I guess we're fine

 

[mayankjet]

SEEMS to be so, I can't confirm because I just found out CWM boots, but probably since many people reported the same according to fobos

anyway, no secure boot error so I guess we're fine

Thanks dude , it finally booted into cwm but it takes unusually long to boot into cwm.Cheers mate

 

[Korelev]

Thanks dude , it finally booted into cwm but it takes unusually long to boot into cwm.Cheers mate

glad to hear!

 

[pvineeth97]

glad to hear!

If you get a black screen there is a problem with your recovery. Enjoy

 

[pvineeth97]

I'm trying this right now and seems to hang for me when I reboot into recovery.

edit: I'm able to boot into the system normally. Will try to reboot into recovery again.

edit 2: Multiple people have confirmed that, when using this aboot and rebooting into recovery, they only get a black screen and it stays like that. the secure boot error ISN't there.

There is a problem with your recovery. Edit your detailed guide. First flash patched aboot then flash TWRP/CWM.

 

[Korelev]

There is a problem with your recovery.

We figured out CWM recovery works, so the aboot provided by your friend made the trick

 

[pvineeth97]

We figured out CWM recovery works, so the aboot provided by your friend made the trick

Made some changes in patched aboot. I updated that link into the main post. Enjoy XD

 

[Korelev]

Made some changes in patched aboot. I updated that link into the main post. Enjoy XD

Thanks man, I think I can speak for almost everyone here if I say we thought this phone was dead for good. We probably will make a thread with detailed explanations and give all the credit to you and your friend, you might as well leave us a donate link in case anyone wants to.

again, thanks a lot!