yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] timothydonohue:
took me a bit to get into the thing myself after > 4.2 update

i'm on ubuntu

i had to use the terminal command

android update sdk --no-ui

a couple of times to get the thing actually updated. using just

android update sdk

wasn't cutting it for some reason. probably because i'm stupid and didn't fiddle with it enough.

then, realized when i STILL couldn't access the device (even after accepting the computer's RSA key on my n7),

it was because i had previously put a now deteriorated version of adb in /usr/bin. so, i rm'd it (navigate to /usr/bin and

sudo rm adb

then navigate over the folder whereeveryouputyoursdk/platform-tools/ and

sudo cp adb /usr/bin

that should be the new version of adb into /usr/bin. remember, do all that after running the

android update sdk --no-ui

a few times

peace
[Android Q&A, Help & Troubleshooting] svs57:
Long time I play with adb (1.0.31) from Linux without problem.

Today I flash new kernel (GT-I9505_AdamKernel.V1.6 then try Abyss-GT-I9505-1.6.1)

Got abd "device offline"

I come back on KT-SGS4.

adb works.

Can anyboby explian be why adb down't work with some kernels?
[Android Q&A, Help & Troubleshooting] LastStandingDroid:
ah great i thought there was an issue with my adb and you wrote the solution :)
[Android Q&A, Help & Troubleshooting] WaveMaster1406:
Thanx man you saved me !!!
[Android Q&A, Help & Troubleshooting] Prashanth Meesara::


Thanks
[Android Q&A, Help & Troubleshooting] edounn:
I still had this problem on OSx and Ubuntu in cli.

what i've done on both to address it is, update the SDK to get the newest adb. (i'm suing 1.0.31)

killall adb

then turn off USB debugging on device.

start new adb (doesn't work nothing to connect to)

then turn on USB debugging and suddenly you get the pop up on the android device that says "always allow this computer at xxx"

test adb devices and should show 'device' instead of 'offline'

or try sudo, unplug the device, run adb under sudo on the desktop (sudo adb kill-server; sudo adb start-server), then plug the device back in.

yay!
[Android Q&A, Help & Troubleshooting] es0tericcha0s:
When it does that, go to Developer Options and Revoke Permissions and replug it back in. If that isn't it, then make sure you have the newest version of adb. Have had that happen on a couple of times on newer Samsungs.
[Android Q&A, Help & Troubleshooting] maxritz:
Had the same problem on my q1010i.

1) Killed all the adb.exe active

2) Killed Moborobo and mobilego from taskmanager.

3) I changed the usb port

It works now.
[Android Q&A, Help & Troubleshooting] g511:
Well, for me works:

and my phone asks for authorization!
[Android Q&A, Help & Troubleshooting] MrCancela:
Hello, I have an LG F180L with Android 4.4.2 and when I run adb devices it appears offline. However I have not this problem with my Galaxy S4 (Android 4.4.2 also). I have tried using different USB 2.0 ports and sdk is updated. I will be grateful if someone could help me.
[Android Q&A, Help & Troubleshooting] jkolner:
Tried everything, change usb cable, update adb, different usb port.

It turned out to be some USB 3 drivers that had some how been installed. Disabled them in Device Manager and adb is online again.
[Android Q&A, Help & Troubleshooting] vaibhav.ravi:
Thank you, helped solve my problem too :) :)
[Android Q&A, Help & Troubleshooting] kikodog:
Here my solution

I think adb exe is too old thats why not request autorization in mobile

here my tutorial on video.

https://www.youtube.com/watch?v=ltR2uQJxNRw
[Android Q&A, Help & Troubleshooting] ivancorpiz:
It works for me - maybe another solution :cyclops:

I use gt-s5360 cm11 with my own mods

I lost adb connection to windows so I can't work, then:

device connect to pc/laptop

go to CWM

advanced

power off

wait reboot!

yes! windows reconize my device again > android Phone > SAMSUNG Android ADB Interface

