Database Info

Custom rom Samsung Gio s-5660

I hope somebody can help me to solve my problem.
when i flash my custom rom(made with dsixda-Android-Kitchen) i get the error using clockwordmod recovery
assert failed:write_raw_image("/tmp/boot.img", "boot") error in sd card etc.(status 7)
I have this error in cwm log
no mtd partition named "boot"
Any help please..

UP.....
Come on guys i like to make a custom rom.

I'm getting:
E:Error in /sdcard/boot0.8.zip
(Status 0)
Will let you know if I can figure it out. I'd rather use CWM than Odin to flash.

Ok thanks!

Lenovo A! no boot in to recovery or OS

I was in the process of updating the A1 to the OTA ICS update.
I got an error that stated the following:
assert failed: run_program("/tmp/fuse", "system", "/tmp/system.zip")
E:Error in /sdcard/update.zip
(Status 7)
Installation Aborted
it was suggested that i rename the file to update.zip and apply from that. Well i renamed it and went to go back in to recovery by powering on and holding volume down and all i get is a battery icon screen. no recovery.
I was on CWM Recovery 5.0.2.7. I would really like to be able to get back to CM7 since this update to ICS didn't work.

tedhrs said:
I was in the process of updating the A1 to the OTA ICS update.
I got an error that stated the following:
assert failed: run_program("/tmp/fuse", "system", "/tmp/system.zip")
E:Error in /sdcard/update.zip
(Status 7)
Installation Aborted
it was suggested that i rename the file to update.zip and apply from that. Well i renamed it and went to go back in to recovery by powering on and holding volume down and all i get is a battery icon screen. no recovery.
I was on CWM Recovery 5.0.2.7. I would really like to be able to get back to CM7 since this update to ICS didn't work.
Click to expand...
Click to collapse
look into this....
http://forum.xda-developers.com/showthread.php?t=1624979&page=10

Stuck in bootloop and voodoo lagfix, unable to connect via USB

So I decided it'd probably be a good idea to finally upgrade as I was sitting on Emancipation AI So I tried flashing Dark Knight upon first flash everything worked, so I rebooted recovery from "green" to CWM 5.5.0.4 "Blue" I got the rainbow bug but was able to flash again, I then got stuck in the CWM 5.5.0.4 boot loop. I managed to get out of that by flashing Emancipation back but then I've been stuck in between Voodoo lagfix "red" and a bootloop of the samsung loading screen. I am now unable to get the phone out of voodoo recovery. And the kicker is that the DarkNight now gets errors while flashing so It fails to install:
assert failed: getprop("ro.product.device") == "aries" || getprop("ro.build.product") == "aries" == getprop("ro.product.device") == "infuse4g" || getprop("ro.build.product") == "infuse4g" || getprop("ro.product.device") == "SGH-I997" || getprop("ro.build.product") == "SGH-I997" || getprop("ro.build.product") == "SGH-I997"
E:Error in /sdcard/download/I997_Dark_Knight_Infuse_4G_v6.3_beta.zip
(status 7)
Installation aborted.
Click to expand...
Click to collapse
Normally I'd just boot the phone into download mode but for some reason none of my computers are able to recognize the device, so I tried 2 Win 7 x64 machines one sees that something is plugged in but automatically "installs" and empty driver for it even If I manually go through Device manager and try to upgrade to the actual driver but it says the driver is up to date and just reloads the empty driver, the other Win 7 x64 machine doesn't even recognize that the device is plugged in, I've tried to install the driver Via Kies for both the Infuse and the captivate didn't work on either machines I even found a rar named SGH-i997_Infuse4G_USB_Drivers_5_2_0_2.zip that didn't work either, I then proceeded to try to get the phone to be recognized both on a laptop running MacOSX 10.6.5 and ubuntu 11.10 neither found the device either. I used multiple(3-4) USB cords all had the same result.
So any help is appreciated

Does heimdall work at all
Sent from my SAMSUNG-SGH-I997 using xda app-developers app

nope heimdall/odin or anything used to interact with the phone via usb does not work. As no computers will recognize the device. I tried using the drivers manually through windows but kept getting errors. I even tried using the drivers included with Super One Click to no avail.

Try flashing emancipation again...might take two flashes...if that doesn't work the when in red cwm go under advanced and enable or disable voodoo lagfix...which ever its currently set to set the opposite
Sent from my HTC PH39100 using Tapatalk 2

I've tried flashing emancipation multiple times, I have also messed with the voodoo settings I was still stuck in bootloop, I'm going to try it again both ways but I doubt it will change.
EDIT:
Flashed emancipation with
lagfix :enabled
nextboot: disabled
/system lagfix conversion: no
debug: no
to no avail
Now going to try with everything enabled
Re-Edit:
Still stuck on boot

