yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] jmotler:
Hi,

Seemingly some Samsung S6s (mine is T-Mobile) do not permit OTG, I have tested the OTG cable and mouse with another Android device.

I have also tried using adb to pull data from my phone, but the only option there seems to be adb sideload as per this thread

Looking for ways to get into my phone to enable USB debugging, or just to use a mouse or keyboard so I can check my texts and backup my photos etc before trying to fix the screen

Any ideas on other method of getting into my phone?
[Android Q&A, Help & Troubleshooting] Atifbaig786:
Three Ways for you

1-Get another model of the same Mobile.Flash the Cwm Recovery on it.Backup the Firmware and Restore on Broken Device.Now Make a Simple Script to move all you files and Voila.

2-Get the screen Fixed.I am pretty Sure they Won't smash your data

3-**** it.Buy another phone.
[Honor View 10 ROMs, Kernels, Recoveries, & Other D] flex1911:
#include <std_disclaimer.h>

/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/

About:

These are my personal builds of AOSP for View 10 based on berkeley-dev trees. It's a plain Android with only a few minor changes added by me to make it more usable: better OTA packages support, some application fixes, under-the-hood improvements and kirin-specific patches. No additional system functional included.

What's working/broken:

Same as LineageOS 15.1

Installation:

Flash the latest ROM zip via recovery

Flash any other additional zip that you need

Reboot

Downloads:

ROM builds: Google Drive

Gapps: OpenGapps

Source code:

Common device tree: https://github.com/Flex1911/android_device_huawei_kirin970-common

Device tree: https://github.com/Flex1911/android_device_huawei_berkeley

Patches: https://github.com/Flex1911/android_patcher

Credits:

[MENTION=5075128]LuK1337[/MENTION], [MENTION=5778309]luca020400[/MENTION] - for amazing work on device trees
[MENTION=2233641]AdrianDC[/MENTION] - for porting some essential things like backuptool to AOSP

XDA:DevDB Information

AOSP Oreo for View 10, ROM for the Honor View 10

Contributors

flex1911

ROM OS Version: 8.x Oreo

ROM Kernel: Linux 4.x

Based On: AOSP

Version Information

Status: Testing

Created 2018-06-13

Last Updated 2018-06-13
[Honor View 10 ROMs, Kernels, Recoveries, & Other D] flex1911:
Reserved

Changelog:

[B]20180613:[/B]
Initial build based on android-8.1.0_r30 tag

Additional notes:

AOSP itself is bare bones and unlike LineageOS it is not very usable without gapps. Stock gapps package is preferred for the best experience, but you can use small packages too.

Compared to EMUI system may look very gigantic with stock DPI value, 420 dpi is recommended (it is used by Google on their 1080p devices). Go to dev settings and set smallest width to 411dp instead of 360dp.
[Honor View 10 ROMs, Kernels, Recoveries, & Other D] Aryapars:
This looks very promising. Thank you very much!

Will it also work with L09? Will there be OTA (security) updates?
[Honor View 10 ROMs, Kernels, Recoveries, & Other D] flex1911:
While I didn't test it on L09, it uses same compatibility hacks as Lineage, so it should work fine here as well.

I'll keep it up-to-date with the latest AOSP tag always, so system-side security updates are guaranteed. Though device will still report vendor security patch level.
[Honor View 10 ROMs, Kernels, Recoveries, & Other D] awells845:
Hi there, I was able to install this successfully on an Honor 10 device. Please can I create a thread for the Honor 10 forums with your aosp Oreo rom thread? I will add credits and mention that your the maintainer of the rom.
[Honor View 10 ROMs, Kernels, Recoveries, & Other D] flex1911:
Yeah, sure.
[Honor View 10 ROMs, Kernels, Recoveries, & Other D] MuyKurioso:
Will this work for any Kirin device treble-enabled? I own a Mate 10 Pro. Thanks.
[Honor View 10 ROMs, Kernels, Recoveries, & Other D] flex1911:
While it's intended for use only on V10, it should work for everything else as well. Although it may be necessary to remove the assertion from update-script.
[Honor View 10 ROMs, Kernels, Recoveries, & Other D] sky104hk:
Hey flex, is the "Pie version" has same "hotspot" bug as compare to other 9.0 lineage ROM?
[Honor View 10 ROMs, Kernels, Recoveries, & Other D] flex1911:
Wrong thread?

