Database Info

Checking firmware rev without activation

Is there a way to check if a new phone is pre-RC30 without activating it?
I'm looking to buy an unlocked G1 on ebay and would like the seller to verify the firmware revision before shipping.

1. Get adb.exe from the SDK or adbwin.zip and unzip the contents.
2. Plug G1 into computer via usb and turn it on.
3. Touch the android on screen when prompted.
4. Open command prompt on computer and navigate to the directory adb.exe is in.
5. Type in the command prompt adb shell getprop ro.build.fingerprint. The fingerprint will have the software version in it.

1. Have the seller power on the handset
2. After the startup screen finishes and it gets to the "no sim card" point, have them type "reboot"(enter). If the phone blanks its screen and restarts, it's <RC30.
This worked for me when quicly testing in a tmobile store.
-sparkle [I have an extra <RC30 handset that may be for sale]

foonly said:
1. Have the seller power on the handset
2. After the startup screen finishes and it gets to the "no sim card" point, have them type "reboot"(enter). If the phone blanks its screen and restarts, it's <RC30.
This worked for me when quicly testing in a tmobile store.
-sparkle [I have an extra <RC30 handset that may be for sale]
Click to expand...
Click to collapse
The original method

jashsu said:
1. Get adb.exe from the SDK or adbwin.zip and unzip the contents.
2. Plug G1 into computer via usb and turn it on.
3. Touch the android on screen when prompted.
4. Open command prompt on computer and navigate to the directory adb.exe is in.
5. Type in the command prompt adb shell getprop ro.build.fingerprint. The fingerprint will have the software version in it.
Click to expand...
Click to collapse
You have to Enable the USB Debugging in Phone But without Activating it is it Possible ??

hetaldp said:
You have to Enable the USB Debugging in Phone But without Activating it is it Possible ??
Click to expand...
Click to collapse
Just tried. It is totally not possible with device which "reboot + enter" trick doesn't work.
You can only access APN Setting without activation. Sadly.

How to Bypass 'No Sim Card' locked screen on no data plan G1

Hi all,
I'm trying hard to bypass the 'no sim card' locked screen that I am currently getting on my G1 Android Dev Phone 1 RC29 that I recently installed DREAIMG.nbh on. Ideally, I would like to run the android scripting environment on my phone with wireless access.
So far, my primary document that I've used to consult this matter has been this one from JesusFreke: forum.xda-developers.com/showthread.php?t=452316.
The first thing the document suggests is, "to connect to your phone with adb shell and get root access, and then type the following command:
sqlite3 /data/data/com.android.providers.settings/databases/settings.db "INSERT INTO system (name, value) VALUES ('device_provisioned', 1);"
When I run this command, I get a 'sqlite3: permission denied' error (see below).
3.bp.blogspot.com/_scN4BTBqXiY/S-dOBTo8LiI/AAAAAAAAAfU/rtmnXywBPzI/s1600/sqlite3+permission+denied1.jpg
I recognize now that the assumption with this command is that your phone is running on RC30, as the article notes. Mine is running on RC29. In order to make this command functional, it appears as though I need to ADB push the busybox binary.
As you can see in the image above, I was able to successfully adb push the busybox binary to the /data/local of the G1.
Furthermore, I ran the wireless command in step two of the above tutorial just to see what would happen and I get this message:
3.bp.blogspot.com/_scN4BTBqXiY/S-dMU3sO2-I/AAAAAAAAAfM/Z9r_glscNvU/s1600/Wireless.jpg
With all of this being said, however, I still can't seem to bypass my original screen that says 'No Sim Card'
3.bp.blogspot.com/_scN4BTBqXiY/S-dLhIjpQ7I/AAAAAAAAAfE/JkbHfOgW3f0/s1600/DSCN5623.JPG
If someone out there knows that is going on that I should change, please let me know, because I am really running into a dead end here.
Thank you very much!

I don't remember if RC29 has this, but in the initial setup wizard you should be able to press the menu key and access a wireless setup utility to connect to wifi.
Also, after you wipe and flash (or turn the phone on the first time), and if you get the "touch the android to begin" screen you can touch each of the 4 corners of the black background in a clockwise pattern starting in the upper left to go to the home screen.
That sqlite3 command needs to be run in a root shell. Make sure you're root. The $ prompt is the regular phone user. The root prompt will be # instead. Try running "su" after connecting with "adb shell" to become root. Is the rom you're using rooted?

