yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] a-dead-trousers:
Or you could do WITHOUT flashing my recovery (Atom XL) at all.

1. Install LATEST Magisk 22.0 apk.

2. Download the Official ROM from Unihertz and extract "boot.img".

3. Transfer "boot.img" onto your SD card (or whatever).

4. Use Magisk on your phone to install it into your "boot.img".

5. Transfer the modified "boot.img" (different name!) back onto your computer.

5. Boot your phone into bootloader and use "fastboot flash boot boot.img" to flash the magisk mdified "boot.img".

6. Profit!

EDIT2: EDIT: No need for vbmeta & co. Obviously the steps for vbmeta to disable AVB are needed nonetheless.

(see my post further down)
[Miscellaneous Android Development] a-dead-trousers:
See my PM.
[Miscellaneous Android Development] covexx:
There are few more steps to do

0. switch on developer mode, switch on oem unlocking, adb reboot bootloader, fastboot flashing unlock - othewise it is not possible to flash anything.

In the step 5. I would recommend to test the modified boot.img with just fasbtoot boot boot.img (this boots it one time) - I did that but I overlooked that the device rebooted after that back to original bootloader and I thought it is OK, but it was not.

After flashing the boot.img from magisk I ended up in an infinite bootloader loop - it start the bootloader up to message the device is not trusted (unlocked), it will boot in 5s but it then reboots.

I had to take the device apart (two layers of terrible design to get to battery contact) to disconnect the battery, but still no go - holding the Pwr and VolDwn button does not react. I thought I'll try the SP flash tool for MTK, but my only Windows 7 are not in the best shape, not sure the provided drivers from Uniherzt really do work.

So now obvious question - what to try next to resurect the phone?
[Miscellaneous Android Development] covexx:
I managed to bring it back to life with the SPMultiportFlashDownloadProject.exe provided by Unihertz (under Windows).
[Miscellaneous Android Development] covexx:
Tried to repeat the boot.img patching with magisk after I reflashed AtomL with the provided EU image, it boots with just fastboot boot boot.img but no root, if flashed the phone is in bootloop again. There are two differences 1. I use the AtomL EU image 2020110320_g63v71c2k_dfl_eea.zip, and 2. I use the latest Magist 23.

Sadly this simple method is not working for this configuration.
[Miscellaneous Android Development] a-dead-trousers:
That's odd...

Thanks.

I didn't mention that because you also need to do that when you are using TWRP (beforehand).

Whoa... Glad I didn't had to go through this for all the times I nearly bricked my device. I was always able to use spflash to get out of the bootloop by simply flashing a corrected partition img (boot or recovery) or in some totally ****ed up situations the whole stock rom.

@ Everyone

I really recommend to try at least one stock rom flash with spflash before getting anything done custom rom wise. That way you can be sure that you are always able to revert what you did without the need to disassemble the phone.
[Miscellaneous Android Development] a-dead-trousers:
I think I know the reason now:

AVB is active by default. So maybe that's why you cannot boot into system.

If you are still willing to test this you could try to

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

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

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

If that helps your problem is definitly AVB related. AFAIK magisk should have an option to handle this but I'm not sure how well it has been tested with the latest big overhaul (v20 > v21). Maybe you can ask in the magisk support threads if there is a better solution than to disable AVB completly to get arround this.
[Miscellaneous Android Development] covexx:
After all, it was not necessary, I was hoping that after battery disconnection, I can enter the recovery via power and volume button, but it did not work. After I made a Windows MTK driver working, I was able to get from the boot loop just via SPflash tool. So yes I agree - before any manipulation with boot.img everybody should make sure that SPflash is working for them.
[Miscellaneous Android Development] covexx:
RIght, so after this tripplet, the boot with magisk modified boot.img works and root is working. Great.
[Miscellaneous Android Development] covexx:
To sum it up:

0a. Reflash phone with the original Uniherzt image from their google disk https://drive.google.com/drive/folders/0By1nhWOmuw2KdDhTUlFOZHpXQjg

using their SPflash tool (works under Windows (on Linux you may try Wine), the MTK driver needs to be properly installed and phone detected in device manager - everyting is on Unihertz gdrive)

- 2020110320_g63v71c2k_dfl_eea.zip at that time for EU AtomL

The SPflash tool is not very intuitive, generally it is enought to pres Scan and wait until it detects the phone (phone reboot needed), then press "Start all".

This way you'll make sure you can get phone from any bricked state, also the phone software will be at known version and clean.

