Database Users

[Q] Stuck on Fastboot (Unable to go to download mode)

I have an LG G2 AT&T D800.
After I rooted my phone successfully, I also flash a custom recovery successfully.
After I did that, I wipe out my data / cache.
And i tried to install a ROM and Google Apps.
I rebooted my phone and I'm stuck with " Fast boot mode started "
I had download mode working but i accidentally made it stop working after i did CMS88168 steps from this page.
http://forum.xda-developers.com/showthread.php?t=2477595
Now I don't have my download mode starting to work and I have no clue on how to fix my phone.
Please help.

alvingaoat said:
...
I rebooted my phone and I'm stuck with " Fast boot mode started "
...
Now I don't have my download mode starting to work and I have no clue on how to fix my phone.
Click to expand...
Click to collapse
Look here
It's for the F320 variants but there is also a link to search for other variant files.

Also just in case you are unable to do what phoost suggested, what i did was keep tr ying to get into recovery, the lg logo would blink fast, but you just have to keep tr ying, and i finally got it and reflashed my rom and its been fine ever since...i did get scared tho, but my g2 is only 4 days old right now, so i can always return and get another, but just do what i said

help
MasterSe7en said:
Also just in case you are unable to do what phoost suggested, what i did was keep tr ying to get into recovery, the lg logo would blink fast, but you just have to keep tr ying, and i finally got it and reflashed my rom and its been fine ever since...i did get scared tho, but my g2 is only 4 days old right now, so i can always return and get another, but just do what i said
Click to expand...
Click to collapse
My lg g2 is stuck in fastboot mode started/usd start() an I press the buttons to go to recovery mode but recovery mode just flashes on the screen an it goes back to fastboot mode screen

larryb723 said:
My lg g2 is stuck in fastboot mode started/usd start() an I press the buttons to go to recovery mode but recovery mode just flashes on the screen an it goes back to fastboot mode screen
Click to expand...
Click to collapse
I am having this issue. Has anyone figured out how to fix? I need download mode to return to stock.

Droc1983 said:
I am having this issue. Has anyone figured out how to fix? I need download mode to return to stock.
Click to expand...
Click to collapse
i got the same problem here when flashing the slimkat.
fastboot is like adb sideload.
when you see the usb command, you need to plug the phone to the PC to sync them.

This happened to me a while back the link in post two is how I solved it. You just need to find the laf.img for your model, put it in the same folder as adb and run the adb commands in the tutorial. You might have to change the directory in cmd prompt to where adb is located. Once the laf is successfully flashed you can boot into download mode and flash the kdz for your model.

Swizzle82 said:
This happened to me a while back the link in post two is how I solved it. You just need to find the laf.img for your model, put it in the same folder as adb and run the adb commands in the tutorial. You might have to change the directory in cmd prompt to where adb is located. Once the laf is successfully flashed you can boot into download mode and flash the kdz for your model.
Click to expand...
Click to collapse
I tried this but it starts download mode but then goes to fastboot. I was trying to keep download mode. I used the laf.img in the the link you posted. I'm on verizon lg g2 is that the right laf.img?
***Got it thanks***

In the link above that is for the Korean g2 I believe. If I remember correctly there's a link to other img files in his thread. You might also consider flashing the proper boot.img as well. It was a while ago that this happened so I don't recall exactly but if you flash the Verizon boot.img and laf.img you should be good.

Phoost said:
Look here
It's for the F320 variants but there is also a link to search for other variant files.
Click to expand...
Click to collapse
that link is not working

[Q] Stuck in fastboot mode after flashing wrong device image

Hey guys.
I wanted to update my LG G2 32GB from slimlat 7.4 to 7.6.
This time i was just too tired to notice, that i downloaded the wrong image for my device. I flashed the d800 (AT&T) image instead of the d802 (international). Now i am stuck at fastboot mode:
Code:
[690] Fastboot mode started
[740] udc_start()
Iam not able to access recovery mode (TWRP) by pressing power and volume down, but i can access download mode (power and volume up).
Question 1: Can is access TWRP on a different way than pressing power and volume down while starting? Because i made a backup..
This guy some how managed to get into recovery.
Question 2: If there is no way to access TWRP. Do i have to make tabula rasa using the guide recommended for "Stuck in Fastboot with Broken Download Mode" "HOW TO get back to stock when your phone stuck in fastboot mode" or is there a way to repair & access recovery?
Question 3: The Guide "Stuck in Fastboot with Broken Download Mode" confused me, because it says: "First in fastboot mode (refer to my previous post, I enter it by plugging USB into G2 with pressing the volume + )" When i press power and volume up (which is +, right?) i access "download mode", but not fastboot mode. It looks like this. Does this mean my "download mode" is still operational and i can skip this guide?
Question 4: When i can skip the latter guide, do i have to continue with this (LG G2 Stock Firmware (Go Back to Stock)) one? Do i need to go back to stock to access TWRP and restore my backup?
I hope i haven't confused you with too many questions. I really looking forward to your answers. Thanks in advance for your help!
greetings mellhen

