yashsingh1/xdaforums huggingface dataset:
[Lenovo P11] LSS4181:
You can simply use a minimalist TWRP manifest to set up a TWRP build environment. Also, any known-working TWRP device tree of a similar device can be used as a starting point.

In this device's case, the necessary blobs are included in the device tree. Normally you just need to replace any blob present in the tree with the ones from your own stock firmware (refer to guides on how to extract files from stock FW images). There is no need to bring in more, unless some blobs refused to work due to it depending on other files not present.

As for kernel binary and some device-specific configuration parameters, you can count on twrpdtgen (refer to the OP) which I've been using for this device. It creates a simple device tree for your device using a stock recovery image, extracting the kernel binary and some useful information in the progress, which you can then refer and apply to the tree you're working on.

The trickiest part, however, is to figure out the correct parameters to allow the data partition to be decrypted correctly. Sadly, encrypted /data can be very delicate and if you consider this a hassle you can simply use a Magisk module to disable encryption entirely.
[Lenovo P11] Isrgish:
Thanks for your reply. I did disable encryption on my device so that for now wont be a problem. I will try your suggestions and see where that will lead me.

Is the twrp tree on the OP the tree you are suggesting for me to use? If not where can I find the twrp tree you used?

It would just be great if I can figure out why using your twrp as per the guide at Porting TWRP without source doesn't work. I would have assumed that it would work since the 2 devices are similar.

If you are willing to help me with this I can provide more info.

Thanks again for your help.
[Lenovo P11] LSS4181:
I used Ungeskriptet's TB-J716F tree as a base. Also, while twrpdtgen can create a basic TWRP device tree for you using a stock recovery as input, I did not use it directly. Only the extracted kernel files as well as some usable TWRP-related parameters were used.

