Database Users

Recovery Flashing

If you are new to the Incredible and you want to flash a custom recovery there are three ways you can do this.
-I nor HTC is responsible for anything which happens to your phone.
1.) Rom Manager *Requires ROOT*
Go to the Play Store
Download Rom Manager
Flash ClockworkMod Recovery
Select HTC Incredible (If selection is not there try method 2 or three)
Allow Superuser Permissions
Done!
2.) HBOOT *Requires S-OFF or Unlocked Bootloader*
Download your custom recovery image
Download my PB31IMG(2).zip file *Do Not Extract*
Place your recovery image inside the zip and rename folder PB31IMG.zip
Place folder on the root of your sdcard
Power off you device completely (For Gingerbread HTC Sense users take out battery and put it back in)
Hold Power Button and Down Volume key
Wait for HBOOT to come up and let go
Volume up (Confirms you want to install it)
Done!
3.) Fastboot (Windows) *Requires S-OFF or Unlocked Bootloader, HTC Drivers and ADB package*
Download your custom recovery image
Download my ADB Package.zip file and extract it
Place your recovery image where you extracted the ADB Package and rename it recovery.img
Shift+Right Click in the folder where you extracted the ADB Package and select Open Command Window Here
Reboot into fastboot mode
a.) Type adb reboot bootloader in the command window with your phone
plugged in (ensure HTC Drivers are installed) and USB Debugging enabled
b.) Power off you device completely (For Gingerbread HTC Sense users take
out battery and put it back in) then Hold Power Button and Trackball. Plug in
phone
Type in the following into the terminal:
fastboot devices
(device serial number) fastboot
fastboot flash recovery recovery.img
sending 'recovery' (3064 KB)...
OKAY [ 0.446s]
writing 'recovery'...
OKAY [ 0.890s]
finished. total time: 1.338s
Done!

[Q] Cannot boot into a custom recovery

