Database Info

Issues with installing CarbonROM on the K1 -> Bootloop

Hello guys.
Last time I rooted and installed a Custom ROM was like 7-8 years ago with CM5 or so. So I'm not really up to date.
On my K1 tablet, I wanted to install the CarbonROM. Tablet runs Nougat.
The Root was successful, used fastboot for TWRP recovery. (Version 3.1.1 and 3.0.2, tried both). As in many tutorials described I wiped data/cache before installing. Installed CarbonROM (latest version) + gapps micro for 7.1 then wiped cache/dalvik and rebooted.
System then was stuck in bootloop forever, waited about 20mins but nothing happend.
Managed to backup by hard-reboot into recovery/adb and flash twrp again. Tried this time with twrp version 3.0.2, same issue.
I know about the presence of "blob", whatever it is. But since a few guides use it, and few dont, I tried with once with it but managed to land in bootloop again.
Tried with CWM but it didnt even recognize my SD card, or confused the internal storage as sd card. Moved the CarbonROM to the internal storage then and tried to install it. After boot image there was an android with a red "!" and "no command". Vol up + pwr -> recovery. rebooted. Still had the firmware from before, nothing happend at all.
I don't know anymore what to do to get CarbonROM installed and actually started.
Anybody got ideas or a actually a solution?
Greetings