mellhen said:
Hey guys.
I wanted to update my LG G2 32GB from slimlat 7.4 to 7.6.
This time i was just too tired to notice, that i downloaded the wrong image for my device. I flashed the d800 (AT&T) image instead of the d802 (international). Now i am stuck at fastboot mode:
Code:
[690] Fastboot mode started
[740] udc_start()
Iam not able to access recovery mode (TWRP) by pressing power and volume down, but i can access download mode (power and volume up).
Question 1: Can is access TWRP on a different way than pressing power and volume down while starting? Because i made a backup..
This guy some how managed to get into recovery.
Question 2: If there is no way to access TWRP. Do i have to make tabula rasa using the guide recommended for "Stuck in Fastboot with Broken Download Mode" "HOW TO get back to stock when your phone stuck in fastboot mode" or is there a way to repair & access recovery?
Question 3: The Guide "Stuck in Fastboot with Broken Download Mode" confused me, because it says: "First in fastboot mode (refer to my previous post, I enter it by plugging USB into G2 with pressing the volume + )" When i press power and volume up (which is +, right?) i access "download mode", but not fastboot mode. It looks like this. Does this mean my "download mode" is still operational and i can skip this guide?
Question 4: When i can skip the latter guide, do i have to continue with this (LG G2 Stock Firmware (Go Back to Stock)) one? Do i need to go back to stock to access TWRP and restore my backup?
I hope i haven't confused you with too many questions. I really looking forward to your answers. Thanks in advance for your help!
greetings mellhen
Click to expand...
Click to collapse
To access twrp try power + vol down then vol up + vol down. If that doesn't work then no you cannot access your recovery.
Your actually in a much better position than the guy in that guide. You've got download mode so you can skip to the easy part and just follow the back to stock guide.
You can also use fastboot mode to flash the correct partitions if you want by setting up adb and using fastboot commands with all the partition images. Its up to you.

Art Vanderlay said:
To access twrp try power + vol down then vol up + vol down. If that doesn't work then no you cannot access your recovery.
Your actually in a much better position than the guy in that guide. You've got download mode so you can skip to the easy part and just follow the back to stock guide.
You can also use fastboot mode to flash the correct partitions if you want by setting up adb and using fastboot commands with all the partition images. Its up to you.
Click to expand...
Click to collapse
Hey Vanderlay.
Thanks for your reply,
I tried to access recovery using your suggestion, but the time between turning the device on and "fastboot mode" is just to small to press key combinations.
You mentioned that i can use ADB commands to manually write on the G2 partitions. Honestly i don't know exactly what the problem is and therefore i have no clue which partitions have to be written on. What i understand is, that i cant boot because the kernel of the D800 is different from the D802. But i dont get, why i cant access recovery. Is TWRP somehow destroyed so i have to write a new one on the recovery partition or do i need the correct rom image to access recovery? If you could explain me this or have a link to a good explanation i would be very grateful.
[EDIT]
I have fast boot access. But as far as i know fastboot only allows to flash stock images (what a shame) as the commands are interpreted vendor specifc. Nevertheless i found that you can flash recovery by
Code:
fastboot flash recovery recovery.img
But as i don't know if the recovery is destroyed or the correct rom-image is needed to simply access recovery, i cant continue here.
Am I right assuming that there is know way to repair recovery, boot into it and simply restore from my backup? Do i realy have to go back to stock, re-root it and install custom recovery again, to be able to restore from my backup?

If you've got a system then just flash your original kernel
fastboot flash boot boot.img
and
fastboot flash aboot aboot.img
and
fastboot flash laf laf.img (download mode)
your original files please..

bender_007 said:
If you've got a system then just flash your original kernel
fastboot flash boot boot.img
and
fastboot flash aboot aboot.img
and
fastboot flash laf laf.img (download mode)
your original files please..
Click to expand...
Click to collapse
My backup is stored on the internal SD-card (as i was simply to lazy to transfer it to my PC). As i cant remove this card from my phone i don't know to flash the phone via fastboot.
Is there a way to command fastboot to acceess those files on the internal SD-card?
Or is there a way to transfer those files from the internal SD-card to my PC?

