yashsingh1/xdaforums huggingface dataset:
[Android Software Development] alpha4test:
Hi ppl!

Done so far:

I also rebooted in recovery mode, and the result was the same, just the exclamation mark+droid logo and no text or soft button of any kind.

In the case, i used Quick Boot (Reboot), to get to recovery mode since i tried "the hard way" but no results..

Here´s the download link from appbrain

appbrain.com/app/quick-boot-%28reboot%29/com.siriusapplications.quickboot

I'm from Portugal and i got a ZTE V9 from Vodafone.

LCD Density changer Worked ok also, i'm using the 120 or 140 setting (stiil didn´t make a permanent change, so if i reboot is necessary to redifine the resolution, but since i got it 3 days ago its best this way for now).

LCD Density For Root: appbrain.com/app/lcddensity-for-root/lv.n3o.lcddensity

For root i used the Universal Androot, tha in the latest version of the app, when it opens gives the option to select a version to dowload so its always uo to date.

wiki.cyanogenmod.com/index.php?title=Universal_Androot

Thing's to come...

Waitting to a 2.2 room (i still trying to learn how to cook!);

I trying to get app2sd to work on this room (ZTE/V9_VPT; version:20101104.100345; release: 2.1update1 - kernel 2.6.29 -4.4.0 GCC);

Also trying to find a way to get ahdoc network to work, the goal is to get my Boston (z71) to share is internet connection using barnacle wifi teather.

(sorry could't post the link's in the rigth way since i don't have clearance yet...

Carry On!

alphaxs
[Android Software Development] serialmonkey:
I'm speaking with Sebastian404 at the moment who is looking into building a copy of Clockwork for us since he built the version that works on the ZTE Blade. I had an attempt last night just taking the recovery image for the Blade, replacing the kernel and updating a few obvious things but no joy. Mind you - that was a 5 minute attempt and I'm pretty clueless. If we can get the Clockwork recovery image working then we can take a look at building off the 2.2 image used on the Blade.
[Android Software Development] tinkai2:
app2sd with stock 2.1

Hi

If anyone is interested, I managed to get app2sd to work with the ZTE stock 2.1 s/w. Slight change to a procedure for Samsung.

androidforums.com/tablets-mids/244613-zte-smartpad-light-v9-7-tablet-android-2-1-a.html

Waiting for 2.2 to see what further improvement Android brings. Android really rocks!!

Cheers.
[Android Software Development] alpha4test:
Free network unlocking code genarator!!!

Hi just unlocked the device using selecting the "ZTE Blade Android" option!!!

nextgenserver.com/calculator/

(zero €)

alphaxs
[Android Software Development] julz:
hey mate what's with the backdoor su step you posted in the other forum? Is this necessary? I still have su permissions after reboot...

BTW for those who don't have the Android SDK installed - you can do all of the steps via a Terminal program on your ZTE V9 tablet. Just download a free Terminal app, run the terminal on your V9 and then type in 'su' <enter>. A superuser box may appear asking for superuser permissions so click to grant permissions. From there you can then type in the rest of the stuff directly on your device. Use an app like Root Explorer to create the 'install-recovery.sh' file in your /system/etc directory and then use Root Explorer to edit the file.

I had to do this because I couldn't get ADB talking to my device - not sure why as I had debug mode on? Maybe I'm missing drivers - can't remember as I used to use it when i had my HTC magic
[Android Software Development] julz:
AWESOME! This works! Tested successfully on my Australian Optus MyTab :)
[Android Software Development] amiazmel:
How to use the unlock code?

Hi,

alpha4test or julz, how to use the code given by the nextgenserver. what are we suppose to do. there is no guide for zte.
[Android Software Development] tinkai2:
Hi

ANDroot may not work after reboot. (e.g. your /data/app failed to mount) For safety, pls install another su in /system/bin ( I rename it su_new) Steps can be gathered from

Magic Root Access - Android Wiki

# Below show the su from ANDroot and su_new I installed

$ su_new

su_new

su: access granted, courtesy of Your Page Title

# cd /system/bin

cd /system/bin

# ls -l su*

ls -l su*

lrwxrwxrwx root root 2011-01-03 21:42 su -> /system/xbin/su