Hmmm...so you can't get any computer to detect it...you tried every port??? I'm really kinda at a lost...maybe your USB port is borked on the phone...idk, best advice I can give is to keep flashing....when the first cm9 was released, I flashed it while on vacation away from a computer...I was in the same situation as you...couldnt get it to boot into any Rom...just kept looping but I could still get recovery...so I just kept trying to flash...after an hour of flashing it finally took one of the flashes and booted me into a gb rom-don't remember which gb Rom...again this was a long time ago...when the first cm9 build was released for us...
I think I wiped everything in mounts and storage except the actual sd card or wherever the Roms were that I was trying to flash...
Sent from my HTC PH39100 using Tapatalk 2

alright yeah I've been flashing the rom constantly for 3 days now under different settings, I'll continue trying but I don't know if it will do anything. :/
EDIT: I also have an error while mounting and formatting /system
that's also why I can't use any backups
it says
E: Can't mount /dev/block/st19 (file exists)
error mounting /system/!

EDIT: I also have an error while mounting and formatting /system
that's also why I can't use any backups
it says
E: Can't mount /dev/block/st19 (file exists)
error mounting /system/!
Click to expand...
Click to collapse
Did you ever fix this?
I'm stuck on a CWM 6.0 boot loop and this is the error I'm getting.

[Q] roms won't flash. build.prop problem?

so my friend screwed up his optimus v. he said he did a factory reset, but im not sure how exactly he went about it.
anyway, now i can only get into his recovery (cwm 3.2.0.0). ive wiped everything but the sdcard, but no ROM i flash will work. Mirage and IHO both say:
assert failed: getprop("ro.product.device") == "thunderc"
and so on...
the overdrive rom says its installed when i flash it, but rebooting brings me back to recovery.
should i be finding a way to edit the build.prop or what?
any help would be much appreciated.

peopleface said:
so my friend screwed up his optimus v. he said he did a factory reset, but im not sure how exactly he went about it.
anyway, now i can only get into his recovery (cwm 3.2.0.0). ive wiped everything but the sdcard, but no ROM i flash will work. Mirage and IHO both say:
assert failed: getprop("ro.product.device") == "thunderc"
and so on...
the overdrive rom says its installed when i flash it, but rebooting brings me back to recovery.
should i be finding a way to edit the build.prop or what?
any help would be much appreciated.
Click to expand...
Click to collapse
There is a option in the Cwm " toggle assert " or something like that. Just toggle it to turn it off and try flashing again.
Also try to verify the md5 of rom to know whether it is corrupted or not.

Problems when flashing custom/official ROM

Hi guys. this is my first post here. I'm brazillian, sorry if I make some language mistake.
Yesterday I tried to install this ROM. My girlfriend asked for it, we have the same phone model (C2104). so I tried to install it in mine, to check if it's good and so on. but I started making mistakes here.
I installed CWM, downloaded the ROM and downloaded gapps. according to the ROM page, I should flash it through fastboot. I didn't pay enough attention and tried to flash it through recovery... my phone got bricked, it wouldn't turn on. it would just keep vibrating if I held the power button. if I connected it to the pc or to the charger, the red led would just keep blinkin.
after a lot of trying & searching I'd found out I should reinstall the stock ROM. so I installed Flashtool and tried to flash a stock ROM with it, but I received the same message every time: "processing of loader.sin finished with errors". then I tried repairing the phone through pc companion and it worked. until 30 minutes ago I was using my phone as if it was brand new. note: when I repaired it through pc companion, my pc started recognizing it as c2105.
earlier this sunday, I tried to flash it through flashtool in fastboot mode (after installing CWM again), but I always received an error message. this time I downloaded adb and fastboot sdk, and I received the same error. then I tried unlocking bootloader, and voila. it worked. but after this my phone got bricked again...
now it shows the SONY logo, but it's frozen on this screen. the only way I can power it off is removing the battery. I can access the recovery (now the cyanogen recovery is installed), but there's nothing I can do there. I tried to install the ROM through the recovery, but it says: "this package is for device: c2105, c2104, c2105, c2104, taoshan. this device is .". I tried pc companion repair again, but it says my phone has a modified firmware and so it can't be repaired through that tool. yesterday I made a stock ROM using this tutorial, but if I try to flash it through flashtool I get the same error I was getting yesterday ("processing of loader.sin finished with errors").
I'm stuck here. I've made a full backup through cwm, but since I can't boot the phone I can't install it again. please help me :crying: I wouldn't mind using stock ROM again, but I've had enough of it, I wanted to use a custom ROM for some time...
EDIT: after some thinking and trying, I've found out that pc companion wasn't working because I had unlocked bootloader. relocked it and could repair my phone. but now I have some doubts:
- is it possible for me to get a TA backup from my girlfriend's phone and restore it to my phone? will it work?
- can you guys help me on installing that ROM?

