yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] SPHM900:
Hello all!! So I'm having an issue. Following the installation guide, I get up to the point where I have TWRP installed, but when I go to wipe the phone (from recovery) the live log tells me that I do not have root access and it cannot wipe the partitions. Can anyone give me a hint as to what step I may have missed? Thank you in advanced!
[Miscellaneous Android Development] a-dead-trousers:
Just ignore it ;)

If you want to be sure flash an empty img over userdata (for example userdata.img from the stock rom)

EDIT:

You do mean the red error message showing that it cannot access certain partitions?
[Miscellaneous Android Development] SPHM900:
I had screenshots but couldn't pull them lol. TWRP (when I boot into it I slide the bar for read write permissions) I follow the instructions, but when I go to wipe it, it says I don't have access. I've had to re flash my phone a few times. I've had it boot, but I've also had bootloops and green lines lol. I am going to try again tonight. Saw the Troubleshooting guide at the bottom, but it doesn't help.

will try what you said, can i use ADB sideload from TWRP or should i flash it from the bootloader menu after i flash recovery
[Miscellaneous Android Development] a-dead-trousers:
If it is "system_root" or "system" that's a know problem and can be ignored.

What kind of "bootloop"?

Direct reboot without Lineage Logo = Possibly wrong kernel. Did you use my latest release?

Reboot during Lineage Logo = Possibly some remains on data which crash LOS boot. If wipe doesn't help do a flash of userdata.

Green Line indicates an incompatiblity between bootloader and kernel. Did you use the latest release and is it the same variant as your stock rom?

That's mainly for "error 7" during install. Maybe I need to extend it for all the problems you and others mentioned *lol*.

From within TWRP you need to use "Install > Image". No sideload possible.

If it isn't going to work at all with TWRP you can completly rely on fastboot. You need to create a super.img following this guide though:

https://github.com/ADeadTrousers/an...om_LXL/blob/master/docs/HOW-TO-FLASH-SUPER.md

After that flash "boot.img" and "super.img" like you did with "vbmeta.img" and "recovery.img"
[Miscellaneous Android Development] a-dead-trousers:
Good news everyone!

