Develop Bugs

[Solved][Q] rooting on 4.4 kitkat

i have tried numerous ways to gain root on 4.4 but failed miserably. ive sideloaded and used nrt without success. supersu icon doesnt appear in the app drawer. any suggestions?

dalbig said:
i have tried numerous ways to gain root on 4.4 but failed miserably. ive sideloaded and used nrt without success. supersu icon doesnt appear in the app drawer. any suggestions?
Click to expand...
Click to collapse
Do you have TWRP installed? The automatic root feature in it worked fine for me.

mandrsn1 said:
Do you have TWRP installed? The automatic root feature in it worked fine for me.
Click to expand...
Click to collapse
I have the exact same problem with not being able to root every method I try

mowz9999 said:
I have the exact same problem with not being able to root every method I try
Click to expand...
Click to collapse
use toolkit for nexus 7 2013 and chose root and twrp recovery
work very well with me

murad052 said:
use toolkit for nexus 7 2013 and chose root and twrp recovery
work very well with me
Click to expand...
Click to collapse
I tried root kit too and it completes with no problems but superuser is never there and I don't have root access

mowz9999 said:
I tried root kit too and it completes with no problems but superuser is never there and I don't have root access
Click to expand...
Click to collapse
wired.. try this. first enable usb debuging mode from developer option
rebot to fast boot. and open tools kite i have version 1.0.2
chose ur device.
first install recovery TWRP.. number 6 i think in toolkit
then go back again and root the device number 4.. then chose number 2..
remember you have to unlock ir device first.
i hope this could work for you

dalbig said:
i have tried numerous ways to gain root on 4.4 but failed miserably. ive sideloaded and used nrt without success. supersu icon doesnt appear in the app drawer. any suggestions?
Click to expand...
Click to collapse
Install this in TWRP
http://download.chainfire.eu/346/SuperSU/UPDATE-SuperSU-v1.55.zip
Some later versions have non-functioning install scripts.

would using ART be a conflict maybe?

dalbig said:
would using ART be a conflict maybe?
Click to expand...
Click to collapse
no effect at all... i disable it just cuz of whatsapp

i still cant gain root.. im going to try using dalvik and see if there is a change.

All I did was I flashed TWRP then installed SuperSU 1.65 through TWRP. It says I have root access.

murad052 said:
wired.. try this. first enable usb debuging mode from developer option
rebot to fast boot. and open tools kite i have version 1.0.2
chose ur device.
first install recovery TWRP.. number 6 i think in toolkit
then go back again and root the device number 4.. then chose number 2..
remember you have to unlock ir device first.
i hope this could work for you
Click to expand...
Click to collapse
I still could not get superusersu installed Its able to flash over recovery fine but when rooting it says everything is fine but superuser never shows up and I dont have root access Thanks for trying I appreciate it

I had problems originally but I did like others. I downloaded the newest SuperSU 1.65.zip, moved it onto the N7. Booted into TWRP, selected Install and selected the zip. After that I rebooted from TWRP and I had root.
Sent from my Nexus 7 (2013) running 4.4

ive tried 1.55, 1.65 and 1.69... not one of them worked

dalbig said:
ive tried 1.55, 1.65 and 1.69... not one of them worked
Click to expand...
Click to collapse
Exact same thing here!:crying:

dalbig said:
ive tried 1.55, 1.65 and 1.69... not one of them worked
Click to expand...
Click to collapse
How are you installing them? Where are you downloading from? Have you tried just allowing TWRP to install root using the one it comes with?

sfhub said:
How are you installing them? Where are you downloading from? Have you tried just allowing TWRP to install root using the one it comes with?
Click to expand...
Click to collapse
Sideload, flashing the zips through twrp, using nrt... Got the zips of this forum.
Sent from my MB886 using XDA Premium 4 mobile app