cJames2 said:
- is it possible for me to get a TA backup from my girlfriend's phone and restore it to my phone? will it work?
Click to expand...
Click to collapse
NO, don't do it will hardbrick your phone.
Edit : for more info about TA go HERE

cJames2 said:
Hi guys. this is my first post here. I'm brazillian, sorry if I make some language mistake.
Yesterday I tried to install this ROM. My girlfriend asked for it, we have the same phone model (C2104). so I tried to install it in mine, to check if it's good and so on. but I started making mistakes here.
I installed CWM, downloaded the ROM and downloaded gapps. according to the ROM page, I should flash it through fastboot. I didn't pay enough attention and tried to flash it through recovery... my phone got bricked, it wouldn't turn on. it would just keep vibrating if I held the power button. if I connected it to the pc or to the charger, the red led would just keep blinkin.
after a lot of trying & searching I'd found out I should reinstall the stock ROM. so I installed Flashtool and tried to flash a stock ROM with it, but I received the same message every time: "processing of loader.sin finished with errors". then I tried repairing the phone through pc companion and it worked. until 30 minutes ago I was using my phone as if it was brand new. note: when I repaired it through pc companion, my pc started recognizing it as c2105.
earlier this sunday, I tried to flash it through flashtool in fastboot mode (after installing CWM again), but I always received an error message. this time I downloaded adb and fastboot sdk, and I received the same error. then I tried unlocking bootloader, and voila. it worked. but after this my phone got bricked again...
now it shows the SONY logo, but it's frozen on this screen. the only way I can power it off is removing the battery. I can access the recovery (now the cyanogen recovery is installed), but there's nothing I can do there. I tried to install the ROM through the recovery, but it says: "this package is for device: c2105, c2104, c2105, c2104, taoshan. this device is .". I tried pc companion repair again, but it says my phone has a modified firmware and so it can't be repaired through that tool. yesterday I made a stock ROM using this tutorial, but if I try to flash it through flashtool I get the same error I was getting yesterday ("processing of loader.sin finished with errors").
I'm stuck here. I've made a full backup through cwm, but since I can't boot the phone I can't install it again. please help me :crying: I wouldn't mind using stock ROM again, but I've had enough of it, I wanted to use a custom ROM for some time...
EDIT: after some thinking and trying, I've found out that pc companion wasn't working because I had unlocked bootloader. relocked it and could repair my phone. but now I have some doubts:
- is it possible for me to get a TA backup from my girlfriend's phone and restore it to my phone? will it work?
- can you guys help me on installing that ROM?
Click to expand...
Click to collapse
Ok you got far x) so now you got cyanogenmodrecovery....
-Download the rom you told (Ressurection) to pc
- Extract Meta-inf/com/google/android/updater-script from it
Open it with word ... Search for lines that looks like that
assert(getprop("ro.product.device") == "C2105" || getprop("ro.build.product") == "c2105" || getprop("ro.product.device") == "taoshan" || getprop("ro.build.product") == "C2104" || abort("This package is for device: taoshan; this device is " + getprop("ro.product.device") + ".");
If you find it delete it...
Then repack it to the zip.... Now you should be able to flash
Sent from my Xperia T using XDA Free mobile app

SdtBarbarossa said:
Ok you got far x) so now you got cyanogenmodrecovery....
-Download the rom you told (Ressurection) to pc
- Extract Meta-inf/com/google/android/updater-script from it
Open it with word ... Search for lines that looks like that
assert(getprop("ro.product.device") == "C2105" || getprop("ro.build.product") == "c2105" || getprop("ro.product.device") == "taoshan" || getprop("ro.build.product") == "C2104" || abort("This package is for device: taoshan; this device is " + getprop("ro.product.device") + ".");
If you find it delete it...
Then repack it to the zip.... Now you should be able to flash
Sent from my Xperia T using XDA Free mobile app
Click to expand...
Click to collapse
tried again right now, following your directions. now I received this error:
"E:failed to verify whole-file signature
E:signature verification failed
Installation aborted."

cJames2 said:
tried again right now, following your directions. now I received this error:
"E:failed to verify whole-file signature
E:signature verification failed
Installation aborted."
Click to expand...
Click to collapse
Oh i see...cyanogen recovery....
Download my fota flasher apk.... Open it as a ZIP ... Look into assets and extract fotatwrp.img ...
Put it on a sdcard and insert it into the phone
Start the phone in recovery and connect it to pc
Download and install " minimal adb and fastboot"
Open it and type:
adb shell
dd if=/storage/sdcard1/fotatwrp.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
then you got my newest recovery... That one should work
Sent from my Xperia T using XDA Free mobile app