Database Develop

(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] Issues moving from Darky 10.1-3 to CM7.1

Well, I was trying to move from Darky 10.1-3 to CM7.1 oona GT-i9000 and whatever method I have tried I couldn't do so.
1. When I tried flashing CM7.1 directly from Dark Core Recovery (threads show it's supposed to work) I have first encountered some sort of a boot-loop. I see console flashes quick and then it reboots. I have entered CWM recovery mode and reflashed and now the phone starts, with the USIM card inside I have no reception and com.android.phone continuously crashes. Was unable to do much with that.
2. As method 1 failed I have downloaded EZBase's Froyo bootloader and flashed it. There from CWM Recover I have tried flashing but it failed and I'm getting the following:
assert failed: getprop("ro.product.device") == "galaxys" || getprp("ro.beuild.product") == "galaxys"
and it keeps repeating itself, just instead of "galaxys" it says "GT-I9000" and other possible names for an i9000.
Any advice anyone ?

Did you Wipe? (wipe data/factory reset + wipe cache partition)
Also you might have ext4 lagfix enabled. Go to CWM and disable it.
Then try again.

I normally flash the CM7 initial kernel using odin and then only use CWM to flash CM7 nightly or stable.

Problem flashing any rom

Hi all,
I recently flashed an android for the first time, so go easy on me!
I flashed my galaxy note gt-n7000 with the CM10 preview #3 (dated 20th August 2012) with success... but!
When I try to install preview #4 of CM10 (24-08-1012), I always get an error message coming from the updater-script.
It says:
assert failed: getprop("ro.product.device") == "galaxynote" || getprop("ro.build.product") == "galaxynote" ||
getprop("ro.product.device") == "n7000" || getprop("ro.build.product") == "n7000" ||
getprop("ro.product.device") == "N7000" || getprop("ro.build.product") == "N7000" ||
getprop("ro.product.device") == "GT-N7000" || getprop("ro.build.product") == "GT-N7000"
I already figured out that my note's name/product/device has been changed to I9100 (S2 build), so I simply opened /system/build.prop and changed it back to GT-N7000. (settings -> about phone -> model is showing GT-N7000 as it should now). Although, I didn't change ro.build.product because the build.prop said it isn't used anymore :s
Still, while running the zip from cwm (6.0.x.x) I still get the same message and it aborts with status 7.
One thing to take notice: I can't install from SD card, it says it's unable to mount the /sdcard when I try to update from external sd card in cwm. I'm trying to install from internal sd...
I already tried installing another rom without success.
I'm in the dark here, so please light up the way :crying: :fingers-crossed:

selman555 said:
Hi all,
I recently flashed an android for the first time, so go easy on me!
I flashed my galaxy note gt-n7000 with the CM10 preview #3 (dated 20th August 2012) with success... but!
When I try to install preview #4 of CM10 (24-08-1012), I always get an error message coming from the updater-script.
It says:
assert failed: getprop("ro.product.device") == "galaxynote" || getprop("ro.build.product") == "galaxynote" ||
getprop("ro.product.device") == "n7000" || getprop("ro.build.product") == "n7000" ||
getprop("ro.product.device") == "N7000" || getprop("ro.build.product") == "N7000" ||
getprop("ro.product.device") == "GT-N7000" || getprop("ro.build.product") == "GT-N7000"
I already figured out that my note's name/product/device has been changed to I9100 (S2 build), so I simply opened /system/build.prop and changed it back to GT-N7000. (settings -> about phone -> model is showing GT-N7000 as it should now). Although, I didn't change ro.build.product because the build.prop said it isn't used anymore :s
Still, while running the zip from cwm (6.0.x.x) I still get the same message and it aborts with status 7.
One thing to take notice: I can't install from SD card, it says it's unable to mount the /sdcard when I try to update from external sd card in cwm. I'm trying to install from internal sd...
I already tried installing another rom without success.
I'm in the dark here, so please light up the way :crying: :fingers-crossed:
Click to expand...
Click to collapse
Just flash a cm10 safe kernel first before flashing rom, reboot the recovery and then flash away.
Sent From My GT-N7000 Using XDA Premium.

You missed something
sahilarora2003 said:
Just flash a cm10 safe kernel first before flashing rom, reboot the recovery and then flash away.
Sent From My GT-N7000 Using XDA Premium.
Click to expand...
Click to collapse
Sorry, but I think you missed the fact that I am already on the unofficial cm10 preview 3 rom. Meaning I already have a cm10 safe kernel?
Perhaps I am missing something too?

buildprop flash,
Or format in mounts system then reflash a rom. Thats where it is saved. I think you are on a save kernel so I think it should not be an issue.
Edit: Just to be sure you can flash a safe kernel, reboot in recovery and then do above. All at your own risk
Sent from my GT-N7000 using Tapatalk 2

Are you sure?
baz77 said:
buildprop flash,
Or format in mounts system then reflash a rom. Thats where it is saved. I think you are on a save kernel so I think it should not be an issue.
Edit: Just to be sure you can flash a safe kernel, reboot in recovery and then do above. All at your own risk
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
You're suggesting formatting /system and then reflashing another rom (without rebooting in between)?
Could that be the solution? The build.prop file can be found there, how will the updater-script be able to find the parameters it needs if the /system folder was formatted?
Sorry if it's an obvious question (which I think it is), but I'm not yet an android savvy. I've had some experience with linux tho...
Any help is appreciated!

well funny thing is, it will work, try it
Sent from my GT-N7000 using Tapatalk 2

No good!
baz77 said:
well funny thing is, it will work, try it
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
I'm not panicking, but still, I formated /system and tried flashing cm10 preview #4, but it still gives me the aser failed error.
My build.prop is GONE and still it says it can't assert... what gives?

ok then I am suspecting recovery and kernel, Can you flash a different safe kernel, and then reflash the rom?
edit, appears my case, when I had it, it must have been different. I did change kernel in similar case and it worked
Sent from my GT-N7000 using Tapatalk 2

Trying parandroid now
baz77 said:
ok then I am suspecting recovery and kernel, Can you flash a different safe kernel, and then reflash the rom?
edit, appears my case, when I had it, it must have been different. I did change kernel in similar case and it worked
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
I installed cwm 5.8 now, It seems I can't mount /emmc but i'm gonna give it a go...

Got the solution.
Downgrade to GB, root the device and upgrade to cm10 in recovery.
It will work.

Another problem...
sahilarora2003 said:
Got the solution.
Downgrade to GB, root the device and upgrade to cm10 in recovery.
It will work.
Click to expand...
Click to collapse
I tried to install speedmod K3-13, which landed me on cwm 5.8.1.8. I can't get back to 6.0.x because this version screws up the mount /emmc and /sdcard! When I choose install from /sdcard, the content that is displayed is actually my internal storage.
I can't put anything on my internal storage, because my rom doesn't work anymore and I can't connect to my pc...
I've seen the posts about downgrading to GB, but I can't because of the sdcard & emmc screwup..
Some tips & tricks would be helpful. :fingers-crossed:

good one, remember to reboot recovery after flashing kernel.
last resort try flashing a gb rom from pc odin with or without regular pitfile. Flashing takes some time so be patient. If it get stuck about an hour at factorysys you might have case of superbrick, but I am not expecting that.
Sent from my GT-N7000 using Tapatalk 2

I'll try
baz77 said:
good one, remember to reboot recovery after flashing kernel.
last resort try flashing a gb rom from pc odin with or without regular pitfile. Flashing takes some time so be patient. If it get stuck about an hour at factorysys you might have case of superbrick, but I am not expecting that.
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Way to put my mind at ease
Do you have a link to where I can find the correct gb for odin?

selman555 said:
I tried to install speedmod K3-13, which landed me on cwm 5.8.1.8. I can't get back to 6.0.x because this version screws up the mount /emmc and /sdcard! When I choose install from /sdcard, the content that is displayed is actually my internal storage.
I can't put anything on my internal storage, because my rom doesn't work anymore and I can't connect to my pc...
I've seen the posts about downgrading to GB, but I can't because of the sdcard & emmc screwup..
Some tips & tricks would be helpful. :fingers-crossed:
Click to expand...
Click to collapse
Download prerooted GB rom from my sig.
Reboot in Download mode.
Open PC Odin on your PC
Connect your phone to pc via usb cable
Select GB file under PDA tab
Hit Start
Wait for the completion.

Thanks!
sahilarora2003 said:
Download prerooted GB rom from my sig.
Reboot in Download mode.
Open PC Odin on your PC
Connect your phone to pc via usb cable
Select GB file under PDA tab
Hit Start
Wait for the completion.
Click to expand...
Click to collapse
Alright, very good!
So afterwards, I can just reflash through cwm to cm10?
That would be awesome!

selman555 said:
Alright, very good!
So afterwards, I can just reflash through cwm to cm10?
That would be awesome!
Click to expand...
Click to collapse
Yes you can. Just reboot into recovery and flash rom+gapps, do all 3 wipes(Cache/Dalvik/Data) and reboot woaah you are on cm10 now Cheers

Fingers crossed for now...
sahilarora2003 said:
Yes you can. Just reboot into recovery and flash rom+gapps, do all 3 wipes(Cache/Dalvik/Data) and reboot woaah you are on cm10 now Cheers
Click to expand...
Click to collapse
I was on CM10 preview 3, but I just had to go to 4!!!
Especially the fact that the g-sensor didn't work bothered me!
The GB download is very slow though, i'm downloading at 80~800kb/s. It's taking for ages.
Perhaps you should find another mirror for you sig...
I'll let you know how it went

Going great!
sahilarora2003 said:
Yes you can. Just reboot into recovery and flash rom+gapps, do all 3 wipes(Cache/Dalvik/Data) and reboot woaah you are on cm10 now Cheers
Click to expand...
Click to collapse
I've gotten past the factorysys.img and it's now writing nand...
Would it be safe to go to paranoid android from here?

Should be, but follow the procedure from paranoid android thread to the letter. Its in first post of the thread, or in the thread.

selman555 said:
I've gotten past the factorysys.img and it's now writing nand...
Would it be safe to go to paranoid android from here?
Click to expand...
Click to collapse
Yes. Just reboot into recovery and flash rom+gapps and do all three wipes. Time to reboot now.
Sent From My GT-N7000 Using XDA Premium.

Samsung Captivate Multiple issues

So I'm trying to install a ROM onto my Samsung Captivate. I've went through this process multiple times, although not with this phone. Im in CWM recovery (Version 2.x, which is probably the problem), first I realize my ext-SD won't mount. I find a simple work around and load the .zip onto my internal SD. So I try to install it again and and it it has some long error message (I'll post it on here in a few minutes), ending with "Installation aborted".
Any ideas of what I need to do? My only idea is to update recovery but I can't get around to that right now. I'm just trying to avoid anymore roadblocks.
Sent from my Desire HD using xda app-developers app
EXACTLY WHAT IT SAYS ON MY PHONE:::::
ClockwordMod Recovery v.2.5.1.0 SpeedMod ULFK
-- Installing: SDCARD:cm-10-20121004-NIGHTLY-captivatemtd.zip
Finding update package...
Opening update package...
Installing update...
assert failed: get prop("ro.product.device") == "
captivate" I I getprop("ro.build.product") == "ca
ptivate" I I
getprop("ro.product.device")
== "captivatemtd" I I getprop("ro.build.product")
== "captivatemtd" I I
getprop("ro.product
.device") == "SGH-I896" I I getprop(ro.build.pro
duct") == "SGH-I897" I I getprop("ro.build.p
roduct") == "SGH-I897"
E:Error in /mnt/sdcard/cm-10-20121004-NIGHTLY-ca
ptivatemtd.zip
(Status 7)
Installation aborted.

That means you have a device/ Rom file mismatch. However, that seems to be in order since you say you have a captivate and you are flashing the file for captivate. Your build prop must be modified by your current Rom. Try flashing a kernel first, then redoing the installation from the new recovery.
Sent from my SGH-I777 using xda premium

Okay. Quick question, can I flash a kernel .zip using the recovery I have right now?
Sent from my Desire HD using xda app-developers app

Try loading a gingerbread stock rom that has been updated to contain cwm recovery using 1-click package(there is thread with all 1-clicks). If you never had a gb rom before then select a package with bootloader so that you'll have gb bootloader too. Then flash CM10. That should work.

Assert Error

I have a Samsung Galaxy Tab (GT-p1000) thats currently Gingerbread 2.3.6. I restocked it recently with Overcome, and would like to install CM-9.1.0. I've tried flashing CM-9.1.0 several times over the past few weeks and continue to get error
"script aborted: assert failed: run_program("/tmp/updater.sh") == 0
assert failed: run_program("/tmp/updater.sh") == 0"
I always make sure to wipe data, cache, d cache, and I've restocked with the Overcome Kernel a few times as well. I've also tried installing from the SDCard, AND the internally SDCard. I've downloaded CM-9.1.0 from a few different sources as well. No matter what I've done, I'm sitting getting that error.
Ideas anyone?

two things come to mind:
1) GB-stock-safe-v5 is GB 2.3.3 , so why are you on GB 2.3.6? Are you not using Overcome Method?
2) if all fails, you can edit the updater script to remove assert
http://forum.xda-developers.com/showpost.php?p=37595824&postcount=2

