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
Related
I currently am running an older version of jf's recovery image and would like to upgrade to Cm recovery 1.4.
I have looked through the fourms and can't find any help on installing a new recovery image over the old one. I was just wondering if I would have to install it like I did with the first one, downgrade my phone and all that or is there a way I can insatll it with out having to do all those steps over again.
Thanks for you help in advance
Ps. Didn't really know where to post this thread sorry if it is in the wrong area..
Hi,
This should really be in the Q&A section.
To answer your question, save the .img on to your SD card, do not rename it, go to your terminal emulator and type flash_image recovery /sdcard/cm-recovery-1.4.img
As long as you did not rename the file, and you spell the commands right, then you should be golden.
QUESTION !!!!!!!!!! >>>> Q&A Section !!!
don't forget the su. also you will want to do reboot recovery so you can see your pretty new recovery image.
thanks
Thanks for all the help guys
ps
And I guess I brain farted not putting it in the Q&A section, my bad
still not working
ironnius said:
Hi,
This should really be in the Q&A section.
To answer your question, save the .img on to your SD card, do not rename it, go to your terminal emulator and type flash_image recovery /sdcard/cm-recovery-1.4.img
As long as you did not rename the file, and you spell the commands right, then you should be golden.
Click to expand...
Click to collapse
I did what you said it it didn't work, it gave me the message, this was all done in terminal emulator.
"error writing recovery : Permission denied"
Is there something i have to do to allow this?
do the following in terminal emu
su
flash_image recovery /sdcard/cm-recovery-1.4.img
Put the recovery img on the root of your ad card
Installing the CyangenMod Recovery IMG
1. Open up the Terminal App on your phone
2. Type in su then press on "Always Allow"
3. Type in the following:
Code:
cd /sdcard
wget http://n0rp.chemlab.org/android/cm-recovery-1.4.img
flash_image recovery /sdcard/cm-recovery-1.4.img4. Done! Easy as Pie
Fingerlickin said:
do the following in terminal emu
su
flash_image recovery /sdcard/cm-recovery-1.4.img
Click to expand...
Click to collapse
thank you that worked
1sickat said:
Put the recovery img on the root of your ad card
Installing the CyangenMod Recovery IMG
1. Open up the Terminal App on your phone
2. Type in su then press on "Always Allow"
3. Type in the following:
Code:
cd /sdcard
wget http://n0rp.chemlab.org/android/cm-recovery-1.4.img
flash_image recovery /sdcard/cm-recovery-1.4.img4. Done! Easy as Pie
Click to expand...
Click to collapse
yes please download the recovery image and put it on the sdcard, THEN download the recovery image AGAIN using the wget command and replace the first one. THEN use the flash_image command which requires su permissions WITHOUT getting those permissions first.
Sorry, in a bad mood today.
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?
I rooted using UniversalAndRoot, which worked according to the app. Installed ROM Manager and flashed ClockworkMod Recovery.
This is where I stumble. I've tried selecting Reboot into Recovery, Install from SD, powering up with Vol Down pressed and selecting Recovery. All three boot as far as the X, flash a bit of white at the bottom of the screen then the phone turns off.
Waiting for a minute/pressing buttons or pulling the battery lets me boot back up fine, but I still can't boot into Recovery.
I've tried choosing install AltRecovery and old versions of Clockwork but they both behave the same way.
Any advice guys? Is it because I rooted with UniAndRoot?
top_bunk said:
I rooted using UniversalAndRoot, which worked according to the app. Installed ROM Manager and flashed ClockworkMod Recovery.
This is where I stumble. I've tried selecting Reboot into Recovery, Install from SD, powering up with Vol Down pressed and selecting Recovery. All three boot as far as the X, flash a bit of white at the bottom of the screen then the phone turns off.
Waiting for a minute/pressing buttons or pulling the battery lets me boot back up fine, but I still can't boot into Recovery.
I've tried choosing install AltRecovery and old versions of Clockwork but they both behave the same way.
Any advice guys? Is it because I rooted with UniAndRoot?
Click to expand...
Click to collapse
You probably have SLCD screen. Then you have to use Amon_RA 1.8.0.1 recovery which is only one (as far as i know) intended for SLCD screens.
Ah okay. Is there an easy way for me to flash that? Not really comfortable with the SDK approach...
Thanks for the fast reply btw
If you don't have unlocked bootloader you have to use flash_image binary to flash new recovery because amon_ra 1.8.0.1 recovery don't show up in rom manager.
Download it from here http://cyanogen-files.carneeki.net/flash_image.zip. Put it in root of sdcard as well as 1.8.0.1 img file and in phone terminal type
1) cd /sdcard
2) flash_image recovery 1.8.0.1.img (replace with name of img file)
houmles said:
2) flash_image recovery 1.8.0.1.img (replace with name of img file)
Click to expand...
Click to collapse
I'm getting flash_image: not found
I've double checked the file name is correct
Did you unpack the zip file? There is only one file named exactly "flash_image" so you should not getting not found error if you have that file in root of sdcard and you are at /sdcard in terminal.
Send me output of "ls -la" command from /sdcard.
----rwxr-x system sdcard_rw 17638414 2010-09-10 20:20 gapps-hdpi-20100817-signed.zip
----rwxr-x system sdcard_rw 70864056 2010-09-10 20:22 update-cm-6.0.0-N1-signed.zip
----rwxr-x system sdcard_rw 11818685 2010-09-10 21:05 FRF50-radio-4_06_00_12_7.zip
----rwxr-x system sdcard_rw 4145152 2010-09-10 23:10 recovery.img
----rwxr-x system sdcard_rw 26172 2009-10-03 18:07 flash_image
Try ./flash_image instead of just flash_image.
One more thing: type this as the first command when you enter the Terminal:
su
Then type:
cd /sdcard
./flash_image recovery <insert_recovery_img_name_here>
Jack_R1 said:
Try ./flash_image instead of just flash_image.
One more thing: type this as the first command when you enter the Terminal:
su
Then type:
cd /sdcard
./flash_image recovery <insert_recovery_img_name_here>
Click to expand...
Click to collapse
./flash_image: permission denied
top_bunk said:
./flash_image: permission denied
Click to expand...
Click to collapse
Weird. Try:
1) su
2) cd /sdcard
3) chmod +x flash_image
4) ./flash_image recovery file.img
Well, that's because SD card isn't a good place to put flash_image. Permissions inherited from FAT32 are awkward and aren't changeable. But there's a way around it.
Do the following sequence: run Terminal, enter the following commands:
su
cd /sdcard
cp flash_image /data/local/tmp
chmod 755 /data/local/tmp/flash_image
/data/local/tmp/flash_image <insert_recovery_img_name_here>
houmles said:
3) chmod +x flash_image
Click to expand...
Click to collapse
Won't work for 2 reasons:
1) In Android, chmod seems not to recognize letters for permissions.
2) On SD card formatted with FAT32, the mount assigns default permissions for all files, and they can't be changed - since the file system doesn't support it.
Jack_R1 said:
Won't work for 2 reasons:
1) In Android, chmod seems not to recognize letters for permissions.
2) On SD card formatted with FAT32, the mount assigns default permissions for all files, and they can't be changed - since the file system doesn't support it.
Click to expand...
Click to collapse
It didn't work...
Jack_R1 said:
su
cd /sdcard
cp flash_image /data/local/tmp
chmod 755 /data/local/tmp/flash_image
/data/local/tmp/flash_image <insert_recovery_img_name_here>
Click to expand...
Click to collapse
cp: not found
Have any file explorer installed? Astro / EStrongs / whatever?
Copy the file manually in file explorer, and skip the "cp ......" instruction.
Jack_R1 said:
Have any file explorer installed? Astro / EStrongs / whatever?
Copy the file manually in file explorer, and skip the "cp ......" instruction.
Click to expand...
Click to collapse
I just thought of the same thing
Installing Astro now (it's a new phone no apps!)
Jack_R1 said:
Won't work for 2 reasons:
1) In Android, chmod seems not to recognize letters for permissions.
2) On SD card formatted with FAT32, the mount assigns default permissions for all files, and they can't be changed - since the file system doesn't support it.
Click to expand...
Click to collapse
ah, didn't know that
Jack_R1 said:
Have any file explorer installed? Astro / EStrongs / whatever?
Copy the file manually in file explorer, and skip the "cp ......" instruction.
Click to expand...
Click to collapse
As Jack wrote, you can only copy the file manually with some file explorer.
houmles said:
As Jack wrote, you can only copy the file manually with some file explorer.
Click to expand...
Click to collapse
It won't let me copy it... I've tried Astro and ES.
Lots of complications...
Install Busybox from the Market. Then you'll have "cp" working.
If it still won't work, try "busybox cp" instead.
If you have adb connection you can try this:
unpack zip I sent you and recovery.img to root of c:\ for example .. then:
1) adb push c:\flash_image /data/flash_image
2) adb push c:\recovery.img /data/recovery.img
3) adb shell
4) chmod 755 /data/flash_image
5) /data/flash_image recovery /data/recovery.img
Jack_R1 said:
Lots of complications...
Install Busybox from the Market. Then you'll have "cp" working.
If it still won't work, try "busybox cp" instead.
Click to expand...
Click to collapse
Lots
...but it's done! Thanks a lot for the help guys
I've gotta be up in a few hours so I don't have time to install a ROM and faff about, but hopefully it will be all good from here on in.
Cheers again!!
this guide is for those who still have Clockwork Mod Recovery still on device you can thank bogdi1988 for his work and orginal guide here :
http://forum.xda-developers.com/showpost.php?p=12185475&postcount=76
BUT THIS MAY WORK FOR OTHERS IF YOU KNOW HOW TO MOUNT SYSTEM AND DATA AND THOSE THINGS FROM ADB
but to simplify I did this :
stock images
recovery.img
http://dl.dropbox.com/u/2252176/recovery.img
boot.img
http://dl.dropbox.com/u/2252176/boot.img
Once in recovery mount everything you can system , data , cache , everyrthing besides sd card
then go into command prompt and type adb shell make sure its working if you still have root it will show # if not it will show $ I believe no biggie as long as it picks up in shell.
then type : flash_image /dev/block/mmcblk3p2 /sdcard/boot_orig.img
then type : flash_image /dev/block/mmcblk3p1 /sdcard/recovery_orig.img
select reboot from the recovery. now it will reboot and it will format misc and it will reboot again.
bogdi1988 suggest flash all images over again in fastboot
in this order
system.img
recovery.img
boot.img
thanks go to everyone who has a dell streak 7 that was willing to try all these hacks and risking your devices for the greater good of the streak
P.S. I will post system.img in a second
Also for fastboot help thank bogdi1988 again heres his post that helped me
http://forum.xda-developers.com/showpost.php?p=11929063&postcount=23
I have read and tried everything
I attempted the adb method but can't get into fastboot... I believe I got the adb commands correct and I don't get an error but my the restore is not taking... at the reboot it goes right back into CWM 3.0.2.0 here's my adb shell read out...
C:\android\platform-tools>adb shell
~ #
C:\android\platform-tools>adb shell
~ # flash_image /dev/block/mmcblk3p2/sdcard/boot_orig.img
flash_image /dev/block/mmcblk3p2/sdcard/boot_orig.img
usage: flash_image partition file.img
~ # flash_image /dev/block/mmcblk3p1/sdcard/recovery_orig.img
flash_image /dev/block/mmcblk3p1/sdcard/recovery_orig.img
usage: flash_image partition file.img
~ #
I don't know what else to do, I can't find a thread that stays on track long enough to follow this issue all the way thru... please help... I have read and tried everything, i can't find a clear set of alternatives... am i missing a step?
ya, i'm stuck in the same situation. I either get a "error -1" or it says "usage: flash_image partition file.img"
does getting "usage: flash_image partition file.img" mean the file was successfully flashed?
dfspot said:
I attempted the adb method but can't get into fastboot... I believe I got the adb commands correct and I don't get an error but my the restore is not taking... at the reboot it goes right back into CWM 3.0.2.0 here's my adb shell read out...
C:\android\platform-tools>adb shell
~ #
C:\android\platform-tools>adb shell
~ # flash_image /dev/block/mmcblk3p2/sdcard/boot_orig.img
flash_image /dev/block/mmcblk3p2/sdcard/boot_orig.img
usage: flash_image partition file.img
~ # flash_image /dev/block/mmcblk3p1/sdcard/recovery_orig.img
flash_image /dev/block/mmcblk3p1/sdcard/recovery_orig.img
usage: flash_image partition file.img
~ #
I don't know what else to do, I can't find a thread that stays on track long enough to follow this issue all the way thru... please help... I have read and tried everything, i can't find a clear set of alternatives... am i missing a step?
Click to expand...
Click to collapse
You are missing the space between mmcblk3pX and /sdcard.
ok, thats what i thought. when i do it the other way i get the "failed with Error: -1" any ideas on that. also if i send it back to t-mobile under the warranty, they won't send it back as damaged since i had CMW installed o it will they?
thatruth132 said:
this guide is for those who still have Clockwork Mod Recovery still on device you can thank bogdi1988 for his work and orginal guide here :
http://forum.xda-developers.com/showpost.php?p=12185475&postcount=76
BUT THIS MAY WORK FOR OTHERS IF YOU KNOW HOW TO MOUNT SYSTEM AND DATA AND THOSE THINGS FROM ADB
but to simplify I did this :
stock images
recovery.img
http://dl.dropbox.com/u/2252176/recovery.img
boot.img
http://dl.dropbox.com/u/2252176/boot.img
Once in recovery mount everything you can system , data , cache , everyrthing besides sd card
then go into command prompt and type adb shell make sure its working if you still have root it will show # if not it will show $ I believe no biggie as long as it picks up in shell.
then type : flash_image /dev/block/mmcblk3p2 /sdcard/boot_orig.img
then type : flash_image /dev/block/mmcblk3p1 /sdcard/recovery_orig.img
select reboot from the recovery. now it will reboot and it will format misc and it will reboot again.
bogdi1988 suggest flash all images over again in fastboot
in this order
system.img
recovery.img
boot.img
thanks go to everyone who has a dell streak 7 that was willing to try all these hacks and risking your devices for the greater good of the streak
P.S. I will post system.img in a second
Also for fastboot help thank bogdi1988 again heres his post that helped me
http://forum.xda-developers.com/showpost.php?p=11929063&postcount=23
Click to expand...
Click to collapse
great how to
white99 said:
ok, thats what i thought. when i do it the other way i get the "failed with Error: -1" any ideas on that. also if i send it back to t-mobile under the warranty, they won't send it back as damaged since i had CMW installed o it will they?
Click to expand...
Click to collapse
humz mine wont flash at all
Guys,
If someone can help people struck here like me, it would be great.. i get the same -1 error message... when i run the second command. the first one passes through and i get a # for flash_image /dev/block/mmcblk3p2 /sdcard/boot_orig.img.
When we downloaded the file boot.img, how would boot_orig.img work? am i missing something?
The second command throws me an error..
Guys really waiting for help... bricked my streak in hours after i brought it..
where are you at in la
I need a little bit of help for an ex-ipohone user
Hey guys sorry to ask u a noob question, but can anyone give me an ideea how to remove/unistall CWM Recovery so i can send back my Streak 7 for repair? I have installed CWM thru fastboot an i am currently on stock 2.2.2 rom. Or if there is a thread that i didnt find please a little help would be much apreciated.
i have figured it out eventualy after 20 hrs of brain scratching ived used NVflash and worked fast and easy
thatruth132 said:
this guide is for those who still have Clockwork Mod Recovery still on device you can thank bogdi1988 for his work and orginal guide here :
http://forum.xda-developers.com/showpost.php?p=12185475&postcount=76
BUT THIS MAY WORK FOR OTHERS IF YOU KNOW HOW TO MOUNT SYSTEM AND DATA AND THOSE THINGS FROM ADB
but to simplify I did this :
stock images
recovery.img
http://dl.dropbox.com/u/2252176/recovery.img
boot.img
http://dl.dropbox.com/u/2252176/boot.img
Once in recovery mount everything you can system , data , cache , everyrthing besides sd card
then go into command prompt and type adb shell make sure its working if you still have root it will show # if not it will show $ I believe no biggie as long as it picks up in shell.
then type : flash_image /dev/block/mmcblk3p2 /sdcard/boot_orig.img
then type : flash_image /dev/block/mmcblk3p1 /sdcard/recovery_orig.img
select reboot from the recovery. now it will reboot and it will format misc and it will reboot again.
bogdi1988 suggest flash all images over again in fastboot
in this order
system.img
recovery.img
boot.img
thanks go to everyone who has a dell streak 7 that was willing to try all these hacks and risking your devices for the greater good of the streak
P.S. I will post system.img in a second
Also for fastboot help thank bogdi1988 again heres his post that helped me
http://forum.xda-developers.com/showpost.php?p=11929063&postcount=23
Click to expand...
Click to collapse
OMFG I would so kiss you right now. I was stuck where I could only load up CWR and nothing else was working. You are my hero. *sigh*
No biggie just hit that thanks.button
Sent from my Dell Streak 7 using XDA Premium App
The links are down, any mirrors?
Same need files links re not working
IMG Reposted?
Hi Folks,
A couple of people have posted that the boot, recovery, and system image links respond with a "404 not found" error. This is still the case.
I recall reading somewhere else that the images may still live on the SD card on the device. If this is true does someone know where in the file structure they may be?
If not, does anyone know where to obtain the images?
Currently I'm in CWM reboot hades on my Dell Streak 7. Tried the Dell OTA update for Honeycomb...didn't know that was a BAD thing until it was too late.
I've tried flashing boot and recovery images from a backup I'd made earlier, but no luck, so thatruth's excellent guide here: http://forum.xda-developers.com/show....php?t=1006829 doesn't help much...unless I can get the recovery and boot images.
So to reiterate:
I can get to CWM and clear the caches and flash a recovery.
I can communicate with the device via ADB and have flashed it with the backup images.
I can mount the internal SD card via CWM and my pc.
After flashing with the backup images, Fastboot still does not recognize that the device is connected, and the device does not apper to go through the 'format steps'.
Cheers,
L2
Found 'lightly modified' roms (thank you DJ Steve!) for a T-Mobile streak on another XDA thread. Flashed using adb, and tadaaaa, it booted! sliiiight problem. Will not boot into recovery and no wireless.
Managed to install rom manager (AKA ClockWorkMod) via ADB but CWM wan't an internet connection to install the recovery rom. grrrrr.
One of the other modifications (aside from root) by DJ Steve is the installation of 'BusyBox', This actually seems to complicate things for me because I don't really know how to issue ADB commands from the BusyBox shell. I get a lot of 'invalid command' and the like... I was able to install CWM OUTSIDE the adb shell (adb install rommanager) but once I'm in the shell (adb shell)I don't know how to issue the proper commands.
What I want to do is either remove busybox, or use ADB inside busybox to flash the CWM recovery rom, then flash my backup roms. (and hopefully return to full functionality.)
Any suggestions on how to use ADB commands inside of busy box to flash a rom?
Can anyone upload the stock rom images? I need to flash back to stock :\
Hello, as I said in the title, I have a problem with the recovery menu (Same with OR) - problem is I can boot in recovery (the screen with the triangle) but there can not go to the menu. I press Volume Up + camera and nothing happens. Remains the same screen with the triangle and phone.
Please give me a solution because my phone is moving very slowly with Android 2.2.x
Device - Motorola a853 Milestone
Bootloader - 90.78
Button on the camera work, as well as the volume.
What could be the problem?
Sorry for bad English ..
Come on guys, 26 views and no response to my question?
I searched all forums and tried all the solutions posted there, but none worked! But those were old solutions ...
No one knows who could be my problem?
Not sure what kind of problem you are facing. You can surely try this.
Looks like OR is not loading in ur case. You can download the latest OR, I'm using minimod OR, copy the update.zip file into the root of SD card, again reboot into recovery. If u find ur milestone stuck in triangle button try pressing volume up button. This time it should invoke the OR or it should ask u to update the zip file.
Still if it doesnt works i think u have to take advice from experts who can help u to use ADB comnands to troubleshoot further. Anyways best of luck.
Sent from my Milestone using xda app-developers app
like the last post, you should verify if you have OpenRecovery folder and update.zip file in your /sdcard.
You can try via adb or terminal emulation "reboot recovery"
I tried what you said nagabushan.c, but it does not work ... Always the same problem, no menu displays..
At least do u get exclamatory mark when u booted or milestone while pressing camera button ? Then give a sec gap and then press volume up button.
Any device both rooted or non rooted should display this.
Try ADB steps..
Let us know what u observe
Sent from my Milestone using xda app-developers app
nagabushan.c said:
At least do u get exclamatory mark when u booted or milestone while pressing camera button ? Then give a sec gap and then press volume up button.
Any device both rooted or non rooted should display this.
Try ADB steps..
Let us know what u observe
Sent from my Milestone using xda app-developers app
Click to expand...
Click to collapse
I see an exclamation mark only when you press power + x (bootloader 90.78).
I tried ADB steps..not working.
Have you verified OpenRecovery folder and its update.zip on sdcard? Try to re-download and unpack it fresh new.
What rom you said you currently have?
Have you installed vulnerable recovery?
Have you verified OpenRecovery folder and its update.zip on sdcard? Try to re-download and unpack it fresh new.
I tried, does not work ...
What rom you said you currently have?
Stock rom 2.2.x.
Have you installed vulnerable recovery?
Of course, just as there's no difference ... the menu does not show.
The menu should show. Any menu. Either from stock or OpenRecovery. I would try with a different sdcard because the older kernel (2.6.29) in recovery does not support some cards well. If the buttons are working and you have installed everything correctly then it should work. I'd try with different sdcard.
Alternatively, you can try to tell recovery to apply update.zip from sdcard automatically
Code:
echo "--update_package=SDCARD:update.zip" > /cache/recovery/command
but note that I am not sure if you need to be rooted for that. I assume not. You can either install Terminal emulator from PlayStore or enable usb debbuging in settings and try to connect through adb if you choose to try.
To see if adb detects your device
Code:
adb devices
if all is OK you should get some output (aphanumeric) and after that 16 characters, it should display in what mode is your device (device for a normally booted system, recovery for device in recovery...)
And then
Code:
adb shell
echo "--update_package=SDCARD:update.zip" > /cache/recovery/command
reboot
I'm no expert but it might be an unsupported sdcard...
mrvek said:
The menu should show. Any menu. Either from stock or OpenRecovery. I would try with a different sdcard because the older kernel (2.6.29) in recovery does not support some cards well. If the buttons are working and you have installed everything correctly then it should work. I'd try with different sdcard.
Alternatively, you can try to tell recovery to apply update.zip from sdcard automatically
Code:
echo "--update_package=SDCARD:update.zip" > /cache/recovery/command
but note that I am not sure if you need to be rooted for that. I assume not. You can either install Terminal emulator from PlayStore or enable usb debbuging in settings and try to connect through adb if you choose to try.
To see if adb detects your device
Code:
adb devices
if all is OK you should get some output (aphanumeric) and after that 16 characters, it should display in what mode is your device (device for a normally booted system, recovery for device in recovery...)
And then
Code:
adb shell
echo "--update_package=SDCARD:update.zip" > /cache/recovery/command
reboot
I'm no expert but it might be an unsupported sdcard...
Click to expand...
Click to collapse
Here's what I get from cmd:
C:\android-sdk\platform-tools>adb devices
List of devices attached
04037B7518003010 device
C:\android-sdk\platform-tools>adb shell
# echo "--update_package=SDCARD:update.zip" > /cache/recovery/command
echo "--update_package=SDCARD:update.zip" > /cache/recovery/command
cannot create /cache/recovery/command: directory nonexistent
#
My device is rooted wth "superoneclick" method.
es7ar said:
cannot create /cache/recovery/command: directory nonexistent
Click to expand...
Click to collapse
Create it.
Code:
adb shell
mkdir -p /cache/recovery
mrvek said:
Create it.
Code:
adb shell
mkdir -p /cache/recovery
Click to expand...
Click to collapse
C:\android-sdk\platform-tools>adb shell
$ mkdir -p /cache/recovery
mkdir -p /cache/recovery
mkdir failed for -p, Read-only file system
$
Try without -p
Code:
mkdir /cache/recovery
mrvek said:
Try without -p
Code:
mkdir /cache/recovery
Click to expand...
Click to collapse
I created the folder "recovery" inside "cache" with root explorer.
Now cmd shows me: ( check attachments )
are you missing "echo"?
Code:
echo "--update_package=SDCARD:update.zip" > /cache/recovery/command
it simply writes what is in the first argument (in quotes) to file named "command" located in /cache/recovery
Edit: you can ommit adb devices. You just test the first time when you connect to be sure if adb detects your device. After that it should generally give "device not found" or something like that if connection to device is lost.
I do not understand ...
The command "echo" - update_package = sdcard: update.zip "> / cache / recovery / command" should create a file called "command" in the folder "recovery" from the "cache"?
If so, there is no file called "command"
Sorry, I'm newbie ... I do not want to stress you out.
Edit : Hmm ...
Instead of reboot, like you said, I typed "reboot recovery" then restated the phone ... and the loading bar appears. The phone has rebooted when it came to approx. 30% ..
es7ar said:
I do not understand ...
The command "echo" - update_package = sdcard: update.zip "> / cache / recovery / command" should create a file called "command" in the folder "recovery" from the "cache"?
If so, there is no file called "command"
Sorry, I'm newbie ... I do not want to stress you out.
Click to expand...
Click to collapse
Yes, it should create that file with that content, to instruct recovery to automatically apply update.zip.
You can try to create that file manually with the
Code:
--update_package=SDCARD:update.zip
content in it.
Could you post the content of
Code:
mount
executed in adb? i was sure you can write to cache, it should be mounted read-write.
---------- Post added at 03:32 PM ---------- Previous post was at 03:30 PM ----------
es7ar said:
Edit : Hmm ...
Instead of reboot, like you said, I typed "reboot recovery" then restated the phone ... and the loading bar appears. The phone has rebooted when it came to approx. 30% ..
Click to expand...
Click to collapse
hm...
could you please execute in adb:
Code:
ls -laR /sdcard/OpenRecovery /sdcard/*.zip
post output.
Okay, it looks like it was done!
You've explained it very well ... but I did not openrecovery and update.zip in sdcard.
I thank you so much for helping me! Thanks a lot!!
es7ar said:
but I did not openrecovery and update.zip in sdcard
Click to expand...
Click to collapse
That leads us back to the very begining of the process...