yashsingh1/xdaforums huggingface dataset:
[One (M7) Q&A, Help & Troubleshooting] Dr3x1:
[MENTION=4518565]Seanie280672[/MENTION] http://www.htc1guru.com/dld/ruu-zip-m7_ul_jb43_sense50_mr_cingular_us_3-17-502-3-decrypted-zip/
[One (M7) Q&A, Help & Troubleshooting] Seanie280672:
try this one instead, im not so sure the one you flashed contained the firmware, this one will be official stock: http://androidruu.com/getdownload.ph...5_signed_2.exe

I thought you were on HBOOT 1.44? which is why windows 8 couldnt see your phone, what else did you flash to get to 1.55 ?
[One (M7) Q&A, Help & Troubleshooting] Dr3x1:
I was on Hboot 1.44. I could use adb when the phone was on, but I couldn't use fastboot commands when the phone was in the bootloader. As to why I'm on 1.55 now, It must have been included in the zip I flashed. I wasn't on 1.55 before. Now that I am I'm able to use fastboot commands from my windows machine though.

I don't currently have access to a linux machine so will the exe you linked keep me on Hboot 1.55? I don't want to not be able to talk to my phone again on windows if I can avoid it.

Edit: http://www.htc1guru.com/dld/ruu_m7_...13_10-33-1150-01_release_318450_signed_2-exe/

This RUU is the one recommended by the guide I was following (I have the same device as the example device used in the guide). I didn't use it because it's an exe and I was on a linux machine at the time. I could try using that one, but I know it contains HBOOT 1.44.
[One (M7) Q&A, Help & Troubleshooting] Seanie280672:
yup if that RUU works, then yes you will still beable to use windows 8, that file will come with 1.54 or 1.55, failing that you can flash this firmware first using fastboot: https://www.androidfilehost.com/?fid=23329332407574042

dont forget to flash twice

and then this matching RUU: https://www.androidfilehost.com/?fid=95916177934536694

the 4 red triangles basically mean you have a bad firmware, or wrong firmware, or some sort of conflict going on between rom and firmware at the moment, which makes sense to me as im pretty sure 1.26.502 should come with HBOOT 1.44 not 1.55.

[MENTION=2895182]clsA[/MENTION] is the best man for AT&T products, maybe he can confirm the above.

---------- Post added at 11:02 PM ---------- Previous post was at 11:00 PM ----------

see the difference there is that one is signed, making it official.
[One (M7) Q&A, Help & Troubleshooting] Dr3x1:
Right, thanks. I'll do that and get back to you.
[One (M7) Q&A, Help & Troubleshooting] Dr3x1:
Great Success! :D

The phone booted, greeting me with that ugly ATT logo and music I'd hopped to never hear again lol. The sim unlock code took so now I should flash a Tmobile RUU then?

Also I am still on HBoot 1.55 so that's good, I guess.

Edit: It seems I have no cellular network connection with TMobile right now. Yet more things for me to figure out. >_< Maybe if I'm lucky flashing a Tmobile RUU will fix that too. Any recommendations on which one to use?

Edit 2: I just needed to update the APN settings. I knew that of course I'm just tired because I"ve been working on this for too long. I would still like a suggestion on whether or not I should bother flashing another RUU. My end goal is to be rooted using a CM12 nightly like I was doing before. Should I change my CID, flash a stock Tmobile RUU and then Cyanogen mod? I also appear to have lost root, but I expected that.
[One (M7) Q&A, Help & Troubleshooting] Dr3x1:
Update:

http://www.htc1guru.com/dld/ruu_m7_...3_10-38m-1157-04_release_336982_signed_2-exe/

I'm guessing this is the right one. I've updated my CID and MID for Tmobile and re-rooted. Do I really need to flash that RUU now? I can just safely go back to Cyanogen Mod at this point right?
[G2 Q&A, Help & Troubleshooting] alexward:
Hi,

I have a LG G2 D803 and I have flashed the wrong aboot.img, boot.img and lag.imf image through Fastboot. I think it was the images from a verizon variant or whatever, I really don't remember where those images came from.

I feel so stupid, just dragged and dropped in the cmd the files from the wrong folder.

