Develop Bugs

Can someone offer some guidance? Please.

Hey guys. Please forgive anything dumb I might say, and also that I've searched a bit for this, on google and on xda, but seem to be getting a bit confused. First, let me say, I rooted my evo months ago, using Unrevoked 3.21. I never really have had to use ADB for anything, I use terminal emulator or Root Explorer for anything I have needed to do. My friend just got an Evo today, and I'm assuming it will come with 3.70 software and hboot 2.1. She wants me to root it for her, which I will do, once I feel comfortable with the steps I need. I have followed ziktroniks thread of how to root the new hboot since it was called "like a boss" edition, and I feel like I shouldn't have a problem doing that. I can follow instructions pretty well. The problem I'm having is, since I rooted using Unrevoked 3.21, and I've never had to use ADB, I'm a little confused about what I need to do, and what drivers I need to install to get ADB working. I know that at the time I rooted, I installed Unrevoked hboot drivers on my computer. I downloaded the android SDK tools, but am having trouble getting it set up. When I try to run the installer, it says "android SDK relies on the Java SE Development Kit (JDK). Then it provides a link to the java website, and I downloaded and installed the JDK that it pointed me to. However, when I try to set up the android SDK, it brings me to same prompt, saying android SDK relies on Java SE Development Kit, and that i need to install it first, which I thought I already have. I'm sure it's something stupidly simple, and I feel embarassed that I haven't yet got ADB set up, but hey, I guess there's a first for everything. So if anyone could be so kind to help point me in the right direction to getting ADB set up, I'd be very gratefull for that. I've gone long enough without knowing how to use ADB, and I'd really like to get this ironed out.
My computer is running windows vista, 64 bit system, if that helps out at all.
Thanks in advance.

I just came over to check out your question from Myn's thread... I did not have the problem you mention when I set up ADB, so I cann't be of much use there.
I noticed you have WIN 64bit. You may have a hard time finding the drivers you will need for the computer to recognize your phone. If you end up needing them, PM me and I can throw them in dropbox and get a link for you. Good luck with everything.

Yeah, getting the 64 bit drivers might be a problem, but when you do it'll be easy if you remember this:
If you've used Terminal Emulator then ADB is demystified. Once you confirm the drivers are working, ADB is just Terminal Emulator on your computer.
I use Vista (I actually like it!), but I assume you have a Start Menu on W7...open it and at the bottom is the Start Search box. Type cmd and an old-style DOS prompt/box will come up. Once you've used the commands to log onto the phone (sorry I forgot them, but I'm sure they're in the directions, if not PM me and I'll look 'em up) that DOS box is exactly like Terminal Emulator.
And the rest should be easy to follow. It'll make you smile the first time the phone reboots after you issue a command on the 'puter, it did me.
Hope this helps...
[EDIT] here y'go...this is a good one...
http://forum.xda-developers.com/showthread.php?t=502010

Thanks for the quick responses guys, I've made some progress. I will post back in a few and let you know how I'm making out. Thanks again.

k2buckley said:
Hey guys. Please forgive anything dumb I might say, and also that I've searched a bit for this, on google and on xda, but seem to be getting a bit confused. First, let me say, I rooted my evo months ago, using Unrevoked 3.21. I never really have had to use ADB for anything, I use terminal emulator or Root Explorer for anything I have needed to do. My friend just got an Evo today, and I'm assuming it will come with 3.70 software and hboot 2.1. She wants me to root it for her, which I will do, once I feel comfortable with the steps I need. I have followed ziktroniks thread of how to root the new hboot since it was called "like a boss" edition, and I feel like I shouldn't have a problem doing that. I can follow instructions pretty well. The problem I'm having is, since I rooted using Unrevoked 3.21, and I've never had to use ADB, I'm a little confused about what I need to do, and what drivers I need to install to get ADB working. I know that at the time I rooted, I installed Unrevoked hboot drivers on my computer. I downloaded the android SDK tools, but am having trouble getting it set up. When I try to run the installer, it says "android SDK relies on the Java SE Development Kit (JDK). Then it provides a link to the java website, and I downloaded and installed the JDK that it pointed me to. However, when I try to set up the android SDK, it brings me to same prompt, saying android SDK relies on Java SE Development Kit, and that i need to install it first, which I thought I already have. I'm sure it's something stupidly simple, and I feel embarassed that I haven't yet got ADB set up, but hey, I guess there's a first for everything. So if anyone could be so kind to help point me in the right direction to getting ADB set up, I'd be very gratefull for that. I've gone long enough without knowing how to use ADB, and I'd really like to get this ironed out.
My computer is running windows vista, 64 bit system, if that helps out at all.
Thanks in advance.
Click to expand...
Click to collapse
I didn't use windows to root my evo, I used a mac, and I do all my java development on a debian linux box, but I think the problem may have to do with your computer using the wrong java by default. On mac and linux, this is controlled by the environmental variable $JAVA_HOME, on windows, I have to assume there is a similar variable, or registry entry - I am looking it up on google right now...
Here we go, I found it - try the directions on this page:
http://confluence.atlassian.com/display/DOC/Setting+the+JAVA_HOME+Variable+in+Windows
hopefully this helps

oh, one other thing, I noticed you said she has hboot 2.10, and I think "like a boss" technique is for hboot 2.02. I think for 2.10 you need to find a thread entitled something like "like wood on fire", or something - although I may be wrong, maybe they updated the "like a boss" thread to cover hboot 2.10 also. Just wanted to make sure you double-check.
Good luck.

Bleys43 said:
oh, one other thing, I noticed you said she has hboot 2.10, and I think "like a boss" technique is for hboot 2.02. I think for 2.10 you need to find a thread entitled something like "like wood on fire", or something - although I may be wrong, maybe they updated the "like a boss" thread to cover hboot 2.10 also. Just wanted to make sure you double-check.
Good luck.
Click to expand...
Click to collapse
Thanks for the heads up. Yea, that thread has been updated and the name has changed nearly daily. Right now it just changed to something else "The final edition" or something like that, yesterday it was "yea, yes im on top" or something like that. ha. I feel confident that I can execute the necessary commands, once i get this damn ADB up and running. I find myself getting confused. I got the java issued figured out, and installed the Android SDK started package. Im reading more before I attempt anything, but the problem I find is that half or more of the stuff I find while searching, is out dated I think. I keep landing threads and such from june and july, and i'm not sure if that's current or obsolete. **** changes so much. So where I'm at now, is the android SDK tools windows is installed, and I'm kinda at a standstill right now. Lol. I see a late night this evening.

And just to mention, to my surprise, her brand new white evo came with : hardware 004, hboot 2.02, software 3.30. I would've thought it'd come with the latest OTA update and hboot etc. Guess I was wrong. Anyways, shouldn't affect much I don't think, if I can ever get ADB to set up correctly. Any other/additional advice is more than welcomed. My pm inbox has plenty of room. THanks

