Bricked my phone by flashing it with firmware in this link http://forum.xda-developers.com/showthread.php?t=2453921, now it wont go into flashmode or do anything infact any ideas how to revive it
baldevp said:
Bricked my phone by flashing it with firmware in this link http://forum.xda-developers.com/showthread.php?t=2453921, now it wont go into flashmode or do anything infact any ideas how to revive it
Click to expand...
Click to collapse
You are not alone.
The question is if you have warranty or not?
Because if yes, that play dump in Sony Service Center.
Otherwise you will need to open your device.
Solution is not ready yet, I am working on it.
I am waiting for new battery(I damaged mine), after that I will continue experiments.
Stay in touch in this tread, it's for Z1, but they have hell a lot of bricks.
vovanx500 said:
You are not alone.
The question is if you have warranty or not?
Because if yes, that play dump in Sony Service Center.
Otherwise you will need to open your device.
Solution is not ready yet, I am working on it.
I am waiting for new battery(I damaged mine), after that I will continue experiments.
Stay in touch in this tread, it's for Z1, but they have hell a lot of bricks.
Click to expand...
Click to collapse
its rooted do you expect warranty on that
baldevp said:
its rooted do you expect warranty on that
Click to expand...
Click to collapse
If you got a red blinking led or no led at all, then they will change a motherboard.
Even if you got unlocked bootloader.
Just go to Sony and tell then something like " The Sony software asked for update,and after that my device died"
Remember not to use words such "Root" or "firmware"
Just play noob.
Just make sure phone is completely dead
My situation is worse, my phone is from Singapore so, no warranty for me.
vovanx500 said:
If you got a red blinking led or no led at all, then they will change a motherboard.
Even if you got unlocked bootloader.
Just go to Sony and tell then something like " The Sony software asked for update,and after that my device died"
Remember not to use words such "Root" or "firmware"
Just play noob.
Just make sure phone is completely dead
My situation is worse, my phone is from Singapore so, no warranty for me.
Click to expand...
Click to collapse
thanks man a lie can surely save my day
baldevp said:
thanks man a lie can surely save my day
Click to expand...
Click to collapse
You are welcome.
You can always open your device, but then no warranty for sure.
vovanx500 said:
You are welcome.
You can always open your device, but then no warranty for sure.
Click to expand...
Click to collapse
ya why to void it
baldevp said:
Bricked my phone by flashing it with firmware in this link http://forum.xda-developers.com/showthread.php?t=2453921, now it wont go into flashmode or do anything infact any ideas how to revive it
Click to expand...
Click to collapse
Which ftf did you flash?
What parts of the ftf did you flash (or exclude)?
What exactly are the symptoms?
What was the battery state when you started the flash?
What firmware did you start on?
What dos the LED do when the phone is on charge?
Does the PC make any sound or say anything when the phone is connected?
What does flashtool say when the ultra is connected?
baldevp said:
ya why to void it
Click to expand...
Click to collapse
I got your PM... I'm hoping that you were using the latest version of Flashtool. As that could be the bugger!
Using the previous version has been bricking devices flashing .290. Not sure about .132 but im betting it does too...
Check if you had the latest version.... if not then your are currently screwed!
If it was the latest, then I'm sure it can be resolved.
Note: opening your device rips some adhesive tape inside it. So then technicians know that you've been inside your device... and hence warranty void!
hamdogg said:
Using the previous version has been bricking devices flashing .290. Not sure about .132 but im betting it does too...
Click to expand...
Click to collapse
This is mostly for @hamdogg regarding the above
One thing I have noticed and has been mentioned in the Z1 forum is that flashing .290 ftf often dropped the battery by huge amounts, I have seen 40% or more, and then very fast charging - looks like calibration is right out of whack.
Yesterday when flashing to play with root (I flashed .136 mayby 6 - 8 or more times) I never saw a battery drop/jump outside of the few % I would expect from a full flash.
This leads me to believe that there was something very wrong in .290
blueether said:
This is mostly for @hamdogg regarding the above
One thing I have noticed and has been mentioned in the Z1 forum is that flashing .290 ftf often dropped the battery by huge amounts, I have seen 40% or more, and then very fast charging - looks like calibration is right out of whack.
Yesterday when flashing to play with root (I flashed .136 mayby 6 - 8 or more times) I never saw a battery drop/jump outside of the few % I would expect from a full flash.
This leads me to believe that there was something very wrong in .290
Click to expand...
Click to collapse
Yeah good points. When piecing together the ROM tree for doggROM (still not 100%, but its up; need to work on the kernel image) I noticed quite a few added lib files. There are a few changes that we probably wont see for a while.
I also flashed dogg and stock FTF probably about 10 times yesterday. went from 60-30-odd %... not bad for constant use for 3 hours and then flashing different ROM's..
blueether said:
This is mostly for @hamdogg regarding the above
One thing I have noticed and has been mentioned in the Z1 forum is that flashing .290 ftf often dropped the battery by huge amounts, I have seen 40% or more, and then very fast charging - looks like calibration is right out of whack.
Yesterday when flashing to play with root (I flashed .136 mayby 6 - 8 or more times) I never saw a battery drop/jump outside of the few % I would expect from a full flash.
This leads me to believe that there was something very wrong in .290
Click to expand...
Click to collapse
Same thing happened to me yesterday. I continuously flashed or 2-3 hours first flashed .532 to gain root ,then flashed.290 couple of times, and then.136 .
Flashing .290 always lead to drop in % around 40.But after flashing .532 over .290 lead to battery percentage rise.Also flashing .136 or .532 had percentage dropped by 5-6 only.
Now am on .136 and charged it and charging was way faster than before.
Wanted to know did it anyhow damaged the battery considering the faster charging?
Or it will be normal after a while?
baldevp said:
Bricked my phone by flashing it with firmware in this link http://forum.xda-developers.com/showthread.php?t=2453921, now it wont go into flashmode or do anything infact any ideas how to revive it
Click to expand...
Click to collapse
What firmware were you updating from?
Did you use latest Flashtool?
Most importantly, did you flash the 136 kernel but not the 136 bootbundle?
Im asking because if answer yes to the last question, the brick bug hasn't been fixed.
blueether said:
Which ftf did you flash?
What parts of the ftf did you flash (or exclude)?
What exactly are the symptoms?
What was the battery state when you started the flash?
What firmware did you start on?
What dos the LED do when the phone is on charge?
Does the PC make any sound or say anything when the phone is connected?
What does flashtool say when the ultra is connected?
Click to expand...
Click to collapse
it does not connect man, its ****ed up, i cant connect it in any mode or start it, it goes goo-gaa some time when connected to lappy by connecting-disconnecting continously but many times do not connect i flashed the generic firmware, 1 st link on the link given originally
baldevp said:
it does not connect man, its ****ed up, i cant connect it in any mode or start it, it goes goo-gaa some time when connected to lappy by connecting-disconnecting continously but many times do not connect i flashed the generic firmware, 1 st link on the link given originally
Click to expand...
Click to collapse
We want to know exactly the firmware you flashed, just saying the first link is hard for us, as we dont know the model phone you have etc
anyway did you just leave it as all defaults when you flashed?
and what about the other questions?
blueether said:
We want to know exactly the firmware you flashed, just saying the first link is hard for us, as we dont know the model phone you have etc
anyway did you just leave it as all defaults when you flashed?
and what about the other questions?
Click to expand...
Click to collapse
battery was way above 80%
I didn't exclude any part
the pc connects and disconnect and many times doesn't even detect it
flashtool doesn't detect it
flashtool version 0.9.11.0
I used the earlier 14.1.B.1.526 GENERIC Taiwan http://forum.xda-developers.com/showthread.php?t=2439438
baldevp said:
battery was way above 80%
I didn't exclude any part
the pc connects and disconnect and many times doesn't even detect it
flashtool doesn't detect it
flashtool version 0.9.11.0
I used the earlier 14.1.B.1.526 GENERIC Taiwan http://forum.xda-developers.com/showthread.php?t=2439438
Click to expand...
Click to collapse
ok, that is a different link than in your first post, but atleast we know what you were flashing.
What firmware were you on before the flash?
I have a feeling the issue might be with the old version of flashtool. I have used that version before without issues, and also that FTF without issues.
I think it might be bricked, but there may still be hope.
Upgrade flashtool to at least 0.9.13.0
Reboot the computer
Reinstall drivers
If you hold the volume + and plug in the phone to the PC do you get any lights on the Ultra?
How about if you hold the volume - and plug in the phone to the PC doe the leds flash then go out?
do the above two while the new flashtool is running and post it's output if you can.
I'll be away fron a PC for most of the next 30+ hours but hopefully @hamdogg, @LordManhattan, @zeppelinrox will have some more hints
Oh it's likely due to the old Flashtool version.
9.13 was giving an error (at bootbundle phase) to one guy so he tried 9.11
Bricked it.
http://forum.xda-developers.com/showthread.php?t=2624641
9.11 and newest ftfs don't go well together but I don't know exactly why.
Does 9.11 not flash the bootbundle?
@Androxyde would have the best guess as to what goes wrong with 9.11
But my guess is that you ended up with a 526 bootbundle with the 136 kernel and if so, that means the brick bug hasn't been fixed.
zeppelinrox said:
Oh it's likely due to the old Flashtool version.
9.13 was giving an error (at bootbundle phase) to one guy so he tried 9.11
Bricked it.
http://forum.xda-developers.com/showthread.php?t=2624641
9.11 and newest ftfs don't go well together but I don't know exactly why.
Does 9.11 not flash the bootbundle?
@Androxyde would have the best guess as to what goes wrong with 9.11
But my guess is that you ended up with a 526 bootbundle with the 136 kernel and if so, that means the brick bug hasn't been fixed.
Click to expand...
Click to collapse
so what do i do now, will they accept it at service centre if i play noob
Yep they will.
It got bricked while updating to latest Sony release.
Just get an RMA from Sony support.
First they'll give you instructions on how to reset the phone with PCC.
Then you say "hello... I can't get into flash mode..."
Need an RMA and BTW, there's over a hundred reported bricks plus god knows how many more
Related
I tried to downgrade to 1.6 and now my phone wont turn on.
It will vibrate and the led will flash green? once during this vibrate but nothing more...
I cant get the thing into boot mode
Any help?
Z3X said:
I tried to downgrade to 1.6 and now my phone wont turn on.
It will vibrate and the led will flash red once during this vibrate but nothing more...
I cant get the thing into boot mode
Any help?
Click to expand...
Click to collapse
Try repairing using PC companion.
Welcome to this side of flashing issue. I just recovered from it this morning after hours of search and flashing. Jerpelea said that Kernel has gotten mixed up and try to take the battery our for a while and then put it in and try to go to boot, Flash earlier 1.6 ROM I did the R16 and it worked, I had a hardtime flashing with R26.
Nimche said:
Welcome to this side of flashing issue. I just recovered from it this morning after hours of search and flashing. Jerpelea said that Kernel has gotten mixed up and try to take the battery our for a while and then put it in and try to go to boot, Flash earlier 1.6 ROM I did the R16 and it worked, I had a hardtime flashing with R26.
Click to expand...
Click to collapse
Could you get into flash mode? I currently can not... I am bricking myself at the thought of my phone being bricked!!
I had the same problem a while ago and the only thing that worked was a firmware uploaded by jerpelea. Have a look at what I posted here http://forum.xda-developers.com/showpost.php?p=9206194&postcount=11
I had about the same problem with my phone a while back, I could still get it into flash mode if I was quick though. If you can get it into flash mode try and follow this tutorial on Youtube, it's a working way for downgrading from 2.1 to 1.6
ht tp:// w w w. youtube .c o m/watch?annotation_id=annotation_468774&v=K9qB8z6EjtY&feature=iv
If it bricks it will prolly brick after a few seconds, just pull out the battery and try again getting it into Flash Mode. Good luck
As stated on one of your other threads, until you've repaired your usb port posts like this are pointless.
I can angle it to get a connection. That's why I am continuing with this thread
But thanks
tie your x10 to a brick and throw it at a SE service centre.
Waste of a brick.
Hi there.... a similar thing happened to me. I have a UK T-mobile X10 which I had upgraded to nordic 2.1 and needed to downgrade back to 1.6 because I was getting a warranty exchange the next day.
I used the CDA method to change my phone cda back to uk t-mobile and the damn thing wouldnt downgrade via seus. Then I tried flashing to R2BA26 which bricked my fone...green light would come on and the damn thng would just vibrate!!!
I then flashed it with 2.1 Global generic from jeprelea's thread and everything is ok now!
XperiaX10iUser said:
As stated on one of your other threads, until you've repaired your usb port posts like this are pointless.
Click to expand...
Click to collapse
@Z3X, you've started 3 threads on this same topic, here, here and here.
Not
Hi all...
I saw this thread already on other forums, but there was not enough detail to explain the trouble, so this topic.
I am affraid there is a trouble on some devices when you update to 2.3.4 (GENERIC GLOBAL) then downgrade to 2.3.2 (GENERIC GLOBAL) with the reason of ROOT them, battery looks dead, but is not.
I saw on the forum in two different devices already, and yesterday it happened to me as well.
So I tell you what I've done, and I really hope there will be a solution.
- my phone (MT15i) shown me a message, that there is a new software available. I wanted to try how is that, so I made a system backup, relocked the bootloader and then I updated via SEUS. Everything was fine, with it, except that little problem, that I wanted my baby to be rooted.
- downgraded to 2.3.2 (GENERIC GLOBAL) via SE Flashtool 2.9.1, to complete the GingerBreak treathment (I've done this due to the locked bootloader)
- GingerBreak has been successfuly completed, phone restarted, battery were on 0%, I knew this can be normal, so I switched off, removed the battery for 1 min and restarted.
- And the nightmare began: THE BATTERY STAYS ON 0% and the phone goes off. If I plug the device to the mains, stays on, looks like is charging, but it does not.
I've tryied other battery same issue. I tried my batteries in other NEO, the were perfectly fine.
Funy is, I unlocked the bootloader again, and I can do any operation with my phone like such a ClockWork Recovery or flashing it, but I can not start the ANDROID O/S a without mains.
Please guys help me, and those who have the same experience with Arc/Neo/X10.
Many many thanks.
Remove battery, and put it back after 10 minutes.
I have tried even for two hours. Nothing changed, same issue, but thank you anyway..
Also "battery calibration etc battery stats wipe?
Yes my friend. All of these things I tried. Even reflashed sytem and boot images with fastboot (I guess this has nothing to do with bootloader, but I gave a try)... No changes..
broken bootloader, search this forum...
Enough information is on these forums about rooting without needing to relock the bootloader, like RootXperia method.
That very day there was not solution yet for the latest S/W update about rooting it. But I already tried many solution I can find here, but there is no luck.
Your problem, but your spreading false information. Rooting method has been available before 2.3.3 and is same for all FWs
No matter which FW you have anyone can root if they have unlocked bootloader, just get RootXperia.zip and install via recoveryNeo.img
Search
Yeah, the thing is, I wanted to relock my bootloader, and doing the OTA update. From 2.3.2 to 2.3.4. Please read what I wrote again. And that time I did not found anything about rooting the 2.3.4.
Cheers
Raoa said:
No matter which FW you have anyone can root if they have unlocked bootloader, just get RootXperia.zip and install via recoveryNeo.img
Search
Click to expand...
Click to collapse
I's it true?
Sent from my MT15i using Tapatalk
battery 0%
taaviu said:
I's it true?
Sent from my MT15i using Tapatalk
Click to expand...
Click to collapse
Yeah i've rooted all my FWs with RootXperia.zip
OTA is if you have locked bootloader, the whole method of going back to 2.3.2 is to not unlock bootloader and get root. To go through that with already unlocked bootloader is like going around when you could go straight.
The reports of, oh wait... this is not the first time OTA bricks phones. Wasn't it with 2.3.3 Arc update as well. So why do people fall to same trap?
Really there's enough relevant information on Arc forum, read up before doing something you don't need to do. It's a phone so thrashing around with flashing in any random way will end with bricked phones. It's your fault for not reading up and thinking well. SE might do something stupid with all these people bricking their phones in ways and for a reason they should not.... for customer protection. That would suck for us all.
Raoa said:
Yeah i've rooted all my FWs with RootXperia.zip
OTA is if you have locked bootloader, the whole method of going back to 2.3.2 is to not unlock bootloader and get root. To go through that with already unlocked bootloader is like going around when you could go straight.
The reports of, oh wait... this is not the first time OTA bricks phones. Wasn't it with 2.3.3 Arc update as well. So why do people fall to same trap?
Really there's enough relevant information on Arc forum, read up before doing something you don't need to do. It's a phone so thrashing around with flashing in any random way will end with bricked phones. It's your fault for not reading up and thinking well. SE might do something stupid with all these people bricking their phones in ways and for a reason they should not.... for customer protection. That would suck for us all.
Click to expand...
Click to collapse
What can we do?
I have a unlock bootlander.
Scroll down this forum and you'll see http://forum.xda-developers.com/showthread.php?t=1254409 Get a new battery or connect USB wires to - and + battery connectors and try it or send it to repairs.
Unless any dev finds yet another method to unbrick this new batch of phones then nothing else can be done.
Raoa said:
broken bootloader, search this forum...
Enough information is on these forums about rooting without needing to relock the bootloader, like RootXperia method.
Click to expand...
Click to collapse
I can confirm is not bootloader problem
Maybe is something with trim area.
This can be fixed but if you have warranty is better to send it to SE
Anyway if someone want to try this method to repair the trim area please contact me by PM.
Also anyone with working locked or unlocked NEO I need some trim area backups to acn repair others phones.
Please if you want to help send me a PM, the backup process is as easy as connect in flashtool by pressing back key
Raoa said:
Scroll down this forum and you'll see http://forum.xda-developers.com/showthread.php?t=1254409 Get a new battery or connect USB wires to - and + battery connectors and try it or send it to repairs.
Unless any dev finds yet another method to unbrick this new batch of phones then nothing else can be done.
Click to expand...
Click to collapse
Rember this was my same problem Raoa,, you told me to reflash with a difernt ftf file,,, problem was fixed there and then,,,
Sent from my MZ604 using xda premium
I am not so certain it is the exact same situation, Kormatoes. IF it's not a bootloader problem then I don't know what it is.
IF this would be fixed as easily as flashing a full working FW... well worth a try, nonetheless.
It is not a randomly flashing around and I DO WANTED my bootloader to be relocked and not open it again.. I used to flash my phone without any problem. I never had any problem repair anything. Since SonyEricsson and then Xperia exists, I know what to do with them if they are sick. I had enough experience, and I know you can find solutions on the forum, this is why you can see that from my posting history, that since I am member of XDA, never had stupid questions. I knew what to do when phone was bricked because of unlocked bootloader+over the air update. It is a simple accident that can happen to anyone. And here I asked for solution not for meaningless words, where some people try to show how brilliant and perfect they are. This is a development website, we are here to help for eachother or on those who needs help. So please stop to sue anyone, and help or please just do not reply for threads that you think is stupid, moderators/operators will deal with those. Just keep the rules of the website.
BTW, this MUST be a software problem, as I tested the battery, works perfectly in other devices, the phone is all okay about the 'elctrovise'
As I saw this on ARC's forum as well, this happened there in same way: Update to 2.3.4 then downgrade to any of the previous S/W versions, caused this. So I think this situation will incrase soon, this why I thing we need to find a solution as well. I normally working with Linux/ubuntu laptops. I had simular issue, but then was just the battery. Now... I dont know.
laceex said:
It is not a randomly flashing around and I DO WANTED my bootloader to be relocked and not open it again.. I used to flash my phone without any problem. I never had any problem repair anything. Since SonyEricsson and then Xperia exists, I know what to do with them if they are sick. I had enough experience, and I know you can find solutions on the forum, this is why you can see that from my posting history, that since I am member of XDA, never had stupid questions. I knew what to do when phone was bricked because of unlocked bootloader+over the air update. It is a simple accident that can happen to anyone. And here I asked for solution not for meaningless words, where some people try to show how brilliant and perfect they are. This is a development website, we are here to help for eachother or on those who needs help. So please stop to sue anyone, and help or please just do not reply for threads that you think is stupid, moderators/operators will deal with those. Just keep the rules of the website.
BTW, this MUST be a software problem, as I tested the battery, works perfectly in other devices, the phone is all okay about the 'elctrovise'
As I saw this on ARC's forum as well, this happened there in same way: Update to 2.3.4 then downgrade to any of the previous S/W versions, caused this. So I think this situation will incrase soon, this why I thing we need to find a solution as well. I normally working with Linux/ubuntu laptops. I had simular issue, but then was just the battery. Now... I dont know.
Click to expand...
Click to collapse
I have the ****ed same problem!!
batery 0%....
i tried flash to other versions and no get solution..
wipe batery stats none
.......
ANY IDEA?
anikill3010 said:
I have the ****ed same problem!!
batery 0%....
i tried flash to other versions and no get solution..
wipe batery stats none
.......
ANY IDEA?
Click to expand...
Click to collapse
I am affraid we still have to wait until more people will have the same problem. Right now there is no solution, only to leave on charger. Why not. A little retro. Just like a landline phone
Hi,
I bought my neo just a month ago and I got an indication for a new update available for my phone yesterday. I did a FOTA and my phone just stopped booting.When I press the power button all I get is a blinking green light, nothing on screen.
I had unlocked my neo a while ago.
I tried flashing it to MT15i_4.0.2.A.0.42_Global version. Still nothing.
I have tried SEUS and PC companion. My phone gets detected but they say i have a modified software and thats it.
Please help me, it hurts having lost a month old phone......
Thanks in advance
Well i got my phone up and running.....
For those who are still struggling check out the following link.....
http://forum.xda-developers.com/showthread.php?t=1324707
First of all , if your bootloader is unlocked-RELOCK IT.
After that , try flashing the stock firmware or use SEUS.
That's how i got my NEO V up and running.
No harm in trying the same method with NEO.
shaunshd said:
Well i got my phone up and running.....
For those who are still struggling check out the following link.....
http://forum.xda-developers.com/showthread.php?t=1324707
Click to expand...
Click to collapse
Yes, try this! It should work! If there are news just tell us!
When people go to bootloader unlock their phones, do they completely miss the prominent warning or what?
Some customers with unlocked boot loaders have experienced problems when they are accepting over the air upgrades (FOTA - Firmware upgrade Over The Air). For customers that have unlocked the boot loader, please do not accept any over the air upgrades. For additional information, check out the hints and tips from the community on the XDA forum.
http://unlockbootloader.sonyericsson.com/instructions
you are lucky you got your phone to reach 1month. mine didn't even reach 1 week!. i bricked when i tried to testpoint and ground to unlock bootloader. it never turned on. im not sure if i did the right procedure but the battery is in the phone and the phone is turned on when i do the TP ground thing to install the driver.. any idea?
SquallDNA said:
you are lucky you got your phone to reach 1month. mine didn't even reach 1 week!. i bricked when i tried to testpoint and ground to unlock bootloader. it never turned on. im not sure if i did the right procedure but the battery is in the phone and the phone is turned on when i do the TP ground thing to install the driver.. any idea?
Click to expand...
Click to collapse
Please tell me what instructions did you follow?
Where did you read that phone needs to be turned on or even with battery inserted!?
Easy answer. Try WotanServer i had this problem too but i solved it via Wotan.
u Can Flashed Again By This Program :
http://www.wotanserver.com/en/sony-ericsson/se/xperia-neo-mt15/unlock-tool/debranding-flash
Very Easy To Use ...
I think OP solved his problem, as he wrote it at second post.
nvm..............
Hey guys i've a problem with my x10
So one night i was playing with it than the other day the phone would start
so i thought yeah right might be the battery or something. i took it to my friends x10 it was with 87% charged so i exclude this
Than i tried to flash with flashtool a new kernel and i get stuck at 9% or 15% depending on the kernel i use.
With SEUS it starts to repair but it says. No new updates avaiable after a few moments.
Some information regarding my phone
Unlocked Bootloader
FXP KERNEL
MM TEAM MIUI V4
The phone vibrate but doesn't start or load the kernel.
What do i do?!
Srry for my bad english
Thx in advance
Usrle flashtool to reflash kernel or firmware.
already did but i get stuck at 9% or 15% flashing the kernel
I'm downloading a full generic rom x10a
having similar problem
Hi, I had similar problem as well
X10i running FXP CM7 suddenly just wont boot n charge after I turn off the phone
it wont boot after flashing anything (firm or kernel) except the official firm
now that I end up with a cap R bootloader but flashtool claim that bootloader is rooted
do I still keep the bootloader unlock?
i guess you have a locked bootloader since the original firmware is loading just fine even tho rooting has nothing to do with the bootloader it self. i'm only guessing.
I'm stuck at. Flashing Loader
I bricked my phone last week and it got stuck in a boot loop.
I downloaded the x10a generic Stock ROM and flashed it via Flashtool and it worked like a charm.
Hope this helps.
[XBOCT]™ said:
I bricked my phone last week and it got stuck in a boot loop.
I downloaded the x10a generic Stock ROM and flashed it via Flashtool and it worked like a charm.
Hope this helps.
Click to expand...
Click to collapse
But that way you weren't at a brick point.
You get brick when u get those 3 blink red LED and the phone doesn't do anything
By the fact that your phone were able to load the kernel. i guess
same problem repeat
Hi, just confirm that the bootloader remain unlock as long as the flashtool claim its ROOTED
had you try other than official 2.3.3 ftf?
because I just got the same unable to boot problem repeated again
this time cant get boot on even stock 2.3.3 firm
but I was able to boot up and charge on 2.1, then get root, recovery and kernel (w/o unlock bootloader again) and go straight to custom ROM with no problem
mooving said:
Hi, just confirm that the bootloader remain unlock as long as the flashtool claim its ROOTED
had you try other than official 2.3.3 ftf?
because I just got the same unable to boot problem repeated again
this time cant get boot on even stock 2.3.3 firm
but I was able to boot up and charge on 2.1, then get root, recovery and kernel (w/o unlock bootloader again) and go straight to custom ROM with no problem
Click to expand...
Click to collapse
i'm using
X10a_2.1update1_r2.1.A.0.435_Generic.ftf
And it get stuck at Flashing loader
Idk but i can "read" the kernel when i dump the propriets but i can't "right" when i try to flash something
Anyone?
guys?
you said your phone is "bricked"
I'm not sure if you know what that means.
If you say you've bricked your phone then no one can help you.
A brick is a brick. It doesn't matter if it weighs a few kgs or a few hundred grams. A brick can't receive phone calls.
And your phone isn't even a normal brick... You wrote that it's "really bricked"
Are you building a house anytime soon?
LJE said:
you said your phone is "bricked"
I'm not sure if you know what that means.
If you say you've bricked your phone then no one can help you.
A brick is a brick. It doesn't matter if it weighs a few kgs or a few hundred grams. A brick can't receive phone calls.
And your phone isn't even a normal brick... You wrote that it's "really bricked"
Are you building a house anytime soon?
Click to expand...
Click to collapse
maybe i'm wrong idk maybe is a soft brick. thats why i'm asking for some help.
almomdegal said:
But that way you weren't at a brick point.
You get brick when u get those 3 blink red LED and the phone doesn't do anything
By the fact that your phone were able to load the kernel. i guess
Click to expand...
Click to collapse
The red led blinking rapidly three times means the battery is "out of juice".
I've said it earlier: Several X10 devices have reached an age, where battery failures are fairly common due to charge cycles and/or age. Specially if one got it just after the launch.
Anyhow, what you can do, is let the device charge "blindly" for a while, and a while I mean for half an hour to a few hours. Then it should, out of the blue, jump into "active" charging (With the battery screen showing offline charging)
If this doesn't happen you might have to charge the battery externally.
...or even replace the battery.
-"Why?", one might ask.
Reason is that the flash mode only works with a charged battery.
If it empty, it won't engage the flash mode at all. Stupid design, yes, but that is how it is.
Worst thing is, that the battery does deplete/discharge while in flashing mode. That is why it's so important it's fully charged and fully working, before one engages in flashing activities.
See this post for more information about this: http://forum.xda-developers.com/showthread.php?t=1642154
Try wotanserver's flashtool...
http://www.wotanserver.com/en/
Good luck
SysGhost said:
The red led blinking rapidly three times means the battery is "out of juice".
I've said it earlier: Several X10 devices have reached an age, where battery failures are fairly common due to charge cycles and/or age. Specially if one got it just after the launch.
Anyhow, what you can do, is let the device charge "blindly" for a while, and a while I mean for half an hour to a few hours. Then it should, out of the blue, jump into "active" charging (With the battery screen showing offline charging)
If this doesn't happen you might have to charge the battery externally.
...or even replace the battery.
-"Why?", one might ask.
Reason is that the flash mode only works with a charged battery.
If it empty, it won't engage the flash mode at all. Stupid design, yes, but that is how it is.
Worst thing is, that the battery does deplete/discharge while in flashing mode. That is why it's so important it's fully charged and fully working, before one engages in flashing activities.
See this post for more information about this: http://forum.xda-developers.com/showthread.php?t=1642154
Click to expand...
Click to collapse
Didn't work, i even use my friends battery to flash it and it didn't work
almomdegal said:
Didn't work, i even use my friends battery to flash it and it didn't work
Click to expand...
Click to collapse
Well, if the battery issue was fixed, and you're sure the battery is fully charged, then try this: (Quoting from my other post)
I've charged/replaced the battery, and are having trouble with starting up. Earlier flash failed. Now what?
Don't worry. It's pretty darn hard to truly brick this device. Even if the screen remains black, there's still hope.
Once that the battery issue has been dealt with, you can move on:
Download the latest Flashtool and the proper global firmware (FTF-file) for your device from here:
http://forum.xda-developers.com/show...ight=flashtool
1: Extract/Install the Flashtool to a folder of your liking.
2: Copy the ftf-file to the "firmware" folder in the Flashtool folder you just created above.
3: Start Flashtool. Click the Bolt icon (flash). A Window appear. There, choose "flashmode". Cllick OK.
4: A new window appears. In the list on the left, choose the Generic firmware you downloaded and copied into the "firmware" folder. Should have a similar name as the file itself. (Or manually open the ftf-file from the "..." icon on the top right.)
5: Hit "OK. Follow the instructions you get on the screen:
1 - Unplug the device.
2 - Power off the device. (Unplug and replug the battery to be sure it really off, and not stuck in black screen)
3 - Press the "back" putton, and hold it down while performing the next task.
4 - Plug the device into the computers USB.
Click to expand...
Click to collapse
Forced flashing should now start.
Click to expand...
Click to collapse
time to accept the fact that it is really brick
Hi @almomdegal,
if you try flash using another full charge batt n its not work, I think this forum is no longer works for u anymore.
I own a faulty X10 as well, random shut down (no warning at all) then wont boot n charge
reflash it, revive for few days and dead again, and reflash....
now it is really dead, no problem appears and it show flash successful and it just wont boot or charge but vibrate non stop
I just send the phone to service center and the board need to be replace
so its time to send to the real professional to solve it, coz this problem ain't software downloaded from internet can solve anymore
mooving said:
Hi @almomdegal,
if you try flash using another full charge batt n its not work, I think this forum is no longer works for u anymore.
I own a faulty X10 as well, random shut down (no warning at all) then wont boot n charge
reflash it, revive for few days and dead again, and reflash....
now it is really dead, no problem appears and it show flash successful and it just wont boot or charge but vibrate non stop
I just send the phone to service center and the board need to be replace
so its time to send to the real professional to solve it, coz this problem ain't software downloaded from internet can solve anymore
Click to expand...
Click to collapse
yeah i guess so.
I just needed this closure i'll send it to service today
First of all, I wanted to say hello since this is my first post here :victory: and also please if I am posting wrong or if this question has been answered before forgive me, but I have already searched on google and on this forum and found no related posts Ok now about my problem:
I have a "Sony Ericsson Xperia X10mini Pro" with MiniCM10-4.1.0-20130416(mimmi) and 2.6.32.60-nAa-jb-05 kernel installed. Yesterday I decided to go back to U20_nAa-14_2.6.29.6-nAa-14 kernel and MiniCM7-2.2.1-mimmi-UNOFFICIAL because of wifi problems. I have done the flashing process with flashtool a lot of times in the past and I can't be wrong with it this time.
The problem started after flashing my kernel. Flashtool flashed the U20_nAa-14_2.6.29.6-nAa-14 kernel fine and phone was OK ready to reboot, so I unplugged the USB cable to start it on recovery so I could install Minicm from SD, but since I unplugged the cable the phone is DEAD! No led and no charging! :crying: When I try to reflash it, flashtool doesn't recognize it, I am pressing the back button and plugging it in but the phone is not recognized. It is not charging when I am plugging it on the charger and its not even trying to boot. I tried different cables, different battery (from a friend with the same phone) and nothing. Is there a way to force flash it back? Please any help will be appreciated since I have tried everything I know...
This has happend to other users too reasently.
I'm not sure if it only happens when going from JB to GB or it also happens when going from GB to JB.
We need to investigate why/how it happens and how to prevent it.
I always recomend to do a battery stat whipe just before a planed kernel-flash. I had simular problem once (no charge, no boot, no nothing) after a kernel-flash. I solved it by putting in a battery from another Mimmi (my wife has the same model). For some reason everything worked fine doing so. After battery stat whipe, the phone worked with my own battery again.
Best advise for others is for now: When you want to flash new kernel, first do a SEUS/PC Companion repair
This should be written into all install-instructions and mentioned again and again to avoid same problem for others.
I'm not sure how the other users solved this. Was it only by JTAG?
Thank you for your answer! :good:
First of all, there was no battery wipe option on this release of the kernel As I said before I have done it a couple of times in the past and every time with battery wipe, except this one and besides, I already tried your solution with my friends battery with no luck... So probably I am looking for another solution.
And one last thing about your post, what is "JTAG"?? I have seen it on other posts before but without explanation as to what it is, the only JTAG I know of is on the xbox360 And if its a possible solution how can I possibly do it? Is there a post with instructions?? (I will search on my own too now, but a recommended guide from someone who knows better is much appreciated!)
Emperor.dk said:
This has happend to other users too reasently.
I'm not sure if it only happens when going from JB to GB or it also happens when going from GB to JB.
We need to investigate why/how it happens and how to prevent it.
I always recomend to do a battery stat whipe just before a planed kernel-flash. I had simular problem once (no charge, no boot, no nothing) after a kernel-flash. I solved it by putting in a battery from another Mimmi (my wife has the same model). For some reason everything worked fine doing so. After battery stat whipe, the phone worked with my own battery again.
Best advise for others is for now: When you want to flash new kernel, first do a SEUS/PC Companion repair
This should be written into all install-instructions and mentioned again and again to avoid same problem for others.
I'm not sure how the other users solved this. Was it only by JTAG?
Click to expand...
Click to collapse
zero2048 said:
Thank you for your answer! :good:
First of all, there was no battery wipe option on this release of the kernel As I said before I have done it a couple of times in the past and every time with battery wipe, except this one and besides, I already tried your solution with my friends battery with no luck... So probably I am looking for another solution.
And one last thing about your post, what is "JTAG"?? I have seen it on other posts before but without explanation as to what it is, the only JTAG I know of is on the xbox360 And if its a possible solution how can I possibly do it? Is there a post with instructions?? (I will search on my own too now, but a recommended guide from someone who knows better is much appreciated!)
Click to expand...
Click to collapse
I'm pretty sure he flashed the x10blrelock.ftf instead of the u20 kernel and that is why his phone went dead.
A JTAG for our phone will do basically the same thing as a JTAG for the xbox, it restores original phone-state, but you need special equipment to do it, which is quite expensive. Most repair-shops will have one.
SmG67 said:
I'm pretty sure he flashed the x10blrelock.ftf instead of the u20 kernel and that is why his phone went dead.
A JTAG for our phone will do basically the same thing as a JTAG for the xbox, it restores original phone-state, but you need special equipment to do it, which is quite expensive. Most repair-shops will have one.
Click to expand...
Click to collapse
Thank you for the answer about jtag, I also checked for myself and found about the expensive equipment and propably its not the way for me
But about the kernel I am pretty sure it was the right file...
I know that a dead phone means bad kernel but its a process that I have done before a lot of times with success on mine and other phones My best guess is that something interrupted the process (bad usb cable?) or corrupted downloaded kernel file If that's the case is there an alternative solution? :crying:
zero2048 said:
Thank you for the answer about jtag, I also checked for myself and found about the expensive equipment and propably its not the way for me
But about the kernel I am pretty sure it was the right file...
I know that a dead phone means bad kernel but its a process that I have done before a lot of times with success on mine and other phones My best guess is that something interrupted the process (bad usb cable?) or corrupted downloaded kernel file If that's the case is there an alternative solution? :crying:
Click to expand...
Click to collapse
Usually, whatever you flash, even if it goes bad, flashmode is still available because that doesn't get tampered with, the only true hardbrick i've ever seen is when flashing that x10blrelock.ftf, which happens quite a lot lately.
Just for fun i even formatted my entire phone once, no kernel, no rom, completely empty, and flashmode was still there so it could be recovered.
I noticed that in some older versions of flashtool you sometimes had to click the kernel you wanted twice in order to get it to pick up the right one. Normally there's not much difference you can spot (most .ftf's just contain a loader and a kernel), but i had full SE firmware in .ftf format, which contained other sections too, and that's where i noticed it didn't always pick it up right at the first time of clicking.
SmG67 said:
Usually, whatever you flash, even if it goes bad, flashmode is still available because that doesn't get tampered with, the only true hardbrick i've ever seen is when flashing that x10blrelock.ftf, which happens quite a lot lately.
Just for fun i even formatted my entire phone once, no kernel, no rom, completely empty, and flashmode was still there so it could be recovered.
I noticed that in some older versions of flashtool you sometimes had to click the kernel you wanted twice in order to get it to pick up the right one. Normally there's not much difference you can spot (most .ftf's just contain a loader and a kernel), but i had full SE firmware in .ftf format, which contained other sections too, and that's where i noticed it didn't always pick it up right at the first time of clicking.
Click to expand...
Click to collapse
I understand what you mean and its really easy to make the mistake!! But well, still I don't think I made it but I guess there is nothing more to do anyway Thank you both for your help and I hope soon to return the favor on this forum :victory:
Can you tell me an average cost about the recovery process according to your experiance in your country?? Is is expensive in general?
zero2048 said:
I understand what you mean and its really easy to make the mistake!! But well, still I don't think I made it but I guess there is nothing more to do anyway Thank you both for your help and I hope soon to return the favor on this forum :victory:
Can you tell me an average cost about the recovery process according to your experiance in your country?? Is is expensive in general?
Click to expand...
Click to collapse
Someone in this forum had it done in Latvia for next to nothing.
In the USA it will cost you, your right arm.
zero2048 said:
I understand what you mean and its really easy to make the mistake!! But well, still I don't think I made it but I guess there is nothing more to do anyway Thank you both for your help and I hope soon to return the favor on this forum :victory:
Can you tell me an average cost about the recovery process according to your experiance in your country?? Is is expensive in general?
Click to expand...
Click to collapse
I just had a look online for prices in my country, it seems to be around €25.
SmG67 said:
I just had a look online for prices in my country, it seems to be around €25.
Click to expand...
Click to collapse
Emperor.dk said:
Someone in this forum had it done in Latvia for next to nothing.
In the USA it will cost you, your right arm.
Click to expand...
Click to collapse
Emperor.dk how old are you?
SmG67 thank you again and I will delete x10blrelock.ftf just in case....
hi guys, i have the same problem too, when my rom is minicm10 and my kernel is jb-naa-05, i want to go back to MiniCM7 because of green screen camera in MiniCM10 so i go back to MiniCM7, I flashed the right kernel e10-2.6.29.6-naa-14 for my x10 mini via flashtool and after i flash the kernel, my phone does not booting up(5 mins no booting up) so i decided to use seus but seus does not recognize my x10 mini, i try flashtool, but flashtool is not recognize my x10 mini so i tried to flash my created stock 2.1.ftf(thanks to leajian) and selected x10 mini from device selection(my x10 mini is not recognize in flashtool), then i wait until it finish, when i tried to open my phone, it boots up and show sony ericsson logo and it boots up(sucess!!!)...
sorry for my english...
so for all MiniCM10 Users, Dont try to go back to MiniCM7 If your Rom is MiniCM10 because it will cause your phone to not booting up like my problem.
Renz29 said:
hi guys, i have the same problem too, when my rom is minicm10 and my kernel is jb-naa-05, i want to go back to MiniCM7 because of green screen camera in MiniCM10 so i go back to MiniCM7, I flashed the right kernel e10-2.6.29.6-naa-14 for my x10 mini via flashtool and after i flash the kernel, my phone does not booting up(5 mins no booting up) so i decided to use seus but seus does not recognize my x10 mini, i try flashtool, but flashtool is not recognize my x10 mini so i tried to flash my created stock 2.1.ftf(thanks to leajian) and selected x10 mini from device selection(my x10 mini is not recognize in flashtool), then i wait until it finish, when i tried to open my phone, it boots up and show sony ericsson logo and it boots up(sucess!!!)...
sorry for my english...
so for all MiniCM10 Users, Dont try to go back to MiniCM7 If your Rom is MiniCM10 because it will cause your phone to not booting up like my problem.
Click to expand...
Click to collapse
If you follow nAa's instructions properly, there is no problem.
What you have to do:
Wipe data/factory reset in CWM on the JB-kernel
Flash the GB-kernel
Format /system, /data en /cache, so they get back to the original sizes
Flash the GB-ROM, or restore a previous GB-backup you may have had
No problems at all...
And your phone still had flashmode available, unlike the OP of this thread, so you don't have the 'same' problem
zero2048 said:
Emperor.dk how old are you?
Click to expand...
Click to collapse
Why?
If you are asking me on a date? LOL, the answer is no :laugh: