Database Users

[RECOVERY] ClockworkMod Touch 6.0.2.3 flashable zip (update 2012-12-19)

Hey Guys
I am sharing the latest CWM recovery images; CWM 6.0.2.3.
To be straight, I used Koush's Recovery Builder to build these
latest recovery images in touch.
And so I do not take any credit, all of it to Koush. Also, I didn't
publish a thread for this in development section since I didn't
perform any development on this.
Download link:
ClockwordMod Touch 6.0.2.3-p3100
ClockwordMod Touch 6.0.2.3-p3110
ClockwordMod Touch 6.0.2.3-p3113
How to build on your own?
Visit the Recovery Builder
Click on the "Existing Devices" tab.
Now under the Existing Devices dropdown, select "p3100" or your device.
Tick "Touch Recovery" option if you desire for the touch variant, otherwise do not touch it.
Now click on the blue colored "Build" tab.
The page will then prompt you with a reference build ID, take note of it.
Now continue to build server.
Look for the corresponding build ID.
Once its done, click on it.
You can now download your "recovery.img" build.
How to flash?
Flash through CWM recovery.
Updated the OP with the newer version and a flashable zip.
Hope you enjoy it.
If You like just hit the thanks button.

I did instal on my tablet and worked without any problem.
I just want to say I´m not responsible for any brick, damage or anything else that happens to your tablet.

i need to sign in to the site to download right ?
any other testers here ?
thanks a lot for sharing...have you wiped and flashed files from it ?

You don't need to wipe. You flash it with Odin as another cwm recovery.
After installed I flashed some goodies and made a backup and worked perfectly.
If someone else test it will be great if and some feedback for other people.
Sent from my GT-I9300 using xda premium

And I think 4 shared need to subscribe
Sent from my GT-I9300 using xda premium

