Status 7 CM7 - Captivate Q&A, Help & Troubleshooting

So I was trying to follow directions at this video http://www.youtube.com/watch?v=mLNv_-sEng4 to install CyanogenMod 7 on Captivate. But it fails after applying CM7. (at 6:44 on that video). It finds the package, opens it, but then errors out, (Staus 7). Heres what I did, and what I downloaded. First I copied "captivate-efsbackup.zip 2011-03-03 159.4 KB" and "update-cm-7-04282011-NIGHTLY-Captivate-signed.zip < 8 hours ago 94.1 MB" from "http://sourceforge.net/projects/teamhacksung/files/captivate/" and downloaded "cm7-captivate-initial-kernel.tar 2011-03-19 3.5 MB" from same website. (on video, file name is "cm7-Captivate-initial-20110304.zip"), I tried twice, and same thing. Heres the status when I try to apply CM7
**************************************
--Installing: /sdcard/update-cm-7-04212011-NIGH
TLY-Captivate-signed.zip
E:no misc partition
Finding update package...
Opening update package...
Installing update...
assert failed: getprop("ro.product.device")== "
captivate" || getprop("ro.build.product") == "ca
ptivate" || getprop("ro.product.board") == "capt
ivate"
E:Error in //sdcard/update-cm-7-04212011-NIGHTLY-
Captivate-signed.zip
(Status 7)
Installation aborted.
**************************************
p.s. First I tried with "update-cm-7-04282011-NIGHTLY-Captivate-signed.zip"

please follow the WRITTEN instructions in the cyanogenmod thread. you are doing it wrong (you never used the initial zip).
please don't open new threads because you are incapable of reading.

oh, my bad... thats where the mistake is, i didnt see the initial, thank you, I will try that later.

one quick questions. instructions say
12. Apply zip from sdcard: cm7-DEVICE-initial-XXXXXXXX.zip
13. Do a factory reset / data wipe!
14. Reboot
15. Install the latest update after a reboot!
on step 14, do I have to boot into the android OS, and then restart into recovery mode, and select updated from sd card, and install the update?

zheka1 said:
one quick questions. instructions say
12. Apply zip from sdcard: cm7-DEVICE-initial-XXXXXXXX.zip
13. Do a factory reset / data wipe!
14. Reboot
15. Install the latest update after a reboot!
on step 14, do I have to boot into the android OS, and then restart into recovery mode, and select updated from sd card, and install the update?
Click to expand...
Click to collapse
yes, you have to botto into android at least once before updating.

There's a sticky in here for these kinds of questions. Do NOT start new threads.

and another one closed. Please do a search before posting.

Related

[Q] Cyanogen Mod 6 won't install on N1

I've updated the radio and the latest stable version of Cyanogenmod 6 won't install. I've tried ROMmanager and Manual install via recovery and always end up with a Status 7, aborted install. What am I doing wrong? I am running FRF91 ROM right now with the latest Radio with no problem, but would at least like to check out Cyanogenmod6 to see what it offers over the Stock Froyo ROM.
Here are the steps I take:
Enter Recovery Mode.
BOOTLOADER
RECOVERY
Which takes me to ClockworkMod Recovery v2.5.0.7
WIPE DATA/FACTORY RESET
WIPE CACHE PARTITION
INSTALL ZIP FROM SDCARD
CHOOSE ZIP FROM SDCARD
Then I navigate to and select:
update-cm-6.0.0-N1-signed.zip
The install starts running, and then I get this error message:
assert failed: getprop("ro.bootloader") == "0.333.2012" ||getprop("ro.bootloader") == "0.333.2012"
E: Error in sdcard/update-cm-6.0.0-N1-signed.zip
(Status 7)
Installation aborted
Then I have to restore my ROM back to FRF91.
Any help will be much appreciated
Looks like you have a new HBOOT.
Here's a guide for downgrading:
http://forum.xda-developers.com/showthread.php?t=726258
HBOOT
I'll take your word for it and try the steps you pointed me to and see if it works. Thanks in advance!
It Works
I followed your instructions and it worked! Thanks.

not able to update my nexus one from 2.1.

