ZTE V9 Tablet

[Guest cork45]

Not sure if this is the right place to post but is there any where that sells the V9 to Ireland?

[Guest Swedroidman]

Found this on the XDA forums, and it seems like ZTE is gonna let everybody who wants a upgrade to 2.2 be able to get it :D

ZTE light v9 2.2 upgrade from ZTE is here

--------------------------------------------------------------------------------

Download from here

http://www.mediafire.com/?b6ty863olhb36t8

please follow the instructions carefully.

You need to email ZTE a screencapture of a page.

Edited March 17, 2011 by Swedroidman

[Guest Sebastian404]

Found this on the XDA forums, and it seems like ZTE is gonna let everybody who wants a upgrade to 2.2 be able to get it :D

....

The program seems to be a cut down/fixed version of THIS program

From reading the word document, they seem to imply there is a file called something like (V9_GENERICV1.0.0B03(offical))...

that is the interesting part, that we need.

It looks like that Word Document is something they have sent out to telco service centres, its unlikely that anyone outside of one of ZTE's resellers would get a licence code to use that software..

Edited March 17, 2011 by Sebastian404

[Guest andi_baden]

I have a bigger problem, I just changed my framework-res.apk to a skinned one, and phone not booting, android text reloading all time, no recovery available, I cannot able to get adb, what can I do now? :D

An idea how to get adb work or go to recovery?

I got adb to work on XP with the adb drivers for the blade. It's working with my original ZTE light. I used it to make a rom dump without rooting.

[Guest Sebastian404]

BTW, anyone with a Optus MyPad...

can you dump your splash partition for me?

Edited March 17, 2011 by Sebastian404

[Guest slapnuts]

BTW, anyone with a Optus MyPad...

can you dump your splash partition for me?

Will do when i get home from work, does it matter that i am running your rom though?

[Guest Sebastian404]

Will do when i get home from work, does it matter that i am running your rom though?

No that's fine, I was experimenting with the Russian TPT and overwrite the standard android splash with....something horrible in russian (I think).....

Thanks

[Guest psychbiz]

For those concerned about being able to load applications to SD card, I suggest using Link2SD from the android market. I have a ZTE V9 (Optus Mytab), which I rooted and then installed Link2SD. After following the very clear install instructions I now am able to load all 'non-system' applications to the SD card and after updating the app database updates for apps works fine. I await the 2.2 upgrade of Android with great interest. Also interested in custom ROM for this device. Haven't felt confident installing a ZTE Blade ROM in case of compatibility issues.

[Guest Gaz14]

In case anyone is interested in changing the splash screen on the V9, well the optus mytab version atleast

I reflashed my splash screen to Fev's photo of lara bingle(Australian users should know who Fev and Lara are), looks good

I can write up how i did it if anyones interested.

[Guest slapnuts]

For those concerned about being able to load applications to SD card, I suggest using Link2SD from the android market. I have a ZTE V9 (Optus Mytab), which I rooted and then installed Link2SD. After following the very clear install instructions I now am able to load all 'non-system' applications to the SD card and after updating the app database updates for apps works fine. I await the 2.2 upgrade of Android with great interest. Also interested in custom ROM for this device. Haven't felt confident installing a ZTE Blade ROM in case of compatibility issues.

Well that's a good thing, as the blade roms won't work.

[Guest Biti]

Please somebody explain me how rooting works? I added root access in kitchen to the ROM and it's say rooted, but root not works there is no superuser request when run a root access required app

Add su to xbin fix this problem?

Edited March 18, 2011 by Biti

[Guest Stephen J. Knill]

No that's fine, I was experimenting with the Russian TPT and overwrite the standard android splash with....something horrible in russian (I think).....

Thanks

lolz, done that a few times now... which part of the "boot splash" have you nerfed... the actual initial android icon (which is the logo file in the ramdisk section and just displays the green android before passing onto the animation file) or the bootanimation (from system folder which displays the Optus logo upon boot)? Either way I can easily help you out with that one... I have several variations now, including that weird Russian (or is it Hungarian?) one :D

Edited March 19, 2011 by Stephen J. Knill

[Guest Stephen J. Knill]

