Bricked Galaxy Core Prime - Samsung Galaxy Core Prime Questions & Answers

(NOTE: This is NOT my phone, but I do have it until it's fixed)
I tried rooting this MetroPCS Galaxy Core Prime via Kingroot, something went wrong. After I rooted it, I gave it back to its owner, and he came back from Spring Break with a Samsung paperweight. Recovery doesn't work, neither does booting it up regularly. It gives me the " Custom Binary blocked by FAP. " and in red text, it says " SECURE FAIL: KERNEL " So, I was like "Hey, no biggie, let's just flash the stock firmware." Well, there's an issue there. It boots into Download mode, but it doesn't show up on Odin. I REALLY need help, as this isn't my phone. Thanks guys.

TacoTank said:
(NOTE: This is NOT my phone, but I do have it until it's fixed)
I tried rooting this MetroPCS Galaxy Core Prime via Kingroot, something went wrong. After I rooted it, I gave it back to its owner, and he came back from Spring Break with a Samsung paperweight. Recovery doesn't work, neither does booting it up regularly. It gives me the " Custom Binary blocked by FAP. " and in red text, it says " SECURE FAIL: KERNEL " So, I was like "Hey, no biggie, let's just flash the stock firmware." Well, there's an issue there. It boots into Download mode, but it doesn't show up on Odin. I REALLY need help, as this isn't my phone. Thanks guys.
Click to expand...
Click to collapse
OK first make sure the drivers are installed because I had the same problem with my galaxy prime, after that open Odin then boot into download mode.
Sent from my SM-G530T using Tapatalk

EvilDeveloper said:
OK first make sure the drivers are installed because I had the same problem with my galaxy prime, after that open Odin then boot into download mode.
Sent from my SM-G530T using Tapatalk
Click to expand...
Click to collapse
I ended up fixing it after all! Thanks for the help though. (Can a mod take this thread down?)

i bricked my galaxy core prime can you guys help? i have kies but i cant find the serial number on the phone

Pandabearzzz said:
i bricked my galaxy core prime can you guys help? i have kies but i cant find the serial number on the phone
Click to expand...
Click to collapse
Boot the phone into download mode (home, vol-, power), connect to PC with USB, and use Odin to flash the stock firmware (AP button). If you know your phone's model number I can give you a link to the stock firmware file

thisisapoorusernamechoice said:
Boot the phone into download mode (home, vol-, power), connect to PC with USB, and use Odin to flash the stock firmware (AP button). If you know your phone's model number I can give you a link to the stock firmware file
Click to expand...
Click to collapse
Thanks. Worked perfectly.

well...i still have a bricked core prime
flashed stock firmware and still get only the model number to blink on, then a vibration. same thing over and over and over.
For a split second, I was able to get into recovery mode, but only once. I picked "system reboot" and it went right back to the
model number blinking. Kies won't recognize the serial number, Odin says "success" but the phone still a no-go. Any ideas?

phoneless butthead said:
flashed stock firmware and still get only the model number to blink on, then a vibration. same thing over and over and over.
For a split second, I was able to get into recovery mode, but only once. I picked "system reboot" and it went right back to the
model number blinking. Kies won't recognize the serial number, Odin says "success" but the phone still a no-go. Any ideas?
Click to expand...
Click to collapse
Under battery there are:
IMEI
IMEI
S/N
Are you sure you input S/N not IMEI?
I did it the first time i use KIES since i am very nervous.
The phone should be put on downloading mode to perform the procedure.

Galaxy Core Prime stuck in endless boot, trying everything
Hey guys, I found this thread and I'm hoping I can figure out this massively frustrating issue with the Galaxy Core Prime as well.
It was stuck in endless boot so I downloaded the Samsung drivers to my PC and then used Odin (v3.10.7) to load twrp-3.0.2-0-coreprimelte.img.tar (from dl.twrp.me/coreprimelte/) on AP and clicked Start. Failed.
My log from Odin is below, and the phone showed "Custom Binary Recovery blocked by FRP Lock".
<ID:0/003> Added!!
<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> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> recovery.img
<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)
Now I'm trying to use Kies3 firmware upgrade to see if it'll get the phone out of endless boot mode but it required a serial number and I don't have one. Don't have the box, and it's not on the sticker.
Check it out -- am I nuts or is this void of SN?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Meanwhile I'm downloading the firmware to flash with Odin but it's going to be a while before the download finishes... so in the mean time I'm trying whatever I can.
I tried looking up how to bypass the FRP lock but couldn't find directions that involved not being able to boot the actual phone.
Any ideas?

heymishka said:
Hey guys, I found this thread and I'm hoping I can figure out this massively frustrating issue with the Galaxy Core Prime as well.
It was stuck in endless boot so I downloaded the Samsung drivers to my PC and then used Odin (v3.10.7) to load twrp-3.0.2-0-coreprimelte.img.tar (from dl.twrp.me/coreprimelte/) on AP and clicked Start. Failed.
My log from Odin is below, and the phone showed "Custom Binary Recovery blocked by FRP Lock".
<ID:0/003> Added!!
<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> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> recovery.img
<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)
Now I'm trying to use Kies3 firmware upgrade to see if it'll get the phone out of endless boot mode but it required a serial number and I don't have one. Don't have the box, and it's not on the sticker.
Check it out -- am I nuts or is this void of SN?
Meanwhile I'm downloading the firmware to flash with Odin but it's going to be a while before the download finishes... so in the mean time I'm trying whatever I can.
I tried looking up how to bypass the FRP lock but couldn't find directions that involved not being able to boot the actual phone.
Any ideas?
Click to expand...
Click to collapse
I believe the S/N on your sticker is the FCC ID.