Download slimkat d802 kernel, extract boot.img and flash itcvia fastboot

bender_007 said:
Download slimkat d802 kernel, extract boot.img and flash itcvia fastboot
Click to expand...
Click to collapse
I downloaded the complete image for d802 and extracted the boot image. I connected the phone via fastboot and did
Code:
C:\Users\XX>fastboot flash boot boot.img
target reported max download size of 1862270976 bytes
sending 'boot' (6284 KB)...
OKAY [ 0.264s]
writing 'boot'...
OKAY [ 0.526s]
finished. total time: 0.797s
And then
Code:
C:\Users\hen>fastboot reboot
rebooting...
finished. total time: 0.104s
Now iam getting a secure boot error cause boot certification verify.
EDIT:
I cant access neither recovery, nor fastboot or download mode.

By "image" what exactly do you meanm

bender_007 said:
By "image" what exactly do you meanm
Click to expand...
Click to collapse
I downloaded the rom image. There i found boot.img and extracted it. I couldnt find a kernel file on the slimroms server. But should a complete rom also contain a kernel?
EDIT: As i cant access download-mode, fastboot or recovery i should continue here, right?

Exactly. I'll try to help you 2 out although I see you searched already

bender_007 said:
Exactly. I'll try to help you 2 out although I see you searched already
Click to expand...
Click to collapse
Ok, i continue with these instructions with my kubuntu laptop at home. This will be in about 1h.
[EDIT]
Ok back. My kubuntu was able to recognize my G2, i see all partitions. But i couldn't find the files for the 32GB Model, only 16GB. Some guys (Jilke, Ixan) had the same issue and bender_007 suggested to use the 16GB versions. But i couldnt find any confirmation, if the 16GB files worked for the 802.32GB. Have i overlooked a post, which confirmed this suggestion?

mellhen said:
Ok, i continue with these instructions with my kubuntu laptop at home. This will be in about 1h.
[EDIT]
Ok back. My kubuntu was able to recognize my G2, i see all partitions. But i couldn't find the files for the 32GB Model, only 16GB. Some guys (Jilke, Ixan) had the same issue and bender_007 suggested to use the 16GB versions. But i couldnt find any confirmation, if the 16GB files worked for the 802.32GB. Have i overlooked a post, which confirmed this suggestion?
Click to expand...
Click to collapse
Since the kdz is the same for all you can use it.
use just the aboot, boot and laf
Do you need any further assistance ?

Hey bender_007 was it wrong to use the boot.img from the rom file instead of a kernel file?
bender_007 said:
Since the kdz is the same for all you can use it.
use just the aboot, boot and laf
Click to expand...
Click to collapse
I used the files for the european 802 16GB device from here: http://downloads.codefi.re/autoprime/LG/LG_G2/D802/Stock_Firmware/10b_EUR_16G_partitions
The original thread says i should use 1- sbl1.img, 2- aboot.img, 3- rpm.img and 4- tz.img
Why do i not need slbl1, rpm and tz, but instead boot and laf? I dont get that (?).
[EDIT]
So i just started beginning with aboot. Which yours and the original instructions have in common. I didn't care about the bin-extension, as it usually makes no difference in linux.
Code:
[email protected]:~# dd if=/home/mellhen/Entwicklung/android/LG\ G2/partition\ images/4-aboot.bin of=/dev/sdb5
2048+0 Datensätze ein
2048+0 Datensätze aus
1048576 Bytes (1,0 MB) kopiert, 0,278651 s, 3,8 MB/s
Continued with boot. As you have recommended this (aboot, boot and laf) procedure to another guy in that thread, this seems to be an update to the original instruction?
Code:
[email protected]:~# dd if=/home/mellhen/Entwicklung/android/LG\ G2/partition\ images/6-boot.bin of=/dev/sdb7
21504+0 Datensätze ein
21504+0 Datensätze aus
11010048 Bytes (11 MB) kopiert, 2,97537 s, 3,7 MB/s
And finally laf
Code:
[email protected]:~# dd if=/home/mellhen/Entwicklung/android/LG\ G2/partition\ images/laf.bin of=/dev/sdb23
31744+0 Datensätze ein
31744+0 Datensätze aus
16252928 Bytes (16 MB) kopiert, 5,13812 s, 3,2 MB/s
So i will try to reboot in TWRP now.
[EDIT 2]
I cant access recovery. I see an LG logo without text and a blue-green pulsing LED. I can't turn the device of and it gets hot.
I had a lot nearly bricked devices, but now i get scared! How can i continue?
greetings