I went thru the steps for the p3113 (my version of the 7" tab 2) and it outputs a recovery.img file after about 5 minutes to build it, how do I make that an Odin flashable .tar like you have?
I have attached the recovery.img to this thread for the p3113 if it's simpler for you to do it then to walk me through it, any help would be appreciated.

image file can be flashed with mobile odin i read
thanks for second link
but havent flashed
will give yellow triangle ?

rraaka said:
image file can be flashed with mobile odin i read
thanks for second link
but havent flashed
will give yellow triangle ?
Click to expand...
Click to collapse
I've not rooted yet, I'm just getting setup for it and wanted the latest stuff to do it with.

CWM TOUCH 6.0.1.9 for P3110
https://hotfile.com/dl/183312759/30a80ea/recovery.img.html
Tested: works well.
Flash with Mobile Odin or Odin
@Marcelo.tti: thank You very much to make this possible

daniel644 said:
I went thru the steps for the p3113 (my version of the 7" tab 2) and it outputs a recovery.img file after about 5 minutes to build it, how do I make that an Odin flashable .tar like you have?
I have attached the recovery.img to this thread for the p3113 if it's simpler for you to do it then to walk me through it, any help would be appreciated.
Click to expand...
Click to collapse
I put the file link in the OP. Thanks to build the image file
rraaka said:
image file can be flashed with mobile odin i read
thanks for second link
but havent flashed
will give yellow triangle ?
Click to expand...
Click to collapse
No It won't.
I did an update to the thread with link for .tar images files to p3110 and p3113. Thanks to @daniel644 to build the image file for p3113 and @monfro to build the image file for p3110.
Here is a guide to build a .tar file to flash with odin.
You have to use the commands below with Linux. Just make sure you are in the correct folder to make the commands. It's good to put the file in the personal folder as the terminal always open in this folder.
$ tar -H ustar -c recovery.img > recovery.tar
$ md5sum -t recovery.tar >> recovery.tar
$ mv recovery.tar recovery.tar.md5

I have downloaded the 3113 version twice. Odin always says md5 does not match and then fails the flash. Any ideas?
Here is the output
<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> MD5 hash value is invalid
<OSM> ClockWordMod_touch-6.0.1.9-p3113.tar.md5 is invalid.
<OSM> End...

d11dog11 said:
I have downloaded the 3113 version twice. Odin always says md5 does not match and then fails the flash. Any ideas?
Here is the output
<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> MD5 hash value is invalid
<OSM> ClockWordMod_touch-6.0.1.9-p3113.tar.md5 is invalid.
<OSM> End...
Click to expand...
Click to collapse
remove the .md5 off the end of the file name, thats what I've done in the past in similar situations.

daniel644 said:
remove the .md5 off the end of the file name, thats what I've done in the past in similar situations.
Click to expand...
Click to collapse
Worked perfectly. Thanks!!
Sent from my Galaxy Nexus using Tapatalk 2

Finally decided to flash CWM and Root and ROM all in one night, wanted to see how long the stock ROM on a full charge would last using it as strictly a music player for when driving (22 DAYS for the record).
Honestly, as much as I like being able to TOUCH what I want to do it's just ugly and you have to scroll to see anything, but here is another user confirming the build for the P3113 works perfectly.
Now running this ROM as my first Custom on this device http://forum.xda-developers.com/showthread.php?t=2028663
Now all I need is for Supercurio to release his Voodoo Sound with Tab 2 support, he said when he releases the one for the WM1811 in the S3 it will also do our Tab 2's, OH YEAH!!!

Op Updated with the newer version.
Tested for p3100 end works good with no problem with the flashable zip.
If someone can test the other zips and say it's ok I'll be really grateful.

You can also get this CMW Recovery by downloading ROM Manager and let the app update it by itself.

Can You update the ClockworkMod Touch Recovery for p3100, p3110, p3113 to the version 6.0.2.7 ???

RrOoSsSsOo said:
Can You update the ClockworkMod Touch Recovery for p3100, p3110, p3113 to the version 6.0.2.7 ???
Click to expand...
Click to collapse
p3100 : http://forum.xda-developers.com/showthread.php?t=2064871
p3113 : http://forum.xda-developers.com/showthread.php?t=2073854
if you need 3110 then just build the recovery.img using the link in the OP and use winrar to "insert" that recovery.img into the zip replacing the one in the zip, thats how the p3113 builds where made.

I have a problem with flashing. I want to flash AOKP, but first I need CWM and root (obviously). I set USB debug settings. I'm using Odin, and I flash CWM, Odin says PASS and everything is green. But when I restart and boot into recovery the stock rcovery shows up. I'm on stock JB rom btw.
Other methods say that I should use Rom Manager which needs root which needs CWM in the first place.
I'm baffled here, what am I doing wrong?

sterby81 said:
I have a problem with flashing. I want to flash AOKP, but first I need CWM and root (obviously). I set USB debug settings. I'm using Odin, and I flash CWM, Odin says PASS and everything is green. But when I restart and boot into recovery the stock rcovery shows up. I'm on stock JB rom btw.
Other methods say that I should use Rom Manager which needs root which needs CWM in the first place.
I'm baffled here, what am I doing wrong?
Click to expand...
Click to collapse
your VERY FIRST boot up that you do has to be straight into CWM after using Odin to flash the .tar, which is why your supposed to uncheck auto reboot and f reset time in Odin, if your tablet boots up it will automatically revert back to stock recovery.

[Q] Custom recovery on Galaxy s4 AT&T

Hello. I have a rooted AT&T Samsung Galaxy s4 running 4.2.2. I am trying to flash cyanogenmod11 and have had no luck even loading a recovery. I first tried to flash twrp 2.6.3.1 from GooManager. It said that it flashed successfully, but when I tried to boot into recovery, it looked like it was in download mode and I got the message:
Could not do normal boot.
ODIN MODE
PRODUCT NAME: SGH-I337
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
CSB-CONFIG-LISB: 0X30
WRITE PROTECTION: Enable
The only way I can get out of this mode is by pulling the battery, going into download mode, then pressing cancel. I tried the same thing with ROMManager using both CWM and TWRP. Same problem.
Does anyone have this problem or know how to fix it?
Thanks!

You're kidding right? Do some reading.

I have read up on this, but there's nothing I can find that works. Everywhere just tells me how to get it into the OS, not how I can load a ROM.
jd1639 said:
You're kidding right? Do some reading.
Click to expand...
Click to collapse

gradymcd said:
I have read up on this, but there's nothing I can find that works. Everywhere just tells me how to get it into the OS, not how I can load a ROM.
Click to expand...
Click to collapse
Look for mf3 and safestrap

gradymcd said:
Hello. I have a rooted AT&T Samsung Galaxy s4 running 4.2.2. I am trying to flash cyanogenmod11 and have had no luck even loading a recovery. I first tried to flash twrp 2.6.3.1 from GooManager. It said that it flashed successfully, but when I tried to boot into recovery, it looked like it was in download mode and I got the message:
Could not do normal boot.
ODIN MODE
PRODUCT NAME: SGH-I337
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
CSB-CONFIG-LISB: 0X30
WRITE PROTECTION: Enable
The only way I can get out of this mode is by pulling the battery, going into download mode, then pressing cancel. I tried the same thing with ROMManager using both CWM and TWRP. Same problem.
Does anyone have this problem or know how to fix it?
Thanks!
Click to expand...
Click to collapse
Where are all these noobs coming from just having phones that are already magically rooted and just automatically think they can flash a custom recovery. Great you just lost your stock recovery..... But no fear, search mf3 md5 files. flash it fresh through odin 1.75 and then root not using a one click. You don't deserve root if you can't format a card and run a few simple terminal commands.... Just my opinion. Oh is your gs4 red also....?
---------- Post added at 05:20 PM ---------- Previous post was at 05:11 PM ----------
Here is a little tut I wrote some time ago. Providing everything for you besides the main files you'll need so you'll learn how to search.
You should realy read.... All of us on MF3 know that !!... That was one of the fist ways to boot back up. Safe strap is going to be a savior for you.... Basically this has been discussed a million times..... If you are on MF3 you cannot downgrade you can only upgrade or stay on MF3, If you want 4.3 sooooo bad I will link it for you. But I suggest staying patient. There is nothing really that improved over 4.2.2. So I would advise you not to upgrade but I will post the links and tell you how to do it. One if you were smart you would have made a nandroid backup thru SS and then when you boot into that you stay on the stock rom slot. Hit then go in and write your backup just the system folder.... So you won't lose all of your data. Now if you didn't make a nandroid backup. Then you can try flashing the stock recovery and fixing the permissions thru safe strap..... IF that doesn't work well you are just up the creek.....
HAHAHAHA. JK Get odin and get the MF3 Tar.MD5 files But your phone manually into odin mode and Go back to stock MF3. Seriously read, read, read. I will make it real easy for you this time. By posting links but you are just asking for it. So first grab these files: https://mega.co.nz/#!WEEzSA7Z!aB46731_AwM7P83eMdDlmFYd1hUZfFBcQAZjc1X7wAE These are the stock MF3 files that were contributed to the community by Shockndrop: http://forum.xda-developers.com/showthread.php?t=2502003
Now grab Odin, I prefer this one: ODIN 1.85 http://forum.xda-developers.com/showthread.php?t=1262272
Now put the MD5 files in their proper places in odin and and hook your phone up with a Good **** Solid Universal Serial Bus Cable: Like pitured here:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Put her down into a coma AKA, ODIN Recovery mode manualy by holding power, home, and volume down. Then when prompt after the warning volume up to continue. Flash with Odin to restore to stock MF3. Brand Spaking new!!!!
Use your favorite root Method, New root method is the only one we support here on XDA, Which involves an SD Card,and the Terminal from the Play store. Or if you want the fast and dirty way because you are lazy do the Kingo root, I don't indorse it, but I have yet to hear anything negative about it, other than speculation. Links: http://www.kingoapp.com/android-root/download.htm - one click method Easy.
Old proper way: Quoting Jortex "HOWTO:
Use a card reader to format the micro SD card to exFAT (FAT32 or other formats does not work) in Windows. I haven't tried Linux or MacOS X, so they may not work.
Download the attached file (Root_for_ATTSG4_FM3.rar) http://forum.xda-developers.com/attachment.php?attachmentid=2165629&d=1375669716 and extract it into the root of your EXTERNAL microSD card using the card reader in Windows. (You can do the extraction using WinRAR, http://www.rarlab.com/download.htm or 7-zip, http://www.7-zip.org/download.html ).
Put the SD card back to the phone and download the Android Terminal Emulator app.
Open the Terminal Emulator app and run below 3 commands:
Code:
cd /mnt/extSdCard
./pwn
./script.sh
Then, open SuperSU and check everything looks good.
Then open a root app and it should be working properly.
Reboot your device once to confirm root is still working after reboot.
Come back to the post and press the THANKS button
Notes:
I uploaded a screenshot from the Terminal screen where the instructions are entered. Yours should be the same except you don't need to enter the "ls -l" command. It's just to show what files I have on the SD card. Ignore LOST.DIR directory.
Remove any SuperSU apps from your phone before following the above steps. script.sh installs it automatically.
You can use adb shell instead of a terminal app which is more convenient but requires Android SDK. Follow these steps only if you are about to use adb:
Download and install all Samsung Galaxy S 4 drivers from here: http://www.samsung.com/us/support/owners/product/SGH-I337ZWAATT#
Activate Developer options -> USB Debugging mode. To have the phone show the Developer options, go to Settings -> More -> About device. Tap on "Build number" 6 times.
You have to use an external SD card. No other alternative have been found yet. Using the device storage, i.e. /mnt/sdcard, or /data/local/tmp, DOES NOT work.
Warning (suggested by rushi.1986): "We have root for MF3 but we neither have a working recovery, nor an ODIN back to stock package. Be very careful what you do with your root. At this point, there is no way to recover even from a soft brick. (unless you know exactly what caused the soft brick and can correct it using adb)"
For those who do not know how to format an SD card on Windows (thanks to jee'sgalaxy):
Insert the micro SD into the computer (may have to use a reader or a micro SD adapter).
Go to "My Computer".
Right click on your SD card that showed up.
Click Format.
Choose exFAT as the format.
Click "OK".
Don't forget to press the THANKS button.
Credits:
***Exploit adapted for AT&T by Jortex***
***Original Guide by Open1Your1Eyes0 for Verizon Galaxy S 4***
***Original Exploit by DooMLoRD***
Next install your only way as of now to run custom roms period in your current situation and you should be incredibly grateful instead of saying that you want 4.3 soooooo bad....... really not tooo many benefits at all. Now 4.4 KittyKit lol is a different story..... So grab the latest and greatest version of safestrap from here: http://forum.xda-developers.com/devdb/project/dl/?id=1814&task=get
After Flashing Any Compatable Rom flash these every time Link: http://forum.xda-developers.com/devdb/project/dl/?id=508
They are the MF3 modules you will need them for wifi to work.
Transfer to sd card install just as you would a regular unknown source APK File..... Tick that in settings Security tab. Also hit your build number 20 times to unlock developer options and always have usb debugging on.
Now boot into safe-strap and dump a nandroid backup and you will be good to go. All thanks to the HashMan aka HashCode, And his sexifing SS. Okay now that you have a backup do anything of your hearts content. Just don't be fooling around with the bootloaders code.... this can really turn your cell phone into a paper weight.
Now here is a list of known compatable roms with SS:
Confirmed working ROMs Thanks to graydiggy http://forum.xda-developers.com/showthread.php?t=2428254
Google Play Edition 4.2.2
http://forum.xda-developers.com/showthread.php?t=2356276
http://forum.xda-developers.com/showthread.php?t=2341376
Deadly Venom
SHOStock
Darth Stalker
Graviton (Installs fine for some, will not install for others)
Goldeneye (May have issues)
Wicked ROM (T-Mobile) Input correct APN and change network mode to Auto LTE/GSM Will most likely lose root.
All Infamous TW Roms should work
Input correct APN settings for non AT&T ROMs (ie i9505 ROMs) to get LTE
Omega ROM i9505
Echo ROM i9505
Vision X i9505
BoBCaTROM i9505 (May not need to change APN)
Hyperdrive ROM. (May not be able to send SMS while on LTE)
Grab one create a rom slot and flash to your hearts content.
As for the 4.3 Odin files...... I think you can find them yourself it would be ignorant for me to post them for you.

You are right. I am a newb at this. My last phone was a Motorola Triumph, and I had no problems flashing ROMs on that. So I would flash the md5 file (d-h.st/AuY) through odin 1.75 and then flash CWM? My phone is white. Didn't even know they made it in red.
Thank!
JohnMonsour said:
Where are all these noobs coming from just having phones that are already magically rooted and just automatically think they can flash a custom recovery. Great you just lost your stock recovery..... But no fear, search mf3 md5 files. flash it fresh through odin 1.75 and then root not using a one click. You don't deserve root if you can't format a card and run a few simple terminal commands.... Just my opinion. Oh is your gs4 red also....?
Click to expand...
Click to collapse

gradymcd said:
You are right. I am a newb at this. My last phone was a Motorola Triumph, and I had no problems flashing ROMs on that. So I would flash the md5 file (d-h.st/AuY) through odin 1.75 and then flash CWM? My phone is white. Didn't even know they made it in red.
Thank!
Click to expand...
Click to collapse
I was just giving you a hard time... LOL. That is why we are here is to help not bring you down. I remember my first line of code.... Boy! jk. Any questions. v 1.85 works best for me. But just make sure you have a very good usb cable and strong connection. I have bricked a phone with Odin on MF3.

Are the only supported ROMs the ones listed, because I want to flash the cm11 nightly for KitKat?
JohnMonsour said:
Where are all these noobs coming from just having phones that are already magically rooted and just automatically think they can flash a custom recovery. Great you just lost your stock recovery..... But no fear, search mf3 md5 files. flash it fresh through odin 1.75 and then root not using a one click. You don't deserve root if you can't format a card and run a few simple terminal commands.... Just my opinion. Oh is your gs4 red also....?
---------- Post added at 05:20 PM ---------- Previous post was at 05:11 PM ----------
Here is a little tut I wrote some time ago. Providing everything for you besides the main files you'll need so you'll learn how to search.
You should realy read.... All of us on MF3 know that !!... That was one of the fist ways to boot back up. Safe strap is going to be a savior for you.... Basically this has been discussed a million times..... If you are on MF3 you cannot downgrade you can only upgrade or stay on MF3, If you want 4.3 sooooo bad I will link it for you. But I suggest staying patient. There is nothing really that improved over 4.2.2. So I would advise you not to upgrade but I will post the links and tell you how to do it. One if you were smart you would have made a nandroid backup thru SS and then when you boot into that you stay on the stock rom slot. Hit then go in and write your backup just the system folder.... So you won't lose all of your data. Now if you didn't make a nandroid backup. Then you can try flashing the stock recovery and fixing the permissions thru safe strap..... IF that doesn't work well you are just up the creek.....
HAHAHAHA. JK Get odin and get the MF3 Tar.MD5 files But your phone manually into odin mode and Go back to stock MF3. Seriously read, read, read. I will make it real easy for you this time. By posting links but you are just asking for it. So first grab these files: https://mega.co.nz/#!WEEzSA7Z!aB46731_AwM7P83eMdDlmFYd1hUZfFBcQAZjc1X7wAE These are the stock MF3 files that were contributed to the community by Shockndrop: http://forum.xda-developers.com/showthread.php?t=2502003
Now grab Odin, I prefer this one: ODIN 1.85 http://forum.xda-developers.com/showthread.php?t=1262272
Now put the MD5 files in their proper places in odin and and hook your phone up with a Good **** Solid Universal Serial Bus Cable: Like pitured here:
Put her down into a coma AKA, ODIN Recovery mode manualy by holding power, home, and volume down. Then when prompt after the warning volume up to continue. Flash with Odin to restore to stock MF3. Brand Spaking new!!!!
Use your favorite root Method, New root method is the only one we support here on XDA, Which involves an SD Card,and the Terminal from the Play store. Or if you want the fast and dirty way because you are lazy do the Kingo root, I don't indorse it, but I have yet to hear anything negative about it, other than speculation. Links: http://www.kingoapp.com/android-root/download.htm - one click method Easy.
Old proper way: Quoting Jortex "HOWTO:
Use a card reader to format the micro SD card to exFAT (FAT32 or other formats does not work) in Windows. I haven't tried Linux or MacOS X, so they may not work.
Download the attached file (Root_for_ATTSG4_FM3.rar) http://forum.xda-developers.com/attachment.php?attachmentid=2165629&d=1375669716 and extract it into the root of your EXTERNAL microSD card using the card reader in Windows. (You can do the extraction using WinRAR, http://www.rarlab.com/download.htm or 7-zip, http://www.7-zip.org/download.html ).
Put the SD card back to the phone and download the Android Terminal Emulator app.
Open the Terminal Emulator app and run below 3 commands:
Code:
cd /mnt/extSdCard
./pwn
./script.sh
Then, open SuperSU and check everything looks good.
Then open a root app and it should be working properly.
Reboot your device once to confirm root is still working after reboot.
Come back to the post and press the THANKS button
Notes:
I uploaded a screenshot from the Terminal screen where the instructions are entered. Yours should be the same except you don't need to enter the "ls -l" command. It's just to show what files I have on the SD card. Ignore LOST.DIR directory.
Remove any SuperSU apps from your phone before following the above steps. script.sh installs it automatically.
You can use adb shell instead of a terminal app which is more convenient but requires Android SDK. Follow these steps only if you are about to use adb:
Download and install all Samsung Galaxy S 4 drivers from here: http://www.samsung.com/us/support/owners/product/SGH-I337ZWAATT#
Activate Developer options -> USB Debugging mode. To have the phone show the Developer options, go to Settings -> More -> About device. Tap on "Build number" 6 times.
You have to use an external SD card. No other alternative have been found yet. Using the device storage, i.e. /mnt/sdcard, or /data/local/tmp, DOES NOT work.
Warning (suggested by rushi.1986): "We have root for MF3 but we neither have a working recovery, nor an ODIN back to stock package. Be very careful what you do with your root. At this point, there is no way to recover even from a soft brick. (unless you know exactly what caused the soft brick and can correct it using adb)"
For those who do not know how to format an SD card on Windows (thanks to jee'sgalaxy):
Insert the micro SD into the computer (may have to use a reader or a micro SD adapter).
Go to "My Computer".
Right click on your SD card that showed up.
Click Format.
Choose exFAT as the format.
Click "OK".
Don't forget to press the THANKS button.
Credits:
***Exploit adapted for AT&T by Jortex***
***Original Guide by Open1Your1Eyes0 for Verizon Galaxy S 4***
***Original Exploit by DooMLoRD***
Next install your only way as of now to run custom roms period in your current situation and you should be incredibly grateful instead of saying that you want 4.3 soooooo bad....... really not tooo many benefits at all. Now 4.4 KittyKit lol is a different story..... So grab the latest and greatest version of safestrap from here: http://forum.xda-developers.com/devdb/project/dl/?id=1814&task=get
After Flashing Any Compatable Rom flash these every time Link: http://forum.xda-developers.com/devdb/project/dl/?id=508
They are the MF3 modules you will need them for wifi to work.
Transfer to sd card install just as you would a regular unknown source APK File..... Tick that in settings Security tab. Also hit your build number 20 times to unlock developer options and always have usb debugging on.
Now boot into safe-strap and dump a nandroid backup and you will be good to go. All thanks to the HashMan aka HashCode, And his sexifing SS. Okay now that you have a backup do anything of your hearts content. Just don't be fooling around with the bootloaders code.... this can really turn your cell phone into a paper weight.
Now here is a list of known compatable roms with SS:
Confirmed working ROMs Thanks to graydiggy http://forum.xda-developers.com/showthread.php?t=2428254
Google Play Edition 4.2.2
http://forum.xda-developers.com/showthread.php?t=2356276
http://forum.xda-developers.com/showthread.php?t=2341376
Deadly Venom
SHOStock
Darth Stalker
Graviton (Installs fine for some, will not install for others)
Goldeneye (May have issues)
Wicked ROM (T-Mobile) Input correct APN and change network mode to Auto LTE/GSM Will most likely lose root.
All Infamous TW Roms should work
Input correct APN settings for non AT&T ROMs (ie i9505 ROMs) to get LTE
Omega ROM i9505
Echo ROM i9505
Vision X i9505
BoBCaTROM i9505 (May not need to change APN)
Hyperdrive ROM. (May not be able to send SMS while on LTE)
Grab one create a rom slot and flash to your hearts content.
As for the 4.3 Odin files...... I think you can find them yourself it would be ignorant for me to post them for you.
Click to expand...
Click to collapse

gradymcd said:
Are the only supported ROMs the ones listed, because I want to flash the cm11 nightly for KitKat?
Click to expand...
Click to collapse
Only SafeStrap recovery works with MF3 4.2.2. Currently there is a test going on for 4.3 MK2. It only flashes 4.2.2 if on MF3 or 4.3 on MK2. Only Touchwiz roms can be flashed although certain GE roms also do work.
You wont be able to flash kitkat roms or any aosp roms sadly.

Kaze105 said:
Only SafeStrap recovery works with MF3 4.2.2. Currently there is a test going on for 4.3 MK2. It only flashes 4.2.2 if on MF3 or 4.3 on MK2. Only Touchwiz roms can be flashed although certain GE roms also do work.
You wont be able to flash kitkat roms or any aosp roms sadly.
Click to expand...
Click to collapse
The closest you will get to the pure vanilla android we all have become accustomed to is the GPE roms. Just Usb does't work. Personally my fine was on hyperdrive. Originally a Verizon rom but made compatible to all other variants. It is an awesome rom. Anything with 4.2.2. will work so just look for those in the link's in the dev section on the titles of roms. Make sure you flash those modules after. Good luck.

cannot load the MF3 modules
Hi all,
I have been trying to go through the whole process multiple times only to be blocked when trying to load the MF3 kernel modules.
- I have a AT&T MF3 S4
- installed SS 3.65
- tried a couple ROMS, ge4.2.2clean-20130907, INTIKA.LOCKY.MF3.MH8.ST.DEODEX, I9505_-_Google_Edition_Final-v1_by_Jamal2367
- all boot, even if only after a couple minutes
- LTE 4g works
- Bluetooth works
- installed the MF3 modules. I even checked that they are identical from the modules used in the Stock ROM.
- None of the modules can load within the custom ROMS. To verify, I tried to insmod manually, I get this error :
insmod: init_module 'dhd.ko' failed (Exec format error)
Looking at the messages :
4>[ 3120.892608] TIMA: lkmauth--launch the tzapp to check kernel module; module len is 620372
<3>[ 3120.898956] QSEECOM: __qseecom_get_fw_size: error with request_firmware
<3>[ 3120.899200] TIMA: lkmauth--cannot get tzapp handle from kernel.
This happens with any modules, not only the dhd wifi driver. I verified that I could rmmod/insmod everything fine when running the stock ROM.
I researched this as much as I could. There are comments about non-signed modules, but here, the modules are the exact ones from Samsung stock image.
Has anyone seen something like this ?
Since it seems that many people are successful with this, is there something that I am missing ?
Thanks,
Philippe

pmoutarlier said:
Hi all,
I have been trying to go through the whole process multiple times only to be blocked when trying to load the MF3 kernel modules.
- I have a AT&T MF3 S4
- installed SS 3.65
- tried a couple ROMS, ge4.2.2clean-20130907, INTIKA.LOCKY.MF3.MH8.ST.DEODEX, I9505_-_Google_Edition_Final-v1_by_Jamal2367
- all boot, even if only after a couple minutes
- LTE 4g works
- Bluetooth works
- installed the MF3 modules. I even checked that they are identical from the modules used in the Stock ROM.
- None of the modules can load within the custom ROMS. To verify, I tried to insmod manually, I get this error :
insmod: init_module 'dhd.ko' failed (Exec format error)
Looking at the messages :
4>[ 3120.892608] TIMA: lkmauth--launch the tzapp to check kernel module; module len is 620372
<3>[ 3120.898956] QSEECOM: __qseecom_get_fw_size: error with request_firmware
<3>[ 3120.899200] TIMA: lkmauth--cannot get tzapp handle from kernel.
This happens with any modules, not only the dhd wifi driver. I verified that I could rmmod/insmod everything fine when running the stock ROM.
I researched this as much as I could. There are comments about non-signed modules, but here, the modules are the exact ones from Samsung stock image.
Has anyone seen something like this ?
Since it seems that many people are successful with this, is there something that I am missing ?
Thanks,
Philippe
Click to expand...
Click to collapse
Try downloading the modules again. I've never had issues with any of those ROMs. You got the module zip from the Safestrap OP?

DeadlySin9 said:
Try downloading the modules again. I've never had issues with any of those ROMs. You got the module zip from the Safestrap OP?
Click to expand...
Click to collapse
Just re-downloaded it from here :
http://forum.xda-developers.com/devdb/project/?id=680#downloads
still failing with the same message .. weird since it seems to work fine with everyone else ..
Do we need to restore the original kernel as well (boot.img from stock) ?
Thanks,
Philippe

pmoutarlier said:
Just re-downloaded it from here :
http://forum.xda-developers.com/devdb/project/?id=680#downloads
still failing with the same message .. weird since it seems to work fine with everyone else ..
Do we need to restore the original kernel as well (boot.img from stock) ?
Thanks,
Philippe
Click to expand...
Click to collapse
When using safestrap it never touches the kernel, so your stock should be in place and you can't restore it except by reflashing the whole MF3 system, which you may have to do. I'm not sure why it would be blocked. You flashed them right after installing the ROM and before booting into the ROM right?

My GS4 I337 keep getting stuck on download mode when I am using Odin 3.07.. also tried 1.85
On phone:
in download mode it says:
ODIN MODE
PRODUCT NAME: SGH-I337
CURRENT BINARY: SAMSUNG OFFICIAL
SYSTEM STATUS: CUSTOM
KNOX KERNEL LOCK: 0X0
KNOX WARRANTY VOID: 0X1
CSB-CONFIG-LSB: 0X30
WRITE PROTECTION: ENABLE
eMMC BURST MODE: ENABLE
START [224,1440]
SW REV. CHECK FAIL : FUSED : 4 , BUNARY : 2
ON ODIN:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOTLOADER_I337UCUAMF3_812098_REV06_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> PLATFORM_I337UCUAMF3_812098_REV06_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_I337UCUAMF3_812098_REV06_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_ATT_I337ATTAMF3_812098_REV06_user_low_ship_MULTI_CERT.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> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
plz help..

Just to confirm, you were on MF3 instead of MK2?

Kaze105 said:
Just to confirm, you were on MF3 instead of MK2?
Click to expand...
Click to collapse
Honestly I dont know. I am downloading the MK2 at the moment to try it again. I been trying with MF3.
I had 4.2.2 then att OTA update changed it to 4.3
---------- Post added at 11:05 AM ---------- Previous post was at 10:17 AM ----------
c5downlow said:
Honestly I dont know. I am downloading the MK2 at the moment to try it again. I been trying with MF3.
I had 4.2.2 then att OTA update changed it to 4.3
Click to expand...
Click to collapse
UPDATE: MK2 is working so far.. I am doing it as we speak.
yay it worked!!!!

Difficult Soft Brick - Need Urgent Help

I think it's a soft brick because I can get into download mode. Flashing anything in Odin fails. I posted this in xBeerDroidx's All In One Guide:
I went through the entire process of
1. returning to stock MF3 (I was using SafeStrap 3.65 and Hyperdrive 10.1 successfully...wanted to try the MK2 > SafeRoot > SafeStrap 3.71 > HD Rls 12)
2. Ran Update.zip successfully, got to MK2
3. Ran SafeRoot - successfully rooted phone
4. Installed SafeStrap 3.71 APK - no issues
5. From SS Recovery, installed HD Rls12 went OK but had an issue with the reboot menu
6. Installed the AT&T compatibility pack, still had issues with reboot menu, so I thought I'd re-run the HD RLS12 install
7. Went into SS Recovery, did a wipe but this time I did a system wipe...this is where I FU'd, I think
8. Still in SS recovery, I then hit the reboot button...my OS was gone so it stayed on the Samsung screen indefinitely.
I can still get into Download mode, but when trying to reflash the 4 MF3 files via Odin, I get a fail every time. I've tried to flash just the Platform, or all but the bootloader, (thinking this was where my write error occurred), and it seemed to go OK but still failed.
I'm stuck with a phone that can enter Download mode but that's it.
And was advised to get the .PIT file for my device. I found what was said to be the proper .PIT file for my build (MF3). I tried flashing the .PIT alone, and it seemed to do something, then reset my phone, but when the phone re-booted, it had a yellow triangle and a statement about unauthorized software. It would go no further. So I added the .PIT file to Odin, along with the other 4 MD5 files, and I get these results every time:
<ID:0/010> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOTLOADER_I337UCUAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> PLATFORM_I337UCUAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> MODEM_I337UCUAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> CSC_ATT_I337ATTAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> sbl1.mbn
<ID:0/010> NAND Write Start!!
<ID:0/010> sbl2.mbn
<ID:0/010> sbl3.mbn
<ID:0/010> rpm.mbn
<ID:0/010> aboot.mbn
<ID:0/010>
<ID:0/010> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Can anyone help me?

JohnnyMac999 said:
Wanted to try the MK2 > SafeRoot > SafeStrap 3.71 > HD Rls 12)
Click to expand...
Click to collapse
This is where you went wrong... once you update to MK2 it is IMPOSSIBLE to downgrade to a lower firmware due to hardware related issues caused by the MF3 update. Go back the this thread and read how to go use your semi-bricked MF3 device to upgrade back to stock MK2. As for running stock MF3 your never again be able to unless the bootloader is unlocked at some point. This was stated multiple times in many threads around the forum... please take your time to read and search before jumping into things. It can be assumed with any future S4 upgrades that you are committing to that update with no chance of returning to a previous one.

You are the man! I've already flashed the MJ6 recovery successfully, and am in the process of downloading the MF3 emergency files. Hopefully, before too long, I'll have my S4 back, humming away on Hyperdrive RLS 12!! As a side note, I see you're on GPE 4.2.2. When I first loaded SafeStrap and was able to load ROMs, I tried using a GPE ROM and was running into nothing but trouble. Hyperdrive 10.1 ended up being my daily driver until I caused this mess. Did you have to do anything special to get the GPE ROM working properly?

JohnnyMac999 said:
You are the man! I've already flashed the MJ6 recovery successfully, and am in the process of downloading the MF3 emergency files. Hopefully, before too long, I'll have my S4 back, humming away on Hyperdrive RLS 12!! As a side note, I see you're on GPE 4.2.2. When I first loaded SafeStrap and was able to load ROMs, I tried using a GPE ROM and was running into nothing but trouble. Hyperdrive 10.1 ended up being my daily driver until I caused this mess. Did you have to do anything special to get the GPE ROM working properly?
Click to expand...
Click to collapse
Nope, flashed it to the stock slot, then the MF3 modules. It's one of the many reasons I haven't updated to MK2 yet... I have no desire to have my phone locked down further. I'm just monitoring how Safestrap evolves, along with the BypassLKM exploit.

Remember that u are on MK2 now prior to bricked . ...U CAN'T DOWNGRADE TO MF3. ... after u unbricked your device u would end up with stock mk2 ... and u should know the rest of the SS guide on how to install custom rom. ..... make sure try it first on slot 1 before u install to stock slot and ALWAYS DOUBLE CHECK WHICH ROM SLOT ARE ACTIVE BEFORE REBOOTING. ...... GOODLUCK. .........FOR MK2 FIRMWARE U CAN ONLY INSTALL 4.3TW ROM........U CAN'T INSTALL GPE,CM,AOSP,AOKP AS OF RIGHT NOW....... :crying::crying:
......MOD PLEASE MOVE THIS TO Q&A SECTION.....
Swyped from MF3 Deadly Venom SS

ted77usa said:
Remember that u are on MK2 now prior to bricked . ...U CAN'T DOWNGRADE TO MF3. ... after u unbricked your device u would end up with stock mk2 ... and u should know the rest of the SS guide on how to install custom rom. ..... make sure try it first on slot 1 before u install to stock slot and ALWAYS DOUBLE CHECK WHICH ROM SLOT ARE ACTIVE BEFORE REBOOTING. ...... GOODLUCK. .........FOR MK2 FIRMWARE U CAN ONLY INSTALL 4.3TW ROM........U CAN'T INSTALL GPE,CM,AOSP,AOKP AS OF RIGHT NOW....... :crying::crying:
......MOD PLEASE MOVE THIS TO Q&A SECTION.....
Swyped from MF3 Deadly Venom SS
Click to expand...
Click to collapse
Thanks Ted. Would you mind giving me a hand with this? NightHawk pointed me to your thread, but I am unsure whether to use the "
MK2_UNBRICKED_METHOD_(HARD-BRICKED)" or the separate files to recover from a soft brick - "ONLY USE THESE IF U (SOFT-BRICKED)". I tried both, unsuccessfully unfortunately, but maybe I missed something.
When going through the soft-bricked files, "Stock Recovery" and "Stock Modem" seems to check out fine, according to Odin's MD5 verification. The last one, labeled "Boot" failed the MD5 check. I put Stock Recovery in PDA, Stock Modem in Phone and was attempting to put BOOT in BOOTLOADER. Maybe I did something wrong? Should I flash them one at a time?
Thanks in advance, and yes, I did hit your Thanks button, and will keep doing so every time I log in!!
John

Also, I assume Deadly Venom is a TW 4.3 ROM? Maybe I'll give that one a shot if I ever recover this wonderful piece of equipment!

JohnnyMac999 said:
Thanks Ted. Would you mind giving me a hand with this? NightHawk pointed me to your thread, but I am unsure whether to use the "
MK2_UNBRICKED_METHOD_(HARD-BRICKED)" or the separate files to recover from a soft brick - "ONLY USE THESE IF U (SOFT-BRICKED)". I tried both, unsuccessfully unfortunately, but maybe I missed something.
When going through the soft-bricked files, "Stock Recovery" and "Stock Modem" seems to check out fine, according to Odin's MD5 verification. The last one, labeled "Boot" failed the MD5 check. I put Stock Recovery in PDA, Stock Modem in Phone and was attempting to put BOOT in BOOTLOADER. Maybe I did something wrong? Should I flash them one at a time?
Thanks in advance, and yes, I did hit your Thanks button, and will keep doing so every time I log in!!
John
Click to expand...
Click to collapse
Appreciated the Thank button. .... It was created for that purpose. .......BTW u should only flash it on PDA....one at the time and if md5 check failed or different ....please redownload the files......
JohnnyMac999 said:
Also, I assume Deadly Venom is a TW 4.3 ROM? Maybe I'll give that one a shot if I ever recover this wonderful piece of equipment!
Click to expand...
Click to collapse
Yes Sir. .... Both Deadly Venom and Dark Carnage are base from international rom 4.3 ML6. .... For ATT users. ..... For other US carrier might also work but Need to enter APN manually. ......As far as unbricking your phone follow post #3 from my thread and download all the MF3 emergency files. .... Recovery.mj6.tar.md5. .... and make sure u also download MF3>MK2 update. Zip files from OP (Original Post) coz u need it in the end of the unbricked_ Method. ..... Either u flash that update.Zip (mf3> mk2) from stock recovery by choosing apply update via external sd card or apply update via adb by using adb sideload.... check post#2 on how to update. ...... let me know which part that u don't understand. ......Goodluck. .....:thumbup::thumbup:
Swyped from MK2 Dark Carnage SS Edition

ted77usa said:
Appreciated the Thank button. .... It was created for that purpose. .......BTW u should only flash it on PDA....one at the time and ig md5 checked different....please redownload the files......
Yes Sir. .... Both Deadly Venom and Dark Carnage are base from international rom 4.3 ML6. .... For ATT users. ..... For other US carrier might also work but Need to enter APN manually. ......As far as unbricking your phone follow post #3 from my thread and download all the MF3 emergency files. .... Recovery.mj6.tar.md5. .... and make sure u also download MF3>MK2 update. Zip files from OP (Original Post) coz u need it in the end of the unbricked_ Method. ..... Either u flash that update.Zip (mf3> mk2) from stock recovery by choosing apply update via external sd card or apply update via adb by using adb sideload.... check post#2 on how to update. ...... let me know which part that u don't understand. ......Goodluck. .....:thumbup::thumbup:
Swyped from MK2 Dark Carnage SS Edition
Click to expand...
Click to collapse
One part I don't understand is in gtj0's guide, lines 7&8:
7. Force Reboot the phone back into Download mode (Voldown+Home+Power) and restart Odin.
8. The phone should now reboot to a black screen with the pulsing notification LED.U need to install...
He says force the phone into Download mode, and re-start Odin. The very next line says 'the phone should now re-boot'. What happens after line 7 that we needed Odin for?

That was If you coming from MJ6 his original thread to go back to Mj6 and then use the MJ9 update zip..... Since we coming from newer rom MK2. ... It would stuck on download mode .... That's when u need to install stock recovery .... Either Recovery.mj6.tar.md5 or i337mk2 stockrecovery.tar.md5 (either way worked) and then u need to force reboot to stock recovery. ..and then flash mf3> Mk2 update zip. ... follow post#2 on how to update. .... There is two method. ....apply update via external card or using adb sideload...... Goodluck
Swyped from MK2 Dark Carnage SS Edition

JohnnyMac999 said:
One part I don't understand is in gtj0's guide, lines 7&8:
7. Force Reboot the phone back into Download mode (Voldown+Home+Power) and restart Odin.
8. The phone should now reboot to a black screen with the pulsing notification LED.U need to install...
He says force the phone into Download mode, and re-start Odin. The very next line says 'the phone should now re-boot'. What happens after line 7 that we needed Odin for?
Click to expand...
Click to collapse
I went back through Post 3, re-downloaded all the files, everything has gone as you suggest it would to this point. I am re-downloading the update.zip file (MF3>MK2) from post 1 and am about to do the final step in the process. This is the exact same process I used yesterday when I tried to recover this the first time, but once I got to the step of side-loading the update file, I got an 'Error 7' failure from the 'asserts' line in the update script. Hopefully a re-DL will make things right this time! Keep wishing me luck!
Update: New DL for update.zip completed late. Just finished final step with the same failure as before:
Verifying current system....
assert failed: apply_patch_check( "system/SW_Configuration.xml", "acdd86b773e13cca512e4bb4f7c88a8489640994", "428f3b805bef7bc04df9eab6b262ff39f416cc41")
E:Error in /tmp/update.zip
(Status 7)
Installation aborted.
Any ideas?

Update: I'm back to MK2. The process was a bit painful, but if you follow the instructions in this post: http://forum.xda-developers.com/showthread.php?t=2618314, you will recover. Just read everything first!! I actually recruited help from a patient buddy that got me to MJ9, then I used the Update-mj9-mk2.zip file to takeme the rest of the way.
Special thanks to Ted77 for his patience, guidance and files!! (Yes, I will hit your 'Thanks' button!)
Moderators, please close this thread.

[Q] SM G900H Root Problem ????

Hi everybody i m new to the forum really glad to be part of such a great forum
first time i post for a problem cause after hours of search and tries cant get to root mt s5 sm g900h the exynos version try many differents official roms from sammobile and some requested by some users to be rootable but always same problem when i flash cf with odin i get
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-k3g-k3gxx-smg900h.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/022> Added!!
<ID:0/022> Odin v.3 engine (ID:22)..
<ID:0/022> File analysis..
<ID:0/022> SetupConnection..
<ID:0/022> Initialzation..
<ID:0/022> Get PIT for mapping..
<ID:0/022> Firmware update start..
<ID:0/022> SingleDownload.
<ID:0/022> recovery.img
<ID:0/022> NAND Write Start!!
<ID:0/022> FAIL!
<ID:0/022>
<ID:0/022> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
whatever the rom i put on it and for flashing an entire rom several times it works perfectly just cant figure why for a complete rom no problem and for a little 24 mo of cf root it crashes every time tried several ports cables odin versions 3.09 3.07 1.85 1.87 niet
so has anyone succed rooting the 900h version and how and do you advice me to wait or keep trying and risking to brick it
thanks in advance for interest and answer

no one have the 900h variant ??? :crying:

for those interested the problem was from reactivation lock that's it ,question ansered by my self

You need to enter into security settings and disable Reactivation Lock. After procedure you can turn it on again.
I habe G900H version and everything gone ok. Piece of cake.

I've been through some serious root problems. When I root successfully. I have flash cook rom 4.2 JB and memory partitions in the device's successful I lost root. Luckily I have TWRP 2.5.0.0. Then I tried to re-root your device by supersu.zip but without success. I also use framaroot failed. I finally copied the su binary file in system / xbin and copy files supersu.apk in system / app but I still can not get root. So how to root this device. My device is lenovo-p770 rom: 4.2 JB
Sent from my LENOVO P770 using XDA Premium 4 mobile app

Android5011 said:
I've been through some serious root problems. When I root successfully. I have flash cook rom 4.2 JB and memory partitions in the device's successful I lost root. Luckily I have TWRP 2.5.0.0. Then I tried to re-root your device by supersu.zip but without success. I also use framaroot failed. I finally copied the su binary file in system / xbin and copy files supersu.apk in system / app but I still can not get root. So how to root this device. My device is lenovo-p770 rom: 4.2 JB
Sent from my LENOVO P770 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You are advised to report this at Lenovo's section

Can you please list down the steps you used to root the G900h?
I have one too and soft bricked it while trying to use cf. Don't want that to happen again.

Prince107rox said:
Can you please list down the steps you used to root the G900h?
I have one too and soft bricked it while trying to use cf. Don't want that to happen again.
Click to expand...
Click to collapse
You can try this linkhttps://www.google.com/url?q=http://forum.xda-developers.com/galaxy-s5/general/how-to-root-g900h-lollipop-t3029027&sa=U&ved=0CAQQFjAAahUKEwiDzoSIje3HAhUKig0KHRifBvI&client=internal-uds-cse&usg=AFQjCNEY2JPhkBALA6H5Iqqn4VXkmNw_Cw
Perhaps yu ve to reinstall OS of PC like me link http://forum.xda-developers.com/galaxy-s5/general/trick-how-to-success-odin-flash-newbies-t3195645
use windows7 or XP
Then reinstall Samsung drivers
Good luck

hello guys. .
I have 3 problems regarding my Samsung galaxy s5 SM G900H . .
1)I have recently rooted with cf auto root via ODIN. . BT by default I got super su version 2.68 which it beta app. . .even play store have version2.65 as latest version. . .super su keeps on asking for binary update. .when I try to update it normally,it always gets failed. .
2)I thought if I could install cwm/twrp recovery I could install super su version 2.65 and fix the binary issue. . I got the cwm recovery and flashes it via ODIN. . .cwm was installed. .BT it shows mount issues and seems to have reading SD card issues. . I can't backup to my SD card or so. . .
this is the text which I see when open cwm recovery. . .even when I installed Phil's recovery from rashr recovery tools. . ven Phil's recovery showed same issues. .
3)I have installed flashfire in my Samsung galaxy s5. . it shows the following warning. . .
I just want to backup my current stock ROM and move to s6 ROM for my Samsung galaxy s5 SM G900H. . .if you have any working alternatives feel free to suggest. . .
please help. .
Sent from my Venue7 3740 LTE using XDA Free mobile app

