Database Info

can't get root. missing a step?

bought sunshine, have s-off.
read a bunch.
took forever to get adb drivers working on windows. got them working.
followed guide on twrp.me site to try and flash twrp on phone. i put the .img file in c:\adb folder which has adb and fastboot files. i can get the cmd line inputs to boot phone into bootloader. here's the cmd results.
C:\adb>adb reboot bootloader
C:\adb>fastboot flash recovery twrp.img
target reported max download size of 1826418688 bytes
sending 'recovery' (20046 KB)...
OKAY [ 2.152s]
writing 'recovery'...
OKAY [ 0.725s]
finished. total time: 2.878s
C:\adb>fastboot reboot
rebooting...
finished. total time: 0.013s
the phone reboots and then i try titaniumbackup but it says i don't have root still.
what step(s) did i miss?

You need to reboot to recovery and flash SuperSU
Sent from my HTC6545LVW using Tapatalk

You got S-OFF, which allows you to modify the secured partitions; system, boot, recovery and the radios. With S-ON these are locked and any modifications will not be saved. SuperSU will manage and grant root access. Technically you can root an S-ON device, but it'll only ever be a "temporary" root, because as I mentioned before, changes won't be saved.

Thanks for the quite responses in helping a noob
ok, got recovery boot figured out. after i did "fastboot reboot" from command line the phone restarted normally and i read somewhere that if it does that it wipes out twrp and i have to start over. apparently not true.
got into recovery and twrp is there.
want to confirm the next steps....
1) flash supersu while in recovery(twrp)
2) boot and should have root now
3) backup with titaniumbackup
4a) delete verizon junk and have access to more options with tasker and other apps since i have root
-or-
4b) install cyanogenmod through twrp.

You're correct. Although step 4 could be dozens of different options. The world is your oyster!

How to root my Moto G 3 with Android version 6.0.1

I have seen threads but nothing related to the 6.0.1 version. Please do help

jerry94 said:
I have seen threads but nothing related to the 6.0.1 version. Please do help
Click to expand...
Click to collapse
6.0 or 6.0.1... no difference, must do manual systemless install

acejavelin said:
6.0 or 6.0.1... no difference, must do manual systemless install
Click to expand...
Click to collapse
how to do that?

Already answered google it
Sent from my MotoG3 using Tapatalk

flash supersu zip in twrp.. to simple

HelpMeruth said:
flash supersu zip in twrp.. to simple
Click to expand...
Click to collapse
This doesn't work... if you just flash the latest SuperSU in TWRP, a 3rd/4th Gen Moto device will fail to boot because SuperSU's install script does not recognize that this device must have a systemless install. You must start TWRP and before flashing go to Advanced - Terminal and enter "echo SYSTEMLESS=true>>/data/.supersu" so the SuperSU install script will parse the file and know it has to do a systemless install.

jerry94 said:
I have seen threads but nothing related to the 6.0.1 version. Please do help
Click to expand...
Click to collapse
Check this tutorial
forum.xda-developers.com/2015-moto-g/general/guide-install-twrp-root-xposed-t3294588
Or this one(better)
forum.xda-developers.com/2015-moto-g/general/root-how-to-root-moto-g-2015-android-t3320113e

