Develop Bugs

[HOW TO][LTE] Revert to original 4.0.1 STOCK on Windows

Hello, I did some searching and didn't see anything like this for Windows.
** NOTE: This requires the ADB and bootloader drivers to be installed already **
Google released the original 4.0.1 firmware (including radios and bootloader) in a compressed .tgz file. You can get that here:
https://dl.google.com/android/aosp/mysid-itl41d-factory-516b56c2.tgz
Extract the file into a working directory. Then... extract this (attached) into that directory as well.
Either reboot to bootloader manually or turn on USB Debugging, then run flash-all.bat and everything should go from there!
This is just a modified version of the script Google sent along with the package, so there shouldn't be any issues.
Tested the script on my own phone, and it completed twice. So it should be safe. But as always, you assume the risk!

Thanks, this worked for me. However, it does not re-lock the bootloader. You can tell by when the Google logo is on the screen while booting up, if there is an unlocked lock on the bottom then it is unlocked. To fix this, type in:
flashboot oem lock
Click to expand...
Click to collapse
After that you should be good to go again and be stock.

Why not use the 4.0.2 image? Makes more sense to use the latest version:
https://dl.google.com/dl/android/aosp/mysid-icl53f-factory-65895fa8.tgz

I get a "Missing adbwinapi.dll" error when trying to use your .bat? How do I ensure ADB is installed correctly?

Zzim said:
I get a "Missing adbwinapi.dll" error when trying to use your .bat? How do I ensure ADB is installed correctly?
Click to expand...
Click to collapse
If you've got the SDK installed put the fastboot files in the sdk\tools or sdk\platform folder where adb is located. The adbwinapi.dll should be located in there.
Or just copy adbwinapi.dll into the same folder where you have the "restore kit" files downloaded from the OP.

confirmed working bailed me out on a bootloop when trying to root my CDMA Verizon Galaxy Nexus

error
i have the flash.all file in my platform tools but i got an error device not recognnized message?
how do i get this file in zip form?
https://dl.google.com/android/aosp/m...y-516b56c2.tgz

djeddieone said:
confirmed working bailed me out on a bootloop when trying to root my CDMA Verizon Galaxy Nexus
Click to expand...
Click to collapse
cerotes have galaxy nexuses? hrm

mikedfromaz said:
i have the flash.all file in my platform tools but i got an error device not recognnized message?
how do i get this file in zip form?
https://dl.google.com/android/aosp/m...y-516b56c2.tgz
Click to expand...
Click to collapse
Winzip.. unzip it twice...
Sent from my Galaxy Nexus using XDA App

edit: got it thanks

Thank you for the script..i know it will come in handy one day or another!
Sent from my Galaxy Nexus using xda premium

whenever i try to extract the files using winzip it says it can't read the header etc etc. Any ideas?

bigeric828 said:
whenever i try to extract the files using winzip it says it can't read the header etc etc. Any ideas?
Click to expand...
Click to collapse
It was zipped with WinRAR as a standard zip file. Should be able to be opened on just about anything... Have you tried redownloading?

oops already posted this but i put it in the wrong thread but here it is again sorry.
does anyone know how i can get this working? whenever i run it i just get an error: device not found
waiting for bootloader...
flashing bootloader...
error cannot load "bootloader-toro-primek10.img"
<waiting fo device>
anyone suggestion? ive tried reinstalling the drivers and its still not working
any help is appreciated thanks

so.....how do we run the script? with fastboot? with what commmands? it's late, i'm tired and i just want to start from scratch on my GNex...had Wallet running, then loaded BB, lost Wallet, now wallet won't run on ANY rom i have, even rebuilt to 4.0.2, but need to get back to 4.0.1...i posted a question in the Q&A section if there was an ODIN of 4.0.1 lying around somewhere....hopefully i'll get some help either way...
thanks.
EDIT...got it, double click the bat file...the original post did not say that.....thanks for the last post for mentioning it

