I had lineage os 17 installed on it. I wanted to access the recovery and I got into lineage s recovery even if I have twrp recovery. So I wanted to reboot back to the system and it always boots right into lineage os recovery. How can I fix this?
Hey! No need to worry, I just upgraded my LOS to 18.1 via TWRP and rooted it with magisk. You must have accidentally swiped to reboot to system with the install twrp option checked when you should've tapped the do not install option. You have two options.
1. Now you can try to "dirty flash" LOS via TWRP, download LOS 18.1 to a pen drive and go to "Wipe" and delete cache and dalvik cache and keep all your data in the process.
2. Or you can just try to get it to boot to system and backup your data and upgrade.
Some questions, do you have potentially boot loop causing magisk modules installed? or is your device even rooted in the first place? That is all for now.
Related
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?
Hello guys,
I'm having trouble trying to install a Custom ROM (Tresk Mod, but I get it with others too)
So basically some days ago my whole Internal Storage got encrypted so I had to a full wipe.
From there I decided to use Msmtools just in case, so I got back to OOS 5.1.5 from there I updated to OOS 9.0.5 via OTA and unlock the bootloader and install TWRP everything works fine.
But when I tried to install any custom ROM I either cannot boot and just boots to Bootloader (Not even the recovery works) and I get "Failed to load/authenticate boot image: Load Error" which I can fix fastboot flashing all the partitions...
Or I straight get a black screen with the White Notifications LED whenever I try to boot either to system or recovery and from there I can only recover using Msmtools...
So I'm now asking, what are the steps for flashing Custom ROMs now?? Because seems like I'm doing something wrong since I'm ending having a Bricked device...
try to flash rom with bluespark recovery
Nothing changed that I'm aware of, but I found that I'll have the same experience if I try to root before booting the system at least once rootless first. Also, I have issues like that whenever I keep TWRP (even Blu Spark) installed. Now I only use it via sideload every time. I never have issues anymore.
Mdknight said:
Nothing changed that I'm aware of, but I found that I'll have the same experience if I try to root before booting the system at least once rootless first. Also, I have issues like that whenever I keep TWRP (even Blu Spark) installed. Now I only use it via sideload every time. I never have issues anymore.
Click to expand...
Click to collapse
I did the following:
1. Upgraded from 5.1.5 to 9.0.5 (Since I was coming from Msmtools fix)
2. Unlock bootloader
3. Reboot to system and then boot again to bootloader for doing (fastboot boot TWRP.xxx.img)
4. Once in the recovery flash recovery and Magisk (just because) and back to system (where everything was working perfectly)
5. Rebooted to recovery and did the following:
Factory Reset (The one that you slide which should wipe Cache, Dalvik and Data)
Flashed the ROM (HavocOS 2.5) and right after that TWRP
And at this point I tried to reboot back to recovery but black screen and cannot boot to recovery nor system not even via fastboot
Is your order different? Am I missing something?
Asiier said:
I did the following:
1. Upgraded from 5.1.5 to 9.0.5 (Since I was coming from Msmtools fix)
2. Unlock bootloader
3. Reboot to system and then boot again to bootloader for doing (fastboot boot TWRP.xxx.img)
4. Once in the recovery flash recovery and Magisk (just because) and back to system (where everything was working perfectly)
5. Rebooted to recovery and did the following:
Factory Reset (The one that you slide which should wipe Cache, Dalvik and Data)
Flashed the ROM (HavocOS 2.5) and right after that TWRP
And at this point I tried to reboot back to recovery but black screen and cannot boot to recovery nor system not even via fastboot
Is your order different? Am I missing something?
Click to expand...
Click to collapse
You have to install twrp.zip again after havoc, boot Back Into Recovery and then gapps and magisk
Asiier said:
I did the following:
1. Upgraded from 5.1.5 to 9.0.5 (Since I was coming from Msmtools fix)
2. Unlock bootloader
3. Reboot to system and then boot again to bootloader for doing (fastboot boot TWRP.xxx.img)
4. Once in the recovery flash recovery and Magisk (just because) and back to system (where everything was working perfectly)
5. Rebooted to recovery and did the following:
Factory Reset (The one that you slide which should wipe Cache, Dalvik and Data)
Flashed the ROM (HavocOS 2.5) and right after that TWRP
And at this point I tried to reboot back to recovery but black screen and cannot boot to recovery nor system not even via fastboot
Is your order different? Am I missing something?
Click to expand...
Click to collapse
Sconny said:
You have to install twrp.zip again after havoc, boot Back Into Recovery and then gapps and magisk
Click to expand...
Click to collapse
Agreed. Always reboot from recovery to recovery after flashing a new one (TWRP). THEN, go ahead and flash gapps and magisk.
Sconny said:
You have to install twrp.zip again after havoc, boot Back Into Recovery and then gapps and magisk
Click to expand...
Click to collapse
Mdknight said:
Agreed. Always reboot from recovery to recovery after flashing a new one (TWRP). THEN, go ahead and flash gapps and magisk.
Click to expand...
Click to collapse
I finally figured it out
The problem was that as I was updating via OTA OOS 9.0.5 was only installed in one Slot so I need to install it in the other as well.
Did the following process:
1. Boot to Bootloader and do "fastboot boot TWRP.img"
2. From there flash TWRP.zip and Reboot back to it (Recovery)
3. Flash OOS Latest (9.0.5)
4. Flash TWRP
5. Reboot to TWRP
6. Flash OOS Latest (9.0.5)
7. Flash TWRP
8. Reboot to TWRP
9. Wipe data, dalvik cache
10. Flash ROM
11. Flash TWRP
12. Reboot to TWRP
13. Flash gapps + Misc (Magisk, etc)
14. Boot system
Technically just one 1 installation should do as the other slot was already populated but the twice just to be safe.
Hey guys, so i had weird problem (status bar not visible after unlocking device) when updating my phone to 9.5.8. so i decided to flash the rom again to see if the issue goes away. I am rooted and unlocked and everything was working fine (apart from the status bar). I tried this method:
1. Downloaded the 9.5.8 update from Oxygen Updater (DONT REBOOT)
2. Went to Settings\System\System Update and click on the wheel on upper right corner.
3. Select Local Upgrade, then install the update (DONT REBOOT)
*DO NOT REBOOT after applying the update.
4. Launch Magisk, and click the first "install"
5. Choose the "Install to inactive slot (OTA)" option
6. Reboot once completed
On step 6 it failed, i rebooted directly into the Oneplus recovery and not TWRP. So i tried fastboot boot twrp.img and flash the installer. After that i rebooted the device and now it goes directly into twrp but without decryption, it wont ask for my PIN and i get the screen "Unmodified System Partition. Keep System Read only? Installing zips or performing adb operations may still modify the system partition." On the bottom i can "swipe to allow modifications", which i swipe to allow but i can't access any files on my phone, and that is my dead end. Help would be much appreciated.
I also tried flashing Magisk and also Magisk Uninstaller (uninmod wasn't found).
Also tried command "twrp decrypt password" in the Terminal and got "Failed to decrypt data"
sapalot said:
Hey guys, so i had weird problem (status bar not visible after unlocking device) when updating my phone to 9.5.8. so i decided to flash the rom again to see if the issue goes away. I am rooted and unlocked and everything was working fine (apart from the status bar). I tried this method:
1. Downloaded the 9.5.8 update from Oxygen Updater (DONT REBOOT)
2. Went to Settings\System\System Update and click on the wheel on upper right corner.
3. Select Local Upgrade, then install the update (DONT REBOOT)
*DO NOT REBOOT after applying the update.
4. Launch Magisk, and click the first "install"
5. Choose the "Install to inactive slot (OTA)" option
6. Reboot once completed
On step 6 it failed, i rebooted directly into the Oneplus recovery and not TWRP. So i tried fastboot boot twrp.img and flash the installer. After that i rebooted the device and now it goes directly into twrp but without decryption, it wont ask for my PIN and i get the screen "Unmodified System Partition. Keep System Read only? Installing zips or performing adb operations may still modify the system partition." On the bottom i can "swipe to allow modifications", which i swipe to allow but i can't access any files on my phone, and that is my dead end. Help would be much appreciated.
I also tried flashing Magisk and also Magisk Uninstaller (uninmod wasn't found).
Also tried command "twrp decrypt password" in the Terminal and got "Failed to decrypt data"
Click to expand...
Click to collapse
So to be clear: right now, you have access to twrp but not the data partition (twrp does not prompt you to decrypt), and when you reboot to system from, you are bounced back to twrp. Right?
reaper000 said:
So to be clear: right now, you have access to twrp but not the data partition (twrp does not prompt you to decrypt), and when you reboot to system from, you are bounced back to twrp. Right?
Click to expand...
Click to collapse
Yes, but i got frustrated and as i had done a Titanium Backup i just wiped everything on stock recovery and flashed the latest rom with twrp. Is there a clear instruction on how to update the rom when rooted? I just don't want it to happen again.
sapalot said:
Yes, but i got frustrated and as i had done a Titanium Backup i just wiped everything on stock recovery and flashed the latest rom with twrp. Is there a clear instruction on how to update the rom when rooted? I just don't want it to happen again.
Click to expand...
Click to collapse
Don't mess with stock recovery if you already have TWRP and Magisk aboard.
Here's how to update to 9.5.9 (or whatever) when it arrives:
- download your 3 zips: the latest full ota ROM, the latest Magisk, and the latest TWRP installer.
- boot to TWRP recovery
flash the ROM and TWRP installer
- reboot to TWRP recovery
flash Magisk
wipe dalvik
- reboot to system
There's a possibility after these steps and you're happily on the ROM, you might find that you're not rooted (it's more likely on a custom ROM than OOS). In which case you just reboot to recovery and flash Magisk, and then reboot to system. Done.
Discussion:
If you want a clean flash, you'd simply do a TWRP factory reset (standard wipe) instead of wiping dalvik.
Consider flashing both slots (A and B) whenever you update OOS, for two reasons. First, you don't have to keep track of which slot has which version of OOS should you flash a custom ROM or kernel with a specific version of OOS required as a base. The second reason is more compelling: the way the data partition changes encryption every update has obviated the reason for A/B slots, in that if newly updated B changes data encryption upon boot and then something happens, you cannot revert to A because A can't read the new data encryption. So the solution is to update both A and B at the same time so both slots use the same encryption and can both access the data partition.
Or like me, run the device decrypted (i. e. without forced encryption).
Good luck
I decided to root my Oneplus 6 (10.30.1) yesterday and everything went fine using TWRP 3.3.1.17 mauronofrio and Magisk 20.3.
Today I wanted to installed EdXposed which I did by going in to Magisk Manager, install Riru, reboot, install EdXposed and then reboot.
However, after installing EdXposed my phone would not boot, it would just hang on the loading screen.
I forced a reboot in to TWRP recovery and proceeded to restore my nandroid backup. This only made things worse.
When i try to boot I get the unlocked bootloader warning, it tries to boot in to the OS for about one second, then back to the bootloader warning screen and so on and so on.
I can still boot in to TWRP with Vol down + Power and i've tried wiping data and i've tried 'fix recovery bootloop' in the advanced settings but neither has worked.
Could someone kindly help fix this? I dont mind if i have to reinstall a stock Rom and lose root etc. I just want my phone back
Thanks
Goooober said:
I decided to root my Oneplus 6 (10.30.1) yesterday and everything went fine using TWRP 3.3.1.17 mauronofrio and Magisk 20.3.
Today I wanted to installed EdXposed which I did by going in to Magisk Manager, install Riru, reboot, install EdXposed and then reboot.
However, after installing EdXposed my phone would not boot, it would just hang on the loading screen.
I forced a reboot in to TWRP recovery and proceeded to restore my nandroid backup. This only made things worse.
When i try to boot I get the unlocked bootloader warning, it tries to boot in to the OS for about one second, then back to the bootloader warning screen and so on and so on.
I can still boot in to TWRP with Vol down + Power and i've tried wiping data and i've tried 'fix recovery bootloop' in the advanced settings but neither has worked.
Could someone kindly help fix this? I dont mind if i have to reinstall a stock Rom and lose root etc. I just want my phone back
Thanks
Click to expand...
Click to collapse
Use the msm tool to recover your device...
Try booting into the mauronofrio twrp recovery from fastboot. Then wipe the system partition and reinstall your rom.
Then boot mauronofrio twrp again from fastboot and install the zip, and reboot to recovery.
Install custom kernel, Magisk.
Uninstall edexposed
People reply here with no clue and advise to just restore stock. How is this a solution and how did not OP think of it themselves?
This is too little too late, but maybe it helps someone else:
Unofficial TWRP for Android 10 is glitchy. E.g. nanodroid backups are not restoring properly. Given current A/B mess this is not at all surprising.
Solution: wipe everything, reinstall *same* lineageOS version as before, flash same gapps as you had, and if you took the nanodroid backup after magisk, install it as well.
Don't boot yet!
Restore the backup *partially*, e.g. only the data partition.
This should work.
Or, emh, it did for me with some minor glitches. But even Google Authenticator didn't notice spoofing (otherwise RIP my accounts). So, i definitely recommend trying this workaround.
Hello! Today i tried Lineage os (came from PPUI) thought it was nice but i wanted to go back for the extra customisation options.
Steps i did: Removed screen locks
Reboot into TWRP recovery
I wiped the Dalvik+ Data+ Cache
Realised my PPUI restore was in the wrong folder and not the TWRP recovery thought i would just reboot and move it to the corect place
Then i got into a bootloop cause i wiped my os. Now phone says storage is encrypted.
Since i have no access to storage i tried to adb sideload the LOS i had in before and then just do a freshly install of PPUI. At 47% it says adb: failed to read command: No Error, (mobile mentions a magisk module missing) Any ideas?
Guns&roses said:
Hello! Today i tried Lineage os (came from PPUI) thought it was nice but i wanted to go back for the extra customisation options.
Steps i did: Removed screen locks
Reboot into TWRP recovery
I wiped the Dalvik+ Data+ Cache
Realised my PPUI restore was in the wrong folder and not the TWRP recovery thought i would just reboot and move it to the corect place
Then i got into a bootloop cause i wiped my os. Now phone says storage is encrypted.
Since i have no access to storage i tried to adb sideload the LOS i had in before and then just do a freshly install of PPUI. At 47% it says adb: failed to read command: No Error, (mobile mentions a magisk module missing) Any ideas?
Click to expand...
Click to collapse
You still should be able to access TWRP recovery? You can format data partition there and be able to use internal storage on your next boot to recovery.
From the looks of things i have formated all my storage data in my panic state. Thoughts on moving the Rom to the phone to be installed by recovery?
So as it looks i have nothing into the phone itself and i cant send files from the pc! How would i go about getting the LOS rom to the mobile and flashing from there?
Tried Adb sideload and i get error Magisk addon.d failed can not find magisk binaries. Do i flash magisk first?
Update: I get the rom in. i Flash the rom in. and im still stuck to the LOS loading screen for atleast 5 mins Thoughts?
Fixed. for some reason it was the LOS flash that had issues. when i tried flashing PPUI it worked the first time no issues
Lineage install at 47% for poco
I use lineage recovery and I didn't encounter any magisk thingy. That sound like a previous os persistence script which shouldn't be loaded in the first place....but still did for unknown reason
However, important to note that other user flashed using twrp without issue
Try these steps
1. Format Data
2. Sideload latest firmware
3. Sideload nightly LineageOS
4. Sideload opengapp arm64 (if you are using)
5. Sideload magisk (if you are using)
Boot