Database Info

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?

Rooted i9023, some help needed please!

Ok guys so I have managed to root my i9023 and flash clockwork recovery which was all good, I set about flashing some new roms via rom manager, again, all good.
So now I settle on this cm7 based rom which I love, used anim mod to get some nice transitions, then I used font changer.
All was good, then I decided that the font I was using was a bit ott so I decided to change it again, upon reboot it starts boot looping, bollocks !!!
So I try to get into clockwork recovery, and it seems to have gone back to the stock bootloader, grrrrr
I re flash clockwork, wipe / clear etc... then flash the rom again, but it would not flash, so I went to my backup of stock n flashed that, all good.
I then install rom manager again and flash the rom I liked again, this time no problem, but when it loads up the home button and search button are not working
So i decide on a factory reset, I select wipe everything including sd just to be sure but it comes up "error null"???
So now I wipe the sd manually and then do the reset and it works, ok, I re load everything on from scratch and all is good, but when I installed rom manager it says that clockwork recovery IS NOT installed again
Can anyone here work out from my ramblings WTF is going on???
I dont get why the font changer all of a sudden caused a boot loop, as I had changed font about 15 times with it without issue, also why clockwork recovery will not stick anymore after a reboot, when before it did and I have not changed a thing!
Cheers!!!

Rename install-recovery.sh in system/etc to something else, flash cwm recovery again, this time it'll stick until you install a stock rom again.
Rom manager is causing more problems than it's saving time, hence I don't use it.
Sent from my Nexus S using XDA App

Thanks for the reply, can you go into detail on what exactly I need to do to get clockwork to stick? I still hold noob status!
Thanks!
Also rom manager seems fine, I flashed loads of roms with it with no issue, I also rebooted a few time at least between flashes so I dont get why clockwork suddenly decided to jump ship.
It was the font changer that f&%ked it all up for me, or anim mod (which I wont touch now even tho I miss the wicked transitions).

When using Font Changer, it's better to do a reboot manually instead of selecting Reboot from within the program. That sometimes cause me a boot loop too. But after turning the phone off / on a.k.a. "reboot manually", the phone boots fine.
To elaborate what rentaric said, use Root Explorer and go to /system/etc/, there should be a file named install-recovery.sh. This file is responsible for flashing the stock recovery every time the phone boots. If you rename it to something else e.g. install-recovery.sh.bak then CWM will stick on reboot.

Thanks, but when I get into the /system/etc/ there is not file called install-recovery.sh.
The only .sh in there is init.goldfish.sh
Any ideas???

bump...............

Flash cwm rec and either stock or custom rom.
Stock rom incl the .sh you want.
Sent from my Nexus S using XDA App

I've read on these forums that using Clockwork on the I9023 is a no-go. Serves up incompatible ROMs, etc.
BTW, I'm looking to root my I9023. Can the OP please point me to the method he used.

athani said:
I've read on these forums that using Clockwork on the I9023 is a no-go. Serves up incompatible ROMs, etc.
BTW, I'm looking to root my I9023. Can the OP please point me to the method he used.
Click to expand...
Click to collapse
LINK: http://forum.xda-developers.com/showthread.php?t=1007782
Please read the whole thread, if I had it would have saved me half a night scratching my head...lol

rentaric said:
Flash cwm rec and either stock or custom rom.
Stock rom incl the .sh you want.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Yeah I have a custom rom installed, supercm7, but the install-recovery.sh. that I have been told is causing the problem of clockwork disappearing is not in the /system/etc/ folder, so I am asking if there is anything else that could be causing me to have to re flash clockwork via my pc every time I want to change rom?
I will tell you exactly what happens.
1. I go into rom manager
2. download a rom and choose flash rom from sd card
3. it asked if I want to wipe etc, i select yes
4. phone re boots and I get ! with an android
5. I pull the battery, hold volume up n power and boot / connect to my pc
6. re flash clockwork via SDK
7.the phone then load the new rom on its own
Before it would just flash the rom without me having to install clockwork again.

