Hello dear friends
I tried to install TWRP Recovery on my Samsung Galaxy A50 A505fn - https://forum.xda-developers.com/galaxy-a50/development/recovery-twrp-galaxy-a50-t3916199 following the exact instructions given in the guide above. After I factory reset the phone and enabled the USB Debugging and OEM Unlock options in the Developer Options menu, I used Odin 3.13.3 and loaded the Magisk Patch file onto the AP Field(while in download mode). After restarting the phone it stuck in a bootloop reaching the samsung logo and resetting again saying that the phone is not running samsung software.
After an unsuccessful try to flash the stock firmware(downloaded the right firmware online - Germany) I went back to download mode and selected the option Lock Bootloader and Factory Reset as a last resort.
Odin Log:
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1303)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 68 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> NAND Write Start!!
<ID:0/003> SingleDownload.
<ID:0/003> vbmeta.img
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> RQT_CLOSE !!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1303)..
<ID:0/003> File analysis..
<ID:0/003> skip file list for home binary
<ID:0/003> param.bin
<ID:0/003> userdata.img
<ID:0/003> Home Binary Download
<ID:0/003> Total Binary size: 5511 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> NAND Write Start!!
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> up_param.bin
<ID:0/003> cm.bin
<ID:0/003> keystorage.bin
<ID:0/003> uh.bin
<ID:0/003> vbmeta.img
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> __XmitData_Write
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Now the phone launches into download mode after a short show-up of the text screen with the "not running official Samsung software" .
Download mode says " Error verifying vbme....: OK_NOT_SIGNED (3)
CUSTOM VBMETA
VBMETA : No sign info
VBMETA ,
I cannot get any further than this, so I would be thankful for any help :highfive:
If any other info is required I'm here to answer.
Kind regards
OblakKoz said:
Hello dear friends
I tried to install TWRP Recovery on my Samsung Galaxy A50 A505fn - https://forum.xda-developers.com/galaxy-a50/development/recovery-twrp-galaxy-a50-t3916199 following the exact instructions given in the guide above. After I factory reset the phone and enabled the USB Debugging and OEM Unlock options in the Developer Options menu, I used Odin 3.13.3 and loaded the Magisk Patch file onto the AP Field(while in download mode). After restarting the phone it stuck in a bootloop reaching the samsung logo and resetting again saying that the phone is not running samsung software.
After an unsuccessful try to flash the stock firmware(downloaded the right firmware online - Germany) I went back to download mode and selected the option Lock Bootloader and Factory Reset as a last resort.
Odin Log:
Now the phone launches into download mode after a short show-up of the text screen with the "not running official Samsung software" .
Download mode says " Error verifying vbme....: OK_NOT_SIGNED (3)
CUSTOM VBMETA
VBMETA : No sign info
VBMETA ,
I cannot get any further than this, so I would be thankful for any help :highfive:
If any other info is required I'm here to answer.
Kind regards
Click to expand...
Click to collapse
Download newest firmware and reflash stock.I think you flashed older firmware.
Thanks for the answer muhamet! The problem is I cannot even get to flash this one since odin stucks at recovery.img. however I am past that because odin can no more do anything in the download mode I am stuck in. I am thinking about something using fastboot or adb, but I dont have any experience to get an idea what may do the job
OblakKoz said:
Thanks for the answer muhamet! The problem is I cannot even get to flash this one since odin stucks at recovery.img. however I am past that because odin can no more do anything in the download mode I am stuck in. I am thinking about something using fastboot or adb, but I dont have any experience to get an idea what may do the job
Click to expand...
Click to collapse
Samsung doesn't have fastboot.You flashed firmware whit old bootloader,because of that you're stuck.Just go to samifirmware and download newest JANUARY firmware and go to download mode.Connect phone to pc press volume up and down same time you will boot to download mode.Then flash firmware.
OblakKoz said:
Thanks for the answer muhamet! The problem is I cannot even get to flash this one since odin stucks at recovery.img. however I am past that because odin can no more do anything in the download mode I am stuck in. I am thinking about something using fastboot or adb, but I dont have any experience to get an idea what may do the job
Click to expand...
Click to collapse
Are you flashing the NON patched TWRP or the PATCHED TWRP ? as you flash the MAGISK_PATCHED file in AP field you must flash the PATCHED TWRP otherwise the phone won't boot
it' same thing with me need help please.i flash file AP with mgisk patched. not worked when try to flash back to official firmware
brounxx said:
it' same thing with me need help please.i flash file AP with mgisk patched. not worked when try to flash back to official firmware
Click to expand...
Click to collapse
check fail (bootloader) device:5 binary:3
lit flash binary - unsupported version
brounxx said:
check fail (bootloader) device:5 binary:3
lit flash binary - unsupported version
Click to expand...
Click to collapse
what must i do?
Related
Hello,i recently got Note 8.0 N5100 with official 4.2.2 and i decided to root it. I used CF-Auto-Root and followed instructions, downloaded newest drivers and everything went well in odin 3.07 but after odin finished i got stuck wirh samsung galaxy note logo and nothing happens now.
what shall i do now, can anybody please help me!!!!!!!
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-espresso10rf-espresso10rfxx-gtp5100.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> cache.img
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Problem solved. I exidently when i was using search in cf auto root website downloaded wrong cf file for p5100 instead of n5100.
miloslavc said:
Hello,i recently got Note 8.0 N5100 with official 4.2.2 and i decided to root it. I used CF-Auto-Root and followed instructions, downloaded newest drivers and everything went well in odin 3.07 but after odin finished i got stuck wirh samsung galaxy note logo and nothing happens now.
what shall i do now, can anybody please help me!!!!!!!
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-espresso10rf-espresso10rfxx-gtp5100.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> cache.img
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Problem solved. I exidently when i was using search in cf auto root website downloaded wrong cf file for p5100 instead of n5100.
Click to expand...
Click to collapse
Your not the only one who had this problem... I which the mod would shut down the thread pushing rooting via flashing.
Too many newbies are having issues flashing.
I recommend saveroot.zip. It leaves your device's counter untouched. Also it is 100% safe.
Now what to do with your device since it is stuck at the Samsung logo.
You can do what I do for stuck screens. Power on, and hold only the up volume key. Keep it held until boot screen is finished.
If that does not work, go into recovery and clear cache and reboot.
If none of the options work, you may have flashed with an incompatible file, there are three versions and only one is specific to your device. you can try re-flashing with a good file.
saveroot
Hello,
I am having a heck of a time finding this. Would you please point me in the right direction?
Thx!
gooberdude said:
Your not the only one who had this problem... I which the mod would shut down the thread pushing rooting via flashing.
Too many newbies are having issues flashing.
I recommend saveroot.zip. It leaves your device's counter untouched. Also it is 100% safe.
Now what to do with your device since it is stuck at the Samsung logo.
You can do what I do for stuck screens. Power on, and hold only the up volume key. Keep it held until boot screen is finished.
If that does not work, go into recovery and clear cache and reboot.
If none of the options work, you may have flashed with an incompatible file, there are three versions and only one is specific to your device. you can try re-flashing with a good file.
Click to expand...
Click to collapse
Hi, i have a GT-N5100 running 4.4.2 Kitkat
My problem is i can't boot to recovery and it says:
Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again later.
But i can boot in Download Mode.
My phone keeps blinking and it won't charge, so, I've tried to flash the stock rom via ODIN and it says:
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N5100XXDNG2_N5100OXEDNG1_N5100XXDNE2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> tz.img
<ID:0/003> boot.img
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
While flashing the ROM, i saw this code:
Code:
KNOX WARRANTY VOID 0
RP SWREV A1
And I've tried several times, but it always FAILS!
I've tried to go to Recovery mode through Kies,
>Firmware Upgrade and Initialisation >Type the Model Name: and it did not detect the Phone.
Hoping that someone can help me with this. Thanks guys!
rongregoryred said:
Hi, i have a GT-N5100 running 4.4.2 Kitkat
My problem is i can't boot to recovery and it says:
Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again later.
But i can boot in Download Mode.
My phone keeps blinking and it won't charge, so, I've tried to flash the stock rom via ODIN and it says:
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N5100XXDNG2_N5100OXEDNG1_N5100XXDNE2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> tz.img
<ID:0/003> boot.img
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
While flashing the ROM, i saw this code:
Code:
KNOX WARRANTY VOID 0
RP SWREV A1
And I've tried several times, but it always FAILS!
I've tried to go to Recovery mode through Kies,
>Firmware Upgrade and Initialisation >Type the Model Name: and it did not detect the Phone.
Hoping that someone can help me with this. Thanks guys!
Click to expand...
Click to collapse
Use Odin v3.07 and flash in PDA mode. Also, make sure you have the right tar file for your Note and turn Kies off so it doesn't interfere with Odin.
CCallahan said:
Use Odin v3.07 and flash in PDA mode. Also, make sure you have the right tar file for your Note and turn Kies off so it doesn't interfere with Odin.
Click to expand...
Click to collapse
Thanks! I will try that! :good:
Edit: Fail. Did'nt work also. Hmm. I will try kies again.
rongregoryred said:
Thanks! I will try that! :good:
Edit: Fail. Did'nt work also. Hmm. I will try kies again.
Click to expand...
Click to collapse
If you are sure you have the correct file for your device and are using Odin correctly, might try using Heimdall to flash instead of Odin: http://glassechidna.com.au/heimdall/
I had a similar problem with my note 8.0. I can't remember exactly what I did but I managed to get it to reboot. It'll reboot to download but after it booted into download mode my Odin was able to find it.
---------- Post added at 09:19 PM ---------- Previous post was at 09:03 PM ----------
I think maybe holding down the power button should reboot it.
CCallahan said:
If you are sure you have the correct file for your device and are using Odin correctly, might try using Heimdall to flash instead of Odin: http://glassechidna.com.au/heimdall/
Click to expand...
Click to collapse
Tried heimdall, but no work. I think it's because of Knox. It won't flash Stock rom through Odin or heimdall.
BTW, i flashed a recovery through Odin and it works. Now im running a Custom Rom. Thanks for the help guys!
I'm currently in the same situation
What recovery did you flash?
I odin 4.4.4 poland.. it failed, it says Firmware upgrade encountered an issue. Please select recovery mode in Kies
I can't go to recovery, I tried to odin recovery but no luck
and in odin mode it says Secure Download : enabled
EDIT: I use philz_touch_6.48.4-n5100.tar.md5.. and it works
Our daughter deleted all of the pics on my wife's phone. She tried to use Dr. Fone, but someone told us that it failed because her phone wasn't rooted. So I tried to root it from this post on cnet:
It failed during the root. Now it says "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again. Which I tried and also failed.
After a lot of heart ache and hours working on it, i have what a friend told me was the right tar file. I have attached the error in Odin.
When I run the tar file in Odin here is what the output screen shows:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747UCDLK3_I747ATTDLK3_I747UCDLK3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Then my phone screen show this:
SW REV CHECK FAIL : Fused 3 > Binary 0
Not really my area of expertise at all. Any help would be appreciated!!
Thanks,
Brian
You cannot flash that tar file onto your phone. It is failing because that file is trying to downgrade the bootloader.
I recommend not flashing anymore files until you know the bootloader version of your phone.
I recommend you flash the latest Philz Touch custom recovery using desktop Odin from here:https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
Use Philz to flash the latest CM11 and Gapps. Then install the Samsung Phone Info app from the play store to verify your bootloader.
Once you know your bootloader, let us know the version.
Need help recovering SM-T310 8", stuck at boot screen, Odin won't load TWRP onto it
I've been trying to get this tab back in working order for several hours now - When I first started working on it, all it showed was the "Samsung Galaxy Tab 3" screen, going right back to that when I turn it off (not even staying off.) I tried putting it in download mode (Power+Down+Home, it does work) and loading TWRP 3.1.1 with Odin (tried both 3.07 and 3.12.3) and it fails almost immediately after hitting Start, Kies won't recognize it over USB, and when I put in the model and S/N it says it's "not eligible".
Also, I've tried using the stock recovery mode, but the factory reset doesn't help, and it doesn't recognize the format of the only rom I could find for it (that doesn't require a premium membership.) It's a .tar.md5, TWRP is supposed to be able to handle it, but the system recovery doesn't see it at all.
(click for big)
Here's the Odin log:
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T310.TWRP.3.1.1-0.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
Help, please? I've gone through multiple past threads here and on other sites I found on Google to get this far, but I've been unable to make any appreciable progress.
Hi all,
Some quick background: A few days ago while I was using my S9 plugged in, my device all of a sudden froze. I did a force restart (Volume Down + Power) and from then on my phone would boot up, get to the white 'Samsung' logo then shut down and restart over and over. It never could get past the 'Samsung' logo. I tried a bunch of the solutions in Recovery Mode that I could find on the internet (wipe cache, etc.) and nothing worked so I ended up as a final resort going with the factory reset option. The same issue persisted after factory reset which lead me to this forum and giving Odin a try.
I found the correct firmware for my phone from this site which matched the firmware my device showed in recovery mode. I initially bought the phone through Rogers but switched to Bell and had them unlock it. I followed the instructions from this forum trying both the Bell and Rogers firmware's which gave me a FAIL! My phone read SECURE CHECK FAIL: system. I reset tried using Home CSC and CSC for both firmware's and neither worked. Then I downloaded the patched Odin3 v3.13.1 from here with both firmware's (after reading you may have to use it to patch unlocked phones) and got the same error. I then tried 3.14.1 and the patched version from the same forum, both giving me the exact same error. I then tried running all of the Odin programs as administrator, still the same issue. I also tried various different USB cords and ports, nothing has worked.
My phone is now stuck in Download Mode with an Error message reading 'An error has occurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC software.' but Odin still seems to be working with it so I don't think that is an issue. I tried the Smart Switch software which did not even pickup my phone like the instructions.
Below is my 'Log' from an attempt with the Bell firmware on Odin3 v3.14.1. I have gotten the same error across all Odin versions and with both firmware's. Under the 'Options' tab in Odin, Auto Reboot and F. Reset Time are selected by default. I tried deselecting one then both, as well as selecting 'Re-Partrition' and still no success
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1401)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 7172 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> NAND Write Start!!
<ID:0/003> SingleDownload.
<ID:0/003> abl.elf
<ID:0/003> xbl.elf
<ID:0/003> xbl_config.elf
<ID:0/003> tz.mbn
<ID:0/003> hyp.mbn
<ID:0/003> devcfg.mbn
<ID:0/003> pmic.elf
<ID:0/003> aop.mbn
<ID:0/003> cmnlib.mbn
<ID:0/003> cmnlib64.mbn
<ID:0/003> keymaster64.mbn
<ID:0/003> qupv3fw.elf
<ID:0/003> sec.dat
<ID:0/003> apdp.mbn
<ID:0/003> msadp.mbn
<ID:0/003> bksecapp.mbn
<ID:0/003> storsec.mbn
<ID:0/003> vaultkeeper.mbn
<ID:0/003> engmode.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> vendor.img.ext4
<ID:0/003> system.img.ext4
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Sorry for the long post. Any solutions or help that can be offered would be greatly appreciated. I am new to this so is there something I am doing wrong? Please let me know if you need anymore information
SUMMARY: Phone would not stop rebooting over and over, never making it past the 'Samsung' Logo. Tried everything I could in Recovery Mode including a factory reset. Issue persisted. Tried to flash the firmware via Odin3 v3.13.1, 3.13.1 patched, 3.14.1, 3.14.1 patched, all failed in the same spot (FAIL! Auth SECURE CHECK FAIL: system). Firmware matched what my device showed in Recovery mode. Tried 2 different carriers, one that I am currently using and one that I bought my phone through. Stuck and need help.