Guest tom619 Posted January 6, 2011 Report Posted January 6, 2011 will this give us a perfect 2.2 rom based on technincal similarities?
Guest Sebastian404 Posted January 6, 2011 Report Posted January 6, 2011 will this give us a perfect 2.2 rom based on technincal similarities? if by 'perfect' you mean 'not working' then yes... I guess I'd need to have one before I could say 100% how similar it is... and I'm not going to rule it out... but it's unlikely, and not likely to be soon if ever.....
Guest Pegaxs Posted January 6, 2011 Report Posted January 6, 2011 (edited) This is near driving me nuts... spent half the day working on getting USB drivers to work in bootloader mode. I cant flash a new boot image with fastboot because the drivers arnt working... anyone else got the drivers to work in bootloader and recovery modes yet ? ADB works fine in normal operation... just not in any other mode... :/ EDIT: Wow that was really weird... tried for hours trying to get drivers to work for fastboot and recovery... posted it here and the next set i found worked :unsure: Anyway... Frankish, your boot.img doesn't work. Device just goes into a boot loop and wont boot past the android logo. Had to reflash my original boot ROM back to get it started again... There is a huge bump down from 5mb to 2.3mb in size... this is the V9 boot.img mod ? Edited January 6, 2011 by Pegaxs
Guest Sebastian404 Posted January 6, 2011 Report Posted January 6, 2011 This is near driving me nuts... spent half the day working on getting USB drivers to work in bootloader mode. I cant flash a new boot image with fastboot because the drivers arnt working... anyone else got the drivers to work in bootloader and recovery modes yet ? ADB works fine in normal operation... just not in any other mode... :/ There is something 'wrong' with the recovery image, so I'd assume fastboot might be just as broken... have you got flash_image ? you could use that during normal mode
Guest Pegaxs Posted January 6, 2011 Report Posted January 6, 2011 The b8 recovery i flashed last night seems to be working fine at the moment. I havent come across any issues. I think it was more the fact that i had busted USB drivers. Now i have the 25th set installed and working, i can adb into bootloader, i can flash alternative boot.img and flash back to mine when it went all wrong... I think Frankish might have sent me an img from a blade not the Light. Their boot.img was about 1/2 the size of mine... I got the 40a2sd that i want to run from /init.d, but i cant find the line i require to put into init.rc to make it go looking there for it. I got a2sd working, i just cant get it to remount at boot from install-recovery.sh for some reason... the script isnt even being started... possibly disabled some where else ? Doesnt even matter what i put in install-recovery.sh, nothing gets run from this script....
Guest Pegaxs Posted January 6, 2011 Report Posted January 6, 2011 Got the boot.img pulled apart... edited the init.rc with the necessary lines to run the a2sd script... Only problem is now that i require the base address to i can ./makebootimg.... How do i find this base address, or can someone find it and let me know what it is and how to find it for future reference The other thing is i require the command line... most of the "examples" seem to have the same thing... Command Line: "no_console_suspend=1 console=null" So i guess i could give that a crack and see if it works... unless someone can help me find where this might be so i can extract that as well :unsure: Thanks
Guest Sebastian404 Posted January 6, 2011 Report Posted January 6, 2011 (edited) Got the boot.img pulled apart... edited the init.rc with the necessary lines to run the a2sd script... Only problem is now that i require the base address to i can ./makebootimg.... How do i find this base address, or can someone find it and let me know what it is and how to find it for future reference The other thing is i require the command line... most of the "examples" seem to have the same thing... Command Line: "no_console_suspend=1 console=null" So i guess i could give that a crack and see if it works... unless someone can help me find where this might be so i can extract that as well :unsure: Thanks This is what worked for clockworkmod recovery... mkbootimg --cmdline '' --kernel kernel --ramdisk ramdisk.gz --base 0x03000000 --output recovery.img I cant see any reason it wont work for boot... Edited January 6, 2011 by Sebastian404
Guest serialmonkey Posted January 6, 2011 Report Posted January 6, 2011 That is the correct base. You can see the commands I've been using to unpack/repack here - http://www.markwallis.id.au/wiki/index.php/ZTEv9#Repack
Guest Pegaxs Posted January 7, 2011 Report Posted January 7, 2011 Oh poop... I recompiled boot.img and noticed it came out as 2.3mb instead of 5.1 as it originally was. Why is there a huge change in size ? Is it leaving something out ? compressing it ? just seems odd... Other issue i have is that it gets to what looks like the bootloader and just hangs there... little picture of the Android logo... and that's as far as it goes. Any ideas on what i should start on now to track down why it isnt working ? I was just trying to get Darktremor A2SD loaded to see if it work on this machine as an alternative to trying to get init.d working... Do i need to clear any cache... just logged into shell and did a logcat and it seems to be in some sort of boot loop... think i killed it now! :P lucky i backed up... i hope... Lots of this came up (over and over again...) and i know this is important... just dont know why :D E/dalvikvm( 1468): Can't open dex cache '/data/dalvik-cache/system@framework@cor [email protected]': No such file or directory E/dalvikvm( 1468): Can't open dex cache '/data/dalvik-cache/system@framework@ext [email protected]': No such file or directory E/dalvikvm( 1468): Can't open dex cache '/data/dalvik-cache/system@framework@fra [email protected]': No such file or directory E/dalvikvm( 1468): Can't open dex cache '/data/dalvik-cache/system@framework@and [email protected]': No such file or directory E/dalvikvm( 1468): Can't open dex cache '/data/dalvik-cache/system@framework@ser [email protected]': No such file or directory E/dalvikvm( 1468): Can't open dex cache '/data/dalvik-cache/system@framework@qcn [email protected]': No such file or directory E/dalvikvm( 1468): Can't open dex cache '/data/dalvik-cache/system@framework@qcr [email protected]': No such file or directory E/dalvikvm( 1468): Can't open dex cache '/data/dalvik-cache/system@framework@Oma [email protected]': No such file or directory E/dalvikvm( 1468): ERROR: no valid entries found in bootclasspath '/system/frame work/core.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/ framework/android.policy.jar:/system/framework/services.jar:/system/framework/qc nvitems.jar:/system/framework/qcrilhook.jar:/system/framework/OmaDrmClient.jar' W/dalvikvm( 1468): JNI_CreateJavaVM failed E/AndroidRuntime( 1468): JNI_CreateJavaVM failed
Guest Johnnyfinlandia Posted January 8, 2011 Report Posted January 8, 2011 (edited) I have an unlocked V9 from Sonera (here in Finland). I have unlocked and rooted my ZTE Blade (Orange San Fran) and have the Japanese Jellyfish 2.2 ROM on and it seems OK. It took me a while to sort out following various instructions. I would like to get the v9 to the same level .. are the instructions the same .. install 'Sebastians' Clockwork recovery and then cold boot with down vol pressed to activate the low level phone access screen? Or is it more complex ? Main reason for me to do it is that the phone/tab is always running out of memory so want A2SD enabled and be able to actually have the option to use it. Also the new keyboard (Gingerbread from Jelly) is a bit nicer etc etc. Main reason probably is being able to do it :D Edited January 8, 2011 by Johnnyfinlandia
Guest serialmonkey Posted January 10, 2011 Report Posted January 10, 2011 Oh poop... I recompiled boot.img and noticed it came out as 2.3mb instead of 5.1 as it originally was. Mine does the same when I unpack/repack boot. Seems to be fine though. Do i need to clear any cache... just logged into shell and did a logcat and it seems to be in some sort of boot loop... think i killed it now! :D lucky i backed up... i hope... Worth a shot. You can do this through recovery. Perhaps clear the Dalvik cache (from the advanced recovery menu) as well.
Guest serialmonkey Posted January 10, 2011 Report Posted January 10, 2011 I would like to get the v9 to the same level .. are the instructions the same .. install 'Sebastians' Clockwork recovery and then cold boot with down vol pressed to activate the low level phone access screen? Or is it more complex ? Yes, just make sure you get his V9/light image and not a Blade recovery image.
Guest alpha xs Posted January 14, 2011 Report Posted January 14, 2011 I ppl! I manage to get app2sd to work, as seen bellow on. I used the device the hole day and reboted several times, but was missging the resixed screen so After that I wanted to set te sreen with LCD Resizer, and make the changes permanent. So i made 140, and rebooted Same error than before 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. any ideas?
Guest hayabusagr Posted February 15, 2011 Report Posted February 15, 2011 Hello everybody Does anybody know if the usb port on ZTE V9 can be used as USB host (to connect for example a USB Stick and transfer files) using the appropriate adapter (see picture below) ? Your replies would be appreciated. Thank you very much !
Guest a19074 Posted June 20, 2011 Report Posted June 20, 2011 Hello everybody Does anybody know if the usb port on ZTE V9 can be used as USB host (to connect for example a USB Stick and transfer files) using the appropriate adapter (see picture below) ? Your replies would be appreciated. Thank you very much ! I have bought a similar adaptor thing from ebay. Plugged it in but nothing happened. I tried connecting the adaptor (from MyTab) to my desktop ( via normal male to male usb cable) and it worked. I guess .. 1. ZTE Light v9 (Optus myTab) doesn't support USB Host or 2. If it does support USB host, your usb must have its own power (i.e. not obtaining power from the tab)
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now