Database Develop

Root Nexus 7 from terminal, without replacing firmware or losing data

Even if you lose data, brick your device or/and throw it against the wall after reading this post
I am absolutely not responsible for anything you do to your android !
​
This procedure works on Linux (see NOTES below before).
1 - Ensure you have the latest android SDK installed on your computer, and that USB debugging is enabled on your device
2 - Backup your data with "adb backup":
adb backup -apk -shared -all -f backup.ab
(No warranty: You should also backup your sms (and paid application or application data) with something else.
Details and latest warnings here: http://forum.xda-developers.com/showthread.php?t=1420351)​
3 - Restart in bootloader:
adb reboot bootloader​
4 - Unlock the bootloader (everything will be erased, you need to confirm on your device)
fastboot oem unlock​
5 - Restart, skip configuration steps, enable USB debugging again
6 - Restore your data with adb restore:
adb restore backup.ab​
7 - Download the latest TWRP image on your computer, from the official TeamWin Recovery Project site: http://teamw.in/project/twrp2
8 - Download or push the latest CWM-superSU zipped package from eg http://download.chainfire.eu/282/SuperSU/
9 - Restart in bootloader:
adb reboot bootloader​
10 - Boot TWRP, eg;
fastboot boot openrecovery-twrp-2.3.1.0-grouper.img​
11 - Using TWRP, Install the CWM-superSU zipped package previously downloaded on your android.
12 - Reboot your device, you are set !
NOTES:
- If you need to re-root your system after a firmware update, restart at step 7 with USB debugging enabled.
- with Linux you need to:
* Run "sudo bash" first in the terminal window to enter administrator mode.
* Change to directory "android-sdk-linux/platform-tools" and prefix every command with ./
* If command "./adb devices" returns a "????? no permissions" error, restart adb server as root:
./adb kill-server
./adb start-server​

Is this not the wrong forum ?
Sent from my Galaxy Nexus using xda premium

danishprakash said:
Is this not the wrong forum ?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Ditto.

Step 4 should read 'Unlock Bootloader.'

Is this not the injustice forum ?
Dispatched from my Collection Linkage using xda reward

this is good for those who have been holding out on root and don't want to lose everything. the first time i rooted i was hesistant because i lost everything. so nice post, and im sure it'll be useful to lots of people, who understand it

Um, so..
adb backup + Nexus 7 Rooting Guide
http://forum.xda-developers.com/showpost.php?p=29271179&postcount=218

on the walkthrough over in the gnex forums, users found out that you need to set a backup password in developer options, otherwise the backup would not work, does the n7 not need the password?

I just wanted to root, not problems...
My priority was to backup the stock partitions just in case - user data is a bonus i did not need..
Then I found out it was possible to start a recovery partition with "fastboot boot" while keeping every partitions untouched
Ideal to not mess up things with flashing an unsuitable or syphilitic version of a system partition downloaded I don't know where ...
I did not want to use any rootkit for the exact same reasons, plus i'm allergic to Windows...

Hi luc, don't bother he complaints - I reckon you're on the right sub-forum (Nexus 7 General : tips & tricks), and your tutorial is so clear, simple, and to the point. I got my Nexus 7 rooted pretty much straigh away.
I've sent my thanks to your posts. Much appreciated.
Just need a bit of editing - "fastboot oem unlock" should be "sudo fastboot oem unlock"
The same with "sudo fastboot boot openrecovery-twrp-2.3.1.0-grouper.img"
(without the sudo prefix, fastboot waits forever)
Now my Nexus 7 is rooted, and I can stick my 64 GB flashdisk to my Nexus 7, making its capacity 80 GB
Thanks again for sharing.

Unlocking the downloader wipes the device does it not?

sufehmi said:
Just need a bit of editing - "fastboot oem unlock" should be "sudo fastboot oem unlock"
The same with "sudo fastboot boot openrecovery-twrp-2.3.1.0-grouper.img"
(without the sudo prefix, fastboot waits forever)
Click to expand...
Click to collapse
I did not want to scare others users with linux stuff on top of page.
However linux users should read the NOTES for linux mentioned there and run "sudo bash"
Thanks for your return !

CJHolderUK said:
Unlocking the downloader wipes the device does it not?
Click to expand...
Click to collapse
You can backup before unlocking the bootloader, as described in step 2.

Would I be right in thinking this will only work using Linux? would it be possible if I ran Linux as a virtual machine in Microsoft Virtual PC? Sorry if it's a dumb question, I am rather new here.

OP - clean and nice write up, thanks.
shezzuk1 said:
Would I be right in thinking this will only work using Linux? would it be possible if I ran Linux as a virtual machine in Microsoft Virtual PC? Sorry if it's a dumb question, I am rather new here.
Click to expand...
Click to collapse
It will work from windows, just don't forget to install Android SDK. Start cmd as Admin and navigate to platform-tools
Code:
cd "c:\Program Files (x86)\Android\android-sdk\platform-tools"
All other commands will be the same and you don't need to care about Linux stuff at the end of OP post.

Don't forget that unlocking the bootloader wipes the internal SD card, too. That's part of the data partition. Read more here.

[Q] PLEASE HELP. HTC One with no os

I rooted my sprint HTC One and when i was going to flash a rom i accidentaly wiped the phone completely. I can go into TWRP but cant move files into the phone. When i try plugging it into my computer all i hear is the little ring that windows does when you plug in something into the usb but i cant access the phones storage. I also tried buying a USB otg cable but the phone didnt seem to recognize it. please help. I've been stuck without a phone for about a week now

You try adb sideload(adb push (drag rom here) /sdcard / (hit enter)
From My TweakedOut ONE

Maybe
dased14 said:
You try adb sideload(adb push (drag rom here) /sdcard / (hit enter)
From My TweakedOut ONE
Click to expand...
Click to collapse
i tried to do something with the windows command line but i dont know if i did it right. im a noob with complicated stuff like this. i dont know if i had to download anything to make the adb work.

IVcruz said:
i tried to do something with the windows command line but i dont know if i did it right. im a noob with complicated stuff like this. i dont know if i had to download anything to make the adb work.
Click to expand...
Click to collapse
If your having trouble with ADB just grab this tool http://forum.xda-developers.com/showthread.php?t=2236814 and download the rom you want and within the tool click Sideload Rom and then select the rom. And you should be all set.
This might help you in the future so you dont wipe your data again http://forum.xda-developers.com/showthread.php?t=2237021

I tried
Konfuzion said:
If your having trouble with ADB just grab this tool http://forum.xda-developers.com/showthread.php?t=2236814 and download the rom you want and within the tool click Sideload Rom and then select the rom. And you should be all set.
This might help you in the future so you dont wipe your data again http://forum.xda-developers.com/showthread.php?t=2237021
Click to expand...
Click to collapse
I gave it a shot but when i tried to sideload the rom it says device not found. i got the same thing when i tried to adb push the rom onto my sdcard. i get an error saying device not found i also tried running the RUU but apparently i need a newer version of the RUU that is not out yet so i think im stuck and just have to wait and hope that the RUU i need comes out soon.

IVcruz said:
I rooted my sprint HTC One and when i was going to flash a rom i accidentaly wiped the phone completely. I can go into TWRP but cant move files into the phone. When i try plugging it into my computer all i hear is the little ring that windows does when you plug in something into the usb but i cant access the phones storage. I also tried buying a USB otg cable but the phone didnt seem to recognize it. please help. I've been stuck without a phone for about a week now
Click to expand...
Click to collapse
What os are you using?
When you plug the phone in and your computer makes the ding what shows up in device manager?

Having same issue...
Flashed Android Revolution HD...probably hosed my partitions
I can access FastBoot, but no ADB access from newly formated Windows 7 PC...
...I can't sideload via ANY recovery...
and I can't OTG with USB flash drive via ANY recovery too
Looking for latest RUU but no luck.
I tried to S-Off so I can RUU with 1.29 but no luck with RevOne since I can't ADB for some reason.
Thoughts? Suggestions? Thanks for looking

IVcruz said:
I gave it a shot but when i tried to sideload the rom it says device not found. i got the same thing when i tried to adb push the rom onto my sdcard. i get an error saying device not found i also tried running the RUU but apparently i need a newer version of the RUU that is not out yet so i think im stuck and just have to wait and hope that the RUU i need comes out soon.
Click to expand...
Click to collapse
You don't need to RUU. From that tool click install HTC drivers. And see if that works if not unusual the HTC drivers and install universal naked htc one drivers (Google it you will find it).
Sent from my HTCONE using xda app-developers app
---------- Post added at 06:00 PM ---------- Previous post was at 05:55 PM ----------
rvelajr said:
Having same issue...
Flashed Android Revolution HD...probably hosed my partitions
I can access FastBoot, but no ADB access from newly formated Windows 7 PC...
...I can't sideload via ANY recovery...
and I can't OTG with USB flash drive via ANY recovery too
Looking for latest RUU but no luck.
I tried to S-Off so I can RUU with 1.29 but no luck with RevOne since I can't ADB for some reason.
Thoughts? Suggestions? Thanks for looking
Click to expand...
Click to collapse
You flashed a GSM Rom on your Sprint CDMA device.
Now to fix it follow this guide
http://forum.xda-developers.com/showthread.php?p=44243635
To make your life easy you will need drivers for your phone the best are the universal naked drivers for HTC One
http://forum.xda-developers.com/showthread.php?t=2263822
If installed, uninstall HTC sync, and disable any anti virus or firewalls including Windows firewall. You will also need to download ADB if you don't have it minimal ADB is great
http://forum.xda-developers.com/showthread.php?p=42407269
Next time read before you flash!
Sent from my HTCONE using xda app-developers app

Still battling with ADB...no devices detected...I'm stumped
Universal Driver installed without a hitch...
No firewall
No anti-virus
No HTC Sync
Fastboot works...no adb...daemon starts on port 5037..but no luck
Thoughts?

rvelajr said:
Still battling with ADB...no devices detected...I'm stumped
Universal Driver installed without a hitch...
No firewall
No anti-virus
No HTC Sync
Fastboot works...no adb...daemon starts on port 5037..but no luck
Thoughts?
Click to expand...
Click to collapse
Are you doing this from recovery?
Sent from my HTCONE using xda app-developers app

Got device recognized in recovery...
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Program Files\Minimal ADB and Fastboot>adb devices
List of devices attached
FA35GS910838 recovery
Typed "adb shell"
Then copied/paste echo "1.29.651.10" | dd of=/dev/block/mmcblk0p19 bs=1 seek=160
with following result...
Sorry for Noob experience here...
C:\Program Files\Minimal ADB and Fastboot>adb shell
~ # ←[6necho "1.29.651.10" | dd of=/dev/block/mmcblk0p19 bs=1 seek=160
echo "1.29.651.10" | dd of=/dev/block/mmcblk0p19 bs=1 seek=160
warning: seek lseek64 failed
12+0 records in
12+0 records out
12 bytes (12B) copied, 0.006990 seconds, 1.7KB/s
~ # ←[6n
Am I missing something?

rvelajr said:
Got device recognized in recovery...
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Program Files\Minimal ADB and Fastboot>adb devices
List of devices attached
FA35GS910838 recovery
Typed "adb shell"
Then copied/paste echo "1.29.651.10" | dd of=/dev/block/mmcblk0p19 bs=1 seek=160
with following result...
Sorry for Noob experience here...
C:\Program Files\Minimal ADB and Fastboot>adb shell
~ # ←[6necho "1.29.651.10" | dd of=/dev/block/mmcblk0p19 bs=1 seek=160
echo "1.29.651.10" | dd of=/dev/block/mmcblk0p19 bs=1 seek=160
warning: seek lseek64 failed
12+0 records in
12+0 records out
12 bytes (12B) copied, 0.006990 seconds, 1.7KB/s
~ # ←[6n
Am I missing something?
Click to expand...
Click to collapse
Nope now flash the RUU.
Need anything PM me

SOLVED!
Is is worth to S-Off with revone at this point?
I've installed ViperOne rom (my fav) and all looks well.
Since, I'm back to 1.29...what is best way to get back to 1.31.651.2?

budeone said:
What os are you using?
When you plug the phone in and your computer makes the ding what shows up in device manager?
Click to expand...
Click to collapse
Im using windows 8 and when i plug in my phoen it actually does show up under devices under a "unspecified" category where it says that drivers are unavailable. I have tried installing the drivers though and it still wont work.

rvelajr said:
SOLVED!
Is is worth to S-Off with revone at this point?
I've installed ViperOne rom (my fav) and all looks well.
Since, I'm back to 1.29...what is best way to get back to 1.31.651.2?
Click to expand...
Click to collapse
S-off will help you if you need to RUU again if your on 1.31
Sent from my HTCONE using xda app-developers app

[Q] Help with bricked HTC One

I've been a lurker for the last few years; never thinking I would need any help or assistance .. but I have a situation ..
My Sprint HTC One was working better than I had ever seen it just last Thursday. I was running CM11, with ART. I had an old version of SuperOne (Sense 5) backed up with TWRP. I thought I'd go ahead and load the backup, and update all the apps and then make another more recent backup before returning to CM11. I got as far holding the power button and selecting recovery. The phone locked up at that point.
It took 10 minutes to get it back to the screen where you can select fastboot, factory reset, etc. Interestingly I couldn't get into TWRP. The screen read "entering recovery" and nothing. It would just hang there.
I read that erasing the cache with fastboot might work, and it did. But when I was able to enter recovery, instead of restoring CM11, I thought, "well, maybe now it'll work", so I just rebooted. Wrong. Wouldn't boot. And, now running fastboot cache erase (or erase cache) doesn't do anything.
Now, by pressing the power button alone and holding it in I'm able to get to the fastboot, factory reset, etc screen. Went to fastboot usb, and fastboot commands work but ADB doesn't detect the device. I can't send ADB commands, but I can send ONE fastboot command. After sending any fastboot command, the phone locks up. Nothing from that point.
I tried installing a RUU. The .exe file detected the version on my phone, and everything went great until the program said it was booting to the bootloader. Locked it up. Nothing from that point.
I need help.
Thanks.
I uninstalled the HTC drivers and reinstalled them. A suggestion since ADB didn't work. And I can't get into bootloader. No difference.

Any suggestions
Any suggestions at all. I'm desperate.

Ogre77497 said:
Any suggestions at all. I'm desperate.
Click to expand...
Click to collapse
You can get into fastboot correct?

Fastboot - Yes .. Sorta
I can get into fastboot, but I copy anything to the phone via fastboot. I'm told "unable to write". Thanks.

Ogre77497 said:
I can get into fastboot, but I copy anything to the phone via fastboot. I'm told "unable to write". Thanks.
Click to expand...
Click to collapse
Ok it's probably a problem with your USB cable or USB port. Try using another PC and another cable.
If this doesn't work read some guide to properly set up ADB, uninstall all HTC stuff and install only the "naked driver" and than run the LATEST ruu. Maybe you have upgraded your firmware and can't flash older ruu's.
Sent from my HTCONE using Tapatalk

Will Try
I'll give that a try. I really appreciate the help. I run my whole business on that phone.

Just make sure you follow my suggestions properly. It should be just the cable, and I think you don't have the right drivers for ADB. Stay calm your phone is just soft bricked. You only need to be patient and read. Naked driver here http://forum.xda-developers.com/showthread.php?t=2263822
Sent from my HTCONE using Tapatalk

elvisypi said:
Ok it's probably a problem with your USB cable or USB port. Try using another PC and another cable.
If this doesn't work read some guide to properly set up ADB, uninstall all HTC stuff and install only the "naked driver" and than run the LATEST ruu. Maybe you have upgraded your firmware and can't flash older ruu's.
Sent from my HTCONE using Tapatalk
Click to expand...
Click to collapse
+1
I did the same thing a few weeks ago and lost recovery in the process. The naked driver did the trick. Also the thread about restoring after a gsm rom install is a great. It's not a loss. Not having an sd card in the one made things a little different for me, but I was able to get everything back. These drivers suck!

Progress
I've followed your directions. I downloaded the naked driver, and the minimal ADT. I found the correct RUU (3.04.651.2) I attempted to relock the bootloader, but I got a message .. " Status read failed <no such file or directory>" Went ahead and tried flashing the RUU (fastboot flash zip ruu.zip), and got the message "FAILED Remote: not allowed"
The phone is unlocked, CID SPCS_001, and HBOOT 1.44
I wasn't able to access TWRP recovery earlier, so I tried reflashing the img file. Failed remote: image update error. I tried erasing the cache .. "Failed remote erasing error", but now I can get into TWRP.
TWRP says I have "0" internal storage. I also can't mount system, data or cache. The choices are there but can't be selected.
I can't use ADB (device not found). and the phone isn't detected by windows. I had installed the HTC drivers, but couldn't uninstall them, so I install HTC Sync manager and then uninstalled it. The program deleted the HTC drivers when I uninstalled it. When I plugged in the HTC One (with a new cable) nothing happened, so I used the windows hardware wizard to install the naked driver. The phone still isn't detected, but again I can issue fastboot commands. Well, one fastboot command and then the phone freezes up.
If I use filemanager within TWRP there's no emulated sd card. I really think that's where my problem is. No partitions are available. And, when I use TWRP to shut down, it warns me that no OS is installed.
Any other suggestions?
I sure appreciate all your help. Thanks.
elvisypi said:
Just make sure you follow my suggestions properly. It should be just the cable, and I think you don't have the right drivers for ADB. Stay calm your phone is just soft bricked. You only need to be patient and read. Naked driver here http://forum.xda-developers.com/showthread.php?t=2263822
Sent from my HTCONE using Tapatalk
Click to expand...
Click to collapse

Are you Linux savvy at all? All this crap is far easier on Linux. I guarantee the drivers are absolute cakewalk -- there isn't a specific driver at all, just a rule to tell the kernel about the device.
I can give you the udev rule for the phone if you are sick of trying to get Windows to work. The Android SDK is also quite easy to install.
If you want to try, just install Ubuntu 12.04 LTS. Later versions also work, but that version is the current stable release. I can help from there.

Try another cable maybe it's faulty. Uninstall all the HTC crap, run some cleaner app like ccleaner (maybe there are leftovers) and install only the naked driver. Your phone should be detected. Make sure you have the latest version of ADB. here's the latest http://click.xda-developers.com/api...n 1.1.3 Here&jsonp=vglnk_jsonp_13877458281136
The ruu is not to be flashed with fastboot commands, you must run the exe file
Here's the latest ruu
http://click.xda-developers.com/api....05.651 .5&jsonp=vglnk_jsonp_138775039936710
-extract zip to a folder on your pc
-using fastboot, type this cmd: fastboot oem lock this will relock the bootloader
-from pc, run ARUWizard.exe from the extracted folder. it will run the RUU utility & flash back to stock
Sent from my HTCONE using Tapatalk

Installing Ubuntu
Not Linux savy at all, but I'll install Ubuntu. I'll let you know when I'm able to boot into it. Thanks.
tdhite said:
Are you Linux savvy at all? All this crap is far easier on Linux. I guarantee the drivers are absolute cakewalk -- there isn't a specific driver at all, just a rule to tell the kernel about the device.
I can give you the udev rule for the phone if you are sick of trying to get Windows to work. The Android SDK is also quite easy to install.
If you want to try, just install Ubuntu 12.04 LTS. Later versions also work, but that version is the current stable release. I can help from there.
Click to expand...
Click to collapse

Ogre77497 said:
Not Linux savy at all, but I'll install Ubuntu. I'll let you know when I'm able to boot into it. Thanks.
Click to expand...
Click to collapse
When you get it installed, login and open a terminal windows (it'll install Unity by default, so click on the first button on the left sidebar and search for terminal, then click on it), then type exactly the following (cut/copy/paste should do it too) noting that the first command will make you give your password since sudo requests root level access:
sudo apt-get update -y
sudo apt-get install -y wget openjdk-7-jdk
wget http://dl.google.com/android/android-sdk_r22.3-linux.tgz
mkdir ~/bin
cd ~/bin
tar xvzf ~/android-sdk_r22.3-linux.tgz
cat >> ~/.bashrc <<EOF
if [ -d ${HOME}/bin/android-sdk-linux ]; then
PATH+=":${HOME}/bin/android-sdk-linux/tools"
PATH+=":${HOME}/bin/android-sdk-linux/platform-tools"
fi
export PATH
EOF
exit
That last command will exit the terminal. Start another and it'll read the .bashrc file and presto -- you have SDK access from everywhere.
Then, type this command:
android
That will bring up the SDK UI -- let it download/install all of the latest stuff (r22 of the tools and whatnot).
When done, close the android SDK window.
Type adb (bet it works), but fastboot will require root access (I'm not going to teach you how to get around that yet -- no problem, you just run sudo and I'll show that in a sec).
Finally, plug in your HTC One and type adb devices and let's see if it didn't just know it already.
Lemme know.

Ubuntu 12.04 LTS Installed
I have Linux running on my Dell laptop. No internet though. Something about installing broadcom drivers ..
What do I need to do, sir?
tdhite said:
Are you Linux savvy at all? All this crap is far easier on Linux. I guarantee the drivers are absolute cakewalk -- there isn't a specific driver at all, just a rule to tell the kernel about the device.
I can give you the udev rule for the phone if you are sick of trying to get Windows to work. The Android SDK is also quite easy to install.
If you want to try, just install Ubuntu 12.04 LTS. Later versions also work, but that version is the current stable release. I can help from there.
Click to expand...
Click to collapse

Ogre77497 said:
I have Linux running on my Dell laptop. No internet though. Something about installing broadcom drivers ..
What do I need to do, sir?
Click to expand...
Click to collapse
Check PM

bigdaddy619 said:
Check PM
Click to expand...
Click to collapse
@bigdaddy619 probably got you covered, but if not, let me know. Your friend for Broadcom chips on Dell boxes is here:
https://help.ubuntu.com/community/WifiDocs/Driver/bcm43xx
The gist is pretty simple. If you don't know which wireless you have, do this:
1) widen your terminal window so you have ample room (good and wide);
2) run sudo lspci -v
Hunt down the Broadcom info -- it'll say which device is your broadcom wifi. Just need the numbers.

Working ..
I feel like I'm making some progress here, but it's still not being recognized. Everything worked great up until ...
After closing the SDK window, I connected the HTC One, and "Fastboot USB" came up on my phone. I typed adb devices and got a line "List of Devices attached" by nothing was showing as being attached.
If I enter a fastboot command, it hangs saying "waiting on device".
tdhite said:
When you get it installed, login and open a terminal windows (it'll install Unity by default, so click on the first button on the left sidebar and search for terminal, then click on it), then type exactly the following (cut/copy/paste should do it too) noting that the first command will make you give your password since sudo requests root level access:
sudo apt-get update -y
sudo apt-get install -y wget openjdk-7-jdk
wget http://dl.google.com/android/android-sdk_r22.3-linux.tgz
mkdir ~/bin
cd ~/bin
tar xvzf ~/android-sdk_r22.3-linux.tgz
cat >> ~/.bashrc <<EOF
if [ -d ${HOME}/bin/android-sdk-linux ]; then
PATH+=":${HOME}/bin/android-sdk-linux/tools"
PATH+=":${HOME}/bin/android-sdk-linux/platform-tools"
fi
export PATH
EOF
exit
That last command will exit the terminal. Start another and it'll read the .bashrc file and presto -- you have SDK access from everywhere.
Then, type this command:
android
That will bring up the SDK UI -- let it download/install all of the latest stuff (r22 of the tools and whatnot).
When done, close the android SDK window.
Type adb (bet it works), but fastboot will require root access (I'm not going to teach you how to get around that yet -- no problem, you just run sudo and I'll show that in a sec).
Finally, plug in your HTC One and type adb devices and let's see if it didn't just know it already.
Lemme know.
Click to expand...
Click to collapse

Ogre77497 said:
I feel like I'm making some progress here ....
Click to expand...
Click to collapse
Hang in, writing you some instructions, just a few minutes -- just need to get a udev rule into place but I want to make it easy for you.
---------- Post added at 08:18 PM ---------- Previous post was at 07:50 PM ----------
tdhite said:
Hang in, writing you some instructions, just a few minutes -- just need to get a udev rule into place but I want to make it easy for you.
Click to expand...
Click to collapse
Actually -- let's walk before we run. I loaded up Ubuntu real quick to assure I can duplicate what I want you to see. So, do this:
1) connect (if not already connected) the HTC to the usb port so you get 'fastboot (usb)' as normal;
2) type the following:
sudo su
lsusb -v >/tmp/lsusb.txt
chmod 666 /tmp/lsbusb.txt
exit
Now, edit that file in the text editor (just search for 'edit' like you did for 'termina' and select the "Text Editor". When you get that open, have it "File | Open" the file above -- /tmp/lsusb.txt
Then look through for text similar to what I give below. If we get that -- I need the idVendor line -- it should read: "idVendor 0x0bb4 High Tech Computer Corp."
I copied some sample output from my own machine so you can see how it should look:
--------
probably a bunch of stuff we don't care about, then something like...
Bus 001 Device 005: ID 0bb4:0ff0 High Tech Computer Corp.
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.10
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x0bb4 High Tech Computer Corp.
idProduct 0x0ff0
bcdDevice 1.00
iManufacturer 1 htc, Inc
iProduct 2 Android 1.0
iSerial 3 XXXXXXXXXXXX (I X'd this out -- it'll be your device serial id).
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 32
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
and a bunch more stuff...
If we don't see that, we got troubles. If we do -- we'll make a udev rule to load it up for adb and fastboot.

It appears he's bricked, when we first mounted the phone to the PC and it tried to install drivers we got QHSUSB_DLOAD which usually indicates a brick.
The strange thing was we could still access fastbootusb and the PC would recognize it being in fastboot. But any other command then fastboot devices would lock up the bootloader and fail.

Getting Closer
That's exactly it. "idVendor 0x0bb4 High Tech Computer Corp."
Finally, something worked. Thanks.
Now, edit that file in the text editor (just search for 'edit' like you did for 'termina' and select the "Text Editor". When you get that open, have it "File | Open" the file above -- /tmp/lsusb.txt
Then look through for text similar to what I give below. If we get that -- I need the idVendor line -- it should read: "idVendor 0x0bb4 High Tech Computer Corp."

How do I get ADB to see my device?

I have a Sprint HTC One M8. It's rooted. I have TWRP. I basically just wanted to get rid of bloatware. But now I want to follow a tutorial that requires me to be S-OFF.
I think I am on this step:
Push, Prepare, and Execute firewater:
adb reboot <–important!!!!
adb wait-for-device push firewater /data/local/tmp
adb shell
su
chmod 755 /data/local/tmp/firewater
/data/local/tmp/firewater
When I type any commands nothing happens. adb devices, adb shell, etc. Nothing. Am I supposed to go in Recovery?
If I go into recovery they work.. so I rebooted.. I pushed firewater over. I did adb shell and up pops:
~ # <-[6n.
I hit SU and it says /sbin/sh: su: not found.
I did chmod command from above. When I do the last step /data/local/tmp/firewater it says permission denied.

When you are booted into android make sure usb debugging is enabled. Settings > About > Software Information > More > click Build Number like 10 times to enable developers options. Then go to Settings > Developer Options > check USB Debugging. Also go to Settings > Power > uncheck Fastboot, You have to run firewater from android, NOT from recovery. What exactly are you trying to do that requires S-OFF?

Thanks. I've already got Developer. USB Debugging is enabled.
EDIT: Because I misread your post. I didn't know I run Firewater through Android. But anyway, it's not working.
I'm just doing a simple mod to hide the Boomsound icon. Stupid to have that clog up my notification area.

PS - I see you're in Ocean City, NJ? My friends wife's parents live in Somers Point. I go down to Smithville sometimes.. little town with all the shops in it.. it's fantastic when they decorate it for Christmas. Really nice stores to shop in and the inn has the best french onion soup I've ever had.

yuppicide said:
I have a Sprint HTC One M8. It's rooted. I have TWRP. I basically just wanted to get rid of bloatware. But now I want to follow a tutorial that requires me to be S-OFF.
I think I am on this step:
Push, Prepare, and Execute firewater:
adb reboot <–important!!!!
adb wait-for-device push firewater /data/local/tmp
adb shell
su
chmod 755 /data/local/tmp/firewater
/data/local/tmp/firewater
When I type any commands nothing happens. adb devices, adb shell, etc. Nothing. Am I supposed to go in Recovery?
If I go into recovery they work.. so I rebooted.. I pushed firewater over. I did adb shell and up pops:
~ # <-[6n.
I hit SU and it says /sbin/sh: su: not found.
I did chmod command from above. When I do the last step /data/local/tmp/firewater it says permission denied.
Click to expand...
Click to collapse
I am not sure exactly what you have going on, but here are a few tips. Make sure you have it mounted as a storage device. Also, make sure you open the command window in the same folder you have adb in, or navigate to that directory properly.

KUmike said:
I am not sure exactly what you have going on, but here are a few tips. Make sure you have it mounted as a storage device. Also, make sure you open the command window in the same folder you have adb in, or navigate to that directory properly.
Click to expand...
Click to collapse
That reply helped me. You said "mounted as storage device". When I clicked my phone it said "HTC SYNC" on it.
I'm good now, thanks!

I just went through this yesterday. Updating adb fixed it for me. Also, following those commands necessitates that the file is where u type it. So, I followed another website's guide and achieved s-off.
Sent from my 831C using xda app-developers app

iandmacdonald said:
I just went through this yesterday. Updating adb fixed it for me. Also, following those commands necessitates that the file is where u type it. So, I followed another website's guide and achieved s-off.
Sent from my 831C using xda app-developers app
Click to expand...
Click to collapse
Every time I connect my phone, all I need to do is select "Disk Drive" rather than HTC Sync. By default the phone chooses that. Now everything works fine.

I know you have already fixed your problem but I recommend uninstalling the HTC Sync Manager from your computer. Keep the HTC Drivers though. If you still get the popups to install HTC Sync after you uninstall it; remove the installer/option on your M8. You'll need a file manager and root to do that or you could install ViperOne and de-select the option in Aroma.
I can't remember the file you have to remove off-hand though, I just went through my folders and deleted stuff I didn't need or want. I made backups just in case it needed to be re installed.

KUmike said:
I am not sure exactly what you have going on, but here are a few tips. Make sure you have it mounted as a storage device. Also, make sure you open the command window in the same folder you have adb in, or navigate to that directory properly.
Click to expand...
Click to collapse
I had ADB work fine without switching to Mass Storage.

mswlogo said:
I had ADB work fine without switching to Mass Storage.
Click to expand...
Click to collapse
It definitely won't for me
Sent from my 831C using Tapatalk

KUmike said:
It definitely won't for me
Sent from my 831C using Tapatalk
Click to expand...
Click to collapse
Maybe you have HTC Sync installed? You shouldn't.

mswlogo said:
Maybe you have HTC Sync installed? You shouldn't.
Click to expand...
Click to collapse
Nope, I dunno. Works in mass storage mode
Sent from my 831C using Tapatalk

I was having similar problems with my M7 and Windows 7 devices after upgrading to 4.4.2 and Sense 6 (Team Nocturnal NuiSense). My phone wasn't recognized by HTC Sync or CDMA Workshop.
I kept uninstalling/reinstalling drivers, to no avail.
What finally worked like a magic bullet for me was to dial ##3424# and turn on DM Command Service.
I'm not sure if that will work for you, but it may be worth a shot.

I hv same problem but how I can on my USB debbuging mode ,,, rooted but no OS
{ParanoiA} said:
When you are booted into android make sure usb debugging is enabled. Settings > About > Software Information > More > click Build Number like 10 times to enable developers options. Then go to Settings > Developer Options > check USB Debugging. Also go to Settings > Power > uncheck Fastboot, You have to run firewater from android, NOT from recovery. What exactly are you trying to do that requires S-OFF?
Click to expand...
Click to collapse
I hv same problem but how I can on my USB debbuging mode ,,, rooted but S-on and I hv TWRP but no OS firmware ,,,, Kindly guide me what I should do to make active my usb debugging mode in HTC desire 828 dual sim ? plzzzz

[how to]remove your "tampered" banner

*this thread is for desire 510 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.
*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 cricket desire 510 variant(a11_ul),but use this info at your own risk. if it melts your phone into a little pile of plastic goo,its not my fault.
credits
-beaups for schooling me on echo command protocol
--strace for originally discovering the location of the lock status flag(check out this thread for more info) wich started off my love for chasing such things.
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
other useful threads:
lock/unlock without htcdev: http://forum.xda-developers.com/desire-510/general/how-to-lock-unlock-bootloader-htcdevs-t3179874
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.

one more

scotty1223 said:
one more
Click to expand...
Click to collapse
btw.32bit Desire 510 Cricket support WCDMA?

bl4ckluna said:
btw.32bit Desire 510 Cricket support WCDMA?
Click to expand...
Click to collapse
Yes
Sent from my HUAWEI ALE-L04 using Tapatalk

find Problem....that device only Support WCDMA USA Band....not support ASIA （

Correct me, please.
Correct me if I'm wrong, please! But isn't the only way, currently, to get S-off for our phone, is to pay $25 when using Sunshine?

JimFritzMI said:
Correct me if I'm wrong, please! But isn't the only way, currently, to get S-off for our phone, is to pay $25 when using Sunshine?
Click to expand...
Click to collapse
Sunshine is one way to skin the cat. I am Not sure if there are others
Sent from my HUAWEI ALE-L04 using Tapatalk

That seems like an elusive answer...
scotty1223 said:
Sunshine is one way to skin the cat. I am Not sure if there are others
Sent from my HUAWEI ALE-L04 using Tapatalk
Click to expand...
Click to collapse
Almost as if there were other ways...
I seriously considered paying for it to be done, when I first started. However, I can't seem to find a reason to do so.

this is great. but how do you get S-OFF on the desire 510.
also if you get S-OFF won't that void the warranty anyway?