Help unlocking/rooting Lenovo Vibe C2 K10a40 - General Questions and Answers

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

Related

[Q] easiest way to boot into bootloader/recovery

okay guys looking for the easiest way to boot into recovery / bootloader
would prefer both physical on the phone and adb commands
if you would be so kind
Volume down+power = BOOTLOADER
adb commands are the same across nearly every device
adb reboot recovery
adb reboot bootloader
Pirateghost said:
Volume down+power = BOOTLOADER
adb commands are the same across nearly every device
adb reboot recovery
adb reboot bootloader
Click to expand...
Click to collapse
thanks, i never had to use adb with my captivate or infuse so i figured i would ask .
also for some reason sometimes volume down +power wont work to get me into the bootloader.
I use Quickboot...it has many reboot options, including reboot into Bootloader and Reboot into Recovery.
Another simple way is to pick restart from the power menu then just hold volume down as the phone restarts.
Sent from my HTC One X using Tapatalk 2
The_Zodiac said:
thanks, i never had to use adb with my captivate or infuse so i figured i would ask .
also for some reason sometimes volume down +power wont work to get me into the bootloader.
Click to expand...
Click to collapse
You have to hold volume down the entire time until it gets to the bootloader. On the Captivate you could release it as soon as the splash screen came up but on this HOX you have to continue holding.
The_Zodiac said:
also for some reason sometimes volume down +power wont work to get me into the bootloader.
Click to expand...
Click to collapse
If the phone is powered off when you want to go into bootloader, you have to make sure "Fast boot" in Settings>Power is unchecked.
Going into bootloader using power+vol down requries the phone to be fully powered off or a reboot. Fast boot is actually just a deep sleep mode and not a full power down.
---------- Post added at 10:42 AM ---------- Previous post was at 10:37 AM ----------
BBock9 said:
Another simple way is to pick restart from the power menu then just hold volume down as the phone restarts.
Click to expand...
Click to collapse
That method never seems to work for me. Holding the vol down immediately after selecting restart, or even holding the vol down while picking restart, it just boots normally.
I have to power down (with fast boot unselected in Settings>Power) then hold vol down while pressing power button, in order to get to bootloader.
Pirateghost said:
Volume down+power = BOOTLOADER
adb commands are the same across nearly every device
adb reboot recovery
adb reboot bootloader
Click to expand...
Click to collapse
I am trying to boot my samsung captivate into the boot loader. I've tried the physical key combos mentioned in this thread and there not working.
I tried using ./adb reboot bootloader but the phone does a regular reboot.
I am able to get a splash screen with that says "Download" and has a picture of the Android shoveling, by pressing both volumes and plugin in the power.
But if i do this, the device is not visible when I used ./adb devices
The question is how can i get this to reboot into the bootloader preferably from the terminal so that I can unlock it and install CWM.
Any advice would be much appreciated!
Good job finding the wrong phones forum and digging up an old thread to post on
Sent from my HTC One XL
leptone said:
I am trying to boot my samsung captivate into the boot loader.
Click to expand...
Click to collapse
This forum is specific to the HTC One X/XL. You need to go to the forum specific to the Samsung Captivate. The key sequence is likely different, and getting advice from people with a different device can quite possibly lead get you the incorrect info.
Also, as mentioned above, try not to dig up old threads from 7 months ago.
derp.
wrong thread
Quick question: I'm trying to reboot my android STB in bootloader mode to check its lock/unlock status... Obviously I can't use the Vol Down + Power button in a STB...
So I tried "adb reboot bootloader", which didin't seem to work. I mean, it powered down, then powered up in a screen with the brand's logo, but nothing else happened, and the command "fastboot devices" didn't find any device either (while before that, "adb devices" showed the device normally). Also, I didn't get any unrecognized devices under Device manager which would denote that a new "device" got connected into the system...
I then tried "adb reboot recovery" which works fine...
So what does this situation mean for my STB?

[Q] Too many pattern attempts... No Recovery menu

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:

[Q] Power button unresponsive in bootloader/fastboot

