Database Users

[RECOVERY][21.Feb.12] ClockworkMod Recovery v5.5.0.4

Hey Everyone! So long story short, I ended up picking up a 8.9 tab and now we have a 100% confirmed working ClockworkMod Recovery!
So, quick and dirty instructions for users WITHOUT any form of CWM recovery on their device:
1) Download the attached ClockworkMod_Recovery_v5.5.0.4.tar
2) Reboot the tab into download mode
3) Fire up Odin 1.85 and put the ClockworkMod_Recovery_v5.5.0.4.tar in the PDA field.
4) Flash!
5) Reboot into ClockworkMod Recovery
Quick and dirty instructions for users WITH some form of CWM recovery on their device:
1) Download the attached ClockworkMod_Recovery_v5.5.0.4.zip to your device
2) Reboot the tab into recovery
3) Install the zip
5) Reboot
If, for any reason, you want to return to the stock recovery, simply download the P73xx_Stock_Recovery.tar and follow the instructions above (with odin)!
DISCLAIMER: THIS WILL NOT WORK WITH LTE TABS!

I kinda "bricked" my tab yesterday trying to create a recovery.
Now it just continually boots to the splash screen then restarts.
I can not get into recovery.
I can get into download.
I tried the ClockworkMod Recovery v5.0.2.6 but odin just hangs after setup connection.
Trying to download the stock recovery:
<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>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Any ideas?
Thanks,
-dana

Thankfully Samsung devices are notoriously hard to brick
So is the tab still booting into the OS? Or are you ONLY able to get to download mode?
Also, what did you do to try and create a recovery and what did you flash? If I can understand what has been done I can help you get up and running again
As for Odin hanging at "Setup Connection" when you tried to flash my recovery, it is likely just coincidence more than anything. Odin isn't the most dependable application...well, it is and it isn't...but getting stuck at Setup Connection is a common issue.
First tell me what you did yesterday so we can figure out how to proceed. Then we'll go from there!

I kinda want to volunteer as I am familiar with ODIN coming from a Vibrant but what's stopping me is 3 questions with all due respect. What's the related thread you were talking about at the OP? Are you sure that is the right 8.9 Stock Recovery? How did you find it as there is (at least) no American ODIN image as of today (checked Samfirmware as of this post)?

nirogu325 said:
I kinda want to volunteer as I am familiar with ODIN coming from a Vibrant but what's stopping me is 3 questions with all due respect. What's the related thread you were talking about at the OP? Are you sure that is the right 8.9 Stock Recovery? How did you find it as there is (at least) no American ODIN image as of today (checked Samfirmware as of this post)?
Click to expand...
Click to collapse
Excellent -
This is the thread I was talking about in 10.1 section:
http://forum.xda-developers.com/showthread.php?t=1307242
The recovery is standard, regardless of region. In fact, with the exception of precompiled binary modules, the recovery is even identical to that of the 10.1 tab
What I have done here is repacked the recovery image with a vanilla build of clockworkmod. This should work on both the P7300 and the P7310.
Give it a shot and let me know how it goes!

Neither got flashed via ODIN, but I too tried to install CWM yesterday via the market app so my recovery is messed up to start with.
After trying to flash the two the tab wouldn't boot and I got an error about a failed update.
Flashed the bootloader file below with ODIN to get it to boot.
Code:
ID:0/010> Added!!
<ID:0/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> recovery.img
<ID:0/010> NAND Write Start!!
<ID:0/010>
<ID:0/010> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Hmm ok...
So yesterday you tried the market CWM, which caused the tab not to boot at all? Then, you had to flash the bootloader to make it boot again?
I'm assuming you had a booting tab prior to trying to flash these files, but still had the borked recovery yes?

That is correct, but the recovery was fine when i got the device, I used it to root.
I know I should do a full flash but I don't want to lose all my stuff.
Also flahing the bootloader somehow removed the cwm ?script? That was forcing the tab to try and boot into the borked recovery on each boot.

Damn that app does a number on the poor tab...unfortunately the best course of action is really to completely restock the thing - flash an entire rom through Odin with a repartition.
Since you are able to boot, you can back up all your data with Titanium backup, then move the data off your internal storage and onto your computer in case it gets wiped by the Odin flash.
Now i really wish I had an 8.9 because I'm curious if someone who hasn't got the messed up recovery tries to flash my file if it will go through or fail like yours and the Geologist.
Any takers?

alterbridge86 said:
Now i really wish I had an 8.9 because I'm curious if someone who hasn't got the messed up recovery tries to flash my file if it will go through or fail like yours and the Geologist.
Any takers?
Click to expand...
Click to collapse
That'd be me. Once I backup my apps, I will (give me some minutes and I will post the result as an EDIT post). If it fails, worst case scenario would be flashing the Asian ODIN image since it is the only one available. That one displays everything in Chinese but I can change the language. Sidenote: Damn I wonder what is taking so long to bring an American ODIN image of the 7310 live???

