Database Info

[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.

Rooting Issue - I9020T [ SOLVED]

Hello,
I am stuck with rooting process. I tried rooting, unrooting before but this time, for some odd reason. I am unable to proceed
I followed this procedure from unlockr website to root the nexus S. Could not post the exact link because of restrictions
Phone is unlocked , USB debugging is ON. ADB mode is working, I can use other commands. But its giving me the following error on step 6 . Line 3
Mount : Operation Not permitted
Attaching image !
When I boot using volume up & Power button and go to Recovery, It gives me exclamation mark & Android Sign... So I cant unroot it either.
I always tried to unroot so I can go back to original state and restart the process. If I flash through recovery.img I can go into recovery but after few steps, I am stuck

Yeah that's normal. The mount command requires root permission (which you don't have yet)
Generally what you have to do after flashing the (right version of) custom recovery is:
copy the su.zip to your SD card
reboot into custom recovery
choose apply zip from SD card and select the su.zip
reboot
That's it.

Su have already been installed in previous step. Infact, I can even see its icon in menu...

Then it sounds like your recovery reverted back to stock. Did you rename the .sh file that rewrites the recovery on reboot? If not, do that using root explorer or any other method you find in the guide. Then flash the recovery again and it will stick.
Sent from my Nexus S using Tapatalk

No I didnot renamed. I was just following the process. I tried to unroot but cant do it either. I am stuck

ahaseeb said:
Su have already been installed in previous step. Infact, I can even see its icon in menu...
Click to expand...
Click to collapse
If su is installed correctly then for the "Mount : Operation Not permitted" problem, you just have to type su in adb shell (there may be a Superuser permission popup on the phone, just allow it) -- the prompt should change from $ to #, which means you are now root. After that the mount command should work.
To make custom recovery stick on every boot, rename /system/etc/install-recovery.sh to other name e.g. install-recovery.sh.disabled

When I typed su it said Permission denied !

Just because you have superuser in your app drawer does not mean you're rooted. You can downloaded from the market on any phone/rom.
You are not rooted.
Flash custom recovery via fastboot
Boot directly into recovery etc.

ahaseeb said:
When I typed su it said Permission denied !
Click to expand...
Click to collapse
Then I suggest you re-install Superuser from Android Market. Normally it shouldn't just say permission denied, there should be a Superuser popup asking for permission.
Or better, try to redo everything following this guide instead.

Again YOU HAVE TO FLASH SU FROM CUSTOM RECOVERY.
Do not install from market. Hell don't even boot up the OS. Flash recovery. Boot directly into recovery and flash su.zip from your phones internal storage/sdcsrd in recovery. The you're rooted.
Now you can update delete/rename the script to make the custom recovery stick. Update su in market or whatever else you want to do.
.

I believe i got it fixed. When ever the phone used to boot after installation of SU, dialogue box to ask for unlock. That dialogue box disappear very quickly. It took me time to figure it out. Thanks, I guess I am good now.
Thanks every one

[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

A701 rooting

Got A701 with following version:
Acer_AV_043_A701_RV08RC02_EMEA_DE
Acer_AV043_A701_1.017.00_EMEA_DE
trying to use rooting methods don't help much.
Got unlock and installed CWM, got su copied over to /system/xbin/ or to /system/bin, but not too much use. Any ideas how to get root without reflashing a different rom?

fix found
OK...got a fix...i guess
0) install CWM
1) nandroid backup (you're crazy if you don't do it)
2) download backup to your PC
3) PM me for a modified boot.img (or use some kitchen to mod the boot.img and get rid of the pesky ro.secure) (or let me know if you have time to write some proper content)
4) adb reboot fastboot
5) fastboot flash boot newboot.img
6) reboot to recovery
6) adb push su /system/bin/
7) reboot
8) happy days
Works for
Acer_AV_043_A701_RV08RC02_EMEA_DE
Acer_AV043_A701_1.017.00_EMEA_DE
for others most likely will cause a nuclear disaster though

If you have CWM, rooting is as easy as flashing the Superuser zip from
http://androidsu.com/superuser/
Sent from my GT-I9000 using xda app-developers app

Pawitp
nop, it is not enough.
With firmware that i 've got, the ro.secure has to be disabled, and even after that when i have everything running from root i can't remount system as rw.
Using any of the older firmwares isn't an option, as i apparently seem to have the "latest" one and i wanna stick to it to share at a later stage

andlommy said:
Pawitp
nop, it is not enough.
With firmware that i 've got, the ro.secure has to be disabled, and even after that when i have everything running from root i can't remount system as rw.
Using any of the older firmwares isn't an option, as i apparently seem to have the "latest" one and i wanna stick to it to share at a later stage
Click to expand...
Click to collapse
Having root and being able to remount /system as rw are 2 different things. Acer's kernel has some block which disallow /system from being remounted as rw. You'd need to flash a source-built kernel or just make the modifications you want in /system from recovery.