arch enermss
priyana said:
two things come to mind:
1) GB-stock-safe-v5 is GB 2.3.3 , so why are you on GB 2.3.6? Are you not using Overcome Method?
2) if all fails, you can edit the updater script to remove assert
http://forum.xda-developers.com/showpost.php?p=37595824&postcount=2
Click to expand...
Click to collapse
Found the solution to my issue! (I did use the Overcome Method, and did flash with the 4.1.0, sorry )
To fix my issue:
Used ADB -
adb shell
mount /dev/block/stl3 /efs
No more error, and CM-9.1.0 installed without issue.

chrisxrussell said:
Found the solution to my issue! (I did use the Overcome Method, and did flash with the 4.1.0, sorry )
To fix my issue:
Used ADB -
adb shell
mount /dev/block/stl3 /efs
No more error, and CM-9.1.0 installed without issue.
Click to expand...
Click to collapse
What is ADB?
How to install/use it?
I just installed GB-stock-safe-v5 ROM (GB 2.3.3) on my tab, i want to install the CM9.1.0 ROM in it..whta should i do now?

use odin and flash overcome kernel 4.0.tar
follow the thread in my signature, there is a guide in PDF format on how to do that.
You will then have CWM recovery.
Use that to flash CM ROM , 3 times (don't ignore this).
The flash gapps for the right ROM.