I updated my Xperia S to the latest version and I decided to try out the new feature-unlocking via face recognition. The problem arose at the beginning of the code, which I gave as an alternative way to unlock did not work. After a few hoursthe application responsible for face recognition also stopped working. And there was a really big problem: I can not in any way unlock the screen, because the code does not work, so I can not hook up the phone to the computer completely, because it requires unlocking the screen. Do you know what I can do now to be able to fully use the phone? Any entry in Safe Mode of FastBoot Mode did not work. Flashtool does not recognize the phone.
Hold volume up and power button to shut it down? Then re flash
Sent from my SeXperia S via Tapatalk 2
do you have unlocked Bootloader? if not you can use the Update Service and reinstal the firmware and everything should be OK ( whit the risk of losing ur data and apps) just like a brand new phone, you mention that you have the lastest firmware so the Update Service will tell u that you already have it, just ignore it and choose to update anyway.
if yout bootloader is unlocked you can relock it and then use the Update Service.
hope to help you
for relocking BL
http://forum.xda-developers.com/showthread.php?t=1527159
Related
Hi!
I'm sorry if I posted in the wrong topic.
Yesterday I used this: (http://forum.xda-developers.com/showthread.php?t=1320350) to root my SE Xperia Mini Pro.
The rooting process was ok and afterwards the phone was rooted.
Then I wanted to connect the phone to my PC, but
- it was not recognized (the phone by the [any] PC) in media transfer mode
- there was no lock screen (except before SIM unlocking on start)
- can't receive or make calls (incoming and outgoing calls are "Disabled" and it can't be changed [asks for password, but says "Network or SIM card error"]), I tried another phone and calls work.
I used the unrooting script, but nothing changed.
Then I downloaded a firmware I found on this forum (SE FW: 4.0.A.2.368), the media transfer mode and the lock screen worked, but not the calls. After that I applied the T-Mobile 2.3.4 software from my PC, but it's still the same.
Could anyone please tell me what I have to do?
Thanks in advance.
I think flashing a firmware will restore a rooted phone to his original state...
Maybe it has something to do with unlocking the boot loader?
http://unlockbootloader.sonyericsson.com/
My experience is that,
no matter how you mess with your SK17
I.e. bad boot loader, unplug while flashing, Relock bootloader fail unbootable bootloader etc etc,
Wotan Server brings everything work again.
Run Wotan Server, press the Volume down button (or Up i forgot), connect the USB cable, follow step by step to flash the newest version firmware.
And there you go.
Then root your phone again.
Thats what I did for many times. No panic. Seems our phone would never brick. LOL
*Sorry for bad English. I am not EFL speaker.
RE : bad behavior after Easy root toolkit
me too.. but the problem is the problem is the GPS is not working..
when i use foursquare the GPS is detected as inactive
can someone tell me what's wrong with my phone?
*sorry for the spoiled english
Phone: Live with walkman
For a while i have wanted to unlock my bootloader but i cant.
I have found a thread where you can unlock your phone using the test point method.
Using this tutorial - HERE
I have some questions
Can i use this method if unlocking the bootloader is not allowed?
Is there such thing as bricking? If i do it wrong will it brick my phone?
Will it effect my INSURANCE (not warranty)?
I have no experience over unlocking via test point method, so I am unable to help with it.
There is no such thing as bricking, although you can get your phone bricked, if you try to update your phone firmware over the air(3G or WiFi), while having unlocked bootloader.
But don't worry about that, chance to make it completely bricked is quite low, if you know, what you are doing.
About the insurance, check your contract details, can't help with that.
Jhawsh said:
Phone: Live with walkman
For a while i have wanted to unlock my bootloader but i cant.
I have found a thread where you can unlock your phone using the test point method.
Using this tutorial - HERE
I have some questions
Can i use this method if unlocking the bootloader is not allowed?
Is there such thing as bricking? If i do it wrong will it brick my phone?
Will it effect my INSURANCE (not warranty)?
Click to expand...
Click to collapse
About the bootloader:
The s1tool method might work even if the phone is branded but if you want to unlock the boot loader to flash custom kernels and roms you will need to enter to fast boot mode which is disabled in all the branded phones that I know of, you can try to enter the phone in fastboot mode turning it of and connecting the USB cable to the PC and the phone holding down the volume up key, if the notification led turn on blue then you can flash custom kernels and rooms once the bootloader is unlocked if not then you will need to pay to unlock it if that is what you want.
About the brick and the insurance the answer was given in the previous post.
Cheers!!
If i get unlocked will it also allow me to unlock the bootloader?
After some searching.
If your phone has SIM-lock(locked to a specific network), you cannot unlock the bootloader. The only way currently is to pay some money and it will remove SIM-lock and unlock bootloader also.
Can't remember the provider exactly.
I have been trying for two days now to unlock the bootloader on a friend's Live with Walkman (Wt19i) with little success.
The phone came with firmware 4.0.2.A.0.58 and is branded so in the *#*#7378423#*#* /Service info/Configuration menu, the rooting status is :
Bootloader unlock allowed: No
Rooting was easy, thanks DoomLord.
Next is unlock bootloader. I tried to do this via the s1tool method because the official Sony method was a no-go because of branding.
The s1tool method seemed like it would work but then I read that it also doesn't work on branded phones.
I attempted it anyway - the result was no change whatsoever in the phone's bootloader status.
Can I unlock the bootloader without having to pay someone to do it?
The s1tool method might work even if the phone is branded but if you want to unlock the boot loader to flash custom kernels and roms you will need to enter to fast boot mode which is disabled in all the branded phones that I know of, you can try to enter the phone in fastboot mode turning it of and connecting the USB cable to the PC and the phone holding down the volume up key, if the notification led turn on blue then you can flash custom kernels and rooms once the bootloader is unlocked if not then you will need to pay to unlock it if that is what you or your friend wants.
Hope it's helpful!!
Thanks for your reply, very helpful indeed.
I will see if I can boot into that mode when I get back home and at least then I'll know for sure.
It would be ever-so-nice if I could unlock this for her without having to pay money for it. (She won it in a competition that she only entered because her iPhone died recently - but the Live WT19i is locked to the wrong network)
Max-E-Moose said:
Thanks for your reply, very helpful indeed.
I will see if I can boot into that mode when I get back home and at least then I'll know for sure.
It would be ever-so-nice if I could unlock this for her without having to pay money for it. (She won it in a competition that she only entered because her iPhone died recently - but the Live WT19i is locked to the wrong network)
Click to expand...
Click to collapse
Well actually for a sim unlock at this moment you will need to pay for, there's no way to unlock the sim for free. Unlocking the bootloader it's a different matter than the sim. I didn't mention it because you were asking about the boot loader sorry.
And I stupidly assumed unlocking the bootloader would allow me to unlock the SIM lock/branding.
Thanks again for the help, I'll just tell her she has to pony up the dough if she wants to use it on her network.
Hi I've tried searching about quite a bit but can't seem to find the correct solution.
I've had the bootloader unlocked once by following DoomLords instrucions but locked it as an upgrade popped up on my pc companion, now I can't seem to unlock it again.
I've followed the same process as before, even through the sony bootloader unlock site (this gave me the same unlock key as before) I've attached my error from the command prompt screen.
Anyone??
the screenshot is not readable.
maybe you forgot to remove the last number form the unlock key.
or flash a firmware first then try again
Sorry here's another screen.
I tried to re unlock the bootloader after an update via pc companion, it didn't work then.
I've now flashed ICS onto the phone with flash tool and unlocking the bootloader still doesn't work.
I've tried taking the last digit off the unlock code, with no luck!
Random post to keep the thread alive, hopefully someone will know whats up
Last try, anyone?
You're not using 0xFFFFFFF as the key are you?
No definitely not. That was the error the 2nd time round trying.....
Hi guys, so I seem to have scewed up my phone quite badly. I tried to deodex running the new nougat firmware (with drm-fix and ric-off) by flashing a zip in the nougat firmware thread. Somehow I ended up with not being able to fastboot anymore.
I found out that my bootloader seems to be locked again. Thus I am not able to approach the fastboot mode, but failed to do any flash, as it says [FAILED (remote: not allowed)].
I checked the service menu and found the [Bootloader unlock allowed:no] and [Remote Lock State: Locked] after reflashing the nougat firmware.
So I wanted to unlock the device, how ever I ended up with flashing back to Lollipop and the device boots and then power off after a few seconds of use.
Could this due to "remote lock state: not allowed"?
Try relocking via flashtool?
So. Tried to lock and relock via flashtool. Checked drivers which are working fine.
I was trying to relock and then unlock again using flashtool after updating to .305 Marshmallow firmware . However this does nothing to the bootloader states. The weird thing is that there are no errors showing up in flashtool when unlocking/relocking. I can't even unlock via OEM because when I tick OEM unlock in the developer options this doesn't do any change (Rooting status: Bootloader unlock allowed : No, Remote Lock State: Locked). My DRM keys are gone as well. However I do have a TA Backup but can't restore because after downgrading to lollipop the device shuts down after 30 seconds.
I'm really annoyed because I bought the device with an locked bootloader (without carrier costumizations) and unlocked it via OEM unlock then updated to . Is there any chance to unlock the device again? Restore TA? Any recommendations what I could have done wrong would be helpful.
iArvee said:
Try relocking via flashtool?
Click to expand...
Click to collapse
[solved ] Bootloader is now sucessfully relocked andBootloader states are back to [Bootloader unlock allowed: Yes] and [Remote Lock State: UnLocked].
I need to mention that I bought a phone without carrier lock with [Bootloader unlock allowed: Yes].
So, for anyone who is interested or might face the issue in the future, here's what I did.
You will need your backed up TA-Partition-Image to restore via iovyroot:
1. Downgrade to Lollipop (32.0.A.6.200 / R2B (STOREFRONT GENERIC)) using Flashtool .
->Therfore select/tick everything in the wipe section when selecting the Lollipop-tft
2. Unmount your SIM, reboot the device
3. Skip everything on the welcome/configuration screen as fast as you can to get beyond the Android configuration screen
(skip wif config, Google-Account setup, untick myXperia services! etc.)
The phone might power off only after a few seconds because of the downgrade. So be fast!!!
4. Once you end up on the home screen, unlock developer options, and activate ADB debugging, grant ADB access (check via cmd: fastboot devices)
again: be fast! --> Don't worry if the phone shuts down again. Just reboot if you were not fast enough.
5. Download iovy.root ( iovy.root. Place TA-backup.img in the iovyroot-folder.
Then I modified "tarestore. bat" to save some time regarding the shutdowns. I used notepad++:
...
set response=
set /p response=Type "y" if you want to restore this file:
if "%response%" == "y" (
echo Starting restore
echo.
adb push "root/iovyroot" "/data/local/tmp/iovyroot" > NUL 2> NUL
adb push "root/restore.sh" "/data/local/tmp/restore.sh" > NUL 2> NUL
...
5. Run CMD as admin. CD to Iovyroot folder.
Restore using tarestore.bat (tarestore.bat TA-2016-xxx.img) as soon as your device boots up to home screen and seems to be connected as ADB device.
( I checked this by running the windows device manager simultaniously)
Wait to end the process.
-->When the restore was sucessfull, the device shouldn't shutdown again.
6. Reboot. Your bootloader is now locked again (but able to unlock via OEM unlock). DRM keys/functionality is restored.
I have the same problem (after i had nougat working incl drm fix and root, also the deodex, tried flashing lower ftf files too when i got this problem, noticed the rebooting, which it does not do at 305 kernel or higher..
I would have hope in your solution, if I could find my ta backups (i have from some other phones, this one, may have been on a crashed laptop, already searched through old hdds)
Could this be because of fastboot flash recovery twrp.img (cause that is something i never done before on the z5c.)
If anyone has a solution other than restoring the ta partition, i would like to know. Because i am very uncertain that i can find those files again...
Same case here z5c unlocked since +/- 1 year and I don't have any TAbackup too
I will try to downgrade to .200 But with bootloader unlock allowed : no ... I don't have much hope
edit : no chance, I tried .200 but without tabackup, I can't do nothing
When I faced this problem I noticed it happened because I wiped TA options with Flashtool. Never do that if you don't want to lose TA partition and all other things connected to it. I could fix it only by flashing TA backup even though I hadn't the timing issue zegovernator had for flashing back TA.
I actually wonder why Flashtool allows to wipe these critical partitions/options
ric69 said:
Same case here z5c unlocked since +/- 1 year and I don't have any TAbackup too
I will try to downgrade to .200 But with bootloader unlock allowed : no ... I don't have much hope
edit : no chance, I tried .200 but without tabackup, I can't do nothing
Click to expand...
Click to collapse
I'm sorry for you. I would recommend updating back to MM since LP gives you immediate shut downs when recognising that your TA is lost/wiped. It's sometime a pain in the ass that stuff gets posted before testing. Nonetheless, you could still try to send in your device back to Sony Costumer Service if you are under warranty (after flashing .200, say that it is "broken" and keeps crashing). However, I would not trust on them sending you a new device.
jutphaas said:
I have the same problem (after i had nougat working incl drm fix and root, also the deodex, tried flashing lower ftf files too when i got this problem, noticed the rebooting, which it does not do at 305 kernel or higher..
I would have hope in your solution, if I could find my ta backups (i have from some other phones, this one, may have been on a crashed laptop, already searched through old hdds)
Could this be because of fastboot flash recovery twrp.img (cause that is something i never done before on the z5c.)
If anyone has a solution other than restoring the ta partition, i would like to know. Because i am very uncertain that i can find those files again...
Click to expand...
Click to collapse
I sorry to say that, but if you lost your TA-backup or didn't even back it up before unlocking the bootloader there is no hope at the moment. You simply can't fastboot because of the Remote State: Locked. It keeps you from accessing the bootloader.
I found my iovyroot TA-backup.img file, I did have a .200 storefront ftf and tried it on that one, which was very anoying as it wants to start a demo , i found an other .200 ftf online which I tried, and the iovyroot seems to work, at that time no reboot, in service menu, the drm keys now seem fine there, Bootloader unlock allowed : No, Remote Lock State: unLocked , fastboot boot or oem unlock still seemed not working well i think that is what it said, (flashtool unlock always seems to, i did try) now i flash a new ftf and try my luck there with the unlock status.
flashing ftf 5.11 flashtool says
03/005/2017 05:05:49 - INFO - Loader : S1_Root_f936 - Version : MSM8994_50 / Boot version : S1_Boot_MSM8994_LA1.2_119 / Bootloader status : ROOTED
And now in 5.11 it also says bootloader unlocked : Yes Lost my drm again
So I am back in flashing and rooting (with drmfix etc) Android 7 again Thanks for sharing this solution!!
So you confirm that TA backup is the only solution to solve the "unlock allowed" bad state, don't you?
This is good for other people because when I faced the problem I was really scared to have messed up my phone!!!
i want to confirm the solution here
i had the same problem and the only way back of it was to downgrade to Lollipop and restore the TA-Partition
i dont think there is a solution if you did not backup your TA and have an image of it.
Yes, the TA restore is the only known solution, and I am glad Zegovernator shared his solution here