I got my OnePlus 7 Pro today and tried to install Magisk by patching the boot.img. After trying to flash the patched image, I now have an issue where rebooting the devices leads me straight back to the bootloader. Trying to enter recovery also leads me straight back to the bootloader. I tried flashing the original boot.img I extracted from the OTA update file provided by OnePlus, but it still isn't working. I do not have TWRP or any custom recovery installed. Any help would be much appreciated. I noticed similar threads, however they all installed twrp, though I haven't yet as trying to run "fastboot boot twrp.img" always resulted in it booting to a screen saying "fastboot mode" which wasn't terribly helpful.
Edit: Its not the tmobile/5g/carrier version. I purchased it through OnePlus' website though I forget the exact model number.
Well, "fastboot boot twrp.img" does not work on all devices, sometimes you have to use: fastboot flash boot insert_twrp_img_name_here.imgLearned that the hard way, also use the unofficial twrp from mauronofrio.
Had the same problem as you have, and fixed it with that unofficial twrp.
Faith1105 said:
Well, "fastboot boot twrp.img" does not work on all devices, sometimes you have to use: fastboot flash boot insert_twrp_img_name_here.imgLearned that the hard way, also use the unofficial twrp from mauronofrio.
Had the same problem as you have, and fixed it with that unofficial twrp.
Click to expand...
Click to collapse
Did you need to completely revert to stock after the issue, or did flashing twrp fix the fastboot loop?
Edit: Trying to flash the stock fastboot rom currently as flashing twrp did nothing probably because me trying to fix it broke everything. Hopefully the stock rom will get everything back to a working state where I can try again, just this time flashing twrp.
Also using windows this time instead of linux....
mnbvcxzl90 said:
Did you need to completely revert to stock after the issue, or did flashing twrp fix the fastboot loop?
Edit: Trying to flash the stock fastboot rom currently as flashing twrp did nothing probably because me trying to fix it broke everything. Hopefully the stock rom will get everything back to a working state where I can try again, just this time flashing twrp.
Also using windows this time instead of linux....
Click to expand...
Click to collapse
Ok, so, trying to restore stock seems to have failed miserably.... any advice is most welcomed qq
OK.... so trying to unbrick the device using the msm stuff, I couldn't even make it to the downloader screen. After holding volume +/- and powering off, my screen is now black HOWEVER the phone gets detected by windows when I plug & unplug it. I have no idea what to do anymore. Someone please help
Figured I'd give the solution here in case someone else is in the same exact problem as me:
Follow the instructions over at https://forum.xda-developers.com/oneplus-7-pro/how-to/op7pro-collection-unbrick-tools-t3956595
I tried to de-brick it using the fastboot roms and all that, no dice. The only thing that seems to have worked was following the above and using the msm tool. Everything wiped, but hey, at least the phone is bootable again and now I have a way to fix it should this happen again. Yay for happy endings.
Edit: Also, following Faith1105's advice, flashing twrp to boot instead of trying to just boot it first worked successfully and from there I was able to install magisk.
Edit 2: Now wifi isn't working.... why life, why...
Edit 3: OK: EVERYTHING IS GOOD NOW. Twrp ran into a boot loop issue, used twrp to flash the most recent android 10 zip, rebooted and was greeted by stock recovery, then used that to wipe absolutely everything and reboot. After skipping through initial setup and making use wifi was working I rebooted again and this time tried booting twrp the way the usual instructions say to, this time it worked for whatever reason so once that started I used twrp to flash twrp's installer and magisk. It looks like everything is working correctly now. If you have the same issue maybe this stuff will work for you or maybe not: I don't know, and honestly I'm now brain dead lol.
Related
Hey Guys,
so i got a wierd bootloop problem and for now i didn't find any solution here on xda or somewhere else,
not even a thread where someone has the same problem.
I'll try to give you as much information as possible in a chronological order.
First of all I got the international model (G920F).
So like 2-3 months ago everything was fine, my phone was rooted, got TWRP working and was flashing Roms with no problem what so ever. TW-Roms like Noble Rom and also AOSP/Lineage OS.
One day I wanted to flash UltImAtE NoUgAt A8 Port and that is where the trouble began, dont think it has something to do with the rom but maybe it helps.
So i flashed the Rom(wiped everything except int. storage), flashing was no problem but it didnt boot.
I know first boot always takes some time but after about 20-30 min I forced a reboot (Power+Vol. Down for 7sec).
After that the phone got into a Bootloop(always rebooted into the "first bootingscreen")
I let this process happen for about 15 min. and then tried to enter TWRP via hitting the buttons between the boots which didn't work. I then did "force" a reboot(Power + Vol. Down) which strangely resulted in one final reboot and turning the phone off after the first bootscreen.
So with the phone finally turned off I was able to boot into TWRP and reflashed the rom but the result was the same.
I did the same procedure again to get into TWRP and flashed the Stock Deodexed TW Rom, flashing worked but then the Phone directly rebooted into TWRP. Rebooting out of TWRP or booting the phone from beeing shut down both resulting into booting to TWRP.
So to get my Phone working again I had to flash stock ROM which in my case is G920FXXU5EQDF_G920FDBT5EQD1_G920FXXU5EQCD via Odin.
That worked but of course root and TWRP were gone so I then flashed TWRP via Odin(both newest Versions at that point)
aaaaaand phone straightly booted into TWRP again all the time. I tried different combinations of older versions of both twrp and odin but the result always was the same.
So at the moment I am on Stock, the phone works which is nice but i really wanna get TWRP working again and i have no idea what to do.
I hope someone can help me with that.
Cheers Guys
MuTec said:
Hey Guys,
so i got a wierd bootloop problem and for now i didn't find any solution here on xda or somewhere else,
not even a thread where someone has the same problem.
I'll try to give you as much information as possible in a chronological order.
First of all I got the international model (G920F).
So like 2-3 months ago everything was fine, my phone was rooted, got TWRP working and was flashing Roms with no problem what so ever. TW-Roms like Noble Rom and also AOSP/Lineage OS.
One day I wanted to flash UltImAtE NoUgAt A8 Port and that is where the trouble began, dont think it has something to do with the rom but maybe it helps.
So i flashed the Rom(wiped everything except int. storage), flashing was no problem but it didnt boot.
I know first boot always takes some time but after about 20-30 min I forced a reboot (Power+Vol. Down for 7sec).
After that the phone got into a Bootloop(always rebooted into the "first bootingscreen")
I let this process happen for about 15 min. and then tried to enter TWRP via hitting the buttons between the boots which didn't work. I then did "force" a reboot(Power + Vol. Down) which strangely resulted in one final reboot and turning the phone off after the first bootscreen.
So with the phone finally turned off I was able to boot into TWRP and reflashed the rom but the result was the same.
I did the same procedure again to get into TWRP and flashed the Stock Deodexed TW Rom, flashing worked but then the Phone directly rebooted into TWRP. Rebooting out of TWRP or booting the phone from beeing shut down both resulting into booting to TWRP.
So to get my Phone working again I had to flash stock ROM which in my case is G920FXXU5EQDF_G920FDBT5EQD1_G920FXXU5EQCD via Odin.
That worked but of course root and TWRP were gone so I then flashed TWRP via Odin(both newest Versions at that point)
aaaaaand phone straightly booted into TWRP again all the time. I tried different combinations of older versions of both twrp and odin but the result always was the same.
So at the moment I am on Stock, the phone works which is nice but i really wanna get TWRP working again and i have no idea what to do.
I hope someone can help me with that.
Cheers Guys
Click to expand...
Click to collapse
You do know that if you flash TWRP, you need to use a kernel that has dm-verity disabled or you need to be rooted. Flash TWRP then Flash Magisk through TWRP
U99Dev said:
You do know that if you flash TWRP, you need to use a kernel that has dm-verity disabled or you need to be rooted. Flash TWRP then Flash Magisk through TWRP
Click to expand...
Click to collapse
As it seems I did not, good thing that its written right at the TWRP download page...
Can't remember doing this when I installed TWRP first but as it seems I did.
Everything is working fine, just flashed Nexus OS and it booted.
Thank you so much dude
Hi.
So this was pretty stupid of me. I was trying to flash LiquidRemix onto my OP6, but I forgot to wipe the system partition. Flashed the rom, then blu_spark twrp, and rebooted into recovery to flash gapps and all. Got a black screen with a static LED. Didn't think that was a big issue cause this has happened before with normal TWRP on OB6 or OB7. Tried hard resetting to see if I could get into system, same result. Tried fastboot flashing 9.0.2, no help. And finally tried flashing OB9 via fastboot, and also no help.
I've reverted back to my tiny S6 and have sent repair request to OP. I haven't gotten anything back yet, so I thought in the mean time, I'd look for help on XDA and try to fix it before having the chance to send it in.
Any help/advice would be greatly appreciated.
Cheers
// EDIT
Figured out how to fix it. Used the MSMDownloadTool to unbrick my device. Worked wonders. Thanks to r/oneplus Discord
I did something like that I had to format data after I flashed the stock rom
mightyblazer said:
I did something like that I had to format data after I flashed the stock rom
Click to expand...
Click to collapse
How did you get to format? I really can't get into the OS or recovery at all
I was actually able to boot into TWRP maybe you can get into fastboot? And try flashing TWRP again
mightyblazer said:
I was actually able to boot into TWRP maybe you can get into fastboot? And try flashing TWRP again
Click to expand...
Click to collapse
I'm able to get into fastboot, but even if I fastboot boot [insert twrp file name here], it'd still result in the blank screen and static LED
Hmm I don't know then sorry
Try
fastboot flash boot twrp.zip
Then
fastboot reboot
You will need to use full stock rom first before doing anything else though.
I was in the same boat as you the other day. I flashed different versions of twrp until i managed to boot one because some twrp isn't compatible with pie.
Lol I never wipe system...
Might sound like a "hard-bricking" issue since you cant boot into the OS nor recovery. There 's a hard brick recovery guide, but it'll put you down to oreo OOS: https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892
As long as you can boot into fastboot, you can follow the guide's process with no problem.
Today I tried to finally update to the latest version of crDroid, but ended up having a bunch of issues doing so, and after a lot of troubleshooting and trying to fix it, I ended up putting it into a bootloop of some sort instead.
I'm pretty sure the last thing I tried was installing a different version of TWRP to see if that version would let me properly install the rom, and stop my phone from always rebooting into recovery mode.
Trying to turn it on normally or boot into TWRP leaves it hanging on the "Redmi" boot screen, it can boot into fastboot mode though.
I'm guessing that the only way to recover my phone at this point is to flash the Official MIUI rom back onto the phone, but that also involves wiping Data and losing pretty much everything I've put on the phone.
I was smart enough to make a TWRP of the Data folder, but while making the backup, the console said it doesn't include all personal files or something.
How much of my personal data and files can I rescue from the phone in this state, and how can I do that before it gets wiped when fixing it?
Also, I think I really need some help in actually restoring my phone and flashing the custom rom properly.
No matter how much effort I put into figuring out how to do this stuff, unexpected issues always seem to happen, and turns something that initially seemed so simple into multiple hours of troubleshooting.
The only way I think i've gotten rom flashing to work at all was by wiping everything and installing the official MIUI rom, but I don't want to be losing my data every month when an update comes out.
So, could someone please help me get my phone working again?
Edit: I ended up fixing my own issue by ADB flashing on a different release of TWRP, and then installing fcrypt disabler after the rom but before everything else.
Sanarise said:
Today I tried to finally update to the latest version of crDroid, but ended up having a bunch of issues doing so, and after a lot of troubleshooting and trying to fix it, I ended up putting it into a bootloop of some sort instead.
I'm pretty sure the last thing I tried was installing a different version of TWRP to see if that version would let me properly install the rom, and stop my phone from always rebooting into recovery mode.
Trying to turn it on normally or boot into TWRP leaves it hanging on the "Redmi" boot screen, it can boot into fastboot mode though.
I'm guessing that the only way to recover my phone at this point is to flash the Official MIUI rom back onto the phone, but that also involves wiping Data and losing pretty much everything I've put on the phone.
I was smart enough to make a TWRP of the Data folder, but while making the backup, the console said it doesn't include all personal files or something.
How much of my personal data and files can I rescue from the phone in this state, and how can I do that before it gets wiped when fixing it?
Also, I think I really need some help in actually restoring my phone and flashing the custom rom properly.
No matter how much effort I put into figuring out how to do this stuff, unexpected issues always seem to happen, and turns something that initially seemed so simple into multiple hours of troubleshooting.
The only way I think i've gotten rom flashing to work at all was by wiping everything and installing the official MIUI rom, but I don't want to be losing my data every month when an update comes out.
So, could someone please help me get my phone working again?
Click to expand...
Click to collapse
can u boot into twrp?
if u can boot, while in twrp, connect your phone via usb cable to pc. u can copy everything on pc
Simoom Sadik said:
can u boot into twrp?
if u can boot, while in twrp, connect your phone via usb cable to pc. u can copy everything on pc
Click to expand...
Click to collapse
Unfortunately, I can't.
Trying to boot into TWRP just gets stuck on the 'Redmi' boot logo.
I just remembered that you can install TWRP over ADB, and that Peter's one says it works even when the system partition is empty, so maybe the issue is the TWRP I installed and could possibly undo this part of the issue over ADB.
It won't fix the issue preventing my from updating my rom, but recovery only is still better than a soft brick.
Edit: That worked, i've put Peter's TWRP back on, and it's launching into recovery mode/TWRP again now
twrp not boot after successfully flash in this rom
Sanarise said:
Unfortunately, I can't.
Trying to boot into TWRP just gets stuck on the 'Redmi' boot logo.
I just remembered that you can install TWRP over ADB, and that Peter's one says it works even when the system partition is empty, so maybe the issue is the TWRP I installed and could possibly undo this part of the issue over ADB.
It won't fix the issue preventing my from updating my rom, but recovery only is still better than a soft brick.
Edit: That worked, i've put Peter's TWRP back on, and it's launching into recovery mode/TWRP again now
Click to expand...
Click to collapse
flash latest twrp download from github, install twrpbuilder img twrp ,it boot fine and you will copy your data to pc and then install any other twrp img which u want , dont wipe anything from phone before phone boot.flash only original twrp builder 3.2.3.1 official,it boot only on latest updates.
Why nobody use orangefox?
is your issue solve or not tell,
Simoom Sadik said:
can u boot into twrp?
if u can boot, while in twrp, connect your phone via usb cable to pc. u can copy everything on pc
Click to expand...
Click to collapse
if your problem is not solve then tell me you need to flash a fastboot rom first with save user data.bat file and when it installed then you can install twrp builder 3.2.1. and then boot to twrp this methods working fine,if you recently flashed any android 10 rom then first you need to flash a miui fastboot rom,or flash it via command mode direct only 3 files
first click on extract a fastboot rom and copy boot system and vender file with flash.all bat file and make a new folder then click on flash.bat save user data file to flash these images
or you can do this manually
fastboot flash system system.img
fastboot flash vender vender.img
fastboot flash boot boot.img
then reboot device to fastboot again
now flash latest official twrp builder 3.2.3.1 img twrp and take all your data backup,
in fastboot flash latest miui do not downgrade direct otherwise you lost your data,
after this if you sucess then you can flash your old rom which is running before issue of boot loop of redmi logo
it will deincrypt your data safely and then root device and boot normally, if you lost anything then contact me with mail or whatsapp i will help you,7009197673 india
and this twrp work on all version from chines to global beta stable and indian stable
joke19 said:
Why nobody use orangefox?
Click to expand...
Click to collapse
In the end, I did try orangefox, and it might have been part of why it worked.
However, the crDroid installation instructions specifically mentions using Peter's TWRP, so I initially used that one.
anmoltinder said:
if your problem is not solve then tell me you need to flash a fastboot rom first with save user data.bat file and when it installed then you can install twrp builder 3.2.1. and then boot to twrp this methods working fine,if you recently flashed any android 10 rom then first you need to flash a miui fastboot rom,or flash it via command mode direct only 3 files
Click to expand...
Click to collapse
Thank you for the effort you put into typing up a guide to help me, but I ended up fixing my own problem.
I was able to use fastboot to flash on a better TWRP release, and then get the rom to install properly by installing fcrypt-disabler just after it.
Sanarise said:
Today I tried to finally update to the latest version of crDroid, but ended up having a bunch of issues doing so, and after a lot of troubleshooting and trying to fix it, I ended up putting it into a bootloop of some sort instead.
I'm pretty sure the last thing I tried was installing a different version of TWRP to see if that version would let me properly install the rom, and stop my phone from always rebooting into recovery mode.
Trying to turn it on normally or boot into TWRP leaves it hanging on the "Redmi" boot screen, it can boot into fastboot mode though.
I'm guessing that the only way to recover my phone at this point is to flash the Official MIUI rom back onto the phone, but that also involves wiping Data and losing pretty much everything I've put on the phone.
I was smart enough to make a TWRP of the Data folder, but while making the backup, the console said it doesn't include all personal files or something.
How much of my personal data and files can I rescue from the phone in this state, and how can I do that before it gets wiped when fixing it?
Also, I think I really need some help in actually restoring my phone and flashing the custom rom properly.
No matter how much effort I put into figuring out how to do this stuff, unexpected issues always seem to happen, and turns something that initially seemed so simple into multiple hours of troubleshooting.
The only way I think i've gotten rom flashing to work at all was by wiping everything and installing the official MIUI rom, but I don't want to be losing my data every month when an update comes out.
So, could someone please help me get my phone working again?
Edit: I ended up fixing my own issue by ADB flashing on a different release of TWRP, and then installing fcrypt disabler after the rom but before everything else.
Click to expand...
Click to collapse
help.I woke up yesterday and I turned on my phone and it is stuck on the Mi logo.All i can do is get it to fastboot thing.It seems like you and I have the same problem and I would love to have some help from you
Fcsubxrhi said:
help.I woke up yesterday and I turned on my phone and it is stuck on the Mi logo.All i can do is get it to fastboot thing.It seems like you and I have the same problem and I would love to have some help from you
Click to expand...
Click to collapse
If you can access fastboot, then flash TWRP.... Enter recovery, wipe your system partitions and then flash the Stock MIUI ROM or use the MiFlash tool. Make sure you aren't flashing an older version of the ROM than the onle already installed.
CongestedHangman said:
can u boot into twrp?
if u can boot, while in twrp, connect your phone via usb cable to pc. u can copy everything on pc
Click to expand...
Click to collapse
I have the same problem that stated after installing the update for derpfest and I can boot into twrp. Any solution for me?
Hi, as the title explains I can flash and boot into lineage os but when I try to flash a stock OxygenOS signed flashable zip from this thread (https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-mirrors-official-oxygen-os-t3792244)
and when I boot to system, the screen doesn't show a boot logo, it just goes black for a few seconds before rebooting back to twrp (also if it helps, when it goes to twrp all the files are gibberish, I have to shut off the phone and boot into it from fastboot or I can't see any files).
This all started because I misunderstood the instructions and tried to flash an ota package which then broke the system, it's working now but I'd much rather use OOS as Lineage is missing a lot of the features I'm used to on Oxygen.
I've also tried the "flash-all-partitins-fastboot" from https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665 but unfortunately that gave the same issue, it just went back to recovery and wouldn't load OOS.
If anyone has any ideas on how to get back to oxygen that'd be super helpful! I'm considering using the MSM tool but I'd rather not have to start from scratch and lose all my files.
I'm just guessing, but there might be something wrong with your TWRP, did you try re-flashing it?
mati11233 said:
I'm just guessing, but there might be something wrong with your TWRP, did you try re-flashing it?
Click to expand...
Click to collapse
I should've clarified in the post, I mean all the files are gibberish (as in not decrypted I think?) but when I
Code:
fastboot boot twrp.img
it works fine and I can see all the files.
I've probably tried flashing it 4 times through twrp but every time it just does the same thing, boot to system just shows a black screen for a few seconds then reboots to twrp.
I'd love to use blu_spark like everyone recommends but I can't find the blu_spark recovery for the op6, only their kernel.
The reason why it's gibberish is because your device is encrypted and you need to input the password in the twrp to be able to access it. Seems the twrp doesn't detect the encryption correctly so there might be something wrong with it.
Here is the bluespark twrp https://github.com/engstk/android_device_oneplus_enchilada/releases
mati11233 said:
The reason why it's gibberish is because your device is encrypted and you need to input the password in the twrp to be able to access it. Seems the twrp doesn't detect the encryption correctly so there might be something wrong with it.
Here is the bluespark twrp https://github.com/engstk/android_device_oneplus_enchilada/releases
Click to expand...
Click to collapse
I just tried with blu_spark and the same thing happens but I realised something else, twrp only doesn't work on slot A.
If I see that it didn't decrypt the files, I can set B to active, reboot to recovery, and it works perfectly.
I noticed after one of the failed boots it switched the active slot to B even though I had set it to A before flashing. So every time it doesn't show the logo or anything, it sets the active slot from A to B and reboots to recovery.
Also I just looked and from the Backup page, it shows 2.7 GB for system on slot A and 1.7GB on slot B so I'm going to try wiping both and reflashing the flashable signed zip on each then twrp.
UPDATE: Just did that and the twrp installer was giving an error saying unsupported android version so I looked and system is only 4MB after flashing that package (OnePlus6Oxgygen_22_OTA_034_all_...zip), I'm trying an older one (...OTA_026...zip) to see if that actually works.
So I tried with the older one and lineage and they both still left the system partition at 4MB and the blu_spark twrp installer isn't detecting an android version. The system image partition is at 2.6GB if that means anything.
Oh wait more update, I'm dumb and shut off the phone while taking the case off (got stuck and it was pushing the power button) and even though the twrp installer couldn't detect anything and twrp said No OS installed when trying to boot to system, lineage just started up, no problem. I am very confused I miss when there was one system partition.
How are you flashing the OS?
mati11233 said:
How are you flashing the OS?
Click to expand...
Click to collapse
I'm using twrp, blu_spark and normal, and both have the same result. They can flash lineage and it runs fine, but oxygen refuses to boot and just switches the active slot and goes to recovery instead.
I also tried the fastboot rom flashing thing from the thread I linked to in the OP and it's the same thing, just goes back to recovery and wont boot.
P.S. I'm currently copying over /sdcard to an external drive and if I can't figure out how to fix this by the time that's done, I'll just use MsmDownloadTool and start over.
And you are wiping each time before flashing it, right? If it is the case then the download tool is probably the easiest way to go about it, rather than spending days troubleshooting it.
mati11233 said:
And you are wiping each time before flashing it, right? If it is the case then the download tool is probably the easiest way to go about it, rather than spending days troubleshooting it.
Click to expand...
Click to collapse
I've tried it with and without wiping and it always seems to do the same thing either way, works with LOS not with OOS. Thanks for the help! but yeah I think I'm just going to end up using the download tool once everything's over.
Dear oneplus community,
the recent days I wanted to update my stock system and keep my magisk at the same time. But somehow things messed up and lost my root status so I had to go back and flash magisk via twrp again. Since I didn't install twrp as default recovery, I had to boot manually into it.
Here is one of the first issues: the command "fastboot boot recovery.img" had an output line which said that the file is unauthorized. That is quite a common error so I booted into twrp via the all in one tool. Alright here I am in the recovery, ready to install magisk again as usual. Now I am facing the unable to mount vendor, storage and system error, so I fixed it by going to exfat and back to ext4 if I am correct.
Now somehow things messed up even more because at this point I was stuck in a boot loop. I managed to get out of it with the MSM back to stock method.
So in the end I got a stock android 10 oxygenos system I want to have magisk on it again. But when I try to get into the recovery mode sometimes itll work and sometimes it wont. Sometimes the command prompt gives me the unauthorized error message again and sometimes I get stuck in the fastboot mode screen with the oneplus logo.
Eventually I get into the recovery by using various methods e.g. all in one tool, but also here it happenes that the command prompt gives me the unauthorized error.
At this point everything seems to be okay with the installation of magisk (no errors, etc.). But when I'm trying to boot up from the recovery it says that I have no OS installed whether I have magisk installed or not. In a second and third try I additionally tried to flash a rom before installing magisk so I am sure to actually having a OS installed. But it still gives me the same error.
Any ideas how to deal with that, so that I can install magisk on my stock rom properly without having these weird issues.
At this point I'm losing the belief in myself because it shouldn't be that hard at all, since I already rooted my previous phones like mi6 the oneplus 6 haswell..
I will post error codes later.
Thank you.
I actually just started a thread about installing TWRP and magisk yesterday. I am having the same problem installing. I assume it's the versions of each file that I am using that are incompatible, because I am following the instructions as written.
https://forum.xda-developers.com/oneplus-7-pro/help/current-twrp-magisk-unlocked-oneplus-7-t4094307
At this point, since no one seems to know what the problem is, I'm just gonna stay on stock, unlocked bootloader, no root. Which defeats the purpose of even having an unlocked bootloader, but at least I'll have functioning phone. If you need to install an OS on your phone, follow this method.
https://forum.xda-developers.com/oneplus-7-pro/how-to/bricked-oneplus-7-pro-stuck-fastboot-t3972469
This will get you back to factory settings, unlocked bootloader.
+1 here, actually quite confused how to get TWRP properly so it sticks, amd confused about two slots situation.
Now going back to stock via MSM Method. Im in a bootloop/bricked device again.
I'll try to do it one more time and i'll document my steps detailed, so more experienced users can follow the steps better.
Silencex33 said:
Now going back to stock via MSM Method. Im in a bootloop/bricked device again.
I'll try to do it one more time and i'll document my steps detailed, so more experienced users can follow the steps better.
Click to expand...
Click to collapse
Get twrp from here https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3932943. 3.3.1-79
im about to try this on my tmob oneplus 7 pro, any suggestions as to if I should wait for new updates ?