Database Users

Stuck at boot animation

I do not know if this question has been brought up before, but I am in desperate need of an answer. I recently got my 6P and immediately proceeded to unlock the bootloader and flash TWRP to start loading custom roms. I decided to start use Pure Nexus with it's accompanying gapps package but when I go to reboot the device, I am stuck at the circles boot animation. I decide to try CM13 nightlies and the same problem occurs. After searching online for some time, I realize I needed to flash a SuperSU file from recovery that flashes a custom boot.img. I flash Version 2.66 and restart the device. After 5+ minutes on the boot screen, I decided I am stuck still. What do I need to do, I am unable to boot the device.
Thanks.

I'd use Nexus Root Toolkit to unbrick your phone just so that it is working to start with. Then follow the steps more closely for installing a rom. You'll be doing something wrong, I've had no issues!! Best of luck with this.

hmm I'm not sure. this is happening to me right now as I try to restore my backups... maybe has to do with twrp's system handling/mounting, but I just don't know.

New to the 6P, how to run a rooted N preview and use Xposed ?

I just got my 64GB Aluminum Nexus 6P last night
I enrolled in the N developer preview and running it stock, to test it out, but I need root, and stuff. Couple questions;
- So how do I go about running the latest Developer 4 preview rooted ?
- Does Xposed work on the N Preview ?
Do I go about the normal method of unlocking the phone, rooting it, and installing TWRP first, and then flash an N ROM ? Or is there some specific radio, firmware or modem I need first before flashing an N ROM ?
No idea, but does Xposed even work on these N Previews ? I am guessing that's a NO, or slight maybe ? But then again Xposed needs a stable release of N released first with the source code, before Xposed can be made to work on it ?

PLEASE HELP:
Ok need a little help, I am following the excellent video by Rootjunky ( thank you ), and got through the unlocked bootloader part easily, and now installed TWRP Recovery, but upon first time booting into TWRP, it's just sitting at the Blue and Gray teamwin screen, and not doing anything else, it's not actually entering into the Recovery, to see the list of options, etc...
I powered the device down, and started up again in Fastboot mode, then chose Recovery, and does the same again, just sits at the blue gray colored teamwin screen, and does nothing.
What happened ?
UPDATE:
I powered the device down / off. Then started up again, it went and booted up, to the fresh clean Android N DP 4. But I am not rooted at all yet, due not being able to fully enter Recovery and flash the SuperSU zip yet.

Zorachus said:
PLEASE HELP:
Ok need a little help, I am following the excellent video by Rootjunky ( thank you ), and got through the unlocked bootloader part easily, and now installed TWRP Recovery, but upon first time booting into TWRP, it's just sitting at the Blue and Gray teamwin screen, and not doing anything else, it's not actually entering into the Recovery, to see the list of options, etc...
I powered the device down, and started up again in Fastboot mode, then chose Recovery, and does the same again, just sits at the blue gray colored teamwin screen, and does nothing.
What happened ?
UPDATE:
I powered the device down / off. Then started up again, it went and booted up, to the fresh clean Android N DP 4. But I am not rooted at all yet, due not being able to fully enter Recovery and flash the SuperSU zip yet.
Click to expand...
Click to collapse
Number one xposed will not work at all do not try
You need modified boot. Img for twrp to work thread is in general on here

Boot loop after rooting with Magisk

I am puzzled by what's happening...
We got a new Moto G7 for my wife and following the instructions here https://www.the***********.com/install-twrp-root-moto-g7-plus-guide/, I successfully rooted the phone. However, there was a security update that needed to be installed, so with some great advice from ptn107, see https://forum.xda-developers.com/mo...-trying-to-t3977463/post80429619#post80429619, I flashed the updated ROM onto the phone. (Note that I omitted 'fastboot erase userdata'. Also note that the warning message 'is-logical:<partition>: not found' was seen for all flash commands.)
The phone booted properly after the update, so I then went through the exact same rooting steps that had worked previously. However, this time, the phone gets stuck in a boot loop. I reflashed the ROM and can boot successfully, but the phone is no longer rooted. (I have tried this twice, with Magisk 19.3 and 19.4 - same result.)
Any ideas as to what I may be doing incorrectly? More importantly, what is the best way forward?
Thanks.