But yeah, every treble Pie ROM has broken hotspot and it's not like there is any idea to fix it (for now).
[Honor View 10 ROMs, Kernels, Recoveries, & Other D] mondalakash:
Sadly your aosp build doesn't boot on l09....would have been good if your build booted before pie roms became stable enough to daily drive:)
[Honor View 10 ROMs, Kernels, Recoveries, & Other D] sky104hk:
Tks for answering, not wrong thread, I just simple confirm something before flashing:)
[Honor View 10 ROMs, Kernels, Recoveries, & Other D] flex1911:
Thread closed as this ROM is not supported anymore.
[Google Pixel 2 Questions & Answers] mikeprius:
I just pulled out my phone and had this happen again for the 4th time. Sometimes when I pull out my phone it had the brightness maxed out, sometimes flashlight on, and battery saver mode. It's not always those changes, but sometimes I have a freakout of the phone and when I take a look at it I see all these random changes. Does this happen to anyone else ?

The only thing I can think of is that the gesture is waking the phone and since the pull down menu is not locked on the lockscreen things are auto getting pressed.
[Google Pixel 2 Questions & Answers] TCUofficial:
If you have swipe fingerprint for notifications on, it could be you're swiping down on the sensor which would turn the phone on and swipe notifications down, making it easy to accidentally toggle something on as you pull it out.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] steamport:
I am not responsible for anything that happens as a result of you using the ROM. Sure, i'm willing to help with bugs, but if you get fired because the Alarm app crashed, gremlins crawl out of your arse, thermonuclear war starts, or if your progress in Clash of Clans gets reset, i'm not the one to blame.

Features

microG and F-Droid pre-installed
Anything else LineageOS can do
Is not certified cancer-free in California

Stuff you need to actually use this

- Unlocked Bootloader (duh). Seriously, I will ignore you if you mention that you tried to boot this with Safestrap.

- Update TWRP to Android-7.1 builds located here. Please make sure to use the recovery image which is appropriate for your device (Thor or Apollo)

How do I actually install this?

- Backup existing ROM if you want. Or don't. I don't really care, truth be told.

- Wipe /data partition. You can keep media storage if you want, but I prefer to format it to make it SQUEAKY CLEAN

- Flash the .zip

- Do not flash OpenGapps. Or any Gapps. That defeats the purpose of microG.

- Flash any other crap you want. This'll probably Magisk.

- Reboot.

Downloads

AndroidFileHost: Thor, Apollo

Extra junk you might want

Magisk

Yalp Store (play store wrapper)

Flashable Standalone Google Play Store

Sources

I didn't make any of this. I just compiled and signed it. People smarter than me, like hashcode and ggow did, made this work on the HDX. Lots of other people made LineageOS and microG. Thanks to you all.

Phoenix Kernel

HDX-Common device tree

Thor device tree

Apollo device tree

Docker instance that I use to build this

How do I tell the NSA didn't tamper with my download?!

Luckily, I signed the builds with my own key!

$ keytool -list -printcert -jarfile lineage-14.1-20180613-UNOFFICIAL-thor.zip
Signature:
Owner: EMAILADDRESS=steamport@protonmail.com, CN=steamport, OU=steamport, O=steamport, C=US
Issuer: EMAILADDRESS=steamport@protonmail.com, CN=steamport, OU=steamport, O=steamport, C=US
Serial number: b1b3cdcf593b5030
Valid from: Tue Jun 12 20:49:48 EDT 2018 until: Sat Oct 28 20:49:48 EDT 2045
Certificate fingerprints:
MD5: 13:E0:38:54:47:CC:FA:B8:24:50:16:6D:41:90:C7:4F
SHA1: 5F:AD:C9:4B:43:D3:1E:C3:6B:5F:86:DE:6A:F6:C7:F8:72:CB:B7:04
SHA256: BB:A1:BB:0F:7B:E1:62:2D:87:27:FE:EC:C5:CA:C6:B7:E3:EA:1A:CB:32:33:7E:F4:2C:D6:BC:BC:6E:46:27:CC
Signature algorithm name: SHA256withRSA
Subject Public Key Algorithm: 2048-bit RSA key
Version: 3

XDA:DevDB Information

LineageOS for microG, ROM for the Amazon Kindle Fire HDX 7" & 8.9"

Contributors

steamport