So the phone is basically dead, no screen, no fastboot, no download mode, not recognized on computer (doesn't even make refresh the devices list in Windows in the Device Manager).

Is there anything that can be done?
[G2 Q&A, Help & Troubleshooting] tiguy99:
Read the unbrickabke thread.

Pretty sure your fix is there
[G2 Q&A, Help & Troubleshooting] devvb:
Hi I have the same situation now phone is dead no screen and windows not defecting. If you press all buttons, after some time red light will flash for 8 times and nothing after that.

I think phone is dead but still looking for solution if have .

Any help is helpful thanks
[Galaxy Note 4 Q&A, Help & Troubleshooting] algenash:
Hi does any one have a stock floating features xml? (Sm-n910f) N910FXXU1BOB4

As have edited mine wrong and forgot to back up original
[Galaxy Note 4 Q&A, Help & Troubleshooting] Sidharth21:
Same problem my galaxy note 3 NEO SM-N750 Floating _ feature. Xml modified and forget to backup
[Android Apps and Games] osworup007:
Bringing you people - unique, beautiful and high definition wallpapers from the various most popular image hosting sites across the globe. Wallpapers are intelligently categorized for meeting your needs thereby saving your time. Moreover, recent tab is there to get the latest wallpapers right on your homescreen.

It has covered most of the sections including the latest goolge's material design to classic ones. Some of its categories are:

•	Material Design

•	Blur

•	Inspirational

•	Solid Colors

•	Stock/OEM

•	Minimal

•	Hipster

•	Cities/Architecture

Link>>>https://play.google.com/store/apps/details?id=hd.osworup.wallpapers
[Android Apps and Games] pytachok:
Very good Wallpapers
[Samsung Gear 2] gyuri81:
Hi!

I put the Note 3 on the official android 5.0 . Since then, if we move away from the clock and the bluetooth connection is interrupted , then back in the circle simply do not want to associate itself !

What makes you think this is?

(google translate)
[P3600 General] pMingo:
Hi!

I just received a HTC S300 from Vodaphone Spain, and I suspect this could be a P3600. Someone can confirm this? It looks exactly the same.
[P3600 General] anakinz:
Yep !

Same phone ;)

HTC P3600 = SFR or Vodafone S300, Orange SPV M700 ...
[P3600 General] pMingo:
Thanks! ;)

Someone succeded on running blackberry connect on these phones ?
[One (M8) Q&A, Help & Troubleshooting] CM17X:
Hey there, guys.

I got today an HTC one M8 and i figure that in the box it is labeled as M8X, so i am kinda confused.

I want to root, not S-OFF, but i have not any files downloaded like Fastboot, adb, etc, i use to have them long ago when i had my HTC One X but i lost the files and also the knowledge.

I'll appreciate if you can link me to some post in order to choose a root method, cause all those i see there are for Verizon or international and i'm not sure if they are gonna work for me.

Thanks in advanced.
[One (M8) Q&A, Help & Troubleshooting] CM17X:
Anyone?
[One (M8) Q&A, Help & Troubleshooting] badboy47:
Some pictures of whats software version its running on and maybe a picture of the phone. The more info you provide the faster someone will help you.
[One (M8) Q&A, Help & Troubleshooting] Th3MuffStuff:
Quick google search shows the M8X as a taiwanese imported variant.. should work the same as all the others
[One (M8) Q&A, Help & Troubleshooting] CM17X:
I'm running Lollipop right now, as far i know it can be rooted. Correct me p¿lease if i'm wrong.

That's good to know. I've been searching but all what i can find are some threads with "old" fastboot or adb drivers and i'm not sure if they will work as well at the time. I'll appreciate if you can link me to a thread to root.

Thanks in advance
[One (M8) Q&A, Help & Troubleshooting] CM17X:
Mods can delete - close this thread, i found a memory refresher here. Threads like that should be sticky on every sub forum for each variant.

Thanks for help, guys.
[Android Auto General] mikereidis:
I am closing this thread. Please see new thread for discussion and much new information: http://xdaforums.com/general/paid-software/android-4-1-headunit-android-auto-t3125252

Free APK: http://xdaforums.com/showpost.php?p=60894402&postcount=94 :)

The below was written well before I successfully developed this Headunit app:

EDIT: After much smali and java jar spelunking it appears that:

- An Android Auto standalone/dock like mode that wouldn't need a head unit is not possible in the first released APK. The needed code is either dead (I see dead code in FirstActivity.java), stripped out manually or via Proguard, or such a mode was never there/working in the first place, or recently.

But even if there was such a standalone mode, I think Google would never support it, and it would likely be stripped out or disabled in future releases.

