I am trying to unlock the bootloader for my device (it's a cheap Chinese phone) and then root using Magisk. The first problem is that OEM Unlock option is not available in developer options, so I got no choice other than try unlocking using fastboot. Now the second problem is that fastboot doesn't show anything at all. Normally there is a Fastboot written at the top left corner of the device but in my case there is no output but the blank screen, and I do verify that my device is in fastboot mode because when I do fastboot devices, it show's the output:
Code:
C:\Users\Mujtaba>adb devices
List of devices attached
Y3123A0310Q0100020953 device
C:\Users\Mujtaba>adb reboot bootloader
C:\Users\Mujtaba>fastboot devices
Y3123A0310Q01000209 fastboot
Since fastboot was responding (partially), I tried to unlock the bootloader using different commands but each time I get read/write failed error.
Code:
C:\Users\Mujtaba>fastboot oem unlock
...
FAILED (command write failed (Unknown error))
finished. total time: 5.011s
C:\Users\Mujtaba>fastboot oem unlock
...
FAILED (status read failed (Too many links))
finished. total time: 80.886s
Alas, I got the same results with fastboot oem unlock-go and fastboot flashing unlock as fastboot is not accepting (at least I think) any command except fastboot devices.
I read the official guide and there I found that:
Devices should deny the fastboot flashing unlock command unless the get_unlock_ability is set to 1. If set to 0, the user needs to boot to the home screen, open the Settings > System > Developer options menu and enable the OEM unlocking option (which sets the unlock_ability to 1).
Click to expand...
Click to collapse
My device supports unlocking bootloader because I've checked the build.prop file using adb shell getprop and it includes the properties stated below:
The ro.oem_unlock_supported property should be set at build time based on whether the device supports flashing unlock.
If the device suppports flashing unlock, set ro.oem_unlock_supported to 1. If the device doesn't support flashing unlock, set ro.oem_unlock_supported to 0. If the device supports flashing unlock, then the bootloader should indicate the lock status by setting the kernel command line variable androidboot.flash.locked to 1 if locked or 0 if unlocked.
For devices that support dm-verity, use ro.boot.verifiedbootstate to set the value of ro.boot.flash.locked to 0; this unlocks the bootloader if the verified boot state is orange.
Click to expand...
Click to collapse
Code:
C:\Users\Mujtaba>adb shell getprop
[ro.oem_unlock_supported]: [1]
[ro.boot.verifiedbootstate]: [green]
[ro.boot.flash.locked]: [1]
[sys.oem_unlock_allowed]: [0]
.
.
Someone on reddit did this to find the OEM unlock state, mine of course returned 0 as you can see above.
Code:
adb shell getprop sys.oem_unlock_allowed
Device Specs:
CPU: ARM Cortex-A-7 @ 1.20 Ghz
GPU: Mali-400 MP
Board: sp7731cea (Unisoc aka Spreadtrum)
Build: Q Infinity C_MP_26_01
Treble: NA
Seamless update (A/B): NA
Your phone is based on Spreadtrum chipset. Means such a device has its own mechanism to unlock the bootloader.
jwoegerbauer said:
Your phone is based on Spreadtrum chipset. Means such a device has its own mechanism to unlock the bootloader.
Click to expand...
Click to collapse
Yes I know that and I already found a method but again it uses oem get_identifier_token to get Identifier token and when I do that fastboot returns nothing.
There are other methods as well, like getting a PAC file for your device then extracting boot.img from it, patching it with magisk manager and then flashing that single partition (in this case BOOT partition) using SPD Research Tool but it gives me error as well.
Install the matching Android USB Driver if not done yet. Having installed common ADB / Fastboot drivers isn't enough.
Additional advice: Replace Help in this thread's title by QMobile QInfinity C
jwoegerbauer said:
Install the matching Android USB Driver if not done yet. Having installed common ADB / Fastboot drivers isn't enough.
Additional advice: Replace Help in this thread's title by QMobile QInfinity C
Click to expand...
Click to collapse
I have installed SPD drivers and Google USB drivers however the problem is not with drivers because I can use the following commands without an issue:
Code:
fastboot devices
fastboot reboot
fastboot reboot bootloader
The problem occurs when using:
Code:
fastboot oem unlock
fastboot flashing unlock
Google's USB driver is only suitable to Google devices like the Pixel / Nexus.
As already said: Install the Android USB Driver matching your phone!
Take note that OEM's Fastboot implementation isn't always same as AOSP 's Fastboot.
IMO before trying to unlock a device's bootloader it's always a good idea to check by means of ADB whether unlocking the bootloader is natively supported on device:
Code:
adb shell "getprop ro.oem_unlock_supported"
If returned value is 1, then it's supported otherwise it's not.
BTW: I no longer participate this thread.
jwoegerbauer said:
IMO before trying to unlock a device's bootloader it's always a good idea to check by means of ADB whether unlocking the bootloader is natively supported on device:
Code:
adb shell "getprop ro.oem_unlock_supported"
If returned value is 1, then it's supported otherwise it's not.
Click to expand...
Click to collapse
I've already included this property in the post. It returned 1
Related
Hello
I have a problem when I want to unlock my nexus 9.
First I have a problem because my tablet freezed.
I have made a factory reset, then google said me : used the first account to use your tablet" but I lost this account
So I want to flash my tablet.
to do that, I use the tutorial on HTC site. on step 5 they say:
type adb oem unlock
but the CMD windows just say:
<waiting for device>
then I try to show devices with adb device but my window don't show device.
to do those step my tablet was in recovery more "fastboot usb"
can you help me?
thanks
Jack
@jackvig Looks like you encountered Factory Reset Protection!
You can not use adb commands while in fastboot mode! "fastboot devices" should list your device.
And the command to unlock is "fastboot oem unlock" not adb!
Plus you won't be able to unlock the bootloader unless you have selected the option to do so in developer options, since you have factory reset that option may have been turned off even if you set it previously.
Your going to have to try and remember your account password to make the device usable.
Depending on what version/patch of the rom your device is on it maybe possible to Bypass FRP, google it.
If your device was on a very recent patch level, no bypass trick will work.
corkiejp said:
@jackvig Looks like you encountered Factory Reset Protection!
You can not use adb commands while in fastboot mode! "fastboot devices" should list your device.
And the command to unlock is "fastboot oem unlock" not adb!
Plus you won't be able to unlock the bootloader unless you have selected the option to do so in developer options, since you have factory reset that option may have been turned off even if you set it previously.
Your going to have to try and remember your account password to make the device usable.
Depending on what version/patch of the rom your device is on it maybe possible to Bypass FRP, google it.
If your device was on a very recent patch level, no bypass trick will work.
Click to expand...
Click to collapse
thanks @corkiejp for your reply
I agree with you for fastboot instead of adb but the result is the same.
I cannot go inside the tablet to change parameters
Some forum said that I can Unlock in recovery mode
Is it true?
when my tablet is in recovery mode (On/off + Vol Up)
the tablet show me device state : locked
I am in state HBOOT
the on my computer I do that
C:\Users\maison>fastboot oem unlock
...
(bootloader) ability is 0
(bootloader) Permission denied for this command!
OKAY [ 0.015s]
finished. total time: 0.018s
after I go in FASTBOOT mode then :
C:\Users\maison>fastboot oem unlock
< waiting for device >
what can I do to have the Key to unlock
No you need fastboot mode to unlock the bootloader!
Is the command "fastboot devices" listing your device. If not check your drivers for your device.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
HT4B6JT00881 fastboot
after that i try :
C:\Program Files (x86)\Minimal ADB and Fastboot>adb sideload volantis-ota-n9f27m-ad1aee0f.zip
loading: 'volantis-ota-n9f27m-ad1aee0f.zip'adb server is out of date. killing...
* daemon started successfully *
serving: 'volantis-ota-n9f27m-ad1aee0f.zip' (~0%) * failed to read command: Invalid argument
i think tablet i now connected to computer
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock
...
(bootloader) ability is 0
(bootloader) Permission denied for this command!
OKAY [ 0.011s]
finished. total time: 0.014s
As suspected the option to unlock is not selected in developer options.
If your successful in sideloading an OTA image in recovery mode (not fastboot mode), you will still encounter FRP on booting the device.
Edit: - As said before ADB commands do not work in fastboot mode. And fastboot commands do not work in Recovery mode!
As said before your only hope is to remember your account and password used (or the very last account you used on the device might work).
If you haven't updated the rom in the last year, you maybe able to use FRP Bypass trick.
jackvig said:
Hello
I have a problem when I want to unlock my nexus 9.
First I have a problem because my tablet freezed.
I have made a factory reset, then google said me : used the first account to use your tablet" but I lost this account
So I want to flash my tablet.
to do that, I use the tutorial on HTC site. on step 5 they say:
type adb oem unlock
but the CMD windows just say:
<waiting for device>
then I try to show devices with adb device but my window don't show device.
to do those step my tablet was in recovery more "fastboot usb"
can you help me?
thanks
Jack
Click to expand...
Click to collapse
You should not have factory reset if you do not know the account password. It is protected by "factory reset protection". To prevent it from being used if it is stolen. You are most likely going to need the password for the account that was logged in when you reset.
Flashing is not going to help. And as mentioned previously, you cannot unlock the bootloader now since you cannot go into developer options and turn on oem unlocking.
Dear all,
I have made numerous attempts to unlock the bootloader of my Wiko U Feel Prime, but to no avail.
(My goal is to flash TWRP, root with Magisk and install LineageOS.)
USB debugging and OEM unlocking are enabled in the developer settings.
ADB recognises the device. When I execute adb reboot bootloader, the device reboots, and doesn't get past the "powered by Android" screen – but is nonetheless found by fastboot when I run fastboot devices. Seems like the USB drivers are functioning properly, correct?
Now, when I run fastboot oem unlock, I get the following response:
Code:
...
FAILED (remote: unknown command)
finished. total time: -0.000s
The command fastboot flashing unlock gives the same result.
Moreover, fastboot getvar all displays no unlocked variable. The command fastboot getvar unlocked yields
Code:
unlocked:
By the way, this phone was shipped SIM unlocked.
I've spent hours looking around the web for solutions, but everyone (including guides specifically written for Wiko U Feel Prime) simply says "unlock the bootloader" as if it's a trivial task. And I've run out of ideas. Could anyone help?
Thank you very much.
Hi,
I've now spent quite a few frustrating hours trying to root my Alcatel 1c (model 5003D, running Android 8.1 Go) and nothing seems to work. A short overview of some of the rabbit holes I've gone down:
Root tools
Started with the obvious: root tools. In short, none that I ran work. There's a couple I haven't tried because the instructions were mostly in Russian and some googling turned up quite a few mentions of them containing malware, but other than that I've pretty much tried all the major ones.
Flashing images via fastboot
Naturally, the next place I turned was the awesome resource that is this forum. This thread gave me plenty of hope, but I was soon flummoxed by my device's fastboot mode for which a bunch of the normal features are either broken or are simply not implemented. Some examples of things that should work (and indeed work on other Alcatel phones, notably, it seems, ones that are not based on Spreadtrum) but didn't:
Code:
~/D/platform-tools > ./fastboot oem unlock
FAILED (remote: 'unknown cmd.')
fastboot: error: Command failed
Code:
~/D/platform-tools > ./fastboot oem unlock-go
FAILED (remote: 'unknown cmd.')
fastboot: error: Command failed
Code:
~/D/platform-tools > ./fastboot oem unlock-go --wipe
FAILED (remote: 'unknown cmd.')
fastboot: error: Command failed
Code:
~/D/platform-tools > ./fastboot flashing unlock
FAILED (remote: 'Not implemet.')
fastboot: error: Command failed
(note the spelling error in the error message...)
Code:
~/D/platform-tools > ./fastboot flash recovery ../recovery.img
Sending 'recovery' (28266 KB) OKAY [ 1.582s]
Writing 'recovery' FAILED (remote: 'Flashing Lock Flag is locked. Please unlock it first!')
fastboot: error: Command failed
That last one was particularly intriguing, as it suggests there is a Flashing Lock Flag that can be unlocked. I tried all of the fastboot commands that seemed relevant but couldn't find any way of setting that flag or even figuring out if it actually exists. I even rand the boot.img through strings to see if I could find something interesting, but didn't turn up anything.
Just to be clear, before doing all this I set the phone to Developer Mode and checked the "OEM unlocking" feature.
Flashing tools
I tried various tools with which it's possible to flash phones. A lot of them use fastboot under the covers which doesn't work (see above). Some of them don't but didn't work on my phone all the same, for various reasons:
SPD flash tool - After yet more Googling I stumbled upon the SPD flash tool,built specifically to flash Spreadtrum-based devices. I downloaded the latest version, installed all of the necessary USB drivers and tried to flash the phone with the stock ROM. No dice. The tool fails to connect to the device via the USB2Serial thing that it uses to communicate. No idea what's going on or why it won't work, and haven't yet mustered the courage to dive into the source code. Of course, if I do get it to work, then I have to figure out how to actually root the device using this tool. I'm guessing it will involve unpacking the ROM (a PAC file), modifying the recovery.img to a TWRP (or similar), repacking it and flashing the result. I've only managed the unpacking so far, no clue as to the other 2 steps. BTW, the SPD flash tool site als has a "factory" and a "research" tool, besides the "upgrade" tool that I tried. Unless I'm missing something, all three seem to be exactly the same (save for the color scheme).
Alcatel Mobile Upgrade S - Installs just fine and then allows you to choose your phone out of a dropdown... that doesn't include my model.
Sugar MTK/QCT - Installed it and the necessary drivers but it can't find my phone, no matter what I try. Also, I keep reading that it needs login credentials (wut?)
Conclusion: argh!
So, nothing so far. Since it's a Spreadtrum phone it has an engineering mode that can be explored with an APK I found in this thread. Nothing in the settings it reveals appears to be of any help though. I also contacted the makers of the AIO Alcatel toolkit to see if they had any ideas, but after I explained the situation one of them concluded "Hmmm. New one on me". Needless to say I also tried searching this forum for more tips, but googling 'site:forum.xda-developers.com "5003D"' returns no hits.
For now, I'm forced to conclude that there is a lot of really awesome tooling out there created by some very talented people, but none of it works on my phone. As of yet the 5003D appears pretty unrootable. If anyone has any tips to help me along or point me in the right direction, I would be very appreciative.
bump
bump
Then type the command to show the device
fastboot -i 0x1bbb devices
Execute the next command which will show device info including bootloader status (e.g. locked).
fastboot -i 0x1bbb oem device-info
This command is to unlock the bootloader on Alcatel device
fastboot -i 0x1bbb oem unlock
Repeat Step and you should see “Device unlocked: true”
To reboot normally type:
fastboot -i 0x1bbb reboot
Done
This command is to unlock the bootloader on Alcatel device
fastboot -i 0x1bbb oem unlock
Click to expand...
Click to collapse
I've tried that a bunch of times in an bunch of different ways, and unfortunately that doesn't work for this particular phone.
lotus118 said:
I've tried that a bunch of times in an bunch of different ways, and unfortunately that doesn't work for this particular phone.
Click to expand...
Click to collapse
Rooting your phone's Android does NOT require you fiddle around with its boot-loader. Forget trying to make use of Fastboot.
So how would I go about this without using fastboot?
lotus118 said:
So how would I go about this without using fastboot?
Click to expand...
Click to collapse
1. Open Windows command prompt and input the following comand
Code:
adb devices
2. Start the ADB sideload in your phone's recovery
3. Then input the following command in the Windows command prompt
Code:
adb sideload <filename.Zip>
where <filename.zip> must of course be the real full filepathname of ZIP to get flashed
my device is asus zenfone c z007, anyone know how to unlock this device, or related to unlock this device. I has been searching all the threads but I can't find one, please help me to unlockbootlader this device. I only find to unlock app for asus A400CG with the same specification.http://dlcdnet.asus.com/pub/ASUS/ZenFone/A400CG/Unlock_Tool_A400CG.zip from this threads https://forum.xda-developers.com/zenfone-4/cm-12-1-cyanogenmod-12-1-asus-zenfone-4-t3249637.
.
.
here the specification + compare = https://www.ubergizmo.com/products/lang/en_us/devices/zenfone-c,zenfone-4/
@ArthurBalaOs
Before wasting your time with this check for boot-loader can get unlocked
Code:
adb devices
adb shell "getprop ro.oem_unlock_supported"
If returned value is 1, then it's supported otherwise it's not.
jwoegerbauer said:
@ArthurBalaOs
Before wasting your time with this check for boot-loader can get unlocked
Code:
adb devices
adb shell "getprop ro.oem_unlock_supported"
If returned value is 1, then it's supported otherwise it's not.
Click to expand...
Click to collapse
ok it's nothing happened, but I try this command to my other device which supporting oem unlock it's nothing happened to. why ? btw, thanks :good:
0
ArthurBalaOs said:
ok it's nothing happened, but I try this command to my other device which supporting oem unlock it's nothing happened to. why ? btw, thanks :good:
Click to expand...
Click to collapse
May be they forgot to populate that entry...
Because not ADB but Fastboot is needed to unlock a Android device's boot-loader you always can try
Code:
fastboot devices
fastboot oem unlock
fastboot reboot
fastboot unlock-info
If outpout of last command is TRUE, then boot-loader got unlocked.
jwoegerbauer said:
May be they forgot to populate that entry...
Because not ADB but Fastboot is needed to unlock a Android device's boot-loader you always can try
Code:
fastboot devices
fastboot oem unlock
fastboot reboot
fastboot unlock-info
If outpout of last command is TRUE, then boot-loader got unlocked.
Click to expand...
Click to collapse
[COLOR="RESULT : FAIL (unknown OEM command)"][/COLOR]
that"s the result, what's that mean?
Seppppx said:
I checked the Asus website and I found no official unlocking tool for the zenfone c. I don't think I missed anything because other model have that.
Click to expand...
Click to collapse
nahh. they release the source code and kernel source, without unlocking tool. I mean everytime I trying to force unlock or force installing twrp the result always error
ArthurBalaOs said:
[COLOR="RESULT : FAIL (unknown OEM command)"][/COLOR]
that"s the result, what's that mean?
Click to expand...
Click to collapse
As I can see the version of Fastboot you use doesn't support the subcommand "OEM unlock":
Each OEM/Carrier has its own version of the Fastboot driver.
Try this instead
Code:
fastboot flashing unlock
BTW:
Become familiar with Fastboot subcommands supported on your device. Simply run
Code:
fastboot
or
Code:
fastboot OEM
you can see on this thread.
https://forum.xda-developers.com/zenfone-4/how-to-unlock-bootloader-asus-zenfone-c4-t3577340/amp/
Hi
I recently upgraded a Honor 5c to Nougat(which works)NRD90M test keys build. I did this through Flashfire to try and preserve root. It failed(what a surprise).
The device is recognised now with 'fastboot devices', by running ADB using root in Linux.
I can get into bootloader screen using fastboot and have unlocked the phone AGAIN to be sure. BUT, cannot flash TWRP which is vital. The error now is:
Sending 'boot.img' (24464 KB) OKAY [ 0.869s]
Booting FAILED (remote: 'Command not allowed') fastboot: error: Command failed
This suggests the phone is locked which is absurd. I think this is a permission problem within Android, it that possible?
It doesn't matter how I'm going to root, if I can't communicate the whole thing is usesless.
The same issue continues with ADB in Win10
Any thoughts hear, because I've trawled Google.
thanks
To clarify things: ADB and Fastboot are 2 completly different things. Fastboot deals with device's bootloader, whereas ADB deals with device's Android OS.
Run this command sequence
Code:
fastboot devices
fastboot getvar all 2>%TEMP%\phoneinfo.txt
fastboot reboot
type "%TEMP%\phoneinfo.txt" | more
which will get you a list of various variables on the phone with model and such useful things.
jwoegerbauer said:
To clarify things: ADB and Fastboot are 2 completly different things. Fastboot deals with device's bootloader, whereas ADB deals with device's Android OS.
Run this command sequence
Code:
fastboot devices
fastboot getvar all 2>%TEMP%\phoneinfo.txt
fastboot reboot
type "%TEMP%\phoneinfo.txt" | more
which will get you a list of various variables on the phone with model and such useful things.
Click to expand...
Click to collapse
Excuse if this format is incorrect
Thanks for that.
ADB and Fastboot are 2 completly different things
Click to expand...
Click to collapse
Sure
fastboot devices
Click to expand...
Click to collapse
MQH4C17330000094 fastboot
fastboot getvar all 2>%TEMP%\phoneinfo.txt
Click to expand...
Click to collapse
Returns to prompt
fastboot reboot
Click to expand...
Click to collapse
Works
type "%TEMP%\phoneinfo.txt" | more
Click to expand...
Click to collapse
getvar:all FAILED (remote: 'Command not allowed')
Finished. Total time: 0.005s
Same thing again
Cliff
cliffhanger54 said:
getvar:all FAILED (remote: 'Command not allowed')
Click to expand...
Click to collapse
That a Fastboot cmd does not work ( e.g. error Command not allowed ) is not unusual because Fastboot is different from version to version and also depends on how OEM/Carrier implemented it.
Again:
Bootloader and Android OS are different things, as this is same on PC where UEFI/BIOS and Windows OS are different things, too. A device's bootloader doesn't depend on any permissions granted within device's OS. A bootloader is a kind of software that runs as soon as you start up your phone. It tells the phone which programs are loading in order to make your phone run smoothly. This software packages all the instructions that are supposed to boot the Android OS, and initializes hardware and serves as security checkpoint.
Don't mix things up.
BTW:
Whether device's bootloader is unlockable / is already unlocked or not is stored in system file named build.prop.
Code:
adb devices
adb shell "getprop ro.oem_unlock_supported"
If returned value is 1, then unlocking bootloader is supported otherwise it's not.
or
Code:
fastboot devices
fastboot oem device-info
If "Device unlocked: true" is shown then bootloader is unlockedd.
jwoegerbauer said:
That a Fastboot cmd does not work ( e.g. error Command not allowed ) is not unusual because Fastboot is different from version to version and also depends on how OEM/Carrier implemented it.
Again:
Bootloader and Android OS are different things, as this is same on PC where UEFI/BIOS and Windows OS are different things, too. A device's bootloader doesn't depend on any permissions granted within device's OS. A bootloader is a kind of software that runs as soon as you start up your phone. It tells the phone which programs are loading in order to make your phone run smoothly. This software packages all the instructions that are supposed to boot the Android OS, and initializes hardware and serves as security checkpoint.
Don't mix things up.
BTW:
Whether device's bootloader is unlockable / is already unlocked or not is stored in system file named build.prop.
Code:
adb devices
adb shell "getprop ro.oem_unlock_supported"
If returned value is 1, then unlocking bootloader is supported otherwise it's not.
or
Code:
fastboot devices
fastboot oem device-info
If "Device unlocked: true" is shown then bootloader is unlockedd.
Click to expand...
Click to collapse
Thanks again for answering. I understand what you say. I've used Linux for 20 years and understand the differences. But where does this leave us/me. I should be able to flash TWRP into the recovery partition surely? Or are we dependent on software versions here as you say? It would be relatively easy in Linux and of course Android is based on it.
cliffhanger54 said:
I should be able to flash TWRP into the recovery partition surely?
Click to expand...
Click to collapse
TWRP completely removes device's default /recovery partition if it exists ( exists only on A-only Android devices), TWRP creates its own in device's /boot partition.
To flash TWRP on A-only ( or on current active boot slot if it's an A/B ) device
Code:
fastboot devices
fastboot flash boot <PATH_ON_PC_TO_YOUR_TWRP_IMAGE_HERE>
jwoegerbauer said:
TWRP completely removes device's default /recovery partition if it exists ( exists only on A-only Android devices), TWRP creates its own in device's /boot partition.
To flash TWRP on A-only ( or on current active boot slot if it's an A/B ) device
Code:
fastboot devices
fastboot flash boot <PATH_ON_PC_TO_YOUR_TWRP_IMAGE_HERE>
Click to expand...
Click to collapse
Thanks I think I've tried this one. I do get a different response though:
'fastboot: error: cannot get boot partition size'
I've seen suggestions that formating the boot partition is required - sounds extreme.
Why not simply re-flash device's Stock ROM to restore it to its original state ?
:good:
Sukrus said:
:good:
Click to expand...
Click to collapse
Yes wouldn't that be great. Have tried that from the beginning when I couldn't flash TWRP.
Put the Update.app on the SDcard, reboot the phone, hold down the buttons(tried them all), Bingo, it always takes me to eRecovery and how useless that is.
I have backups of Marshmallow with TWRP and Flashfire, which is why I took the flash TWRP route.
Wish I'd never upgaded now, although was forced to because of banking.
thanks
@cliffhanger54
I have noticed that current thread basically is a duplicate of this thread you started on XDA some days ago, too.
jwoegerbauer said:
@cliffhanger54
I have noticed that current thread basically is a duplicate of this thread you started on XDA some days ago, too.
Click to expand...
Click to collapse
Yes, couldn't really get anyone to answer, needed more info. Apologies. Will cease other question
Cliff
cliffhanger54 said:
Yes, couldn't really get anyone to answer, needed more info. Apologies. Will cease other question
Cliff
Click to expand...
Click to collapse
Right. After many attempts at other things I became convinced this was a locked bootloader problem despite the phone saying it was unlocked. Anyway have persisted in unlocking the phone several times and am now at a screen saying 'Your device is unlocked' but it also says 'you device is booting now'. But that's as far as it goes. If I turn the phone off it comes back to this screen and holding the power button+-volume also comes back to this screen, i.e I can't turn it off. How do I get back to the bootloader/fastboot mode or is this a genuine brick?
thanks
Cliff
cliffhanger54 said:
Right. After many attempts at other things I became convinced this was a locked bootloader problem despite the phone saying it was unlocked. Anyway have persisted in unlocking the phone several times and am now at a screen saying 'Your device is unlocked' but it also says 'you device is booting now'. But that's as far as it goes. If I turn the phone off it comes back to this screen and holding the power button+-volume also comes back to this screen, i.e I can't turn it off. How do I get back to the bootloader/fastboot mode or is this a genuine brick?
thanks
Cliff
Click to expand...
Click to collapse
Okay finally solved it. Let the battery run down as all I was getting was a bootloop. I was then able to get into fastboot mode with the necessary keys. From here i flashed TWRP but this required numerous attempts with different versions, finally got '3.1.1 venus' to load and the rest was straight forward!
thanks to everyone