Database Info

Elaboration on "how to root"

I think this thread can eventually turn into a sticky. I am going to ask all the common / newbie questions relating to the post by toast that is quoted below. Please contribute clear answers in the thread and I'll include them here at the top:
Q: What does RUU stand for?
A: ROM Upgrade Utility. It is used when a new ROM is available by your carrier. Don't use this since it will nullify your root.
Q: Where can I find photos of the root process?
A: Right Here, thanks to pingpongboss
Q: Where can I find the details and download locations of the custom roms available?
A: ???
Q: What is a custom recovery?
A: ???
Q: What is a recovery partition?
A: ????
Q: What things are we not able to do since we don't have the ability to
toastcfh said:
Write to system or recovery while in android
- Flash a custom recovery that can be booted into by holding vol down and powering on
Click to expand...
Click to collapse
A:
1) You cannot remove unwanted applications inside of android that couldn't normally be removed. You must remove them prior to boot.
2) ???
Q: What are all those code snipbits?
A: ??
Q: What is the point of the "recovery instructions"?
A: ??
toastcfh said:
HOW TO ROOT YOUR HTC EVO
DO NOT USE A RUU FROM SPRINT IF U WANNA MAINTAIN ROOT. WAIT FOR ME OR SOMEONE HERE TO MAKE A ROOT UPDATE.ZIP.
Major thanx for those who helped:
keishou (for the rooted build. without it none of this would be possible)
maejrep (for testing and modding a recovery for the EVO)
Flipz (for hosting the files)
Paul (for his recovery work on the desire and legend)
Amon_RA (for his recovery source on github)
WHAT THIS ROOT METHOD WILL DO:
- wipe all of your data so brace for that. backup or what not
- Allow you to flash custom roms
- Boot into a custom recovery
- Write to system, boot and recovery partitions through recovery
WHAT THIS ROOT METHOD SADLY WONT ENABLE YOU TO DO:
- Write to system or recovery while in android
- Flash a custom recovery that can be booted into by holding vol down and powering on
THINGS YOU WILL NEED:
download files below:
- PC36IMG.zip
- evorecovery
INSTUCTIONS FOR ROOTING:
- Put the PC36IMG.zip on the root of your sdcard
Code:
adb push PC36IMG.zip /sdcard
- Power off the phone
- Hold volume down while powering the phone on. continue to hold volume down until you see the WHITE bootloader screen.
- After a few seconds it will begin to checking for files, and find PC36IMG.zip. while its doing this it will show a blue progress bar while its checking. (this takes 30 - 60 seconds to finish)
- It will then list all the images in the zip and ask you if want to flash. SAY YES
- When its finished it will ask you if you would like to reboot. AGAIN... SAY YES
- At this point it will boot into a rooted rom.
- YOU ARE NOW ROOT!!!
- rename the PC36IMG.zip on your sdcard:
- plug your phone into a usb port on your desktop and do:
Code:
adb shell mv /sdcard/PC36IMG.zip /sdcard/root-PC36IMG.zip
RECOVERY INSTRUCTIONS:
- Extract the evorecovery.zip to your desktop
- plug your phone into a usb port on your desktop
- In a shell:
Code:
adb reboot recovery
- this will reboot your EVO into recovery mode. at this point turn your attention to the directory u extracted the evorecovery.zip to.
Code:
For Windows XP ~~> Run recovery-windows.bat
For Vista and Windows 7 do it as Admin
- in a shell do:
Code:
For Linux ~~> ./recovery-linux.sh
- at this point turn your attention to the phone and navigate to create a Nandriod Backup. you can now flash custom roms, write, and make changes to system.
- to flash a custom rom put the rom on the root of your sdcard. wipe data, dalvic cache and chose the option to flash update.zip from sdcard.
RECOVERY NAVIGATION:
-
Code:
Volume up/down moves through the list and Power selects.
RECOVERY SOURCE:
- http://github.com/jhansche/amonra_bootable_recovery/tree/supersonic
Code:
git clone git://github.com/jhansche/amonra_bootable_recovery.git
git checkout supersonic
Click to expand...
Click to collapse

Pics of the rooting process: http://androidforums.com/htc-evo-4g/90122-root-out.html

