Develop Bugs

[HOWTO]- Performing a Nandroid Restore Manually using ADB

[HOW TO] Perform a Nandroid Restore via the Android Debug Bridge (ADB)
(This guide assums that you have already installed and set up adb tools on you PC)
1. Start phone in recovery mode, by turning it on while holding "Home" and "Power" buttons.
2. Plug the phone into the PC with a USB cable
3. Start Windows Command Prompt on your PC, by pressing Start on your PC and typing CMD into the run or search bar depending on your operating system. Then selecting Command Prompt.
4. Within the command prompt window, change the directory to the one your adb tools are by typing the following:
cd c:\sdk\tools
Click to expand...
Click to collapse
The path you put in may be different to this example, as it depends where on your PC your adb tools are kept.
5. Then type:
adb shell
Click to expand...
Click to collapse
6. Now type:
mount /sdcard
Click to expand...
Click to collapse
7. Now you need to change directory again to the one holding your nandroid back-up data, so first type
cd /sdcard
Click to expand...
Click to collapse
8. Then type:
cd nandroid
Click to expand...
Click to collapse
9. Now you need to find the specific name for the folder that holds your Nandroid Backup images, so type:
ls
Click to expand...
Click to collapse
and view the list that appears.
10. Now to enter the folder you want to back up to type
cd HT**********
Click to expand...
Click to collapse
obviously replacing the *s with your numbers and letters. FYI the number string is your Device Serial number.
11. Again type
ls
Click to expand...
Click to collapse
and view the list that appears.
12. Now to enter the folder you want to back up to type
cd BCD***-********-****
Click to expand...
Click to collapse
obviously replacing the *s with your numbers and letters. FYI the format of these digits is BCDXYZ-YYYYMMDD-HHMM from when the back up was created.
13. Now type:
nandroid-mobile.sh restore
Click to expand...
Click to collapse
14. Just press enter to select default.
15. Double check that the Default backup that is found is the one you want then press enter again.
Your selected backup will now be restored. When your CMD window looks like the one below you can reboot your phone and it will be as you remember it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
A big thanks goes to Pulser, without whom I would still be stuck, and this guide wouldn't have been written.

Nice. But are steps 6-12 really necessary? When in shell it should enough enter nandroid-mobile.sh -r, press enter to get you the list of available backups, pressing enter once again restores the last backup, or if you want an older just type the full name of that backup.

Install apk
Hello Fellow Androids!
If this is off topic, please accept my apologies. I am searching through all of XDA for a simple solution to adding apk. Now before you start bashing, please keep in mind that I am well aware of the "search" options + google + XDA etc.
Long story short, I have:
1) Rooted
2) Fashed many Roms (currently on Stock 2.1)
3) Lag Fixxed (see signature)
4) Removed Bloatware
5) I am familiar with ABD and commands
Problem:
All I'm trying to do is install certain "apk"s using ADB. I am well aware of the Program that installs/ pushes apps automatically that are found in G1 + Vibrant + HTC + Droid Forums without having to do any typin......BUT.....I would like to know my way around ABD <----Main reason why i dont want the easy way out.
I have been here:
http://forum.xda-developers.com/showthread.php?t=716806
as well as here:
http://forum.xda-developers.com/showthread.php?t=743457
even been here:
http://forum.xda-developers.com/showthread.php?t=740545
I know what you are thinking, why not use them? As i said before, i would like to be efficient with ADB. So...
I have tried methods found here:
http://forum.xda-developers.com/showthread.php?t=517874
As well as:
http://forum.xda-developers.com/showthread.php?t=532719
The problem I am having is:
Whether i navigate to my folder (desktop with all my apps) and use either
"adb push app /system/sd/app
adb push app-private /system/sd/app-private"
or simply
"adb install <path to file> - Example: adb install c:/apps/apps2sd.apk"
I always get the error: "cant find <whatever apk> to install"
No matter which directory i have it, i get that message.
Note:
1) I have debugging on
2) I mounted sd <----also tried Without mounting
3) I have used the same command when I removed bloatware but i understand Adding apks are slightly different.
4) I have all the drivers installed + Microsoft's .net framework + etc
What am i doing wrong?
All Critics, input, education bashing (just not hating) lol are welcome. Thanks!

put adb in your path... cd to the apk directory and run adb push *.apk /system....