dalbig said:
Sideload, flashing the zips through twrp, using nrt... Got the zips of this forum.
Sent from my MB886 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I am just trying to understand where things are going wrong.
I went back and did a fresh factory image of KRT16O wiping user data.
I then copied
http://download.chainfire.eu/346/SuperSU/UPDATE-SuperSU-v1.55.zip
to the virtual sdcard.
I rebooted to bootloader and started twrp using
fastboot boot twrp.img
Then I chose to install SuperSU 1.55 using the above file.
Then rebooted to Android.
The SuperSU app was in the app drawer and I could perform su from adb shell and it would ask for permissions.

After I installed the factory images, I rooted my device. I don't use toolkits, because I think they make thing more complicated that it actually is. It is best to learn ADB whenever you can. That makes rooting so much easier.
Before I entered the bootloader, I downloaded SuperSU v1.69 through Chrome.
I made sure that all drivers were installed and began rooting.
Since my bootloader already was unlocked, I just flashed TWRP 2.6.3.1 with fastboot using this command:"fastboot flash recovery openrecovery-twrp-2.6.3.1-flo.img" without quotes.
That went smoothly, afterwards I rebooted to TWRP and flashed the zip... There I was rooted.
SuperSU: http://download.chainfire.eu/365/SuperSU/UPDATE-SuperSU-v1.69.zip
TWRP: http://techerrata.com/file/twrp2/flo/openrecovery-twrp-2.6.3.1-flo.img
Hope this helped.

I just got root access! I found superuser in settings under apps but it would not show up in app drawer and would not give permissions to anything.I then disabled the updates back to superusers 1.55 and it showed up in app drawer and busy box asked for permission right away and root checker confirmed root access. Then updated through play store and everything is good now. Hope that helps

TWRP cannot Mount all the storage, and everytime I reboot, fastboot page comes out

I am really in trouble.
Is there anyone who can help me？
I’m not sure whether it is the fastboot page or something, but it says: your device has been unlocked and Nextbit OS can't be checked for tempering. You device will continue
booting in 5 seconds.
Here I find another problem. Once I get rooted, my camera stops working, no matter which ROM I try.

pickmeup12345 said:
I am really in trouble.
Is there anyone who can help me？
I’m not sure whether it is the fastboot page or something, but it says: your device has been unlocked and Nextbit OS can't be checked for tempering. You device will continue
booting in 5 seconds.
Here I find another problem. Once I get rooted, my camera stops working, no matter which ROM I try.
Click to expand...
Click to collapse
The first boot up page after unlocking the bootloader is simply to tell you THE BOOTLOADER IS UNLOCKED.
Now, for the camera.. Assuming the camera works in stock, I would do a complete factory reset, then try Omni. Are you using Magisk 11.1 or SuperSu SR3? Because anything else breaks the camera usually.
SuperSu SR3: https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Magisk 11.1: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445

Saythis said:
The first boot up page after unlocking the bootloader is simply to tell you THE BOOTLOADER IS UNLOCKED.
Now, for the camera.. Assuming the camera works in stock, I would do a complete factory reset, then try Omni. Are you using Magisk 11.1 or SuperSu SR3? Because anything else breaks the camera usually.
SuperSu SR3: https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Magisk 11.1: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Click to expand...
Click to collapse
THX, I used SuperSu 2.76 before, and I tried SR3, now it works well.
So you mean the boot up page will be there whenever I reboot my phone?

pickmeup12345 said:
THX, I used SuperSu 2.76 before, and I tried SR3, now it works well.
So you mean the boot up page will be there whenever I reboot my phone?
Click to expand...
Click to collapse
Yes it will be unless you relock the bootloader

Update does not finishes stuck on downloading (March update)?

I was using magisk so before update i uninstalled the magisk and checked for update it started immediately since then its stuck on downloading i did force stop for play services and google framework and checked again but nothing worked. However i did factory reset and then checked again this time also it stuck on downloading update. Does anyone know what is the issue ?

goti(0) said:
I was using magisk so before update i uninstalled the magisk and checked for update it started immediately since then its stuck on downloading i did force stop for play services and google framework and checked again but nothing worked. However i did factory reset and then checked again this time also it stuck on downloading update. Does anyone know what is the issue ?
Click to expand...
Click to collapse
There's really no reason to uninstall magisk before an update. Just let it update itself through the app. You should be able to just flash the magisk 16.0 zip in twrp to get things back to normal.
When you say update, you mean OTA or fastbooting the factory image?

