[ROOT] HOWTO: AT&T H910 up to v20g (FULLY TESTED)

Search This thread
Nov 7, 2010
29
3
Thank you very much runningnak3d ! I finally did it with the help of your post, as well as Nerd magic's youtube video, after 15 or so hours of trying while snowed in, but kept missing steps and creating a mess. Had nothing else to do while snowed in, so what the heck.. Besides it's my secondary phone now and I use it to just play around with. Maybe time to try Lineage 17.1 now?!! :)
 

Fouzzi

New member
Dec 28, 2020
3
0
Hi everyone !
I recently bought a refurbished V20 H910 running on Nougat from Aliexpress.
This one keeps freezing everytime I put it in my pocket and go out, it Takes really longer to Come back to normal.
I flashed many other versions using LGUP: US996, H915, F800, but loosing signal everytime, thank god I dumped the files. I even rooted it using the dirtysanta method and flashed the H910 Oreo and the modem but still freezes, it doesn't accept any custom Rom.
Does anybody know if that is due to screen or motherboard! Or simply a software problem ?
Thank you
 

SpicySnack69

New member
Mar 8, 2021
4
0
Maybe I am just really stupid, but I am losing my mind over the Step1.bat. For context I have an h910 with the december 2016 software update so I highly I doubt that dirtysanta has been patched.

Here is what the terminal spits out after I run the first two instructions:

dirtysanta: 1 file pushed, 0 skipped. 14.9 MB/s (18760 bytes in 0.001s)
': remote couldn't create file: Permission deniedage/emulated/0
aboot.img: 1 file pushed, 0 skipped. 2129.9 MB/s (2097152 bytes in 0.001s)
': remote couldn't create file: Permission deniedge/emulated/0
dirtycow: 1 file pushed, 0 skipped. 94.1 MB/s (9984 bytes in 0.000s)
': remote couldn't create file: Permission deniedocal/tmp
my-run-as: 1 file pushed, 0 skipped. 120.3 MB/s (13796 bytes in 0.000s)
': remote couldn't create file: Permission deniedlocal/tmp
: No such file or directory
could not open /data/local/tmp/my-run-as
could not open /data/local/tmp/dirtycow
adb: unknown command shell


I tried running the bash as sudo and it litterally changed nothing, I did a bunch of other **** last time but then I gave up on this a few weeks ago only to pick it back up again now.

In all honestly I am just overwhelmed at this point, all I want a functional phone that isn't full of Gapps and bloatware, and honestly was not prepared for the ***** that the h910 is in this regard.

I get that it is a permissions/directory issue but don't know how to approach that as this is a stock h910 that other than having terminal emulator installed is completely untouched and obv unrooted.

Any help would be appreciated as I have dug for hours only to find nothing usefull online and also don't know who else to ask.

thx for your time
 

clsA

Senior Member
Aug 28, 2010
9,823
3,458
Central Florida
Maybe I am just really stupid, but I am losing my mind over the Step1.bat. For context I have an h910 with the december 2016 software update so I highly I doubt that dirtysanta has been patched.

Here is what the terminal spits out after I run the first two instructions:

dirtysanta: 1 file pushed, 0 skipped. 14.9 MB/s (18760 bytes in 0.001s)
': remote couldn't create file: Permission deniedage/emulated/0
aboot.img: 1 file pushed, 0 skipped. 2129.9 MB/s (2097152 bytes in 0.001s)
': remote couldn't create file: Permission deniedge/emulated/0
dirtycow: 1 file pushed, 0 skipped. 94.1 MB/s (9984 bytes in 0.000s)
': remote couldn't create file: Permission deniedocal/tmp
my-run-as: 1 file pushed, 0 skipped. 120.3 MB/s (13796 bytes in 0.000s)
': remote couldn't create file: Permission deniedlocal/tmp
: No such file or directory
could not open /data/local/tmp/my-run-as
could not open /data/local/tmp/dirtycow
adb: unknown command shell