I just bought a Nexus 5 today and I wanted to root it as soon as possible primarily to disable those pesky ads in Youtube. I have been following guide after guide to get this working, but I keep getting stuck when trying to unlock the bootloader.
Just as a side note, I have tried this on two different computers and have been using the official newest SDK files for adb/fastboot tools and for google drivers.
I have enabled usb debugging and I can use both "adb devices" when the Nexus is on and "fastboot devices" in FASTBOOT MODE with success so I don`t think I have a driver issue.
Basically I got phone, 4.4 was installed, and then I did the update to 4.4.2 before trying to unlock the bootloader.
When I put the phone into fastboot mode, I can scroll though different commands, such as "power off", "start"... with the volume buttons, but when I press the power button, nothing happens. Then when I connect the device to my computer and type "fastboot oem unlock" into the command prompt, I am greeted with the option to unlock the bootloader and I can scroll through yes or on, but again, when I press the power button, nothing happens. I have tried clicking it multiple times as well, and when I hold it for a about 10 seconds, the device powers off, still locked.
Like I said, i don;t believe this is a driver issue, because even when the phone is not plugged in, I can`t select those options at the fastboot screen.
Would any of you have any advice for me, perhaps I`m missing something?
I tried charging the phone completely, figured maybe it wouldn`t work because the battery charge was too low. Still doesn't work, I can`t even get into recovery mode.
Think I may have a dud? I don't know what do to, I can't really say I want to return the phone because it won't go into recovery mode or because I can't unlock the bootloader...
Am I the only one?
Accessing recovery is a standard feature of the device and in itself has nothing to so with rooting or unlocking bootloaders so you can definitely use this as reasoning.
I assume you used vol down + power to get into bootloader. What if you vol up + vol down + power to bootloader?
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
What if you fastboot flashed just the bootloader from the factory image. Maybe something is messed up with it where it doesn't recognize the power button. Just an idea a I've never seen this issue before.
Thank you for the replies, I have tried both volume down+ power and both volume keys and power. As I read somewhere else, it`s like it keeps two bootloaders, one for 4.4 and the other 4.4.2. Both do not respond to the power button input.
Would I be able to flash over the bootloader without unlocking it?
If I do decide to return it and they ask me why I need to access recovery (I galled google support last night and they told me they wouldn't support me when it comes to the bootloader, he also didn't understand what I was asking him), for which reason would I need to access recovery?
This is a replacement phone to my old GS3 which broke. I had a Best Buy replacement plan, so that's how I got the nexus 5. I'm almost tempted to bring it back for a GS4, with Samsung it was easy to flash over the whole phone with odin, without these bootlocker unlocker steps.
If I can flash over the bootloader without unlocking it, how would I do so?
I really do appreciate all your help with this, I love the phone otherwise but I'd like to have the option to root.
EDIT: found these steps, but the post assumes the phone already has an unlocked bootloader, but doesn't mention that it is necessary:
adb reboot bootloader
fastboot flash bootloader bootloader-hammerhead-HHZ11d.img
fastboot reboot-bootloader
fastboot flash radio radio-hammerhead-M8974A-1.0.25.0.17.img
fastboot reboot-bootloader
fastboot -w update image-hammerhead-krt16m.zip
fastboot reboot-bootloader
I gues there is one way to find out...
Read a lot before you decide on the s4. The boot loader is locked and you are extremely limited to what and how you can flash roms. I would not recommend the s4, my opinion.
And I spaced out the fact you can't unlock the bootloader. That's a problem.
I tried the above steps to flash the bootloader, it won't let me do it since the device is locked...
Just rma it. Tell them it cannot enter recovery from bootloader which is essential to factory reset the device in the Case it doesn't boot.
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
murc585 said:
I tried the above steps to flash the bootloader, it won't let me do it since the device is locked...
Click to expand...
Click to collapse
try to boot into recovery from adb command, and see if power button works (wipe data and cache)
Ok, I did "adb devices", I see my device and the word "device" after. When I try the "adb reboot recovery" command nothing happens.
Edit:I got the no command window finally, pressed the volume yet, the menu showed up, I was able to flash the cache and do a data wipe. I will try the bootloader now
Edit 2: after data wipe and cache format from recovery, bootloader still does not recognise power button, can i flash anything from recovery?
Would there be a way to sideload the update through adb?
There is clearly an issue. Please rma
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
Alright, seems I have no choice but thank you for helping me troubleshoot this issue.

HELP! Can't get fastboot to recognize device and can't get into bootloader / recovery

ok so:
i was trying out the new PAC build today, and i went into philz to wipe, and wiped the old OS and data. i accidentally hit reboot system, instead of installing a new os and then getting into it.
"no big deal" i thought. figuring i'd just boot into bootloader and get into recovery and then flash away
i seem to be stuck at the nvidia screen and cant get past that.
when i hold vol down and power, it just brings me to the nvidia screen with nothing to do there. using cmd i can:
adb devices: shows my serial and offline, makes sense
fastboot devices: does nothing and goes back to the command prompt
fastboot any command brings me to <waiting for devices>
my device manager shows "portable devices: shield tablet" and "android device: android composite adb interface"
anyone have any clue what i may have done....or what i can do? i am freaking out a little over here, thinking i may have bricked this thing
Hold Volume down pressed, but release Power immediately after pressing it and you will enter the bootloader. When this succeeds you should never see the nvidia screen.
Gnurou said:
Hold Volume down pressed, but release Power immediately after pressing it and you will enter the bootloader. When this succeeds you should never see the nvidia screen.
Click to expand...
Click to collapse
if i could kiss you. i would
thank you so much... STUPID NVIDIA!
That's how it is explained in the recovery flashing instructions, although I agree this is somehow confusing.
Gnurou said:
Hold Volume down pressed, but release Power immediately after pressing it and you will enter the bootloader. When this succeeds you should never see the nvidia screen.
Click to expand...
Click to collapse
I could kiss you too...I did almost the same thing. You are my favorite person on the planet atm.
Sent from my xt926
Unlocking bootloader on shield
minieod said:
if i could kiss you. i would
thank you so much... STUPID NVIDIA!
Click to expand...
Click to collapse
How did you managed to succeed with this minieod ?
I get the message <waiting for device> as you... Please help.
---------- Post added at 10:51 PM ---------- Previous post was at 10:22 PM ----------
Wulfpk said:
I could kiss you too...I did almost the same thing. You are my favorite person on the planet atm.
Sent from my xt926
Click to expand...
Click to collapse
How did you managed to succeed with this Wulfpk?
I get the message <waiting for device> as you... Please help.
djebm2 said:
I get the message <waiting for device> as you... Please help.
Click to expand...
Click to collapse
Just to confirm, you are using fastboot for bootloader and not adb right?
Unlocking bootloader on shield
amartolos said:
Just to confirm, you are using fastboot for bootloader and not adb right?
Click to expand...
Click to collapse
Yes amartolos. adb is able to print my shield talbet serial number, but not fastboot...
You need administrative privileges for fastboot command but not for adb. If you're using linux, make sure to do sudo fastboot; if you're in Windows, make sure you started command prompt with Administrative privileges. Hope that helps =)
Unlocking bootloader on shield
amartolos said:
You need administrative privileges for fastboot command but not for adb. If you're using linux, make sure to do sudo fastboot; if you're in Windows, make sure you started command prompt with Administrative privileges. Hope that helps =)
Click to expand...
Click to collapse
Admin privileges does not solve the problem.

Bootloader relock

Hi,
is it a problem to relock the bootloader ?
What steps do i have to do ?
Greetz
adb devices
Now, you will see a serial number in the command prompt window which indicates that the device is connected.
adb reboot bootloader
As the device booted into Fastboot mode, type the following command to lock the bootloader.
fastboot oem lock
Now, a confirmation pop-up will appear on the device screen. Use the volume buttons to navigate the highlight to “Relock Bootloader” and press the Power button to confirm it.
And after this, what will happen? Especially when you are rooted? Will it wipe all your data and can you start all over again, or will you face errors/issues/bootloops?
Person I wont just relock my bootloader. Your hash records are broken and you won't get working upgrades anymore, it's even the question if you still can oem unlock it again..... Besides this I don't know if, when you will brick your device, the msm tools still work. If you want to go back to stock better use MSMtools directly and go back to stock. https://www.xda-developers.com/how-to-unbrick-oneplus-nord-msmdownloadtool/amp/
Matija Gubec said:
adb devices
Now, you will see a serial number in the command prompt window which indicates that the device is connected.
adb reboot bootloader
As the device booted into Fastboot mode, type the following command to lock the bootloader.
fastboot oem lock
Now, a confirmation pop-up will appear on the device screen. Use the volume buttons to navigate the highlight to “Relock Bootloader” and press the Power button to confirm it.
Click to expand...
Click to collapse
Is this a safe method ? I dont want to brick the phone.... because i read a thread,where the relock ends in a bootloop..... THX
Im not test it but i have last week close BL on my O+ 8pro without any problem!
But before you close BL read this:
https://forum.xda-developers.com/on...de-fix-persist-img-loss-finger-print-t4125909
So i make it. And everything works without any problem.
If you have root remove it.
Flash last original firmware!
(so if you use patched boot.img you have now the "original" again!)
Then relock bootloader...
After that i test it with FP,Face Unlock and OTA update!
Everything is fine ...
reef2009 said:
Person I wont just relock my bootloader. Your hash records are broken and you won't get working upgrades anymore, it's even the question if you still can oem unlock it again..... Besides this I don't know if, when you will brick your device, the msm tools still work. If you want to go back to stock better use MSMtools directly and go back to stock. https://www.xda-developers.com/how-to-unbrick-oneplus-nord-msmdownloadtool/amp/
Click to expand...
Click to collapse
This 10.5.11.AC01AA version is ok?

Categories

Resources