Related
I've been posting here and there around here lately but thought I'd get a cleaner, more focused thread going for those of us who used HTC's unlock tool and want root.
I managed to get the bootloader unlocked with HTC's tool and installed SU and clockwork onto my Inc2 but I think I'm having problems because I'm still S-On instead of S-Off.
So, what do we do next after unlocking the bootloader? I'm under the impression that because I'm S-On still, I can flash a custom ROM, but not only the ones with the stock kernel intact. This would be why Sabotage was able to install, but Mik wouldn't. Still only a theory, though.
ANY HELP PLEASE!!!
Kayak83 said:
I've been posting here and there around here lately but thought I'd get a cleaner, more focused thread going for those of us who used HTC's unlock tool and want root.
I managed to get the bootloader unlocked with HTC's tool and installed SU and clockwork onto my Inc2 but I think I'm having problems because I'm still S-On instead of S-Off.
So, what do we do next after unlocking the bootloader? I'm under the impression that because I'm S-On still, I can flash a custom ROM, but not only the ones with the stock kernel intact. This would be why Sabotage was able to install, but Mik wouldn't. Still only a theory, though.
ANY HELP PLEASE!!!
Click to expand...
Click to collapse
There are 2 options to flash a custom ROM that has a custom kernel on an unlocked bootloader.
1. Instead of booting to recovery mode directly, you need to boot in Fastboot mode and issue the command:
Fastboot boot [path to custom recovery.img]
This will boot you into recovery mode using the custom recovery image. Then you can flash a custom ROM with a custom kernel correctly.
2. Extract the boot.img from the custom ROM zip file and copy it to your SDK tool directory.
Then boot into recovery mode and flash the custom ROM. Next you must reboot into bootloader mode and enter Fastboot mode. Enter the following command:
Fastboot flash boot [path to the boot.img file].
Try either option 1 or option 2. You do not need to do both.
Hope this helps.
tpbklake said:
There are 2 options to flash a custom ROM that has a custom kernel on an unlocked bootloader.
1. Instead of booting to recovery mode directly, you need to boot in Fastboot mode and issue the command:
Fastboot boot [path to custom recovery.img]
This will boot you into recovery mode using the custom recovery image. Then you can flash a custom ROM with a custom kernel correctly.
2. Extract the boot.img from the custom ROM zip file and copy it to your SDK tool directory.
Then boot into recovery mode and flash the custom ROM. Next you must reboot into bootloader mode and enter Fastboot mode. Enter the following command:
Fastboot flash boot [path to the boot.img file].
Try either option 1 or option 2. You do not need to do both.
Hope this helps.
Click to expand...
Click to collapse
Tried option 1 and when I go to select install zip from sd card after booting to cwm the phone restarts. Trying option 2 now...
Option #2 won't work since I get stuck at the HTC screen when trying to load a custom ROM.
Kayak83 said:
Option #2 won't work since I get stuck at the HTC screen when trying to load a custom ROM.
Click to expand...
Click to collapse
How did you try to reboot into bootloader from recovery once the ROM was flashed. Once I get into recovery I connect the phone with a USB cable and then type
Adb reboot bootloader
This will boot you into HBOOT straight from recovery and should prevent the hang at the HTC.
Ok. Let's start fresh and complete:
1- Plug phone into computer.
2- select HTC sync on phone
3- open cmd and get to sdk
4- type "adb reboot bootloader"
5- phone should reboot to HTC's recovery thing
now what?
I have cwm installed already.
Kayak83 said:
Ok. Let's start fresh and complete:
1- Plug phone into computer.
2- select HTC sync on phone
3- open cmd and get to sdk
4- type "adb reboot bootloader"
5- phone should reboot to HTC's recovery thing
now what?
I have cwm installed already.
Click to expand...
Click to collapse
Just select Charge Only, not HTC Sync.
Once you type adb reboot bootloader you should get the HBOOT screen and it should show FASTBOOT USB.
At this point you should enter Fastboot commands from you PC command prompt.
So you said you tried fastboot boot [path to recovery.img file] and it did boot you into recovery, right? Then you should be able to flash the custom ROM and reboot normally when the install is complete.
For option 2 once you are in recovery mode flash the custom ROM and then when it is finished connect the phone with the USB cable and at the command prompt you should be able to type adb devices and it will respond with your device id.
If it does, then type adb reboot bootloader and it will take you back to the HBOOT screen. From there you would then enter the following Fastboot command:
Fastboot flash boot [path to boot.img file]
Then Fastboot reboot
tpbklake said:
Just select Charge Only, not HTC Sync.
Once you type adb reboot bootloader you should get the HBOOT screen and it should show FASTBOOT USB.
At this point you should enter Fastboot commands from you PC command prompt.
So you said you tried fastboot boot [path to recovery.img file] and it did boot you into recovery, right? Then you should be able to flash the custom ROM and reboot normally when the install is complete.
For option 2 once you are in recovery mode flash the custom ROM and then when it is finished connect the phone with the USB cable and at the command prompt you should be able to type adb devices and it will respond with your device id.
If it does, then type adb reboot bootloader and it will take you back to the HBOOT screen. From there you would then enter the following Fastboot command:
Fastboot flash boot [path to boot.img file]
The Fastboot reboot
Click to expand...
Click to collapse
I'm able to fastboot into cwm. But when I go to select install zip from sd card via the phone controls (volume up/down/power), the phone reboots.
Kayak83 said:
I'm able to fastboot into cwm. But when I go to select install zip from sd card via the phone controls (volume up/down/power), the phone reboots.
Click to expand...
Click to collapse
Which version of CWM are ou using. I use CWM 5.0.2 and it works fine.
SUCCESS. Thanks for your help!
Glad you got it goin!
Sent from my ADR6350 using xda premium
Kayak83 said:
SUCCESS. Thanks for your help!
Click to expand...
Click to collapse
Which option did you have success with?
dumb question but...
how do you find the path to your custom recovery?
mza929 said:
dumb question but...
how do you find the path to your custom recovery?
Click to expand...
Click to collapse
You determine what the path is when you download the recovery image to your PC. The best place to download or copy it to is the same folder you run adb.exe and fastboot.exe from.
tpbklake said:
You determine what the path is when you download the recovery image to your PC. The best place to download or copy it to is the same folder you run adb.exe and fastboot.exe from.
Click to expand...
Click to collapse
great thank you... i was thinking i had to use a path to the recovery on my phone's storage not my PC's...
Can someone link me to a cwm recovery that works. I'm having the reboot issue after selecting choose file from SD card.
Sent from my dinc2 using XDA App
mza929 said:
Can someone link me to a cwm recovery that works. I'm having the reboot issue after selecting choose file from SD card.
Sent from my dinc2 using XDA App
Click to expand...
Click to collapse
You should look for and use CWM 5.0.2
Kayak83 said:
I've been posting here and there around here lately but thought I'd get a cleaner, more focused thread going for those of us who used HTC's unlock tool and want root.
I managed to get the bootloader unlocked with HTC's tool and installed SU and clockwork onto my Inc2 but I think I'm having problems because I'm still S-On instead of S-Off.
So, what do we do next after unlocking the bootloader? I'm under the impression that because I'm S-On still, I can flash a custom ROM, but not only the ones with the stock kernel intact. This would be why Sabotage was able to install, but Mik wouldn't. Still only a theory, though.
ANY HELP PLEASE!!!
Click to expand...
Click to collapse
OK maybe I am missing something here. Do you actually have full root? If you do, how did you get it? I don't know how to get the su binary and busybox installed. I have unlocked my bootloader using the htc supertool and I don't have root, which is keeping me from installing CWM or anything root related for that matter. I have not seen any instructions on how to root this thing since the unlock tool became compatible 3 days ago. But maybe I have missed something.
Thanks for any help.
Still cant get rom to boot... however, i have been able to fastboot into custom recovery and complete the flashing process...
Now i am just stuck at the HTC screen after reboot.
Any suggestions?
Thank you all so far. You have been most helpful.
***** update ***** I finally got it after fast booting into recovery, flashing rom, and then extracting boot.img from that rom and flashing it via fastboot.
mza929 said:
Still cant get rom to boot... however, i have been able to fastboot into custom recovery and complete the flashing process...
Now i am just stuck at the HTC screen after reboot.
Any suggestions?
Thank you all so far. You have been most helpful.
***** update ***** I finally got it after fast booting into recovery, flashing rom, and then extracting boot.img from that rom and flashing it via fastboot.
Click to expand...
Click to collapse
Yes good job. The last part is the key to getting a custom ROM installed. Glad it worked for you.
---------- Post added at 09:13 AM ---------- Previous post was at 09:09 AM ----------
hackweed said:
OK maybe I am missing something here. Do you actually have full root? If you do, how did you get it? I don't know how to get the su binary and busybox installed. I have unlocked my bootloader using the htc supertool and I don't have root, which is keeping me from installing CWM or anything root related for that matter. I have not seen any instructions on how to root this thing since the unlock tool became compatible 3 days ago. But maybe I have missed something.
Thanks for any help.
Click to expand...
Click to collapse
After you have an unlocked HBOOT, you need to flash CWM recovery image in FASTBOOT mode. Once you have CWM installed, you can install the latest SU-3.0.xx.zip to root your current ROM and then you can installl and use root programs like ROM Manager, Busybox, Titianium Backup, etc. or you can install a rooted custom ROM.
I have a nexus 7 2013 LTE build KOT49H
I initially managed to unlock and root using nrt 1.8...everything was perfect...there was some confusion getting adb setup though..
(for WugFresh...your instructions are fantastic but you should add a line to "check your device for the message to accept a connection for adb and select ok"...I found myself waiting and waiting, staring at my computer screen thinking that the nrt was hanging when all I needed to do was press "ok" on my device.)
Like I said...everything was perfect but I had to go one step further...
I then installed cyanogenmod 10.2 using twrp...tihs also went fine but I hated it and wanted to get back to my original google os. I had a really hard time getting adb set up once cyanogen was installed but once I finally did I was able to get back to stock again using nrt 1.8.
So now I'm back to stock image KOT49H. Everything runs fine and I see the unlocked logo when I boot so I assume I'm still unlocked.
Here's the problem..
When I try to root now, (I always run the NRT driver test until I get "success" message first) my device hangs on the "Booting modified boot.img to enable..." message.
And I mean hangs...can't even power it down without popping the cover and disconnecting the battery! Thankfully this gets me back to a running device but I still want to root this thing.
Any idea what might be wrong or where I should go to from here?
Thanks for any help you can suggest!
Did you re-enable USB debugging? Another thing is to switch to PTP mode instead of MTP. If none of that is the issue, it may be drivers, fire up wugs toolkit, hook up your device, and click the button "Full Driver Installation Guide", skip to Step 3 tab, and run the "Full Driver Test", if it fails then you're going to need to run through the steps in that "Full Driver Installation Guide, going through each step.
Well all you need to do for root is flash supersu.zip binary. If you have twrp on your device, boot to recovery. When you power on, hold down the volume down button also. When in boot loader mode, select recovery. If its not booting, you could just wipe to factory reset. Flash your supersu zip you'll be good.
Sent from my Nexus 7 using xda app-developers app
mdamaged said:
Did you re-enable USB debugging? Another thing is to switch to PTP mode instead of MTP. If none of that is the issue, it may be drivers, fire up wugs toolkit, hook up your device, and click the button "Full Driver Installation Guide", skip to Step 3 tab, and run the "Full Driver Test", if it fails then you're going to need to run through the steps in that "Full Driver Installation Guide, going through each step.
Click to expand...
Click to collapse
Thanks for the response...
All these check...I do have to switch to PTP to get adb functional and I do get success on the full driver test before I try rooting...device still hangs at "Booting modified boot.img to enable running privileged commands" message and then wont power down without disconnecting battery...
Which recovery are you on stock or still on twrp? If still on twrp, you might want to try flashing the supersu.zip yourself, just get the latest SuperSU put it on your device, and boot into twrp and manually flash it like datallboy suggests, this eliminates the PC/drivers/usb connection as a possible issue.
If you are on stock recovery either flash twrp, or if you want to keep stock recovery, you can boot into twrp temporarily without replacing the stock recovery.
datallboy said:
Well all you need to do for root is flash supersu.zip binary. If you have twrp on your device, boot to recovery. When you power on, hold down the volume down button also. When in boot loader mode, select recovery. If its not booting, you could just wipe to factory reset. Flash your supersu zip you'll be good.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the suggestions...
I lost twrp when I went back to stock build.
Sorry...I'm real green at all of this...
You think I should:
power up to fastboot mode...select boot loader mode...then select recovery to see if it boots?
You need to be real clear for me, I'm a total newb
I would need a link to thorough instructions for wiping to factory reset and flashing the supersu.zip...I do have adt installed and have my path modified so that I can run instructions like "adb devices" in a command window but I'm unclear as to where to place files so they will be seen if I try to flash them via adt. (like I say...this is all new to me and I'm not even sure if that last sentence makes sense)
mdamaged said:
Which recovery are you on stock or still on twrp? If still on twrp, you might want to try flashing the supersu.zip yourself, just get the latest SuperSU put it on your device, and boot into twrp and manually flash it like datallboy suggests, this eliminates the PC/drivers/usb connection as a possible issue.
If you are on stock recovery either flash twrp, or if you want to keep stock recovery, you can boot into twrp temporarily without replacing the stock recovery.
Click to expand...
Click to collapse
Thanks for responding!
TWRP was wiped when I went back to stock build...I'm assuming I have stock recovery now but when your device freezes in fastboot mode and wont power down without pulling the battery you cable you gotta wonder if you have any recovery at all!!!
I'll need instruction on how to flash twrp again...but I believe that this is the step that WugFresh's NRT is trying to do when the device freezes.
SMELZBAD said:
Thanks for responding!
TWRP was wiped when I went back to stock build...I'm assuming I have stock recovery now but when your device freezes in fastboot mode and wont power down without pulling the battery you cable you gotta wonder if you have any recovery at all!!!
I'll need instruction on how to flash twrp again...but I believe that this is the step that WugFresh's NRT is trying to do when the device freezes.
Click to expand...
Click to collapse
I typed this up on the fly so pardon any mistakes, there's more than one way to do this, but I'm basing this on already having wugs toolkit installed and updated and configured for your device on the PC you're going to do this on.
Plug device in, enable USB debugging mode, connect to PC, verify you can access your device through the PC, get the latest UPDATE-SuperSU-v1.XX zip, save it to your device (in the root of the sdcard).
EDIT: OR, even better, you can just boot the device and download it with chrome or whatever and save it to the sdcard, then you can continue:
Open windows explorer and navigate to (assuming you picked the default install directory):
C:\Program Files (x86)\WugFresh Development\data
...in that window, hold down shift, right click, select "Open command windows here", in it, type:
adb devices
...if nothing shows up post back (screenshot would be nice), if your device shows up, then open another windows explorer window and navigate to:
C:\Program Files (x86)\WugFresh Development\data\Recovery_Custom\TWRP\
...and copy the img (mine is openrecovery-twrp-2.6.3.1-flo.img) file you see in there to the other explorer window I told you to open earlier, now assuming you put the SuperSU file on your device in the root folder of the device, you should be able to do:
fastboot boot openrecovery-twrp-2.6.3.1-flo.img
This should reboot your device and boot twrp (this method does not replace whatever recovery you have on there now).
If you want to flash twrp and replace your current recovery you'd want to do:
fastboot flash recovery openrecovery-twrp-2.6.3.1-flo.img
Then once in twrp recovery you can select flash file, navigate to the UPDATE-SuperSU-v1.XX.zip file on your device, select it, and swipe to flash, reboot, run/install busybox and see what happens..it will let you know if there is a problem with root.
mdamaged said:
I typed this up on the fly so pardon any mistakes, there's more than one way to do this, but I'm basing this on already having wugs toolkit installed and updated and configured for your device on the PC you're going to do this on.
Plug device in, enable USB debugging mode, connect to PC, verify you can access your device through the PC, get the latest zip, save it to your device (in the root of the sdcard).
Open windows explorer and navigate to (assuming you picked the default install directory):
C:\Program Files (x86)\WugFresh Development\data
...in that window, hold down shift, right click, select "Open command windows here", in it, type:
adb devices
...if nothing shows up post back (screenshot would be nice), if your device shows up, then open another windows explorer window and navigate to:
C:\Program Files (x86)\WugFresh Development\data\Recovery_Custom\TWRP\
...and copy the img (mine is openrecovery-twrp-2.6.3.1-flo.img) file you see in there to the other explorer window I told you to open earlier, now assuming you put the SuperSU file on your device in the root folder of the device, you should be able to do:
fastboot boot openrecovery-twrp-2.6.3.1-flo.img
This should reboot your device and boot twrp (this method does not replace whatever recovery you have on there now).
If you want to flash twrp and replace your current recovery you'd want to do:
fastboot flash recovery openrecovery-twrp-2.6.3.1-flo.img
Then once in twrp recovery you can select flash file, navigate to the UPDATE-SuperSU-v1.XX.zip file on your device, select it, and swipe to flash, reboot, run busybox and see what happens.
Click to expand...
Click to collapse
Thanks a ton for the instruction!
I'm starting to make sense of this.
Found some other instruction for getting twrp back on the device which I think I'll try before flashing the superSU:
They're exactly what you're describing. I've also figured out where the flashboot.exe stuff is on my computer and added twp.img file there. I'' try getting twrp on and then I'll flash the superSU via twrp.
It'll probably be tomorrow before I get a chance to try all this but I'll be sure to post back once I do.
I'm still in the dark as to why missing this superSU thingy would be causing the device to freeze up the way it does when I try to root using WugFresh's NRT...I thought that flashing twrp and superSU is what the NRT is trying to do when it tries to root my device???
Anyway gtg...thanks all for assisting...I'll post back after the flash attempts...hopefully with happy news!
SMELZBAD said:
Thanks a ton for the instruction!
I'm starting to make sense of this.
Found some other instruction for getting twrp back on the device which I think I'll try before flashing the superSU:
They're exactly what you're describing. I've also figured out where the flashboot.exe stuff is on my computer and added twp.img file there. I'' try getting twrp on and then I'll flash the superSU via twrp.
It'll probably be tomorrow before I get a chance to try all this but I'll be sure to post back once I do.
I'm still in the dark as to why missing this superSU thingy would be causing the device to freeze up the way it does when I try to root using WugFresh's NRT...I thought that flashing twrp and superSU is what the NRT is trying to do when it tries to root my device???
Anyway gtg...thanks all for assisting...I'll post back after the flash attempts...hopefully with happy news!
Click to expand...
Click to collapse
Wug's toolkit is doing exactly that, the main difference in doing it manually is we get to see where the problem is.
If this fails then I would probably say you should backup anything on your device you don't want wiped, and try one click restore and try rooting again.
Good luck.
mdamaged said:
I typed this up on the fly so pardon any mistakes, there's more than one way to do this, but I'm basing this on already having wugs toolkit installed and updated and configured for your device on the PC you're going to do this on.
Plug device in, enable USB debugging mode, connect to PC, verify you can access your device through the PC, get the latest UPDATE-SuperSU-v1.XX zip, save it to your device (in the root of the sdcard).
EDIT: OR, even better, you can just boot the device and download it with chrome or whatever and save it to the sdcard, then you can continue:
Open windows explorer and navigate to (assuming you picked the default install directory):
C:\Program Files (x86)\WugFresh Development\data
...in that window, hold down shift, right click, select "Open command windows here", in it, type:
adb devices
...if nothing shows up post back (screenshot would be nice), if your device shows up, then open another windows explorer window and navigate to:
C:\Program Files (x86)\WugFresh Development\data\Recovery_Custom\TWRP\
...and copy the img (mine is openrecovery-twrp-2.6.3.1-flo.img) file you see in there to the other explorer window I told you to open earlier, now assuming you put the SuperSU file on your device in the root folder of the device, you should be able to do:
fastboot boot openrecovery-twrp-2.6.3.1-flo.img
This should reboot your device and boot twrp (this method does not replace whatever recovery you have on there now).
If you want to flash twrp and replace your current recovery you'd want to do:
fastboot flash recovery openrecovery-twrp-2.6.3.1-flo.img
Then once in twrp recovery you can select flash file, navigate to the UPDATE-SuperSU-v1.XX.zip file on your device, select it, and swipe to flash, reboot, run/install busybox and see what happens..it will let you know if there is a problem with root.
Click to expand...
Click to collapse
Followed your instructions...everything went as it should until I got to:
fastboot boot openrecovery-twrp-2.6.3.1-deb.img
instead of rebooting the device I only got waiting for device message in command window...
is device supposed to be put in bootloader mode before entering this instruction maybe???
okay I got twrp to flash...took like .7 seconds so I guess it was already on there...
when I tried to flash UPDATESuperSU (and by flash I assume you mean install???)
I get:
Updating partition details...
E: Unable to open zip file.
Error flashing zip ' /sdcard/UPDATE-SuperSU-v1.89.zip
Updating partition details...
and the in red underneath: Failed
and the 3 twrp button choices of home Wipe cache/davlik and Reboot System
I selected reboot system and then got message "this device is not rooted swipe to install SuperSU now
I swiped...and the system has rebooted and I now have SuperSU installer app icon in apps bit after running root checker I get device is not properly rooted message
I then ran the SuperSU installer app and it gave me an option to update via the play store...which I did...then ran SuperuserSU which was now updated and installed and it completed rooting...after rebooting the device Root Checker now shows device properly rooted!
THANKS A TON GUYS!!!
SMELZBAD said:
okay I got twrp to flash...took like .7 seconds so I guess it was already on there...
when I tried to flash UPDATESuperSU (and by flash I assume you mean install???)
I get:
Updating partition details...
E: Unable to open zip file.
Error flashing zip ' /sdcard/UPDATE-SuperSU-v1.89.zip
Updating partition details...
and the in red underneath: Failed
and the 3 twrp button choices of home Wipe cache/davlik and Reboot System
I selected reboot system and then got message "this device is not rooted swipe to install SuperSU now
I swiped...and the system has rebooted and I now have SuperSU installer app icon in apps bit after running root checker I get device is not properly rooted message
I then ran the SuperSU installer app and it gave me an option to update via the play store...which I did...then ran SuperuserSU which was now updated and installed and it completed rooting...after rebooting the device Root Checker now shows device properly rooted!
THANKS A TON GUYS!!!
Click to expand...
Click to collapse
Curious. It sounds like a permissions problem, not sure if fix permissions would have helped (no need to try if it's working as it should).
Oh well, glad to help and that it's sorted.
mdamaged said:
Curious. It sounds like a permissions problem, not sure if fix permissions would have helped (no need to try if it's working as it should).
Oh well, glad to help and that it's sorted.
Click to expand...
Click to collapse
Ya...something likely still abit wacky...I'll be sure to post if anything weird starts happening but for now all is good...I'm definitely rooted though...I was just able to mount a flash drive via Stick Mount and run a video off of it!
Hello to all. I have just unlocked bootloader, installed twrp and su. After everything booted up properly, I went to install an adblocker zip file, however once it booted into twrp it had no download folder, as well as when I went to reboot system it told me I had no os installed.. I'm a bit confused as to what to do now.. My apologies for clogging the thread if this has been answered before..
Edit: do I adb side load an image file or OS? I'm afraid of bricking this phone as I don't know how to continue from this point..
Which guide did you use to do all of this? I will help us understand where you started
Mrbobrowitz said:
Which guide did you use to do all of this? I will help us understand where you started
Click to expand...
Click to collapse
Hi thanks for the reply. This link right here:
http://www.androidsage.com/2016/11/...timate-guide-root-twrp-and-bootloader-unlock/
Steps I followed:
1 unlocked bootloader
2 Download the below files TWRP and Root files for Google Pixel & Pixel XL
Official TWRP for Pixel phones → Download |
Files: twrp-pixel-installer-sailfish-3.0.2-0-alpha1.zip 7.6M
twrp-3.0.2-0-alpha1-fastboot-sailfish.img 25M
Flash SuperSU 2.78 SRF4 → Download | File: SR4-SuperSU-v2.78-SR4-20161115184928.zip
Twrp install instructions:
Step 1: Download the TWRP recovery and latest SuperSU zip file for your Google Pixel and Pixel XL devices. There are 2 TWRP files with .zip and .img extensions. You will need both. You don’t need to extract the files, just place all the files on your PC as well as your Android phone’s internal storage where you can easily locate it.
Step 2: Make sure that you setup ADB and Fastboot on your PC and gone through all the prerequisites from above.
Step 3: Now plug in the Pixel device to the computer and open a command prompt or terminal on your PC to the window where TWRP.zip file is located. (See above to know how to open cmd)
Step 4: Boot your Android device into the bootloader or Fastboot mode. To do so, issue the following command through cmd or terminal. You can also manually boot into it using the hard key combination like Power+Volume Down while the device is turned off. Meanwhile, use code:
adb reboot-bootloader
Step 5: Now issue the following command in the command prompt to check your device connectivity
fastboot devices
Step 6: Now issue the following command to temporarily boot up the TWRP image.
fastboot boot path/to/twrp.img
Note: If you have installed our recommend quick 15 second ADB & fastboot installer, you do not need to insert the complete file path. Simply go to where the TWRP image file is and issue command “fastboot boot twrp.img” Otherwise, note that “path/to/” is the actual directory for the TWRP image file. Use fastboot boot and not fastboot flash and that the file you are booting is not the zip file.
Simply After that, TWRP will be accessible to you no matter which active partition slots are being used.
Step 7: After that fastboot command, you will be rebooted into a temporary TWRP recovery interface. To make it permanent, use the TWRP interface to navigate to and install the TWRP.zip file. This is just like using TWRP to flash custom ROMS and SuperSU.
Once the installation completes, you can now enjoy your new firmware. Alternatively, while, on Mac OS, you can issue “./fastboot boot path/to/twrp.img” command or on Linux type “sudo fastboot path/to/twrp.img” to flash the TWRP. For detailed tutorial and alternate methods to flash the TWRP recovery, click here.
Now it’s time to root your Google Pixel with latest SuperSU 2.78 SR4.
How to root :
Place the latest SuperSU 2.78 SR4 package onto your device’s internal storage or SDcard.
Boot your device into the custom TWRP recovery and tap install. For that, turn off your device completely and hold volume down and power buttons for a few seconds.
Once into TWRP tap the install button and select the SuperSU file.
Swipe the confirmation action below to start flashing.
Once done. reboot to system.
You can boot into the TWRP recovery by issuing the following command:
adb reboot recovery
There is an alpha 2 for twrp now. I would try installing this and seeing if it works. If not, you can simply flash the latest factory image and "start over". Granted you would lose any data that you might have had not backed up on your device, but youre not out of luck!
I wouldn't waste your time. Just flash the factory image and start all over. You managed to wipe the Rom off your device
Smallsmx3 said:
I wouldn't waste your time. Just flash the factory image and start all over. You managed to wipe the Rom off your device
Click to expand...
Click to collapse
Mrbobrowitz said:
There is an alpha 2 for twrp now. I would try installing this and seeing if it works. If not, you can simply flash the latest factory image and "start over". Granted you would lose any data that you might have had not backed up on your device, but youre not out of luck!
Click to expand...
Click to collapse
Thanks guys, I actually have installed the alpha 2 twrp. I guess my question is how do I proceed? I'm in twrp and my PC does not see the device when typing adb devices.. Within twrp it says no os installed... What do I do here?
So how do I "start over" or "flash factory image" from the state that I'm in?
mazubo said:
Thanks guys, I actually have installed the alpha 2 twrp. I guess my question is how do I proceed? I'm in twrp and my PC does not see the device when typing adb devices.. Within twrp it says no os installed... What do I do here?
So how do I "start over" or "flash factory image" from the state that I'm in?
Click to expand...
Click to collapse
You should be able to boot into fastboot
Smallsmx3 said:
You should be able to boot into fastboot
Click to expand...
Click to collapse
Ok, and if that works then flash 7.1.1? Then twrp alpha then root via SuperSU flash?
A side question here is how did I wipe the os/from off the phone? I'm stumped on that one..
mazubo said:
Ok, and if that works then flash 7.1.1? Then twrp alpha then root via SuperSU flash?
A side question here is how did I wipe the os/from off the phone? I'm stumped on that one..
Click to expand...
Click to collapse
I couldn't tell you! I've had it happen to me before a couple times. But yes if you can get into fastboot you should be able to fastboot flash a factory image. Then go and flash TWRP and root
Smallsmx3 said:
I couldn't tell you! I've had it happen to me before a couple times. But yes if you can get into fastboot you should be able to fastboot flash a factory image. Then go and flash TWRP and root
Click to expand...
Click to collapse
Ok thanks. I've been able to reboot to bootloader...
I've figured it out via fast boot. The phone is back in action, however not sure how it got wiped initially.. Thanks everyone!
mazubo said:
Ok, and if that works then flash 7.1.1? Then twrp alpha then root via SuperSU flash?
A side question here is how did I wipe the os/from off the phone? I'm stumped on that one..
Click to expand...
Click to collapse
mazubo said:
I've figured it out via fast boot. The phone is back in action, however not sure how it got wiped initially.. Thanks everyone!
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Off the top of my head... Probably selected the wrong "slot" maybe?
Remember on this device there are two locations for the ROM. Slot A and B. If you select the wrong one it will show no OS.
As far as the download folder missing... I know its mute at this point, but that has to do with the FBE (File Based Encryption). Make sure TWRP asks you for your Pattern Password. If you do not have one I would consider setting one. That way you know for fact that the File system will get decrypted properly. Also reports say you may have to reboot TWRP twice to get it to decrypt as well.
Attempted to root phone use ADB and fastboot.
during process noticed difficulty in getting recovery mode open manually and had to use adb reboot recovery, whereupon android recovery picture was there but no menu options.
Could not install TWRP conventionally thus attempted the method shown here.
"NSTALL TWRP
Make sure you have ADB and Fastboot installed.
I always put TWRP.img in the ADB folder - so if I want to boot into TWRP with out installing it this is what I do:
make sure you open a command prompt in the ADB folder "VERY IMPORTANT" and type:
adb reboot bootloader <enter>
fastboot boot TWRP.img <whatever your TWRP image is called in your ADB folder><enter> dont forget the .img at the end
That will re-start your phone straight into TWRP - You can transfer files to and from your computer while in recovery.
If you want to install TWRP permanently, copy your TWRP image to your mobile "while you are in TWRP RECOVERY mode" then press install, then select images, then select recovery NOT BOOT, then swipe to flash. This method does not install TWRP app on your phone, all you need is a reboot app from the play store that will re-boot you into recovery. "
Flashed both twrp image and super-su within the TWRP booted from pc through adb (as shown in the previously mentioned method).
Upon reboot phone has hung at LG symbol. LED is flashing. ADB recognises device as connected however won't respond to reboot requests.
How do i fix this?
GhostlessShell said:
Attempted to root phone use ADB and fastboot.
during process noticed difficulty in getting recovery mode open manually and had to use adb reboot recovery, whereupon android recovery picture was there but no menu options.
Could not install TWRP conventionally thus attempted the method shown here.
"NSTALL TWRP
Make sure you have ADB and Fastboot installed.
I always put TWRP.img in the ADB folder - so if I want to boot into TWRP with out installing it this is what I do:
make sure you open a command prompt in the ADB folder "VERY IMPORTANT" and type:
adb reboot bootloader <enter>
fastboot boot TWRP.img <whatever your TWRP image is called in your ADB folder><enter> dont forget the .img at the end
That will re-start your phone straight into TWRP - You can transfer files to and from your computer while in recovery.
If you want to install TWRP permanently, copy your TWRP image to your mobile "while you are in TWRP RECOVERY mode" then press install, then select images, then select recovery NOT BOOT, then swipe to flash. This method does not install TWRP app on your phone, all you need is a reboot app from the play store that will re-boot you into recovery. "
Flashed both twrp image and super-su within the TWRP booted from pc through adb (as shown in the previously mentioned method).
Upon reboot phone has hung at LG symbol. LED is flashing. ADB recognises device as connected however won't respond to reboot requests.
How do i fix this?
Click to expand...
Click to collapse
use you variant KDZ file and flash it with LGUP.
raptorddd said:
use you variant KDZ file and flash it with LGUP.
Click to expand...
Click to collapse
That worked very well. Thankyou raptorddd.
Praise him. Praise him with great praise.
Hi.
So I was messing around with the twrp custom recovery and (without thinking much of it) wiped everything in the advanced wipe menu :crying: (System, data, EVERYTHING)
I knew I had removed my OS and that I could just use the twrp recovery to install a new rom onto my phone BUT little did I know, when I tried to boot into the custom recovery, it would just loop the screen with the redmi logo
I am still able to boot into fastboot mode, and I have tried to flash the same twrp recovery but with no avail (It still loops the redmi logo screen)
So now I'm here to ask if there is any advice that you could give me to try and fix this problem that I have gotten myself in (I am not worried about deleting any of my personal files. I would just like to get twrp to boot so that I can install another rom)
Thanks in advance to anyone who can help me with this problem :highfive:
Hi, which rom are you trying to install? for android 9 use this recovery https://forum.xda-developers.com/re...overy-unofficial-twrp-recovery-redmi-t4002397, for android 10 this one... https://forum.xda-developers.com/showpost.php?p=82062075&postcount=7...
If what nuvulet said doesn't work, in fastboot, flash the exact same stock ROM you had before, let it boot and then flash TWRP.
nuvulet said:
Hi, which rom are you trying to install? for android 9 use this recovery https://forum.xda-developers.com/re...overy-unofficial-twrp-recovery-redmi-t4002397, for android 10 this one... https://forum.xda-developers.com/showpost.php?p=82062075&postcount=7...
Click to expand...
Click to collapse
Hi, thanks for the fast reply.
The stock android I had before I wiped everything was android 9, MIUI 11. I tried againt to flash the recovery through fast boot but (like before) when I try to boot into the recovery (by holding the volume up button as it reboots), the redmi logo keeps appearing and disappearing and doesn't go to the twrp recovery. At the current moment I don't have any OS installed (since it got deleted when I wiped everything)
Any other leads I could try?
wang1chung said:
If what nuvulet said doesn't work, in fastboot, flash the exact same stock ROM you had before, let it boot and then flash TWRP.
Click to expand...
Click to collapse
I'm not sure how I can flash the stock ROM without the twrp recovery. I had the impression that you needed twrp recovery in order to install ROMs in the first place.
If there is a method to flash a ROM using fastboot, please explain since my unexperienced self has no idea how to do this. :laugh:
Thanks for the fast reply too
Sqorpz said:
I'm not sure how I can flash the stock ROM without the twrp recovery. I had the impression that you needed twrp recovery in order to install ROMs in the first place.
If there is a method to flash a ROM using fastboot, please explain since my unexperienced self has no idea how to do this. :laugh:
Thanks for the fast reply too
Click to expand...
Click to collapse
MiFlash works through fastboot mode. It's also safer to flash with MiFlash, just make sure you have the correct ROM.
I can't find the guide right now, I'm at work
Ok, do you know adb fastboot... if not, follow this guide...
https://forum.xda-developers.com/showthread.php?t=2317790
Install usb adb drivers for RN8P if you don't have, try this for w10...
https://forum.xda-developers.com/redmi-note-8-pro/help/usb-drivers-t4035617
Download twrp for android 9 or android 10 from here...
https://forum.xda-developers.com/showpost.php?p=82115341&postcount=2
Put the recovery (*.img format) into installed adb folder...
Open cmd and navigate to inside adb folder...
Put the phone into fastboot mode (press volume- and power) connect usb and type in console...
adb devices (this start adb server)
Type...
fastboot devices (this return a device number, if not, something is wrong)
Type...
fastboot flash recovery *.img (change * for the name of the recovery file)
Disconnect the phone and press volume+ and power at the same time and now you have twrp intalled...
When start if the data is encrypted, push cancel, go to wipe, go to format data, type "yes", and confirm slide...
Now connect the phone to usb (if not recognize the phone, go to mount, and enable MTP)
Copy the rom in to internal storage for your android twrp version... search here
https://forum.xda-developers.com/redmi-note-8-pro/how-to/redmi-note-8-pro-android-10-public-t4072795
You have several versions... for eu, search in my post...
And the rest, install, select, etc. etc....
nuvulet said:
Ok, do you know adb fastboot... if not, follow this guide...
https://forum.xda-developers.com/showthread.php?t=2317790
Install usb adb drivers for RN8P if you don't have, try this for w10...
https://forum.xda-developers.com/redmi-note-8-pro/help/usb-drivers-t4035617
Download twrp for android 9 or android 10 from here...
https://forum.xda-developers.com/showpost.php?p=82115341&postcount=2
Put the recovery (*.img format) into installed adb folder...
Open cmd and navigate to inside adb folder...
Put the phone into fastboot mode (press volume- and power) connect usb and type in console...
adb devices (this start adb server)
Type...
fastboot devices (this return a device number, if not, something is wrong)
Type...
fastboot flash recovery *.img (change * for the name of the recovery file)
Disconnect the phone and press volume+ and power at the same time and now you have twrp intalled...
When start if the data is encrypted, push cancel, go to wipe, go to format data, type "yes", and confirm slide...
Now connect the phone to usb (if not recognize the phone, go to mount, and enable MTP)
Copy the rom in to internal storage for your android twrp version... search here
https://forum.xda-developers.com/redmi-note-8-pro/how-to/redmi-note-8-pro-android-10-public-t4072795
You have several versions... for eu, search in my post...
And the rest, install, select, etc. etc....
Click to expand...
Click to collapse
Yes, this is the method I used to flash the twrp recovery.
My problem was that even after installing it (using this method), i would still not be able to boot into the recovery.
However, it is fixed now. I used the Mi Flash tool in order to install the stock rom and then installed twrp after that. :good:
wang1chung said:
MiFlash works through fastboot mode. It's also safer to flash with MiFlash, just make sure you have the correct ROM.
I can't find the guide right now, I'm at work
Click to expand...
Click to collapse
I tried this method and IT WORKED!!
After installing Mi flash I was able to download the stock rom and install it through the program without any errors.
I was then able to finally boot into the OS and install twrp recovery, then install the custom rom! :laugh:
Thanks for this method. I would probably still be stuck on the Redmi logo if it weren't for this