Guest jeffmasson Posted April 24, 2011 Report Posted April 24, 2011 Can someone help me I am having trouble installing some roms. R8 installs fine so dose c7 nightlys but all the rest fail cwm comes up with errors Fuji installs but when you boot up you start doing the Google login stuff then it chrashes and then just hangs on the boot logo Corvus 0.5 give a invaded Rom error Corvus5 starts to install and gives Writing boot image... assert failed:write_raw_image("/tmp/bootimg" , "boot") E:Error in /sdcard/download/Crvus5.zip (Status 7) Installation aborted. I like c7 for all the tools ect. But still slow at times and r8 is stage but very lacking in extras. So want to try the rest to find the best one for me
Guest beegee1962 Posted April 24, 2011 Report Posted April 24, 2011 Can someone help me I am having trouble installing some roms. R8 installs fine so dose c7 nightlys but all the rest fail cwm comes up with errors Fuji installs but when you boot up you start doing the Google login stuff then it chrashes and then just hangs on the boot logo Corvus 0.5 give a invaded Rom error Corvus5 starts to install and gives Writing boot image... assert failed:write_raw_image("/tmp/bootimg" , "boot") E:Error in /sdcard/download/Crvus5.zip (Status 7) Installation aborted. I like c7 for all the tools ect. But still slow at times and r8 is stage but very lacking in extras. So want to try the rest to find the best one for me Do you do a full wipe between flashing the ROMs? If not use CWM to wipe data, cache and dalvik-cache (under advanced). Reformat your SDcard and try again.
Guest jeffmasson Posted April 24, 2011 Report Posted April 24, 2011 Do you do a full wipe between flashing the ROMs? If not use CWM to wipe data, cache and dalvik-cache (under advanced). Reformat your SDcard and try again. Sorry I forgot to say I did the 3 wipes and downloaded with PC and Vega tried 2 different cards but no luck
Guest beegee1962 Posted April 25, 2011 Report Posted April 25, 2011 Sorry I forgot to say I did the 3 wipes and downloaded with PC and Vega tried 2 different cards but no luck Then I have no idea what is going wrong on your tablet. I am flashing nearly every day a new ROM and have only problems if I forget to wipe.
Guest premieral Posted April 25, 2011 Report Posted April 25, 2011 Can someone help me I am having trouble installing some roms. R8 installs fine so dose c7 nightlys but all the rest fail cwm comes up with errors Fuji installs but when you boot up you start doing the Google login stuff then it chrashes and then just hangs on the boot logo Corvus 0.5 give a invaded Rom error Corvus5 starts to install and gives Writing boot image... assert failed:write_raw_image("/tmp/bootimg" , "boot") E:Error in /sdcard/download/Crvus5.zip (Status 7) Installation aborted. I like c7 for all the tools ect. But still slow at times and r8 is stage but very lacking in extras. So want to try the rest to find the best one for me Do you do the clockwork mod instal on all roms and do you set up your wifi before the Google set up stuff, I think if you try and describe every stage exactly (ball ache I know) but it might point to something we can help with
Guest jeffmasson Posted April 25, 2011 Report Posted April 25, 2011 Do you do the clockwork mod instal on all roms and do you set up your wifi before the Google set up stuff, I think if you try and describe every stage exactly (ball ache I know) but it might point to something we can help with Ok I will try. I had installed r8 with out cwm then installed c7 nightly using cwm. I downloaded Fuji on the Vega and then used cwm to install doing the 3 wipes first when I rebooted I leaped getting forced errors every time I click the screen then I rembered I had read you are mentioned to do the 3 wipes after as well so did the 3 wipes untapped did 3 wipes. Booted in to Fuji the Google stuff starts auto so start going though it no way to set wifi as you can't get to setting untill you done it. I skiped that and it chrashed then rebooted and stuck on logo After I had the stuck boot screen from the Fuji rom I had to re flash stock rom then I installed cwm using the quick install exe from this site. I the truer again with Fuji 3 wipes install 3 wipes skip Google then it crashed and froze on logo Reflashed to stock reinstalled cwm I then downloaded corvus5 from hotfile using my PC fromated my memcard and copyed it to root of card. Next I booted Vega into cwm and did the 3 wipes then install rom but get error above. Then tried Corvus 0.5 but go a different error sorry can't remember what it was. Then gave up reinstalled c7 and posed this
Guest premieral Posted April 25, 2011 Report Posted April 25, 2011 Ok I will try. I had installed r8 with out cwm then installed c7 nightly using cwm. I downloaded Fuji on the Vega and then used cwm to install doing the 3 wipes first when I rebooted I leaped getting forced errors every time I click the screen then I rembered I had read you are mentioned to do the 3 wipes after as well so did the 3 wipes untapped did 3 wipes. Booted in to Fuji the Google stuff starts auto so start going though it no way to set wifi as you can't get to setting untill you done it. I skiped that and it chrashed then rebooted and stuck on logo After I had the stuck boot screen from the Fuji rom I had to re flash stock rom then I installed cwm using the quick install exe from this site. I the truer again with Fuji 3 wipes install 3 wipes skip Google then it crashed and froze on logo Reflashed to stock reinstalled cwm I then downloaded corvus5 from hotfile using my PC fromated my memcard and copyed it to root of card. Next I booted Vega into cwm and did the 3 wipes then install rom but get error above. Then tried Corvus 0.5 but go a different error sorry can't remember what it was. Then gave up reinstalled c7 and posed this The only thing that stands out as glaringly obvious is that you only wipe the cache etc ( the threee wipes ) before loading a rom not after. if you do it before then after you will wipe the new stuff. give it a another go factory reset/wipe date, clear the cache then clear dalvik cache and then just install a rom using the insatl zip from sd card and see if this makes a difference? i`m sorry i cant be more help but i have installed every rom including stock 1.09 and never had this problem, just bsod a few times :) thank goodness for cwm backup. let us know if you are still getting the problem as the bright sparks on here are bound to be able to help
Guest jeffmasson Posted April 25, 2011 Report Posted April 25, 2011 The only thing that stands out as glaringly obvious is that you only wipe the cache etc ( the threee wipes ) before loading a rom not after. if you do it before then after you will wipe the new stuff. give it a another go factory reset/wipe date, clear the cache then clear dalvik cache and then just install a rom using the insatl zip from sd card and see if this makes a difference? i`m sorry i cant be more help but i have installed every rom including stock 1.09 and never had this problem, just bsod a few times :) thank goodness for cwm backup. let us know if you are still getting the problem as the bright sparks on here are bound to be able to help ok so getting closer to getting corvus5 going i redownloaded and italled still got the error but this time insted of giving up i rebooted and hay presto i was in corvus5 so error did not stop the install but when i try to install the modules.zip using cwm it just says installation aborted! are you not ment to use cwm to intall this?
Guest Lukas Zapletal Posted May 1, 2011 Report Posted May 1, 2011 I am running in the same issue on my MOBII. 1) Vega stock ROM 1.09 installed 2) Clowkmod Recovery (tried both V2 and V3 - latest and greatest) 3a) Wiping all three items as you recommend 3b) ZIP installation fails: assert failed:write_raw_image("/tmp/bootimg" , "boot") E:Error in /sdcard/download/Crvus5.zip (Status 7) Installation aborted.
Guest Zebrahead Posted May 1, 2011 Report Posted May 1, 2011 I am running in the same issue on my MOBII. 1) Vega stock ROM 1.09 installed 2) Clowkmod Recovery (tried both V2 and V3 - latest and greatest) 3a) Wiping all three items as you recommend 3b) ZIP installation fails: assert failed:write_raw_image("/tmp/bootimg" , "boot") E:Error in /sdcard/download/Crvus5.zip (Status 7) Installation aborted. Ok, that's an asserion. It basically says, if this fails, stop. What's it's saying is the boot image in the ROM you've downloaded is potentially corrupt as it's failing to flash correctly. What'd I'd suggest is, just to try and download the rom again. Other than that... BE WARNED, THIS IS POTENTIALLY RISKY - I'M NOT RESPONSIBLE IF THIS GOES WRONG In CWM, when you go to flash from sdcard, there's an option about toggling assertions. This will basically toggle whether or not the flashing stops if an assertion fails. If you change the toggle status, it will carry on to flash and ignore the error you got there. This is risky as if there genuinely is a problem, you'd be flashing problematic data - this is not advised. Good luck, Zeb
Guest Lukas Zapletal Posted May 1, 2011 Report Posted May 1, 2011 Other than that... BE WARNED, THIS IS POTENTIALLY RISKY - I'M NOT RESPONSIBLE IF THIS GOES WRONG In CWM, when you go to flash from sdcard, there's an option about toggling assertions. This will basically toggle whether or not the flashing stops if an assertion fails. Nice to know. Thanks! I gave up with that ROM and installed r8. It was giving the same error but it did not stop and its working now.
Guest jeffmasson Posted May 1, 2011 Report Posted May 1, 2011 Ok, that's an asserion. It basically says, if this fails, stop. What's it's saying is the boot image in the ROM you've downloaded is potentially corrupt as it's failing to flash correctly. What'd I'd suggest is, just to try and download the rom again. Other than that... BE WARNED, THIS IS POTENTIALLY RISKY - I'M NOT RESPONSIBLE IF THIS GOES WRONG In CWM, when you go to flash from sdcard, there's an option about toggling assertions. This will basically toggle whether or not the flashing stops if an assertion fails. If you change the toggle status, it will carry on to flash and ignore the error you got there. This is risky as if there genuinely is a problem, you'd be flashing problematic data - this is not advised. Good luck, Zeb I think you'll. Find that's off by default. Ignore that error and reboot and all should be ok.
Guest Zebrahead Posted May 1, 2011 Report Posted May 1, 2011 I think you'll. Find that's off by default. Ignore that error and reboot and all should be ok. If it was off for OP then it would have skipped the assertion ^^
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now