So I have changed the title/purpose of this thread to "HeadUnit app...". I think an app on an external tablet is feasible, assuming any crypto-like HeadUnit validation can be disabled or otherwise compromised. Google, HeadUnit and car OEMs probably won't like it though....;)

Original 1st post follows:

The Android Auto app is released and there is a developer mode:

http://www.androidpolice.com/2015/0...-a-developer-mode-and-heres-how-to-enable-it/

Now, how to use it ?

There are 3 modes: Release, Developer and Demo.

I tried all 3 on a stock MotoG with Lollipop 5.0 and didn't see much happening, even after starting an APK of the new “Universal Music Player” that has Android Auto Support.

Maybe iHeart radio or other Auto compatible app might show something.

What I am wanting to see if the phone/tablet UI overtaken with the AA GUI.

With this, we would be able to run AA on any old 5.0+ tablet or phone; $200 or less for an N7 say, instead of close to a thousand or much more for commercial head units.

I am wondering if Google is trying to prevent this somehow ? Otherwise Google Nexus devices become like cheap head units, minus a few things like audio amps of course. Hardware and Auto OEMs won't like "their business" going to phone and tablet OEM's Google included.

And Google also does not want regulators to be freaked out by driving distraction and of course lawsuits are a risk.

But IMO this is clearly the way to go for hackability, upgradability, and just sheer cheapness for what we hope is a good system.
[Android Auto General] windraver:
Found your thread. Interesting idea. I'll look into this as well.
[Android Auto General] manorton:
Agreed. Let's hope we can crack the nut and figure out how to get a dumb terminal type setup working.
[Android Auto General] brainscollector:
Awesome !

[IMG="http://3.bp.blogspot.com/-Hqyny0xRr-c/U_IWFhcCZvI/AAAAAAAAA2A/KEmOft-A8_4/s1600/image.png"]http://3.bp.blogspot.com/-Hqyny0xRr-c/U_IWFhcCZvI/AAAAAAAAA2A/KEmOft-A8_4/s1600/image.png[/IMG]

Will it be possible to make it run on phone/tablet ? It feels like it's just sending live preview from phone (that's why phone is unusable and blocked) to car screen and reading touch positions and send it back to phone. Well, I hope there is a BIIIG chance to make it work without damn 1000$ car radio.

Also that makes sense as in lollipop screen cast is way more advanced and even made default and accessible from quick toggles, and that's why it's requirement to use lollipop to even use this app.
[Android Auto General] mikereidis:
I am sure it is already possible, we just have to figure out how to use the developer mode.

In November, simulators were released for developers to start testing AA apps, one for messaging and the other for media: media-browser-simulator.apk . If you want to see AA in action (as a demo, more or less), run one of those simulator apps.

I have not got the dev mode working on this "real" AA APK yet, but I've seen much of interest.

It appears there is validation for "Projecters"/Head units, probably crypto too. So I think head unit etc. manufacturers will have to get Google's approval to be supported. The hordes of Chinese OEMs might have issues here, unless they can piggyback, but I think that could be difficult on a platform that will be regularly updated by Google.

There is a whitelist, and even a blacklist for validation.

For dev mode, Google's app has it's own pseudo-Projector, in a class called EmulatedCarActivity . So far I have been able to start this activity, and it briefly flashes an AA screen before killing itself for some reason I haven't figured out yet.
[Android Auto General] brainscollector:
Thank you for awesome reply.

I just had some though, maybe its possible to make some "false connection", what I mean, if we have phone and tablet, we could connect them together with male/male USB cable as its connecting with head unit, and simulate this head unit on tablet just to project screen on it. IMO, I don't know, it sounds legit to me.

Edit. I just tried to sniff around activities and best what I could find is this flashing screen that appears only for second on screen

It seems like halfway to run android auto
[Android Auto General] mikereidis:
Effectively I think you are talking about creating a "head unit app" which would make a 2nd Android device look like a head unit.

Unless Google approves of/allows this (which I doubt, unless for development only) I think this will be difficult to do.

AA validates the head unit. If it doesn't validate, AA won't work. I think the validation is likely cryptographic and will like unlocking bootloaders. IE, security holes may be found, but Google will patch them in updates.

I think Google does not want to see a flood of cheap Chinese head units that have no approval from Google.