I tried running the bash as sudo and it litterally changed nothing, I did a bunch of other **** last time but then I gave up on this a few weeks ago only to pick it back up again now.

In all honestly I am just overwhelmed at this point, all I want a functional phone that isn't full of Gapps and bloatware, and honestly was not prepared for the ***** that the h910 is in this regard.

I get that it is a permissions/directory issue but don't know how to approach that as this is a stock h910 that other than having terminal emulator installed is completely untouched and obv unrooted.

Any help would be appreciated as I have dug for hours only to find nothing usefull online and also don't know who else to ask.

thx for your time
Not sure on linux, but this tutorial is based on using Windows 10 (7 ? )
the error messages you posted look like you don't have permission to use the phone storage ( ge/emulated/0 ). Are you trying to run these commands in terminal on the phone ?

Its been a long time since I messed with the H910, but I can tell you it all works if you download all the correct files and do it on a windows 10 PC. All the missing downloads from this tutorial can be found in my AFH account.
 

SpicySnack69

New member
Mar 8, 2021
4
0
Not sure on linux, but this tutorial is based on using Windows 10 (7 ? )
the error messages you posted look like you don't have permission to use the phone storage ( ge/emulated/0 ). Are you trying to run these commands in terminal on the phone ?

Its been a long time since I messed with the H910, but I can tell you it all works if you download all the correct files and do it on a windows 10 PC. All the missing downloads from this tutorial can be found in my AFH account.
Using windows did fix the issue, I got all the way through to Step3. Thank you.

I am now stuck on a greenscreen, so yay I bricked it, worth it tho.
Time to dig through the internet to see if this is salvagable.

Generally if anyone knows of a way to enter recovery mode from here that would be great, otherwise thanks for reading lol.

Edit: Nvm It booted into the password question, the problem I have is that the volume down button seems to be broken and adb is being useless so I cannot boot into recovery/fastboot mode. I really don't want to have to fix the button first as I don't know if it will boot into the password question again without problem.

Edit2: After messing with a thin tip of a pen around the buttons I was able to press the volume button. I tried booting into recovery but the phone just doesn't do it and on each boot the password counter counts these boots down as if they were false password attempts, this is stressfull, I am down to 15 attempt out of 30 and don't wanna mess this up.

Edit3: I got into fastboot mode and it's not TWRP but the standard android fastboot, on a scale of 0-10 how ****ed am I? I tried redoing step 3 already to no effect and adb claimes to not recognize the device.
 
Last edited:

clsA

Senior Member
Aug 28, 2010
9,823
3,458
Central Florida
Using windows did fix the issue, I got all the way through to Step3. Thank you.

I am now stuck on a greenscreen, so yay I bricked it, worth it tho.
Time to dig through the internet to see if this is salvagable.

Generally if anyone knows of a way to enter recovery mode from here that would be great, otherwise thanks for reading lol.

Edit: Nvm It booted into the password question, the problem I have is that the volume down button seems to be broken and adb is being useless so I cannot boot into recovery/fastboot mode. I really don't want to have to fix the button first as I don't know if it will boot into the password question again without problem.

Edit2: After messing with a thin tip of a pen around the buttons I was able to press the volume button. I tried booting into recovery but the phone just doesn't do it and on each boot the password counter counts these boots down as if they were false password attempts, this is stressfull, I am down to 15 attempt out of 30 and don't wanna mess this up.

Edit3: I got into fastboot mode and it's not TWRP but the standard android fastboot, on a scale of 0-10 how ****ed am I? I tried redoing step 3 already to no effect and adb claimes to not recognize the device.
Did you flash the correct MK2000 kernel ?
Did you flash 10r or 20G or 20H ?
each requires the correct kernel.
To bypass the login password screen just pull the battery out

all the files you need to make the phone work are in my AFH folders here >
Oreo > https://www.androidfilehost.com/?w=files&flid=281251
Older 10r > https://www.androidfilehost.com/?w=files&flid=281250