-rwsr-sr-x root root 76232 2011-01-03 21:34 su_new

-rwxr-xr-x root shell 5392 2010-12-15 01:55 surfaceflinger

Cheers.
[Android Software Development] alpha4test:
Hi amiazmel,

Just enter the IMEI of your device (you can find it on a stiker usually in the batery compartiment, in the box where it came, or by using a code on the dialpad, or by going to device information on android settings.

power on the ZTE V9 with any sim card from another operator and

then use the generated unlock code

And its done!
[Android Software Development] bbfin:
Any luck porting Blade's 2.2 to V9?
[Android Software Development] jimmyjack72:
Check out the thread zte-v9-tablet over at MoDaCo.

These guys are working on a recovery image for the V9.
[Android Software Development] serialmonkey:
We have a recovery image working (currently using a hacked in adbd, but it works).

It's a start :-)

Sebastian404 is being fantastic help !
[Android Software Development] amiazmel:
Thank you for your effort to bring froyo 2.2 to zte and also many thanks to sebastian404. I go through the forum on modaco. I am not a programmer or tech guy but I wish that one day my zte smartpad light will have froyo or maybe gingerbread. :)
[Android Software Development] xlrate:
Not building anymore. Available for download !!! :p
[Android Software Development] rjm2k:
yes and there is the froyo source for the blade, no defconfig for the v9 in there but they do share the same codebase so maybe worth migrating the .29 config to .32 to see if it works. If so then you may well be able to use the 03z romdump that we are using for the blade.
[Android Software Development] Mark Trainor:
Unlock Code

I've been able to get 3G with Telstra and Vodafone SIMs. With Vodafone in my area (North Perth) I get 950+ kb/s on the speed tests at DSL Reports. This is more than three times what I was getting with the original Optus SIM. I rooted with Universal Androot, am tethering with Barnacle via Wifi, and am using the vfprepaymbb APN.
[Android Software Development] julz:
screw paying $15 - check out the other free link posted previously. Tested and proven to work perfectly on my Optus MyTab
[Android Software Development] Jucastan:
I got one too but it seen 2.1 android is not good enough.we should kick these Chinese bu!t to make them upgrade to2.2
[Android Software Development] camo.b:
Following closlely.....
[Android Software Development] manuellima:
Hi, somebody knows how install flash player on zte v9? I ask for this because my company site is 100% flash and I can't loggin.

Thank you all
[Android Software Development] pegaxs:
Cant be done at the moment. We are going to have to wait for a 2.2 update to come out or for someone to cook up a 2.2 ROM... Over on ModaCo there is some development on this already. Talk of using the 2.2 Froyo ROM update from the ZTE Blade...

I am also personally working on A2SD for the V9 that i have working... only problem is i cant get it to remount at boot time and it has to be done manually. Soon as this issue is worked out, i will post a tutorial to get it working... I know of a few others who have it working, but this seems to be an issue possibly related to the Optus version of the V9. :)
[Android Software Development] manuellima:
Thank you, for the quick answer. I guess it is better wait for a group version for v9.

Regards
[Android Software Development] woohoo70:
I really hope we can get 2.2 on this thing soon, the internal storage is driving me crazy hope its not to far away......
[Android Software Development] zidee:
yeah....rather disappointed with ZTE unresponsive and slow attitude. I'm desperate for 2.2 update too mainly for application storage on SD card. Even my old Palm Treo has this features for ages. Why Android is so slow?

For ZTE, if they behave like this it will take them a while for them to catch another Chinese giant like Huawei. They just don't know how to do branding. Look at how Samsung Galaxy Tab is?

If we put V9 and Galaxy Tab side by side we know V9 can match Tab at half of the price. But then, branding from Samsung is good so receive a lot of support from accessories producer for example. Try to find screen protector or silicone/leather/PU case for V9 over eBay. None !. I end up have to use CSL tablet screen protector which is almost fit. Galaxy Tab is slightly wider, although the vertical side is about the same. There are plenty for Galaxy Tab.

Come back to Froyo update issue. Toshiba tablet has a nice feature to update to Froyo. Just a click of button.

Wake up ZTE ! Don't just know to dump the price but poor support.
[Android Software Development] SrMoure:
Is 2.2 the only solution for storing apps in the sd card?

