using osx to unlock bootloader??? - Nexus 6 Q&A, Help & Troubleshooting

first, i have already unlocked my bootloader using windblowz on a boot camp partition of my mac. BUT, since android is a unix-like os, and osx is a unix-like os, FOR MY OWN EDUCATION, i want to be able to use the osx terminal to do this stuff to my n6.
so here's what i tried, and none of it works... as in, none of it even results in any like link between my phone and my osx computer.
1) i watched this youtube video from droidmodderX, and followed it to the letter:
https://www.youtube.com/watch?v=aUkcWlknFsE
from the time he plugs his n6 into his mac, NOTHING he says will happen, actually happened. it was as if i had plugged the phone into nothing. He says NOTHING about installing the android SDK for osx in his video. sooo....
2) next, i install the android SDK for osx, thinking droidmodderX was just careless in his video, and forgot to mention that you need to do this. NOTHING. i open the terminal and run the various fastboot commands from the root directory... NOTHING. using the terminal, i change over to the directory where i actually put the SDK, and then run the fastboot/adb commands from terminal again, and NOTHING. I tried this with the phone in fastboot, and with the phone not in fastboot, and NOTHING.
so how do you get osx to talk to this phone with fastboot/adb commands using the terminal?
fwiw, android file transfer works fine in the gui, so i know the physical connecction is good.
also, fwiw, i did use the search function and someone asked a similar question about his n5 about a year ago... and got no answer. not a single one.
-peter

If you run "./adb devices" without quotes does it see the phone at all? Make sure you have the most up to date SDK for OS X and also make sure you update the platform-tools in the SDK manager.
Check this thread out, might help a bit.
EDIT: Try running the commands as root/sudo.

I used this method on my MacBook Air to root my device without any issues. Make sure that you are in the correct folder when executing the commands. The first time it should ask you for your password. Also make sure that you have USB debugging enabled on your phone and that you are in the bootloader. You can also try to download Android File Transfer (google it) and see if it works with your phone. Hope that this helps.

You're aware that the bootloader on the Nexus 6 can be unlocked simply by toggling "Enable OEM Unlock" under Developer Settings, right?
With that said, I agree that it is smart to keep up with proper ADB/Fastboot commands as those are the most sure fire way to get you out of a pinch.
I have had absolutely no issues using Terminal to perform Fastboot commands on my Nexus 6 using my Mac with OSX Yosemite. As long as you get it setup correctly you should have no issues.
I just dug up the detailed instructions I used to get my Mac setup for this. Start from scratch, follow these instructions and you should be good to go:
http://forum.xda-developers.com/showthread.php?t=1917237

geebee1932 said:
I used this method on my MacBook Air to root my device without any issues.
Click to expand...
Click to collapse
what method? can you be more specific? did you mean to put in a link describing the "method"?
geebee1932 said:
Make sure that you are in the correct folder when executing the commands.
Click to expand...
Click to collapse
I ran all the fastboot commands, to the letter, from the youtube video, from the terminal, in the folder where i had the SDK. nothing....
geebee1932 said:
The first time it should ask you for your password.
Click to expand...
Click to collapse
It didn't.
geebee1932 said:
Also make sure that you have USB debugging enabled on your phone and that you are in the bootloader.
Click to expand...
Click to collapse
I did.
geebee1932 said:
You can also try to download Android File Transfer (google it) and see if it works with your phone. Hope that this helps.
Click to expand...
Click to collapse
As I said in my original post, I already have Android File Transfer, no need to google it. It works great. Had it for years.
I made some headway when I started using ./adb before each command. It sees my device now and when i ran ./adb help, it put out a list of commands and switches in the terminal, that I'm starting to play with. thanks for the ./adb clue. that was a biggie now using ./adb i can reboot and boot into bootloader. but for example "./adb fastboot oem lock", (without the quotes), does nothing. (i used "oem lock" as a test, because the bootloader is already unlocked)
-peter

geebee1932 said:
I just dug up the detailed instructions I used to get my Mac setup for this. Start from scratch, follow these instructions and you should be good to go:
http://forum.xda-developers.com/showthread.php?t=1917237
Click to expand...
Click to collapse
thanks mate. that's the second reference to that link. it must be good
and geebee, sorry i sounded so douchey. i know you're trying to help. i was frustrated.
-peter

