Database Users

Got a bricked X2, please help.

Ok, so i got fed up with my phone freezing so i thought i would get SEUS to
re install the rom, (mr1, mr2 is not available to me yet).
The indicator got to about an inch along when a message popped up saying
update failed.
Now i cannot enter bootloader to try again, the phone will not turn on, SE refuse
to help saying it is not released in the UK so i am not entitled to support.
I have not yet had a reply from where i got it from.
Is there any way to get this piece of junk going again?
Thanks.

Try to charge your battery on another phone / external charger.
I encountered a similar problem when trying to flash the X2. I received the UPDATED FAILED error, pulled out the battery, Volume Down + Power and gave it another try.
SEUS shouldn't brick your phone, maybe it's a problem with your battery.

The battery is at about 80%, i have tried it in my X1 as it is the same battery.
I tried the X1's battery in the X2 as well.
When i press the volume down and power buttons it vibrates for a fraction of a
second and then just stays on a black screen.

Let's try then a forced bootmode connection.
1. Insert the data cable into the phone without the battery plugged in.
2. Open SEUS and go to the connection screen.
3. While the software is searching for the phone, keep VOL DOWN + POWER and insert the battery.
After the phone vibrates, the software should recognize the X2.
This procedure generally applies to dead phones and sometimes works.
Post the result.

Still nothing, i kept the buttons pressed for about 30 seconds, then vista popped up a message 'usb device not recognised' the phone stayed as it did before and SEUS did nothing.

Sadly the support excuse they are using is what a lot of manufacturers do if you are in an area where they don't support it. This is the downside of buying a device on eBay etc. before it is "officially" released in your area. Contact the point of sale and hopefully they can send it in for you. You might have to pay shipping costs.
Leave your battery out and unplugged for an hour and then try again after that to revive it.

I did not even realise it had not been released in the UK, i got it from a UK website.
I am still waiting for them to get back to me, as it is Sunday they won't be getting back to me till Mon Tue i would think.
SE were fast though, less than an hour to reply, about the only credit they get though.
I have had the battery out for more than an hour a few times so that does not work.
Thanks for the suggestions though, keep em coming if there are any more.

WINE GLASS said:
Ok, so i got fed up with my phone freezing so i thought i would get SEUS to
re install the rom, (mr1, mr2 is not available to me yet).
The indicator got to about an inch along when a message popped up saying
update failed.
Now i cannot enter bootloader to try again, the phone will not turn on...
Click to expand...
Click to collapse
The exact same thing happened to me today, but I did not even get the update failed message (but I got the inch )
The phone is now bricked. No bootloader no nothing.

I guess you guys have the Singapore English versions? A lot of those retailers in the UK were getting them through Malaysia and so on. Then selling in the UK but not informing buyers that SE wont support it in the UK yet. It's really sad

It's a French X2, and I got it in France. I think I will have no issue with getting my X2 unbricked (or replaced), SE support is pretty good over here.
But if in the mean time someone has an idea or a trick on how to unbrick a X2 (other than the tips already listed in this thread), I would be happy to test it

HI!!
I have a T3238+ with a K3 Proccessor, I flash it with a wrong ROM, when I try to reflash again the K3Aid tool display the following error message : "Read FTM State Error" after i click the download mode button, Anyone can help me??? thank you!!!

-kOS- said:
HI!!
I have a T3238+ with a K3 Proccessor, I flash it with a wrong ROM, when I try to reflash again the K3Aid tool display the following error message : "Read FTM State Error" after i click the download mode button, Anyone can help me??? thank you!!!
Click to expand...
Click to collapse
Wrong phone, wrong forum, wrong idea.

-kOS- said:
HI!!
I have a T3238+ with a K3 Proccessor, I flash it with a wrong ROM, when I try to reflash again the K3Aid tool display the following error message : "Read FTM State Error" after i click the download mode button, Anyone can help me??? thank you!!!
Click to expand...
Click to collapse
Learn to "Read" and use the "Search" function newb.

Hi!
This has happened to me also. The solution was to connect the original charger (I usually charge from the USB port on my PC).
Try this:
1. Disconnect all cables from phone.
2. Remove battery.
3. Insert battery.
4. Connect original SE charger and charge for 5 minutes.
5. With the charger still connected, press volume down and then power on simultaneously - hold until SE logo appears.
If not working, repeat from step 1 several times (i tried 3 times before it finally worked).
6. Connect PC USB and run SEUS update.
Seems to me like the phone does not always charg from USB, and that when it enters the "black-screen-after-short-vibration-after-power-on"-mode it does not charge while in this mode.

Mod edit: not rom dev related, moved to general

well... when it say update fail but if save the new rom to ur phone then its fine, take the battery out and restart ur phone.. it should load the new OS.. my one says fail everytime.. so no problem for me

[Q] Help!! I bricked it

Please help. Background. I rooted it and had it set up to work on Cricket. Well I like the latest rom so I attempted to update it to a different rom. First one wouldn't boot so I was able to get into Clockwork mod and load a saved original version back. Then i tried flashinf the Rumm rom and now when I start it it immediately goes to the Rumm screen and stays there. I can't figure out how to get into the Clockwork menu agiain and it wont boot up. I can press camera down volume and power and get it into the bootloader. But I have no idea what to do from there. I am new to the droid X but I was successful with the HTC Hero. but this is new.
Thanks for any help

Bigstew33 said:
Please help. Background. I rooted it and had it set up to work on Cricket. Well I like the latest rom so I attempted to update it to a different rom. First one wouldn't boot so I was able to get into Clockwork mod and load a saved original version back. Then i tried flashinf the Rumm rom and now when I start it it immediately goes to the Rumm screen and stays there. I can't figure out how to get into the Clockwork menu agiain and it wont boot up. I can press camera down volume and power and get it into the bootloader. But I have no idea what to do from there. I am new to the droid X but I was successful with the HTC Hero. but this is new.
Thanks for any help
Click to expand...
Click to collapse
Looks like you'll want to SBF the device. Google search on how to SBF the Droid X and you should come up with some really good guides. Make sure you flash to 2.3.320 if you want to use the latest and greatest that Team Defuse has to offer. I would post a link to one of the guides, but I'm away from my computer today.
Sent from my DROIDX using XDA App

The only way. Into clockwork is pull battery so he says.if not send me your email to [email protected] I have the links.or download
http: market_android_com search?q=pnamerg. teamblackhat.leakloader
Its an app on marketplace call teamblackhat downloader
Sent from my DROIDX using XDA App

I have rsd lite and SHADO_X6_2.3.34_SYSTEM-ONLY.sbf I open the RSD and choose the sbf file but RSD doesn't find the phone. there are drivers loaded says Motorola Flash Interface v. 3.2.5.0. I have it in the bootloader says ok to program transfer mode usb. Thoughts
Thanks

Windows 7 64bit pro gives some difficulty with recognizing the phone. I suggest removing the motorola drivers and downloading them again.
I got it to work by plugging my phone in, then installing the drivers immediately after. It is screwy sometimes though.
Also RSD has device ID options. change that and see if it recognizes it. I also find that sometimes if I plug in my phone after RSD is open it finds it.

wow this has been a long process. after not able to get the phone to get recognized on Win7 I moved everything to my win xp comp. while it was in the provess of creating the image file ( took like an hour) the battery on my phone died. So I am charging the phone still. it's still creating a image file. Hope I can resume once phone is charged. I am not sure why the phone doesn't chrge while plugged into the USB port but ok. Thanks for the ideas so far. Will update later

Bigstew33 said:
wow this has been a long process. after not able to get the phone to get recognized on Win7 I moved everything to my win xp comp. while it was in the provess of creating the image file ( took like an hour) the battery on my phone died. So I am charging the phone still. it's still creating a image file. Hope I can resume once phone is charged. I am not sure why the phone doesn't chrge while plugged into the USB port but ok. Thanks for the ideas so far. Will update later
Click to expand...
Click to collapse
FYI it shouldn't take over an hour to create image. I flashed the .320 SBF 2 days ago and the whole process from start to finish was under 10 minutes.
Also, I don't believe it charges when in bootloader mode. You could power it via USB if necessary (involves stripping a USB cable). I've never done it but there are various tutorials. I'll look around.

http://www.droidforums.net/forum/droid-x-hacks/68222-unbricking-your-droid-x.html
See code corrupt error section.
The easiest option is to charge your battery in another X.

amasse said:
FYI it shouldn't take over an hour to create image. I flashed the .320 SBF 2 days ago and the whole process from start to finish was under 10 minutes.
Also, I don't believe it charges when in bootloader mode. You could power it via USB if necessary (involves stripping a USB cable). I've never done it but there are various tutorials. I'll look around.
Click to expand...
Click to collapse
yes I charged the phone to 100% and tried again and again the battery died before it finished. the sbf file I have is 280 Mb. If there is a smaller one then maybe it will work

It's more likely that the SBF file you have is bad or there is still some sort of USB driver issue going on. Try downloading it again from wherever you got it.
The phone should not go from 100% to dead in an hour. Also the SBF flash shouldn't take nearly that long.

for now I am stuck. I can't get the phone to charge the battery any more. When I plug the phone into the wall it just goes to the bootloader screen by its self and has an error number and a message that the battery is low. So I ordered some batteries with a wall charger. Once those arrive I will try again. thanks for all the help you guys are giving me. update later date

phone Display is gone when rooting with step1

hye guys,
im totally new here and i tried rooting my x10
with the xda-dev section
but things turned out to be ugly as i cant see any display after step1 completed,
pls im very nervous and thinking i might have broken it down ,
any help wud be really appreciated.
thnx.
the version i had was 2.1

If your phone wont turn on or you got no display try reflashing with seus for now. That should fix you up for now.
After that i can help you out with flash tool.
Sent from my X10a using XDA App

brother,
it will be awkward to ask too much but i really dont get u.
im fresher here,
so wud u go easy on me,/?pls

Ok, first if you havent already, and I can almost guess you haven't you need to download PC Companion and Sony Ericsson Update Service (SEUS) to your computer.
Once you do that, turn your phone off, and run SEUS. Follow the steps and select your phone when given the option. After you select your phone, it will tell you to plug your phone into your computer in flash mode, basically just hold the "back" button on your phone until SEUS tells you to release it. If you have a new upgrade available then feel free to do so,..if you already have the latest software then in the bottom right corner you will see an option that says "install" click on it and proceed. It will reflash your phone for you and should be ready to go once done.
Good luck

i did just as you said , but i there is no "install" option at the last step
pls help

[SOLVED] Xperia Arc bricked?! HELP!

