Develop Bugs

Play Store FC trying to buy app

Okay I have two pixels. One with magisk and one running SuperSU with suhide, both pass safety net. Both on Oreo. I'm trying to buy a substratum theme in the Play Store everytime I enter my password to buy it if force closes on either phone. Anyone else have this issue I imagine it still detects the root, but I'm not sure I was hoping somebody new a workaround. Both pixels are on Android o.
Edit. I did try clearing cache and data. I am certified

mac796 said:
Okay I have two pixels. One with magisk and one running SuperSU with suhide, both pass safety net. Both on Oreo. I'm trying to buy a substratum theme in the Play Store everytime I enter my password to buy it if force closes on either phone. Anyone else have this issue I imagine it still detects the root, but I'm not sure I was hoping somebody new a workaround. Both pixels are on Android o.
Edit. I did try clearing cache and data. I am certified
Click to expand...
Click to collapse
I have this same issue. However, I am stock unrooted. Somebody in the Pixel forum was having the same issue. His problem was solved by reflashing the full Oreo image. A factory reset did not fix it. I'm planning to reflash the Oreo image to both partitions tomorrow to see if it fixes the problem.

mlin said:
I have this same issue. However, I am stock unrooted. Somebody in the Pixel forum was having the same issue. His problem was solved by reflashing the full Oreo image. A factory reset did not fix it. I'm planning to reflash the Oreo image to both partitions tomorrow to see if it fixes the problem.
Click to expand...
Click to collapse
It's very strange happens on both my pixels so must be a bug on googles side maybe.

mac796 said:
It's very strange happens on both my pixels so must be a bug on googles side maybe.
Click to expand...
Click to collapse
I have the issue but my wife doesn't. She updated to Oreo via OTA, I updated via manually flashing. I was previously rooted with a custom ROM but had returned to stock Nougat long before updating to Oreo. How did you update?

mlin said:
I have the issue but my wife doesn't. She updated to Oreo via OTA, I updated via manually flashing. I was previously rooted with a custom ROM but had returned to stock Nougat long before updating to Oreo. How did you update?
Click to expand...
Click to collapse
I flashed the factory image with fastboot. I'm on September that's a good idea maybe I'll Flash August and take the OTA see how that goes.

mac796 said:
I flashed the factory image with fastboot. I'm on September that's a good idea maybe I'll Flash August and take the OTA see how that goes.
Click to expand...
Click to collapse
I flashed the factory image on release day and OTA'd to September security patch. No dice.

mlin said:
I flashed the factory image on release day and OTA'd to September security patch. No dice.
Click to expand...
Click to collapse
So it's still not working for you? Maybe I'll just wait till next update then.

mac796 said:
So it's still not working for you? Maybe I'll just wait till next update then.
Click to expand...
Click to collapse
Nope, still not working. I'll let you know if my efforts tomorrow are successful.

mlin said:
I flashed the factory image on release day and OTA'd to September security patch. No dice.
Click to expand...
Click to collapse
So I flashed back to August and it let me put in my password and buy an app and then if FC right after that. But it did go through lol

mac796 said:
So I flashed back to August and it let me put in my password and buy an app and then if FC right after that. But it did go through lol
Click to expand...
Click to collapse
Lol, weird. So just reflash before each app purchase and you should be good!

mlin said:
Lol, weird. So just reflash before each app purchase and you should be good!
Click to expand...
Click to collapse
Geez I hope not. Google sure making things alot harder all around
Edit: ok it took the OTA to September and same thing. No go. I have Verizon, wonder if that has anything to do with it

mac796 said:
Geez I hope not. Google sure making things alot harder all around
Edit: ok it took the OTA to September and same thing. No go. I have Verizon, wonder if that has anything to do with it
Click to expand...
Click to collapse
I have Verizon as well. I used fastboot to flash the factory image to both slots and now everything works. Not sure if there was an easier way to get it working but at least it works now. Took the OTA to September and everything is still working.

