Database Info

Adb question

I had a bit of trouble setting up adb and fastboot,when I typed adb devices nothing came up except wrong command so I copied fastboot.exe to platform tools folder and now it gives me a serial number and I was able to copy an apk using adb pull blah blah to my PC,anyway my question is am I set up for unlocking then rooting?
wildfire cyanogenmod nightly
hboot -1.01 s-off xtc clip

SuperCID on Mac OSX

Okay, I'm about to pull my hair out. I've Googled this, I've looked for YouTube videos for this, and I've even looked on here for this.
I found one post about obtaining SuperCID on Mac, but the post ends with no real solution (that I can see).
I'm trying to get SuperCID but I do not own a Windows PC. I downloaded the SDK for Mac on the Android Dev site, but what now? I don't know where to go from there.
Can anyone help me?
Sent From My HTC Sensation 4G Using XDA Premium

Bump to the top.
Sent From My HTC Sensation 4G Using XDA Premium

Avoid trouble. Visit someone with real computer before you'll brick your Sensation.
Mike

sp5it said:
Avoid trouble. Visit someone with real computer before you'll brick your Sensation.
Mike
Click to expand...
Click to collapse
I've seen it's possible, it just wasn't explained In detail.
Sent From My HTC Sensation 4G Using XDA Premium

Set up adb (make sure you have the htc drivers), open utilities, then terminal, cd to your adb directory, write in commands from dev section with ./ in front (ex: ./adb devices)

Couldn't you use VirtualBox on your mac to install linux (ubuntu or something) and do it the proper way using revolutionary.io and the android SDK?

Behold_this said:
Set up adb (make sure you have the htc drivers), open utilities, then terminal, cd to your adb directory, write in commands from dev section with ./ in front (ex: ./adb devices)
Click to expand...
Click to collapse
I thought the drivers could only be set up on Windows.
Sent From My HTC Sensation 4G Using XDA Premium

[GUIDE] Set up ADB & fastboot on Mac OSX
Make sure you have already downloaded the ADB & fastboot files and that they at located in a directory that is easy for you to find (example: /Users/home/Android-sdk/platform-tools).
1) you have two options for using ADB & fastboot:
open terminal and navigate to your directory containing ADB and fastboot **if using this method skip to step 5, also you should note that you will need to add "./" (without the quotes) to the beginning of each ADB or fastboot command (example: ./adb devices)**
configure ADB & fastboot to run natively (recommended) **if using this method proceed to next step**
2) make an entry in ~/.bash_profile configuration file by executing the following command in terminal:
Code:
nano ~/.bash_profile
3) the corresponding file will open in a text editor window, add the following line of text, save your changes, and exit text editor:
Code:
export PATH=${PATH}:your_sdk_dir
(example: export PATH=${PATH}:/Users/home/android-sdk/platform-tools)
4) execute the following command in terminal, then quit terminal:
Code:
source ~/.bash_profile
5) check if all is working by entering the following command in terminal (your phone should be connected to your Mac via USB and must have USB debugging enabled):
Code:
adb devices
(you should see your device serial number returned. if device is not found move on to step 6)
6) if necessary, install HTC driver, and run the above command again - can be done by:
installing naked htc driver (can be found in dev section)
installing PDAnet which installs the drivers for many Android devices

Behold_this said:
Make sure you have downloaded the ADB & fastboot files and that they at located in a directory that is easy for you to find (example: Users/home/Android-sdk/platform-tools).
1) you have two options for using ADB:
open terminal and navigate to your directory containing adb **if using this method skip to step 5
configure adb to run natively **if using this method proceed to next step
2) make an entry in ~/.bash_profile configuration file by typing the following command in terminal:
Code:
nano ~/.bash_profile
3) a new file will open in a text editor, add the following line to text file and save:
Code:
export PATH=${PATH}:your_sdk_dir
(example: export PATH=${PATH}:Users/home/android-sdk/platform-tools)
4) type the following command in terminal then quit terminal:
Code:
source ~/.bash_profile
5) install HTC driver, can be done by:
installing naked htc driver (can be found in dev section)
installing PDAnet which installs the drivers for many Android devices
6) check if all is working by entering the following command in terminal:
Code:
adb devices
(you should see your device serial number returned)
7) follow steps as normal for superCID by entering fastboot commands in terminal (found in dev section)
Click to expand...
Click to collapse
Thanks man.

[S-Off] and Device Offline for PJ831000