So it's the kernel doing a remount block? Wow...recompiling means I'd need to get source etc. Sounds quite a job...
Sent from my A701 using Tapatalk 2

Ezterry provided a script in github or pastbin cant remember to do this and ez explained it to me on how to use it.
If you send me the original boot.img I can patch it for you so you have full system /RW.
It takes 10 minutes to do it.
Pm me as I don't come in here very often. Or go true MD as he's my rusky homeboy.
But only if you are interested. I can do this for A700 and A701 ICS and JB boot.img

civato said:
Ezterry provided a script in github or pastbin cant remember to do this and ez explained it to me on how to use it.
If you send me the original boot.img I can patch it for you so you have full system /RW.
It takes 10 minutes to do it.
Pm me as I don't come in here very often. Or go true MD as he's my rusky homeboy.
But only if you are interested. I can do this for A700 and A701 ICS and JB boot.img
Click to expand...
Click to collapse
I already posted the modified boot image you did for the 701
http://forum.xda-developers.com/showthread.php?t=1934056
Should just have to unlock, fastboot the boot image, Download SU and BB and be good to go.
MD

Moscow Desire said:
I already posted the modified boot image you did for the 701
http://forum.xda-developers.com/showthread.php?t=1934056
Should just have to unlock, fastboot the boot image, Download SU and BB and be good to go.
MD
Click to expand...
Click to collapse
I see it know, I tought it was for different img.
And you got only 5 thank you's for posting that ?Only 5 A701 sold ? Or people are so big hearted these days?

BLU Advance 5.0 HD

It looks to me like the best phone $80 can buy I spent couple hours trying to figure out how to enable Multi User module.
My understanding is that adding this to /system/build.prop would bring users module back:
fw.max_users=3
fw.show_multiuserui=1
None of the commonly used apps can root this phone.
Without root I cannot remount /system to read-write to edit build.prop
Stock recovery can mount /system
There are options in recovery to run update from sd card or to update via adb sideload but the phone does not show in adb devices while in recovery. There is also fastboot option.
I also tried dirty cow exploit but it fails with "only position independent executables (PIE) are supported"
I am into this for only couple hours, so I know I am missing a lot. Any pointers that could get me closer to enabling Users module would be welcome.

So, after some reading, i figured I should be able to apply update form recovery that will replace build.prop with modified one. For start, to test things out, I just want to copy file from update.zip to /system/build.prop.test
I created update.zip with update-script and the file I want to add to /system.
Here is update.zip: www . filedropper.com /update_10
I signed update.zip using this:
www . learn2crack.com /2014/02/sign-android-apk-zip.html
I get error "Signature verification failed". Is the problem that keys are test keys or that they are outdated? Is some special manufacturer key required to sign updates?
I am not looking for someone to do this, I just need to be pointed in the right direction.

I have multiple users now :
- downloaded TWRP from bluroms.info
- connected the phone, enabled USB debugging and OEM unlocking in developer options
- run "adb reboot bootloader"
- after phone booted in fastboot mode
fastboot oem unlock (followed instructions on screen / all data wiped)
fastboot boot blutwrp.img (downloaded TWRP)
- twrp started...
- mounted /system
adb pull /system/build.prop
- edited build.prop
adb push build.prop /system/build.prop
adb reboot
- phone got stuck on logo after reboot
removed battery and started the phone again and all seems good

@sasha_ Hey I know this isn't about how to root but could you tell me exactly how you managed to root your Blu Advance 5.0 HD? PM me.

mrfunnybone said:
@sasha_ Hey I know this isn't about how to root but could you tell me exactly how you managed to root your Blu Advance 5.0 HD? PM me.
Click to expand...
Click to collapse
If by rooting you mean, installing supersu so that apps can request root access, i did not do that, because i do not need it. There must be some tutorial around about installing supersu once you root access to the /system - and the steps I described can you get there.

sasha_ said:
If by rooting you mean, installing supersu so that apps can request root access, i did not do that, because i do not need it. There must be some tutorial around about installing supersu once you root access to the /system - and the steps I described can you get there.
Click to expand...
Click to collapse
So is getting root access to system like booting recovery TWRP? then pressing the Mount button and checking System? Sorry I'm a newb at this.

I'd love to gain root on this phone I have twrp installed but can't seem to find a root method that works

Just in case you guys are still watching this, I posted my experience with this phone here
https://forum.xda-developers.com/showpost.php?p=75164672&postcount=26