Develop Bugs

Lineage OS on A2 lite?

Is it possibleto flash the Lineage treble rom to mi A2 lite?

I still didn't tried this (I must search for a spare phone to use while experimenting with daisy) but you can precede me, simply reset your phone and flash via fastboot with
Code:
fastboot flash system lineagetreblerom.img
You must use the A/B image type.
If something goes wrong you can flash the stock firmware.

BubuXP said:
I still didn't tried this (I must search for a spare phone to use while experimenting with daisy) but you can precede me, simply reset your phone and flash via fastboot with
Code:
fastboot flash system lineagetreblerom.img
You must use the A/B image type.
If something goes wrong you can flash the stock firmware.
Click to expand...
Click to collapse
As far as i understood treble, it is only the vendor partition which is not flashed. So you would still need a LOS compatible kernel to flash (or you are lucky and the original kernel works). Also, LOS needs to be adjusted for specific things on this phone (like resolution, dpi, options to show up in settings, avaiable ram/storage, etc).
So we have to wait until xiaomi or a proper dev releases a kernel source. It would probably also be possible to adjust the build environment to fit the original kernel.
Or did i understand sth wrong here?
edit:
Flashing GSI's should work, it is a nice way to have another rom with more features on the device, but it is not a homebuilt n optimized rom (probably similar perf/battery to stock).

treble gsi rom don't need the vendor partition that's what makes treble great . you just flash the gsi rom into system on a treble compatible device

Hi
sgi ab images works (does not handle well rounded corners as icons are a bit near corners) but works

lineage booted. I will test and report
Both Lineage and RR boots but they are laggy. Camera quality is quite bad.
Both can be used as daily drivers
*can not handle well rounded corners as max-232 said

BubuXP said:
I still didn't tried this (I must search for a spare phone to use while experimenting with daisy) but you can precede me, simply reset your phone and flash via fastboot with
Code:
fastboot flash system lineagetreblerom.img
You must use the A/B image type.
If something goes wrong you can flash the stock firmware.
Click to expand...
Click to collapse
fastboot erase system
fastboot -u flash system name_of_system.img

The Xiaomi MI A2 Lite stock comes compatible with treble, has it been tested with an image of Androoid 9?

menphis said:
The Xiaomi MI A2 Lite stock comes compatible with treble, has it been tested with an image of Androoid 9?
Click to expand...
Click to collapse
yes, I did before.
it booted, but the sgi I used needs a lot of work, many things didn't work.
but, yes, I confirm, it booted

max-232 said:
yes, I did before.
it booted, but the sgi I used needs a lot of work, many things didn't work.
but, yes, I confirm, it booted
Click to expand...
Click to collapse
What SGI you use?

forum.xda-developers.com/project-treble/trebleenabled-device-development/aosp-9-0-phh-treble-t3831915
This above

max-232 said:
yes, I did before.
it booted, but the sgi I used needs a lot of work, many things didn't work.
but, yes, I confirm, it booted
Click to expand...
Click to collapse
max-232 said:
forum.xda-developers.com/project-treble/trebleenabled-device-development/aosp-9-0-phh-treble-t3831915
This above
Click to expand...
Click to collapse
I recently received my A2 Lite, because you do not test the next one that is more stable, as everything works: https://androidfilehost.com/?fid=5862345805528067642
All the files:
https://androidfilehost.com/?w=files&flid=280192

How can flash these post zips with out twrp?

I really hope we get more going ons here it's dead and i cant stand android one if nothing happens soon im going to sell this phone.

mortmaru said:
I really hope we get more going ons here it's dead and i cant stand android one if nothing happens soon im going to sell this phone.
Click to expand...
Click to collapse
I don't think what happening right now is dead, it is still very active and you can flash Lineage or RR if you want
For a few weeks old phone, i consider this as reasonable

mortmaru said:
I really hope we get more going ons here it's dead and i cant stand android one if nothing happens soon im going to sell this phone.
Click to expand...
Click to collapse
This device is new, barely has a month that went on the market, also comes with factory Oreo, also Android 9 came out a few days ago official ...
What development do you need urgently?