Unihertz finally decided to "release" their Android 11 roms (flagged "R1" so maybe it's a "release candidate") on google drive. So I should be able to fully test my builds with Lineage OS 18.1 now.

Stay tuned for more information.

For the meantime I did a (belated, due to vacation) release for 17.1.
[Miscellaneous Android Development] clewis.it:
Ooh, that's exciting!

I would love to know what has changed in the Intercom app. Unfortunately, it seems they made some major changes and now it won't initialize on my phone. Apparently, the helper program that it used (extmodule) is no longer used, but I can't tell what has replaced it. Any ideas?

Otherwise, I would appreciate an overview of the Intercom features on the Android 11 version.
[Miscellaneous Android Development] SepticFuddy:
So recently, calling stopped working on my new carrier, but texts still work fine. Apparently, they've just been pushed into stricter requirements by AT&T (their host), including a pre-approved list of devices and Android 12 (!). But... calling was working fine when I tried 8 days ago. As part of troubleshooting to see if we could make mine work anyway, they asked me to conform my APN settings. They're quite different from what they used to be and what the apns-conf.xml has on the current version on line 5961 (from /product/etc/, assuming that's the one that matters). But I'm having the same problems with trying to change it. Options grayed out, "Save" and "Discard" doing nothing whether trying to edit an existing APN or create a new one. Reinserting the SIM and rebooting doesn't pick up the new settings either.

Here is what their instructions were:

From which I came up with:

<apn apn="ERESELLER" carrier="FreedomPop" mcc="310" mmsc="http://mmsc.mobile.att.net" mmsport="80" mmsproxy="proxy.mobile.att.net" mnc="410" protocol="IPV4" type="default,mms,supl" />

based on the syntax found in the file to replace the existing line:

<apn apn="fp.com.attz" carrier="FreedomPop" mcc="310" mnc="170" type="" />

I tried hot-swapping a corrected version of the file but that was too much to hope for. Presumably, this is a much simpler case than it_unihertz_when_i_pee and can actually be fixed on your side ADT? Any chance of getting to that sooner than later? Need to know if I'm screwed on my carrier again or not.

Thanks
[Miscellaneous Android Development] a-dead-trousers:
Is A12/LOS 18.1 a requirement for this to work too? Cause that would take some time to finish.

Otherwise you are lucky cause I still haven't switched one of my two build enviornments to LOS 18.1.

BUT I don't think I can managed to do a modified build today and the next time I'm at my flat is on sunday. So If that's suitable for you I can provide it by then at the latest.

If that's too late you may try to build your own modified version using my guide. I recommend using linux for that although It should theoretically work under windows too. You simply need to modify this file https://github.com/ADeadTrousers/android_device_Unihertz_Atom_LXL/blob/master/etc/apns-conf.xml in order to include your settings.
[Miscellaneous Android Development] SepticFuddy:
I won't have the chance to get that done before you could anyway, and my most critical contacts I can still reach in the mean time, so that's not too much of a wait. As for LOS 18.1, isn't that still just A11, not A12? My instinct is that this is just an institution (or two) making arbitrary requirements to simplify the issue for themselves, not that there's actually any technical reason A12 is required. But I have nothing to justify that speculation, at least until I can try a correctly configured APN and see if that fixes the issue or not. Anyway, thanks in advance for the help
[Miscellaneous Android Development] a-dead-trousers:
You are right. LOS 18.1 is of course A11.

I see what I can do. My appointments just slightly changed so maybe I can squeeze in a build + upload. ;)

In the meantime can you please run

getprop gsm.sim.operator.numeric

and

getprop gsm.operator.numeric

to check if the settings recognized by you device apply to those provided by your operator?
[Miscellaneous Android Development] a-dead-trousers:
@SepticFuddy

Here it is https://github.com/ADeadTrousers/an...01-UNOFFICIAL-Atom_XL_TEE-signed-test_apn.zip
[Miscellaneous Android Development] SepticFuddy:
gsm.sim.operator.numeric is 310170

gsm.operator.numeric is 310410

Which seems to confirm the old settings

So I patched it, and the FreedomPop entry in the APN list is still the same fp.com.attz as before (with an extra other entry or two than before for whatever reason). I checked the XML file just to be sure and it does have the corrected line. I don't know much about this stuff, but my guess is it's pulling that from the SIM itself, and can only be fixed by a reboot update? And maybe I'm having the same problem as with T-Mobile, where I can't get those updates on my home tower in the woods? If that's case, I'll have to try to remember to pop the SIM and reboot while I'm in town.

If you have any other ideas, let me know. Thanks for jumping on it so quickly!

EDIT: By the way, seems like you added Magisk in at some point? I queued it in with the zip and it appeared to install twice, first as an "addon". I also didn't have to reinstall it when I updated OTA yesterday. It does make things more convenient, and also makes it easier to avoid going past v23.
[Miscellaneous Android Development] a-dead-trousers:
Maybe changing mnc=410 to mnc=170 will do the trick then.

But I'm sorry I can't do another update right now.

On sunday, when I'm back. promise.

I don't include it my public builds. I only use it my private builds alongside opengapps.

As long as the recovery is able to encrypt the data partition (which it should for quite some time now) the "addon" installation will queue in right after the update.
[Miscellaneous Android Development] SepticFuddy:
It still thinks it is 170 when it's supposed to have changed to 410. It's just still using the data from the original APN entry rather than the new one, and I don't know where else it's getting that from. So we still don't know what it would do with the new settings yet. Wifi calling still works thankfully since they're VOIP only, just have to deal with some dropout issues from my ISP for the next 2-3 weeks.

Interesting, I had no idea about the addon feature
[Miscellaneous Android Development] a-dead-trousers:
It's getting theese infos from the sim card. apns-conf.xml is then used to determine the additional settings. But there is also a signed app that interacts with the sim card in a certain way which produces alternative values and that's what prevents it_unihertz_when_i_pee's phone from working correctly. Sadly I don't know how to fix this cause I don't know an operator with this kind of "registration" in my area to be able to run some tests and figuring this **** out.
[Miscellaneous Android Development] SepticFuddy:
Seems like my best bet then is to try rebooting next time I'm in town, and if that doesn't work maybe ask them for a new SIM. Not sure if they'll have any because the VOIP-only service is sort of a legacy product, but also possibly the only reason it works where I live. I'll update if I learn anything else
[Miscellaneous Android Development] a-dead-trousers:
@SepticFuddy

Here is a new try with BOTH settings https://github.com/ADeadTrousers/an...03-UNOFFICIAL-Atom_XL_TEE-signed-apn_test.zip
[Miscellaneous Android Development] SepticFuddy:
Same result. Rebooting in town didn't work either. I guess I should note I have not been wiping anything during installation to avoid the pain of the restore process. I figured a changed system file should do the trick on its own, but is it possible I need to be wiping something to make this work?
[Miscellaneous Android Development] a-dead-trousers:
Nope, normally no wipe is needed.

So, you're saying that there is no ERESELLER entry in the APN List?
[Miscellaneous Android Development] SepticFuddy:
Nope. This is what I've got. Pretty sure one or two of those weren't there before the first custom build but I don't remember which.
[Miscellaneous Android Development] a-dead-trousers:
@SepticFuddy

Another day, another test build

https://github.com/ADeadTrousers/an...04-UNOFFICIAL-Atom_XL_TEE-signed-apn_test.zip

In this one I fixed the ordering of my "stock apn overwrite" feature. Apparently it was overwriting my overwrites with stock entries and not the other way round :poop:

This should also slightly reduce the amount of entries.
[Miscellaneous Android Development] SepticFuddy:
Progress! All the settings have updated to the ERESELLER entry, except the MNC is still 170 instead of 410, so now I can't connect to LTE. I think fixing that should solve the problem
[Miscellaneous Android Development] a-dead-trousers:
And that's what I don't know how to do. See problem of it_unihertz_when_i_pee. The 170 is from the sim/carrier and can't be changed (or at least shouldn't be needed to be changed)
[Miscellaneous Android Development] SepticFuddy:
Hm. Guess I'm back to trying to get another SIM from them or maybe find another VOIP-only carrier. Thanks for the help
[Miscellaneous Android Development] talmid01:
I following the guide, but I'm not able to flash the recovery. I tried different versions of it from other threads. Every time I try to get into the recovery I get a chinese menu, not the TWRP one. I know that going to Android will overwrite the recovery, but doesn't matter how I try it doesn't get into the TWRP. The command "fastboot boot recovery.img" fails.