Rooting S4 with Android 5.0.1

Hi guys,
I'm trying to root a Galaxy S4 GT-I9505 / Baseband I9505XXUHPK2 / Build LRX22C.I9505XXUHPK2 / Android 5.0.1 / Security-level 2016-11-01
Unfortunately I don't have any success...
I tried the method shown here: https://forum.xda-developers.com/showthread.php?t=2219803
- Phone in Download mode
- Odin Odin3-v3.10.6.exe with CF-Auto-Root-jflte-jfltexx-gti9505.tar.md5 (running as admin)
- phone is properly connected (shown in ID:COM)
- Odin displays FAIL!
log:
<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/005> Odin engine v(ID:3.1005)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
<ID:0/005> Added!!
<ID:0/005> Removed!!
Did I miss anything? Is this root-method outdated?
What can I do about that PIT partition?

luxcassidy said:
Hi guys,
I'm trying to root a Galaxy S4 GT-I9505 / Baseband I9505XXUHPK2 / Build LRX22C.I9505XXUHPK2 / Android 5.0.1 / Security-level 2016-11-01
Unfortunately I don't have any success...
I tried the method shown here: https://forum.xda-developers.com/showthread.php?t=2219803
- Phone in Download mode
- Odin Odin3-v3.10.6.exe with CF-Auto-Root-jflte-jfltexx-gti9505.tar.md5 (running as admin)
- phone is properly connected (shown in ID:COM)
- Odin displays FAIL!
log:
<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/005> Odin engine v(ID:3.1005)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
<ID:0/005> Added!!
<ID:0/005> Removed!!
Did I miss anything? Is this root-method outdated?
What can I do about that PIT partition?
Click to expand...
Click to collapse
if your phone still boot fine, then forget that method.
use the same method but instead of flashing that file you tried (cf-auto-root....), flash TWRP recovery using Odin (download a .tar file), and in Odin tick only "auto reboot" and "F . reset time".
after the success, let the phone boot, to make sure it boots fine, when it boots, download SuperSU.zip from here, and place it in your internal storage.
after that:
1- turn off your phone.
2- boot into recovery using the three button (power+home+vol up).
3- and flash the zip then reboot, now you have root.