pingpongboss said:
Pics of the rooting process: http://androidforums.com/htc-evo-4g/90122-root-out.html
Click to expand...
Click to collapse
Phenomenal. Added to the original post. Could you please help with some of the other questions if possible?
Thanks

forumsid987 said:
Phenomenal. Added to the original post. Could you please help with some of the other questions if possible?
Thanks
Click to expand...
Click to collapse
Where to find custom roms: in this subforum xD
the rest of the questions I don't know how to answer correctly. Custom recovery lets you flash custom roms and make nandroid backups?

forumsid987 said:
Q: Where can I find the details and download locations of the custom roms available?
A: ???
Q: What is a custom recovery?
A: ???
Q: What is a recovery partition?
A: ????
Q: What things are we not able to do since we don't have the ability to
A:
1) You cannot remove unwanted applications inside of android that couldn't normally be removed. You must remove them prior to boot.
2) ???
Q: What are all those code snipbits?
A: ??
Q: What is the point of the "recovery instructions"?
A: ??
Click to expand...
Click to collapse
In order top to bottom:
As they become available you will find them in this forum. I will release a fresh rom for evo once I can test on my own device. It will be posted here, as well as at http://geekfor.me like always.
The green and black screen that you see that lets you flash a custom rom and create a nandroid backup, that is a custom recovery. The problem is because of NAND protection we can't currently flash that recovery and have it stick. That's why you have to run the bat/sh script each time, to load it manually.
It's the partition that the recovery resides on (the part of the internal storage memory).
Aside from not writing to system while booted (which was answered already) all that means is that instead of being able to boot directly in to the custom recovery view power button + home button or volume down, you need to run that script to get in to recovery. That's the only thing not being able to load the custom recovery means.
Code snipbits?
Um, because how else would you know how to get in to recovery so that you can flash a rom / create a backup / etc??

Is there any chance of fixing that recovery issue? Having to run the script to access it each time is going to get old fast.
-------------------------------------
Sent via the XDA Tapatalk App

In the rooting instructions it keeps mentioning just plug phone into usb port on a pc and in shell do this.
I am on windows 7..what shell?

maybe change the thread title to FAQ on how to root rather than elaboration, might attract more attention.
i was going to answer the questions which haven't been answered but flipzmode did a great job and the 1st post hasn't been updated. once the 1st post has been updated i'll check back and add more detailed if there is anything left to help with!
MrDSL said:
In the rooting instructions it keeps mentioning just plug phone into usb port on a pc and in shell do this.
I am on windows 7..what shell?
Click to expand...
Click to collapse
good question, this would be good to add to the guide above.
the shell on windows 7 means the command prompt. never used win 7 but on win xp and vista, start->run->cmd
and it pops open the command prompt, navigate to where you extracted the zip file contents to, cd c:\evo-root\ . then run the .bat file by typing recovery-windows.bat .
on linux the terminal interface is called a shell because it actually brings up a shell binary, /bin/sh or /bin/bash . google these binaries for more detailed information. on windows the shell, is basically the command line which is now emulated in windows, where back in the days of DOS it was the actual system with windows loaded on top as a GUI...
sorry prob too much information!

Is there an alternative to reboot recovery that does not require ADB?

forceOnature said:
Is there an alternative to reboot recovery that does not require ADB?
Click to expand...
Click to collapse
an alternative way to reboot into recovery without using adb?
boot into the bootloader and select recovery? use the quick boot GUI to reboot directly into recovery? use connectbot and connect localhost, type reboot recovery?
you'll be needing ADB for a good chunk of the custom recovery process in order to load this Froyo ROM.
adb isnt too bad, just dive in and we're all here to help!

MrDSL said:
In the rooting instructions it keeps mentioning just plug phone into usb port on a pc and in shell do this.
I am on windows 7..what shell?
Click to expand...
Click to collapse
Start -> Accessories -> Right-Click on "Command Prompt" -> select "Run as Administrator".
If you don't need to run as admin, you can do
Start -> type cmd -> Enter
and it'll come up.

adb driver for windows 7
http://depositfiles.com/en/files/yd61xorii

Anyone have some solid "Adb on Mac" instructions? LIke how to get it going on a mac... Just switched from PC... Thanks

a5ehren said:
Start -> Accessories -> Right-Click on "Command Prompt" -> select "Run as Administrator".
If you don't need to run as admin, you can do
Start -> type cmd -> Enter
and it'll come up.
Click to expand...
Click to collapse
I believe Start -> type cmd -> Shift+Enter will run as admin also.