You can't get to twrp but tou can get to download mode. Turn the g2 off, disconnect it first. Then hold volume up and connect it to pc

bender_007 said:
You can't get to twrp but tou can get to download mode. Turn the g2 off, disconnect it first. Then hold volume up and connect it to pc
Click to expand...
Click to collapse
Ok, i really had cold sweat and have had to take a deep breath. It was the first time that i was really scared. In older devices you can pull the battery but this one is known to burn itself (or at least its screen).
I am now in download mode and it stopped heating. I had to first plug it in. Then turn it off and when it turned off press volume up. Shall i continue with the LG G2 Stock Firmware (Go Back to Stock)? Can i continue using linux?
OT: How far have you brought your devices to the abyss of death?

Yap. Use the flash tool 2014 . You're good to go

I followed the instructions and flashed "Europe OPEN D80220B_00". The process continued to 100% (both mobile and flash tool 2014). After this the phone rebooted, i could see the LG logo again and now it stays at the green droid "doing something" since 6 minutes. The phone is still connected to the Windows computer. Shall i wait a little longer? unplug the phone? reboot the phone?
[EDIT] i just took its time, it started finally! bender_007 how can i thank you for your patience(!)?

Np m8, you did all the work and research, that's the real way.

bender_007 said:
Np m8, you did all the work and research, that's the real way.
Click to expand...
Click to collapse

bender_007 said:
Since the kdz is the same for all you can use it.
use just the aboot, boot and laf
Do you need any further assistance ?
Click to expand...
Click to collapse
Hi,
I need your help.
Flashed wrong kernel 16 g on 32 g
my G2 is now having below issues ,please help.
bootloop,touch screen problem,no recovery mode or fastboot mode,
download mode is working.
Couple of time it booted normally but touch is not working properly and then it goes for reboot.
I want to flash original kernel but i am not able to get into fastboot

Yoga Tab 2 (830,1050,1380) - TWRP 2.8.7.0(6)

'what? lol'

1050F - All Good!
Thanks!

YamYam

ionioni said:
you tried to flash a partition from dnx mode
Click to expand...
Click to collapse
Doh... Been so confused lately....

workdowg said:
Doh...
Click to expand...
Click to collapse
maybe you should put that SMT AoL on a break... the YT2 one is almost forgotten.

ionioni said:
maybe you should put that SMT AoL on a break... the YT2 one is almost forgotten.
Click to expand...
Click to collapse
Probably... I had 3 or 4 more people interested... I posted the working MicroSD install files... But I do feel lonely...

Thanks brother, I will test in upcoming Saturday and will revert back.

a beginner's guide....tnx[emoji1] [emoji1]

@workdowg now that we have a permanent recovery does this mean we can start building cm and kernels? I am almost setup with my machine (just configuring Ubuntu). From what I have read on lenovo website is they messed something up with the charging and battery life in the last update

pug1 said:
@workdowg now that we have a permanent recovery does this mean we can start building cm and kernels? I am almost setup with my machine (just configuring Ubuntu). From what I have read on lenovo website is they messed something up with the charging and battery life in the last update
Click to expand...
Click to collapse
Since the bootloader is unlocked you may do what you wish. Permanent TWRP will make the job easier. Have at it!
As far as the current ROM from Lenovo.... It is really stable for me. I froze the usual suspects and I get about 3-4 days with 8-9hrs SOT. I don't game on this tablet and keep the brightness down to about 1/3.

updated: added compilation from 6.0 sources - TWRP 2.8.7.0(6)

ionioni said:
updated: added compilation from 6.0 sources - TWRP 2.8.7.6
Click to expand...
Click to collapse
Pretty... all good on the 1050F.

1050F (Latest LP OTA): I am able to flash it (bl is unlocked), but cannot access it after that. Stock recovery is still present... am I missing sth??

dtrail1 said:
1050F (Latest LP OTA): I am able to flash it (bl is unlocked), but cannot access it after that. Stock recovery is still present... am I missing sth??
Click to expand...
Click to collapse
it works in the 'live' mode? from dnx (PwrOn with both Vol pressed, screen shows 'fastboot starting...' message):
fastboot flash osloader bootx64.efi
fastboot boot twrp-1050f-b.img
you should also try to boot in the recovery right AFTER you flash it and if it goes twrp means that recovery from boot is still active on your build (and will write the recovery partition with a fresh image that he builds from the boot partition on each normal android start)
what is the OTA you're on?

