Database Info

[Flashing Rom] Just making sure I have everything I need.

Rather than dive head first in to a situation I can't get myself out of, I'm going to make sure I have everything I need before I begin. I have not received my Htc One x yet, but assuming it comes with 1.85, I follow these steps.
Device setup (hopefully):
Device: Att Htc One X
Filmware version: 1.85
Step one: Root
Following these steps... Edit: http://forum.xda-developers.com/show....php?t=1709296
Quote from iElvis: DO NOT use the one-click method as this can update you to 2.20 if you goof it up, and then you're stuck until there's a new exploit.
Step two: Unlock bootloader
Following these steps... http://briefmobile.com/how-to-unlock-att-one-x-bootloader (from download link here: http://forum.xda-developers.com/showthread.php?t=1672284)
Step 3: Flashing preferred Rom -NOT INTERNATIONAL VERSIONS OF ROMS-:
I have selected Nocturnal Limited Edition... http://forum.xda-developers.com/showthread.php?t=1816853
Following these steps...
How to Flash
Download Rom.zip and save to phone storage
boot into recovery
wipe system
wipe data if coming from another rom
wipe cache
go to flash rom
select the proper download
follow the options in the Aroma installer
Reboot & Enjoy
Some questions before attempting:
"boot into recovery" Meaning I use Twrp2 (from download link here: http://forum.xda-developers.com/showthread.php?t=1677447)
"Wipe system/data/cache" I assume thats done via recovery (Twrp2) correct?
"go to flash rom, select proper download" I assume thats similar to clockwordmod, where you find the Rom on your sdcard (in this case, phone storage) and select it.
"follow options in the Aroma installer" follow instructions in the installer... simple enough.
Is there anything I missed? Devil's in the details.
Edit (more questions): In the following thread ( http://forum.xda-developers.com/showthread.php?t=1709296) it says "Put su in same directory as ADB. Get to adb command prompt and cd into that directory"
Put su (superuser) in same directory as ADB, means that you put Superuser in the same folder as ADB, right?
and cd into that directory. What does this mean?

A cool username said:
Filmware version: 1.85
Step one: Root
Following these steps... http://briefmobile.com/how-to-root-htc-one-x-att (from download link here: http://forum.xda-developers.com/showthread.php?t=1644167)
Click to expand...
Click to collapse
That's the wrong root procedure for 1.85. You need this one:
http://forum.xda-developers.com/showthread.php?t=1709296
DO NOT use the one-click method as this can update you to 2.20 if you goof it up, and then you're stuck until there's a new exploit.

I tried to do this using that post but found it confusing and had some trouble with it. I prefer onexroot.com. they have a great guide here http://onexroot.com/one-x-root/root-any-htc-one-x-windowsmaclinuxattinternationalone-click-method/ hope this helps!
Sent from my HTC One X using xda premium

A cool username said:
Edit (more questions): In the following thread ( http://forum.xda-developers.com/showthread.php?t=1709296) it says "Put su in same directory as ADB. Get to adb command prompt and cd into that directory"
Put su (superuser) in same directory as ADB, means that you put Superuser in the same folder as ADB, right?
and cd into that directory. What does this mean?
Click to expand...
Click to collapse
cd means change directory. It is a windows command prompt command. So you would type "cd C:\adb" if that was where your adb folder was. Folder and directory can be used interchangeably, although directory is more "correct". We only say folder because GUIs use folders to represent directories.

A cool username said:
Rather than dive head first in to a situation I can't get myself out of, I'm going to make sure I have everything I need before I begin. I have not received my Htc One x yet, but assuming it comes with 1.85, I follow these steps.
Device setup (hopefully):
Device: Att Htc One X
Filmware version: 1.85
Step one: Root
Following these steps... Edit: http://forum.xda-developers.com/show....php?t=1709296
Quote from iElvis: DO NOT use the one-click method as this can update you to 2.20 if you goof it up, and then you're stuck until there's a new exploit.
Step two: Unlock bootloader
Following these steps... http://briefmobile.com/how-to-unlock-att-one-x-bootloader (from download link here: http://forum.xda-developers.com/showthread.php?t=1672284)
Step 3: Flashing preferred Rom -NOT INTERNATIONAL VERSIONS OF ROMS-:
I have selected Nocturnal Limited Edition... http://forum.xda-developers.com/showthread.php?t=1816853
Following these steps...
How to Flash
Download Rom.zip and save to phone storage
boot into recovery
wipe system
wipe data if coming from another rom
wipe cache
go to flash rom
select the proper download
follow the options in the Aroma installer
Reboot & Enjoy
Some questions before attempting:
"boot into recovery" Meaning I use Twrp2 (from download link here: http://forum.xda-developers.com/showthread.php?t=1677447)
"Wipe system/data/cache" I assume thats done via recovery (Twrp2) correct?
"go to flash rom, select proper download" I assume thats similar to clockwordmod, where you find the Rom on your sdcard (in this case, phone storage) and select it.
"follow options in the Aroma installer" follow instructions in the installer... simple enough.
Is there anything I missed? Devil's in the details.
Edit (more questions): In the following thread ( http://forum.xda-developers.com/showthread.php?t=1709296) it says "Put su in same directory as ADB. Get to adb command prompt and cd into that directory"
Put su (superuser) in same directory as ADB, means that you put Superuser in the same folder as ADB, right?
and cd into that directory. What does this mean?
Click to expand...
Click to collapse
Did you end up getting root and unlock bootloader to work?

smartnphone said:
Did you end up getting root and unlock bootloader to work?
Click to expand...
Click to collapse
I'm not trying to be rude, but as stated in my opening post, first paragraph. I don't have my one x yet, I am just making sure I have everything before I get my one x so that way I don't have to worry about it.

Bump. Might get my One X today! (^_^)
Will keep updated on what happens

I really hope you find a rootable one.

gunnyman said:
I really hope you find a rootable one.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1842670
Me too. Me too....

It's 1.85!
Sent from my HTC One X using xda app-developers app

Dang.... I cant get the Spoof-Cid to work. Every time I try it says...
Restarting ADB
Pulling files
Checking files
Couldn't pull files from device. Your device was not altered.
Press any key to continue . . .
I'm rooted (checked with terminal emulator) and usd debugging is ON. Set to charge only. No matter what I try, its not working.

A cool username said:
Dang.... I cant get the Spoof-Cid to work. Every time I try it says...
Restarting ADB
Pulling files
Checking files
Couldn't pull files from device. Your device was not altered.
Press any key to continue . . .
I'm rooted (checked with terminal emulator) and usd debugging is ON. Set to charge only. No matter what I try, its not working.
Click to expand...
Click to collapse
Try rebooting your phone... worked for me!
Sent from my SGH-I777 using Tapatalk 2

C3RGIOSE1 said:
Try rebooting your phone... worked for me!
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
I will reboot.... AS MANY TIMES AS IT TAKES!!! -Determined-

A cool username said:
I will reboot.... AS MANY TIMES AS IT TAKES!!! -Determined-
Click to expand...
Click to collapse
Also make sure you use USB 2.0 and not front ports, but main ones on the back, if using desktop :thumbup:
Sent from my SGH-I777 using Tapatalk 2

C3RGIOSE1 said:
Also make sure you use USB 2.0 and not front ports, but main ones on the back, if using desktop :thumbup:
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
its not working (-_-) i have rebooted 5+ times and it wont do it.

A cool username said:
its not working (-_-) i have rebooted 5+ times and it wont do it.
Click to expand...
Click to collapse
I'm going to do mine Super CID on my X, see how it goes... I'll follow up
Sent from my SGH-I777 using Tapatalk 2

C3RGIOSE1 said:
I'm going to do mine Super CID on my X, see how it goes... I'll follow up
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
Thankyou so much. In the meantime I will start from square one and see if that works afterwords

A cool username said:
its not working (-_-) i have rebooted 5+ times and it wont do it.
Click to expand...
Click to collapse
Just did my SuperCID - and successfully unlocked BL....I just followed one-click by kennethpenn... where exactly do you get stuck? USB debugging enabled?
Sent from my SGH-I777 using Tapatalk 2

Step by step what I do.
Rooted: achieved. (checked via terminal emulator)
Next I connect my one x via usb, download the supercid file, extract it, run the file, get to where it wants me to press any button, I press any button, it then says it can't get the files and that my device is unchanged, then it closes out of the file. And that's where I'm stuck.
Any questions? At this point I'm thinking I'm missing something incredibly simple...
Sent from my HTC One X using xda app-developers app

Connect phone to computer. Open command prompt. Type adb devices. Does the phone show up ?

[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

[Q] Froze velvet.apk

So, I did something really stupid. While trying to freeze unnecessary aps, I froze the velvet.apk Which I think is part of the launcher in 4.4.2. After that the phone gets stuck at the boot-up screen (specifically at the four colored circles) and nothing ever happens.
So, I found that there's a command I can use to unfreeze apks: "pm enable velvet.apk"
But I need someone to teach me where and how to use it. The phone doesn't boot up and when I connected to fastboot and used "adb shell su" I got a "device not found error" I already had drivers installed to root phone!
Any quick answer is definitely appreciated!

nivakis said:
So, I did something really stupid. While trying to freeze unnecessary aps, I froze the velvet.apk Which I think is part of the launcher in 4.4.2. After that the phone gets stuck at the boot-up screen (specifically at the four colored circles) and nothing ever happens.
So, I found that there's a command I can use to unfreeze apks: "pm enable velvet.apk"
But I need someone to teach me where and how to use it. The phone doesn't boot up and when I connected to fastboot and used "adb shell su" I got a "device not found error" I already had drivers installed to root phone!
Any quick answer is definitely appreciated!
Click to expand...
Click to collapse
A could of things, you can't use adb commands in fastboot. You need to use fastboot commands. A little more brute force then you're looking for but,
fastboot flash system system.img will solve the problem. System.img is from the factory image
Sent from my Nexus 5

jd1639 said:
A could of things, you can't use adb commands in fastboot. You need to use fastboot commands. A little more brute force then you're looking for but,
fastboot flash system system.img will solve the problem. System.img is from the factory image
Sent from my Nexus 5
Click to expand...
Click to collapse
Well, it could work but remember that I didn't uninstall the app, I just froze it, so I guess flashing the partition wouldn't do much good because info on frozen apps are stored elsewhere, right?
EDIT:
Is there a way to push via fastboot another velvet.apk or launcher, just to boot the phone and fix the problem?

nivakis said:
Well, it could work but remember that I didn't uninstall the app, I just froze it, so I guess flashing the partition wouldn't do much good because info on frozen apps are stored elsewhere, right?
EDIT:
Is there a way to push via fastboot another velvet.apk or launcher, just to boot the phone and fix the problem?
Click to expand...
Click to collapse
I wasn't familiar with the pm command but it looks like if you boot into recovery and then do
adb shell
pm enable /system/priv-app/velvet.apk
it should work
Edit, I'm getting a pm not found error
The other option would be to adb push the apk
Sent from my SAMSUNG-SGH-I727

jd1639 said:
I wasn't familiar with the pm command but it looks like if you boot into recovery and then do
adb shell
pm enable /system/priv-app/velvet.apk
it should work
Sent from my SAMSUNG-SGH-I727
Click to expand...
Click to collapse
So the million dollar question is, since I don't have any recoveries installed, is there a recovery that includes a terminal to try this command?

nivakis said:
So the million dollar question is, since I don't have any recoveries installed, is there a recovery that includes a terminal to try this command?
Click to expand...
Click to collapse
Well, the two million dollar question is, is your bootloader unlocked?
Sent from my SAMSUNG-SGH-I727

jd1639 said:
Well, the two million dollar question is, is your bootloader unlocked?
Sent from my SAMSUNG-SGH-I727
Click to expand...
Click to collapse
Well, in order to root using CF-auto-root, it was needed to unlock the bootloader, so, yes!

nivakis said:
Well, in order to root using CF-auto-root, it was needed to unlock the bootloader, so, yes!
Click to expand...
Click to collapse
Good. Download twrp recovery from http://d-h.st/nbu and put it in the same folder as fastboot.exe is in. Boot into the bootloader then type
fastboot flash recovery recovery-2.6.3.4.img in a cmd window opened in the same folder a fastboot.exe is on
Sent from my Nexus 5

jd1639 said:
Good. Download twrp recovery from http://d-h.st/nbu and put it in the same folder as fastboot.exe is in. Boot into the bootloader then type
fastboot flash recovery recovery-2.6.3.4.img in a cmd window opened in the same folder a fastboot.exe is on
Sent from my Nexus 5
Click to expand...
Click to collapse
I think you meant "fastboot"
good, now I am into Team Win Recovery Project. I push: Advanced > Terminal Command and it asks to select a starting folder. Which should I choose? If I don't choose the correct one, when I type adb shell, it says:
/ # adb shell
sh:
adb: not found

nivakis said:
I think you meant "fastboot"
good, now I am into Team Win Recovery Project. I push: Advanced > Terminal Command and it asks to select a starting folder. Which should I choose? If I don't choose the correct one, when I type adb shell, it says:
/ # adb shell
sh:
adb: not found
Click to expand...
Click to collapse
You don't need the terminal in twrp. You just needed a recovery that allows you to use adb commands from your computer. Leave your device in twrp and then open a command window on your pc. Run the commands from there
Sent from my Nexus 5

jd1639 said:
You don't need the terminal in twrp. You just needed a recovery that allows you to use adb commands from your computer. Leave your device in twrp and then open a command window on your pc. Run the commands from there
Sent from my Nexus 5
Click to expand...
Click to collapse
Drivers for "AOSP on Hammerhead"?
EDIT:
Scratch that. I found them and I am about to try the commands
EDIT 2:
Grrrr, I get a /sbin/sh: pm: not found
I tried downloading the Android SDK manager but can't get over this...

Well, I finally fixed it! Thank you jd1639, you've been VERY helpful.
To sum it up, after failing with the adb commands, I used the file browser at the recovery to copy the frozen velvet.apk to system/app. Then I booted my phone and while it was stuck at the booting animation, I called my phone and that gave me access to the taskbar. Then I unfroze the original velvet.apk in /system/priv-app and deleted the one in /system/app
I'll be sure to double-check what I freeze next time!

nivakis said:
Well, I finally fixed it! Thank you jd1639, you've been VERY helpful.
To sum it up, after failing with the adb commands, I used the file browser at the recovery to copy the frozen velvet.apk to system/app. Then I booted my phone and while it was stuck at the booting animation, I called my phone and that gave me access to the taskbar. Then I unfroze the original velvet.apk in /system/priv-app and deleted the one in /system/app
I'll be sure to double-check what I freeze next time!
Click to expand...
Click to collapse
Glad you got it fixed. Pretty clever way to do it
Sent from my Nexus 5

jd1639 said:
Glad you got it fixed. Pretty clever way to do it
Sent from my Nexus 5
Click to expand...
Click to collapse
Well I am told to be resourceful when needed! But I couldn't have done it without your help!

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...

Does Anyone Understand How To Do This?! (I NEED HELP)

Hello. I am trying to use rootmyvalet.apk to root my phone. I am extremely confused on how to do this.
Here are the steps on how to do it...
The Second way (app way):
1)Push the su binary to /data/local/tmp using adb push su /data/local/tmp
2)Push the roothandler binary to /data/local/tmp using adb push roothandler /data/local/tmp
3)Set the roothandler binary permission using adb shell chmod 0755 /data/local/tmp/roothandler
4)Push the installsu.sh script to /data/local/tmp using adb push installsu.sh /data/local/tmp
5)Set the installsu.sh script the execution permission using adb shell chmod 0755 /data/local/tmp/installsu.sh
6)Install the APK using adb install RootMyValet.apk. If that does not work then type the full path to the apk. E.G. adb install /path/to/apk/app.apk
Start the app on the device, hit the button that says "Push SU Binary"
Wait about a minute
Enjoy your root!
If root fails, try rebooting the device