|Jason8| said:
Hello, I did some searching and didn't see anything like this for Windows.
** NOTE: This requires the ADB and bootloader drivers to be installed already **
Google released the original 4.0.1 firmware (including radios and bootloader) in a compressed .tgz file. You can get that here:
https://dl.google.com/android/aosp/mysid-itl41d-factory-516b56c2.tgz
Extract the file into a working directory. Then... extract this (attached) into that directory as well.
Either reboot to bootloader manually or turn on USB Debugging, then run flash-all.bat and everything should go from there!
This is just a modified version of the script Google sent along with the package, so there shouldn't be any issues.
Tested the script on my own phone, and it completed twice. So it should be safe. But as always, you assume the risk!
Click to expand...
Click to collapse
Having seen the Nexus S sticky for factory firmware etc., I think its time we see this or another post evolve into the same sort of thing including full restores for 4.0.1, 4.0.2 and the eventual 4.0.3(lte) radio's etc.,

Here's a modified script that will allow you to choose between 4.0.1 and 4.0.2. (as long as you have either image or both) It also has the option to re-lock the bootloader.
I'll also update it when the official 4.0.3 images are released.
I don't take no credit for what was already done, I just modified 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"
}
Instructions:
=========
1- Extract folder with contents of this package.
2- You will need the Google Factory image for the version you want to restore, or both if you want.
3- Extract the image files to the same folder in step one. Image files should not be in a seperate folder!
So you should have, in one folder, the above files contained in this package plus:
image-mysid-xxxxxx.zip (xxxxxx= pertains to what version)
radio-tor-i515.xxxx.img
radio-cdma-tor-i515.xxxx.img
flash-all.sh
bootloader-tor-primexxxx.img
4- Dbl click on GNexRestore.bat and follow the prompts.
Optionally, if you do have the Android SDK installed, just copy the image files and GNexRestore.bat to the platform-tools folder.
fastboot.exe will also be needed, if you don't have it already, just copy the one in this package to the same location.
Then run GNexRestore.bat

when you extraxt the factory image i get one file and the icon looks like a blank piece of paper. is that how it is suppose to be

When you extract the image, you should see a folder with the files you need.
e.g. this is from 4.0.2

Flashing Gio from ODIN with .tar.md5

I dowloaded my stock firmware from samfirmware.com and now i would like to flash it. It is a single tar.md5 package. I would like to known how to flash it. I searched, but it was not much help to me. Do i use the single package option in ODIN?
- i have never used odin, but i have flashed alot of roms so im not completely stupid when it comes to this stuff.

Yes, one package

Once you have Odin
To do so
The file "GIO_v0.1.ops"
You will find in the package of Odin
{
"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"
}
You put the file you downloaded md5
How do you see "PASS!" disconnect and if appears
"Close serial port and wait until rebooting" a disconnect, and wait until the phone turns on, of course, disconnect the cable.
It says Samsung on the phone remove the battery and enter the Recovery Menu
select "wipe"
select reboot
READY
I already have the new rom

Is it possible to unzip the rom with 7zip and remove the recovery image so i can still have my custom recovery?

AlwaysDroid said:
Is it possible to unzip the rom with 7zip and remove the recovery image so i can still have my custom recovery?
Click to expand...
Click to collapse
Ypu can but must be able to do a md5sum or flash as .tar without md5 check
Sent from my GT-S5660 using xda premium

Cant find?
voetbalremco said:
Ypu can but must be able to do a md5sum or flash as .tar without md5 check
Sent from my GT-S5660 using xda premium
Click to expand...
Click to collapse
Im trying to flash a file called S5660MUGKG3_S5660MBMCKG3_BMC. When ever i try to one package i cant seem to find it? Can anyone help me with this?

Did you unzip it?
If you haven't already, please check "show extensions for known file types" in your Windows Explorer settings.

Darkshado said:
Did you unzip it?
If you haven't already, please check "show extensions for known file types" in your Windows Explorer settings.
Click to expand...
Click to collapse
How do I unzip it? Can I use winrar and extract?

