Related
Hi everybody! I'm new at this forum, i come from xperia x8 forum, and I have problems with custom kernels. I have a xperia Neo V, and I just cant connect the phone in fastboot mode. I'm not sure if it is properly bootloader-unlocked, as in the oficial sony's webpage it said that cdma devices cannot be unlocked (check http://unlockbootloader.sonymobile.com/), and I think that is the standard in Europe isn't it? (I'm from spain). Also, I checked the service menu and it also indicates that the bootloader cannot be unlocked.
Anyway i tried through the testpin-s1 tool method and everything seemed to work fine, i got the output with the two lowercase "r", but not the messages showing the model, software version, custom version, filesystem version and serial number, as said in vimjam's guide (check the post regarding unlock BL here: http://forum.xda-developers.com/showthread.php?t=1409269).
When I try to connect it in fastboot mode it just shows the sony ericsson logo and starts to charge, not showing any blue led. I know that this happens in locked devices, but the two lowecase "r" in s1 tool indicate that it is unlocked, so i dont understand... Can someone tell me if my phone is properly unlocked, or if custom kernels can be flashed connecting the device in flash mode (as it does work for me)? Thanks in advance
Eventhough your bootloader is now unlocked, your fastboot is still locked, you have sim-locked phone and you need to pay to unlock it.
ok, so you mean I have to sim-unlock my phone in adition to bl-unlock to connect it in fastboot mode? can this be done in wotanserver or i have to take it to some tech service?
danygarss said:
ok, so you mean I have to sim-unlock my phone in adition to bl-unlock to connect it in fastboot mode? can this be done in wotanserver or i have to take it to some tech service?
Click to expand...
Click to collapse
Yes, you can use wotanserver.
Madfysh said:
Yes, you can use wotanserver.
Click to expand...
Click to collapse
Hi,I managed to unlock my bootloader using msm7227_semc.cmd method.However when I tried to enter fastboot I couldnt
as my sim was locked.I paid for unlock via S1 tool and now have an unloked phone.However when I identify the phone to check
the status of the bootloader I only get one r "Look For Line RUNNING S1_EROM VER "r8A029" but the loader version has a
R .Is my bootloader still unlocked? I have tried getting into fastboot mode but nothing seems to happen.Can you please guide me?
Thanks for reading .Your reply is much appreciated.
Hey guys,
I got a problem.
Bought a second hand z2 today and it sayt it got a update 17.1.2.A.0.314
When I dontload it it sayt cant verify,same with pc companion,but then it says this phone has custom software or something.
I suspect,unlocked bootloader,but when I try to relock bootloader with flash tool it sayt,this phone can not be unloaded officialy?
Someone know how I can fix this?
and is there a way how to check if bootloader is unlocked,like Samsung when u boot with power button and volume up.
Thnx
Go to your dialer and enter *#*#7378423#*#*. Then go to Service Info -> Configuration. What is indicated under Rooting status?
If it says "Bootloader unlock allowed - Yes", this means that your bootloader is still locked but can be unlocked.
If it says "Bootloader Unlocked - Yes", then it means that your bootloader is already unlocked.
If it says "Bootloader unlock allowed - No", then it means your bootloader can never be unlocked.
If your bootloader is indeed unlocked and you want to flash stock firmware, you cannot use PC Companion. You need to use Sony Flash Tool instead.
I faced the same problem. If you have modified any system files (like build.prop) or removed/uninstalled any system apps, then it will error out with the "can't verify".
Just revert all changes you made, re-install and system apk u removed, and try again.
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
Hi people!
I know, I'm completely newbie in this.
But I'm getting in trouble and confused about it.
The question is simple:
What's means FRP lock / unlocked and Phone lock / unlocked?
And what's the difference between them?
FRP means Factory Reset Protection. If locked your phone will be protected of unauthorized factory resets. If a stranger tries to reset your phone, the phone will ask for your Google password on startup.
So if you unlock FRP you will lose that protection but this is required too unlock your bootloader (that's what you called phone locked/unlocked).
Phone locked (bootloader locked) means that you cannot make any changes too the partitions of your phone for example the recovery. So you are required to unlock your phone to install custom recoveries and ROMs like TWRP or RR etc.
Hope I could help you clear some things up.
If you're planning to sell your Android phone, make sure to remove your Google account from it first or else the next owner wouldn't be able to use it.
FRP means Factory Reset Protection. If locked your phone will be protected of unauthorized factory resets. If a stranger tries to reset your phone, the phone will ask for your Google password on startup.
So if you unlock FRP you will lose that protection but this is required too unlock your bootloader (that's what you called phone locked/unlocked).
Phone locked (bootloader locked) means that you cannot make any changes too the partitions of your phone for example the recovery. So you are required to unlock your phone to install custom recoveries and ROMs like TWRP or RR etc.
actory Reset Protection (FRP) is a security method that was designed to make sure someone can't just wipe and factory reset your phone if you've lost it or it was stolen. Starting with Android Lollipop, FRP is "standard" in vanilla Android, and most companies making our phones have implemented it in their own models.Mar 29, 2016
Killus3 said:
Hi people!
I know, I'm completely newbie in this.
But I'm getting in trouble and confused about it.
The question is simple:
What's means FRP lock / unlocked and Phone lock / unlocked?
And what's the difference between them?
Click to expand...
Click to collapse
Hi everybody,
My question is going to sound stupid, but now that I've got the unlock code for the bootloader, how do I unlock the FRP?
It is to this part that I am lost.
Sorry but I'm not very young anymore and not healthy. I had a big car accident and am much more on my phone and my computer
Rommco05 said:
You need have enabled OEM unlock in Developer options for unlock FRP
Click to expand...
Click to collapse
Hi,
OK so I activate the OEM to unlock the FRP.
And for unlocking the Bootloader I can use Huawei Multi Tools?
Should I delete my Google Account or Huawei before doing these manipulations?
I do not have fingerprint or pattern lock.
Thanks in advance for your answers.
This video is for the Honor 8, but the same steps are used to unlock the bootloader on the Honor 9.
https://www.youtube.com/watch?v=C_svTrjyU7o
Hey, guys! I have on the screen now written in green font "PHONE Relocked", "FRP Lock". What to do?
Rommco05 said:
What u need to do?
Click to expand...
Click to collapse
I can't restore the system
Rommco05 said:
You can't boot to system? What u do before
Click to expand...
Click to collapse
I unlocked the bootloader. Done on the instructions of the website:https://emui.huawei.com/en/plugin/unlock/step. After unlocking bootloader on my phone fastboot appeared the inscription "PHONE Unlock" and "Unlock FPR". On my device sprosili settings. After that, I re-entered entered the Google account, but the phone then began to hang periodically. I went into developer mode, done a factory reset there. And decided to turn back. Went to fastboot, blocked Downloader. Phone rebooted, then on the screen appeared the inscription: "Relock PHONE" and "FPR Lock". Out of fastboot, there was a black window where it says to restore the system through recovery in the air, but when I try to do fails. Help me, please!
Rommco05 said:
You can't boot to system? What u do before
Click to expand...
Click to collapse
Here are pictures of my screen:
Reset via HiSuite does not help.
I have the honor 6a.
Rommco05 said:
I understand but I don't know how fix it
Click to expand...
Click to collapse
I think he became a brick forever((((((crying:
Rommco05 said:
U can try something like dc unlocker or funkyhuawei but is a payed services
Click to expand...
Click to collapse
How much is the service on DC Unlocker?
First try using funkyhuawei?
nl520 said:
I think he became a brick forever((((((crying:
Click to expand...
Click to collapse
First you should try the HWOTA procedure without rebranding.
Dear all,
I bought Mi Pad 4 and it was running well, and I want to update the ROM. The device is comes with Locked bootloader.
I unlocked my Mi Pad 4 using MI Unlock. And when I try to relock it using "fastboot oem lock" command, it become suddenly comes with black screen with written: "The system has been destroyed. Press power button to shutdown".
So I entered the fastboot mode and try some command/solutions:
- My device status is locked:
E:\Minimal ADB and Fastboot>fastboot oem device-info
...
(bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
OKAY [ 0.006s]
finished. total time: 0.006s
- I can't unlock it using Mi Unlock:
- Flashing using MiFlashalso not allowed since it is still locked:
- I tried to unlock using fastboot, also failed:
E:\adb>fastboot oem unlock
...
FAILED (remote: Token Verify Failed, Reboot the device
)
finished. total time: 0.003s
- The faastboot screen in my mi pad is only for around 10 Second. After that it goes to "The System has been Destroyed" stage...
Any help is appreciated, because I cant use it anymore...
Why did you even want to close the BL again?!? I dont understand anyone who does that.
And AFAIK you can flash an original Image from Xiaomi even with locked BL. But I have never done it and the guide shows a working phone..
http://en.miui.com/thread-835254-1-1.html
You need the Mi-Flash Tool. And these damn Indian people with their fake titles on youtube.. The title is english and the freaking video is hindi or whatever.. SO ANNOYING!!!
Hi, the tutorial you gave is for 'normal' xiaomi phone, where it boot normally (even its BL is locked).
In my case, I cant load the BL (It said: Destroyed). The only thing I can do is restart to fastboot state, and after 20 seconds it goes again to Destroyed state.
Ok, so I have read some other threads and what seems the "only" solution is to unlock the bootloader again.. But the other people had no problem running "oem unlock".. And you get an error, what is kinda strange.
What happens in MiUnlock? Error?
Hi, I think the main problem is current status is "The System has been Destroyed", therefore it cannot load the BL.
Meanwhile, the BL is in Locked status. So it need to be un-locked first, so I can load the new ROM.
MIUnlock is error, it said: "Current account is not bound to this device", which is strange, because previously I unlocked using it before.
I assume MIUnlock said this because the status of "System destroyed"...
Never lock if there is not 100% Xiaomi official rom inside, and better use MiFlash with "clean all and lock" option for locking.
Thanks for your suggestion. Will do that after I fix this problem..
I think you have a bricked device.. Some devices have this "test-pins", where you can enable some debug-bridge and there you could flash it (mi5 or redmi5 was that in that thread). I dont know if the Pad4 has such Pins and you would have to open the whole device.. (its not something you can access from the outside).
But I dont know if the Pad has these test-pins, just because another Xiaomi device had it..
Noted on that, but too risky for me to open the case..
Any other solution would be really appreciated.
thE_29 said:
But I dont know if the Pad has these test-pins, just because another Xiaomi device had it..
Click to expand...
Click to collapse
On some devices you have to login your Mi Account with MiFlash when flashing in EDL mode and account needs special permissions.
P.Kosunen said:
On some devices you have to login your Mi Account with MiFlash when flashing in EDL mode and account needs special permissions.
Click to expand...
Click to collapse
Yup, and I cant do that since cannot load the BL, because it's "Destroyed" right now..
Up.
Does anyone have the solution on this?
Thanks.
Seemed "bricked" to me, welcome to the bricked world dude, I have had 2 beautiful paper holder on my desk.
mac_erot said:
Up.
Does anyone have the solution on this?
Thanks.
Click to expand...
Click to collapse
The only solution was already posted several times -> open device, find test-pins, use them and flash ROM. And yet, you still ignore it everytime. THERE is no other solution for bricked devices.
And: NEVER close the bootloader again on NON official ROMs.
2 ways to try out...
1st run
"fastboot flashing unlock"
2nd
"fastboot oem reboot EDL"
Or this link if the command doesn't work
https://www.google.com/amp/s/forum....e-how-to-reboot-to-edl-fastboot-t3394292/amp/
go to service centre they will be able to restore the device using edl i hope
I tried also all solutions, but nothing helped. EDL, fastboot, etc.
If there is a way to unlock the BL again I can go on. Otherwise there will be no chance for me to get it running.
Has anyone got a solution how I can unlock the BL again? Or flash with locked BL?
Thanks!
maluc said:
I tried also all solutions, but nothing helped. EDL, fastboot, etc.
If there is a way to unlock the BL again I can go on. Otherwise there will be no chance for me to get it running.
Has anyone got a solution how I can unlock the BL again? Or flash with locked BL?
Thanks!
Click to expand...
Click to collapse
Looks like it is straightforward to remove the back cover. Perhaps you can find the EDL test points on the motherboard?
https://www.youtube.com/watch?v=RZpj0k9HKTQ
Is there no possibility to enable USB Debugging without entering the miui surface?
maluc said:
I tried also all solutions, but nothing helped. EDL, fastboot, etc.
If there is a way to unlock the BL again I can go on. Otherwise there will be no chance for me to get it running.
Has anyone got a solution how I can unlock the BL again? Or flash with locked BL?
Thanks!
Click to expand...
Click to collapse
Edl with test points should work, try some different ones, maybe the ones you are trying are wrong
---------- Post added at 06:47 AM ---------- Previous post was at 06:47 AM ----------
Also, try to run fastboot erase vbmeta