nirogu325 said:
That'd be me. Once I backup my apps, I will (give me some minutes and I will post the result as an EDIT post). If it fails, worst case scenario would be flashing the Asian ODIN image since it is the only one available. That one displays everything in Chinese but I can change the language. Sidenote: Damn I wonder what is taking so long to bring an American ODIN image of the 7310 live???
Click to expand...
Click to collapse
Excellent! Let me know how it goes!

alterbridge86 said:
Excellent! Let me know how it goes!
Click to expand...
Click to collapse
It does not flash. This is what ODIN shows after following instructions:
<ID:0/010> Added!!
<ID:0/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> recovery.img
<ID:0/010> NAND Write Start!!
<ID:0/010>
<ID:0/010> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
EDIT: Oh well...it's been a while since I last saw a "device-!-PC" screen.
EDIT 2: The "device-!-PC" screen vanished after one or two restarts as if nothing ever happened.

That's really weird, because I can even flash the p73xx stock recovery on my 10.1 tab and it at least goes through...it won't boot into recovery, as expected, but it at least FLASHES...
Maybe next question - are you guys using Odin 1.85? Also, are you using the driver from Kies or did you install a standalone driver? Try installing this driver:
http://www.multiupload.com/ISBTL9TADO
And then flashing after. It also may be worthwhile to switch USB ports after installing the new driver. Don't mind the p7510 in the file name, it works with multiple devices.

alterbridge86 said:
That's really weird, because I can even flash the p73xx stock recovery on my 10.1 tab and it at least goes through...it won't boot into recovery, as expected, but it at least FLASHES...
Maybe next question - are you guys using Odin 1.85? Also, are you using the driver from Kies or did you install a standalone driver? Try installing this driver:
http://www.multiupload.com/ISBTL9TADO
And then flashing after. It also may be worthwhile to switch USB ports after installing the new driver. Don't mind the p7510 in the file name, it works with multiple devices.
Click to expand...
Click to collapse
Yes, ODIN 1.85. Will install that driver and see how it goes.
EDIT: Same result as pointed earlier, even after installing the quoted driver and changing USB ports.
EDIT 2: Wait a second. I think I might have figured it out. This does not work on an encrypted system, right? I think I'll unencrypt and then try doing this.
EDIT 3: Nope, unencrypted or not, it does not flash. Same result.
Sent from my GT-P7310

Well, I have good news and bad news...lol
I was strolling through best buy this evening after dinner and made an impulse purchase...i'm now the new owner of a Galaxy Tab 8.9
EDIT (10/22/11): We're back open! Confirmed working STOCK recovery is in first post...confirmed working CWM recovery coming momentarily
EDIT 2 (10/22/11): And we're official. ClockworkMod is 100% working Enjoy guys!
Now on to my next project...making this thing FASTER

Confirmed working CWM-Recovery . Doing a NANDROID backup as of this post.

Working great, thanks.
Sent from my GT-P7310 using Tapatalk

Works perfectly on my gtab P7300 and ki1 rom.
Thanks for your job !
Now, wait noTW rom !

work perfectly on my gtab P7300 asia
AWeSOME

Thanks, working perfectly on my gtab 7300 as well. So glad you are one of us now, looking forward for your overcome roms

[Q] [HELP] - Undoing MH8 update

So... Like a fool, having successfully rooted my phone a couple of days ago on the I9505XXUBMGA firmware, I saw this appear in Kies when I plugged my phone into Kies this morning. I thought (yeah you know where this is heading) "Oooh shiny new update, must download".
So although I had root I didn't think it would be a problem I'd just re-root afterwards. And hey if it didn't work I'd just downgrade the firmware and repeat the original process.
Trouble is I now have a message saying "SuperSU has been forced to stop for an unauthorized attempt to access system in your device. It may be solved by the policy update service. It may be safe to delete an application obtained from an unauthorized route. Check now?". I then have the option to not show for 30 days and then Cancel, Update or OK. Trouble is now when I attempt to revert the firmware back to an earlier version.
So now when I go into Download mode I see:
Code:
ODIN MODE
PRODUCT NAME: GT-I9505
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x1
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
If I try and Odin a new (stock) firmware on I get a write error from Odin and on the I9505 I get the following below the above text:
Code:
START [224, 1440]
SW REV. CHECK FAIL : fused: 2, Binary : 1
Odin shows:
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUBMGA_I9505OXXBMG3_I9505XXUBMGA_HOME.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> 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>
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
So, kind of stuck now. If the phone tries to restart I get the message: "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.". For a while I couldn't get the phone to boot, and Kies doesn't see the phone, but oddly re-partitioning via Odin using the PIT file means the phone will boot. From there I still get the SuperSU message but can switch it off and get into recovery mode, does that mean there is a chance I can re-flash things via adb / fastboot?
Yep I'm an idiot for trying and being the Guinea pig, but as I don't know how to proceed if anyone wants to help out and see if we can get it back and un "Knoxed" (which I think might be the issue) I'm more than happy to help.
Limitations currently are that I am running Windows XP 32-bit via Parallels virtual machine. The unbricking steps seem to indicate needing a 64-bit machine? I could probably do that but would have to get hold of and install 64-bit Windows 7 as a VM.
In terms of Android hacking I'm a noob, but can follow instructions, and am comfortable with a Unix/Linux command line if that's any help to anyone who wants to take pity on me...

