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....
...but you forgot the link
ZTE V9 (Light) updates
- Thread starter Jefox
- Start date
...but you forgot the link
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....
You don't need your tab unlocked for the upgrade.
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!
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!
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
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
That left me with the word "FAIL"and something that looked like restoring ov .NV failed at 98%. Any advice?
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
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
sent from the underdog
Head over to madaco and there is cm7 which will unbrick your tab if you still have ftm mode
Sent from my V9 using Tapatalk
Sent from my V9 using Tapatalk
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?
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?
Last edited:
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
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
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
2Here is my Froyo dump TELENOR_V9V1.0.0B01
md5 checksum: c68099e15534149373b3fc5517435b21
Firmware version: 2.2
Baseband Version:V9B01
Kernel version:2.6.32.9 zte-kernel@Zdroid-SMT
Build number: TELENOR_V9V1.0.0B01
Recovery: recovery-clockwork-3.0.1.4-light thx to Sebastian404
root only temp with z4root
Tested all v9 and light clockworkmod recovery images
Tested All Universal Androot and all z4root (only temporary root works with z4root)
Androot 1.6.2 beta 5 force closing
ROM created from my 2.2 rooted and all extras added
Need ClockWorkMOD Recovery 3+
http://www.mediafire.com/?uk55o60h3kpxwgg
DAMAGE OLD DEVICES, USE FOR BUILDING FROYO TO YOUR DEVICE, DO NOT INSTALL IT IF YOU CAN'T GET ADB OR RECOVERY WHEN BOOTLOOP!2Ho
How did u flash it
?
Did you need the licence number?
BTW this tablet is now selling for $150aud in Australia while the galaxy tab is 300
read this thread
http://android.modaco.com/content/other/337130/zte-v9-light-2-2-update-now-available/#entry1669546
post 9, download the patch
but be carefull. if you brick it, it's on you.2I ppl!
After all that happened, i left the device in he tech support and here´s the fresh result after a reflashing done by them.
(when i sent the device only ftm worked)
boot.img (147.72 MB) http://www.multiupload.com/K2SQNIBBDT
ftm.img (106.01 MB) http://www.multiupload.com/PKK972V2IN
recovery.img (147.72 MB) http://www.multiupload.com/56MTQSZOB8
system.img (147.72 MB) http://www.multiupload.com/Q3CKW0I1I5
the images were generated via mkyaffs2image
This is the VODAFONE-PT version 2.1-upgrade12Can confirm LinksSD 1.0.4 is working on Optus MyTab.
One thing i noticed is that titanium*backup does not like restoring to this type of system. I also noticed that it leaves the dalvik-cache on the /data/ partition on the internal memory. Not that there is an issue with that last part, but dalvik-cache will continue to grow as well, all be it not as fast as adding apps will eat up available space...
Other thing i noticed was that when you uninstalled the Link2SD app, it did not appear to reverse any changes that it made. Not that that is an issue, as it appears to be a handy tool that i dont think anyone would be uninstalling any time soon
For anyone still interested, i have updated my app2sd script. From the feedback i was getting, been trying to cure some of the bugs. It's a little bit harder to install than Link2SD but you dont have to reboot every time an app is moved to the SDcard. Also shows up in Titanium*backup as an app2sd partition so you can keep an eye on how much space you have left...
Any issues, let me know. And dont forget... RTFM1We 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.