Maybe there is an app to do this which works in 2.1
[Android Software Development] linuxproffs:
I used universal androot and get temporary root only. I have changed su as proposed by "magic root access", but it didn't help me.

Any proposals?
[Android Software Development] rjm2k:
Thought I knew why, but don't
[Android Software Development] pegaxs:
Something isnt right... I have 600mb set aside for a2sd from previous install and playing around, while this one mounts at boot, my a2sd storage is only 250mb.

It is either mounting in the wrong place or something else... I think it is mounting to the system partition... and not to the SDcard

Will pull the scripts apart and have a look at them and play around a bit to see if i can get it working :)

EDIT:

Got it working finally... I found the script was using vold to mount and unmount the ext2 partition. While not incorrect, for some reason on the ZTE V9 Light, it just never seemed to work. I changed it and used...

mount -t ext2 /dev/block/mmcblk0p2 /system/sd

I also changed the default /system/sdcard link it was using to /system/sd thinking that it was possibly causing confusion in the system.

If anyone else is interested in trying this out, i have re-written the scripts and i can do up a tutorial if it works for someone else... This isnt setup for everyone just yet, as it requires some knowledge of linux/android. If you dont feel comfortable using command line, then my suggestion is to wait till i can make it work a little easier... Will try and get a script made up to make it easier to install..

For anyone interested in trying for me, make sure you have done a backup in clockwork recovery of everything in case something isnt quite right... And make sure you have your sdcard partitioned out correctly. vfat on the front partition and ext2 on the last. I dont use swap partition for this install, so it doesn't really require it. I have put an ext2 partition on the end of my SD card that is 650mb. It's more then enough. I have read on places all over the forums to not use to big an ext2 partition and that anywhere up to about 700mb is usually more then sufficient.
[Android Software Development] alpha4test:
just made a mess out of it...

No backups and only ftm mode avaiable...

I wanted to set te sreen with LCD Resizer, and make the changes permanent.

So i made 140, and rebooted

Same error than befoere appeared, but this time only with SDW.Launcher, and it gets stuck in that loop, since i does't load. everything seems ok in some way since de lock sreen seems ok, ans it unlocks, the top bar show the info and some apps loading in the background, just the launcher does load.

Since i had startup manage installed i managed to add launcher, settings, lcd resizer and others to load on boot

then with some patience i managed to get the resolution in 240

now it just boots gives vofadone logo... and reboots in a loop...

any ideas?
[Android Software Development] pegaxs:
If you have just installed a2sd and got it working, you may need to uninstall and reinstall some apps. Thats why i use titanium backup... every time i played with a2sd, my market app would fail and force close.

Uninstall ADW and try reinstaling it to see if that makes a difference. I had this problem with launcher pro after i did a a2sd chaqnge. It would just force close back to the OEM desktop until i reinstalled launcher pro.

you could also try resetting the LCD density back to normal (for memory its 160) and see if that helps
[Android Software Development] alpha4test:
managed to get to settings menu and reset to factory settings

Still de sreen doesn't accpets the normal size... (i've been using 240) isn't that the default en zte v9?

and i can use the same sdcard or it loop to reboot... so i will have to format it again.

Would a backup from other device work?

or for this case anyone can post the system\"build.prop" file here pls!? (i belive thar woul solve the sreen issue.
[Android Software Development] pegaxs:
240 is WAY to high... It is only 160 by default. I have checked this in "default.prop"

ro.sf.lcd_density=160

I have mine set to 160 because i found that a lot of the other settings were not right or looked wrong.

A backup from another device might work, but unless it is from the same area of the world, its not worth trying. I already know there are things on the Optus V9 from Australia that are different to the UK version.

You can install clockwork recovery from here...

android.podtwo.com/light/recovery-clockwork-2.5.1.8-light.zip (Thanks Sebastian404! :D )

And that will allow you to install other images to get your V9 back to standard.
[Android Software Development] alam1971:
Can you please guide me installing clockwork recovery?
[Android Software Development] pegaxs:
you need to have ADB installed and working with fastboot... If that is all working, its pretty easy from there... You will also need a rooted device, so make sure that is done first.

Download the zip file from the link above and extract the img file to your working directory where you adb installed... (for this example, i will use my setup where i unzipped the recovery update to my c:\Android folder..)

You will need to use command line for this (aka "DOS prompt")... I am working from Windows XP and Ubuntu Linux... dont know anything about Vista or Win7 sorry...

With your device turned on, you will need to connect with adb and reboot the device into bootloader..

c:\Android> fastboot reboot-bootloader

It will turn off, reboot onto a screen that is blank. nothing will show up... if you are using windows, you will know it's in bootloader because you will hear the USB connection noise, on linux, you can just query the device using

pegaxs@pegaxs-desktop:~$ adb get-state

Once you're happy it is in bootloader, you can flash the img file...

c:\Android> fastboot flash recovery b8_recovery-clockwork-2.5.1.8-light.img

It will tell you in your command window that is happening... just wait for it to finish. Once it is finished, you can reboot into recovery by using the command...

c:\Android> fastboot reboot-recovery

There you can backup your device to the SD card and install other good stuff :)
[Android Software Development] chocolat2:
You can change the lcd density permanently editing the properties file "default.prop" in the dir /system. editing the value of