Heck, I just re-read the Google info for we developers who want to add AA support to our media and messaging apps. Google MUST approve the app manually for things like distractability before they will appear on Google Play.

They even advise not to add AA to existing apps, because the existing app "will not be available for distribution until the app is approved". Read at the bottom here: http://developer.android.com/distribute/essentials/quality/auto.html

Yeah, that's what I got. Did you check the log ? :

EVENT_READY gets fired at the FSM and that's good.

Then EVENT_CAR_DISCONNECTED gets fired and that closes the Activity.

I have looked at the various related bits of Smali "code" but it's a lot harder to figure out what is going on without original Java source. Even if we had the source, the amount of code is huge.

"TermsOfServicesState" seems to imply that there should be a legal notice dialog. I thought about just setting preferences manually, but I'm just "grasping at straws" at this point.

One thought is that developer mode has been neutered in this released APK. I think someone on that external thread said dev mode was needed for the Pioneer, which is a bit weird.

This AA launch has been kinda funny; Google seems not ready yet and the manufacturers want to get their product out.

And I think Google is going to get a lot of flack for not having a simple tablet mode, all while using the excuse/reason that it's about safety (which is hard to argue with too much IMO.)
[Android Auto General] brainscollector:
Yea, I have seen log to see what's going on.

So first idea goes with ashes.

Funny thing is that sometimes with updates comes new holes and what wasn't possible in previous versions, is possible with newer "bugged" version. Maybe we need to wait for some other releases. Also though about pushing app seems legit. But this "distraction" argument that google would use sounds quite bs as it's way less distracting than using some launcher instead AA so for me this argument would backfire.

And yes, they are very strict with how apps SHOULD look alike for AA and it can't be other than modified template. I dunno how it will look alike with messanging apps as each of them will look the same because "they should not distract" so they have forged some rules that they won't break for anyone. Seems reasonable but not much "android style".

But still I think it must be possible to run it on screen somehow.

Also what I think, screen that pops up will only lead to lock device and work like it would be connected to head unit, so it's quite useless
[Android Auto General] mikereidis:
There are 2 properties that can be used in gms/car/CarClientConfig.smali:

debug.car.enable_validation

debug.car.allow_first_party

I think the first would do what we want IF we had external hardware (or a tablet with a headunit emulator) that was not blessed by Google. May go away in future of course.

And in theory some hacks could be done with Xposed, though Google likely doesn't make that too easy.

Could be. My head has been swimming in the code for several days now and it's just making me dizzy now.

AFAICT, there appears to be no easily accessible standalone mode. I'm sure Google and OEMs have something; code be this app without the developer test code stripped out, could be a separate app that runs on the same device or a 2nd device.

I note there are 4 application types:

Notification and Media are the 2 that Google allows 3rd party developers to build.

Service I think might be the AA "service" itself running on the phone.

EDIT: I likely mis-interpreted this: But the last one, Projection is the most interesting. Google COULD allow 3rd parties to build projection apps, to run on the device itself or a 2nd device.

Hypothetically such apps might go through a validation/testing process at Google (likely for a bunch of "fees") and end up blessed.

But I've developed plenty myself with an eye to theoretical future generation capabilities to know that code does not equal supportable capabilities. Google especially seems to do this, which I'd except from such a forward looking company looking to run the most profitable sectors of the world economy...

Auto is just a next step. Maybe next decade Google self driving cars will bring us places while we play Android games and listen/watch Google music/movies...

And the car will say "McD's has a special today; should I pull in for you and pay with Google wallet ? And, your gas is getting low and you need an oil change, let me find a place for you since I see you are between chores in your schedule....
[Android Auto General] Entropy512:
Rather than using smali/baksmali - perhaps try AndroGuard's decompile or jd-gui?
[Android Auto General] mikereidis:
I've never tried AndroGuard's decompile so I guess I should try it.

I've run the latest dex2jar then ran the jars through jdgui.

There are 3 dex files. Google is using Multidex to avoid their 65K method limit.

What's annoying is that there is some code I can only see with apktool, and some code I can only see with dex2jar/jdgui.

And apktool seems to be better at decoding class names than dex2jar/jdgui. (?)

dex2jar/jdgui shows proguarded classes, but apktool seems to not.

I haven't done anything with these reversing tools since I stopped trying to support OEM FM APIs 1-2 years ago, but it seems there is no best free tool, and I'm not sure about the few commercial ones for Android.