Badger50 said:
There's really no reason to uninstall magisk before an update. Just let it update itself through the app. You should be able to just flash the magisk 16.0 zip in twrp to get things back to normal.
When you say update, you mean OTA or fastbooting the factory image?
Click to expand...
Click to collapse
OTA only

goti(0) said:
OTA only
Click to expand...
Click to collapse
Ah..gotchya. Yep, those can cause problems for sure with magisk. Did you try side loading the OTA zip, or consider learning fastboot?

goti(0) said:
OTA only
Click to expand...
Click to collapse
You probably got my issue lol did you flash a custom rom before flashing back stock or any mod that would give you the internal provider error pop up after every boot?

goti(0) said:
I was using magisk so before update i uninstalled the magisk and checked for update it started immediately since then its stuck on downloading i did force stop for play services and google framework and checked again but nothing worked. However i did factory reset and then checked again this time also it stuck on downloading update. Does anyone know what is the issue ?
Click to expand...
Click to collapse
No magisk installed here. Had the same issue of getting stuck at downloading. Factory reset and it worked. Need enough battery charge for it to work. Download was slow on a fast internet btw.
Hope it works fine for you soon
Sent from my Pixel 2 XL using Tapatalk

Badger50 said:
Ah..gotchya. Yep, those can cause problems for sure with magisk. Did you try side loading the OTA zip, or consider learning fastboot?
Click to expand...
Click to collapse
finally i did flash latest image using deuces script as factory reset did not solve the problem but i was wondering what may be the reason as i have never heard of this kind of issue so i posted if anyone else has the same problem.
Jiggs82 said:
You probably got my issue lol did you flash a custom rom before flashing back stock or any mod that would give you the internal provider error pop up after every boot?
Click to expand...
Click to collapse
no i am on stock+magisk since day 1 no rom at all.
X-jo said:
No magisk installed here. Had the same issue of getting stuck at downloading. Factory reset and it worked. Need enough battery charge for it to work. Download was slow on a fast internet btw.
Hope it works fine for you soon
ya i did that but i used deuces script so i can not tell that it will check the update correctly for next month security bulletin.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse

Enable Always On Display on Pixel XL Android Pie - Magisk

