Related
I need help installing a custom recovery. I believe my stock recovery is corrupt or somehow deleted. I have tried looking in multiple forums, but they had no help but using adb or fresh kitchen. Neither of those work, Fresh Kitchen comes up with an error and adb shows this
Code:
C:/android-sdk-windows/tools>adb shell
$ su
su
# flash_image recovery /sdcard/recovery.img
flash_image recovery /sdcard/recovery.img
flash_image: not found
Can someone please tell me how to fix this, I want 2.2 badly.
MobileSWord said:
I need help installing a custom recovery. I believe my stock recovery is corrupt or somehow deleted. I have tried looking in multiple forums, but they had no help but using adb or fresh kitchen. Neither of those work, Fresh Kitchen comes up with an error and adb shows this
Code:
C:/android-sdk-windows/tools>adb shell
$ su
su
# flash_image recovery /sdcard/recovery.img
flash_image recovery /sdcard/recovery.img
flash_image: not found
Can someone please tell me how to fix this, I want 2.2 badly.
Click to expand...
Click to collapse
well first off i would post this in the right section. Seeing as you actually made the CHECK to say this thread is a question shows you knew it was a question. Look at the sticky that at the toop of this page. POST QUESTIONS IN THERE RIGHT SECTION...Q&A!
my suggestion would to try and do unrevoked or the 1 click apk for hero(or universal androot). those should install a recovery for ya.
i have attached 2 of them but you can go to unrevoked.com and do it there.
My personal favourite way to do it is using the one click root, then flashing a recovery with rom manager (clockwork)
Sent from my HERO200 using XDA App
Hi,
as you can see im a newbie. but i feel i have to ask as i just cant find and answer as all the steps i have tried just dont work. i know there are many threads with this problem but working through like 13 different ones still did not help.
basically I have just rooted my HTC desire Z and want to flash the recovery image form clockwork mod on it. (flashing from the app says it worked but when rebooting in recovery mode it has that little triangle symbol)
so i have tried:
clockworkmod app
SDK tools
phone terminal
SDK tools
getting into shell and su i tried flash_image but it was flash_image: not found.
i have typed it in correctly and made sure there is a flash_image file in the tools folder. i have updated to sdk revision 10 (no there is no flash_image for some reason and tried all possibilities by adding one etc) i have tried many different locations and diffrent commands but it always says:
C:\androidSDK\tools>adb shell
su
#flash_image recovery recovery.img
flash_image: not found
exit
exit
i have also tried to push a flash_image into the system folder bin to flash from the terminal on the phone but it again says push: not found. (there is no flash_image standard on HTC in this folder)
su
#push flash_image.zip /system/bin/flash_image
push flash_image.zip /system/bin/flash_image
push: not found
I have a feeling it has something to do with the SDK as i cannot get any to work.. other than reboot recovery command. fastboot, push, pull: all say *: not found) this is weird though because it worked on my HTC tattoo. (i have reinstalled SDK a few times)
i have tried the mac version of SDK but there is also no flash_image in the tools either. (tried adding one)
i have tried all the combinations of commands that are i can find here and googled, but i just can figure it out.. please help.
I have now also tried flashing older recovery images via the app and it successfully flashed but still get the little bloody triage after reboot in recovery mode..
i have also tried HBOOT and fastboot.. ADB keeps saying : not found
HELP!
I don't think there is an adb command flash_image.
To push/pull files you have to be in windows command prompt, and not through adb shell on the phone. There is no adb tools in the phone, thats why it is not found. Adb tools is installed on your computer.
ya i got that, but from all the blogs that i have read thats how you flash the recovery file.. via adb flash_image. (if clockwork does not work)
if not then please please please let me know how to do it...
tophermetcalfe said:
ya i got that, but from all the blogs that i have read thats how you flash the recovery file.. via adb flash_image. (if clockwork does not work)
if not then please please please let me know how to do it...
Click to expand...
Click to collapse
I have only flashed through recovery mode on the phone itself or through odin software on my computer.
I just checked my sdk tools and could not find the command flash_image.
Navigate in your windows command prompt to your sdk directory, for example C:\android\platform-tools\ and type "adb -h" it will show you all avaiable commands.
can i use odin to flash an HTC?
SOLVED
OMG!!! three days and i have found the problem!
first of all dont rely on the VISIONary apk, it roots but for some reason did not change the s-off (even when selected)
USE GFREE
thanks to XDA i finally found the thread i was looking for so for so long:
http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision
THANK YOU GUYS!
tophermetcalfe said:
Hi,
as you can see im a newbie. but i feel i have to ask as i just cant find and answer as all the steps i have tried just dont work. i know there are many threads with this problem but working through like 13 different ones still did not help.
basically I have just rooted my HTC desire Z and want to flash the recovery image form clockwork mod on it. (flashing from the app says it worked but when rebooting in recovery mode it has that little triangle symbol)
so i have tried:
clockworkmod app
SDK tools
phone terminal
SDK tools
getting into shell and su i tried flash_image but it was flash_image: not found.
i have typed it in correctly and made sure there is a flash_image file in the tools folder. i have updated to sdk revision 10 (no there is no flash_image for some reason and tried all possibilities by adding one etc) i have tried many different locations and diffrent commands but it always says:
C:\androidSDK\tools>adb shell
su
#flash_image recovery recovery.img
flash_image: not found
exit
exit
i have also tried to push a flash_image into the system folder bin to flash from the terminal on the phone but it again says push: not found. (there is no flash_image standard on HTC in this folder)
su
#push flash_image.zip /system/bin/flash_image
push flash_image.zip /system/bin/flash_image
push: not found
I have a feeling it has something to do with the SDK as i cannot get any to work.. other than reboot recovery command. fastboot, push, pull: all say *: not found) this is weird though because it worked on my HTC tattoo. (i have reinstalled SDK a few times)
i have tried the mac version of SDK but there is also no flash_image in the tools either. (tried adding one)
i have tried all the combinations of commands that are i can find here and googled, but i just can figure it out.. please help.
Click to expand...
Click to collapse
I have a Hero, but Try what worked for me Flash Clockwork, whether it does it or Not, Then Try Flashing the Alternate at the Bottom!
*Sent on My*
Fast as its Ever Been....
"Sprint" Hero.... Running My, *ExpressoEnergyHero* ROM, KIFNO's Build.Prop.Tweek, & The XDA BLUE.apk!! "Page 10" of My Thread!!
http://forum.xda-developers.com/showthread.php?t=957867
http://www.megaupload.com/?d=WTMLMK6M
http://m.youtube.com/index?desktop_uri=/&gl=US#/profile?user=PMGRANDS
How many posts do I need to have before I can post in the development threads? I want to install SRF and I'm sure I'll have plenty of questions.
Actually I already have one. I have an Epic on Eclair DI18. For the OneClickRoot Mod can I use the DK28 zip file?
Well, I just received the OTA update for Froyo EC05. So now do I use the OneClickRoot zip for EB13?
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?
Hello,
I am stuck with rooting process. I tried rooting, unrooting before but this time, for some odd reason. I am unable to proceed
I followed this procedure from unlockr website to root the nexus S. Could not post the exact link because of restrictions
Phone is unlocked , USB debugging is ON. ADB mode is working, I can use other commands. But its giving me the following error on step 6 . Line 3
Mount : Operation Not permitted
Attaching image !
When I boot using volume up & Power button and go to Recovery, It gives me exclamation mark & Android Sign... So I cant unroot it either.
I always tried to unroot so I can go back to original state and restart the process. If I flash through recovery.img I can go into recovery but after few steps, I am stuck
Yeah that's normal. The mount command requires root permission (which you don't have yet)
Generally what you have to do after flashing the (right version of) custom recovery is:
copy the su.zip to your SD card
reboot into custom recovery
choose apply zip from SD card and select the su.zip
reboot
That's it.
Su have already been installed in previous step. Infact, I can even see its icon in menu...
Then it sounds like your recovery reverted back to stock. Did you rename the .sh file that rewrites the recovery on reboot? If not, do that using root explorer or any other method you find in the guide. Then flash the recovery again and it will stick.
Sent from my Nexus S using Tapatalk
No I didnot renamed. I was just following the process. I tried to unroot but cant do it either. I am stuck
ahaseeb said:
Su have already been installed in previous step. Infact, I can even see its icon in menu...
Click to expand...
Click to collapse
If su is installed correctly then for the "Mount : Operation Not permitted" problem, you just have to type su in adb shell (there may be a Superuser permission popup on the phone, just allow it) -- the prompt should change from $ to #, which means you are now root. After that the mount command should work.
To make custom recovery stick on every boot, rename /system/etc/install-recovery.sh to other name e.g. install-recovery.sh.disabled
When I typed su it said Permission denied !
Just because you have superuser in your app drawer does not mean you're rooted. You can downloaded from the market on any phone/rom.
You are not rooted.
Flash custom recovery via fastboot
Boot directly into recovery etc.
ahaseeb said:
When I typed su it said Permission denied !
Click to expand...
Click to collapse
Then I suggest you re-install Superuser from Android Market. Normally it shouldn't just say permission denied, there should be a Superuser popup asking for permission.
Or better, try to redo everything following this guide instead.
Again YOU HAVE TO FLASH SU FROM CUSTOM RECOVERY.
Do not install from market. Hell don't even boot up the OS. Flash recovery. Boot directly into recovery and flash su.zip from your phones internal storage/sdcsrd in recovery. The you're rooted.
Now you can update delete/rename the script to make the custom recovery stick. Update su in market or whatever else you want to do.
.
I believe i got it fixed. When ever the phone used to boot after installation of SU, dialogue box to ask for unlock. That dialogue box disappear very quickly. It took me time to figure it out. Thanks, I guess I am good now.
Thanks every one
Hello all.
I looked and can't find but is there a rooted 1.55.531.3 rom for the device anywhere.
Rooted the phone tried the ICS from sensation and kinda want to go back but not unroot.
I could send you my recovery if you have the ability to flash
rooted 1.55.531.3 with clockwork recovery and SU
M9x3mos said:
Hello all.
I looked and can't find but is there a rooted 1.55.531.3 rom for the device anywhere.
Rooted the phone tried the ICS from sensation and kinda want to go back but not unroot.
Click to expand...
Click to collapse
yeah, what you are looking for doesn't exist at the moment. i too thought about making a nandroid of the the new ROM for people to flash, but since the new setup comes with a new radio, new kernel, new HBOOT, etc., i'm not sure how it would fly if someone just flashed the nandroid?
Hboot n radio would be the only thing missing... Kernels sits in recovery....
rooted 1.55.531.3 with clockwork recovery and SU
I know I made a flashable package out of the Google Talk apk file, and either did or meant to make some out of the other apps in it - I'm not sure which thread it's in.
I can check later and link it. Not sure what else anyone did with it, if wifi calling wasn't pulled forward from it I'll have a package for that sometime soon anyway.
I also never did get a chance to check what the gps changes were I remember being in it.
Edit:
Link to Gtalk flashable zip package from that update.
Sent from my Bulletproof_Doubleshot using xda premium
nlarge said:
I could send you my recovery if you have the ability to flash
rooted 1.55.531.3 with clockwork recovery and SU
Click to expand...
Click to collapse
Do you have the stock rom for 1.55.531.3 that I can flash on my mt4gs? I would really appreciate it
http://forum.xda-developers.com/showthread.php?t=1484679
http://forum.xda-developers.com/showthread.php?t=1433805
It would be flashed as if restoring a nandroid. I would flash the above link. If you really want it I can send it
rooted 1.55.531.3 with clockwork recovery and SU
Thanks. Okay, this is where I am:
Unlocked bootloader with htcdev
s-on
hboot 1.45.0013
software 1.55.531.3
Would like to achieve root so that I can flash custom roms/use titanium backup. From what I can tell, nlarge was able to accomplish this. (http://forum.xda-developers.com/showthread.php?t=1474933&page=6). However, couldn't post on that thread because I have less than 10 posts....sorry.
Cannot use temproot (FR3VO) method because says needs s-off and/or adb mount issue:
An error occurred while running the exploit (-1) (errno: 22)
c:\Android>adb wait-for-device
c:\Android>adb remount
remount failed: Operation not permitted
c:\Android>adb shell mount -o rw,remount rootfs /
mount: Operation not permitted
c:\Android>adb shell mount -oremount,suid /dev/block/mmcblk0p23 /data
mount: Operation not permitted
c:\Android>adb shell mkdir /vendor/bin
mkdir failed for /vendor/bin, Read-only file system
c:\Android>adb shell chown root.shell /vendor/bin
Unable to chmod /vendor/bin: No such file or directory
c:\Android>adb shell chmod 755 /vendor/bin
Unable to chmod /vendor/bin: No such file or directory
c:\Android>adb push ./sqlite3 /vendor/bin
cannot stat './sqlite3': No such file or directory
c:\Android>adb push ./su /vendor/bin
cannot stat './su': No such file or directory
c:\Android>adb push ./busybox /vendor/bin
cannot stat './busybox': No such file or directory
c:\Android>adb shell chown root.shell /vendor/bin/su
Unable to chmod /vendor/bin/su: No such file or directory
c:\Android>adb shell chown root.shell /vendor/bin/busybox
Unable to chmod /vendor/bin/busybox: No such file or directory
c:\Android>adb shell chown root.shell /vendor/bin/sqlite3
Unable to chmod /vendor/bin/sqlite3: No such file or directory
c:\Android>adb shell chmod 6555 /vendor/bin/su
Unable to chmod /vendor/bin/su: No such file or directory
c:\Android>adb shell chmod 4555 /vendor/bin/busybox
Unable to chmod /vendor/bin/busybox: No such file or directory
c:\Android>adb shell chmod 755 /vendor/bin/sqlite3
Unable to chmod /vendor/bin/sqlite3: No such file or directory
c:\Android>adb shell busybox --install -s /vendor/bin
busybox: permission denied
c:\Android>adb shell sync
c:\Android>adb shell chmod 6555 /vendor/bin
Unable to chmod /vendor/bin: No such file or directory
c:\Android>adb install ./Superuser.apk
can't find './Superuser.apk' to install
c:\Android>pause
Press any key to continue . . .
So, I understand, permission denied/operation not permitted, I assume because I don't have root.
When I look at superuser, it says "su binary voutdated" and when I tap to check for updates, automatic update fails and error message "su was not updated. A zip file (su-2.3.1-bin-signed.zip) has been placed on your sdcard, please reboot into recovery mode and flash it to update your su binary.
Can't boot into recovery mode, phone just sits on mytouch 4g slide screen. Again, I assume because no root. Same thing happens if I try to factory reset, just stays on the mytouch 4g slide screen.
Anyone have any suggestions? I am going crazy trying to get this phone to work. I would really appreciate the help!
Flash clock work recovery... I think I linked it somewhere... Or Google will help
rooted 1.55.531.3 with clockwork recovery and SU
Now find yourself a nice recovery image (CWM), boot phone into fastboot mode, "fastboot flash recovery recovery.img".
When this is done you will have a free and open recovery image, and can use that to write/install the su binary and apk (either with flashable zip or through adb shell, either will work).
rooted 1.55.531.3 with clockwork recovery and SU
nlarge said:
Now find yourself a nice recovery image (CWM), boot phone into fastboot mode, "fastboot flash recovery recovery.img".
When this is done you will have a free and open recovery image, and can use that to write/install the su binary and apk (either with flashable zip or through adb shell, either will work).
rooted 1.55.531.3 with clockwork recovery and SU
Click to expand...
Click to collapse
Have tried flashing new and old versions of cwr and the earlier links from blue with no luck. Trying to do it manually through the computer with fastboot, results in 'waiting for device' message. All drivers installed, usb debug, have tried charge only/mount as disk drive options. Neither work. Have tried flashing manually by converting .img to .zip without compression and flashing through phone. No error message but nothing changes.
Cannot use cwm to flash because not error message says not rooted. Not sure what else to do. BTW, you guys are awesome for helping me out Thanks!
Put your phone in fastboot. Pull battery, hold down and power then try again
rooted 1.55.531.3 with clockwork recovery and SU
How to fastboot flash recovery
Return to Contents Page - doubleshot Developers Reference
Boltinghouse said:
Have tried flashing new and old versions of cwr and the earlier links from blue with no luck. Trying to do it manually through the computer with fastboot, results in 'waiting for device' message. All drivers installed, usb debug, have tried charge only/mount as disk drive options. Neither work. Have tried flashing manually by converting .img to .zip without compression and flashing through phone. No error message but nothing changes.
Cannot use cwm to flash because not error message says not rooted. Not sure what else to do. BTW, you guys are awesome for helping me out Thanks!
Click to expand...
Click to collapse
(hah, thanked but meant to hit quote)
What you need to do is go here: http://clockworkmod.com/rommanager
Scroll down the list and find the recovery for our device (5.0.2.7 for the myTouch 4G Slide) - download this.
Put it in the same folder as 'fastboot.exe' on your computer. Rename it to recovery.img
On your phone, turn off 'fastboot' in power options.
Power off the phone.
Now, give it a minute to power off - then hold the volume down button and press power.
Now it will boot up to the hboot menu. The list presented will have you highlighted on the word 'fastboot' - press power to choose this.
Now you are presented with the fastboot menu. It should say fastboot with a red highlight around it near the top.
At this time you should plug the USB cord from your computer into the phone. It will update to say fastboot USB in red highlight now.
-okay-
We have the phone booted up in fastboot, attached to the computer, and ready to work with.
Open up your command prompt, and navigate to the folder where you have the fastboot command. This is the same folder that you have the new clockworkmod recovery.img in from before.
In your terminal now type:
Code:
fastboot devices
This will come back with your device, serial number, and show you it is connected and ready to go. (if it is not something is wrong)
Now type:
Code:
fastboot flash recovery recovery.img
Let's break this down:
fastboot = activates the fastboot.exe command, and says that what's typed next uses the definitions in that fastboot.exe file.
flash = command that says write to
recovery = destination (name of partition) being written to
recovery.img = file written to previously defined location.
----
Since you have the new clockworkmod recovery file in the same folder as fastboot.exe, and you renamed it to recovery.img, then the previously shown command will overwrite your stock recovery with the new image you are providing it.
At this point you should have clockworkmod recovery in place of your stock recovery when you boot the device to hboot menu and select recovery.
Let us know if you have any other problems.
Good explanation blue.... It sounded like he knew what he was doing, hence my quick correction...
Hate typing a lot out from phone!
rooted 1.55.531.3 with clockwork recovery and SU
OMG! Thats awesome. FINALLY ROOTED!!!!! yay! So happy. Thank you guys so much. nlarge and blue, you two are the best!
Thanks again
~Brandi~
Oops... Sorry I called you a he...LOL... Most of us nerds are guys
We help where we can
Boltinghouse said:
OMG! Thats awesome. FINALLY ROOTED!!!!! yay! So happy. Thank you guys so much. nlarge and blue, you two are the best!
Thanks again
~Brandi~
Click to expand...
Click to collapse
rooted 1.55.531.3 with clockwork recovery and SU
nlarge said:
Oops... Sorry I called you a he...LOL... Most of us nerds are guys
We help where we can
rooted 1.55.531.3 with clockwork recovery and SU
Click to expand...
Click to collapse
It's all good, I know being a chick I'm in the minority here. Either way, thank you so much.
So it looks like both nlarge and boltinghouse rooted s-on phones. Is there any reason not to go ahead and root that way? Is there any reason you need/want s-off?
it depends on what you want to do with your phone...
If you just want to be able to make recovery and flash ROMS than you dont need s-off
If you want to play with other stuff(radios and mounts) then you need s-off.
I personally like doing things to my phone so I would like to get to s-off. I am ok with it for now, but S-off will give me the full control I want.
qwerty3656 said:
So it looks like both nlarge and boltinghouse rooted s-on phones. Is there any reason not to go ahead and root that way? Is there any reason you need/want s-off?
Click to expand...
Click to collapse