Is it actually possible? I tried today and soft bricked, had to flash back to stock and go through all the hub-bub to get back to root.
I actually just got as far as root on 4.4, flashed the OC4 Kernel, wiped cache, and then after about 20 mins of waiting android came back up.
I reinstalled flashfire somehow (EVERY SINGLE APP crashed every few seconds) and flashed my flashfire nandroid backup. It allowed me to boot android once more; this time system UI constantly crashed.
This time I reflashed the actual ROM and am now back into 5.0 FreedomROM with OC4 (I previously had OA8)..
Before I touch anything else, is Xposed possible? I really don't want to go through this all again without having a better idea.
The custom Galaxy Xposed zip here says 5.1.1. Is this a total pre-requisite?
Lutero said:
Is it actually possible? I tried today and soft bricked, had to flash back to stock and go through all the hub-bub to get back to root.
I actually just got as far as root on 4.4, flashed the OC4 Kernel, wiped cache, and then after about 20 mins of waiting android came back up.
I reinstalled flashfire somehow (EVERY SINGLE APP crashed every few seconds) and flashed my flashfire nandroid backup. It allowed me to boot android once more; this time system UI constantly crashed.
This time I reflashed the actual ROM and am now back into 5.0 FreedomROM with OC4 (I previously had OA8)..
Before I touch anything else, is Xposed possible? I really don't want to go through this all again without having a better idea.
The custom Galaxy Xposed zip here says 5.1.1. Is this a total pre-requisite?
Click to expand...
Click to collapse
i dont think its compatible with touchwiz
Related
I managed to upgrade my Nexus 7 2013 LTE from KitKat to Marshmallow using factory images yesterday and took some notes. All apps and settings kept (or at least I haven't noticed any issues other than no Xposed) and rooted. I figured someone might find this useful.
So, short version: upgrading directly from 4.4.4 to 6.0 with factory images didn't work without wiping data and where's the fun in that? So I took a longer route and went 4.4.4->5.02->5.1.1->6.0.0. It's possible I could've gone from 5.0.2 to 6.0 or 4.4.4 to 5.1.1 directly but I'm not going to try and see if that's the case. Enjoying Marshmallow now.
Basically, I did the same thing for all three update steps:
Unpacked factory image, rebooted to bootloader, flashed bootloader, radio, system.img, boot.img, cache.img. I rebooted to bootloader after flashing bootloader and again after flashing radio, same thing the flashall.bat does. Don't know if it matters.
Booted to TWRP recovery, flashed supersu zip and renamed /system/recovery-from-boot.p to keep TWRP.
Booted system and grew some gray hairs while the boot animation went on and on until it finally got to the long "optimizing apps" phase.
For 6.0 I flashed a modified kernel and supersu beta 2.52.
So, enjoying Marshmallow now. No issues so far. Root cloak detectors seem to be becoming a plague and I've only used an Xposed module for that.
Hi All,
I had obtained root via CF-Autoroot and was using it with xposed for the last few weeks without issues. I took the lunge and tried to install phh super su, magisk systemless root. so the nightmare begins for me and i'm hoping it's an easy fix!
My system is still encrypted (I believe because TWRP can't see the system) SD card is fine. I've wiped my device a few times already and am hoping I don't need to wipe it again(prior to this setup).... So currently it's running fine without root access (How I hate android without root!!!)
- I've tried flashing Supersu zip in TWRP and it's failed - I believe it's not supported yet for encrypted devices.
-I've tried using the original CF-Autoroot method I used initially.
Both methods, it boots up straight away (no optimising apps) and after installing supersu app from playstore, it says no binaries found.
What are some ways I can inject root without wiping my device?
Please help me! Thankyou!
Maybe go back to the start and flash original FW through Odin and start from scratch, so you have a fresh phone to work with.
dwarfer66 said:
Maybe go back to the start and flash original FW through Odin and start from scratch, so you have a fresh phone to work with.
Click to expand...
Click to collapse
That's my plan when I get home tonight. I want to flash the original firmware file my phone started with (I'm assuming it won't delete anything?) and then run through the root steps again.. if it doesn't work, I'll wipe my phone and make sure I get rid of encryption this time..
kevinwu128 said:
That's my plan when I get home tonight. I want to flash the original firmware file my phone started with (I'm assuming it won't delete anything?) and then run through the root steps again.. if it doesn't work, I'll wipe my phone and make sure I get rid of encryption this time..
Click to expand...
Click to collapse
I think you will only lose stuff if you do a system reset after installing the original FW.
I only have had to do that on my tab S not my Edge after coming from a custom rom as I got slow down.
Resolved: flashed original rom and obtained root with cf-autoroot.
If someone has detailed instructions for magisk systemless root and xposed, it'd be much appreciated.. i want to have the option to use android pay or play pokemon go if i wanted. Thankyou
Just installed Nougat stock ROM for my S7 Edge with ODIN, and trying to root.
I installed TWRP latest version 3.01 and immediately after installed supersu 2.79 SR3 from TWRP.
At first I could not boot the phone because it kept saying I used the wrong PIN code for boot. I reflashed stock rom and was able to boot again (same PIN) - disabled PIN on boot, and reflashed TWRP and supersu, but it keeps hanging at the Samsung Logo.
Flashing stock rom solves it, but I still want to root it..
What am I doing wrong?
currently there is no reliable root for nouget roms. It is being worked on.
Cosmic Blue said:
currently there is no reliable root for nouget roms. It is being worked on.
Click to expand...
Click to collapse
Thanks for replying.
In this case - even if the goal is to root - it seems the problem is with TWRP.. Even if I do not root, but just install TWRP, the neverending bootlogo shows up..
Nougat OS has been changed that all the old rooting and twrp need to be updated.
It will be a while till developers can modify the os to allow changes.
Have posted the same question in the TWRP S7 thread that I did not see before posting this one - sorry
I've spent the past few days trying to install the new Nougat update on my phone, and I finally managed to do it. I heard Magisk works for Nougat so I decided to use it as my root so i could back up my partitions and whatnot for the next update. I download the Magisk installer using the app, use fastboot to boot into TWRP, and flash the installer. All seemingly goes well, but when I reboot, nothing happens. I can access bootloader, I can access the stock recovery that's still loaded, but it will not start up, and any attempt to start it while the phone is plugged in leaves it in a black screen with the LED next to the fingerprint sensor consistently flashing. I'm no expert, but this doesn't seem good. Is it bricked? Is there an easy fix? So far I've tried using the recovery to wipe the cache and used TWRP to do a full factory reset, neither of which did anything. My Moto G4 Plus is an XT1644, and my model number was mpj24.139-64, which I'd assume means it is now npj24.139-64, but I have no way to check.
I feel like my best bet here is for someone else to extract their system, logo, boot, and all those partitions and I can just flash those in, but I honestly have no idea. This is my only phone by the way, so help would be muchly appreciated.
You need a custom Kernel first thing after re-flashing the stock, recommend ElementalX. Only after that you can root (I prefer the latest beta SuperSU, in systemless mode).
The stock Nougat is locked up pretty good.
Solved
No worries, managed to safely flash the stock rom I had for the previous version and re-update. Seems to work fine now.
Hey people
I have a Samsung sm-j320f 2016, OS android 5.1.1 and im trying to root it.
I flashed trwp recovery mode uaing odin and i tried several times rooting the phone with superSU or magisk. Cut to the chase, i rooted my phone...after hours it powered itself off and kept bootlooping
I flashed the firmware using oding and its working again now
I tried again rooting it with magisk...same happened but this time o restored it.
I found out it was because of stock rom and touchwiz ui that causes bootlooping
I really want to root my phone and i dont know how should i prevent bootloop
Can you help me?
AminNadery said:
Hey people
I have a Samsung sm-j320f 2016, OS android 5.1.1 and im trying to root it.
I flashed trwp recovery mode uaing odin and i tried several times rooting the phone with superSU or magisk. Cut to the chase, i rooted my phone...after hours it powered itself off and kept bootlooping
I flashed the firmware using oding and its working again now
I tried again rooting it with magisk...same happened but this time o restored it.
I found out it was because of stock rom and touchwiz ui that causes bootlooping
I really want to root my phone and i dont know how should i prevent bootloop
Can you help me?
Click to expand...
Click to collapse
first thing, go back to the stock of your device, activate OEM unlock, download the latest version of twrp and install by DOWNLOAD mode, rom stock only supports SuperSu, if you want to use magisk, just use a custom rom (I recommend Viper )
G0K4LT3 said:
first thing, go back to the stock of your device, activate OEM unlock, download the latest version of twrp and install by DOWNLOAD mode, rom stock only supports SuperSu, if you want to use magisk, just use a custom rom (I recommend Viper )
Click to expand...
Click to collapse
I realizd i shouldn't use 2 root apps.
Im using magisk now
Without any problems
Thanks tho