mlin said:
I have Verizon as well. I used fastboot to flash the factory image to both slots and now everything works. Not sure if there was an easier way to get it working but at least it works now. Took the OTA to September and everything is still working.
Click to expand...
Click to collapse
Yes I did that to. I'm still having the problem kind of glad it didn't work, didn't really want to buy anything lol. I'm not sure what the deal is

mac796 said:
Yes I did that to. I'm still having the problem kind of glad it didn't work, didn't really want to buy anything lol. I'm not sure what the deal is
Click to expand...
Click to collapse
Did you wipe data as well?

mlin said:
Did you wipe data as well?
Click to expand...
Click to collapse
Yes I wiped everything except internal storage

mac796 said:
Yes I wiped everything except internal storage
Click to expand...
Click to collapse
I did wipe internal storage, though hard to say if that difference made it work. I'd be curious to hear if you do get it working eventually or if you find a different solution. Best of luck, hope you get it resolved eventually though I get the appeal of being unable to buy apps lol.

Shield Oreo

It's possible that it comes today/tomorrow at some point!!
Source: https://twitter.com/nvidiashield/status/913265527480475648
Yes, major speculating here, but usually Nvidia is very very quick with updates. SO let's all hope and pray. This COULD also be the Nvidia Spot announcement/availability.

Tomorrow 29th or today 28th. Their message is very cryptic. Google Assistant was just released for Nvidia Shield TV! Not Oreo unless they have their own announcement since Assistant one was by Google

Apparently some people are updating to Oreo already. But it looks like US only. :crying:
edit...not Oreo

kalinskym said:
Tomorrow 29th or today 28th. Their message is very cryptic. Google Assistant was just released for Nvidia Shield TV! Not Oreo unless they have their own announcement since Assistant one was by Google
Click to expand...
Click to collapse
Yes, correct. It was assistant that was released! http://www.androidpolice.com/2017/09/28/assistant-finally-come-shield-tv-looks-great/

JoeFCaputo113 said:
Yes, correct. It was assistant that was released! http://www.androidpolice.com/2017/09/28/assistant-finally-come-shield-tv-looks-great/
Click to expand...
Click to collapse
Unfurtunately only in U. S.... Hopefully there will be a way to get it, elsewhere

Kantraz said:
Unfurtunately only in U. S.... Hopefully there will be a way to get it, elsewhere
Click to expand...
Click to collapse
Wonder if changing the language to English US will force it to work like with phones. I'll have a play about tonight.
Also...from what I understand this is Nvidia Experience 6 and not Oreo. The new launcher is not yet here for the shield.

dunjamon said:
Wonder if changing the language to English US will force it to work like with phones. I'll have a play about tonight.
Also...from what I understand this is Nvidia Experience 6 and not Oreo. The new launcher is not yet here for the shield.
Click to expand...
Click to collapse
Hopefully it is enough, gonna try as soon as I get home from work!

Kantraz said:
Hopefully it is enough, gonna try as soon as I get home from work!
Click to expand...
Click to collapse
Snap! I've already told the missus to plug in the controller to get it charged up and ready. Ha!

dunjamon said:
Snap! I've already told the missus to plug in the controller to get it charged up and ready. Ha!
Click to expand...
Click to collapse
I can confirm that Google Assistant, can be enabled by changing the language

Just got the update. But it failed to install. It downloads the update and restarts the shield, but never finishes the install. Stops at about 20% on the Android System Update Screen then restarts back to the home screen asking if I want to install the Experience 6.0 update. Is it because I'm rooted? I don't have TWRP installed but I do have superuser installed....Tried 3 times.

dk1keith said:
Just got the update. But it failed to install. It downloads the update and restarts the shield, but never finishes the install. Stops at about 20% on the Android System Update Screen then restarts back to the home screen asking if I want to install the Experience 6.0 update. Is it because I'm rooted? I don't have TWRP installed but I do have superuser installed....Tried 3 times.
Click to expand...
Click to collapse
I always remove root then do the update. No TWRP either but it would always fail on me.

