[Q] Stuck in boot loader - Please check & correct steps - Xperia Arc Q&A, Help & Troubleshooting

Hello,
I'm stuck in bootloader (I think). It's my first attempt to flash a kernel and ROM, so I may have done something stupid... please correct any mistakes in my workflow:
1) rooted phone (ZergRush) - OK
2) Unlocked the bootloader (lollylost100) - OK
3) Flashed DoomKernelv22 using fastboot
4) Doomkernel recommends baseband36(+patch), so used flashtool to flash baseband36 (note first time I tried this I tried using "Select Kernel to Flash" - but got an error messge "FAILED (remote: Image won't fit, partition too small!)". So then I tried using "Select System to Flash", and had success:
07/005/2012 00:05:03 - INFO - Selected system (system.img or system.sin): C:\Flashtool\LT15_LT18_36_Baseband.ftf
07/005/2012 00:05:03 - INFO - Flashing selected system
07/005/2012 00:05:03 - INFO - Please check the log before rebooting into system
07/005/2012 00:05:28 - INFO - Finished Fastboot Toolbox​5)Booted into recovery and flashed the following (all in one session):
- ARC-DooMKernel-v22-modules_CWM
- PatchBaseBand36Libs.zip
- update-Arconium-8.2.zip
- update-arconium-FBInside_Timescape-v5.zip
- update-arconium-Sounds.zip
5a) didn't flash these ones:
- update-arconium-StockModules.zip (this is only for reverting back to a stock ROM?)
- couldn't find doomlord wifi/BT update, assumed it was all part of arconium? Also assumed that if this was a problem it would only affect wifi/BT not the rest of the install.
6) Booted phone - but just get a a loop of the "booting doomkernal" graphic / blank screen/buzz.
7) booted into recovery and wiped dalvik cache (no change)
8) booted into recovery and did factory reset/clear cache (no change)
9) reloaded all of the above (no change - still boot loop)
Think that's all, tried to be comprehensive.
Thanks in advance. R.

r_southampton said:
Hello,
I'm stuck in bootloader (I think). It's my first attempt to flash a kernel and ROM, so I may have done something stupid... please correct any mistakes in my workflow:
1) rooted phone (ZergRush) - OK
2) Unlocked the bootloader (lollylost100) - OK
3) Flashed DoomKernelv22 using fastboot
4) Doomkernel recommends baseband36(+patch), so used flashtool to flash baseband36 (note first time I tried this I tried using "Select Kernel to Flash" - but got an error messge "FAILED (remote: Image won't fit, partition too small!)". So then I tried using "Select System to Flash", and had success:
07/005/2012 00:05:03 - INFO - Selected system (system.img or system.sin): C:\Flashtool\LT15_LT18_36_Baseband.ftf
07/005/2012 00:05:03 - INFO - Flashing selected system
07/005/2012 00:05:03 - INFO - Please check the log before rebooting into system
07/005/2012 00:05:28 - INFO - Finished Fastboot Toolbox​5)Booted into recovery and flashed the following (all in one session):
- ARC-DooMKernel-v22-modules_CWM
- PatchBaseBand36Libs.zip
- update-Arconium-8.2.zip
- update-arconium-FBInside_Timescape-v5.zip
- update-arconium-Sounds.zip
5a) didn't flash these ones:
- update-arconium-StockModules.zip (this is only for reverting back to a stock ROM?)
- couldn't find doomlord wifi/BT update, assumed it was all part of arconium? Also assumed that if this was a problem it would only affect wifi/BT not the rest of the install.
6) Booted phone - but just get a a loop of the "booting doomkernal" graphic / blank screen/buzz.
7) booted into recovery and wiped dalvik cache (no change)
8) booted into recovery and did factory reset/clear cache (no change)
9) reloaded all of the above (no change - still boot loop)
Think that's all, tried to be comprehensive.
Thanks in advance. R.
Click to expand...
Click to collapse
i think you should
make a factory reset,wipe dalvic cache,wipe cache in recovery
then again flash doomlord kernal
and then flash acronium8.2 in recovery
and then reboot your phone
after it reboots successfully
see your phone is working
if it is working then you should enter into recovery and then flash any other zip module u want to flash
it is recommended not flash the any other zip file at the same instance when you are flashing a custom rom in recovery

Thank you abhisheak.bansal
Just did Factory Reset / Wipe Cache
Then booted to Recovery and flashed doomkernel modules
Powered off
rebooted to recovery and flashed arconium8.2
Powered off / repowered
Still loops in boot.
Need to go out now, but will try repeat slowly one step at a time from the initial kernel image using fastboot. Will leave the baseband stuff until the end in case that's confused things.

i would reccommend if all doesnt work out at all
then flash the official ftf via flashtool

1. Flash an official stock 4.0.2.A.0.42/.58/.62 FW --> http://forum.xda-developers.com/showthread.php?p=22105604
2. Flash/install the baseband patch AND the baseband itself --> http://forum.xda-developers.com/showthread.php?t=1382657
3. Flash Doomkernel --> http://forum.xda-developers.com/showthread.php?t=1172885
4. Flash the Doomkernel modules (MODULES for DooMKernel (v22)) --> http://forum.xda-developers.com/showthread.php?t=1172885
5. Flash the Arconium ROM --> http://forum.xda-developers.com/showthread.php?t=1325640 (doesn't include doomkernel 22 modules, hence step 4)
6. Flash optional Arconium packs
Apply a reboot between all steps and read/apply instructions as written the listed threads.

Thank you to all who have offered advice.
Decided to go with ICS (Arconium 3.C) and Stock Kernel+CWM. & baseband70
Flashed the above and all started working.
Although I was still on baseband-56....
That was my problem, I hadn't been using Flashtool properly. Although it appeared to be flashing something... It was until I started trying to use it in "Flashmode" rather than "Fastboot" mode (and with the firmwares in the firmware directory - rather than browsing to them), that I then got prompted to install lots of drivers... and was then able to flash the baseband properly. For those of you still reading, the 4 INFO lines in the first post do not indicate a successful baseband flash. This was the successful log:
07/039/2012 18:39:21 - INFO - Selected LT15_LT18_70_Baseband.ftf
07/039/2012 18:39:21 - INFO - Preparing files for flashing
07/039/2012 18:39:21 - INFO - Please connect your device into flashmode.
07/039/2012 18:39:27 - INFO - Device connected in flash mode
07/039/2012 18:39:27 - INFO - Opening device for R/W
07/039/2012 18:39:27 - INFO - Reading device information
07/039/2012 18:39:27 - INFO - Phone ready for flashmode operations.
07/039/2012 18:39:27 - INFO - Start Flashing
07/039/2012 18:39:27 - INFO - Flashing loader
07/039/2012 18:39:30 - INFO - Loader : S1_Loader_Root_773f - Version : R4A066 / Bootloader status : ROOTED
07/039/2012 18:39:30 - INFO - Flashing fota0.sin
07/039/2012 18:39:31 - INFO - Flashing fota1.sin
07/039/2012 18:39:32 - INFO - Flashing adsp.sin
07/039/2012 18:39:35 - INFO - Flashing amss.sin
07/039/2012 18:39:44 - INFO - Flashing amss_fs_ayame.sin
07/039/2012 18:39:45 - INFO - Ending flash session
07/039/2012 18:39:45 - INFO - Flashing finished.
07/039/2012 18:39:45 - INFO - Please wait. Phone will reboot

I was wondering why you'd want to flash a GB rom instead of an ICS one
But glad you got it sorted out!
By the way, the steps I mentioned before (minus step 2) also work for the Arconium 3C release. And if you flash the official .431 FW in step 1, you'll have baseband .72

I was thinking that GB would probably be better on single core Arc... but it was a close call.
Anyway, so far ICS is doing nicely. Certainly faster than it used to be, but that's probably down to the increase in memory I got by going with a custom ROM.
Out of curiosity, what might BB 72 offer by way of improvement?

As far as I know, there's no difference between .70 and .72 basebands.
But I found it easyer, when I did the steps, to just flash the newest firmware, which included the .72

Related

Brick recovery

Hello all, I am requesting help with my Xperia Play.
It was not working smoothly, so I decided to install a custom ROM. I installed the ICS beta and then attempted to install xDark ICS but it has failed.
Pretty sure its R800i, bought unlocked in the UK
I cannot see anything on screen when I turn the device on
When the power button is pressed it vibrates slightly
I can put it in recovery mode (Holding Back and plugging USB) -light appears green
I can put it in fastboot mode (Holding Search and plugging USB) -light appears blue
When I try to flash any .ftf files with Flashtool it either comes up with an error or stays on "retrieving device information"
I cannot work out how to repair with PC Companion
When I select the .ftf file, no files appear in the firmware content. (I have tried various firmware files but any more would be appreciated)
My flash tool logs: When selecting firmware or dragging firmware
22/001/2012 22:01:27 - INFO - <- This level is successfully initialized
22/001/2012 22:01:27 - INFO - Flashtool Version 0.9.0.0 built on 2012-07-19 22:57:15
22/001/2012 22:01:27 - INFO - You can drag and drop ftf files here to start flashing them
22/001/2012 22:01:33 - INFO - Device connected in flash mode
22/001/2012 22:01:33 - INFO - Selected R800i_4.0.2.A.0.42_Generic_UK.ftf
22/001/2012 22:01:33 - INFO - Flash canceled
Click to expand...
Click to collapse
22/004/2012 22:04:45 - INFO - Selected R800i_4.0.2.A.0.42_Generic_UK.ftf
22/004/2012 22:04:45 - INFO - Preparing files for flashing
22/004/2012 22:04:45 - INFO - Please connect your device into flashmode.
22/004/2012 22:04:45 - INFO - Opening device for R/W
22/004/2012 22:04:45 - INFO - Reading device information
22/005/2012 22:05:01 - INFO - Start Flashing
22/005/2012 22:05:01 - INFO - Flashing loader
22/005/2012 22:05:01 - INFO - Ending flash session
22/005/2012 22:05:01 - ERROR -
22/005/2012 22:05:01 - ERROR - Error flashing. Aborted
22/005/2012 22:05:01 - INFO - Device disconnected
Click to expand...
Click to collapse
This sometimes appears
22/010/2012 22:10:03 - INFO - Selected R800i_4.0.2.A.0.42_Generic_UK.ftf
22/010/2012 22:10:03 - INFO - Preparing files for flashing
22/010/2012 22:10:03 - INFO - Please connect your device into flashmode.
22/010/2012 22:10:04 - INFO - Opening device for R/W
22/010/2012 22:10:04 - INFO - Reading device information
22/010/2012 22:10:04 - INFO - Phone ready for flashmode operations.
22/010/2012 22:10:04 - INFO - Start Flashing
22/010/2012 22:10:04 - INFO - Flashing loader
22/010/2012 22:10:04 - INFO - Ending flash session
22/010/2012 22:10:04 - ERROR - ERR_SEVERITY="MAJOR";ERR_CLASS="SECURITY_CLASS";ERR_DYNAMIC="SIN header verification failed"
Click to expand...
Click to collapse
I'm not interested in what I did wrong I just want my phone functionality back.
I want the stock rom back on my phone. Thanks!
Do you know how to flash roms with flash tools?
Sure that your phon has unlock bootloader? (if don't, follow this http://unlockbootloader.sonymobile.com/instructions)
The same problem happened to me... I learn how to unlock bootloader and install roms with flashtools... now I'm running CM9 RC2...
If you know how to flsh see post #5 of this thread...http://forum.xda-developers.com/showthread.php?p=28977879#post28977879
if you don´t, Tell me!
cheers :good:
Alejandroch said:
Do you know how to flash roms with flash tools?
Sure that your phon has unlock bootloader? (if don't, follow this http://unlockbootloader.sonymobile.com/instructions)
The same problem happened to me... I learn how to unlock bootloader and install roms with flashtools... now I'm running CM9 RC2...
If you know how to flsh see post #5 of this thread...http://forum.xda-developers.com/showthread.php?p=28977879#post28977879
if you don´t, Tell me!
cheers :good:
Click to expand...
Click to collapse
Yeah I know how but I cant access the recovery menu.
Anyway, I resolved the issue by flashing the latest stock (.62) .ftf file from here and it seemed to work. Thanks

Flash always fails (system.sin)

Hi everybody,
I've a Xperia Arc LT15i and tried to update to ICS using PC Companion. However, after the progress bar was about 50%, an error message appeared, saying that it was not possible to complete, and to try again later. I tried several times again, with the same result. Then, tried to update using Update Service, without success too.
As the official update software weren't working, I decided to flash some roms using Flashtool. Althouth it looked promissing, most of the roms I tried can't be fully flashed (both GB and ICS). Following several tips found here, I tried to use older Flashtool releases, different roms, restarted my computer, check the "No final verification" option... Nothing worked.
The only thing I noticed is that, if I remove the system.sin from the ftt files, specially from GB roms, the flash successfully finishes. But, after that, if I try to flash only the remaining system.sin file, it always fails...
Please, I would really appreciate some advice to make my Xperia Arc work again.
Thanks in advance!
Post full Flashtool log please.
Sent from my Xperia Arc S using xda premium
^
+1
post the flashtool log so we can help you .., ~
SubScorpion said:
Hi everybody,
I've a Xperia Arc LT15i and tried to update to ICS using PC Companion. However, after the progress bar was about 50%, an error message appeared, saying that it was not possible to complete, and to try again later. I tried several times again, with the same result. Then, tried to update using Update Service, without success too.
As the official update software weren't working, I decided to flash some roms using Flashtool. Althouth it looked promissing, most of the roms I tried can't be fully flashed (both GB and ICS). Following several tips found here, I tried to use older Flashtool releases, different roms, restarted my computer, check the "No final verification" option... Nothing worked.
The only thing I noticed is that, if I remove the system.sin from the ftt files, specially from GB roms, the flash successfully finishes. But, after that, if I try to flash only the remaining system.sin file, it always fails...
Please, I would really appreciate some advice to make my Xperia Arc work again.
Thanks in advance!
Click to expand...
Click to collapse
what about bl? locked or unlocked?
and what roms you tried custom or stock?
I had the same prob , the thing was,
you need to clean syste,data,catch (on "mount" menu<cant remember the corect path>)
and other catch folders thru CWM.
Just do it. you will be fine
creative_md said:
what about bl? locked or unlocked?
and what roms you tried custom or stock?
Click to expand...
Click to collapse
chathudagr8 said:
I had the same prob , the thing was,
you need to clean syste,data,catch (on "mount" menu<cant remember the corect path>)
and other catch folders thru CWM.
Just do it. you will be fine
Click to expand...
Click to collapse
Lolwat guys.
There is nothing to do with custom ROMs or bootloader at here.
He clearly said, he is attempting to install stock firmware via Flashtool. There is not even a word about custom stuff.
And bootloader has nothing to do with Flashtool in that case.
Thank you guys for the replies.
Here is the latest logs - actually, it failed when flashing the amss.sin w/ Flashtool 0.6.9.1:
Code:
22/003/2012 21:03:48 - INFO - <- This level is successfully initialized
22/003/2012 21:03:48 - INFO - Flashtool Version 0.6.9.1 built on 2012-04-09 19:22:19
22/003/2012 21:03:48 - INFO - You can drag and drop ftf files here to start flashing them
22/003/2012 21:03:54 - INFO - Device disconnected
22/004/2012 21:04:26 - INFO - Selected LT15a arc_v2.3.4, 4.0.2.A.0.42_Generic America.ftf
22/004/2012 21:04:26 - INFO - Preparing files for flashing
22/004/2012 21:04:28 - INFO - Please connect your device into flashmode.
22/004/2012 21:04:45 - INFO - Device connected in flash mode
22/004/2012 21:04:45 - INFO - Opening device for R/W
22/004/2012 21:04:45 - INFO - Reading device information
22/004/2012 21:04:45 - INFO - Phone ready for flashmode operations.
22/004/2012 21:04:45 - INFO - Start Flashing
22/004/2012 21:04:45 - INFO - Flashing loader
22/004/2012 21:04:49 - INFO - Loader : S1_Loader_Root_773f - Version : R4A066 / Bootloader status : ROOTED
22/004/2012 21:04:49 - INFO - Flashing adsp.sin
22/004/2012 21:04:52 - INFO - Flashing kernel.sin
22/004/2012 21:04:54 - INFO - Flashing amss_fs.sin
22/004/2012 21:04:54 - INFO - Flashing fota1.sin
22/004/2012 21:04:55 - INFO - Flashing fota0.sin
22/004/2012 21:04:56 - INFO - Flashing amss.sin
22/005/2012 21:05:00 - INFO - Ending flash session
22/005/2012 21:05:00 - ERROR - ERR_SEVERITY="MAJOR";ERR_CLASS="MEMORY_CLASS";ERR_STATIC="HASH_VER";ERR_DYNAMIC="Block verification failed";
22/005/2012 21:05:00 - ERROR - Error flashing. Aborted
22/005/2012 21:05:01 - INFO - Device connected in flash mode
22/005/2012 21:05:02 - INFO - Device disconnected
22/005/2012 21:05:04 - INFO - Device connected in flash mode
I'm trying only stock roms, as Someguyfromhell noticed; latest ones were:
LT15a arc_v2.3.4, 4.0.2.A.0.42_Generic America
LT15i_4.1.B.0.431[Generic World FR]
But I'm pretty sure I tried most of the stock roms available in other topics.
Update your flashtool. Maybe that will fix the error :good:
http://forum.xda-developers.com/showthread.php?t=1000012
Marcskim said:
Update your flashtool. Maybe that will fix the error :good:
http://forum.xda-developers.com/showthread.php?t=1000012
Click to expand...
Click to collapse
Unfortunately, it doesn't. I tried several versions:
flashtool-0.9.0.0-windows
flashtool-0.8.5.0-windows
flashtool-0.8.0.0-windows
flashtool-0.6.9.1-windows
flashtool-0.6.8.0-windows
Flashtool-0.2.9.1-windows
Hi everybody,
I've attached a full (detailed) log from Flashtool 0.9.0 when trying to flashing rom LT15i_4.0.2.A.0.62.ftf - this one failed in the system.sin.
With this rom, the Sony Ericsson logo appears on the screen, but right after that a warning icon is presented and the device turns off.
Someguyfromhell said:
Lolwat guys.
There is nothing to do with custom ROMs or bootloader at here.
He clearly said, he is attempting to install stock firmware via Flashtool. There is not even a word about custom stuff.
And bootloader has nothing to do with Flashtool in that case.
Click to expand...
Click to collapse
I have anwser to both q
1st if he is on unlocked bl he Cannot use pc companion to update it will brick his device and only applying patch can solve it I think or it may give error
2nd if he is on gb as I guess and tried to flash ICS CUSTOM ROMS as he said he tried rom(S) he cannot.
Because ics rom requires ics kernels.
And yes about custom roms I was wrong as I know NOW that he tried stock roms
Sent from my R800i using xda premium
SubScorpion said:
Hi everybody,
I've a Xperia Arc LT15i and tried to update to ICS using PC Companion. However, after the progress bar was about 50%, an error message appeared, saying that it was not possible to complete, and to try again later. I tried several times again, with the same result. Then, tried to update using Update Service, without success too.
As the official update software weren't working, I decided to flash some roms using Flashtool. Althouth it looked promissing, most of the roms I tried can't be fully flashed (both GB and ICS). Following several tips found here, I tried to use older Flashtool releases, different roms, restarted my computer, check the "No final verification" option... Nothing worked.
The only thing I noticed is that, if I remove the system.sin from the ftt files, specially from GB roms, the flash successfully finishes. But, after that, if I try to flash only the remaining system.sin file, it always fails...
Please, I would really appreciate some advice to make my Xperia Arc work again.
Thanks in advance!
Click to expand...
Click to collapse
here is your solution http://www.icsforums.com/comment/210181#comment-210181
Sorry, it's not 100% clear to me what was your suggestion. But I tried to check the "No final verification" option, used a LT18 rom and even followed that specific steps to flash first everything except system and then system only. Same results all the time:
24/010/2012 23:10:18 - INFO - <- This level is successfully initialized
24/010/2012 23:10:18 - INFO - Flashtool Version 0.9.0.0 built on 2012-07-19 22:57:15
24/010/2012 23:10:18 - INFO - You can drag and drop ftf files here to start flashing them
24/010/2012 23:10:24 - INFO - Device disconnected
24/011/2012 23:11:20 - INFO - Selected LT18_4.1.A.0.562_NCB.ftf
24/011/2012 23:11:20 - INFO - Preparing files for flashing
24/011/2012 23:11:41 - INFO - Please connect your device into flashmode.
24/012/2012 23:12:01 - INFO - Device connected in flash mode
24/012/2012 23:12:02 - INFO - Opening device for R/W
24/012/2012 23:12:02 - INFO - Reading device information
24/012/2012 23:12:02 - INFO - Phone ready for flashmode operations.
24/012/2012 23:12:02 - INFO - Start Flashing
24/012/2012 23:12:02 - INFO - Flashing loader
24/012/2012 23:12:07 - INFO - Loader : S1_Loader_Root_773f - Version : R4A066 / Bootloader status : ROOTABLE
24/012/2012 23:12:07 - INFO - Disabling final data verification check
24/012/2012 23:12:07 - WARN - This file is ignored : simlock.ta
24/012/2012 23:12:07 - INFO - Flashing kernel.sin
24/012/2012 23:12:09 - INFO - Flashing fota0.sin
24/012/2012 23:12:10 - INFO - Flashing fota1.sin
24/012/2012 23:12:11 - INFO - Flashing adsp.sin
24/012/2012 23:12:13 - INFO - Flashing amss_fs_ayame.sin
24/012/2012 23:12:13 - INFO - Flashing amss.sin
24/012/2012 23:12:18 - INFO - Ending flash session
24/012/2012 23:12:18 - ERROR - ERR_SEVERITY="MAJOR";ERR_CLASS="MEMORY_CLASS";ERR_STATIC="HASH_VER";ERR_DYNAMIC="Block verification failed";
Click to expand...
Click to collapse
I really thank you guys for all suggestions. I spent several nights trying to fix my phone and I really appreciate your effort to help me.
I never imagined that the official software update may end up with my phone bricked. I'm really, really disappointed with SE. The worst thing is, I bought my phone in the US, but I live in Brazil and our local SE only provides support for devices bought in Brazil. In other words, they won't even try to repair my phone. I'll think twice before buying other SE phone.
SubScorpion said:
Sorry, it's not 100% clear to me what was your suggestion. But I tried to check the "No final verification" option, used a LT18 rom and even followed that specific steps to flash first everything except system and then system only. Same results all the time:
I really thank you guys for all suggestions. I spent several nights trying to fix my phone and I really appreciate your effort to help me.
I never imagined that the official software update may end up with my phone bricked. I'm really, really disappointed with SE. The worst thing is, I bought my phone in the US, but I live in Brazil and our local SE only provides support for devices bought in Brazil. In other words, they won't even try to repair my phone. I'll think twice before buying other SE phone.
Click to expand...
Click to collapse
did you check the md5 sum of ftf file?
if not check it and confirm its a complete file.....
---------- Post added at 01:59 PM ---------- Previous post was at 01:33 PM ----------
also try to flash it in safe mode....
Hi creative_md,
The ftf files are not corrupted. And I re-tried in safe mode a few minutes ago, but it had the same results.
FYI, here are the list of roms I tried until now - they failed when flashing amss.sin or system.sin:
LT15a arc_v2.3.4, 4.0.2.A.0.42_Generic America
LT15a_2.3.4_US generic
LT15i_4.0.2.A.0.42_(1247-1041)
LT15i_4.0.2.A.0.42_Generic Global
LT15i_4.0.2.A.0.62
LT15i_4.1.B.0.431[Generic World FR]
LT18_4.1.A.0.562_NCB
Is there any other way to flash the .ftf files? I would try fasboot, but I didn't find an .img with stock rom or a reliable way to flash all .sin files that are inside of .tft roms.
Thanks!
SubScorpion said:
Hi creative_md,
The ftf files are not corrupted. And I re-tried in safe mode a few minutes ago, but it had the same results.
FYI, here are the list of roms I tried until now - they failed when flashing amss.sin or system.sin:
LT15a arc_v2.3.4, 4.0.2.A.0.42_Generic America
LT15a_2.3.4_US generic
LT15i_4.0.2.A.0.42_(1247-1041)
LT15i_4.0.2.A.0.42_Generic Global
LT15i_4.0.2.A.0.62
LT15i_4.1.B.0.431[Generic World FR]
LT18_4.1.A.0.562_NCB
Is there any other way to flash the .ftf files? I would try fasboot, but I didn't find an .img with stock rom or a reliable way to flash all .sin files that are inside of .tft roms.
Thanks!
Click to expand...
Click to collapse
i searched a lot for you and most of times this problem got solved by ticking "no final verification box" and in your case its not working even though you tried .42 too. so at last try this:
start flashtool >get in flashmode > choose ftf you want
now tick boxes
wipe cache >exclude system >flash ftf
after flash again do 1 step with these boxes tick:
exclude baseband > exclude kernel >flash ftf
finally this:
wipe data >exclude kernel >exclude system > exclude baseband
if it didnt worked i suggest you now to do some modifications to your phone:silly:
i.e unlock your bootloader and flash roms using cwm i will tell you all how to do it. pm me for that
remember it will void your warrenty and it doesnt matter bcoz you dont have se service in brazil as you said
Thanks, creative_md. I was finally able to make the phone boot - here are the steps, if someone faces the same issue:
1. Flashed everything in the .ftf file using Flastool, except system (system.sin).
2. Opened the .ftf file using 7zip and extracted the system.sin.
3. Rooted the phone.
4. Flashed the system.sin using fastboot: fastboot flash system system.sin.
Unfortunately, I think there's really something else wrong with the phone, as it restarts randomly, several processes stop to work unexpectedly and it's not possible to update some apps (maps, facebook, flash player and youtube) - when installing the updates, the phone restarts. This behavior happened with two different stock roms.
This weekend, I'll try to flash some custom roms.
SubScorpion said:
Thanks, creative_md. I was finally able to make the phone boot - here are the steps, if someone faces the same issue:
1. Flashed everything in the .ftf file using Flastool, except system (system.sin).
2. Opened the .ftf file using 7zip and extracted the system.sin.
3. Rooted the phone.
4. Flashed the system.sin using fastboot: fastboot flash system system.sin.
Unfortunately, I think there's really something else wrong with the phone, as it restarts randomly, several processes stop to work unexpectedly and it's not possible to update some apps (maps, facebook, flash player and youtube) - when installing the updates, the phone restarts. This behavior happened with two different stock roms.
This weekend, I'll try to flash some custom roms.
Click to expand...
Click to collapse
make sure you do nandroid backup before you do anything
Fix with the latest FlashTool 0.9.9.0 (maybe bug on version 0.9.8.0) I got the same problem, SEUS brick my W8 when I try restore to stock. Retry several time stuck ini 15% progress. Get same result with Flashtool 0.9.8.0 with lot of ROM, always stop when flash system.sin part.
Just download and try latest Flashtool 0.9.9.0 maybe it solve the problem.
try to flash this firmware LT18_4.1.A.0.562_NCB.ftf

[Q] bricked my xperia play whilst flashing cm10

Hi,
plz help me make my phone working again. I wanted to flash cm 10 after manged to flash cm9. cm 9 ran after trying everything out for hours. Today i downloaded cm10 and flashed the kernel. after that i wasnt able to open the bootloader, so i flashed cm9 kernel again. That worked so far. i was able to open bootloader again, but it showed an failure notice whilst installing cm 9.
"assert failed: getprop ("ro.product.device") == "r800i" ......" this is copied with the endings r800i/a/at and zeus
E: Error in sd /sdcard/cm-9.1.0-zeus.zip
(Status 7)
Installation aborted.
I tried it a few times. Flashed cm 10 kernel, flashed cm9 kernel back, but its always the same failure notice. I would like to use cm9 again, it was good at all, but i wanted to update cm10 today. Please give me an how-to what to do unbricking my play.
_hacker_ said:
Hi,
plz help me make my phone working again. I wanted to flash cm 10 after manged to flash cm9. cm 9 ran after trying everything out for hours. Today i downloaded cm10 and flashed the kernel. after that i wasnt able to open the bootloader, so i flashed cm9 kernel again. That worked so far. i was able to open bootloader again, but it showed an failure notice whilst installing cm 9.
"assert failed: getprop ("ro.product.device") == "r800i" ......" this is copied with the endings r800i/a/at and zeus
E: Error in sd /sdcard/cm-9.1.0-zeus.zip
(Status 7)
Installation aborted.
I tried it a few times. Flashed cm 10 kernel, flashed cm9 kernel back, but its always the same failure notice. I would like to use cm9 again, it was good at all, but i wanted to update cm10 today. Please give me an how-to what to do unbricking my play.
Click to expand...
Click to collapse
If you're able to flash, you're not bricked. One thing is to make sure you are clearing data, cache and dalvik. That is often the root to the sort of issues you have had. My recommendation would be to find the correct ftf file for your model of Play and flash it back to stock. Get that working first, then go with CM10 if you like.
netizenmt said:
If you're able to flash, you're not bricked. One thing is to make sure you are clearing data, cache and dalvik. That is often the root to the sort of issues you have had. My recommendation would be to find the correct ftf file for your model of Play and flash it back to stock. Get that working first, then go with CM10 if you like.
Click to expand...
Click to collapse
i wiped cache n dalvik again now, but i cant install cm9. same failure notice as everytime
EDIT:
i tried flashing stock firmware. didnt worked. Log:
03/043/2013 12:43:39 - INFO - <- This level is successfully initialized
03/043/2013 12:43:40 - INFO - Flashtool Version 0.9.9.0 built on 2012-11-13 22:53:30
03/043/2013 12:43:40 - INFO - You can drag and drop ftf files here to start flashing them
03/044/2013 12:44:01 - INFO - Device disconnected
03/044/2013 12:44:33 - INFO - Selected Xperia_Relock_bootloader.ftf
03/044/2013 12:44:33 - INFO - Preparing files for flashing
03/044/2013 12:44:34 - INFO - Please connect your device into flashmode.
03/044/2013 12:44:40 - INFO - Device connected in flash mode
03/044/2013 12:44:40 - INFO - Opening device for R/W
03/044/2013 12:44:41 - INFO - Reading device information
03/044/2013 12:44:41 - INFO - Phone ready for flashmode operations.
03/044/2013 12:44:41 - INFO - Start Flashing
03/044/2013 12:44:41 - INFO - Processing loader
03/044/2013 12:44:41 - INFO - Checking header
03/044/2013 12:44:41 - INFO - Flashing data
03/044/2013 12:44:44 - INFO - Loader : S1_Loader_Root_773f - Version : R4A066 / Bootloader status : ROOTED
03/044/2013 12:44:44 - INFO - Flashing preset.ta
03/044/2013 12:44:44 - INFO - Writing TA unit : [00, 00, 08, B2, 00, 00, 00, 02, 00, 00]
03/044/2013 12:44:44 - INFO - Ending flash session
03/044/2013 12:44:44 - INFO - Flashing finished.
03/044/2013 12:44:44 - INFO - Please unplug and start your phone
03/044/2013 12:44:44 - INFO - For flashtool, Unknown Sources and Debugging must be checked in phone settings
03/044/2013 12:44:45 - INFO - Device connected in flash mode
03/044/2013 12:44:50 - INFO - Device disconnected
03/045/2013 12:45:01 - INFO - Selected Xperia Play_Release_Generic UK.ftf
03/045/2013 12:45:01 - INFO - Preparing files for flashing
03/045/2013 12:45:27 - INFO - Please connect your device into flashmode.
03/045/2013 12:45:34 - INFO - Device connected in flash mode
03/045/2013 12:45:35 - INFO - Opening device for R/W
03/045/2013 12:45:35 - INFO - Device connected in flash mode
03/045/2013 12:45:35 - INFO - Reading device information
03/045/2013 12:45:35 - INFO - Unable to read from phone after having opened it.
03/045/2013 12:45:35 - INFO - trying to continue anyway
03/045/2013 12:45:35 - INFO - Start Flashing
03/045/2013 12:45:35 - INFO - Processing loader
03/045/2013 12:45:35 - INFO - Checking header
03/045/2013 12:45:35 - INFO - Ending flash session
03/045/2013 12:45:35 - ERROR - Error in processHeader : 6 : Das Handle ist ungültig.
03/045/2013 12:45:35 - ERROR - Error flashing. Aborted
03/045/2013 12:45:36 - INFO - Device connected in flash mode
03/045/2013 12:45:44 - INFO - Flash canceled
first locked bootloader,second flashing stock rom
_hacker_ said:
i wiped cache n dalvik again now, but i cant install cm9. same failure notice as everytime
EDIT:
i tried flashing stock firmware. didnt worked. Log:
03/043/2013 12:43:39 - INFO - <- This level is successfully initialized
03/043/2013 12:43:40 - INFO - Flashtool Version 0.9.9.0 built on 2012-11-13 22:53:30
03/043/2013 12:43:40 - INFO - You can drag and drop ftf files here to start flashing them
03/044/2013 12:44:01 - INFO - Device disconnected
03/044/2013 12:44:33 - INFO - Selected Xperia_Relock_bootloader.ftf
03/044/2013 12:44:33 - INFO - Preparing files for flashing
03/044/2013 12:44:34 - INFO - Please connect your device into flashmode.
03/044/2013 12:44:40 - INFO - Device connected in flash mode
03/044/2013 12:44:40 - INFO - Opening device for R/W
03/044/2013 12:44:41 - INFO - Reading device information
03/044/2013 12:44:41 - INFO - Phone ready for flashmode operations.
03/044/2013 12:44:41 - INFO - Start Flashing
03/044/2013 12:44:41 - INFO - Processing loader
03/044/2013 12:44:41 - INFO - Checking header
03/044/2013 12:44:41 - INFO - Flashing data
03/044/2013 12:44:44 - INFO - Loader : S1_Loader_Root_773f - Version : R4A066 / Bootloader status : ROOTED
03/044/2013 12:44:44 - INFO - Flashing preset.ta
03/044/2013 12:44:44 - INFO - Writing TA unit : [00, 00, 08, B2, 00, 00, 00, 02, 00, 00]
03/044/2013 12:44:44 - INFO - Ending flash session
03/044/2013 12:44:44 - INFO - Flashing finished.
03/044/2013 12:44:44 - INFO - Please unplug and start your phone
03/044/2013 12:44:44 - INFO - For flashtool, Unknown Sources and Debugging must be checked in phone settings
03/044/2013 12:44:45 - INFO - Device connected in flash mode
03/044/2013 12:44:50 - INFO - Device disconnected
03/045/2013 12:45:01 - INFO - Selected Xperia Play_Release_Generic UK.ftf
03/045/2013 12:45:01 - INFO - Preparing files for flashing
03/045/2013 12:45:27 - INFO - Please connect your device into flashmode.
03/045/2013 12:45:34 - INFO - Device connected in flash mode
03/045/2013 12:45:35 - INFO - Opening device for R/W
03/045/2013 12:45:35 - INFO - Device connected in flash mode
03/045/2013 12:45:35 - INFO - Reading device information
03/045/2013 12:45:35 - INFO - Unable to read from phone after having opened it.
03/045/2013 12:45:35 - INFO - trying to continue anyway
03/045/2013 12:45:35 - INFO - Start Flashing
03/045/2013 12:45:35 - INFO - Processing loader
03/045/2013 12:45:35 - INFO - Checking header
03/045/2013 12:45:35 - INFO - Ending flash session
03/045/2013 12:45:35 - ERROR - Error in processHeader : 6 : Das Handle ist ungültig.
03/045/2013 12:45:35 - ERROR - Error flashing. Aborted
03/045/2013 12:45:36 - INFO - Device connected in flash mode
03/045/2013 12:45:44 - INFO - Flash canceled
first locked bootloader,second flashing stock rom
Click to expand...
Click to collapse
Hi I think you are flashing wrong file line 5 (03/044/2013 12:44:33 - INFO - Selected Xperia_Relock_bootloader.ftf) you need a stock ftf file!
I have used R800i_4.0.2.A.0.62_phoenixvendor.ftf file before found on this site somewhere might be wrong but would try flashing that file hope it helps.:fingers-crossed:
There is a ftf collection here: http://forum.xda-developers.com/showthread.php?t=1589399
tallman43 said:
Hi I think you are flashing wrong file line 5 (03/044/2013 12:44:33 - INFO - Selected Xperia_Relock_bootloader.ftf) you need a stock ftf file!
I have used R800i_4.0.2.A.0.62_phoenixvendor.ftf file before found on this site somewhere might be wrong but would try flashing that file hope it helps.:fingers-crossed:
Click to expand...
Click to collapse
Cosmicdan's R800i_4.0.2.A.0.62_phoenixvendor.ftf link kere: http://forum.xda-developers.com/showthread.php?t=1817548
Scroll down to the downloads section.
thanks for that information, but i tried flashing 2 files, at first the relock bootloader ftf. because i read somewhere that flashing firmware with open botloader with "OTA" will brick your phone. so i wanted to be save and locked bl before flashing firmware. if you read on into log there is another ftf. and a failure notice. because i tried today so many things, my accu is fully empty (3 times red led blinking) so i hope itll load a bit tonight and i can go on trying to flash cm 9 tomorrow again. but this file should be stock firmware isnt it?: 03/045/2013 12:45:01 - INFO - Selected Xperia Play_Release_Generic UK.ftf
its from uk, im from germany, but only want to boot once and than flash cm9, so i dont worry bout that. last flahing try come further than log posted already i think. ill try flashing that file tomorrow again, cause i think that flashing failed cause of battery was too low.
log of last try:
04/035/2013 09:35:58 - INFO - Device connected in flash mode
04/036/2013 09:36:12 - INFO - Selected R800i_4.0.2.A.0.62_(1253-4437).ftf
04/036/2013 09:36:12 - INFO - Preparing files for flashing
04/036/2013 09:36:40 - INFO - Device disconnected
04/036/2013 09:36:45 - INFO - Device connected in flash mode
04/037/2013 09:37:04 - INFO - Please connect your device into flashmode.
04/037/2013 09:37:05 - INFO - Opening device for R/W
04/037/2013 09:37:05 - INFO - Reading device information
04/037/2013 09:37:05 - INFO - Phone ready for flashmode operations.
04/037/2013 09:37:05 - INFO - Start Flashing
04/037/2013 09:37:05 - INFO - Processing loader
04/037/2013 09:37:05 - INFO - Checking header
04/037/2013 09:37:05 - INFO - Flashing data
04/037/2013 09:37:08 - INFO - Loader : S1_Loader_Root_773f - Version : R4A066 / Bootloader status : ROOTABLE
04/037/2013 09:37:08 - WARN - This file is ignored : simlock.ta
04/037/2013 09:37:08 - INFO - Processing kernel.sin
04/037/2013 09:37:08 - INFO - Checking header
04/037/2013 09:37:08 - INFO - Flashing data
04/044/2013 09:44:23 - INFO - Processing fota1.sin
04/044/2013 09:44:23 - INFO - Checking header
04/044/2013 09:44:23 - INFO - Flashing data
04/044/2013 09:44:24 - INFO - Processing fota0.sin
04/044/2013 09:44:24 - INFO - Checking header
04/044/2013 09:44:24 - INFO - Flashing data
04/044/2013 09:44:28 - INFO - Processing adsp.sin
04/044/2013 09:44:28 - INFO - Checking header
04/044/2013 09:44:28 - INFO - Flashing data
04/046/2013 09:46:51 - INFO - Processing amss_fs.sin
04/046/2013 09:46:51 - INFO - Checking header
04/046/2013 09:46:51 - INFO - Flashing data
04/046/2013 09:46:51 - INFO - Processing amss.sin
04/046/2013 09:46:51 - INFO - Checking header
04/046/2013 09:46:51 - INFO - Flashing data
04/036/2013 12:36:58 - INFO - Ending flash session
04/036/2013 12:36:58 - ERROR - 31 : one connected device doesnt functions.
04/036/2013 12:36:58 - ERROR - Error flashing. Aborted
04/036/2013 12:36:59 - INFO - Device disconnected
(i translated error 31, cuz of it was originaly in german)
I'm sure as long as the led works theres life in it
Maybe battery dead
Sent from my R800i using xda app-developers app
Strange but true, the dreaded red light of death. To fix it u will need a spare micro usb.
→ Cut micro usb on the micro end.
→ Strip back the plastic to expose wires black(negative) red(positive)
→ get sticky tape an connect it to the positive and negative terminals on battery(they are marked)
→ plug it in to wall socket
→ 3hours or so battery should be ready to go
→ phone SHOULD boot normally
Its happened to me and one of my mates. Both our devices fixed this way, but up to u if u want to take the chance of ruining a micro usb
Sent from my GT-I9300 On Official JB
thats a strange way of loading battery. Luckily if got 2 usb cabels for my play, so ill give it a try. but my phone wont boot after doeing this, it will only give me the chance to try to repair it. an mobile without working rom wont boot i think. its unlogical that i cant load a phone without an working rom. i hope i dont make me crunchy if i connect microusb with electricity.
_hacker_ said:
thats a strange way of loading battery. Luckily if got 2 usb cabels for my play, so ill give it a try. but my phone wont boot after doeing this, it will only give me the chance to try to repair it. an mobile without working rom wont boot i think. its unlogical that i cant load a phone without an working rom. i hope i dont make me crunchy if i connect microusb with electricity.
Click to expand...
Click to collapse
Ok goodstuff, just be careful and dont plug phone in untill u have the sticky tape on the battery. When your phone has enough battery then u can flash the ftf via flashtool
Sent from my GT-I9300 On Official JB
there are 4 cabels in my usb cabel, one is red, one black, one green and one gray/white and many metalstripes around them. do i have to connect the green and grey one also, or only the other both?
Off-topic:
how long do i have to do the image verification before i can answer?
EDIT:
i hope i did it right, ill see if i did it or not in a few hours. big thanks to all of you, i hope my play will boot soon
edit 2:
looks good, no explosion yet
_hacker_ said:
there are 4 cabels in my usb cabel, one is red, one black, one green and one gray/white and many metalstripes around them. do i have to connect the green and grey one also, or only the other both?
Off-topic:
how long do i have to do the image verification before i can answer?
EDIT:
i hope i did it right, ill see if i did it or not in a few hours. big thanks to all of you, i hope my play will boot soon
edit 2:
looks good, no explosion yet
Click to expand...
Click to collapse
Good luck! By the way don't think you needed to have the battery in the phone to charge that way?Might damage phone more! Back to original problem can you get into recovery?(once battery full lol) if you can daft question but are you flashing cm9 from zip on sd card?Also can you flash other kernel's with fastboot ,DoomLords,Lupus,etc if you can try some of these and rom's to go with them.Get your phone stable with a rom before trying cm9/10 again.Also don't worry about locking your bootloader again as long as you do not update over the air you will be fine.I think your problems started when you tried to lock your bootloader again.:fingers-crossed:
Ye looks good but u dont needto have battery connected into phone as its the battery your charging.
Let me know how it goes
Sent from my GT-I9300 On Official JB
wedgess said:
Ye looks good but u dont needto have battery connected into phone as its the battery your charging.
Let me know how it goes
Sent from my GT-I9300 On Official JB
Click to expand...
Click to collapse
battery isnt connected to phone, its only laying into
EDIT:
@tallman, thanks, i hope i wont damage all
i flashed kernel and came into bootloader, but it showed failure notice i posted on first page of thread.
i hope i can flash stock firmware with full battery. after that ill try to flash cm9 again.
and yes, originally nonbooting was due to relocked bootloader
Edit2:
didnt worked, 3 red leds are there again. i think the cabels, especially the - cabel hadnt enough contact with the battery. do anyone know any tricks doing this better?
Edit3:
i cut now more of the isolation of the red and black cable away, so that i have more metalcabel to fix it on the battery. lets see if it loads now
If that don't work you can always buy a battery
sent from my Sony Ericsson Xperia Play™(r800x) Running Slimbean 3.0 using Tapatalk 2™
crazymonkey05 said:
If that don't work you can always buy a battery
sent from my Sony Ericsson Xperia Play™(r800x) Running Slimbean 3.0 using Tapatalk 2™
Click to expand...
Click to collapse
i dont wanna buy a new battery if theres any other way.
maybe that would work: Sony Ericsson EP900
problem is that i cant find it anywhere. its on amazon, but its not available. buying a new battery isnt a problem itself, but i would like to buy it at a store, not via internet. and i cant find an market where i can buy an battery for xplay
Edit:
i hope it works now. i couldnt fix the cabels on the battery contacts with tape. now i pressed them onto the contacts and pushed battery into my phone. so theres an constant pressure and it loads hopefully
Weird I had same flashtool error the other day but it while flashing phoenix ftf and seemed to still be working, wonder if it windows 8 causing issues for me, different version of flashtool?
Sent from my R800i using Tapatalk 2
fma965 said:
Weird I had same flashtool error the other day but it while flashing phoenix ftf and seemed to still be working, wonder if it windows 8 causing issues for me, different version of flashtool?
Sent from my R800i using Tapatalk 2
Click to expand...
Click to collapse
ive got win 7, and what version of flashtool do u have? i hope i can flash stock firmware today. Yesterday i couldnt do that because flash- and fastboot modes were only stable for 20 seconds or so, after this time green/blue led expired and my phone didnt showed any action
EDIT:
i think battery charged now, but i think also that i cut the wrong micro usbcable. one is thin and long, one is thick and big. i cut the short one because i thought they are the same cable. now my netbook doesnt installs the drivers for the cable, it only says "unknown device". with the other cable that i cut it worked. so ill have to buy a new cable and a new battery if i can find them anywhere. i hope ill be able to go to the nearest city where i can buy one. this will take some time because im living far away of next city, and my mother, wich drives there at least once a week is sick at the moment. so i havent got the opportunity to buy one the next few days :-c
Edit 2:
i got an new usb cable now. i was able to unlock bootloader and flash cm9kernel. now im trying to flash stock firmware just to make sure that my phone still works normally. than ill try to flash cm9 completely
Edit3:
cm9 runs now. great! bit i cant write anything with the virtual keyboard, and an phone without keyboard is completely useless. can anyone help me making the keyboard opening?
last edit:
the bug that my keyboard didnt opened was because i installed the wrong gapps. i installed jelly bean gapps, with ics gapps all works perfect
for returning to CM 9
_hacker_ said:
Hi,
plz help me make my phone working again. I wanted to flash cm 10 after manged to flash cm9. cm 9 ran after trying everything out for hours. Today i downloaded cm10 and flashed the kernel. after that i wasnt able to open the bootloader, so i flashed cm9 kernel again. That worked so far. i was able to open bootloader again, but it showed an failure notice whilst installing cm 9.
"assert failed: getprop ("ro.product.device") == "r800i" ......" this is copied with the endings r800i/a/at and zeus
E: Error in sd /sdcard/cm-9.1.0-zeus.zip
(Status 7)
Installation aborted.
I tried it a few times. Flashed cm 10 kernel, flashed cm9 kernel back, but its always the same failure notice. I would like to use cm9 again, it was good at all, but i wanted to update cm10 today. Please give me an how-to what to do unbricking my play.
Click to expand...
Click to collapse
I think you are very new to mod world and suggest you that first know the terminology of mobile developing fully like kernel, ROM, bootloader, factory (or Stock ROM) , baseband, android versions, custom ROM, what CM is actually etc etc before trying to kill ur phone!!!!(joking)...
same happened to me before a few days on my xperia play R800i phone but I was successful in restoring it back to CM 9.1.0 after unsuccessful try of restoring it to factory(Stock) ROM that came with it from sonyericsson.
Though there are many more experienced memebers but try mine at least once no harm...
1. make sure ur battery is full or 70% at least
2. put the CM9 ROM u downloaded in SD card in home directory(home means just put inside SD without making any folder on SD card)
3. enter into recovry mode (i assume you have clockworkmod recovery already installed)
4.do factory wipe/reset and then cache wipe
5.do dalvik cache wipe (u can do step 4 & 5 one or two times just to be in safe side)
6.install zip file CM9 (make sure you have stable version only) from SD card
7. reboot phone
I hope you should be successful now step 4 & 5 is important to wipe any mess that was created by CM10 if not successful then move the battery from phone wait for about 2-3 minutes and try again above steps u should succeed. good luck!!

[Q] How to install LuPuS-JBv6 on xperia arc S

Hello as the title says I need to help installing THIS I dont quite get how to install it so if you could please baby step me on this will be much appreciated
I have an experia
ARC S lt18i
Android Version 4.0.4
Kernel 2.6.32.9-perf
[email protected] #1
Build Number 4.1.B.0.587
is rooted
superuser
xparts installed
flashtools
drivers installed too
Win7 if relevant
not sure if any more info is needed but I'll be happy to add what is needed
thanks in advance for all your help
Raps
Rapsody10 said:
Hello as the title says I need to help installing THIS I dont quite get how to install it so if you could please baby step me on this will be much appreciated
I have an experia
ARC S lt18i
Android Version 4.0.4
Kernel 2.6.32.9-perf
[email protected] #1
Build Number 4.1.B.0.587
is rooted
superuser
xparts installed
flashtools
drivers installed too
Win7 if relevant
not sure if any more info is needed but I'll be happy to add what is needed
thanks in advance for all your help
Raps
Click to expand...
Click to collapse
Open Flashtool and select Fastboot mode
In the next window, select 'Select kernel to Flash'
Browse and select the .img file (LuPuS-JBv6-ARC&S.img). This will flash the kernel.
Also, move the wifi modules zip file (anzu-LuPuS-jB-v6-wifi_cm-ti-wlan_signed.zip) to SD card and then flash it via CWM
Reboot and enjoy LuPuS kernel
ela703 said:
Open Flashtool and select Fastboot mode
In the next window, select 'Select kernel to Flash'
Browse and select the .img file (LuPuS-JBv6-ARC&S.img). This will flash the kernel.
Also, move the wifi modules zip file (anzu-LuPuS-jB-v6-wifi_cm-ti-wlan_signed.zip) to SD card and then flash it via CWM
Reboot and enjoy LuPuS kernel
Click to expand...
Click to collapse
Thank you very much
I'm charging my phone in order to install LuPus
is there any rom you will advice to install after this kernel ?
should the kernel format my SD card ? for ext4 support ?
thanks again for your help and advice
Raps
mmmm
It seems I did something worng did not let me do it
here is the log
24/032/2013 19:32:31 - INFO - Flashtool Version 0.9.10.1 built on 2013-01-09 19:49:47
24/032/2013 19:32:31 - INFO - You can drag and drop ftf files here to start flashing them
24/032/2013 19:32:40 - INFO - Device connected with USB debugging on
24/032/2013 19:32:41 - INFO - Connected device : LT18
24/032/2013 19:32:41 - INFO - Installed version of busybox : N/A
24/032/2013 19:32:41 - INFO - Android version : 4.0.4 / kernel version : 2.6.32.9-perf / Build number : 4.1.B.0.587
24/032/2013 19:32:42 - INFO - Root Access Allowed
24/032/2013 19:32:50 - INFO - Launching Fastboot Toolbox 1.0 by DooMLoRD
24/032/2013 19:32:50 - INFO - Device Status: ADB mode
24/032/2013 19:32:52 - ERROR - This action can only be done in fastboot mode
24/033/2013 19:33:20 - ERROR - This action can only be done in fastboot mode
24/033/2013 19:33:30 - INFO - Launching Fastboot Toolbox 1.0 by DooMLoRD
24/033/2013 19:33:30 - INFO - Device Status: ADB mode
24/033/2013 19:33:33 - ERROR - This action can only be done in fastboot mode
24/033/2013 19:33:48 - INFO - Please wait device is rebooting into fastboot mode (via ADB)
24/033/2013 19:33:51 - INFO - Device will soon enter fastboot mode
24/033/2013 19:33:51 - INFO - Device disconnected
24/033/2013 19:33:54 - INFO - Device connected in fastboot mode
24/034/2013 19:34:01 - INFO - Finished Fastboot Toolbox
24/034/2013 19:34:20 - INFO - Selected kernel (boot.img or kernel.sin): C:\Flashtool\firmwares\LuPuS_ARC-S_v6-jb2.img
24/034/2013 19:34:20 - INFO - Flashing selected kernel
24/034/2013 19:34:20 - INFO - sending 'boot' (6294 KB)...
24/034/2013 19:34:20 - INFO - FAILED (remote: The Device must be rooted first)
24/034/2013 19:34:20 - INFO - finished. total time: 0.002s
24/034/2013 19:34:20 - INFO - FASTBOOT Output:
sending 'boot' (6294 KB)...
FAILED (remote: The Device must be rooted first)
finished. total time: 0.002s
24/034/2013 19:34:20 - INFO - Please check the log before rebooting into system
Any advice will be appreciated
Raps
Did you unlocked the bootloader?
eeeeeerrrrrr
that is a good question
I might not have
which lead to the next question how to find out and how to do it if is not
Raps
Rapsody10 said:
eeeeeerrrrrr
that is a good question
I might not have
which lead to the next question how to find out and how to do it if is not
Raps
Click to expand...
Click to collapse
If you don't know, you didn't unlocked. You'll have to search a little, but a good start point is here: http://forum.xda-developers.com/showthread.php?t=2067008
It's your call to unlock or not... Unlock bootloader may void the warranty plus loose the DRM Keys (if you unlock via Sony Method). But unlocking is the only way to install Custom Kernels.
If you choose to keep it locked, you'll have to use only roms that are compatible with stock kernel (GB, ICS).
Thank you
I'm reading about the "unlocking" procedure
once is done can I revert it ? like flashing rom or something like that ?
Raps
OK I have unlooked the bootloader
am I supposed to "re-root" the phone after that ?
since I'm using "4.1.B.0.587" will need to downgrade again then
use DooMLoRD_v1_Xperia-2011-ICS-ROOT-emu-busybox-su
then reflash "4.1.B.0.587"
then fastboot lupus ?
thanks in advance for your help
Raps
Rapsody10 said:
OK I have unlooked the bootloader
am I supposed to "re-root" the phone after that ?
since I'm using "4.1.B.0.587" will need to downgrade again then
use DooMLoRD_v1_Xperia-2011-ICS-ROOT-emu-busybox-su
then reflash "4.1.B.0.587"
then fastboot lupus ?
thanks in advance for your help
Raps
Click to expand...
Click to collapse
Since it's unlocked (and I don't remember the steps, so I dunno if you have to reboot or not), just follow the instructions from ela703's post to install the kernel.
You just have to pay attention to the fact that this lupus kernel is designed for JB roms (eg: ParanoidAndroid 2.57). Probably comes with root and CWM, so you won't have to worry with root and CWM anymore.
(You only need doomlord's toolkit to root phones with stock kernel/locked bootloader).
After you flash the new kernel, just keep pressing 'vol down' and you'll enter in CWM with the .zip of the rom of your choice in your sdcard (again: if you use this kernel, look for JB roms). Thenceforth, follow the install instructions in the corresponding thread of your rom.
have installed lupus and also ParanoidAndroid seems to be working ok so far some problems with the camera but I think nothing mayor
I dont feel particulary faster thgovernor is set to 134 and 1401 or something like that
set it on smarassv2 tried ondemand first
thank you all for all your help
Raps
Use quick image is convenient
Rapsody10 said:
have installed lupus and also ParanoidAndroid seems to be working ok so far some problems with the camera but I think nothing mayor
I dont feel particulary faster thgovernor is set to 134 and 1401 or something like that
set it on smarassv2 tried ondemand first
thank you all for all your help
Raps
Click to expand...
Click to collapse
Camera is a problem in all JB ROMs. But it works so thats the main thing at leasst it does on CM. Intellidemand2 is probably fastest but drains battery, smatassv2 is best for performance and battery life.
For full working camera you should go back to ICS, I also got a kernel for that. To your question about relocking bootloader why would you want to. If you want to go back to STOCK just flash an FTF via flashtool.
wedgess said:
Camera is a problem in all JB ROMs. But it works so thats the main thing at leasst it does on CM. Intellidemand2 is probably fastest but drains battery, smatassv2 is best for performance and battery life.
For full working camera you should go back to ICS, I also got a kernel for that. To your question about relocking bootloader why would you want to. If you want to go back to STOCK just flash an FTF via flashtool.
Click to expand...
Click to collapse
Hello
thanks for the info
I'm going to evaluate it at least for a week to get the real day by day with it
I definitely agree with you about smatassv2 is the best for performance and battery life went from 22 hours or so on ICS to 2 days 9 hours ( 32 % left ) at the time of writing this post
I might try your ICS kernel and see how different they are
about the re-locking was only to be be sure could be undone.
at the moment the performance is brilliant I only miss my 16:9 pics that I cannot take and a few "minor" things but then there must be some sort of compromise I guess
Thanks again and open to your suggestions
Raps

[Q] something gone wrong when flashing

So here's what I did so far... The bootloader was unlocked, so I rooted the phone, installed clockwork. I spent hours reading about kernels and the different roms but wasn' really getting anywhere. Since my phone needed to be taken to get repaired anyway I decided to just choose a rom and install it from the guide i was using.
I backed up using clockwork, formatted and installed, and it said it was fine. But when I reboot it just hangs on the Sony Ericsson screen, have to take battery out to turn it off....what can I do now? I can't load the backup image because it won't let me load clockwork. did this happen because I didn't install a custom kernel first?
renvaar said:
So here's what I did so far... The bootloader was unlocked, so I rooted the phone, installed clockwork. I spent hours reading about kernels and the different roms but wasn' really getting anywhere. Since my phone needed to be taken to get repaired anyway I decided to just choose a rom and install it from the guide i was using.
I backed up using clockwork, formatted and installed, and it said it was fine. But when I reboot it just hangs on the Sony Ericsson screen, have to take battery out to turn it off....what can I do now? I can't load the backup image because it won't let me load clockwork. did this happen because I didn't install a custom kernel first?
Click to expand...
Click to collapse
flash another kernel (supported for your rom always)
boot on cwm
factory reset
mounts and storage > format system
advanced > wipe dalvik cache
advanced > wipe battery stats
flash your desirable rom, flash wifi modules and try again fresh
renvaar said:
So here's what I did so far... The bootloader was unlocked, so I rooted the phone, installed clockwork. I spent hours reading about kernels and the different roms but wasn' really getting anywhere. Since my phone needed to be taken to get repaired anyway I decided to just choose a rom and install it from the guide i was using.
I backed up using clockwork, formatted and installed, and it said it was fine. But when I reboot it just hangs on the Sony Ericsson screen, have to take battery out to turn it off....what can I do now? I can't load the backup image because it won't let me load clockwork. did this happen because I didn't install a custom kernel first?
Click to expand...
Click to collapse
Your kernel is stock and bootloader locked? If so then download pc companion and do a repair and if your bootloader is unlocked then download a stock ftf file for your phone and flash it with flashtool. I had exactly same problem with flashing custom firmwares on my Arc s but after few tries I realized that i need to format every partition excluding sdcard in a "mounts and storage" sub-menu.
---------- Post added at 11:31 AM ---------- Previous post was at 11:29 AM ----------
Retrosid said:
flash another kernel (supported for your rom always)
boot on cwm
factory reset
mounts and storage > format system
advanced > wipe dalvik cache
advanced > wipe battery stats
flash your desirable rom, flash wifi modules and try again fresh
Click to expand...
Click to collapse
I think his bootloader is locked because he lost a recovery after flashing new rom. His CWM was probably installed with x-parts.
as I said... it wont let me go as far as being able to load up clockwork...
thanks pypcier, I'm trying flashtool now... but I get this error...
18/036/2013 18:36:40 - INFO - Device disconnected
18/036/2013 18:36:53 - INFO - Device connected in flash mode
18/037/2013 18:37:03 - INFO - Selected LT15i_4.0.2.A.0.42_Generic Global.ftf
18/037/2013 18:37:03 - INFO - Preparing files for flashing
18/037/2013 18:37:03 - INFO - Please connect your device into flashmode.
18/037/2013 18:37:03 - INFO - Opening device for R/W
18/037/2013 18:37:03 - INFO - Reading device information
18/037/2013 18:37:03 - INFO - Phone ready for flashmode operations.
18/037/2013 18:37:03 - INFO - Current device : LT15i - CB5A1FEFCM - 1247-1061_R7D - 1241-4324_4.0.2.A.0.42 - WORLD-1-8_4.0.2.A.0.42
18/037/2013 18:37:03 - INFO - Start Flashing
18/037/2013 18:37:03 - INFO - Processing loader
18/037/2013 18:37:03 - INFO - Checking header
18/037/2013 18:37:03 - INFO - Ending flash session
18/037/2013 18:37:03 - ERROR - ERR_SEVERITY="MAJOR";ERR_CLASS="SECURITY_CLASS";ERR_DYNAMIC="SIN header verification failed"
Can you tick a "no final verification" box and try again?
it changes to this if i check the button...
18/052/2013 18:52:28 - INFO - Selected LT15i_4.0.2.A.0.42_Generic Global.ftf
18/052/2013 18:52:28 - INFO - Preparing files for flashing
18/052/2013 18:52:28 - INFO - Please connect your device into flashmode.
18/052/2013 18:52:29 - INFO - Opening device for R/W
18/052/2013 18:52:29 - INFO - Reading device information
18/052/2013 18:52:45 - INFO - Unable to read from phone after having opened it.
18/052/2013 18:52:45 - INFO - trying to continue anyway
18/052/2013 18:52:45 - INFO - Start Flashing
18/052/2013 18:52:45 - INFO - Processing loader
18/052/2013 18:52:45 - INFO - Checking header
18/052/2013 18:52:45 - INFO - Ending flash session
18/052/2013 18:52:45 - ERROR - Error in processHeader : 2 : The system cannot find the file specified.
18/052/2013 18:52:45 - ERROR - Error flashing. Aborted
18/052/2013 18:52:45 - INFO - Device disconnected
EDIT: it did that the first time, then i try the same way again and it gives me the previous error. would an older ftf make a difference?
You are sure that your bootloader is unlocked? Have you ever flashed a custom kernel using fastboot? If yes then try to flash custom kernel with recovery. If this wont help then try to update and reinstall your flashtool and download newest stock ftf for your phone.
I'm pretty sure it is, as I remember having a similar problem a long time ago and flashing it. problem is I don't have the old files i used before, and I can't find any downloads that work in my country..
Error code from your flashtool log looks like there is a problem with acquiring permission to flash a firmware and that suggests that your bootloader is locked. Try to download pc companion from sony site and do a repair. If your bootloader is locked this will restore your phone to stock and if your bootloader is unlocked then pcc wont recognize your phone.
just tried pc companion. it asks me to swipe the bar down, but as I can't get past the logo it wont work. so repair just hangs there...
What bar... I don't understand what you are talking about. For a repair with pc companion you don't even need to turn on your phone you just click update button and then small blue "repair" text in a popup window then firmware is downloaded and you are asked to turn off your phone and connect usb cable while holding a back button.
I found your previous thread and It looks like your bootloader is unlocked because OTA update bricked your phone. I have a link to a ftf you used last time to repair your phone http://forum.xda-developers.com/showthread.php?t=1324707 (its inside of this archive with complete but outdated flashtool and drivers) but you should try a pcc first so we will be sure if your bootloader is locked or not.
renvaar said:
just tried pc companion. it asks me to swipe the bar down, but as I can't get past the logo it wont work. so repair just hangs there...
Click to expand...
Click to collapse
Use this http://developer.sonymobile.com/201...ocked-xperia-smartphones-video-beta-download/ if your bootloader is unlocked it will return it to stock if it does not connect it means your bootloader is locked.It is a new beta tool from sony for the arc:good:
tallman43 said:
Use this http://developer.sonymobile.com/201...ocked-xperia-smartphones-video-beta-download/ if your bootloader is unlocked it will return it to stock if it does not connect it means your bootloader is locked.It is a new beta tool from sony for the arc:good:
Click to expand...
Click to collapse
Wow its great I hadn't heard of this before.
pypcier said:
Wow its great I didn't heard of this before.
Click to expand...
Click to collapse
Yep it's a good tool to return to stock and also to check if your bootloader is unlocked (Because it only works on unlocked bootloaders) Arc & couple other devices are supported but they are going to make more devices available:good:
pypcier said:
Wow its great I hadn't heard of this before.
Click to expand...
Click to collapse
You would have had you browsed the stickys.
XperienceD said:
You would have had you browsed the stickys.
Click to expand...
Click to collapse
I'm not going to read through every new sticky just to make you happy.
pypcier said:
I'm not going to read through every new sticky just to make you happy.
Click to expand...
Click to collapse
Mines been there while, and People shouldn't read them to please anyone, they should read them, especially when new, to LEARN.
Sent from Myushi

Categories

Resources