Develop Bugs

How can i root after flashing a ROM?

So here is what i did step by step:
1.Installed the Kindle Fire Utility v.0.9.6 drivers
2.Connected Kindle and waited for all drivers to install
3.Started the utility (ADB Status: online)(Boot Status: i dont remember)
4.Chose option 2 and got stuck on a "Please Wait" after the utility said it was trying to remove root checker, meanwhile my kindle was already in TWRP and stopped booting, so i figured why not just install a custom ROM, so i flashed CM10 by lithium76, the tablet edition rom, then flashed gapps.
5.When it finished i chose reboot system and it didnt reboot system it just kept going back to the Recovery so i got very scared(note: I formatted everything before flashing, dalvik, cache, factory reset, and system)
6.I kept trying to run the utility again but it would always get stuck saying that it cant rename root and telling me to wait and the phone would just stay in the recovery( i cant remember this part at all)
7. So i chose reboot and chose bootloader and held down the power button and from there chose "boot normally", it booted normally and now i'am running cm10 on the kindle
8.BUT.... i dont have root access at all, superuser is installed but i dont have root access, i tried going back to the utility but it doesnt recognize my device at all, it is always offline now.
How can i get root access now, I'am completely lost and dont know what to do, also i cant reboot from the recovery, i have to go to the bootloader and reboot normally from there.Please help me, i know i should't have done things the way i did but i wasnt thinking, i know you dont need root access for a custom rom but i think you wont have the full android experience without root, please somebody help me.

All of the ROMs here (Unless it says they don't, correct me if I'm wrong.) should give you root. I'm not sure about your problem. Er, There isn't anything I can do to help, sorry.

Jared631 said:
All of the ROMs here (Unless it says they don't, correct me if I'm wrong.) should give you root. I'm not sure about your problem. Er, There isn't anything I can do to help, sorry.
Click to expand...
Click to collapse
yeah they all should but if you dont have the root binaries installed you dont have root even if you have an apk installed.