thanks everybody for your tutorials
[Android Q&A, Help & Troubleshooting] hinix:
I have same problem like others here. Nexus 5 16GB. ROM Cataclysm (5.1), kernel; ElementalX. I already updated adb to 1.0.31. Tried restart device, adb server, computer. I can't find file with keys in my device. I don't have a /data/misc/adb directory. I tired 2 diferent cables (from Z1 i Note3. I don't have stock cable now), 3 different ports (both 3.0 and 2.0), even via hub to be sure. And is still ofline. I tried revoke permission, turn off/on debug mode. My operating system to Win7 x64. Debugging aplication from Android Studio works perfects. At first debug i saw question about allow fingerprint on Nexus. But still is offline in comand line.

What can I should try?

---------- Post added at 07:53 PM ---------- Previous post was at 07:30 PM ----------

Problem solved. From few years I'm using only adb.exe and two dll's. It's from times before I started some app developing. These files works great with my every phone. I put them to /System32 or /SysWOW64 for easiest usage. I updated this exe. Few minutes ago I found /platform-tools from SDK. I tried adb.exe (it's 1.0.32) from this location and it WORKS! At first sho i get psecurity pop-up. Now my 'old' version works too.

I do another quick research (revoke permission, try again with 'my old' 1.031 - nothing, download from Internet 1.0.32, manual update 'old one', restart cmd, and I get pop-up and everything works. So my conclusion is:

To get security pop-up on the device we need adb version 1.0.32 instead of 1.0.31 like nouvelle-adr wrote here:

Funny thing is that about 1.0.31 Google wrote on devs page:

Source: http://developer.android.com/tools/device.html

Anyway - form me works adb 1.0.32
[Android Q&A, Help & Troubleshooting] sebastjanp:
Wooorks

Thanks I was loosing my mind :D
[Android Q&A, Help & Troubleshooting] vikrantsingh47:
this was simple in my case

in terminal emulator, i did

setprop service.adb.tcp.port -1
su
stop adbd
start adbd

i just terminated the adb.exe process in task manager, and connected my phone back. enter "adb devices" and it worked. i am on windows 10.
[Android Q&A, Help & Troubleshooting] Rohganthompson:
Xperia Z3 Same problem!

Well i tried to root my Z3 and failed.

im new to Android and how it all works, thought following a tutorial would be ok but i must have gone wrong somewhere....

Basically i am able to get to recovery (clockworks (Or somthing)

i have SDK all set up and drivers etc. my cmd window picks up my device "adb devices"

List of devices ......

BHSDASD"!£$!£$142 < > OFFLINE!

I have tried every soloution on this thread (Thank you all btw) But i still cant get it to work... and i need my phone!!!!!!!!!!!!!!!

i realy wanted to root it but ended up somehow removing everything on the phone, it says No OS when i go to "System" in recovery

and when i go to boot up obviously it either gets stuck on 1 of the load screens or it Boot loops! i can enter the "Connect usb and hold ^ vol" mode (bootloader?)

And i can get to recovery press up and down volume 1 after another.

My brain is frazzeled i have spent 10 hours serching the web trying to fix it... or atleast get a better understanding but everything here i have tried and no luck please help me!
[Android Q&A, Help & Troubleshooting] xomikronx:
OMG thank YOU!!
[Android Q&A, Help & Troubleshooting] JaS H:
Fix adb device offline error.

I was using adb version 1.0.26. It worked fine in my 5.0 and 4.0 devices until I installed Android studio and SDK. After installing them, the 'adb devices' command returned device ID with status as 'offline' in my 5.0 device, while the 4.0 device was shown as 'Device' which obviously means it's online. Then I have tried with adb version 1.0.32. which returned both as 'Device'.

I think, the Android SDK should be up to date if the 1.0.26 or any other older version than 1.0.31 is used. There came no problem before installing the SDK. But if it is installed, it should be up to date for the older adb-s to function properly. Else adb should be 1.0.31 or higher.

I have tested it with the most possible sdk updates. 1.0.32 version works very well.
[Android Q&A, Help & Troubleshooting] lemics:
Fantastic, it solved my problems,

thanks.

Michel
[Android Q&A, Help & Troubleshooting] 750Mythique:
Huge thanks. this beats all issues I was having. Great tricks.
[Android Q&A, Help & Troubleshooting] Jorge Doguim:
ADB device offline

This is what worked for me. . .

Located the OLD ( 1.0.26 )version being used by my ADB programs: It was in the WINDOWS folder of root directory [ WIn 7 (64)]

Renamed adb.exe to adb.old

Problem fixed.
[Android Q&A, Help & Troubleshooting] kpoccep:
How to access adb in boot mode?

I have Amazon Fire HDX 8.9 4gen, I ****ed up, and now it's in endless loading. I installed and try to conect adb, it shows device is unauthorized, when I make adb kill-server and adb devices it shows offline. I installed drivers from amazon site, and adb from a android (1.0.39), so drivers should be up to date. I tried 3 diffrent usb cables, and nothing. I cannot get the popup for acception cause tablet cannot even load, so how can get into adb. Any ideas? :rolleyes:
[Android Q&A, Help & Troubleshooting] aguy46:
thanks u
[Android Q&A, Help & Troubleshooting] Eversmile23:
I have a peculiar situation. My device shows 'device unauthorized' when connected to my laptop. To add to my woe, I have forgotten the screenlock password of my android device, as a result I can not access the 'settings' in my device. So, I can not apply 'revoke USb debugging authorization' and try adding it again. Can I do this in any other way?
[Samsung Galaxy Nexus] beekay201:
In fastboot, there's no fast charge, since there's no Android running aka no Android kernel running.

Sent from my Nexus
[Samsung Galaxy Nexus] 7ontheline:
Thanks for the response.

I am running Win7. Like I said, I have tried connecting my wife's Nexus to the same computer and it is recognized as usual. The only reason I thought it had something to do with FastCharge was that toggling it has an effect on the charging capabilities of my phone. When I boot into FastBoot the phone still does not show up in the Toolkit and running any operation in the Toolkit that uses FastBoot gets hung on "waiting for devices."

My latest experiment is to Flash a Nandroid of a Stock Nexus Image. However, I have not been able to find flashable stock image! Seems like something that would have been a common file so if you are aware of any Stock Nandroid Backups I would love to try that.
[Samsung Galaxy Nexus] beekay201:
I don't use toolkits, so I don't know how to help there. Does the device get recognized under Device Manager as a fastboot interface? Have you followed http://xdaforums.com/showthread.php?t=1812959? Tried the Universal Naked Drivers?
[Samsung Galaxy Nexus] 7ontheline:
My device does not get recognized within Device Manager. No yellow exclamation mark, no mention of a connected device, nothing. When my wife's Nexus is connected it shows up as expected and communicates just fine via adb. I have followed the guide you mentioned and have installed ROMs many many times with nor problems previously. I have tried the Universal Naked Drivers. I uninstalled all other drivers and installed these. They work as expected with another Nexus, just nothing with mine. Starting to look like I may just be out of luck here.
[Samsung Galaxy Nexus] beekay201:
You seem to be confusing stuff... Fastboot is not ADB, and you have to feed the same driver to windows twice.

You've done this? Sure the USB port doesn't have a bent pin or something?

Sent from my Nexus
[Samsung Galaxy Nexus] tdf666:
My phone is doing the exact same thing. Started about 2 weeks ago. I can't remember but I think it started after flashing the latest liquid smooth rom. I don't think it was a dirty flash but hell I can't remember.
[Samsung Galaxy Nexus] 7ontheline:
Let me know if you figure anything out. I am just dealing with it right now using the SoundAbout App and rebooting my phone whenever it won't charge. It is pretty annoying, but I am at a loss for fixes at this point.

I am not really confusing ADB and Fastboot. I understand that they are two separate ways of communicating with the phone via USB. However, as I stated, there is no USB connectivity other than for charging.
[Samsung Galaxy Nexus] tdf666:
I'm at a loss. Then the other day I got down to 13 percent battery and it started shutting off. I think I'm just going to get another phone. This has been the best and worst phone I've ever had.
[HTC Wildfire S] thehacka1:
Alright this thread will no longer be maintained. See all changes to the rom here: https://github.com/thehacka1/htc_sense_4_marvel
[HTC Wildfire S] Olivier:
Have you considered about something similar to INT2EXT? You can do what you want, Sense is just huge.

First of all, we should mount the sd-ext.

run_program("/sbin/mkdir", "/sd-ext");
run_program("/sbin/busybox", "mount", "-t", "auto", "/dev/block/mmcblk0p2", "/sd-ext");

then, we should format it.

run_program("/sbin/busybox", "rm", "-rf", "/sd-ext/*");
run_program("/sbin/busybox", "rm", "-rf", "/sdcard/.android_secure/*");

After that, we create folders on our ext partition: (the "_s" stands for "second" I guess)

run_program("/sbin/mkdir","/sd-ext/app_s");
run_program("/sbin/mkdir","/sd-ext/system_s");
run_program("/sbin/mkdir","/sd-ext/usr_s");
run_program("/sbin/mkdir","/sd-ext/media_s");

Now, we can extract the stuff to the folder we just have created:

package_extract_dir("sd-ext/app_s", "/sd-ext/app_s");
package_extract_dir("sd-ext/media_s", "/sd-ext/media_s");
package_extract_dir("sd-ext/usr_s", "/sd-ext/usr_s");
package_extract_dir("sd-ext/system_s", "/sd-ext/system_s");

and set the permissions:

set_perm_recursive(0, 0, 0755, 0644, "/sd-ext/app_s");
set_perm_recursive(0, 0, 0755, 0644, "/sd-ext/media_s");
set_perm_recursive(0, 0, 0755, 0644, "/sd-ext/usr_s");
set_perm_recursive(0, 0, 0755, 0644, "/sd-ext/system_s");
package_extract_dir("bootanimation", "/sd-ext/media_s");

Do you still think that the size is the problem? :D
[HTC Wildfire S] thehacka1:
No. I have to build the kernel again using a different exportBOOTPATH
[HTC Wildfire S] thehacka1:
Here is the guide I am using. http://xdaforums.com/showthread.php?p=27327943
[HTC Wildfire S] Olivier:
Be careful with that. :D
[HTC Wildfire S] Olivier:
I think that you could brick your device easily.
[HTC Wildfire S] Nightshadow931:
I don't think that you can brick your device if you're not S-OFF.I mean on hard brick.

Correct me if I'm wrong though.

By the way, good luck with porting, many have tried in the past, but they failed in the end.They said it's impossible to port sense 4 to our device, since it's armv6.
[HTC Wildfire S] thehacka1:
I will not give up. If it is impossible then I will find another way to get it.
[HTC Wildfire S] shahkam:
+1 for your determination and your positive attitude good luck !
[HTC Wildfire S] izi501:
You should symlink too ;)

I would be pleased to be a tester but as I have exams now it will be difficult... Anyway I really hope you will succeed :)
[HTC Wildfire S] Olivier:
Yeah I know that, but that's only a part of the updater-script :)

