Database Info

[Q] Can't chown/mod /system/bin

i have a samsung intercept and whenever i try to flash a rom i get this error
"E:Can't chown/mod /system/bin (no such file or directory) E:Failure at line 7: set_perm_recursive 0 2000 0755 0755 SYSTEM:bin Error applying update!"
what's causing this error and is there a way to fix it?

Have you rooted your phone? Is it running stock firmware or a custom ROM? What kind of update are you trying to apply? These details are important and can help one of us solve the problem 9 times out of 10.
I need to know these things before I can give you a definitive answer. If you've modified the firmware in ANY way, chances are you'll need to reflash with a stock firmware to apply that update.

Right, sorry. I have stock everything now. I had inxanes kernel installed but I started to get audio popping so I went back to stock. I've tried installing cherry kernel but it just gets stuck at the first samsung screen.

You're in luck. http://www.howardforums.com/showthread.php/1691827-Intercept-free-stock-ROMs-and-apps! that URL contains links to the ROMs plus directions for flashing them. I would use the SWUpgrade ones. Download the one that has both the ROM and recovery.

well the only one that i see that has both the rom and recovery is for sprint and i'm on VM. i will download the stock vm tar and try flashing it through swupgrade.
which custom rom would you recommend for the intercept? when i first had my phone rooted and everything i installed basicROM, but i would always get lots of force closes on apps.
well, the swupgrade doesn't work... i guess. whenever i go to flash it with swupgrade my phone just boots up normally and the patcher just stays at 0%. is it doing this because i already have the stock rom?
so i tried installing inxane's kernel and then installing the stock rom through the custom recovery that's installed. got the kernel installed no problem, but i still get the error in the OP whenever i try to install the stock rom zip i have. i restored my system backup that i have so i am back on the stock kernel and stock rom. i still have the boot image from when i had basicROM installed, but it says everything is stock in the about phone.

Power button should be the last one you press. Hold down the other 2 until it boots into recovery.
Sent from my T-Mobile G2 using XDA App

yes, i know. i get into the recovery/flash menu fine (vol down + cam + power), but whenever i plug in the usb and press start for the flashing on swupgrade, my phone just boots up normally from that screen. sorry for the confusion.

I'm downloading the firmware now. Ill post results. You may have to flash with odin
Sent from my T-Mobile G2 using XDA App

According to some users you need to uninstall and reinstall swupgrade then copy the .tar files from your archive into your swupgrade/models/binary folder. Then boot into recovery again and flash.
Sent from my T-Mobile G2 using XDA App

Can't install any custom roms any longer

I am lost.
I had FireFly 2.05 on my SGS (ATT US version) and was going to update to 2.1. I followed the procedure as I aways do; ODIN 1 click to stock rom, master clear, copy update.zip and rom file and reboot into recovery. This time however I get the following error
E:Can't symlink /system/xbin/su SYSTEM:bin/su
E:Failure at line 14
I checked some notes on this and found out that it might be a currupt file. So I re-downloaded FireFly2.1 again and transfered the file to the internal SD card. The outcome was the same.
Then I copied the original 2.05 version back which I know was fine and I still get the same error. Even after a full stock 1-click and master clear the above error will not go away.
Is my internal SD card messed up? Or am I missing something else?
It's running stock right now and all seems to work fine, but I cannot stand all the bloatware and other crap ATT puts on the phone and really want to try FireFly2.1.
Any help is greatly appreciated.
Thanks.

Did you flash clockwork recovery

Did you root the phone after you flashed back to stock?
Sent from my SAMSUNG-SGH-I897 using XDA App

Agree with DaveyBB - sounds like you are not rooted.
Sent from my SAMSUNG-SGH-I897 using XDA App

You do not need to root on stock just flash clockwork with update zip

The update.zip i use is the current clockwork recovery.
I boot into the stock e2 recovery, then apply cw recovery and update the rom. Never had to root stock before when i update via cw recovery.
I will try to root stock first this time and then apply rom via recovery.
Thx
Sent from my SAMSUNG-SGH-I897 using XDA App