OP, I'm in the same position as you, however I'm still stuck in download mode. Can you tell me EXACTLY what you did with Odin to manage to be able to boot the phone up again? I'd rather be able to use it un-rooted for now than to not use it at all!

Boolean = True said:
OP, I'm in the same position as you, however I'm still stuck in download mode. Can you tell me EXACTLY what you did with Odin to manage to be able to boot the phone up again? I'd rather be able to use it un-rooted for now than to not use it at all!
Click to expand...
Click to collapse
So, assuming you are stuck at the "there was a problem stage" you need to turn off the phone and get it into download mode (hold volume down, home + power - I guess you know this but just in case). I found this a bit fiddly I think because the phone is auto-rebooting, so try pressing power off and just holding the volume down and home buttons.
Then in Odin I used the PIT file listed in this thread. In the 'Re-partition' section and the boxes for Auto Reboot, Re-Partition, and F. Reset Time were all checked. I left all the other boxes empty (including the Files section). Click start and then after a while the phone reboots. It take a minute or two but if you see the Samsung logo it should boot.
Hope that helps... now to find a way around the MH1 firmware... oh and glad it wasn't just me that was daft enough to go and try it.

No, not just you mate. I had a hell of a time last night. Flash pre-rooted MGG firmware via odin, which bootlooped. I couldn't flash MGA firmware again.
So I flashed Stock MGG which booted but the security measures implemented have stopped me from changing my font using ifont.
I have now flashed MH8 over the top and it's working better than MGG, but still can't use some apps due to the new security measures.
I was able to flash Omega V10 from TWRP and it booted fine, but no wifi and I'm unable to flash LTE modem to correct it.
Looks like I'm stuck unrooted on MH8 for the time being.
There are some instructions on this thread on how to root this firmware, they're a bit lengthy tho.
http://forum.xda-developers.com/showthread.php?p=45283966
Sent from my GT-I9505 using Tapatalk 4

Bugger.
To add insult to injury it appears that WiFi is now no longer working either.
I'll look into the post you linked too, but I can't see how it will update that all, i.e. it says to use Odin which currently fails for me.

Odin doesn't fail for me when flashing kernels or recoveries, just when I try and flash full firmware earlier than MGG which includes the bootloader.
Flash full MH8 firmware from samfirmware, I have no issues except for the security problems.
Sent from my GT-I9505 using Tapatalk 4

In the odin output, the "fused: 2" shows the update has blown a q-fuse. You won't be able to odin an earlier firmware.

jd1639 said:
In the odin output, the "fused: 2" shows the update has blown a q-fuse. You won't be able to odin an earlier firmware.
Click to expand...
Click to collapse
No I know, but you can still flash recovery and modem etc. Is it failing at trying to flash older bootloader?
Sent from my GT-I9505 using Tapatalk 4

shrubz said:
No I know, but you can still flash recovery and modem etc. Is it failing at trying to flash older bootloader?
Sent from my GT-I9505 using Tapatalk 4
Click to expand...
Click to collapse
Yes, I hadn't realised that flashing the same or newer would work (it does). But WiFi is still borked... any ideas?

Tiny amount of progress, more out of hope I tried to flash a pre-rooted ROM - obviously this didn't work, but when I reflashed MH8 again I noticed the device made the start up sound (which it hadn't been) and WiFi is now working.
As a bonus if I go into Device Status it is now showing as Official, which is nice!
I think I'll leave it there for now, but will keep an eye out for progress, hopefully the bootloader will be "fixed" in due course.

Chainfire is working on a fix for CF-Root. So hopefully all will be good soon.
Sent from my GT-I9505 using Tapatalk 4

Bricked Galaxy Core Prime

