Related
*I TAKE NO CREDIT FOR ANY OF THIS, IM JUST TELLING HOW I DID IT. I AM ALSO NOT GUARANTEING YOU WILL HAVE THE SAME OUTCOME*
*I recommend going to this new update guide by CVertigo1 in the ROM's section as this version of the PlayStore ROM is outdated.*
Credit for Root and PlayStore Rom goes to jrkruse (https://forum.xda-developers.com/member.php?u=1949695)
ROOTING
1)Flashed stock Nougat ROM
2)Flashed ENG-ROOT found here https://www.androidfilehost.com/?fid=457095661767141717
- Make sure to flash the correct kernel included in the zip file
3) Install SuperSU. Link: https://www.androidfilehost.com/?fid=529152257862710010
- I used the regular Root.bat not the one with tweaks
FIXING LAG
1)Install Flashfire from PlayStore
2)Download the PlayStore Rom from https://www.androidfilehost.com/?fid=457095661767144652
-Transfer the file to the S7
3)Open Flashfire and flash the zip choosing only Mount/ system read/write
4)Now AROMA Installer will pop up and go through all of the terms and conditions
-When asked what to wipe I choose to wipe everything
-Next when asked what bloat to remove I choose the PlayStore Rom which removes all bloat and replaces stock apps with google apps (To see full list of changes refer to the PlayStore thread)
5)Now when my S7 boot it showed no launcher, I simply held the home button down which opened the google search, in there I searched for the playstore app and installed Nova Launcher.
-Now reinstall SuperSU by double clicking the root.bat like before
6) Installed the following apps to help with lag; Lspeed, Greenify, Kernal Auditor, LeanDroid, Force Doze, and SSD Boost
-I used most of the settings found on Lag fix threads for the MM root
My S7 is smooth as butter after all of this, no lag spikes and random crashes like I was experiencing with just the ENG Root flashed.
EXTRA
1)I did have to to a reboot to get the camera to work properly
2) I had to download a Dialer/Contacts and Message app from the playstore because the stock ones were deleted in this process. But the store ones work just fine, I am recieving calls and messages like normal.
3) *Battery life is just a little worse than stock, might be worth waiting for Xposed to released for Nougat.*
Credit for Root and PlayStore Rom goes to jrkruse (https://forum.xda-developers.com/member.php?u=1949695) :good:
setup wizard keeps stopping...
I have followed your step with my phone (Galaxy S7 Verizon - Android 7), but when go to step no 5 my phone always alert (The process com.android.phone has stopped, Setup Wizard keep stopping...). I tried to hold HOME button but still nothing and message always alert even reboot phone.
Please help. thank in advance
Bunrin said:
I have followed your step with my phone (Galaxy S7 Verizon - Android 7), but when go to step no 5 my phone always alert (The process com.android.phone has stopped, Setup Wizard keep stopping...). I tried to hold HOME button but still nothing and message always alert even reboot phone.
Please help. thank in advance
Click to expand...
Click to collapse
Weird, did you wipe your S7 completely before doing the process? I would flash fresh nougat and try again.
UPDATE
Went through the entire process once more and found that wiping but keeping SU image works the best, I chose "no wipe" but it caused random reboots. I then wiped my phone and did as stated in my original post and it is working smooth once again.
ikoyhn said:
Weird, did you wipe your S7 completely before doing the process? I would flash fresh nougat and try again.
Click to expand...
Click to collapse
My S7 model (SM-G930V). it's not compatible with VZW_TMO_HYBRID_PLAYSTORE_BS_FREE_STOCK_V6.zip? while installing show DEVICE: Samsung Galaxy S7 G935V
Bunrin said:
My S7 model (SM-G930V). it's not compatible with VZW_TMO_HYBRID_PLAYSTORE_BS_FREE_STOCK_V6.zip? while installing show DEVICE: Samsung Galaxy S7 G935V
Click to expand...
Click to collapse
The rom is for Verizon and T mobile devices. Your good to go.
Blade22222 said:
The rom is for Verizon and T mobile devices. Your good to go.
Click to expand...
Click to collapse
Bunrin said:
My S7 model (SM-G930V). it's not compatible with VZW_TMO_HYBRID_PLAYSTORE_BS_FREE_STOCK_V6.zip? while installing show DEVICE: Samsung Galaxy S7 G935V
Click to expand...
Click to collapse
Yup it says G935 but it also works with the G930.
ikoyhn said:
Yup it says G935 but it also works with the G930.
Click to expand...
Click to collapse
When install finish after reboot my phone show "Setup Failed....". any ideas. thanks
Bunrin said:
When install finish after reboot my phone show "Setup Failed....". any ideas. thanks
Click to expand...
Click to collapse
Did you start on a factory fresh Nougat? It must be trying to run the setup that you first have to do when you get/wipe your phone. But you should have already done this prior IF you wiped your phone completely and started from there.
Here is another guide that you might find helpful: https://forum.xda-developers.com/verizon-galaxy-s7/development/rom-t3576124
ikoyhn said:
Did you start on a factory fresh Nougat? It must be trying to run the setup that you first have to do when you get/wipe your phone. But you should have already done this prior IF you wiped your phone completely and started from there.
Here is another guide that you might find helpful: https://forum.xda-developers.com/verizon-galaxy-s7/development/rom-t3576124
Click to expand...
Click to collapse
Thanks for your support.
Is this for the Qualcomm processor?
Gon Rouge said:
Is this for the Qualcomm processor?
Click to expand...
Click to collapse
Yes the *US*S7 does have the Qualcomm processor, and this ROM does work with it. If you are looking to see if it will work for another device with the processor then I recommend looking here: https://forum.xda-developers.com/member.php?u=1949695, for more information on the ROM and compatibility.
ikoyhn said:
Yes the S7 does have the Qualcomm processor, and this ROM does work with it. If you are looking to see if it will work for another device with the processor then I recommend looking here: https://forum.xda-developers.com/member.php?u=1949695, for more information on the ROM and compatibility.
Click to expand...
Click to collapse
Not all s7s are Qualcomm, we sometimes get international users in here.
Blade22222 said:
Not all s7s are Qualcomm, we sometimes get international users in here.
Click to expand...
Click to collapse
Whoops forgot about that, I fixed my reply. Thanks for pointing it out:good:
My phone is now stuck on the boot text (Samsung Galaxy S7) have yet to see past it.
IDCM said:
My phone is now stuck on the boot text (Samsung Galaxy S7) have yet to see past it.
Click to expand...
Click to collapse
-After what step did it get stuck on the boot text?
-Did you start factory fresh?
ikoyhn said:
-After what step did it get stuck on the boot text?
-Did you start factory fresh?
Click to expand...
Click to collapse
I've got it all in working order, but to address the issue.
It was just straight after using the first Odin file. (Flashed ENG-ROOT)
Although with hours of sitting here and determination, I came to a solution using this post and many others.
I now have my S7 (Verizon) rooted and functioning with no issues.
Thank you for sharing. :highfive: :good:
IDCM said:
I've got it all in working order, but to address the issue.
It was just straight after using the first Odin file. (Flashed ENG-ROOT)
Although with hours of sitting here and determination, I came to a solution using this post and many others.
I now have my S7 (Verizon) rooted and functioning with no issues.
Thank you for sharing. :highfive: :good:
Click to expand...
Click to collapse
Glad you got it all sorted out:good:
I haven't rooted a phone in a few years but I feel like I missed a fundamental step of the root process so I have a stupid question: I get to the rom flashing step and my phone can't reboot because "Custom binary locked by SECURE BOOT (boot.img)." Then I reflash the ENG-ROOT boot.img and that same secure boot blocks because of the custom modem binary. So I just reflashed stock to get it working again, but it still gives that message if I try to install something like magisk. Am I missing something?
fjgrf said:
I haven't rooted a phone in a few years but I feel like I missed a fundamental step of the root process so I have a stupid question: I get to the rom flashing step and my phone can't reboot because "Custom binary locked by SECURE BOOT (boot.img)." Then I reflash the ENG-ROOT boot.img and that same secure boot blocks because of the custom modem binary. So I just reflashed stock to get it working again, but it still gives that message if I try to install something like magisk. Am I missing something?
Click to expand...
Click to collapse
You cannot use any custom kernels on us snapdragon models. No magisk or anything. The only root option is engboot and root.bat plus the setups to smooth it out or no root at all
Hello,
hopefully you can help me with my seemingly bricked Honor Pro 8 because of root and stock rom update procedures. I bought the phone with amazon and the package seemes to give me the information to have an EU-version of the phone.
The fastboot get-oem-information code or so also puts out the status of an European bootloader.
Regarding my working steps first of all the phone took the new update. Then I was successful in unlocking the bootloader, installing TWRP and rooting it by supersu.
But after that I was curious about the "Magisk" rooting abilities. Therefore I tried a superuser-unroot via script finding inside this forum following by flashing a extracted boot.img of an update.app file of a DUK-L09C432B130 update. After ending in a bootloop by trying the 1.30 beta version of magisk I was able to boot the normal android desktop after I uninstalled the beta version and having flashed the normal 1.20 version.
But then I tried to install 2 certain modules inside of magisk. In consequence the problem was to see the rebooted android not to load any icons. In the other side it put up the message of not having enough mobile disk memory after some minutes which couldn't be true in fact. So I tried a factory reset inside TWRP and also a full wipe. Disappointingly I haven't been successful in rebooting android once more.
Therefore I unseccessfully tried to flash the Full-OTA-MF stock rom of DUK-L09C432B130 in two versions and the L09-C432b120a via the EMUI-install mode by pressing vol+ and - and power buttons. To do that I prepared a SD card as a exfat format. But I just received the message of "software install failed" when reaching 5 %.
So I got to the frustrating point not to know what stock rom I can flash in another try or doing anything else. I would be very glad if U could help me in this desperating situation. :fingers-crossed:
Thanks and best regards.
Can you boot to erecovery?
adriansticoid said:
Can you boot to erecovery?
Click to expand...
Click to collapse
I can but it just puts out the message "Getting package info failed"
Filo83 said:
I can but it just puts out the message "Getting package info failed"
Click to expand...
Click to collapse
Please try another version of firmware.
adriansticoid said:
Please try another version of firmware.
Click to expand...
Click to collapse
That is my problem not to know which version to use because three dowloaded EU-versions weren't successful to install. It resulted in an error at 5 % of the 3-buttons-install mechanism.
Filo83 said:
Hello,
hopefully you can help me with my seemingly bricked Honor Pro 8 because of root and stock rom update procedures. I bought the phone with amazon and the package seemes to give me the information to have an EU-version of the phone.
The fastboot get-oem-information code or so also puts out the status of an European bootloader.
Regarding my working steps first of all the phone took the new update. Then I was successful in unlocking the bootloader, installing TWRP and rooting it by supersu.
But after that I was curious about the "Magisk" rooting abilities. Therefore I tried a superuser-unroot via script finding inside this forum following by flashing a extracted boot.img of an update.app file of a DUK-L09C432B130 update. After ending in a bootloop by trying the 1.30 beta version of magisk I was able to boot the normal android desktop after I uninstalled the beta version and having flashed the normal 1.20 version.
But then I tried to install 2 certain modules inside of magisk. In consequence the problem was to see the rebooted android not to load any icons. In the other side it put up the message of not having enough mobile disk memory after some minutes which couldn't be true in fact. So I tried a factory reset inside TWRP and also a full wipe. Disappointingly I haven't been successful in rebooting android once more.
Therefore I unseccessfully tried to flash the Full-OTA-MF stock rom of DUK-L09C432B130 in two versions and the L09-C432b120a via the EMUI-install mode by pressing vol+ and - and power buttons. To do that I prepared a SD card as a exfat format. But I just received the message of "software install failed" when reaching 5 %.
So I got to the frustrating point not to know what stock rom I can flash in another try or doing anything else. I would be very glad if U could help me in this desperating situation. :fingers-crossed:
Thanks and best regards.
Click to expand...
Click to collapse
you download the nocheck recoveries from my rebranding guide, download the corresponding firmware by morph (important!), flash both recovery images just like stated in the guide, boot into recovery mode like you would do to boot into twrp, do a factory reset, reboot and insert the microsd with the dload folder from extracted downloaded firmware and boot into force dload mode (vol+ and vol- and power) - the installation should start now and reset everything back to full stock.
Regards
Thank you very much OldDroid. You're my hero. It worked fine.
But to install the new 130-update the phone starts inside TWRP and ends with an "error 9" and the words "block image verify", "asserts failed". Could it be possible to perform the update by starting the forced update process by pressing the three hardware buttons on booting? And is it possible not to wipe the data and losing root by using a update?
Viele Grüße aus Berlin nach Berlin
Filo83 said:
Thank you very much OldDroid. You're my hero. It worked fine.
But to install the new 130-update the phone starts inside TWRP and ends with an "error 9" and the words "block image verify", "asserts failed". Could it be possible to perform the update by starting the forced update process by pressing the three hardware buttons on booting? And is it possible not to wipe the data and losing root by using a update?
Viele Grüße aus Berlin nach Berlin
Click to expand...
Click to collapse
OTA packages cannot be installed via twrp at the moment
you should use stock recovery for that!
Best regards
Grüße zurrück aus Berlin nach Berlin
Could you explain me a bit more please? Is it the standard system update ins the systems menu, here it wants to load the 2,9 GB file. Updating this way with the "no check recovery" resulted in an checking error at about 12 %.
Or could it be via recovery shortly after starting the phone? But there are no choices to choice. It just automaticely begins installing something stopping at 5 %.
Hope you can help one more please.
Filo83 said:
Could you explain me a bit more please? Is it the standard system update ins the systems menu, here it wants to load the 2,9 GB file. Updating this way with the "no check recovery" resulted in an checking error at about 12 %.
Or could it be via recovery shortly after starting the phone? But there are no choices to choice. It just automaticely begins installing something stopping at 5 %.
Hope you can help one more please.
Click to expand...
Click to collapse
soooo, if you flashed one of @-=MoRpH=- 's firmwares, your device is back to stock and the recoveries have been overwritten again! I don't recommend flashing OTA updates or other things through the NoCheck version as it is only intended for worst-case cenarios.
But could you tell me the single steps to update from Morph's DUK-L09C432B120 version to the newest version DUK-L09C432B130?
I only got errors to update the firmware DUK-L09C432B130 from the stock rom thread in this forum and the russian website mentioned there.
Filo83 said:
But could you tell me the single steps to update from Morph's DUK-L09C432B120 version to the newest version DUK-L09C432B130?
I only got errors to update the firmware DUK-L09C432B130 from the stock rom thread in this forum and the russian website mentioned there.
Click to expand...
Click to collapse
extract the firmware and flash manualy using fastboot
thilak devraj said:
extract the firmware and flash manualy using fastboot
Click to expand...
Click to collapse
That is just needed to be done as last resort. Better stick with dload.
adriansticoid said:
That is just needed to be done as last resort. Better stick with dload.
Click to expand...
Click to collapse
he said he got some errors doing dload, so this method works too
thilak devraj said:
he said he got some errors doing dload, so this method works too
Click to expand...
Click to collapse
He must find the right firmware first.
adriansticoid said:
He must find the right firmware first.
Click to expand...
Click to collapse
finding a firmware for huawei devices is a pain in the ass, you know
thilak devraj said:
finding a firmware for huawei devices is a pain in the ass, you know
Click to expand...
Click to collapse
That's why we have Firmware Finder.
adriansticoid said:
That's why we have Firmware Finder.
Click to expand...
Click to collapse
even in firmware finder, it will be difficult sometimes for sone devices
thilak devraj said:
even in firmware finder, it will be difficult sometimes for sone devices
Click to expand...
Click to collapse
Maybe. But they are constantly improving.
adriansticoid said:
Maybe. But they are constantly improving.
Click to expand...
Click to collapse
i appreciate the firmware finder, but sometimes, its just inappropriate
Hi all. I'm having a few niggles on my M8.
LineageOS v13.0 was the only version I could install successfully without any error in TWRP so I've ran with it and I'm looking for some help.
I'm experiencing random app crashes where certain apps close and I get the message "Unfortunately, xyz has stopped running". Some apps run fine but can randomly close (google play store will crash quite often) and others I'm not able to run at all (Evie Launcher for example will not open without getting the *has stopped running* error message). It's gotten to the point where the phone is unusable because it can't run anything.
I'm also running Magisk for SU but was having exactly the same problems when I was running SuperSU on a previous install.
Any help or insight truly appreciated! Thanks
Are you using the newest TWRP version?
Saleen28 said:
Are you using the newest TWRP version?
Click to expand...
Click to collapse
Was running 2.8.6.0, now flashed to the latest 3.1.1.0, will try re-installing and let you know how I get on. Cheers
Update: The newest version of TWRP for the M8s I could find was twrp-3.1.1. I flashed the new version of TWRP, did a factory reset, flashed LOS 13 again and still the same problem
kin'cheezus said:
Update: The newest version of TWRP for the M8s I could find was twrp-3.1.1. I flashed the new version of TWRP, did a factory reset, flashed LOS 13 again and still the same problem
Click to expand...
Click to collapse
Wait, so do you have M8 or M8s? Those are different devices you know.
Saleen28 said:
Wait, so do you have M8 or M8s? Those are different devices you know.
Click to expand...
Click to collapse
Yep I've got the M8s, yes I'm now aware I've posted in the wrong forum lol :good:
Point still stands, I'm using all the correct ported tools and still getting nowhere.
Ah, that narrows it down.
There's only los13 for m8s afaik, this one https://forum.xda-developers.com/ht...al/lineageos-13-1-htc-one-m8s-m8qlul-t3629761
You've been trying roms for regular m8, right? I'm surprised they even booted up.
Saleen28 said:
Ah, that narrows it down.
There's only los13 for m8s afaik, this one https://forum.xda-developers.com/ht...al/lineageos-13-1-htc-one-m8s-m8qlul-t3629761
You've been trying roms for regular m8, right? I'm surprised they even booted up.
Click to expand...
Click to collapse
Nope I'm using that ROM you linked above
kin'cheezus said:
Nope I'm using that ROM you linked above
Click to expand...
Click to collapse
Whoops, missed that part in the first post, sorry :silly:
No idea what's exactly wrong as the twrp shows no errors as you've said.
Are you using an sd card as an adoptable storage? Stock rom works without problems?
all I want is a completely stock version of android, just android and none of the skinned crap I'll do that myself with Evie Launcher, I just want stock android but it seems theres ROMs for every other variant of this phone EXCEPT for the one I have, yes I could have bought a pixel but money and I like the looks of samsungs. is anyone able to help me out here? I've flashed custom roms and rooted all the phones I've had in the past but it seems there is nothing at all for this version of the A50
tripleplug said:
all I want is a completely stock version of android, just android and none of the skinned crap I'll do that myself with Evie Launcher, I just want stock android but it seems theres ROMs for every other variant of this phone EXCEPT for the one I have, yes I could have bought a pixel but money and I like the looks of samsungs. is anyone able to help me out here? I've flashed custom roms and rooted all the phones I've had in the past but it seems there is nothing at all for this version of the A50
Click to expand...
Click to collapse
You have Gsi rom for flashing you need just twrp and plenty of Gsi
muhamet said:
You have Gsi rom for flashing you need just twrp and plenty of Gsi
Click to expand...
Click to collapse
Is it for my exact model of the phone though? I dont want to brick my phone or install stuff that isn't the correct version for the phone I have
tripleplug said:
Is it for my exact model of the phone though? I dont want to brick my phone or install stuff that isn't the correct version for the phone I have
Click to expand...
Click to collapse
Well you have FN model (Europe) i use FN
muhamet said:
Well you have FN model (Europe) i use FN
Click to expand...
Click to collapse
Yeah but on the end of FN it has "/DS" on it, so I dont know if that changes anything
tripleplug said:
Yeah but on the end of FN it has "/DS" on it, so I dont know if that changes anything
Click to expand...
Click to collapse
Yea and I have that model
muhamet said:
Yea and I have that model
Click to expand...
Click to collapse
whaaaaat? so you have a custom rom running on the same device that I have??? I've spent ages tryna find one for my device and I couldn't, either that or I'm just stupid and wasnt reading stuff properly lol
tripleplug said:
whaaaaat? so you have a custom rom running on the same device that I have??? I've spent ages tryna find one for my device and I couldn't, either that or I'm just stupid and wasnt reading stuff properly lol
Click to expand...
Click to collapse
You just need to flash twrp
Ok, I don't get what I am doing wrong. Got twrp 3.3.1.0 in place, I can flash the GSI rom to system. Then it just gets stuck several hours with the google logo and (boot) progress bar. Once 8 hours and once 12+ hours until I decided this wasn't going to work.
It just never gets past the boot logo.
inglorious_bastard said:
Ok, I don't get what I am doing wrong. Got twrp 3.3.1.0 in place, I can flash the GSI rom to system. Then it just gets stuck several hours with the google logo and (boot) progress bar. Once 8 hours and once 12+ hours until I decided this wasn't going to work.
It just never gets past the boot logo.
Click to expand...
Click to collapse
Try a different GSI, for example Havoc OS 3.1. My guess is that you're trying to flash Pixel Experience, or something similar?
Skytex_ said:
Try a different GSI, for example Havoc OS 3.1. My guess is that you're trying to flash Pixel Experience, or something similar?
Click to expand...
Click to collapse
I will give that a try, thanks for pointing out. I have been experimenting with the pixel experience GSI and the resurrection remix GSI which both left me with a phone that didn't boot.
inglorious_bastard said:
I will give that a try, thanks for pointing out. I have been experimenting with the pixel experience GSI and the resurrection remix GSI which both left me with a phone that didn't boot.
Click to expand...
Click to collapse
Flash only Phh source gsi.Dont flash Sgsi,they are oem sgsi.Some will boot,some of them will stay on bootanimation.Gsi with phh source will boot
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.