Guest burstlam Posted December 26, 2010 Report Posted December 26, 2010 (edited) This is a tragic day for my buddy. his blade system clashed accidently and cannot reboot. he try to enter the clockwork mod recovery but failed (for unknown reasons) yet he still able to connect the fastboot mode he flash recovery newest version 2.5.1.8 yet still failed. now he try to turn the clock back by flashing the stock images, he succeed to flash the boot and recovery partition but stucked when trying the system.img (208M)download from this forum he flash it by: "fastboot flash system system.img" but he received the failed message that keep saying the length is too long . is there any kind of limitiations? or simply the syntax is wrong or he should do this by renaming a ZIP-version rom to update.zip and use "fastboot -w update update.zip?" Edited December 26, 2010 by burstlam
Guest Phoenix Silver Posted December 26, 2010 Report Posted December 26, 2010 i would try to flash clockwork again download this file : recovery_clockwork_2.5.1.3_blade.img type fastboot-windows flash recovery recovery-clockwork-2.5.1.3-blade.img go in clockwork as usual and flash the zip if this doesn't work try with clockwork 2.5.0.9
Guest Gerson2k Posted December 26, 2010 Report Posted December 26, 2010 (edited) This is a tragic day for my buddy. his blade system clashed accidently and cannot reboot. he try to enter the clockwork mod recovery but failed (for unknown reasons) yet he still able to connect the fastboot mode he flash recovery newest version 2.5.1.8 yet still failed. now he try to turn the clock back by flashing the stock images, he succeed to flash the boot and recovery partition but stucked when trying the system.img (208M)download from this forum he flash it by: "fastboot flash system system.img" but he received the failed message that keep saying the length is too long . is there any kind of limitiations? or simply the syntax is wrong or he should do this by renaming a ZIP-version rom to update.zip and use "fastboot -w update update.zip?" update.zip or anyfile.zip is for use once you've sucessfully installed ClockWordMod, not to install from Fastboot. please read the ClowWorkMod installation guide thoroughly to install it, I would suggest you install the older version first and get your phone back up and running with the stock image. Edited December 26, 2010 by Gerson2k
Guest burstlam Posted December 26, 2010 Report Posted December 26, 2010 let me clarify that he did flash the clockwork mod again but failed to enter the clockwork mod by pressing the power button and volume down button he could access the phone thr fastboot mode only.. indeed , the fastboot command update could do so only it the rom contain proper txt-base information.
Guest Gerson2k Posted December 26, 2010 Report Posted December 26, 2010 let me clarify that he did flash the clockwork mod again but failed to enter the clockwork mod by pressing the power button and volume down button he could access the phone thr fastboot mode only.. indeed , the fastboot command update could do so only it the rom contain proper txt-base information. Have you tried pulling your battery and leaving it out for 15 mins or rebooting without your SD card as these ave been known to cause boot issues? Also, could the clockworkmod files you have be corrupt? Which version did you use, Paul's Clockworkmod: 2.5.0.9 (d7664757ec3d4862cc408b7304e4df8f), 2.5.1.3 (0733acd513717f2dc7ee08809bd7ea20) do the MD5 checksum check out? Is your device a TFT or OLED - you can also try Seb404 ClockWorkMod 2.5.1.8 to see if it makes any difference? Another option is to use fastboot to flash a stock MCRi ROM, I can't find one on the forum, but that could be down to me using incorrect search strings.
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now