Database Users

lost root after 4.4.2 upgrade, cant re-root

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.

One plus stuck at boot loop

OP2 is stuck at OP logo after the latest OTA. What do I need to do to have it restored it back ..

sguy156 said:
OP2 is stuck at OP logo after the latest OTA. What do I need to do to have it restored it back ..
Click to expand...
Click to collapse
If you have twrp you can flash a full oxygen rom to restore it if you dont you need to Download latest full rom on your pc go in recovery mode connect phone to pc and put the zip in your storage and after that flash it via recovery mode

No it doesn't go into recovery mode it only goes into fastboot mode ..

sguy156 said:
No it doesn't go into recovery mode it only goes into fastboot mode ..
Click to expand...
Click to collapse
Try this zip on your pc while phone connected and on fastboot mode It auto flashes twrp on your phone so you can try to flash oxygen os via it
https://forum.xda-developers.com/devdb/project/?id=13708#downloads

that worked so do I need to flash modified SU 2.79 to root this phone or stay with the TWRP which came with the first aid script

sguy156 said:
that worked so do I need to flash modified SU 2.79 to root this phone or stay with the TWRP which came with the first aid script
Click to expand...
Click to collapse
If you want to root your phone use this file and Flash it via twrp
https://www.androidfilehost.com/?fid=24591000424939898

modified SU is not going to work and have to use seemless SU . Thanks for your help which version of TWRP works without any issues with the newest Oxygen OS..

sguy156 said:
modified SU is not going to work and have to use seemless SU . Thanks for your help which version of TWRP works without any issues with the newest Oxygen OS..
Click to expand...
Click to collapse
Go to Playstore and download twrp app en flash the latest compiatble version

What is needed to re-root OOS 3.5.6 if you did like me and let the OTA update your phone.
TWRP 3.0.2-2 link
OOS3 SuperSu 2.78 link
You can get latest TWRP flashable OOS packages from here.
For future reference.

Oneplus two Rooted stuck on Boot Loop Mode
Hi Guys I need your Help Can anyone Help me as soon as possible
I was Using Resurrection Remix 5.8.5 Nougat 7.1.2 and in Twrp recovery
I was using Resurrection Remix 5.8.5 Nougat 7.1.2 and in Twrp recovery apk a small mistake was done by me
I tick marked as
Allow Flashing to boot partition after that it got stuck in Boot Loop Mode How fix that guys
But Fastboot Mode only Working

Hi it's done with me but not in your way I was realising why it is not boot loading then I came to know maybe TWRP recovery is not installed so I just wanted to flash TWRP recovery in fastboot mode there are so many people trying in different different way to switch on the mobile which got stuck and boot loop mode I found a simple way with all in one tool for Android I am giving you a description or a link below just to flash TWRP recovery and don't forget to select after flash reboot you have to select tick mark it's the best way you can boot load your phone very very simple way to do that
Download Link
https://basketbuild.com/devs/mauronofrio/TOOL

How can I remove Magisk?

I've flashed Magisk, but because I can't get Xposed to work, I'd like to remove Magisk and install SuperSU, but I don't know how. I tried to flash the uninstaller via TWRP and it says everything is fine, but after rebooting it just stays installed. If I try to flash SuperSU anyway I get stuck on boot. I have to flash stock boot.img via TWRP and then Magisk magically reappears. I tried using MiFlash but it refuses to do anything. It says no permission.
One possible solution, I guess, would be to flash stock ROM via TWRP. Can this be done? Any other ideas? Or am I just stuck with Magisk until a new version is available?

