Database Develop

Cannot flash a recovery image to a rooted hero. Please help.

I have tried every method I can find. The Flashrec, adb push, mount-a, flash_image recovery *.img
Flashrec says cannot run command
mount -a says something about no device
Flash_image says no such file or directory
Please help Im on 1.2.3
Thanks.
adb push recovery-green.img /sdcard/
1445 KB/s (3868672 bytes in 2.613s)
C:\android\tools>adb shell reboot
C:\android\tools>adb shell
# su
su
# cd /sdcard/
cd /sdcard/
# flash_image recovery recovery-green.img
flash_image recovery recovery-green.img
error opening recovery-green.img: No such file or directory
# flash_image recovery recovery-green.img
flash_image recovery recovery-green.img
error opening recovery-green.img: No such file or directory
# flash_image recovery recovery-green.img
flash_image recovery recovery-green.img
error opening recovery-green.img: No such file or directory
# flash_image recovery recovery-green.img
flash_image recovery recovery-green.img
error opening recovery-green.img: No such file or directory
# flash_image recovery recovery-green.img
flash_image recovery recovery-green.img
error opening recovery-green.img: No such file or directory
#

One thing you could try is renaming the file to recovery.img or rec.img. I do something quick and easy. Also try rooting both computer and phone. I had this problem, went to sleep and the next morning have it a try and it worked. Make sure you type everything just as it says. Might also try using flashrec or fresh kitchen.
-------------------------------------
Sent via the XDA Tapatalk App

All these things I have done. Except rebooting the pc. It runs great, its 7 64, but geeesh, I hate rebooting it..lol
Ok Ill try that and let you know,. As far as fresh kitchen, can you tell me more about it, or point me in the correct direction?
thanks!

Stramondroid said:
I have tried every method I can find. The Flashrec, adb push, mount-a, flash_image recovery *.img
Click to expand...
Click to collapse
I had a similar problem upgrading the recovery image, where I ultimately corrupted the recovery image, and then could not boot into recovery at all anymore (though the phone worked perfectly on a regular boot). The new fresh kitchen was the only thing that worked for me.
http://forum.xda-developers.com/showthread.php?t=644007&page=2
Fresh Kitchen
http://geekfor.me/new-release/fresh-kitchen-105/#more-972
download
Go to the "Rooter" tab, under the "Options" heading, and check "Flash RA only"

I have corrupted my recovery image also ,but Kitchen didn't work to fix it. Any other suggestions/

Try rom manager in the market. It had a button to flash recovery, it's the easiest way
Sent from my HERO200 using XDA App

danaff37 said:
Try rom manager in the market. It had a button to flash recovery, it's the easiest way
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
+1...I was going to suggest the same thing
Sent from my froyo using the xda app

[Q] how to format system with adb

so i've been looking around, search/google etc and i can't seem to figure out how to format this partition with adb. you might say, just go to it in recovery, but i'm using amon RA instead of clockwork (restore bugs).
so if anyone was to enlighten me in to what exactly i would write in the command prompt, that would be of great help... thanks!

you could adb push erase_image and run it from adb shell
erase_image can be found in a rom.zip under /system/bin
or you could use fastboot erase system

rattking said:
you could adb push erase_image and run it from adb shell
erase_image can be found in a rom.zip under /system/bin
or you could use fastboot erase system
Click to expand...
Click to collapse
fastboot erase system doesn't seem to work...=\

are you s-on or is there another reason fastboot erase isn't working?
anyways the method i mentioned with erase_image goes
extract erase_image from a rom's .zip it is in /system/bin
in recovery
adb push erase_image /tmp
adb shell
cd /tmp
chmod +x erase_image
./erase_image system
hope this helps..
I used this on a s-on phone before to correct filesystem corruption

rattking said:
are you s-on or is there another reason fastboot erase isn't working?
anyways the method i mentioned with erase_image goes
extract erase_image from a rom's .zip it is in /system/bin
in recovery
adb push erase_image /tmp
adb shell
cd /tmp
chmod +x erase_image
./erase_image system
hope this helps..
I used this on a s-on phone before to correct filesystem corruption
Click to expand...
Click to collapse
yes i am on s-on... i'll try that as soon as i flash a new rom!

rattking said:
are you s-on or is there another reason fastboot erase isn't working?
anyways the method i mentioned with erase_image goes
extract erase_image from a rom's .zip it is in /system/bin
in recovery
adb push erase_image /tmp
adb shell
cd /tmp
chmod +x erase_image
./erase_image system
hope this helps..
I used this on a s-on phone before to correct filesystem corruption
Click to expand...
Click to collapse
keep getting bad blocks... =\ can someone point me in the way of s-off? yes yes i've used search but maybe you guys know some secrets i dont.

