Related
Hello!
I have a Samsung Galaxy S Captivate previously rooted over a year ago. I was mostly using CyanogenMod for a while, and some time ago, I decided to try out some random ROM (can't remember the name, but it was an unofficial port of ICS).
It had some issues and bugs, so I decided to switch back to CyanogenMod. I've tried installing CyanogenMod 7.2, 9.0 and 10.0
Everytime, I get the following error message:
Code:
Finding update package...
Opening update package...
Installing update...
assert failed: getprop("ro.product.device") == "captivate" ||
getprop.("ro.build.product") || ... (and so on)
E:Error in /sdcard/#whateverpackage#.zip
Status 7
Installation aborted.
*Where "whateverpackage" is the zip/ROM I am trying to install.
Things I attempted to no avail:
1. Toggling asserts. I get the same error.
2. Reflashing recovery-clockwork-2.5.1.2, but I get the same type of error.
3. Installed USB Drivers for Samsung, and attempted to run Odin3 One-Click Downloader (I897UCJF6-final-OCD-REV0.exe), but it isn't responding it seems.
I'm thinking of trying to install ADB and see if I can get the device to properly go into "download mode" and see if Odin responds.
This may be important: When I boot in recovery, the top of my screen shows "CWM-based Recovery v5.5.0.2"
So if anyone knows a straightforward fix to this, or can at least give me rough steps to try/follow, I would greatly appreciate your help.
Thanks for taking the time to read this!
You could have quickly found an answer if you searched "status 7" or "assert failed." It simply means your phone is identifying as a different device because of the ROM you flashed. You can get around this by flashing a kernel appropriate for whatever you're trying to install, so Devil or Semaphore will do. From there, reboot recovery and install the ROM.
korockinout13 said:
You could have quickly found an answer if you searched "status 7" or "assert failed." It simply means your phone is identifying as a different device because of the ROM you flashed. You can get around this by flashing a kernel appropriate for whatever you're trying to install, so Devil or Semaphore will do. From there, reboot recovery and install the ROM.
Click to expand...
Click to collapse
I did look up assert failed, but I couldn't get a clear answer.
I didn't occur to me to look up "status 7"; just seemed like a very cryptic error code.
Thank you for your advice nonetheless. I'll update if the error persists.
Semaphore & CyanogenMod
So, I flashed Semaphore 2.8.0 and then attempted to install CyanogenMod 10 (Android 4.1.2, I think).
Got Status 0.
Tried reflashing Semaphore 2.8.0, and 1.2.6. No progress.
Any recommendations?
I tried to flash CyanogenMod 9 on Semaphore 1.2.6 and got Status 7.
Thanks.
Headless_One said:
So, I flashed Semaphore 2.8.0 and then attempted to install CyanogenMod 10 (Android 4.1.2, I think).
Got Status 0.
Tried reflashing Semaphore 2.8.0, and 1.2.6. No progress.
Any recommendations?
I tried to flash CyanogenMod 9 on Semaphore 1.2.6 and got Status 7.
Thanks.
Click to expand...
Click to collapse
If you would read a bit before doing the flashing you would know that status 0 is from rebuilding the partition. You simply need to flash CM10.1 twice. So it goes like this: Flash CM10.1, reboot recovery, flash CM10.1.
BWolf56 said:
If you would read a bit before doing the flashing you would know that status 0 is from rebuilding the partition. You simply need to flash CM10.1 twice. So it goes like this: Flash CM10.1, reboot recovery, flash CM10.1.
Click to expand...
Click to collapse
I do look up the error. Just no one actually mentioning that until your post.
Thank you for your advice.
I flashed it 3 times (rebooting each time) and I always get Status 0.
More explicitly:
Code:
-- Installing: /sdcard/cm-10.0.0-captivatemtd.zip
Finding update package...
Opening update package...
Installing update...
E:Error in /sdcard/cm-10.0.0-captivatemtd.zip
(Status 0)
Installation aborted.
Side note: I'm on Semaphore 2.8.0 and I used Heimdell to flash it (through Ubuntu).
Any additional thoughts?
Headless_One said:
I do look up the error. Just no one actually mentioning that until your post.
Thank you for your advice.
I flashed it 3 times (rebooting each time) and I always get Status 0.
More explicitly:
Code:
-- Installing: /sdcard/cm-10.0.0-captivatemtd.zip
Finding update package...
Opening update package...
Installing update...
E:Error in /sdcard/cm-10.0.0-captivatemtd.zip
(Status 0)
Installation aborted.
Side note: I'm on Semaphore 2.8.0 and I used Heimdell to flash it (through Ubuntu).
Any additional thoughts?
Click to expand...
Click to collapse
Tried simply booting up?
If that doesn't work, reflash without rebooting recovery.
BWolf56 said:
Tried simply booting up?
If that doesn't work, reflash without rebooting recovery.
Click to expand...
Click to collapse
I tried rebooting the device, but, after shortly showing "At&t", it goes straight to the Recovery screen.
I tried installing CM10 again, but same error.
Just reflashed Semaphore. It always gets stuck on At&t after flashing (for several minutes). Is that normal?
So I've been removing the battery, and putting it back in. Then it goes straight to 'Semaphore CWM Recovery v6.0.2.0'.
My steps from there:
Attempted to install CM10. Status 0 error. Turned phone off.
Rebooted straight to CWM-Based Recovery v6.0.1.5.
Tried installing CM10 from there. Status 0 error.
Rebooted. Right back to Recovery v6.0.1.5.
Tried installing CM10 again. Status 0 error
Tried installing CM9. Phone rebooted midway and got stuck on 'At&t' screen.
Rebooted using 3-key button combo (to get to recovery screen).
Went to Recovery v6.0.1.1. (What the hell is going on?)
Tried installing CM9. SUCCESSFUL. Also installed gapps for ICS while at it.
Booted to CM9 correctly.
Rebooted to Recovery and it was still Recovery v6.0.1.1.
Rebooted back to CM9 properly.
Edit:
Rebooted to Recovery. Updated to CM10.
Noticed that Recovery version changed back to v6.0.1.5.
CM10 seems to be working properly.
Anyone knows why I am getting 3 different Recovery versions?
Note: Sorry for the somewhat long post. I just figured I should tell you everything I am doing step-by-step.
Headless_One said:
I tried rebooting the device, but, after shortly showing "At&t", it goes straight to the Recovery screen.
I tried installing CM10 again, but same error.
Just reflashed Semaphore. It always gets stuck on At&t after flashing (for several minutes). Is that normal?
So I've been removing the battery, and putting it back in. Then it goes straight to 'Semaphore CWM Recovery v6.0.2.0'.
My steps from there:
Attempted to install CM10. Status 0 error. Turned phone off.
Rebooted straight to CWM-Based Recovery v6.0.1.5.
Tried installing CM10 from there. Status 0 error.
Rebooted. Right back to Recovery v6.0.1.5.
Tried installing CM10 again. Status 0 error
Tried installing CM9. Phone rebooted midway and got stuck on 'At&t' screen.
Rebooted using 3-key button combo (to get to recovery screen).
Went to Recovery v6.0.1.1. (What the hell is going on?)
Tried installing CM9. SUCCESSFUL. Also installed gapps for ICS while at it.
Booted to CM9 correctly.
Rebooted to Recovery and it was still Recovery v6.0.1.1.
Rebooted back to CM9 properly.
Anyone knows why I am getting 3 different Recovery versions?
Note: Sorry for the somewhat long post. I just figured I should tell you everything I am doing step-by-step.
Click to expand...
Click to collapse
Actually that's great details, thanks!
Have you tried flashing CM10 from CM9? It will still have to rebuild the partition so 2 flashes will be needed.
BWolf56 said:
Actually that's great details, thanks!
Have you tried flashing CM10 from CM9? It will still have to rebuild the partition so 2 flashes will be needed.
Click to expand...
Click to collapse
Yes sir, I just did that. It works
Thanks for your help.
Just wanted to thank you both for this thread. Totally helped me upgrade my Cappy to CM10.1 today. Thanks!
I wanted to flash custom rom on my galaxy S. I flashed clean rom, then kernel with CWM, but there is a problem. Everytime I try to flash rom it ends with bootloop. I tried cm7, cm10, rootbox, miui 2.4. Every time is the same. It starts installing (only few secodns), then screen becames brighter, then restart and bootloop. I tried different kernels, roms but still same result.
ps. sorry for my english
Hi, here is a great guide to fix bootloops:
http://forum.xda-developers.com/showthread.php?t=1660596
Usually, doing factory reset, wipe cache and wipe dalvik cache before and after intalling the ROM should fix the issue though.
I'm doing all necessary wipes, I can recover from bootloop easly but I want flash custom rom and I can't. Istalling zip lasts few second, not few minutes, there is a problem.
Sorry if this is too basic, but are you using the right ROM for your phone?
of course...
I don't know if I'll be able to help you, but can you please list the exact model of your phone just in case? You can see the different variants here:
http://en.wikipedia.org/wiki/Samsung_Galaxy_S#Variants
It is just GT-I9000. Now I managed to flash CM7.2 but if I want install CM9 or CM10 im getting bootloop and can't enter recovery mode ;o
Sorry, I can't really give you an answer with that information. If you are following the steps in each ROMs thread, you should have no problems patching as far as I know (someone more knowledgeable than me may say otherwise).
Maybe posting the exact steps you are following would help me or others to find out what the issue is.
I'm following right steps. It's not my first phone. I know how it should be but it isn't. Here are my steps:
Flash stock ROM w/ODIN v1.85 - OK
Flash CF-Root w/ODIN v1.85
Wipe Data/Wipe Cache
Phone now rooted OK
Boot to CWM Recovery
Install zip from sdcard
Select update on SDCard (cm-7.1.0 from CM site)
Flash completes in just a few seconds
Phone reboots automatically
Now stuck in boot loop
Remove battery
Go to CWM again and reflash CM7.1 zip
Now i have CM7
Reboot to recovery, facotry reset, wipe cache, wipe dalvik
Flash CM9/CM10, finishes in few sec, reboots, then black screen, can't go to recovery mode ;(((
Flashing stock with odin again...and every time is the same, sometimes when I choose CM10 i see info: "Incompatible Partition Layout" so it may be the reason (something with partition, idk)
My phone has never rebooted like that, so I'm not sure what the problem is. I do know I use ODIN v3.07. I also have CWM 6.0.2.7
Best of luck finding a solution, sorry I could no be of more help.
I think CWM6 would help but I can't find this version for cm7
IGNORE ALL LINKS BELOW, they are for the wrong phone
I don't think it matters what CM you have on your phone, you should be able to upgrade CWM from recovery: Maybe not in i9000...
http://forum.xda-developers.com/showthread.php?t=1843825
Doesn't work in i9000 as far as I can tell: You can also try installing TWRP, which I like better than CWM and have in a different device:
http://forum.xda-developers.com/showthread.php?t=1694617
Finally, and don't take me on this because is just a guess, maybe your bootloader is not working properly? I don't really remember how to do this myself:
You are showing me links to CMW and TWRP for i9001, I have i9000...
You are right, please ignore those links... I do know I patched CWM 6.0.2.7 through ODIN on my phone, so maybe that's the only way. In any case, I'll let you look for the actual links.
Hi fellows,
I need your guidance and expert advice in resolving a situation, I have ran into recently. I was trying to install CM10.1 on my brother's galaxy Note GT-N7000 international version which was running official ICS 4.0.4.
Since, I had experience in installing different ROMs on my Galaxy S2, Nexus 7 and Xperia Arc so I was not worried about it being a big deal. So, I followed the procedure described in this page http://techgoneinsane.blogspot.com/2012/08/installing-cm10-on-galaxy-note-n7000.html?m=1 and used Odin and file from 'speedmod' to gain root access and flash CWM which was successful. Then, as planned, I tried update zip in the CWM recovery for CM10.1 nightly. But, I came across error 'Status 7' installation aborted. This was new to me, so I tried few things like 'factory reset', wipe data etc and even tried installing stock ROM ICS XXLRK which was previously installed but no avail. I tried several other ROMs like stable CM9 and other nightlies but no success. The phone is stuck on the boot Samsung logo with yellow triangle. However, I'm able to go in the recovery and download mode.
Upon doing couple of Google searches, I came to know, quite a number of people have faced this error by I couldn't understand the fix properly so can anyone of you please guide me for the solution. Thanks.
Your help will be greatly appreciated.
perceptorz said:
Hi fellows,
I need your guidance and expert advice in resolving a situation, I have ran into recently. I was trying to install CM10.1 on my brother's galaxy Note GT-N7000 international version which was running official ICS 4.0.4.
Since, I had experience in installing different ROMs on my Galaxy S2, Nexus 7 and Xperia Arc so I was not worried about it being a big deal. So, I followed the procedure described in this page http://techgoneinsane.blogspot.com/2012/08/installing-cm10-on-galaxy-note-n7000.html?m=1 and used Odin and file from 'speedmod' to gain root access and flash CWM which was successful. Then, as planned, I tried update zip in the CWM recovery for CM10.1 nightly. But, I came across error 'Status 7' installation aborted. This was new to me, so I tried few things like 'factory reset', wipe data etc and even tried installing stock ROM ICS XXLRK which was previously installed but no avail. I tried several other ROMs like stable CM9 and other nightlies but no success. The phone is stuck on the boot Samsung logo with yellow triangle. However, I'm able to go in the recovery and download mode.
Upon doing couple of Google searches, I came to know, quite a number of people have faced this error by I couldn't understand the fix properly so can anyone of you please guide me for the solution. Thanks.
Your help will be greatly appreciated.
Click to expand...
Click to collapse
If you are on Speedmod's recovery (which is safe), you can try this:
1) Download the latest CM10.1 kernel and save it to your SD card.
2) Flash it in Recovery (Install zip from sdcard > choose zip from sdcard), then reboot in the new Recovery (advanced > reboot recovery).
3) Do a full wipe (even format preload and system in "mounts")
3) Flash the latest CM10.1 build
4) Flash the 4.2.2 Gapps
5) Do a data wipe / factory reset
6) Reboot
You got a yellow triangle because you flashed an unofficial kernel through Odin. To get rid of it, use TriangleAway.
Good luck!
Solved
Kortxero said:
If you are on Speedmod's recovery (which is safe), you can try this:
1) Download the latest CM10.1 kernel and save it to your SD card.
2) Flash it in Recovery (Install zip from sdcard > choose zip from sdcard), then reboot in the new Recovery (advanced > reboot recovery).
3) Do a full wipe (even format preload and system in "mounts")
3) Flash the latest CM10.1 build
4) Flash the 4.2.2 Gapps
5) Do a data wipe / factory reset
6) Reboot
You got a yellow triangle because you flashed an unofficial kernel through Odin. To get rid of it, use TriangleAway.
Good luck!
Click to expand...
Click to collapse
Thanks a lot man. Issue has been resolved by following your procedure and phone is working all fine with CM10.1 on it. Xda rocks!!!
perceptorz said:
Thanks a lot man. Issue has been resolved by following your procedure and phone is working all fine with CM10.1 on it. Xda rocks!!!
Click to expand...
Click to collapse
You're welcome. Glad I could help . If you feel like it, hit the Thanks button on Chasmodo's first message in the repository (where you downloaded your CM10.1 kernel). He really deserves it. You may also want to do the same on Entropy's first post in the unofficial CM10.1 thread :good: That way, you'll show your support and appreciation :angel:.
I'm a noob I know and yes I watched the noob-video. But I need help! Cuz I'm too dump! So please help me
I wanted to update my Galaxy S Plus to the newest CM 10 (Beta 4) (before it was the Beta 3) over the CWM recovery it suddenly says
"symlinks failed"
"error in /sdcard/cm-10-20130324-invendor-beta4-ariesve.zip"
"(Status 7)"
"installation aborted"
so I looked to the CWM recovery and I saw that I don't have the latest version....okay I downloaded the latest one and installed it over the CWM recovery. The same error .... with friends. Now I got when I went into the CWM recovery: (after I tried to wipe data/factory reset or wipe cache)
"E:Can't mount /cache/recovery/log"
"E:Can't open /cache/recovery/log"
"E:Can't mount /cache/recovery/last_log"
"E:Can't open /cache/recovery/last_log"
I tried to restart the phone...black-screen after the samsung cyanogen mod screen.
Okay
So I tried to flash a older firmware "I9001XXKQ7_I9001DBTKP2_I9001XXKPK_HOME.tar.md5" with Odin. I restarted the phone...nope black screen. I installed the newest CWM recovery again and tried to flash again the CM 10. Black-screen. So I tried the old version of the CM which I had before (Beta 3) -> black-screen and still errors in the recovery mode.
I can still go into the download mode and the recovery mode. The charging symbol is not working when i connect it (just the battery but bot moving)
My device:
Samsung Galaxy S Plus
Provider: Vodafone IT
ROM: CM 10 (Beta 3) installed but not working
Kernel: Phenom 3.2 UV (updated after the symlinks failed error)
I hope some genius out there can help me
And sorry for my bad english...I don't use it often (Italy)
Follow my HOW TO Guide at Bottom till you get to Flash CM 10 and use the one you want
Remember Use PIT and Re-Partition to Flash 2.3.6..then Root then use yours!
Will clear up any errors you may have
Thanks!
Hey! Thanks a lot! I'll try it out and report it if its working :good:
EwOkie said:
Follow my HOW TO Guide at Bottom till you get to Flash CM 10 and use the one you want
Remember Use PIT and Re-Partition to Flash 2.3.6..then Root then use yours!
Will clear up any errors you may have
Click to expand...
Click to collapse
!!!!!!!!
dont download the files there!
i think they are for i9000, but the thread starter has an i9001
!!!!!!!!!
have you tried to flash a recovery like CWM 5.x.x.x via odin? it is stable. i think it is linked in the i9001 development at the CM9 Rom by arco
edit: just found
http://forum.xda-developers.com/showthread.php?p=39640245
Regards
Okay
Okay! I didn't do it yet sooo ... I'll try that one and thanks for the link! :good:
then...?
"have you tried to flash a recovery like CWM 5.x.x.x via odin? it is stable. i think it is linked in the i9001 development at the CM9 Rom by arco"
I flashed the CWM recovery via odin, I could format now tho folders and mount them again, but the recovery always freezes when I wanna format the user data. Why? and what should I do as my next step?
Imanidiot said:
I flashed the CWM recovery via odin, I could format now tho folders and mount them again, but the recovery always freezes when I wanna format the user data. Why? and what should I do as my next step?
Click to expand...
Click to collapse
take your time...
what errors does the cwm 5.5.0.4 recovery shows without doing anything?
try to additionally mount system and data partition (see under <mount and storage>)
then click on wipe data/factory reset in the main menu
Hi everybody I'm new.
My situation is exactly the same, I did the same things, got the same problems... got stuck with no solutions yet if not to send it to samsung assistance.
Flashad many other android phones in the past and never had issues like this... it's a nightmare...
try to additionally mount system and data partition (see under <mount and storage>)
then click on wipe data/factory reset in the main menu
Click to expand...
Click to collapse
Without doing anything the recovery says nothing....just the normal main-screen.
After I mounted system and data I click on wipe data/factory...but then it doesn't do anything. It freezes after "Formatting /data..."
I flashed the FeaMod Recovery v.1.2. based on CWM v5.0.2.7
Imanidiot said:
Without doing anything the recovery says nothing....just the normal main-screen.
After I mounted system and data I click on wipe data/factory...but then it doesn't do anything. It freezes after "Formatting /data..."
I flashed the FeaMod Recovery v.1.2. based on CWM v5.0.2.7
Click to expand...
Click to collapse
I also tried the broodROM RC5, succesfully flashed with Odin but still the same problems as before.
Can't format /data.
Stock-Firmware
I am trying to flash now the latest stock firmware with Odin...hopefully it will work.... Still waiting for other ideas :/
Imanidiot said:
I am trying to flash now the latest stock firmware with Odin...hopefully it will work.... Still waiting for other ideas :/
Click to expand...
Click to collapse
I already did that too but it didn't work...
I'm gonna go to the samsung assistance in the afternoon... :crying:
Well....Nothing is working...Anyone who could help me? ... Or better us..
If my guide is no use to you as its for i9000 : try this HERE
If that helps you in any way let me know.
I did this already... I flashed it with the newest stock-FW but it doesn't do anything...and the stock-recovery can't make a factory reset. It always freezes....
other things that could be worth a try:
try flashing different recoveries - not only feamod... also cwm,...
for me cwm5.5.0.4 works
look: our wiki-page -> un-brick
if all doesnt help you could try to reset all partitions
I tried already a few recoveries...like the CWM or the TeamWin... How can I reset them? Can you give me a link please? ^^
Flash BroodROM RC 5... flash this multiple times without touching any buttons like repartion etc..
After that, wipe system and data via the recovery provided in the ROM.
Then flash the newest stock FW from samsung..
This solved all my issues multiple times xD
thanks for the reply, but my phone is now finally brocked....it doesn't even start....and I don't have any idea what i can do now...
??
So, now Samsung, no Samsung Galaxy S Plus GT-I9001? No nothing. Not even the soft brick image (see wiki)
I have a problem, I try to install the CM11, I did everything I needed to blackrose, I made the partition, put the rom and the gapps on the sd but when I try to install the rom gives me an error saying status of 0, what is success?
you help me? thanks
status 0 means that it has flashed successfully. Have you tried booting it up yet?
I solved a problem, reflash new hboot 280mb, reflash all, and nexus start.thank's