yashsingh1/xdaforums huggingface dataset:
[Android Software Development] chocolat2:
I don't like this version of android 2.2 for this tablet. the touch screen is worse. It has less sensitivity to touch. For me the difference is quite large. The version 2.2 is worse in this regard. Scroll is a pain. Worse than before. It goes crazy or does not move.

How can I return to the original version ? How to return to the official zte android 2.1.?
[Android Software Development] julz:
crap - need some help. Tried to flash the old Optus 2.1 ROM (via recovery) back onto my Optus MyTab V9 after having 2.2 installed. Now it won't boot and is stuck on the ZTE logo screen. Can't seem to boot into FTM or Recovery either :(

Any ideas?
[Android Software Development] 02xda1:
Sorry I didn't get back to you sooner before you tried it, if you read back a couple of pages and back at modaco it had something to do with the new partitioning for 2.2 which is why we needed the special zte tool to flash 2.2 in the first place. Try re flashing it with the zte upgrade tool again. Or pm Sebastian at modaco, as this is above my skill level.
[Android Software Development] radmir:
Returning to 2.1 is not safe and it's possible with only using the flasher.
[Android Software Development] chocolat2:
why is not safe? where can I get the flasher?

please anybody knows how to return to the stock rom?
[Android Software Development] JakDac:
Froyo 2.2 for ZTE V and Telstra T-Touch when ? where ?

Froyo 2.2 for ZTE V and Telstra T-Touch when ? where ?
[Android Software Development] jimmyjack72:
The custom 2.2 runs like a dream on my optus mytab. I reckon it makes it an even better tab than it was already.

I dont want the official optus branded one, as it will be bloated and locked up.
[Android Software Development] 02xda1:
No telstra t-touch. Fail.
[Android Software Development] 02xda1:
+1. It is a rather large improvement
[Android Software Development] tuomi:
I just picked up this device as one of our carriers in Sweden dropped the price from approx 400 usd to 150 usd($).

Would love to see the modding scene around this unit spring to life, allthough from looking at the specs i dont think it is all too different from a hero / legend specwise. Meaning a cm6-port wouldn't be too far fetched?

Is anyone sitting on the info how and if it is possible to root and flash the european/scandinavian version?
[Android Software Development] gosa:
There's a bit more activity with regards to the ZTE Light/ZTE V9 over at modaco:

http://android.modaco.com/category/445/other/

Both with updates to 2.2 and other useful info...

(and don't forget to give feedback in the Swedroid forums if you manage to get 2.2 up and running...)

I'll start tinkering with mine as soon as it arrives from Sweden...

Lycka till!
[Android Software Development] daml:
You cant. I'm not sure on the details but you need a jtag box to return to 2.1.

Can i ask why you want to go back?
[Android Software Development] alpha4test:
2.2 up and runnning

Just follow this instructions:

(fon forgrt to thank sebastian!)

http://androidpt.com/index.php?option=com_kunena&func=view&catid=135&id=110704&Itemid=30

It's in pt but had the time to translate yet, so use gtranslator

any device seem to be upgradable, just do it carefully and keep a backup at all time.

The rom been used seems to be fruit from a leak from ZTE our a partner...

And yes it as all the languages!
[Android Software Development] 02xda1:
Thanks, but your about 2 weeks behind the ball.

Will you be doing your own custom rom for this one too?
[Android Software Development] alpha4test:
been working around the clock... so time's been shorth as helll, but yes give some days
[Android Software Development] alpha4test:
I ppl,

Any has the same problem?

Can´t boot Sebastian404 recoverymod using the hardware buttons!
[Android Software Development] alpha4test:
alphaxsMOD2.2.0.1

Summary

alphaxsMOD2.2.0.1

Based on V9_GENERICV1.0.0B03

"Clean" Rom + Rooted

With : recovery-clockwork-3.0.2.8-v9-gen2 by Sebastian404

Hardware butons dont'seem to start recovery so use quick boot...for now

alphaxsMOD2.2.1 will be realeasad next, with new boot logo and with the basic apps loaded, and other improvements.

It will be installed via recovery.

This one is installed via FTM flasher - Multisales.

And is a room to use to upgrade from 2.1 to 2.2., or some emergency.

How to Install:

(this part used gtranslate(its 02:00 got to go to slepp)

from: http://androidpt.com/index.php?option=com_kunena&func=view&catid=135&id=164280&Itemid=30

Good Start for general tutorial to upgrade to 2.2

NOTE: Due to some errors advise drivers who have a machine with XP to use for this process, who do not have it you can create a virtual machine with virtual box (always the way trust me)

1 - Download from:

Sales_MultiDL_MSM7227

Sales_MultiDL_MSM7227_patched

alphaxsMOD2.2.0.1

2) Unzip everything to a directory

3 - Install the program Sales_MultiDL_MSM7227_V1.00.01

4 - Copy the file to the folder Sales_MultiDL_MSM7227_patched.exe program installation

5 - Run the program Sales_MultiDL_MSM7227_V1.00.01 and indicate the path to the directory where the room was extracted alphaxsMOD2.2.0.1

6 - With ZTE off removing the battery and wait 10 seconds, can touch the contacts of ZTE to accelerate discharge wastewater, and then reconnect the battery.

7 - Press (and hold) VOL (-) & VOL (+) and then also press the power button button, (you'll see the light flashes one time).

8 - Now turn on the ZTE with the USB cable to the PC;

9 - Go to My Computer, selecting with the right mouse button and choose to manage;

10 - Select the Device Manager and go to the door and see the number that appears;

11 - Go Sales_MultiDL_MSM7227_V1.00.01 window and select an ADC that port;

12 In low-in 'Information File' clicks SW Directory and browse to the folder 'alphaxsMOD2.2.0.1'

13 - Select 'Backup NV' and then 'Start All'

14 - Will you stay with a new file in the program folder called 'Channel1.nvm' (make a copy for safety) (if error, does everything till the end if you finish with FTM screen returns to repeat the process, the second time ja will create the file correctly (may be the first time at 0 kb)

15 - Now in Action Mode select 'Download' and then 'Start All'

16 - Began ensures that not even turn off the PC or the tablet!

17 - If everything went well you have the 2.2 if you stay locked up on the screen MTF (if the file has 0 kb Channel1.nvm can happen, then repeats the process going and this time the backup already generates a file of any size. If FTM der again takes the battery and repeat the process that I explained before, then waits for the first boot takes more time. You can also try to link carrying power & vol +
[Android Software Development] Destroyer-XDA:
Which version?
[Android Software Development] alpha4test:
IMEI change ZTE V9

Just checked myne and the imei changed to, so it must be the NV step!!!!

In my case it didn't want to do it so i was forced to skip it...

the second time it did created a NV file with no problem... but i figured now that it was it the wrong imei this time...

So try to make the NV backup

my imei now ends with: 642710 and yours any change?
[Android Software Development] daml:
alpha4test, come create a thread for this in my v9 forums. cheers!
[Android Software Development] alpha4test:
sorry bu just do'n have the time already herem in modaco and androidpt betwem getting spare time to cook, write and translate, anwser ppl pm questions, post in the foruns and all the rest... just can get in another site to try update the info...
[Android Software Development] alpha4test:
Downloads

alphaxs MODLink3SD2.2

alphaxs MODApp2SD2.1

alphaxs MOD2.2.1
[Android Software Development] hdfanatic:
Here is a link for the official Froyo 2.2 upgrade for unlocked devices ZTE v9

It is an OPTUS branded rom but is 2.2.... :)
[Android Software Development] LayZeeDK:
...but you forgot the link :D
[Android Software Development] mallaccra:
i got the official froyo but flash still doesn't work. is it because of the hardware limitations or something else...
[Android Software Development] 02xda1:
hardware, simply not up to it.
[Android Software Development] xd4d3v:
Anyone has the Optus stock ROM?

Thanks
[Android Software Development] 02xda1:
Grab it from the zte official site/forum. Or there's a copy at modaco I think
[Android Software Development] fromaron:
You don't need your tab unlocked for the upgrade.
[Android Software Development] Corran:
I must say this is a fun little machine; with CM7 it really is just fine. I too bought it for scraps and I'm really a happy camper :)
[Android Software Development] alpha4test:
Gingerbread anyone!? CyaogenMOD 7 ( android V-2.3.4)

Guess what!!!

A Gingerbread anyone!? That's it version 2.3.4

CyaogenMOd ported to ZTE V9 (no flash... but with no overcloking...no can do....)

Thank's to all that used their time into developing what we have today!

In this case to kallt_kaffe in www.swedroid.se!!!

For those with a gen2 device/rom such as alphaxs 2.2 just use sebastian404 recovery and have fun! here's the last build

Before booting here's google apps for this set, and don't forget to do a full wipe.

hope to get time to put it all together and improve the sreen issues

carry on!
[Android Software Development] alpha4test:
Sorry for not awsering the PM's

I apologize to you all that i didn't managed to anwser im PM, but i only saw today som meassages from january... time's been short, so please jsut post here, so me or anyonelse can help asap.

for you all i belive and hope that by this time most oof the issues have been solved, once again sorry.

thank's
[Android Software Development] J.K Nilsson:
That left me with the word "FAIL"and something that looked like restoring ov .NV failed at 98%. Any advice?

J.K Nilsson
[Android Software Development] xd4d3v:
yes, you need to be in FTM mode to do the NV backup or restore.
[Android Software Development] J.K Nilsson:
Shouldn't the installer handle it on its own? The unit starts to bootloop, I can see that an android device shows up in the hard ware list. I can stop it by taking out the battery and restart the device and pressing volume up and down simultaneously. The V9 now enters download mode.

I thought that I now should be entering CVM recovery or another recovery to be able to flash a rom and then flash stoch FTM recovery mode back. But no luck.

J.K Nilsson
[Android Software Development] richarddwyer10:
I have bricked my tab while upgrading to 2.2 with the optus tool.it's stuck in a bootloop so I flashed again but its the same.I have upgraded these tabs before with no problems. Any ideas to get it working again would be great, otherwise back to the shop she goes

sent from the underdog
[Android Software Development] richarddwyer10:
Solved
[Android Software Development] cocomunga:
But not shared?
[Android Software Development] rinkle:
Could you explain how you solved it as i got mine bricked aswell?
[Android Software Development] richarddwyer10:
Head over to madaco and there is cm7 which will unbrick your tab if you still have ftm mode
[Android Software Development] Corran:
As of today the CM7 port by kallt_kaffe is merged into the official! He's really done a great job getting it supported.
[Android Software Development] Dr_Wolodya:
I have TIM MyTab:

Homepage: http://www.tim.it/consumer/o127828/prodotto.do

On sticker: ONDA, Model: TT101, NMU: 720850.

It is very similar to ZTE V9 (Light).

Android - 2.2.

Firmware version: TT101.TIM.FW.B02.

Here is full dump (boot, recovery, system, config and checksum) dumped by romdump:

http://depositfiles.com/files/8vlttxck4

How to determinate - can I flash Clockwork Recovery and CyanogenMod7 to it?
[Android Software Development] dipidabelyah:
excuse me..

does anybody know how to fix bootlooping ZTE V9, could you please teach me how to fix it? and if i want to flash a new stock rom, could you teach me how to flash it to ZTE V9? please help
[Android Software Development] vincentshjuan:
Officially supported by Cyanogen Mod 7

To all v9 users,

We are officially now supported by Cyanogen Mod 7 now, go here :

http://www.cyanogenmod.com/blog/cyanogenmod-7-1-released

Beats depending on the original manufacturer!!

---------- Post added at 08:53 AM ---------- Previous post was at 08:51 AM ----------

In XDA, v9 threads are non active, suggest to head over to http://android.modaco.com/forum/534-zte-light-v9-lightv9modacocom/, it's must more active for our devices over there and you should find what you need.

For your issue, there is an unbrick thread in Modaco, maybe that might help you, otherwise reflash, and if you can still get into Clock Work, you will need some terminal emulation apps to let you mount and copy the ROM in Modaco to your SD before flashing. Look for the installation with memory partitioning thread, all new v9 users uses that to start....

Hope this helps.....
[Android Software Development] alpha4test:
Flash Player for Arm7

Flash Player for Arm7 tested and working (except with opera)

FlashPlayer-10.2.apk (4.41 MB)	http://www.multiupload.com/XFT7DVWURY
[Android Software Development] mccm:
please link me to the zte optus v9 drivers ,thank you

your help will be much appreciated
[Android Software Development] Dr_Wolodya:
Here is I upload drivers for ZTE V9 (Beeline M2, Tim MyTab, Optus MyTab):

http://www.multiupload.com/0DUL6IHPLU

;)
[Android Software Development] Fgroia:
i need vodafone portugal 2.2 stock rom, can someone help?
[Android Software Development] naifaharsy:
want jellybean in ur V9??:D

Sent from My Naifah
[Android Software Development] mcnascimento:
Where can we get it?
[Android Software Development] naifaharsy:
see in my other post...
[Android Software Development] Funkmonkey:
Custom ROM?

So having trouble finding any answers, are there any custom roms for the V9 that arent that Cyanogenmod crap?
[Android Software Development] Dr_Wolodya:
Here is: http://get.cm/?device=v9
[Android Software Development] spaces27:
V9 light Root

Hello guys.. I'm really having a hard time rooting this tablet. I think because the tablet i have is already version 2.3.5 and most of the software i found were for 2.2. I hope that someone had successfully found a way to root this tablet in this version.. thank you.. !!
[Android Software Development] alpha4test:
Multiupload failed and i don't find a copy of these mod's

alphaxsMOD 2.1 ZTE V9 App2sd Full 1.2

alphaxsMOD 2.1 ZTE V9 Link2sd Full 1.2

alphaxsMOD2.2.0.1

Can anyone post a link?

!???
[Android Software Development] naifaharsy:
anybody can i get CM rom for ZTE V9+?thanks..
[Android Software Development] julz:
Ive got the v9 but running out of internal memory. its supposed to have 512 mb rom but only about 165 mb is available for apps. Currently using root explorer to move apps into internal memory. Would be great if apps2sd was available for the v9
[Android Software Development] bbfin:
I have rooted my V9 too, but i don't have any idea how to move apps to sd cause this feature is supported only in android 2.2. It there easy way to do that in rooted v9?
[Android Software Development] cocomunga:
How do you move the apps using root explorer?

Cheers
[Android Software Development] julz:
you need to first get root access and then install root explorer.

Then you can use root explorer to move apps from 'user memory' (still internal memory) to 'system memory' (again this is still internal memory but there is additional space reserved for system memory which you can only access using root explorer).

To do this you will need to move app files from /data/app to /system/app. I generally only moved apps that I believed weren't going to be updated regularly as the Android Market is unable to update apps that you have moved into /system/app because it is protected. To do the updates you will need to use root explorer to move the app back from /system/app to /data/app. Whilst in root explorer you can also delete any unwanted bloatware (e.g. optus apps) from the /system/app directory.
[Android Software Development] mks$>:
kernel source

Well on ZTE's support page:

support.zte.com.cn/support/index.aspx

there is a link to the kernel source, though that page only says:

"ZTE V9 Tablet series-Eclair kernel(2.6.29) source code

Building"

Hopefully that means they are still in the process of sorting out the upload and will be ready soon.

It would be great to do some dev on it, prehaps fising some of the more obvious bugs like wifi not reconnecting after sleep or incorrect 3gt signal indicator...
[Android Software Development] rjm2k:
lol good luck! That "Building" message has been up for a while, I've told them about it too. We have been waiting for working source for the Blade (which has the same kernel and chipset as the V9 so you could start using that probably with some missing support) for months, their source control is a little on the wild side and they are pushing out so many devices/releases all of the time that they simply can't keep the released kernel upto date or even in a state where it can compile in some instances.

If you manage to fix the wifi re-connect issue post here, it's a problem found on the Blade and also many other non-ZTE phones, probably due to the wifi driver or the chipset firmware, we keep trying the drivers from each new release and there are perceived improvements sometimes but it's not clear if they are real or not. In the meantime if someone wants to dump their V9 Rom ( http://android.podtwo.com/romdump/ ) it might be possible to see just how close it is to the Blade, you should keep your eye on Blade developments as they may be of use to you (we already have froyo and a gingerbread build is in progress) . check out the boards on here or modaco.com which has a bigger blade userbase.

posting /proc/config.gz and the contents of /proc/mtd and the results of mount would be useful too.

Note that clockwork recovery is available for the blade so if the partitions are the same you may be able to use that but BEFORE YOU INSTALL CLOCKWORK make sure that you backup your default recovery as in rompdump link above. Clockwork allows you to use Rom Manager too.
[Android Software Development] Rainard:
depositfiles.com/files/xc8kfv6g6 - romdump

depositfiles.com/files/vwgf6yxhu - config.gz
[Android Software Development] rjm2k:
thanks, i can't download config.gz though it just loops when attempting, could you re-post or maybe attach to a post on here?
[Android Software Development] serialmonkey:
I've attached the config from my device (Optus Mytab - rebadged ZTE light)
[Android Software Development] serialmonkey:
And there is the /proc/mtd and mount output

# cat mtd

dev: size erasesize name

mtd0: 00500000 00020000 "recovery"

mtd1: 00500000 00020000 "boot"

mtd2: 00180000 00020000 "splash"

mtd3: 00080000 00020000 "misc"

mtd4: 02800000 00020000 "cache"

mtd5: 0ef00000 00020000 "system"

mtd6: 0a280000 00020000 "userdata"

mtd7: 00200000 00020000 "oem"

mtd8: 00180000 00020000 "persist"

# 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 rw 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:1 /sdcard vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8 0 0

I'm having trouble getting romdump to behave on my device though. After the output below my /sdcard/romdump doesn't have much in it at all.

# ./romdump

Android ROM dumper v0.72b

(c)2010 Sebastian404

Device : V9 Prepaid-T02

cat: can't open 'Prepaid-T02/system.info': No such file or directory

sort: Prepaid-T02/system.info: No such file or directory

sed: Prepaid-T02/system.info: No such file or directory

gzip: can't open '/sdcard/romdump/V9.gz': File exists

gzip: Prepaid-T02/system.info: No such file or directory

Creating required files... done.

Opening mtd table... done.

Prepaid-T02/config.gz: No such file or directory

Dumping kernel config... done.

Dumping boot partition... done.

Dumping recovery partition... done.

Dumping system partition... done.

find: Prepaid-T02: No such file or directory

awk: Prepaid-T02/checksum.md5: No such file or directory

Creating Checksums... done.

Cleaning up... done.

All done.
[Android Software Development] Rainard:
contents of my config.gz from unbranded ZTE Light.

please tell me if I can provide any further assistance
[Android Software Development] serialmonkey:
Solved. The device ID in build.prop had a space in it which isn't romdump friendly. I remounted /system as rw and removed the space. I have a romdump available from an Optus device if anyone wants it.

Next problem is I can't seem to get into recovery mode. With the ZDE blade you hold the minus button during power on to get to FTM mode, and the plus button (after taking the battery out) to get into recovery mode where you can use fastboot. For me, holding the plus button does nothing - the device just boots as normal.

Can someone try on a non-Optus V9 ?
[Android Software Development] bbfin:
Hi!

I can boot to FTM-mode by pressing POWER and - on boot. Still with unbranded V9 i couldn't boot to recovery by pressing POWER and +.
[Android Software Development] serialmonkey:
Glad to see it's not just me :-) Anyone have any ideas how to get this device into recovery mode ?
[Android Software Development] rjm2k:
We can only get into recovery by pressing vol - on the blade because we hijacked FTM mode. FTM mode uses the same parition as recovery but disabled lots of stuff, so when our custom clockwork recovery starts up it checks to see if it's in FTM mode and then does a reboot recovery to get into proper recovery mode where everything is enabled. You really need to get a modification of clockwork going for your device, this may be as esy as starting with the Blade recovery, unpacking, replace the kernel with yours and re-pack. Then flash either using fastboot or if you can SU then from terminal run flash_image recovery /sdcard/cwrecovery.img.

For now, if you just want to see what the stock recovery is like, SU in terminal then do reboot recovery.

On the blade vs the V9 front, it seems they are similar but also different, the board is different so it's unlikely that the same kernel binary will work on both. However, with the skills it may be possible to use your kernel on the 2.2 we have for the blade.
[Android Software Development] serialmonkey:
Thanks for the guidance rjm2k. I'm a droid newbie but I have kernel dev experience so I'm happy to give this a shot.

Can I do this using the recovery.img I got from romdump as an initial test ? I'm looking for ways to revert back to a working device when I break it :-)

I can get into recovery via this method, and by using 'adb reboot recovery'. The recovery mode I get though is just the exclamation mark+droid logo and no text. Is that what you see on the Blade ? The device doesn't appear via USB in this mode - so I can't see me being able to use fastboot ?
[Android Software Development] rjm2k:
Yes you can revert to the stock recovery you backed up, from an end users point of view the stock recovery is useless but it's a good idea to keep a backup in case you need to return the device. On the blade the recovery doesn't recognise any of the keys and is also upside down (they put the screen in upside down!), it's totally useless. If you modify the blades clockwork you may need to double check things like mounts just in case they are different.
[Android Software Development] serialmonkey:
The mounts do look slightly different - there is an additional oem partition and the locations are slightly off.

I'll recompile my kernel overnight for yaffs2 support and see if I can extract/update the image based on the Blade's latest ClockWork from Sebastian404. unyaffs2 isn't working for me at the moment.