You can't get s-off on your phone. The equivalent on the Nexus One is unlocking the bootloader.
Only a very small number of N1's have the ability to s-off...

[HOWTO] Root any Atrix after .sbf flash

See 2nd post for International users and Fastboot rooting.
For ATT users only:
What this is:
This is a full clean SBF of 2.3.4 or 1.8.3 WITH the BL unlock and rooting built in to /preinstall.
Flashable SBF: Full 2.3.4 with preinstall root and pudding bootloader unlock, full sbf
Flashable SBF: Full 1.8.3 with Bootloader unlock and preinstall root. It's over 9000 (600mb DL service sbf)
1. Flash with RSDLite 5.3.1 or sbf_flash
2. Root your phone from adb
Code:
adb shell
/preinstall/restoresu
3. If you don't have superuser.apk do this as well
Code:
/preinstall/restoresu all
Apparently I am a terrible scripter, so follow eval-s instructions from here:
type in adb ("adb shell") or terminal emulator, exactly:
Code:
/preinstall/dosu
/bin/mount -o remount,rw /system
cp /preinstall/su /system/bin/
chmod 6755 /system/bin/su
PATH=/system/bin:$PATH pm install /preinstall/Superuser.apk
The last step is optional (and next-to-last *should* be unnecessary), as you can install Superuser however you like. In fact, if you've installed it, simply typing "/preinstall/su" is another way to root, and you could then mount /system read-write and copy it into /system/bin.
Click to expand...
Click to collapse
4. Enjoy
Lastly, you can make your own preinstall pretty easily, include any kind of mod you want P_ROM etc. For instance when I reinstall I always want to install wget and crond, turn off tomoyo permissions and disable the usb plugin sound. You can put apps in /preinstall/app then make a md5sum file in /preinstall/md5 and apks will get loaded on reboot every time you flash. This is more of a fyi for those of you out there cooking up sbfs. you've got a huge partition to play with so I'm sure people out there can come up with creative ways of using it.

Hi guys.. here is a useful little /preinstall for you (attached)
Put phone in fastboot mode, then:
Code:
fastboot flash preinstall preinstall.img
fastboot reboot
(older versions maybe need "fastboot -i 0x22b8")
after fastboot & reboot, type in adb ("adb shell") or terminal emulator, exactly:
Code:
/preinstall/dosu
/bin/mount -o remount,rw /system
cp /preinstall/su /system/bin/
chmod 6755 /system/bin/su
PATH=/system/bin:$PATH pm install /preinstall/Superuser.apk
The last step is optional (and next-to-last *should* be unnecessary), as you can install Superuser however you like. In fact, if you've installed it, simply typing "/preinstall/su" is another way to root, and you could then mount /system read-write and copy it into /system/bin.
Many thanks to Brandon & The2d for brainstorming this out in a crazy "there's no way it could be possible" rooting session. There were a lot of harder ways... who knew we'd be so lucky! And thanks to Edgan for the great "dosu" =)
You can find fastboot here: http://forum.xda-developers.com/showthread.php?t=1138092

Woohoo! 10 char!

Love you long time! Congrats on figuring this out!

i just unlocked my phone and wanted to root, i installed the img but when i try to enter /preinstall/dosu it gives me file path not found. do i need to reboot or something after flashing the img?

Worked a treat with gingerbread! Thanks a lot guys!
For some reasons, could not adb to go, so had to do it with the terminal but it's all good!

neotekz said:
i just unlocked my phone and wanted to root, i installed the img but when i try to enter /preinstall/dosu it gives me file path not found. do i need to reboot or something after flashing the img?
Click to expand...
Click to collapse
I am having the same problem, path not found. What can i do?

bump
Anyone else figure out how to root? Is this only for gingerbread?

-eval, would we just push that SuperUser app to our phone through ADB if we already have Gingerbread on it? Or do we just flash that through fastboot?

airbillion said:
bump
Anyone else figure out how to root? Is this only for gingerbread?
Click to expand...
Click to collapse
This will work for any firmware version

neotekz said:
i just unlocked my phone and wanted to root, i installed the img but when i try to enter /preinstall/dosu it gives me file path not found. do i need to reboot or something after flashing the img?
Click to expand...
Click to collapse
Using linux?
Sent from my MB860 using XDA Premium App

LancerV said:
Using linux?
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
I used fastboot from windows.