Please somebody explain me how rooting works? I added root access in kitchen to the ROM and it's say rooted, but root not works there is no superuser request when run a root access required app

Add su to xbin fix this problem?

"Rooting" a device simply means altering the permissions on the device to enable access to the su command.

You will only get the popup request when the SU is associated with the SuperUser app, otherwise permission will just be granted in the background (this will cause some apps to fail, as the "permission granted by" message will make the app think it was denied)

Also, root access with the v9 will only be temp if Secure mode is enabled. (which can be messy to disable)

Edited March 19, 2011 by Stephen J. Knill

[Guest Stephen J. Knill]

Found this on the XDA forums, and it seems like ZTE is gonna let everybody who wants a upgrade to 2.2 be able to get it :D

ZTE light v9 2.2 upgrade from ZTE is here

--------------------------------------------------------------------------------

Download from here

http://www.mediafire.com/?b6ty863olhb36t8

please follow the instructions carefully.

You need to email ZTE a screencapture of a page.

Dear Sir / Madam,

Thank you for contacting ZTE.

I'm sorry to tell you that the V9 series can completely support android2.2 on the hardware part.

But no android2.2 software is available for those released phones.

End-users are advised not to upgrade their phone versions until the software is released formally.

Always you can follow other pertinent information from our official website.

Should you require any further assistance, please do not hesitate to contact us!

Best Regards

Sincerely yours

Just sad... lol

[Guest jimmyjack72]

Does anyone know where the bootanimation is on the Optus Mytab version?

[Guest Biti]

Also, root access with the v9 will only be temp if Secure mode is enabled. (which can be messy to disable)

Please explain me how :D

default.prop

ro.secure=0

ro.allow.mock.location=0

ro.debugenable=1

persist.service.adb.enable=1

My boot.img is unsecured, I am cooked the ROM in kitchen.

So method like this: http://www.theandroidphone.com/guide-to-ro...vo-shift-99187/ is the same if I have rooted custom ROM right?

Fix me if I am wrong or explain me what I need to do too..

So I accept any help what assist me to resolve temp root problem.

Root apps say Phone rooted, only this superuser app not works and I can't access /data with rootexplorer, but I have full access to /system LOL.

About the splash screen, here I have a White backgrounded ZTE Logo, this is what I got when go tu DFU mode too.

After green android logo, than bootanimation.zip (actually I added my custom)

Edited March 19, 2011 by Biti

[Guest Stephen J. Knill]

Does anyone know where the bootanimation is on the Optus Mytab version?

/system/bin/bootanimation

[Guest Stephen J. Knill]

Drat!! I figgered out how to enable the "desktop" (mainly the lock screen actually) rotation on my Optus v9... but forgot to save the setting into my backup, now I've gone and lost it again... lol :s

Edit: Hmm, I just noticed Sebastian404 figgered this part out (maybe) seems his rom is allowing the lock screen rotation. Anyone know what setting he changed? -- I'll go start having a looksie tho anyways :D

Edited March 19, 2011 by Stephen J. Knill

[Guest Stephen J. Knill]

Please explain me how :D

default.prop

ro.secure=0

ro.allow.mock.location=0

ro.debugenable=1

persist.service.adb.enable=1

My boot.img is unsecured, I am cooked the ROM in kitchen.

So method like this: http://www.theandroidphone.com/guide-to-ro...vo-shift-99187/ is the same if I have rooted custom ROM right?

Fix me if I am wrong or explain me what I need to do too..

So I accept any help what assist me to resolve temp root problem.

Root apps say Phone rooted, only this superuser app not works and I can't access /data with rootexplorer, but I have full access to /system LOL.

About the splash screen, here I have a White backgrounded ZTE Logo, this is what I got when go tu DFU mode too.

After green android logo, than bootanimation.zip (actually I added my custom)

You've already done the most critical part and set the ro.secure=0 setting (which is also the messiest part)