ro.sf.lcd_density=160

with console

su

mount /system -o rw,remount

edit ro.sf.lcd_density in /system/build.prop

mount /system -o ro,remount

then reboot

Or do the same with a root explorer and a text editor.

mount dir /system r/w->edit file default.prop->save file->mount dir /system ro->reboot

I have set it to 220.
[Android Software Development] alam1971:
Thanks. I have managed to install recovery image using windows 7.

I have another question

How can I revert my ZTE V9 to original state? I have got some problem and my stock browser,camera, gps and some other applications is missing. I tried hard reset but it did not helped me.

Can I use the following rom to flash my ZTE? Will it bring it to original state?

depositfiles.com/files/xc8kfv6g6 - romdump post #27
[Android Software Development] alpha4test:
thank's... but the problem is that i get permissions denied on su... (can´t figure why, since i made all the other alteratons before, such as app2sd and all. worst thant that, is that i only can got to ftm mode, and since i made de mistake to set adw as the default lancher (the sreen was no rigth with stock lancher so i gigured i give a try, but i marked as default (dumb) now it boots an it stays in loop, adw error, forced close, and that it, i oficially bricked it good this time!

My hope it to get a nb0 to try via RUT to restore via ftm... i don't see any other wayaround this one...
[Android Software Development] rjm2k:
If you have clockwork etc then a wipe of data should restore your launcher
[Android Software Development] alpha4test:
i don´t have acess to recory, neither i can do anything since no GUI load's.

I thinking about trying a blade room... (scary i now!!!)
[Android Software Development] alpha4test:
anyone know's how to build from source code (that is avaiable, if we have a built nb0 buit from that, i belive that would be a life saver, since we could always use FTM to reflash? rigth?)
[Android Software Development] rjm2k:
cant you flash recovery using fastboot on these things?
[Android Software Development] alpha4test:
i tried adb and what i get is no permissions, when i type "su".

I have the rut tool, but i can't load the img from there
[Android Software Development] pegaxs:
If you get su permission denied from adb, you are either not in shell mode or you have not given it permission to run. What you need to do is have the device unlocked and open on the desktop page. You also need to have usb debug turned on. You can shell into your device and run su from adb. You will then see on the device screen it asking permission to grant superuser access. Click on ok. If the screen is off or locked, you wont see this being asked...

Just check you have root by typing su in a terminal emulator. Sometimes root does not stick after a reboot.
[Android Software Development] alpha4test:
As i've said before, I have no access to the GUI (grafical user interface)

The default lancher was set to ADW, and since then it crashes on start, and keeps crashing in a loop.