Try a different ROM, or try another gapps (I've often had to mess with different gapps on AOSP ROMs on previous devices).
As for just getting the phone working again, you should have made a TWRP backup before trying to flash a custom ROM. Then you could have just restored the backup.

OS reset after update to Magisk 18 - SDCARD untouched, how can I restore best?

Hello,
I use my OnePlus 6 rooted with Magisk since the beginning and had no issues. Today the update to Magisk v18 was proposes, so I installed the update in Magisk Manager and of course didn't do a backup before.
After the reboot the system was not really usable anymore. Every 30 seconds I received the message that the system UI stopped working and it froze for a while.
So I wanted to get rid of Magisk and what I did was:
- boot to twrp and uninstalled Magisk (I didn't use the newest uninstaller, I used the one from September).
- tried to reboot but received the message "Wiping, please wait. Do not remove battery of turn off your phone".
- after some seconds the message disappeared, the screen was black and when I pressed the power button it was vibrating but didn't do anything else.
So my tried to get it working again:
- rebooted to TWRP again
- used the latest uninstaller to uninstall Magisk
- then the OS didn't reboot at all
- once more went to TWRP and installed Magisk 18 again. Then the phone rebooted normally but I got a wiped OS.
My sdcard partition (/storage/emulated/0/) is not wiped, everything is still there.
Is there a possibility to go back to a last "stable" version and continue using the phone with the data on the filesystem?
My thought: is it possible to boot from the other slot (before last update) and would this work with my current data on the sdcard partition? Like this I would just lose the Apps and updates I installed since then, right?
Is there another or better solution?
Thank you and best regards

den_zel said:
Hello,
I use my OnePlus 6 rooted with Magisk since the beginning and had no issues. Today the update to Magisk v18 was proposes, so I installed the update in Magisk Manager and of course didn't do a backup before.
After the reboot the system was not really usable anymore. Every 30 seconds I received the message that the system UI stopped working and it froze for a while.
So I wanted to get rid of Magisk and what I did was:
- boot to twrp and uninstalled Magisk (I didn't use the newest uninstaller, I used the one from September).
- tried to reboot but received the message "Wiping, please wait. Do not remove battery of turn off your phone".
- after some seconds the message disappeared, the screen was black and when I pressed the power button it was vibrating but didn't do anything else.
So my tried to get it working again:
- rebooted to TWRP again
- used the latest uninstaller to uninstall Magisk
- then the OS didn't reboot at all
- once more went to TWRP and installed Magisk 18 again. Then the phone rebooted normally but I got a wiped OS.
My sdcard partition (/storage/emulated/0/) is not wiped, everything is still there.
Is there a possibility to go back to a last "stable" version and continue using the phone with the data on the filesystem?
My thought: is it possible to boot from the other slot (before last update) and would this work with my current data on the sdcard partition? Like this I would just lose the Apps and updates I installed since then, right?
Is there another or better solution?
Thank you and best regards
Click to expand...
Click to collapse
If you can get into TWRP dirty flash your ROM. Otherwise change to the other partition either via TWRP or via fastboot set_active A (or B).
Magisk is only installed on the active partition meaning switching it would let you boot into a non-rooted OS.
Apps etc. should be the same as it uses /data. Only /system and some other partitions are A/B.

Phone unable to wipe anything via TWRP recovery.

About a month ago I installed PixysOS v2.4 for my device along with Magisk v18.1. Everything was working fine until today phone suddenly froze. I tried to boot to fastboot mode and restart device but to my unfortunate luck it would just stuck atWarning Bootloader Unlocked Screen and won't proceed further. I tried rebooting via TWRP by selecting recovery mode but no matter which option I select it would stuck at TWRP then.
Then I thought to uninstall magisk as it may have caused some error so I again booted into TWRP and flashed the latest Magisk Uninstaller but it would not go further after detecting my device system. I tried this 3-4 times then I thought to completely wipe out the system and install PixysOS again.
Now when I tried to wipe System,Dalvik,Cache and Data it is stuck at Wiping Dalvik Cache DIrectories...
I can still start TWRP by pressing Vol down+Start button but its kind of useless as it would not wipe anything!
Here is my device info:-
Device name :- Motorola Moto G Turbo Edition (MotoG3-TE)(MERLIN)
Os running :- PixysOs v2.4 based on Android Pie.
TWRP version :- 3.2.3-0
Magisk Version :- 18.1
Magisk Modules :- Youtube Vanced and Viper4Android.
Can anyone guide me how do I fix my phone?
Edit :- So I just realized that I have a Nandroid Backup already on my SD card. I tried restoring it through TWRP and now it seems something 'Internal' is wrong with my phone.

Howling Wolf1210 said:
About a month ago I installed PixysOS v2.4 for my device along with Magisk v18.1. Everything was working fine until today phone suddenly froze. I tried to boot to fastboot mode and restart device but to my unfortunate luck it would just stuck atWarning Bootloader Unlocked Screen and won't proceed further. I tried rebooting via TWRP by selecting recovery mode but no matter which option I select it would stuck at TWRP then.
Then I thought to uninstall magisk as it may have caused some error so I again booted into TWRP and flashed the latest Magisk Uninstaller but it would not go further after detecting my device system. I tried this 3-4 times then I thought to completely wipe out the system and install PixysOS again.
Now when I tried to wipe System,Dalvik,Cache and Data it is stuck at Wiping Dalvik Cache DIrectories...
I can still start TWRP by pressing Vol down+Start button but its kind of useless as it would not wipe anything!
Here is my device info:-
Device name :- Motorola Moto G Turbo Edition (MotoG3-TE)(MERLIN)
Os running :- PixysOs v2.4 based on Android Pie.
TWRP version :- 3.2.3-0
Magisk Version :- 18.1
Magisk Modules :- Youtube Vanced and Viper4Android.
Can anyone guide me how do I fix my phone?
Edit :- So I just realized that I have a Nandroid Backup already on my SD card. I tried restoring it through TWRP and now it seems something 'Internal' is wrong with my phone.
Click to expand...
Click to collapse
Tried wiping everything? Tried some other ROM other than Pixys?

baalajimaestro said:
Tried wiping everything? Tried some other ROM other than Pixys?
Click to expand...
Click to collapse
Tried Pixel Experience and LineageOS but it just won't flash!
By wiping everything you mean all of the options I see in wipe tab?

Need help about encryption probably. .

So guys stuck in a problem,
**Before flashing the update**
Device OP7Pro.
Twrp was Installed.
Magisk was Installed..
What i did, Downloaded latest OSS 10.0.2 GM21AA full rom, (to update)
Flashed with twrp, then Flashed Twrp zip again, rebooted the recovery, and then system reboot,
------
What happened after update flashing
OSS running with latest build,
Now the problem starts..
Magisk Manager is there,
But Magisk is not installed,
Rebooted to Recovery, all folders are empty in sdcrd folder, there is not a single file,
If i reboot back to oos, all files are there,
And my windows PC is also not Recognizeing My OP7pro anymore..
Need help pls

I messed up - stock ROM update via TWRP :(

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