Victory is mine!
xCrakerZ said:
I believe the S/N on your sticker is the FCC ID.
Click to expand...
Click to collapse
I tried that to no avail - luckily I just successfully reinstalled the firmware with Odin3 v3.10.7!
It stayed stuck on the boot screen for a few minutes and then suddenly it kicked into the welcome screen. VICTORY!
The phone was wiped of course, but at least it's a phone again. Thanks everyone - I know I just posted in this thread today but I read through the whole thing and it helped me figure this out. :good:

heymishka said:
I tried that to no avail - luckily I just successfully reinstalled the firmware with Odin3 v3.10.7!
It stayed stuck on the boot screen for a few minutes and then suddenly it kicked into the welcome screen. VICTORY!
The phone was wiped of course, but at least it's a phone again. Thanks everyone - I know I just posted in this thread today but I read through the whole thing and it helped me figure this out. :good:
Click to expand...
Click to collapse
Glad you make it

TacoTank said:
(NOTE: This is NOT my phone, but I do have it until it's fixed)
I tried rooting this MetroPCS Galaxy Core Prime via Kingroot, something went wrong. After I rooted it, I gave it back to its owner, and he came back from Spring Break with a Samsung paperweight. Recovery doesn't work, neither does booting it up regularly. It gives me the " Custom Binary blocked by FAP. " and in red text, it says " SECURE FAIL: KERNEL " So, I was like "Hey, no biggie, let's just flash the stock firmware." Well, there's an issue there. It boots into Download mode, but it doesn't show up on Odin. I REALLY need help, as this isn't my phone. Thanks guys.
Click to expand...
Click to collapse
Ok you'll need to go to sammobile.com, go to firmware and search for Galaxy core prime (the model) and download the firmware.
Then download the latest Odin and open the .exe and select PDA or AP and select the firmware you just downloaded.
Now boot your phone to Download mode b yholding the home, power and volume down button at the same time and when a warning dialog
appears press the volume up button and now connect the phone to your PC and click on start in Odin.
After the flasihng process ends, you will have your Galaxy Core Prime working perfectly.
If you want to root your phone again then I recommend checking the OEM Unlock in the developer option in android settings, this will disable FRP/FAP Lock.

Hey can anyone help me i to am unable to find a stock rom to fix my phone. It's a Samsung galaxy core prime sm-s820l. Won't boot past Samsung galaxy core prime screen, kies or Odin aren't working for me.

Flavinkelly said:
Hey can anyone help me i to am unable to find a stock rom to fix my phone. It's a Samsung galaxy core prime sm-s820l. Won't boot past Samsung galaxy core prime screen, kies or Odin aren't working for me.
Click to expand...
Click to collapse
Got to sammobile.com and download your rom. Switch your phone to download mode, connect your phone with your PC (if your PC cannot detect your phone Odin then uninstall and reinstall Samsung drivers on your PC) and select AP or PDA in Odin and select your ROM (the zip file) and wait until it's finished flashing the ROM.

FardeenTGO said:
Got to sammobile.com and download your rom. Switch your phone to download mode, connect your phone with your PC (if your PC cannot detect your phone Odin then uninstall and reinstall Samsung drivers on your PC) and select AP or PDA in Odin and select your ROM (the zip file) and wait until it's finished flashing the ROM.
Click to expand...
Click to collapse
Not to be unkind, but I don't think there is any firmware for the sm-s820l. If you find any, could you post a link?

heymishka said:
Hey guys, I found this thread and I'm hoping I can figure out this massively frustrating issue with the Galaxy Core Prime as well.
It was stuck in endless boot so I downloaded the Samsung drivers to my PC and then used Odin (v3.10.7) to load twrp-3.0.2-0-coreprimelte.img.tar (from dl.twrp.me/coreprimelte/) on AP and clicked Start. Failed.
My log from Odin is below, and the phone showed "Custom Binary Recovery blocked by FRP Lock".
<ID:0/003> Added!!
<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> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> recovery.img
<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)
Now I'm trying to use Kies3 firmware upgrade to see if it'll get the phone out of endless boot mode but it required a serial number and I don't have one. Don't have the box, and it's not on the sticker.
Check it out -- am I nuts or is this void of SN?
Meanwhile I'm downloading the firmware to flash with Odin but it's going to be a while before the download finishes... so in the mean time I'm trying whatever I can.
I tried looking up how to bypass the FRP lock but couldn't find directions that involved not being able to boot the actual phone.
Any ideas?
Click to expand...
Click to collapse
Download the latest Odin and Samsung driver and install it.
Download the stock ROM of your phone in sammobile.com
Go to the download mode by long pressing on volume down+power+home button.
Connect your phone to your pc with a usb cable.
Launch Odin and choose PDA or AP.
Select the stock rom of your phone and press on download in Odin.
It may take some minutes and when the process is complete, reboot your phone if it stays on the download mode.
Hit Thank if it helped
---------- Post added at 03:57 PM ---------- Previous post was at 03:47 PM ----------
hydroman202 said:
Not to be unkind, but I don't think there is any firmware for the sm-s820l. If you find any, could you post a link?
Click to expand...
Click to collapse
Here ; https://drive.google.com/open?id=0B-KfJE4M0My6Z1RsNUpXaFA3bmM
Its a deodexed rom.
Hit Thank if helped.