dk1keith said:
Just got the update. But it failed to install. It downloads the update and restarts the shield, but never finishes the install. Stops at about 20% on the Android System Update Screen then restarts back to the home screen asking if I want to install the Experience 6.0 update. Is it because I'm rooted? I don't have TWRP installed but I do have superuser installed....Tried 3 times.
Click to expand...
Click to collapse
Got #root#?!
If so, well there's your problem. You can NOT update in the conventional way once your rooted. In short you'll have to first download, and use fastboot, to flash the last 5.0.x Recovery For (Chiefly Recovery, System, and Vendor), and then most likely as not do a full system reset. Which if your unfortunate to be doing this on a Pro. Will mean about roughly 2.5h's+ of downtime. Before you'll then need to worry about the latest Update.
Unfortunately I keep telling myself to never root the damned thing again. 'Cause this IS a huge PitA! but, somehow I never learn.
JagXK8 said:
I always remove root then do the update. No TWRP either but it would always fail on me.
Click to expand...
Click to collapse
Alas One does NOT just remove root on the Shield. And, sadly 'cause of it. The only way I know of to be rid of it is flashing a new (Clean Recovery OS), and then factory resetting it fresh for the "New OS" to actually get written. Otherwise root seem to longer like a bad smell on the Shield.
And, now an aside...
Where is all this scuttlebutt about Oreo (Cookie), coming from?
Having done the above... (Sigh again!) I just finished wrapping up that part of the Install. When it occurred to me to check the Version... Which is still Android 7 (e.g. Nougat), so unless someones getting something I'm not. Then, this is not the Chocolate Wafer Cookie your looking for....
Which begs a different question. Why are they calling this "Experience 6..x", and not 5.x.x?

Ichijoe said:
Got #root#?!
If so, well there's your problem. You can NOT update in the conventional way once your rooted. In short you'll have to first download, and use fastboot, to flash the last 5.0.x Recovery For (Chiefly Recovery, System, and Vendor), and then most likely as not do a full system reset. Which if your unfortunate to be doing this on a Pro. Will mean about roughly 2.5h's+ of downtime. Before you'll then need to worry about the latest Update.
Unfortunately I keep telling myself to never root the damned thing again. 'Cause this IS a huge PitA! but, somehow I never learn.
Alas One does NOT just remove root on the Shield. And, sadly 'cause of it. The only way I know of to be rid of it is flashing a new (Clean Recovery OS), and then factory resetting it fresh for the "New OS" to actually get written. Otherwise root seem to longer like a bad smell on the Shield.
And, now an aside...
Where is all this scuttlebutt about Oreo (Cookie), coming from?
Having done the above... (Sigh again!) I just finished wrapping up that part of the Install. When it occurred to me to check the Version... Which is still Android 7 (e.g. Nougat), so unless someones getting something I'm not. Then, this is not the Chocolate Wafer Cookie your looking for....
Which begs a different question. Why are they calling this "Experience 6..x", and not 5.x.x?
Click to expand...
Click to collapse
I don't know about any Oreo update, but I updated to the new release without doing any data reset. Simply boot to fastboot and flash the downloaded system.img, boot.img, and recovery.img. No need to clear data. Then in the system you can install the OTA as normal and re-root using TWRP and Magisk/SuperSu.

eelsid said:
I don't know about any Oreo update, but I updated to the new release without doing any data reset. Simply boot to fastboot and flash the downloaded system.img, boot.img, and recovery.img. No need to clear data. Then in the system you can install the OTA as normal and re-root using TWRP and Magisk/SuperSu.
Click to expand...
Click to collapse
Can you elaborate on this? Maybe post a small guide? I am bootloader unlocked, and currently rooted, but recovery is stock. Where do I get the files you are talking about? Download, boot, and recovery img files? Thanks in advance!

