Develop Bugs

Screen Bleeding issue

I am having a screen bleeding issue in my pixel experience rom 11/21
Magisk flashed
nothing else
the screen bleeding does exist in twrp as well
Can anyone tell me the solution ?
P.S.: I'm not allowed to send screenshots being a new member.

Hi,
It's hard to say what's a screen bleed according to your definition without visually see it. You could simply image upload and post the link, you'll get more results.
On the other hand, most standard screen bleeds are HW related so i'm not sure there's anything that can be done...
What FW do you have in your PE rom? (copy the baseband version from settings/ system/about phone/android version /baseband)

htchd2sucks said:
Hi,
It's hard to say what's a screen bleed according to your definition without visually see it. You could simply image upload and post the link, you'll get more results.
On the other hand, most standard screen bleeds are HW related so i'm not sure there's anything that can be done...
What FW do you have in your PE rom? (copy the baseband version from settings/ system/about phone/android version /baseband)
Click to expand...
Click to collapse
Okay ...
My problem on my device , left and right side of the screen is brighter than rest of the screen , it is SW related because it wasn't there on miui .... (I mean the area near the edges )
screenshot -> https://imgur.com/a/OcTYovC
Baseband version -> 660_GEN_PACK-1.164129.0.164270.1
I had miui 10.0.0.4 stable before this
do I need to flash firmware again? from here https://forum.xda-developers.com/redmi-note-5-pro/development/firmware-xiaomi-redmi-note-5-t3766138

DarkLegend_1943 said:
Okay ...
My problem on my device , left and right side of the screen is brighter than rest of the screen , it is SW related because it wasn't there on miui .... (I mean the area near the edges )
screenshot -> https://imgur.com/a/OcTYovC
Baseband version -> 660_GEN_PACK-1.164129.0.164270.1
I had miui 10.0.0.4 stable before this
do I need to flash firmware again? from here https://forum.xda-developers.com/redmi-note-5-pro/development/firmware-xiaomi-redmi-note-5-t3766138
Click to expand...
Click to collapse
Your baseband confirms you have firmware 10.0.0.4 stable, so you have the current latest stable.
I do have similar but I don't have any "screen bleed".
You should not need to flash anything again, it should be fine.
We don't see the screen bleed in the screen capture (which is probably normal), you could take a picture of the phone with another phone, or simply put a mirror a use the front camera.
To be fair, I doubt it's very visible, it might be "your perception", but do take a picture to show the extend.
(especially you have dark mode enabled, did you have that or similar in MIUI?)
In any case, I see your comment that it wasn't on MIUI, but it's rather strange and I never heard of that on PE. Maybe it's something like now your background is darker the the "screen bleed" is more visible or something.

htchd2sucks said:
Your baseband confirms you have firmware 10.0.0.4 stable, so you have the current latest stable.
I do have similar but I don't have any "screen bleed".
You should not need to flash anything again, it should be fine.
We don't see the screen bleed in the screen capture (which is probably normal), you could take a picture of the phone with another phone, or simply put a mirror a use the front camera.
To be fair, I doubt it's very visible, it might be "your perception", but do take a picture to show the extend.
(especially you have dark mode enabled, did you have that or similar in MIUI?)
In any case, I see your comment that it wasn't on MIUI, but it's rather strange and I never heard of that on PE. Maybe it's something like now your background is darker the the "screen bleed" is more visible or something.
Click to expand...
Click to collapse
Here is another picture https://imgur.com/a/Yhh5Kh3
observe closely ....

DarkLegend_1943 said:
Here is another picture https://imgur.com/a/Yhh5Kh3
observe closely ....
Click to expand...
Click to collapse
Hm, is that the "stain" on the bottom left?
Say starting 2cm from bottom left corner, up to 4cm higher?
Hm, you mention it's even in TWRP, which tends to indicate it's not even ROM related...At least not in system.
At this point I'm not sure what is the root cause and I'm not even sure if there's a problem...
You don' t have anything pressuring the screen like a bumper case or something?

htchd2sucks said:
Hm, is that the "stain" on the bottom left?
Say starting 2cm from bottom left corner, up to 4cm higher?
Hm, you mention it's even in TWRP, which tends to indicate it's not even ROM related...At least not in system.
At this point I'm not sure what is the root cause and I'm not even sure if there's a problem...
You don' t have anything pressuring the screen like a bumper case or something?
Click to expand...
Click to collapse
if it was because of the case I would have seen it way before , but will stop using it now !
the stain you see is the tempered glass having air bubble
I guess lcd density is messed up that's why I see something like this , because Ive watched a lot of videos regarding pixel experience , the icon size is comparitively small on my device.
I guess I'll have to go back to miui ...
Kindly tell me your
.TWRP version , Method of installation
(antirbpass dummy.img flash or fastboot boot recovery twrp.img and then flashing twrp )
.Rom that are using
.If I have to go back to miui
tell me the safest method so that I don't end up in bricking.

DarkLegend_1943 said:
if it was because of the case I would have seen it way before , but will stop using it now !
the stain you see is the tempered glass having air bubble
I guess lcd density is messed up that's why I see something like this , because Ive watched a lot of videos regarding pixel experience , the icon size is comparitively small on my device.
I guess I'll have to go back to miui ...
Kindly tell me your
.TWRP version , Method of installation
(antirbpass dummy.img flash or fastboot boot recovery twrp.img and then flashing twrp )
.Rom that are using
.If I have to go back to miui
tell me the safest method so that I don't end up in bricking.
Click to expand...
Click to collapse
https://in.c.mi.com/thread-714161-1-0.html
Seems easier than going through twrp. Although flashing latest miui rom should not trigger arbV4 protection so should not brick anything.