This was answered a little bit in the S-Off thread and I would like to post it for everyone that has the PJ8310000 device and they are running into device "offline" when using adb devices. This is for Windows 8 only. I had the same problem in OSX, but I believe the solution is the same. I cannot post in the thread in the developer section yet, that is why this is here.
First, if you can't see your device in your device manager, make sure you have the latest HTC Device drivers installed or install the latest version of HTC Sync. This is very important for Windows 8.
Second, you will need to download and install the latest Android SDK. Just "Download From Other Platforms" and choose the appropriate SDK installation. You will need to run the SDK Manager.exe to install the latest tools. Note: ADB and Fastboot have been moved from the "tools" folder to "platform-tools".
Make sure your phone is in debugging mode by going into the Developer Options and choosing "Android debugging."
Find your SDK installation and make sure you are under "platform-tools" folder. You can ctrl-shift-right click on that folder to open a command prompt at that folder location. Saves you time.
Type in the command prompt:
Code:
adb devices
Your device should be listed and probably says Offline. This is normal. Take a look at your phone, you should get a prompt on your phone asking you if you trust the device that is trying to connect to it (this should be your computer). Allow it.
Type in the command prompt:
Code:
adb devices
This time, your device should be listed with the word "device" instead of offline.
To restart the daemon, type the following separately:
Code:
adb kill-server
adb start-server
This is the best I can do for everyone and it solved my problems with no further issues. I am not an expert and this is the only solution that has worked for me.

Thanks, this worked for me.

I did this in Windows 7 SP1 no problem. All I had to so was get the latest Android SDK and replace all the adb/fastboot files I already had and it worked no problems.
If you get permission denied when doing the last "adb shell" command, get adbd insecure from the forums here and run debugging mode insecurely from there.
Sent from my One X using xda app-developers app

Desertman123 said:
If you get permission denied when doing the last "adb shell" command, get adbd insecure from the forums here and run debugging mode insecurely from there.
Click to expand...
Click to collapse
I had this problem because SU was only allowing apps in CM10.1 (4.2.1). I found the solution by enabling the Dev Options via multiple clicks on the Build number until dev options was enabled, then changed Root access to Apps adn ADB.
FYI for anyone else that gets lost like I was.

ok so i can s-off now?

yes get some, 9 steps to s0ff

Ponarona said:
ok so i can s-off now?
Click to expand...
Click to collapse
Yes, you can use the HTC One XL link in the S-Off thread with no issues. I made this to help people with Win8 and trying to get their phones to appear properly in their device manager and to list it under adb devices.

If you get device offline, my issue, I was running android 4.2.2 but had an outdated adb. Just update adb if you still have problems

I know this is exceedingly random, but if you run a mac and can't see your device in adb, and in the past you tried sharing your phone internet with your mac via usb try running this:
sudo kextunload /System/Library/Extensions/EasyTetherUSBEthernet.kext
./adb kill-server
I need to do that before every adb session.
I'd be amazed someone actually has those conditions, but hey, it might help someone.
Sent from my HTC One X using xda app-developers app

[TOOL] Android ADB and Fastboot MSI installer with PATH variable

Description
After always having to search for the latest versions of Android's ADB and Fastboot tools instead of downloading the whole Android SDK for just 1 mb in a few files, I decided to make my own MSI installer using the latest versions of ADB and Fastboot.
You can install it wherever you want and it will work from any path in the command prompt. The installer will append the installation folder location to the system PATH variable, allowing you to run ADB or Fastboot without you having to change the command prompt path to where they are installed.
This installer is 32-bit and 64-bit compatible.
Usage
The default installation path is C:\ADB so you can easily add your flashable files in there.
After installing Android ADB Fastboot you can open a command prompt and type adb or fastboot commands right away, you don't need to change paths. Keep in mind that you need admin privileges, though.
To open a command prompt with administrator rights on Windows 8, just right click on the bottom left corner of the screen or use the Win+X shortcut and then click on Command Prompt (Admin).
Click to expand...
Click to collapse
If you have Windows 7 or Vista, the quickest way to do it is to type CMD on the Start Menu search box and press Ctrl+Shift+Enter instead of just pressing Enter.
Click to expand...
Click to collapse
Requisites
You need to have ADB Debugging under Developer Options on your device. You also need the drivers for every device you want to use with ADB installed and working.
You can type adb devices on a command prompt. If your device is listed, the drivers are working and good to go for ADB and Fastboot use.
Click to expand...
Click to collapse
Download
I will always check the ADB version whenever a new Android SDK is released and I will update my installer when needed.
The download link and screenshots are on my website.
http://rubenalamina.mx/custom-installers/android-adb-fastboot/
Latest version of the installer: 1.5 (ADB 1.0.36) updated on 2016.09.21

Thanks mate, it really help people with lacks internet connection like mine
Sent from my WT19i using xda app-developers app

Installer updated to version 1.2 with the new ADB and Fastboot included in Android SDK 23.0.2.

Installer updated to version 1.3 based on the Android SDK 24.0.2.

