Jump to content

[RECOVERY] : ClockworkMod Recovery for ZTE V9 Tablet

Guest Sebastian404

By Guest Sebastian404
in ZTE Light V9 - LightV9.MoDaCo.com

 Share

Recommended Posts

Guest Sebastian404

Guest Sebastian404

Posted
Posted (edited)

Please find attached *MY* build of the latest version of Koush's ClockworkMod Recovery for the ZTE V9/Light Tablet. It is not officially supported by Koush, please do not bother him with support questions for this build.

I have tested it as much as I can, but I'm always open to any more constructive feedback. Please see one post down for a change log for THIS build. Koush seems not to publish a change log (unless you know of one).

To install:

  • Recovery Manager
      Download the img file to your SD card, and then you can use the Recovery Manager application to install your recovery.

    • fastboot method
      • Unplug the USB cable, turn off your device and take out the battery
      • Replace the battery and turn the device on holding the 'volume up' key. The device will stay at the 'green android' screen.
      • Plug the device into the PC.
      • From a command prompt run 'fastboot flash recovery <filename>.img'
      • When this finishes, from the command prompt run 'fastboot reboot'

      • update.zip method
          If you have a previous version or another recovery install, install the update.zip and restart your device.

          • restart your device holding down the 'volume down' key
          • Use the Recovery Manager application to Reboot into Recovery
          • if you have ADB configured type 'adb reboot recovery' from the command line.
              The Latest version of Clockworkmod Recovery can found here

              • Older versions of Clockwork recovery can be found here.

                • Official release

                  [*]The offical version of ClockworkMod Recovery if available for this device can be found here

                  Which version:

                    [*]ClockworkMod Recovery now comes in 2 different versions for 1st and 2nd Generation devices, if your device originaly shipped with Android 2.1, it will usually be 1st generation, if it came with 2.2 it will usually be 2nd generation. Please note if you have used an officaly updater on a 1st generation device it will now be a 2nd generation device.

                    Warning:

                      [*]Support for the old style update files that use the Amend scripting (update-script) method is no longer supported With ClockworkMod Recovery from v3 onwards, if you require support for the Amend scripting method, use v2.5.1.8.

                      Source

                        [*]The Device Config to build ClockworkMod Recovery as part of CyanogenMod can be found on my GitHub.

                        Kernel Information

                          [*]Information about the Kernel used in this ROM can be found on this thread.

Edited by Sebastian404
Guest Sebastian404

Guest Sebastian404

Posted
Posted (edited)

Know issues:

none.

Build Change Log:

2011-02-07 - v2.5.1.8 b1 - Initial release

2011-02-07 - v3.0.0.5 b1 - Initial release

2011-02-16 - v3.0.0.6 b1 - Initial release

2011-03-12 - v3.0.1.4 b1 - Initial release

2011-04-01 - v3.0.2.4 b1 - Initial release

2011-04-01 - v3.0.2.4 b1 - two versions of recovery image to support Generation 1 & 2 devices

2011-04-14 - v3.0.2.4 b2 - usb problem resolved

2011-04-25 - v3.0.2.8 b1 - Initial release

Edited by Sebastian404
Guest weijinfengdu

Guest weijinfengdu

Posted
Posted

Thanks. I will download and try now.

While where could we find the Android 2.2 ROM?

Guest yuden

Guest yuden

Posted
Posted

Hello, a noob question here. :D

Can I revert the changes from ClockworkMod and revert to the stock condition if i want?

Thank you.

Guest Sebastian404

Guest Sebastian404

Posted
Posted
Hello, a noob question here. :D

Can I revert the changes from ClockworkMod and revert to the stock condition if i want?

Thank you.

If you have a device thats the same as one of the 3 stock roms we've found so far, you can install that and it will overwrite the recovery with the stock one.... if you have a different model then you should use romdump and pm me a link to resulting file so I can create your a stock recovery

Guest yuden

Guest yuden

Posted
Posted

It's the greek version with the following info

Firmware version: 2.1-update1

Baseband Version:V9B01

Kernel version:2.6.29 zte-kernel@zdroid-SMT

Build number: COSMOTE_V9V1.0.0B06

I will try to do a romdump later today.

Thanks again. :D

  • 4 weeks later...
Guest Biti

Guest Biti

Posted
Posted (edited)

Tested all only White screen with ZTE logo when try to reboot in recovery.

Firmware version: 2.2

Baseband Version:V9B01