iraiderx said:
yeah they all should but if you dont have the root binaries installed you dont have root even if you have an apk installed.
Click to expand...
Click to collapse
All custom ROMs (except maybe 2-3 you'll never use) come with Superuser.apk and the su binary already packaged in the flashable ROM.zip. Not only that, but custom recoveries like TWRP already have root access, so going through the "rooting" process only to install a custom ROM is absolutely pointless.
Who knows why you don't have root access. It could be your recovery's fault or you may have a bad ROM download (did you check the md5?). Either way you should start all over from the beginning and skip all the unnecessary steps like installing su and Superuser.apk
Access fastboot (you've done it once, so I'm sure you can figure it out)
Download custom recovery and check md5
(Re)Install custom recovery (via fastboot)
Download FFF1.4a.zip
Use recovery to flash FFF1.4a.zip (checksum is automatic)
Download a custom ROM and check md5
Transfer ROM to sdcard
Wipe System & Factory Reset
Install ROM
Reboot System
Enjoy your fully rooted ROM

soupmagnet said:
All custom ROMs (except maybe 2-3 you'll never use) come with Superuser.apk and the su binary already packaged in the flashable ROM.zip. Not only that, but custom recoveries like TWRP already have root access, so going through the "rooting" process only to install a custom ROM is absolutely pointless.
Who knows why you don't have root access. It could be your recovery's fault or you may have a bad ROM download (did you check the md5?). Either way you should start all over from the beginning and skip all the unnecessary steps like installing su and Superuser.apk
Access fastboot (you've done it once, so I'm sure you can figure it out)
Download custom recovery and check md5
(Re)Install custom recovery (via fastboot)
Download FFF1.4a.zip
Use recovery to flash FFF1.4a.zip (checksum is automatic)
Download a custom ROM and check md5
Transfer ROM to sdcard
Wipe System & Factory Reset
Install ROM
Reboot System
Enjoy your fully rooted ROM
Click to expand...
Click to collapse
Thank you so much, i didnt do extacly as you said but what it did worked! i flashed a stock rom which came with busybox and su and then went to the recovery and flashed the rom i already had in my internal storage and now i have root access

[KERNEL] [5.0] Modified Kernel to Allow Root Access

WARNING: THIS IS NOT A FLASHABLE ZIP
This is a modified kernel for Android 5.0 that allows root to work.
This kernel alone will not grant root access.
Flash this in custom recovery to obtain root: http://download.chainfire.eu/591/SuperSU/BETA-SuperSU-v2.17.zip
The kernel boot.img can be flashed using fastboot.
Credit goes to Chainfire. After seeing this post: https://plus.google.com/+Chainfire/posts/VxjfYJnZAXP ,
I took it upon myself to decompile, edit, then recompile the stock manta LPX13D kernel since he had only done so for the Nexus5/7.
Link: https://plus.google.com/+Chainfire/posts/ZzXaU1W7Uzm
Keep in mind this kernel allows root to work, but most apps that require root will need to be updated in order to fully work on Android 5.0.
Chainfire explains this in greater detail in the first G+ post i linked.

Damn, titanium backup is a no go.

great! works perfect, thanks a lot

newellj79 said:
Damn, titanium backup is a no go.
Click to expand...
Click to collapse
TiBu Works on 5.0!!!
Link: Experimental Version of TiBu that works on Andriod 5.0

phrix626 said:
TiBu Works on 5.0!!!
Link: Experimental Version of TiBu that works on Andriod 5.0
Click to expand...
Click to collapse
Thanks I'll give it a shot.

phrix626 said:
TiBu Works on 5.0!!!
Link: Experimental Version of TiBu that works on Andriod 5.0
Click to expand...
Click to collapse
What has your experience been with this so far? Does it delete system apps too? Thanks for the link!

anoneemooz said:
What has your experience been with this so far? Does it delete system apps too? Thanks for the link!
Click to expand...
Click to collapse
So far I've only restored a previous backup of flappybird from tibu on 5.0, I'm restoring a twrp backup of kitkat now so i can run a new backup in tibu, then restore lollipop, then test all the things!

It force closes when trying to sync with my Google cloud backup.

So far I've found that the experimental version of TiBu fails to uninstall system apps claiming "Cannot remove system app, failed to locate the apk file."
But... It does restore backups (app + data)

phrix626 said:
So far I've found that the experimental version of TiBu fails to uninstall system apps claiming "Cannot remove system app, failed to locate the apk file."
But... It does restore backups (app + data)
Click to expand...
Click to collapse
Aw man. That's all I really want right now. I'm about to give rooting this a shot now. Hopefully to try out some ad removing stuff like adaway! Thanks for the updates on TiBu!

I can't seem to get this to work. I flashed the boot.img via fastboot using "fastboot erase boot" followed by "fastboot flash boot boot.img" and then I reboot into recovery to flash the superuser zip in this thread..and I still get the same error with SuperSU about missing stuff and all root apps I've tried say I'm not rooted. I'm using the latest TWRP. Anything I'm missing?

Off topic: if you only need root to restore TiBu backup - create update zip from your backup, then flash the update zip in recovery. No root needed.
On topic: since you followed Chainfires' method, this won't set the whole system to permissive, right?
edit: I believe not, if TiBu is not working with this boot image. TiBu has not adopted to the new 5.0 SELinux environment yet.

Thanks for this kernel. İs there anybody tried this kernel ? I havent got much experience about android.

Thanks, this gave me root. Just need to wait for the various apps to be updated in due course. First one I tried, rashr, gained root access but said device not supported.
as an aside, anyone looking to block ads with or without root you can always flash this from recovery http://forum.xda-developers.com/showthread.php?t=1916098

Keep up to date with the latest versions of TiBu. Check out their Twitter feed.
https://mobile.twitter.com/TitaniumBackup/status/524487475738443776
The first test version I linked was older. I haven't had a chance to test this one yet.

Flashed the modified boot image & flashed SuperSu 2.17
SuperSU app won't let me update the binaries - so no root. SuperSU 2.16 doesn't work for me either.
Where to look? Can't find flashable SU binaries either.
Thanks!

Ti2 said:
Flashed the modified boot image & flashed SuperSu 2.17
SuperSU app won't let me update the binaries - so no root. SuperSU 2.16 doesn't work for me either.
Where to look? Can't find flashable SU binaries either.
Thanks!
Click to expand...
Click to collapse
If you flashed the boot.img and the SuperSU zip, root access should work.
The SuperSU zip includes the SuperSu app and the su binaries. It won't let you update the binaries because 2.16 is the latest stable release.
To test root:
Download and open Terminal Emulator > type "su" > you should get a SuperSU promt > grant access to Terminal Emulator.
The $ should now be a # , this confirms you are using the shell as root user.

Latest tibu test version working ok here for backup and restore :good:

phrix626 said:
If you flashed the boot.img and the SuperSU zip, root access should work.
The SuperSU zip includes the SuperSu app and the su binaries. It won't let you update the binaries because 2.16 is the latest stable release.
To test root:
Download and open Terminal Emulator > type "su" > you should get a SuperSU promt > grant access to Terminal Emulator.
The $ should now be a # , this confirms you are using the shell as root user.
Click to expand...
Click to collapse
No # for me... not even the prompt (duh..)
I flashed the boot.img and the SuperSU zip. I just don't have root.

What build of Lollipop are you running?
I flashed the images from this post :http://forum.xda-developers.com/showpost.php?p=56505625&postcount=99
Edit: that build is android-5.0.0_r2 (LRX21M)

Impossible to remove bloatware

Hi Guys,
I need help as strange thing is happening to my phone.
I have unlocked phone, installed TWRP recovery latest, rooted the phone. The phones has now superuser apk and I can work with superuser rights.
However when it comes to uninstall bloatware I go through Titanum back up and try to uninstall the bloatware. It is strange that it says there it is uninstalled but when I restart phone I find all apks in the phone. Indeed nothing has been removed.
Any idea why is that and how is possible this?
Thanks for any help.
I', on Lollipop, 4.16.401.13, unlocked, stock-rooted.
Regards,

Yes, in the Recovery Mode with Aroma Filemanager...

wurstherpes said:
Yes, in the Recovery Mode with Aroma Filemanager...
Click to expand...
Click to collapse
Thanks a lot for your reply.
I'll give a try now.

Be carefull

wurstherpes said:
Yes, in the Recovery Mode with Aroma Filemanager...
Click to expand...
Click to collapse
Do yo know what directory apk are located.? I can't find them.

System/App and private/app

You can't delete system apps within the running rom because your stock kernel doesn't allow it. You need a custom kernel or at least the system write protection module.

[G4/G4 Plus] How to Install Magisk and pass safetynet?

Disclaimer
Your warranty is now void. I am not responsible if this in anyway bricks your device or anything else that might go wrong and you cant restore it back. It is assumed that you are familiar with TWRP environment and fastboot in case you need to restore stock.
Click to expand...
Click to collapse
This was last updated on 07/02/2017
This guide will tell you how to install magisk (or magiskify as the app calls it) in order to make systemless mods possible for everything. The thing about magisk is as everything is systemless you can just uninstall magisk in the end and take an ota update without having to worry about what in your system had changed. For custom roms, though not as important, systemless mods are useful for stuff like passing safetynet.
For G4/G4 plus there is no support for Android Pay(at least where I live as there is no h/w for NFC) but various banking apps and apps like Pokemon Go.
First of all, if you want to pass safetynet you will need to use the MagiskSU method to root. This root is based on phh Superuser.
This means if you have anything like SuperSU or phh Superuser then you need to unroot first. Magisk will still work if its systemless but safetynet will not.
Also if you have Xposed installed and enabled, then it will not pass safetynet.
Requirements
1. Unlocked bootloader
2. TWRP installed
This is untested in stock NPJ25-93.11/12/14. If someone can test and report I can update this.
Please flash a custom kernel like elementalX if you are on stock rom
If you are stuck in a bootloop the you need to restore your current boot.img and everything will return back to as it was.
Steps
Take a TWRP backup of current rom. Just the boot image should be enough but everything will make it safer.
1. If you are using a custom rom, I recommend you start from a fresh flash. A dirty flash works as well.
A clean boot.img is recommended as debugging is more difficult without it.
A unrooted rom (Like official Lineage-OS) is best but if you are using a pre-rooted rom then you would need to use the UnSU script by osm0sis (tested on unofficial Lineage by Silesh.Nair)
Get UnSU script from here:
https://forum.xda-developers.com/showthread.php?t=2239421
https://forum.xda-developers.com/showpost.php?p=63615067
2. Download the latest magisk zip and uninstaller from the Magisk release thread.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
3. After flashing your ROM (or your clean stock rom if you will), flash the magisk zip using TWRP. If your rom is unrooted, Magisk will provide a root solution. If you are rooted with systemless SuperSU, magisk integrates itself there but you will not pass safetynet.
4. Reboot and install magisk manager from play store. Enable Magisk Hide. You can pass safetynet now.
Magisk also supports systemless host files(for Adaway) and busybox support from the app itself. You can just enable and reboot.
If you are on MM, then you can install xposed through magisk itself(but no safetynet support in this case)
Also magisk already has ports of Viper4Android as well. Creating your own mod is simple as well. For further guide search in the Magisk forum. Excellent guides are published there.
Credits:
topjohnwu for Magisk and MagiskSU development
osm0sis for unSU script
shreps for porting TWRP
mrinmaydhar for kernel info
None of this is my work. All I did was compile it so that it becomes easier for others.
If I missed anything please remind me. This is my first thread so everything might not be smoothest.

Shouldn't we flash a custom kernel like elementalx if we are on stock rom. I think current root methods have problems with the stock boot image.

mrinmaydhar said:
Shouldn't we flash a custom kernel like elementalx if we are on stock rom. I think current root methods have problems with the stock boot image.
Click to expand...
Click to collapse
So it's working fine after flashing ElementalX first? Because I remember it boot looped before but I am not sure which version it was. If you have tested please report back so that I can add that to the post.

guessingagain said:
So it's working fine after flashing ElementalX first? Because I remember it boot looped before but I am not sure which version it was. If you have tested please report back so that I can add that to the post.
Click to expand...
Click to collapse
So without custom kernel, it bootloops. Any custom kernel would do

mrinmaydhar said:
So without custom kernel, it bootloops. Any custom kernel would do
Click to expand...
Click to collapse
OP updated. thanks for this info.

I keep getting this error, any ideas what could be causing it?
I'm on stock rom (marshmallow) and I already removed supersu

aSuperSaiyanG0D said:
I keep getting this error, any ideas what could be causing it?
I'm on stock rom (marshmallow) and I already removed supersu
Click to expand...
Click to collapse
Nope. SuperSU exists. Search the threads for stock boot image of your ROM. Flash it and then continue installation of Magisk.

mrinmaydhar said:
Nope. SuperSU exists. Search the threads for stock boot image of your ROM. Flash it and then continue installation of Magisk.
Click to expand...
Click to collapse
I have a nandroid backup of my entire system before I installed supersu and Elemental Ex, would restoring just the boot suffice?

aSuperSaiyanG0D said:
I have a nandroid backup of my entire system before I installed supersu and Elemental Ex, would restoring just the boot suffice?
Click to expand...
Click to collapse
Yeah. But flash ElementalX though. Just skip SuperSU. If anything goes wrong just restore the boot partition.
If you want to just remove SuperSU, disable root access from within the app then perform full unroot. But it's usually better to flash stock boot.img as everything is cleaner in that case.
Edit: did you try flashing the unsu script first? Did that fail?

guessingagain said:
Yeah. But flash ElementalX though. Just skip SuperSU. If anything goes wrong just restore the boot partition.
If you want to just remove SuperSU, disable root access from within the app then perform full unroot. But it's usually better to flash stock boot.img as everything is cleaner in that case.
Edit: did you try flashing the unsu script first? Did that fail?
Click to expand...
Click to collapse
Yes I tried the unsu zip and it went thru without any errors but magisk still gave me that error

If I do a ROM update do I need to unSU and flash Magisk again?

Covalex said:
If I do a ROM update do I need to unSU and flash Magisk again?
Click to expand...
Click to collapse
As every ROM update flashes a clean boot.img it's necessary to flash magisk again. If your ROM comes prerooted you need to unsu otherwise not needed.
But you have to flash magisk Everytime after a ROM update. As long as you don't uninstall before updating, all your settings should be fine though.

aSuperSaiyanG0D said:
Yes I tried the unsu zip and it went thru without any errors but magisk still gave me that error
Click to expand...
Click to collapse
Did ElementalX help? Any problems after that?

guessingagain said:
Did ElementalX help? Any problems after that?
Click to expand...
Click to collapse
No problems other than the same error about supersu being installed.
However last night I tried flashing a custom rom "resurrection remix" and magisk installed fine, downside was titanium backup didn't really like magisks root and it wouldn't restore my apps, it just froze.
Has titanium backup worked for you?

aSuperSaiyanG0D said:
No problems other than the same error about supersu being installed.
However last night I tried flashing a custom rom "resurrection remix" and magisk installed fine, downside was titanium backup didn't really like magisks root and it wouldn't restore my apps, it just froze.
Has titanium backup worked for you?
Click to expand...
Click to collapse
Just tried. Works for me. Normally I install the apps through play store and just restore data. Tried restoring firefox it works. Maybe it's a specific problem. Are you sure that restoring with SuperSU works without errors
Magisk is known to have problems with tibackup. A fix may be incoming(maybe an update to tibackup).

guessingagain said:
Just tried. Works for me. Normally I install the apps through play store and just restore data. Tried restoring firefox it works. Maybe it's a specific problem. Are you sure that restoring with SuperSU works without errors
Magisk is known to have problems with tibackup. A fix may be incoming(maybe an update to tibackup).
Click to expand...
Click to collapse
Yes titanium backup works fine with my SuperSU on stock, and on my tablet (Nexus 7 2013) I installed magisk and titanium works as intended.
So maybe something was just iffy with titanium backup last night, actually come to think of it I don't think Resurrection Remix comes with BusyBox.
I'll try again but install BusyBox first when I get more time.

Would using the wrong unSU version affect safetynet detection?

Covalex said:
Would using the wrong unSU version affect safetynet detection?
Click to expand...
Click to collapse
As long as the there are no SU links and executables left, using any unSU script should be fine.
If you are on a custom rom check /system/bin/su and /system/xbin/su are there or not.
BTW which script did you use to unSU?

guessingagain said:
As long as the there are no SU links and executables left, using any unSU script should be fine.
If you are on a custom rom check /system/bin/su and /system/xbin/su are there or not.
BTW which script did you use to unSU?
Click to expand...
Click to collapse
I used unSU like you linked, but it was an older version. Reflashing the rom, updated unSU and magisk fixed safetynet.

Covalex said:
I used unSU like you linked, but it was an older version. Reflashing the rom, updated unSU and magisk fixed safetynet.
Click to expand...
Click to collapse
You used this right?
https://forum.xda-developers.com/showpost.php?p=63615067
Or is there another unSU script that is updated? If so can you link that?

How to install SYSTEM-MODE Supersu on Android Oreo?

Hello there,
I'm running my OnePlus 3 with the latest 8.1.0 Omni rom build, and I would like to root with SuperSU in system mode. Now before you post anything let me show you what I have tried so far.
1) echo SYSTEMLESS=false > /data/.supersu in TWRP and then flashing latest supersu (also tried with versions 2.80 and 2.76) -> bootloop every time.
2) Flashing system mode supersu ready zips from here: https://forum.xda-developers.com/apps/supersu/v2-64-2-66-supersu-mode-t3286120 -> stuck on flashing in TWRP, nothing happens and I have to shut down the phone manually
3) Installing supersu aroma zip, choosing system mode, leave everything default and the flash the latest supersu zip -> bootloop
4) Installing phh superuser, device won't boot, but I think it has to do with the dm-verity which I have enabled, don't know how to fix this. Anyway still doesn't work.
So, does anyone have any idea on how to root Android oreo in system-mode?? I really don't like system less and magisk, and I won't be using them.
Any help appreciated.
Thanks

