yashsingh1/xdaforums huggingface dataset:
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] ultramag69:
2 things to check, the .nbh file MUST be named hermimg.nbh with no spelling errors. The sd card MUST be 2Gb or less and HAS TO BE FORMATTED FAT32. It comes formatted FAT.

To get to bootloader, hold power, ok button above flywheel and reset with stylus. Hold in until tri-colour screen appears.

I know you are familiar with it but others who read this may not be.

Most people who say that it doesn't work have the one of the 2 things I mentioned set up wrong, mostly they don't format the sd card FAT32 as they assume its already formatted like that. I also found, on occsion, even though I had formatted the SD card \fat32 that it required formatting again.

Hope this helps.

Cheers...:D
[Treble-Enabled Device Development A/AB ROMS] harvey186:
Hi all,

I have created a GSI based on latest TrebleDroid AOSP Android 13. Thanks all TrebleDroid devs for the great work.

What is LeOS:

1. It's full ungoogled

2. It includes full Working MicroG -- but this is a special LeOS-MicroG version. pls see attachment

3.This version is still a beta version and not booting on all treble devices. In some cases the GSI is better booting on devices with a custom (LineageOS) rom as base. Especially devices with A10 firmware.

4. available for now only arm64 VNDK

5. no google Apps will work !!!!

You can download latest release at https://leos-cloud.de/s/JFrFgLgSSTEMtmL?path=/LeOS-T-beta

A list of tested devices is also available in download section

Join us a telegram group for support: https://t.me/LeOS_Support

Short overview: http://leos-gsi.de
[Treble-Enabled Device Development A/AB ROMS] Ainz_Ooal_Gown:
So in theory you could flash this with Pixilify and have a Pixel ROM on Android 13???
[Treble-Enabled Device Development A/AB ROMS] bentalebnordine:
Beta 8 won't boot (stuck on bootanimation) on my OnePlus nord 100
[Treble-Enabled Device Development A/AB ROMS] Aniketvardey:
Booted

Device: 10orG

Codename - holland2

Bugs:

camera - 99% vendor issue

Maybe more
[Treble-Enabled Device Development A/AB ROMS] massima:
Sad but Huawei Mediapad M5 bootloops :confused:(Android 9 vendor), i swiched back to Phh v415.
[Treble-Enabled Device Development A/AB ROMS] birdibird:
I am running the LeOS 20 version. This rom is wonderfully fluid on my Cubot Kingkong mini 2 A64 device. It runs better than A12.1!
[Treble-Enabled Device Development A/AB ROMS] bentalebnordine:
Yesterday January 24th I can't log in to Google sites from LeOS A13🤔
[Treble-Enabled Device Development A/AB ROMS] birdibird:
That's the design of LeOS -> ungoogled GSI. Choose another GSI if you need google.
[Treble-Enabled Device Development A/AB ROMS] bentalebnordine:
Hi guys, I wonder where you moved next your files, the last location is empty 👀
[Treble-Enabled Device Development A/AB ROMS] K_a_m_i:
I'm also looking for the files.
[Treble-Enabled Device Development A/AB ROMS] birdibird:
Here you can find the recent links:

https://leos-gsi.de
[Treble-Enabled Device Development A/AB ROMS] bentalebnordine:
Thank you
[Treble-Enabled Device Development A/AB ROMS] bentalebnordine:
Thanks,

LeOS-Files

LeOS-Cloud - make Love not Waste

leos-cloud.de
[Treble-Enabled Device Development A/AB ROMS] K_a_m_i:
Thank you!
[Treble-Enabled Device Development A/AB ROMS] bentalebnordine:
Best battery life 🔋📱
[Treble-Enabled Device Development A/AB ROMS] dank2019:
What happend to LeoOS 20? I cant find it anymore.
[Treble-Enabled Device Development A/AB ROMS] bentalebnordine:
LeOS-Files

LeOS-Cloud - make Love not Waste