htchd2sucks said:
https://in.c.mi.com/thread-714161-1-0.html
Click to expand...
Click to collapse
I'm using anti 4 so I guess I'll have to flash latest miui 10.0.0.4 ... I'll update you if the problem persists maybe we could come up with the solution!
I had developed roms in gingerbread , I must say that was easiest Android version ??

DarkLegend_1943 said:
I'm using anti 4 so I guess I'll have to flash latest miui 10.0.0.4 ... I'll update you if the problem persists maybe we could come up with the solution!
I had developed roms in gingerbread , I must say that was easiest Android version
Click to expand...
Click to collapse
Yes, lot of things have changed...
By the way, there's a place where you can customize official miui rom, and for example, remove the ads and unwanted features.
The problem is someone posted that here on XDA but forgot the link.
If you want to look around...
I did flash back a MIUI rom from TWRP once, to have encryption again, I think if you want to come back "as MIUI was", the best is miui flash.

htchd2sucks said:
Yes, lot of things have changed...
By the way, there's a place where you can customize official miui rom, and for example, remove the ads and unwanted features.
The problem is someone posted that here on XDA but forgot the link.
If you want to look around...
I did flash back a MIUI rom from TWRP once, to have encryption again, I think if you want to come back "as MIUI was", the best is miui flash.
Click to expand...
Click to collapse
freezing msa will disable adds I guess!

DarkLegend_1943 said:
freezing msa will disable adds I guess!
Click to expand...
Click to collapse
https://mi-globe.com/rom-builder-features/?codename=whyred&img=redminote5pro.png&realname=RedMi+Note+5+Pro
I think that was the link, not entirely sure, I never found it again.
In that link it talks about installing ad blocker. I kind of remember that we could turn off some ads service in the MIUI rom custom thing...
Well that seems a good workaround anyway!
It even have clear instructions from TWRP:
https://mi-globe.com/globerom-rom-builder/

htchd2sucks said:
Yes, lot of things have changed...
By the way, there's a place where you can customize official miui rom, and for example, remove the ads and unwanted features.
The problem is someone posted that here on XDA but forgot the link.
If you want to look around...
I did flash back a MIUI rom from TWRP once, to have encryption again, I think if you want to come back "as MIUI was", the best is miui flash.
Click to expand...
Click to collapse
What's the step I need to flash lazy flasher ?
Don't need to format data ?
Mi flash doesn't read the updater script it does it on its own built in script I guess.....
I need to flash lazy flasher ?

DarkLegend_1943 said:
What's the step I need to flash lazy flasher ?
Don't need to format data ?
Mi flash doesn't read the updater script it does it on its own built in script I guess.....
I need to flash lazy flasher ?
Click to expand...
Click to collapse
No, lazy flasher is for example when you want to force disabling encryption checks.
Format data, I'm not sure, I think it's wiping it anyway during the flash. Nothing related to encryption (especially that MIUI rom will detect non encrypted /data fs and re.encrypt if needed).
Yes, maybe MIFlash only needs MI official roms (to be confirmed).
Maybe you need to wipe though, that i'm not entirely sure. I think a "clean flash" is expected (=wiping).

htchd2sucks said:
No, lazy flasher is for example when you want to force disabling encryption checks.
Format data, I'm not sure, I think it's wiping it anyway during the flash. Nothing related to encryption (especially that MIUI rom will detect non encrypted /data fs and re.encrypt if needed).
Yes, maybe MIFlash only needs MI official roms (to be confirmed).
Maybe you need to wipe though, that i'm not entirely sure. I think a "clean flash" is expected (=wiping).
Click to expand...
Click to collapse
confirmed
It's happening in pie only
I tried flashing linage os 15.1 (no success)
but the bleeding in twrp was gone.

DarkLegend_1943 said:
confirmed
It's happening in pie only
I tried flashing linage os 15.1 (no success)
but the bleeding in twrp was gone.
Click to expand...
Click to collapse
Then you might want to take proper screen illustration and describe your issue in a way that the dev can read it in the PE forum...
Maybe it's related to Derp Kernel, I don't know.
To be fair, others don't have the issue so maybe you have specific hw or pb?
There's an app called AIDA which can help to show you what's your screen manufacturer, it can be useful to post that too!

htchd2sucks said:
Then you might want to take proper screen illustration and describe your issue in a way that the dev can read it in the PE forum...
Maybe it's related to Derp Kernel, I don't know.
To be fair, others don't have the issue so maybe you have specific hw or pb?
There's an app called AIDA which can help to show you what's your screen manufacturer, it can be useful to post that too!
Click to expand...
Click to collapse
pannel is from official vendor

htchd2sucks said:
Then you might want to take proper screen illustration and describe your issue in a way that the dev can read it in the PE forum...
Maybe it's related to Derp Kernel, I don't know.
To be fair, others don't have the issue so maybe you have specific hw or pb?
There's an app called AIDA which can help to show you what's your screen manufacturer, it can be useful to post that too!
Click to expand...
Click to collapse
now facing screen burning ! I'm installing miui today I guess that's the most optimised rom.

Custom ROMs for SM-A505FN/DS, any at all?

