Database Develop

SuperSU 2.66 beta on Shamu

Please write your experience with SuperSU 2.60 / 2.61 / 2.62-3...2.66 on Shamu.
2.56 didn't work on my unlocked, unencrypted 6.0.0 (MRA58R)
Systemless 2.62-3 with works as a charm with my 6.0.1.
I dirty flashed 6.0.1 system.img and boot.img, then I flashed SuperSU 2.62-3 (in TWRP). I stayed unencrypted.
Xposed, ES File Explorer, Double tap 2 wake, Greenify, BetterBatteryStats ... work perfectly.
Edit:
2.62-3 works for some with 6.0.1. and with Android Pay

2.52 has been working fine for me since mm has been out, running on MRA58R now. Have not tried 2.6 but 2.49 was also working perfectly. If you need android pay to work then 2.6 or there are other options like custom ROMs that have it successfully working
Sent from my Nexus 6 using Tapatalk

Running it here without issue. Also had it running on mra58r.
The only casualty I suppose was/is es file explorer. It could not gain root access for some reason.
I am rooted, unencrypted and have the latest Elite kernel.
Sent from my Nexus 6 using Tapatalk

Using 2.6.1 and brand new 6.0.1 fresh install and Android pay is working flawlessly!

Does anybody have a downloadlink for 2.61, can`t find it anywhere
Nevermind, found it.

gee2012 said:
Nevermind, found it.
Click to expand...
Click to collapse
Adding the link to the post would have been useful!

f2 said:
Adding the link to the post would have been useful!
Click to expand...
Click to collapse
Thread http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344. Link http://forum.xda-developers.com/attachment.php?attachmentid=3568267&d=1449521348.

belek1979 said:
Please write your experience with SuperSU 2.60/2.61 on Shamu.
2.56 didn't work on my unlocked, unencrypted 6.0.0 (MRA58R)
Maybe 2.60/2.61 will work with 6.0.1?
Click to expand...
Click to collapse
Although 2.61 is installed
TWRP says: no root
Root Explorer says: you are not rooted
Quick reboot says: no root

NLBeev said:
Although 2.61 is installed
TWRP says: no root
Root Explorer says: you are not rooted
Quick reboot says: no root
Click to expand...
Click to collapse
Root Checker Pro, BusyBox Pro said i was rooted and the Franco FKU app has root too. Maybe its a problem with apps not adapted/compatible with systemless root (2.61) yet.

gee2012 said:
... Maybe its a problem with apps not adapted/compatible with systemless root (2.61) yet.
Click to expand...
Click to collapse
I am using the lite Rom 6.0.1 of @Danvdh. Works, but with Franco's kernel (r35) installed, problems with the sim-card. (Not recognized).
Going back to 6.0...... Too many issues.

NLBeev said:
I am using the lite Rom 6.0.1 of @Danvdh. Works, but with Franco's kernel (r35) installed, problems with the sim-card. (Not recognized).
Going back to 6.0...... Too many issues.
Click to expand...
Click to collapse
Well i`am on stock 6.0.1/TWRP/2.61/Franco r35 and so far no issues, everything working well :fingers-crossed:

gee2012 said:
Well i`am on stock 6.0.1/TWRP/2.61/Franco r35 and so far no issues, everything working well :fingers-crossed:
Click to expand...
Click to collapse
Now back on 6.0. Will retry with a full wipe.

NLBeev said:
Now back on 6.0. Will retry with a full wipe.
Click to expand...
Click to collapse
Good luck, from what i understand systemless root works best on stock.

gee2012 said:
Good luck, from what i understand systemless root works best on stock.
Click to expand...
Click to collapse
Did a full wipe and flashed again the lite Rom 6.0.1 of Danvdh. This rom is stock based.
After reboot I restored the 6.0-data from a nandroid backup with TWRP. Root checker says 'no root'.
Now last try with full wipe and restore from Google.
At this moment my N6 is restoring the apps from Google take a long time, but root checker says there is root access.
So this update needs a complete wipe and factory reset.

NLBeev said:
Did a full wipe and flashed again the lite Rom 6.0.1 of Danvdh. This rom is stock based.
After reboot I restored the 6.0-data from a nandroid backup with TWRP. Root checker says 'no root'.
Now last try with full wipe and restore from Google.
At this moment my N6 is restoring the apps from Google take a long time, but root checker says there is root access.
So this update needs a complete wipe and factory reset.
Click to expand...
Click to collapse
Maybe thats it, i didn`t mention i actualy did a full wipe prior to rooting.