Alright, I am kind of stuck here, I believe that I have everything installed and all the drivers I need, following the links you guys posted here. I open a command prompt, and when it opens initially, it reads : C:\Users\Kyle> Then I enter C:\ android-sdk-windows\tools Then the initial prompt changed from C: \users\kyle> to C:\android-sdk-windows\tools> Thats as far as I get. I tried typing adb devices, and I got 'adb' is not a recognized as an internal or external command.
Im not sure where to go from here. If anyone could point me in the right direction from here, it would be super appreciated. I feel like I'm getting very close here, I just don't know what to check next?? Thanks in advance.

Try this thread. It has a lot of ADB info.
http://forum.xda-developers.com/showthread.php?t=694250

damn, well I think I'm at a standstill for tonight. All the info you guys have posted has been very helpful, however I'm still unable to get it working. I'm pretty sure I have all the drivers that I need installed. I have usb debugging checked on the phone. HTC sync is installed, along with some other drivers that I have found while researching adb. I'm either missing something big, or I'm making stupid mistakes. I just can't seem to get it to work. Any time I type anything 'adb' into the command prompt, it says that adb is not a recognized command, internal or external. So I'm assuming that I must not have the right drivers. Also, just so I understand, if anyone could confirm this. While trying to use adb, does the phone have to be in bootloader? recovery? Booted into the OS, connected as charge only? I seem to be finding conflicting information.