all I want is a completely stock version of android, just android and none of the skinned crap I'll do that myself with Evie Launcher, I just want stock android but it seems theres ROMs for every other variant of this phone EXCEPT for the one I have, yes I could have bought a pixel but money and I like the looks of samsungs. is anyone able to help me out here? I've flashed custom roms and rooted all the phones I've had in the past but it seems there is nothing at all for this version of the A50

tripleplug said:
all I want is a completely stock version of android, just android and none of the skinned crap I'll do that myself with Evie Launcher, I just want stock android but it seems theres ROMs for every other variant of this phone EXCEPT for the one I have, yes I could have bought a pixel but money and I like the looks of samsungs. is anyone able to help me out here? I've flashed custom roms and rooted all the phones I've had in the past but it seems there is nothing at all for this version of the A50
Click to expand...
Click to collapse
You have Gsi rom for flashing you need just twrp and plenty of Gsi

muhamet said:
You have Gsi rom for flashing you need just twrp and plenty of Gsi
Click to expand...
Click to collapse
Is it for my exact model of the phone though? I dont want to brick my phone or install stuff that isn't the correct version for the phone I have

tripleplug said:
Is it for my exact model of the phone though? I dont want to brick my phone or install stuff that isn't the correct version for the phone I have
Click to expand...
Click to collapse
Well you have FN model (Europe) i use FN

muhamet said:
Well you have FN model (Europe) i use FN
Click to expand...
Click to collapse
Yeah but on the end of FN it has "/DS" on it, so I dont know if that changes anything

tripleplug said:
Yeah but on the end of FN it has "/DS" on it, so I dont know if that changes anything
Click to expand...
Click to collapse
Yea and I have that model

muhamet said:
Yea and I have that model
Click to expand...
Click to collapse
whaaaaat? so you have a custom rom running on the same device that I have??? I've spent ages tryna find one for my device and I couldn't, either that or I'm just stupid and wasnt reading stuff properly lol

tripleplug said:
whaaaaat? so you have a custom rom running on the same device that I have??? I've spent ages tryna find one for my device and I couldn't, either that or I'm just stupid and wasnt reading stuff properly lol
Click to expand...
Click to collapse
You just need to flash twrp

Ok, I don't get what I am doing wrong. Got twrp 3.3.1.0 in place, I can flash the GSI rom to system. Then it just gets stuck several hours with the google logo and (boot) progress bar. Once 8 hours and once 12+ hours until I decided this wasn't going to work.
It just never gets past the boot logo.

inglorious_bastard said:
Ok, I don't get what I am doing wrong. Got twrp 3.3.1.0 in place, I can flash the GSI rom to system. Then it just gets stuck several hours with the google logo and (boot) progress bar. Once 8 hours and once 12+ hours until I decided this wasn't going to work.
It just never gets past the boot logo.
Click to expand...
Click to collapse
Try a different GSI, for example Havoc OS 3.1. My guess is that you're trying to flash Pixel Experience, or something similar?

Skytex_ said:
Try a different GSI, for example Havoc OS 3.1. My guess is that you're trying to flash Pixel Experience, or something similar?
Click to expand...
Click to collapse
I will give that a try, thanks for pointing out. I have been experimenting with the pixel experience GSI and the resurrection remix GSI which both left me with a phone that didn't boot.

inglorious_bastard said:
I will give that a try, thanks for pointing out. I have been experimenting with the pixel experience GSI and the resurrection remix GSI which both left me with a phone that didn't boot.
Click to expand...
Click to collapse
Flash only Phh source gsi.Dont flash Sgsi,they are oem sgsi.Some will boot,some of them will stay on bootanimation.Gsi with phh source will boot

Tested GSI List for the Nord N10 5G

Decided a list might be nice to have for those interested in flashing GSI Images
All these GSI's I've tested on a BE2026 Lito, but I'd assume its the same for other models. As long as you can unlock bootloader anyway
GSI List
Havok OS
-- Android 10
-- Pros: Reads SIM cards, wifi functions, bluetooth works, camera works, everything works
-- Cons: Once you flash Magisk using custom recovery, it only boots to bootloader, GAPPS won't flash, had to debrick device after this...
/e/OS DeGoogled GSI
-- Android 10
-- Pros: Wifi/Bluetooth/Camera and system work. Magisk flash with custom recovery works
-- Cons: Doesn't read sim cards at all, Screen stays exceptionally bright at all times even at 0% brightness
LeOS DeGoogled GSI
-- Android 10 and Android 11
-- Pros: Same as /e/OS
-- Cons: Same as /e/OS
DotOS GSI
-- Android 11
-- Pros: Not really any lol
-- Cons: Upon initial boot ,screen flashes, System Force Closes, screen is black. Unusable
Android 12 GSI from Google
-- Android 12
-- Never Boots
crDroid GSI
-- Android 11
-- Pros: nothin
-- Cons: have to delete product_a and _b slot partitions to resize for it to function, never boots, kicks you back to bootloader
- currently flashing

Android 12 if it works I also have a list give me time but some roms need permissiver.zip

Huh did not know of that. Know a fix for issues with SIM Card not being seen at all? /e/OS does it to me on every device I flash it to. I've seen people say to flash back to stock then flash an A-Only GSI, sometimes that fixes the SIM issue
EduardoA3677 said:
Android 12 if it works I also have a list give me time but some roms need permissiver.zip
Click to expand...
Click to collapse

