yashsingh1/xdaforums huggingface dataset:
[Google Pixel 2 XL Questions & Answers] Desert.pro.riders:
I believe I only used the unlock critical, but I unlocked the bootloader before I did the December update. Not sure that has anything to do with it?

Oem unlocking is enabled, but it is greyed out in the on position. I'll attach picture. And USB debugging is enabled as well

I updated to the latest platform tools yesterday, I tried on my two macs & swapped ports and tried my two different cables that I had on hand, maybe today I'll see if I can get anything with my buddy's pc. Windows 7 I believe.

And okay I'll look getting the recovery going again

Thanks a lot

View attachment 4492382
[Google Pixel 2 XL Questions & Answers] Badger50:
Well at least you can still get into your OS apparently, which is good. I'm not a Mac guy, so I can't help much in that regard, just seems a bit more quirky when using fastboot. Be interested to know how it goes on the Windows 7 machine. That's what I use without issues at all :good:
[Google Pixel 2 XL Questions & Answers] Desert.pro.riders:
Yes! At least the phone os on the phone works fine

Yeah you're right about the macs. They are pretty cool because it works with removable devices without having to mess with drivers. But it sucks when something goes bad because there are really any device managers or drivers to mess with.

Blessing/curse.

I'm usually a pc dude too, but my ex took my PC ?

Well once I get home from school I'll get to trying to fix this once again
[Google Pixel 2 XL Questions & Answers] Desert.pro.riders:
So the windows PC does detect that something gets plugged in But this the only thing that happens