ionioni said:
it works in the 'live' mode? from dnx (PwrOn with both Vol pressed, screen shows 'fastboot starting...' message):
fastboot flash osloader bootx64.efi
fastboot boot twrp-1050f-b.img
you should also try to boot in the recovery right AFTER you flash it and if it goes twrp means that recovery from boot is still active on your build (and will write the recovery partition with a fresh image that he builds from the boot partition on each normal android start)
Click to expand...
Click to collapse
Already figured it, but thx!! I forgot to FIRST boot it from DNX mode once, and then flash it permanently from fb mode. thx

I have followed each steps mentioned to flash perm. twrp recovery on my YOGA Tablet 2-830LC lollipop, unlocked bootloader; the process of flashing completes successfully yet I am unable to enter into recovery... When ever I try to enter into recovery it simply boots up normally... I have tried entering recovery by both hardware and software modes, but it fails... Kindly help me out of this mess...
Thank you

QuazIqbal said:
I have followed each steps mentioned to flash perm. twrp recovery on my YOGA Tablet 2-830LC lollipop, unlocked bootloader; the process of flashing completes successfully yet I am unable to enter into recovery... When ever I try to enter into recovery it simply boots up normally... I have tried entering recovery by both hardware and software modes, but it fails... Kindly help me out of this mess...
Thank you
Click to expand...
Click to collapse
while i don't know 100% whether it is working or not on your model and since those who download the files don't give their feedback...
try rebooting in recovery, when in normal android, send a adb reboot recovery or boot in fastboot mode and chose the RECOVERY as target with Volkeys and activate with Power button
check also that you flashed the correct img file (you did unzipped the file before flashing no? ) fastboot flash recovery twrp....img

ionioni said:
while i don't know 100% whether it is working or not on your model and since those who download the files don't give their feedback...
try rebooting in recovery, when in normal android, send a adb reboot recovery or boot in fastboot mode and chose the RECOVERY as target with Volkeys and activate with Power button
check also that you flashed the correct img file (you did unzipped the file before flashing no? ) fastboot flash recovery twrp....img
Click to expand...
Click to collapse
I tried all the ways including 'adb reboot recovery and also tried to enter recovery through droidboot but each time it simply rebooted without going into recovery.... I also tried the temp recovery, by these commands "fastboot flash osloader bootx64.efi" & "fastboot boot twrp-830f-b.img" in this case also it simply rebooted in to android os.
P. S. I am able to enter twrp recovery through social design recovery.

any 830 owner can confirm if it is working or not on his device?

QuazIqbal said:
I tried all the ways including 'adb reboot recovery and also tried to enter recovery through droidboot but each time it simply rebooted without going into recovery.... I also tried the temp recovery, by these commands "fastboot flash osloader bootx64.efi" & "fastboot boot twrp-830f-b.img" in this case also it simply rebooted in to android os.
P. S. I am able to enter twrp recovery through social design recovery.
Click to expand...
Click to collapse
1. when you are entering the above two commands are you in DNX mode? ('fastboot starting' on screen)
2. when you upgraded to Lollipop did you used the OTA update process or you just flashed a stock Lollipop rom?
3. boot to your normal Android OS and open Contacts and in the search contacts box enter ####0000# it will open a VersionInfo window, tell me what it says under BIOS version line
by these commands "fastboot flash osloader bootx64.efi" & "fastboot boot twrp-830f-b.img" in this case also it simply rebooted in to android os.
Click to expand...
Click to collapse
4. right after you entered the commands it rebooted (ie you heard the tab buzzing as if you power on from off state) or just continued and booted t Android?

Help please can't see my phone in adb

I've had my Essential two weeks i was on 8.1 beta.Today i unlocked the boot loader.Then installed twrp while in twrp i side loaded magisk.I went back to fastboot then hit start .The phone just went into a bootloop.I Was able to go back to twrp 2 times but now i can't get back to any type of recovery.I Can get back to fastboot mode ishow all the info and secure boot says yes and device state unlocked.My pc see essential phone fastboot in the device manager but i can't get adb to see it .Can anyone help me ?

forgot something
looks like i skipped this part . Once you're in TWRP, install the stock boot image and then the Magisk/SuperSU zip.Is there anything i can do?