KaptinBoxxi said:
Huh did not know of that. Know a fix for issues with SIM Card not being seen at all? /e/OS does it to me on every device I flash it to. I've seen people say to flash back to stock then flash an A-Only GSI, sometimes that fixes the SIM issue
Click to expand...
Click to collapse
It may be a problem with the vendor or kernel, I could compile but my laptop broke down and renting a server is very expensive in my country

KaptinBoxxi said:
Huh did not know of that. Know a fix for issues with SIM Card not being seen at all? /e/OS does it to me on every device I flash it to. I've seen people say to flash back to stock then flash an A-Only GSI, sometimes that fixes the SIM issue
Click to expand...
Click to collapse
Ok, you have telegram, it makes me a bit uncomfortable to write here

EduardoA3677 said:
Ok, you have telegram, it makes me a bit uncomfortable to write here
Click to expand...
Click to collapse
Don't have anything except Discord, Twitter and FB, but I generally only share my discord.
I'm thinking something's just missing from the ROMs, since it works with Havok ROM and such

KaptinBoxxi said:
Don't have anything except Discord, Twitter and FB, but I generally only share my discord.
I'm thinking something's just missing from the ROMs, since it works with Havok ROM and such
Click to expand...
Click to collapse
How did you get HavocOS to boot? This specific image never seems to boot no matter what I do. Did you flash any fixes or did it just boot up first time?

Generic123. said:
How did you get HavocOS to boot? This specific image never seems to boot no matter what I do. Did you flash any fixes or did it just boot up first time?
Click to expand...
Click to collapse
Flash this after installing the gsi

KaptinBoxxi said:
Don't have anything except Discord, Twitter and FB, but I generally only share my discord.
I'm thinking something's just missing from the ROMs, since it works with Havok ROM and such
Click to expand...
Click to collapse
Hi need your help

EduardoA3677 said:
Flash this after installing the gsi
Click to expand...
Click to collapse
Permissiver on this phone for every rom so far just kicks me back to fastboot.

KaptinBoxxi said:
Decided a list might be nice to have for those interested in flashing GSI Images
All these GSI's I've tested on a BE2026 Lito, but I'd assume its the same for other models. As long as you can unlock bootloader anyway
GSI List
Havok OS
-- Android 10
-- Pros: Reads SIM cards, wifi functions, bluetooth works, camera works, everything works
-- Cons: Once you flash Magisk using custom recovery, it only boots to bootloader, GAPPS won't flash, had to debrick device after this...
/e/OS DeGoogled GSI
-- Android 10
-- Pros: Wifi/Bluetooth/Camera and system work. Magisk flash with custom recovery works
-- Cons: Doesn't read sim cards at all, Screen stays exceptionally bright at all times even at 0% brightness
LeOS DeGoogled GSI
-- Android 10 and Android 11
-- Pros: Same as /e/OS
-- Cons: Same as /e/OS
DotOS GSI
-- Android 11
-- Pros: Not really any lol
-- Cons: Upon initial boot ,screen flashes, System Force Closes, screen is black. Unusable
Android 12 GSI from Google
-- Android 12
-- Never Boots
crDroid GSI
-- Android 11
-- Pros: nothin
-- Cons: have to delete product_a and _b slot partitions to resize for it to function, never boots, kicks you back to bootloader
- currently flashing
Click to expand...
Click to collapse
I'm using Corvus 16.7 and everything works just fine EXCEPT connecting a headset or a speaker. I can't do it no matter if I use a cable or via Bluetooth, which is a shame because I use to listen to music that way.
Everything else works fantastic, so I don't have regrets.

bbabel said:
I'm using Corvus 16.7 and everything works just fine EXCEPT connecting a headset or a speaker. I can't do it no matter if I use a cable or via Bluetooth, which is a shame because I use to listen to music that way.
Everything else works fantastic, so I don't have regrets.
Click to expand...
Click to collapse
Ever since the Android 11 update went through, even if I use the debricking Android 10 software to go back, no gsi boots at all. Even GSI's I had that were working.

Yesterday I tested Android 12 AOSP GSI+GMS on my N10 5G. It works, but 90hz needs to be set from adb, biometrics won't work at all (build.prop might need edits) and 5G cannot be enabled. LTE, 3G and 2G works, calls work, WiFi & Bluetooth works, camera works and audio works.
I think that the issue is on build.prop. Also you need to install proper vbmeta.img so it can boot.

UsedNametag said:
Yesterday I tested Android 12 AOSP GSI+GMS on my N10 5G. It works, but 90hz needs to be set from adb, biometrics won't work at all (build.prop might need edits) and 5G cannot be enabled. LTE, 3G and 2G works, calls work, WiFi & Bluetooth works, camera works and audio works.
I think that the issue is on build.prop. Also you need to install proper vbmeta.img so it can boot.
Click to expand...
Click to collapse
I've had this bookmarked for when I had my laptop working.
https://developer.android.com/topic/dsu
Seems we have the ability to add gsi images and everything.

I'll try Pixel 5 Android 12 Beta 4.1 firmware GSI port too, maybe more stuff works.

UsedNametag said:
Yesterday I tested Android 12 AOSP GSI+GMS on my N10 5G. It works, but 90hz needs to be set from adb, biometrics won't work at all (build.prop might need edits) and 5G cannot be enabled. LTE, 3G and 2G works, calls work, WiFi & Bluetooth works, camera works and audio works.
I think that the issue is on build.prop. Also you need to install proper vbmeta.img so it can boot.
Click to expand...
Click to collapse
Did you use the DSU or did you install something using this method?

