Hi, I'm having issues trying to root brand new XZ1 following this guide: https://forum.xda-developers.com/xperia-xz1/how-to/guide-how-to-persistant-root-xperia-xz1-t3718375 .
When I try to fastboot flash G8342 boot img I get "Flashing is not allowed in Lock State" error. I have made sure that OEM bootloader is unlocked in developer options...
I have tried updating drivers, using different boot img no luck. Anyone know what the solution is?
goldenboy23 said:
Hi, I'm having issues trying to root brand new XZ1 following this guide: https://forum.xda-developers.com/xperia-xz1/how-to/guide-how-to-persistant-root-xperia-xz1-t3718375 .
When I try to fastboot flash G8342 boot img I get "Flashing is not allowed in Lock State" error. I have made sure that OEM bootloader is unlocked in developer options...
I have tried updating drivers, using different boot img no luck. Anyone know what the solution is?
Click to expand...
Click to collapse
Sounds like your bootloader is still locked, just because you flipped the OEM switch doesn't mean it's unlocked... Go read over here before you do anything else.. ( https://developer.sony.com/develop/open-devices/get-started/unlock-bootloader/ )
lilbrat said:
Sounds like your bootloader is still locked, just because you flipped the OEM switch doesn't mean it's unlocked... Go read over here before you do anything else..
Click to expand...
Click to collapse
Thanks, that's a good guide. But when I try to run "fastboot -i 0x0fce oem unlock 0x<insert your unlock code>" it always returns that the command's syntax is incorrect. Is this because I don't have 26.0.2 platform tools?
goldenboy23 said:
Thanks, that's a good guide. But when I try to run "fastboot -i 0x0fce oem unlock 0x<insert your unlock code>" it always returns that the command's syntax is incorrect. Is this because I don't have 26.0.2 platform tools?
Click to expand...
Click to collapse
Did you get your unlock code?
lilbrat said:
Did you get your unlock code?
Click to expand...
Click to collapse
Actually I sorted that out, I was entering it with the brackets when I was meant to remove them. But when I enter it now, it doesn't tell me incorrect syntax, but tells me instead "unknown option: -- i" I wonder if this is an issue of using too new version of Platform tools? (I'm using 28.0.1)
Right I figured it out. Just omitted the -i option and it worked. So it looked like "fastboot oem unlock 0x<unlock code>"
no further issues cheers
I get same problem (bootloader unlocked, OEM unlocked .....But show I'm in lock state)
goldenboy23 said:
Hi, I'm having issues trying to root brand new XZ1 following this guide: https://forum.xda-developers.com/xperia-xz1/how-to/guide-how-to-persistant-root-xperia-xz1-t3718375 .
When I try to fastboot flash G8342 boot img I get "Flashing is not allowed in Lock State" error. I have made sure that OEM bootloader is unlocked in developer options...
I have tried updating drivers, using different boot img no luck. Anyone know what the solution is?
Click to expand...
Click to collapse
Google 'unlock xperia bootloader', and check the xz1 compact forum for the DRM backup method for your phone. (I know you said you have a xz1)
You need to unlock the bootloader using a code from sony, and enter it via a fastboot command before twrp can be booted/installed.
Related
Hello,
every Time i end this command
fastboot -i 0x0fce oem unlock IMEI-Number
i get this answer:
FAILED (remote: Command not allowed)
finished. total time: 0.006s
What do i wrong?
Can someone help me please?
cheers
Why don't you read official guide?
http://developer.sonymobile.com/unlockbootloader/
-i ?
check your USB-driver (if on Windows) and fastboot binary
on Windows 10?
-> http://forum.xda-developers.com/crossdevice-dev/sony/minitut-installing-adb-drivers-sony-t3185585
AndroPlus said:
Why don't you read official guide?
http://developer.sonymobile.com/unlockbootloader/
Click to expand...
Click to collapse
great help -.-
i followed these instructions before, but it didnt work
DHGE said:
-i ?
check your USB-driver (if on Windows) and fastboot binary
on Windows 10?
-> http://forum.xda-developers.com/crossdevice-dev/sony/minitut-installing-adb-drivers-sony-t3185585
Click to expand...
Click to collapse
yes -i .... its a command where sony says u must use it.
i am on windows 7
how can i check fastboot binary?
how can i check fastboot binary?
Click to expand...
Click to collapse
http://developer.sonymobile.com/downloads/drivers/
You really want to unlock the BL?
DHGE said:
http://developer.sonymobile.com/downloads/drivers/
You really want to unlock the BL?
Click to expand...
Click to collapse
yes?
i think u need it for rooting?
I don't even get to fastboot part - every time I reboot with adb reboot bootloader the tablet goes into some mode with a black screen, green led indicator and fastboot devices returning nothing.
At the same time the device is recognized by windows as something S1???? and unknown driver, and I totally failed to find a proper driver for that.
Any help will be appreciated. Btw, Windows 10 here
@XBOHDPuKC
READ this thread!
DHGE said:
@XBOHDPuKC
READ this thread!
Click to expand...
Click to collapse
Which one...
Some bootloaders are unlockable. Mine is the same way. I have to wait for a root method that does not unlock the bootloaders.
Sent from my Nexus 6
Some bootloaders are unlockable
Click to expand...
Click to collapse
= you can unlock them
to be expected with SGP712 and SGP771
Maybe with some provider branded Tablets in Japan they are "not unlockable".
interesting read (!) with a warning:
http://forum.xda-developers.com/xperia-z4/help/rooting-status-uknown-t3160932
DHGE said:
Maybe some Japanese provider branded.
But not SGP712 or SGP771. We are in the tablet forum.
Click to expand...
Click to collapse
my service menu shows bootloader as unlockable
Sent from my SGP771 using Tapatalk
UPDATE (03/09/2019):
This thread is now dedicated to the development of the Vertu Aster P replica, which has MTK's MT6755 Helios P10 chipset.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Hi All,
I've just recently bought a Vertu Aster P replica, which came pre-loaded with a Vertu-themed (skinned) version of Android 6.0 Marshmallow. In the 'About Device' menu, however, the developers have (not so cleverly) disguised it to say Android 8.1.0 (Oreo). Why they would do this, rather than just taking Oreo and skinning it with the Vertu theme, I don't know. Anyway, I've gone and hard bricked the phone while trying to install a custom recovery, and it will not turn on or charge. It is still recognised when plugged into the laptop, so if I had the original ROM that it came with, I would be able to reflash it and have a working phone again. Sadly, I cannot find the ROM for it anywhere online. I can find the ROM's for the Vertu Signature Touch replica and Vertu Ti, and others, but not for the new Aster P replica, which uses the MT6755 chipset. Here are a few photos of the phone's OS. So, I'm wondering if anyone might be able to point me in the right direction of where I might be able to find this ROM. I have already been in contact with the company I bought it from. Still waiting to hear back from them. Hopefully they can just send me a download link.
Chris
Still living in hope that someone has access to the ROM for this phone.
Someone kind enough eventually came along and sent me the ROM. Flashed it and my phone now works again. Lesson learnt. ALWAYS DO A BACKUP BEFOREHAND.
I will upload it myself and make it available on here for other Aster P (replica) owners shortly.
Chris
Here it is.
https://www.needrom.com/download/vertu-aster-p-mt6755-chinese-clone-firmware/
I have also successfully managed to root the device using Magisk. If anyone else has the same device and wishes to root it, I'll guide you through the method if need be.
Chris
chris8189 said:
I have also successfully managed to root the device using Magisk. If anyone else has the same device and wishes to root it, I'll guide you through the method if need be.
Chris
Click to expand...
Click to collapse
Chris are you fastbooting to Recovery or actually flashing to the recovery partition?
I found a TWRP on XDA forums which @lopestom made for the BLU Pure XR P0030UU smartphone -
https://forum.xda-developers.com/pure-xr/development/twrp-twrp-3-1-x-x-blu-pure-xr-p0030-t3623865
The above phone also has the MT6755 P10 Helios chip, same as the Vertu Aster P clone, so I thought I would try and port the ROM over for the Vertu Aster P replica.
I got an error while doing the repack, however @ashyx managed to perform a successful repack on the image file and the phone does indeed boot up the TWRP. Problem is, there is no touch functionality. Plugging in an OTG mouse however might work, or likewise flashing the recovery image file to the boot partition, doing what you need to do in TWRP, and then flashing the stock (or modified) boot image back. I have put the feelers out for the kernel source, so (hopefully) we can then do the necessary tweaks to make TWRP function correctly, or even better, build a TWRP from source (if we can get it). Below is the link to the TWRP file.
https://mega.nz/#!J45FWIzJ!aFyFooO5aOtxjFany_osL4BpRRQSMljQjtfnYSFKDis
Chris
ashyx said:
Chris are you fastbooting to Recovery or actually flashing to the recovery partition?
Click to expand...
Click to collapse
I am flashing the recovery using SP Flash Tool (for MTK devices) to the recovery partition.
Chris
chris8189 said:
I am flashing the recovery using SP Flash Tool (for MTK devices) to the recovery partition.
Chris
Click to expand...
Click to collapse
Does this device not support fastboot?
Also does touch work if flashed to the boot partition?
ashyx said:
Does this device not support fastboot?
Also does touch work if flashed to the boot partition?
Click to expand...
Click to collapse
Yes, the device does support fastboot mode.
When flashing this TWRP to the boot partition, touch functionality, and all aspects of TWRP work perfectly.
Chris
chris8189 said:
Yes, the device does support fastboot mode.
When flashing this TWRP to the boot partition, touch functionality, and all aspects of TWRP work perfectly.
Chris
Click to expand...
Click to collapse
What happens if you just Fastboot boot 'recovery.img' rather than flashing it?
ashyx said:
What happens if you just Fastboot boot 'recovery.img' rather than flashing it?
Click to expand...
Click to collapse
When I do that, it says that oem unlock is false, however in the developer options on my phone, I have the OEM Unlock turned on, so I don't understand why it's saying that. When type in 'fastboot oem unlock', my phone gives me the option to unlok the bootloader, or not, with the volume up and down keys. Volume up being unlock the bootloader and volume down being don't unlock the bootloader. When I press volume up, nothing happens. If I press volume down, however, it allows me to not unlock the bootloader, lol. Has an extra layer of security been added to this device? Is the OEM unlock option in my dev options just a fake toggle switch?
Chris
chris8189 said:
When I do that, it says that oem unlock is false, however in the developer options on my phone, I have the OEM Unlock turned on, so I don't understand why it's saying that. When type in 'fastboot oem unlock', my phone gives me the option to unlok the bootloader, or not, with the volume up and down keys. Volume up being unlock the bootloader and volume down being don't unlock the bootloader. When I press volume up, nothing happens. If I press volume down, however, it allows me to not unlock the bootloader, lol. Has an extra layer of security been added to this device? Is the OEM unlock option in my dev options just a fake toggle switch?
Chris
Click to expand...
Click to collapse
What result do you get for:
fastboot oem device-info
I tried it and the command doesn't work.
chris8189 said:
I tried it and the command doesn't work.
Click to expand...
Click to collapse
Try:
fastboot getvar unlocked
Typing 'fastboot getvar unlocked' confirms that the bootloader is locked. It says 'unlocked :no'
Chris
chris8189 said:
Typing 'fastboot getvar unlocked' confirms that the bootloader is locked. It says 'unlocked :no'
Chris
Click to expand...
Click to collapse
It definitely says OEM_UNLOCK enabled in developer settings and you're issuing the oem unlock command while in FASTBOOT mode?
ashyx said:
It definitely says OEM_UNLOCK enabled in developer settings and you're issuing the oem unlock command while in FASTBOOT mode?
Click to expand...
Click to collapse
Correct.
I read up online about it and some MTK devices don't support bootloader unlocking. Or, you have to obtain an 'unlock code' from the manufacturer.
Chris
chris8189 said:
Correct.
I read up online about it and some MTK devices don't support bootloader unlocking. Or, you have to obtain an 'unlock code' from the manufacturer.
Chris
Click to expand...
Click to collapse
Probably a daft question, but have you actually tried booting the unpacked twrp recovery image?
If these devices are so similar maybe the kernel is too.
ashyx said:
Probably a daft question, but have you actually tried booting the unpacked twrp recovery image?
If these devices are so similar maybe the kernel is too.
Click to expand...
Click to collapse
It doesn't load. It bootloops. So they have different kernels.
Chris
Ive tried all the normal ways fastboot oem lock ect ect
And it it safe for me? Are there any prequisite's?
Thanks
medseven said:
Ive tried all the normal ways fastboot oem lock ect ect
And it it safe for me? Are there any prequisite's?
Thanks
Click to expand...
Click to collapse
The "fastboot oem lock" command does not exist, it is certainly not a normal way
The best method to lock bootloader is searching for the Service rom on https://androidhost.ru/ and doing the dload method. Process will erase all the data from your device !
(Before you do anything, read carefully Software Upgrade Guidline in "ReleaseDoc" . With Service ROM you will get full stock with locked bootloader (warranty will not void any more).)
Hi thanks a lot for your reply, Unfortunately I cannot find such rom on the site for the life of me.
medseven said:
Hi thanks a lot for your reply, Unfortunately I cannot find such rom on the site for the life of me.
Click to expand...
Click to collapse
Hi, which build number do you run? (e.g. ANE-LX1 9.1.0.306 (C432))
bozka1 said:
The "fastboot oem lock" command does not exist, it is certainly not a normal way
The best method to lock bootloader is searching for the Service rom on https://androidhost.ru/ and doing the dload method. Process will erase all the data from your device !
(Before you do anything, read carefully Software Upgrade Guidline in "ReleaseDoc" . With Service ROM you will get full stock with locked bootloader (warranty will not void any more).)
Click to expand...
Click to collapse
bozka1 said:
Hi, which build number do you run? (e.g. ANE-LX1 9.1.0.306 (C432))
Click to expand...
Click to collapse
it is ane-lgprs-ovs 9.1.0.13 it does not show me the c variant.
I see your replying to my other thread aswell, no point having 2 so I will carry on here.
I have downloaded a rom called Huawei P20 Lite ANE-LX1 ANE-L01 hw eu HLRCF Anne-L01 8.0.0.167(C432) Firmware 8.0.0 r1 EMUI8.0 05015ACF [androidhost.ru] so I am going to try this with HuRUUpdater 0.4
medseven said:
it is ane-lgprs-ovs 9.1.0.13 it does not show me the c variant.
Click to expand...
Click to collapse
It can be found in System - About phone . It's very important.
all it gives me in build number is ANE-LGRPS-OVS 9.1.0.132
there really is no brackets or c variant
medseven said:
all it gives me in build number is ANE-LGRPS-OVS 9.1.0.132
there really is no brackets or c variant
Click to expand...
Click to collapse
Strange, maybe you tried to install some firmware manually before, hm?
Connect your phone in fastboot mode to PC , open 'Minimal ADB and fastboot' and use command
fastboot oem get-build-number
Unfortunately not even HuRUUpdater 0.4 is working with this particular rom it reports unknown error so I am at a complete loss really
bozka1 said:
The "fastboot oem lock" command does not exist, it is certainly not a normal way
The best method to lock bootloader is searching for the Service rom on https://androidhost.ru/ and doing the dload method. Process will erase all the data from your device !
(Before you do anything, read carefully Software Upgrade Guidline in "ReleaseDoc" . With Service ROM you will get full stock with locked bootloader (warranty will not void any more).)
Click to expand...
Click to collapse
bozka1 said:
Hi, which build number do you run? (e.g. ANE-LX1 9.1.0.306 (C432))
Click to expand...
Click to collapse
bozka1 said:
Strange, maybe you tried to install some firmware manually before, hm?
Connect your phone in fastboot mode to PC , open 'Minimal ADB and fastboot' and use command
fastboot oem get-build-number
Click to expand...
Click to collapse
even with fastboot its the same, no brackets or c variant!
on another not are the service roms called 'board software' ?
medseven said:
even with fastboot its the same, no brackets or c variant!
Click to expand...
Click to collapse
it should now be clear that you have installed the wrong version of firmware, IMO...
I can't you help anymore, sorry.
ok thanks for your time
Hello guys I'm trying to save my bricked P20 Lite but I am running into some issues. I unlocked the bootloader using testpoint but twrp won't flash or boot. Flashing gives me a flash write failure, booting gives me a invalid command error and I can't wipe cache either. I could really use your help.
Advanced07 said:
flash write failure
Click to expand...
Click to collapse
"flash write failure" - it might be due to a locked bootloader or hardware issue, AFAIK.
Try explaining what exactly happened, step by step.
-Alf- said:
"flash write failure" - it might be due to a locked bootloader or hardware issue, AFAIK.
Try explaining what exactly happened, step by step.
Click to expand...
Click to collapse
I unlocked my bricked P20 lite bootloader with the test pin method, then I tried to flash TWRP in fastboot and I got those errors.
Advanced07 said:
I unlocked my bricked P20 lite bootloader with the test pin method, then I tried to flash TWRP in fastboot and I got those errors.
Click to expand...
Click to collapse
Are you sure that bootloader is unlocked? (With unlocked BL you will see that message each time when you reboot: "Your device has been unlocked and can't be trusted").
Have you enabled in Developer menu
"OEM unlock" ?
In fastboot mode run commands :
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
and post the results.
-Alf- said:
Are you sure that bootloader is unlocked? (With unlocked BL you will see that message each time when you reboot: "Your device has been unlocked and can't be trusted").
Have you enabled in Developer menu
"OEM unlock" ?
In fastboot mode run commands :
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
and post the results.
Click to expand...
Click to collapse
1. Yes I do get that message that it's unlocked.
2. My device is bricked so that's impossible to enable. I unlocked it after it started bootlooping.
3. Gonna do those commands and tell the results
(bootloader) :ANE-LX1 9.1.0.372(C432E7R1P7)
(bootloader) ANE-LX1
vendorcountry: hw/eu
(bootloader) :ANE-LX1-CUST 9.1.0.7(C432)
(bootloader) :ANE-LX1 9.1.0.132(C432E5R1P7)
What shows Fastboot screen, at the bottom, Phone unlocked and FRP unlock ?
-Alf- said:
What shows Fastboot screen, at the bottom, Phone unlocked and FRP unlock ?
Click to expand...
Click to collapse
Phone unlocked and FRP unlock.
I unlocked the phone and the frp went away but it still gave me errors. Rebooted and frp lock was back + bootloader unlock gives error
Advanced07 said:
Rebooted and frp lock was back + bootloader unlock gives error
Click to expand...
Click to collapse
as i mentioned a month ago :
-Alf- said:
IMO it might be the HW problem , dead memory or damaged motherboard
Click to expand...
Click to collapse
Probably your emmc memory is fried. Not being able to unlock BL & FRP permanently is a sure sign. But I'm just an amateur and an android fan, maybe I'm wrong.
-Alf- said:
as i mentioned a month ago :
Probably your emmc memory is fried. Not being able to unlock BL & FRP permanently is a sure sign. But I'm just an amateur and an android fan, maybe I'm wrong.
Click to expand...
Click to collapse
It does have water damage could it be because of that? That would be unfortunate.
Advanced07 said:
It does have water damage could it be because of that? That would be unfortunate.
Click to expand...
Click to collapse
- known failure due to water exposure , although the write failures are intermittent.
P.S.: since January are you trying unbrick a water damaged phone?
-Alf- said:
- known failure due to water exposure , although the write failures are intermittent.
P.S.: since January are you trying unbrick a water damaged phone?
Click to expand...
Click to collapse
Nope i already know it was dead (repairs say it was total loss) but when I saw the new unlock method I thought it might be saved. Guess I was wrong but oh well I tried anyways.
Advanced07 said:
Nope i already know it was dead (repairs say it was total loss) but when I saw the new unlock method I thought it might be saved. Guess I was wrong but oh well I tried anyways.
Click to expand...
Click to collapse
Hi i have a query, the phone that you unlocked was it running on emui 9.1? If yes did you use potato nv to unlock? I wanna try it myself
apexashwin said:
Hi i have a query, the phone that you unlocked was it running on emui 9.1? If yes did you use potato nv to unlock? I wanna try it myself
Click to expand...
Click to collapse
It was running on the latest version and yes I did use potato NV
Advanced07 said:
It was running on the latest version and yes I did use potato NV
Click to expand...
Click to collapse
Hello thanks for your quick reply,I finally managed to unlock my p20 lite using potato nv.
i try the version of Magisk 23.0 but this is not worked.
It's the same with all other Xperia devices without customise recovery.
You first use Unsin (can find it in XDA) to the boot_blahblahblah.sin from stock firmware for unsin it. Therefore you will see a .IMG is generated.
Second, you transfer the .IMG to your phone, and use Magisk to patch (install - select file and patch) the boot file.
After it's patched (you can find it in the Download folder). Transfer the patched one back to your PC, and make phone enter fastboot mode (or the blue light mode). Then you run this command on Windows Shell (Google it, it's easy)
Fastboot flash boot the_file_name.img
After it's done, boot into your phone, you can find icon of Magisk, install it, and your phone is rooted in this stage.
Nevermind figured it out
Kylewolf said:
Nevermind figured it out
Click to expand...
Click to collapse
Before you do anything, a unlocked bootloader is must required.
JaneValley said:
It's the same with all other Xperia devices without customise recovery.
You first use Unsin (can find it in XDA) to the boot_blahblahblah.sin from stock firmware for unsin it. Therefore you will see a .IMG is generated.
Second, you transfer the .IMG to your phone, and use Magisk to patch (install - select file and patch) the boot file.
After it's patched (you can find it in the Download folder). Transfer the patched one back to your PC, and make phone enter fastboot mode (or the blue light mode). Then you run this command on Windows Shell (Google it, it's easy)
Fastboot flash boot the_file_name.img
After it's done, boot into your phone, you can find icon of Magisk, install it, and your phone is rooted in this stage.
Click to expand...
Click to collapse
good job my friend.
JaneValley said:
Before you do anything, a unlocked bootloader is must required.
Click to expand...
Click to collapse
Hello
Did you find Xperia 1 iii on Sony Developer site?
Or how did you achieve the unlock file?
Regards,
Olavbson
Where the hell do i find the official firmware, thats where im stuck
ya id like to unlock bootloader so i can achieve root on us xperia 1 iii. nothing has worked. and xperia 1 iii isnt on sony develope site to unlock bootloader. either. how are people doing this.
jporter396 said:
ya id like to unlock bootloader so i can achieve root on us xperia 1 iii. nothing has worked. and xperia 1 iii isnt on sony develope site to unlock bootloader. either. how are people doing this.
Click to expand...
Click to collapse
same am stuck at bootloader unlock rn. Cannot flash
olavbson said:
Hello
Did you find Xperia 1 iii on Sony Developer site?
Or how did you achieve the unlock file?
Regards,
Olavbson
Click to expand...
Click to collapse
Sorted it? Rooted mine earlier on. To unlock the bootloader you can just pick Xperia 1 or 1II it doesn't matter 1III will be added eventually but doesn't make a difference.
AJHutchinson said:
Sorted it? Rooted mine earlier on. To unlock the bootloader you can just pick Xperia 1 or 1II it doesn't matter 1III will be added eventually but doesn't make a difference.
Click to expand...
Click to collapse
What about DRM keys? how do u deal with that.
AJHutchinson said:
Sorted it? Rooted mine earlier on. To unlock the bootloader you can just pick Xperia 1 or 1II it doesn't matter 1III will be added eventually but doesn't make a difference.
Click to expand...
Click to collapse
Hey sorry another question, i know rooting will kill netfleex and such but did u notice any other side effects, can you still view HDR
rom4ster said:
Hey sorry another question, i know rooting will kill netfleex and such but did u notice any other side effects, can you still view HDR
Click to expand...
Click to collapse
I haven't noticed anything that's not working buddy
AJHutchinson said:
I haven't noticed anything that's not working buddy
Click to expand...
Click to collapse
Thanks, sorry to bother you more but how did you unlock the phone exactly?
I am getting this error on fastboot
fastboot oem unlock 0x2DC728328A49EEAB
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
rom4ster said:
Thanks, sorry to bother you more but how did you unlock the phone exactly?
I am getting this error on fastboot
fastboot oem unlock 0x2DC728328A49EEAB
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
Click to expand...
Click to collapse
Mine was doing the same buddy, make sure you have entered the correct IMEI and that you have OEM unlock and usb debugging turned on in the developer settings
AJHutchinson said:
Mine was doing the same buddy, make sure you have entered the correct IMEI and that you have OEM unlock and usb debugging turned on in the developer settings
Click to expand...
Click to collapse
i verified OEM unlock is on in settings I am copying the IMEI reported by ADB directly, and USB debugging is on yet the error persists. What solved it for you?
rom4ster said:
i verified OEM unlock is on in settings I am copying the IMEI reported by ADB directly, and USB debugging is on yet the error persists. What solved it for you?
Click to expand...
Click to collapse
Check the IMEI by dialing *#06# see if it matches up with that one, if using Dual SIM variant use the first code
AJHutchinson said:
Check the IMEI by dialing *#06# see if it matches up with that one, if using Dual SIM variant use the first code
Click to expand...
Click to collapse
Also is
Code:
Fastboot devices
showing a device? Maybe it's not installed properly?
same issue here. command not supported error. did everything on sony guide to the t. us variant, windows 10. not sure what to do
fastboot shows device too
jporter396 said:
same issue here. command not supported error. did everything on sony guide to the t. us variant, windows 10. not sure what to do
fastboot shows device too
Click to expand...
Click to collapse
Annoying aye, my issue was with the IMEI I must have been putting a wrong digit in but it worked eventually