Next post, the protocol:
[Android Auto General] mikereidis:
Running dex2jar and jdgui I am now seeing over 50 proguarded classes under com.google.android.gms.car.senderprotocol .

Finally, the low level protocol I want to see, given that I am exploring feasibility of a "headunit emulator" app that could run on a tablet.

I note that USB may be the only connection supported now, but there are indications that WiFi direct may be supported, as well as some emulator mode/thing.

Looking around Googles dev pages, rewatching Googles AA tech videos and the recent podcast, I now see that many of the "parts" that are new to me are actually openly documented, at least in part:

- Protocol buffers for the protocol.

- Open accessory protocol looks similar to the AA protocol and the way it works on USB. I'd guess the head unit is the host and the connected phone is the uhh... non-host.

- There is a Google Client API for AA and Google documents other, similar-ish client APIs for apps to use.

There is an SslWrapper class and associated JNI library that's used to encrypt communications. Perhaps this is more needed for WiFi connection than USB, but I'd guess it'd make USB sniffing more difficult.

So now I'm thinking my Linux PC could be used to emulate a head unit, implementing the protocol bit by bit until it works.
[Android Auto General] Entropy512:
That's the impression I got from various looking around - It appears that the AA protocol is an extension of the ADK protocol, and you're right, the headunit acts as the host.
[Android Auto General] mikereidis:
I updated the first post with:

After much smali and java jar spelunking I think it's likely that:

- Any standalone/dock like mode that wouldn't need a head unit is not possible in the first released APK. The needed code is either dead (I see dead code in FirstActivity.java), stripped out manually or via Proguard, or such a mode was never there/working in the first place, or recently.

But even if there was such a standalone mode, I think Google would never support it, and it would likely be stripped out or disabled in future releases.

So I have changed the title/purpose of this thread to "HeadUnit app...". I think an app on an external tablet is feasible and supportable going forwards, assuming any crypto-like HeadUnit validation can be disabled or otherwise compromised. Google, HeadUnit and car OEMs probably won't like it though....;)
[Android Auto General] mikereidis:
The Android Open Accessory Protocol (OAP) is confirmed to be used for communications between the phone running the Android Auto (AA) companion app and the HeadUnit.

I have a C program that successfully connects with the AA app, as seen in the logcat, but it does not yet push any data, which would start with an SSL based handshake request.

Next step would be deciphering the Proguarded sendprotocol classes and seeing if handshake is possible without any secret keys.

Then on to the other bits of the protocol. I'd guesstimate that a first prototype of major functionality might be possible in a month or so.

Interesting that Google provides source for a remote video and HID sink and source app over USB OAP. And that uses the same H.264 as AA.

Apparently there is prioritization for different streams or channels. The main ones seem to be:

- Video, from AA phone to HU.

- Response of touchscreen inputs, button presses, dial turns or steering wheel controls etc, from HU to AA.

- Audio, from AA to HU, though there is also microphone input, from car/HU to AA.

- Sensor inputs, from car to AA. Here is where Google eventually hopes to learn everything from how often we change the oil, to current wheel speed and fuel level. Google loves data, and will be happy to take a commission when fuel is low and we are next to a participating gas station...

There is more, but these are the basics.

Ironic string: "Android Open Automotive Protocol". If it's "Open", where are the documents Google ? Or did you just replace "Accessory" with "Automotive" and forgot about the "Open" part ?

Google has been suspiciously quiet every Google+ and other post made asking about a standalone mode. And they have been slammed in the comments for their AA app, with a few defenders saying something like "It says Auto, you need a compatible car".
[Android Auto General] Schischu:
Which accessory pid did you use to instantiate the oap session?

I tried 0x2D00 - 0x2D07 without any luck...
[Android Auto General] mikereidis:
The standard 0x2D01. I think that any standard documented value from 0-5 would work.

What's important is the special manuf and device/product strings for AA.

Only way I figured those out was by modifying some framework files and building a custom ROM.

Are you also interested in building some sort of headunit app ?
[Android Auto General] deeper-blue:
Just a small pointer for you guys since I don't have the time to fiddle with it at the moment:

download the NEX4100 head unit update and unpack it

dd if=PJ150PLT.PRG of=PJ150PLT.img bs=512 skip=1

mount -o loop PJ150PLT.img test/

dissect the the android system that is running on the head unit, take a close look at AAPPlayer and all the libaap*.so files

profit