Hey guys, I've been lurking around threads trying to gather as much information before I root my phone but just in case I brick it I wanted to ask a question.
Basically, I'm on android 5.0.1 (lollipop obviously) however my build number for my phone has been different then the one in the tutorials, I'm just wondering if I flashed files from this thread (http://forum.xda-developers.com/galaxy-s4/general/guide-t3018625) onto my phone, would there be any issue? Especially due to SuperSU being an older version as well! Thanks
Details of my phone:
Model - GT-19505
Android Version - 5.0.1
Baseband - I19505XXUHOJ3
Build Number - LRX22C.I19505XXUHOJ3
follow method 2 but instead of using Philz custom or CWM use TWRP, the other recoveries are outdated.
if you want some extra reassurance, after flashing the recovery you can take a backup of your entire phone with it (switch the memory the backup will be on to your SDcard).
then you can flash a later version of superSU like v2.68 or v2.71 via recovery as in method 2 or using odin again you can flash CFautoroot by chainfire
Method 1 also works.
Related
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
Hi guys,
Not sure of this wss covered already but i was unable to locate anything that helps
I currently have a Galaxy Note 3 n9005 international LTE version with stock kitkat installed 4.4.2. The phone is rooted which i did upon receiving it and have super user 2.0 installed. i have confirmed root with titanium back.
Now i wanted to try a custom rom and tried to install the new phillz touch recovery but observed that it kept failing in odin (tried several times) i even tried to install a custom recovery via ROM Manager which it said the update was complete but when ever i boot into recovery mode i keep get the stock android recovery.
i have search and cannot find anything that help so here i am.
My Android version N9005XXUENC2 AND Kernel version is 3.4.0-636608 dpi @SWDD5619 #1
From my understanding once u root it should have install a custom recovery. When i got the phone it came with Jelly bean 4.3 and i rooted then updated to kitkat, could this be the issue. Does that mean i have root again?
Any assistance given is greatly appreciated.
Install CWM 6.0.4.7 by Chinglu via pc odn (tar)
Then if you wantvto change to Philz, install Ohilz (zip) through custom recovery
Sent from my SM-N9005
I'm having some trouble figuring out what i need to do for custom recovery flashed twrp and couldnt get it to function for me. little bit of research found talk of sagfestrap but im stilll a little confused. can someone clarify if i need safestrap if so what version . or should i upgrade to latest firmware and start over? this is the longest ive had a device on stock firmware from samsung (couple days) lol
I too had trouble with twrp for whatever reason and have used Philz recovery since http://forum.xda-developers.com/showthread.php?t=2201860
don't worry that it is no longer being updated just use the latest version and it functions very well e.g. 6.58.7 https://goo.im/devs/philz_touch/CWM_Advanced_Edition/jflte/philz_touch_6.58.7-jflte.zip.md5 which you install using Odin
Hello all...I have to first say that I HAVE been reading A LOT before I posted this question but I am somewhat confused. I have an SM-N900V with the following details :
- Rooted with Arabic Tool
- Android 5.0
- Build OF1
- Bootloader unlocked based on instructions at http://forum.xda-developers.com/ver...l/official-note-3-verizon-bootloader-t3359370
I also have a SM-N900T for which I have been using CWM based recovery for many years and I am very happy with it. But I am not forced to change to the N900V and I have it rooted already but I am having a hard time finding the right recovery for it. I tried a philz CWM based recovery and it ended u getting the unit into a recovery bootloop so I have to flash the stock firmware from scratch and start again.
Can someone save me a few hours, and potentially more reflashes, and tell me which is the right recvery for this unit and how to install it? I am partial to CWM but I have read that it does not work. As long as I can take backups and restore them I am happy with TWRP. I have also read that SafeStrap is the only option. So again, I just need a straight answer so I can get this done.
Your feedback will be much appreciated!
thanks!
Did you mean "now forced" instead of "not forced" in the 2nd paragraph? The use later on of antecedent references such as "it" and "this phone" make it slightly confusing which phone you are talking about.
calderonr said:
I tried a philz CWM based recovery and it ended u getting the unit into a recovery bootloop so I have to flash the stock firmware from scratch and start again.
Click to expand...
Click to collapse
If you have unlocked the SM-N900V's bootloader, then a bootloop can be remedied by flashing with Odin only the partitions you need fixed, not the entire firmware set. This relieves you from having to re-customize a stock ROM and/or re-root. Moreover and more importantly having an unlocked bootloader means that your phone will no longer require blobs to be Sammy-signed: you can flash custom recoveries with Odin if you please. (You just need to learn how to create the *.tar.md5 files for Odin and you are in business - search for "Odin ustar md5")
So had you know that, you could have just prepared Odin flash tarballs for different recoveries and tried them out according to whim (It is also possible to flash a recovery from the rooted ROM as well, but you need to know how to escape from a perpetual failed recovery boot loop, I.e. : battery pull -> restart with VolDown+Home+Power -> Cancel)
I haven't ever put CWM on my SM-N900V, but can tell you that either the " hlte" or "hltevzw" variants of twrp should work just fine; as you are on OF1 firmware, the -4.4 versions should be used, e.g. twrp-3.0.2-0-hlte-4.4.img or twrp-3.0.2-0-hltevzw-4.4.img
PS Safestrap was the method of choice prior to bootloader unlock methods, and I believe does not work with OB6 or OF1 (possibly also NK1?).
.
calderonr said:
Hello all...I have to first say that I HAVE been reading A LOT before I posted this question but I am somewhat confused. I have an SM-N900V with the following details :
- Rooted with Arabic Tool
- Android 5.0
- Build OF1
- Bootloader unlocked based on instructions at http://forum.xda-developers.com/ver...l/official-note-3-verizon-bootloader-t3359370
I also have a SM-N900T for which I have been using CWM based recovery for many years and I am very happy with it. But I am not forced to change to the N900V and I have it rooted already but I am having a hard time finding the right recovery for it. I tried a philz CWM based recovery and it ended u getting the unit into a recovery bootloop so I have to flash the stock firmware from scratch and start again.
Can someone save me a few hours, and potentially more reflashes, and tell me which is the right recvery for this unit and how to install it? I am partial to CWM but I have read that it does not work. As long as I can take backups and restore them I am happy with TWRP. I have also read that SafeStrap is the only option. So again, I just need a straight answer so I can get this done.
Your feedback will be much appreciated!
thanks!
Click to expand...
Click to collapse
As long as you are rooted and have the bootloader unlocked... Use Flashify to load TWRP which is an excellent recovery and does what you wish.
See this message:
http://forum.xda-developers.com/showthread.php?p=66380697
Sent from my SM-N900V using Tapatalk
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