Database Users

[Q] MT4G not taking CWM recovery

I'm working on a friend's MT4G after having rooted mine several months ago. The phone I'm working on is perm rooted with s=off. I can go into hboot and it shows s=off. The problem is the phone will not take Clockwork Mod's recovery.
CWM downloads and installs, then gets superuser permission and claims to be flashing recovery, but trying to reboot into recovery doesn't work. The phone boots to the "T-Mobile MyTouch 4G" screen, blinks off, comes back to that screen, then proceeds to boot to stock Android.
Uninstalling and reinstalling CWM just gets the same result - no recovery.
Shutting down completely then hoilding Vol up while pressing power makes the phone vibrate rapidly 3 times, then the LED blinks orange.
Going to hboot, then selecting recovery from there boots to stock Android same as trying to get to recovery through CWM.
How do I get this sucker to take CWM recovery?

It happened to me also, I just kept pressing it over and over and eventually it downloaded the file, If you have your's rooted why not go into your SD card and take the recovery IMG and put it on the other phone?

If you have the engineering screen you can ADB flash it via fastboot.
or you can use the ADB commands from within the ROM to do it.
either way download the recovery image i have posted in this thread. or from koush's web site store just the recovery image on the root of the SD card.
Code:
adb shell
su
flash_image recovery /sdcard/recovery.img
via hBOOT, give you have the .85 hBoot.
1) Download the attached file from the link i showed above and store just the recovery image to your folder from which you preform all of your ADB commands
2) plug the phone into the computer
3) boot the phone into HBoot
4) from the ADB commands change the drive to the folder where you stored the recovery image.
5) type these commands
Code:
Code:
fastboot flash recovery recovery.img
the screen should say something to the degree of
Code:
sending 'recovery' (3426 KB)... OKAY [ 1.172s]
writing 'recovery'... OKAY [ 0.797s]
finished. total time: 1.969s
6) then select "bootloader"
7) navigate to "reboot recovery"

Turns out that particular phone did NOT like CWM recovery 3.0.2.4. Once I got legacy recoveries to show up, I put 3.0.0.5 on it and was able to get into CWM recovery. From there I flashed 3.0.0.6, then put RoyalGinger on it.
Works great now, it's just odd that 3.0.2.4 didn't work on it.

Need help re-rooting N7 on 4.3