eval- said:
Hi guys.. here is a useful little /preinstall for you:
http://www.multiupload.com/A9X3718TXK
Put phone in fastboot mode, then:
Code:
fastboot flash preinstall preinstall.img
(older versions maybe need "fastboot -i 0x22b8")
steps:
Code:
/preinstall/dosu
/bin/mount -o remount,rw /system
cp /preinstall/su /system/bin/
PATH=/system/bin:$PATH pm install /preinstall/Superuser.apk
http://forum.xda-developers.com/showthread.php?t=1138092
Click to expand...
Click to collapse
You still need to set the permissions on SU after you copy it from preinstall.
chmod 06755 /system/bin/su

rjohnstone said:
You still need to set the permissions on SU after you copy it from preinstall.
chmod 06755 /system/bin/su
Click to expand...
Click to collapse
In adb shell when I enter the 2nd command:
adb shell
$
cd /preinstall/dosu
cd: can't cd to /preinstall/dosu
this is my output.

airbillion said:
I used fastboot from windows.
Click to expand...
Click to collapse
You have to use the linux version
Sent from my MB860 using XDA Premium App

LancerV said:
You have to use the linux version
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
Ill give it a shot. thanks

airbillion said:
In adb shell when I enter the 2nd command:
adb shell
$
cd /preinstall/dosu
cd: can't cd to /preinstall/dosu
this is my output.
Click to expand...
Click to collapse
cd /preinstall
then...
dosu
HTH

the2dcour said:
cd /preinstall
then...
dosu
HTH
Click to expand...
Click to collapse
that is what I keep on trying, but it says:
can't dosu

airbillion said:
that is what I keep on trying, but it says:
can't dosu
Click to expand...
Click to collapse
might have to wait till tomorrow when I'm done with the sbf with a 1 command install then ^^;

this worked:
Code:
adb shell
cd /preinstall
su
/bin/mount -o remount,rw /system
cp /preinstall/su /system/bin/
reboot

(SOLVED)--Require of sim unlock ...how to carry out instruction

------------------------------------SOLVED---------------------------------------------------------------------
JUST CARRIED OUT THE COMMANDS IN CWM RECOVERY ....THAT SOLVED ALL PROBLEMS
I have htc j one ...japanese htc one
Hboot is 1.52 and android 4.1.2
I have been able to s off, unlock bootloader using revone
I have flash cwm and rooted phone
Now I need to sim unlock the phone with some adb commands given in the below mentioned website :-
http://htcsoku.info/htcsokudev-news/au-m7-device-sim-unlock/
You can easily auto translate the above page if u open it in google chrome
Can anyone help me with that ?
Thanks in advance
Sent from my GT-N7000 using xda premium

download and unrar this in adb folder >>> http://www.androidfilehost.com/?fid=23159073880933098
they edited misc.img and say to do this :
adb push misc.img /
adb shell
# dd if=/misc.img of=/dev/block/mmcblk0p19
# reboot
hope it helps

criszz said:
download and unrar this in adb folder >>> http://www.androidfilehost.com/?fid=23159073880933098
they edited misc.img and say to do this :
adb push misc.img /
adb shell
# dd if=/misc.img of=/dev/block/mmcblk0p19
# reboot
hope it helps
Click to expand...
Click to collapse
Thanks for replying
I will download this file and put in adb folder
I shud do
adb push misc.img
( is this commabd correct or do I need to to put / ar back)
Then
Adb shell
It shows $ at the end
So it type
Su
Now it becomes #
Then I shud type
dd if=/misc.img of=/dev/block/mmcblk0p19
# reboot
Am I correct ?
Plz help as I am noob in this ...but am trying to learn
Sent from my GT-N7000 using xda premium

The auto-translated instructions are not good enough, and this is a very risky procedure. Fortunately, with code you usually don't need to read the words to understand it. Fortunately, with my Japanese-speaking colleague's help, I understand everything. Some things to know:
- Don't try this unless you are content to risk your phone, because I can tell he made mistakes in his instructions
- To reiterate, you either need to follow his incorrect instructions or you need to listen to me (why would you do that?)
- Look at the code blocks--all that code is meant to be run on your computer while the phone is connected to USB.
- There is only one complicated step, and this is the one with the incorrect instructions.
What he says:
Open misc.img in a hex editor, represent [00001023] as [11] and save. If you are lazy, use the file I modified already. <link>
There are two problems with this statement. First, "00001023" is not a reasonable position in the file. It means "line 10, column 3" (lines start with zero, columns start with zero). But there are 16 bytes per line, so what he really means is "byte 147". (Each pair of hex characters is a byte. The lowest value is 00, the highest value is ff.)
The second problem is that in his "already modified" file, that byte is "00", not "11". This is what I expected, because it's not reasonable for number="11" to mean "unlocked". More likely, "11" is his carrier and "00" is when the phone is unlocked.
What I advise is getting your carrier to unlock the phone, and if that's not possible, proceed only if you are willing to risk your phone. Follow his instructions, but when you get your misc.img file, download his modified version and compare them. If they differ in only one position, install his file to your phone (as per the instructions). If they are very different but the same size, you can try changing byte 147 to 00 (if the surrounding bytes are also all 00). Save the unmodified .img file, because you might be able to use it to rescue your phone if this fails.
Note: this is risky, with or without language barrier issues. At least 10% chance of bricking your phone.

