Database Info

[Q] OTA 4.4.2 update failed, Samsung Experience no help, Please help me

I did the verizon pushed update to 4.4.2 today on my SCH I535 S3 which was totally stock with encryption. After the install finished "upgrading apps" it then did a re-boot and asked for my encrypt pin then showed the outline Andy. Then after a couple of vibrations it re-boot again and will continue this cycle until battery is removed. After sitting on the phone for several hours and conversing with Samsung and Verizon they pointed me to Samsung Experience in a Best Buy and if that doesn't work I have to send it to Samsung for re-flash. They said they couldn't get their software to recognize my phone. The guy there recommended using odin to download a stock rom.
I have downloaded odin 3.07 and have downloaded a 4.3 stock rom. I set up odin with auto reboot and F. reset time checked and nothing else. I select the .tar.md5 in the bootloader and here is my odin output:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I535VRUCNC1_I535VZWCNC1_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> sbl2.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl3.mbn
<ID:0/004> aboot.mbn
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
My phone says:
ODIN MODE
PRODUCT NAME: SCH-I535
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
QUALCOMM SECURE BOOT: ENABLE
BOOTLOADER AP SWREV: 2
SW REV CHECK FAIL : Found 2 > Binary 1
Please tell me how to recover my phone. I am new to this so give me detail please.

I believe since u pushed the 4.4.2 ne1 update u need to Odin the 4.4.2 ne1 tar file, not the 4.3 file

Thanks so much! I tried the 4.4.2 tar file and... it worked. I thought that since the 4.4.2 update is what failed I'd have to go back to the 4.3 but that was clearly flawed thinking on my part. I can't believe that it worked and best of all everything is still there! I still have all my apps and data, as if nothing at all happened.
Thanks so much for your suggestion!

4theluvof2 said:
Thanks so much! I tried the 4.4.2 tar file and... it worked. I thought that since the 4.4.2 update is what failed I'd have to go back to the 4.3 but that was clearly flawed thinking on my part. I can't believe that it worked and best of all everything is still there! I still have all my apps and data, as if nothing at all happened.
Thanks so much for your suggestion!
Click to expand...
Click to collapse
No problem!! Glad it worked, hit that thanks button if you don't mind!

SCH-I535
hey did you get back on 4.3 or not???? plz if u did then refer me link plzzzzzzzz

hammadsalik said:
hey did you get back on 4.3 or not???? plz if u did then refer me link plzzzzzzzz
Click to expand...
Click to collapse
No I didn't get the 4.3 working. I did get the 4.4.2 working though. I am not sure how exactly you'd revert back to an older version, Sorry.

[Completed] [HELP] Galaxy S6 Stuccked into Boot Mode

Hi guys I got a problem with my Galaxy S6 SM-G920F. Some mounths ago I flashed CF-Auto Root for my device and it gets bricked because my model hadn't the opportunity to disable the bootloader or something else like this. So, to fix the phone, I just flashed up via Odin 3.10.6 the stock firmware and everything worked like a charm. I re-tried to root my device with the UniKernel and it worked very well. After done the root, I flashed a new BL and CP taken from the XtreStoLite ROM link.
- XtreStoLite ROM: http://forum.xda-developers.com/gal...xtrestolite-deodexed-mod-edition-1-3-t3119968
- XtreStoLite BL and CP: http://forum.xda-developers.com/showpost.php?p=60112855&postcount=3
And then I flashed up via TWRP the XtreStoLite ROM.
One week ago I resetted my device and I flashed again the stock firmware and everything worked once again. Today I'm been trying to re-flash the BL and CP and then flashing again the ROM but when I tried to flash the BL an error appears "FAIL" on Odin.
I also tried flashing the CP before and then BL but nothing (The CP flash worked instead of BL).
I did a mistake, I flashed the CF-Auto Root on my device and of course it gets bricked so I tried to fix it flashing again the stock firmware but I have "FAIL" on Odin..
P.S: I also flashed the UniKernel because I thought to have a chance to restore it but the device's still bricked.
This is what I see on Odin:
<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> 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> 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)
I hope you can help me and sorry for my bad english. Thanks

