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.

cannot for the love of all thats holy get adb to work

ive tried everything i read in most of these forums, and i know im missing something so stupid, so feel free to point out the obvious. but i cannot or have not ever been able to issue a command using adb.exe ive adjusted path name to were my android sdk is located. i know that the adbexe. in the tools folder itself doesnt open but i cant seem to get it working from command prompt either. im rooted and i thought i was nand unlocked until i tried recently to flash fresh's latest rom. (hboot 0.79.0000.) im currently running fresh.3 and would like to update. currently i have clockworks recovery running in rom manger because everytime i use ra amons i cant get into recovery at all to flash fresh update. dos opens up and shuts down after running some unknown commands. Being a noob to android coming from the iphone im at a loss. consider myself tech smart i can follow and understand most things. ive jailbroken and rooted my two previous phones so not a total noob. i just want to be able to do this one task its like a brick wall ive run into and im at a standstill!!!!! anyy help anyone could offer would be greatly appreciated

dbc00per said:
ive tried everything i read in most of these forums, and i know im missing something so stupid, so feel free to point out the obvious. but i cannot or have not ever been able to issue a command using adb.exe ive adjusted path name to were my android sdk is located. i know that the adbexe. in the tools folder itself doesnt open but i cant seem to get it working from command prompt either. im rooted and i thought i was nand unlocked until i tried recently to flash fresh's latest rom. (hboot 0.79.0000.) im currently running fresh.3 and would like to update. currently i have clockworks recovery running in rom manger because everytime i use ra amons i cant get into recovery at all to flash fresh update. dos opens up and shuts down after running some unknown commands. Being a noob to android coming from the iphone im at a loss. consider myself tech smart i can follow and understand most things. ive jailbroken and rooted my two previous phones so not a total noob. i just want to be able to do this one task its like a brick wall ive run into and im at a standstill!!!!! anyy help anyone could offer would be greatly appreciated
Click to expand...
Click to collapse
This would be better suited for Q&A that being said post the commands you are issuing and the errors you are getting. This would help someone trying to help you. Good luck

Try posting in clear concise sentences and it will help as well. Your post is like reading a teenagers tantrum and it's hard to follow.
From what I gathered, you can't get ADB to work, even though you're attempting to run it from a command prompt but the command prompt immediately closes from some unknown commands. That makes no sense.
From your computer, in windows, browse to the Android SDK folder.
Hold down the SHIFT key, and RIGHT-CLICK the tools folder and then LEFT CLICK "OPEN COMMAND WINDOW HERE."
With your phone connected via USB and debugging mode enabled type:
adb remount
and press enter.
What do you get?

First off...wrong section, this belongs in Q&A
Anyways...
1) Go to Settings -> Applications -> Development -> Enable USB debugging
2) Make sure HTC Sync is installed. Link
3) Right-click My Computer and go into Device Manager (while your phone is plugged in), if you see any yellow flags or unknown devices, remove them.
Now unplug your phone and plug it back in.
4) Place the sdk folder on your C:\ and run command prompt in Administrator mode.
Type "cd " (don't forget the trailing space), do not hit enter yet.
Now try to physically drag the tools folder into the prompt window, it will type text for you.
Hit enter.
5) Type adb and it should work.
If it doesn't work, well, you're going to need to give us more details...especially since if you follow what I wrote above correctly there is no reason it shouldn't work.

Sirchuk said:
Hold down the SHIFT key, and RIGHT-CLICK the tools folder and then LEFT CLICK "OPEN COMMAND WINDOW HERE."
Click to expand...
Click to collapse
Does that work in XP? I've never heard of that shortcut and it doesn't work on my current workstation.

Neotelos_com said:
Does that work in XP?
Click to expand...
Click to collapse
Oh gosh... i hope thats a work PC...
Its just a simple way to open up command window into that folder. Just Winkey+R, type 'cmd', hit enter, then navigate to the tools folder through command line. Hopefully you know command line well enough.

