Good afternoon, and thank you for taking your time to read my thread.
I recently attempted to root my phone, and having little to no issue rooting many other devices (including my previous phone, a Galaxy Prevail) I decided I was fed up with the bloatware.
I began the process, but encountered an issue where ODIN failed while attempting to root the device.
I am not 100% sure, but I know this information may very well help me to a solution: I don't think I enabled debug mode in settings.
When attempting to use KIES to restore firmware, I get a "this device is not recognized" error, and even when trying to manually enter S/N and device info, it will not let me use any part of KIES to restore it.
So I then tried to use ODIN to flash stock firmware...
First error I receive is almost immediate:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747UCDLK3_I747ATTDLK3_I747UCDLK3_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> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
Occasionally, and after about 3 minutes this appears. (and it seems only when attempting to use ODIN on the device multiple times before reboot)
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747UCDLK3_I747ATTDLK3_I747UCDLK3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Please, if you have any advice for me I am begging.. I only was able to upgrade to this device because of a promotion AT&T had to get it for $5 dollars.. I am very income restricted so buying a new device is a crippling idea. If you do by chance suggest I download a new version of ODIN ( I am using 3.07, I find it most stable) or a new stock firmware etc, please provide links as I have attempted many different mirrors (with horrendous download speeds) for different stock recovery firmware.
THANK YOU!!!
I appreciate your time.. All it took was attempting to root the phone another time to restore access... Wow.. I hate myself ._.
Vonzilla said:
I appreciate your time.. All it took was attempting to root the phone another time to restore access... Wow.. I hate myself ._.
Click to expand...
Click to collapse
So, what's the state of the phone now and what happens when you try to power on? Is it now booting normally to system?
Related
Help!
Phone kept crashing on occasion after an install of BBM for android. An Uninstall and Factory Reset in the settings did not help.
2 days ago it crashed and after powering it back on I get the:
Downloading Do not turn off target !!
&
Could not do normal boot.
ODIN MODE
PRODUCT NAME: SGH-I747M
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS: NONE
QUALCOMM SECUREBOOT: ENABLE
I tried flashing back to stock via ODIN 3.6/3.7 but all I get is the below:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_I747MVLDMF1_I747MOYCDMF1_1189444_REV04_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<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>
<ID:0/003> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
I've searched but this is as far as I can get
Kies firmware recovery was no help either.
Please Help!
I don't know what you did, but it looks like you need to send it to Samsung. If there isn't a PIT partition, that's bad, and you wouldn't want to mess with those, or you might end up with even worse a brick.
Ok, I got a new Note II the other day with 4.3 already installed via Kies or OTA. I attempted to push, via ODIN, "CF-Auto-Root-d2tmo-d2tmo-sght999.tar". I REALIZE THIS IS THE ROOT FOR S3; I KNOW I FLASHED THE WRONG FILE. PLEASE DO NOT POST SAYING I FLASHED THE WRONG FILE. I KNOW I SCREWED UP BIG TIME, AND I'M HOPING SOMEONE IS NICE ENOUGH TO TRY AND HELP ME THROUGH THIS. My laptop sat there for the better part of 2 hours acting like ODIN was cranking along but the bar never moved. After 2 hours, I had to pull the cord from the phone (stupid move, I know!), and this is, of course, where the problem began.
Now, I get the coveted "Firmware Upgrade encountered an issue. Please select recovery mode in Kies & try again." screen. The phone will, obviously, go no further than this in booting up. I am able to get to download mode.
I attempted to install JellyBean Release 4.3 (December 2013) from this thread to alleviate the issue. Here's the ODIN result:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_TMO_T889UVUCMK7_2.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> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> cache.img
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
Now, as I sit here and write this, I think installing a stock firmware like this one might not work at all. I need to install a recovery (stock or otherwise) to make this problem disappear. I tried to reinstall the CF-Auto-Root file and got this result:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-d2tmo-d2tmo-sght999.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-d2tmo-d2tmo-sght999.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..
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
Again, it didn't do anything for hours. I pulled the cord again since it didn't look like it was actually writing anything to my phone.
I don't think I can use KIES as a last resort since I never backed up the phone through KIES before. I am out of ideas, and I would really like to get this phone operational again. Also, the serial number has been removed from the device (Igot the phone from Ebay), so I don't think I could use this route either.
Any and all help would be greatly appreciated.
Thanks in advance!
Download and flash CF auto-root for sgh-t889(link below)it includes recovery, then perform factory reset by rebooting in to recovery.
http://download.chainfire.eu/266/CF-Root/CF-Auto-Root/CF-Auto-Root-t0ltetmo-t0ltetmo-sght889.zip
Sent from my SGH-T889 using xda app-developers app
Hello, i have one piece n7100 16gb that was stuck on repair mode...i tried to repair it with odin on windows 10 detected the device but fail: Used Odin3_v3.10.7 and N7100XXUFNL1_N7100OJVFOD1_LYS
Tried on windows xp still fail same..
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin engine v(ID:3.1100)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006>
<ID:0/006> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
Tried flashing with 16gb pit file...fail now when turn on phone shows grey screen but goes into download mode....help
andrew21 said:
Hello, i have one piece n7100 16gb that was stuck on repair mode...i tried to repair it with odin on windows 10 detected the device but fail: Used Odin3_v3.10.7 and N7100XXUFNL1_N7100OJVFOD1_LYS
Tried on windows xp still fail same..
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin engine v(ID:3.1100)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006>
<ID:0/006> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
Tried flashing with 16gb pit file...fail now when turn on phone shows grey screen but goes into download mode....help
Click to expand...
Click to collapse
search for note 2 partition problem, there are multiple guidea on xda. keep trying with different versions of odin and roms from sammobile
yaro666 said:
search for note 2 partition problem, there are multiple guidea on xda. keep trying with different versions of odin and roms from sammobile
Click to expand...
Click to collapse
Hello, when i go into download mode i get following info:
Product Name: GT-N7100
Custom Binary Download: No
Current Binary: Samsung Official
System Status: Custom
KNOX WARRANTY VOID: 0
RP SWREV:
ALso, i tried flashing 4 files with odin, i get following log:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOTLOADER_N7100XXDLJ2_422394_REV00_user_low_ship.tar.md5 is valid.
<OSM> CODE_N7100XXDLJ2_422394_REV00_user_low_ship.tar.md5 is valid.
<OSM> MODEM_N7100XXDLJ2_422394_REV00_user_low_ship.tar.md5 is valid.
<OSM> CSC_OJV_N7100OJVDMB1_679347_REV04_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006>
<ID:0/006> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
i forgot to mention i flashed only the folllowing pit file: PIT_N7100_16GB_20121102 with Odin3_v3.10.7 after which i get grey screen when i switch on the mobile, but i can still go into download mode....pleeeeaaasssee help
Also need to inform im using windows 10 but with correct drivers and connects with odin.
Cant anyone please help me...tried different roms and firmware still same problem...
I believe the eMMC chip has failed. The same happened to my phone and the service guy said i needed a new motherboard.
Some say it may also be a corrupted bootloader, which i have had no luck in fixing.
Wish i could help
It's ok thanks for informing me at least
Love to hear if you get it up and running again
I would love that too but don't have any solutions at the moment
so i just want to tell you what all happened exactly..
my phone was kept on charging and after i unplugged it .. it did not start..
so i tried researching and find out solutions..
one possible solution i found out was to flash the STOCK FIRMWARE using ODIN..
but when i entered the download mode and i started flashing the stock firmware i am facing this issue
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7100XXUFNL1_N7100ODDFNI1_N7100DDUFND1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<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> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
need HELP ON HOW TO FIX THIS PROBLEM :| :crying:
Did you try different USB cables and USB ports?
Hi all,
Some quick background: A few days ago while I was using my S9 plugged in, my device all of a sudden froze. I did a force restart (Volume Down + Power) and from then on my phone would boot up, get to the white 'Samsung' logo then shut down and restart over and over. It never could get past the 'Samsung' logo. I tried a bunch of the solutions in Recovery Mode that I could find on the internet (wipe cache, etc.) and nothing worked so I ended up as a final resort going with the factory reset option. The same issue persisted after factory reset which lead me to this forum and giving Odin a try.
I found the correct firmware for my phone from this site which matched the firmware my device showed in recovery mode. I initially bought the phone through Rogers but switched to Bell and had them unlock it. I followed the instructions from this forum trying both the Bell and Rogers firmware's which gave me a FAIL! My phone read SECURE CHECK FAIL: system. I reset tried using Home CSC and CSC for both firmware's and neither worked. Then I downloaded the patched Odin3 v3.13.1 from here with both firmware's (after reading you may have to use it to patch unlocked phones) and got the same error. I then tried 3.14.1 and the patched version from the same forum, both giving me the exact same error. I then tried running all of the Odin programs as administrator, still the same issue. I also tried various different USB cords and ports, nothing has worked.
My phone is now stuck in Download Mode with an Error message reading 'An error has occurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC software.' but Odin still seems to be working with it so I don't think that is an issue. I tried the Smart Switch software which did not even pickup my phone like the instructions.
Below is my 'Log' from an attempt with the Bell firmware on Odin3 v3.14.1. I have gotten the same error across all Odin versions and with both firmware's. Under the 'Options' tab in Odin, Auto Reboot and F. Reset Time are selected by default. I tried deselecting one then both, as well as selecting 'Re-Partrition' and still no success
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1401)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 7172 M
<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> NAND Write Start!!
<ID:0/003> SingleDownload.
<ID:0/003> abl.elf
<ID:0/003> xbl.elf
<ID:0/003> xbl_config.elf
<ID:0/003> tz.mbn
<ID:0/003> hyp.mbn
<ID:0/003> devcfg.mbn
<ID:0/003> pmic.elf
<ID:0/003> aop.mbn
<ID:0/003> cmnlib.mbn
<ID:0/003> cmnlib64.mbn
<ID:0/003> keymaster64.mbn
<ID:0/003> qupv3fw.elf
<ID:0/003> sec.dat
<ID:0/003> apdp.mbn
<ID:0/003> msadp.mbn
<ID:0/003> bksecapp.mbn
<ID:0/003> storsec.mbn
<ID:0/003> vaultkeeper.mbn
<ID:0/003> engmode.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> vendor.img.ext4
<ID:0/003> system.img.ext4
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Sorry for the long post. Any solutions or help that can be offered would be greatly appreciated. I am new to this so is there something I am doing wrong? Please let me know if you need anymore information
SUMMARY: Phone would not stop rebooting over and over, never making it past the 'Samsung' Logo. Tried everything I could in Recovery Mode including a factory reset. Issue persisted. Tried to flash the firmware via Odin3 v3.13.1, 3.13.1 patched, 3.14.1, 3.14.1 patched, all failed in the same spot (FAIL! Auth SECURE CHECK FAIL: system). Firmware matched what my device showed in Recovery mode. Tried 2 different carriers, one that I am currently using and one that I bought my phone through. Stuck and need help.