This is actually relatively simple, and has worked with every update on Oreo.
Use at your own risk, while it's unlikely something like this will brick your device, I take no responsibility if anything happens. Always know how to get yourself out of a bootloop. The APKs and Magisk module posted by others should be fine, however feel free to extract the APK yourself from the Pixel 2/3 factory images.
Download the APK here (or extract it from the Pixel 2/XL's P DP1 factory image), install TWRP and Magisk (I used v16). Use a file manager with root permissions, I used ES file manager. Copy Framework-res__auto_generated.apk from here to System/Vendor/Overlay/ and overwrite (you could also copy the original somewhere if you wanted a backup). SystemUI will crash or the phone will reboot. Due to this, apps will constantly be crashing, to fix this, open up the file manager again and set the permissions correctly.
(Incase anyone is curious why I don't have a navbar, I removed it with a buildprop edit, I'm a bit nervous about burn in, and that way I can avoid it. Also, AOD moves around slowly)
Based on what I've seen with the leaks from the Pixel 3, it may be this simple to get the AOD with a wallpaper when we get the file from the Pixel 3 XL. But then again, I'm not a developer, so maybe not. But I'm glad this is still working for now!
APKs are posted by various users here, once I get access to my PC I'll be sure to post them in chronological order every time a update is put out.
Magisk module here https:/forum.xda-developers.com/pixel/themes/mod-display-enabler-magisk-module-t3857034

But doesn't magisk not work?

muppetmaster916 said:
But doesn't magisk not work?
Click to expand...
Click to collapse
That's what I thought, it seems it's just a Magisk manager issue, root works but not in all apps. Worked fine with a file manager for me.

Doesn't work for me. Everytime I navigate to root folder, it comes up blank

dictionary said:
Doesn't work for me. Everytime I navigate to root folder, it comes up blank
Click to expand...
Click to collapse
Did you install Magisk via TWRP? Only other thing I can think of, is going back to 8.1, rooting and giving the file manager root permissions, then flashing P (as a update, without wiping data) then flashing Magisk again. Then opening the file manager, it will already be able to use root permissions. It seems like it's just the Magisk app that is broken, not root itself.

YTSec said:
Did you install Magisk via TWRP? Only other thing I can think of, is going back to 8.1, rooting and giving the file manager root permissions, then flashing Oreo (as a update, without wiping data) then flashing Magisk again. Then opening the file manager, it will already be able to use root permissions. It seems like it's just the Magisk app that is broken, not root itself.
Click to expand...
Click to collapse
Yeah. It's not so serious to do all that work lol. I'm sure a real solution will come soon, but thank you

What's the battery hit? Negligible?

nadiros said:
What's the battery hit? Negligible?
Click to expand...
Click to collapse
It's just a disclaimer they have, I have been using AOD since early December with no battery issues.

Tried this on Android O March 2018, extracted the file from Pixel 2 XL factory images, but I'm not getting the option in setting.
Do I have to do anything else other than copy file and set permissions?
Edit: Read your other thread, and did it through TWRP file manager as I don't have root. I guess it only works using a file manager with root while booted.
Sent from my Pixel XL using Tapatalk

Couldn't get Android P to boot after this. Anyone installed on DP1 ?

nadiros said:
Couldn't get Android P to boot after this. Anyone installed on DP1 ?
Click to expand...
Click to collapse
The system isn't booting or you are having other issues?

Any way to enable this without root? Like for Oreo installing the Substratum and Andromeda plugin?

nadiros said:
Couldn't get Android P to boot after this. Anyone installed on DP1 ?
Click to expand...
Click to collapse
Yeah I'm up and running. I moved the file, rebooted, got into ES file (after a few tries) and was able to fix the permissions. I'm on Dev preview with magisk and a few modules + this mod now.

muppetmaster916 said:
Yeah I'm up and running. I moved the file, rebooted, got into ES file (after a few tries) and was able to fix the permissions. I'm on Dev preview with magisk and a few modules + this mod now.
Click to expand...
Click to collapse
Great, glad it worked out. I'm having issues with Magisk though, no modules seem to work. Did you do anything different to get them working?

jidccruz said:
Any way to enable this without root? Like for Oreo installing the Substratum and Andromeda plugin?
Click to expand...
Click to collapse
I don't think so, unfortunately. I tried via TWRP and nothing stuck until I rooted.

YTSec said:
I don't think so, unfortunately. I tried via TWRP and nothing stuck until I rooted.
Click to expand...
Click to collapse
Will try your workaround. Hopefully it works. I'm already in Android P? Any way to install TWRP and Magisk without clearing data?

jidccruz said:
Will try your workaround. Hopefully it works. I'm already in Android P? Any way to install TWRP and Magisk without clearing data?
Click to expand...
Click to collapse
As long as you have a unlocked bootloader (which you should if you are on the first P preview, even though it is insanely stable) it won't wipe your device. Magisk was actually updated to work with P.

YTSec said:
As long as you have a unlocked bootloader (which you should if you are on the first P preview, even though it is insanely stable) it won't wipe your device. Magisk was actually updated to work with P.
Click to expand...
Click to collapse
Thanks for the info. Will try it now!

Magisk has just been updated to support Android P

YTSec said:
Great, glad it worked out. I'm having issues with Magisk though, no modules seem to work. Did you do anything different to get them working?
Click to expand...
Click to collapse
Choose download rather than install, within magisk, then use twrp to flash.

Device turns off randomly after root

Hi guys, I rooted my redmi note 8 yesterday. Everything went well except two things: on boot the error message said that "there is an internal problem" and the phone reboots/shuts down itself.
Any thoughts?

cicish said:
Hi guys, I rooted my redmi note 8 yesterday. Everything went well except two things: on boot the error message said that "there is an internal problem" and the phone reboots/shuts down itself.
Any thoughts?
Click to expand...
Click to collapse
You should explain the problem obviously if you want a help, if your phone still working you should flash twerp.img to be able to root it and solve any existing problem by flashing new rom

niceman2007 said:
You should explain the problem obviously if you want a help, if your phone still working you should flash twerp.img to be able to root it and solve any existing problem by flashing new rom
Click to expand...
Click to collapse
Hey thanks for answer.
Actually i did everything correctly, flashed latest twrp, tried several roms, oficial, unoficial etc., But still no result. After all these, ive flashed the stock rom which solved the problem but phone is no more rooted. So..

cicish said:
Hey thanks for answer.
Actually i did everything correctly, flashed latest twrp, tried several roms, oficial, unoficial etc., But still no result. After all these, ive flashed the stock rom which solved the problem but phone is no more rooted. So..
Click to expand...
Click to collapse
If you still want to root it again,after flasing new rom go to twero and then go to wipe then format,you should format your phone after rom flashing,try this and inform me

Yes yes! I want to root phone once again. So the steps are these:
1) booting into twrp with adb from pc.
2) from the twrp menu wiping and formating the data
3) instaling new rom
Is this true?
Thanks!