gee2012 said:
Maybe thats it, i didn`t mention i actualy did a full wipe prior to rooting.
Click to expand...
Click to collapse
I did some reading and trial with the lite rom of Danvdh. What seems important is that SuperSU 2.6x is flashed as the last file after flashing system stuff, like mods, kernel.

NLBeev said:
I did some reading and trial with the lite rom of Danvdh. What seems important is that SuperSU 2.6x is flashed as the last file after flashing system stuff, like mods, kernel.
Click to expand...
Click to collapse
Yup, that what i did too. Thought you knew that

gee2012 said:
Yup, that what i did too. Thought you knew that
Click to expand...
Click to collapse
It is logical, but I was too busy with trying to flash without wiping the data partition.

gee2012 said:
...about wiping data...
Click to expand...
Click to collapse
I managed to update from M6.0 to M6.0.1 with data kept.
Important is that the system partition does not contain su-stuff of previous versions.
In TWRP I wiped the M 6.0 system and caches, but not the data.
Flashed the lite 6.0.1 rom of Danvdh;
Flashed Franco's kernel r35;
Flashed SuperSU 2.61;
Reboot - TWRP button 'do not install SU'.
Needed to restore settings (dpi), layers and the black themed apps of the TBO team.

I dirty flashed from stock rooted 6.0.0 to 6.0.1 today and rooted using Systemless 2.62-3. Everything is working great so far.

Bootloop after rooting CrDroid

I Installed the latest 2.1 crDroid today, the ROM is smooth and almost everything works perfectly fine. So I decided to install the substratum theme engine, and it failed and because it couldn't get the root privileges. Then I came to know that the ROM itself is not rooted and tried to flash super su 2.4.6. zip in order to root it.. but instead it gave me bootloop... can anyone confirm if they faced the same?
Thanks in advance

Kalp3sh S1NGH said:
I Installed the latest 2.1 crDroid today, the ROM is smooth and almost everything works perfectly fine. So I decided to install the substratum theme engine, and it failed and because it couldn't get the root privileges. Then I came to know that the ROM itself is not rooted and tried to flash super su 2.4.6. zip in order to root it.. but instead it gave me bootloop... can anyone confirm if they faced the same?
Thanks in advance
Click to expand...
Click to collapse
Try installing this..

Ashish Banka said:
Try installing this..
Click to expand...
Click to collapse
I flashed the latest zip. Thanks anyway

Flash ROM gapps and root files together and check

Kalp3sh S1NGH said:
I flashed the latest zip. Thanks anyway
Click to expand...
Click to collapse
hello frnds. I have installed RR rom (5-02-17 built) by Rishab Rao every thing is working good. but i m facing network reception issue specially on jio network. although its working fine fine but there is a flactuation in network every time. 1.. 2.. 3.. but never 4 ( full network). Anyone facing this issue..??

Unable to flash anything in TWRP Or in MAGISK

Hi
In latest open beta with Magisk 15.3 , used debloater and made space in system , but on flashing anything no error is there but nothing shows in app drawer , same is happening with Magisk also . Managed to flash viper but the drivers are not getting installed showing io error while same works fine for others without manual driver installation, no idea what's wrong !!!!

Yikes. Sounds like something is glitched in there. Try wiping : system and cache ( only )and reloading the rom and then rebooting into recovery and then booting up in system.
.
If it's still glitched ( ugg ) then its wipe all ( less external data ) and factory reset and start over.
.
Um, did you make yourself a nandroid backup ?

AKHIL.cochin said:
but on flashing anything no error is there but nothing shows in app drawer.
Click to expand...
Click to collapse
What do you mean by this? Do you mean that you don't see any apps after flashing a Magisk module? Many modules don't install any apps and you either don't have to do anything to configure or run a terminal command. What modules are you talking about?
Managed to flash viper but the drivers are not getting installed showing io error while same works fine for others without manual driver installation, no idea what's wrong !!!!
Click to expand...
Click to collapse
That's a known issue with V4A on OxygenOS Oreo. Some don't experience it though, which is incredibly frustrating...

Also what version of twrp r u using

old_fart said:
Yikes. Sounds like something is glitched in there. Try wiping : system and cache ( only )and reloading the rom and then rebooting into recovery and then booting up in system.
.
If it's still glitched ( ugg ) then its wipe all ( less external data ) and factory reset and start over.
.
Um, did you make yourself a nandroid backup ?
Click to expand...
Click to collapse
did a clean flash and checked , its still there , no idea whats wrong ..

Bradl79 said:
Also what version of twrp r u using
Click to expand...
Click to collapse
twrp-3.2.1-0

Didgeridoohan said:
What do you mean by this? Do you mean that you don't see any apps after flashing a Magisk module? Many modules don't install any apps and you either don't have to do anything to configure or run a terminal command. What modules are you talking about?
That's a known issue with V4A on OxygenOS Oreo. Some don't experience it though, which is incredibly frustrating...
Click to expand...
Click to collapse
" not only magisk , have u read my post , on flashing arise magnum on twrp also gave no errors and i selected viper , dolby , dolby atmos , xperia music etc and all flashed fine but none was showing in there thats what i have mentioned i also tried many viper and dolby modules in magisk , nothing s working "

AKHIL.cochin said:
" not only magisk , have u read my post , on flashing arise magnum on twrp also gave no errors and i selected viper , dolby , dolby atmos , xperia music etc and all flashed fine but none was showing in there thats what i have mentioned i also tried many viper and dolby modules in magisk , nothing s working "
Click to expand...
Click to collapse
Yes, I did read your post, but it was lacking in detail so I needed to ask some clarifying questions. Unfortunately, your answer is also somewhat lacking in detail...
But, I'm guessing you're trying to install some audio mods. V4A isn't working properly on OOS Oreo for the OP3T. A few users have it running fine, but it seems like those are a minority.
There are not that many Dolby mods that work on Oreo yet, so you might have to look around a bit to find one that does. There'll most likely be some more readily available soon though.

Didgeridoohan said:
Yes, I did read your post, but it was lacking in detail so I needed to ask some clarifying questions. Unfortunately, your answer is also somewhat lacking in detail...
But, I'm guessing you're trying to install some audio mods. V4A isn't working properly on OOS Oreo for the OP3T. A few users have it running fine, but it seems like those are a minority.
There are not that many Dolby mods that work on Oreo yet, so you might have to look around a bit to find one that does. There'll most likely be some more readily available soon though.
Click to expand...
Click to collapse
THE FRUSTRATING THING S ITS WORKING FOR ALL THE OTHERS WITHOUT ANY ISSUES IN SAME ROM KERNEL COMBO

AKHIL.cochin said:
THE FRUSTRATING THING S ITS WORKING FOR ALL THE OTHERS WITHOUT ANY ISSUES IN SAME ROM KERNEL COMBO
Click to expand...
Click to collapse
Yes, it's frustrating, but there's no need to shout. And it does NOT work for everyone else. I haven't had an audio mod working properly on my OP3T since updating to OOS 5+...
It works for some, but not for others. You could try the OOS beta. It seems like some have better luck with that.
Either you try to help, if possible, or you change to a working ROM combo, or you wait until someone finds a fix.

I had a problem that some modules wouldn't activate (they install successfully, but after reboot I would still see "module will be updated at next reboot"). As I didn't have time and will to debug this, I reverted to OOS 4.5.1.

Uninstalled a system app after I rooted my phone. How do I fix this?

Hey,
I am a Xiaomi Redmi 4A user. Over the past few days, I unlocked its bootloader, installed twrp. I then flashed AOSP Extended and rooted my phone by flashing SuperSU.
Today, I used the in built system device uninstaller and I uninstalled the android stock Calendar app, thinking the Google Calendar app from the play store is better and it would work. Now, I see something like 'com.android.providers.Calendar' has stopped every once in a while.
Is there any viable solution to this error that regularly keeps popping up? I do not want to flash the ROM again/factory reset/root my phone again or something like that.
Any help would be greatly appreciated. Thanks!

Try flashing Oreo gapps it may fix it just clean cache and dalvink before flashing

rseragon said:
Try flashing Oreo gapps it may fix it just clean cache and dalvink before flashing
Click to expand...
Click to collapse
Sure, it worked all right. Thanks!

mobileenthusiast said:
Sure, it worked all right. Thanks!
Click to expand...
Click to collapse
No problem bro

Front camera doesn't popup in custom ROM (only Cosmic OS tested)

Hi guys
I'm quite new to the K20 Pro. Last night, my friend asked me to install some custom AOSP ROMs for him. I chose Cosmic OS first since it just got updated recently. Installed and booted up just fine, BUT here's the problem :
- First boot up and installed GCam : front camera pops up fine
- Installed 81Hz mod and Immensity kernel : still pops up fine
- Some Magisk modules like NFS, Viper4android v2.7, Google dialer framework : still pops up fine
- Substratum app and apply Liv Dark theme : front camera STUCKS after a reboot, can't even use the Motor Control app to get it pop up again
So I thought the problem lies in the Substratum and the theme but uninstalling those didn't help, EVEN clean flashing the ROM again. Changing to MIUI 11 EU rom, front camera works fine again.
If anyone knows whether the problem is in the ROM itself or conflict with the modules/theme/mod/kernel or it's a common issues in custom AOSP ROMs then please let me know asap, I'll be very appreciated.
THANK YOU !!!!!!

S.N.A.P said:
Hi guys
I'm quite new to the K20 Pro. Last night, my friend asked me to install some custom AOSP ROMs for him. I chose Cosmic OS first since it just got updated recently. Installed and booted up just fine, BUT here's the problem :
- First boot up and installed GCam : front camera pops up fine
- Installed 81Hz mod and Immensity kernel : still pops up fine
- Some Magisk modules like NFS, Viper4android v2.7, Google dialer framework : still pops up fine
- Substratum app and apply Liv Dark theme : front camera STUCKS after a reboot, can't even use the Motor Control app to get it pop up again
So I thought the problem lies in the Substratum and the theme but uninstalling those didn't help, EVEN clean flashing the ROM again. Changing to MIUI 11 EU rom, front camera works fine again.
If anyone knows whether the problem is in the ROM itself or conflict with the modules/theme/mod/kernel or it's a common issues in custom AOSP ROMs then please let me know asap, I'll be very appreciated.
THANK YOU !!!!!!
Click to expand...
Click to collapse
Front Camera just works fine except you don't mess with the sensors while downgrading. For a flawless experience either stick to Q or P.
Sent from my Redmi K20 Pro using Tapatalk

Sukhi said:
Front Camera just works fine except you don't mess with the sensors while downgrading. For a flawless experience either stick to Q or P.
Click to expand...
Click to collapse
well the custom ROM is Pie-based and I'm pretty sure I didn't do anything related to sensors
anyway thanks for your answer

S.N.A.P said:
well the custom ROM is Pie-based and I'm pretty sure I didn't do anything related to sensors
anyway thanks for your answer
Click to expand...
Click to collapse
Jumping b/w Q and P roms does break the sensors.
Sent from my Redmi K20 Pro using Tapatalk

S.N.A.P said:
Hi guys
I'm quite new to the K20 Pro. Last night, my friend asked me to install some custom AOSP ROMs for him. I chose Cosmic OS first since it just got updated recently. Installed and booted up just fine, BUT here's the problem :
- First boot up and installed GCam : front camera pops up fine
- Installed 81Hz mod and Immensity kernel : still pops up fine
- Some Magisk modules like NFS, Viper4android v2.7, Google dialer framework : still pops up fine
- Substratum app and apply Liv Dark theme : front camera STUCKS after a reboot, can't even use the Motor Control app to get it pop up again
So I thought the problem lies in the Substratum and the theme but uninstalling those didn't help, EVEN clean flashing the ROM again. Changing to MIUI 11 EU rom, front camera works fine again.
If anyone knows whether the problem is in the ROM itself or conflict with the modules/theme/mod/kernel or it's a common issues in custom AOSP ROMs then please let me know asap, I'll be very appreciated.
THANK YOU !!!!!!
Click to expand...
Click to collapse
Hey, how good is the fingerprint sensor with this rom? And also can you try watching a YouTube
To see how stable the audio is.

Sukhi said:
Jumping b/w Q and P roms does break the sensors.
Click to expand...
Click to collapse
oh
I was from MIUI china stable 10.3.17 Pie, so it's just Pie-MIUI to Pie-AOSP
Does it break the sensors too ???

m1chb3ltr3 said:
Hey, how good is the fingerprint sensor with this rom? And also can you try watching a YouTube
To see how stable the audio is.
Click to expand...
Click to collapse
audio works as it should, completely normal
fingerprint works fine too

S.N.A.P said:
oh
I was from MIUI china stable 10.3.17 Pie, so it's just Pie-MIUI to Pie-AOSP
Does it break the sensors too ???
Click to expand...
Click to collapse
Nope ! I thought you came back from MIUI 11. If you're jumping within Pie, it's not a problem. There should be no other reason why the Cam won't Pop-up other than the Camera sensor fail. Did you wipe Vendor?.
Sent from my Mi A3 using Tapatalk

Sukhi said:
Nope ! I thought you came back from MIUI 11. If you're jumping within Pie, it's not a problem. There should be no other reason why the Cam won't Pop-up other than the Camera sensor fail. Did you wipe Vendor?.
Click to expand...
Click to collapse
(S.N.A.P here, just my other account)
Yes, I did wiped Vendor
At first I used TWRP 3.3.1-15 by Mauro, 5 wipe and flashing Vendor 10.3.17 + Rom + Gapps but failed at the vendor so I switched to LRTeam TWRP. This time only 4 wipe since there's no Vendor option. Flashing was ok and the phone booted up
And then everything went like the first post

75_TZ said:
(S.N.A.P here, just my other account)
Yes, I did wiped Vendor
At first I used TWRP 3.3.1-15 by Mauro, 5 wipe and flashing Vendor 10.3.17 + Rom + Gapps but failed at the vendor so I switched to LRTeam TWRP. This time only 4 wipe since there's no Vendor option. Flashing was ok and the phone booted up
And then everything went like the first post
Click to expand...
Click to collapse
Never ever touch vendor again. It's the set of drivers for your device. Go back flash the complete MIUI stock Pie rom and then continue with the Cosmic flash w/o any system/vendor wipes. Data,Cache,Dalvik wipes should be more than enough.
Sent from my Redmi K20 Pro using Tapatalk

Sukhi said:
Never ever touch vendor again. It's the set of drivers for your device. Go back flash the complete MIUI stock Pie rom and then continue with the Cosmic flash w/o any system/vendor wipes. Data,Cache,Dalvik wipes should be more than enough.
Click to expand...
Click to collapse
OH
My fault
Just check back some tutorials of some custom ROMs, only wipe system, data, cache, dalvik cache, no Vendor wipe needed
No wonder when I flashed MIUI 11 EU rom, popup cam works fine again
Thank you so much
I'll try again and see if it works

75_TZ said:
OH
My fault
Just check back some tutorials of some custom ROMs, only wipe system, data, cache, dalvik cache, no Vendor wipe needed
No wonder when I flashed MIUI 11 EU rom, popup cam works fine again
Thank you so much
I'll try again and see if it works
Click to expand...
Click to collapse
People are just copy pasting tutorials from old devices which have dedicated System, Recovery, Vendor etc partions and and wiping one of these won't crash the device. K20P is a system as a root device and wiping system wipes of everything except vendor. Moreover, wiping System isn't required at all as most of the roms these days have System wipe scripts already baked in and would wipe the system irrespective of whether you wipe it or not. There's no real added advantage of wiping system before you flash the rom. System wipes should only be done occassionally whenever you have really messed up something or getting FC's.
Sent from my Redmi K20 Pro using Tapatalk

Sukhi said:
People are just copy pasting tutorials from old devices which have dedicated System, Recovery, Vendor etc partions and and wiping one of these won't crash the device. K20P is a system as a root device and wiping system wipes of everything except vendor. Moreover, wiping System isn't required at all as most of the roms these days have System wipe scripts already baked in and would wipe the system irrespective of whether you wipe it or not. There's no real added advantage of wiping system before you flash the rom. System wipes should only be done occassionally whenever you have really messed up something or getting FC's.
Click to expand...
Click to collapse
OH :fingers-crossed:
That's a great tip
I'm very appreciated
Thank you :highfive: