Hi Guys,
I have a SE X10i (Orange UK) running stock 2.1 (Rooted) with dual touch mod. I really wanted to give the FROYO roms a go but found that my baseband was still 046. I downloaded 54 and flashed but was not getting any service fron orange (despite numberous reboots). I found the 046 baseband on the dev thread, compiled it (as was unable to use the batch cmd) and flashed to my phone.
I rebooted and service from Orange returned fine. I thought all was ok until I turned on the wireless and then phone crashed with a white LED; it powered back up fine but then crashed again when I tried to enable wireless.
The question I have is; if I conduct a repair via PC Companion, etc will this fix my wireless problem or is there another way I can fix the wireless?
I have searched on the forums but as of yet not found a solution; so apologies if I have not seen one already posted.
I hope someone can help and point me in the right direction.
Thanks.
Related
Hello all,
To keep it concise:
Received my SII from Vodafone yestersday - all is well.
Proceeded to flash the phone with XWK37 firmware and rooted the phone by flashing chainfire's insecure kernel, applying root and then flashing the stock XWK37 kernel - have used Odin before and all is well.
By the time I finish playing with the phone it's 3.00am so I put the SII on charge (battery at around 30%) - all is still suspiciously well.
Get up at 7am to take my kid to school and when I get back I discover that the menu key no longer does anything when pressed (home key and return key still work fine) - it doesn't light up nor does it bring up a menu - all is not well.
So far I've tried:
Reflashing both the firmware and kernal - no effect.
Removing sim card, sd card and battery - no effect.
Hard resetting (both via button method and android privacy menu) / formatting sd card - no effect.
Dialling *#*#2663#*#* and updating the touch firmware - no effect.
Accused my wife of breaking my phone before she went to work - no effect.
Now If it's a hardware problem (which would be disappointing since I've only had the phone for 1 day) then I'm stuck since there is no stock UK Vodafone firmware available yet to flash back to before handing in for repair - plus I don't want to go back to using my N97 in the meantime.
Yes I preordered the N97 before it was released and got myself stuck in an 18 year contract - words can't describe how much I hate that worthless piece of Nokia - I kept it to teach myself a lesson, early adoptions don't pay off.
The only other relevant thing I can think of is that I was trying to install ADW launcher (previously used it a lot) before I went to sleep last night however although the phone claimed that it downloaded and installed - no icon appeared and I was unable to launch it although it's wallpapers showed up when I was switching my live wallpaper.
Can anyone help with any idea's of what it might be aside from a hardware issue?
If it is a hardware issue, anyone know when the Vodafone UK firmware might shown up?
Tell you what, I'll throw in a free N97 for anyone who solves the problem
Thanks guys.
K37 firmware ????
I would flash old firmware like WKDD .
Possible with pit and repartition checked if that failed . Not used either yet on SGS2 but always cleared SGS1 by that method .
jje
Thanks for the reply jje,
The XWKE7 is the latest generic XEU firmware available from this guide:
http://forum.xda-developers.com/showthread.php?t=1075278
I flashed it exactly as the guide stipulated.
However I didn't even think to try flashing it to a earlier version to see if the problem might be with the actual firmware.
Should be finishing work in a couple of hours so will try flashing the older XWKDD
firmware and see if that relocates the menu key.
Will update as soon as I know.
Damn.
No luck - tried flashing KDD (and also KE1/KE2 for good measure) accompanied by full memory wipes - still no luck. All these firmware files come in one .tar package which i place into the PDA section of Odin.
Even tried one where the pda, modem and csc were split into seperate files from:
http://forum.xda-developers.com/showthread.php?t=1075278&page=11
Still no return of the menu key.
When I am flashing - I leave the pit section of Odin completely alone and leave re-partition unticked - I take it this is correct?
It's strange because apart from the menu key - the S2 is working perfectly.
The only other thing I can think of is that the Vodafone branded version of the S2 in won't work with any other generic firmware which is pretty unlikely methinks.
jje - "...possible with pit and repartition checked if that failed.." - I didn't quite understand what you were recommending there mate - should I be using a pit file and checking repartition?
Any other ideas guys?
Off to go glare at my wife's dumbed down yet fully working iphone - it's laughing at me...
I've got the same problem. The menu button works just when it wants. Sometimes it doesn't react at all, sometimes it works perfectly.
I have KE1 firmware, I have rooted it and unrooted (for sim unlocking), then installed original kernel via Odin. Everything was wonderful and I was the happiest guy in the world! One day later the button began behaving like a goast! as chronicpoetic mentioned.
I would like to try installing the new firmware via Odin, but I am afraid that if it's hardware problem, then it won't be taken by service.
Any suggestions?
sounds like hardware faults guys :/
Thank you for reply! I thougt it was too, but... read below
I found out something else.
The menu button works, but with an extreme long delay - 15-30 seconds! More often just right after screen unlock. It just appears and disappers 30 times if I pushed it 30 times before.
And still it can work just perfectly. Sometimes after connecting it to PC or charging it. That dosn't work like a rule.
I am trying to find the reason of such unusual behaviour, but I am lack of expirience.
Any help?
Hello man
I hope that my info will help you
I was in samfirmware.com site and i remembered your problem and i recall that you say Vodafone
so i saw "Provider Samsung I9100 Firmwares" and one of them looks like Vodafone firmware...... please see this site hope to helps you:
http://www.samfirmware.com/WEBPROTECT-i9100.htm
sorry for my bad english
Yeapp, I visited the partner of samsung service center, they said it was a hardware.
Same thing here, any progres?
Just revisited this post - I managed to get a hold of the original Vodafone Firmware from Intratech's thread, flashed it and returned the phone - turns out it was a hardware fault.
Vodafone promptly replaced mine folks.
Sent from my GT-I9100 using xda premium
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.
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
Hey all!
First of all, I started a new thread because there are so many replies in Mini CM7 ROM thread and to me it looks (sort of) like a salad. Sorry if I did wrong.
Now, the problem.
A few days ago I managed (I would add that this was not too hard...) to brick my x10 mini. What I did was to relock boot-loader without flashing stock kernel back. After disconnecting and reconnecting the battery wires, I was able to flash an original rom (sadly, SEUS didn't help, it only said that I had the last software installed and the only option showed was exit. So I did another stupid thing, I unistalled SEUS, so bye-bye blob_fs files...), which I downloaded from here. So my phone was back to life and usable. I unlocked the bootloader again and now I can flash any kernel I want. There's only one little problem: no matter what kernel I flash and no matter what rom I install, my phone goes in a boot-loop. The only rom that works is the Orange branded one I used to unbrick my phone. I followed step by step (at least now) all the instructions to install Mini CM7-2.1.1 and Mini CM7-2.13, but no chance, my phone keeps restarting. I even tried to install other custom roms, which are requiring kernel 2.1, with no result. The only one who works is the Orange one.
Now, if anybody could upload the 2.1.1.a.0.6 SE firmware (stock ROM+kernel), I think I might get a chance to solve this (I could only find 2.1.1.c.0.0 and looks like SEUS - at least in my case - doesn't like it). Or if anyone else here knows other ways or have other ideas of how to solve this problem, I'd be very grateful.
Thank you for reading my "book", any help would be much appreciated.
Now before anyone responds by telling me to search the forums I have spent HOURS on XDA going through innumerable forums clicking on dead or misleading links and have not found anything that will help.
My old x10 crapped out on me and I need to reflash it so that SEUS will recognize it. I know what I am doing and have done this before. I have the latest (and multiple copies of older) version of flashtool. This all started with 2.1 randomly shutting down irrespective of what the battery level is. I have had this happen in the past and EVERY time a reflash resolved it.
ALL I need is either the official Rogers 1.6 or 2.1 stock rom. There seem to be HUNDREDS of dead links here and this has become a uber frustrating situation. I have flashed X10a_3.0.1.G.0.75_AMERICA-US GENERIC 1233-8200 which 100% solved the reboot issue but now my sd card is no longer recognized. And please don't tell me to try other cards as I have used 6 different capacity and speed cards and none are seen in the phone but ALL work on my pc and on my xperia T. I am using the original 16GB card that the phone came with.
For some reason I can get roms for every other carrier except Rogers so I am suspecting Rogers had them pulled, but SURELY someone here has what I need and can help.
Once I can get it back to stock I can use SEUS or PC companion to update and I will take care of the rooting later, if at all.
So here it is, I am asking VERY nicely...BEGGING in fact...can ANYONE help me get a stock ROGERS rom for my x10?
Following http://www.youtube.com/watch?v=HmX-IYNYqL8&hd=1 was of zero help as the page shown in the vid has been edited and now does not have any of the links for the firmwares, only the flashtool.
I honestly thank you for any help you can offer here. My kids want\need their phone back and there is no way I can afford to replace it right now...and frankly I shouldn't have to replace it if all I need is the rom. I do apologize if I am coming off like a jerk. That is not my intent. I am just SUPER frustrated and running out of time and searches on XDA have become less than friendly over the past few years...too much content to dig through and too many old/dead links.