hi there,
been trying to update my nexus one which has firmware 2.1update1 installed on it and build number is ERE27.....i have tried manually updating the firmware FRF50-from-ERE27 and have tried other 2.3.3 firmwares....
i have been trying the method of Copying the file onto the SD card and renaming it as update.zip file onto your microSD card.
i keep getting this error:
assert failed: getprop ("ro.bootloader") == "0.33.2012"||
getprop ("ro.bootloader") == "0.33.2012"||
E:error in /sdcard/update.zip
(status 7)
instillation aborted
Please help me...am stuck on 2.1 still.
Read the Wiki.
Execute "unroot/restore" guide, PASSIMG way, with FRG33 ROM.
Then you can root, install custom recovery, and flash rooted (or stock) Gingerbread.
... sorry wrong posting
Hi,
if you are still unrooted, please consider 2 hints (among others):
1. follow the right sequence of the updates starting from ERE27 when using the original update files is required
2. when renaming to update.zip make sure it does not became update.zip.zip
I am short of time atm and cannot provide you more detailed links, so you may look for them here on xda-developers, if you need.
Good luck!

(Status 7) Installaiton Aborted

Installing update...
assert failed: getprop("ro.product.device") == "SCH-I800" || getprop("ro.build.product") == "SCH-I800" ||
getprop("ro.product.board") == "SCH-I800"
E:Error in/sdcard/KhasMek.DJ11.Kleanmod.v3.zip
(Status 7)
Installaiton Aborted
Can,t install rom, does anybody have some simmilar?
bombarder said:
Installing update...
assert failed: getprop("ro.product.device") == "SCH-I800" || getprop("ro.build.product") == "SCH-I800" ||
getprop("ro.product.board") == "SCH-I800"
E:Error in/sdcard/KhasMek.DJ11.Kleanmod.v3.zip
(Status 7)
Installaiton Aborted
Can,t install rom, does anybody have some simmilar?
Click to expand...
Click to collapse
Yes just search in this forum. I had the same problem too. Basically here is what to do
1- download and flash the full firmware JJ4 with pit and partition cheched (this will resolve the csc errors)
Your tab might still get stuck on the boot logo. Turn it off then go to download mode
2- Flash Gingerbread 2.3.3 following Chainfire instructions
Your tab should reboot normally.
Good luck
Sent from my GT-P1000 using XDA Premium App
I, sorry for noob qestion, but I have cdma device I800, this method for gsm device isn,t it?
bombarder said:
I, sorry for noob qestion, but I have cdma device I800, this method for gsm device isn,t it?
Click to expand...
Click to collapse
Yes gsm tab
Sent from my GT-P1000 using XDA Premium App
if I flashed it could it damage my device?I read somewhere about posibility damaging
bombarder said:
I, sorry for noob qestion, but I have cdma device I800, this method for gsm device isn,t it?
Click to expand...
Click to collapse
I actually had the same issue, and have been scouring the forums for days. Unfortunately, I wasn't able to find a solution. I tried following the instructions listed for Unbricking the Galaxy Tab and it worked for about a day.
After that it began generating errors. First my widgets disappeared saying there was a problem, second reboot wifi generated errors and wouldn't turn on, and third reboot was the Verizon Logo. When it was on the VZW logo, it would vibrate once, pause, and vibrate three times. Wash. Rinse. Repeat.
So, if this is what you were dealing with, this is what I did to resolve it. (Warning: I am not a developer, and take no responsibility for what happens should you choose to repeat my steps.)
1.) I noticed it was still on CWM3, tried to reflash Khasmek's Voodoo plus v.5. -Booted into Recovery
-Wiped Data, Cache
-Flashed
Got me out of the vzw loop. Went to boot loop.
2.) Flashed rom (tried K-lean v3 and Khasmeks Aosp and Simply Aosp.
-Copy rom to SD card.
-Boot into Recovery
-Update from Zip on SD
-Flash
Fail. Still a status 7 on install of any given rom. Still displaying CWM 3.0 after kernel flash.
3.) Heimdall with original files.
-Go look it up.
Booted, but a function died on every reboot (Camera, Wifi, Widgets, etc). Noticed that system only displayed 512 RAM. May have flashed incorrect files.
-Verified. Idiot. Downloaded and Repeated with correct files.
Still had same issue with rebooting and losing a function every time.
Still displaying CWM3.0
4.) Got frustrated. Drank a little. Remembered I had a recovery from March.
-Boot into recovery
-Backup and Restore
-Restore
Bingo. Everything seems to be functioning correctly and has been for a few days. Have rebooted multiple times, no issues. Also, CWM is 2.5 again.
Hope that helps.

[Q] Need help going back to stock - can't get past CWM

