Database Info

HowTo re-flash the recovery image after old 2.1 RUU

This guide was taken from AndroidCentral and I thought I would share it here because it's taken me 4 hours this morning to figure out why I was having so many problems trying to flash a recovery image when I know my phone was rooted and flashed in order to get 2.1 a month or so ago. I have been searching these forums and google and hope anyone else who has my issue finds this post.
1. Make sure you have the Android SDK installed.
2. Download flash_image.zip
3. Download recovery-RA-heroc-v1.5.2.img
4. Unzip the first file, and place both in your Android SDK/tools folder.
5. Make sure USB debugging is ON
6. Connect your phone to the PC
7. Open the command window and navigate to the Android-sdk/tools folder on your computer.
8. At the prompt enter the following, one line at a time followed by enter
Code:
adb shell
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
exit
exit
adb push flash_image /system/bin
adb push recovery-RA-heroc-v1.5.2.img /sdcard
adb shell
chmod 0755 /system/bin/flash_image
reboot
9. Your phone will reboot. When it is finished, back at your command window, once again enter
Code:
adb shell
su
cd /sdcard
flash_image recovery recovery-RA-heroc-v1.5.2.img
reboot recovery
10. With any luck, you'll have the recovery image back and can load custom 2.1 based ROMS again.
Hope this helps. All credit goes to gbhil at Android Central.

You might want to change the title of the post. People might get confused thinking you found a way to downgrade the hboot and not how to flash the recovery image.

Can't get it to work.
I ran the RUU earlier.
Tried to root the old way.......didn't work.
Just tried this to get the recovery image back.
At the SU command it says: permission denied
Thanks,
Bubba.

bubbacs1 said:
Can't get it to work.
I ran the RUU earlier.
Tried to root the old way.......didn't work.
Just tried this to get the recovery image back.
At the SU command it says: permission denied
Thanks,
Bubba.
Click to expand...
Click to collapse
This won't work for the leak that was put out today. You lost root. This process requires root.

bubbacs1 said:
Can't get it to work.
I ran the RUU earlier.
Tried to root the old way.......didn't work.
Just tried this to get the recovery image back.
At the SU command it says: permission denied
Thanks,
Bubba.
Click to expand...
Click to collapse
If you used the new RUU that was leaked today you're screwed. The older 2.1 leaks were test ROMs that were already rooted so you could use the instructions above to flash the RECOVERY. Notice recovery in bold, not bootloader. Once hboot is updated there is no known way to downgrade so you could use an older RUU file.

This rom has no root. There is NO WAY to re-root after flashing the newest RUU. I'm sorry to say... you're ****ed.

HeroMeng said:
This rom has no root. There is NO WAY to re-root after flashing the newest RUU. I'm sorry to say... you're ****ed.
Click to expand...
Click to collapse
So they can't run an older ruu with 1.5?

HeroMeng said:
This rom has no root. There is NO WAY to re-root after flashing the newest RUU. I'm sorry to say... you're ****ed.
Click to expand...
Click to collapse
To clear that up, if you run the RUU you have no root. If you extract the ROM, set it up, and flash it, you will preserve root, just like damageless made for all of us. But, yeah, you are not gonna be able to get back from this one. at least until someone figures it out.

I changed the thread title to hopefully alleviate some confusion. I didn't realize there was a newer RUU released.
I flashed the Damageless Rom and it's running smoothly so far, but I'm still trying to figure out why wifi tethering isn't working out for me. :-(

celemew2 said:
I changed the thread title to hopefully alleviate some confusion. I didn't realize there was a newer RUU released.
I flashed the Damageless Rom and it's running smoothly so far, but I'm still trying to figure out why wifi tethering isn't working out for me. :-(
Click to expand...
Click to collapse
Did you get wifi tether version 1_60? That's the only version that ever worked for me.