Which of the steps have you taken so far? Where did you get to in that list?

KodyChristianson said:
Which of the steps have you taken so far? Where did you get to in that list?
Click to expand...
Click to collapse
Sadly enough, I am stuck on step one. I'm probably going to need help on every single step.

Do you have windows drivers working with the device? ie, does it show up when you run:
adb devices
if so, what happens when you run:
adb push su /data/local/tmp
Also,
I've noticed a sticky here which may be of help to you. [GUIDE][30/10/2013]New To Adb And Fastboot Guide by Ricky Divjakovski

KodyChristianson said:
Do you have windows drivers working with the device? ie, does it show up when you run:
adb devices
if so, what happens when you run:
adb push su /data/local/tmp
Also,
I've noticed a sticky here which may be of help to you. [GUIDE][30/10/2013]New To Adb And Fastboot Guide by Ricky Divjakovski
Click to expand...
Click to collapse
1) To install the drivers, I use connect to PC right?
2) To run the command adb push su /data/local/tmp , do I use command prompt?

Use the "package" which is at the start of the guide linked above.

KodyChristianson said:
Use the "package" which is at the start of the guide linked above.
Click to expand...
Click to collapse
I also have a command terminal on my phone, is there any way i can do this from there? Because at the moment, i do not have a usb cable to connect my phone to my computer. I have all of the files i need already on my phone. I just need to move them to the proper directory.