TylerDurdenK said:
[HOW TO] Perform a Nandroid Restore via the Android Debug Bridge (ADB)
(This guide assums that you have already installed and set up adb tools on you PC)
and view the list that appears.
12. Now to enter the folder you want to back up to type
obviously replacing the *s with your numbers and letters. FYI the format of these digits is BCDXYZ-YYYYMMDD-HHMM from when the back up was created.
13. Now type:
MD window looks like the one below you can reboot your phone and it will be as you remember it.
http://farm3.static.flicn.[/QUOTE]
I get the error "nandroid-mobile.sh not found" after step 13. please help.
Click to expand...
Click to collapse

Dont use this, use jordfaz's clockworkmod, if you really need to use this adb script then you need to get nandroid-mobile.sh script somewhere

Adb Shell

So I have a rooted Evo and am wondering how the heck do I open up a shell? I'm trying to see if I my Evo is properly rooted and it says I need to open up a shell so I can check for this. I'm guessing it's like opening a Linux terminal but I have no idea how to do this on my phone and it seems like it's a fairly common thing. Should I have access to an adb shell after rooting? I am new to all of this so please go easy on me...

PC-48 said:
So I have a rooted Evo and am wondering how the heck do I open up a shell? I'm trying to see if I my Evo is properly rooted and it says I need to open up a shell so I can check for this. I'm guessing it's like opening a Linux terminal but I have no idea how to do this on my phone and it seems like it's a fairly common thing. Should I have access to an adb shell after rooting? I am new to all of this so please go easy on me...
Click to expand...
Click to collapse
Just try downloading an app that requires root... like Titanium backup or wifi tether... all on the market...
or goto your tools folder from the SDK..with your phone plugged into your computer...on charge mode.... from a command prompt type "adb shell" and then if you get a "#" you are rooted.

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
that is for the terminal emulator for your phone. Or just grab it from the market:
'Android Terminal Emulator' by Jack Palevich

Ok so I downloaded that app using the barcode scanner and it runs so I must be properly rooted. I'm just wondering what the SDK is that apristel mentioned. I'm guessing Software Development Kit but I don't have one of those that I am aware of. I used the Terminal Emulator and typed in adb shell and it responded with "adb: permission denied". I'm just trying to learn about how all of this stuff works, Thank you for your help so far.

PC-48 said:
Ok so I downloaded that app using the barcode scanner and it runs so I must be properly rooted. I'm just wondering what the SDK is that apristel mentioned. I'm guessing Software Development Kit but I don't have one of those that I am aware of. I used the Terminal Emulator and typed in adb shell and it responded with "adb: permission denied". I'm just trying to learn about how all of this stuff works, Thank you for your help so far.
Click to expand...
Click to collapse
http://developer.android.com/sdk/index.html
After you install that you will be able to open command prompt (windows) and type adb shell (when device is pluged in and in usb mode) to get shell access via your pc.

Ahh! Ok it's all starting to make sense now. By "usb mode" do you mean the Disk drive option or is it the Charge only option? I'm talking about the Connect to PC options...

I think he means usb debugging mode and charge only.

vbyt said:
I think he means usb debugging mode and charge only.
Click to expand...
Click to collapse
Yeah thats exactly what i meant. thanks for clearing that up.

[Q] Adb is not recognized as an intern or extern command

Hi, so i'm very new to Android and while attempting to do the gfree permaroot for my desire Z, i came across a problem. When I type the commands, it says that adb is not and intern or extern command. I have adb file in platform-tools (400ko). When i open it, it make a cmd screen for about 2 seconds then shuts down. Can someone help me with this problem
I just installed HTC sync and my computer cannot find any device attached. It says: the htc vision htc port does not repons.
Thanks
Vince

are you doing CD C:/location of adb/adb?
You must direct your command line to the directory of adb.
also run cmd as administrator if you're on vista or win7.
If you're not a command line pro I suggest you just rename your folder to whatever you want in C:/folderhere
For example heres the folder renamed to "android"
then just do CD C:/android
Then type "adb" and hit enter
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and boom! you're in adb!
Hope this helps
I'm no adb pro but I'm ok at cmd. Maybe I should make a video or something on the basics to getting adb running if there isn't one already?

Thanks for the quick reply! It helped me figure out that you need to open adb before using the adb command but the same error occurs (is not an intern/extern command) when i try it

Vincethedevil said:
Thanks for the quick reply! It helped me figure out that you need to open adb before using the adb command but the same error occurs (is not an intern/extern command) when i try it
Click to expand...
Click to collapse
Nah, you still aren't getting it
How did you install ADB? If you search in Windows for the file "adb.exe" what does it tell you?