Gesendet von meinem HTC Wildfire™ S mit Tapatalk 4 BETA
[HTC Wildfire S] thehacka1:
Found a funny way to port sense 4 easily. :D
[HTC Wildfire S] izi501:
Wow are you sure it works ?

Envoyé depuis mon HTC FeuSauvage S avec CM10.1 :D
[HTC Wildfire S] thehacka1:
I have a SENSE 4 Gingerbread rom that BOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOTS!!!
[HTC Wildfire S] Kevinjoa:
Can you please upload it. I am really nervous and wanna test it, please.
[HTC Wildfire S] thehacka1:
Uploading...

Features

*Based on gingerbread not ics for more stability.

*LauncherPRO and official sense 4 Rosie fused together.

*Official Sense 4 lock ring.

*Official Sense 4 widgets.

*The rest is sense 3.5 but extremely smooth.
[HTC Wildfire S] thehacka1:
Teaser.
[HTC Wildfire S] Kevinjoa:
Thats cool and bugs are only of sense 3.5 am I right ??
[HTC Wildfire S] izi501:
Could you add please the email and SMS apps ? If possible only! Anyway, thanks a lot for all your work !

Envoyé depuis mon HTC FeuSauvage S avec CM10.1 :D
[HTC Wildfire S] 4ndaKava:
We appreciate your work thehacka1 :) One year ago 3 devs worked on it. Now 1 dev is doing everything.