hey fellas...
....as the title says, i'm afraid i might have bricked my device!
what happened: assumingly, the battery was too low to perform a firmware flash via flashtool 0.2.9.1 - despite that, i tried it. the result was an abort of the process (error flashing, process aborted)....
....the situation now is that the device won't even boot anymore, it just shortly vibrates, that's it! (i've tried to reflash the uk 184 firmare several times, all resulting in process aborted....windows vista, 64 bit)...it does not matter if i use flashtool 0.2.9.1 or 0.2.9....
what was done to the device before: a successful flash of the uk 184 firmware, a successful unlock of the bootloader (done on a computer running winxp, 32bit)....
...it'd be great if anyone of you guys had some advice, any help is greatly appreciated!
regards,
paddy
EDIT: reflashed generic uk 184 on a windows xp (32bit) computer, everything went smoothly and the deivce is running again! thank you everybody that tried to help!!!!

So you battery is charged? What happens when you plug it in? Does the battery charging icon shows up?

no, nothing shows up....only the battery led keeps blinking, which is kind of strange

Leave it for a few hours and see if it charges. Its possible your battery wont charge, this was a problem with motorola defys and there is a mcgyver workaround but I would say only attempt it if your sure it will fix it and done mind blowing up your phone if it goes wrong. So basically only as a very last resort
have you tries SEUS?

thanks for replies so far....nope, i haven't tried seus yet, i'll do that right now.....despite that, i did try pc companion to "repair" the phone, which actually resulted in pcc telling me it is not able to do anything since the phone is running a modified firmware
edit: seus won't workt either, "firmware is not supported"

Try turning off holding the menu and back button starting up seus with the usb already plugged in. When detects phone let go of menu button but keep the back button held until it says let go is the boot loader unlocked. I believe its impossible to brick if its not
Sent from my LT15i using XDA App

if possible get the battery charged from some other device or external charger...
and then try flashing via flashtool again..

this is weird....just tried it on a win7 computer, doesn't work either, flashing gets aborted immediately...even stranger is the fact that i've just let the device chrage for 45 minutes, still, the led just blinks in flashmode color, won't turn on at all and just shortly vibrates....fastboot recognizes the device though

279Paddy said:
this is weird....just tried it on a win7 computer, doesn't work either, flashing gets aborted immediately...even stranger is the fact that i've just let the device chrage for 45 minutes, still, the led just blinks in flashmode color, won't turn on at all and just shortly vibrates....fastboot recognizes the device though
Click to expand...
Click to collapse
have u been using the testing recovery files that were posted?

no, i haven't used them
when i connect it via usb, it seems to get stuck in flashmode

279Paddy said:
no, i haven't used them
Click to expand...
Click to collapse
hm... ok so the chargemon is not changed....
i dont know if fastboot can flash system.img / boot.img even at low battery...
still i would recommend u try to get the battery charged externally then try normal flashing via flashtool...

so you'd say it's probably the battery causing the problems? mh, okay, i'll see if i can find a way to charge it externally....hopefully the brick is reversible

Unbricked a Hard Bricked Captivate - Truly Invincible Phone - No JTAG

Past few days were the worst for me as I had Hard Bricked my Captivate.
*** History*** (You may skip this is you wish)
This all started few days ago, like every cappy owner I too had a craze of testing different Roms, untill i settled for RemICS. But soon after a month I got bored and moved to Nostalgic 6.2. The rom looks good, but then when I called someone, there was a lot of static on the line and the other person could not hear me. So I decided to try a different modem, so I installed a different modem and things went back to normal.
Later I found another post on XDA, a comparision table for different modems on captivate. So i wanted to give a try, & this is when things started to get rough.
I installed a few modems and then found that my mobile would not get any network signal. So I planned to use ODIN One-Click (I897UCJF6-final-OCD-REV0) and go back to factory. I used ODIN and was able to go back to factory and everything was back to normal.
***When & How I Messed up my Cappy***
As I was back to Factory (2.1) I wanted to upgrade it to GingerBread. I used Samsung Kies to update it to 2.2 Froyo and while this happened, Kies downloaded the firmware, however while flashing the phone it was stuck at 3% and was there for about 4 hours and wouldnt move further, and the screen was solid green and no images or characters. So I took the risk and manually killed Kies and rebooted the phone. Now the phone would come to AT&T screen and was stuck there, tried the firmware update again and still had the same issue. This is when I decided to go back to Factory using ODIN. Used Odin to flash the phone again and it wouldnt move ahead of Factoryfs.rfs and would be stuck there for hours. So I took the risk and disconnected the cable (I know there is a risk of hard brick, but I trust this phone so much and was impatient to give it another go) and restarted the process. It again did the same thing, but this time the phone shutdown and was on a Black Dead screen. I disconnected the phone and tried to put it to download mode and it wouldnt work. The phone would just not show any signs of life. Connected the charger to check if there is any display and still had a dead screen & no sound. ODin would not recognise the phone anymore and no signs of any PCI device in device manager. Even tried Heimdal and still no go. Tried this for the whole day and i was preety satisfied that this might need JTAG.
I had also left a post for connexion2005 on http://forum.xda-developers.com/showthread.php?t=1041042
By now I had started to surf ebay looking for another Cappy or Infuse. All the signs that the phone gave me were of a Hard Bricked Captivate. However I did notice that if I reseat the battery and then try to power ON the phone, there was no sign of life, but after leaving it for 20 minutes the phone would get a little warm. So I knew that the phone was still alive, just a no video/no post kind of situation.
It was 11:00 pm when it just struck to me that I should try Linux, as there was a faint possibility that Linux may recognise the phone if it was in any kind of life mode.
So i grabbed a copy of Ubuntu and installed it on the same laptop, where the phone showed no life and used the same usb cable. Well once the OS was installed all I did was tried using the Vol UP + Vol Down + USB to put it into download mode and to my surprize the phone immediately went into Download Mode and there was display. :good::good::good::laugh::good::good::good:
Then I just flashed the phone with ODIN and went back to factory........ and everything is back to normal. :laugh::laugh::laugh:
I wouldnt be trying to brick the phone again, but if anyone has a hard bricked phone can definately try this and hopefully should be able to boot back. Please let me know if it wokred for you.
I am not sure if this is the right section to post this but, definately it worked for me where the phone showed all the symptoms of a Hard Bricked Cappy. If the moderators feel it should move to a different section, please feel free to move it.
I am now convinced that Captivate is Immortal...... :angel:\m/:angel:
Please use the Thanks:good: button if this worked for you.:good:
I may not be able to recreate the issue and havent captured any images, but if you have a dead cappy, you can definitely try this and let me know.

Glad your phone got fixed, thanks for taking the time to write it. I'd suggest moving it to captivate general though. This is the development thread.

You didn't have a hard bricked cappy. You had a soft bricked cappy. A hard bricked cappy is when the primary and secondary bootloaders get corrupted, this also breaks download mode. You interrupted the odin process when it was at factoryfs, which is a long time after it's already successfully installed bootloaders.
The fact it booted right into download mode shows us that it had simply been soft bricked the whole time. This has nothing to do with linux, Kies had installed its own USB drivers that do not support the proper communication with the phone in download mode, this is why when you tried to odin it was being so fussy - it was using Kies USB drivers.
A simple removal of kies, installation of the correct samsung USB drivers, and plugging your phone into a different USB port even would have allowed odin to flash properly. This is why when you went into linux it worked right off the bat, because you didn't have kies and kies drivers in linux.
The captivate is far from immortal - I invite you to see what happens when you interrupt an odin session while it is flashing boot.bin and sbl.bin - you'll have yourself a real hard brick very quickly

fohdeesha said:
The captivate is far from immortal - I invite you to see what happens when you interrupt an odin session while it is flashing boot.bin and sbl.bin - you'll have yourself a real hard brick very quickly
Click to expand...
Click to collapse
believe it or not my cable got pulled out right in the middle of the factoryfs and since i cud still enter download mode i tried it again and then my power got cut in boot.bin part, and i was actually still able to boot into download mode even when nothing showed up on my screen, all i did was first pull the battery, hold the down and up volume button, insert usb into phone and insert battery, and somehow it booted into download mode according to odin, so idk the phone may not be invincible, but its close

fohdeesha said:
You didn't have a hard bricked cappy. You had a soft bricked cappy. A hard bricked cappy is when the primary and secondary bootloaders get corrupted, this also breaks download mode. You interrupted the odin process when it was at factoryfs, which is a long time after it's already successfully installed bootloaders.
The fact it booted right into download mode shows us that it had simply been soft bricked the whole time. This has nothing to do with linux, Kies had installed its own USB drivers that do not support the proper communication with the phone in download mode, this is why when you tried to odin it was being so fussy - it was using Kies USB drivers.
A simple removal of kies, installation of the correct samsung USB drivers, and plugging your phone into a different USB port even would have allowed odin to flash properly. This is why when you went into linux it worked right off the bat, because you didn't have kies and kies drivers in linux.
The captivate is far from immortal - I invite you to see what happens when you interrupt an odin session while it is flashing boot.bin and sbl.bin - you'll have yourself a real hard brick very quickly
Click to expand...
Click to collapse
And unbrickable mod fixes this. Therefore the captivate is pretty much immortal. You can even take a hard bricked cappy, do the unbrickable mod once it's already broken, and still have it return to working order.
Way say you now?

Arisenhavok91 said:
Way say you now?
Click to expand...
Click to collapse
What*
I would say of course JTAG'ing a hardbrick is capable of unbricking it, same for about any other device in the world with volatile memory based firmware. this is not a magical new discovery.
They aren't called hard bricks because they become impossible to recover, corrupting bootloaders is called a hardbrick because it takes HARDware modification to fix, not software utilizing the preexisting hardware. Anything else? Anyone else have some wonderful insider info as to how linux can make download mode magically appear? I'm loving the knowledge in here, really. If you're going to spread misinformation, we please ask that you do it in the correct subforum.

Of course, I argued that the Samsung Captivate is "immortal" due to it's ability to be resurrected at times when even a JTAG would fail.
So back to my point of you saying "the captivate is far from immortal" - what say you now?
Edit: If you can't take someone poking fun as such, please don't bother to respond. I won't look back at this even if you do reply, so please, take a chill pill... or some midol.

Arisenhavok91 said:
So back to my point of you saying "the captivate is far from immortal" - what say you now?
Click to expand...
Click to collapse
I would continue to say the captivate is far from immortal, in the same context as my original post you seem so excited to quote - in a software recoverable situation. We are not talking about JTAG and hardware modification anywhere in this thread. he was claiming the captivate is immortal in regards to all situations being software recoverable by magically switching to a different OS, if you could please put on your reading comprehension and context goggles the pieces of the puzzle might start coming together. Also, do not ask questions you won't bother reading the answer to. Thanks!

I say the captivate is pretty much inmortal! xD even without power button ive been using it with no problem and getting into DLmode.
Sent from my SAMSUNG-SGH-I897 using xda app-developers app