install-recovery.sh is only there if you're using a stock android rom.
"so I am asking if there is anything else that could be causing me to have to re flash clockwork via my pc every time I want to change rom?"
ROM Manager.
It's not a reliable working tool for ME as I'm changing ROMs/kernels on a regular basis and it might not work reliable the one time you need it.

Thanks for that, I may just sack rom manager then.
Its a shame as I flashed several roms with it without issue.
Oh well, loving this supercm7 so gonna stick with it untill an update comes out.
Many thanks to all who have replied, clicking the thanks buttons now!

I had the same problem but i installed a previus recovery and works fine formeforme
Sent from my Nexus S 4G using XDA Premium App

[Q] problems with rom manager

hey guys a have problems with rom manager.
i was trying to do a backup rom. but rom manager gives me 2 different errors 2 different times.
first it tells me the i need to have cmw v4 and up and the other is it cant mount system so it only backup the bootlogo!!!
how can i fix this

gypsy214 said:
hey guys a have problems with rom manager.
i was trying to do a backup rom. but rom manager gives me 2 different errors 2 different times.
first it tells me the i need to have cmw v4 and up and the other is it cant mount system so it only backup the bootlogo!!!
how can i fix this
Click to expand...
Click to collapse
Backup from recovery

mr mystery said:
Backup from recovery
Click to expand...
Click to collapse
i did that and got the same issues.

gypsy214 said:
i did that and got the same issues.
Click to expand...
Click to collapse
Did you boot into recovery from rom manager? Or by holding power + volume down to boot into the nvflashed version? Make sure you're making backups by booting into the nvflashed recovery.

I've noticed that stock GB and ROM Manager do not get along. I'm forced to boot into recovery to do anything.
Sent from my LG-P999 using xda premium

Personally, I find Rom Manager to be completly useless and doesn't allow you to do anything right. Your best bet is to boot into recovery by holding power and vol down if you want something done right.

Tattooed5150 said:
Personally, I find Rom Manager to be completly useless and doesn't allow you to do anything right. Your best bet is to boot into recovery by holding power and vol down if you want something done right.
Click to expand...
Click to collapse
Agreed I find rom manager totally useless too, I haven't even used it since my mytouch 4g days, no need to with the nvflash recovery, once flashed it is just about fool proof. I never. Ever had a problem. Using it, and to rename my backups I use andro zip from the market and its free, also nvflash gets updated in a timely manner.......great great tool and like I said no problems using it

sarni84 said:
Agreed I find rom manager totally useless too, I haven't even used it since my mytouch 4g days, no need to with the nvflash recovery, once flashed it is just about fool proof. I never. Ever had a problem. Using it, and to rename my backups I use andro zip from the market and its free, also nvflash gets updated in a timely manner.......great great tool and like I said no problems using it
Click to expand...
Click to collapse
ROM Manager works fine on phones where the recovery partition is accessible when the phone is booted into the Android OS. On my Nexus One it works great and flashes recovery to the recovery partition where it is supposed to go.
On the G2X, LG made the recovery partition non-accessible when the phone is booted into the Android OS. So ROM Manager cannot flash recovery directly to the recovery partition. It flashes it to regular phone memory and then tricks the phone into running it when you say reboot to recovery in ROM Manager. Because of this people call this a "fake flash" and is not as reliable as recovery flashed to the recovery partition where it should be. Therefore, it is not advisable to use ROM Manager with the G2X and just use NVFlash to flash Clockworkmod Recovery to the recovery partition where it should be.

[Q] Noob uncertain as to what I need to flash a ROM?

I have been reading all kinds of stuff on flashing ROMS. I don't know if it is really that complicated, as it seems. I have looked at the wikkis at XDA and Cyanogen...there are lots of similarities, but trying to figure out exactly what you need to flash a ROM seems to be anything but straight forward. There also seems to be no absolute SINGLE meaning for some terms.
Do you need to install SDK, or is it already part of something, like Titanium, ClockworkMod or Busybox?
Every time I look at another source of information, I end up thinking that there is an almost infinite number of ways to skin the ROM flashing cat.
I am just looking for a clear linear path to follow.
Rooted sgh-i727R

