Database Info

[Q] Lost ROOT after manually updating last OTA via TWRP

As title says... I had unlocked bootloader and flashed TWRP then SuperSU and ROOT was working fine.
- Last OTA I got which was yesterday (as only just got the phone) was XNPH33R.
- I used TWRP to install the update which went fine except I lost ROOT access.
- Went back to TWRP and reinstalled SuperSU which shows as installed on my phone - however no apps that require ROOT can get ROOT access and RootChecker shows that the phone is not rooted.
- Rebooted to System / Tried to Fix Permissions / Tried to reinstall newest SuperSU - nothing works
Does anyone have any suggestions as to how I can regain ROOT or is not possible on XNPH33R?
Further issues I have now got no ADB access in Fastboot no matter what drivers I install... don't know if this is all linked!!!
Jesus christ
Any help appreciated.
Thanks in advance

Too much work if you do a full wipe and re rooted ?
Also try to put zip file with airdroid and flash it in download mode

So I've found out that although adb was telling me that it couldn't recognise any devices in fastboot mode - all the actual commands from the OnePlus One toolbox were actually getting through as I relocked my Bootloader to see what would happen and then tried to Flash Recovery and it told me Bootloader was locked - so that confirmed adb commands were working.
To solve my ROOT problem I did the following:
1) Flashed CM XNPH22R
2) Installed all OTA updates
3) Unlocked Bootloader
4) Installed TWRP - then chose REBOOT TO SYSTEM (this told me I wasn't rooted and then followed prompts)
5) I chose to install SuperSU from Play Store
6) Opened SuperSU and updated binaries
7) Turned off Update CM Recovery in Developer Options
8) Rebooted and installed and ran Root Checker....
9) Success!

Remove the respect CM root settings from the SU settings menu and your root will come back i had the same problem until i found this out.

Cholerabob said:
Remove the respect CM root settings from the SU settings menu and your root will come back i had the same problem until i found this out.
Click to expand...
Click to collapse
Thanks - wish you told me that earlier!!
I assumed it should be on because it's CM right!!! Doh!
Oh well - this might help someone else...

[Q] Not able to root my Nexus 5

Device : Nexus 5
Premise: Not able to root using SuperSU
OS: 5.0 build: LRX21O
1. I flashed my Nexus 5 with the factory image of the above build.
2. Boot loader unlocked
3. Custom recovery installed(CWM)
4. Tried flashing SuperSU 2.16
-While rebooting, I got the error "Root privileges might be lost"
- Clicked fix
5. But, rooting didn't come through.
6. SuperSU says "There are no binaries and it can't install"
Any fixes? Please help. This is getting on my nerves.
PS : I don't wanna use CFAR coz it will erase everything even though the boot loader is unlocked. I don't want to lose any data.

Try this
this software is Vroot and do root even on toasters XD
kingo install root to manage root. and also makes root on any device
go to google and type Vroot. and a program with a click does it all installs drivers

I think failed rooting on N5 causes issues

I flashed, unlocked and tried to root my phone with this guide:
http: //wccftech.com/flash-and-root-nexus-5-on-android-6-0-1-mmb29k/
Why I think rooting failed is that that I followed the guide through to the last step and after the last step clockwork mod said that rooting failed and I had two options to root or go back (but judging by the system messages the SU zip was installed). I think here I made the mistake to choose rooting "again". I read later in another guide but concerning twrp that this situation where the SU zip gets installed but the message says Installation failed a bug is and that I should not do what I did.
Anyway root was not achieved as I checked with the root checker app. The recovery mode now looks a bit strange. And I cannot install the current patch for marshmallow because it is an unsigned zip.
Where do I go from here reflash the recovery? And install SU again

Flash twrp, then flash the latest supersu from twrp.

will this wipe my device?

No, it should not wipe the device.
If there is data on your phone that needs to be saved, you could try flashing TWRP, boot to TWRP, mount the data partition, and copy the required data to a computer. Once copied, flash supersu and try to boot.

[Completed] Help with reinstalling bootloader

Hi.
I am relatively experienced user who has rooted and installed custom roms on samsung galaxy and HTC desire phones before.
I have now attempted to root my alcatel onetouch pixi 4 (4034X) using instructions from this thread :- https://forum.xda-developers.com/android/general/alcatel-one-touch-pixi-4-t3376597
I got as far as flashing twrp recovery and now the phone is stuck in constant reboot. I downloaded alcatels mobile upgrade tool in hopes of reflashing the stock rom but it seems to be looking for a later rom than the one I have installed and keeps telling me I have the lastest and so wont flash.
So can I recover from this at all or have I just bricked my phone? Is there a way to FORCE the mobile upgrade tool to reflash the current rom rather than looking for an upgrade?
It seems that everything except the bootloader is intact so is there another tool I can use to restore the bootloader?
Any help would be greatly appreciated.