ROM OS Version: 7.x Nougat

ROM Kernel: Linux 3.4.x

ROM Firmware Required: Unlocked Bootloader, TWRP

Based On: LineageOS

Version Information

Status: Testing

Created 2018-06-13

Last Updated 2018-06-22
[Kindle Fire HDX 7" & 8.9" Original Android Develop] locolyric:
so confuse about microg. there are some games we must live with google play or the games can't run.

but micro g are great for user who not play games rely on google play.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] steamport:
What is there to be confused about? Yes, Google Play Games doesn't work with microG yet. Just don't play with games that mine your data. Problem solved. Or just try to lubricate it with cat piss. I don't care.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] CCF_100:
Stupid Question: does this support LTE?
[Kindle Fire HDX 7" & 8.9" Original Android Develop] steamport:
I don't think any Nougat ROM for thor or apollo supports LTE. Sadly, no.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
Correct - only KitKat based custom ROMs support LTE (data only). FireOS 4.5.x is the best choice for voice and mobile data support.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] steamport:
New zips are out. I just updated microG's GMSCore to one I built myself based on master and a fix PR. Also pulled from latest Lineage 14.1 sources.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] NeverSmile:
Bluetooth issue ? I still use kitkat because i can use bluetoooth. But so boring ..
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
Likely won't be any different with this ROM as core issue resides at the kernel level. Inconsistent connection behavior leads to erroneous claims based on individual experiences but really not ROM related other than the binary KitKat (Android 4.4.x) or above checkpoint.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] kfhdxuser:
Firstly this is an amazing ROM! Well done to you and the team! However, the recent Apollo release is broken. Not sure about the Thor version, i would check but the device I bricked because I was messing around... :( Anyway it boots successfully but the screen is blank and is still turned on, no boot animation other than the generic grey kindle fire. I can still tap the screen and hear android feedback noises after waiting awhile so it works! Just I cant see anything :laugh: The previous release worked fine, no problems! Maybe you could keep the recent previous releases available for download for backups in case? Thanks again ;)

Edit: Obviously I have the bootloader unlocked etc. Using latest TWRP if that helps at all.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] steamport:
I don't have an apollo, so can you do some debugging for me? ADB into it. It'll ask for authorization on the screen, just guess where the OK button is til it works. Anyways, when you do get adb auth, run this:

adb shell
logcat > log.txt
exit
adb pull log.txt

, then put the log.txt on pastebin and give me the link
[Kindle Fire HDX 7" & 8.9" Original Android Develop] kfhdxuser:
Been trying for about an hour now all i'm getting is feedback noises, is the confirmation dialog being prevented due to the setup process if there is one? Cant seem to get out of it and ADB keeps saying the device is unauthorized. I'll keep trying on the OS and once i get anything i'll update you as soon as i can. :)
[Kindle Fire HDX 7" & 8.9" Original Android Develop] steamport:
I've seen the dialog pop up as soon as it finishes booting
[Kindle Fire HDX 7" & 8.9" Original Android Develop] kfhdxuser:
Done!

Okay i've got a log file after a few unsuccessful attempts, i'm not sure why the code you gave me did not work but I tried myself using "adb shell adb logcat -d > Lineage14.1.txt" and that seemed to do the trick. (Hopefully this is what you were after).

I tried to upload this to pastebin but it refused so i've uploaded it to an alternative website here: https://paste.ee/p/kL4Ur
[Kindle Fire HDX 7" & 8.9" Original Android Develop] steamport:
Thanks.... this is a weird log. It mentions turning the screen on several times? Can you try fully wiping system and reinstalling?
[Kindle Fire HDX 7" & 8.9" Original Android Develop] kfhdxuser:
Yep i'll do that, was it the method that I used to extract the log file that could be the culprit? I should probably mention that you can see the screen when it turns off and on its just a different shade of black indicating that the screen works but it just won't display anything if that makes sense. I'll do a complete wipe and start again to see if its any different this time around.

Edit: Here is the new log: https://paste.ee/p/VK4oS

^^^

I've noticed it is considerably smaller this time around so hopefully this a good sign haha.

