Bricked my phone after turning off "oem unlock" - Samsung Galaxy On5 Questions & Answers

I installed the Superstarz ROM and TWRP onto my phone (Samsung Galaxy On5) (SM-G550T). The phone booted, and everything was working fine.
Like an idiot, I decided I didn't need to keep "usb debugging" and "oem unlock" enabled, so I turned them both off. When I restarted my phone, it was stuck at the boot screen ,with "custom binary blocked by frp lock" showing in red.
I cannot boot into recovery or into the system. I'm only able to boot into download (Odin) mode. I tried to flash the stock ROM in Odin, but FRP prevents anything from being flashed. I cannot re-enable "oem unlock" or "usb debugging" because I'm unable to boot into the system.
What are my options here?

halomaster said:
I installed the Superstarz ROM and TWRP onto my phone (Samsung Galaxy On5) (SM-G550T). The phone booted, and everything was working fine.
Like an idiot, I decided I didn't need to keep "usb debugging" and "oem unlock" enabled, so I turned them both off. When I restarted my phone, it was stuck at the boot screen ,with "custom binary blocked by frp lock" showing in red.
I cannot boot into recovery or into the system. I'm only able to boot into download (Odin) mode. I tried to flash the stock ROM in Odin, but FRP prevents anything from being flashed. I cannot re-enable "oem unlock" or "usb debugging" because I'm unable to boot into the system.
What are my options here?
Click to expand...
Click to collapse
You should still be able to flash full stock from recovery, the version of Android you were on or higher. Even with frp.
Sent from my SM-T350 using Tapatalk

Koognod said:
You should still be able to flash full stock from recovery, the version of Android you were on or higher. Even with frp.
Sent from my SM-T350 using Tapatalk
Click to expand...
Click to collapse
This is what happens when I try to flash anything in Odin. Same results in both Odin 3.12.3 and 3.10.7
<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> Added!!
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Erase...
<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> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse

Flashing latest firmware will solve this problem...
Or
Other you can try Z3X Box ...
There are many tutorial on youtube..

Was there no answer to this problem or some what of a outcome? I am having the same issues,odin log identical

i have done this same thing - do not know enough about "flashing" and "roms" to understand these solutions. can someone please help?
do i need to just download Odin and try to "flash" from my pc?

fixed mine with this SM-G550T1 BRICK FRP BLOCK FIX
glennnall said:
i have done this same thing - do not know enough about "flashing" and "roms" to understand these solutions. can someone please help?
do i need to just download Odin and try to "flash" from my pc?
Click to expand...
Click to collapse
The stock rom you have is the wrong version. i got the info and fixed mine here..
https://androidforums.com/threads/galaxy-on5-metropcs-t-mobile-stock-firmware.1140060/
then i got the software from:
https://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647
the exact firmware for metropcs is:
Country/Region USA
Product Code TMK
OS Version Marshmallow (Android 6.0.1)
Release Date 23.03.2017
PDAG550T1UVU2AQC4
CSCG550T1TMK2AQC4
Phone G550T1UVU2AQC4
once downloaded and extracted it is self explanatory on where to place files in Odin (files are labeled for appropriate slots) hope this helps. mine was bricked for 2 weeks determination is the key to success.

Related

Is my phone permanently bricked?

