Develop Bugs

Unlock NAND on MAC anyone?

tryin to get mac to adb to device, but cannot get it to work.
anyone have success? would like to test these nice roms out.
thanks

nitty917 said:
tryin to get mac to adb to device, but cannot get it to work.
anyone have success? would like to test these nice roms out.
thanks
Click to expand...
Click to collapse
I did it on my MBP. What problems are you having?

I did it on my macbook..

I also did it on my Mac. Like someone else said what specifically is the issue you're encountering?

there is a post in about using Terminal app from the market to do this and it works!

brianb7590 said:
I did it on my MBP. What problems are you having?
Click to expand...
Click to collapse
thanks, I cant get it to communicate in terminal,
i have no idea. i dloaded the sdk, dragged the adb from tools folder,
onto the terminal, it opens up all the adb commands but after that i cant type
nothing.

nitty917 said:
thanks, I cant get it to communicate in terminal,
i have no idea. i dloaded the sdk, dragged the adb from tools folder,
onto the terminal, it opens up all the adb commands but after that i cant type
nothing.
Click to expand...
Click to collapse
Don't drag it to the terminal.
I would navigate to the directory where you stored the SDK and go to the tools folder and run it that way or you search up how to set your PATH to include the tools folder.

nitty917 said:
tryin to get mac to adb to device, but cannot get it to work.
anyone have success? would like to test these nice roms out.
thanks
Click to expand...
Click to collapse
Like the others who have already replied, I also did it on my mac and was a complete noob. It was only through much trial, error, YouTube, and 3 other sites that I figured it out. Needless to say I'm now fluent in adb and would be happy to answer any questions you have since I was in exactly the same shoes as you last weekend. Below are the biggest things you need to know when you start:
1. When you plug the phone into your computer make sure you select "Charge Only." If you select "Use Phone as Disk Drive" you won't be able to write to the phone, only read. I ran in circles for a long time getting "Read-Only File System" errors and it was all due to having the phone mounted as drive.
2. Make sure you have USB Debugging turned on. After that, you should be able to communicate with the phone fine.
3. ADB - The instructions are nearly identical regardless of operating system but on a mac you need to add "./" (without the quotes) before adb commands. For example, lets say I have a file on my desktop called "Test_File.img" that I want to push to the root of the sdcard. On my Mac I would type "./adb push /Users/Bryan/Desktop/Test_File.img /sdcard/" (without the quotes of course) & (Bryan is my Username)
4. To avoid any issues make sure none of the folders or file names you are working with have spaces in the name.
Hopefully all this helps and does no lead to more confusion than when you started. Again, if there are any specific errors you are seeing post them here and either I or someone else would be happy to answer them.
Bryan

okolowicz said:
Like the others who have already replied, I also did it on my mac and was a complete noob. It was only through much trial, error, YouTube, and 3 other sites that I figured it out. Needless to say I'm now fluent in adb and would be happy to answer any questions you have since I was in exactly the same shoes as you last weekend. Below are the biggest things you need to know when you start:
1. When you plug the phone into your computer make sure you select "Charge Only." If you select "Use Phone as Disk Drive" you won't be able to write to the phone, only read. I ran in circles for a long time getting "Read-Only File System" errors and it was all due to having the phone mounted as drive.
2. Make sure you have USB Debugging turned on. After that, you should be able to communicate with the phone fine.
3. ADB - The instructions are nearly identical regardless of operating system but on a mac you need to add "./" (without the quotes) before adb commands. For example, lets say I have a file on my desktop called "Test_File.img" that I want to push to the root of the sdcard. On my Mac I would type "./adb push /Users/Bryan/Desktop/Test_File.img /sdcard/" (without the quotes of course) & (Bryan is my Username)
4. To avoid any issues make sure none of the folders or file names you are working with have spaces in the name.
Hopefully all this helps and does no lead to more confusion than when you started. Again, if there are any specific errors you are seeing post them here and either I or someone else would be happy to answer them.
Bryan
Click to expand...
Click to collapse
If you're going to be using adb on a regular basis, and want to avoid typing "./" before each command, you can add the android sdk tools path to your .bash_profile file in your home directory. Something along the lines of:
export PATH=${PATH}:/path_for_ur_sdk_folder_location/android-sdk-mac_86/tools