videodave1 said:
I've had my Essential two weeks i was on 8.1 beta.Today i unlocked the boot loader.Then installed twrp while in twrp i side loaded magisk.I went back to fastboot then hit start .The phone just went into a bootloop.I Was able to go back to twrp 2 times but now i can't get back to any type of recovery.I Can get back to fastboot mode ishow all the info and secure boot says yes and device state unlocked.My pc see essential phone fastboot in the device manager but i can't get adb to see it .Can anyone help me ?
Click to expand...
Click to collapse
adb only works while phone is booted into system so nothing wrong there. If you're in the bootloader menu where you see that the status of your device is unlocked then you're already in fastboot mode. Just flash twrp again and the sideload stock 8.1 beta boot image (you can probably find it on xda), sideload magisk too. Go into install and press flash image file and find the stock boot image and then go into install again and change to flash .zip and flash magisk. After that, reboot into system.

WOW thank you so much'
Arju said:
adb only works while phone is booted into system so nothing wrong there. If you're in the bootloader menu where you see that the status of your device is unlocked then you're already in fastboot mode. Just flash twrp again and the sideload stock 8.1 beta boot image (you can probably find it on xda), sideload magisk too. Go into install and press flash image file and find the stock boot image and then go into install again and change to flash .zip and flash magisk. After that, reboot into system.
Click to expand...
Click to collapse
I was able to flash twrp i'll try the rest when i get home from work

sideloading stock img
videodave1 said:
I was able to flash twrp i'll try the rest when i get home from work
Click to expand...
Click to collapse
Do i need it to be zipped I've tried it as image that i downloaded from xda and I've tried a zip i got from Essential neither are working?

zip file
videodave1 said:
Do i need it to be zipped I've tried it as image that i downloaded from xda and I've tried a zip i got from Essential neither are working?
Click to expand...
Click to collapse
When i try i get invalid file format. This is using a zip i got from Essential.

Stuck twrp says no os installed . But i did learn how to push files.

just trying to get back to stock now 

videodave1 said:
just trying to get back to stock now 
Click to expand...
Click to collapse
https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681

thanks been there tried the Oreo beta that is what i was on when i started and tried the 1st build before the betas i get an error on both i'll try to download them on another pc my phone does show up when i type fastboot devices now just need an os now .

Okay got back to 8.1 bootloader still unlocked twrp not install and i don't have root.I may just wait until P comes out.I'll try and learn more about adb. Thanks for your help Arju.

thanks everyone.

videodave1 said:
Okay got back to 8.1 bootloader still unlocked twrp not install and i don't have root.I may just wait until P comes out.I'll try and learn more about adb. Thanks for your help Arju.
Click to expand...
Click to collapse
No problem. Thank you very much for the donation, that was really kind of you. Hey I'm sure you'll get the hang of it before android P drops. you did figure out what went wrong all by yourself so get a hold of the right boot.img and the rest is exactly as how you did it in the first place but flash the boot.img before magisk. Let me know if you want to give it a dive again.

I'm on 8.1 boot loader unlocked and ready to try to root again .Thanks for the help

This is the closest thread i could find to what is happening to my PH-1.
Like videodave1 I 'was' running the latest stock 8.1 and have my bootloader unlocked. In trying to root the phone I did this:
flash boot flash boot twrp.img
adb shell twrp sideload
adb sideload magisk.zip
All installations went well, but when trying to reboot from twrp it forced me to install the app. After that the phone went into boot loop.
* Note how I didn't sideloaded the Oreo 8.1 image before magisk.
By pressing all 3 buttons I can get the phone to reboot and releasing the volume up I can get to Fastboot. Just volume down and power doesn't work.
The problem now is that adb and fastboot no longer recognise the phone. adb devices just gives an empty list and fastboot only shows < waiting for device >
Trying to go into Recovery mode doesn't work either. Power off doesn't work and Restart bootloader, well, restarts the bootloader.
It might be relevant to mention that I'm running adb and fastboot from Terminal in a Mac and that this is my very first and frustrated attempt to root any phone.
For reference this is what the FastBoot Mode brings:
PRODUCT_NAME - Mata
VARIANT - OPENUS
BOOTLOADER VERSION - mata-aad8ac4
BASEBAND VERSION - 2.0.C4-M1.3.1
SECURE BOOT - yes
DEVICE STATE - unlocked
I might have to just resign myself to the ordinary land of unlocked full stock phones
Thanks very much