im dealing with the same issue. you can flash TWRP and go to advanced, fix boot loop, and that should get it to boot, but then you lose Magisk. May be a verity / checksum issue with the stock ROM. probably an easy fix but I dont have it.
EDIT: also you can flash the stock boot.img back and that will do the same thing, but again you lose Magisk/Root.

I keep loosing root after reboot, Pls help.

Hey guys,
first time posting here so i dont kow how to style the text, so sorry about that.
last time i rooted a phone was on my sony xperia sp , where all i had to do was to go to towelroot .com and click to root.
I tryed to root my OP6T yesterday, after some setbacks i managed to sucessfully do it.
I did it like this:
1. Downloaded full ROM of OOS 10.3.2,
2. copied the payload to a program called payload dumper that extracted the boot image.
3. Copied the boot image to the phone
4. opened Magisk manager and selected install from source where i chose the boot.img
5. it created a copy called magisk_patched.img
6. booted in fastboot
7. on my pc used the command prompt to "fastboot boot magisk_patched.img"
booted normally and i had root.
but then problem appeared
#Problem 1
everytime i rebooted my phone i would loose root and it would say Magisk not installed. To get it back i would need to perform step 7 again and it was not ideal to do that everytime i turned off my phone.
#Problem 2
While tryng to solve problem 1 i read that i needed to open magisk manager and "Install to Inactive Slot (After OTA)."
After doing that it rebooted but now it wont boot at all, even if i try to "fastboot boot magisk_patched.img" the cmd gives me error:
fastboot boot magisk_patched.img
downloading 'boot.img'...
OKAY [ 0.838s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.845s
now my phone is just sitting there i dont want to reset it again. it would be the 4th time that i need to set up my phone in 2 days, so im trying to see if there are alternatives.
If reset is really the only way, i read that with root you can make a full backup of your phone and then restore it. How to do that? can i do it in the situation im in?
How can i root my OP6T running OOS10.3.2, and keep it? Whats the right method bc the one i followed seemed flawed.
I also tried one that had TWRP but maybe i did something wrong bc it didnt work., also there is no official one working for 10.3.2.

What is happening is normal with those instructions (they aren't right).
All you need to do is install TWRP. Do not use the official one, it is out of date. Use TWRP from this thread Link here. The TWRP from that thread is from the official maintainer. It works fine with OOS 10.
- You need to get the phone in fully working order again. Which may mean you need to use the fastboot ROM, as you've probably "goofed" something up at this point. (no offense meant). Make sure your phone boots and such after this.
- For OOS 10 with the phone in fastboot, fastboot boot recoveryimgfilename.img (<-- For OOS 10 you will need TWRP 3.3.1-32 Q Unofficial by mauronofrio from the thread I linked to above) This will boot to TWRP.
- Now run TWRP 3.3.1-32 Unofficial Installer by mauronofrio this will install TWRP. The installer is the same for Android 9 and 10, doesn't matter.
- Once the installer runs, click back, choose reboot to recovery. If you boot to the system, you have to start over. Reboot to recovery!
- Install Magisk 20.3 <-- The current version. The official download page. After that you can reboot to the system. You should now have a rooted, phone with Magisk, and TWRP installed.
Any questions ask.

OhioYJ said:
What is happening is normal with those instructions (they aren't right).
All you need to do is install TWRP. Do not use the official one, it is out of date. Use TWRP from this thread Link here. The TWRP from that thread is from the official maintainer. It works fine with OOS 10.
- You need to get the phone in fully working order again. Which may mean you need to use the fastboot ROM, as you've probably "goofed" something up at this point. (no offense meant). Make sure your phone boots and such after this.
- For OOS 10 with the phone in fastboot, fastboot boot recoveryimgfilename.img (<-- For OOS 10 you will need TWRP 3.3.1-32 Q Unofficial by mauronofrio from the thread I linked to above) This will boot to TWRP.
- Now run TWRP 3.3.1-32 Unofficial Installer by mauronofrio this will install TWRP. The installer is the same for Android 9 and 10, doesn't matter.
- Once the installer runs, click back, choose reboot to recovery. If you boot to the system, you have to start over. Reboot to recovery!
- Install Magisk 20.3 <-- The current version. The official download page. After that you can reboot to the system. You should now have a rooted, phone with Magisk, and TWRP installed.
Any questions ask.
Click to expand...
Click to collapse
So getting it straight, i need to first reset my phone and then do the steps you described.
Can i backup the data first with TWRP to restore it later and avoid setting up everything again?

Davide1713 said:
So getting it straight, i need to first reset my phone and then do the steps you described.
Can i backup the data first with TWRP to restore it later and avoid setting up everything again?
Click to expand...
Click to collapse
Supposedly. I've never used that function of TWRP. Some people have luck with, some people restore things that shouldn't be restored and end up having to wipe the phone again. Personally I just use TitaniumBackup like I always have. I would search for information on that in the TWRP thread if you want to try method. I don't know enough on that to provide solid information.

OhioYJ said:
Supposedly. I've never used that function of TWRP. Some people have luck with, some people restore things that shouldn't be restored and end up having to wipe the phone again. Personally I just use TitaniumBackup like I always have. I would search for information on that in the TWRP thread if you want to try method. I don't know enough on that to provide solid information.
Click to expand...
Click to collapse
Hey man,
Thank you so much. It worked and i stay rooted even after reboot.
May i ask how you use the Titanium Backup, i think back in the days all i used it for was uninstalling system apps. Or if you know some nice guides. If you know other good things to checkout now that i have root i would appreciate it, i have been far away from rooting for too long.
Once again thank you so much

Davide1713 said:
Hey man,
Thank you so much. It worked and i stay rooted even after reboot.
May i ask how you use the Titanium Backup, i think back in the days all i used it for was uninstalling system apps. Or if you know some nice guides. If you know other good things to checkout now that i have root i would appreciate it, i have been far away from rooting for too long.
Click to expand...
Click to collapse
I use it to back up app and app data primarily. It allows me to restore data to apps after a clean install. Since I have the Pro version it's just a batch action (one click essentially). There is also a way to create a flashable .zip you can use in TWRP, although I haven't tried that method, as I'm typically not restoring apps, just data. I also use it remove apps from time to time.

OhioYJ said:
I use it to back up app and app data primarily. It allows me to restore data to apps after a clean install. Since I have the Pro version it's just a batch action (one click essentially). There is also a way to create a flashable .zip you can use in TWRP, although I haven't tried that method, as I'm typically not restoring apps, just data. I also use it remove apps from time to time.
Click to expand...
Click to collapse
Hey man, im sorry i am once again in need.
Idk why but at first i can reboot the system normally without issues. but after a while once i set up everything it just doesnt boot anymore. Am i missing something? do i have to do anything with magisk? download a module or something?
Could it be that google security update is the fault?

Davide1713 said:
Hey man, im sorry i am once again in need.
Idk why but at first i can reboot the system normally without issues. but after a while once i set up everything it just doesnt boot anymore. Am i missing something? do i have to do anything with magisk? download a module or something?
Could it be that google security update is the fault?
Click to expand...
Click to collapse
When you installed everything originally did you fix everything with a clean install? Both slots are the same version of Android? (Like you don't have something weird going on like Android 9 on one and Android 10 on another?)
You definitely have something abnormal going on. There shouldn't be anything in Magisk that you have to do, at least not to prevent crashing. I normally hide it, but that has to do with keeping apps from detecting root.

OhioYJ said:
When you installed everything originally did you fix everything with a clean install? Both slots are the same version of Android? (Like you don't have something weird going on like Android 9 on one and Android 10 on another?)
You definitely have something abnormal going on. There shouldn't be anything in Magisk that you have to do, at least not to prevent crashing. I normally hide it, but that has to do with keeping apps from detecting root.
Click to expand...
Click to collapse
I got it to boot by uninstalling magisk,
I am 100% sure i dont have two different version of android in different slots, bc yesterday i was in big trouble and nothing was working and i flashed on both slots the same version of android 10(dont remember exactly wich one as i tried a couple, but they were the same).
Today when i couldnt boot anymore i went into stock recovery, factory reset -> when it booted i placed the stockOS.zip file in the phone and applied update from local file -> after that i factory reset again from the system settings, so i think the phone should have installed it properly.
Only after that i did what you told me and installed TWRP and Magisk. and as i said it worked and i could restart my device etc..
After a while when i restarted i couldnt boot anymore and went to bootloader. Removing Magisk fixed it,apperantly on install magisk creates a copy of the boot.img that it restores on uninstall, and i booted to system.
Now i can use my phone but dont have root.
Im very thankful for you being there and helping me out trough this, i cant thank you enough

GuestD2272 said:
I got it to boot by uninstalling magisk,
I am 100% sure i dont have two different version of android in different slots, bc yesterday i was in big trouble and nothing was working and i flashed on both slots the same version of android 10(dont remember exactly wich one as i tried a couple, but they were the same).
Today when i couldnt boot anymore i went into stock recovery, factory reset -> when it booted i placed the stockOS.zip file in the phone and applied update from local file -> after that i factory reset again from the system settings, so i think the phone should have installed it properly.
Only after that i did what you told me and installed TWRP and Magisk. and as i said it worked and i could restart my device etc..
After a while when i restarted i couldnt boot anymore and went to bootloader. Removing Magisk fixed it,apperantly on install magisk creates a copy of the boot.img that it restores on uninstall, and i booted to system.
Now i can use my phone but dont have root.
Im very thankful for you being there and helping me out trough this, i cant thank you enough
Click to expand...
Click to collapse
Not sure if you're still having this issue but I'll post the solution just in case anyone gets stumped, does a google search, and comes across this post. You were using the wrong command.
"fastboot boot" just lets you boot with the img so you can verify that root works.
"fastboot FLASH boot" will flash it and root will stick after reboot.
No need to jump through hoops with TWRP and such.

Whats happened with my J5? Need Help guys Sorry (CustomROM)

My device is a J530F (J5 2017).
Im using custom roms for years, but now im deparated with a situation that I don’t understand.
I decided to back to my StockRom (J530FXXS7CTG2_J530FBTU7CTG1_BTU) via Oddin because the CustomRom im using doesn’t have GooglePlayServices (crDroidAndroid-10.0-20210418-j5y17lte-v6.17 flashed with OrangeFox Recovery). PS: This CustomRom is 64Bits, do u think that changed or damaged something in my device?
So, for the 1st time I haved some troubles during the flash stockrom but with few tryes I solved.
When Im back to my StockRom, im surprised to see that my CTS Profile is false and GooglePlay non-certified device. (I think is not normal)…
I rooted the device with magisk for solve this problem and in fact, I solved the Cts Profile but Google Play keeps say that non-certified device. (I searched for Netflix on google play and appear to me so its fine…)
My next step was Reboot in Recovery to flash custom rom. I turn off and turn on with Power, Volume+ and HomeButton. Recovery don’t appear and hes reboot to system mod… So I opened magisk and click Reboot to Recovery but hes turn off and reboot in system mod again… (wtf? -.-‘).
So I have to flashed the TWRP throw Oddin (again) to reboot to recovery. In TWRP I Wiped (Dalvik/Art Cache; System; Data; Internet Storage; Cache) and swipe. Next step was flash new CustomRom (PROMETHEUS_V3_G610X_ARM64 based on A730FXXU6CSJ2)… After flash, when phone rebooted hes show SAMSUNG GALAXY J5 LOGO and then Black Screen (No Samsung Logo) and do not do nothing. (I waited 45min… was the Binary that cause the error??... Was because is 64bits rom? IDK)…
So I repeat all process, go into Download Mode, flashed StockRom, rooted again and flash another CustomRom (PrometheusOneUI V2.0 based on A600FNXXU3BSC5 by Ananjaser1211 @xda-developers That im sure that works on my device because I used during like 1 year). After flash and reboot, the device turn on with Samsung Galaxy J5 and black screen again.
So in conclusion, I cant install custom roms now and don’t know why… somebody can help me?? I don’t tried the same process with OrangeFox twrp because don’t feel that make different but whos know…
Sorry for the long text and bad English, but I did my best for sure…