TacoTank said:
I ended up fixing it after all! Thanks for the help though. (Can a mod take this thread down?)
Click to expand...
Click to collapse
Can you tell me how you fixed it because my Galaxy core prime has been soft brick for a year now and I need help

Mrkingg said:
Can you tell me how you fixed it because my Galaxy core prime has been soft brick for a year now and I need help
Click to expand...
Click to collapse
Flash stock rom through odin on a pc/laptop.

FardeenTGO said:
Flash stock rom through odin on a pc/laptop.
Click to expand...
Click to collapse
I've done everything it still not working the reason I brick my is because I used kingroot and forgot to activate OEM unlock now not even my PC recognizing my phone I really need help

Related

please,want to return to my original boatloader

i nserted a file named sgt-boatloader-patch-v1.00 apk to my galaxy tab 7 p1000 to break my phone protection but after installation, my phone screen became a logtudinal coloured line before start and cannt go to recovery mood or reboot, please help me to remove this boatloader and return my phone to work. as also the pc and kies cannt recognize my tab p1000
It you cannot get into download mode, then congratulations. You have got yourself a brick, and your Galaxy Tab is "GAME OVER".
IcedCube said:
It you cannot get into download mode, then congratulations. You have got yourself a brick, and your Galaxy Tab is "GAME OVER".
Click to expand...
Click to collapse
This pretty much. If you can't get into download mode by powering off the tab and trying to turn it on via Vol Down + Power, then it may indeed be bricked.
I believe there was 1 person who flashed the wrong kernel or something, and couldn't see anything on-screen, but was able to get into download mode (I think he had the wrong graphics driver), but idk.
If your tab is bricked though, you'll either have to checkout the "Unbrickable" mod, find someone else to perform the unbrickable mod for you, or talk to Samsung about it.
The main thing is to get into Download mode. Normally you see the Android-at-work screen in this mode, but there are other screens, and these will work as well. The Phone ! PC screen, though worrying, is a Download mode as well. Even a black screen showing nothing may be a Download screen. See for instance this helpful topic by k0sh.
That said, flashing a bootloader, or messing (patching) with one is one of the very few ways to hard brick your Tab...
If you can get the Tab recognised by Odin or Heimdall (remember to install their drivers first) in Download mode, you're good to go (flash that is). Heimdall has a Close PC screen function that's very handy, and may get you to boot a bricked Tab. Remember to charge it 4 hours or so before trying anything, even if it doesn't seem to show or do anything.
Reflashing to a ROM known to be able to boot is good if you can go to Download mode. Overcome can do this. Follow the flash to stock guide in this thread. I don't know if this will work for all Tabs, but it certainly works for a European GSM tab.
i also have the problem with "logtudinal coloured line" after patch the bootloader. but i can enter the download mode (power off,volume down+home+power on) and can see the 'android on work' logo.
i surf back the bootloader thread and found this.
"DO NOT USE THIS ON THE GINGERBREAD RELEASES ! THE SAMSUNG GINGERBREAD RELEASES DO HAVE SIGNED BOOTLOADERS, BUT THEY ARE NOT LOCKED. In other words, you can still flash custom kernels and such, and the bootloader patch will only break things, not fix them."
well, my gtab p1000 is 2.3.3 (dxjpi).
and the question, how to get back the original bootloader? i've read that bootloader come with rom. but doesn't really understand it (android newbie).
Flash the whole stock official rom
Sent from my GT-P1000 using XDA
priyana said:
Flash the whole stock official rom
Sent from my GT-P1000 using XDA
Click to expand...
Click to collapse
here what i did.
THIS IS MY EXPERIENCE WITH MY GALAXY TAB P1000 AND TRY IT (IF YOU WANT TO) WITH YOUR OWN RISK!
- downloaded "XXJQ1_2.3.3_P1000.zip" that included with ODIN3 1.3 and "gt-p1000_mr.pit".
- get gtab to dowload mode (android at work logo), run ODIN3 1.3 and COM detected.
- select pit and pda file (P1000XXJQ1_P1000XXJQ1_P1000XXJPZ_HOME.tar). using default settings (no re-partition), click start.
- odin result:-
<ID:0/029> Added!!
<ID:0/029> Odin v.3 engine (ID:29)..
<ID:0/029> File analysis..
<ID:0/029> SetupConnection..
<ID:0/029> Initialzation..
<ID:0/029> Get PIT for mapping..
<ID:0/029> Firmware update start..
<ID:0/029> boot.bin
<ID:0/029> Sbl.bin
<ID:0/029> param.lfs
<ID:0/029> gt-p1000_mr.pit
<ID:0/029>
<ID:0/029> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
- gtab reboot, now got "phone and computer logo link with exclamation mark in between. bricked my galaxy tab).
- then i look at ODIN3 1.3, device still detected. close ODIN3 1.3.
- downloaded "CF-Root-TAB7_XX_OXA_JQ1-v3.3-CWM3RFS.zip" and "Odin3 v1.7.zip".
- run ODIN3 1.7, device detected. select pda file "CF-Root-TAB7_XX_OXA_JQ1-v3.3-CWM3RFS.tar" (and i make sure the re-partition is NOT SELECTED).
- start, and here is the result:
<ID:0/029> Added!!
<ID:0/029> Removed!!
<ID:0/029> Added!!
<ID:0/029> Removed!!
<ID:0/029> Added!!
<ID:0/029> Odin v.3 engine (ID:29)..
<ID:0/029> File analysis..
<ID:0/029> SetupConnection..
<ID:0/029> Initialzation..
<ID:0/029> Get PIT for mapping..
<ID:0/029> Firmware update start..
<ID:0/029> zImage
<ID:0/029> Removed!!
<ID:0/029> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
- my galaxy tab now reboot, and now i dont see the "horizontal coloured line" @ boot screen @ animation messy one.
- using bootloader patch, checked the status. result:-
signed: pbl, sbl_backup
not signed: sbl, kernel
device condition nothing unusual, normal. i think i have repaired the bootloader back to original stock jq1.
Flashing a "full ROM" will amongst others flash the boot loader to the Tab. A full ROM is a ROM that includes all the parts necessary to create a bootable and working system on a possibly corrupted or otherwise non-working system. Your first attempt flashed the boot loader (boot.bin, sdl.bin), but failed on something else. It seems you repaired that by flashing a kernel. So yes, you have restored the boot loader.
ableeker said:
Flashing a "full ROM" will amongst others flash the boot loader to the Tab. A full ROM is a ROM that includes all the parts necessary to create a bootable and working system on a possibly corrupted or otherwise non-working system. Your first attempt flashed the boot loader (boot.bin, sdl.bin), but failed on something else. It seems you repaired that by flashing a kernel. So yes, you have restored the boot loader.
Click to expand...
Click to collapse
yes. at first i am so worried and curious to try repair the bootloader. after searching here in xda related to rom and bootloader,ive gained some confidence to do so. but,what is the "phone-triangle-pc" logo means?
It is just another "download" mode.
Sent from my GT-P1000 using XDA
You usually get this when something goes wrong during a flash, like when the flash doesn't even start, and you reboot the Tab. It seems that in such a case the Tab can't get to the normal download mode, and shows this image to let you know something's wrong. However, Odin in this mode is still able to connect to the Tab, so luckily you can flash again. That's why it's called a soft brick, and not a hard brick, because it can be fixed by software.

