Database Info

Need Help rooting and Flashing on Sprint?

Hello. I am sick from school today and decided to make a thread to help out some people.
DOWNLOADS ARE BELOW(AT THE BOTTOM!!!)
All of these steps are posted on TheUnlockr.com in a Video but The video is for the GSM version. The difference is just the recovery image. (http://theunlockr.com/2009/08/27/how-to-root-your-htc-hero-in-one-click/)
Ok lets get started.
This method works on all Sprint phones with updates. I am not sure how long this will last unpatched.
First YOU HAVE TO HAVE ADB WORKING!!!
Download my zip file if you do not want to download the entire SDK.
1)After it is downloaded, extract the files to C:\Windows\System32\
(you can copy and past the file-path)
2) Now pickup your phone and go into Settings-Applications and Enable Unknown Sources then from there go into Development and make sure that USB Debugging is enabled.
3) Now connect your phone to your computer and open up command prompt (Start-Run(or search) cmd.exe.
4)When it is open type: ADB Devices.
You should see your'r phone's serial.
Now download flashrec-1.1.3-20091107-2.apk (the download is below)
1) Copy the file to your sdcard.
2) Download any File Manager from the android market.
3) Go to your Sdcard in the file manager app on your phone.
4) Press flashrec-1.1.3-20091107-2.apk
Let it install.
5) When it is complete, go to your apps drawer and open the Recovery Flasher app.
My method requires you to have a recovery image before root.
6) In the recovery flasher app, Press Backup Recovery Image
7) Let it work. You may have to try twice for Success.
8) Now Mount your phone back on the computer and replace the recovery-backup.img with the recovery-backup.img on this thread(MAJOR thanx to Amon_RA)
9) Now unmount your phone and go back into the Recovery Flasher app on your phone.
10) Now press restore and let it flash recovery-RA-heroc-v1.2.3.img(Amon_RA's Sprint custom recovery image)
YOU NOW HAVE A CUSTOM RECOVERY IMAGE!!! WOOT WOOT
the work is still not done.
Download the Superuser.zip(http://forum.xda-developers.com/attachment.php?attachmentid=211569&d=1249225060 or in the downloads below) and extract it to your Sdcard
Now go into your new recovery image (power off the phone and then power it on by holding the Power and Home buttons)
Connect your phone to a computer and run command prompt.
IN COMMAND PROMPT TYPE:
Code:
adb shell
mount /sdcard
mount /system
cp /sdcard/su /system/bin/
chmod 4755 /system/bin/su
cp /sdcard/Superuser.apk /system/app/
reboot
(you can copy and past the code into command prompt from the thread)
Download the Better Terminal Emulator app from the market and type:
Code:
$ su
if you get a
Code:
#
then...YOU NOW HAVE ROOT!!
now you can install custom ROMs and root-required apps
FlashREC(Recovery Flasher): http://zenthought.org/system/files/asset/2/flashrec-1.1.3-20091107-2.apk
Amon RA's Sprint Recovery: http://www.mediafire.com/file/uozzgzmmnym/recovery-backup.img
Superuser.zip: http://www.mediafire.com/file/3mddanwztzd/superuser.zip
ADB and Fastboot(for those who need it): http://www.mediafire.com/file/tyib2wmomym/ADB_Fastboot.zip

[GUIDE] How To Root The Sprint CDMA Hero (Windows)

I have compiled this guide from the other one posted on this forum, the discussion therein, and my own knowledge. If you have any suggestions on making it better or to correct any mistakes I may have made please let me know.
This guide is intended for Windows and includes detailed instructions. It will cover the steps necessary to root, flash the new recovery image, create a full backup. This will work with software versions 1.29.651.1 and 1.56.651.2 (aka Android 1.5). If you have updated to 2.1 please following this guide here. I am not responsible for any damage done to your phone using this guide. Root at your own risk.
I have put to together a video on YouTube for you to follow along as well. The version numbers of certain files are now outdated in the video so change file names as necessary.
If you own a non-Sprint Hero, you will need to do some extra steps. Follow the guide in the How to Root Non-Sprint CDMA Hero thread.
Step 1: Download the Android SDK from http://developer.android.com/sdk/index.html The Windows file is called android-sdk_r06-windows.zip. Extract the files to your C: drive so that you now have the folder C:\android-sdk-windows
Step 2: Download the asroot2 exploit file from http://forum.xda-developers.com/attachment.php?attachmentid=244212&d=1257621154 Extract asroot2.zip to C:\android-sdk-windows\tools folder.
Step 3: Download the Hero recovery image from http://forum.xda-developers.com/showpost.php?p=4898505&postcount=1g Place this file in C:\android-sdk-windows\tools as well.
Step 4: Make sure USB Debugging is off by going to Settings>Applications>Development. Now connect the phone to your PC via USB cable.
Step 5: Mount your sdcard; Browse to the HTC Sync folder and install HTC Sync on your pc. After it is done installing unmount the sdcard then enable your USB debugging.
Step 6: Open a command prompt by clicking the Start button and typing cmd into the search box and pressing enter or found under All Programs>Accessories.
Step 7: You will now enter a series of commands which I will place inside code boxes to indicate the entire command. You may copy and then paste them into the command prompt window by right clicking. Only enter one command at a time.
1:
Code:
cd C:\android-sdk-windows\tools
2:
Code:
adb devices
If you've been following this guide you will see your phone's serial number. If you get "device not found" error, you either need to make sure you the drivers were properly installed or make sure you enable USB debugging AFTER you connect the USB cable. Continue on once you get the proper phone serial output.
3:
Code:
adb push asroot2 /data/local/
4:
Code:
adb shell
5:
Code:
chmod 0755 /data/local/asroot2
6:
Code:
/data/local/asroot2 /system/bin/sh
You should see an output that says:
$ /data/local/asroot2 /system/bin/sh
[+] Using newer pope_inode_info layout
Opening: /proc/857/fd/3
SUCCESS: Enjoy the shell.
#​Now for a few last commands.
7:
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
8:
Code:
cd /system/bin
9:
Code:
cat sh > su
10:
Code:
chmod 4755 su
You are now officially rooted. A few more steps and you will have flashed the recovery image.
11:
Code:
exit
12:
Code:
exit
13:
Code:
adb push recovery-RA-heroc-v1.6.2.img /sdcard
Pushing is equivalent of copy the file to the root of your sdcard. By the time you finished reading this it should be done. You'll know its done because the ouput will say something like transferred X bytes in X secs.
14:
Code:
adb shell reboot
This will cause the phone to restart automatically. Wait till it is fully booted to continue.
15:
Code:
adb shell
16:
Code:
su
17:
Code:
cd /sdcard/
18:
Code:
flash_image recovery recovery-RA-heroc-v1.6.2.img
FLASHING TO THE RECOVERY TAKES SEVERAL SECONDS-- BE PATIENT. ENTER THE NEXT COMMAND ONLY AFTER THE COMMAND PROMPT RETURNS TO THE # (ROOT SYMBOL).
19:
Code:
reboot recovery
Step 8: This is the last command; you may now close the cmd prompt. This will cause your phone to boot into recovery mode; it should take no longer than 30 secs. The third option on the list is "- Backup/Restore"; select it. Now, select the first option "- Nand backup". The phone will prompt you to press HOME to confirm which is want you want to do. The backup will begin. You will see the screen say, "Performing backup : .........." When done, the bottom of the screen will say "Backup complete!" and you will be given the menu options again. Go back to the main menu and select reboot system. Rebooting your phone after installing the new recovery image may take several minutes.
Step 9: Once your phone is fully booted, mount the sdcard. You will see a folder called "nandroid"; I highly recommend you copy this to your pc in case you lose your sdcard data or reformat it. Your phone is rooted, 100% backed up, and ready to install a custom rom if you wish!

wow dude,
instructions worked great on Win7
i was able to download the missing usb_drivers by running SDK Setup in C:\android-sdk-windows, and selecting the usb driver from the available packages. I was unable to download the index for the SDK Setup program until I enabled "force http://" in the settings menu.
had to copy over asroot again after i ran SDK Setup (that program deleted it from the directory)
your instructions worked like a charm. total time spent rooting this thing after finding your post: 18 minutes.
(you might want to add a line there in the "mount and copy over the zip file step" to backup the nandroid folder from your SDCard to your comp just as a backup of your stock phone image)
anyway.. cheers!

izanagi said:
wow dude,
i'm about to follow these instructions. thank's for the precise list!
(btw, about to try it on Win7.. may have to change some folder pathing but we'll see)
okay.. typo on the first command in parentheses, and I'm missing the usb_drivers folder (do you have it / can sent it to me) so am unable to install the device in win7.
Click to expand...
Click to collapse
Heh, thanks for the misspell heads up. I did my rooting from Win7 pc; it automatically installed correct drivers for me. To check go to the Control Panel>View devices and printers. You see one device named "Android Phone". Otherwise as far as Ive heard installing HTC Sync installs proper drivers.​

izanagi said:
*** edit had to copy over asroot again after i ran SDK Setup (that program deleted it from the directory)
**** edit: all done.. your instructions worked like a charm. total time spent rooting this thing after finding your post: 18 minutes.
(you might want to add a line there in the "mount and copy over the zip file step" to backup the nandroid folder from your SDCard to your comp just as a backup of your stock phone image)
anyway.. cheers!
Click to expand...
Click to collapse
Thank you for taking the time help make my guide better. I'm very glad to know there are little to no hiccups.

When I do step 5, instead of:
5. "/data/local/asroot2 /system/bin/sh"
You should see an output that says:
$ /data/local/asroot2 /system/bin/sh
[+] Using newer pope_inode_info layout
Opening: /proc/857/fd/3
SUCCESS: Enjoy the shell.
#
I get:
[1] Killed /data/local/asroot2 /system/bin/sh
Any suggestions? Should I just be quiet until there is an Eris specific way to do this?

When I do step 5, instead of:
5. "/data/local/asroot2 /system/bin/sh"
You should see an output that says:
$ /data/local/asroot2 /system/bin/sh
[+] Using newer pope_inode_info layout
Opening: /proc/857/fd/3
SUCCESS: Enjoy the shell.
#
I get:
[1] Killed /data/local/asroot2 /system/bin/sh
Any suggestions? Should I just be quiet until there is an Eris specific way to do this?

detox702 said:
When I do step 5, instead of:
5. "/data/local/asroot2 /system/bin/sh"
You should see an output that says:
$ /data/local/asroot2 /system/bin/sh
[+] Using newer pope_inode_info layout
Opening: /proc/857/fd/3
SUCCESS: Enjoy the shell.
#
I get:
[1] Killed /data/local/asroot2 /system/bin/sh
Any suggestions? Should I just be quiet until there is an Eris specific way to do this?
Click to expand...
Click to collapse
This guide is for the CDMA Hero not the Eris!

When I go to apply the rom I get an white screen with skateboarding androids on the bottom and the prompt to erase data yes/no. I press the home key and the Hero reboots without asking to "Apply sdcard:choose zip". This is done from the boot menu. Does the rom load automatically? Did I do something wrong? I got root with no problem. A tip; to make it easier and to avoid spelling mistakes copy and paste the rooting commands from the instructions. Made it go faster too. Thanks in advance.
Never mind. I held down Home and Power at
the same time instead of Home THEN power! ARRGH! Loading up now as I type. Sorry.

ELIMINATED said:
When I go to apply the rom I get an white screen with skateboarding androids on the bottom and the prompt to erase data yes/no.
I press the home key and the Hero reboots without asking to "Apply sdcard:choose zip".This is done from the boot menu.
Does the rom load automatically? Did I do something wrong? I got root with no problem.
A tip; to make it easier and to avoid spelling mistakes copy and paste the rooting commands from the instructions. Made it go faster too. Thanks in advance.
Click to expand...
Click to collapse
yuck... break up your sentences, that's alot of crap to throw on someone all at once... and the bold doesn't help it any.
check to see if you have the custom recovery installed....
-turn off phone
-hold vol down + power
-should search for some stuff then give three options
-press "home" to enter recovery image
do you see "!" and a phone.... does it just hang or do you see a green/yellow menu?

At the end of his post he says he figured it out. He wasn't holding down home key

None of this is working for me at all... I'm not sure what I'm doing wrong, but every time I enter ANY of the commands into the prompt all I get is "cannot find the path specified".
For reference, i have done everything in this guide to the letter, everything is downloaded, unzipped to the correct location, USB drivers installed, etc etc. Not sure what's wrong.
EDIT: I figured it out.. user error, awesome. Worked great, thanks for this!

awesomeindeed said:
None of this is working for me at all... I'm not sure what I'm doing wrong, but every time I enter ANY of the commands into the prompt all I get is "cannot find the path specified".
For reference, i have done everything in this guide to the letter, everything is downloaded, unzipped to the correct location, USB drivers installed, etc etc. Not sure what's wrong.
EDIT: I figured it out.. user error, awesome. Worked great, thanks for this!
Click to expand...
Click to collapse
"cd C:\android-sdk-windows\tools" is actually "cd C:\android-sdk_r3-windows\tools"
is that where you are stuck?

thank you TS. I've been lurking xda for a couple years now when i had the mogul and tp. First time on an android device. Thank you for your time in helping me.

someone buy this man a drink!!!
Invaluable piece of work right here, helped me get it done in no time at all....real clear concise and very helpful....REQUEST THIS BE A STICKY!!!!!

fenske09 said:
"cd C:\android-sdk-windows\tools" is actually "cd C:\android-sdk_r3-windows\tools"
is that where you are stuck?
Click to expand...
Click to collapse
That was the name of the zip file not the extracted folder.

Please help, I followed all of your instructions, I received no errors however I can't boot the recovery image. I checked and it is in the sd card, but every time it just hangs at the HTC logo
I downloaded a terminal emulator and typed su and it gave me # so I assuming I am rooted?!

newtodroid said:
Please help, I followed all of your instructions, I received no errors however I can't boot the recovery image. I checked and it is in the sd card, but every time it just hangs at the HTC logo
I downloaded a terminal emulator and typed su and it gave me # so I assuming I am rooted?!
Click to expand...
Click to collapse
Redownload the recovery image and reflash it. The one you're using probably became corrupt during DL or something.

theresthatguy said:
Redownload the recovery image and reflash it. The one you're using probably became corrupt during DL or something.
Click to expand...
Click to collapse
also make sure you have the heroc version there's a hero and heroC, i messed that up once and had similar results

new ROM
So i loaded the custom ROM, and i followed all the istructions as listed on this guide. When i rebooted my phone, a bunch of my apps started Force Closing on startup.
did i miss something, or do something wrong?
if i reinstall them on the new ROM will they work right?
thanks for any insight

kristaps said:
So i loaded the custom ROM, and i followed all the istructions as listed on this guide. When i rebooted my phone, a bunch of my apps started Force Closing on startup.
did i miss something, or do something wrong?
if i reinstall them on the new ROM will they work right?
thanks for any insight
Click to expand...
Click to collapse
you converted your sd card to fat32,ext2,swap and now the apps are looking for the program on your sd card,
turn off your phone
take out sd card
turn on phone
uninstall app
turn off phone
put in sd card
turn on phone
reinstall app
this should fix you

adfree android

now that we have an easy way to push update.zip files I was wondering if there was any way to push the host file that adfree android downloads to the sdcard. I know that it doesn't have write access to the system partition when booted but in recovery we do right?
So it should be as simple as creating an update.zip that overwrites the old host right?
I'm going to try to get this working
EDIT: Here's how to get this working
1. Search for Adfree Android on the market
2. Install and run
3. allow it to download and install new hosts file, it will copy it to your sdcard and try to replace /system/etc/hosts but fail (it should reboot the phone shortly)
4. Power off the phone and hold Volume Down and power.
5. Use volume down to select recovery
6. In clockwork recovery volume down to "partitions menu" and hit the track pad to select
7. Select "mount /system" and "mount /sdcard" "mount /data"
8. Plug in your usb cord and open a command line on your pc
9. enter adb shell and type the following commands
cp /sdcard/hosts /data/data/hosts
rm /system/etc/hosts
ln -s /data/data/hosts /system/etc/hosts
10. Reboot your phone and enjoy adfree android.
Thanks to all for help in getting this running.

Just adb push your modified host file to /system/etc/hosts. No need for update.zip

ive already done this doesnt work still have tons of adds

word, I figured it out

junjlo said:
ive already done this doesnt work still have tons of adds
Click to expand...
Click to collapse
what I did was install adfree android, wait for it download and error (the phone will reboot itself) put it into recovery and run the following command from adb shell
cp /sdcard/hosts /system/etc
All my ads are gone

You mind sharing the host file? I'd like to do the same. Now that I can connect as root with 'adb shell' then 'su' after the new Unrevoked^2 root. I'd like to start tweaking with things.

supagene said:
You mind sharing the host file? I'd like to do the same. Now that I can connect as root with 'adb shell' then 'su' after the new Unrevoked^2 root. I'd like to start tweaking with things.
Click to expand...
Click to collapse
just download and install adfree android, it copies the host file to your sdcard.

n0-0ne said:
what I did was install adfree android, wait for it download and error (the phone will reboot itself) put it into recovery and run the following command from adb shell
cp /sdcard/hosts /system/etc
All my ads are gone
Click to expand...
Click to collapse
i may have an older hosts file than but i just used adb push hosts /system/ect/hosts
tryed cp but get a box with busybox info

n0-0ne said:
just download and install adfree android, it copies the host file to your sdcard.
Click to expand...
Click to collapse
I intalled the app and when I hit download and intall I get java/io.FileNotFoundException:/sdcard/hosts
My guess is that it's not downloading.
Tried it on both WiFi and 3G

supagene said:
I intalled the app and when I hit download and intall I get java/io.FileNotFoundException:/sdcard/hosts
My guess is that it's not downloading.
Tried it on both WiFi and 3G
Click to expand...
Click to collapse
ok well here's what was downloaded to my card
https://www.yousendit.com/transfer.php?action=batch_download&batch_id=K0JRUGhYT2JQb0t4dnc9PQ
Thats good for 100 downloads.

Found this. forum.xda-developers.com/showthread.php?t=664532 do you guys know if the zip file with hosts good enough since I can't seem to get the AdFree app to work correctly? Of is there an apk somewhere for this app and I shouldn't have gotten the one in the app store?

host installed still doesnt block ever ad using tikl and fring to test

supagene said:
Found this. forum.xda-developers.com/showthread.php?t=664532 do you guys know if the zip file with hosts good enough since I can't seem to get the AdFree app to work correctly? Of is there an apk somewhere for this app and I shouldn't have gotten the one in the app store?
Click to expand...
Click to collapse
I used the one from the market, it does error but it should copy the hosts file to your SD card (and reboot your phone shortly thereafter).

What now?
Great...
cat /sdcard/hosts > /system/etc/hosts
write: No space left on device

junjlo said:
host installed still doesnt block ever ad using tikl and fring to test
Click to expand...
Click to collapse
I've tested both apps and no ads in either.
The one thing I did different that I didn't post was in recovery under partitions I mounted both system and sdcard. Try that and copy the file over.

Thanks!!
So I downloaded the hosts file, booted in recovery, mounted both /system and /sdcard and then 'adb shell' and 'su' and then 'cd /system/etc' and then 'cat /sdcard/hosts > hosts' and it seemed to have worked.
I go to fring and it displays 'Web page not available', not what I'd like to see but it's better than those retarded ads that I keep clicking on by accident.

can someone post step by step how to get adfree working I installed the one from the market and let it error and reboot then i entered into clockworkmod recovery now what? do i need to mount system and sd how do i enter into adb shell and change host file. thanks in advance for any help.

supagene said:
So I downloaded the hosts file, booted in recovery, mounted both /system and /sdcard and then 'adb shell' and 'su' and then 'cd /system/etc' and then 'cat /sdcard/hosts > hosts' and it seemed to have worked.
I go to fring and it displays 'Web page not available', not what I'd like to see but it's better than those retarded ads that I keep clicking on by accident.
Click to expand...
Click to collapse
Glad it worked out, not sure why your getting page not available, I just get a blank box at the top of my contacts list, other apps show the same as well, a blank box where the ad used to be.

j1000 said:
can someone post step by step how to get adfree working I installed the one from the market and let it error and reboot then i entered into clockworkmod recovery now what? do i need to mount system and sd how do i enter into adb shell and change host file. thanks in advance for any help.
Click to expand...
Click to collapse
Edited OP.

thanks for the quick response everything is good until step 8. I know i sound stupid but i learning fast you say enter adb shell. the way i think you do this is type
1. cd\
2. cd sdk
3. cd tools
4. adb shell
when i do this i get error device not found
can you help from there. thanks

Android 2.3 (CM7) Font Replacement

Hey guys, I have a similar thread to this running on both CyanogenModForums and TypoPhile, but it seems as though I'm not going to find the help I need.
When I go to replace the fonts, I use two different methods. Both have ended in a bootloop for me as of 7RC2. I even know why the bootloop is happening, I just have no idea how to fix it.
The first method is in the terminal. For this to work, you need root (obviously), busybox, a terminal emulator and the fonts:
su
mount -o remount /dev/block/mtdblock4 /system
busybox cp /sdcard/Fonts/* /system/fonts
mount -o ro,remount /dev/block/mtdblock4 /system
sync
reboot
Unfortunately, the second mount command fails. It throws the error: filesystem is busy (not an exact quote because I don't really want to reboot to recovery again right now). Because it never remounts as r/o, the writing never gets done correctly and the system bootloops.
The second method is through Root Explorer.
I mount /system as r/w and then proceed to copy my fonts over (I've tried both using multi-select and copying one-by-one). Then, when I click mount R/O, I get the same problem. It won't remount. Therefore, same thing happens and bootloop ensues upon reboot.
Though I cannot imagine that it would matter, the fonts I am trying to use are as follows:
Liberation Sans => Droid Sans (Rg, Bd)
Terminus => Droid Sans Mono
Linux Libertine G => Droid Serif (Rg, It, Bd & BI)
I say that it shouldn't matter because this is exactly what I had for a very long time on 6.1.
I suspect that the problem may be coming from the fact that since 2.3, Android changed how the /system/fonts folder is setup, and I'm not sure how to handle the changes. If anyone is familiar at all with this, I would much appreciate any and all help you can send my way!

Bump. Please guys, any ideas are welcome. I really want to get to the bottom of this. Typographers are people too!

Same here, anyone has found something ?
ok I found that on CM7 forum :
Method 1: The Terminal Emulator
For this, you need root (obviously), busybox, a terminal emulator, ROM Manager and your fonts: They must already be renamed to which fonts you want them to replace (e.g., you could rename LiberationSans to DroidSans in order to use LibSans instead. For easiness, don't have any spaces in your pathname)
Step 1:
su
mount -o remount /dev/block/mtdblock4 /system
busybox cp /sdcard/[Font Dir]/* /system/fonts #Replace "[Font Dir]" with where ever you put your fonts (minus the "")
mount -o ro,remount /dev/block/mtdblock4 /system
sync
Step 2: If the second mount command does not work, try "umount -f /dev/block/mtdblock4" without the quotes. If that doesn't work, then you just have to hope that it will work anyways. If the second mount command succeeds, then you're done. It worked and your phone should now be using the new fonts. Skip to Method 1 > Step 4.
Step 3: Next, go into ROM Manager, and press the "Fix Permissions" option. Wait for it to finish going through everything, and then reboot. If your device bootloops, then something went wrong that ROM Manager's Permissions Corrector couldn't catch. In this case, I strongly recommend purchasing Root Explorer and giving it a go because Method 2 hasn't ever failed for me.
Step 4: If everything worked fine, then your fonts will already be used by the system (you don't even need to reboot!). However, if you now plan to backup your ROM, make sure that you reboot once first to make sure that the fonts survive and your system doesn't bootloop upon reboot.
Method 2: Root Explorer (Recommended)
For this method, you need root, possibly busybox (but I'm actually not sure about that), Root Explorer, ROM Manager and the fonts setup the same way they would have been for Method 1.
Step 1: Enter into Root Explorer and navigate to the fonts folder on your sdcard that has all of the renamed fonts. Press Menu > Multi-Select and select all of the fonts you wish to use. Then press "copy."
Step 2: Next, navigate to /system/fonts/ and press "Mount R/W" at the top of the screen. Press "Paste."
Step 3: Now comes the tedious part, long-press each file you replaced individually and select "Permissions." The permission set you want for each of these files is "r-xr-xr-x." So the first and last column should all be checked and the middle column should be empty. You can try to press "Mount R/O" at the top of the screen, but if it won't change, it will still be okay (It's not ideal, but it's happened to me, and it worked fine).
Step 4: Next, go into ROM Manager and hit the "Fix Permissions" option. Wait for it to go through everything and then "Voila!"
Step 5: If everything worked fine, then your fonts will already be used by the system (you don't even need to reboot!). However, if you now plan to backup your ROM, make sure that you reboot once first to make sure that the fonts survive and your system doesn't bootloop upon reboot.

[HTC EXPLORER] Flash back to Yannou90's recovery after flashing CWM

The official CWM has problems in mounting SD-EXT, thus, Jaggyrom and other custom roms (except stock) won't work properly and your phone will reboot everytime you install apps. You'll also get a lot of app crashes because Dalvik cache can't move properly. Now here's how to flash back to Yannou90's recovery using only Android Terminal Emulator.
__________
THINGS YOU NEED:
1. Your HTC Explorer must be rooted
2. Flash_image and Recovery (You can download it here on this thread)
3. Root File Explorers (Like Root Explorer and ES File Manager, at play store)
STEPS:
1. Download the zip file, read the readme inside the zip, and extract flash_image and recovery.img to the root of your SD Card
2. Download Root Explorer from play store, you can use ES file explorer if you want a root file explorer for free
3. Using your root explorer, copy flash_image to /system/bin/ but before you do that, make sure you mount /system/bin/ as R/W.
4. After copying flash_image, set flash_image permissions to rwxrwxrwx
5.Download Android Terminal Emulator on Play store
6. Run Terminal Emulator and open up preferences.
7. at the initial command, put this:
export PATH=/system/bin:$path
7. Go back to Terminal and Type su
8. Superuser should prompt. Accept it.
9. If you saw # it means you are running it as root, which is that we really needed. If you saw $ , it's not running as root and do type su again.
10. now type this:
flash_image recovery /sdcard/recovery.img
11. Wait for it and if it's done, boot your phone to recovery.
12. CONGRATULATIONS AND YOU ARE BACK TO YANNOU90's RECOVERY
DOWNLOAD LINK:
Flash_Image and Recovery.zip

mrchezco1995 said:
......
2. Flash_image and Recovery (You can download it here on this thread)
......
Click to expand...
Click to collapse
Sorry, on trying to download the following message shows up.
"The page you have requested does not exist. Please check your spelling and try again."
Can you please re-upload the Flash_image and Recovery.zip ?

Download link 404..
Sent from my HTC desire_HD using xda app-developers app

beegeevee said:
Sorry, on trying to download the following message shows up.
"The page you have requested does not exist. Please check your spelling and try again."
Can you please re-upload the Flash_image and Recovery.zip ?
Click to expand...
Click to collapse
Deivi_Z said:
Download link 404..
Sent from my HTC desire_HD using xda app-developers app
Click to expand...
Click to collapse
Download link fixed. Uploaded it to mediafire instead. Thanks for reminding guys.

permission denied
followed all the steps....still got the "Permission Denied" message

followed all the steps....still got the "Permission Denied" message
Click to expand...
Click to collapse
Check superuser and make sure Terminal is allowed. And type su in all lowercase, not uppercase like SU. That wont work
Sent from my HTC Explorer using XDA

mrchezco1995 said:
The official CWM has problems in mounting SD-EXT, thus, Jaggyrom and other custom roms (except stock) won't work properly and your phone will reboot everytime you install apps. You'll also get a lot of app crashes because Dalvik cache can't move properly. Now here's how to flash back to Yannou90's recovery using only Android Terminal Emulator.
__________
THINGS YOU NEED:
1. Your HTC Explorer must be rooted
2. Flash_image and Recovery (You can download it here on this thread)
3. Root File Explorers (Like Root Explorer and ES File Manager, at play store)
STEPS:
1. Download the zip file, read the readme inside the zip, and extract flash_image and recovery.img to the root of your SD Card
2. Download Root Explorer from play store, you can use ES file explorer if you want a root file explorer for free
3. Using your root explorer, copy flash_image to /system/bin/ but before you do that, make sure you mount /system/bin/ as R/W.
4. After copying flash_image, download Android Terminal Emulator on Play store
5. Run Terminal Emulator and open up preferences.
6. at the initial command, put this:
export PATH=/system/bin:$path
7. Go back to Terminal and Type su
8. Superuser should prompt. Accept it.
9. If you saw # it means you are running it as root, which is that we really needed. If you saw $ , it's not running as root and do type su again.
10. now type this:
flash_image recovery /sdcard/recovery.img
...
After this step what I get is as follows
usage: flash_image partition file.img
sh-3.2#
Click to expand...
Click to collapse

Superuser worked fine on terminal. But also got permission denied on last command in terminal.. should I push it via ADB?

You can simply flash the recovery using fastboot. Download this ZIP: http://forum.xda-developers.com/attachment.php?attachmentid=913094&d=1329843100 (courtesy of jaggyjags), start your phone in fastboot mode (ROM Manager might be able to reboot your phone into this mode, otherwise just turn it off, pull out the battery and replace it, then turn on while holding volume down and choose "FASTBOOT" from the menu that appears), then run "recovery.bat" from inside the ZIP. It's simpler than having to mess with adding files to /system/bin.
FYI, you need to set permissions on flash_image to allow it to be executed. I think typing this in the terminal emulator should work:
Code:
chmod 777 /system/bin/flash_image
(otherwise use your file manager to change the permissions to give read, write and execute permissions to all users i.e. tick all the boxes). This is the missing step from your guide to make it work from terminal emulator.
Also, you don't need multiple apps, you can just use terminal emulator for it all by using the "cp" command e.g. if flash_image is on the root of your SD card, use the following commands:
Code:
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cp /sdcard/flash_image /system/bin/flash_image
then use the chmod command above and then the original command from the first post.
[BTW, if you're wondering, the first command identifies as root, the second remounts /system as RW, the last copies the file]
So the full process for terminal emulator ONLY, would be this:
Code:
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cp /sdcard/flash_image /system/bin/flash_image
chmod 777 /system/bin/flash_image
flash_image recovery /sdcard/recovery.img
{rm /sdcard/flash_image
rm /sdcard/recovery.img}
The commands in the {} are optional and just delete the two files from your SD card. The 2nd and 3rd commands can be excluded if you copy flash_image with a root capable file manager, as can the 4th if you change permissions with the file manager.
(This post ended up being much longer than I originally intended. I was just going to post the first paragraph, but figured I may as well post how to make it work the way the OP described as well - or at least what I think should make it work, I haven't actually tested the full process [I have tested the exact same process with other binaries {viewmem, tcpdump} and it works perfectly. Provided the usage of flash_image as in the OP is correct and works, this method will work])
EDIT: You also shouldn't have to change the initial command, /system/bin is already specified in $PATH. If it wasn't, pretty much nothing on the phone will work.

SifJar said:
You can simply flash the recovery using fastboot. Download this ZIP: http://forum.xda-developers.com/attachment.php?attachmentid=913094&d=1329843100 (courtesy of jaggyjags), start your phone in fastboot mode (ROM Manager might be able to reboot your phone into this mode, otherwise just turn it off, pull out the battery and replace it, then turn on while holding volume down and choose "FASTBOOT" from the menu that appears), then run "recovery.bat" from inside the ZIP. It's simpler than having to mess with adding files to /system/bin.
FYI, you need to set permissions on flash_image to allow it to be executed. I think typing this in the terminal emulator should work:
Code:
chmod 777 /system/bin/flash_image
(otherwise use your file manager to change the permissions to give read, write and execute permissions to all users i.e. tick all the boxes). This is the missing step from your guide to make it work from terminal emulator.
Also, you don't need multiple apps, you can just use terminal emulator for it all by using the "cp" command e.g. if flash_image is on the root of your SD card, use the following commands:
Code:
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cp /sdcard/flash_image /system/bin/flash_image
then use the chmod command above and then the original command from the first post.
So the full process for terminal emulator ONLY, would be this:
Code:
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cp /sdcard/flash_image /system/bin/flash_image
chmod 777 /system/bin/flash_image
flash_image recovery /sdcard/recovery.img
{rm /sdcard/flash_image
rm /sdcard/recovery.img}
The commands in the {} are optional and just delete the two files from your SD card. The 2nd and 3rd commands can be excluded if you copy flash_image with a root capable file manager, as can the 4th if you change permissions with the file manager.
(This post ended up being much longer than I originally intended. I was just going to post the first paragraph, but figured I may as well post how to make it work the way the OP described as well - or at least what I think should make it work, I haven't actually tested the full process [I have tested the exact same process with other binaries {viewmem, tcpdump} and it works perfectly. Provided the usage of flash_image as in the OP is correct and works, this method will work])
EDIT: You also shouldn't have to change the initial command, /system/bin is already specified in $PATH. If it wasn't, pretty much nothing on the phone will work.
Click to expand...
Click to collapse
Thank You. U completed this thread. Decided to use fastboot (faster) instead of terminal emulator way.

SifJar said:
You can simply flash the recovery using fastboot. Download this ZIP: http://forum.xda-developers.com/attachment.php?attachmentid=913094&d=1329843100 (courtesy of jaggyjags), start your phone in fastboot mode (ROM Manager might be able to reboot your phone into this mode, otherwise just turn it off, pull out the battery and replace it, then turn on while holding volume down and choose "FASTBOOT" from the menu that appears), then run "recovery.bat" from inside the ZIP. It's simpler than having to mess with adding files to /system/bin.
FYI, you need to set permissions on flash_image to allow it to be executed. I think typing this in the terminal emulator should work:
Code:
chmod 777 /system/bin/flash_image
(otherwise use your file manager to change the permissions to give read, write and execute permissions to all users i.e. tick all the boxes). This is the missing step from your guide to make it work from terminal emulator.
Also, you don't need multiple apps, you can just use terminal emulator for it all by using the "cp" command e.g. if flash_image is on the root of your SD card, use the following commands:
Code:
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cp /sdcard/flash_image /system/bin/flash_image
then use the chmod command above and then the original command from the first post.
So the full process for terminal emulator ONLY, would be this:
Code:
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cp /sdcard/flash_image /system/bin/flash_image
chmod 777 /system/bin/flash_image
flash_image recovery /sdcard/recovery.img
{rm /sdcard/flash_image
rm /sdcard/recovery.img}
The commands in the {} are optional and just delete the two files from your SD card. The 2nd and 3rd commands can be excluded if you copy flash_image with a root capable file manager, as can the 4th if you change permissions with the file manager.
(This post ended up being much longer than I originally intended. I was just going to post the first paragraph, but figured I may as well post how to make it work the way the OP described as well - or at least what I think should make it work, I haven't actually tested the full process [I have tested the exact same process with other binaries {viewmem, tcpdump} and it works perfectly. Provided the usage of flash_image as in the OP is correct and works, this method will work])
EDIT: You also shouldn't have to change the initial command, /system/bin is already specified in $PATH. If it wasn't, pretty much nothing on the phone will work.
Click to expand...
Click to collapse
Mine worked for me on terminal without any problems, but thanks for filling up what I just missrf for others. Hehe
Sent from my HTC Explorer using XDA

mrchezco1995 said:
10. now type this:
flash_image recovery /sdcard/recovery.img
11. Wait for it and if it's done, boot your phone to recovery.
]
Click to expand...
Click to collapse
I did upto this point when I write and enter this string nothing happens it gives me another sh-3.2# to write in. How would I know that the Yannou90 recovery has completed??? I'm stuck

SherazHashmi said:
I did upto this point when I write and enter this string nothing happens it gives me another sh-3.2# to write in. How would I know that the Yannou90 recovery has completed??? I'm stuck
Click to expand...
Click to collapse
Why don't you try step 3 from jaggyjag's rooting tutorial....
Sent from my HTC Explorer A310e using xda app-developers app

My HTC Explorer's recovery was stuck green logo, but what thing that helped to get back my clockword recovery
is just downloading you recovery file and renamed it recovery.img
And...
I used Android SDK tool, and used the below command in command prompt and then I reboot the mobile, and I got back:
fastboot flash recovery recovery.img
Thanks for this valuable thread

SU not found !
after changing the INITIAL COMMAND
i restarted d terminal and now the initial command just gets printed and after that i typed 'su'...d output was 'su not found'..
wats d problem ???
I even tried d fastboot method...dats epic, whenever i try to install any .zip from it dis is wat i see
"Installing update...
Installation aborted."
Plz suggest nythng else other than REFLASHING it...its just that sumthng is restricting it to install :laugh:

hi! I have a question regarding recoveries... i have a recovery by yannou90 installed on my htc explorer, will this recovery work for other roms such as CM9 and CM10? It worked well with JaggyJags rom (3.2.1).. i am wondering if I need to switch to other recovery prior to installing CM roms.. thanks!

iamwin said:
hi! I have a question regarding recoveries... i have a recovery by yannou90 installed on my htc explorer, will this recovery work for other roms such as CM9 and CM10? It worked well with JaggyJags rom (3.2.1).. i am wondering if I need to switch to other recovery prior to installing CM roms.. thanks!
Click to expand...
Click to collapse
Yeah, ll work for all rom installation...
Hit :thumbup: if i helped...

R. SAINT said:
Yeah, ll work for all rom installation...
Hit :thumbup: if i helped...
Click to expand...
Click to collapse
got it man!

the steos for flashing the recovery worked for me but after 2 weeks now it responds to nothing when i try to wipe dalwik cache or perform any other funtion it displays nothing only the green title saying yonnou90 recovery.

Mayank T said:
the steos for flashing the recovery worked for me but after 2 weeks now it responds to nothing when i try to wipe dalwik cache or perform any other funtion it displays nothing only the green title saying yonnou90 recovery.
Click to expand...
Click to collapse
My initial response to such a situation would be start the phone in fastboot mode and then flash the recovery from there. Download the ZIP here: http://forum.xda-developers.com/attachment.php?attachmentid=913094&d=1329843100, extract it and double click "recovery.bat" once the phone is in fastboot mode (start phone holding volume down, select fastboot from menu instead of recovery).
This assumes you're on Windows. If you're on Mac/Linux, find the fastboot binary for your platform and run the following command in a terminal:
Code:
./fastboot flash recovery recovery.img
where recovery.img is taken from the ZIP I linked above.
Alternatively, you could install a more up-to-date recovery such as TWRP or a newer build of CWM (not sure of links for the latest versions of either, but have a look around the forum and you should find them. Also some older builds of CWM had bugs [hence this thread exists], but I think the newer builds work fine on the Explorer; not 100% sure as I still use yannou90's build)