I was also doing research if there is a Treble Vanilla version, that is easy to flash from fastboot, but doesn't look like there is one developed.

Any ideas how to continue on installing Lineage on this?
[Miscellaneous Android Development] SepticFuddy:
Sounds to me like you are holding volume down instead of volume up. I did the same thing at one point without realizing, bringing me to the Chinese menu instead of TWRP
[Miscellaneous Android Development] a-dead-trousers:
@talmid01

I just answered your mail ;)

Like SepticFuddy wrote you need to press Vol+ and not Vol-.
[Miscellaneous Android Development] dr-dude:
Sorry to be 'that guy', but any assistance? I'm DESPERATELY trying to get lineage running on my Atom L and have run into yet another wall.

Anybody know why TWRP keeps "failing to mount 'system_root' (permission denied)" and ends updater process ERROR: 7?

Unihertz stock rom dated: 202105

unlocked boot loader

magisk and rooted image (magisk says root is good)

I can recover into TWRP 3.5.2_10-0

Trying either as ADB sideload or install from SD card gives the ERROR 7 message (see attached screen shot)

I've even gone so far as to use a text editor to remove the first few lines of text in the 'updater script', but that doesn't seem to make a difference

Again, sorry to be an idiot. I'm sure it's something super easy that I'm screwing up

BTW HUGE THANKS to @ADeadTrousers for boss level work on this project

THANKS!!
[Miscellaneous Android Development] a-dead-trousers:
The "system_root" error can be ignored. Some parts need it but others complain about it, I don't know why.

The "Error 7" (updating_dynamic_partition) and what to do is described in the install guide under "Troubleshooting".
[Miscellaneous Android Development] dr-dude:
HA! This is a great reminder about the quote, 'when all else fails - read the instructions'

I'm on it. Thanks again!!!!
[Miscellaneous Android Development] dr-dude:
I'm now sooooo excited to be up and running on lineage with my Atom L. Thanks!

By chance, has anyone got Google Fi running? I'd previously read that it also needs 'carrier services' and 'google connective services', so i installed them. I've also allowed all service permissions for both apps and google fi.

When i try to credential phone with a fi SIM, i get error B042. Anybody else run into this? Any recommendations?