try from recovery or odin for mobile
i don t now very much but when something fialed in odin i go to try flashing via recovery
i am just trying to help me freind

Abdo sh said:
i don t now very much but when something fialed in odin i go to try flashing via recovery
i am just trying to help me freind
Click to expand...
Click to collapse
Abdo sh, I appreciate your answer but I can't even transfer files from my PC to the device. By the way I think that's not possible flashing the stock rom via TWRP or recoveries in general. Thanks anyways

transferring files
My recovery is twrp and when I get into twrp recovery and connect my device to pc it opening on pc and i can transfer files

Phone only boots to download mode after failed ODIN installation.

So I was running Ressurection Remix ROM and I was on OG1 but I wanted to upgrade from OG1 to OK4 so I downloaded the .tar for OK4. Went to install it through ODIN and I got this message.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G900PVPU3BOK4_G900PSPT3BOK4_G900PVPU3BOK4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin engine v(ID:3.1005)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> sbl1.mbn
<ID:0/006> rpm.mbn
<ID:0/006> tz.mbn
<ID:0/006> sdi.mbn
<ID:0/006> NON-HLOS.bin
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img.ext4
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

I also tried odin flashing og1 but it does not work I also try to recover through kies but it says device is unsuppported even though it shows me on the phone screen to use the recovery feature in kies.

forget kies, use Odin. Im betting its a bad tar.md5 (same as the thread before this one in this forum). Id get a fresh copy of the next to newest tar.md5 and flash it in Odin, and while youre at it, get a new copy of odin (the one i use is 3.10) and ive been getting all my tarballs from idoneapps.com for a few mos now and theyve been solid as a rock. Give that a whirl and see whatcha got. Also, i think your culprit is a bad bootloader, S5s booting to download mode after a factory image flash is usually caused by the bootloader

youdoofus said:
forget kies, use Odin. Im betting its a bad tar.md5 (same as the thread before this one in this forum). Id get a fresh copy of the next to newest tar.md5 and flash it in Odin, and while youre at it, get a new copy of odin (the one i use is 3.10) and ive been getting all my tarballs from idoneapps.com for a few mos now and theyve been solid as a rock. Give that a whirl and see whatcha got. Also, i think your culprit is a bad bootloader, S5s booting to download mode after a factory image flash is usually caused by the bootloader
Click to expand...
Click to collapse
Got it to work I had redownloaded the tar file and got the latest odin. But still didn't work. I went to go eat and tried it again and then suddenly it worked -.- Odin is unstable compared to HTC's RUU. I am just glad I got it to work
Sent from my SM-G900P using XDA-Developers mobile app

svz235 said:
Got it to work I had redownloaded the tar file and got the latest odin. But still didn't work. I went to go eat and tried it again and then suddenly it worked -.- Odin is unstable compared to HTC's RUU. I am just glad I got it to work
Sent from my SM-G900P using XDA-Developers mobile app
Click to expand...
Click to collapse
Unstable? How so? I can tell you this about Odin, it can take a while for it to load a file of the size of S5 restore tar.md5s. The root files you flash in Odin are small, so Odin only takes about 5 seconds to load them(if that), but a 1.5 GB file can take about 4 to 5 min on slower processors. My desktop (benchmarks at 5700) loads those files in about 90 seconds and almost instantaneously for the root and recovery files
Sent from my SM-G900P using XDA Free mobile app

WIFI broken, MM 6.0.1 DBT version SM-N915FY

my wifi is broken after 5-10 seconds and comes back, than again brocken. tested with stock rom and custom. bootloader is MM.
thats correctly firmware " N915FYXXU1DPE1_N915FYDBT1DPE1_N915FYXXU1DPC3 " now...
can any help please?
ps: mobile phone is very clean and without scratches or breaks. never dropped !!!

Tafty said:
my wifi is broken after 5-10 seconds and comes back, than again brocken. tested with stock rom and custom. bootloader is MM.
thats correctly firmware " N915FYXXU1DPE1_N915FYDBT1DPE1_N915FYXXU1DPC3 " now...
can any help please?
ps: mobile phone is very clean and without scratches or breaks. never dropped !!!
Click to expand...
Click to collapse
OK, always the same suspects:
1. Did you flash MM via Odin, or OTA? If Ota, proceed with 2. If flashed manually, reflash the rom and go to 2.
2. Try clearing cache
3. If that doesn't help, make a full wipe, reinstall MM via Odin

