Hello everyone!
Today i tried to install twrp on my s10+ SM-G765F/DS to install android 12 lineage os.
I placed TWRP at AP and VBmeta at CS.
VBmeta was stuck at the installing phase, for a very long time too.
I decided to quit Odin and unplug the phone.
Error showed up : An error uas occured while updating the device software. Use the emergency revovery function in the Smart Switch PC software.
Using smart switch pc : device dosent show up
FRP Bypass : into download mode, tried flashing original firmware, back to download mode, tried flashing twrp, didn't work, with vbmeta and without.
top left said:
ODIN MODE (AVB FAIL)
recovery: Error validating footer. (0)
recovery: Error verifying vbmeta image : invalid vbmeta footer (6)
CUSTOM RECOVERY
VBMETA G975FXXSBFUE6, 40448985R
Please help me, i dont know what this means and whether my phone can be saved.
I have found a fix.. to everyone who is facing this problem, here is what you need to do.
1.get frija ( you will need visual c++ 2010 and 2008.)
2. obtain your model number and your csc ( found if you search up your carrier in sammobile along with your phones model number product code in my case, i got it under starhub in Singapore therefore, STH)
3. key in the details into frija
4. download the firmware from frija.
5. frija will give you a rar with your firmware, unpack that.
6. match the BL, AP, CS and CSC with the firmware and start.
The process will take a while as its a big file but your phone will be saved!
precautionary measures if you were to attempt again
1. keep the firmware files
2. use a good version of Odin, my error happened because my version of odin didnt work.
3. do a lot of research
For me with my S10+ G975F, this saved me:
An error has occured while updating the device software.
Hello everyone! Today i tried to install twrp on my s10+ SM-G765F/DS to install android 12 lineage os. I placed TWRP at AP and VBmeta at CS. VBmeta was stuck at the installing phase, for a very long time too. I decided to quit Odin and unplug...
forum.xda-developers.com
Related
hey guys im sorry if i post this on the wrong section but i followed this tutorial: droidviews(dot)com/root-galaxy-s6-and-s6-edge-on-android-6-0-1-marshmallow-update/ to root my s6 edge+ and it went black... after some research i found out the tutorial wasnt for my device(SM-G2928F) so i flashed it with cf-autoroot and then it boot looped for like an hour. I downloaded the original greek firmware from sammobile but it brings me up this error: SECURE CHECK FAIL : (BOOTLOADER).. any help?
UPDATE: changed the port and run Odin as admin now it says: SECURE CHECK FAIL : (RADIO) Odin log: pastebin(dot)com/4w1943HF
UPDATE: now when I exit recovery mode it doesnt start and tells me: An error has occured while updating the device software. Use the Emergency recovery function in the Smart Switch PC software.(I can still go into recovery mode)
Let me check you have flashed a firmware not for your device with odin or just a zip? First I would try flashing the most recent firmware you can find for your device with odin, some bootloaders can't be downgraded. If that doesn't work then the emergency firmware recovery will work, I've used kies emergency firmware a few times.
Hopefully someone with your device will point you in the right direction if you are stuck
I flashed a firmware not for my device but I found a solution on another XDA post thank you
Summary: My tablet is soft-brick now. Can only access to Download (ODIN) mode. I have tried 2,3 different firmwares, tried 3 versions of ODIN. But it doesn't work.
Here is the story:
I bought this tablet from bestbuy (USA)
I only wanted to root my tab A 7.0 SM-T280.
I enabled the OEN unlock from the developer mode.
Then I tried to flash the TWRP by the tutorial from this topic by @ashyx :
To install TWRP:
1. Flash with ODIN 3.10.7 in the AP slot.
Uncheck Auto reboot.
2. Load the respective file below into the AP slot and hit start.
3. After flashing when ODIN says PASS immediately reboot to recovery by holding POWER + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding the other buttons.
You should now see TWRP recovery.
TWRP_3.0.2-1_SM-T280_261016
Click to expand...
Click to collapse
After flashing, on the download mode it showed: "SECURE CHECK FAIL: (RECOVERY)", then I reboot into recovery mode to access the TWRP but it said: "RECOVERY IS NOT SEANDROID FORCEFUL (although in ashyx topic said the SECURE FAIL is fine).
I still was able to reboot into the system this time.
And then I thought I should try another way. And then I came up with the TINKER ROM.
I tried to flash the Rom (v5) but somehow ODIN said FAIL.
I COULD NOT access the system since then.
Bu @zenful 's advices, I tried some different stock firmwares and different versions of ODIN just to get back to normal, but it never works.
Every time I flash, it always has the same problem:
- First try, ODIN fails at:
sboot.img
sboot2.img
complete (write) failed... (I don't remember though)
And in the download mode screen (from the phone) said:
SECURE CHECK FAIL (SBOOT)
SECURE CHECK FAIL (SBOOT2)
- Second try, ODIN fails at:
boot.img
system.img
Complete (write) fail...
And in the screen said:
SECURE CHECK FAIL (BOOT)
SECURE CHECK FAIL (RECOVERY)
I also tried emergency recovery mode in smart switch but it didn't solved the problem. One good thing (after I entered the tablet model and serial number) is that it showed "PHONE: QA4 CSC: PH3 (XAR)"
______________
I'm pretty sure that the problem doesn't come from fw nor from ODIN since I downloaded the fws from sammobile and updato and downloaded ODIN from xda (the latest version from samsungodin.com)
I'm seriously need a help right now. I just wanna have a rooted tablet so I can play game with my ps4 controller.
I have experienced with these flashing business. I rooted my galaxy s2, HTC desire c, HTC evo, etc. and so on, but have never done rooting in the last 1 year. I can attach some snapshots if you guys request
ngvhoang96 said:
Summary: My tablet is soft-brick now. Can only access to Download (ODIN) mode. I have tried 2,3 different firmwares, tried 3 versions of ODIN. But it doesn't work.
Here is the story:
I bought this tablet from bestbuy (USA)
I only wanted to root my tab A 7.0 SM-T280.
I enabled the OEN unlock from the developer mode.
Then I tried to flash the TWRP by the tutorial from this topic by @ashyx :
After flashing, on the download mode it showed: "SECURE CHECK FAIL: (RECOVERY)", then I reboot into recovery mode to access the TWRP but it said: "RECOVERY IS NOT SEANDROID FORCEFUL (although in ashyx topic said the SECURE FAIL is fine).
I still was able to reboot into the system this time.
And then I thought I should try another way. And then I came up with the TINKER ROM.
I tried to flash the Rom (v5) but somehow ODIN said FAIL.
I COULD NOT access the system since then.
Bu @zenful 's advices, I tried some different stock firmwares and different versions of ODIN just to get back to normal, but it never works.
Every time I flash, it always has the same problem:
- First try, ODIN fails at:
sboot.img
sboot2.img
complete (write) failed... (I don't remember though)
And in the download mode screen (from the phone) said:
SECURE CHECK FAIL (SBOOT)
SECURE CHECK FAIL (SBOOT2)
- Second try, ODIN fails at:
boot.img
system.img
Complete (write) fail...
And in the screen said:
SECURE CHECK FAIL (BOOT)
SECURE CHECK FAIL (RECOVERY)
I also tried emergency recovery mode in smart switch but it didn't solved the problem. One good thing (after I entered the tablet model and serial number) is that it showed "PHONE: QA4 CSC: PH3 (XAR)"
______________
I'm pretty sure that the problem doesn't come from fw nor from ODIN since I downloaded the fws from sammobile and updato and downloaded ODIN from xda (the latest version from samsungodin.com)
I'm seriously need a help right now. I just wanna have a rooted tablet so I can play game with my ps4 controller.
I have experienced with these flashing business. I rooted my galaxy s2, HTC desire c, HTC evo, etc. and so on, but have never done rooting in the last 1 year. I can attach some snapshots if you guys request
Click to expand...
Click to collapse
Try this: download your desire firmware via samfirm (BL+AP+CP+CSC when extracted) plus you need a pit file for your model with the same region as firmware and then flash (with 4 firmware files incl pit) via odin autoreboot+repartition+nand erase+f.reset time. At least you will get working stock tablet. It worked on my note 4 soft bricked.
Stixas said:
Try this: download your desire firmware via samfirm (BL+AP+CP+CSC when extracted) plus you need a pit file for your model with the same region as firmware and then flash (with 4 firmware files incl pit) via odin autoreboot+repartition+nand erase+f.reset time. At least you will get working stock tablet. It worked on my note 4 soft bricked.
Click to expand...
Click to collapse
Last time I tried download fw by using samfirm was last week and it didnt work. Can you test yours again?
And whre can I found the pit file? I dont think there is one in the internet right now.
I have an SM-T280 that I've been trying to put LineageOS on, so I can use my MicroSD card as app storage. I downloaded TWRP Recovery, used Heimdall to transfer it over... DISASTER! Heimdall says:
Code:
Downloading device's PIT file...
PIT file download successful.
Uploading RECOVERY
100%
RECOVERY upload successful
Ending session...
ERROR: Failed to receive session end confirmation!
Releasing device interface...
And on the screen of the tablet itself, "Custom Binary(Recovery) Blocked by FRP Lock". Now my phone is stuck in Odin Download Mode (won't turn on or off), I can't find the stock firmware because I don't have the CSC code, and worst of all, Heimdall won't even connect to the tablet anymore. It gives me this error:
Code:
Initialising protocol...
ERROR: Protocol initialisation failed!
Anyone got any ideas?
nickmatavka said:
I have an SM-T280 that I've been trying to put LineageOS on, so I can use my MicroSD card as app storage. I downloaded TWRP Recovery, used Heimdall to transfer it over... DISASTER! Heimdall says:
And on the screen of the tablet itself, "Custom Binary(Recovery) Blocked by FRP Lock". Now my phone is stuck in Odin Download Mode (won't turn on or off), I can't find the stock firmware because I don't have the CSC code, and worst of all, Heimdall won't even connect to the tablet anymore. It gives me this error:
Anyone got any ideas?
Click to expand...
Click to collapse
Just reboot to download mode (before you say you can't, I guarantee you can) then either just install the stock recovery or the whole firmware.
Boot to the OS and enable OEM_UNLOCK.
I suggest in future you read the installation instructions properly.
@OP
Whats the update? Did you manage to install LigeageOS?
I have the same device and want to install another OS for the same reason.
Did you have any luck installing another OS?
Hello to everybody.
like the title of the thread suggests i have a Samsung S7 Edge (g935f) that isn't able to boot anymore. For what I remember I rooted this phone in 2017, using cf autoroot with Odin, but never installed some other custom rom.
Friday i needed to install upgrades and make a big mistake, I've disabled the unlock oem option. Now the device don't boot anymore, showing the Custom binary blocked by FRP lock when try to boot and even when is in charge, and in recovery mode you can see dm-variety verification failed... error.
I've tried to flash a new stock firmware, downloaded using the Samfirm tool, with odin but stuck in NAND Wright.
I've read that with this two errors, the phone is most likely in a hard brick situation.
Some other informations: in recovery mode I have the following informations:
MMB29K.G935FXXU1BPH6
samsung/hero2ltexx/hero2lte
6.0.1/MMB29K/G935FXXU1BPH6
and at the bottom the "dm-verity" error message
in download mode:
Current binary: Custom
System status: Custom
FRP LOCK: On (that's my fault)
Hope someone can help, and thanks.
Sorry didn't read your post correctly.. since you are still on v1 bootloader
Follow this link :
https://www.techzai.com/fix-drk-device-root-key-for-samsung-galaxy-phones/amp/
In short, extract AP and copy boot.img and system.img to new folder, then rename boot.img to recovery.img and repack AP using only these 2 files (system.img and renamed recovery.img) or maybe repack system+renamed recovery+boot which means we flash boot.img 2 times.. if using only system and renamed recovery doesn't work, and maybe add userdata.img too if adding boot.img doesn't work..and try flashing in official odin (if it doesnt get flashed in official odin.. use prince comsy modified odin)
(before doing this download this firmware and apply above procedure on it :
https://www.sammobile.com/samsung/galaxy-s7-edge/firmware/SM-G935F/EUR/download/G935FXXU1BPH6/89733/ )
(Auto tar 2.0 link use to repack files to tar :
https://www.mediafire.com/file/ah20ha869prdkkc/Autotar2.0_By_FixFirmwares.com.rar/file )
Don't tell me if you detect any viruses lol, i don't own any file, just helping to get your phone working again (delete all such files after using them)
Flash bl, csc, cp as usual alongwith this modified AP, use default odin options (don't tick nand erase or any other advanced option in odin)
And dont try to boot into recovery as there will be no recovery .. if lucky .. you will be able to boot phone to go in settings and enable oem unlock option.. if unlucky you will brick your phone even further like efs partition further damage/ nv data corruption (which could be fixed by a box)
So i told you the risks, i will not be responsible for anymore damage.
Note : don't update to newest/latest firmwares or higher bootloader (because it makes rooting and fixing device very difficult as firmware with a higher bootloader version cannot be downgraded to lower bootloader version) and also your dm verity is permanently destroyed so even if you are able to fix your phone by yourself you will always need to keep oem enabled and dm verity disabled to use it.. and upgrading to latest firmware will only create more problems
Good luck ..
Hello every one. Total noob here. But this is to answer a question I had earlier but found no help with at least upon a basic google search. Earlier I bricked my Tab S6 Lite while trying to install TWRP to replace the current recovery. Hind sight being 20/20 I know now that TWRP is no long active and that is was simply a bad idea. I ended up stuck in odin boot loop with the error message of..
Odin Mode (DT Load Fail)
[DTH] dt table header check Fail: <unknown error>
Load_kernal: Could not do normal boot. (DT LOAD FAILURE)
vbmeta: Error verifying vbmeta image: OK_NOT_SIGNED (3)
CUSTOM VBMETA
VBMETA : No sign info
This put me in a bad spot as ADB, and Fastboot were no longer an option and I could not pull a viable pit from Tab using Heimdall, and Odin will not allow you to flash the recovery that can be found in Lineage downloads page as they are img files.
The solution I found was to use a program to change the recovery.img file found in the Nightly lineage zip folder into to a tar file using the program. And then flash that tar file using odin. This brought me back to standard liniage with no data loss.
Disclaimer: The file attached is not my own, download and use at your own risk.
I do not recommend you mess with software if you're not ready to brick and fix your own device.
Thanks