Related
When I attempt to go to Cofface's Baidu page to download his 5.1 TWRP version, I get a message saying the content is no longer available. Specifically, Google Translate shows "Lol, you visit the page does not exist." Does anyone happen to have a copy they're willing to share? Or is there some issue with the 5.1 version that would suggest that I shouldn't use it? If I shouldn't ask for some reason, I apologize. Otherwise, thanks in advance.
https://yadi.sk/d/5YI63uiAhz5UD/Recovery/TWRP
Thanks very much for the link! I think I must have some deeper problems, as every time I flash this recovery (and another version I found in my old downloads), I just get stuck in a boot loop. I was able to use TWRP when I was on B015, but for some reason, I can't get it to work on B106. I'm using:
fastboot flash recovery c:\android\twrp_cn.img
However, like I said I just get stuck in a boot loop. When I flash the stock recovery, everything starts working again.
wpennhokie said:
Thanks very much for the link! I think I must have some deeper problems, as every time I flash this recovery (and another version I found in my old downloads), I just get stuck in a boot loop. I was able to use TWRP when I was on B015, but for some reason, I can't get it to work on B106. I'm using:
fastboot flash recovery c:\android\twrp_cn.img
However, like I said I just get stuck in a boot loop. When I flash the stock recovery, everything starts working again.
Click to expand...
Click to collapse
Did you unlock your bootloader?
Yes, it is. I was able to run TWRP when I was on B015. The phone is rooted, so I've just been using Titanium Backup to back everything up before I wipe the phone, but it would be nice to take a Nandroid backup instead of having to reinstall from TB.
wpennhokie said:
Yes, it is. I was able to run TWRP when I was on B015. The phone is rooted, so I've just been using Titanium Backup to back everything up before I wipe the phone, but it would be nice to take a Nandroid backup instead of having to reinstall from TB.
Click to expand...
Click to collapse
Thats the same problem I have. I used the other twrp recovery https://mega.nz/#!l5kmUByA!41uExNuasZRgLBML9TTSp8myX-_F6UgQZuE2F2BRZUE
This one worked with out boot loops for me. you can give it a shot.
Thanks for the link! I can now get into TWRP. However (sadly), after I leave TWRP, it reboots directly back to TWRP. I've tried rebooting from TWRP into the system and shutting down, but each time, it just goes straight back to TWRP. I was able to boot into fastboot, so I reflashed the boot.img file, but it still goes straight to TWRP. I actually have had this issue before, and I wasn't ever able to figure it out. Any help would be greatly appreciated, as usual.
wpennhokie said:
Thanks for the link! I can now get into TWRP. However (sadly), after I leave TWRP, it reboots directly back to TWRP. I've tried rebooting from TWRP into the system and shutting down, but each time, it just goes straight back to TWRP. I was able to boot into fastboot, so I reflashed the boot.img file, but it still goes straight to TWRP. I actually have had this issue before, and I wasn't ever able to figure it out. Any help would be greatly appreciated, as usual.
Click to expand...
Click to collapse
I had that exact same problem twice on Kangvip B015. When I would restart it would all of a sudden automatically boot into TWRP every time and never boot into the OS. When that happens, in TWRP make a backup, then Fastboot flash the stock ROM (system, boot, cust, recovery, user data etc) then when it boots do a factory data reset, then reroot, flash TWRP and restore from the backup you made. The OS will boot from your backup. I dunno why this happens, maybe it has something to do with with Kernel.
I've tried it a couple of times now, and I'm still not getting it to boot past TWRP once I flash the recovery. It was able to take a backup with TWRP, but when I restored it, I still had to restore the stock recovery before I could boot into the system. At worst, at this point, I can always flash TWRP, take a backup, flash the stock recovery, and then have my system back. It's a few extra steps, but I think I'll do this until I find a custom ROM that I like. I greatly appreciate the help so far.
wpennhokie said:
Thanks for the link! I can now get into TWRP. However (sadly), after I leave TWRP, it reboots directly back to TWRP. I've tried rebooting from TWRP into the system and shutting down, but each time, it just goes straight back to TWRP. I was able to boot into fastboot, so I reflashed the boot.img file, but it still goes straight to TWRP. I actually have had this issue before, and I wasn't ever able to figure it out. Any help would be greatly appreciated, as usual.
Click to expand...
Click to collapse
Reflash the stock b106 recovery and wipe user data and cache, Then reflash twrp recovery and restore your backup. It should boot then.
To follow up, I tried using the updated version of TWRP that you (mtyler7807) posted in the development thread and following the instructions above. I can flash the recovery, boot into it, and take a backup. After that, as long as I boot into the system, I'm fine. However, once I boot into recovery for the first time after that initial backup, it just reboots into TWRP every time. So, right now, I took a backup a day or so ago, and I've just avoided going back in to TWRP again. I have another X2 on the way (a 32GB version), so I'm hoping that I'll have better luck with that one.
wpennhokie said:
To follow up, I tried using the updated version of TWRP that you (mtyler7807) posted in the development thread and following the instructions above. I can flash the recovery, boot into it, and take a backup. After that, as long as I boot into the system, I'm fine. However, once I boot into recovery for the first time after that initial backup, it just reboots into TWRP every time. So, right now, I took a backup a day or so ago, and I've just avoided going back in to TWRP again. I have another X2 on the way (a 32GB version), so I'm hoping that I'll have better luck with that one.
Click to expand...
Click to collapse
By any chance, did you delete anything from the Cust Folder at any point?
ajsmsg78 said:
By any chance, did you delete anything from the Cust Folder at any point?
Click to expand...
Click to collapse
As far as I know, I have not. I did do a complete wipe of everything (except the SD card) at one point using TWRP, but I've always restored the system using the stock system.img file. Right now, the Cust folder is showing five folders, with several more folders/files underneath. Is there a particular file I should be checking for?
wpennhokie said:
As far as I know, I have not. I did do a complete wipe of everything (except the SD card) at one point using TWRP, but I've always restored the system using the stock system.img file. Right now, the Cust folder is showing five folders, with several more folders/files underneath. Is there a particular file I should be checking for?
Click to expand...
Click to collapse
I don't think so. It's weird how some of us have different problems than others. I've had zero issues with TWRP but lately my screen has been going crazy. My touches don't work, things jump it's like my digitizer is messed up but when I restart everything is fine again. So I reloaded everything and the problem went away. I guess I debloated too much last time.
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.
Dear op7p xda community,
A few months ago, I rooted my device and flashed TWRP succesfully. After a stock OTA (still Pie), I lost both. Today, I wanted to re-root and re-flash TWRP. I used mauronofrio's Tool All In One 2.0.0.7 for this. I didn't flash TWRP, but booted it and used that to flash Magisk 19.4. Now, I wanted to see if the rooting process was successful, so I booted the OS. Unfortunately, once it boots and reaches the lockscreen, the "shutting off..." prompt immediately shows and reboots me into the stock recovery.
Edit: I now flashed TWRP after booting TWRP again and ran Magisk to root it again. Unfortunately, the problem persists (only now reboots to TWRP instead of stock recovery). Help is much appreciated!
Can someone help me get my phone to work again? Thanks a lot in advance!
Regards,
Wouty
What version TWRP? Maybe try a different one?
redpoint73 said:
What version TWRP? Maybe try a different one?
Click to expand...
Click to collapse
Thank you for your reply. I am now on TWRP 3.3.1-4 (latest). I have tried to factory reset and wipe the phone in hopes of getting it to start properly again, but now the OS doesn't even boot and immediately reboots me into TWRP. I have now tried to flash 3 different stock, official ROMs, both International and Europe, like OnePlus7ProOxygen_21.O.14_OTA_014_all_1907281611. I used the recommended flashing instructions (flash ROM, flash TWRP, reboot TWRP, flash Magisk) But none of them boot at all. Only TWRP is usable now. I don't know what to do
Wouty said:
Thank you for your reply. I am now on TWRP 3.3.1-4 (latest). I have tried to factory reset and wipe the phone in hopes of getting it to start properly again, but now the OS doesn't even boot and immediately reboots me into TWRP. I have now tried to flash 3 different stock, official ROMs, both International and Europe, like OnePlus7ProOxygen_21.O.14_OTA_014_all_1907281611. I used the recommended flashing instructions (flash ROM, flash TWRP, reboot TWRP, flash Magisk) But none of them boot at all. Only TWRP is usable now. I don't know what to do
Click to expand...
Click to collapse
When it reboots back to TWRP try to format data if that doesn't work then you need to use MSM tool.
boybkol said:
When it reboots back to TWRP try to format data if that doesn't work then you need to use MSM tool.
Click to expand...
Click to collapse
Thanks for your reply. I had indeed wiped data, but that worsened the situation (not booting at all, instead of rebooting once booted). I have now tried this https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424 and it now seems to be booting (booting animation on-going for quite some time now, though). I will keep you posted. If it doesn't work, I'll look into the MSM tool. Thanks for the suggestion!
Wouty said:
I am now on TWRP 3.3.1-4 (latest).
Click to expand...
Click to collapse
That is the latest official TWRP for this device. The official builds don't support Android 10, as decryption is not supported, so that may be part of your problem. The latest unofficial is -70, and I believe you need to use build -65 or later for Android 10.
https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322
---------- Post added at 11:13 AM ---------- Previous post was at 11:12 AM ----------
Wouty said:
Thanks for your reply. I had indeed wiped data, but that worsened the situation
Click to expand...
Click to collapse
Wipe is not the same as format. In TWRP, go to Wipe section, and you will see a button "Format data".
If you are now stuck on a boot loop, try booting into twrp and clearing cache. If you still can't boot, then i recommend downloading the full official rom and flashing it via fastboot. This will remove twrp and u'll end up with stock recovery and everything. Then after that follow proper instructions to install twrp first, then clear cache. Then magisk, and clear cache.
milindpatel63 said:
If you are now stuck on a boot loop, try booting into twrp and clearing cache. If you still can't boot, then i recommend downloading the full official rom and flashing it via fastboot. This will remove twrp and u'll end up with stock recovery and everything. Then after that follow proper instructions to install twrp first, then clear cache. Then magisk, and clear cache.
Click to expand...
Click to collapse
Trying to flash an official ROM via fastboot for a second time did indeed solve the problem for me. Now able to boot. Now backing up everything to make sure I'm able to solve these issues faster in the future. Thanks to all for your input!
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?
Started to go down the Lineage 19.1 route. Despite the warning, I forgot to update firmware to 12, realized this halfway through the flash.
Thought no worries, I will just flash 18.1 again as I still have the files, but now I can't get into recovery. Any booting leads only to the crash dump screen
Is an MSM tool reset the only way?
Now I am pretty much an amateur when it comes to this stuff, but I want to think that I did a lineage19 upgrade on another device I didn't have to do a firmware upgrade.
I downloaded the files a while ago and I definitely read the instructions then, so I can only assume I forgot about the firmware update in the time since.
UPDATE EDIT 11/6: So now I can get into Recovery and have access to an older Lineage Recovery for 18.1 and TWRP but neither allows me to flash any of the Lineage 18.1 OTA files I had extracted from my phone, resulting in a Code:: kInstallDeviceOpenError.
Did I mess up the firmware by trying to install 19.1 without updating the firmware?
I am trying to preserve some files so don't want to wipe the phone completely if at all possible.
LOSXDA98 said:
Started to go down the Lineage 19.1 route. Despite the warning, I forgot to update firmware to 12, realized this halfway through the flash.
Thought no worries, I will just flash 18.1 again as I still have the files, but now I can't get into recovery. Any booting leads only to the crash dump screen
Is an MSM tool reset the only way?
Now I am pretty much an amateur when it comes to this stuff, but I want to think that I did a lineage19 upgrade on another device I didn't have to do a firmware upgrade.
I downloaded the files a while ago and I definitely read the instructions then, so I can only assume I forgot about the firmware update in the time since.
Click to expand...
Click to collapse
Try to boot the recovery file from bootloader mode with fastboot.
LOSXDA98 said:
Started to go down the Lineage 19.1 route. Despite the warning, I forgot to update firmware to 12, realized this halfway through the flash.
Thought no worries, I will just flash 18.1 again as I still have the files, but now I can't get into recovery. Any booting leads only to the crash dump screen
Is an MSM tool reset the only way?
Now I am pretty much an amateur when it comes to this stuff, but I want to think that I did a lineage19 upgrade on another device I didn't have to do a firmware upgrade.
I downloaded the files a while ago and I definitely read the instructions then, so I can only assume I forgot about the firmware update in the time since.
Click to expand...
Click to collapse
You can manually update your firmware and flash the ROM with fastboot.
This thread should have been started in the 8T Q&A forum.
Depending on what you've done, you can sometimes switch slots in bootloader and then boot recovery.
But as recommended by the other responses, reflashing in bootloader is also a good option.
If neither work, then the MSM Tool is the best option to get things going again.
The problem is I can't get into fastboot mode from the hardware buttons, it still results in crash dump screen. Trying to get into recovery the same way results in the same.
LOSXDA98 said:
The problem is I can't get into fastboot mode from the hardware buttons, it still results in crash dump screen. Trying to get into recovery the same way results in the same.
Click to expand...
Click to collapse
No fastboot means the only solution is the MSM Tool. You should feel lucky that you are not on the 10 Pro.
Can I use MSM tool to reflash lineage or is the only option a factory reset?
Not sure if there is any other way to access the data on the device.
LOSXDA98 said:
Can I use MSM tool to reflash lineage or is the only option a factory reset?
Not sure if there is any other way to access the data on the device.
Click to expand...
Click to collapse
I don't know any. Even the firehose readback feature of MSM Tool doesn't allow to backup the data partition.
LOSXDA98 said:
The problem is I can't get into fastboot mode from the hardware buttons, it still results in crash dump screen. Trying to get into recovery the same way results in the same.
Click to expand...
Click to collapse
You can't go straight to fastboot from Crash Dump mode.
You must first get out of Crash Dump using power + vol up (see https://community.oneplus.com/wap/thread/1316587) and then use the keys to get into fastboot.
If you wait too long after getting out of Crash Dump the phone tries to boot again and you'll end up back in CD.
I can get it to shut down using the volume up and power.
So starting from a completely shutdown phone, and holding Volume up and power to go to fast boot, results in crash dump.
Holding volume up and releasing power when the logo appears also results in a crash dump.
Lastly holding both Volume up and Power the entire time results in crash dump.
If there is another combination or I am doing something wrong, I am happy to try again.
Sadly I'm out of ideas.
Well I managed to get into fastboot. I had to hold all buttons down until it loaded.
So I was able to reinstall TWRP, thinking I could use the access to the root to reinstall OS 18.1 from the OTA folder. I just get errors Failed to Mount, 'system root' invalid and 'vendor.'
So now I cannot reinstall 18.1.
Trying to use Lineage Recovery it would not even start the install process.
So now I am not sure what I should try next
LOSXDA98 said:
Well I managed to get into fastboot. I had to hold all buttons down until it loaded.
So I was able to reinstall TWRP, thinking I could use the access to the root to reinstall OS 18.1 from the OTA folder. I just get errors Failed to Mount, 'system root' invalid and 'vendor.'
So now I cannot reinstall 18.1.
Trying to use Lineage Recovery it would not even start the install process.
So now I am not sure what I should try next
Click to expand...
Click to collapse
The first thing I would do is backup important data if you have any using adb from TWRP. Then you could factory reset with MSM Tool or try to flash LOS from fastboot.
Pictures and texts are the important files and to my knowledge TWRP doesn't back those up
I am trying to figure out what the failed install might have corrupted and what I can reflash.
Do I need to reflash dtbo and vbm?
Can I use the newer 19.1 recovery with older OS files?
None of the older 18.1 official build files seem to exist online anymore.
Did I somehow switch partitions, and how would I know this?
LOSXDA98 said:
Pictures and texts are the important files and to my knowledge TWRP doesn't back those up
I am trying to figure out what the failed install might have corrupted and what I can reflash.
Do I need to reflash dtbo and vbm?
Can I use the newer 19.1 recovery with older OS files?
None of the older 18.1 official build files seem to exist online anymore.
Did I somehow switch partitions, and how would I know this?
Click to expand...
Click to collapse
You can use adb to backup files in the internal sdcard while being in TWRP.
Regarding switching partitions, in the reboot menu of TWRP you can see which slot you have activate and switch it.
Does that include texts?
What slot should I be installing in?
I want to say active slot was A
LOSXDA98 said:
Does that include texts?
What slot should I be installing in?
I want to say active slot was A
Click to expand...
Click to collapse
With texts do you mean whatsapp messages or sms?
I would try to install in both slots (first A and if it doesn't work B)
Sms
LOSXDA98 said:
Sms
Click to expand...
Click to collapse
For sure a backup of the data partition will include them but the problem is to be able to restore them afterwards. You can try to find a guide on the internet like this (although this one is old and may be outdated).