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:
Related
here is the situation
the x10 is dead, when trying to turn it on nothing happens(no vibration w/ black screen)
if take the battery out and put it back and try to turn it on, the phone would vibrate a bit with black screen
the programs however do recognize the phone when plugged in
well i basiclly tried three things to try to repair it
1. SEUS-which oddly tells me that the phone is up to date but the phone is still a brick
2. PCC- which gave me err
3. Flashtool- which gave me err too(i was trying with X10i 2.1.A.435 Global Generic)
when i tried to flash the phone it told me to turn on the phone then turn on Unkonwn Sources and Debugging... which obviously i can't do
i believe this would be the 1000th time someone post thread about this problem but i have to ask for some help after spending my whole sunday afternoon trying to solve the problem by myself.
i'm on the edge of giving up so this will be my last attempt if nothing new comes up
╰(￣▽￣)╮ thanks to anyone who finished reading this boring thread and if there is a suggestion feel free to post it thanks again
I think we both have the same problem, I tried flashing it to the generic 1.6 fw and I was able to revive the phone. After which I updated it to 2.1 fw, now it seems to be working fine.
maybe a physical problem?
please try to flash with flashtool and post a log
Well, I also had a similar issue after updating a busybox from market on CM 6.1.3 rom.
Download the Flash tool & rom for the following link, follow the instruction & you are done my friend.
http://forum.xda-developers.com/showthread.php?t=928343
I got my phone working again.
All the best & happy modding.
getjayu said:
Well, I also had a similar issue after updating a busybox from market on CM 6.1.3 rom.
Download the Flash tool & rom for the following link, follow the instruction & you are done my friend.
http://forum.xda-developers.com/showthread.php?t=928343
I got my phone working again.
All the best & happy modding.
Click to expand...
Click to collapse
Well, you don't reinstall busybox and/or xRecovery when you are in a custom rom.
Yeh i agree, you've gone a bit too far. Private message obe of the devs, ur situation is way worse than normal bricks.
Sent from my X10i using XDA Premium App
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've just got bricked u20i. I don't know what previous owner have done with this phone, but it has bootloop. I've tried to flash stock 2.1 with flashtool and seus with the same result. Phone normally enters flashmode and can be flashed. Is there any way to resurrect that phone?
Well..all you have to do is http://forum.xda-developers.com/showthread.php?t=1682966
You can solve the problem by searching.
Sent by Vince™
It doesn't seems to be helpful to me. I just can't boot it - it looks to be frozen after second boot animation. I don't want to mod it (at the moment) but if I would, I should have rooted phone, but I can't do it, because it can't boot.
Dreadlish said:
It doesn't seems to be helpful to me. I just can't boot it - it looks to be frozen after second boot animation. I don't want to mod it (at the moment) but if I would, I should have rooted phone, but I can't do it, because it can't boot.
Click to expand...
Click to collapse
Maybe there's a problem with the sd-card, if it's missing, put one in, if there's one in the phone format it if you can.
SmG67 said:
Maybe there's a problem with the sd-card, if it's missing, put one in, if there's one in the phone format it if you can.
Click to expand...
Click to collapse
Just tried it with some different cards - without result.
Dreadlish said:
Just tried it with some different cards - without result.
Click to expand...
Click to collapse
If fresh firmware from SEUS Does not yield results there's a piece of hardware that's broken I suppose, don't think there's much you can do about that.
Morning everyone
i have tried to search the forums with a similar problem, but i couldnt find a solution to this.
NOTE; If there is, please provide a link to the post, i'll appreciate that.
So this is what happened :
i flashed the phone with custom rom ( MiniCM9/JB/ICS) successfully..but after finding that the camera didnt work with one of the roms ICS i think, i reverted back to the original e10i kernel.
the problem with this is that PC Companion couldnt update my phone, as it didnt recognise it, it only said SONY/SONY ERICSSON phone..apart from that, the battery seems to have died out, i tried charging it on the wall plug but it would boot up and display the SONY ERICSSON logo and after a few seconds, restart. it doesnt seem to charge the phone but rather gives it a 'boost' to boot up. it does the same thing when plugged in the laptop. Now, the baterry seems to have been depleted completely as the red led flashes while still connected in flash mode.
I expected a big battery icon to display when i charged it on the wall plug but i got the boot logo...and restarts..SEUS said i have the latest software..PC companion couldnt ''repair'' it because the battery would run out while still connected in flashmode.
Please assist me in anyway.
thanks
AGAIN : if there is a problem somewhere in the forums PLEASE direct me to it, i dont wanna cause any spam on the forums.
Thank you
hands360 said:
Morning everyone
i have tried to search the forums with a similar problem, but i couldnt find a solution to this.
i flashed the phone with custom rom ( MiniCM9/JB/ICS) successfully..but after finding that the camera didnt work with one of the roms ICS i think, i reverted back to the original e10i kernel.
I expected a big battery icon to display when i charged it on the wall plug but i got the boot logo...and restarts..SEUS said i have the latest software..PC companion couldnt ''repair'' it because the battery would run out while still connected in flashmode.
Click to expand...
Click to collapse
Your main problem is that you still have the custom ROM although you're back on stock kernel. Try to flash this with flashtool.
downloading
SmG67 said:
Your main problem is that you still have the custom ROM although you're back on stock kernel. Try to flash this with flashtool.
Click to expand...
Click to collapse
Thanks bro..i'm downloading it now will try it after an hour or so..have to go to a friends house for a laptop..thanks to lighting storm. Anyway i'll keep you updated with the process.
After doing so can i flash custom rom?(i'd like to think so, just confirming to ease my conscience lol) and currently which is the most stable rom between the aforementioned roms? Just looking for your opinion.
Thanks again.
hands360 said:
Thanks bro..i'm downloading it now will try it after an hour or so..have to go to a friends house for a laptop..thanks to lighting storm. Anyway i'll keep you updated with the process.
After doing so can i flash custom rom?(i'd like to think so, just confirming to ease my conscience lol) and currently which is the most stable rom between the aforementioned roms? Just looking for your opinion.
Thanks again.
Click to expand...
Click to collapse
Yes, your bootloader will remain unlocked, so you will be able to flash custom kernels and roms, no problem.
They are working on a fix for the camera, and the first one updated will be MiniCM9 i think, but for now MiniCM7 (or other gingerbread based roms) remains the best performing option for our phones.
fail
SmG67 said:
Yes, your bootloader will remain unlocked, so you will be able to flash custom kernels and roms, no problem.
They are working on a fix for the camera, and the first one updated will be MiniCM9 i think, but for now MiniCM7 (or other gingerbread based roms) remains the best performing option for our phones.
Click to expand...
Click to collapse
Smg, i tell you, Yesterday was not my xperias day. My data bundles depleted while it had gone 80% (i think) into the download, i then recharged for another 100MB unfortunately i was using my ageing 6730c on Opera mini n the download couldnt resume! So i'd like to know, how big is the file itself because when it started, it said 114MB it reached that size and kept on going till 188MB i guess that's how much bundles i had. Anyway will try to get a wifi hotspot.
I think i'll go with the MiniCM7 for now till further development is made for these ROMS. A very big up to the developers.
Till i get that file! Later
hands360 said:
Smg, i tell you, Yesterday was not my xperias day. My data bundles depleted while it had gone 80% (i think) into the download, i then recharged for another 100MB unfortunately i was using my ageing 6730c on Opera mini n the download couldnt resume! So i'd like to know, how big is the file itself because when it started, it said 114MB it reached that size and kept on going till 188MB i guess that's how much bundles i had. Anyway will try to get a wifi hotspot.
I think i'll go with the MiniCM7 for now till further development is made for these ROMS. A very big up to the developers.
Till i get that file! Later
Click to expand...
Click to collapse
Yes, sorry about that.. it's the original SE stock 2.1 firmware and it comes in at about 210mb, although the site keeps saying differently, i don't know why it does that. You need to flash it with flashtool.
success
hey bro....guess what..it worked. I ended up downloading the file via a blackberry lol anyway it was 210MB...215 in fact..anyway my phone is fixed and ready for customisation. A very big Thank u man. I'm just waiting for it to fully charge because it was completely drained i was lucky it survived the original stock flashing.
Thanks for the time and energy you put in. I really appreciate it. Cant wait to get my Samsung Galaxy Gio lol i know its a bit old now but it hasn't seen the 'other side' of the grass.
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