leos-cloud.de
[Treble-Enabled Device Development A/AB ROMS] dank2019:
I cant see there LeoOS 20. Any naming mistake from my side? Do you have a direct link?
[Treble-Enabled Device Development A/AB ROMS] Vilkoko:
Hello,

I don't know if I posted in the right topic. Just to let you know I have a SMS issue with LeOS 20, explained here.

Thank you

Edit: this was a sim problem, nothing to do with LeOS or my phone. Forget my warning.
[Treble-Enabled Device Development A/AB ROMS] Hatrackman:
TextNow is dependent on Google Play Services to login (after which I disable it). Can that dependency transfer to MicroG?... Isn't that what MicroG is for?

PS: I'm using a lot of your apps and would otherwise be using LeOS if it were not for my parameter of needing TextNow (I don't use a sim card, banks or bluetooth and find arbitrary encryption of my Android folder insulting). Anyhoo, cheers.
[Treble-Enabled Device Development A/AB ROMS] KenHerman:
FYI - I've updated my Sony Xperia 1 iii to this rom successfully. It is now my dd (from LEOS 19.1/A12). There were a few bumps in the road, but it all (all that I need) seems to be working fine. For others, here are my observations, etc...:

OS / System Apps:

1) I use VNDK-arm64 - not LITE. LITE doesn't boot properly and shows as corrupted. This was pretty much the same for 19.1.

2) LEOS-Phone app is wonky - i.e won't receive calls and won't dial out sometimes. I use Simple Dialer instead - this works perfectly. It took a while and a bunch of fiddling to determine it was the app - not the OS.

3) LEOS-contacts is usable, but wonky. Crashes in some Group tasks (like adding contacts occasionally). Again, I use Simple Contacts instead. I wish some app could handle group and ringtone back-up and restore - not just contact info (still looking for good way to do this).

OS Settings:

1) SMS (MMS) needs: PHH Treble Setting - IMS Features: both checkboxes checked / install APK / and Create IMS APN - in order to receive MMS messages.

2) Headphone jack needs: PHH Settings - Qualcomm features - Use alternate audio policy checked - otherwise plugging in headphones won't be recognized.

3) Camera needs: PHH Treble Settings - Qualcomm features - Use alternate camera profile checked. Also PHH Treble Settings - Misc features - Expose Aux cameras and ForceEnableCamera2APIHAL3 checked - to use all cameras. I use Open Camera app.

Issues:

Misc.:

I try to use Open Source apps (F-Droid) as much as possible. Here are some of the ones I rely upon (in no specific order):

LawnChair (12) - launcher

BitWarden - passwords

Neo Backup - backups

Open Camera - camera

OSMAND - navigation

NewPipe - youtube

VLC - media player

RHVoice - text to voice

Dicio - digital assistant

K9 Mail - mail client

Simple apps (Simple Mobile Tools) - a bunch of utilities

Simple Solitaire Collection - gotta have solitaire

Super Retro Mega Wars - old timey games

Obsidian (with SyncThing as sync to PC) - notes

Geometric Weather - weather (obviously)

World Clock & Weather - alternate time zone display (not weather)

I also use Magisk with:

AccA (Advanced Charging Controller) - control charging % to extend battery life

AlwaysOn - display clock and battery level at night during charging (with display off)

CloudflareDNS4Magisk - DNS

If you have any suggestions or alternatives, I'm open to hear about them.

Other than the small issues mentioned above, everything seems smooth. Great OS for non-Googled phones. I highly recommend it. Very polished and reliable. Plus monthly security patches and updates at:

LeOS-Files

LeOS-Cloud - make Love not Waste

leos-cloud.de
[Treble-Enabled Device Development A/AB ROMS] PantsDownJedi:
This is really good. Thank you for putting it together.

On my phone, the only problem was initializing the Mozilla location module.

It just needed to have the settings for which information, WIFI and Cell Data, disabled, then the Mozilla module could be enabled, afterwards the WIFI and/or Cell data could be selected.

Everything else I've used is working.