MigoMujahid said:
if your phone still boot fine, then forget that method.
use the same method but instead of flashing that file you tried (cf-auto-root....), flash TWRP recovery using Odin (download a .tar file), and in Odin tick only "auto reboot" and "F . reset time".
after the success, let the phone boot, to make sure it boots fine, when it boots, download SuperSU.zip from here, and place it in your internal storage.
after that:
1- turn off your phone.
2- boot into recovery using the three button (power+home+vol up).
3- and flash the zip then reboot, now you have root.
Click to expand...
Click to collapse
Will i trigger the knox flag by doing this? ty

Yes, flashing twrp will trip Knox.

audit13 said:
Yes, flashing twrp will trip Knox.
Click to expand...
Click to collapse
Is there a way to avoid that? ty m8

Nope, can't avoid it.
At this point, I don't think it matters unless your phone has warranty.

Honestly, it doesn't matter at all. The last Galaxy S4 devices were US models from Straight Talk, and those have been out of warranty for at least a year now.

audit13 said:
Nope, can't avoid it.
At this point, I don't think it matters unless your phone has warranty.
Click to expand...
Click to collapse
Alright, i am ready to trip it, can you tell me what methoud should i use to root my s4? I can't find any newest tutorial i keep getting those from 2013-15, i want to flash imperium ROM i'm kinda excited. Cheers

