yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] WeAreGod:
Got any Crypto addresses or PayPal that I can send gratitude to?
[Miscellaneous Android Development] a-dead-trousers:
Nope.

Your happiness is gratification enough.:cool:
[Miscellaneous Android Development] WeAreGod:
I am very happy!

I have one more question though, I installed Magisk using TWRP, then installed the app. Now I am able to grant superuser permissions but some apps say root access not achieved. I thought Superuser permissions are the equivalent of root. If not, then can you please send me in the direction of achieving root?
[Miscellaneous Android Development] WeAreGod:
Nevermind, it says I have root now. I am concerned that I installed Supersu and then when I tried to uninstall it, it says "cannot uninstall system app" but the app icon disappeared and now I can't find it.
[Miscellaneous Android Development] brn5ck:
Hi guys,

i've got an Atom XL last week and immediately flash your Lineage OS build on it.

The system runs smooth, but i'm having some issues with TWRP recovery that has no touchscreen.

I was able to install the system with an OTG cable and an USB mouse, but cannot solve the no-touch in recovery problem.

Tried to use older versions and reflash the stock ROM 2021052010_g63v71c2k_dfl_seea and start again but no success.

So i tried to follow your instructions to build my own TWRP but i'im stuck at "repo init -u https://github.com/minimal-manifest-twrp/platform_manifest_twrp_omni.git -b twrp-10.0": it seems that there's no twrp-10.0 but i can find a twrp-10.0-deprecated, not sure if that's what i need

Yesterday the system notified me about a new LineageOS update: if i enable the update recovery option which recovery i will get?

Some info about my device:

AtomXL EEA

TWRP TWRP 3.5.2 10-0 v20210810-beta

Lineage 17.1 v20211114-alpha

Thank you for your work
[Miscellaneous Android Development] a-dead-trousers:
Yeah TWRP just recently decided to drop their 10.0 trees in favour of 9.0 and 11.0 (10.0 should switch to 11.0) but the minimal manifest for omni which I based my build on isn't ready yet. As soon as this gets finished I'll try to create a new build with TWRP 3.6.0.

You coud try the "twrp-10.0-deprecated" branch instead but I cannot guarantee that this will work.

The problem with no touch in recovery is with a hardcoded boot-mode detection which disables the touch driver when booting into recovery mode. Therefore I had to "modify" the kernel in my TWRP build to behave mirrored (no touch in system while touch in recovery). I have the same phone and also the same twrp build running on it for quite some time now. I also just reinstalled v20210810 fresh from github without problems.

My only guess is that the phone boots the recovery in "system" mode, maybe because of a problem with the internal partitioning layout.

It would be interesting to test this theory by creating a TWRP with the unmodified kernel from my Lineage OS build.

The automatic update should work even without touch. You just need to "reboot" the phone after the update finished by long pressing the power button.
[Miscellaneous Android Development] brn5ck:
I'm trying to build a TWRP image with the kernel from LOS image without downloading the entire source, here the steps i followed (where boot_LOS.img is the boot image from the Lineage OS installation zip and recovery_TWRP.img is your github build):

But still no touch in recovery.

How could i check if there's a problem with the partitioning layout and eventually fix it? Is there a way to find in which mode it booted the recovery or any other useful debug command?

Maybe during holidays i'll take some time to reflash sock rom and start again the installation process, but for now i'd prefer to not factory reset the phone before being sure of the real cause (if there's no risk of bricking the phone after an update is something i can live with)

Anyway i already installed the LOS update and didn't have any problem
[Miscellaneous Android Development] a-dead-trousers:
This was just a wild guess. ;)

I don't really know how to test for that.

Thanks to SPFlash you should be able to get at least back to stock after "bricking" the phone.

The only thing you shouldn't EVER do is to "format" the phone cause that will clear everything including the IMEI information you'd need to connect to your ISP.

That's good to hear.

Just a hunch:

By "touch is not working", do you mean that it isn't working on the unlock screen of TWRP? Because there I also need to press down a little bit longer until it is registered.
[Miscellaneous Android Development] brn5ck:
Unfortunately i mean not working at all for password input or menu navigation
[Miscellaneous Android Development] a-dead-trousers:
I just found out that my previous TWRP release for the Atom L TEE wasn't working (possible since the May update). So there is a new release which should fix this.