I was updating my samsung galaxy grand prime duos (SM-G531H) with kies, not knowing my cable was broken while the updating the phone disconnected and i ended up with a screen saying "firmware upgrade encountered an issue. please select recovery mode in kies and try again" i changed the cable and decided to flash the update with odin... process went through and the phone booted up normal with the new update installed... now i decided to factory reset so i went into the stock recovery and did but it came up with a bunch of errors which i didn't take note of... i flashed twrp and repaired the file system, wiped system and then i flashed the the firmware together with the pit file on odin once more... the phone booted up normal and i was using it and eveything when i put it to charge and came back 10 mins later the phone was off.... when i powered it on it just stays on the "samsung galaxy grand prime" screen and doesn't boot... it doesn't go into recovery anymore it just hangs whe're it says "recovery is not seandroid enforcing" i tried flashing the firmware with odin again but every single time i tried it keeps failing at...
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary 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.1100)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Removed!!
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> recovery.img
<ID:0/003> system.img
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I tried the repair firmware together with the pit file and it gets stuck at
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Binary 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.1100)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
it's been like that for over an hour now... any help would be much appreciated guys.
No
Try with orignal firmware
nihu.46 said:
Try with orignal firmware
Click to expand...
Click to collapse
I tried everything and nothing seems to work
I also get this problem. Does anyone know how to fix it?
Ghettovybz said:
I tried everything and nothing seems to work
Click to expand...
Click to collapse
Remove kies. Reinstall samsung drivers.
Find and flash TWRP 3.0.0 with odin ( on recovery is not SEAndroid enforcing hold volume up and home for 5-10 seconds. Also flash the Custom Kernel by eyeless95 on the forum, its sepermissive.
u0aol said:
Remove kies. Reinstall samsung drivers.
Find and flash TWRP 3.0.0 with odin ( on recovery is not SEAndroid enforcing hold volume up and home for 5-10 seconds. Also flash the Custom Kernel by eyeless95 on the forum, its sepermissive.
Click to expand...
Click to collapse
What about for SM-G530H?
Do u have the link for the kernel?
After installing kernel what should I do then?
Two ways. Find stock rom in Sammobile and install via Odin (newest). Or try once again install it via Kies. You sould can restore it with Kies, but dont plug phone to computer. Write down S/N or something like that (it's under battery) and model, and Kies will download system
argounaut said:
What about for SM-G530H?
Do u have the link for the kernel?
After installing kernel what should I do then?
Click to expand...
Click to collapse
I have a g531h so I'm not sure. I'm below ten posts so i cant post links.
There are kernels and recoverys in the development section that work fine for your phone .

I screwed up flashing with odin. Plz halp!

SO, I made a stupid mistake and along with AP CSC and CP flashed BL to my Verizon S7. I tried to go back and do the steps correctly, but the odin flash's are failing now over and over. Get the "software update failed, use verizon repair assist." screen. Issue is in this state I can't get it in software install mode to use said repair assistant. Please tell me someone can help me fix my screw up!? I have googled and tried to solve this, but I came up empty.
T1geR086 said:
SO, I made a stupid mistake and along with AP CSC and CP flashed BL to my Verizon S7. I tried to go back and do the steps correctly, but the odin flash's are failing now over and over. Get the "software update failed, use verizon repair assist." screen. Issue is in this state I can't get it in software install mode to use said repair assistant. Please tell me someone can help me fix my screw up!? I have googled and tried to solve this, but I came up empty.
Click to expand...
Click to collapse
What did you flash, firmware wise? What are you trying to flash?
I was going from the newly updated PH1 (OTA) to Samsung_G930x_QC_Rooted_BOOT.TAR I was just not paying attention ...lol singing and goofing off but yeah I flashed BL AP CP and CSC.
ps. Then I did try to go back and flash the right things, but not surprisingly it was unsuccessful. I after that found a stock tar to try to redo the whole thing (G935VVRS4APH1_CL8875708_QB10880117_REV02_user_low_ship_MULTI_CERT.zip) and that was also failed.
T1geR086 said:
I was going from the newly updated PH1 (OTA) to Samsung_G930x_QC_Rooted_BOOT.TAR I was just not paying attention ...lol singing and goofing off but yeah I flashed BL AP CP and CSC.
ps. Then I did try to go back and flash the right things, but not surprisingly it was unsuccessful. I after that found a stock tar to try to redo the whole thing (G935VVRS4APH1_CL8875708_QB10880117_REV02_user_low_ship_MULTI_CERT.zip) and that was also failed.
Click to expand...
Click to collapse
I was having flashing issues before. I was doing it on my laptop. What I did was deleted the firmware files and re-downloaded it and was able to flash.
Sent from my SM-G930V using XDA-Developers mobile app
ickedmel said:
I was having flashing issues before. I was doing it on my laptop. What I did was deleted the firmware files and re-downloaded it and was able to flash.
Sent from my SM-G930V using XDA-Developers mobile app
Click to expand...
Click to collapse
I tried re downloading:
BL_G935VVRS4APH1_CL8875708_QB10880117_REV02_user_low_ship_MULTI_CERT.tar
AP_G935VVRS4APH1_CL8875708_QB10880117_REV02_user_low_ship_MULTI_CERT.tar
CP_G935VVRS4APH1_CL8875708_QB10880117_REV02_user_low_ship_MULTI_CERT.tar
CSC_VZW_G935VVZW4APH1_CL8875708_QB10880117_REV02_user_low_ship_MULTI_CERT.tar
HEROQLTE_USA_VZW.pit Tried several more times.
Errors:
"re-partition operation has failed" nearly immediately after start of ODIN flash every time.
On boot attempts it does "erase" and "System Update", reboots and comes up in Android Recovery with "Supported API: 3" and "dm-verity verification failed..."
If someone could point me I don't mind learning and figuring it out, but yeah....tad frusterated so I'm gonna smoke some cancer lol brb.
Are you using the modified odin? The original one wont work. The modified one is in the root guide.
Do what he suggests. Use the modified Odin. If that does not work try swapping cables, computers, etc...
craazy82013 said:
Are you using the modified odin? The original one wont work. The modified one is in the root guide.
Click to expand...
Click to collapse
PrinceComsy version and the ? non PrinceComsy version linked in http://forum.xda-developers.com/ver...-to-notes-root-install-xposed-unroot-t3411039
Neither worked. Everything failed the same way as described previously (re-partition op. failed, and on recovery dm-vert failure)
Will try again.
Flash BL AP CP CSC, or BL AP CP CSC +pit or AP CP CSC?
Want to make sure I at least get this right.
T1geR086 said:
PrinceComsy version and the ? non PrinceComsy version linked in http://forum.xda-developers.com/ver...-to-notes-root-install-xposed-unroot-t3411039
Neither worked. Everything failed the same way as described previously (re-partition op. failed, and on recovery dm-vert failure)
Click to expand...
Click to collapse
Does the phone even boot? USB debugging on?
craazy82013 said:
Does the phone even boot? USB debugging on?
Click to expand...
Click to collapse
It powers on. then go's to recovery, I have turned on USB debugging while trying to figure out wtf I did last night through maintence boot or not sure what its called but it has the option to enable debugging.
T1geR086 said:
It powers on. then go's to recovery, I have turned on USB debugging while trying to figure out wtf I did last night through maintence boot or not sure what its called but it has the option to enable debugging.
Click to expand...
Click to collapse
Check for usb debugging in maintenance mode. Power off device hold volume down and power at same time till maintenance mode shows up.
craazy82013 said:
Check for usb debugging in maintenance mode. Power off device hold volume down and power at same time till maintenance mode shows up.
Click to expand...
Click to collapse
Does it stay enabled or do I need to do it every so often. I will do it again, but I had already last night.
T1geR086 said:
Does it stay enabled or do I need to do it every so often. I will do it again, but I had already last night.
Click to expand...
Click to collapse
I would think it would stay. I know you did some of this. Im not a dev. Just trying to help. Redownload everything. Try a different computer. Different usb cable. Try everything. Gotta get back to it but ill hit up a dev and see what he thinks. Sorry if im no help brother
craazy82013 said:
I would think it would stay. I know you did some of this. Im not a dev. Just trying to help. Redownload everything. Try a different computer. Different usb cable. Try everything. Gotta get back to it but ill hit up a dev and see what he thinks. Sorry if im no help brother
Click to expand...
Click to collapse
Not trying to be short. Sorry if it came off that way. I appreciate hitting up a dev. I've been rather fixated on fixing this...*phone detox itch*
New error (or first I noticed it) when attempting to flash:
BL_G935VVRS4APH1_CL8875708_QB10880117_REV02_user_l ow_ship_MULTI_CERT.tar
AP_G935VVRS4APH1_CL8875708_QB10880117_REV02_user_l ow_ship_MULTI_CERT.tar
CP_G935VVRS4APH1_CL8875708_QB10880117_REV02_user_l ow_ship_MULTI_CERT.tar
CSC_VZW_G935VVZW4APH1_CL8875708_QB10880117_REV02_u ser_low_ship_MULTI_CERT.tar
<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.1203)..
<ID:0/003> File analysis..
<ID:0/003> skip file list for home binary
<ID:0/003> persist.img.ext4
<ID:0/003> Home Binary Download
<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> emmc_appsboot.mbn
<ID:0/003> lksecapp.mbn
<ID:0/003> xbl.elf
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Auth error instead of re-partition failure.
T1geR086 said:
New error (or first I noticed it) when attempting to flash:
BL_G935VVRS4APH1_CL8875708_QB10880117_REV02_user_l ow_ship_MULTI_CERT.tar
AP_G935VVRS4APH1_CL8875708_QB10880117_REV02_user_l ow_ship_MULTI_CERT.tar
CP_G935VVRS4APH1_CL8875708_QB10880117_REV02_user_l ow_ship_MULTI_CERT.tar
CSC_VZW_G935VVZW4APH1_CL8875708_QB10880117_REV02_u ser_low_ship_MULTI_CERT.tar
<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.1203)..
<ID:0/003> File analysis..
<ID:0/003> skip file list for home binary
<ID:0/003> persist.img.ext4
<ID:0/003> Home Binary Download
<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> emmc_appsboot.mbn
<ID:0/003> lksecapp.mbn
<ID:0/003> xbl.elf
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Auth error instead of re-partition failure.
Click to expand...
Click to collapse
What version of Odin are you using?
Illogi.xbone said:
What version of Odin are you using?
Click to expand...
Click to collapse
3.12 Princecomsy
I am DLing APE1 zip from sammobile because that's the version that shows up in recovery. heh have 2hrs left on that DL (non premium throttling)
Try using Odin 3.14
T1geR086 said:
3.12 Princecomsy
I am DLing APE1 zip from sammobile because that's the version that shows up in recovery. heh have 2hrs left on that DL (non premium throttling)
Click to expand...
Click to collapse
Dont think you can downgrade ph1. Bootloader supposedly changed. There is a faster download in the forum. Way faster. http://downloadmirror.co/29Uj/G930VVRU2APE1_G930VVZW2APE1_VZW.zip<br />
Illogi.xbone said:
Try using Odin 3.14
Click to expand...
Click to collapse
Ty will try. Best place to find that? Odin downloader lists odin3 3.11.2 as latest? Didn't see any 14 ending versions.

SM-G550T1 boot loop "Custom binary is blocked by FRP Lock"

I had used TWRP to install SuperSU to root. This seemed successful, but a day or two later the phone had powered itself off, and on power-up loops displaying the tiny red "Custom binary is blocked by FRP Lock" message. The phone will boot into download mode, but won't enter recovery mode.
I tried repeating the install of TWRP using ODIN 3.12, but now that fails. Tried installing factory images (\BL_G550T1UVU1APF1_CL8180604_QB9902404_REV00_user_low_ship.tar.md5 etc.) w/ ODIN, and that fails too.
Is this an indication I don't have the latest image files? ODIN messages below:
<ID:0/004> 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..
<ID:0/004> Odin engine v(ID:3.1203)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)​
Made some progress
Reviewing other threads I found a not that talked about installing only the "AP" file using ODIN. That seems to have worked.
BHarris said:
Reviewing other threads I found a not that talked about installing only the "AP" file using ODIN. That seems to have worked.
Click to expand...
Click to collapse
what worked? and what firmware. I have 2 on5's one sm-G-550T and a sm-g550T1 that both ended up with the "custom binary blocked by FRP lock" on the same day..
Please help!
I just tried a bin I downloaded from S U site and it didn't work. Gotta love the On5 lol.
Custom Binary Lock
The same happened to me: i have not found a complete solution, the closest i get to anything is; i put the On5 in Odin3 v3.12 and select the AP option and putting the recovery.tar file and running it. it goes good till its done and the result is Custom Binary (recovery) blocked by FRP lock in green letters. but still no success. i have tried trwp recovery, the home.tar file, each file by them selves and having trouble. i may not be an expert at this type of programimng but i pick things up quickly if there is any solution to my problem please let me know. thx............ by the way i have also tried kies and wont connect to it as well
Same Problem FRP Blocked Bootlooping
I did all the same as you and have the same problem. Everything was fine till the phone got restarted.
XDA HEEEEEEEELP!!
SeleneKnightress said:
I did all the same as you and have the same problem. Everything was fine till the phone got restarted.
XDA HEEEEEEEELP!!
Click to expand...
Click to collapse
You need to reinstall the firmware using Odin. Then, when you root again, you need to make sure you have oem unlock and usb debugging on in the developer options. Not having those on and rebooting when rooted cause the custom binary problem.

