Hi everyone - I'm having problems getting my device to turn on properly, and I can't seem to find a solution anywhere. I bought the SGP311, and everything was going great with it until like 2 weeks ago when it just wouldn't turn on properly. The red light on the side next to the power button was on, and I had to mess with the buttons in different combinations (I think while the device was plugged in) in order to get it to turn on properly. It was not out of charge or low on charge at this point, and I had never tried to alter the device in any way prior to this.
I encountered the same problem yesterday where the device wouldn't turn on, and I couldn't get it to turn on no matter what I tried. I thought that it might be a problem with the OS, so I used FlashTool to install a custom FTF file (a Japanese one), and it wouldn't boot up after. I plugged it directly into a power source (not through my computer), and eventually the device turned on and I was able to go through setup, etc.
The OS had a lot of Japanese text, even though I had selected English, so I thought I'd wipe the tablet and update the OS using the Sony Update Service tool, which successfully detected the device and did a factory reset and software update after I put the device in flash mode. The app then told me to unplug the tablet and power it on, but nothing happens when I hold the power button down.
Here's what happens when I try to do different button combinations:
With the device plugged into the power (ie into the wall):
The red light comes on and stays on.
If I hold the power button only for a few seconds and then let go, nothing happens (red light stays on).
Hold up on the volume and hold power, the white light flashes once and then nothing happens (red light is off and stays off).
Hold up on volume and wait for the 3 white light flashes then let go gives me back the right light, which then stays on.
When the device is unplugged:
the red light remains on.
Holding the power button doesn't do anything (red light remains on).
Holding volume up and power causes the white light to blink once and then the red light turns off (as before).
Holding volume up and waiting for the three white flashes does not return the red light (unlike before), but then plugging the device back into the wall makes the red light return.
When the device is plugged into my laptop:
Red light comes on and remains on.
Holding up and power causes the white light to flash once and then the device actually booted, and I went through the setup (but it was still in Japanese, for some reason). When I power off the device, I am unable to power it back on by holding the power button. I am unable to turn it back on after by using the method (holding the volume up and pressing power when plugged into my computer). It just stays off.
Holding power up for long enough to cause the 3 white blinks returns me to the red light.
My device is charged through all of this (>80%), so I don't think it's a battery thing, but boot up can't just be happening randomly. When the device actually does turn on, everything functions normally. It's only when it's turned off that I can't get it back on without dumb luck each and every time.
Has anyone encountered anything like this? It's really driving me nuts. Please let me know if I need to clarify things more. I could really use help on this because I don't think I possess the cranial capacity to solve this on my own.
Thanks!
I almost bricked my device and I was having exactly the same problem as you are. So I thought I'd share my solution with you.
To fix it try this:
1. Download Emma (Sony's own flash tool program).
2. Press and hold Volume up and Power button while the device is off... wait for the first white light AND the 3 white lights.
3. Hold the Volume down button while plugging the device into the computer (this should boot flashmode and Emma should detect the device)
4. On Emma it should detect the device and start downloading the latest version of android (4.2.2 - the file should be about 800mb). Once it has downloaded click on 'Apply Service'.
5. Let the installation finish (this may take a few minutes)
6. Turn on the device and it should be back in english with the latest Android version! Enjoy
One thing to note: The battery may start high and seem to discharge very quickly at first - this should settle when it hits the actual power left in the battery. (Mine was at 95% and falling about 10% per minute until it hit 30%!)
Thanks for your reply! Were you having the same problem with it not turning on?
Emma always tells me that it's detecting a locked device, and it won't do anything with it. I'm scared of unlocking it in case I have to bring it to Sony to have it repaired.
Wonka_Vision said:
Thanks for your reply! Were you having the same problem with it not turning on?
Emma always tells me that it's detecting a locked device, and it won't do anything with it. I'm scared of unlocking it in case I have to bring it to Sony to have it repaired.
Click to expand...
Click to collapse
Yes I was having the same problem. My device didn't even get detected by my computer either! If you haven't done anything with the device, the best option is to send it back to Sony... They should replace it if it's not been rooted or unlocked.
With my case though, I couldn't do that so I just used Emma As long as you follow the instructions on the Sony development site properly, unlocking it shouldn't do any harm (although it will void your warranty) and Emma will be able to flash the device easily. Also you can relock the device after - which means if the problem happens again in the future, you can just take it to Sony.
It really depends on which you are prepared to do... Wait a while for Sony to send a replacement... or attempt to fix it yourself! One thing I'm not sure about... you mentioned that you flashed the Japanese FTF version onto your device? Sony might get a bit funny about that...
It was Sony's software that flashed the Japanese software to my tablet after I selected a factory reset and software update. It even asks me if I want to use my phone or some such, so I'm wondering if it was flashes with the Xperia Z phone OS? Would you know where I can get a stock US firmware?
There might have been something weird set on the tablet initially, but I'm not sure. Maybe I downloaded the software from a Japanese site?
I'm sorry I can't offer any help, but I can offer some advice for others who may be reading this tale of disaster....
- if your newly bought device goes wrong, take it back.
- if you are going to unlock your bootloader, you will need an unlock code from Sony. Some people say once this is given you have lost your warranty anyway (you will have provided your device details to Sony to get the code)
- if you unlock your bootloader without backing up the TA partition you will lose data such as DRM keys which are unique to your device and you will not be able to restore your device to its original state, even if you re-lock the bootloader. Sony will see this.
GretaLewd said:
I'm sorry I can't offer any help, but I can offer some advice for others who may be reading this tale of disaster....
- if your newly bought device goes wrong, take it back.
- if you are going to unlock your bootloader, you will need an unlock code from Sony. Some people say once this is given you have lost your warranty anyway (you will have provided your device details to Sony to get the code)
- if you unlock your bootloader without backing up the TA partition you will lose data such as DRM keys which are unique to your device and you will not be able to restore your device to its original state, even if you re-lock the bootloader. Sony will see this.
Click to expand...
Click to collapse
Well the answer seems simple... just take it back to Sony! If you haven't unlocked the bootloader you should be fine to get a replacement.
martyn12444 said:
Well the answer seems simple... just take it back to Sony! If you haven't unlocked the bootloader you should be fine to get a replacement.
Click to expand...
Click to collapse
That's actually what I'm going to do.
martyn12444 said:
Well the answer seems simple... just take it back to Sony! If you haven't unlocked the bootloader you should be fine to get a replacement.
Click to expand...
Click to collapse
I wasn't asking a question, just giving advice.
Wonka_Vision said:
It was Sony's software that flashed the Japanese software to my tablet after I selected a factory reset and software update. It even asks me if I want to use my phone or some such, so I'm wondering if it was flashes with the Xperia Z phone OS? Would you know where I can get a stock US firmware?
There might have been something weird set on the tablet initially, but I'm not sure. Maybe I downloaded the software from a Japanese site?
Click to expand...
Click to collapse
In your first post you state " so I used FlashTool to install a custom FTF file (a Japanese one), ".
Now you are saying "It was Sony's software that flashed the Japanese software to my tablet"
Anyway, best of luck to you:fingers-crossed:
Could you let us know if Sony exchange it for you, I'd like to know
GretaLewd said:
I wasn't asking a question, just giving advice.
In your first post you state " so I used FlashTool to install a custom FTF file (a Japanese one), ".
Now you are saying "It was Sony's software that flashed the Japanese software to my tablet"
Anyway, best of luck to you:fingers-crossed:
Could you let us know if Sony exchange it for you, I'd like to know
Click to expand...
Click to collapse
Oh yeah so I did install a Japanese FTF file myself, but then when I tried to use the Sony Update Service it reinstalled the Japanese version and updated it to 4.2.2. It seems to have updated it to the Xperia Z (phone) software though because it asks me if I want to power off or use the phone at the beginning. Do you know if it's possible to flash back to US? I've tried US FTFs with flashtool and it always comes up as Japanese whenever the device bothers to boot up. Emma says it has a Japanese filesystem.
I spoke to a lady on the phone today and she said that I am still under warranty as long as I didn't try to root or unlock it, which I never did for either. She raised a question about the Japanese system though saying that I would have had to have rooted the device to install a Japanese version (which is untrue), but I told her I never rooted anything. Anyway she's sending an RMA package. I would still like to set it back to US (even a previous android version) if anyone knows how I can accomplish this. Again, all the US ones I've tried keep me at the Japanese version.
Thanks!
GretaLewd said:
I wasn't asking a question, just giving advice.
Click to expand...
Click to collapse
I know... I was just saying what I thought was the best choice from your advice
Wonka_Vision said:
Oh yeah so I did install a Japanese FTF file myself, but then when I tried to use the Sony Update Service it reinstalled the Japanese version and updated it to 4.2.2. It seems to have updated it to the Xperia Z (phone) software though because it asks me if I want to power off or use the phone at the beginning. Do you know if it's possible to flash back to US? I've tried US FTFs with flashtool and it always comes up as Japanese whenever the device bothers to boot up. Emma says it has a Japanese filesystem.
I spoke to a lady on the phone today and she said that I am still under warranty as long as I didn't try to root or unlock it, which I never did for either. She raised a question about the Japanese system though saying that I would have had to have rooted the device to install a Japanese version (which is untrue), but I told her I never rooted anything. Anyway she's sending an RMA package. I would still like to set it back to US (even a previous android version) if anyone knows how I can accomplish this. Again, all the US ones I've tried keep me at the Japanese version.
Thanks!
Click to expand...
Click to collapse
If you haven't rooted or unlocked the device and they said they'll replace it... I wouldn't bother trying to get back to the US version. Just send it off as soon as possible before you get tempted to try and 'fix' it yourself
Just as a followup: Sony replaced the device with a SGP312. I have no idea what was wrong my original one, but it must have been pretty severe.
I removed the rear cover with a little heat and done a battery pull. Works perfectly now
Related
First of all sorry for my english not good.
Start : with my HD2 have brick after task29 and not success to flash new ROM I'm take USB. cable out and try to open my HD2 in to boot loader by put volum down + power bottom but screen not show any image or 3 color my phone it only long vibration pull battery out waiting 30 minute and put battery in and try to open my phone to boot loader but is same only long vibration.
Now : can not do any think with it when try to plug power in my phone is auto startup and long vibration.
I'm search on google and in this forum not have some one face problem same as me please help me to fix this.
Any body please help me, I'm love it because now we can run both WM. and Android
Upppp waiting for your help
Did you try a long press of the reset-button?
You could try to put the original Stock Image from HTC onto the root-folder of your SD-Card, rename it to LEOIMG.nbh and Push Vol up + Vol down during start and follow the on-screen instructions if it works.
Otherwise use Search-Function in the forum.
ı have jtag HTC for samsung and HTC devices if u want send for repair to me..
www.sevgigsm.net/forum
admin..
I use ORT
Did you check to make sure your radio version was correct before flashing? This is probably the number one reason for bricking.
Check this thread it may help you if you did the flash properly:
http://forum.xda-developers.com/showthread.php?t=668347
i got same problem now...
no screen, no boot, vol down+ power oso same
no screen just a long vibration
anybody help?
I am using the correct radio so don't tell me I am using a wrong radio or something, I have been flashing for 4 months so I know EXACTLY how to flash.
now i can neither get into tri-color or hard reset so don't tell me to flash or smth like that, just tell me how to recover properly
Don't tell us to use search or something because seems like only 2 of us is encountering this problem in the internet
I'm exactly the same problem as TS coz it juz auto go vibrate when plug in battery
This problem actually started when I flash ROM halfway, it stucked and failed...
the device is already HSPL-ed!!!!
but why the F it cannot get into tri-color bootscreen now?
Also, I have to state that my device already got several problems before, my device was very hard to bootup as it will always stuck at HTC screen w/o red version number at bottom left corner, must keep on removing and reinstall battery and reboot until it can boot, not an issue with rom/radio/sim/sd as I tried flash proper rom and radio and remove sd and SIM.
my device also seems like got problem at the gps chip, because when using it for a few minutes, it will lost signal and never reconnects unless i soft reset, after use gps the device will also use battery VERY FAST(-100mA in standby, from -4mA).
now i cannot flash to stock completely, how do I get warranty it?
at the long vibrate, when i plug in to my pc, it will keep on got usb connected and disconnected sound
and dont know what device is connected as not shown in found new hardware and device manager
I also have been searching all possible keywords about what me and TS encountered but all linked to completely UNRELATED results(like search for long vibrations only link to people asking how to make vibration long and 1st result is this thread)
bountygiver said:
This problem actually started when I flash ROM halfway, it stucked and failed...
the device is already HSPL-ed!!!!
but why the F it cannot get into tri-color bootscreen now?
Also, I have to state that my device already got several problems before, my device was very hard to bootup as it will always stuck at HTC screen w/o red version number at bottom left corner, must keep on removing and reinstall battery and reboot until it can boot, not an issue with rom/radio/sim/sd as I tried flash proper rom and radio and remove sd and SIM.
my device also seems like got problem at the gps chip, because when using it for a few minutes, it will lost signal and never reconnects unless i soft reset, after use gps the device will also use battery VERY FAST(-100mA in standby, from -4mA).
now i cannot flash to stock completely, how do I get warranty it?
Click to expand...
Click to collapse
Silly question, but are you holding (and keep on holding) the Volume-Down button while you press the power button?
of course YES
i told you i have been flashing for so long
Leo from T-Mobile. Hi! I've got same problem. After flashing new (next) rom phone definetely died. Phohe is currently simfree and with HSPL. Only one reaction is short vibration after press power button. I searched everywhere. My phone has no bootloader but system see him as Qualcom CDMA Technologies MSM. Thats all, any ideas? Please and thanks for advice.
czaruch said:
Thats all, any ideas?
Click to expand...
Click to collapse
Yes, you flashed a non tmous stock rom that included a ..51.. radio and it destroyed your phone.
What rom? exact filename please.
thank you so much.
I bricked a Leo with the .51 radio. I think I read that is a European or otherwise foreign radio. Since your ROM has Euro in the name.......
czaruch said:
ROM_Leo_HTC_WWE_EastEurope_1-66.
Click to expand...
Click to collapse
The full filename for that rom is
RUU_Leo_HTC_WWE_EastEurope_1.66.479.2_Radio_CRC_Si gned_15.32.50.07U_2.07.51.22_2_Ship.exe
it comes with a version x.xx.51.x radio, and they do Not work on tmous (t mobile us) phones. They kill them
Your phone is dead, sorry. No known fix.
warranty or repair (or JTAG if you are brave and have the money)
a friend of mine bricked his phone. he then tried to microwave it, but that didn't work after that he took a power wire from an old computer, cut it and connected it directly to the phone's parts where the battery would go...this completely f-ed his phone up (he also used a lighter to fake a powersurge of the battery). Then he called htc and a few weeks later he got a new hd2!
GOOD LUCK
lol, he doesnt need to do any of that, its allready as dead as it can be. Loads of epople have had them replaced under warranty with this kind of brick. It wont start, so htc/tmo cant see that its been hacked.
Hi! I understand and realy sad. Somebody know where could I fix it in UK? And how much for this pleasure. Thanks.
i would contact htc, see what they have to say. (dont say you flashed it, it just stopped working")
First, please, I tried tons of different things. I'm a linux kernel hacker too, although I never hacked android related stuff yet.
When I try to turn the phone on, it just quickly blinks the green line, vibrate and nothing else happens.
It was running firmware version 1.6 fine until I tried to upgrade the phone using a windows xp running in a vmware VM. I tried companion, SEUS and FlashTools. All left the phone running with the yellow exclamation mark after.
I continue trying to flash it until suddenly even the exclamation mark stopped showing up.
After that I moved to a native windows installation and SEUS went all the way through updating the phone, but the phone never turned on again. It just happened what I described above.
I already tried everything I came across with in the forums: flashing versions 2.1 and 1.6 from different places, with different versions of the FlashTool, and SEUS, and the companion .... it always goes all the way through, saying all ok, but when I turn on the phone: same-o. just quickly blinks, vibrate and dies.
Any idea? had I really hard broken my phone?
Please, any direction would do.
Interestingly - I have excatly the same situation with my partners phone. Attempted to downgrade to 1.6 using a couple of methods - editing build.prop and then SEUS and flashing this firmware.
Problem I have now is SEUS says I have the latest firmware and doesn't offer an update - I guess this is because the version of the software that is installed is higher than what is currently avaiable to the CDA I have put in the build.prop
Next I tried putting 2.1 back on from this thread.
The phone will not boot still it does excatly what you have said - blinks, vibrates and then turns off!
Thank you for the reply. It is good to know Im not alone
In my case SEUS always says there is a newer version and flashes the phone. It goes all the way to the end and says the upgrading was successful.
Would it be possible that although the phone "accepts" being flashed, it is not actually writting anything to a persistent state?
Is there a way to verify if what I flashed is really there? Otherwise SEUS should way nothing to upgrade, since it already did it all the way through successful.
easy question:
are you sure you have battery remaining to start it up and flash? if not, try to charge the battery on another phone.
I guess so.
I'm using a multimeter to measure the power of the battery, which varies from 3.6 to 4.1 volts, depending on how long I leave it on the charger.
So although the phone gives no indication of being charged, I guess that measure is enough to say it is being charged, right?
I've even just tried Omnius Server, which flashed perfectly fine, but still the phone won't boot Its completely dead now
Yep. I also tried that. Wasted money..
So far no change.. the thing is still a brick.
.. well, a brick is at least heavy enough to actually deal some damage when thrown..
Hah Just getting it exchanged now - tried everything - given up!
well, just in case you have it on warranty, go ahead
take it to the shop
repair
stop wasting time and money... go to a GSM SERVICE... you need service tool to revive your phone if it's deadboot...
i use setool to flash sony-ericsson phones and it's the best flash tool...
if it's bootfcked, then you need jtag's...
@sanyyous
setool will flash the phone just like SEUS or FlashTool will, right? or it will do some other kind of flashing witchery?
and jtag you mean hardware debug and service, right?
the issue is: I bought the phone in London and I'm in Brazil now. So either I fix or I see a trash bin in this little x10's fate.
setool flashes the same way than my tool,but it has more tricks afterwards for some other things.
For me it sounds like :
1.) False USB-Port or Cable
2.) False nand
Please try to following:
Go into your car with a laptop and flashtool on it -> Start the engine and pull down the AC to the coldest state it can do.
hold your phone DIRECTLY with the battery in Front of the cold airstream.
Flash it now
I have recovered a few dead phones so, the problem is that they get too hot and the nand shows errors while temporary placing the flashimages -> If so the loader rejects the image because of checksum fail.
-> Give it a try, if it don't work you have to send it to service.
Regards
Bin4ry
Man.. I will try as soon as I get home... and if it works.. expect a good donation.
Out of curiosity - did it work?
Sent from my X10i using Tapatalk
I still couldnt try.
In Italy now. I'm going back to Brazil only Feb 3rd.
Meanwhile I'm trying to convince my gf that she couldnt break the phone even further for trying. Hopefully I'll lure her into doing it until this weekend.
Firgers crossed.
Bin4ry said:
setool flashes the same way than my tool,but it has more tricks afterwards for some other things.
For me it sounds like :
1.) False USB-Port or Cable
2.) False nand
Please try to following:
Go into your car with a laptop and flashtool on it -> Start the engine and pull down the AC to the coldest state it can do.
hold your phone DIRECTLY with the battery in Front of the cold airstream.
Flash it now
I have recovered a few dead phones so, the problem is that they get too hot and the nand shows errors while temporary placing the flashimages -> If so the loader rejects the image because of checksum fail.
-> Give it a try, if it don't work you have to send it to service.
Regards
Bin4ry
Click to expand...
Click to collapse
If this works, it's a miracle.
Maybe trying the fridge would have the same result, but all that ice could damage the phone .
Good luck and I really want to know if it works.
Yeah, on the fridge the moisture would probably ruin the phone even further. .. if thats at all possible.
And believe me, no one would wanna see if it works more than me.
<girlfriend-apeal>
you see, everyone wants to know if that works. please, you wont ruin the phone further just by trying it )
</girlfriend-apeal>
My wife's x10 is OK, so it would just be out of curiosity for me .
Good luck.
I got my gf to try but it didnt work
I'll try it myself when I get home next week, but I dont think thats gonna work..
Anyway, I drop by next week to comment on the final status.
Thanks for the replies so far.
fabioroger said:
First, please, I tried tons of different things. I'm a linux kernel hacker too, although I never hacked android related stuff yet.
When I try to turn the phone on, it just quickly blinks the green line, vibrate and nothing else happens.
It was running firmware version 1.6 fine until I tried to upgrade the phone using a windows xp running in a vmware VM. I tried companion, SEUS and FlashTools. All left the phone running with the yellow exclamation mark after.
I continue trying to flash it until suddenly even the exclamation mark stopped showing up.
After that I moved to a native windows installation and SEUS went all the way through updating the phone, but the phone never turned on again. It just happened what I described above.
I already tried everything I came across with in the forums: flashing versions 2.1 and 1.6 from different places, with different versions of the FlashTool, and SEUS, and the companion .... it always goes all the way through, saying all ok, but when I turn on the phone: same-o. just quickly blinks, vibrate and dies.
Any idea? had I really hard broken my phone?
Please, any direction would do.
Click to expand...
Click to collapse
i tried to install the gingerbread theme but after i moved the framework file into system/framework folder my phone rebooted by itself and blocked to SE logo screen.... i wanna flash the phone but i'm unable to switch usb debugging mode on..... any suggestions to turn the usb debugging on or flash the phone witout it....???? tnx in advance 4 any suggestion
Here's the situation:
My sister did something bad about her phone(x10 mini pro).
It has a newly installed stock rom (the phone used to have cyanogen but she told me to revert it back to stock).
She told me that all she did was install SonyEricsson Xperia Flasher on her machine and used it to flash her x10 mini pro. The flasher tells her that it is succesfull but when she turned off her phone for a restart, the phone does not turn on anymore. I have tried charging the battery overnight as well as using a different working battery but it does not help. Pressing the power button does nothing. No led light, no vibration, nothing. I have also tried different button combo(tried almost any combination) found here in forums but it does nothing as well.
I bought this device to a tech guy which is in a mall and he is charging me Is there something else I can do to fix thing device without spending? Is there another way other than unbrickin it with JTAG?
Any help or suggestion would be greatly appreciated.
Edit:
SEUS does not help because the phone cannot be detected when plugged in because it doesnt turn on and yes, I tried using a different usb cable.
I think my sister flashed the wrong kernel.
Does the battery charge (green LED)?
Do you know someone with the same phone? Try his/her battery. I had this problem too once, it would not turn on or anything, untill i tried to insert another battery. Then it started up and all. After clear battery stats, it worked again with my own battery.
This gives me the assumption, that is has something to do with battery stat (doh') - therefore all guides about doing a SEUS or other stock flash, should also instruct users to do a clear battery stat before the stock-flash.
Any one correct me on this if i'm totally wrong
gonix said:
Here's the situation:
My sister did something bad about her phone(x10 mini pro).
It has a newly installed stock rom (the phone used to have cyanogen but she told me to revert it back to stock).
She told me that all she did was install SonyEricsson Xperia Flasher on her machine and used it to flash her x10 mini pro. The flasher tells her that it is succesfull but when she turned off her phone for a restart, the phone does not turn on anymore. I have tried charging the battery overnight as well as using a different working battery but it does not help. Pressing the power button does nothing. No led light, no vibration, nothing. I have also tried different button combo(tried almost any combination) found here in forums but it does nothing as well.
I bought this device to a tech guy which is in a mall and he is charging me Is there something else I can do to fix thing device without spending? Is there another way other than unbrickin it with JTAG?
Any help or suggestion would be greatly appreciated.
Edit:
SEUS does not help because the phone cannot be detected when plugged in because it doesnt turn on and yes, I tried using a different usb cable.
I think my sister flashed the wrong kernel.
Click to expand...
Click to collapse
The Experia Flasher is not for the 2010 devices i think, so she may well have flashed the wrong firmware. SUS doesn't need to detect the phone, if you choose update and it can't recognise the phone it offers a repair option, this lets you choose the model yourself, it will download the proper firmware and all you have to do is connect your phone in flash-mode (ie hold the back-button while you plug in the usb-cable).
But she may well have bricked it properly and in that case, JTagging it is the only option to get it back up and working.
Screen-shots are from the old PC Companion, byt they still looks very much like them in the new version
http://forum.xda-developers.com/showpost.php?p=17458289&postcount=8
Emperor.dk said:
Does the battery charge (green LED)?
Do you know someone with the same phone? Try his/her battery. I had this problem too once, it would not turn on or anything, untill i tried to insert another battery. Then it started up and all. After clear battery stats, it worked again with my own battery.
This gives me the assumption, that is has something to do with battery stat (doh') - therefore all guides about doing a SEUS or other stock flash, should also instruct users to do a clear battery stat before the stock-flash.
Any one correct me on this if i'm totally wrong
Click to expand...
Click to collapse
Oh I know someone who has the same x10 with me. I guess Ill have to try your suggestion.
SmG67 said:
The Experia Flasher is not for the 2010 devices i think, so she may well have flashed the wrong firmware. SUS doesn't need to detect the phone, if you choose update and it can't recognise the phone it offers a repair option, this lets you choose the model yourself, it will download the proper firmware and all you have to do is connect your phone in flash-mode (ie hold the back-button while you plug in the usb-cable).
But she may well have bricked it properly and in that case, JTagging it is the only option to get it back up and working.
Click to expand...
Click to collapse
It doesnt help because when Im in the part where it says, press the back button while inserting the usb, the phone cannot be detected and so the update cannot continue.
Hi there!
This thread is my last hope, so please dont let me down folks...:cyclops:
The story short - one sunny morning i turned on my HTC Nexus One and it got stuck with te X on the screen for about 15 minutes, non of the buttons responded, so i did the first thing that came in my mind - i pulled out the battery. After inserting the battery the phone went full brick, i mean literally, no reaction on anything, even conected to the wall charger, there is no sign of life, no charging LED, nothing. Connected to the PC, it says USB device not recognised.
I dont think this is a hardware proble, the phone workwd fine until this interrupted power on. Phone runned on stock Androud, i have not played aroun with it - no bootloader unlock, no rooting.
I searched the internet for a solution, tried a lot of button combinations like in this thread:
http://forum.xda-developers.com/showthread.php?t=1069032
but still no luck, i cannot restore or flash it while my PC does not recognise the phone.
Found some info about those Usb Jig things, but they work only on Samsung phones, so, is there a way to force the phone to go in recovery mode, or give any sign of life so i can try to recover it or flash a diferent ROM?
The warranty has ended, so no hope there.
Hope there is a way out of this, and, sory for my bad english. :good:
Veesais said:
Hi there!
This thread is my last hope, so please dont let me down folks...:cyclops:
The story short - one sunny morning i turned on my HTC Nexus One and it got stuck with te X on the screen for about 15 minutes, non of the buttons responded, so i did the first thing that came in my mind - i pulled out the battery. After inserting the battery the phone went full brick, i mean literally, no reaction on anything, even conected to the wall charger, there is no sign of life, no charging LED, nothing. Connected to the PC, it says USB device not recognised.
I dont think this is a hardware proble, the phone workwd fine until this interrupted power on. Phone runned on stock Androud, i have not played aroun with it - no bootloader unlock, no rooting.
I searched the internet for a solution, tried a lot of button combinations like in this thread:
http://forum.xda-developers.com/showthread.php?t=1069032
but still no luck, i cannot restore or flash it while my PC does not recognise the phone.
Found some info about those Usb Jig things, but they work only on Samsung phones, so, is there a way to force the phone to go in recovery mode, or give any sign of life so i can try to recover it or flash a diferent ROM?
The warranty has ended, so no hope there.
Hope there is a way out of this, and, sory for my bad english. :good:
Click to expand...
Click to collapse
Well no, bricked is a term used when you are rooted and flash a bad rom,kernel,etc. You have no root, so you cannot be "bricked". Just a software failure, you cannot flash another rom because, again, you have no root or custom recovery. Your best bet is trying to send it back to your carrier and get it replaced
ParanoidKang said:
Well no, bricked is a term used when you are rooted and flash a bad rom,kernel,etc. You have no root, so you cannot be "bricked". Just a software failure, you cannot flash another rom because, again, you have no root or custom recovery. Your best bet is trying to send it back to your carrier and get it replaced
Click to expand...
Click to collapse
The warranty time is out, so there is no help from the carrier, unless for cash...
But there must be a way to bring it back to life.
Veesais said:
The warranty time is out, so there is no help from the carrier, unless for cash...
But there must be a way to bring it back to life.
Click to expand...
Click to collapse
Now the screen may not show, but try booting into fastboot mode by press and hold the Trackball+Power buttons together.
I'm not sure about the nexus one, but newer nexus devices have factory images, supplied by Google. If they exist for the nexus one, you should be able to save your device by flashing them through fastboot. That is if the images exist and you can get to fastboot.
Sent from my Nexus 4 using XDA Premium 4 mobile app
NOTHING
You can charge it without it being turned on I assume.
That should get you to 80 or more % so you can repair it with the companion software
glovesave said:
You can charge it without it being turned on I assume.
That should get you to 80 or more % so you can repair it with the companion software
Click to expand...
Click to collapse
Sorry, I do not quite understand how to charge it without being turned on, once connected to the power it will automatically start and restart infinitely, is there any detailed operation method can tell me?
Can you both to recovery and charge there?
Standard way per internet:
"
Recovery Mode SONY Xperia 1 III
At first hold down the Power key for a few seconds to switch off SONY Xperia 1 III.
After that hold down Volume Down and Power button for a couple of seconds.
If the SONY logo appears release the Power key."
In your case see if you can match step 2 up with the phone rebooting if that makes sense.
I would try that with power cable in first, then without the cable in, if the other doesn't work. Then put power in while in recovery mode.
Hope that works
IKIZZN said:
Please help me, my Hong Kong version 512 grey xperia 1 iii arrived on the first day, I tried to brick the Taiwan version of the firmware, and now I am prompted as shown in the picture, and reboot infinitely. I want to use xperia companion to fix it, but it says it needs more than 80% battery so it keeps failing. I'd like to know how to charge it in case of infinite reboot. I'm really afraid of using newflasher as a white guy, I can't understand what partitioning or whatever I said in other posts, adb always prompts waiting for device, and the driver is always a yellow exclamation mark. Please have no big brother to help me! I am more anxious to use the phone also stall on such a thing!
View attachment 5378119
Click to expand...
Click to collapse
Were you able to fix your phone? I have the same problem, I unlocked my phone and rooted it but then decided to relock my phone. Silly me i didn't charge my phone before using the Sony companion to repair it now it just keeps rebooting when I tried to charge it. Anyone has a solution to this is very much appreciated.
I had the same problem and brought it back to the store. It seemed that there was a problem with the fingerprint button, which kept the phone in restart boot. The only thing you need to do is to bring it back, have them/Sony check the phone. Ultimately you will get a New phone. I did. Yesterday. Hope it does not occur again.
I have same problem please help us. I have XQ-BC72 HK and I used New Flasher to flash RU or TW and corrupted. And I tried to fix with Xperia Companion but I have no charge.
Bro I solve the problem and phone is running now... Contact me...
THREAD LOCKED
First post and thread title removed by OP.
Regards,
shadowstep
Forum Moderator