Thanks again!
[Miscellaneous Android Development] dr-dude:
Yet another noob question. Sorry. I'm successfully up and running 17.1-20220421 But ...

Having difficulty getting my virtual network operator SIM to function. I can't seem to find the configuration section of the settings. Any help? Where I usually look (network & internet / mobile network / advanced setting) doesn't have the usual spot to config the APN. The only option there is "carrier video calling". When i search for "APN" in settings, nuthin comes up.

Help, as always, is very much appreciated.
[Miscellaneous Android Development] a-dead-trousers:
Here is the thing:

On my device and ISP/contract/SIM the setting is there and editable.

Others reported they have the option but it's not editable. For them I tried to provide the settings directly via apn-conf.xml which isn't always working.

And now you, with no options at all. Sorry but I'm at my wits end.

You can send me your mcn/mcc from your phone and the settings provided by your operator and I'l try to integrate it in my next build.

https://xdaforums.com/t/rom-10-0-un...and-xl-alpha-2022-04-21.4171407/post-86671635

But I also don't know when that will be cause I'm kneedeep in 18.1 and that ****er won't boot :mad:

Another option would be to try it with a sim from a friend who has a more "common" phone operator and see if it works then. This way we can at least rule out an error in the ROM/device.
[Miscellaneous Android Development] dr-dude:
You, sir, are a gentleman and a scholar. Thanks for your continued diligence with this project.

1) I'm happy to standby for 18.1 to see if that fixes the issue

2) Looks like the t-mobile connection for google fi is 310/260. Fi won't carrier switch unless the phone is designed for it, so this code should be the only one needed

3) I tried to find the mentioned package to see if that'd fix it, but couldn't find the 'signed-test_apn' package over on github. Am I doing something wrong?

4) great idea to try a traditional carrier SIM to eliminate problems. I'll work that angle as well

Thank you !
[Miscellaneous Android Development] a-dead-trousers:
Thanks. :giggle:

I just checked the apn-files I use/combine and there are plenty 310/260 settings so I'm guessing there is something else at miss here. Maybe that elusive "signed ims apk" as mentioned in the developer docs. But as I'm no expert on this matter I don't really know where and how to look for a solution. sorry.

It got already integrated into my "regular" builds. So no test_apn package anymore.
[Miscellaneous Android Development] dr-dude:
Soooo. ... anybody able to help provide some guidance on IMEI? I'm trying to test my device with t mobile and just looked up my IMEI as part of the enrollment process. As you can see on the pic, it seems 'weird'. SIM slot #1 is all ones while SIM slot #2 is all twos. Never seen anything like that before.

Could that be part of my inability to get credentialled on a mobile network? Is there a way to go back to whatever the number was from the factory?

My ignorance is obvious. Helpful guidance is very much appreciated
[Miscellaneous Android Development] clewis.it:
Were you able to get this fixed? The only information I found was to use a program to rewrite your IMEI, but I think you need to know what those original numbers were.

Download SN Write Tool (all versions) - Mediatek IMEI Tool

Download the latest version of SN Write Tool to flash IMEI on MediaTek Devices. All available versions are v2.1128.00, v2.1436.00, v2.1444.00, v2.1504.00.

androidmtk.com
[Miscellaneous Android Development] clewis.it:
@a-dead-trousers, do you mind if I PM you? I wanted to compare notes on any remaining issues with the DMR radio.
[Miscellaneous Android Development] a-dead-trousers:
You should NEVER FORMAT the device. Otherwise you need to send it back to Unihertz for repairs. That's why I left a note in my "how to use the SPFlash tool" guide.
[Miscellaneous Android Development] a-dead-trousers:
Not at all.
[Miscellaneous Android Development] dr-dude:
Credit where credit is due, I reached out directly to Unihertz and they sent me a private link to a windows based app to rewrite the IMEI. Tho they did not have a record of what my original IMEI was, but fortunately I still had it on the box the phone came in. I'll plan to install the app and attempt IMEI rewrite next week probably.

As our fearless leader wisely mentioned, I should have just followed the instructions and avoided all this headache. Ugh.
[Miscellaneous Android Development] dijama:
So I hate to be that guy coming to the party late but I 'upgraded' the rom to the stock version noted, was able to get into TWRP, but the touch screen doesnt seem to function so I can't proceed. I feel like i missed some obvious step maybe?

