Root ZTE Smartpad Light v9 7 in tablet android 2.1

[tinkai2]

Hi
Anyone has the instruction to root this device?

Actually , I just got a ZTE smartpad Light v9 running on android 2.1. After installing a couple of apps, I am getting low on space message.

Browsing around, the problem will be solve in 2.2 when my app can be installed in the sd card. While waiting for ZTE to release the 2.2 update (or a way to root 2.1 for this device), I would like to move some apps off the internal memory to my 16 GB SD card.

I was thinking of the files moving /system/app to /sdcard/app, creating a symbolic link between these directory. I got shell access from Android SDK (with adb shell) but when running any command (cp, mv, ln), I got error "permission denied". It seems I need to be a root user.

Is it possible to switch to superuser without having a rooted device? There is no material on how to root this device so rooting this device seems to be out of the question?

Help!! Would really want to have more apps on my device but stuck due to this 2.1 issue. (all apps in internal memory)
Thanks.

 

[tinkai2]

just to update, found the soln finally and would like to share with all zte light v9 user who might also be looking for this.

Step 1 : Download androot. allow root access for your device
[APP] [ROOT] 1-click root for N1 (Latest ver: 1.6.2 beta 5) - xda-developers
//androot still works for os 2.1 (ignore the end of support statement)

Step 2 : Root your phone.
- Copy it to sd card and install it with a file manager get one from market free or i recomend root explorer its the best once it is installed run it see pic below.

Step 3 : I use Android SDK to access shell
- adb shell
- su (at this time, the phone will prompt you to allow superuser access)

Step 4: partition your sdcard to have ext2 partition. (google this)

Step 5 : mount your ext2 partition, move your apps there

http://androidforums.com/samsung-ga...ions-into-sd-card-samsung-galaxy-5-i5500.html

This will do till I get the 2.2 update from zte.

Cheers.

 

[jimmyjack72]

ZTE V9 (Light) updates - Page 2 - xda-developers

Have you seen this? Looks like no official 2.2 for the ZTE Light.

Is your App2SD fix working?

 

[jimmyjack72]

ZTE V9 (Light) updates - Page 2 - xda-developers

Have you seen this? Looks like no official 2.2 for the ZTE Light.

Is your App2SD fix working?

 

[tinkai2]

bummer. no 2.2???? I am up to the stage of manually mounting the sd ext2 filesystem and running the apps from there. first attempt to automatically mount the partition failed, have to send back for service. (they reload the software)
currently want to try rageagainstthecage (ratc) to recover my root access if the same failure occurs.
will retry and let you know.

 

[tinkai2]

nope, auto mount steps did not work.
If you want to try, better install a backdoor su as androot su will fail to work after the reboot. (that's why I have to send back for sw reinstallation)
we are stuck unless we get 2.2.

 

[tinkai2]

Yippie app to SD working now for ZTE V9 2.1. Just need to modify step 12 below

http://androidforums.com/samsung-ga...ions-into-sd-card-samsung-galaxy-5-i5500.html

12) Now comes the tricky part: making Android mount your new partition at boot time. All the hard work would be useless if Android discarded the mount points every time we restarted our phones. To do this we’ll need to create 1 script and store it into /system/etc. Obviously the script should be started by init.rc and need to run as root. Fortunately Android’s init.rc have a gap that makes this possible. The scripts are named install-recovery.sh.

install-recovery.sh content:
#!/system/bin/sh
MYLOG=/data/install-recovery.log
echo "$(date) Starting install-recovery.sh" > $MYLOG
echo "$(date) Waiting SD to become ready..." >> $MYLOG
sleep 10
mount -t ext2 /dev/block/mmcblk0p2 /system/sd 1>>$MYLOG 2>>$MYLOG
mount -o bind /system/sd/app /data/app 1>>$MYLOG 2>>$MYLOG
mount >> $MYLOG

No need for init-sd2.sh, it seems in 2.1 not this script is not allowed, the crytic response when you try to run un-allowed script in /system/etc is "file not found". I was stucked here, retype the command and wondering what was wrong.

Cheers and now I can install all the apps onto with my ZTE light.

My new partition, automounted and now I have 767 MB for apps on sdcard. Thanks to all the sifu who shared theirs experience with it I would be stuck with the measly internal memory for apps.

# mount
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/mmcblk0p2 /system/sd ext2 rw,errors=continue 0 0
/dev/block/mmcblk0p2 /data/app 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_utime=0020,codepage=cp437,iocharset=iso8859-1,s
hortname=mixed,utf8 0 0

 

