unable to stay in bootloader after kdz to h81120p - T-Mobile LG G4

So I justI fixed my phone by flashing KDZ h81120p to it. But now I lost my root/TWRP. When I try ADB and sent the command "adb reboot boatloader" the phone just reboots and doesn't stay in the bootloader. So I can't send the command to flash TWRP image.
It does still show "bootloader unlocked" at startup.
Just want to flash TWRP so I can root.
any ideas? thanks

Problematic.
As far as I know, there are just a few ways to get into bootloader:
1/adb reboot bootloader
2/"quick boot" app with root, or advanced power menu from certain ROMs
3/power off, and then key combination boot( NEVER worked for me )

also me, flash h81120p kdz, everything work fine except root lost & boot into recovery but its showing android icon with explanation mark.
please help

Same here.

Related

Bootloader won't start

After a long search, I couldn't find anything related to this issue, that's why I've posted this here.
So I tried to root an LG 4X HD, I rooted it immediately without unlocking BL, now everytime I boot into bootloader, I get this:
[LGE_SECURITY] ERROR: boot image signature
Critical failure: unable to start kernel
Unrecoverable bootloader error (0x0000002)
Android (ICS) boots just fine, has root access... but can't access recovery
I know I did something wrong here, little help?
Sent from my LG G2 using Tapatalk... Awesome
Unlock the boot loader
don't forget to hit thanks!
abhi08638 said:
Unlock the boot loader
don't forget to hit thanks!
Click to expand...
Click to collapse
Tried that, won't get into OEM BL unlock mode... it's just odd.
Sent from my LG G2 using Tapatalk... Awesome
hanisod said:
Tried that, won't get into OEM BL unlock mode... it's just odd.
Sent from my LG G2 using Tapatalk... Awesome
Click to expand...
Click to collapse
On ICS you can't unlock bootloader, try upgrading to JB.
Press thanks if it helps
hanisod said:
After a long search, I couldn't find anything related to this issue, that's why I've posted this here.
So I tried to root an LG 4X HD, I rooted it immediately without unlocking BL, now everytime I boot into bootloader, I get this:
[LGE_SECURITY] ERROR: boot image signature
Critical failure: unable to start kernel
Unrecoverable bootloader error (0x0000002)
Android (ICS) boots just fine, has root access... but can't access recovery
I know I did something wrong here, little help?
Sent from my LG G2 using Tapatalk... Awesome
Click to expand...
Click to collapse
My problem is same as yours or nearly the same.
I unlocked bootloader on V20a with "adb reboot oem-unlock" and installed CWM + CM11. Everything was working fine, but GPS. From time to time loses signal, takes more minutes to get lock, etc...
I read somewhere on this forum that there is a problem with the V20x basebands and the solution is to roll back to V10x. So I flashed back to V10H with .dz file. When I type "adb reboot bootloader", "adb reboot-bootloader" or "adb reboot oem-unlock" the phone just restarts. (At this point I can boot into LG's recovery.) Rooted the system and flashed CWM recovery from shell. When I want to boot in to new recovery then appears this message. (I can boot into system.)
Again if I flash back the V20a, I can boot into bootloader and can install custom recovery (without re-unlocking).
I would like to know, how could I manage to work V10x+CWM+CM11 together
jeBACH said:
My problem is same as yours or nearly the same.
I unlocked bootloader on V20a with "adb reboot oem-unlock" and installed CWM + CM11. Everything was working fine, but GPS. From time to time loses signal, takes more minutes to get lock, etc...
I read somewhere on this forum that there is a problem with the V20x basebands and the solution is to roll back to V10x. So I flashed back to V10H with .dz file. When I type "adb reboot bootloader", "adb reboot-bootloader" or "adb reboot oem-unlock" the phone just restarts. (At this point I can boot into LG's recovery.) Rooted the system and flashed CWM recovery from shell. When I want to boot in to new recovery then appears this message. (I can boot into system.)
Again if I flash back the V20a, I can boot into bootloader and can install custom recovery (without re-unlocking).
I would like to know, how could I manage to work V10x+CWM+CM11 together
Click to expand...
Click to collapse
you need to mod 20x kdz with 10x baseband, and flash that. there's a tutorial somewhere around the forum, search and you'll find it.
The tutorial that Flying_Bear is talking about is:
[BASEBANDS][TUTORIAL] Freedom! Choose your baseband.

[Q] Verizon Developers Edition help

Hoping somebody can help me figure out what is going on with my phone. Sorry for the long post, but hoping folks with custom rom and flashing experience will read on to help.
I have the Verizon Developer Edition. I have unlocked the bootloader, installed TWRP 2.7, and rooted the phone. I have never installed any custom ROMs on the phone. I had done custom ROMs on my GS3, but I just wanted this phone rooted, and maybe mess around with a few ROMs down the road.
I followed this video from RootJunky when I originally installed TWRP.
So a few weeks ago I kept getting the OTA message to upgrade to the latest kitkat. I decided to flash back to the original recovery so I could do the upgrade. I contacted RootJunky on his youtube channel and he provided a link to the stock recovery and I flashed it using the same video and his linked file.
After flashing the stock recovery, when I was in bootloader mode, I scrolled down to "recovery" and selected it. It would not go into recovery. It just stays in a bootloop. I went back and forth with RootJunky a few times trying to resolve this, but I got no response to my last few comments.
I can get the phone back into bootloader mode by holding the volume up/dwn and power buttons, if I time it correctly during the bootloop. When in bootloader mode, I can select "Normal Powerup" option and the phone will boot up and function properly. But, if I shut the phone down, I can't turn the device on with the power button, otherwise it will just bootloop. I have to get into bootloader mode, then select "Normal Powerup" to get the phone to work.
Once back in the phone, my USB debugging option is unchecked. I can recheck it, open a command prompt, and do a "adb devices" and it shows it connected. But if I do a "adb reboot bootloader" from the command prompt it will bootloop.
When I get into bootloader mode manually, when I connect it to the computer, and do a "adb devices", it doesn't show as connected, as I think the USB debugging option is getting toggled off somehow, so I can't connect or flash anything to the phone at this point.
One thing I see, in the video @ 4:50, he says you need to be at "status code 1" to flash recoveries. I am/was at status code 3. Not sure if that is why I am having this issue, or how to get this changed.
Any help would be greatly appreciated. I can use the phone just fine, but at this point, I would just like to be able to do a full restore to stock, upgrade to 4.4.4, keep the unlocked bootloader, and root the phone. No custom ROM.
THANKS!
08G8V8 said:
Hoping somebody can help me figure out what is going on with my phone. Sorry for the long post, but hoping folks with custom rom and flashing experience will read on to help.
I have the Verizon Developer Edition. I have unlocked the bootloader, installed TWRP 2.7, and rooted the phone. I have never installed any custom ROMs on the phone. I had done custom ROMs on my GS3, but I just wanted this phone rooted, and maybe mess around with a few ROMs down the road.
I followed this video from RootJunky when I originally installed TWRP.
So a few weeks ago I kept getting the OTA message to upgrade to the latest kitkat. I decided to flash back to the original recovery so I could do the upgrade. I contacted RootJunky on his youtube channel and he provided a link to the stock recovery and I flashed it using the same video and his linked file.
After flashing the stock recovery, when I was in bootloader mode, I scrolled down to "recovery" and selected it. It would not go into recovery. It just stays in a bootloop. I went back and forth with RootJunky a few times trying to resolve this, but I got no response to my last few comments.
I can get the phone back into bootloader mode by holding the volume up/dwn and power buttons, if I time it correctly during the bootloop. When in bootloader mode, I can select "Normal Powerup" option and the phone will boot up and function properly. But, if I shut the phone down, I can't turn the device on with the power button, otherwise it will just bootloop. I have to get into bootloader mode, then select "Normal Powerup" to get the phone to work.
Once back in the phone, my USB debugging option is unchecked. I can recheck it, open a command prompt, and do a "adb devices" and it shows it connected. But if I do a "adb reboot bootloader" from the command prompt it will bootloop.
When I get into bootloader mode manually, when I connect it to the computer, and do a "adb devices", it doesn't show as connected, as I think the USB debugging option is getting toggled off somehow, so I can't connect or flash anything to the phone at this point.
One thing I see, in the video @ 4:50, he says you need to be at "status code 1" to flash recoveries. I am/was at status code 3. Not sure if that is why I am having this issue, or how to get this changed.
Any help would be greatly appreciated. I can use the phone just fine, but at this point, I would just like to be able to do a full restore to stock, upgrade to 4.4.4, keep the unlocked bootloader, and root the phone. No custom ROM.
THANKS!
Click to expand...
Click to collapse
First, Status code 3 is normal - that indicates an unlocked bootloader.
You should be able to use the 4.4.4 FXZ to flash back to 100% stock. Afterwards, you can flash TWRP, and re-root. Use the latest TWRP from here: http://techerrata.com/browse/twrp2/ghost
The important thing about TWRP is that immediately after flashing it, you have to "fastboot reboot-bootloader" and immediately boot into recovery - otherwise it doesn't 'stick'. We don't know why, but as long as you do it that way, you will be fine.
Here is the link for the 4.4.4 FXZ: http://forum.xda-developers.com/moto-x/general/fxz-moto-x-4-4-4-212-55-26-t2827307
If you follow the instructions, you will be on stock, rooted 4.4.4 in less than 20 minutes.
Good Luck, and let me know if you need additional assistance :good:
Also, please remember to post your questions to Q&A - not General. Don't worry as I have already requested that the Mods move it to the appropriate sub-forum.
EDIT: The problem I see with "rootjunky"s video is that first, he advises that "Status code 1" is required to flash recovery -- this is incorrect. Status code 3 works fine for custom recovery.
Additionally, he did not "fastboot reboot-bootloader" before booting into recovery. This is necessary. I'm not sure why he left that step out....likely he already had custom recovery flashed when he made the video.
Thanks for the quick response. Sorry about posting in the wrong section. I should have known better.....
I will look at this, but probably won't do it until after work tomorrow. I will post back tomorrow, hopefully with success.
Thanks!
I saw your edit to your post. I did the reboot boot loader step when I originally flashed twrp. I can't remember where I saw it, but I remember reading it and doing it.
The phone was running fine with twrp installed for a few months. The problem I am having now happened after flashing the stock recovery back onto the phone.
Do you recommend the RSD Flasher or House of Moto method to flash this FXZ?
08G8V8 said:
I saw your edit to your post. I did the reboot boot loader step when I originally flashed twrp. I can't remember where I saw it, but I remember reading it and doing it.
The phone was running fine with twrp installed for a few months. The problem I am having now happened after flashing the stock recovery back onto the phone.
Do you recommend the RSD Flasher or House of Moto method to flash this FXZ?
Click to expand...
Click to collapse
Either will work fine. If you don't care about keeping your data, you can use RSD Lite (will wipe everything). If you use one of the tools in the thread I linked you to, make absolutely sure you follow the instructions -- you can't have any spaces in any folder-names. If you use RSD Lite, you just select the zip file and flash (no worries about directory structure).
Ok, I just assumed those were the methods to flash it. I will look into the RSD Lite method, as if don't mind wiping the data.
I just watched a quick video on YouTube about using RSD Lite, and they state you must reboot the boot loader and do the flash in fastboot. I can't reboot into the bootloader from the command prompt, as it goes into the boot loop. I can get into fastboot manually, but when connecting to the computer it doesn't recognize it since the USB debugging option keeps getting reset on me.
Am I missing something? I don't see how I can flash this.
08G8V8 said:
I just watched a quick video on YouTube about using RSD Lite, and they state you must reboot the boot loader and do the flash in fastboot. I can't reboot into the bootloader from the command prompt, as it goes into the boot loop. I can get into fastboot manually, but when connecting to the computer it doesn't recognize it since the USB debugging option keeps getting reset on me.
Am I missing something? I don't see how I can flash this.
Click to expand...
Click to collapse
So you are telling me that when you type "adb reboot bootloader" (if usb debugging is enabled) or "fastboot reboot-bootloader" (if usb debugging is not enabled) it doesn't take you to the "AP Fastboot Mode" screen?
samwathegreat said:
So you are telling me that when you type "adb reboot bootloader" (if usb debugging is enabled) or "fastboot reboot-bootloader" (if usb debugging is not enabled) it doesn't take you to the "AP Fastboot Mode" screen?
Click to expand...
Click to collapse
Sorry, the "adb reboot bootloader" sends me into the bootloop.
I hadn't tried the "fastboot reboot bootloader" or "fastboot reboot-bootloader". Now when I try that, with USB debugging checked I just get "<waiting for device>" It does nothing.
What about turning off the device. Then holding power button and volume down at the same time. Does it take you to the bootloader screen like it should?
It sounds to me like when you were attempting you flash your stock recovery back, you flashed it to the wrong partition. I've seen another member do this....
He accidentally typed "fastboot flash bootloader stockrecoveryfile.img"
That would cause the issues you are describing... I might have a way to fix it if you are currently still rooted and able to access adb...
Travisdroidx2 said:
What about turning off the device. Then holding power button and volume down at the same time. Does it take you to the bootloader screen like it should?
Click to expand...
Click to collapse
Yes, I can manually get into bootloader, but it keeps toggling my USB debugging option, so when I connect it to the computer, it doesn't see it.
08G8V8 said:
Yes, I can manually get into bootloader, but it keeps toggling my USB debugging option, so when I connect it to the computer, it doesn't see it.
Click to expand...
Click to collapse
USB debugging isn't used in the bootloader, and adb isn't used for fastboot mode... I'm very confused by what you are saying...
Once you are in the boot loader screen does "fastboot devices" recognize your device?
samwathegreat said:
It sounds to me like when you were attempting you flash your stock recovery back, you flashed it to the wrong partition. I've seen another member do this....
He accidentally typed "fastboot flash bootloader stockrecoveryfile.img"
That would cause the issues you are describing... I might have a way to fix it if you are currently still rooted and able to access adb...
Click to expand...
Click to collapse
No, I typed "fastboot flash recovery stockrecoveryfile.img"
I did just like originally when flashing TWRP, just replaced the file in the command line.
I am still rooted.
samwathegreat said:
USB debugging isn't used in the bootloader, and adb isn't used for fastboot mode... I'm very confused by what you are saying...
Click to expand...
Click to collapse
I can get into fastboot with the phone powered off, holding the volume UP/DWN and PWR. But when connected to the computer it isn't recognized.
Sorry, but I am confused as well. I am just going off what I have seen in RootJunky's videos. In this video, https://www.youtube.com/watch?v=1LkuLb8hV6Q#t=285 at 4:44, after he does the "adb reboot bootloader" he says the device is now in "bootloader mode" which is what I am talking about, but I guess is actually Fastboot Mode. This is the same mode I am talking about getting into from the device powered off holding the volume UP/DWN and PWR buttons, but going in this way doesn't get recognized by the computer.
Travisdroidx2 said:
Once you are in the boot loader screen does "fastboot devices" recognize your device?
Click to expand...
Click to collapse
YES it does! Thanks. I kept trying "adb devices", and when it wasn't recognizing it, I figured it wasn't connected. I wasn't doing "fastboot devices". But, my USB debugging still was getting unchecked after getting back into the phone.
So with it recognizing my device in fastboot mode I should be able to go ahead with the RSD Lite flashing?
08G8V8 said:
No, I typed "fastboot flash recovery stockrecoveryfile.img"
I did just like originally when flashing TWRP, just replaced the file in the command line.
I am still rooted.
I can get into fastboot with the phone powered off, holding the volume UP/DWN and PWR. But when connected to the computer it isn't recognized.
Sorry, but I am confused as well. I am just going off what I have seen in RootJunky's videos. In this video, https://www.youtube.com/watch?v=1LkuLb8hV6Q#t=285 at 4:44, after he does the "adb reboot bootloader" he says the device is now in "bootloader mode" which is what I am talking about, but I guess is actually Fastboot Mode. This is the same mode I am talking about getting into from the device powered off holding the volume UP/DWN and PWR buttons, but going in this way doesn't get recognized by the computer.
Click to expand...
Click to collapse
OK, glad you didn't flash to bootloader. That is tricky to fix...but I've dealt with people who have done it before.
Try another PC...or re-install the drivers. Also, DO NOT use a usb 3.0 port, always use 2.0.
Bootloader = AP fastboot mode. They are one and the same. Try to get it recognized with "fastboot devices", on any PC. If you can get to that point, you can flash back to stock and recover everything. The FXZ can actually FIX a corrupted or damaged filesystem. It replaces all the relevant partitions.
Remember you do NOT use adb or usb debugging. They have nothing to do with fastboot.
---------- Post added at 09:10 PM ---------- Previous post was at 09:09 PM ----------
08G8V8 said:
YES it does! Thanks. I kept trying "adb devices", and when it wasn't recognizing it, I figured it wasn't connected. I wasn't doing "fastboot devices". But, my USB debugging still was getting unchecked after getting back into the phone.
So with it recognizing my device in fastboot mode I should be able to go ahead with the RSD Lite flashing?
Click to expand...
Click to collapse
YES!!!!
It seems you were confusing adb and fastboot. As long as "fastboot devices" recognizes your device, SO WILL RSD LITE!!!
Now follow my initial instrucitons, and you will be up and running in no time...
Thanks guys! I am going to do this tomorrow, but I feel pretty good that it is going to work.
Yes, I got VERY confused, and definitely need to go study up some more. I thought I had it, but obviously not.
Will report back tomorrow.
Happy to help
Absolutely get the Dev Edition for the same price. While Safestrap is out for other Galaxy devices with locked bootloaders (not sure if the S5 got SS yet) it allows customs Roms....but not kernel changes. With a Dev edition, there may be less development, but I'm sure there will still be some development out there.

Cannot install TWRP recovery

Which is weird as it worked before.
Basic stuff. Android 6.0.1, MIUI 8.1
Bootloader unlocked
USB ADB drivers installed
Debugging on
Run TWRP and device is recognised, TWRP isntalled successfully but when I reboot phone into recovery, I get the standard "phone connected to usb cable" graphic. Im at a loss to know it wont go into TWRP, suggestions please?
Need to root to adjust in cqll volume settings, thx.
2bullish said:
Which is weird as it worked before.
Basic stuff. Android 6.0.1, MIUI 8.1
Bootloader unlocked
USB ADB drivers installed
Debugging on
Run TWRP and device is recognised, TWRP isntalled successfully but when I reboot phone into recovery, I get the standard "phone connected to usb cable" graphic. Im at a loss to know it wont go into TWRP, suggestions please?
Need to root to adjust in cqll volume settings, thx.
Click to expand...
Click to collapse
Not sure about alle the steps you did or did not do.
But if you install TWRP and then reboot back to MIUI, it will overwrite the recovery again.
From the TWRP.me site:
fastboot flash recovery twrp.img
fastboot reboot
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
Ok, followed all the steps exactly, the phone boots into twrp, then i reboot in system, or let it reboot by disconnecting, same thing happens. Black screen MI logo, bootloader unlock, in red, at the bottom of the screen with an open padlock.
Now it wont boot at all.
This is weird, I can boot into fastboot and recovery but when i try to flash, the device is redognised but i cannot see it in the drop down menu to find the rom. Grrrrrr im stuck.
2bullish said:
This is weird, I can boot into fastboot and recovery but when i try to flash, the device is redognised but i cannot see it in the drop down menu to find the rom. Grrrrrr im stuck.
Click to expand...
Click to collapse
OK, if you want to keep MIUI, just flash MIUI again and it should install the needed firmware, recovery etc.
You can use the recovery zip for this or the fastboot gz version to install (both should work).
If you want a custom rom installed, go to the Lineage thread (i use that since feb, with weekly updates) or another one.
Read the first few post carefully, but if you want to install it (Lineage), do flash the firmware first via recovery before flashing the rom (don't forget this one).
Update. I can get into TWRP recovery but have no back up.
If I try to boot into system I get a black screen with Mi logo and a red unlocked boot loader padlock graphic.
If i boot into fast boot and run miflash, the phone is recognised but the sd storage does not appear in the drop down at all.
I cannot use the pcsuite software and if the phone is not in TWRP or fastboot mode it is on the black screen with logo with red unlocked padlock and is not recognised by the PC. I dont know what else to do, any help will be greatly appreciated.
Found out the problem it was supersu, gonna try a different version
2bullish said:
Found out the problem it was supersu, gonna try a different version
Click to expand...
Click to collapse
Glad you found the problem.
I think that MIUI has already build in the SU via the Developer options, but i'm not sure of that.
If you think of Lineage, just flash the Lineage Su addon after the Lineage rom.
Works great.
2bullish said:
Update. I can get into TWRP recovery but have no back up.
If I try to boot into system I get a black screen with Mi logo and a red unlocked boot loader padlock graphic.
If i boot into fast boot and run miflash, the phone is recognised but the sd storage does not appear in the drop down at all.
I cannot use the pcsuite software and if the phone is not in TWRP or fastboot mode it is on the black screen with logo with red unlocked padlock and is not recognised by the PC. I dont know what else to do, any help will be greatly appreciated.
Click to expand...
Click to collapse
MIUI has some sort of verification on boot. If it detects a custom recovery different from stock one, it won't boot. You need to use zcx twrp. It can bypass this verification.

[FIXED] Fastboot? Recovery bootlooping, but never getting there

Hi All, I need fastboot!
Perhaps someone can help with my brick? I've unlocked the bootloader, installed TWRP and had lineageOS 18.1 installed once. The screen was dim so I tried to flash DotOS. And got a "failed to mount /tmp/com.android.resolv.apex to loop device /dev/block/loop16" error so I tried to reinstall stock 57 ROM.
I did "fastboot flash recovery boot.img" with the decrypted boot.img hoping to get colourOS recovery.
The phone is now bootlooping trying to get into recovery mode. It won't power off or respond to button presses except vol up + vol down seems to delay the reboot on a blank screen.
I was hoping to get to fastboot mode to flash TWRP. Can anyone help? Should I surrender and accept the bricking?
you can get back to stock by install the stock rom, vendor, and kernel with adb drivers and commands.
or
if your mobile is MIUI you can just use the software to revert back to stock rom remember it re-locks the bootloader and again you need to unlock
The phone is currently boot looping.
I can't even turn it off.
It displays RealME/Android logo, then small "> RECOVERY MODE" text at bottom, then "Orange State" text. Repeat..
It has no response to a usb cable - no usb messages in dmesg. So it is not detected by adb or fastboot.
When the battery finally goes flat, my only hope is that I can get fastboot to flash TWRP into the recovery partition. I am not confident of this :-(
frolyx said:
The phone is currently boot looping.
I can't even turn it off.
It displays RealME/Android logo, then small "> RECOVERY MODE" text at bottom, then "Orange State" text. Repeat..
It has no response to a usb cable - no usb messages in dmesg. So it is not detected by adb or fastboot.
When the battery finally goes flat, my only hope is that I can get fastboot to flash TWRP into the recovery partition. I am not confident of this :-(
Click to expand...
Click to collapse
did you ever get this solved and fixed? i have accidently done the same thing.
hey guys follow this youtube
managed to unbrick my phone
smiley.raver said:
did you ever get this solved and fixed? i have accidently done the same thing.
Click to expand...
Click to collapse
Not yet, but I will try the youtube method above..
This recovered the Phone!
But, win10 reported the MCT extractor contained a worm (the python script under linux didn't work). I'm not sure I can trust this phone 100% from now on LOL!
the bypass just deactivates mtk hardware verificaton as normally they have a special dongle they use with the software download
I havent had any issues
I will upload thw bypass i use which doesnt havw any virus

Question Phone stuck in boot loop, unable to get to FastBoot

Hi,
Sequence of steps:
1. Extracted the boot.img from payload.bin and flashed it to the phone. At this point I was able to get into Fastboot
2. While in Fastboot I went into advanced and wiped the "System Settings", and that's when the trouble started - now the phone is stuck into a boot loop forever, I do however get the options to "Power Off" and "Restart"
3. But none of the options above in Step 2 is able to bring me back to Fastboot (and hence into fastbootd either)
Question: How can I get the phone into Fastboot Mode - have tried MSM Tool v4 as well, but that doesn't even recognize the phone
Edit - This seems to have been resolved now, think I had to press Vol Down + Power instead of Vol Up + Power
Was able to enter into Fastbootd as well, will try to proceed with unbricking the phone with a fresh mind tomorrow
FYI for others reading I was able to install magisk by booting the patched file (dump the payload using the python script mentioned above). Running the command Fastboot boot filename boots into the operating system and then magisk can be installed using the direct method.
I assume running this command the phone doesn't actually flash the boot image but could be wrong
VoltaGe86 said:
FYI for others reading I was able to install magisk by booting the patched file (dump the payload using the python script mentioned above). Running the command Fastboot boot filename boots into the operating system and then magisk can be installed using the direct method.
I assume running this command the phone doesn't actually flash the boot image but could be wrong
Click to expand...
Click to collapse
Thats right, "fastboot boot <file_name>" loads temporarily your custom recovery of choice. After rebooting your phone, the custome recovery is gone.
Otherwise, the command "fastboot flash <file_name> recovery" flashs permamently your custom recovery of choice to your device.
Hi I have a oneplus 8t and I tried flashing a payload.bin file using fastboot enhanced. after the operation completed I tried to reboot but the phone only shows the logo and then the bootloader unlocked warning message and then turns off briefly, then it does it again and the screen goes black. When connected to the PC, the PC recognizes the devices as android adb recovery devices but i can't do anything from there. Tried the volume up+power combo and it just does the same thing. tried the volume down+power combo and absolutely nothing happens. If i could at least get to the bootloader I could unbrick it but I just can't get there. Any advice
Zekedw said:
Hi I have a oneplus 8t and I tried flashing a payload.bin file using fastboot enhanced. after the operation completed I tried to reboot but the phone only shows the logo and then the bootloader unlocked warning message and then turns off briefly, then it does it again and the screen goes black. When connected to the PC, the PC recognizes the devices as android adb recovery devices but i can't do anything from there. Tried the volume up+power combo and it just does the same thing. tried the volume down+power combo and absolutely nothing happens. If i could at least get to the bootloader I could unbrick it but I just can't get there. Any advice
Click to expand...
Click to collapse
I have exactly the same issue, on a nord 2
How about vol+/vol-&power all together? When stuck that gives me some screen that allows start, recovery (the one where you can enter advanced settings I expect from your description) and bootloader booting.

Categories

Resources