Darkshado said:
Did you unzip it?
If you haven't already, please check "show extensions for known file types" in your Windows Explorer settings.
Click to expand...
Click to collapse
Yay I got it!
Thanks for your help!
Is it fine if it says 1 (COM10) ? and also its keeps on showing the boot animations over over... wont go further and on odin it says pass. should i keep on waiting or is somthing wrong? is it bricked?

1 (COM10) is simply to indicate the serial port number assigned to your phone by Windows and the Samsung USB driver in Odin.
Your phone is boot looping, some might consider this a soft brick. My best guess is that you previously installed a ROM that formatted your /data and /cache partitions from the stock RFS format to ext4 instead. The stock 5660M ROM doesn't support ext4.
Reboot in the stock recovery, either with "adb reboot recovery" or by using the home and power keys simultaneously.
From there, wipe user data and cache, or something similar I don't recall the exact wording, but I do remember they were two separate commands.
Reboot, should work now. Use ddms (part of the Android SDK) to see what's going on under the hood if you feel like it.
I take it computers are a relatively new thing for you to ask how to unzip files. My best advice: make very regular backups and read instructions carefully. Losing data is not cool. Losing someone else's data is worse. (I'm guessing you're on the family computer here...)

[TOOL] Verizon HTC One Splash Image Creator

With all the splash screen discussion and threads popping up, I decided it was time to make a tool which could help users create and flash their own splash screens.
Verizon HTC One Splash Image Creator
This simple Windows command-line tool allows the creation of splash images, which are automatically converted to zip files and placed in the 'flash' folder, ready to be flashed, which can be flashed by the second option. It also allows the backing-up of your current splash image, as well as extracting the image from custom '.img' files.
Instructions:
S-OFF is required for this to function!
Everything needed is included aside from the image you want to be a splash screen, and the on-screen directions are quite straight-forward.
Unzip it to a location you can easily find and run 'splash.bat'. If necessary, run it as Administrator.
Make sure you maintain the folder structure as it is in the zip.
DISCLAIMER:
This tool consists of several files, most of which I didn't create. Specifically, it includes the most up-to-date ADB and Fastboot files, along with the FFMPEG free software licensed under GPL, as well as 7-Zip, also licensed under GPL. I am not making money from this tool, therefore everything should be copacetic. All I'm doing is collecting them in one place, making it significantly easier to perform its specific function.
I can not be held responsible for your use of this tool. Flashing custom images generally can't brick your device, but if it does, the fault lies with you, the user. I am not liable. Use this tool at your own risk. This is for the Verizon HTC One only!
Screenshots:
{
"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"
}
Known Issues:
When creating a splash image, sometimes it asks you to specify whether the destination is a file or directory. It's a directory. I have overwrite and quiet mode on, so it shouldn't pop up and ask that. It only does it about 2 out of 30 times.
When flashing the splash zip, it sometimes tells me that fastboot flash isn't a valid command, despite it working without changing anything since the last time I ran it. I also tested it about 30 times, and it also only gave me that error twice. It immediately reboots and works again right after that without any modification.
Potential Limitations:
I have only been able to test this on the 1.10.605.8 software release. I don't know if you need to change the text in the android-info.txt file in the '/tools/' folder to the updated version or not. I would appreciate it if someone would test that for me who is currently on the new update.
Changelog:
Code:
v1.01 - Bux fix regarding folder structure.
v1.0 - Initial release.
Download:
http://d-h.st/OTD
Please let me know if you discover any bugs, or if you think you know why I have the two I have now. Also, let me know if it works on the .10 software update.

RESERVED

This isn't working for me. Its saying that '/tools/adb.exe' does not exist.

