Database Develop

[Q] Recovery Flashing Error

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.

can't mount sdcard under root

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

How to flash stock images.

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 :\

How to restore your DS7

This may void your warranty, cost you your soul, and cause your spouse to leave you - ALL OF WHICH I AM NOT RESPONSIBLE FOR!
So, if it's because you screwed up flashing something, bricked your tablet with an OTA update after you installed CWM, or whatever, this is how you get it back to its outta-da-box shape!
(Please note, this assumes you have both installed CWM on your DS7 AND have installed the latest SDK on your computer).
1. Download the three attached .img files
2. Boot into CWM (since there really isn't anything else you can do)
3. In CWM, mount your SD card (so that you can view files via USB)
4. Plug in your DS7 to your computer, and copy the three .img files to the root of your SD card
5. Unmount your SD card, but leave the USB cable plugged into computer
6. Mount as many things as you can (ie system, boot, etc)
7. Open up command prompt, and navigate to your Android/tools folder, and type "adb devices"
8. There should be a number that shows up, or a "?" - either at this point is fine
9. Type the following command:
Code:
adb shell
a hash tag should show up that looks like this:
Code:
#~
10. Now, type the follow two commands one at a time:
Code:
flash_image /dev/block/mmcblk3p2 /sdcard/boot_orig.img
flash_image /dev/block/mmcblk3p1 /sdcard/recovery_orig.img
11. now, select "reboot" from DWM to reboot your device. It should boot and say something like "Formating Misc", and then it will reboot repeatedly
12. Use something small to push the RESET button on the DS7 (it's next to the SD card slot)
Your screen should go blank
13. Now, press and hold both the POWER button and the VOLUME - button until the screen comes on saying that the "fastboot downloader" is booted
14. Copy the three .img files into the your Android/tools folder
15. Now type the following code:
Code:
fastboot devices
16. There should be a number that shows up, or a "?" - either at this point is fine once again
17. Now type the following commands one at a time. The first will take a while to complete - this is okay:
Code:
fastboot flash system system_orig.img
fastboot flash recovery recovery_orig.img
fastboot flash boot boot_orig.img
Now, if after every command a "finished." is given, along with the total time each command took, you may continue.
18. You may now type the triumphant command:
Code:
fastboot reboot
Which will reboot your device.
Give it a little bit to boot, but when all is done you should see the original T-Mobile boot animation and everything.
Special thanks to DJ_Steve, bogdi1988, and [email protected] for all your help!
Needed files:
system_orig.img
recovery_orig.img
boot_orig.img
[Edit]
For those users who need the original "flash_image.zip" file, I have uploaded it and it is available here.
PS: As an added note: **** you Koush! From all of the DS7 community!

Just what was needed
sent from somewhere

thanks but if you would of search there was a thread made already but i am sure the more the marrier

mooch777 said:
This may void your warranty, cost you your soul, and cause your spouse to leave you - ALL OF WHICH I AM NOT RESPONSIBLE FOR!
So, if it's because you screwed up flashing something, bricked your tablet with an OTA update after you installed CWM, or whatever, this is how you get it back to its outta-da-box shape!
(Please note, this assumes you have both installed CWM on your DS7 AND have installed the latest SDK on your computer).
1. Download the three attached .img files
2. Boot into CWM (since there really isn't anything else you can do)
3. In CWM, mount your SD card (so that you can view files via USB)
4. Plug in your DS7 to your computer, and copy the three .img files to the root of your SD card
5. Unmount your SD card, but leave the USB cable plugged into computer
6. Mount as many things as you can (ie system, boot, etc)
7. Open up command prompt, and navigate to your Android/tools folder, and type "adb devices"
8. There should be a number that shows up, or a "?" - either at this point is fine
9. Type the following command:
Code:
adb shell
a hash tag should show up that looks like this:
Code:
#~
10. Now, type the follow two commands one at a time:
Code:
flash_image /dev/block/mmcblk3p2 /sdcard/boot_orig.img
flash_image /dev/block/mmcblk3p1 /sdcard/recovery_orig.img
11. now, select "reboot" from DWM to reboot your device. It should boot and say something like "Formating Misc", and then it will reboot repeatedly
12. Use something small to push the RESET button on the DS7 (it's next to the SD card slot)
Your screen should go blank
13. Now, press and hold both the POWER button and the VOLUME - button until the screen comes on saying that the "fastboot downloader" is booted
14. Copy the three .img files into the your Android/tools folder
15. Now type the following code:
Code:
fastboot devices
16. There should be a number that shows up, or a "?" - either at this point is fine once again
17. Now type the following commands one at a time. The first will take a while to complete - this is okay:
Code:
fastboot flash system system_orig.img
fastboot flash recovery recovery_orig.img
fastboot flash boot boot_orig.img
Now, if after every command a "finished." is given, along with the total time each command took, you may continue.
18. You may now type the triumphant command:
Code:
fastboot reboot
Which will reboot your device.
Give it a little bit to boot, but when all is done you should see the original T-Mobile boot animation and everything.
Special thanks to DJ_Steve, bogdi1988, and [email protected] for all your help!
Needed files:
system_orig.img
recovery_orig.img
boot_orig.img
PS: As an added note: **** you Koush! From all of the DS7 community!
Click to expand...
Click to collapse
Thanked using the Thanks button and Thanks for your post!
Just to remind me a little as I may miss something,
why we **** Koush? It is not his fault that we stuck at CWM, or is it????

jiwengang said:
Thanked using the Thanks button and Thanks for your post!
Just to remind me a little as I may miss something,
why we **** Koush? It is not his fault that we stuck at CWM, or is it????
Click to expand...
Click to collapse
No its not his fault.. people shouldn't have tried to install the ota update while having cwr installed.. instead should have waited for a zip of the update that hell posted on behalf of did steve. As I have said if you have cwr you really can't get ota updates and install them the normal way. If the update was an update.zip you could flash through cwr but dell uses pgk files not zip.. so the only way to update is to wait for a dev to release a flashable cwr zip fike
Sent from my HTC Glacier using XDA App

The reason I made this post was so that we could have one concise, iD10t proof solution for people who were dumb like me. There's other posts, but you have to go back and forth to get the solution.
And the "Koush-****ing" was because of his unannounced abandonment of his projects, and those he was working with.
And thank you for the kind thanks!
Sent from my Dell Streak 7 using XDA App

mooch777 said:
The reason I made this post was so that we could have one concise, iD10t proof solution for people who were dumb like me. There's other posts, but you have to go back and forth to get the solution.
And the "Koush-****ing" was because of his unannounced abandonment of his projects, and those he was working with.
And thank you for the kind thanks!
Sent from my Dell Streak 7 using XDA App
Click to expand...
Click to collapse
Did he retire completely?

graffixnyc said:
Did he retire completely?
Click to expand...
Click to collapse
Think so!
From my CM7 UrBan Glacier

Hi,
I am the situation described above as I tried the OTA and am now stuck in CWR.
I followed the directions putting the 3 files on the root of my DS7 and am stuck at the following:
~ # flash_image /dev/block/mmcblk3p2 /sdcard/boot_orig.img
flash_image /dev/block/mmcblk3p2 /sdcard/boot_orig.img
failed with error: -1
~ #
Any ideas.....?
Thanks
SkI

Error 1
Error 1 means that the file is not where it is supposed to be. In this case on the SD card. Check and make sure that you have the right file, with the right file name on the root of your SD card and try again!
Good Luck

What does
"Error scanning partitions" means?...

jiwengang said:
What does
"Error scanning partitions" means?...
Click to expand...
Click to collapse
nvm, it is solved. don't use your own flash_image. use the stock one.

dj_ski69 said:
Hi,
I am the situation described above as I tried the OTA and am now stuck in CWR.
I followed the directions putting the 3 files on the root of my DS7 and am stuck at the following:
~ # flash_image /dev/block/mmcblk3p2 /sdcard/boot_orig.img
flash_image /dev/block/mmcblk3p2 /sdcard/boot_orig.img
failed with error: -1
~ #
Click to expand...
Click to collapse
+1 same here...
I find that at step 3... I mount sdcard... it shows on PC... I copy the 3 files to drive... unmount sdcard... mount everything else... run the other commands then get error... when I repeat the process I notice the files I copied are not there... ?
so I tried to adb push the files... they say they went thru correctly... but still get the same result as above...
any ideas?

dfspot said:
+1 same here...
I find that at step 3... I mount sdcard... it shows on PC... I copy the 3 files to drive... unmount sdcard... mount everything else... run the other commands then get error... when I repeat the process I notice the files I copied are not there... ?
so I tried to adb push the files... they say they went thru correctly... but still get the same result as above...
any ideas?
Click to expand...
Click to collapse
when you adp push to sdcard, make sure you mounted it already.
after that , it always help to adb shell ls /sdcard to make sure all files are there.
then you go to adb shell,
use the stock flash_image to flash. remember point to the path to flash_image
eg. flash_image /dev/block/mmcblk3p2 /sdcard/boot_orig.img

my understanding, if you don't mount sdcard, you canot see your sdcard FROM the tablet's perspective.
I mean, for table's flash_image to work, it has to be able to access its drive, in this case, is sdcard 's content.
so did you try leave sdcard mount and do the command above?

Hey Team...
can someone help me find the stock flash_image plz.....

I soooooooooooooo happy I was able to fix my Streak 7......yahooooooooo
I was missing the correct flash_image file which i took from the Galaxy Tab flash_image which is the same for the Dell and follow the direction and I now up again.......
Thanks guys

chris73 said:
I soooooooooooooo happy I was able to fix my Streak 7......yahooooooooo
I was missing the correct flash_image file which i took from the Galaxy Tab flash_image which is the same for the Dell and follow the direction and I now up again.......
Thanks guys
Click to expand...
Click to collapse
What command did you do.
Sent from my HTC Glacier using XDA App

chris73 said:
I soooooooooooooo happy I was able to fix my Streak 7......yahooooooooo
I was missing the correct flash_image file which i took from the Galaxy Tab flash_image which is the same for the Dell and follow the direction and I now up again.......
Thanks guys
Click to expand...
Click to collapse
do I need to push flash_image to my tablet?

If I remember correctly it needs to be in the nvflash folder
Sent from my Dell Streak 7 using XDA Premium App

Compiled ROW CWR image and ROW diff discussion

UPDATE(Feb 07, 2012): Updating this with most recent info and installation instructions:
ROW 16GB with /data/sdcard fix
http://everyrandom.com/files/download.php?file=381ventana_recovery_row_16.img
ROW 32GB with /data/sdcard fix
http://everyrandom.com/files/download.php?file=165ventana_recovery_row_32.img
ROW 64GB with /data/sdcard fix
http://everyrandom.com/files/download.php?file=656ventana_recovery_row_64.img
Again, use at your own risk. 32GB and 64GB versions have not been tested.
NOTE: Backup has been tested, but recovery hasn't, though I'd be surprised if it didn't. This is a USE AT YOUR OWN RISK image. Also, I noticed my tablet rebooted once or twice while attempting to backup. This was likely due to the 9% battery indicator, but I figure I'd warn you just in case. If you leave your tablet to backup and you get back to it and you see your launcher unlock screen, it rebooted and likely didn't finish so you'll have to try again(again, I'm pretty sure this was just due to me having run down my battery).
WARNING: The following assumes you haven't installed any CWR image yet. If you've already installed CWR successfully, follow the 'Update Steps'.
Installation Steps:
Code:
adb push recovery_ventana_row16.img /data/local/
adb shell
su
mount -o rw,remount /system
cp /system/etc/install-recovery.sh /system/etc/install-recovery.sh.backup
echo "#!/system/bin/sh" > /system/etc/install-recovery.sh
dd if=/data/local/recovery_ventana_row16.img of=/dev/block/mmcblk0p1
Uninstallation Steps:
Code:
adb shell
su
mount -o rw,remount /system
cat /system/etc/install-recovery.sh.backup > /system/etc/install-recovery.sh
dd if=/system/recovery-from-boot.p of=/dev/block/mmcblk0p1
Update Steps:
Code:
adb push recovery_ventana_row16.img /data/local/
adb shell
su
mount -o rw,remount /system
echo "#!/system/bin/sh" > /system/etc/install-recovery.sh
dd if=/dev/block/mmcblk0p1 of=/data/local/recovery_backup_image.img
dd if=/data/local/recovery_ventana_row16.img of=/dev/block/mmcblk0p1
If CWR randomly reboots on you when you either try to do a backup or simply stay on the menu too long, try the following(thanks stewarta):
Boot into CWR. Then select to reboot the device(not "Reboot recovery", just the normal reboot).
Allow it to boot into full Android.
Reboot the device again and re-enter CWR. It should no longer be rebooting.
I don't know why the above happens or fixes it. If it doesn't work for you, please do the following:
Boot into CWR. Either wait at the menu screen or attempt a backup(we want to provoke a reboot)
On reboot, hit Vol+ to enter CWR again.
Select 'Advanced'.
Select 'report recovery'. It will tell you at the bottom where the log is stored. Make a note of it.
Boot into full Android and use your favourite file manager to get the log. Paste its contents in this thread.
And once again thanks to Koshu, logxen and jcase and everyone else involved. They did most of the work. I mostly just hit "make".
____________________________________
So with that out of the way:
The kernel is the only change between jcase's port and the ROW version. The BuildConfig and such are untouched.
So why does it work? I would imagine a recovery image would be beyond caring about region of even the kernel version of the main OS. I can't imagine they'd have altered the hardware between builds, especially as ROW merits as much attention as bundling Canada and Berlin...
So, any ideas as to what could cause the difference? Could it be the nvflash signing keys? Could there be a driver inconsistency? Anyone have any ideas on how to troubleshoot at that level seeing as it doesn't look like Android even logs anything that early in the boot process.

Many thanks to realyst2k and every one made this work.
Just wondering can we replace the ROW rom with the US rom in CWR? The lenovo ftp already has a US image.

fhing said:
Many thanks to realyst2k and every one made this work.
Just wondering can we replace the ROW rom with the US rom in CWR? The lenovo ftp already has a US image.
Click to expand...
Click to collapse
I didn't do anything but make using the ROW kernel extracted from my tablet. Koshu and jcase deserve those thanks more than I.
As far as a US image, go to the following post. Koshu has US CWR images for all models.
http://forum.xda-developers.com/showpost.php?p=21992089&postcount=106

Once again thank you realyst2k for compiling CWR for ROW.
I have TPT ROW 16GB. I backuped with no problem. Only one question, when backuping /data folder it skips /data/media folder which is internal memory same as /mnt/sdcard. From one side it's OK because it can contain up to 10G data and it would be hard to backup it, but from other side resetting to factory defaults also deletes /mnt/sdcard and so you need backup it also. I am little confused?!?!?! What is the situation in other tablets with internal storage?

It skips that mountpoint on purpose. I believe this is how the Transformer does it too. The reasoning aside from potentially gigantic backups and recoveries, is that it can also prevent a proper backup since it could easily overpower the filesystem on some SD cards(especially if you consider the 32GB model).
It's not needed in any case. CWR is made to do a NAND backup, which are your OS files and such. You can use Titanium Backup if you need to backup your media.

@realyst2k:
(SOLVED)

stewarta said:
@realyst2k:
I couldn't get this to work:
I followed the UPDATE steps but even though the file permissions are okay (rw-rw-rw) it could not read the file at the last step. Probably something simply ....
Click to expand...
Click to collapse
Make sure the image file actually is in your /data/local directory(you can use a file manager like root explorer).
If it's named differently(remember, it's case sensitive), adjust the name in the dd command accordingly.
If it isn't there, put it there(again, you can use root explorer if you have trouble using the the adb push command).

realyst2k said:
Make sure the image file actually is in your /data/local directory(you can use a file manager like root explorer).
If it's named differently(remember, it's case sensitive), adjust the name in the dd command accordingly.
If it isn't there, put it there(again, you can use root explorer if you have trouble using the the adb push command).
Click to expand...
Click to collapse
Thanks for the speedy reply. That was the first thing I checked .... the second was that I can still do Nand backups ... and I can. I'll copy it into the directory and try that command line again.
---------- Post added at 03:31 AM ---------- Previous post was at 02:54 AM ----------
realyst2k said:
Make sure the image file actually is in your /data/local directory(you can use a file manager like root explorer).
If it's named differently(remember, it's case sensitive), adjust the name in the dd command accordingly.
If it isn't there, put it there(again, you can use root explorer if you have trouble using the the adb push command).
Click to expand...
Click to collapse
@realyst2k: Guess what it was .... the download file name is ventana_recovery_row_32.img. Compare that with the command line below ...
dd if=/data/local/recovery_ventana_row_32.img of=/dev/block/mmcblk0p1
So that was never going to work until I renamed the file. Duh! Boots into CWR, so I did my usual trick of booting into CWR, doing nothing and booting back into Android OS. Now back in CWR and doing a Nandroid backup without any issues at all. So thank you once again.
Might uninstall CWR over Easter and get OTA2. Perhaps not ... might just wait for ICS in May/June.

OTA 2 and Root with CWR
@realyst2k Being impatient, I decided to rename the install-recovery.sh and the install-recovery.sh.forrecovery and install the OTA and see what was what.
It installed fine. I've lost root, so I will have a go at using the original method of rooting the TPT. Oddly, Root Explorer works, but SuperUser (chainsdd) is not logging this fact. NSTools seems to work as well (reports the scheduler is Noop).
Anyway, long story short, I will report more tomorrow. When I have more time.
Happy Easter.

OTA2 = No Root
(SOLVED)

OTA 2.5 + Root + CWR
Yay! I am back in business with root after installing OTA 2.5. For the low down, use this new exploit. But make sure you have the right drivers and lines in the android_winusb.inf file (Do a check using adb devices in a command window while the TPT is connected and in recovery mode. If no device is reported go into Win Device Manager and check out if you have Android phone showing or Portable device with a MTP driver--the latter is WRONG and you need to get the correct driver loaded otherwise you get the errors being reported by many others):
Code:
[Google.NTamd64]
;
;NVIDIATegra
%SingleAdbInterface% = USB_Install, USB\VID_0955&PID_7000
%CompositeAdbInterface% = USB_Install, USB\VID_0955&PID_7100&MI_01
;
;NVIDIA Tegra %SingleAdbInterface% = USB_Install, USB\VID_17EF&PID_741C
%CompositeAdbInterface% = USB_Install, USB\VID_17EF&PID_741C&MI_01
;
;Lenovo Think Tablet
;%CompositeAdbInterface% = USB_Install, USB\VID_17EF&PID_741B&MI_01
;%CompositeAdbInterface% = USB_Install, USB\VID_17EF&PID_741C&MI_01
;%CompositeAdbInterface% = USB_Install, USB\VID_17EF&PID_741D&MI_02
;%CompositeAdbInterface% = USB_Install, USB\VID_17EF&PID_741E&MI_02
His script does work. Even without a factory reset. So now I have 0089_ROW with root. And yes, I am now using 'Root Keeper' from Play Store.
And before you ask, realyst2k's method of gaining CWR works. Just make sure your first boot in CWR is only to reboot back into the OS. Then on your next boot into CWR, you can do a Nandroid backup without any unintended boots and the like. This means boot into CWR from shutdown using Vol+ and Pwr, then Vol+ after the vibration (do not use such as Rom Manager). Enjoy!

Doesn't work for my TPT 64GB.
I'm ready to trace/play/debug/... to get it work

I'm still working on it but for some reason I have the MTP USB and the Android Phone listed in Device Manager, I thought it was suppose to be one or the other.
Also, if I'm reading your post right I should check in windows device manager while the tablet is in recovery, correct? That is when I see Android Phone > Lenovo ThinkPad Tablet ADB Interface and farther down Portable Devices > MTP USB Device. The MTP USB Device always tries to install whenver I plug or unplug the tablet and always fails, but the Android Phone part always does fine.
For what it's worth it didn't matter that I had both devices that ended up working.

josh451 said:
I'm still working on it but for some reason I have the MTP USB and the Android Phone listed in Device Manager, I thought it was suppose to be one or the other.
Also, if I'm reading your post right I should check in windows device manager while the tablet is in recovery, correct? That is when I see Android Phone > Lenovo ThinkPad Tablet ADB Interface and farther down Portable Devices > MTP USB Device. The MTP USB Device always tries to install whenver I plug or unplug the tablet and always fails, but the Android Phone part always does fine.
For what it's worth it didn't matter that I had both devices that ended up working.
Click to expand...
Click to collapse
Yes, I think that as long as the Android phone driver from Lenovo is there it will work. But if it is Portable Devices > MTP USB Device on its own, it will not. Well done!

I'm an idiot !
Links are not dead, for those looking for files you need to wait for a reservation ticket. Too impatient

Great work, thx!
As a TPT 32Gb user, had to rename files on cmdline then all went well.
Just one question: any way to activate emmc instead of using external SD to work with recovery?
I do know it is achieving by patching recovery.fstab, but don't know what exactly should be added..

As for differencies:
My try was to install WE system image on ROW, I succeed. After trying to install also boot image it loops at first lenovo logo.. and as kernel source is common the remainig thing is ramdisk oO

i have CWM-based Recovery v5.0.2.7
trying to load firmware:
ThinkPadTablet_A310_03_0069_0121_ROW.zip
or
ThinkPadTablet_A310_02_0039_0089_ROW.zip
- install zip from sdcard
- toggle signature verification
- choose zip from sdcard
Choose any of the
ThinkPadTablet_A310_03_0069_0121_ROW.zip
ThinkPadTablet_A310_02_0039_0089_ROW.zip
and get a 20-30%% check the exact same error:
E:failed to veryfy whole-file signature
E:signature verification failed
Installation aborted
if you try to upgrade without checking the signature, I get this error:
assert failed: getprop ("ro.producrt.devices") == "Indigo" || getprop ("ro.producrt.product") == "Indigo"
E: Error in sdcard/ThinkPadTablet_A310_.................
(Status7)
Installation aborted
anyone have any ideas what? to upgrade
recovery of stock recovery (Uninstallation Step) it does not help
TPT refuses to respond to the button VOL+ and continue to load.

the problem was resolved. need to recover after the stock bootloader
adb shell
$ su
dd if=/system/recovery-from-boot.p of=/dev/block/mmcblk0p1
Click to expand...
Click to collapse
TWICE TPT reboot, reboot, and the second is already possible to enter the recovery boot (Vol+)
---------- Post added at 05:05 PM ---------- Previous post was at 05:02 PM ----------
new problem: how to install the CWM on 0121_ROW firmware. instruction from the first post does not fit.

CWM Recovery and ICS 4.0.3
Anyone got a CWM Recovery for ICS 4.0.3. ICS sure brings the TPT alive ... but I'd like to be able to do a Nandroid backup so I can stay that way. OTARootkeeper ensured I have root access, so that is a big help.
---------- Post added at 08:16 AM ---------- Previous post was at 08:03 AM ----------
Driver'z said:
i have CWM-based Recovery v5.0.2.7
trying to load firmware:
ThinkPadTablet_A310_03_0069_0121_ROW.zip
or
ThinkPadTablet_A310_02_0039_0089_ROW.zip
- install zip from sdcard
- toggle signature verification
- choose zip from sdcard
Choose any of the
ThinkPadTablet_A310_03_0069_0121_ROW.zip
ThinkPadTablet_A310_02_0039_0089_ROW.zip
and get a 20-30%% check the exact same error:
E:failed to veryfy whole-file signature
E:signature verification failed
Installation aborted
if you try to upgrade without checking the signature, I get this error:
assert failed: getprop ("ro.producrt.devices") == "Indigo" || getprop ("ro.producrt.product") == "Indigo"
E: Error in sdcard/ThinkPadTablet_A310_.................
(Status7)
Installation aborted
anyone have any ideas what? to upgrade
recovery of stock recovery (Uninstallation Step) it does not help
TPT refuses to respond to the button VOL+ and continue to load.
Click to expand...
Click to collapse
Slip across here as there may be quite a few reasons for this.