(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

SM-T580, hopeless?

Hi everyone!
I hope I'm asking this in the right place. I think I may have really messed up my tablet. My apologies, this is going to be a long one.
After following some very bad advice I was using my SM-T580 8.1 (rooted with TWRP, Magisk and Manager) to explore Xposed. I now know Xposed + Samsung = bootloops. While trying to restore my poor little tablet I messed something up big time. When I tried to boot into recovery....it didn't work. So I booted into download mode and tried to flash stock firmware downloaded from Sammobile. While flashing with Odin 3.13.1, the connection was broken, my dog decided that it as the perfect moment for playtime. Now I can only boot into Odin mode and nothing else. To let it boot normally I get a bootloop with the Samsung Logo and the red warning "Could not boot into normal mode. Invalid Kernal length." Every time I try to flash the firmware I get "re-partition failed" error. I've tried two different PCs, 7 different USB cords, every USB port I have and stock firmware from 6.0 to 8.1. I've tried with and without the PIT file and tried checking/unchecking the repartition box in Odin's options. If I leave the repartition box empty is hangs on "setting up connection" and never moves past that. In the past week, I'm not sure how, I did get to the recovery menu. I cleared the cache and did a factory reset. It still went into the loop, so I tried recovery mode again and was able to look at the logs. I don't know why I looked because I really dont have any idea what they say. The only thing I did understand was that one of them said there was no recovery file. I assume this is a VERY bad thing. Since then I cant get back to it. Oh, depending on which USB port I plug into... sometimes the FRP is ON, with another port it is OFF. Don't know if that would help with a diagnosis. Sorry again for the long post, but I've tried to include as much information as possible. At this point is there any hope of fixing it?
Thank you in advance and a huge thanks for being my "go-to" since my SM-T530nu.

kstehling said:
Hi everyone!
I hope I'm asking this in the right place. I think I may have really messed up my tablet. My apologies, this is going to be a long one.
After following some very bad advice I was using my SM-T580 8.1 (rooted with TWRP, Magisk and Manager) to explore Xposed. I now know Xposed + Samsung = bootloops. While trying to restore my poor little tablet I messed something up big time. When I tried to boot into recovery....it didn't work. So I booted into download mode and tried to flash stock firmware downloaded from Sammobile. While flashing with Odin 3.13.1, the connection was broken, my dog decided that it as the perfect moment for playtime. Now I can only boot into Odin mode and nothing else. To let it boot normally I get a bootloop with the Samsung Logo and the red warning "Could not boot into normal mode. Invalid Kernal length." Every time I try to flash the firmware I get "re-partition failed" error. I've tried two different PCs, 7 different USB cords, every USB port I have and stock firmware from 6.0 to 8.1. I've tried with and without the PIT file and tried checking/unchecking the repartition box in Odin's options. If I leave the repartition box empty is hangs on "setting up connection" and never moves past that. In the past week, I'm not sure how, I did get to the recovery menu. I cleared the cache and did a factory reset. It still went into the loop, so I tried recovery mode again and was able to look at the logs. I don't know why I looked because I really dont have any idea what they say. The only thing I did understand was that one of them said there was no recovery file. I assume this is a VERY bad thing. Since then I cant get back to it. Oh, depending on which USB port I plug into... sometimes the FRP is ON, with another port it is OFF. Don't know if that would help with a diagnosis. Sorry again for the long post, but I've tried to include as much information as possible. At this point is there any hope of fixing it?
Thank you in advance and a huge thanks for being my "go-to" since my SM-T530nu.
Click to expand...
Click to collapse
I would first attempt to flash TWRP and see if it boots.

ashyx said:
I would first attempt to flash TWRP and see if it boots.
Click to expand...
Click to collapse
Sorry, I'm a little star struck that you responded to my post. I wanted to use the first TWRP i had installed, but it is a .img and I'm not sure how to use that without being able to access recovery mode. I am a baby when it comes to this stuff. I apologize for my lack of skills in this department. You guys that do this stuff for a living/hobby must have super human abilities. I've only been at this for several days and I'm already pulling my hair out.

kstehling said:
Sorry, I'm a little star struck that you responded to my post. I wanted to use the first TWRP i had installed, but it is a .img and I'm not sure how to use that without being able to access recovery mode. I am a baby when it comes to this stuff. I apologize for my lack of skills in this department. You guys that do this stuff for a living/hobby must have super human abilities. I've only been at this for several days and I'm already pulling my hair out.
Click to expand...
Click to collapse
Where do you find the image, it should also be available in tar format?

kstehling said:
Sorry, I'm a little star struck that you responded to my post. I wanted to use the first TWRP i had installed, but it is a .img and I'm not sure how to use that without being able to access recovery mode. I am a baby when it comes to this stuff. I apologize for my lack of skills in this department. You guys that do this stuff for a living/hobby must have super human abilities. I've only been at this for several days and I'm already pulling my hair out.
Click to expand...
Click to collapse
The Odin version of TWRP can be found here https://dl.twrp.me/gtaxlwifi/ When you flash it with Odin, be sure to go into options and uncheck "auto reboot". When it finishes, press and hold Home, Vol down and Power buttons till the screen goes black. Quickly shift from Vol down to Vol up buttons till the first screen appears. Keep holding Home and Vol up but release the power button. When the screen blanks you can release all the buttons and you should then be in the TWRP menu.
---------- Post added at 03:36 PM ---------- Previous post was at 03:29 PM ----------
kstehling said:
Hi everyone!
I hope I'm asking this in the right place. I think I may have really messed up my tablet. My apologies, this is going to be a long one.
After following some very bad advice I was using my SM-T580 8.1 (rooted with TWRP, Magisk and Manager) to explore Xposed. I now know Xposed + Samsung = bootloops. While trying to restore my poor little tablet I messed something up big time. When I tried to boot into recovery....it didn't work. So I booted into download mode and tried to flash stock firmware downloaded from Sammobile. While flashing with Odin 3.13.1, the connection was broken, my dog decided that it as the perfect moment for playtime. Now I can only boot into Odin mode and nothing else. To let it boot normally I get a bootloop with the Samsung Logo and the red warning "Could not boot into normal mode. Invalid Kernal length." Every time I try to flash the firmware I get "re-partition failed" error. I've tried two different PCs, 7 different USB cords, every USB port I have and stock firmware from 6.0 to 8.1. I've tried with and without the PIT file and tried checking/unchecking the repartition box in Odin's options. If I leave the repartition box empty is hangs on "setting up connection" and never moves past that. In the past week, I'm not sure how, I did get to the recovery menu. I cleared the cache and did a factory reset. It still went into the loop, so I tried recovery mode again and was able to look at the logs. I don't know why I looked because I really dont have any idea what they say. The only thing I did understand was that one of them said there was no recovery file. I assume this is a VERY bad thing. Since then I cant get back to it. Oh, depending on which USB port I plug into... sometimes the FRP is ON, with another port it is OFF. Don't know if that would help with a diagnosis. Sorry again for the long post, but I've tried to include as much information as possible. At this point is there any hope of fixing it?
Thank you in advance and a huge thanks for being my "go-to" since my SM-T530nu.
Click to expand...
Click to collapse
Are you using Home, Vol up and Power buttons to get to recovery? If that works, you can try Factory Reset from that menu. That should wipe the partitions so you can then go to download mode and flash with Odin. If not, then you'll have to try installing TWRP.
edit: If you can't get out of download mode, try the trick of Home, Vol down and Power till the screen blanks and quickly switching from Vol down to Vol up.

lewmur said:
The Odin version of TWRP can be found here... When you flash it with Odin, be sure to go into options and uncheck "auto reboot". When it finishes, press and hold Home, Vol down and Power buttons till the screen goes black. Quickly shift from Vol down to Vol up buttons till the first screen appears. Keep holding Home and Vol up but release the power button. When the screen blanks you can release all the buttons and you should then be in the TWRP menu.
---------- Post added at 03:36 PM ---------- Previous post was at 03:29 PM ----------
Are you using Home, Vol up and Power buttons to get to recovery? If that works, you can try Factory Reset from that menu. That should wipe the partitions so you can then go to download mode and flash with Odin. If not, then you'll have to try installing TWRP.
edit: If you can't get out of download mode, try the trick of Home, Vol down and Power till the screen blanks and quickly switching from Vol down to Vol up.
Click to expand...
Click to collapse
I have tried the Vol up + home + power to get to recovery without success. It happened once, days ago and I wiped the cache and tried a factory reset. It didnt work. I still get the bootloop with the Samsung logo and the Invalid Kernel length error at the top in red letters.
This afternoon I was able to download 3 different TWRP files for my device and tried to flash them. This time Odin stalled...
<OSM> Enter CS for MD5..
<OSM> Checking MD5.. Do not unplug the cable..
<OSM> Please wait..
and it never moves any further.

kstehling said:
I have tried the Vol up + home + power to get to recovery without success. It happened once, days ago and I wiped the cache and tried a factory reset. It didnt work. I still get the bootloop with the Samsung logo and the Invalid Kernel length error at the top in red letters.
This afternoon I was able to download 3 different TWRP files for my device and tried to flash them. This time Odin stalled...
<OSM> Enter CS for MD5..
<OSM> Checking MD5.. Do not unplug the cable..
<OSM> Please wait..
and it never moves any further.
Click to expand...
Click to collapse
Which version of Odin are you using? Also can you actually post screen shots of both odin after the failure and download mode on your device?

ashyx said:
Which version of Odin are you using? Also can you actually post screen shots of both odin after the failure and download mode on your device?
Click to expand...
Click to collapse
Odin 3.13.1
I'm not sure how to include a picture. I have several.
On the Odin/Download screen is says:
Odin Mode
Download Speed: Fast
Product Name: SM-T580
Current Binary: Samsung Official
System Status: Custom
FRP Lock: ON (or off depending on the day)
Secure Download: Enabled
Warranty Void: 1 (0x030c)
the last numbers are B:4 K:1 S:2

This is the log from my most recent attempt. First without the PIT file and then with it included. Don't know if it was the right thing to try, but at this point, why not
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1301)..
<ID:0/005> File analysis..
<ID:0/005> Total Binary size: 21 M
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005>
<ID:0/005> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Odin engine v(ID:3.1301)..
<ID:0/005> File analysis..
<ID:0/005> Total Binary size: 21 M
<ID:0/005> SetupConnection..
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!