Thanks a lot for your advice.
But it is not possible to carrier unlock the phone
Is there any safe way to sim unlock the phone ?
Currently am stuck ...
Sent from my GT-N7000 using xda premium

sitanshu91 said:
But it is not possible to carrier unlock the phone
Is there any safe way to sim unlock the phone ?
Click to expand...
Click to collapse
I think it's probably safe to flash the misc.img file he uploaded and linked to, if (and only if) it is exactly the same as yours, except for that one byte. Low chance of bricking the phone.

But currently can you tell me to how to pull the image coz I havr followed his command ...
Adb shell
It strt with $
Su
Now # come
Then somd dd comand
Here it shows operation cannot complete(will update what is exactly error in few min)
Exit
Adb pull misc.img
Here it shows error device not detected
Can you help me to first pull file so I can compare
Sent from my GT-N7000 using xda premium

Weird... you got a successful ADB shell, then it stopped detecting your device? I suppose you should just try again.
My phone is not the same as yours, so you shouldn't compare your partition19 to mine. You have a phone specific to Japan, right?

fenstre said:
Weird... you got a successful ADB shell, then it stopped detecting your device? I suppose you should just try again.
My phone is not the same as yours, so you shouldn't compare your partition19 to mine. You have a phone specific to Japan, right?
Click to expand...
Click to collapse
see this is what i get
C:\adb\adt-bundle-windows-x86-20131030\sdk\platform-tools>adb shell
[email protected]:/ $ su
su
[email protected]:/ # dd if=/dev/block/mmcblk0p19 of=/misc.img
dd if=/dev/block/mmcblk0p19 of=/misc.img
/misc.img: cannot open for write: Read-only file system
1|[email protected]:/ #
can you tell me why it says " /misc.img: cannot open for write: Read-only file system "
requesting your help
thanks

sitanshu91 said:
can you tell me why it says " /misc.img: cannot open for write: Read-only file system "
Click to expand...
Click to collapse
That's actually normal (because you're not supposed to write to the root of the phone's filesystem). Every time the instructions say "/", you can replace it with "/sdcard/", and every time they say "/misc.img", you can think "/sdcard/misc.img". (The instructions were carelessly written.)

fenstre said:
That's actually normal (because you're not supposed to write to the root of the phone's filesystem). Every time the instructions say "/", you can replace it with "/sdcard/", and every time they say "/misc.img", you can think "/sdcard/misc.img". (The instructions were carelessly written.)
Click to expand...
Click to collapse
so you say i should proceed
see again i did the same
C:\adb\adt-bundle-windows-x86-20131030\sdk\platform-tools>adb devices
List of devices attached
HT35Z******* device
C:\adb\adt-bundle-windows-x86-20131030\sdk\platform-tools>adb shell
[email protected]:/ $ su
su
[email protected]:/ # dd if=/dev/block/mmcblk0p19 of=/misc.img
dd if=/dev/block/mmcblk0p19 of=/misc.img
/misc.img: cannot open for write: Read-only file system
1|[email protected]:/ # exit
exit
1|[email protected]:/ $ adb pull misc.img
adb pull misc.img
* daemon not running. starting it now on port 5038 *
* daemon started successfully *
error: device not found
1|[email protected]:/ $
now how should i proceed ....please help

Guys requesting help before the new year starts
So I can use my phone in new year
Sent from my GT-N7000 using xda premium

sitanshu91 said:
/misc.img: cannot open for write: Read-only file system
Click to expand...
Click to collapse
are you doing this is fastboot? / recovery? is your device bootloader unlocked through htc dev?

