Hi!
I hope someone here can tell me if i can still fix my fried's X10 (so 1b) or it will need a trip to the repair centers...
First up, my friend said he bricked the phone by upgrading to 2.3 using Flashtool.
as I can see, the phone wont boot up anymore. it will just vibrate, flash green led once, but the screen wont even show the white SE logo, just black. phone wont even charge offline. but the good thing is, it can still go on flashmode.
I tried flashing using flashtool, but most of the time, i get the error "flashing aborted" after the system.sin is flashed (before userdata.sin is flashed), then it ask me to unplug, and reboot.
I tried SEUS, but it says that there is no update available for the phone (no option to install update, just the exit button).
Pc Companion on the other hand, says "No available download yet, please try again later".
after more than 5 hours of reading and re-flashing, i came to an article that says x10s that are having the same symptoms as mine (flashing aborted with flashtool, SEUS wont install update, PC companion saying no software available), are caused by NAND memory failure.
in which case, i am not entirely sure if it can still be repaired, or we have a very expensive paperweight
http://forum.xda-developers.com/show...1#post18850231
does this needs to have the memory replaced? or is it like what others have reported, just a case of loose soldering on the memory chips?
i reckon the memory is not that totally fried, since its not until the later part of flashing that i'm getting the error.
hope someone can help
Motherboard problem/ NAND
do you guys know if this can still be fixed without the need to replace the motherboard?
i did a lot of research, and the symptoms that most people on various threads indicates a corrupted NAND memory.
so far, the only instance of this condition being repaired did mentioned about his motherboard getting replaced.
is it really necessary to have the whole motherboard replaced, or it is just a matter of a few parts that needs to be re-soldered or replaced (flash chip, power IC)?
at least one on these threads have the same exact condition that points to a damaged motherboard, and unfortunately, in my country (Philippines), SE service center would not want to replace the motherboard of out-of-warranty-phones.
http://forum.xda-developers.com/showpost.php?p=18436249&postcount=57
http://forum.xda-developers.com/showthread.php?t=1165061
http://forum.xda-developers.com/showpost.php?p=17539374&postcount=18
http://forum.xda-developers.com/showthread.php?p=17113461#post17113461
Related
Hey there =)
Yesterday I tried to update my X10 with SEUS. I followed the instructions carefully but at the end of the update (90 % ) the processing bar of the programm get stuck and the "Update Failed" window appeared
I turned on the phone but after the "Sony Ericsson" Logo the yellow exclamation mark appeared, and it didn't start the OS.
So i tried about 20 times to update it with SEUS again and after that i tried the restore function of PC Companion but it also diddnt work....the processing bar gets stuck at about 90 % or 95 percent and the the update failed again....
I tried the rooting thread for newbies to get the firware back on the phone but it didn't work because the phone doesn't start, so i couldn't activate USB Debugging....
WHAT CAN I DO??
please help me!
Unfortunately there is nothig you can do besides sending the Phone to SE for replacement.
The problem that you have encountered is a hardware fault.
It happened to me once while I tried to root my phone. At some point the flashtool returned with an error and the last lines said something about a write error and a major error servity.
What's the problem exactly?
Some parts of the memory are faulty and can't be written to. Therefore the flash tool or SEUS can't complete their task and return with an error.
How to solve?
The only ay to resolve this problem is to get a replacement.
If you have tried to flash it with some older firmware flash it again with SEUS (just for warranty reasons) and it to SE or visit a shop of your carrier and have them return it to SE. Just tell them you tried to update with SEUS and it broke your handset.
I had a short chat with SE support and told them my problem, only advice was: return the phone to SE, nothing else can be done.
To me it seems like they had that problem a few times already.
StopControl said:
I tried the rooting thread for newbies to get the firware back on the phone but it didn't work because the phone doesn't start
Click to expand...
Click to collapse
So did you actually try it, because you don't need the phone in debugging mode to get into flash mode. Run Step 1, and if it completes your phone should be ok, then try seus again.
What if the memory fault hypothesis is true? Then running Step 1 will probably also stall as it does with SEUS, because of write-to-memory problems?
maistora said:
What if the memory fault hypothesis is true? Then running Step 1 will probably also stall as it does with SEUS, because of write-to-memory problems?
Click to expand...
Click to collapse
Possibly, but won't know unless you actually try.
Worry not, you're not the only one with the issue. A couple of people on the SE forums as well as myself have experienced this phenomenon.
(See here: talk.sonyericsson.com/message/27709#27709 ) - add the HTTP yourself, because I have less than 10 posts.
Only yesterday, I handed my X10 into the T-Mobile store for a free "repair". No telling whether they'll attempt to "repair" the phone, or if they'll swap the phone entirely, though; only two weeks of waiting will tell.
I've had software-related problems before with Sony Ericsson phones - namely the K850i and the C902. I've had to send those models off for repair several times, to eventually agree to have the K850i replaced for free after the third repair. The only thing the T-Mobile repair guys can do is attempt to reinstall the software and perform some test phone calls to ensure the device works - if I can't flash the X10 to repair it, then I have serious doubts that the phone techs can flash it.
While brining this up, the T-Mobile representative also said that the C905 "was even worse than the C902." The X10 is just another addition to the history of Sony software failures. In this case, it's probably a hardware flaw with the X10 that causes the problem, but the problem experienced is still software-related. What happened to their long line of stable phones, like the W810i? That phone really was a jewel for its time.
Please help me, I played around with BBs yesterday and lost radio, so installed a stock FW with FlashTool, and got radio back again, but on some 4x BB.. Wanted the new 58 BB, and found out that a .. ..0.16 FW would give me that, so installed the polish one (found no other), and after that no response when touching the screen!
xRecovery is of course gone after "stocking" (also rooting?), but I have tried a number of FWs for FlashTool, and even FW directly from S-E using Update Service, but still my phone is next to bricked.. I am n00b and could very well have done something wrong unknowingly, and/or overlooked something, but what might that be, and what are my options?
Sounds like corrupted FW. Not a big deal cause without a cracked Bootloader, you realy can't screw the phone up.
Turn phone completely off.
Pop Battery - SIM card - Micro-SD card out.
Let it sit for a few minutes.
While your letting it sit, take your Micro SD card and Format it using your PC.
"not saying this is your issue but I have had the phone lock up and appear to be unresponsive due to a corrupt file on the SD Card and it fails to mount and gets stuck." If you have any files you want to save, copy them to your PC Hard Drive.
Reinsert your SD Card - Sim Card.
Plug your USB cord into your phone " LEAVE THE BATTERY OUT "
Start up SEUS " Sony Erricson Update Service ".
While holding the back button, reinsert the battery.
Follow the instructions and restore the phone to factory settings.
I hope this works for you as this should elliminate any problems that could have or would be occuring prior. If it doesn't, shoot me a mail and I will get with you on messenger for trouble shooting.
_-_- Press Thanks if its useful-_-_
Nope, didn't do it, touched the thanks-bottom anyway, because on my PC I can...
PM'ed xKrisx, but everybody are welcome with suggestions as I'm completely lost without my phone!
Edit while waiting, hoping:
Followed instructions above several times now, except
xKrisx said:
.. .. .. and restore the phone to factory settings.
Click to expand...
Click to collapse
no such option, wouldn't that be S-E-Android 1.6 ? In fact I see no other options in SEUS than accepting (or not) uneditable choices towards an update -and done-, so I suppose that's what was meant(?)!
Have tried a number of slight variations including SEUS update without sim and SD at all (was actually allowed that), but most noticeable difference was that first boot pre-choose English instead of Danish (my language), and still no response from touch screen, so can't select anything at all!
My phone shows evidence of "moderate physical pressure" (bought second hand with one corner missing), so I can't totally reject the possibility of a sudden HW digitizer breakdown though I think that would more likely have occurred while phone in use than while sitting on my mouse-pad.. No matter what, I would really like to exclude any SW related errors before moving to torx-driver surgery! Plz help guys!
Hi seek4
Did you ever find a solution for your touchscreen?
Hello,
I have a Samsung Galaxy S2.
After reading this post http://forum.xda-developers.com/showthread.php?t=2382579 I decided to root my phone.
So I went ahead and started with this step http://forum.xda-developers.com/showthread.php?t=1118693 because I was unsure if I had a kernel with the MMC-SUPERBRICK-BUG.
After I flashed CWM-SuperSU-v0.97.zip using Odin version 1.85 and after the phone rebooted it was stuck at the "triangle screen" for a few seconds then the display went black and I couldn't do anything further.
Up to this point the phone was still accessible in download mode (volume up, power and center button). I believe this is called "download mode". Sorry but I am a complete noob with rooting phones, etc...
So I panicked and took the phone to a repair shop (big mistake). The guy ran it in download mode then tried to flash something onto the phone (I think he used all 4 fields: Bootloader, PDA, Phone and CSC.
Then, in the middle of the operation, Odin froze when writing "setting up connection". Then the phone died ! pressing the 3 famous buttons does nothing and the phone just stays dead.
I had to leave the phone there as the guy said they will try to bypass stuff and try to connect to the CPU directly (sorry again if this sounds noobish). I did update my modem firmware and my computer BIOS in the past... but I guess this one was more complicated.
At the shop, they asked me to check again in 3 days. I am lost here. I don't know what to do anymore.
Is the phone hard bricked ? Should they bear all expenses for what they did ? I would bring back my phone and try something like this http://forum.xda-developers.com/showthread.php?t=1878255 or even a stock flash but I am afraid I cannot do that as the phone isn't even powering up anymore after they tried to repair it at the shop.
Any advice is appreciated.
Nope. You borked it. You tried to flash custom firmware to the phone & obviously failed spectacularly at it. Instead of trying to flash it yourself via download mode (which you could easily have done unless the NAND was borked), you paid them to do it. Sometimes flashes go bad. Sounds like that's what happened in this case.
Reading between the lines they sound like they're going to try & JTAG it (or have someone else do it). And if that fails I presume they'll change motherboards. You could always get the phone back & take it to someone who does JTAGs if that shop doesn't themselves.
MistahBungle said:
Nope. You borked it. You tried to flash custom firmware to the phone & obviously failed spectacularly at it. Instead of trying to flash it yourself via download mode (which you could easily have done unless the NAND was borked), you paid them to do it. Sometimes flashes go bad. Sounds like that's what happened in this case.
Reading between the lines they sound like they're going to try & JTAG it (or have someone else do it). And if that fails I presume they'll change motherboards. You could always get the phone back & take it to someone who does JTAGs if that shop doesn't themselves.
Click to expand...
Click to collapse
Yes I know I failed at it
Or maybe the shop technician is the one who broke it. At least when I had the phone with me I was still able to boot in Odin mode.
Do you think I could have recovered my phone if I had kept it with me and it was booting in download mode ?
I feel so pissed that I took it to that shop. I just wish I hadn't panicked and I had tried, instead, to fix it at home by asking for more help.
Anyway I still haven't paid them anything so far.
We agreed that they will pay for the motherboard because I brought in a working phone (that would power up at least). The owner of the shop was nice enough to agree that he would only charge me fees for installing new software on the phone (even if they have to change the motherboard) because he knows the phone was booting in Odin mode when I came in to the shop and his technician flashed the wrong firmware.
I also wrote down the board serial number so I can be sure they changed it (if they say they did that). So you are telling me the phone can still be fixed ? What does JTAG mean ?
Even if it is fixed I think I will be too scared to try and root it again. Unless I can understand in advance, step by step, what I need to do and what file version(s) I need to use.
Ok, I got my phone today in good working condition.
According to the shop, they had to replace an IC (I don't know what damaged the IC, I am assuming this happened when they tried to electrically jolt the phone) then JTAG it to get it to work again. They charged me a small fee (and they did end up bearing more than 50% of the expenses) because I brought in a phone that was booting in download mode and they take responsibility for what happened after that (flashing wrong files which caused the phone to completely stop booting).
Anyway, long story short, this was my first attempt to root a mobile phone and I learned my lesson.
I am running the following:
Model Number: GT-I9100
Android Version: 4.0.3 (which I will need to upgrade to 4.1.2 of course)
Baseband Version: I9100XXLPW
I know you will say read the sticky posts or the guides but the truth is, that's exactly what I did (you can see the links to the guide I tried to follow in my original post) and I still ended up failing at rooting/installing cyanogen on my phone right after installing Clockwork Mod.
The truth is I am scared to try again and mess up the phone. So this time I would rather be safe than sorry.
What can I do, this time, to safely root it and install a mod like Cyanogen.
Detailed steps are appreciated:
- Do I need to upgrade to 4.1.2 before rooting as 4.0.3 might have the superbrick bug ?
- How to backup the phone.
- Odin version to use, ClockWork Mod version to use, Cyanogen version to use
- How to connect the phone, how to reboot in download mode and all the necessary actions to avoid bricking my phone.
No spoon feeding aloud on XDA.better to read and learn how to do this and that but before you flash anything after learning how to do that learn how to fix it if it doesn't work. :thumbup:
andrewwright said:
No spoon feeding aloud on XDA.better to read and learn how to do this and that but before you flash anything after learning how to do that learn how to fix it if it doesn't work. :thumbup:
Click to expand...
Click to collapse
Fair enough, I figured I'd get that reply from someone and it's normal to be honest.
I decided not to try anything on my phone before I re-read the guides and be sure I know what I am doing.
I will also keep the phone running on stock firmware (after upgrading to JB 4.1.2) to check the battery consumption behavior which, I hope, will be fine since someone tampered with my phone's electronic components at the shop.
I got a new xperia active st17i yesterday, it was on gingerbread fw.
I used flashtool to unlock the bootloader. I reset the phone but it hung on the sony logo, which was odd. (I have unlocked and flashed around a dozen xperias and this has never happened). I pulled the battery and turned it back on and it boot looped on the sony logo. (left it for several minutes to be sure). Every time it was switched on after that the screen powered on but remained blank.
I flashed the Rage kernel for GB. Turned the phone on and the sony logo came up, went bright, and I got into CWM recovery ;0) all good I thought. I rebooted the phone. It started up, the sony logo came up, went bright, the animation started but then crashed/hung. I left if for a few minutes and nothing, so I pulled the battery. After this, no screen function at all, no back light, completely dead. ;0( When I power on the phone it vibrates and after a few seconds the front led flashes blue and goes out.
Fast boot works, Flash mode works, Flash tool lets me lock and unlock the phone, flash kernels (rage/X-kernel and Lupus) and ftf firmwares ... S1 tool sees my phone, pc companion updates the phone perfectly, but still no screen.
I read the other ST17i bricked threads here and looked at trying the Wotan server method but the phones date code is not covered, its newer than the ones Wotan cover (maybe an issue?).
I have not idea right now, apart from I have hard bricked it somehow. (searching for 'st17i dead screen' gives a few results from Sony's service forum with similar sounding phone activity, with no resolutions). Searching for bricked st17i all relate to soft bricked devices.
As the phone is brand new, I am not sure about the bootloader issue, is it still covered by warranty? The phones current state is locked and fully updated via pc companion, as it was out of the box.
Any advice and help will be greatly appreciated!
Fixed!!! ... (see edit)
I started from 100% scratch. I use an old laptop with winxp to do all my phone work. I did a factory reset on it (begrudgingly) and reinstalled everything*. ADB, flashtool, drivers/kernels etc. (Its now working a lot better I have noticed).
Bear in mind my phones state was factory stock ics 4.1.B.0.587 and locked.
I unlocked the phones bootloader in flastool, it turned on?! Resurrected.
I flashed the ics rage kernel and installed a custom rom, backed up x2 ;0) I AM HAPPY :0D
I honestly tried everything methodically beforehand, hence my post!
*Is it possible to install a corrupt zip? I noticed when downloading files that some were showing as downloaded but were not the correct file size. I only noticed this when grabbing a kernel file, its size was around 6.7mb but the file I had on my desktop was 633kb, it unpacked and came up with the correct size of 6.7mb? (downloaded on my main work laptop with windows 8.1). I had so many bits and pieces on my xp laptop, swapping files from usb pens etc I will assume this could have been my issue!
lol... I must have spent near to 6+ hours reading about tespoint method flashing, TA restoring/backup up, and a whole range of other bricked device issues... I am educated a little bit more now, in more ways heheh...
Update....
The phone worked for about 30 minutes and then a blank screen again. No CWM, because of blank screen. Had fastboot and flashmode still.
So from scratch again, I relocked and flashed with original ftf CE (I have two CE ftf's of different sizes (will need to do homework on these)). The phone was still dead? When plugged into my pc (tried all three USB ports), sometimes when in fastboot/flashmode the device keeps connecting/disconnecting randomly, which is definitely wrong. Possibly my problem is a bad port or maybe the micro usb cable, or loose connection somewhere? Irdk? So now I tried a brand new sony, original, cable and all seems fine again. So, used flashtool to unlock, flash kernel, get to CWM, use my backup and the phone is working again.... but for how long? There's definitely an issue with the ftf files (mabye something to do with my corrupt file size problem? Will go to another place to grab these from and if the phone goes off again will try). odd.
**last edit**
The phone is now running okay. I had a dud battery, which I was using/swapping between several phones that I was returning to stock. It was showing 100% charged but upon disconnecting USB the phone died. Took me the best part of two days to figure that one out... I know! (I'm very busy). So it was possibly the bad battery all along!
So my s3 has been having problems for months, kept shutting off randomly, then just over a week ago it got stuck on the bootup logo and wouldn't work at all. I plugged it into Kies and tried to restore it although it somehow failed and told me to try an emergency restore, although never told me any code and the device doesn't show up on the list of devices to emergency restore.... wtf.... So now it boots to an error saying "Firmware upgrade encountered an issue"
I think it still had a warrenty from the shop I bought it, but not from samsung (I got it from a used phone dealer with 1 year warrenty) but they are not in my city, so I'd need to have it shipped to them, wait weeks, and as it now has the appearance that I am the one who bricked it doing firmware upgrades (even though I used samsungs Kies software) I have a feeling they might just tell me to bugger off, after waiting weeks without my phone....
So I tried to flash it with odin using stock firmware but when I tried this I get the error "There is no PIT partition". As I know the next thing to do is download a .pit file, although I've also read this can permanently brick the phone and I am feeling a little out of my depth. So I wanted to ask the advice/opinion of the more tech savvy people here before I continue going deeper and deeper down the rabbit hole.
-Would downloading a .pit file likely fix my phone?
-Is it really as easy to permanently brick it as people make it sound?
-Are there any safer options to try?
-Do you think I've probably already invalidated my warrenty anyway and have nothing to lose?
Thanks for any advice or opinions.
Your guarantee will still be valid. Stop messing with it and return it. Most likely the nand is bad and flashing a pit file will finish it off for good.
I wish I stole my HTC M9.