mocalve said:
If you're going to be using adb on a regular basis, and want to avoid typing "./" before each command, you can add the android sdk tools path to your .bash_profile file in your home directory. Something along the lines of:
export PATH=${PATH}:/path_for_ur_sdk_folder_location/android-sdk-mac_86/tools
Click to expand...
Click to collapse
That wont be saved. It goes away after every reboot.

Fixter said:
That wont be saved. It goes away after every reboot.
Click to expand...
Click to collapse
True, if you enter it from the command line. But if you add it to the .bash_profile file , it will stick... at least on my Mac Pro it does...

mocalve said:
True, if you enter it from the command line. But if you add it to the .bash_profile file , it will stick... at least on my Mac Pro it does...
Click to expand...
Click to collapse
If I add those entering nano .bash_profile and enter that command and the pressing Ctrl X and Yes it will stick?

Fixter said:
If I add those entering nano .bash_profile and enter that command and the pressing Ctrl X and Yes it will stick?
Click to expand...
Click to collapse
It should... although I use vi instead of nano. Regardless, after saving the .bash_profile, you'll have to fully exit the terminal application and restart for the path setting to take effect. After that, it'll be in effect every time you start terminal.

mocalve said:
It should... although I use vi instead of nano. Regardless, after saving the .bash_profile, you'll have to fully exit the terminal application and restart for the path setting to take effect. After that, it'll be in effect every time you start terminal.
Click to expand...
Click to collapse
Nano is way cleaner. And yeah. It got applied.

Unlocking Xoom on a Mac (edit - solved!)

Hey guys, while I'm not exactly new to rooting, it has been quite some time since I rooted my N1 (and that was the only time I've ever rooted anything. I'm now a little lost with the unlock/rooting process. At this point,:
*I have the latest SDK, and I've updated the Platform Tools and added the contents to the Tools folder
*I've connected via USB and I've done the volume-down-power-up combination and have the "Starting Fastboot protocol support" screen.
However, that's all I've been able to do, and I honestly don't know what I'm missing. I can't get the the commands in Terminal to communicate with the tablet. Any assistance that anyone could provide would be greatly appreciated.
THANKS!

You have the Motorola v4.9 USB charging drivers installed?

When you do "adb devices" in terminal, can you confirm the Xoom is recognized?
If it is, following the guide here on XDA should go swimmingly. If it isn't, something is wrong with your SDK installation.

Elysian893 said:
You have the Motorola v4.9 USB charging drivers installed?
Click to expand...
Click to collapse
Well I was looking for drivers initially, but then I read in the "how to unlock" thread that someone said drivers werent needed on a Mac. Plus I looked for Mac drivers and couldn't find any, just Windows.

bcgaynor82 said:
When you do "adb devices" in terminal, can you confirm the Xoom is recognized?
If it is, following the guide here on XDA should go swimmingly. If it isn't, something is wrong with your SDK installation.
Click to expand...
Click to collapse
Well I'm not sure I'm opening Terminal in the right location. Entering "adb devices" gives me "command not found.

Ah, Mac, I'm of no use to you then.

Well should anybody see this, I'm still trying to get this to work. I can now confirm that the xoom does not show up after entering "adb devices". Otherwise I think the SDK is set up properly...at least I think it is.

take the file you want to use (adb or fastboot) and drag/drop in to the terminal window. Then just finish typing the command.

tanman21 said:
take the file you want to use (adb or fastboot) and drag/drop in to the terminal window. Then just finish typing the command.
Click to expand...
Click to collapse
AH, FINALLY! See, I knew whatever the solution would be, it would be a simple one. Xoom unlocked! Now to move on to root! Thanks a LOT!

