Hello XDA !
This is my first post..sorry for my bad english.
I bought a S7 (SM-G930F) Android 8.0 and i rooted it then i noticed that was just systemless root.. and it's totally useless for me because i want to uninstall system apps and change build.prop..
so I flashed the stock rom and reflashed TWRP, then I executed a command to force SuperSU to install in system
(echo SYSTEMLESS=false>>/data/.SuperSU)
and I installed SuperSU.zip..but it stucks on bootloop.. I tried many different SuperSU.zip versions even a modified version for system mode root, but nothing works..
by the way I installed no-verity-opt-encrypt-6.1.zip before installing SuperSU.zip !
ysnelazzab said:
Hello XDA !
This is my first post..sorry for my bad english.
I bought a S7 (SM-G930F) Android 8.0 and i rooted it then i noticed that was just systemless root.. and it's totally useless for me because i want to uninstall system apps and change build.prop..
so I flashed the stock rom and reflashed TWRP, then I executed a command to force SuperSU to install in system
(echo SYSTEMLESS=false>>/data/.SuperSU)
and I installed SuperSU.zip..but it stucks on bootloop.. I tried many different SuperSU.zip versions even a modified version for system mode root, but nothing works..
by the way I installed no-verity-opt-encrypt-6.1.zip before installing SuperSU.zip !
Click to expand...
Click to collapse
i havent rooted an S7 in a while, but dont you just flash twrp in Odin with the reboot box unchecked and once the flash completes, reboot into twrp which will present you a slider that says something along the lines of "slide to allower SU access" or something like that. Once youve done that, then you flash magisk in TWRP, boot, install busybox, and you should then be asked if you want to grant SU access to busybox, if it does that, youre all set
youdoofus said:
i havent rooted an S7 in a while, but dont you just flash twrp in Odin with the reboot box unchecked and once the flash completes, reboot into twrp which will present you a slider that says something along the lines of "slide to allower SU access" or something like that. Once youve done that, then you flash magisk in TWRP, boot, install busybox, and you should then be asked if you want to grant SU access to busybox, if it does that, youre all set
Click to expand...
Click to collapse
Thank you so much for your response !
I did everything in the correct way, i flashed twrp with reboot option disabled.. and i formated data then reboot to recovery and I installed no verity and after that i installed SuperSU and it's done successfully but it ended up with a bootloop..
also I tried to install a system mode supersu.zip and it freezes TWRP and stuck on "installing"
I think literally I can't do the system root.. so i did systemless root.
ysnelazzab said:
Thank you so much for your response !
I did everything in the correct way, i flashed twrp with reboot option disabled.. and i formated data then reboot to recovery and I installed no verity and after that i installed SuperSU and it's done successfully but it ended up with a bootloop..
also I tried to install a system mode supersu.zip and it freezes TWRP and stuck on "installing"
I think literally I can't do the system root.. so i did systemless root.
Click to expand...
Click to collapse
the F models should allow for system root, not sure tho as i didnt spend much time with my S7 and S7 Edge. Still have em tho. If i remember, i could dink with them tonight
youdoofus said:
the F models should allow for system root, not sure tho as i didnt spend much time with my S7 and S7 Edge. Still have em tho. If i remember, i could dink with them tonight
Click to expand...
Click to collapse
mine is G930F oreo 8.0 i tried everything to do system root but failed.. one thing I didn't do is a custom rom. i prefer a rooted stock rom.
ysnelazzab said:
mine is G930F oreo 8.0 i tried everything to do system root but failed.. one thing I didn't do is a custom rom. i prefer a rooted stock rom.
Click to expand...
Click to collapse
well, you cant do a custom ROM without a custom recovery. bootloader is unlocked i assume
youdoofus said:
well, you cant do a custom ROM without a custom recovery. bootloader is unlocked i assume
Click to expand...
Click to collapse
as I said i have TWRP which is a custom recovery. and i don't want custom ROM i just want my stock ROM system rooted not systemless.
ysnelazzab said:
as I said i have TWRP which is a custom recovery. and i don't want custom ROM i just want my stock ROM system rooted not systemless.
Click to expand...
Click to collapse
im well aware that TWRP is a custom recovery, i remember when it first launched and people were converting from CWM to TWRP. Anyways, if youve successfully installed twrp, try factory resetting the device and then booting. You should only need to flash magisk in TWRP and busy box in the OS once booted
Related
Just flashed the factory Rom and got everything set up. I flashed TWRP then tried to flash the latest SuperSu to get root and it installed it but when I went to open it it would say that I don't have any binaries installed and I can't uninstall SuperSU either. I tried to install CWM Recovery and refresh it through there but I still have the same issues... :/ What am I doing wrong or how can I get my phone rooted properly? Thanks for any help!
Nocturnal86 said:
Just flashed the factory Rom and got everything set up. I flashed TWRP then tried to flash the latest SuperSu to get root and it installed it but when I went to open it it would say that I don't have any binaries installed and I can't uninstall SuperSU either. I tried to install CWM Recovery and refresh it through there but I still have the same issues... :/ What am I doing wrong or how can I get my phone rooted properly? Thanks for any help!
Click to expand...
Click to collapse
You need to flash a kernel that is permissive and then flash SuperSU there are a few in the forums if you search you shall find them
Instead of a permissive kernel, simply use Chainfire's AutoRoot, which will flash a more secure kernel and SuperSU automatically. You don't even need TWRP for this. http://download.chainfire.eu/363/CF-Root/CF-Auto-Root/CF-Auto-Root-hammerhead-hammerhead-nexus5.zip
Go to http://autoroot.chainfire.eu/ to get AutoRoot for other devices.
aalaap said:
Instead of a permissive kernel, simply use Chainfire's AutoRoot, which will flash a more secure kernel and SuperSU automatically. You don't even need TWRP for this. http://download.chainfire.eu/363/CF-Root/CF-Auto-Root/CF-Auto-Root-hammerhead-hammerhead-nexus5.zip
Go to http://autoroot.chainfire.eu/ to get AutoRoot for other devices.
Click to expand...
Click to collapse
So I flash this in ADB? Is the secure kernel the same as stock? and if I were to flash a customer kernel like FK would I lose root? Sorry for all the questions just trying to clarify some stuff so I'm not completely ignorant to what I'm doing lol
There's a batch file that does it. You run it in the bootloader, not ADB.
FK has a Lollipop compatible kernel, but try and root stock first. Then flash FK's Lollipop version (it's different) and run CF AutoRoot again. Just to be sure things are working. Personally, I'm going to use stock for a while, understand the performance and then try FK or EX or whatever, so I'll be able to tell the difference.
hi guys.....
i had recently unroot my moto g3 and install stock root to use my jio sim.
but i really miss the root access so, is there any way to to have root access.
when i flash supersu it will get stuck into bootlogo and will not proceed.
i waited for half an hr but no sign of booting up
anyone have a way to get root access to stock rom plzz help........
Just flash this super user zip file
http://forum.xda-developers.com/attachment.php?attachmentid=3655401&d=1456122222
is supersu installing systemless?
make sure to do this first in twrp terminal: "echo SYSTEMLESS=true>>/data/.supersu"
Sushilsingh said:
hi guys.....
i had recently unroot my moto g3 and install stock root to use my jio sim.
but i really miss the root access so, is there any way to to have root access.
when i flash supersu it will get stuck into bootlogo and will not proceed.
i waited for half an hr but no sign of booting up
anyone have a way to get root access to stock rom plzz help........
Click to expand...
Click to collapse
You already have an existing thread on this problem, and were told what needs to be done and where to go to get that information and additional assistance... Why are you not using the resources that were given to you previously? There is no magic fix, something was done incorrectly or you are using the incorrect files.
The answer and all support you will need are in this thread: http://forum.xda-developers.com/2015-moto-g/general/guide-how-to-root-moto-g-2015-model-t3448572
acejavelin said:
You already have an existing thread on this problem, and were told what needs to be done and where to go to get that information and additional assistance... Why are you not using the resources that were given to you previously? There is no magic fix, something was done incorrectly or you are using the incorrect files.
The answer and all support you will need are in this thread: http://forum.xda-developers.com/2015-moto-g/general/guide-how-to-root-moto-g-2015-model-t3448572
Click to expand...
Click to collapse
buddy i just install a clean XT1550_OSPREY_RETASIA_DS_2GB_6.0.1_MPI24.107-55_cid7_subsidy-DEFAULT_CFC.xml.zip
stock rom and twrp twrp-osprey-3.0.2-r1.img as you told.
and that command also
echo SYSTEMLESS=true>>/data/.supersu
cat /data/.supersu
it shows systemless=true
and installed latest supersu SR1-SuperSU-v2.78-SR1-20160915123031.zip from its official site
after that i wipe cache and dalvik.
i reboot it.
and its get reboot without supersu (root) permission.
what should i do?
Sushilsingh said:
buddy i just install a clean XT1550_OSPREY_RETASIA_DS_2GB_6.0.1_MPI24.107-55_cid7_subsidy-DEFAULT_CFC.xml.zip
stock rom and twrp twrp-osprey-3.0.2-r1.img as you told.
and that command also
echo SYSTEMLESS=true>>/data/.supersu
cat /data/.supersu
it shows systemless=true
and installed latest supersu SR1-SuperSU-v2.78-SR1-20160915123031.zip from its official site
after that i wipe cache and dalvik.
i reboot it.
and its get reboot without supersu (root) permission.
what should i do?
Click to expand...
Click to collapse
So you fastboot flashed the ROM and verified it booted successfully (an initial boot is essential prior to rooting, it sets up the RAM disk and other boot image things the first time), rebooted, flashed TWRP (3.0+) and backed up, did the echo command and flashed SuperSU 2.78 SR1 and it still failed?
Flash the 2.62-3 beta of SuperSU https://download.chainfire.eu/751/SuperSU/ it forces systemless install regardless of detected options. You can update normally in the Play Store, then update the binary in the app.
One of those two methods will work, if it doesn't then you have something more going on then meets the eye or there is a piece of information you are not giving us. This is a tested and working process on every single known Moto G 2015 variant.
BTW, clearing cache and dalvik is not required when rooting, you are just increasing the time it takes to boot for no reason.
acejavelin said:
So you fastboot flashed the ROM and verified it booted successfully (an initial boot is essential prior to rooting, it sets up the RAM disk and other boot image things the first time), rebooted, flashed TWRP (3.0+) and backed up, did the echo command and flashed SuperSU 2.78 SR1 and it still failed?
Flash the 2.62-3 beta of SuperSU https://download.chainfire.eu/751/SuperSU/ it forces systemless install regardless of detected options. You can update normally in the Play Store, then update the binary in the app.
One of those two methods will work, if it doesn't then you have something more going on then meets the eye or there is a piece of information you are not giving us. This is a tested and working process on every single known Moto G 2015 variant.
BTW, clearing cache and dalvik is not required when rooting, you are just increasing the time it takes to boot for no reason.
Click to expand...
Click to collapse
well, all the things get installed successfully but even the installation of supersu.zip file also
but it always reboot without any root access or supersu app
i try to install supersu from playstore but it wont help much
after that i tried BETA-SuperSU-v2.62-3-20151211162651.zip this version
and this version does the job
thanks buddy, i really appreciate your help.
acejavelin said:
So you fastboot flashed the ROM and verified it booted successfully (an initial boot is essential prior to rooting, it sets up the RAM disk and other boot image things the first time), rebooted, flashed TWRP (3.0+) and backed up, did the echo command and flashed SuperSU 2.78 SR1 and it still failed?
Flash the 2.62-3 beta of SuperSU https://download.chainfire.eu/751/SuperSU/ it forces systemless install regardless of detected options. You can update normally in the Play Store, then update the binary in the app.
One of those two methods will work, if it doesn't then you have something more going on then meets the eye or there is a piece of information you are not giving us. This is a tested and working process on every single known Moto G 2015 variant.
BTW, clearing cache and dalvik is not required when rooting, you are just increasing the time it takes to boot for no reason.
Click to expand...
Click to collapse
Thanks, thats works for me..! i tried 3 time until work
PD: (when you root, install recovery or unlock bootloader without enough time happens this kind of things)..
I have Galaxy S6 (920F) with Android Nougat.
I have managed to install TWRP Recovery on my device and it is allowing me to install .zip files. But my phone is Not ROOTED.
So my question is,
If I flash .zip(s) now that are made for my device, will it be installed successfully?
or my device will stuck on bootloop?
Well, if you are flashing some files into directories that don't require root to access, it will work.
But lets say you want to flash ported system app (like message app). It will not work, since it requires flashing into \system and that directory requires root to be accessed and modified. :good:
Ragazzza said:
Well, if you are flashing some files into directories that don't require root to access, it will work.
But lets say you want to flash ported system app (like message app). It will not work, since it requires flashing into \system and that directory requires root to be accessed and modified. :good:
Click to expand...
Click to collapse
so if I'd want to install a custom rom i need to have twrp installed and also the phone needs to be rooted, right?(kind of a stupid question, I know)
also, are these tutorials good to install twrp and root my g920f with the xef 7.0 android?
/watch?v=oDX8OT0jWw0&t=4s
/watch?v=sHXvuRRlNnI
ciprian97pop said:
so if I'd want to install a custom rom i need to have twrp installed and also the phone needs to be rooted, right?(kind of a stupid question, I know)
also, are these tutorials good to install twrp and root my g920f with the xef 7.0 android?
/watch?v=oDX8OT0jWw0&t=4s
/watch?v=sHXvuRRlNnI
Click to expand...
Click to collapse
Yup, you need root for rom. Hm i would like to guide you by writting here, but just watch on youtube how to root galaxy s6 nougat, about a week ago i have rooted my friends s6 flat g920f, everything went smooth! :good:
Ragazzza said:
Yup, you need root for rom. Hm i would like to guide you by writting here, but just watch on youtube how to root galaxy s6 nougat, about a week ago i have rooted my friends s6 flat g920f, everything went smooth! :good:
Click to expand...
Click to collapse
ok then
basically, boot into recovery, flash twrp, reboot, boot again into recovery which now is twrp then flash another zip and in the end you have a custom recovery and root, righr?
ciprian97pop said:
ok then
basically, boot into recovery, flash twrp, reboot, boot again into recovery which now is twrp then flash another zip and in the end you have a custom recovery and root, righr?
Click to expand...
Click to collapse
Nah man, you flash twrp with odin
here you go
How did u manage to install twrp on sm-g920f ??
Hello, I currently have a G920T that had been working alright for quite some time. The problem is that yesterday while using it normally, it suddenly froze. Thought it was the app, but saw it was the phone itself. Thus, I decide to turn it on again. When I do that, the phone does not continue after the logo and has the LED light white, while blinking on an off. When I manage to enter the Android Recovery menu it gives me the error shown in the title. The phone's rooted and was unlocked, so I could use it with AT&T.
I attempted doing a full reset, upgraded it to Nougat, and I am still stuck. Any help's appreciated in advanced.
Would like to say, when I installed the official Nougat Upgrade for my phone, upon starting, it began installing some things and then preceded to start Deleting. Afterwards, it just froze again. Did I do something wrong?
To get past this issue you have to Root with SuperSU, this will patch the Kernel to disable DM-Verity and will allow you to boot normally.
If you don't want to get rooted then reflash stock firmware via odin. never do OTA updates as i have always say the come "Dirty"
EDIT: Sorry didn't read you were rooted, just re-root again with SuperSU (To get your Kernel patched again) for DM-Verity
Starnel said:
To get past this issue you have to Root with SuperSU, this will patch the Kernel to disable DM-Verity and will allow you to boot normally.
If you don't want to get rooted then reflash stock firmware via odin. never do OTA updates as i have always say the come "Dirty"
EDIT: Sorry didn't read you were rooted, just re-root again with SuperSU (To get your Kernel patched again) for DM-Verity
Click to expand...
Click to collapse
So I use (what I previously used) cf-autoroot again? I ask this, since it seems their website have the recovery for marshmallow version and not for nougat (if I am not able to downgrade to 6).
Junito72 said:
So I use (what I previously used) cf-autoroot again? I ask this, since it seems their website have the recovery for marshmallow version and not for nougat (if I am not able to downgrade to 6).
Click to expand...
Click to collapse
Root with TWRP and superSU zip, i don't recommend CF-AutoRoot
Before flashing the Zip do the following on a Terminal in TWRP
Mount o- bind /dev/urandom /dev/random
Junito72 said:
So I use (what I previously used) cf-autoroot again? I ask this, since it seems their website have the recovery for marshmallow version and not for nougat (if I am not able to downgrade to 6).
Click to expand...
Click to collapse
You can use CF-AutoRoot for 6.0.1 and 7.0.
forumber2 said:
You can use CF-AutoRoot for 6.0.1 and 7.0.
Click to expand...
Click to collapse
When I use CF-Autoroot and attempt to boot it into recovery I get the following message, "recovery is not seandroid enforcing".
So I'd take I try installing a custom ROM first before attempting to start it in recovery?
Junito72 said:
When I use CF-Autoroot and attempt to boot it into recovery I get the following message, "recovery is not seandroid enforcing".
So I'd take I try installing a custom ROM first before attempting to start it in recovery?
Click to expand...
Click to collapse
Oh, that means CF-AutoRoot has not updated to work on 6.0 & 7.0 bootloader for G920T (It is updated and working on 6.0.1 & 7.0 for G920F)
Flash the stock ROM again. After that, flash TWRP and than flash latest SuperSU zip via TWRP.
forumber2 said:
Oh, that means CF-AutoRoot has not updated to work on 6.0 & 7.0 bootloader for G920T (It is updated and working on 6.0.1 & 7.0 for G920F)
Flash the stock ROM again. After that, flash TWRP and than flash latest SuperSU zip via TWRP.
Click to expand...
Click to collapse
I tried doing that, but wouldn't get past the main ROM's screen. I tried a custom ROM then (I think nemesis or such) and lasted longer, but again froze and loops with the white LED light on.
Any suggestions?
Hello guys i successfully unlocked Bootloader now i want to root my Nokia 3 via magisk i don't want twrp i just want boot img for magisk but for that i need root i try many apps for rooting but unsuccessfull i want to root then get boot img then unroot then root from magisk please help me.
mudit johari said:
Hello guys i successfully unlocked Bootloader now i want to root my Nokia 3 via magisk i don't want twrp i just want boot img for magisk but for that i need root i try many apps for rooting but unsuccessfull i want to root then get boot img then unroot then root from magisk please help me.
Click to expand...
Click to collapse
You can boot twrp without flashing and then flash root
https://forum.xda-developers.com/no...w-to-unlock-bootloader-nokia-3-t3699344/page2
Check post #15 by @SkaboXD
But when i flash twrp recovery then i go to recovery and ask for password i cancel it then ask for system modifications I'm confused so i dont give permission to twrp for system modifications then i flash magisk zip then wipe cache of dalvik cache and reboot then its stuck in bootloop
mudit johari said:
But when i flash twrp recovery then i go to recovery and ask for password i cancel it then ask for system modifications I'm confused so i dont give permission to twrp for system modifications then i flash magisk zip then wipe cache of dalvik cache and reboot then its stuck in bootloop
Click to expand...
Click to collapse
You said you wanted root, you were supposed to use the process to get root not flash magisk. I thought you had a method of installing magisk after getting root. I thought you were going to boot twrp recovery, not flash it, since you said you didn't want twrp.
Unfortunately you're going to have to flash stock with OST.
Check this link for more information:
https://forum.xda-developers.com/nokia-3/development/nokia-3-official-firmware-india-uae-t3674320
yeah now i got twrp but only come when boot from fastboot commands and i want magisk how can i get it?
did i have to first flash supersu zip from twrp then install magsik? but i want only magisk not supersu
mudit johari said:
did i have to first flash supersu zip from twrp then install magsik? but i want only magisk not supersu
Click to expand...
Click to collapse
I have never actually used magisk. I thought you had a way of installing/flashing magisk once you had root
I try installing magisk by flashing magisk zip from twrp but got bootloop
mudit johari said:
I try installing magisk by flashing magisk zip from twrp but got bootloop
Click to expand...
Click to collapse
Might I ask: what do you need magisk for?
Also in that recovery I got errors like can't Mount and some kind of encryption error and it say's I have to format data
Need magisk for root and modules as also I want all updates properly installed means i want to in stock recovery
mudit johari said:
Also in that recovery I got errors like can't Mount and some kind of encryption error and it say's I have to format data
Click to expand...
Click to collapse
In my opinion, only use the recovery for flashing stuff, don't mount anything other than sdcard, don't unlock. Maybe when there is a more compatible version of twrp ...
---------- Post added at 02:00 PM ---------- Previous post was at 01:17 PM ----------
mudit johari said:
Need magisk for root and modules as also I want all updates properly installed means i want to in stock recovery
Click to expand...
Click to collapse
Well i don't know about the modules, but when I flashed stock firmware with OST (first time I flashed recovery my phone was stuck in twrp) then flashed root and xposed, I was still able to install updates. The stock firmware I installed was 7.0, but now i'm on the most recent update. So unless there are some specific modules that you need from magisk, I think you can stick with the regular root.
On the other hand you can continue to experiment with magisk, maybe you will find something that we don't know yet and get it working. But remember, if you want to flash anything, don't format with twrp at all, just leave everything readonly and flash
I'm not able to go to recovery by buttons. Only by fastboot command why is that?
What the hell is this i just try to go to recovery by buttons it works but I'm on stock recovery but i flashed twrp then i format data did formatting data did something to recovery? Or is it that i have to use fastboot command to go to twrp recovery? Where the hell is that recovery?
mudit johari said:
What the hell is this i just try to go to recovery by buttons it works but I'm on stock recovery but i flashed twrp then i format data did formatting data did something to recovery? Or is it that i have to use fastboot command to go to twrp recovery? Where the hell is that recovery?
Click to expand...
Click to collapse
I don't know; the process of flashing recovery on HMD's nokias isn't yet fully developed, people have complained about flashing recovery but still not booting into it. Personally I would recommend that you use stock recovery and use fastboot to boot into twrp instead of actually flashing twrp whenever you want to flash anything. That way you are still able to install system update
But for installing magisk every where written that flash magisk zip from twrp but i got bootloop
mudit johari said:
But for installing magisk every where written that flash magisk zip from twrp but i got bootloop
Click to expand...
Click to collapse
Have you flashed stock firmware with OST? Can you boot normally now? If not, do that, then update ti the current android version using OTA. After that boot into twrp (whether you chose to flash twrp or just boot twrp is up to you). Do a backup then try flashing magisk again, maybe it will work this time
Yeah i already flashed stock rom with ost and already update to latest version i think magisk is not supported in Nokia 3
mudit johari said:
Hello guys i successfully unlocked Bootloader now i want to root my Nokia 3 via magisk i don't want twrp i just want boot img for magisk but for that i need root i try many apps for rooting but unsuccessfull i want to root then get boot img then unroot then root from magisk please help me.
Click to expand...
Click to collapse
Hello mate, you can't root nokia 3 with Magisk. Why? Because noone never send boot img to dev! So only option to root it is Chainfire SuperUser 2.79v.
Ok brother but i have a question if i root and then remove some system apps then can I safely install updates?