Broken screen, need to retrieve files off phone! help please

My screen first cracked and then the LCD completely went now... I have files I need to retrieve off the phone. It is rooted and running some ICS build... I believe the phone is in USB debugging mode, the screen still 'works' I can unlock the phone but nothing is displayed on the screen. Possibly someone could help me out with the adb process for pulling the contents off the /sd
Any help will be GREATLY appreciated, thank you for your time.

ur usb mass storage should still work. can u just plug ur phone to a usb port and get things off the phone ?

As previously stated. I believe the phone was in USB debugging mode. And now the screen is completely black... impossible to navigate to where i need to be.

You'll need adb setup on your computer, and you'll need to cd your way into the folder with adb.exe. Forgive me for hotlinking, but this will make it easier: Download this file, courtesy of NexusSHacks.com (I believe it is Zedomax around here). I would advise to unzip the contents in this file to your C:\Nexus directory, so that adb.exe is at C:\Nexus\adb.exe.
Now, plug in your phone. Open your start menu and search for "cmd" and open up Command Prompt. This is the basic Windows CLI (Command Line Interface).
First, you'll need to open the directory of the Nexus folder you created earlier. To do this, type in the command prompt:
Code:
cd C:\Nexus
Now, you want to make sure adb sees your phone:
Code:
adb devices
The adb service should start and if it sees your phone it will pop up a serial number. If there is no serial number, you can't use adb while inside android and you'll need to tick the option or find an alternative way. Assuming it finds your device, you are good to go.
In order to copy the /sdcard folder of your Nexus S, you will use the pull command. We will throw all of the files into C:\Nexus\sdcard, for reference. So in the command prompt, type:
Code:
adb pull /sdcard .\sdcard
It looks a little confusing but don't stress. Just make sure you type it in exactly (dot, correct slash, etc). This will take a little while since it might transfer up to ~15GB worth. You'll see a new line with "C:\Nexus>" with a flashing cursor when it is done. Then you can view all the contents of your sdcard at C:\Nexus\sdcard and do with them as you please.
Also note, for this you'll need up to ~15GB of free space on your C:\ partition, make sure you have this before you start. Good luck

old post I know, but I just dropped my Samsung Captivate (rooted with debugging on) and internal screen cracked (gorilla glass is perfectly fine!), so I am in the same boat. After DAYS... actually DAYS of trying everything from every forum I FOUND A FIX!!!
Now admittedly, I am unsure which of these two (or both) fixed the issue, but here is what I did:
via Google Play's online "shop", I installed "Auto Mount Your SD Card" by JRTStudio (admittingly, unsure if this did anything as I cannot verify if it installed or anything via the phone)
https://play.google.com/store/apps/...wsMSwxLDEsImNvbS5qcnRzdHVkaW8uYXV0b21vdW50Il0.
then I DL'ed MoboRobo and after a few frustrated phone reboots, usb cable connections and much cursing IT CONNECTED!
http://www.moborobo.com/
I am currently DLing all my files from my broken phone!
I had to pass this along as I said... NOBODY seems to know about this as it has taken me DAYS to do this! Not even ATT (Current carrier) nor Spring (whom I am switching to in a month or so) could help me!

You save my life with that "moborobo". Thank you very much.

Glad I could help!!!

Thanks went to both of u, quit important piece of knowledge.
One question; r u downloading "moborobo" on ur Android, on your pc or on both of them?

just on PC, not needed on the phone unless you want to go via WiFi

Harbb said:
If there is no serial number, you can't use adb while inside android and you'll need to tick the option or find an alternative way.
Click to expand...
Click to collapse
What do you mean by this?
My adb service doesn't detect my phone, I used Droidzone's tutorial. I believe usb debugging needs to be on for adb to work, which in my case is useless cause my screen is broken so can't turn on usb debugging.
This is what happens:
---------------------------
C:\>adb devices
List of devices attached
C:\>
---------------------------
---------- Post added at 11:31 PM ---------- Previous post was at 11:23 PM ----------
^when I say broken, I mean the whole screen is distorted, I cannot see anything