Sorry for the inconvenience.
[Miscellaneous Android Development] clewis.it:
Hey. I just saw this. How did you modify this kernel? I have wanted to do the same thing for my phone, but I can't find any specifics to patch this boot-mode detection.
[Miscellaneous Android Development] a-dead-trousers:
See my guide

twrp_device_Unihertz_Atom_LXL/docs/HOW-TO-PATCH.md at master · ADeadTrousers/twrp_device_Unihertz_Atom_LXL

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

github.com
[Miscellaneous Android Development] clewis.it:
Ah, thanks for this. That's quite a read. I do recall seeing that hovatek guide. I tried to follow it, but I do not have access to that ominous tool you mention. If I send you the recovery image kernel, would you be able to modify it for me?
[Miscellaneous Android Development] a-dead-trousers:
I could do that but you wouldn't learn anything from that ;)

There is a possibility to get that tool by searching for "github" and it's name in google.

If you want to take the easy way out I'd need the symbols besides the kernel. Contact me via PM.
[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 (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).
[Miscellaneous Android Development] a-dead-trousers:
I just realized that there are in fact TWO different touchpad drivers in the kernel. So I created a new release with both drivers modified to load in recovery mode. Hopefully this will fix that elusive "touchpad not working" bug. Also the new twrp version 3.7.0_11.0 seemed to have been already active in the repos while not officially endorsed yet.
[Miscellaneous Android Development] DocMAX:
Can you do a Jelly2 build too? It's almost the same device. Thanks.
[Miscellaneous Android Development] a-dead-trousers:
Nope, because I can' t test the result.
[Miscellaneous Android Development] a-dead-trousers:
Finally I was able to get the decryption to work on TWRP 3.7.0_11-0 for our devices. 🥳
[Miscellaneous Android Development] droidzer1:
I'm very willing to test as this Jelly 2 is not a primary phone. I've tried porting about a hundred times using your twrp for the Atom L and Atom XL by running them through Android Image Kitchen but no luck with all variations I tried. It only reboots to stock after doing 'fastboot reboot recovery'. However when I just used your image as is without any changes it seems to boot and stop with a green line across the top of the screen. It's almost as if it has booted TWRP but I can't see it or do anything with screen taps.
[Miscellaneous Android Development] a-dead-trousers:
I don't recommend this approach as it tends to be instable.

This command is invalid. You can only do a 'fastboot reboot' and press the Vol+ key to boot into the recovery.

Nope, that's the ultimate kernel panic to tell you the hardware isn't compatible.

If you are so willing why don't you start by setting up a build environment and get into building your own recovery?
[Miscellaneous Android Development] droidzer1:
I did manage to build a working TWRP several years ago ( https://xdaforums.com/t/twrp-modded-to-work-now-with-unihertz-atom.3885793/ ) for the Unihertz Atom (I could not find TWRP for it anywhere else after searching for a couple months) but that only had Nougat on it. However I built it in a very round about way as I don't know anything about setting up a build environment or any of the ways I believe are more often used to make TWRP. And having been born in the 40's I just may be a little too far over the hill to be able to learn all that is needed for such a task. However if I had someone who could answer a boat load of questions I'd be willing to give it a try if it sounded like an achievable task.
[Miscellaneous Android Development] droidzer1:
I agree Android Image Kitchen seems of very little help. I even tried unpacking and repacking the stock recovery without any modifications and it would not boot. Actually the "fastboot reboot recovery" does take me to the same place as the power button + volume Up does which gives the belly up Android and 'No command' screen. From there just holding power and doing a quick click on volume up gets me to the stock recovery page. There does not seem to be any way (that I have found) to get directly to the recovery page in one step. I began wondering if that is some sort of protection the Jelly 2 has to prevent replacing recovery.
[Miscellaneous Android Development] a-dead-trousers:
I just checked the Unihertz GoogleDrive.

By any chance are you using the latest stock rom from 2023? (see build date in settings > about > android version)
[Miscellaneous Android Development] droidzer1:
No, I did download that one but the phone had a 2021 version on it until today I put this one on it: 2022062721_g55v71c2k_dfl_tee.zip . The ROM it came with didn't match anything I saw on the Google drive. Would it be better to have that latest 2023 version? I tend to avoid updates as they always seem to implement more things that block root and custom recoveries.
[Miscellaneous Android Development] a-dead-trousers:
So you are using the stock rom? Why do you need a custom recovery then?

Also in my experience the stock ROM tends to replace any custom recovery on boot. More so with the latest stock ROM for the Atom L/XL (and probably also for your Jelly 2) as they moved it to the vedor partition which is needed for a custom ROM to fully work. That's the reason why I asked. If you are using the latest vendor partition even a custom ROM can't "protect" the custom recovery from being overwritten on every reboot.
[Miscellaneous Android Development] droidzer1:
Thanks for the replies and that bit of info I didn't know. I like having a TWRP type whole image backup so if something develops a problem that causes loss of function I can do a restore without having to track down the problem. Or if the phone becomes completely non-functional a TWRP restore can qucikly make things right again.

If there is a custom ROM that has full functionality of all the phones capabilities I'd be interested in it. From most of what I've seen though custom ROM's often have some issues that prevent an occasional function from working correctly so while I've used some in the past I have mostly stuck with stock ROMs. I guess I'll likely give up on this unless someone figures out a way to bypass TWRP from being overwritten.

I did finally find a fairly good backup app that actually backs up Settings, apps, app data, messages and so on with the ability to save that on the phone or to your PC. Nothing else I have found covers as much and does it as well as this app - "Backup Your Mobile_2.3.43" except of course TWRP but that seems out of reach for now.
[Miscellaneous Android Development] droidzer1:
While I didn't seem to get this impression from reading Meetoul's thread on TWRP on the Jelly I now have TWRP installed on my Jelly 2 fully working with touch and it even backs up user data AND survives rebooting the stock ROM. I did first flash OS10 and apparently was lucky to have one of the Jelly 2's before an apparent hardware change that broke some things like ability to use the touch screen. I'm totally fine with OS10. I read through Meetoul's thread several times and this was not obvious there so I'll post this info on Meetoul's thread and apologies for taking space here on a less relevant subject - just wanted to say I didn't give up :cool:
[Miscellaneous Android Development] bankerjoe:
I recently acquired an Atom L from a local buy nothing group. I've puddled around, including installing Magisk on it (via instructions here - https://gist.github.com/zArubaru/70bf07a3c729e4771c8753b94faf203d), although this was more to get SU access and debloat the thing some.

Franky, I think I like the interface (it's pretty clean) and what I guess is the stock ROM. Just curious if there's any point in installing TWRP, since if I'm following the above, it has the potential to present challenges (I do like having TWRP though, I have it on other devices). I currently have the 2021-10-07 build, I think, although I have downloaded the official ones from Unihertz, although none of them are the dates mentioned in this post either (none EEA).

Anyway, curious about some thoughts. TYIA.
[Miscellaneous Android Development] a-dead-trousers:
There might be slight differences of what the rom files says to what the actual build date is. Most of the time I'm referring to the dates in the rom filenames (up to the month) as these should be consistent for everyone downloading them. Also I think there are some minor OTA updates that never saw a stock rom zip release on the unihertz gdrive.

As for a custom recovery you'd need to unlock the phone first which removes all security related basics of the android ecosystem (not being able to change system/product/vendor). This will inevitably break SafetyNet/Play Integrity API. Sometimes you might be able to hide magisk using special magisk modules and so on but this can't hide an unlocked phone. So you really need to be sure to do that.

My TWRP should in theory work with the stock rom but unfortunaly unihertz included a recovery "restore" script right inside the system partition which replaces the recovery on every boot with the stock one. I have some reports of other users claiming that it doesn't happen for them but on my two phones it's always resetting the recovery.

In the later roms (2022-12 and 2023-01) the recovery restore script was moved to vendor which is even worse GSI and custom rom wise meaning it forces you to modify the vendor image in order to get rid of it. That's one of the many reasons I didn't bother to upgrade my builds from the stock 2021s to the 2022/2023s.
[Miscellaneous Android Development] bankerjoe:
So it sounds like unless I feel like using a custom ROM, don't bother with TWRP. Do I understand correctly?
[Miscellaneous Android Development] a-dead-trousers:
Pretty much. Or you'd need to "deactivate" the restore script somehow.
[Miscellaneous Android Development] bankerjoe:
Yea, that's way outside my skillset haha. Thanks.
[Miscellaneous Android Development] a-dead-trousers:
3.7.1_12-0 is live.

Please consider this an alpha built for now and for the future as it will never ever be able to decrypt data. *RIP*
[Samsung Galaxy A71 Questions & Answers] PatrykP56:
Hello, I have a problem after changing the software from PLS to XEO, I do not have range, but the sim card sees normally. I was uploading through odin
[T-Mobile LG G5 Questions & Answers] schalli110:
Hi all,

today I updated Magisk on my H830 (stock H83030c with TWRP) and now it's stuck in a boot loop.

Since the phone does not support flashing in fastboot, is there any way to fix this without re-flashing a stock kdz?

<edit>

The phone is showing the "bootloader unlocked warning", then flashes black and shows the warning again, over and over.

I can't enter TWRP, only fastboot and download mode.

Thanks,

schalli110
[T-Mobile LG G5 Questions & Answers] schalli110:
Never mind.

Mashing the power button like crazy finally got me into TWRP and I was able to reflash a stock boot.img and then an old version of Magisk.

Phew.

I'll leave this thread in the hopes it helps other poor souls.
[T-Mobile LG G5 Questions & Answers] Leroy_Sparks:
I have the exact same problem (thanks Magisk team!). Can you expound on the power button technique that allowed you to access TWRP? By repeatedly pressing it?

Funny, I've seen multiple posts about this happening on G5 phones after the Magisk update, but nothing on the Magisk threads.
[General Topics] Strunky25:
Hi guys,

I' have a Xiaomi mi 9T on MIUI 12 beta.

I used to have a password encryption on TWRP but after flashing my rom to fix some issues I also cleaned data and everything else, so now im not supossed to have a TWRP password anymore,

after trying my old password several times and trying the defaults passwords i saw online my issue wasn't fixed so I tried formatting everything again. I continue to have the same issue, TWRP is asking for a password and i cant fix it even after clean data.

First post, im new to all this so sorry if something is wrong any help would be appreciated!
[Wing, P4350 General] fuenbry:
I have read all the sreps but i still feel kinda iffy. I'm scared to brick my phone... can anyone help me and possible tell me what to do!:(
[Wing, P4350 General] hotrod101:
Sorry I cannot help you; however, you really need to avoid creating a new thread every time you have a question - especially if it is the same question. Read the forum rules, FAQ's, WIKI etc... There are many answers and guides available that a lot of people put a lot of time and effort into writing.
[Wing, P4350 General] BillG24:
Don't worry, it all comes down to something very simple. I did it the first time myself a few weeks ago by following a thread created by Papamopps. He wrote a very good step by step instruction. You can find it here http://xdaforums.com/showthread.php?t=369397

Custom makes all things easy :)

Happy flashing
[General Questions and Answers] nenno1983:
Hi,

i 'm developping a app and i need use a magisk module inside, but i don't know how do it.

Is there someone who can help me?

The phone is rooted by magisk 21.2

Thanks
[Xiaomi Mi 10 Questions & Answers] bungalowbill:
Since updating to MIUI 12.2.1.0 Stable (RJBEUXM) I have two issues -

Fingerprint reader is dire - it used to open in fractions of a second, now it fails to read my finger 80% of the time. I have re-trained again and again, but it just can't read my fingers any more.

Google Maps force closes after a random amount of use - sometimes it will go an hour, sometimes just after a few minutes - not much use as a SatNav any more.

I've reset the phone and set it up again from scratch just in case (a pain with all my apps to reinstall and set up!), but both these issues persist.

Has anyone else experienced similar? This is a stock Mi 10, never tinkered with, from Amazon UK.

Bill.
[Xiaomi Mi 10 Questions & Answers] sparkyhoney:
Did you get the update ota? When did you get the update? I bought the phone from the same place as you.
[Xiaomi Mi 10 Questions & Answers] Antyhaker:
I have the same problem on this and latest version. I don't know if this is a problem with MIUI or Android 11 itself.
[Xiaomi Mi 10 Questions & Answers] bungalowbill:
I got the update about the 30th December, it just appeared overnight. When I picked up my phone in the morning, fingerprint broken and Google Maps crashing.
[Xiaomi Mi 10 Questions & Answers] bungalowbill:
I see that V12.2.4.0.RJBEUXM came out on 14th January, I wonder if I should force an update to this, or wait till OTA.
[Xiaomi Mi 10 Questions & Answers] Antyhaker:
You can always download ZIP and manual nstall it via updater (EEA ROM).
[Samsung Galaxy S21 Questions] 4umexdeeay:
Hi there,

Currently using the OnePlus 7T-Pro and will be using my carrier's upgrade service to switch to the S21 Ultra by the end of January.

Since the S21 doesn't include a charging brick, I'm wondering if it's safe/compatible to use non Samsung branded power brick with it?

Furthermore, would the 30W charging speed of the 7T-Pro brick be equalled on the S21?

Any feedback is appreciated - thanks in advance 😉
[Samsung Galaxy S21 Questions] mzsquared:
You have to try it. It's safe, yes and it should charge the s21 faster then Samsung's standard 25W charger. Am not sure if OnePlus uses a proprietary USB-C cable, but you'll get the cable from Samsung as well.
[Samsung Galaxy S21 Questions] 4umexdeeay:
Really helpful...thanks mzsquared (y)
[Samsung Galaxy S21 Questions] BladeRunner:
One Plus's Warp chargers will charge other phones very slowly as some of the charging circuitry is built into the phone. I mean like REALLY slow. Just plugged a warp charger into my S20 plus at 71% and it says 10 hours 23 minutes until full.
[Samsung Galaxy S21 Questions] 4umexdeeay:
Hi BladeRunner,

Good lookin out, as they say...sounds like I'll have to go the proprietary route after all.

I'll also update this thread in a couple weeks after testing out the OP charger on the Samsung.
[Samsung Galaxy S21 Questions] mzsquared:
Yes, try it out first and w/ different cables too, the USB 3.0/3.1/3.2 supposed to be all back compatible, but there are many pos* manufacturers who cut corners.

*("profits-over-standards")
[Samsung Galaxy S21 Questions] Collin80:
You can also try just plain using a cord between your PC and the phone. Really, I've seen fairly decent charging performance this way. Technically USB 3.X has support for some pretty heavy power modes so if your PC can do it then the phone might charge pretty fast. Yes, that limits where you can charge potentially but it might be a decent option for at home or work.
[Samsung Galaxy S21 Questions] hehfahq:
These super fast change my S20+ at maximum speed. I assume it will also work for the S21 series

Amazon.com: Super Fast Charger Type C, PD 25W USB C Wall Charger for Samsung Galaxy S21/S21 Ultra/S21+/S20/S20 Ultra/S20+/Note10/ 10+/Note 20/20 Ultra,Z Fold3 5G[2-Pack Charging Block+2-Pack 5ft USB C Cable] : Cell Phones & Accessories

Amazon.com: Super Fast Charger Type C, PD 25W USB C Wall Charger for Samsung Galaxy S21/S21 Ultra/S21+/S20/S20 Ultra/S20+/Note10/ 10+/Note 20/20 Ultra,Z Fold3 5G[2-Pack Charging Block+2-Pack 5ft USB C Cable] : Cell Phones & Accessories

www.amazon.com
[Samsung Galaxy S21 Questions] 4umexdeeay:
Update:

The OP charger works but at standard speed, with a description of "Cable charging" when in use.

A properly compatible 25W brick & cable from Amazon, nearly identical to the ones linked by hehfahq above, effectively have the "Super fast charging" speeds.

Thanks to all in this thread for contributing your feedback & guidance. 👍
[Samsung Galaxy S21 Questions] sykozylot:
Same results for me, using Oneplus 5 and 5t power bricks. They charge my s21 Ultra slowly.
[Samsung Galaxy S21 Questions] shobuddy:
My OnePlus 30W brick also charges the S21 at a snails pace. In general, I'm finding charging to be really slow on the S21 compared to my previous OnePlus 3. Granted the battery is 1000mAH larger but the charging times are more than double using PC charging via USB.

Anyone have experience with this charger: Link
[Samsung Galaxy S21 Questions] deziderkovacs:
You have to look after chargers with Power Delivery system with equal PD generation that is used in the OEM charging brick. And yes, cable could be misconductive aswell so it´s highly recommended to use OEM or similar PD cable with it.