Everything else (TWRP,Kernels) here > https://androidfilehost.com/?a=show&w=files&flid=235271
Tip: Don't flash anything that's not for your model (H910) If your not sure don't flash it !

As to Fastboot mode ... adb commands don't work in fastboot
it's just fastboot comands
fastboot devices
fastboot flash recovery twrp.img
fastboot reboot
..etc

Tip once you get the phone working get a root reboot app to boot directly to fastboot / recovery / ect
 
Last edited:

SpicySnack69

New member
Mar 8, 2021
4
0
Did you flash the correct MK2000 kernel ?
Did you flash 10r or 20G or 20H ?
each requires the correct kernel.
To bypass the login password screen just pull the battery out

all the files you need to make the phone work are in my AFH folders here >
Oreo > https://www.androidfilehost.com/?w=files&flid=281251
Older 10r > https://www.androidfilehost.com/?w=files&flid=281250

Everything else (TWRP,Kernels) here > https://androidfilehost.com/?a=show&w=files&flid=235271
Tip: Don't flash anything that's not for your model (H910) If your not sure don't flash it !

As to Fastboot mode ... adb commands don't work in fastboot
it's just fastboot comands
fastboot devices
fastboot flash recovery twrp.img
fastboot reboot
..etc

Tip once you get the phone working get a root reboot app to boot directly to fastboot / recovery / ect
Ok so in the mean time I did manage to get into TWRP, at some point it just offered me the factory reset, I manged to get into TWRP twice this way.

using the command fasboot reboot recovery just reboots the phone regularly.

On boot the phone does a Kernel panic, tho this is probably due to me flashing a ROM and has nothing do to with this thread anymore.

I assume I need to wipe the phone again and install a proper Kernel but can't boot into anything and it's really annoying. So I am back to square one at how I can get into TWRP without spending hours of my life rebooting the phone until it offers me a reset every blue moon? The fastboot command, tho a good tip, didn't work for some reason.
 
Last edited:

clsA

Senior Member
Aug 28, 2010
9,823
3,458
Central Florida
Ok so in the mean time I did manage to get into TWRP, at some point it just offered me the factory reset, I manged to get into TWRP twice this way.

using the command fasboot reboot recovery just reboots the phone regularly.

On boot the phone does a Kernel panic, tho this is probably due to me flashing a ROM and has nothing do to with this thread anymore.

I assume I need to wipe the phone again and install a proper Kernel but can't boot into anything and it's really annoying. So I am back to square one at how I can get into TWRP without spending hours of my life rebooting the phone until it offers me a reset every blue moon? The fastboot command, tho a good tip, didn't work for some reason.
If I recall correctly the command would be
fastboot reboot bootloader

fastboot will not boot you to recovery but back to fastboot (bootloader)
thats why it's necessary to do it from the phone with a root reboot app.

stick to the AT&T roms until you figure all this stuff out, Lineage comes with it's own set of issues on this device
 

SpicySnack69

New member
Mar 8, 2021
4
0
If I recall correctly the command would be
fastboot reboot bootloader

fastboot will not boot you to recovery but back to fastboot (bootloader)
thats why it's necessary to do it from the phone with a root reboot app.

stick to the AT&T roms until you figure all this stuff out, Lineage comes with it's own set of issues on this device
How do I flash the stock if I can't get into TWRP? ._.

The phone doesn't boot, it tries to and then Kernel panic.
 
Last edited:

Fouzzi

New member
Dec 28, 2020
3
0
Hi guys at&t has released the H91020i. Can anybody make a flashable stock rom Zip for the community pleaaaaase ? :)
Screenshot_2021-03-22-18-25-55.png
 

pakwarrior

