Database Info

[HOW TO] Fix Quickboot as well as reboot into recovery from ROM Manager.

For those of you who want to use Quickboot
OR
Have ROM Manager from market and want to "Reboot into recovery" directly, do this
Extract Reboot from Reboot.zip and place it in \androidsdk\tools folder
Then
adb shell
mount /dev/block/mtdblock4 /system
exit
adb push reboot /system/bin
adb shell
cd /system/bin/
ls
chmod 755 reboot
chmod 755 /system/bin/reboot
And of course, this can't be done in Android system. You would have to boot to toast's recovery.
Also, i didn't know the command to push from shell, therefore the redundant adb shell. =)

so this takes out the HBoot? and goes straight to Recovery Rom?

unfortunately no,
but it lets you skip the step "Vol up+power" and go straight to stock recovery.
From there you can use the "fake-flash"

awesome...Thanks for sharing, i will try this

I would recommend "rm /system/bin/reboot" before pushing the new one.

Great job! Works like a charm!

I guess TheBiles and I were posting in the wrong sub-forum?
http://forum.xda-developers.com/showthread.php?t=695978

wcasdf said:
For those of you who want to use Quickboot
OR
Have ROM Manager from market and want to "Reboot into recovery" directly, do this
Extract Reboot from Reboot.zip and place it in \androidsdk\tools folder
Then
adb shell
mount /dev/block/mtdblock4 /system
exit
adb push reboot /system/bin
adb shell
cd /system/bin/
ls
chmod 755 reboot
chmod 755 /system/bin/reboot
And of course, this can't be done in Android system. You would have to boot to toast's recovery.
Also, i didn't know the command to push from shell, therefore the redundant adb shell. =)
Click to expand...
Click to collapse
C:\Documents and Settings\Owner>adb shell
# mount /dev/block/mtdblock4 /system
mount /dev/block/mtdblock4 /system
Usage: mount [-r] [-w] [-o options] [-t type] device directory
# exit
what am i doing wrong??

worked great, we are only one step away now

Help......
Hi Sorry to bother..
Have started the process got to push the file to the system bin. However when then attempting the next command adb shell, i recieve the following error:-
- exec '/system/bin/sh' failed: Not a directory (20) -
Any advice????
Cheers
Andy
.....Extract Reboot from Reboot.zip and place it in \androidsdk\tools folder
Then
adb shell
mount /dev/block/mtdblock4 /system
exit
adb push reboot /system/bin
adb shell
cd /system/bin/
ls
chmod 755 reboot
chmod 755 /system/bin/reboot

wcasdf this will also useful for desire user, i have pushed reboot into /system/bin but didnt sames to work
desire /system is /dev/block/mtdblock3, this is the problem?

Sorted....
Kali- said:
wcasdf this will also useful for desire user, i have pushed reboot into /system/bin but didnt sames to work
desire /system is /dev/block/mtdblock3, this is the problem?
Click to expand...
Click to collapse
Absolutely right Kali........the mtdblock3 resolved the issue.....now able to enter recovery mode and also back up rom.....
Brilliant....many thanks......

watzone69 said:
I guess TheBiles and I were posting in the wrong sub-forum?
http://forum.xda-developers.com/showthread.php?t=695978
Click to expand...
Click to collapse
I was just afraid the thread would get moved with these super-strict mods in this board.
-------------
Sent from my HTC EVO 4G using Tapatalk Pro.

Worked great. Now the reboot commands in ROM Manager and Quick Boot work.

tells me reboot file is not there its in the androidsdk\tools folder

Sporkman said:
tells me reboot file is not there its in the androidsdk\tools folder
Click to expand...
Click to collapse
adb push is pretty versatile, you can give it absolute paths. if you downloaded the reboot file to a different directory, example:
adb push c:\downloads\reboot /system/bin/reboot
hope that helps!
OP: where did this reboot binary come from?
im running PC36IMG.zip and reboot recovery and reboot bootloader both work in normal android mode ...

joeykrim said:
adb push is pretty versatile, you can give it absolute paths. if you downloaded the reboot file to a different directory, example:
adb push c:\downloads\reboot /system/bin/reboot
hope that helps!
OP: where did this reboot binary come from?
im running PC36IMG.zip and reboot recovery and reboot bootloader both work in normal android mode ...
Click to expand...
Click to collapse
i dropped the file in C:\androidsdk\tools WHERE it needs to be

trying to figure this for my desire i understand block needs to be 3 and the rest the same but
keep getting device or resource busy when trying the mount command?

fixed it..you need to be in recovery before doing the above-otherwise you get a resource busy message
dont forget to change to block3 not 4 if using desire- rom manger now works as it should !! thanks

joeykrim said:
...OP: where did this reboot binary come from?
Click to expand...
Click to collapse
I'm not the OP but I originally got mine from the Hero sub-forum:
http://forum.xda-developers.com/showpost.php?p=5356050&postcount=623

How to Install Ubuntu on Your Desire/Android

