Database Info

[Q] Recovery Mode inexistant

Okay, so I posted about a week ago re: my softkey issue and fortunately that was fixed by returning my phone to stock, however, I followed nexushacks method and when it told to do this:
Step 12. Once you get the Android guy with exclamation mark, hit Volume Up and Power button at the same time until you get blue menus.
Nothing bloody happens. Please don't tell me I have to hold it for something like 60 seconds because I. Will. Rage. Lol.
When I try to go into recovery I get that symbol and can't do anything but batt pull. I'm still unlocked and rooted, to my knowledge.
I downloaded ROM Manager because I wanted to flash a recovery on it but it told me that "An error occurred while attempting to run privileged commands"
It also says this when I open Rom Manager "You must root your phone for ROM Manager to function. Superuser was not found at "/xbin/su" or "/system/xbin/su". Use google blabla"
I'm also in the process of trying a command prompt on windows but it keeps giving me the "waiting for device" or awaiting a responce from device" whatever that message is...
Trying to give as info as possible so someone can help a brother out.
I can't deal with this Stock OEM crap anymore *twitch*
Thanks!

Herp Derp
Okay, I didn't realize it was Press the Power button, then the volume up button.
Silly noobs.
So my question, is there a way to get Clockwork Recovery back on now or do I have to go through the whole "Rooting" process again?

I assume you see a lock symbol while booting. This means you're unlocked. Now you'll just need to use fastboot to flash a custom recovery (namely, CWM). NexusShacks details how to setup and use fastboot and i think they provide TWRP now, feel free to use this or just download CWM from here and flash that .img file instead.
After this, download the latest Superuser-3.0.7-efghi-signed.zip and flash that. Note that on a stock ROM it will flash stock recovery on every boot. To change this, rename /system/etc/install-recovery.sh to something else.

But how do I flash a .img file when I don't have Recovery mode?
Or can I use do that through the OEM Recovery (blue screen)?

You flash it with fastboot. Fastboot is a command line tool to flash various images through the bootloader screen. To enter the bootloader, turn off the device and hold Vol. Up + Power. This is the same place you would've typed "fastboot oem unlock", except to flash the new recovery you'll be typing something along the lines of "fastboot flash recovery recovery.img". NexusSHacks teaches you how to do all of this.

Ah sorry, I still get Fastboot and Bootloader mixed up.
Only problem is that I don't know if my computer is recognizing my device when I plug it in through Bootloader.
As mentioned in my original post
"I'm also in the process of trying a command prompt on windows but it keeps giving me the "waiting for device" or awaiting a response from device" whatever that message is..."

I'm at work now and trying to figure out how to do this using Terminal on my mac.
When I type in "cd /nexussrootICS" it keeps on telling me "no such file or directory"
Do I need to put this file in a specific folder? I got this step working on my PC at home but it told me "Waiting for device" the whole time.
Any thoughts?

I'm not particularly familiar with OS X so forgive anything i say that might be off target.
You need to direct the terminal to the relative OR absolute directory of that folder. A relative directory can be done by "cd ./blah", while an absolute will be done by "cd /blah". This is quite confusing for people who aren't used to command line, but very simple once you've done it a few times.
Easiest way aside from magical OS X shortcuts i don't know about is:
-Unzip the files to a "nexus" folder on the desktop, making sure the adb files are in this nexus folder and not a sub folder
-open terminal
-"cd /user/artist/desktop/nexus" or whatever the FULL PATH to the folder is. You should be able to see this through the folders properties or in the file explorer.
-Now you are in the folder, you can use adb and fastboot by just typing those words
I believe OS X can recognise the device straight away so you shouldn't need to install any drivers - at least my linux distros were like that. Installing drivers on Windows is detailed in the video, too.

Ah!!!! I feel like I'm so bloody close...
Okay that part worked perfectly, I found out how to at least direct Terminal to the right location but now I'm lost again...
It's giving me this
"
USER-iMac:nexus user$ ./fastboot-mac flash recovery-clockwork-5.0.2.0-crespo.img
unknown partition 'recovery-clockwork-5.0.2.0-crespo.img'
error: cannot determine image filename for 'recovery-clockwork-5.0.2.0-crespo.img'
USER-iMac:nexus user$
"