So, this is my first attempt at rooting a device and so far it's gone pretty well despite several hiccups along the way. My current problem is the inability to boot into a custom recovery. I'm running the stock 4.4.2 ROM, have root access per towelroot, have SU installed and updated from SuperSU, and have unlocked the boot loader via the motopocalypse exploit in it's .apk format. Booting into fastboot, I am able to verify I have unlocked the boot loader (Status Code 3.) Now, I have several custom recovery files downloaded and have attempted, including ClockWork Mod offical touch and non, and unofficial versions of TeamWin Recovery Project. All four of these yield the same results, namely, I cannot access them.
The steps I preform are:
(1. Turn the device off
(2. Boot into AP fastboot by holding down the volume + and - buttons, turning on the device, and selecting AP Fastboot as prompted
(3. Run the command "fastboot flash recovery <filename>.img"
(4. Have the following returned:
> sending 'recovery' (8228 KB)...
> OKAY [ 0.640s]
> writing 'recovery'...
> OKAY [ 2.180s]
> finished. total time: 2.820s
(5. Run the command "fastboot boot <filename.img>"
(6. Have the following returned:
> downloading 'boot.img'...
> OKAY [ 0.640s]
> booting...
> Command restricted
> FAILED (remote failure)
> finished. total time: 0.730s
(7. Run the command: "fastboot continue" to regain access to my phone
Also, when I boot into the boot selector and select the recovery option, it will show the "Warning, your warranty is void" prompt, flicker, then show the prompt again, which I presumed to be the phone flashing back the stock recovery, which I hadn't had previous success accessing fully either, and then continue to boot normally. Because of that, I used RootBrowser on my device and proceeded to move the "recovery-from-boot.p" file from it's /system home to /storage/emulated/0/Download in the case that I needed it again in the future.
Moving said ".p" file yielded no different result in the aforementioned fastboot commands. However, when I boot into recovery on the device itself via the boot selector, it will hang (let it run for five minutes at one point) at the "Warranty Void" screen, then restart into AP Fastboot after holding the power button, at which point I am unable to turn on the device and need to run the "fastboot continue" command to be able to access my device again. I will also need to run said command every time I want to restart my phone.
Copying said ".p" file back caused the device to again hang at the "Warning: Bootloader Unlocked" screen before I held down the power button which cause it to run AP Fastboot, at which point I could run the "fastboot continue" command and access my phone again.
Suffice to say I'm in a bit of a pickle and am a little lost as to how to get myself out of it. Any help would be greatly appreciated!
- J

The recoveries you should be using are here( TWRP for kitkat second from the bottom works the best) you can either fastboot flash or use rashr/ flashify available on the play store...
We cannot teach people anything; we can only help them discover it within themselves.

4502
I used the TWRP2710-RAZR_M-KITKAT.img and used the Fastboot command to flash it. My phone still isn't liking fastboot commands except for a few, but rebooting into recovery from the boot selector menu now works like a charm. Thank you!
- J

So, now I have the TeamWin Recovery Project functioning, however now I'm unable to flash any ROM. I've wiped the whole device using the advanced wipe feature, attempted to flash an official version of Cyanogen mod (namely 10.2-something,) and an official version of PacMan Rom. Both give me a failed error message whenever I try to flash them. I've just downloaded a fresh nightly from http://forum.xda-developers.com/showthread.php?t=2735565 from 25.08.2014 and I'm going to see if that does the trick. If that doesn't work, much as I'm anticipating, do you have any suggestions? (Also, would I be better off starting a new thread as this is pretty much a secondary issue?)
- J

Never mind! I was actually able to have a friend show me how to properly wipe a device before flashing a custom ROM and now it's functioning properly. Thank you again for your help!
In case someone else has this issue, how I wiped was first a Factory Data Reset, then an advanced wipe for the Cache and the Dalvic, then flashed the ROM and GAPPS, then wiped the Cache/Dalvic again, then actually rebooted the system and it started right into Cyanogen mod.

Yep, I tend to wipe each one(FDR & system+dalvic+cache) 3 times tho I don't think that's really necessary I just wanna be sure it got it all... Happy you got it all working
We cannot teach people anything; we can only help them discover it within themselves.

[Q] Flashing a recovery to I9505 (jgedlte)

I've been trying during the last few hours to flash CWM/TWRP to my S4. Before starting, my phone was simply rooted (with CF-auto-root and Odin).
So I ran
Code:
fastboot oem unlock
and now I'm trying to flash with
Code:
fastboot flash recovery <recovery.img>
, but I keep getting the following error:
Code:
sending 'recovery' (9588 KB)...
OKAY [ 0.419s]
writing 'recovery'...
FAILED (remote: FAILSecure - Secure check failed)
finished. total time: 1.224s
(This one is from a run with recovery-clockwork-6.0.4.7-jfltexx.img, I also tried openrecovery-twrp-2.6.3.0-jgedlte.img and got the same error).
I ran
Code:
fastboot erase recovery
to see if it would help, but it did not do any better in the next tries to flash.
Now, I DID manage to boot into CWM with
Code:
fastboot boot recovery-clockwork-6.0.4.7-jfltexx.img
, but I rather flash it (Especially now that I erased the stock recovery.)
I also tried Odin and Heimdall, but Odin simply crashes when I hit "Start" and Heimdall fails to to communicate with my phone.
EDIT: Great. When booting with "fastboot boot", TWRP's touch doesn't work. CWM's touch doesn't work either, so I use the non-touch version, but when trying to install CM with ADB sideload, adb on my PC doesn't recognize CWM. What am I supposed to do now...?

Jon-G said:
I've been trying during the last few hours to flash CWM/TWRP to my S4. Before starting, my phone was simply rooted (with CF-auto-root and Odin).
So I ran
Code:
fastboot oem unlock
and now I'm trying to flash with
Code:
fastboot flash recovery <recovery.img>
, but I keep getting the following error:
Code:
sending 'recovery' (9588 KB)...
OKAY [ 0.419s]
writing 'recovery'...
FAILED (remote: FAILSecure - Secure check failed)
finished. total time: 1.224s
(This one is from a run with recovery-clockwork-6.0.4.7-jfltexx.img, I also tried openrecovery-twrp-2.6.3.0-jgedlte.img and got the same error).
I ran
Code:
fastboot erase recovery
to see if it would help, but it did not do any better in the next tries to flash.
Now, I DID manage to boot into CWM with
Code:
fastboot boot recovery-clockwork-6.0.4.7-jfltexx.img
, but I rather flash it (Especially now that I erased the stock recovery.)
I also tried Odin and Heimdall, but Odin simply crashes when I hit "Start" and Heimdall fails to to communicate with my phone.
EDIT: Great. When booting with "fastboot boot", TWRP's touch doesn't work. CWM's touch doesn't work either, so I use the non-touch version, but when trying to install CM with ADB sideload, adb on my PC doesn't recognize CWM. What am I supposed to do now...?
Click to expand...
Click to collapse
This process will trigger knox to 0x1
1. Download the recovery you want:
Download philz touch revovery from here:
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/jflte/?page=4 (download the one with .tar.md5 extension)
Download TWRP here:
http://techerrata.com/browse/twrp2/jfltexx (download the one with .tar extension)
2. Download odin3 (v3.10.0) here:
https://mega.co.nz/#!OANlQZBS!GIq9q4Yy72syVYh36Q2whYIg85PST0QJhtIBrRh5MCk
3. Connect your phone in download mode to your PC (Don't reboot into download mode, shut down your phone and then boot into download mode) (you may have to install the driver, here: https://mega.co.nz/#!HQd12QYY!wuM2FvxmScI8rQIdosPaS6CLcvI4-yJNHHOiR3Rv0I0)
4. Open Odin click AP button, choose the file you downloaded and then click start.
5. Your phone will reboot, shut down your phone and try to boot into recovery (hold volume up and home and then press and hold power button release the power button when the blue text appears but keep pressing volume up and home, release those when the screen goes black).
6. You should now be in your chosen recovery.

jeffrey268 said:
This process will trigger knox to 0x1
1. Download the recovery you want:
Download philz touch revovery from here:
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/jflte/?page=4 (download the one with .tar.md5 extension)
Download TWRP here:
http://techerrata.com/browse/twrp2/jfltexx (download the one with .tar extension)
2. Download odin3 (v3.10.0) here:
https://mega.co.nz/#!OANlQZBS!GIq9q4Yy72syVYh36Q2whYIg85PST0QJhtIBrRh5MCk
3. Connect your phone in download mode to your PC (Don't reboot into download mode, shut down your phone and then boot into download mode) (you may have to install the driver, here: https://mega.co.nz/#!HQd12QYY!wuM2FvxmScI8rQIdosPaS6CLcvI4-yJNHHOiR3Rv0I0)
4. Open Odin click AP button, choose the file you downloaded and then click start.
5. Your phone will reboot, shut down your phone and try to boot into recovery (hold volume up and home and then press and hold power button release the power button when the blue text appears but keep pressing volume up and home, release those when the screen goes black).
6. You should now be in your chosen recovery.
Click to expand...
Click to collapse
You are giving him instructions for the I9505. I think he has a I9505G, so he should not follow your instructions. You are giving him a recovery for the I9505. The I9505G is a different model.
If Heimdall fails to communicate with your phone, then you don't have the correct drivers installed. TWRP doesnt have a non touch version. So my guess is that you flashed the recovery for a different device.

If the phone is already rooted just use ROM Manager or TWRP Manager apps from Google Play.
Both will just wipe out and overwrite any existing recovery image and replace it with the one you want. Problem solved right from the phone. No ADB shell needed.

Thanks guys. I managed to flash both philz (That link you gave me, although it is for I9505 and I do have a I9505G) and TWRP.
Both work, but besides them the phone is completely bricked.

Jon-G said:
Thanks guys. I managed to flash both philz (That link you gave me, although it is for I9505 and I do have a I9505G) and TWRP.
Both work, but besides them the phone is completely bricked.
Click to expand...
Click to collapse
If you can boot to recovery the phone is not a complete brick.
Once you are in recovery you can flash anything you want. You should be able to flash any new ROM and it will boot right up.

[GUIDE] Unlock Bootloader, Install Custom Recovery, and Root the Pixel C (2/4/2016)

The instructions in this guide are outdated and way more complicated than necessary. Once the official release of Android 7.0 Nougat becomes available/rooted, I will update the procedures in this thread. In the meantime, I recommend referencing this post along with the original instructions.
A massive shout out to @cheep5k8 for all the hard work he did in getting root and recovery working on the Pixel C. Please donate to him if you can. He deserves it.
Disclaimer: This will wipe your device. Backup anything important before you start. I mostly made this guide for selfish reasons. cheep5k8 has done a great job but some of the instructions are a little vague. I like being spoon fed and I wanted a resource to refer to in the future. You know the drill. If it breaks, not my problem. Post in the forums or hop onto the XDA IRC channel.
There may be more efficient ways to do this, but this will get you where you need to be. If you find any problems or have any suggestions, feel free to reply (BE VERY SPECIFIC WITH STEPS) and I will do my best to update the instructions.
Prerequisites:
ADB/Fastboot - Minimal ADB and Fastboot
ADB/Fastboot Drivers - I recommend using Wugfresh's Nexus Root Toolkit and using the full driver installation guide. Alternatively, you can install them yourself using the official Google Drivers (no installer)
An easy way to access the ADB prompt is to navigate to the directory that ADB is installed in, hold shift and right click inside the directory. This will give you an expanded right click menu that includes an option to "Open command window here." Select this option and a command prompt will open that is already in the ADB directory, saving you from having to do a bunch of cd nonsense. You can check to see if your device is recognized in ADB by typing "adb devices." If ADB and the driver are all working correctly, it should come back with something like "5A20001071 device." You can also check to make sure your device is recognized in fastboot by booting to the bootloader and typing "fastboot devices." It will show something similar.
Necessary Files:
Pixel C Recovery - Cheap5k8's Recovery -- NYCHitman's Recovery (newer)
Pixel C Root files - Download the XCeeD kernel, su.img, and SuperUser.apk
Copy these files to your directory that contains the ADB and Fastboot executables.
Device Prep:
Enable developer mode
Go to Settings > About tablet
Tap on Build Number 7 times until it says "You are now a developer"
Enable OEM Unlocking
Go to Settings > Developer options
Enable OEM Unlocking
Tap on Enable when a disclaimer pops up
Enable USB Debugging (ADB)
Go to Settings > Developer options
Enable USB debugging
Tap on OK when prompted with a disclaimer
If the ADB USB driver has been installed, you will see a popup that says "The computer's RSA key fingerprint is: xx:xx:xx:xx(blah blah)"
Check the box next to "Always allow from this computer"
Tap on OK
Unlock Bootloader:
Open ADB prompt (see prerequisites)
Input the following:
Code:
adb reboot-bootloader
The device will now boot into the bootloader and say
Code:
Waiting for fastboot command...
Input the following to unlock the bootloader:
Code:
fastboot flashing unlock
You will be prompted on the tablet screen with a warning about unlocking the bootloader.
Press the power button to unlock the bootloader.
The device will reboot and say "Bootloader is unlocked and OS verification is OFF. Device will continue booting in 30 seconds." You will also hear an audible beep. You will then see the green android with some spinny stuff. This is the userdata being formatted.
When complete, the device will boot back into the bootloader and say
Code:
Waiting for fastboot command...
Boot back into Android by inputting:
Code:
fastboot reboot
Your Pixel C will be reset, so you will need to re-enable USB debugging. Connect to your wireless network and then skip past everything else in the initial setup, as all of this setup info will be wiped again later on. Refer to the "Enable USB Debugging (ADB)" steps above to re-enable USB debugging.
Install Custom Recovery:
Open ADB prompt (see prerequisites)
Input the following:
Code:
adb reboot-bootloader
The device will now boot into the bootloader and say
Code:
Waiting for fastboot command...
With the Pixel C in the Fastboot bootloader and the recovery file in your ADB directory, input the following:
Code:
fastboot flash recovery (replace with custom recovery filename).img
Example:
Code:
C:\>fastboot flash recovery twrp-2.8.7.0-dragon-ryu-01082016-2.img
target reported max download size of 268435456 bytes
erasing 'recovery'...
(bootloader) erasing flash
OKAY [ 0.054s]
sending 'recovery' (13760 KB)...
OKAY [ 0.349s]
writing 'recovery'...
(bootloader) writing flash
OKAY [ 0.375s]
finished. total time: 0.783s
Reboot into Recovery using the physical buttons. If you reboot the device back into Android, it will write over the custom recovery with the stock one. This will be fixed in the future.
Code:
Power + Volume down until screen turns off, keep pressing volume down to boot into Coreboot Bootloader. Navigate to Reboot into Android Recovery with volume down and then press power to select.
Install Root:
In TWRP, navigate to Wipe > Format Data
Type "yes" in the warning prompt and wait for the userdata partition to format. Again, this will wipe your tablet.
Press the Home button at the bottom when the format is complete
Navigate to Reboot > Bootloader to boot back into Fastboot
In the ADB prompt, flash the new kernel:
Code:
fastboot flash boot (replace with xCeeD kernel filename).img
Example:
Code:
C:\>fastboot flash boot xceed-kernel-google-dragon-02-01-2016-RC1.img
target reported max download size of 268435456 bytes
erasing 'boot'...
(bootloader) erasing flash
OKAY [ 0.064s]
sending 'boot' (6220 KB)...
OKAY [ 0.161s]
writing 'boot'...
(bootloader) writing flash
OKAY [ 0.197s]
finished. total time: 0.426s
Reboot into Android. The device may boot twice.
Code:
fastboot reboot
Reboot back into Recovery. Power + Volume down until screen turns off, keep pressing volume down to boot into Coreboot Bootloader. Navigate to Reboot into Android Recovery with volume down and then press power to select.
In TWRP, navigate to Mount and check only Data
In the ADB prompt move su.img to /data:
Code:
adb push su.img /data
Example:
Code:
C:\>adb push su.img /data
5677 KB/s (33554432 bytes in 5.772s)
In TWRP, navigate to Mount and uncheck Data
In TWRP, navigate to Reboot > System
Perform initial device setup
Once you are at the home launcher, re-enable USB debugging (Refer to Device Prep)
In the ADB prompt, install superuser.apk:
Code:
adb install Superuser.apk
Example:
Code:
C:\>adb install Superuser.apk
8612 KB/s (6227998 bytes in 0.706s)
pkg: /data/local/tmp/Superuser.apk
Success
Install Busybox from the Play Store: link
Congrats. You are now rooted (not in the Australian sense).

Big big thanks
Amazing, great job.

P.S. One thing to add, for those who bought SuperSU Pro, you can install that too from the Play Store instead of installing the APK, but at the moment, it will say that the su binary is outdated (because the xCeeD kernel comes with 2.66, but SuperSU is already at 2.67). There needs to be a somewhat better solution but it's a bit hard to come up with it.
xCeeD v1-RC4 will have SuperSU updated to 2.67, and I'm thinking of how to make it possible to flash the normal SuperSU ZIP in TWRP. I will probably modify TWRP in some way to make that possible.

Very good step by step, guide, I went through the same process myself yesterday, although without the benefit of your guide!
Just one additional suggestion I would make, especially for people who have already got things set up nicely on their device.
Before doing anything you can make a backup of your device data using adb.
I used the guide at - http://forum.xda-developers.com/galaxy-nexus/general/guide-phone-backup-unlock-root-t1420351
Although you cannot guarantee everything will restore perfectly (I recommend that for important apps that have the capability - backup the settings manually and remember to copy them off the device), it certainly saved me a heck of a lot of time in putting things back exactly as they were before - and it is a lot quicker than letting google backup restore things.

Does this void the warranty?
Great job,anyway
Enviado desde mi Pixel C mediante Tapatalk

Cool, but you don't mind make put the video or pictured for guides.
Keep it up!!

there no show up wipe/ fromat data when I into in reboot into android recovery look like said no command

Scarfacez2007 said:
there no show up wipe/ fromat data when I into in reboot into android recovery look like said no command
Click to expand...
Click to collapse
Are you booting into TWRP recovery or the stock Android recovery?

I have unlocked and I was install install custom recovery that all
---------- Post added at 01:11 AM ---------- Previous post was at 12:21 AM ----------
I just installed trwp then I into on reboot into android recovery but still no command

Thank you for this in depth tutorial.. GREATLY appreciated..my C will be in tomorrow just in time for RC4! Hopefully all goes smooth with this. So no need to swipe fastboot fix in twrp??

Scarfacez2007 said:
I have unlocked and I was install install custom recovery that all
---------- Post added at 01:11 AM ---------- Previous post was at 12:21 AM ----------
I just installed trwp then I into on reboot into android recovery but still no command
Click to expand...
Click to collapse
I had that too after my first attempt, I reinstalled TWRP and it worked after the second flash.
There were no errors shown either time.

The same thing - no command, though the TWRP is installed. Re-installing doesn't help at all.
UPD Just managed to do this step by manually booting into recovery without booting the ui.

I updated the instructions saying to use the physical buttons to boot into recovery immediately after writing TWRP to flash. I believe this should mitigate the issue with the device overwriting the custom recovery before the kernel is flashed.

You don't mind guide put with the video or picture?

Scarfacez2007 said:
You don't mind guide put with the video or picture?
Click to expand...
Click to collapse
I have no plans to make a video or pictures.

Finally I got rooted about time!!!! thanks oRAirwolf!!!!

I just wondering I can download Xposed 6.0.1 on my pixel c?

Scarfacez2007 said:
I just wondering I can download Xposed 6.0.1 on my pixel c?
Click to expand...
Click to collapse
I have no idea. I would probably start a new thread in the Q&A section.

Scarfacez2007 said:
I just wondering I can download Xposed 6.0.1 on my pixel c?
Click to expand...
Click to collapse
Yep xposed works fine

How did you get download xposed with arm64 for Google Pixel C? where get it? you don't mind can find for me on link?

[GUIDE]Oneplus X MAC Root Guide

This guide will help mac users with rooting their Oneplus X
BEFORE STARTING!
This could void the warranty of your device.
I won’t be held responsible for anything that happens from doing this tutorial so please proceed at your own risk.
All your data will be erased, so please make a back-up!
Please enable usb debugging in developer options(tap 7 times on build number).
Connect your phone to your mac and you will see Oneplus Drivers in your finder.
Double click on AndroidFileTransfer(OSX).dmg
Drag Android File transfer to the programs folder.
Step 1: Setting up ADB and FASBOOT and unlocking the bootloader
- Power off your phone and hold power button+volume up
- The phone should enter fastboot mode
- Go to https://drive.google.com/drive/u/0/folders/0B-baud5R8XkwLWYxcHNmbGZTY1U
and download the 3 files.
- Go ahead and unzip fastboot.zip then copy over the recovery.img file into fastboot folder.
- Open Terminal
- In Terminal type the following with hitting enter at the end of each line:
cd downloads
cd fastboot
chmod 755 *
./fastboot-mac oem unlock
- Your phone will reboot and you will be asked to unlock the bootloader. Just hit the Power button and unplug
your phone
- Phone will reboot
- Setup your phone
- Copy the UPDATE-SuperSU-2.78.zip to the internal storage of your OnePlus X using Android File Transfer.
- Power off your phone and hold power button+volume up, you should enter fastboot.
- Re-connect the USB cable once in fastboot mode.
Step 2: Flashing custom recovery and rooting
- Open terminal
- In Terminal type the following with hitting enter at the end of each line:
./fastboot-mac flash recovery recovery.img
./fastboot-mac erase cache
- Wait for it to finish and unplug your phone
- Hold down power and volume down for 20 seconds.
- The phone should boot into recovery.
- Once in TWRP recovery, choose “Install”
- Choose the Super SU zip file you copied over to your phone earlier.
- Swipe to flash.
- Choose “Reboot System”.
- If twrp asks your to disable stock recovery, swipe to disable.
YOUR OPX WILL REBOOT AND IS NOW ROOTED!
To check, open to superSU app and check for errors, no errors=rooted!
Thanks to https://theunlockr.com/ for the windows tutorial.
Need help ? Post a comment and I will help. :good:
Noticed spelling mistakes? Please let me know

ᕕ( ಠ‿ಠ)ᕗ
Just hijacking this post here to say, way to go buddy !
jk, reserved

Sorry guys, I know this is a very old thread but I've tried this so many times and did not work. My problem is that nothing happens in my device when I type the command to unlock the bootloader using Terminal.
I get the following message: Brunos-MacBook-Pro:fastboot Brunolima$ ./fastboot-mac oem unlock
...
OKAY [ 0.001s]
finished. total time: 0.001s
Brunos-MacBook-Pro:fastboot Brunolima$
And then that's it. It doesn't reboot and when i manually reboot it is in the same state as before.
Any ideas guys?

Hey, I've been trying the same thing. Didn't have your specific issue but I think it may be related to the fact that it's already unlocked.
That said, I to make everything work I basically used this guide + the commands from the official TWRP guide at the page "TWRP for OnePlus X" + the command from a guide in the official OnePlus guide called "[GUIDE] ONYX: How to Unlock Bootloader, Install Custom Recovery, Root, Take EFS Backup & More !!" --- sorry but I can't post links.
All in all the commands I've used where:
adb reboot bootloader
fastboot devices
fastboot oem unlock
fastboot oem device-info
fastboot flash recovery twrp.img
fastboot boot twrp.img
brunolimaam said:
Sorry guys, I know this is a very old thread but I've tried this so many times and did not work. My problem is that nothing happens in my device when I type the command to unlock the bootloader using Terminal.
I get the following message: Brunos-MacBook-Pro:fastboot Brunolima$ ./fastboot-mac oem unlock
...
OKAY [ 0.001s]
finished. total time: 0.001s
Brunos-MacBook-Pro:fastboot Brunolima$
And then that's it. It doesn't reboot and when i manually reboot it is in the same state as before.
Any ideas guys?
Click to expand...
Click to collapse