Accidentally deleted my System folder SGH-M919

Hello, I accidentally deleted my systems folder. I was trying to overwrite one file but apparently it deleted my entire system folder, now I cannot use recovery. If I try to go into recovery mode i get "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again."
I tried downloading Kies and updating it through that but I then get the error "the device's version cannot be updated." I have updated KIES to the newest firmware and still get the error.
I have tried adb pushing but my device is unrecognized and does not fully connect to my computer (Kies will just be stuck at "Connecting...")
I have tried installing a stock rom back with odin (ran as administrator), but odin gives me the error:
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
So it seems I have tried pretty much everything so far with no avail, may someone please help me? I am really stressed out and confused at all these errors.
titaniums4 said:
Hello, I accidentally deleted my systems folder. I was trying to overwrite one file but apparently it deleted my entire system folder, now I cannot use recovery. If I try to go into recovery mode i get "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again."
I tried downloading Kies and updating it through that but I then get the error "the device's version cannot be updated." I have updated KIES to the newest firmware and still get the error.
I have tried adb pushing but my device is unrecognized and does not fully connect to my computer (Kies will just be stuck at "Connecting...")
I have tried installing a stock rom back with odin (ran as administrator), but odin gives me the error:
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
So it seems I have tried pretty much everything so far with no avail, may someone please help me? I am really stressed out and confused at all these errors.
Click to expand...
Click to collapse
I managed to fix this! WOW was this such a headache!
after a long time researching, I found out the 4.4.2 update has some sort of updated bootloader that will not let you install older firmware. So I downloaded the 4.4.2 stock rom from www sammobile com
After you download that, i ran it with odin 1.09 and it installed.
My phone went into some weird loop where the samsung logo would come out for 1 second then my phone would vibrate every 2 seconds and not turn on... great another wall...
After more research i found out it could have been a power button issue, luckily it wasnt this, someone had mentioned that if you go into download mode and hold down the power button until your phone reboots you can get out of this "glitch". So this got me out of the glitch and my s4 started up normally!
Right now I am back to stock, I hope this helps out anyone who encounters something similar!
titaniums4 said:
Hello, I accidentally deleted my systems folder. I was trying to overwrite one file but apparently it deleted my entire system folder, now I cannot use recovery. If I try to go into recovery mode i get "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again."
I tried downloading Kies and updating it through that but I then get the error "the device's version cannot be updated." I have updated KIES to the newest firmware and still get the error.
I have tried adb pushing but my device is unrecognized and does not fully connect to my computer (Kies will just be stuck at "Connecting...")
I have tried installing a stock rom back with odin (ran as administrator), but odin gives me the error:
Initialzation..
Get PIT for mapping..
Firmware update start..
sbl2.mbn
NAND Write Start!!
sbl3.mbn
rpm.mbn
aboot.mbn
FAIL! (Auth)
All threads completed. (succeed 0 / failed 1)
So it seems I have tried pretty much everything so far with no avail, may someone please help me? I am really stressed out and confused at all these errors.
Click to expand...
Click to collapse
I think u should download new firmware from sammobile (because sometimes some firmware corrupted) and try different pc for reflash stock...
Sent from my GT-I9500 using XDA Premium 4 mobile app
fleming.patel said:
I think u should download new firmware from sammobile (because sometimes some firmware corrupted) and try different pc for reflash stock...
Sent from my GT-I9500 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
thanks for the reply, however i already fixed this!
titaniums4 said:
I managed to fix this! WOW was this such a headache!
after a long time researching, I found out the 4.4.2 update has some sort of updated bootloader that will not let you install older firmware. So I downloaded the 4.4.2 stock rom from www sammobile com
After you download that, i ran it with odin 1.09 and it installed.
My phone went into some weird loop where the samsung logo would come out for 1 second then my phone would vibrate every 2 seconds and not turn on... great another wall...
After more research i found out it could have been a power button issue, luckily it wasn't this, someone had mentioned that if you go into download mode and hold down the power button until your phone reboots you can get out of this "glitch". So this got me out of the glitch and my s4 started up normally!
Right now I am back to stock, I hope this helps out anyone who encounters something similar!
Click to expand...
Click to collapse
Hey I am also in a similar difficulty. > http://forum.xda-developers.com/galaxy-s4/help/help-firmware-upgrade-encountered-issue-t2821045
Basically read this above, and tell me what you think I should do. One thing I forgot to add is that when I try to flash a Official Firmware via ODIN, my S4 doesn't really do anything then ODIN would say FAILED, and it would have no affect on my S4 because it just stays on the firmware upgrade encountered an issue part.