MetaruSonikkuX said:
Did you use the DSU or did you install something using this method?
Click to expand...
Click to collapse
I used GSI installation tutorial from this forum. Also issues on GSI might be possible to solve, but I have no idea how...

I've totally forgotten to update about my GSI experience on this phone. Pixel 5 port didn't work properly, but I haven't tried any Phh-Treble images yet.

a(11)-a(12) gsi+gms dsu loader worked fine (its the 'easy' button for flashing)on N10 5G (w/unlocked bootloader).but i noticed my storage space was reduced to like 8 or 9gb,(tryin to recall but i flashed back as soon i saw it).and then almost corupted my sd card.. or it misread it. cant remember if it wiped my phone(it was already wiped)or id just flash back over,but setting up phone again and again sucks.man,i got the memory of a goldfish

limitlessbydesi9n said:
a(11)-a(12) gsi+gms dsu loader worked fine (its the 'easy' button for flashing)on N10 5G (w/unlocked bootloader).but i noticed my storage space was reduced to like 8 or 9gb,(tryin to recall but i flashed back as soon i saw it).and then almost corupted my sd card.. or it misread it. cant remember if it wiped my phone(it was already wiped)or id just flash back over,but setting up phone again and again sucks.man,i got the memory of a goldfish
Click to expand...
Click to collapse
Hm I might have to try this out out of boredom. Mind sharing where you found dsy loader? Never heard of it is it specifically for the N10 5g or just a global tool? Oh yeaahhh, I'd also say my memories are about the same. It's from all that reefer mann.

Question [FIXED] Has one of you been able to disable /data Encryption on the Poco F3?

This isn't an urgent question. Has one of you been able to disable the forced /data encryption on the Poco F3?
I'm curious, because I've tried it many times in the past with multiple ways, to no success.
Edit: This works!: https://forum.xda-developers.com/t/...e-for-poco-f3-alioth-decryption-data.4317277/

Again out of curiosity and without rushing, what would be the benefit of removing encryption?

pegasoc said:
Again out of curiosity and without rushing, what would be the benefit of removing encryption?
Click to expand...
Click to collapse
Probably because any custom recovery needs to read /data partition without the encryption.
My old Xiaomi Mi8 and Mi11 have this problem.
dreamytom said:
This isn't an urgent question. Has one of you been able to disable the forced /data encryption on the Poco F3?
I'm curious, because I've tried it many times in the past with multiple ways, to no success.
Edit: I found a guide, will try: https://forum.xda-developers.com/t/...-decryption-data.4317277/page-2#post-85514117
Click to expand...
Click to collapse
Yes, you need to Format Data (not Wipe) and delete everythings on your device so. [ndr. TWRP offers this way easily]
Of course I suggest you to put a ROM via adb or USB to flash it suddenly after the format.
That's because format the Internal Storage produces No OS Installed error, of course.
Other than that, flash dm-verity and force-no encryption if your Xiaomi device has it.

pegasoc said:
Again out of curiosity and without rushing, what would be the benefit of removing encryption?
Click to expand...
Click to collapse
-Slight speed improvements
-Better for Power-users (or shall I say Superusers ;D) who constantly do mods
-Less problems in potentially buggy environments outside of Android (like a Custom Recovery)
zSyntex said:
Probably because any custom recovery needs to read /data partition without the encryption.
My old Xiaomi Mi8 and Mi11 have this problem.
Yes, you need to Format Data (not Wipe) and delete everythings on your device so. [ndr. TWRP offers this way easily]
Of course I suggest you to put a ROM via adb or USB to flash it suddenly after the format.
That's because format the Internal Storage produces No OS Installed error, of course.
Other than that, flash dm-verity and force-no encryption if your Xiaomi device has it.
Click to expand...
Click to collapse
Have you tried this for yourself? That doesn't work for the Poco F3. That's why I'm mentioning "for the Poco F3".
I'll try the guide I linked above, this afternoon.

dreamytom said:
-Slight speed improvements
-Better for Power-users (or shall I say Superusers ;D) who constantly do mods
-Less problems in potentially buggy environments outside of Android (like a Custom Recovery)
Have you tried this for yourself? That doesn't work for the Poco F3. That's why I'm mentioning "for the Poco F3".
I'll try the guide I linked above, this afternoon.
Click to expand...
Click to collapse
I tried with old Xiaomi Mi8, Poco F1 and F2 Pro (of my family) and Mi11.
Same hardware, same OS and methods. I don't think Poco F3 is different from them.
In fact, a lot of users of this device modded it witouth any problem.
Only problem is that you could lost, most probably, the DRMs apps like Home Banking (in Italy work without problems) and Netflix/Amazon Prime HD. Are you concerned about that, right?

zSyntex said:
I tried with old Xiaomi Mi8, Poco F1 and F2 Pro (of my family) and Mi11.
Same hardware, same OS and methods. I don't think Poco F3 is different from them.
In fact, a lot of users of this device modded it witouth any problem.
Only problem is that you could lost, most probably, the DRMs apps like Home Banking (in Italy work without problems) and Netflix/Amazon Prime HD. Are you concerned about that, right?
Click to expand...
Click to collapse
Poco F3 is different than those devices.
I'm not concerned about anything, just would like to not have encryption. I don't need it.
It's like forcing people to use BitLocker on Windows...

