Related
I have G925S model and 2G network not work stable because the stock rom only have 3G and LTE option.
So someone have G925F model can use this software and backup Radio image, please?
https://play.google.com/store/apps/details?id=ma.wanam.partitions
Thanks.
Bump
you could also download your firmware..rename the tar.md5 to tar and extract it..voila
Odin don't let me flash G925F modem. Failed everytime. I think bootloader not accept another baseband.
kakahoho said:
Odin don't let me flash G925F modem. Failed everytime. I think bootloader not accept another baseband.
Click to expand...
Click to collapse
also not if you repack the modem with the tool posted in development thread..?
I tried repack modem.bin to tar.md5 and failed too.
kakahoho said:
I tried repack modem.bin to tar.md5 and failed too.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=3101195
by using this tool works..do it with the multiple file option..
Alex-V said:
http://forum.xda-developers.com/showthread.php?t=3101195
by using this tool works..do it with the multiple file option..
Click to expand...
Click to collapse
I can't flash G925F's modem via Odin. Even with SkipSoft ToolKit you mention above. I think G925S carrier bootloader prevent flash another radio/modem.
is there a fastboot method for Samsung..? that was good on HTC
Alex-V said:
is there a fastboot method for Samsung..? that was good on HTC
Click to expand...
Click to collapse
Do you know another flash modem.bin without Odin? I tried Flashfire but not successful.
those 2 I think..not sure about fastboot using Adb..
not Googled yet if there's fastboot also with Samsung..
I need help in the problem of non-completion of the installation of the firmware
phone Galaxy S6 Edge Model SM-G925I
Root was rooting , When you attempt the firmware installation is not completed See attached photo .
The file was the inauguration of linkage here and then returned to life, but so far the inauguration of the firmware can not be the same problem .
http://forum.xda-developers.com/galaxy-s6-edge/orig-development/cf-auto-root-t3056631/page16
Thank you pending resolution of the problem
you need to have a pit file that matches you device..or you need to have the firmware file your phone comes with..
Alex-V said:
you need to have a pit file that matches you device..or you need to have the firmware file your phone comes with..
Click to expand...
Click to collapse
Yes it is true I read it but how do I get the file Pit ..? , thank you very much
Abdulaziz7888 said:
Yes it is true I read it but how do I get the file Pit ..? , thank you very much
Click to expand...
Click to collapse
now..comes the part that is not simple..there non online..you must get it from your phone..the best is a rooted phone..there are some tutorials and tools online..simple google search it..I tried but was tired with my non rooted phone..
BTW..what you can try is to extract the firmware and make your own with only system and kernel firmware..look in the general thread for new Vodafone firmware..I will try that also...it should bring a few updates..
Alex-V said:
you need to have a pit file that matches you device..or you need to have the firmware file your phone comes with..
Click to expand...
Click to collapse
Alex-V said:
now..comes the part that is not simple..there non online..you must get it from your phone..the best is a rooted phone..there are some tutorials and tools online..simple google search it..I tried but was tired with my non rooted phone..
BTW..what you can try is to extract the firmware and make your own with only system and kernel firmware..look in the general thread for new Vodafone firmware..I will try that also...it should bring a few updates..
Click to expand...
Click to collapse
Sorry I do not know how to extract a file from the firmware, I will try, don't leave me I need your help, thank you very much Alex-v
Abdulaziz7888 said:
Sorry I do not know how to extract a file from the firmware, I will try, don't leave me I need your help, thank you very much Alex-v
Click to expand...
Click to collapse
up up
Abdulaziz7888 said:
up up
Click to expand...
Click to collapse
I got the same issue many times with some regional FWs on my old GS5, just follow these steps and you should be ok, i guess it's a mismatched "hidden" partition size, you don't need anyway, i contains only some bloats most of the times.
- Extrat the FW with any archiving tool (i recommend 7zip).
- Remove "Hidden.img"
- Repack all other files as "tar" archive with 7zip, OR linux command line "tar -cvf G925I_AOD1.tar sboot.bin cm.bin recovery.img boot.img cache.img modem.bin system.img"
- Flash it through Odin
wanam said:
I got the same issue many times with some regional FWs on my old GS5, just follow these steps and you should be ok, i guess it's a mismatched "hidden" partition size, you don't need anyway, i contains only some bloats most of the times.
- Extrat the FW with any archiving tool (i recommend 7zip).
- Remove "Hidden.img"
- Repack all other files as "tar" archive with 7zip, OR linux command line "tar -cvf G925I_AOD1.tar sboot.bin cm.bin recovery.img boot.img cache.img modem.bin system.img"
- Flash it through Odin
Click to expand...
Click to collapse
Thank you my friend, but how do I package the files using ZIP7. I tried a lot to transfer tar and gzip but ODIN does not recognize the file, please I need an explanation for this, I spent 3 hours trying. Please wanam
wanam said:
I got the same issue many times with some regional FWs on my old GS5, just follow these steps and you should be ok, i guess it's a mismatched "hidden" partition size, you don't need anyway, i contains only some bloats most of the times.
- Extrat the FW with any archiving tool (i recommend 7zip).
- Remove "Hidden.img"
- Repack all other files as "tar" archive with 7zip, OR linux command line "tar -cvf G925I_AOD1.tar sboot.bin cm.bin recovery.img boot.img cache.img modem.bin system.img"
- Flash it through Odin
Click to expand...
Click to collapse
Thank you so much, I hope to return to the last reply to you there, know that you are available here more, await you there.
Try this Rom, unpack and flash it through Odin.
wanam said:
Try this Rom, unpack and flash it through Odin.
Click to expand...
Click to collapse
You are a great person, thank you so much . :laugh::laugh::laugh:
Help!!! Sw rev. Check fail. Device= 2. Binary=1.// efs corrupted s6 edge 64gb
hi I have a s6 edge 64gb from south Africa and I have rooted it. After a while I felt the phone was lagging and decided to unroot and flash stock firmware I did so and then my efs got corrupted now im stuck. after doing a bit of research I decided to flash a official rom from another country and its stuck on the samsung s6 edge powered by android screen....... please help
hi there.
soooo I kinda bricked my mate 10 lite (RNE-L21C432)
bootloader is unlocked, rooted.
I tried flashing a flashable rom and got a bootloop...sooooo
I downloaded the firmware via huawei firmware finder , the oreo one.
I opened the UPDATE.APP via huawei update extractor, there are alot of files, so can you please tell me what files I need to extract and flash to unbrick my phone?
I extracted system, kernel, vendor and odm for now, system flashed fine. but I cant flash kernel it gives me the error FAILED: remote: command not allowed
can you pleaste help me?
Edit: I can flash system, I did flash kernel, I can flash recovery too, but when I try to flash anything else, it gives me that error
Edit2: can someone tell me which files do I need to extract via huawei update extractor to flash? I know that system.img is one of them
konopla4 said:
hi there.
soooo I kinda bricked my mate 10 lite (RNE-L21C432)
bootloader is unlocked, rooted.
I tried flashing a flashable rom and got a bootloop...sooooo
I downloaded the firmware via huawei firmware finder , the oreo one.
I opened the UPDATE.APP via huawei update extractor, there are alot of files, so can you please tell me what files I need to extract and flash to unbrick my phone?
I extracted system, kernel, vendor and odm for now, system flashed fine. but I cant flash kernel it gives me the error FAILED: remote: command not allowed
can you pleaste help me?
Click to expand...
Click to collapse
Check if you're still FRP unlock in Fastboot.
ante0 said:
Check if you're still FRP unlock in Fastboot.
Click to expand...
Click to collapse
Both bootloader and from are unlocked
konopla4 said:
Both bootloader and from are unlocked
Click to expand...
Click to collapse
Ah, didn't see your edit.
Fastboot is limited in flashing, you can't flash everything.
From memory I think it is:
System, vendor, recovery_ramdisk, recovery_vendor, recovery_vbmeta, ramdisk, kernel, cache, userdata
You could use HWOTA for Mate 10 Lite if you can get into stock recovery, as it will flash the full update.app rather than the limited partitions fastboot can flash.
https://forum.xda-developers.com/ma...development/hwota-huawei-mate10-lite-t3777115
ante0 said:
Ah, didn't see your edit.
Fastboot is limited in flashing, you can't flash everything.
From memory I think it is:
System, vendor, recovery_ramdisk, recovery_vendor, recovery_vbmeta, ramdisk, kernel, cache, userdata
Click to expand...
Click to collapse
So I can flash all of these without getting the error and it'll will restore my system?
I remember on p8 lite I needed to flash only system, boot, and cust. To restore the system. It was much easier.
konopla4 said:
So I can flash all of these without getting the error and it'll will restore my system?
I remember on p8 lite I needed to flash only system, boot, and cust. To restore the system. It was much easier.
Click to expand...
Click to collapse
Edited while you posted, use HWOTA if you can get into stock recovery
https://forum.xda-developers.com/ma...development/hwota-huawei-mate10-lite-t3777115
ante0 said:
Edited while you posted, use HWOTA if you can get into stock recovery
https://forum.xda-developers.com/ma...development/hwota-huawei-mate10-lite-t3777115
Click to expand...
Click to collapse
Yeah, just noticed.
So hwota. I don't have the "stock recovery" I can only flash the recovery that I extract from update.app
The one I flash is bugged for some reason, probably because it's from a slightly different system than the one I had.
konopla4 said:
Yeah, just noticed.
So hwota. I don't have the "stock recovery" I can only flash the recovery that I extract from update.app
The one I flash is bugged for some reason, probably because it's from a slightly different system than the one I had.
Click to expand...
Click to collapse
If it can be booted into it should work. HWOTA will replace it anyway with a no-check recovery. Or you could use TWRP by Caucava21 and use HuRUpdater (https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279) to update from TWRP.
Either way will work.
ante0 said:
If it can be booted into it should work. HWOTA will replace it anyway with a no-check recovery. Or you could use TWRP by Caucava21 and use HuRUpdater (https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279) to update from TWRP.
Either way will work.
Click to expand...
Click to collapse
Waaaait it, I can update from TWRP?
Or is it a specialized one?
konopla4 said:
Waaaait it, I can update from TWRP?
Or is it a specialized one?
Click to expand...
Click to collapse
It's a script, but it needs a TWRP that's compatible. The one by Catuva21 is (or so I've heard).
The following is a guide for repairing failed to mount efs and dm-verify fail (drk error)
We finally did it ~~~
Warning - We will not take any responsibility for your device. Follow the steps at your own risk. If your device is Knox 0, This guide would convert it into Knox 1 due to TWRP. For solutions that does not convert to knox 1 check out payed remote solutions. Everything on your device will be reset, including efs partition. You will need backup of efs.
Test on N950F binary 4 may work on other exynos models comment below if it worked for other samsung devices.
Problem Detail -
Bootloop with samsung stock firmware boot logo.
Recovery error E:Failed to mount /efs (Invalid argument) or dm-verity verification failed...
Device cannot boot into Factory binary or Stock Rom
Actions that could cause this problem -
Flashing a non-signed efs.img by odin
Corrupt flash of efs partition.
Note - Must have efs backup for device to work (very important)
Any error that cause bootloop would show in recovery required if
Files Required
Latest Odin (recommend 3.13)
Working Stock firmware and Combination file (same binary as bootloader)
PC
Winrar or 7zip etc
Solution for efs failed bootloop-
Extract Stock firmware AP file (rename .md5 to .tar)
Rename dqmdbg.img to efs.img (or smallest image must be smaller than 8000 KB). Extract Dqmdbg.img.lz4 so it’s just “Dqmdbg.img” and then rename it to efs.img and put that one in a tar. Other option is downloading a file that’s already made this way if your bootloader is binary 4, Saves you trouble of extracting / renaming: http://www.mediafire.com/file/589wucja9rk2v8f/efs.tar/file (if you download this file just move onto number 3)
Add file new efs.img into tar archive.
Flash tar as AP file in odin + download mode
Reboot download mode
Flash Combination with odin + nand erase option on Edit: suggest you to flash stock rom first and oem unlock, don't need to wait for 7 days if imei is 0000 skip combination step
Device Should boot into Factory binary
Use IME to restore imei using *#06# (or imei 0000 in stock rom) Edit: This step is not required if efs backup is restored successful
Your device should have dm-verify failed in recovery due to drk error
Continue drk bypass for dm verify error below to continue
Solution for dm-verify error (also known as drk bypass - but temporary read note)-
Extract Stock firmware AP file
Make a copy of boot.img and delete recovery.img
Note - if files is boot.img.lz4 format change name to recovery.img.lz4
Rename boot.img copy to recovery.img
Add all the files (including other files extracted) to tar.
Flash Modded AP file with BL, CP, CSC (nand erase not required)
The phone will boot into stock firmware
Note- cannot reboot, will stuck at dm-verify error again and need to flash modded AP again.
Wait 7 days to oem unlock phone or use 7 day bypass by changing dates (not always work, keep trying, don’t reboot, worked for Samsunguser932 Edit: Imei must be 0000)
Edit: oem unlock will fix drk - if not you must follow next step
Once oem unlock flash TWRP and restore efs backup Edit: if you haven't fixed imei fix now by *#06# with combination file
Flash stock firmware once again by odin (stock, not modded)
Done - phone is back to normal
If you cannot be bothered doing by yourself you can pay https://www.facebook.com/gsm.xraxxx/ to do this.
(after he used plexihub to fix phone, i believe he is using similar method. It doesn’t seem fair to post this guide as i’ll be damaging his income but it seemed also unfair to keep this as a secret. If you want to donate to me please donate to him and his team instead at https://spacial-file.com/ or paypal [email protected] Thx)
Special Thanks to -
Samsunguser932 - testing this guide you can see his post on https://forum.xda-developers.com/galaxy-note-8/help/note-8-phone-booting-efs-restore-t3830209
Ravi Kumar - for his help in giving me clues how to fix.
Resources: (where i got most my info)
https://forum.xda-developers.com/galaxy-note-8/help/unbrick-methods-t3703767
https://forum.xda-developers.com/galaxy-note-8/help/to-fix-efs-secondary-note-8-t3785600
https://forum.xda-developers.com/galaxy-note-8/help/note-8-phone-booting-efs-restore-t3830209
http://forum.gsmhosting.com/vbb/f453/samsung-s8-g955f-2426383/
Comment below for help.
Give me a thanks if you find this guide very/extremely helpful. :angel:
Share it with those in need.
edit: not all images were able to upload
update: to skip 7 day oem unlock imei must be 0000
The best method for bypassing oem unlock for 7 days.
Requirements - clean phone with stock firmware, samsung account logged in, imei 0000
Go to setting and check for manual update. This will fail/stuck and oem unlock would appear in development settings
Reserved
hello , i have samsung j737t with bad efs ,
Recovery error E:Failed to mount /efs (Invalid argument)
any help please ,i have cert in hand
maxpatri9 said:
hello , i have samsung j737t with bad efs ,
Recovery error E:Failed to mount /efs (Invalid argument)
any help please ,i have cert in hand
Click to expand...
Click to collapse
Try the above guide. This guide isn't just designed for the note 8.
from what file i need to create efs.img for s8+ g955F?
ditternation said:
from what file i need to create efs.img for s8+ g955F?
Click to expand...
Click to collapse
You do not need an efs.img to repair efs failed to mount. It is only required for the functionality of the phone (sim). This guide would work without an efs.img, it is recommended to install a custom rom after the guide. Even though this guide can allow you phone to work, but due to drk/dm-verify errors, it is currently impossible to restore the phone to the original state.
Note - you'll need to find someone that is kind enough to share a copy/backup of their efs.img g955F. Most people think it is illegal to share as the efs.img contain imei, but with cpid devices, the imei would be overridden by your current device. Most importantly you need to change the serial number in the SVC (or else you will have the same serial number as the person sharing.
plz my problem is oem lock on, frp on and drk error. i have combination file and stock can your guide work for me?
soundn said:
plz my problem is oem lock on, frp on and drk error. i have combination file and stock can your guide work for me?
Click to expand...
Click to collapse
This would only work if you're still on binary 3. Follow the steps for DM verity fix with 7.1.1 firmware. Flash stock 7.1.1 with replaced boot.img using Odin and fix frp using adb (guides online to enable adb). Wait for 7 day OEM unlock (no method to skip do not restart). Flash twrp and use twrp to flash custom ROM or DM verify fix.
Note - this method would fix function ability of the phone only if efs is not corrupted. (If you had paid someone to fix efs, this would not work). Finally the phone will become Knox 1 and normal update functions might not work. Practically makes the phone unable to resell as a working phone.
Hello. My efs partition was erased by a z3x box. Or an octopus, I do not know. I followed your instructions. The IME combination is empty. I install a modified firmware, it works but I can not enter the Samsung account (crashing), I can not check the system updates (infinite device registration). Should I wait 7 days before the OEM unlock? Will it work?
@Alarg read post 2 to skip 7 days. Infinite device registration should make OEM unlock show with samsung account logged in. OEM unlock must be first done before installing modified firmware (suggest kernel). You must have backup of efs, a backup from another phone will not work.
bluecub1st said:
@Alarg read post 2 to skip 7 days. Infinite device registration should make OEM unlock show with samsung account logged in.
Click to expand...
Click to collapse
I can't log in Samsung account (processing failure). Imei unknown, s/n 0000000000 This method does not work for me.
@Alarg Which firmware ver are you using?
Have you tried nand flash combination file and then flash firmware (before boot, hold download mode buttons so the phone won't boot to factory mode). I do not see a reason why Samsung account would not work, try another ver maybe the version you downloaded is corrupted.
bluecub1st said:
The following is a guide for repairing failed to mount efs and dm-verify fail (drk error)
We finally did it ~~~
Warning - We will not take any responsibility for your device. Follow the steps at your own risk. If your device is Knox 0, This guide would convert it into Knox 1 due to TWRP. For solutions that does not convert to knox 1 check out payed remote solutions. Everything on your device will be reset, including efs partition. You will need backup of efs.
Test on N950F binary 4 may work on other exynos models comment below if it worked for other samsung devices.
Problem Detail -
Bootloop with samsung stock firmware boot logo.
Recovery error E:Failed to mount /efs (Invalid argument) or dm-verity verification failed...
Device cannot boot into Factory binary or Stock Rom
Actions that could cause this problem -
Flashing a non-signed efs.img by odin
Corrupt flash of efs partition.
Note - Must have efs backup for device to work (very important)
Any error that cause bootloop would show in recovery required if
Files Required
Latest Odin (recommend 3.13)
Working Stock firmware and Combination file (same binary as bootloader)
PC
Winrar or 7zip etc
Solution for efs failed bootloop-
Extract Stock firmware AP file (rename .md5 to .tar)
Rename dqmdbg.img to efs.img (or smallest image must be smaller than 8000 KB). Extract Dqmdbg.img.lz4 so it’s just “Dqmdbg.img” and then rename it to efs.img and put that one in a tar. Other option is downloading a file that’s already made this way if your bootloader is binary 4, Saves you trouble of extracting / renaming: http://www.mediafire.com/file/589wucja9rk2v8f/efs.tar/file (if you download this file just move onto number 3)
Add file new efs.img into tar archive.
Flash tar as AP file in odin + download mode
Reboot download mode
Flash Combination with odin + nand erase option on Edit: suggest you to flash stock rom first and oem unlock, don't need to wait for 7 days if imei is 0000 skip combination step
Device Should boot into Factory binary
Use IME to restore imei using *#06# (or imei 0000 in stock rom) Edit: This step is not required if efs backup is restored successful
Your device should have dm-verify failed in recovery due to drk error
Continue drk bypass for dm verify error below to continue
Solution for dm-verify error (also known as drk bypass - but temporary read note)-
Extract Stock firmware AP file
Make a copy of boot.img and delete recovery.img
Note - if files is boot.img.lz4 format change name to recovery.img.lz4
Rename boot.img copy to recovery.img
Add all the files (including other files extracted) to tar.
Flash Modded AP file with BL, CP, CSC (nand erase not required)
The phone will boot into stock firmware
Note- cannot reboot, will stuck at dm-verify error again and need to flash modded AP again.
Wait 7 days to oem unlock phone or use 7 day bypass by changing dates (not always work, keep trying, don’t reboot, worked for Samsunguser932 Edit: Imei must be 0000)
Once oem unlock flash TWRP and restore efs backup Edit: if you haven't fixed imei fix now by *#06# with combination file
Flash stock firmware once again by odin (stock, not modded)
Done - phone is back to normal
If you cannot be bothered doing by yourself you can pay https://www.facebook.com/gsm.xraxxx/ to do this.
(after he used plexihub to fix phone, i believe he is using similar method. It doesn’t seem fair to post this guide as i’ll be damaging his income but it seemed also unfair to keep this as a secret. If you want to donate to me please donate to him and his team instead at https://spacial-file.com/ or paypal [email protected] Thx)
Special Thanks to -
Samsunguser932 - testing this guide you can see his post on https://forum.xda-developers.com/galaxy-note-8/help/note-8-phone-booting-efs-restore-t3830209
Ravi Kumar - for his help in giving me clues how to fix.
Resources: (where i got most my info)
https://forum.xda-developers.com/galaxy-note-8/help/unbrick-methods-t3703767
https://forum.xda-developers.com/galaxy-note-8/help/to-fix-efs-secondary-note-8-t3785600
https://forum.xda-developers.com/galaxy-note-8/help/note-8-phone-booting-efs-restore-t3830209
http://forum.gsmhosting.com/vbb/f453/samsung-s8-g955f-2426383/
Comment below for help.
Give me a thanks if you find this guide very/extremely helpful. :angel:
Share it with those in need.
edit: not all images were able to upload
update: to skip 7 day oem unlock imei must be 0000
Click to expand...
Click to collapse
thanx! for your guide but i have this problem after taking an official OTA!
DM-Verity ERRor!
any help will be greatly appreciated!
Can someone explain me what is this EFS ?? I'm flashing roms many many times and I hadn't such problems etc
klisza1993 said:
Can someone explain me what is this EFS ?? I'm flashing roms many many times and I hadn't such problems etc
Click to expand...
Click to collapse
Just Google "EFS android"
pixel989 said:
thanx! for your guide but i have this problem after taking an official OTA!
DM-Verity ERRor!
any help will be greatly appreciated!
Click to expand...
Click to collapse
Follow
Solution for dm-verify error (also known as drk bypass - but temporary read note)-
Extract Stock firmware AP file
Make a copy of boot.img and delete recovery.img
Note - if files is boot.img.lz4 format change name to recovery.img.lz4
Rename boot.img copy to recovery.img
Add all the files (including other files extracted) to tar.
Flash Modded AP file with BL, CP, CSC (nand erase not required)
The phone will boot into stock firmware
Note- cannot reboot, will stuck at dm-verify error again and need to flash modded AP again.
Wait 7 days to oem unlock phone or use 7 day bypass by changing dates (not always work, keep trying, don’t reboot, worked for Samsunguser932 Edit: Imei must be 0000)
Once oem unlock flash TWRP and restore efs backup Edit: if you haven't fixed imei fix now by *#06# with combination file
Flash stock firmware once again by odin (stock, not modded)
Done - phone is back to normal
Click to expand...
Click to collapse
Note -
dm verify cannot be completely fixed, it can only be bypassed (in the system by flashing no dm verify).
You will need to wait for 7 days for oem unlock (there is no method to skip oem unlock)
Warranty will be voided (KNOX 1) - don't think there is a method to avoid tripping knox.
Suggest installing a custom rom after oem unlock (many reports that no dm verify on latest oreo does not work without root)
klisza1993 said:
Can someone explain me what is this EFS ?? I'm flashing roms many many times and I hadn't such problems etc
Click to expand...
Click to collapse
EFS partition is not touched when flashing roms (they actually do but in a safe way), only retards like I would try to mod efs partition.
Hi guys, will it work in my case? https://ibb.co/mJRcHK
Device is SM-N950N FRP ON and OEM ON.
What kind of solution should I follow?
@Anvar2005 - This looks like a drk verify error. Which binary are you on? frp bypass only works with binary 3. You will not find anything for frp unlock on this forum. Same steps for drk verify but use nougat.
I wanted to root my A52 5G (SM-A526B) i first unlocked the bootloader
then i downloaded my Firmware with Frija and patched the boot.img with Magisk then i went into download mode and flashed it with Odin
Odin gave me a Green PASS Message and i knew i needed to factory reset with recovery mode but i couldnt get into it then i got into a boot loop with the Samsung Galaxy Bootlogo
then i tried to flash Twrp with odin to factory reset because i couldnt get into the stock recovery mode Odin again gave me a PASS Message then i tried to get into recovery mode but it still didnt work and now im trying to flash Stock Firmware but cant get it to work what should i do
The picture is what happens when i try to boot please help me to flash stock firmware
When i try to flash Stock Firmware it fails at the very end on vbmeta.img
The a52 5g doesn't have twrp currently. Also, you might have flashed the incorrect firmware.
Plus, just for you to know, you do not need to do factory reset after flashing your firmware. What steps have you taken to flash this firmware? How did you patch magisk? Show the steps so we can help you cuz you might have done something wrong
Ok it seems that your mistake here is that you are trying to flash boot.img. so what you actually suppose to do is to download the firmware, take the AP file from the firmware(don't extract the file!). Then, move the file to your phone and download magisk on your phone. You will see that magisk is offering you to install magisk on the top corner of your screen. You need to choose to patch the file, the AP file. Once magisk done, on your file explorer(probably in downloads) a file called "magisk_patched xxxx.tar" (the xxxx representing the version of magisk). Take this file and copy it to your computer, and on Odin, instead of using the AP file, use the magisk file. Boom, done. Now first, we need to recover your phone to its original condition. Take the AP file and flash it(not the boot.img!)
DownBaddie said:
When i try to flash Stock Firmware it fails at the very end on vbmeta.img
Click to expand...
Click to collapse
Try flashing other parts of firmware, not just AP
i.e. BL, CSC and CP
But don't add home_csc (USERDATA).
If all fails, you can use EDL mode to flash firmware
How To Flash Qualcomm MBN Firmware Via QPST tool
If your device is based on Qualcomm’s CPU and you’re searching for an easy way to flash the device’s stock ROM, here ends your search. You just need the QPST tool and the instructions here to guide you. Follow the instructions below to get you started. Prerequisites: Qualcomm QPST tool –...
www.leakite.com