Spend whole day browsing XDA, still can't get the thing done.
Running stock Nougat 39.2.A.0.361 with unlocked bootloaders and TWRP 3.0.2.0. Downloaded SuperSU 2.79, booted into recovery and flashed SuperSU. No errors, just a success message. However, after rebooting the phone, no sign of SuperSU exists. Flashtool also indicates root access is denied.
When installing custom ROM with SuperSU integrated ( http://forum.xda-developers.com/xperia-xz/development/rom-romaur-v1-0-fast-stable-t3486874 ) root works perfectly. Once custom ROM is installed, SuperSu icon is displayed and root access is OK.
I read that this problem might be because of incompatible kernel? I installed custom kernel (which was attached to RomAur - Stock_Kernel_f8331_fw.327-DRM FIX) before installing custom ROM, but I guess that re-flashing stock ROM later (using Flashtool) restored original kernel as well? If so, what exactly do I need to do in order to have rooted stock Nougat? Just flash some custom kernel (which one exactly?) and try flashing SuperSU again? Really don't want to brick anything.
P.S. Current kernel - 3.18.31-perf-g6af3ae9
if you are on stock nougat,
flash androplus kernel v18 from here:
https://kernel.andro.plus/tone2.html
after that,
flash supersu 2.78.
Thanks, will try. Is there any reason why using SuperSU 2.78 is needed? I see the latest one is 2.79?
manxp85 said:
Is there any reason why using SuperSU 2.78 is needed?
Click to expand...
Click to collapse
No - mine is running fine on 2.79SR1
BTW:
With stock kernel DM_Verity is ON
That detects any modification (e.g. installing SuperSU) in the non-USERDATA partitions via comparing signed checksums and if there is any modification found refuses to boot the device.
Well, my device boots perfectly, but SuperSu doesn't appear in apps list. Anyhow, I'll try with new kernel.
P.S. At the moment, phone runs androplus kernel v18 and custom ROM (Aura v4). After I will flash stock Nougat (using FTF file via Flashtool), will I need to re-flash androplus kernel v18 again?
manxp85 said:
Well, my device boots perfectly, but SuperSu doesn't appear in apps list. Anyhow, I'll try with new kernel.
P.S. At the moment, phone runs androplus kernel v18 and custom ROM (Aura v4). After I will flash stock Nougat (using FTF file via Flashtool), will I need to re-flash androplus kernel v18 again?
Click to expand...
Click to collapse
Welcome to the quirks of RomAur
It lasted less than a day on my device. I find the claims a bit overblown (did not notice them) and there were minor quirks/annoyances.
It needs time I suppose. But without the SONY sources auras76 can't do magic.
On my SAMSUNG G S5 I am on ResurrectionRom. THAT is an improvement over stock for me with LOTS of stuff I use and appreciate.
My Xperia XZ runs on stock ROM with AndroPlus Kernel v18 now. Do not forget to flash the Recovery too.
I am not sure if the SuperSU app is within the zip-file (80% positive it is). If not install it via Appstore.
Replaced RomAur with stock - works so much better. For some reason, root access on RomAur was lost every time after device was encrypted. No such problem with stock ROM.
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.
hello guys
i have a Samsung galaxy S6 g920F running on 6.0.1 with baseband G920FXXU3DPB6.
I have previously rooted my phone using CF-autoroot. Suddenly today when i tried to use superSU, it said "There is no SU binary installed, and superSU cannot install it. This is a problem!. If you have upgraded to Android 5.0, you need to manually re-root".
As i said above that i have rooted after i updated to 6.0.1 and was working till yesterday. i don't know what happen today that it started giving me this error.
I even downloaded latest cf-autoroot from its site and flash it through odin, but still no luck.
Can anyone please help me.
Thanks.
Flash a custom recovery and a kernel and then This
Had the same issue and doing this solved it. hope it helps
Here is how I get the root access back.
1. Copy to phone SuperSU 2.72
2. Flash with Odin arter97 kernel 13.1 (it has TWRP also)
3. Reboot in TWRP and flash SuperSU.
4. Reboot the phone
turulojko said:
Here is how I get the root access back.
1. Copy to phone SuperSU 2.72
2. Flash with Odin arter97 kernel 13.1 (it has TWRP also)
3. Reboot in TWRP and flash SuperSU.
4. Reboot the phone
Click to expand...
Click to collapse
can't we use on stock kernel only as it was before instead of flashing a custom kernel..?
So I've seen a few threads asking a similar thing but since they're quite old, I'd like to ask again.
Quick info about my setup:
running stock ROM, MOB30H
system-less root
system-less Xposed
kernel: ElementalX
TWRP recovery
I was hoping I'll be able to install OTAs with less hassle thanks to up-to-date SuperSU and a special version of Xposed. I indeed have received an OTA today - a small update, I believe 9 MB. When I tried to install it though, TWRP booted up and nothing happened.
Does someone run a similar setup? Have you been able to install an OTA after flashing stock recovery (which I guess is what needs to be done to install OTAs)? Would I have to reflash SuperSU and/or Xposed?
Have now done the following .
1. Cell unroot per SuperSU ( If only a short note, then the app closed )
2. boot into TWRP manually and flashed Magisk - v6
3. next phh 's systemless superuser ) with Super SU magisk version already tried )
4. Mobile launched new
5. After that, it will not boot - When loading only the LED that flashes red and I have to flash a new firmware ...
Anyone know what I'm doing wrong ?
Have a Sony Xperia Z3 D6603
gerooted and SuperSU ( 2.78 )
TWRP 3.0.2-0
Rom : PureX v5 ( Android 6.0.1 - 23.5.A.1.291 )
Locked Blootloader
would be great if he had a solution for me ...
smellz said:
Have now done the following .
1. Cell unroot per SuperSU ( If only a short note, then the app closed )
2. boot into TWRP manually and flashed Magisk - v6
3. next phh 's systemless superuser ) with Super SU magisk version already tried )
4. Mobile launched new
5. After that, it will not boot - When loading only the LED that flashes red and I have to flash a new firmware ...
Anyone know what I'm doing wrong ?
Have a Sony Xperia Z3 D6603
gerooted and SuperSU ( 2.78 )
TWRP 3.0.2-0
Rom : PureX v5 ( Android 6.0.1 - 23.5.A.1.291 )
Locked Blootloader
would be great if he had a solution for me ...
Click to expand...
Click to collapse
I had the same, but maybe the SU can't uninstall. I'm on existenz Rom...
Don't you need an unlocked bootloader?
Sent from my D6633 using Tapatalk
at magisk was nothing about it because that an unlocked bootloader is required.
Yes unlocked Bootloader is required. My Bootloader is unlocked. But can't delete the superuser.apk. That's bad
Exactly the same happened to me. I tried SLiMM 3.1 and PureX V5. After installing Magisk in TWRP device is like dead - only led flashes. If I used Elite kernel, system boots, but the system gets random restarts. Now flashing eXistenZ.
Maybe cause you need to be on stock rom and stock kernel
I use the stock kernel with custom Rom based on the latest official version
Got same issue when using stock kernel on my Xperia Z2, switched to Advanced stock kernel Marshmallow 6.0.1 'cause it has Systemless root support and SElinux permissive and now everything works.
I have try it again, with unroot and install Magisk. Now it works with the advanced stock kernel. But I have some reboots when root is enabled.
Hi All,
I have the same problem, I can see S1 /SOMC Flash Device in Device Manager.
Could someone please post step by step instructions to restore a to Marshmellow?
Will I have to download an Image and a Flashtool?
I have D6603 with TWRP, I am not able to boot to recovery.
Z3- said:
Hi All,
I have the same problem, I can see S1 /SOMC Flash Device in Device Manager.
Could someone please post step by step instructions to restore a to Marshmellow?
Will I have to download an Image and a Flashtool?
I have D6603 with TWRP, I am not able to boot to recovery.
Click to expand...
Click to collapse
Resolved using Emma. I installed the S1 SOMC Flash Device Drivers and I was able to download lollypop.
I will attempt now to reinstall recovery, new rom, and Magisk
What is a stable lollipop ROM? I don't like the marshmallow SD card update. I have a 128gb and I like using it on my PC. I'm looking for a stable ROM that works with Magisk so I can play Pokémon go rooted. Should I just go back to stock lollipop rooted?
ive been rockin MOAR 7.0 for quite some time and i installed Magisk the other day. I flashed something in recovery that caused a bootloop and havent really messed with it since, but it worked before i likely did something wrong LOL
stock 5.0 pogo smg900p thoughts
i7vSa7vi7y said:
What is a stable lollipop ROM? I don't like the marshmallow SD card update. I have a 128gb and I like using it on my PC. I'm looking for a stable ROM that works with Magisk so I can play Pokémon go rooted. Should I just go back to stock lollipop rooted?
Click to expand...
Click to collapse
Stock rooted lp should* work. Rwilco12 has a few stock odexed and deodexed roms and I saw another 5.0 recently that all seem to be positive but I haven't tried.
Got pogo to work on my lgg2 with no network. Using blast gators mostly stock lp from somewhere on xda, uninstal supersu, twrp flashed unsu, used adb shell to remove bin and xbin su files. Flashed magisk v6, bumped my bootloader, flashed phh su, rebooted to system. Installed app side of phh, installed 1.2 magisk manager, installed newest pogo. Unmount root, worked fine when I had internet. Flashed stock 4.4.2, manual update to 4.4.4 and again to 5.0 and then installed blastgators mostly stock rom: worked again. Pdanet crashes on the phone and I still can't get my native Hotspot opened on my smg900p ok4 build, only my phone has net where I live :/ Even used paid fakegps moved to system on expert mode to spoof location on the lgg2. WORKED LIKE A CHARM.
However, on my smg900p ok4 build, last lollipop build, I can't get it to work. The methods were different. Prior to all of this I had flashed a sound mod that I never undid. I Uninstalled cf su from system, reboot, boot to twrp, flashed unsu, TERMINAL EMULATOR TO DELETE BIN AND XBIN SU FILES, LEFT ONE IN BIN, DELETED WITH ES AFTER FIRST POGO ATTEMPT. I then flashed magisk v7 and the phh magisk 7 su, manager 2.0. Didn't like the module mode, so I got rid of manager, flashed magisk Uninstall, flashed magisk v6, phh su for that, installed app side of phh and 1.2 magisk manager. Doesn't authenticate my login.
I want to try what you're talking about but I haven't done it to my s5 yet, it's my working phone and I'm a skid so I'm worried. 1. Does flashing a full tar/zip stock image in Odin replace the bootloader as well? 2. Should I take my SIM and SD card out? 3. Will I need to repatriation my miniSD ext2/4 memory after flashing stock ok4, 0g1, or one other I can't remember? 4. Which 5.0 build should I use
I want to try what you're talking about but I haven't done it to my s5 yet, it's my working phone and I'm a skid so I'm worried. 1. Does flashing a full tar/zip stock image in Odin replace the bootloader as well? 2. Should I take my SIM and SD card out? 3. Will I need to repatriation my miniSD ext2/4 memory after flashing stock ok4, 0g1, or one other I can't remember? 4. Which 5.0 build should I use
i think we covered a good deal of this in your other post, but for those looking still,
1: yes
2: nope, its just fine
3: nope (and its micro, not mini), and id go to OK4
4: MOAR 7.0 with the MOAR extras zip too. Its slick as hell
Hehe one answer in a thread is enough thanks bro