Database Info

[Q] Help to flash Note 2 with stock ROM 4.3

Hello
I decided to try jedi master x2 (the version of my stock ROM was 4.3). After trying it out for a while I noticed poor battery performance and when phone was locked I had to press the menu button several times to see the screen. Yesterday my phone was booting up by itself. It did a couple times then got stuck with the samsung logo. Reboot again and again and the same stuff happened that's when I decided to flash stock rom from samsung.updates/device site using odin3 v3.09 however, I have not been successful. After it checks the md5 OK, it fails on the NAND write. Is it the case that the NAND memory is not unlocked? I am still able to boot into recovery though. I'd appreciate if anybody can land me a hand on how to flash stock rom on my device.
Thanks
** Update to the issue above 1/13/14 8:24 AM
I use ODIN 3.09 to upload the md5 I got from samsung.updates.com I get this:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T889UVUCMK7_T889TMBCMK7_T889UVUCMK7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I am able to boot into recovery mode. I have not tried to upload any other ROM to my sdcard and install it there. The stock ROM I had before was Android version 4.3.
I read this post http://forum.xda-developers.com/showthread.php?t=2470262&page=3
then I looked at my device and read the following:
custom binary download: Yes (1 counts)
current binary: custom
system status: custom
knox warranty void: 1 <--- I think that's the problem
As you may know knox is a security feature which helps you to securely separate your personal and professional data. Well, in my case is not helping at all.
Another question: How am I going to remove knox with my phone only able to get into recovery or download mode?

Galaxy S3 SCH-I535- Stuck In Odin Mode After Trying To Downgrade To 4.3

Screwed up, need some help. (4.4.2 to 4.3 attempt gone bad)
Hello everyone out there! Long time lurker, first time poster.
So I've had what seems to be a soft brick on my verizon s3 (SCH-I535) and it is time to just lay it out here because (as always) I can't find the fix to MY problem (so selfish I know )
So let's start at the very beginning..
I have had my s3 for awhile now and I ended up rooting the phone to stay on 4.3. The biggest reason for this was to keep FoxFi working (I have no internet where I live and tethering is the only option). Once FoxFi was working for 4.4 I decided to go ahead and update but first I had to unroot which wasn't a big deal. I unrooted and voila! I was on 4.4.2!
Okay so I just tried ThePagel's methosd
When I upgraded, I noticed my FoxFi was VERY slow all of a sudden and being a gamer, I didn't like this one bit! So I thought to myself "Hey, just flash back to your 4.3 file."... as I hear all of your collective heads shaking in disappointment, followed by facepalms, I now see the error of my ways.. Attempting to flash back to 4.3 of course hung my phone up in Odin (It was stuck at SetupConnect I believe) and this led to my soft brick. Bummer...
So what have I attempted? Well I kept seeing this thread pop up, http://forum.xda-developers.com/showthread.php?t=2586319 but it's talking about the OTA for 4.3.... I was 4.4.2. I also attempted to fix the issue via this thread: http://forum.xda-developers.com/showthread.php?t=1840030 and alas, it fails me as well.
Now as far as errors for these trails, let's get down to what I see on my phone and what I see on odin..
When trying the Hero's method, Odin fails with this log:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> VRALEC.bootchain.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> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
On my phone, I get this log: (Under download mode of course)
ODIN MODE
PRODUCT NAME: SCH-I535
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
(In grey)
QUALCOMM SECUREBOOT: ENABLE
BOOTLOADER RP (or AP, can't tell) SWREV: 2
(in red)
SW REV CHECK FAIL : Fused 2 > Binary 0.
Right now I am downloading the file needed in ThePagel's fix but it is VERY slow (only dial up and satellite internet I **** you not, out here). When that gets done I will come back here and post the same logs for both the phone and ODIN should it not work.
I see there are a lot of fixes out there for various things but the problem is, I don't know exactly what is wrong with my phone. Of course if I try to turn it on normally I get the yellow triangle so the fact it turns on means it is a soft brick. I have also read a lot of threads talking about custom recovery but I don't know how this works. Does custom recovery get me back into recovery mode? Or is this only for when your phone is rooted. Anyway, I'd love to pick some brains on this matter and maybe someone sees something in the errors that I do not.
I apologize for my ignorance... all I wanted to do was go back to 4.3 and root it to stay there.. if this can not be done and I am forced to stay with 4.4.2, I will do so.. but any advice for either would be a great welcomed sight. Send links to threads and what have you if you don't want to type, other than to call me an idiot, I deserve it for not reading and understanding everything fully before attempting this flash.
Okay I just tried ThePagel's method and this is what I get:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_I535VRUCNC1_I535VZWCNC1_2198062_REV09_user_low_ship.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> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
On my phone, everything looks the same except the last line reads:
SW REV CHECK FAIL : Fused 2 > Binary 1.
So.....what do you guys think?
****UPDATE****
I was able to find a stock, no frills 4.4.2 kitkat and I flashed that. My phone is back working again. Is there a way to delete this thread?

I don't believe there is any way to delete the thread without getting a forum moderator to do so.
Personally I would recommend against deleting it. Better would be using it as a teaching example for others who find themselves in the same predicament, especially since you added how you fixed the issue. It may also help some from making the same error.

Boot Loop after failed root

Hello, at this point I don't care about rooting my phone. I would just like to fix it and restore it back to normal.
I have a Galaxy S6 Edge. The thing that's wrong with my phone is that it's on a boot loop and it can't go into recovery mode (or boot loader what ever its called). It also says when on the Samsung screen boot loop (RECOVERY IS NOT SEANDROID ENFORCING)
My model is G925TUVU2COF8 and it's running 5.1.1. Every time I try to flash my firmware in odin 3.10.6 I always get this:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G925TUVU2COF8_G925TTMB2COF8_G925TUVU2COF8_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1005)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Can somebody please help!

if you need your phone fast fixed, you could flash custom recovery and adb push a rom, for the odin problem idk..., after latest bootloader got myself a strange odin flash bug if i try to flash a stock rom :/

"My model is G925TUVU2COF8"
That's not the model, that's a firmware version.
Your model number is the G925T. Which is the tmobile S6 edge. The F8 firmware is 4 months old, which is probably why it's not working for you, you may unintentionally be trying to downgrade. You need G925TTMB3DOI1 firmware. You can get it here http://www.sammobile.com/firmwares/download/56137/G925TUVU3DOI1_G925TTMB3DOI1_TMB/ or google for a faster dl source.

It's fixed now!!! Thank you so much!

Sboot.bin is the bootloader part of firmware. Only the latest firmware will fix this issue. Glad your issue is now okay.

can't flah stock firmware

when I boot it just gives me some kernel is not seandroid enforcing so i'm trying to flash a stock firmware. G900P_SPR_G900PVPU3BOG1_G900PSPT3BOG1_Original.zip. is the name of file and its for a sprint S5.
Here is the odin output
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1100)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
HELP ME please.