It is weird how the previous release worked and this one doesn't, i'd assume it's an application interfering from the latest build but if it works on Thor then it mustn't be right? Maybe something was accidentally changed for the Apollo release somewhere. Sorry if my ramblings aren't useful
[Kindle Fire HDX 7" & 8.9" Original Android Develop] NextDroid:
Thanks [MENTION=8668868]steamport[/MENTION]! What is the security patch level on this build?
[Kindle Fire HDX 7" & 8.9" Original Android Develop] steamport:
Whatever the latest for 14.1 was as of 6/7/18?
[Kindle Fire HDX 7" & 8.9" Original Android Develop] NextDroid:
Well, that depends, as the last AEX build, for example, was still on May 5.

Tapatalk を使用して私の LG-RS988 から送信
[Kindle Fire HDX 7" & 8.9" Original Android Develop] bobcat131:
I've got the same problem. Loads but no screen and unable to find the "ok" to authorize the device. There must be a better way.

I will revert back to previous version until this is fixed.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] pipyakas:
I successfully flashed the build, but screen-rotating is not working for me, and it was working previously on the non microg LOS build. Anyone has this issue?
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
Common issue faced by new ROM maintainers for Amazon devices. Best stick with one of the more mature builds until issues are ironed out.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] steamport:
How do I fix it? I didn't change the Device repos any.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
You'll need to consult w/@ggow.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] steamport:
Ok, so according to hashcode, it's several patches, spread out through the framework.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] lampylamp:
i changed the orientation with adb:

adb shell content insert --uri content://settings/system --bind name:s:accelerometer_rotation --bind value:i:0

adb shell content insert --uri content://settings/system --bind name:s:user_rotation --bind value:i:1

it keeps the orientation after reboot and power off but it obviously doesn't auto rotate anymore.

so it's only a solution for testing the rom more comfortably
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
I use Xposed module OwnOrientation on unlocked HDX devices regardless of custom ROM. Completely resolves bizarre rotation issues in all targeted apps; auto-rotate just works.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] sapientsaxonsaboo:
Latest Build Works

I was having the same issues with the ROM linked here and getting any display output after boot. However the latest version, lineage-14.1-20180818-UNOFFICIAL-apollo.zip seems to work with no issues so far. Screen rotation works perfectly too.

The only issue now is Magisk installation. I have tried flashing v12, v14 and v16 and all result in boot hang prior to loading the OS (i.e. before the LineageOS logo). Does anyone have any idea how to get Magisk to work with this ROM? Most other posts at least suggest success with earlier versions of Magisk.

- SSS
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
Boot hang following root attempt is almost certainly the result of failing to unlock the bootloader. Other operational anomalies will pop up over time with any non-kitkat based ROM running on a locked HDX. PM [MENTION=5828306]draxie[/MENTION] for a link to 1-click as previously advised.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] sapientsaxonsaboo:
How do I check if the bootloader is unlocked? I followed the instructions when preparing the device and received the message '"unlock code is correct". I would assume it's unlocked if everything went ok. I've tried running fastboot oem device-info but that just gives:

...
(bootloader)	Device tampered: true
OKAY [ 0.035s]
finished. total time: 0.035s

Nothing about the bootloader being unlocked so I'm unsure. I have used the LineageOS addonsu and that seems to work fine for rooting. I'd prefer to get Magisk working though.

Edit: actually, finally found a post suggesting to run 'fastboot oem idme' and if you get a response the bootloader is unlocked. I received 'idme done' so all looks good I assume...

- SSS
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
If you get a response from 'fastboot -i 0x1949 oem idme' the bootloader is unlocked.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] sapientsaxonsaboo:
Sure, just tried that too and still get a response (just edited the previous post, think we cross posted)...
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
Hum - don't have an immediate explanation why Magisk hangs on boot. I opt for SuperSU 2.82 SR5 on this device which suits my needs without Magisk wonkiness. Lineage su addon is also a good choice.

Edit: make sure data partition is formatted ext4 which is the default. Legacy kernel does not fully support f2fs.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] sapientsaxonsaboo:
Yeah, it's all good. Will use addonsu which is fine for what I need. Thanks for the pointers.

Testing encryption now which seems to have issues. Enabling encryption results in the android logo briefly, then flashes the Lineage logo and reboots. On reboot it creates a boot loop. The only way out is to format and restore. Have read reports about wrongly sized data partition or installing another ROM, encrypting, then rm-f and flashing LOS again to keep the encryption in place.