Neotelos_com said:
Does that work in XP? I've never heard of that shortcut and it doesn't work on my current workstation.
Click to expand...
Click to collapse
Only works in vista and win 7

gx1400 said:
Oh gosh... i hope thats a work PC...
Its just a simple way to open up command window into that folder. Just Winkey+R, type 'cmd', hit enter, then navigate to the tools folder through command line. Hopefully you know command line well enough.
Click to expand...
Click to collapse
Yeah like I said "workstation", I don't call any of my personal machines "workstations".
Also, I'd hope I know command line well considering I just gave advice on how to run adb through it.

thank you I've just gathered more information here than searching for days
Anywhere else.

my G2 is root proof.

Ive tried the black prince video, the unlockr method and the original xda perm root guide and my G2 will not perm root. Seriously need some help.

do you have adb and sdk installed?

>
no such thing!
its just smarter than you (;
lol

it is funny that you mention the black prince video, because that is what i used. im not sure, but i followed that video exactly and got it my first try. just watch the video very carefully, and follow EVERYTHING that he does and it should work. if not, then i am really not sure. obviously, you just need "S-off"

Are you using Visionary ? I would suggest the rage method, IMHO it's a lot more reliable and you can see if anything goes wrong because you're using individual commands.

i know its possible because I rooted my friends G2 just days before I got mine. I don't have adb, to be honest as soon as i see that it takes more than just installing a program on my pc, i flee, and its not because im new to android or rooting or anything like that, i just don't have a whole lot of spare time. And i DO have S-OFF. Like ill do everything in the blackprince video, then after I'm done I'll got and test the root by typing SU in terminal, and it says permission denied. Or for any of the other methods, same thing.
Now if someone could give me a REAL WALK THROUGH on how to do it in ADB and not just assume I already know how to use it and use vocabulary I don't understand because I've never used the program, i would be willing to try that method. It's just all the walkthroughs for ADB ive found just assume I've already used it before and know how to use it.

adamtheindien said:
Now if someone could give me a REAL WALK THROUGH on how to do it in ADB and not just assume I already know how to use it and use vocabulary I don't understand because I've never used the program, i would be willing to try that method. It's just all the walkthroughs for ADB ive found just assume I've already used it before and know how to use it.
Click to expand...
Click to collapse
Download HTC Sync from the HTC website (look in the downloads section), and install that on your PC. That'll give you all the USB drivers you need.
Download the Android SDK from http://developer.android.com/sdk/index.html and install it on your PC. Be sure to read the guide on installing it at http://developer.android.com/sdk/installing.html
Plug your phone in to your PC using the original HTC cable (do not use a third-party cable for this) and type "adb devices" at your PC's command prompt, and tell us if it can see your phone. It should show up your phone's serial number (don't tell us exactly what that is, this is a public forum), but if there's an error then we need to sort that first.
Edit - partially prompted by this request, I've started an "adb for Noobs" guide (very much a work-in-progress) at http://forum.xda-developers.com/showthread.php?t=865685

installed htc synce, sdk, jdk for sdk, went into command prompt, typed adb devices, said adb was recognized as any kind of command.
and thank you for starting that guide, definitely something that needed to be done.

http://www.youtube.com/watch?v=A1SOSXwkc_8

adamtheindien said:
installed htc synce, sdk, jdk for sdk, went into command prompt, typed adb devices, said adb was recognized as any kind of command.
and thank you for starting that guide, definitely something that needed to be done.
Click to expand...
Click to collapse
when you type adb devices does it recognize your device?
Super easy way.... http://forum.xda-developers.com/showthread.php?t=834228 just copy paste the codes.

Your phone might be s-off, but not allowing you to do any su commands. Mine was, but I just installed rom manager and it flashed clockwork recover no problem, then I flashed cyanogen and everything was good. Go into hboot and just make sure it says s-off, then do the rom manager bit. Try it and see if it works.

no it doesnt do anything. just says its not a command. and ive already looked at that link, i'm already lost when it tells me to navigate to a folder in a command window.

yeah, but i cant use rom manager since i dont have super user permissions. do i just temp root then try to install a rom? that seems sketchy. haha.

Earlier you said that you have S-OFF. If this is the case, then just open up Market and download Superuser by ChainsDD. Then you should be good to go.

adamtheindien said:
no it doesnt do anything. just says its not a command. and ive already looked at that link, i'm already lost when it tells me to navigate to a folder in a command window.
Click to expand...
Click to collapse
When you type "adb" on your PC, Windows needs to know where to find the "adb" program to run it. So you either need to specifically add the directory containing adb to your Windows PATH variable (which you can do in the environmental variables section, which will be in different places on different operating systems - on XP you need to right-click on My Computer, then select Properties, then Advanced, then the "Environmental Variables" button) - or you need to cd to where adb is stored under where you installed the Android SDK, and run it from that folder.

pretend youre explaining this to a five year old...

ok, which operating system do you have on your PC ?
Where did you install the Android SDK, i.e. which folder on the PC did you put it in ?

never mind guys, did what that dude said and just installed a rom with temp root and im all good now. thanks for everyones help though, sorry for my lack of knowledge in adb and what not.

[Q] before I begin rooting, one question...

So I just set up ADB (I THINK) can someone tell me if I did it correctly or not? When I typed in "adb devices" on the cmd thing a bunch of stuff popped up. After watching a video the guy said type "adb shell" for to test to see if it works and I got a msg saying "adb server is out of date. killing... *daemon started successfully"
So is my ADB set up properly so I can now begin rooting??

I dont recommend ADB try using this method.
http://forum.xda-developers.com/showthread.php?t=928160
Sent from my HTC Vision using XDA Premium App

what's wrong with ADB??

I would at least have it set up in case you need it before you root. It might save you from bricking (it has for me).
It doesn't sound set up correctly. When I run adb devices, it says the serial number, nothing else.

Sinistah_ said:
what's wrong with ADB??
Click to expand...
Click to collapse
ADB isn't required to root, and if you're having troubles and have no other need for the SDK or ADB, it can be a lot of unnecessary work.

for awhile it said it was incorrect or sumthin when I'd type "adb devices" into the cmd. Then when I messed with the path a bit and when I typed "adb devices" again, all this stuff popped up. Then I did the "adb shell" and that last thing popped up. What should I do??

martonikaj said:
ADB isn't required to root, and if you're having troubles and have no other need for the SDK or ADB, it can be a lot of unnecessary work.
Click to expand...
Click to collapse
so with this said, can I still use the method shown on wiki to root or do I have to do it the way with Visionary/Gfree??

Sinistah_ said:
so with this said, can I still use the method shown on wiki to root or do I have to do it the way with Visionary/Gfree??
Click to expand...
Click to collapse
I rooted my MyTouch4G with visionary/gfree/terminal emulator. No adb required but its a lifesaver if your phone can't boot!

well now I'm confused on what to do... Do I continue trying to fix this ADB problem or do I just do this other method everyones mentioning.

Sinistah_ said:
well now I'm confused on what to do... Do I continue trying to fix this ADB problem or do I just do this other method everyones mentioning.
Click to expand...
Click to collapse
They really aren't as separate of methods as you think. Every command you enter in ADB can be done by manually moving files into the proper locations, and executing commands via the Terminal Emulator app in the Market instead of the command window (via ADB) on your computer.

So when using the wiki instructions, instead of using cmd commands I use terminal emulator instead??
Sent from my T-Mobile G2 using XDA App

How am I supposed to do the first step on the wiki guide without abd??? I don't get it.
Sent from my T-Mobile G2 using XDA App

[Q] Hard Bricking

What are the odds of hard-bricking the Nexus 7 while rooting and istalling a custom kernel? And if it bricks, is there a way to fix it?
I ask this because I want to root it, but I'm really worried.
Also, how can you fix a soft brick?

I think you should really care of these questions if you somehow corrupt both bootloader and recovery. I don't really know, but bootloader isn't a thing that is modified during rooting or changing kernel. Just carefully read the thread about rooting programs, follow the instructions and everything should be ok. The most potentially harmful thing that can be done is corrupting the recovery. It can be solved if you have a computer with adb and drivers installed. Just a sшmple command and recovery is reflashed. Unlocking the bootloader is a kind of thing that doesn't really change anything so you couldn't boot or something. It just clears the storage and changes something deep inside. Flashing ROMS/Kernels is a kind of coping files and if something goes wrong you can always reflash it from recovery or with adb or some app from the rooting kit. And also you can always flash everything stock. Just read and think of what you're doing. Good luck.

Can you help me, when I type fastboot oem unlock in the command prompt, it says <waiting for device>. Any idea?

LittleConfucy said:
Can you help me, when I type fastboot oem unlock in the command prompt, it says <waiting for device>. Any idea?
Click to expand...
Click to collapse
You probably have not configured devide ids for adb.
But probably the use of "sudo" should solve your problem.

rtfpessoa said:
You probably have not configured devide ids for adb.
But probably the use of "sudo" should solve your problem.
Click to expand...
Click to collapse
So, what do I have to do?! Sorry, I'm a complete noob xD

LittleConfucy said:
So, what do I have to do?! Sorry, I'm a complete noob xD
Click to expand...
Click to collapse
Just run:
sudo fastboot oem unlock

rtfpessoa said:
Just run:
sudo fastboot oem unlock
Click to expand...
Click to collapse
It doesn't recognize sudo as a command

LittleConfucy said:
It doesn't recognize sudo as a command
Click to expand...
Click to collapse
Are you on windows?
If yes, are you on bootloader mode?
If not:
1-Power off
2-Power On + Vol. Down
Then you execute "fastboot oem unlock"
If it doesn't work try to use any of the auto tools that you can find all over XDA forums

LittleConfucy, as you haven't told us what OS you're using, I'll assume it's Windows 7 or 8, doesn't really matter. Go here, download, install, launch, press the big button on top named "Full Driver Installation" and read what it tells you to do. It's written clear enough to understand. Just will give you some tips.
1. To install adb drivers, you should enable camera mode. It can be done in Settings->Storage. Just click on 3 dots and go to the USB connection settings. Select the option with PTP in its name and uncheck MTP if checked. After that your device should be recognized properly.
2. This App had a bug some time ago. It downloaded drivers and couldn't find them later. The workaround is to copy c:\Program Files (x86)\WugFresh Development\data\drivers\universal_drivers\UniversalAdbDriverSetup7.msi and rename the copy to UniversalAdbDriverSetup6.msi. It'll help.

Do you have any idea where can I see the drivers that were installed on the computer?

Slavon-93 said:
LittleConfucy, as you haven't told us what OS you're using, I'll assume it's Windows 7 or 8, doesn't really matter. Go here, download, install, launch, press the big button on top named "Full Driver Installation" and read what it tells you to do. It's written clear enough to understand. Just will give you some tips.
1. To install adb drivers, you should enable camera mode. It can be done in Settings->Storage. Just click on 3 dots and go to the USB connection settings. Select the option with PTP in its name and uncheck MTP if checked. After that your device should be recognized properly.
2. This App had a bug some time ago. It downloaded drivers and couldn't find them later. The workaround is to copy c:\Program Files (x86)\WugFresh Development\data\drivers\universal_drivers\UniversalAdbDriverSetup7.msi and rename the copy to UniversalAdbDriverSetup6.msi. It'll help.
Click to expand...
Click to collapse
So I have to copy the file, paste it in the same directory, without deleting the previous file, and change its name?

Need help...
After I rooted, I opened BusyBox and it said:
"There was a problem opening a shell with root acces. This is either being caused by superuser/supersu or by a device that is inproperly rooted."
I downloaded root checker, and it says that it's not proprly rooted