I can flash the backup although it gets stuck at yellow boot screen. but that does get rid of the seaandroid enforcing

If someone could help me as well I'm having a similar problem. I have tried using multiple Odin versions and many stock SM-G900P 4.4.2 firmwares from multiple sources, but always have the same messages pop up.
Odin:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_SPT_G900PVPU1BOA6_G900PSPT1BOA6_CL3859396_QB3804569_REV00_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
USB debugging is on and Odin does recognize the device is connect, I have also already installed the drivers again just to be sure. I have used Odin before with no trouble maybe its the fact the phone is from sprint and on lollipop since sprint is stingy on unlocking -_-. If someone could point me in the right direction or 100% working firmware links I'd appreciate it. I have also tried going about this through Heimdall and failed not even being able to obtain the pit file. If someone could provide a working one I'd also appreciate it I am fully aware it may brick the phone as everything else may do. Or show me the me the step by step to flash with Heimdall with a .tar. I'll take any advice thank you

you can try the newer firmware ok4
maybe this will work . unzip and place md5 in ap slot of odin
http://forum.xda-developers.com/spr...t/rom-sprint-ok4-stock-tar-file-odin-t3262667

Sprint new locked bootloaders
unteaglejohnk said:
when I boot it just gives me some kernel is not seandroid enforcing so i'm trying to flash a stock firmware. G900P_SPR_G900PVPU3BOG1_G900PSPT3BOG1_Original.zip. is the name of file and its for a sprint S5.
Here is the odin output
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1100)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
HELP ME please.
Click to expand...
Click to collapse
I have the same problem myself and it took me a few minutes to realize what the problem is. I just got a new phone from Sprint because my other one the USB port was basically broken I couldn't connect or charge. So after a few failed attempts at flashing a ROM I decided to look at my firmware and realized that it was the new updated bog1 version. Sprint decided to lock all the boot loaders so as of this moment I don't know how to flash any ROM or downgrade as the bootloader will not let you. As a matter of fact just last night I was walking into Walmart I pulled my phone out of my pocket to look at it and it was just finishing up installing some security policy updates. My phone then immediately restarted and got stuck at the spark screen. Just the fact that I was rooted sent my phone into a boot loop. As of right now the only thing I can do is reflash the stock bog 1. I have managed to get access to this one and I'm working on modifying the bootloader in anyway I can. I'm a little newer to this but I catch on pretty quick. As of now I have all the permissions unlocked for me to access all the files in that stock bog1 rom but haven't found a way to make them stick yet. I'm going to have to break down each individual file and hopefully I can come up with a solution or anybody for that matter because I'm a few months away from my contract being up and if I can't root my phone and customize it I don't want it. If they want my phone lock down and toddler mode then they can pay for it that's how I look at it lol. Make sure you turn off automatic security updates. There's also a post in here of how to clean that out so you don't have the newest security policy update. I know the exact file the bootloader is in but haven't found a way to get into it or modify it yet even though I have permission. It shows it copying /deleting but doesnt change. There is way too many people in this world to not have someone come up with a solution by now and anytime I search for it I get results from a year to five years ago , hardly anything recent thanks google. I also posted on times and started a thread I'm trying but I'm not as advanced as some of these developers on here but I am determined lol