kstehling said:
This is the log from my most recent attempt. First without the PIT file and then with it included. Don't know if it was the right thing to try, but at this point, why not
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1301)..
<ID:0/005> File analysis..
<ID:0/005> Total Binary size: 21 M
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005>
<ID:0/005> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Odin engine v(ID:3.1301)..
<ID:0/005> File analysis..
<ID:0/005> Total Binary size: 21 M
<ID:0/005> SetupConnection..
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
Click to expand...
Click to collapse
I would suggest downloading the combination firmware and see if that can be flashed.
Also where did you obtain the PIT file and are you choosing repartition with the the PIT file loaded?

ashyx said:
I would suggest downloading the combination firmware and see if that can be flashed.
Also where did you obtain the PIT file and are you choosing repartition with the the PIT file loaded?
Click to expand...
Click to collapse
If the combination firmware is the BL, AP, CSC and Home CSC, it did not work. The only file I haven't tried to flash is the Home CSC because there aren't settings I was trying to keep. I got PIT file two ways. One was a download I found and another was by extracting it from the CSC file. I tried to compare them to the best of my ability and it seemed like they matched. I tried flashing with and without the repartition option. The only thing I haven't selected in the options is NAND erase.
I've tried
XAR-T580UEU1APF5
XAR-T580UEU4CRK5
XAR_T580XAR4CSC1
And GTAXLWIFI_EUR_OPEN.pit with all 3.

