[Q] arc s into boot loop - Xperia Arc Q&A, Help & Troubleshooting

I have bought a new arc s recently, and it is still in warranty. I rooted it with stock rom 4.0.2.A.0.58 without unlocking the bootloader, since I don't want to loss warranty.
I want to do some mod about the battery in status bar. While I was copying 3 files into /system/framework:
framework.jar
framework-res.apk
android.policy.jar
the last file cannot be copied, since I used a different file browser and it prompted for file replacement.
Then my arc s just keep rebooting, and there is nothing I can do.
When it starts and show the logo, I found that I can run 1-2 adb command before it reboots again. However running su causes segfault.
Can anyone help me? If possible, I do not want to unlock the bootloader. If that isn't possible, is that I can flash original rom (given I haven't unlock bootloader yet)?
Thank you very much.

Do you have a CWM back up? If so then restore using that? If not, then download the stock firmware (ftf file) from somewhere on the xperia arc forum and then flash the firmware using the flash tool. ( Hold the back button and plug in the usb cable and youll get a green LED light then find the file on the flash tool and flash it

OP, as a precaution, framework-res.apk should always be pasted last in /system/framework folder, otherwise it will really cause bootloop when you paste it early than other files.

Run a Firmware repair using Sony Ericson PC Companion.

Thanks a lot.
I tried the PC companion, but can't get it to work. Maybe I need to press back key while plugging the usb cable?
I used flashtool, and just restored the /system and without wiping the data or cache. Everything works as before, and all the apps and data are still here, except I need to root again. I can still use trackID.

Related

BIG problem!! please help (no sd-card, no usb-connection AFTER recovery image update)

hey guys,
once every serveal months i check for updates for my rom, my recovery, and some apps.
yesterday i wanted to update tp the latest recovery (1.52)
now, the phone connected, driver was installed correctly (windows 7 32-bit)
i used the adb commands as posted in the recovery topic.
now it updated it, but after a few minutes using and wiping the phone, the usb-connection will not come to live (in any way, not even a "unknown device") and when the phone booted it gave a message: "SD removed, please place sd-card." while it has a 8 gb on there. luckily i backed up all data i needed from the sd before i flashed. so i used recovery to recreate partitions and wipe sd. but nothing works anymore... when i select ANY option in recovery wich needs SD access it immediatly gives errors.
also tried a nother microsd of 1 gb which did also not work...
about the usb-connection, it also does not work in Recovery.
but in the bootloader, it installs without any problems the well known "My HTC" device. using fastboot to boot to recovery image works, but again: no usb connection
please guys... help me... without sd-card i find my phone completely useless. (because of many documents and pictures for my work.)
I've had this problem and I had to send my Hero for repair, but it could be difficult if you have custom software in there, thry to flash original rom. Not sure though if it can be done through fast boot.
Also if you have to send it back, pretend to be an idiot and say it just went wrong. "I didn't do anything" could work.
Use fastboot to revert to a stock ROM (update.zip)
This sounds very similar to this issue on Modaco - http://android.modaco.com/content-page/299174/no-adb-no-sd/
Still ongoing, as I (pulser) am trying to guide the OP through making the goldcard (need to find another android phone to do this) and then we need to try an RUU somehow???
adwinp said:
Use fastboot to revert to a stock ROM (update.zip)
Click to expand...
Click to collapse
ok, and how?
thanks for reply.
i was thinking of letting it be repaired, but as you all say, unlocked spl, recovery image, custom rom. it does not look so good when they disver that.
but i am a stupid guy, so pretending to be stupid should be easy for me
If you are just interested in getting it back to stock for returning under guarantee to HTC, here is what I would suggest.
(No guarantees, as I haven't had to try this, and won't, for obvious reasons)
Get the stock RUU file from the hero that you have. I would recommend the oldest one that is available for you. (eg. a 1.73 one).
DISCONNECT your phone, and run the exe file(Yes, sounds strange, but bear with me).
Wait till the splash screen for the RUU is up, asking you to accept the EULA etc.
Now browse in my computer to your temp directory (C:\Users\Username\AppData\Temp in Vista/7, C:\Documents And Settings\Username\Application Data\temp in XP)
Sort the folders/files by date modified, and the most recently modified (or one of the most recently modified) folder should contain the RUU stuff. Inside a subfolder is a file called rom.zip. Copy this file to the desktop or another safe place. Once file is copied, close the RUU.
Now get your phone plugged in and booted into fastboot. (hold back + power)
Then use the command
Code:
fastboot flashall C:\Users\Username\Desktop\rom.zip
No guarantees, but it should get you back to the stock recovery, system and boot (NOT HBOOT or SPL, the actual boot.img that android uses to boot the kernel)
can i also flash custom rom with fastboot? to test if something is wrong with the rom?
That would depend on what version of SPL/HBOOT you have. If it is security off, then maybe. Otherwise I doubt it. You usually need an original, HTC signed file to flash using that method.
Feel free to give it a go, but I don't think it would work.

[Q] I need to restore my original build.prop file

Hi all,
Okay, so I tried to mess with the build.prop file in order to get Netflix. I made a copy of the original file. I also have a backup using the Clockwork recovery mod. I tried restoring the file via Root manager but I must have deleted it because the phone will not start. The Motorola logo shows but then the phone goes into a dimly lit gray blank screen. I can go to the bootloader by pressing start and up on the volume switch. How can I access the system folder so I can replace the build.prop file? Do I use RSDlite or SuperOneClick? I have the OTA 2.2 Froyo - no ROMS. Is there a file manager app so that I can access the phone files via my pc? Do I have to flash?
Thanks!
If you cannot access the adb shell anymore and the phone cannot start, the only way I know is to flash it. It's possible to can send build.prop back to it's location, but you cannot access to it under bootloader

Boot Loop stuck in Animation help.

Hey everyone. I know there are already a few threads with boot loop animations, and am having difficulties finding the same situation as what I'm going through. Here is what the phone used to have before it randomly started looping:
Rooted - with Stock rom, using ClockwordMod Recovery 5.5.0.2
Used Go Launcher Theme ( if that even matters )
No additional roms installed or anything, the phone is 3 months old.
Ok here is where I'm stuck. I understand I should reflash somethings like recovery image or something, but I'm stuck with one big problem. My computer and phone don't recognize using the USB mount.
The message I get is called "Unable to open lunfile ( no such file or directory)
Here's what screens I can get to:
1. Hold vol up/down while holding power ( the little android with its belly open, and the options Start - Restart Bootloader - Recovery mode - Power Off )
2. Hold vol down - ODIN mode, with the START option only
I can access WMD recovery and factory reset, Try to install my old backup, nothing works at all in that area, no matter what I do.
Can someone advise me a step by step way of getting my computer to recognize my phone, so that I am able to do fastboot, or reflash, or anything to get my phone working again. I can't access my internal memory at all.
It's even possible that I've read too much, and my frustration is getting in the way, if so I apologize! Some guidance would be greatly appreciated!
Thanks in advance of course! I need my phone for business!
Cheers,
Install the drivers on a computer then use fastboot oem unlock. Or just factory reset it from within recovery.
Sent from my Galaxy Nexus using Tapatalk 2 Beta-4
Try my siggy.
I'm not sure about the exact error:
But the link there will get you the correct drivers.
Also, as stated...try to factory reset.
You'll lose your apps/data that way though =/
Hopefully you can get the driver installed and get your computer to recognize.
If so, follow this to back up your apps:
http://forum.xda-developers.com/showthread.php?t=1420351
Have exactly the same setup as you (rooted/stock/CWM) and had the animation bootloop - animation would just loop until a battery pull.
Only thing that solved it was a factory reset from recovery. Been working fine for the 4 weeks since. No need for any reflashing etc. Titanium recoveries have all worked fine as well. Didn't try my Nandroid backup as I thought that may still have the 'fault' built in.
I had a boot loop for every from I tried to flash...wat fixed it was before flashing u need to wipe system data and wipe the cache in the recovery...ie a clean install...then every rom I tried worked...so I think ur missing that crucial step coz it worked for me
Sent from my Galaxy Nexus using Tapatalk
Hey guys, as stated above I've done numerous factory resets, it still seems to boot. I will for sure try to get the drivers installed so my phone is recongised by the computer, but would need step-by-step assistance when doing fastboot, or whatever the next step is.
Looking for more help though! Keep em coming!
?
Any other ideas?
Thanks!
Ok guys, so here's where I'm at now. I've used Jubakuba's sticky link, located here:
http://forum.xda-developers.com/showthread.php?t=1529058
Everything is able to be recognized up to the point where it says "Put the su.zip on your phone."
Since I cannot access my phone contents, since I keep getting this "Unable to open lunfile ( no such file or directory), it does not allow me to add anything to my phone.
I re-installed CWD as stated in the list of things to do, and all that went well. But I have the same issue, I tried factory resetting all that. erase cache, and still stuck with the same issue.
What's my next step now peeps? Looking for a quick answer as I have time to do it tonight!
Edit***
Just tried this trick: but it says it does not recognize the device?? what is going on! Please help someone! Thanks!
Panic Section! (Something is Wrong)
Q: My phone won't boot!
A: The easiest option is to get into recovery and restore a nandroid using the above guide (pull battery to put phone in an off-state if needed).
However, more advanced options are available if you don't have a nandroid available (You're naughty).
Do you have another rom .zip available on your SD card? If so, simply use the above guide for installing a rom to get you booting again.
If not, you can download one on your PC. Boot into fastboot (the green Android with open chest menu).
Move the .zip to the C:\android-sdk-windows\platform-tools folder.
Open ADB.
Change the NAMEOFZIP.zip below to the correct file name...and perform the action.
Surely your computer recognizes your phone. Otherwise how were you able to unlock the bootloader and flash the recovery?
And I've never seen that error message before. It doesn't even make any sense to me. Where are you seeing it? On your phone or on your computer? And in what context? What are you trying to do when it shows up?
If your phone isn't booting I'm not sure that you can copy any files to it yet. (Maybe you can use adb in clockworkmod? I'm not sure) What I do know you can do is flash the stock ROM and start over.
Download the image from Google here:
http://code.google.com/android/nexus/images.html
Here's a instructions for the GSM version:
http://forum.xda-developers.com/showthread.php?t=1366806
For the Verizon version, I can't find the thread at the moment but you just replace the filenames and also there's 2 radios to flash so:
fastboot flash radio *filename*
fastboot reboot-bootloader
fastboot flash radio-cmda *filename*
"Unable to open lunfile ( no such file or directory) appears on the phone, in CWD mode, when trying to attempt "mount Usb" to be able to access my internal storage .
I am attempting your thoughts right now.
I will post with results
Ok I tried to do this step. This is the outcome I received on the computer after even typing the first step:
'fastboot-windows' is not recognized as aninternal or external command, operable program or batch file.
A thing to stress, I'm not sure how to do step 1: 1) Take a Nandroid Backup if you have CWM installed.
EDIT***
GREAT NEWS!
used this setup!
http://android.modaco.com/topic/348161-01-feb-r4-superboot-rooting-the-gsm-lte-galaxy-nexus/
and it worked!
Thank you everyone! Going to play with my phone and make sure it all works!
Macinshak said:
Ok here is where I'm stuck. I understand I should reflash somethings like recovery image or something, but I'm stuck with one big problem. My computer and phone don't recognize using the USB mount.
The message I get is called "Unable to open lunfile ( no such file or directory)
Click to expand...
Click to collapse
the problem is when that happen?? when ur phone is booted and u plug the usb cable to ur pc? or when u are under recovery and want mount the usb mass storage? the second one doesn't work

System partition, Internal SDcard issue?

Hello.
I am writing here as i am hoping that one of You experienced android users will be able to help me to fix my phone (i8150).
I am rather new to android and so far i have been following instructions very carefully and it wasn't the very first time i was flashing rom.
I did rooted my phone, flashed CWM Recovery via adb, used titanium backup, root explorer etc. Also its been long time since i started using Kezra V4 rom with ICS theme, unmodified vold.fstb. I never ever had any issues with the phone or rom.
To make things as clear as possible i will start with the brief info on what i did to my phone last week.
Last weekend (a week ago) i did a fresh install of Kezra v4 rom with ics theme, original vold.fstab, root explorer and launcher pro (placed in system/app).
Flashing process went fine, no errors in CWM (and yes i did wipe dalvik, cache, formatted system). Several apps were restored with titanium. Phone and rom were working as intended, no signs of slowdowns, errors etc.
Couple days latter i decided to add 1 ringtone and 1 notification sound. Both are ogg files and were placed to system/media/audio/ringtones and notifications. I did remember to mount as r/w change permissions and remount it as r/o. I rebooted phone once but i didn't see new ringtone or notification sound on the list so i rebooted it again. After second reboot the phone booted without any problems but once the system was loaded touch screen stopped to respond and the phone froze. I rebooted it again and this time everything went back to normal.
Yesterday i tried to copy new Kezra rom to my INTERNAL sdcar in order to flash it with CWM. But instead of that i stumbled upon a problem that is beyond my knowledge and comprehension. I DID NOT FLASH ANYTHING AT THIS POINT AS I LOST ACCESS TO CWM
- CWM Recovery disappeared - when i am trying to boot to CWM my phone turns off. There is very very very quick flash of the screen showing recovery but that is it.
- when copying 270mb rom to INTERNAL sdcard it stops at 10% with message that the file can not be read
- when copying smaller files, files are being copied from pc to phone but once the phone (usb storage) is disconnected from pc the files that were copied to internal sdcard are not there as if they were never copied
- i can copy files from external sdcard to internal sdcard with rootexplorer but after rebooting phone the files are gone from internal sdcard
- i can install any app from market or from sdcard but after rebooting, the installed app is gone, it doesnt exist in data/app, the cache files on internal sdcard are gone as well and the installed app is not on the list
- i can take pictures and if they are saved to internal sdcard they vanish after rebooting phone
- if i change any settings of the phone (volume, brightness, wifi settings, any settings) after rebooting phone the settings that i changed are reverted to the state from before rebooting
- i did try to delete those 2 files - ringtone and notification sound from the system/media/audio/ringtones and notification but after rebooting the phone they are still there not deleted (i do remember abot mounting r/w r/o and permissions)
- after formatting internal usb storage (settings/storage/format usb) and rebooting phone all the files are there - as if it was not formatted at all
- after formatting internal usb storage from pc and rebooting phone all the files are there - as if it was not formatted at all
- after "factory reset data" and rebooting phone nothing has changed as if it has not been reseted
- i tried to update superuser binary (my binary is 3.0.3) via wifi - there is new ver 3.0.3.2(ok), update(ok), downloading(ok),
gaining root(ok),remounting /system as rw (ok), md5sum(ok), changing file mode to 06755(ok), moving su (ok), checking md5sum(ok),
remounting /system as ro(ok), installed ver 3.0.3, update failed - superuser message -> "this updater cannot update the su binary on phones that have some kind of write protection on the system partition like S-ON"
Now i guess you are wondering if the phone works. Yes it does.
- it is eu phone bought in England and used in England
- the phone is not assigned to a network carrier, it is not locked in any way - network lock (off), network subset lock (off), SP lock (off), CP lock (off)
- I can make/receive calls and messages
- wifi, g3, tethering, bluetooth, gps, camera etc. are working fine
- all the applications including new apps are working fine as long as i don't reboot phone.
- I don't experience any slowdowns, crashes or freezes
- I have access to system files via root explorer, the phone is rooted
- i don't get any messages that file system is write protected
- rumdump works
- download mode works
Here is what i tried so far:
- flash CWM Recovery via adb but after rebooting i still have no access to recovery (no errors in adb - process completed)
- flash original stock recovery via adb but after rebooting i still have no access to recovery (no errors in adb - process completed)
- flash CWM Recovery via ODIN but after reboot i can not boot to CWM
- flash stock rom I8150XXKK1 via ODIN - no changes to rom. Phone is loadin the old rom
ODIN Explanation:
In both cases of flashin CWM and stock rom i followed the procedure step by step with and without automatic reboot. ODIN says that flashing is done and PASS. During automatic reboot phone doesnt reboot it only turns off. After manual reboot phone is loading old rom (Kezra V4 installed a week ago) and there is no sign of CWM.
So now i am wondering:
- is it software or hardware issue
- how can i identify and isolate the problem
- how to make the phone to save the changes after reboot
- how to get a working CWM Recovery so i can flash the phone
- How to make ODIN to flash the phone
What do You make out this?
Man.....I am so sorry.
I have never seen such a well documented OP...
Congrats on that first!!
I really am at a loss as to what to suggest, as you have covered so many bases yourself.
Just to me, looking again at your post, I don't really think those .ogg files have anything to do with it.
It seems your problems originated with flashing the Kezra Custom ROM.
To lose your Recovery Partition must mean some data corruption introduced by the flashing process.
I know you have flashed stock with ODIN, this was One Package??
I am not sure, but I think there may be Stock ROM which has seperate files.......???
It is just a suggestion, perhaps someone else may know.....
At least this will bump your post!!!
All I can say further is best of luck....hope it can be solved.
Also, there also is return for repair to Sammy.....as we say in Ireland.... Play the eejit!!
Sent from my SGW GT-I8150 using Tapatalk!!
Thanks Irish for taking your time to reply.
Well... yes i did my best to make the post as much descriptive as possible due to the nature of the issue itself.
When it comes to ODIN it was one file only. I didn't try with multiple files.
I don't think that ogg files itself are the source of all that mess. On the other hand i wouldn't blame Kezra rom.
As you noticed i tried to track down the time and place when it happend and how it all started.
It may be a coincidence but i suspect that "ogg glitch" (keep in mind that was the very first fail reboot and system crash of my phony since i bought it) has something to do with it. Why? All the settings, apps etc. in the phone are as they were set on Wednesday 28.03 including Alarm set to 8:00am. Same day "ogg glitch" occurred. Betwene Wednesday and Now no flashing has been done except all the mentioned steps (failed) that i have taken in order to restore my phone. Every time i reboot the phone, all the setting, apps etc. are being reverted to the state from before "ogg glitch"
Another thing is the message given by superuser while trying to update su binary. "Some kind of write protection like S-ON". (at this point i didn't have time to do a in depth search on "S-ON")
Now... i am not an expert but it makes me wonder... is it?
- internal phone memory (the chip itself) is corrupted or damaged
- the file system of internal memory is corupted
- system partition is corupted
- there is an issue with root access and permissions
- while copying ogg files to /system/... i made a mistake at some point and set wrong mount rw/ro and wrong permissions
- is such thing as "recovery loop" possible - after every each reboot the phone is "restored" to the state from before "ogg glitch"
When it comes to return to Samsung... The phone is not only working but is rooted, has a custom rom... She is not a VIRGIN mate.
Sorry, I didn't mean to say that Kezra's ROM is at fault......phew...nearly got into trouble there.
I meant that during the flash of the ROM, there may have been an event, loss of power??? which has caused corruption of the Partition system on your phone??
I know there is no locked Bootloader on our phone, which is what s-on indicates....usually HTC phones have/had this....hence problems with flashing Custom ROM's Recovery......
Somehow, your phone has got into a state which mimics locked bootloader, has to be corruption, IMO.
If you can locate ODIN files to flash separately, maybe will work, but I'm not sure..
As for returning to Samsung......
there is a thread here somewhere, Rio Saputro, where Sammy has accepted phones with boot-loops back for repair, due to hardware issues, so I am not sure haw much checking they do!!!
I can still access download mode but i think i wont be able to flash anything.
ODIN MODE
PRODUCT NAME: GTI8150
CUSTOM BINARY DOWNLOAD: NO
CURRENT KERNEL: UNKNOWN !!
Irish would You be so kind and compare that info with your downlod mode please?
Otherwise i think i will have to return my W to Samsung.
Cheers
jbs.sc said:
I can still access download mode but i think i wont be able to flash anything.
ODIN MODE
PRODUCT NAME: GTI8150
CUSTOM BINARY DOWNLOAD: NO
CURRENT KERNEL: UNKNOWN !!
Irish would You be so kind and compare that info with your downlod mode please?
Otherwise i think i will have to return my W to Samsung.
Cheers
Click to expand...
Click to collapse
Don't worry, your phone is not bricked.. Just download the Asian firmware from the development thread (it will have multiple files inside the package) and flash it through Odin (look for flashing process for multiple file package), you will be good to go.
Sent from my Novo704FC-E2 using Tapatalk
I have already tried multi part asian firmware provided by THE-E.
Same thing as with one file firmware.
With auto reboot phone just turns off and doesn't turn on.
Without auto reboot... well it just stays on and that's it.
After manual reboot i am back to the old rom.
I am using odin 4.43
Should i try other versions?
I do have factory gurantee on my phone till 2013 and if they won't accept it...
oh well s*** happens... not for the first nor the last time in my life. There is no fun of modding without a risk.
jbs.sc said:
I can still access download mode but i think i wont be able to flash anything.
ODIN MODE
PRODUCT NAME: GTI8150
CUSTOM BINARY DOWNLOAD: NO
CURRENT KERNEL: UNKNOWN !!
Irish would You be so kind and compare that info with your downlod mode please?
Otherwise i think i will have to return my W to Samsung.
Cheers
Click to expand...
Click to collapse
Hi friend.....
Not sure what your current state of play is, but my download mode was exactly as you have quoted above.
see this from last Christmas,
when I was in despair.....symptoms very similar to what you have now, after failed ODIN flash....I had no recovery and my phone would not boot, just download mode, as you have above.
However, I solved it pretty easily, after modifying my ODIN settings.
Unfortunately THE-E's instructions said "unmark Auto Reboot"......which is not correct.....
this meant the Flash never completed.......
See here for my celebratory post, much relieved...
This was very much like your recent experience.
I think there may be some hope/help for you there!!!!
Let me know......bast of luck......
Irish,
I did try with auto reboot marked. When ODIN starts the procedure of auto reboot the phone turns off but it doesn't turn on. ODIN waits for the phone till the flashing is completed and says PASS but the phone stays turned off anyway.
Btw. Perhaps i should use KIES to try to update and brick my phone.
I would have a valid reason to claim warranty
jbs.sc said:
Irish,
I did try with auto reboot marked. When ODIN starts the procedure of auto reboot the phone turns off but it doesn't turn on. ODIN waits for the phone till the flashing is completed and says PASS but the phone stays turned off anyway.
Btw. Perhaps i should use KIES to try to update and brick my phone.
I would have a valid reason to claim warranty
Click to expand...
Click to collapse
OK.....I think that was my last shot......I am out of ideas!!!
Maybe post screen shot of ODIN procedure if you can??
I can't remember how my phone reacted after PASS and Reboot, but that doesn't sound right.......
Can you post the ODIN Message output.....just so ppl can compare and perhaps help.
OK i tried to flash it again just to take screenshots. And again same thing.
OK.....just have a look at my thread here.......
which is a pdf of the Service manual I "procured"
There is something there about ODIN, which Samsung use as well....
I just noticed a little thing when using multiple files.....
they have also set the " Reset Time = 300" for their Flash.......
P.21....or [6 Level 1 Repair]........
the pdf files are a little out of sequence!!!!
Also, try flash without SD or SIM card inserted.....
Irish,
Just to let you know. I did what you suggested.
Flashing with timer, without sim card and without external memory did't help.
As far as i remember someone had similar problem, unfortunately solution was never found.
I think when it comes to ODIN i run out of options.
Thanks for all the help and assistance.
OK......out of suggestions here!!
It is just such a pity.....
download mode normally means "no brick-can flash"
Sorry we could not fix.....next move?? Sammy??
Best of luck anyway!!
Sent from my SGW GT-I8150 using Tapatalk!!
Did you try to flash only boot img? Not sure if that's possible but it looks like your boot is messed up.
Sent from my GT-I8150 using Tapatalk 2 Beta-5
I dont think it makes any difference what am i flashing.
Whether it is software or hardware problem it prevents phone from auto rebooting (and applying any changes made during flashing process)
Not only during ODIN auto reboot but also from download mode reboot (once in download mode you can press volume down button to reboot phone)
Just thinking if you try to do it part by part and not whole firmware in 1 go. But if you manage reflash image boot hope you should by fine

Stuck on bootlogo

i installed CyanogenMod 7.2 RC3 on my Xperia Arc S (2.3.4) and the CM didnt load it just kept repeating itself, so before i had made a backup of my stock rom with apps installed (such as Titanium Backup, Rom manager, etc.) but when i restored it, it still was stuck at the SE boot logo and i have no idea what to do
my phone has a unlocked bootloader and its rooted on firmware .42 so i no CM stuffed my phone up cause it was probably not compatible with my Arc S
does anyone have any solutions to this (my phone is not bricked, its just stuck at the SE logo)
Please help me
Are you restoring the backup with the kernel you backed up on? If not then that's the reason for bootloops.
sinksterĀ©
i dont no, i think CM 7.2 RC3 didnt support on my xperia arc s (vers. 2.3.4) and i dont even know if i installed a kernel
but by the way is therer CyanogenMod working for my xperia arc s?
and if a kernel is need to run CM
I am nearly 100% certain, from what you have said about Sony Ericsson logo, that the reason you are stuck is because you are still using the kernel from the (official Sony) .042 firmware.
You need to use Cyanogenmod's own kernel which is inside the zip that you used to install CM7. File you need should be named boot.img
Download the attachment below and unzip it to your hard drive.
Place boot.img in the same place you unzipped the attachment.
Open a command prompt and change directory to the where you unzipped attachment.
Power off your phone.
Hold down menu button and insert data cable.
Notication LED should turn blue, indicating you are in fastboot mode.
In the command prompt type "fastboot devices" . This is just to make sure that the PC and phone are communicating okay. It should give a serial number if all is ok.
To flash the kernel type "fastboot flash boot boot.img" .
After a few seconds the command prompt window says "finished total time...". At this point you are done.
Unplug data cable and start up phone. You will probably see a different logo than Sony now and CM7 should now boot up properly.
Hope this helps.
i did exactly what u said before, i extracted the boot.img from the CM7RC3.zip to the fastboot folder of my android SDK, and then i put the CM7RC3.zip on the root of my Xperia Arc S SD card
then i used CWM to install the .zip from my SD card, the reason i think my phone was stuck on BL is because CM7 only works with gingerbread 2.3 my version is 2.3.4
build.prop of FXP124_CM7.2_RC3 indicates that it is 2.3.7
CM7 is classed as Gingerbread also, just that it is built completely from the Google open source code, rather than from anything officially released by Sony.
If using CWM you wiped data and installed the CM7 zip, plus you also flashed the CM7 kernel file, there should be nothing left of the older 2.3.4 for CM7 to clash with.
Wipe data is very important before installing ROMs. Failing to do so is often the cause of bootloops or causing other failures of a ROM to start up (such as when it just sits there doing nothing for a long time instead of loading up to the homesecreen).

Categories

Resources