dreamytom said:
Poco F3 is different than those devices.
I'm not concerned about anything, just would like to not have encryption. I don't need it.
It's like forcing people to use BitLocker on Windows...
Click to expand...
Click to collapse
Well, is not different. They're all Qualcomm based, all with the same re-partition and OS.
F2 Pro, F3 and Mi11 are on the same set of Xiaomi haha.
Maybe you're new in modding, but trust me or everyone else on this forum.
For encryption, well every device above Android 7 or 8 have it of default, Google force them with the kernel, too.

zSyntex said:
Well, is not different. They're all Qualcomm based, all with the same re-partition and OS.
F2 Pro, F3 and Mi11 are on the same set of Xiaomi haha.
Maybe you're new in modding, but trust me or everyone else on this forum.
For encryption, well every device above Android 7 or 8 have it of default, Google force them with the kernel, too.
Click to expand...
Click to collapse
Bruh.

zSyntex said:
Well, is not different. They're all Qualcomm based, all with the same re-partition and OS.
F2 Pro, F3 and Mi11 are on the same set of Xiaomi haha.
Maybe you're new in modding, but trust me or everyone else on this forum.
For encryption, well every device above Android 7 or 8 have it of default, Google force them with the kernel, too.
Click to expand...
Click to collapse
Instead of lowkey calling me stupid, try it out for yourself.
Disabling Encryption does, not, work, per the usual methods on the Poco F3.
Unlike the phones you mentioned, the Poco F3 launched with Android 11 and a read-only /system.
And problems with banking apps and Netflix etc don't have anything to do with Encryption, but with SafetyNet.

dreamytom said:
This isn't an urgent question. Has one of you been able to disable the forced /data encryption on the Poco F3?
I'm curious, because I've tried it many times in the past with multiple ways, to no success.
Edit: I found a guide, will try: https://forum.xda-developers.com/t/...-decryption-data.4317277/page-2#post-85514117
Click to expand...
Click to collapse
yep there is a zip that helps disable encryption and works flawlessly, tho you need to format once after flashing it after that you can switch between roms only by wiping data. tried it on multiple roms now except hentai os, There's an xda thread on it as well ill link it ere a

m0lly. said:
yep there is a zip that helps disable encryption and works flawlessly, tho you need to format once after flashing it after that you can switch between roms only by wiping data. tried it on multiple roms now except hentai os, There's an xda thread on it as well ill link it ere a
Click to expand...
Click to collapse
disable force encryption(DFE) for Poco F3(alioth) decryption Data
decryptionData I have simplified patching for the end user as much as possible at the moment. Instructions for ROMs based on MIUI (TWRP) 1. Flash ROM_MIUI.zip 2. Flash DFE_BETA_2.zip. Follow the instructions sent to the TWRP display. 3. If you...
forum.xda-developers.com
ere ye go
he's got a tg group too. join ere too everything is explained in detail.

Thank you! I found that one as well right after I made my post. I will try it now, since at 10 pm afternoon no one is gonna call me lol

dreamytom said:
Thank you! I found that one as well right after I made my post. I will try it now, since at 10 pm afternoon no one is gonna call me lol
Click to expand...
Click to collapse
Did you try the actual fix proposed by the script author in comments?
Boot Android , run script from inside running Android and then later fastboot flash the super image that you get as output?
I was looking at it this morning lmao , I'm really curious how the fk there's such a huge coincidence for me too see your post later the same day...
I don't trust the script developer that wrote the Poco f3 thread... I am not knowledgeable enough to know where to look inside his script and see if there's any malicious code or something so I think going with what's written inside comments is the safer bet.
If you decide to go that route share with us how it went ! I'm not comfortable enough to try it just yet...

Rstment ^m^ said:
Did you try the actual fix proposed by the script author in comments?
Boot Android , run script from inside running Android and then later fastboot flash the super image that you get as output?
I was looking at it this morning lmao , I'm really curious how the fk there's such a huge coincidence for me too see your post later the same day...
I don't trust the script developer that wrote the Poco f3 thread... I am not knowledgeable enough to know where to look inside his script and see if there's any malicious code or something so I think going with what's written inside comments is the safer bet.
If you decide to go that route share with us how it went ! I'm not comfortable enough to try it just yet...
Click to expand...
Click to collapse
You mean system_rw flashable?
Yes, I did try it many months ago with an older version! I don't remember the details, but I had 2 errors while trying to flash it. The first error I somehow fixed, but the second error, I couldn't around it... I have also tried to make system read-write manually by using his instructions, but that hadn't worked out either.
I'm now formatting data and trying out the link (it looks very promising!). It also has a video guide.
After that, I'll try out "MiuiVn" and see what that MIUI Custom ROM has to offer.

dreamytom said:
You mean system_rw flashable?
Yes, I did try it many months ago with an older version! I don't remember the details, but I had 2 errors while trying to flash it. The first error I somehow fixed, but the second error, I couldn't around it... I have also tried to make system read-write manually by using his instructions, but that hadn't worked out either.
I'm now formatting data and trying out the link (it looks very promising!). It also has a video guide.
After that, I'll try out "MiuiVn" and see what that MIUI Custom ROM has to offer.
Click to expand...
Click to collapse
Nothing much... You have everything inside miui beta global + it's much more stable than custom ROM from some random Devs
I was referring to this comment :
This installation error can be avoided if /data is decrypted and mounted properly. Apparently some recoveries still have trouble doing that... This error doesn't happen if script is launched from within Android because /data partition is decrypted/mounted properly in Android.
Before running SystemRW script you can check free space in /data partition using this command in terminal:
df -h
You need at least 10+ GB to run the script properly.
I think you need to do a full boot into Android operating system as soon as you flashed a new ROM for the device to become fully operational. Maybe that's why /data partition is not mounted properly in recovery?
Maybe in next version of script I should use this path as project path:
/data/systemrw_1.32b
What do you think?
__________
If you check his original post there are instructions on how to manually flash.