Member
Nov 23, 2019
17
1
can somebody tell me is it ok to flash H910 FIRMWARE WHICH THAT GUY GIVEN THE LINK ON FIRST POST IN MY LG V20 H910 10I OR 10l ID KIF IT IS L OR I TELL ME ALSO IS IT OK OR IT WILL AGAIN HARD BRICK MY PHONE LIKE IS BRICKED H918 MOTHERBOARD PREVIOUSLY I KNOW ITS TTO LATE BUT I NEED ANSWER ASAP.......
 

clsA

Senior Member
Aug 28, 2010
9,823
3,458
Central Florida
can somebody tell me is it ok to flash H910 FIRMWARE WHICH THAT GUY GIVEN THE LINK ON FIRST POST IN MY LG V20 H910 10I OR 10l ID KIF IT IS L OR I TELL ME ALSO IS IT OK OR IT WILL AGAIN HARD BRICK MY PHONE LIKE IS BRICKED H918 MOTHERBOARD PREVIOUSLY I KNOW ITS TTO LATE BUT I NEED ANSWER ASAP.......
Well if you have TWRP on your device it means you didn't take an OTA update.
So 10I and 10L are both way before 20H .. anything after 20H is not rooted yet.

You will have to return your phone to the H915 software to root it and install TWRP
rooting the H910 is the first post
 
Last edited:

pakwarrior

Member
Nov 23, 2019
17
1
Well if you have TWRP on your device it means you didn't take an OTA update.
So I and L are both after H .. anything after H is not rooted yet.