joeski27 said:
AH, FINALLY! See, I knew whatever the solution would be, it would be a simple one. Xoom unlocked! Now to move on to root! Thanks a LOT!
Click to expand...
Click to collapse
Set your path. Edit your .bash_profile and you can run commands from anywhere in the terminal. Example:
Code:
export PATH=$HOME/bin/android-sdk-mac_x86/tools:$HOME/bin/android-sdk-mac_x86/platform-tools:$PATH

tanman21 said:
take the file you want to use (adb or fastboot) and drag/drop in to the terminal window. Then just finish typing the command.
Click to expand...
Click to collapse
That makes me a little sad. People should know how to use a command line
Sent from my PC36100 using XDA Premium App

Rooting Sprint GNex on Mac?

Okay so I can't find a clear guide on how to root the Sprint Gnex on a Mac. I know it is simple but there is no clear guide on how to do so. I have searched on XDA and Googled it, Can someone please tell me how they rotted their's or if you know of an easy way to do so.
Thanks
Urge

Exact same as windows, except all of the commands are in Terminal instead of Command Prompt, and you put "./" before the commands.
Ex:
Code:
./adb devices
Here's the Mac ADB and Fastboot that I've used countless times attached. Unzip to your home folder and put any images or files you're gonna need for flashing in that folder. I'll assume you know how to navigate Terminal well enough to find the folder.

martonikaj said:
Exact same as windows, except all of the commands are in Terminal instead of Command Prompt, and you put "./" before the commands.
Ex:
Code:
./adb devices
Here's the Mac ADB and Fastboot that I've used countless times attached. Unzip to your home folder and put any images or files you're gonna need for flashing in that folder. I'll assume you know how to navigate Terminal well enough to find the folder.
Click to expand...
Click to collapse
I am trying to root my gs3 will this guide be along the same lines for my device and also how do I go about using the terminal to root it?

moderntech- said:
I am trying to root my gs3 will this guide be along the same lines for my device and also how do I go about using the terminal to root it?
Click to expand...
Click to collapse
What the hell? Why did you bump a thread that is like more than 5 months old?
Sent from my i9250

bk201doesntexist said:
What the hell? Why did you bump a thread that is like more than 5 months old?
Sent from my i9250
Click to expand...
Click to collapse
This thread has the closest information that I need to root, and instead of starting a new thread and potentially not having someone answer my question I am contacting you, the one that provided said information to pick your brain.

moderntech- said:
This thread has the closest information that I need to root, and instead of starting a new thread and potentially not having someone answer my question I am contacting you, the one that provided said information to pick your brain.
Click to expand...
Click to collapse
This is the Google Galaxy Nexus forums!
sent from my Google Galaxy Nexus

Stuck in recovery with no Rom

To make it short, I got downloaded a corrupted ROM (only one on the phone), and with no nandroid. Is there any other way to access my "sd" card on my phone to put another ROM in? Is flashing a stock img the only way to get it back to work without losing my pictures? Thanks..

If its recognized by the computer, just "adb push" the ROM file (and anything else you need) to your phone.

martonikaj said:
If its recognized by the computer, just "adb push" the ROM file (and anything else you need) to your phone.
Click to expand...
Click to collapse
This.
Problem sorted.

Thanks for the suggestion, but can you provide some commands to push this file through adb?

if you are not familiar with adb commands, use Android Commander. Saves alot of time.

I'm a bit more familiar with adb, it's just need the to be directed to the right path with the specific command to push a rom to my phone. Does anyone know?
i tried
adb push "filename"/sdcard/"filename" but it's not giving me any response.

Deekayy said:
I'm a bit more familiar with adb, it's just need the to be directed to the right path with the specific command to push a rom to my phone. Does anyone know?
i tried
adb push "filename"/sdcard/"filename" but it's not giving me any response.
Click to expand...
Click to collapse
Is your ROM file in the Android>Platform Tools folder?
adb push rom.zip /sdcard/
You need the extension (.zip) as well.
Edit: does adb devices indicate you're connected?