+Oops, I spoke too soon. Wifi reverts back to DHCP after setting it to a manual address.
[Treble-Enabled Device Development A/AB ROMS] veloc_h:
Thanks for this great rom. Very reactive! With andyyan's rom I had a tts configuration problem (settings wouldn't let me configure the tts, it would instantly close).

Use the king kong mini for navigation using f-droid ( osmand and brouter). However I have to activate "Disable HW overlays" (thanks @michael205!), see https://xdaforums.com/t/flickering-screen-on-gsi-rom.4289667/ . Otherwise Osmand would flicker every 2 seconds. Is there any other less battery consuming work-around?

I didn't have the problem with AndyYan's LOS adaption (not sure about his phh treble /misc features default settings).

I do like the screenshot feature (which is not available with Andyyan's custom rom).

I followed these installation instructions on

https://gitlab.com/leos1/leos-wiki/...Android-10-and-above-(with-dynamic-partition). Instead of the crossed commands I selected fastboot mode/recovery mode with the help of vol+ and on/off buttons (commands did not work).

Plus i changed the sequence of factory reset

For cubot king kong mini the proper vbmeta.img is the one, which fits the cubot rom version, which is allready on the system

reboot recovery via recovery mode via vol+ and on/off

use "factory reset / wipe data"

adb reboot bootloader fastboot mode via vol+ and on/off

fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img

fastboot reboot fastboot

fastboot flash system LeOS.img

reboot
[Google Pixel 4 XL Themes, Apps, and Mods] darkpower_4:
I just got a new pixel 4 xl from Google. Yes I said new. I had a bad battery batch from my preorder pixel 4 xl and it wasn't as bad but it was sensitive to 70°F Santa Cruz CA weather and over heat while charging in my car. I'm a phone technician myself so I'm savvy on quality charging equipment always used it. But it took this long to convince and my phone finally "not reading meter" not charging. It came with Android 10 still. So its upgraded to 13 and it's the 3rd fastest google phone out so why is my pixel 3xl which started rebooting over and over still getting lineage 13 updates but no android 13 custom roms for the 4 xl? I might have to change that start selling a AWS script to build 13 Roms?
[Google Pixel 4 XL Themes, Apps, and Mods] #mcl:
I think maybe it's because it's still supported, and android 13 was launch mast month, so maybe as there isn't a very high demand, and it has been launch recently, devs didn't made the android 13 roms.

I would like to create them but I am working in getting a method to unlock the bootloader of a carrier-locked Pixel.
[Google Pixel 4 XL Themes, Apps, and Mods] kmry:
hows your battery and SoT in A13?
[Google Pixel 4 XL Themes, Apps, and Mods] #mcl:
My battery usually lasts the hole day, with motion sense enabled and the always on display based on motion sense. Medium usage though. For high usage I need to charge it on the middle of the day .

I don't know what SoT means 😅
[Google Pixel 4 XL Themes, Apps, and Mods] kmry:
SoT means Screen On time, which is how many hours you really use the phone with the screen ont; you can find more on the battery configuration or with GSAM for example.
[Google Pixel 4 XL Themes, Apps, and Mods] darkpower_4:
Well it's definitely better I've been using soli now that I have a new battery and the battery life has been about the same if I'm comparing it to 6 months before I had to rma it with soli disabled. I've been putting it through its rounds as a doordash driver. It doesn't die as quickly it runs a lot better. Android 11 was the worst I felt like when 12 came out I was robbed a whole year of performance before and 13 is even better I just want there to be security updates.
[OnePlus 9] c0d3f0rc37:
Good day!

Is there any way to get the official OnePlus 9 T-Mobile (LE2117) OxygenOS zip file? Android version does not matter (11 or 12).

I want to install it by:

I found official OOS from the OnePlus website, but it has only global version. (BTW I was able to sideload it and it works)

PS: I found the MSM Download Tool for it, but I'm having trouble with installing it, as it is stuck on "Waiting for device". Although I installed Qualcomm HS-USB QDLoader 900 driver.

Thank you!
[OnePlus 9] _MartyMan_:
You'll need this driver for MSM to work.

Also you need to boot to EDL: Power off, Hold down both vol up and down, connect device to USB. Then click enum in MSM and the device will show up.

FYI it'll only work with USB 2.0, anything else will fail on donwloading super.img.
[OnePlus 9] rizzmughal:
How did u sideload global rom
[OnePlus 9] c0d3f0rc37:
I wanted to install StagOS as shown here. After booting into recovery mode I found out that I can easily sideload zip file. So, instead of StagOS file I used OxygenOS one.

Note: my phone's bootloader is unlocked.
[OnePlus 9] c0d3f0rc37:
I was hoping to find the official zip file and install it the easy way. But, I think the MSM is the only way for now. So, will try your guidance. Thank you!
[OnePlus 9] mattie_49:
Thread 'Tmobile 11.2.8.8 msm' https://xdaforums.com/t/tmobile-11-2-8-8-msm.4504361/
[Xiaomi Mi 11] __halvar__:
Hi i have Flash global rom with Mi Flash and now Google Pay says my phone is rooted why?

How do i get back to 100 % stock dont want root
[Xiaomi Mi 11] NOSS8:
Maybe because the bootloader is unlocked but if you have a Chinese device and use a global rom you will must root your device.
[Xiaomi Mi 11] __halvar__:
Its a global phone :) can o lock the bootloader with fastboot command ?
[Xiaomi Mi 11] V0latyle:
Only if you're on factory firmware. If you attempt to lock the bootloader on modified firmware (or other than stock) you risk bricking your device.
[Xiaomi Mi 11] NOSS8:
Use Miflash again and select "clean all and lock".
[Xiaomi Mi 11] __halvar__:
Do i need to Flash the firmware agian with clean all and lock?? I didnt thick the lock i was worried to brick it :) but its global with global rom .. cant i lock it with fastboot method?
[Xiaomi Mi 11] __halvar__:
Its a global version on a global phone ? So i can lock it with fastboot ?
[Xiaomi Mi 11] NOSS8:
Miflash works in Fastboot mode.

