Guest rjm2k Posted January 2, 2011 Report Posted January 2, 2011 Someone on XDA was asking for info on the new ZTE V9 Tablet, which afaik has the same chipset/kernel as the blade so I suggested they dump their ROM in order to identify whether or not the Blade 2.2 might work on the tablet but also if the V9 gets 2.2 whether that will work on the blade etc. Also maybe new wifi drivers to try.... V9 depositfiles.com/files/xc8kfv6g6 - romdump depositfiles.com/files/vwgf6yxhu - config.gz
Guest serialmonkey Posted January 2, 2011 Report Posted January 2, 2011 which afaik has the same chipset/kernel as the blade Comparing the kernel config.gz from a Light to the config.gz of the Blade (which I found at http://android.modaco.com/content/zte-blad...ploading-over/) I see a large amount of difference. While the kernel version might be the same, I'm thinking ZTE might have altered the kernel for the Light beyond what is found in the Blade.
Guest rjm2k Posted January 2, 2011 Report Posted January 2, 2011 Comparing the kernel config.gz from a Light to the config.gz of the Blade (which I found at http://android.modaco.com/content/zte-blad...ploading-over/) I see a large amount of difference. While the kernel version might be the same, I'm thinking ZTE might have altered the kernel for the Light beyond what is found in the Blade. yes it looks like the kernel source may be shared but the particular configuration which controls which bits of the source are used is not. It may still be of use though, since android itself maybe similar enough plus the wifi drivers and maybe RIL look the same.
Guest Tom G Posted January 2, 2011 Report Posted January 2, 2011 (edited) Someone on XDA was asking for info on the new ZTE V9 Tablet, which afaik has the same chipset/kernel as the blade so I suggested they dump their ROM in order to identify whether or not the Blade 2.2 might work on the tablet but also if the V9 gets 2.2 whether that will work on the blade etc. Also maybe new wifi drivers to try.... V9 depositfiles.com/files/xc8kfv6g6 - romdump depositfiles.com/files/vwgf6yxhu - config.gz The RIL setup could be interesting. Its basically a blade with a bigger screen so if it doesn't have the framework changes we might get something usable out of it. These are available over here, so I should see if I can get a dump of the local version (Optus MyTab). I haven't seen any shops with one setup to test yet, but I'm sure I can find one. I wonder what they would think about me dumping a rom off it. Edited January 2, 2011 by Tom G
Guest Matty-p Posted January 2, 2011 Report Posted January 2, 2011 (edited) The RIL setup could be interesting. Its basically a blade with a bigger screen so if it doesn't have the framework changes we might get something usable out of it. These are available over here, so I should see if I can get a dump of the local version (Optus MyTab). I haven't seen any shops with one setup to test yet, but I'm sure I can find one. I wonder what they would think about me dumping a rom off it. well they dont have to find out do they your just checking to see if your sd card would work in it :unsure: obviously !! Edited January 2, 2011 by Matty-p
Guest rjm2k Posted January 2, 2011 Report Posted January 2, 2011 The RIL setup could be interesting. Its basically a blade with a bigger screen so if it doesn't have the framework changes we might get something usable out of it. These are available over here, so I should see if I can get a dump of the local version (Optus MyTab). I haven't seen any shops with one setup to test yet, but I'm sure I can find one. I wonder what they would think about me dumping a rom off it.someone posted config from optus in thread. On xda could ask for rom too
Guest serialmonkey Posted January 2, 2011 Report Posted January 2, 2011 These are available over here, so I should see if I can get a dump of the local version (Optus MyTab). I've tried to romdump mine (I've got the optus version) but I'm having trouble as per - http://forum.xda-developers.com/showpost.p...mp;postcount=30 I haven't seen any shops with one setup to test yet, but I'm sure I can find one. Every Optus shop I spoke to didn't have any demo units. Some said they would in the future, others said it was because it was pre-paid and they didn't carry demo's of pre-paids. M.
Guest Pegaxs Posted January 5, 2011 Report Posted January 5, 2011 I've got a Optus V9 here im happy to give a hand out with. I can try and do a ROM dump for you guys, only problem is that i have already been toying around with it to get A2SD working... That might be the only difference over a stock rom. Although my A2SD seems a little weird :/ Will see how i go... If i can get it to dump, i will edit this post with a link to it. Another funny issue i have with it... not really related, is that i cant mount it with ADB under Ubuntu, but i can mount my Desire HD, my wifes Desire (hahah no pun intended) and my LG, just this V9 tab wont play ball under Linux... works fine on XP... :/
Guest serialmonkey Posted January 5, 2011 Report Posted January 5, 2011 FYI, romdump will cause you issues on the Optus model due to a space in the product ID. If you really want to dump then you need to root, then via a combination of adb and a terminal emulator edit the default.props to remove the space in the product ID. Sebastian404 was going to look at fixing the issue with romdump to allow it to dump images that contain spaces in the ID.
Guest Pegaxs Posted January 5, 2011 Report Posted January 5, 2011 (edited) FYI, romdump will cause you issues on the Optus model due to a space in the product ID. If you really want to dump then you need to root, then via a combination of adb and a terminal emulator edit the default.props to remove the space in the product ID. Sebastian404 was going to look at fixing the issue with romdump to allow it to dump images that contain spaces in the ID. That's kinda weird, because it dumped ok for me... And my device comes up as V9_Optus so there is no space. Unless i am dumping wrong. I just used busybox to make a tar of the /system part... is that right ? i got it off a tutorial on XDA. No point uploading a 144meg file if it's not the right way to dump the ROM. EDIT: i searched this ZTE - Blade forum and found another way to dumprom after doing a cat /proc/mtd I have 3 img files now. system.img (240mb) boot.img (5mb) recovery.img (5mb) Anyone let me know how to do it correctly if this isnt, or confirm this is right and i will upload :unsure: Cheers! On a side note... I got a2sd to work... partially... I followed a howto on Androidforums and it all appears to work... if i mount everything manually. I have been trying to get install-recovery.sh script to remount them at boot time. No good. I have to adb shell in and mount them manually. It's like the system isnt even running install-recovery.sh. I added the option to log to the script, and it has never written a log file, hinting to me that the script isnt even being init. I checked init.rc and the line to run the script is in there. Is there somewhere else it could be being blocked, or another way i could auto mount the a2sd ext2 on reboot ? thanks! B) Edited January 5, 2011 by Pegaxs
Guest Frankish Posted January 5, 2011 Report Posted January 5, 2011 That's kinda weird, because it dumped ok for me... And my device comes up as V9_Optus so there is no space. Unless i am dumping wrong. I just used busybox to make a tar of the /system part... is that right ? i got it off a tutorial on XDA. No point uploading a 144meg file if it's not the right way to dump the ROM. Anyone let me know how to do it correctly if this isnt, or confirm this is right and i will upload :unsure: Cheers! On a side note... I got a2sd to work... partially... I followed a howto on Androidforums and it all appears to work... if i mount everything manually. I have been trying to get install-recovery.sh script to remount them at boot time. No good. I have to adb shell in and mount them manually. It's like the system isnt even running install-recovery.sh. I added the option to log to the script, and it has never written a log file, hinting to me that the script isnt even being init. I checked init.rc and the line to run the script is in there. Is there somewhere else it could be being blocked, or another way i could auto mount the a2sd ext2 on reboot ? thanks! B) What a2sd are you using? Are you using the method where it allows scripts to be started from init.d?
Guest Pegaxs Posted January 5, 2011 Report Posted January 5, 2011 The tutorial i used is a combination of... http://androidforums.com/tablets-mids/2446...roid-2-1-a.html http://androidforums.com/samsung-galaxy-5/...xy-5-i5500.html http://android-dls.com/wiki/index.php?titl...gic_Root_Access And for some reason i cant find init.d... I have been trying to get it to mount from init.rc using the install-recovery.sh and it just wont work for me. PS: Please dont ban me if im doing this linking thing wrong...
Guest Frankish Posted January 5, 2011 Report Posted January 5, 2011 (edited) The tutorial i used is a combination of... http://androidforums.com/tablets-mids/2446...roid-2-1-a.html http://androidforums.com/samsung-galaxy-5/...xy-5-i5500.html http://android-dls.com/wiki/index.php?titl...gic_Root_Access And for some reason i cant find init.d... I have been trying to get it to mount from init.rc using the install-recovery.sh and it just wont work for me. PS: Please dont ban me if im doing this linking thing wrong... The way i would do it is decompile boot.img, add start userinit on property:userinit.filesystem.ready=1 to init.rc above class_start default. Recompile. Create init.d folder in /system/etc/ and add the attached script to the init.d folder. That's all i have done in the past. Oh and remove the .txt from the end of the a2sd file :unsure:40a2sd.txt Edited January 5, 2011 by Frankish
Guest Pegaxs Posted January 5, 2011 Report Posted January 5, 2011 Just reading up now how to decompile and recompile boot.img and adding lines to init.rc Will the system then just run every script i put in init.d or how do i call them at boot time? Do i need to add a line into the init.rc for that as well?
Guest Frankish Posted January 5, 2011 Report Posted January 5, 2011 It will automatically run any script that is in init.d folder at startup. Upload your boot.img and i'll add the lines for you?
Guest Pegaxs Posted January 5, 2011 Report Posted January 5, 2011 (edited) Hope this is the right one... The only other thing i might need help with is how to reflash it back to the phone.... reading up on that now as well... something about fastboot flash boot newimage.img??? ps: sorry i had to RAR the image, there is a 4.88mb cut off for files, and this boot img is 5.1mb. Compressed it's about 2.5mb While i was waiting, i created the init.d folder... do i need to set permissions for it ? What do i need to rename the txt file you posted? and what permissions will it need to have ? Thanks heaps for the help :unsure:boot.rar Edited January 5, 2011 by Pegaxs
Guest Frankish Posted January 5, 2011 Report Posted January 5, 2011 Actually i'm not sure i only know how to do it when you're flashing a new rom. Sorry :S
Guest Sebastian404 Posted January 5, 2011 Report Posted January 5, 2011 I dont have a device (yet) Ive put together a port of ClockworkMod, I'm told it works... http://android.podtwo.com/light/ if anyone wants to grab the b8 version and let me know how it works..... any feedback would be welcome.
Guest Pegaxs Posted January 5, 2011 Report Posted January 5, 2011 been reading heaps... so i might have a crack at it... worst i can do is brick it... send it back for warranty and get a new one! :unsure: Big questions though... do i need to set permissions for the init.d folder and the script thats going to be in there ? What i have done so far is put the file in as /system/etc/init.d/40a2sd and did a chmod 755 on 40a2sd to give it root + exec... does that sound about right ? i have not changed any permissions on the init.d folder. a: cause i dont know if i have to and b: i dont know what they would need to be changed too ??? Getting there... im determined to get this working one way or another...
Guest Frankish Posted January 5, 2011 Report Posted January 5, 2011 been reading heaps... so i might have a crack at it... worst i can do is brick it... send it back for warranty and get a new one! :unsure: Big questions though... do i need to set permissions for the init.d folder and the script thats going to be in there ? What i have done so far is put the file in as /system/etc/init.d/40a2sd and did a chmod 755 on 40a2sd to give it root + exec... does that sound about right ? i have not changed any permissions on the init.d folder. a: cause i dont know if i have to and b: i dont know what they would need to be changed too ??? Getting there... im determined to get this working one way or another... Shouldn't need to change any permissions. First try sebastians clockwork recovery. If that is working ok then try my boot.img. (I know it's smaller!) Flash through fastboot. Look it up if you need to. Command would be "fastboot flash boot boot.img".boot.img
Guest serialmonkey Posted January 5, 2011 Report Posted January 5, 2011 That's kinda weird, because it dumped ok for me... And my device comes up as V9_Optus so there is no space. Unless i am dumping wrong. I just used busybox to make a tar of the /system part... is that right ? i got it off a tutorial on XDA. Ahh, you didn't use romdump. That explains :-) Can you post a cut/paste of your default.prop sometime just to be sure ?
Guest Pegaxs Posted January 5, 2011 Report Posted January 5, 2011 can boot into recovery... only problem i have now is that windows doesnt have the drivers so i can use recovery to install this recovery image... unless there is another way around doing it... i tried going through ROM Manager, but it doenst give me the option to flash a custom recovery... adb is now saying no devices are connected.... I have installed the V9 drivers from ZTE... but i dont think they are enough... anyone have an alternative way for this ???
Guest Frankish Posted January 5, 2011 Report Posted January 5, 2011 Download terminal emulator and do it all on the device?
Guest Pegaxs Posted January 5, 2011 Report Posted January 5, 2011 (edited) Installed ok... dont know why i didnt think of doing this via terminal... been up all night working on this crazy thing... Anyway, recovery worked. Installed without any issues... adb reboot recovery <--- booted straight in without an issue... (As a side issue... how do we get this device into recovery without ADB... ie: if i totally mess up the flashing of the ROM. power + ??? so i can reflash to my backup) Just doing a back up to see how it goes... All appeared to do a smooth backup... rebooted ok back into OS... anything else i can try with it ? might try flashing the boot img later with the apps2sd fix thanks Frankish :unsure: and serialmonkey... i think this is what you were looking for ??? Default.prop was in the / folder... the one is /system is "build.prop" # cat default.prop cat default.prop # # ADDITIONAL_DEFAULT_PROPERTIES # ro.secure=1 ro.allow.mock.location=0 ro.debuggable=0 persist.service.adb.enable=0 # cat /system/build.prop cat /system/build.prop # begin build properties # autogenerated by buildinfo.sh ro.build.id=ERE27 ro.build.display.id=V9 Prepaid-T02 ro.build.version.incremental=20101203.170854 ro.build.version.sdk=7 ro.build.version.codename=REL ro.build.version.release=2.1-update1 ro.build.date=Fri Dec 3 17:20:23 CST 2010 ro.build.date.utc=1291368023 ro.build.type=user ro.build.user=user ro.build.host=localhost.localdomain ro.build.tags=release-keys ro.product.model=V9 ro.product.brand=ZTE ro.product.name=V9_Optus ro.product.device=v9 ro.product.board=v9 ro.product.cpu.abi=armeabi ro.product.manufacturer=ZTE ro.product.locale.language=en ro.product.locale.region=AU ro.wifi.channels= ro.board.platform=msm7k # ro.build.product is obsolete; use ro.product.device ro.build.product=v9 # Do not try to parse ro.build.description or .fingerprint ro.build.description=V9_Optus-user 2.1-update1 ERE27 20101203.170854 release-key s ro.build.fingerprint=ZTE/V9_Optus/v9/v9:2.1-update1/ERE27/20101203.170854:user/r elease-keys usb.default.pid=0x1354 # end build properties # # system.prop for surf # ########################################## #History: #when who what, where, why #-------- ---- --------------------------------------------------- #2010-01-27 zhangxian new file for moonckae bord config #2010-03-03 luwenjun modify the version number #2010-04-01 zhaobin need setupwizard when first boot #2010-05-11 zhangping add default value of the timezone is Europe/London(Londo n, Dublin) #2010-06-25 lirong set default value of "ro.camera.sound.forced" #2010-07-15 lichuan disable setupwizard #2010-10-20 wt set default value of "ro.camera.sound.forced" as "1" ########################################## #ro.com.google.clientidbase=android-optus-au ro.setupwizard.mode=DISABLED ro.build.baseband_version=V9B01 ro.build.software_version=OPTUS_V9V1.0.0B10 ro.build.sw_internal_version=OPTUS_V9V1.0.0B10 ro.product.board_name=soft-stone rild.libpath=/system/lib/libril-qc-1.so rild.libargs=-d /dev/smd0 persist.rild.nitz_plmn= persist.rild.nitz_long_ons_0= persist.rild.nitz_long_ons_1= persist.rild.nitz_long_ons_2= persist.rild.nitz_long_ons_3= persist.rild.nitz_short_ons_0= persist.rild.nitz_short_ons_1= persist.rild.nitz_short_ons_2= persist.rild.nitz_short_ons_3= DEVICE_PROVISIONED=1 debug.sf.hw=0 dalvik.vm.heapsize=24m ro.config.ringtone=BeatPlucker.ogg ro.config.notification_sound=OnTheHunt.ogg ro.config.alarm_alert=BellPhone.ogg persist.service.mount.playsnd = 1 persist.sys.timezone=Australia/Sydney ro.camera.sound.forced=1 # # ADDITIONAL_BUILD_PROPERTIES # ro.com.google.gmsversion=2.1_r12 ro.sf.lcd_density=160 ro.com.google.clientidbase=android-zte ro.com.google.clientidbase.ms=android-zte ro.com.google.clientidbase.yt=android-zte ro.com.google.clientidbase.am=android-optus-au ro.com.google.clientidbase.vs=android-zte ro.com.google.clientidbase.gmm=android-zte net.bt.name=Android ro.config.sync=yes dalvik.vm.stack-trace-file=/data/anr/traces.txt Edited January 5, 2011 by Pegaxs
Guest Sebastian404 Posted January 5, 2011 Report Posted January 5, 2011 and serialmonkey... i think this is what you were looking for ??? Default.prop was in the / folder... the one is /system is "build.prop" ro.build.display.id=V9 Prepaid-T02 Thats what he was looking for, there is a space in the display.id I'm going to swear 100% to it, but I thought that was against the rules...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now