Kernel version:2.6.32.9 zte-kernel@Zdroid-SMT

Build number: TELENOR_V9V1.0.0B01

My romdump: http://www.mediafire.com/?2cyqkddw64z5247

Edited by Biti
  • 2 weeks later...
Guest andremio8

Guest andremio8

Posted
Posted

Hi Sebastien404 can you please tell me step by step, how to resore or back-up my ZTE V9 firmware, because i had a serious problems with my device, just after i installed ( mobile shell V5.0) then after restart .. something happended ( sorry The application SPB Mo-shell Has stopped unexpectedly please try again.....) its keep continues apeared on screen.. so i couldnot get inside main manu to remove

thanks buddy cheers...

  • 3 weeks later...
Guest Biti

Guest Biti

Posted
Posted

g2 works great on my device, but voldown+poweron still not goes to recovery.

Guest Sebastian404

Guest Sebastian404

Posted
Posted
g2 works great on my device, but voldown+poweron still not goes to recovery.

That unfortunately seems to be something that ZTE have removed from the gen2 devices across the board, I'm still trying to get hold on a gen2 device to see what I can find out.

  • 2 weeks later...
Guest Milamber_29

Guest Milamber_29

Posted
Posted

ok im really annoyed and confused at this point.....

this is whats happening. i have optus mytab edition of the v9 light. 2.2 went on fine. no problems there.

but it refuses to root properly. i tryed z4root which worked when it did a temp root but when it did a perminent root it installed the stuff but they didnt actually function and androot just fails. however through the temp z4root i managed to install the gen2 recovery which DOES boot instead of the FTM when i vol down +power but the volume keys DONT work so its pointless.

also now i have the recovery installed i dont need the recovery-clockwork-3.0.2.4-v9-gen2-update_signed version of the file at all do i thats only for when you already have CWM installed yes?

am i just an idiot and have done something wrong?

Guest Nicke

Guest Nicke

Posted
Posted (edited)

How do i know if i have gen1 or gen2?

No branding. ZTE Light.

This unit is beeing sold in sweden for 165 USD or 99 GBP unbranded and unlocked so its becoming quite popular over here.

Edited by Nicke
Guest Nicke

Guest Nicke

Posted
Posted (edited)
This is just a wild guess, but try this https://market.android.com/details?id=com.a...e=search_result . It's for the ZTE Blade, but they are very similar.

Well.. i used the gen2-files.

I cant get into recovery in any other way but using "Recovery Manager". Holding vol down and booting just shows the white ZTE-screen, no boot. Holding vol up just boots the phone.

Edited by Nicke
Guest destroyerGT540

Guest destroyerGT540

Posted
Posted (edited)

Never mind.

Edited by destroyerGT540
Guest destroyerGT540

Guest destroyerGT540

Posted
Posted (edited)

Posted this in the Recovery Manager thread but I'll put it here as well.

Got it working on a stock My Tab upgrade to 2.2. At first it fc when I clicked 'Install Recovery', then I installed Rom Manager and did a fix permissions, reboot. Copied the gen 2 img version to sdcard and it worked!

WOOHOO!

Now to try a new rom..... :unsure:

Cheers Sebastien404!!!

Edited by destroyerGT540
  • 4 weeks later...
Guest navodroid

Guest navodroid

Posted
Posted
Hi Sebastien404 can you please tell me step by step, how to resore or back-up my ZTE V9 firmware, because i had a serious problems with my device, just after i installed ( mobile shell V5.0) then after restart .. something happended ( sorry The application SPB Mo-shell Has stopped unexpectedly please try again.....) its keep continues apeared on screen.. so i couldnot get inside main manu to remove

thanks buddy cheers...

did you find out how to flash it back?

i'm having a problem

my tablet has the ftm working but no boot after the optus logo and i want to flash it back to 2.1 please help i'm going to die.

i tries using the optus upgrade tool but after it finishes it won't boot more than the optus logo.

Guest modacool

Guest modacool

Posted
Posted

Guys.

Is there anything to bring the stock recovery back without having to flash the whole thing back to stock?