If you want to root with TWRP, try this for the gt-i9505:
open Odin 3.07 and uncheck everything except r reset time;
download the tar version of twrp for the gt-i9505: https://dl.twrp.me/jfltexx/
download the latest version of supersu.zip and copy it to an sd card or the phone's internal storage: http://www.supersu.com/download;
place the sd card in the phone if twrp has been saved to the sd card from the step above;
connect the phone in download mode and flash twrp in Odin's PDA slot;
when you see the word "reset" in the status window, remove USB cable from the phone, remove battery, replace battery, boot into recovery, install supersu.zip, reboot.
If you just want to install a custom ROM, copy the ROM to the internal or external sd card, install twrp, and install the ROM. Root is not required to install a custom ROM, only a custom recovery.
Warning: whenever you flash anything to a phone, it is always possible for something to go wrong and you must be prepared to deal with any consequences. I have used this method for several note 2, note 3, s3, and s4 phones without any issues. With this being said, I can't guarantee that the above steps will work for your phone or your phone won't be bricked.

audit13 said:
If you want to root with TWRP, try this for the gt-i9505:
open Odin 3.07 and uncheck everything except r reset time;
download the tar version of twrp for the gt-i9505: https://dl.twrp.me/jfltexx/
download the latest version of supersu.zip and copy it to an sd card or the phone's internal storage: http://www.supersu.com/download;
place the sd card in the phone if twrp has been saved to the sd card from the step above;
connect the phone in download mode and flash twrp in Odin's PDA slot;
when you see the word "reset" in the status window, remove USB cable from the phone, remove battery, replace battery, boot into recovery, install supersu.zip, reboot.
If you just want to install a custom ROM, copy the ROM to the internal or external sd card, install twrp, and install the ROM. Root is not required to install a custom ROM, only a custom recovery.
Warning: whenever you flash anything to a phone, it is always possible for something to go wrong and you must be prepared to deal with any consequences. I have used this method for several note 2, note 3, s3, and s4 phones without any issues. With this being said, I can't guarantee that the above steps will work for your phone or your phone won't be bricked.
Click to expand...
Click to collapse
hey man i tried this method https://www.youtube.com/watch?v=4iPhBfGFMVk i think it's the same method as yours, when i do this and press power button and volume up it doesn't get me in TWRP recovery but it eneters in default recovery instead, thus my phone isn't rooted................. what to do? maybe samsung drivers .? Cheers