<ID:0/003> FAIL! (Auth) When trying to Flash Stock

Hi, when trying to flash my Verizon S7 back to stock (with the correct verizon files) I got this odin log
<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)
When trying to exit I got the "Software Update Failed" and when trying to flash again it's just a stuck bar on my screen. Not sure what to do and I'm kinda of new to this but I'd appreciate any help. Since then my phone has been stuck on the green screen since and whenever I press anything it just returns to the screen.
Any fast help would really be appreciated, it's been like this for hours and I'm not sure what to do ):
I'm gonna take a quick stab at this and say use the other CSC file, whichever one you haven't tried (either csc_vzw or home_csc_vzw).
Do not use the HOME_CSC file. Use the CSC and be sure that all of the images are in the correct spots in ODIN.
Was the device rooted? If so, you may not have gotten rid of all the root files, so it detects modified and won't flash.
Which firmware are you trying to flash? Were you on Nougat? We need more information.
Are you going from U firmware? I had to check repartition when I did.
ironbesterer said:
Do not use the HOME_CSC file. Use the CSC and be sure that all of the images are in the correct spots in ODIN.
Was the device rooted? If so, you may not have gotten rid of all the root files, so it detects modified and won't flash.
Which firmware are you trying to flash? Were you on Nougat? We need more information.
Click to expand...
Click to collapse
I was rooted through the steps found here
https://forum.xda-developers.com/ve...-to-notes-root-install-xposed-unroot-t3411039
I tried to flash back to stock and got the error after that. My phone's battery died and it's just sitting on my desk now );
Sayunoi said:
I was rooted through the steps found here
https://forum.xda-developers.com/ve...-to-notes-root-install-xposed-unroot-t3411039
I tried to flash back to stock and got the error after that. My phone's battery died and it's just sitting on my desk now );
Click to expand...
Click to collapse
Same thing here. I can only get into stock recovery with the error "dm-verity verification failed" (most options are disabled), and into bootloader, but unable to flash stock ROM; it just fails every time.
I'd be glad for a solution!
Don't forget the bootloader file too. I believe the root thread doesn't include the BL file in the instructions, but the error disappeared when I included the Bootloader.
azoller1 said:
Don't forget the bootloader file too. I believe the root thread doesn't include the BL file in the instructions, but the error disappeared when I included the Bootloader.
Click to expand...
Click to collapse
Mine still has the error when I included the bootloader file.
Another thing I should mention is in the top right it says "SW REV CHECK FAIL : [system] Fused 3 > Binary 1
I tried changing the wire, using the boot loader file, and changing usb ports. Lost here );
Sayunoi said:
When trying to exit I got the "Software Update Failed"
Click to expand...
Click to collapse
I tried going back to stock as well and am stuck on this screen. It says to use the Verizon Software Repair Assistant on a computer to repair it. I've only ever rooted a kindle fire so I don't know too much. Any way I can just get my phone back to normal?
JaffXsMan said:
I tried going back to stock as well and am stuck on this screen. It says to use the Verizon Software Repair Assistant on a computer to repair it. I've only ever rooted a kindle fire so I don't know too much. Any way I can just get my phone back to normal?
Click to expand...
Click to collapse
Really wondering the same thing =/
I think maybe I'm trying to flash back to an older version. Does anyone have a link for the latest Galaxy S7 stock rom?
Sayunoi said:
I think maybe I'm trying to flash back to an older version. Does anyone have a link for the latest Galaxy S7 stock rom?
Click to expand...
Click to collapse
You cannot flash a stock rom with an older bootloader than what ever you currently have on your phone. You can only Odin flash a stock rom with same or newer bootloader. So usually you cannot go to an older rom only newer.
Can I try flashing stock rom while in the Software update failed screen, or do I need to be in download mode?
Sayunoi said:
I tried changing the wire, using the boot loader file, and changing usb ports. Lost here );
Click to expand...
Click to collapse
Try re-downloading the firmware. Are you sure you had the right firmware downloaded? The error seems to be caused by some kind of mismatch between the software trying to be flashed and what software you currently have on your phone
Also, make sure you are using the non princecosmy Odin 3.12
When ever I try to flash stock onto my phone, i'm getting the error "SW REV CHECK FAILED : [aboot] fused 4 > binary 2" I don't know what any of this means. Could someone explain this? Also when trying to flash stock i'm in "System Update Failed" screen and a little bar appears at the bottom. Does this mean it is still able to download the stock rom at all? One last thing, if I were to try and flash G935U instead of G935V could that help? Any help would be nice
go to samfirm and download the latest firmware for the S7 that you have, try flashing with that. I had to put everything in it's place in odin and select reformat to unroot my phone. I ran into the dm_verification failed and the only option was to download the latest firmware and flash that.
JerseyDubbin said:
go to samfirm and download the latest firmware for the S7 that you have, try flashing with that. I had to put everything in it's place in odin and select reformat to unroot my phone.
Click to expand...
Click to collapse
Do you mean sammobile? https://www.sammobile.com/firmwares/database/SM-G935F/
That or http://samfirm.net/I believe.

