Related
I have 20a firmware and that should be unlockable. Ive tried different solutions but none of them works.
Ive tried with script but it says permission denied.
Ive tried with the all in one tool but when it reboots it shows an error message at the top of the screen "ERROR : boot image signature".
Its just my fault or i just cant unlock my phone with anything?
If i try from terminal the adb reboot oem-unlock line reboots my phone but it also gives unlock permission denied error message.
So I cant unlock this... any ideas?
XxXDarknessXxX said:
I have 20a firmware and that should be unlockable. Ive tried different solutions but none of them works.
Ive tried with script but it says permission denied.
Ive tried with the all in one tool but when it reboots it shows an error message at the top of the screen "ERROR : boot image signature".
Its just my fault or i just cant unlock my phone with anything?
If i try from terminal the adb reboot oem-unlock line reboots my phone but it also gives unlock permission denied error message.
So I cant unlock this... any ideas?
Click to expand...
Click to collapse
I did it by doing this you can give it a try!! to unlock bootloader ( so you can flash roms with kernels) go to this thread, http://forum.xda-developers.com/show....php?t=2224020
and download the BL_unlock_new .rar file when its download copy it to your desktop on pc and then extract it to desktop on pc . now make sure your phone is not connected to your computer go to phone settings,then go to development options, and then select usb debugging on. once debugging is on now connect your phone to pc wait for it to connect you can keep your phone on charging mode. now open the BL_unlocking_new extracted folder on desktop on pc and double click on the BL_unlock file a box should open up on your desktop asking you to tap a key to continue so press a key now your phone should reboot and some white writing will appear on screen .on your desktop the bottom line should say please... now tap a key on computer it should say press any key to continue < waiting for device> now disconnect phone from computer look on phone screen it should say now ready! now hold power button for 10 secs and let phone reboot. to test if bootloader is unlocked on phone go to dail pad and dail this 3845#*880# you should get the hidden menu on your screen scroll down to bootloader unlock check and select then select bootloader unlock check and hopefully it should say unlock...
I had the same problem as you. Tried everything, but the only one that works is this one:
http://forum.xda-developers.com/showthread.php?t=2245415 it's also the simplest way.
Goodluck!
Sent from my LG-P880 using xda app-developers app
Thanks guys i figured out how to unlock on my own... but really, thanks for the help
Hello everyone, I'm trying to unlock my bootloader but I have hit a roadblock and cannot seem to find anything that helps.
The part where i am stuck at is that when i enter "fastboot.exe -i 0x0fce getvar version" all i get is "waiting for device" infinitely.
I know the phone is in fastboot mode because the blue light is on
It seems my pc isn't recognizing my phone when it's in fastboot mode. I can see my phone in windows device manager as "S1 boot fastboot" but when i try to update the drivers manually using the drivers provided by sony, i just get an update failed screen.
any help would be much appreciated, i'm sure it's something dumb that i did, but i just can't figure out what.
KlamKhowder said:
Hello everyone, I'm trying to unlock my bootloader but I have hit a roadblock and cannot seem to find anything that helps.
The part where i am stuck at is that when i enter "fastboot.exe -i 0x0fce getvar version" all i get is "waiting for device" infinitely.
I know the phone is in fastboot mode because the blue light is on
It seems my pc isn't recognizing my phone when it's in fastboot mode. I can see my phone in windows device manager as "S1 boot fastboot" but when i try to update the drivers manually using the drivers provided by sony, i just get an update failed screen.
any help would be much appreciated, i'm sure it's something dumb that i did, but i just can't figure out what.
Click to expand...
Click to collapse
unlock it using flash tool, just press unlock wait and enter the code.. done
KlamKhowder said:
Hello everyone, I'm trying to unlock my bootloader but I have hit a roadblock and cannot seem to find anything that helps.
The part where i am stuck at is that when i enter "fastboot.exe -i 0x0fce getvar version" all i get is "waiting for device" infinitely.
I know the phone is in fastboot mode because the blue light is on
It seems my pc isn't recognizing my phone when it's in fastboot mode. I can see my phone in windows device manager as "S1 boot fastboot" but when i try to update the drivers manually using the drivers provided by sony, i just get an update failed screen.
any help would be much appreciated, i'm sure it's something dumb that i did, but i just can't figure out what.
Click to expand...
Click to collapse
try using different usb cable/ different port.
Had same problem....some driver was missing
Sent from my C5503 using xda app-developers app
I've finally gotten flash tool to work, however now it gives me an error saying that my device cannot be officially unlocked,
EDIT: i'm pretty sure i've unlocked the bootloader now, as flashtool had me enter an unlock code and my device has had all of its data reset.
however my issues continue as now flashtool utterly refuses to pick up my device. I have re-installed all drivers, flashtool, etc but still nothing.
sometimes it may have conflicts when flashtool and other tools use their own instance of adb or fastboot. I think the best thing to do now is reinstalling regular drivers normally. don't forget to enable usb debugging...
this may be useful :
Code:
[I]ADB_PATH[/I]\adb kill-server
exit
create a text file, paste this code then save it as ADB - Kill.cmd
After installing the "15 seconds adb installer", I shift clicked the folder with my twrp file, "twrp-3.0.2-0-tbltetmo.img" to open the command prompt and type in "adb reboot bootloader" , causing my screen to go into boot loader mode. [ e.g. image ] ]So far, everything is going well, according to this guide.. However, the problem is the next step. Once in boot loader mode, i type in "fastboot flash recovery twrp-3.0.2-0-tbltetmo.img" . Instead of masses of text appearing, I instead receive the message: "Waiting for device." To be honest, I think my problem lies in the fact that before i went into boot loader mode, my phone was detected by my pc, but after it shifts to boot loader mode, it stops being detected, this causing the "waiting for device" message. However, even though I know the cause, I can't find any means to fix it after searching for hours. Also, yes, I enabled allow unknown sources and usb debugging. I've also went to T-Mobile's website to install their usb driver.
Jordan Miles said:
After installing the "15 seconds adb installer", I shift clicked the folder with my twrp file, "twrp-3.0.2-0-tbltetmo.img" to open the command prompt and type in "adb reboot bootloader" , causing my screen to go into boot loader mode. [ e.g. image ] ]So far, everything is going well, according to this guide.. However, the problem is the next step. Once in boot loader mode, i type in "fastboot flash recovery twrp-3.0.2-0-tbltetmo.img" . Instead of masses of text appearing, I instead receive the message: "Waiting for device." To be honest, I think my problem lies in the fact that before i went into boot loader mode, my phone was detected by my pc, but after it shifts to boot loader mode, it stops being detected, this causing the "waiting for device" message. However, even though I know the cause, I can't find any means to fix it after searching for hours. Also, yes, I enabled allow unknown sources and usb debugging. I've also went to T-Mobile's website to install their usb driver.
Click to expand...
Click to collapse
Possibly the cable. Not sure if the USB drivers you got from T-Mobile's website are the same as the one that TEKHD posted in his Tutorial thread for rooting...but I use those and with my original cable. (sometimes with my Xbox One charge cable) Hope that helps.
I know that if I use a a cheap or thin cable, I get problems.
SiNJiN76 said:
Possibly the cable. Not sure if the USB drivers you got from T-Mobile's website are the same as the one that TEKHD posted in his Tutorial thread for rooting...but I use those and with my original cable. (sometimes with my Xbox One charge cable) Hope that helps.
I know that if I use a a cheap or thin cable, I get problems.
Click to expand...
Click to collapse
Thanks for your reply. I gave up using the usb cable method to connect to adb. Instead, I just flashed it with Odin, which works (strangely, even though my device still didn't appear under "Computer")
I have an update waiting to be done on my P9, every time I go to do it, it fails and comes up saying reboot system, any ideas how to fix this??
Your BOOTLOADER is unlock ?
Yes mate but I can't seem to lock it, when I try to, on reboot it white screens with the android symbol then sits like that unless I manually reboot it
swannyboy83 said:
Yes mate but I can't seem to lock it, when I try to, on reboot it white screens with the android symbol then sits like that unless I manually reboot it
Click to expand...
Click to collapse
You're on Nougat?
Marshmallow
Just follow this to lock bootloader
https://forum.xda-developers.com/p9/themes/antic-theme-t3664356
I tried it and it's come up saying device has failed verification, it attempts the update and fails then reboots
swanny83 said:
I tried it and it's come up saying device has failed verification, it attempts the update and fails then reboots
Click to expand...
Click to collapse
try this, i got from emui website
Note: to re-lock the bootloader after unlocking it, restore the device’s software to the Huawei official version using a microSD card then switch the device to fastboot mode and enter “fastboot oem unlock ****************” in the computer’s command prompt, where * refers to the 16-digit unlock password. The device will then restart, and the bootloader lock status will change to “Bootloader Lock State: RELOCKED”.
Well I tried, I've not got a clue what I am doing, it's still unlocked so I will leave it as it is, I have a working phone don't want to mess around with it and end up totally ruining it
Try installing the update via dload
... (3 dot option) and then, download latest full build inside updater setings, thry that need to be around 2gb file
Ok so I managed to sort this out...... finally, just one thing else how can I change the lock screen picture, it gives me the option to do so but I select the picture but remains the same as it was, any ideas?
I've ran into the following problem:
came home and try to open my phone, code doesn't work to unlock screen. Unless I'm going insane was sure the code was correct twice.
Restart phone, stuck on enjoy.now for a long time, goes to alcatel logo, then goes into an Android Recovery message saying "can't load Android system. Your data may be corrupt."
Then 2 options: try again or Factory data reset.
I've managed to find the following possible solution: https://glebovdev.medium.com/how-to-fix-cant-load-android-system-issue-8a5b0ead5a15
..but I can't even get to recovery screen with more than 2 options. It would be a huge pain if I have to factory reset.. should it be possible to get to recovery mode on my phone as well?
Is there any possible way to get the data off the phone (mainly Google Authenticator to which I'm not sure I have the codes anymore)?
Thanks
BrickAlcatel said:
I've ran into the following problem:
came home and try to open my phone, code doesn't work to unlock screen. Unless I'm going insane was sure the code was correct twice.
Restart phone, stuck on enjoy.now for a long time, goes to alcatel logo, then goes into an Android Recovery message saying "can't load Android system. Your data may be corrupt."
Then 2 options: try again or Factory data reset.
I've managed to find the following possible solution: https://glebovdev.medium.com/how-to-fix-cant-load-android-system-issue-8a5b0ead5a15
..but I can't even get to recovery screen with more than 2 options. It would be a huge pain if I have to factory reset.. should it be possible to get to recovery mode on my phone as well?
Is there any possible way to get the data off the phone (mainly Google Authenticator to which I'm not sure I have the codes anymore)?
Thanks
Click to expand...
Click to collapse
It could be that your device is trying to boot to the inactive slot, verify in fastboot mode which slot is marked as active and try to boot either in A and/or in B slot.
Idk if I'm doing something wrong but holding volume up or down as it restarts, the only boot screen I get is:
Android Recovery
TCL/5003d_EEEA/Curie
8.1.0/OPM2.171019.012/5003d_ALWE_EEA_V3
user/release-keys
(aforementioned error)
Try again
Factory data reset
fastboot mode should show other options right?
BrickAlcatel said:
Idk if I'm doing something wrong but holding volume up or down as it restarts, the only boot screen I get is:
Android Recovery
TCL/5003d_EEEA/Curie
8.1.0/OPM2.171019.012/5003d_ALWE_EEA_V3
user/release-keys
(aforementioned error)
Try again
Factory data reset
fastboot mode should show other options right?
Click to expand...
Click to collapse
Well, fastboot is to interact through fastboot commands and you can check from there the slot that is active with
Code:
fastboot getvar all
and you see something like slot_active xx
When I run adb devices in powershell it does not show any devices connected (although the device does show as connected in Windows device management).
In device management it does show as "MTP USB device".
Is this likely to be a driver issue?
BrickAlcatel said:
When I run adb devices in powershell it does not show any devices connected (although the device does show as connected in Windows device management).
In device management it does show as "MTP USB device".
Is this likely to be a driver issue?
Click to expand...
Click to collapse
Device has to be power on to respond to adb commands and from what you were telling your device is bricked..
It's technically powered on but yes still does nothing but bootloop and try again/factory reset screen. There's no possible other way to get to Android recovery mode when the volume down+power option doesn't seem to be working?
BrickAlcatel said:
It's technically powered on but yes still does nothing but bootloop and try again/factory reset screen. There's no possible other way to get to Android recovery mode when the volume down+power option doesn't seem to be working?
Click to expand...
Click to collapse
Device has to be strongly and consistently on so adb commands can work, they can't work while in bootloop so forget it this way.
What you can try is tipically pwr + vol. up and pwr + vol. dwn, one of them will take you to fastboot mode where you can give it a try to what I pointed out in previous outputs.
OK some progress.. apparently you have to let go of power button and volume up right as the alcatel logo appears, the timing seems to matter. I'm now able to see Android recovery with more options at least so will try from there.
Thanks again for taking time to reply.
I've tried
Code:
fastboot getvar all
this results in <waiting for any device>
adb devices still shows no list of devices even though in Device Manager it shows as "Fastboot gadget" under other devices
I've downloaded drivers from Alcatel website in case it's a driver issue but on the list of model numbers during setup mine (5003D_EEA according to recovery screen) doesn't show.
I do see a bunch of websites allegedly offering these specific drivers but assume it's risky to download from anywhere other than Alcatel official site.
BrickAlcatel said:
I've tried
Code:
fastboot getvar all
this results in <waiting for any device>
adb devices still shows no list of devices even though in Device Manager it shows as "Fastboot gadget" under other devices
I've downloaded drivers from Alcatel website in case it's a driver issue but on the list of model numbers during setup mine (5003D_EEA according to recovery screen) doesn't show.
I do see a bunch of websites allegedly offering these specific drivers but assume it's risky to download from anywhere other than Alcatel official site.
Click to expand...
Click to collapse
It seems to be a reliable site https://www.androidusbdrivers.com/alcatel-1-usb-drivers/ it offers the 4 different drivers needed covering all the modes that your device can enter to.
I would recommend mainly two things:
- Uninstall/remove firstly all the drivers that you don't use, it could be something for an old android/tablet that you don't use anymore.
- Don't swap the cable data from/for other device, any of them have its own type of connection, use the same proper cable data for only one device.
From there the typical first step in fastboot is just typing
Code:
fastboot devices
], if the message is "waiting for device" then it's not working.
hi im having the exact same problem, but cant get out of this. Could somebody maybe help me? How did you eventually fixed it? kindregards