Hi
I tried to install stock Android 12 on my samsung A31. Due to some error in the PC the installation stopped halfway.
I used FRP hijacker tool to get back to download window. However now the error shows "Partitions prism. Reason prism: Error verifying vbmeta image : invalid vbmeta header(6) "
And when I tried to flash using odin again it says setup connection. Complete failed.
Is there no way to get this phone working? Please help!!
Repartition definitely should be off. Also make sure you have the right file to flash, I know there are some different Note 10 tab models. Easiest way to download the latest firmware version is Frija, it doesnt have the limited download speed like Sammobile. The .enc4 file it will give you can easily be extracted just like a .zip file omegle xender .
You shouldt need the .pit file when repartition is off
Junkun007 said:
Hi
I tried to install stock Android 12 on my samsung A31. Due to some error in the PC the installation stopped halfway.
I used FRP hijacker tool to get back to download window. However now the error shows "Partitions prism. Reason prism: Error verifying vbmeta image : invalid vbmeta header(6) "
And when I tried to flash using odin again it says setup connection. Complete failed.
Is there no way to get this phone working? Please help!!
Click to expand...
Click to collapse
You're trying to flash a firmware with an older RP rev than the one stored in your device, you can see it from the error "Fused 2 > Binary 1". Download a firmware with RP rev 2 or higher (more info here)
Related
Ulefone power 2 Development and Support-
Basic Device Details-
Display- 5.5 inch
OS- android 7.0 Nougat
Chipset - MT6757T
RAM- 4GB
Disclaimer-
Code:
i am not Responsible for any damage to Your Device..
official Firmware-
https://drive.google.com/drive/folders/0B8NC4kBpjQhYV1lWOEtYWThRRms
twrp Recovery-
https://drive.google.com/open?id=0B1aXJDZjE8bvM0h0aTVEOEdBS1U
SP Flash tools and Driver-
https://drive.google.com/folderview?id=0B6O3B5Tc7Wr9ZzgxQmcyNmNoX00
Magisk-
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
No verity opt-Encrypt-
https://www.androidfilehost.com/?fid=673368273298927206
extras-
Greenify for Battery-
http://m.hiapphere.com/apk-com.oasisfeng.greenify
Build.prop tweaks-
[Must Backup official before try-
https://forum.xda-developers.com/attachment.php?attachmentid=4248841&stc=1&d=1503381757
Guide-
Flash Firmware-
1. Install Vcom Driver Run SP flash tools, Load Scatter File , Check Everything and then click Download, as soon as connect your Switched off Phone.
Flash twrp-
Code:
fastboot oem unlock
fastboot flash recovery recovery.img
or use inbuild script
if you have Scatter then you can Flash with SP flash tools.
Root-
flash Magisk via twrp or you can also use Supersu 2.78XX.
Mod-
Will be added Soon....:good:
version- 3.00XX
Credit- XN Logos
Donation- https://Paypal.me/droiddeveloper
Please Don't create mirror Without the Link of This Page.
I tried it but it didn't work. twrp is installed but my phone doesn't boot into the system anymore. When I reboot it goes back to Twrp and then the touchscreen doesn't work anymore. I have to connect an USB-mouse. But it still doesn't boot.
When I try to flash or wipe sth it says "unable to mount"
I had to flash the original software again with SP Flash Tools
No flash No verity encrypt to Disable boot verification
XN Logos said:
No flash No verity encrypt to Disable boot verification
Click to expand...
Click to collapse
sorry but what does that mean?
So i used your TWRP Recovery, normally it should work and it does but why is my data shown as 0.
Thank you too. Please help
where is the scatter file?
gasperoni said:
where is the scatter file?
Click to expand...
Click to collapse
no Scatter included use Fastboot, or You can take scatter from ROM.
Ok but where is the recovery image file to flash via SP Flash Tools? I only see an exe-file saying "flash recovery" and a 12.6MB file called "rk" but it's shown me as a mp4-file
it worked!!! Thank yoU!! @gasperoni, just start "Flash Recovery.exe" and do what is written in the window. It's really easy.
i have include a Script which have ability to unlock bootloader and then flash twrp, if you flash with SP flash tool your Device not bootup because bootloader is Loacked. so Simply use Given Instruction Not SP flash.
any custom ROM
non yet
hm..i install twrp with your "flash recovery.exe", my phone reboots, i have to press "volume up" to unlock my bootloader. then trwp starts.
until here everything works fine. But when i am installing Superuser and restart my phone, it writes sth like "orange mode, your phone is untrusted" and just boots into twrp, touchscreen isnt working. So i have to flash it again, but i didnt achieve twrp of course :S
Unlucky25 said:
hm..i install twrp with your "flash recovery.exe", my phone reboots, i have to press "volume up" to unlock my bootloader. then trwp starts.
until here everything works fine. But when i am installing Superuser and restart my phone, it writes sth like "orange mode, your phone is untrusted" and just boots into twrp, touchscreen isnt working. So i have to flash it again, but i didnt achieve twrp of course :S
Click to expand...
Click to collapse
Same issue for me.
I tried twice to install the recovery with the .exe file. Both times I bricked the phone. Why?
kylebutler said:
Same issue for me.
I tried twice to install the recovery with the .exe file. Both times I bricked the phone. Why?
Click to expand...
Click to collapse
Same result here. But how did you get the factory rom to flash on the phone? I first got some checksum error and had to find a checksum generator and now the silly multiport flash software says:
" Warning maybe error as follows: 1 com port number repetitive or invalid 2 brom and preloader have the same comport number! Please modify them in INI file or scan again."
I think i did everything correctly (installed the drivers and stuff as it says on the ulefone download page) but i haven't flashed any mediatek devices in a long time and i would be very thankful if someone can tell me what i'm doing wrong. I don't mind it getting bricked as i know that is always a risk with mediatek, but i do need to be able to flash the stock rom.
ml11ML said:
Same result here. But how did you get the factory rom to flash on the phone? I first got some checksum error and had to find a checksum generator and now the silly multiport flash softwhttps://forum.xda-developers.com/usercp.phpare says:
" Warning maybe error as follows: 1 com port number repetitive or invalid 2 brom and preloader have the same comport number! Please modify them in INI file or scan again."
I think i did everything correctly (installed the drivers and stuff as it says on the ulefone download page) but i haven't flashed any mediatek devices in a long time and i would be very thankful if someone can tell me what i'm doing wrong. I don't mind it getting bricked as i know that is always a risk with mediatek, but i do need to be able to flash the stock rom.
Click to expand...
Click to collapse
I had also issues using the flash tool provided on the Ulefone website, the same as you say (with the checksum). None of checksum-generating software worked for me, so I was searching long for an alternative and found this flash tool: https://spflashtool.com/. Using this tool, flashing worked for me perfectly even without having to bother with checksums.
Good luck!
pavelmracek said:
I had also issues using the flash tool provided on the Ulefone website, the same as you say (with the checksum). None of checksum-generating software worked for me, so I was searching long for an alternative and found this flash tool: https://spflashtool.com/. Using this tool, flashing worked for me perfectly even without having to bother with checksums.
Good luck!
Click to expand...
Click to collapse
Thank you very much for this! That tool works flawlessly unlike the ulefone garbage.
On another note... anyone know if there is source code for the power 2 to be found somewhere or did the dev just port another recovery somehow? I tried a while back just porting twrp by swapping files but i couldn't get the image to repack with the kitchen tool so i gave up.
ml11ML said:
Same result here. But how did you get the factory rom to flash on the phone? I first got some checksum error and had to find a checksum generator and now the silly multiport flash software says:
" Warning maybe error as follows: 1 com port number repetitive or invalid 2 brom and preloader have the same comport number! Please modify them in INI file or scan again."
I think i did everything correctly (installed the drivers and stuff as it says on the ulefone download page) but i haven't flashed any mediatek devices in a long time and i would be very thankful if someone can tell me what i'm doing wrong. I don't mind it getting bricked as i know that is always a risk with mediatek, but i do need to be able to flash the stock rom.
Click to expand...
Click to collapse
hey, how did you set your IMEIs after bricking? I usually used Engineer Mode to set them, but thats not working since i am missing "CDS Information"
Unlucky25 said:
hey, how did you set your IMEIs after bricking? I usually used Engineer Mode to set them, but thats not working since i am missing "CDS Information"
Click to expand...
Click to collapse
Uh, i never even bothered to think about imei as it just worked without doing anything.
ml11ML said:
Uh, i never even bothered to think about imei as it just worked without doing anything.
Click to expand...
Click to collapse
ok nevermind, i found a solution..yeyy
so if anybody stumples across here, who has no IMEI set, CDS information in MTK mode and no rooted phone... u can set your IMEI in MTK engineering mode under "GPRS"!
I downloaded Odin3 and Heindall, Samsung A01 core stock rom, and pacthed the AP file with magisk (https://topjohnwu.github.io/Magisk/install.html). My phone is Samsung A01 core, have OEM disabled, and have Ramdisk. I am using usb 3 and a official samsung usb cable.
i had Patched the Boot.img from AP file, and Patched the whole AP file on Magisk . so i tried to flash Boot.img with "fastboot" and tried to flash AP file on download mode with odin. Fastbot is not working to flash the "Boot.img", because the command `fastbot boot Boot.img` is not recognized (FAILED (remote: unknown command)), i had try `fastbot flash:raw boot boot.img` with no sucess too, giving me the same error.
so i am tried Jodin3, and keep trying to flash the whole magiskAP file. following the tutorial above, and Jodin3 always tell .PIT is corrupted (even generated by heimdall or using the .pit inside CSC file). but is not to work, Jodin3 keep give me errors, it say .pit is corrupted.
Some versions of ODIN for windows, don't ask for .PIT... so what i can do? Can i regenerate a PIT from a "patched AP" ?
Hey! As I see that no one has responded to you in two years, I will give you some tips.
First of all, I need to warn you that the Samsung system does not have fastboot, unlike other devices, so there is no way to use commands like that on any Galaxy device.
And secondly, I noticed that you are a Linux user. From my own experience, I recommend you try using Odin on Windows, as I've tried several times to use Jodin, and I've only had problems.
As for the .PIT, I don't know how to help you, since I don't remember anything about the procedure.
I hope I was helpfull. If you're still trying, try my tips and let me know if it worked!
adonisSMS said:
I downloaded Odin3 and Heindall, Samsung A01 core stock rom, and pacthed the AP file with magisk (https://topjohnwu.github.io/Magisk/install.html). My phone is Samsung A01 core, have OEM disabled, and have Ramdisk. I am using usb 3 and a official samsung usb cable.
i had Patched the Boot.img from AP file, and Patched the whole AP file on Magisk . so i tried to flash Boot.img with "fastboot" and tried to flash AP file on download mode with odin. Fastbot is not working to flash the "Boot.img", because the command `fastbot boot Boot.img` is not recognized (FAILED (remote: unknown command)), i had try `fastbot flash:raw boot boot.img` with no sucess too, giving me the same error.
so i am tried Jodin3, and keep trying to flash the whole magiskAP file. following the tutorial above, and Jodin3 always tell .PIT is corrupted (even generated by heimdall or using the .pit inside CSC file). but is not to work, Jodin3 keep give me errors, it say .pit is corrupted.
Some versions of ODIN for windows, don't ask for .PIT... so what i can do? Can i regenerate a PIT from a "patched AP" ?
Click to expand...
Click to collapse
This is working for me on Ubuntu.
OFFICIAL Samsung Odin v4 1.2.1-dc05e3ea - For Linux​
OFFICIAL Samsung Odin v4 1.2.1-dc05e3ea - For Linux
Try out my new Linux flash tool called Thor - https://forum.xda-developers.com/t/dev-thor-flash-utility-the-new-samsung-flash-tool.4597355, which has all the features of this tool + extras, like the usual Windows Odin ones which are missing in...
forum.xda-developers.com
somehow when updating my phone it crashed and now i lost recovery mode all i can get into is download mode now i have tried reinstalling multiple different firmware to no avail this is what i get can anyone help me get my phone back i cant afford a new one
i have a note 10+ star wars edition unlocked atraight from samsung
PARTITION PRODUCT
REASON PRODUCT ERROR VALIDATING FOOTER (6)
PRODUCT ERROR VERIFYING VBMETA IMAGE INVALID VBHEADER (6)
SAMSUNG PROFUCT N975U1UEUF7FUJ8, 45284190R
VBMETA N975U1UEUF7FUJ8, 45284190R
did you use patched odin ?
Hello! I have the phone from the title and I need a scatter firmware for this model to flash it with the SP Tool program, to unbrick it. I can't flash it with Odin, because download mode or recovery does not work. I have working MT Bypass tool and drivers installed correctly and phone is detected as mediatek usb but I need the correct firmware. Can somebody share a link to a firmware like this or a complete backup scatter firmware from a working phone, for this model?
Samsung Galaxy A12 (SM-A125F) MT6765 Scatter Firmware Flash File Free Download
Samsung Galaxy A12 (SM-A125F) hang logo stuck frp bypass hard reset drivers restart MT6765 Scatter Firmware Flash File Free Download
mr-mobiles-city.blogspot.com
i found this website somewhere in the internet
That archive is password protected and the password "gsmVNtool" is not working...
I have this yt video link
But just curious what did you do to the device before hardbrick(eg.Install TWRP,flash firmware?
How did you brick it?
It's my father's phone. I suspect an update has started and the battery has been discharged. The phone restarted continuously and does not charge the battery. Showed only the charging sign but without the charging percentage. I tried to flash it with odin and nothing changed. Then I used SP Flash Tool with a firmware found on internet an choosed to format all. But here was my mistake, because that firmware was for A125U1. Now, I followed your post and I converted the last firmware but when I try to flash the files with sp tool, i get errors , something with image too large, invalid header, etc... I'm at work now, but I think that you know what I'm reffering to... Thanks for the help.
Is there a way to unlock the bootloader without the phone working with ODIN? I'm trying to write the latest firmware version, (A125FXXS2BVA3_A125FOXM2BVA3_ROM), with SP Flash Tool, because I can't downgrade back to Android 10, and I get the errors: "STATUS_SEC_IMGHDR_TYPE_MISMATCH; Verified boot is enabled. Please download signed image or disable verified boot."
If I try to write a firmware version with Android 10, SP Flash Tool returns the error: "STATUS_SEC_VIOLATE_ANTI_ROLLBACK".
Unlocktool.net its a paid tool to unlock bl and remove kg lock without having access to download
Patching AP.tar with magisk doesn't seem to work...
What do you mean it's not work? What error message do you get? Got a screenshot? Thanks
When I flash patched AP.tar, I get "error verifying vbmeta: HASH MISMATCH" error. I followed the official instructions for installing magisk.
I also tried flashing patched boot.img, but I get another error saying that only official firmware is allowed to be installed.
I never installed magisk this way, so I don't know if this procedure worked on previous Android versions (or if I'm even doing it right considering it's Samsung...).
umh..I made the mistake of connecting my M21 2021 Edition to internet and it updated something in the blink of an eye and then when I checked Developer Options the OEM Unlock button disappeared. I cant flash TWRP-ODIN-patch-file anymore , it shows Secure Download error in Download Mode also Custom Binary Blocked error. Without TWRP I cant flash anything. I'm dead!
I am also getting same error, I downloaded my firmware from samfw.com (SM-M215F / Android 12 / Binary 3), then I extracted it to my PC. Then copied AP file from PC to my phone, Patched it using Magisk v25.2 (From Github). Copied patched file from phone to PC. Flashed it using Odin v3.14.4 (BL, AP, CP, CSC). Getting error that VBMETA ERROR HASH_MISMATCH (3).
Has anyone found solution for it?
xyncronix said:
I am also getting same error, I downloaded my firmware from samfw.com (SM-M215F / Android 12 / Binary 3), then I extracted it to my PC. Then copied AP file from PC to my phone, Patched it using Magisk v25.2 (From Github). Copied patched file from phone to PC. Flashed it using Odin v3.14.4 (BL, AP, CP, CSC). Getting error that VBMETA ERROR HASH_MISMATCH (3).
Has anyone found solution for it?
Click to expand...
Click to collapse
You dont want to use Custom Recovery?
xyncronix said:
I am also getting same error, I downloaded my firmware from samfw.com (SM-M215F / Android 12 / Binary 3), then I extracted it to my PC. Then copied AP file from PC to my phone, Patched it using Magisk v25.2 (From Github). Copied patched file from phone to PC. Flashed it using Odin v3.14.4 (BL, AP, CP, CSC). Getting error that VBMETA ERROR HASH_MISMATCH (3).
Has anyone found solution for it?
Click to expand...
Click to collapse
I have successfully rooted my m21 with Android 12 . Watch the
Follow the process described here . Root will be successful.
OldNoobOne said:
You dont want to use Custom Recovery?
Click to expand...
Click to collapse
Custom recovery is good but to flash we can use Odin by samsung. Official samsung software.
Flashing the whole AP feels pretty big. All you actually need is the boot image. Extracting it from the stock rom can be pretty annoying though. If patching ap isn't working for you there's two ways to go. Either flash the magisk apk from recovery (this still works for m21) or patch just the boot image and flash it using Odin or recovery.
You can get the boot image of your respective stock rom from here inside the AP folder.
1. Patch the boot image using the magisk app and rename the patched boot image to "boot.img"
2. Add boot.img it to a tar archive
3. Flash the tar file to AP in Odin
Something you need to note is that magisk no longer patches some stuff from v25.0, so there's a small chance it might bootloop. So ideally, patch using magisk 24.x and then you can update later on using the magisk app.
.