Galaxy S8 Odin problem

Hello
It seems to me that my Galaxy S8 is brick and I would like to reset it with odin, I have the firmware but when i flash this is what i get
<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>
<ID:0/003> FAIL! (DeviceInfo)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> FAIL! (DeviceInfo) : Seems uncommon to me. :-/
And my Galaxy S8 remains blocked on startup menu, could you help me please ?
Extract from csc file pit. Once that is done place pit in pit option in Odin. Place AQG7 bl or any bl and flash. When It fails enter download mode and as it does that spam the start button. Like your button mashing a game. It'll flash and be successful I JUST recovered from this 5 mins ago
this.guy.lol said:
Extract from csc file pit. Once that is done place pit in pit option in Odin. Place AQG7 bl or any bl and flash. When It fails enter download mode and as it does that spam the start button. Like your button mashing a game. It'll flash and be successful I JUST recovered from this 5 mins ago
Click to expand...
Click to collapse
Hello, thanks for your help, I will try to follow your step, here are the files I have :
AP_G950FXXU1AQDD_CL11168760_QB13202424_REV00_user_low_ship_meta.tar.md5
BL_G950FXXU1AQDD_CL11168760_QB13202424_REV00_user_low_ship.tar.md5
CP_G950FXXU1AQDD_CP6222485_CL11168760_QB13202424_REV00_user_low_ship.tar.md5
CSC_OXM_G950FOXM1AQDD_CL11168760_QB13202424_REV00_user_low_ship.tar.md5
HOME_CSC_OXM_G950FOXM1AQDD_CL11168760_QB13202424_REV00_user_low_ship.tar.md5
And I have this : DREAMLTE_EUR_OPEN.pit (I'm french)
Amsro said:
Hello, thanks for your help, I will try to follow your step, here are the files I have :
AP_G950FXXU1AQDD_CL11168760_QB13202424_REV00_user_low_ship_meta.tar.md5
BL_G950FXXU1AQDD_CL11168760_QB13202424_REV00_user_low_ship.tar.md5
CP_G950FXXU1AQDD_CP6222485_CL11168760_QB13202424_REV00_user_low_ship.tar.md5
CSC_OXM_G950FOXM1AQDD_CL11168760_QB13202424_REV00_user_low_ship.tar.md5
HOME_CSC_OXM_G950FOXM1AQDD_CL11168760_QB13202424_REV00_user_low_ship.tar.md5
And I have this : DREAMLTE_EUR_OPEN.pit (I'm french)
Click to expand...
Click to collapse
No problem. Flash pit and BL at same time. Once it fails quickly boot it back into download mode as it's failing. Once it said press up to enter download mode, as you press up spam the start button in Odin. After that install twrp. Then wipe as you would normally like format data etc. Reinstall stock and you should be golden after that
this.guy.lol said:
No problem. Flash pit and BL at same time. Once it fails quickly boot it back into download mode as it's failing. Once it said press up to enter download mode, as you press up spam the start button in Odin. After that install twrp. Then wipe as you would normally like format data etc. Reinstall stock and you should be golden after that
Click to expand...
Click to collapse
Okay thanks you very much
It's not the problem, problem is because of Bootloader AQG5, look that:
Galaxy S8/S8+ Odin FAIL, BOOTLOOP, BOOTLOADER FIX! | QG5 Nightmare
this.guy.lol said:
Extract from csc file pit. Once that is done place pit in pit option in Odin. Place AQG7 bl or any bl and flash. When It fails enter download mode and as it does that spam the start button. Like your button mashing a game. It'll flash and be successful I JUST recovered from this 5 mins ago
Click to expand...
Click to collapse
dude. i dont care how late i am but you just saved me from completely breaking down and crying after what seemed to be bricking my 2 week old device, i cant thank you enough. THANK YOU SO MUCH
YaoSta said:
dude. i dont care how late i am but you just saved me from completely breaking down and crying after what seemed to be bricking my 2 week old device, i cant thank you enough. THANK YOU SO MUCH
Click to expand...
Click to collapse
your very welcome. i was in the same boat for 25 mins till i did some research...it was bad. glad to help.
Amsro said:
Hello
It seems to me that my Galaxy S8 is brick and I would like to reset it with odin, I have the firmware but when i flash this is what i get
<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>
<ID:0/003> FAIL! (DeviceInfo)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> FAIL! (DeviceInfo) : Seems uncommon to me. :-/
And my Galaxy S8 remains blocked on startup menu, could you help me please ?
Click to expand...
Click to collapse
Hey,
Please listen to me ! It's work.
When the device reboot after this error : Fail Device Info. Repress immediately Volume- / Bixby / Power to enter a second time in download mode. Normally you enter directly in the mode, and you don't have the Splash Screen ( Samsung Power BY Android )
Now you can flash with Odin, and tis problem diseapear !
The more important is the rapidity ! when you click start in Odin, the phone reboot and you must immediately re-enter in download mode.
Enjoy
brilliant mate, sorted a ~bricked phone (when it won't power off and sits at the first screen until the battery dies, all you can do is hold the buttons until it forces a reboot and then you can only get to the Odin downloader screen or it sits on the first screen, all flash attempts fail until you do the trick, then it's sorted )
Soft-Tech643 said:
Hey,
Please listen to me ! It's work.
When the device reboot after this error : Fail Device Info. Repress immediately Volume- / Bixby / Power to enter a second time in download mode. Normally you enter directly in the mode, and you don't have the Splash Screen ( Samsung Power BY Android )
Now you can flash with Odin, and tis problem diseapear !
The more important is the rapidity ! when you click start in Odin, the phone reboot and you must immediately re-enter in download mode.
Enjoy
Click to expand...
Click to collapse
I agree with this claim, I was almost frustrated on how to cure my S8+ , you only have to be fast when pressing the combination buttons for download mode. I attached a screen shot showing the "FAIL! (DeviceInfo)" and followed by the logs which represents a continuous flow of good flashing of firmware. Credits to the discoverer of this method :good::good::good::good::laugh::laugh::laugh:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Soft-Tech643 said:
Hey,
Please listen to me ! It's work.
When the device reboot after this error : Fail Device Info. Repress immediately Volume- / Bixby / Power to enter a second time in download mode. Normally you enter directly in the mode, and you don't have the Splash Screen ( Samsung Power BY Android )
Now you can flash with Odin, and tis problem diseapear !
The more important is the rapidity ! when you click start in Odin, the phone reboot and you must immediately re-enter in download mode.
Enjoy
Click to expand...
Click to collapse
Sorry for necroposting, but i need to say THANK YOU to Soft-Tech643, After 10 different firmware, download, zip, unzip, tar, md5 file, download mode, and FAIL with this suggest i finally flashed my s8 with an official update. Thanks mate, it work!!!
Thanks a lot it's work for me. you save my life
Try Odin 3.13.1, it fixed this problem

My rooted device has Custom binary blocked by FRP with disabled USB debugging

I know, firmware of my device, flash with Odin3, but that method doesn't work, because the USB debugging and the whole developer settings are disabled.
So, I can't turn on my Samsung Galaxy j5 2016, because if I try, it say ,,Custom binary blocked by FRP, secure fail: kernel". I downloaded a lot of firmware for my device (SM-J510FN, Hungary) and try to flash with Odin3, but it not work. I write the full error message of Odin3 bellow.
I tried to instal Samsung USB driver, but nothing has changed. I need to do more than install the USB driver? Maybe I download a wrong version?
I tried to use Samsung smart switch, but the Windows application do not detect my device, I think because my phone is turned off. Or how it works?
Odin3 say this if I try to flash the Firmware:
...
<ID:0/004> Odin engine v(ID:3.1301)..
<ID:0/004> File analysis..
<ID:0/004> skip file list for home binary
<ID:0/004> param.bin
<ID:0/004> userdata.img
<ID:0/004> Home Binary Download
<ID:0/004> Total Binary size: 2822 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> NAND Write 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)
Gilgamesh-KoH said:
I know, firmware of my device, flash with Odin3, but that method doesn't work, because the USB debugging and the whole developer settings are disabled.
So, I can't turn on my Samsung Galaxy j5 2016, because if I try, it say ,,Custom binary blocked by FRP, secure fail: kernel". I downloaded a lot of firmware for my device (SM-J510FN, Hungary) and try to flash with Odin3, but it not work. I write the full error message of Odin3 bellow.
I tried to instal Samsung USB driver, but nothing has changed. I need to do more than install the USB driver? Maybe I download a wrong version?
I tried to use Samsung smart switch, but the Windows application do not detect my device, I think because my phone is turned off. Or how it works?
Odin3 say this if I try to flash the Firmware:
...
<ID:0/004> Odin engine v(ID:3.1301)..
<ID:0/004> File analysis..
<ID:0/004> skip file list for home binary
<ID:0/004> param.bin
<ID:0/004> userdata.img
<ID:0/004> Home Binary Download
<ID:0/004> Total Binary size: 2822 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> NAND Write 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)
Click to expand...
Click to collapse
Well, There is only one explanation! Try booting in recovery, hoping stock one and aplly update.zip with sd card help, if not well, i recomend trying lower vesrion of Odin3 bc in my case lastest gave me pain, so i use lower version!
RootingPro-18 said:
Well, There is only one explanation! Try booting in recovery, hoping stock one and aplly update.zip with sd card help, if not well, i recomend trying lower vesrion of Odin3 bc in my case lastest gave me pain, so i use lower version!
Click to expand...
Click to collapse
Can't boot to recovery mode, if I try it say the same thing. And what version of Odin3 is enough low?
I'm getting the same problem, my GF turned off the USB Debuggin and now I can't fix it anymore... (Using custom rom Epsilon_Orionis_ROM_V1_By_LUCiONE )
I searched a lot, but nothing works until now.
Did you try to put the .PIT file and enable the Re-Partition? Unfortunately I can't find the .PIT to G570M
RaR System said:
I'm getting the same problem, my GF turned off the USB Debuggin and now I can't fix it anymore... (Using custom rom Epsilon_Orionis_ROM_V1_By_LUCiONE )
I searched a lot, but nothing works until now.
Did you try to put the .PIT file and enable the Re-Partition? Unfortunately I can't find the .PIT to G570M
Click to expand...
Click to collapse
I didn't know so far this PIT and Re-Partition solution. Can you tell me more about that or where can I search for it?
Gilgamesh-KoH said:
Can't boot to recovery mode, if I try it say the same thing. And what version of Odin3 is enough low?
Click to expand...
Click to collapse
I think something.12.something(i don't remember) but why it doesn't allow flashing stock FW anyway.
---------- Post added at 04:50 PM ---------- Previous post was at 04:47 PM ----------
RaR System said:
I'm getting the same problem, my GF turned off the USB Debuggin and now I can't fix it anymore... (Using custom rom Epsilon_Orionis_ROM_V1_By_LUCiONE )
I searched a lot, but nothing works until now.
Did you try to put the .PIT file and enable the Re-Partition? Unfortunately I can't find the .PIT to G570M
Click to expand...
Click to collapse
You don't need PIT file, it's for repartiton! Download SamFirm ( https://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647/amp/ )and download FW from there and try!
RootingPro-18 said:
I think something.12.something(i don't remember) but why it doesn't allow flashing stock FW anyway.
---------- Post added at 04:50 PM ---------- Previous post was at 04:47 PM ----------
You don't need PIT file, it's for repartiton! Download SamFirm ( https://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647/amp/ )and download FW from there and try!
Click to expand...
Click to collapse
I will try, but can I really flash that firmware with Odin, even if when the USB debugging are disabled? This USB debugging thing is the source of all trouble.
Someone can recommend me some forum or something, where I can write this question?
Gilgamesh-KoH said:
I will try, but can I really flash that firmware with Odin, even if when the USB debugging are disabled? This USB debugging thing is the source of all trouble.
Someone can recommend me some forum or something, where I can write this question?
Click to expand...
Click to collapse
USB debugging is for ADB, not for Download mode, so no it can't interfere with Odin3
RootingPro-18 said:
I think something.12.something(i don't remember) but why it doesn't allow flashing stock FW anyway.
---------- Post added at 04:50 PM ---------- Previous post was at 04:47 PM ----------
You don't need PIT file, it's for repartiton! Download SamFirm ( https://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647/amp/ )and download FW from there and try!
Click to expand...
Click to collapse
Yes, I tried with SamFirm, I did the download of Firmware (everything ok until there). After Run Odin (3.13.1 and others version) with Admin privileges, but stops at step "Setup Connection...".
I have the USB Drivers, tried with anothers USB Ports (2.0, 3.0) and I already used Odin before and never happened it.
So now, I have no ideia what can I do. I am desperate...
RaR System said:
Yes, I tried with SamFirm, I did the download of Firmware (everything ok until there). After Run Odin (3.13.1 and others version) with Admin privileges, but stops at step "Setup Connection...".
I have the USB Drivers, tried with anothers USB Ports (2.0, 3.0) and I already used Odin before and never happened it.
So now, I have no ideia what can I do. I am desperate...
Click to expand...
Click to collapse
Unistall all USB hub drivers and samsung drivers, and try again!
RootingPro-18 said:
Unistall all USB hub drivers and samsung drivers, and try again!
Click to expand...
Click to collapse
Tried it too. Did the download of last version of Samsung USB Drivers... Is there any other option?
Edit: After reinstall Samsung USB Driver it works. It's reinstalling the Stock rom (BL, AP, CP and CSC ). After it end I come back to edit my comment.
Edit 2: Omg, thank you so much. Everything is working again.
I did the download of the last version of Samsung USB Driver right here
Install it, restart computer, run Odin 3.13.1 as Admin, use the SamFirm too, so you will have the last version of Stock Firmware, put the BL, AP, CP, CSC (Put HOME_CSC if you don't wanna lose userdata )and Start.
After 10minuts my J5 Prime finished the Loading and now I can configure the phone again.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
RaR System said:
Tried it too. Did the download of last version of Samsung USB Drivers... Is there any other option?
Edit: After reinstall Samsung USB Driver it works. It's reinstalling the Stock rom (BL, AP, CP and CSC ). After it end I come back to edit my comment.
Edit 2: Omg, thank you so much. Everything is working again.
I did the download of the last version of Samsung USB Driver right here
Install it, restart computer, run Odin 3.13.1 as Admin, use the SamFirm too, so you will have the last version of Stock Firmware, put the BL, AP, CP, CSC (Put HOME_CSC if you don't wanna lose userdata )and Start.
After 10minuts my J5 Prime finished the Loading and now I can configure the phone again.
Click to expand...
Click to collapse
Thats good to hear!
Hello. In advance I'm sorry about my english..
My Samsung J5 SM-J500F as stopped on FRP screen. I have already tried every methods what I found on Internet.
I flashed 2 times with odin, the 1st one only AL file and other with all files. When I try to flash TWRP via odin the system gives me FRP block message.
I can't even use RealTerm solution because just have 2 green lights and commands fail always.
EDIT: SOLVED USING THIS METHOD
https://www.youtube.com/watch?v=hDtYjtnysT0

Categories

Resources