Deekayy said:
I'm a bit more familiar with adb, it's just need the to be directed to the right path with the specific command to push a rom to my phone. Does anyone know?
i tried
adb push "filename"/sdcard/"filename" but it's not giving me any response.
Click to expand...
Click to collapse
you just need:
Code:
adb push ROMname.zip /sdcard/
Assuming you put "ROMname.zip" in your platform-tools folder, or another folder you're running ADB out of.

Keep in mind, not any response, aka, just hanging, means it is still working. ADB transfers are slow, so big files will take a little bit.

Nevermind.

martonikaj said:
you just need:
Code:
adb push ROMname.zip /sdcard/
Assuming you put "ROMname.zip" in your platform-tools folder, or another folder you're running ADB out of.
Click to expand...
Click to collapse
Yes I did that, and now for some reason my sdk is not recognizing my phone (funny cause i tried flashing a new recovery.img). Now i'm re-installing sdk tools.
adrynalyne said:
Keep in mind, not any response, aka, just hanging, means it is still working. ADB transfers are slow, so big files will take a little bit.
Click to expand...
Click to collapse
Thanks, gotta fix the first problem though.

error:Cannot load Unlock_code.bin NO solutions????

This is bothering me alot, bought an HTC10 thats with o2 and i cant get the final step to work.
I have received the email twice in as a many attempts,used Chrome and IE to download the unlock code. I placed the unlock code in the same folder as fastboot adb and the other adb
all drivers were installed,including the Android studio one thats 1.6gb along htcsync. When i type in adb devices my device sn comes up
Not sure what to make of this, i looked over the web their issues were that they either had a typo or missplaced the code ,is there really no solution for me?

I only saw this once before when I accidentally renamed the unlock file unlock_code.bin.bin. can we see the properties of the unlock_code.bin? Also I couldn't see from the picture if you had run the command prompt as admin?

Cat_On_Droid said:
This is bothering me alot, bought an HTC10 thats with o2 and i cant get the final step to work.
I have received the email twice in as a many attempts,used Chrome and IE to download the unlock code. I placed the unlock code in the same folder as fastboot adb and the other adb
all drivers were installed,including the Android studio one thats 1.6gb along htcsync. When i type in adb devices my device sn comes up
Not sure what to make of this, i looked over the web their issues were that they either had a typo or missplaced the code ,is there really no solution for me?
Click to expand...
Click to collapse
Why don't u uninstall HTC sync and try again.

In folder options for Windows turn on the option to see all file extensions and make sure its labeled "Unlock_code.bin". Also just Shift+Right Click in that folder so you have a Command Prompt that's already loaded in there so all you have to do is type the fastboot commands and not the entire directory. (makes life a little easier)

Tachi91 said:
In folder options for Windows turn on the option to see all file extensions and make sure its labeled "Unlock_code.bin". Also just Shift+Right Click in that folder so you have a Command Prompt that's already loaded in there so all you have to do is type the fastboot commands and not the entire directory. (makes life a little easier)
Click to expand...
Click to collapse
it is a bin file, the pic provided just cuts before it says its a bin file. �ts labaled exactly as in attachment
i updated to latest OTA , enabled USB debugging and still same problem :crying::crying::crying::crying:
attached the Unlock_code for refference

Try just dragging the .bin file onto the command window and then pressing "Enter." This gets rid of any possible path or name issues.

rwallhtc said:
I only saw this once before when I accidentally renamed the unlock file unlock_code.bin.bin. can we see the properties of the unlock_code.bin? Also I couldn't see from the picture if you had run the command prompt as admin?
Click to expand...
Click to collapse
Solved !
You need to run cmd as admin, simple as that haha
Question , OTA updates with unlocked bootloader+root will work or no?

Cat_On_Droid said:
Solved !
You need to run cmd as admin, simple as that haha
Question , OTA updates with unlocked bootloader+root will work or no?
Click to expand...
Click to collapse
Look into Magisk.
http://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445