sebastianraven said:
This isn't working for me. Its saying that '/tools/adb.exe' does not exist.
Click to expand...
Click to collapse
Are you maintaining the folder structure as it is in the zip?
EDIT:
I did leave a bug in there regarding folder structure. I was operating from C:\ during testing, and left "C:" in there as part of the test for whether the needed files existed. If you were operating on a drive letter besides C:, it would throw that error. I removed that drive letter requirement. Please download version 1.01 and try it again from any drive letter you like.

IceDragon59 said:
Are you maintaining the folder structure as it is in the zip?
EDIT:
I did leave a bug in there regarding folder structure. I was operating from C:\ during testing, and left "C:" in there as part of the test for whether the needed files existed. If you were operating on a drive letter besides C:, it would throw that error. I removed that drive letter requirement. Please download version 1.01 and try it again from any drive letter you like.
Click to expand...
Click to collapse
Ok. Here's what I did:
Redownloaded the zip.
Unzipped and moved it to my C: drive to make this as simple as possible.
Ran as Administrator
Selected #2.
Got the same error.

sebastianraven said:
Ok. Here's what I did:
Redownloaded the zip.
Unzipped and moved it to my C: drive to make this as simple as possible.
Ran as Administrator
Selected #2.
Got the same error.
Click to expand...
Click to collapse
That's very odd. Are you placing a picture in the 'image' folder, using option #1 and converting it to the flashable zip, then trying to flash it? If there's no zip to flash, it throws an error, even though that's the wrong error.

ak074 said:
if this creates the .img to be flashed via hboot, then the android-info.txt will need to be changed to reflect the current version of the phone.
Click to expand...
Click to collapse
I know there is a way to fix it but yea it's better to be safe than sorry
on rezound I accidentally flashed a leaked one, so i couldn't flash any of these, we eventually figured out a way to fix it thankfully but it was a lesson learned

Good job man!
Worked great for me.
Thanks!

I would like to start using this tool, but I am using santods modded no-text hboot from the latest OTA...
What should the android-info.txt file have? do i just change the mainver?

peteschlabar said:
I would like to start using this tool, but I am using santods modded no-text hboot from the latest OTA...
What should the android-info.txt file have? do i just change the mainver?
Click to expand...
Click to collapse
I've used this with multiple ROMs and HBOOT versions, including the newest one, without altering anything in this program, and all worked without a problem. While I can't guarantee that that will always be the case, I haven't come across any problems as of yet. Flashing a splash image generally can't screw your phone up, but there are always exceptions. I really should update this tool with more specific instructions. Maybe I'll do that while I'm off over the holidays. To be specific in what I've tested it with, I've listed everything that I recall testing it with. I haven't seen it fail yet, and I haven't updated it since the original version.
ROMs tested with:
1.08.605.8
1.08.605.10
1.08.605.15
2.10.605.1
CM 10.2
HBOOTs tested with:
1.08.605.8 HBOOT 1.54.0000
1.08.605.10 HBOOT 1.54.0000
1.08.605.15 HBOOT 1.54.0000
2.10.605.1 HBOOT 1.55.0000
Santod's modded HBOOT 1.54.0000
RegawMOD Bootloader Customizer HBOOT 1.54.0000

Thanks! Worked great on 1.55hboot ViperOne 4.2.1 rom. Great work.

LG G3 D851 Hard Bricked after installing D855 firmware

Well I messed up while using TWRP and I'm unable to enter download mode or turn on the phone, my computer recognizes it as a LG COM port, but I can also recognize it as a Qualcomm HS-USB QDLoader 9008 by short circuiting. I tried the BoardDiag method, but I get "Failed during loading flash programmer".
And when I use LG Flash Tool I get "Model Information Check Fail!"
I really need help!

hi,if you uses lg flash tool that dealing with t.ot files and .ddl i will able to gelp you so i mean you must use tge lg flasg tool i have said it before not the .kds flash toll(2014) so try ti select the correct .tot filr of your for whick is d851 i think then rename the correct d851.ddl file to tge name of the d855 we flashed his rom by mistace and hopefully the flash tool will complete the flashing progress as he should i hope it nit fails as you said "cannt cgeck th model nomber" 2sd methid it to change tge name of your device to lg g3 i think if you dont know the lg flash tool or you dont have the nesserly files http://forum.xda-developers.com/showthread.php?t=2785089 read the second part of the thread (2015 methode) have a nice day