Nikos dima said:
Check this tutorial
forum.xda-developers.com/2015-moto-g/general/guide-install-twrp-root-xposed-t3294588
Or this one(better)
forum.xda-developers.com/2015-moto-g/general/root-how-to-root-moto-g-2015-android-t3320113e
Click to expand...
Click to collapse
C:\Program Files\Minimal ADB and Fastboot>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.313s]
booting...
FAILED (remote failure)
finished. total time: 0.391s
C:\Program Files\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 268435456 bytes
sending 'recovery' (8122 KB)...
OKAY [ 0.313s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.344s
C:\Program Files\Minimal ADB and Fastboot>
I tried to flash Twrp but iam getting this

Root 6.0.1
jerry94 said:
I have seen threads but nothing related to the 6.0.1 version. Please do help
Click to expand...
Click to collapse
I was also facing the same problem First of all u need to unlock bootloader then at bootloader "fastboot boot recovery.img" change your name twrp to recovery after that you will gets boot into twrp from there flash https://www.androidfilehost.com/?fid=24269982087018189 this file
Hit like if I'm helped you

I followed all the steps of unlocking the bootloader using AdB and Fastboot. After I enter my unique key it sends some commands rather than showing that the device is unlocked.

jerry94 said:
I followed all the steps of unlocking the bootloader using AdB and Fastboot. After I enter my unique key it sends some commands rather than showing that the device is unlocked.
Click to expand...
Click to collapse
Check this video to unlock bootloader. https://youtu.be/BCRpCEtcZ_c and if you are getting errors just search in google for solution

jerry94 said:
I followed all the steps of unlocking the bootloader using AdB and Fastboot. After I enter my unique key it sends some commands rather than showing that the device is unlocked.
Click to expand...
Click to collapse
Can you screenshot it and post it here?
Sent from my Motorola XT1575 using XDA Labs

acejavelin said:
Can you screenshot it and post it here?
Sent from my Motorola XT1575 using XDA Labs
Click to expand...
Click to collapse
I have unlocked the bootloader and flashed twrp now. It opened the twrpmode.i booted the fone.But after that while opening the recovery mode in fastboot it is showing 'no command'

jerry94 said:
I have unlocked the bootloader and flashed twrp now. It opened the twrpmode.i booted the fone.But after that while opening the recovery mode in fastboot it is showing 'no command'
Click to expand...
Click to collapse
If you are getting "No command" that is not TWRP, it is the factory recovery...
When you install TWRP with `fastboot flash recovery twrp.img` you must start TWRP, allow it to make changes to the system, then go to TWRP's reboot menu and select Reboot to Recovery. This action will permanently set TWRP as the recovery, otherwise the OS has a script which will restore the stock recovery on boot.
Proper way to flash TWRP, in my opinion, on a new (to TWRP) Moto device once the bootloader is unlocked:
1) fastboot boot twrp.img
2) do NOT tick "Never show this screen again on boot" and select Keep Read Only button
3) do a complete backup in TWRP, preferably to the microSD card. Make a copy of this backup and store it away safely for possible future use and keep a copy on the device if possible
4) reboot into bootloader
5) fastboot flash recovery twrp.img
6) start Recovery (TWRP)
7) tick "Never show this screen again on boot" and swipe to allow modification
8) go to Reboot and select Recovery **IMPORTANT** this step allows TWRP to "lock" itself in and prevent the OS from replacing it with the stock recovery again
9) TWRP should start again, and it should not prompt you at all and just go to the TWRP menu
10) Do what you wish in TWRP (flash SuperSU, install ROM, or whatever) if anything
11) Reboot - System
Replace twrp.img with the appropriate filename from http://twrp.me for the device. If you have already made changes to the system, just start at step #4

acejavelin said:
<< Proper way to flash TWRP, in my opinion, on a new (to TWRP) Moto device once the bootloader is unlocked:
1) fastboot boot twrp.img
2) do NOT tick "Never show this screen again on boot" and select Keep Read Only button
3) do a complete backup in TWRP, preferably to the microSD card. Make a copy of this backup and store it away safely for possible future use and keep a copy on the device if possible
4) reboot into bootloader
5) fastboot flash recovery twrp.img
6) start Recovery (TWRP)
7) tick "Never show this screen again on boot" and swipe to allow modification
..
..
.. >>
Click to expand...
Click to collapse
I've seen these steps a few times (OK, many times, with all the threads started on this exact question).
I'm just curious.. Why does it work? i.e. How is rebooting into TWRP without installing it, then immediately turning around, installing it, and running it... how is that different from just installing it first thing and running it? Like, what's going on internally that makes those two things different?
Thanks x
Sent from my Nexus 7 using XDA Labs

