Develop Bugs

Moto z problems

Phone - Moto Z play XT1635-02-DS
Android- 7.1.2
Installed TWRP 3.1.1.0
Viper addison 7.1.2
Here are my problem:
1. Flashed with supersu v2.79 and also v2.82, neither works. Phone still not rooted. When i tried toa access supersu app, it says "there is no su binary installed and supersu can't install it..."
2. Camera does open but it doesn't function, it stays dark. (I have custom gapps 7.1.x)
3. Proximity sensor does not seem to be working in other cases, but the phone goes dark as soon as i press dial or as soon as i pick a call and remains so untill the other party cuts the call. Otherwise i need to shut down the phone if i have to end the call from my phone.
4. When i shut down the phone, in order to reboot manually from recovery-reboot-bootloader. Otherwise it remains in twrp recovery.
Can anyone help please?

Have you tried flashing back to stock and seeing if that fixed these issues?

Pal Guite said:
Phone - Moto Z play XT1635-02-DS
Android- 7.1.2
Installed TWRP 3.1.1.0
Viper addison 7.1.2
Here are my problem:
1. Flashed with supersu v2.79 and also v2.82, neither works. Phone still not rooted. When i tried toa access supersu app, it says "there is no su binary installed and supersu can't install it..."
2. Camera does open but it doesn't function, it stays dark. (I have custom gapps 7.1.x)
3. Proximity sensor does not seem to be working in other cases, but the phone goes dark as soon as i press dial or as soon as i pick a call and remains so untill the other party cuts the call. Otherwise i need to shut down the phone if i have to end the call from my phone.
4. When i shut down the phone, in order to reboot manually from recovery-reboot-bootloader. Otherwise it remains in twrp recovery.
Can anyone help please?
Click to expand...
Click to collapse
This is not really a problem with the phone per se but the rom you chose to flash. The reboot issue can be checked by setting a command at bootloader using "fastboot oem fb_mode_clear".

gman88667733 said:
Have you tried flashing back to stock and seeing if that fixed these issues?
Click to expand...
Click to collapse
Thanks. But i don't have the stock rom. I didn't intend to use a custom rom. I tried to root it to recover some deleted photos and the moron that i am, i didn't back up the stock firmwares and while tweaking around in the recovery i somehow deleted the stock rom. This is my 1st time...

DroneDoom said:
This is not really a problem with the phone per se but the rom you chose to flash. The reboot issue can be checked by setting a command at bootloader using "fastboot oem fb_mode_clear".
Click to expand...
Click to collapse
Thanks... I tried the above command (it does recognize my device) bur this is what i get :
{bootloader} slot-count: not found
{bootloader} slot-suffixes: not found.

Pal Guite said:
Thanks... I tried the above command (it does recognize my device) bur this is what i get :
{bootloader} slot-count: not found
{bootloader} slot-suffixes: not found.
Click to expand...
Click to collapse
Is there an option for the bootloader in developer settings in your rom similar to the screenshot I attached? Make sure it's enabled.