Once you have the secure setting disabled, you should be able to download and install UniversalAndroot-1.6.2-beta5 (I found earlier versions didn't work quite as well as this one does)...

for the most part you should be able to just run this app (I'd remove any existing versions of the Superuser app before running, just to be safe), do not alter the settings in UniversalAndroot... just run as is.

This app will take care of the exploit and permission changes needed to link the Superuser app to requests for root (otherwise apps will just be granted access, which will cause some to fail).

Open a terminal window and run the sync command (or just run via "adb shell sync", either works fine).

P.S. The method between devices (and brands) is slightly different, there is a huge difference between the HTC Desire and the ZTE v9 (and the key part is... it's easier to root the v9 once secure is off)

Edited March 19, 2011 by Stephen J. Knill

[Guest Biti]

You've already done the most critical part and set the ro.secure=0 setting (which is also the messiest part)

Once you have the secure setting disabled, you should be able to download and install UniversalAndroot-1.6.2-beta5 (I found earlier versions didn't work quite as well as this one does)...

for the most part you should be able to just run this app (I'd remove any existing versions of the Superuser app before running, just to be safe), do not alter the settings in UniversalAndroot... just run as is.

This app will take care of the exploit and permission changes needed to link the Superuser app to requests for root (otherwise apps will just be granted access, which will cause some to fail).

Open a terminal window and run the sync command (or just run via "adb shell sync", either works fine).

P.S. The method between devices (and brands) is slightly different, there is a huge difference between the HTC Desire and the ZTE v9 (and the key part is... it's easier to root the v9 once secure is off)

I tried Universal Androot, says Failed Fu goo or something like that, now I try to manuall install su binaries from recovery maybe this fix the problem.

Update# Not fixed superuser app say Su binary v original

Installed this package, su-2.3.6.1-ef-signed.zip

My V9 override this or look for su in a different place I dunno.

My system/bin/su is r-sr-x--- and created when I cooked the rom, after isntall package from recover what replace this file lol :S

After reboot phone restore the original su in /system/bin and what I emoved from xbin why?

OK all fixed now except the su permissions in /system/bin, after reboot its go back to the original, any idea?

Edited March 19, 2011 by Biti

[Guest Stephen J. Knill]

I tried Universal Androot, says Failed Fu goo or something like that

Oh, my bad... I just realized you have the new v9 running 2.2. From what I can tell there are some minor differences which prevent the UniversalAndroot application from working on the new v9's with 2.2, sadly I'm not entirely sure what they are yet. (prolly something simple like relocated files or some junk like that, but without access to one... it's a bit hard to test out)

I'll let you know if I find any solution to perm root the v9 with 2.2

Until then, you'r in uncharted waters my friend... and all I can do is wish you the best!

[Guest Stephen J. Knill]

Biti, not sure if this will help or not... but you should be able to figger out how to manually apply these "patches"

Preparing Exploit ... :true

Preparing busybox binary ... :true

User selected: Eclair

Preparing Su binary ... :true

Preparing Superuser apk ... :true, resid:2131034118

Preparing root toolkit script ... :true

Trying to get mount point:/data

/dev/block/mtdblock6 /data yaffs2 rw,nosuid,nodev 0 0

Trying to get mount point:/system

/dev/block/mtdblock5 /system yaffs2 rw 0 0

mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system

mkdir /system/xbin

cat su > /system/xbin/su

chmod 04755 /system/xbin/su

ln -s /system/xbin/su /system/bin/su


mount -o remount,ro -t yaffs2 /dev/block/mtdblock5 /system

mount -o remount,rw,nosuid,nodev -t yaffs2 /dev/block/mtdblock6 /data


mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system

rm /system/bin/su

rm /system/xbin/su


Preparing to execute exploit, do chmod

Executing exploit..

cmd: /data/data/com.corner23.android.universalandroot/files/getroot /dev/block/mtdblock6 yaffs2

[*] Android local root exploid (C) The Android Exploid Crew

[*] Modified by shakalaca for various devices

[+] Using basedir=/sqlite_stmt_journals, path=/data/data/com.corner23.android.universalandroot/files/getroot

[+] opening NETLINK_KOBJECT_UEVENT socket

[+] sending add message ...

[*] Try to invoke hotplug now, clicking at the wireless

[*] settings, plugin USB key etc.

[*] You succeeded if you find /system/bin/rootshell.

[*] GUI might hang/restart meanwhile so be patient.

Wifi enabled ...

mkdir failed for /system/xbin, File exists

link failed File exists

rm failed for /data/local/tmp/rootshell, No such file or directory

Exploit delete success

Install/Uninstall rootkit: true

ls -l /sqlite_stmt_journals

-rws--x--x root	 root		16224 2011-03-20 01:46 rootshell

ls -l /data/local/tmp

opendir failed, Permission denied

ls -l /app-cache

/app-cache: No such file or directory

run mount

rootfs / rootfs rw 0 0

tmpfs /dev tmpfs rw,mode=755 0 0

devpts /dev/pts devpts rw,mode=600 0 0

proc /proc proc rw 0 0

sysfs /sys sysfs rw 0 0

/dev/block/mtdblock5 /system yaffs2 ro 0 0

/dev/block/mtdblock6 /data yaffs2 rw,nosuid,nodev 0 0

/dev/block/mtdblock8 /persist yaffs2 rw,nosuid,nodev 0 0

tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0

/dev/block/mtdblock4 /cache yaffs2 rw,nosuid,nodev 0 0

/dev/block//vold/179:2 /data/sdext2 ext2 rw,errors=continue 0 0

/dev/block//vold/179:1 /sdcard vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_uti

e=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8 0 0

run df

Error running exec(). Commands: [df] Working Directory: null Environment: null

java.lang.ProcessManager.exec(ProcessManager.java:196)

java.lang.Runtime.exec(Runtime.java:225)

java.lang.Runtime.exec(Runtime.java:313)

java.lang.Runtime.exec(Runtime.java:246)

com.corner23.android.universalandroot.utils.Utils.genSysDebugInfoReport(Utils.java:181)

com.corner23.android.universalandroot.asynctask.RootTask.onPostExecute(RootTask.java:398)

com.corner23.android.universalandroot.asynctask.RootTask.onPostExecute(RootTask.java:1)

android.os.AsyncTask.finish(AsyncTask.java:443)

android.os.AsyncTask.access$300(AsyncTask.java:134)

android.os.AsyncTask$InternalHandler.handleMessage(AsyncTask.java:455)

android.os.Handler.dispatchMessage(Handler.java:99)

android.os.Looper.loop(Looper.java:214)

android.app.ActivityThread.main(ActivityThread.java:4415)

java.lang.reflect.Method.invokeNative(Native Method)

java.lang.reflect.Method.invoke(Method.java:521)

com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:868)

com.android.internal.os.ZygoteInit.main(ZygoteInit.java:626)

dalvik.system.NativeStart.main(Native Method)

The su file being used with root is the one from busybox, might try installing that and re-installing Superuser app... just a thought. (But this should head you in the right direction atleast)

[Guest Biti]

Biti, not sure if this will help or not... but you should be able to figger out how to manually apply these "patches"

The su file being used with root is the one from busybox, might try installing that and re-installing Superuser app... just a thought. (But this should head you in the right direction atleast)

I ROOTed the ROM now manually pushed superuser.apk and last su binary with adb, all works, after reboot /system/bin/su permissions goes back to the old s***, only this part is not clear for me, wh revert permissions and how can I solve this.

My first idea for solution is add this "chmod 4755 /system/bin/su" to init.rc ?!

hehe on inir.rc this s*** revert the permissions, I found it xD

Edited March 19, 2011 by Biti

[Guest Stephen J. Knill]

... I found it xD

That's what I like to hear :D -- I didn't even think of the init.rc for some damn reason, which is embarrassing cause I should of. But all is well that ends well. :( (UniversalAndroot will correct those settings, that is when it runs... it also sets /data and /system to be mounted rw instead of ro which is also set in the init.rc file... so why the hell did I not think of this lol)

Edited March 19, 2011 by Stephen J. Knill

[Guest Biti]

That's what I like to hear :D -- I didn't even think of the init.rc for some damn reason, which is embarrassing cause I should of. But all is well that ends well. :( (UniversalAndroot will correct those settings, that is when it runs... it also sets /data and /system to be mounted rw instead of ro which is also set in the init.rc file... so why the hell did I not think of this lol)

I changed the permissions in init.rc, pushed the file to the phone, sync than reboot and got the same file than before, any idea? :S Really anoying, now I tryed to add this line to other rc files, got the same, any idea to execute a line on boot without this files?

Edited March 19, 2011 by Biti