Guest Moxo6 Posted July 12, 2011 Report Posted July 12, 2011 As far as I've seen, numerous people have had this problem, and I'd like to solve it once and for all if possible When installing Corvus5.zip in cwm I get this: Assert failed write_raw_image ^ ("/ tmp / boot.img" / "boot") E: Error in / sdcard/Corvus5.zip (Status 7) Installation aborted I know there are various other topics that cite this error but none of them have actually solved the problem. Would someone take a nandroid backup of Corvus5+SP1+Flash 10.2 (Gles optimised & ensuring that all works properly) and post it here? This isn't a permanent solution, but it would be interesting to see how the two backups differ. P.S. I'm aware that the vega is unbrickable so I'm willing to perform evil experiments on it for the sake of humanity
Guest chaosss Posted July 12, 2011 Report Posted July 12, 2011 As far as I've seen, numerous people have had this problem, and I'd like to solve it once and for all if possible When installing Corvus5.zip in cwm I get this: Assert failed write_raw_image ^ ("/ tmp / boot.img" / "boot") E: Error in / sdcard/Corvus5.zip (Status 7) Installation aborted I know there are various other topics that cite this error but none of them have actually solved the problem. Would someone take a nandroid backup of Corvus5+SP1+Flash 10.2 (Gles optimised & ensuring that all works properly) and post it here? This isn't a permanent solution, but it would be interesting to see how the two backups differ. P.S. I'm aware that the vega is unbrickable so I'm willing to perform evil experiments on it for the sake of humanity I would be very interested in somebody posting a Vegacomb nandroid backup as well as I am having massive problems installing it.
Guest Moxo6 Posted July 12, 2011 Report Posted July 12, 2011 I would be very interested in somebody posting a Vegacomb nandroid backup as well as I am having massive problems installing it. How so? What is it that is not working?
Guest chaosss Posted July 12, 2011 Report Posted July 12, 2011 How so? What is it that is not working? I have posted in the ROM thread but basically after I have flashed the custom ROM it fails to boot (just a black backlit screen). I have tried every combination of deleting the cache etc. I must have tried the process 50 times or so. The updated 1.10 ROM installs perfectly and everytihng works after that but it is just when I apply the VegaComb ROM. Interestingly I had exactly the same problems with Corvus5 but Paul's R8 ROM worked perfectly. Given that all Vegas are the same hardwise wise the only variable i can see is the SD card - I tried with several different format options (one formatted on Windows with Linux Swap ext 2 etc. and one formatting on the Vega). Neither of these made a difference. If someone can upload a nandroid backup I can at least get it running and start diagnostics from there. Currently looking for a way to log the boot process to see exactly where it is failing.
Guest lesd Posted July 12, 2011 Report Posted July 12, 2011 Just a thought... When I first downloaded Corvus5 it wouldn't install properly. It turned out that the zip file hadn't downloaded correctly. The same thing happened the first time I downloaded Vegacomb 1.7. In both cases, downloading the file, and making sure the size was correct, fixed the problem. I had to download Corvus 5 three times. Anyway Vegacomb 1.7 should be 93.62MB and Corvus 5 should be 89.67MB Good luck. PS If I can get this site to work properly on my Vega, I'll post that nandroid backup (after I've deleted personal data)
Guest Moxo6 Posted July 13, 2011 Report Posted July 13, 2011 Just a thought... When I first downloaded Corvus5 it wouldn't install properly. It turned out that the zip file hadn't downloaded correctly. The same thing happened the first time I downloaded Vegacomb 1.7. In both cases, downloading the file, and making sure the size was correct, fixed the problem. I had to download Corvus 5 three times. Yeah, a corrupt zip had crossed my mind, but I did an MD5 against the one on the Corvus5 page and they were the same, so it's not a corruption problem :/ If you could post a Nandroid that would be fantastic
Guest dibbles Posted July 13, 2011 Report Posted July 13, 2011 (edited) Yeah, a corrupt zip had crossed my mind, but I did an MD5 against the one on the Corvus5 page and they were the same, so it's not a corruption problem :/ If you could post a Nandroid that would be fantastic Have you tried a different SD card...? I had a very similar problem with my San Fran phone (ZTE Blade) and even though the micro SD card checked out fine it still give me problems when trying to flash the ROM. Changing the card solved that one for me. Also what version (not that many though) of CWM are you using...? Have you tried flashing the Official 1.10 ROM and noted any such errors..? Edited July 13, 2011 by dibbles
Guest Moxo6 Posted July 13, 2011 Report Posted July 13, 2011 Have you tried a different SD card...? I had a very similar problem with my San Fran phone (ZTE Blade) and even though the micro SD card checked out fine it still give me problems when trying to flash the ROM. Changing the card solved that one for me. Also what version (not that many though) of CWM are you using...? Have you tried flashing the Official 1.10 ROM and noted any such errors..? 1) Tried 3 different SD Card's 4gb, then 8gb, then 2gb 2) Tried 2 different versions of CWM 2.5.1.8 and 3.something 3) I've flashed the official 1.9 and 1.10 and the modaco r8 and had no errors at all
Guest dibbles Posted July 13, 2011 Report Posted July 13, 2011 (edited) 1) Tried 3 different SD Card's 4gb, then 8gb, then 2gb 2) Tried 2 different versions of CWM 2.5.1.8 and 3.something 3) I've flashed the official 1.9 and 1.10 and the modaco r8 and had no errors at all What happens if you flash the latest nightly of CM 7 or the Fuji ROM (very good imo)....? http://download.cyan...om/?device=vega http://android.modac...4-ghz-25042011/ I have read, somewhere, of others experiencing problems when trying to flash ROM's other than those based on the "official" releases, if that makes sense. I imagine that you could also successfully flash the modified 1.10 ROM (used before flashing to VC 1.7 to change the partition sizes). However I never followed up with those posts to note if any solution was found. If you do a nandroid restore from another persons ROM backup would you not then have a potential problem of also using their MAC address rather than your own unique one (if it applies)...? IIRC it can be changed but I do not remember how to do that. If you have the same issues trying to flash the above ROM's then your problem would then be very similar to those others I have noted. I just hope that if any of them have found a solution they then reply here for you. Glad that you have tried differnt cards and CWM's - at least that negates those as potentially causing the problem. Edited July 13, 2011 by dibbles
Guest lesd Posted July 13, 2011 Report Posted July 13, 2011 Yeah, a corrupt zip had crossed my mind, but I did an MD5 against the one on the Corvus5 page and they were the same, so it's not a corruption problem :/ If you could post a Nandroid that would be fantastic Sorry, The quota for uploading files is 4.88MB and the nanroid backup (zipped) is 134MB so I can't upload it. However, I notice that you wanted the optimised version of Flashplayer 10.2:- (libflaskplayer_froyo_gles2_20110318_v10.2.1155.67_signed.apk) and can report that I've just tried to use this version of the flashplayer with BBC Iplayer from within the stock browser. IT DOES NOT WORK with Corvus5 and SP1. IT DOES NOT WORK with R8. i have not tried any other ROMs. Flashplayer 10.3 (from the marketplace) works fine in both cases. In another thread, some people have reported poor sound sync with BBC IPlayer on Corvus5, but I have compared Corvus 5 to R8 and My PC and can't see any difference. I've got some free time today, so i'll try to find out what the error report you got means, and get back to you if I do.
Guest Moxo6 Posted July 13, 2011 Report Posted July 13, 2011 Sorry, The quota for uploading files is 4.88MB and the nanroid backup (zipped) is 134MB so I can't upload it. However, I notice that you wanted the optimised version of Flashplayer 10.2:- (libflaskplayer_froyo_gles2_20110318_v10.2.1155.67_signed.apk) and can report that I've just tried to use this version of the flashplayer with BBC Iplayer from within the stock browser. IT DOES NOT WORK with Corvus5 and SP1. IT DOES NOT WORK with R8. i have not tried any other ROMs. Flashplayer 10.3 (from the marketplace) works fine in both cases. In another thread, some people have reported poor sound sync with BBC IPlayer on Corvus5, but I have compared Corvus 5 to R8 and My PC and can't see any difference. I've got some free time today, so i'll try to find out what the error report you got means, and get back to you if I do. Yeah I tried 10.2 out and none of the aforementioned roms worked (Force closes) anyways, would it be possible for you to upload it to mediafire perhaps (pretty please) I'm aware that it's unlikely to work day to day I just want to eliminate this problem.
Guest lesd Posted July 13, 2011 Report Posted July 13, 2011 I've got some free time today, so i'll try to find out what the error report you got means, and get back to you if I do. OK. I found this link. Post #10 (From Zebrahead) explains the error message and provides a solution. The advice given in the whole thread is: Before installing a new ROM, 1. Wipe Data (in the 'settings app) 2. Delete the cache and the Dalvik cache 3. Toggle the 'script asserts' (just once) I would also suggest that you make sure your battery is fully charged and you have the power lead connected. (I could be wrong about this, but in the dim and distant past, writing to flash memory had different power requirements. That may not be the case here, but better safe than sorry). Good Luck
Guest Moxo6 Posted July 14, 2011 Report Posted July 14, 2011 OK. I found this link. Post #10 (From Zebrahead) explains the error message and provides a solution. The advice given in the whole thread is: Before installing a new ROM, 1. Wipe Data (in the 'settings app) 2. Delete the cache and the Dalvik cache 3. Toggle the 'script asserts' (just once) I would also suggest that you make sure your battery is fully charged and you have the power lead connected. (I could be wrong about this, but in the dim and distant past, writing to flash memory had different power requirements. That may not be the case here, but better safe than sorry). Good Luck Sorry, tried and tested, that's the page I've spent most of last week on. I've tried it with script asserts on and off (just out of curiosity) and I've wiped everything, I've even tried formatting every drive to see if that helps, but it doesn't.
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now