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.
Related
Hi, everyone I just joined this forum. I have X10i with firmware 2.1. While searching the thread i came acrosss terms like root, xrecovery, flashing, MT, generic etc. Can someone help me out what these terms mean. I wanted to upgrade my phone to gingerbread. Previously I am an iphone user So i am total noob to this OS and the phone
Thanks in advance
good get away from iphone
root--same thing as jailbreak
xrecovery-- a badass tool that lets you flash roms onto your phone.
flashing-- umm... it is like installing a modified version of even the legit version on the device
generic-- A product having no brand name or registered trademark
example= for device there is branded or non branded
branded means that a company like ATT or Rogers approves that firmware or OS version. So when you turn your phone on, you will usually see something related to them. like an animation of the att world
generic--- clean install. no company restrictions. just regular
ok links for all that crap above
2.3.3 firmware (does not matter if you download x10a or x10i)
Generic-----
http://forum.xda-developers.com/showthread.php?t=936733
do yourself a favor and read
http://forum.xda-developers.com/showthread.php?t=936733 before and download the program WINDOWS only
Thanks for your help. I am going to upgrade my phone soon so is their any problem in doing so and by the way should i just use the SEUS or flash tool
angel eyes said:
Thanks for your help. I am going to upgrade my phone soon so is their any problem in doing so and by the way should i just use the SEUS or flash tool
Click to expand...
Click to collapse
Either will do.
ok thanks for the advice going for the upgrade now lets hope everything goes smoothly will post the results
Now this is the end result of upgrading my phone I used SEUS to upgrade my X10i the phone went into flash mode and the SEUS detect that new software is available soit downloads it but when it comes to installing it stopped at about 15% and said that updATE cannot continue check battary is fully charged and than again try. As far is i remember phone was fully charged when i put it for update now what should i do. The phone doesnt restarts now and when I power up my phone only th egreen led blinks and it vibrates for split second than nothing I waited for it but the phone is not responding what should i do now
HELP NEEDED
to tell you the truth i dont know what SEUS is
i think it is for drivers or something but you should use PC comapanion for drivers
ok
use flashtool in the first link i gave you and download one of the 2.3.3 files
or use a 2.3.3 rom
and flash the sucker on
it should work
Try flashtool if doesn't work let your phone on charge for 1 hour and take it off try again whit seus should be good to go
Sent from my X10i using xda premium
Thanks for the help guys now i have downlaoded flashtool 0.2.8, 2.9,3.0 i also downloaded the firmware and did all the steps according to the toturiol but that what happens it detect the phone in flash mode the flashing starts but at fato1.sin it gives as error message "error flashing abort". I also tried other firmwares but the same error.
Now guys I think I am great trouble so need help
What to do next
And I used the desktop charger to charge the battery for whole two houra but SEUS gives the same error plus pc companion gives error as well i am stuck
Go to pc application manager, close seus and pc companion. Try flashtool tool once again http://forum.xda-developers.com/showthread.php?t=928343. I hope this work for you.
Sent from my SO-01C using Tapatalk
Ok i will try that one too thanks alot lets see wat happens
ok tried that too nu luck
What should i Do now One thing more i was goignaround the threads looking for solution So in one thread it said that firmware can ber installed through flash tool 0.2.5
I tried that too and amazingly the flashing goes all the way to the end on 0.2.5 in the end i get the msg that flashing complete and remove the phone but when i remove the phone and turn it on it just vibrates and small blip of green flash led than nothing
What could be the problem
1. Download Flashtool from
http://doomlord.sylvester20007.com/x10/x10_gb/FlashTool_0.2.9.1-GBready_root_xRec.exe
2. Download the generic 2.3 ROM of your choice
http://forum.xda-developers.com/showpost.php?p=11038646&postcount=1
Personally I would get the Global version unless you can find your country specific one.
Global version download - http://www.multiupload.com/JEXUAHAZTL
3.
a) connect your phone to your PC, make sure it installs the drivers (if your Sony software is working it is fine)
b) Extract Flashtool into a directory you know
c) Extract the firmware file you downloaded. And move the ftf file into the "firmware" directory of Flashtool
d) Make sure your phone is not connected to the PC and is off.
e) Run Flashtool, click on Flash and select the firmware you have just downloaded.
f) It will give you the same instruction - holding the "back" key, (phone still off) connect it to the PC. If you did this correctly, the light will be green and it will start flashing your phone.
g) After it is completed, reboot your phone once or twice and check that it is working.
4. Installing xrecovery and rooting refer to instructions (you already have all the files from when you download in step 1)
http://forum.xda-developers.com/showthread.php?t=1196808
Let me know when you have completed the steps above.
Thanks for advice downloading it now and going to try and will let now about the results
sasukewa said:
1. Download Flashtool from
http://doomlord.sylvester20007.com/x10/x10_gb/FlashTool_0.2.9.1-GBready_root_xRec.exe
2. Download the generic 2.3 ROM of your choice
http://forum.xda-developers.com/showpost.php?p=11038646&postcount=1
Personally I would get the Global version unless you can find your country specific one.
Global version download - http://www.multiupload.com/JEXUAHAZTL
3.
a) connect your phone to your PC, make sure it installs the drivers (if your Sony software is working it is fine)
b) Extract Flashtool into a directory you know
c) Extract the firmware file you downloaded. And move the ftf file into the "firmware" directory of Flashtool
d) Make sure your phone is not connected to the PC and is off.
e) Run Flashtool, click on Flash and select the firmware you have just downloaded.
f) It will give you the same instruction - holding the "back" key, (phone still off) connect it to the PC. If you did this correctly, the light will be green and it will start flashing your phone.
g) After it is completed, reboot your phone once or twice and check that it is working.
4. Installing xrecovery and rooting refer to instructions (you already have all the files from when you download in step 1)
http://forum.xda-developers.com/showthread.php?t=1196808
Let me know when you have completed the steps above.
Click to expand...
Click to collapse
I have done it as adviced but no luck flashing aborts in the middle and giving error message now wehat should i do
Do you have the new flash tool?
angel eyes said:
I have done it as adviced but no luck flashing aborts in the middle and giving error message now wehat should i do
Click to expand...
Click to collapse
Can u do a screen shot or tell us what the error message is?
Thx.
Dark Nightmare said:
Do you have the new flash tool?
Click to expand...
Click to collapse
I have flash tool 0.2.5,0.2.8,0.2.9,0.3.0
Have tried them all only 0.2.5 goes all the way to the end but when i turn on the phone it only virbrates and green led flashes for sec than nothing
When you reboot is there anything showing on the screen? Sony logo...anything? If yes, wait it can take a long time for a new rom to install. If no, I think you need to revert back to the 2.1 rom, root and install busybox, superuser, and xrecovery. once thats done you can backup your rom and data so you don't get stuck updating or if you have trouble with a custom rom etc. Also I think your battery stats should be wiped using xrecovery, it sounds like SEUS checked this and the file said your battery was too low to continue the update. Here is a good place to start.
http://forum.xda-developers.com/showthread.php?t=928343&highlight=flashtool+for+noobs
Here is a video on youtube that may help too:http://www.youtube.com/watch?v=HmX-IYNYqL8
Hope this helps you, Good Luck.
angel eyes said:
I have flash tool 0.2.5,0.2.8,0.2.9,0.3.0
Have tried them all only 0.2.5 goes all the way to the end but when i turn on the phone it only virbrates and green led flashes for sec than nothing
Click to expand...
Click to collapse
Try taking the battery out and then try flashing again. Which ftf file are you flashing or selecting in the flash program. You need to use at least a 0.2.9 version of the flashtool.... if you use 0.2.5 start with the 2.1.54 ROM first.
Hello XDA members
2 weeks ago i bought a brand new Neo V and fully updated it from SEUS
1 week ago i started reading your forums [facepalm]
Yesterday i followed a series of tutorials on the Neo V Development forum and i managed to brick my phone [facewall!!!]
What i did :
1) Download lots of stuff!!!
a) .42 ftf file from here : http://forum.xda-developers.com/showpost.php?p=19808360&postcount=3
b) flashtool from it's original website
c) DoomKernel's rooting script
d) CWM script from here : http://forum.xda-developers.com/showpost.php?p=19733978&postcount=1 (the 1st way)
e) S1tool from here : http://forum.xda-developers.com/showpost.php?p=18013064&postcount=44
2) Use them ALL!!!
a) Install and extract where necessary
b) put .42 in C:\flashtool\firmware
c) put everything else in C:\SETools\ to act tidy
3) Feel like McGuyver!
a) used needle & wire to unlock bootloader with s1tool [success]
4) Take the big step!
a) flash .42 firmware with flashtool [all OK]
phone took it's time to reboot, scared me to death! at least 4 full minutes :/
b) use flashtool to root from the Advanced>Root>ZergRush menu [Fail]
it seems flashtool failed after first part.
c) used DoomKernel's script and rooted phone [all OK]
d) reboot and enjoy! [all OK]
.42 firmware was ok, root ok, boot was slow.. other than that everything worked. (except market, could not download anything!)
e) used Upgrade Service from phone menu and found .62 OTA upgrade. [Failed]
phone downloaded the new firmware, i pressed install, that was it.
And thus my Neo V rebooted to complete the upgrade to .62
The upgrade was never completed, the phone never turned on again.
No SE logo, no led, no nothing!
Everytime i press the power button nothing happens, if i keep it pressed for some time the led flashes green every second.
Everytime i connect it to the PC usb it goes to flash mode on it's own, no back key pressed.
When plugged on charger led flashes green every second.
Last thing i tried was to reflash it (since it went on flashmode) with .42 again.
Nothing there
Still, i would like to see it alive once more since 200 euro for a green led is not really a bargain
Any help appreciated!!
Ok if the pc recognizes it you should be able to resurrect it with pccompanion, seus or wotan client
Sent from my MT11i using Tapatalk
Will try, though phone is not really recognised..
it functions only as when turned off and pressing back button while connecting to pc usb.
EDIT : Installed SEUS again and tried to do an upgrade (only option available through support zone)
Failed first couple of times, then it popped up a new window asking to repair since update is not working.
Asked me phone model and downloading ATM, will report soon
EDIT 2 : Nothing with Pc Companion or SEUS. It reflashed the phone with .62 firmware but the phone is in the same state.
About Wotan Client, i would love to try it but i have no idea how to install it or run it, it asks for credits and i don't think reflashing will help in this case.
wotan flashing is free bro, just download their client and follow steps most probably u will get ur fone back to ur life. best of luck !
Just a thought, the phone acts as if the back button is constantly pressed and i find that VERY weird..
Also, SEUS discovers the phone as "Sony / Sony Ericsson" (?), is it possible that this has to do with the s1tool driver i installed before while unlocking the bootloader?
wow, thats what i call entire history of your phone
anw you experienced OTA brick. because you have unlocked bootloader.
strange, some people get brick some don't, with un-official(s1tool) method.
but with official, everyone get brick.
Madfysh said:
wow, thats what i call entire history of your phone
Click to expand...
Click to collapse
Thanx
I think asking people to help you requires you to help them too so yes, history is all i could do!
Madfysh said:
anw you experienced OTA brick. because you have unlocked bootloader.
Click to expand...
Click to collapse
OTA brick? The tutorials i followed requested me to upgrade with OTA to have .62 with root. Where they wrong?
Dodo_the_Bird said:
Thanx
I think asking people to help you requires you to help them too so yes, history is all i could do!
Click to expand...
Click to collapse
wow, if only more people would br like you
Dodo_the_Bird said:
OTA brick? The tutorials i followed requested me to upgrade with OTA to have .62 with root. Where they wrong?
Click to expand...
Click to collapse
they werent wrong, but if I think on which tutorial you mean, it says its for people with locked bootloader.
now when you have unlocked bl, your life is easier
you can simply use custom kernel which have root included in itself
go to dev section, you can use galaxian or bbooff kernel.
while you are there check sticky threads to see how to flash kernel.
after you read those, ask if you have any question.
---------- Post added at 12:55 AM ---------- Previous post was at 12:52 AM ----------
http://forum.xda-developers.com/showthread.php?t=1496102
http://forum.xda-developers.com/showthread.php?t=1520516
Thank you all SOOOOOO much!!!
Wotan worked, my phone is up and running on .42!!!
So now about tweaking a bit, those kernels support official roms only,
if i wanted to go for something more goodlooking, faster, nicer.. what would you suggest?
No, those kernels arent only for official rom's.
And about custom roms, I'm not the one to talk about it much, as I'm not so much into custom roms dont have enough time to test them.
so you will need to go trough development section and find something you like. remember you can also look in neo section, most of the roms can work on your phone with minor modifications.
also remember, first read then install
So.. i managed to have a working phone and now i am trying to flash galaxian.
i went on cmd, started fastboot with appropriate command and plugged in phone pressing the menu button.
Now in device manager i can see "S1boot Fastboot" and it is not recognised, what am i suppossed to do????
-turn off your phone.
-hold menu key(the right one )
-connect cable
-you should see blue light on led on the side, do you see it?
-go to folder where you have fastboot.exe file
-hold shift key and right-click of mouse anywhere in that folder except on files
-sellect start comandprompt here(or something like that)
- type fastboot devices
-tell if it says something.
Seems like you didn´t install drivers for fastboot...
i thought they are included in adb drivers !?
Well i have installed the whole android sdk with it´s drivers.
As long as it is unrecognized in Windows (no drivers installed) S1Tool has no Chance to detect it
Dodo_the_Bird said:
So.. i managed to have a working phone and now i am trying to flash galaxian.
i went on cmd, started fastboot with appropriate command and plugged in phone pressing the menu button.
Now in device manager i can see "S1boot Fastboot" and it is not recognised, what am i suppossed to do????
Click to expand...
Click to collapse
u havent installed the correct drivers, connect the phone again in fastboot mode, go to device manager, select s1tool fastboot, click update driver, browse for it manually and point it to the the folder in which you have fastboot, done.
Wow! Wotan client can unbrick a phone that bricked with OTA?
Sent from my MT11i using XDA
If you dont want to brick phone with new custom kernel, use ,,hotboot,, function.
That should boot phone with new kernel one time.
If you dont like kernel, just reboot your phone
Sorry for English.
talk about good memory i pity u LoL btw good luck on flashing ur phone and yeah i brick my neo a while back and have to search on google for 6 hrs then fix my neo for half a day thats 12hrs in real life now im happy that im d only in my family tree and clasm8 know how to flash a brick phone hell yeah im proud of it anyways gudluck
Sent from my MT15i using xda premium
soybi said:
Wow! Wotan client can unbrick a phone that bricked with OTA?
Sent from my MT11i using XDA
Click to expand...
Click to collapse
Yep
I hit the level 100 brick twice or thrice
Wotan server really helps
I bricked my phone yesterday after doing OTA( bootloader unlocked by testpoint method)...wotan server got it back alive and kicking
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
Okay, so I waited patiently for Lollipop to drop on the Z Ultra C6833 in Singapore -- but apparently this is almost the only country which will not be getting the OTA (I can't even get them to answer on Twitter or FB whether this is true). So, I finally followed Sony's instructions to unlock the bootloader. That succeeded. But then I was presented with a language-selection screen after the subsequent boot which I wasn't expecting, and since I thought I just wanted to just go down into recovery and not set up a refresh ROM, I powered off the device without proceeding through the language selection screen.
Apparently, that was a bad call because I've been in a bootloop since then which triggers after a freeze in the swishy boot animation. I flashed the TWRP recovery image I found on these forums, but no go. The volume up/down tricks have never put me into a recovery environment, and the only thing I can succeed in doing still is putting it into fastboot. Sony PC Companion's recovery process won't complete because it detects foreign software (probably the TWRP recovery, right? -- but where do I get stock recovery, and would that even work anyway? And Emma let me in once, but subsequently refuses to respond to the supplied configuration INI file (I'll try to fully reinstall this thing later).
I love this phone. Best phone I've ever had. My plan is up and I *could* get a new phone, but I don't want to move on! I want my Z Ultra. So, someone hold my hand, please. I am even willing to pay a bounty (via PayPal) for a live chat if that is what it takes to get someone knowledgeable to help me in a timely fashion. I live in Singapore (UTC+8), and I do biphasic sleeping, so I'll also be awake between 1:30am and 4:00am my time. Thanks in advance for **any kind of help!**
Sincerely,
Hopeful and anxious expat in Singapore
Edit: I will pay $60 USD by PayPal to the individual who can provide a productive resolution (preferably write here and be available over chat so I can learn from you -- PM me for Hangouts, Skype, VSee, or Firefox Hello contact details). A "productive resolution" does not mean necessarily that we will fix my phone. It may mean that we conclude definitively that we can't. I will take this thing into the Sony Service Centre and give them my money if I have to, but I'd rather give it to one of you fine folks. I only want to give a few more hours to this. I've already been phoneless for two days.
New information in the continuing saga
Reinstalling Emma didn't help, nor did putting customization.ini in creative locations or pasting the developer mode line from that INI file into other INI files within the Emma directories. So I gave up on Emma until I can get to another computer.
After a user kindly uploaded this SIN file (http://forum.xda-developers.com/xperia-z-ultra/general/bootloader-devices-real-recovery-t3117566) to a fileshare for me, I figured out (here https://android.stackexchange.com/questions/65058/why-custom-roms-are-zip-filed-than-made-as-ftf) that "FlashTool" is not the same as Sony's "flashtool" Emma, so I installed it. It wanted me to put the phone in flashmode -- so I held volume down while plugging in the cable, which never before displayed anything different on the screen, nor a green LED which I've read elsewhere I should be seeing (e.g. http://www.theandroidsoul.com/sony-xperia-z-ultra-flash-mode-51769/). But despite the lack of visual clues, FlashTool told me it connected to flashmode and the flash succeeded. It didn't seem to help at all, though, as I still get the bootloop just as before and I still can't access a recovery mode.
That means that I can apparently get into both fastboot and flashmode, which I wanted to make special note of. Is it possible to access ADB while the phone is powered off?
just download flashtool, install driver in included in flashtool folder.
download also any FTF, generic zultra, dont care if 3g or lte.
flash it, should resolve the issue.
in flashtool, make sure you dont touch and leave the flash option as default. it will wipe your data, cache and everything.
to be safe, remove sim and sdcard.
More information...
curiouso9 said:
just download flashtool, install driver in included in flashtool folder.
download also any FTF, generic zultra, dont care if 3g or lte.
flash it, should resolve the issue.
in flashtool, make sure you dont touch and leave the flash option as default. it will wipe your data, cache and everything.
to be safe, remove sim and sdcard.
Click to expand...
Click to collapse
None of the supplied drivers match the "S1Boot Fastboot" device which comes up in my Device Manager. Also, none of the updated FlashTool Xperia Driver Pack match (http://forum.xda-developers.com/showthread.php?t=2635830), nor the drivers on SonyMobile.com, nor the drivers which come with Sony PC Companion. I didn't have this problem on my other Windows 10 machine, but just in case that is an issue, I'm downloading the Android SDK 1.2.1.1 Beta to see if I get any mileage out of that.
I attempted to flash the FTF supplied here (http://forum.xda-developers.com/showpost.php?p=60958777&postcount=3) but I got the following messages:
INFO - Opening device for R/W
INFO - Start Flashing
INFO - Checking header
ERROR - Processing of loader.sin finished with errors.
INFO - Ending flash session
ERROR -
ERROR - Error flashing. Aborted
INFO - Device connected in flash mode
Click to expand...
Click to collapse
Then I used XperiFirm to download my original .108 firmware and attempted to flash it but got the same errors as above.
Download flashtool
I assume you're on windows 8.1/8 you have to disable driver signature enforcement. Then install the drivers than flashtool will detect your phone.
Flash ftf
You will need to re-root, and you can unlock the bootloader.. After that flash away. Remember to install recovery and back up ta. I'm a noob at this and did it for the first time a few weeks ago, so I know you can do it.
Rockin' and rollin'
RealityFails said:
I assume you're on windows 8.1/8 you have to disable driver signature enforcement. Then install the drivers than flashtool will detect your phone.
Click to expand...
Click to collapse
I'm on Windows 10 -- I wasn't getting any errors, so DSE didn't even occur to me. I disabled it and was able to re-flash stock. Still, I struggled with getting a recovery installed, but after several attempts, and started from scratch a few times, one of them finally stuck. After that, I installed a custom ROM and things are running perfectly.
Thanks!
David
mypetocean said:
I'm on Windows 10 -- I wasn't getting any errors, so DSE didn't even occur to me. I disabled it and was able to re-flash stock. Still, I struggled with getting a recovery installed, but after several attempts, and started from scratch a few times, one of them finally stuck. After that, I installed a custom ROM and things are running perfectly.
Thanks!
David
Click to expand...
Click to collapse
Download rashr and it will have recoveries for you
Disappointment with the Service Center
By the way, when I decided I had been too long without an operating phone (before I got the DSE tip), I took the phone to a Sony Mobile Service Center and had them diagnose it. They concluded that there was a hardware failure rather than a software failure (which would require some 300 SGD to repair). I declined, returned to the office, saw the message about DSE, and was immediately successful in reflashing stock. I took it back to the Sony Mobile Service Center and had them confirm that there was in fact no hardware issue -- and that their diagnosis was incorrect. Thanks for the help folks!
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.