[Q] Baseband Upgrade Led to Bootloop (X10a) - XPERIA X10 Q&A, Help & Troubleshooting

Hey guys, I think i made a pretty nub mistake just now, and im just looking for a solution at this point. I have an x10a on At&t, and I finally got fed up enough with 1.6 to try and update to 2.1 or higher. First option was the official update that came out at the end of May, so i went ahead and downloaded pc companion and attempted an update. Companion recognized the phone fine, but when i hit update, it said my phone was "up to date" which is BS, i was on 1.6 under the phone's settings. IDK why it didnt recognize it as 1.6 (possibly due to a failed root attempt i had done a few months back) but regardless, i went onto xda to find an alternative.
This led me to flashtool and the noob guide. went through it, downloaded the at&t baseband update, as well as the generic 2.1 update and the tool itself. I wasnt sure about the order, so i went ahead and just installed the baseband update first. (i dont remember the exact numbering of the original baseband, but it was something like 1.xx.xxx, as far as i remember...) flashtools flashed 2.1.65 (X10a - AT&T) successfully, but once i was suppose to unplug the USB cable, restart the phone, and enable the debugging mode, the phone was already bricked. It now boots to the white lettered 'Sony Ericsson' on a black background, then the screen goes dark, and the LED in the top right corner turns white, and the process repeats.
Help me out guys!
Much appreciated.

You have to flash generic firmware 2.1.A.0.435 first. Then if you really want baseband 2.1.65, you flash it over firmware. I don't recommend flashing the AT&T 2.1.65 baseband, because there are known text message problems and it limits data to 3G. You will get "H"-HSPA or 3.5G.
Btw, the baseband is not a separate requirement from the firmware. The firmware includes the designed baseband. The baseband on X10A generic 2.1.A.0.435 firmware is 2.1.54, which works great for ATT and you will be ready for the official 2.3.3 Gingerbread update directly from SE when available.
Here's a good noob thread for updating ATT X10a.....
http://forum.xda-developers.com/showthread.php?t=1012380

Good to go, thanks so much. finally satisfied with my phone!

Not me. upgraded 2.1 to2.2 using flashtool and now..
random_people said:
Good to go, thanks so much. finally satisfied with my phone!
Click to expand...
Click to collapse
Hi, glad you sorted your problem. Mine is stuck in a boot loop.
when I connect in flash mode with flashtool displaying its screen, the tool detects my x10a and does its stuff...trying to install busybox ..etc. I have attached a cut n paste into text file for a log of what is happening.
the disconnects are the phone.. not me unplugging.
the phone has not got any motherboard probs. its restarts are soley due to this flashtool fail.
now put a second log with debug level selected

Related

[Q] In dire need of help

Hey, I'm not entirely sure this is the right place to post, but here I go -
I was originally on Nordic Generic firmware when I first tried to upgrade to 2.1 through PCC.
The update failed at 100% and I was left with the bricked icon. I tried to update through SEUS and the update was successful, however the phone never booted up after 10 minutes of blinking.
I tried to update again through SEUS, this time it failed. My first thought was to flash back to the Generic Nordic firmware but I kept getting the brick icon.
So I downloaded the XIOFUB.rar file and it successfully flashed and my phone booted. Version: R1FA016. Now that the phone at least booted up I though, hey.. let's try to update trough SEUS and at least go back to R2BA026. Update failed, phone bricked.
I tried the XIOFUB with R2BA026 .sin files, successful flash, bricked phone.
Now, what options am I left with? What can I do to successfully get my 2.1?
Edit: Even tried upgrading OTA through R1FA016. Even then it bricked...

Flashing Home and Menu Lights

Hello Everyone,
Earlier I tried rooting my phone with a file I downloaded that was named r2-4399-6601-streak-superboot.zip. Basically, it worked, however I'm having the problem where the Menu and Home buttons alternate flashing very fast. Also, my menu sometimes stays lit up while the other two are dark.
Does anyone know what I can do to fix this problem? As far as I know I am still running the stock rom with the stock baseband. If it helps, I am at build number 6601, my baseband version is GAUSB1A111231-US. My OEM version matches my Baseband, except for the -US on the end. My kernel version is 2.6.29-perf and my firmware version is 1.6
Factory restore did nothing for me, that was the first thing I tried.
If anyone can help me get rid of this annoyance that would be great. I'm trying not to update my phone to O2's 2.1 rom as I am looking forward to the 2.2 update from Dell. I'll gladly unroot my phone if needed, if someone can tell me how...
hey, there is a known problem with flashing for anyone that has upgraded to dj_steves v1.2.0 & above espcially when using rebelsim as the baseband is not compatible yet. Other than that... your description sounds just like an app i got from the market called "streakLED" which flashes all different patterns on the buttons when you receive an sms text? My home button also stays lit when i have a message.
Not sure if this helps at all but i thought i would suggest it just incase
Sent from my Dell Streak
http://www.streaksmart.com/2010/08/superboot-root-method-works-with-att-dell-streak-build-6601.html
I've been to that link... But the only fix the guy had was to install 2.1. I don't feel like going through the trouble of doing that. especially since the 2.2 update is coming soon. I feel like it might just cause trouble for me.
What suxs is that at leats urs turns on a the way my just got stuck on the Dell logo an never finishes powering on an I get the flashing buttons as well..
check the stickies thread and factory reset ur phone then use "UNIVERSAL ANDROOT" you wont get the flashing lights if you root with that app.
oh and it usually takes two or sometimes three tries to acquire root
I had this problem also. It is caused by upgrading to a new ROM which is meant for a certain baseband (00 for unlocked Streaks, 21 for UK (I believe) Streaks and 31 for US Streaks) without actually upgrading the baseband as well. For me, it has been a mystery to figure out what the sequence is to get from one baseband to another and one ROM to another. I had this problem flashing lights problem with one Streak when I tried the flash it from one ROM/baseband to another in order to get 2.2 flashed properly (You can't go from AT&T 1.6 directly to DJ Steves 1.5.1). The only thing that fixed it for me was using the QDL Tool. It took my dead Streak with flashing light with God-only-knows what baseband and ROM sequence I had tried to a fully functioning, unlocked Streak with AT&T official 2.2. From there, it was an incredibly simple flash to DJ Steve's 1.5.1 using fastboot. Then I was done. Give the QDL Tool a try if you want 2.2 and it very well might take your phone from dead and worthless to something worth carrying around in your pocket.
yeah the qdl tool is by far the most simple way to get 2.2 on you streak, which you can root without any worries. i dont think theres actually a reason to still be on 1.6.

[Q] X10 flash issue?

Today I finally got around to try and flash my X10 phone that AT&T refuses to update. I really went into this not really knowing what i was doing, so basically I was throwing this at wall here not knowing what'll happen. So I got a firmware .ftf file and a baseband file put it into my firmware folder and the flashtool said everything was alright. So now my X10 just goes through an endless loops of the boot logo for Sony Ericsson and then goes black screen and a blue LED (supposedly this is the Push-to-Talk LED) shows up. So now I'm wondering.. how exactly do I restore factory default on it without being able to go into the phone itself?
Just want to put this out there, I did use the search function but got no results, probably my internet giving me trouble
Thanks in advance for any help!
Use SEUS to restore to AT&T 1.6 first,
then go to the flashtool post to find a 2.1 global generic firmware to flash into your phone.
I think there are youtube tutorial vids showing you how to do so.

Bricked X10a

I got this phone from ebay, and it worked a few days before I flashed it so I know it's not hardware or a bad flash on their part because it was stock when I got it. Anyway, I flashed the generic fw through flashtool and it was working fine for awhile until one day it froze and nothing was responsive. The battery died, and I recharged it and threw it into flash mode to repair the firmware through SEUS, and it got it working for awhile until it happened again. So instead I went ahead and used flashtool to put AT&T's fw back on the phone. After I did that, the phone now only vibrates when I turn it on and then does nothing. If it does do something, it just continuously vibrates until I pull the battery. I tried using SEUS and Flashtool to flash another fw because I can get it to flash mode, but it says failed everytime no matter what firmware I use. And SEUS fails right up front when trying to repair. Any ideas?
Pull out the battery....plug the usb cable...run latest flash tool...click on flash button..when it is searching for the fone then put back the battery with pressing the return key.
Recheck the latest driver for 2.3.3
Did it work?
Dude are you aware of rooting procedures?
First you should flash the stock rom back in, then you flash some pre-rooted GB rom. Threads on X10 Android Development are full of options.
jeancca said:
Dude are you aware of rooting procedures?
First you should flash the stock rom back in, then you flash some pre-rooted GB rom. Threads on X10 Android Development are full of options.
Click to expand...
Click to collapse
Dude did you even read my post?
I've been a member here for 3 years and have been flashing Android to phones ever since then. I have looked at the troubleshoots but they were all giving a failed flash. Not to mention this has nothing to do with root or GB, I was talking stock firmware, this brick happened before SE pushed out the GB update.
To subhanker.ds, thank you for the input, I'll give it a shot.
EDIT: Just got the same error
Uploaded with ImageShack.us
As per your screen shot, debugging mode is of....but it is not possible to on now as ur phone is dead.
I think somehow jeancca is correct...use rooting process..(no need to flash any rom)..it will automatically turn on debugging mod & then you flash ur rom...
Hope ur prob will be solved dear...
I've tried several rooting methods that and they all state I should turn on Unknown Sources and Debugging. But I cannot do this, is there a way that will force it into usb debugging as you said?
Actually at the time of flashing debugging mode automatically turn on...
Anyway i'm not getting any clue...although you can try to flash only system.sin file.then see what will happen....best of luck...
I've tried everything I can think of and I still can't get it to work. A new symptom has came up though, when I try and connect it to my PC, it will go into flash mode but after awile the LED goes off but is still recognized by the PC as being in flash mode. Same goes for when I plug it into the charging cable.
Bump.
Sorry for doing it, but is there anyone out there that can help me?! I had to think I have a $200 paperweight.
Hi..... I mentioned this on another post but thought I might see if this might help you. Although I didn't mention the use of other Flashtools in the other thread, I did end up trying Flashtool 2.8.0 and 2.9.1 and the latest edition. In the end I ended up going with the 2.8.0 to start fresh and since that was the one that was used for An Android 2.1, I flashed back to 2.1. With a few instances like those you mention I tried this and worked out.
What I did was open my devices and printers (control panel) and noticed the SEMC USB or IDE blah blah......The device pops up when connecting my phone. I would flash my phone and the go to the "Turn on phone and check debug" and ..... Same as you green light (Flash) would go on and then nothing.
What I did was unplug my phone and Uninstall the device used (SEMC USB or IDE, it named itself differently on an occasion or two) and then started my Flashtool then tried again. Goto Flashtool and prepare your Flash and wait for it to load up (took some time once or twice but....) connect your phone and try again.
I have been messing around with a bunch of apps and FW's and ROMS and lately Unlocking the BootLoader.
Some you can just goto Task Manager and Stop the ADB.exe processes but this uninstall worked excellent for me when needed.
Hope this solves your issue. Good Luck. Oh you may not need the other Flashtools but I have them on file just in case because 2.9.1 gave me a problem before when doing something. You might be able to do with whatever Flashtool you are using but just thought I would share my experience.
I have the same problem . i I flashed it with X10i rom but work for while and after 1 or 2 hours hanged and when i remove the battery it's hang in sony ericsson .
After that I flashed it with SEUS and upgrade to official rom 2.3.3
and has the same problem .DO THINK IT IS A HARDWARE PROBLEM
Tingles said:
Hi..... I mentioned this on another post but thought I might see if this might help you. Although I didn't mention the use of other Flashtools in the other thread, I did end up trying Flashtool 2.8.0 and 2.9.1 and the latest edition. In the end I ended up going with the 2.8.0 to start fresh and since that was the one that was used for An Android 2.1, I flashed back to 2.1. With a few instances like those you mention I tried this and worked out.
What I did was open my devices and printers (control panel) and noticed the SEMC USB or IDE blah blah......The device pops up when connecting my phone. I would flash my phone and the go to the "Turn on phone and check debug" and ..... Same as you green light (Flash) would go on and then nothing.
What I did was unplug my phone and Uninstall the device used (SEMC USB or IDE, it named itself differently on an occasion or two) and then started my Flashtool then tried again. Goto Flashtool and prepare your Flash and wait for it to load up (took some time once or twice but....) connect your phone and try again.
I have been messing around with a bunch of apps and FW's and ROMS and lately Unlocking the BootLoader.
Some you can just goto Task Manager and Stop the ADB.exe processes but this uninstall worked excellent for me when needed.
Hope this solves your issue. Good Luck. Oh you may not need the other Flashtools but I have them on file just in case because 2.9.1 gave me a problem before when doing something. You might be able to do with whatever Flashtool you are using but just thought I would share my experience.
Click to expand...
Click to collapse
Thanks a lot, I will give this a shot as soon as I get home. I'll keep my fingers crossed that this may help me and the others having this sort of issue.
Mobark, I don't think it's a hardware issue. For awhile I was thinking it was a dead screen, but from the people I have heard that did indeed have dead screens, they have lines in the center of the screen while my screen just doesn't turn on.
Hi everyone i am having the same problem my phone only vibrates for sec and the green led just flash for sec than nothing but my phone goes into flash mode but the flash aborts i have also made a thread in which i fully listed my progess and software i used http://forum.xda-developers.com/showthread.php?t=1257581
Nope, didn't seem to work. I think my problem is the phone doesn't want to stay in Flash mode for some reason.
I fix this error, i download and flash this, next i updated in SEUS, my phone is Xperia Play
Sorry for my bad english.
Ok, so I upgraded to 3.0.0 and tried flashing the generic fw again to no avail. And as far as above, the firmware isn't for the x10, it's for the Play, Arc, and Neo.
This is what i did
Not sure if this will work for you but this is how I fixed my phone.
When I first changed the rom on my phone i was on baseband 435. I never changed the baseband with the custom rom install.
My friend factory erased the phone and then it would take 45 - 50 mins to finish booting (would turn on i would see se logo and 50 mins later I'd get to a stock "slide to unlock screen" upon doing so i would get a black bg with the custom batt meter and clock at the top. it also dected the sd wasnt plugged in.
While the phone was on, Sony Ericsson pc Companion would say please mount sd card, and that i couldnt do.
While trying to use flashtool 2.9.1 it would say please put the phone in debuggign mode.
At this point, your ss shows you making it further than i did. because mine wouldnt make it past the date/time (yours starts flashing an fails some way through).
I tried 4 roms and none of them worked.
Then i found http://www.multiupload.com/9H20YEXEHR and After updating to flash tool 3.0.0, and using the stock rom that i posted the link to, It worked. but i had to try a few times. At http://forum.xda-developers.com/showthread.php?t=920746 There are 3 different stock roms for x10a (I used the first one in the x10a list)
I used the one that matched my baseband. Try an match yours if you know it.
When i connected usb, the phone would not turn on. The phone would only turn on with batt in. So i connected usb, held back and put batt in.
Doing this worked, I held the back button until the flash completed.
Also as a note, I did not change the bootloader, that could be why it would boot after 50 mins or so.
I hope this helps.
-Mike

[Q] Xperia Ray locked bootloader, 2.3.4 OTA update bricked phone

Hi guys, I've had a look around for this, but I can only find the solution for bootloaders that are unlocked. I suspect my Ray WASN'T unlocked. I accepted the OTA 2.3.4 update, thinking it would be fine. But the phone now shows the exclamation mark. I can get into both the recovery and fastboot modes (green/blue LED).
None of the recovery solutions are working for me. Is there a way for me to fix this, or will the phone have to go to a Sony Ericsson shop.
The official PC software from SE won't restore it either.
it is wise to go to sony shop , they will fix it
Not sure if this will solve your problem, but it solved mine:
The problem was with the bootloader. So I tried FlashTool_0.2.9.1_FOTAUnbrick which brings a small firmware information to reset the bootloader.
The problem I was having was to be able to correctly connect the phone to the flash tool. My phone's USB connection was constantly going up and down. So I decided to uninstall all the tools and drivers and install them from scratch.
In short, here's what I did.
Installed Update_Service_Setup-2.11.10.7.exe from sony ericcsson in order to get the USB drivers to work.
Followed the instructions of the Update_Service and flashed the latest update available for my phone (2.3.4). This didn't solve the startup problem, just installed the latest update.
I ran the Update_Service again and restarted the process has if I was going to flash again, but after the Update_Service detected the phone I canceled the installation. (I did this just to make sure the phone was connected in FlashBoot)
Then I installed FlashTool_0.2.9.1_FOTAUnbrick.exe, opened the folder of the application and ran X10FlashTool.exe
Hit Flash button and the program opens a Firmware Selection window with a preloaded firmware with two reseting contents (loader.sin, preset.ta). Hit OK button and waited until the program indicated the flash process was finished. The process of flashing takes a few minutes and we need to be patient. It might even seem like it's doing nothing but we just have to wait.
After finishing the flash process the program invited me to disconnect the phone and turn it on. I did so and the phone took probably a minute or so to startup. At first I thought it didn't solve the problem, because it was taking so long to start, but it did solve! So I waited patiently and the Sony Ericsson logo showed up giving me a new hope. After that I had to wait another 4 or 5 minutes for the phone to finish applying the new firmware mentioned in point 2. (There's no visual information of the conclusion process so you might wonder the phone might have hung.) Just waited and everything got back to normal with the benefits of the new firmware 2.3.4 (instead of the previous 2.3.3).
I hope it helps someone having the same issue.
xperia ray said:
it is wise to go to sony shop , they will fix it
Click to expand...
Click to collapse
Might not fall under warranty.
http://forum.xda-developers.com/showthread.php?t=1568792, check my tutorial, there is a guide to unbricking.

Categories

Resources