First, I believe you need to get rid of HTC Sync, or at very least make absolutely certain it isn't running...it conflicts with adb.
Second, when it's plugged into USB, make sure your phone's in the "Charge Only" mode.
Third, make sure that under "Settings, Applications, Development" you've got "USB Debugging" checked.
Ok, so when SDK installed itself it should have created a sub-directory (I'm using your screen name as 2nd directory, but substitute the correct one)
C:\Users\K2Buckley\android-sdk-windows\platform-tools
In this directory should be 2 files: "adb.exe" and "adbwinapi.dll". Copy them to your windows\system32 (64?) folder. This will/should allow you to run ADB from any directory, and eliminate the need for you to add anything to your Environment Variables.
Now, if your drivers are running properly and your phone's plugged in, open the Command Prompt by going to the Start Menu, and in the Start Search box at bottom type CMD.
No matter which directory it opens in you should be able to run adb, so as a test, type
adb devices
If it's working, (and it should be), you'll see your phone's ID come up.
You can then do a directory change to whatever directory on your puter you have put all the files you're going to need for your process. For instance I would type
cd c:\users\neil\evo-rooting
That command prompt should pop up. From that point on follow your directions to push, pull, reboot, etc. whatever is called for right from that command prompt. As an example, if I wanted to "push" the file "warm22rom.zip" from that directory to the "zip" directory on my sd card, from that C:\USERS\NEIL\EVO-ROOTING command prompt I'd type
adb push warm22rom.zip sdcard/zip
And if I wanted to reboot my phone from the computer, from that command prompt I'd type
adb reboot
In fact, try that one as a test (be patient, it takes about 20-30 seconds to execute but it's a trip when your phone boots...).
I've just run through this whole process myself just to make sure it works. It does. So if it doesn't work for you, it's gotta be the drivers.
2 other quick checks:
In your computer's Device Manager should be "Android Phone" with "Android Composite ADB Interface" listed if you click the plus sign...
and/or
In Vista, when I plug the phone into the USB port, a little gray square with a white check in a green circle pops up on the right side of my task bar (you should have something similar). This is the "Safely Remove Hardware" icon, and if I double click it it opens a box that shows me what devices/drivers are installed. In that box are 2 things you need to look for: a single line that says "Android Composite ADB Interface" and a short "tree" that reads "USB Mass Storage Device, HTC Android Phone USB Device, Generic Volume - J" (this is my SD Card designation).
If you see these things, or something close, you've got it all installed right.
It's up to you now...go forth and Root, and ADB to your heart's content.
Good luck, I hope this helped.

Fail for me. I feel like a moron. Still can't get this going. Don't know what the hell I'm missing. Anything special that I'm missing about using a 64 bit system? I'm officially stumped. I don't know how much it matters, but can't seem to find any threads/guides specific to the Evo. I keep finding them for moto droid, g1, vibrant. I must be too tired and not thinking straight.
I also keep finding information saying that there should be an adb.exe file in the tools folder, as well as a couple .dll files. I can't find any anywhere on my computer, not even when I search. So does this mean I have either not extracted to the right place or something? Now I'm more lost. F*_k.

Persnlmgr said:
First, I believe you need to get rid of HTC Sync, or at very least make absolutely certain it isn't running...it conflicts with adb.
Second, when it's plugged into USB, make sure your phone's in the "Charge Only" mode.
Third, make sure that under "Settings, Applications, Development" you've got "USB Debugging" checked.
Ok, so when SDK installed itself it should have created a sub-directory (I'm using your screen name as 2nd directory, but substitute the correct one)
C:\Users\K2Buckley\android-sdk-windows\platform-tools
In this directory should be 2 files: "adb.exe" and "adbwinapi.dll". Copy them to your windows\system32 (64?) folder. This will/should allow you to run ADB from any directory.
Now, if your drivers are running properly and your phone's plugged in, open the Command Prompt by going to the Start Menu, and in the Start Search box at bottom type CMD.
No matter which directory it opens in you should be able to run adb, so as a test, type
adb devices
If it's working, (and it should be), you'll see your phone's ID come up.
You can then do a directory change to whatever directory on your puter you have put all the files you're going to need for your process. For instance I would type
cd c:\users\neil\evo-rooting
That command prompt should pop up. From that point on follow your directions to push, pull, reboot, etc. whatever is called for right from that command prompt. As an example, if I wanted to "push" the file "warm22rom.zip" from that directory to the "zip" directory on my sd card, from that C:\USERS\NEIL\EVO-ROOTING command prompt I'd type
adb push warm22rom.zip sdcard\zip
And if I wanted to reboot my phone from the computer, from that command prompt I'd type
adb reboot
In fact, try that one as a test (be patient, it takes about 20-30 seconds to execute but it's a trip when your phone boots...).
I've just run through this whole process myself just to make sure it works. It does. So if it doesn't work for you, it's gotta be the drivers.
2 other quick checks:
In your computer's Device Manager should be "Android Phone" with "Android Composite ADB Interface" listed if you click the plus sign...
and/or
In Vista, when I plug the phone into the USB port, a little gray square with a white check in a green circle pops up on the right side of my task bar (you should have something similar). This is the "Safely Remove Hardware" icon, and if I double click it it opens a box that shows me what devices/drivers are installed. In that box are 2 things you need to look for: a single line that says "Android Composite ADB Interface" and a short "tree" that reads "USB Mass Storage Device, HTC Android Phone USB Device, Generic Volume - J" (this is my SD Card designation).
If you see these things, or something close, you've got it all installed right.
It's up to you now...go forth and Root, and ADB to your heart's content.
Good luck, I hope this helped.
Click to expand...
Click to collapse
Whoa, thanks dude. I'm going to try that right now. I made my last post as you were typing that up apparently, I was ready to throw in the towel, but I'm going to try what you said. Thats very very close to what i was doing, out of all the different tutorials i was trying to follow.
I still couldn't find the .exe or .dll files, so I have no clue what happened there. I'm going to try re installing sdk all together and see if I can get this. Thanks again dude, I know it's late, I appreciate you taking the time to type that up.
. I'm going to give this a try.
And yes, by the way, the drivers listed in my "safely remove hardware" are the same as what you have there. I'm reinstalling the sdk tools now. Hopefully that adb.exe file is there. Before, all that was there was 'adb', among some other folders. I'm assuming there needs to be one that is actually 'adb.exe', correct? when i clicked on the properties of that 'adb' one that was there, it said 'file type: .exe (application)'. Is that what I'm looking for?
http://developer.android.com/sdk/index.html
that is the site I downloaded the sdk tools from, the one for windows that says 'installer ro8 windows.exe (recommended) Does that appear to be the correct one? Once i downloaded that, the installer popped up, installed everything, then sdk manager popped up, requested that I download and install some stuff (android platforms?). Once that's finished, that should be it, right? Just want to make sure I haven't been missing a step or something.
(and thanks for your patience with me, I'm learning though. all the flashing I've done in the past few months, still can't believe that I never took to the time to learn adb. now I know why people are against Unrevoked, cuz I didn't learn sh!t by doing that. A few clicks and I was rooted and flashing away!)
well. I fubared something, ha. This is becoming comical. I followed what you said. The only thing is, which I'm sure this is the issue...after sdk tools installed again, there was still no 'adb.exe' folder in platform-tools. just 'adb'. The adbwinapi.dll was there, and i copied it to "windows/system32" I copied the 'adb' to that folder as well. So either the 'adb' that i copied was incorrect, and I have no idea where that damned 'adb.exe' is at, or i was supposed to move or cut them, rather than copy. either way, i give up for tonight, need some sleep.
when I opened a command prompt, and typed 'adb devices', a windows error with a red x pops up (outside the command prompt) that reads "this application has failed to start because AdbWinApi.dll was not found. Re installing the application may fix the problem". Then I click ok.. Then it says "adb.exe has stopped working, a problem caused the program to stop working correctly. windows will close the program and notify you if a solution is available" HA. DAMn I suck.
Not thinking clearly right now, need some sleep. Thanks again, hopefully we can get this straightened out tomorrow, or later today i guess it is now, damn its late.
Edit!! whoa! My final attempt was to copy the adbwinapi.dll to windows\system (instead of system32), and i believe that worked. I typed in adb devices, and I got "list of devices attached HT0###L00069 device" I assume that's my Evo? Hooray! Thank you so much man, I cannot express how happy I am right now, ha. That adb reboot kicked ass, lol. Now I can learn some stuff.
Finally, last question. My friend (who's phone I was going to root) had to leave hours ago. I was using my phone to do this and get it working. When I go to root her phone, in theory, should it connect to adb just fine at this point? Thanks again man, you were a huge, massive help.

I suck. I had it working. For some reason, through my tiredness and confusion, I thought I had to type "adb kill-server" to exit adb. After I did that, now if I type anything starting with adb, it says:
"daemon not running. starting it now on port 5037
CreateProcess failure, error 2
failed to start daemon
error: cannot connect to daemon"
Have no idea what the eff I did. Tried doing some research, will have to check more tomorrow. I tried adb start-server, and got the same message. Rebooted phone and computer, same thing. So i messed something up. Anyone know what I did and what i could try to get it working again? damn i suck.

k2buckley said:
I suck. I had it working. For some reason, through my tiredness and confusion, I thought I had to type "adb kill-server" to exit adb. After I did that, now if I type anything starting with adb, it says:
"daemon not running. starting it now on port 5037
CreateProcess failure, error 2
failed to start daemon
error: cannot connect to daemon"
Have no idea what the eff I did. Tried doing some research, will have to check more tomorrow. I tried adb start-server, and got the same message. Rebooted phone and computer, same thing. So i messed something up. Anyone know what I did and what i could try to get it working again? damn i suck.
Click to expand...
Click to collapse
The "kill-server" should not have completely disabled ADB. Relax until you get her phone, then do everything you did to yours to hers. It should re-start. Yes, "adb.exe" was the proper file (not folder) to have moved into your computer windows\system(32,64,-) directory, as was the dll file. Obviously. Or it never would've told you the device ID.
You're on the right track.
And, when in doubt, issue that "adb reboot" command. It's not gonna hurt the phone and it'll let you know if ADB is working... Just don't do it halfway through any process.
And stop experimenting with things like adb kill-server, dummy!!! The only way you need to know to STOP adb is you DON'T NEED TO STOP ADB! It's not like a background program that you need to kill when you're done.
The way to "stop" or "kill" ADB is simply not to issue ADB commands. And when you close that Command Prompt box, ADB IS closed.

Okay, I just tried issuing the adb kill-server command. It takes me back to a DOS prompt with no notes. Then I typed ADB and my daemon started back up. I then issued adb start-server and it took me back to a blank (no notes) command prompt.
Don't know why it completely shut down your ADB, but I think when you plug her phone in you'll have a fresh start and it'll all work.
Start with adb devices, then if it shows her ID, issue adb reboot. If the phone reboots, you're good to go forward.
[EDIT] Okay, I just tried something I should've told you to try: without the phone plugged in, open the Command Prompt and type adb devices. Prompt should come back up as below. I then issued adb kill-server. Again, see below, nada. But then I issued adb start-server and got what you see in the string below:
Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\Neil>adb devices
List of devices attached
[blank, so none]
C:\Users\Neil>adb kill-server
[blank]
C:\Users\Neil>adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\Users\Neil>[blank]
Yours should look and work like this. If it does, plug in the phone and get started.
If not, pull out that .38 on the top shelf of your closet. Put in only 1 bullet. Spin chamber. Point at head. Pull trigger.
If you're still standing, (that's a good sign), go back to step one (unplug phone, reboot phone and computer), and try, try again. (Or Google Chat me...I PMd my screen name to you).

Just saw this one...responses in Green
k2buckley said:
Whoa, thanks dude. I'm going to try that right now. I made my last post as you were typing that up apparently, I was ready to throw in the towel, but I'm going to try what you said....
I'm assuming there needs to be one that is actually 'adb.exe', correct? when i clicked on the properties of that 'adb' one that was there, it said 'file type: .exe (application)'. Is that what I'm looking for?
YES INDEED!!
that is the site I downloaded the sdk tools from, the one for windows that says 'installer ro8 windows.exe (recommended) Does that appear to be the correct one? Once i downloaded that, the installer popped up, installed everything, then sdk manager popped up, requested that I download and install some stuff (android platforms?). Once that's finished, that should be it, right? Just want to make sure I haven't been missing a step or something.
All Good
(and thanks for your patience with me, I'm learning though. all the flashing I've done in the past few months, still can't believe that I never took to the time to learn adb. now I know why people are against Unrevoked, cuz I didn't learn sh!t by doing that. A few clicks and I was rooted and flashing away!)
We all have to start somewhere. And I used Unrevoked, too, so had to go back and learn ADB
well. I fubared something, ha. This is becoming comical. I followed what you said. The only thing is, which I'm sure this is the issue...after sdk tools installed again, there was still no 'adb.exe' folder in platform-tools. just 'adb'. The adbwinapi.dll was there, and i copied it to "windows/system32" I copied the 'adb' to that folder as well. So either the 'adb' that i copied was incorrect, and I have no idea where that damned 'adb.exe' is at, or i was supposed to move or cut them, rather than copy. either way, i give up for tonight, need some sleep.
when I opened a command prompt, and typed 'adb devices', a windows error with a red x pops up (outside the command prompt) that reads "this application has failed to start because AdbWinApi.dll was not found. Re installing the application may fix the problem". Then I click ok.. Then it says "adb.exe has stopped working, a problem caused the program to stop working correctly. windows will close the program and notify you if a solution is available" HA. DAMn I suck.
No you don't. You're doing good...
Not thinking clearly right now, need some sleep. Thanks again, hopefully we can get this straightened out tomorrow, or later today i guess it is now, damn its late.
Edit!! whoa! My final attempt was to copy the adbwinapi.dll to windows\system (instead of system32), and i believe that worked. I typed in adb devices, and I got "list of devices attached HT0###L00069 device" I assume that's my Evo? Hooray! Thank you so much man, I cannot express how happy I am right now, ha. That adb reboot kicked ass, lol. Now I can learn some stuff.
Agreed. Totally trippy when you type on the 'puter and the phone reacts
Finally, last question. My friend (who's phone I was going to root) had to leave hours ago. I was using my phone to do this and get it working. When I go to root her phone, in theory, should it connect to adb just fine at this point? Thanks again man, you were a huge, massive help.
Click to expand...
Click to collapse
YES INDEED IT SHOULD CONNECT, and you're very welcome!!
I still really don't understand why anyone has to install SDK if they're only going to tweak their phone and not write programs. That's what SDK is for. I think the whole SDK Install thing is just to get those f-ing USB drivers...which seems patently absurd.
SO FORGET SDK AND JUST CONCENTRATE ON ADB...

Persnlmgr said:
Okay, I just tried issuing the adb kill-server command. It takes me back to a DOS prompt with no notes. Then I typed ADB and my daemon started back up. I then issued adb start-server and it took me back to a blank (no notes) command prompt.
Don't know why it completely shut down your ADB, but I think when you plug her phone in you'll have a fresh start and it'll all work.
Start with adb devices, then if it shows her ID, issue adb reboot. If the phone reboots, you're good to go forward.
[EDIT] Okay, I just tried something I should've told you to try: without the phone plugged in, open the Command Prompt and type adb devices. Prompt should come back up as below. I then issued adb kill-server. Again, see below, nada. But then I issued adb start-server and got what you see in the string below:
Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\Neil>adb devices
List of devices attached
[blank, so none]
C:\Users\Neil>adb kill-server
[blank]
C:\Users\Neil>adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\Users\Neil>[blank]
Yours should look and work like this. If it does, plug in the phone and get started.
If not, pull out that .38 on the top shelf of your closet. Put in only 1 bullet. Spin chamber. Point at head. Pull trigger.
If you're still standing, (that's a good sign), go back to step one (unplug phone, reboot phone and computer), and try, try again. (Or Google Chat me...I PMd my screen name to you).
Click to expand...
Click to collapse
Well I'm awake and rested! Now that I'm not stupidly tired, I think I remember something bad. For some reason, I'm thinking I might've, just possibly, typed adb kill. as opposed to adb kill-server. I probably did just that, killed adb! But yea, even with the phone disconnected, if I type adb devices, i get the same error message, failed to start daemon. Crap. Wonder if I should start all over? Or if "kill adb' did something worse. The reason I tried to do that (which I know I shouldn't have, and I've learned a lesson from it) is because when I tried to removed the device, from the "safely remove hardware", it wouldn't let me stop the "adb compositte interface" because it said something was still using it. I had everything closed, no windows of any sort open. I thought to myself, "hmm, adb must still be connected to my phone somehow, perhaps i need to kill it before I can unplug the phone." So, that was my dumbass reasoning. But I do think I typed "adb kill" When I typed that, no errors came up, and it did indeed allow me to stop the device. However, it's just when I try any other adb commands now. If I type "adb", it pops up a crapload of information, looks like it shows me a bunch of different adb commands. but as soon as I type anything after "adb" such as "adb devices," "adb start-server" or whatever, it gives me the error message and says failed to start daemon. So I believe i effed something up.

k2buckley said:
Well I'm awake and rested! Now that I'm not stupidly tired, I think I remember something bad. For some reason, I'm thinking I might've, just possibly, typed adb kill. as opposed to adb kill-server. I probably did just that, killed adb! But yea, even with the phone disconnected, if I type adb devices, i get the same error message, failed to start daemon. Crap. Wonder if I should start all over? Or if "kill adb' did something worse. The reason I tried to do that (which I know I shouldn't have, and I've learned a lesson from it) is because when I tried to removed the device, from the "safely remove hardware", it wouldn't let me stop the "adb compositte interface" because it said something was still using it. I had everything closed, no windows of any sort open. I thought to myself, "hmm, adb must still be connected to my phone somehow, perhaps i need to kill it before I can unplug the phone." So, that was my dumbass reasoning. But I do think I typed "adb kill" When I typed that, no errors came up, and it did indeed allow me to stop the device. However, it's just when I try any other adb commands now. If I type "adb", it pops up a crapload of information, looks like it shows me a bunch of different adb commands. but as soon as I type anything after "adb" such as "adb devices," "adb start-server" or whatever, it gives me the error message and says failed to start daemon. So I believe i effed something up.
Click to expand...
Click to collapse
Okay, well as I said, **** SDK, it's irrelevant.
"You need the driver only if you are developing on Windows and want to connect an Android-powered device to your development environment over USB."
So, go here ( http://developer.android.com/sdk/win-usb.html ) to get and (re)install the ADB Composite drivers. You should not have to do anything else. If they ask WHERE you want to install them, either direct them to the root of your harddrive, likely C:\ , or if you can set the directory where the DRIVERS (not the program) goes, choose WINDOWS.
Then you should be ready to go back and follow the rest of my instructions easily.
BTW, I assume you've checked UNRevoked.com to see if they have a fix for their super easy, automatic Root process to accomodate the new HBoot?
Jus' askin...
Keep me posted, or GChat me. I'm at my desk...

[Guide] ADB connection between two Android devices

Probably not breaking any ground here (since in hindsight it was blatantly obvious), but I thought I would share anyways...
I own several Android devices, and I'm always playing. well, tonight I was tweaking a few things over adb and got to wondering if I could use adb to connect from one Android device to another. Well, turns out it's pretty easy, if you're rooted...
Both devices need to be connected to the same wireless network.
Install adbWireless from the Playground (sorry, Play Store): https://play.google.com/store/apps/...251bGwsMSwyLDEsInNpaXIuZXMuYWRiV2lyZWxlc3MiXQ..
You only really need it on the receiving device, but I have it on everything anyway.
Copy the Linux adb binary into /system/xbin/ and set the permissions to 755 (rwxr_xr_x), and reboot.
You only really need to do this on the controlling device, but may as well do it on all.
Fire up adbWireless on the receiving device, grant root privileges, and note the IP address
Fire up a Terminal Emulator on the other device, and enter: adb connect <IP address from other device> (you typically don't need to add the :5555 on the end.
Job done! Pretty handy when working from a slate!
I also run dd-wrt firmware on my router, which let's me assign static IPs by MAC address, so the IP for the devices are always the same.
Regards - dr

adb binary is already built in, /system/bin/adb.
besides that, all that's left is get adbd running, and that can be achieved either by an app (like you suggest) or edit init.rc to have adbd as one shot service to allow manual start (doesn't boot with the system). cyanogenmod also has adbd over wireless done like this.
also, one could use an OTG cable to connect devices directly, while i agree adb over wireless is good, adb over ssh would be best.

Valid points.
The adb in /system/bin is a less functional version than the standard Linux binary (94kb versus 156kb); kinda similar to the chown binary, where the recursive function doesn't work...
I'll concede to the rest though...

danger-rat said:
Valid points.
The adb in /system/bin is a less functional version than the standard Linux binary (94kb versus 156kb); kinda similar to the chown binary, where the recursive function doesn't work...
I'll concede to the rest though...
Click to expand...
Click to collapse
Agreed.
Sent from my i9250
edit: checkout this commit @aosp-master: https://android-review.googlesource.com/#/c/41846/
i'll be cherry-picking this one today

danger-rat said:
Valid points.
The adb in /system/bin is a less functional version than the standard Linux binary (94kb versus 156kb); kinda similar to the chown binary, where the recursive function doesn't work...
I'll concede to the rest though...
Click to expand...
Click to collapse
Hi - Where can I get this more functional binary that's half the size of a standard linux binary? I've tried two, they are both around 330Kb, and they fail to run with error "non executable: magic 7F45" because they were not compiled for my ARMV71 processor. I ran chmod 755 on it and when I check the permissions it is executable (-rwxr-xr-x). Can you post a link to the one that's 156kb - I can't find it.

elfaure said:
Hi - Where can I get this more functional binary that's half the size of a standard linux binary? I've tried two, they are both around 330Kb, and they fail to run with error "non executable: magic 7F45" because they were not compiled for my ARMV71 processor. I ran chmod 755 on it and when I check the permissions it is executable (-rwxr-xr-x). Can you post a link to the one that's 156kb - I can't find it.
Click to expand...
Click to collapse
Bumb. Anyone home? Shoot me a link please.

Hey guys,
Now, I have a tablet (running android) and is rooted already (so, I'm ready to get any needed binary on my device). It supports OTG. When I plug in my phone (rooted) using OTG to my tablet, my phone says 'Android debugging enabled' in notifications, is also charging. When I go to TE (Terminal Emulator) of my tab and type: 'adb devices', it displays no device in the list of attached devices (obvious).
And yes, my tab has got OTG host modules in kernel because when I turn on USB mass storage on (in my phone), my tab detects it and I can use it.
Now, my question:
Can I actually do this? i.e., using adb in my tablet (for my phone) via OTG?

Can we run adb from the device to detect itself?
I'm sure you can see why this would be amazing and powerful.. possibly giving root to apps on non-rooted devices with adb's run-as com.package.apk and such?
Is this possible? To have adb run on the Android device and connect to itself? If it is, can you guide me to where to learn it?
Dave :cyclops:

[Guide] Let's get this over with - WebOS install

Welcome to jimmyco2008's Layman's Guide to the Galaxy (Nexus) - Open WebOS Edition!
------------------------------------------------------------------------------------------------------------------------------------
EDIT: I wonder if I can spare you guys all the building and just upload the 1/2 GB WebOS image and Fastboot file... I'm going to try that out, upload them to Google Drive tonight/now, I'll add the link by tomorrow and you guys can try to just download the files instead of building everything, at least for those who just want to try this out. If you're serious about working with this Open WebOS, I recommend going through all the steps to get all the files building gets you, and so you can update your build files as webos-ports.org updates them.
But here's a link to the folder containing the WebOS developer image file (I didn't build the regular image, not sure of the difference) and the fastboot file needed to boot the thing. Get these files, and you can skip to the giant, bolded "LIKE A BOSS" heading somewhere in the middle of the guide below. Keep in mind you still need to meet prerequisites, save the decent resources, if it runs Ubuntu, and ADB/the Android SDK are/is set up, you're clear for takeoff.
Also note that the .ext2 image of WebOS has a different name, relax, it's the same thing!
Download! .. And feel free to mirror, though I doubt demand nor lack of reliability for Google Drive warrants one.
------------------------------------------------------------------------------------------------------------------------------------
Know this before diving in:
- You NEED Linux.. Not OS X, not Windows, some Linux distro... For the Laymen, you'll want Ubuntu 11.10 or above (can't go wrong with the latest 12.10)
- Get 64-bit, no questions asked.
- Building/compiling the WebOS image in Linux/Ubuntu takes A LOT of resources, generally you can build with any old computer, but it'll take a long time.
- I'm saying if you're running Ubuntu full-boot (not in a Virtual Machine), have at least 3GB of RAM and a 60GB hard drive... any decently-modern processor should do, but the slower and older, the longer it will take to build... You're more than welcome to try this with whatever computer you have, just give it plenty of time to do its thing.
- If you're doing this in a Virtual Machine, like with Parallels or VirtualBox, give the Ubuntu Virtual Machine (VM) as much of your computer's resources as possible. For example, I have a 2012 Macbook Pro (240GB SSD, Ivy bridge Intel Core i5 @ 2.5Ghz, 8GB DDR3 RAM @ 1600 Mhz), I gave the Parallels Ubuntu VM 4GB of RAM, 60GB of hard drive space (I'm at 51 GB used and all I did was the minimum to get WebOS on the GalNex) and all of my cores (4) at 100% cap. It took... well, a few hours to build.
- This boots on both the GSM and CDMA Galaxy Nexuses, so toro, toroplus and maguro are all supported, well except for anything related to the radio.. As with anything Galaxy Nexus-related, GSM gets radio stuff working first.
- This procedure boots WebOS tethered, so you can unplug the Galaxy Nexus once WebOS (Luna) is booted, but rebooting gets you back to Android, and you have to do the fastboot boot image thing again to boot into WebOS. So this doesn't touch your Android (or Ubuntu Mobile I guess) setup.
- Ignore the dollar signs ($) and pounds (#) preceding commands, it's just for organization!
- I am not responsible for anything that happens to your phone or any of your property as a result of using this guide... Standard disclaimer.
---------------------------------------------------------------------------------------------------------------
Alright the Layman's Guide to the Galaxy Nexus! (isn't that punny lol)
Preflight Checklist
- Ubuntu 12.10 (probably good with 11.10 or 12.04 as well) 64-bit.
- Java Runtime 6 or 7 (available for download @ Ubuntu Software Center, or if you're a boss with Linux, you can do the Terminal install, you know what you're doing lol)
- Android SDK
- Android Tools installed via the Android SDK Manager (run from Terminal or double click "Android" script, located in sdk/platform-tools (or some other folder in sdk)
- You can access your Galaxy Nexus via ADB on Ubuntu (getting the host to share the Galaxy Nexus with the Ubuntu VM can be a ***** sometimes, make sure ADB finds your Galaxy Nexus via "./adb devices" .
- At least... eh 1-2 GB free on your Galaxy Nexus sdcard0 storage (who out there actually has to check this lol)
- Your Galaxy Nexus' Bootloader is unlocked... At first I didn't think I had to add this, but for the sake of being thorough...
- If # ./adb commands aren't working, like ./adb devices or ./adb reboot-bootloader, and it gives you some error in Terminal, you need to update 'cha libs. Open a fresh Terminal window and enter:
# sudo apt-get install libc6:i386 libncurses5:i386 libstdc++6:i386
Go through all that, tell it yes however many times, and when it finishes, ADB commands should work.
---------------------------------------------------
The Main Event
This is actually kind of boring, you have to literally copy and paste like 10 commands into Terminal for the Prerequisites webos-ports.org dictates.
Enter all this into Terminal one at a time as it processes and finishes each line (by giving you the block cursor back), and remember to answer "y"/yes to all questions!
1$ sudo apt-get install build-essential
2$ sudo apt-get install gawk && sudo apt-get install diffstat && sudo apt-get install chrpath
3$ mkdir webos-ports-env && cd webos-ports-env
4$ wget https://raw.github.com/openwebos/build-webos/master/scripts/prerequisites.sh * Ugh, damn, XDA forums sets this as a URL and shortens it, if you copy and paste directly into Terminal, it won't work...just right click and Copy Link URL or whatever, and paste that separately from "wget".. Do the same for the link below.
6$ sudo sh prerequisites.sh (this takes a while, ~10-20 minutes depending on your internet/hardware)
6$ wget https://raw.github.com/webOS-ports/webos-ports-setup/master/Makefile
7$ make setup-webos-ports
Now you can probably build, I know the official guide says differently, but I've done this MANY times, just hear me out!
1$ cd /webos-ports-env/webos-ports
2$ . setup-env
Now the text preceeding whatever you type should be blue and green (how magical!), if it's not.. Well post below and I'll help you out.
So actually building this, commands vary depending on if you want the developer image or the regular image... In fact a bunch of WebOS not working for me (like apps) may be because I opted to build the developer image... Honestly, I'm not sure what the difference between the two is, it's open source, you should be able to develop on either... If I were you I'd go for the non-developer image, but here's both commands, choose ONE:
*Also, on the webos-ports.org website, they offer advice about speeding up the build by editing the number of threads value in a config file, default value is 4 cores and 4 threads, I changed mine to 8 threads, I dunno, really shouldn't matter unless you're rocking an i7 Extreme Edition or a Bulldozer, you know something with more than 4 processor cores (physical and virtual). If you have less than 4 cores, like you have a Phenom II X2 or an Intel Core 2 Duo, maybe even an older i3, you should be fine with the default 4/4 settings.* If you're into changing the settings, the file you edit (with TextEditor or whatever) is located at webos-ports/conf/local.conf . Lookin' for BB_NUMBER_THREADS and the line above it, both should = 4 by default.
Regular Image (make sure you're in the build environment > Magic green & blue text!)
$ MACHINE=tuna bb webos-image
Developer Image (again, make sure the magic blue and green text is there)
$ MACHINE=tuna bb webos-dev-image
Now the magic happens, if all goes well, within a couple of minutes (or sooner) you'll see "preparing runqueue"... If you look at System Monitor, you'll see it's downloading (at 100 - 400 kbps, even if you have a 50mbps down internet connection) the build stuffs, which takes 1- 3 hours (don't be afraid to use Netflix haha).
It'll actually go between downloading at a rather slow rate and running tasks (over a thousand of 'em)... All in all, give it, again depending on your hardware and internet, like the night (5 - 12 hours), perhaps even more... It'll finish when it finishes. If you get errors at the end, well that's normal, ignore it, you may not even get errors for the regular image, again I've just used the developer image.
-----------------------------------------------------------
Booting Open WebOS *LIKE A BOSS*
Make your life easier and have a file manager window open to webos-ports-env/webos-ports/tmp-eglibc/deploy/images/tuna. Let's call this directory "Foxtrot" for the sake of simplicity.
Okay this is the part where the official guide at webos-ports.org just... ugh... It says to enter this command from your Android SDK /platform-tools folder:
adb push webos-dev-image-tuna.ext2 /storage/sdcard0/linux/rootfs.ext2
Actually it should be (type this in, don't copy and paste):
./adb push *click and drag the webos-dev-image-tuna.ext2 file to Terminal* /storage/sdcard0/linux/rootfs/.ext2
NOTE: Yes, you can click and drag that .ext2 file and Terminal automatically figures out the path, remember that this file is located in webos-ports-env/webos-ports/tmp-eglibc/deploy/images/tuna . Let's call that directory "Foxtrot" for easy reference.
If all goes well, you see the cursor is gone, it's doing its thing- pushing the WebOS image to Galaxy Nexus sdcard0 in a folder called "linux" (as shown above), if you wish to delete this later. Pushing this file took my Macbook about 6 minutes, allow up to 15 minutes for those slower computers out there.
Now reboot your GalNex to the bootloader (you know how to do that)
./adb reboot-bootloader ...or just power off and hold vol up + vol down + power.
Okay here's where the official guide will really **** you up... The file isn't called what the guide states it's called, at least for me...
Type (don't copy and paste this one either):
sudo fastboot boot *click and drag whatever file is closest to "zImage-tuna.fastboot" in our "Foxtrot" directory. Mine had a bunch of numbers, it was like zImage 8246237860837462387462038756012831982 .fastboot. Make sure the file you drag to Terminal ends in ".fastboot", there's one that ends in ".bin".
So: sudo fastboot boot *that file dragged over*
Now it should do its thing, may see a black screen on the Galaxy Nexus for a minute or two. Eventually you'll see a clock where it would be in WebOS (top-middle) and "First Boot" (something like that, I forget) at the upper-left corner.
Now we have to send a couple of simple commands to this WebOS thing from Ubuntu to get Luna (the UI itself) to boot.
You'll see that there is an Ethernet connection in Ubuntu, mine was Wired Connection 2.... Click on the network icon on the top bar in Ubuntu, click "Edit Connections", click on Wired Connection 2, add an Address. Address is 192.168.7.1, Netmask is 255.255.255.0 (actually you can probably get away with entering the default value), Gateway is 192.168.7.2 . Save that bad boy.
Now in a fresh Terminal window, enter, one at a time of course (remember to omit the dollar signs, just good syntax):
$ ssh [email protected]
$ stop LunaSysMgr
$ touch /var/luna/preferences/ran-first-use
$ start LunaSysMgr
Congratulations! Give it a few seconds, you should be in Open WebOS! Woo!
Feel free to contact me if you need help, I made an error in the guide, or you want to help make this a realistic alternative to Android!
Remember, to get back to Android, just pull the battery and reboot normally!
Credit goes to the webos-ports team at webos-ports.org for making this happen!
---------------------------------------------------------------------------------------------------------------
Details about the port!
Hardware acceleration appears to be at least partially working, that's probably about it, calling (and possibly SMS) works on GSM versions of the GalNex. For those of us with CDMA (myself included), this port should work, however about all it will do is boot for now. So it's just for fun atm. Furthermore, it's uncertain as to whether the Verizon or Sprint GalNexes will ever get a fully-working port because they're CDMA. That would be a shame, but we'll just have to see, won't we?
EDIT (after I actually got it booting): Not a whole lot to do with it, I'm hoping someone can work with me to make this port better, or at least get the radio portion going, no one will use this if it can't send and receive calls/SMS... I (with my Verizon toro) was unable to get any apps to actually open, but the UI is EXTREMELY smooth, I mean holy damn, and the on-screen nav light/bar from past WebOS devices is slick and really cool! WiFi turns on and eventually picks up networks, but I was unable to actually connect (though it may work for unsecured networks, never prompted me for a password so..). Bluetooth does not work (again, at least for the toro), and I had difficulty with the orientation, like sometimes it would go landscape but I couldn't get it back to portrait...

...As for the poll, it's pretty pointless, if a mod happens by, please remove it! No need to worry about bricking (for obvious reasons), and the lack of radio support is no excuse, just battery pull and reboot to get back to Android.... No reason to wait till someone else does it, I just did it!...So go for it!
-----------------------------------------------
Re-Booting Open WebOS after doing it once before!
Now reboot your GalNex to the bootloader (you know how to do that)
./adb reboot-bootloader ...or just power off and hold vol up + vol down + power.
Okay here's where the official guide will really **** you up... The file isn't called what the guide states it's called, at least for me...
Type (don't copy and paste this one either):
sudo fastboot boot *click and drag whatever file is closest to "zImage-tuna.fastboot" in our "Foxtrot" directory. Mine had a bunch of numbers, it was like zImage 8246237860837462387462038756012831982 .fastboot. Make sure the file you drag to Terminal ends in ".fastboot", there's one that ends in ".bin".
So: sudo fastboot boot *that file dragged over*
Now it should do its thing, may see a black screen on the Galaxy Nexus for a minute or two. Eventually you'll see a clock where it would be in WebOS (top-middle) and "First Boot" (something like that, I forget) at the upper-left corner.
Now we have to send a couple of simple commands to this WebOS thing from Ubuntu to get Luna (the UI itself) to boot.
You'll see that there is an Ethernet connection in Ubuntu, mine was Wired Connection 2.... Click on the network icon on the top bar in Ubuntu, click "Edit Connections", click on Wired Connection 2, add an Address. Address is 192.168.7.1, Netmask is 255.255.255.0 (actually you can probably get away with entering the default value), Gateway is 192.168.7.2 . Save that bad boy.
Now in a fresh Terminal window, enter, one at a time of course (remember to omit the dollar signs, just good syntax):
$ stop LunaSysMgr
$ touch /var/luna/preferences/ran-first-use
$ start LunaSysMgr
Congratulations! Give it a few seconds, you should be in Open WebOS! Woo!

Got it booting just now lol, and the instructions at webos-ports could be... better, clearer, so if anyone wants to try this out, it doesn't affect their Android installation and you can just reboot into Android easily enough.
If you encounter issues, post here, I should be able to help you out!

jimmyco2008 said:
Got it booting just now lol, and the instructions at webos-ports could be... better, clearer, so if anyone wants to try this out, it doesn't affect their Android installation and you can just reboot into Android easily enough.
If you encounter issues, post here, I should be able to help you out!
Click to expand...
Click to collapse
Would you mind writing a simplified version?
Their instructions are Daunting!

Sure, here's a really layman version, I'll add to it over the next day or so:
Okay so what we're doing is using Linux (specifically Ubuntu if you're following this guide to a tee) to build the WebOS image for the Galaxy Nexus which webos-ports.org put out. Then we're using ADB and Fastboot to push the image to a certain directory within sdcard0 (the emulated SD Card on the Galaxy Nexus), then we're using Fastboot to deploy, not flash (over the Android boot.img), to the Galaxy Nexus to tether-boot WebOS. It actually boots a really basic version, not sure what it's called exactly... From there we connect via ssh (like telnet) to the Galaxy Nexus with IP to send the final commands to initiate Luna (the WebOS UI).
EDIT: Actually I'll edit the OP with the instructions...

Why would anyone want web os? Ugh awful..
Sent from my Galaxy Nexus using xda app-developers app

Why would anyone want iOS? Ugh awful..

Does anyone have a video of this working on a Galaxy Nexus?

Yeah.... I'm not making a video, but there's a couple on YouTube.
Sent from my Galaxy Nexus using xda app-developers app

Really cool. Im a ubuntu beginner and hope i can pass the installation ^^ thank you for this guide. Have a gsm (maguro) gnex -> calling/sms/3g is working?!

Raphi86 said:
Really cool. Im a ubuntu beginner and hope i can pass the installation ^^ thank you for this guide. Have a gsm (maguro) gnex -> calling/sms/3g is working?!
Click to expand...
Click to collapse
3g isnt working , call and sms is .

Beat me to it lol... Yeah I may have to pick up a GSM Nexus, no one ever supports CDMA :/
Unless some kind sir out there in the community is ambitious enough to port the radios, not sure how involved that is...

Why is there no easier way to install it? Cant they compile a "ready to flash" rom for maguro/toro etc?
(Sorry for my bad english)

Not really, this isn't Android... But it may work if I just upload the two files needed to start WebOS, instead of having everyone compile it for 6 hours or whatever. I'm looking into that.

Sounds good Makes it a lot easier. Thanks

Alright check the OP for the download link, it's about 550 MB or so.

Okay.... after 3 Hours its running.
It feels very good on gnex, but there is a lot of work to do.
On my Maguro wlan works. Bluetooth isnt.
The gesture bar is very very cool and works like a charm.
The os (+Launcher) itself is very smooth. Apps in fullscreen are laggy.
The virtual keyboard and some apps look like cutted up
Cant open phone, but i think its because i have a simlock on my card. cant find a sms button?!
Is the ext2 image build with the lastest source/uploads? the keyboard, especially the scaling, looks better in this version -> http://youtu.be/XelmomAq91o?t=1m19s
Thanks a lot for your guide... it helped me a lot!!! :good:
Two things:
-
Rename "webos-dev-image-tuna-20130226032314.rootfs.ext2" File to "rootfs.ext2"
-
ssh [email protected]
stop LunaSysMgr
touch /var/luna/preferences/ran-first-use
start LunaSysMgr

Glad to hear it, what about the two things, could you elaborate?
The files linked were what I got when I built them a couple days ago, the difference in the video is probably from it being the normal image whereas I built and uploaded the dev image...Damn, there is a difference I guess, well who wants the Dev image over the one that looks and works better (supposedly)?
I deleted my Ubuntu VM for housekeeping, considered moving it, but in any case I won't be able to build for a little bit, anyone care to upload the normal 500 MB image? I can take it and upload to my cloud so you're not losing space.
Sent from my Galaxy Nexus using xda app-developers app
EDIT: Oh I gotcha, fixed. Thanks!

Just thought I'd remind people that this exists... And does anyone out there have any interest in this, either as a user or a developer?

jimmyco2008 said:
Just thought I'd remind people that this exists... And does anyone out there have any interest in this, either as a user or a developer?
Click to expand...
Click to collapse
webOS ? i wont mind .

Mounting w/ Gentoo

So up until now, I've been using a small windows image just to work with adb on my OP5T but am kind of wanting to just move on and get this thing working on my main machine, which is installed with Gentoo.
The problem I'm having is having it even see the OP5T and I can't figure out why. I'm hoping someone here can help out. I've done this with many other phones, but the OP5T Is the only one giving me trouble
Yes I've emerged android tools
As of right now, here is the line I've added to /etc/udev/rules.d/51-android.rules:
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="2a70", ATTR{idProduct}=="9011", MODE="0666", GROUP="plugdev"
Where I got this? `lsusb` shows:
Bus 003 Device 004: ID 2a70:9011
It's the only device that shows up or is removed when I unplug the phone (although it has no label for some reason).
I've even attempted another file I've had to use for other android devices, 80-android.rules and placed the line in there.
I have also removed idProduct from the line just to see if that was conflicting. No luck. Yes, my user is in the plugdev group.
So yeah, I'm out of ideas. Anyone got anything?

Does Z2 have a MLC or TLC flash? Then is it possible to estimate its lifetime?

I'm running LineageOS 17.1 official on my Z2, with Magisk.
The command "cat /sys/block/mmcblk0/device/name" (with root permission) gave the output data "CWBD3R".
Googling "CWBD3R" shows that it's an EMMC, which was also used by some tablets. However I still couldn't figure out the exact chip model.
I then found a teardown and disassembly report of Z2 from a Chinese website: https://news.mydrivers.com/1/485/485103.htm
Then I could read out the exact chip model: "KLMCG8WEBD-B031".
Googling "KLMCG8WEBD-B031" brought me a datasheet, which told me that it has a "Product Name" of "0x435742443352" - bingo, it's exactly the HEX representation of ASCII string "CWBD3R".
However, that datasheet didn't tell me it's a TLC or a (2-bit) MLC.
I found that some merchant claimed that it's a TLC, while "KLMCG8GEND-B031" is (2-bit) MLC - sigh, it's quite a bad news to me.
"tune2fs -l" told me that, I have already written about 20 terabytes of data onto (userdata partition of, let alone the system partition) this poor TLC flash, which roughly means at least ~312.5 P/E cycles! Then what about the write amplification? Oh...
I found the datasheet mentioned "DEVICE_LIFE_TIME_EST_TYP_A(or B)" in its "extended CSD" section. However I don't know how to query this "extended CSD" data.
I think this should be quite an important type of information for an user and owner of Z2 smartphone, however so far I haven't met any guide for this - probably I missed something? Please help if you are knowledgable in this field!

Edit: Oh, an android stackexchange answer already covers what I wrote below:
https://android.stackexchange.com/q...vel-information-of-a-phone-like-ssd-have-with
It's also somewhat funny that there's already a handy "life_time" or "pre_eol_info" virtual file in the "/sys/block/mmcblk0/device/" subdirectory, so that I don't need to struggle to parse the extended CSD data at all!
Okay, I think I've figured out this problem by myself...
Googling brought me this git commit of Pixel Experience:
https://gerrit.pixelexperience.org/...^2..534aa7adab846c9e2f9dc2f1e57bec253d985db3/
...which gave me the handy path to read out extened CSD data: /d/mmc0/mmc0:0001/ext_csd
Googling "PRE_EOL_INFO" brought me a technical note of eMMC device health report from Micron, which told me how to interpret the data.
After that, I think I've figured out the the steps of manually checking eMMC lifetime/wearout status:
1. adb shell on PC, or terminal emulator (like ConnectBot) on phone
2. Run "su" to open a root shell
3. Read out "Device life time estimation type A":
"dd if=/d/mmc0/mmc0:0001/ext_csd bs=2 count=1 skip=268 2> /dev/null; echo"
"01" means "0% to 10% of device lifetime used", and "02" means "10% to 20% of device lifetime used"... and so on.
"0a" means "90% to 100% of device lifetime used", and "0b" means "exceeded the maximum estimated device lifetime".
4. Ditto for reading out "Device life time estimation type B", the only difference is to skip 269 bytes instead of 268 bytes (note that dd is actually reading out a base16 hexdump, so that 2 bytes in the output only represents 1 byte of raw HEX data actually):
"dd if=/d/mmc0/mmc0:0001/ext_csd bs=2 count=1 skip=269 2> /dev/null; echo"
5. Skipping 267 bytes would read out the "Pre EOL information"
"dd if=/d/mmc0/mmc0:0001/ext_csd bs=2 count=1 skip=267 2> /dev/null; echo"
...where a valid value showed here could only be "01", "02" or "03".
"01" means "normal".
"02" means "warning" and "consumed 80% of the reserved block".
"03" means "urgent" and "consumed 90% of the reserved block".

Here comes the question that: have I meaninglessly repeated the job already done by LineageOS? In other words, does LineageOS or AOSP itself already have the ability to detect the health status of flash memory, so that it can then warn the user?

linuxnoobbbb said:
Here comes the question that: have I meaninglessly repeated the job already done by LineageOS? In other words, does LineageOS or AOSP itself already have the ability to detect the health status of flash memory, so that it can then warn the user?
Click to expand...
Click to collapse
LineageOS exposes a lot of great metrics, but I don't think didn't do anything with this eMMC attribute.
I'm pretty sure this flash is a TLC one, because it's so common in relatively cheap devices.
I have a tablet with the following device:
- CWBC3R which is a Samsung KLMCG8WEBC-B031
Which's datasheet has a list about the possible features any this line at page 5:
- Enhanced Mode (SLC + MLC)
So this flash chip probably uses some SLC or MLC cache according to the workload, utilization, etc and this can dramatically decrease the WA, if you write a smaller amount of data to the flash chip each day, utilizing only the SLC/MLC cached part.