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
Related
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
The right edge of my touchscreen has gone dead, not sure what the problem is, maybe the ribbon cable? I'm not sure, but I contacted htc and they said it's still under warranty and will be repaired (just so long as there's no physical/water damage, ect.) well my phones in pretty good shape, so I'm hoping I wont get charged.
However, I figured I should probably get back to stock and S-On
an quick tutorials on how?
This is why we have a Wiki, and a search function.
http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Returning_to_Stock
If you have any particular questions, search first, if you can't fix them at that point, then post back to the thread for specific help with a problem.
I can't even figure out the first step :/
how do I check Gfree verify? I type that into terminal emulator, nothing heppens
Edit:
I'm not a n00b and the rest of the instructions look do-able, but how do I do gfree_verify?
bumpity bump bump
It's on the wiki page. You can find it if you search the page for 'gfree_verify'. I've linked the section for you below. Scroll down till you see '5. Verify the success of gfree'.
http://forum.xda-developers.com/wik..._Root_.2F_.22Permaroot.22.29_using_gfree_v0.7
Thank you both very much
Sorry, I'm trying to unroot it, but it's not working.
When I "$ adb shell chmod 755 /data/local/tmp/gfree_verify" it says "no such file or directory exists
But i'm positive that I have gfree, so I decided to skip the verifying
I go down to the next step, (and honestly, I don't know what my main version is) but when I use "# /data/local/tmp/misc_version -s 1.19.531.1" It says "permission denied"
Bump (sorry)
swee08315 said:
Sorry, I'm trying to unroot it, but it's not working.
When I "$ adb shell chmod 755 /data/local/tmp/gfree_verify" it says "no such file or directory exists
But i'm positive that I have gfree, so I decided to skip the verifying
Click to expand...
Click to collapse
You are positive the you have gfree.
Your device is positive you haven't got gfree_verify.
Guess who's right?
Follow Bharakrama's link, read, follow, success.
I too was sure I had adb and gfree but it wasn't working. I updated my android sdk and path variable and it worked again.
I'm also trying to return to stock. My gfree is working. How do I know if my main version is higher than 1.19.531.1? I'm using Cyanogen. Do you know how I find, or what the CID for Bell Mobility is?
I'm pretty sure I have Gfree, when I rooted it, it got unlocked and I'm now using it on at&t, that means I have gfree, doesn't it?
I'm thinking that I probably have footclans problem with the adb because I had ubuntu on thiis machine before and I just installed windows recently. I haven't had to use adb since then.
Try reinstalling ADB or updating the android sdk.
thanks, everything works now except this:
Disconnect the phone from USB and shutdown the phone.
Boot into hboot by holding <Vol-Down> while powering on.
hboot should load the PC10IMG.zip automatically and the ask you if you want to update. Press <Vol Up> to start the update.
After updating the radio hboot will start again (screen will get dark for some seconds)
If you had the fake S-OFF engineering hboot installed it will be replaced by this process
Click to expand...
Click to collapse
The text is too fast to read, but I think it says wrong image or something?
edit: theres a bunch of lines, and I think most of them say "no image"
bump bump.
my screen is really becoming very annoying to use now. I really have to get this factory reset soon so I can send it in.
I really need to get this figured out.
Sorry, but if I can get this resolved by the weekend, it would be wonderful.
anyone know why the factory image wouldn't be writing?
I'll try again tomorrow and record what is displayed across the screen if that will help.
Did you name the file right and check the md5 sum? Also make sure PC10IMG.zip is not is labeled exactly that! not.zip.zip unhide file extensions if your on windows. Also it must be on the root of the sd not in a folder of any kind.
Here's a screenshot of the zip on my sdcard
{
"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 here's what happen when I boot with the volume down key pressed:
I also tried to use the following in adb shell, but I get permission denied
# /data/local/tmp/gfree -s on -c T-MOB010
Click to expand...
Click to collapse
Does that last screenshot help at all?
I'm busy with classes, and really need this done before the 1 year warranty is up.
Sent from my HTC Desire Z using XDA App
So I was messing around with different one clicks since I got ADB going on my kindle fire and I was able to Successfully use SuperOneClick 2.2 to root my kindle fire!
Sorry for the mess. Its late, and I wanted to type this up so I could crash...
To get adb going you must download the android sdk (google it).
*Run SDKManager.exe and download the google-usb_drivers package from "3rd party tools"
* Download platform-tools as well
Open a command prompt and run adb update usb to get the .android folder to appear.
goto: %USERPROFILE%\.android and edit the adb_usb.ini and add this to the end of the file and save:
Code:
0x1949
then go into where you have the sdk at and open the google-usb_driver folder and edit android_winusb.inf and add this to the [Google.NTx86] section and [Google.NTamd64] section:
Code:
;Kindle Fire
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0006
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&MI_01
save and close
If you have already plugged your kindle into the usb you may have to open device manager and find "Kindle" under other devices and choose the android_winusb.inf file.
Turn on Installation of apps from unknown sources: tap the top bar>choose more...(+)>device
open a command prompt and run adb kill-server then try adb devices..
you should see a device listed.
go here: http://forum.xda-developers.com/showthread.php?t=803682a
download and run SuperOneClick and choose the "root" option. let it go!
Enjoy!
Proof:
{
"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"
}
Awesome!
Why do I have a mac
That was quick. I wonder if Amazon prefers the device to be rootable or not? Normal Kindle is quite easy to root too.
soundslikemitch said:
Why do I have a mac
Click to expand...
Click to collapse
^^ now THAT is funny ^^
Magnesus said:
That was quick. I wonder if Amazon prefers the device to be rootable or not? Normal Kindle is quite easy to root too.
Click to expand...
Click to collapse
Supposedly it was supposed to be easy to root. So I would think so. I am sure amazon could have made it a lot harder if they wanted to.
aimbdd said:
Supposedly it was supposed to be easy to root. So I would think so. I am sure amazon could have made it a lot harder if they wanted to.
Click to expand...
Click to collapse
I almost suspect from their coy comments (yes, it will be rooted, no we don't care, type of thing) That they're just after market share, period. Now let's bring on CM ICS! (impatient optimist in me, sorry!)
My question is can anyone get TTS to work?
soundslikemitch said:
Why do I have a mac
Click to expand...
Click to collapse
I lawl'd
* * *
Amazon said they wouldn't get in the way of root.
wow, this was quick! i hope we get custom gingerbread and later on ICS roms quick
Rooted Fire
Death2All - Rooting instructions worked like a champ!
Thanks for posting.
Donation to Shortfuse OTW.
Kind regards
Worked Beautifully!
Success!
My Kindle Fire is rooted and happily working with ADB.
Now lets get some dev-action love going on here . Thanks.
Good work
hey so can we now get the Amazon VOD app on our android phones with this root? If So...How do we do it?
soundslikemitch said:
Why do I have a mac
Click to expand...
Click to collapse
You could do it manually using the zergRush exploit, SuperOneClick just makes it easier for Windows people.
zergRush exploit: http://forum.xda-developers.com/showthread.php?t=1296916
(Usage instructions are there, it's fairly simple - push the binary to device with adb, chmod binary and then execute binary. this gives temp root, push su and busybox binaries for perm root and install superuser.apk)
[This replaces the SuperOneClick part of the original post, you still need to do everything leading up to that (editing adb_usb.ini etc.) - some parts may be changed slightly for mac/linux e.g. I would assume you need to edit a different file than "android_winusb.inf"]
EDIT: Guide for getting ADB working on Mac: http://blog.actlocalmedia.com/2011/11/developing-on-kindle-fire.html (probably applicable to Linux too). Do this, then you can manually root via ADB and zergRush.
Did rooting break video on demand playback for anyone else? When i go to watch a prime instant video now the play buttons are greyed out, and my device is "no longer configured correctly to play Amazon videos.
death2all110 said:
<snip> To get adb going you must already have the sdk on your machine and used it. <snip>
Click to expand...
Click to collapse
Never used it, but I have it installed. I don't even know where to begin
mipakr said:
Never used it, but I have it installed. I don't even know where to begin
Click to expand...
Click to collapse
to get the adb_usb file to show up, you can go into the tools directory of the sdk, open a command prompt and run android update adb - thatll at least create the file, then you just edit it as the directions state.
abremel said:
Did rooting break video on demand playback for anyone else? When i go to watch a prime instant video now the play buttons are greyed out, and my device is "no longer configured correctly to play Amazon videos.
Click to expand...
Click to collapse
Ditto for me. I called customer service, they claim to be looking into it. Debating whether to do factory reset and see what happens.
Sent from my ADR6300 using xda premium
smtom said:
Ditto for me. I called customer service, they claim to be looking into it. Debating whether to do factory reset and see what happens.
Sent from my ADR6300 using xda premium
Click to expand...
Click to collapse
Actually an easy fix - the unroot button on superoneclick unroots it, and a reboot restores video playback - the instant video app must have some sort of check in place to see if the device is rooted.
abremel said:
to get the adb_usb file to show up, you can go into the tools directory of the sdk, open a command prompt and run android update adb - thatll at least create the file, then you just edit it as the directions state.
Click to expand...
Click to collapse
You also need to install the Google USB driver via the SDK Manager I think to generate the other files that need editing.
4.2.2 now enforces RSA authentication via ADB. This is only supported in later versions of ADB.
On Windows, you can see your local user profile folder's .android folder and see if there's a file called 'adbkey'.
Or use 'adb version' to see if you have the latest version. ADB version 1.0.31 is working.
Google just added this in the ADB protocol last November, so you need the NEWEST ADB:
https://github.com/android/platform_system_core/commit/d5fcafaf41f8ec90986c813f75ec78402096af2d
The keys for your hosts are stored at /data/misc/adb/adb_keys, I believe.
If your ADB works correctly, you will see this when you plug in for the first time. You may still have to reseat your cable.
{
"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"
}
(Pic credit to rickbosch)
* * *
This will not affect all of you.
But on the stock Android 4.2.2 kernel from Google, I cannot get adb to work (always shows 'adb offline') on the stock kernel. This is with my laptop (a Lenovo Thinkpad), and I never had issues with this before with the same setup.
My current workaround is to use a custom kernel for 4.2.2 (thanks to renaud for delivering)
A custom Fugumod kernel that works with 4.2.2 and does not have this issue with ADB:
http://forum.xda-developers.com/showpost.php?p=37892325&postcount=2167
Stable builds (future?):
http://fugumod.org/galaxy_nexus/stable-4.2.2/
Please report back with the PC/Mac and possibly the cable you are using, thanks.
In default.prop is new line!
That is ro.adb.secure=1 or something like that, I think this is the issue! changing it to 0 may let you to use ADB!
I gonna test it out in 5 minutes.
It'll ask you to give ADB permission if you're all set up correctly. Mine did...Seems it's a whitelist system now where you can allow or not allow individual PCs to use ADB on your device.
manumanfred said:
In default.prop is new line!
That is ro.adb.secure=1 or something like that, I think this is the issue! changing it to 0 may let you to use ADB!
I gonna test it out in 5 minutes.
Click to expand...
Click to collapse
That's default.
I resolved my issue swapping my kernel, not the ramdisk (that's where default.prop is in anyway). Hm...
rickbosch said:
It'll ask you to give ADB permission if you're all set up correctly. Mine did...Seems it's a whitelist system now where you can allow or not allow individual PCs to use ADB on your device.
Click to expand...
Click to collapse
This never came up for me . Didn't wipe though.
How do you manage devices?
I'm using 4.2.2 and I didn't got that popup!
I extracted boot.img and made it to insecure and changed adb secure line from 1 to 0 and now I can use ADB!
neither did I. Just flashed via TWRP over stock Takju 4.2.1
edit: And about managing devices, I have no idea.
You shouldn't have to make ro.adb.secure=0 default. I think something is definitely wrong with this OTA lol.
Or maybe this is a new feature. Was the screenshot taken with Linux? How the heck do I get a RSA key with ADB on Windows?
xaueious said:
Or maybe this is a new feature. Was the screenshot taken with Linux? How the heck do I get a RSA key with ADB on Windows?
Click to expand...
Click to collapse
Screenshot was taken on my phone, and about RSA key and ADB on Windows, I'm afraid I can't answer those for you.
xaueious said:
You shouldn't have to make ro.adb.secure=0 default. I think something is definitely wrong with this OTA lol.
Or maybe this is a new feature. Was the screenshot taken with Linux? How the heck do I get a RSA key with ADB on Windows?
Click to expand...
Click to collapse
Why not!
It lets to use ADB then, now I can use ADB without any issues, before editing default.prop I wasn't able to use ADB!
This is probably a new feature of some sort. Linux works fine, Windows doesn't. Mac probably works too.
Windows works fine for me. Maybe you changed something somewhere. I had 0 problems.
Never changed anything on the phone. Fixed the issue though. I was using an older version of ADB: 1.0.31
Older versions don't support key RSA authentication.
I also had this problem.
Then I deleted some spare copy of adb.exe and its dlls that where installed under \windows\ by some "do-it-all" tool and updated the adb tools with SDK-Manager.
After connecting to the PC, my GNexus asked for confirmation before allowing USB debugging and since then everything is fine :victory:
I updated android sdk tools on my mac today (before that I couldn't launch abd sideload update.zip) and haven't noticed any issues with adb/fastboot commands.
AH, so it's the outdated ADB drivers playing up, perhaps good to mention in OP as a solution.
For me with stock kernel adb and fastboot ok.
I'm using bigxie rom deodex.
rickbosch said:
AH, so it's the outdated ADB drivers playing up, perhaps good to mention in OP as a solution.
Click to expand...
Click to collapse
Done
It may seem obvious for some, but wasn't for me.
I flashed the upgrade, with the cable always connected then couldn't get adb to work. Just need to re-plug the cable for the prompt to show up
Is this new version in the latest Android SDK? If not, where can you get it from?
EddyOS said:
Is this new version in the latest Android SDK? If not, where can you get it from?
Click to expand...
Click to collapse
Yes, it is in the new SDK.
On a side note, OP, the image you used and credited in the first post was mine, not manumanfred's.
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.