droidoidoid said:
What do you mean by this?
My adb service doesn't detect my phone, I used Droidzone's tutorial. I believe usb debugging needs to be on for adb to work, which in my case is useless cause my screen is broken so can't turn on usb debugging.
This is what happens:
---------------------------
C:\>adb devices
List of devices attached
C:\>
---------------------------
---------- Post added at 11:31 PM ---------- Previous post was at 11:23 PM ----------
^when I say broken, I mean the whole screen is distorted, I cannot see anything
Click to expand...
Click to collapse
Reboot to recovery. Bam, working ADB. You can navigate there pretty easily. Pull battery, then re-insert. VOL + & PWR, two click on VOL -, PWR button once. You're in recovery now.

QtADB also can be used is this case
http://qtadb.wordpress.com/download/

paskalion said:
QtADB also can be used is this case
http://qtadb.wordpress.com/download/
Click to expand...
Click to collapse
No go on this either.
Downloaded QtADB, ran the .exe
Pointed to the folder with the aapt and adb binaries, program opened up
Phone's connected and on (I can hear texts coming through), hit refresh a few times, still not detecting

polobunny said:
Reboot to recovery. Bam, working ADB. You can navigate there pretty easily. Pull battery, then re-insert. VOL + & PWR, two click on VOL -, PWR button once. You're in recovery now.
Click to expand...
Click to collapse
That's a little tough. I'm using a Galaxy S so I'm following instructions for that, but it's hard to know if I'm in recovery mode or not. Since adb doesn't detect the device, it's hard to know whether the phone went into recovery mode, or whether adb is setup correctly. It would be handy for a voice sample to play "recovery mode" once the phone boots into it.

droidoidoid said:
That's a little tough. I'm using a Galaxy S so I'm following instructions for that, but it's hard to know if I'm in recovery mode or not. Since adb doesn't detect the device, it's hard to know whether the phone went into recovery mode, or whether adb is setup correctly. It would be handy for a voice sample to play "recovery mode" once the phone boots into it.
Click to expand...
Click to collapse
You're in the wrong forum, then.
And whether or not adb is installed properly, you would know in your device manager under Windows. Appears as a device.

