After a long struggle I installed Clockworkmod rec and did all backups and Wiped off the rom.
I just downloaded virtuous_quattro_alpha3_pyramid.zip and tried installing it.
it throws an error "assert failed" with status 7. Am unable to install.
Please provide a solution or suggest any other ROMs for HTC Inc S. This really irritates.
ganapathi said:
After a long struggle I installed Clockworkmod rec and did all backups and Wiped off the rom.
I just downloaded virtuous_quattro_alpha3_pyramid.zip and tried installing it.
it throws an error "assert failed" with status 7. Am unable to install.
Please provide a solution or suggest any other ROMs for HTC Inc S. This really irritates.
Click to expand...
Click to collapse
Why are you using such an old version. The latest version of Virtuous Quattro for the IncS is RC3. Try downloading the latest. Also make sure you have a current version of ClockworkMod installed.
ganapathi said:
After a long struggle I installed Clockworkmod rec and did all backups and Wiped off the rom.
I just downloaded virtuous_quattro_alpha3_pyramid.zip and tried installing it.
it throws an error "assert failed" with status 7. Am unable to install.
Please provide a solution or suggest any other ROMs for HTC Inc S. This really irritates.
Click to expand...
Click to collapse
i had status 7 error with another rom when i used "old" recovery, so first of all - update it
and btw is ur IncS s-offed?
I just unlocked the boooader and installed clockworkmod. I did the backups and wiped off successfully.
Sent from my HTC Incredible S using xda premium
You're using the wrong quattro build! The pyramid isn't for the Incredible S, you need the Vivo- hulkshare. com/pgwu1qvoiyvt (remove space before com)
Grab this .zip and it should solve all your problems (assuming you have S-OFF)
Related
i am using a t-mobile g1/htc dream
i cant not install any new roms i have tried cyanogen mod v5.0.8 but my phone keeps getting stuck on the g1 start up screen after installing the rom ....
and when i try to install cyanogen mod v6.0.0 ... it gives a status 7 error and aborts the installation
i have rooted my phone using the application universal androot... because i cant do it the normal way so i had to use the application..
the roms were downloaded using rom manager premium v2.0.2.6 and i am using clockworkmod recovery v2.5.0.1 ....
and my dream is currently running on the stock 1.6 my first time trying to update
can anyone give a set of instructions on what to do . or upload a video that will help???? please help ...!!!!!!!!!!
i am using a t-mobile g1/htc dream
i cant not install any new roms i have tried cyanogen mod v5.0.8 but my phone keeps getting stuck on the g1 start up screen after installing the rom ....
and when i try to install cyanogen mod v6.0.0 ... it gives a status 7 error and aborts the installation
i have rooted my phone using the application universal androot... because i cant do it the normal way so i had to use the application..
the roms were downloaded using rom manager premium v2.0.2.6 and i am using clockworkmod recovery v2.5.0.1 ....
and my dream is currently running on the stock 1.6 my first time trying to update
can anyone give a set of instructions on what to do . or upload a video that will help???? please help ...!!!!!!!!!!
EDIT: Problem solved!
Hi all,
I just tried to install CWM Recovery on a Samsung Galaxy GT-I9000, and it didn't work.
The phone was (originally) running under Android Froyo (2.2), and unrooted. First of all, I used UnlockRoot to root it, and it worked fine. I checked the root access right after using dedicated apps (rootChecker, sdMaid, etc), to confirm.
Then I wanted to install a ClockWorkMod recovery. I followed this guide (on the CyanogenMod wiki). I downloaded and installed Kies to have the USB drivers installed. Then I downloaded Heimdall (my computer is running under Windows 7) + hardcore CMW Kernel. I booted into download mode, then installed the driver. (Step 2 on the tutorial). Then next step was flashing the kernel. It suceeded, and the phone powered off. Turning it on, it just starts to make endless boot loops. The system won't start running, and it is not possible to access to the CWM recovery menu. But the download mode is still available.
So, does anyone have pointers to help me fix this issue ? i would like to have CMW installed, and then install a custom ROM (the latest Jelly Bean based Cyanogenmod release).
Thanks in advance.
Just try again installing stock Rom with odin
See my post Here
http://forum.xda-developers.com/showthread.php?t=1994759
Hi Donovan,
Thanks for the swift answer. And yes, it definitely worked. I downloaded this stock rom, and I flashed it successfully with Odin v3 1.85. I am running now under Android 2.3.6, but I lost the root access. Rooting it won't be a problem, hopefully. I still have access to the download mode, and to the stock recovery. I'll try once again to dive into the ClockWorkMod Recovery, and then install a Jelly Bean rom.
I'm hitting the thanks button right after posting this.
Thanks back at ya. Cf root you can find here
http://forum.xda-developers.com/showthread.php?t=788108
Dont forget the wiping before flashing jb.
Most times u have 2 flash custom twice.
If first time hangs just pull battery out, get in recovery & flash second time or third if its needed.
If it says install completed then its done
Much pleasure flashing the i9000
Actually, I spoke to fast, the problem just got much worse.
Okay, just after flashing the stock rom (2.3.6), everything was fine. Then I downloaded the latest stable CM10 (direct link).
I booted into recovery mode (CWM Recovery,actually) and I did try to install (i din't not forget wiping data/cache, dalvik and batt stats), but it failed, saying the package was incorrect. I tried many times, copying again and again the zip file, same problem.
Then I downloaded a previous version, CM9. I tried to installed it, and i run into a very weird error, saying an assertion failed when trying to install the package.
Something like;
assert failed: getprop("ro.product.device") == "galaxys" || getprop ("ro.build.product") == "galaxys" ... getprop ("ro.build.device") = GT-I9000 etc...
Click to expand...
Click to collapse
And then installation program aborts (error code 7.)
My assumption, is that it looks like my phone is no longer being considered by a samsung gt i9000, according to the installer. Weird, though...
Now, I still have access to the recovery. But the phone can't boot, as everything was wiped. Much worse, I can switch to download mode, but i can't flash back the stock rom, Odin can't detect the phone (I tried with Odin v3 1.82, 1.83 and 1.87).
I'm getting desperate, any pointers ?
Thanks in advance!
Did u try to flash the custom more then 1 time?
Oh yes, I did it like a dozen of times.And I still get the same error.
Sent from my HTC Wildfire S A510e using xda app-developers app
gti9000 rooting
Hi Donovan, could you help me please:fingers-crossed:
I've purchased a unlocked galaxy s gti9000 and I want to root it. Something I've never done on any phone as I'm a complete noob. I managed to install XWJW1 FIRMWARE. I've now got as follows PDA:I9000XWJW6
PHONE: I9000XWJW1
CSC: I9000XSAJV8.
All the links to the file for rooting seem to be dead. I've found some for rooting XXJVU, But that's not right is it? I would really like to try ICS or Jelly Bean. I must admit I'm nervous about this as it's taken me a while to get a phone as good as this one!! Any help would be greatly appreciated. Thanks in advance
@Nooga:There is a very complete and straightforward guide here (http://forum.xda-developers.com/showthread.php?t=1852546). You might want to take a look at it.
Now can we please come back on my topic ? Thanks!
Sent from my HTC Wildfire S A510e using xda app-developers app
Thanks
Roland_Y said:
@Nooga:There is a very complete and straightforward guide here (http://forum.xda-developers.com/showthread.php?t=1852546). You might want to take a look at it.
Now can we please come back on my topic ? Thanks!
Sent from my HTC Wildfire S A510e using xda app-developers app
Click to expand...
Click to collapse
Thanks Roland will give it a try tonight.
Well, that is now solved. I tried something silly that ended up working fine.
As the cm9-smtd update package couldn't run (because of the assertion fail), I just opened the zip package, then edited the file META-INF/com/android/google/updater-script.
I basically removed the assert statement at the top of the file.
CMW recovery installed it properly, without any err. I now have an ICS based rom (Cyanogen Mod 9).
Problem definitely solved now. Going to make a Nandroid backup.
Thanks all, again.
i have been flashing roms now since january this year. I've already flashed a lot for both the Gio and the Ace.
Now I'm running into this same problem again with several roms:
when I want to flash the rom, it returns me a status 7 error. Why? I don't know. I've tried already so much: md5 checksum, downloading again, formatting my sdcard partition
I have it with many roms (cm 7 blackhawk / firekernel, cm 10.1.1 mardon, cm10 maclaw etc etc).
I would like to find out what the problem is and possibly how I can solve it.
Maybe there is a problem with your recovery install. You could try to install that again.
Try to toggle signature verification in cwm. Or just reflash the recovery.
Sent from my Galaxy Ace GT-S5830 using xda premium
Venomous Viper 119 said:
Try to toggle signature verification in cwm. Or just reflash the recovery.
Sent from my Galaxy Ace GT-S5830 using xda premium
Click to expand...
Click to collapse
should i download a new recovery or the same i already had? (file name: recovery-clockwork-5.0.2.6-galaxyace-fix.zip)
DutchArjo said:
should i download a new recovery or the same i already had? (file name: recovery-clockwork-5.0.2.6-galaxyace-fix.zip)
Click to expand...
Click to collapse
Just download the same file again. I use the same one.
nikwen said:
Just download the same file again. I use the same one.
Click to expand...
Click to collapse
thanks. I've tried this but even reflashing my cwm file returns a status 7 error
but flashing my px-cwm v2.zip recovery completed.
I managed to install cwm 6.0.3.2 (although it still says 5.0.2.6) and still i'm getting all these status 7 errors.
the error is " assert failed". Is it possible that cwm isn't able to "read" the several getprop requests from my phone?
Or should the line in script update be changed with removing the spaces between the getprop for cooper and the getprop for gt-s5830?
DutchArjo said:
thanks. I've tried this but even reflashing my cwm file returns a status 7 error
Click to expand...
Click to collapse
Ok. In that case there is an error with your recovery.
@The Others: Would it help to flash a Samsung Firmware via Odin? Would that replace the recovery?
I managed to install cwm 6.0.3.2 and still i'm getting all these status 7 errors.
the error is " assert failed". Is it possible that cwm isn't able to "read" the several getprop requests from my phone?
Or should the line in script update be changed with removing the spaces between the getprop for cooper and the getprop for gt-s5830?
DutchArjo said:
I managed to install cwm 6.0.3.2 and still i'm getting all these status 7 errors.
the error is " assert failed". Is it possible that cwm isn't able to "read" the several getprop requests from my phone?
Or should the line in script update be changed with removing the spaces between the getprop for cooper and the getprop for gt-s5830?
Click to expand...
Click to collapse
Try it if you know what you are doing.
nikwen said:
Ok. In that case there is an error with your recovery.
@The Others: Would it help to flash a Samsung Firmware via Odin? Would that replace the recovery?
Click to expand...
Click to collapse
Hi nikwen, yes, to flash via Odin will replace the recovery with the stock recovery. Cheers.
Sent from my GT-S5830 with TouchWiz UX 5.0 by NaTHaN
BajoPrimate said:
Hi nikwen, yes, to flash via Odin will replace the recovery with the stock recovery. Cheers.
Sent from my GT-S5830 with TouchWiz UX 5.0 by NaTHaN
Click to expand...
Click to collapse
i've flashed a stock rom with mobile odin.
After that: i've tried to flash the cm10.1.3 rom from mardon. It returned a status 0 error. After that, I've flashed cwm 6.0.3.2 and tried to flash the rom again. Still a status 7 error.
Is it possible that maclaw's cm9 or cm10 have changed something in my Phone which causes that i'm unable to flash anything anymore? I only get status 7 errors. When i follow the suggested steps at XDA to get rid of these errors (read: delete the assert lines in updater script) the status 7 errors are replaced by status 6 errors.
when i'm in cm9 and execute getprop in terminal, the ro.product.build / devide / model = cooper (no gt-s5830).
the label on my Phone (which is located underneath the battery) says gt-s5830.
How do I get rid of the maclaw history and return to the completely Original rom to see if I can flash from there?
DutchArjo said:
i've flashed a stock rom with mobile odin.
After that: i've tried to flash the cm10.1.3 rom from mardon. It returned a status 0 error. After that, I've flashed cwm 6.0.3.2 and tried to flash the rom again. Still a status 7 error.
Is it possible that maclaw's cm9 or cm10 have changed something in my Phone which causes that i'm unable to flash anything anymore? I only get status 7 errors. When i follow the suggested steps at XDA to get rid of these errors (read: delete the assert lines in updater script) the status 7 errors are replaced by status 6 errors.
when i'm in cm9 and execute getprop in terminal, the ro.product.build / devide / model = cooper (no gt-s5830).
the label on my Phone (which is located underneath the battery) says gt-s5830.
How do I get rid of the maclaw history and return to the completely Original rom to see if I can flash from there?
Click to expand...
Click to collapse
Are there differences between Odin and Mobile Odin? If there are some, flashing using the desktop one might help.
Cooper is the codename for our Ace. So that is ok.
I've tried 2 stock roms now. Neither can boot. I've reflashed the 5.0.2.6 cwm recovery because that one is the only one that can restore my cm9 backup. I'm lost... I don't know what to do now because there is simply no way of getting a different rom on this Phone and i would really like to know why.
What did maclaws rom do that f*ck*d up my Phone?
DutchArjo said:
I've tried 2 stock roms now. Neither can boot. I've reflashed the 5.0.2.6 cwm recovery because that one is the only one that can restore my cm9 backup. I'm lost... I don't know what to do now because there is simply no way of getting a different rom on this Phone and i would really like to know why.
What did maclaws rom do that f*ck*d up my Phone?
Click to expand...
Click to collapse
You could send them an email.
Flash stock via PC using odin. You will be stuck in a bootloop. Reboot into recovery & factory reset. Reboot & phone boots. Now, important , you cannot flash custom Roms via stock recovery. Place the cwm 5.0.2.6 zip on sd card. Reboot into recovery , select " install update from sd card ", select the zip file, select yes & reboot. Again reboot into recovery, do full wipes & select " install zip from sd card " & NOT " install update from sd card " & flash any stock based Rom like Touchwiz 5 by Nathan. If you follow this, everything must be fine.
Sent from my Galaxy Ace GT-S5830 using xda premium
nikwen said:
You could send them an email.
Click to expand...
Click to collapse
YEs... I managed to flash px recovery 0.4 (again: I still had to delete the assert lines from updater script). Now I was able to flash the cm 10.1.3 rom from Mardon. Just booted for the first time. Hopefully my status 7 errors are now history... (i don't know if I can restore my cm9 backup from maclaw but we will see).
DutchArjo said:
YEs... I managed to flash px recovery 0.4 (again: I still had to delete the assert lines from updater script). Now I was able to flash the cm 10.1.3 rom from Mardon. Just booted for the first time. Hopefully my status 7 errors are now history... (i don't know if I can restore my cm9 backup from maclaw but we will see).
Click to expand...
Click to collapse
Great.
Do you want to restore it? I prefer 4.2.2.
i prefer not. But it depends on how satisfied I am on this cm 10.1.3 rom. And how many bugs / errors I experience, How smooth/fast it is etc.
When I'm not satisfied, I can Always return to this rom I was most satistied off so far. But I wanted another rom because I have a lot spontaneous reboots when turning on Wifi again....
DutchArjo said:
i prefer not. But it depends on how satisfied I am on this cm 10.1.3 rom. And how many bugs / errors I experience, How smooth/fast it is etc.
When I'm not satisfied, I can Always return to this rom I was most satistied off so far. But I wanted another rom because I have a lot spontaneous reboots when turning on Wifi again....
Click to expand...
Click to collapse
In case like yours a fresh often install helps, too.
nikwen said:
In case like yours a fresh often install helps, too.
Click to expand...
Click to collapse
it might, but it also means reinstalling all my apps again. And I do not want to do that
hopefully, this cm10 rom is satisfying enough. I will then stick to it...
Hello,
Since yesterday I am trying to install a custom rom for the first time.
My phone is Sony Xperia V (tsubasa)
Android 4.1.2
Build 9.1.A.1.140
My phone is botloader unlocked and rooted. However I've never managed to install a custom rom.
I've been trying to install custom roms with CWM4XperiaT_v8i_JB and CWM4XperiaT_v8i_JB, however with both versions of CWM I had the following errors:
at first I have status 7 error, but when correcting using this thread http://forum.xda-developers.com/showthread.php?t=2522762 I then have an istallation aborted error.
I've tried installing several releases of Cyanogen and PAC-AIO with the same error messages everytime.
If anyone has another method for flashing roms that bwould be helpful.
Has anyone an idea ?
Thanks in advance.
tanukikoopa said:
Hello,
Since yesterday I am trying to install a custom rom for the first time.
My phone is Sony Xperia V (tsubasa)
Android 4.1.2
Build 9.1.A.1.140
My phone is botloader unlocked and rooted. However I've never managed to install a custom rom.
I've been trying to install custom roms with CWM4XperiaT_v8i_JB and CWM4XperiaT_v8i_JB, however with both versions of CWM I had the following errors:
at first I have status 7 error, but when correcting using this thread http://forum.xda-developers.com/showthread.php?t=2522762 I then have an istallation aborted error.
I've tried installing several releases of Cyanogen and PAC-AIO with the same error messages everytime.
If anyone has another method for flashing roms that bwould be helpful.
Has anyone an idea ?
Thanks in advance.
Click to expand...
Click to collapse
If deleting the "asserts" command from the updater-script didn't work for you, than, in CWM, go to "Advanced" and then "Show log", and get the exact error for when it fails, that way you can see what/where exactly it's failing.
After checking the logs it appears that the format of the partition is not recognized. It also appears that the dalvik wipe fails before that. I have to investigate why the dalvik fails.
Sent from my LT25i using xda app-developers app
tanukikoopa said:
After checking the logs it appears that the format of the partition is not recognized. It also appears that the dalvik wipe fails before that. I have to investigate why the dalvik fails.
Sent from my LT25i using xda app-developers app
Click to expand...
Click to collapse
Try CWM v7.