You can't let the phone boot to the desktop after flashing twrp. Are you disabling auto reboot?

audit13 said:
You can't let the phone boot to the desktop after flashing twrp. Are you disabling auto reboot?
Click to expand...
Click to collapse
I did like in video, only leaving auto-reboot checked...

I said uncheck everything except f reset time.

audit13 said:
I said uncheck everything except f reset time.
Click to expand...
Click to collapse
Voila, root accesss granted! Thanks a bunch man, now i am heading over to flash Imperium ROM
---------- Post added at 01:01 AM ---------- Previous post was at 12:52 AM ----------
audit13 said:
If you want to root with TWRP, try this for the gt-i9505:
open Odin 3.07 and uncheck everything except r reset time;
download the tar version of twrp for the gt-i9505: https://dl.twrp.me/jfltexx/
download the latest version of supersu.zip and copy it to an sd card or the phone's internal storage: http://www.supersu.com/download;
place the sd card in the phone if twrp has been saved to the sd card from the step above;
connect the phone in download mode and flash twrp in Odin's PDA slot;
when you see the word "reset" in the status window, remove USB cable from the phone, remove battery, replace battery, boot into recovery, install supersu.zip, reboot.
If you just want to install a custom ROM, copy the ROM to the internal or external sd card, install twrp, and install the ROM. Root is not required to install a custom ROM, only a custom recovery.
Warning: whenever you flash anything to a phone, it is always possible for something to go wrong and you must be prepared to deal with any consequences. I have used this method for several note 2, note 3, s3, and s4 phones without any issues. With this being said, I can't guarantee that the above steps will work for your phone or your phone won't be bricked.
Click to expand...
Click to collapse
Wait so if i wan't to have Imperium ROM i need to flash twrp again first then flash Imperium?