[tinkai2]

important backup step, create an backdoor su (as ANDroot will not be available after reboot)
Magic Root Access - Android Wiki

 

[pegaxs]

Wow... It all seems so easy...

Anyway, a few issues... I tried installing the backdoor root only to find that it works ok, until i reboot. Then i have to use androot again to root the device. So i guess im not going to have root at reboot if that's the case. Followed everything to the letter except the xbin part, as there is no /system/xbin on this phone, only /system/bin but that is where i found the orginal SU anyway and replaced it.

Another problem is, i have tried and tried to format this SD card with ext2 and FAT32. I have tried gParted and Disk Utility under Ubuntu and Paragon Partition Manager under Winblows. They all format the card in exactly the same way. They are both readable and writeable under Winblows and Ubuntu. They both mount. When i go to remount it in the V9, it just comes up with "unsupported file system, Format ?" When it formats, it kills the partitions and makes it all back to FAT32 covering the whole SD card...

How did you get it to re-mount the SD card with the ext2 partition without it wanting to format it every time ?

And how did you get root to stick after reboot ? That one is giving me the s#!ts something bad... every time i want to use titanium back up, i have to root again...!

EDIT:-

rebooted and installed a different androot.apk and now it seems to be rooted 100% of the time, even after reboot...

Had to reboot it a few times and then it just suddenly mounted the SD card without asking to format it. Mounted the FAT32 partition no issues as 6.8 gig from 8gig (7.4gb) card and 600mb ext2.

It now seems to be working... but not happily. i set aside 600mb for the ext2 partition but it only shows up as 260mb and already shows that as half full. Every time i add an app, the internal memory does down as does the a2sd space. i cant get it to log to /data/install-recovery.log so i cant see what the issue is (yet) and when i type "mount" under SU, the ext2 partition never shows up as mounted, but it shows up under titanium backup... i can manually mount the ext2 partition as -rw and it shows up if i type "mount" again...

 

[tinkai2]

Hi