menphis said:
This device is new, barely has a month that went on the market, also comes with factory Oreo, also Android 9 came out a few days ago official ...
What development do you need urgently?
Click to expand...
Click to collapse
Some custom roms the base version is awful it is missing so much you cant even backup all stuff from miui to this even app data doesn't transfer over using googles so called backup
With it being month old i expected modded versions even if it was based on the current andriod one loaded with new look bunch of extra options

Can anyone confirm if on AOSP/LOS systems notification LED od still single color (white only)?

Doman said:
Can anyone confirm if on AOSP/LOS systems notification LED od still single color (white only)?
Click to expand...
Click to collapse
It's impossible to have other colors on mi a2, as the phisical LED is only white, not rgb

Another month passes and still nothing.
Hopefully some one will come up with something soon even the official updates for this phone are really slow

"Phone is starting" Magisk bug on most custom ROMs

Hello, I have this weird bug, after a reboot I always get this message. It seems to appear only when flashing magisk, had this issue on LineageOS, CRdroid and AICP.
Only fix is to reboot again until the message is gone.
Also I flashed magisk after phone setup.
Does anybody know a solution, it seems that this happened to more people across the ROM threads but no reports in the magisk tread.

Don't use Magisk 18.1 as of now. Flash Magisk 18.0.

bravonova said:
Don't use Magisk 18.1 as of now. Flash Magisk 18.0.
Click to expand...
Click to collapse
Tried Magisk 18.0 on LineageOS, still get the message.

I have a work around for it. Extract the boot.img file from your ROMs zip file. Transfer it to you phone. Then open magisk manager and tap install, and then install again. Then select the Patch Boot Image File option. Select the extracted boot.img file and let magisk do it's business. After it's done it will save the file as patch_boot.img. Next time you flash your ROM, or upgrade or simply get stuck, reboot into recovery. Then select install and then select image file. Select the patch_boot.img file and flash it as your boot Image. Reboot and everything should be fine.
It's a but annoying but that's what works for me 100% of the time.

dsahai said:
I have a work around for it. Extract the boot.img file from your ROMs zip file. Transfer it to you phone. Then open magisk manager and tap install, and then install again. Then select the Patch Boot Image File option. Select the extracted boot.img file and let magisk do it's business. After it's done it will save the file as patch_boot.img. Next time you flash your ROM, or upgrade or simply get stuck, reboot into recovery. Then select install and then select image file. Select the patch_boot.img file and flash it as your boot Image. Reboot and everything should be fine.
It's a but annoying but that's what works for me 100% of the time.
Click to expand...
Click to collapse
Thanks man, I will try it:laugh:
Does this mean I can flash the ROM, set it up and flash the patched boot.img and this bug should not reappear?

Mr. Cube said:
Thanks man, I will try it:laugh:
Does this mean I can flash the ROM, set it up and flash the patched boot.img and this bug should not reappear?
Click to expand...
Click to collapse
I guess
Whenever I get stuck in the "Phone is starting", I just reboot into recovery and flash the patch_boot.img and it seems to fix the issue The bug may reappear if you flash some Magisk modules, or update. So just keep that img file ready.

bravonova said:
Don't use Magisk 18.1 as of now. Flash Magisk 18.0.
Click to expand...
Click to collapse
I've flashed 18.0, then I updated through the Manger to 18.1 and working great!

TRY Magisk 18.2
https://forum.xda-developers.com/on...l-twrp-xposed-framework-t3910141#post79103367

DoR3M3 said:
I've flashed 18.0, then I updated through the Manger to 18.1 and working great!
Click to expand...
Click to collapse
I tried Magisk 18.0 but got the "phone is starting" bug four times in a row, than I gave up.
Strangely this also happens on OOS to me but there it disappears 10 seconds after boot