kstehling said:
If the combination firmware is the BL, AP, CSC and Home CSC, it did not work. The only file I haven't tried to flash is the Home CSC because there aren't settings I was trying to keep. I got PIT file two ways. One was a download I found and another was by extracting it from the CSC file. I tried to compare them to the best of my ability and it seemed like they matched. I tried flashing with and without the repartition option. The only thing I haven't selected in the options is NAND erase.
I've tried
XAR-T580UEU1APF5
XAR-T580UEU4CRK5
XAR_T580XAR4CSC1
And GTAXLWIFI_EUR_OPEN.pit with all 3.
Click to expand...
Click to collapse
Where did you obtain the combination firmware?
https://drive.google.com/file/d/1sSIFiAeBBL5EMKNyxE31aUfsH9CefnfI

ashyx said:
Where did you obtain the combination firmware?
https://drive.google.com/file/d/1sSIFiAeBBL5EMKNyxE31aUfsH9CefnfI
Click to expand...
Click to collapse
SamMobile and Samfew

kstehling said:
SamMobile and Samfew
Click to expand...
Click to collapse
I doubt that is the combination firmware.
Use the one I posted.

ashyx said:
I doubt that is the combination firmware.
Use the one I posted.
Click to expand...
Click to collapse
<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/005> Added!!
<ID:0/005> Odin engine v(ID:3.1301)..
<ID:0/005> File analysis..
<ID:0/005> Total Binary size: 1016 M
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Odin engine v(ID:3.1301)..
<ID:0/005> File analysis..
<ID:0/005> Total Binary size: 1016 M
<ID:0/005> SetupConnection.. it got stuck here for more than 20 minutes.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
The first attempt was without the PIT, second try was with the PIT file as well as the repartition option checked. It did seem to take longer this time before it failed. I thought we were going to get lucky for a second.

kstehling said:
<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/005> Added!!
<ID:0/005> Odin engine v(ID:3.1301)..
<ID:0/005> File analysis..
<ID:0/005> Total Binary size: 1016 M
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Odin engine v(ID:3.1301)..
<ID:0/005> File analysis..
<ID:0/005> Total Binary size: 1016 M
<ID:0/005> SetupConnection.. it got stuck here for more than 20 minutes.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
The first attempt was without the PIT, second try was with the PIT file as well as the repartition option checked. It did seem to take longer this time before it failed. I thought we were going to get lucky for a second.
Click to expand...
Click to collapse
I suppose its worth now trying with nand erase.

ashyx said:
I suppose its worth now trying with nand erase.
Click to expand...
Click to collapse
Ok. I'll try it now. Should I use the PIT file? Or any of the others? BL, CSC? And just to be sure the file you gave me the link to should be in the AP spot, right?

I found how I could attach pictures for you. There is one that shows Odin with the "Pass" 1 successful/0 Failed. That happened in the middle of all of this by chance. I don't know if that helps any (I doubt it). The same problem was happening before it and after.