- SSS
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
Encryption is a nightmare on this device; stay away.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] sapientsaxonsaboo:
I can certainly confirm. It looks like encryption doesn't work with this ROM. The errors attempting to encrypt shown in logcat suggest that there is a library/module missing in the build so it's definitely not possible. I did manage to find a CM 14.1 ROM and was hoping to be able to use this to enable FDE then possibly use TWRP to rm -r the content and re-flash LineageOS. However it appears the TWRP images for the device don't support decryption and attempts to boot failed to unlock the drive anyhow.

The CM 14.1 ROM was also problematic when enabling FDE. Initial attempts via the UI rebooted the device and caused a boot loop. I did manage to get it to work at one point via the UI but couldn't replicate it. Using both EXT4 and F2FS it still failed to encrypt the drive. Logcat for both showed the well known issue with the data filesystem having no space at the end of the partition for encryption metadata. As there is no way to resize F2FS I tried recreating and leaving ~32KB free at the end with no luck. There is a solution for EXT4 though as per this thread and basic instructions below (see thread for commands).

1. Boot into TWRP

2. Get to adb shell

3. Resize the EXT4 data file system

4. Boot to CM 14.1

5. adb root and then adb shell

6. Run the encryption via adb shell and use the wipe rather than inplace option (remember you'll have to backup any data using an in OS option like Titanium as you can't access/restore the data via TWRP)

7. This will fail and complain that the F2FS filesystem can't be created on the encrypted container dm-0

8. Run again and it will succeed

9. Reboot, enter your PIN or passphrase then wait for initialisation (I had to wait for a few hours)

It's a shame that the microG ROM doesn't work as it would have been preferred, however I think encryption is a necessity on any device.

- SSS
[Kindle Fire HDX 7" & 8.9" Original Android Develop] steamport:
I'm going to update this ROM when a version of microG services core is released that actually works with the latest app updates.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
I would rephrase as desirable on most modern devices and a necessity for some users depending on device contents (data and app portfolio), exposure and other security practices that mitigate losses if the device is compromised (eg: stolen). Most of my legacy gizmos are unencrypted for various reasons. I sleep well understanding the risks and worst case scenario should the device go missing. A few pictures of the dog and a bunch of unsecured logs. Oh wait, SSIDs and associated MAC addresses. Meh ...
[Kindle Fire HDX 7" & 8.9" Original Android Develop] steamport:
Alright, microG is working again it seems. As I'm a man of my word. I'm going to update this soon... Just gotta find my signing keys.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] lokalkey:
any news?
[Kindle Fire HDX 7" & 8.9" Original Android Develop] gt_o:
Please find a new build here:

https://www.androidfilehost.com/?w=files&flid=291502

The security patch is dated March 2019 and it uses the ng-7.1 branch for the kernel.

There seems to be an issue with Google Maps though. It always crashes for me when I am closing it.

Have fun!
[Kindle Fire HDX 7" & 8.9" Original Android Develop] pipyakas:
it's running good for me, although I haven't complete the setup yet

Can you make a build that prioritize landscape mode as the default orientation? As in taking the current 270 degree as 0 degree?

I know that the wiring's making it difficult but the form factor was designed with landscape in mind, but having the rom priorizite portrait view makes a few things awkward
[HD2 Windows Mobile 6.5 Themes and Apps] betatest3:
A while back I found a link to a mediafire archive with something like 50 CAB's in it, for Windows Mobile 6.x. Does anyone know where that archive is?

It used to be bookmarked on my computer, but I accidently deleted it, so it's now gone.

I imagine that some of those CAB's are probably somewhere else on the interwebs as well, but I have been searching all day to no avail.

Also, FreewarePocketPC still has lot's of stuff available for WM devices, but a lot of it is intermixed with crap for Android(most of the Android **** that's clogging the site is just virus anyways), and Windows Phone 7, and some of the links are dead.

P.S. I have an archive of CAB's as well, I will be sharing soon, most of the CAB's I have are still available elsewhere on the interwebs, but with WM6.x getting older by the day, and so many things linkrotting as we type, it won't be long before the ever-diminishing set of workable programs reaches zero, and our beloved WinCE/WM6.x based devices are dead forever. So the more mirrored archives there are, the better.

NOTE: IF anyone wants an app, PM me, do not clog the forums with requests. NO, I do not have warez and paid software, I do not have any way to make your paid software work without paying, DO NOT ask for warez, if you do, your PM will be copied to this thread for everyone to see and laugh at.