anosis said:
The update.zip i use is the current clockwork recovery.
I boot into the stock e2 recovery, then apply cw recovery and update the rom. Never had to root stock before when i update via cw recovery.
I will try to root stock first this time and then apply rom via recovery.
Thx
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
To install clockwork select reinstall packages twice

The issue is not with cw recovery. I am already in it, but the error that i get is after i click "yes apply this zip"... The script starts to format the system, data, datadata, etc. And then this error shows up after files ate copied
Sent from my SAMSUNG-SGH-I897 using XDA App

Have you tried re download of rom package?

My only guess is that clockwork and the rom are not working well. I would try downloading a different clockwork
Sent from my SAMSUNG-SGH-I897 using XDA App

mcord11758 said:
Have you tried re download of rom package?
Click to expand...
Click to collapse
Done that too.
So just to reiterate...
I had FireFly2.05 running and many other cooked Android 2.1 and 2.2 roms before this. I follow the instrution of the cooks to the 't' on how to update to the newest rom and never had any issue.
This time I downloaded FireFly2.1 and also Phoenix4.5 from the respective cooks and followed the instructions as usual. The issues does not show up until the 'copy files' part of the script is running (formating of the filesystem already passed).
All I can imagine are these:
1) The transfer from the PC to the Phone is corrupt (ruled out the download from the net as even the existing FireFly2.05 rom no longer loads)
2) The internal SD card is messes up
3) There is some configuration change I am not aware off that prevents the install of the cooked rom.

Maybe try to reformat sd through clockwork

Problem solved, kind of.
My desktop PC, which I always use to transfer the files is somehow responsible for the error I get in CWM recovery. I ended up using my laptop to transfer the ROM to the phone and it worked again.
Something is messing up the USB transfer? That seems very odd but I am glad it's not the phone that caused the issue.
If I find out what the issue is with my Desktop I will post again just in case this rather rare issue might happen to someone else.