0b. On the phone switch on developer mode, switch on oem unlocking, adb reboot bootloader, fastboot flashing unlock - othewise it is not possible to flash anything. (now the message the phone is not trusted starts to appear).

1. Install LATEST Magisk 23.0 apk on the phone (https://github.com/topjohnwu/Magisk)

2. Extract "boot.img" from Unihertz image

3. Transfer "boot.img" onto your SD card (or whatever - adb push, mtp).

4. Use Magisk on your phone to install it into your "boot.img" (see magisk github doc)

5. Transfer the modified "boot.img" (different name! magisk_patched*.img) back onto your computer.

6. Boot your phone into bootloader - adb reboot bootloader

7. Disable vmbeta verification:

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

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

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

8. "fastboot flash boot boot.img" to flash the magisk modified "boot.img".

fastboot reboot

9. Open Magisk, you should see it is installed (not only in ramdisk) and there is a menu for superuser capabilities.

10. adb shell; su -; allow
[Miscellaneous Android Development] a-dead-trousers:
I made an updated how-to for spflash (with latest version & drivers)

android_device_Unihertz_Atom_LXL/docs/HOW-TO-FLASH-STOCK.md at master · ADeadTrousers/android_device_Unihertz_Atom_LXL

Common device tree for the Unihertz Atom L and XL - ADeadTrousers/android_device_Unihertz_Atom_LXL

github.com
[Miscellaneous Android Development] covexx:
Today Unihertz anounced a new OTA update for Atom L|XL. OTA (of course) fails on rooted device. There is no archive available yet on their google disk. It seems Atom (X)L does not have a A/B partitioning, so we can not get the OTA to work... am I right?
[Miscellaneous Android Development] a-dead-trousers:
At least not rooted ;)

You'd need to do spflash of previous ROM release to revert the root. Setup the phone once more and then run the ota update. There should be a way to extract boot.img from an unrooted device. Just search the net for it. Otherwise you'd need to wait for the google drive release to get root back again.
[Miscellaneous Android Development] it_unihertz_when_i_pee:
@a-dead-trousers

I didn't mean to ghost you. I found myself in the position of having some major life changes and wasn't really in a spot where I could afford to experiment with my phone and possibly be without it for some days. Now that the dust has settled, I'm coming back around to this project. Primarily because...

The LineageOS ROM from the OP doesn't allow me to get LTE service from my new provider (the stock ROM *does*, so I know the phone is capable). So I wanted to try a newer version...

I tried following the build guides you posted/PMed to me, with no success. My Linux skills are good but I have no experience with resolving ninja errors and the like. I might try to set up a dedicated Ubuntu VM for a build env, so I can do more copy-pasting and less thinking, but I'll need to chase down a terabyte-sized hard drive for the process.

In the mean time I thought to myself a rooted stock rom is probably good enough for now. I'd have LTE service and I can use root to force all of the Google-ware off the phone. However...

@GameHunter1

If I follow your steps with the 2020-11 stock image from Unihertz, it works. However, I can't apply the OTA update when rooted (as others have stated), and if I apply the OTA update before trying to root, the phone never boots into recovery to do the sideload. So there's a disconnect somewhere in that process, but that's as far as I've gotten.
[Miscellaneous Android Development] a-dead-trousers:
Do you use me recovery for the sideload?

If yes the problem is that I've set up decryption support and that's probably not gonna work with the 2021-05 update as I integrated the 2020-11 vendor binaries.
[Miscellaneous Android Development] it_unihertz_when_i_pee:
Yes.

I got a working Lineage installed with your instructions here:

https://xdaforums.com/t/rom-10-0-un...hertz-atom-l-and-xl-alpha-2021-05-10.4171407/

Drunk-me wasn't bright enough to find that thread last night, but I was able to get it running this morning.

