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 ?
Related
Update:
I've got my phone back thanks to this post! https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
--------------------------------------[/B]-----------------------------------------------------------------------------------------------------------------------------------------------
I successfully upgraded my NXT-L29 to Oreo, using the files in this post: https://forum.xda-developers.com/mate-8/general/discussion-oreo-huawei-mate-8-t3785320
(Only difference: used another TWRP version - twrp-3.1.1-1-next.img - since the one in this post didn’t work).
Though my phone worked, it was unrooted again and I tried to solve it by flashing TWRP again. It didn’t work, so I tried flashing TWRP-3.1.0-EMUI-5.0.img. Here’s where everything went wrong.
I get:
ERROR MODE, Please update system again!"
Error! Func: NO: 11 (recovery image)
Error NO: 2 (load failed!)
Here’s what I still can do:
- Get into Fastboot – Bootloader and FRP both Unlocked
- Use ADB
- Get into eRovery
- Get into EMUI update
- Flash TWRP, SYSTEM.img and BOOT.img
What I can’t do:
- Access my phone – get or one of the two yellow messages or Error Mode or Fastboot
- Connect to HiSuite
- Acces Wipe Partion, Factory Settings
- Boot into TWRP
- Flash any Recovery (partition: (length) error, or Cannot load Recovery). No matter what command I try. Fastboot flash recovery_ramdisk RECOVERY.img doesn’t work either.
- Find a RAMDISK.img in the Update.app. Flashing the SYSTEM, CUST and BOOT.img won’t do the trick with rebooting volume up + volume down + power. EMUI update states: Software install failed!
- Use eRovery. Recovery fails every time after 7%
- Find the current Build Number, since there’s no way of getting passed the two yellow messages or Error Mode or Fastboot
I’ve been up till 5 in the morning, trying to solve this without success. Think I’ve tried a 100 commands and methods. Is there anyone who has a solution? I’m really desperate by now.
HQuinn said:
I successfully upgraded my NXT-L29 to Oreo, using the files in this post: https://forum.xda-developers.com/mate-8/general/discussion-oreo-huawei-mate-8-t3785320
(Only difference: used another TWRP version - twrp-3.1.1-1-next.img - since the one in this post didn’t work).
Though my phone worked, it was unrooted again and I tried to solve it by flashing TWRP again. It didn’t work, so I tried flashing TWRP-3.1.0-EMUI-5.0.img. Here’s where everything went wrong.
I get:
ERROR MODE, Please update system again!"
Error! Func: NO: 11 (recovery image)
Error NO: 2 (load failed!)
Here’s what I still can do:
- Get into Fastboot – Bootloader and FRP both Unlocked
- Use ADB
- Get into eRovery
- Get into EMUI update
- Flash TWRP, SYSTEM.img and BOOT.img
What I can’t do:
- Access my phone – get or one of the two yellow messages or Error Mode or Fastboot
- Connect to HiSuite
- Acces Wipe Partion, Factory Settings
- Boot into TWRP
- Flash any Recovery (partition: (length) error, or Cannot load Recovery). No matter what command I try. Fastboot flash recovery_ramdisk RECOVERY.img doesn’t work either.
- Find a RAMDISK.img in the Update.app. Flashing the SYSTEM, CUST and BOOT.img won’t do the trick with rebooting volume up + volume down + power. EMUI update states: Software install failed!
- Use eRovery. Recovery fails every time after 7%
- Find the current Build Number, since there’s no way of getting passed the two yellow messages or Error Mode or Fastboot
I’ve been up till 5 in the morning, trying to solve this without success. Think I’ve tried a 100 commands and methods. Is there anyone who has a solution? I’m really desperate by now.
Click to expand...
Click to collapse
Hi.
According to your post, you flashed TWRP-3.1.0-EMUI-5.0.img then got the problems .
Did you try to flash stock recovery by adb?
You can find it in original ROM files
afromoh said:
Hi.
According to your post, you flashed TWRP-3.1.0-EMUI-5.0.img then got the problems .
Did you try to flash stock recovery by adb?
You can find it in original ROM files
Click to expand...
Click to collapse
Yes, I've tried that about a million times. Everything worked, except flashing the (stock) recovery.
I'm really sorry for my late reply. I've been very ill. Luckily the problem is solved and I've got my phone back. Thanks to Georgian51 who suggested this post: https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279.
That did the trick! Thanks for your reply
Hey yall,
so I finally managed to successfully brick my honor :laugh:
Everything was pretty much fine, I was messing with trying different ROMs. Then I used the "Change location" option in HWOTA8 (it probably flashed some extra files) and my systems "erecovery" or something likely essential "dissappeared".
Fastboot works, I tried flashing 'system' and recovery images with no success. It won't accept TWRP or any other image as I get "partition size get error"
When I try to boot into recovery or system, I get the error
Error Mode message: Func no 11 [recovery image], Error NO 2 [load failed]
I tried dload methods with (B132, B340 and some other versions, I get the Error Mode anyway)
What I think is the core of the problem could be one of following:
boot.img,
erecovery
frp
I get a boot loop no matter what I do.
The phone model is BLN-L22 indian (debranded from BLN-L21) and the last flashed ROM was Oreo
The FRP and Bootloader are unlocked.
I think it could work if I'd flash every partition, but it doesn't seem to work with images I got from "update.app"
Could you recommend me some repair/flashing tools/flashing files?
Any help in the investigation is greatly appreciated
Update: Just bought DC Phoneix
Now I managed able to boot into the "update via usb" screen. (with the help of DC Phoneix)
I can access adb, altho I cannot use adb shell, because it cannot access /bin/sh
Does having access to adb give me any advantage?
Solved using this <3. Now I'm at android 4
https://forum.xda-developers.com/honor-6x/how-to/guide-unbrick-honor6x-boot-fastboot-t3904381
I have a pixel 2 which is stuck in bootloader due to "Slot Unbootable: Load Error".
So far I tried to flash / wipe the device with https://flash.android.com/ but the process can't be started due to "Device Unlock Disabled".
Anyone got some hints for me?
Unfortunately your options are rather limited because the bootloader is locked, and because OEM Unlocking is off (get_unlock_ability=0), unlocking it is not possible. This is one of those shortcomings I think should be addressed in Pixel devices but that's another conversation for another time.
Are you able to boot into recovery or Download Mode?
I'll break out my old Pixel 2 when I get home and see if I can figure something out.
Trying to boot into Recovery Mode gives the same Load Error. Trying to boot into Download Mode gives: "ERROR: Operation Denied" .
50g said:
Trying to boot into Recovery Mode gives the same Load Error. Trying to boot into Download Mode gives: "ERROR: Operation Denied" .
Click to expand...
Click to collapse
Yeah, I had the same result on my Pixel 2.
Rescue Mode unfortunately wasn't introduced until the Pixel 3.
Unfortunately I don't think there is any way to fix your device beyond taking it to a repair center and having them replace the mainboard...unless you can find someone who has both the Qualcomm Product Support Tool as well as the necessary files. It's not possible to flash the device via bootloader when bootloader is locked; the prescribed method to update outside of system is via recovery (ADB sideload).
Sorry I couldn't be of more help.
I was concerned that might be the case. Appreciate your efforts.
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)
Hi,
I must admit that I clearly underestimated the level required to root my phone.
Today, I have the feeling that my phone is dead and this is a bottle in the sea that I'm dropping here to try to resurrect it.
I am currently stuck on a green screen with "Downloading" written in the middle of the screen and this in the upper left corner:
ODIN MODE (SVB Fail)!
prism: No footer detected (0)
prism: Error verifying vbmeta image: invalid vbmeta header (6)
CUSTOM prism
VBMETA S908BXXU4CWCG, 63617910R
Custom Binary(VBMETA) Blocked By OEM Lock
I put the phone in Download mode thanks to FRP Hijacker by Hagard, then I launch Odin and I tried to flash the file "vbmeta_disabled_R.tar" in USERDATA without success.
I can't flash "AURORA_TWRP_S908X_2200_3.6.2.12_OneUI4.X.tar" in AP either.
I also tried to flash the 4 files from "Samfw.com" about my phone "Samfw.com_SM-S908B_SFR_S908BXXU4CWCG_fac" without success.
I only dream of restarting my phone as on its first day.
This is how I ask you: please help me
What guide did you follow? Those steps seems very strange to me. Didn't you unlock your bootloader first? If it is the case, I think just flashing stock firmware with Odin should fix it.
SirFurion said:
Hi,
I must admit that I clearly underestimated the level required to root my phone.
Today, I have the feeling that my phone is dead and this is a bottle in the sea that I'm dropping here to try to resurrect it.
I am currently stuck on a green screen with "Downloading" written in the middle of the screen and this in the upper left corner:
ODIN MODE (SVB Fail)!
prism: No footer detected (0)
prism: Error verifying vbmeta image: invalid vbmeta header (6)
CUSTOM prism
VBMETA S908BXXU4CWCG, 63617910R
Custom Binary(VBMETA) Blocked By OEM Lock
I put the phone in Download mode thanks to FRP Hijacker by Hagard, then I launch Odin and I tried to flash the file "vbmeta_disabled_R.tar" in USERDATA without success.
I can't flash "AURORA_TWRP_S908X_2200_3.6.2.12_OneUI4.X.tar" in AP either.
I also tried to flash the 4 files from "Samfw.com" about my phone "Samfw.com_SM-S908B_SFR_S908BXXU4CWCG_fac" without success.
I only dream of restarting my phone as on its first day.
This is how I ask you: please help me
Click to expand...
Click to collapse
Since none of what you tried to flash was a success, and your phone isn't dead, you can breathe easy. Only a little more research is required on your part to make it reboot successfully.
Hope this is of some reassurance to you, if not technical support.
blackhawk_LA said:
What guide did you follow? Those steps seems very strange to me. Didn't you unlock your bootloader first? If it is the case, I think just flashing stock firmware with Odin should fix it.
Click to expand...
Click to collapse
Hi,
I follow those steps:
How to Root any Samsung device via Magisk and Odin
In thios guide, we will show you the steps to root any Samsung device via Magisk and Odin by flashing the magisk_patched.tar file.
droidwin.com
But it failed at step 5, when I flashing with Odin.
It stay lock during "Prism" step on Odin.
I cancelled the download and ended up with the phone in Brick mode.
I used Hijacker to unbrick it and try to reset factory but unsuccessfully.
Someone advice me to follow this:
Download TWRP Recovery for Samsung Galaxy S22 Ultra | Root Using It
In this tutorial, we will guide you on how to install the TWRP Recovery on Samsung Galaxy S22 Ultra. TWRP recovery is probably the most
www.getdroidtips.com
And it seems work!
I've the welcome screen and I followed step to lauch my phone but recovery system from Google or Samsung doesn't work. So I restart my phone a first time and doesn't success.
I can do things but not finish the set-up of my phone.
I restart another time and I would like to lock bootloader because each time I restart my phone a too quickly red message appears on the screen.
But at the moment when I press up volume button for lock bootloader, my phone switch on download mode with message that I wrote in my first message.
SirFurion said:
Hi,
I must admit that I clearly underestimated the level required to root my phone.
Today, I have the feeling that my phone is dead and this is a bottle in the sea that I'm dropping here to try to resurrect it.
I am currently stuck on a green screen with "Downloading" written in the middle of the screen and this in the upper left corner:
ODIN MODE (SVB Fail)!
prism: No footer detected (0)
prism: Error verifying vbmeta image: invalid vbmeta header (6)
CUSTOM prism
VBMETA S908BXXU4CWCG, 63617910R
Custom Binary(VBMETA) Blocked By OEM Lock
I put the phone in Download mode thanks to FRP Hijacker by Hagard, then I launch Odin and I tried to flash the file "vbmeta_disabled_R.tar" in USERDATA without success.
I can't flash "AURORA_TWRP_S908X_2200_3.6.2.12_OneUI4.X.tar" in AP either.
I also tried to flash the 4 files from "Samfw.com" about my phone "Samfw.com_SM-S908B_SFR_S908BXXU4CWCG_fac" without success.
I only dream of restarting my phone as on its first day.
This is how I ask you: please help me
Click to expand...
Click to collapse
I've bricked my previous Galaxy phone and successfully revived it. Just Google 'reinstall stock firmware Samsung Galaxy S22 Ultra Odin' and you'll see sites that can help you.