Over the years I've always been good at solving these things, but this is the first time I've every had to request help/guidance.
LG
1. Came from from 4.4.2, ioroot rooted, installed twrp via freegee, but not the kernel patch. This prevented me from booting back into Android.
2. Factory reset everything, wiped everything from twrp.
3. Ran adb commands here:http://forum.xda-developers.com/showthread.php?t=2451696 Got me into fastboot.
4. Flashed all .img files for LG D800 from prime's D800 img stash. Fastboot rebooted.
5. Installed Mahndi ROM via adb. Reboot
6. Stuck. Phone hangs on LG logo, loading modem and com drivers in windows. Recovery is now stock, so no flashing. Download mode works but always get a "Device Model is different" error at 0% when flashing from LG Flash Tools. Correct .tot and correct .dll for D800.
Any help or ideas to get my G2 up and running again would be amazing. I'm still trying to figure out if I can modify the .tot to match my device's current model or just ignore it and overwrite (best hope). Even if i can get ubuntu to detect the phone that would lit my spirits.
Thanks.
Progress
So I have actually figured out the problem completely, yet I do not yet have a solution.
-I after flashing the correct .img over to my device, I was all set to go, but read somewhere about flashing over mahdi ROM.
-I successfully flashed Mahdi, but DID NOT FLASH THE DEVICE VERSION PATCH (literally hit my head on the desk when I realized).
-I panicked after it did not work and reflashed all the .img so I was stuck with stock recovery, no adb, no sideload, no fastboot.
Is there ANY WAY to flash back to stock with the LG Flash Tool for the ATT D800 that ignores the model number inconsistency. This type of phone only supports the .TOT method of flashing. There is no other way (KDZ = NO). Currently my device's build.prop says that the model is "g2" (this is what the patch was supposed to fix) and my flashing file/.dll is for "D800".
My device can not be seen in Ubuntu.
Any suggestions?
datdude_tc said:
So I have actually figured out the problem completely, yet I do not yet have a solution.
-I after flashing the correct .img over to my device, I was all set to go, but read somewhere about flashing over mahdi ROM.
-I successfully flashed Mahdi, but DID NOT FLASH THE DEVICE VERSION PATCH (literally hit my head on the desk when I realized).
-I panicked after it did not work and reflashed all the .img so I was stuck with stock recovery, no adb, no sideload, no fastboot.
Is there ANY WAY to flash back to stock with the LG Flash Tool for the ATT D800 that ignores the model number inconsistency. This type of phone only supports the .TOT method of flashing. There is no other way (KDZ = NO). Currently my device's build.prop says that the model is "g2" (this is what the patch was supposed to fix) and my flashing file/.dll is for "D800".
My device can not be seen in Ubuntu.
Any suggestions?
Click to expand...
Click to collapse
over here http://androtransfer.com/AndroidUser00110001/ROM/G2/KK/D80220a/ there is a dll named lgup_8974.dll which is for d800 and is supposed to skip the model check
datdude_tc said:
Over the years I've always been good at solving these things, but this is the first time I've every had to request help/guidance.
LG
1. Came from from 4.4.2, ioroot rooted, installed twrp via freegee, but not the kernel patch. This prevented me from booting back into Android.
2. Factory reset everything, wiped everything from twrp.
3. Ran adb commands here:http://forum.xda-developers.com/showthread.php?t=2451696 Got me into fastboot.
4. Flashed all .img files for LG D800 from prime's D800 img stash. Fastboot rebooted.
5. Installed Mahndi ROM via adb. Reboot
6. Stuck. Phone hangs on LG logo, loading modem and com drivers in windows. Recovery is now stock, so no flashing. Download mode works but always get a "Device Model is different" error at 0% when flashing from LG Flash Tools. Correct .tot and correct .dll for D800.
Any help or ideas to get my G2 up and running again would be amazing. I'm still trying to figure out if I can modify the .tot to match my device's current model or just ignore it and overwrite (best hope). Even if i can get ubuntu to detect the phone that would lit my spirits.
Thanks.
Click to expand...
Click to collapse
I have almost the exact same problem will keep an eye on thread, hope we git it sorted soon!
I'll Take a look
XxZombiePikachu said:
over here http://androtransfer.com/AndroidUser00110001/ROM/G2/KK/D80220a/ there is a dll named lgup_8974.dll which is for d800 and is supposed to skip the model check
Click to expand...
Click to collapse
Thanks!
I have seen and downloaded that one before, and if I recall correctly, I didn't get a model error, but rather something else. I believe it was a bin file error??, but I do not recall. I actually just sent my G2 in on a warranty claim (*please oh please don't notice I replaced the screen") and hopefully that will take care of it. I was just posting so that maybe someone doesn't have to dig through 350 pages of replies to find out what happened. I'll keep the post going when I find anything out though.
Working together!
MRobbo80 said:
I have almost the exact same problem will keep an eye on thread, hope we git it sorted soon!
Click to expand...
Click to collapse
I won't have my phone available for a few days. Any chance you could go ahead and give that lgup_8974.dll a test run and report back? I'd be more than willing to help do any research if it gives a different error besides the model.
Sorry to dig up this thread, but I have the exact same problem, except I flashed mahdi on my D802 and somehow the version patch didnt flash correctly. Is there anything like a lgup_8974.dll for D802s?
I'm really desperate here.
i have the exact same problem!!
Any solution found yet??
jeanclaudevandamme said:
Right, I've figured out where things have went wrong but still can't find a fix
1) So after Step 14 after running the BAT files all cmd windows closed. I then clicked step3.bat while in fastboot mode. because he did not explain clearly where you were supposed to get CMD window for commands in Step 16.
I had used CMD / ADB / Fastboot years ago, but I had forgotten how they worked exactly, as the instructions for the previous phones I have rooted were so much better written.
later i discovered how to see what was inside a BAT file (use notepad to open it) so step3.BAT contained instructions to flash "boot1.img" which came with the Dirty Santa v20 files. I don't know what model that boot image was taken from. it also contained instructions to flash a twrp file name that didn't exist (so I guess nothing would have gotten flashed).
2) later I was able to launch into fastboot mode and manually flash the correct twrp file onto the phone. then led me being able to get into twrp recovery to flash kernel + SU.
However phone still didn't boot, presumably of the mistake was previously by clicking Step3.BAT, which flashed a "boot1.img" from dirty santa files
Also when going into download mode, the phone would crash with static 1 second after connection.
3) At the time, I didn't know the difference between aboot and boot files. So I went into fastboot and flashed abootbackup.img
I still don't know fully what aboot does. But the effect it has is it locked the bootloader, so i am no longer able to flash anything with fastboot. writing the old aboot.img has caused my device to go into a corrupt bootloop, cannot launch into recovery.
I think that if I flashed bootbackup.img then things might have worked out ok. i had 2 choices and I picked the wrong one, but that's gone now.
flashing the abootbackup.img also had another effect, download mode no longer crashed with static after 1 second, however a new error code came up when download mode is launched <633A B50>, the phone acts like a firmware is currently trying to be flashed but stuck at 0% even just by launching download mode.
I'm guessing there may be some sort of variant mismatch between the boot1.img and the abootbackup.img as the boot1.img wouldn't have originally come from my phone? As well as the other stuff pushed onto device in Step2.BAT
eithe way, LG Bridge / LGUP do not recognise model even with Uppercut.. LG Flash 2014 has the error messge of "connection to server failed", I tried letting it run in the background without closing error message as suggested in that thread, but I guess because of my 633A B50 error message, flashing did not occur in the background like other people.
----------------
I don't know where to go from here exactly. because
1) boot1.img, that came with dirtysanta files, which model / variant did it come from?
2) what LGUP_common.dll will recognise my device now? I know someone patched their DLL, but how do you patch a DLL using hex editor and how to make the DLL recognise my presumably mismatched device?
3) i don't know what the <633A B50> error message means exactly
------
https://forum.xda-developers.com/v20/help/help-h990ds-t3650303
looks like someone did something similar to what I did. he didn't get answers to his questions and he hasn't been logged in since August..
Click to expand...
Click to collapse
It's more bricked than usual..
Have a go at this?
I like using the LGUP Patched DLL for H91810J. It seems to recognize all variants.
as a last resort use LG Bridge, refurbish. it will repair all sorts of half installs and messed up partitions. the only thing is : IT WILL BRING YOUR BUILD UP TO 10q=================WHICH IS NOT ROOTABLE!!======================
Just in case this issue has not been resolved. I did the same thing 10 minutes ago. I flashed the wrong abootbackup.img (10c) instead of 10d.
All you have to do is open LGUP and if the device won't be recognise, just run the Uppercut tool and the device will show up. Flash your .kdz file and the phone should be running once again.
WARNING
DO NOT LET YOUR PHONE REBOOT, OR POWER OFF UNTIL I TELL YOU THAT IS WHAT YOU NEED TO DO.
If you do, I am not sure what shape your phone will be in.
This should go without saying, but you MUST have your bootloader unlocked (check OEM UNLOCK in developer options AND fastboot oem unlock). If you don't, you will probably brick your phone.
If you use this on any model G6 besides the H872, you will be stuck in a bootloop, and you will not be able to fix it since you will have wiped out download mode!
This is safe if no mistakes are made (typos, missing a step, etc). However, if you do mess up, the risk is high that you lose download mode at best, or brick your phone at worst.
If you deviate from this procedure, and think: "I can just skip a step, or I can do this on my own Linux install". Don't complain if you brick your phone.
PREREQUISITES:
You must have a version of laf that has the COPY opcode.
Since none of the firmware available for the H872 has the COPY opcode, we have to use the H918 laf partition.
Grab the H918 10p KDZ: link to 10p KDZ
You need to be on 11g or above. Be aware, once you are on 11g+ you cannot downgrade to any versions prior to 11g due to anti-rollback.
You will need a copy of the KDZ that your phone is on. If you are not currently on 11g, upgrade before continuing.
For 11g : Link to 11g KDZ
For 11h : Link to 11h KDZ
For 20a : Link to 20a KDZ
We are going to flash this using the patched LG UP. There may be one that was patched specifically for the G6 -- don't use it,
it has NOT been tested. Grab the one for the V20: link
It MUST be installed in: Crogram Files (x86)LG ElectronicsLGUP
You can't just unzip it anywhere and run it, it will not find the model file.
You need the H872 Unofficial 3.2.3 TWRP by @Eliminator74. 3.2.3 is included in the repo so that you know that you have the exact version.
If you decide to use any other version, you will brick your phone because the commands below are for this exact version!
You need to grab FWUL (version 2.7 or later) and burn it to a USB stick: link
Even if you have Linux, and you think you can install the dependencies, don't. I know this works from FWUL.
If you are rooting on 20a, you will need a Micro-SD card. Copy the TWRP 3.2.3 image and the latest Magisk zip to the SD card.
WARNING: Only applies if rooting while on 20a
Minor Encryption-related issues have occurred while testing 20a. If your data partition is encrypted, TWRP will NOT be able to decrypt it. Because of this, you will have to perform a wipe and format of your Data partition. Be sure to backup all data on your device prior to continuing by copying important files to an external SD card or using LG Mobile Switch to back it up.
PROCEDURE PART 1: Getting a working LAF onto your phone
By far this is the most dangerous part of this procedure.
Boot to download mode
In LG UP, choose partition DL.
Pick the H918 10p KDZ
Click start / ok
When you will be given a list of partitions to flash, only check laf
Click start / ok
You will get a warning about additional modified partitions -- ignore it, and click OK.
As a safety feature, LG UP will start flashing those modified partitions after laf completes flashing.
After the flash is initiated, pay close attention to the "step" and as soon as it changes from laf to another partition, PULL THE USB CABLE!
If you let it completely flash the H918 KDZ, your phone WILL reboot, and you WILL have a brick that can't be fixed.
You need to pay attention, but you also don't need to be sitting on pins and needles. You have quite a bit of time to pull the cable since system is one of the partitions that is flashed
Click OK and it will start flashing.
Once laf is flashed, and you have pulled the USB cable, you can click exit, and then re-open LG UP.
Choose partition DL again, and this time pick the H872 KDZ for the version your phone was on prior to flashing 10p (11g, 11h, or 20a)
Select all partitions except laf. If you forget to uncheck laf, you will have to do this all over again.
When it completes, it will reboot your phone.
Go back into download mode. This time you will be running the H918 laf, and we can continue with PART 2
PROCEDURE PART 2: Installing TWRP
Boot from your FWUL USB stick.
Put your phone into download mode. With the phone powered off, hold vol up and plug in the USB cable. You do not need to touch the power button -- the phone will power on and enter download mode.
This will NOT look like normal download mode on the phone. All you will get is small box that says: "Download mode" -- this is normal. You will also not have ANY indication on the PHONE that it is being flashed.
Once booted, login. The password is: linux
Double click the LG folder that is on the desktop
Double click on LG LAF (runningnak3d) icon and you will be at a terminal prompt.
The following are the commands that you enter into that terminal. You can copy / paste them if you like.
Code:
git pull
git checkout h872-miscwrte
./step1.sh
When you are told to, pull the USB cable, and the phone will power off. You now have TWRP on your laf partition. At this point you can flash a ROM, or Magisk or whatever you like, but I would suggest
at least flashing TWRP to the recovery partition. There is no button combination to get into laf (download mode), so if you only have TWRP on laf, then you will need a USB cable to get into recovery.
OPTIONAL:
If you don't know what to do with TWRP, and you just want to run rooted stock 11g, 11h or 20a, this is for you....
First boot into TWRP - with the phone off, hold vol up and plug in the USB cable.
PROCEDURE PART 3: Rooting and cleanup
Now that you are in TWRP:
Nougat (11g, 11h Users)
./step2.sh
If you ran step2.sh you have TWRP on laf, and recovery, and you are rooted. If you only ran step1.sh, then you have TWRP on laf. Either way, enjoy!
Oreo (20a) Users
Once in TWRP, click the “Wipe” button.
Choose Advanced Wipe and select the Dalvik, Data and Cache options and Wipe. Do not reboot the phone.
Go back to the main menu or main wipe screen
Select “Format Data” and complete the format.
Go back to the main menu and choose Install, and then Install Image.
Flash the TWRP 3.2.3 image from external_sd to the RECOVERY partition. DO NOT Reboot to System.
Go back to the main screen and attempt to reboot to Recovery.
If you are able to reboot to recovery without any issues, you should now Install the Magisk zip from external_sd.
After flashing Magisk, you may now reboot to system and Oreo should boot to the initial Android Setup screen.
After booting to Oreo, make sure you enable installations from Unknown Sources in your Android Settings and install the latest Magisk Manager.
If Oreo boots to an "Encryption Unsuccessful" screen, you will need to format the Data partition again. Tap the reset button and it should boot to Recovery. Perform another wipe of cache/data/dalvik and go back to the Wipe screen and Format Data. Reboot system and you should boot to Oreo Normally.
To Restore Download Mode
20a - Flash @Eliminator74's Bootstock with LAF image using TWRP
11g - Flash @weakNPCdotCom's StockLAF image using TWRP
CREDITS:
@KAsp3rd -- he risked his phone to make this happen. There were no guarantees that the H918 laf would boot and function.
Lekensteyn -- His base work on the G2 / G3 gave me a GREAT headstart!
@steadfasterX - He added some real nice features, great guy to bounce ideas off, and just testing crazy ideas because he wasn't afraid to brick his phone Also, for FWUL
tuxuser - Helping with my lacking in Python
@smitel - His original reverse engineering of LG UP. Great inspiration!
@weakNPCdotCom - Testing/Help with H87220a (Oreo)
-- Brian
XDA:DevDB Information
lafsploit - H872, Tool/Utility for the T-Mobile LG G6
Contributors
runningnak3d, KAsp3rd, weakNPCdotCom
Source Code: http://gitlab.com/runningnak3d/lglaf
Version Information
Status: Testing
Created 2018-04-09
Last Updated 2018-10-09
You ARE the man!
Good job, I'm certainly tempted to try, but have never done such kind of procedure to get root and I started flashing and rooting some time ago but everything was easier back then, I'll probably wait a bit, what's a week or two when I got the phone May last year.
Enjoy your time off. You really deserve it.
From a SM-960U that thinks is a SM-960U1...
Sent from my SM-G960U1 using Tapatalk
brick to me i didn't pull out the cable during laf partition...im on qualcomm 9008 no way to come out
Just curious, did you somehow overlook that step, or were you not looking and missed it?
-- Brian
runningnak3d said:
Just curious, did you somehow overlook that step, or were you not looking and missed it?
-- Brian
Click to expand...
Click to collapse
I feel like he just wants a way or a tool to unbrick Qualcomm 9008 models. Looking at his name and post on other thread. I might be wrong tho.
Amazing job btw. Much respect for you sir !!
pantmunu said:
I feel like he just wants a way or a tool to unbrick Qualcomm 9008 models. Looking at his name and post on other thread. I might be wrong tho.
Amazing job btw. Much respect for you sir !!
Click to expand...
Click to collapse
it my fall, when i start to do laf partion i didn't see when come out laf partition, so i let the program do his job after i see that it come to system write and i understand that it was there that i will pull the cable out, btw i will wait some good person will found solution for the qualcomm 9008 problem..they made a lot of good job..and of course is my mistake...if someone know how to come out from this problem i will be grated for all life..for the moment i will wait..or i found someone can unlock for a good price i will pay him and do the job...
The only fix for 9008 mode on UFS devices (which the G6 is) is a firehose programmer and QFIL. It is no longer possible to boot from an SD card. AFAIK, there is no signed (yes it MUST be signed) firehose for the H872.
Your only options are T-Mobile or LG warranty, or pay to have it repaired if it isn't under warranty. You could also swap the board with an H872 that has a cracked screen, but getting the thing apart looks like a real PITA.
-- Brian
runningnak3d said:
The only fix for 9008 mode on UFS devices (which the G6 is) is a firehose programmer and QFIL. It is no longer possible to boot from an SD card. AFAIK, there is no signed (yes it MUST be signed) firehose for the H872.
Your only options are T-Mobile or LG warranty, or pay to have it repaired if it isn't under warranty. You could also swap the board with an H872 that has a cracked screen, but getting the thing apart looks like a real PITA.
-- Brian
Click to expand...
Click to collapse
did you think in the future will come out a firehose file the lg g6? very thanks for your unswer and help, and very good job, i admire this talent people
Done!!! Where's your PayPal brother? I need to give you my pledge, thanks so much for opening the doors for this device's development. Can't thank you enough really...
Glad you came through it without issue.
Just click on the Donate to Me button -- tis linked to my PayPal.
Thanks,
-- Brian
Guys i found this on the web... maybe for the profesional user this can be a way to unbrick lg g6 with hard brick like mine https://www.androidbrick.com/download/download-latest-2018-qualcomm-flasher-qfil-qpst-2-7-472/
i try to use it and i didn't understand nothing..but my mobile it see as download mode
Thanks for putting this together, runningnak3d!
So, reading through the tutorial, you say this towards the end, after doing the cleanup steps:
Now you have TWRP on laf, and recovery, and you are rooted.
Click to expand...
Click to collapse
So... does that mean attempting to boot into LAF will always put you into TWRP? If yes... is there any way to get the original LAF partition back, while keeping TWRP in recovery?
Denversmartphone said:
Guys i found this on the web... maybe for the profesional user this can be a way to unbrick lg g6 with hard brick like mine https://www.androidbrick.com/download/download-latest-2018-qualcomm-flasher-qfil-qpst-2-7-472/
i try to use it and i didn't understand nothing..but my mobile it see as download mode
Click to expand...
Click to collapse
It's for Huawei.
Sent from my SM-G960U1 using Tapatalk
hendusoone said:
Thanks for putting this together, runningnak3d!
So, reading through the tutorial, you say this towards the end, after doing the cleanup steps:
So... does that mean attempting to boot into LAF will always put you into TWRP? If yes... is there any way to get the original LAF partition back, while keeping TWRP in recovery?
Click to expand...
Click to collapse
Yes, you can extract it from the 11g KDZ and flash it, but why? There will never be a situation where you would want laf over TWRP.
-- Brian
runningnak3d said:
Yes, you can extract it from the 11g KDZ and flash it, but why? There will never be a situation where you would want laf over TWRP.
-- Brian
Click to expand...
Click to collapse
My main reason is to maintain multiple methods of recovery. With a working LAF, you can flash a KDZ to get back to a working phone (even though it would need to be re-rooted). With TWRP in the LAF partition, if for some reason both instances of TWRP failed, that is no longer possible.
If something stopped TWRP from booting on laf, then laf wouldn't boot on laf either. They are both just kernel / initrd boot images.
Do what you want, but trust me, you are a lot safer with two copies of TWRP.
-- Brian
runningnak3d said:
If something stopped TWRP from booting on laf, then laf wouldn't boot on laf either. They are both just kernel / initrd boot images.
Do what you want, but trust me, you are a lot safer with two copies of TWRP.
-- Brian
Click to expand...
Click to collapse
Generally, I'd agree. Having redundant TWRP recoveries is probably better.
But it is nice that we can restore LAF on the off chance we want to restore the phone to default via KDZ. Perhaps to sell it or such.
---
Anyway, thanks for all the great work! I'll probably give it a whirl in a few days. Hopefully, this will spur some ROM development for the H872.
I made it all the way through to mounting system with read/write, twrp console just complains that it failed to mount /system with "device or resource busy". I haven't attempted to boot into recovery again since booting into system but twrp is definitely on laf still. I did try booting from laf twrp to recovery twrp before booting to system and it didn't have permissions either.
Installing Magisk doesn't give me root as it spits an error can't write to /system.
I truly never thought I'd ever see TWRP on this device, this is incredible.
slayer3032 said:
I made it all the way through to mounting system with read/write, twrp console just complains that it failed to mount /system with "device or resource busy". I haven't attempted to boot into recovery again since booting into system but twrp is definitely on laf still. I did try booting from laf twrp to recovery twrp before booting to system and it didn't have permissions either.
Installing Magisk doesn't give me root as it spits an error can't write to /system.
I truly never thought I'd ever see TWRP on this device, this is incredible.
Click to expand...
Click to collapse
U can mount /system. If u still have twrp on the laf partition all u have to do is reboot twice back into twrp then go to mounts and check system, clear cache then flash the magisk zip. But one thing o truly hate about magisk is my frequencies don't stick on kernel apps so I flashed regular su and right now everything is running amazing.
---------- Post added at 02:04 PM ---------- Previous post was at 01:42 PM ----------
Also if anyone has got a bootloop after flashing something I found out that the phone reboots when you are restoring backup. To fix this flash recovery system and boot from the backup but u have to keep tapping on the screen so it dont timeout and restore wrong.
Think I will wait till next week I'm just happy you got this far
I tried to use the dirtysanta method to root my H910. Here is what I did:
1. Because I have the April 2017 security patch, I used LGUP to load up an kdz that is on Dec 2016.
This step was successful. Everything worked as expected.
2. Then I followed the dirtysanta approach, and everything worked great. I got into TWRP and wiped stuff as instructed.
3. However, at the last step, when the instruction says to adb fastboot into recovery, instead of booting back into TWRP, the phone boot into strange screen with stripes, and after a while it will show me a "kernel crash!" screen with a lot of text.
Question - is there any way to get my phone back? I cannot get into TWRP, and there is no more ADB. I also tried LGUP but it lists my phone under "unknown" model and I cannot select it.
Please anyone help me. Thanks!
zhangla said:
I tried to use the dirtysanta method to root my H910. Here is what I did:
1. Because I have the April 2017 security patch, I used LGUP to load up an kdz that is on Dec 2016.
This step was successful. Everything worked as expected.
2. Then I followed the dirtysanta approach, and everything worked great. I got into TWRP and wiped stuff as instructed.
3. However, at the last step, when the instruction says to adb fastboot into recovery, instead of booting back into TWRP, the phone boot into strange screen with stripes, and after a while it will show me a "kernel crash!" screen with a lot of text.
Question - is there any way to get my phone back? I cannot get into TWRP, and there is no more ADB. I also tried LGUP but it lists my phone under "unknown" model and I cannot select it.
Please anyone help me. Thanks!
Click to expand...
Click to collapse
Obviously you did not do enough reading on the ds root process because then you'd know static on boot is normal and you would have read about the button combo to get into twrp. I suggest you do some more reading
Sent from my LG-H910 using XDA Labs
I admit I did not read the thread fully, because it has about 2000+ posts on several hundreds of pages...
I did read the OP's instructions very carefully, and followed it word by word.
Right now, I could get into fastboot and flash TWRP again. That can get me into TWRP but any ROM I flash (either stock based, or custom ROMs), the phone will simply just get back into the static stripes and eventually crash on kernel or modem.
Is this because I should not use H910 ROMs anymore, because the DS uses other models kernels? 996?
zhangla said:
I admit I did not read the thread fully, because it has about 2000+ posts on several hundreds of pages...
I did read the OP's instructions very carefully, and followed it word by word.
Right now, I could get into fastboot and flash TWRP again. That can get me into TWRP but any ROM I flash (either stock based, or custom ROMs), the phone will simply just get back into the static stripes and eventually crash on kernel or modem.
Is this because I should not use H910 ROMs anymore, because the DS uses other models kernels? 996?
Click to expand...
Click to collapse
Flash whatever rom you want/can and then after flash preferably the mk2000 kernel (your varient) right after initial flash of rom-then reboot. Static will vanish like tacos on fat Tuesday. You can then do whatever.
Mysticblaze347 said:
Flash whatever rom you want/can and then after flash preferably the mk2000 kernel (your varient) right after initial flash of rom-then reboot. Static will vanish like tacos on fat Tuesday. You can then do whatever.
Click to expand...
Click to collapse
My problem now is that I can no longer boot into TWRP anymore.... I had recovery-twrp-h910-2018-10-18.img flashed and worked fine, but after I flashed the H910 Oreo stock rom, vol- and power then power, yes and yes to factory reset, the phone just boots into statics then LG then statics then the initial setup wizard. No more TWRP.
Trying to use fastboot to flash TWRP again, but now my phone can only be seen by adb under MTP mode, not when it's in fastboot mode.
Any way to flash TWRP when I am in regular MTP mode (e.g. regular adb)?
zhangla said:
My problem now is that I can no longer boot into TWRP anymore.... I had recovery-twrp-h910-2018-10-18.img flashed and worked fine, but after I flashed the H910 Oreo stock rom, vol- and power then power, yes and yes to factory reset, the phone just boots into statics then LG then statics then the initial setup wizard. No more TWRP.
Trying to use fastboot to flash TWRP again, but now my phone can only be seen by adb under MTP mode, not when it's in fastboot mode.
Any way to flash TWRP when I am in regular MTP mode (e.g. regular adb)?
Click to expand...
Click to collapse
I believe that via adb you can type "push" then type your directed file area of located file (twrp). Double check with google search on how push files via adb
Yeah for some odd reason adb reads via mtp (or photo transfer) only for some reason.
Mysticblaze347 said:
I believe that via adb you can type "push" then type your directed file area of located file (twrp). Double check with google search on how push files via adb
Yeah for some odd reason adb reads via mtp (or photo transfer) only for some reason.
Click to expand...
Click to collapse
The push command is to send files to external SD card while in recovery mode. I did that once. I don't think it actually flashes anything...
zhangla said:
The push command is to send files to external SD card while in recovery mode. I did that once. I don't think it actually flashes anything...
Click to expand...
Click to collapse
Might just have to redo Dirty Santa again...I really dont know what else other than researching ADB commands.
Im assuming that you already tried manual boot in twrp as Cnjax stated. Look into those as well. Different models sometimes have different button combos.
@zhangla
You best slow down and do more reading
You made another mistake
I had recovery-twrp-h910-2018-10-18.img flashed and worked fine, but after I flashed the H910 Oreo stock rom
Click to expand...
Click to collapse
The Oreo stock rom is Stock and flashes Stock recovery and removed TWRP.
Their are two v20 rooted Oreo h910 roms
you needed to use those.
You now need to start over by flashing the h915 nougat kdz and following the root guide
https://r.tapatalk.com/shareLink?ur...share_tid=3664500&share_fid=3793&share_type=t
[ROOT] HOWTO: AT&T H910 up to v20g (FULLY TESTED)
Sent from my PH-1 using Tapatalk