[Q] Attempted Root Failed - AT&T, Rogers, Bell, Telus Samsung Galaxy S III

Murphy's law - It worked the umpteenth time I tried. /smackshead This thread can be deleted...
------------------------------------------
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_ATT_I747UCDLK3.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
Click to expand...
Click to collapse
I tried the root method by mrRobinson explained in the [HOWTO] [ROOT] No Tripping Flash Counter - [ATT / Bell / Telus / Rogers / Sasktel] thread, but when I went to apply the new image via Odin, after I pressed start, I got the above outcome.
It looks like someone in the how-to thread had a similar issue, but the proposed solution of "pressing the vol. up button" didn't do anything for me. So has anyone else had this issue, and do they have another way to fix it? Thanks in advance!

Related

[Q] Problems rerooting phone with Odin/CF-Auto Root

My phone was rooted but the firmware had some sort of update and now my rooted apps won't work. I tried multiple times to reroot my phone the same way I did before and Odin is giving me this information when I run it.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-t0lteatt-t0lteatt-samsungsghi317.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
Any help would be appreciated. I'd prefer to just run the stock rom if possible.
Looks like your phone is not connected
No pit mapping prompt...
Make sure you are using the factory cable...and are flashing in PDA...
I agree that Odin is not seeing your device...g
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
And download mode not recovery
Never mind. I got it. Thanks.

Very dead S4 mini GT-I9195 LTE Germany

Hey guys,
i have a serious phone damage/brick over here.
I can start the device only in download mode, which is probably not that bad.
Anything i flash through Odin is not working:
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9195XXUCOE4_I9195OXACOE1_I9195XXUCOE4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
I tried flashing the stock firmware, only the stock recovery, firmware with pit file, because of missing pit file on phone and of course Odin 1.85, 3.09 and 3.10.7
3.09 and 3.10.7 are not working at all:
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> recovery.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/011> Odin v.3 engine (ID:11)..
<ID:0/011> File analysis..
<ID:0/011> SetupConnection..
So, is there any possibility left, or the phone really dead?
Background information: phone was working the other day and then turned black. Bootlooping for a while, and then even the visual effects (samsung logo) didn't even show up. At this point, only download mode is working.
Hope someone knows a solution, or even a possibility to check if emmc is still working?

E-signature verification failed and struggling for a flashing of stockROM

I am facing typical problem and struggling for a solution. My Samsung grand 4.2.2 (build no. JDQ39.I9082XXUBNG3) is definitely going to recovery mode by various method ( by pressing keys or, adb recovery reboot ) but showing only options which is its stock rom option is giving as earlier . When phone is in normal mode ( i.e kept ON ), Odin is sensing it but flashing with any philz_touch_5.15.0-i9082.tar ,CWM-touch_i9082_chotu.tar.md5 OR, any other recovery_20120412.tar is not passed through completely and when run it in Odin shows as below and when flashed directly from device through stock ROM option with above tar file /md5 file in recovery mode it shows E-signature verification failed & does not happen any thing further. I am able to boot my device in stock recovery mode of samsung ( e 3) which is having very limited option and my device is also in working condition.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CWM-touch_i9082_chotu.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> philz_touch_5.15.0-i9082.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 1) or failed 0.
all other command adb reboot recovery, adb system etc, are working but fastboot system is not giving any return values instead it is returning to same command prompt .
ODIN IS ALSO NOT WORKING AND SENSING DEVICES WHEN DEVICE IS KEPT IN RECOVERY MODE
<ID:0/003> 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/003> Odin engine v(ID:3.1100)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CWM-touch_i9082_chotu.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> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Hello,
Did you ever find a solution for your problem?
Mohdhamm said:
Hello,
Did you ever find a solution for your problem?
Click to expand...
Click to collapse
Hi dear
I find the solution. First I was doing flashing ROM for first time for mobile and due to some confusion I was not able to differentiate between Recovery mode and Download mode in Grand -i9082 and hence I was going to recovery mode always by pressing Volume Up +Home +Power instead of going to Download mode Volume Down +Home +Power. This mistake was saved in my mind and hence I was not able to do flashing through Odin or , other way. Now this is not needed and hence problem solved.
Sent from my GT-I9082 using Tapatalk

Bricked Samsung S4 Mini (UK VODAFONE) GT-I9195I

Hi all im on my last hopes here so please help if you can, I recently tried to root my phone, unscusessfully. Phone soft bricked, so fired up odin (as a novice) and checked all boxes including NAND Erase and format partition !!
Now my phone does nothing other than boot into download mode, recovery mode appears to be non existent all i have is download mode. The phone does occasionally boot into OS but comes up with a message saying internal memory damaged, reboot doing so will erase all data... I click restore button and all it does is reboots me into download mode !!!
I've tried kies, which failes to convert into mode
ODIN which fails to do anything this is the message from the most recent attempt using advise given in this thread ... http://forum.xda-developers.com/showthread.php?t=2751224
this is the message odin gave me...
<ID:0/010> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOTLOADER_I9195XXUBML4_2340422_REV01_user_low_ship_MULTI_CERT.tar.md5 is valid.
<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> CODE_I9195XXUBML4_2340422_REV01_user_low_ship_MULTI_CERT.tar.md5 is valid.
<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> MODEM_I9195XXUBML4_2340422_REV01_user_low_ship_MULTI_CERT.tar.md5 is valid.
<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> CSC_OXA_I9195OXABML4_2340422_REV01_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/010> Odin engine v(ID:3.1005)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
really stuck with what to do with this phone, i want it working as i need to donate it to a relatve that has no phone
any help appreciated.
nice! if you have exactly! gt-i9195i why you flash rom for gt-i9195? This is different models!
i9195i has SoC Qualcomm Snapdragon 410
i9195 has SoC Qualcomm Snapdragon 400
If you realy have gt-i9195i download ROM from here : http://www.sammobile.com/firmwares/database/GT-I9195I/
and flash it via Odin

Errors with odin in Tab 3 7.0 t210r

I've been trying for a long time to unlock the bootloader of my SM-T210R, to install twrp and change the rom, but odin doesn't work at all.
I have already downloaded my rom stock, but it doesn't even install properly, here is the error:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MD5 hash value is invalid
<OSM> T210RUES0CQA1_T210RXAR0CQA1_HOME.tar.md5 is invalid.
<OSM> End...
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MD5 hash value is invalid
<OSM> T210RUES0CQA1_T210RXAR0CQA1_HOME.tar.md5 is invalid.
<OSM> End...
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T210RUEU0COI1_T210RXAR0COI1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
I've tried dozens of solutions and etc., with different versions of odin and even different recoverys, but none will. There's this guy rootjunky(.com) who has made several videos with this model, so it works, but he never mentions bootloader and does not favor.
I am not a novice in this area, I had a moto g3 osprey and exchanged direct rom and kernel on it, however motorola facilitates the unlocking of the bootloader.
An important information is that it has root king root, I don't even remember how I did it, but the system status is as custom, and the rom is from the factory.
I once used odin on it and installed the rom stock to remove a flawed root, and did not delete anything, just removed the root.
Dude I'm going crazy I don't know what to do lol
I await a salvation
I made a profile just so I could respond to this. I've been searching the internet over for 6 years - so many so close, but sm-t210r will be made a fool of by no man!! I've seriously spent 100s of hours, even acquired EXTRA tablets just so I could break them in different ways. You can't put the baby back in the mother. Even with the heroics of gr8nol - t210r's true firmware remains exit only :-(

Categories

Resources