polobunny said:
You're in the wrong forum, then.
And whether or not adb is installed properly, you would know in your device manager under Windows. Appears as a device.
Click to expand...
Click to collapse
Ok... Galaxy S i9000 stuff goes in the Galaxy S i9000 forum.... that's probably why my other post got deleted! :laugh:
As for adb... it appears as a process in task manager, so it's running - I know that much. It's not appearing as a device in device manager (why would it if it's a process? or are you referring to my phone appearing as a device?)
Only areas I can think of that aren't correct are the environment variable and the way I'm doing recovery mode. Since I can't see the screen, I don't know which one is causing the issue! :crying:

Samsung broken??
Contact this guy in Paris , he's very good and friendly!! he repairs my blue Galaxy S3 in front of me
Tel: 0950 850 500 Direct Technique
repare-galaxy com
don't hesitate to call them because i know their skills and it's very good!!
tell them that u call from Mike ciao guys!!

Problem!
Harbb said:
Code:
adb pull /sdcard .\sdcard
It looks a little confusing but don't stress. Just make sure you type it in exactly (dot, correct slash, etc). This will take a little while since it might transfer up to ~15GB worth. You'll see a new line with "C:\Nexus>" with a flashing cursor when it is done. Then you can view all the contents of your sdcard at C:\Nexus\sdcard and do with them as you please.
Click to expand...
Click to collapse
Hey, I got to this problem and I got stuck. I also have a Nexus S with a cracked screen. When I put in the final phrase into the command window it just told me that 0 filles were pulled! Why didnt it pull my files?
What I am trying to do is get all of my pictures and others off the phone.
Please help!

SkullMblem said:
Hey, I got to this problem and I got stuck. I also have a Nexus S with a cracked screen. When I put in the final phrase into the command window it just told me that 0 filles were pulled! Why didnt it pull my files?
What I am trying to do is get all of my pictures and others off the phone.
Please help!
Click to expand...
Click to collapse
This happened to me as well. You have to make sure that your phone has its sdcard folder mounted. Type "adb shell" to get access to the phones command terminal. Then type in "mount /sdcard" I think, or maybe it was "mount sdcard". Either way will probably work so long as you are in the root directory of the phone. You can navigate around in the phone just like a normal linux terminal. "ls" shows list of files and folders in the current directory, "cd foldername" moves into a folder, "cd ../" moves back, "cd /" goes to root directory, etc. Anyhow, once you have mounted the sdcard, you can type exit to leave the shell terminal, and then issue the command "adb pull /sdcard .\sdcard" to get the files. I had a custom rom image in the root of my sdcard so the move took quite a while ~15 minutes. On success of the pull command you should see a bunch of statuses like:
pull: sdcard/data/somefile -> .\sdcard/data/somefile
pull: sdcard/DCIM/somefile -> .\sdcard/DCIM/somefile
.
.
.
XXXX files pulled. 0 files skipped
(Some more transmission stats)
Hope it works out for who ever reads this.
Side note:
On my phone the screen was smashed. I replaced it and it still would not turn on, but it was still running. I had a rooted phone with CM10 rom on it. ADB debugging was one (if its off your pretty much screwed). I started up the phone, and plugged in the usb cable. I tried to use both adb and fastboot from windows terminal. "fastboot devices" would echo back nothing, and "adb devices" would echo back my phone's device number but state it was offline. So to get it online I did the following:
1.) pull batttery.
2.) boot into bootloader (hold power and volume up) the phone shouldn't vibrate if it does you have just normally powered it on. It took me quite a few times to get this to go into the bootloader. To make sure you get in the bootloader type "fastboot devices". If nothing comes up you not there.
3.) once verified you are in the bootloader you need to go into recover mode. Press volume down twice and then hit power (this would normally move the cursor on your phone down to recovery and select it if you could see whats happening on the screen).
4.) wait a bit for it to load into recovery, try typing "adb devices". You should eventually see you device show up as online. At this point you may enter the shell as above, mount the sdcard, exit the shell and pull your files.
Windows instuctions:
Prerequisites are installing adb.exe and fastboot.exe via installing the Android SDK on your computer. They will show up in the platform-tools folder of the install location. Add that folder to your environmental path variable so you can run the ADB and fastboot commands from any folder. Install the ADB driver for your phone (allows you to issue adb commands to your phone when USB is plugged in) by plugging in your phone and going to device manager, find your phone which should show up as a exclamation point, right click update driver, click "browse...", then "let me pick...", click top entry something like "show all", and then let the list populate. On the left look for "samsung" and then select the first one that is something like "samsung adb driver interface". And you should be good to go.
Sorry for the long winded post, I just like to try and explain as much as possible.

Successfully Recoverd data
Well My Samsung S2's Screen broke down few days ago.. Now i have retrieved the data by following the 2nd method in the following article..! I Hope this works for you aswell...
I can not Post the link here.. PM me if you want the link...!

Dream G1 Flash Error

I was trying to downgrade from RC30 to RC7. Pressed Camera+Power button, after gray screen popped, it checks something and then an error popped..."Not allow"
What happened here?

*should be in q&a thread*
you may not be flashing the right dreaming.nbh or you may need to make a gold card first - don't have a link handy but google "cyanogen g1 root wiki" here you will have all the info you need as well as links to the proper downloads
Sent from my HTC Vision using xda premium

Actually, I really don't know where to begin. I cannot get into phone w/out register with google. But then, no wifi. Cannot run adb because everytime I plug in phone to pc, it reads the sd card. Already put all necessary files for rooting. Install everything but still end up with nothing.
DREA100 PVT 32B
HBOOT-0.95.0000
CPLD-4
RADIO-2.22.19.261
SEP 2 2008
SERIAL 10
I tried all the bypass methods but nothing... no reboot, nothing.... Going around in circles as there are many guides on how to root this phone. Also applied the method where you code in the commands to activate developement w/out going into the phone.... that too cannot get thru. So far, I've tried 3 different ways to root. None of them worked.
Thanks....