This sucks :(

Edit:

I was able to get into stock recovery now. But I don't think you can do much from there.

Adb & fastboot continue to be unresponsive :(
[Google Pixel 2 XL Questions & Answers] Ericarthurc:
Well couple things about Mac, you don't need any usb drivers for it. To view the file contents of the /sdcard you need Android File Transfer --> https://www.android.com/filetransfer/ plug in your phone then make sure you change it to MTP on the phone. As for adb and fastboot in terminal, download the latest platform tools for mac --> https://developer.android.com/studio/releases/platform-tools You will get a folder called "platform-tools" put that folder some where you like on your mac. I put mine at /Users/"my username"/platform-tools So to get it working correctly you need to open terminal and run "cd ~/" [no quotes on these commands btw] then run "sudo nano ~/.bash_profile" when nano opens it should be blank, type on the first line export PATH="$PATH:your/path/to/platform-tools" [with the quotes on that one]. In my case mine is export PATH="$PATH:~/platform-tools" or export PATH="$PATH:Users/ericarthurc/platform-tools"

Just make sure you get the right file path and that its writing correctly; then type ctrl + x and then y for yes to save. Then in terminal type source ~/.bash_profile

Quite terminal and relaunch, run the command "adb version" you should now see the correct file path and no errors; run adb device now and it will start the adb server
[Google Pixel 2 XL Questions & Answers] Gregzi:
I never had problems connecting my Pixel to mac, even to other hackintosh...

I have Android File transfer installed and no SDK platform tools.

Usually I just download the package from Google and place it somewhere. Than opening Terminal, going into that folder, which btw contains adb and fastboot...

For example: when typing the " ./ adb devices" for the first time, the message about not running / starting Daemon service pops up. This is normal.

I presume that you are using the "./" before every command in Terminal.... This is obligatory on Mac.
[Google Pixel 2 XL Questions & Answers] Desert.pro.riders:
Yes so I've gotten adb, fastboot, and the Android file transfer working before on both of my Macs, so I know they are set up right. The problem was when I updated my pixel to the December version via adb. Adb stopped completely working.

I can have my phone booted up and in usb debugging mode and run the "./adb devices" and it'll show the list of devices empty.

Same thing if I put the phone in fastboot and try running "./fastboot devices" it hangs for about a second then it shows up with an empty device list.

I was able to wipe the phone clean with the stock recovery & got my stock kernel back I think.( I'll attach a picture) but I'm still not able to ota to the April patch, I'm thinking because I used twrp right?

Either way I still cant get fastboot & adb working, I've tried my two Macs one in high Sierra & the other on El capitan. And a Windows 10 pc and a combination of about 6 different us cables.

Has anyone ever seen this happen? I think I might have hit a wall here ☹️
[Google Pixel 2 XL Questions & Answers] Desert.pro.riders:
The way I do it is

1. Open terminal

2.write "cd "

3. Drag the platform tools folder from the desktop to the terminal window

4. Check adb devices , "./adb devices"

I will try to reinstall adb again your way, as I am out of options so anything helps, thanks
[Google Pixel 2 XL Questions & Answers] Badger50:
Just outa curiosity, since it appears your stock everything again, do you get any response from Google when you go into....settings/system/system update??
[Google Pixel 2 XL Questions & Answers] Desert.pro.riders:
This, stops before it goes into step 2
[Google Pixel 2 XL Questions & Answers] uicnren:
disconnect your phone from the mac.

reboot the mac

open developer options on the pixel

disable USB debugging

tap on 'revoke USB debugging authorizations'

enable USB debugging

reboot your phone

plug your phone into the mac again

If all goes well, you will need to authorize it on the phone, and adb/fastboot should work correctly

if you wish to easily install adb/fastboot into your PATH, see here.

That will properly install it, as well as the latest version(s) of each.
[Google Pixel 2 XL Questions & Answers] Desert.pro.riders:
Still nothing :( I tried this a few times & did the path install too

IDK what else there is trouble try I'm pretty much open to anything
[Google Pixel 2 XL Questions & Answers] Desert.pro.riders:
Do you guys think I can do anything thru stock recovery?

I tried adb sideload with no success and I tried the apply update thru sd card and I gave me a error unable to mount message?
[Google Pixel 2 XL Questions & Answers] Badger50:
You can adb side load from stock recovery as well.
[Google Pixel 2 XL Questions & Answers] Desert.pro.riders:
If I'm on adb sideload mode & I type adb devices into the terminal, should the serial number show up in the terminal? Because it's not. I'll try messing with it a lil more once I get home from work
[Google Pixel 2 XL Questions & Answers] mattyb65:
Try using a different wire. For some reason, I've had trouble with certain usb-c wires when connecting my pixel 2 xl to macs. Are you using the one that came with the phone?
[Google Pixel 2 XL Questions & Answers] uicnren:
yes, you should see the serial of the device.

when you clear permissions, do you get a prompt on the device to allow the connection when you plug it in ?
[Google Pixel 2 XL Questions & Answers] Desert.pro.riders:
I think I lost the OEM cable, but I've tried about 4 different usbc to USB-a cables and also a micro usb with an adapter. Which is the same one I would use when my adb was working.
[Google Pixel 2 XL Questions & Answers] Desert.pro.riders:
Even after clearing permissions I get nothing on the phone or the Mac. Other than the charging lightning bolt on the phones notification bar, super odd...
[Google Pixel 2 XL Questions & Answers] Desert.pro.riders:
What is a pixel 2 xl google edition without the ability to adb :(
[Fire Q&A, Help & Troubleshooting] JKSurf:
I have 3 5th gen rooted Amazon fires running different builds of CyanogenMod and Lineage. On all tablets flashfire force closes after "checking for Pro" during start of the app. Anyone else have this issue? Maybe a different version of Flashfire that works?
[Fire Q&A, Help & Troubleshooting] DB126:
Well known issue discussed in multiple threads. FlashFire developer has retired (at minimum taking a sabbatical with no publicly communicated end date) leaving in place "time bombs" that disable the free version of his tools.

Three workarounds:

- roll date back to March 31st, 2018 for v0.73 (not always easy to do on FireOS)

- purchase 'pro' version of FlashFire on another device which will then allow access to 'pro' version everywhere (no time bomb)

- purchase ODIN from same developer which alsos unlock FlashFire

First option is probably your best best if running CM 12.1 as the date can easily be rolled back from the UI. Be sure to use FlashFire v0.73; if opting for an earlier build you'll need to set the date back further which can trigger other unpleasant device behavior.
[Fire Q&A, Help & Troubleshooting] s00thsayer:
Add this line to file /data/data/eu.chainfire.flash/shared_prefs/eu.chainfire.flash_preferences.xml

<boolean name="have_pro_cached" value="true" />
[Fire Q&A, Help & Troubleshooting] DB126:
Interesting hack. Looking for collaboration as I purchased pro long ago. Pretty simplistic validation method if it holds up.
[Fire Q&A, Help & Troubleshooting] Rortiz2:
For flashfire to work, first install it from the play store, then in a command window you type this:

adb.exe shell su 0 date -s 20130503.100022

And then I'll let you use it.
[Fire Q&A, Help & Troubleshooting] DB126:
Has this been validated with FireOS v5 (specifically 5.11-5.3.1 inclusive)? There are several reports that suggest it is ineffective. ATM I do not have a gizmo loaded up with (rooted) FireOS to test with.
[Fire Q&A, Help & Troubleshooting] s00thsayer:
I have tested this on a couple devices and modifying eu.chainfire.flash_preferences.xml works fine and gets around the date change thing. Of course root is required to mod this file. Just thought I would share an alternative to changing the date.
[Fire Q&A, Help & Troubleshooting] Hymix:
Also worked for me. Just had to add the line below the "boolean name" line that's already in the file. Tried adding to the bottom at first and it wouldn't work for me.
[Fire Q&A, Help & Troubleshooting] dave678:
Unknown error when trying to flash
[HTC One A9] mabf000:
Hello all, i'm trying to update my OS but im S-on

my bootloader is unlocked, my rom is rooted and have the twrp

this are my htc one a9 specs
[HTC One A9] eavandijk83:
There is a lot to find about updating your OS here on XDA. The latest ROM can be found on lineageos.org.

Basically:

1st time

1. Unlock bootloader

2. Install latest TWRP

3. Wipe Data, System, Cache, Dalvik Cache partitions from withing TWRP

4. Flash latest ROM from within TWRP

5. Flash latest GApps package from within TWRP

6. Flash latest SuperSU or Magisk (I prefer SuperSU) from within TWRP

Before I forget... make sure you've got the proper Nougat RUU installed! More info can be found here.
[HTC One A9] Wonders_Never_Cease:
Since you are currently using a branded ATT device,and are S-On... No you cannot upgrade beyond current version. If you were to S-Off and convert device to Dev/Unlocked version,you could then upgrade to latest build available.
[Xiaomi Mi A1 Questions & Answers] rajatchawla66:
previously i was on stock rom and Video calling was working just fine but when i enabled camera api2 then the other person wasn't getting my video but i could see his fine.

Yesterday i flashed RR 6.0 in hope for that my video call will work fine from now but in any of custom roms video call is just not connecting.

Anyone else facing the same or is it just me who messed up with something that i am not aware of?

P.S- I am taking about Videocall by dialer not over any third party apps(on which video calls are working fine)
[Xiaomi Mi A1 Questions & Answers] mity_dev:
I am facing the exact same problem I guess before i enabled the camera2api without root method by using the tool the video calling was working fine but after enabling camera2api it shows a black screen to the person i called but i can see their video. I also thought it might be a stock rom bug then i switched to RR still the problem is there.

Mine video calls are getting connected but not showing video.

I think the problem is with camera2api if we disable it we can make video calls without any problem.

If you can try disabling it and give me the results it would be great or if i could do it i will inform the results.
[Xiaomi Mi A1 Questions & Answers] mr_prakhar007:
issue in native video call please help

same problem is with me too
[Xiaomi Mi A1 Questions & Answers] 25vikasp:
Any solution please let me know
[Xiaomi Mi Mix 2S Guides, News, & Discussion] elanstiles:
Finally was able to get full LTE working on my Mi Mix 2s.

The problem is when that updated the IMEI on my account, the AT&T system didn't recognize the manufacturer and device so it only provisioned HSPA assuming it was a flip phone.

When they reverted to my Pixel IMEI but with the sim in my Mi Mix 2s full LTE came up after reboot.

A request was added to include the XIaomi on their list of acceptable devices, but was told that it could take 10 days or more.

So if you are switching from another nexgenphone don't update the IMEI until you can confirm that they recognize the device as an LTE capable device. Curious if I had the IMEI of a VoLTE device if that would also get provisioned.

Cheers,
[Xiaomi Mi Mix 2S Guides, News, & Discussion] tarek619:
Hey, are you on the Chinese miui or another rom? Does it show 4G for you or it actually says LTE? Can't get it beyond 4g
[Xiaomi Mi Mix 2S Guides, News, & Discussion] Flatric:
Isn't 4g=LTE?:D
[Xiaomi Mi Mix 2S Guides, News, & Discussion] tarek619:
Great! That means i got super lucky with my purchase. Thanks!
[Xiaomi Mi Mix 2S Guides, News, & Discussion] elanstiles:
Yes, Chinese rom. Says AT&T LTE. at the top.
[Xiaomi Mi Mix 2S Guides, News, & Discussion] Flatric:
For you it shows Lte on the top? For me it shows 4g if I'm on Lte and 4g HD if I'm on Lte and VoLTE is enabled. On previous phones I had the option to decide if I want 4g or Lte shown on the top if I'm on Lte
[Xiaomi Mi Mix 2S Guides, News, & Discussion] elanstiles:
Which phone does AT&T think you have? VoLTE is not provisioned for me so I don't see 4g HD. or VoLTE. From what I have experienced, the level of service provisioned is based on At&t recognizing the device from the IMEI.

Prior to my Mix 2s I had a Pixel, when I originally provided my 2S IMEI number to At&t the service fell from LTE to HSPA. took a few days with them on the phone and emails to rollback to the IMEI on the Pixel for LTE to be restored.

Don't know if they can custom provision service or if the options are driven by the IMEI selection off of some pre-defined menu.
[Wing, P4350 ROM development] zcink:
Update: There is a newer radio even. Its version 03.18.90:

http://xdaforums.com/showthread.php?t=387696

If you like your current rom and just want to flash the new Radio -- here it is. Version 03.12.90
[Wing, P4350 ROM development] blaiseid:
can i load it into my HERA100?

can it change my language? from germany to english?
[Wing, P4350 ROM development] speoples20:
What exactly would this do for me? Would it improve reception or data speed?
[Wing, P4350 ROM development] Inclement_Death:
I saw no change after upgrading from 3.08
[Wing, P4350 ROM development] nikmel420:
could you give me step by step instructions i have a stock wing i dont think i know enuf yet to flash a new rom ive read a hundred posts but they are not all the same or it seems they send you to other posts in the midle so im gona keep studying. the main reason i want a new rom is the radio. i have bad reception were i live so id like to try this. so a step by step would be gratiously apreciated. thank you im using vista if that maters
[Wing, P4350 ROM development] f_v_man:
Step-by-Step instructoin please

I know. I have been reading a lot. In-Fact for the whole day!!! But I just want to be sure by step-by-step instructions. Thanks in advanced.
[Wing, P4350 ROM development] zcink:
You can Flash it the same as would any other rom using herald-uspl.exe. Just put this Radio.nbh file in the RUU folder. It will only Flash the new Radio and will not affect anything else. (Just make sure this is the only .nbh file in there.)

It should also work with Hard SPL.
[Wing, P4350 ROM development] nikmel420:
ok ill go back and read the hunreds of posts how to flash. not one of witch is a stand alone guide. every one sends you to another post eather how to do part one, or two, or three, ect. or to download what you need for part one, or two, or three, ect. what i need is "An Idiots Guide to Flashing" :confused:
[Wing, P4350 ROM development] zcink:
I simply typed in Search box -- How to Flash a rom.

Came up with this link:

http://xdaforums.com/showthread.php?t=358615

All the information you need is on one page.
[Wing, P4350 ROM development] nikmel420:
thank you i followed it and finaly got the nerve (beer balls)to do my first flash. could'nt of been smoother
[Wing, P4350 ROM development] zcink:
Great. see I knew you could do it. I was nervous my first time too. Its easier than you think. I paid $400.00 for my Wing when they first came out so I was nervous about bricking it. So I read how to do it for a long time before I tried it.

Once you start flashing, it get addictive.
[Wing, P4350 ROM development] zcink:
Yes probably not much difference from 3.08 but huge difference from Stock T-Mobile radio.
[Wing, P4350 ROM development] davidsalinas:
i loaded the stock rom on my wing becuase i was sending it back and had better signal in my school befor my stock rom i had Touch-IT - Touched by Vista wm6.1 v6.1.52 BETA and now i have the newest radio version and still dose not work as well any ideas why?
[Wing, P4350 ROM development] zcink:
Try this one:

http://xdaforums.com/showthread.php?t=387696
[Wing, P4350 ROM development] davidsalinas:
thanks i just flashed it on hope it works better
[Wing, P4350 ROM development] nashwing:
filename?

The file in the zip say 3.12.90 version???

NEVERMIND:

I see the correct one in the link... mis-read the post...
[Wing, P4350 ROM development] Personne2:
Not very satisfied...

I loses the signal very often there where the 03.12.90 was profoundly

Then I'll downgrade to the 03.12.90

Other report for this new radio ?
[Asus Transformer TF700] technodino:
My tablet is gently used. I bought a "new" dock for my TF700T (Android 4.1). The dock charges but will not type.; no response on tablet when I tap on a key. Touch pad does not work.

The tablet does not recognize that the dock is attached. No dock software version is shown in properties.

1. Tablet Build Number: JOP40D.US_epad-10.6.1.14.10-20130801

2. Kernel version: 3.1.10-gb1a9af5 + the following text: android@cancer #1; Thu Aug 1 17:00:24ST 2013 (last part is date and time, obviously and an email address??)

3. I can get the dock about 95% open but it is really tough to open when I get close to the touch pad (I have removed all 6 screws). I was hoping to check for a loose cable but stymied. Not willing to pry too hard for fear of cracking the plastic.

Any help greatly appreciated.

Thanks

John
[Asus Transformer TF700] Nektopoli:
Check the serial number on Asus website, if you register the keyboard/dock it will return the model "ASUS VivoTab RT Mobile Dock". Mine is a dock for the TF201 but it works fine on the TF700. Give that a try to make sure you have the correct keyboard dock. You can also check the sticker on the back, it has the model on it is very small type, did you get the box? - NP
[Asus Transformer TF700] technodino:
Sorry for the delay in responding. I was upgrading my ROM to Android 7 and had a few challenges. I registered the dock and it came up as "Asus TF300T" assuming this is a TF300T dock. This dock should be good?

After the ROM upgrade the tablet recognizes the dock is attached; 2 battery icons shown when charging. Still not responsive to key presses. No box. I bought dock on eBay. When the dock arrived it was in the plastic "bag" that would be found on a new unit. The dock charges fine. Any other thoughts on a next step?

Thanks

John
[Asus Transformer TF700] Nektopoli:
I'm using a TF201t dock with my TF700, but I don't think the TF300 dock is compatible with the TF700. - NP
[Asus Transformer TF700] technodino:
Digging around online & learned the TF300 dock will work with the TF700 if the dock firmware is 027 or greater.

Does anybody have any idea how to check the dock firmware version? How to upgrade?

Thanks

John
[Asus Transformer TF700] Nektopoli:
I'm on 7.1.2 and in the About section of settings there's not mobile dock version info giving and I don't know if you can "flash" the keyboard dock. - NP
[Asus Transformer TF700] technodino:
I tried one last time to connect to the dock, the space time contimum must have been perfectly aligned because it now works as expected.

John
[Xiaomi Mi A1 ROMs, Kernels, Recoveries, & Other De] Adesh15:
[IMG="AOSIP"]https://img.xda-cdn.com/ZAQhLl2X0i-A19WIqR8BYhNSFsc=/http%3A%2F%2Fi.imgur.com%2FDr6rSI1.png[/IMG]​

[B][CENTER]**** Disclaimer: I'm not responsible if you destroy your device. Use at your own risk!!! ****[/CENTER][/B]

Android Open Source illusion Project​

About us:​

AOSIP is a quality custom rom based purely on GOOGLE AOSP source since 6.0 release. Twisted with the latest features and blended with stability. We strive for perfection and it shows.​

Team Illusion:​

Josh Fox (xlxfoxxlx)

Akhil Narang

Shreesha Murthy

Brett Montague

Sri Harsha​

Source code:

AOSiP Gerrit Review

AOSiP Github

Kernel source

Latest Downloads:

DOWNLOADS <-- click here

Open GApps<-- click here

Credit/Thanks:

Mike Williams(founder and creator of AOSiP)

Google

Dirty Unicorns

AICP

ABC Rom

Screwd

Omni

Krexus

Cyanogenmod

SlimRoms

ChainFire (SuperSU)

Beanstown106

Cory Collins

Sultanxda

flar2

francisofranco

---------

Any others i may have forgotten(sorry, pls pm me)

All our testers

XDA:DevDB Information

AOSiP, ROM for the Xiaomi Mi A1

Contributors

Adesh15

Source Code: https://github.com/aosip

ROM OS Version: 8.x Oreo

ROM Kernel: Linux 3.x

Based On: AOSP

Version Information

Status: Stable

Stable Release Date: 2018-05-03

Created 2018-05-03

Last Updated 2018-05-03
[Xiaomi Mi A1 ROMs, Kernels, Recoveries, & Other De] Adesh15:
First Build Is Up!

Download link in OP

Changelog:

ROM Specific

Device Specific:

Compiled Kernel with Clang 7.0.1

Kernel Upstreamed to 3.18.108

Merged latest CAF tag in kernel

Kernel has minimal features like KCAL, Sound Control, Boeffla Wakelock Blocker

Defualt TCP Congestion Algorithm is Westwood

Default I/O scheduler is Maple

WireGuard support
[Xiaomi Mi A1 ROMs, Kernels, Recoveries, & Other De] JagravNaik:
ayy!
[Xiaomi Mi A1 ROMs, Kernels, Recoveries, & Other De] sauru.660:
Some SS Pls....??

Would love to flash..
[Xiaomi Mi A1 ROMs, Kernels, Recoveries, & Other De] Bot96:
Hell yeah!
[Xiaomi Mi A1 ROMs, Kernels, Recoveries, & Other De] Micka84:
More information please. Screenshots? Selinux permissive or enforcing? Features?
[Xiaomi Mi A1 ROMs, Kernels, Recoveries, & Other De] TedGok:
Nice to see this rom in mi a1. :svetius::)
[Xiaomi Mi A1 ROMs, Kernels, Recoveries, & Other De] Buckethand:
I used this rom on my n5x before it bootlooped nice to see it again on this device :laugh:
[Xiaomi Mi A1 ROMs, Kernels, Recoveries, & Other De] JOSE_1889:
Bugs? Screenshots. I want to try it but i need to know that things
[Xiaomi Mi A1 ROMs, Kernels, Recoveries, & Other De] AkashAlien:
no bugs as of. now, go ahead flash it
[Xiaomi Mi A1 ROMs, Kernels, Recoveries, & Other De] JOSE_1889:
Okey, i wll try it. Thanks
[Xiaomi Mi A1 ROMs, Kernels, Recoveries, & Other De] sauru.660:
Some screenshots pls
[Xiaomi Mi A1 ROMs, Kernels, Recoveries, & Other De] AkashAlien:
nope doesnt work for me though
[Xiaomi Mi A1 ROMs, Kernels, Recoveries, & Other De] praviappu:
Thanks for the update:good:
[Xiaomi Mi A1 ROMs, Kernels, Recoveries, & Other De] Buckethand:
For those wandering selinux is permissive other than that nothing to report so far :good:

Edit: just one small request under display is it possible to add screen size as "alternative" to dpi change?