bradleyw801 said:
Can you elaborate on this? Maybe post a small guide? I am bootloader unlocked, and currently rooted, but recovery is stock. Where do I get the files you are talking about? Download, boot, and recovery img files? Thanks in advance!
Click to expand...
Click to collapse
I found this guide here: https://forums.geforce.com/default/topic/667705/-guide-how-to-update-a-rooted-nvidia-shield/

I actually found this helpful guide for updating if you are on a pro and unlocked. http://nvidiashieldzone.com/2017/10/shield-tv-pro-500gb-experience-6-0-upgrade-solution/

Ascend XT2 B130 Update and CleanRom Rom's

Well here we go
This is the First Update for the XT2 in a flashable rom​
This is for those who unlocked their bootloader and installed TWRP and can not take OTA update on their phones
As most here know ower version of TWRP is not complete and cannot decrypt the /data partition
so unfortunately you'll have to wipe your phone to install this update (sorry)
Note This also Removes TWRP and restores Stock Recovery
Flashing instructions
download and copy the Stock_B130_ XT2_H1711.zip to your ex_sdcard
copy Magisk-v16.0.zip to your ex_sdcard (just in case you need to patch the boot.img)
Boot into TWRP swipe to allow system access
Go to Settings check Use rm -fr instead of formatting
next choose Wipe / Format Data / Type "yes" to confirm
Now choose Home / Install /Select storage Micro sd /Stock_B130_ XT2_H1711.zip and Flash it (watch the flash for any Red Errors)
choose wipe cache and then reboot.
If everything went well you should be on B130 and ready to setup your phone
Huge thanks go to @m0000 for sharing his updated files
If you have any problems you'll need to reflash TWRP and Try patching the boot.img with Magisk or restore your last backup or simply flash my B120 stock rom
XT2 B130 CleanRom​
Now that you have a Stock updated phone you may want to remove all the AT&T Bloat
Here's my CleanRom that removes around 350mb of useless junk from the phone.
First you'll need to flash TWRP back to your phone from fastboot
download recoveryV3_Fixed.zip > https://androidfilehost.com/?fid=673956719939832036
and extract it to your fastboot folder
Shutdown the phone
reboot to the bootloader (power + volume down + plugged in to the PC)
and flash it from command prompt with
fastboot flash recovery recoveryV3_Fixed.img
next reboot to TWRP (power + volume up )
Now you can Download the CleanRom and copy it to your ext_sdcard from your pc.
Flashing instructions are the same as above, but you can do a dirty flash by not formatting data like above if you want to keep your current apps
Here's the list of whats removed
Apps deleted from System:
Amazon shopping
App select
Call Protect
Protect Plus
Device Help
Setup & Transfer
CricketWiFiManager
Facebook
Facebook App Installer
Facebook app manager
Gmail
Google Duo
Google Chrome
Google Drive
Google Maps
Google Play Photos
Google Play Video
Google Play Music
Google Text to Speach Engine
Ignite
Lookout
myCricket
Apps deleted from /Data/hwinit/: (If you dirty flashed these will still be on your phone)
Google Editor Slides
Google Editor Sheets
Google Editor Docs
Firefox
Apps deleted from Cust:
AT&T Remote Support
myAT&T
AT&T Hot Spots
Google Talkback
everything in the H1711z folder
The rom includes the patched boot.img from magisk v16 (it's rooted)
This will probably be the only rom I release for this phone because I don't own one.

Awesome. Thank you! So if I flash magisk after I should be able to keep my root then?

clsA said:
Huge thanks go to @m0000 for sharing his updated files
Click to expand...
Click to collapse
No thanks needed. You did all the work I only followed clear directions

freedomwarrior said:
Awesome. Thank you! So if I flash magisk after I should be able to keep my root then?
Click to expand...
Click to collapse
Yes will need to start over ( TWRP & Magisk )
Your phone will be bone stock after flashing the rom
Sent from my LG-H910 using Tapatalk

Alright. I just want to confirm that the update was successful
Out of curiosity I wanted to see if I could relock the bootloader and that finally worked too. (see screenshot) I was never able to do that before on the B120 stock rom so this is great news if I ever decide to sell the phone or just wanna get SafetyNet working correctly.
I went ahead and unlocked my bootloader again and I flashed TWRP through fastboot, Booted into TWRP and flashed magisk v16 in the OP, rebooted and I am enjoying root again with an updated phone.
Thanks again guys!

freedomwarrior said:
Alright. I just want to confirm that the update was successful
Click to expand...
Click to collapse
thanks for the update! All we need now is a @clsA CleanRom for this version

So does anybody know how hard it would be to compile lineage os 14.1 for the elate/ xt2?

903tex said:
So does anybody know how hard it would be to compile lineage os 14.1 for the elate/ xt2?
Click to expand...
Click to collapse
I have no idea but that sure would be awesome! I am guessing it would be a real pain due to the fact Huawei has not released the source code for this phone.

freedomwarrior said:
I have no idea but that sure would be awesome! I am guessing it would be a real pain due to the fact Huawei has not released the source code for this phone.
Click to expand...
Click to collapse
What about the h1611?

MaxxTwo said:
What about the h1611?
Click to expand...
Click to collapse
I am not sure. I don't own that phone.

First post updated

clsA said:
This will probably be the only rom I release for this phone because I don't own one.
Click to expand...
Click to collapse
If you need a guinea pig for future testing let me know. I have one with your CleanRom and a stock unlocked one for any and all future updates.
Thanks!

I really liked this phone, i was actually impressed. I had money to spend on a new budget phone and I was between a ZTE blade spark and this huawei.
ZTE was ok for me because a couple of years ago i bought one of their big phones but their camera sucked a lot of blur and never had focus. sometimes i even had to touch the screen again and again to make it focus, while capturing video. So i gave a shot to this Huawei, went to walmart, they wanted 89 for the phone, told them to check online because it was 69 online and they lowered me the price right away.
then used the huawei for about an hour and damn, the camera is awesome, and the LCD screen is beautiful.
I have to research on how to unlock the bootloader and pay the 5bucks to make that happen.
One thing i noticed is that altho the phone has a 16gb capacity, i was looking at the storage area and you actually end up having something like 7.3gigs free. Is that normal? most of the space is taken by the rom. Your clean rom would help a lot at least to get more space, but how come it only frees 300megs.
and thank you very much for the update. i do know how damn hard it is to update at&t gophones because those assholes only let you update the phone if you have an att simcard inserted that is also activated and you have to be with an IP that is inside USA, and have celular data ON, and sometimes even having all that.. it doesnt even update

ZeldaWW said:
I really liked this phone, i was actually impressed. I had money to spend on a new budget phone and I was between a ZTE blade spark and this huawei.
ZTE was ok for me because a couple of years ago i bought one of their big phones but their camera sucked a lot of blur and never had focus. sometimes i even had to touch the screen again and again to make it focus, while capturing video. So i gave a shot to this Huawei, went to walmart, they wanted 89 for the phone, told them to check online because it was 69 online and they lowered me the price right away.
then used the huawei for about an hour and damn, the camera is awesome, and the LCD screen is beautiful.
I have to research on how to unlock the bootloader and pay the 5bucks to make that happen.
One thing i noticed is that altho the phone has a 16gb capacity, i was looking at the storage area and you actually end up having something like 7.3gigs free. Is that normal? most of the space is taken by the rom. Your clean rom would help a lot at least to get more space, but how come it only frees 300megs.
and thank you very much for the update. i do know how damn hard it is to update at&t gophones because those assholes only let you update the phone if you have an att simcard inserted that is also activated and you have to be with an IP that is inside USA, and have celular data ON, and sometimes even having all that.. it doesnt even update
Click to expand...
Click to collapse
Instructions for DC Unlocker are here
https://r.tapatalk.com/shareLink?ur...share_tid=3780903&share_fid=3793&share_type=t
Sent from my LG-H910 using Tapatalk

@clsA
At&t is trying to push another software update to my phone. Is this the B130 we already have or a new one?

freedomwarrior said:
@clsA
At&t is trying to push another software update to my phone. Is this the B130 we already have or a new one?
Click to expand...
Click to collapse
Looks like b173
You would need to return to stock b130
To attempt the update
Sent from my LG-H910 using Tapatalk

freedomwarrior said:
@clsA
At&t is trying to push another software update to my phone. Is this the B130 we already have or a new one?
Click to expand...
Click to collapse
clsA said:
Looks like b173
You would need to return to stock b130
To attempt the update
Sent from my LG-H910 using Tapatalk
Click to expand...
Click to collapse
B130_B173_ATT is the files i sent to clsA for his b130 rom. i've not received any notification on a newer update yet.
@freedomwarrior nice dark theme btw. what are you using?
Thanks

m0000 said:
B130_B173_ATT is the files i sent to clsA for his b130 rom. i've not received any notification on a newer update yet.
@freedomwarrior nice dark theme btw. what are you using?
Thanks
Click to expand...
Click to collapse
Awe ok. That would just be att update being stupid then.
I am using Pure Dark 5.0. So far it is the best dark theme I have come across.
https://play.google.com/store/apps/details?id=sk.hanni.emuithemes.puredark

freedomwarrior said:
Awe ok. That would just be att update being stupid then.
I am using Pure Dark 5.0. So far it is the best dark theme I have come across.
https://play.google.com/store/apps/details?id=sk.hanni.emuithemes.puredark
Click to expand...
Click to collapse
Awesome, i'll check it out. Are the ads annoying? or can disable with a proper ad blocker?
Thanks

m0000 said:
Awesome, i'll check it out. Are the ads annoying? or can disable with a proper ad blocker?
Thanks
Click to expand...
Click to collapse
No ads so far that I have noticed.

Question The new update made the cellular issue come back again

i accidentally updated to the new android 13 firmware (5.1) its actually the smoothest version of all time.
i have knox tripped but locked bootloader even in this situation it broke the cellular and it stops randomly and it isnt downgradable im just starting to hate this phone

musatbz said:
i accidentally updated to the new android 13 firmware (5.1) its actually the smoothest version of all time.
i have knox tripped but locked bootloader even in this situation it broke the cellular and it stops randomly and it isnt downgradable im just starting to hate this phone
Click to expand...
Click to collapse
uh oh.. i didnt notice that. I switched to crdroid 9.2 immidiately after installing the update. i'll extract system.img from the firmware and see if it is an actual issue here too. i faced it on one ui 4.1 before. Otherwise since downgrade isnt an option, consider switching to a gsi?

Captain_cookie_200 said:
uh oh.. i didnt notice that. I switched to crdroid 9.2 immidiately after installing the update. i'll extract system.img from the firmware and see if it is an actual issue here too. i faced it on one ui 4.1 before. Otherwise since downgrade isnt an option, consider switching to a gsi?
Click to expand...
Click to collapse
just flashed one ui with dsu. tried speedtest on data 4 times. seemed fine. try a fw reflash maybe?

Captain_cookie_200 said:
just flashed one ui with dsu. tried speedtest on data 4 times. seemed fine. try a fw reflash maybe?
Click to expand...
Click to collapse
yeah actually maybe it was because i upgraded from android 12 but im not sure

musatbz said:
i accidentally updated to the new android 13 firmware (5.1) its actually the smoothest version of all time.
i have knox tripped but locked bootloader even in this situation it broke the cellular and it stops randomly and it isnt downgradable im just starting to hate this phone
Click to expand...
Click to collapse
just make a full wipe and done, but make a full backup first

musatbz said:
yeah actually maybe it was because i upgraded from android 12 but im not sure
Click to expand...
Click to collapse
try a fw reflash and lmk how it goes

im wiping rn

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.