If you want to root you don't have to install another custom rom unless you don't like the stock rom. If you like your current stock rom, then flash twrp in fastboot and download the latest magisk stable zip and also diasble dm-verity zip. Using twrp first flash disable dm-verity zip and then magisk zip, wipe dalvik cache and reboot to system, hopefully you would have root permission.

Leeban Joseph said:
If you want to root you don't have to install another custom rom unless you don't like the stock rom. If you like your current stock rom, then flash twrp in fastboot and download the latest magisk stable zip and also diasble dm-verity zip. Using twrp first flash disable dm-verity zip and then magisk zip, wipe dalvik cache and reboot to system, hopefully you would have root permission.
Click to expand...
Click to collapse
You mean that its possible to have root access on stock rom?

Leeban Joseph said:
If you want to root you don't have to install another custom rom unless you don't like the stock rom. If you like your current stock rom, then flash twrp in fastboot and download the latest magisk stable zip and also diasble dm-verity zip. Using twrp first flash disable dm-verity zip and then magisk zip, wipe dalvik cache and reboot to system, hopefully you would have root permission.
Click to expand...
Click to collapse
Hey, I was able to flash magical using twrp but can't flash dm-verity. It gives me some error 1 with no description. I could flash magisk. What can the problem be? Thanks!

cicish said:
Hey, I was able to flash magical using twrp but can't flash dm-verity. It gives me some error 1 with no description. I could flash magisk. What can the problem be? Thanks!
Click to expand...
Click to collapse
From your stock rom extract the boot.img and place it on your SD card. Flash the boot image using twrp or you can also flash in fastboot, then reboot. Now boot to twrp recovery and flash dm-verity first and then magisk zip. Worked for me I'm having root permission with stock rom.

Leeban Joseph said:
From your stock rom extract the boot.img and place it on your SD card. Flash the boot image using twrp or you can also flash in fastboot, then reboot. Now boot to twrp recovery and flash dm-verity first and then magisk zip. Worked for me I'm having root permission with stock rom.
Click to expand...
Click to collapse
i could grant the root permission on stock rom before you wrote this. thank you very much! but i still have a problem with a custom rom as it randomly turns off or reboots the device. strange

cicish said:
i could grant the root permission on stock rom before you wrote this. thank you very much! but i still have a problem with a custom rom as it randomly turns off or reboots the device. strange
Click to expand...
Click to collapse
UPDATE: after another custom rom install failure, i got back to stock miui 11 with miflash tool. the problem is now that when i unlock the bootloader and try to flash magisk and disable-dm-verity, the system refuses to boot. the redmi note 8 logo is sticked on boot. i dont understand what i am doing incorrectly. if there are any suggestions im ready to try.

