I have a German S6 Galaxy Edge G925F. I rooted it early on with Kingroot, which (I gather) blocked me from receiving OTA updates from my provider. So I was stuck at 5.0.2. I've flashed custom ROMs on all my previous android devices, so this morning I thought I'd try flashing XtreStoLite as a way of getting to 5.1.1, and a nicer 5.1.1 at that! I used the directions at http://forum.xda-developers.com/gal...-xtrestolite-pure-edition-1-0-beta-1-t3082467 . I made a stupid mistake though, and started the update before reading ALL the instructions ALL the way through.
Now I can get into Download mode, but otherwise I'm stuck at the initial "samsung galaxy s6 edge powered by android" boot screen, with red text at the top:
Code:
KERNEL IS NOT SEANDROID ENFORCING
SYSTEM REV. CHECK FAIL. DEVICE: 2, BINARY: 1
I'm on a Mac, and since JOdin can't seem to read PIT files anymore I'm using pure heimdall command line. So here's what I did:
1) Downloaded G925F-XXU2BOGG-BOOTLOADER.tar from the above thread, and flashed the contained 5.1.1 cm.bin and sboot.bin. (
Code:
heimdall flash --no-reboot --80 sboot.bin --90 cm.bin
)
2) Immediately found myself unable to boot. Worried I had already ****ed up, I did not flash the modem (since that's the part that REALLY can't go back AFAIK)
3) Flashed TWRP linked from http://zidroid.com/how-to-install-twrp-root-galaxy-s6-edge-on-android-5-1-1/ . (
Code:
heimdall flash --no-reboot --6 recovery.img
).
Still couldn't boot into recovery.
4) Flashed a 5.1.1 kernel to see if that would help me boot: S6_UniKernel_v8-0002-ODIN from http://forum.xda-developers.com/gal...d-development/kernel-stockmod-kernel-t3100395 .
Now I'm stuck. I can't get into recovery mode to flash the actual rom, and my 5.0.2 OS doesn't match my 5.1.1 bootloader or kernel. If I could flash a 5.1.1 OS from heimdall that would be my next step, but I can't find one to use, and I'm not sure which partition(s) it would go to anyway.
On the download mode screen I see
Code:
ODIN MODE
PRODUCT NAME: SM-G925F
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
REACTIVATION LOCK: OFF
Secure Download: Enabled
KNOX WARRANTY VOID: 1 (0x0304)
AP SWREV: B: 2 K:2 S:2
Please help! How I can get to recovery mode from here?
I dusted off an old Windows machine and fired it up, just to use ODIN. Found a vanilla 5.1.1 ROM for ODIN, and installed it from there... and it worked perfectly!
I don't understand why so many ROMs exist for odin, but no one packages for Heimdall. Heimdall seems much more reliable, and it's cross platform! Plus, we actually know what it's doing... /rant
Anyway, for whatever unlucky soul finds this... Flashing 5.1.1 via ODIN involved overwriting boot.img, cache.img, recovery.img, system.img, and modem.bin . Of course that's just one step for ODIN, you get a single .tar.md5 file, press the "AP" button to load it in, and it flashes those files to the right partitions in sequence.
So unless you have all of those files, I guess you can't do an update with Heimdall. You actually NEED a windows device.
ohthehugemanatee said:
I dusted off an old Windows machine and fired it up, just to use ODIN. Found a vanilla 5.1.1 ROM for ODIN, and installed it from there... and it worked perfectly!
I don't understand why so many ROMs exist for odin, but no one packages for Heimdall. Heimdall seems much more reliable, and it's cross platform! Plus, we actually know what it's doing... /rant
Anyway, for whatever unlucky soul finds this... Flashing 5.1.1 via ODIN involved overwriting boot.img, cache.img, recovery.img, system.img, and modem.bin . Of course that's just one step for ODIN, you get a single .tar.md5 file, press the "AP" button to load it in, and it flashes those files to the right partitions in sequence.
So unless you have all of those files, I guess you can't do an update with Heimdall. You actually NEED a windows device.
Click to expand...
Click to collapse
hi there i did the same thing as the op and my situation is identical but i am using windows so could you please help me because i am stuck now.
Just flash a custom recovery, boot into recovery, wipe everything then flash the custom rom. Pretty simple stuff no rocket science involved
Related
Hello everyone,
I want to share my experience with rooting (n00b). So for the first time ever, I managed to root my g900t and my p-600 note --needless to say, I was very excited. When everything checked out and Root Checker told me that I was indeed rooted, the first thing I did was going to Youtube to see what I could do first.
The very first thing that came up was to create a Custom Recovery...fair enough. I watched multiple videos that guaranteed to install the CR "easily". Well, I think I'm an idiot because I couldn't get anything to work.
I tried TWRP, CWM, Philz Touch and TWRP and Philz both loaded on my recovery boot but I still kept getting messages on Rom Manager that I didn't have a custom recovery. At times I also got a lot of errors. I not only tried to get information from the forum but their respective sites and matching my device, installing it through flash & Odin--no luck.
Anyways, I soft-bricked both my g900t and my p600 and after reading hundreds of posts here and other forums and spending all day, I managed to get them running again.
Right now, I'm thankful that I have both devices running and rooted but I still don't know if I have a custom recovery and frankly, I'm scared to try it again. How important is it to get a CR?
By the way, is it bad that all those bad CRs that I installed are still there (if they are)?
I read the rules and also a a lot of forum posts with different variations of CRs for my devices with no luck.
For reference:
Galaxy s5 (5.1.1) Rooted SM-G900T
Samsung Note 10.1 (5.1.1) (Wi-fi) Rooted SM-P600
Thanks guys!
Flashing TWRP through ODIN is very simple - lots of guides out there, but here are some steps:
- Install Samsung Mobile Driver
- Download and unzip ODIN 3 (e.g, 3.1.0.7) to a directory
- Download twrp-2.8.7.0-klte.img.tar from twrp.me
- Boot phone into Download Mode (Vol Down - Home - Power), follow instruction to get to the download mode
- Connect phone to PC, wait for the drivers to be ready
- Start Odin, wait for "Added" message to show up
- Click AP and choose the TWRP tar file
- Go
Sometimes a trick is to uncheck "auto reboot", then flash it twice. That is, flash once, when completely done ("success" on Odin), disconnect and remove/replace battery, power up to boot mode again, then flash again. This is rarely needed but I've had to do this for modem flash once or twice in the past.
Alternatively, you can flash it on the phone from a terminal/cmd shell (lots of apps to choose from on Google Play), and if you have twrp.img extracted to /sdcard, you can do this (again, on the phone):
> su
# dd if=/sdcard/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
The dd method is also doable from ADB shell, but that requires ADB to be set up on the PC.
Hope this helps - I wrote the steps the above from memory but others can correct me I stated anything inaccurately.
EDIT: there are also apps that can install custom recovery, such as Flashify, TWRP manager, ROM Toolbox, Nandroid Manager, etc. Of course, root is required.
many thanks
lost_ said:
Flashing TWRP through ODIN is very simple - lots of guides out there, but here are some steps:
- Install Samsung Mobile Driver
- Download and unzip ODIN 3 (e.g, 3.1.0.7) to a directory
- Download twrp-2.8.7.0-klte.img.tar from ]
- Boot phone into Download Mode (Vol Down - Home - Power), follow instruction to get to the download mode
- Connect phone to PC, wait for the drivers to be ready
- Start Odin, wait for "Added" message to show up
- Click AP and choose the TWRP tar file
- Go
Sometimes a trick is to uncheck "auto reboot", then flash it twice. That is, flash once, when completely done ("success" on Odin), disconnect and remove/replace battery, power up to boot mode again, then flash again. This is rarely needed but I've had to do this for modem flash once or twice in the past.
Alternatively, you can flash it on the phone from a terminal/cmd shell (lots of apps to choose from on Google Play), and if you have twrp.img extracted to /sdcard, you can do this (again, on the phone):
> su
# dd if=/sdcard/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
The dd method is also doable from ADB shell, but that requires ADB to be set up on the PC.
Hope this helps - I wrote the steps the above from memory but others can correct me I stated anything inaccurately.
EDIT: there are also apps that can install custom recovery, such as Flashify, TWRP manager, ROM Toolbox, Nandroid Manager, etc. Of course, root is required.
Click to expand...
Click to collapse
Thank you lost_,
my issue wasn't rooting the devices --they both are, it's getting a custom recovery installed. Neither TWRP nor CWM can find a recovery for my device (g900t). I've looked at countless posts with the same luck. At one point at recovery I had TWRP, which from what I was reading, it meant that I had a custom recovery, right? but again, TWRP and CWM say that I don't have one installed and when I tried to reboot out of recovery it would go into a boot loop forcing me to re-root my device. Basically, I'm stuck at this point and all I really want is to backup all my apps so that they run from my SD card, no coding, no custom roms but it gives me issues. Thanks again.
molotovgod said:
Thank you lost_,
my issue wasn't rooting the devices --they both are, it's getting a custom recovery installed. Neither TWRP nor CWM can find a recovery for my device (g900t). I've looked at countless posts with the same luck. At one point at recovery I had TWRP, which from what I was reading, it meant that I had a custom recovery, right? but again, TWRP and CWM say that I don't have one installed and when I tried to reboot out of recovery it would go into a boot loop forcing me to re-root my device. Basically, I'm stuck at this point and all I really want is to backup all my apps so that they run from my SD card, no coding, no custom roms but it gives me issues. Thanks again.
Click to expand...
Click to collapse
No offense intended, I think you're lost and confused. My post was never about rooting. I did understand you were rooted already. I was outlining how to install a custom recovery, which TWRP and CWM are. Yeah, if you're having a hard time sorting things out based on what I outlined, I don't know how else to get you going. Perhaps start over with your research and read up again on some basic Android 101 (not a HOWTO but an explanation on what is what). Good luck!
ps: this thread should be on the Q&A forum, but we're all helpful and friendly here and you should ask specific questions on that forum instead.
if you're using stock samsung recovery & its stock android, they will overwrite what you just flashed when they boot
odin->flash twrp WITHOUT reboot option->remove battery->put battery->turn on phone directly into recovery, you should see TWRP & you'll be able to flash whatever you want from here, i have no idea what happens if you boot to stock after this since i use CM
i came from stock 4.4 november 2014, used odin 3.07 & https://dl.twrp.me/klte/ 2.8.7.0
kn00tcn said:
if you're using stock samsung recovery & its stock android, they will overwrite what you just flashed when they boot
odin->flash twrp WITHOUT reboot option->remove battery->put battery->turn on phone directly into recovery, you should see TWRP & you'll be able to flash whatever you want from here, i have no idea what happens if you boot to stock after this since i use CM
i came from stock 4.4 november 2014, used odin 3.07 &TWRP 2.8.7.0
Click to expand...
Click to collapse
I have the same phone and cannot flash custom recovery either, as I am a linux user I used heimdall and here is my output
Code:
[[email protected] Downloads]# heimdall flash --RECOVERY twrp-2.8.7.0-klte.img --no-reboot
Heimdall v1.4.1
Copyright (c) 2010-2014 Benjamin Dobell, Glass Echidna
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
Initialising connection...
Detecting device...
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
ERROR: Failed to send request to end PIT file transfer!
ERROR: Failed to download PIT file!
Ending session...
ERROR: Failed to send end session packet!
Releasing device interface...
Re-attaching kernel driver...
[[email protected] Downloads]#
I flashed my wife's Samsung Galaxy S3 (GT-i9300) and my Galaxy Tab 2 (GT-P5113) a successfully using the procedure described in each device wiki in cyanogenmod page, but same procedure in my phone fails.
My Samsung Galaxy S5 (GT-G900T) is running Samsung's stock Android 5.1.1 (not rooted btw) and stock recovery.
Can you spot what I am doing wrong? Thank you in advance.
pablomino said:
I am a linux user I used heimdall
Click to expand...
Click to collapse
https://github.com/Benjamin-Dobell/Heimdall/issues/209 i couldnt use heimdall either, but there is a patch in that thread that might work for you, you just have to recompile yourself if they didnt update the linux binary
if that still doesnt work, i think you should just use virtualbox to run windows7 & odin with whatever the option is called to have usb pass-through/direct usb access
kn00tcn said:
if that still doesnt work, i think you should just use virtualbox to run windows7 & odin with whatever the option is called to have usb pass-through/direct usb access
Click to expand...
Click to collapse
I moved to a physical Win7 PC, it didn't work either, same error. Could it be because the device is already on Android 5?
Thank you a lot.
Code:
Microsoft Windows [Versión 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. Reservados todos los derechos.
C:\>cd heimdall
C:\heimdall>heimdall version
v1.4.0
C:\heimdall>cd Drivers
C:\heimdall\Drivers>zadig
C:\heimdall\Drivers>zadig
C:\heimdall\Drivers>cd ..
C:\heimdall>heimdall flash --RECOVERY twrp-2.8.7.0-klte.img --no-reboot
Heimdall v1.4.0
Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
ERROR: Failed to send request to end PIT file transfer!
ERROR: Failed to download PIT file!
Ending session...
ERROR: Failed to send end session packet!
Releasing device interface...
C:\heimdall>
---------- Post added at 08:42 PM ---------- Previous post was at 08:13 PM ----------
kn00tcn said:
you just have to recompile yourself
Click to expand...
Click to collapse
Anyway I will try compiling the tool from source, I will update with my results. Thank you lot.
pablomino said:
I moved to a physical Win7 PC, it didn't work either, same error.
Click to expand...
Click to collapse
i said to use odin, i have done it several times already, although some people say a newer odin is needed for lollipop based samsung installations... i mentioned 3.07 earlier, today i did 3.10.7 with the latest G900TUVS1FOL1 complete package from sammobile so i can update my baseband & bootloader easily, then once again odin->flash twrp without reboot->remove battery->boot into twrp recovery->flash CM
heimdall does not have the code update that supposedly fixes the PIT error in the official windows binaries, so heimdall will never work on windows unless you compile the fix yourself
(if using odin, always check the exe on virustotal, always get it from someplace reliable like sammobile or an active thread here rather than google)
kn00tcn said:
i said to use odin
Click to expand...
Click to collapse
This solved my problem, thank you a lot.
Hey
Yesterday I flashed a boot logo on my SM-G928F in TWRP. After that my phone doesn't boot into system or recovery anymore - there's always a blackscreen. I only can boot into download mode.
I tried to flash a stock-rom via Odin but that didn't helped - the same blackscreen, because a stock rom does not replace the boot logo.
I think I have to flash the stock boot logo ( https://drive.google.com/file/d/1378RQ5w_vAAmnQ3HB0FymZXWIm12T0Mg/view ) , but thats a zip which I can't flash via Odin.
There a two ways in my mind which could work:
1. Getting a tar.md5 file with the stock boot logo.
2. Getting a tool which allows to flash zips in download mode of the phone.
I really hope that someone could help me with my big problem.
Best regards
DGB
Hey there
I recommend to flash the firmware again but this time after flashing firmware flash the twrp and flash the zip via adb sideload ( a feature present in TWRP) as by adb sideload one is able to flash zip files as well
Or i recommend you to get to know the combination of keys that will help you to directly enter into recovery
Hope it will work
And if there is any problem let me know
As in the internet there are various ways by which a person can flash the custom rom and custom recovery via odin
Look at this link:-
http://www.lineageosrom.com/2017/07/how-to-flash-custom-rom-via-odin.html?m=1
nr10prashant said:
Hey there
I recommend to flash the firmware again but this time after flashing firmware flash the twrp and flash the zip via adb sideload ( a feature present in TWRP) as by adb sideload one is able to flash zip files as well
Or i recommend you to get to know the combination of keys that will help you to directly enter into recovery
Hope it will work
And if there is any problem let me know
As in the internet there are various ways by which a person can flash the custom rom and custom recovery via odin
Look at this link:-
http://www.lineageosrom.com/2017/07/how-to-flash-custom-rom-via-odin.html?m=1
Click to expand...
Click to collapse
Thank you for your answer but that didn't worked. The problem is that flashing the stock firmware doesn't replace or repair the boot image. So I've got a never ending blackscreen when I want to boot in system or TWRP/Recovery and that means that I'm not able to configure ADB Sideload.
I can only boot into download mode, nothing else.
I think the jpg of the boot logo I've installed was corrupted so it can't be loaded
You are in download mode so you have to press all the keys including the home button and once the download mode closes then press the "volume up key and power key and also the home button and then your phone will automatically reboot into recovery.
I know, I tried that multiple times but it doesn't work. Blackscreen... only a never ending blackscreen. The download mode is the only thing taht works. I have to flahs the old boot logo via download mode... but i don't know how
Wait for the battery to be drained out completely and then do what i said earlier
nr10prashant said:
Wait for the battery to be drained out completely and then do what i said earlier
Click to expand...
Click to collapse
I did. but it didn't work, too
I really need someone who is able to integrate the stock boot logo into a custom rom which can be flashed via Odin... Or I need a tool which allows to install zips in download mode. I tried adb sideload again but it didn't recognizes my phone when its not in recovery.
I really think that my S6 edge + is nearly died :crying:
Try to flash the firmware with the samsung smart swith.....
This will 100% works!!!!!4
Inderpreets said:
Try to flash the firmware with the samsung smart swith.....
This will 100% works!!!!!4
Click to expand...
Click to collapse
I know but Samsung removed this feature some months ago so I'm not able to do this
--- I know, it's from the German Samsung Support but it's a confirmation that Samsung removed this feature:
DGB100 said:
I know but Samsung removed this feature some months ago so I'm not able to do this
--- I know, it's from the German Samsung Support but it's a confirmation that Samsung removed this feature:
Click to expand...
Click to collapse
Not even flashing a factory firmware (4 files with pit) with repartition option selected?
What about a combination firmware and then a full stock FW?
яι¢αя∂σ said:
Not even flashing a factory firmware (4 files with pit) with repartition option selected?
What about a combination firmware and then a full stock FW?
Click to expand...
Click to collapse
I only tried to flash stock firmware with AP in Odin... and I tried stock rom with re-partition.
Where do I get those 4 files? I need XEU for my SM-G928F. It would be very nice if you could give me a more detailed instruction for this because I never worked with PIT...
get samfirm v0.3.6
On the model you put sm-g928f, region XEU, tick the binary nature box and press "check update". Download the resulting file, that is a factory firmware to do repairs in a 4 files format: bootloader, pda or ap, modem or cp and csc!
You will get this file:
SM-G928F_1_20180305151001_nsg8uwd0sh_fac.zip
Put each file in the correct field in odin!
About combination firmware, it needs to be same binary version as stock firmware already programed on phone! if first number on firmware version is a 3, combination FW need to be also bin 3!
G928FXXS4CRB4 if is 4, you need comb fw also in bin 4! if you downgrade you get odin error and a softbrick!
Was checking if any comb. fw is available, but i find only paid files for your phone model!
яι¢αя∂σ said:
get samfirm v0.3.6
On the model you put sm-g928f, region XEU, tick the binary nature box and press "check update". Download the resulting file, that is a factory firmware to do repairs in a 4 files format: bootloader, pda or ap, modem or cp and csc!
You will get this file:
SM-G928F_1_20180305151001_nsg8uwd0sh_fac.zip
Put each file in the correct field in odin!
About combination firmware, it needs to be same binary version as stock firmware already programed on phone! if first number on firmware version is a 3, combination FW need to be also bin 3!
G928FXXS4CRB4 if is 4, you need comb fw also in bin 4! if you downgrade you get odin error and a softbrick!
Was checking if any comb. fw is available, but i find only paid files for your phone model!
Click to expand...
Click to collapse
Thanks it worked for me but now I need a pit-file. Do you now where I get it?
EDIT: I found a pit-file for myself. Thank you very much for your help!
HTML:
https://drive.google.com/file/d/0BzyeAt2hy6XednpHZmhRUmtOMFk/view
DGB100 said:
Thanks it worked for me but now I need a pit-file. Do you now where I get it?
EDIT: I found a pit-file for myself. Thank you very much for your help!
HTML:
https://drive.google.com/file/d/0BzyeAt2hy6XednpHZmhRUmtOMFk/view
Click to expand...
Click to collapse
It worked means you got your phone back to normal or you could get the firmware using samfirm?
Pit file is always inside csc file on a 4 files fac firmware. Use the pit on firmware because the pit from your link can be from a early version of android and have different bits for partition sizes!
EDIT: Here, got the combination fw for the binary 4. IF your phone is already ok, don't use this!
DGB100 said:
I know but Samsung removed this feature some months ago so I'm not able to do this
--- I know, it's from the German Samsung Support but it's a confirmation that Samsung removed this feature:
Click to expand...
Click to collapse
SmartSwitch still works for my G925v.
яι¢αя∂σ said:
It worked means you got your phone back to normal or you could get the firmware using samfirm?
Pit file is always inside csc file on a 4 files fac firmware. Use the pit on firmware because the pit from your link can be from a early version of android and have different bits for partition sizes!
EDIT: Here, got the combination fw for the binary 4. IF your phone is already ok, don't use this!
Click to expand...
Click to collapse
I got my phone back to normal so thank you very much!
I have the same problem on my j2 prime I can only goto download mode and in odin tried to install stock firmware but got write fail..can you please help me with this error
As stated on the title I tried to do SamFAIL on my N950, it was on latest Oreo and I didn't know it would not work (my mistake)
I did the system flash with the .pit file on comsy odin successfully (it finished with fail as expected) but after that I cant flash anything.
I downloaded many official FW packages, Nougat and Oreo everything fails on official Odin, gives model mismatch error on comsy odin.
The only file I can flash is this : HOME_CSC_OYN_N950UOYN4CRD7_CL13303302_QB17839096_REV00
Its from the Oreo official package. If I try the regular CSC it fails as everything else. HOME CSC from nougat versions fail as well.
What I have tried so far:
Other Computer, Windows 7/10, other cable, all versions of odin (only 3.12.3 flashes home csc successfully), Smart Switch says unsupported device, no recovery mode stuck on Emergency Mode, sometimes it boots to normal download Mode
Is there a trick to force the flash? Did I break my device by doing the .pit flash? I thought that official FW would always flash no matter what... Hope someone has some ideas. Thanks in advance!
Hello
I have a Samsung J7 on which I successfully ran a custom ROM (LineageOS).
Today I was playing around in Developer Settings and foolishly disabled OEM Unlocking. I had no idea what that would cause. After the next reboot my phone is now stuck in the dreaded FRP lock state. Of course, I now can’t get into recovery mode.
Having read up on this, my understanding is that flashing the phone with a stock firmware should get me up and running again.
So I found what I think is the correct firmware from updato.com
I’m running on a Linux environment and used heimdall to flash my device last time, when I installed my custom ROM. The command I used then was
Code:
sudo heimdall flash --RECOVERY twrp-xxx.img --no-reboot
However, what I downloaded from updato.com is a zip containing five files:
Code:
AP_J730FXWU1AQF6_CL11460356_QB13916694_REV00_user_low_ship_meta.tar.md5
BL_J730FXWU1AQF6_CL11460356_QB13916694_REV00_user_low_ship.tar.md5
CP_J730FXXU1AQF1_CP6623266_CL11460356_QB13769558_REV00_user_low_ship.tar.md5
CSC_OJK_J730FOJK1AQG1_CL11901644_QB14314170_REV00_user_low_ship.tar.md5
HOME_CSC_OJK_J730FOJK1AQG1_CL11901644_QB14314170_REV00_user_low_ship.tar.md5
I have no idea what to do next. Should I flash one of them or several/all of them? And which partition should I specify to flash into? Is it still RECOVERY or should it be another one? I don’t want to hard brick my device, so need you help please.
Device: Samsung Galaxy J7 Pro (SM-J730F)
Error message: Custom binary blocked by FRP Lock.
Thank you for reading
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