Looks like I managed to unbrick using a combination of SP Flash tool and an SPFT rom for the 4034X I found on the internet. will now try reflashing a different recovery tool.

O.K. so I think what is happening is an issue when unlocking the bootloader and not when flashing recovery.
This is what I did:-
1. Enabled developer mode.
2. Turned on usb debugging and unlocked bootloader oem
3. Rebooted phone, plugged in cable and accepted connection authorisation.
4. From windows typed adb reboot bootloader. Went into to fastboot.
5. Typed fastboot oem unlock, Pressed volume up on phone.
At this point I was put back in fastboot but none of the buttons worked and the phone looked like it had frozen. Was It wiping data at this point? There was no indication that it was doing anything.
I removed the battery and reinserted but when I restarted I got the same boot loop problem. Had to restore stock firmware AGAIN.
Am I doing something wrong?

Update: I managed to install caliv touch recovery without unlocking the bootloader by using the same sp flash tool I used to restore the stock rom. However, I cant install root. The recovery will only let me sideload and I could only find the chainfire SU binaries for sideload (SuperSU 2.78-SR1 and superSU 2.46). Both of these seem to flash ok using adb sideload with ctr recovery but the phone hangs at the boot logo. I also had superuser-r197 (ph's sueruser) but that wouldn't sideload.
So I now have a custom recovery but still can't root
Has anyone succesfully rooted the 4034X (UK)? If so, how?

nyarlathotep_uk said:
Update: I managed to install caliv touch recovery without unlocking the bootloader by using the same sp flash tool I used to restore the stock rom. However, I cant install root. The recovery will only let me sideload and I could only find the chainfire SU binaries for sideload (SuperSU 2.78-SR1 and superSU 2.46). Both of these seem to flash ok using adb sideload with ctr recovery but the phone hangs at the boot logo. I also had superuser-r197 (ph's sueruser) but that wouldn't sideload.
So I now have a custom recovery but still can't root
Has anyone succesfully rooted the 4034X (UK)? If so, how?
Click to expand...
Click to collapse
Hi & welcome to xda-assist,
you can try to force the installation of supersu systemless by this step, chances are good that this will make it boot properly.
boot into twrp >go to the terminal > and type:
echo SYSTEMLESS=false>>/data/.supersu
Don't know if the recovery you use has this terminal option but it's very likely.
You can do additional a Google search on "force SuperSU systemless" to get more information / background information..
Good luck
Sent from my OnePlus 2 using XDA Labs

Thanks for your reply Sam.
I only read that after I had found a copy of a CM13 Rom that worked with The 4034X. I basically flashed superSU first then did a wipe, then installed the custom rom and google apps nano before downloading the supersu apk from google play and reinstalling. Now I have a rooted phone with a custom rom and am somewhat happier. The reason I wanted to root was to remove the bloatware that was taking up 1.5 GB of my already measly 2GB internal memory and this new ROM only takes up .5 GB.
I still have some pain. For example many of the Rom Toolbox Pro functions don't work and I think its because the system image seems protected and refuses to mount rw no matter what I do. Even issuing a remount command using the device name from cat /proc/mounts tells me the block device is read only. I also seem to be unable to verify if I have busybox or install it due to the same reason.
It also took me some time to work out that the boot animations weren't stored in /data/local or /system/media but to /data/system/theme.
This used to be so much easier in the days of ice cream sandwich and lollipop. Ah well!

Update:- Managed to flash busybox 1.26 using a flashable zip via adb sideload in Caliv Recovery (Caliv can't see my adopted storage for some reason).
I'm happy now! Would still like to have a rw system so I can remove some system apps I don't use but its no biggie.

D6633 Boot loop after SU update

Dear folks,
I have a rooted D6633 with locked bootloader , TWRP and super user from
Z3-lockeddualrecovery2.8.26-RELEASE
After being prompted by the super user app to follow the update of super user, I choosed "normal" , and then I was asked to by the installer to do a "reboot". So hit the button to do that.
Unfortunately, I am stucked in a boot loop. I am on 5.1.1.
What can I do? I have an old backup from May 1st, but I would like to keep my data after that date as much as possible. Please help.
Thanks.

When this happened to me, I've reflashed my ROM to get it working again. If you have recent TWRP backup, you might as well to use that.
Currently, I run cracked SuperSU 2.82 and have disabled automatic SuperSU update.