Kasi!995 said:
are you doing this is fastboot? / recovery? is your device bootloader unlocked through htc dev?
Click to expand...
Click to collapse
yes this is unlocked bootloader ...i have done it thru revone
now i have installed busybox
and i can progress
C:\adb\adt-bundle-windows-x86-20131030\sdk\platform-tools>adb devices
List of devices attached
HT3******* device
C:\adb\adt-bundle-windows-x86-20131030\sdk\platform-tools>adb shell
[email protected]:/ $ su
su
[email protected]:/ # dd if=/dev/block/mmcblk0p19 of=/misc.img
dd if=/dev/block/mmcblk0p19 of=/misc.img
2045+0 records in
2045+0 records out
1047040 bytes transferred in 0.106 secs (9877735 bytes/sec)
[email protected]:/ # exit
exit
[email protected]:/ $ adb pull misc.img
adb pull misc.img
* daemon not running. starting it now on port 5038 *
* daemon started successfully *
error: device not found
1|[email protected]:/ $
can you help me now
i want to do as written in this
http://htcsoku.info/htcsokudev-news/au-m7-device-sim-unlock/
thanks

sitanshu91 said:
can you help me now
i want to do as written in this
http://htcsoku.info/htcsokudev-news/au-m7-device-sim-unlock/
thanks
Click to expand...
Click to collapse
what Recovery do you have flashed? TWRP?

Its cwm recovery
Sent from my GT-N7000 using xda premium

Run adb pull outside of adb shell.

1st problem :-
C:\adb\adt-bundle-windows-x86-20131030\sdk\platform-tools>adb shell
[email protected]:/ $ su
su
[email protected]:/ # dd if=/dev/block/mmcblk0p19 of=/misc.img
dd if=/dev/block/mmcblk0p19 of=/misc.img
2045+0 records in
2045+0 records out
1047040 bytes transferred in 0.106 secs (9877735 bytes/sec)
[email protected]:/ # exit
exit
[email protected]:/ $ adb pull misc.img
adb pull misc.img
* daemon not running. starting it now on port 5038 *
* daemon started successfully *
error: device not found
1|[email protected]:/ $
can you tell me where is my mistake
What can I do can you type command
2nd problem
similiarly when i try
C:\adb\adt-bundle-windows-x86-20131030\sdk\platform-tools>adb push misc.img /
failed to copy 'misc.img' to '//misc.img': Permission denied
request you to please help me
thanks and regards
Sent from my GT-N7000 using xda premium

what is your status now?

criszz said:
what is your status now?
Click to expand...
Click to collapse
i am very glad that you asked .....happy new year
Now my status is sim unlocked ....but i can use only to make and receive phone calls and sms ...
now here is the problem
i cant use data (2g/3g) on my phone
do u know how to do that
thanks
sitanshu

Can't press power button in recovery mode

Well, after wiping data using adb shell I wanted to install a rom with CWM recovery that was already installed from someone but as soon as I got on recovery mode power button was unable to press. When phone is on or off, power button works perfect. The problem is in the recovery mode. Is there any way I can flash the rom and the gapps without using my phones buttons? Through adb maybe?

Dont use cwm, its outdated, install twrp 2.8.6.0.

Marko055 said:
Dont use cwm, its outdated, install twrp 2.8.6.0.
Click to expand...
Click to collapse
Ok mate, I'll give it a try. Is there anyway I can install it from adb? Because my cwm don't let me press the powerbutton and also I dont have access to my rom because I cant install gapss

Installation guide:
[Method 1° ~ fastboot]
Code:
$ adb reboot oem-unlock
$ fastboot flash recovery /PATH-TO-THE-IMG-FOLDER-ON-YOUR-COMPUTER/twrp.img
$ fastboot reboot
[Method 2° ~ adb] (put the recovery.img in your sdcard)
Code:
$ adb shell
$ su
# cat /sdcard/twrp.img > /dev/block/mmcblk0p1
# sync
# exit
$ exit

Marko055 said:
[Method 2° ~ adb] (put the recovery.img in your sdcard)
Code:
$ adb shell
$ su
# cat /sdcard/twrp.img > /dev/block/mmcblk0p1
# sync
# exit
$ exit
Click to expand...
Click to collapse
Worked like a charm thank you so much for your help!

zhulk13 said:
Worked like a charm thank you so much for your help!
Click to expand...
Click to collapse
One more thing, install theme, its way better for eyes.
http://forum.xda-developers.com/android/themes/theme-twrp-materialised-dark-light-play-t2915584

Marko055 said:
One more thing, install theme, its way better for eyes.
http://forum.xda-developers.com/android/themes/theme-twrp-materialised-dark-light-play-t2915584
Click to expand...
Click to collapse
Wow! I didn't even know that there are themes for recoveries! Thank you very much!!