kstehling said:
I found how I could attach pictures for you. There is one that shows Odin with the "Pass" 1 successful/0 Failed. That happened in the middle of all of this by chance. I don't know if that helps any (I doubt it). The same problem was happening before it and after.
Click to expand...
Click to collapse
So you are able to flash the bootloader files?
Have you tried just AP?

kstehling said:
I found how I could attach pictures for you. There is one that shows Odin with the "Pass" 1 successful/0 Failed. That happened in the middle of all of this by chance. I don't know if that helps any (I doubt it). The same problem was happening before it and after.
Click to expand...
Click to collapse
I don't recognize the file you are using. The latest T580 stock ROM can be found here: https://www.sammobile.com/samsung/galaxy-tab-a-2016-101-wi-fi/firmware/SM-T580/
For the U.S. it is the one for Cellular South. It is a zip file that needs to be extracted. You only want to flash two of the four. The one starting with AP and the one starting with BP.
The Odin screen should look like the attached image before you click start. Don't change any of the default options.

SM-G935T bootlop after succesful flash with odin

Hi guys, I tried to factory reset my phone by flashing the latest firmware. These are the files that I used:
AP_G935TUVSBCTA2_CL14365146_QB28658134_REV02_user_low_ship_MULTI_CERT_meta.tar.md5
BL_G935TUVSBCTA2_CL14365146_QB28658134_REV02_user_low_ship_MULTI_CERT.tar.md5
CP_G935TUVSBCTA2_CP14916856_CL14365146_QB28658134_REV02_user_low_ship_MULTI_CERT.tar
CSC_TMB_G935TTMBBCTA2_CL14365146_QB28658134_REV02_user_low_ship_MULTI_CERT.tar.md5
HOME_CSC_TMB_G935TTMBBCTA2_CL14365146_QB28658134_REV02_user_low_ship_MULTI_CERT.tar.md5
I am a noob and I accidentally flashed the HOME_CSC file in the USERDATA section but every other file was in its place. Then after the successful flash, the phone restarted and entered a boot loop with the galaxy s7 and t-mobile logo. Also, I could't boot into recovery. It shows " recovery booting..." and stays there. After that, I tried to flash several different firmware versions but I always get errors like "fw ver check failed" and stops flashing. I only managed to reflash the first firmware again with success but the phone still doesn't boot. Does anyone know what is causing the problem? Am I using wrong firmware? can anyone help on this?
regards

bassist82 said:
Hi guys, I tried to factory reset my phone by flashing the latest firmware. These are the files that I used:
AP_G935TUVSBCTA2_CL14365146_QB28658134_REV02_user_low_ship_MULTI_CERT_meta.tar.md5
BL_G935TUVSBCTA2_CL14365146_QB28658134_REV02_user_low_ship_MULTI_CERT.tar.md5
CP_G935TUVSBCTA2_CP14916856_CL14365146_QB28658134_REV02_user_low_ship_MULTI_CERT.tar
CSC_TMB_G935TTMBBCTA2_CL14365146_QB28658134_REV02_user_low_ship_MULTI_CERT.tar.md5
HOME_CSC_TMB_G935TTMBBCTA2_CL14365146_QB28658134_REV02_user_low_ship_MULTI_CERT.tar.md5
I am a noob and I accidentally flashed the HOME_CSC file in the USERDATA section but every other file was in its place. Then after the successful flash, the phone restarted and entered a boot loop with the galaxy s7 and t-mobile logo. Also, I could't boot into recovery. It shows " recovery booting..." and stays there. After that, I tried to flash several different firmware versions but I always get errors like "fw ver check failed" and stops flashing. I only managed to reflash the first firmware again with success but the phone still doesn't boot. Does anyone know what is causing the problem? Am I using wrong firmware? can anyone help on this?
regards
Click to expand...
Click to collapse
What country are you in?

cooltt said:
What country are you in?
Click to expand...
Click to collapse
USA

bassist82 said:
USA
Click to expand...
Click to collapse
Oops! Very temperamental phone, the bootloader is locked.
You can only flash the same firmware that was on the device before you started but if not the latest G935T firmware should work.
p. s. Factory reset is an option in the settings menu, there's no need to flash new firmware.

cooltt said:
Oops! Very temperamental phone, the bootloader is locked.
You can only flash the same firmware that was on the device before you started but if not the latest G935T firmware should work.
p. s. Factory reset is an option in the settings menu, there's no need to flash new firmware.
Click to expand...
Click to collapse
I don't know what firmware the phone had installed before. What are my options now? I can't get into recovery menu, only download menu works. Tried already a bunch of different android 8.0 ROMs for g935t but Odin fails to install them. It only works with just one but it goes into boot loop.