Yamen Nwilaty said:
hi,if you uses lg flash tool that dealing with t.ot files and .ddl i will able to gelp you so i mean you must use tge lg flasg tool i have said it before not the .kds flash toll(2014) so try ti select the correct .tot filr of your for whick is d851 i think then rename the correct d851.ddl file to tge name of the d855 we flashed his rom by mistace and hopefully the flash tool will complete the flashing progress as he should i hope it nit fails as you said "cannt cgeck th model nomber" 2sd methid it to change tge name of your device to lg g3 i think if you dont know the lg flash tool or you dont have the nesserly files http://forum.xda-developers.com/showthread.php?t=2785089 read the second part of the thread (2015 methode) have a nice day
Click to expand...
Click to collapse
I tried renaming the d851.dll to 855.dll but it still doesn't work. Always looks like this:
{
"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"
}

Yamen Nwilaty said:
hi,if you uses lg flash tool that dealing with t.ot files and .ddl i will able to gelp you so i mean you must use tge lg flasg tool i have said it before not the .kds flash toll(2014) so try ti select the correct .tot filr of your for whick is d851 i think then rename the correct d851.ddl file to tge name of the d855 we flashed his rom by mistace and hopefully the flash tool will complete the flashing progress as he should i hope it nit fails as you said "cannt cgeck th model nomber" 2sd methid it to change tge name of your device to lg g3 i think if you dont know the lg flash tool or you dont have the nesserly files http://forum.xda-developers.com/showthread.php?t=2785089 read the second part of the thread (2015 methode) have a nice day
Click to expand...
Click to collapse
What? Renaming the file change nothing, nice try though
---------- Post added at 08:13 PM ---------- Previous post was at 08:11 PM ----------
Akhlut_ said:
Well I messed up while using TWRP and I'm unable to enter download mode or turn on the phone, my computer recognizes it as a LG COM port, but I can also recognize it as a Qualcomm HS-USB QDLoader 9008 by short circuiting. I tried the BoardDiag method, but I get "Failed during loading flash programmer".
And when I use LG Flash Tool I get "Model Information Check Fail!"
I really need help!
Click to expand...
Click to collapse
That sound more like a hard brick, take a look at this: http://forum.xda-developers.com/lg-g3/general/fix-unbrick-lg-g3-stuck-qualcomm-hs-usb-t2933853

RapHaeL_4_4_4_ said:
That sound more like a hard brick, take a look at this: http://forum.xda-developers.com/lg-g3/general/fix-unbrick-lg-g3-stuck-qualcomm-hs-usb-t2933853
Click to expand...
Click to collapse
That's what I'm trying but I always get this:
If I retry I get:
So I need to keep reconnecting every time it fails.

Akhlut_ said:
That's what I'm trying but I always get this:
If I retry I get:
So I need to keep reconnecting every time it fails.
Click to expand...
Click to collapse
You have the latest drivers? and do you run it as administrator?

RapHaeL_4_4_4_ said:
You have the latest drivers? and do you run it as administrator?
Click to expand...
Click to collapse
I am running the exe as admin, and I installed the drivers from this post: http://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359 (64 Bit)

Akhlut_ said:
I am running the exe as admin, and I installed the drivers from this post: http://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359 (64 Bit)
Click to expand...
Click to collapse
Try to install
1- (Microsoft mtp drivers): https://www.microsoft.com/en-us/download/confirmation.aspx?id=48231
2- (g3 drivers): http://18d5a.wpc.azureedge.net/8018D5A/tool/dn/downloader.dev?fileKey=UW00120120425
and if it dosen't work, try this
1- https://www.youtube.com/watch?v=YafV2zlGA38#t=152
2- reinstall the g3 drivers

