Related
Hey guys,
I've been messing around with my brand new N7 yesterday and somehow screwed up badly.
Right now, all I have is a working TWRP recovery and a locked bootloader.
When I try to unlock the bootloader, the device just freezes so flashing stock images is not an option.
Can I do something via TWRP to get my N7 working again?
I already opened a RMA with amazon.
Second question: If I am out of options, is there a way to remove TWRP?
Really need your help right now,
thanks in advance,
DrTek
which method did u try to unlock the bootloader?
MoonBlade said:
which method did u try to unlock the bootloader?
Click to expand...
Click to collapse
I tried with "fastboot oem unlock"
The moment I choose yes and push the power button for confirmation - the device freezes.
drtek said:
I tried with "fastboot oem unlock"
The moment I choose yes and push the power button for confirmation - the device freezes.
Click to expand...
Click to collapse
is it freezing for more than 2 mins ? it should not freeze like that unless it is already unlocked ??
It might already be unlocked. Do you have an unlocked symbol when you turn it on? If you do, run the Dead Nexus batch file from here. I was unable to do anything from TWRP or CWM. Just a bunch of errors when it tried to do anything with the drive. Flashing, copying, formatting, etc. This saved my Nexus!
http://forum.xda-developers.com/showthread.php?t=2381582
Do you have access to the internal SD? From a computer or anywhere? Because if you do you can just flash a ROM from twrp
sent from my nex7
I was using my phone like I usually do, and then it suddenly froze. So I held down the power button, forcing it to restart. Ever since, the screen only shows "Google" for a while, then becomes blank; no booting animation. It would restart itself occasionally.
I tried booting into recovery mode by holding Power+VolDown, and selecting "recovery mode". For the first few tries, it would go back to the Google screen, the turn blank. After giving it a break and trying again, I finally got to the "no command" screen, and I wiped the cache partition. Sadly, I'm still having the same problem.
Is this a bootloop? How can I fix this?
Any help would be greatly appreciated.
This happened to me and Google sent a replacement phone. However the replacement phone is a refurbished phone that suffers from ghost touches Now trying to get a replacement for the replacement.
Ocelot584 said:
I was using my phone like I usually do, and then it suddenly froze. So I held down the power button, forcing it to restart. Ever since, the screen only shows "Google" for a while, then becomes blank; no booting animation. It would restart itself occasionally.
I tried booting into recovery mode by holding Power+VolDown, and selecting "recovery mode". For the first few tries, it would go back to the Google screen, the turn blank. After giving it a break and trying again, I finally got to the "no command" screen, and I wiped the cache partition. Sadly, I'm still having the same problem.
Is this a bootloop? How can I fix this?
Any help would be greatly appreciated.
Click to expand...
Click to collapse
can u boot into bootloader mode?
dominoeflux said:
can u boot into bootloader mode?
Click to expand...
Click to collapse
What's that? Is it the screen that comes up when you hold down Power+VolumeDown and gives you the option to select Start, Power Off, Restart Bootloader, or Recovery?
Ocelot584 said:
What's that? Is it the screen that comes up when you hold down Power+VolumeDown and gives you the option to select Start, Power Off, Restart Bootloader, or Recovery?
Click to expand...
Click to collapse
Yes that's the one. If u can get back to that screen you should be able to flash it back stock and re root the phone with out any problems
dominoeflux said:
Yes that's the one. If u can get back to that screen you should be able to flash it back stock and re root the phone with out any problems
Click to expand...
Click to collapse
So are you saying that I should factory reset my phone from the recovery menu, or do I have to use the method that requires the factory image?
My phone wasn't rooted btw, so I can't re-root it.
Ocelot584 said:
So are you saying that I should factory reset my phone from the recovery menu, or do I have to use the method that requires the factory image?
My phone wasn't rooted btw, so I can't re-root it.
Click to expand...
Click to collapse
Oh ok I thought it was sorry if I wasn't of any help
dominoeflux said:
Oh ok I thought it was sorry if I wasn't of any help
Click to expand...
Click to collapse
haha it's ok you tried to.
Rooted or not, do you think factory resetting it will fix the problem as long as I can get to the bootloader menu?
Ocelot584 said:
haha it's ok you tried to.
Rooted or not, do you think factory resetting it will fix the problem as long as I can get to the bootloader menu?
Click to expand...
Click to collapse
In pretty positive that it will, make sure u unlock the Bootloader first before you do anything. Do you know how to unlock it?
dominoeflux said:
In pretty positive that it will, make sure u unlock the Bootloader first before you do anything. Do you know how to unlock it?
Click to expand...
Click to collapse
nope...what's a bootloader anyway?
Ocelot584 said:
nope...what's a bootloader anyway?
Click to expand...
Click to collapse
The bootloader allows the phone to be unlocked to flash custom ROMs on it, without it unlocked you'll brick your phone. Read up about rooting your phone first so you can get the idea of what goes into it before attempting it. Once you get the general idea of unlocking the phone and flashing things on it, it becomes relatively easy. There's even a nexus root toolkit on this forum that you can download on your computer for free as well as "how-to's" for doing it
dominoeflux said:
The bootloader allows the phone to be unlocked to flash custom ROMs on it, without it unlocked you'll brick your phone. Read up about rooting your phone first so you can get the idea of what goes into it before attempting it. Once you get the general idea of unlocking the phone and flashing things on it, it becomes relatively easy. There's even a nexus root toolkit on this forum that you can download on your computer for free as well as "how-to's" for doing it
Click to expand...
Click to collapse
Wait...what?? So if I choose to factory reset my phone now without unlocking the bootloader, it might become completely useless? Is rooting necessary?
Ocelot584 said:
Wait...what?? So if I choose to factory reset my phone now without unlocking the bootloader, it might become completely useless? Is rooting necessary?
Click to expand...
Click to collapse
No is not necessary, but in order to re flash the factory image to fix the problem the bootloader must be unlocked. You never have to root your device but having a unlocked bootloader is essential to flashing anything on your device other wise like I said, you'll brick your phone. You can even lock it back to full stock once you've re flashed the image.
Edit: there's another way of flashing the factory image but it requires some searching. You might not be able to do it the way I'm explaining to you Because you would have to give it permission to be unlocked in the developers option while the phone is booted up and operative
dominoeflux said:
No is not necessary, but in order to re flash the factory image to fix the problem the bootloader must be unlocked. You never have to root your device but having a unlocked bootloader is essential to flashing anything on your device other wise like I said, you'll brick your phone. You can even lock it back to full stock once you've re flashed the image.
Edit: there's another way of flashing the factory image but it requires some searching. You might not be able to do it the way I'm explaining to you Because you would have to give it permission to be unlocked in the developers option while the phone is booted up and operative
Click to expand...
Click to collapse
Oh...I see. So what about the factory reset option in the recovery menu? Would you expect that to fix it too?
Ocelot584 said:
Oh...I see. So what about the factory reset option in the recovery menu? Would you expect that to fix it too?
Click to expand...
Click to collapse
Of course
Edit: have you tried resetting it in the factory recovery?
dominoeflux said:
Of course
Edit: have you tried resetting it in the factory recovery?
Click to expand...
Click to collapse
Nope...I was waiting to see if I could find a way to recover my data first
Ocelot584 said:
Nope...I was waiting to see if I could find a way to recover my data first
Click to expand...
Click to collapse
When u first bought your phone and it takes you through the set up window, when it asked you to put in your email, that right there backs up all your apps that you previously had in the phone so when you go through the setup again, it's going to ask you if you want to start as a new phone or recover your previous apps. You won't be able to recover all of your data but you should be able to recover all of your apps.
dominoeflux said:
When u first bought your phone and it takes you through the set up window, when it asked you to put in your email, that right there backs up all your apps that you previously had in the phone so when you go through the setup again, it's going to ask you if you want to start as a new phone or recover your previous apps. You won't be able to recover all of your data but you should be able to recover all of your apps.
Click to expand...
Click to collapse
Alright, but since all my data won't be recovered, is there a way to get access to files on my phone before I factory reset it?
Ocelot584 said:
Alright, but is there a way to get access to files on my phone before I factory reset it?
Click to expand...
Click to collapse
Sorry bro but I wish there was.... There actually is away, but you would have have to have been rooted with a custom recovery on your phone and since you had neither, there's my other way
Edit: I meant no other way
dominoeflux said:
Sorry bro but I wish there was.... There actually is away, but you would have have to have been rooted with a custom recovery on your phone and since you had neither, there's my other way
Edit: I meant no other way
Click to expand...
Click to collapse
oh... wow.
I'll just suck it up and reset it then. I'll let u know how it goes.
I bought my Pixel XL (2016) used last week. Everything was perfect. Tried Android P Beta and then went back to official Oreo. The phone worked perfectly all week.
Then tonight I'm watching a YouTube video and the thing shuts off to never turn back on. I can't access recovery but the bootloader is there. The thing is it's locked and I can't allow OEM unlock cause I can't boot into Android.
When I try to boot normally or go into recovery mode there's a white flicker on top. Like it's trying to load it but can't.
It's possible that it's no longer under warranty...
Can anyone help?
Thanks :crying:
Prosis said:
I bought my Pixel XL (2016) used last week. Everything was perfect. Tried Android P Beta and then went back to official Oreo. The phone worked perfectly all week.
Then tonight I'm watching a YouTube video and the thing shuts off to never turn back on. I can't access recovery but the bootloader is there. The thing is it's locked and I can't allow OEM unlock cause I can't boot into Android.
When I try to boot normally or go into recovery mode there's a white flicker on top. Like it's trying to load it but can't.
It's possible that it's no longer under warranty...
Can anyone help?
Thanks :crying:
Click to expand...
Click to collapse
If it still boots into the boot loader you're fine and fixable.
Phalanx7621 said:
If it still boots into the boot loader you're fine and fixable.
Click to expand...
Click to collapse
Well that's good news at least!
What can I do?
Prosis said:
Well that's good news at least!
What can I do?
Click to expand...
Click to collapse
This will wipe your device. If it won't boot up, there are a ton of other things you COULD try, but without knowing what caused it to be this way it'd be fishing in the dark.
Go to this website https://developers.google.com/android/images
download Android 8.1 Oreo Factory Image (make sure Factory Images is selected in the upper left portion of the screen at the top, not OTA).
After downloading, extract the files to a folder, go into that folder and select all the items in it and copy them to wherever you have fastboot / adb installed. Make sure phone is in bootloader, then open a command prompt (or Windows Powershell in Windows 10)use Fastboot command:
fastboot flash-all.bat
If in Windows Powershell, use command:
.\fastboot flash-all.bat
If you need platform-tools (adb/fastboot) they're here
https://developer.android.com/studio/releases/platform-tools
Phalanx7621 said:
This will wipe your device. If it won't boot up, there are a ton of other things you COULD try, but without knowing what caused it to be this way it'd be fishing in the dark.
Go to this website https://developers.google.com/android/images
download Android 8.1 Oreo Factory Image (make sure Factory Images is selected in the upper left portion of the screen at the top, not OTA).
After downloading, extract the files to a folder, go into that folder and select all the items in it and copy them to wherever you have fastboot / adb installed. Make sure phone is in bootloader, then open a command prompt (or Windows Powershell in Windows 10)use Fastboot command:
fastboot flash-all.bat
If in Windows Powershell, use command:
.\fastboot flash-all.bat
If you need platform-tools (adb/fastboot) they're here
https://developer.android.com/studio/releases/platform-tools
Click to expand...
Click to collapse
But don't I need to have an unlocked bootloader for that? It's currently locked and OEM Unlock was not enabled in Android before it crashed.
Prosis said:
But don't I need to have an unlocked bootloader for that? It's currently locked and OEM Unlock was not enabled in Android before it crashed.
Click to expand...
Click to collapse
Ohh....well then you'd need to enter recovery mode, but you're saying that doesn't work?
Have you powered down the device completely, plugged it into a power source, then tried booting into bootloader mode, choosing Recovery Mode, and then once the dead android appears on the screen from recovery mode, hold down the power button and while holding that down click the Volume Up button once, then release the Power button. This should allow access to the stock recovery where you can do a factory reset.
Phalanx7621 said:
Ohh....well then you'd need to enter recovery mode, but you're saying that doesn't work?
Have you powered down the device completely, plugged it into a power source, then tried booting into bootloader mode, choosing Recovery Mode, and then once the dead android appears on the screen from recovery mode, hold down the power button and while holding that down click the Volume Up button once, then release the Power button. This should allow access to the stock recovery where you can do a factory reset.
Click to expand...
Click to collapse
Yeah I tried that but the dead android never appears. It reacts the same way it does when I try to boot into the system, which is just a white flicker that appears and disappears on the top of the screen. It's like it's trying to load the white screen with the Google logo but it can't.
Had you modified the system at all? Was this bare bones stock? As far as I know, nothing can touch system files without root, so recovery (boot.img) should be fine. What about overheating, that was my next question. Was it getting super hot before this happened?
edit: I found this website, with this gentleman claiming that the Nexus Root Toolkit also works for our devices in a "bricked" situation. I know nothing about it, nor have I tried it, was just looking to see if I could find anyone else with your situation and ran across this website .
https://forums.androidcentral.com/google-pixel-pixel-xl/804286-help-bricked-my-pixel-xl.html
http://www.wugfresh.com/nrt/
Again, I have never used this, so use at your own risk. Hopefully someone else will help out here who may have this similar situation.
Phalanx7621 said:
Had you modified the system at all? Was this bare bones stock? As far as I know, nothing can touch system files without root, so recovery (boot.img) should be fine. What about overheating, that was my next question. Was it getting super hot before this happened?
edit: I found this website, with this gentleman claiming that the Nexus Root Toolkit also works for our devices in a "bricked" situation. I know nothing about it, nor have I tried it, was just looking to see if I could find anyone else with your situation and ran across this website .
https://forums.androidcentral.com/google-pixel-pixel-xl/804286-help-bricked-my-pixel-xl.html
http://www.wugfresh.com/nrt/
Again, I have never used this, so use at your own risk. Hopefully someone else will help out here who may have this similar situation.
Click to expand...
Click to collapse
Thank you! No it was not modified in any way. The only thing that happened was that I tried the P Beta (through OTA) during the weekend and flashed (through fastboot) the factory Oreo ROM then relocked the bootloader. So everything was back to factory state. Everything worked fine all week. It wasn't hot when it shut down at all.
I'll try this while I wait for Google's response to whether it's under warranty or not and keep you updated.
In the meantime, if you or anyone else has a way to just try to flash the ROM or recovery again even with the locked bootloader I'm all ears!
Thanks
Prosis said:
Thank you! No it was not modified in any way. The only thing that happened was that I tried the P Beta (through OTA) during the weekend and flashed (through fastboot) the factory Oreo ROM then relocked the bootloader. So everything was back to factory state. Everything worked fine all week. It wasn't hot when it shut down at all.
I'll try this while I wait for Google's response to whether it's under warranty or not and keep you updated.
In the meantime, if you or anyone else has a way to just try to flash the ROM or recovery again even with the locked bootloader I'm all ears!
Thanks
Click to expand...
Click to collapse
Ohhh ok I see. Yes, never ever relock the bootloader. In case of situations like this, it's always a good idea to leave it unlocked. Just out of curiosity, have you tried plugging it into a power source, powr it up to the boot loader screen, choose Recovery, then hold in Volume Down + Power for about 30 seconds? It should reboot it back to bootloader menu again. This sometimes works for me when nothing else does, but I have no idea why.
Phalanx7621 said:
Ohhh ok I see. Yes, never ever relock the bootloader. In case of situations like this, it's always a good idea to leave it unlocked. Just out of curiosity, have you tried plugging it into a power source, powr it up to the boot loader screen, choose Recovery, then hold in Volume Down + Power for about 30 seconds? It should reboot it back to bootloader menu again. This sometimes works for me when nothing else does, but I have no idea why.
Click to expand...
Click to collapse
Oh getting into bootloader menu is no issue at all. I just can't go anywhere else (recovery, system, etc.).
It's not even able to show me the charging animation when the device is off.
Prosis said:
Oh getting into bootloader menu is no issue at all. I just can't go anywhere else (recovery, system, etc.).
It's not even able to show me the charging animation when the device is off.
Click to expand...
Click to collapse
Unforunately, if recovery mode isn't booting and you don't have the bootloader unlocked, I'm out of ideas. Have you tried, just for ****s and giggles, to unlock the bootloader again via fastboot just to see what it says?
Phalanx7621 said:
Unforunately, if recovery mode isn't booting and you don't have the bootloader unlocked, I'm out of ideas. Have you tried, just for ****s and giggles, to unlock the bootloader again via fastboot just to see what it says?
Click to expand...
Click to collapse
Yeah I did. I even tried several tools that are supposed to be able to help but without having Allow OEM Unlock enabled nothing works :/
After maybe 2 hours left alone charging now it's not even booting into the booloader anymore...
Are you going to be able to RMA it? Is it still under warranty?
Phalanx7621 said:
Are you going to be able to RMA it? Is it still under warranty?
Click to expand...
Click to collapse
I'm waiting for my seller to give me the original order number (which seems like forever right now given the situation). Then Google will be able to tell me if it's still under warranty. If not then, according to the authorized repair center, it's either the battery, the port or the motherboard which means it's probably the end for this phone as prices range from less than $100 to nearly $400. :crying:
Prosis said:
I bought my Pixel XL (2016) used last week. Everything was perfect. Tried Android P Beta and then went back to official Oreo. The phone worked perfectly all week.
Then tonight I'm watching a YouTube video and the thing shuts off to never turn back on. I can't access recovery but the bootloader is there. The thing is it's locked and I can't allow OEM unlock cause I can't boot into Android.
When I try to boot normally or go into recovery mode there's a white flicker on top. Like it's trying to load it but can't.
It's possible that it's no longer under warranty...
Can anyone help?
Thanks :crying:
Click to expand...
Click to collapse
Post this information on this thread: Need Pixel XL 128GB complete eMMC image file by noriharsha
Homeboy76 said:
Post this information on this thread: Need Pixel XL 128GB complete eMMC image file by noriharsha
Click to expand...
Click to collapse
Thanks but the phone isn't even powering on at this point so it's probably a physical problem.
Prosis said:
Thanks but the phone isn't even powering on at this point so it's probably a physical problem.
Click to expand...
Click to collapse
Good news! I got an RMA!!
Thanks for your help everyone!
Hello guys, I just got a Pixel 3XL from somebody and I thought I could make it to work, but now I'm stucked. The phone is stucked in fastboot and the bootloader is LOCKED. I tried to unlock it using GUIDE for Google Pixel 3 XL unlock bootloader, but I cannot do this task 100% because I cannot enable OEM unlock and USB debugging since the phone is stucked in fastbood mode. Also, if I try to get into recovery mode, when I press the power button to get into recovery, the phone turns off. I ust want to make it stock.
Any idea how to solve this? Thank you
try sideloading the full OTA.
https://developers.google.com/android/ota
robertoancini51 said:
Hello guys, I just got a Pixel 3XL from somebody and I thought I could make it to work, but now I'm stucked. The phone is stucked in fastboot and the bootloader is LOCKED. I tried to unlock it using GUIDE for Google Pixel 3 XL unlock bootloader, but I cannot do this task 100% because I cannot enable OEM unlock and USB debugging since the phone is stucked in fastbood mode. Also, if I try to get into recovery mode, when I press the power button to get into recovery, the phone turns off. I ust want to make it stock.
Any idea how to solve this? Thank you
Click to expand...
Click to collapse
The answer is the same as in your other thread. If you cannot get into recovery mode and your bootloader is locked there is nothing you can do. The mystery is how you lost recovery with a locked bootloader... it may have been unlocked at one time and someone re-locked it?
v12xke said:
The answer is the same as in your other thread. If you cannot get into recovery mode and your bootloader is locked there is nothing you can do. The mystery is how you lost recovery with a locked bootloader... it may have been unlocked at one time and someone re-locked it?
Click to expand...
Click to collapse
that's the mistery. so I cannot do nothing with the phone? Is no any solution to put the recovery mode back into the phone to work?
robertoancini51 said:
that's the mistery. so I cannot do nothing with the phone? Is no any solution to put the recovery mode back into the phone to work?
Click to expand...
Click to collapse
Not if you can't fastboot the boot.img there isn't. Like the others said, if you can't get into stock recovery to side load the OTA, your kinda hosed.
robertoancini51 said:
that's the mistery. so I cannot do nothing with the phone? Is no any solution to put the recovery mode back into the phone to work?
Click to expand...
Click to collapse
No, nothing you can do because you cannot fastboot flash any partition when the bootloader is locked, and without a working recovery you cannot use adb to sideload an OTA. My guess is your friend at one time had the bootloader unlocked but he later locked it back before giving it to you. Once the bootloader is unlocked it should never be locked again... unless you know exactly what you are doing and have good reason to do so. If you have tried multiple times to unlock the bootloader using fastboot -and- exhausted all means of booting to recovery (you are positive you know how to get there and cannot) then there is no way to recover. Until one of these two things changes you cannot get back in. Sorry man!
Badger50 said:
Not if you can't fastboot the boot.img there isn't. Like the others said, if you can't get into stock recovery to side load the OTA, your kinda hosed.
Click to expand...
Click to collapse
ok, thank you
v12xke said:
No, nothing you can do because you cannot fastboot flash any partition when the bootloader is locked, and without a working recovery you cannot use adb to sideload an OTA. My guess is your friend at one time had the bootloader unlocked but he later locked it back before giving it to you. Once the bootloader is unlocked it should never be locked again... unless you know exactly what you are doing and have good reason to do so. If you have tried multiple times to unlock the bootloader using fastboot -and- exhausted all means of booting to recovery (you are positive you know how to get there and cannot) then there is no way to recover. Until one of these two things changes you cannot get back in. Sorry man!
Click to expand...
Click to collapse
I just cannot believe that the phone is unusable
robertoancini51 said:
I just cannot believe that the phone is unusable
Click to expand...
Click to collapse
Just to be sure I am reading this right, instead of seeing the "no command" screen when you toggle the smart menu option to recovery and hitting the power button, the device shuts down?
sliding_billy said:
Just to be sure I am reading this right, instead of seeing the "no command" screen when you toggle the smart menu option to recovery and hitting the power button, the device shuts down?
Click to expand...
Click to collapse
Yes
robertoancini51 said:
Yes
Click to expand...
Click to collapse
You mention not being able to toggle OEM unlock or USB debugging, but are you sure they are not already toggle? Have you tried locking or unlocking the bootloader from fastboot (hopefully you can see the device on your computer when plugged in)? Your issue reminded me of another thread https://forum.xda-developers.com/showpost.php?p=78277194&postcount=260 where it looked like an unlock only partially worked. I assume you are not the registered owner and cannot contact Google about the issue.
sliding_billy said:
You mention not being able to toggle OEM unlock or USB debugging, but are you sure they are not already toggle? Have you tried locking or unlocking the bootloader from fastboot (hopefully you can see the device on your computer when plugged in)? Your issue reminded me of another thread https://forum.xda-developers.com/showpost.php?p=78277194&postcount=260 where it looked like an unlock only partially worked. I assume you are not the registered owner and cannot contact Google about the issue.
Click to expand...
Click to collapse
I'm not sure if they are already toggle. Yes, I've tried to lock/unlock bootloader from fastboot, but nothing. The PC sees it from device manager. No,I'm not registered.
robertoancini51 said:
I'm not sure if they are already toggle. Yes, I've tried to lock/unlock bootloader from fastboot, but nothing. The PC sees it from device manager. No,I'm not registered.
Click to expand...
Click to collapse
Might be worth posting something on the Google forum. If an agent isn't checking registration, you might get some ideas. The only thing else I can think is that there may be some key combination (vol down or up and hold) when pressing the power button to get to recovery to keep it from shutting down. Good luck.
sliding_billy said:
Might be worth posting something on the Google forum. If an agent isn't checking registration, you might get some ideas. The only thing else I can think is that there may be some key combination (vol down or up and hold) when pressing the power button to get to recovery to keep it from shutting down. Good luck.
Click to expand...
Click to collapse
I Have written to ghem, I wait an answer from them. I will try some combination and come back with an answer
i have the same problem
robertoancini51 said:
I Have written to ghem, I wait an answer from them. I will try some combination and come back with an answer
Click to expand...
Click to collapse
who did you write to? can you share please? also if you manage to solve the problem, please share the solution.
many thanks,
Cant you take the back of and use EDL Mode? its qualcomm so its available.? wheres all the master techys in the pixel thread?You can push the entire factory image whether its locked or unlocked with EDL.
---------- Post added at 04:56 PM ---------- Previous post was at 04:50 PM ----------
https://www.leakite.com/revised-how-to-unbrick-qualcomm-android/
Remember to change any images to googles.
I try to relock bootloader on my htc 10, stock rom, s-on (whatever that means), I go to cmd, enter adb devices and when the device ID shows up I proceed with adb reboot bootloader and then fastboot oem lock which shows failed unknown command, what do I do wrong here? the fastboot exe is present in the folder so what's going on here? Please help
Selvyn said:
I try to relock bootloader on my htc 10, stock rom, s-on (whatever that means), I go to cmd, enter adb devices and when the device ID shows up I proceed with adb reboot bootloader and then fastboot oem lock which shows failed unknown command, what do I do wrong here? the fastboot exe is present in the folder so what's going on here? Please help
Click to expand...
Click to collapse
Try from Download Mode instead of bootloader mode, if you haven't already.
Sent from my Pixel 3 XL using Tapatalk
santod040 said:
Try from Download Mode instead of bootloader mode, if you haven't already.
Sent from my Pixel 3 XL using Tapatalk
Click to expand...
Click to collapse
I... don't know how to thank you. Now I can finally give my mom this phone. On all videos I've seen this was performed from bootloader mode, not download mode. The reason I've unlocked the bootloader was because I wanted to do root but never got around it and left it that way which made it vulnerable. In consequence something went wrong recently when I tried to send files through usb, phone froze, I restarted using vol down+power and the phone wiped itself just like that with all my files, notes and photos gone. I decided to give the phone to my mom but I had to lock it first to make sure this won't ever happen to her. Thank you so much :good:
Selvyn said:
I... don't know how to thank you. Now I can finally give my mom this phone. On all videos I've seen this was performed from bootloader mode, not download mode. The reason I've unlocked the bootloader was because I wanted to do root but never got around it and left it that way which made it vulnerable. In consequence something went wrong recently when I tried to send files through usb, phone froze, I restarted using vol down+power and the phone wiped itself just like that with all my files, notes and photos gone. I decided to give the phone to my mom but I had to lock it first to make sure this won't ever happen to her. Thank you so much :good:
Click to expand...
Click to collapse
No problem.
Glad that did the trick for you. [emoji106]
Sent from my Pixel 3 XL using Tapatalk