Database Info

Question about rooting and flashing recovery image..

Just curious, what happens if I follow the rooting steps in the other thread but only do this:
adb push /directory_you_placed_asroot2/asroot2 /data/local/
adb shell
chmod 0755 /data/local/asroot2
/data/local/asroot2 /system/bin/sh
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd /system/bin
cat sh > su
chmod 4755 su
At this point, what state is the phone in? Do I have full root access to the file system? What are the issues/concerns if I don't proceed with flashing the recovery image. Just trying to understand the process and what each step is for. I understand the part above but can't understand why you have to flash a recovery image and can't just use the phone after root is achieved.
Thanks in advance. FYI...all I want to do with root access is delete some system files, nothing more.

mobilehavoc said:
Just curious, what happens if I follow the rooting steps in the other thread but only do this:
adb push /directory_you_placed_asroot2/asroot2 /data/local/
adb shell
chmod 0755 /data/local/asroot2
/data/local/asroot2 /system/bin/sh
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd /system/bin
cat sh > su
chmod 4755 su
At this point, what state is the phone in? Do I have full root access to the file system? What are the issues/concerns if I don't proceed with flashing the recovery image. Just trying to understand the process and what each step is for. I understand the part above but can't understand why you have to flash a recovery image and can't just use the phone after root is achieved.
Thanks in advance. FYI...all I want to do with root access is delete some system files, nothing more.
Click to expand...
Click to collapse
You don't have to flash the recovery image. I believe from that code you would have root and can run programs that require root. However, you would be unable to flash a new rom or any other update.zip (which means no auto apps2sd), partition your sd card easily or backup your phone in case something goes wrong. I suppose you are probably just asking for the sake of asking and knowledge but this is why a recovery image is HIGHLY recommended.