RapHaeL_4_4_4_ said:
Try to install
Click to expand...
Click to collapse
Should I keep trying to run it as Qualcomm HS-USB QDLoader 9008?

Akhlut_ said:
Should I keep trying to run it as Qualcomm HS-USB QDLoader 9008?
Click to expand...
Click to collapse
Yes, and after try again BoardDiag to see, because I'm sure that its a driver problem with windows 10

RapHaeL_4_4_4_ said:
Yes, and after try again BoardDiag to see, because I'm sure that its a driver problem with windows 10
Click to expand...
Click to collapse
I'm not getting any digital signature warnings tho.

Akhlut_ said:
I'm not getting any digital signature warnings tho.
Click to expand...
Click to collapse
Ohh, if you don't get any warning the second part of my post is useless..
If the first part don't work, I don't know why it dosen't work

RapHaeL_4_4_4_ said:
Ohh, if you don't get any warning the second part of my post is useless..
If the first part don't work, I don't know why it dosen't work
Click to expand...
Click to collapse
Still no good. :c

it seems like you have hardware brick sorry:crying:

[GUIDE][BR][LP]Complete guide for unlock bootloader and flash TWRP in H442F DUAL SIM

Hello folks!
It's been a while since last time I spent in this forum section (when the method for flashing Poland MM KDZ was published), but suddenly I decided to check the current development and it was great do discover that developers found a way to unlock bootloader! Then, I tried to do the procedures, found some adversities around the path, flashed stock KDZ for my device A LOT and finally managed to obtain a fully working LP stock with root and TWRP for my model: H442F (Dual SIM) ("LG Volt 4G" in Brazil).
The thing is: although a lot was done regarding the Spirit LTE, I found near zero information specifically for my device variant. Since I tried a lot of paths and eventually achieved an interesting result, I decided to write a full tutorial, with a lot of instructions and pictures for "novices" who desire learn all the steps but gives up at the high learning curve. Finally, I also wrote this tutorial in Brazilian Portuguese, which I believe will help at least some comrades (you can download the PDF in portuguese HERE).
Needed files:
LG Drivers (remove old ones if already instaled)
LG Flash Tool 2014 (credits to @quangnhut123 from this thread)
Brazilian H442F10a Firmware (this is a low speed server, I can upload to a better one if someone asks)
Android SDK Tools (for Windows users; Linux ones just install the package android-tools-adb)
Kingroot (or download here: www.kingroot.net)
Latin America Patched Aboot (credits to @pvineeth97 , for more info check this thread)
TWRP (or download here: https://twrp.me/lg/lgspiritlte.html)
Flashfy (or download here: https://play.google.com/store/apps/details?id=com.cgollner.flashify&hl=en)
SuperSU (or download here: http://www.supersu.com/)
Finally, if you prefer, you can download a full pack in this link (except for KDZ), however, I did prefer to keep isolated links for better credits and referrals
Step-by-step
Download all needed files
Install drivers, SDK and unpack Flash Tool
Save all files in the same folder, but keep KDZ file inside Flash Tool folder
Put your phone in download mode (power off, hold vol+, plug usb in pc, keep holding until download icon appears)
Wait a little for Windows completely detects device and load all drivers
Verify in Device Manager if your pc detects phone as "LG Mobile USB Serial Port (COM#)"
{
"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"
}
Open LG Flash Tool as admin
Select KDZ file
Choose the downloaded H442F10a_03.kdz file
Choose CSE Flash
Click START
Then, "Clear phone software update registry"
You'll see a warning
Then, OK (no need to change country)
Another app will open for the flashing. If you are offline, it is possible to show just a "?" character. Wait patiently...
In about 5min it will finish
After some reboots, you'll see the phone starter screen. Just move forward (no need to configure anything right now, maybe wifi, but not google account)
Enable Developer Options going to Settings/General/Common/Software Information and tap some simes in Build Number until the "You are a developer" message appears
Go back to Settings/Developer Options and turn on USB Debugging
With Debugging on, choose MTP (for Windows) or PTP (Linux), and when asked, allow the computer
Now, make sure you installed (and know how to use, since I will cover just a few commands here) the Android Debugging Bridge (adb). It will be essential for some steps, as well for entering Recovery Mode (I will show some Linux screenshots because I do not use Windows - for this tutorial, just for KDZ flash - but with a working adb the commands are the same)
Open a command prompt (Windows: right click in start menu) or a terminal (Linux) and run "adb devices" to see if the device was detected. If not, run again and check if phone are asking permissions (and grant it)
Go (cd) to the folder with all downloaded files and write the commands (some names may be different if you downloaded individual files from official links)
adb push aboot_5120_patched.bin /sdcard/
adb push twrp-3.2.1.0-cn70n.img /sdcard/
adb push SuperSU-v2.82-201705271722.zip /sdcard/
adb install Flashify_1.9.2.apk
adb install KingrootV5.3.1.apk
At whit point, make sure your internet is fully working (3-4G or WIfi), then, open Kingroot and root the device
After a well successful root, go back to adb and run "adb shell" and then "su". The phone will ask root permission. Grant it and in adb again run "cd /sdcard"
Now we arrived a critical step. Make sure to type the command as is show, because an error may result brick. We will copy the modified aboot into the respective phone partition (check code, check picture, and double check!)
If everything occurs all right, will appear this message
Great! Now you have an unlocked bootloader! What we have to do now is fhash a custom recovery (in this case, TWRP).
Open Flashify, give root rights, then go into Flash/Recovery Image/Choose a file/File explorer/sdcard/[downloaded file]. When asked to flash click "YUP!" and then "Flash More" (as we do not want the phone to reboot right now)
An extra step I prefer to do is remove Kingroot, since it installs a lot of services and keep device substantially slow. If you prefer Kingroot over SuperSU, you are DONE!
Case you prefer SuperSU... Open Kingroot/.../Settings/Uninstall Kingroot
It will prompt if you are sure. Just click Continue/OK
Go back to prompt/terminal and run "adb reboot recovery"
Phone will enter TWRP!
Now, just a few steps!
Go to Install and flash SuperSU
Go to Wipe and do a Factory Reset
Go to Settings and disable TWRP app installer (optional)
And finally go to Reboot and choose System
DONE!!!
Now you have a phone with an unlocked bootloader, a recovery capable of doing a lot of stuff (sideload, wipe cache, backups), and rooted as well.

A really good job, I'm sure a lot of your fellow countryman will find this very useful!

Korelev said:
A really good job, I'm sure a lot of your fellow countryman will find this very useful!
Click to expand...
Click to collapse
Thanks man! Today I finally added a link with portuguese-br instructions. Hope more Brazilian users will have the chance to perform these operations!

Valeeeu dms irmao, ajudou dmss

Ninloth said:
Thanks man! Today I finally added a link with portuguese-br instructions. Hope more Brazilian users will have the chance to perform these operations!
Click to expand...
Click to collapse
Thanks for the instructions. After unlocking its bootloader, wil it be compatible with any H440 custom rom (single sim operation, of course)? Or the only custom rom we get is Cm12?

Mrkblo said:
Thanks for the instructions. After unlocking its bootloader, wil it be compatible with any H440 custom rom (single sim operation, of course)? Or the only custom rom we get is Cm12?
Click to expand...
Click to collapse
Hi!
Well, unfortunately I don't know. I made the procedure, wrote the tutorial, and 2 months later changed my phone for a new one. Can't test anymore.

Mrkblo said:
Thanks for the instructions. After unlocking its bootloader, wil it be compatible with any H440 custom rom (single sim operation, of course)? Or the only custom rom we get is Cm12?
Click to expand...
Click to collapse
Yes, it should be compatible with any custom rom as long as your phone is Lg spirit LTE( snapdragon variant ).