Hello,
I have many problems with my oneplus 6, twrp and the a/b partitioning.
I installed twrp successfully and had a working setup, but wanted to start from scratch so I installed a custom-oos using twrp again.
But then I only could boot to twrp and no chance of getting the rom to boot up.
In twrp I installed the rom again and now the only thing I see when trying to boot up is the white led, nothing else.
This happened a few times now, don't know what I am doing wrong.
Any help?
Thanks
Try flashing Magisk. It worked for me but I was on official OOS...
Joan Tur (OP6)
Thanks, but magisk says "unable to repack boot image"
Related
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.
So I've been on the Global Indian MIUI for a while now. And what I usually did was I patched a boot image file using Magisk and then flashed it through fastboot. That way I didn't need a custom recovery and I could get straight updates from MIUI as usual.
After updating to MIUI 10.3.13 I tried to do the same thing once again, but this time I'm met with a Bootloop. The bootlogo shows and the boot animation starts and then suddenly phone reboots and it keeps going on like this until I flash back the stock boot image.
So I installed TWRP and tried flashing Magisk from there but same result. Goes into bootloop. Tried flashing the patched image file from TWRP but end result still same.
So any solution to this? Or any rooting alternative other than magisk?
Is anybody else facing this or are is it just me?
Like the title says, I can´t boot to recovery (Oneplus one). If I try to boot to recovery, I´m ending in the Qualcomm CrashDump Mode.
I have a Oneplus 7 Pro with Stable 10.0 BA FW.
Rooted with Magisk (Patched Boot.img) Is this causing the problem?
After pressing Vol+ and powerbutton, the devices boots normally.
Thanks in advance.
RealDanyo said:
Like the title says, I can´t boot to recovery (Oneplus one). If I try to boot to recovery, I´m ending in the Qualcomm CrashDump Mode.
I have a Oneplus 7 Pro with Stable 10.0 BA FW.
Rooted with Magisk (Patched Boot.img) Is this causing the problem?
After pressing Vol+ and powerbutton, the devices boot normally.
Thanks in advance.
Click to expand...
Click to collapse
I had the same issue this morning when trying to update to 10.0.1. Just boot to bootloader and boot twrp then install 10.
I think is the magisk update (magisk 20.0) that causes this, because it's happening to me in the beta 3 and before I updated magisk it was working fine with the beta 2
ItsTecnoDavid said:
I think is the magisk update (magisk 20.0) that causes this, because it's happening to me in the beta 3 and before I updated magisk it was working fine with the beta 2
Click to expand...
Click to collapse
I have no issues with magisk or twrp.
It might be the way you are installing ota or rom.
Might be model specific not sure as I don't know what model you are on. Mine is GM1915.
I'm talking about the official recovery
GM21AA, exactly the same situation (from 10 stable to 10.0.1 and magisk from 19.4 beta to 20) and the stock recovery bump into Qualcomm Crashdump problem here, system bootup normal as well as bootloader.
Troubleshooting:
1. Local update twice, install magisk at inactive slot OTA before reboot, for Android 10's A/B partitions machinasm , try let magisk patch both boot.img. Same...
2. Local update and reboot, lost root but stock recovery work, Fastboot boot twrp.img (latest, not flash, cause I don't need the permanent twrp)->twrp install magisk, reboot system, then, again, same problem.
Todo:
Magisk manager or twrp uninstall magisk, but if it's fail maybe ended up to bootloop, scary.
May try to install back old 19.4 magisk.zip via twrp, it's working in 10.0.0
Anyone with the same problem have any idea?
Thats the exact same error I ran into.
But as mentioned earlier, I never had TWRP on my OP7P. I flashed the patched boot.img via adb and I´m still on 10.0 BA Firmware.
I thought TWRP dosn´t work on Android Q (I´m coming from an Pixel3 and there it won´t work) So maybe I will give TWRP a try tomorrow. Are there different versions or is the official one the best?
RealDanyo said:
Thats the exact same error I ran into.
But as mentioned erlier, I never had TWRP on my OP7P. I flashed the patched boot.img via adb and I´m still on 10.0 BA Firmware.
I thought TWRP dosn´t work on Android Q (I´m coming from an Pixel3 and there it won´t work) So maybe I will give TWRP a try tomorrow. Are there different versions or is the official one the best?
Click to expand...
Click to collapse
The recovery here is the one to use.
https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322
Be sure to read through
So thanks erveryone who helped.
I now have TWRP running as recovery. So there is no need for official recovery. (and no Qualcomm CrashDump Mode)
Had this happen to me earlier this week. Just ended up using the MSM tool and restoring shipping firmware. You can look for the unbricking thread here for more info on that.
Yea, this just happened to me. Updated Magisk, Updated to 10.0.1 from 10.0. Booted fine.
Re-installed a few magisk modules (didn't just re check the modules, but reinstalled each)
Now OS won't boot, and recovery goes to Crash Dump. Would be ok if OS wouldn't bootloop and I could get to OS.
Oh, and my ADB now is an unauthorized device while its in bootloop mode
EDIT:
phew. Tried to hold volume up+dn rather than up or dn, got into bootloader. Able to fastboot boot TWRP and then delete problematic RIRU magisk modules. All is well in the world now...
I don't get it why it have to be so hard.
I'm constantly soft bricking/ bootlooping this phone when trying to do simple things such flashing magisk and twrp. I remember it being so much easier with my Poco F1, never got close to bricking it.
Now every little mistake ends with a bricked phone and 5 hours on the internet trying to understand why
WillyRy said:
Yea, this just happened to me. Updated Magisk, Updated to 10.0.1 from 10.0. Booted fine.
Re-installed a few magisk modules (didn't just re check the modules, but reinstalled each)
Now OS won't boot, and recovery goes to Crash Dump. Would be ok if OS wouldn't bootloop and I could get to OS.
Oh, and my ADB now is an unauthorized device while its in bootloop mode
EDIT:
phew. Tried to hold volume up+dn rather than up or dn, got into bootloader. Able to fastboot boot TWRP and then delete problematic RIRU magisk modules. All is well in the world now...
Click to expand...
Click to collapse
Same issue here and no TWRP installed.
I did ADB REBOOT FASTBOOT and was able to install the twrp image by FASTBOOT BOOT twrp-3.3.1-70-guacamole-unified-Q-mauronofrio.img
Going to try and remove Magisk and see if I can salvage my data and then re-install Magisk afterwards.
Ok...got back into the system by flashing the Magisk Uninstaller in TWRP that is here: https://magiskroot.net/md/Magisk_Manager_for_Recovery_Mode_(mm)-2019.4.4.zip
Went to advanced in TWRP, then to terminal, then typed mm.
Typed in C for Core only to load into system without Magisk. Deleted my Magisk modules that may have interfered with it (I had an older version of No Limit that I should have updated prior. After removing and rebooting back into system, all is fine now.
JLine05 said:
Same issue here and no TWRP installed.
I did ADB REBOOT FASTBOOT and was able to install the twrp image by FASTBOOT BOOT twrp-3.3.1-70-guacamole-unified-Q-mauronofrio.img
Going to try and remove Magisk and see if I can salvage my data and then re-install Magisk afterwards.
Ok...got back into the system by flashing the Magisk Uninstaller in TWRP that is here: https://magiskroot.net/md/Magisk_Manager_for_Recovery_Mode_(mm)-2019.4.4.zip
Went to advanced in TWRP, then to terminal, then typed mm.
Typed in C for Core only to load into system without Magisk. Deleted my Magisk modules that may have interfered with it (I had an older version of No Limit that I should have updated prior. After removing and rebooting back into system, all is fine now.
Click to expand...
Click to collapse
Yea man, things are hinkey this update.
My big problem was i had twrp but it got wiped i guess (could no longer access) and couldn't access adb nor fastboot. But finally got into bootloader (cmd fastboot) so was able to fix.
Easier solution than installing Magisk uninstaller (presuming one has twrp installed, which would be the case if able to flash Magisk uninstaller) is go to TWRP>advanced>file manager and navigate data/adb/modules and delete from there
DO you guys know if there is an updated magisk being developed or what is the way to fix it? Uninstall magisk via TWRP (since I can temporarily install and get into TWRP using the all in one tool by the TWRP developer). Then install TWRP and then Install Magisk ?
I have same problem
How to fix it and bring back stock recovery?
wawanRedblack said:
I have same problem
How to fix it and bring back stock recovery?
Click to expand...
Click to collapse
Can you boot OS?
Can you get to bootloader?
WillyRy said:
Can you boot OS?
Can you get to bootloader?
Click to expand...
Click to collapse
Yes i can boot os and bootloader is ok
Ok, so I had to reinstall my OS through TWRP (2GB Full update)... and rebooting to the Bootloader to reinstall TWRP and rebooting again, I want to install Magisk again.
When I install Magisk through TWRP and reboot, the boot animation is stuck forever and animates very slowly. The only way to get out is to press VOL UP + POWER and inmediately VOL DOWN + POWER to enter TWRP. To fix the stuck boot animation I have to reinstall the full OxygenOS update and reinstall TWRP.
My problem is that I'm in this vicious cicle where if I install Magisk it doesn't work and I have to reinstall the OS and TWRP.
What am I missing? Why Magisk is making my device stuck on the boot screen?
Any help will be appreciated. Thanks!
I had that earlier today. For me I switched to the other partition from twrp and rebooted and it worked fine. Guess I'll flash ROM and magisk to both partitions next time
skymera said:
I had that earlier today. For me I switched to the other partition from twrp and rebooted and it worked fine. Guess I'll flash ROM and magisk to both partitions next time
Click to expand...
Click to collapse
So let me make sure I understood you. I need to switch to Slot B and also install the OS and Magisk?
OK, an update. After trying to switch slots, install the OS in both of them and Magisk and all the possible permutations, I tried flashing 19.4 and it worked flawlessly first time.
Now I'm going to update it!
Update 2: I'm finally running the latest version! Updating Magisk through Magisk Manager worked fine.
Deses said:
OK, an update. After trying to switch slots, install the OS in both of them and Magisk and all the possible permutations, I tried flashing 19.4 and it worked flawlessly first time.
Now I'm going to update it!
Update 2: I'm finally running the latest version! Updating Magisk through Magisk Manager worked fine.
Click to expand...
Click to collapse
I have the same issue with the slow boot animation and the endless loading. I tried to install the OTA again, TWRP again and magisk 20.1, 20.0, 19.4 ...
Sadly the animation stays that slow and my OP7Pro doesnt boot up. How exactly did you get rid of that problem? I feel like I tried every combination of flashing
dennisgrue said:
I have the same issue with the slow boot animation and the endless loading. I tried to install the OTA again, TWRP again and magisk 20.1, 20.0, 19.4 ...
Sadly the animation stays that slow and my OP7Pro doesnt boot up. How exactly did you get rid of that problem? I feel like I tried every combination of flashing
Click to expand...
Click to collapse
I had this with PA. Not sure what caused it as my flashing process is the same every time.
In the end I gave up and formatted /data
skymera said:
I had this with PA. Not sure what caused it as my flashing process is the same every time.
In the end I gave up and formatted /data
Click to expand...
Click to collapse
I decided to give up too... Was a bad mistake. I accidentely rebooted the phone after the update today. I will never do that mistake again
That dreadful moment when you have this problem again and googling points you to your own thread with no solutions.
UPDATE: Oh I think I got it! I had to uninstall Magisk Manager AND flash Magisk Uninstaller zip, reboot to OS, reboot to Recovery again and flash Magisk 20.3 again and it finally worked! No more stuck slow boot animation.
Probably the two reboots aren't needed, but I like doing things slow.
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.