Related
hey guys
i have a HTC Sensation that is password locked, but the real problem is that it won't enter recovery mode.
the volume down key is working as i've tested it in a "sos call", the volume up doesn't work when the phone is turned, but that's not important as it's not needed.
is there any other way to get into recovery mode?
also, if i hold the up key with the power switch, it boots up in "safe mode"
mmcr said:
hey guys
i have a HTC Sensation that is password locked, but the real problem is that it won't enter recovery mode.
the volume down key is working as i've tested it in a "sos call", the volume up doesn't work when the phone is turned, but that's not important as it's not needed.
is there any other way to get into recovery mode?
also, if i hold the up key with the power switch, it boots up in "safe mode"
Click to expand...
Click to collapse
did you try to pull out the battery?
if not take it off,put it again
then hold volume down + power button until it shows the bootloader screen
mmcr said:
hey guys
i have a HTC Sensation that is password locked, but the real problem is that it won't enter recovery mode.
the volume down key is working as i've tested it in a "sos call", the volume up doesn't work when the phone is turned, but that's not important as it's not needed.
is there any other way to get into recovery mode?
also, if i hold the up key with the power switch, it boots up in "safe mode"
Click to expand...
Click to collapse
several times sir, even went as far as draining the battery inside the phone completely, trying it with another battery, leaving the battery out of the phone for a whole day...
are there no usb hacks or something like there is with the samsung android phones?
mmcr said:
several times sir, even went as far as draining the battery inside the phone completely, trying it with another battery, leaving the battery out of the phone for a whole day...
are there no usb hacks or something like there is with the samsung android phones?
Click to expand...
Click to collapse
Are you on a stock rom? if you are the you would have to have un-ticked fastboot from the settings to be able to boot into the bootloader...
try to attach the device to a usb port of a laptop and see if the usb debugging symbol shows up in the status bar. if it does you can use the adb command adb reboot recovery to force a jump into the recovery.
heavy_metal_man said:
Are you on a stock rom? if you are the you would have to have un-ticked fastboot from the settings to be able to boot into the bootloader...
try to attach the device to a usb port of a laptop and see if the usb debugging symbol shows up in the status bar. if it does you can use the adb command adb reboot recovery to force a jump into the recovery.
Click to expand...
Click to collapse
i have no idea if the phone has a stock rom on it, can't access the menu and it's not in usb debugging mode, coz when i access it in adb cmd i get this msg, "error: device not found"
the pc does pick it up, but as a disk drive anything else i can do?
mmcr said:
i have no idea if the phone has a stock rom on it, can't access the menu and it's not in usb debugging mode, coz when i access it in adb cmd i get this msg, "error: device not found"
the pc does pick it up, but as a disk drive anything else i can do?
Click to expand...
Click to collapse
ok try battery pull, the hold down both volume keys and power for 10 seconds to see if it boots into stock recovery.
heavy_metal_man said:
ok try battery pull, the hold down both volume keys and power for 10 seconds to see if it boots into stock recovery.
Click to expand...
Click to collapse
boots up in safe mode
mmcr said:
boots up in safe mode
Click to expand...
Click to collapse
hmmmm. running out of ideas now. was this your device? do you know the google account ect?
heavy_metal_man said:
hmmmm. running out of ideas now. was this your device? do you know the google account ect?
Click to expand...
Click to collapse
no sir, i have a cellphone repair kiosk, the client doesn't remember the account that he used to create the security feature and his kid busted the pattern lock.
mmcr said:
no sir, i have a cellphone repair kiosk, the client doesn't remember the account that he used to create the security feature and his kid busted the pattern lock.
Click to expand...
Click to collapse
can you take a photo of the pattern lock screen
also what do you know about the device? is it eu,uk,us? also what carrier is the device on? is it on ice cream sandwich or gingerbread? you may be able to run a RUU (rom update utility) on the device, updating the firmware and remove the lock that is currently on the device.
So, no bootloader? When you hit vol down + power it should land you in the bootloader screen, where you then select recovery. Have you tried with the cover, SD, and SIM removed from the phone?
se1000 said:
So, no bootloader? When you hit vol down + power it should land you in the bootloader screen, where you then select recovery. Have you tried with the cover, SD, and SIM removed from the phone?
Click to expand...
Click to collapse
i've tried that several times bro, just the same out come everytime
heavy_metal_man said:
can you take a photo of the pattern lock screen
also what do you know about the device? is it eu,uk,us? also what carrier is the device on? is it on ice cream sandwich or gingerbread? you may be able to run a RUU (rom update utility) on the device, updating the firmware and remove the lock that is currently on the device.
Click to expand...
Click to collapse
i don't know any of the above, how do i check any of these without getting into the bootloader? the device only connect to the pc as a disk drive.
mmcr said:
i don't know any of the above, how do i check any of these without getting into the bootloader? the device only connect to the pc as a disk drive.
Click to expand...
Click to collapse
you will need to talk to the owner of the phone, without that info your stuffed tbh. with fastboot enabled in the stock rom you cannot boot into bootloader. without the info like what carrier they are on you dont know what ruu to run to reset the device. without usb debugging you cannot use the pc to send commands as far a i am aware :/ assuming you have the correct htc drivers installed connect the device to the pc, open cmd in your adb directory and type in adb reboot bootloader and see if it responds. again without that info you've pretty much had it. you can try to flash ruu's from the pc at random in the hope that you find the correct firmware and cid, but without usb debugging on there is no guarantee that the ruu will even find it.
heavy_metal_man said:
you will need to talk to the owner of the phone, without that info your stuffed tbh. with fastboot enabled in the stock rom you cannot boot into bootloader. without the info like what carrier they are on you dont know what ruu to run to reset the device. without usb debugging you cannot use the pc to send commands as far a i am aware :/ assuming you have the correct htc drivers installed connect the device to the pc, open cmd in your adb directory and type in adb reboot bootloader and see if it responds. again without that info you've pretty much had it. you can try to flash ruu's from the pc at random in the hope that you find the correct firmware and cid, but without usb debugging on there is no guarantee that the ruu will even find it.
Click to expand...
Click to collapse
yeah, tried the adb reboot recovery, no dice. just error, no device connected.
the owner bought it 2nd hand, so he has no clue, i'm just going to return it. pity that htc doesn't have a "usb key" like samsung that forces "download mode" on the android devices
mmcr said:
yeah, tried the adb reboot recovery, no dice. just error, no device connected.
the owner bought it 2nd hand, so he has no clue, i'm just going to return it. pity that htc doesn't have a "usb key" like samsung that forces "download mode" on the android devices
Click to expand...
Click to collapse
indeed so. but you cannot fault it as a security measure :silly:
I think i have a huge problem here. I flashed Paranoid and my phone now is stuck on boot logo, the problem is that i cant turn off the phone nor star fastboot cuz my volume down key is not working... is there any way to get into fastboot using commands or sommething? thanks in advance.
DualDark said:
I think i have a huge problem here. I flashed Paranoid and my phone now is stuck on boot logo, the problem is that i cant turn off the phone nor star fastboot cuz my volume down key is not working... is there any way to get into fastboot using commands or sommething? thanks in advance.
Click to expand...
Click to collapse
If you are stuck in bootloop you won't be able to enter bootloader directly by pushing Powe+VolDown.
Firstly you have to power off the device (Power+VolUp+VolDown) and, when the screen goes off, you will be able to enter bootloader again (VolDown+Power)
I hope it helps,
-Z-
skorpionvenom said:
If you are stuck in bootloop you won't be able to enter bootloader directly by pushing Powe+VolDown.
Firstly you have to power off the device (Power+VolUp+VolDown) and, when the screen goes off, you will be able to enter bootloader again (VolDown+Power)
I hope it helps,
-Z-
Click to expand...
Click to collapse
thank you, but the problem is that my voldown key is not working, it broke down a few days ago...
DualDark said:
thank you, but the problem is that my voldown key is not working, it broke down a few days ago...
Click to expand...
Click to collapse
Can you detect your phone via adb ?
--> adb devices
if the answer is yes, you can just type
--> adb reboot recovery (I hope that you have twrp because that's a touch recovery)
skorpionvenom said:
If you are stuck in bootloop you won't be able to enter bootloader directly by pushing Powe+VolDown.
Firstly you have to power off the device (Power+VolUp+VolDown) and, when the screen goes off, you will be able to enter bootloader again (VolDown+Power)
I hope it helps,
-Z-
Click to expand...
Click to collapse
skorpionvenom said:
Can you detect your phone via adb ?
--> adb devices
if the answer is yes, you can just type
--> adb reboot recovery (I hope that you have twrp because that's a touch recovery)
Click to expand...
Click to collapse
Tried... but when in bootlogo and type it, not any device is shown...
DualDark said:
Tried... but when in bootlogo and type it, not any device is shown...
Click to expand...
Click to collapse
you can always try fastboot, even if I don't know if it's gonna work:
--> fastboot reboot-bootloader
skorpionvenom said:
you can always try fastboot, even if I don't know if it's gonna work:
--> fastboot reboot-bootloader
Click to expand...
Click to collapse
didnt work either... it just said <waiting for device>... damn it... ¬¬
DualDark said:
didnt work either... it just said <waiting for device>... damn it... ¬¬
Click to expand...
Click to collapse
Some users reported that it may take a while before the phone gets detected... alternatively you can try to change USB port.
If you cannot physically enter bootloader and you do not have access to either adb or fastboot, I am afraid that I don't know how to help you :crying:
skorpionvenom said:
Some users reported that it may take a while before the phone gets detected... alternatively you can try to change USB port.
If you cannot physically enter bootloader and you do not have access to either adb or fastboot, I am afraid that I don't know how to help you :crying:
Click to expand...
Click to collapse
I let it detecting since my last post till' this one and nothing happens... imma try changing to another usb port... this must be the most stupid half brick ever ¬¬
DualDark said:
I let it detecting since my last post till' this one and nothing happens... imma try changing to another usb port... this must be the most stupid half brick ever ¬¬
Click to expand...
Click to collapse
I honestly do not believe that your device is bricked... it just sucks that you cannot use the physical VolDown... I am pretty sure that if you get that fixed than you'll be able to restore your phone
skorpionvenom said:
I honestly do not believe that your device is bricked... it just sucks that you cannot use the physical VolDown... I am pretty sure that if you get that fixed than you'll be able to restore your phone
Click to expand...
Click to collapse
well i think so, but it is a brick till' i get fixed it... the problem is that the people that repairs in my country is like "oh this is a very new model, it'll be expensive to fix it" ¬¬, and also i cant use the warranty, im pretty sure they wont realise that i unlocked the bootloader, but the custom bootlogo is gonna be the problem...
anyway thanks for your help, now im on my way to check it out how much will cost repair the button...
So guys, the thing is: I haven't found a way to root nor to unlock the bootloader in this phone.
Focusing on the bootloader, there is an option in the Developer options which says "OEM unlocking", that supposedly allows the bootloader to be unlocked. Plugging the phone on the pc USB and using adb to get into fastboot works fine, but after typing "fastboot flashing unlock" the command prompt keeps on waiting with "..." for the next phone's action, that's where the problem begins: on the cellphone screen, right after the warnings about the consequences of unlocking the bootloader, appears: "Press the Volume UP/Down buttons to select Yes or No." If Volume_Down is pressed, it returns to fastboot, but if Volume_UP is pressed nothing happens, literally nothing, Power button also does nothing, the only one who works is Volume_Down, making it unable to unlock the bootloader via this method.
I tried to use "adb shell input keyevent 24" (knowing it wouldn't work) to try to send the Volume_Up command from the pc.
So I wanna know if there is a way that, through that fastboot waiting instance (the three dots "..."), I can send the Volume_Up command from the pc, enabling the Bootloader to be unlocked, making the root easy or even possible.
Thanks in advance!
Matt1355 said:
So guys, the thing is: I haven't found a way to root nor to unlock the bootloader in this phone.
Focusing on the bootloader, there is an option in the Developer options which says "OEM unlocking", that supposedly allows the bootloader to be unlocked. Plugging the phone on the pc USB and using adb to get into fastboot works fine, but after typing "fastboot flashing unlock" the command prompt keeps on waiting with "..." for the next phone's action, that's where the problem begins: on the cellphone screen, right after the warnings about the consequences of unlocking the bootloader, appears: "Press the Volume UP/Down buttons to select Yes or No." If Volume_Down is pressed, it returns to fastboot, but if Volume_UP is pressed nothing happens, literally nothing, Power button also does nothing, the only one who works is Volume_Down, making it unable to unlock the bootloader via this method.
I tried to use "adb shell input keyevent 24" (knowing it wouldn't work) to try to send the Volume_Up command from the pc.
So I wanna know if there is a way that, through that fastboot waiting instance (the three dots "..."), I can send the Volume_Up command from the pc, enabling the Bootloader to be unlocked, making the root easy or even possible.
Thanks in advance!
Click to expand...
Click to collapse
Just because you have the "OEM unlock" option in settings doesn't necessarily mean you can unlock bootloader, the manufacturer or your carrier may have disabled that option in fastboot. Not all devices can be unlocked.
Sent from my SM-S903VL using Tapatalk
still waiting for rooting app, too...
Why God! Why??!! Why Google & Lenovo d'nt just make possible 4 rooting?
Kirzoczek said:
Why Godzin why??!! Why Google d'nt just make possible 4 rooting?
Click to expand...
Click to collapse
Well i'm pissed of. Lenovo just turn off vol up button. U just can't press it in fastboot mode to unlock bootloader. F...... ?
Kirzoczek said:
Why God! Why??!! Why Google & Lenovo d'nt just make possible 4 rooting?
Click to expand...
Click to collapse
Google isn't the the one that has control of that, that's controlled by the device manufacturers and/or each mobile carrier. In this case, it's controlled by Lenovo
The only devices that Google has control over whether they're rootable or not is only the Nexus and Pixel devices, not any of the others.
I DO NOT PROVIDE HELP IN PERSONAL MESSAGE, I DO NOT TAKE REQUESTS IN PERSONAL MESSAGE, YOU WILL BE IGNORED. KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
---------- Post added at 04:01 PM ---------- Previous post was at 03:47 PM ----------
Matt1355 said:
So guys, the thing is: I haven't found a way to root nor to unlock the bootloader in this phone.
Focusing on the bootloader, there is an option in the Developer options which says "OEM unlocking", that supposedly allows the bootloader to be unlocked. Plugging the phone on the pc USB and using adb to get into fastboot works fine, but after typing "fastboot flashing unlock" the command prompt keeps on waiting with "..." for the next phone's action, that's where the problem begins: on the cellphone screen, right after the warnings about the consequences of unlocking the bootloader, appears: "Press the Volume UP/Down buttons to select Yes or No." If Volume_Down is pressed, it returns to fastboot, but if Volume_UP is pressed nothing happens, literally nothing, Power button also does nothing, the only one who works is Volume_Down, making it unable to unlock the bootloader via this method.
I tried to use "adb shell input keyevent 24" (knowing it wouldn't work) to try to send the Volume_Up command from the pc.
So I wanna know if there is a way that, through that fastboot waiting instance (the three dots "..."), I can send the Volume_Up command from the pc, enabling the Bootloader to be unlocked, making the root easy or even possible.
Thanks in advance!
Click to expand...
Click to collapse
The command is supposed to be
fastboot OEM unlock
I DO NOT PROVIDE HELP IN PERSONAL MESSAGE, I DO NOT TAKE REQUESTS IN PERSONAL MESSAGE, YOU WILL BE IGNORED. KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Yes, you have right. But what with this vol+ button?
Volume+ button is not working on Lenovo C2 ?
GPSSlovakia said:
Volume+ button is not working on Lenovo C2 ?
Click to expand...
Click to collapse
I mean that vol up did' t work in fastboot mode. When u try to unblock bootloader u have two options. U may choose yes or no. Offously vol up is for "yes" answer. And whoop!!! It don't work
How to restore the imei number of this phone ..i tried several methods to restore..pls help me
rijukrishnan said:
How to restore the imei number of this phone ..i tried several methods to restore..pls help me
Click to expand...
Click to collapse
If you didn't make an IMEI backup then we can't discuss restoring your IMEI at XDA, it's in the Forum Rules.
Sent from my SM-S903VL using Tapatalk
then what can i do next to make it in stock condetion
What is this message means
rijukrishnan said:
What is this message means
Click to expand...
Click to collapse
I think it is saying that the connection between PC and your device was interrupted for some reason. I was probably a problem with your cable being loose and losing connection where it plugs into your device.
It is not very likely but it could also be an unstable electrical supply grid in your area, the power in the building where you are could have dropped momentarily, I doubt this was the cause though, but it is one possibility.
Use a different cable or find a way to make sure it connects and stays connected, then try flashing again.
The error you have is described in the attachment below, it explains how to solve.
For future reference, the link below has a list of all flash tool errors and how to solve them.
https://forum.hovatek.com/thread-439.html
Sent from my SM-S903VL using Tapatalk
Droidriven said:
If you didn't make an IMEI backup then we can't discuss restoring your IMEI at XDA, it's in the Forum Rules.
Click to expand...
Click to collapse
i have a bckup of imei number
Eh..,,.... no unlock oem ... no root , bad phone
Droidriven said:
Just because you have the "OEM unlock" option in settings doesn't necessarily mean you can unlock bootloader, the manufacturer or your carrier may have disabled that option in fastboot. Not all devices can be unlocked.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
You can access the recovery for this model after you send the command (ADB and fastboot commands): "Adb reboot recovery" where "Adb reboot boot loader" and then you have to click on the volume up and the power button at the same time and its success
* But the problem is that I have not found the trwp compatible with this model to make the root that can help us
medzbody said:
You can access the recovery for this model after you send the command (ADB and fastboot commands): "Adb reboot recovery" where "Adb reboot boot loader" and then you have to click on the volume up and the power button at the same time and its success
* But the problem is that I have not found the trwp compatible with this model to make the root that can help us
Click to expand...
Click to collapse
TWRP for your device probably doesn't exist, you'll have to wait for someone to be interested in building TWRP for your model (not likely to happen if it hasn't already) or you can port or build your own TWRP.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
TWRP for your device probably doesn't exist, you'll have to wait for someone to be interested in building TWRP for your model (not likely to happen if it hasn't already) or you can port or build your own TWRP.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
I do not know how to build twrp for my device you can help me
What about making a TWRP and then flashing it thru modified scatter file in flash tool
Hello,
My Pixel 2 was unlocked bootloader and Rooted.
I went to Magisk app then pressed Uninstall All, then my phone rebooted and brick at boot (Screenshot "No command").
I tried to flash back to stock rom but computer cannot reconize the phone. (I supposed USB debugging was not turned on yet).
Please advise how I can make my Pixel 2 back to work?
Many thanks in advance.
thieuvn said:
Hello,
My Pixel 2 was unlocked bootloader and Rooted.
I went to Magisk app then pressed Uninstall All, then my phone rebooted and brick at boot (Screenshot "No command").
I tried to flash back to stock rom but computer cannot reconize the phone. (I supposed USB debugging was not turned on yet).
Please advise how I can make my Pixel 2 back to work?
Many thanks in advance.
Click to expand...
Click to collapse
Anyone can help?
thieuvn said:
Anyone can help?
Click to expand...
Click to collapse
Hi! Can you see your Pixel in device manager when you connect it to PC?
somin.n said:
Hi! Can you see your Pixel in device manager when you connect it to PC?
Click to expand...
Click to collapse
I cannot see it.
Nothing happen when I plug the phone in.
thieuvn said:
I cannot see it.
Nothing happen when I plug the phone in.
Click to expand...
Click to collapse
Try to power off the phone and than hold power button until phone will vibrate and try again connect to pc ...
somin.n said:
Try to power off the phone and than hold power button until phone will vibrate and try again connect to pc ...
Click to expand...
Click to collapse
Thanks. I will try one more time
somin.n said:
Try to power off the phone and than hold power button until phone will vibrate and try again connect to pc ...
Click to expand...
Click to collapse
Still cannot connect my phone with the PC.
Tried 03 different PCs already.
thieuvn said:
Still cannot connect my phone with the PC.
Tried 03 different PCs already.
Click to expand...
Click to collapse
Do you have google usb drivers on your PC?
Code:
[url]https://developer.android.com/studio/run/win-usb[/url]
somin.n said:
Do you have google usb drivers on your PC?
Click to expand...
Click to collapse
Yes I had it all.
But still cannot connect, I tried All in one tool, 15s ADB , and all cannot reconize phone
thieuvn said:
Yes I had it all.
But still cannot connect, I tried All in one tool, 15s ADB , and all cannot reconize phone
Click to expand...
Click to collapse
And do you use original usb-c cable?
somin.n said:
And do you use original usb-c cable?
Click to expand...
Click to collapse
Yes i do.
The ADB driver keeps not working is the main problem.
thieuvn said:
Yes i do.
The ADB driver keeps not working is the main problem.
Click to expand...
Click to collapse
It is really weird :/ I tried to boot to bootloader with usb debuging off and still my PC correctly recognize my phone. Just last idea, try to boot to bootloader with key combination (power of phone and hold Power + vol down)...
Here is the version of usb driver which I have ...
somin.n said:
It is really weird :/ I tried to boot to bootloader with usb debuging off and still my PC correctly recognize my phone. Just last idea, try to boot to bootloader with key combination (power of phone and hold Power + vol down)...
Here is the version of usb driver which I have ...
Click to expand...
Click to collapse
Thank you.
Let me buy another cable then try again...
Download and extract the latest version of Platform Tools to a folder, then run all ADB and fastboot commands in command prompt or powershell within that folder. Don't rely on Windows drivers for ADB.
DuckRuckus said:
Download and extract the latest version of Platform Tools to a folder, then run all ADB and fastboot commands in command prompt or powershell within that folder. Don't rely on Windows drivers for ADB.
Click to expand...
Click to collapse
I already did it but no respond so far
thieuvn said:
I already did it but no respond so far
Click to expand...
Click to collapse
Forget about ADB, you need Fastboot access. While in the bootloader interface, connect your phone, look for it in the Device Manager and change its driver to Android Bootloader Interface, or something of the sort. Next try "fastboot devices" on the command line, see if it detects your device.
I brought my phone to repair shop and they detected that the hard disk was dead.
Just bought another Pixel 2 to have more awesome photos
You have no fastboot I guess.
Boot into fastboot, plug in the usb cable and press and hold the volume down button for like 15 seconds, and then it will be recognized by the PC. You can flash back the stock rom after that.
Hey I had the same problem. Just stuck in bootloader mode. In my case, the boot slot changed itself from b to a (access denied, same as your problem). What I did:
1. I boot my phone, then it'll be in bootloader mode (same as the first picture when it says 'operation denied')
2. I kept pressing the power button, then my phone boot into bootloader again (bootloop). I kept holding my power button until my phone boot into right boot slot. (It took me 10 bootloop to boot into right boot slot, I just keep holding my power button when in the bootloader mode)
You can add my telegram : (@)Djkuns if you're confused. Hope I can help! Goodluck!
can you even unlock the a53 5g bootloader because i have been trying to unlock for a while now but it dosnt work because it dosnt have a fastboot mode
Myrn69 said:
can you even unlock the a53 5g bootloader because i have been trying to unlock for a while now but it dosnt work because it dosnt have a fastboot mode
Click to expand...
Click to collapse
Unlocking the bootloader on Samsung devices works differently from many others. This is a summary of the steps needed:
Enable Developer Options
Enable OEM Unlocking (if not available or grayed out, ensure device is connected to Internet; if this remains unavailable, unlocking is not possible)
Turn device off and boot to download mode
While in download mode, hold Volume + to get to the bootloader unlock screen
However....Not every Samsung device is bootloader unlockable, especially not in the US. Almost all Qualcomm powered devices are locked, and some Exynos devices as well.
V0latyle said:
Unlocking the bootloader on Samsung devices works differently from many others. This is a summary of the steps needed:
Enable Developer Options
Enable OEM Unlocking (if not available or grayed out, ensure device is connected to Internet; if this remains unavailable, unlocking is not possible)
Turn device off and boot to download mode
While in download mode, hold Volume + to get to the bootloader unlock screen
However....Not every Samsung device is bootloader unlockable, especially not in the US. Almost all Qualcomm powered devices are locked, and some Exynos devices as well.
Click to expand...
Click to collapse
hi VOIatyle im have put the device in download mode and im holding Volume UP and its not doing anything
Myrn69 said:
hi VOIatyle im have put the device in download mode and im holding Volume UP and its not doing anything
Click to expand...
Click to collapse
Did you enable OEM Unlocking in Developer Options?
V0latyle said:
Did you enable OEM Unlocking in Developer Options?
Click to expand...
Click to collapse
Yes its enabled it says in the dev options
Myrn69 said:
Yes its enabled it says in the dev options
Click to expand...
Click to collapse
Hmm. How are you putting your device in download mode?
V0latyle said:
Hmm. How are you putting your device in download mode?
Click to expand...
Click to collapse
i just use ADB (adb reboot bootloader)
Myrn69 said:
i just use ADB (adb reboot bootloader)
Click to expand...
Click to collapse
Ah. No, you have to power your device off completely. Then, hold both Volume buttons (without pressing Power) and plug in the USB cable from your computer. The device should start in download mode. Then, hold Volume Up until you get the bootloader unlock screen.
Myrn69 said:
i just use ADB (adb reboot bootloader)
Click to expand...
Click to collapse
is there any other way?
Myrn69 said:
is there any other way?
Click to expand...
Click to collapse
See my message above. You have to start with the device powered off.
V0latyle said:
Ah. No, you have to power your device off completely. Then, hold both Volume buttons (without pressing Power) and plug in the USB cable from your computer. The device should start in download mode. Then, hold Volume Up until you get the bootloader unlock screen.
Click to expand...
Click to collapse
oh thanks i unlock thank you soo much
Myrn69 said:
oh thanks i unlock thank you soo much
Click to expand...
Click to collapse
Glad to be of help.
hi im sorry for asking again but can you help with something else