As for what blobs are needed (in case you're going to develop TWRP for a device from scratch with no viable reference), I'm not an expert, though fortunately my device is mostly similar to J716F that I don't really need to introduce more blobs. A device using the same SoC would be the best. If you can't find a same SoC, similar ones may also do.

On the other hand, screen functionality could be a main issue due to differences in display and touchscreen hardware. In my first TWRP builds, the display was correct (landscape), but the touchscreen was rotated (portrait), that I had to add parameters to correct it.

I just checked the "Porting TWRP without source" guide you mentioned... it seems to be using an existing TWRP image as a base instead of building... so no device trees or build environments were involved at all...

If you have a good Linux environment (be it physical or virtual), it should not be difficult to set up a build environment following related guides, and start working on a device tree. The good part is, the kernel source of the device you want to work on is not required for building TWRP. If you can obtain your device's factory images then you should be able to start your work.
[Lenovo P11] Alex57185:
Hi, was everyone able to get the sn.img file to unlock the bootloader?

I have the 5G version (TB-Q706Z), and it seems to be impossible to get the file on the zui website.
[Lenovo P11] Isrgish:
Thanks I will try to work on this. and hope to succeed.
[Lenovo P11] Isrgish:
Have you tried to unlock with fastboot? You will need to set the OEM Unlocking in developer settings.
[Lenovo P11] Alex57185:
It was so damn simple ... Thank you, I totally forgot that this one option.
[Lenovo P11] fakeall:
I can now answer my own question regarding the Chinese global ROM, since It's bought a tablet from a Chinese vendor. It came with Android 11, and worked ok, but when l ran into a software problem I decided to do a factory reset. To my surprise it booted into Android 12! After working with it for two weeks I have not found any problems.

TheROM is reported as

TB-Q706F_S410335_230719_ROW

The first difficulty appeared today, when I tried to boot into fastboot. It just opens the same page again instead of fastboot. At the bottom it says "device state locked", but I do not know whether this refers to the bootloader or to fastboot?

Is there anything I can do to activate fastboot?
[Lenovo P11] hyunno:
How about for Lenovo Pad Pro 12.7(TB371FC, Chines version, ZUI 15)?
[Lenovo P11] fakeall:
Things have progressed, the bootloader is unlocked, and interestingly it now reports Android 13 ! If that is the, it must have autoupdated itself.

Would like to root the device now, but without permanently installing TWRP. Sadly the temporary boot will not work work on this device

fastboot boot twrp.img

returns a "Command failed", so I can neither install Magisk nor extract boot.img.
[Lenovo P11] LSS4181:
If you can obtain the factory images for the device you mentioned, then you probably could start working on one. I don't own a TB371FC, so you'll have to test its functionality on your own device.

You probably need to take a note of your device's partition table and see if there is any difference in comparison with other similar devices like J716F and Q706F.

And you most likely would have to disable encryption altogether. I could not get TWRP to decrypt newer /data (A12 and onwards) when PIN/Pattern is present, and encryption in general will get in the way when restoring your system data to a previous state in case you did anything wrong, as the keys are affected by many factors beyond user's control.
[Lenovo P11] Isrgish:
@LSS4181

I finaly was able to get this all together and started working on buildingba twrp for mt device.

I'm able to vuild the twrp but the same problem I originaly had with using a ported one continues to plague me with the built obe.

Basicaly the twrp opens and all I can see is a thin gray line at the top. This line then changes to blue. The rest of the screen is black. If I toggle the device off and then on again, then I have a slightly thicker blue line at the top and the top half of the title line of a tipical twrp is visible in it. The rest of the screen is now blue ( a different shade then the top line). It seems as if I get only a 1/50 th of the screen and the rest is missing.

I know that the twrp is working since I can access the device with adb and am able to run twrp commands from the command line (adb shell).

As far as I can tell the recovery log looks fine.

Any idea what I can do to fix this?
[Lenovo P11] LSS4181:
Hmmm... looks like something odd with your display drivers or configurations, but other functions appear to work fine.

I don't own your device model, so I can't be not sure what parameters may be needed. Are you using your own device's kernel (preferably from stock recovery)?

Perhaps consider doing a dmesg from recovery, or if that doesn't work, from running system (may require you to be rooted), to see if there is any information related to your display hardware that could be helpful for debugging. It probably won't be easy considering some poorly written vendor drivers may spew out a lot of unnecessary outputs there preventing you from reaching the information you want...
[Lenovo P11] Isrgish:
@LSS4181

I'm using the kernel from my stock recovery.

How do I get the dmsg logs? Should I just run dmsg > file?
[Lenovo P11] LSS4181:
Yes. You can just dump the dmesg into file.

Not sure if stock recovery permits such... but I think you can do this in your own-built TWRP. It's mainly to look for any kernel output regarding display initialization.
[Lenovo P11] Isrgish:
@LSS4181

Sorry for not getting back sooner but I installed a GSI on my device and was having issues with it so I didn't have time to look at TWRP. Now that I got that setteled I'm back to TWRP.

I 'm attaching here the dmesg log as well as recovery log and the logcat.

I don't see anything that pops out at me from these logs but I'm not really familiar what I should be looking for. Maybe if you have some time you can look at them and see if there is anything there.

I wish I can take a screenshot to show you what it looks like because it seems that there is a TWRP screen just that it is only showing the top sliver of it. To me this makes it seem that the graphics is being loaded correctly. Maybe this is more that the size of the screen is not being recognized correctly.

Any help would be greatly appreciated.
[Lenovo P11] Isrgish:
@LSS4181

I'm attaching here 2 screenshots that show my TWRP

The first one shows the TWRP right after loading it. The 2nd one shows after I toggle the power button off and on again.
[Lenovo P11] MetaErgo:
I am redirected from getdroidtips's tb-j607f guide. why is it heading into tb-q706f? is it compatible?
[Lenovo P11] LSS4181:
I grepped about some display-related key words (drm, dsi) in your dmesg and found a bit of info about your device's display panel (nt36523) and there seems to be an error regarding ktz8866 probably when you turned the display off then on.

As I don't own your particular model what I could help out is limited. Are you using vendor libraries from your own device? If there's no factory image available for your device, consider extracting the files directly from your device. Provided TWRP itself is operational, then you should already be able to do so -- just mount /vendor and copy its contents out.

Anyway, you should consider start your own thread about your progress (such as device tree) as well as related questions, as I prefer keeping the scope of this thread to my own device (Q706F) to avoid confusion.
[Lenovo P11] Isrgish:
Thanks for your help.

Sorry for using your thread it is just that your device is very similar to my=ine (internally). There is a section for my device and requests for help with twrp but no one seems to be able to help. Here you have good knowledge and was willing to help. But as you requested I will stop posting here.

Would you be willing to help (when you can and have time) from my own thread? Can I tag you there?

Sorry again and thanks for all the help you provided.
[Lenovo P11] LSS4181:
You're welcome. Honestly I still have a lot to learn about Android building.

By the way, I've just found the forum section for your particular device (Legion Y700). I'm not seeing any TWRP related discussions there, however...
[Lenovo P11] Isrgish:
@LSS4181

It's more that in the Main Thread questions were asked about the TWRP and there wasn't much torthcoming answers. This made it seem to me that no one has the knoledge for building it or to help. I will try to put together a thread and see where it leads.

BTW since I'm posing anyways which files were you referring to when you said I should take them from /vendor on my device. Which files?

Thanks again for all your help it is really appreciated. It took me to learn how to compile TWRP (even though it isn't fully working) a step which I was reluctant to take before hand.
[Lenovo P11] LSS4181:
You can refer to my device tree's "recovery/root" folder about a list of the files you need to replace with those from your own vendor.

Can't be sure if using the right vendor blobs will really address issues related to display initialization, as I happened to find an existing 9707F tree for TWRP which appears to be hitting the same wall (display issues) as yours...

It's possible that you need to adjust some parameters in BoardConfig.mk and other related files. If you have used twrpdtgen on your stock recovery image, you probably could get some hints on what you need to modify from the generated tree.

Consider referring to the main TWRP dev thread to see if anyone had any experience on display-related issues in the past... the thread is very big so you'll need to do some search.
[Lenovo P11] moluanshanhe:
sorry
[Lenovo P11] moluanshanhe:
Hello! Can you give me a twrp that you made? I really need it. Thank you very much.
[Lenovo P11] Isrgish:
Which device are you looking for a TWRP?

As mentioned I haven't been successful in building a fully working TWRP for the TB-9707F but there is a TWRP that works with the Command line script available. Please take a look at my post here.
[Lenovo P11] moluanshanhe:
Thank you very much for your reply, I am looking for a TWRP for the TB371FC, I think I replied to the wrong message, very sorry.
[Samsung Galaxy A71 Questions & Answers] vulcanrvn:
Hello all,

I have a SM-A715F/DS and since it is an international version there isn't any USA CSC firmwares. I wanted to see which CSC has worked best for those in the USA, and better yet if you use T-mobile.

I've been using XXV (Vietnam) since I got the phone since that is what came with it but have had one issue that has driven me nuts.

At least 3-5 times a day, usually in the evening my data will randomly stop working. I've noticed that the network traffic icon in the status bar will show the upload error stuck on and I'll have zero data. The only way I've found to fix it without having to reboot is to switch the Mobile network type from LTE/Automatic to WCDMA/CDMA then back. Does anyone else have a similar issue they've been able to fix permanently?

I've tried manually adding various APN settings but that doesn't seem to make a difference.

Thanks
[Touch Diamond, MDA Compact IV Themes and Apps] odyssey96:
Hi,

I have searched for the below but cannot seem to find any relevant results so I shall post my requests here and hopefully some very generous individual(s) with the necessary knowledge and resources may be able to provide...

1. Is there a way of reducing the font size in Touchflo3d interface, like the text message font size?? I think it is rather large...

2. Is there a way (I think this maybe .tsk related) to change the background colour of the sms/mms outlook colours to a black background with white text? I mean if you were to select the All Messages option in the SMS tab of Touchflo for example..

Apologies if this sounds demanding, but I think it may benefit more than just me for those who, for example have installed the IPC Black Phone Dialer because in my opinion it matches the overall colour theme of the Diamond.

Thank you for your time!
[Touch Diamond, MDA Compact IV Themes and Apps] w7excursion:
Im looking for the answer to #2. Anyone?
[Touch Diamond, MDA Compact IV Themes and Apps] sakkehh:
Would like to know the answer to #2 aswell.
[General Questions and Answers] Lionel David:
Greetings! Well, the Title says it all. It's almost 1 year from the phone's release and there's no custom ROM yet. This is a direct request to the Devs out there to support Poco C3 so please, help us out. I see a lot of devs supporting Redmi 9C and Redmi 9A(India) which are basically Poco C3 so why not support this too ;-). Thanks in advance for any kind of support (Also, the device is not even in the list of devices in xda. Do help us out on that too).

Regards,

Poco C3 users.
[Redmi 9 Power / 9T] hamid_dabouz:
Hi, I've noticed that the battery on my Redmi 9t draining faster on custom roms comparing to the stock miui rom

And I've tried many custom roms like Dot os, pixel experienc.......etc , but they all drain battery morz then the stock rom, and i've tried many custom kernels but it still drain battery, so please Has anyone noticed this problem or have been able to fix it ?
[Redmi 9 Power / 9T] Qpb:
Download AccuBattery and check which app is draining the battery. And also check the battery's health.
[Redmi 9 Power / 9T] Atanassoww:
Some apk's draining the Battery fast, example the Facebook application.
[Redmi 9 Power / 9T] Caliburno:
That's the price of using custom roms. Unless the device is quite popular and has a huge fan base working on stuff, you will never get a custom rom better than the original.
[Redmi 9 Power / 9T] conduisant:
i'm using havoc os without GAPPS and no battery problem, such as said, it depend on wich apps you have installed after the ROM
[8125, K-JAM, P4300, MDA Vario ROM Development] evoluzionne:
hi... i want a clean WM6.1 Rom for my G3 device please....
[8125, K-JAM, P4300, MDA Vario ROM Development] + Que PPC:
Good luck in your search travel!

So search for vanilla flavored Roms There are many... just SEARCH!!! :p
[8125, K-JAM, P4300, MDA Vario ROM Development] Uracil:
Are you sure about that? The only bare-bones recent WM6.1 ROM build I see is j.vd.spank's "WM 6.1 CE OS.19588 from Diamond", and that one has a few issues that were never fixed.

It might be nice to see a truly clean 20273 ROM.
[8125, K-JAM, P4300, MDA Vario ROM Development] + Que PPC:
It is too much vanillas please!!!!

TNT 20273 vanilla

yes that 19588!

AMP is 6.1 too...

Search people search....

But... tell me... honestly... Is there any Coocked ROM that is Perfect!???? :p

That comment maybe starts fire on this web men!!! but I dont think so... just words... :D
[8125, K-JAM, P4300, MDA Vario ROM Development] Uracil:
TNT is new but even the vanilla version is far from "clean". AMP is older and no cleaner. No ROM is perfect, of course, but I really think evoluzionne's request is valid... and probably easily satisfied. Making a fully customized ROM must be more challenging (albeit more satisfying) than a naked version.
[8125, K-JAM, P4300, MDA Vario ROM Development] joemanb:
I used to be a believer in vanilla ROMs, but I have found that any ROM space that goes unused is just wasted. Cook your own ROM and pack it to the MAX to utilize all the space that's available. Tweak it as you find problems and recook.

The Wizard ROM holds about 80 megs (this total will decrease if you put compressed files in your ROM), but if you only cook 60 megs into it, you cannot reclaim that wasted 20 megs. You might as well use it.

I have been on a space saving crusade for the last 3 weeks and realized that my vanilla ROM was just a big waste of space. You can test it yourself by cooking a fully packed ROM, and a vanilla ROM, and check the free space for each after the first boot. (it usually says about 2 megs of storage RAM has been used. This is from initflashfiles copying files from ROM into RAM.)

During this time I also realized I could use the Extended_Rom to store some system files! I have put NetCF3.5, SqlCE3.5, and TCPMP on the Extended_Rom, and it's working great. This saves me 10 megs, my cooked ROM has over 80 APPs (before UC)! It's as fast and stable as any ROM I've tried.
[8125, K-JAM, P4300, MDA Vario ROM Development] evoluzionne:
-joemanb-

ahh that really what i want.. so i want a basic ROM of 6.1 so that i will able to cook it to match my own need....

(basically i often using office, email, music player, etc)

but i realize that i just cannot to just ask for it to anybody (search, search......)

wish me luck

cheers

evo
[8125, K-JAM, P4300, MDA Vario ROM Development] Uracil:
That's a pretty good point. Clutter is bad regardless, and I strive for its elimination, but it is important to realize that unused ROM space doesn't translate into available storage space.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Eidoron1:
View attachment 5503907

Project Arcana for Poco F3/Mi 11x/Redmi K40 [alioth/aliothin]

What is this?

*Project Arcana is a simple rom, fueled by Pixel Experience that aims to be simple yet cunning. Project Arcana provides necessary

customization that is needed for every day life, from your traffic indicator down to your favorite icon styles.

While also promising to be simple, Project Arcana was made to be aesthetic without making its users go through a lot

of configurations. Project Arcana is a fan of simplicity. We strive to keep the ROM bloat free and fast.

Based on Android 12

Whats working?

Wi-Fi

RIL

Mobile data

GPS

Camera

Flashlight

Camcorder

Bluetooth

FM radio

Fingerprint reader

NFC

Lights

Sound/vibration

Known issues

Nothing yet

You tell me

DON'T FLASH GAPPS, THEY'RE ALREADY INCLUDED

Stay tuned

Our Telegram channel

​

Android OS version: Android 12

Security patch level: January 2022

Build author/Device Maintainer: Eidoron1

Device Source code: https://github.com/Eidoron1/android_device_xiaomi_alioth

Source code: https://github.com/projectarcana-aosp

ROM Developer: dlwlrma123

Download

Kernel Source
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] cooleydoo22:
What is the battery endurance like in this rom in on pixelos
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Karanrana1911:
Is it work on realme 8.?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] IAMPRISM:
Don't be an idiot please this is the Poco F3 forum not realme 8.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Karanrana1911:
😑😑😑 Any thing about realme 8
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] lapirado:
Loved this one! Would live to see it return
[Samsung Galaxy A22 5G] Platypus Enthusiast:
Since nobody wanted to make a TWRP build for the A22 5G, I tried making one myself.