You have to Root the phone first, if you don't do that then you can't do anything to the phone. Then flash a Clockwork Recovery, and install the ROM.
What phone are you using though?

ZiggyR2005 said:
You have to Root the phone first, if you don't do that then you can't do anything to the phone. Then flash a Clockwork Recovery, and install the ROM.
What phone are you using though?
Click to expand...
Click to collapse
It's a Rooted Samsung GS ll Sgh-727R. I thought it was a bit more complicated than that?? Don't you need to copy the rom to your p.c. 1st?
In one of the wikkis they were also talking about unmounting the SD card etc. Every time I read one" Guide",it conflicts with the next..

Is flashing the ROM as straight forward as the instructions in this link?
And, just to be sure. In the instructions, when they say" SD CARD", do they mean; Download the CM7 & Google apps to the INTERNAL SD, or the Removable EXTERNAL SD CARD?

sdcard usually means the internal sdcard, i.e. /mnt/sdcard
the instructions differ from device to device, because some just can't be flashed another way.
it usually boils down to two methods:
- put the rom on the sdcard, and use a recovery manage like CWM (clock work mod) to flash the rom from the device itself
OR
- install the correct usb drivers on your computer and use a tool like heimdall/odin to flash the rom from your computer
i did not see any link

Dark3n said:
sdcard usually means the internal sdcard, i.e. /mnt/sdcard
the instructions differ from device to device, because some just can't be flashed another way.
it usually boils down to two methods:
- put the rom on the sdcard, and use a recovery manage like CWM (clock work mod) to flash the rom from the device itself
OR
- install the correct usb drivers on your computer and use a tool like heimdall/odin to flash the rom from your computer
i did not see any link
Click to expand...
Click to collapse
Thanks! Would I be correct in thinking, that it's easier to just flash the ROM from the phone?
Sorry, here are a couple of the links that I was looking at
http://forum.xda-developers.com/showthread.php?p=12874680#post12874680
http://www.theandroidsoul.com/cyanogenmod-7-cm7-for-the-att-galaxy-s-ii-skyrocket-sgh-i727/
The HUGE difference between the two instructions, is what was kind of confusing.
One other question... if your phone is rooted, but you still have the stock ROM, will you still be able to update to ICS via OTA once it becomes available?
THANKS!

What counts as easy depends on what you find easy ;-).
I prefer flashing through recovery mode.
Sometimes it is not possible to flash it through recovery and you need odin/heimdall for certain steps (i.e. when your recovery does not allow flashing of unsigned files and you need to flash a custom recovery like CWM).
It is also easier to brick your device by ticking the wrong box in odin/heimdall ;-).
I have never updated a device via OTA, i think you can still receive the OTA update, but will most likely have to root your device again.

Dark3n said:
What counts as easy depends on what you find easy ;-).
I prefer flashing through recovery mode.
Sometimes it is not possible to flash it through recovery and you need odin/heimdall for certain steps (i.e. when your recovery does not allow flashing of unsigned files and you need to flash a custom recovery like CWM).
It is also easier to brick your device by ticking the wrong box in odin/heimdall ;-).
I have never updated a device via OTA, i think you can still receive the OTA update, but will most likely have to root your device again.
Click to expand...
Click to collapse
Vielen Danke

Going to root, am I doing it right?

I am on stock 4.0.4 with a locked bootloader. I want to have root with the stock rom, nothing else just root.
So I am gonna use the tool provided here,
http://forum.xda-developers.com/showthread.php?t=1544940
I have already installed drivers and have the tool downloaded.
Then I would like to flash the stock google 4.0.4 rom that will let me receive OTA updates. Is this the right file?
http://forum.xda-developers.com/showthread.php?t=1569509
Or can I just flash the stock rom from here?
http://forum.xda-developers.com/showthread.php?t=1572307
I heard there are problems flashing stock rom with CWR if the stock recovery isnt removed? Thats why I dont know if I should flash the stock image.
Is the process of flashing rom with CWR recovery the same as with stock recovery?
My phone is the i9023.
Thanks a bunch in advance.