no matter what i do it stills says ABD is not reconizedf as an internal or external command. i even downloaded the whole stinking dev kit to make sure nothing missing in these little installers. made sure that a path was put still dose NOT work :/. and yes im running cmd prompt as adminastrator.

Nightmare-Rex420 said:
no matter what i do it stills says ABD is not reconizedf as an internal or external command. i even downloaded the whole stinking dev kit to make sure nothing missing in these little installers. made sure that a path was put still dose NOT work :/. and yes im running cmd prompt as adminastrator.
Click to expand...
Click to collapse
Have you tried running it from the C:\ADB path just in case? Maybe try PowerShell instead of the command prompt. I don't really know what else you can try if even the SDK is not working for you.

ajua said:
Have you tried running it from the C:\ADB path just in case? Maybe try PowerShell instead of the command prompt. I don't really know what else you can try if even the SDK is not working for you.
Click to expand...
Click to collapse
yes ive been trying both Shift open command prompt here, and aslso left click run as adminastrator and CD c:/abd both still says abd not reconized.

Nightmare-Rex420 said:
yes ive been trying both Shift open command prompt here, and aslso left click run as adminastrator and CD c:/abd both still says abd not reconized.
Click to expand...
Click to collapse
Try using PowerShell. Also, see if you are able to run the ADB that comes with the SDK but run it from the folder where it is located.

[how to] remove your "tampered" banner