Good luck with it. :)
[HTC Wildfire S] thehacka1:
Oh dear. This can't be good. Maybe it's not something you need to patch. Try parsing the error within the log cat.
[HTC Wildfire S] thehacka1:
Going to start development after breakfast. Breakfast is important.
[HTC Wildfire S] thehacka1:
Here comes the party!

E/JNIHelp ( 104): Native registration unable to find class 'com/android/server/NetworkManagementSocketTagger', aborting

Time to put my porting skills to the test.
[HTC Wildfire S] Guitarfreak12:
Lol

Sent from my Sense Baby
[HTC Wildfire S] thehacka1:
So lets see here. It says it can't find NetworkManagementSocketTagger but the file is there and is the exact same as the CM9 one. The line says com/android/server instead of Lcom/android/server. So what if the error was not caused by the file but another file relating to this one. The only two files I did not diff properly are AssetManager and SqLiteDatabase. If one of those files happen to be linked to this file then I think we can find a way. However though if the native was missing in one of those files then it would say that in the logcat. But, what if the error was in the other smalis. NetworkManagementSocketTagger$SocketTags or NetworkManagementSocketTagger$1. An error in one of those two could have caused the main smali to abort. [MENTION=4360192]benjamingwynn[/MENTION] what are your views on these ideas/assumptions?
[HTC Wildfire S] 4ndaKava:
Maybe there is somewhere a wrong implentation.. The error says it can't find the file.