Does Oreo even support system-mode su?
And why exactly would you like system-mode? Flashing Magisk is much easier and painless, plus you also get access to Magisk Modules that are kept between updates, unlike (most) system mods.

BolintsMiki said:
Does Oreo even support system-mode su?
And why exactly would you like system-mode? Flashing Magisk is much easier and painless, plus you also get access to Magisk Modules that are kept between updates, unlike (most) system mods.
Click to expand...
Click to collapse
I don't know if oreo supports system-mode supersu. I read on a XDA Thread that someone got it to work. Followed his steps but still it wasn't doing the job for me. As to why I prefer system-mode, take the app FasterGPS for example. It's a very simple app which modifies the GPS.conf file in /etc in order to have a faster satellite lock depending on you country. This app does not work with SYSTEMLESS supersu. It won't edit the file, despite having super user rights. I'm also facing problems with the terminal emulator, not able to acquire superuser rights when I type su. Don't know what's up with that.

Same request from me, I need to move an app to system, but keeps telling me that I can't, so I started investigating and found out that /system is in r/o mode, and it seems that this depends on Oreo root method, and as far as I know system root is the only method to do that...or am I wrong? Maybe there's a Magisk module to do that?
And what if I try to flash a Nougat rom, will this make my /system folder r/w finally?

MajinBug said:
Same request from me, I need to move an app to system, but keeps telling me that I can't, so I started investigating and found out that /system is in r/o mode, and it seems that this depends on Oreo root method, and as far as I know system root is the only method to do that...or am I wrong? Maybe there's a Magisk module to do that?
And what if I try to flash a Nougat rom, will this make my /system folder r/w finally?
Click to expand...
Click to collapse
You are correct. As far as I'm aware, there is no magisk module that mounts system as rw, so that's a problem. As of now, there is no way that you can root system mode. Too bad.

I have here a V30 and hate too magisk systemless root.
Tried like you, every combi but there just will not work.

me too i almost tried everything.. system mode supersu.zip with no verity.zip.. and i tried the command "echo SYSTEMLESS=false>>/data/.supersu" and also with the normal supersu.. nothing works, i think 2 things can solve ur problem.. it's a custom ROM or downgrading to lollipop or marshmallow I dunno exactly.. (I didn't switch to to a custom ROM cuz i prefer stock oreo rom on my S7 G930F)