*this thread is for E8. it will NOT work on m7(or anything older). search your device general forum for a specific thread
if you have recently s-off'ed using an exploit that did not remove your tampered banner from the bootloader screen,then this thread is for you.
*note: if you are on hboot 3.19.0.0000 this thread will change software status: modified banner to: software status: official. to my knowledge,this banner is not completely removable (more info)
you do NOT need to downgrade your hboot. this simple adb command works without any scary hboot downgrades.
*you must be s off.
*you must have superuser installed
read this:
this will not work if your s on
the usual disclaimers:
i have tested this my my m8_ul t mobile variant,but use this info at your own risk. if it melts your phone into a little pile of aluminum goo,its not my fault.
credits
-beaups for schooling me on echo command protocol
-andybones for testing it on m7_wlv
-WorldIRC and brar.arsh for testing on m8
-ian.anindya and a couple others have provided dumps. let me know and ill add you to the credits. if someone wants to provide screen shots,i can add those as well.
IF you are an advanced user with adb/fastboot set up and some basic knowlede of the cmd window,you can skip to #2
1)set up adb(windows 7 and lower)
-download this file
-install drivers: if you have htc sync installed,you should allready have drivers. if not,you can install htc sync,or install these modified htc drivers from revolutionary (driver mirror)
-unzip your miniadb_v1031.zip file. this is native funtionality in windows 7. you otherwise may need a utility such as "7-zip" to extract,or unzip it. place the unzipped folder onto the root of your C drive on your PC. root means the top level,not inside any folders. so just copy and paste,or drag and drop the folder onto C with everything else that is there. you may want to rename it to "miniadb_m7" since youll be putting some device specific files in here.
-open a command window. on windows 7,click the start bubble in the lower left and type "command" in the search box. xp i believe is similar or the same. doing this should open a small black command window.
-change to your miniadb_m7 directory. type the following at the prompt in your cmd window:
cd c:\miniadb_m7
your command promt should change to "c:miniadb_m7>" provided you: 1)unzipped the miniadb_v1031 zip file,and 2)put the folder on your c drive,and 3)entered the name of the folder correctly ("miniadb_m7" in this case)
-now make sure usb debugging is checked in developer options(you will need to turn it on first),and plug your phone into your PC with a usb cable
-make sure your phone is being recognized- type:
adb devices
if your drivers are installed correctly,this should return your phones serial number. you should hear the "found device" noises when you plug your phone in. if it starts installing drivers,wait for it to finish before typing the adb devices command.
if you get your serial number back,then enter this command:
adb reboot bootloader
this should take your phone to the "fastboot" screen,wich is white with colored letters. this is one mode of your bootloaders interactive modes. at the top youll see fastboot devices as confirmation youre in fastboot.
now enter:
fastboot devices
again,this should return your phones serial number. you should hear the "found device" noises when you plug your phone in. if it starts installing drivers,wait for it to finish before typing the adb devices command.
if you get your serial number back,you can enter the following to boot back to the phones OS:
fastboot reboot
and now,youve installed adb/fastboot and tested youre phones drivers. if at either spot,you have trouble and dont get your serial number back,there is some sort of connection issue. use these steps to troubleshoot:
troubleshooting connectivity issues:
-try a reboot of the PC
-try different usb cables and ports
-dont use a usb hub
-dont use usb 3.0
-make sure nothing capable of comunicating with the phone is enabled and running. htc sync,pdanet,easy tether,and even itunes have all been known to cause issues.
-windows 8 has been known to have issues. try a windows 7 or older machine
failing the above,
-i use these drivers for fastboot and adb(donwload and run as admin): http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe (mirror)
failing that,try manually updating the drivers in the following manner:
-put the phone in fastboot mode(select fastboot from the hboot menu)
-open device manager on the PC
-plug in phone,watch for it to pop up in device manager.
-update drivers with device manager,pointing the wizard to the extracted
driver download folder from above
note that you can check the connectivity of the phone,and make sure drivers are working by in the following manner:
-open cmd window. change to directory containing adb/fastboot utilities
-adb with the phone in the booted OS,usb debug enabled,enter:
adb devices in a cmd window
-fastboot with phone in fastboot,enter:
fastboot devices in cmd window
in either case,a properly connected phone with working drivers installed should report back the phones serial number.
Click to expand...
Click to collapse
this process,in your cmd window,should look something like this:
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Scott>[COLOR="red"]cd c:\miniadb_m7[/COLOR]
c:\miniadb_m7>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
FAxxxxxxxxxx device
c:\miniadb_m7>[COLOR="red"]adb reboot bootloader[/COLOR]
c:\miniadb_m7>[COLOR="red"]fastboot devices[/COLOR]
FAxxxxxxxxxx fastboot
c:\miniadb_m7>[COLOR="red"]fastboot reboot[/COLOR]
rebooting...
finished. total time: 0.037s
c:\miniadb_m7>
2)reset your "tampered flag"
enter the following:
adb devices
adb shell
su (if needed to get a # prompt)
echo -ne '\x00' | dd of=/dev/block/mmcblk0p6 bs=1 seek=5314564
(i would very strongly recomend you copy/paste this)
exit
(exit a second time if you need to to get back to a normal > prompt)
adb reboot bootloader
verify tamered is gone
your cmd window should look something(but not exactly) like this(red= my inputs,blue=additional comments):
Code:
c:\miniadb_m8>[COLOR="Red"]adb shell[/COLOR]
[email protected]_m8:/ $ su
su
[email protected]_m8:/ # [COLOR="red"]echo -ne '\x00' | dd of=/dev/block/mmcblk0p6 bs=1 seek=5314564[/COLOR]
ock/mmcblk0p6 bs=1 seek=5314564 <
1+0 records in [COLOR="Blue"][COLOR="red"]adb reboot bootloader[/COLOR]
c:\miniadb_m8>[COLOR="red"]fastboot reboot[/COLOR]
rebooting...
finished. total time: 0.022s
c:\miniadb_m8>
other useful threads:
lock/unlock without htcdev:
change mid without eng hboot: http://forum.xda-developers.com/one-e8/general/how-to-change-mid-eng-bootloader-t3019148
if this does not work for you
*first reread this thread in its entirety. make sure you have met the prerequisites,and double check your code and make sure you have not forgotten a step,or screwed something up trying to type it (especially if using a terminal emulator),and check that you have not gotten any errors.
if youre still confident you did things correctly,you need to PM me:
1)the results of: fastboot getvar all
2)a link to an uploaded p6.
you get fastboot getvar all by:
-place phone in fastboot
-enter in fastboot getvar all right click,click mark,highlight in white,hit enter or right click to copy
you dump p6 by:
adb shell
su (if needed to get a #)
dd if=/dev/block/mmcblk0p6 of=/sdcard/mmcblk0p6
transfer the file on internal storage to your pc and upload it
im not trying to be a ****,but its not helpful to post "didnt work" if you screwed something up,or if your not willing to help find a solution. especially if others have found it to work on their same variant.
important:
from now on,i will need a copy of your cmd window as well if we want to get to the bottom of whats happening. some folks seem to be simply writing extra bytes,wich is screwing up the flag location. please make sure this shows an entire session,not just a last part where it looks correct. we cant figure it out if you only show part of what you did.

mine

Working like a Bomb

Many thanks. Works like a charm.

thank you sir, it works on M8Sd MEC_DWGL :good:

Works on the M8sd Indian version HBOOT 3.19.0.0000
Sent from my HTC One_E8 dual sim

how can we remove tampered banner when device is s-on please help me

eminteoman said:
how can we remove tampered banner when device is s-on please help me
Click to expand...
Click to collapse
The only way is to run a signed ruu that meets all the phone's s on criteria

scotty1223 said:
The only way is to run a signed ruu that meets all the phone's s on criteria
Click to expand...
Click to collapse
Can you explain a little further? I really couldn't understand

eminteoman said:
Can you explain a little further? I really couldn't understand
Click to expand...
Click to collapse
Easy way: s-on can't get rid of the text
Send via my CM 12 Gtab3

wildanw2 said:
thank you sir, it works on M8Sd MEC_DWGL :good:
Click to expand...
Click to collapse
Does it works on m8sx??