You will have to return your phone to the H915 software to root it and install TWRP
link to rooting the H910 is in the first post
that is wut i am asking if i flash h915 20g firmware can it hard brick my phone again or it will be safe to flash in my no rooted and no twrp installed lg v20 h910 10I model
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    so can you give me kernel link also why we needed to flash kernel
    kernel fixes the static screen and many other things
    link > https://androidfilehost.com/?w=files&flid=283977
    only use ones marked H910

    Direct link to newest v2.2 > https://ava3.androidfilehost.com/dl...8081/6006931924117929492/H910_v2.2-mk2000.zip
    1
    hey where is lg v20 h910 20g rom link can you give me plz
    My roms are here > https://www.androidfilehost.com/?w=files&flid=281251
    1
    hey I did everything from installed but there is an issue of password id what is it is not going anyway weather I do plz tell me how to fix it also I factory reset 100 times but that not going after it I try to fail 30 times then it says it going to be wiped i did that but there was a problem occurs decryption unsuccessful plz tell me what to do now tell me the password or fix
    keep referring to page one for questions
    if you get static screen > turn screen off and back on
    If you get password screen > pull battery
    after you have Oreo TWRP
    format data
    if you flash any rom reflash Oreo TWRP

    use the TWRP here > https://www.androidfilehost.com/?fid=1395089523397955602
  • 83
    ***WARNING***
    This is ONLY for the H910. If you flash H915 firmware on an H918 -- you WILL brick it.​

    If you are currently on Oreo, you can root your phone, but you CAN NOT keep Oreo - for now. This will downgrade you back to Nougat, which is rootable.

    I know this is a long post, but this is also a complicated root procedure. Please read the ENTIRE post before starting.
    Also, if you run into a problem, please use the search thread box to see if your problem has already been addressed. It will save having to ask the same questions over and over.

    If you want to restore to stock v10q after rooting, you can use this: link.

    Standard disclaimer: There are no guarantees in life. No part of this should brick your phone, but if it does somehow, that is on you.

    This should work on any H910 version, up to v20g, that is no longer rootable by DirtySanta (IE: dirtycow has been patched). It has been tested on 10m to 20g

    • Make sure that you have an SD card that has at least 8 gigs of free space. It CAN NOT be formatted FAT, or FAT32. It needs to be exFat or ext4, otherwise the zip won't fit (2 gig file limit on FAT and FAT32).
    • Make sure you have a working adb environment. I use Linux so hopefully this is a good resource. If not, you will have to Google this yourself: link.
    • Make sure that you have a working WiFi connection. Part of this process involves installing a terminal emulator. Since the phone will have no signal at that time, you use WiFi, or you can side load.
    • Download the H915 v10e KDZ: H91510e_00_VTR_CA_OP_1205.kdz.
      - WARNING: Do not use any newer H915 firmware, as they all have dirtycow patched (v10p, v10q), and I do not know if they increment ARB.
      - If they do increment ARB, then you will be stuck with a phone that can't be rooted, and you can't fix the modem! You have been warned.
    • Download the patched LG UP from this thread: link.
    • Make sure you install it in C:\Program Files (x86)\LG Electronics\LGUP or it will either read the wrong model file (if you had a previous installation of LG UP), or it will not be able to find the model file at all.
    • Put your phone into download mode (power off / hold vol. up / plug in USB cable)
    • Use LG UP to dump your phone. When you run it, there will be additional radio buttons.
      - Pick the one that says DUMP and click Start. You will be asked what partitions to dump, click the "select all" checkbox, and then you can uncheck userdata.
      - This is an OPTIONAL but HIGHLY recommended step. It is a good idea to have a full backup of your phone, but with this new procedure, this is no longer needed.
    • When it is finished, click the PARTITION DL radio button, pick the H915 v10e KDZ that you downloaded above, and click start. Make sure all partitions are checked.
    • Once it is complete, your phone should reboot into a nice new (old) Freedom Mobile ROM (complete the setup), and you may not have signal.
      - If you are on AT&T I understand that you will, but T-Mobile does not. Either way, this is normal.
    • Before continuing, make sure that you enable developer mode, and enable USB debugging. Also, make sure that your PC is authorized (plug the phone in and touch always allow, and then OK).
    • Also go ahead and download a terminal emulator -- NOT Termux. I recommend good old "Terminal Emulator for Andorid" -- the first thing that pops up if you search for "terminal"
    • Download this modified (by modified, I mean it contains all the extras needed to make this work) DirtySanta root package: link.
      - Extract this somewhere that you can run adb and fastboot from.
      - Check the SHA hash: 88a3a0f90c66a486807da3e69e9fb0a08c779efe
    • Download the v10r firmware + boot + system here: link (sorry - no time to dump and package 10v)
      - Check the SHA hash: 5451146030393e490dcfba3558b620badefe75cd
      - This includes v1.0 of the mk2000 kernel
    • Copy the zip, to your SD card, and insert it in the phone.
      - Alternatively, you can use adb to push the zip to your phone while in TWRP. This is NOT supported.
      - I switched to having people flash from SD card because too many people were having problems with adb.
      - If you want, try it, if it doesn't work, don't ask for help -- use the SD card method!
    Open two command windows. In each one change to the directory that you extracted the root package.

    In the first one execute:
    Code:
    adb logcat -s dirtysanta

    Then in the second one execute:
    Code:
    STEP1.BAT

    Wait till you get a prompt back then type (or copy / paste):
    Code:
    run-as con
    chmod 0777 /storage/emulated/0/*

    Now open up your terminal emulator on your phone and type:
    Code:
    applypatch /system/bin/atd /storage/emulated/0/dirtysanta

    Watch the window that has logcat running. When it says to run step 2, execute:
    Code:
    STEP2.BAT

    Once fastboot comes up -- it will be a really small red font that says, FASTBOOT MODE. Once that is up, execute:
    Code:
    STEP3.BAT
    This is flashing TWRP and the WW 2.0 kernel onto your phone. The phone will reboot once they are flashed.
    When it reboots, you will get a very nasty looking warning about the fact that your phone has been compromised and will not boot.
    This is due to running the engineering aboot and is normal -- don't panic your phone will boot. You will see this every time the phone reboots.

    At this point, you have H915v10e and TWRP. You can now boot into TWRP so that we can flash the H910 firmware back onto the phone:
    If you have re-enabled developer mode, and enabled USB debugging, and have your phone connected, you can execute the following in a command window:
    Code:
    adb reboot recovery

    Otherwise just pull the battery, put the battery back in, hold vol down + power till the LG logo appears. Release power, and then immediately press and hold it again until you get to a screen that asks if you want to factory reset your phone. Say yes twice and it will take you into TWRP. If the phone had the stock recovery, it would do a factory reset -- however, since you now have TWRP, that is what you are taken to instead. This is a key combination that is embedded into the bootloader that tells it to execute recovery - in this case TWRP. Hope that clears up some confusion as to why you get a screen asking you to factory reset your phone...

    Now that you are in TWRP you need to do a couple of things:

    • Format data. Wipe -> Format data. It will ask you to type "yes". If you don't do this, you will be prompted to enter a passcode, and will have 30 tries. If that happens, just boot back to TWRP and do this step again.
    • Wipe cache / dalvik cache
    • Flash the zip. Choose "Install" and browse to your SD card, and select the h910-10r.zip file. When complete hit the home button.
    • Now, format data again for good measure....

    Once the second format completes you can reboot your phone, and it will be just like you got it fresh off the factory floor, except it will have TWRP.
    No part of the H915 firmware is left on the phone. The only things that are not 100% stock v10r firmware are ABOOT (it is the US996 engineering aboot that is unlocked. It also gives the nasty warning on boot), BOOT (it is the 10q kernel with a few patches added by @askermk2000 - KCAL, Adreno idler, etc), and of course RECOVERY (TWRP).

    It takes a little while for the first boot -- be patient. It should NOT take longer than 10 minutes. If it does, something went wrong. Boot back to TWRP and try flashing the 10r zip again.

    Now that you have a phone with TWRP, feel free to download whatever root method you would like (SuperSU or Magisk).



    Old, unsupported ROMs will NOT work with the 10p, 10q or 10r firmware.
    If you want to run NATF or WETA (or any old, unsupported ROM that you find floating around these forums) you will need to flash the older 10m firmware: here.
    SHA: 1007dedb6e935b0bea1e25f28e39ccb8e69f9694
    This is JUST the firmware! It has no kernel, or system. You MUST flash a 10m or earlier ROM or your phone will not boot. If you forget, you can always boot back to TWRP and try again.
    The newer kernel should work, but I have not tested it with the older firmware. If it doesn't grab the WW2.0 kernel, it works fine with 10m.


    For the latest kernel, please visit @askermk2000's thread: here

    Do NOT flash firmware for the H918 -- it will brick your phone. Firmware for the other models won't work, but they won't brick your phone.

    Feel free to ask away if any of this doesn't make sense. I really hope that isn't the case now :)

    Most of all -- have fun. That is what this is supposed to be about!


    Again, If you want to restore to stock v10q, you can use this: link.

    Serious credits go out to:
    @me2151 for DirtySanta. Please visit his original thread and hit the thanks button.
    @smitel for Reversing LG UP and figuring out how unlock lab mode. No partition dl, no root on the new firmware. Again, hit the thanks button.
    @Prowler_gr for patching LG UP for the V20 not to mention finding that thread. I never go into the G5 forums, so I would have never seen it. AGAIN -- hit that thanks button.
    @USA-RedDragon for his Werewolf kernel. I know I sure like not having static on boot. Most people get the ability to hit thanks 6 or 7 times a day -- be sure to use up one more.
    @askermk2000 For the new 10q kernel. Dude doesn't even have a V20 and jumped in to help out.

    Seriously, these guys are the real devs, and the ones that have left the V20 scene are missed...

    -- Brian
    8
    FAQ:

    Q1: If I revert to stock will AT&T know that I rooted my phone?
    A1: Nope. Unlike Samsung phones (at least older ones, I don't know about current ones), there is no KNOX style indicator that shows how many times a phone has been flashed.

    Q2: Do we have to flash ALL of the H915 firmware, that seems like a waste?
    A2: You would be correct -- it is a waste, but I am going to need more time to test and make sure that only the XBL and ABOOT need to be flashed AND that doesn't break trusted boot. As I have stated, the H910 and H915 have the same PBL. I ran my phone with the H915 XBL, with the rest of the firmware being H910 and I don't have a brick -- but I did it manually and not though LG UP. When I feel like wiping my phone again, I will test this.

    Q3: Can any other variants be rooted with this method?
    A3: Maybe. I was able to get the patched LG UP to recognize a KDZ that I modified, and it let me flash. My next step is to completely roll my own KDZ. If that works, then ANY LG phone will be rootable simply by flashing a KDZ.
    A3: YES! It turns out that the LS997 is able to use the VS995 KDZ. I have written up a post on the procedure.

    Q4: If that works, and you can roll your own KDZ, can you get around ARB?
    A4: I believe so. Now that we have the ability to take a dump of an unmodified / stock / out of the box phone, we could dump the XBL (this is what updates ARB), and package that up with an older ABOOT. I am mainly talking about H918s here, since all other V20s work with the engineering ABOOT. But it will also apply if AT&T ever increments ARB on the H910.
    Nope, there is no getting around ARB. Once a particular ARB version is blown into your QFPROM, you *MUST* use a boot stack that has that ARB version, and that is basically the entire firmware except for boot, recovery, laf and system.

    Q5: Will the AM&FM Radio still work
    A5: Yes.

    Q6: Why are my boot times longer after rooting?
    A6: In order to unlock the bootloader, an engineering aboot had to be used, and a lot of additional data is generated on boot.

    Q7: Can I return my phone to stock?
    A7: This was addressed in the post above, but I will address it again. Yes. For the link, see the post above.
    5
    @runningnak3d could you update the link from DirtySanta root package?

    all the root files for this thread are in my AFH (in my signature) the root package is here >> https://androidfilehost.com/?fid=1322778262903990218
    4
    Jerry SQ to the rescure, follow these steps to fix signal and data (h910 only):
    1 Dowload US99610f.kdz and F800K10e.kdz firmware, LGUP with patch in the first post
    2 KDZ F800K10e.kdz, partition dl, tick select all, wait for it to boot into rom, install TWRP with dirtysanta steps, boot into TWRP, then select reboot, select bootloader (or using adb, your choice, but the bootloader need to be unlocked)
    3 type these codes in booloader
    fastboot erase modemst1
    fastboot erase modemst2
    4 wait till it done, don't rebooted the phone yet, instead, pull the batterry out, get back to TWRP by hardware button
    5 format your rom, reboot back to TWRP, wipe Cache, System, internall storage, then poweroff the phone
    6 get in dowload mode, KDZ US996 firmware, partition dl, tick select all, boot into rom, if it stuck somewhere, factory reset might do the trick
    7 when it boot up, it will get bootloop after you get in the setup screen (i don't know it'll happen to you, but for me it'll bootloop)
    8 pull battery out, get in dowload mode, KDZ F800K firmware, partition dl, TICK MANUALLY EVERY THING EXEPT BOOT, MODEM, ABOOT, ABOOTBAK
    9 when it done, you will have signal, data mobile again, if you like, you can use F800K firmware or you can follow dirtysanta steps and install any rom you like
    4
    Kernel with some features

    Ok :)

    This one is a bit more experimental. I've looked at some patches from Werewolf and D.O.T.S Kernel, and picked a few compatible ones that looked rather straight forward without risk of complications.

    So we have:
    KCAL - the one that started it all.
    Adreno Idler - Battery savings.
    Disable software CRC checking of SD Card - More performance.
    Remove temperature polling - Battery savings.
    Reduce DSI status check - Battery savings.
    Fixed USB erratic behavior with some chargers.
    Static Screen fixed.
    RCTD removed.

    ^^Let's hope it works :) Would welcome feedback.
    If it works nicely I'll make one for H918 as well.

    --removed-- Look here!
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone