Hello,
I encountered a annoying problem with my oneplus 6 tonight, a device i am fairly new with, previously owning a oneplus 3t.
While restoring a TWRP backup out of lazyness i screwed up something in my device to the point that it was booting in TWRP on the second try (the first was just a bootloop).
I said ok, there's something wrong, lets do that again and booted in TWRP (blu_spark, latest). There, i was not asked about any decryption password and obviously everything was encrypted.
I re-installed everything now using MSM tool and re-rooted but this is a painful process that takes time.
Anyone encountered that?
I am, and was on latest OOS with stock kernel, latest TWRP blu_spark (the stock one gives me QUALCOMM CrashDump when trying to boot from fastboot in it), rooted with magisk (latest 18.1) and using magisk custom rom on top of stock (XXX_nolimits, latest).
Any of you encoutered this issue?
Thanks!
0xPraeT0Rian said:
Hello,
I encountered a annoying problem with my oneplus 6 tonight, a device i am fairly new with, previously owning a oneplus 3t.
While restoring a TWRP backup out of lazyness i screwed up something in my device to the point that it was booting in TWRP on the second try (the first was just a bootloop).
I said ok, there's something wrong, lets do that again and booted in TWRP (blu_spark, latest). There, i was not asked about any decryption password and obviously everything was encrypted.
I re-installed everything now using MSM tool and re-rooted but this is a painful process that takes time.
Anyone encountered that?
I am, and was on latest OOS with stock kernel, latest TWRP blu_spark (the stock one gives me QUALCOMM CrashDump when trying to boot from fastboot in it), rooted with magisk (latest 18.1) and using magisk custom rom on top of stock (XXX_nolimits, latest).
Any of you encoutered this issue?
Thanks!
Click to expand...
Click to collapse
All you need to do is backup data. There are multiple threads explaining nandroid backup and restore. Just install OOS and TWRP, reboot recovery and flash all mods that you use, then restore data only and reboot.
Related
Droid Turbo (quark) is the device in question...
So over the weekend I attempted to boot into TWRP recovery and TWRP ended up in a bootloop. Never had this happen before (version 3.1.1-0 is installed). Attempted to reinstall version using Flashify, however Flashify hung up and stalled when I'd click on "search for file to flash" or whatever it's called. So I (successfully) flashed TWRP version 3.2.1-0 using the TWRP app, rebooted to recovery, and TWRP still bootlooped (showed that version 3.2.1-0 was installed). Using TWRP app I (successfully) reflashed the 3.1.1-0 version .img file I had saved from the first time I flashed TWRP months ago, rebooted to recovery, and TWRP still bootlooped (showed that version was again 3.1.1-0).
I'm fairly certain that some rogue apps I installed caused the issue. It's the only thing I can think of as to why TWRP is messed up. I've uninstalled the rogue apps with Titanium Backup, TWRP still bootloops.
Any ideas on what I've botched, and how to unbotch it? Phone otherwise works as it should booting up normally, running normally, etc. I'm just at a loss for any future tinkering I want to do since I can't get into TWRP to make or restore backups.
Hi guys,
so since a few days I have a really strange problem. No matter what I do, everytime I flash the TWRP installer after the rom I get stuck in a recovery loop.
I found out that if I do not install TWRP it will boot into the ROMs recovery. If I do a factory reset (erase everything) in there it will boot again just fine into the system.
If I install TWRP afterwards, for example through Magisk it will stay and work without any problem.
I've also tried a restore with the MSMDownloadTool multiple times (which worked without any problem) however after that, again, everytime I want to install a ROM and flash the TWRP installer afterwards
I'm stuck in the recovery.
I've never had this problem before and am at my wits end, because I just can't figure out what is causing this problem.
Did anyone of you also had this problem and found a way to resolve it? Any help would be much appreciated!
Note: I'm using this TWRP (3.3.1-71) -> https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322
Observed same behavior.
ROM: 10.0.1 GM21AA
TWRP: 3.3.1-71 q
Magisk: v20.1
EDIT: seems the problem is related to F2FS, after formatting data back to ext4 my phone booted.
aqua_hopps said:
Observed same behavior.
ROM: 10.0.1 GM21AA
TWRP: 3.3.1-70 q
Magisk: v20.1
EDIT: seems the problem is related to F2FS, after formatting data back to ext4 my phone booted.
Click to expand...
Click to collapse
Good to know, however in that case it seems that my problem is unrelated to this, as I have never used F2FS.
TheExoduser said:
Hi guys,
so since a few days I have a really strange problem. No matter what I do, everytime I flash the TWRP installer after the rom I get stuck in a recovery loop.
I found out that if I do not install TWRP it will boot into the ROMs recovery. If I do a factory reset (erase everything) in there it will boot again just fine into the system.
If I install TWRP afterwards, for example through Magisk it will stay and work without any problem.
I've also tried a restore with the MSMDownloadTool multiple times (which worked without any problem) however after that, again, everytime I want to install a ROM and flash the TWRP installer afterwards
I'm stuck in the recovery.
I've never had this problem before and am at my wits end, because I just can't figure out what is causing this problem.
Did anyone of you also had this problem and found a way to resolve it? Any help would be much appreciated!
Note: I'm using this TWRP (3.3.1-71) -> https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322
Click to expand...
Click to collapse
Sounds like your using bad command. fastboot boot whatever.img, it's better if after the word boot, drag and drop TWRP.img into command line. Oh, try 3.3.1-70, then upgrade TWRP to 71, I was having the same issue.
Hi all,
update: I made update at the end.
My OP7 version is GM1900, so far I was on build 10.0.6GM57BA with Magisk 20.4, but for some time I had 10.0.8 update notification.
Today I decided to update build.
I consider myself as medium experienced user the type that is using rather step by step guides.
But this time I thought I don't need guide cause I should remember how I did update last time. In the meantime I help my son to make homework what was an additional distraction.
I always download full OTA from oneplus.com support but it turned out there was no 10.0.8 (instead there was/is 10.0.7). So I tried to search for 10.0.8 and I found this xda news. As there is a mess with versions and links and I was doing it on mobile Chrome I accidentally tapped Global/India Full OTA
Steps I made:
1.1. Downloading file OnePlus7Oxygen_14.P.29_OTA_029_all_2009152124_ba2424a.zip
1.2. Downloading official TWRP twrp-installer-3.4.0-0-guacamole.zip
1.3. Boot into TWRP.
1.4. Flash twrp-installer-3.4.0-0-guacamole.zip
1.5. Restart to TWRP
1.6. Flash magisk uninstall
1.7. Flash 10.3.5 (India & Global) - OnePlus7Oxygen_14.P.29_OTA_029_all_2009152124_ba2424a.zip
1.8. Flash magisk 20.1 (but forgot to reboot after flashing TWRP it was first mistake I think)
1.9. Ended with 10.3.5 (India & Global) build with stock recovery and without Magisk.
Next I tried to return to GM57BA.
Then the steps I made:
2.1. Downloading official build 10.0.7.GM57BA from oneplus support site.
2.2. Downloading Mauronofrio's TWRP twrp-3.4.0-0-guacamole-unified-Q-mauronofrio.img and twrp-3.4.0-0-guacamole-unified-installer-mauronofrio.zip
2.3. Boot OP7 into fastboot then command "fastboot boot twrp-3.4.0-0-guacamole-unified-Q-mauronofrio.img"
2.4. After phone booted into TWRP I flashed twrp-3.4.0-0-guacamole-unified-installer-mauronofrio.zip
2.5. Restart to TWRP
2.6. Flashed magisk uninstall.
2.7. Flashed 10.0.7.GM57BA
2.8. Flashed magisk 20.4
2.9. Only then I rebooted to TWRP (I think it was mistake).
2.10. Then I saw first problem - there was no lockscreen security with TWRP (unlock pattern).
2.11. Restarted to TWRP again - the same no unlock pattern screen, no access to data partition
2.12. I started to panic and restarted into system.
2.13. I ended with hard bootloop - I mean I can't even do force reset (force reboot) by pressing and holding the Power and Volume down buttons at the same time :crying:
I'm sorry for this long description but I thought it will be helpful to diagnose what I messed up.
Questions and my thoughts:
1. Did I messed up by not restarting after last magisk flash?
2. What to do now? Do I need to wait for battery discharge? Then unbrick using MSM tool?
3. Is there any chance to repair and preserve personal data? I have TWRP backup about 3 months old. Maybe after battery discharge I should go to TWRP and then sideload this backup? Maybe magisk uninstall or stock boot image flash?
Please help
Update:
After battery discharge I managed to boot into TWRP recovery (Mauronofrio's 3.4.0.0)
Then couldn't access /data
But when I switched to Slot B and reboot to recovery situation is back to normal (I guess).
I'm still in recovery scared to boot into system.
What to do now?
kold11 said:
Hi all,
update: I made update at the end.
My OP7 version is GM1900, so far I was on build 10.0.6GM57BA with Magisk 20.4, but for some time I had 10.0.8 update notification.
Today I decided to update build.
I consider myself as medium experienced user the type that is using rather step by step guides.
But this time I thought I don't need guide cause I should remember how I did update last time. In the meantime I help my son to make homework what was an additional distraction.
I always download full OTA from oneplus.com support but it turned out there was no 10.0.8 (instead there was/is 10.0.7). So I tried to search for 10.0.8 and I found this xda news. As there is a mess with versions and links and I was doing it on mobile Chrome I accidentally tapped Global/India Full OTA
Steps I made:
1.1. Downloading file OnePlus7Oxygen_14.P.29_OTA_029_all_2009152124_ba2424a.zip
1.2. Downloading official TWRP twrp-installer-3.4.0-0-guacamole.zip
1.3. Boot into TWRP.
1.4. Flash twrp-installer-3.4.0-0-guacamole.zip
1.5. Restart to TWRP
1.6. Flash magisk uninstall
1.7. Flash 10.3.5 (India & Global) - OnePlus7Oxygen_14.P.29_OTA_029_all_2009152124_ba2424a.zip
1.8. Flash magisk 20.1 (but forgot to reboot after flashing TWRP it was first mistake I think)
1.9. Ended with 10.3.5 (India & Global) build with stock recovery and without Magisk.
Next I tried to return to GM57BA.
Then the steps I made:
2.1. Downloading official build 10.0.7.GM57BA from oneplus support site.
2.2. Downloading Mauronofrio's TWRP twrp-3.4.0-0-guacamole-unified-Q-mauronofrio.img and twrp-3.4.0-0-guacamole-unified-installer-mauronofrio.zip
2.3. Boot OP7 into fastboot then command "fastboot boot twrp-3.4.0-0-guacamole-unified-Q-mauronofrio.img"
2.4. After phone booted into TWRP I flashed twrp-3.4.0-0-guacamole-unified-installer-mauronofrio.zip
2.5. Restart to TWRP
2.6. Flashed magisk uninstall.
2.7. Flashed 10.0.7.GM57BA
2.8. Flashed magisk 20.4
2.9. Only then I rebooted to TWRP (I think it was mistake).
2.10. Then I saw first problem - there was no lockscreen security with TWRP (unlock pattern).
2.11. Restarted to TWRP again - the same no unlock pattern screen, no access to data partition
2.12. I started to panic and restarted into system.
2.13. I ended with hard bootloop - I mean I can't even do force reset (force reboot) by pressing and holding the Power and Volume down buttons at the same time :crying:
I'm sorry for this long description but I thought it will be helpful to diagnose what I messed up.
Questions and my thoughts:
1. Did I messed up by not restarting after last magisk flash?
2. What to do now? Do I need to wait for battery discharge? Then unbrick using MSM tool?
3. Is there any chance to repair and preserve personal data? I have TWRP backup about 3 months old. Maybe after battery discharge I should go to TWRP and then sideload this backup? Maybe magisk uninstall or stock boot image flash?
Please help
Update:
After battery discharge I managed to boot into TWRP recovery (Mauronofrio's 3.4.0.0)
Then couldn't access /data
But when I switched to Slot B and reboot to recovery situation is back to normal (I guess).
I'm still in recovery scared to boot into system.
What to do now?
Click to expand...
Click to collapse
To force restart I need to use power button and both volume keys..
To keep TWRP you need to flash rom, then without restart flash TWRP again, then restart TWRP, then flash Magisk.
Likely the r reason why your system doesn't boot is because it can't decrypt your data.
Why this happens I don't know, maybe in the upgrade they changed something related to the exception and then by downgrading again it isn't able to read it anymore.
I would suggest to:
Flash the latest rom.
Flash TWRP
Reboot TWRP
If TWRP then doesn't ask for PIN or password, then I'm afraid you have lost your data. I hope you have a backup.
I'm that case format (not just clear) data -> yes
Reboot TWRP
Then flash Magisk.
Thanks for reply.
Like I wrote in update after changing slot to b I managed to run TWRP with decrypted data, made even new new backup.
I also restarted into system and it occurs I'm still 10.3.5 (India & Global) GM57AA, so everything I flashed in with build 10.0.7.GM57BA was unsuccessful.
I think I messed with changing inactive slot procedure. Noob mistake I need to read about it.
kold11 said:
Thanks for reply.
Like I wrote in update after changing slot to b I managed to run TWRP with decrypted data, made even new new backup.
I also restarted into system and it occurs I'm still 10.3.5 (India & Global) GM57AA, so everything I flashed in with build 10.0.7.GM57BA was unsuccessful.
I think I messed with changing inactive slot procedure. Noob mistake I need to read about it.
Click to expand...
Click to collapse
I would suggest do restore your device with msm unbrick tool.
1. From recovery, turn off (i noticed, that when tried to turn off from somewhere else, the device would auto reboot later in downlaod mode)
2. In windows, turn off the connection & open device manager: Get this driver http://download.windowsupdate.com/c..._fba473728483260906ba044af3c063e309e6259d.cab
3. Press volume/down + volume/up, after about 5s connect to pc
4. Your device should show up in device manager, open it and install the driver manuell from step 2 (keep device options open... if fail you need to uninstall the driver before trying again)
5. Now wait for about 40s, if your device stays in download mode, you can open & start the msm tool (leave the options in msm as they are)
6. It will take about 280s, then the device will reboot.... (its normal that it stays longer at the oneplus logo at first start)
MSM Thread: https://forum.xda-developers.com/oneplus-7/how-to/op7-unbrick-tool-to-restore-device-to-t3954325
I've also uploaded the 10.0.5OOS Unbrick tool on mega, because android file hosted downloads are so terrible: https://mega.nz/file/ArZFkYpS#Z_rOIwZeYN27IG6L8rOi-yfw8wXGiwvK-uWVDlsmvTI
Hello,
i have a question about getting into Recovery or maybe i have to install it again?
So i installed twrp following this guide
Install LineageOS on walleye | LineageOS Wiki
wiki.lineageos.org
At first i installed the Lineage OS recovery but wasnt able to flash a ROM with that so i switched and installed twrp.
It was installed to slot A.
I then went ahead and installed an ASOP ROM.
Now the ROM is working fine and i wanted to go into TWRP and do a Backup.
However i cant get into TWRP. Not with key combos nor with adb reboot recovery.
All i get is the fallen Android Robot picture.
I guess i wrote the image to Slot A as well and now have no recovery left.
Do i have to flash TWRP again and this time to Slot B?
I dont wanna brick anything by accident as i have seen some posts where people switched Slots and got bricks / semi bricks.
Thanks for any help or clarification.
Kind Regards
Hello mate, i never reinstalled twrp on my pixel 2 after catching a bootloop after installing it and then flashing magisk so stuck with using fastboot to fastboot boot twrp when I wanted to flash a ROM/mod.
Sounds strange that twrp was only on 1 slot as the twrp installer zip should flash both slots when flashed?
With regard to losing twrp you'll probably find that the new ROMs recovery has overwritten your twrp recovery during the flashing process giving you a stock recovery again (Fallen android). When I was using a 6T which is an A/B slot device you always had to reflash the twrp installer after a ROM flash to keep twrp installed.
I'd check the official twrp thread re backing up with twrp as it did have problems either backing up or restoring last I used it.
Hope that's some help.
My Phone was running Android 11 perfectly fine. Has been for about a week and a half, and I've decided that I don't like the OS. I was going to flash a custom ROM and went to create a nandroid before flashing. Literally all I did was boot into recovery and TWRP got stuck in a bootloop, the TWRP splash screen appears, crashes and then reappears about 2 seconds later, now when I try to boot back into system, TWRP appears instead and continues to bootloop. I can enter fastboot mode but that's all.
So far I've tried
Booting TWRP through fastboot. Failed another bootloop.
Rebooting through ADB. Boots into TWRP.
Rebooting Bootloader. Seems to do nothing.
Does anyone have any ideas on how to fix this ? It seems strange to me that something as simple as booting recovery could do this much harm. I also have a nandroid backup stored on the device from about a month ago, so the data loss wouldn't be THAT major, but I'm also not sure how I could access it without system or recovery access.
Hi , Which version of TWRP use? I think there is an update a new version TWRP 3.5.2 , Try to flash it. if its still not booting try to boot the original Boot of OOS11.
May be this threads will help you.
OnePlus Community
Introducing our new OnePlus Community experience, with a completely revamped structure, built from the ground-up.
forums.oneplus.com
humood96 said:
Hi , Which version of TWRP use? I think there is an update a new version TWRP 3.5.2 , Try to flash it. if its still not booting try to boot the original Boot of OOS11.
May be this threads will help you.
OnePlus Community
Introducing our new OnePlus Community experience, with a completely revamped structure, built from the ground-up.
forums.oneplus.com
Click to expand...
Click to collapse
New version does not work as well. Flash the stock boot img to get out of bootloop.
Jacobo123 said:
My Phone was running Android 11 perfectly fine. Has been for about a week and a half, and I've decided that I don't like the OS. I was going to flash a custom ROM and went to create a nandroid before flashing. Literally all I did was boot into recovery and TWRP got stuck in a bootloop, the TWRP splash screen appears, crashes and then reappears about 2 seconds later, now when I try to boot back into system, TWRP appears instead and continues to bootloop. I can enter fastboot mode but that's all.
So far I've tried
Booting TWRP through fastboot. Failed another bootloop.
Rebooting through ADB. Boots into TWRP.
Rebooting Bootloader. Seems to do nothing.
Does anyone have any ideas on how to fix this ? It seems strange to me that something as simple as booting recovery could do this much harm. I also have a nandroid backup stored on the device from about a month ago, so the data loss wouldn't be THAT major, but I'm also not sure how I could access it without system or recovery access.
Click to expand...
Click to collapse
Did your problem got solved?As i updated to A11 a few days ago and am facing the same problem since.Did flashing the new version of twrp worked for you?
Jacobo123 said:
My Phone was running Android 11 perfectly fine. Has been for about a week and a half, and I've decided that I don't like the OS. I was going to flash a custom ROM and went to create a nandroid before flashing. Literally all I did was boot into recovery and TWRP got stuck in a bootloop, the TWRP splash screen appears, crashes and then reappears about 2 seconds later, now when I try to boot back into system, TWRP appears instead and continues to bootloop. I can enter fastboot mode but that's all.
So far I've tried
Booting TWRP through fastboot. Failed another bootloop.
Rebooting through ADB. Boots into TWRP.
Rebooting Bootloader. Seems to do nothing.
Does anyone have any ideas on how to fix this ? It seems strange to me that something as simple as booting recovery could do this much harm. I also have a nandroid backup stored on the device from about a month ago, so the data loss wouldn't be THAT major, but I'm also not sure how I could access it without system or recovery access.
Click to expand...
Click to collapse
At first.- Stable TWRP is not available til now for OOS11
For TWRP to work your device must be decrypted.
This link will help you, will get full details
- https://forum.xda-developers.com/t/...-oneplus-7-pro.3931322/page-152#post-84727891
For more questions and help, please post in that twrp thread only
Regards