charly-whiskey said:
OK, always the same suspects:
1. Did you flash MM via Odin, or OTA? If Ota, proceed with 2. If flashed manually, reflash the rom and go to 2.
2. Try clearing cache
3. If that doesn't help, make a full wipe, reinstall MM via Odin
Click to expand...
Click to collapse
many thanks for answere.
I had bought the note edge with stock rom 5.1.1. there already worked wlan not right. so I flashed MM stock rom it as stock !! there the same problems .....
then I wanted to go back to 5.1.1. no chance .... I had used extra again share the edge PIT and the DBT firmware in 3 parts for odin. Whenever want odin the "hidden.img" Write, cancels odin the installation.
Odin error;
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N915FYXXU1DPE1_N915FYDBT1DPE1_N915FYXXU1DPC3_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> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> boot.img
<ID:0/003> cache.img.ext4
<ID:0/003> hidden.img.ext4
<ID:0/003> FAIL! (Ext4)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

I'd suggest to use the one-part-DBT firmware, that worked for me.
Just flash with Odin, put in AP, should work. I'll send you a PM.
To revert to 5.11 you need to fully wipe the phone, then flash the DBT one-part 5.11 firmware.

[Help Needed] Failed Firmware update using Odin. Need help flashing correct firmware.

Hello,
I tried to update my wife's Samsung S7 firmware using Odin and managed to brick/boot loop it.
I need some help getting it working again.
Its an unlocked T-Mobile Samsung S7 (SM-G30T) from Ebay using a Virgin Mobile SIM and it originally had the G930TUVU4APK1 (Android 6.0.1) firmware on it.
It would not update OTA, so I downloaded the G930TUVS8CRJ1 (Android 8.0) from Sammmobile.com.
I opened Odin, selected the BL, AP, CP and CSC files and hit Start. The Odin log said "failed (auth)".
I exited Download Mode and tried to restart the phone, it would try to boot but it gave me the message "security error: this phone has been flashed with unauthorized software and is locked".
I downloaded and tried to flash the older G930TUVU4APK1 (Android 6.0.1) firmware, but it did not work.
I am able to get back into Download Mode and Odin still recognizes the phone. I think its possible to save it?
I should have never tried to do this, I feel terrible and I need some help. How can I fix this? Where can I find firmware that I can flash to fix this?
I would really appreciate your help! Thank you very much!!

I just tried to flash the older Android 6.0.1 firmware again. This time selecting only AP, CP and CSC.
This is what the Odin log says.
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1301)..
<ID:0/005> File analysis..
<ID:0/005> Total Binary size: 4661 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> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> NAND Write Start!!
<ID:0/005> SingleDownload.
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Something I noticed. Before I tried to update it, on the Download Mode screen, it said "Current Binary: Official".
Now it says "Current Binary: Custom". I think I need to get that to say "Official" again.

I would suggest that you download the firmware again and then try flashing it.....
As far as that custom binary thing is concerned.... That's not going to change as far as i know cause that tripped the knox.... And the warranty is lost... If it was there ..... So i hope u recover it again.... Also try getting into the recovery mode and format before flashing the firmware.... That might help.....
Let me know what happens....
All the best

Thanks for the help soyuz4u!
After spending a long night trying various things,
I was finally able to fix it by flashing the G930TUVS8CRJ1 (Android 8.0) firmware again using Odin. Except this time I used the "CSC..." file, instead of the "HOME_CSC..." file.
Originally I was trying to preserve the data on the phone, so thats why I used the Home file. However, after struggling for a while I eventually gave up hope and decided try it again, this time wiping everything out with the CSC file... and to my delight, it worked! Thank goodness! Its working perfectly on an official firmware!

Just as an FYI, USA model S7's can't be downgraded via Odin, so once you're on Oreo your only option to resolve issues would be to flash Oreo.

i doubt there is working stock firmware for android 6.0.X. I have tried several stock firmwares they all fail.