anosis said:
Done that too.
So just to reiterate...
I had FireFly2.05 running and many other cooked Android 2.1 and 2.2 roms before this. I follow the instrution of the cooks to the 't' on how to update to the newest rom and never had any issue.
This time I downloaded FireFly2.1 and also Phoenix4.5 from the respective cooks and followed the instructions as usual. The issues does not show up until the 'copy files' part of the script is running (formating of the filesystem already passed).
All I can imagine are these:
1) The transfer from the PC to the Phone is corrupt (ruled out the download from the net as even the existing FireFly2.05 rom no longer loads)
2) The internal SD card is messes up
3) There is some configuration change I am not aware off that prevents the install of the cooked rom.
Click to expand...
Click to collapse
One Question:
What method are you using to enter recovery method when you attempt to flash the rom? And what color is your recovery menu (should be green)?
(Don't go into recovery via rom manager. Try entering recovery via your advanced power menu)

bames said:
One Question:
What method are you using to enter recovery method when you attempt to flash the rom? And what color is your recovery menu (should be green)?
(Don't go into recovery via rom manager. Try entering recovery via your advanced power menu)
Click to expand...
Click to collapse
I don't think he's getting into Clockwork via ROM Manager, as he's said multiple times he's using the CWM update.zip; reinstalling packages in 2e recovery to get to CWM.
He's also said he doesn't believe this to be an issue with Clockwork (and I don't either). And I'm also pretty sure we're not dealing with newbie mistakes of Android Recovery vs. Clockwork Recovery.

any chance you're leaving your usb plugged into your cappy while you're trying to flash it?

[Q] Trouble with 2.3.6 update on I9020a.

I've been in and out of these forms for hours now, and I still can't figure this out. I have an I9020a from Fido (Canadian). I flashed the stock ROM & modem from this post (http://forum.xda-developers.com/showthread.php?t=1056062&page=68). When I try to flash the 2.3.6 update through CWM 5.0.2.3 I get the following
-- Installing: /sdcard/7d11404284c0.signed-soju-
GRK39F-from-GRJ22.7d114042.zip
Finding update package...
Opening update package...
Installing update...
assert failed: file_getprop("/system/build.prop"
. "ro.build.fingerprint") == "google/soju/crespo
:2.3.4/GRJ22/121341:user/release-keys" ||
file_getprop(/system/build.prop". "ro.build.fin
gerprint") == "google/soju/crespo:2.3.6/GRK39F/1
89904:user/release-keys"
E:Error in /sdcard/7d11404284c0.signed-soju-GRK3
9F-from-GRJ22.7d114042.zip
(Status 7)
Installation aborted.
Now I know that some people say I need to use the stock recovery, however there doesn't seem to be any way to get that back. The post (http://forum.xda-developers.com/showthread.php?t=1033269) that everyone mentions has dead links in it, so I cannot download the stock recovery from it.
Can anyone help?
Wolfgar2k

Have you renamed the file to update.zip. placed it on the root of the sd ard and flashed it by selecting the install update.zip option in clockwork. You cannot use the flash zip from sdcard option.
Sent from my Nexus S 4G using xda premium

I tried renaming it to update.zip, but got the same results. I tried with Clockwork 4.0.0.2 and 5.0.2.3. Both of these are missing the install from update.zip option for some reason. I also tried to flash a recovery.img file that was supposed to be stock recovery from post (http://forum.xda-developers.com/showthread.php?t=1033269&page=4) but all it did was make the phone go to the screen with the ! in a triangle with the android logo beside it.

Have you been on stock the whole time? These errors usually mean that there is some different configuration than expected on your phone when using an update package. It could be your radio or your recovery and I have read that even different versions of google apps can cause this. I have seen this myself. Your best bet is to flash the full rom package for your I9020A with clockwork recovery to get you to 2.3.6 you can download here. http://android.clients.google.com/p...8148de0d.signed-sojua-ota-189904.0b9c8148.zip You won't receive any errors because it's a full rom package. You will however have to re flash clockwork recovery aftewards.

Had same issue coming from 2.3.4 I was rooted . Flash the full ROM 2.3.6 you shouldn't have to wipe. after flashing you lose cwr and root
Sent from my Nexus S using XDA Premium App

I tried flashing that ROM with CWM. It made my phone go into a boot loop. I even tried using the NAND 2.3.1 backup. That didn't work, nor did it replace my recovery with the stock one. I did manage to flash to a full 2.3.6 ROM that was pre-rooted, though that's not quite what I was going for. I was trying to get back to pure stock with the 2.3.6 update.

Wolfgar2k said:
I tried flashing that ROM with CWM. It made my phone go into a boot loop. I even tried using the NAND 2.3.1 backup. That didn't work, nor did it replace my recovery with the stock one. I did manage to flash to a full 2.3.6 ROM that was pre-rooted, though that's not quite what I was going for. I was trying to get back to pure stock with the 2.3.6 update.
Click to expand...
Click to collapse
2.3.1 was never designed for the i9020a the first release was 2.3.3. A nand backup will never get you to stock recovery. when making a backup it doesnt save a recovery.img because you make the nand using the fastboot flashed clockwork recovery.img.
The link I provided for you is the full rom which is pure stock 2.3.6 for the i9020a Nexus S straight from Google. This is the update presented to me when going from 2.3.3 up to 2.3.6. If you flashed that you are completly stock including radio, kernel and recovery.
After if you want cwm and root back you have to fastboot flash cwm again and then from cwm I flash su.

I am in the same boat as Wolfgar2k. I am also in Canada and have a Nexus S I9020A with Fido. I wanted to ditch CyanogenMod and go back to the stock 2.3.6 version.
I tried installing the build that blowtorch provided (copy to SD card, rename to Update.zip, select "Install from SDCard"). The install completed without error but when I boot the phone, it gets to the loading animation (colourful X-shaped particle system), the animation then freezes and restarts, over and over.
Anyone know what could be going wrong here?

I have (finally) solved my problem. It turns out all I had to do was use fastboot to erase the cache (fastboot -w) and the phone no longer crashed on boot. Tons of thanks to blowtorch for posting that 2.3.6 build, which does in fact work just fine. I have my phone back!
So happy.

Cooper39,
can you guide me how can i do "use fastboot to erase the cache (fastboot -w)" on my nexus .. I am having the same problem
Ahmed

[Q] CM7 / ICS Flashing issues

I soft bricked my phone playing with ICS, I got a JIG and solved the problem
I can now ODIN back to any version and once rooted I can install any samsung based rom, the problem comes when I try to flash aosp both CM7 and any ICS beta
What happens is I select the zip, it runs a script and the phone reboots, I see the AT&T logo and then it mounts the sd card, it says it can't find the zip file.
I've tried Froyo, Eclair, even gingerbread (I know your not supposed to flash cm7 from gingerbread, I'm just running outta ideas) I have froyo bootloaders, I reinstalled them with heimdal. I've also done a master clear and erased the internal sd card
Does anyone have an idea of why this is happening?

Are you trying to install the zip from ClockworkMod?

Most likely, the rom is incompatible with the flash method you are choosing which bricks your phone. I had this happen to me twice from either flashing a rom the wrong way or just trying to flash the wrong rom all together and killing my system, but I ended up telling AT&T Techs that it happened when I tried upgrading to 2.2 to avoid warranty issues and they replaced my whole device with a refurbished unit =]
However keep in mind that they cannot jig your device and you will have to do that yourself to get your data off your device before you try getting a new one via this method.
Possible Solution:
1. If you can, flash cm7 to your device
2. Flash This ICS rom
http://forum.xda-developers.com/showthread.php?t=1363760
If you have already tried this then I apologize, but I hope this helps.

Another problem
Ok, everything I see says I should flash from a captivatemtd recovery, but when I install Rom manager and select captivatemtd, it says their are no offical recoveries for it, I'm currently running cognition froyo 2.2 with froyo bootloaders
Does anyone know where I can manually get the captivatemtd CWM? and how do I install it?

kataishin said:
Most likely, the rom is incompatible with the flash method you are choosing which bricks your phone. I had this happen to me twice from either flashing a rom the wrong way or just trying to flash the wrong rom all together and killing my system, but I ended up telling AT&T Techs that it happened when I tried upgrading to 2.2 to avoid warranty issues and they replaced my whole device with a refurbished unit =]
However keep in mind that they cannot jig your device and you will have to do that yourself to get your data off your device before you try getting a new one via this method.
Possible Solution:
1. If you can, flash cm7 to your device
2. Flash This ICS rom
http://forum.xda-developers.com/showthread.php?t=1363760
If you have already tried this then I apologize, but I hope this helps.
Click to expand...
Click to collapse
I can't flash cm7 either

movielover76 said:
Ok, everything I see says I should flash from a captivatemtd recovery, but when I install Rom manager and select captivatemtd, it says their are no offical recoveries for it, I'm currently running cognition froyo 2.2 with froyo bootloaders
Does anyone know where I can manually get the captivatemtd CWM? and how do I install it?
Click to expand...
Click to collapse
I'll go over my method of installing(I've had ZERO issues flashing from/to any ROM)
1. I FTS/MC using Odin 1 Click. My phone build is 1008
2. Root with 1 click root(I have to do steps 2 and 3 because I do not have 3 button recovery)
3. Sideload and install ROM Manager(Rom manager, and CWM update.zip are in the Sideload zip that's attached)
4. Copy CWM Update.zip and ROM to device. Reboot and install CWM
5. Reboot into recovery and install ROM
Odin 1 Click(If you can use it)
http://dl.dropbox.com/u/12100225/Odin I897UCJF6-final-OCD-REV0.zip
Root 1 Click
http://dl.dropbox.com/u/12100225/Root.zip
Sideload Wonder Machine and ROM Manager
http://dl.dropbox.com/u/12100225/Sideloading.zip
Edit** What is the build number of your phone?

Here's what you need
Just download this rom
http://download.cyanogenmod.com/get/cm_captivatemtd_full-181.zip
And then watch this video!
http://www.youtube.com/watch?v=iBPu-GqM9RE
Flash CM7 using odin
then flash ICS using clockwork mod using the instructions I gave you before.
That's the easiest way I found to do it and that's how I went from stock rom to CM7 rom and then finally to ICS

kataishin said:
Most likely, the rom is incompatible with the flash method you are choosing which bricks your phone. I had this happen to me twice from either flashing a rom the wrong way or just trying to flash the wrong rom all together and killing my system, but I ended up telling AT&T Techs that it happened when I tried upgrading to 2.2 to avoid warranty issues and they replaced my whole device with a refurbished unit =]
However keep in mind that they cannot jig your device and you will have to do that yourself to get your data off your device before you try getting a new one via this method.
Possible Solution:
1. If you can, flash cm7 to your device
2. Flash This ICS rom
http://forum.xda-developers.com/showthread.php?t=1363760
If you have already tried this then I apologize, but I hope this helps.
Click to expand...
Click to collapse
Tried this to the letter still doesn't work, could it be because of rom manager not finding a recovery for captivatemtd, some pages say I need that recovery but it isn't available in rom manager.

Finnally
Finnally got CM7 installed the problem was I had to do the three button boot into recovery twice, the first time updates clockworkmod to version 5.x
Now to try ICS again, wish me luck

Thanks
Thanks for all the suggestions, the tip in the video about flashing the speedmod kernel did help I think, I've successfully flashed
teamhacksung's ICS Port for Captivate (BUILD 9) again.

A couple notes here:
1 when your flashing cm7 from cwm( NOT 3e RECOVERY THOUGH) you need to flash the. Zip file, then reboot system, IT WILL PROBABLY BOOT LOOP, three button back to recovery and flash again, then while in recovery still flash gapps. Reboot and it will install fine. You should ONLY need to do the two time flash the first time going to cm7.
2. When you go to rom manager and choose manual flash overide from hitting the menu button you will get the unsupported recovery, DON'T WORRY about it and hit ok. Then another popup will come up and choose 3.x and it will work.
Sent From My KickAss ATT SGS2 SPORTING CM7

[Q] Samsung Infuse - Can't boot into correct recovery

First a disclaimer: The only reason I opened up a fresh thread on this is because a lot of the existing posts do not answer this question or a bunch of rabbit trails that only repeat and never get to root (no pun intended) of things.
OK simple plan is to Upgrade to ICS and then Jellybean on my infuse.
Phone is rooted to gingerbread (2.3.6) and have confirmed superuser status. Completed this through oden3
Installed modded 3e recovery file into /system/bin (btw there was never a recovery file in this location to start)
I do have a recovery file in the root. If I place my modified recovery file there (and set r/w permissions) it still does not work and is overwritten by the standard recovery file on the next reboot - which leads me to this error when I try to upgrade the ROM
E: failed to verify whole-file signature
E: signature verification failed
I think the problem is I never enter the alternative recovery but it always kicks me back to the standard recovery, which will not allow me to use a custom ROM.
I do have CWM, Root explorer and tried a number of different schemes and apps to boot into recovery but always the same outcome.
I have tried just about all i could see in this forum but still missing something.

You need to use SGS Kernel Flasher to flash one of the custom kernels out there (Entropy's kernel, for example). Stock kernel doesn't give you access to CWM.

That did it!
PharmNerd said:
You need to use SGS Kernel Flasher to flash one of the custom kernels out there (Entropy's kernel, for example). Stock kernel doesn't give you access to CWM.
Click to expand...
Click to collapse
that was the missing piece of the puzzle.
thanks ...