Database Users

Bricked VS995 after Dirty Santa attempt - could use some help! :(

So my VS995 (Verizon LG V20) is stuck in a fastboot loop. I can't do anything outside of fastboot. I got to after step 3 in the Dirty Santa root method and could not get the phone to boot into TWRP recovery. I kept getting an ADB device offline error and could not get ADB to see my device to initiate the "ADB reboot recovery command".
In a stupid and drunk state I did a "fastboot erase system" and thats what locked me into the fastboot loop.
Any help is appreciated as my V20 is now unusable :crying:.
I guess I would need a stock boot image, and stock recovery to get back to where I started. If anyone could point me in the right direction and help me get my phone back (and possibly rooted), I would be more than happy to donate via PayPal .
P.S. The LGUP software used in the how to restore v20 thread linked-> ( https://forum.xda-developers.com/v20/how-to/restore-v20-to-100-stock-bricked-devices-t3524903) does not recognize the model of device giving the error ("you have to select a known model, please")

Kevin_xail said:
So my VS995 (Verizon LG V20) is stuck in a fastboot loop. I can't do anything outside of fastboot. I got to after step 3 in the Dirty Santa root method and could not get the phone to boot into TWRP recovery. I kept getting an ADB device offline error and could not get ADB to see my device to initiate the "ADB reboot recovery command".
In a stupid and drunk state I did a "fastboot erase system" and thats what locked me into the fastboot loop.
Any help is appreciated as my V20 is now unusable :crying:.
I guess I would need a stock boot image, and stock recovery to get back to where I started. If anyone could point me in the right direction and help me get my phone back (and possibly rooted), I would be more than happy to donate via PayPal .
P.S. The LGUP software used in the how to restore v20 thread linked-> ( https://forum.xda-developers.com/v20/how-to/restore-v20-to-100-stock-bricked-devices-t3524903) does not recognize the model of device giving the error ("you have to select a known model, please")
Click to expand...
Click to collapse
Use this thread https://forum.xda-developers.com/v20/development/vs995-kdz-t3527538
If you have verizon VS995
Follow the procedure in the thread https://forum.xda-developers.com/v20/how-to/restore-v20-to-100-stock-bricked-devices-t3524903
download these
VS99512A_06_1114_ARB00.kdz
lg-firmwares.com/download-file/?fileId=4889
https://forum.xda-developers.com/lg-g5/development/uppercut-lgup-loader-g5-variants-t3511295
LGUP_Store_Frame_Ver_1_14_3_3.msi http://downloads.codefi.re/autoprime/LG/LG_G5/LGUP
LGMobileDriver_WHQL_Ver_4.1.1.exe http://downloads.codefi.re/autoprime/LG/LG_G5/LGMobileDriver_WHQL_Ver_4.1.1.exe

I was able to flash the appropriate stock .kdz file (THANKS dwertz!) but my phone immediately boots right back into FastBoot Mode
Do I need a stock Boot.img file?
I can communicated with the device through the PC's terminal using fastboot. Are there any fastboot commands I could try to boot into the stock firmware I just flashed? Are there any partitions I need to erase or format?
Any help is appreciated!

Kevin_xail said:
I was able to flash the appropriate stock .kdz file (THANKS dwertz!) but my phone immediately boots right back into FastBoot Mode
Do I need a stock Boot.img file?
I can communicated with the device through the PC's terminal using fastboot. Are there any fastboot commands I could try to boot into the stock firmware I just flashed? Are there any partitions I need to erase or format?
Any help is appreciated!
Click to expand...
Click to collapse
to my understanding, the kdz file contains the stock boot.img and stock system.img, everything to bring the device completely back to stock .
In fastboot to boot to the system the command is "fastboot reboot"

dwertz said:
to my understanding, the kdz file contains the stock boot.img and stock system.img, everything to bring the device completely back to stock .
In fastboot to boot to the system the command is "fastboot reboot"
Click to expand...
Click to collapse
After flashing the stock .kdz firmware for the VS995 fastboot is no longer working and giving me the error FAILED (remote: unknown command).
My phone can not get past FastBoot! :crying: I think I really bricked this thing now. My bootloader is locked, fastboot commands don't work at all.
The only thing that does work is download mode (holding volume up and plugging phone in) and I am able to flash the vs995 firmware from the lg website but i STILL can't boot into anything but fastboot.
Does anyone have any suggestions as to what I can try to fix this thing. I think i'm doomed. I may try to flash the stock us996 firmware because at this point it seems like it wont get any worse.
Any help would be appreciated!

Kevin_xail said:
After flashing the stock .kdz firmware for the VS995 fastboot is no longer working and giving me the error FAILED (remote: unknown command).
My phone can not get past FastBoot! :crying: I think I really bricked this thing now. My bootloader is locked, fastboot commands don't work at all.
The only thing that does work is download mode (holding volume up and plugging phone in) and I am able to flash the vs995 firmware from the lg website but i STILL can't boot into anything but fastboot.
Does anyone have any suggestions as to what I can try to fix this thing. I think i'm doomed. I may try to flash the stock us996 firmware because at this point it seems like it wont get any worse.
Any help would be appreciated!
Click to expand...
Click to collapse
did you ever get any help? I would go directly to the dirty santa thread and make your issue known. I'm not sure how much help I could give you but if no one else is willing to help I can try.

Kevin_xail said:
After flashing the stock .kdz firmware for the VS995 fastboot is no longer working and giving me the error FAILED (remote: unknown command).
My phone can not get past FastBoot! :crying: I think I really bricked this thing now. My bootloader is locked, fastboot commands don't work at all.
The only thing that does work is download mode (holding volume up and plugging phone in) and I am able to flash the vs995 firmware from the lg website but i STILL can't boot into anything but fastboot.
Does anyone have any suggestions as to what I can try to fix this thing. I think i'm doomed. I may try to flash the stock us996 firmware because at this point it seems like it wont get any worse.
Any help would be appreciated!
Click to expand...
Click to collapse
Did you flash the kdz using Uppercut?

imucarmen - I can't post in the dirty santa thread because I am a new member to XDA (been coming here for years just never made an account )
bond32 - Yes I was able to flash the .kdz using Uppercut+LGUP but my problem is not fixed. My phone still boots right to FastBoot Mode in the "Locked State" to where I can't issue any commands or alter any partitions.
This makes no sense to me if LGUP is able to 100% flash the stock firmware, WHY CAN'T I GET OUT OF FASTBOOT! Lol
Does anyone have any ideas as to what I could try to unbrick this thing?

I know it's a different issue from the one that I had, but the LG Support Tool method that KedarWolf posted might help solve this issue too.
https://forum.xda-developers.com/showpost.php?p=70337463&postcount=5

Splinter 77 - Thank you for the suggestion. I have been trying to get this tool to work for a couple hours and everytime it hangs on the Downloading Firmware section. No matter what I try I can't get it to download the firmware....

Does anyone have some ideas I can try? I'm up for anything at this point!

Kevin_xail said:
Does anyone have some ideas I can try? I'm up for anything at this point!
Click to expand...
Click to collapse
Did you try pulling the battery, put the battery back in.
Hold the volume down and power button at same time. When the lg logo shows up let go of the power button but continue to hold the volume down and press the power button again. It will bring you to a screen tgat has 2 questions. Answer yes to both of them. Then reboot. I believe that resets the way the phone boots almost like resetting a cmos
Sent from my VS995 using XDA-Developers Legacy app

im in the same boat now... ugh
---------- Post added at 06:01 PM ---------- Previous post was at 05:56 PM ----------
ahh i got it man! @Kevin_xail
i dont know if this will help seince u relocked, but do the factory reset dance
hold the vol down and power and put in battery as soon as its on click the power button and re hold it. it will get to recovery, it took me hours but its there.

I had tried that a few times after reading about it but I'll try now for an extended period of time and see if I can activate it. I'll report back with what happens, thanks for the tip dwertz and Team DevDigitel

Well I got in to the recovery menu and reset to factory settings and wipe cache (the only two options) but I still am booting right into FastBoot and can't escape!
I even flashed the stock .kdz again after the factory reset and wiping cache and I'm still stuck in FastBoot
Any other suggestions to try?

Kevin_xail said:
Well I got in to the recovery menu and reset to factory settings and wipe cache (the only two options) but I still am booting right into FastBoot and can't escape!
I even flashed the stock .kdz again after the factory reset and wiping cache and I'm still stuck in FastBoot
Any other suggestions to try?
Click to expand...
Click to collapse
When you have a unlocked boot loader and you do a factory reset, I believe it wipes the OS from the phone giving you no OS. If you can get back to recovery, flash this rom https://forum.xda-developers.com/v20/development/vs995-vzw-nrd90m-modded-notsostock-rom-t3525864
That will at least get you booted so you can flash the kdz.

I can't get into any kind of recovery to flash a rom though

Kevin_xail said:
I can't get into any kind of recovery to flash a rom though
Click to expand...
Click to collapse
How long ago did you get the phone?

Bricked with locked Bootloader on fastboot
Splinter77 said:
I know it's a different issue from the one that I had, but the LG Support Tool method that KedarWolf posted might help solve this issue too.
https://forum.xda-developers.com/showpost.php?p=70337463&postcount=5
Click to expand...
Click to collapse
I was bout ready to give up, got it working with newest lg up and stock flash file from lg support website, I haven't seen a whole lot (any) solved posts so I thought I would share. At least got it working again, rooted is another story.

Kevin_xail said:
Well I got in to the recovery menu and reset to factory settings and wipe cache (the only two options) but I still am booting right into FastBoot and can't escape!
I even flashed the stock .kdz again after the factory reset and wiping cache and I'm still stuck in FastBoot
Any other suggestions to try?
Click to expand...
Click to collapse
Same problem here, did you ever fix it?

Messed things up with upgrade/downgrade?

My wife got a P9 Lite L31. I wanted to upgrade to Nougat. I finally succeeded, but after that I messed things up. I tried to do a clean intall with a update that wasn't ment for this.
In the beginning I could still enter the Nougat recovery, but I wasn't able to reinstall the update.zip. The device wouldn't boot, etc.
I tried to do many different things, but at this moment I cant enter TWRP anymore, I can enter fastboot and is says:
PHONE Unlocked
FRP Unlocked
But flashing an other TWRP recovery doesn's work because I get an error:
(Remote: Command not allowed).
Also relocking the bootloader doesn't work because is gives the same error as the one above.
I can't flash a OEM file through fastboot because it gives the same error as the one above.
I can't use HiSuite because it says it does not support the phone.
I don't know what else I can do right now.
I tried the 3 button method, but I can't get in the official recovery. The phone reboots to some kind of recovery where it wants to update the recovery through wifi, but it ends up with an error that it can't fails to get the package info. But there is no option to do a factory reset (I've put the MM update.app file in sdcard/dload folder).
Any ideas what else I can do to recover the phone?

Unlock the bootloader again.

Johnny TDN said:
Unlock the bootloader again.
Click to expand...
Click to collapse
Ok, did not expect to do that again, but I did it.
What's the next step? flash a nougat recovery? flash a oem recovery?
Fastboot now says:
Error!
Func NO: 11 (recovery image)
Error NO: 2 (load failed)
Looks like fastboot isn't recognized by the computer anymore after the re-unlocking of the bootloader.
Windows device management also doesn't see the device. Not even as an unknown device.... Looks like the bootloader unlock completely bricked the device.

Well.
You must change your motherboard.

Johnny TDN said:
Well.
You must change your motherboard.
Click to expand...
Click to collapse
As per usual, your comment was of no help at all.

Take a look to this thread, it seems similar to your problem https://forum.xda-developers.com/p8lite/help/stuck-rescue-mode-screen-please-help-t3244872
What are you able to do with the phone?

igreja94 said:
As per usual, your comment was of no help at all.
Click to expand...
Click to collapse
-_-
---------- Post added at 09:02 AM ---------- Previous post was at 09:00 AM ----------
Try to discharge your battery by leaving it on Fastboot mode.
Charget the batery and let it boot itself.
If it boots in the software, it will be very easy to fix. If no, then changing the motherboard is required

Potato997 said:
Take a look to this thread, it seems similar to your problem https://forum.xda-developers.com/p8lite/help/stuck-rescue-mode-screen-please-help-t3244872
What are you able to do with the phone?
Click to expand...
Click to collapse
To be honest, nothing.
It can do two things, you can let it boot and then it says it's booting, and that's it (after the warning that the bootloader is unlocked), or I can boot into fastboot but the phone is not detected by the computer. Device manager doesn't see the device at all not even as an unknown device. Nothing. So no way to flash anything using fastboot. KI also can't get into the fastboot&repair.
So yeah, I decided to send it in for repair.

Please help! ZTE Axon 7 won't boot after deleting Lineage and TRWP

Hi,
don't know if this problem has already occurred before.
I had lineage and TRWP installed on my Axon 7 (EU version) and wanted to go back to the stock a2017g.
Therefore I deleted the ROM and wiped everything with TWRP.
Then I deleted TWRP and now i'm stuck at the the bootloader (which is unlocked), but TWRP seems to be gone.
The main problem is, whenever I try to flash a new stock rom (via recovery), I get the error "signature verification failed" and the process is aborted with no change to the system whatsoever.
Is there anything I can do at this point or is my phone practically dead?
Thanks in advance for any help.

tempest89 said:
Hi,
don't know if this problem has already occurred before.
I had lineage and TRWP installed on my Axon 7 (EU version) and wanted to go back to the stock a2017g.
Therefore I deleted the ROM and wiped everything with TWRP.
Then I deleted TWRP and now i'm stuck at the the bootloader (which is unlocked), but TWRP seems to be gone.
The main problem is, whenever I try to flash a new stock rom (via recovery), I get the error "signature verification failed" and the process is aborted with no change to the system whatsoever.
Is there anything I can do at this point or is my phone practically dead?
Thanks in advance for any help.
Click to expand...
Click to collapse
Try to boot into bootloader interface, and issue command "fastboot flash recovery TWRP.img" on your computer( the current working directory should contain the TWRP.img file) . If your bootloader is unlocked, you should see no error of this command. Then press up/down button to select recovery mode. You should see the familiar TWRP again. Good luck!

tempest89 said:
Hi,
don't know if this problem has already occurred before.
I had lineage and TRWP installed on my Axon 7 (EU version) and wanted to go back to the stock a2017g.
Therefore I deleted the ROM and wiped everything with TWRP.
Then I deleted TWRP and now i'm stuck at the the bootloader (which is unlocked), but TWRP seems to be gone.
The main problem is, whenever I try to flash a new stock rom (via recovery), I get the error "signature verification failed" and the process is aborted with no change to the system whatsoever.
Is there anything I can do at this point or is my phone practically dead?
Thanks in advance for any help.
Click to expand...
Click to collapse
Did you try flashing an official full zip, like B10? That's another thing you can try, since you're going to lose TWRP after you flash a stock rom anyways

If you dont have recovery, flash it from edl mode, you can flash twrp or stock.
Once you install it, performa a full wipe from stock recovery, and flash a full zip.
I have similar problems, I dont loose recovery, but stock dont boot after coming back from aosp, a factory reset did the job. I think is because different filesystems in data partition

Choose an username... said:
Did you try flashing an official full zip, like B10? That's another thing you can try, since you're going to lose TWRP after you flash a stock rom anyways
Click to expand...
Click to collapse
Hi, the B10 ROM from the ZTE homepage did the trick.
Worked out nicely.
Thank you so much.
One final question remains for myself: How can I relock the bootloader (so that the 5 second screen won't show up at the start).
Tried different ways with adb and fastload, but nothing seemed to have an effect here.
So what to do?
Thank you again for your help.

tempest89 said:
Hi, the B10 ROM from the ZTE homepage did the trick.
Worked out nicely.
Thank you so much.
One final question remains for myself: How can I relock the bootloader (so that the 5 second screen won't show up at the start).
Tried different ways with adb and fastload, but nothing seemed to have an effect here.
So what to do?
Thank you again for your help.
Click to expand...
Click to collapse
you shouldn't. Fastboot should do the trick, by doing fastboot oem lock, but many people reported bricking and bad stuff...
Actually that screen comes very handy in case of a brick or if you want to enter a specific mode.l, you just select the mode and voila
Do you have fastboot? I don't know if B10 still has it, but 7.0 hasn't got it

Choose an username... said:
you shouldn't. Fastboot should do the trick, by doing fastboot oem lock, but many people reported bricking and bad stuff...
Actually that screen comes very handy in case of a brick or if you want to enter a specific mode.l, you just select the mode and voila
Do you have fastboot? I don't know if B10 still has it, but 7.0 hasn't got it
Click to expand...
Click to collapse
Hi,
I tried adb and fastboot via pc and with the axon toolkit.
The adb worked fine, but no sign of effect by the fastboot commands.
So I guess I don't have it.
Is there any other solution to at least bypass the 5 second screen?
Thanks

tempest89 said:
Hi,
I tried adb and fastboot via pc and with the axon toolkit.
The adb worked fine, but no sign of effect by the fastboot commands.
So I guess I don't have it.
Is there any other solution to at least bypass the 5 second screen?
Thanks
Click to expand...
Click to collapse
Lol fastboot is not something like EDL, it looks similar to the 5 sec screen...
When you get the 5 sec screen, use the vol keys and pwr to get to the Fastboot option and enter - it should reboot and get to fastboot after some time
You should look up what fastboot, EDL, ADB and DFU are before doing all this stuff - you can mess up badly, and by not knowing you're complicating everything - my explanation and your understanding

TWRP stuck at splash screen, fastboot not working, don't know how to boot into EDL...

Hello, i've got a big problem:
i've tried to install 8.1 Oreo, but it asked for password, i've tried to format data and it showed me an error, i've tried to reboot recovery but it stuck on splash TWRP screen... And also fastboot mode from bootloader can't be launched - it just starting system which i can't access. I have a2017g btw.
Hoping for help and happy new year to everybody!

kingracer said:
Hello, i've got a big problem:
i've tried to install 8.1 Oreo, but it asked for password, i've tried to format data and it showed me an error, i've tried to reboot recovery but it stuck on splash TWRP screen... And also fastboot mode from bootloader can't be launched - it just starting system which i can't access. I have a2017g btw.
Hoping for help and happy new year to everybody!
Click to expand...
Click to collapse
uuhh.. MiFlash?
If you can get TWRP 3.2.1-0 to work, try to format data again. If it fails follow raystef66's method on how to get rid of the 5 second screen (you'd be doing it only to restore fastboot) then boot to fastboot and issue 'fastboot erase userdata'

Choose an username... said:
uuhh.. MiFlash?
If you can get TWRP 3.2.1-0 to work, try to format data again. If it fails follow raystef66's method on how to get rid of the 5 second screen (you'd be doing it only to restore fastboot) then boot to fastboot and issue 'fastboot erase userdata'
Click to expand...
Click to collapse
Where can i find that method? I've already got it figured out but i still can't install Oreo because after using the instruction I've had the same problem

kingracer said:
Where can i find that method? I've already got it figured out but i still can't install Oreo because after using the instruction I've had the same problem
Click to expand...
Click to collapse
On the guides section of course

6T stuck in "the bootloader is unlocked" screen

Hello,
I've installed a twrp recovery file on my oneplus 6t recently, and for some reason after trying to boot up the OS this frozen "bootloader is unlocked" screen appears. It won't go away! The screen turns black for a second after holding down the volume up+power button, but then goes back to the "bootloader is unlocked" screen again. Draining the battery doesn't help either.
Any ideas on how to fix this?

You probably have to MSMTool it but you could try activating your other partition.
Code:
fastboot --set-active=a
Or
Code:
fastboot --set-active=b
You didn't give much info on what happened exactly. We dig the technical details on here!
Wrapped with delicious Fajita [emoji896]

FiWe20 said:
Hello,
I've installed a twrp recovery file on my oneplus 6t recently, and for some reason after trying to boot up the OS this frozen "bootloader is unlocked" screen appears. It won't go away! The screen turns black for a second after holding down the volume up+power button, but then goes back to the "bootloader is unlocked" screen again. Draining the battery doesn't help either.
Any ideas on how to fix this?
Click to expand...
Click to collapse
Is your phone the T-Mobile or International version?
If International, have a look at this thread and see if the issue you are facing is similar to mine. The solution posted by Mannan Qamar further down the thread is what solved the issue for me, and I've detailed the solution step by step in the latest post in that thread.

Timmmmaaahh said:
You probably have to MSMTool it but you could try activating your other partition.
Code:
fastboot --set-active=a
Or
Code:
fastboot --set-active=b
You didn't give much info on what happened exactly. We dig the technical details on here!
Wrapped with delicious Fajita [emoji896]
Click to expand...
Click to collapse
Thanks for replying!
For some reason after days of desperately trying to fix it, the 6t it suddenly booted into fastboot after being battery-drained. I am not experienced in rooting at all but I think this stuck "bootloader is unlocked" issue happened when I installed the twrp file via the "flash boot_a" instead of the "flash recovery".
FAILED (remote: '(recovery_a) No such partition')
comes up when using the normal "flash recovery".
So the flashing is the main problem I guess. Is there any other way to install twrp?

FiWe20 said:
Thanks for replying!
For some reason after days of desperately trying to fix it, the 6t it suddenly booted into fastboot after being battery-drained. I am not experienced in rooting at all but I think this stuck "bootloader is unlocked" issue happened when I installed the twrp file via the "flash boot_a" instead of the "flash recovery".
FAILED (remote: '(recovery_a) No such partition')
comes up when using the normal "flash recovery".
So the flashing is the main problem I guess. Is there any other way to install twrp?
Click to expand...
Click to collapse
You need to boot TWRP first as there is no recovery partition to flash to (hence the error). From there, you can flash a TWRP installer as explained in the TWRP thread. If you're not knowledgeable or have doubts about the topic then I strongly recommend in reading thoroughly before taking any actions.
Alternatively, you can flash from within Magisk Manager when you get the boot image right as explained in my previous post here. That can be a bumpy ride though! You've been warned
Just note that, with Android 10 (if that is your goal), the safest option is having root without TWRP recovery. If you're sticking with Android Pie, just ignore these last two paragraphs.

Timmmmaaahh said:
You need to boot TWRP first as there is no recovery partition to flash to (hence the error). From there, you can flash a TWRP installer as explained in the TWRP thread. If you're not knowledgeable or have doubts about the topic then I strongly recommend in reading thoroughly before taking any actions.
Alternatively, you can flash from within Magisk Manager when you get the boot image right as explained in my previous post here. That can be a bumpy ride though! You've been warned
Just note that, with Android 10 (if that is your goal), the safest option is having root without TWRP recovery. If you're sticking with Android Pie, just ignore these last two paragraphs.
Click to expand...
Click to collapse
I tried "fastboot boot twrp.img" before but then the next issue comes up...
Sending 'boot.img' (31136 KB) OKAY [ 0.667s]
Booting FAILED (remote: 'unknown command')

FiWe20 said:
I tried "fastboot boot twrp.img" before but then the next issue comes up...
Sending 'boot.img' (31136 KB) OKAY [ 0.667s]
Booting FAILED (remote: 'unknown command')
Click to expand...
Click to collapse
Are you on Android 10? Because in that case this is expected behaviour or in sweet dev terms: by design. OOS Android 10 Beta 1 doesn't allow TWRP for some reason. You can only get it by fastboot flashing a patched boot image or via a Magisk flash. You also need some luck because in both cases it can fail miserably. On top of that, you need some old keymaster to be able to access any files. It's all a true joyride for now, lol...
---------- Post added at 02:18 PM ---------- Previous post was at 02:14 PM ----------
Wait, "fastboot boot twrp.img" gives you "Sending 'boot.img'"? That can't be. Enlighten us on version numbers first please.

Timmmmaaahh said:
Are you on Android 10? Because in that case this is expected behaviour or in sweet dev terms: by design. OOS Android 10 Beta 1 doesn't allow TWRP for some reason. You can only get it by fastboot flashing a patched boot image or via a Magisk flash. You also need some luck because in both cases it can fail miserably. On top of that, you need some old keymaster to be able to access any files. It's all a true joyride for now, lol...
---------- Post added at 02:18 PM ---------- Previous post was at 02:14 PM ----------
Wait, "fastboot boot twrp.img" gives you "Sending 'boot.img'"? That can't be. Enlighten us on version numbers first please.
Click to expand...
Click to collapse
Its interesting because I managed to get TWRP working the first time and if I remember correctly it was via the "flash boot_a" command. And yes it was through the Open Beta version of Android 10. I think this whole "bootloader is unlocked" problem was caused after rebooting from twrp.
How do you fastboot flash a patched boot image if flashing a normal boot image cause errors? I really appreciate you taking your time on this.
---------
Fastboot version 29.0.4-587166

FiWe20 said:
Its interesting because I managed to get TWRP working the first time and if I remember correctly it was via the "flash boot_a" command. And yes it was through the Open Beta version of Android 10. I think this whole "bootloader is unlocked" problem was caused after rebooting from twrp.
How do you fastboot flash a patched boot image if flashing a normal boot image cause errors? I really appreciate you taking your time on this.
Click to expand...
Click to collapse
There could be many reasons; Android works in mysterious ways. The "bootloader is unlocked" screen shows the minute you.. well, unlock your bootloader (fastboot oem unlock)
The fact that it freezes is simply because it finds something to boot but it fails to do so, which could be either an OS or a recovery. I've been there as well but forcing a restart with power+volume buttons did fix it for me (different situation of course, it was months ago).
Trust me, experiencing these annoying situations is the best way to learn more about your device. Before you know it you'll be playing around with fastboot, adb, recoveries, ROMs, kernels and mods like a pro.

Timmmmaaahh said:
There could be many reasons; Android works in mysterious ways. The "bootloader is unlocked" screen shows the minute you.. well, unlock your bootloader (fastboot oem unlock)
The fact that it freezes is simply because it finds something to boot but it fails to do so, which could be either an OS or a recovery. I've been there as well but forcing a restart with power+volume buttons did fix it for me (different situation of course, it was months ago).
Trust me, experiencing these annoying situations is the best way to learn more about your device. Before you know it you'll be playing around with fastboot, adb, recoveries, ROMs, kernels and mods like a pro.
Click to expand...
Click to collapse
Booting OS doesn't work(-> "freeze screen"), recovery mode doesn't work(-> also freeze) and installing new recovery files won't work either because it's in the beta version of android 10. So my 6t is completely broken unless twrp releases an open beta android 10 version of their recovery file?

FiWe20 said:
Booting OS doesn't work(-> "freeze screen"), recovery mode doesn't work(-> also freeze) and installing new recovery files won't work either because it's in the beta version of android 10. So my 6t is completely broken unless twrp releases an open beta android 10 version of their recovery file?
Click to expand...
Click to collapse
Great. What did you do this time? lol. I thought you had it working. Not to worry, you can always resort to the MSMtool (found here). But before you do, there's a few 'softer' methods you can try. I advise reading the first post of this thread.
One piece of advice: if at all possible, try avoiding locking the bootloader again. It serves no purpose and can only create more problems. I have to admit that I haven't used MSMtool myself (been quite lucky so far) but I'm guessing it locks the bootloader in its automated process. If there's a switch to prevent that, use it! If not, ah well...

Timmmmaaahh said:
Great. What did you do this time? lol. I thought you had it working. Not to worry, you can always resort to the MSMtool (found here). But before you do, there's a few 'softer' methods you can try. I advise reading the first post of this thread.
One piece of advice: if at all possible, try avoiding locking the bootloader again. It serves no purpose and can only create more problems. I have to admit that I haven't used MSMtool myself (been quite lucky so far) but I'm guessing it locks the bootloader in its automated process. If there's a switch to prevent that, use it! If not, ah well...
Click to expand...
Click to collapse
Nah. It locks the Bootloader. Meaning if something went wrong you can't do anything. Happened to one guy here but I guess that was cause he erased persist. Another thing about MSM is that it only flashes One Slot.

Mannan Qamar said:
Nah. It locks the Bootloader. Meaning if something went wrong you can't do anything. Happened to one guy here but I guess that was cause he erased persist. Another thing about MSM is that it only flashes One Slot.
Click to expand...
Click to collapse
That's why I referred to the 'softer' methods, sometimes just switching partition slots can solve all your problems.

FiWe20 said:
Booting OS doesn't work(-> "freeze screen"), recovery mode doesn't work(-> also freeze) and installing new recovery files won't work either because it's in the beta version of android 10. So my 6t is completely broken unless twrp releases an open beta android 10 version of their recovery file?
Click to expand...
Click to collapse
MSM tool and stop suffering

FiWe20 said:
Booting OS doesn't work(-> "freeze screen"), recovery mode doesn't work(-> also freeze) and installing new recovery files won't work either because it's in the beta version of android 10. So my 6t is completely broken unless twrp releases an open beta android 10 version of their recovery file?
Click to expand...
Click to collapse
Msm tool dude