I did encounter a new problem though that is not only unique but fairly interesting. I'll post about it there, since I'm using that ROM.
[Miscellaneous Android Development] covexx:
I am still using this "May" image on Atom L. just found out that if secondary user sets up the Alarm (Clock) then the alarm starts only if set a few minutes in the future. After that the alarm just does not start (the clock app is probably put asleep). As an Owner the alarm works as expected. I set the clock app for both users as not battery optimized, behaves the same. Is there any known workaround, know android "feature", or maybe a fix in newer builds (https://xdaforums.com/t/rom-10-0-un...om-l-and-xl-alpha-2021-11-14.4171407/page-9)? Thanks
[Miscellaneous Android Development] a-dead-trousers:
With "May" image you mean stock ROM or (my) LOS ROM?

(The LOS ROM by PeterCxy never had a May release)
[Miscellaneous Android Development] covexx:
Sorry for missunderstanding, I am already lost in all my experimets. ATM I am using a stock image, just rooted.
[Miscellaneous Android Development] a-dead-trousers:
In that case you should contact Unihertz' technical support.

(Don't mention that you are root though ;) )

Or wait (shouldn't be very long now) until they release their A11 upgrade. Maybe it's fixed there.

Slightly off-topic:

I also had a minor issue with stock that I belive has the same root cause although it wasn't directly connected with multi user. Using Signal I wasn't able to receive any push notifications for new messages unless I opened the app. 9 out of 10 times I was then bombarded with push notifications until I got one for every new message recevied.

My conclusion was that stock somehow suspends all background jobs for apps not actively running because on LOS I never had this problem.

If this is so similar to your problem, why is this not happening with the clock app as "owner" you ask?

Because the clock app is a system app and maybe has more privileges.
[Miscellaneous Android Development] SepticFuddy:
Were you using Signal as your default SMS app while in stock? I didn't have that issue in stock, but I've long used Signal as my default SMS app going back several phones now both to avoid those kinds of system wonkery issues and just for convenience's sake. It treats it more like a core system app when you do.

Also thanks for keeping up with updates... one of these days I'll find the courage to get up to date on security patches when I know I've got time for possible damage control lol
[Miscellaneous Android Development] ratnikrus:
Hello. Tell me-I don't understand how to do it:

3. Run `fastboot flash --disable-verification --disable-verity vbmeta vbmeta.img`

4. Run `fastboot flash --disable-verification --disable-verity vbmeta_system vbmeta_system.img`

5. Run `fastboot flash --disable-verification --disable-verity vbmeta_vendor vbmeta_vendor.img`

6. Run `fastboot flash recovery lineage_recovery_XXX.img`

7. Run `fastboot reboot recovery` to reboot into the newly-installed LineageOS Recovery
[Miscellaneous Android Development] covexx:
Seriously - if you do not understand then do not try do it. Otherwise first backup with SP flash tool for mediatek at least.

Then learn what ADB for android is. Those are commands for adb/bootloader.
[Magisk] ChaosEmpire:
i found a working magisk version, but its just 16.7 so it does not help anymore to pass SafetyNet checks

Any version above fails to install , only 16.7 shows message about high compression mode

any magisk manger below 6.10 crashed, and the new one is not able to work with version below 18

so fo rnow i m stucked at 16.7 with manager 6.10

but this wont help me in any way

i saw lineage build for my old tablet, which is working with newer magisk 20, but then i get an android version not compatible with those old apps i have to keep (else my kids kill me)
[Magisk] Didgeridoohan:
I would first try the Canary release, since it might have improvements the are relevant to your case.
[Magisk] ChaosEmpire:
Tried Canary, did not changed anything
[Magisk] Didgeridoohan:
What about the installation log from the Canary? It might give more info...
[Xiaomi Redmi Note 7 Questions & Answers] francanna:
Hi all, I had official MIUI Global 11 on Android 10 on a phone with unlocked bootloader and a recovery. I wanted to re-lock the bootloader, so I went to fastboot and I gave the command to lock it.

Obviously (but I didn't even imagine it) the devide DID lock, but now it doesn't start any longer. ""System destroyed" is the message.

What I want to get is one of these two results: having a working phone OR having everything erased.

What I have already tried is:

- installing a firmware via fastboot: failed because the bootloader is locked

- flashing single .img via fastboot: failed because the bootloader is locked

- erase partitions: failed because the bootloader is locked

- unlock again the phone via fastboot: failed

- unlock again the phone via Mi Unlock: failed because missing authorization in developer options

Let's add the fact that I don't have windows, but Mac, that reduces the available options.

ANY SUGGESTIONS?
[Xiaomi Redmi Note 7 Questions & Answers] Kanak Mahmuf:
You can use Platform tools in windows.As far as i know platform tools can be used both locked and unlocked bootloader.You can search on YouTube how to flash mi phones through platform tools.
[Xiaomi Redmi Note 7 Questions & Answers] Z750z:
I think that the only way to flash it successfully again is to use QPST ,but you need to open the phone remove battery and get 9008 port , check in YouTube.
[Realme X50 5G Questions & Answers] floridaman:
I need the dual sim and need to make sure Volte at least is working, particularly on T Mobile USA and EE UK
[Realme X50 5G Questions & Answers] comp101inc:
Not working it has it just haven't been able to provision it
[Realme X50 5G Questions & Answers] floridaman:
So after several emails with Realme I was finally able to talk to someone, they did call me as well.

This person gave me a song and dance lie that Volte in fact wasn't shut off and also said in his response there is no way to see a toggle switch either. Which we both know to be an absolute lie.

I told him people are complaining across forums from various countries, it clearly fell on deaf ears as the company line of it is on was repeated. Then I was told also it doesn't work on T Mobile because they're not in the North American market and didn't install T Mobile firmware. Well, you don't need to and it doesn't matter where in the world goes as long as the carrier has Volte and the device has it, it works.

It's clear they know it's shut off on purpose and just tell lies with no intention of turning it on. The only way anyone who buys one of their devices is going to get it is to root the device and go in and turn it on yourself.

Not sure how I see this company growing if this is going to be their attitude and behavior.
[Realme X50 5G Questions & Answers] comp101inc:
Thanks for the update ROOT here I come
[Realme X50 5G Questions & Answers] Jvlc:
It would be so cool if you suceeded at rooting the X50 and shared your progress!
[Realme X50 5G Questions & Answers] floridaman:
Let us know how that works out

Have you complained to realme? I ended up sending an email to their President of India and Europe. That's how I got someone to actually give me a response then call.

I also have a Umidigi A7 Pro, it's a $100 device and yet VoLTE and Wifi Calling works no problem.... Yet Realme can't seem to get its act together.
[Realme X50 5G Questions & Answers] comp101inc:
I also have a umidigi power3 and volte and vowifi works there. So realme needs to get there act together.
[Realme X50 5G Questions & Answers] floridaman:
I'm wondering is root is absolutely needed and if like their sister company Oneplus who hid the function switch in the 8 models, if using the QPST tool would get you to the menu to change the VoLTE profile and get it working on their devices.

From what I am seeing the two companies both are now hiding the menu's, so that tells me they're both following the same game plan. There's several posts and a video showing using QPST to change the profile and get VoLTE working.

Do you think this would work?
[Realme X50 5G Questions & Answers] jergud:
Hi all

Did you find a way to activate VOLTE ? I have a x50 pro 5g, settings made for 4g brands, volte OK with my provider but not on the phone.

Thank you
[Shadow General] tissle:
Any of you guys use it?

I found couple of good scripts that I might use, but havent installed MortScript yet.
[Redmi Note 9S / Note 9 Pro (Indian Model) Question] WALLFL0WER:
can redmi note 9s(curtana) roms be used on the poco m2 pro given that they share the same hardware?
[Redmi Note 9S / Note 9 Pro (Indian Model) Question] Apcoolboy:
No. don't do it. Wait for poco m2pro development or you will end up hard bricking your poco.
[Redmi Note 9S / Note 9 Pro (Indian Model) Question] WALLFL0WER:
Alright

Appreciate it
[Redmi Note 9S / Note 9 Pro (Indian Model) Question] gerega:
Only if you want to buy a new one ;) Never flash a ROM for the wrong phone and model!! NEVER!
[Redmi Note 9S / Note 9 Pro (Indian Model) Question] WALLFL0WER:
lol alright

i was just hoping that it would be possible since the internals are supposedly the same:D
[Redmi Note 9S / Note 9 Pro (Indian Model) Question] pecholino:
What about manual ota updating curtana EEA 11.0.4.0 with international 11.0.10.0?

I have two rn9s's. One european and one international. The european one sometimes lags.
[Fire TV Q&A, Help & Troubleshooting] veeroohre:
I tried an software update to the newst prerooted image from rbox but unfortunatelly installed Magisk V20 directly after it (without reboot).

After reboot my Fire TV 1 stopps now at the first white Amazon logo.

Fastboot via USB-A-to-A is working

dḿesg shows the follwing:

[10671.732229] usb 1-2: new high-speed USB device number 44 using xhci_hcd

[10671.887334] usb 1-2: New USB device found, idVendor=1949, idProduct=0401

[10671.887339] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3

[10671.887343] usb 1-2: Product: FireTV

[10671.887346] usb 1-2: Manufacturer: Lab126

[10671.887348] usb 1-2: SerialNumber: xxxxxxxxxxxx

When I try to flash something I get the following message:

target reported max download size of 805306368 bytes

sending 'recovery' (9544 KB)...

OKAY [ 0.303s]

writing 'recovery'...

FAILED (remote: flashing not allowed for locked hw)

finished. total time: 0.314s

This is strange since I unlocked the bootloader years ago.

Is there hope for my Fire TV 1 or did I finally brick it?

Update:

"fastboot getvar unlocked" gives me:

"unlocked: "
[Fire TV Q&A, Help & Troubleshooting] Sus_i:
Magisk won't work on the first fireTV ;)

Flash a clean boot.img (the unlocked one in the prerooted rom zip) with fastboot onto boot partition.
[Fire TV Q&A, Help & Troubleshooting] veeroohre:
Would love to do that, but as mentioned I get the error message "flashing not allowed for locked hw".

I read that sometimes fastboot is the problem and not the hardware. Could that be? I'm on Ubuntu LTS 18.04.
[Fire TV Q&A, Help & Troubleshooting] Sizzlechest:
You need to reflash the boot. Extract the boot_unlocked.img from bueller-5.2.7.3-rooted_r1.zip and flash it from the command line when you have the FireTV connected with the USB A-A cable.

fastboot flash boot boot_unlocked.img

EDIT: Here's my thread about it: https://xdaforums.com/fire-tv/help/warning-attempting-to-flassh-magisk-16-t3778096
[Fire TV Q&A, Help & Troubleshooting] veeroohre:
As I wrote, unfortunately this does not work:

< waiting for any device >

target reported max download size of 805306368 bytes

sending 'boot' (6460 KB)...

OKAY [ 0.206s]

writing 'boot'...

FAILED (remote: flashing not allowed for locked hw)

finished. total time: 0.217s

Any other ideas?

Update:

Under Windows "fastboot devices" is not listing anything.
[Fire TV Q&A, Help & Troubleshooting] Sus_i:
Maybe try 'fastboot boot recovery.img' instead of a flash.

Connect the box via usb a-a cable to linux, boot the box and watch out if any mounted partitions pop up.

If yes, you may be able to follow this Guide.

Take a look here too.
[Fire TV Q&A, Help & Troubleshooting] veeroohre:
Doesn't work:

downloading 'boot.img'...
OKAY [ 0.304s]
booting...
FAILED (remote: Restricted command
)
finished. total time: 0.312s

With "fdisk -l" no partition shows up.

I think my box is dead :crying:
[Fire TV Q&A, Help & Troubleshooting] Sus_i:
It seems so.

Writing a new boot.img to the fireTVs eMMC via hardware mod is probably a solution, but that's a bit overkill ;)
[Fire TV Q&A, Help & Troubleshooting] veeroohre:
You're right. I thought about it, too. But too expensive and time consuming for such an old device. Probably I'll buy a new one. Although I hate to dump hardware which in principle still works . :(
[Xiaomi Mi A2 Lite Questions & Answers] nikkky:
Anyone knows which is the bluetooth power class and bluetooth max transmit power for this phone?
[Xiaomi Mi A2 Lite Questions & Answers] TeoXSD:
All I can tell you it's that it's a wi-fi, bt, fm SOC called WCN3990. I don't have a spec sheet to know more about those and in the kernel build there's no info about actual dB limit.
[MIUI Central] Yanyad:
You say you can sync the Notes app but do not mention the Tasks. How do you sync the tasks as well? I can't find a way to do it.
[Samsung Galaxy S20 / S20+ / S20 Ultra Questions & ] maddie01:
After this update yesterday my unlocked GS 20+ on AT&T now shows 5G ? I wonder if they opened up anything else?? View attachment 5069969View attachment 5069971
[Samsung Galaxy S20 / S20+ / S20 Ultra Questions & ] dutch_in_seattle:
No such luck. You're most likely seeing 5Ge (with a little 'e' at the end), which is just a marketing gimmick for slightly improved 4G LTE. For example, see https://9to5google.com/2020/05/20/att-5ge-android-icon/.

You won't have real 5G unless you have a get a real (and undoubtedly) expensive 5G phone plan from AT&T.

--Ron
[Samsung Galaxy S20 / S20+ / S20 Ultra Questions & ] maddie01:
Thanks for your reply, I am fully aware if the 5G evolution gimmick but this shows 5G with no “e” as you can see in the pictures and I do pay for the 5G plan with AT&T...So I was very surprised to see it on an unlocked phone ...crazy stuff
[Samsung Galaxy S20 / S20+ / S20 Ultra Questions & ] olkitu:
Your device at least see UpperLayerIndicator from network so that will activate 5G icon. CellMapper App is very good app to show if your phone connected to 5G really or not.

But maybe you just see 5G icon without having 5G-connection. From modem log could check if your device support really AT&T 5G-network: https://mt-tech.fi/en/how-to-get-4g...ons-from-your-android-phone/#Qualcomm_devices