Or run the "flash all lock" bat file in the rom folder in fastboot mode.
[Xiaomi Mi 11] __halvar__:
Thanks :) i use miflash and flash with flash all lock now its locked
[Xiaomi Redmi Note 7 Questions & Answers] saonaylinn:
Hello Everyone,

I would like to install fastboot ROM on Redmi Note 7 and my PC cannot recognized it on fastboot mode. I almost tried everything like intall 5sec fastboot driver and latest fastbott drivers but it didn't work. I sincerely ask you guys how can I solve it.

Thank you so much
[Xiaomi Redmi Note 7 Questions & Answers] NOSS8:
Install Miflash +drivers.

https://xdaforums.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/

and/or

https://avalonsciences.com/wp-conte...Signature-Verification-on-Windows-8-or-10.pdf
[Xiaomi Redmi Note 7 Questions & Answers] Pig Vomit:
I recently started having trouble sideloading updates through ADB. I was using Win 11, PowerShell and had Bitdefender installed as anti-virus. However, I had no problem on a Win 10 machines using the same programs.

To fix it on my primary Win 11 machine, I disconnected from internet after my download of the OTA, killed BitDefender, and used a Command window instead of PowerShell. That worked for me.

Granted fastboot is different than ADB, but it could be the same problem. Also make sure your Platform Tools is up to date.
[Moto G40 / G60] rowhen_:
Wanted to find out if there was a way to revert to the stock rom without hassle.
[Moto G40 / G60] arsradu:
Yeah, you can use LMSA for that.
[Moto G40 / G60] rowhen_:
will it lock my bootloader though? Also did you face any issues while using that
[Moto G40 / G60] arsradu:
No. And no. :)

Just make sure your power is stable, so it doesn't interrupt the flashing process.

