Guest ltkun Posted February 7, 2011 Report Share Posted February 7, 2011 I have got a ZTE Blade of China version. Unfortunately it ship a custom rom by China Unicom which can not be reflashed now. I find the official android recovery has upgraded to 3e. So the clockword recovery is not compatible with this edition？ I have try all kinds of custom recovery image but they do not work any more. Link to comment Share on other sites More sharing options...
Guest Sebastian404 Posted February 7, 2011 Report Share Posted February 7, 2011 I have got a ZTE Blade of China version. I've been trying to find someone who will test my v880 build of clockworkmod recovery... you could try it and report back you can get it from HERE you need the recovery-clockwork-3.0.0.5-x880.img file Link to comment Share on other sites More sharing options...
Guest ltkun Posted February 7, 2011 Report Share Posted February 7, 2011 (edited) I've been trying to find someone who will test my v880 build of clockworkmod recovery... you could try it and report back you can get it from HERE you need the recovery-clockwork-3.0.0.5-x880.img file I have tried this recovery using recovery manager and ssh. But when reboot it, my blade stop at the splash "wo" , no green robot and texts. Would you please give me more suggestion? I am familiar with Linux and can ssh my blade. Also I have installed the sdk for android. I find some samsung I9000 users to downgrade the official recovery 3e to 2e , so they can use the clockwork mod recovery. They make a update.zip to do the job. But the update.zip for i9000 does not match the blade. And I also hear the blade for China changes the flash address to avoid reflash custom rom. I can not using TPT to flash this blade. Edited February 7, 2011 by ltkun Link to comment Share on other sites More sharing options...
Guest ltkun Posted February 7, 2011 Report Share Posted February 7, 2011 (edited) …… Edited February 7, 2011 by ltkun Link to comment Share on other sites More sharing options...
Guest Sebastian404 Posted February 7, 2011 Report Share Posted February 7, 2011 I have tried this recovery using recovery manager and ssh. But when reboot it, my blade stop at the splash "wo" , no green robot and texts. Would you please give me more suggestion? Hmm, when you say SSH, you mean ADB? The problem with the V880 version of the blade is that it does infact use a different Kernel entry address, so all the stuff built for the original blade will not work with the v880 version... the version of clockwork I linked you to has a custom kernel that I build with the new entry address... but if it wont boot, maybe there is more differences. once you have installed that version of clockwork mod, have you tried booting the phone normally and doing a 'reboot recovery' from adb to see if that makes any difference? Link to comment Share on other sites More sharing options...
Guest oh!dougal Posted February 7, 2011 Report Share Posted February 7, 2011 ... I can not using TPT to flash this blade. :P :D :huh: Have you tried? :P That would be new territory -- there are specific warnings about NOT using it with the V880. The China Unicom V880 is NOT a standard Blade, and will not run standard Blade firmware ("roms" and recoveries). Sebastian has made a Clockwork-3-for-V880, which should work, but the condition of your device is unclear from here. Is it still working normally? Link to comment Share on other sites More sharing options...
Guest ltkun Posted February 7, 2011 Report Share Posted February 7, 2011 Hmm, when you say SSH, you mean ADB? The problem with the V880 version of the blade is that it does infact use a different Kernel entry address, so all the stuff built for the original blade will not work with the v880 version... the version of clockwork I linked you to has a custom kernel that I build with the new entry address... but if it wont boot, maybe there is more differences. once you have installed that version of clockwork mod, have you tried booting the phone normally and doing a 'reboot recovery' from adb to see if that makes any difference? I have install a sshd daemon on my phone not ADB . I always do this in order to type command easily. I can boot the phone normally when I install this x880 version . But other images also get this result. The recovery manager always crashes on my phone. And androot can not give me a permanent root privilege. I have to run androot everytime when I reboot the phone. I have installed the x880 img , then reboot the phone normally ,and do a 'reboot recovery' from adb ,but I get then same answer ,the phone just stop at the splash "Wo". Link to comment Share on other sites More sharing options...
Guest El Nino9 Posted February 8, 2011 Report Share Posted February 8, 2011 (edited) I have install a sshd daemon on my phone not ADB . I always do this in order to type command easily. I can boot the phone normally when I install this x880 version . But other images also get this result. The recovery manager always crashes on my phone. And androot can not give me a permanent root privilege. I have to run androot everytime when I reboot the phone. I have installed the x880 img , then reboot the phone normally ,and do a 'reboot recovery' from adb ,but I get then same answer ,the phone just stop at the splash "Wo". write protection like HTC and motorola?!!? :| question to Sebastian... what would in theory happen if they flashed the Hungarian update for memory? *i recommend nobody to do this!* in theory it probably will brick? or would it wipe everything and flash the same things as the Hungarian? this is me not knowing the x880 specs as i haven't googled it lol but if it changed the partition layout, the kernel would also be changed and the recovery partition too? maybe RIL issues to follow if they did that as we needed to mod it to work on our blades? just interested about this topic :P Edited February 8, 2011 by El Nino9 Link to comment Share on other sites More sharing options...
Guest ltkun Posted February 9, 2011 Report Share Posted February 9, 2011 Here is some information I get from my v880. I can scratch any file from my v880. # cat /proc/mtd dev: size erasesize name mtd0: 00500000 00020000 "recovery" mtd1: 00500000 00020000 "boot" mtd2: 00180000 00020000 "splash" mtd3: 00080000 00020000 "misc" mtd4: 02580000 00020000 "cache" mtd5: 0dc00000 00020000 "system" mtd6: 0a280000 00020000 "userdata" mtd7: 01500000 00020000 "oem" mtd8: 00180000 00020000 "persist" how to open img file on the windows7 ? Link to comment Share on other sites More sharing options...
Guest Phoenix Silver Posted February 10, 2011 Report Share Posted February 10, 2011 Here is some information I get from my v880. # cat /proc/mtd dev: size erasesize name mtd0: 00500000 00020000 "recovery" mtd1: 00500000 00020000 "boot" mtd2: 00180000 00020000 "splash" mtd3: 00080000 00020000 "misc" mtd4: 02580000 00020000 "cache" mtd5: 0dc00000 00020000 "system" mtd6: 0a280000 00020000 "userdata" mtd7: 01500000 00020000 "oem" mtd8: 00180000 00020000 "persist" from a "normal" blade # cat /proc/mtd dev: size erasesize name mtd0: 00480000 00020000 "recovery" mtd1: 00480000 00020000 "boot" mtd2: 00180000 00020000 "splash" mtd3: 00060000 00020000 "misc" mtd4: 02940000 00020000 "cache" mtd5: 0cf80000 00020000 "system" mtd6: 0d020000 00020000 "userdata" mtd7: 00180000 00020000 "persist" what is in oem ???? Link to comment Share on other sites More sharing options...
Guest El Nino9 Posted February 12, 2011 Report Share Posted February 12, 2011 Hmm, when you say SSH, you mean ADB? The problem with the V880 version of the blade is that it does infact use a different Kernel entry address, so all the stuff built for the original blade will not work with the v880 version... the version of clockwork I linked you to has a custom kernel that I build with the new entry address... but if it wont boot, maybe there is more differences. once you have installed that version of clockwork mod, have you tried booting the phone normally and doing a 'reboot recovery' from adb to see if that makes any difference? hello sebastian. erm i have a question to ask you relating to this as i would like to try help them also have custom roms. my question is can we use our back up of an 2e recovery or even a custom recovery by using the command: dd if=/sdcard/recovery.img of=/dev/block/mmcblkXpyy when a recovery image is on the sdcard called recovery ofcourse and block found correct? i.e. X in bold maybe 0?and the partition can be found? just a theory... i dont recommend anyone tries this. im now thinking ZTE might have patched it? Link to comment Share on other sites More sharing options...
Guest hecatae Posted April 2, 2011 Report Share Posted April 2, 2011 from a "normal" blade # cat /proc/mtd dev: size erasesize name mtd0: 00480000 00020000 "recovery" mtd1: 00480000 00020000 "boot" mtd2: 00180000 00020000 "splash" mtd3: 00060000 00020000 "misc" mtd4: 02940000 00020000 "cache" mtd5: 0cf80000 00020000 "system" mtd6: 0d020000 00020000 "userdata" mtd7: 00180000 00020000 "persist" what is in oem ???? seems to be the usb handset driver Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now