avocom said:
This is the closest thread i could find to what is happening to my PH-1.
Like videodave1 I 'was' running the latest stock 8.1 and have my bootloader unlocked. In trying to root the phone I did this:
flash boot flash boot twrp.img
adb shell twrp sideload
adb sideload magisk.zip
All installations went well, but when trying to reboot from twrp it forced me to install the app. After that the phone went into boot loop.
* Note how I didn't sideloaded the Oreo 8.1 image before magisk.
By pressing all 3 buttons I can get the phone to reboot and releasing the volume up I can get to Fastboot. Just volume down and power doesn't work.
The problem now is that adb and fastboot no longer recognise the phone. adb devices just gives an empty list and fastboot only shows < waiting for device >
Trying to go into Recovery mode doesn't work either. Power off doesn't work and Restart bootloader, well, restarts the bootloader.
It might be relevant to mention that I'm running adb and fastboot from Terminal in a Mac and that this is my very first and frustrated attempt to root any phone.
For reference this is what the FastBoot Mode brings:
PRODUCT_NAME - Mata
VARIANT - OPENUS
BOOTLOADER VERSION - mata-aad8ac4
BASEBAND VERSION - 2.0.C4-M1.3.1
SECURE BOOT - yes
DEVICE STATE - unlocked
I might have to just resign myself to the ordinary land of unlocked full stock phones
Thanks very much
Click to expand...
Click to collapse
Even though your phone does not show up its there wipe everything.Fallow what Arju said in his post.I got back to stock then took the 8.1 update i'm not rooted but my bootloader is still unlocked.Oh make sure you unlock critical

videodave1 said:
Fallow what Arju said in his post.
Click to expand...
Click to collapse
Thanks for coming back to me. I really appreciate it.
Arju said:
Just flash twrp again and the sideload stock 8.1 beta boot image (you can probably find it on xda), sideload magisk too.
Click to expand...
Click to collapse
I might be missing something hopefully obvious here. How can I flash twrp again if I my computer can't see the phone. With the USB phone plugged in and in the FastBoot screen I enter into Terminal:
fastboot flash boot twrp.img
and I get:
< waiting for any device >
How do I flash it from the FastBoot screen? BTW, going to Recovery mode just hangs at the Essential logo.
Thanks

avocom said:
Thanks for coming back to me. I really appreciate it.
I might be missing something hopefully obvious here. How can I flash twrp again if I my computer can't see the phone. With the USB phone plugged in and in the FastBoot screen I enter into Terminal:
fastboot flash boot twrp.img
and I get:
< waiting for any device >
How do I flash it from the FastBoot screen? BTW, going to Recovery mode just hangs at the Essential logo.
Thanks
Click to expand...
Click to collapse
are you able to get to the bootloader menu? where it says start on the top.

Arju said:
are you able to get to the bootloader menu? where it says start on the top.
Click to expand...
Click to collapse
Thanks Arju. If you are referring to the FastBoot menu where you can use the up and down volume keys to select Start, Restart Bootloader, Recovery mode and Power off Yes, but not much else unfortunately.
If I select Recovery mode I don't go to the screen with the blue buttons from twrp.
Thanks

avocom said:
Thanks Arju. If you are referring to the FastBoot menu where you can use the up and down volume keys to select Start, Restart Bootloader, Recovery mode and Power off Yes, but not much else unfortunately.
If I select Recovery mode I don't go to the screen with the blue buttons from twrp.
Thanks
Click to expand...
Click to collapse
What you need to understand is that twrp will not stick after you flash it. This device does not have a recovery partition and that's why you replace the boot partition with twrp and while you're in twrp you need to flash the boot.img back and whatever mods on top of that such as kernel etc.. If you flash a rom then it will replace the twrp with the boot.img found in the rom zip.
So now we need the computer to recognize you device. Could you unplug the cable and change the usb port on you computer. connect your phone while you're in the bootloader menu where it says start on the top.
The use use fastboot command: fastboot devices
See if the computer recognizes you device.

Error in installing twrp

Hy everyone ineed help..
I have h990ds in nouget android security before 2016.
I try to root but in the middle of proses,its error, i try to flashing by lgup but the screen only flashboot mode. :crying::crying:
The some words in my screen:
Fastboot mode(red color)
Product name_msm8996 64gb
Varian_msm8996 64gb
Hw version_rev10
Bla...
Serial number -lgus996af7da36 (my type h990ds)
Secure boot-disable
Lock state_lock
[1090]
[1140]fastboot mode started
There 3 steps .bat after runfirsttime.bat
An i click step3 after step 2.