JustinChase said:
I believe Start -> type cmd -> Shift+Enter will run as admin also.
Click to expand...
Click to collapse
Simply put im on a mac and a windows at the same time.. I cannot get the bat to run correctly I see it run but it looks like a fc and then it closes.. On the mac I get asked for this..
sudo: ./adb-mac: command not found
sudo: ./adb-mac: command not found
new-host:~ GodDriven$ sudo: ./adb-mac: command not found
Please help?

[RECOVERY][TOUCH]TWRP 2.7.0.0 Touch Recovery [UPDATE TO #define's thread]

Since, @#define doesn't has the device anymore and I was working on updates of TWRP Recovery, so after some talks with him, I am making a new thread where I will maintain TWRP Releases.
OFFICIAL TWRP HTC EXPLORER PAGE
Latest Release - v 2.7.0.0 by @thewisenerd
What's new in 2.7.0.0:
Faster graphics rendering by disabling alpha blending on fully opaque objects thanks to Tassadar
Allow sideloading from /tmp on encrypted devices
Check for a crypto footer before asking for a password to prevent user confusion
Additional checks for validity to auto generated backup names
Text wrap in the console output
Proper caps lock support in the keyboard
Mouse support via USB OTG for devices with a broken digitizer
Improve scanning of storage locations for OpenRecoveryScript
Haptic feedback for buttons, keyboard, and vibration at the end of longer running actions
Fixed ext4 wiping when no selinux contexts are defined for that partition (e.g. sd-ext)
Update SuperSU to 1.93 and improve installation process
Added selinux contexts restoration to fix permissions
Load RTC offset on Qualcomm devices to fix the date/time in recovery
USB Mass Storage fixes Add SELinux support checking
Add Disk Usage class to better handle excluded folders (e.g. Google Music cache)
Add 4.4 AOSP decrypt support
Add some toolbox utilities to TWRP (namely to support SELinux functions not supported in busybox)
Various SELinux fixes and bug fixes
Removed Superuser prebuilt binary and Superuser.apk (By me not in Official TWRP) to trim the recovery size.(Thanks for the idea @galaxyfreak )
Older Changelogs
For the new people, here are the instructions..
----> For Windows :
1) Download the recovery zip and the tools given above..
2) Extract the zips someplace safe (for eg, C:/TWRP)..
3) Open the command prompt, and navigate to the folder in which you extracted the files..
4) Boot your phone into Fastboot mode, and connect it to the computer.. It should show "Fastboot USB"
5) In the command prompt, type :
Code:
fastboot flash recovery recovery.img && fastboot reboot
6) Enjoy your new recovery!! :good:
----> For Linux :
1) ADB and Fastboot for linux are also attached above..
2) Download and extract all the stuff in a safe location (for eg, ~/TWRP)
3) Open terminal, and navigate to the goodies folder..
4) Put your phone in fastboot mode, and connect to USB, and it should show "Fastboot USB"..
5) Now in terminal, type :
Code:
$ ./fastboot flash recovery recovery.img && fastboot reboot
6) Enjoy your new touch recovery!! :good:
Credits -
@#define
@galaxyfreak
@thewisenerd

thank you for updating this man

Nice Work mann!!
Thnks!! for update!!

a bug is it reboots when wiping partitions sometimes

theBstep said:
a bug is it reboots when wiping partitions sometimes
Click to expand...
Click to collapse
Yes I know. Restarting device/recovery fixes it!

v_superuser said:
Yes I know. Restarting device/recovery fixes it!
Click to expand...
Click to collapse
just letting you know cus so far no one's been posting around about this cus it's just a minor bug but if you can fix it for further builds that will be good

Bug founded
When restore/wipe than recovery restart not rebooting recovery.second time working?
If it's already noticed,solve in next version?
logcat:

Recovery restarts when try to fix permissions

Was anyone able to get fastboot working?
I remember it working in my home builds, but I don't recollect it working in this recovery though.
Is this "bug" only for me?
Edit: NVM, borked USB
edit: spoke too soon. Yes. adb *is* broken. works at times, doesn't work, at times.
edit: let's put this post to good use:
Download: http://www.mediafire.com/download/sx78aa9eu21c54q/twrp_21may2014.img
Don't give the crap that you're even interested in changelog. You just need something that works. You'd not even know if this is just the same file, with a different name.
For those who really are, go over to https://github.com/omnirom/android_bootable_recovery/commits/android-4.4, and check the commits from Mar 28, 2014.