beachfl said:
I've seen these steps a few times (OK, many times, with all the threads started on this exact question).
I'm just curious.. Why does it work? i.e. How is rebooting into TWRP without installing it, then immediately turning around, installing it, and running it... how is that different from just installing it first thing and running it? Like, what's going on internally that makes those two things different?
Thanks x
Sent from my Nexus 7 using XDA Labs
Click to expand...
Click to collapse
OK... Booting TWRP without installing has nothing to do with functionality of TWRP, it is only to get a clean backup or if you want to root without installing TWRP. TBH, this entire piece is optional and could be skipped, but if you can get a clean backup it sure can makes things easier down the road.
When you flash TWRP, it is flashed... it is written into the recovery partition of your device, but if you start the operating system at this point there is a script (or something, going from my memory of the Nexus 4 which has a script that sat in /system that ran on each boot, so this has been an issue for a while in some devices) that re-writes the recovery it isn't "official". But, but flashing TWRP, allowing it to make changes, then rebooting into TWRP again, it gives TWRP a chance to do something that stops the restoring to official process to stop. I am not sure of the specific details, and I am not sure it really matters, but it works.

acejavelin said:
... Booting TWRP without installing has nothing to do with functionality of TWRP.. .
Click to expand...
Click to collapse
I get that thank you!
Sent from my Nexus 7 using XDA Labs

TWRP-3.2.0-0-sailfish.img Installing.

