I have Moto G 2014 Xt1068
I unlocked the bootloader, rooted, flashed CM13 (it was working perfectly) and tried to update SuperSu. It wouldn't work so I tried to flash it and then got stuck in a boot loop.
What can I do?
I have not done anything since then so as not to mess up further.
Thanks.
TheSaffronArmy said:
I have Moto G 2014 Xt1068
I unlocked the bootloader, rooted, flashed CM13 (it was working perfectly) and tried to update SuperSu. It wouldn't work so I tried to flash it and then got stuck in a boot loop.
What can I do?
I have not done anything since then so as not to mess up further.
Thanks.
Click to expand...
Click to collapse
Which SuperSU did you flash?
You have to flash the builds after 2.60
Here the latest : Click Here
Remember you need to flash SuperSU again after each cm update.
sagar846 said:
Which SuperSU did you flash?
You have to flash the builds after 2.60
Remember you need to flash SuperSU again after each cm update.
Click to expand...
Click to collapse
I reflashed CM13 and this got me out of the bootloop. Also, I think I had flashed the latest version of SuperSu. However, now I have found the root options on CM13 and I don't think I really need SuperSu.
Thanks for your help!
This just started a couple days ago. I rebooted the phone after SuperSU updated its binary, and the phone would not boot past the "starting apps" screen. I've tried everything I can think of - disabling systemless root and Xposed, upgrading CM 13, downgrading it, wiping everything and doing a fresh install, restoring stock 20i with TWRP and reinstalling CM... nothing works. It either hangs on the boot animation or the "starting apps" screen. I finally managed to get stock 20o loaded with the KDZ method and everything seems to work, but I would really like to have CM back. Can anyone help?
Same issue here, was running resurrection remix, powered off to swap battery and stuck at starting apps. Went back to stock and it works.
I had the same issue after updating the SuperSU binary following the flash of the latest nightly. Here is what I did to get CM13 back:
Flashed 20o kdz via LGUP - http://forum.xda-developers.com/g4/help/lgup-install-kdz-mm-lp-t3249803
Booted Stock Rom - Set Developer options on and enable OEM unlocking and USB debugging
Added TWRP - http://forum.xda-developers.com/tmo...ck-guide-h811-20-o-bootloader-unlock-t3421589
Booted Stock Rom
Reboot to Recovery
Flashed CM13 via TWRP
Booted CM13
Enabled Developer options ensured OEM unlock and Usb debugging were enabled (Debugging was for Titanium Backup). Also, extended boot menu (for ease)
Reboot to Recovery flash additional items (SuperSU, Gapps, Xposed) Note: I flashed each one individually and booted (wanted to check each for functionality after this mess)
Let me know if you have questions, I'll be happy to try and help.
Cheers!
My phone is functional again, I didn't notice originally but even with the stock flash I had no sound, sensors or camera. I ended up flashing the KDZ and reinstall RR and everything is normal again. Follow the step Surly33 posted and you should be fine.
Thanks a TON surly33 and Pantslessape !!!!
Struggled all day yesterday and half of today, trying to get it working again...
Wonder what was the problem?
I wonder if something changed in SuperSU 2.78 and we should stick with 2.76.
Thanks Surly33, I will try it and see how it goes.
I flashed CM and GApps, and all seems to be working. Gonna try it with just the stock su for now. Thanks
Worked like a charm
Surly33 said:
I had the same issue after updating the SuperSU binary following the flash of the latest nightly. Here is what I did to get CM13 back:
Flashed 20o kdz via LGUP - http://forum.xda-developers.com/g4/help/lgup-install-kdz-mm-lp-t3249803
Booted Stock Rom - Set Developer options on and enable OEM unlocking and USB debugging
Added TWRP - http://forum.xda-developers.com/tmo...ck-guide-h811-20-o-bootloader-unlock-t3421589
Booted Stock Rom
Reboot to Recovery
Flashed CM13 via TWRP
Booted CM13
Enabled Developer options ensured OEM unlock and Usb debugging were enabled (Debugging was for Titanium Backup). Also, extended boot menu (for ease)
Reboot to Recovery flash additional items (SuperSU, Gapps, Xposed) Note: I flashed each one individually and booted (wanted to check each for functionality after this mess)
Let me know if you have questions, I'll be happy to try and help.
Cheers!
Click to expand...
Click to collapse
So happy that Xda developed me into someone who could help others! Cheers family!
Mogster2K said:
I flashed CM and GApps, and all seems to be working. Gonna try it with just the stock su for now. Thanks
Click to expand...
Click to collapse
Also, on SuperSU 2.78 with no issues
Surly33 said:
Also, on SuperSU 2.78 with no issues
Click to expand...
Click to collapse
i wonder what went wrong
Mogster2K said:
This just started a couple days ago. I rebooted the phone after SuperSU updated its binary, and the phone would not boot past the "starting apps" screen. I've tried everything I can think of - disabling systemless root and Xposed, upgrading CM 13, downgrading it, wiping everything and doing a fresh install, restoring stock 20i with TWRP and reinstalling CM... nothing works. It either hangs on the boot animation or the "starting apps" screen. I finally managed to get stock 20o loaded with the KDZ method and everything seems to work, but I would really like to have CM back. Can anyone help?
Click to expand...
Click to collapse
So I had this same problem happen to me. I happened to have a complete TWRP backup including all partitions from right after I unlocked the SIM and bootloader. I wiped everything including the SD Card then restored the backup and it's still having issues.
After restoring the backup I was able to get the SlimROM to boot but during the setup the phone locks up. I will try reinstalling Cyanogenmod to see if I encounter the same problem with that, but it doesn't seem like SuperSU 2.78 is the common denominator because I was running that version since it's release and only started having problems yesterday.
Meh Same here
Was running the nightly from 160920, had downloaded but not installed latest nightly 160930, before I had a chance to install it, phone locked up. Figured ok, maybe something I flashed? ( although last thing I flashed and or changed was on the 21st) so reflashed my previous backup of CM13 with just Cm13 installed, no extras or additions, and phone locked up again.
Stuck at the Starting apps screen.
Recharging my battery now and gonna reflash stock which Suuuuuuuuuuxxxxxxxxxxxxx :crying:
Meh dbl meh.
Anybody figure it out yet?
shadow813 said:
Was running the nightly from 160920, had downloaded but not installed latest nightly 160930, before I had a chance to install it, phone locked up. Figured ok, maybe something I flashed? ( although last thing I flashed and or changed was on the 21st) so reflashed my previous backup of CM13 with just Cm13 installed, no extras or additions, and phone locked up again.
Stuck at the Starting apps screen.
Recharging my battery now and gonna reflash stock which Suuuuuuuuuuxxxxxxxxxxxxx :crying:
Meh dbl meh.
Anybody figure it out yet?
Click to expand...
Click to collapse
This happened to me when I flashed the CM 20160929 nightly on top of the 20160928 nightly. I was encrypted and I had been running SuperSU 2.78 since it released. Updating my phone to the 20o base fixed the problem and I took the opportunity to switch to the SlimROM6 port since CM decided they don't really want to get around to release a stable build of CM13 so that bug reports can be submitted. At least now I can toggle data on and off in the quicksettings pulldown. The downside is I have to re-setup all my accounts and stuff but on the upside I had been meaning to do this anyway as I encrypted and TWRP still can't decrypt properly (amongst other time zone bugs) to run backups and such.
I was on Stock 20i before I initially installed CM 13. Maybe something changed in CM 13 so that it won't boot unless Stock 20o gets installed. I know there's more to it than just the boot and system images that custom ROMs use. (I count 57 separate partitions and I have no idea what most of them do.) The Stock 20o KDZ seems to contain 27 of them.
I was on Stock 20i before I initially installed CM 13. Maybe something changed in CM 13 so that it won't boot unless Stock 20o gets installed. I know there's more to it than just the boot and system images that custom ROMs use. (I count 57 separate partitions and I have no idea what most of them do.) The Stock 20o KDZ seems to contain 27 of them.
Click to expand...
Click to collapse
I think there was a boot loader compatibly issue with SuperSU and 20i. But, that is just a guess.
Surly33 said:
I had the same issue after updating the SuperSU binary following the flash of the latest nightly. Here is what I did to get CM13 back:
Flashed 20o kdz via LGUP - http://forum.xda-developers.com/g4/help/lgup-install-kdz-mm-lp-t3249803
Booted Stock Rom - Set Developer options on and enable OEM unlocking and USB debugging
Added TWRP - http://forum.xda-developers.com/tmo...ck-guide-h811-20-o-bootloader-unlock-t3421589
Booted Stock Rom
Reboot to Recovery
Flashed CM13 via TWRP
Booted CM13
Enabled Developer options ensured OEM unlock and Usb debugging were enabled (Debugging was for Titanium Backup). Also, extended boot menu (for ease)
Reboot to Recovery flash additional items (SuperSU, Gapps, Xposed) Note: I flashed each one individually and booted (wanted to check each for functionality after this mess)
Let me know if you have questions, I'll be happy to try and help.
Cheers!
Click to expand...
Click to collapse
Haha, this happened to me like 3 weeks ago too. I ended up doing this after like 3 hours of messing around with the phone. I wish i would have just saw this instead of figuring it out on my own haha
So i sucessfully rooted my Huawei P8 Lite and installed TWRP. Then i tried to install Xposed v.89 for sdk23 (Android 6.0). The installation worked and it rebooted sucessfully, but after i installed the App on my phone it said xposed framework is installed but not active. So i tried to reboot my phone once more and this is when my phone started to be stuck in the huawei starting logo. I revoked everything and tried it a couple of times again and tried v85. It didnt change anything.
Can anyone help me with this because the virtual sensor module doesnt work without xposed framework being active and i just cant find a way to get it active and have the phone not get stuck while starting
My Huawei p8 Lite is running on android 6.0 with an ARM64 CPU
I hope anyone can help me with this.
Have you tried the uninstall zip?
You also shouldn't install a different Xposed zip if the one meant for your version didn't work. The others definitely won't work then.
Also, did you install any modules and tried to activate them? Maybe the module you activated is what caused the bootloop.
Sent from my Nexus 6P using Tapatalk
I've been trying to hide root from an app with no luck from xposed and root cloak (and many other modules in xposed). So I discovered Magisk and decided to give it a go. I followed the instructions in the Magisk thread and unrooted my phone, downloaded Magisk and flashed with TWRP.
After the installation was "successful", I rebooted and just got boot loops after the Sony screen. I couldn't even boot into recovery. I'm assuming the cause of this was because I didn't have a stock kernel (I missed that part in the instructions lol). Anyway, to fix the boot loops, I flashed the kernel boot.img with fastboot.
I then tried installing Magisk with boot bridge, but got the exact same result.
So I'm gonna assume I need to go back to the stock kernel to install Magisk. Can someone help me with this? Or just point me in the right direction to installing Magisk? Would be very appreciated, cheers.
Phone info:
Xperia Z1 - C6903
5.1.1
14.6.A.1.236
using Kryptonian kernel
bootloader unlocked
Hi, i had installed TWRP and magisk in few months ago, and for some reason, i installed stock rom file on my device. But I realized that my device got unrooted.
So, i flashed the same twrp.tar that i used before, now my device keeps booting into twrp (even when i select reboot>system)
Help me, thx