My daughter's Nook Color is acting up and I would like to return it. Some time ago I installed NookieFroyo to the emmc, but for the life of me I can't return this thing to stock. I have tried the 8 interrupted boots, and I tried using ADB (end Terminal Emulator) to change the boot count but when it reboots it goes into CWM rather than reflash the system partition.
I tried to simply install the update.zip, but I can't get CWM to see the external SD, nor can I get the stinking PC to see the nook so I can install it to the root of the system. I tried to Mount USB storage, but that did me no good. USB debugging is checked, but I am not able to see anything on the PC, even using different USB ports.
I also tried to download the file via my Dropbox account, but there is an error message on the Nook when I open Dropbox that says "Yourdevice has no SD card, or you have your phone connected to your computer, so Dropbox won't work properly." I get this even with an SD card installed and not plugged into the PC. When I try to download a file, I initially get the "file downloading" notification, then "download failed" in just a few seconds.
I am at a loss - anyone got any ideas?
Thanks,
Shack
EDIT: When I open ES File Explorer and try to view the /sdcard/, I get a mesage that says SD Card unmounted or not present. I can explore all the other folders (data, emmc, media, etc.) I can mount sdcard in ES File Explorer, but it says it is an empty folder. I get the same thing when I mount emmc.
EDIT 2: Okay, I finally got the sdcard to mount properly and went into CWM to install the update.zip. However, when trying to run the install I got a crazy error message. It found, opened, and began installing the update, then I got:
assert failed: getprop("ro.product.device") == "zoom2 11 getprop("ro.build.product") == "zoom2" 11 getprop("ro.product.overall.name") == "NOOKcolor" 11 getprop("ro.product.device") == "encore" 11 getprop("ro.build.product") == "encore"
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted.
HELP!?!?!?!
Follow these instructions to make a bootable SD card. Make sure that you use CWR version 3.2.0.1. But instead of installing the 2 .zips mentioned, install this complete 1.3 stock ROM.
http://mrm3.net/nook-color-how-to-install-cyanogenmod-7-1
1.3 ROM: http://dl.dropbox.com/u/30572895/Nook_Color/update-nc-stock-1.3.zip
Huge thanks patruns
Thank you so much for the timely reply and the very helpful links. I haven't been messing with the NC much lately - I have a GTAB for all my flashing pleasure. I had fallen out of touch with the specifics, and this was a good re-education on all the NC goodies.
Perfect timing too as my wife's NC got stuck on the "Touch the Future of Reading" and would not boot either!
Thanks again!
Shack

Getting ICS on the Bell Mobility GT-P1000M

