Hi guys so i flashed cm 10 and the bootloader all was fine switched internal for eternal storage still every thing was fine tried restoring some apps it stuck at 92% for 3 hour so i rebooted phone, then gave back to wife however dont think she liked it and she told me she had restored back to factory and when her phone rebooted nothing happened i have tried hooking it up to flash tools but it wont find my phone i have tried logging in to fastboot via cmd prompt just says waiting for device no lights come on totally dead me thinks but looking for an expert to tell me hopefully different
but really think its dead it also as unlocked bootloader please help TIA
Oh it might be hard bricked.. Does it vibrate on pressing power button. Flashmode doesn't start? (green led)
And how did your wife return to stock? Flash ftf file?
Also how does device manager show the connected phone?
Sent from my ST27i
no it doesnt vibrate and no lights all she did was it was on cm10 she went into settings and restore to factory then this happened pc makes the noise when plug it in but nothing happens and device manager wont pick it up, dont even thinki can take to shop or send to sony as it has unlocked bootloader can this phone be fixed to u no bud or will it be cheaper to just buy new 1 as i honestly think this 6 week old phone is dead it doesnt do anything m8
Download stock ftf
Open flashtool first
Press power off +vol down button and connect usb quickly if flashtool recognizes
Then flash the stock ftf and research before flashing anything
And give me the built number of cm10 buicd
noob and learning
hit thanks if I helped you
it was fxp 211 and fashtool doesnt help m8 as it wont pick my phone up
Sounds hard bricked.. Try flashtool on another pc to rule out driver issue. If flashtool can't fix it, it's gotta go back to Sony.
Also try plugging it to charger for a few hrs, battery may be drained..
Sent from my ST27i
from what i have read bud sony will charge me to fix it as i have unlocked bootloader will it be cheaper to buy new phone or will it be best to send back TIA
flash again with flashtool
ratboy666 said:
from what i have read bud sony will charge me to fix it as i have unlocked bootloader will it be cheaper to buy new phone or will it be best to send back TIA
Click to expand...
Click to collapse
You will have to act lame, and not mention anything about rooting or unlock bootloader.. Tell it died under normal circumstances, like dead battery, or something weird like crashed, and on reboot it never started. Depending on how you sell it, and your country, them may not check BL (or they may not be able to) so give it a shot and be creative
And before repairing and charging you anything, they have to inform you of your warranty status, so you can decide then which is cheaper.
Sent from my ST27i
awesome thanks m8 i will give it a try as i got nothing to lose bud kind of hoping it needs a new phone so they dont find out but thanks for help m8
same thing happened to me.just take it to any repair center.
They check via IMEI if the bootloader is unlocked. If it is they don't touch it and they tell you to buy a new one. My tipo was dead almost two months ago. If it is possible use another battery and try to install stock firmware via flashtool. My brother has Neo V which use the same battery with tipo and my device became alive.
saitri said:
flash again with flashtool
Click to expand...
Click to collapse
read above bud tried already no respond m8 to anything i try
tassosmer said:
They check via IMEI if the bootloader is unlocked. If it is they don't touch it and they tell you to buy a new one. My tipo was dead almost two months ago. If it is possible use another battery and try to install stock firmware via flashtool. My brother has Neo V which use the same battery with tipo and my device became alive.
Click to expand...
Click to collapse
tried another battery phone is completly dead shipped to sony guess they wont fix i=as it has unlocked bootloader sure i will get email in couple days saying this but have to be worth a try i wont pay them nothing just to get my phone back so if they want money just to send my phone back they can keep it i will buy another maybe not a sony tho and then read alot more i cant believe this was caused by doing a factory reset , thanks to all who tried helping guys but phone will not do anything even leaving on charge for 8 hours did nothing
ratboy666 said:
Hi guys so i flashed cm 10 and the bootloader all was fine switched internal for eternal storage still every thing was fine tried restoring some apps it stuck at 92% for 3 hour so i rebooted phone, then gave back to wife however dont think she liked it and she told me she had restored back to factory and when her phone rebooted nothing happened i have tried hooking it up to flash tools but it wont find my phone i have tried logging in to fastboot via cmd prompt just says waiting for device no lights come on totally dead me thinks but looking for an expert to tell me hopefully different
but really think its dead it also as unlocked bootloader please help TIA
Click to expand...
Click to collapse
Well don't judge hard brick so easily
It can be due to no battery charge in phone
It happened to my friend and I thought it is hard bricked
Well but I inserted my battery and he was able to flash it
Try to charge battery with car charger etc....:laugh:
ratboy666 said:
read above bud tried already no respond m8 to anything i try
tried another battery phone is completly dead shipped to sony guess they wont fix i=as it has unlocked bootloader sure i will get email in couple days saying this but have to be worth a try i wont pay them nothing just to get my phone back so if they want money just to send my phone back they can keep it i will buy another maybe not a sony tho and then read alot more i cant believe this was caused by doing a factory reset , thanks to all who tried helping guys but phone will not do anything even leaving on charge for 8 hours did nothing
Click to expand...
Click to collapse
i had bought it from vodafone for 127 euros. One day vodafone told me that sony will not repair my phone as the bootloader is unlocked and i have illegal firmware and that it replaces my tipo with a new one for 153 euros. I said no of course and a few days later sony sent my bricked tipo back without charge.
help me pls urgent
hi frnds here i am with new problem can anyone helpme pls i rooted my xperia tipo successfully but i big mistake is done by me at installation that is i execute the instruction fastboot flasboot boot.img successfully but unfortunately i forgot about fastboot reboot . i disconnect my mobile and restart it from that moment it is in off state a red led is blinking on while i want to bring it in recoverymode (by holdingvolume+ and connecting usb) so pls help me can i correct my mistake or i have to visit sony service pls help me by your suggestion as soon as possible
Y u guys unlocking boot loader without knowing abt it completely....
I think that 92% only recovered Is the problem...
Did u back up the system files in that 92% back up and tried to restore.....,??????
If u backed up the system files in that, I ll tell its coz u tried to overwrite the moded system files with stock system files... And wen ur wife used reset to factory, the stock files is mixed with moded files, so phone is dead.....
So tell me sir, did u back up system files?????
Sent from my ST21i using xda app-developers app
yes sir i have clockwork backup if that helps i got like 12 backups but wont help cause no way to get them on phone the phone wont connect to pc or anything living in hope that sony will repair lol
i think i have hard bricked my Sony Xperia Tipo.. Just after installing CM10 FXP 212 i tried to reboot but it would not boot. It is totally dead. After i take out the battery and put it back it vibrates but can boot up...
Is there any way to fix it??
Please help......
volumedown, hold it while pluggin the USB, and flash a stock .ftf via flashtool.
Related
update to 4.1 Jellybean .i used servarl day.one day,i shutdown the phone,then power on the phone,but i can't power the phone.i use the method "ubuntu UnBrickableResurrectorR40",but it's not useful.
in tencent qq group(qq group id:203219460),there are three people who encountered the same problem. xdaer,who can help me?please help,help,help!!!!
bsqsbylt said:
update to 4.1 Jellybean .i used servarl day.one day,i shutdown the phone,then power on the phone,but i can't power the phone.i use the method "ubuntu UnBrickableResurrectorR40",but it's not useful.
in tencent qq group(qq group id:203219460),there are three people who encountered the same problem. xdaer,who can help me?please help,help,help!!!!
Click to expand...
Click to collapse
help me out！
So you cannot even get into the bootloader?
I'm having the same problem...No bootloader...Nothing :crying:
Nexus S GT-I9020T Bricked
similar problem here. i took the batery out while the phone was booting and cant switch it on now.cant get in to fastboot mode (power + vol up).
i tried AdamOutler's UnBrickableResurrectorR40 tool (http://forum.xda-developers.com/show....php?t=1397393). it didnt detect my phone, so i made the hardware mod recomended by AdamOutler ( http://forum.xda-developers.com/show....php?t=1566475). Now it detects the phone and it is able to load the modified SBL.But the phone still stays dead.
why dont u guys try the tool and let us know how it goes... cheers
kwibis said:
So you cannot even get into the bootloader?
Click to expand...
Click to collapse
yes，any mod can't in.
similar problem
My battery fell out while my phone was booting. (Bought a spare battery and it didn't make great contact and the phone turned on and then lost contact with the battery while it was booting.)
I've tried multiple battery pulls, charging both batteries, plugging it in and unplugging it, different chargers... Nothing works.
I bought this phone used without a warranty so I'm screwed for just taking it back to any store to get it fixed and I can't afford to buy a new phone. :/
Gonna try that Ubuntu fix when I get home but as for now I have no idea what I'm going to do to fix this phone... >_<
While I was flashing a ROM (Synergy1.3), my wife decided to move my phone to another table. When i looked at it a few minutes later,the screen was blank. Now it wont turn on at all. I had used that particular ROM before without any problems. My battery was at 90% when i started to flash. I have a terrible feeling i am bricked. Any ideas?
goralla said:
While I was flashing a ROM (Synergy1.3), my wife decided to move my phone to another table. When i looked at it a few minutes later,the screen was blank. Now it wont turn on at all. I had used that particular ROM before without any problems. My battery was at 90% when i started to flash. I have a terrible feeling i am bricked. Any ideas?
Click to expand...
Click to collapse
You take out the battery..then try it?
Dominazn said:
You take out the battery..then try it?
Click to expand...
Click to collapse
yes,also tried charging it from wall charger ans USB. I get this error when plugging into USB (QHSUSB_DLOAD)
It's hard to brick a phone. Worst case, boot into download mode and Odin up the stock image.
If you can't access Download mode, you've most likely bricked as any research I've done points to it. If you've got insurance you can pay the premium, or send it to one of the JTAG services for repair (such as MobileTechVideos).
Just don't leave or touch the phone next time when you're flashing!
With my case it's hard to hit the buttons for recovery and download. I created across to get to them. Not what you're wanting to here. But here's a tip: if you can get adb to recognize your phone but can't use buttons to get into download mode you can "adb shell" and then "reboot download". That will cause the phone to boot download/Odin mode. Hopefully that will work and you can flash back to stock.
Sent from my SCH-I535 using xda app-developers app
The phone will not power up in any way at all. I am in the 5th stage of the grieving process. Back to my Tbolt and hope Samsung honors the warranty.
goralla said:
The phone will not power up in any way at all. I am in the 5th stage of the grieving process. Back to my Tbolt and hope Samsung honors the warranty.
Click to expand...
Click to collapse
They won't honor it with a rooted phone or flash count pass 0
Sent from my Verizon Samsung Galaxy S3 4G LTE
If you cant get to download mode or get adb to recognize when properly set up you do probably have a brick. What's happening to you with the warning happened to my friend on Sprint while accidentally flashing a ROM for a different phone. What he had to do was send it in to MobileTechVideos and got it repaired for around 60$. Samsung/Verizon wont likely fix them under warranty.
My only question is if you indeed were flashing synergy, how did a system ROM brick a device. o_0 And hell even if it was another phones ROM wouldn't our locked bootloader deny overwriting?
enomele said:
If you cant get to download mode or get adb to recognize when properly set up you do probably have a brick. What's happening to you with the warning happened to my friend on Sprint while accidentally flashing a ROM for a different phone. What he had to do was send it in to MobileTechVideos and got it repaired for around 60$. Samsung/Verizon wont likely fix them under warranty.
My only question is if you indeed were flashing synergy, how did a system ROM brick a device. o_0 And hell even if it was another phones ROM wouldn't our locked bootloader deny overwriting?
Click to expand...
Click to collapse
I also accidentally flashed a rom for a different phone and am considering sending it to MobileTechVideos. Your friend had good success with them fixing his phone?
-Purk
I think this might also work for you, if the battery charging icon comes on while your charging it then this might work. When you have it connected and the charging icon comes on put it in download mode(do not unplug it until your in download mode). Then use odin to flash it back to stock. It happen to me ones and when i did this it work for me, so i don't know if this will work for you. (Sorry for my grammar)
Hello guys I was wondering if anyone can help me with this issue. But first things first the details!
I have kitkat AOSPA 4.0 Beta-6 installed on my xl with thunderzap kernel 4.1 r2 with internal storage fix. I have been running this ROM and kernel on my phone for about 3 to 4 days max.
Now when the issue happened was this morning. The alarm went off my phone and was working fine. I then noticed the battery was at 20% so i decided to switch off the phone and plug it into the mains. I then went out for about 2-3hrs by the time I got back I noticed that the display did not light up with the charging logo when I pressed the power button. I tried to switch it on but nothing happens what so ever.
Things that I have already tried.
-Removed battery for 10mins
-Leave it on charge again for 3hrs
-Tried to enter into flash mode and fastboot.
I have connected the phone to the pc without the battery and the led just lights up green very briefly. My pc detects it as a Qualcomm HS-USB QDLoader 9008 (COM4).
I have run out of ideas and any help you provide will be very appreciated.
HatchetEgg said:
Hello guys I was wondering if anyone can help me with this issue. But first things first the details!
I have kitkat AOSPA 4.0 Beta-6 installed on my xl with thunderzap kernel 4.1 r2 with internal storage fix. I have been running this ROM and kernel on my phone for about 3 to 4 days max.
Now when the issue happened was this morning. The alarm went off my phone and was working fine. I then noticed the battery was at 20% so i decided to switch off the phone and plug it into the mains. I then went out for about 2-3hrs by the time I got back I noticed that the display did not light up with the charging logo when I pressed the power button. I tried to switch it on but nothing happens what so ever.
Things that I have already tried.
-Removed battery for 10mins
-Leave it on charge again for 3hrs
-Tried to enter into flash mode and fastboot.
I have connected the phone to the pc without the battery and the led just lights up green very briefly. My pc detects it as a Qualcomm HS-USB QDLoader 9008 (COM4).
I have run out of ideas and any help you provide will be very appreciated.
Click to expand...
Click to collapse
this happens to me before month (ill send it to RMA and got new motherboard) ive got accidental pc poweroff while flashing
at this moment theres no other way how to revive this state bcz nobody have proper data to program internal mlc via QPST and without this one it means you have dead motherboard, you need to send it to RMA
edit: before you shut off phone you maybe do something wrong, like formating whole internal memory or switching internal to external or something like that ... phone is now in download mode for qpst sw, so it looks like you have no bootloader so phone doesnt know how to boot to os
Flashing_Expert said:
this happens to me before month (ill send it to RMA and got new motherboard) ive got accidental pc poweroff while flashing
at this moment there no other way how to revive this state bcz nobody have proper data to program internal mlc via QPST and without this one it means you have dead motherboard, you need to send it to RMA
Click to expand...
Click to collapse
Thanks for your help. The strange thing is this is my 3rd xperia l because of the same issue it only seems to happen only when flashing another rom other than stock. When I had the same issue they told me there was nothing wrong with it.
I had a Samsung galaxy ace before Major difference in spec I know but I had never had any issues flashing a new rom.
Would they actually repair the phone? as it is rooted and unlocked bootloader?
Propably first ''Sudden Death'' noticed on Xperia L.. That's not funny, Sony.
HatchetEgg said:
Thanks for your help. The strange thing is this is my 3rd xperia l because of the same issue it only seems to happen only when flashing another rom other than stock. When I had the same issue they told me there was nothing wrong with it.
I had a Samsung galaxy ace before Major difference in spec I know but I had never had any issues flashing a new rom.
Would they actually repair the phone? as it is rooted and unlocked bootloader?
Click to expand...
Click to collapse
if mobo is dead they even cant read internal memory, so be calm they probably replace mobo to new one without any asking...
and this is not bcz flashing this is only bcz human factor...
Flashing_Expert said:
if mobo is dead they even cant read internal memory, so be calm they probably replace mobo to new one without any asking...
and this is not bcz flashing this is only bcz human factor...
Click to expand...
Click to collapse
Interesting well it wont be long until I have a new contract anyway. Hopefully I will get a new one. I just wont use a custom rom ever again.
Thanks for your support on this matter.
EDIT: Is there anyway to get the bootloader to work again if thats the reason to why it will not boot.
On the rom that I used for it. It had emulated the internal storage just to get the 4g back.
Try to flash a stock ftf, losing your data (I'm sorry) if you can enter flashmode. Then try to not install the Kernel, possibly the problem is there.
Luck!
Sent from my C2105 using xda app-developers app
HatchetEgg said:
Interesting well it wont be long until I have a new contract anyway. Hopefully I will get a new one. I just wont use a custom rom ever again.
Thanks for your support on this matter.
EDIT: Is there anyway to get the bootloader to work again if thats the reason to why it will not boot.
On the rom that I used for it. It had emulated the internal storage just to get the 4g back.
Click to expand...
Click to collapse
no theres no other way to get internal memory back, its gone, its erased (whole 8gb memory, even partitions or bootloader is erased) or memory chips are broken nothing more or less
theres a sw called QPST from qualcomm for programming internal memory (mainly for right partitions formating inside mmc and basic BL programming) without it theres no other option than get your xl to RMA and mobo change
---------- Post added at 10:19 PM ---------- Previous post was at 10:16 PM ----------
ArnauGonzalez98 said:
Try to flash a stock ftf, losing your data (I'm sorry) if you can enter flashmode. Then try to not install the Kernel, possibly the problem is there.
Luck!
Sent from my C2105 using xda app-developers app
Click to expand...
Click to collapse
OP said that in first comment that his xl is dead without flashmode/fastboot mode, and if it shows in pc after connection qhusb dload driver memory is broken or formated, mobo=dead
kernel surely cant broke your xl, only playing with memory like switch internal/external
Sorry Man, your phone is now at the heavens of mobile phones.
Buy another XL!
Sent from my C2105 using xda app-developers app
Hello, my problem is that exactly yesterday i turned my phone off
wanted to turn it on ,but it simply doesn't work
can't get it to recovery or the pc communication mode (i guess it's locked anyway, i don't know).
Thought it was battery, charged it to 100%, nothing.
Literally anything would help me.
.kyon said:
Hello, my problem is that exactly yesterday i turned my phone off
wanted to turn it on ,but it simply doesn't work
can't get it to recovery or the pc communication mode (i guess it's locked anyway, i don't know).
Thought it was battery, charged it to 100%, nothing.
Literally anything would help me.
Click to expand...
Click to collapse
can't get it to recovery or the pc communication mode:same but i can see batery icon when i plug on charger but not charge device
It happened to me also the phone no longer loads so I dismantle them check the motherboard(its ok ) and manually charge the battery because it had the problem of 0 volt
If nothing works for you just flash it
Constant boot loop even after flashing rom
My sony e3 gets in boot loop every one or two day even when i try to flash the stock rom or lineage, nitrogen one.
So basically i have to flash any of the rom every now and then to keep it running. Can anyone please suggest me a solution or at least tell me why this happens??
Did you do a wipe before flashing?
Sent from my Xperia E3 d2202 with nougat
So someone gave me a bricked Sony experia z5, i believe that's what it is. When i plug in a charger the red light comes on but i cannot turn on the phone. i tried holding the power off button next to the sim slot for 10+ seconds but that didn't help either. I also tried holding the power on button with the volume down to no avail. I did some googling and found im not the only one with this issue. Altough advice was hard to find i managed to find a video about the same issue on a z3. As in the video i opened up the phone, reconnected all of the connectors. I left the battery connector out, then plugged it in and try to start it. Still didn't work.
I have never used a sony phone before and i have no idea what i should do next, i hope someone has advice for me
ok mate its probably hard bricked because your friend may have flashed the wrong rom for wrong phone oh well mistakes happened basically i have soft bricked my xperia many times easy to fix but i am not sure with hard brick try flashtool 64 and wipe everything if you can get the green flash if you cant there is not much more i can help you with bro
Quantumkk123 said:
ok mate its probably hard bricked because your friend may have flashed the wrong rom for wrong phone oh well mistakes happened basically i have soft bricked my xperia many times easy to fix but i am not sure with hard brick try flashtool 64 and wipe everything if you can get the green flash if you cant there is not much more i can help you with bro
Click to expand...
Click to collapse
i have tried using flashboot but it cannot detect my device. I honestly have no clue what happened to it. I read somewhere that it has some battery bug so i will leave it charging for a very long time. also its the experia m5, not the z5 i found out.
@marceltjeg then wrong forum mate go to that one you may have more people to help you out