pcrussell50 said:
thanks mate. that's the second reference to that link. it must be good
and geebee, sorry i sounded so douchey. i know you're trying to help. i was frustrated.
-peter
Click to expand...
Click to collapse
No worries at all - I was frustrated myself until I found the YouTube video. I think after ./ you need a space before you use the command line. What I did was put the CF auto-root folder (unzipped) on my desktop. I renamed the folder CF to make it easy. I opened the folder and doubled clicked on the Mac file. It should open and say just press enter - it will not work. Keep the folder open and open up the terminal. Here is what I had to do.
Put the phone is download mode with "Start" appearing - then plug into computer. (make sure debugging on)
cd /Users/mycomputername/desktop/CF - I needed a space after cd
paste and copy the 3 sudo commands (with the sudo) out of the CF folder one at a time - pressing enter after each.
The first enter - you should be asked for your password.
Mike

Going well now guys thanks. I like having two unix-like devices (osx computer and android handset), talking without needing drivers.
-peter

sn0warmy said:
You're aware that the bootloader on the Nexus 6 can be unlocked simply by toggling "Enable OEM Unlock" under Developer Settings, right?
With that said, I agree that it is smart to keep up with proper ADB/Fastboot commands as those are the most sure fire way to get you out of a pinch.
I have had absolutely no issues using Terminal to perform Fastboot commands on my Nexus 6 using my Mac with OSX Yosemite. As long as you get it setup correctly you should have no issues.
I just dug up the detailed instructions I used to get my Mac setup for this. Start from scratch, follow these instructions and you should be good to go:
http://forum.xda-developers.com/showthread.php?t=1917237
Click to expand...
Click to collapse
Hello everyone,
I'm in the same boat, except my device won't show up under devices in transmission after the "./adb devices" command.
Got a Nexus 6, 2009 Macbook running OSX Mavericks. I followed http://forum.xda-developers.com/showthread.php?t=1917237 to a T, but no luck. Android File Transfer works just fine. Usb debugging and oem unlock is checked on my phone, I restarted both phone and computer. Any advice/guidance/direction would be greatly appreciated, thanks!

Related

ADB HELP

