Hey,
I wanted to root my Galaxy S4 i9505 using CF-auto root. I cheked the version of my s4 i9505 which was i9505xxuhoj2, then go to https://desktop.firmware.mobi/ find my device model and exact same build (i9505xxuhoj2). I generated cf auto root file, boot phone in bootloader mode, unzip file and used odin (which was in that zip file too) to flash this generated file (using AP). Odin gives me FAIL and I cant boot my phone normally because of error during start (firmware upgrade encountered an issue please select recovery mode in kies).
So I flashed stock firmware (using Odin) with another build. This time i9505xxupqg1. Everything went well my S4 was running normally. So i decided repeated the procedure. Go to https://desktop.firmware.mobi/ and genereate cf auto file (this time for build i9505xxupqg1). I flashed the cf auto root file using odin and again it gives me FAIL.
Below screen of that FAIL:
https://imgur.com/a/SujjD
Can anyone help me with this?
Why this is happening ?
Cheers
Flash back to stock, flash twrp, flash supersu from twrp.
Thanks for reply.
I did this earlier what you said and everything was OK.
I had TWRP and Root using SU.
The problem isnt rooting itself.
The point is i wanted to tested rooting with CF-AutoRoot method.
And I'm wondering what am I doing wrong.
I did everyting correctly (exact same device model and build version) and ODIN gives me FAIL like i said above.
If Odin is failing, try a different version of Odin, a different USB cable, and different USB port.
I got the same problem with a Sprint Note Edge that I tried to root the same way. I'm currently downloading the stock firmware from sammobile.com to flash a stock ROM.
Thomass30 said:
Hey,
I wanted to root my Galaxy S4 i9505 using CF-auto root. I cheked the version of my s4 i9505 which was i9505xxuhoj2, then go to https://desktop.firmware.mobi/ find my device model and exact same build (i9505xxuhoj2). I generated cf auto root file, boot phone in bootloader mode, unzip file and used odin (which was in that zip file too) to flash this generated file (using AP). Odin gives me FAIL and I cant boot my phone normally because of error during start (firmware upgrade encountered an issue please select recovery mode in kies).
So I flashed stock firmware (using Odin) with another build. This time i9505xxupqg1. Everything went well my S4 was running normally. So i decided repeated the procedure. Go to https://desktop.firmware.mobi/ and genereate cf auto file (this time for build i9505xxupqg1). I flashed the cf auto root file using odin and again it gives me FAIL.
Below screen of that FAIL:
https://imgur.com/a/SujjD
Can anyone help me with this?
Why this is happening ?
Cheers
Click to expand...
Click to collapse
Hello
You do not need to generate a CF-AutoRoute, just google and download the original CF-AutoRoute.zip which roots ALL versions of the device, the baseband does not matter.
Ensure debugging is enabled
Place device into recovery (download)
Add device to Odin
Unzip the file, add the .md5 file to Odin and flash, job done.
Related
So
I have been struggling a couple of hours with this issue: Trying to root my samsung galaxy s4 i 9505, with three different odin versions (now last tried v.1.85) and both CWM and TWRP. I finally managed to get a pass from odin, but whenever I go into recovery mode on my phone, I am at the stock recovery "page", saying Android recovery on the top. Which must mean that I am not rooted.
I have no idea what to do, anyone there with some tricks up their sleeves?
snorre89 said:
So
I have been struggling a couple of hours with this issue: Trying to root my samsung galaxy s4 i 9505, with three different odin versions (now last tried v.1.85) and both CWM and TWRP. I finally managed to get a pass from odin, but whenever I go into recovery mode on my phone, I am at the stock recovery "page", saying Android recovery on the top. Which must mean that I am not rooted.
I have no idea what to do, anyone there with some tricks up their sleeves?
Click to expand...
Click to collapse
1. Reflash Stock Rom.
2. Root your phone with latest version of ODIN following this GUIDE or you can:
- Download and unzip this FILE in your pc.
- Take your device in DOWNLOAD MODE.
- Flash it via ODIN.
3. Install SUPERSU of Play Store app if you don't see it in desktop of your device.
4. Reboot in DOWNLOAD MODE and flash TWRP via ODIN. Your phone will reboot or reboot manually.
5. Done, your have root and custom recovery installed. Good luck :highfive:
Joku1981 said:
1. Reflash Stock Rom.
2. Root your phone with latest version of ODIN following this GUIDE or you can:
- Download and unzip this FILE in your pc.
- Take your device in DOWNLOAD MODE.
- Flash it via ODIN.
3. Install SUPERSU of Play Store app if you don't see it in desktop of your device.
4. Reboot in DOWNLOAD MODE and flash TWRP via ODIN. Your phone will reboot or reboot manually.
5. Done, your have root and custom recovery installed. Good luck :highfive:
Click to expand...
Click to collapse
Cheers for your reply, unfortunately I haven´t gotten longer than the first step. I try to flash stock rom, but it seems like i need a pit file and i cannot find a working one anywhere around the internet. Is there some way to find the pit file stored in my phone? Or another place where I can find a working pit file other than the one called CSB_signed_Fusion3_EUR_0325_V2?
Edit: Now I successfully reflashed stock rom and installed CWM recovery. Problem is that whenever I try to flash a rom I get the message "installation aborted".
What to do?
Good afternoon guys,
i have a big issue with my galaxy s5 SM-G900S (korean version). I bought it as a refurbished device. Knox was on 0x1 so something may have been modified.
It came with the stock (?!) android 4.4.2 from march14. I tried to update but it returned a registration error. Probably because knox is 0x1
In any case, I activated usb debugging and tried to root the phone using cfautoroot and the corresponding root file: CF-Auto-Root-klteskt-klteskt-smg900s.zip which I still assume to be the correct one.
I used odin for flashing. The device was properly connected (blue).
Everything seemed to go smooth until the phone restart when it said "recovery is not seandroid enforcing". I tried several times with both odin 3.07 and 3.09 but i cannot pass this step. I also tried the method to untick auto reboot, shut the phone down manually and boot into recovery mode but it failed.
This means I am now stuck in the bootloop. I can access download mode, but i cannot reach recovery mode. Also the phone is not recognized by the computer if i try to connect it to adb, kies etc. Odin seems to connect properly still.
Alright how should i proceed now?? My actual target is to flash a custom rom. I will need to go for a dirty flash now correct? Should I flash a stock rom with odin? If yes, which one?
Please support me a bit, I am very frustrated on this topic, especially cause I still dont realize my mistake......
Merry Christmas and greets from Bavaria, Germany.
cheeet
Flash the stock firmware to get out of boot loop. After flashing the stock firmware, everything should be working fine and booting again. Instead of using CF auto root, flash a custom recovery like TWRP and then use it to flash the SuperSU zip.
toxious651 said:
Flash the stock firmware to get out of boot loop. After flashing the stock firmware, everything should be working fine and booting again. Instead of using CF auto root, flash a custom recovery like TWRP and then use it to flash the SuperSU zip.
Click to expand...
Click to collapse
Alright, Im back to stock android 4.4.2 now. Works perfect, aside from registration. If I click on "update now" it shows: SKT-USIM required.
Can someone link a detailed guide for flashing cm13? I checked the web but i still dont entirely understand.
In any case I do not want to risk going into a tricky situation once more.....
Thanks in advance.
Greets, cheet
So I have a galaxys s5 g900f which i cleared it from a rom i used before and got it back to the original form of it. Got the .tar.md5 file of the official galaxy software from sammobile and installed it with odin. After that I wanted to root my phone again and stick with the official software. I tried to do that by the way I always used to with CF-Auto-Root using Odin once more and after downloading the file my phone was normally rebooting to recovery but it actually got stuck there without doing anything. Tried to flash twrp too but still nothing. The only thing i can flash at the time is the official software. Anyone had this issue before and can help? Thanks in advance
Flash the stock ROM again and get your phone back up and working properly
Then use this guide to root / twrp
http://forum.xda-developers.com/showpost.php?p=64961009&postcount=2
I have a Galaxy S7 SM-G935FD International Edition which, thru a long sequence of missteps, I have gotten to the point where I can only get to the Samsung Logo Screen or the ODIN download mode (ie. no boot). I flashed TWRP 3.0.2-0-herolte, apparently successfully, by converting the zipped file I found to a .tar and using ODIN 3.10.7 on a Win10PC. But I am unable using any key sequence to get into any TWRP recovery mode - only the two modes above. I tried to convert the Superman rom on this forum to a tar also, but flashing stopped after Aroma at starting NAND write. In my many missteps, what I was trying to accomplish is to debloat and root the phone, at least to gain root access using Android adb. I was able to do this on my previous S6 Edge, but Samsung's vast security barriers have defeated me.
Steps to recover from this mess greatly appreciated ...... hopefully steps I can complete using ODIN ............ thx, Gus
gus_zernial said:
I have a Galaxy S7 SM-G935FD International Edition which, thru a long sequence of missteps, I have gotten to the point where I can only get to the Samsung Logo Screen or the ODIN download mode (ie. no boot). I flashed TWRP 3.0.2-0-herolte, apparently successfully, by converting the zipped file I found to a .tar and using ODIN 3.10.7 on a Win10PC. But I am unable using any key sequence to get into any TWRP recovery mode - only the two modes above. I tried to convert the Superman rom on this forum to a tar also, but flashing stopped after Aroma at starting NAND write. In my many missteps, what I was trying to accomplish is to debloat and root the phone, at least to gain root access using Android adb. I was able to do this on my previous S6 Edge, but Samsung's vast security barriers have defeated me.
Steps to recover from this mess greatly appreciated ...... hopefully steps I can complete using ODIN ............ thx, Gus
Click to expand...
Click to collapse
Flash Stock Rom via ODIN.
Joku1981 said:
Flash Stock Rom via ODIN.
Click to expand...
Click to collapse
I was unable to find a stock rom for the international. I found a zipped UK no carrier stock rom. Since ODIN doesn't flash zipped files, I unzipped and saved to a tar file using 7-Zip on Win10. Attempts to flash the tar file using ODIN crashed ODIN on the PC. I'm not sure what's wrong, as I used the same method to flash the zipped TWRP file, and finished with a "success"
I note that I have a message saying kernel is not seandroid enforcing. Somehow I think using ODIN to flash a stock rom is being blocked by some Samsung secutity feature I cannot identify and haven't overcome. Gus
Check this thread http://forum.xda-developers.com/showthread.php?t=3335065 I don't know if you have experience with Odin process. Google it preferably look at YouTube video, if you feel shaky on Odin concepts.
Sent from my SM-G935F using Tapatalk
gus_zernial said:
I was unable to find a stock rom for the international. I found a zipped UK no carrier stock rom. Since ODIN doesn't flash zipped files, I unzipped and saved to a tar file using 7-Zip on Win10. Attempts to flash the tar file using ODIN crashed ODIN on the PC. I'm not sure what's wrong, as I used the same method to flash the zipped TWRP file, and finished with a "success"
I note that I have a message saying kernel is not seandroid enforcing. Somehow I think using ODIN to flash a stock rom is being blocked by some Samsung secutity feature I cannot identify and haven't overcome. Gus
Click to expand...
Click to collapse
1. "I flashed TWRP 3.0.2-0-herolte, apparently successfully, by converting the zipped file I found to a .tar and using ODIN 3.10.7 on a Win10PC." Reflash this FILE via ODIN coz you flashed wrong one and boot in it. Go to next step if doesn't work.
2. Flash Stock ROM via ODIN. SM-G935FD use the same firmwares that SM-G935F.
Careful with ODIN. Make sure you are running on the latest version, as I myself has problems using it for the Galaxy S7 Edge on an offer version
Sent from my SM-G935F using Tapatalk
maybe my question will be weird lol...how can i sofbrick a s7 g930p to be exact and then i can just unbrick flashing the U firmware? thanks.
Hello everyone,
I was thinking about installing Lineage OS on my Samsung Galaxy S4 GT-I9515 (Value Edition) currently running Stock Android Version 5.0.1 without root.
Is the version of Lineage OS and TWRP I found at https://forum.xda-developers.com/galaxy-s4/i9505-develop/rom-cm14-1-galaxy-s4-jfvelte-gt-i9515-t3534552 appropriate for that purpose?
Now, my confusion arises from the fact that different guides seem to give incomplete or even contradictory instructions on how to approach that. As a first step, I need to install a custom recovery, such as TWRP:
Does this require my device to be rooted?
Some guides apparently require my bootloader to be unlocked; Is this necessary? If so, how do I do that?
Other guides suggest that I use Odin. Is this the correct approach? Does my bootloader need to be unlocked for that method? Is a root required?
Anything else I should pay attention to?
Thank you very much in advance
You need to find a guide for your phone
Different phones have different processes
For example Motorola phones require you to unlock the bootloader where as Samsung phones Iv worked with you don't
Some devices you have to root first before you can flash twrp while others you flash twrp first then root
For most Samsung phones around the age of yours you can root using CF-Auto-Root
This is done via odin and all you do is put your phone in download mode load the img file into odin & flash
The same is true for flashing twrp
Here are the files for your phone
CF-Auto-Root
TWRP
Flash each image in odin
Not able to root S4 GT-I9515
TheFixItMan said:
You need to find a guide for your phone
Different phones have different processes
For example Motorola phones require you to unlock the bootloader where as Samsung phones Iv worked with you don't
Some devices you have to root first before you can flash twrp while others you flash twrp first then root
For most Samsung phones around the age of yours you can root using CF-Auto-Root
This is done via odin and all you do is put your phone in download mode load the img file into odin & flash
The same is true for flashing twrp
Here are the files for your phone
CF-Auto-Root
TWRP
Flash each image in odin
Click to expand...
Click to collapse
I tried to flash CF-Auto-Root on my phone after completing the flash till reset on odin phone gets restarted and is showing following messages on top left corner on the samsung s4 logo screen
recovery booting....
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit: recovery
it is not going any further than this please help.
TheFixItMan said:
You need to find a guide for your phone
Different phones have different processes
For example Motorola phones require you to unlock the bootloader where as Samsung phones Iv worked with you don't
Some devices you have to root first before you can flash twrp while others you flash twrp first then root
For most Samsung phones around the age of yours you can root using CF-Auto-Root
This is done via odin and all you do is put your phone in download mode load the img file into odin & flash
The same is true for flashing twrp
Here are the files for your phone
CF-Auto-Root
TWRP
Flash each image in odin
Click to expand...
Click to collapse
the twrp file bricks the phone
raffux3 said:
the twrp file bricks the phone
Click to expand...
Click to collapse
What do you mean by brick?
Does the twrp boot?
You must boot twrp straight after it's flashed - if you don't and your phone starts to boot you need to reflash it (once booted to twrp for the first time the recovery will stick)
Also if you swipe to allow modifications in twrp your rom may not boot unless you disable dm-verity - this can be done with a root zip eg CF-Auto-Root or magisk
Remember you may need to do other steps like enabling adb debugging & oem unlock before using CF-Auto-Root
You also may need to root before flashing twrp
That is the twrp for the S4 GT-I9515 - if you have a different variant it will not work
If you have a different model of S4 check the twrp website to see if there is an official version
I don't own your device - I'm sure there's guides that will you step by step process if you Google
TheFixItMan said:
What do you mean by brick?
Does the twrp boot?
You must boot twrp straight after it's flashed - if you don't and your phone starts to boot you need to reflash it (once booted to twrp for the first time the recovery will stick)
Also if you swipe to allow modifications in twrp your rom may not boot unless you disable dm-verity - this can be done with a root zip eg CF-Auto-Root or magisk
Remember you may need to do other steps like enabling adb debugging & oem unlock before using CF-Auto-Root
You also may need to root before flashing twrp
That is the twrp for the S4 GT-I9515 - if you have a different variant it will not work
If you have a different model of S4 check the twrp website to see if there is an official version
I don't own your device - I'm sure there's guides that will you step by step process if you Google
Click to expand...
Click to collapse
when you install it with odin, it starts for some seconds and stops with a FAIL. So the smartphone become bricked!!! I have the same model of s4 (I9515)
raffux3 said:
when you install it with odin, it starts for some seconds and stops with a FAIL. So the smartphone become bricked!!! I have the same model of s4 (I9515)
Click to expand...
Click to collapse
Flashing a recovery should not brick your device - you are just replacing stock recovery with a custom one - your phone should boot regardless but anyway
I assume you have enabled USB debugging - enabled oem unlock (if it's on your device) and flashed CF-Auto-Root first
I also assume you are flashing the tar image in the AP section of odin (you may need to Unzip to get filename.tar)
If you have done all the above search Google for a step by step guide for your device
Since I don't own this device I can't offer anymore support than that
TheFixItMan said:
Flashing a recovery should not brick your device - you are just replacing stock recovery with a custom one - your phone should boot regardless but anyway
I assume you have enabled USB debugging - enabled oem unlock (if it's on your device) and flashed CF-Auto-Root first
I also assume you are flashing the tar image in the AP section of odin (you may need to Unzip to get filename.tar)
If you have done all the above search Google for a step by step guide for your device
Since I don't own this device I can't offer anymore support than that
Click to expand...
Click to collapse
of course. i have installed root before and after I tried to install twrp recovery but it failed. Now I don't know how I can do to restore my s4. :crying:
I'm trying all prcedures for install the original firmware but odin fails always
raffux3 said:
of course. i have installed root before and after I tried to install twrp recovery but it failed. Now I don't know how I can do to restore my s4. :crying:
I'm trying all prcedures for install the original firmware but odin fails always
Click to expand...
Click to collapse
Long as it's the correct firmware for the device no reason why it wouldn't flash
Check download mode & make sure that the model number matches the firmware
If the firmware is also failing to flash I would guess there is a problem with your setup rather than the files (assuming the files are correct)
TheFixItMan said:
Long as it's the correct firmware for the device no reason why it wouldn't flash
Check download mode & make sure that the model number matches the firmware
If the firmware is also failing to flash I would guess there is a problem with your setup rather than the files (assuming the files are correct)
Click to expand...
Click to collapse
I have re-installed the usb drivers and odin works fine finally. I will try to root and install twrp again...thank you for support