Hello all
I was trying to get S-OFF, but my phone is not being recognized as online in ADB. I'm almost positive that I have the correct drivers, etc installed because I had no problem rooting it/being recognized in fastboot. But when I do ' adb devices ' it shows the phone, but says offline. I've done kill server, start server... I've updated everything in the sdk... Debugging is on... I'm completely lost and don't know what to do.
Thanks
What happens when you type a command like "adb reboot recovery" (without quotation marks)?
Sent from my EVO using xda premium
FinZ28 said:
What happens when you type a command like "adb reboot recovery" (without quotation marks)?
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Before you responded, I manually rebooted to recovery to make a back up, then rebooted back to system. Now when I do "adb devices" it shows the device and says "device", is this what I'm looking for?
Also, I did the "adb reboot recovery" and noting happens.... The cursor moves to next line and just blinks. Nothing more. The phone doesn't reboot.
Thanks
It should output the device serial number when you type "adb devices".
Sent from my EVO using xda premium
FinZ28 said:
It should output the device serial number when you type "adb devices".
Sent from my EVO using xda premium
Click to expand...
Click to collapse
When I type "adb devices", I get
Code:
List of devices attached
HT25MS402628 offline
When I type "adb reboot recovery", nothing happens.
Strange. I've never seen the offline message in ADB before
You are booted into your ROM when trying to run ADB, correct?
Sent from my EVO using xda premium
FinZ28 said:
Strange. I've never seen the offline message in ADB before
You are booted into your ROM when trying to run ADB, correct?
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Download HTC sync or pdanet drivers and you should be golden
Sent from my HTCONE using xda app-developers app
Thanks for the help everyone
I finally got it working; the problem was (apparently) the ROM... I was using RageLTE, but I restored a backup of Stock w/Goodies and everything was fine.
Unfortunately, It looks like my firmware is too new(?) and I can't use LazyPanda, and DirtyRancun has dropped support for Windows 8/64, so I guess I'll have to try the Live CD route....
Now im understanding, I have the same problem with Rage. I think i posted somewhere in that thtead. Didnt expierience it on any otber sense rom.
bjb_nyj101 said:
Thanks for the help everyone
I finally got it working; the problem was (apparently) the ROM... I was using RageLTE, but I restored a backup of Stock w/Goodies and everything was fine.
Unfortunately, It looks like my firmware is too new(?) and I can't use LazyPanda, and DirtyRancun has dropped support for Windows 8/64, so I guess I'll have to try the Live CD route....
Click to expand...
Click to collapse
What are u on? Try facepalm s-off yet?
scttydb411 said:
What are u on? Try facepalm s-off yet?
Click to expand...
Click to collapse
Hes on Rage Rom, its a known issue. Rom specific. I had the exact same issue with that rom
*Information IS the most dangerous weapon of all*
Thanks for the help everyone. Yeah, Rage was the problem, so I flashed back to Stock w Goodies and used dirty racun thru an ubuntu live CD. Finally s-off and running cm10.1!!
thanks for this thread. I was having the same issue my device was reading HT251W3005.... offline and it just so happen that I was running the Rage XL rom.
I guess search does work
Update Your Android
I was having this same problem with Cyanogenmod 10.1 (a.k.a. JellyBean 4.2.2). I figured out that I had an older install of the Android SDK. I updated it, then unplugged and replugged my USB cable. The device prompted me with something like "is it okay to accept ADB from this computer?" I told it yes and now I can see my device in adb devices output again.
i have the same problem
tried but nothing happened
i guess i have problem in rom
Related
I am attempting to get s-off and I seem to be running into some issues. Here is the output of Control bear:
======== ControlBear 0.4 beta for JuopunutBear S-OFF ==========
Starting up......
Backing up......
Transferring backups....
Backup ok!!
Using eMMC dev /dev/block/mmcblk0
Using MMC dev /dev/block/mmcblk1
Boot partition is /dev/block/mmcblk0p22
Recovery partition is /dev/block/mmcblk0p23
Is information correct? You have 5 seconds time to press CTRL+C
Finding some beer.....
Found first....
Found second....
Found third....
Hmmmm... where is that last one....... Wait a sec....
Found fourth....
Rebooting.......
=== Waiting device....
(45/45)
Hmmm, still no device
Resetting connection....1........2....
(45/45)
Hmmm, still no device
Resetting connection....1........2....
(45/45)
Hmmm, still no device
Resetting connection....1........2....
(45/45)
Hmmm, still no device
Resetting connection....1........2....
(45/45)
Hmmm, still no device
Resetting connection....1........2....
(45/45)
Hmmm, still no device
Resetting connection....1........2....
(45/45)
Hmmm, still no device
Any ideas why it is unable to find the device? BTW, this is on linux, and I am running as root.
Same exact thing it does to me on windows. Once mine gets to the screen with the arrow it can't find my phone anymore. Odd since cleanflash has no trouble. I tried reinstalling adb and HTC drivers to no avail. I finally just gave up for the moment.
Sent from my ADR6425LVW using XDA
I ended up just copying all of the control bear stuff to my platform tools folder with rest of my adp stuff and bam.
Sent from my ADR6425LVW using xda premium
blestsol said:
I ended up just copying all of the control bear stuff to my platform tools folder with rest of my adp stuff and bam.
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
I tried that, still didn't work for me. I've installed and uninstalled the drivers multiple times. It just refuses to find my phone no matter what I do.
Just thinking out loud, but are you unlocked, custom recovery?
Sent from my ADR6425LVW using xda premium
trickster2369 said:
Just thinking out loud, but are you unlocked, custom recovery?
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
I am unlocked, CWM recovery, usb debugging on (at least it is when control bear starts). adb just seems to be unable to connect to the device after the first reboot.
Unlocked aman-ra 3.15. Its odd that it finds the phone just fine to backup and reboot. Also reboots from fastboot no problem. Its once it gets to the green arrow and tries to find my phone it fails.
Sent from my ADR6425LVW using XDA
kain72 said:
Unlocked aman-ra 3.15. Its odd that it finds the phone just fine to backup and reboot. Also reboots from fastboot no problem. Its once it gets to the green arrow and tries to find my phone it fails.
Sent from my ADR6425LVW using XDA
Click to expand...
Click to collapse
We seem to be having the exact same problem (except I am on CWM). Guess that eliminates the recovery as the culprit....
kain72 said:
Unlocked aman-ra 3.15. Its odd that it finds the phone just fine to backup and reboot. Also reboots from fastboot no problem. Its once it gets to the green arrow and tries to find my phone it fails.
Sent from my ADR6425LVW using XDA
Click to expand...
Click to collapse
This is before the wire trick or after you do the wire trick?
CharliesTheMan said:
This is before the wire trick or after you do the wire trick?
Click to expand...
Click to collapse
Before the wire trick, immediately after the initial boot into JP.
trud9340 said:
Before the wire trick, immediately after the initial boot into JP.
Click to expand...
Click to collapse
I also had a very similar issue the day it launched. I can't remember what was keeping the program from running like it should, I believe that when I uninstalled or killed HTC syn running, and went to the task manager and killed ADB.exe in windows I realized that there was a droid explorer service running that kept instantly restarting ADB. Once I finally killed the service then restarted the program it worked.
Have you tried using a second windows computer just for kicks? If it's convenient I would try that and then just run a linux live cd if windows is still having driver issues.
I'm stuck with only my laptop for the moment. Its odd, I've killed HTC sync and everything else I can think of including antivirus
Sent from my ADR6425LVW using XDA
I had the same problems yesterday, there was some htcsyncupdate process running that kept on interfering with the process.
In task manager make sure to show processes of all users. Also be sure in msconfig.exe you have selective startup selected so that it's not just restarting what you kill when you reboot.
I can't think of much else off the top of my head, I'm willing to remote in and take a look on team viewer just to offer a second set of eyes if you would like. Someone else may post and tell you exactly where the issue lies.
Hmm
Query if enough permissions, drivers, and other services are running in safe mode to still allow for Controlbear to run without any HTC software interference.
I think I am going to give it a shot in safe mode here on the next try. Or at minimum make a custom boot state to kill everything but needed windows services. Unfortunately not near my pc for a while yet. Thanks for the suggestions guys can't hurt to try.
Sent from my ADR6425LVW using XDA
remote not allowed
Im trying to flash recovery through adb but it starts the install fails and says remote not allowed. Any suggestions? Im s-off, running 3.11
For recovery flashes I've always used clean flash. Just makes it easier for me.
Sent from my ADR6425LVW using XDA
Amon Ra
Please tell me you are NOT on CWM.
Lol not me aman-ra 3.15
Sent from my ADR6425LVW using XDA
I was just wiping my tablet to get it ready to turn in to best buy so they can exchange me for the Infinity, and I'm just doing my final data wipes of the tablet and I chose to wipe it from the settings menu. Since I'm rooted and have CWM Recovery, when I wiped, the tablet was probably looking for the stock recovery and won't boot back into the ROM anymore it just continually boots back into recovery. I followed the unbrick guide in the Dev section. But only issue is that. ADB won't recognize my prime. Also, I have nothing in my internal storage, so I can't flash a ROM...
Any advice?
Sent from my Nexus 7 using xda premium
speedygonzo said:
I was just wiping my tablet to get it ready to turn in to best buy so they can exchange me for the Infinity, and I'm just doing my final data wipes of the tablet and I chose to wipe it from the settings menu. Since I'm rooted and have CWM Recovery, when I wiped, the tablet was probably looking for the stock recovery and won't boot back into the ROM anymore it just continually boots back into recovery. I followed the unbrick guide in the Dev section. But only issue is that. ADB won't recognize my prime. Also, I have nothing in my internal storage, so I can't flash a ROM...
Any advice?
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Try installing universal naked drivers on the PC and try ADB again.
Ok, I'll try that. Thanks for the reply!
Sent from my Nexus 7 using xda premium
I ran into the issue...took me 3 days to get my PC to recognize the prime....tried universal drivers, 3 different computers...and then one day it magically appeared
Sent from my ADR6425LVW using xda premium
Dang, well hopefully I can fix it before my mom leaves to Chicago on Friday. (I'm passing down my Prime to her since she got me the Nexus 7)
Thanks for the info though!
Sent from my Rooted Nexus 7 using xda premium
So i tried to work on my prime earlier today, and i drained my battery on purpose (it only had like 20% left)
And when I went to power it on after charging it for like 20 minutes, it does not turn on. The only feedback I get is the LED on the power button blinking 3 times.
Sent from my Rooted Nexus 7 using xda premium
I had the same thing happen to me. Once you get your drivers installed and adb recognizes it you'll be fine. Its literally a 5 minute fix. What recovery are you running btw?
Edit. Saw in op you're running CWM.
Sent from my SCH-I535 using xda premium
Now, when I do get the drivers installed and ADB does recognize my Prime, what commands do need to type? I'm assuming "adb push" and push a ROM? I'm not that great with ADB
Sent from my Rooted Nexus 7 using xda premium
Yea, the command is
Adb push directorywhereromislocated\rom.zip /sdcard/rom.zip
You may have to use /system/data if you get an error though
Also, i put the rom @ C:\ because for some reason, it wouldn't push from the adb folder, so my command looked like this
adb push C:\rom.zip /sdcard/rom.zip
Edit: If you're using windoze
Sent from my Transformer Prime TF201 using Tapatalk 2
speedygonzo said:
Now, when I do get the drivers installed and ADB does recognize my Prime, what commands do need to type? I'm assuming "adb push" and push a ROM? I'm not that great with ADB
Sent from my Rooted Nexus 7 using xda premium
Click to expand...
Click to collapse
Save yourself a lot of grief, put the rom in the same folder on the computer as your adb.exe is, this eliminates the need to put in the proper path. So then it is adb push [name of rom].zip /sdcard/
or
adb push [name of rom].zip /sdcard/media/
If this is the first time you are trying this, I would suggest trying to push a small text file first, this way you are not wait 5 minutes to find out it failed.
Note do not use the brackets, and for ease of use, right click the rom file, go to properties and copy the name of the file then right click and paste it in the command window, this way you won't mistype it.
Also proper use of the cmmand window is go to the folder where adb.exe is, press and hold the shift button then right click in the window and select open command propmt here.
In the excitement of wanting to try out Sense 5.0, I did what was suggested and flashed the "Beastmode" Kernel.
After flashing, my current rom (Viper DNA) stopped booting. It's in a constant bootloop now.
I wasn't prepared and didn't place the new Rom that I wanted to flash on my SD Card (because it was still downloading.)
Now, the only backup and the Rom I have on my SD Card is ViperDNA, which won't boot.
How do I mount my USB and push the file onto my phone from my computer, when it doesn't boot?
Use adb push romfile.zip
Sent from my HTC6435LVW using xda app-developers app
Edit: ^beat me to it lol
That's exactly what I was thinking but at what point do I plug the phone in?
I've tried:
-the phone completely off - and the "adb devices" isn't detecting my phone.
-in recovery - not detecting my phone.
So when do I plug it in, as in as what screen?
In fastboot, "fastboot devices" seems to be working fine.
arozer said:
That's exactly what I was thinking but at what point do I plug the phone in?
I've tried:
-the phone completely off - and the "adb devices" isn't detecting my phone.
-in recovery - not detecting my phone.
So when do I plug it in, as in as what screen?
In fastboot, "fastboot devices" seems to be working fine.
Click to expand...
Click to collapse
You do it in recovery, you may need to turn on the adb service depending on which recovery your using.
Sent from my HTC6435LVW using xda app-developers app
Bigandrewgold said:
You do it in recovery, you may need to turn on the adb service depending on which recovery your using.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
I'm using Clockword v6.0.2.7 (The touch one).
How do I turn on "adb service"? I'm not even quite sure what that means.
arozer said:
I'm using Clockword v6.0.2.7 (The touch one).
How do I turn on "adb service"? I'm not even quite sure what that means.
Click to expand...
Click to collapse
update to the newer CWM recovery 6.0.2.8
Okay, I finally got it mounted and now ADB is recognizing the device.
Now, how exactly do I push it to my SDCard location?
As far as I understand, I tried:
adb push C:\AndroidSDK\android-sdk-windows\platform-tools\Sense_5.0_Beta_.signed.zip
but it's not appearing on my SD Card.
Am I supposed to tell it WHERE to be pushed to?
If so, what is that?
Edit:
I did
adb push C:\AndroidSDK\android-sdk-windows\platform-tools\Sense_5.0_Beta_.signed.zip /sdcard/Sense_5.0_Beta_.signed.zip
And I THINK it's pushed. (took forever)
However, I don't see it on my phone SD card through recovery.
Where did it get pushed to??
Isn't that what sideloading in CWM does, or is it different?
Sent from my HTC6435LVW using xda app-developers app
arozer said:
Okay, I finally got it mounted and now ADB is recognizing the device.
Now, how exactly do I push it to my SDCard location?
As far as I understand, I tried:
adb push C:\AndroidSDK\android-sdk-windows\platform-tools\Sense_5.0_Beta_.signed.zip
but it's not appearing on my SD Card.
Am I supposed to tell it WHERE to be pushed to?
If so, what is that?
Edit:
I did
adb push C:\AndroidSDK\android-sdk-windows\platform-tools\Sense_5.0_Beta_.signed.zip /sdcard/Sense_5.0_Beta_.signed.zip
And I THINK it's pushed. (took forever)
However, I don't see it on my phone SD card through recovery.
Where did it get pushed to??
Click to expand...
Click to collapse
You pushed it directly to the root of the sdcard... In the recovery just scroll down till you see it
Sent from my HTC6435LVW using XDA Premium HD app
---------- Post added at 01:14 AM ---------- Previous post was at 01:14 AM ----------
cquick97 said:
Isn't that what sideloading in CWM does, or is it different?
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Side load would actually have flashed it. What he did was just pushed it to the sdcard
Sent from my HTC6435LVW using XDA Premium HD app
Hey
so my computer, running Win7Pro x64, is not recognizing my phone (HTC DNA verizon) in fastboot mode. it can see it in ADB both in android and recovery.
i'm trying to either follow moonshine or rumrunner to get my phone to go into s-off so that i'll be able to install the ROM i want.
little back story -
my daughter (11 months) was playing with a baby app and got into the phone settings and somehow made it so the notification bar was gone (though the settings still said it should be there) and also made it so the UI kept crashing. i tried reinstalling my ROM didn't correct it so i reset bask to factory. it got it back up and working
at this point i noticed there is an update for my ROM and so i went to install it and it got stuck at the boot screen. so i followed some tips from a guy in the ROM thread and sideloaded stock so i can attempt to go s-off. this is where i am now.
i'm not sure why fastboot is not working correctly. anyone have any ideas?
When you plug your phone in does it say fastboot USB
Sent from my dlx using XDA Premium 4 mobile app
thayl0 said:
When you plug your phone in does it say fastboot USB
Sent from my dlx using XDA Premium 4 mobile app
Click to expand...
Click to collapse
yes it does
trinity343 said:
yes it does
Click to expand...
Click to collapse
Have you tried reinstalling ask? Just to make sure some files that requires fastboot hadvnt gone missing
Sent from my dlx using XDA Premium 4 mobile app
thayl0 said:
Have you tried reinstalling ask? Just to make sure some files that requires fastboot hadvnt gone missing
Sent from my dlx using XDA Premium 4 mobile app
Click to expand...
Click to collapse
yeah i did. on this particular computer it was a brand new installation as well. though i suppose i could try again just to see what happens.....
So if u boot Ur phone normal... It will pop up Ur sdcard
Sent from my dlx using XDA Premium 4 mobile app
thayl0 said:
So if u boot Ur phone normal... It will pop up Ur sdcard
Sent from my dlx using XDA Premium 4 mobile app
Click to expand...
Click to collapse
sometimes.
i did find that it was loading fine on my laptop. it was my desktop that wasn't working correctly. laptop recognizes the phone in fastboot.
Are you typing "fastboot devices" or "adb devices" when your phone is in fastboot?
Sent from my HTC6435LVW using XDA Premium 4 mobile app
jnorrisman said:
Are you typing "fastboot devices" or "adb devices" when your phone is in fastboot?
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Fastboot devices. I'm only hitting adb devices when in recovery side load or when android is running
Sent from my HTC6435LVW using xda app-developers app
yeah... don't know why but it just wasn't working on my desktop. i connected to my laptop and it worked fine. guess my laptop will forever be my android 'hacking' computer even though it's 5 years older then my desktop... eh who knows. i'm good now though this thread can be closed
same problem
when i try to update the phone manually using win 8.1 , the phone is not recognised after the command adb reboot bootloader, when i give the next command fastboot oem rebootRUU it says waiting for the device , please help me
schoolguy_10 said:
when i try to update the phone manually using win 8.1 , the phone is not recognised after the command adb reboot bootloader, when i give the next command fastboot oem rebootRUU it says waiting for the device , please help me
Click to expand...
Click to collapse
Windows 8.1 broke the fastboot drivers. AFAIK there is no workaround or fix. Use another computer.
Update... you can go back to windows 8.0 by going to >settings >change pc settings, then I think it's the middle option to restart system and saves your files. This got me back to windows 8.0 and now my fastboot drivers work again.
i am also unable to go into fastboot mode,,but surprisingly adb recognized my devices,,but when i type "adb reboot bootloader" after that i get an error USB malfunctioned !!!,,please help me to unlocked my bootloader??? HTC DROID DNA,HBOOT 1.54.00 ,Firmware 3.06,,os4.2.2, sence 5
I've searched and not found anyone with my exact issue so please forgive if this redundant.
I am unlocked and s-off with CWM v6.0.4.5. I've been on CM11 nightlies and unable to get my pc to see the phone(vista 32bit). I flashed back to CM10.2 and could then see the phone in windows. I wanted to install CM11 again with a clean start so I moved Rom and gapps to the pc and wiped and formated EVERYTHING in CWM intending to then sideload CM. Now I cannot get my pc to see the phone at all. I've tried uninstalling and reinstalling HTC sync, tried different usb cables and ports and tried a different computer(windows 7 64bit) all to no avail.
Are there any tricks that can be done with drivers to make the pc see the phone or is there any other way for me to get files back on the phone. Any help is greatly appreciated.
In settings goto storage. Then open the menu in storage (either the 3 dot menu or the hardware button if remapped) and you will be able to pick USB COMPUTER CONNECTION
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Here
Sent from my HTC6435LVW using XDA Premium 4 mobile app
djelement1 said:
In settings goto storage. Then open the menu in storage (either the 3 dot menu or the hardware button if remapped) and you will be able to pick USB COMPUTER CONNECTION
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for the reply. I probably should have clarified that there is not a bootable rom on the device. The device has the bootloader and recovery and nothing else on it at all. To farther clarify, my pc does see my device as HTC6435LVW, it simply won't find the drivers even though they are installed and when I type "adb devices" in a command prompt it doesn't find my phone. Also tried putting the phone into fastboot and searching for "fastboot devices" and nothing comes up that way either.
gatorbyte said:
Thanks for the reply. I probably should have clarified that there is not a bootable rom on the device. The device has the bootloader and recovery and nothing else on it at all. To farther clarify, my pc does see my device as HTC6435LVW, it simply won't find the drivers even though they are installed and when I type "adb devices" in a command prompt it doesn't find my phone. Also tried putting the phone into fastboot and searching for "fastboot devices" and nothing comes up that way either.
Click to expand...
Click to collapse
Your probably going to laugh. But download PDANet and it will install adb needs to push files to your phone.
thayl0 said:
Your probably going to laugh. But download PDANet and it will install adb needs to push files to your phone.
Click to expand...
Click to collapse
THANK YOU! THANK YOU!!!!!! I've been sitting with a dead phone for days trying to figure this out. You saved me having to go buy another phone.
Guessing it worked?
Sent from my HTC6435LVW using XDA Premium 4 mobile app
thayl0 said:
Guessing it worked?
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It did! As soon as I installed pdanet adb was able to see my phone. Sideloaded CM11 with no issues. Thanks again.
gatorbyte said:
It did! As soon as I installed pdanet adb was able to see my phone. Sideloaded CM11 with no issues. Thanks again.
Click to expand...
Click to collapse
Your welcome.
Sent from my HTC6435LVW using XDA Premium 4 mobile app