cicish said:
UPDATE: after another custom rom install failure, i got back to stock miui 11 with miflash tool. the problem is now that when i unlock the bootloader and try to flash magisk and disable-dm-verity, the system refuses to boot. the redmi note 8 logo is sticked on boot. i dont understand what i am doing incorrectly. if there are any suggestions im ready to try.
Click to expand...
Click to collapse
Is your bootloader unlocked right now or did you lock it while flashing using miflash tool.

Leeban Joseph said:
Is your bootloader unlocked right now or did you lock it while flashing using miflash tool.
Click to expand...
Click to collapse
the bootloader was unlocked. everything went kinda fine, until i flashed youtube vanced from magisk: when i did that, the system was unable to boot. i don't know what's happening. is there anything to do with kernel or something? really interesting what i am doing wrong.

cicish said:
the bootloader was unlocked. everything went kinda fine, until i flashed youtube vanced from magisk: when i did that, the system was unable to boot. i don't know what's happening. is there anything to do with kernel or something? really interesting what i am doing wrong.
Click to expand...
Click to collapse
I think it may be because of YouTube vanced module. If you remove the module you might be able to boot. In twrp in the advanced option select file manager and then select data/adb/magisk/ in that you will find the list of installed modules, select the one which is causing the problem and delete that folder and try to reboot.

Leeban Joseph said:
I think it may be because of YouTube vanced module. If you remove the module you might be able to boot. In twrp in the advanced option select file manager and then select data/adb/magisk/ in that you will find the list of installed modules, select the one which is causing the problem and delete that folder and try to reboot.
Click to expand...
Click to collapse
I've already flashed the stock rom but this will help me next time! Thanks!
I'll stop trying for some days cause I'm really tired with tweaking so thanks and will get back!

cicish said:
i could grant the root permission on stock rom before you wrote this. thank you very much! but i still have a problem with a custom rom as it randomly turns off or reboots the device. strange
Click to expand...
Click to collapse
Your device reboots randomly on custom rom because probably it was made for tianma display and you have hauxing display

the_weird_aquarian said:
Your device reboots randomly on custom rom because probably it was made for tianma display and you have hauxing display
Click to expand...
Click to collapse
Hey, thanks for the answer. i've just googled about it and you are right. checked the TP version and it says that i have huaxing display. in the Lineage OS thread the moderator wrote that the next update will fix that bug. hopefully ill be able to install custom rom. also if you know, are there any custom roms for huaxing display? thank you man!

cicish said:
Hey, thanks for the answer. i've just googled about it and you are right. checked the TP version and it says that i have huaxing display. in the Lineage OS thread the moderator wrote that the next update will fix that bug. hopefully ill be able to install custom rom. also if you know, are there any custom roms for huaxing display? thank you man!
Click to expand...
Click to collapse
currently bootleggers rom,PE official and unofficial and drepfest all have reboot issues in huaxing display. Haven't tried any other rom yet..still on MIUI..waiting to get the issue fixed asap.

the_weird_aquarian said:
currently bootleggers rom,PE official and unofficial and drepfest all have reboot issues in huaxing display. Haven't tried any other rom yet..still on MIUI..waiting to get the issue fixed asap.
Click to expand...
Click to collapse
i've tried Lineage OS too and it also has reboot issue. i've checked a thread here https://forum.xda-developers.com/redmi-note-5-pro/development/derp-kernel-clang-4-4-138-t3804996 that flashing a different kernel when you have flashed a custom rom can fix the problem. idk if its safe to do

cicish said:
i've tried Lineage OS too and it also has reboot issue. i've checked a thread here https://forum.xda-developers.com/redmi-note-5-pro/development/derp-kernel-clang-4-4-138-t3804996 that flashing a different kernel when you have flashed a custom rom can fix the problem. idk if its safe to do
Click to expand...
Click to collapse
that thread is for redmi note 5 pro..and flashing different kernel probably won't solve it because I know few guys flashed genom kernel but still ended up with reboot in huaxing display. Maybe waiting for fix is better.