Question about rooting my device - AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin

Ok. So I've run Odin3 v3.07 on my device, and got a successful pass. I've downloaded root checker and Titaniu Backup.
Root Checker has sat on "Please wait for Root Check to complete. System appears to be running very slowly" For about 10 minutes. Titanium Backup is stuck on trying to get root permissions.
Any Ideas?
edit:
If it helps, I have the logs from Odin here:
<ID:0/003> Added!!
<ID:0/003> Removed!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-d2att-d2uc-samsungsghi747.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Added!!
<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> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> cache.img.ext4
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/003> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)

ryno9100 said:
Ok. So I've run Odin3 v3.07 on my device, and got a successful pass. I've downloaded root checker and Titaniu Backup.
Root Checker has sat on "Please wait for Root Check to complete. System appears to be running very slowly" For about 10 minutes. Titanium Backup is stuck on trying to get root permissions.
Any Ideas?
edit:
If it helps, I have the logs from Odin here:
<ID:0/003> Added!!
<ID:0/003> Removed!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-d2att-d2uc-samsungsghi747.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Added!!
<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> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> cache.img.ext4
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/003> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Click to expand...
Click to collapse
What firmware are you running? I've never used CF auto-root..i've always done MOTOCHOPPER and it's worked great. (I'm on MDL). Also I noticed that the "<OSM> CF-Auto-Root-d2att-d2uc-samsungsghi747.tar.md5 is valid." says d2att <--- thats the Galaxy S3 not S4...not sure if that matters. (again i've never used CF Auto Root).

Questions go in q&a
Thread moved

Either you have an S3 and are posting in the wrong forums or you have an S4 and are playing around with the wrong software. That's a dangerous game.

What are you try to do? serious, if you are trying to brick your phone, you are going to if you complete this little task. From what you posted it is a att g3 image.
he's right.

Related

[Solved] Help fast please i got stuck in odin

I downloaded the new firmware from sammobile. Everything was ok but then odin got stucked in system.img and after a while it said that it had failed. What should i do now?
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9500UBUBMG1_I9500UUBBMG1_I9500UBUBMG1_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> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004> __XmitData_Read ..
<ID:0/004> XmitData Fail..
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I could find the solution myself, sorry for creating the thread i was in real panic. Aparently kies was interrupting odin, lesson learned. I should have uninstalled kies before.
Gab! said:
I downloaded the new firmware from sammobile. Everything was ok but then odin got stucked in system.img and after a while it said that it had failed. What should i do now?
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9500UBUBMG1_I9500UUBBMG1_I9500UBUBMG1_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> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004> __XmitData_Read ..
<ID:0/004> XmitData Fail..
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Since Its done in the thread make it solved in the bracket it will help others too
.
did you check the md5 checksum on that? perhaps it's a bad download..
also, you should tick debug

[Q] Trying to root S4

So i've tried a few ways to root my galaxy s4 running 4.4.2 but when i try it will say flash failed or in odin 3 it says
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-jflte-jfltexx-gti9505.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> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Any ideas what to do from here?
darksmite653 said:
Any ideas what to do from here?
Click to expand...
Click to collapse
Yeah. Go to S4 forum and ask there because your problem has nothing to do with Omni.
chasmodo said:
Yeah. Go to S4 forum and ask there because your problem has nothing to do with Omni.
Click to expand...
Click to collapse
ok sorry, i couldent find it at the time, its my first post
darksmite653 said:
So i've tried a few ways to root my galaxy s4 running 4.4.2 but when i try it will say flash failed or in odin 3 it says
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-jflte-jfltexx-gti9505.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> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Any ideas what to do from here?
Click to expand...
Click to collapse
By doing this method, you run the risk of tripping knox 0x1 which will definitely void your warranty. If you want to root without triggering it, try towelroot.

NOTE 4 SM-G910S bootloop after attempt to use CF-autoroot

Hello, my phone stocked on bootloop and i try to flash it to stock firmware and odin fails
<ID:0/004> 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/004> Odin engine v(ID:3.1100)..
<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> sboot.bin
<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 also try to factory reset it and it is still in bootloop
Please someone help me. Thanks a lot
louellgat said:
Hello, my phone stocked on bootloop and i try to flash it to stock firmware and odin fails
<ID:0/004> 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/004> Odin engine v(ID:3.1100)..
<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> sboot.bin
<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 also try to factory reset it and it is still in bootloop
Please someone help me. Thanks a lot
Click to expand...
Click to collapse
Hi,
I have reported this thread to be moved to the right Q & A section where you might be able to get help quickly.
Good luck.

Odin fails to root after recovery.img

I've been searching for 3 days now and I haven't seen anyone with the same problem. I've tried everything I can think of. I have disabled reactivation lock. Every time I see someone with the same error the problem is they need to disable reactivation lock and it always works.
Here's the error I get:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-kltevzw-kltevzw-smg900v.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1005)..
<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> recovery.img
<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)
<ID:0/004> Removed!!
I Have tried every single USB port on my computer, and it still doesn't work. I have NO idea what to do!
(I have SM-G900V and I'm using CF-Auto-root)
SM-G900V has a locked bootloader by default.
It does not accept custom recovery.
have NO idea what to do!
Click to expand...
Click to collapse
Have a look at the section devoted to SM-G900V.

Tab S2 Odin reset problem.....

I have a Tab S2 SM-T813 that Im trying to reset it keeps giving me an error.
I tried the original cable and many different cables still gives an error
please help!
<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/004> Added!!
<ID:0/004> Odin engine v(ID:3.1101)..
<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> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> __XmitData_Write
<ID:0/004> Complete (Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
wickedblue2007 said:
I have a Tab S2 SM-T813 that Im trying to reset it keeps giving me an error.
I tried the original cable and many different cables still gives an error
please help!
<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/004> Added!!
<ID:0/004> Odin engine v(ID:3.1101)..
<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> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> __XmitData_Write
<ID:0/004> Complete (Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
Click to expand...
Click to collapse
That error is almost always a bad cable or one that is too long or a bad port.
It might also be worth redownloading the firmware.
If you still have issues then I suggest rooting and using Flashfire to install the firmware.

Categories

Resources