Database Users

[Q] Cannot re root after 4.4.3 upgrade

Hi,
I previously had purity rom on my nexus 10. I decided to back to stock and use the xposed framework. So with 4.4.3 I flashed the stock images (manualy so it didn't wipe my sdcard partition), wiped data, cache and dalvick.
Stock 4.4.3 works fine, no issues here, but in acquiring root by flashing supersu update (both 93 and 99r3) root doesn't seem to stick. I can adb in and su from terminal, but when booting android supersu days it couldn't acquire root. I have tried other clockworkmod recovery and team win recovery so see if it was a bug with recovery, but no dice. Clockwork did occasionally say it lost root and press Yes to put it back, it did this on my nexus 5 and I still kept root.
I have even tried the universal nexus toolkit but that didn't work either. All methods I have tried have run the zip output fine, saying success.
Any ideas what's wrong. I assume I have done something wrong but can't find much information about root not working like this.

Did you try chainfire 2.00?
Link to Chainfire page

Hi,
Some time ago I've faced the same issue as you, what worked for me was using an older supersu flashable zip and after flashing it I flashed the latest. Don't know if it was placebo or something, but always worked for me .
~Lord

I did the exact same couple days ago after running Omnirom. I used this odex stock image http://forum.xda-developers.com/showthread.php?t=2529492
After the initial factory wipe I wiped dalvik,cache,data, and flashed SU after flashing the ROM but before reboot. Using latest TWRP. Hope this helps.

Stuck in bootloop after every restart.

Hey guys,
Just installed the latest CM12 ROM from the official site, Installed via TWRP, Done a full wipe, Installed the ROM then flashed the latest GAPPS for CM12, Problem is every time i reboot i get stuck in a bootloop(shows the CM12 face)i have to manually reboot into recovery, Wipe cache and dalvik then reboot, The G2 says "Optimising apps", After its does this the device boots fine and runs fine!
I dont get why it gets stuck in a bootloop every time! Anybody that can shed some light onto this maybe?
Thanks.

There's a bug on CM12 and I read somewhere that is from bootanimation, if you replace the bootanimation then it may fix your problem.
I was facing that problem too and I switched back on a older version 20150128.

yes, in order to fix this problem you can remove or rename a file called bootanimation.zip placed in /system/media/

Thanks guys, Removing the bootanimation.zip seems to have solve the issue. :good:

[root] 900w8 boc1

Has any one successfully rooted I just rooted mine but caused full system crash
LRX21T.G900w8vlu1boc1 [TELUS]

bulldog2000 said:
Has any one successfully rooted I just rooted mine but caused full system crash
LRX21T.G900w8vlu1boc1 [TELUS]
Click to expand...
Click to collapse
G900W8 TLS here too. No problem rooting by installing TWRP and then CFAutoroot through ODIN. The version of CF for 4.4.2 works just fine on 5.

after using CF-root on first boot it went MTP application could not start rebooted cleared the cache after that I got media has stopped and a a few other system errors, I did a Factory reset and issue was resolved and root was maintained

bulldog2000 said:
after using CF-root on first boot it went MTP application could not start rebooted cleared the cache after that I got media has stopped and a a few other system errors, I did a Factory reset and issue was resolved and root was maintained
Click to expand...
Click to collapse
Kingo root works too if you're lazy...

Stock Recovery and issues with TWRP

Sorry I'm on mobile! Poor formating and typing is all my fault
So I'm out of my mind trying to fix and find a guide to fix my issues. This is how it all started
I was running the latest magisk (20.1) and OOS (9.0.17), when I installed Vance through magisk. I didn't read the instructions all the way, so I installed the module, it worked, then I saw that you can uninstall the YouTube system apk then install Vance. I deleted the Vance on my next reboot AND uninstalled YouTube system app, and I got stuck rebooting my phone. I have TWRP installed on my phone, not flashed (I didn't know the issues with TWRP when I installed the zip through TWRP). When it got stuck booting, I flashed magisk Uninstaller and it fixed the issue. I tried to reinstall magisk 20.1, and I got the same issue, stuck at boot. So I was able to go home, and use the oneplus 6t manager found here on the forums, which roots with magisk 18.0, and, it worked! But I couldn't update to the new magisk without it freezing my boot. After some deliberation on it, I decided to wipe my phone to try and fix it, and TWRP was still installed, and all my issues still persisted. After this setback, I found fastboot rom also on xda, and got it working, did an Ota to 9.0.17 from 9.0.16. Everything was working, until I went into my recovery and it wiped my phone. I don't even know where to go from here and I need help. Any and all help would be appreciated!
Edit: I just local upgraded to android 10 oos, and it seems to be fine. I don't know yet fully because I'm not at my house!

My device is stuck at fastboot after rooting it and updating Magisk

I'm a total noob at rooting. I tried rooting my Xiaomi Redmi Note 7 today and everything was going surprisingly well until I decided to reboot my device.
My device is now stuck at fastboot, this may have been caused because I updated Magisk.
I can access TWRP but don't know what to do with it. I don't care about my data, I just want my device to work again.
Could anyone suggest any solutions? Thank you in advance!

Did you try rebooting it fron twrp?. twrp >reboot>reboot into system.

Anon-cross said:
Did you try rebooting it fron twrp?. twrp >reboot>reboot into system.
Click to expand...
Click to collapse
Yeap, didn't work.
I just flashed the stock ROM using MiFlash and it worked fine.
Half a hour later, I messed up again and stuck at fastboot for a second time, so I flashed the stock ROM once again and it works like a charm now.
My second failure made me realize what the problem was (well, kind of).
So, the first time I got a bootloop, I thought that it was due to the fact that I had updated Magisk (I read some similar issues online, that's why I thought so).
But that's not the case because the second time, I installed the latest version of Magisk and the same thing happened.
So, the only action that could have caused the bootloop, which was performed both the first and the second time, is the removal of a system app using System App Remover.
I clearly removed something that I wasn't supposed to. It was one of those system apps but don't know exactly which one cause I removed all of them in bulk and then tried to reboot:
GetApps (com.xiaomi.mipicks)
Games (com.xiaomi.glgm)
Mi Credit (com.xiaomi.payment)
Thanks for helping, I hope my answer helps someone else.
My only problem now, is that I'm unable to install updates to the stock MIUI ROM, but that's fine, rooting the device was worth it anyway.

I faced the same problem today
Install twrp ,root and install system app remover
delete some apps i did not need it
when i reboot the phone stuck at fastboot
I reboot to twrp and do a factory reset, format data didnt help
Return again to recovery and unroot
The phone boot to system
I dont understand why this happened because i
remove the same apps before with xiaomi adb fasboot tools didnt face any problem

Aures Batna said:
I faced the same problem today
Install twrp ,root and install system app remover
delete some apps i did not need it
when i reboot the phone stuck at fastboot
I reboot to twrp and do a factory reset, format data didnt help
Return again to recovery and unroot
The phone boot to system
I dont understand why this happened because i
remove the same apps before with xiaomi adb fasboot tools didnt face any problem
Click to expand...
Click to collapse
Sounds strange.
I thought it was the removal of specific apps, but could it be the System Apps Remover that causes the issue?
I wonder if using Titanium would make any difference but I'm not willing to risk it for a third time, I'm good now.

Test orangefox, maybe the older magisk 19.4 and the magisk module debloater.