I have just been given a Sony Xperia Mini Pro with a broken touch screen.
The LCD works and when I was given the device it was in Airplane mode somehow I was able to access the device but what I did to get it to bypass the slider I couldn't tell you. I then put it into adb debugging and started adding an account etc... anyway at some point the screen turned off and now I cannot access it again. I have tried using moroboro to install other launchers then pressing home button (back button home and menu work but nothing above that) after entering a couple of numbers to activate the emergency dialer. This allows me to choose the launcher that I want to use but it still has the same lock screen slider.
I am trying to either bypass the slider part of the process, I thought I accomplished this by switching to a password to open the phone, but that didn't work and now no matter whether I am using airplane mode or not I cannot get the screen to unlock like I did before. It even connects to the internet because I setup wifi on the device. It is in MTP mode though and one potential fix I thought of for using flashtool to reinstall the rom says MTP BAD or words to that effect. Can anyone help me with this?
I can connect via emmulator when the phone is off but connected to the computer and I can get adb shell su to work, but don't know where to go from there. I found a few things regarding changing the sqlite3 db but am nowhere near knowledgeable to start messing with that.
If you need anything further as to information please let me know.
Thanks
Phone should in flash mode for flash tool to work
machv5 said:
I have just been given a Sony Xperia Mini Pro with a broken touch screen.
The LCD works and when I was given the device it was in Airplane mode somehow I was able to access the device but what I did to get it to bypass the slider I couldn't tell you. I then put it into adb debugging and started adding an account etc... anyway at some point the screen turned off and now I cannot access it again. I have tried using moroboro to install other launchers then pressing home button (back button home and menu work but nothing above that) after entering a couple of numbers to activate the emergency dialer. This allows me to choose the launcher that I want to use but it still has the same lock screen slider.
I am trying to either bypass the slider part of the process, I thought I accomplished this by switching to a password to open the phone, but that didn't work and now no matter whether I am using airplane mode or not I cannot get the screen to unlock like I did before. It even connects to the internet because I setup wifi on the device. It is in MTP mode though and one potential fix I thought of for using flashtool to reinstall the rom says MTP BAD or words to that effect. Can anyone help me with this?
I can connect via emmulator when the phone is off but connected to the computer and I can get adb shell su to work, but don't know where to go from there. I found a few things regarding changing the sqlite3 db but am nowhere near knowledgeable to start messing with that.
If you need anything further as to information please let me know.
Thanks
Click to expand...
Click to collapse
Bro,u can use flashtool only in flashmode not in mtp mode
so turn off your device..press and hold vol down while connecting the usb cable and your phone led should turn green..now get yourself a stock ftf file from http://talk.sonymobile.com/thread/35239 and flash it..or use SEUS and see if you can get the touchscreen working...
remember that phone data and apps will be lost when you flash but sdcard will be untouched..
may be your touchscreen drivers are corrupted and reflashing stock may solve the problem..i hope so..
regards..
a|\|droid_user said:
Bro,u can use flashtool only in flashmode not in mtp mode
so turn off your device..press and hold vol down while connecting the usb cable and your phone led should turn green..now get yourself a stock ftf file from http://talk.sonymobile.com/thread/35239 and flash it..or use SEUS and see if you can get the touchscreen working...
remember that phone data and apps will be lost when you flash but sdcard will be untouched..
may be your touchscreen drivers are corrupted and reflashing stock may solve the problem..i hope so..
regards..
Click to expand...
Click to collapse
machv5 said:
I have just been given a Sony Xperia Mini Pro with a broken touch screen.
The LCD works and when I was given the device it was in Airplane mode somehow I was able to access the device but what I did to get it to bypass the slider I couldn't tell you. I then put it into adb debugging and started adding an account etc... anyway at some point the screen turned off and now I cannot access it again. I have tried using moroboro to install other launchers then pressing home button (back button home and menu work but nothing above that) after entering a couple of numbers to activate the emergency dialer. This allows me to choose the launcher that I want to use but it still has the same lock screen slider.
I am trying to either bypass the slider part of the process, I thought I accomplished this by switching to a password to open the phone, but that didn't work and now no matter whether I am using airplane mode or not I cannot get the screen to unlock like I did before. It even connects to the internet because I setup wifi on the device. It is in MTP mode though and one potential fix I thought of for using flashtool to reinstall the rom says MTP BAD or words to that effect. Can anyone help me with this?
I can connect via emmulator when the phone is off but connected to the computer and I can get adb shell su to work, but don't know where to go from there. I found a few things regarding changing the sqlite3 db but am nowhere near knowledgeable to start messing with that.
If you need anything further as to information please let me know.
Thanks
Click to expand...
Click to collapse
There is a simple solution flash stock rom
http://forum.xda-developers.com/showthread.php?p=43897224
a|\|droid_user said:
Bro,u can use flashtool only in flashmode not in mtp mode
so turn off your device..press and hold vol down while connecting the usb cable and your phone led should turn green..now get yourself a stock ftf file from http://talk.sonymobile.com/thread/35239 and flash it..or use SEUS and see if you can get the touchscreen working...
remember that phone data and apps will be lost when you flash but sdcard will be untouched..
may be your touchscreen drivers are corrupted and reflashing stock may solve the problem..i hope so..
regards..
Click to expand...
Click to collapse
I don't think you understand about the touchscreen it's physically cracked it was dropped on the ground or something like that. I don't think it's a driver problem. lol. I should have been more specific considering that most of the references to the touchsecreen not working that I found were more software related than hardware like mine.
I know how to get into flashmode but thought that I had to have a bootloader that was unlockable (Rogers would never allow that setting to be overlooked). I can't update via the PC companion because I can't unlock the screen and I don't have a Rogers sim to put in it. The main reason I want to do this mainly is to see if it is working other than the damage to the screen and I didn't get around to checking everything before I shut off the screen which locked it. I don't want to spend $35 on a new screen assembly only to find out that one or more fundamental things on the phone don't work.
I am suprised that there isn't an unlock key-combination that you can use via the slider keyboard.
Does anyone know what it would be that would cause the phone to bypass the lockscreen before and why it won't now?
Alright i got it...
machv5 said:
I don't think you understand about the touchscreen it's physically cracked it was dropped on the ground or something like that. I don't think it's a driver problem. lol. I should have been more specific considering that most of the references to the touchsecreen not working that I found were more software related than hardware like mine.
I know how to get into flashmode but thought that I had to have a bootloader that was unlockable (Rogers would never allow that setting to be overlooked). I can't update via the PC companion because I can't unlock the screen and I don't have a Rogers sim to put in it. The main reason I want to do this mainly is to see if it is working other than the damage to the screen and I didn't get around to checking everything before I shut off the screen which locked it. I don't want to spend $35 on a new screen assembly only to find out that one or more fundamental things on the phone don't work.
I am suprised that there isn't an unlock key-combination that you can use via the slider keyboard.
Does anyone know what it would be that would cause the phone to bypass the lockscreen before and why it won't now?
Click to expand...
Click to collapse
Alright I got it..
Install this app ShareKM via adb on your phone and download the share km server on your pc... now you can use your mouse and keyboard as input devices via usb..just google sharekm and you will find it...assuming that you know the screen unlock code or pattern you can fully use your device with you pc's keyboard and mouse
Are we good?
Regards..
prantoroy said:
There is a simple solution flash stock rom
http://forum.xda-developers.com/showthread.php?p=43897224
Click to expand...
Click to collapse
I couldn't find the SK17A firmware the link you gave me. The list below is from the page
A Guide For New Users 2 Extreme User.
As We All Are Using Any Phone From Xperia 2011 Lineup
Phones Are
1. Sony Ericsson Live With Walkman (WT19i)
2. Sony Ericsson Xperia Mini (ST15i)
3. Sony Ericsson Xperia Mini Pro (SK17i)
4. Sony Ericsson Xperia Active (ST17i)
This Guide Only Tested On These Phones. So, I would Recommend These Only to Users of These Phones.
a|\|droid_user said:
Alright I got it..
Install this app ShareKM via adb on your phone and download the share km server on your pc... now you can use your mouse and keyboard as input devices via usb..just google sharekm and you will find it...assuming that you know the screen unlock code or pattern you can fully use your device with you pc's keyboard and mouse
Are we good?
Regards..
Click to expand...
Click to collapse
Yes I know the screen unlock code. I'll try it and get back to you.
Well that didn't work. I don't know what i was supposed to see but I ran it via USB and Wifi and nothing. I didn't even see any Ui other than phone connected. And using the keyboard shortcuts like win+b opened up bookmarks and ctrl+win did nothing and rather than start ctrl+(x) my way through the keyboard I decided to uninstall it.
Also regarding the firmware that I found called "Sk17a_4.1.B.0.431_Generic Trade US" it's not for a Rogers phone and I don't want to flash the myriad of files no matter how tempted I might be until I know for sure that it won't brick the device.
Files included in the package are
adsp.sin
amss.sin
amss_fs_mango.sin
apps_log.sin
cache.sin
fota0.sin
fota1.sin
kernel.sin
loader.sin
simlock.ta
system.sin
userdata.sin
I have an idea though on how I can basically factory reset the phone through flashmode if it will work and it not brick anything let me know. I am thinking that if I check exclude for all the parts that can be installed:
SYSTEM
BASEBAND
KERNEL
FOTA
TA
and also for wipe check:
DATA
CACHE
APPSLOG
I will factory reset the phone while at the same time not flash anything that could harm the device. My device cannot have it's bootloader unlocked.
The only thing that I can see that I am not able to change is the loader.sin from being installed to the phone, (likely the only thing if installed to the wrong carrier version, etc... that will have the phone burst into flames knowing my luck, lol Whimper)
Oh and btw I have managed to root the phone using flashtool successfully but am unable to allow anything to run as root because of the pesky locked screen problem I'm having so I am getting fails for anything I try to do as root.
machv5 said:
I couldn't find the SK17A firmware the link you gave me. The list below is from the page
A Guide For New Users 2 Extreme User.
As We All Are Using Any Phone From Xperia 2011 Lineup
Phones Are
1. Sony Ericsson Live With Walkman (WT19i)
2. Sony Ericsson Xperia Mini (ST15i)
3. Sony Ericsson Xperia Mini Pro (SK17i)
4. Sony Ericsson Xperia Active (ST17i)
This Guide Only Tested On These Phones. So, I would Recommend These Only to Users of These Phones.
Click to expand...
Click to collapse
go lower
u will find .ftf firmware list
prantoroy said:
go lower
u will find .ftf firmware list
Click to expand...
Click to collapse
ok, will do
prantoroy said:
go lower
u will find .ftf firmware list
Click to expand...
Click to collapse
I didn't find the exact firmware for my Rogers device through that page. But I did find a solution to the problem. I downloaded SEUS and used that to update and factory reset my device. First thing I did afterwards was to make sure that I had 30mins for screen off then shut off the slide lock. Now the phone is running Android 4.04 and I did install the sharekm and it works great I'll have to give the dev a good rating. Quite simple to use and the only peev is the overshoot disconnect that happens when you move the mouse too far over the edge. Anyway that is for a review. I haven't done much with it yet and will have to play around some more later on.
It's a pity that I can't unlock the bootloader and flash custom ROMs considering the tutorial for building your own customs specific to this device are available. And that the Flashtool allows you to extract images without having to use Linux commandline (which I am still learning and breaking things more often than not with sudo). That aspect in itself is one more step removed. I have to set up cygwin properly and then I can extract the files properly. I got some errors when trying to do so. Then once i have done that I guess I have a hel of a lot of reading to do.
Thanks for all your help even for the stuff that didn't work it got me reading and learning a few more things than I had erm known before. Have a great day
Related
I have a SE X10i with standard GB 2.3.3.
I have rooted the phone using flashtool I believe and it was all going well.
I then updated Home.apk in system/app with the new one from the X10S (port from XPERIA S) and when I rebooted the phone it just gets to the green Sony Ericsson logo and hangs.
I started to read a few of the 'how to' here, but I'm not clued up enough to know what my options are and what I should or should do.
I was VERY stupid to think I could just update my home.apk without really understanding what I was do.
So I'm humbly asking how I could recover the SE X10i or how I could reflash a new ROM.
I tried just reinstalling using PC Companion, but the USB connection can not be established.
I thus thought, best ask for some guidance before I make a bad thing worse.
I hope it's OK to ask this question here.
Thank you VERY much for any help.
well the first thing you can try is SEUS
this is used when PC companion fails.
http://sony-ericsson-update-service.en.uptodown.com/
it reflashes sony ericssons stock rom.
and if this fails then i have a question to answer.
what did you do other then rooting your phone ?
be exact and share all info regarding what and how the more info the more people will be able to help
I now see my phone has 'booted'.
I had it connect via USB to my notebook and as it was 'hung' booting I just left it.
The lock screen was displayed and when I unlocked it, the screen was 'black', however the notification bar at the top is visible and effectively active,
It has my 3G data disabler (3Gwatchdog) icon, USB debug, USB connect icon, Wifi and battery indicator.
If I pull the slider down I can see the notifications, saying USB connect, Debug enabled etc.
However, the menu or back buttons do nothing and the screen remains black with only the top notification bar visible.
PC companion now see the phone and says the Software is up to date when checked.
There is the fix option available on the PC companion update check 'pop-up'
--------
The Home.apk I installed was the 'seven' screen one.
http://forum.xda-developers.com/showpost.php?p=23129126&postcount=371
I used File explorer to place it in system/app with wr-r-r permission.
I used Titanium backup to 'delete' the Sony Home [2-0-a-0-20] version as I couldn't locate anything home like in system/app to move elsewhere or find any way of locating the source of the file.
I did do a Titanium backup of the file before I deleted it. I'm not sure if the delete retains the backup of the 'home' app file?
http://www.theandroidsoul.com/download-new-sony-ericsson-home-launcher-apk-v2-0-a-0-20/
Is the previous home app I had and have now deleted...Doh!!!
Now probably did another dumb thing, cause the phone 'booted' via USB connection, I thought maybe it'd boot OK albeit slowly normally, but 15minutes later and the Sony Ericsson green logo is still on the screen with nothing visibly happening.
I don't know how long I had it connected via USB before it became 'active' so I can't tell if I should wait longer or if I should attempt some sort of 'fix'/rebuild via PC companion if I can get USB connected again.
Thank you for your help.
[Update] Took about 30minutes, but it showing the lock screen.
Clock in the centre with day/date, unlock or mute sound at bottom and 'standard' notification bar at the top of the screen
Not going to touch it, till I have a plan
well what i understand from the links you gave me is that its simply installed as you would any application.
while the phones running and when pressing home button it would give you the option to go to
A- your 5 page home
B- your 7 page home
and after that tough it doe not mention this
you could i suppose delete the 5 page home.
anyways your scared to tough your phone now huh
from reading your last post i cant seem to find you trying the SEUS option (not pccompanion)
heres a guide!!
http://www.esato.com/board/viewtopic.php?topic=171599
this brings you back to the original software (as you updated to 2.3.3 i believe bin a while )
so all i can say is somewhere something went wrong try your phone now see what its doing etc if its ok (GREAT) if its not try SEUS to get your phone back to the way it was and try again or keep your 5 pages
Was wondering if there was a third way, but I'll get onto a recovery and start over.
I was just using PC Companion as a known reference point to identify the phones possible state of connectivity (or lack there of)
So SEUS, here I come...
Thanks again.
[Update]
All back up and running.
Just doing a few benchmarks on a fresh install while battery recharges and before I 'root' the phone again and reinstall everything.
Next time I'll get a change control approved by mum before I start tinkering
try installing it as a normal app this time and see if you can acces it with your home button instead of replacing
Bjornlindekens said:
try installing it as a normal app this time and see if you can acces it with your home button instead of replacing
Click to expand...
Click to collapse
Nope, too scared.
I have to reinstall cifsmanager, samba filesharing and OpenVPN... so, like I've had enough excitement for one week.
One thing that drove me nuts was (re)rooting the Sony Ericsson XPERIA X10i using Flashtool (like just now). After many false starts on Win7 I found that the USB driver SEMC HSUSB normally fails even using Gordon Gate and etc. As an alternative I used Windows 8 and it 'seems' to install a driver which even asked for the specific model of phone (x10, X10 mini, Arc...etc) and everything worked from then on. I've read(cause I was looking for answers) many queries related to Flashtool and USB SEMC connection drivers, so Windows 8 for some people may be an answer.
But, hay, I've learnt how to crash and rebuild my phone so my fear of the unknown may subside over time.
You wouldnt believe how many times i scratched my head thinking "oh dear you broke it this time for good "
Especially when i booted i got a phone image with a triangle sign!?
But in the end reflashin saved evry time!
Sent from my x10 using xda premium
Hi guys,
please help me.
i'm stucked in MTP mode because I've forgotten my number pin code.
before the touchscreen broke, i've managed to change the USB debugging mode on..but i failed to change the usb connection to storage mode
(because the touchscreen was broken and i had it fixed just recently but i forgot my number pin code).
now i can't enter the boot mode, can't unlock, can't reset the phone.
what shall i do?
I'm not sure if i should help coz it sounds like a question someone with a stolen locked phone would ask...:angel:
Rudjgaard said:
I'm not sure if i should help coz it sounds like a question someone with a stolen locked phone would ask...:angel:
Click to expand...
Click to collapse
well, yeah it sounded like someone just stole a pin coded phone.
but i can show you my receipt and the box and everything that came with the brand new unit. if you would track my records here, you will see that i have been in the sk17 forums
after the touchscreen of the phone broke last May, i've scouted for good repairman but couldn't have enough time since i transferred to a new company. since then, i had hectic work schedule. it's just recently (first week of October), right after the phone's 1year warranty (September30), that I had the chance to get the phone fixed.
i have contacted sony via email and waiting for their reply. see, i still have erratic work schedule these days.
i have posted here my question, since i know that there are a lot of brilliant people who could help me.
if you don't know the answer, it's fine. thank you for bumping my thread. :angel:
Can you still enter flashmode? This should work
Download flashtool and the gingerbread or ice cream sandwich ftf for your device. Go to installation folder of flashtool>drivers and install all drivers for all devices.
Copy the downloaded ftf in the firmware folder.
Launch flashtool, click on the flash > flashmode > select the downloaded ftf > don't exclude anything on the right side > check again that the ftf is for your device (xperia mini pro=sk17a/i) and click ok.
Turn phone off, hold volume down and plug in pc. The green led will light up and it will be flashed automaticly. Don't disconnect while flashing. If it has ended and there are no errors, boot phone up.
Done
Hey Guys,
Really hoping someone can help me out here. I've been trying to root a friend's Xperia U for the past 3 days now, without much luck!
Its on ICS, Firmware ST25a 6.1.1.B.1.10, unlocked bootloader. The two methods are Bin4ry's script and using FlashTool .For starters, USB debugging is enabled.
In both cases, the phone was undetected, even after installing loads of drivers found all over the web. After extensive reading, I came across a suggestion to enable USB tethering, and lo behold! The phone was detected!
"What's the problem then?", you ask?
Well, after following the careful instructions to restore the 'RootME' backup (on the phone), it phone reboots. When it comes back on, the screen is a mess, very dark (similar to a burnt screen) and extremely slow to respond. I read elsewhere that this is quite normal(!) and will be fixed after subsequent reboots.
The problem lies here, as I believe USB tethering is no longer ticked after the reboot, and it needs to be, doesn't it? Both Flashtool and the script wait for the phone to be detected, with no change at all. I somehow manage to navigate to 'Settings', but on trying to access tethering, it always crashes as below:
"Unfortunately settings has stopped"
Ugh.
How do I see the message when the screen is burnt out, you ask?
Pulling down the notification bar lets me see parts of the screen on its way down, and back up
Soooo...
Without USB tethering enabled, rooting does not complete, and I am left with a nearly un-useable device (until a factory reset). My internet speeds are terrible, and I am now in the process of downloading another firmware (6.1.1.b.1.54) in the hopes that it does not need USB tethering enabled to be detected by Flashtool (or Bin4ry's scripts)!
Thoughts? I want this baby rooted and CWM'ed!
Use xperia u toolkit..search in forums.eats very easy to root and do so many other things.i rooted mine using that only.
Sent from my ST25i using xda app-developers app
sanstorm said:
Hey Guys,
Really hoping someone can help me out here. I've been trying to root a friend's Xperia U for the past 3 days now, without much luck!
Its on ICS, Firmware ST25a 6.1.1.B.1.10, unlocked bootloader. The two methods are Bin4ry's script and using FlashTool .For starters, USB debugging is enabled.
In both cases, the phone was undetected, even after installing loads of drivers found all over the web. After extensive reading, I came across a suggestion to enable USB tethering, and lo behold! The phone was detected!
"What's the problem then?", you ask?
Well, after following the careful instructions to restore the 'RootME' backup (on the phone), it phone reboots. When it comes back on, the screen is a mess, very dark (similar to a burnt screen) and extremely slow to respond. I read elsewhere that this is quite normal(!) and will be fixed after subsequent reboots.
The problem lies here, as I believe USB tethering is no longer ticked after the reboot, and it needs to be, doesn't it? Both Flashtool and the script wait for the phone to be detected, with no change at all. I somehow manage to navigate to 'Settings', but on trying to access tethering, it always crashes as below:
"Unfortunately settings has stopped"
Ugh.
How do I see the message when the screen is burnt out, you ask?
Pulling down the notification bar lets me see parts of the screen on its way down, and back up
Soooo...
Without USB tethering enabled, rooting does not complete, and I am left with a nearly un-useable device (until a factory reset). My internet speeds are terrible, and I am now in the process of downloading another firmware (6.1.1.b.1.54) in the hopes that it does not need USB tethering enabled to be detected by Flashtool (or Bin4ry's scripts)!
Thoughts? I want this baby rooted and CWM'ed!
Click to expand...
Click to collapse
hope u have downloaded the new firmware, flash it by flashtool to help u simple there are custom kernal that are pre-rooted and CWM installed (just 10mb in size) you can find them here
http://forum.xda-developers.com/showthread.php?t=2391151
in the android 4.0 section
if u need more help just send me a private message by just cliking my avatar.
smartananallavan said:
hope u have downloaded the new firmware, flash it by flashtool to help u simple there are custom kernal that are pre-rooted and CWM installed (just 10mb in size) you can find them here
http://forum.xda-developers.com/showthread.php?t=2391151
in the android 4.0 section
if u need more help just send me a private message by just cliking my avatar.
Click to expand...
Click to collapse
Macha, thanks for your reply! :good:
I didn't realize this thread was around. I thought it was moved here.
Its all good
Why does Android allow 'tinkerers' like me to tinker?? A little knowledge can be dangerous thing.
Hi.
Ok, so, I've gone and buggered it (I think but certainly hope not).
My new Z2 that I LOVE got some water in it last week. The phone continued to work but somewhat erratically, not responding to the touch screen etc etc. After leaving it for a few days on the window ledge, all signs of water ingress had disappeared and it worked ok. I’m sure the relevance of the water is only that it started me thinking…….maybe its knackered, so starting to ‘play’ isn’t a bad thing. I really doubt the water is an issue here.
Here's where the tinkering starts. I have a N5 which has been on Android L prev for months now and loaded the final build last week. It’s great, but hey, that's for the N5 group i guess.
The point of sharing that is.......even as a complete novice, I have flashed, re flashed and returned to stock my N5 many times and thus I thought......how hard can it be?
In an effort to flash a new Rom (CM11) to the Z2 I have buggered it. So in an effort to be as comprehensive as poss....please don’t ask 'why' to any of this because, to be frank, I'm not sure.........
1. I unlocked the phone (bootloader??) via the Sony website process....request code, get token etc etc........all good
2. I flashed CM11 and 'eventually' got it working. I say eventually because my ADHD means that I (perhaps) wasn’t as diligent with following instructions and it took a couple of attempts. Nonetheless it was working.
3. I saw (the next day) that 4.4.4 was available for Z2 and in conjunction with the camera features that I was missing, I thought I'd flash back to stock to see if 4.4.4 was acceptable. That’s where the fun starts.
4. Through either
a. not following instructions,
b. doing something wrong or
c. just bad luck…..the phone is now (nearly) dead. I say nearly because......
5. When you boot it up, it will.....
a. After ~2sec press on pwr, it will vibrate and show the Sony Xperia screen
b. After ~6 secs the Sony screen disappears and a screen with the following message appears….
“The software update failed. Make sure that your phone is connected to a computer and try again”.
That message is accompanied by a kind of (I guess) Ying Yang type graphic and a warning triangle.c. Then the screen goes off. I assume the phone actually goes off because the only way to revive it is to go back to the pwr button.
6. If I follow the instructions for flashmode, once I connect a cable whilst holding down the ‘vol down’ rocker, the LED flashes red momentarily and then (I’m sure) flashes instantaneously to green before going out and the phone is then dead. I say I’m sure because its so bloody quick its almost indeterminable.
7. If I follow the instructions for fastboot, once I connect a cable whilst holding down the ‘vol up’ rocker, the LED flashes red momentarily and then flashes to blue, at which point it stays blue.
I’ve tried many different threads, tutorials etc and can’t get out of this jam.
a)In flashtool, the phone is simply not recognised.
b) In Emma, the phone is obviously ‘seen’ as I get a message telling me that the phone is locked. Eh? WTF?? How is that??
c) In flash tool, when I try to BLU….I get……
07/014/2014 13:14:27 - ERROR - (Bundle.java:443) - Cannot delete C:\Flashtool\.\firmwares\prepared\boot
d) In flash tool, when I try to flash using the fastboot toolbox (using the reboot via ADB) option….I get……
07/014/2014 13:14:44 - ERROR - (FastBootToolBoxJob.java:74) - This action needs a connected device in ADB mode
e) In flash tool, when I try to flash using the fastboot toolbox (using the reboot via Fastboot) option….I can hear the notifications from my PC that it has rebooted and the blue LED comes back on but that’s it. When I select Kernel to flash……..I haven’t got one (I don’t think).So…..devs…can you help?
I’ve tried to be as comprehensive as poss in my description and If I’m missing something, please point out the error of my ways.
I sooo want my Z2 back and promise I wont tinker again (until next time of course).
Much appreciation in advance of suggestions.
Cheers
Thommo.
In reading (and re-reading this) I wonder if ive answered myself……no kernel (whatever the feck that is)??? If that is the case….which one to flash and how??
I understand the kernel can be mismatched to a ROM and thus f**k things up??
(Edit) Also, I understand you cant flash a kernel without an unlocked bootloader???
I'd like to shed a little light on your situation. Maybe it will help you along.
I am assuming you have a program like Flashtool available and a FTF file of a relevant Sony firmware for your Z2.
The key issue seems to be a little confusion about flash mode and fastboot. On my Xperia Z, I always get a red light and then the LED momentarily flashes the colour green or blue depending on which mode I am entering.
So you shouldn't be alarmed by what your phone is doing.
The key is whether when you connect your phone in flash mode, does Flashtool continue the process and notify you in its log window that it is going through the flashing process?
This may require a little more patience as I believe your issue may just be that you don't think anything is happening when actually something is.
The kernel issue won't apply if you are using a stock FTF Sony firmware. The only consideration is to tick the option "exclude: TA" when you flash. The kernel and software will be included and automatically installed if there is no further underlying issue.
Some attention to detail is necessary and I hope this helps you out.
Good luck!
Sent from my C6603 using XDA Free mobile app
shorinryu said:
I'd like to shed a little light on your situation. Maybe it will help you along.
I am assuming you have a program like Flashtool available and a FTF file of a relevant Sony firmware for your Z2.
Click to expand...
Click to collapse
Yes.
shorinryu said:
The key issue seems to be a little confusion about flash mode and fastboot. On my Xperia Z, I always get a red light and then the LED momentarily flashes the colour green or blue depending on which mode I am entering.
So you shouldn't be alarmed by what your phone is doing.
Click to expand...
Click to collapse
The phone does seem to respond to flashtool commands but im not sure (maybe confused now) as to what to do in what order?
shorinryu said:
The key is whether when you connect your phone in flash mode, does Flashtool continue the process and notify you in its log window that it is going through the flashing process?
This may require a little more patience as I believe your issue may just be that you don't think anything is happening when actually something is.
Click to expand...
Click to collapse
Hey......thanks for helpimg.
I just tried again and yes its responding (i.e. booting using the flashttolbox etc but wont go any further. On the fastboot mode option, it asks what system to flash...when i take that route its now looking for a .sin file but i don't have any only ftf files??
I feel like im close but cant bloody fathom what im doing wrong. I wish someone could draw a picture.
Next suggestion?
Cheers
Thommo
http://forum.xda-developers.com/showthread.php?p=53220435
Here is a recovery guide
This guide should provide all the steps neccisary to recover a bricked device
So......i tried the BLU facility.
It appears the phone is going into flashmode as the waiting for device dialogue dissappears after i follow the instructions (pwr button down etc).
this is the log...
07/026/2014 14:26:39 - ERROR - (X10flash.java:255) - Processing of loader.sin finished with errors.
07/026/2014 14:26:39 - ERROR - (GetULCodeJob.java:137) - Error in processHeader : 6 : The handle is invalid.
Is there a clue on the X10Flash error??
there was (and still is) a X10_V1BLRelock.ftf file in the firmwares folder.
Ha66is said:
So......i tried the BLU facility.
It appears the phone is going into flashmode as the waiting for device dialogue dissappears after i follow the instructions (pwr button down etc).
this is the log...
07/026/2014 14:26:39 - ERROR - (X10flash.java:255) - Processing of loader.sin finished with errors.
07/026/2014 14:26:39 - ERROR - (GetULCodeJob.java:137) - Error in processHeader : 6 : The handle is invalid.
Is there a clue on the X10Flash error??
there was (and still is) a X10_V1BLRelock.ftf file in the firmwares folder.
Click to expand...
Click to collapse
Dear Brother, you're trying to flash a Sony Ericsson Xperia X10 FTF file to a Sony Xperia Z2. Please don't do that. Be aware of the things you're doing, look and read carefully. Raise your awareness.
Obtain a Sony Xperia Z2 4.4.4 FTF file on the internet and flash it. Ignore that X10 FTF.
V4LKyR said:
Dear Brother, you're trying to flash a Sony Ericsson Xperia X10 FTF file to a Sony Xperia Z2. Please don't do that. Be aware of the things you're doing, look and read carefully.
Click to expand...
Click to collapse
Actually.......Im not.........to prove a point, i deleted the X10 ftf from the firmwares folder, uninstalled Flashtool and re-installed. After re-installing the X10 FTF is back in there along with a X10 folder (X10 flasher.lib).
Ha66is said:
Actually.......Im not.........to prove a point, i deleted the X10 ftf from the firmwares folder, uninstalled Flashtool and re-installed. After re-installing the X10 FTF is back in there along with a X10 folder (X10 flasher.lib).
Click to expand...
Click to collapse
I'm sorry but V4LKyR is right, you were trying to flash the X10 bootloader relock ftf file. Please download an ftf (look in the general section for the Z2) and flash that instead.
The X10 bootloader relock ftf and the X10 folder always get installed when installing flashtool. The X10 is a completely different phone from the Z2.
Hello everybody,
I have a big problem because my Sony Xperia Z Ultra C6802 doesn't work anymore and doesn't respond to touch anymore since i flashed a certain twrp-recovery to the recovery-partition with fastboot.
So that's why i'm forced to connect my wired mouse to it to be able to control it as far as that's possible. I tried to flash another twrp-recovery to it but fastboot doesn't work anymore and is broken, or so it seems. In any case it's impossible to use fastboot or adb for that matter because the phone wont boot into the bootloader-mode. So could someone please help me with this issue??!! Before i started to hack my phone it worked perfectly and the display responded normally to touch input. The only thing i can do with it at the moment is boot into twrp and the rom which is Lineage-os 18.1. But even when i'm booted into the rom the display still doesn't respond to touch anymore and i still have to use my connected wired mouse to use it.
I hope to hear from you soon about this!
Kind regards,
Laurens
Bump.
[email protected] said:
Hello everybody,
I have a big problem because my Sony Xperia Z Ultra C6802 doesn't work anymore and doesn't respond to touch anymore since i flashed a certain twrp-recovery to the recovery-partition with fastboot.
So that's why i'm forced to connect my wired mouse to it to be able to control it as far as that's possible. I tried to flash another twrp-recovery to it but fastboot doesn't work anymore and is broken, or so it seems. In any case it's impossible to use fastboot or adb for that matter because the phone wont boot into the bootloader-mode. So could someone please help me with this issue??!! Before i started to hack my phone it worked perfectly and the display responded normally to touch input. The only thing i can do with it at the moment is boot into twrp and the rom which is Lineage-os 18.1. But even when i'm booted into the rom the display still doesn't respond to touch anymore and i still have to use my connected wired mouse to use it.
I hope to hear from you soon about this!
Kind regards,
Laurens
Click to expand...
Click to collapse
Bump
It seems your Z ultra is soft bricked. All you have to do is download "Xperia Companion" software
and press "Software Repair", then check the option "My device cannot be detected or started...", then follow the steps provided.
As a result you will have your zultra with a fresh stock rom (Lollipop) from Sony.
Then, you can custom mod your phone again.
EDIT: don't forget to lock your bootloader before running xperia companion!
xda_user749 said:
It seems your Z ultra is soft bricked. All you have to do is download "Xperia Companion" software
and press "Software Repair", then check the option "My device cannot be detected or started...", then follow the steps provided.
As a result you will have your zultra with a fresh stock rom (Lollipop) from Sony.
Then, you can custom mod your phone again.
EDIT: don't forget to lock your bootloader before running xperia companion!
Click to expand...
Click to collapse
Allright!! Thank you so much for responding to my post!! Finally now i can move on and fix my phone again and start all over again!! : D
xda_user749 said:
It seems your Z ultra is soft bricked. All you have to do is download "Xperia Companion" software
and press "Software Repair", then check the option "My device cannot be detected or started...", then follow the steps provided.
As a result you will have your zultra with a fresh stock rom (Lollipop) from Sony.
Then, you can custom mod your phone again.
EDIT: don't forget to lock your bootloader before running xperia companion!
Click to expand...
Click to collapse
I only have one more question: since i can't get access to the bootloader (fastboot), how do i bypass the problem of having to re-lock the bootloader again with (needed) access to the bootloader and fastboot before continuing with Xperia Companion??
Try This:
- Download FlashTool (I'm using version 0.9.30 and it works on my Zultra)
- Extract it to a folder (eg c:\flashtool)
- Go to C:\Flashtool\drivers and install the drivers (FASTBOOT, FLASHMODE and everything with Zultra... )
- Run C:\Flashtool\FlashTool64.exe, and let it update througth github
- Press the BLU botton, follow the instructions on how to connect your phone, then select the model and press Relock
EDIT: The following approach is the flashmode, so you may not have a problem. Please report here if you finally succeed unbricking your phone...
Good luck
xda_user749 said:
Try This:
- Download FlashTool (I'm using version 0.9.30 and it works on my Zultra)
- Extract it to a folder (eg c:\flashtool)
- Go to C:\Flashtool\drivers and install the drivers (FASTBOOT, FLASHMODE and everything with Zultra... )
- Run C:\Flashtool\FlashTool64.exe, and let it update througth github
- Press the BLU botton, follow the instructions on how to connect your phone, then select the model and press Relock
EDIT: The following approach is the flashmode, so you may not have a problem. Please report here if you finally succeed unbricking your phone...
Good luck
Click to expand...
Click to collapse
Could you please upload Flashtool 0.9.30 somewhere and post the downloadlink here in this thread? Because version 0.9.30 is nowhere to be found when i search for it with Google. Only version 0.9.34 is available from the official Flashtool-website, or can i use that one also?
Edit: well first i tried to run Xperia Companion while my phone was unlocked (just to confirm if it works or not) and it didn't gave me any errors, but now it does give me an error saying it can't continu because my phone is locked and i first have to unlock it again before continuing. Do you have any ideas on how to proceed now?
Ps: also my phone is now dead since i locked it again and doesn't respond to anything except it vibrates shortly after pushing the on-button but nothing appears on screen!
Ps1: It appears so that Xperia Companion probably means with "that my phone is locked" that i have a screenlock which i need to unlock first before proceeding.
And yet another thing happened namely: the program complaints about me not having a working internet-connection which doesn't make any sense since every other device in my house has a good working internet connection! I have included a picture of the error below so you can see what i mean.
Eventually it worked!! after successfully relocking the bootloader my phone was completely dead and only vibrated shortly after pressing the power-button and that was it. But since Flashtool reported that the relocking-procedure was successfully fullfilled, i then carried on with Xperia Companion but this time on my Macbook Air (because of the error i got on Windows, see screenshot).
Finally i managed to let it install the original sofware and this time it completely reanimated my phone again, and even my display returned back to normal again!!
So now i can finally begin all over with installing the latest Lineage version onto the phone, thanks to you!!
Ps: before i forget: i found eventually a Flashtool website which has the version you got (0.9.30) so i downloaded that and used it in the process!!
So i can't express enough how much i appreciate your help and can't thank you enough for all of this!!
Glad you could make it!
This is the standard procedure when things go wrong with custom flashing with any xperia device that becomes completely unresponsive.
Two things:
- version 0.9.30 is what I'm currently using. Most likely the newer versions are working as well.
- To unlock your bootloader again, you only have to press the BLU button in Flash Tool and then UNLOCK.