please help me guys!
I've flashed my phone from 1.6 to 2.1 using generic firmware, but after the flash, my phone doesn't want to start up and it's not being recognised by seus..I'm going crazy...i feel the vibration when I try to power on, but that's it, nothing happens..tried to relflash but it's not working..help pls!
I tried to reflash it and do it all over again, the procedure finished but still after pressing the power button, I feel it vibrate and it doesn't boot up..nothing is happening..how can I sort this problem out?? I loved my phone, please don't tell me I've bricked it :'(
**** man, I'm in the same boat
The screens backlighting starts up and it flickers every few seconds but that's it. I've suesed it, x10 flashed it and repeated. Nothing, nadda, zip
I'll be back as soon as I have some more news...
Just used Bin4ry's jerpelea's old X10 flash to flash back to generic nordic 1.6 (026) FW.
MY PHONE LIVES
It's running now so I'm gonna do a SEUS update and see what happens.
hey buddy have you got a link for that??
I got it here before the update came out: http://forum.xda-developers.com/showthread.php?t=683793
the flash tool is in the third post, and just pick a 1.6 rom from the second post.
Just updated with SEUS and everythings sweet now
Hope you get it sorted too.
I have to try again from work as from home since I'm on 64bit Win 7 java is not working (
so what I need to do is download the flash tool
download a 1.6rom (which I've done)
plug into flash mode xperia and hope for the best??
( I've got a bad feeling about this
Mind explaining what you did, exactly? 'Cause I tried running the flashtool and i got "cannot find batch file, Win7 64". =[
I don't know what you guys are worried about -- if it's not working just keep trying -- you're either miss timing things or doing it wrong.
On x64 versions of windows make sure all JVM (Java versions) are uninstalled and just install the 32bit version. Make sure that java directory shows up in your paths section of Environment Variables (Control Panel -> System -> Advanced).
Dont unpack the flasher somewhere with a weird directory structure like C:\My Stuff\Some-Place\x10
Just put it somewhere simple like C:\x10flash to keep any spaces or special characters from possibly breaking any of the batch files.
Most importantly you have to be sure you're actually getting the phone into flash mode -- otherwise you get errors.
Plug the usb cable into the phone, pull the battery, hold the back button, put in battery and plug in the usb just after -- the green led flashes if you got it right (I think -- I don't have my x10 here right now).
It's VERY hard to actually permanently brick one of these phones IMO without doing something incredibly wrong.
I'm definitely in flash mode.
I tried flashing both 2.1 global generic and the 1.6 rom, however none are working. With 2.1 the phone doesn't boot, with 1.6 the phone doesn't boot and keeps vibrating.
What I've done is copied the sin files in the rom folder into the flash folder and run flash.bat and then connect the phone in flash mode. The procedure ends normally, but something is going terribly wrong. I'm sure I'm doing everything right.
I've now downloaded the seus update service and reinstalled the software and finally the phone managed to boot but I'm back on 1.6
I guess there is something wrong in the files?? Oh well at least I didn't brick my phone, but this makes me highly uncomfortable trying the 2.2 custom rom when it's out.
I had the same problem and tried just about everything.
The only thing that worked was the ROOT_F3v3 uploaded
by jerpelea here.
It's a 1.6 version German version and if everything goes fine you can change the CDA
to match the one you like and have 2.1 using SEUS.
thecrazyfarang said:
I'm definitely in flash mode.
I tried flashing both 2.1 global generic and the 1.6 rom, however none are working. With 2.1 the phone doesn't boot, with 1.6 the phone doesn't boot and keeps vibrating.
What I've done is copied the sin files in the rom folder into the flash folder and run flash.bat and then connect the phone in flash mode. The procedure ends normally, but something is going terribly wrong. I'm sure I'm doing everything right.
I've now downloaded the seus update service and reinstalled the software and finally the phone managed to boot but I'm back on 1.6
I guess there is something wrong in the files?? Oh well at least I didn't brick my phone, but this makes me highly uncomfortable trying the 2.2 custom rom when it's out.
Click to expand...
Click to collapse
If with 1.6 the phone boots and keeps vibrating it means you flashed the update that does not include the full version. Don't do this again!
Technically the flash tool is also a "unbricker" so if used according to the instructions it really should not be a problem. I suggest you go through the instructions again to see where your problem might be, as suggested above.
BingoRingo said:
Technically the flash tool is also a "unbricker" so if used according to the instructions it really should not be a problem. I suggest you go through the instructions again to see where your problem might be, as suggested above.
Click to expand...
Click to collapse
Theoretically, you're right. But I had the same problem last night (after doing something I really shouldn't have ). It was the first time I'd had this flavour of brick, but I have had plenty of others and have reflashed numorous times. Still, I reflashed with the old flash tool to 1.6 and still had a brick, repaired with seus 3 times and still had a brick, and flashed three times with the new X10 Flash for 2.1. Still no dice... and I did do everything right, like I said, it's not the first time I've done this.
Flash number 8 with the old flash tool (same procedure and same firmware as flash no. 1) and my phone is back. Rebooted it and then updated to 2.1 with seus and now I'm all sorted.
Just had to say this, because it's not always the user doing something wrong
BingoRingo said:
If with 1.6 the phone boots and keeps vibrating it means you flashed the update that does not include the full version. Don't do this again!
Technically the flash tool is also a "unbricker" so if used according to the instructions it really should not be a problem. I suggest you go through the instructions again to see where your problem might be, as suggested above.
Click to expand...
Click to collapse
I've followed the instructions and I've been very careful as it was my very first time doing this and I've been reading quite a lot before I took the step. The 1.6rom I've downloaded I got it from the link of jerpelea. Most probably the 1.6 global generic and the 2.1 global generic roms have a missing file or something.
I didn't try flashing to Nordic as I thought it will do the same again. As I said, now I'm a little bit reluctant to flash my mobile again and will have to wait for the bastards at SE to release the update for my region.
_calum_ said:
Theoretically, you're right. But I had the same problem last night (after doing something I really shouldn't have ). It was the first time I'd had this flavour of brick, but I have had plenty of others and have reflashed numorous times. Still, I reflashed with the old flash tool to 1.6 and still had a brick, repaired with seus 3 times and still had a brick, and flashed three times with the new X10 Flash for 2.1. Still no dice... and I did do everything right, like I said, it's not the first time I've done this.
Flash number 8 with the old flash tool (same procedure and same firmware as flash no. 1) and my phone is back. Rebooted it and then updated to 2.1 with seus and now I'm all sorted.
Just had to say this, because it's not always the user doing something wrong
Click to expand...
Click to collapse
Wow mate, you really are persistent. I'm glad it worked for you. I think I've flashed 5 times in total and I was praying my lucky star to make the bloody thing boot and I was sooooo relieved when I managed to boot after repairing with seus.
Try this. 2.1 (Rogers FW) tool.
2nd post down by hehh. Saved my phone.
http://forum.xda-developers.com/showthread.php?t=838967&page=2
Related
http://forum.xda-developers.com/showthread.php?t=805112
I had Streakdroid 1.80.
Follow the directions above but only the last OC 1.6 to At&t 1.6
Make sure you have OEM recovery flashed. Streakmod etc wont work.
Put the 3 files on your current system. And the new rom on the SD.
Flash the boot.ing as instructed and then restart your current rom. After it finishes turn on development in the applications settings. Then reboot into recovery. Then install from update.apk this will install the new AT&T rom. If if fails flash boot.img again and repeat.
FYI: the new 340 does not look any different then the 318 or 170 for that matter.
DJ's roms are better and faster. But if OEM is your desire do this.
I'm on 2.2 318 and am trying to go back to stock 1.6 but after extracting all the system files to the sd, completing the steps for that and flashing the new boot.img- I can't get my Streak to boot fully into Android to apply the 1.6 update.... If I try to boot it sticks at the Dell logo, no animation, just the logo with all 3 soft keys lit. If I go into Recovery and try to apply the update, I get a signature verification failure error. I also tried a factory reset from Recovery but cannot get passed the logo.
I have done this a trillion times before without any issues. Why won't it cooperate now? I have one of the temperamental Streaks that only likes Official Stock ROMs. I get FCs and freezes out the whazoo on anything but so thats why I am going to Stock AT&T 1.6 and update to their 2.2...
rnj79 said:
I'm on 2.2 318 and am trying to go back to stock 1.6 but after extracting all the system files to the sd, completing the steps for that and flashing the new boot.img- I can't get my Streak to boot fully into Android to apply the 1.6 update.... If I try to boot it sticks at the Dell logo, no animation, just the logo with all 3 soft keys lit. If I go into Recovery and try to apply the update, I get a signature verification failure error. I also tried a factory reset from Recovery but cannot get passed the logo.
I have done this a trillion times before without any issues. Why won't it cooperate now? I have one of the temperamental Streaks that only likes Official Stock ROMs. I get FCs and freezes out the whazoo on anything but so thats why I am going to Stock AT&T 1.6 and update to their 2.2...
Click to expand...
Click to collapse
Try using the repair tool that will put a 2.2 rom on it.
You don't have to go to stock 1.6. Just follow the instructions on your current system and it will let the new AT&T 2.2 install. I always to a factory reset before installing a new rom. That stops FCs for me.
derechbennoach said:
http://forum.xda-developers.com/showthread.php?t=805112
I had Streakdroid 1.80.
Follow the directions above but only the last OC 1.6 to At&t 1.6
Make sure you have OEM recovery flashed. Streakmod etc wont work.
Put the 3 files on your current system. And the new rom on the SD.
Flash the boot.ing as instructed and reboot into recover. It will install the new AT&T rom. If if fails flash boot.img again and repeat.
FYI: the new 340 does not look any different then the 318 or 170 for that matter.
DJ's roms are better and faster. But if OEM is your desire do this.
Click to expand...
Click to collapse
Hi -
Could you be more specific on "OEM recovery"?
I have downgraded from 318 all the way back to US OEM 1.6 with BB of 31 which matches OEM version. Build number 6601. btw: I had to do a Nandroid flash to get it to 1.6.
It downloads the 340 update fine but gets hung up on the install process - stuck on logo.
Seems like I need to flash the right recovery but I always get a blank screen when I boot into recovery and choose update from SD card.
Can you link me to the right recovery file?
Thanks.
derechbennoach said:
Try using the repair tool that will put a 2.2 rom on it.
You don't have to go to stock 1.6. Just follow the instructions on your current system and it will let the new AT&T 2.2 install. I always to a factory reset before installing a new rom. That stops FCs for me.
Click to expand...
Click to collapse
I do have a 2.2 rom installed already. I used the QDL tool to get it there so I shouldn't have to do it again... I tried updating to AT&T's new 2.2 yesterday from the 2.2 (318) I am currently on but it won't let me. I thought I had to go back down to 1.6 and get my update via notification but now my Streak wont get off the logo.
I hope this is making sense because from what you said, I don't think it does. Its hard to type what my problem is in a way that all can understand.
I am on Rogers and had the same problem. Was on 2.2 through QDL tool. I got an email from Rogers that their official 2.2 update was now available.
Downloaded the update, it wouldn't install.
Probably because baseband is different?
Anyway, did the same thing, tried downgrade back to O2's 1.6, then hopefully AT&T's 1.6, but got stuck after getting down to 2.1. Black screen during update.pkg, Dell logo only when just doing a normal boot.
Tried loading 1.6, 2.1 Rom's again to no avail.
Managed to get the phone working again using the QDL tool to get back to 2.2.
Tried doing the Rogers update again, but not working.
Help!
eugenekim618 said:
I am on Rogers and had the same problem. Was on 2.2 through QDL tool. I got an email from Rogers that their official 2.2 update was now available.
Downloaded the update, it wouldn't install.
Probably because baseband is different?
Anyway, did the same thing, tried downgrade back to O2's 1.6, then hopefully AT&T's 1.6, but got stuck after getting down to 2.1. Black screen during update.pkg, Dell logo only when just doing a normal boot.
Tried loading 1.6, 2.1 Rom's again to no avail.
Managed to get the phone working again using the QDL tool to get back to 2.2.
Tried doing the Rogers update again, but not working.
Help!
Click to expand...
Click to collapse
I can't get mine to boot normal unless I use the QDL tool to pull it out of the logo screen. If we already have a US Basdeband we shouldn't have to upgrade to O2 and back down again, right?
What do the people, like myself, do who are on the 2.2 318 via QDL Tool build to get the AT&T 2.2 rom released yesterday?? I am already on a US AT&T rom so what sense does it make to have to upgrade to an O2 rom and go back to AT&T (I am thinking out loud...).
I don't want Steve's ROM or anything else... my phone does not play well with those. I want the new official 2.2 released to AT&T locked Streaks.
rnj79 said:
I do have a 2.2 rom installed already. I used the QDL tool to get it there so I shouldn't have to do it again... I tried updating to AT&T's new 2.2 yesterday from the 2.2 (318) I am currently on but it won't let me. I thought I had to go back down to 1.6 and get my update via notification but now my Streak wont get off the logo.
I hope this is making sense because from what you said, I don't think it does. Its hard to type what my problem is in a way that all can understand.
Click to expand...
Click to collapse
There are three files that need to be in place. and a boot.img file that is installed from fastboot.
http://forum.xda-developers.com/showthread.php?t=805112
Look at what he says to do the the 1.6 non at&t rom and do that to any 2.2 and it worked.
But really 318 is that same thing. and Streakdroid 1.8.0 is 100% better.
eugenekim618 said:
I am on Rogers and had the same problem. Was on 2.2 through QDL tool. I got an email from Rogers that their official 2.2 update was now available.
Downloaded the update, it wouldn't install.
Probably because baseband is different?
Anyway, did the same thing, tried downgrade back to O2's 1.6, then hopefully AT&T's 1.6, but got stuck after getting down to 2.1. Black screen during update.pkg, Dell logo only when just doing a normal boot.
Tried loading 1.6, 2.1 Rom's again to no avail.
Managed to get the phone working again using the QDL tool to get back to 2.2.
Tried doing the Rogers update again, but not working.
Help!
Click to expand...
Click to collapse
I finally bought root Explorer from the market. If there is a free alternative that can change your /system file to r/w (read/write) I could not find one.
You [email protected]!!!!!!!!! (no other alternative, dont think you are smarter than anybodye else, is non-negotiable) to move the 3 files over into your /system file, because the update will not go through. It says there is a "device mismatch" (or something like that). I tried to short circuit all the processes at every step and was unable to beat the system.
Heres what ya gotta do:
1. Follow the part about downgrading to 1.6, then check for software update.
If you have upgraded to ANY other version of 2.2 ya gotta move the 3 files over.
http://forum.xda-developers.com/show...92&postcount=4
Finally I gotta say that it is not worth all the fuss really. You lose tethering and installing outside apps. You gain nothing.
This release is best for djSteve, because he can take all the good parts of this build and put into his next release of streakdroid.
derechbennoach said:
There are three files that need to be in place. and a boot.img file that is installed from fastboot.
http://forum.xda-developers.com/showthread.php?t=805112
Look at what he says to do the the 1.6 non at&t rom and do that to any 2.2 and it worked.
But really 318 is that same thing. and Streakdroid 1.8.0 is 100% better.
Click to expand...
Click to collapse
I have done all that, many many times before and it has always worked but this time it isn't working. I have done the root explorer thing. My phone will not boot passed the logo after all the steps have been completed. I cannot figure out whats causing the problem. I have downgraded to US AT&T 1.6 several times in the past with the method you and everyone else state but this time I am getting nowhere.
rnj79 said:
I have done all that, many many times before and it has always worked but this time it isn't working. I have done the root explorer thing. My phone will not boot passed the logo after all the steps have been completed. I cannot figure out whats causing the problem. I have downgraded to US AT&T 1.6 several times in the past with the method you and everyone else state but this time I am getting nowhere.
Click to expand...
Click to collapse
I hosed mine to a black screen that would not turn on.
The repair tool would not get it going.
I found streakflash I tried to get a link, I'll keep looking.
I launched steakflash.
I pulled the battery put battery and back on. As I plugged in the cable I held the UP volume button. Streakflash recognised it and I ran it through.
That got me back up. I forget what ROM it was. I then ran repair tool.
That puts 2.2 pre release.
If I can do it anyone can.
rnj79 said:
I have done all that, many many times before and it has always worked but this time it isn't working. I have done the root explorer thing. My phone will not boot passed the logo after all the steps have been completed. I cannot figure out whats causing the problem. I have downgraded to US AT&T 1.6 several times in the past with the method you and everyone else state but this time I am getting nowhere.
Click to expand...
Click to collapse
http://streakdroid.com/downloads/djsteve/
Use this I bricked mine and it fixed it.
Put it in diagnostic mode.
Battery out battery and back on.Start software.
Plug in cable holding up volume.
It saved mine.
derechbennoach said:
http://streakdroid.com/downloads/djsteve/
Use this I bricked mine and it fixed it.
Put it in diagnostic mode.
Battery out battery and back on.Start software.
Plug in cable holding up volume.
It saved mine.
Click to expand...
Click to collapse
Thats what I'm trying to say... the only way I can get out of the logo is by doing this. I am on the pre-release of 2.2 as of now but I want to downgrade to AT&T 1.6 and back to the new AT&T 2.2 rom but it wont cooperate with me. Whenever I try, I get the silly logo and have to use QDL to get me unstuck.
rnj79 said:
Thats what I'm trying to say... the only way I can get out of the logo is by doing this. I am on the pre-release of 2.2 as of now but I want to downgrade to AT&T 1.6 and back to the new AT&T 2.2 rom but it wont cooperate with me. Whenever I try, I get the silly logo and have to use QDL to get me unstuck.
Click to expand...
Click to collapse
Ok. Forget going to 1.6. Download the Rom and the files and. OTA won't work.
Follow the instructions and put the three files and the boot.ing on your 2.2 Rom.
Put the new update.pkg on the sd
Reboot recovery select to instal and it will install it.
I have done this twice.
Sent from my Dell Streak using XDA App
derechbennoach said:
Ok. Forget going to 1.6. Download the Rom and the files and. OTA won't work.
Follow the instructions and put the three files and the boot.ing on your 2.2 Rom.
Put the new update.pkg on the sd
Reboot recovery select to instal and it will install it.
I have done this twice.
Sent from my Dell Streak using XDA App
Click to expand...
Click to collapse
It will not work!! I keep getting the status 7 error which then sends it to reboot but never gets pass the logo! The only way to get out of the logo is to pull the battery and use QDL to put me back at 318.
Whats the malfunction with this? I have always managed to update in the past. Why won't this one go through?
First off I did quick scan of this post so if I am repeating I apologize in advance. You MUST go back to AT&T 1.6 with no Streakmod or Clockwork need Dell recovery program. 340 does a scan as it loads and if finds you modified the Steak in anyway stops the install. I had to purchase Root Explorer to complete my conversion, only thing I can say is Root Explorer is worth the money, as for 340, if you are running Steve's ROM with no problems stay with it. Here is the link to the instructions I used, http://forum.xda-developers.com/showpost.php?p=8558692&postcount=4, good luck.
Same Problem
BigBopper said:
Hi -
Could you be more specific on "OEM recovery"?
I have downgraded from 318 all the way back to US OEM 1.6 with BB of 31 which matches OEM version. Build number 6601. btw: I had to do a Nandroid flash to get it to 1.6.
It downloads the 340 update fine but gets hung up on the install process - stuck on logo.
Seems like I need to flash the right recovery but I always get a blank screen when I boot into recovery and choose update from SD card.
Can you link me to the right recovery file?
Thanks.
Click to expand...
Click to collapse
I have the same problem with BigBopper too. Anyone have any idea to fix it?
vanemburghj said:
First off I did quick scan of this post so if I am repeating I apologize in advance. You MUST go back to AT&T 1.6 with no Streakmod or Clockwork need Dell recovery program. 340 does a scan as it loads and if finds you modified the Steak in anyway stops the install. I had to purchase Root Explorer to complete my conversion, only thing I can say is Root Explorer is worth the money, as for 340, if you are running Steve's ROM with no problems stay with it. Here is the link to the instructions I used, http://forum.xda-developers.com/showpost.php?p=8558692&postcount=4, good luck.
Click to expand...
Click to collapse
If you install the three files and flash the boot.img file to a 2.2 rom and have the new 340 apk as update.apk on the sd it will install. I have done it twice. Once from 1.7.0.and once from the pre release 2.2.
BUT it is not worth the trouble. 318 is a better stock rom.
Sent from my Dell Streak using XDA App
derechbennoach said:
If you install the three files and flash the boot.img file to a 2.2 rom and have the new 340 apk as update.apk on the sd it will install. I have done it twice. Once from 1.7.0.and once from the pre release 2.2.
BUT it is not worth the trouble. 318 is a better stock rom.
Sent from my Dell Streak using XDA App
Click to expand...
Click to collapse
I could not be more serious right now when I tell you mine would not work that way... I had to go from 318 2.2> O2 2.1> O2 1.6 and am FINALLY booting into AT&T 1.6 as I type. A lot of people have Streaks that aren't able to do as yours did, mine is one of them. I don't know if its because my Streak is an older one, I bought it in August, or what the deal is but I was not joking!
All is well though. I have finally gotten it back to Stock AT&T 1.6 with my original baseband of 31. Now I shall see if I can go to the new AT&T Froyo...
rnj79 said:
I could not be more serious right now when I tell you mine would not work that way... I had to go from 318 2.2> O2 2.1> O2 1.6 and am FINALLY booting into AT&T 1.6 as I type. A lot of people have Streaks that aren't able to do as yours did, mine is one of them. I don't know if its because my Streak is an older one, I bought it in August, or what the deal is but I was not joking!
All is well though. I have finally gotten it back to Stock AT&T 1.6 with my original baseband of 31. Now I shall see if I can go to the new AT&T Froyo...
Click to expand...
Click to collapse
Good to hear. Mine is white one. I bricked it twice and have brought it back. I know I am not smarter maybe just lucky.
Good luck.
Sent from XDA app using Streakdroid 1.8.0
SO. i had the red LED of death thing, i fixed that part but now pretty much with my xperia i can flash ONLY 1.6. if i try to flash with flashtool with firmwares 2.1 my phone will only vibrate and blank screen. whereas once i flash to 1.6 the touchscreen is completely unresponsive. i tried updating with SEUS. SEUS says there are updates that can be installed, after i install the updates the my phone wouldnt turn on at all. but will just vibrate for a second. and here's another thing, i can plug it and use SEUS once more and the same thing happens, it will say there is an update. i was wondering if anyone has a solution ?? =.=
by the way. when i flash it at 2.1 it will always be detected in flash mode with my pc.
Sounds like it may be a dead battery if SEUS didn't work.
agentJBM said:
Sounds like it may be a dead battery if SEUS didn't work.
Click to expand...
Click to collapse
it's not actually. when it is at 1.6 firmware i can actually charge it. right now it's at 100%
What flash tool and firmware version are you using?
Edit: Here's acurrent thread for updating from 1.6 to global generic 2.1.A.0.435....
http://forum.xda-developers.com/showthread.php?t=1012380
lams09 said:
SO. i had the red LED of death thing, i fixed that part but now pretty much with my xperia i can flash ONLY 1.6. if i try to flash with flashtool with firmwares 2.1 my phone will only vibrate and blank screen. whereas once i flash to 1.6 the touchscreen is completely unresponsive. i tried updating with SEUS. SEUS says there are updates that can be installed, after i install the updates the my phone wouldnt turn on at all. but will just vibrate for a second. and here's another thing, i can plug it and use SEUS once more and the same thing happens, it will say there is an update. i was wondering if anyone has a solution ?? =.=
by the way. when i flash it at 2.1 it will always be detected in flash mode with my pc.
Click to expand...
Click to collapse
i have the same problem :/... IS THERE A SOLUTION FOR THIS DAMN phone... stupid touchscreen doesnt even work when my phone is on 1.6 ==
Try another pc. I know XP SP3 has issues with usb drivers.
agentJBM said:
Try another pc. I know XP SP3 has issues with usb drivers.
Click to expand...
Click to collapse
this doesnt help :/
everything works. 1.6 is functional now, but the thing is, is that i cant upgrade to 2.1 =[
there are 2 versions of generic 2.1: 2.1 and 2.1 update 1. try to find the first one(older) and flash that first. that one you can root with z4root.apk, just make sure after the do initial flash with flashtool, unplug, boot, select 'unknown sources' 'debugging mode' then download z4root(search on xda) and root. then install xrecovery, and change to whatever ROM you desire
Sent from my X10 using XDA Premium App
I had this problem for MOTHS!!! It was so annoying and frustrating. At the time it seemed like I was the only one having this problem as I started when only nordic was available. I strugged for 3 days trying to flash 2.1, then I gave up and stayed with 1.6 until like 4 days ago when I decided to freaking either toss the phone or make it work because there are no apps for 1.6.
Anyway, I fixed it. What I did was. Find all the latest firmwares for different regions (use only latest) here on XDA. I had like 3 different ones downloaded. Then I flashed each of them with the flash tool (latest stable). After every flash i waited about 30 min for the phone to turn on (the first flash time I waited 3 hours), if it didn't work, I launched SEUS, and re-flashed the phone and waited 30 min again. If that didn't work, I launched flashtool and flashed another region. Then SEUS... and so on. After like 3 flashes the phone started (last flash was SEUS). I think the generic world F/W worked. I can share F/W that I was trying with flashtool if you are interested.
EDIT: Here, maybe you'll find it useful: http://www.mediafire.com/?8c1590tb9to01
m00nman said:
I had this problem for MOTHS!!! It was so annoying and frustrating. At the time it seemed like I was the only one having this problem as I started when only nordic was available. I strugged for 3 days trying to flash 2.1, then I gave up and stayed with 1.6 until like 4 days ago when I decided to freaking either toss the phone or make it work because there are no apps for 1.6.
Anyway, I fixed it. What I did was. Find all the latest firmwares for different regions (use only latest) here on XDA. I had like 3 different ones downloaded. Then I flashed each of them with the flash tool (latest stable). After every flash i waited about 30 min for the phone to turn on (the first flash time I waited 3 hours), if it didn't work, I launched SEUS, and re-flashed the phone and waited 30 min again. If that didn't work, I launched flashtool and flashed another region. Then SEUS... and so on. After like 3 flashes the phone started (last flash was SEUS). I think the generic world F/W worked. I can share F/W that I was trying with flashtool if you are interested.
EDIT: Here, maybe you'll find it useful: http://www.mediafire.com/?8c1590tb9to01
Click to expand...
Click to collapse
is the link you provided with the firmware or flashtool >> ?
ill try this method when im home
Here is a detailed step by step guide for noobs on updating from 1.6 to global generic 2.1.A.0.435 with dualtouch. It has links and instructions for everything you need. It is based on X10A. If you have X10i, just use the X10i firmware instead. By using global generic firmware you will also be set up for the official 2.3.3 Gingerbread update directly from SE when available.
http://forum.xda-developers.com/showthread.php?t=1012380
m00nman said:
I had this problem for MOTHS!!! It was so annoying and frustrating. At the time it seemed like I was the only one having this problem as I started when only nordic was available. I strugged for 3 days trying to flash 2.1, then I gave up and stayed with 1.6 until like 4 days ago when I decided to freaking either toss the phone or make it work because there are no apps for 1.6.
Anyway, I fixed it. What I did was. Find all the latest firmwares for different regions (use only latest) here on XDA. I had like 3 different ones downloaded. Then I flashed each of them with the flash tool (latest stable). After every flash i waited about 30 min for the phone to turn on (the first flash time I waited 3 hours), if it didn't work, I launched SEUS, and re-flashed the phone and waited 30 min again. If that didn't work, I launched flashtool and flashed another region. Then SEUS... and so on. After like 3 flashes the phone started (last flash was SEUS). I think the generic world F/W worked. I can share F/W that I was trying with flashtool if you are interested.
EDIT: Here, maybe you'll find it useful: http://www.mediafire.com/?8c1590tb9to01
Click to expand...
Click to collapse
ill try it now. ill let yuo know how it goes. thanks
denenatse said:
there are 2 versions of generic 2.1: 2.1 and 2.1 update 1. try to find the first one(older) and flash that first. that one you can root with z4root.apk, just make sure after the do initial flash with flashtool, unplug, boot, select 'unknown sources' 'debugging mode' then download z4root(search on xda) and root. then install xrecovery, and change to whatever ROM you desire
Sent from my X10 using XDA Premium App
Click to expand...
Click to collapse
ive downloaded so many firmwares lol. and i flashed those also to no avail =[
agentJBM said:
Here is a detailed step by step guide for noobs on updating from 1.6 to global generic 2.1.A.0.435 with dualtouch. It has links and instructions for everything you need. It is based on X10A. If you have X10i, just use the X10i firmware instead. By using global generic firmware you will also be set up for the official 2.3.3 Gingerbread update directly from SE when available.
http://forum.xda-developers.com/showthread.php?t=1012380
Click to expand...
Click to collapse
thanks but ive been through the guide allready, it's the same results no matter what. for some reason it just seems that something is preventing my phone from flashing to 2.1, whereas 1.6 is perfectly fine
lams09 said:
thanks but ive been through the guide allready, it's the same results no matter what. for some reason it just seems that something is preventing my phone from flashing to 2.1, whereas 1.6 is perfectly fine
Click to expand...
Click to collapse
It's flashtool with all the firmwares I tried. For all the people who try to suggest different guides for flashing, they don't work. I don't know why, but they don't. i had tried everything possible including flshing different 1.6 f/w's and then upgrading with SEUS and PC Companion, flashing 2.1 with flashtool, flashing different version of 2.1. The only thing that worked, was what i described.
m00nman said:
It's flashtool with all the firmwares I tried. For all the people who try to suggest different guides for flashing, they don't work. I don't know why, but they don't. i had tried everything possible including flshing different 1.6 f/w's and then upgrading with SEUS and PC Companion, flashing 2.1 with flashtool, flashing different version of 2.1. The only thing that worked, was what i described.
Click to expand...
Click to collapse
how long did it it after the last flash til the phone turned on ?
To be honest I don't know as I left the phone on my desk. I know for sure it wasn't longer than 20 min. I also made sure my sd card had nothing on as SE support says if it had data, it would take longer for the phone to turn on.
hmm it didnt work =l
Can you try a different cable and/or a different computer? I remembered i did it on my laptop instead of the desktop. Laptop is running Windows 7 32bit, and it never had SEUS installed prior to this.
I'm just throwing different ideas to you as i know how frustrating it is. Maybe something will work. I guess i was just lucky to get it to work.
Sent from my X10i using XDA Premium App
Can't seem to find a problem quite like mine...
I have two different X10a-s in the US, both purchased from at&t. Both running generic 2.1 which I installed using flashtool a while back.
When the Gingerbread update was released, I changed the build.prop file to allow the installation of 2.3 for the US Generic firmware.
The first phone installed GB perfectly... Rooted... and everything works perfectly.
The second phone installed GB, but put me into a bootloop. I am unable to even start the setup wizard, not to mention do anything else on the phone. It reboots as soon as the unlock screen appears.
Reading other people's suggestions with posts about bootloops, I decided to re-install 2.3 using SEUS... Same issue... I then downloaded the ftf file and re-installed 2.3 using flashtool... Same issue... I then decided to downgrade to 2.1 ... however, when I try to flash 2.1 (using flashtool 0.2.8 or 0.2.9) I receive an error, flash aborted.
Any suggestions for me? Thanks so much in advance!
Realized that my intention wasn't very clear after re-reading my post.
I would like to have 2.3 on the second phone. I was going to downgrade to 2.1 simply to try and re-install 2.3.
Sorry for the confusion!
joshuagtgym said:
Realized that my intention wasn't very clear after re-reading my post.
I would like to have 2.3 on the second phone. I was going to downgrade to 2.1 simply to try and re-install 2.3.
Sorry for the confusion!
Click to expand...
Click to collapse
Turn the phone off, get the firmware you wanna install and take the battery out of the phone, get flashtool 3.0.0...
Open up flashtool, click flash and choose the firmware file you wish to flash.(note you have to put the .ftf file into the flashtool firmware folder)
After selecting this, click okay, flash tool will prepare files, when it ask to plug the phone in, put the usb cable in properly, holding the back button, put the battery in while still holding it, once the window to plug your phone it disappears, you can take your finger off the button and wait till flashtool does it's work.
Report back any issue.
Used flashtool 3 to flash 2.3 again... This time the phone will not boot at all... It vibrates when i turn the phone on, but never displays anything (waited several minutes)
Tried flashing to 2.1 using flashtool 3... but when i press flash, choose the 2.1 firmware, hit ok... nothing happens... The program doesn't do anything...
joshuagtgym said:
Used flashtool 3 to flash 2.3 again... This time the phone will not boot at all... It vibrates when i turn the phone on, but never displays anything (waited several minutes)
Tried flashing to 2.1 using flashtool 3... but when i press flash, choose the 2.1 firmware, hit ok... nothing happens... The program doesn't do anything...
Click to expand...
Click to collapse
You tried the same method I previously stated to flash back to 2.1? Did you do something you're not telling us, like say....try to unlock your bootloader?
No... I'm not even sure what the benefits would be to unlocking a bootloader...
So no... all I did was try to update to 2.3 using the exact same method as I did with phone #1 (and everything worked perfectly on that one)
---------- Post added at 08:05 PM ---------- Previous post was at 07:59 PM ----------
I did use flashtool 3 to try and flash 2.3 again... Boots now... But back to the bootloop...
please check my guide, I hope it helps
http://forum.xda-developers.com/showthread.php?p=17501453#post17501453
try ahomads post and download the older flashtool herehttp://forum.xda-developers.com/showthread.php?t=920746 and downgrade to generic 2.1 check this post so u can grab the right firmware to upgrade to 2.3 http://forum.xda-developers.com/showthread.php?t=1186045, then upgrade using pc companion
After several attempts (and several errors), I was able to flash 2.1 back onto the phone using Flashtool 2.8. The phone booted perfectly.
check this post so u can grab the right firmware to upgrade to 2.3
Click to expand...
Click to collapse
Knowing that I would have to change the build.prop file to 1233-8200 to allow me to install 2.3 (2.1 shows a different code, however, I am in the US and this code has worked for many people, including myself on the other X10 that I own), I decided to try and re-flash 2.1 using SEUS (I know it seems like overkill, but I thought it might shed some insight into the root of the problem and save time instead of getting right back into a bootloop).
When trying to re-install 2.1 using SEUS, the status bar goes to about 98% or so and then gives me a "installation failed errror." Now the phone gives me a "!" with a triangle around it.
I have had and used this phone since 1.6 with no issues... I have installed 2.1 before using SEUS with no issues... What got screwed up when I went to 2.3? Any more suggestions on a fix?
At this point, I am going to re-flash 2.1 using flashtool 2.8, then change the build.prop file to 1233-8200 and try using SEUS to flash 2.3 again... Will post the results later.
Thanks to everyone in the community who has helped thus far!
joshuagtgym said:
After several attempts (and several errors), I was able to flash 2.1 back onto the phone using Flashtool 2.8. The phone booted perfectly.
Knowing that I would have to change the build.prop file to 1233-8200 to allow me to install 2.3 (2.1 shows a different code, however, I am in the US and this code has worked for many people, including myself on the other X10 that I own), I decided to try and re-flash 2.1 using SEUS (I know it seems like overkill, but I thought it might shed some insight into the root of the problem and save time instead of getting right back into a bootloop).
When trying to re-install 2.1 using SEUS, the status bar goes to about 98% or so and then gives me a "installation failed errror." Now the phone gives me a "!" with a triangle around it.
I have had and used this phone since 1.6 with no issues... I have installed 2.1 before using SEUS with no issues... What got screwed up when I went to 2.3? Any more suggestions on a fix?
At this point, I am going to re-flash 2.1 using flashtool 2.8, then change the build.prop file to 1233-8200 and try using SEUS to flash 2.3 again... Will post the results later.
Thanks to everyone in the community who has helped thus far!
Click to expand...
Click to collapse
Why don't you just use flashtool and install 2.3.3 1233-8200 ftf file since it's also available right here, full stock if thats what you want and modded versions.
Why don't you just use flashtool and install 2.3.3 1233-8200 ftf file since it's also available right here, full stock if thats what you want and modded versions.
Click to expand...
Click to collapse
Have done that several times... I get stuck in a bootloop...
After several more attempts of flashing 2.3 using flashtool 3... One finally worked...
After flashing successfully, I tried to root the device. During the root, I received an error "uname: permission denied"... I followed the suggestions from this thread here (http://forum.xda-developers.com/showthread.php?t=1196808&page=18) which says:
...try this:
In FlashTool, click 'Advanced' in the menu bar.
Select 'Root.'
Choose 'Force psneuter.'
Click to expand...
Click to collapse
And that finished the root...
After rooting I went into Market to begin downloading my apps... After about the 3rd or 4th app was installed, now I'm right back to the bootloop.
you will need to use this one "X10a AM-US GENERIC 1233-8200" which can be found HERE
Just put the ftf file into the firmware folder of the flashtool and flash... stock SE 2.3.3
---------- Post added at 06:01 PM ---------- Previous post was at 05:48 PM ----------
oops.. nevermind i didnt see the posts above i just saw the ones on the first page. sorry
[Q] Rooted x10a stuck at "se" screen; SEUS, Flashtool not helping. What's next?
Working on my wife's AT&T x10a. When she got it several months ago it came with 1.6, and I updated to 2.1 through PC Companion. She recently decided she wanted root, so yesterday morning I rooted with SuperOneClick 1.5.5, after trying a couple of newer versions with no success. Root Checker from Play Store confirmed root. She said she really wanted 2.2 or 2.3, so this morning I started looking at installing a new rom.
1. Installed Flashtool according to this thread.
http://forum.xda-developers.com/showthread.php?t=928343
It recognized my phone, and appeared to have the needed drivers. I installed CWM via Flashtool, again it appears successfully.
2. Using Flashtool, and the instructions and files in this thread
http://forum.xda-developers.com/showthread.php?t=1192152
I attempted to install 2.3.3 via the Recovery method mentioned. It appeared to be going fine, I followed the instructions completely, but after step 13, when it's time to restart device, it loads the "sony ericsson" logo on the black screen, and hangs there. I left it for 15 minutes or so to see if anything happened, but nothing.
3. I then attempted to go back to stock 2.1 with SEUS, but it wants me to pull down the tray and hook up USB and tick Debugging. Well if the phone is stuck at boot there's no way for me to do that.
4. Attempted to flash x10a generic 2.1 from this thread
http://forum.xda-developers.com/showthread.php?t=920746
but ended up stuck at the se logo screen as in step 2 above.
At this point, I'm lost. I've been reading so many threads I'm having trouble keeping track of what I read and where I read it. I'm going to start from square 1, and re-read what I've gone through so far on the chance that I might have missed something. But in the meantime, any help or suggestions would be greatly appreciated. My wife is enormously patient about this, but it's her phone, and she really liked the little x10. I'd love to get it running for her again, stock 2.1, 2.2, 2.3, CM7, whatever it takes.
Thanks for any help you might be able to provide.
Have you tried an older version of f lash tool. Like 6.8. People have trouble with newer version. Use old flashtool and flash 2.3.3 stock ftf file
From my XPERIA X10S v8.2 @ 1.19ghz. IF SOMEONE HELPS CLICK 'THANKS'
I have always use flashtool to root (no super one click and other things) and there was never any problems so use only flashtool!
When u have an instruction to do something why do not use it?
My ideas:
1. Can u go to xrec now? U could try to restore some backup then.
2. Try to flash 2.3 stock with flashtool or repair phone in official pc companion software
3. Try to flash 2.1 stock with flashtool
4. Try older Flashtool versions
I had a similar problem, I just flashed a stock 2.3.3 firmware via flashtool and booted up fine
Sent from my X10S using xda premium
An update: last night (or rather, early this morning) in desperation I flashed a generic 2.1 x10i rom I had inadvertently downloaded yesterday, using Flashtool. Lo and behold the little phone came to life. Wife can make and receive calls, and Contacts came back. I have no idea why it worked this time, but at least the phone is functional.
So now I'm back to square 1. That's progress I guess. She still wants 2.3, so tomorrow I'll be starting the process over. Think I'll take a different tack this time.
Thank you all for your suggestions. I hadn't considered using an earlier version of Flashtool, though that makes sense; I had to try 3 different versions of SuperOneClick before I got one that worked. I used S1C at first because it seemed so simple, but looking at Flashtool I suspect things might have gone easier if I had used it from the beginning.
A couple more questions:
1. Will having the x10i rom cause any problems? I'm thinking not, but I'm a little leery after yesterday's difficulty.
2. I've heard reports that stock 2.3.3 is kinda laggy. I take you all are pleased?
3. Where's a good place to find stock 2.3.3 ftf?
Thanks for all your advice.
Longstreet said:
An update: last night (or rather, early this morning) in desperation I flashed a generic 2.1 x10i rom I had inadvertently downloaded yesterday, using Flashtool. Lo and behold the little phone came to life. Wife can make and receive calls, and Contacts came back. I have no idea why it worked this time, but at least the phone is functional.
So now I'm back to square 1. That's progress I guess. She still wants 2.3, so tomorrow I'll be starting the process over. Think I'll take a different tack this time.
Thank you all for your suggestions. I hadn't considered using an earlier version of Flashtool, though that makes sense; I had to try 3 different versions of SuperOneClick before I got one that worked. I used S1C at first because it seemed so simple, but looking at Flashtool I suspect things might have gone easier if I had used it from the beginning.
A couple more questions:
1. Will having the x10i rom cause any problems? I'm thinking not, but I'm a little leery after yesterday's difficulty.
2. I've heard reports that stock 2.3.3 is kinda laggy. I take you all are pleased?
3. Where's a good place to find stock 2.3.3 ftf?
Thanks for all your advice.
Click to expand...
Click to collapse
I dont know were you can get a 2.3.3 ftf file i havent found a working one:/ if i were you i would the 2.3.3 and install ferlabs rom for LB its amazing simple fast and awesome. and yes stock 2.3.3 is somewhat laggy but not really just root and install a custom rom! hope this helps you i remebr in i think 7.1 flashtool there is a rebrand option in the pull down menu to rebrand your x10 so like the porivders firmware i think? so try that if you need to
If your ROM won't boot but you have access to recovery, step one is to wipe cache and Dalvik cache and reboot. If that doesn't do the trick, reflash, rinse, and repeat.
I went a little ROM crazy this past weekend. I landed on CM7 for now, but of all the ones I tried X10S was probably the best "stock-like" experience. It's a port of the Xperia S firmware for the X10, and I was really impressed with the speed and responsiveness.
This guy does a little video demo, and you'll find a link to a helpful install guide in the vid description:
Fair warning, I flashed this ROM twice over the weekend, and both times it took multiple boots, pulling the battery and sometimes doing cache/Dalvik wipes in recovery, before I got past the "xperia" boot screen. It's really pretty common after flashing a new ROM.
it take a while but all Stock Gingerbread tft files are still here
http://forum.xda-developers.com/showthread.php?t=936733
try SEUS(Sony Ericsson Update Service) to install fresh v2.3.3 GingerBread directly from sony site, download this SEUS file -> http://www-support-downloads.sonymobile.com/Software%20Downloads/Update_Service_Setup-2.11.12.5.exe
I bought my phone almost a week ago, but I only have a 7 day return policy so I need to figure this out quickly.
It's the C6802, bought in China (where I live), with HK firmware 1.4.1.B.0.475. Naturally, right when turning on the phone, it says to update to 532. The phone shop merchant did this for me when I bought it via PC (not sure what software he used), and afterwords the phone would suddenly just go dead and restart.
So I went back to stock 475, worked fine. Once home, I tried firmware 526, using flashtools, to see if it was stable, and same deal. The seller I bought it from says all the other firmwares are really buggy and I should just wait until there is a newer firmware to upgrade. But by that time, I won't be able to return the phone if indeed the problem IS the phone and not the firmware.
I was able to unlock the bootloader, root the phone, and install CWM, but every time I try to use CWM (whether backup, restore, or just navigating), after a couple seconds, the phone goes dead and restarts (same problem when using other firmware). I tried to install TWRP via goodplay, and that didn't work at all. I'm not sure how to flash it so I can use it during recovery because CWM doesn't work and I haven't seen an img of it for the z ultra (I'm still pretty noob at this as you can probably tell).
So does some firmware just bug out on some phones, like in my case, and will future firmwares fix this random death/restart? Do I just have extremely bad luck with CWM and firmware? Or is it a hardware problem and I should return the phone? Or is there a way to update to 532 and fix the crash problems? My first born for some expert advice.
The software you need to update on your PC is the Sony PC Companion suite. It should not prompted you to install it when you first plugged your phone in to your PC. Download that & see if you can update to 532 through there before you try anything else. To me it sounds like a bad flash & redoing it may resolve your issues. Hopefully...
Nuwidol said:
The software you need to update on your PC is the Sony PC Companion suite. It should not prompted you to install it when you first plugged your phone in to your PC. Download that & see if you can update to 532 through there before you try anything else. To me it sounds like a bad flash & redoing it may resolve your issues. Hopefully...
Click to expand...
Click to collapse
OK, I'll do that first thing tmrw morning, right now I'm making back-ups of everything using titanium and nandroid. But I can only use them when the phone is on, they don't work during recovery, nothing does. And using TWRP even with the phone on just causes it to die and reboot as soon as I click "OK" - is this something to be concerned about? It still rebooting even with CWM (in recovery) and TWRP (in normal bootup), even with stock 475 firmware, this certainly shouldn't be normal, right? I'll update how the PCC flash to 532 goes tomorrow...
I agree with Nuwidol, it does sound like a bad flash...
To put thing simple, forget CWM / TWRP for the moment, try 'CLEAN' install your phone with the latest firmware (532), then test using it for a day or two and see if it works properly. Yes, all firmwares released by Song so far for this phone are kind of buggy but nothing serious - just minor issues I would say, and definitely not random death or restart like you said.
To clean install, I like using SUS (Sony Update Service) because, unlike PC Companion which packs with a whole bunch of functions, SUS only deals with one thing, to reinstall or update firmware for your phone, and it works well.
First, backup whatever you find important, then relock you bootloader (restore from your TA partition backup, and flash back any stock FTF... stuff like that...).
Hook up your phone with SUS by following its instruction. Choose 'erase / format everything (...or something like that)' when it provides you with update options. Sit and wait until it finishes.
Turn on your phone, skip WiFi setting as well as the Google account, go straight to Home. Then:
'Settings' --> 'Backup & reset' --> 'Factory data reset'
Choose 'erase / format everything' (or something like that) again.
After reboot, you should have a very clean system by now. Use it as is for a few hours / days and see if anything strange comes up. If nothing strange comes up, then your phone is fine; if not, go return it or ask for exchange.
One minor note, rooting the phone is ok, pretty straightforward and safe to do I would say. But unlocking the bootloader? Well... it is ok too, unless you know what you're doing.
Hope this help.
so far so good
littopillo said:
I agree with Nuwidol, it does sound like a bad flash...
To put thing simple, forget CWM / TWRP for the moment, try 'CLEAN' install your phone with the latest firmware (532), then test using it for a day or two and see if it works properly. Yes, all firmwares released by Song so far for this phone are kind of buggy but nothing serious - just minor issues I would say, and definitely not random death or restart like you said.
To clean install, I like using SUS (Sony Update Service) because, unlike PC Companion which packs with a whole bunch of functions, SUS only deals with one thing, to reinstall or update firmware for your phone, and it works well.
First, backup whatever you find important, then relock you bootloader (restore from your TA partition backup, and flash back any stock FTF... stuff like that...).
Hook up your phone with SUS by following its instruction. Choose 'erase / format everything (...or something like that)' when it provides you with update options. Sit and wait until it finishes.
Turn on your phone, skip WiFi setting as well as the Google account, go straight to Home. Then:
'Settings' --> 'Backup & reset' --> 'Factory data reset'
Choose 'erase / format everything' (or something like that) again.
After reboot, you should have a very clean system by now. Use it as is for a few hours / days and see if anything strange comes up. If nothing strange comes up, then your phone is fine; if not, go return it or ask for exchange.
One minor note, rooting the phone is ok, pretty straightforward and safe to do I would say. But unlocking the bootloader? Well... it is ok too, unless you know what you're doing.
Hope this help.
Click to expand...
Click to collapse
Litto... your awesome. This has probably been one of the single most helpful replies in my history on xda. I did everything you said, step by step, and I was able to flash 532 without any problems, and so far, after using it for half a day, it's been completely stable. Granted, I haven't installed a single app on it yet or synced anything, I'm hesitant, ha. But I'll do that tonight, and Lord willing, nothing will happen. But so far so good. You really helped me a ton, thanks so much. :victory:
As for the issue about unlocking the bootloader, well, I did it because I was told that is the only way you can install custom ROMs and CWM? So for flashing anything besides stock, I would think it's pretty much mandatory, am I wrong? I hope to install radioactive or paranoid android eventually, but of course with it crashing during CWM and any firmware upgrade, that wasn't an option before. I'll use it for awhile longer with the stock (but rooted) 532 and if no problems occur, I'll move onto flashing the CWM/TWRP img by krabappel, which means then I can finally flash a custom ROM. Here's hoping...