So, I have a ROOTED Samsung Galaxy S5 SM-G900H, rooted through Odin3 by ChainFire's 'CF-Auto Root' Root file (Thanks btw). My phone's firmware is currently G900HXXU1BOD3, If I were to update my phone's firmware to the latest one, which is G900HXXU1BOL1 through Kies3, would I have to use another CF-Auto Root file by ChainFire that is specifically for this firmware (which I guess I have to submit the recovery.img file to ChainFire if there isn't a root file for this firmware yet) or am I just able to use the root file I used to root G900HXXU1BOD3? Please leave ideas/suggestions of what I have to do or even better the actual answers. Thanks in advance.
I've used the same CF Auto Root from KitKat > All Lollipop ROMs, didn't need to change it
Related
I managed root access , and successfully used root . But it stoped working for some unknown reason after 1/1.30hour of root ...Anyone willing to take risk can try it. & share if something better happens . I mean if can manage root access permanently .
What I did was
- upgraded to lollipop 5.0 (WOEA) using Odin 3.10
- flashed twrp 2.8.6.0 via Odin . ( this version is not working but it kills the stock recovery )
- then flashed twrp 2.8.5.0 via Odin . ( this version works on 4.4.2 & on 5.0 also . but stock recovery replaces it during the first boot as a result it is not usable . but I killed stock recovery by flashing twrp 2.8.6.0 . In this case it worked . & I was able to boot into twrp recovery )
- Installed updated SuperSU v2.46 zip via twrp 2.8.6.0
After doing those there was super user app in the app drawer & root checker also confirmed root access.
But as I said before , root access stopped working properly after a while...
Edit : CF-auto root for SC-04f VNF9 firmware is working on WOEA firmware . I recenty flashed it . Though Xmod is not working but other root apps (like titanium backup , greenify etc. ) are working nice .
Sunbir Ahammed said:
I managed root access , and successfully used root . But it stoped working for some unknown reason after 1/1.30hour of root ...Anyone willing to take risk can try it. & share if something better happens . I mean if can manage root access permanently .
What I did was
- upgraded to lollipop 5.0 (WOEA) using Odin 3.10
- flashed twrp 2.8.6.0 via Odin . ( this version is not working but it kills the stock recovery )
- then flashed twrp 2.8.5.0 via Odin . ( this version works on 4.4.2 & on 5.0 also . but stock recovery replaces it during the first boot as a result it is not usable . but I killed stock recovery by flashing twrp 2.8.6.0 . In this case it worked . & I was able to boot into twrp recovery )
- Installed updated SuperSU v2.46 zip via twrp 2.8.6.0
After doing those there was super user app in the app drawer & root checker also confirmed root access.
But as I said before , root access stopped working properly after a while...
Edit : CF-auto root for SC-04f VNF9 firmware is working on WOEA firmware . I recenty flashed it . Though Xmod is not working but other root apps (like titanium backup , greenify etc. ) are working nice .
Click to expand...
Click to collapse
Does it work properly and there is no other risk implied ?
Can you please specify the steps you used to root the phone and provide links if possible.
Thank you a lot !!!
Zikkun said:
Does it work properly and there is no other risk implied ?
Can you please specify the steps you used to root the phone and provide links if possible.
Thank you a lot !!!
Click to expand...
Click to collapse
The steps I took at the first time was bit risky . :silly: And root was working good till I rebooted the device & performed a factory reset. After that root wasn't working properly.
Now I am using root access again . Root checker showing root access & using Greenify , Titanium backup etc. This time I rooted using CF-auto root for SC-04f VNF9 firmware. Instructions are on the website below....
CF-auto root page: https://autoroot.chainfire.eu/
XDA Thread : http://forum.xda-developers.com/showthread.php?t=2696537
Though this method is for SC04FOMU1VNF9 firmware (android 4.4.2) But it is working on SC04FOMU1WOEA firmware (android 5.0)
I also used factory reset option twice after rooting using CF-auto root. Still using root & haven't found any problems.
I haven't made this , so can't guaranty anything. Try at your own risk. But I think there won't be any problem if you follow the instructions properly.
little problem, different outcome
Hey Sunbir Ahammed,
Thanks for sharing your trial and errors. I'm in the same boat you were in. I had a very small instance of root success, then for some reason or other I lost it. My first attempt was with CF-auto root using Oden 3.10. It worked for a very short amount of time (Root Checker did verify). Gave it one restart and haven't been able to get root since. I even went back and tried your original TWRP methods. No dice.
SuperSu is installed after CF-auto root, but isn't usable since the root wasn't successful.
I have a feeling it is related to the stock recovery but not sure. I'm new to the root game and could use some pointers. Any ideas?
Here's the details on the device:
Galaxy S5 (SC-04F)
carrier: NTT Docomo
android 5.0 Lollipop
Kuripi2 said:
Hey Sunbir Ahammed,
Thanks for sharing your trial and errors. I'm in the same boat you were in. I had a very small instance of root success, then for some reason or other I lost it. My first attempt was with CF-auto root using Oden 3.10. It worked for a very short amount of time (Root Checker did verify). Gave it one restart and haven't been able to get root since. I even went back and tried your original TWRP methods. No dice.
SuperSu is installed after CF-auto root, but isn't usable since the root wasn't successful.
I have a feeling it is related to the stock recovery but not sure. I'm new to the root game and could use some pointers. Any ideas?
Here's the details on the device:
Galaxy S5 (SC-04F)
carrier: NTT Docomo
android 5.0 Lollipop
Click to expand...
Click to collapse
Hello friend,
Well, there is good news. Finally CF Auto Root has been released for a new firmware version.
CF Auto Root now supports SC04FOMU1WOJ1 firmware (the latest one available at both Samsung Kies and sammobile.com)
Here is the link for the latest firmware
And here the CF auto Root link
After upgrading the latest firmware using OTA or Samsung Kies or Odin you just need to flash the CF auto root file using Odin
Here is the detail instruction from CF auto root's website
and here is the XDA thread on CF auto root.
I have flash it just now. And will update if any common issue is found while using.
Hope this helps. :angel:
I tried many options form this site to root my Galaxy S5 SM-G900W8 but I couldn't make it. Root doesn't work. When I returned on 5.0 version root works without problem. Does somebody know if there is root for Lollipop 5.1.1?
Thanks
Here you go.
1: Odin flash the TWRP recovery provided in my post.
2: Download and TWRP flash both files (Kernel and SU) in this link http://forum.xda-developers.com/galaxy-s5/general/canadian-users-g900w8-discussion-t3228804
3: Hit thanks button in above link
4: Enjoy root.
I have a Samsung Galaxy J5 SM J500FN. I just install the last update Android 6.0.1 and now I'm trying to root in but I cannot find any rooting tool I tried kingroot,kingoroot but none of them could root my phone
For now I don't know about a way to root without Pc.
You can look here:
http://forum.xda-developers.com/galaxy-j5/how-to/tutorial-upgrade-j5-2015-to-6-0-t3443904
a downgrade solution. Maybe Kingroot is able to root it afterwards.
When unsuccessful you will at least be able to flash twrp via Odin and flash SuperSu zip(Google for it).
Look here:
http://forum.xda-developers.com/galaxy-j5/development/recovery-samsung-galaxy-j5-t3338869
Much fun
Hi I have a Samsung Galaxy j5 on 6.0.1 and I rooted it using the same one as I did for rooting on 5.1.1
Download CF auto root for your model and flash it via odin
bronko3010 said:
For now I don't know about a way to root without Pc.
You can look here:
http://forum.xda-developers.com/galaxy-j5/how-to/tutorial-upgrade-j5-2015-to-6-0-t3443904
a downgrade solution. Maybe Kingroot is able to root it afterwards.
When unsuccessful you will at least be able to flash twrp via Odin and flash SuperSu zip(Google for it).
Look here:
http://forum.xda-developers.com/galaxy-j5/development/recovery-samsung-galaxy-j5-t3338869
Much fun
Click to expand...
Click to collapse
Yes.. Rooting with supersu.zip via TWRP is the easiest method to root any lollipop or marshmallow phone :fingers-crossed:
Hi guys. Wasn't quite sure about rooting my s5.
It now has 6.01 from sammobile.
When I go on chainfire and look at the autoroot for the s5 6.01...yes they have the files for rooting but not matching my build number.
How important is it that we need to match the build number or does it not matter?
Please see screenshots.
Thanms
well, if your bootloader is unlocked, then you should be able to flash TWRP via Odin and root that way. It appears that this is the unlocked version. You should be good to flash TWRP and root via recovery
Hi,
It is not important to have matching build numbers. I would like to warn that the kltedv autoroot method is buggy and instead you can use the kltedd files. I recommend that you use SuperSU (flash via TWRP) to root your device as it is a more commonly used rooting method for our device nowadays.
Saber
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.