bassist82 said:
I don't know what firmware the phone had installed before. What are my options now? I can't get into recovery menu, only download menu works. Tried already a bunch of different android 8.0 ROMs for g935t but Odin fails to install them. It only works with just one but it goes into boot loop.
Click to expand...
Click to collapse
If the phone is a T Mobile device you just need to install a T Mobile firmware from sammobile.
This is the latest for your device (and I'm assuming it is a G935 edge?)....
https://www.sammobile.com/samsung/g...e/SM-G935T/TMB/download/G935TUVSACSI1/297176/
Sammobile is a little slow for non premium members

cooltt said:
If the phone is a T Mobile device you just need to install a T Mobile firmware from sammobile.
This is the latest for your device (and I'm assuming it is a G935 edge?)....
https://www.sammobile.com/samsung/g...e/SM-G935T/TMB/download/G935TUVSACSI1/297176/
Sammobile is a little slow for non premium members
Click to expand...
Click to collapse
I already tried to flash this rom, I downloaded it from a faster source and fails to flash it.
<ID:0/007> Odin engine v(ID:3.1303)..
<ID:0/007> File analysis..
<ID:0/007> Total Binary size: 4575 M
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> NAND Write Start!!
<ID:0/007> SingleDownload.
<ID:0/007> emmc_appsboot.mbn
<ID:0/007> lksecapp.mbn
<ID:0/007> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/007> Removed!!

bassist82 said:
I already tried to flash this rom, I downloaded from a faster source and fails to flash it.
<ID:0/007> Odin engine v(ID:3.1303)..
<ID:0/007> File analysis..
<ID:0/007> Total Binary size: 4575 M
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> NAND Write Start!!
<ID:0/007> SingleDownload.
<ID:0/007> emmc_appsboot.mbn
<ID:0/007> lksecapp.mbn
<ID:0/007> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/007> Removed!!
Click to expand...
Click to collapse
Fail (auth) means your phone is not in download mode or the firmware file is not in the correct box in Odin.
I think you may be better reading a step by step guide on how to flash firmware.
If you manage to flash and get stuck in a bootloop do the following.
1. No matter what the phone is doing just press volume down+home+power (in that sequence)
2. When the screen goes black quickly move your finger to volume up while still pressing home + power. This will boot you into recovery menu.
3. Choose "wipe cache partition" then "reboot system now"
4. Allow phone to go through the first boot up, it could take 10 minutes just leave it until you get the welcome screen.

cooltt said:
Fail (auth) means your phone is not in download mode or the firmware file is not in the correct box in Odin.
I think you may be better reading a step by step guide on how to flash firmware.
If you manage to flash and get stuck in a bootloop do the following.
1. No matter what the phone is doing just press volume down+home+power (in that sequence)
2. When the screen goes black quickly move your finger to volume up while still pressing home + power. This will boot you into recovery menu.
3. Choose "wipe cache partition" then "reboot system now"
4. Allow phone to go through the first boot up, it could take 10 minutes just leave it until you get the welcome screen.
Click to expand...
Click to collapse
When I press volume down+home+power it gets me to a screen says "warning: a custom o/s can cause critical problems bla bla bla..." and underneath it shows these options: 1) Volume up: continue 2) Volume Down: Cancel (restart phone) 3) Home Button: Show Barcode. If I proceed with the 1st option it goes to download mode where I flash with odin. I tried also the combination volume up+home+power with the phone witched off and it shows the message "recovery booting..." on screen with blue text but then it shows the android icon and says" installing system update, then restarts and falls into boot loop again with the samsung logo.

bassist82 said:
When I press volume down+home+power it gets me to a screen says "warning: a custom o/s can cause critical problems bla bla bla..." and underneath it shows these options: 1) Volume up: continue 2) Volume Down: Cancel (restart phone) 3) Home Button: Show Barcode. If I proceed with the 1st option it goes to download mode where I flash with odin. I tried also the combination volume up+home+power with the phone witched off and it shows the message "recovery booting..." on screen with blue text but then it shows the android icon and says" installing system update, then restarts and falls into boot loop again with the samsung logo.
Click to expand...
Click to collapse
Yes that's fine, just keep trying to get it into recovery, it can take a few attempts for recovery to boot successfully.
The locked bootloader models are a nightmare unfortunately but there's lots of info on the forum about all the different issues and how to resolve.
Sometimes the only solution is to try flash the firmware which was there before you did anything to it eventhough there is a newer version.

cooltt said:
Yes that's fine, just keep trying to get it into recovery, it can take a few attempts for recovery to boot successfully.
The locked bootloader models are a nightmare unfortunately but there's lots of info on the forum about all the different issues and how to resolve.
Sometimes the only solution is to try flash the firmware which was there before you did anything to it eventhough there is a newer version.
Click to expand...
Click to collapse
I tried a lot of times already but it finally gets to a point that says "no command" with the android icon on top and if I press some times the volume up/down or home it finally gives some error messages and stuck there. It seems to me that the recovery menu is missing completely for some reason and the second problem is I don't remember which firmware version it had exactly before my attempt to flash another.

Anyone? Do I need a pit file to fix this problem?