DroneDoom said:
Is there an option for the bootloader in developer settings in your rom similar to the screenshot I attached? Make sure it's enabled.
Click to expand...
Click to collapse
Thanks for your concern. Developer option is 'on' and Multiprocess webView renderers seperately - 'on'. But i get the same problem. (and how do you attach screenshots ? I don't see any option for attaching files) In anycase, like you said, i think the problem has more to do with the rom. Can you please suggest me another rom or if possible link from where i can download stock rom for my phone.

Pal Guite said:
Thanks for your concern. Developer option is 'on' and Multiprocess webView renderers seperately - 'on'. But i get the same problem. (and how do you attach screenshots ? I don't see any option for attaching files) In anycase, like you said, i think the problem has more to do with the rom. Can you please suggest me another rom or if possible link from where i can download stock rom for my phone.
Click to expand...
Click to collapse
If your on xda with your browser, it's the paperclip icon to attach files. If you are using a 3rd party app that wraps xda into it then I can't help you there. As for going back to stock, Motorola made things a little critical when they released Nougat. Depending on how far you were on keeping the device up to date through stock, flashing the available stock images (which aren't signed) could brick the device if you aren't careful. There use to be an account on androidfilehost that uploaded current stock packages but it seems they're all gone now. If you remember the build number of the device before you rooted, that will help in picking the right stock files. I've taken a break in keeping my device rooted so I haven't kept track of the resources used to help go back to stock but they're in the MZP guide threads.
EDIT: a word of caution when reverting to stock:
-Don't use flash tools that don't let you see/edit the fastboot commands
-Do not use commands that touch modem/radio or gpt partitions
Found an upload of the latest build release keep it around when you figure out what you need to flash. It's best to clear system, data, and cache before flashing. Also have a rom (and twrp) at hand to adb sideload in case stock doesn't boot.
https://androidfilehost.com/?a=show&w=files&flid=215703
This Android version 7.1.1
Security patch: Sept 2017
Build number: NPN26.118-22-2

Thanks alot... ?

Root stock addison after june patch OTA

I've allready discussed this with @talktosam over at https://forum.xda-developers.com/mo...-to-magisk-root-xposed-oreo-8-t3743273/page16.
We both seem to have some trouble flashing magiks after the june patch ota. Our phones are stuck at bootlogo.
So if there's anybody out there who succeded, please let us know, how you did it.

This pertains to 8.x bootloaders and Oreo stock/factory signed. Maybe any 8.x bl rom?
yeah - read the comment about stuck at reboot in first post here
https://forum.xda-developers.com/moto-z-play/how-to/guide-how-to-magisk-root-xposed-oreo-8-t3743273
Thanks @rafikowy
I also wasted a lot of time last night and advise that don't use 16.4 or 16.6, or the latest uninstaller 7-19 - I could not get out of that repeated bootlogo re-boot loop thing with them. I went back to 16.0, and the 7-08 uninstaller, and re-did the terminal commands and finally got it to work. I have no idea why this is so fussy. But then I found that back a bit when using the old universal fix on Alberto's 8.1 AOSPruns on 7.x bootloaders) so starting to learn that if something works, DON'T go to a later version (of magisk uninstaller or magisk combined install) LOL.
As someone said somewhere - after you do this you will probably need to enter magisk and let it update to the latest manager.

Ok, so I will try again with 16.0, but it will take some time as I'm preparing for my holidays travel now :laugh:

hamudistan said:
Ok, so I will try again with 16.0, but it will take some time as I'm preparing for my holidays travel now :laugh:
Click to expand...
Click to collapse
yeah, I am finding that it requires a lot of patience unless I do exactly what @rafikowy said. I have no idea why it's so fussy.

hamudistan said:
Ok, so I will try again with 16.0, but it will take some time as I'm preparing for my holidays travel now :laugh:
Click to expand...
Click to collapse
Well just tried several times, but with same results. Stuck at bootlogo.
Btw: how do you manage to type the "=" sign in twrp terminal? It's not there on my keys.
So I sent the commands via adb shell.

I do not have June yet, so unless you know of a stock that has it I can't test it. I suppose it's possible retus won't get it.
Those special characters are accessed by tapping the thing right above 123 in lower left - has some other special characters like = and > .

KrisM22 said:
Those special characters are accessed by tapping the thing right above 123 in lower left - has some other special characters like = and > .
Click to expand...
Click to collapse
Man I never thougt that key would reveal more...
Ok after some sleep and some coffee I did it again. Followed all steps exactly and the system booted up and I'm rooted.
Thanks for your patience

hamudistan said:
Man I never thougt that key would reveal more...
Ok after some sleep and some coffee I did it again. Followed all steps exactly and the system booted up and I'm rooted.
Thanks for your patience
Click to expand...
Click to collapse
Did you install f2fs module too?

Nnly loopback workaround. Didn't have f2s since my first stock oreo and everything worked as it should, so felt no need to install.
Back in nougat it was absolutly necessary

hamudistan said:
Nnly loopback workaround. Didn't have f2s since my first stock oreo and everything worked as it should, so felt no need to install.
Back in nougat it was absolutly necessary
Click to expand...
Click to collapse
Isn't the loopback bug and f2fs partition one in the same for that magisk specific module?

As long as they have two different names, I treat them as two (slight?) different modules due to not better (deeper) knowing it

Never underestimate the power of coffee/espresso! Great!!!

hamudistan said:
Nnly loopback workaround. Didn't have f2s since my first stock oreo and everything worked as it should, so felt no need to install.
Back in nougat it was absolutly necessary
Click to expand...
Click to collapse
I thought loopback obviously, not patch Never mind, I just installed june patch, flashed magisk 16.0, wrote terminal commands, flashed f2fs and I'm stuck on logo.... Could you please write down exactly all steps which you had done?
Edit: Never mind, I've already figured it out. After reinstaling magisk it booted up with f2fs loopback module.

Lineage OS on Moto Z2 Force xt1789-06 ?

Hi there,
after unbricking the device I'm able to start TWRP on it. Using fastboot, ADB can't connect, even if TWRP ADB Sideloading is started - strange. Lineage OS 16 can by installed from ZIP after copying it on the Device using explorer.
But neither LOS nor TWRP can't be installed to last on the device.
Before I managed it to get at least TWRP permanently on the phone, but after playing around even this won't work.
Has anyone ever successfully installed LOS on a M3M-Version of the bootloader?
Is there way to get back to stock and then flash LOS?
How to get a real clean restart?
Thanks a lot!

BrickingsSoFunny said:
Hi there,
after unbricking the device I'm able to start TWRP on it. Using fastboot, ADB can't connect, even if TWRP ADB Sideloading is started - strange. Lineage OS 16 can by installed from ZIP after copying it on the Device using explorer.
But neither LOS nor TWRP can't be installed to last on the device.
Before I managed it to get at least TWRP permanently on the phone, but after playing around even this won't work.
Has anyone ever successfully installed LOS on a M3M-Version of the bootloader?
Is there way to get back to stock and then flash LOS?
How to get a real clean restart?
Thanks a lot!
Click to expand...
Click to collapse
Update: Also managed to install this https://forum.xda-developers.com/z2...m-tmo-z2-force-27-1-5-flashall-march-t3917070
But that's not what I want. Nobody Lineage on the Device?

BrickingsSoFunny said:
Update: Also managed to install this https://forum.xda-developers.com/z2...m-tmo-z2-force-27-1-5-flashall-march-t3917070
But that's not what I want. Nobody Lineage on the Device?
Click to expand...
Click to collapse
Since I'm just talking with myself in this thread: From the TMO Stock I managed to install TWRP to last on the device. But anytime I install the LOS ROM and restart the phone stays black and is bricked.
Any ideas? Just to be not so alone?

Heyyo, if you're installing LineageOS, please ensure you're following the steps in the LineageOS wiki as that is what I followed to go from stock to LineageOS and it worked perfectly.
https://wiki.lineageos.org/devices/nash/install

ThE_MarD said:
Heyyo, if you're installing LineageOS, please ensure you're following the steps in the LineageOS wiki as that is what I followed to go from stock to LineageOS and it worked perfectly.
https://wiki.lineageos.org/devices/nash/install
Click to expand...
Click to collapse
Yes, especially
- install os, reboot and THEN gapps and stuff
- if u don't have both slots active (for example, if u flash stock and then immediately go for los) u will have problems , unless u use the pre-los zip, u can find it here somewhere

@Dany XP that is not advised. As the wiki mentions
Sideload the LineageOS .zip package:
On the device, select “Apply Update”, then “Apply from ADB” to begin sideload.
On the host machine, sideload the package using: adb sideload filename.zip
(Optionally): If you want to install any additional add-ons, run adb reboot sideload, then adb sideload filename.zip those packages in sequence.
NOTE: If you want Google Apps on your device, you must follow this step before booting into LineageOS for the first time!
Click to expand...
Click to collapse
The reason is when your device boots to system, it is at that point that it should "handshake" with the Google Play servers or there's a risk of stability issues with the Google Play services.

Dany XP said:
Yes, especially
- install os, reboot and THEN gapps and stuff
- if u don't have both slots active (for example, if u flash stock and then immediately go for los) u will have problems , unless u use the pre-los zip, u can find it here somewhere
Click to expand...
Click to collapse
Can you explain the second solution (about the both slots active and the pre-los.zip)

Alruse122 said:
Can you explain the second solution (about the both slots active and the pre-los.zip)
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=80232409&postcount=264
(In my case, without both slots active, I have bootloops and crashes from turning it on the device...)

Dany XP said:
https://forum.xda-developers.com/showpost.php?p=80232409&postcount=264
(In my case, without both slots active, I have bootloops and crashes from turning it on the device...)
Click to expand...
Click to collapse
But the Download is "XT1789-04_NASH_TMO_C_8.0.0_OCXS27.109-51-14-7_LOS-Prep.zip"
i have an android Pie and XT1789-05, it will work anyway?

Alruse122 said:
But the Download is "XT1789-04_NASH_TMO_C_8.0.0_OCXS27.109-51-14-7_LOS-Prep.zip"
i have an android Pie and XT1789-05, it will work anyway?
Click to expand...
Click to collapse
No, that's for TMO oreo. Don't flash the prep zip

41rw4lk said:
No, that's for TMO oreo. Don't flash the prep zip
Click to expand...
Click to collapse
I supposed, so, what you recommend ti actívate both slots un pie?

Dany XP said:
Yes, especially
- install os, reboot and THEN gapps and stuff
- if u don't have both slots active (for example, if u flash stock and then immediately go for los) u will have problems , unless u use the pre-los zip, u can find it here somewhere
Click to expand...
Click to collapse
I can't believe it's installed and running after all. I used the pre-los ZIP installed, LOS 16 nightly and opengapps pico...
BUT there is a little problem:
The phone recognizes one and two SIM card correctly, but displays empty signal icons.
Anytime I wan't to make a call it says I should disable flight mode to make calls, but flightmode IS of course disabled... tried to disable and reenable it, cleared dalvik und cache restarted etc.
So: Does anybody know, how to resolve this? Seems to be kind of missing carrier support...

BrickingsSoFunny said:
I can't believe it's installed and running after all. I used the pre-los ZIP installed, LOS 16 nightly and opengapps pico...
BUT there is a little problem:
The phone recognizes one and two SIM card correctly, but displays empty signal icons.
Anytime I wan't to make a call it says I should disable flight mode to make calls, but flightmode IS of course disabled... tried to disable and reenable it, cleared dalvik und cache restarted etc.
So: Does anybody know, how to resolve this? Seems to be kind of missing carrier support...
Click to expand...
Click to collapse
"One and two Sim cards..." That means u r NOT in tmo right? U must be on -05 or 06 I don't remember...
Sorry but the pre-los zip is onlynfor tmo devices (at least that's my understanding)

How I can flash a GSI ROM for Redmi Note 8 Pro?

Hello everyone, Im trying to understand how to flash a GSI img ROM (I want to try AOSP stock, or Havoc OS) but, I saw some posts and looks like is a bit hard to do.
I had TWRP installed (unofficial begonia) and magisk installed.
some informations I found: this device is just A slot supported
What exactly I need?
Orange Fox recovery?
Before flash need to disable something in recovery?
A arm64 slot IMG?
And gapps?
What are the steps?
Im waiting your answer

So far with my personal experience trying to flash Lineage 17 GSI on my RN8Pro and have had no luck. Lost baseband and both imei #'s in the process too (still trying to figure out how to restore).

Finally was lucky!
Flash LR Team TWRP:
https://mega.nz/#!B75xWQQQ!8DQdy09luHihxCziRX7ywUWkAwmAahjnWOQDgHxcTPA
Enable debugging and make sure computer has permission to use
On command promp adb reboot bootloader
fastboot flash recovery twrp.img
fastboot reboot (immediately disconnect phone and hold volume up)
In twrp go to advanced and Select "Close AVB2.0" swipe to confirm
Go back to twrp home -> Wipe -> Format
Flash gsi
And presto!
I just flashed Lineage 17 GSI as of now I wouldn't recommend it. Fixing to flash ASOP 10 GSI from phhusson see if it is any better!
Also as a favor since I lost baseband and imei for my phone could you please create a backup through twrp of your nvram and nvdata and PM it to me?
If you need any help just pm me!

JuanM2020 said:
Finally was lucky!
Flash LR Team TWRP:
https://mega.nz/#!B75xWQQQ!8DQdy09luHihxCziRX7ywUWkAwmAahjnWOQDgHxcTPA
Enable debugging and make sure computer has permission to use
On command promp adb reboot bootloader
fastboot flash recovery twrp.img
fastboot reboot (immediately disconnect phone and hold volume up)
In twrp go to advanced and Select "Close AVB2.0" swipe to confirm
Go back to twrp home -> Wipe -> Format
Flash gsi
And presto!
I just flashed Lineage 17 GSI as of now I wouldn't recommend it. Fixing to flash ASOP 10 GSI from phhusson see if it is any better!
Also as a favor since I lost baseband and imei for my phone could you please create a backup through twrp of your nvram and nvdata and PM it to me?
If you need any help just pm me!
Click to expand...
Click to collapse
What problems were there with the los 17 gsi?

Please share what's working on the GSI ROM and what's not. Thank you.

polfrank said:
What problems were there with the los 17 gsi?
Click to expand...
Click to collapse
Off the bat, Bluetooth did not work it just kept giving a Bluetooth has stopped message. Didn't have face unlock. Screen would suddenly flash as if display were damaged and would suddenly freeze when opening stock apps. And a few other things I don't remember as I already flash off of it.

Helhound0 said:
Please share what's working on the GSI ROM and what's not. Thank you.
Click to expand...
Click to collapse
I've flashed Havoc OS 2.9 GSI and after resizing and disabling HW overlays the ROM works near perfectly albeit some camera issues.

JuanM2020 said:
Finally was lucky!
Flash LR Team TWRP:
https://mega.nz/#!B75xWQQQ!8DQdy09luHihxCziRX7ywUWkAwmAahjnWOQDgHxcTPA
Enable debugging and make sure computer has permission to use
On command promp adb reboot bootloader
fastboot flash recovery twrp.img
fastboot reboot (immediately disconnect phone and hold volume up)
In twrp go to advanced and Select "Close AVB2.0" swipe to confirm
Go back to twrp home -> Wipe -> Format
Flash gsi
And presto!
I just flashed Lineage 17 GSI as of now I wouldn't recommend it. Fixing to flash ASOP 10 GSI from phhusson see if it is any better!
Also as a favor since I lost baseband and imei for my phone could you please create a backup through twrp of your nvram and nvdata and PM it to me?
If you need any help just pm me!
Click to expand...
Click to collapse
Of course and thanks dude. In a few hours i will attach the files.

yayimathrowaway said:
I've flashed Havoc OS 2.9 GSI and after resizing and disabling HW overlays the ROM works near perfectly albeit some camera issues.
Click to expand...
Click to collapse
Newbie here. Please let me know what is it for and how to "resizing and disabling HW overlays"

yayimathrowaway said:
I've flashed Havoc OS 2.9 GSI and after resizing and disabling HW overlays the ROM works near perfectly albeit some camera issues.
Click to expand...
Click to collapse
That sounds good. Thanks for sharing. Did you use GSI since you flashed or did you restore MIUI?

Sorry for my ignorance, but what is a GSI ROM?

montechristos1 said:
Sorry for my ignorance, but what is a GSI ROM?
Click to expand...
Click to collapse
Generic System Image. Basically a single ROM image that should technically work in any device running Android 8.1 or newer. It contains the generic AOSP (Pure android) source.

Helhound0 said:
Generic System Image. Basically a single ROM image that should technically work in any device running Android 8.1 or newer. It contains the generic AOSP (Pure android) source.
Click to expand...
Click to collapse
Thanks.
So people were able to flash LOS GSI on their Redmi Note PRO?
No specific thread for this?
(I am one of the people that are waiting for one of the custom open-source ROMs to replace the (ihmo) horrible MUI)

MarkLev said:
Newbie here. Please let me know what is it for and how to "resizing and disabling HW overlays"
Click to expand...
Click to collapse
Disabling HW Overlays means that your GPU is the only thing that will handle all of the graphics on your phone. If this is not on in some GSI ROMs the screen will flicker when it's about to go to sleep and at other random times. It can be accessed in Developer options.
Additionally, as this is a GSI made to work on many different phones, the proportions on the screen are off when you first install it. On Havoc, all of the resizing options are in Havoc Settings. In other ROMs without customization options, there are ADB commands that can resize your ROM. Specifically, the problems I initially experienced were involving the status bar icons and clock only partially being on the screen.
---------- Post added at 07:57 AM ---------- Previous post was at 07:46 AM ----------
Helhound0 said:
That sounds good. Thanks for sharing. Did you use GSI since you flashed or did you restore MIUI?
Click to expand...
Click to collapse
I am actually using the GSI right now. I didn't restore MIUI because I just did not like it. I think I'll stay on this GSI. Again, after some modifications in Settings, the ROM I'm using works near perfectly.
The cameras, of course, are kind of messed up though. No matter what camera app I use I cannot access the 64MP camera and anything other than the camera app that came with the GSI (which is pretty bad) randomly flickers the screen while I'm taking a picture or recording a video, even after disabling HW Overlays in Developer Options. Maybe could be fixed by flashing a third party camera app as a system app.
Other than that, no problems whatsoever.
---------- Post added at 08:04 AM ---------- Previous post was at 07:57 AM ----------
KonahZave said:
Hello everyone, Im trying to understand how to flash a GSI img ROM (I want to try AOSP stock, or Havoc OS) but, I saw some posts and looks like is a bit hard to do.
I had TWRP installed (unofficial begonia) and magisk installed.
some informations I found: this device is just A slot supported
What exactly I need?
Orange Fox recovery?
Before flash need to disable something in recovery?
A arm64 slot IMG?
And gapps?
What are the steps?
Im waiting your answer
Click to expand...
Click to collapse
If you still need some help, I have a full guide on how to flash here

yayimathrowaway said:
I am actually using the GSI right now. I didn't restore MIUI because I just did not like it. I think I'll stay on this GSI. Again, after some modifications in Settings, the ROM I'm using works near perfectly.
The cameras, of course, are kind of messed up though. No matter what camera app I use I cannot access the 64MP camera and anything other than the camera app that came with the GSI (which is pretty bad) randomly flickers the screen while I'm taking a picture or recording a video, even after disabling HW Overlays in Developer Options. Maybe could be fixed by flashing a third party camera app as a system app.
Other than that, no problems whatsoever.
Click to expand...
Click to collapse
I don't really mind the cameras not working at a 100% tbh since i don't use them that much. However did you try GCam on GSI or any other API2 camera app?

Helhound0 said:
I don't really mind the cameras not working at a 100% tbh since i don't use them that much. However did you try GCam on GSI or any other API2 camera app?
Click to expand...
Click to collapse
Yeah, but the screen flashes randomly on them.
CameraMX works great with the cameras that it does support. CameraF5-V crashes randomly. GCam for RN8P can only take photos, and only supports 2 cameras. I think that some of these issues would be fixed if I flashed then as system apps, because the stock camera app works fine, albeit the fact that it's just not a very good camera app.

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.