Also, if you're doing that, I'm curious whether or not your OEM Unlocking option is still ON after flashing stock ROM. It should be ON. If it's not, don't attempt to lock back the bootloader or you may end up in a brick.
[Moto G40 / G60] rowhen_:
yeah, it's turned on by default
[Moto G40 / G60] arsradu:
Is it still on after flashing back stock ROM?

Cause, in my case, it's not. It's greyed out, and turned OFF. And it's driving me crazy, cause I don't know why is it still OFF.
[Moto G40 / G60] rowhen_:
i havent flashed the stock rom yet so cant say, would it pose an issue if the OEM unlocking button is greyed out?
[Moto G40 / G60] arsradu:
No, but it would pose an issue if it's OFF and you want to relock the bootloader. Don't even attempt relocking your bootloader if that option is OFF.

That option can be:

1. active (not greyed out) with toggle ON or OFF.

2. inactive (greyed out) with toggle ON or OFF.

What's important is the position of that toggle. Because, what that says is that the bootloader is still unlockable.

YES, it is unlocked right now. And you might even get a message telling you that, but if the toggle is OFF, that means the bootloader is no longer unlockable (or get_unlock_ability=0).

Why is this bad? Well, because if you want to relock the bootloader, and something goes wrong, and you end up in an unbootable situation (with an error like "no valid operating system could be found"), you won't be able to unlock the bootloader again to fix your issue, or at least flash another ROM or something so you can boot back into the OS.

Fastboot will complain that the OEM Unlocking option is OFF, and will not allow you to flash anything. And obviously, you won't be able to boot back into the OS to turn it on.

So, be very careful about that option!

If you don't plan on relocking the bootloader, no worries. But if you do, be very, very careful what does that option say.

You can read more about it here.
[Moto G40 / G60] rowhen_:
That makes sense. Yeah I dont mind the unlocked bootloader, no plans on relocking it.

Also The LMSA doesnt seem to detect my phone, is there like a guide I that I can follow to flash the stock ROM? (I'm currently on PE 12 )
[Moto G40 / G60] arsradu:
You don't really need a guide. But yeah, LMSA won't detect the phone anymore because of the custom ROM.

You need the Rescue option and you need to enter your IMEI for the device to be detected. Everything else is self explanatory. The device needs to be in fastboot mode for this procedure. And make sure the cable is ok. I would recommend using the original cable.
[Moto G40 / G60] rowhen_:
I flashed the stock rom and yes, the bootloader option is greyed out but unlocked. But tbh the rom's pretty trash lol. This was the reason I started considering custom rom's in the first place.
[Moto G40 / G60] arsradu:
So the OEM Unlocking option is ON in your case? Could you please help me with a screenshot, for reference? I'm trying to understand why mine is OFF.

Also, which custom ROM did you have before going back to stock ROM?
[Moto G40 / G60] rowhen_:
No Its turned off but greyed out. And the subtext below it says "bootloader already unlocked". Sorry cant share screenshots because I've already switched to lineage os 20. The stock rom was almost unusable
[Moto G40 / G60] arsradu:
Ah ok. But why do you say it was almost unusable? I didn’t have any issues with it? Also, in the meantime, I’ve relocked my bootloader, and thank Goodness, everything went fine.

What do you like in LineageOS? Personally I don’t like it.
[Moto G40 / G60] rowhen_:
It was stuttering like crazy, the battery life was surprisingly trash. I prefer Pixel Experience 13 over Lineage OS but I was facing some minor issues with it so stuck with Lineage
[Moto G40 / G60] arsradu:
That's weird... I've got no stuttering, battery is pretty damn good, so is signal, and I've got IMS services, which are pretty important to me. Also, Tap to Pay now works again, after locking the bootloader.

Well, I'm glad Lineage works for your! I also prefer PE. But...there are some issue right now. And I'm waiting for a new update which could potentially fix them.
[Google Pixel 6 Pro] TimDotThomas:
I live in the DMV area so I get calls from multiple area codes. It seems like most calls I get from any area code other than my own goes straight to voicemail. I have co-workers who I've even added to my contacts who still can't get through. I have scoured over the settings and can not find a solution. Has anyone else had this issue and/or found a solution?
[Google Pixel 6 Pro] pedro6669:
Do you have those contacts saved? I've had people call me (I'm on T-mobile) and the phone app thought it was spam and I never got a notification or anything. Look in the phone settings > Spam and Call settings > Call screen.
[Google Pixel 6 Pro] 96carboard:
Check with your service provider, this sounds like its on their end, not the phone.
[Introductions] bryobryo448:
Hello my name is Brian.

