Related
One of my costumer V20 is now stuck in fastboot.
Whatever I do, it's keep coming back to fastboot mode.
I can enter download mode, and try flash , even using the costum LG up, with upgrade option, partition DL option.
I use Box ( octopus, Z3x ).
I don't know what is wrong with this phone.
it's only going back to fastboot.
Any help is really apreciated.
Thank You.
sing2x said:
One of my costumer V20 is now stuck in fastboot.
Whatever I do, it's keep coming back to fastboot mode.
I can enter download mode, and try flash , even using the costum LG up, with upgrade option, partition DL option.
I use Box ( octopus, Z3x ).
I don't know what is wrong with this phone.
it's only going back to fastboot.
Any help is really apreciated.
Thank You.
Click to expand...
Click to collapse
What does using the "fastboot reboot" cmd do ?
Ak7J4 said:
What does using the "fastboot reboot" cmd do ?
Click to expand...
Click to collapse
It goes back straight to fastboot after LG logo
If you can get into download mode try the 'upgrade' option in lgup
It is stuck in fastboot because your customer tried to root it with lafsploit without unlocking the bootloader.
They have two choices:
1 - Send it to LG to have it repaired.
2 - Wait for me to finish lafsploit 2.0 which will unlock their bootloader, and their phone will just start working.
The partitions that hold the unlock information are not touched when you flash a KDZ, so no amount of flashing is going to fix it.
-- Brian
runningnak3d said:
It is stuck in fastboot because your customer tried to root it with lafsploit without unlocking the bootloader.
They have two choices:
1 - Send it to LG to have it repaired.
2 - Wait for me to finish lafsploit 2.0 which will unlock their bootloader, and their phone will just start working.
The partitions that hold the unlock information are not touched when you flash a KDZ, so no amount of flashing is going to fix it.
-- Brian
Click to expand...
Click to collapse
I think that's what happen, and I don't have any choice except to wait . Returning to LG is not an option.
Thank you very much sir.
did you get to solve this problem also have one stuck in fastboot mode but no download mode
boot loader seem to be lock
thee011 said:
did you get to solve this problem also have one stuck in fastboot mode but no download mode
boot loader seem to be lock
Click to expand...
Click to collapse
If you cant get into download mode by powering off, holding vol up and then plugging into a pc (no power button needed) then you dont have a phone anymore. Unless rooted via dirtysanta which replaces aboot (which provides fastboot), the stock fastboot mode of the h918 can't actually flash anything to the phone which means no unbricking with it; TWRP and download mode are only ways to restore firmware.
I know this is an old thread but my gf has the h918 which is unlocked with twrp Installed, she tried updating magisk from inside magisk and now she's stuck in fastboot mode .The fastboot reboot command does not reboot the phone I even booted into twrp and wiped cache any ideas?
wolf45801 said:
I know this is an old thread but my gf has the h918 which is unlocked with twrp Installed, she tried updating magisk from inside magisk and now she's stuck in fastboot mode .The fastboot reboot command does not reboot the phone I even booted into twrp and wiped cache any ideas?
Click to expand...
Click to collapse
This is a Magisk 20.2 issue there's at two threads in the LGV20 forum on how to recover
Sent from my LG-H910 using XDA Labs
So here is what happened. I decided to take a crack at twrp and rooting my essential phone. its fully updated to aprils patch
unlocked my bootloader. HOWEVER i never used the command fastboot flashing unlock_critical. how ever it still said my boot loaders unlocked.
installed twrp no issue (other then touch but i figured that out) installed elementalx kernal. made a backup in twrp just in case.
booted into android fine no problems. found out my wifi does not work. ok now im just giving up. found out flashing the boot img will fix it. well i flashed it via twrp and when it asked where i said to the boot.
now my phone boot loops. i cant get into twrp. only a default recovery mode for android. i can get into the boot loader but im scared because ADB cant find my device anymore. trying to wipe deivce makes it reboot and boot loop again.
am i screwed? i dont care about the data but its 3am and i think i really messed up my phone
xhakz said:
So here is what happened. I decided to take a crack at twrp and rooting my essential phone. its fully updated to aprils patch
unlocked my bootloader. HOWEVER i never used the command fastboot flashing unlock_critical. how ever it still said my boot loaders unlocked.
installed twrp no issue (other then touch but i figured that out) installed elementalx kernal. made a backup in twrp just in case.
booted into android fine no problems. found out my wifi does not work. ok now im just giving up. found out flashing the boot img will fix it. well i flashed it via twrp and when it asked where i said to the boot.
now my phone boot loops. i cant get into twrp. only a default recovery mode for android. i can get into the boot loader but im scared because ADB cant find my device anymore. trying to wipe deivce makes it reboot and boot loop again.
am i screwed? i dont care about the data but its 3am and i think i really messed up my phone
Click to expand...
Click to collapse
Are you still bootloader unlocked?? Can flash files via fastboot? If you can run the command "fastboot flashing unlock_critical" and then flash bts from this thread https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681
Tech_Savvy said:
Are you still bootloader unlocked?? Can flash files via fastboot? If you can run the command "fastboot flashing unlock_critical" and then flash bts from this thread https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681
Click to expand...
Click to collapse
hey hope all is well im sorry for the late reply. i was able to figure everything out i flash the wrong boot.img and twrp its not perm on my device. I saw a threat that lets you go back to stock and has aprils build. thanks for your help tho!!!!!
my nexus 6p is not booting into rom, recovery (stock and custom).
i have a unlocked bootloader, flashed custom recovery(twrp) by fastboot but can't get in to twrp as i wanted to flash blod patch to use 4cores to work.
i tried flashing stock images of MM, Nougat, Oreo using platform tools by google but getting an error like see in the attachment:crying:.
i tried it with fastboot by manually entering commands it will flash but not use still bootlooping.
i tried toolkits like NRT & all in one toolkit by XDA member this toolkits can flash stock rom successfully but cant get boot into system, stock recovery.
help me with your answers. my status is "unlocked bootloader, fastboot working, can access bootloader but can't get into recovery from it".
getting couldn't parse partition size 0x when booting boot img through platform tools.
tell me if i did any mistake. Thank you.
You tried stock images. Does that include factory images? That erases and reflashes quite literally everything (bootloader, recovery, system, etc.)
Find them here for 6P: https://developers.google.com/android/images#angler
Santhosh Jangamgari said:
my nexus 6p is not booting into rom, recovery (stock and custom).
i have a unlocked bootloader, flashed custom recovery(twrp) by fastboot but can't get in to twrp as i wanted to flash blod patch to use 4cores to work.
i tried flashing stock images of MM, Nougat, Oreo using platform tools by google but getting an error like see in the attachment:crying:.
i tried it with fastboot by manually entering commands it will flash but not use still bootlooping.
i tried toolkits like NRT & all in one toolkit by XDA member this toolkits can flash stock rom successfully but cant get boot into system, stock recovery.
help me with your answers. my status is "unlocked bootloader, fastboot working, can access bootloader but can't get into recovery from it".
getting couldn't parse partition size 0x when booting boot img through platform tools.
tell me if i did any mistake. Thank you.
Click to expand...
Click to collapse
You didn't mention which custom recovery you flashed. Did you try the one in this thread? https://forum.xda-developers.com/t/...-death-blod-workaround-flashable-zip.3819515/
If you did and you still can't get into it, your device is likely dead from the BLOD. But to make sure you have the BLOD, flash the latest factory image first (Dec. 2018) with the latest platform tools to see if it boots... https://developer.android.com/studio/releases/platform-tools
Lughnasadh said:
You didn't mention which custom recovery you flashed. Did you try the one in this thread? https://forum.xda-developers.com/t/...-death-blod-workaround-flashable-zip.3819515/
If you did and you still can't get into it, your device is likely dead from the BLOD. But to make sure you have the BLOD, flash the latest factory image first (Dec. 2018) with the latest platform tools to see if it boots... https://developer.android.com/studio/releases/platform-tools
Click to expand...
Click to collapse
firstly i already cant boot into stock recovery from my bootloader i'm on stock os 8.1.
and now i've flashed twrp for angler from twrp website but cant boot into custom recovery too.
now i've flashed twrp image of 4cores but still can't get into recovery.
so what's the problem of this phone if my mobile cant get even into twrp i can't do blod patch if we think my device is suffering from blod issue.
do you think it may be the problem of hardware like ram,emmc, or the SD 810?
Santhosh Jangamgari said:
firstly i already cant boot into stock recovery from my bootloader i'm on stock os 8.1.
and now i've flashed twrp for angler from twrp website but cant boot into custom recovery too.
now i've flashed twrp image of 4cores but still can't get into recovery.
so what's the problem of this phone if my mobile cant get even into twrp i can't do blod patch if we think my device is suffering from blod issue.
do you think it may be the problem of hardware like ram,emmc, or the SD 810?
Click to expand...
Click to collapse
As I said in my previous post, if you can't boot into the 4core custom recovery, your device is likely dead because of the BLOD, unfortunately. If you are on stock with nothing else on your phone that might be preventing you from booting (e.g. mods, Substratum overlays, etc.) there's not much else you can do.
Is your device recognized in fastboot?
marianodelfino said:
Is your device recognized in fastboot?
Click to expand...
Click to collapse
Hi, I am havin same problem as the user above....I am on stock 7.1.2 right now. Unable to boot into TWRP, i flashed twrp-3.2.1-0-fbe-4core-angler.img and then entered recovery from bootloader screen. nothing! i also tried to do a temporary boot to my recovery via fastboot command. didn't work! I dont think my phone is that dead...but I don't see why it isnt booting into twrp...i did the flash all of stock firmware from the Google website. Any assistance? Currently I have a Pixel 2 thats not working, so i thought I would try to revive the 6P, but no luck so far.
DaKoin said:
Hi, I am havin same problem as the user above....I am on stock 7.1.2 right now. Unable to boot into TWRP, i flashed twrp-3.2.1-0-fbe-4core-angler.img and then entered recovery from bootloader screen. nothing! i also tried to do a temporary boot to my recovery via fastboot command. didn't work! I dont think my phone is that dead...but I don't see why it isnt booting into twrp...i did the flash all of stock firmware from the Google website. Any assistance? Currently I have a Pixel 2 thats not working, so i thought I would try to revive the 6P, but no luck so far.
Click to expand...
Click to collapse
thanks but no assistance required as i have sold it to another nexus 6p user for using it's spare parts.
Hi, so I went through the process to flash the boot image to Magisk to root my phone. But now it's stuck on a bootloop and I am able to get it to fastboot and recovery but I don't know how to get the phone to turn normally. I have noticed a few things changed in fastboot, it says "FC 19" under "Device State" and "Variant - SDA UFS" is new as well.
im stuck too. how do you solved that?
Garra1810 said:
im stuck too. how do you solved that?
Click to expand...
Click to collapse
Flash the recovery img via msm tool. If it's the TMobile edition you need to do it while offline and set your date back to Dec.2018. Make sure the date lines up with the date the android version was released.
someone5 said:
Hi, so I went through the process to flash the boot image to Magisk to root my phone. But now it's stuck on a bootloop and I am able to get it to fastboot and recovery but I don't know how to get the phone to turn normally. I have noticed a few things changed in fastboot, it says "FC 19" under "Device State" and "Variant - SDA UFS" is new as well.
Click to expand...
Click to collapse
FC19 was always there, well, not originally, but the first time you did a "fastboot flash" command, FC1 appeared and it incremented for each additional time. Nothing to do with Magisk. In OOS11, this was removed from bootloader.
SDA UFS has ALWAYS been there, absolutely nothing to do with Magisk.
Did you try simply fastboot flashing back to the stock boot image for whatever version of OOS you are running?
someone5 said:
Flash the recovery img via msm tool. If it's the TMobile edition you need to do it while offline and set your date back to Dec.2018. Make sure the date lines up with the date the android version was released.
Click to expand...
Click to collapse
No need to change the dates unless you are using a MSM Tool version for a very old version of OOS10; not quite sure why anyone would do that. Also no need to be offline either if using one of the newer versions (I think they expire 12 months after release)
Also, since this phone was released at end of 2019, you'd want to set the date to Dec 2019, not Dec 2018.
Attached with this post are :
+ Stock boot of OOS12 ( C41) for Oneplus 8T+ 5G (T-Mobile KB2007)
+ Magisk patched boot of OOS12 (C41) for Oneplus 8T+ 5G (T-Mobile KB2007)
+ Modded stock recovery of OOS12 (C41) for Oneplus 8T+ 5G (T-Mobile KB2007) with ADB enabled, security disabled, ability to debug enabled and allow mock location by default.
Just flash in Fastboot mode as usual!
Hi! I'm not very up-to-speed. I just restored my phone to TMO android 11, I was running PixelExperience and I have run the EU rom, what post should I look to for "flash...as usual". I'm not sure what the normal process is. Thanks!
bookofjoshua said:
Hi! I'm not very up-to-speed. I just restored my phone to TMO android 11, I was running PixelExperience and I have run the EU rom, what post should I look to for "flash...as usual". I'm not sure what the normal process is. Thanks!
Click to expand...
Click to collapse
I don't really understand your question but these files are for OnePlus 8T+ 5G Stock OOS12 C41 only, so if u r on A11, then these files are no use for u bro.
LinhBT said:
I don't really understand your question but these files are for OnePlus 8T+ 5G Stock OOS12 C41 only, so if u r on A11, then these files are no use for u bro.
Click to expand...
Click to collapse
It says "just flash in fastboot as usual". I don't know what "as usual" means. I wasn't looking for info on using them with my phone, just what I need to look at for the flashing procedures as I have seen several different methods and requirements,.
bookofjoshua said:
It says "just flash in fastboot as usual". I don't know what "as usual" means. I wasn't looking for info on using them with my phone, just what I need to look at for the flashing procedures as I have seen several different methods and requirements,.
Click to expand...
Click to collapse
Ah, what I mean by "flash in fastboot as usual" is : just flash those files in fastboot mode with fastboot commands which is used to flash boot.img recovery.img.....etc. In this case, are "
+ fastboot flash recovery recovery.img
+ fastboot flash boot boot.img
or you may input option like :
+ fastboot --slot-all flash boot boot.img ( to flash boot.img into both boot slot A/B )
Just that, my friend!
LinhBT said:
Ah, what I mean by "flash in fastboot as usual" is : just flash those files in fastboot mode with fastboot commands which is used to flash boot.img recovery.img.....etc. In this case, are "
+ fastboot flash recovery recovery.img
+ fastboot flash boot boot.img
or you may input option like :
+ fastboot --slot-all flash boot boot.img ( to flash boot.img into both boot slot A/B )
Just that, my friend!
Click to expand...
Click to collapse
So by using those fastboot commands you'll be able to root the KB2007 if you are running 12 as long as your bootloader is unlocked as well as SIM unlocked? That's my current situation right now and was looking go root sometime soon
kevinco1 said:
So by using those fastboot commands you'll be able to root the KB2007 if you are running 12 as long as your bootloader is unlocked as well as SIM unlocked? That's my current situation right now and was looking go root sometime soon
Click to expand...
Click to collapse
True, if you are on OOS12 C41 ( TMO ) to be specific, then u can use the magisk patched boot image from my post to root your device using normal fastboot commands as mentioned!
LinhBT said:
Ah, what I mean by "flash in fastboot as usual" is : just flash those files in fastboot mode with fastboot commands which is used to flash boot.img recovery.img.....etc. In this case, are "
+ fastboot flash recovery recovery.img
+ fastboot flash boot boot.img
or you may input option like :
+ fastboot --slot-all flash boot boot.img ( to flash boot.img into both boot slot A/B )
Just that, my friend!
Click to expand...
Click to collapse
Thank you! I appreciate you taking the time to clear that up for me, and actually type the commands. I was originally flashing Roms to get access to my 5G radio, as I'm using it on Verizon towers, but after applying the latest update my phone connected to 5G so I may not even need it anymore
bookofjoshua said:
Thank you! I appreciate you taking the time to clear that up for me, and actually type the commands. I was originally flashing Roms to get access to my 5G radio, as I'm using it on Verizon towers, but after applying the latest update my phone connected to 5G so I may not even need it anymore
Click to expand...
Click to collapse
There's a guide to enable 5G and/or VoLTE for KB2007 also in our forum. But since u did it, congrats
I just got this device yesterday. Already sim unlocked and requested the bootloader unlock code. Since it's only day one, I haven't flashed the euro firmware/rom yet. Is it worth upgrading it to 12 and then simply rooting it. I don't mind running stock for a while, but I hear 12 is really that bad. Obviously it can't be too bad if you are using it. I am just hesitant on installing the update. What are your thoughts?
works beautifully
heyChristo said:
I just got this device yesterday. Already sim unlocked and requested the bootloader unlock code. Since it's only day one, I haven't flashed the euro firmware/rom yet. Is it worth upgrading it to 12 and then simply rooting it. I don't mind running stock for a while, but I hear 12 is really that bad. Obviously it can't be too bad if you are using it. I am just hesitant on installing the update. What are your thoughts?
Click to expand...
Click to collapse
not bad so far just more security . disabled pinch out hidden menu.. had to create code and use dialer to access hidden menu. i fastbooted this and now rooted have not tried recovery yet im afraid actually
So I converted mine to the EU version and then to the global version and updated to 12 via OTA. However I could not find the file prior to flashing so I couldn't pull it to the PC. Obviously I lose root on that full update. Can I flash this boot image to restore root or will that brick the device?
For those that want the latest C42 update with September security, find attached the stock boot image as well as the magisk patched image
Hey. Thanks for all your work. I'm rooted on stock kb2007. My OTA update to 41 is not working. Would flashing these before asking the system to update fix it, or are these for after you unroot and allow the update. I think the unroot is where I'm having trouble. I uninstalled Magsik and wiped cache for google play. The OTA still won't work. I'm sure there is every note on XDA about this, but I thought I'd ask here because I think I'm so close.
droidgreg said:
For those that want the latest C42 update with September security, find attached the stock boot image as well as the magisk patched image
Click to expand...
Click to collapse
you wouldnt have the last android modem img for android? thx in advance. i forgot to safe modem via msm tool before i converted to global smh
The real question is where can obtain the original firmware for C42? Haven't been able to find it anywhere online
kevinco1 said:
The real question is where can obtain the original firmware for C42? Haven't been able to find it anywhere online
Click to expand...
Click to collapse
There is no 100% confirmation that C42 was released as a full update and not incremental on C41.
If I'm already on Android 12, C41 unrooted than I don't need to do any other flashing except the magisk patched boot image from the post to root my device using normal fastboot?
What is the purpose of the modded stock recovery?
MustangLife03 said:
What is the purpose of the modded stock recovery?
Click to expand...
Click to collapse
The main reason is enabled adb access.
Having ADB enabled on the stock recovery can be really helpful if you are unlocked and rooted.
For example, removing problematic magisk modules.
Though there is unofficial TWRP for A12 which makes stock adb enabled a bit obsolete in this case.
But anyway thanks for LinhBT for compiling it.