Being the genius I am, only having learned one programming language that won't be useful at all, this failed. I can't get it to build and have no idea how GitHub actions work. Also other issues, including possible missing/incorrect directories and values in various files. Since open-source is great, and forking is a thing, I'll put my repo here as a sort of shimmer of hope for anyone desperate for TWRP.

GitHub - CatFishing4Guyz/twrp_device_Samsung_A225G

Contribute to CatFishing4Guyz/twrp_device_Samsung_A225G development by creating an account on GitHub.

github.com

However, if you do become successful, give me most of the credits as well as other people mentioned in the README.md.
[Realme GT Neo 2] Malediktion:
As the title says I'm having trouble when using 4G/5G. All incoming calls are shown as Unknown. When you force 3G/2G only, caller number is displayed normally. Searching google there are many reports with other phones as well having this issue when used with VoLTE and most of them were fixed with software updates. So I contacted my carrier and told them to disable VoLTE from their side. Unfortunatelly I have no slider in Sim settings to disable VoLTE myself.

After VoLTE was disabled from my carrier all incoming calls were displayed normally. It's not the best solution cause I bought this phone specificaly for this reason, to use VoLTE/VoWifi.

I posted the issue on bug tracker of realme as well.

Currently I'm on A.05 version and I have no idea how I could change to another version to test if it would work.

