yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] Pyconehd:
Hi, hopfully someone will help me with this, I bought an Xtrons IA Octa core for focus MK3 and i have no ideea where on this forum where i should look after. Can you tell me guys what type is mine?

HMI: TSKJ.G6.A.Q.F.X.2022.12.01.14.56

MCU: G6FOX.220716(VHD)

BUILD NUMBER XTRONS_IA_)cta core
[OnePlus 7 Pro Questions & Answers] mkarim78:
Hello all,

Even though it is my first post, I'm an old member...

I know people is alwas asking for that answer but I need to ask it before having to reset my phone.

I've never used the pattern way of locking my phone and rather used instead password but I decided to use a pattern to lock my phone and now that I've forgotten it, I'm stuck...

My phone is on stock Rom, locked bootloader and USB debugging mode activated.

Is there any way to bypass that security and to use my phone again WITHOUT wiping anything (I'm on travel and I completely depend on my saved datas, that's why I'm looking for any way to do that) or am I just wasting my time ???

I know a lot of people will tell me that it's not possible but I'm still hoping that one will tell me it is and will give me the way to do that...

Thank you all...
[One (M8) Android Development] npjohnson:
One M8

- Your warranty is now void.
- You have been warned.
- Use at your own risk.

Introduction:

This is the unofficial Lineage OS 18.1 thread for the HTC One M8.

Downloads:

Please follow the install instructions in your device's Wiki page linked below exactly, and make sure your device's firmware matches the required firmware listed.

m8 - Single SIM models

m8d - Dual SIM models

If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.

Known Bugs:

Find any? Report them according to this guide.

Notes:

This is my unofficial with Google Apps/Pixel goodies included. Passes SafetyNet by default. OTA's roll roughly once a month. Support not guaranteed or implied.

Kernel Source: https://github.com/LineageOS/android_kernel_htc_msm8974
[One (M8) Android Development] ze7zez:
The link to the ROM.zip is not easy to find.

Odd Solutions Downloads

updater.oddsolutions.us

Odd Solutions Downloads

updater.oddsolutions.us
[One (M8) Android Development] npjohnson:
Because I don't want people blindly flashing the zips.

I want them reading the wiki and following the instructions - they will download all the files they need in the course of the install guide.
[One (M8) Android Development] K3li:
For some reason some app thinks my device is rooted - even disable developer options but that didn't work. Any particular reason?

Also, I cannot seem to get network location working. Not sure if it's okay to post this here rather than the Gitlab bug tracker but I'll do it anyway considering the device is not officially supported (m8wl variant running the June 23, 2023 build).

Attached are some logcats.
[One (M8) Android Development] K3li:
For some reason one logcat won't upload (the com.google.android.gms one)

Let me try it here.

Edit: It didn't work either. So i've compressed it and it worked.
[One (M8) Android Development] K3li:
So I did a little digging. Using *#*#4636#*#* and going to the Phone information screen, I was able to pull some hex cell info values for the LTE network (LAC=3702, CID=7a0a0b) which translated to 14082 and 7997963. These are consistent with the telephony logcat values which I provided above.

RIL_REQUEST_GET_CELL_INFO_LIST [CellInfoLte:{mRegistered=YES mTimeStamp=572865009389ns mCellConnectionStatus=2147483647 CellIdentityLte:{ mCi=7997953 mPci=227 mTac=14082 mEarfcn=0 mBands=[] mBandwidth=2147483647 mMcc=639 mMnc=null

I tried locating this tower using OpenCelliD but it wasn't found.

Anyway, I switched to GSM network (LAC=84f, CID=3089) which translated to 2127,12425 and entering these on OpenCelliD got me an instant hit! Naturally, I went back to the telephony logcat to check out these values. Something is wrong somewhere.

CellInfoGsm:{mRegistered=NO mTimeStamp=572865009389ns mCellConnectionStatus=2147483647 CellIdentityGsm:{ mLac=2147483647 mCid=2147483647 mArfcn=0 mBsic=0x0 mMcc=null mMnc=null

The value "2147483647" is everywhere! Like someone hardcoded it. Obviously mLac, mCid or mCellConnectionStatus cannot be "2147483647"!! Also, mMcc and mMnc shouldn't be null especially if there's a working Sim card present.

I think this is why google can't get a location because the supplied values from the "CellInfoGsm", "CellInfoLte" and "CellInfoWcdma" functions are wrong.
[One (M8) Android Development] K3li:
For anyone interested,
[One (M8) Android Development] Firdovsi82:
Cannot download, says download failed authentication required
[One (M8) Android Development] npjohnson:
What?
[One (M8) Android Development] Firdovsi82:
Now downloaded with another phone. Checking now, before i downloaded with my M8 where AICP rom installed at 70-80 % download failed and says authentication required. By the way happened twice. Never mind i downloaded with another phone
[One (M8) Android Development] npjohnson:
It downloads fine here
[One (M8) Android Development] Firdovsi82:
Tested rom. What can i say. It is not bad and usable, but did not lik camera app i think it would be better if Gapps pico had been ported. Too many google apps here such as play movies, yt music etc. Overall great thanks for keeping M8 alive
[One (M8) Android Development] Firdovsi82:
Please read this review carefully before flashing this rom.

Cannot boot to recovery after flashing this room. Solved by installing another twrp.

When i installed another rom after this my phone says sim card not installed however it was installed actually. Fixed by several times format my phone via TWRP. Something strange...
[One (M8) Android Development] K3li:
For the sake of tinkering, I decided to look into /e/'s recovery because it DOES work on the m8 and I wanted to compare it with the one bundled with this ROM.

Unfortunately LineageOS's bundled recovery does not play ball when it comes to unpacking - /e/'s recovery does unpack.

I asked Tad about this and he said it might be RAMDISK related - DivestOS recovery for the m8 doesn't work as well.

Here's the output of file command on both recoveries:

Can the compression method used on the LineageOS's recovery have something to do with it refusing to unpack and by extension not working on the device even when flashed successfully?
[One (M8) Android Development] npjohnson:
Doesn't /e/ just build our devices as they are?

That's confusing.

Do they make any modifications?
[One (M8) Android Development] K3li:
I'm not sure if there's any special modification that they do with their recovery build, I can't tell yet.

I've just tried unpacking a twrp recovery file and it worked.

So something must be preventing the LineageOS recovery from unpacking and maybe that's why it doesn't work.

Attached are the directory trees for /e/ and TWRP recoveries. Maybe you can spot/catch something.
[One (M8) Android Development] npjohnson:
I need the device tree that /e/ builds to compare things
[One (M8) Android Development] npjohnson:
wait. where are you getting /e/ OS Android 11 for the m8 from? They only support it on 10
[One (M8) Android Development] K3li:
I'm not using their ROM, I'm using DivestOS (Android 11) but their recovery works even though it's for their Android 10 ROM. I used it a few minutes ago to dump the recovery partition (adb shell cat /dev/block/mmcblk0p45 > recovery.img) and it works just fine.
[One (M8) Android Development] npjohnson:
Dude, lineage's 17.1 recovery boots fine. Of course /e/'s would work from Android 10.

The issue is something related to Android 11 changes.
[One (M8) Android Development] K3li:
And that's why I was asking if it has to do with how the image is compressed.
[One (M8) Android Development] npjohnson:
we've tried various image compressions, it just doesn't work on 11.

Tried LZMA, XZ, LZ4, etc.

Also, the image is totally unpack able, just not by your script unmkbootimg works fine.
[One (M8) Android Development] K3li:
I see.. I'll give unmkbootimg a go then.
[One (M8) Android Development] K3li:
I've just tried unmkbootimg and it does indeed work. What's strange though is that with DivestOS and your recovery I have "Secondary address 0x0" and "OFF_SECOND_ADDR is 0xFE200100" which are different from twrp (including the latest version) and /e/'s recovery. They all have "Secondary address 0xf00000" and "OFF_SECOND_ADDR is 0xFF100100".

I thought these addresses were supposed to stay the same?

Anywho I don't know much about this but I'll continue exploring.
[One (M8) Android Development] npjohnson:
Hey all, I am moving and therefore the unofficial update server/wiki will be down for a few days. Likely Wednesday, Friday at the worst.

Don’t panic when links in the OP don’t work, and your Updater app says something like “Can’t connect to server”. It is planned outage.

Thanks, see you on the other side!
[One (M8) Android Development] npjohnson:
Hey y'all - Unofficial build server/download portal is back up.

It may be hit and miss tomorrow as I rewire everything, but everything /should/ be functional for now.

Thanks!
[One (M8) Android Development] Broman400:
Off topic, but thank you for keeping this ROM updated. It works fantastic on my M8
[One (M8) Android Development] spawnho:
How about those periphal in the ROM?

1. Mhl

2. E-Compass

3. NFC
[One (M8) Android Development] npjohnson:
1. No clue probably not?

2. Yes.

3. Yes.
[One (M8) Android Development] tejljr:
Any chance that this rom will be updated to Android 12 or 13 in the future? The other roms I tried aren't as stable as this one.
[One (M8) Android Development] npjohnson:
Nope.

We have a whole blog post on why legacy devices were dropped, I recommend you go read it.

In short the 3.4 Linux kernel is just too damn old, net VPN, and pretty much all of Android's newer features break.

There's no fixing it, we can't use a newer kernel version feasibly, and we can't backport what is needed.
[Miscellaneous Android Development] npjohnson:
Mini 5G

- Your warranty is now void.
- You have been warned.
- Use at your own risk.

Introduction:

This is the Official Lineage OS 20 thread for the Mini 5G.

Downloads:

Please follow the install instructions in your device's Wiki page linked below exactly, and make sure your device's firmware matches the required firmware listed.

TP1803 - Official builds

TP1803 - My unofficial with Google Apps/Pixel goodies included. Passes SafetyNet by default. OTA's roll roughly once a month. Support not guaranteed or implied.

If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.

Known Bugs:

Find any? Report them according to this guide.

Notes:

The only supported GApps package at the moment is MindTheGapps, linked on our Wiki page about gapps.

Kernel Source: https://github.com/LineageOS/android_kernel_nubia_sm8150
[Miscellaneous Android Development] npjohnson:
Hey all, I am moving and therefore the unofficial update server/wiki will be down for a few days. Likely Wednesday, Friday at the worst.

Don’t panic when links in the OP don’t work, and your Updater app says something like “Can’t connect to server”. It is planned outage.

Thanks, see you on the other side!
[Miscellaneous Android Development] npjohnson:
Hey y'all - Unofficial build server/download portal is back up.

It may be hit and miss tomorrow as I rewire everything, but everything /should/ be functional for now.

Thanks!
[Miscellaneous Android Development] jackeagle:
Moderation Edit

Thread closed per [OP] request.

-jackeagle

Senior Moderator
[Google Home] Chewie610:
Installing MicroG and the Newest Version of the Google Play Store (Magisk Required)​

Download and install the MicroG Services Core and Services Framework Proxy from the MicroG site.

Install the Magisk app (use the Magisk APK). When you open the app, it should say the version of Magisk installed next to "Installed."

On your Android Device go to Settings > Connected Devices > USB > File Transferring Mode.

Download the NanoDroid-patcher.zip file, BusyBox.zip, and terminal_systemizer.zip. Do not unzip these files. Drag and drop these devices onto your Android device.

In Magisk > Modules > Install from storage, find the .zip files and install all 3 Modules. The NanoDroid-patcher module in particular may take awhile so be patient.

Install the apk of Google Play Store of your choice.

Install Termux. In Termux, issue the command

su

A superuser popup should show up. Make sure to allow Termux Superuser access. If you miss clicking on it, you can allow access in the Magisk App > Superuser.

systemize

Follow the dialog prompts to systemize Google Play Store to /system/priv-app

Restart the device.

Open the microG settings app. Register the device in Google device registration. In Self-Check, click on each setting (the words, not the checkboxes) and enable them all. Pay particular attention to System spoofs signature being checked off.

Restart the device again if you want. Google Play Store should be working fine now (may need to clear it's App Data first if it's not working).

Installing Custom Webview (Magisk Required)​

Some apps such as HomeAssistant won't function without an up to date System Webview. As this tablet is running a quite old version Webview version, this causes these apps to not work. Luckily, there's a Magisk Module to fix that.

Download the Webview_Manager zip file and drag and drop it onto your device. Install it using Magisk. You will need to watch it install as it requires some input on which Webviews you want to install.

After restarting the device, navigate into Settings > System > Developer options > Webview implementation. You should now be able to change your Webview to a updated version.

Note, you may need to unplug and replug in the device after the first restart of installing Webview.
[Google Home] Chewie610:
Reserved 2
[Google Home] deadman96385:
A slightly easier way that may work I haven't validated on the thinksmart specifically is using qfil's partition manager tool. It allows you to dump, erase, flash individual partitions, that way you can flash just the one you want without having to deal with a full qfil flash. Finish all original steps up to 10. Instead of clicking download do the following instead:

Navigate to the top menu: Tools -> Partition Manager -> OK. If all goes well, you will be greeted with a dialog listing all partitions in ~5s. If this is not the case even after a full minute, try re-entering EDL/9008 mode.

Once the partition list is loaded, you can perform the following actions on partitions by right clicking a partition and then clicking 'Manage Partition Data'.

This is also a great way of backing up partitions from your device. The dumped partition can be found in C:\Users\%USERNAME%\AppData\Roaming\Qualcomm\QFIL\COMPORT_##. Note that the name of the file is the raw file locations so you will need to rename the imgs as you go.
[Google Home] flog2023:
Hi!

I put the 200628.084 firmware into the Zoom model.

Right now it's in stock android for now.

The problem is installing Magisk.

Of course I'm replacing the boot.img in the firmware, but when I install Magisk.apk, it says Magisk is not installed. So I can't select a module, I can't proceed from there.

I've tried replacing the boot.img and flashing it again several times, but no matter how many times I try, it doesn't work.

That's the only thing I can't figure out.
[Google Home] Chewie610:
Hm... so you've replaced the boot.img in the firmware files? Then you flashed that firmware to the device using the QFIL program?
[Google Home] flog2023:
Thanks for the reply.

Your post has helped me a lot.

You are right. I used QFIL to write the boot.img in the image folder in the extracted 200628.084 farm and replaced it with the boot.img in your post.

Everything is working fine so far except for Magisk.

I'll try starting all over again.
[Google Home] Chewie610:
Oh, interesting. I'm not sure if you're doing it in this order so I'd like to clarify the instructions.

1st: Download the boot.img from the post above. Using your computer's File Explorer, open the firmware files. In the image folder, replace the boot.img file with the one you downloaded.

2nd: Use QFIL to flash the device.

It's been awhile since I've done this, so I'm not sure if you're required to click the "Install" button in the Magisk App. I don't think it's necessary though.

If this doesn't work, there is technically another way to flash the device manually. It's a little harder but your device won't get bricked, it'll just seem likes it's bricked if you don't do it correctly. The instructions are found in the spoiler under here:
[Google Home] keller4879:
Both you and Deadman are absolute legends for this, as someone with no experience modding android outside of some basic adb commands I was able to make this work for me after a night of trial and error. Device is really high quality so I'm happy I could re-purpose it from being pure e-waste.

Few things I ran into that may be useful for others:

- Had to use the 200628.084 Version, newer one would always just lockup on the final Lenovo logo when rebooting.

- QFIL wouldn't initially detect any ports until I disabled driver signing. Second time I re-flashed it it found the ports but would give Sahara error until i went back into Test Mode.

- Device never came back on automatically after flashing, always had to pull the power.

- No idea how but after installing the updated webview it completely broke screen rotation, ended up having to re-flash and start again. This one is likely my screw-up though.

After completing getting it setup i found there were a few packages that I needed to remove before considering it fully functional. Don't have the exact package names but the important ones were:

Kiosk mode app (Search "kiosk")

Boots into MS Teams on startup, and if team's removes still boots to a blank screen.

Managed settings (Search "managed", "management", "provisioning", "mdm")

Constantly resets your settings to default, very frustrating when trying to disable auto-brightness.

There's multiple device management apps installed and unsure which one finally fixed it.

Device Settings

The settings menu from that cog at the top right of teams, seemed to override changes in the default android settings menu

Use "adb shell", "pm list packages" to get the full list, then "pm uninstall -k --user 0 {PACKAGE NAME}"

i.e deleting the navigation bar Chewie included would be

There was allot more bloatware but those are the main problem apps I remember.
[Google Home] KacperA:
Hey @Chewie610 is that normal TWRP touch isn't working?

[EDIT]

Yes it is - because of used screen type. Need to wait to screen - off, then power up once and all works
[Google Home] Chewie610:
Hey keller! Glad it worked for you! Thanks for the information you provided, hopefully it'll be able to help someone else in the future.

This was actually one of the first times I've tried modifying a device so heavily, the device was too well made to not try lol.
[Google Home] morewordsfaster:
Hey, thanks for the guide! I was able to install the new firmware, get Magisk working, Termux, and microG, but when I try to install the Play Store APK per the guide, I get an error: adb: failed to install .\com.google.android.gms-223616054.apk: Failure [INSTALL_FAILED_ALREADY_EXISTS: Attempt to re-install com.google.android.gms without first uninstalling.]. Hoping someone can help as it's been a long time since I've done the cfw thing. There's a navigation bar app that I've paid for the pro version but I can't seem to update it on the tablet without getting Play Store working. I assume I'll need a pro version of a button mapper app too to be able to use vol +/- as back and home as well.
[Google Home] Chewie610:
Hmm... that error comes from if you already have a package/app with the same name on the device.

I'm going to assume you've already installed the NanoDroid-patcher.zip file, BusyBox.zip, and terminal_systemizer.zip onto the device using Magisk (up to step 5)?

Go ahead and check if you already have the Play Store App installed on your device. You can check in Settings > Apps, but you can also check from the launcher.

We can try to uninstall this app using the device's UI or by using "adb uninstall com.google.android.gms" on your computer. Please let me know what you've done and I can try to help you more!
[Google Home] jalohax:
After reading that thread, I have bought brand new box, pretty cheap.

FIrst issue I have encounter was not able to get to EDL mode...

It looked like journey ended at the beggining. So after few attempts I started to look what I can do within that Teams device and appereantly "-" button was not working. I have enabled debug loggin within settings and was able to restart it manually to get things going.

Wen through all above instruciton twice. Both times ended:

- no matter which launcher will use, while device is in horizontal position it always shows "main view" in vertical, while applicaiton seems to be running fine in horizontal view.

- I have used firmware - CD-18781Y.200628.084, but always I have ended with bricking device while installing webview part.

3rd last atempt, I have ended with just google store, leaving webview at all, uninstalled all unneeded stuff. As I wanted to use it with HA, I just installed button mapper, nav bar, boot control and Chrome

Last issue I am facing now is "locking screen" or getting it into sleep. It just runs randomly.

I have set 15s timeout for sleep mode, and immediate lock screen action.

But still very often it just stays on forever. Other time it just go into sleep as needed.

What is more, while I press "lock" button, it also very often just shows black screen with lock but still screen is visible.

I tried to remove all of the other stuff even mcroG and google store, leaving only mentioned apps nad Magisk but still no luck. Removing installed apps also do not help...

Any ideas?
[Google Home] Chewie610:
If the volume - button doesn't work, that would for sure make EDL mode hard to get into...

Regarding "main view," do you mean when you return to home of the device? If so, I need to dig out my device see if that's also the case for me. Can't remember.

I can't exactly remember what happened when I installed webview, but if I recall correctly, I think I thought the device was bricked the first time around. I had to unplug and replug the device back in to get it working, but I can't exactly remember how long it took. If you want to use HA, you do need an up to date webview, otherwise the app will not work.

I need to dig my device out to see how the screen falls asleep. When you say you press the "lock" button, are you referring to a button mapped "lock" button? I think I was able to get HA to fall asleep but I also need to check on my device.

Let me find my device and get back to you.
[Google Home] jalohax:
Yea a little wrong wording :) home screen is always in vertical position no matter what I will change as launcher - while when selecting apps or settings tab it goes to horizontal.

I have even tried to while being in horizontal application view, to lock autorotate via ADB, but no luck.

Anyway as long as Chrome is woring in horizontal I don't really care about :)

I can see that also one of the post here mentiones something about screen rotation:

Regarding webview part, I ended up not using HA as app, or custom view, but directly in Chrome (HA runns addon to be able to run it in kiosk mode) - lets say its fine enough.

*also not sure, but as long you have google store available cant it be just installed from there?

When I did replug it booted in recovery mode asking to try again/erase few times, but as long as I do not have "-" button I couldnt choose any

Yea, I did map "+" button as lock one.

But no matter even button or time schedule in settings end same. I just left tablet now in Home screen when placed 1st post and it was turned on till now. But when I clicked Chrome and left it just turned off within 15s.