Endless boot loop/no recovery mode

I tried to root my Sprint variant with Odin (Credo mobile is the carrier). Although Odin said it PASSED, the phone went into a boot loop. I tried the Sprint firmware to unroot it - Odin said it FAILED. If I hold Volume-up/home/power, I do not get a recovery menu, but just another loop, with "Recovery Booting" flashing in blue at the top. Held the buttons a long time, did everything over, etc. I can get to download mode, and the recovery mode loop, but nothing else. Suggestions?
Kanzeon said:
I tried to root my Sprint variant with Odin (Credo mobile is the carrier). Although Odin said it PASSED, the phone went into a boot loop. I tried the Sprint firmware to unroot it - Odin said it FAILED. If I hold Volume-up/home/power, I do not get a recovery menu, but just another loop, with "Recovery Booting" flashing in blue at the top. Held the buttons a long time, did everything over, etc. I can get to download mode, and the recovery mode loop, but nothing else. Suggestions?
Click to expand...
Click to collapse
Go into download mode and try flashing the firmware again. Tell us the error and I can try and help you fix your phone. By the recovery booting error, I assume you need the pit file to repartition your phone.
Here's the whole sad story, according to Odin:
<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..
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<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> SingleDownload.
<ID:0/003> boot.img
<ID:0/003> recovery.img
<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)
The phone says:
SV REV CHECK FAIL: [system]Fused 3 > Binary 1
I don't know about pit files, but at this point I will try pretty much anything. Thank you!
im having same issue
please help
I had the same issue happened to me when trying to use Odin to flash my Galaxy S7 G930p
It would boot the very first Samsung logo in a shutdown restart and do it again repeatedly I then went back and downloaded a different firmware and it resolved the issue but now shows a unlocked padlock Below Samsung and says modified and I still don't have TWRP recovery installed but at least it fixed my boot.img I think you have flashed the wrong boot image to your phones both of you guys tell me the full model of your phone and firmware version and maybe I could help you resolve your phones
My Galaxy S7 g930p I have the Chinese version Qualcomm Virgin Mobile phone
Odin img TWRP recovery ? does anyone have the proper boot.img I need.
I'm the on android version 7.0 nauget.
Not the S7 Edge
Thank you much