I like a lot of Android stuff, a lot of apps in the app store and even out of the app store can make people really productive and change their life, am not a developer but am admirer for developers and everyone that works in the tech field !

Live long technology, live long science and innovation !

That's all nice to meet you guys <3 .
[Galaxy Tab 3 Q&A, Help & Troubleshooting] Mohib:
Hi everyone, the problem im facing is whenever i try to flash a custom rom on my t217s it gives an error that this rom is for 217s while your tab is (empty log). Now i have tried flashing official ROM and than again flashing TWRP and CWM still same error. I have tried TWRP 2.6, 2.7, 3.1.1.

I would have used the official ROM but the play store keeps crashing.

TIA
[Oukitel (All phone models)] SwedishForenger:
WP17 is a rugged phone with Infrared Night Vision Camera, Helio G95 8GB+128GB 6.78“FHD+ 90Hz 64MP Triple Camera+16MP Selfie 8300mAh Android 11 Global Version.

View attachment 5731957

Bought me a Oukitel WP17, but couldn't find much information about this phone.

So I'm going to post info here for everyone to see and participate in how to flash, root and update the phone.
[Oukitel (All phone models)] SwedishForenger:
Update:

Using the MTK-bypass Small utility to disable bootrom protection(sla and daa).

According to this Exploit, this MT6785 Oukitel WP17 is fully unlocked, and should be flashable:

Windows10:

[2022-10-13 02:45:23.376773] Found device = 0e8d:0003

[2022-10-13 02:45:23.766358] Device hw code: 0x813

[2022-10-13 02:45:23.776413] Device hw sub code: 0x8a00

[2022-10-13 02:45:23.786386] Device hw version: 0xca00

[2022-10-13 02:45:23.796588] Device sw version: 0x0

[2022-10-13 02:45:23.806536] Device secure boot: False

[2022-10-13 02:45:23.816739] Device serial link authorization: False

[2022-10-13 02:45:23.816739] Device download agent authorization: False

[2022-10-13 02:45:23.836660] Disabling watchdog timer

[2022-10-13 02:45:23.846734] Insecure device, sending payload using send_da

[2022-10-13 02:45:23.896695] Found send_dword, dumping bootrom to bootrom_813.bin

Linux:

[2022-10-13 09:15:03.350097] Found port = /dev/ttyACM0

[2022-10-13 09:15:03.423994] Device hw code: 0x813

[2022-10-13 09:15:03.425119] Device hw sub code: 0x8a00

[2022-10-13 09:15:03.425523] Device hw version: 0xca00

[2022-10-13 09:15:03.425902] Device sw version: 0x0

[2022-10-13 09:15:03.426248] Device secure boot: False

[2022-10-13 09:15:03.426595] Device serial link authorization: False

[2022-10-13 09:15:03.426923] Device download agent authorization: False

However, flashing this phone in any Sp flash tool, is ending up in:

ERROR : STATUS_SEC_PUBK_AUTH_MISMATCH_N (0xC002001B)

View attachment 5733457
​

The PUBK_AUTH part of this error message, is the Authorization for flashing Signed/verified image files. In the Oukitel WP17 firmware folder, downloaded from Oukitel Downlod Center, are their only certain files marked as verified.img, and now after testing in Sp flash tool, loading ALL non-verified files, you can flash these files to the phone without problems.

.