Thanks in advance.
[Miscellaneous Android Development] a-dead-trousers:
Which variant (L/XL, TEE/EEA) are you using?
[Miscellaneous Android Development] dijama:
sorry, thats rather important isnt it - L / TEE
[Miscellaneous Android Development] a-dead-trousers:
I'm currently in the process of testing A11/LOS18. Maybe tomorrow I can check the old TWRP on my device. But I wouldn't get my hopes up. Although I heard from multiple sources that they also weren't able to use touch on the recovery I was never able to reproduces this. I use a spare XL for testing and since it's "more" than a L I simply switch between the four rom variants. Maybe that's not 100% correct as there might be differeces in the hardware which are countered by some modifications in the stock rom from unihertz which I cannot reproduce.

For example: I think there are at least two different camera models used for the whole batch of devices. One with FullHD from the start and the other which needs a little bit of coaxing (that I don't know) to behave FullHD.

As far as I know there are only two hardware models: L and XL.

The TEE and EEA variants should only be different in software. (But I could be wrong here)
[Miscellaneous Android Development] a-dead-trousers:
@dijama

As I thought, the touchscreen works just fine on my device. But I just saw in my own release notes that this model uses the kernel of the Atom L EEA because the TEE variant could not be patched cause of a size difference in the compressed kernel img after the modification.

So maybe just wait until I get the A11 versions ready. Their kernels were much easier to modify. No more payload at the end which messes up the addressing. I'm just smoothing out some bugs to come on par with the A10 versions.
[Miscellaneous Android Development] dijama:
That sounds great thank you - I'm upgrading from a lineage'd jelly 2 and was really looking forward to having the same experience here (with security updates woo!). appreciate all your work.
[Miscellaneous Android Development] a-dead-trousers:
After a long time of tampering, testing, failing and starting over from scratch I'm finally confident enough to present you my newest releases. Sadly, I couldn't figure out how to get decryption to work in twrp (it won't boot if enabled) but at least everything else is working just fine.

Please be aware that you NEED to upgrade your stock rom release to 2021-11 (internally it's 2021-07-05).

Simply follow my upgrade guide in the first post.

Although it is possible to switch directly from LOS 17.1 to 18.1 without wiping userdata and therefore not needing a backup

I don't recommend to do that

. If you loose your data don't point your fingers at me.

You've been warned

.
[Miscellaneous Android Development] SepticFuddy:
To clarify, you don't recommend skipping back up, but upgrading without wiping is still worth trying, right?
[Miscellaneous Android Development] a-dead-trousers:
Yes.

In fact I did it without wiping and it worked but I cannot guarantee that this will work for everyone.

Oh, and yes, always do a backup. Unfortunately this is not possible with twrp for now.
[Miscellaneous Android Development] SepticFuddy:
So even using SP Flash tool to put stock A11 on it, I could not get it to work. I had to flash super every time to get it to install, and then it would get stuck in a boot loop. Did it a few times from stock to make sure I wasn't throwing some older file in the mix. When I went to flash super in A11, it showed "Super ()" instead of "Super (Product, System, Vendor)" like it does in A10. Don't know if that means anything.

Also, the newest v5 SP Flash Tool was getting stuck on me. Went back down to 5.1916 that I've been using and it worked all but once. Weird.
[Miscellaneous Android Development] a-dead-trousers:
Try to flash "vbmeta.img" like you would on a "normal" install. I did this on my tests all the time to make absolutely sure I have it in a working condition.

It is also possible to flash "super" via bootloader instead of twrp.

When "wiping" data I always used the "format" option but it is also possible to flash "userdata" from the bootloader.

Last but not least you can create a complete "super.img".

https://github.com/ADeadTrousers/an...om_LXL/blob/master/docs/HOW-TO-FLASH-SUPER.md

EDIT:

HOW does this "bootloop" manifest itself? Did you also install add-ons like gapps?
[Miscellaneous Android Development] SepticFuddy:
I was re-flashing vbmeta every time from stock. Is there a particular advantage to flashing things from the bootloader instead of TWRP?

I was flashing in Magisk 23 which I need for MicroG. No gapps. Are you suggesting that there was not enough space left in the super you provided for Magisk? The zip is 6714KB