Related
Soooooooo I caved hearing that 2.2 would be out for the Streak and went and picked one up on AT&T. Thinking hacking it and putting a 2.2 ROM on there would be cake....after all I'm in IT. LOL yeah right. Anywho got no where with trying to get to 2.1 yet alone get to 2.2. So thought someone had to have a way to get ahold of an official Froyo for the Streak. So by using someone else's baseband version I was able to Dl the .pkg from Dell here: httpCOLON//mobileupdate.dell.com/?version=GAUSB1A111100[/url]
Sooooooo wondering would it work if I DLed that then put it in the root of the SD card and renamed it to Update.pkg, booted the phone in fastboot mode then updated it via the Update.pkg? That can't work, right? That just seems to easy. Dieing over here to get ahold of an official 2.2 build so I can get my exchange to work natively for work. AT&T has now blocked my iPhone from getting on the network so I can't revert waiting for the formal OTA to come out.
I'm a newb when it comes to android (just got my streak 3 hours ago) and I tried what you have stated and was greeted to "FOTA Version Mismatch... Shutting down device in 30 seconds"
Did you flash the clockwork recovery ?
Search for a link to the QDL repair tool, once you get the driver loaded, it's a simple one click solution to getting 2.2
After that, just use any of the links here to download the 318 version, and then you'll have the updated 2.2, or after getting the base 2.2 (308?), just download DJ Steve's updated version.
rahulkadukar said:
Did you flash the clockwork recovery ?
Click to expand...
Click to collapse
Yeah ive flashed clockwork recovery and that is successful. Once I go into fastboot mode and do the update.pkg part it errors on the install.
just follow the steps in the thread "updating and downgrading your streak" i followed the steps to get the UK stock 2.1 rom.. then i daringly tried the OTA update and it worked like a charm. im now running the UK stock 2.2 rom thats rooted.
As I've said before:
I had this problem also....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 on an unlocked 00 baseband. From there, it was an incredibly simple flash to DJ Steve's 1.5.1 using fastboot. Then I was done. No clockwork, no recovery, no nandroid, no nothing. Just follow the instructions for QDL Tool. I'm serious.
Doctor_Watson said:
As I've said before:
I had this problem also....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 on an unlocked 00 baseband. From there, it was an incredibly simple flash to DJ Steve's 1.5.1 using fastboot. Then I was done. No clockwork, no recovery, no nandroid, no nothing. Just follow the instructions for QDL Tool. I'm serious.
Click to expand...
Click to collapse
are you also saying that it unlocked your phone? oO?
It flashes a pre-release of v2.2 with a generic baseband, not locked to a particular carrier. The Sim Lock is still in place, however, so the phone itself will still require an unlock code if it did before.
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
[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
Hello guys, you'll have to excuse me for the wall of text, but it is necessary to fully describe my ordeal.
I bought an used atrix about 4 months ago from ebay (and i'm now deeply regretting it, too many issues). When I first received the phone I was unable to hear callers, even though they could hear me (badly, but could). I resolved that the easiest way possible: I bought a headset. Even with that issue and since it was impractical for me to return the phone because I'm in a different country (customs alone were over $100) I continued to use it. I flashed CM7 and ATT N_.37, flashed TWRP 2.1 and I enjoyed my phone for a couple months (even with the audio issue). Then one day, I went to bed with my phone on a full charge and in the morning I found it turned off. I tried to turn it back on and nothing happened. I thought maybe the battery had been drained by something, because I had left 3G data enabled. I tried to charge it and nothing happened, except the phone started to get really really hot in the lower part so I decided to disconnect it. I tried again a couple hours later and same thing happened. Next day I hit the power button and was able to enter android recovery. I wiped and factory reset, reinstalled cm7, gapps and radio and phone turned on and showed around 60% charge and it seemed fine and then all of a sudden the led started glowing light blue. Then the phone shut down and started to boot loop. I took off the battery, let it rest a while and then when I turned it back on everything worked fine (still, minus audio). That was two weeks ago. Today, it started to do the something similar but worse. Blue led flashing and boot loop are there but if I enter recovery I can't find anything in the sdcard, and if I place a microsd in the slot it isnt recognized. Also, led is flashing blue even while in recovery so I doubt it is a CM7 issue.
tl;dr My phone is dead. Can it be fixed or do I now own a $250 paperweight?
Try to flash your phone with your stock firmware using rsd lite
here a list of firmwares ... http://forum.xda-developers.com/showthread.php?t=1125944
WARNING! : flash it with YOUR stock sbf !!!
isn't that dangerous? from what i understand with this post it seems as if it isn't advisable to use an sbf on an unlocked bootloader.
not.a.troll said:
isn't that dangerous? from what i understand with this post it seems as if it isn't advisable to use an sbf on an unlocked bootloader.
Click to expand...
Click to collapse
Only if you're downgrading. It can work if you do it properly, but it's not recommended. Fruitcakes are the more foolproof way to go.
well i chickened out of the .sbf flash and just tried the moto-fastboot stock restore available elsewhere. while everything seemed to flash correctly i am still bootlooping/shut down. also, light blue led still there and sometimes i get stuck on bootscreen and can't even enter recovery. guess ill have to take it to a shop and see if something can be done. else S>atrix 4g for parts.
D:
hello to all
my atrix 4g originally was in firmware 4.5.141.MB860 ATT, i unlocked the bootloader succesfully and flash CM7... but for reasons of life (silly excuse jejeje) i want to take it back to the original fw... with this files: Blur_Version.4.5.141.MB860.ATT.en.US and 1FF-olympus-user-2.3.6-4.5.141-111212-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P012.sbf.gz can i go back to stock fw? with this stock files i lose the boot unlock? is this a safe method? and what is the safest?
thanks for your help and greetings from Colombia (and sorry for my bad english)
Flash the latest sbf for your phone. I've done several with no problems. Yes, you do lose the unlocked bootloader though.
This will return you to stock. I used the same files.
not.a.troll said:
well i chickened out of the .sbf flash and just tried the moto-fastboot stock restore available elsewhere. while everything seemed to flash correctly i am still bootlooping/shut down. also, light blue led still there and sometimes i get stuck on bootscreen and can't even enter recovery. guess ill have to take it to a shop and see if something can be done. else S>atrix 4g for parts.
D:
Click to expand...
Click to collapse
I also have been through several phones with this issue. Although you can flash the sbf with no troubles, that is really only good for sending it into warranty. From my experience, this is a hardware issue, and flashing the stock sbf doesn't solve the problem. If you do not have warranty, a repair shop is your best bet.
Good luck.
Repy
x-geo said:
hello to all
my atrix 4g originally was in firmware 4.5.141.MB860 ATT, i unlocked the bootloader succesfully and flash CM7... but for reasons of life (silly excuse jejeje) i want to take it back to the original fw... with this files: Blur_Version.4.5.141.MB860.ATT.en.US and 1FF-olympus-user-2.3.6-4.5.141-111212-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P012.sbf.gz can i go back to stock fw? with this stock files i lose the boot unlock? is this a safe method? and what is the safest?
thanks for your help and greetings from Colombia (and sorry for my bad english)
Click to expand...
Click to collapse
Hi,
Yes you can go back to your stock rom. Another yes, you will lose all your files and your bl unlock too. You have to start everithing from the begining. this is a safe method if you flash your own rom.
hi guys,
got a u20i here, which the previous owner installed 2.3.7 cm7 onto.
im trying to get it back to stock (official sony firmware, stock/rooted doesnt matter but 2.1)
im having a bit of trouble though.
ive tried using flashtool with a stock ftf, ive tried with an update.zip and flashing through CWM but all to no avail.
im seriously at my wits end here.
ive never used SE droid phones before, so this is a bit overwhelming.
can anyone give me any pointers, or some sort of idea of where to go from here?
thanks
edit- just using pc companion to 'update' the phone right now. hopefully it doesnt brick it
edit2- well that worked just fine. never thought thatd work.