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?
Related
I has a pretty big problem of that Crash Dump screen some hours ago and i still can't get to fix it. Here is the story, after trying Havoc 2.0 rom i decided to go back to stock so in TWRP i erased the system, cache (dalvik cache and cache), data and internal storage (i wiped internal storage because TWRP just couldn't decrypt it even though the passwd was correct), after that i flashed the stock OOS rom and the TWRP installer (all these being booted on twrp), but when i rebooted into recovery the twrp splash screen just froze there, so i tried to boot twrp through fastboot, but then the crash dump screen apeared, this post: https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892 said this was a way to recover from that problem so i tried it, it worked as far as booting into OOS is concerned, but when i try to boot into twrp through fastboot the crash dump screen keeps showing up.
Any ideas?
mateuxi said:
I has a pretty big problem of that Crash Dump screen some hours ago and i still can't get to fix it. Here is the story, after trying Havoc 2.0 rom i decided to go back to stock so in TWRP i erased the system, cache (dalvik cache and cache), data and internal storage (i wiped internal storage because TWRP just couldn't decrypt it even though the passwd was correct), after that i flashed the stock OOS rom and the TWRP installer (all these being booted on twrp), but when i rebooted into recovery the twrp splash screen just froze there, so i tried to boot twrp through fastboot, but then the crash dump screen apeared, this post: https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892 said this was a way to recover from that problem so i tried it, it worked as far as booting into OOS is concerned, but when i try to boot into twrp through fastboot the crash dump screen keeps showing up.
Any ideas?
Click to expand...
Click to collapse
Use bluespark twrp not official
ON rom 8.1 best is official twrp
on rom 9.0 best is blues park twrp
yldlj said:
Use bluespark twrp not official
Click to expand...
Click to collapse
akswap said:
ON rom 8.1 best is official twrp
on rom 9.0 best is blues park twrp
Click to expand...
Click to collapse
It worked!
Now i'm installing all my mods again.
Thanks!
UPDATE:
Nevermind, it boots into twrp, but it wont boot OOS, i already tried erasing all the partitions (system, data and cache) and installing OOS and bluspark TWRP.
It turns on, shows the bootloader unlocked screen and then it reboots back to twrp.
UPDATE 2:
Fixed it by erasing all data on oneplus recovery, thanks again, my phone is back from the death (a quite unrooted one).
Fixed it by erasing all data on oneplus recovery, thanks again, my phone is back from the death (a quite unrooted one).
Click to expand...
Click to collapse
When u upgrade from os 8.1 to 9 .0 after flash install blues spark twrp.
When Downgrade 9.0 to 8.1 use official OnePlus6Oxygen_22_OTA_007_all_1805131952_O_MR1.zip
& flash official Twrp & Stable magisk only
for 8.1
1- must have a copy of Oxigen Fastboot ROM 8.1
2- Oxigen 8.1 rom ( Revovery) .zip
3- twrp-installer-enchilada-3.2.3-0zip & img file
for 9.0
4- twrp-3.2.3-x_blu_spark_v9.86_op6.zip & img file
5- magisk 16.7 beta & 17.1 Stable
6- official 9.0 Stable rom
7- tool all in One (PC)
Enjoy flashing
Need some help, I keep getting a infinite boot animation. I tried to install LineageOS (thread) on my G920F three times and let them all boot for about an hour without success.
This is the order of how I flashed it:
1. Wipe Davik, System, Data and Cache
2. Flash the LineageOS zip
3. Flash the Zerofltexx kernel img
4. First try flashed OpenGAPPS, second try flashed MindTheGAPPS and third try didn't flash GAPPS at all
5. Reboot and wait, after an hour still booting
Any idea's of what I'm doing wrong?
Fixed my issue!
Hi!
I had the same issue as you, followed the guides and installed TWRP through ODIN and flashed the OS through TWRP to boot it.
When I booted the device it just got stuck indefinitely on the loading animation (the Lineageos loading logo in my case).
Since you and some others had the same issue as me I assumed it was something to do with a new version of some software.
I resolved the issue by installing an older version of TWRP through ODIN,
I installed the TWRP version 3.2.3.
And then I flashed the same ROM with the GAPPS again.
After the ROM and GAPPS I also flashed MAGISK aswell from the magiskmanager website.
Download the MAGISK Zip.
After I flashed the ROM, GAPPS and MAGISK through the TWRP 3.2.3 it booted as intended.
Hope this works for you aswell!
how long did it take to boot
First Boot needs longer...up to 15 minutes is possible.
solonf
speedson
i have same probleme wtih my samsungs6 g920f i wiil try it ...hope it work ....
Remove the TWRP from the phone via the advance key in TWRP. I had tried several ROMs and Gapps only to get stuck on the boot screen then back to the TWRP screen. Removing the app made my new rom boot in less than 10 seconds.
If you can give us exactly the steps you follow
Lineageos 17 boot animation stuck
krimnian said:
If you can give us exactly the steps you follow
Click to expand...
Click to collapse
Steps (I have followed the instructions to the letter)
Wiped all partitions (advanced wipe)
formatted DATA partition
rebooted back into recovery
installed Lineage 17 and Gapps
Rebooted to system and left it all day, still stuck on boot animation
Tried again without gapps same results
Tried other roms they work, AOSP showing no encryption which works fine
What am I doing wrong? Do I have to flash different kernel? TWRP 3.3.1 installed.
Im using G920L it booting to long then just go to twrp anyhelp?
Helpful
crmcc said:
Remove the TWRP from the phone via the advance key in TWRP. I had tried several ROMs and Gapps only to get stuck on the boot screen then back to the TWRP screen. Removing the app made my new rom boot in less than 10 seconds.
Click to expand...
Click to collapse
this was extremely helpful as soon as i unchecked installing with twrp it worked immediately.
crmcc said:
Remove the TWRP from the phone via the advance key in TWRP. I had tried several ROMs and Gapps only to get stuck on the boot screen then back to the TWRP screen. Removing the app made my new rom boot in less than 10 seconds.
Click to expand...
Click to collapse
Can you explain the process a little?I have flashed lineage os 18.1 in moto g5 plus , but it's stuck on lineage booting animation.
rog__ said:
Can you explain the process a little?I have flashed lineage os 18.1 in moto g5 plus , but it's stuck on lineage booting animation.
Click to expand...
Click to collapse
For reference, formatting data after install seems to often be the solution when flashing a new OS to a Moto G5 Plus.
gamemaster2030 said:
Need some help, I keep getting a infinite boot animation. I tried to install LineageOS (thread) on my G920F three times and let them all boot for about an hour without success.
This is the order of how I flashed it:
1. Wipe Davik, System, Data and Cache
2. Flash the LineageOS zip
3. Flash the Zerofltexx kernel img
4. First try flashed OpenGAPPS, second try flashed MindTheGAPPS and third try didn't flash GAPPS at all
5. Reboot and wait, after an hour still booting
Any idea's of what I'm doing wrong?
Click to expand...
Click to collapse
These steps solved my issue. thanks
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.
Hey, so here is my problem.
A day later i installed Lineage OS 18.1 on my OnePlus 6.
All fine.. until i discovered i can't use my banking app.
So i read here and there that in order to use my banking apps i had to install magisk root etc..
I didn't have TWRP recovery so i decided to install it.
I downloaded the latest TWRP - ( Download twrp-3.6.0_11-0-enchilada.img )
Then i rebooted to Fastboot and typed " fastboot boot twrp-3.6.0_11-0-enchilada.img "
Then the device started to boot into TWRP but just stayed there.
Stayed on the " teamwin Recovery Project 3.6.0_11-0 " booting screen.
That's it... I thought that i somehow bricked it but it works normaly i just restarted it by holding the Power button.
I tried 2 times and same problem.
Can someone help?
Vankata958 said:
Hey, so here is my problem.
A day later i installed Lineage OS 18.1 on my OnePlus 6.
All fine.. until i discovered i can't use my banking app.
So i read here and there that in order to use my banking apps i had to install magisk root etc..
I didn't have TWRP recovery so i decided to install it.
I downloaded the latest TWRP - ( Download twrp-3.6.0_11-0-enchilada.img )
Then i rebooted to Fastboot and typed " fastboot boot twrp-3.6.0_11-0-enchilada.img "
Then the device started to boot into TWRP but just stayed there.
Stayed on the " teamwin Recovery Project 3.6.0_11-0 " booting screen.
That's it... I thought that i somehow bricked it but it works normaly i just restarted it by holding the Power button.
I tried 2 times and same problem.
Can someone help?
Click to expand...
Click to collapse
Read my post
Restoring data from stock 11.1.1
Hi, So it seems when i restore data via TWRP it triggers the protection which encrypts the whole sdcard, can this be avoided? Here are the steps i did: Full wipe fastboot boot twrp (Nebrassy) sideload stock 11.1.1 sideload magdisk Finished...
forum.xda-developers.com
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.