So I downloaded the 4.3 OTA (didn't flash, just downloaded it via my N7 (Non Wi-Fi model, also not 3G, just a regular N7).
That said, I can't seem to figure out how to flash twrp, downloaded it via Wug's toolkit (1.6.8)
I get the usual options: Recovery mode, power off, start, restart bootloader.
I tried: Root + "And also flash: custom recovery". I got the "no command" error, stuck there, and powered off my N7.
Now I'm back to square one: trying to figure out how to flash twrp and re-push SuperSU to re-root my N7. SuperSU is up to date via Google Play, but obv I'm still not re-rooted.
Any help would be greatly appreciated.

I just sorted this out myself. I'm certainly no expert, but here's what I did...maybe it can help you, too.
1. Get the files you need --- download the latest SuperSU, mini-sdk kit, and TWRP recovery files (the link I used was here, but I'm sure it's all here in XDA somewhere, too)
2. Place the files --- put the SuperSU zip file on the Nexus' sdcard, put the others in a directory on your PC/laptop
3. Connect the Nexus 7 --- plug it into a USB port on your PC/laptop and make sure USB debugging is enabled
4. Install the recovery --- once you're connected, open a command prompt on your PC/laptop, move to the directory with your files, and reboot the Nexus into fastboot mode; here's my command prompt output so you can see both the commands I typed and the responses I got (I renamed my recovery image from "openrecovery-twrp-2.6.0.0-grouper.img" to "recovery.img" for simplicity's sake):
C:\Users\[computername]>cd C:\Nexus 7\sdk-tools
C:\Nexus 7\sdk-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
[ serial number ] device
C:\Nexus 7\sdk-tools>fastboot devices
C:\Nexus 7\sdk-tools>adb reboot-bootloader
C:\Nexus 7\sdk-tools>fastboot devices
[ serial number ] fastboot
C:\Nexus 7\sdk-tools>fastboot flash recovery recovery.img
sending 'recovery' (7462 KB)...
OKAY [ 0.908s]
writing 'recovery'...
OKAY [ 0.303s]
finished. total time: 1.215s
C:\Nexus 7\sdk-tools>​
5. Reboot and flash --- now you should have the TWRP 2.6 recovery installed; reboot the Nexus into recovery mode (hold the Up & Down Volume keys at the same time; while doing so, press the on/off button until the system starts in recovery) and TWRP should come right up; flash the SuperSU zip file, then wipe cache/Dalvik, then reboot
Mine had to go through the optimization process on all my apps on the reboot, but everything came up correctly after a few minutes. I did some spot-checking of a couple of my root apps, and all appears to be working correctly (at least for the moment).
Hopefully this can get you working again, too. Good luck!

Stuck on boot animation screen? [SOLVED]

I tried to root my NSTV and got as far as flashing the .zip file in TWRP but after I rebooted, it's now stuck in the boot animation screen with the dancing colored circles?
Any ideas please?
SOLUTION
First download Recovery OS Image from here: https://developer.nvidia.com/gameworksdownload
SHIELD RECOVERY IMAGE FLASHING INSTRUCTIONS
To follow the instructions in this guide, you will need adb and fastboot.
 These tools are provided as part of the Android SDK:
http://developer.android.com/sdk/index.html
Before flashing this recovery image to your SHIELD, connect your SHIELD
 via USB to the PC where you downloaded this recovery image.
Next, put your SHIELD into fastboot mode using one of the following methods:
SW method:
- Boot to android home screen
- Connect the device to linux/windows system
- Open terminal (on linux); command prompt (on windows).
- Type "adb reboot bootloader" in terminal/command prompt
HW method:
- Disconnect power cable
- Insert USB OTG cable and make sure to connect other end to a host PC
- Connect power cable to SHIELD
- Quickly start pressing power button for ~3 seconds
- Do not hold the button and connect power supply afterwards
- HDMI TV should be always connected to SHIELD
Alternative method:
- Perform software shutdown on SHIELD by holding Power button for 10 seconds
- Connect USB OTG cable to SHIELD
- Start pressing power button for 3 seconds
- HDMI TV should be always connected to SHIELD
Fastboot menu navigation:
- Single tap on touch button for navigations between different menu.
- Hold down touch button for 4 second and release for selecting any menu
To flash this recovery image to your SHIELD, run the following commands from
 the directory where you extracted the recovery image package. If this is the
first time you have done this procedure, you must unlock the bootloader. Get
 DTB file name to use for flashing for your product(see below):
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash staging blob
fastboot flash dtb <DTB file name>
Unlocking the Bootloader
Your SHIELD may have shipped with a locked bootloader. To update the device,
you must unlock the bootloader using the following:
- fastboot oem unlock
- It will take you to '!!! READ THE FOLLOWING !!!' page.
- Two selectable options are available. 'Confirm' and 'Back to menu'.
- Select 'Confirm' to unlock the bootloader.
Unlock may take upto 2 hours for pro device.
Get <DTB file name>
- For base sku use dtb file "tegra210-foster-e-p2530-0930-e02-00.dtb"
- For pro sku use dtb file "tegra210-foster-e-hdd-p2530-0932-e02-00.dtb"

old thread i know, but still very helpful!
after updating to 3.2 yesterday and then trying to root it again (lost after the update), i was stuck at the boot animation screen for-ev-ver!!
used this guide to fix and was successful, however there was one change that i had to make: after extracting the 3.1 recovery image....there was no "userdata.img" file. so in place of that file, i flashed the "vendor.img", which was in the extracted folder along with the other files i needed to flash.
in the end what worked for me was the following:
downloaded the 3.1 recovery OS image from the link provided in OP. extracted/unzipped the image file to a folder, then from that folder i flashed the following files in this order:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash staging blob
fastboot flash dtb tegra210-foster-e-p2530-0930-e02-00.dtb
worked like a charm for me, booted up fine, ran updates and when it was done it asked if i wanted to update to version 3.2 ....i said yes and when that finished, i tried to root it once again. all went smoothly this time. not sure what went wrong the first time, but i am now on version 3.2, rooted, and did not even lose any data along the way!!
hardest part for me was getting into the bootloader (using HW method posted above). took me quite a few tries before i nailed it, lol
thanks for posting @Neo3D

Just tried to do it, but failed:
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 67108864 bytes
sending 'recovery' (22712 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 5.014s

I;m stuck,it won't except the tegra darcy or tegra foster. Help please i am sitting her stuck!

[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