@Rstment ^m^ The link @m0lly. and I mentioned works!
The script by @LeeGarChat worked flawlessly!

Question Touchscreen not working

Hi, recently I got this a32 from a friend because my phone is broken, but there's a problem. Some time ago she updated this phone from android 11 to 12 and the touchscreen completely stopped working, i got the phone yesterday hoping to fix this problem but i updated to android 13 (oneui 5.1) and it still doesnt work, i tried do downgrade to android 11 but its impossible and for last i tried to install twrp and then a gsi (following a guide here on the forum), i noticed that in twrp the touchscreen does actually work but after installing lineage os 20 it didn't again, is there any hope for this phone?

persifele said:
Hi, recently I got this a32 from a friend because my phone is broken, but there's a problem. Some time ago she updated this phone from android 11 to 12 and the touchscreen completely stopped working, i got the phone yesterday hoping to fix this problem but i updated to android 13 (oneui 5.1) and it still doesnt work, i tried do downgrade to android 11 but its impossible and for last i tried to install twrp and then a gsi (following a guide here on the forum), i noticed that in twrp the touchscreen does actually work but after installing lineage os 20 it didn't again, is there any hope for this phone?
Click to expand...
Click to collapse
Did you contacted the assistance? Seems a bad driver or kernel problem.

zSyntex said:
Did you contacted the assistance? Seems a bad driver or kernel problem.
Click to expand...
Click to collapse
no because i dont know how much it would cost and the phone isnt mine either so if possible i dont want to spend money

persifele said:
no because i dont know how much it would cost and the phone isnt mine either so if possible i dont want to spend money
Click to expand...
Click to collapse
We couldn't provide support for the hardware, mostly because you said that you've tried to reset the device and flash the stock ROM again.
If this doesn't fix the hardware issue, the assistance is the only way.
Probably a failure batch etc.

to be completely honest i flashed the stock rom by a backup i did before flashing lineage os, so if there's a guide on how to flash one ui 5.1 in order to have a clean installation it would be rlly helpful

persifele said:
to be completely honest i flashed the stock rom by a backup i did before flashing lineage os, so if there's a guide on how to flash one ui 5.1 in order to have a clean installation it would be rlly helpful
Click to expand...
Click to collapse
Simply download the latest firmware from SamLoader (Bifrost) and use Odin in order to flash it.
Tell me if you couldn't flash

I tried installing the latest firmware with odin, everything went fine but nothing, touch still doesn't work, i think tomorrow i'll take it to someone to fix it.

persifele said:
Hi, recently I got this a32 from a friend because my phone is broken, but there's a problem. Some time ago she updated this phone from android 11 to 12 and the touchscreen completely stopped working, i got the phone yesterday hoping to fix this problem but i updated to android 13 (oneui 5.1) and it still doesnt work, i tried do downgrade to android 11 but its impossible and for last i tried to install twrp and then a gsi (following a guide here on the forum), i noticed that in twrp the touchscreen does actually work but after installing lineage os 20 it didn't again, is there any hope for this phone?
Click to expand...
Click to collapse
what model of a32 is it? SM-A325F or??
One ui 5.1 firmware cannot be downgraded. I currently daily drive crdroid from nazim on one ui 5.1 firmware. my touch has never had issues. May be a hardware issue. Maybe a custom kernel would solve it. I built one for A325F that works on one ui 5.1 firmware. Give it a try from here. Its permissive btw. Just flash it in twrp. Although take a backup of boot before flashing incase something goes wrong

Captain_cookie_200 said:
what model of a32 is it? SM-A325F or??
One ui 5.1 firmware cannot be downgraded. I currently daily drive crdroid from nazim on one ui 5.1 firmware. my touch has never had issues. May be a hardware issue. Maybe a custom kernel would solve it. I built one for A325F that works on one ui 5.1 firmware. Give it a try from here. Its permissive btw. Just flash it in twrp. Although take a backup of boot before flashing incase something goes wrong
Click to expand...
Click to collapse
Hi, I tried to flash from twrp but it just gives me a series of "unable to unlock /dev/block/mmcblk0p14" and so on, btw yes its a A325F.

persifele said:
Hi, I tried to flash from twrp but it just gives me a series of "unable to unlock /dev/block/mmcblk0p14" and so on, btw yes its a A325F.
Click to expand...
Click to collapse
its fine. those are normal. if the flash suceeds at last that is all that matters

Captain_cookie_200 said:
its fine. those are normal. if the flash suceeds at last that is all that matters
Click to expand...
Click to collapse
The problem is that after flashing it goes in a bootloop where it says that "this phone's bootloader is unlocked, press power button" i do it and it starts the galaxy logo with above the writing "the software you are using isnt official, you may have problems with security and features" and it gets stuck there, rn i flashed the original firmware with odin and the phone is working but touch still isn't.
EDIT: i forgot to add that when i flashed with odin everything was going fine until the phone's screen went from green to red, i've never seen this so idk if i should be worried or not (phone is still running normally).