And as you said, the file is expected to be somewhere else, so in the directory "com/android/server instead of Lcom/android/Server".

But I really don't know much about android. I just have a bit Java knowledge.
[HTC Wildfire S] thehacka1:
OK I found a line that was different in NetworkManagementSocketTagger$SocketTags.smali (Try saying that 5 times :p) I replaced it and I'm testing now. Please work.

EDIT: Same error. Looking at AssetManager now.
[HTC Wildfire S] thehacka1:
Guys I think I might know how to fix the error. I'll try it. If it works then we'll be very lucky. It has to do with the init.rc.
[HTC Wildfire S] Guitarfreak12:
Good luck!

Sent from my Sense Baby
[HTC Wildfire S] iPlopp4D:
Does the rom boots??
[HTC Wildfire S] Kevinjoa:
Nope, at the moment it just bootloops.

Gesendet von meinem Wildfire S A510e mit Tapatalk 2
[HTC Wildfire S] iPlopp4D:
sad to hear
[HTC Wildfire S] thehacka1:
Didn't work. Guys do you know what is responsible for managing natives?
[HTC Wildfire S] thehacka1:
I decompiled core.jar and found dalvik/system/SocketTagger.smali. Interesting...
[HTC Wildfire S] thehacka1:
[MENTION=4749032]izi501[/MENTION] thanks for trying. I found this: https://groups.google.com/forum/?fromgroups#!topic/android-platform/4qHMBrI88YU The guy tells you how to fix the error. We need to add missing methods to the BOOTCLASSPATH. When I do that the rom gets stuck on the HTC screen. Which is really damn confusing.
[HTC Wildfire S] thehacka1:
This would be so much easier if HTC made Sense open-source. :p
[HTC Wildfire S] xizt1boy:
Problem with libc.so?

F/libc ( 104): Fatal signal 4 (SIGILL) at 0x401ea678 (code=1)
[HTC Wildfire S] 4ndaKava:
Well, JDevs said he got it boot. So he should know what to do.
[HTC Wildfire S] thehacka1:
He's very busy but I'll ask him.
[HTC Wildfire S] thehacka1:
Did you replace any libs?
[HTC Wildfire S] xizt1boy:
This happens to cm9 libc.so, with this lib from sense 4 hanging on the log htc.
[HTC Wildfire S] thehacka1:
Same happens to me. I sent a PM to Jdevs. Until he replies I'm gonna try other methods.
[HTC Wildfire S] 4ndaKava:
You could probably post at similar devies too.. I think devs of other arm6 devices with similar Hardware will be interested in sense 4.
[HTC Wildfire S] thehacka1:
OK. Lets get this thing understood.

A file named NetworkManagementSocketTagger hasn't been found. It can't be patched. It is the exact same as CM9. Why do we get that error? Maybe a problem from libnativehelper.so. In libnativehepler there is JNIHelp.c which is the error from the logcat. If there was a way to decompile a lib. Anyone know a way? If not then there's services.jar. That also does not contain the file but ends up DEXOpting fine. he error is definitely in framework.jar.

But, what about framework2.jar. that file is not located in the BOOTCLASSPATH. I think maybe the 'missing' could be in there. But it's not possible to move the smalis all into framework.jar. If you notice in CM9 famework folder there is only framework.jar and no framework2.jar. This is because the framework doesn't exceed the size. In sense 4 the framework does. So there is 2 framework.jars. The rom currently does not dexopt framework2.jar because that file did not show up in the BOOTCLASSPATH in the init.rc. But when we do mod the init.rc we get stuck at the HTC screen.

Then there's the replacing libs method. I tried this with libnativehepler. An error came up with libdevm. So I copied the libdvm. Then I get the rom failing to start Netd 1.0. That's a big no.

In jellybean kernels there is framework2.jar because CyanogenMod exceeded their framework size. If someone can clone modpunk's CM9 sources and mod init.rc there then this may work.

It's like I'm stuck in a bootloop. :p Anyone got any ideas?
[HTC Wildfire S] thehacka1:
Well framework2.jar was not the problem. Does anyone now where the init.rc part of a kernel is before it is compiled?
[HTC Wildfire S] Guitarfreak12:
Should i ask htc tommorow why sense is not open-source?

Sent from my Sense Baby
[HTC Wildfire S] izi501:
It is impossible to decompile a C program...

If it bootloops, there are two possibilities : either you did not mod init.rc correctly, or framework2.jar is not meant to be DexOpted and all, and is just called by framework.jar. Do you have a logcat of what happens when you add it to BOOTCLASSPATH ?

Envoyé depuis mon HTC FeuSauvage S avec CM10.1 :)
[HTC Wildfire S] thehacka1:
Never mind the old stuff. I've changed the BOOTCLASSPATH from this:

export BOOTCLASSPATH /system/framework/core.jar:/system/framework/core-junit.jar:/system/framework/bouncycastle.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/framework2.jar:/system/framework/android.policy.jar:/system/framework/services.jar:/system/framework/apache-xml.jar

To this:

export BOOTCLASSPATH /system/framework/core.jar:/system/framework/core-junit.jar:/system/framework/bouncycastle.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/framework2.jar:/system/framework/android.policy.jar:/system/framework/services.jar:/system/framework/apache-xml.jar:/system/framework/HTCDev.jar:/system/framework/HTCExtension.jar:/system/framework/filterfw.jar:/system/framework/com.htc.android.bluetooth.jar:/system/framework/wimax.jar:/system/framework/usbnet.jar:/system/framework/com.orange.authentication.simcard.jar

I'm guessing that this should work. I'll test now and report back.
[HTC Wildfire S] thehacka1:
Is this some sort of joke?
[HTC Wildfire S] thehacka1:
Stuck on HTC screen. Every time I mod the BOOTCLASSPAH it gets stuck on the HTC screen. Is there any way to change BOOTCLASSPATH before compiling kernel?
[HTC Wildfire S] Guitarfreak12:
Xd just to know. I will not spam your thread, sorry :o

Sent from my Sense Baby
[HTC Wildfire S] thehacka1:
Just pushed all commits to GitHub. If anyone wants to help then feel free to fork the repo. https://github.com/thehacka1/htc_sense_4_marvel
[HTC Wildfire S] thehacka1:
New repo for special kernel modifications. https://github.com/thehacka1/htc_sense_4_marvel_kernel
[HTC Wildfire S] xizt1boy:
When I edited the BOOTCLASSPATH is normally getting bootloop on android log, not stuck on htc screen.. o.O
[HTC Wildfire S] Guitarfreak12:
Maybe you did something wrong? I think not, cuz you're one of the best porers outta here

Sent from my Sense Baby