Mr. Cube said:
I tried Magisk 18.0 but got the "phone is starting" bug four times in a row, than I gave up.
Strangely this also happens on OOS to me but there it disappears 10 seconds after boot
Click to expand...
Click to collapse
I've been using 18.0 on OOS 5.1.7 and my ROM OOS[microG] which is OOS 5.1.7 and no problems ever...
I'd say install 17.1 then upgrade from there and see how it goes, and you can also try "Canary" Branch of Magisk and might have better luck with it...
https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337

If Magisk is a cause, it's not the only cause. I don't use Magisk but get the bug on both my OP3T and OP5 running crDroid. I've also seen it reported on Official LOS. Still looking for common factors, but it might be VPN related. Does anyone here use one? Could be a problem with 3rd Party Launchers. What is everyone using? The only logcat information we have to go on so far is:
Code:
03-13 14:44:37.070 1324 2483 W ActivityManager: Service.startForeground() not allowed due to bg restriction: service com.nordvpn.android/de.blinkt.openvpn.core.OpenVPNService
https://forum.xda-developers.com/showpost.php?p=79109320&postcount=492
There's the possibility that it's just a sporadic bug that could happen to anyone at any time. Could just be a gerenic way of saying "phone ran into something it didn't like during boot" I've only seen reports of this on Pie. Only had it myself on Pie.
The best thing we can do is to get a logcat when it happens. Providing you're in front of your PC, have USB Debugging enabled, and can connect to ADB while the phone is stuck on 'Phone Is Starting', running
adb logcat -d > logcat.txt. should work. (Correct the syntax if i've got that wrong)

I had this problem also on my 5T and got rid of it by using magisk uninstaller. I had this problem on MSM Extended AND crDroid, both the latest versions. I do not use any VPN-apps, but I do use a custom launcher, in my case thats Nova premium.

Are you trying to unlock your phone via fingerprint? For me, the behaviour is consistent: on boot, after entering SIM PIN, try to unlock phone with fingerprint, which leads to unclock code entry as this is the first boot and you need to enter your code. Enter code, and "Phone is starting". If, instead, after entering the SIM PIN, without touching the fingerprint sensor in any way, I manually swipe and enter the unlock code, the phone starts, no problem. Tested repeatedly.
If anyone has any idea where to report this bug, I'll gladly do so, but since apparently it isn't tied to Magisk, nor a specific ROM, I have no clue.

Dirk said:
If Magisk is a cause, it's not the only cause. I don't use Magisk but get the bug on both my OP3T and OP5 running crDroid. I've also seen it reported on Official LOS. Still looking for common factors, but it might be VPN related. Does anyone here use one? Could be a problem with 3rd Party Launchers. What is everyone using? The only logcat information we have to go on so far is:
https://forum.xda-developers.com/showpost.php?p=79109320&postcount=492
There's the possibility that it's just a sporadic bug that could happen to anyone at any time. Could just be a gerenic way of saying "phone ran into something it didn't like during boot" I've only seen reports of this on Pie. Only had it myself on Pie.
The best thing we can do is to get a logcat when it happens. Providing you're in front of your PC, have USB Debugging enabled, and can connect to ADB while the phone is stuck on 'Phone Is Starting', running
adb logcat -d > logcat.txt. should work. (Correct the syntax if i've got that wrong)
Click to expand...
Click to collapse
I'm not sure if it's magisk related but for me the only workaround to get it working again is the solution mentioned by @dsahai. When I flash the patched_boot.img it works again.
Also, I don't use any VPN service but a 3rd party launcher.
I will try to take a log on next reboot and report it to the LOS dev. :silly:

Mr. Cube said:
Also, I don't use any VPN service but a 3rd party launcher.
I will try to take a log on next reboot and report it to the LOS dev. :silly:
Click to expand...
Click to collapse
I use a 3rd party launcher too. The only reason i mention it is because the point where the 'phone is starting' message freezes the phone is at the point where the launcher loads. (or fails to load, which is more accurate to say). Of course everything else is trying to load at that point too so it might just be coincidence.

@Dirk
Someone has made a patch trying to fix the phone is starting bug
Just flash the fix-phone-is starting.zip in twrp and reboot
If it does not work, just flash the restore.zip
you can join op5/t official tg group to give your feedback
https://t.me/joinchat/GQS-ghNaf-1YMpjSbh_puQ

huluhola said:
@Dirk
Someone has made a patch trying to fix the phone is starting bug
Just flash the fix-phone-is starting.zip in twrp and reboot
If it does not work, just flash the restore.zip
you can join op5/t official tg group to give your feedback
https://t.me/joinchat/GQS-ghNaf-1YMpjSbh_puQ
Click to expand...
Click to collapse
That's interesting. Someone must think they've found the problem. What do we know about this?
On crDroid for the OP5 there's something in the latest build that's supposed to be a fix too. I assume it's the same changes. I haven't tried that new build yet so i'm happy to try the zip if it's okay to flash on the OP5?

Dirk said:
That's interesting. Someone must think they've found the problem. What do we know about this?
On crDroid for the OP5 there's something in the latest build that's supposed to be a fix too. I assume it's the same changes. I haven't tried that new build yet so i'm happy to try the zip if it's okay to flash on the OP5?
Click to expand...
Click to collapse
Just flash the fix.zip on ur op5
don't worry u can flash the restore.zip if it doesn't work

huluhola said:
Just flash the fix.zip on ur op5
don't worry u can flash the restore.zip if it doesn't work
Click to expand...
Click to collapse
Thanks.
It's infrequent for me. Perhaps once in a dozen or more reboots. Could be a while before i could say definitively that it's helped, but i'll try it and see. :good:

huluhola said:
@Dirk
Someone has made a patch trying to fix the phone is starting bug
Just flash the fix-phone-is starting.zip in twrp and reboot
If it does not work, just flash the restore.zip
you can join op5/t official tg group to give your feedback
https://t.me/joinchat/GQS-ghNaf-1YMpjSbh_puQ
Click to expand...
Click to collapse
I dont use Telegram. Can you keep us updated here with any news from this Patch? Has anybody reported anything yet?

[ROM][UNOFFICIAL][W.I.P]LineageOS for Redmi Note 9S/9Pro[curtana/joyeuse]

tldr; use the LeddaZ build
Downloads:
ROM
Lineage Recovery
Hello XDA,
I'm posting a build using the unified curtana build code that's on github. I have a joyeuse (9 Pro) so I can't really test it on the 9S (curtana). I've been testing it out for a couple of days and haven't had any bugs other than status bar centered items.
Bugs / not working / To do:
Wireguard support Added 18-Sept
Play Store certification (Workaround using MagiskHide Props Config)
64 MP camera module seems to work only with the ANX Camera ver 185(not included). You must manually add all permissions.
Status bar text around the front camera
Code:
Source Code: https://github.com/LineageOS
Device: https://github.com/xiaomi-sm6250-devs/android_device_xiaomi_curtana-unified
Kernel: https://github.com/xiaomi-sm6250-devs/android_kernel_xiaomi_sm6250
Vendor: https://gitlab.com/m0sin/proprietary_vendor_xiaomi_curtana

Play Store certification: Have you tried with the latest gapps yet?

How to install? Anything I need to look at?

dungphp said:
Play Store certification: Have you tried with the latest gapps yet?
Click to expand...
Click to collapse
I have, it might be Magisk or I'm not hiding it properly.
Edit: I used the Magisk HideProps module and everything works fine now. I think the naming, curtana vs joyeuse and version number were causing the issue.

glurak888 said:
How to install? Anything I need to look at?
Click to expand...
Click to collapse
If you are coming from stock, I installed the Lineage recovery, installed the ROM. After it rebooted, I went back to install OpenGapps and Magisk.
I tried going from stock using Pbrp but it failed for me. After Lineage was installed, PBRP worked fine.

I have just installed it, anything I should know?

Installed successful on
Note pro 9 a Joyeuse (global) with 64mp cam , nfc and Lte aka a M2003J6B2G
Only recovery from lineage worked for me ... it also enables fastbootd !!
Rooting with magiskmanager wasnt possible via patching boot.img but flashing Magisk-v20.4.zip via recovery worked .
nfc works too
fastcharge seems so work fine ...
lte seems to work too
will try anx cam and 64 mpx tomorrow ... //edit - ANXCameraUnity_185.SaltyIntelligentPlainsqueaker and 48MPFixQ_170.SophisticatedFatBetafish make it work too ....
thx

I installed the ANXCameraUnity_185.SaltyIntelligentPlainsqueaker.zip and the camera app crash all time. Should I install and the 48MPFixQ_170.SophisticatedFatBetafish.zip?
Thank you for this nice rom, keep walking.

[email protected] said:
I installed the ANXCameraUnity_185.SaltyIntelligentPlainsqueaker.zip and the camera app crash all time. Should I install and the 48MPFixQ_170.SophisticatedFatBetafish.zip?
Thank you for this nice rom, keep walking.
Click to expand...
Click to collapse
Yes, install the 48 MP Fix to add the 48 MP camera. It's crashing because you need to manually fix the permissions on the app. After you allow everything it'll crash once then work fine.

Minor update:
September security patch
Added wireguard kernel support 1.0.20200908

moffa~ said:
If you are coming from stock, I installed the Lineage recovery, installed the ROM. After it rebooted, I went back to install OpenGapps and Magisk.
I tried going from stock using Pbrp but it failed for me. After Lineage was installed, PBRP worked fine.
Click to expand...
Click to collapse
so basically we flash on joyeuse a curtana recovery in order to flash a curtana rom and then we flash back the joyeuse recovery right?

didicola said:
so basically we flash on joyeuse a curtana recovery in order to flash a curtana rom and then we flash back the joyeuse recovery right?
Click to expand...
Click to collapse
Not sure I understand what you are saying. The build is joyeuse/curtana unified. I don't like not being able to flash zips without sideloading so I'm using the PBRP recovery. For the initial flash I used my PC and the Lineage Recovery.

Are the gapps included or do we need to flash them?

kalehrl said:
Are the gapps included or do we need to flash them?
Click to expand...
Click to collapse
Not included. Must be flashed.

Excellent rom, I have used it since its publication, and so far no problem. The performance of the battery seems to me outstanding, and to this day, it is the only one in which an indispensable application for me (Sony Music) works without problem. I hope the excellent work continues, and it even became an official version. Thanks!

I use redmi note 9s, can i flash this rom?

vanmaitrangchu said:
I use redmi note 9s, can i flash this rom?
Click to expand...
Click to collapse
Theoretically yes. Please share your experience if you try it out.

moffa~ said:
Theoretically yes. Please share your experience if you try it out.
Click to expand...
Click to collapse
When i used mi note 3, lineage is bettest rom for me. But it is officical. with mi note 9s (4/64) i got few bug, i try test it again.
first day i got:
when flash, i have some problem, but it easy, forget it. after that i reboot system, 2 minute its done. reboot to recovery to flash gapp (nano), reboot, but i can sync adress from google .
Try again, i wipe all data (rom in sd card), flash again. reboot device, wait rom instal, reboot recovery, flash gapp again, reboot, it ok :v i dont know why!
some thing i dont like with rom:
- dial not support dual sim, mean: icon sim1 sim2 when use dial pad. i use 2 sim.
- swicht speaker too much make phone restart (im shiper, i usally switch), it make me crazy.
- no 1 hand mod, i ussally use it with 1 hand, to big to use.
And else i like this rom, from mi note 3.
Sorry, my english very bad! I hope offical soon, thanks so much!

vanmaitrangchu said:
When i used mi note 3, lineage is bettest rom for me. But it is officical. with mi note 9s (4/64) i got few bug, i try test it again.
first day i got:
when flash, i have some problem, but it easy, forget it. after that i reboot system, 2 minute its done. reboot to recovery to flash gapp (nano), reboot, but i can sync adress from google .
Try again, i wipe all data (rom in sd card), flash again. reboot device, wait rom instal, reboot recovery, flash gapp again, reboot, it ok :v i dont know why!
some thing i dont like with rom:
- dial not support dual sim, mean: icon sim1 sim2 when use dial pad. i use 2 sim.
- swicht speaker too much make phone restart (im shiper, i usally switch), it make me crazy.
- no 1 hand mod, i ussally use it with 1 hand, to big to use.
And else i like this rom, from mi note 3.
Sorry, my english very bad! I hope offical soon, thanks so much!
Click to expand...
Click to collapse
Thanks for testing it out.
Unfortunately, I don't have a second sim card to test it with.
I have no problem using the speaker phone at all. Could you grab the logs, maybe I can look into it.
It looks like one-hand mode was removed from Lineage. There are gestures for navigation. It works about 90% of the time for me.
------Edit-------
I tested my phone out with a second sim card today and had no issues. Is anyone else having issues with a second sim card?

moffa~ said:
Thanks for testing it out.
Unfortunately, I don't have a second sim card to test it with.
I have no problem using the speaker phone at all. Could you grab the logs, maybe I can look into it.
It looks like one-hand mode was removed from Lineage. There are gestures for navigation. It works about 90% of the time for me.
------Edit-------
I tested my phone out with a second sim card today and had no issues. Is anyone else having issues with a second sim card?
Click to expand...
Click to collapse
The problem occurs when turning on the speakerphone while calling. End of the call without turning off the speakerphone, the next call will easily lose sound. Ratio 1/5. Trying to turn on and off the speakerphone is very easy to reset the device.
Regarding the 2 sim issue: I mean there is no separate button for the 2 sims in the dial pad. Like the dial pad of the EU version, very convenient.
I need one hand mod, too hight with my hand. like picture.

Has anyone tried GSI on the G8 Play?

Just as I asked. I would like to know if anyone has made GSI work or at least tried (like me) to make it work.

RandoMike said:
Just as I asked. I would like to know if anyone has made GSI work or at least tried (like me) to make it work.
Click to expand...
Click to collapse
Update: It IS possible to install Lineage OS GSI on the G8 Play. However, you will trigger a security error (nothing critical, since your phone will still boot up). To install it, you really need to flash the One Macro Firmware (evidently, your device can hard brick, but it's possible to fix it ). Later, you can flash the Lineage rom through fastboot.
Even though it's possible to install it and even boot it, the rom is buggy. It would be wonderful if anyone who knows better developing than me would work on this device, which has been abandoned for so long...
Some bugs of this rom are:
Fingerprint sensor sometimes triggers volume up or down.
The screen is not well adjusted, picture seems weird.
Dm-verity error which will not allow the phone to boot unless you press the power button again.
Bluetooth audio not working.
I have not tested the rom completely yet. However, I would like to get this forum revived again, with the possibility of "messing up" with the phone. It's not impossible, it just needs some attention

You can flash a blank vbmeta image to disable security error this may help with some issues. good luck and thanks for your contribution to the device forum. (also, sorry for bad english)

Ale001 said:
You can flash a blank vbmeta image to disable security error this may help with some issues. good luck and thanks for your contribution to the device forum. (also, sorry for bad english)
Click to expand...
Click to collapse
I already tried that on the official ROM and it didn't work. I only get a DM-Verity error amd a bootloop when trying to boot Lineage, which can be solved if flashing the stock ROM again.

It's possible install a arm-ab gsi or I need to install one macro arm64 firmware first?

Ale001 said:
It's possible install a arm-ab gsi or I need to install one macro arm64 firmware first?
Click to expand...
Click to collapse
It didn't work for me on stock firmware. Lineage GSI worked for me on One Macro's ROM

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.