Nand recovery partition burned
For those who are encountering NAND Recovery Partition burned.
booting on recovery,
TWRP logo shows
then go black screen
then TWRP logo shows again
then stucked at TWRP Logo.
SOLUTION:
BOOT into BOOTLOADER.
FLASH Latest PhilZ Touch Recovery (here: http://forum.xda-developers.com/showpost.php?p=41061154&postcount=3)
Download flash_erase.txt *rename and remove .txt* it's a binary file.(here: http://forum.xda-developers.com/attachment.php?attachmentid=1655489&d=1358514526)
Flash any rom that has working ADB.
Push flash_erase on /system/xbin then set and fix permissions.
Code:
adb push flash_erase system/xbin/
adb shell
su
cd system/xbin/
chomd 755 flash_erase
Reboot
Then perform a NAND Recovery on /recovery partition. (Needs USB debugging enabled and Root access on Apps and ADB)
Code:
adb shell
su
cd /system/xbin
./flash_erase -N /dev/mtd/mtd1 0 0
FLASH TWRP Recovery.
NOTE: IF YOU GOT WHOLE YOUR MTD PARTITION BURNED. flash_erase mtd0 to mtd6.

Agaphetos said:
For those who are encountering NAND Recovery Partition burned.
booting on recovery,
TWRP logo shows
then go black screen
then TWRP logo shows again
then stucked at TWRP Logo.
SOLUTION:
BOOT into BOOTLOADER.
FLASH Latest PhilZ Touch Recovery (http://forum.xda-developers.com/showpost.php?p=41061154&postcount=3)
Then perform a NAND Recovery on /recovery partition (http://forum.xda-developers.com/attachment.php?attachmentid=1655489&d=1358514526)
Code:
flash_erase -N /dev/mtd/mtd1 0 0
FLASH TWRP Recovery.
Click to expand...
Click to collapse
I would suggest you do that not from the recovery.
You can also do the same procedure with any ROM booted and ADB or Terminal Emulator

thewisenerd said:
I would suggest you do that not from the recovery.
You can also do the same procedure with any ROM booted and ADB or Terminal Emulator
Click to expand...
Click to collapse
yeah. i just cut the instructions. haha. they must flash ROM first then put flash_erase on /system/xbin.
then perform flash_erase -N /dev/mtd/mtd1 0 0.
it's only for those who got whole MTD partition got burned.
they can't boot into both /system and /recovery.
Edit: I updated my post already.

Agaphetos said:
yeah. i just cut the instructions. haha. they must flash ROM first then put flash_erase on /system/xbin.
then perform flash_erase -N /dev/mtd/mtd1 0 0.
it's only for those who got whole MTD partition got burned.
they can't boot into both /system and /recovery.
Edit: I updated my post already.
Click to expand...
Click to collapse
I have burnt my nand several times and i couldnt get into TWRP recovery at all ( stuck at the logo ). The solution I found was to downgrade to CWM 5 and then format boot/system/data. Then flash back TWRP 2.7 and superwipe for nand recovery - thanks to thewisenerd works like a charm.

boko_to said:
I have burnt my nand several times and i couldnt get into TWRP recovery at all ( stuck at the logo ). The solution I found was to downgrade to CWM 5 and then format boot/system/data. Then flash back TWRP 2.7 and superwipe for nand recovery - thanks to thewisenerd works like a charm.
Click to expand...
Click to collapse
i suggest you to still flash_erase your /recovery partition.
flashing another recovery on your /recovery partition doesn't recover bad blocks.

Agaphetos said:
i suggest you to still flash_erase your /recovery partition.
flashing another recovery on your /recovery partition doesn't recover bad blocks.
Click to expand...
Click to collapse
Yes right, - I was just giving a workaround if someone can't get into recovery - and what worked for me - after re-flashing TWRP i never had any problems with the recovery partition again.

Do you need to have your device to S-OFF?

fgaurano said:
Do you need to have your device to S-OFF?
Click to expand...
Click to collapse
Pico has no s-off so no developer expects it
Sent from my Xperia S using XDA Free mobile app

I have my Fastboot USB connected, and after typing the command, it justs " < waiting for device> " I tried removing USB a lot of times already and fastbooting USB.

fgaurano said:
I have my Fastboot USB connected, and after typing the command, it justs " < waiting for device> " I tried removing USB a lot of times already and fastbooting USB.
Click to expand...
Click to collapse
That also happened to me. If youre using windows 8.1, maybe thats the problem. The only way was flashing through terminal emulator.

I have the recovery partition burned, but the instrutions to fix are not clear enough for noobs like me.
EDIT: Based on the @Agaphetos instrutions and from this thread http://forum.xda-developers.com/showthread.php?t=2389445
Note: This method WON'T work on Windows 8/8.1. It will work fine on windows 7.
Backup your apps and stuff before doing anything
1. Download and Install HTC Sync Manager http://www.htc.com/pt/software/htc-sync-manager/
2. Download and Install ADB fastboot drivers http://forum.xda-developers.com/showthread.php?t=2588979 (I dont know if this is really necessary)
3. Get the adb and fastboot drivers, you can use the ones from this recovery, just remove the "recovery.img" that comes with http://forum.xda-developers.com/attachment.php?attachmentid=913094&d=1329843100
4. Download this PhilZ Touch Recovery http://forum.xda-developers.com/showthread.php?t=2265055 and rename it as: recovery.img
5 Place the "recovery.img" that you have renamed to the "A310E Recovery" folder
6. Remove the Battery and SIM card (in case you dont have a mobile network plan) If the rom youre using has the "Reboot to Bootloader" option in "Power Menu" you can use that instead.
7. Place the battery, and press "Volume Down" and "Power Button" at the same time till you boot into "Bootloader".
8. Connect your phone to the PC and choose "Fastboot", it will show "Fastboot USB" in red, then go to the "A310E Recovery" folder and run the "recovery.bat". You have flashed the PhilZ Touch Recovery.
9. Press "Power Button" to exit "Fastboot". In "Bootloader" menu choose "Recovery" to enter in PhilZ Touch Recovery.
10. In there make a "Wipe Data/Factory Reset", "Wipe cache", go to Advanced: "Wipe dalvik cache". Go to "Mounts and Storage" and format everything except "/sdcard". (Maybe you dont need to wipe everything Ive mentioned:silly
11. Scroll down and choose "Mount USB storage".
12. Download a CM rom, Ive used this one http://forum.xda-developers.com/showthread.php?t=2535682, and place the .zip rom in root of sdcard. Im sure other CM roms will also work.
13. Download this AROMA Filemanager http://forum.xda-developers.com/showthread.php?t=1646108 and place it in root of sdcard.
14. Download (Save this file as) flash_erase.txt http://forum.xda-developers.com/attachment.php?attachmentid=1655489&d=1358514526 and remove the ".txt" file extension and place it also in root of sdcard.
15. Flash the CM rom. Once flashed the rom go to "Mounts and Storage". Mount everything till you see all "unmount", go back.
16. Flash the "aromafm.zip". It will open AROMA filemanager. Scroll down and enter in "sdcard" and copy the "flash_erase" file, go back. Look for a "system" folder, scroll it down till you find one saying "xbin", enter there and paste the "flash_erase" file.
17. Look for the "flash_erase", and then long press it till you see a menu, choose "Set permissions". The first 3 lines should be all green already, Exit AROMA Filemanager. and reboot system.
18. Once youve booted into the CM rom, go to "Settings" -> "About Phone", In there scroll down to "Build Number" and press it several times to enable "Developer Options".
19. Go back and enter "Developer Options", make sure "Android debugging" is enabled. Connect your phone to the PC. Now go to "Terminal Emulator" and enter the following commands.
Code:
su
cd /system/xbin
./flash_erase -N /dev/mtd/mtd1 0 0
It will show up a message with something about 100% I cant remember:silly:
20. Boot into "Recovery" again, make a Wipe and Format everything, like you did in step .10.
21. In "Power Off" menu of the Recovery, choose "Reboot to Bootloader"
22. Plug in the phone in "Fastboot USB" and repeat the step .4, .5 and .8 but for the TWRP Recovery instead.
23. You should now be able to boot into the TWRP recovery, make sure you Wipe Everything again in "Wipe" -> "Advanced Wipe", except "sdcard". If the recovery reboots while wiping, reboot recovery and try again.
DONE!

HOWTO: Root without unlocking the Bootloader

A lot of people have been asking, so here are my notes for gaining root w/o flashing or unlocking the boot loader. :good:
Thanks to Chromium and The Jack of Clubs for their initial concepts and documentation.
Download ADB and set up Tools
Download the full Android SDK here:
http://developer.android.com/sdk/index.html#download
(scroll to the bottom of the page -> DOWNLOAD FOR OTHER PLATFORMS -> SDK Tools Only)
Extract the android-sdk-windows zip to c:\android-sdk
Browse to C:\android-sdk\android-sdk-windows\
Double Click and run SDK Manager.exe
Uncheck everything except the Android SDK Tools and Android SDK Platform-tools
Hit the Install xx Packages button
Download Super SU and TWRP
Download the latest TWRP here:
http://techerrata.com/browse/twrp2/bacon
Extract the TWRP image file and save it as recovery.img in the following folder:
C:\android-sdk\android-sdk-windows\platform-tools
Download SuperSU here: http://download.chainfire.eu/452/SuperSU/UPDATE-SuperSU-v2.02.zip
Plug your phone into your computer and Copy SU zip to the phone... (anywhere will work)
Get your Phone into Fastboot
Reboot the phone in fastboot mode (hold volume up + power). You should get a cyanogen guy smiling at you, this indicates the phone is in fastboot mode.
Open a command prompt and do:
cd C:\android-sdk\android-sdk-windows\platform-tools
Type:
fastboot devices
NOTE: You should receive a list of connected devices, this means your PC is connected to your phone. If not, something is wrong with ADB or your USB driver and you need to fix it before you can proceed!
Boot with TWRP and Flash
If “fastboot devices” worked without error, type this:
fastboot boot recovery.img
After the recovery.img transfers, your phone reboots into TWRP. Hit “Install” and choose the SuperSU.zip from the location on your phone that you saved it to earlier.
Once flashing is done, reboot and enjoy root. No re-imaging or unlocking your bootloader necessary.

Why is a unlocked bootloader a problem?

_Beni_ said:
Why is a unlocked bootloader a problem?
Click to expand...
Click to collapse
if you dont want to wipe data, it also sets flags a tamper bit (which can now be reset), or if you just plain dont want to.

The Jack of Clubs said:
if you dont want to wipe data, it also sets flags a tamper bit (which can now be reset), or if you just plain dont want to.
Click to expand...
Click to collapse
Ah ok, i did unlock and switch to PA after second boot , so there were no data that would be lost

May I ad that there is an easier way to get adb. Its a program called minimal adb. This what I used originally in case someone prefers to just download that file. Just an option thats all... :good:
Nice tutorial

Install TWRP and root LG v10 H901 T-Mobile

Download
Search for TWRP recovery for LG V10 H901 (File: twrp-2.8.7.0-h901.img (31.7 MB))
Backup Apps and Data
While this process should not wipe any of your data, a backup is highly recommended. Once you install a custom recovery like TWRP, make sure you backup your system, data,etc. from the recovery. It will be helpful in case anything goes wrong.
Prerequisites
This guide is compatible with LG V10 H901 only. Do not try it on any other devices or variants.
Unlocked bootloader is required to install a custom recovery like TWRP on your device. Click here.
Set up ADB and Fastboot on your computer. You can download the minimal ADB and fastboot tool from here (unzip it) or get the quick ADB and fastboot installer from here.
Install Motorola USB Drivers on your computer.
Open Settings> Developer options and enable USB Debugging on your device.
Go to Developer options and enable Allow oem unlock.
How to Install TWRP Recovery on LG V10 H901
Download the recovery image file. Extract if in case a zip file. Now transfer the file to your PC where you can easily locate it.
Make sure you have setup ADB and fastboot on your PC. Also accept Always allow from this computer when you plug in the device for first time to enable USB Debugging.
Now power off your device and unplug it from your PC.
Boot into the bootloader or fastboot mode. To do so, press and hold volume down and the power button simultaneously for 5-6 seconds. When you see the bootloader screen, connect your device to the PC using a USB cable.(Choose fasboot if option is available) Alternatively, you can also issue the following command through your cmd or terminal, while connected to the PC in order to boot into the bootloader.
"adb reboot bootloader"
Navigate to the location where you have placed the recovery file. Rename the recovery file to a simple one, like recovery.img. While the folder with recovery.img file is open, hold shift key on keyboard and right-click on an empty space and select “Open command window here” option to launch a cmd window.
Now issue the following command in the command prompt to check your device connectivity
"fastboot devices"
Now flash custom recovery. Issue the following command for that.
"fastboot flash recovery recovery.img"
Custom recovery will now be installed on your device. Now boot your phone in recovery mode. You can do this by turning your device off and then press and hold volume down and power keys at the same time. Or you can simply enter the following command.
"fastboot boot recovery.img"
Once into the recovery, you can backup your current ROM, data, EFS and more.
Once you have installed TWRP, you are all set to install custom packages onto the device’s system. Alternatively, while on Linux or Mac OS, you can issue “./fastboot flash recovery recovery.img” command to flash the TWRP recovery.
Root
As you already have TWRP, simply flash the SuperSU file (version 2.56) to gain root access

@TheJesus @KAsp3rd, thanks guys for everything you've done over the past few days. no shade to @joe01gun but if people are going to use these instructions make sure you search the rest of the forum for what thejesus and kasp3rd put together to get us to this point - definitely appreciated. thanks @joe01gun for putting these additional instructions together.

Your post says the following:
Set up ADB and Fastboot on your computer. You can download the minimal ADB and fastboot tool from here (unzip it) or get the quick ADB and fastboot installer from here.
yet, there's no link to the necessary files to "unzip" them. Any suggestions?
Thank you for the help, but where do we get fastboot set up on our PCs? Yes, this is getting confusing with the steps outlined above. I followed the first step and had to take out the battery because I was stuck in fastboot screen with small tiny text in the top left that didn't respond to any manipulation with the volume keys on the back of the device and wouldn't restart any way until I took out the battery.

sanjsrik said:
Your post says the following:
Set up ADB and Fastboot on your computer. You can download the minimal ADB and fastboot tool from here (unzip it) or get the quick ADB and fastboot installer from here.
yet, there's no link to the necessary files to "unzip" them. Any suggestions?
Click to expand...
Click to collapse
I think it's cause he's not allowed to post links yet cause he's too new. I followed this guide http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
You can get twrp from the development forum.

Why
Intended to put the information condensed....
Yep....new
Links could not be uploaded.

joe01gun said:
Intended to put the information condensed....
Yep....new
Links could not be uploaded.
Click to expand...
Click to collapse
Your condensed thread is more convoluted than the actual development thread which also includes the links to everything.
I'm still wondering why you have install Motorola USB drivers for an LG phone..

Understood
Understood

The one on development is straightforward and I managed to make it done.
If you don't lock the bootloader back, you will see bootloader unlocked when starting up.
If you have root enabled file explorer, you should remove /system/priv-app/adaptclient folder to avoid annoying root request from adapt.

Please use the main dev thread for instructions on what to do, found below. Having duplicates for what is essentially the same thing can cause confusion and just takes up unnecessary space. So I have closed the thread.
[Recovery][LG-H901] Unofficial TWRP
Forum moderator,
matt4321

[ROOT] Coolad Modena 2 / Sky 2 (E502)

Recently, I successfully ported TWRP from Coolpad Note 3 Lite to Modena 2. After testing, everything works fine, on both devices. Since this device has locked bootloader, we need to bypass this by enabling fastmmi mode and factory mode to enable temporary root access and make initial backup and flashing. So, let´s get started.
Remember to read this post carefully. I am not resposible for any damage to your device. If you brick your device while flashing the TWRP you can *almost* always recover it using SP Flash Tool and YGDP Tool
IF YOU ACCIDENTALY BRICK YOUR DEVICE AND YOU WANT TO FLASH IT VIA SPFT, DO NOT FORMAT THE DEVICE IN SPFT!!! If you´ll format partitions in TWRP, that´s fine, but don´t do FORMAT ALL + DOWNLOAD or FIRMWARE UPGRADE! This will brick your device, like mine This tutorial will not (hopefully) brick it, but just in case something goes wrong, now you know what not to do.
Preparing the environment on your computer
Windows
Download ADB and Fastboot from this link
Open it
Install it system-wide
Also, install the drivers
GNU/Linux (Ubuntu / Debian based distros)
Open terminal
Type "sudo apt install adb fastboot libusb-dev" without the quotes (")
Other things, that are required
Since the file size of the recovery exceeds the maximum 8MB of allowed upload size, you can download it from DataFileHost.
Preparing the device
First, you need to remeber that this could render your device unbootable and will void warranty.
Enable developer options
Go to Settings -> About phone
Tap the build number 7 times
Go back
Go to Developer options
Make sure OEM unlocking and USB Debugging is enabled
Enabling factory mode
Open dialer app
Dial *#9527*#
Click on "DM"
You will be prompted to insert RD personnel password. Enter: 54321
Click cancel button
DM button should change colour to RED
Exit the app by clicking home button
Installing and setting up openrp app
Open terminal / command prompt
Type:
Code:
adb start-server
Type:
Code:
adb devices
Now, click on your phone allow debugging and make sure to tick the radiobutton to remember / always trust this computer
Type:
Code:
adb install
Press spacebar after the install word and drag and drop the downloaded openrp.apk file to terminal
Hit enter
After it´s done, type:
Code:
adb shell monkey -p com.yulong.openrp -v 500
Now, the fun part. ROOTING the device
But before that, BACKUP
Now, keep your phone plugged in, and do a normal reboot by pressing and holding the power button and clicking reboot
When it vibrates, press and hold the Volume down key (Vol-)
You will see these lines on the screen:
Code:
=>[Factory mode]
Code:
=>VolumeDown key is pressed
Code:
=>[fastmmi mode]
After that, you´ll see the LED turns green and "Up Down" text on the screen
Now, back to your computer, type in the command prompt
Code:
adb devices
You should see XXXXXXXXXXXXXX device listed (where XXXX... is the serial number)
Type in the command prompt:
Code:
adb shell dd if=/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/recovery of=/storage/self/primary/stock_recovery.img
and
Code:
adb shell dd if=/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/boot of=/storage/self/primary/stock_bootimg.img
Flashing the TWRP Image
Type in the command prompt:
Code:
adb push (drag and drop the recovery image file here, like you did with the openrp.apk file) /storage/self/primary/
Type:
Code:
adb reboot
Press and hold VolumeDown key (Vol-) to boot to fastmmi mode
Type:
Code:
adb shell dd if=/storage/self/primary/recovery_twrp_e502.img of=/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/recovery
Type
Code:
adb reboot
Press and hold the VolumeUp key (Vol+) to boot into recovery. If you see white screen with "Recovery" text in it, congrats. Everything is working. If not, try again.
Flashing the SuperSU package
Download the zip from SuperSU website
Copy the zip over to the device, with TWRP running
In TWRP, click install, click the zip and confirm the installation.
Factory reset is not required, but you should at least wipe the cache
If this post was useful for you, hit the thanks button

RESERVED

Hi i have a problem here. at the part to drag and drop the openrp file. When i have downloaded the file a drag it and drop it after the install word. The problem is that if I want to drop it there it will do nothing, nothing there shows or anything. Please respond.

I guess you can type the path to the installation file instead of dragging.

Hello,
Very helpful thread, my coolpad Modena 2 (E502) is now rooted.
Don't forget to disable the factory mode once everything is done, or you won't be able to access the storage to usb anymore.
Thanks.

helo, can i get help, when i try to install openrp on abd and fastboot, it printed this message "Failure [INSTALL_FAILED_SHARED_USER_INCOMPATIBLE]"
can anyone help me on that step, so i can root my e502

TCRakt said:
Hello,
Very helpful thread, my coolpad Modena 2 (E502) is now rooted.
Don't forget to disable the factory mode once everything is done, or you won't be able to access the storage to usb anymore.
Thanks.
Click to expand...
Click to collapse
how to disable the factory mode ?? :crying:

Firefa23 said:
how to disable the factory mode ?? :crying:
Click to expand...
Click to collapse
Hello,
If I recall correctly (I don't have the phone anymore, just touched it once to root it at the time), you basically undo the "Enabling factory mode" step.
I think if you dial the number, you'll be back in the menu where you have the option to disable the factory mode.
Factory mode should be disabled when 'DM' is green.
Good luck

very good

Need Custom rom please
nougat / pie

Hello, could you resend the twrp recovery file for this phone again?. old links not work!.
(sorry for my bad english)