Hi everyone,
I really don't like posting redundant information, but I just had to post something to help my Canadian colleagues...
I have a Samsung GT-P1000M (Bell Mobility Canada version) that I updated to Gingerbread via Kies but then wanted to get to ICS (CM9). I'll be honest I can typically easily filter through web garbage when it comes to knowing what to do but the entire world is so active on Android that I had mass confusion. There's a lot of bad information out there... In my initial attempts I had no issues rooting using SuperOneClick: http://www.androidauthority.com/galaxy-tab-p1000-root-superoneclick-72083/
Then, I installed CWM so that I could try installing the flash CM9 zip file. It would not install due to the assert statement (Status 7), where it was trying to match to a GT-P1000, but mine is an M. So I edited the script inside the zip file and tried again but it ended up going into a continuous loop on Status 7. I tried flashing again but had the same issues.
Anyway, long story short, this is what I would suggest with the M version to get CM9 (ICS). Essentially put on this overcome image so that the GT-P1000M version thinks it's a regular GT-P1000 tablet. There's no real point in rooting as you'll blow everything away anyway. Make sure to back up your stuff:
1) Do what priyana suggests in this post and restock your tablet. This involves starting on Page 6 of this guide. Finding all the files is a bit annoying, but doable. Just try to get them from reasonably trusted sources.
2) Stop following the guide at the end of page 11 to proceed to install CM9. Reboot the tablet into the CWM Recovery by holding the volume up key and power button during boot. Install the CM9 zip file as priyana suggests. Then flash the google apps obtained from goo.im (the whole thing is as easy as installing 2 zip files)
Anyway, I think it was necessary to blow away everything so that the tablet stopped believing it was actually a P1000M. Now ICS is on there and runs beautifully. I know the post is a bit redundant but it is to clear up the P1000M difference. As soon as this thing booted the web worked perfectly, never had to put any network settings in or anything.
Also this gives phone functionality, I just don't know how it will get billed considering I'm on a Tablet Only plan... I guess we'll find out in a few days when my bill comes out. It'll probably be at 25 cents/minute or something. Anyway, thanks everyone!
The overcome files are all well hosted by sos_sifou
http://forum.xda-developers.com/showthread.php?t=1881981
Anything broken, just let him know.
Sent from my GT-P1000 using xda app-developers app
Another Canadian GT-P1000M Result
Just wanted to share my experience trying to put CyanogenMod on a Bell Canada Galaxy Tab (GT-P1000M) for anyone coming across this thread. I had one of these fall into my lap, and being a nexus 5 owner, the Froyo that came stock just wasn't going to cut it.
Step1: Update the 2.3.3
First thing I did was update to 2.3.3 using Samsung Kies software on a Windows machine. Every Root+CWM path I seemed to find was aimed at 2.3 not 2.2. That was painful enough. The only real trick have to make sure to set the device up properly Settings->Wireless and Networl->USB Settings->Kies Mode (or something to that effect, I can't see this menu anymore),
Step2: Root and Custom Recovery
From there I pretty much followed the instructions at wiki.cyanogenmod.org/w/Install_CM_for_p1 for a generic P1000 (skipping the "flash gingerbread" step because I did that with Kies). The CM instructions link you to theunlockr.com/2012/05/07/how-to-root-and-flash-the-clockworkmod-recovery-on-the-galaxy-tab-p1000-running-gingerbread/ for the root and recovery installation step. This was pretty straight forward. All you need is the Odin exe, and the root and recovery tar file.
Now it's rooted and unlocked. You can reboot and make sure the superuser and CWM apps are there to be sure.
Step3: CM9.1
Continuing with the instructions at wiki.cyanogenmod.org/w/Install_CM_for_p1. I put the cm9.1.zip and the gapps zip on the table simply by plugging into my computer. Unplug and reboot into recovery with Volume Up + Power. Wipe. Try to flash the cm9.1 zip and I get this error.
assert failed: getprop("ro.product.device") == "galaxytabb" || getprop("ro.buildp.product") =="galaxytab" ||getprop("ro.product.device") == "GT-P1000" || getpropr("ro.build.product") == "GT-p1000"
E:Error in /sdcard/cm-9.0.0-RC1-p1.zip
(Status 7)
Installation aborted.
Like lucgallant mentions, it seems to be something about this tablet being a GT-P1000M as opposed to just GT-P1000.
Here was my fix:
1. Extract the cm9.1.zip
2. Navigate to \cm-9.1***\META-INF\com\google\android and open the "updater-script" in a text editor.
3. change the part with this:
assert(getprop("ro.product.device") == "galaxytab" || getprop("ro.build.product") == "galaxytab" ||
getprop("ro.product.device") == "GT-P1000" || getprop("ro.build.product") == "GT-P1000");
to this:
assert(getprop("ro.product.device") == "galaxytab" || getprop("ro.build.product") == "galaxytab" ||
getprop("ro.product.device") == "GT-P1000M" || getprop("ro.build.product") == "GT-P1000M");
4. Re-zip the folder
Here I ran into snag #1. The zip I created put an extra folder level in (e.g. cm9.1.zip / cm9.1 / META-INF instead of just cm9.1.zip / META-INF). This wouldn't let me flash the zip. Fixed this and managed to start the flash, when I ran into snag #2. Got stuck in a boot loop (one with the CM logo).
Managed to get back the the bootloader, and for the hell of it thought I'd flash the original zip that would fail on the assert message. Sure enough, that worked. So whatever I did to get stuck in the boot loop do something similar to what lucgallant said about convincing your tablet it's a GT-P1000 and not a GT-P1000M (os something). But I didn't have to do any of the overcome image stuff.
So recap:
Files needed
- Odin3 v1.7
- CF-Root-TAB7_XX_OXA_JQ1-v3.3-CWM3RFS.tar
- cm9.1.zip
- cm9.1_modified.zip (that you modified the updater_script in and make a new zip)
- gapps zip
Step1
- update to 2.3.3 in kies
Step2
- reboot into "download mode" (volume down and power)
- use the odin.exe thing to flash the CF.tar
- reboot into regular mode and make sure superuser and a cwm app are there
- put the gapps.zip, cm9.1.zip and cm9.1modified.zip
Step3
- reboot in recovery (volume up + power)
- wipe and factory reset
- flash the cm9.1.zip and fail on assert (never know, you might get lucky)
- flash the cm9.1.zip and get farther but get stuck in a bootloop
- frantic volume up and power and different times to try to get back into recovery mode
- flash the cm9.1.zip original which will now magically work
- flash the gapps.zip
- reboot
Voila. Worked for me at least.

Categories

Resources