it's in the platform tools folder in the sdk

Vincethedevil said:
Thanks for the quick reply! It helped me figure out that you need to open adb before using the adb command but the same error occurs (is not an intern/extern command) when i try it
Click to expand...
Click to collapse
I'm not quite sure what you mean by this, I wonder if you're doing something wrong. Have you followed this guide ? http://forum.xda-developers.com/showthread.php?t=865685
If you have added the correct folders to your path, as explained in the guide, it should find adb ok.
If it's finding adb ok, then if you run "adb devices", is that not showing your phone ? Are you using the original HTC cable to connect to your phone ? Third-party ones sometimes will not work.

Yeah i'm using the original Htc cable. I have downloaded Htc Sync and it appears as "my htc" in device manager. Although, Htc sync doesn't recognize any plugged in phone.
For adb, i go in cmd, change the path with cd to the path where is the adb.exe, then type adb. A series of text follow. Then, i switch to the folder where is gfree (with cd) and type the first line for temp root. That when it says that adb is not recognized as an intern or extern command

Since adb.exe is not located in your gfree directory, it's not a recognized command. You either need to run the commands directly from your platform tools directory (and use the full directory paths for the gfree commands) or place the path for adb in your environment variables so that adb can be called from any directory (step four in the ADB for noobies linked earlier). This is the easier method.

I tried it but it's not working. I'll take pictures tomorrow so my obvious noob error can be spotted

Adding adb to your path
Hey there,
Here's a quick guide to fix your problem (basically, you don't have adb added to your path). Btw, this guide was made on Windows 7, but the principle should be the same for Vista and XP (though the steps are different).
Step 1: Right click "Computer" or "My Computer"
Step 2: On the left side find "Advanced system settings" and click it.
Step 3: On the Advanced tab, click "Environment variables"
Step 4: In the bottom part of the window, scroll until you find the row that starts with "Path" and click "Edit"
Step 5: At the end of the existing line, add a semicolon ( ; ) and the path to your android toolkit. If the path contains spaces, don't forget to enclose it in quote marks ( "C:\path to adb\tools\" )

Vincethedevil said:
For adb, i go in cmd, change the path with cd to the path where is the adb.exe, then type adb. A series of text follow. Then, i switch to the folder where is gfree (with cd) and type the first line for temp root. That when it says that adb is not recognized as an intern or extern command
Click to expand...
Click to collapse
You haven't set the Path up so that it can find adb, as has been said, and that's all covered in the guide that I previously linked to. But the previous poster has provided you with an excellent step-by-step solution.

Thanks alot, my adb problem is now solved! I just have one more question, when i plug my phone, htc sync cannot recognize it. Although, when i write adb devices in cmd, my phone appear. Am I still gonna be able to permaroot or should i mess with the drivers.
Thx
Vince

It's not a driver problem, it's an HTC Sync problem. Your phone has to be in Sync mode and you have to wait a few minutes (mine takes up to 20 mins) for HTC Sync to recognize it.

sounds like you'll be able to root just fine if it recognizes and responds to adb.
Not sure about htc sync, I don't even know what that is...lol

not able to root
i am using this procedure
http://forum.xda-developers.com/showthread.php?t=1601038
as i am running runme.bat i am getting this screen please help

Need to set up adb, there are tons of guides on xda and the web to do this properly, follow one of them and then try your whatever you're doing again
Sent from my Nexus 7 using xda premium

demkantor said:
Need to set up adb, there are tons of guides on xda and the web to do this properly, follow one of them and then try your whatever you're doing again
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
thanx for reply/..
not able to to set up adb.. please help if you can
should i uninstall existing drivers and again install it

You may need to reinstall drivers but first make sure you have the right ones as well as adb.exe download from the sdk or whereever you get it
See the third post. In this thread
http://forum.xda-developers.com/showthread.php?p=31899577
If you're still having issues let me know and ill help ya
Sent from my MyTouch 4G Slide using xda premium

Root LG G4 Marshmallow without bootloader Unlocked

Hi guys,i've updated yesterday my LG G4 (H815) to marshmallow,but i've lost the root.
Could you show me a method to reroot my G4 without unlock the Bootloader please?
Unfortunately i can't unlock my bootloader because of an error and i can only root with another method...
Thanks a lot.

robsup79 said:
Hi guys,i've updated yesterday my LG G4 (H815) to marshmallow,but i've lost the root.
Could you show me a method to reroot my G4 without unlock the Bootloader please?
Unfortunately i can't unlock my bootloader because of an error and i can only root with another method...
Thanks a lot.
Click to expand...
Click to collapse
I'm interested: What error do you get? You maybe do something wrong while unlocking the bootloader? Maybe not copying the token entirely?
Well, for now, there is no method to root your LG G4 on android 6.0, if the bootloader is locked. I'm sorry that I have to disappoint you Greetz

Follow_and_Feel said:
I'm interested: What error do you get? You maybe do something wrong while unlocking the bootloader? Maybe not copying the token entirely?
Well, for now, there is no method to root your LG G4 on android 6.0, if the bootloader is locked. I'm sorry that I have to disappoint you Greetz
Click to expand...
Click to collapse
Hi,i try explain you (sorry for the english):
When i'm on the second stage in command line and i enter "fastboot oem device-id",i don't receive the strings with the ID Number but i receive "Waiting for device" and i can't go on.
I've installed and uninstalled 3 times the SDK and the LG Drivers but the problem remain....
The passeges i've done are:
-Installed the SDK from this file in the website "installer_r24.4.1-windows"
-Installed last LG drivers "LG-Mobile-Driver_v4.0.3.0"
-Connect the phone with debug and Oem flagged

robsup79 said:
Hi,i try explain you (sorry for the english):
When i'm on the second stage in command line and i enter "fastboot oem device-id",i don't receive the strings with the ID Number but i receive "Waiting for device" and i can't go on.
I've installed and uninstalled 3 times the SDK and the LG Drivers but the problem remain....
The passeges i've done are:
-Installed the SDK from this file in the website "installer_r24.4.1-windows"
-Installed last LG drivers "LG-Mobile-Driver_v4.0.3.0"
-Connect the phone with debug and Oem flagged
Click to expand...
Click to collapse
Ok that sounds like you didn't tick "enable OEM-unlock" in the developer options of your phone, did you?

Follow_and_Feel said:
Ok that sounds like you didn't tick "enable OEM-unlock" in the developer options of your phone, did you?
Click to expand...
Click to collapse
Yes,i tick that voice i'm going crazy....damn

robsup79 said:
Yes,i tick that voice i'm going crazy....damn
Click to expand...
Click to collapse
Ok. Maybe you need to confirm the connection on your phone if it says "Waiting for device"? Did you check it? Is your device definately H815 Eu Model? ANd do you have adb.exe and fastboot on your pc?
Please open a command prompt in the adb folder and type:
adb.exe devices
What is the output?

Follow_and_Feel said:
Ok that sounds like you didn't tick "enable OEM-unlock" in the developer options of your phone, did you?
Click to expand...
Click to collapse
Follow_and_Feel said:
Ok. Maybe you need to confirm the connection on your phone if it says "Waiting for device"? Did you check it? Is your device definately H815 Eu Model?
Click to expand...
Click to collapse
Yes is the H815 Italian Model no brand.
How do you mean with "you need to confirm the connection?

robsup79 said:
Yes is the H815 Italian Model no brand.
How do you mean with "you need to confirm the connection?
Click to expand...
Click to collapse
Ok forget about it! You're already in fastboot mode then right? Do you have the fastboot.exe on your computer? You need fastboot.exe and adb.exe on your device if you want to get the unlock token.
Please open a command prompt in windows and type
fastboot.exe devices
and tell me what's the output. Please do the same with
adb.exe devices
Maybe the computer doesn't recognize your phone because you don't have a fastboot.exe

Follow_and_Feel said:
Ok forget about it! You're already in fastboot mode then right? Do you have the fastboot.exe on your computer? You need fastboot.exe and adb.exe on your device if you want to get the unlock token.
Please open a command prompt in windows and type
fastboot.exe devices
and tell me what's the output. Please do the same with
adb.exe devices
Maybe the computer doesn't recognize your phone because you don't have a fastboot.exe
Click to expand...
Click to collapse
Ok when i type "adb.exe devices":
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And when i type "fastboot.exe devices":
And this is the folder where i have the files to open the command:

And now when i try to catch the id,before my control panel recognizes the G4 but i don't know how like Samsung model:
After i open the command and insert the strings:
And in control panel the LG change and becomes an Alcatel:
How is it possibile....damn....

robsup79 said:
Ok when i type "adb.exe devices":
And when i type "fastboot.exe devices":
And this is the folder where i have the files to open the command:
Click to expand...
Click to collapse
Okay. So these screenshots were taken when you were in the bootloader? The problem is, that your PC doesn't recognize your device in fastboot mode! There should be an output if you type fastboot.exe devices, but there isn't. Which windows are you on?
The problem is not your phone or the unlock method. It's you computer I guess. Maybe you do a google search on how to get your device recognized.
And because this is far off the original topic you posted, please change the name of the thread to "Can't unlock bootloader (H815)" or something
EDIT: You're in the bootloader right?

Follow_and_Feel said:
Okay. So these screenshots were taken when you were in the bootloader? The problem is, that your PC doesn't recognize your device in fastboot mode! There should be an output if you type fastboot.exe devices, but there isn't. Which windows are you on?
The problem is not your phone or the unlock method. It's you computer I guess. Maybe you do a google search on how to get your device recognized.
And because this is far off the original topic you posted, please change the name of the thread to "Can't unlock bootloader (H815)" or something
EDIT: You're in the bootloader right?
Click to expand...
Click to collapse
I'm in windows 7....
Yes i'm in the bootloader

robsup79 said:
I'm in windows 7....
Yes i'm in the bootloader
Click to expand...
Click to collapse
Ok. So the problem is your PC not detecting your phone as a fastboot device! This is why you always get the message: "Waiting for device", if you enter "fastboot oem device id". I don't know how to fix that. Maybe you have to download another fastboot.exe for windows 7. But I'm pretty sure that this is the only problem why you can't unlock the bootloader. Maybe you try these. I'm really sorry that I can't help you

Follow_and_Feel said:
Ok. So the problem is your PC not detecting your phone as a fastboot device! This is why you always get the message: "Waiting for device", if you enter "fastboot oem device id". I don't know how to fix that. Maybe you have to download another fastboot.exe for windows 7. But I'm pretty sure that this is the only problem why you can't unlock the bootloader. Maybe you try these. I'm really sorry that I can't help you
Click to expand...
Click to collapse
Ok i try with Minimal ADB and Fastboot and workssssss
But now i've the Unlock.bin on my desktop and i don't know how i can go on...please help me :highfive:

robsup79 said:
Ok i try with Minimal ADB and Fastboot and workssssss
But now i've the Unlock.bin on my desktop and i don't know how i can go on...please help me :highfive:
Click to expand...
Click to collapse
Haha! Glad that I could help (please hit thanks button ). So if you have the unlock token go to this site, register and do steps 10-16 and voila - you're bootloader is now unlocked

Follow_and_Feel said:
Haha! Glad that I could help (please hit thanks button ). So if you have the unlock token go to this site, register and do steps 10-16 and voila - you're bootloader is now unlocked
Click to expand...
Click to collapse
Ahahaha yes but i'm stopped on point 14
I've the Unlock.bin on my desktop and i don't know i can insert it on the terminal....
When i open the Minimal Adb i don't know what i have to type...

