Database Info

****ROOT EVO After July 1 OTA Update

I tried every method, read every thread in every forum in an effort to root my EVO. Nothing worked. I was driving myself mad and spending tons of time. I Eventually I came across a post which directed me to XDA Developers Thread ---==={ROOT GUIDE}===--- | 1.47.651.1 ROOT, post 579 by SharkUW . I have used this on my own phone and I don't see a reason why it wouldn't work. I modified some of the instructions to make it clearer. The instructions may not be exact, and there is some seat-of-the-pants involved, but I got it to work. Use it at your own risk.
Prerequisites (follow in order)
Android-SDK developers program. I loaded it to C:
JAVA SE Development (use correct bit – 32 or 64). loaded in C:
Microsoft .NET Framework V 4.0
Reboot your phone and do a factory reset. Erase everything
Set phone to Charge Only and USB debugging
Open the stock browser and sign-in with your PCS phone number. Leave running.
Shutdown the phone, then restart
Make sure ADB is functional on your computer. You should be able to "adb shell" (confirming adb is working, exit shell if you're in it).
Extract the Do_root.zip (link below) and place all these files into the SAME folder as adb.exe. I have not included the appropriate PC36IMG.zip. Get it here. http://forum.xda-developers.com/showthread.php?t=701835 Leave the name as "eng-PC36IMG.zip". Place that in the SAME directory as well as the .zip.
Open a command prompt on your computer. point directory to Android-SDK directory\tools and a list will come up… click on "root.bat” and click RUN.
If it hangs for more than 30 seconds with the browser ****, CTRL+C, yes to kill the bat and just run it again.
Follow the directions. Your phone is going to reboot. It is then going to do a little **** and reboot into the boot loader. Keep track of the Command screen and wait because some steps take a while and there is no way of telling if it’s working. Nothing lasted more than 5 minutes. Eventually it will be in a "bootloader" and ask if you want to reboot. Say Yes with a Volume UP.
The .bat is now done. You have root. (not sure if next part is true) You now need a custom recovery to flash a proper ROM beyond the scope of this guide.
In original instructions but I’ve found the following Recovery step and code is not necessary: Now take the last step and flash the recovery.img that will already be on the root of your sdcard. To do this, after the PC36IMG flash:
Code:
adb shell
cat /sdcard/flash_image > /data/flash_image
chmod 755 /data/flash_image
/data/flash_image recovery /sdcard/recovery.img
To check for root do ADB Shell and should get #.
If you're all advancedy you can put on a different recovery image.
IMPORTANT If you get a message here about "not writing bad block", flash it again until you get 0 errors. I don't know how common it is, but personally my recovery has issues with flashing. Do NOT let that be a bad flash.
Attached Files
do_root.zip (4.07 MB, 49 views)
________________________________________
Last edited by SharkUW; 7th July 2010 at 01:06 AM.

Going to try it tomorrow and hope it works. Thanks

Where are the attached files?

Can't find the do_root.zip file. Seems there is no attachment, please re-post. Thanks.

I tried to attach the do_root.zip file and a link to Toast 2 file. If that doesn't work, go to the referenced post #579 here: http://forum.xda-developers.com/showthread.php?t=718889&page=58.

Have you tried this SimpleRoot? I just did it, and it worked flawlessly.

Vivix729 said:
Have you tried this SimpleRoot? I just did it, and it worked flawlessly.
Click to expand...
Click to collapse
Simpleroot ftw.

mattrb said:
Simpleroot ftw.
Click to expand...
Click to collapse
QFT. I did simple root (I still setup adb and ensured it was working first) and then flashed the rooted Stock 1.47 ROM in about 40 min. I think most people that are running into issues with Simpleroot do not have adb setup properly or they did something inadvertently and need to clear out the files/cache and need to start over from scratch.

gmanvbva said:
QFT. I did simple root (I still setup adb and ensured it was working first) and then flashed the rooted Stock 1.47 ROM in about 40 min. I think most people that are running into issues with Simpleroot do not have adb setup properly or they did something inadvertently and need to clear out the files/cache and need to start over from scratch.
Click to expand...
Click to collapse
I did simple root and it worked fine too. I don't think the issue is adb being setup since he has an adb file in his download.

Update from a few days ago.
Just got a new SDHC card and simpleroot worked. The SDHC that came with my phone died. I placed a spare in there that was a 2gd regular micro and Hboot would not ready the IMG for nothing.
If simple root is not working then it's the Sh!tty card acting up.
Happy ending for me.

I just got my phone yesterday did the ota simpleroot and seems like it worked fine
but now i dont know what to do next
to get custom roms or froyo 2.2 or anything lol

Awesome post |OP|.
My desktop is Windows 7 x64 and doesn't play nicely with the standard tools.
I was forced to adapt your root.bat script to an OSX friendly BASH script.
The only requirement is that you download the android SDK from developer.android.com/sdk/index.html (apparently, I'm too new to post links).
The steps I took to get root:
Unzip the android SDK
follow |OP|'s instructions, unzipping the contens of do_root into [sdk-root]/tools/
unzip the attached bash script to the [sdk-root]/tools/
run my bash script from the [sdk-root] folder instead of root.bat - type "./root.sh" without the double-quotes
Grab a copy of Froyo while your phone is being rooted

[TUTORIAL] Updating to DI07, Obtaining Root, and Flashing Custom Recovery [FIX]

Scroll to the bottom for a fix to the newest clockwork recovery flasher...
UPDATING TO DI07
First things first, you must update to the latest firmware and kernel, but in order to do this you must un-root and return to the stock kernel in order to avoid problems.
Simply download the zip here, and run the run.bat inside, after extracting the folder to your desktop.
You must have debugging mode enabled for this to work.
Once that's finished you can update to DI07 using the stock recovery. You do this, like any other update, by renaming the zip (found here, to update.zip on throwing it onto the root of your sdcard.
Then, boot up into the stock recovery (power+camera+volume down) and press home to apply the update.zip.
The update will install and your phone will reboot into DI07.
First boot will take some time, so be patient.
Now onto the fun part, rooting your phone.
OBTAINING ROOT
Just as you obtained root before DI07, you obtain root on DI07, if you have the right tools. Download the one click root here, and once more extract the included folder to you desktop, make sure you have usb debugging enabled, and run the run.bat. Your phone will reboot, and you will have root.
FLASHING CUSTOM RECOVERY
Here is where it gets a tad bit more complicated. First off, you have to download the zip here, but this time before running the bat you have to open up command prompt and redirect it to your C:/android-sdk-windows/tools folder and then run the following code.
adb devices
adb shell
su
remount rw
exit
exit
Now the command prompt should close, and you can run the run.bat for build 31 of clockwork recovery flasher. Once more, your phone will reboot and after the script is done running and says "press any key to exit...." you can press enter and boot into recovery.
That's it, three simple steps to updating, obtaining root, and flashing clockwork recovery!
Also, don't forget to check out my ROM coming later today, as well as noobnl's Andromeda Galaxy ROM v1, just released.

great tutorial...and i can use these instructions even if i am using aridons v4 rom and heros overclocked kernel?

Well, it basically reverts you back to the stock kernal, so you will for sure lose the overclocked kernal. However, I'm not sure about the ROM. Your best bet would be either to hold off on this as the ROM you are suing isn't based on DI07, or flash to stock and then follow this guide. Your choice.

bubby323 said:
Well, it basically reverts you back to the stock kernal, so you will for sure lose the overclocked kernal. However, I'm not sure about the ROM. Your best bet would be either to hold off on this as the ROM you are suing isn't based on DI07, or flash to stock and then follow this guide. Your choice.
Click to expand...
Click to collapse
Well I just ran this and at first glance, it got me right into clockwork. I selected one of my nandroid and restored it. After the phone finished restoring and everything, I wanted to make sure that I still had clockwork but instead it was stock recovery once more.
Since I still had root, I redid the steps starting with entering the commands, then I re-ran the bat file for clockwork. I checked and clockwork is back...unknown as to how long though.

Thank you!!! the remount rw was what I needed to get the clockwork custom recovery to flash!!!
I have another question for you? Is it possible to install the custom recovery without having root? I suspect not? The reason I ask is that I would like to have a nandroid backup of the completely stock rom although I guess I could use the one noobnl has posted

well, i got back to a stock rom....applied the stock kernal...but when i went to apply the update.zip...it took me back to clockwork...not the stock recovery....so i tried to apply the update from there but it aborted...how do i get rid of clockwork so i can go into stock recovery and will that fix it?

mrkrabs said:
well, i got back to a stock rom....applied the stock kernal...but when i went to apply the update.zip...it took me back to clockwork...not the stock recovery....so i tried to apply the update from there but it aborted...how do i get rid of clockwork so i can go into stock recovery and will that fix it?
Click to expand...
Click to collapse
Three options I can think of- if you use adb reboot recovery I believe it will load the stock recovery- the other option is to use odin to go back to complete stock. Finally you could use the option for clockwork in this thread look for the link under "B]Update.zip (for clockwork recovery and includes all the listed apps below)"
EDIT: I can confirm that "adb reboot recovery" loads the stock recovery when you have clockwork

bubby323 said:
FLASHING CUSTOM RECOVERY
Here is where it gets a tad bit more complicated. First off, you have to download the zip --- but this time before running the bat you have to open up command prompt and redirect it to your C:/android-sdk-windows/tools folder and then run the following code.
adb devices
adb shell
su
remount rw
exit
exit
Now the command prompt should close, and you can run the run.bat for build 31 of clockwork recovery flasher. Once more, your phone will reboot and after the script is done running and says "press any key to exit...." you can press enter and boot into recovery.
Click to expand...
Click to collapse
Im having a little issue with this. Im running windows 7. Can I do this in windows 7? Also when it says redirect it to your C:/Android---- do I have to change the drive to ex. cd c:/ first or do i just type in the command prompt C:/android-sdk-windows/tools and hit enter and follow the rest of the commands? Sorry extreme noob here..
Thank you for any help!!

I have ClockworkMod Recovery installed, how can I get into the stock recovery to apply this?

Look 2 posts up
Sent from my SPH-D700 using XDA APP

You need to use the DG27 uninstaller instead of the DI07 uninstaller to update to DI07.
The DI07 uninstaller is just to go back to stock DI07 kernel if you already updated
DG27 uninstaller: http://www.sdx-downloads.com/devs/noobnl/one.click.stock.&.root.uninstallerv1.0.1.zip

I think it needs to be pointed out that this alone won't work if you are like me and have removed apps from the phone. All those apps must be restored in addition to reverting to stock kernel before the OTA update can be applied. At least that's how I understand it. Feel free to correct me if I'm wrong.

Thanks a lot, I appreciate step-by-step tutorials like this for noobs like myself ... this made things a lot easier since some of the stuff (files, instructions, etc.) was all over the place.

would seem that way because I removed the alarmclock to start and when i try to run update.zip from sd it fails when checking current system @ /system/app/AlarmClock.odex
i tried rerooting and reinstalling alarm clock using the backup from titanium. says it is successful but i do not find it in my apps drawer. it still fails there too..
WisdomWolf said:
I think it needs to be pointed out that this alone won't work if you are like me and have removed apps from the phone. All those apps must be restored in addition to reverting to stock kernel before the OTA update can be applied. At least that's how I understand it. Feel free to correct me if I'm wrong.
Click to expand...
Click to collapse

Titanium backup does not restore apps in /system. You have to restore those by hand.

Im officially struggling, undid the root then copy/paste the update to the sdcard, renamed it. It unzips but says its failed to open /sdcard/update.zip(no such file or directory)...suggestions?
I know that in the step it said to copy it to the root on the sd but im am very green to this stuff, and didnt see a folder marked that, therefore I just copied it to the sd card

I can't get Clockwork to flash now. I walked through the steps...I did the remount crap and ran the bat and it rebooted the phone but when i reboot into recovery it goes to the normal recovery screen. Now if I try to redo it it does not recognize the remount rw and i can't get anywhere with it and i'm stuck with no clockwork.

but this time before running the bat you have to open up command prompt and redirect it to your C:/android-sdk-windows/tools folder and then run the following code.
adb devices
adb shell
su
remount rw
exit
exit
Click to expand...
Click to collapse
This part is unnecessary because the recovery zip comes with adb built in

is there a manual way to push this to the phone? These one clicks never seem to work for me ever it's just easier to do it myself.

Whosdaman said:
This part is unnecessary because the recovery zip comes with adb built in
Click to expand...
Click to collapse
No you must do this in order to get clockwork.

[ubuntu Q] Any way to root using Ubuntu?

is there a way to use ubuntu to root the epic? I have ubuntu and I want to root my epic but I can't figure out how to use the one-click method because I can't really use the drivers. I was trying to use the terminal with adb but I don't really know what I am doing.

linux doesnt need drivers i made a one click script for linux ill see if i cant find it
http://www.mediafire.com/?hk59z8j5dve6tgf
download that and run the clickhere.sh it should root you just fine, you may need to make the script and adb executable

You can try following along the run.bat script included in the one click root. I did not need to install any drivers to root using Ubuntu, but I did download the Linux version of the android sdk (from Google) just in case (instead of using the adb included in the one-click-root download.
If you have your android-sdk-linux_x86 directory in ~/Downloads/, and you extracted the one.click.root file into ~/Downloads/ as well, here's what you could do:
cd ~/Downloads/one.click.root
(Now you're in the location of the one click root files.)
Next, type each line of the run.bat file manually. Any time you see "adb" replace it with:
sudo ../android-sdk-linux_x86/tools/adb (command)
You'll need to adapt a bit to your situation, but because most of the adb commands are native to adb and run on the phone, they should work verbatim on your Ubuntu system.
Didn't someone put out a Linux one click root, though?
EDIT: Yes, shabbypenguin did. Looks like he posted it above me before I finished typing my post. Whoops.

Complete Big edit....
I thought I bricked my phone but I didn't. I ended up getting the permanent root. I used this guide http://forum.sdx-developers.com/epic-development/adb-root-exploit-test/
Is there anything special I am missing? like busybox? or remount scripts? not sure what either of those are.

remount allows your system to have rw access with a simple command, busybox.. think of it as an extended shell
the zip i included in my post is based off noobnl's latest version and works fine with linux. i made it while using ubuntu

shabbypenguin said:
linux doesnt need drivers i made a one click script for linux ill see if i cant find it
[snip]
download that and run the clickhere.sh it should root you just fine, you may need to make the script and adb executable
Click to expand...
Click to collapse
Thank you so much for this! ... "You have no chance to survive make your time" means I'm rooted?

i made version 2, its in my sig, will root and install clockwork mod 2.5.1.0

[Q]How to install Flash ClockworkMod Recovery on M701 (Apad)?

Hi all!
I finally managed to ROOT an aPad M701 using z4Root.apk
Now I want to make an image of my entire ROM tablet, I've heard that under the ROM manager app is a tool called "Flash ClockworkMod Recovery" that has to be installed in order to make a full ROM backup.
The problem is that everytime I try to install it a screen pops out telling me to choose from the list my model of phone (I'm on an aPad tablet), since I'm not on a phone, I'm unable to continue with the process!
Any method or workaround for installing Flash ClockworkMod Recovery on Haipads/aPads M701?
Thanks in advance for the help.

Custom Recovery Image
On Team Telechips website there is a custom Clockwork recovery image toward the bottom of the page.
Use the .bat file they include in their ZIP file or push the .img file to /nand and flash. You will then be able to back up everything with the custom m701 clockwork application.
If the .bat file doesn't work for you, try opening it up as text and use the commands as a guide to push via adb.

Thanks a lot for the reply Clookeno but I dont know where to start with this, do you know any step by step guide I can use to achieve this?
Again thanks for the info.

Adb push issues
Clookeno said:
On Team Telechips website there is a custom Clockwork recovery image toward the bottom of the page.
Use the .bat file they include in their ZIP file or push the .img file to /nand and flash. You will then be able to back up everything with the custom m701 clockwork application.
If the .bat file doesn't work for you, try opening it up as text and use the commands as a guide to push via adb.
Click to expand...
Click to collapse
I'm trying this and when using adb push to /nand I'm getting back "failed to copy 'recovery.m701.img' to '/nand/recovery.m701.img': Read-only file system"
I'm currently running Haipads 2.2 version and I was looking at testing out CM6 version, but can't seem to get the img file over.
And Ideas?

read only file
adb shell mount -o remount,rw /dev/block/mtdblock3 /system

The /nand folder needs to be read-writeable....since you use z4root go into temporary root and the push the file into /nand folder

Locobox said:
Thanks a lot for the reply Clookeno but I dont know where to start with this, do you know any step by step guide I can use to achieve this?
Again thanks for the info.
Click to expand...
Click to collapse
Locobox, there likely isn't a step-by-step guide for the procedure because it has a .bat file which is basically a executable file in windows that runs a set of commands in the DOS prompt for you. Basically you just double click the install_recovery.bat file and it puts the ADB commands in for you to push the recovery image to your tablet.
If you right click the .bat file and click edit you will see the following ADB commands:
adb push recovery.m701.img /nand/recovery.m701.img
adb shell sync
adb shell flash_image recovery /nand/recovery.m701.img
adb shell sync
adb shell reboot recovery
If you are familiar with ADB you can also copy the .img file to your sd card and flash it from there.
i recommend you have root access and the ADB utility.
Sorry it took so long to reply, work has been killing me lately....

poole699 said:
I'm trying this and when using adb push to /nand I'm getting back "failed to copy 'recovery.m701.img' to '/nand/recovery.m701.img': Read-only file system"
I'm currently running Haipads 2.2 version and I was looking at testing out CM6 version, but can't seem to get the img file over.
And Ideas?
Click to expand...
Click to collapse
poole699,
I have tried everything you can think of to put CM6 on the 2.2 Haipad firmware (which is really a modded 2.1) and had no luck. Either the system directories are all messed up or they locked the ability to edit it somehow. If you figure it out let me know because i have wanted to try it for a while.
I have a working team telechips 2.2 with market and correct orientation settings but it took ALOT of trial and error. If you go that route make sure you back-up your pointercal file because if you do not you will likely have to go back to an official release, save it, and try the telechips mod again...
Good luck

Clookeno said:
Locobox, there likely isn't a step-by-step guide for the procedure because it has a .bat file which is basically a executable file in windows that runs a set of commands in the DOS prompt for you. Basically you just double click the install_recovery.bat file and it puts the ADB commands in for you to push the recovery image to your tablet.
If you right click the .bat file and click edit you will see the following ADB commands:
adb push recovery.m701.img /nand/recovery.m701.img
adb shell sync
adb shell flash_image recovery /nand/recovery.m701.img
adb shell sync
adb shell reboot recovery
If you are familiar with ADB you can also copy the .img file to your sd card and flash it from there.
i recommend you have root access and the ADB utility.
Sorry it took so long to reply, work has been killing me lately....
Click to expand...
Click to collapse
Thanks again for the info, but I'm not familiar with ADB. The procedure seems difficult for me hope this thread helps a lot of other users!
Again thanks for the response.

M701 Screen Flip
Hi guys, I've got a bit of a problem with my M701 tablet. I did a factory reset the other day and now the digitizer is inverted. The screen works fine but when I touch the top it senses the bottom & left = right.
This is a complete pain in the arse.
I plugged the unit into a keyboard via the usb port as a workaround until I could get into it to try to resolve the issue but I'm now stuck in a loop at the sign in to google bit. Every time I sign in it takes me back to the sign in page.
This is also a complete pain in the arse.
It doesn't have clockworkmod installed and so when I tried to install update.zip as per the above post, it comes up with 'E:Failed to verify whole-file signature' error message and aborts.
Again, a complete... you get the picture...
So, I'm slightly frustrated with it to say the least and was wondering if any of you intelligent types could either point me in a suitable direction that doesn't involve the bin. Or a window...
Many thanks in advance.

Help
Locobox said:
Hi all!
I finally managed to ROOT an aPad M701 using z4Root.apk
Now I want to make an image of my entire ROM tablet, I've heard that under the ROM manager app is a tool called "Flash ClockworkMod Recovery" that has to be installed in order to make a full ROM backup.
The problem is that everytime I try to install it a screen pops out telling me to choose from the list my model of phone (I'm on an aPad tablet), since I'm not on a phone, I'm unable to continue with the process!
Any method or workaround for installing Flash ClockworkMod Recovery on Haipads/aPads M701?
Thanks in advance for the help.
Click to expand...
Click to collapse
How were you able to root your apad with Z4? I was not able to find the setting to activate the USB Debugging?
Thanks,
~b

is there development in the forums for the Apad line? im looking at getting a m702 the next 1 up, well i want to find a tablet rom maybe alowing me to run gingerbread on it,
any help?

ljohnso16 said:
is there development in the forums for the Apad line? im looking at getting a m702 the next 1 up, well i want to find a tablet rom maybe alowing me to run gingerbread on it,
any help?
Click to expand...
Click to collapse
I'm not sure if this of help to you, but I have a M701 2Gb (probable fake version), I've messed around with the basics on my exploring Android type thread:
http://forum.xda-developers.com/showthread.php?t=1004824
I've put recovery on both 2.1 and 2.3 roms (need different versions). Any other q's then let me know, I don't know much yet but learning the best i can.
A very useful place for info on the M701 is here:
http://www.androidtablets.net/forum/groups/11-haipad-m701-m701-r.html

[ROOT + CWM + OC KERNEL + Ubuntu] ZTE V11A / V71A / v55 HC3.2

The information provided in this thread is no longer up to date, although useful troubleshooting information can be found for those having issues. For those who would prefer to have the most up-to-date versions of CM9, CM10 or ParanoidAndroid supported by an awesome developer, go here
WARNING: IF YOU UPDATE YOUR TABLETS TO THE LATEST v03 UPDATES OF THE OFFICIAL ROM, YOU WILL LOSE THE ABILITY TO ROOT IT USING THE SUPERBOOT METHOD AND IT WILL BECOME A HUGE PAIN TO RE-INSTALL CWM/CUSTOM ROMS. INSTRUCTIONS FOR THIS SITUATION ARE PRESENTED BELOW, BUT PLEASE KEEP THIS IN MIND AND TRY TO READ THE THREAD CAREFULLY BEFORE MAKING SUCH CHANGES.
For those who need it, you can find a nandroid backup of Vodafone Romania's stock ROM for the v71a, here
Hello friends. With great thanks to utkanos, Koush and mobilx we now have a public alpha CWM and root available on both the ZTE V11A and the V71A, also known as the SFR StarTab 7/10, Vodafone SmartTab 7/10, as well as Sprint's (ZTE) V55 with credits due to utkanos for porting CWM, mobilx for being arguably the most motivated searcher of the holy root grail, and PaulOBrien from modaco and his superboot solution. We also thank alterbridge86 and eldarerathis for their advice and support. Additionally, credits go to joe.stone for custom kernel with loop device support, OC, touched voltages and a few other goodies.
Also, for interested developers, I have made the source code of the kernel available in a more easily accessible fashion. The source code (3 parts, contains the source for both models) is available here:
Part 1, Part 2, Part 3.
INSTALLING CWM:
A new optimized version of CWM for 7"and 10" tabs has been put together by joe.stone. I will also keep utkanos' links available below for those who prefer his versions or wish to thank him for his early efforts in making our tablets awesome
joe.stone said:
For those who have troubles with cwm recovery (freeze while backup ) i have created a new version. Flashable from fastboot.
10" CWM Recovery
7" CWM Recovery
Credit goes to joe.stone.
Click to expand...
Click to collapse
joe.stone said:
If you updated your tablet ROM via OTA or updater exe and can no longer install CWM, follow the following instructions:.
In firmware v03b fastboot flash is disabled and from a running system flash_image will fail too.
Download the twrp recovery http://goo.im/devs/joestone/twrp/v71_recovery.img
download the twrp recovery zip flashable version too
http://goo.im/devs/joestone/twrp/V71A_TWRP.zip
download kernel #60
http://www.4shared.com/zip/tzrUo5_N/v7_kernel_60.html?
copy the two zip files to the sdcard
If you want flash kernel#60 then do the following:
adb reboot bootloader
the tablet will reboot and you will get only a blank screen . Be sure that the drivers are installed from windows update for the fastboot interface.
check it with : fastboot devices. If you get waiting for device the drivers are not installed.
fastboot boot v71_recovery.img
The twrp recovery comes up. Now you can install twrp by selecting install menu. Browse to the v71twrp.zip on the sd and install it. Now you have permanent twrp recovery.
now go back to install menu browse to the v7_kernel_60.zip and install it.
reboot and enjoy.
These are kernel #60 links for the other models :
Sprint Optik (V55)
http://www.4shared.com/zip/RTZrSXyV/v55_kernel_60.html?
SmartTab10 (V11A)
http://www.4shared.com/zip/PrW1TWHF/v10_kernel_60.html?
OR
You can flash cwm using adb , you need root rights .The best is when adbd is running in root mode (for eaxample kernel#60).
Download this :flash_image binary
then turn on usb debugging.
to flash cwm you need the following commands:
adb push CWMrecovery.img /data/local/tmp
(where cwmrecovery.img is the name of the cwm image file name.)
adb push flash_image /data/local/tmp
adb shell chmod 755 /data/local/tmp/flash_image
adb shell (you need # not $ for flashing , so if you got $ type su to get #)
cd /data/local/tmp
./flash_image /dev/block/mmcblk0p18 CWMrecovery.img
Dont forget to remove the install-recovery.sh file from /system/etc othervise it will install stock recovery at system start if it has not the stock recovery.
To revert the bootloader you need to flash NON-HLOS.bin"to "/dev/block/mmcblk0p1" and "emmc_appsboot.mbn" to "/dev/block/mmcblk0p7" from a previous version .
Click to expand...
Click to collapse
Utkanos' v11a version is here.
Utkanos' v71a version is here.
Credit goes to utkanos, mobilx and koush. I have also attached these files at the end of the post.
Also attached, is the original 7-inch stock recovery file, for users who may wish to return to stock and have not performed backup.
--> Plug your tablet into usb, launch a command line, and use "adb reboot bootloader"
--> Download the CWM Recovery image from the link that fits your device.
--> Place it into the adb/fastboot folder (I am assuming you have downloaded fastboot already from the link above, during the root procedure).
--> In the command line, navigate to that folder (use "cd <path>").
--> input the command "fastboot flash recovery <filename>".
--> Reboot into recovery mode (should be Power + Volume down).
--> You should now be in CWM Recovery, and can now attempt to perform a nandroid backup.
Also, in order to prevent a possible hang, you should:
--> Reboot the tablet into the Android OS;
--> Mount it through USB;
--> Go into the clockworkmod folder;
--> Create an empty file with no extension called ".hidenandroidprogress"
After a period of testing this will be submitted to the Koush's Rom Manager. Source code is also available herehere, linked from utkanos' post.
What works:
Nandroid backup/restore on internal sdcard
Battery stats wipe
Dalvik wipe
Cache wipe
etc.
What does not work so far:
USB mass storage
credits:
utkanos
Koush
Click to expand...
Click to collapse
Modified Kernel Available, all credits to joe.stone, give him thanks here:
joe.stone said:
Here it is.
There is a new kernel version available. The new version is #60 and flashable from cwm recovery .
Changelog :
-Revert GPU overclock
-Revert change of system audio files (because of bootloops on some devices after installation #55)
-Increased system volume on kernel level
-Changed VMALLOC_RESERVE=0x19000000 to VMALLOC_RESERVE=0x10000000
-Added Apple Magicmouse HID support
-Added Microsoft HID support
-Changed cpu minimum freq 345MHz to 432 MHz to avoid the black screen effect (the screen does not wake up , you have to reset )
V55_kernel_60.zip Hope will work fine on v55.
V7_kernel_60.zip
V10_kernel_60.zip
Click to expand...
Click to collapse
Also, Benny3 has put together a CWM-flashable ROM package for the V55 tablet, including Joe's kernel #60 and a number of useful goodies. You can thank him and download the package from here.
Both device (v71, v11) were migrated into one kernel tree , so they both use the same source. (In case of v71 it is much newer source)
The whole kernel source was updated from the v55 sources .
Now they are in cwm recovery flashable format , because this package updates the kernel modules too in /system/lib/modules and enables to use the agps and NTP server setting was corrected . It points to europe.pool.ntp.org instead of the test one . Now my tab finds position within seconds . With the new kernel for me it seems the touchscreen is much better , but as before I am waiting for the feedbacks. Other fixes include: Touchscreen sensitivity, USB Charging etc.
Installation :
download the zip file
copy it to your tab's internal storage
start the tab in clockworkmod recovery
select install zip from sdcard
select the file for your model
install
reboot
and stock kernel for 10" :
stock kernel[/QUOTE]
Finally, if you want to obtain a dump of boot.img, please consider the following advice, also by mobilx, here:
mobilx said:
It is a mmcblk device not mtdblock
dd if=/dev/block/mmcblk0p8 of=/sdcard/boot_backup.img
dd if=/dev/block/mmcblk0p18 of=/sdcard/recovery_backup.img
Click to expand...
Click to collapse
ROOTING:
mobilx said:
It is recommended that you skip these steps and proceed to flashing clockwork mod for your respective device from the start using fastboot, and from inside CWM install joe's kernel (or custom rom), which you can find below. Joe's kernels and rom already come with significant updates to stock Vodafone systems, and are pre-rooted.
We will use superboot to root. What does superboot do? It puts the SU binary and makes a 'insecure' kernel to be loaded temporarily on to the device through ADB remount. So it's only purpose is to make ROOT. After execution, you will still be on the stock kernel, only with root privileges.
This method is for the advanced users only who want to have root before we have a fully functional CWM running. With the CWM the root method will be easier.
IMPORTANT!
At this point we have no way to repair a broken device to a factory state. We can unroot and that is it. It is advisable do make dump of your rom before making any changes to the system. We are not responsible for any damage that can occur in the root process and after that.
What will you need?
--> Download Fastboot+Superboot.img from here.
--> Install ADB through the SDK, download from here, although the ADB included with the ZTE drivers should also work.
--> Install the ZTE drivers, you can find them here, although they should already be included on your device when first mounting it.
--> don't forget to enable USB debugging in the tablet's application settings.
--> Put the fastboot.exe and the superboot.img files in the working directory you will be running adb from (Default should be at "C:\Program Files\ZTE Handset USB Driver".
--> Open a Command Line (Start Menu > Run > CMD) and navigate to the working directory. (Use "cd C:\Program Files\ZTE Handset USB Driver" or alter the path accordingly).
--> Write the following commands withing the command line:
--> adb reboot bootloader
--> fastboot boot superboot.img
--> The device should now boot with the Superuser.apk installed and SU in the /system/xbin/su, as well as allowing you adb root commands. Now run the following:
--> adb remount
--> adb shell
--> ln -s /system/xbin/su /system/bin/su
--> You can now exit the ADB shell and reboot the tablet.
--> Install busybox from the market and check the SU binary version with the Superuser.apk - try to update. If it succeed you are done.
Credits:
sangemaru
utkanos
PaulOBrien from modaco and his superboot solution
Click to expand...
Click to collapse

Reserved for future posts

I have ZTE V11A aka Vodafone Smart Tab 10 in my possession
I'm very interested in obtaining root for this device, so if I can be of any help, please let me know.
I hope that whis device will gain more popularity in the near future, because of it's excellent hardware and low price.
Is there any progress going on with rooting this device?
P.S. Two more questions,
Has anyone found where to buy 40pin to hdmi cable/connector? (because you don't get one in the box)
Does any of you experience clock drift with your device after some time, mine is drifting forward about 20min per day with no automatic Network Sync.
Thank you.

assdksl said:
I have ZTE V11A aka Vodafone Smart Tab 10 in my possession
I'm very interested in obtaining root for this device, so if I can be of any help, please let me know.
I hope that whis device will gain more popularity in the near future, because of it's excellent hardware and low price.
Is there any progress going on with rooting this device?
Click to expand...
Click to collapse
Currently, me and mobilx are trying to put aside time to either:
obtain a dump of the boot.img that we can inject su and superuser.apk into;
compile the source code into a flashable rom that we can inject su and superuser.apk into;
get clockworkmod working on the device;
Due to time constraints, I haven't made much headroom this week, but I'm taking a couple of days off work and hope to make some progress.
P.S. Two more questions,
Has anyone found where to buy 40pin to hdmi cable/connector? (because you don't get one in the box)
Does any of you experience clock drift with your device after some time, mine is drifting forward about 20min per day with no automatic Network Sync.
Thank you.
Click to expand...
Click to collapse
Haven't looked for it, but so far accessories for this line of devices seem to be lacking. With the popularization by Vodafone and the launch of the new Sprint V55 and similar tablets, these accessories should become more popular.
I haven't had any problems with the time on my device, sounds really weird.

assdksl said:
Does any of you experience clock drift with your device after some time, mine is drifting forward about 20min per day with no automatic Network Sync.
Click to expand...
Click to collapse
Clock drift is happening due to Network-provided time setting. Im not sure what is causing this. It could be related to a Vip network or a failure of a process which obtains time from the network. If you want this not to happen just untick that option in settings.

Thank you both for quick answering my questions.
mobilx said:
Clock drift is happening due to Network-provided time setting. Im not sure what is causing this. It could be related to a Vip network or a failure of a process which obtains time from the network. If you want this not to happen just untick that option in settings.
Click to expand...
Click to collapse
Yes, indeed, but when I untick sync with Network-provided time, clock is ticking faster then it should.
It seems that clock chip on my device is not calibrated well or there is some other bug, it seems that it is HW issues... this is little more explained here:
http://blogs.keynote.com/mobility/2...wrist-watch-android-doesnt-keep-the-time.html
It seems that I was unfortunate and get device with bad clock, also without root I'm unable to use ClockSync app that will solve my problem.
But what is bugging me, is the fact that I also have SGS I9000, and it is synchronizing with Vip network just fine.
Mobilx are you experiencing time drift issue with network-provided time sync, but with manual time settings it is working fine?
sangemaru said:
Currently, me and mobilx are trying to put aside time to either:
obtain a dump of the boot.img that we can inject su and superuser.apk into;
compile the source code into a flashable rom that we can inject su and superuser.apk into;
get clockworkmod working on the device;
Due to time constraints, I haven't made much headroom this week, but I'm taking a couple of days off work and hope to make some progress.
Click to expand...
Click to collapse
I am a software developer, and I have some Android programming knowledge, but I'm not experienced much with Linux and compiling flashable Roms, but I can try In any case, if I can help, just let me know.

assdksl said:
Mobilx are you experiencing time drift issue with network-provided time sync, but with manual time settings it is working fine?
Click to expand...
Click to collapse
Yes it happend to me once. First I unticked the network-provided time sync and after restart I ticked it again. The clock is fine since than.

assdksl said:
I am a software developer, and I have some Android programming knowledge, but I'm not experienced much with Linux and compiling flashable Roms, but I can try In any case, if I can help, just let me know.
Click to expand...
Click to collapse
Well, so far what possible leads we have that I can think of are these:
mobilx suggested this thread http://forum.xda-developers.com/showthread.php?t=443994 for packing/unpacking boot.img
to quote Alterbridge of Team Overcome: "I presume the ZTE tablet uses boot.img format for its kernels, in which case you can extract the initramfs using mkbootimg (there are a number of scripts floating around). from there you can modify whatever you want in the initramfs and then repackage the boot.img and be on your way."
eldarerathis gave me some more instructions: "You basically need to extract the ROM's zip and add su/Superuser in the proper folders (su in /system/bin, Superuser in /system/app). You'll probably also have to look at the updater-script and add something to give su executable permission. It's usually something like 'set_perm(0, 0, 6755, "/system/bin/su");' that you need to add. The updater-script should be in the zip under /META-INF somewhere."
These are some of the useful bits of advice I received that could probably be put to good use when I have some free time. If you feel that anything is helpful, feel free to try it out.

sangemaru said:
Well, so far what possible leads we have that I can think of are these:
mobilx suggested this thread http://forum.xda-developers.com/showthread.php?t=443994 for packing/unpacking boot.img
to quote Alterbridge of Team Overcome: "I presume the ZTE tablet uses boot.img format for its kernels, in which case you can extract the initramfs using mkbootimg (there are a number of scripts floating around). from there you can modify whatever you want in the initramfs and then repackage the boot.img and be on your way."
eldarerathis gave me some more instructions: "You basically need to extract the ROM's zip and add su/Superuser in the proper folders (su in /system/bin, Superuser in /system/app). You'll probably also have to look at the updater-script and add something to give su executable permission. It's usually something like 'set_perm(0, 0, 6755, "/system/bin/su");' that you need to add. The updater-script should be in the zip under /META-INF somewhere."
Click to expand...
Click to collapse
Thank you, I will do some reading for a start.
We are sure that bootloaders are unlocked?
sangemaru said:
Currently, me and mobilx are trying to put aside time to either:
obtain a dump of the boot.img that we can inject su and superuser.apk into;
compile the source code into a flashable rom that we can inject su and superuser.apk into;
get clockworkmod working on the device;
Click to expand...
Click to collapse
Did you consider getting clockworkmod working in more details? Is it simpler then above method?
I have found this article regarding putting clockwork mode to new devices, I just read it briefly...
http://www.koushikdutta.com/2010/10/porting-clockwork-recovery-to-new.html

assdksl said:
Thank you, I will do some reading for a start.
We are sure that bootloaders are unlocked?
Did you consider getting clockworkmod working in more details? Is it simpler then above method?
I have found this article regarding putting clockwork mode to new devices, I just read it briefly...
http://www.koushikdutta.com/2010/10/porting-clockwork-recovery-to-new.html
Click to expand...
Click to collapse
That's fine. We have a dev utkanos who agreed to build the CWM for our device. He is very experienced in this stuff. The only way to build a proper CWM is to get a boot.img dumped or extracted from a leaked ROM.
So what we need to do:
Get root via some exploit (there is none for 3.2 HC yet) , dump boot.img and build CWM, flash CWM with fastboot, or
Find leaked ROM , extract boot.img, build CWM, flash CWM with the fastboot, root device with Update.zip
Yes the fastoboot is working and the bootloader is unlocked.
I have tried these exploits so far:
GingerBreak
psneuter
zergRush
Also I have tried:
Acer iconia 100 method ADB
Acer iconia 500 method
All ideas are welcome.

Ladies and gentleman the ROOT is here Device is successfully rooted with the superboot method.
Thanks to my friend sangemaru who made this possible.
Expect CWM soon. utkanos is working on it.
Need some testing, before this goes to public

That's great news mobilx! Looking forward to a root and ICS sometime in the future

Congrat`s guys,nice work and many thanks from all users.
This is a beginning of a beautiful friendship with SmartTab
We expect nice custom roms and maybe in a short time and ICS rom for this excellent tablet.
If I or we (other members) can help with something,please,let us know,i dont know programming but i can use Paint (just kidding)

Jeeej!!! I'm looking forward to it!

Ok lets roll
While we are waiting for CWM to be build we can root ZTE V11A/V71A aka Vodafone SmartTab 10/7 with the superboot.
What the superboot does? It puts SU binary and makes a 'insecure' kernel to be loaded temporally on to device( ADB remount). So it's only purpose is to make ROOT. After reboot you are on your old kernel but with the root.
This method is for the advanced users only who want to have root before we build a CWM. With the CWM the root method will be easier.
IMPORTANT!
At this point we have no way to repair a broken device to a factory state. We can unroot and that is it. It is advisable do make dump of your rom before making any changes to the system. We are not responsible for any damage that can occur in the root process and after that.
What we need?
ADB installed through SDK
Zte drivers installed --> debugging ticked in options
fastboot + superboot.img --> Put files in the adb working dir
>adb reboot bootloader
>fastboot boot superboot.img
Device should boot with Superuser.apk installed and SU in the /system/xbin/su.
>adb remount
>adb shell
#ln -s /system/xbin/su /system/bin/su
Install busybox from the market and check the SU binary version with the Superuser.apk - try to update. If it succeed you are done.
#exit
$exit
>adb reboot
Device will reboot with the stock kernel but rooted.
Credits:
sangemaru
utkanos
PaulOBrien from modaco and his superboot solution

Thx mobilx! Hvala

All it's OK
It's working also on v71a.......LOL
10x man

urs71 said:
It's working also on v71a.......LOL
10x man
Click to expand...
Click to collapse
I can also confirm this working on 7 inch

urs71 said:
It's working also on v71a.......LOL
10x man
Click to expand...
Click to collapse
jakaka said:
I can also confirm this working on 7 inch
Click to expand...
Click to collapse
That is great guys. sangemaru will be very happy because he owns A71A
So you can confirm that it boots and the touchscreen is working? That means the kernel is the same for those two variants.

V17A
YES, all work perfectly...........setcpu, blackmarkt,root uninstaller, lucky patcher, etc
The only differences between v11a and v71a is the size of the display
we are wating for CWM..........10x again
v71a