Okie dokie, I've installed cm13 after a couple hours of fighting with my phone bootlooping because of random garbage happening, (mostly due to GAPPS related issues). Now I'm bootlooping when I install the a new SuperSU binary.
It is to my understanding the cm13 in general is having issues with superSU, with it failing to install normally and then requiring a installation through recovery which causes a bootloop. I know cm13 does not require SuperSU, but I need to install it to force my selinux status to permissive on boot. Anyone have a workaround?
Current ROM file is cm-13.0-20160321-NIGHTLY-vs985.zip
JaXxz said:
Okie dokie, I've installed cm13 after a couple hours of fighting with my phone bootlooping because of random garbage happening, (mostly due to GAPPS related issues). Now I'm bootlooping when I install the a new SuperSU binary.
It is to my understanding the cm13 in general is having issues with superSU, with it failing to install normally and then requiring a installation through recovery which causes a bootloop. I know cm13 does not require SuperSU, but I need to install it to force my selinux status to permissive on boot. Anyone have a workaround?
Current ROM file is cm-13.0-20160321-NIGHTLY-vs985.zip
Click to expand...
Click to collapse
Why don't you just use the makepermissive.zip? Flash it in recovery and it'll set selinux to permissive... https://www.androidfilehost.com/?fid=24052804347784981
...and FWIW I use cm13 based ROMs(RR, AOKP) and flash the older superuser 2.52 zip(and the "makepermissive" zip if selinux is set to enforcing or else it may boot loop) and everything works fine.
startswithPendswithOOH said:
Why don't you just use the makepermissive.zip? Flash it in recovery and it'll set selinux to permissive... https://www.androidfilehost.com/?fid=24052804347784981
...and FWIW I use cm13 based ROMs(RR, AOKP) and flash the older superuser 2.52 zip(and the "makepermissive" zip if selinux is set to enforcing or else it may boot loop) and everything works fine.
Click to expand...
Click to collapse
I'll try that out after I get out of my current bootloop and let you know if it works xd
startswithPendswithOOH said:
Why don't you just use the makepermissive.zip? Flash it in recovery and it'll set selinux to permissive... https://www.androidfilehost.com/?fid=24052804347784981
...and FWIW I use cm13 based ROMs(RR, AOKP) and flash the older superuser 2.52 zip(and the "makepermissive" zip if selinux is set to enforcing or else it may boot loop) and everything works fine.
Click to expand...
Click to collapse
ok it seems to have worked! thanks!
Did you have the issue where it was telling you it had a secure boot error? I flashed CM13, the 35B stack.. which I believe failed because I didn't have the correct modem... and then supersu and ran into the secure boot problem. Finally got it back into recovery mode.. it refused over and over to go in and just restarted itself. Then I reflashed CM13,then gapps, then tried to 35B stack unsuccessfully again and was about to go update my modem and accidently powered the phone up.. now it's running no problem. I've just been super confused on what actually cause the boot issue.
Blindprophet32 said:
Did you have the issue where it was telling you it had a secure boot error? I flashed CM13, the 35B stack.. which I believe failed because I didn't have the correct modem... and then supersu and ran into the secure boot problem. Finally got it back into recovery mode.. it refused over and over to go in and just restarted itself. Then I reflashed CM13,then gapps, then tried to 35B stack unsuccessfully again and was about to go update my modem and accidently powered the phone up.. now it's running no problem. I've just been super confused on what actually cause the boot issue.
Click to expand...
Click to collapse
That happened to me once while I was troubleshooting by myself, I flashed an incompatible SU binary
JaXxz said:
That happened to me once while I was troubleshooting by myself, I flashed an incompatible SU binary
Click to expand...
Click to collapse
Which version did you end up using? Because I haven't flashed SU on the phone because of this issue.
Blindprophet32 said:
Which version did you end up using? Because I haven't flashed SU on the phone because of this issue.
Click to expand...
Click to collapse
Try this one... https://download.chainfire.eu/752/SuperSU/BETA-SuperSU-v2.65-20151226141550.zip
I just tried it on temasek's cm13 3/21 build and it works fine.
Blindprophet32 said:
Which version did you end up using? Because I haven't flashed SU on the phone because of this issue.
Click to expand...
Click to collapse
2.52 beta, an old one but it works if selinux is set to permissive (at least on my phone it worked)
Blindprophet32 said:
Which version did you end up using? Because I haven't flashed SU on the phone because of this issue.
Click to expand...
Click to collapse
The version that caused the "brick" (not sure if its the correct term) was 2.67 stable
startswithPendswithOOH said:
Try this one... https://download.chainfire.eu/752/SuperSU/BETA-SuperSU-v2.65-20151226141550.zip
I just tried it on temasek's cm13 3/21 build and it works fine.
Click to expand...
Click to collapse
Is your selinux status set to enforced or permissive? I might update my binary to that one
Just intall the latest beta (2.68) and it will work.
JaXxz said:
Is your selinux status set to enforced or permissive? I might update my binary to that one
Click to expand...
Click to collapse
Temasek was set to enforcing
Danilo-Sanchez said:
Just intall the latest beta (2.68) and it will work.
Click to expand...
Click to collapse
I tried to install 2.65 and got a secure boot error. Installed 2.67 and got a bootloop. I recently successfully updated my binary from 2.52 through the app. I'm not sure what version it updated me to though
Related
I have an HTC One M8 with ROM 4.16.1540.8 (5.0.1)
I'm trying to remove my SuperSU app so that i can downgrade it to a lower version(2.20) due to incompatibility with some of my apps (puzzle and dragons).
Bootloader is unlocked and it is s-on.
I have tried removing SuperSU through the app itself by using the reinstall, switch superuser app, and full unroot functions, but everytime I restarted the phone superSU would be back and in version 2.46. I also tried manually deleting the apk and su files in the bin and xbin folders in system using es file explorer but a restart just brought those back too.
Any help would be greatly appreciated. Thanks!
Find the flashable zip for the "older" version and flash in recovery. I would think that should do it.
Hi thanks for the reply.
I flashed superSU 2.23 from recovery, but i got stuck in bootloop. What should i do to fix it? Thanks!
Edit: flashed the updated su back in and got out of it. How do i do the downgrade without a bootloop?
ah46657 said:
Hi thanks for the reply.
I flashed superSU 2.23 from recovery, but i got stuck in bootloop. What should i do to fix it? Thanks!
Edit: flashed the updated su back in and got out of it. How do i do the downgrade without a bootloop?
Click to expand...
Click to collapse
Hmm, wouldn't expect that to happen. Obviously, since I would never intentionally bootloop someone!
Flash the stock ROM or restore stock nandroid. Then flash the desire SuperSU zip. That's the best I can think of.
Make a nandroid backup of your current setup (if you haven't already) to revert to "just in case".
how to unflash supersu zip
redpoint73 said:
Hmm, wouldn't expect that to happen. Obviously, since I would never intentionally bootloop someone!
Flash the stock ROM or restore stock nandroid. Then flash the desire SuperSU zip. That's the best I can think of.
Make a nandroid backup of your current setup (if you haven't already) to revert to "just in case".
Click to expand...
Click to collapse
recently i installed lineage os 14.1 in my device (rooted) and flashed supersu2.79 , but after updating it it 2.82, its showing SU BINARY OCCUPIED , so can i try downgrade supersu by flshing lower version,, if so how should i unflash previous supersu zip help
rajkumar1221 said:
recently i installed lineage os 14.1 in my device (rooted) and flashed supersu2.79 , but after updating it it 2.82, its showing SU BINARY OCCUPIED , so can i try downgrade supersu by flshing lower version,, if so how should i unflash previous supersu zip help
Click to expand...
Click to collapse
So you tried to flash 2.82? I don't think that is the proper way to update. Since you already have SuperSU installed, you should just be able to go into the SuperSU app, and update the binary from there. Or is that what led to the "binary occupied" error?
But back to the basic question, you can't "unflash" SuperSU. You can "dirty flash" Lineage (just wipe cache and dalvik, can keep user data), and that will put you back on the "unrooted" Lineage ROM. Then you should be able to flash SuperSU 2.82 via zip.
redpoint73 said:
So you tried to flash 2.82? I don't think that is the proper way to update. Since you already have SuperSU installed, you should just be able to go into the SuperSU app, and update the binary from there. Or is that what led to the "binary occupied" error?
But back to the basic question, you can't "unflash" SuperSU. You can "dirty flash" Lineage (just wipe cache and dalvik, can keep user data), and that will put you back on the "unrooted" Lineage ROM. Then you should be able to flash SuperSU 2.82 via zip.
Click to expand...
Click to collapse
i unrooted my device now,, should i have to "first root" it with official lineage os extra file addonsu arm and then should i have to flash supersu zip ?
rajkumar1221 said:
i unrooted my device now,, should i have to "first root" it with official lineage os extra file addonsu arm and then should i have to flash supersu zip ?
Click to expand...
Click to collapse
I don't personally use Lineage. I believe you will need to flash both of those, yes.
@redpoint73 , found this script made by osm0sis to "unSU". not sure if is relevant to earlier posts but thought maybe if you havent seen it yet would be worth looking at. maybe could help someone.?
http://forum.xda-developers.com/showthread.php?p=63615067
Hey guys
I installed CM 13.0 (2016/01/02) on my i9300
Then installed GApps and everything was working fine
TWRP Recovery and SU were installed too
When I tried to open SU though (to enable root options) it said that SU Binary was not installed and that I had to manually re-root it
I used the CF-Auto-Root method but I still got the same message
Then I remember that I had installed a Kernel on my S4 i9500 when I had updated it to CM 12.1
So I googled and downloaded SiyahKernel v1.9.1
Now my phone is stuck on the boot-up. I get the S3 logo, then a purple eye and then a blank screen
I tried booting into recovery and reinstalling CM 13 but it just closes after displaying "Installing update"
Download mode re-rooting doesn't remove the kernel
Another website suggested I use another kernel but I wanted to get help before I did any more stupid things
Any help is appreciated
Joserin said:
Hey guys
I installed CM 13.0 (2016/01/02) on my i9300
Then installed GApps and everything was working fine
TWRP Recovery and SU were installed too
When I tried to open SU though (to enable root options) it said that SU Binary was not installed and that I had to manually re-root it
I used the CF-Auto-Root method but I still got the same message
Then I remember that I had installed a Kernel on my S4 i9500 when I had updated it to CM 12.1
So I googled and downloaded SiyahKernel v1.9.1
Now my phone is stuck on the boot-up. I get the S3 logo, then a purple eye and then a blank screen
I tried booting into recovery and reinstalling CM 13 but it just closes after displaying "Installing update"
Download mode re-rooting doesn't remove the kernel
Another website suggested I use another kernel but I wanted to get help before I did any more stupid things
Any help is appreciated
Click to expand...
Click to collapse
Looks like you totally screwed it up. Siyah on CM13?! you gotta be kidding me. Never ever install siyah again unless you're on stock ROM. Now I recommend 2 methods to you:
1. Backup efs and put it on your PC if you didn't back it up before. Full wipe your phone using twrp. Then extract the CM13 zip file on your PC then grab the boot.img file to an SD and put it on your phone and flash it using twrp. It will recover the stock CM13 kernel and then try to flash your CM13 zip. Better to download the updated ones. Be sure to use the latest twrp. And always use CM13 official root in developer options, trust me it's better.
2. If you couldn't flash CM13 again the only way I recommend is to flash stock using odin and then flash from the ground and bring your phone up.
JohnSmit268 said:
Looks like you totally screwed it up. Siyah on CM13?! you gotta be kidding me. Never ever install siyah again unless you're on stock ROM. Now I recommend 2 methods to you:
1. Backup efs and put it on your PC if you didn't back it up before. Full wipe your phone using twrp. Then extract the CM13 zip file on your PC then grab the boot.img file to an SD and put it on your phone and flash it using twrp. It will recover the stock CM13 kernel and then try to flash your CM13 zip. Better to download the updated ones. Be sure to use the latest twrp. And always use CM13 official root in developer options, trust me it's better.
2. If you couldn't flash CM13 again the only way I recommend is to flash stock using odin and then flash from the ground and bring your phone up.
Click to expand...
Click to collapse
It's okay I fixed it. I installed QS i9300 and then re-flashed CM and GApps. But the SuperSU is still bugged
A cursory reading said that CM is auto-rooted on stable versions and there is no stable version of CM 13 for the i9300 yet so I guess that might be the issue. The phone's working fine now, just no root access :3
Joserin said:
It's okay I fixed it. I installed QS i9300 and then re-flashed CM and GApps. But the SuperSU is still bugged
A cursory reading said that CM is auto-rooted on stable versions and there is no stable version of CM 13 for the i9300 yet so I guess that might be the issue. The phone's working fine now, just no root access :3
Click to expand...
Click to collapse
You read it wrong. It already have internal root. Go to setting--> about device and then tap build number constantly to enable developer settings. There you can find root access options. Turn it on for apps only or adn and apps and done.
Thank me if I helped you.:good:
JohnSmit268 said:
You read it wrong. It already have internal root. Go to setting--> about device and then tap build number constantly to enable developer settings. There you can find root access options. Turn it on for apps only or adn and apps and done.
Thank me if I helped you.:good:
Click to expand...
Click to collapse
I already did that.. Root Checker Basic says I do not have proper root access and the TWRP Manager tool also says I do not have root
It is really weird. I'm on i9300 official nightlies and have working root!
I rooted my S3 with this (by m0xx) https://download.chainfire.eu/229/CF-Root/CF-Auto-Root/CF-Auto-Root-m0-m0xx-gti9300.zip
I downloaded the 20160102 Nightly from this website https://download.cyanogenmod.org/?device=i9300
GApps from this website (ARM, 6.0, Stock) http://opengapps.org/
and TWRP via ODiN with https://twrp.me/devices/samsunggalaxys3internationalexynos.html (twrp-2.8.6.1-i9300.tar)
Idk if I did anything wrong or downloaded an older version... I know there's TWRP 2.8.7 but I dunno how to install the img file, I knew tar would be compatible with ODiN
Joserin said:
I rooted my S3 with this (by m0xx) https://download.chainfire.eu/229/CF-Root/CF-Auto-Root/CF-Auto-Root-m0-m0xx-gti9300.zip
I downloaded the 20160102 Nightly from this website https://download.cyanogenmod.org/?device=i9300
GApps from this website (ARM, 6.0, Stock) http://opengapps.org/
and TWRP via ODiN with https://twrp.me/devices/samsunggalaxys3internationalexynos.html (twrp-2.8.6.1-i9300.tar)
Idk if I did anything wrong or downloaded an older version... I know there's TWRP 2.8.7 but I dunno how to install the img file, I knew tar would be compatible with ODiN
Click to expand...
Click to collapse
If twrp offers to root then don't do that method. Flash superSU 2.4.6.zip and on reboot you will see the app logo in your drawer or if not there it will be above developer options in settings. Open and allow it to update binary.
kush2.0 said:
If twrp offers to root then don't do that method. Flash superSU 2.4.6.zip and on reboot you will see the app logo in your drawer or if not there it will be above developer options in settings. Open and allow it to update binary.
Click to expand...
Click to collapse
Already tried that. SU binary just doesn't update. I even downloaded the Update zip and flashed from recovery, it still asks to update the binary after reboot. There is no TWRP option to update the binary either, it directly goes to the normal method and fails everytime. Tried like 20 times probably
I'd say flash back to stock and start over. Installing siyah probably borked something.
shivadow said:
I'd say flash back to stock and start over. Installing siyah probably borked something.
Click to expand...
Click to collapse
The only reason I installed Siyah was because the binary wasn't installed. Multiple attempts to root didn't fix the issue.
Also I did flash stock ROM because after installing Siyah the phone wouldn't go past the S3 logo screen
What recovery version are you using then?? ??
---------- Post added at 04:02 PM ---------- Previous post was at 03:58 PM ----------
Joserin said:
The only reason I installed Siyah was because the binary wasn't installed. Multiple attempts to root didn't fix the issue.
Also I did flash stock ROM because after installing Siyah the phone wouldn't go past the S3 logo screen
Click to expand...
Click to collapse
I really dont thing a custom kernel for cm13 aosp roms exists for sgs3 gti9300
kush2.0 said:
What recovery version are you using then?? ??
Click to expand...
Click to collapse
kush2.0 said:
What recovery version are you using then?? ??
---------- Post added at 04:02 PM ---------- Previous post was at 03:58 PM ----------
I really dont thing a custom kernel for cm13 aosp roms exists for sgs3 gti9300
Click to expand...
Click to collapse
Yea I didn't know that before I installed it (it was 3 AM I was frustrated at SU)
Current TWRP version is 2.8.6.1
Joserin said:
Yea I didn't know that before I installed it (it was 3 AM I was frustrated at SU)
Current TWRP version is 2.8.6.1
Click to expand...
Click to collapse
Personally I would download twrp manager from play store if you havnt already got it. Flash/install twrp 2.8.7.X and boot into the newer twrp and flash superSU 2.4.6.zip. Try that before going back to stock.
kush2.0 said:
Personally I would download twrp manager from play store if you havnt already got it. Flash/install twrp 2.8.7.X and boot into the newer twrp and flash superSU 2.4.6.zip. Try that before going back to stock.
Click to expand...
Click to collapse
Uhm TWRP Manager doesn't work without root. Already tried that
@Joserin, you did your very best to make it complicated. Go back to firmware to get a clean base, as said several times before. Firmware doesn't mean a Touchwiz-based custom-ROM! Download it from sammobile.com and follow the instructions on downloadsite.
Joserin said:
Uhm TWRP Manager doesn't work without root. Already tried that
Click to expand...
Click to collapse
Yeah sorry you do need root access. Your probably better of doing what rp158
Said. Your twrp recovery isn't up to date enough to install a new cm13 based ROM.
rp158 said:
@Joserin, you did your very best to make it complicated. Go back to firmware to get a clean base, as said several times before. Firmware doesn't mean a Touchwiz-based custom-ROM! Download it from sammobile.com and follow the instructions on downloadsite.
Click to expand...
Click to collapse
Meh Id rather just let it be for what it is. It's my dad's phone and I just wanted him to have AdAway, he's not much of a tech-head.
Thanks people
No root access to S3 when upgraded to CM 13; affecting full access Ext SDcard
Before upgrading to CM 13 for my I 9300 (Int) I was on CM 11 and I had full root access on my device.
In fact I still have that recovery file which I backed up before upgrading to CM 13.
I was able to get root whenever I typed "SU" within the terminal window.
Then CM 13 became available for my device so I upgraded to it by following a few simple steps.
Most Everything works perfectly ...... except for one important problem !
I no longer have root access on my device !!!
Of course the first obvious fix was to try to enable root access by selecting it within the Developer Options to grant root access to Apps and ADB; but that didn't work. And I have tried numerous other possible solutions: reflashing SuperSU2.67, wiping everything clean and reinstalling CM 13 and Gapps from scratch, and other such recommendations but nothing has worked for this problem.
Some of my apps that need to write to the external SD card are unable to work but the apps work if I change the path to the internal storage.
Whenever I need to delete a file from my external SD using ES File Explorer it forces me to go to the CM File manager to approve the deletion.
I am unable to select "Root Access mode" within the CM File manager.
And my little "$" does not change to "#" when I type "SU" in the terminal window.
So all this is definitely a problem with us simply not having root access to our S3 devices.
I really would like to revive this topic because I am pretty sure that Joserin and I are not alone in this one.
The CM 13 is much nicer than the CM 11 and there must be a way to cross this hurdle.
Joserin, please let us know if by chance you have found a solution.
Thanks to all; awaiting your suggestions ......
kevin.a69 said:
Before upgrading to CM 13 for my I 9300 (Int) I was on CM 11 and I had full root access on my device.
In fact I still have that recovery file which I backed up before upgrading to CM 13.
I was able to get root whenever I typed "SU" within the terminal window.
Then CM 13 became available for my device so I upgraded to it by following a few simple steps.
Most Everything works perfectly ...... except for one important problem !
I no longer have root access on my device !!!
Of course the first obvious fix was to try to enable root access by selecting it within the Developer Options to grant root access to Apps and ADB; but that didn't work. And I have tried numerous other possible solutions: reflashing SuperSU2.67, wiping everything clean and reinstalling CM 13 and Gapps from scratch, and other such recommendations but nothing has worked for this problem.
Some of my apps that need to write to the external SD card are unable to work but the apps work if I change the path to the internal storage.
Whenever I need to delete a file from my external SD using ES File Explorer it forces me to go to the CM File manager to approve the deletion.
I am unable to select "Root Access mode" within the CM File manager.
And my little "$" does not change to "#" when I type "SU" in the terminal window.
So all this is definitely a problem with us simply not having root access to our S3 devices.
I really would like to revive this topic because I am pretty sure that Joserin and I are not alone in this one.
The CM 13 is much nicer than the CM 11 and there must be a way to cross this hurdle.
Joserin, please let us know if by chance you have found a solution.
Thanks to all; awaiting your suggestions ......
Click to expand...
Click to collapse
I flashed QSi9300KK on my phone (with kernel. I forget the name but it was the third option - not Agni or stock) and after that TWRP and then CM13. Everything's working fine now, even root access.
Remember do not pick the first two kernels in the installer, they didn't work correctly. Third one works like a charm.
I installed CM13 via TWRP onto my KFHDX 7" (thor). However, 4G LTE isn't working. It isn't detecting my SIM Card.
(the zip I flashed is cm-13.0-20161001-NIGHTLY-thor.zip )
GameExpertNetwork said:
I installed CM13 via TWRP onto my KFHDX 7" (thor). However, 4G LTE isn't working. It isn't detecting my SIM Card.
(the zip I flashed is cm-13.0-20161001-NIGHTLY-thor.zip )
Click to expand...
Click to collapse
Known issue - shown as 'not working' in CM 13 OP (here). CM11 and FireOS are the only two roms that fully support LTE on this device.
*sigh* Ok.
After successfully unlocking the bootloader on my Fire HDX 8.9 Apollo I flashed the newest nightly build of CM13 (cm-13.0-20161006-NIGHTLY-apollo) and tested it. Everything was ok (I was able to set up the system with wifi etc.) , then I continued with flashing Gapps and SU and after the reboot I was stucked at the CM boot screen. Switched Kindle off - only boot screen again. Tried everything again (factory reset, flashing CM-Build&Gapps&SU, this time without a test and still stucked with the boot screen logo. TWRP is working fine.
Any suggestions? Thanx!
Alle9ne said:
After successfully unlocking the bootloader on my Fire HDX 8.9 Apollo I flashed the newest nightly build of CM13 (cm-13.0-20161006-NIGHTLY-apollo) and tested it. Everything was ok (I was able to set up the system with wifi etc.) , then I continued with flashing Gapps and SU and after the reboot I was stucked at the CM boot screen. Switched Kindle off - only boot screen again. Tried everything again (factory reset, flashing CM-Build&Gapps&SU, this time without a test and still stucked with the boot screen logo. TWRP is working fine.
Any suggestions? Thanx!
Click to expand...
Click to collapse
TWRP -> Wipe -> Advanced -> System/Data/Cache/Dalvik. Then reflash everything in one operation before rebooting.
Davey126 said:
TWRP -> Wipe -> Advanced -> System/Data/Cache/Dalvik. Then reflash everything in one operation before rebooting.
Click to expand...
Click to collapse
Thank you! I think I found a source of my problem: I flashed an (outdated) version of SU (2.46). Which version is recommended (or just try the latest?)
Alle9ne said:
Thank you! I think I found a source of my problem: I flashed an (outdated) version of SU (2.46). Which version is recommended (or just try the latest?)
Click to expand...
Click to collapse
You don't need SuperSU with CM13. Just use the native root manager found under developer options. Some have reported WiFi issues with recent SuperSU builds. That said, if you opt to keep it the latest stable build is your best bet.
Davey126 said:
You don't need SuperSU with CM13. Just use the native root manager found under developer options. Some have reported WiFi issues with recent SuperSU builds. That said, if you opt to keep it the latest stable build is your best bet.
Click to expand...
Click to collapse
Ok, I think I am one of this persons with Wifi problems after installing the latest SU. What is the best way to remove SU?
Alle9ne said:
Ok, I think I am one of this persons with Wifi problems after installing the latest SU. What is the best way to remove SU?
Click to expand...
Click to collapse
SuperSU (not SU...) has its own uninstaller under settings (within app); works well. If you want 100% assurance wipe system/data in twrp and reflash rom+gaaps.
I did the following:
Unlocked bootloader
Installed twrp recovery
Flashed lazy flasher
Flashed rr pie rom
Flashed gapps nano
flashed magisk
My phone began restarting randomly once or twice a day.
I thought magisk was the culprit and flashed magisk uninstaller. Didn't solve the issue. Same happened with Pixel exp CAF and crDroid. On AOSP Extended it shuts off randomly instead of restarting. Now back to Pixel CAF cause reboot is better than shutting down.
I'm using latest version of twrp and roms.
How do I fix this. Pls help.
Edit: added magisk
Edit 2: mentioned gapps
SaraKumar said:
I did the following:
Unlocked bootloader
Installed twrp recovery
Flashed lazy flasher
Flashed rr pie rom
flashed magisk
My phone began restarting randomly once or twice a day.
I thought magisk was the culprit and flashed magisk uninstaller. Didn't solve the issue. Same happened with Pixel exp CAF and crDroid. On AOSP Extended it shuts off randomly instead of restarting. Now back to Pixel CAF cause reboot is better than shutting down.
I'm using latest version of twrp and roms.
How do I fix this. Pls help.
Edit: added magisk
Click to expand...
Click to collapse
There's no need to use Lazy Flasher and that's probably a reason why your phone is broken.
And why didn't you flash GApps?
Noter2017 said:
There's no need to use Lazy Flasher and that's probably a reason why your phone is broken.
And why didn't you flash GApps?
Click to expand...
Click to collapse
Thank you for replying.
Twrp was replaced by stock recovery everytime after I installed the rom zip and restarted the phone.
Someone had suggested lazy flasher in the forum. I don't know what it does but it fixed the problem. Is there a way to remove it? And will the recovery problem come back again if I remove it?
Sorry I forgot to mention gapps, I flashed nano after every rom except Pixel CAF(built in gapps).
Just did the 13.2 update, rooted the usual way. And Bluetooth is crashing when I boot or reboot. And won't turn on at all. Any ideas or solutions besides a clean install
The usual way can mean a lot, but most important, did you use Magisk 25.1?
Cheers
Tom
ne0ns4l4m4nder said:
Just did the 13.2 update, rooted the usual way. And Bluetooth is crashing when I boot or reboot. And won't turn on at all. Any ideas or solutions besides a clean install
Click to expand...
Click to collapse
No problem here with Bluetooth crashing when booting or rebooting using Canary Magisk 25101 (same as Stable 25.1) on A13B3.2.
I clean flashed A13B2 and dirty flashed the updates to A13B3+
Lughnasadh said:
No problem here with Bluetooth crashing when booting or rebooting using Canary Magisk 25101 (same as Stable 25.1) on A13B3.2.
I clean flashed A13B2 and dirty flashed the updates to A13B3+
Click to expand...
Click to collapse
Hey, do you know if keeping the root with OTA updates works? Or for each update I need to sideload it? Thanks
AlkaDragos said:
Hey, do you know if keeping the root with OTA updates works? Or for each update I need to sideload it? Thanks
Click to expand...
Click to collapse
In the past it has worked for some but not others. The key is to make sure you haven't made any modifications to any of the partitions. For example, if you are using a custom kernel it won't work unless you flash all the modified images back to stock beforehand.
Also make sure you patch your own boot image so there is a stock boot image backup Magisk can restore.