nuqudlover said:
Hy everyone ineed help..
I have h990ds in nouget android security before 2016.
I try to root but in the middle of proses,its error, i try to flashing by lgup but the screen only flashboot mode. :crying::crying:
The some words in my screen:
Fastboot mode(red color)
Product name_msm8996 64gb
Varian_msm8996 64gb
Hw version_rev10
Bla...
Serial number -lgus996af7da36 (my type h990ds)
Secure boot-disable
Lock state_lock
[1090]
[1140]fastboot mode started
There 3 steps .bat after runfirsttime.bat
An i click step3 after step 2.
Click to expand...
Click to collapse
The good news is that you've got the dirtysanta bootloader installed (that's why it's reporting us996) so you should be able to fix it without using LG UP and having to redo most of the process.
Install twrp by doing fastboot flash path/to/twrp.img .then pull the battery when done. Then enter twrp by using to volume key method (hold volume down, press power until the screen turns on, then tap power repeatedly until a menu asking to factory reset appears, say yes (while twrp is installed it won't actually wipe anything).)
Flash a rom (a stock one is here), and magisk.
If you can't use an sdcard to get them accessible to the phone in twrp, in twrp you can go into advanced then sideload and connect to a PC and do adb sideload path/to/rom-or-magisk.zip

Phoenix591 said:
The good news is that you've got the dirtysanta bootloader installed (that's why it's reporting us996) so you should be able to fix it without using LG UP and having to redo most of the process.
Install twrp by doing fastboot flash path/to/twrp.img .then pull the battery when done. Then enter twrp by using to volume key method (hold volume down, press power until the screen turns on, then tap power repeatedly until a menu asking to factory reset appears, say yes (while twrp is installed it won't actually wipe anything).)
Flash a rom (a stock one is here), and magisk.
If you can't use an sdcard to get them accessible to the phone in twrp, in twrp you can go into advanced then sideload and connect to a PC and do adb sideload path/to/rom-or-magisk.zip
Click to expand...
Click to collapse
After use adb fastboot flash recovery twrp.img, there's new problem.
Using volume key mode my screen is blank, just like broken TV.. :crying::crying:

nuqudlover said:
After use adb fastboot flash recovery twrp.img, there's new problem.
Using volume key mode my screen is blank, just like broken TV.. :crying::crying:
Click to expand...
Click to collapse
to totally back out and bring your phone to totally stock use download mode (from powered off hold volume UP while connecting to the pc). The screen will be still messed up but it will still work on the pc.
Use patched LG UP in partition dl mode to flash everything with a stock h990(ds) kdz.
Once you start using dirtysanta next time (if you decide to try again) be very very careful when using LG UP (easier to just use stock flashabile zip) unless you want to redo the above and flash EVERYTHING back to stock (if you ever flash the aboot partition in LG UP and anything ISN'T stock it will brick you! This mostly applies to partition dl mode since upgrade mode flashes everything, but partition dl mode is the only mode you can even potentially flash things and keep root (but I don't encourage this... its easier and saferto just use zips in TWRP to flash firmware (mostly stock basedrom or so called stock flashible zips tend to also flash all of the firmware except parts needed to keep root. )

Phoenix591 said:
to totally back out and bring your phone to totally stock use download mode (from powered off hold volume UP while connecting to the pc). The screen will be still messed up but it will still work on the pc.
Use patched LG UP in partition dl mode to flash everything with a stock h990(ds) kdz.
Once you start using dirtysanta next time (if you decide to try again) be very very careful when using LG UP (easier to just use stock flashabile zip) unless you want to redo the above and flash EVERYTHING back to stock (if you ever flash the aboot partition in LG UP and anything ISN'T stock it will brick you! This mostly applies to partition dl mode since upgrade mode flashes everything, but partition dl mode is the only mode you can even potentially flash things and keep root (but I don't encourage this... its easier and saferto just use zips in TWRP to flash firmware (mostly stock basedrom or so called stock flashible zips tend to also flash all of the firmware except parts needed to keep root. )
Click to expand...
Click to collapse
I already use lgup pacher, when connected the message unknown model
Can i using flash laf.bin from fastbootmode?

nuqudlover said:
I already use lgup pacher, when connected the message unknown model
Can i using flash laf.bin from fastbootmode?
Click to expand...
Click to collapse
But did you use partition dl mode? It alone bypasses the model checks.
Partition dl mode isn't in regular lg up, you need the special patched version I linked (replace the files of your regular lg up with the special version)

Phoenix591 said:
But did you use partition dl mode? It alone bypasses the model checks.
Partition dl mode isn't in regular lg up, you need the special patched version I linked (replace the files of your regular lg up with the special version)
Click to expand...
Click to collapse
I already put your special patched to my Lgup..

nuqudlover said:
I already put your special patched to my Lgup..
Click to expand...
Click to collapse
Try uppercut then. Use upgrade mode if it works but partition dl mode is missing. Note uppercut asks for lg up version 1.14 . I can't remember what version the patched one is but you may have to reinstall that version instead.