TheArtist8 said:
Ah!!!! I feel like I'm so bloody close...
Okay that part worked perfectly, I found out how to at least direct Terminal to the right location but now I'm lost again...
It's giving me this
"
USER-iMac:nexus user$ ./fastboot-mac flash recovery-clockwork-5.0.2.0-crespo.img
unknown partition 'recovery-clockwork-5.0.2.0-crespo.img'
error: cannot determine image filename for 'recovery-clockwork-5.0.2.0-crespo.img'
USER-iMac:nexus user$
"
Click to expand...
Click to collapse
The command should be
./fastboot-mac flash recovery recovery-clockwork-5.0.2.0-crespo.img
You were missing the recovery flag in the command.
Sent from my Nexus S 4G using Tapatalk 2

Also do "man fastboot-mac" in terminal to show all its options.
Sent from my Nexus S 4G using Tapatalk 2

Son of a... alright ill try after my lunch.
Sent from my Nexus S using XDA

Omfg I love you guys.
Thanks so much
I just got into Recovery mode, now on to Cyber-GR

[INFO] Downgrading firmware

Before I start, you do this at your OWN RISK!
For this to work you need to have ADB and an understanding of how to use it and you need root privileges (although I didn't test this). You also need a hex editor of some sort like HxD.
Ok, enough of that. Here goes:
1. Go to the directory that you have adb in.
2. Plug your device in and make sure that debugging is enabled.
3. Type "adb shell" and hit enter.
4. Once at the shell prompt type "su" and hit enter.
5. Then type "dd if=/dev/block/mmcblk0p23 of=/sdcard/misc" and hit enter. It should say "blah records in, blah records out, blah in blah seconds . This will put a file on your "sdcard" that you will need to edit.
6. Next type "exit" and hit enter. Type "exit" and hit enter again.
7. Type "adb pull /sdcard/misc"
8. Now, open your hex editor and browse to the directory that adb is in. Open the misc file that you just pulled from your device.
9. Look for offset 000000A0. It should have 1.xx.xxx.x or something like that.
10. Change this to 1.00.000.0 and save the file as miscMOD.
11. Go back to your command prompt and adb directory. Type "adb push miscMOD /sdcard/miscMOD" and hit enter.
12. Now go back to the android shell. Type "adb shell" and hit enter then type "su" and hit enter again.
13. Now type "dd if=/sdcard/miscMOD of=/dev/block/mmcblk0p23" and hit enter. It should say "blah records in, blah records out, blah in blah seconds . This will overwrite the misc partition with your edited file and effectively tell it that it is version 1.00.000.0.
14. To make sure that this worked you can restart the phone, go to settings, about phone, and software information. Software number should say 1.00.000.0.
15. You can now downgrade your software via RUU.
Enjoy!

easier than expected ... tks for the writeup...

Cheers!!! hope this works for the Rogers HOX

edit will post back shortly

wow! nice to see this.Thanks for your contribution .

Probably not the place for this, but just saw this on JCase twitter feed:
Justin Case ‏@TeamAndIRC
If you are stuck on the 1.85.x.x firmware for the HTC One X (AT&T), have ADB setup, and are fairly confident hit me up
Collapse
Reply
Retweet
Favorite
12:54 PM - 24 May 12 via TweetDeck · Details

Great write up, this will help a lot of people

No go for me. Software number stayed the same.

akvtiger said:
No go for me. Software number stayed the same.
Click to expand...
Click to collapse
Were you trying to do it as root?

grankin01 said:
Were you trying to do it as root?
Click to expand...
Click to collapse
Correct as root. I did another pull and can confirm that change is there. It's just not showing up under Software number.

This process may be made obsolete. Have you tried the bootloader unlock yet. That was the only reason the I even tried to downgrade but I don't think it will affect the way I did the other process at all.

This does not work for some reason. The file was pushed correctly. I pull it back down and the hex was changed to show 1.0.000.0. However, the software still stays 1.82. Any ideas? I also tried using the complete file path to include the two other sub dicrectories /dev/block/platform/msm_sdcc.1. This made no difference as well.

The number should be in this format: 1.00.000.0
That may be your problem.

I have not tried to bootloader unlock. I was just trying to get it back to stock.

akvtiger said:
Correct as root. I did another pull and can confirm that change is there. It's just not showing up under Software number.
Click to expand...
Click to collapse
Same thing for me earlier
Sent from my HTC One X using XDA

That's a typo from me. How do you downgrade even if you unlock the bootloader?

I would say you still need to make it think the main version is lower than the RUU version. I'm not exactly sure what is going wrong with your. :O

odd, this didn't work when I was testing out the first leak and trying to downgrade to the shipped ruu.

Ok two things I figured out. First you need to put your CID back to CWS rather than Rogers. Or use superCID . This fixed my problem. Also if you follow the directions here you dint need to check the software version. Just ADB reboot bootloader and run RUU . It will tell you there which revision you are on. I went from 1.82 to 1.73.

At the top of my "misc" file in my hex editor it says;
CWS__001..
--
Or however many periods. I already unlocked my bootloader [changed to SuperCID(11111111)] so I found that odd that it remained CWS and not 111.
Anywho, I just unlocked my BL and ran the 1.73 [shipping RUU] installer to hopefully downgrade. It went as far as to the "waiting for bootloader" message on the 1.73 installer then displayed an error. I'm not really in the mood to mess around with it, But I'm just sharing my results here. The CWS at the top of my copied over "misc" file still seems odd..

[Information/Guides] UK One XL Thread - Mod please read and sticky

MODS
Friendly requesting this thread gets stickied to help all the UK OneXL users
Tmobile/Orange/EE have released a UK version of the One XL for us so that users on the EE network can get 4g
Specs of the phone are identical to the US version of the One XL featuring a Dual Core S4 chip only our phone has 32gb of internal storage and not 16gb of internal storage like the US version (Telstra One XL also has 32gb storage)
The main purpose of this thread is to help the lost users of the UK One XL by providing all the information needed to get the ball rolling when it comes to flashing cutom roms as I see many posts in both the rogers forums (here) and in the normal One X forum all asking how to do this and that when its really simple
Now, our phone is the Evita which basically means everything here in this forum should be compatible with our phones. Our phone is basically after all the American One XL we just have 32gb storage no other differences
Bootloader Unlocking
Unlocking the bootloader on the UK One XL is very simple, just go to http://www.htcdev.com/ and follow the instructions, when choosing the device choose "All other supported models" from the dropdown box and follow the rest of HTC's instructions
Please remember that this method of unlocking the bootloader will wipe all your data so make a back-up of everything important first
Also my attached zip will work for all commands needed to do the HTC bootloader unlocking process so feel free to use it instead of downloading all the files from HTC
SuperCID
Now first of all I don't see any need for SuperCID for us at the moment but who knows that might change later on when it comes to S-Off so heres how to do it anyway (you can use copy and paste on Windows instead of typing each command below into your command prompt)
You will need a hex editor and adb installed for this to work or a hex editor and my attached zip
1. Fire up your command prompt and go to the directory that you have ADB installed to (or alternatively just download the attached zip and place it in the your C: drive then just click CMD inside the ADB folder that's created). Type "adb shell" and hit enter.
2. Type "su" and hit enter. You now have root privileges.
3. Next type "dd if=/dev/block/mmcblk0p4 of=/sdcard/mmcblk0p4" and hit enter. This will dump the partition to your sdcard.
4. Next type "exit", hit enter, type "exit", and hit enter again. This should take you back to a command prompt for your computer.
5. type "adb pull /sdcard/mmcblk0p4" and hit enter. NOTE THE SIZE OF THE FILE BEFORE THE NEXT STEP!
6. Open the file (mmcblk0p4) with your hex editor.
7. Look for offset 00000210 (There is a chance the offset may be 00000214) and you should see ORANG001 with your IMEI number attached to it. (As far as im aware all UK HTC One XL's will have this cid, if not please let me know)
8. Change ORANG001 to 11111111 and save the file as mmcblk0p4MOD. MAKE SURE AT THIS POINT THAT THE FILE IS THE EXACT SIZE IT WAS BEFORE YOU HEX EDITED IT!
9. Now go back to your command prompt and type "adb push mmcblk0p4MOD /sdcard/mmcblk0p4MOD" and hit enter.
10. Type "adb shell" and hit enter then type "su" and hit enter again. This will put you back into the android shell and give you root privileges.
11. Type "dd if=/sdcard/mmcblk0p4MOD of=/dev/block/mmcblk0p4" and hit enter. To test if it worked restart the phone into fastboot (type "adb reboot bootloader" and hit enter) and once the bootloader screen comes up type "fastboot oem readcid" and hit enter. It should read "11111111".
Done - Your phone now has SuperCID
Thanks goes to grankin01 for the original SuperCID guide
Flashing a recovery
ADB is needed to flash a recovery or use my attached zip
Simply open up the command prompt and type: fastboot flash recovery recovery.img
"recovery.img" will be the name of your recovery
Recommended recovery:
TWRP - XDA Forum Link
Always make sure to use the Evita recovery not the recovery for the international One X
Flashing a rom
This one is pretty simple and I expact we all know already anyway
Go have a look at the One X Development Section here: http://forum.xda-developers.com/forumdisplay.php?f=1541
Download your favourite rom zip and place it on the root of your sd card
Simply open up TWRP and install it by choosing the zip after clicking install
Help! Rom's not booting!
So you followed all my above steps and now the new roms not booting? Don't panic its ok
This is probably because you need to manually flash the boot.img to get the phone to boot
Simply open up the zip of the rom you are using and extract "boot.img" to your ADB directory or the adb directly supplied in my attached zip and type:
fastboot flash boot boot.img
Now your phone should boot
Anymore problems don't hesitate to ask on here
Now my little bit of fun
I recommend the excellent ViperXL rom found here: http://forum.xda-developers.com/showthread.php?t=1868236
Excellent stable rom based on the latest HTC rom and has 100's of useful tweaks to make your phone look and perform just how you want it to
And if running the ViperXL rom I recommend you check out my theme here: http://forum.xda-developers.com/showthread.php?t=2016695
Thousands of images have been changed to make the rom more colourful and look more "finished" and more pleasing to the eye
.

[HOW-TO] Unlock and Root Moto G via Recovery/SuperSU

Unlocking the Bootloader is Required! This will erase all data and void your warranty!
Since all data will be wiped it's best to do this immediately after getting the phone. At least unlocking the bootloader.
I won't add a disclaimer, because if you trust some guide from some guy on the internet you should know what that means without being told explicitly.
For me the bootimage method posted on Modaco does not work and apparently others seem to have trouble as well (see the poll at Modaco). And since I couldn't find any guide here on XDA I thought I'd write one. XDA helped me a lot when I got my DHD, so maybe now I can help back.
This is based on soyd's guide at swedroid.se which I used to finally get my phone rooted after some unsuccessful attempts.
The guide is for Windows, but could probably be easily adapted to Linux/Mac by using the appropriate drivers/tools. I followed these steps to successfully root my Moto G (16 GB, german retail, Android 4.4.2, OTA 176.44.1).
Here're the neccessary steps:
Install Motorola and ADB Drivers
Unlock Bootloader
Flash Recovery
Flash SuperSU
Enjoy
Install Motorola and ADB Drivers
Do not connect your phone to your PC just yet.
If you already have ADB drivers and Motorola drivers installed, just skip this step.
Download these files:
Motorola Drivers
ADB Tools (thx to androidpit.info)
mfastboot.exe (only download that file from the G-Drive folder - thx to whoever uploaded it)
Run the MotorolaDeviceManager_2.4.5.exe you just downloaded and install it
Extract the two folders from adb-tools_treiber.zip
Open ADB-Treiber folder and run UniversalAdbDriverSetup.msi
Copy mfastboot.exe to ADB-Tools folder
Now this next part might be optional, but some things might not work without it and there's no real harm so:
Enable USB-Debugging
On your phone, open Preferences
Scroll all the way down to About this phone
Scroll all the way down to Build-Number
Tap 7 times on that entry
You'll get a message "You're a developer now"
Go back and open the new item Developer options
Check USB-Debugging
Connect your phone to the PC
Drivers will be installed and the phone will ask you to confirm USB debugging from that computer
Unlock Bootloader
There are probably lots of guides around, but to have it all in one place, here's yet another one:
!YOU WILL LOOSE YOUR WARRANTY AND ALL DATA BY UNLOCKING THE BOOTLOADER!
Switch off your phone
Hold Volume-Down and press and release Power to boot into Fastboot
A text screen should appear
Connect the phone via USB to the PC
Open a command prompt and browse to the ADB-tools folder you just created
Type:
Code:
fastboot oem get_unlock_data
You'll get five lines of characters, all beginning with (bootloader):
Code:
(bootloader) 0A40040192024205#4C4D3556313230
(bootloader) 30373731363031303332323239#BD00
(bootloader) 8A672BA4746C2CE02328A2AC0C39F95
(bootloader) 1A3E5#1F53280002000000000000000
(bootloader) 0000000
Copy all lines into one long string without the (bootloader) part!
You want something like 0A40040192024205#4C4D355631323030373731363031303332323239#BD00 and so on.
Open Motorola Unlocker Site (you need to sign-in)
Copy the string in the box at 6. and press Can my device be unlocked?
A Request my Unlock Key button should appear. Check I Agree to the legal stuff and press that button
Check your mail for the unlock key
In the ADB-tools folder type:
Code:
fastboot oem unlock [I]paste_your_key_here[/I]
The phone should reboot and greet you with a nice warning about you having lost your warranty.
Flash Recovery
Now that the booloader is unlocked you have to flash a custom recovery to be able to flash SuperSU.
Download the CWM image from this post. The file should be named something like recovery-clockwork-6.0.4.7-falcon.img. Copy the file to the ADB-Tools folder you created earlier and rename it to CWM.img
Your phone should still be connected to your PC and have finished rebooting and be in stock ROM.
In the ADB-Tools folder type:
Code:
adb reboot bootloader
The phone should reboot and the bootloader will come up again
To make sure all's working as expected type:
Code:
fastboot devices
You should get a response similar to:
Code:
List of devices attached
TA93005M6V device
To flash the custom recovery, type:
Code:
mfastboot flash recovery CWM.img
On the phone you might get a message about size mismatch, just ignore it. Now you have to enter the newly flashed CWM recovery. Take your phone and:
Press Volume-Down to scroll to the Recovery menu item
Press Volume-Up to select that item (yes, Vol-Up selects)
The phone will boot into recovery
Now is a good time to backup your system.
Press Volume-Down to scroll to Backup and Restore
Press Power to select that item
Press Volume-Down to scroll to Backup to /sdcard
Press Power to select that item
Backup will commence, once it's finished go back to the main menu and select Reboot, then confirm with YES
You phone will reboot into the stock ROM.
Flash SuperSU
Now you can finally flash SuperSU and be done with the whole business.
Download the newest SuperSU and save the file to your phone's SD-Card's root directory. The phone should show up as an MTP device in Windows file explorer.
In ADB-Tools folder type:
Code:
adb reboot recovery
The phone will reboot and once CWM Recovery has come up, use the Vol-Up/Down keys to scroll and Power to select
Select Install zip
Select zip from /sdcard
Select /0
You should find a file like UPDATE-SuperSU-v1.94.zip there.
Select that file, confirm YES and wait for the flashing to finish
Go back to the Main menu and select Reboot, confirm YES
The phone should once again reboot into normal stock ROM operation. To check if all went well, open the app drawer, tap on SuperSU and if no error message comes up... You're done!

I hope there are no mistakes anywhere in this guide and also that it might be helpful to some people...
Please comment if some things should be changed or improved.

Already guide is there general section..
http://forum.xda-developers.com/showthread.php?t=2585755
But you guide is simple and understandable.. So better stick this thread in this section..
Sent from my XT1032 using XDA Premium 4 mobile app

cdma moto g...?
Hey.. what about boost mobile moto g?? Its XT1031 and after pasting that string on motorola website it says your moble's bootloader can't be unlocked??

unlocking the bootloader worked great but it wont let me flash the recovery

keifus.rahn said:
unlocking the bootloader worked great but it wont let me flash the recovery
Click to expand...
Click to collapse
How you flashed it? Explain the steps you tried..
Sent from my XT1032 using XDA Premium 4 mobile app

bondisback said:
Hey.. what about boost mobile moto g?? Its XT1031 and after pasting that string on motorola website it says your moble's bootloader can't be unlocked??
Click to expand...
Click to collapse
I followed each step on this guide and i was using it threw android sdk but every time i select recovery on my device it says commands not found this is what i get in my comand prompt- target max sparse size error cant load recovery.img

keifus.rahn said:
I followed each step on this guide and i was using it threw android sdk but every time i select recovery on my device it says commands not found this is what i get in my comand prompt- target max sparse size error cant load recovery.img
Click to expand...
Click to collapse
Has anyone found success with a boost mobile variant please?

This was the easiest way for me and I used ROM manager to flash my recovery http://www.theandroidcop.com/how-to-root-motorola-moto-g/
Sent from my XT1031 using XDA Premium 4 mobile app

Remove the Spaces
bur2000 said:
I hope there are no mistakes anywhere in this guide and also that it might be helpful to some people...
Please comment if some things should be changed or improved.
Click to expand...
Click to collapse
I had the same problem at first. When you copy and paste the code on the website it put spaces between the code. There cant be any spaces then it will work. Hoped this helps XD

Thanks
Great guide, I used it to root my Moto G I got today but I had problems with flashing the Clockworld recovery. It simply would not work, said error. But I tried TWRP and it worked. But I also named it recovery.img and used your command but replaced CVM.img with recovery.img. Got rid of ALL of the bloatware. I was stuck at first because I didn't start the command promt inside of the adb tools folder.

Recovery issue
Guys I had a similar issue while flashing the cwm.
When I flash it in the first boot it works, I can enter in the interface and can create a backup or flash one, but after a reboot it do not enter again. I tried entering via fastboot -> Recovery and received the dead android icon with the "No command" message.
Tried installing via PlayStore and had the same result, even with the TWRP.
Any ideas ?

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