Yeah, I have 1.60 installed on my phone right now, but when I try to start tethering, a SU Request black screen comes up and nothing happens until I get an error, "Activity SU Request (in application Superuser Permissions) is not responding."
I'm sure there's an answer somewhere, but lately I haven't been having luck searching for it.
Edit:
Thank you 98classic! All I had to do was enable USB Debugging. (I had it turned off cause I didn't like the warning up top when my phone was plugged into the computer)

"flash_image not found" what the f**k

need the binary? physically check its there with a root explorer
Sent from my broken Typewriter!!!

or do this download and set up the android SDK it itself includes the flash_image binary. after that u will need to open a command prompt on your computer u will have to change directory to platform tools
cd /path/to/platform-tools
after that u will get the chance to do
flash_image recovery /path/to/recovery.img
that will flash the recovery
now reboot into recovery
Typed from my broken Typewriter!!!

[Q] help getting update.zip to my sdcard

Did something to my captivate, when it starts and gets to the desktop, it stops force closing the launch and android accore something. I have no way of getting to anything, settings or otherwise.
I'm able to get it into recovery mode, but if i run reinstall packages it says it can't open /sdcard/update.zip.
I can connect to adb and see the device, but i can't seem to push the update.zip to it. I also have a $ i thought it should be a #.
Any ideas on how to proceed, no way to get into anything on the phone, and adb is acting odd. It shows:
List of devices attached
I89789fda6da recovery

If an aftermarket launcher is your problem, use adb uninstall to get rid of it or any other apk that is causing problems.

its the actual launcher thats erroring out - I can't even figure out how to get adb to let me browse the files on the phone. I have the update file that will resolve the issue, but no way to get it to the internal sdcard

JacenSolo2001 said:
its the actual launcher thats erroring out - I can't even figure out how to get adb to let me browse the files on the phone. I have the update file that will resolve the issue, but no way to get it to the internal sdcard
Click to expand...
Click to collapse
in order to push files I think you need root. if you've rooted your phone, use the su command to get the # prompt, which is super user status.

ok, here's where I'm at:
Android system recovery screen, with the 4 options, reboot, reinstall packages (which can't find the zip file), and the 2 deletes. This is the only place i can use adb at from here:
I do an adb devices and get
List of devices attached
I89789fda6da recovery
So at this point, is there a way anyone knows of to get the zip file to the internal sdcard?
oh and btw: the phone is rooted

Do you have busybox on the phone? If you do, do this:
Code:
adb shell
cd /sdcard/
busybox wget <url to update.zip>

i don't think busybox is on there any longer, it just says busybox: not found

dewt said:
Do you have busybox on the phone? If you do, do this:
Code:
adb shell
cd /sdcard/
busybox wget <url to update.zip>
Click to expand...
Click to collapse
I don't get it: what wget will get? Are you saying I need a web-server on my windows laptop?
Please be more specific: update.zip sits on my D:\tmp. How wget will see it?
Example please

JacenSolo2001 said:
Did something to my captivate, when it starts and gets to the desktop, it stops force closing the launch and android accore something. I have no way of getting to anything, settings or otherwise.
I'm able to get it into recovery mode, but if i run reinstall packages it says it can't open /sdcard/update.zip.
I can connect to adb and see the device, but i can't seem to push the update.zip to it. I also have a $ i thought it should be a #.
Any ideas on how to proceed, no way to get into anything on the phone, and adb is acting odd. It shows:
List of devices attached
I89789fda6da recovery
Click to expand...
Click to collapse
If you can get into recovery mode, have you tried a master clear? If you can't copy files via ADB and you can't use any apps on your phone, then that is your only choice. Or an Odin one click restore to stock.

alphadog00 said:
If you can get into recovery mode, have you tried a master clear? If you can't copy files via ADB and you can't use any apps on your phone, then that is your only choice. Or an Odin one click restore to stock.
Click to expand...
Click to collapse
Exactly what I was thinking. It doesn't make sense to be trying so hard to fix that when a simple one click Odin will remedy the problem.
Sent from my Captivate

[Guide] How to gain root on 2.2 for Mac

*******UPDATED 8/31/10 *******
This rooting method was adapted from regaw_leinad's method and toastcfh's method. By following these steps you will successfully downgrade your phone back to android 2.1 in order to gain root.
I don't trust unrevoked as I have had problems with it in the past.

I am not responsible for any damages to your phone.
special thanks to:
regaw_leinad
Sebastian Krahmer
Toastcfh
amon_ra
FILES YOU WILL NEED:
copy and paste into browser
Code:
sdx-downloads.com/sdx/evo/troot/eng-PC36IMG.zip
evo4g.me/downloads//count.php?target=evo-root.zip
files.androidspin.com/downloads.php?dir=amon_ra/RECOVERY/&file=recovery-RA-evo-v1.8.0.img
developer.android.com/sdk/index.html
You will need the Android SDK in order to communicate between your computer and your phone. Download it (last link above) and follow the setup instructions that it comes with.
Unzip the contents of the evo-root.zip and put all the files from it into the tools folder located in the android sdk folder.
Rename the eng-PC36IMG.zip to PC36IMG.zip and then put it the tools folder located in the android sdk folder. DO NOT UNZIP IT!

******* PC36IMG.zip md5sum~ fe8aba99893c766b8c4fd0a2734e4738 *******
Move the recovery-RA-evo-v1.8.0.img into the android sdk folder as well.
Make sure usb debugging is enabled on your device. To do so go to Settings > Applications > Development > and make sure the check box is checked.
Plug your phone into the computer. Select "Charge Only" from the notifications bar.
Open up terminal and navigate your way into the android sdk folder.
Code:
cd /
cd asdk
Push all the files onto your phone.
Code:
tools/adb push /asdk/tools/flash_image /sdcard/
tools/adb push /asdk/tools/rageagainstthecage-arm5.bin /data/local/tmp/
tools/adb push /asdk/tools/mtd-eng.img /sdcard/
tools/adb push /asdk/tools/PC36IMG.zip /sdcard/
tools/adb push /asdk/tools/recovery-RA-evo-v1.8.0.img /sdcard/
Note that the PC36IMG.zip will take longer than the other files to transfer to the sdcard because it is a large file.

Now we will make rageagainstthecage.bin executable.
Code:
tools/adb shell
chmod 0755 /data/local/tmp/rageagainstthecage-arm5.bin
You should see this (below) after it has made the change.
Code:
$
Now to use the rooted shell.
Code:
cd /data/local/tmp
./rageagainstthecage-arm5.bin
You will now see some text on your terminal screen describing the exploit. 

Wait for the adb shell to finish the process. At this point it may or may not terminate the current shell session in terminal. If it does then it should look like this:
Code:
users-iMac:asdk user$
If it doesn't it will return to
Code:
$
in that case you need to exit the current session. To do so type
Code:
exit

Now we need initiate a new shell which should now have root permissions.
Enter the following:
Code:
tools/adb shell
and you will see you now have a
Code:
#
instead of
Code:
$
Now we need to flash the mdt-eng.img in order for it to let us install a custom recovery
Code:
adb shell
cat /sdcard/flash_image > /data/flash_image
chmod 755 /data/flash_image
/data/flash_image misc /sdcard/mtd-eng.img
That will flash your misc partition with Toast's mtd-eng.img


This should return you to
Code:
#
Now boot into hBoot
Code:
reboot bootloader
This will reboot your phone into hBoot. It will scan for the PC36IMG.img. When it asks yes or no, select yes.
It should then reflash your phone into the engineering build.
When it asks to reboot select yes.
You will need to flash custom recovery in order to be able to flash other custom roms or modifications. I use Amon_RA's recovery because it works great and has NEVER caused me any problems.
Now, open up terminal and get back into the android sdk folder
Code:
cd /
cd asdk
Since we have already pushed the recovery onto the sdcard we only need to flash the recovery onto the phone so that we can use it
Code:
adb shell
cat /sdcard/flash_image > /data/flash_image
chmod 755 /data/flash_image
/data/flash_image recovery /sdcard/recovery-RA-evo-v1.8.0.img
Now lets rename that PC36IMG.zip file again
Code:
mv /sdcard/PC36IMG.zip /sdcard/eng-PC36IMG.zip
that way your phone doesn't try to flash it when you go into recovery each time
And last but not least we need to boot into it to flash a custom rom
Code:
reboot recovery
Your phone should then reboot into Amon_RA's recovery and you may now head over to the dev forum to find your new favorite custom rom.

very nice! can anyone confirm this? my buddy wants me to root his 2.2 and i would like to try this.

To make life easier for some people add this to your post mate, and apply it yourself if you would like.
Here is how to add your sdk/tools directory to your .bash_profile file so you won't have to navigate to the folder each time.
Download this so you'll be able to see your hidden files http://www.mediafire.com/?diimft1ninn Run it, check "Show Hidden Files" then click Restart finder. Now, navigate to your home folder (/Users/UserName/) and see if there's a .bash_profile already there. If not, create with textedit.
Now add this to the file: export PATH=${PATH}:/Path/Of/Your/Sdk/Tools/Folder
Mine is /Users/bmxrider4444/Documents/Android/SDK/tools
Now do not save it as rich text. If yours is in rich text, click on "Format" in the menu bar, and click "make plain text". Now save it as .bash_profile and uncheck "if no extension is provided, use .txt".
Now you can go back to Ghost and uncheck "Show all hidden files" and restart finder again (special thanks to ajones7279 for these steps)
Enjoy!
Just as clarification as to what this does, it enables you to run adb commands and other commands without having to navigate to the /android/tools/ folder every time you want to run adb or whatever.

does this work?

seekis said:
At this point we need to push the recovery onto the sdcard
Code:
tools/adb push "location of recovery-RA-evo-v1.8.0.img" /sdcard/
Click to expand...
Click to collapse
This is great! Thanks for the guide - I am planning on rooting my Wife's EVO but have been waiting for an easier method than the other one posted. Question on the above where we write "location of recovery-ra-evo-v1.8.0.img". Is that the exact code, or should we be adding a directory or folder location into this line? I rooted my 2.1 EVO on my Mac a couple months ago and don't remember this step. Once again - very much appreciate the help.
One last question - would it make more sense to have a custom ROM already on your SD Card prior to rooting, so that you can flash it right after you flash AMON-RA for the first time? Probably doesn't matter but thought i'd ask.

^^ same question as above, plus one other n00b question - does this method unlock NAND?
[edit] I was not insinuating that randymac88 is a n00b; I, however, am

seekis said:
I don't trust unrevoked as I have had problems with it in the past.

I am not responsible for any damages to your phone.
Click to expand...
Click to collapse
Don't trust us with the unrevoked 3.x/unrevoked forever application combo that's worked for thousands of users without sideeffects on regaw's post?
You should note to everyone that your method will screw up their PRI, reverting it back to 1.34. By using unrevoked and unrevoked forever, you can keep 1.40.

randymac88 said:
This is great! Thanks for the guide - I am planning on rooting my Wife's EVO but have been waiting for an easier method than the other one posted. Question on the above where we write "location of recovery-ra-evo-v1.8.0.img". Is that the exact code, or should we be adding a directory or folder location into this line? I rooted my 2.1 EVO on my Mac a couple months ago and don't remember this step. Once again - very much appreciate the help.
One last question - would it make more sense to have a custom ROM already on your SD Card prior to rooting, so that you can flash it right after you flash AMON-RA for the first time? Probably doesn't matter but thought i'd ask.
Click to expand...
Click to collapse
Thats not the exact code no. I just put that as a place holder you are suppose to put in the location of where you have the recovery.img. For example, the exact command for me would be:
Code:
/Users/seekis/Downloads/recovery-ra-evo-v1.8.0.img
Don't trust us with the unrevoked 3.x/unrevoked forever application combo that's worked for thousands of users without sideeffects on regaw's post?
You should note to everyone that your method will screw up their PRI, reverting it back to 1.34. By using unrevoked and unrevoked forever, you can keep 1.40.
Click to expand...
Click to collapse
As far as using unrevoked, I stated that I, ME, MYSELF, has had issues with it. not that anybody else has. By all means go and use it if you would like. I will not. It is true that you will loose PRI 1.40, but seeing as how even after installing the OTA from HTC my phone still didn't update it to 1.40, I don't see the issue.

rsage said:
^^ same question as above, plus one other n00b question - does this method unlock NAND?
[edit] I was not insinuating that randymac88 is a n00b; I, however, am
Click to expand...
Click to collapse
i believe it does unlock nand seeing as how i adapted it from toasts method

Hey Seekis - question, I'm stuck here. I keep getting "permission denied", or "operation not permitted" when trying to make the exploit executable at this step:
chmod 0755 /data/local/tmp/rageagainstthecage-arm5.bin
Am I missing something? I've tried a million times and can't seem to get past this. I've successfully pushed all the files onto the sdcard.
I've also have had some trouble finding the exact root path to these files. I've been able to navigate, but I would think a lot of users would have some trouble.
Regardless, many thanks for getting this posted...
EDIT: I pushed the rageagainstthecage file to the sdcard by mistake. Will try again tomorrow.

ok i got rid of that step by moving the file into the android sdk and pushing it with all the other files

Okay now I appear to be in big trouble as I've just messed up my wife's phone, and its probably going to be unusable for a while until I get this figured out (assuming I do!).
I got through most of the process. I flashed the PC36IMG.zip file; however when it asked to reboot, it just dumped me back into the bootloader. Whenever I say reboot, it just takes me back to the bootloader. Pull the battery, same thing - bootloader. Yikes.
I don't know how to get to the next step because I can't get into a booted rom in order to flash the amon-ra recovery. Am I totally effed? Can anyone help me here?
EDIT: Okay reflashed the PC36IMG.zip file, and it rebooted into the stock ROM. Onward! Phew!!

The wife's EVO is now fully rooted running Baked Snack 1.5 w/Netarchy's kernel. Touch and go there for a minute, but it all worked out. No 1.40 PRI, but I don't really care about that right now.
Woot! Thanks Seekis!!

do u have to push the pc36img with adb every time or will drag and drop work or copy and paste work?

FoxHound630 said:
do u have to push the pc36img with adb every time or will drag and drop work or copy and paste work?
Click to expand...
Click to collapse
You can mount the card on your system and copy paste it over as well, yes.

randymac88 said:
Okay now I appear to be in big trouble as I've just messed up my wife's phone, and its probably going to be unusable for a while until I get this figured out (assuming I do!).
I got through most of the process. I flashed the PC36IMG.zip file; however when it asked to reboot, it just dumped me back into the bootloader. Whenever I say reboot, it just takes me back to the bootloader. Pull the battery, same thing - bootloader. Yikes.
I don't know how to get to the next step because I can't get into a booted rom in order to flash the amon-ra recovery. Am I totally effed? Can anyone help me here?
EDIT: Okay reflashed the PC36IMG.zip file, and it rebooted into the stock ROM. Onward! Phew!!
Click to expand...
Click to collapse
Had the same issue. When i first booked into the bootloader i had to select recovery then flash PC36IMG.zip. Then boot loop. Then i went back into the bootloader and it automagically read in the PC36IMG.zip and flashed it, then i got stock 2.1 root. Just a few minutes of "oh crap"

I'm stuck. I got as far as flashing PC36IMG.zip, which was successful, as my phone now runs 2.1, but it doesn't appear I'm rooted. When I go back into the adb shell, I'm getting the $ prompt, and running
Code:
cat /sdcard/flash_image > /data/flash_image
gives me a permission denied error. Help!

atom_jack said:
I'm stuck. I got as far as flashing PC36IMG.zip, which was successful, as my phone now runs 2.1, but it doesn't appear I'm rooted. When I go back into the adb shell, I'm getting the $ prompt, and running
Code:
cat /sdcard/flash_image > /data/flash_image
gives me a permission denied error. Help!
Click to expand...
Click to collapse
i dont know what to tell you other than try again. this happened to me the first time through as well. i dont know why. i just started from the top and it worked the second time through.

seekis said:
i dont know what to tell you other than try again.
Click to expand...
Click to collapse
So after you flash PC36IMG.zip you should automatically get a root (#) prompt when going into the shell? ie, I'll have rooted 2.1 yes?
seekis said:
this happened to me the first time through as well. i dont know why. i just started from the top and it worked the second time through.
Click to expand...
Click to collapse
Aha. Ok, I will keep trying til it gives me a root shell, I guess. I also tried unrevoked3 but that didn't seem to work.

Success!! So, I stupidly assumed that all PC36IMG.zip's were the same, and was using the one from the original 2.2 PC thread. Once I got the correct one, voila!
You might want to post the md5 of the one you are using, so there's no confusion for others. Also, you missed a tiny step when you first start up hboot - you have to select fastboot for it to start scanning for PC36IMG.zip.
Thanks!

Clockwork Recovery for Coby Kyros MID-7015--Updated

All credit for this goes to Razor950
Coby Kyros MID-7015
Download recovery.img from Sendspace.com - send big files the easy way
use flash_image and flash recovery to tablet. (ex flash_image recovery /sdcard/recovery.img)
Navigating:
Home is down
Menu is select
Back is back
Everything works and I'll post stock nandroid dumps on here soon.
Update some are reporting that they are unable to Flash to the recent firmware update that was posted
on the coby website do to the clockworkmod being installed.
Thanks to Kasten for coding this then thanks to adamdietrick for creating a new zip
That can be flashed with the clockworkmod installed.
Clockworkmod Coby Firmware update
Donate if you like Razor950's work!

thanks for posting
any issues that anyone gets with this recovery, please pm me.
enjoy

havic said:
Everything works and I'll post stock nandroid dumps on here soon.
Donate if you like Razor950's work!
Click to expand...
Click to collapse
Here's my backup
http://www.megaupload.com/?d=5ALHYN80

You must be rooted (I assume z4root or universal android root works)
then either using terminal (grab terminal app from market) or using adb.
Grab the recovery.img and drop it into sdcard via usb or adb push.
Open terminal and type su and then flash_image recovery /sdcard/recovery.img
or if using adb, its adb shell and then su and then flash_image recovery /sdcard/recovery.img
Note: I am not the best at writing noobie guides but hopefully it helps

Thanks for this. I do not have mine yet( lol, just ordered it) but I donated for your work!
Thanks!

Anyone have a idea on how to get back into recovery? I have it installed but have tried holding every button to get me back and nothing kinda sucks since I have been testing new mods for this and cant get to my backup because the first shot at the mod was a fail.

I was able to get clockwork installed thanks to you. Do you know of any images that are out for the 7015?

Lawful123 said:
I was able to get clockwork installed thanks to you. Do you know of any images that are out for the 7015?
Click to expand...
Click to collapse
Aside from stock(rooted) dump, there is nothing, I'll work with havic to get a rooted dump with google apps(market mostly) working correctly.
Besides that there is nothing else from my end for now. I personally don't like telechip tablets, bad experience from a gentouch :X
Also telechip company are retards and don't release kernel source, it'd help developers optimize a 2.1 rom and also be able to port kernel to a newer one for 2.2

I can see that this model gained popularity this black Friday. We are just now starting to see android tablets hit " Joe User ". I think that the telechip tabs will become popular so long as the price is on point. Thanks for all you do.

what exactly is this recovery for?
does installing this offer me additional features, or is it merely what we would restore to in case of disaster?

Deenybird said:
what exactly is this recovery for?
does installing this offer me additional features, or is it merely what we would restore to in case of disaster?
Click to expand...
Click to collapse
For now it is a good way to backup your unit so that if you screw it up you can go back. In the future people will make images for it. Hopefully someday android 2.2

Which version of flash_image tool is needed to flash this recovery or is the tool stock on the tablet?
EDIT: figured it out. stock. Looking through the dump now =)

adamdietrick said:
Here's my backup
http://www.megaupload.com/?d=5ALHYN80
Click to expand...
Click to collapse
If you try and recover from the backup that is in the link you may or may not get a error.The error is md5 mismatch. So the recovery fails to install.
What needs to be done is need to have busybox installed then shell in and run the following commands.
This has to be ran from the dir. that contains the backup files.
Which will more than likely be similar to this
/sdcard/clockworkmod/backup/2010-12-01.20.41.18
#busybox md5sum -c nandroid.md5
boot.img: OK
cache.img: OK
data.img: OK
recovery.img: OK
system.img: OK
# reboot recovery
reboot recovery
Once in clockwork then run a recovery.
If you have a Issue let me know I will try my best to get you some answers.

razor950 said:
You must be rooted (I assume z4root or universal android root works)
then either using terminal (grab terminal app from market) or using adb.
Grab the recovery.img and drop it into sdcard via usb or adb push.
Open terminal and type su and then flash_image recovery /sdcard/recovery.img
or if using adb, its adb shell and then su and then flash_image recovery /sdcard/recovery.img
Note: I am not the best at writing noobie guides but hopefully it helps
Click to expand...
Click to collapse
When I type this it it says its file not found.
I double checked and in astro I see
sdcard/recovery.img
any ideas?

beccaannabell said:
When I type this it it says its file not found.
I double checked and in astro I see
sdcard/recovery.img
any ideas?
Click to expand...
Click to collapse
where are you when you type that? does it not find the flash_image binary or the .img?

Worked for me
I got it working by doing the following.
1. Download and installed "Android Terminal Emulator" on to the device.
2. Download and installed Z4Root 1.3.0.apk from here http://forum.xda-developers.com/showthread.php?t=833953
3. Run it and pressed the "Permanent Root" button. It took a bit and it auto rebooted.
4. Place the recovery.img on the root of my sd card. (Razor950's recovery.img is from post#1 on this thread.)
5. Opened "Android Terminal Emulator".
6. Entered the following.
su
flash_image recovery /sdcard/recovery.img
7. Locked everything up for about 5 min and it went back to # prompt when it was done.
8. I powered off the device.
9. After it turned off I pressed and held the back button then pressed the power button. Kept holding it until you see clockworkMod v2.5.1.3. (If it says Android it's too late.)
I have a question myself what is sd-ext on clockwork? Also is there a way to do a selective backup? Just system with no data?
Thanks.

Thanks for your procedure, will try it when I receive my tablet.
Regarding your question about sd-ext, it's a partition of your sdcard. One will be in fat32 and the other in ext2 or ext3. Usually ext2 is used when you have app2sd or 12sd+. The purpose of this is to have more apps in install by installing them on your ext partition instead of internal memory. I use it for my HTC desire (smartphone)
Regarding your second question, I don't know anyway of doing a backup without data but pretty sure it's possible, for example, if you go in your Android do a factory reset. reboot in recovery then do your backup. Not sure if there's another way to do it

Yezir!
Kasten said:
I got it working by downing the following.
1. Download and installed "Android Terminal Emulator" on to the device.
2. Download and installed Z4Root 1.3.0.apk from here http://forum.xda-developers.com/showthread.php?t=833953
3. Ran it and pressed the "permit root" button. It look a bit and it auto rebooted.
4. Place the recovery.img on the root of my sd card.
5. Opened "Android Terminal Emulator.
6. Entered the following.
su
flash_image recovery /sdcard/recovery.img
7. Locked everything up for about 5 min and went back to # prompt when done.
8. Powered off device.
9. Press and held the back button then pressed the power button. Kept holding it until I saw clockworkMod v2.5.1.3. (If it says Android its too late)
I have a question myself what is sd-ext on clockwork? Also is there a way to do a selective backup? Just system with no data?
Thanks.
Click to expand...
Click to collapse
this is perfect!!!!! thanks for thinking of us dummies

Daali said:
where are you when you type that? does it not find the flash_image binary or the .img?
Click to expand...
Click to collapse
same thing for me
"error opening /sdcard/recovery.img:No such file or directory"
Help

noonerealy said:
same thing for me
"error opening /sdcard/recovery.img:No such file or directory"
Help
Click to expand...
Click to collapse
Can you see the recovery.img on your sd card from a file manger app like Astro? If so when your in the terminal can you cd to /sdcard? If so can you enter ls -l recovery.img? Check the size to make sure it is all there.
I have anther question myself.
At cobyusa.com/?p=prod&prod_num_id=10498&pcat_id=1013 there is a firmware update. in the update.zip in system in the build.prop file i see a line that says "ro.build.version.incremental=eng.enzo.20101125.200217". I notice that the build number on the device says "MID7015 1.6a_20101105-2". Looks like they may have changed somethings but not sure what. What would be bet best way to figure out what they changed?
I tried to run it from clockwork and i get
assert failed: getprop("ro.product.device") == "tcc8900" || getprop("ro.build.product") == "tcc8900"
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted.
To install this update would I just have to unroot my device? Not sure how to look what the current ro.build.product is now.
Thanks.

Root access on adb shell but not for apps

Hello,
i am working on chinese android tablet called "MID-U705B". The device came half rooted i guess. I am getting an # in the adb shell, even without running "su", right from the start of adb shell. Nevertheless i am not able to run any root apps. When i am trying to call a root shell command from my app i am getting: [java.io.IOException] : write failed: EPIPE (Broken pipe).
There is a su file inside my /system/xbin folder and i also created a symbolic link to it in /system/bin.
Does someone know how to get full root access on this devices? Whats missing?
Thanks for your help and advice!
Best regards,
Hans

skatehans said:
Hello,
i am working on chinese android tablet called "MID-U705B". The device came half rooted i guess. I am getting an # in the adb shell, even without running "su", right from the start of adb shell. Nevertheless i am not able to run any root apps. When i am trying to call a root shell command from my app i am getting: [java.io.IOException] : write failed: EPIPE (Broken pipe).
There is a su file inside my /system/xbin folder and i also created a symbolic link to it in /system/bin.
Does someone know how to get full root access on this devices? Whats missing?
Thanks for your help and advice!
Best regards,
Hans
Click to expand...
Click to collapse
If you can get root on ADB then just install SuperSU app and its binaries and you are good to go.
Flashing the attached ZIP will install SuperSU app and everything it requires to function.
NOTE: You probably need a custom recovery because the zip isn't signed.

Thanks for your reply!
Unfortunately i dont have a custom recovery because its a no name device an there does not exist a custom recovery for this device. Is there any way to install this without a custom recovery? What happens when i try to flash it from a (chinese) stock-recovery?

skatehans said:
Thanks for your reply!
Unfortunately i dont have a custom recovery because its a no name device an there does not exist a custom recovery for this device. Is there any way to install this without a custom recovery? What happens when i try to flash it from a (chinese) stock-recovery?
Click to expand...
Click to collapse
You should be able to flash it via fastboot.

Thats the next Problem. I cant boot into fastboot mode. When i execute "adb reboot bootloader" or "adb reboot download" the device boots up like normal, so i guess fastboot is not available on this device.
Do you know any other way?