persifele said:
The problem is that after flashing it goes in a bootloop where it says that "this phone's bootloader is unlocked, press power button" i do it and it starts the galaxy logo with above the writing "the software you are using isnt official, you may have problems with security and features" and it gets stuck there, rn i flashed the original firmware with odin and the phone is working but touch still isn't.
EDIT: i forgot to add that when i flashed with odin everything was going fine until the phone's screen went from green to red, i've never seen this so idk if i should be worried or not (phone is still running normally).
Click to expand...
Click to collapse
oh weird . you are using one ui 5.1 right? whats the firmware name or version. Also those things def look like hardware issue. you should get it checked.

Captain_cookie_200 said:
oh weird . you are using one ui 5.1 right? whats the firmware name or version. Also those things def look like hardware issue. you should get it checked.
Click to expand...
Click to collapse
yes i'm on android 13 one ui 5.1, the firmware is A325FXXU3DWB8_A325FOXM3DWB8_ITV. I got it checked and they said that it cant be fixed because i cant downgrade from android 13 to another one, i could try installing crdroid like you and if you could send me a guide it would be amazing, thanks again.

persifele said:
yes i'm on android 13 one ui 5.1, the firmware is A325FXXU3DWB8_A325FOXM3DWB8_ITV. I got it checked and they said that it cant be fixed because i cant downgrade from android 13 to another one, i could try installing crdroid like you and if you could send me a guide it would be amazing, thanks again.
Click to expand...
Click to collapse
Just flash twrp for this thing from here. Follow steps on that thread to decrypt your storage and stuff. Then download crdroid gsi. Extract it. flash img file to system partition in twrp. Afterwards wipe dalvik, cache, internal storage
(internal storage is not necessary). You should be able to boot into twrp sucessfully.
I also have some workarounds and the stuff i use for my daily driving in this thread here.
If you need any further help i'll be here to assist.

Captain_cookie_200 said:
Just flash twrp for this thing from here. Follow steps on that thread to decrypt your storage and stuff. Then download crdroid gsi. Extract it. flash img file to system partition in twrp. Afterwards wipe dalvik, cache, internal storage
(internal storage is not necessary). You should be able to boot into twrp sucessfully.
I also have some workarounds and the stuff i use for my daily driving in this thread here.
If you need any further help i'll be here to assist.
Click to expand...
Click to collapse
Oh um i am sorry looks like thread doesnt contain instructions to that. I'll write em here myself
When you boot into twrp after flashing go to advanced and go to terminal
type
multidisabler
run it two times. Then go to format. Then press format data and type yes. Once its done reboot back into twrp again. Then flash crdroid as i said in my post above. and format the things i said. you should be able to boot into crdroid normally.

Captain_cookie_200 said:
Oh um i am sorry looks like thread doesnt contain instructions to that. I'll write em here myself
When you boot into twrp after flashing go to advanced and go to terminal
type
multidisabler
run it two times. Then go to format. Then press format data and type yes. Once its done reboot back into twrp again. Then flash crdroid as i said in my post above. and format the things i said. you should be able to boot into crdroid normally.
Click to expand...
Click to collapse
I followed everything you said, flashed crdroid but nothing, touch still doesnt work if not for when im twrp, i tried to flash kernel again and it still didn't so i don't know what to do anymore.

persifele said:
I followed everything you said, flashed crdroid but nothing, touch still doesnt work if not for when im twrp, i tried to flash kernel again and it still didn't so i don't know what to do anymore.
Click to expand...
Click to collapse
So uh looks like you have no options left. I just want to make sure. could you list the exact methods you used to flash the fw. Along with where u got the fw from? Lets see if the fw itself is broken or something.
Also this is very unrelated and time wasting. but you could try download one ui 5 firmware. Then extract super.img from ap. unsparse it and extract vendor.img and flash it to vendor partition using twrp. Then decrypt by typing
multidisabler twice in terminal as said in my previous post. Check if maybe an older version one ui 5 firmware has this issue fixed. one ui 5's kernel boots so one ui 5 vendor should work on 5.1 as well. It may not work but worth a try. you could also try doing this with android 12 firmware if that fixes it. if you do not have a linux machine availible i'll do it for you and upload the files for both firmwares here. Otherwise if its a hardware issue get your phone replaced or try getting the screen replaced. if still nothing happens ig switching to a new phone would be the only optiion.

So, to flash the firmware I used odin, the fw was from sammobile.
For trying to extract super.img and so on idk how to actually do it so if you could explain it would be really helpful. Btw trying to flash android 12 firmware is impossible because samsung made it so,
thank you again for the help.

persifele said:
So, to flash the firmware I used odin, the fw was from sammobile.
For trying to extract super.img and so on idk how to actually do it so if you could explain it would be really helpful. Btw trying to flash android 12 firmware is impossible because samsung made it so,
thank you again for the help.
Click to expand...
Click to collapse
i use samfw mostly for my firmwares. anyways. You need a linux machine nearby. ubuntu or arch. any distro based on them would work.
first you need to unsparse the super.img
for that we use
simg2img super.img super-raw.img
then we can use lpunpack or mount it to get our vendor.
we flash it using twrp and then we run multidisabler twice like we did when we first flashed gsi.

As you said above if you could do it for me it'd be awesome because i don't have a pc with linux rn.