Well I flashed 4.4 successfully using TWRP. But some how or another I've unrooted myself. I've tried everything that I can (aside from messing with ADB and the SDK directly) and I can't figure out how to re-root the device.
Help!
Install TWRP again if it's gone and then flash SuperSU
tom1807 said:
Install TWRP again if it's gone and then flash SuperSU
Click to expand...
Click to collapse
No dice. Says I'm unrooted.
Managed to get it working. Koush's Superuser app doesn't work for some reason. SuperSU does. I just hope they fixed the glitches with it causing unnecessary battery drain.
What were your steps?
You can obtain the last flashable zip file from here
Ok, you edited your post, so my one is obsolete
hello guys,
I had 4.4.1 rom+kernel stock, rooted and custom recovery, after the OTA to 4.4.2 lost my root and recovery.
tried re-root with wug's but it gets stuck on "pushing root file to you device".
got superSU application but cant remove it because its system application.
Is there a way to root it?
thanks.
Same here except i had cwm touch latest. It seems i have lost my recovery too. If i try and boot into the recovery menu i get the open hood android with a red triangle.
No custom kernel only custom recovery.
Sent from my Nexus 7 (2012)
I lost my custom recovery too. But I just reflashed it (adb reboot bootloader, then flashed a downloaded custom recovery via fastboot), and then reflashed SuperSU as well.
Sent from my Nexus 4 using XDA Premium 4 mobile app
I'm having the same problem. Root undone, and recovery went back to stock. Custom recovery doesn't stick after reboot.
santoshgs said:
I'm having the same problem. Root undone, and recovery went back to stock. Custom recovery doesn't stick after reboot.
Click to expand...
Click to collapse
I was in the same situation after my OTA of 4.4.2
I had nexus root toolkit, tried to put in twrp with it failed.
Then updated to the latest nrt and then I could flash the latest twrp, havent tried cwm.
and eventually got the root back using nrt
7thAkash said:
I was in the same situation after my OTA of 4.4.2
I had nexus root toolkit, tried to put in twrp with it failed.
Then updated to the latest nrt and then I could flash the latest twrp, havent tried cwm.
and eventually got the root back using nrt
Click to expand...
Click to collapse
Ah, glad that it worked! ^_^
santoshgs said:
I'm having the same problem. Root undone, and recovery went back to stock. Custom recovery doesn't stick after reboot.
Click to expand...
Click to collapse
Found the solution to my problem. Used CF Auto Root instead of manually flashing SuperSU again. Cheers guys!
http://download.chainfire.eu/363/CF...merhead-hammerhead-nexus5.zip?retrieve_file=1
Same thing happened to me. just use fastboot to flash CWM, then before you reboot go into the recovery. then next time you reboot it will still be there. For some reason if I flash the recovery then reboot without entering recovery it will loose the recovery.
Once you have the recovery back, just flash the SuperSU binary through CWM.
Also, IMHO, dont use toolkits... you dont really know whats going on when you use those. Learn to use ADB & fastboot. They are really simple to use and you will be better able to help yourself when you have problems in the future.
Has anyone tried simply flashing a custom recovery, then using the recovery to flash SuperSU as a way to gain root access?
Or do i need to find a rootable kernel somewhere?? I google this issue alot recently, and just want to find out if someone has done this successfully. Odin is killing me because no matter what i DO try to flash using it, fails... other than the Stock Android 5.0.1 firmware. Am i missing something, or can someone give me directions to the simplest instructions possible to gain root on it. I know this has been asked alot, but most solutions i have found have only been for other carriers, and lower builds of the firmware. I would be willing to downgrade to KitKat if necessary... but also that seems impossible because the bootloader blocks downgrades... Please Help
Worked Like A Charm
So its done!! Simple and easy... Three steps! (make sure to copy the newest SuperSU file to your sdcard first)
***Boot into ODIN Download Mode***
1. Using ODIN flash TWRP 2.8.4.0 (dont let it reboot on its own afterwards!... YOU MUST BOOT INTO RECOVERY ON YOUR OWN THE FIRST TIME TO LET TWRP PATCH THE ROM)
2. While in TWRP recovery, then install SuperSU zip file from your SDcard
3. Select reset and perform the "Factory Reset" option.
!!! Success... !!! you now have a rooted Sprint S4 with the OF1 build of lollipop...
*********Credit to "bilgerryan"
For the proper process to use!
:laugh:
I own the 6GB Ram version of the phone and wants to root it so as to use Titanium backup to restore all the contents of my previous phone.
But the Problem is that we are still going to get some big OTA updates regarding camera and maybe more bug fixes.
I know the general procedure for rooting the device i.e. first unlock the bootloader then install a custom recovery then root.
I just wanted to ask if I just install back the stock recovery after rooting the device then will I get the Ota updates?
And I am sorry if any similar question has already been asked, I searched but didn't find any. Thanks
nitish.4you said:
I just wanted to ask if I just install back the stock recovery after rooting the device then will I get the Ota updates?
Click to expand...
Click to collapse
im using twrp and magisk for root. i still get OTA updates. but only the full updates, the 1,5 gb size
after that i need to flash twrp again and then install magisk again too.
but no data lost or anything so if you can live with that, its no biggy.
Hastaloego said:
im using twrp and magisk for root. i still get OTA updates. but only the full updates, the 1,5 gb size
after that i need to flash twrp again and then install magisk again too.
but no data lost or anything so if you can live with that, its no biggy.
Click to expand...
Click to collapse
Can you throw some more light on this.I just want the latest updates. Download size etc doesn't matter.
Can you tell me the procedure what you do to retain rooted access and still get latest updates.? Thanks
nitish.4you said:
Can you throw some more light on this.I just want the latest updates. Download size etc doesn't matter.
Can you tell me the procedure what you do to retain rooted access and still get latest updates.? Thanks
Click to expand...
Click to collapse
i assume you know how to get root ? unlock bootloader, flash twrp, install magisk or supersu ?
well from there its just the same.
getting ota updates see attachment.
after the update you are back to stock recovery without data lost.
so just flash twrp again and install root again, thats all.
nitish.4you said:
Can you throw some more light on this.I just want the latest updates. Download size etc doesn't matter.
Can you tell me the procedure what you do to retain rooted access and still get latest updates.? Thanks
Click to expand...
Click to collapse
1. Unlock Bootloader and Flash TWRP
2. Flash and Download APK Magisk 13.3 (Root + Pass SafetyNet)
3. If there is a new update go to OnePlus 5 Downloads
4. Boot into TWRP and Flash the new update.
5. Everytime you flash a new update you must also flash Magisk Root.
6. Done
Should we flash twrp recovery and root zip right away after flashing full ota package??
PrakashGD said:
Should we flash twrp recovery and root zip right away after flashing full ota package??
Click to expand...
Click to collapse
You don't have to flash twrp recovery again.
You can flash a root zip right after flashing the full OTA package
Hi guys, I have successfully rooted using temporary TWRP + modded magisk method, but now I gain root and checked via Root checker. But the problem is most of the root functions don't work as /system is read-only. Any idea?
Ya i have an idea.. Happened to me as well. I tried almoat everything but system won't be accessible anywhere.. I followed the same tutorial and installed magisk 13.4.
The only solution i could find was flash the latest factory image, and root again using supersu. I used the AIO tool by ghpranav and have got my phone rooted with xposed working without any issues.
zazzy24 said:
Ya i have an idea.. Happened to me as well. I tried almoat everything but system won't be accessible anywhere.. I followed the same tutorial and installed magisk 13.4.
The only solution i could find was flash the latest factory image, and root again using supersu. I used the AIO tool by ghpranav and have got my phone rooted with xposed working without any issues.
Click to expand...
Click to collapse
I also fixed the issue. I flash the modified boot image and I am now gaining proper root access + Xposed. Get it working using Super SU, idk why Magisk keep failing thou. Was wanted to give Magisk a try, but it doesn't work properly on our device.
Cool:good:
Xposed isn't working with magisk? I was planning to install it
amithiel said:
Xposed isn't working with magisk? I was planning to install it
Click to expand...
Click to collapse
Only with SuperSU as I know.
Sent from my Mi A1 using Tapatalk
Guys, this is Magisk from Pixel. You can't expect that it is working. I wrote to MagiskDevs already, they are working on a own Version for Mi A1. Use for that time normal SuperSU (Xposed works normally )
how to??
soralz said:
I also fixed the issue. I flash the modified boot image and I am now gaining proper root access + Xposed. Get it working using Super SU, idk why Magisk keep failing thou. Was wanted to give Magisk a try, but it doesn't work properly on our device.
Click to expand...
Click to collapse
Hay how do you Fix the Read only Issue? can you please share the Modified Boot image and process for same, thanks
maxsan20 said:
Hay how do you Fix the Read only Issue? can you please share the Modified Boot image and process for same, thanks
Click to expand...
Click to collapse
https://desktop.firmware.mobi/device:1748
Just root with replacing the boot image then you are good to go.
soralz said:
https://desktop.firmware.mobi/device:1748
Just root with replacing the boot image then you are good to go.
Click to expand...
Click to collapse
Hi,
I have TWRP installed and unrooted, what I need to do please?
We7dy said:
Hi,
I have TWRP installed and unrooted, what I need to do please?
Click to expand...
Click to collapse
You need flash back stock boot image first, due to some limitations you can't have TWRP and SuperSU root at the same time. If you don't have the stock boot image. I suggest download the ROM from MIUI and then flash it. You can choose "flash_all_except_storage" option, this will keep your data.
http://en.miui.com/download-333.html
After flashing. Reboot back to fastboot and then:
Code:
fastboot oem unlock
After that just run root.bat from the cf-auto root folder you downloaded and wait for it to automatically reboot your phone. You should have root now, if you wish you can download SuperSU from the store.
soralz said:
You need flash back stock boot image first, due to some limitations you can't have TWRP and SuperSU root at the same time. If you don't have the stock boot image. I suggest download the ROM from MIUI and then flash it. You can choose "flash_all_except_storage" option, this will keep your data.
http://en.miui.com/download-333.html
After flashing. Reboot back to fastboot and then:
After that just run root.bat from the cf-auto root folder you downloaded and wait for it to automatically reboot your phone. You should have root now, if you wish you can download SuperSU from the store.
Click to expand...
Click to collapse
Ok, thanks. It's not possible to do that via TWRP? I don't have PC. Currently my bootloader is unlocked, I have TWRP and I'm unrooted.
We7dy said:
Ok, thanks. It's not possible to do that via TWRP? I don't have PC. Currently my bootloader is unlocked, I have TWRP and I'm unrooted.
Click to expand...
Click to collapse
I actually tried before, and I tell you the results:
Option 1 TWRP installed + Rooted with Magisk
= Pretty much useless as /system is read-only. Every root app doesn't function, unless it is system-less. But system-less modules nearly all doesn't work as the Magisk version too old. And this method won't trip safetynet
Option 2 no TWRP + Rooted with SuperSU (cf-root method) -- Currently using this state
= Got proper root access, Xposed works but will trip safetynet
Option 3 TWRP installed + Rooted with SuperSU (cf-root method)
= Don't try this, will cause your phone stuck in boot loop
soralz said:
I actually tried before, and I tell you the results:
Option 1 TWRP installed + Rooted with Magisk
= Pretty much useless as /system is read-only. Every root app doesn't function, unless it is system-less. But system-less modules nearly all doesn't work as the Magisk version too old. And this method won't trip safetynet
Option 2 no TWRP + Rooted with SuperSU (cf-root method) -- Currently using this state
= Got proper root access, Xposed works but will trip safetynet
Option 3 TWRP installed + Rooted with SuperSU (cf-root method)
= Don't try this, will cause your phone stuck in boot loop
Click to expand...
Click to collapse
So not possible via TWRP? Get root access and remove TWRP? I just need that... The root.
We7dy said:
So not possible via TWRP? Get root access and remove TWRP? I just need that... The root.
Click to expand...
Click to collapse
The best bet and possible trouble free is to first download the stock ROM from MIUI, reflash it and then root.
soralz said:
The best bet and possible trouble free is to first download the stock ROM from MIUI, reflash it and then root.
Click to expand...
Click to collapse
:/ Can't root with TWRP without system read only...
We7dy said:
:/ Can't root with TWRP without system read only...
Click to expand...
Click to collapse
It's possible to root without CF-Auto-Root? Why can't flash SuperSu directly with TWRP?
We7dy said:
It's possible to root without CF-Auto-Root? Why can't flash SuperSu directly with TWRP?
Click to expand...
Click to collapse
No, it will cause your phone stuck it boot loop if you try to flash the SuperSU zip directly from the official ChainFire site. I think probably is the AB partitioning problem or some sort (unsure). As I said you need to run CF-Auto root to get proper root access, otherwise flashing Magisk through TWRP will makes most of the root apps does not work properly unless it also uses system-less root function.
soralz said:
No, it will cause your phone stuck it boot loop if you try to flash the SuperSU zip directly from the official ChainFire site. I think probably is the AB partitioning problem or some sort (unsure). As I said you need to run CF-Auto root to get proper root access, otherwise flashing Magisk through TWRP will makes most of the root apps does not work properly unless it also uses system-less root function.
Click to expand...
Click to collapse
Ok I have TWRP installed can I use directly CF auto root?
We7dy said:
Ok I have TWRP installed can I use directly CF auto root?
Click to expand...
Click to collapse
No if you want proper root with CF-auto root you must not have TWRP installed. You either choose TWRP + Magisk (non-working root) or no TWRP but with SuperSU (working root, Xposed works too).
Follow the instruction here to get you on track:
https://forum.xda-developers.com/showpost.php?p=74326169&postcount=2