is there a risk of bricking phone (odin) ? (Samsung Galaxy s3 neo GT-I9301I) - root - Galaxy S3 Neo Q&A, Help & Troubleshooting

Hi guys, i was thinking of rooting my phone with odin but i'm afraid i might brick it ( CF-Auto-Root )
so.. is there any one who used odin and it worked with him without bricking his phone ?
oh and i forgot to mention that i have android 4.4.2 kitkat
because when i use the normal way to download supersu and install it i get
-----
"There is no binary installed, and SuperSU cannot install it. This is a problem!"
"if you just upgraded to android 4.3, you need manually re-root consult the relevant forums for you device!"
edit:
i rooted my device with odin and there was no problem

darker729 said:
Hi guys, i was thinking of rooting my phone with odin but i'm afraid i might brick it ( CF-Auto-Root )
so.. is there any one who used odin and it worked with him without bricking his phone ?
oh and i forgot to mention that i have android 4.4.2 kitkat
because when i use the normal way to download supersu and install it i get
-----
"There is no binary installed, and SuperSU cannot install it. This is a problem!"
"if you just upgraded to android 4.3, you need manually re-root consult the relevant forums for you device!"
edit:
i rooted my device with odin and there was no problem
Click to expand...
Click to collapse
Download SuperSU via this link: http://download.chainfire.eu/641/SuperSU/UPDATE-SuperSU-v2.40.zip and flash it with your custom recovery.

Related

[Q] Failed Root?

Hello everyone, before I continue I will give my phone details below:
Model Number: GT-I9505
Andriod version: 4.4.2
Baseband version: I9505XXUFNC5
So my problem is that I followed a guide to rooting my Galaxy S4, after which Odin confirmed to me that my phone had passed the rooting setup, all very good. The problem occurs when checking to see if my phone had successfully being rooted, I downloaded Root Checker Basic which informed me that my phone actually isn't rooted.
So as anyone would do they start the rooting process again, to which the same outcome repeated.
I can not post the link to the guide I used, the website I followed was ibtimes. The guide I followed is named 'Root galaxy s4 (LTE) I9505 on Official Andriod 4.2.2 Kitkat Firmware.
The link above is the guide I used.
So my question is, has anyone else come across this in the past? I did a brief search in the forums prier to posting this but came to no avail.
Thank you for any and all help with regards to my problem!
1. Try to root ur phone 2 times with same method u used.
2. Always KNOX app will block SuperSU app. You will have to freeze or delete KNOX app.
As requested I deleted the KNOX app and tried a Root, it has again come up with the same results, quoting from the SuperSU app 'There is no SU binary installed, and SuperSU cannot install it. This is a problem!'
I can not think as to what I am doing wrong.
Update:
I have factory reset my phone, and tried the root again to which the results are the same, Odin doesn't go yellow, it goes blue but some people say this can be due to different versions.
I have got usb debugging enabled, the battery is charged. This is really frustrating as I was wanting to get put a ROM on my phone today haha.
If anyone has any further advice that will be much appreciated!
Have you tried flashing CWM Recovery to your phone? When exiting CWM if you're not rooted, it'll tell you and ask if you want to root. Select Yes then go back into Android and check your SuperSU.
Otherwise, you could always try use Odin to flash one of Djembys pre-rooted stock roms?
If you're just wanting to flash a custom rom, then you could just download a custom rom, put it on your phone internal storage (or external SD), flash a custom recovery and then flash the rom? That's worked for me in the past.
Try to root again with odin and if your recovery say anything like ''fix root'' always say no

[Q] Can someone help me please

I purchased a note 3 model : N900 I have rooted the device with Kingo and now wish to install CWMR. I entered into download mode to install the recovery img file and was greeted with Chinese symbols! Anyway to chance this?
1. Kingo root is the worst root you can ever use.
2. Flash stock ROM via Odin. (It wipe kingo root and residues after kingo..)
3. Root again. (CF-auto-root or Use Philz touch recovery and flash superSU.zip)
verny94 said:
1. Kingo root is the worst root you can ever use.
2. Flash stock ROM via Odin. (It wipe kingo root and residues after kingo..)
3. Root again. (CF-auto-root or Use Philz touch recovery and flash superSU.zip)
Click to expand...
Click to collapse
Thanks for your advice, sadly after reading and reading I have seen more posts regarding this issue. The kingo software says your can click the unroot button but is malware still present on the device after the root removal? Also I can not flash stock rom via odin as I already stated its in bloody Chinese.
VonStarkeGSD said:
Thanks for your advice, sadly after reading and reading I have seen more posts regarding this issue. The kingo software says your can click the unroot button but is malware still present on the device after the root removal? Also I can not flash stock rom via odin as I already stated its in bloody Chinese.
Click to expand...
Click to collapse
Update: Managed to install CWM using MTK DROID instead all done

issue installing supersu after rooting G900F

Hi
I successfully used odin to re-root my S5 G900F however when i followed the video posted explaining how to flash supersu using sphinx my phone will not boot i get message at boot saying set warranty bit:kernel and it will not proceed from there can someone help me with this issue i am kind of new to rooting etc so if i have missed something let me know
Thanks
Hi there, whats your android version ?
Try flashing this with your custom recovery
If you're 'successfully rooted' you can download and install SuperSU direct from the playstore......Why would you need to odin flash it?
Sent from my rooted kn0x0 SM-G900F S5
I tried play store it didnt work right as the root was unsuccessful it turns out i had to restore my phone with the stock rom in end as I used flashed something incorrectly. I will attempt to root again i am now on lollipop