CurtisNHL1 said:
I also have a command terminal on my phone, is there any way i can do this from there? Because at the moment, i do not have a usb cable to connect my phone to my computer. I have all of the files i need already on my phone. I just need to move them to the proper directory.
Click to expand...
Click to collapse
Yeah, i guess you could move the files using a filemanager app, just search it in the playstore.
The problem is, if something goes wrong, for example you get stuck in a boot loop, you will need the computer to resolve the problem.
If that happens, you want to be sure that you have all the drivers installed and properly working.
Imagine having your phone not working, you can´t get the computer to talk to the phone, and you don´t know whether the problem is adb, your drivers, or your phone.
If you want to follow those instructions, i think you should get a cable and follow them exactly.
Why do you want to use that rootkit, anyway? what phone do you have?

KodyChristianson said:
Yeah, i guess you could move the files using a filemanager app, just search it in the playstore.
The problem is, if something goes wrong, for example you get stuck in a boot loop, you will need the computer to resolve the problem.
If that happens, you want to be sure that you have all the drivers installed and properly working.
Imagine having your phone not working, you can´t get the computer to talk to the phone, and you don´t know whether the problem is adb, your drivers, or your phone.
If you want to follow those instructions, i think you should get a cable and follow them exactly.
Why do you want to use that rootkit, anyway? what phone do you have?
Click to expand...
Click to collapse
I have the zte valet z665c tracfone. This is the last option i have to root my phone. I've tried everything i can.

CurtisNHL1 said:
I have the zte valet z665c tracfone. This is the last option i have to root my phone. I've tried everything i can.
Click to expand...
Click to collapse
The problem is, if something goes wrong, for example you get stuck in a boot loop, you will need the computer to resolve the problem.
If that happens, you want to be sure that you have all the drivers installed and properly working.
Imagine having your phone not working, you can´t get the computer to talk to the phone, and you don´t know whether the problem is adb, your drivers, or your phone.

KodyChristianson said:
The problem is, if something goes wrong, for example you get stuck in a boot loop, you will need the computer to resolve the problem.
If that happens, you want to be sure that you have all the drivers installed and properly working.
Imagine having your phone not working, you can´t get the computer to talk to the phone, and you don´t know whether the problem is adb, your drivers, or your phone.
Click to expand...
Click to collapse
Believe it or not, the information you told me here just saved my ass. I recently bought a phone that could be rooted and got it stuck in a boot loop. Thank you so much!