...i can hardly change sound volume (if i'm quick enough trough each crash)

At this time i trying to push a stock system image via fastboot... still learning how...
[Android Software Development] jimmyjack72:
Has anyone here tried the build by Sebastian404 for the ZTE V9 over on Modaco?
[Android Software Development] alpha4test:
Hi ppl,

The device loads on FTM mode only, i´m using the zte page drivers for the V9, but using the fastboot i stay's "wainting for device"

The driver display's:

"ZTE handset Diagnostic Interface(DFU) (COM19)"

Is it suposed to be fastboot using ftm?
[Android Software Development] pegaxs:
By build, do you mean the Clockwork recovery mod ? Yes, i have tried it and i am currently running it and can safely say it has saved my bacon a few times already. Works well, the same as clockwork does on any other phone i have here. Easy enough to install as well...

EDIT: the b8 version is working, the b9 version is not. It has a bootloop issue. the working version is located at: android.podtwo.com/light/

About to flash it back to standard to test my a2sd config, so i will be trying out the stock ROM he has loaded up as well for the Optus V9.

Hopefully it all goes well and i can release the a2sd i have been working on.
[Android Software Development] pegaxs:
I dont know what "FTM" mode is on this device, never heard of it on Android phones at all. Remember something about it from Nokia phones like 5 years ago.

What does the screen say, anything or is it just black ?

you may not have the correct drivers installed for bootloader and recovery modes. I had the same issue with my V9 at the start. Would work under normal mode, but not under bootloader mode.

Search the forums for Android bootloader drivers and install the latest. The V9 drivers from the ZTE website dont supply bootloader and recovery mode drivers...
[Android Software Development] alpha4test:
The sreen just display: FTM
[Android Software Development] alpha4test:
i flashed the v9 (before knowing it was.t working) now i can´t reflash anything, with the same driver.

The worst part is that i tried to flash the system.tar (that doesn't work, i'll post here how to create a system.img so we all can have a normal backup), but i tried and then i remenbered i had downloaded the lates version (9) o the recovery, then i just pushed de up arrow and corrected, the file name »system.tar to the "recovery one", but and sadly for me... i forgot to correct the partition (dumb, i know) so i copied the recovery *.img to the system partition....

is this the final "brick" move...!?
[Android Software Development] pegaxs:
It shouldnt be because you didnt flash the bootloader. The bootloader is where all the flashing takes place. unless you put in "fastboot flash boot blahblah.img" then it should still be recoverable.

From what i can gather, FTM stands for Field Test Menu. Most other phones get rid of this by removing the battery for 30 seconds and reinstalling and starting the phone up again. Try that and see what happens... it might not make the phone work, but it might go past the FTM issue...

When you start up your tab, does the usb connect in any way? Even with an error message? If so, it's not dead yet.

i would try and update your drivers and see if you can get ADB working. If your usb connects to the tab, you can still issue commands to it to reboot into different modes.

http://android.modaco.com/content/z...com/319156/winxp-7-zte-blade-drivers-and-adb/

These are the drivers i used to get mine working. I am trying to find out if there is a button press you can do to get it into bootloader mode without ADB as some phones have.
[Android Software Development] alpha4test:
hello i forgot this in the previous message:

when connecting adb (with the v.9 version of sebastian recovery)

if i use : fastboot devices

just returns the command line again

if i try to start adb : adb shell

gives the 2 first lines starting and sucess...

but gives a 3rd line... : --exec '/system/bin/sh' failed: No such file or directory (2) -

***

Also in my device manager i have:

ADB interface

ZTE Composite ADB Interface

Modems

ZTE Handset USB Modem

Disk units

ZTE Mass Storage USB Device
[Android Software Development] pegaxs:
Ok... Version 9 of the recovery is broken. you need to flash version 8. Version 8 can be found at ...

http://android.podtwo.com/light/

you have some control at least over the system... We can work on that...

Can you get a command prompt in ADB shell? Should look like a $ sign. as below. You can then type su and get a root prompt. #

C:\Android> adb shell

$ su

#

another option you could try is typing... When it is in bootloader mode, you wont see anything on the screen apart from the little green Android logo man.

c:\Android> fastboot reboot-bootloader

or

c:\Android> adb reboot bootloader

Recovery wont work because you installed the wrong one. I think you are in the broken recovery, that's why nothing is working.

After you have downloaded the v.8 of the recovery mod, unzip it to your working folder and you can just try typing that into the command line and see if it works...

c:\Android> fastboot flash recovery b8_recovery-clockwork-2.5.1.8-light.img
[Android Software Development] alpha4test:
Pegaxs you've been a live saver!

adb reboot bootloader did the job!

more details later!

Now got to get a working rom/backup to flash the system partition back!

Anyone as a stock backup or other from the system partition done with the clockworkrecovery that can post here?

Thank's!