well if you downloaded adb through the xda package and you followed the link in there to bypass and you still can't, I suggest finding someone with a tmobile sim card to bypass, then remove their card after you get wifi on and continue the steps
Sent from my HTC Vision using xda premium

I have T-Mobile simcard. Problem is there's no tmobile here on the islands. Now how do I activate wifi so I can register? At the moment, still cannot get pass the google registration because of no wifi.

the steps listed in the cyanogen g1 root wiki will do it, if you read through the wiki you will see a link explaining it very well
if you still have problems report back exactly what you have done, and you'll get more help
Sent from my HTC Vision using xda premium

Ok, I tried this link but got stuck at the following:
Rooting your RC29 or lower phone:
On RC29 phones and lower, anything you type into your keyboard is also being run in a hidden console with root permissions. More information regarding that at the bottom of this post. But, to get root access, do the following:
Instructions:
Download recovery.img or the new version by Amon recovery-RA-dream-v1.5.2.img and copy it to your SD card (see the previous instructions on how to copy from your computer to your Phone's SD card).
Download the Hard SPL and copy the zip file to the SD card.
All files must be on the root of your SD card.
Restart your phone. Wait for your phone to start up fully and show the home screen.
After your phone starts up, hit the enter key twice, type "telnetd" and press enter. (Yes, it will start up a contact search, don't worry. Just type it.)
Download an Android "Telnet" application from the Market and connect to localhost.
If you connect successfully, you will have a root prompt "#".
Type the following into Telnet (these commands will give you root access easier in the future):
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
cd sdcard
flash_image recovery recovery.img
cat recovery.img > /system/recovery.img
Now you have root!
Cannot accept "telnetd"....

so you are in the android os now? if so do you have telnet app downloaded onto phone?
Sent from my HTC Vision using xda premium

Not in android os. Tried adb devices and no devices shown. I tried this link but cannot enter "setprop persist.service.adb.enable 1". It doesn't change to adb development mode. Tried a thousand times. Could it be because this phone is network locked? But then I am using TMobile Sim which goes directly to the main screen.
Any other possible ways to activate the wifi?

I am very sorry guys. I just put up this computer and forgot to install android drivers but I plug in the phone. After numerous attempts, I decided to try other computers. Wallah, it reads phone as adb. All is fine now. Phone working perfectly.
Once again I am very sorry for all this.

Jabbacks said:
I am very sorry guys. I just put up this computer and forgot to install android drivers but I plug in the phone. After numerous attempts, I decided to try other computers. Wallah, it reads phone as adb. All is fine now. Phone working perfectly.
Once again I am very sorry for all this.
Click to expand...
Click to collapse
I was just about to mention the adb android drivers, as I recently had to perform the same steps (using a different xda guide tho, telnetd is weird). Congratulations.
Everything working?

Unlocked bootloader

I have my Samsung note 3, and it will never be unlocked. So i was thinking about moving to this. Is the Verizon edition unlocked for custom roms?
Sent from my SM-N900V using XDA Free mobile app

scoreboard said:
I have my Samsung note 3, and it will never be unlocked. So i was thinking about moving to this. Is the Verizon edition unlocked for custom roms?
Sent from my SM-N900V using XDA Free mobile app
Click to expand...
Click to collapse
It doesn't come unlocked, but you can unlock it. That's why are a lot of us are on this phone. I had an S5 ordered, but decided against it, when I saw there wasn't any progress being made on it. I cancelled my order, bought my M8, and haven't looked back. Give me an unlocked bootloader, or give me death.

You can S-OFF (which unlocks bootloader) & root it immediately after getting it.
I came from a locked Galaxy S4 and have to say this phone is snappier than an iPhone & as unlockable as a door thats compatible with all keys ;D. Love love loveeee this phone and highly recommend it! Go for it!
I unlocked mine the moment I got home with it, no OTA update required as some people have said to do before unlocking it & as far as I've seen no ones had an actual "Oh no! They made it impossible to unlock like Sammysung!" moment.

Ive tried a for the last two days to root my htc m8..but i can not get it to work...tried htc unclock tried setting up adb...but the first gives me an mid error and the second does not recognize my phone...i did install the newest update before i tried to s-off....any help would be great...

Frausbite77 said:
Ive tried a for the last two days to root my htc m8..but i can not get it to work...tried htc unclock tried setting up adb...but the first gives me an mid error and the second does not recognize my phone...i did install the newest update before i tried to s-off....any help would be great...
Click to expand...
Click to collapse
Have u tried the weak sauce app for root then fire water to s-off?
Sent from my Insanely powered M8 using Tapatalk

holla420 said:
Have u tried the weak sauce app for root then fire water to s-off?
Sent from my Insanely powered M8 using Tapatalk
Click to expand...
Click to collapse
I set up adb using the method from root junky. but my computer won't recognize my device. I must have tried it like 50 times, so i tried the htcdev unlock method...my computer recognizes by device but after i copy the token i get the mid 160 error.

Frausbite77 said:
I set up adb using the method from root junky. but my computer won't recognize my device. I must have tried it like 50 times, so i tried the htcdev unlock method...my computer recognizes by device but after i copy the token i get the mid 160 error.
Click to expand...
Click to collapse
U must not being in the right directory
Sent from my Insanely powered M8 using Tapatalk

Frausbite77 said:
I set up adb using the method from root junky. but my computer won't recognize my device. I must have tried it like 50 times, so i tried the htcdev unlock method...my computer recognizes by device but after i copy the token i get the mid 160 error.
Click to expand...
Click to collapse
What that guy above me said, if you using Windows make sure you right click+shift in the platform tools directly then see if it shows up with adb devices, if not check your drivers.

Frausbite77 said:
Ive tried a for the last two days to root my htc m8..but i can not get it to work...tried htc unclock tried setting up adb...but the first gives me an mid error and the second does not recognize my phone...i did install the newest update before i tried to s-off....any help would be great...
Click to expand...
Click to collapse
HTCDEV unlock doesn't work for the Verizon variant. To s-off just follow this step by step guide:
http://forum.xda-developers.com/showthread.php?t=2708628
PRO TIPS: Let's say that your adb and fastboot files are located in C:\Program Files\Android. Add this directory to your system path by pressing the Windows key and typing "environment". After a few letters you'll see an option called "Edit the System Environment Variables". Click on this option. The system properties windows will open to the Advanced tab. Click the Environment Variables button. In the System Variables field you'll see a variable called Path. Click on it and choose edit. In the variable value field you'll see a list of paths separated by semi colons. We want to add the path of your adb and fastboot files to the system Path variable so that adb and fastboot commands can be executed anywhere. For the example location I used above you would add the following to the end of the list:
;C:\Program Files\Android
To test, open a command prompt and type "adb". This should launch adb with no parameters. Now you can use adb and fastboot commands anywhere. When you download the firewater script file, you can just leave it in the Downloads directory. If you use Chrome you could click the arrow next to the file and choose "show in folder". Then shift+right click an empty portion of the Downloads directory window and choose "open command window here" (you can also shift+right click on folders icons to accomplish this). Should be easy to s-off now.
NOTES:
*Once adb is setup issue the command "adb devices" to ensure your phone is recognized. The first time you will get a popup on your phone asking if you want to allow the PC adb access. Make sure you check "always allow".
*Before you issue the "su" command wait about 30 seconds to allow WeakSauce to root the phone after reboot. If you get an error saying "su not found" it's because WeakSauce has not yet rooted the phone. Wait 10 seconds and try again.
*When you issue the "su" command wake your phone's display and look for a SuperSu request. Allow it obviously.
*It's possible that the process may fail. If it does just try again. If it keeps failing try a different USB 2.0 port. Also make sure you're using the best USB cable that you have. The one that came with the phone should work.

Doc Ames said:
HTCDEV unlock doesn't work for the Verizon variant. To s-off just follow this step by step guide:
http://forum.xda-developers.com/showthread.php?t=2708628
PRO TIPS: Let's say that your adb and fastboot files are located in C:\Program Files\Android. Add this directory to your system path by pressing the Windows key and typing "environment". After a few letters you'll see an option called "Edit the System Environment Variables". Click on this option. The system properties windows will open to the Advanced tab. Click the Environment Variables button. In the System Variables field you'll see a variable called Path. Click on it and choose edit. In the variable value field you'll see a list of paths separated by semi colons. We want to add the path of your adb and fastboot files to the system Path variable so that adb and fastboot commands can be executed anywhere. For the example location I used above you would add the following to the end of the list:
;C:\Program Files\Android
To test, open a command prompt and type "adb". This should launch adb with no parameters. Now you can use adb and fastboot commands anywhere. When you download the firewater script file, you can just leave it in the Downloads directory. If you use Chrome you could click the arrow next to the file and choose "show in folder". Then shift+right click an empty portion of the Downloads directory window and choose "open command window here" (you can also shift+right click on folders icons to accomplish this). Should be easy to s-off now.
NOTES:
*Once adb is setup issue the command "adb devices" to ensure your phone is recognized. The first time you will get a popup on your phone asking if you want to allow the PC adb access. Make sure you check "always allow".
*Before you issue the "su" command wait about 30 seconds to allow WeakSauce to root the phone after reboot. If you get an error saying "su not found" it's because WeakSauce has not yet rooted the phone. Wait 10 seconds and try again.
*When you issue the "su" command wake your phone's display and look for a SuperSu request. Allow it obviously.
*It's possible that the process may fail. If it does just try again. If it keeps failing try a different USB 2.0 port. Also make sure you're using the best USB cable that you have. The one that came with the phone should work.
Click to expand...
Click to collapse
Thank you for letting me know about the HTC Dev...I have a mac and set up ADB...it shows my phone off line...i get the message that says allow this computer and check always...i run adb devices and now it just returns blank...i reinstall drivers which is htc sync but the problem persists....

Frausbite77 said:
Thank you for letting me know about the HTC Dev...I have a mac and set up ADB...it shows my phone off line...i get the message that says allow this computer and check always...i run adb devices and now it just returns blank...i reinstall drivers which is htc sync but the problem persists....
Click to expand...
Click to collapse
Try 'adb kill-server' then issue 'adb start-server' then try 'adb devices'. If that doesn't work, try a different USB port. If still no joy try a different USB cable. If that doesn't work try restarting the Mac, restarting the phone, spinning around in an office chair three times, and blowing into a Nintendo cartridge. If that doesn't work I don't know what else to suggest besides trying it on a different computer or maybe in Windows. I've never had an issue with ADB so if somebody else has any ideas for Frausbite77 please chime in.
Edit: I googled this Mac ADB guide. I don't know if it really matters, but it says to have ADB/fastboot in the /usr/bin directory. Check it out. There's a script file and when run it installs the Android SDK tools to the appropriate folder. Also check the comments. Somebody else has probably had the same problem as you:
http://htc-one.wonderhowto.com/how-...-mac-os-x-send-commands-your-htc-one-0151178/
Edit 2: After reading a user's comment that the script was broken I looked at the script and it was, in fact, broken. I fixed it. Follow the guide but use this zip instead:

Doc Ames said:
Try 'adb kill-server' then issue 'adb start-server' then try 'adb devices'. If that doesn't work, try a different USB port. If still no joy try a different USB cable. If that doesn't work try restarting the Mac, restarting the phone, spinning around in an office chair three times, and blowing into a Nintendo cartridge. If that doesn't work I don't know what else to suggest besides trying it on a different computer or maybe in Windows. I've never had an issue with ADB so if somebody else has any ideas for Frausbite77 please chime in.
Edit: I googled this Mac ADB guide. I don't know if it really matters, but it says to have ADB/fastboot in the /usr/bin directory. Check it out. There's a script file and when run it installs the Android SDK tools to the appropriate folder. Also check the comments. Somebody else has probably had the same problem as you:
http://htc-one.wonderhowto.com/how-...-mac-os-x-send-commands-your-htc-one-0151178/
Edit 2: After reading a user's comment that the script was broken I looked at the script and it was, in fact, broken. I fixed it. Follow the guide but use this zip instead:
Click to expand...
Click to collapse
Ok, well so I never got adb to show my device on line....but when i typed ./adb reboot, the device actually responds to the commands...taking a risk i went ahead and pushed the firewater files and the process worked. I was able to unlock my device and install twrp...so i figured out that for and to work i have to type in ./ before i type in any commands...i don't if i messed something up along the way or what...but in the end i have gotten i was able to root and get s off....maybe i got lucky lol...thanks so much for the help!!

Frausbite77 said:
Ok, well so I never got adb to show my device on line....but when i typed ./adb reboot, the device actually responds to the commands...taking a risk i went ahead and pushed the firewater files and the process worked. I was able to unlock my device and install twrp...so i figured out that for and to work i have to type in ./ before i type in any commands...i don't if i messed something up along the way or what...but in the end i have gotten i was able to root and get s off....maybe i got lucky lol...thanks so much for the help!!
Click to expand...
Click to collapse
That's the proper command line for using Adb on a Mac. It won't work without using ./ before the command.
Sent from my HTC6525LVW using Tapatalk

Frausbite77 said:
Ok, well so I never got adb to show my device on line....but when i typed ./adb reboot, the device actually responds to the commands...taking a risk i went ahead and pushed the firewater files and the process worked. I was able to unlock my device and install twrp...so i figured out that for and to work i have to type in ./ before i type in any commands...i don't if i messed something up along the way or what...but in the end i have gotten i was able to root and get s off....maybe i got lucky lol...thanks so much for the help!!
Click to expand...
Click to collapse
My bad. I should have mentioned that to execute a file in a Unix-like operating system you need to enter the full or relative path if it's not in your $Path environment variable. That's why you needed to add a './' before the command. The './' indicates that the file is in the current directory. That's probably why that guide recommended putting adb and fastboot in /usr/bin. If you want to fix it so that adb and fastboot commands can be run from anywhere open a terminal, change to the directory where adb and fastboot are located, and issue the following commands:
sudo mv adb /usr/bin
sudo mv fastboot /usr/bin
That will move adb and fastboot into /usr/bin which is in your $Path so you can issue the commands anywhere without using './'. I'm glad you got your M8 s-offed and recovery installed. If you're looking into custom ROMs, I can personally recommend ViperOne as a great stock option and LiquidSmooth as an AOSP option. Try em' out. Now that you have recovery you can just restore a backup if you don't like your current ROM.

Doc Ames said:
My bad. I should have mentioned that to execute a file in a Unix-like operating system you need to enter the full or relative path if it's not in your $Path environment variable. That's why you needed to add a './' before the command. The './' indicates that the file is in the current directory. That's probably why that guide recommended putting adb and fastboot in /usr/bin. If you want to fix it so that adb and fastboot commands can be run from anywhere open a terminal, change to the directory where adb and fastboot are located, and issue the following commands:
sudo mv adb /usr/bin
sudo mv fastboot /usr/bin
That will move adb and fastboot into /usr/bin which is in your $Path so you can issue the commands anywhere without using './'. I'm glad you got your M8 s-offed and recovery installed. If you're looking into custom ROMs, I can personally recommend ViperOne as a great stock option and LiquidSmooth as an AOSP option. Try em' out. Now that you have recovery you can just restore a backup if you don't like your current ROM.
Click to expand...
Click to collapse
Thanks for the advice...actually i was just going to ask about some roms...just flashed viper rom and gonna give it a go...thanks for all the help...

Frausbite77 said:
Thanks for the advice...actually i was just going to ask about some roms...just flashed viper rom and gonna give it a go...thanks for all the help...
Click to expand...
Click to collapse
You'll love it. A couple thing to note though. For some reason the 1.6 download doesn't actually contain the 1.6 OTA so you'll want to go to 'About phone' and update to 1.6. Also I believe that ViperOne defaults to power saver mode. You can change this by using the toggle in the notification drawer. If you want to add power saver and extreme power saver to the settings menu follow this guide:
http://forum.xda-developers.com/showthread.php?t=2710946

Doc Ames said:
You'll love it. A couple thing to note though. For some reason the 1.6 download doesn't actually contain the 1.6 OTA so you'll want to go to 'About phone' and update to 1.6. Also I believe that ViperOne defaults to power saver mode. You can change this by using the toggle in the notification drawer. If you want to add power saver and extreme power saver to the settings menu follow this guide:
http://forum.xda-developers.com/showthread.php?t=2710946
Click to expand...
Click to collapse
wow, man viper rom is insane, thanks for the update heads up...i wouldn't have even thought to do that...guess i have tons of reading to catch up on...thanks...