Ok, trying to edit framework-res.apk. I have a metamorph them running, and I also have a battery that got changed via update.zip. The problem is, I wanted the battery to be all white, rather than colored in order to fit with my black and white theme.
So I pulled my framework-res.apk, took out the battery .png's, and edited them. Then I put them back in. Problem is, I can't get it on my phone.
I tried putting the new framework-res.apk in the old update.zip and flashing it, but that just made my battery meter disappear. I tried adb push, but I got a permission denied error. Any help? First .apk edit.
adb pushing shoulda worked... what did the error say?
failed to copy 'framework-res.apk' to '/system/framework/framework-res.apk': Per
mission denied
Click to expand...
Click to collapse
That's the error I get. Not sure what I have to do to get permission to edit?
E_man5112 said:
That's the error I get. Not sure what I have to do to get permission to edit?
Click to expand...
Click to collapse
Do
Code:
Adb remount
first. Then push
adb remount only gives me another error
Code:
remount failed: No such file or directory
K go in recovery, cuz thts the safest place to push framework-res.apk
Once in recovery and ur phone connected to ur pc
After a few seconds (20'ish)
Type
Code:
adb shell
mount /system
exit
adb push <drag framework-res.apk here> /system/framework/framework-res.apk
adb shell reboot
This is harder than I though.
Code:
adb shell
$ mount /system
mount /system
mount: not found
Now what?
E_man5112 said:
This is harder than I though.
Code:
adb shell
$ mount /system
mount /system
mount: not found
Now what?
Click to expand...
Click to collapse
lol. k wht recovery u using ?
stock recovery
Code:
adb reboot recovery
E_man5112 said:
stock recovery
Code:
adb reboot recovery
Click to expand...
Click to collapse
lol time to upgrade to amon-ra recovery bro. also...make sure u signed ur files or else nothing works...assuming you're not a complete noob.
E_man5112 said:
stock recovery
Code:
adb reboot recovery
Click to expand...
Click to collapse
yea wht opasha said. u need root/custom recovery to modify system apps. sorry.
Will clockwork recovery do the trick?
Sent from my SAMSUNG-SGH-I897 using XDA App
E_man5112 said:
Will clockwork recovery do the trick?
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Yup it'll do.
Ok, making progress, /system mounts, so I type
Code:
adb shell
su
mount /system
exit
adb push framework-res.apk /system/framework/framework-res.apk
and I get
Code:
/sbin/sh: adb: not found
in your above post, you didn't mention su, but /system won't mount unless I'm root user, so I don't know any other way to do it? exit keeps me in the shell it seems (I still have ~$) but exiting again kicks me out of adb all together, then if I restart, I'm back at the permission denied error.
opasha said:
lol time to upgrade to amon-ra recovery bro. also...make sure u signed ur files or else nothing works...assuming you're not a complete noob.
Click to expand...
Click to collapse
Bad assumption I really am
How do I sign my files?
Related
I've been trying to figure out how to fix my phone and through using the adb logcat the only thing left is just getting the core.jar file in the /system/framework to change from read only to rw. Each time I try to change it it says its read only or bad mode. Any ideas?
Metatronx said:
I've been trying to figure out how to fix my phone and through using the adb logcat the only thing left is just getting the core.jar file in the /system/framework to change from read only to rw. Each time I try to change it it says its read only or bad mode. Any ideas?
Click to expand...
Click to collapse
try
Code:
adb remount
What would the syntax be for remounting the core.jar and is it possible to do in terminal? Thank you especially for the quick response\!
From your other thread..
The entire /system partition is always read-only, unless you tell your phone to remount it read-write.
Code:
mount -o remount,rw /dev/block/mtdblock3 /system
But for your problem.. You shouldn't really need to manually tweak files in /system if you flash another ROM. The new ROM will replace that entire partition. Have you wiped? What ROM are you trying to flash?
Kudos for using logcat and trying to jump in yourself though.
Hi,
I have a T-Mobile G1.
It was in Android 1.5 when I received it.
I rooted it woth the "one click" method (flashrec 1.1.2) using recovery-RA-dream-v1.2.2.img.
It worked fine, and I was able to test some ROMS.
But the last one I installed, Android 1.6 User debug from HTC, doesn't allow to get root access again.
The one click method doesn't work anymore. I get "Could not run command".
The Fastboot method doens't work anymore too.
I'm stuck with the 1.6 "Android dev phone 1".
Anyone has an idea ?
Thanks,
Yves
yvesg said:
Hi,
I have a T-Mobile G1.
It was in Android 1.5 when I received it.
I rooted it woth the "one click" method (flashrec 1.1.2) using recovery-RA-dream-v1.2.2.img.
It worked fine, and I was able to test some ROMS.
But the last one I installed, Android 1.6 User debug from HTC, doesn't allow to get root access again.
The one click method doesn't work anymore. I get "Could not run command".
The Fastboot method doens't work anymore too.
I'm stuck with the 1.6 "Android dev phone 1".
Anyone has an idea ?
Thanks,
Yves
Click to expand...
Click to collapse
if i remember right the 1 click root only works with 1.5 and wont work with 1.6 . if you made a nandroid back up before you flash the 1.6 i think you can restore from there to get root .read threw the thread on 1.6 i think there was some mention of this !
yvesg said:
It worked fine, and I was able to test some ROMS.
But the last one I installed, Android 1.6 User debug from HTC, doesn't allow to get root access again.
The Fastboot method doens't work anymore too.
I'm stuck with the 1.6 "Android dev phone 1".
Click to expand...
Click to collapse
I think you have still root. Do you have adb installed?
Try this one:
Code:
adb root
adb shell
Now you should get the root-prompt ("#").
The reason why you can't flash any other rom anymore is because the recovery-img operates with wrong keys (that's what I think).
What you could do now is to reflash the recovery by using the flash_image command (you have to copy the flash-image-binary on your phone first - extract it from any other rom - it's located in /system/bin).
So, copy the flash_image binary to your phone:
Code:
adb remount
adb push flash_image /system/bin/.
adb shell chmod 0755 /system/bin/flash_image
Now copy the recovery-image you want on your phone:
Code:
adb push recovery.img /sdcard/.
Flash the recovery:
Code:
adb root
adb shell flash_image recovery /sdcard/recovery.img
Now ... boot into recovery-mode ([power]+[home]) and reflash your phone with whatever you like. Since fastboot doesn't work for you I guess you have never replaced the original SPL.
And ... what I've heard ... the ADP1.6-firmware will check the recovery on boot and will reflash it every time!
You could also check this site.
lucky 69 said:
if i remember right the 1 click root only works with 1.5 and wont work with 1.6 . if you made a nandroid back up before you flash the 1.6 i think you can restore from there to get root .read threw the thread on 1.6 i think there was some mention of this !
Click to expand...
Click to collapse
I ashamed, but I didn't do the backup :-( .....
yvesg said:
I ashamed, but I didn't do the backup :-( .....
Click to expand...
Click to collapse
Try what Harry wrote.
harry_m said:
I think you have still root. Do you have adb installed?
Try this one:
Code:
adb root
adb shell
Now you should get the root-prompt ("#").
The reason why you can't flash any other rom anymore is because the recovery-img operates with wrong keys (that's what I think).
What you could do now is to reflash the recovery by using the flash_image command (you have to copy the flash-image-binary on your phone first - extract it from any other rom - it's located in /system/bin).
So, copy the flash_image binary to your phone:
Code:
adb remount
adb push flash_image /system/bin/.
adb shell chmod 0755 /system/bin/flash_image
Now copy the recovery-image you want on your phone:
Code:
adb push recovery.img /sdcard/.
Flash the recovery:
Code:
adb root
adb shell flash_image recovery /sdcard/recovery.img
Now ... boot into recovery-mode ([power]+[home]) and reflash your phone with whatever you like. Since fastboot doesn't work for you I guess you have never replaced the original SPL.
And ... what I've heard ... the ADP1.6-firmware will check the recovery on boot and will reflash it every time!
You could also check this site.
Click to expand...
Click to collapse
Hi,
Thanks a lot.
I'm now able to get root access and I'm about to flash the G1.
I thaught I replaced the SPL, but I'm not sure .... I've tried so much things since I have this phone (since last sunday) .....
Again, thank you for your help.
Yves
ooops,
"Installation aborted", during the apply of update.zip.
Now the phone is bricked.
I'm going to format my sdcard and retry the flash ....
Same error :
(No such file or directory)
E:Failure at line 80:
set_perm_recursive 0 2000 0755 06755 SYSTEM:xbin
Installation aborted.
redownload the rom
Spon4ik said:
redownload the rom
Click to expand...
Click to collapse
Meanwhile, I try with another rom and it seems to work ....
Thanks again for your help.
In fact, I can only flash with HTC SIGNED roms .....
I tried several others and each crash the same way
If you ask me ... the above mentioned error
Code:
E:Failure at line 80:
set_perm_recursive 0 2000 0755 06755 SYSTEM:xbin
has nothing to do with a wrong-signed rom!
SPL
yvesg said:
In fact, I can only flash with HTC SIGNED roms .....
I tried several others and each crash the same way
Click to expand...
Click to collapse
would this have to do with the SPL? similar to not being able to flash a EUR ROM on a USA phone .. you have to flash the HardSPL etc in order to switch ROMs
Or you could just gain root access manually the way those of us who had RC30 did...
You are may be right about the HardSPL.
When I try to flash it, (with Camera + Power), I get "not allow".
After I got my nexus back from HTC for a faulty power button, my nexus has been rooted via a replaced motherboard. Now I have already root my phone and unlocked the bootloader, however when I try to flash the recovery image I get
sending 'recovery' (4074 KB)... OKAY
writing 'recovery'... FAILED (remote: image update error)
Also I can somehow access recovery, and it looks as it should. However when I try to backup my rom it says "Run 'nandroid-moblie.sh' via adb!" and similar things when I try any other the other options. Could someone please help with this?
How are you trying to flash it? Fastboot is the best foolproof way to do flash the recovery. I have never really seen that error before, what recovery are you trying to flash?
Your nandroid error is most likely because the sdcard thinks it's still mounted, or is mounted. Also, I don't know if this still happens but make sure you only do a backup, not backup +ext if you don't have an ext partition on the sdcard.
he's obviously using fastboot...
Did you make sure recovery.img had the right MD5 hashes as amon_ra posted?
I have check the MD5 checksums, and they match up. Also, i am using fastboot to flash, and I am trying to flash RA-nexus v2.0.0. Are you suggesting that I remount the sd card to get it to flash the recovery image?
cajer said:
I have check the MD5 checksums, and they match up. Also, i am using fastboot to flash, and I am trying to flash RA-nexus v2.0.0. Are you suggesting that I remount the sd card to get it to flash the recovery image?
Click to expand...
Click to collapse
I would suggest you try in command line with the adb commands as follows:
adb shell
su
mount -o rw,remount /dev/block/mtdblock4 /system
cat /sdcard/flash_image > /system/bin/flash_image
chmod 775 /system/bin/flash_image
flash_image recovery /sdcard/recovery.img
rm /system/etc/install-recovery.sh
rm /system/recovery-from-boot.p
reboot recovery
You need flash_image for this, check the wiki for the file...don't forget to put the recovery in the root of the sdcard and rename it to recovery.img for convenience purpose
gravufo said:
I would suggest you try in command line with the adb commands as follows:
adb shell
su
mount -o rw,remount /dev/block/mtdblock4 /system
cat /sdcard/flash_image > /system/bin/flash_image
chmod 775 /system/bin/flash_image
flash_image recovery /sdcard/recovery.img
rm /system/etc/install-recovery.sh
rm /system/recovery-from-boot.p
reboot recovery
You need flash_image for this, check the wiki for the file...don't forget to put the recovery in the root of the sdcard and rename it to recovery.img for convenience purpose
Click to expand...
Click to collapse
What do I do with flash_image? Also this device came back stock with frg 83, which I am trying to flash the recovery on. When I type in adb shell, I get "error: device not found" even though I can see it through "fastboot devices".
cajer said:
What do I do with flash_image? Also this device came back stock with frg 83, which I am trying to flash the recovery on. When I type in adb shell, I get "error: device not found" even though I can see it through "fastboot devices".
Click to expand...
Click to collapse
flash image has to be placed in the root of your sd card as well as the recovery!
As for the adb shell, try enabling USB Debugging in Setting > Applications > Development
Make sure you're rooted too (use SuperOneClick if you're not already)
I can get through that string of commands until
rm /system/etc/install-recovery.sh
rm /system/recovery-from-boot.p
reboot recovery
Then it says "No such file or directory". I have already rooted, and both the flash_image and recovery file have been placed in the root directory of the sd card.
Well, after you did that string of commands, does the problem persist?
Also, do you have at least 400MB free on your SD card?
Well, I can't get
rm /system/etc/install-recovery.sh
rm /system/recovery-from-boot.p
reboot recovery
to work as it responds with "No such file or directory". Even if I go through after the errors, the recovery still gives 'nandroid-moblie.sh' via adb!" and similar messages. Do I need to find a way to put the file install-recovery.sh in my sd card root directory if so, where can I get it? In addition when I try to flash recovery with nexus one superboot I get "(remote: signature verify fail)" even though the MD5 sum matches up.
Yes I have over 5 gbs on the sd card.
rm = remove
The steps you are trying to perform with the 2 rm command is to remove the 2 files that automatically rewrite your recovery.
If you reboot without succeeding in removing these files, the recovery image you just flashed will be written over by the stock recovery...
Since you have rebooted, and are still having the problem, you need to do the whole list of commands again... be careful how you type...
Sent from my Nexus One using XDA App
Danger, it seems as I can't remove those two files as I get the error message "rm failed for /system/etc/install-recovery.sh, No such file or directory". Any ways to successfully remove them?
Sounds like the files aren't actually there then, unless you're making a typing error...
Did your recovery update after the last attempt? Did it look different, what is the recovery version that is listed on the recovery screen?
Sent from my Nexus One using XDA App
I have been flashing different themed recoveries to see if any data transfers, and the background changes. But as before the actions all say "Run 'nandroid-moblie.sh' via adb!" or something similar.
cajer said:
I have been flashing different themed recoveries to see if any data transfers, and the background changes. But as before the actions all say "Run 'nandroid-moblie.sh' via adb!" or something similar.
Click to expand...
Click to collapse
if the rm doesn't work it's fine.
But what about your flashing command? It simply works or outputs an error too?
When u flashed themed ones, did the background change?
The background did change when I flashed the themed ones, however it still outputs errors like "Run 'nandroid-moblie.sh' via adb!" when i try to run any of the options under recovery. The fastboot flashing command gives this "writing 'recovery'... FAILED (remote: image update error)" error.
cajer said:
The background did change when I flashed the themed ones, however it still outputs errors like "Run 'nandroid-moblie.sh' via adb!" when i try to run any of the options under recovery. The fastboot flashing command gives this "writing 'recovery'... FAILED (remote: image update error)" error.
Click to expand...
Click to collapse
When you try running a NAND backup or restore a previous NAND?
When restoring, the backup must be at the exact position where it was when you did it: /sdcard/nandroid/HT#####/BCD######
I was trying to backup my current image, and this happens with all other actions even the shut down action on the recovery page just with "Run 'reboot -p' via adb!"
lawl xD that seems useful...
well, that's extremely odd to be honest...uhm...I think you should try and contact amon_ra if possible...He knows the code of his recovery and might know what's wrong...
I really have no clue, sorry =\
PS: Have u tried clockworkmod recovery?
Alright I will try contacting amon_ra, and I will try clockwork tomorrow. I was going for amon_ra recovery to get Sense HD on it with sd partition. Thanks for the help though I learned more stuff about my phone.
EDIT: Wow, clockwork installed like a charm, and I didn't even have to do anything. I'm now a clockwork convert.
MIne is Nexus one. It's just rooted.
http://forum.xda-developers.com/showthread.php?t=611829 the newest Ra recovery for n1 is here.
There was a note:
Install
Pre-Requirements :
Root
Make sure that init.rc isn't calling any install-recovery.sh script, otherwise you'll boot back to stock recovery (exclamation mark with a little Android).
I tried on my n1 and I booted back to stock recovery......
How could I fix it?
philanini said:
MIne is Nexus one. It's just rooted.
http://forum.xda-developers.com/showthread.php?t=611829 the newest Ra recovery for n1 is here.
There was a note:
Install
Pre-Requirements :
Root
Make sure that init.rc isn't calling any install-recovery.sh script, otherwise you'll boot back to stock recovery (exclamation mark with a little Android).
I tried on my n1 and I booted back to stock recovery......
How could I fix it?
Click to expand...
Click to collapse
after you flash the recovery, without rebooting, just run these two commands:
rm /system/etc/install-recovery.sh
rm /system/recovery-from-boot.p
gravufo said:
after you flash the recovery, without rebooting, just run these two commands:
rm /system/etc/install-recovery.sh
rm /system/recovery-from-boot.p
Click to expand...
Click to collapse
Thank you friend.
I used the fastboot-windows.exe in cmd to flashed the recovery ,and I don't know where to run your cammands.
philanini said:
Thank you friend.
I used the fastboot-windows.exe in cmd to flashed the recovery ,and I don't know where to run your cammands.
Click to expand...
Click to collapse
Alright, open a command prompt into adb shell (or use terminal emulator from your phone) and run the following. Note that you don't need to run the first command if you're doing it from the terminal emulator on the phone.
adb shell
su
mount -o rw,remount /dev/block/mtdblock3 /system
rm /system/etc/install-recovery.sh
rm /system/recovery-from-boot.p
reboot recovery
After you run these commands, you should flash the recovery again and you should have no problem!
Good luck!
Eeeeeek - sorry!
gravufo said:
Alright, open a command prompt into adb shell (or use terminal emulator from your phone) and run the following. Note that you don't need to run the first command if you're doing it from the terminal emulator on the phone.
adb shell
su
mount -o rw,remount /dev/block/mtdblock3 /system
rm /system/etc/install-recovery.sh
rm /system/recovery-from-boot.p
reboot recovery
After you run these commands, you should flash the recovery again and you should have no problem!
Good luck!
Click to expand...
Click to collapse
Thank you man! I will post the result.
gravufo said:
Alright, open a command prompt into adb shell (or use terminal emulator from your phone) and run the following. Note that you don't need to run the first command if you're doing it from the terminal emulator on the phone.
adb shell
su
mount -o rw,remount /dev/block/mtdblock3 /system
rm /system/etc/install-recovery.sh
rm /system/recovery-from-boot.p
reboot recovery
After you run these commands, you should flash the recovery again and you should have no problem!
Good luck!
Click to expand...
Click to collapse
Thank you my friend. I tried what you've told me, unfortunately,and it said not found there.
However, I tried MiuiRomInstaller.apk ,it flashed a clorkworkmod recovery. Then I flashed RA recovery back, luckily I succeeded!
I could use that change my rom now.
Thank you Gravufo.
philanini said:
Thank you my friend. I tried what you've told me, unfortunately,and it said not found there.
However, I tried MiuiRomInstaller.apk ,it flashed a clorkworkmod recovery. Then I flashed RA recovery back, luckily I succeeded!
I could use that change my rom now.
Thank you Gravufo.
Click to expand...
Click to collapse
Your welcome, glad it worked one way or the other
gravufo said:
Your welcome, glad it worked one way or the other
Click to expand...
Click to collapse
Man~I restored and tried your way again, This ok now.Thank you!
My recovery got blown-up and when I try to install another recovery, from # mount /sdcard , I get mount: can't read
/etc/fstab: No such file or directory
or from adb mount shell /sdcard , I get the same thing.. How do I format the sdcard or whatever it needs to be able to mount it from the # prompt , or adb ?
Thanks for any help..
I'm trying to get sdk manager working, can I get in to flash a recovery thru fastboot ?
have you tried using terminal emulator? also, are you s-off?
Did you change your directory??? As in cd\???
And which method did you choose to install adb??? And are you just trying to install a recovery from adb??? If so then change the directory then try mount -a then try the flash recovery commands. Good luck
Yea its me Again With the
Modified Hero-
Yes terminal, CMD rooted but not x-off
I'm in the platform-tools dir of sdk , when I >adb shell mount -a I get /etc/fstab: No such file or directory.
Houndog101 said:
Yes terminal, CMD rooted but not x-off
I'm in the platform-tools dir of sdk , when I >adb shell mount -a I get /etc/fstab: No such file or directory.
Click to expand...
Click to collapse
what happened when you tried the terminal method? it should work. Make sure the recovery image is on your sd, in no folder at all, rename it to recovery.img. Then in TE type: su , then press enter. then type: flash_image recovery /sdcard/recovery.img , then press enter - what happens?
il Duce said:
what happened when you tried the terminal method? it should work. Make sure the recovery image is on your sd, in no folder at all, rename it to recovery.img. Then in TE type: su , then press enter. then type: flash_image recovery /sdcard/recovery.img , then press enter - what happens?
Click to expand...
Click to collapse
Problem is I can't get the program on my SD . I think my sd has gotten corrupted some how . I need a linux command to format the sd card so it can be mounted. I can get to SU . if this help,, I really appericate any help I can get, Thank you..
Houndog101 said:
Yes terminal, CMD rooted but not x-off
I'm in the platform-tools dir of sdk , when I >adb shell mount -a I get /etc/fstab: No such file or directory.
Click to expand...
Click to collapse
From the command line type
Cd\ "hit enter"
Then
cd\AndroidSDk\tools\ " hit enter"
Then mount -a if you want to mount your sd card "hit enter"
Or adb shell "hit enter"
To use adb
Or adb remount to mount your file directory/system " I think "
Or just use the commands to flash your recovery.
Yea its me Again With the
Modified Hero-
OK, I'll do that and get back.. Thanks.
Houndog101 said:
Problem is I can't get the program on my SD . I think my sd has gotten corrupted some how . I need a linux command to format the sd card so it can be mounted. I can get to SU . if this help,, I really appericate any help I can get, Thank you..
Click to expand...
Click to collapse
Are you running windows or linux on your computer??? And y not just take your card out and format threw your pc or via card reader???
Edit : don't forget to name your recovery correctly as in
recovery-RA-heroc-v.1.7.img
If your trying to flash RA
And make sure it reads on your sd/card correctly as in .img and not
img.img
So to flash RA for example would be
flash_image recovery /sdcard/recovery-RA-heroc-v.1.7.img
Yea its me Again With the
Modified Hero-
I'm gonna reinstall sdk, takes a while , then I'll post results..
thanks again.
Houndog101 said:
I'm gonna reinstall sdk, takes a while , then I'll post results..
thanks again.
Click to expand...
Click to collapse
If your by chance looking for an easy way to setup adb you can check out my thread in hero development section on how to install adb on windows. It takes like 15/20 min tops to have it all setup. That's if your using windows. Good luck
Yea its me Again With the
Modified Hero-
Houndog101 said:
I'm gonna reinstall sdk, takes a while , then I'll post results..
thanks again.
Click to expand...
Click to collapse
ok, but I still don't get why you can't boot into the ROM you're on, open the terminal emulator app, and follow the instructions, it should work.
il Duce said:
ok, but I still don't get why you can't boot into the ROM you're on, open the terminal emulator app, and follow the instructions, it should work.
Click to expand...
Click to collapse
I agree that should work. Would be way easier as well.
Yea its me Again With the
Modified Hero-
laie1472 said:
Are you running windows or linux on your computer??? And y not just take your card out and format threw your pc or via card reader???
Edit : don't forget to name your recovery correctly as in
recovery-RA-heroc-v.1.7.img
If your trying to flash RA
And make sure it reads on your sd/card correctly as in .img and not
img.img
So to flash RA for example would be
flash_image recovery /sdcard/recovery-RA-heroc-v.1.7.img
Yea its me Again With the
Modified Hero-
Click to expand...
Click to collapse
I don't have a card reader that small . wierd because from su
prompt # ls , its says the sdcard is there, but when I try to mount it I get, " mount: can't read
/etc/fstab: No such file or directory"
il Duce said:
ok, but I still don't get why you can't boot into the ROM you're on, open the terminal emulator app, and follow the instructions, it should work.
Click to expand...
Click to collapse
I can only boot to the 3 skateboard screen.
Houndog101 said:
I can only boot to the 3 skateboard screen.
Click to expand...
Click to collapse
oh, ok then. adb for you.
il Duce said:
oh, ok then. adb for you.
Click to expand...
Click to collapse
When I " adb push recovery-RA-heroc-v1.6.2.img /sdcard/recovery-RA-heroc-v1.6.2.img"
I get failed to copy 'push recovery-RA-heroc-v1.6.2.img /sdcard/recovery-RA-heroc-v1.6.2.img' : Read-only filesystem
Geez, been at this for 2 days now.. I'm at a lost..
Ok well lets start from the beginning then. When your at your command line are you typing su??? If so you don't have to. And y are you trying to push the recovery instead of flashing it????
Yea its me Again With the
Modified Hero-
laie1472 said:
Ok well lets start from the beginning then. When your at your command line are you typing su??? If so you don't have to. And y are you trying to push the recovery instead of flashing it????
Yea its me Again With the
Modified Hero-
Click to expand...
Click to collapse
ok, I type adb shell and I get the # prompt
then at the # prompt I type #flash_image recovery /sdcard/recovery-RA-heroc-v1.6.2.img
hit enter and I get Failed with error: -1