Gambler_3 said:
I am on stock 4.0.4 with a locked bootloader. I want to have root with the stock rom, nothing else just root.
So I am gonna use the tool provided here,
http://forum.xda-developers.com/showthread.php?t=1544940
I have already installed drivers and have the tool downloaded.
Then I would like to flash the stock google 4.0.4 rom that will let me receive OTA updates. Is this the right file?
http://forum.xda-developers.com/showthread.php?t=1569509
Or can I just flash the stock rom from here?
http://forum.xda-developers.com/showthread.php?t=1572307
Is the process of flashing rom with CWM recovery the same as with stock recovery?
Thanks in advance.
Click to expand...
Click to collapse
Baseband version? under about phone

billchen0014 said:
baseband version? Under about phone
Click to expand...
Click to collapse
i9023xxki1.
Sorry should have specified my phone in the OP.

Best way is to do it manually. You can find all of the steps required here. The only difference is that you should be flashing the latest recovery from here and the latest superuser.zip file when flashing with recovery.
Note, unlocking bootloader will cause loss of EVERYTHING on the device that you have put on there (sdcard, apps, data partition, etc).

Harbb said:
Best way is to do it manually. You can find all of the steps required here. The only difference is that you should be flashing the latest recovery from here and the latest superuser.zip file when flashing with recovery.
Note, unlocking bootloader will cause loss of EVERYTHING on the device that you have put on there (sdcard, apps, data partition, etc).
Click to expand...
Click to collapse
You suppose thats better to do manually so I will have latest version of recovery and superuser?
And yes I am aware of the data loss waited sometime to finish all my games now I am ready to lose all my app data.

Harbb said:
Best way is to do it manually. You can find all of the steps required here. The only difference is that you should be flashing the latest recovery from here and the latest superuser.zip file when flashing with recovery.
Note, unlocking bootloader will cause loss of EVERYTHING on the device that you have put on there (sdcard, apps, data partition, etc).
Click to expand...
Click to collapse
Do it this way. The one click is fine but using Android SDK and going through all that will help you in the long run. This way you know the process in case something goes wrong. It may be confusing at first but worth it. It will teach you a lot more than flashing a one click!
I learnt a lot from this and feel much more experienced and capable because of it. I know I will be able to solve any major issues using Android Debug Bridge (adb).

Okay then I am gonna try the manual way and gonna take out time for it. Now I just need to know what do I flash once I have unlocked bootloader and installed CWR?
I just want the stock google rom and receive OTA if nexus S continues to be supported by google.

You won't need to reinstall the ROM if you are currently on 4.0.4. The ROM stays there as-is. Feel free to do your wipes in recovery and reflash stock 4.0.4 through CWM if you must. You flash CWM to your phone and then superuser through CWM.
Steps:
Setup ADB/fastboot
Bootloader --> fastboot oem unlock --> agree
Bootloader --> fastboot flash recovery recovery.img --> this will give you CWM
Recovery --> flash superuser.zip and, if you must, wipe and reflash ICS (flash su AFTER this if done)
Reboot --> bingo
Also note, with stock ROMs it will replace your current recovery with stock recovery on each boot. If you want to keep CWM, delete /system/etc/flash-recovery.sh when you first boot. You'll have to reflash recovery afterward and it will stick.

Oh I was of the impression that unlocking bootloader wipes everything means it wipes the OS as well. That is nice if it's just data and not the OS, dont think I would reflash it if it's not needed.
Can you explain what you mean by will have to reflash recovery? I will have to do that even if I delete that file on first boot? And whats the drawback if I dont delete that file and stick with stock recovery?