SM-T510 - Trying to recover the os

Hello,
I am a newbie but I have tried reading and researching. Got past a few of my questions but got stuck so looking for some suggestions.
I have a samsung galaxy tab a sm-t510 (2019??) i believe. Its about 2 to 3 years old so the 2019 version would match. Physically looking at the device its smt-510 and it says this on the oden download mode page as well. All i have access to, to verify this. OS is dead. Here is my issue. I got this tab for my nephew and it died. It was low on battery and he just left it for like a month. Since then he said it just stopped working and kept on restarting. Reading online it seems like the battery died to the point where the charging module cant load so it cant change and boot into the os. It just keeps restarting with the error "could not do normal boot invalid Kernel length". I cannot get into the recovery mode and can only get it into the download mode. Reading online says i should just reload the firmware which should fix the issue. So this is what i am trying to do. The region for this device is in canada. Next in the download mode it says secure boot enabled and oem lock on. I cant get into the os to turn these off. I cant find a way to disable these without getting into the OS. My goal is to get it working, custom rom or oem, dont really care. I know if i load an oem firmware these settings should not matter. I've downloaded a few different versions of the oem image (sammobile and using frija).
I keep getting Re-Partition operation failed. when trying to load the image. I have tried v9 which came with the tab and tried latest v11 using frija.
I can see it connect fine and all is good but it seems like i have the wrong image and this is why i keep getting the re-partition failed? I have tried this with Oden 3.09 which has a few check boxes and one is re-partition. its unchecked. Defaults (auto reboot and f. reset time) are only on. I have also tried it with Oden 3.13.3 with same options. Again my goal is to load anything on it to get it working. Any thoughts on options and what i can do to recover this? My theory is i have the wrong image and thats why the oem and secure download is giving me an error but not sure. Any help would be nice.
just to add. if i select the home csc file i get the there is no pit partition error.
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BL_T510XXU2ASK5_CL17420370_QB27658722_REV02_user_low_ship.tar.md5 is valid.
<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> CSC_OMC_OXM_T510OXM2ASK5_CL17420370_QB27658722_REV02_user_low_ship.tar.md5 is valid.
<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> AP_T510XXU2ASK5_CL17420370_QB27658722_REV02_user_low_ship_meta_OS9.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Set PIT file..
<ID:0/008> DO NOT TURN OFF TARGET!!
<ID:0/008> FAIL!
<ID:0/008>
<ID:0/008> Re-Partition operation failed.
Thanks,
Mike

Categories

Resources