1. To partition the sdcard, I used the following procedures :
How To Partition SD Card With Ubuntu For Dummies - xda-developers
I think you need to follow the order partition fat32 first, then ext2, then linux_swap (just 32 MB, I think not necessary buyt anyhow what's 32MB)
2. ANDroot may not work after reboot. 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

To your issues after retry :
4. Did you get
/dev/block/mmcblk0p2 /system/sd ext2 rw,errors=continue 0 0
/dev/block/mmcblk0p2 /data/app ext2 rw,errors=continue 0 0
This shows the sdcard ext2 partition is mounted and the remount from /data/app to ext2 partition as carried out by install-recovery.sh commands

mount -t ext2 /dev/block/mmcblk0p2 /system/sd 1>>$MYLOG 2>>$MYLOG
mount -o bind /system/sd/app /data/app 1>>$MYLOG 2>>$MYLOG

If not, I did notice the init.rc seems to mount the sdcard ext2 partition automatically.
####
service vold /system/bin/vold
socket vold stream 0660 root mount
###
Your install-recovery.sh might have failed to run/not ran. This script is execured by init.rc via
###
service flash_recovery /system/etc/install-recovery.sh
oneshot
###
and remember it needs to contain.
install-recovery.sh content:
#!/system/bin/sh
MYLOG=/data/install-recovery.log
echo "$(date) Starting install-recovery.sh" > $MYLOG
echo "$(date) Waiting SD to become ready..." >> $MYLOG
#sleep 10
mount -t ext2 /dev/block/mmcblk0p2 /system/sd 1>>$MYLOG 2>>$MYLOG
mount -o bind /system/sd/app /data/app 1>>$MYLOG 2>>$MYLOG
mount >> $MYLOG

sleep 10 is not necessary. I expanded another ZTE light using the same steps without sleep and it works. (boot up faster)

I would recommend a factory reset and retry. (takes 2 hour on the second ZTE light)

Here's my log :
# ls -l *.sh
ls -l *.sh
-r-xr-x--- wifi system 111 2010-12-15 00:48 init.athwlan.sh
-rw-r--r-- root root 3205 2010-12-15 01:06 init.bt.sh
-r-xr-x--- root shell 1176 2010-12-15 01:00 init.goldfish.sh
-rw-r--r-- root root 3327 2010-12-15 01:00 init.qcom.bt.sh
-rw-r--r-- root root 2735 2010-12-15 01:00 init.qcom.coex.sh
-rw-r--r-- root root 2132 2010-12-15 01:00 init.qcom.fm.sh
-r-xr-x--- wifi wifi 2137 2010-12-15 01:00 init.qcom.sdio.sh
-r-xr-xr-x root root 309 2011-01-05 10:33 install-recovery.sh
# cat install-recovery.sh
cat install-recovery.sh
#!/system/bin/sh
MYLOG=/data/install-recovery.log
echo "$(date) Starting install-recovery.sh" > $MYLOG
echo "$(date) Waiting SD to become ready..." >> $MYLOG
#sleep 10
mount -t ext2 /dev/block/mmcblk0p2 /system/sd 1>>$MYLOG 2>>$MYLOG
mount -o bind /system/sd/app /data/app 1>>$MYLOG 2>>$MYLOG
mount >> $MYLOG

## a reboot and the log of /data/install-recovery.log
$ su_new
su_new
su: access granted, courtesy of Your Page Title
# cd /data
cd /data
# ls in*
ls in*
install-recovery.log
# cat install-recovery.log
cat install-recovery.log
Wed Jan 5 10:36:08 MYT 2011 Starting install-recovery.sh
Wed Jan 5 10:36:08 MYT 2011 Waiting SD to become ready...
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/mmcblk0p2 /system/sd ext2 rw,errors=continue 0 0
/dev/block/mmcblk0p2 /data/app ext2 rw,errors=continue 0 0

Cheers.

 

[tinkai2]

I would recommend a factory reset. AND retry.

 

[tinkai2]

Just to add

the internal memory is still growing, it seems /data/data is used as cache by the apps
From
Android tips
the solution is to move the cache to sdcard. From this tip, a word of warning, apps can access your data in /sdcard. so no banking etc. on my tab.

Is this true? How 2.2 fix this issue?

Cheers.

 

[pegaxs]

I would recommend a factory reset. AND retry.

Going to give that a go.

It does not seems to be mounting the ext2 partition.

If i go into adb shell and do a mount, it only comes up with SDCARD vfat

Want to try and do a rom dump once it has reset back to factory default..

One thing at least is im getting lots of practice to say the least!

EDIT: Got the ROM dump to work... EXt2 is still not auto mounting at reboot...

If i log in with ADB shell and SU and check mount, i only get this...

# mount
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,s
hortname=mixed,utf8 0 0

I did a factory reset and went back and did everything one single step at a time, checking and double checking every time i went along... I can manually mount ext2 and it mounts, no issues... Just wont auto mount at reboot :/

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

And still no logging to anywhere i can find... So i know either the script is not running, or it is getting an error before it even gets to that line...

Just to make sure, i even checked the file permissions on the install file...

# ls -l install-recovery.sh
ls -l install-recovery.sh
-r-xr-xr-x root root 315 2011-01-06 01:33 install-recovery.sh

They match yours. So it cant be a execute issue... It's located in /system/etc

This is what i put...

# cat /system/etc/install-recovery.sh
cat /system/etc/install-recovery.sh
#!/system/bin/sh
MYLOG=/data/install-recovery.log
echo "$(date) Starting install-recovery.sh" > $MYLOG
echo "$(date) Waiting SD to become ready..." >> $MYLOG
#sleep 10
mount -t ext2 /dev/block/mmcblk0p2 /system/sd 1>>$MYLOG 2>>$MYLOG
mount -o bind /system/sd/app /data/app 1>>$MYLOG 2>>$MYLOG
mount >> $MYLOG#

I wish these things had a verbose boot mode. I cant even seem to catch whats going on with logcat :/

 

[tinkai2]

Pegaxs

Bummer. Not sure what is the different between yours ZTE and mine. Can you check init.rc whether it has the lines below? It is located at /, you cannot modify it as it is created fresh during reboot.


###
service flash_recovery /system/etc/install-recovery.sh
oneshot
###

Cheers.

 

[pegaxs]

Pegaxs

Bummer. Not sure what is the different between yours ZTE and mine. Can you check init.rc whether it has the lines below? It is located at /, you cannot modify it as it is created fresh during reboot.
###
service flash_recovery /system/etc/install-recovery.sh
oneshot
###


Cheers.

Defiantly in there... Just for reference, mine is the OptusV9 My Tab sold in Australia... Different places may have a different build or something.

This is what it looks like on my Tab from pulling it down via cat through ADB and direct cut and paste...

service flash_recovery /system/etc/install-recovery.sh
oneshot

Im going a different way about it now. Im going to pull the boot.img out, decompile it, fix init.rc to run a script from /etc/init.d and see if that helps...

 

[tinkai2]

Pegaxs

Ok. Do update us on the progress.

Cheers.

 

[pegaxs]

Darktremor a2sd isnt working just yet.... I have an issue when i recompile the boot.img

Basically, the boot image is 5.1mb... after i pull it down and edit init.rc and recompile it, it doesnt recompile to the same size, but rather half the size. When i try and flash it back, it just goes into a bootloop...

I am still trying to work out why init.rc wont run the install-recovery script like you have said in yours... one way or another, i will get it working

 

[pegaxs]

Still no joy after nearly a week...

I have just tried running the script from the command line to see if that would get it to work... and that was a no joy as well. I just cant seem to work it out... manually it works, i just cant get this script to run... It's like it is ignoring it as soon as it is run, like there is something in the boot that is turning install-recovery.sh off, although in init.rc it seems to be ok... I have even just tried to get the logging part of it working to see if it was the mounting that was getting to be the problem... i just dont know :/

Still working on it though!

EDIT: Update....

Weird this is... took the mount info out of the script and run it again and finally got a log file... yay. Only one issue now... This is a bit weird...

# cat /data/install-recovery.log
cat /data/install-recovery.log
/data/install-recovery.log: No such file or directory
# pwd
pwd
/data
# ls -l in*
ls -l in*
-rw-rw-rw- root root 0 2011-01-10 03:31 install-recovery.log
-rw-rw-rw- root root 944 2011-01-10 03:42 install-recovery.log

Cant move, cant copy, cant chmod... they arnt directories... they show up under LS, just not if i try and do anything else with them...

 

[squzzi]

just try to install 2.2, download to pc from optus website, turn off zte, unzip file from pc, plug in zte to pc, power up zte using power button and - and + at the same time til u see ftm, press start on pc and there u go, wait and when it is done, ur zte will power up good luck, need more help? squzzi123@gmail.com

 

[Deleted User]

How's the camera in 2.1? I'm using 2.2 and camera quality is bad. It's like 640 px and not 3M.

 

[jadedme33]

hi guys, kinda noob here, i just hope this info could help
i just bought zte light a couple of weeks ago at KL, at first it was running on android 2.1 it was good though the screen gives me a lot of headache and also the back soft key always brings me back to where i start it really pissed me off...so the 3rd day of using it the touch screen suddenly wont work, (i did not mention i lived @ penang)...so since the unit is still new i brought it to the service center @ prangin mall...luckily theres a service center here @ penang...u can find it @ the warranty card btw...so i told them the screen suddenly wont work then ask them if they upgrade to android 2.2...they said yes..so they only get the unit except the battery and the back cover...and after 2 days they called me my unit is ready for pick up..they replaced the screen its very responsive now...they also upgrade it to froyo..sweeeeet...now i installed app2sd its working good and also can use wifi tethering...now i really love my smartpad...so i suggest if u still got the warranty card and find the service center located near you they do upgrade and its for free of charge..as long as it still covered by warranty....only downside is still this device doesnt support flash player 10.1 even upgraded to froyo...but still theres skyfire browser...

hope my experience helped...

 

[Deleted User]

I cant seem to play flash using skyfire. I'm using ZTE v9 running Android 2.2

hi guys, kinda noob here, i just hope this info could help
i just bought zte light a couple of weeks ago at KL, at first it was running on android 2.1 it was good though the screen gives me a lot of headache and also the back soft key always brings me back to where i start it really pissed me off...so the 3rd day of using it the touch screen suddenly wont work, (i did not mention i lived @ penang)...so since the unit is still new i brought it to the service center @ prangin mall...luckily theres a service center here @ penang...u can find it @ the warranty card btw...so i told them the screen suddenly wont work then ask them if they upgrade to android 2.2...they said yes..so they only get the unit except the battery and the back cover...and after 2 days they called me my unit is ready for pick up..they replaced the screen its very responsive now...they also upgrade it to froyo..sweeeeet...now i installed app2sd its working good and also can use wifi tethering...now i really love my smartpad...so i suggest if u still got the warranty card and find the service center located near you they do upgrade and its for free of charge..as long as it still covered by warranty....only downside is still this device doesnt support flash player 10.1 even upgraded to froyo...but still theres skyfire browser...

hope my experience helped...

 

[tztm211]

Where can i send my ZTE V9 to reload the SW again in Shah Alam? Anyone got any ideal where i should go? Thanks in advance for the reply. Is there a way to do it by myself.