I was downloading a OTA update the other day & in preparation I thought I would go ahead & uninstall Magisk. Magisk asked me if I wanted to restore images or uninstall I just uninstalled, not ever having made a image before I didn't know what it was talking about.
The phone rebooted once then booted again into TWRP, I can't get back into my phones OS.
Later I couldn't get back into TWRP so I had to boot using the fastboot commands in Windows. I was able to see & "Backup" the contents of my phone to an external drive.
Now how do I get back into my phone like normal?
Do I need to flash an image or I've seen other threads they wipe the data & there phone boots?
Please advise.
Thank you
justinstrack said:
I was downloading a OTA update the other day & in preparation I thought I would go ahead & uninstall Magisk. Magisk asked me if I wanted to restore images or uninstall I just uninstalled, not ever having made a image before I didn't know what it was talking about.
The phone rebooted once then booted again into TWRP, I can't get back into my phones OS.
Later I couldn't get back into TWRP so I had to boot using the fastboot commands in Windows. I was able to see & "Backup" the contents of my phone to an external drive.
Now how do I get back into my phone like normal?
Do I need to flash an image or I've seen other threads they wipe the data & there phone boots?
Please advise.
Thank you
Click to expand...
Click to collapse
First of all, no need to uninstall Magisk - unnecessary and waste of time.
Once in TWRP (fastboot boot twrp.img, or via your phone if you still can) - flash OOS OTA update (as that was what you were trying to do).
Then flash TWRP, reboot TWRP. Now you can flash Magisk again (so you get root, since you removed it for some reason).
Everything should be fine.
only4dank said:
First of all, no need to uninstall Magisk - unnecessary and waste of time.
Once in TWRP (fastboot boot twrp.img, or via your phone if you still can) - flash OOS OTA update (as that was what you were trying to do).
Then flash TWRP, reboot TWRP. Now you can flash Magisk again (so you get root, since you removed it for some reason).
Everything should be fine.
Click to expand...
Click to collapse
Unfortunately now I can't get the "fastboot boot twrp.img" to boot into twrp? FAILED authentication.
Now what?
Fastboot devices work & the reboot function works, just can't boot twrp.img. I've seen somewhere I can maybe force boot the device idk if it will work. damn
justinstrack said:
Unfortunately now I can't get the "fastboot boot twrp.img" to boot into twrp? FAILED authentication.
Now what?
Fastboot devices work & the reboot function works, just can't boot twrp.img. I've seen somewhere I can maybe force boot the device idk if it will work. damn
Click to expand...
Click to collapse
Sorry to hear. You are going to have to provide logs of what commands you are typing into terminal, and what is the output.
So are you in TWRP or not. I literally have no idea what is going on with your device or what you are doing.
Next time, maybe check guides in this forum of how to do what you are doing.
Randomly uninstalling/installing/flashing/issuing commands via terminal/random backup and restores/etc.... does not sit well with android devices.
I'll try another pc tonight.
If you can get back to twrp you need to flash magik to boot normally
Still can't back into twrp. Failedremote: failed to load/authenicate boot image: Load error.)
Tried a different computer. Tried deleting my fastboot files on PC then copying them from a backup thinking I modified the twrp image wrong thinking this unmotified version would work, still nothing.
Can I get some advice links to guides. Thank you.
justinstrack said:
Still can't back into twrp. Failedremote: failed to load/authenicate boot image: Load error.)
Tried a different computer. Tried deleting my fastboot files on PC then copying them from a backup thinking I modified the twrp image wrong thinking this unmotified version would work, still nothing.
Can I get some advice links to guides. Thank you.
Click to expand...
Click to collapse
Still.... what are you typing into terminal... take a screen shot .....
ARE YOU SURE you are typing 'fastboot boot twrp.img' - BOOT, not FLASH!!!???
I'm now able to boot into twrp. Had to use fastboot --set-active=a. Worked great. Left it like that at home. I'm at work now.
What next?
justinstrack said:
I'm now able to boot into twrp. Had to use fastboot --set-active=a. Worked great. Left it like that at home. I'm at work now.
What next?
Click to expand...
Click to collapse
I would start by reading forum page 1 information about what you are trying to do.
I already explained to you the order to flash to make things work.
If that is not enough, once again, go learn what you are trying to do (via the forum thread).
You will probably save yourself these types of situations in the future if you understand what you are doing.
Good luck.
Everything is FULLY Operational Thank You. What a experience but Ive learned.
justinstrack said:
Everything is FULLY Operational Thank You. What a experience but Ive learned.
Click to expand...
Click to collapse
And not even a single thanks button hit or anything... Weird flex, but OK
I'm so sorry LOL. found it. Have a good day xda forum members, I found the button. THANK YOU
Related
So i recently tried flashing a new kernel and for whatever reason my pixel 2 did not like that at all. Upon reboot after flashing it now just goes into the download mode where i have the option to reboot bootloader go into recovery and go into download mode. Normally not a big issue at all but this time when i go to load into recovery or load into Download mode its says Operation Denied. Upon a reboot or trying to reboot into safe mode it says ERROR: Slot unbootable: Load Error. Will ADB still work to flash this? not really sure what to do at this moment.
EDIT: Solved it by using Fastboot and flashing the stock firmware without the -w so far everything is back to normal....know to get that dern kernel again
gears177 said:
So i recently tried flashing a new kernel and for whatever reason my pixel 2 did not like that at all. Upon reboot after flashing it now just goes into the download mode where i have the option to reboot bootloader go into recovery and go into download mode. Normally not a big issue at all but this time when i go to load into recovery or load into Download mode its says Operation Denied. Upon a reboot or trying to reboot into safe mode it says ERROR: Slot unbootable: Load Error. Will ADB still work to flash this? not really sure what to do at this moment.
Click to expand...
Click to collapse
First off, does fastboot recognize the device?
DuckRuckus said:
First off, does fastboot recognize the device?
Click to expand...
Click to collapse
It does not under adb devices nothing shows up. In device manager it does show up as Android bootloader interface
gears177 said:
It does not under adb devices nothing shows up. In device manager it does show up as Android bootloader interface
Click to expand...
Click to collapse
ADB=system. Fastboot=boot. You can't boot your phone, so you're not in android, thus no ADB devices. Type "fastboot devices" and see if it's recognized.
DuckRuckus said:
ADB=system. Fastboot=boot. You can't boot your phone, so you're not in android, thus no ADB devices. Type "fastboot devices" and see if it's recognized.
Click to expand...
Click to collapse
Ah nice didnt even realize its recognized under fastboot ive tried flashing the stock recovery but it just gives me an error
gears177 said:
Ah nice didnt even realize its recognized under fastboot
Click to expand...
Click to collapse
Good news! So, your best bet at this point would be to re-flash your current factory image, with /w removed. If you still want that same kernel, flash it before Magisk.
Just out of curiosity, what method did you use to flash it in the first place?
DuckRuckus said:
Good news! So, your best bet at this point would be to re-flash your current factory image, with /w removed. If you still want that same kernel, flash it before Magisk.
Just out of curiosity, what method did you use to flash it in the first place?
Click to expand...
Click to collapse
Flashed it through twrp aroma installer.
What does the -w do in the fastboot command just curious
Nevermind got it flag responsible for deleting userdata thanks alot for the help appreciate your time
gears177 said:
Flashed it through twrp aroma installer.
What does the -w do in the fastboot command just curious
Click to expand...
Click to collapse
It wipes all your data, that's why you remove it from the flash-all.bat script, unless you need to perform a full wipe. Telperion has an excellent guide for installing the lastest software, if you haven't already read it.
I've heard users having back luck flashing kernels in TWRP, as the kernel has something to do with recovery. I always use the method of booting the TWRP image in fastboot, use ADB to push the files to /tmp, and then do an ADB shell TWRP install of those files. TWRP, kernel, then magisk, in that order. I always reinstall all three, just to be on the safe side, and have never had any issues. Takes a little while, but not as long as redoing the whole freaking thing:silly:
Looks like you figured it out, before I finished my reply
So today my new One Plus 6 arrived. I tested it out for a bit made sure everything seemed to be working ok.
Then I unlocked bootloader, flashed twrp, magisk, all without issue. (I followed a guide I found on google) While setting everything up, I noticed that there was an update avaliable. So I installed that and got a message that the update will remove root. I thought "ok, i'll just have to do that again after. Update installed, rebooted device to recovery and realize TWRP is also gone after the update. So then I rebooted again to the bootloader and do fastboot devices command on my pc. Phone is there. Next I do the fastboot flash boot twrp.img command.
Sending.. Writing.. Finished... But I was still on the bootloader on the phone. I tried it a couple more times with no result. Restarted the phone only to boot into TWRP now. I thought to myself "hmm I'm not sure that's what's supposed to happen" but I continued to flash twrp.zip anyway. Rebooted the device.. TWRP booted again. Tried rebooting a couple more times with the same result.
Now, maybe this is where I messed things up more seriously. I'll also mention I foolishly didn't perform a backup on TWRP before doing all this. Not sure what to do, I flashed magisk as well. And I tried rebooting system, then when that didn't work I think I rebooted "slot B' for some reason.... After that it would only show the oneplus boot animation for a seemingly indefinite period of time.
I found I could get int the bootloader menu by holding vol up and power. Tried flashing TWRP, seemed to work on my computer's end but didn't boot recovery on phone. I rebooted into recovery from bootloader menu, brought me to endless oneplus boot animation again. Selecting start on the boot loader booted to TWRP. From there I rebooted back to slot A. Now it boots straight into TWRP.
I'm not sure what went wrong. I've rooted, installed various roms, etc on previous devices. Never had any issues before. But as I'm sure you can tell I don't really know what I'm doing. Does anyone have any advice? Thanks.
Your not supposed to fastboot flash the twrp, youre supposed to fastboot boot it. Just reflash stock boot.img and you'll be good
usernameisausername said:
I'm not sure what went wrong. I've rooted, installed various roms, etc on previous devices. Never had any issues before. But as I'm sure you can tell I don't really know what I'm doing. Does anyone have any advice? Thanks.
Click to expand...
Click to collapse
A number of things work differently on this phone. Don't assume any of your previous knowledge transfers over. There is a steep learning curve.
Stay away from random guides on Google. There are reliable guides here that, if you follow them to the letter, will keep you out of trouble.
fastboot flash boot [.IMG]
Is the issue. Should be
fastboot boot [.IMG]
On www.twrp.me/Devices you'll find the OnePlus 6 plus a corresponding how-to, directly from the source.
Your best bet:
1. Download the full ROM zip from either OnePlus directly or one of the links here on XDA.
2. Download latest TWRP files from twrp.me
3. fastboot boot [.IMG]
4. If in TWRP, connect to your PC and send the ROM over to your phone (MTP should work I think. Else, just ADB push it)
5. Flash the ROM in TWRP as you would flash any other ROM.
6. Should work, your system is now back to stock (also recovery). Let it boot once to be sure and then retry magisk but with the right fastboot commands.
To flash TWRP permanently, move the installer.zip you find on TWRP.me to your phone, fastboot boot the .IMG and flash the installer.zip in recovery.
Let me know if it worked
schwarzerfleck said:
4. If in TWRP, connect to your PC and send the ROM over to your phone (MTP should work I think. Else, just ADB push it))
Click to expand...
Click to collapse
MTP is disabled on most versions of twrp including official. There is an unofficial version with MTP working though it's a bit wonky.
iElvis said:
MTP is disabled on most versions of twrp including official. There is an unofficial version with MTP working though it's a bit wonky.
Click to expand...
Click to collapse
Yeah that's why I suggested the ADB push
schwarzerfleck said:
Yeah that's why I suggested the ADB push
Click to expand...
Click to collapse
So I'm having the same issue as OP currently and am somewhat a noob to this. I'm stuck booting into recovery, how do I adb push to the phone? its not showing up in adb devices at all
Eilermoon said:
So I'm having the same issue as OP currently and am somewhat a noob to this. I'm stuck booting into recovery, how do I adb push to the phone? its not showing up in adb devices at all
Click to expand...
Click to collapse
If you have USB debugging enabled, it's probably a driver problem. Windows 10 has issue with driver signatures and there's a setting that needs to be disabled. Do a search as it's been discussed (I use a Mac so I'm not certain what).
iElvis said:
If you have USB debugging enabled, it's probably a driver problem. Windows 10 has issue with driver signatures and there's a setting that needs to be disabled. Do a search as it's been discussed (I use a Mac so I'm not certain what).
Click to expand...
Click to collapse
Thanks for the info! If anyone has a source for this, that'd be awesome
Own the OPP6; Rooted, on OxygenOS 5.18.
Went to install the newest TWRP (was going to install XXX no limits), when asked where to install it to, accidentally, without thinking, hit install to Boot.
Problems.
I can get into fastboot, the PC sees the phone in fastboot.
Have tried to flash a recovery image and similar, got an error saying: FAILED (remote: (recovery_b) No such partition).
Just want to get the phone booting again, wipe the whole thing start over, from fastboot.
Any help appreciated.
https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892
Thank you, the tool worked like a charm.
BTW: I did search and find other "methods" but none of them worked
noncomjd said:
Own the OPP6; Rooted, on OxygenOS 5.18.
Went to install the newest TWRP (was going to install XXX no limits), when asked where to install it to, accidentally, without thinking, hit install to Boot.
Problems.
I can get into fastboot, the PC sees the phone in fastboot.
Have tried to flash a recovery image and similar, got an error saying: FAILED (remote: (recovery_b) No such partition).
Just want to get the phone booting again, wipe the whole thing start over, from fastboot.
Any help appreciated.
Click to expand...
Click to collapse
What you should have done was fastboot boot twrp.img. which would start twrp, then you could have used the installer in to install twrp on phone. After that you would have to installed stock or custom kernel.
MrSteelX said:
What you should have done was fastboot boot twrp.img. which would start twrp, then you could have used the installer in to install twrp on phone. After that you would have to installed stock or custom kernel.
Click to expand...
Click to collapse
That is exactly what I wanted to do.
I could get into TWRP, but I couldn't see the phone on the PC and couldn't move files (ROM) to the phone (although fastboot was working and I could see the device using adb) but I couldn't figure out how to have TWRP look for or find the ROM on the PC.
There's no recovery partition on A/B phones remember.
RusherDude said:
There's no recovery partition on A/B phones remember.
Click to expand...
Click to collapse
Thanks for that. and that explains a few things and explains why when I installed TWRP, I didn't see the recovery option. Doesn't pardon my hitting install to Boot.
Just thought of another Q, if there is no recovery partition, where is the OEM recovery stored? (I figured the lack of a recovery partition is why TWRP gets overwritten if installed without a custom ROM)
I did a quick read on that, it seems really interesting and may be of some use as soon as I learn more.
I've got so much to learn about this. I keep meaning to take time to begin, but stuff comes up and boom more changes.
I've got to do more reading to take advantage of that.
@MrSteelX mentioned that I could have used TWRP to install a ROM from the PC.
Is this what is referred to as "sideloading". I've been looking for some info on this and haven't really come across much that is any good.
Are there any available guides that anyone can point to so I can learn about using TWRP that way?
noncomjd said:
Thanks for that. and that explains a few things and explains why when I installed TWRP, I didn't see the recovery option. Doesn't pardon my hitting install to Boot.
Just thought of another Q, if there is no recovery partition, where is the OEM recovery stored? (I figured the lack of a recovery partition is why TWRP gets overwritten if installed without a custom ROM)
I did a quick read on that, it seems really interesting and may be of some use as soon as I learn more.
I've got so much to learn about this. I keep meaning to take time to begin, but stuff comes up and boom more changes.
I've got to do more reading to take advantage of that.
@MrSteelX mentioned that I could have used TWRP to install a ROM from the PC.
Is this what is referred to as "sideloading". I've been looking for some info on this and haven't really come across much that is any good.
Are there any available guides that anyone can point to so I can learn about using TWRP that way?
Click to expand...
Click to collapse
In twrp, you go to advance/sideload. Twrp then waits for adb sideload to push file to phone then auto flashes file.
In your case, you would sideload rom to flash and have been go to go.
noncomjd said:
Own the OPP6; Rooted, on OxygenOS 5.18.
Went to install the newest TWRP (was going to install XXX no limits), when asked where to install it to, accidentally, without thinking, hit install to Boot.
Problems.
I can get into fastboot, the PC sees the phone in fastboot.
Have tried to flash a recovery image and similar, got an error saying: FAILED (remote: (recovery_b) No such partition).
Just want to get the phone booting again, wipe the whole thing start over, from fastboot.
Any help appreciated.
Click to expand...
Click to collapse
If you have working fastboot mode and getting detected via fastboot then
fastboot flashable stock rom via fastboot mode.
U don't have to do anything just downloaded zip file unzip it any folder u want. Connect u r phone to. Computer in fastboot mode
Then go to that folder and just click flash all bat waut for 10to 15 min and then phone boots in working oos.
(all data will be get wipes after this)
Link
https://www.google.co.in/amp/s/foru...m-stock-fastboot-roms-oneplus-6-t3796665/amp/
MrSteelX said:
In twrp, you go to advance/sideload. Twrp then waits for adb sideload to push file to phone then auto flashes file.
In your case, you would sideload rom to flash and have been go to go.
Click to expand...
Click to collapse
Thanks.
I will give this a try. After I learn a little more about the A/B partitions & recovery on this phone, I want to try one on the custom ROMs.
pankspoo said:
If you have working fastboot mode and getting detected via fastboot then
fastboot flashable stock rom via fastboot mode.
U don't have to do anything just downloaded zip file unzip it any folder u want. Connect u r phone to. Computer in fastboot mode
Then go to that folder and just click flash all bat waut for 10to 15 min and then phone boots in working oos.
(all data will be get wipes after this)
Link
https://www.google.co.in/amp/s/foru...m-stock-fastboot-roms-oneplus-6-t3796665/amp/
Click to expand...
Click to collapse
Thanks for the link/guide. I had been trying an iteration of this (and the guide) but after reading your link, it too explains some things. I was trying to restore a Stock ROM from fastboot according to your link:
Things are changing with the advent of project treble. OnePlus will no longer release ROMs flashable via recovery (either stock or twrp) because is no more needed. The updates will be done on the slot not used for example if you are using slot a the update will be installed on slot b and the slot b will be set as default. If you brick and you are in bootloop how you can restore the rom? You can't with Stock ROM you have, because the zip can be only installed via Update Engine, so what can you do? Flash a stock rom via fastboot. I have extracted all images from the stock zip and i have made a new zip with the Fastboot ROM with a flash-all.bat included. This will work only if your bootloader is unlcoked. This will erase all your data and will wipe
I download and was trying to use the stock ROMs, I didn't see any bats, and now I know why.
Lots more reading to do. I love doing playing with this stuff, but trying to learn & keep up with things burns time, which most days I don't have.
This is the longest I've ever been on a stock OS (6 weeks? got the phone right after its release) although it's rooted (can never leave things completely alone).
noncomjd said:
Thanks for the link/guide. I had been trying an iteration of this (and the guide) but after reading your link, it too explains some things. I was trying to restore a Stock ROM from fastboot according to your link:
Things are changing with the advent of project treble. OnePlus will no longer release ROMs flashable via recovery (either stock or twrp) because is no more needed. The updates will be done on the slot not used for example if you are using slot a the update will be installed on slot b and the slot b will be set as default. If you brick and you are in bootloop how you can restore the rom? You can't with Stock ROM you have, because the zip can be only installed via Update Engine, so what can you do? Flash a stock rom via fastboot. I have extracted all images from the stock zip and i have made a new zip with the Fastboot ROM with a flash-all.bat included. This will work only if your bootloader is unlcoked. This will erase all your data and will wipe
I download and was trying to use the stock ROMs, I didn't see any bats, and now I know why.
Lots more reading to do. I love doing playing with this stuff, but trying to learn & keep up with things burns time, which most days I don't have.
This is the longest I've ever been on a stock OS (6 weeks? got the phone right after its release) although it's rooted (can never leave things completely alone).
Click to expand...
Click to collapse
I have to unzip the downloaded fastboot ROM at any folder on computer and open that folder u will see named [flash all bat]
Now connect phone in fastboot mode to computer and just click [flash all bat] file
noncomjd said:
Thanks for that. and that explains a few things and explains why when I installed TWRP, I didn't see the recovery option. Doesn't pardon my hitting install to Boot.
Just thought of another Q, if there is no recovery partition, where is the OEM recovery stored? (I figured the lack of a recovery partition is why TWRP gets overwritten if installed without a custom ROM)
I did a quick read on that, it seems really interesting and may be of some use as soon as I learn more.
I've got so much to learn about this. I keep meaning to take time to begin, but stuff comes up and boom more changes.
I've got to do more reading to take advantage of that.
@MrSteelX mentioned that I could have used TWRP to install a ROM from the PC.
Is this what is referred to as "sideloading". I've been looking for some info on this and haven't really come across much that is any good.
Are there any available guides that anyone can point to so I can learn about using TWRP that way?
Click to expand...
Click to collapse
"recovery" (what's left of it... wipe and mostly nothing else) is inside the boot partition. TWRP on those devices is installed into the boot partition (NOT overwriting the boot partition, but into the "ramdisk", a part of the kernel where OEM recovery resides and where TWRP, Magisk, Xposed and all the mods do their stuff on the kernel. On a phone with A/B partitions, you have to fastboot BOOT twrp, and then you have to flash the installer zip, you should never ever flash the image to any partition since there isn't any.
RusherDude said:
"recovery" (what's left of it... wipe and mostly nothing else) is inside the boot partition. TWRP on those devices is installed into the boot partition (NOT overwriting the boot partition, but into the "ramdisk", a part of the kernel where OEM recovery resides and where TWRP, Magisk, Xposed and all the mods do their stuff on the kernel. On a phone with A/B partitions, you have to fastboot BOOT twrp, and then you have to flash the installer zip, you should never ever flash the image to any partition since there isn't any.
Click to expand...
Click to collapse
Thanks for the information.
and this is what I did, originally I thought I had accidentally selected the wrong partition, but it seems since there is no recovery partition, I did it wrong from the start.
Q: I'm guessing this is why when you do load TWRP (the correct way, which I did once, following a guide) without a custom ROM (still using Oxygen OS) that the OEM recovery overwrites TWRP or the OEM recovery is called up at the next reboot into recovery?
Q: I understand, at least in theory the benefit of the A/B partitions, what is the benefit of eliminating the recovery partition other than giving more control of the phone to the OEM and OS? Is this setup limited to the stock kernel or mandated to be copied by any potential replacement kernels (this information is new to me, I haven't yet read up on kernels).
Hey all,
I've got an issue with my phone. I can't get into recovery.
My phone had Bluspark TWRP, was rooted with magisk and was running XXX.
I then updated to new version of OOS via recovery and stupidly re-booted the phone without flashing magisk again.
I then tried to enter recovery to flash magisk and Bluspark was gone.
I've tried re-flashing recovery via terminal, but the phone won't let me.
When I type in 'fastboot devices' in terminal, it says my phone is connected.
As soon as I type in 'fastboot boot twrp-3.2.3-x_blu_spark_v9.86_op6.img' and execute the command, the phone exits fastboot mode and there is some writing in the top left of the screen that says, 'press any key to exit'.
This is the method I used to flash my phone the first time, so I have no idea why it won't work.
Any ideas?
Thanks
EDIT: I'm on 9.01
You needed to flash recovery prior to rebooting the first time.
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
Ducter said:
You needed to flash recovery prior to rebooting the first time.
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
Click to expand...
Click to collapse
What can I do now that it is too late?
If I factory reset, will I be able to flash recovery again?
cubic25 said:
What can I do now that it is too late?
If I factory reset, will I be able to flash recovery again?
Click to expand...
Click to collapse
The link I posted is the only way I could get my phone back functioning after I first started messing with the OnePlus 6 and it's a/b partitioning. It's basically starting over, the a/b setup works fine so long as we educate ourselves first..I had been flashing and tinkering since 08 and stupidly thought it was all the same. Now I know.
Hey Guys,
So my idiot brain decided to mess around with substatum themes after I updated and rerooted my OP7P. I rooted with magisk but forgot to put TWRP recovery on.
Anyways, got the phone semi bricked when applying one of the overlays. The phone boots and I can see my lock screen wallpaper but the screen is just flashing on/off.
I cant use the fingerprint or pin to get it. Is there a way for me to backup my pictures and data or somehow remove substratum?
Biggest problem is that for whatever reason, the update revoked my ADB authorization so it looks like I cant do anything with ADB.
If someone has any way to salvage my situation, please reply. Factory reset is my last resort due to no backup.
Thank You
Try booting into TWRP and using ADB there.
Well boot to fastboot. Flash twrp there and then reboot to twrp.
Flash rescue zip and you should be good to go
tech_head said:
Try booting into TWRP and using ADB there.
Click to expand...
Click to collapse
pranacrockz said:
Well boot to fastboot. Flash twrp there and then reboot to twrp.
Flash rescue zip and you should be good to go
Click to expand...
Click to collapse
Problem is, I dont have TWRP recovery flashed, looks like it reverted to stock recovery after I updated. I rooted with Magisk which does not put TWRP back. I forgot to flash it after.
I also probably wont be able to do anything in fastboot either because the update removed the ADB Authorization and I am unable to accept it since my screen doesnt respond to anything, I will attempt this route though.
Edit: No go. ADB vendor key not set and I dont think I will be able to accept it on my device due to unresponsive screen
morphius88 said:
Problem is, I dont have TWRP recovery flashed, looks like it reverted to stock recovery after I updated. I rooted with Magisk which does not put TWRP back. I forgot to flash it after.
I also probably wont be able to do anything in fastboot either because the update removed the ADB Authorization and I am unable to accept it since my screen doesnt respond to anything, I will attempt this route though.
Edit: No go. ADB vendor key not set and I dont think I will be able to accept it on my device due to unresponsive screen
Click to expand...
Click to collapse
Fastboot doesn't need adb.
Switch off the phone, reboot to fastboot.
Then type fastboot boot (filelocation of twrp.img)
Then your phone will boot to twrp.
Flash rescue.zip.
If it is still a no go. Then use msm tool
pranacrockz said:
Fastboot doesn't need adb.
Switch off the phone, reboot to fastboot.
Then type fastboot boot (filelocation of twrp.img)
Then your phone will boot to twrp.
Flash rescue.zip.
If it is still a no go. Then use msm tool
Click to expand...
Click to collapse
Rebooted to fastboot, entered the PIN but Fastboot is a no go. Just keeps saying <waiting for any device> and nothing happens. Would that be because the authorization keys were not accepted after the update?
I am downloading the MSM Tool and will try that if I cant get it to work with fastboot. Will update if it works.
Thanks for suggestions
Ended up using the MSM tool. Did not know it wipes data and also put me back to Android 9.
Oh well, lesson learned. Gotta make monthly backups, make sure twrp is installed and working before messing around with substatrum.
Thanks for the help.