Related
Is there anyway to unbrick the x10?
It is showing up an exclaimation mark with picture of x10 when the phone starts up
It just stops there and the phone won't boot.
I have tried using SEUS version 2.10.5.11 and PC companion 2.00.134.
For SE update service, when I clicked on X10 and did the instructions given, it says that I have already installed the latest firmware and the only option was to exit. There is no reinstall option.
For PC companion, when I click repair and followed the instructions, it told me to check my internet connection as it wasn't able to connect. I tried disabling my firewall but to no avail. I'm just stalled at Step 3. I have also pressed both pictures of X10 and both gave me the same error.
From other websites, one person was able to unbrick his phone by using davinciteam's debranding service from their x10 blog. I don't know whether it will work and I do not have an account to purchase their service.
So does anyone have any ideas on how to unbrick the X10?
EDIT: Seems that we can only use Davinciteam debranding to unbrick the phone but it costs 10 euros - I personally did not try it
And I have sent my phone to Sony Ericsson service to get it unbricked.
So next time guys, after you debrand your phone, remember to rebrand it to original before debranding it to another firmware. That was my mistake. After I get my phone back, I'm going to try it again
EDIT: 22/5/10
My phone is unbricked and seriously, how do they do it?
Wonder if they can like share their methods with us
I will try to debrand once again tomorrow, and hopefully I do not need to pay them another visit at their service center
Sony Ericsson service. I was yesterday and 15 - 20 minute to unbricked my phone ;-)
slezi said:
Sony Ericsson service. I was yesterday and 15 - 20 minute to unbricked my phone ;-)
Click to expand...
Click to collapse
Hey can you explain to me your steps?
I tried to unbrand my phone, the first firmware upgrade succes. The third firmware (nordic 16) SEUS said succes, but when i turn on my phone i gace sam nic picture on my phone. I called my place nearest SE service and i get may car, and drive the service...
Oh, so you went to their services..
How did you tell them to fix your phone?
They are special update software.
Aztriltus - my friend happened the same thing to you, he use this Davinci Flashing / Debranding service and his X10 works well again. But it costs 10euro.
Search google for "davinciteam".
Hmm so I guess there isn't any manual way to unbrick x10..
Nevermind, I have already sent my phone to servicing
Wonder how do they unbrick them lol.
just use the debranding service davinciteam is offering. You download the program off their website and purchase credits, then just login with your user details on the program and follow the instructions (much like seus). You can choose from the list what firmware you want and it'll be up and running.
davinci
I was so happy when I read about DaVinci. My phone hung quite down as described above. But with the software I got him running again. Approximately 15 minutes and he is back again. I have already rooted him again.
Root your phone & it's unbricked
Have you tried the flash unbrick tool? It fixes it nomatter what. No need to spend any money for something available here for free
what is that called?
omarr50 said:
what is that called?
Click to expand...
Click to collapse
XIOFUB.rar is the flash tool.
a_WWE_R1FA014_DEK is the Rogers file (select the one that you need for your region)
http://forum.xda-developers.com/showthread.php?t=683793
Posts 2 and 3
My phone wasn't Bricked like yours in the sense that it didn't show the exclamation point when you attempted to turn it on, mine just stayed at the "Sony Ericsson" screen and wouldn't not move on.
This video is what got me back to 1.6:
http://www.youtube.com/watch?v=4AZ_10cvd9k
I did a lot of theme changes, I think that's why I screwed my phone up. Lesson learned.
Moved to Correct Forum
Many months ago I updated my Rogers X10a to a X10i firmware. Later, thanks to a method and tools posted by Gorokhan (sp) I was able to switch to the Japanese Docomo X10a.
Now I would like to rebrand my phone to the current Rogers X10a firmware. I have tried many methods for about a week now. I've used the different flash tools from http://forum.xda-developers.com/showthread.php?t=683793 and http://forum.xda-developers.com/showthread.php?t=740240 as well as various firmwares posted in these forums.
So far I've managed to:
Revert to a generic X10i
Brick my phone 4 times
Debrick my phone as many times (thanks devs, love your tools )
Never ever been able to switch back to any X10a firmware
I've also tried SEUS, PC Suite, etc... to no avail.
I know some people on Rogers have done this successfully in the past but with various methods that don't necessarily work anymore. Can someone please explain what method, with which files, currently works to rebrand from an X10i firmware back to a genuine X10a Rogers?
Thanks
Download this firmware:
http://hotfile.com/dl/43225669/598add6/a_WWE_R1FA014_DEK.zip.html
Should have the flash tool for 1.6 included.
Flash it then upgrade with SEUS or PC to R2BA020 (latest Rogers FW)
Thank you. I I will try this tonight when I get home.
Well, it did the job for me
If you don't run in java problems with the flasher.
DevID problems, damaged USB or whatever you should be fine
It worked!!
For the first time in my life I was pretty happy to see that ugly Rogers logo show its face Naw, to be honest, they've been pretty good to me, I have no complaints.
Thanks for the help tuxStyle
Do you mind me asking why you wanted to go back to Rogers?
The phone needs warranty repair. I had to buy a new phone in the meantime :/
I have the same situation but I don't know how to use the flash tool, can you give me a brief tutorial? thanks
Where is the flash tool
Is the flash tool included with the file? I couldn't find it in the .zip file. can someone upload it for me please?
tuxStyle said:
Well, it did the job for me
If you don't run in java problems with the flasher.
DevID problems, damaged USB or whatever you should be fine
Click to expand...
Click to collapse
I believe I just hit the "DevID" wall. Anyway to "overcome" this?
Thanks.
I ran into the same problem. Trick is, when you find the device id in the registry, if it doesn't work, keep hitting F3 until you find another one. I think it creates a dev ID for every USB port on the computer you have ever plugged the computer into. So either try different IDs or try plugging your phone into another USB port.
Rebranding Xperia X10 to Rogers firmware to get update
Follow this link for a brief tutorial on rebranding and then updating to 2.1. The post is just a collective of bits of information found in various posts here in XDA.
http://blog.jeshurun.ca/random-scribblings/re-branding-rogers-xperia-x10a-for-android-2-1-update
Great news for Xperia Neo User
After several try, i successful root 2.3.3 Xperia Neo
First at all thank to kistigun and kokbiel for discover this in Xperia ARC, therefore i take this as a credit for them
If you are Neo user i believe u have go through this page
[TUT]
But if you try that, i ensure you that you may brick your phone, as that tutorial is for Xperia Arc only. So this is how to root your NEO.
Basicly is using back the same way like Xperia ARC, just you change the firmware to M15 instead of L15. i copy entire thing from Kistigun step in here
...........................................................................................................
Do not try this if you have an unlocked bootloader or if you dont know what your doing! I'm not resposible if you break or brick your phone!
If you're allready on a rooted .181 and OTA update is available for you just update your firmware. If there is no OTA update available for your customazation version follow these instuctions:
- flash back to M15 3.0.A.2.181 generic with the flashtool
- Use Gingerbreak or Superoneclick to root your device
- Update your Xperia Neo using a OTA(over the air) update(Go to settings->About phone->Software update)
- Enjoy your rooted 2.3.3!!!
Update 1: it seems that the OTA update is not working if you did any modifications to/deleted system files so it's adviced to always flash the .181 firmware provided in this post
Update 2: if you have any battery problems after flashing the .181 firmware(if it's only showing 1%) removing the battery for a few minutes should solve this
Update 3: thanks to ricstc we now have a video tutorial on how to follow these instructions
Update 4: if you want you can keep your user data by unchecking the whipe user data in the flashtool while selecting the correct ftf file. this will cause a lot of error message's on 2.3.2 but just click them away and continue the procedure, after upgrading again to 2.3.3 the error message's will be gone!
Update 5: IF some of you unable update the via OTA, don worry, restart the phone and left it 1-6 min, and try to update again.
M15 3.0.A.2.181 Generic Rom
How come the neo doesn't have a section of it's own?
Sent from my R800i using XDA App
it looks that file with .181 is no longer available from this Chinese site...
Thanks!! is great =)
Need a Neo forum!
Here is the HF mirror of the M15 3.0.A.2.181 Generic Rom
Cheers,
lovenemesis said:
Here is the HF mirror of the M15 3.0.A.2.181 Generic Rom
Cheers,
Click to expand...
Click to collapse
thanks for helping
Just add a few lines from my experience.
The booting after OTA upgrade seems to go forever. After a looooooong time it just greyed.
(I cannot believe) it's not bricked. Just knock off the battery and put it back. This time the rebooting will be done in a flashy manner.
Now a pop-up will welcome you to the world of Android 2.3.3 with root privilege.
Now I have
lovenemesis said:
Just add a few lines from my experience.
The booting after OTA upgrade seems to go forever. After a looooooong time it just greyed.
(I cannot believe) it's not bricked. Just knock off the battery and put it back. This time the rebooting will be done in a flashy manner.
Now a pop-up will welcome you to the world of Android 2.3.3 with root privilege.
Now I have
Click to expand...
Click to collapse
really, maybe it depend on the network, i just done it after brick my phone 1 time, but after that found this way,flash, root and update, seem is ok for me.
Hello guys,
I really need some help!!
I've started this but after "found on usb..." it gave an error and told me to turn on the phone...
But the phone does not turn on!! I press the power and there is the small vibration but nothing happens. All stays black screen.
Can anyone help me please?
Thanks.
I've sorted this out! Had to use a special shielded microUSB cable to be able to complete the update using SEUS without loosing connection.
About flashing, I had no luck. Always the same error asking to alow untrusted apps and usb debugging...
Anyone did this with success?
Hello,
Can we apply the M15 3.0.A.2.181 on a MT15a phone?
Thanks
Hi,
Which version of FlashTool did you use, 0.2.9.1 beta or 0.2.8 stable ?
I used the beta one.
After that, I did try with 0.2.8 but the samething happens.
Are there permissions needed on the mobile to flash it?
I've sorted this out! Had to use a special shielded microUSB cable to be able to complete the update using SEUS without loosing connection.
About flashing, I had no luck. Always the same error asking to allow untrusted apps and usb debugging...
Anyone did this with success?
Edit:
Just to let everyone know that I've managed to get rooted! Thanks for everything...
By the way, GingerBreak took 35 munites before shutting down!
I'm also stuck with black screen, any help???!!!! how did you pul it off??
How I did it:
wiewiur333 said:
I'm also stuck with black screen, any help???!!!! how did you pul it off??
Click to expand...
Click to collapse
The problem I had was related with flashing crashing in the middle of the process...
So, I tried times and times (about 35 or 40) and finally, the flashing completed with no errors.
Honestly, it took many times as sometimes the computer would not recognize the phone, and I had to unplug and replug the usb cable again.
After that, I did use a bettermicro USB cable to do all the procedure as explained on the first topic and all was successfull. I still did has 3 or 4 errors but I started over till it completes with no error.
I am now convinced (after some experiences on this same Neo) that different computers or windows versions may have an influence as on my laptop I get many less erros than on the desktop. Both using Win7.
And on the last weekend, at my friend's XP it did flash at first with no errors at all (coincidence?).
Hope this helps.
dreasi0n said:
Hello guys,
I really need some help!!
I've started this but after "found on usb..." it gave an error and told me to turn on the phone...
But the phone does not turn on!! I press the power and there is the small vibration but nothing happens. All stays black screen.
Can anyone help me please?
Thanks.
I've sorted this out! Had to use a special shielded microUSB cable to be able to complete the update using SEUS without loosing connection.
About flashing, I had no luck. Always the same error asking to alow untrusted apps and usb debugging...
Anyone did this with success?
Click to expand...
Click to collapse
then how about you unchecked Allow Untrusted apps and usb debugging
for the flashing part, if u follow the video tutorial closely should be no problem
@ nash_ph_41
Hi... 3 posts before the one you quoted I'm letting everyone know that I'm rooted already.
Those USB and Trusted warnings are 'default'? error messages that flashtool displays on unexpected errors, I think...
nash_ph_41 said:
Great news for Xperia Neo User
...........................................................................................................
Do not try this if you have an unlocked bootloader or if you dont know what your doing! I'm not resposible if you break or brick your phone!
Click to expand...
Click to collapse
i need to disagree. i cannot root my neo using gingerbreak if not unlocking bootloader. if i use different method using superoneclick, it will give an error something like this: cannot mount /system
so what i did:
1. unlock bootloader.
2. run gingerbreak, it will rooting less than 3 minutes comparing to locked bootloader, taking forever
3. locking back the bootloader.
4. update.
after the updating process, i get android 2.3.3 with root enabled.
@ mohdazuan
If you already unlocked your bootloader, why didn't you just use DooMLord's kernal and flash the latest firmware? You anyway wiped the DRM files. So there's no point in actually relocking it unless of course it's to use SEUS.
thats the point, i just want to use SEUS
i did the bootloader unlocking at the first time because want to flash custom rom using fastboot before finding out that rooted 2.3.2 can be updated to 2.3.3 without losing root access.
anyway i don't care about DRM since my digital contents is not all "right"
Gentlemen, I couldn't find a section for Xperia Pro, please excuse me if this is misplaced.
I rooted my MK16i from ICS 4.0. according to a guide here on XDA forum, with no problems (from 4.1.a.435 .. i think).*
Then I installed system tuner and backed up the bloatware and what I believed was obviously named as packages that support them. Things were working great and the phone gained some performance improvements.
UNTIL, I installed Viber and Skype, and niether were working. I thought I would fix it by restoring all the backed up services and apps. Once I did that and rebooted the phone, it became useless
THe phone keeps rebooting. I get to the XPERIA loading screen and then it restarts again
I tried to connect it to the PC to flash another ROM with the Flashtool, but it is not recognized. All I get is in the computer screen a removable disk drive, that is not accessible.
Note: I didnt update the firmware after I rooted.
Can anybody help?
have you worked with flashtool before ? because there hardly could be any wrong with flashtool. use the latest version with proper drivers.
and since you have rooted phone, have you unlocked your bootloader ? if yes, then flash any custom kernel, go to CWM, then place rom zip on sdcard and stright flash rom via CWM.
flashtool should work though. you can try on different computer.
If flashing a kernel or installing custom ROM sounds a bit out-of-reach, you can always go for the repair option in PC Companion. It worked for me when I had soft-bricked my Neo V (it wouldn't go past the SONY logo). However, be advised that this repair option will erase your phone's internal memory. Also, your phone will be brought on the latest stock ROM, so you will need to root your phone again.
Good Luck!!! :good:
acemccloud1 said:
If flashing a kernel or installing custom ROM sounds a bit out-of-reach, you can always go for the repair option in PC Companion. It worked for me when I had soft-bricked my Neo V (it wouldn't go past the SONY logo). However, be advised that this repair option will erase your phone's internal memory. Good Luck!!! :good:
Click to expand...
Click to collapse
I tried to do somethingn like this but sony companion itself cannot detect the phone either.
My question is, is there a brick that cannot be fixed? I took it to a shop today and still they cannot fix it.
Have you tried to use sony update service?
How are you connecting your phone to flashtool?
Can you show us log from flashtool?
New development:
Now I tried to flash the phone with flashtool 32bit rather than 64-bit and it detected the phone! I could even flash the only firmware in Aeonworld's post Here.
Now I can see the phone connected in my computer.
However, the phone still won't boot but when I power on it gives black screen and after a short while, the led on the side becomes green.
For some reason though, I cannot continue with the rooting steps in his guide.
So anyways, after the second reboot, not the first for some reason, the phone gets detected in PC Companion, and I installed the update and now it is working again :victory:
Thank you all for your support.
moeness86 said:
New development:
Now I tried to flash the phone with flashtool 32bit rather than 64-bit and it detected the phone! I could even flash the only firmware in Aeonworld's post Here.
Now I can see the phone connected in my computer.
However, the phone still won't boot but when I power on it gives black screen and after a short while, the led on the side becomes green.
For some reason though, I cannot continue with the rooting steps in his guide.
So anyways, after the second reboot, not the first for some reason, the phone gets detected in PC Companion, and I installed the update and now it is working again :victory:
Thank you all for your support.
Click to expand...
Click to collapse
Good to hear that bro!!! R&D always makes a man better
Hi guys
I followed this guide for unlock bootloader and install magisk: https://forum.xda-developers.com/t/...re-and-gsi-rom-flashing-without-twrp.4344371/
I don't blame the author of the guide, it is my device, my responsibility, my decision to attempt this. My fault.
Everything was going great, I unlocked the bootloader successfully and my device wiped and rebooted. It boot back into android, I turn off, go to fastboot mode, and try to flash magisk img file I made earlier in the guide. It says success, then last step of the guide is to wipe with fastboot -w. This fails, says cannot wipe metadata. Reboot, now my phone says "your device is corrupted and cannot be trusted and will not boot"
No idea what to do here, so i try to use Xperia Companion to restore. But it refuses because it detect bootloader is unlocked. Now I try to use NewFlasher to flash firmware from XperiFirm, this starts off fine but then NewFlasher reaches this point
"Extracting sparse chunk super.040"
"Uploading sparse chunk C:\temp\xperiafirmware\flash_sesson_super.0.40"
"download:03b4c9c"
"ERROR: TIMEOUT: failed with error code 997 as follows:
Overlapped I/O operation is in progress
I have tried to do this with another computer, I have tried 2 other USB cables, I have tried another firmware (originally tried the latest version with open carrier but also tried with carrier specific one) I am now running out of ideas to try.
I can get to fastboot mode or flash mode, but if I try to boot OS it says "your device is corrupted and cannot be trusted and will not boot"
Any help or a point in the right direction would be much appreciated
Thank you so much in advance
Last week that happened to me. As long as you can go to fastboot you're good. First is relock the bootlaloader via fastboot then repair it using xperia companion. Or if you can download the firmware via xperifirm then flash it via flasher.
Also make sure that the PC your using has both an Intel CPU or AMD CPU and a full windows install not that cheap windows store only crap..but one you can actually install windows .exe files and make sure you have installed the Xperia drivers by turning off driver verification...o tried without and my 2 in 1 couldn't find my phone for Xperia companion nor the other flashing tool...
Thank you @Mangtas_666 @Ainz_Ooal_Gown I have no idea why but I just couldn't flash the UK firmware, tried 2 versions but neither would flash with NewFlasher. kept getting these timeout errors. But then i randomly decide to try the US firmware (XQ-BC62 instead of XQ-BC52) and it worked 1st try. My phone is up and running again!
The strangest part, when it connect to the internet and I apply all my UK settings, it somehow change back to XQ-BC52 on its own. It is detected as such in "about phone" now even though I didn't re-install firmware since fixing it with the US one. Oh well, i'm not going to complain, I'm just happy it's fixed. Thanks for replying
marshedpotato said:
Thank you @Mangtas_666 @Ainz_Ooal_Gown I have no idea why but I just couldn't flash the UK firmware, tried 2 versions but neither would flash with NewFlasher. kept getting these timeout errors. But then i randomly decide to try the US firmware (XQ-BC62 instead of XQ-BC52) and it worked 1st try. My phone is up and running again!
The strangest part, when it connect to the internet and I apply all my UK settings, it somehow change back to XQ-BC52 on its own. It is detected as such in "about phone" now even though I didn't re-install firmware since fixing it with the US one. Oh well, i'm not going to complain, I'm just happy it's fixed. Thanks for replying
Click to expand...
Click to collapse
No problem fam, glad it got sorted out