I have tried every process I can find in the forum regarding rooting and ADB but I cannot seem to figure this out. I would like to think that I am computer literate and that I know my way around pretty well but somehow this escapes me. I am running Windows 7 64 bit and can't seem to get anything right as far as this process goes.
Is there a rooting/adb for dummies section that someone can point me to?
the sticky wiki for guides at the top of the front page....
try to look around a little before starting new threads.
beyondinferno said:
the sticky wiki for guides at the top of the front page....
try to look around a little before starting new threads.
Click to expand...
Click to collapse
Thanks for your help...I did look around but I still can't get it to work. I've been through quite a few threads. I don't know if I'm missing something somewhere or what.
is your problem your computer not seeing the phone?
i RUU'd my phone earlier today to test out something i did, but then i found out that adb couldn't connect anymore. i'm still trying to figure it out.
Exactly what are ya having problems with?
http://forum.xda-developers.com/showthread.php?t=502010
1. HTC Sync installed?
2. Android SDK downloaded?
3. Debugging enabled on the phone?
4. is ADB showing up in the Device manager?
5. Check this thread out dealing with x64 drivers
http://forum.xda-developers.com/showthread.php?t=560962
Hmmm..
I have Win7 64bit too
I think I just downloaded the newest Android SDK and HtcSync for the Eris. It
works fine for me. What exactly is the issue? You have the phone in debug mode or whatever mode right?
some folks have used PdaNet
http://www.junefabrics.com/android/download.php
first off, I can't get Sync to work at all no matter which version I've tried. Then the drivers won't load for sdk. it just seems like nothing is working together at all.
alright, i figured it out.
uninstall HTC Sync and the HTC Drivers.
reinstall.
done.
justinisyoung said:
alright, i figured it out.
uninstall HTC Sync and the HTC Drivers.
reinstall.
done.
Click to expand...
Click to collapse
yeah just make sure you use the newest HTC Sync for the Eris!
just out of curiosity why the eris? am i going to have issues later down the road?
DanWalker said:
I have tried every process I can find in the forum regarding rooting and ADB but I cannot seem to figure this out. I would like to think that I am computer literate and that I know my way around pretty well but somehow this escapes me. I am running Windows 7 64 bit and can't seem to get anything right as far as this process goes.
Is there a rooting/adb for dummies section that someone can point me to?
Click to expand...
Click to collapse
Alright... what's your main problem? Are you not able to get the ADB driver to work with your phone in Windows 7 64 bit -- if so, do know that it is possible, because I have it working fine on my computer (Win 7 64B).
If ADB driver situation is your problem, do as follows:
1. Download the file below (to desktop for easy access - This is the Vista 64 bit Drivers)
2. Unzip
3. Go to Device Manager
4. Find ADB (It should come up as ADB with a Yellow Exclamation mark next to it)
5. Right click on it, choose update driver
6. When it asks you to auto find the driver or browse for the driver -- choose BROWSE.
7. Set the path to where you downloaded the file, and then click next.
8. If done correctly, you should see a window pop up that says "Successfully installed My HTC driver".
ADB will work after that is complete. To test, open CMD - go to androidsdk\tools folder, and then run adb devices (If serial # appears, there you have it).
Also with the method above, this will allow the HTC Sync application to work as well.
Source: ME, tested extensively and more than once.
DanWalker said:
just out of curiosity why the eris? am i going to have issues later down the road?
Click to expand...
Click to collapse
HTC Sync for the Hero was released before Win7, so the Vista drivers will work but you have to jump through some hoops.
Now the Eris version is the same HTC Sync but it has drivers for Windows 7, it is the same software but is bundled with newer drivers.
Roger that guys, thanks for the help. I will attempt tonight when I get back to my computer.
Ok just got home and am doing the suggested things, after installing the SDK it wants me to install packages and when I choose cancel, windows says the program was not installed correctly. what do i need to install?!
Also no ADB in device manager!
yeah they took out the packages of the SDK, so you have to add them in as needed.
I have a 2nd Win7 box that's an Android virgin, I will try and run through the install tonight(off at 5pm PST)when I get home and I'll document the install.
hang in there.
rlaxton said:
yeah they took out the packages of the SDK, so you have to add them in as needed.
I have a 2nd Win7 box that's an Android virgin, I will try and run through the install tonight(off at 5pm PST)when I get home and I'll document the install.
hang in there.
Click to expand...
Click to collapse
That would be awesome, I'm at the point where I am just about to give up. I have never been so frustrated with a computer. This is the first Windows 7 system I have done anything with and I already don't like it.
DanWalker said:
Ok just got home and am doing the suggested things, after installing the SDK it wants me to install packages and when I choose cancel, windows says the program was not installed correctly. what do i need to install?!
Also no ADB in device manager!
Click to expand...
Click to collapse
Install packages? What? Weird, the Android SDK is natively 32 bit, but will work in Windows 7 64 BIT (That's what I'm running now).
Alright, steps to take:
1. Uninstall/remove everything you did before.
2. Grab the Windows Android SDK -- download it (to the desktop is fine)
3. UNZIP/Extract the SDK
4. Drag the Android SDK to the root of your drive (Local Disk C: )
5. For easy access purposes, RENAME the Android SDK from what you see to something like: androidsdk
6. Open Command Prompt
7. Verify that you can get to the "androidsdk" directory by running the command: cd androidsdk\tools
8. If you can get there -- then good, so far.
9. Now to test "adb" -- Have your phone connected to the PC.
10. While still in command prompt and STILL in the c:\androidsdk\tools: dir... run command: adb devices
11. This should return your Serial #
12. If your serial # shows up, then make sure you can run the command adb shell and see if you get the # sign, which indicates that you are rooted -- If not, then you need to begin the process of rooting your phone.
Also, if ADB doesn't work after this point, do what I told you earlier, I can guarantee that it does work, because I actually did it this morning on my work computer (Which is Windows 7 64 Bit).
Good luck, report back.
Holy crap it looks like it worked!! Thanks Pseudo! Now if I could only get my damn phone to find Sync I'd be all set.
Still can't get sync to register with phone but that's no biggie. But have a small issue that I dunno where to look to find an answer. I'm trying to update my recovery from 1.5.2 to 1.6.2 and can't seem to follow the directions appropriately.
via adb -> Requires a custom recovery (with test-keys)
Code:
Copy recovery-RA-heroc-v1.6.2.img to the root of your sdcard
Boot into your current custom recovery (boot while holding HOME)
Connect your Hero via usb to your pc/mac/...
adb shell
$su (not required if you have root already)
#mount -a
#flash_image recovery /sdcard/recovery-RA-heroc-v1.6.2.img
None of that seems to work lol.
So since we're on the subject does anyone know how to set up the drivers for linux mint kde? I'm brand new to linux and I've managed to do some things but that is just one thing that i cant do so far and after almost a day pf searching this forum and others i just cant seem to get it
DanWalker said:
Holy crap it looks like it worked!! Thanks Pseudo! Now if I could only get my damn phone to find Sync I'd be all set.
Still can't get sync to register with phone but that's no biggie. But have a small issue that I dunno where to look to find an answer.
Click to expand...
Click to collapse
First off, no problem for the help -- glad it worked. What ROM are you currently running, that would be helpful in solving your sync issue.
DanWalker said:
I'm trying to update my recovery from 1.5.2 to 1.6.2 and can't seem to follow the directions appropriately.
Click to expand...
Click to collapse
Alright, lets begin - To upgrade to RA 1.6.2, (You have to be in recovery mode (Home + Power) -- and also have your phone connected to the PC). Then do as follows:
1. Download the 1.6.2 file
2. Copy or move it to your androidsdk\tools folder
3. Run commands below:
Code:
adb push recovery-RA-heroc-v1.6.2.img /sdcard
Code:
C:\AndroidSDK\tools>adb shell
Code:
mount -a
You'll probably get the next line below -- that's okay.
Code:
mount: mounting /dev/block/mmcblk0p2 on /system/sd failed: No such file or directory
Keep going...
Code:
flash_image recovery /sdcard/recovery-RA-heroc-v1.6.2.img
After you do this, the shell should return #, if it does, then run:
Code:
reboot recovery
Now verify that your recovery says 1.6.2.
Good luck.
thatguythatdid said:
So since we're on the subject does anyone know how to set up the drivers for linux mint kde? I'm brand new to linux and I've managed to do some things but that is just one thing that i cant do so far and after almost a day pf searching this forum and others i just cant seem to get it
Click to expand...
Click to collapse
Well, since you've asked a good question, I shall direct you in the right direction. Linux Mint is a derivative of Ubuntu, so this guide should work for you., however do note that I have not tested this in Linux Mint, as I currently run Ubuntu 9.10, but you should be okay.
Go HERE and bookmark this page for reference, it has some good stuff -- Now this guide is not directly for our phones (CDMA HERO), however the directions, if followed correctly... DO WORK and have been tested by me (did this last night) with successful results.
When you get to the web page, start at "Generic Linux Instructions". Also, when you get to the heading "Set up ubuntu to recognize your phone, and the adb/fastboot commands in the terminal" -- step 4 will ask you to create an empty file, use the Ubuntu 9.10 format and NOT the older versions, again this format should work in the latest version of Linux Mint.
Hope that helps. Also, if have problems or want a step by step tutorial (pending how "new" to Linux you are), just ask me or PM me, I'll write one up.

[Q] Tons of Trouble with ADB and Fastboot

I'm having a crapload of trouble with adb and fastboot. I've been searching for the last few hours but to no avail. I've downloaded multiple drivers and tried to do everything i can to setup the adb and fastboot. I managed to get the bootloader unlocked and its rooted and usb debugging is enabled. Every time i type "adb devices" into a command prompt it says that adb is not a valid command etc. What the heck am i doing wrong and why is this supposedly simple process so difficult here?? Please help...
Did you use the "cd" command to change the directory to where the platform-tools folder is?
That's assuming you have the Android SDK and Java Dev Kit (JDK) installed already..
Sent from my Atrix HD via XDA-Developers application
pianoman102 said:
I'm having a crapload of trouble with adb and fastboot. I've been searching for the last few hours but to no avail. I've downloaded multiple drivers and tried to do everything i can to setup the adb and fastboot. I managed to get the bootloader unlocked and its rooted and usb debugging is enabled. Every time i type "adb devices" into a command prompt it says that adb is not a valid command etc. What the heck am i doing wrong and why is this supposedly simple process so difficult here?? Please help...
Click to expand...
Click to collapse
Here is installer. Run it under administration mode on windows.
No needs to install the whole android SDK anymore. Enjoy!!
http://d-h.st/FFo
P/s: U still need JDK as Byakko Custom said.
devilsking said:
Here is installer. Run it under administration mode on windows.
No needs to install the whole android SDK anymore. Enjoy!!
http://d-h.st/FFo
P/s: U still need JDK as Byakko Custom said.
Click to expand...
Click to collapse
Ah, thanks so much! That finally got it working after i installed jdk and ran the program. Awesome! time to start flashing!
pianoman102 said:
Ah, thanks so much! That finally got it working after i installed jdk and ran the program. Awesome! time to start flashing!
Click to expand...
Click to collapse
U're welcome
devilsking said:
Here is installer. Run it under administration mode on windows.
No needs to install the whole android SDK anymore. Enjoy!!
http://d-h.st/FFo
P/s: U still need JDK as Byakko Custom said.
Click to expand...
Click to collapse
2 Questions
Does that install the tools in the Windows equivalent of "$PATH" so users don't have to cd to the tools' location.
And do you mind if I link to this in my how-to guide? Credit will be given to you and your team of course.
skeevydude said:
2 Questions
Does that install the tools in the Windows equivalent of "$PATH" so users don't have to cd to the tools' location.
And do you mind if I link to this in my how-to guide? Credit will be given to you and your team of course.
Click to expand...
Click to collapse
Yep. U can do it I'm happy to share this tools with other users :good:
About the location, I set the installation path to C:\Windows so it means that it can be used as an windows services whenever u call it on cmd. No needs to set the location.
For example: If users use command "adb devices", it will work immediately and show the result. However when they want to decompile an apk and put file in a folder named "X", it's needed to use cd command to set the location in cmd to "X" then use adb/apktool/fastboot as normal without having adb/apktool/fastboot files in "X" folder. It helps to define the location of apk file, not the apktool/adb/fastboot.
Hope u can understand my idea =.= Sometimes, my explanation is really not good becoz English is not my mother language
devilsking said:
Yep. U can do it I'm happy to share this tools with other users :good:
About the location, I set the installation path to C:\Windows so it means that it can be used as an windows services whenever u call it on cmd. No needs to set the location.
For example: If users use command "adb devices", it will work immediately and show the result. However when they want to decompile an apk and put file in a folder named "X", it's needed to use cd command to set the location in cmd to "X" then use adb/apktool/fastboot as normal without having adb/apktool/fastboot files in "X" folder. It helps to define the location of apk file, not the apktool/adb/fastboot.
Hope u can understand my idea =.= Sometimes, my explanation is really not good becoz English is not my mother language
Click to expand...
Click to collapse
Thanks.
That's what I thought it did. I was going to do something similar, but I couldn't remember if the correct folder was and I was just too lazy to do the research and find out. I was thinking System32, but its been so long that I couldn't remember.

[Q] Total Newb, Question about Soft Brick

EDIT: Many apologies, I now see this belongs in a different thread, specifically the "7" Kindle Fire HD Q&A, Help & Troubleshooting" one... very sorry. I don't know how to move/delete this, and I don't want to repost it there without deleting this one, because double posting = bad. I don't know how to ask a mod to do it, if you can. Sorry for not knowing the forums. Many apologies.
So I'm pretty sure I Soft Bricked my Kindle Fire HD 7". I'm not too mad, but I would like to try and fix it. To be exact, it redscreens on boot.
I was attempting to install TWRP and was at the last few steps when I did it, which seemed like the ones that would brick it. From all my looking around based off what was going on and the log I have from the command prompt.
These where the last steps I took before the problem. pastebin.com/BqGGKziP
My questions are:
Is this a soft brick?
Is it fixable?
If so, any ideas?
I already know if this is fixable to expect to be told I need a developer cable, but please tell me anyways if I do.
EDIT: If I do need one, which I assume I do, where can I get one? Sorry for being a newb, I knew I would probably brick my device, but I really don't know too much about these things and would like to make sure I am getting the right thing.
I apologize for being new and not knowing my way around this forum, and if this is the right place exactly to post this, as well as if I accidentally broke any rules. I'd simply like to know if anyone who knows much could help. Again this isn't a big deal to me, but I would like to get it at least back to it's original state. I will do my best to provide any information asked for.
TecmagDiams said:
So I'm pretty sure I Soft Bricked my Kindle Fire HD 7". I'm not too mad, but I would like to try and fix it. To be exact, it redscreens on boot.
Click to expand...
Click to collapse
Get a tip for your USB cord here to http://shop.teamblackhat.info/Factory-Adapters-motadapt.htm otherwise get a fastboot cord from ebay.
Download the SDK package https://developer.android.com/sdk/index.html
Take take your SDK file and look for the folder that has the ADB.exe in it. I think this is the tools folder. Now open it and stick the drivers stunts has in that folder. Drivers here http://forum.xda-developers.com/showthread.php?t=2477379
Now go install that driver for the Kindle in the device manager. Remember that where ever you CD from, that USB driver has to be in that folder as well. Now open that folder with the drivers in it again and stick the stock Amazon images needed in it (get from restore tool if want or Hascode has some in his OP for this) and hold shift and right click on "open command window here." Now you are in CD cmd. You can probably just as easy CD from inside the system restore tool as well (unzip it.)
With your tablet in fastboot, open a command window and type "fastboot devices" with no quotes and you should be able to see a number and your device. This is good and means there is communications. if not then you need to install the proper drivers.
You need three files. boot.img, recover.img and system.img get them from here http://forum.xda-developers.com/showthread.php?t=2128848
issue these commands
fastboot -i 0x1949 flash boot "your boot image name here."
fastboot -i 0x1949 flash recovery "your recovery image name here."
fastboot -i 0x1949 flash system "your system image name here"
Make sure you end the commands with .img
Wait a little bit for it finish
fastboot -i 0x1949 reboot
Your bootloader crashed and that's why the red screen. You forgot to tick the the option to flash Amazon OS 7.2.3. always works better to downgrade to 7.2.3 first (for 7" KFHD)
Thanks a ton, and sorry for posting this in the wrong spot, I did find how to report it for a move.
I will hold onto this information and get myself the cable, try it out, and see where things go. Again, thanks for helping someone who hasn't a clue. ^.^
TecmagDiams said:
Thanks a ton, and sorry for posting this in the wrong spot, I did find how to report it for a move.
I will hold onto this information and get myself the cable, try it out, and see where things go. Again, thanks for helping someone who hasn't a clue. ^.^
Click to expand...
Click to collapse
No worries. If you get hung up, hit "reply" under the post above and respond. That way it goes to my email. Good luck and don't get overwhelmed.
So I recently got the head piece from the store you linked me to, and I have been attempting to follow your steps, but I am having trouble at one I thought would be fairly straightforward. Installing the drivers.
My device manager shows no device to update the drivers for. I'm sure I'm just not knowing something really simple, but I'm not sure how to install the drivers you showed me without having the device to update in the Device Manager.
Additionally I would just like to ask that once I have the drivers installed, how do I get the device into fastboot? Is it just running a line of "fastboot -i 0x1949 getvar product" and then plugging it in?
Thanks again for all the help.
TecmagDiams said:
So I recently got the head piece from the store you linked me to, and I have been attempting to follow your steps, but I am having trouble at one I thought would be fairly straightforward. Installing the drivers.
My device manager shows no device to update the drivers for. I'm sure I'm just not knowing something really simple, but I'm not sure how to install the drivers you showed me without having the device to update in the Device Manager.
Click to expand...
Click to collapse
Try these drivers http://forum.xda-developers.com/showthread.php?t=2477379 Update them through device drives.
Make sure you have the SDK package downloaded and the paths set. watch this video for a great tutorial https://www.youtube.com/watch?v=oaNM-lt_aHw
Are you using a Windows7 X64 or Windows 8? If you are, you need to disable driver enforcement as well. You will want to do this first.
Disable device driver signature enforcement -
Both must be done from the administrator profile to work right
Both of these are for Windows 7 X64 users.
Windows 7 X32 and earlier version users do not have this issue
A.
1. Reboot and on start up press F8 a couple times.
2. Scroll down to "Disable Driver Signature Enforcement."
Note: This must be done on every bootup you want to install something not MS signed.
B. For a more permanent solution.
1. First go and uninstall the driver (delete driver) you want to replace and then restart your computer.
2. Now go to the start menu and type cmd.
3. Right click on "cmd" and open a command prompt with elevated privileges (run as administrator.)
4. Now copy these in the command prompt one at a time hitting enter after each one.
bcdedit.exe -set TESTSIGNING ON
bcdedit.exe -set loadoptions DDISABLE_INTEGRITY_CHECKS
4. Now install the driver you want.
5. Restart the computer.
6. Profit.
Note: If you do this right, you will see "Test Mode Windows 7 Build 7601" (or something comparable) in the lower right corner of your screen. This means that drivers not signed by MS can be installed without getting the Windows has installed the best driver already bit.
If you opt to take your computer out of test mode, the drivers will more than likely be replaced by MS drivers next time. Following steps 1,2 and 3 in part B of tutorial copy these commands in the command prompt one at a time hitting enter after each one.
bcdedit.exe -set loadoptions ENABLE_INTEGRITY_CHECKS
bcdedit.exe -set TESTSIGNING OFF
bcdedit /set nointegritychecks ON
bcdedit /set nointegritychecks OFF
Possible Windows 8 cmd
bcdedit /set loadoptions DDISABLE_INTEGRITY_CHECKS
Since I don't have Windows 8 to do a personal tutorial, I'll just link to a good tutorial for that.
http://www.fotoclubinc.com/blog/how...on-of-windows-7-printer-drivers-on-windows-8/
Additionally I would just like to ask that once I have the drivers installed, how do I get the device into fastboot? Is it just running a line of "fastboot -i 0x1949 getvar product" and then plugging it in?
Click to expand...
Click to collapse
With the tablet powered completely down, plug the USB cord (with tip) into the USB port and also the tablet. The tablet should lit up and say fastboot. At this point, the tablet will stay energized and in fastboot.
Thanks again for all the help.
Click to expand...
Click to collapse
You're welcome
Click to expand...
Click to collapse
So I booted up with the driver security disabled, however I'm still having the problem that no where in the device manager can I find my device to update the drivers for.
I'm super sorry if I'm missing something obvious and simple, I just don't see what it is, and thusfar all my attempts have simply resulted in plugging in the usb to the tip and tip to the device and having absolutely zero reaction.
I am running Windows 7 (64bit) to answer that question, sorry I didn't think to say that before.
TecmagDiams said:
So I booted up with the driver security disabled, however I'm still having the problem that no where in the device manager can I find my device to update the drivers for.
I'm super sorry if I'm missing something obvious and simple, I just don't see what it is, and thusfar all my attempts have simply resulted in plugging in the usb to the tip and tip to the device and having absolutely zero reaction.
I am running Windows 7 (64bit) to answer that question, sorry I didn't think to say that before.
Click to expand...
Click to collapse
I just looked on your pastebin link. That is an incredibly old TWRP. The most recent one is 2.6.3.1
The reason you had the red screen is because you never flashed a bootloader. I see a boot.img and a recover.img
If you are getting no response at all, even with the fastboot tip on the USB cord, you could have a hard brick. If you can try another USB cord first to make sure. Maybe another port on your computer.
LinearEquation said:
I just looked on your pastebin link. That is an incredibly old TWRP. The most recent one is 2.6.3.1
The reason you had the red screen is because you never flashed a bootloader. I see a boot.img and a recover.img
If you are getting no response at all, even with the fastboot tip on the USB cord, you could have a hard brick. If you can try another USB cord first to make sure. Maybe another port on your computer.
Click to expand...
Click to collapse
Welp, as I said, I'm not too mad, and I knew going in that I would never be sure enough to know what I was doing.
From the seems it would be hard bricked then, because with the tip I get no response, I've tried all 3 of my cables, and all of my ports. Thanks for all the help though, it's very much appreciated. ^.^
TecmagDiams said:
Welp, as I said, I'm not too mad, and I knew going in that I would never be sure enough to know what I was doing.
From the seems it would be hard bricked then, because with the tip I get no response, I've tried all 3 of my cables, and all of my ports. Thanks for all the help though, it's very much appreciated. ^.^
Click to expand...
Click to collapse
Bummer. Maybe next time eh???
Sent from Nexus 7 flo running SinLess ROM 4.4.2 with ElementalX kernel using xda app-developers app

Trying to do a backup but adb pull isn't working

Hi all
So I'm doing step 1 of this guide but I seem to be having problems..
I did install the ADB drivers on my comp, installed SDK, and set the directories in PATH. ADB is turned on in the Kindle. But when I try to do the backup commands, I get a "remote object xxxxxxxxxxx does not exist"
Anyone have any idea what's going on here? I appreciate your help!
Any ideas?
I think you're on the wrong partition...
Rushead said:
I think you're on the wrong partition...
Click to expand...
Click to collapse
What do you mean? Sorry, I'm total noob with adb in general (and I just got the Kindle like a couple weeks ago )
I should add that when I do the first command the Kindle responds to it (as in the screen turns on when I send the command). Don't know if that helps you.
You need to pull from the correct directory. I think that's your only problem.
Thanks for your response.
How do I pull from the right directory? I'm using the code from the thread that's apparently supposed to work for everyone, don't know what's going wrong on my end :s
Are you rooted? Did you allow adb on the Kindle? Are you running as administrator in windows?
Rushead said:
Are you rooted? Did you allow adb on the Kindle? Are you running as administrator in windows?
Click to expand...
Click to collapse
Yeah I'm rooted (I have root access on the phone but no superuser app ever popped up when I rooted), adb is on in the Kindle, and I am running cmd as admin. :s
Hovo said:
Yeah I'm rooted (I have root access on the phone but no superuser app ever popped up when I rooted), adb is on in the Kindle, and I am running cmd as admin. :s
Click to expand...
Click to collapse
You can't run cmd as an Admin. You have to actually be using the Admin profile on your PC.
I'm on the admin account on my computer as well. Typing "adb devices" shows the device on the list, I don't understand why the backup code doesn't work.
Hovo said:
I'm on the admin account on my computer as well. Typing "adb devices" shows the device on the list, I don't understand why the backup code doesn't work.
Click to expand...
Click to collapse
The code works. It's just not finding your boot img.
Does your kindle boot normally?
Yep, I haven't installed the second bootloader yet because I wanted to backup the device first.
BTW, for what it's worth, the error happens with all 4 items the code is meant to backup; the system, recovery, bootloader and bootblock.
It sounds like adb is not enabled, though you said it is. Have you tried a factory reset?
Decided to give it another go this morning, and I feel so silly...
The adb shell was asking for root access this entire time, I never saw it until now though...
Thanks for all your help and sorry for makin you run around in circles. :s

Root on Mac?

Anyway to root the Fire on a Mac? I see the Windows tool but nothing for Mac...
Mac . . .
Do we have to help?
What FireOS version do you have? Did you avoid connecting to wifi?
There may not be a point n click rooting tool for macs but you can always do it manually.
It is new, never connected to internet. I have enabled ADB but fast boot does not see the device, Where do I need to get the drivers for the Fire at for Mac? I have FireSO 5.0.1
You can get drivers from google.
This also came up on google.
GUIDE Set up ADB and Fastboot on a Mac easily (With Screenshots!)
blueberry.sky said:
Mac . . .
Do we have to help?
What FireOS version do you have? Did you avoid connecting to wifi?
There may not be a point n click rooting tool for macs but you can always do it manually.
Click to expand...
Click to collapse
I'll port http://forum.xda-developers.com/amazon-fire/general/root-fire-5th-gen-autoroot-script-noob-t3276923 with your help. Try the .sh file and tell me the result.
Think these are up to date.
https://github.com/simmac/minimal_adb_fastboot
Support page
http://forum.xda-developers.com/android/general/adb-fastboot-binaries-os-x-inclusive-t2941205
blueberry.sky said:
You can get drivers from google.
This also came up on google.
GUIDE Set up ADB and Fastboot on a Mac easily (With Screenshots!)
Click to expand...
Click to collapse
Can use the long winded way from there with the sdk but the attached files are for older version of adb that wouldn't connect to my friend's Fire as it's a Lollipop based device.
glitch3yf0x said:
I'll port http://forum.xda-developers.com/amazon-fire/general/root-fire-5th-gen-autoroot-script-noob-t3276923 with your help. Try the .sh file and tell me the result.
Click to expand...
Click to collapse
i'll gladly help.
dustintinsley said:
i'll gladly help.
Click to expand...
Click to collapse
Sweet! I'm working to make this fully compatible with linux, windows, and Mac OS X by tonight plus a few last minute added features. I have no idea how to emulate Mac OS X so when the time comes would you mind telling me if the script runs properly?
glitch3yf0x said:
Sweet! I'm working to make this fully compatible with linux, windows, and Mac OS X by tonight plus a few last minute added features. I have no idea how to emulate Mac OS X so when the time comes would you mind telling me if the script runs properly?
Click to expand...
Click to collapse
Code:
/Users/dustintinsley/Downloads/Fire5/fire_root.sh: line 1: @echo: command not found
Plug in your device with a USB data cable.
/Users/dustintinsley/Downloads/Fire5/fire_root.sh: line 3: syntax error near unexpected token `('
/Users/dustintinsley/Downloads/Fire5/fire_root.sh: line 3: `echo Please enable ADB debuging in the developer options (Tap Serial Number in Device Options 20 tim's if it is hidden)
Dustins-MacBook-Air:~ dustintinsley$
dustintinsley said:
Code:
/Users/dustintinsley/Downloads/Fire5/fire_root.sh: line 1: @echo: command not found
Plug in your device with a USB data cable.
/Users/dustintinsley/Downloads/Fire5/fire_root.sh: line 3: syntax error near unexpected token `('
/Users/dustintinsley/Downloads/Fire5/fire_root.sh: line 3: `echo Please enable ADB debuging in the developer options (Tap Serial Number in Device Options 20 tim's if it is hidden)
Dustins-MacBook-Air:~ dustintinsley$
Click to expand...
Click to collapse
Those will be an easy fix. Dummy me forgot to remove those. I thought I did. Thanks!
glitch3yf0x said:
Those will be an easy fix. Dummy me forgot to remove those. I thought I did. Thanks!
Click to expand...
Click to collapse
Just let me know i will test again...
dustintinsley said:
Just let me know i will test again...
Click to expand...
Click to collapse
Alright. I need to get a hold of the ADB platform-tools for MAC. Is there a way you can install android SDK for me and use the SDK manager to download platform-tools (latest version)? Then go into the platform-tools and send me the fastboot and adb tool?
http://dl.google.com/android/android-sdk_r24.4.1-macosx.zip
glitch3yf0x said:
Alright. I need to get a hold of the ADB platform-tools for MAC. Is there a way you can install android SDK for me and use the SDK manager to download platform-tools (latest version)? Then go into the platform-tools and send me the fastboot and adb tool?
http://dl.google.com/android/android-sdk_r24.4.1-macosx.zip
Click to expand...
Click to collapse
I really need these files in the above post. They are the last step before final testing and release. If anyone can upload them, please do it.

Categories

Resources