As soon as you boot into stock android it will replace the recovery. So if that file is there on first boot, it will replace it while booting and you will be without CWM (stock instead). After first boot you can delete the file (you can reflash a ROM which has this deleted, or delete it yourself from a stock ROM, or even use adb or a recovery-based file manager to delete the file, then you won't have this problem at all) and it will no longer reflash stock recovery, but you would already have the stock one and need to flash CWM one more time to get it to stick. Easiest way is to just flash CWM and delete it within android imo, saves mounting commands and the such.
No downside really. If you need to flash something for one reason or another you'll just have to reflash CWM before you do so. Once rooted, ROM Manager can do this for you within android anyway.

I had already downloaded and installed the drivers from the one click root thread and my computer shows the android adb thing when I connect my phone with USB debugging.
But as you guys suggested I am gonna do the manual way. So do I just skip the installing driver on computer in the part 1 of this guide?
http://forum.xda-developers.com/showthread.php?t=1007782

In my bootloader menu why is it showing my phone as an i9020?? Is it normal?

Gambler_3 said:
In my bootloader menu why is it showing my phone as an i9020?? Is it normal?
Click to expand...
Click to collapse
Because you have a Nexus S with amoled. That's the i9020. The i9023 is SLCD.

DeuXGod said:
Because you have a Nexus S with amoled. That's the i9020. The i9023 is SLCD.
Click to expand...
Click to collapse
He has the i9023 to my knowledge. It is completely normal, though. Bootloader and recovery for i9020 and i9023 series are the same, this can be attributed to the issue with 4.0.3 recovery backlight not turning on.
If fastboot recognises your phone in the bootloader (the fastboot menu), your drivers are installed an working perfectly.

Finally got to the unlock bootloader screen, didnt do it just yet but now I know how to do it.
I must say the guide is a bit outdated, the software has changed quite a bit seems. The most frustrating part was that the fastboot file is actually in the platform tools folder instead of the tools folder which I didnt figure for a while. I will hold off rooting when I have a whole day off because once I lose everything I would be very anxious to get my phone back to normal which will take time.
Thanks for the help harbb, if I have any problem flashing recovery and superuser I will come back for more help.
And yes I have the LCD version i9023.

Btw the guide said the fastboot will be in the tools folder but the tools folder had a read me that "adb has moved to the platform tools folder" this is how I figured to go to that folder and thats where the fastboot file actually was.
Now it says I should put the recovery image in the tools folder so should I do that or put it in the platform tools folder?

In the instructions for the flashing recovery I am not understanding one thing.
6 - Then back on the SNS select Power Off (Reboot also works)
Part 4 - Root
1 - Power ON the SNS
So after flashing recovery I have to reboot? Since I am on stock rom that would bring back the stock recovery so how would I flash superuser then?
If I delete the stock recovery can I still get OTA updates?

fastboot and adb is now in platform tools, that is correct. Easiest way is to put your recovery in there too so you don't have to type in the absolute file path to it, don't put it in tools.
Don't power off or reboot the phone. After you flash recovery go straight into the recovery menu and root, flash custom ROMs, kernels, etc. You can transfer files to flash via the mounts and storage --> mount usb storage menu. After this feel free to reboot.

Harbb said:
fastboot and adb is now in platform tools, that is correct. Easiest way is to put your recovery in there too so you don't have to type in the absolute file path to it, don't put it in tools.
Don't power off or reboot the phone. After you flash recovery go straight into the recovery menu and root, flash custom ROMs, kernels, etc. You can transfer files to flash via the mounts and storage --> mount usb storage menu. After this feel free to reboot.
Click to expand...
Click to collapse
Just wanted to update that I successfully unlocked and rooted. Thanks a bunch mate.

Gambler_3 said:
Just wanted to update that I successfully unlocked and rooted. Thanks a bunch mate.
Click to expand...
Click to collapse
Good work, been wandering what you were up to on this
Hope you enjoy the possibilities.