I believe i've seen this somewhere but can't remember where now :-(

Guest Nemesis2k9

Guest Nemesis2k9

Posted
Posted

Hey dude, installed the zte v9 clockwork recovery mod to my zte v9, works after it installs, and automatically runs.. but it wont start when i hold the volume 'down' key.. just sits at the green android screen.. i MUST access recovery, have cyanogen 7 mod for zte installed, but "boot loop" it rebooted my phone after update, could'nt access clockwork to wipe cache/ data.. Any other way around this? or a way to wipe cache/ data and reflash? i cant access anything..

  • 1 month later...
Guest Gaz14

Guest Gaz14

Posted
Posted

Hey Sebastian. Don't know if it's just me or not but if I run a fix permissions in recovery I get segmentation error after showing log happens in every build of 4.x.x.x not just v9 for your u8160 builds too

Sent from CM7 V9 using Tapatalk

  • 3 weeks later...
Guest Sebastian404

Guest Sebastian404

Posted
Posted

Hey Sebastian. Don't know if it's just me or not but if I run a fix permissions in recovery I get segmentation error after showing log happens in every build of 4.x.x.x not just v9 for your u8160 builds too

Sent from CM7 V9 using Tapatalk

Sorry I did'nt see this sooner, I'm starting to get too many theads to follow, and the email notification thing on here seems to of gone a bit flakey since the upgrade.. or at least for me...

I have grabbed both my V9 and U8160, the v9 was running 4.0.1.0 for some reason, but they both did work for me...

I've attached a screenshot from my smart...

Do you have a recovery.log file from the /cache dir.. that would be one way to see if I can tell whats going on.....

post-764508-0-46496700-1313846083_thumb.

Guest Gaz14

Guest Gaz14

Posted
Posted (edited)

Sorry I did'nt see this sooner, I'm starting to get too many theads to follow, and the email notification thing on here seems to of gone a bit flakey since the upgrade.. or at least for me...

I have grabbed both my V9 and U8160, the v9 was running 4.0.1.0 for some reason, but they both did work for me...

I've attached a screenshot from my smart...

Do you have a recovery.log file from the /cache dir.. that would be one way to see if I can tell whats going on.....

If I select fix permissions it just says done instantaneously which made me suspicious so I checked the log which I've posted below.

Starting recovery on Sat Aug 20 23:02:45 2011

framebuffer: fd 4 (800 x 480)

CWM-based Recovery v4.0.1.4

recovery filesystem table

=========================

0 /tmp ramdisk (null) (null)

1 /recovery mtd recovery (null)

2 /boot mtd boot (null)

3 /misc mtd misc (null)

4 /cache yaffs2 cache (null)

5 /system yaffs2 system (null)

6 /data yaffs2 userdata (null)

7 /sdcard vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0

8 /sd-ext auto /dev/block/mmcblk0p2 (null)

I:Completed outputting fstab.

I:Processing arguments.

mtd: successfully wrote block at c3a6800000000

I:Set boot command "boot-recovery"

I:Checking arguments.

I:device_recovery_start()

Command: "/sbin/recovery"

ro.secure=0

ro.allow.mock.location=0

ro.debuggable=1

persist.service.adb.enable=1

ro.modversion=clockwork-4.0.1.4-v9

ro.product.device=v9

ro.product.name=V9

usb.default.pid=0x1354

persist.usb.enable_switch=1

persist.usb.linux_switch=1

persist.usb.switch_pid=0x1351

persist.usb.linux_pid=0x1350

persist.usb.default.pid=0x1354

ro.build.date=Sun Jul 31 08:27:55 PDT 2011

ro.build.datei.utc=1307898549

ro.build.owner=sebastian404

ro.build.url=http://android.podtwo.com/

ro.factorytest=0

ro.serialno=

ro.bootmode=unknown

ro.baseband=unknown

ro.carrier=unknown

ro.bootloader=unknown

ro.hardware=v9ztehandset

ro.revision=0

ro.emmc=0

init.svc.usbconfig=stopped

init.svc.recovery=running

init.svc.adbd=running

I:Checking for extendedcommand...

I:Skipping execution of extendedcommand, file not found...

mtd: successfully wrote block at c3a6800000000

I:Set boot command ""

Fixing permissions...

Segmentation fault

Done!

Edited by Gaz14
Guest Sebastian404

Guest Sebastian404

Posted
Posted

I:Set boot command ""

Fixing permissions...

Segmentation fault

Done!

do you have a sd-ext partition?

Guest Sebastian404

Guest Sebastian404

Posted
Posted

Yeah EXT4

im going to guess that is why.. can you do me a favour and test it without the sdcard in?

I'll see if I can find a spare SDcard and see if I can reproduce the problem and fix the fix-permisions.sh script...

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
 Share
Go to topic listing
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.

  I accept