Filip013 said:
I've flashed Magisk, but because I can't get Xposed to work, I'd like to remove Magisk and install SuperSU, but I don't know how. I tried to flash the uninstaller via TWRP and it says everything is fine, but after rebooting it just stays installed. If I try to flash SuperSU anyway I get stuck on boot. I have to flash stock boot.img via TWRP and then Magisk magically reappears. I tried using MiFlash but it refuses to do anything. It says no permission.
One possible solution, I guess, would be to flash stock ROM via TWRP. Can this be done? Any other ideas? Or am I just stuck with Magisk until a new version is available?
Click to expand...
Click to collapse
Magisk is pretty much "useless" for now. Because it is based on system-less root, and cannot be updated (because still in testing phase! Newer Xposed module from Magisk requires latest Magisk root binary, which is pretty out of option atm as we can't update to the latest binary). The only solution if you want to have proper root access is:
1. Head over to Xiaomi MIUI website and download the full stock ROM again, and then flash it via fastboot (choose flash_all_except_storage.bat if you want to preserve your data).
2. Once flashed, reboot back to bootloader and unlock it.
3. While still in bootloader flash the correct CF-Auto root boot image for your ROM (contains SuperSU 2.82 binary, https://desktop.firmware.mobi/device:1748)
4. Wait patiently and it will automatically reboot. Install SuperSU from Play Store if you want root management app.
5. If you need Xposed, download the Xposed apk from XDA and then install it normally (not via recovery).
6. ??? Profit
*DO NOT INSTALL permanent TWRP as it will cause your phone stuck in boot loop.

@soralz
Thanks for your help, but no luck. I understand what I'm supposed to do, but I can't get MiFlash to work. When I try to flash stock image I get a "Permission Denied" error. (I have unlocked my bootloader successfully). I tried flashing modified stock image from here But then I couldn't boot. My only solution is to flash stock boot.img via TWRP and I can boot, but I stay stuck with Magisk.
So far, the only options I can think of is to wait for a recovery-flashable ROM, a new software update or a new version of Magisk.

Filip013 said:
@soralz
Thanks for your help, but no luck. I understand what I'm supposed to do, but I can't get MiFlash to work. When I try to flash stock image I get a "Permission Denied" error. (I have unlocked my bootloader successfully). I tried flashing modified stock image from here But then I couldn't boot. My only solution is to flash stock boot.img via TWRP and I can boot, but I stay stuck with Magisk.
So far, the only options I can think of is to wait for a recovery-flashable ROM, a new software update or a new version of Magisk.
Click to expand...
Click to collapse
You couldn't boot, are you using permanent TWRP?
Have you tried download the Full ROM from here and run this (as attachment)?
http://en.miui.com/download-333.html
Btw, place the folder under 1 directory only eg: as attachment. (I tried in multiple directory eg: "D:\Phones\ROM\Stock ROM", it just wouldn't flash)

@soralz
OMG!!! I can't believe it. MiFlash refused to let me flash because I tried to do that from the wrong location. Weird??!!
Good. I’ve managed to follow your instructions and success!! Just a minor note, I couldn't flash the modified boot.img directly via fastboot, it still won't let me. But I just booted TWRP (without flashing) and then flashed it from there. Again, THANK YOU!
BTW, yes, I had flashed permanent TWRP and then unsuccessfully tried to remove it.

Filip013 said:
@soralz
OMG!!! I can't believe it. MiFlash refused to let me flash because I tried to do that from the wrong location. Weird??!!
Good. I’ve managed to follow your instructions and success!! Just a minor note, I couldn't flash the modified boot.img directly via fastboot, it still won't let me. But I just booted TWRP (without flashing) and then flashed it from there. Again, THANK YOU!
BTW, yes, I had flashed permanent TWRP and then unsuccessfully tried to remove it.
Click to expand...
Click to collapse
Oh you manage to fix that? Good for you then. And yes you cannot have permanent TWRP and SuperSU at the same time. The CF-auto root for me I just click root.bat and done. btw side note, you will lose root after each update, besure to check out the new patched boot image. I m sure in the future we will have automated process, don't need to re-root manually after each update

help please

my oneplus 6t has the red ! warning and will not boot. i can get into the stock recovery menu and the fastboot menu. can someone please help me.
i unlocked my bootloader
installedd twrp (which i can only seem to get the stock recovery)
rooted
installed custom rom
and thats what i get when it rebooted.
am i just screwed or is there hope for my phone ?

skaroger867 said:
my oneplus 6t has the red ! warning and will not boot. i can get into the stock recovery menu and the fastboot menu. can someone please help me.
i unlocked my bootloader
installedd twrp (which i can only seem to get the stock recovery)
rooted
installed custom rom
and thats what i get when it rebooted.
am i just screwed or is there hope for my phone ?
Click to expand...
Click to collapse
Go to below link, download and flash latest fastboot ROM.
https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516
If that does not work, use MS tool to recover phone to factory state.

Thanks this worked for me. Was freaking out a little. The scene has really changed since I've been here.

skaroger867 said:
Thanks this worked for me. Was freaking out a little. The scene has really changed since I've been here.
Click to expand...
Click to collapse
As an FYI, in order to root on this phone, assuming you are using Magisk (recommended) you will need to:
Unlock bootloader
Install custom rom (Optional step, but also recommended)
Then flash TWRP zip (This phone, TWRP is part of the boot.img)
Boot the phone
Reboot to recovery
Install GAPPS (OpenGAPPS Stock recommended personally, but any should work)
Then flash Magisk

sandix said:
As an FYI, in order to root on this phone, assuming you are using Magisk (recommended) you will need to:
Unlock bootloader
Install custom rom
Then flash TWRP zip (This phone, TWRP is part of the boot.img)
Boot the phone
Reboot to recovery
Install GAPPS (OpenGAPPS Stock recommended personally, but any should work)
Then flash Magisk
Click to expand...
Click to collapse
Custom rom is not required for root

bladestonez said:
Custom rom is not required for root
Click to expand...
Click to collapse
Correct. I edited my comment to reflect that, however since OP installed a custom rom, I put the step in since I figured he would have asked about it.

sandix said:
As an FYI, in order to root on this phone, assuming you are using Magisk (recommended) you will need to:
Unlock bootloader
Install custom rom (Optional step, but also recommended)
Then flash TWRP zip (This phone, TWRP is part of the boot.img)
Boot the phone
Reboot to recovery
Install GAPPS (OpenGAPPS Stock recommended personally, but any should work)
Then flash Magisk
Click to expand...
Click to collapse
Ok so my phone currently is bootloader unlocked and rooted with magisk. So if I want to install a custom rom I flash in twrp, then flash twrp (while still in twrp), boot phone, reboot to recovery, flash gapps then flash magisk?

read the OP in any custom rom you want to flash, and the dev will have the details on how to flash..

skaroger867 said:
Ok so my phone currently is bootloader unlocked and rooted with magisk. So if I want to install a custom rom I flash in twrp, then flash twrp (while still in twrp), boot phone, reboot to recovery, flash gapps then flash magisk?
Click to expand...
Click to collapse
Essentially. Each custom ROM is differrent, so make sure to read the OP of each custom ROM you try to confirm flashing instructions but that's the **general** flashing method I use. Magisk is overwritten with each flash because Magisk installs to the same partition as the kernel.

rooting shield

So i recently installed developer image 8.0 on my 2017 16gb shield, now i want to install twrp and then flash the kernel to increase cpu and gpu clock and mainly full fan control, i have read that there is no root available but with dev image which is already rooted is it safe to install twrp and the kernel and how do i do it, thank you.

https://forum.xda-developers.com/shield-tv/development/kernel-overclock-kernel-2-22-ghz-t3943079
There is root available, works with both the developer image but also the stock ota.
All the kernel's/modified boots there comes with magisk root.
If you have no idea how to do it, I wouldn't suggest you start doing it.
But there a plenty of guides here on the forum on how to root, flash images and boot into twrp.

I guess my question is as the dev edition is already rooted do i need to install magisk or just flash the kernel which is what i wanted to begin with. So just to twrp temporarily and then flash kernel but not install twrp, i am not entirely sure.

lingarajug said:
I guess my question is as the dev edition is already rooted do i need to install magisk or just flash the kernel which is what i wanted to begin with. So just to twrp temporarily and then flash kernel but not install twrp, i am not entirely sure.
Click to expand...
Click to collapse
You can boot into twrp from fastboot.
"fastboot boot twrp.img"
Magisk is included in the kernel, so if you flash the kernel, magisk will also be installed.

I understood that part, so do i have to flash twrp after flashing kernel with temporary twrp or just leave as it is with stock recovery for it to work.

lingarajug said:
I understood that part, so do i have to flash twrp after flashing kernel with temporary twrp or just leave as it is with stock recovery for it to work.
Click to expand...
Click to collapse
I would suggest just leaving the stock recovery there.
I tried flashing twrp and ended with a bootloop, so now I just boot into twrp instead.