I finally got it to boot up. Just took like 20 mins. Now it boots sometimes while others it won't and says process has stopped responding after the yellow screen. Why does it do this. The rom is official rom directly off Samsung kids.

may have cracked bootloader BOG1 G900P
i have been playing in thr sys files and today i managed to get a custom animation boot installed. after that i flashed a modded bog1 file from philz. it took and succesfully booted and am now reinstalling all my apps. i think i over wrote or blocked my bootloader. ill get back when i know for sure:laugh:

http://samsung-updates.com/device/?id=SM-G900P

Can't load J700p into bootloader

So i recently flashed lineage 14.1 j7ltespr to my J700p, and the rom loaded up fine, but it won't recognize the sim card. As this is my daily driver that can't be the case, so i tried to flash a stock rom back on. I think i could get it to work, but the phone won't boot into bootloader anymore.
It has the most recent version of twrp for the model. And it will system boot, and boot recovery just fine. But when i try to boot loader, it just gives me a charging symbol, and freezes. I've been trying to fix this anyway i can for the last 12 hours.
I also tried adb, and odin. Odin gives me an auth error every time i try to load a stock rom. If anyone could help, i'd be very appreciative.
I'd take fixing the sim not found, the bootloader not coming up, or the NAND Write Start!! FAIL! (Auth) error
thank you for your time

J700P
tjjc4 said:
So i recently flashed lineage 14.1 j7ltespr to my J700p, and the rom loaded up fine, but it won't recognize the sim card. As this is my daily driver that can't be the case, so i tried to flash a stock rom back on. I think i could get it to work, but the phone won't boot into bootloader anymore.
It has the most recent version of twrp for the model. And it will system boot, and boot recovery just fine. But when i try to boot loader, it just gives me a charging symbol, and freezes. I've been trying to fix this anyway i can for the last 12 hours.
I also tried adb, and odin. Odin gives me an auth error every time i try to load a stock rom. If anyone could help, i'd be very appreciative.
I'd take fixing the sim not found, the bootloader not coming up, or the NAND Write Start!! FAIL! (Auth) error
thank you for your time
Click to expand...
Click to collapse
Can you go into settings an turn off adb root then you should be able to flash stock from Odin ! Use Odin 3.12.5 !!

peter couniaz said:
Can you go into settings an turn off adb root then you should be able to flash stock from Odin ! Use Odin 3.12.5 !!
Click to expand...
Click to collapse
Thank you peter for the advice. I tried what you suggested. Still no luck. Here is the output of the odin runs, they were all identical though i tried different roms, 3 different versions of odin, root on and off, as well as with debugging on and off. Same out put every time.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1301)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 2970 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> NAND Write Start!!
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Also the output on the download screen on the phone throws this error
SW REV CHECK FAIL : [aboot] Fused 2 > Binary 1
I hope that helps.

J700P
tjjc4 said:
Thank you peter for the advice. I tried what you suggested. Still no luck. Here is the output of the odin runs, they were all identical though i tried different roms, 3 different versions of odin, root on and off, as well as with debugging on and off. Same out put every time.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1301)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 2970 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> NAND Write Start!!
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Also the output on the download screen on the phone throws this error
SW REV CHECK FAIL : [aboot] Fused 2 > Binary 1
I hope that helps.
Click to expand...
Click to collapse
It all or nothing on this if you can get into recovery factory reset then wipe system an go into download mod an try Odin one last time ! But before all that make shore debugging is on an make shore you are using a Samsung usb cord best the one that came with the phone ! An use Odin 3.12.5 or older 3.13.01 doesn't work right for that phone !!! PS make the firmware file isn't mest up ! Get the latest firmware file !