chuckhriczko said:
You don't have to flash the recovery image. I believe from that code you would have root and can run programs that require root. However, you would be unable to flash a new rom or any other update.zip (which means no auto apps2sd), partition your sd card easily or backup your phone in case something goes wrong. I suppose you are probably just asking for the sake of asking and knowledge but this is why a recovery image is HIGHLY recommended.
Click to expand...
Click to collapse
thanks. So if I don't flash the recovery image, I can't update to cooked ROMs or do the stuff you suggested but will the phone otherwise function normal? i.e. I can update to a Sprint/HTC update, I can factory reset the phone (assuming that'll kill root), etc.? I may do the whole process with the recovery image later but don't need it right now.
I only need to do this as a stopgap until Sprint/HTC releases an update.

mobilehavoc said:
thanks. So if I don't flash the recovery image, I can't update to cooked ROMs or do the stuff you suggested but will the phone otherwise function normal? i.e. I can update to a Sprint/HTC update, I can factory reset the phone (assuming that'll kill root), etc.? I may do the whole process with the recovery image later but don't need it right now.
I only need to do this as a stopgap until Sprint/HTC releases an update.
Click to expand...
Click to collapse
Well, I wouldnt recommend doing a sprint update either. That will cause you to lose root most likely. The only way then to keep root is wait until we get a dump of the update and then cook a rom that includes root, in which case you would need to flash the recovery image. Updates usually fix the exploits we use to gain root.

chuckhriczko said:
Well, I wouldnt recommend doing a sprint update either. That will cause you to lose root most likely. The only way then to keep root is wait until we get a dump of the update and then cook a rom that includes root, in which case you would need to flash the recovery image. Updates usually fix the exploits we use to gain root.
Click to expand...
Click to collapse
What he said...but yes, at the steps you quoted, mobilehavoc, you are capable of root access (you don't actually have it until you run that "su" command ). That allows you to read and modify otherwise locked away files and tweak to your hearts content!

Ive rooted and played around some but very little and followed everyones instructions very closely ( thank you for teaching a newbie ). Now how do I go back to original state that I backed up ( think I did ).
When I press the power and volume down button I get to the droid on skateboard, then I press the Home for recovery. I get the screen with all the options and I go to nandroid v2.2 restore and press trackball. It says restore latest backup press home to confirm. I do that and get the following error
Error : run 'nandroid-mobile.sh restore' via console.
What does this mean? Do i have to be tethered to PC and run this command from cmd prompt?
I am now lost again, any help is appreciated

Grinder16 said:
Ive rooted and played around some but very little and followed everyones instructions very closely ( thank you for teaching a newbie ). Now how do I go back to original state that I backed up ( think I did ).
When I press the power and volume down button I get to the droid on skateboard, then I press the Home for recovery. I get the screen with all the options and I go to nandroid v2.2 restore and press trackball. It says restore latest backup press home to confirm. I do that and get the following error
Error : run 'nandroid-mobile.sh restore' via console.
What does this mean? Do i have to be tethered to PC and run this command from cmd prompt?
I am now lost again, any help is appreciated
Click to expand...
Click to collapse
Just to confirm since it wasn't mentioned, you did a Nandroid backup earlier right? can you confirm that there's a folder on your sdcard called "nandroid"?

thecodemonk said:
Just to confirm since it wasn't mentioned, you did a Nandroid backup earlier right? can you confirm that there's a folder on your sdcard called "nandroid"?
Click to expand...
Click to collapse
Dont see that folder - I guess that is not good. Any ideas?

Grinder16 said:
Dont see that folder - I guess that is not good. Any ideas?
Click to expand...
Click to collapse
You must do a backup BEFORE you can do a restore..

To clarify for everyone, here's a breakdown of the steps:
adb push /directory_you_placed_asroot2/asroot2 /data/local/
This copies the asroot2 program to the /data/local folder on your phone.
adb shell
This logs you into the phone. From here on out, you are no longer executing Windows commands from a DOS shell - you are actually executing Linux commands on the phone.
chmod 0755 /data/local/asroot2
This changes the permissions on the asroot2 program so that it can be executed.
/data/local/asroot2 /system/bin/sh
This actually runs the root exploit and creates a file called /system/bin/sh that we will later turn into su.
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
This unmounts the /system partition and remounts it as writeable.
cd /system/bin
This puts you into the /system/bin folder.
cat sh > su
This creates the su program.
chmod 4755 su
This changes the persmissions on the su file to allow it to be executed.

theresthatguy said:
You must do a backup BEFORE you can do a restore..
Click to expand...
Click to collapse
I thought I had. What are the steps? I have a flash recovery image on my SD card. I have followed all instructions that I could find

Grinder16 said:
I thought I had. What are the steps? I have a flash recovery image on my SD card. I have followed all instructions that I could find
Click to expand...
Click to collapse
Boot to the recovery image then select "nandroid backup"

jonnythan said:
Boot to the recovery image then select "nandroid backup"
Click to expand...
Click to collapse
Can you provide those steps? Sorry but complete newbie here

"I get the screen with all the options and I go to nandroid v2.2 restore and press trackball. It says restore latest backup press home to confirm. I do that and get the following error"
Go there but select Backup instead of Restore.
Turn the phone off, hold the Home key, and turn it on. When you get to the screen with the green text select nandroid backup.

[Q] Flashed 2.3.3 Radio- No Service

I have 2.3.3 rooted from a backup without the new radio.
I backed up abd decided to install the new Radio from:
http://forum.xda-developers.com/showthread.php?t=971272
After Installing, I am getting no service and " error while searching for networks ".
I cannot post in the above thread (as it is in Dev. forum), but I tried: *#*#4636#*#* and put CDMA only or GSM only and still no service.
Flashing back to my own nandroid backup does not even solve the problem!
Flashed to 2.3.3 rooted and setup the phone as new and still no service!
Tried the SIM in another Cellphone and it works fine so it is not SIM related bu I noticed that If i Go to the Phone Information Menu via *#*#4636#*#* I cannot turn off the Radio or that If i change the network pref, it remains the same even after flashing!

Maybe I'm misunderstanding you. You rooted 2.3.3 then flash the radio? Did you check the file mud5?
Try extracting the radio and install with fastboot method.

I had 2.3.3 rooted from an image without the new radio.
Tried restoring to the original 2.3.3 img and still no service.

If you have an unlocked bootloader, then perhaps installing the complete rom will do the trick:
http://android.clients.google.com/p...2cf141e6a.signed-soju-ota-102588.f182cf14.zip
You will lose root, but it is simple enough to get back with an unlocked bootloader.

There seems to be some kind of bug with clockwork recovery on 2.3.3 if you reboot the phone you lose it!
I am downloading android SDK and trying to fastboot the recovery so I can actually install any new ROM!
2.3.3 should have worked but It did not, I already have 2.3.3 stock will try to flash it, but it seems a tough problem as the service should have been working after I flashed to earlier versions!

jsaade said:
There seems to be some kind of bug with clockwork recovery on 2.3.3 if you reboot the phone you lose it!
Click to expand...
Click to collapse
The system automatically restores the stock recovery with /etc/install-recovery.sh. You need to rename that file to something else, like install-recovery.sh.old.
It's actually a good idea, it means that if people manage to mess up recovery beyond hope, a reboot will fix it.

No not a good idea at all!
I officially do not know what to do.
I cannot access clockworkmod, tried fastboot -flash to crespo recovery image (which should install clockworkmod) but after I do so and reboot, I am back to stock recovery. so no nandroid backups. stuck on 2.3.3 rooted, the device does not detect the network and wifi is kind of corrupt (would not let me sign in to gmail but everything else works) so I cannot even get Rom Manager as I do not have access to market.
How can I rename the /etc/install-recovery.sh if I cannot go to etc dir?

shrivelfig said:
The system automatically restores the stock recovery with /etc/install-recovery.sh. You need to rename that file to something else, like install-recovery.sh.old.
It's actually a good idea, it means that if people manage to mess up recovery beyond hope, a reboot will fix it.
Click to expand...
Click to collapse
can I rename from the adb shell?
if yes then how (I am new to all this). if i try renaming directly it says permission denied.

jsaade said:
How can I rename the /etc/install-recovery.sh if I cannot go to etc dir?
Click to expand...
Click to collapse
You're rooted, aren't you?
Code:
adb shell
su
cd /etc
mv install-recovery.sh install-recovery.sh.old
or use Root Explorer or Android Terminal Emulator.
jsaade said:
can I rename from the adb shell?
if yes then how (I am new to all this). if i try renaming directly it says permission denied.
Click to expand...
Click to collapse
For one, you need to be super user, secondly, you might need to remount the partition to be read-writable instead of read-only.
Code:
mount -o rw,remount /etc /etc
jsaade said:
I am new to all this
Click to expand...
Click to collapse
This is why install-recovery.sh is a good idea

I am rooted and I have superuser, tried:
Code:
E:\android\sdk\platform-tools>adb shell
$ su
su
cd /etc
cd /etc
mv install-recovery.sh install-recovery.sh.old
mv install-recovery.sh install-recovery.sh.old
Permission denied
$ cd /etc
$ mv install-recovery.sh install-recovery.sh.old
failed on 'install-recovery.sh' - Read-only file system
trying droid explorer next...

The $ prompt means that you are not super user. You need the # prompt. Also, try remounting with
Code:
mount -o rw,remount /etc /etc

shrivelfig said:
The $ prompt means that you are not super user. You need the # prompt. Also, try remounting with
Code:
mount -o rw,remount /etc /etc
Click to expand...
Click to collapse
How am I not a superuser if I have the superuser on the phone?
Code:
E:\android\sdk\platform-tools>adb shell
adb server is out of date. killing...
* daemon started successfully *
$ su
su
Permission denied
$
Anything I can do to fix?

Ok I just noticed when I go to the Bootloader, it says on the top:
fastboot Mode - No Boot or Recovery IMG
even though I just flashed a recovery Image, and when I reboot as I said before it goes back to stock recovery.
Aslo trying to boot the crespo recovery image (as explained in "http://jaxov.com/2011/02/how-to-root-android-2-3-3-gingerbread-on-nexus-s/")
gets me stuck on google logo.
so how can I get su?

jsaade said:
How am I not a superuser if I have the superuser on the phone?
Code:
E:\android\sdk\platform-tools>adb shell
adb server is out of date. killing...
* daemon started successfully *
$ su
su
Permission denied
$
Anything I can do to fix?
Click to expand...
Click to collapse
update your SDK to 2.3.X
hence it says... E:\android\sdk\platform-tools>adb shell
adb server is out of date. killing...
refer to stickies in Dev forum to update SDK if you dont know how to.

I managed to get my backup running.
I still have no service, is there a way I can disable the new Radio?
flashing new rom does not even do anything.

jsaade said:
How am I not a superuser if I have the superuser on the phone?
Code:
E:\android\sdk\platform-tools>adb shell
adb server is out of date. killing...
* daemon started successfully *
$ su
su
Permission denied
$
Anything I can do to fix?
Click to expand...
Click to collapse
When you're in adb shell and run the su command, you have to grant permission for that to happen on the phone. A pop-up gives you the choice between allow and deny.
jsaade said:
I managed to get my backup running.
I still have no service, is there a way I can disable the new Radio?
flashing new rom does not even do anything.
Click to expand...
Click to collapse
How would disabling the radio help you? There is no "old" or "new" radio, there is only the one radio. And what does "not even do anything" mean? Like nothing happened, or error messages or didn't really pay attention?

shrivelfig said:
When you're in adb shell and run the su command, you have to grant permission for that to happen on the phone. A pop-up gives you the choice between allow and deny.
How would disabling the radio help you? There is no "old" or "new" radio, there is only the one radio. And what does "not even do anything" mean? Like nothing happened, or error messages or didn't really pay attention?
Click to expand...
Click to collapse
I do not have service since I updated the radio and flashing new rom does not re-enable the service.
When I try to search for network it says error in search.

jsaade said:
I do not have service since I updated the radio and flashing new rom does not re-enable the service.
When I try to search for network it says error in search.
Click to expand...
Click to collapse
Airplane mode on?
Sim card inserted wrong way?

shrivelfig said:
Airplane mode on?
Sim card inserted wrong way?
Click to expand...
Click to collapse
No, tried different Sims, it was working fine until the Radio Update which messed it up!
The problem is that I cannot revert the update, restoring does not solve the problem.

jsaade said:
No, tried different Sims, it was working fine until the Radio Update which messed it up!
The problem is that I cannot revert the update, restoring does not solve the problem.
Click to expand...
Click to collapse
You can't restore because the radio doesn't get backed up. A typical backup consists of these files:
Code:
boot.img
cache.img
data.img
nandroid.md5
recovery.img
system.img
No radio.img.
You have to flash a new radio image through recovery (update.zip) or fastboot (fastboot flash radio radio.img) or a complete rom update (f182cf141e6a.signed-soju-ota-102588.f182cf14.zip).

2.3.4 rooting/recovery Q

Quick question about rooting and clockwork. I managed to gain root on 2.3.3 without using clockwork a while back (i find it buggy sometimes) but the current re-rooting guide for 2.3.4 assumes clockwork usage. Does it matter if I use the procedure in http://forum.xda-developers.com/showthread.php?t=1007782 but bypass clockwork? I.e. using vanilla recovery.

Actually you don't need clockworkmod -- or even recovery mode -- for rooting. The process of rooting is simply putting the su binary into /system/bin directory and install Superuser app.
You could try to install zip from stock recovery, I'm pretty sure it won't hurt even the installation is not successful. For me, I always do the rooting by:
Code:
adb remount
adb push su /system/bin/
adb shell chmod 6755 /system/bin/su
Then install the Superuser app from Market.

suksit said:
Actually you don't need clockworkmod -- or even recovery mode -- for rooting. The process of rooting is simply putting the su binary into /system/bin directory and install Superuser app.
You could try to install zip from stock recovery, I'm pretty sure it won't hurt even the installation is not successful. For me, I always do the rooting by:
Code:
adb remount
adb push su /system/bin/
adb shell chmod 6755 /system/bin/su
Then install the Superuser app from Market.
Click to expand...
Click to collapse
Does the bootloader need to be unlocked w/this method?

suksit said:
Actually you don't need clockworkmod -- or even recovery mode -- for rooting. The process of rooting is simply putting the su binary into /system/bin directory and install Superuser app.
You could try to install zip from stock recovery, I'm pretty sure it won't hurt even the installation is not successful. For me, I always do the rooting by:
Code:
adb remount
adb push su /system/bin/
adb shell chmod 6755 /system/bin/su
Then install the Superuser app from Market.
Click to expand...
Click to collapse
Thanks for that. But for the n00b part of me, could you tell me which directory I need to launch that command from? I.e. which directory of the android sdk.
From memory it was something like c:\program files (x86)\android\android-sdk\tools... or something.
EDIT: mm, I just tried initating those commands from within both the \\tools and \\platform-tools and in both instances I either get "unrecognised command" or "error: device not found" or "remount failed: operation not permitted"; depending on whether the device is fully booted or just in recovery. Any ideas?

Slight problem unrooting

Hi all,
I've done a search and not found anything that has helped. Long story short I think I have flashed the wrong stock image to my Nexus S so that I can get a warranty repair done.
The problem I am having is that my bootloader seems to be frozen and I cannot use fastboot to flash cwm again to install the stock nandroid that I found in the FAQ. The phone can boot normally and I can use adb but cannot do anything in the bootloader. I've also tried using adb to push the recovery to data but get a permission denied error.
Any helps guys as its kinda urgent.

FirmShark said:
Hi all,
I've done a search and not found anything that has helped. Long story short I think I have flashed the wrong stock image to my Nexus S so that I can get a warranty repair done.
The problem I am having is that my bootloader seems to be frozen and I cannot use fastboot to flash cwm again to install the stock nandroid that I found in the FAQ. The phone can boot normally and I can use adb but cannot do anything in the bootloader. I've also tried using adb to push the recovery to data but get a permission denied error.
Any helps guys as its kinda urgent.
Click to expand...
Click to collapse
What error are you getting in fastboot? You're on the fastboot screen and not trying to access the recovery, right?
Make sure you clean your phone of CWM recovery too before sending to warranty.

polobunny said:
What error are you getting in fastboot? You're on the fastboot screen and not trying to access the recovery, right?
Make sure you clean your phone of CWM recovery too before sending to warranty.
Click to expand...
Click to collapse
I boot into the bootloader and I cannot select any options on the menu, it appears frozen. "Fastboot devices" brings up no devices at all. ADB works when the phone is booted normally. Also it is on the stock recovery so I cannot flash the stock nandroid image that is available. I have got myself into a proper dilemma with it. Believe it or not I have been quite successful with rooting and flashing in the past but this has me puzzled.
I think it is down to the stock image I flashed which was Android 2.3.6/GRK39F/UCKF1 Radio/KA3 Bootloader for the i9020a. I was always under the impression I had the i9020a as that's the ota updates I had used since I got the phone.
If I can get fastboot working again then I can flash cwm and restore the nandroid and get myself back to stock. Then I can re-lock the bootloader.

FirmShark said:
I boot into the bootloader and I cannot select any options on the menu, it appears frozen. "Fastboot devices" brings up no devices at all. ADB works when the phone is booted normally. Also it is on the stock recovery so I cannot flash the stock nandroid image that is available. I have got myself into a proper dilemma with it. Believe it or not I have been quite successful with rooting and flashing in the past but this has me puzzled.
I think it is down to the stock image I flashed which was Android 2.3.6/GRK39F/UCKF1 Radio/KA3 Bootloader for the i9020a. I was always under the impression I had the i9020a as that's the ota updates I had used since I got the phone.
If I can get fastboot working again then I can flash cwm and restore the nandroid and get myself back to stock. Then I can re-lock the bootloader.
Click to expand...
Click to collapse
So if I get this straight:
-Booting into fastboot you cannot move your cursor using vol + or vol - (?)
-You cannot access recovery, which is stock
-You can use your phone but cannot do anything requiring SU permissions (not rooted)
-You are on stock ROM
-Device is unlocked
Is everything right?

-Booting into fastboot you cannot move your cursor using vol + or vol - (?)
Yeah that's what happens.
-You cannot access recovery, which is stock
I can reboot using adb to get to it. Recovery is stock.
-You can use your phone but cannot do anything requiring SU permissions (not rooted)
I can use my phone but cannot make/recieve calls or send/recieve sms. Wifi works however.
-You are on stock ROM
I am on stock 2.3.6.
-Device is unlocked
Device is unlocked.
Hopefully that clear's it up a bit. Beginning to worry about my phone now

Hi!
If ADB work , you can root your devices then you can change stock recovery with CWM 5.0.2.0 or......

How so? I don't know of a way to change the recovery using adb. I only know how to using fastboot which isn't working.

FirmShark said:
How so? I don't know of a way to change the recovery using adb. I only know how to using fastboot which isn't working.
Click to expand...
Click to collapse
If ADB work it's very easy....
You can changed by installing Rom Manager with root acces and rerwrite recovery with CWR....after that you can install all what you want...

Can you tell me how then as I can't find how to do it???

FirmShark said:
Can you tell me how then as I can't find how to do it???
Click to expand...
Click to collapse
ok
You must do exactly as I say and you will see that it is not hard ... it will root your phone

Yes, what are the instructions?

you need that : http://www.4shared.com/file/7wJht93f/Root.html
unpack in your pc...and waitt me...for detail...
it's not virus...I can help you ....
waitt me 5 min .....

I have downloaded the file.

if you are ready....let's go...
connect your device and see if adb responding >adb devices
normal you will see your id device or un number...and tell me
---------- Post added at 11:52 PM ---------- Previous post was at 11:52 PM ----------
FirmShark said:
I have downloaded the file.
Click to expand...
Click to collapse
ok just unpack

adb is working fine and my device is present.

FirmShark said:
adb is working fine and my device is present.
Click to expand...
Click to collapse
click cmd
>adb push files\zergRush /data/local/tmp/
>adb shell
#chmod 777 /data/local/tmp/zergRush
#exit
---------- Post added at 11:58 PM ---------- Previous post was at 11:56 PM ----------
>adb shell
#./data/local/tmp/zergRush
WAITING FOR DEVICE TO RECONNECT
if it gets stuck over here for a long time then try:
disconnect usb cable and reconnect it
toggle "USB DEBUGGING" (first disable it then enable it)

done that, now what?

>adb push files\busybox /data/local/tmp/
>adb shell
#chmod 755 /data/local/tmp/busybox
#exit
>adb shell
#/data/local/tmp/busybox mount -o remount,rw /system
#dd if=/data/local/tmp/busybox of=/system/xbin/busybox
#chown root.shell /system/xbin/busybox
#chmod 04755 /system/xbin/busybox
#/system/xbin/busybox --install -s /system/xbin
#rm -r /data/local/tmp/busybox
#exit
>adb push files\su /system/bin/su

done that now. what do i do now?

>adb shell
#chown root.shell /system/bin/su
#chmod 06755 /system/bin/su
#rm /system/xbin/su
#ln -s /system/bin/su /system/xbin/su
#exit
>adb push files\Superuser.apk /system/app/
>adb shell
#cd /data/local/tmp/
#rm *
#exit
>adb reboot
ALL DONE!!!
now instal ROM Manager for ClockWordMod Recovery

[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)