Guest H3ROS Posted January 2, 2012 Report Posted January 2, 2012 (edited) I got ClockworkMod installed when I unlocked my phone via this. Steps 17 and 18. Using the original v3.0 I got the error 7 message, but after flashing the 200MB TPT recommended by you I now have a blue menu and I'm now able to install just about any ROM. CWM-based Recovery v4.0.1.4 Edited January 2, 2012 by H3ROS
Guest eddev Posted January 2, 2012 Report Posted January 2, 2012 I edited the boot.img and rebuilt the v3b ROM. Those having the flashing boot.img error please try this and let me know(I also removed zte logo). http://min.us/mbeFlCTI9m To use fastboot/adb you can download & install the program ADB Made Easy in my siggy, start it, select "Open CMD for ADB commands" and issue adb reboot bootloader and after your phone shuts down and gets stuck in the boot logo(that's bootloader mode) issue fastboot flash boot <path-to-boot.img> For those who wish to use a2sd it's enabled in this ROM(the one I posted and original v3b) as well as init.d scripting support, so if you know what you need to do you can do it. P.S.: Yes, fastboot and adb are part of SDK. I can confirm that the modded v3b ROM installed OK where the orignal v3b did not. Just out of interest what was modified?
Guest tillaz Posted January 2, 2012 Report Posted January 2, 2012 (edited) anyone with install error flash this CWM http://ftpb.free.fr/...pdate_skate.zip then reboot your phone (you must reboot) then try flashing the rom again Edited January 2, 2012 by tillaz
Guest TouchyAndalou Posted January 2, 2012 Report Posted January 2, 2012 Can someone please confirm if the TPT-ing is still required to flash v3B? Looks like some have done so but tillaz seemed to say at one point that he'd fixed the installation errors and I'm a bit confused with the timeline of events. I'm on v2.5 at the moment if that makes any difference. It's worth tpt'ing regardless, as it'll give you more room for installing apps, themes, add-ons, etc.
Guest D3abL3 Posted January 2, 2012 Report Posted January 2, 2012 (edited) I simply rebuilt boot.img without the zte logo and then recompiled the ROM. @tillaz: I think you should replace your link for the one I posted above as it's the one giving no errors. Don't you think? installed bluemonte one instead as this rom dosent seem to want to work as tried installing it 5 times and the error 7 keeps coming up Download the one in 1st post at page 54. Edited January 2, 2012 by D3abL3
Guest pandalorian Posted January 2, 2012 Report Posted January 2, 2012 TPT is still necessary for 3.0b?
Guest tillaz Posted January 2, 2012 Report Posted January 2, 2012 I simply rebuilt boot.img without the zte logo and then recompiled the ROM. @tillaz: I think you should replace your link for the one I posted above as it's the one giving no errors. Don't you think? Download the one in 1st post at page 54. i will, just my internet is playing up & minus wont load for me at the min, got some other stuff i need to add
Guest D3abL3 Posted January 2, 2012 Report Posted January 2, 2012 Is not your connection tillaz, it's really Minus that's having issues.
Guest H3ROS Posted January 2, 2012 Report Posted January 2, 2012 (edited) Comparing the modded one to 3B I can see that tillaz has an extra data folder. The D3abL3 release contains the cert files and manifest in the META-INF folder too, plus many of the files in the system directory have a different size e.g. LatinIME.apk is 7,188,243 bytes in one release and 7,188,147 bytes in another :mellow: Edited January 2, 2012 by H3ROS
Guest Bazabaza Posted January 2, 2012 Report Posted January 2, 2012 (edited) Now got a nice green recovery. Getting confused now...not hard. But is 3B and the modded file the same in essence or are we missing functionality in the modded v 3B? Edited January 2, 2012 by Bazabaza
Guest tillaz Posted January 2, 2012 Report Posted January 2, 2012 Thanx Tilaz, darktremor only works in a sort of halfass way....it really needs to be integrated into the rom using his script here on his facebook site, I can't do it as I only have microsoft and it needs linux or mac.... its has this done
Guest tillaz Posted January 2, 2012 Report Posted January 2, 2012 (edited) that CWM i posted above is the one that finally let us get a full & clean rom dump via adb... all the others failed or they were missing the boot.img i would give it a try Edited January 2, 2012 by tillaz
Guest D3abL3 Posted January 2, 2012 Report Posted January 2, 2012 Comparing the modded one to 3B I can see that tillaz has an extra data folder. The D3abL3 release contains the cert files and manifest in the META-INF folder too, plus many of the files in the system directory have a different size.LatinIME.apk is 7,188,243 bytes in one release and 7,188,147 bytes in another :mellow: Probably because I've optimized(for RAM compensation) and zipaligned the ROM at compilation, data folder was not needed and so I removed it.
Guest frozzcsoo Posted January 2, 2012 Report Posted January 2, 2012 hi Tillaz, my problem is assert failed: write_raw_image("/tmp/boot.img","boot") E: error in "blabla" (status 7) installation aborted :((((( I've installed the PhoTom- CWM - recovery V4.0.1.5 but not working :''(( Can you recommend something? :) pls help meeeee! :]
Guest tillaz Posted January 2, 2012 Report Posted January 2, 2012 hi Tillaz, my problem is assert failed: write_raw_image("/tmp/boot.img","boot") E: error in "blabla" (status 7) installation aborted :((((( I've installed the PhoTom- CWM - recovery V4.0.1.5 but not working :''(( Can you recommend something? :) pls help meeeee! :] just wait i will upload v3c soon
Guest frozzcsoo Posted January 2, 2012 Report Posted January 2, 2012 just wait i will upload v3c soon thank you. Please hurry up my brother! :) otherwise good and nice PhoTom green recovery ^^,
Guest H3ROS Posted January 2, 2012 Report Posted January 2, 2012 Probably because I've optimized(for RAM compensation) and zipaligned the ROM at compilation, data folder was not needed and so I removed it. Maybe thats whats helping to fix some issues then. The files are definitely different in some areas, and yours do end up being smaller.
Guest cyberbit Posted January 2, 2012 Report Posted January 2, 2012 i was getting that error too but the 200M partition like tillaz said solve my prob
Guest tillaz Posted January 2, 2012 Report Posted January 2, 2012 (edited) Maybe thats whats helping to fix some issues then. The files are definitely different in some areas, and yours do end up being smaller. its the boot.img that's the problem not system, for instance if i change the updater script so it writes system first you would see it installs fine then fails when writing boot... im sure its because of the boot.img size because when you do the tpt partition it makes boot & recovery partitions bigger... i think 5mb they are & looking at my boot.img its just over 5mb Edited January 2, 2012 by tillaz
Guest D3abL3 Posted January 2, 2012 Report Posted January 2, 2012 its the boot.img that's the problem not system, for instance if i change the updater script so it writes system first you would see it installs fine then fails when writing boot... im sure its because of the boot.img size Exactly. I will have a look at the TPT's structure to see maximum size for boot partition. Can some who had this error please tell me what partition they had?
Guest H3ROS Posted January 2, 2012 Report Posted January 2, 2012 (edited) @ tillaz One is 2.73MB while the other (yours) is 5MB. I'd just use whichever gave the best overall performance, even if it requires TPT changes. @ D3abLe When I had the error I had the stock 250MB OMC TPT. Edited January 2, 2012 by H3ROS
Guest tillaz Posted January 2, 2012 Report Posted January 2, 2012 things are moving slow until minus its working again... cant even download the battery mods to update them
Guest Bazabaza Posted January 2, 2012 Report Posted January 2, 2012 (edited) @ D3abLe As I haven't done anything I assume that Ive got the stock partition also. Edited January 2, 2012 by Bazabaza
Recommended Posts