First sorry for my English
All credits are for zedomax, who has gotten it to work in Nexus One and for Desire is practically the same.
Sorry about "h t t p" of link adress I am very new here.
Original howto -> h t t p : / /nexusonehacks.net/nexus-one-hacks/how-to-install-ubuntu-on-your-nexus-oneandroid/
For now, I've only gotten it to work with Windows 7 and "CyanogenMod 5.0.8" and "Defrost2.0c" ROMs. The rom is important for get this works.
Practically almost all the steps are the same as in the guide of nexus one by zedomax. Well go:
Before anything, download ubuntu.zip from original HOWTO and unzip it.
Now download the updated script from zedomax.
h t t p : / /zedomax.com/android/bootubuntu
and overwrite the bootubuntu file of unzipped ubuntu.zip
1. First, you will need a rooted Desire.
zedomax say that you must have the latest version of busybox 1.16.1 but in Defrost2.0c works with 1.16.0 and cyanogenmod has 1.16.1. So we ignore this step from original guide.
2. Once you have a rooted Android phone, you will be able to run Ubuntu under Chroot.
3. Copy these six files from ubuntu.zip over into your SD card’s root folder under folder name “ubuntu“
4. Put your Desire in recovery mode. And connect it to your computer via USB.
5. I am assuming you've already installed the Android SDK (while you were rooting your phone) so let's head to your Android SDK directory and load up ADB Shell.
For Windows, go to your Android SDK Tools directory such as c:\sdk\tools and type "adb shell".
(FYI, cd is the command you can use to browse to your sdk\tools directory. For Windows, do cd \sdk\tools and for Mac/Linux, do cd /sdk/tools.
For linux and Mac, go to your Android SDK Tools directory such as /sdk/tools and type "./adb shell" or it can also be "sudo ./adb shell" for Ubuntu.
6. Once you are in the ADB shell, you should see a “#”symbol. Great, let’s start bootin’ Ubuntu right away.
7. Next, type "mount system", press enter and then type "mount sdcard". If you get this "mount: mounting /dev/block/mmcblk0p1 on /sdcard failed: Device or resource busy" ignore it, sdcard is already mounted.
8.- Next, type "cd /sdcard/ubuntu"
9.- Now we will write separate commands instead of using a script to see if something has gone wrong easily. Copy and paste each line separately and hit Enter at the end of each command.
rm /system/bin/fsrw <--(this problably return an error, ignore this)
rm /system/bin/bootubuntu <--(this problably return an error, ignore this)
rm /system/bin/unionfs <--(this problably return an error, ignore this)
rm /system/bin/mountonly <--(this problably return an error, ignore this)
cp -f fsrw /system/bin
cp -f bootubuntu /system/bin
cp -f unionfs /system/bin
cp -f mountonly /system/bin
cd /sdcard/ubuntu
chmod 4777 * <--(this problably return an error, ignore this)
cd /system/bin/
chmod 4777 *
cd /
umount sdcard
umount system
exit
Now select "reboot system now" from recovery menu of your Desire. When android fully loaded you need load up again ADB Shell.
For Windows, go to your Android SDK Tools directory such as c:\sdk\tools and type "adb shell".
Type "su" to enter superuser mode. Is very important not to forget this!
type "mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system"
type "mkdir /data/local/mnt"
10. Once that completes, type "bootubuntu" to "chroot" or boot into your new Ubuntu on your Android!
If you get the "root_localhost:/#" sign, congratulations! You've just installed Ubuntu on your Desire/Android phone!
the hardest part is complete!. From now, follows the original guide for the "nexus one" to get access to Gnome (visual desktop).
Other problems like keyboard mapping can fix it follow the original post from nexus one forum:
http://forum.xda-developers.com/showthread.php?t=718952
well, I hope this helps

thats pretty cool mate thanks ill try it out tonight when i get home from work

Thanks for this! Will give it a shot when I have a moment

Script?
Anybody fancy writing a nice script to do this for us? I'm on Holiday in Spain so I'm feeling pretty lazy.

Awesome, thanks a lot!
I'm on DJ Droid's Sense with Froyo 2.2, will try it.. hope it works! But do you know why it's rom specific? Is it because of busybox?

I tried this out, and got stuck on bootubuntu from the bootloader menu.
command not recognized. . .
everything works ok until i try to boot ubuntu from the bootloader menu.

Works great for me, SixOclock rom with busybox 1.16.2

peewster said:
I tried this out, and got stuck on bootubuntu from the bootloader menu.
command not recognized. . .
everything works ok until i try to boot ubuntu from the bootloader menu.
Click to expand...
Click to collapse
Try ./bootubuntu instead

as soon as i get home, i will.
Thnx

Is anyone nice enough to break the ubuntu.zip down into the 6 files and upload separately?

good job, works fine on SetRom 3.5

someone can post screenshoots ???

?¿?The uncompressed "ubuntu.zip" has a 2Gb .img!!!

peewster said:
I tried this out, and got stuck on bootubuntu from the bootloader menu.
command not recognized. . .
everything works ok until i try to boot ubuntu from the bootloader menu.
Click to expand...
Click to collapse
humm, are you get any error in this part?
cp -f fsrw /system/bin
cp -f bootubuntu /system/bin
cp -f unionfs /system/bin
cp -f mountonly /system/bin
and, where are you launching the bootubuntu command? You need do it from adb shell (at least until you set gnome) or terminal client directly from your phone, like better terminal emulator. Don't forget do "su" before launch bootubuntu. If it still does not work I recommend you start again the guide

why would anyone want to install ubuntu on a phone?

horadee said:
why would anyone want to install ubuntu on a phone?
Click to expand...
Click to collapse
Why would anyone not want to install ubuntu on their phone?

Ok, so it worked. I'm now logged in through adb into Ubuntu. But how can i run ubuntu directly from my phone ?

VNC?
10chars.

abc27 said:
VNC?
10chars.
Click to expand...
Click to collapse
I was wondering if you can run ubuntu (shell) directly from phone instead of adb

Anyone got screenshots?
Sent from my Desire using XDA App

[Q] cat /sdcard/update.zip "invalid length"

I recently purchased a Xoom WiFi and wanted to upgrade to 3.2 but due to the fact that I'm currently deployed to Afghanistan I can not get the OTA update in which case I then unlocked, rooted and attempted to install it on my own. I successfully unlocked and rooted my xoom yet I am stuck on the update portion. I'm getting stuck at the "cat /sdcard/update.zip" command in ADB in which it returns with "invalid length" and I can not for the love of me get it to work. The commands I complete until that part are;
adb push update.zip /sdcard/update.zip
adb shell
su
cd /cache
mkdir recovery
then,
cd recovery
echo ‘-update_package=CACHE:/recovery/update.zip’ > command
cat /sdcard/update.zip > update.zip
reboot recovery
which is where I get the "invalid length" after typing the cat /sdcard/update.zip > update.zip command. If anyone could help me out I would greatly appreciate it!
Thanks

Mr.Buckley said:
I recently purchased a Xoom WiFi and wanted to upgrade to 3.2 but due to the fact that I'm currently deployed to Afghanistan I can not get the OTA update in which case I then unlocked, rooted and attempted to install it on my own. I successfully unlocked and rooted my xoom yet I am stuck on the update portion. I'm getting stuck at the "cat /sdcard/update.zip" command in ADB in which it returns with "invalid length" and I can not for the love of me get it to work. The commands I complete until that part are;
adb push update.zip /sdcard/update.zip
adb shell
su
cd /cache
mkdir recovery
then,
cd recovery
echo ‘-update_package=CACHE:/recovery/update.zip’ > command
cat /sdcard/update.zip > update.zip
reboot recovery
which is where I get the "invalid length" after typing the cat /sdcard/update.zip > update.zip command. If anyone could help me out I would greatly appreciate it!
Thanks
Click to expand...
Click to collapse
Nevermind.

Help plz!!!
Hey, I have a similar issue. I'm using adb to install cmw on my p690 but get an error of invalid length for the cat command for /sdcard/flash_image....... can u giv me a soln?

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

S-off help - "cannot stat soffbin3"

So I was performing the Facepalm S-off method and ran into this when I got the push soffbin3 step
-------------------------------------------------
adb push soffbin3 /data/local/tmp
"cannot stat 'soffbin3': No such file or directory"
-------------------------------------------------------------------------
Any idea what that means or what to do from here?

Did you put the file in the folder that contains adb (most likely your platform-tools folder) or change directory to that folder?

panda_mode said:
Did you put the file in the folder that contains adb (most likely your platform-tools folder) or change directory to that folder?
Click to expand...
Click to collapse
yep. the soffbin3.zip file is there.
Do I have to extract it?

Yup you have to extract it lol

panda_mode said:
Yup you have to extract it lol
Click to expand...
Click to collapse
haha!
<----noob
no dice though... I'm still S-ON :/

Did you get the 99 error instead of the 92?

panda_mode said:
Did you get the 99 error instead of the 92?
Click to expand...
Click to collapse
First off - got it work. I'm showing S-off now! :arty::
Yep, had the 99 error. So I rebooted into recovery, wiped cache and dalvik cache - then did a hard power off. Powered on into bootloader.
Then repeated all the steps and got the 92 this time.
The reason why it failed the first time was because I forgot to grant adb su access. Second time around I caught it and granted the permissions request but only on third command of "adb shell su -c...etc"
Does the second command "adb shell chmod 744...etc" need su access to perform correctly? What does that command do anyway.
I'm wondering if the second command needed su, I may have messed something up that won't rear its ugly head until I stumble on it.

I checked the log for su requests and adb only popped up once, which means the "adb shell su -c..." is the only one that needed.
I think I'm in the clear!

To be honest I'm not sure what it does either lol. But I do know the command: adb shell su -c "/data/local/tmp/soffbin3" will contact SU and you have to grant access. Glad you got it, though!