robsup79 said:
Ahahaha yes but i'm stopped on point 14
I've the Unlock.bin on my desktop and i don't know i can insert it on the terminal....
When i open the Minimal Adb i don't know what i have to type...
Click to expand...
Click to collapse
you need to retrieve the unlock.bin via email. Do all the steps again from the beginning please and you'll have no problems
EDIT: If you already have received the unlock.bin put everything (ADB and fastboot exe AND the unlock.bin in one folder! Should work then

robsup79 said:
Ahahaha yes but i'm stopped on point 14
I've the Unlock.bin on my desktop and i don't know i can insert it on the terminal....
When i open the Minimal Adb i don't know what i have to type...
Click to expand...
Click to collapse
First question; Where'd you get the unlock.bin file? Was it generated with your specific device?
Boot back into Android on your phone. Go to "Settings>General>Developer Options> Activate "Enable OEM unlock"". In the same menu, with the USB-Cable detached, enable "USB debugging".
Put the unlock.bin file in the same folder as the ADB and Fastboot files (Usually C:/adb/)
Plugin your phone via USB. It's better you use a port on the back of your PC.
Type adb reboot bootloader
Type fastboot flash unlock unlock.bin
If this fails, try a different PC.
EDIT: Which version of ADB do you use? I know that 1.4.2 has some issues. It's worth a shot to try ADB 1.3 Minimal installer.
EDIT2: Sorry, overlooked that your thread has two pages and you already enabled OEM unlock. I'd say you try it on another PC. I also have issues with ADB and Fastboot on Marshmallow.
EDIT3: You're missing a file in your ADB folder. Extract and put the attached .dll file into the same folder as your ADB files.

Hi,i've solved with Adb Minimal and "Follow_and_Feel" help.
Thanks a lot to all,you're the best.

robsup79 said:
Hi,i've solved with Adb Minimal and "Follow_and_Feel" help.
Thanks a lot to all,you're the best.
Click to expand...
Click to collapse
Some time ago I had a similar issue with a permanent message, either 'waiting for device' or 'downloading <file>' (sorry, I don't remember what exactly was in a message). But I have solved that problem by changing usb data cable. I tried a few pieces until I found a good one. It's preferable to use an original data cable.

Bootloader

I have read, I have searched thread after thread. I have the Google Pixel XL on Verizon. I have followed the directions to the letter for unlocking bootloader using dePixel. The issue I have is with the Developer Options. I am unable to enable the OEM Unlocking because it is grayed out. I have reset the device like 10 times. I have automatic updates disable in developer options. I need to be point in the right direction or have someone that can relate, to chime in. I am not looking for root....I just want the bootloader unlocked
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

That button will always be greyed out on the VZW firmware. After you unlocked do you see a warning message on boot? How do you know you are not, in fact, unlocked?

You don't mess with that button. Just follow the directions for dePixel8
Sent from my Pixel XL using Tapatalk

DualSportDad said:
You don't mess with that button. Just follow the directions for dePixel8
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
I followed to the letter and I get nothing

Mike02z said:
That button will always be greyed out on the VZW firmware. After you unlocked do you see a warning message on boot? How do you know you are not, in fact, unlocked?
Click to expand...
Click to collapse
well for starters after I entered the cmd lines.....device never rebooted into fastboot for me to run the unlock cmd line

Ok first before we can help you, can you post the screen of the cmd window or copy paste the results of it?

mikeutsey said:
well for starters after I entered the cmd lines.....device never rebooted into fastboot for me to run the unlock cmd line
Click to expand...
Click to collapse
Set the phone from charging to file transfer. After hitting enter for the last command line op pen the chrome browser app. I don't know why but that's what worked for me.
Sent from my Pixel XL using Tapatalk

Why not just flash the Google factory image once you run the depixel8 program?
Edit: Looks like you missed a step somewhere. Make sure your device is connected to your computer via adb. I would run the 15 second adb install (Google it) than put the depixel8 file in your tools folder. Open tool folder shift and right click to to open cmd promt. Type adb devices and see if it's connected. Also be sure to turn on USB debugging in dev options.

jaxenroth said:
Why not just flash the Google factory image once you run the depixel8 program?
Edit: Looks like you missed a step somewhere. Make sure your device is connected to your computer via adb. I would run the 15 second adb install (Google it) than put the depixel8 file in your tools folder. Open tool folder shift and right click to to open cmd promt. Type adb devices and see if it's connected. Also be sure to turn on USB debugging in dev options.
Click to expand...
Click to collapse
The dePixel8 Program has yet to work for me. Still have not successfully unlocked bootloader

Marghost said:
Ok first before we can help you, can you post the screen of the cmd window or copy paste the results of it?
Click to expand...
Click to collapse

On the pic you posted i see that you need to put a Space between 755 and /...
Can you post the full log If this is not working!

Was able to get it to reboot with cmd line but still not working. Thanks for all of your help with this
Marghost said:
On the pic you posted i see that you need to put a Space between 755 and /...
Can you post the full log If this is not working!
Click to expand...
Click to collapse

OK I see try close your phone and boot to the bootloader screen with power and vol down pressed at boot. After run the command
fastboot oem unlock
And tell me what you see!

That did it.....thanks guys....never would have even considered physically turning off device and and manually fastboot :highfive:
Marghost said:
On the pic you posted i see that you need to put a Space between 755 and /...
Can you post the full log If this is not working!
Click to expand...
Click to collapse

Np bro glad I helped. If you want give me some thumbs up hehe
Great day
Sent from my Pixel XL using XDA Labs

Is ADB working for you? I'm not sure where your are in the process, so forgive me if you've done these steps:
- enable debugging in developer options (must first tap on build number 10x or whatever
- if you do adb devices from command prompt, do you get the device id? You need to allow the computer to talk to the phone (security authorization on the phone the first time you attempt adb), as well as have drivers properly installed on computer
- assuming adb is writing properly, people seem to have best success with depixel8 if they set screen timeout to 5 min or longer, and after starting depixel8 commands on the computer, is screen blanks out, truth screen back on and try and run an app ...
Hope this helps