Root Galaxy S5 G900D (SC-04f) Android 5.0 (WOEA)

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:

S4 GTI9505 flashed recovery without root help

So I accidentally flashed the recovery package through Odin to a friend's s4 gt i9505 and i get a no access error in the recovery with an android and a red triangle. Since it has a custom recovery odin doesnt detect it. My question is what should i do ? . There is literally noone that has experienced the same (noob) mistake so there is no real fix. The phone is running 4.4.2 with an official upgrade to lollipop but KNOX was tripped so I would like to fix for him without having to pay for official service.
Thanks in advance.
Odd. I have a custom recovery on my S4 and Odin detects my S4 without a problem, meaning something else is causing your connection woes. Obviously, make sure you're in download mode first (hold down the volume down, home, power keys), which wouldn't be affected by a custom recovery, and change USB ports until Odin does recognize the device. Then flash the stock ROM again to restore the S4 to working order.
Strephon Alkhalikoi said:
Odd. I have a custom recovery on my S4 and Odin detects my S4 without a problem, meaning something else is causing your connection woes. Obviously, make sure you're in download mode first (hold down the volume down, home, power keys), which wouldn't be affected by a custom recovery, and change USB ports until Odin does recognize the device. Then flash the stock ROM again to restore the S4 to working order.
Click to expand...
Click to collapse
the thing is it bypassed download mode straight into the recovery so it didnt recognize it at all. Maybe it was because it had a non rooted recovery? Anyway i rooted the phone with kingoroot which on the one hand it worked on the other hand the phone laggs like hell but it wiped the custom recovery somehow so i got samsung's download mode back flashed cf auto root but it doesnt update su binary so thats my problem now . The phone is a 4.4.2 firmware so should i Flash first lollipop and then root it or flash a recovery to install the su binary from there?
CostasV23 said:
the thing is it bypassed download mode straight into the recovery so it didnt recognize it at all. Maybe it was because it had a non rooted recovery? Anyway i rooted the phone with kingoroot which on the one hand it worked on the other hand the phone laggs like hell but it wiped the custom recovery somehow so i got samsung's download mode back flashed cf auto root but it doesnt update su binary so thats my problem now . The phone is a 4.4.2 firmware so should i Flash first lollipop and then root it or flash a recovery to install the su binary from there?
Click to expand...
Click to collapse
Based on your first post and this post I have come to the conclusion that you have absolutely no idea what you are doing. You are mixing everything up. And I mean everything.
- A non rooted recovery? What is that? It doesn't excist. A recovery has nothing to do with root.
- Because you had a custom recovery Odin doesn't detect it? Completely impossible. A custom recovery has nothing to do with Odin detecting or not detecting.
- Wiping the recovery and getting download mode back? Dude that's impossible. Download mode and recovery are two completely different things.
1. Flash Lollipop if you want Lollipop. With .pit and re-partition.
2. Perform a factory reset.
3. Flash cf-auto root.
That's all there is to it.
Lennyz1988 said:
Based on your first post and this post I have come to the conclusion that you have absolutely no idea what you are doing. You are mixing everything up. And I mean everything.
- A non rooted recovery? What is that? It doesn't excist. A recovery has nothing to do with root.
- Because you had a custom recovery Odin doesn't detect it? Completely impossible. A custom recovery has nothing to do with Odin detecting or not detecting.
- Wiping the recovery and getting download mode back? Dude that's impossible. Download mode and recovery are two completely different things.
1. Flash Lollipop if you want Lollipop. With .pit and re-partition.
2. Perform a factory reset.
3. Flash cf-auto root.
That's all there is to it.
Click to expand...
Click to collapse
What I meant was that I accidentally flashed the recovery tar.md5 file before cf-auto-root and it wasn't working . aside that I get an su binary update error is there a fix for that?
CostasV23 said:
What I meant was that I accidentally flashed the recovery tar.md5 file before cf-auto-root and it wasn't working . aside that I get an su binary update error is there a fix for that?
Click to expand...
Click to collapse
Root and recovery are two unrelated things. You don't need root for a custom recovery and you don't need a custom recovery to root.
I would start with a clean install since you used Kingoroot and cf auto-root.
Flash a stock rom with re-partition and .pit. Then only use cf auto-root.
Lennyz1988 said:
I would start with a clean install since you used Kingoroot and cf auto-root.
Flash a stock rom with re-partition and .pit. Then only use cf auto-root.
Click to expand...
Click to collapse
If I flash the official lollipop firmware via odin will it work you mean ? (Sorry for noob question ) also about that .pit I haven't found anywhere a .pit file is it necessary ?
CostasV23 said:
If I flash the official lollipop firmware via odin will it work you mean ? (Sorry for noob question ) also about that .pit I haven't found anywhere a .pit file is it necessary ?
Click to expand...
Click to collapse
You can also wipe /system and /data in TWRP and then flash Lollipop firmware.
Lennyz1988 said:
You can also wipe /system and /data in TWRP and then flash Lollipop firmware.
Click to expand...
Click to collapse
Is it obligatory i wipe the system partition because odin flash rewrites it anyway or am i wrong on this one?
Also after kingroot the recovery was wiped clean for some reason
Bro my s4 GT I9505 have stock rom v5 .0.1 UHOE3.now I need rooted and install philz touch recovery so pls proper guide and file.thanks in advance.
Philz is outdated, and certain ROMs will not install with it. Use TWRP instead. For installing, it's just like installing a stock ROM through Odin. We have guides on this in the General section.

Categories

Resources