Any help would be appreciated regarding this issue.

PS. I tried factory resetting several times. Clear data/cache of phone/contacts app as well and tried with another dialer.
[Touch Diamond, MDA Compact IV Themes and Apps] nickgeys:
does anyone know how i can make my TD vibrate when i missed an SMS/EMAIL/CALL

(and keep vibrating every 5 minutes or so untill i read the message)

???
[Touch Diamond, MDA Compact IV Themes and Apps] doinbox:
I'm intersted in this too. Is it possible?
[Touch Diamond, MDA Compact IV Themes and Apps] Kal-El:
I am very interested to this. + 1!
[Touch Diamond, MDA Compact IV Themes and Apps] davidgiga:
great idea!

it is possible?
[Touch Diamond, MDA Compact IV Themes and Apps] efex:
Phoneweaver can do this among other things. Google it, its not freeware thou.
[Touch Diamond, MDA Compact IV Themes and Apps] TheDoctor79:
SPB Phone Suite can do this!
[Touch Diamond, MDA Compact IV Themes and Apps] hefman:
Pocketmax PhoneAlarm as well...

I believe all of these are Today plugins, so you'll need something like SecondToday to run them.
[Touch Diamond, MDA Compact IV Themes and Apps] nickgeys:
This looks nice, i'm gonna try this one, THX FOR THE REPLY!!!!
[Touch Diamond, MDA Compact IV Themes and Apps] nickgeys:
damn it phone alarm does not work, my HTC TOUCH DIAMOND already has a today screen so i don't need to install other software right?
[Touch Diamond, MDA Compact IV Themes and Apps] nickgeys:
nevermind i got it working, using secondToday
[Touch Diamond, MDA Compact IV Themes and Apps] nickgeys:
last post;

in the end i'm using alarmPAL, wich is a simplyfied version of phoneAlarm, but i don't need second today to run this...
[Touch Diamond, MDA Compact IV Themes and Apps] Genius2000:
Also you can try one of this application, doesn't do exactly what you need, but it's useful.

Ciao, Andrea