I followed the instructions on https://www.xda-developers.com/how-to-install-twrp/
when i run -- fastboot flash recovery twrp-2.8.x.x-xxx.img
(in my case -- fastboot flash recovery twrp-3.2.0-0-sailfish.img)
target reported max download size of 536870912 bytes
sending 'recovery' (26520 KB)...
writing 'recovery'...
(bootloader) Flashing active slot "_b"
FAILED ((remote: partition [recovery] doesn't exist
finished. total time 1.000s
I also tried this method from https://twrp.me/google/googlepixel.html
Installation:
If you do not already have TWRP installed: Download both the img and the zip. Copy the zip to your device. You will need to have fastboot binaries and the correct drivers installed. Power off your device completely. Hold volume down and turn on the device. Your device should now be in the bootloader. Connect the device to your PC. Open a command window and run the following command from the proper location:
fastboot boot path/to/twrp.img
This will temporarily boot TWRP on your device. If you are using a lockscreen pin/pattern/password and do not get prompted to enter your passord, reboot to the bootloader and try again. Go to install and browse to the zip and install the zip. The zip will install TWRP to both boot slots. Installing TWRP at this time will remove root if you are currently rooted.
this all seemed to go ok.... but i still dont have root ?????
any help to what i'm doing wrong ?

smudge100 said:
I followed the instructions on https://www.xda-developers.com/how-to-install-twrp/
when i run -- fastboot flash recovery twrp-2.8.x.x-xxx.img
(in my case -- fastboot flash recovery twrp-3.2.0-0-sailfish.img)
target reported max download size of 536870912 bytes
sending 'recovery' (26520 KB)...
writing 'recovery'...
(bootloader) Flashing active slot "_b"
FAILED ((remote: partition [recovery] doesn't exist
finished. total time 1.000s
I also tried this method from https://twrp.me/google/googlepixel.html
Installation:
If you do not already have TWRP installed: Download both the img and the zip. Copy the zip to your device. You will need to have fastboot binaries and the correct drivers installed. Power off your device completely. Hold volume down and turn on the device. Your device should now be in the bootloader. Connect the device to your PC. Open a command window and run the following command from the proper location:
fastboot boot path/to/twrp.img
This will temporarily boot TWRP on your device. If you are using a lockscreen pin/pattern/password and do not get prompted to enter your passord, reboot to the bootloader and try again. Go to install and browse to the zip and install the zip. The zip will install TWRP to both boot slots. Installing TWRP at this time will remove root if you are currently rooted.
this all seemed to go ok.... but i still dont have root ?????
any help to what i'm doing wrong ?
Click to expand...
Click to collapse
TWRP does not provide root privileges. You need to use Magisk 14.5 for root privileges on the Pixel. Link for Magisk:
https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589

phaino00 said:
TWRP does not provide root privileges. You need to use Magisk 14.5 for root privileges on the Pixel. Link for Magisk:
https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
Click to expand...
Click to collapse
Is there a guide anywhere on installing Magisk on the OG Pixel? I got TWRP installed and I have no password set so everything is decrypted. But whenever I boot my phone, I get errors about system stuff crashing and can't use my phone.
Do I need to install ElementalX as well? What could I be doing wrong?

daddylonglegs said:
Is there a guide anywhere on installing Magisk on the OG Pixel? I got TWRP installed and I have no password set so everything is decrypted. But whenever I boot my phone, I get errors about system stuff crashing and can't use my phone.
Do I need to install ElementalX as well? What could I be doing wrong?
Click to expand...
Click to collapse
Try a fresh install of the complete firmware, letting it wipe everything including data. Magisk v14.5 build 1456 works fine for me with the final 8.1.

daddylonglegs said:
Is there a guide anywhere on installing Magisk on the OG Pixel? I got TWRP installed and I have no password set so everything is decrypted. But whenever I boot my phone, I get errors about system stuff crashing and can't use my phone.
Do I need to install ElementalX as well? What could I be doing wrong?
Click to expand...
Click to collapse
Just as @roirraW "edor" ehT mentioned, do a completely fresh install of the December Factory Image. Boot into system and set up. Reboot into bootloader and install TWRP 3.2.0.0 via fastboot. Install Magisk 14.5 and reboot system. (In TWRP, you will want to hit cancel when prompted for pin/password, then select read only and install Magisk 14.5 via usb-otg). All should be good.
Hope this helps.

phaino00 said:
Just as @roirraW "edor" ehT mentioned, do a completely fresh install of the December Factory Image. Boot into system and set up. Reboot into bootloader and install TWRP 3.2.0.0 via fastboot. Install Magisk 14.5 and reboot system. (In TWRP, you will want to hit cancel when prompted for pin/password, then select read only and install Magisk 14.5 via usb-otg). All should be good.
Hope this helps.
Click to expand...
Click to collapse
Thanks but I have my phone set up so perfectly that the idea of losing all the data on my apps, their locations on my home screens, my widgets and how they are set up, etc. is something I don't think I can bring myself to do
I did install the complete factory image; the only thing I changed was I removed the -w command. Why is completely wiping the phone necessary to install Magisk anyway?

daddylonglegs said:
Thanks but I have my phone set up so perfectly that the idea of losing all the data on my apps, their locations on my home screens, my widgets and how they are set up, etc. is something I don't think I can bring myself to do
I did install the complete factory image; the only thing I changed was I removed the -w command. Why is completely wiping the phone necessary to install Magisk anyway?
Click to expand...
Click to collapse
Wiping the phone completely is not necessary to install Magisk, just recommended if issues persist.

be sure you have the right magisk version: 14.5 if you have the latest 8.1

smudge100 said:
I followed the instructions on https://www.xda-developers.com/how-to-install-twrp/
when i run -- fastboot flash recovery twrp-2.8.x.x-xxx.img
(in my case -- fastboot flash recovery twrp-3.2.0-0-sailfish.img)
target reported max download size of 536870912 bytes
sending 'recovery' (26520 KB)...
writing 'recovery'...
(bootloader) Flashing active slot "_b"
FAILED ((remote: partition [recovery] doesn't exist
finished. total time 1.000s
Click to expand...
Click to collapse
Make sure you've got the latest platform-tools: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
I was getting the same error until I updated the platform tools. Maybe it's a new version of fastboot? Regardless, fastboot boot [TWRPnamehere].img worked for me with the new tools/fastboot.

Twrp touchscreen not working.

First time trying to root, in order to install magisk and to get the full functionality of Edge sense +.
I was following this guide:
www-DOT-theandroidsoul-DOT-com/htc-u11-root-twrp-recovery-and-bootloader-unlock/
1. I have successfully unlocked bootloader
2. I have installed twrp
After some research, i think i made a mistake here, by installing twrp-3.1.1-0-ocn instead of the 3.2.1.2-ocn.
When booting to recovery mode, TWRP shows up, it asks for a password or to swipe the screen, but the screen is not responsive.
So i tried to flash the newest version of TWRP on top of the old one and i get this error :
PS C:\Users\ilan\Desktop\unlock-bl> fastboot flash recovery twrp.img
target reported max download size of 536870912 bytes
sending 'recovery' (39676 KB)...
OKAY [ 1.137s]
writing 'recovery'...
FAILED (remote: Not allowed on PRODUCTION device)
finished. total time: 1.145s
PS C:\Users\ilan\Desktop\unlock-bl>
How should i proceed?
I thought about going to stock recovery and then try to flash the new version of TWRP, but i didnt do a recovery. I have found that there is a way to recover to stock using something called RRU.
Help will b amazingly appreciated, tnx in advance

U may have already resolved..had same issue. Need to reboot directly to recovery and not via DL menu...then do Install Twrp Image file. Boot phone then if u can reboot directly to recovery go that route. If not try via Cmd Prompt...adb reboot recovery. Either way Twrp screen should be respnsive so u can flash Twrp img.

jelive said:
U may have already resolved..had same issue. Need to reboot directly to recovery and not via DL menu...then do Install Twrp Image file. Boot phone then if u can reboot directly to recovery go that route. If not try via Cmd Prompt...adb reboot recovery. Either way Twrp screen should be respnsive so u can flash Twrp img.
Click to expand...
Click to collapse
This is partially true. If anyone expierience touch screen not working in TWRP after following this tutorial: "theandroidsoul.com htc-u11-root-twrp-recovery-and-bootloader-unlock" - problem is, that old version of TWRP is linked there. You HAVE to download version 3.2 not 3.1 ->eu.dl.twrp.me/ocn/twrp-3.2.1-2-ocn.img.html
when touch screen is not working, use "adb reboot" and then "fastboot flash recovery twrp3.2.img"
it works for me

[SOLVED]Oneplus 7 stuck in fastbootmode after trying to restore a backup from TWRP

My bootloader is unlocked, I was rooted with Magisk and i had twrp recovery installed as well. A few modules were installed and i had made a backup about 3 weeks ago. Yesterday i tried restoring the backup in twrp and it seemed to restore properly without errors . When i pressed reboot in the end the phone went to the fastboot mode screen and has since been there. All i can do is turn it off and regardless of what i pick, (START, Restart Bootloader, Recovery mode) it just starts into fastboot mode. Confused as to what i should do now and why this happened in the first place. All the threads i found were only for the 7 pro so i didnt want to risk anything by following those. Please advice on what i should do.
Edit : The problem was solved by flashing the STOCK ROM for android 9 which is what i was on when the device was softbricked.

hi
Hi, download adb fastboot and twrp recovery image for guacamoleb. then open a new command prompt (CMD) in the same location and run the following commands:
Code:
fastboot flash recovery (file name of twrp that you download).img
after that by holding volume up + power reboot to twrp recovery that you just installed via adb fastboot command.
when you enter on twrp recovery, install twrp recovery zip, and magisk 19.3 zip (download and copy on phone storage first, after you enter on twrp when reboot, you can connect your phone with computer or USB that contain twrp recovery zip and magisk or copy to phone storage) after this step install twrp zip first than magisk and then reboot.
i hope i helped.
sorry for my english , is not my native language.

klediY said:
Hi, download adb fastboot and twrp recovery image for guacamoleb. then open a new command prompt (CMD) in the same location and run the following commands:
Code:
fastboot flash recovery (file name of twrp that you download).img
after that by holding volume up + power reboot to twrp recovery that you just installed via adb fastboot command.
when you enter on twrp recovery, install twrp recovery zip, and magisk 19.3 zip (download and copy on phone storage first, after you enter on twrp when reboot, you can connect your phone with computer or USB that contain twrp recovery zip and magisk or copy to phone storage) after this step install twrp zip first than magisk and then reboot.
i hope i helped.
sorry for my english , is not my native language.
Click to expand...
Click to collapse
Thank you for the reply. Unfortunately i am stuck in the very first step. After typing C:\adb\Oneplus 7>fastboot flash recovery twrp-3.3.1-1-guacamoleb.img in cmd the following happens
target reported max download size of 805306368 bytes
sending 'recovery' (56612 KB)...
OKAY [ 1.220s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 1.228s
I have tried using fastboot boot recovery instead in cmd. The following error comes up
cannot load 'recovery': No such file or directory.
I have checked whether the device is connected by typing in fastboot devices and it shows as connected. Any other suggestions will be helpful.

wolfsbane169 said:
Thank you for the reply. Unfortunately i am stuck in the very first step. After typing C:\adb\Oneplus 7>fastboot flash recovery twrp-3.3.1-1-guacamoleb.img in cmd the following happens
target reported max download size of 805306368 bytes
sending 'recovery' (56612 KB)...
OKAY [ 1.220s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 1.228s
I have tried using fastboot boot recovery instead in cmd. The following error comes up
cannot load 'recovery': No such file or directory.
I have checked whether the device is connected by typing in fastboot devices and it shows as connected. Any other suggestions will be helpful.
Click to expand...
Click to collapse
Something similar happened to me, I was on OOS 10 stable and wiping the system and data from TWRP got in fastboot mode without being possible to do anything else. The way that I solved was flashing from fastboot the OOS 10 stable posted rom here: https://forum.xda-developers.com/oneplus-7/how-to/rom-stock-fastboot-roms-oneplus-7-t3937478 This will erase all your data but you will unbrick your phone.
One important thing, if you are on android 10 you can't flash TWRP via fasboot, maybe that's the problem you are having right now.
Hope this helps

ryupunk said:
Something similar happened to me, I was on OOS 10 stable and wiping the system and data from TWRP got in fastboot mode without being possible to do anything else. The way that I solved was flashing from fastboot the OOS 10 stable posted rom here: https://forum.xda-developers.com/oneplus-7/how-to/rom-stock-fastboot-roms-oneplus-7-t3937478 This will erase all your data but you will unbrick your phone.
One important thing, if you are on android 10 you can't flash TWRP via fasboot, maybe that's the problem you are having right now.
Hope this helps
Click to expand...
Click to collapse
Ok so thank you for the help and you were right. Now i have an all new different problem. In a nutshell i flashed the stock ROM for android 9 while i was in android 10. I completely forgot you aren't supposed to do that. As a result i cant even access fastboot mode now. Can you please tell me how i can fix this problem?

wolfsbane169 said:
Ok so thank you for the help and you were right. Now i have an all new different problem. In a nutshell i flashed the stock ROM for android 9 while i was in android 10. I completely forgot you aren't supposed to do that. As a result i cant even access fastboot mode now. Can you please tell me how i can fix this problem?
Click to expand...
Click to collapse
I think that you will need to use the MSM tool, it looks like you have a hard brick, the good news is that oneplus devices can be revived in almost all cases. I have never used the tool but I found some posts that might help you. Best of luck!
XDA Oneplus 7 thread
https://forum.xda-developers.com/oneplus-7/how-to/unbrick-tool-oneplus-7-msmtool-hydrogen-t3953240
XDA Oneplus 7 pro thread
https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691
Oneplus forum guide
https://forums.oneplus.com/threads/...ide-for-a-hard-bricked-oneplus-7-pro.1041896/

ryupunk said:
I think that you will need to use the MSM tool, it looks like you have a hard brick, the good news is that oneplus devices can be revived in almost all cases. I have never used the tool but I found some posts that might help you. Best of luck!
XDA Oneplus 7 thread
https://forum.xda-developers.com/oneplus-7/how-to/unbrick-tool-oneplus-7-msmtool-hydrogen-t3953240
XDA Oneplus 7 pro thread
https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691
Oneplus forum guide
https://forums.oneplus.com/threads/...ide-for-a-hard-bricked-oneplus-7-pro.1041896/
Click to expand...
Click to collapse
I have tried using it but the problem is that MSM download tool does not detect my phone. i have uninstalled and let windows automatically update qualcomm drivers. I have also made windows manually install them after uninstalling.