Once twrp is installed on the phone, you do not have to reflash it again unless you want a different version.
To flash a custom ROM, you just have to flash twrp and then use twrp to install the custom ROM. Root is not required to install TWRP from Odin.

audit13 said:
Once twrp is installed on the phone, you do not have to reflash it again unless you want a different version.
To flash a custom ROM, you just have to flash twrp and then use twrp to install the custom ROM. Root is not required to install TWRP from Odin.
Click to expand...
Click to collapse
Well i want to flash Imperium and i already got twrp so i just have to flash Imperium ROM and that's it

Here's how I usually flash a custom ROM:
install twrp;
copy the custom ROM and Gapps (if required) to an sd card and place the sd card into the phone;
boot into twrp and create a backup of my existing ROM;
use twrp to wipe system, cache, data;
install rom, install gapps, reboot.

audit13 said:
Here's how I usually flash a custom ROM:
install twrp;
copy the custom ROM and Gapps (if required) to an sd card and place the sd card into the phone;
boot into twrp and create a backup of my existing ROM;
use twrp to wipe system, cache, data;
install rom, install gapps, reboot.
Click to expand...
Click to collapse
It says on imperium page "Auto format system before flashing the ROM" so i assume it's enough before flashing the ROM, btw. he doesn't mention gapps, dunno why, maybe it's integrated tol the ROM itself

I'm not familiar with the Imperium ROM but some ROMs have Gapps included.

Ah nice, currently i'm doing a backup it's taking a while, once it's done i am going for ROM flash! Cheers
---------- Post added at 01:58 AM ---------- Previous post was at 01:18 AM ----------
First boot taking too long... i scared of going to bootloop