Hello,
I have the Samsung Galaxy A50 (model number: SM-A505FN) and I wanted to root it with CF-Auto-Root, because I previously rooted an S5 in this way and it worked out without problems.
Now I have two questions:
1. Does the bootloader have to be unlocked because I read in other forums that you only have to unlock it if you want to get custom recoveries or OS.
As the description of CF-Auto-Root says, I want to stay as close as possible to the stock and only give apps root rights. I also want to keep getting OTA-updates and I don't want my phone to be wiped because I've already set everything up.
2. On the Firmware.Mobi page, to which you will be redirected if you go to ChainFires homepage, there are 3 Galaxy A50's listed, but with the model numbers SM-A505F, SM-A505U1 and SM-A505W (all without "fn" at the end unlike my modell number). Now to my question: Can I use one of these or do complications arise? If so, which one should I take?
Thank you in advance for future answers!
Kind regards,
Shademaster639
It's an English forum
I hope i am right but translated from german to english using google translate.
I have the Samsung Galaxy A50 (model number: SM-A505FN) and I wanted to root it with CF-Auto-Root, because I previously rooted an S5 in this way and it worked without problems.
Now I have two questions:
1. Must the bootloader be deactivated because I read in other forums that you only have to deactivate the bootloader if you want to get custom recoveries or OS.
As the description of CF-Auto-Root says, I want to stay as close as possible to the floor and only give apps root rights. I also want to keep getting OTA updates and I don't want my phone to be wiped because I've already set everything up.
2. On the Firmware.Mobi page, to which you will be redirected if you go to ChainFires homepage, there are 3 Galaxy A50's listed, but with the model numbers SM-A505F, SM-A505U1 and SM-A505W (all without "fn" on End, as with my model number). Now to my question: Can I use it or do complications arise? If so, which one should I take?
Thank you in advance for future answers!
Kind regards
Shademaster639
Lol, just recognized that the forum is english. I didn't think about this as I wrote the entry. The translation @spawnlives gave fits my question. Sorry for my mistake!
EDIT: I've edited my entry now to english.
Shademaster639 said:
Hello,
I have the Samsung Galaxy A50 (model number: SM-A505FN) and I wanted to root it with CF-Auto-Root, because I previously rooted an S5 in this way and it worked out without problems.
Now I have two questions:
1. Does the bootloader have to be deactivated because I read in other forums that you only have to deactivate the bootloader if you want to get custom recoveries or OS.
As the description of CF-Auto-Root says, I want to stay as close as possible to the stock and only give apps root rights. I also want to keep getting OTA-updates and I don't want my phone to be wiped because I've already set everything up.
2. On the Firmware.Mobi page, to which you will be redirected if you go to ChainFires homepage, there are 3 Galaxy A50's listed, but with the model numbers SM-A505F, SM-A505U1 and SM-A505W (all without "fn" at the end unlike my modell number). Now to my question: Can I use one of these or do complications arise? If so, which one should I take?
Thank you in advance for future answers!
Kind regards,
Shademaster639
Click to expand...
Click to collapse
I have not used cf auto root.
On earlier version of Android I used a different root method, now am using magisk on android version 9
Since cf auto root ( now SuperSu ) has not been updated for a while use of it on current Android version may not work.
Generally bootloader needs to be unlocked as rooting phones is a modification to the original firmware. Generally with Samsung, modifications to the phone OTA updates won't be possible. To update phone you will have to flash with odin then root again.
For point 2 I am not sure. If you are going to try it maybe use F model number. I think the U1 and W are for snapdragon variants not Eyxnos variants.
If you haven't read them yet these threads maybe of some help.
https://forum.xda-developers.com/showthread.php?t=1980683
https://forum.xda-developers.com/android/development/firmware-mobi-t3675896/page43
Note: Before trying anything always backup up your phone first.
As I have said I have not used cf auto root so maybe not able to help to much.
spawnlives said:
I have not used cf auto root.
On earlier version of Android I used a different root method, now am using magisk on android version 9
Since cf auto root ( now SuperSu ) has not been updated for a while use of it on current Android version may not work.
Generally bootloader needs to be unlocked as rooting phones is a modification to the original firmware. Generally with Samsung, modifications to the phone OTA updates won't be possible. To update phone you will have to flash with odin then root again.
For point 2 I am not sure. If you are going to try it maybe use F model number. I think the U1 and W are for snapdragon variants not Eyxnos variants.
If you haven't read them yet these threads maybe of some help.
https://forum.xda-developers.com/showthread.php?t=1980683
https://forum.xda-developers.com/android/development/firmware-mobi-t3675896/page43
Note: Before trying anything always backup up your phone first.
As I have said I have not used cf auto root so maybe not able to help to much.
Click to expand...
Click to collapse
Thank you for your quick answer.
I am a newbie regarding rooting as I rooted my phone years ago and I just followed some instructions by chainfire.
1. It would be kind if you could explain a bit more detailed what you mean with "flashing with odin then root again".
2. How do I backup my phone optimally?
Kind regards
Shademaster639
Shademaster639 said:
Thank you for your quick answer.
I am a newbie regarding rooting as I rooted my phone years ago and I just followed some instructions by chainfire.
1. It would be kind if you could explain a bit more detailed what you mean with "flashing with odin then root again".
2. How do I backup my phone optimally?
Kind regards
Shademaster639
Click to expand...
Click to collapse
Samsung firmware can be downloaded from the internet or using PC apps. Generally if needed to flash firmware with Odin it will revert back to stock rom.So generally any modifications done to the phone ( ie: custom recovery,root,customs Rom's etc ) will be reverted back to stock firmware.
So if the phone is modifiied and you want upgrade to lastest firmware you would flash with Odin and then you would have to modify you phone again.
From a backup point of view I don't really have any non root method that I use. I mainly use custom recovery ( TWRP ) to backup when making changes to the phone ( except for firmware upgrades ). You could try something like a cloud backup service or try Samsung Smart Switch. There are also apps ( like on play store ) that will do backups up as well ( keep/copy backup's on SD card or PC ).
spawnlives said:
Samsung firmware can be downloaded from the internet or using PC apps. Generally if needed to flash firmware with Odin it will revert back to stock rom.So generally any modifications done to the phone ( ie: custom recovery,root,customs Rom's etc ) will be reverted back to stock firmware.
So if the phone is modifiied and you want upgrade to lastest firmware you would flash with Odin and then you would have to modify you phone again.
From a backup point of view I don't really have any non root method that I use. I mainly use custom recovery ( TWRP ) to backup when making changes to the phone ( except for firmware upgrades ). You could try something like a cloud backup service or try Samsung Smart Switch. There are also apps ( like on play store ) that will do backups up as well ( keep/copy backup's on SD card or PC ).
Click to expand...
Click to collapse
If I got it right, you root your phone by flashing a modified AP-file with Odin, so if I want stock firmware back, I have to flash the original firmware?
Shademaster639 said:
If I got it right, you root your phone by flashing a modified AP-file with Odin, so if I want stock firmware back, I have to flash the original firmware?
Click to expand...
Click to collapse
Basically yes. Stock firmware will generally replace any modifications done to the phone.
spawnlives said:
I have not used cf auto root.
On earlier version of Android I used a different root method, now am using magisk on android version 9
Since cf auto root ( now SuperSu ) has not been updated for a while use of it on current Android version may not work.
Generally bootloader needs to be unlocked as rooting phones is a modification to the original firmware. Generally with Samsung, modifications to the phone OTA updates won't be possible. To update phone you will have to flash with odin then root again.
For point 2 I am not sure. If you are going to try it maybe use F model number. I think the U1 and W are for snapdragon variants not Eyxnos variants.
If you haven't read them yet these threads maybe of some help.
https://forum.xda-developers.com/showthread.php?t=1980683
https://forum.xda-developers.com/android/development/firmware-mobi-t3675896/page43
Note: Before trying anything always backup up your phone first.
As I have said I have not used cf auto root so maybe not able to help to much.
Click to expand...
Click to collapse
CF auto root uses modified firmware and requires an unlocked bl if it even works.. if he wants root he will have to unlock the BL. Also to add, CF auto root uses SuperSU, it hasn't become SuperSU.. in fact, CF stands for ChainFire if I'm not mistaken who made SuperSU.. the auto root basically pre-rooted/patched firmware similar (but different of course) as magisk patching firmware with root. You are correct though that it might not work on newer devices/OS with system as root and ram disk in recovery or on system etc etc.
Also, the A505U A505U1 A505W A505FN or w.e models are all Exynos, not snapdragon. He will be taking a risk though flashing firmware from a different model so he better be prepared to fix it if it doesnt work. His best bet is to stick to his variant. I am sure if he looks around a bit he'll find all he needs. Last comment, the U and U1 models in USA are not BL unlockable. They are exynos but still locked in the USA.
elliwigy said:
CF auto root uses modified firmware and requires an unlocked bl if it even works.. if he wants root he will have to unlock the BL. Also to add, CF auto root uses SuperSU, it hasn't become SuperSU.. in fact, CF stands for ChainFire if I'm not mistaken who made SuperSU.. the auto root basically pre-rooted/patched firmware similar (but different of course) as magisk patching firmware with root. You are correct though that it might not work on newer devices/OS with system as root and ram disk in recovery or on system etc etc.
Also, the A505U A505U1 A505W A505FN or w.e models are all Exynos, not snapdragon. He will be taking a risk though flashing firmware from a different model so he better be prepared to fix it if it doesnt work. His best bet is to stick to his variant. I am sure if he looks around a bit he'll find all he needs. Last comment, the U and U1 models in USA are not BL unlockable. They are exynos but still locked in the USA.
Click to expand...
Click to collapse
Thanks.
Appreciate the insight and the clarification.
Hopefully @Shademaster639 will pay attention to your post.
O/T: should say thanks also to the exploits made even though I don't have a ( US ) snapdragon variant on other devices.
elliwigy said:
CF auto root uses modified firmware and requires an unlocked bl if it even works.. if he wants root he will have to unlock the BL. Also to add, CF auto root uses SuperSU, it hasn't become SuperSU.. in fact, CF stands for ChainFire if I'm not mistaken who made SuperSU.. the auto root basically pre-rooted/patched firmware similar (but different of course) as magisk patching firmware with root. You are correct though that it might not work on newer devices/OS with system as root and ram disk in recovery or on system etc etc.
Also, the A505U A505U1 A505W A505FN or w.e models are all Exynos, not snapdragon. He will be taking a risk though flashing firmware from a different model so he better be prepared to fix it if it doesnt work. His best bet is to stick to his variant. I am sure if he looks around a bit he'll find all he needs. Last comment, the U and U1 models in USA are not BL unlockable. They are exynos but still locked in the USA.
Click to expand...
Click to collapse
I have unlocked my bootloader now since I had to do it nevertheless. I couldn't use cf-auto-root since there was no modified firmware for my device (sm-a505fn) listed on firmware.mobi. I tried rooting my phone using the latest version of magisk (v20.x) now, got random bootloops though. So I flashed my device back to stock with the original samsung firmware.
@spawnlives
1. Could you suggest me a video/forum entry/method that worked for rooting the a50 (SM-A505FN)? Is it recommended to install TWRP or just root with Magisk?
2. Are the newer devices protected with something like a "hidden OEM unlock" as I saw some videos about it how to deactive it? You are supposed to see this if this appears in your download mode: "KG STATE: Prenormal"?
Thank you in advance for future answers!
Kind regards
Shademaster639
EDIT: I have tried to root my phone now with latest Magisk version v20.x, but I got random bootloops. Same with version v19.3, which should work stable on a50 referring to this post: https://forum.xda-developers.com/galaxy-a50s/how-to/guide-root-galaxy-a50s-magisk-v19-3-t4001271
Kind regards
Shademaster639
Shademaster639 said:
@spawnlives
1. Could you suggest me a video/forum entry/method that worked for rooting the a50 (SM-A505FN)? Is it recommended to install TWRP or just root with Magisk?
2. Are the newer devices protected with something like a "hidden OEM unlock" as I saw some videos about it how to deactive it? You are supposed to see this if this appears in your download mode: "KG STATE: Prenormal"?
Thank you in advance for future answers!
Kind regards
Shademaster639
EDIT: I have tried to root my phone now with latest Magisk version v20.x, but I got random bootloops. Same with version v19.3, which should work stable on a50 referring to this post: https://forum.xda-developers.com/galaxy-a50s/how-to/guide-root-galaxy-a50s-magisk-v19-3-t4001271
Kind regards
Shademaster639
Click to expand...
Click to collapse
From you private message
Magisk has 2 parts to it.
Magisk- root method
Magisk Manager - control panel for magisk.
Magisk Manager is an apk app so it will show up regardless whether you phone is rooted or not ( except safe mode ).
Not having your device I not sure about you reboot issues. While doing a quick search there are issues posted here on xda and on Google about it. If i see anything useful I let you know.
KG and RMM states ( checked in download mode ) is a extra lock to prevent modifying your phone. I don't know if it effects every Samsung device though. So basically if KG and/or RMM state is showing Prenormal it will prevent modifying your phone.
Some more info from here
https://forum.xda-developers.com/sa...w-to/guide-root-install-twrp-samsung-t3747535
spawnlives said:
From you private message
Magisk has 2 parts to it.
Magisk- root method
Magisk Manager - control panel for magisk.
Magisk Manager is an apk app so it will show up regardless whether you phone is rooted or not ( except safe mode ).
Not having your device I not sure about you reboot issues. While doing a quick search there are issues posted here on xda and on Google about it. If i see anything useful I let you know.
KG and RMM states ( checked in download mode ) is a extra lock to prevent modifying your phone. I don't know if it effects every Samsung device though. So basically if KG and/or RMM state is showing Prenormal it will prevent modifying your phone.
Click to expand...
Click to collapse
I know that Magisk Manager will show up regardless whether my phone is rooted as I just installed it on my phone (like any other apk/app). I was asking if there was a way to fix the bootloop with the manager.
I checked if the bootloader is unlocked by going into the odin/download mode [VOLUME UP] + [VOLUME DOWN] and it showed: KG STATE: checking.
(Comment under a video of @AndroidHowTo: https://www.youtube.com/watch?v=zqbu7jCmeMY
@AndroidHowTo OK But Now I Have Another Problem
your video ( KG STATE:Checking) but its Must be (KG STATE:NORMAL)
Until it is solved
AndroidHowTo:
If your device KG State = Checking it means the status is normal / unlocked bootloader. it different with RMM State)
Shademaster639 said:
I know that Magisk Manager will show up regardless whether my phone is rooted as I just installed it on my phone (like any other apk/app). I was asking if there was a way to fix the bootloop with the manager.
I checked if the bootloader is unlocked by going into the odin/download mode [VOLUME UP] + [VOLUME DOWN] and it showed: KG STATE: checking.
(Comment under a video of @AndroidHowTo:
@AndroidHowTo OK But Now I Have Another Problem
your video ( KG STATE:Checking) but its Must be (KG STATE:NORMAL)
Until it is solved
AndroidHowTo:
If your device KG State = Checking it means the status is normal / unlocked bootloader. it different with RMM State)
Click to expand...
Click to collapse
KG state - prenormal
and / or
RMM state - prenornal
Problems with modifying phone.
KG state - checking
RMM state - normal or disappeared
Allows modifying phone.
For want of better terminology they are separate keys to the same lock.
There are plenty of sites regarding this:
https://chimeratool.com/fr/docs/sam...onitoring-and-management-rmm-unlock-functions
Related
Hi Guys,
I am really new to the rooting customary process. Pardon me if there are information that I am not aware of. Okay, I always wanted to root to install apps that were restrictive to what I want and how to manage the phone properly. But I bought my Note 2 in Singapore, which is why I was hesitating as most of the guides were for AT&T and other American phone companies.
I was hesitating but a friend of me referred me to a very simple clip to root with using Odin
Needless to say, I rooted the phone and was able to install the couple of applications I wanted though there were a few I still couldn't find replacements for (Market Unlocker, AdAway).
However, I find myself not being to use ROM Manager to backup and change ROMS and being different with how normal people rooted. I think it has got to do with the how I had my phone rooted.
Please advice how I can place myself in what the general public is using as it would be easier for me to configure the phone if I were to try looking for assistance in the future.
Should I unroot and root using the XDA developer suggested way (I found the clip on YouTube but it wasn't for the firmware 4.1.2, thus I hesitated) ? After rooting my phone says its firmware is 4.1.1
Actually, if someone could also answer me whether
1) I can update my phone after rooting or do I need to unroot and update and root it again ?
2) Is the furthest update for Note 2 is 4.1.2 and in order to go for further updates I need to root ?
Again, pardon my knowledge on rooting. Thanks
McBrand said:
Hi Guys,
I am really new to the rooting customary process. Pardon me if there are information that I am not aware of. Okay, I always wanted to root to install apps that were restrictive to what I want and how to manage the phone properly. But I bought my Note 2 in Singapore, which is why I was hesitating as most of the guides were for AT&T and other American phone companies.
I was hesitating but a friend of me referred me to a very simple clip to root with using Odin
Needless to say, I rooted the phone and was able to install the couple of applications I wanted though there were a few I still couldn't find replacements for (Market Unlocker, AdAway).
However, I find myself not being to use ROM Manager to backup and change ROMS and being different with how normal people rooted. I think it has got to do with the how I had my phone rooted.
Please advice how I can place myself in what the general public is using as it would be easier for me to configure the phone if I were to try looking for assistance in the future.
Should I unroot and root using the XDA developer suggested way (I found the clip on YouTube but it wasn't for the firmware 4.1.2, thus I hesitated) ? After rooting my phone says its firmware is 4.1.1
Actually, if someone could also answer me whether
1) I can update my phone after rooting or do I need to unroot and update and root it again ?
2) Is the furthest update for Note 2 is 4.1.2 and in order to go for further updates I need to root ?
Again, pardon my knowledge on rooting. Thanks
Click to expand...
Click to collapse
Please do more research before doing anything but I would question if you have a custom recovery installed? You could use GooManager on the market to install a custom recovery (Open GooManager -> menu -> "Install OpenRecoveryScript") but check your phone model number first and make sure it matches the file you are about to flash. This would enable you to work with flashing and such. Also check your model number I believe the Verizon phones have locked bootloaders and don't know if your will or not (I believe this adds steps to flashing a custom recovery.) Wish I could be of more help.
Hi guys,
I am new to the xda forums and I have been researching about rooting my note 10.1 2014 p600 (WIFI). I have three questions about rooting my device.
1. How would I update my tab with root? I heard you can't get OTA updates.
2. What is the best and safest way to root?
3. How do I get TWRP and is it good?
I haven't installed knox on it yet and I am a beginner to linux and have done research so I know what root is.
dudeian said:
Hi guys,
I am new to the xda forums and I have been researching about rooting my note 10.1 2014 p600 (WIFI). I have three questions about rooting my device.
1. How would I update my tab with root? I heard you can't get OTA updates.
2. What is the best and safest way to root?
3. How do I get TWRP and is it good?
I haven't installed knox on it yet and I am a beginner to linux and have done research so I know what root is.
Click to expand...
Click to collapse
Ok, First, for the p600 if you root, you will trip Knox which will void your warranty and there is no way around this and this is the only way to root your model (p600), If you don't care about warranty then continue...
1) Download this file https://dl.dropboxusercontent.com/u/11938873/CF-Auto-Root-lt03wifi-lt03wifixx-smp600.zip then unzip, you will see this file CF-Auto-Root-lt03wifi-lt03wifixx-smp600.tar.md5.
2) Turn Off Tablet, Hold Volume Down + Power. Follow the instructions on the screen to get to download mode (Odin mode).
Rooting Instructions
1.Flash the CF-Auto-Root-lt03wifi-lt03wifixx-smp600.tar.md5 file with Odin v3.09 (put in AP slot, don't change any other settings, click start)
2.Let it do its trick! boot up then go to play store download and install supersu in order to update supersu to the latest binary.
3. Boot back into Odin mode and flash TWRP version 2.6.3.3 found here https://goo.im/devs/OpenRecovery/lt03wifiue/
That's all!
buhohitr said:
Ok, First, for the p600 if you root, you will trip Knox which will void your warranty and there is no way around this and this is the only way to root your model (p600), If you don't care about warranty then continue...
1) Download this file then unzip, you will see this file CF-Auto-Root-lt03wifi-lt03wifixx-smp600.tar.md5.
2) Turn Off Tablet, Hold Volume Down + Power. Follow the instructions on the screen to get to download mode (Odin mode).
Rooting Instructions
1.Flash the CF-Auto-Root-lt03wifi-lt03wifixx-smp600.tar.md5 file with Odin v3.09 (put in AP slot, don't change any other settings, click start)
2.Let it do its trick! boot up then go to play store download and install supersu in order to update supersu to the latest binary.
3. Boot back into Odin mode and flash TWRP version 2.6.3.3 found here
That's all!
Click to expand...
Click to collapse
Thanks! This is great help.
buhohitr said:
Ok, First, for the p600 if you root, you will trip Knox which will void your warranty and there is no way around this and this is the only way to root your model (p600), If you don't care about warranty then continue...
Click to expand...
Click to collapse
Knox is just a shortcut to the install link, Does this mean it's not installed or is the shortcut just extras (I don't know how to post screenshots).
dudeian said:
Knox is just a shortcut to the install link, Does this mean it's not installed or is the shortcut just extras (I don't know how to post screenshots).
Click to expand...
Click to collapse
I don't understand what you are saying???
When I said tripped Knox void warranty is that your device detected that you installed unauthorized software which tripped the knox counter. You can see this by boot into download mode (Odin mode) and you should see a line like this:
Warranty bit: 1 (factory is 0x0)
I hope that what you're asking!
buhohitr said:
I don't understand what you are saying???
When I said tripped Knox void warranty is that your device detected that you installed unauthorized software which tripped the knox counter. You can see this by boot into download mode (Odin mode) and you should see a line like this:
Warranty bit: 1 (factory is 0x0)
I hope that what you're asking!
Click to expand...
Click to collapse
Yup.
ok, now i'm getting confused.
my p600 is still on 4.3 jellybean. but from what i read, as long as did not update to kitkat firmware, i can still unroot and reverse the warranty bit bcoz they don't have knox yet. but it'll be too late if i updated to kikat right? btw, i used cf-auto-root.
just weeks ago i rooted my p600 and flashed stock recovery, so now my p600 thinks its stock official firmware, even say so in about device.
i haven't tried unrooting it yet to confirm that i can get warrenty back by flashing back whole stock firmware bcoz i don't want to redo all settings again. but thats the impression i'm geting.
anyhow if i can't really reverse that warranty thing i don't really care anyways. i warranty my stuff better than they do it, and since i think i can still get updates, it bothers me even less if its unreversible. but in the case if i'm right, and i can reverse that warranty bit. maybe one day i'd like to update to kitkat. then what? i'll have to have knox in my system and i can't reverse warranty counter anymore?
is there a way i can update to a custom kikat firmware (one day) and not have knox so i'll still be able to get warranty back?
i kind of realized the dilemma i have here since if i own the device for more than a yr, my warranty wouldn't matter anymore. am i just thinking too much and worrying myself?
kazukiflame said:
ok, now i'm getting confused.
my p600 is still on 4.3 jellybean. but from what i read, as long as did not update to kitkat firmware, i can still unroot and reverse the warranty bit bcoz they don't have knox yet. but it'll be too late if i updated to kikat right? btw, i used cf-auto-root.
just weeks ago i rooted my p600 and flashed stock recovery, so now my p600 thinks its stock official firmware, even say so in about device.
i haven't tried unrooting it yet to confirm that i can get warrenty back by flashing back whole stock firmware bcoz i don't want to redo all settings again. but thats the impression i'm geting.
anyhow if i can't really reverse that warranty thing i don't really care anyways. i warranty my stuff better than they do it, and since i think i can still get updates, it bothers me even less if its unreversible. but in the case if i'm right, and i can reverse that warranty bit. maybe one day i'd like to update to kitkat. then what? i'll have to have knox in my system and i can't reverse warranty counter anymore?
is there a way i can update to a custom kikat firmware (one day) and not have knox so i'll still be able to get warranty back?
i kind of realized the dilemma i have here since if i own the device for more than a yr, my warranty wouldn't matter anymore. am i just thinking too much and worrying myself?
Click to expand...
Click to collapse
Yes you're confused!!. Knox has nothing to do with warranty bit, once this tripped, you can't undo doesn't matter you on 4.3 or 4.4.
I'm a little confused on a few other issues. I have read over 40 pages on another thread here about rooting etc and I couldn't find the answer to a few questions. I've just successfully rooted using the most recent instructions (P600 - CF Auto root) but in earlier instructions (about a year ago) you had to also install the stock recovery file using Odin. Is that a necessary step? Is it needed for OTA updates? Since I've read that OTA updates will unroot and possibly prevent you from rooting at all, is it best to just forget about OTAs and flash up to date files from this site? Is it also prudent to turn off auto updating in the settings.
If I'm not installing custom roms and backed up using Titanium Pro do I really need to install TWRP? Any other benefits other than nandroid? Thanks
jbarr3 said:
I'm a little confused on a few other issues. I have read over 40 pages on another thread here about rooting etc and I couldn't find the answer to a few questions. I've just successfully rooted using the most recent instructions (P600 - CF Auto root) but in earlier instructions (about a year ago) you had to also install the stock recovery file using Odin. Is that a necessary step? Is it needed for OTA updates? Since I've read that OTA updates will unroot and possibly prevent you from rooting at all, is it best to just forget about OTAs and flash up to date files from this site? Is it also prudent to turn off auto updating in the settings.
If I'm not installing custom roms and backed up using Titanium Pro do I really need to install TWRP? Any other benefits other than nandroid? Thanks
Click to expand...
Click to collapse
Once you rooted you can't use OTA update any more. So the easiest going forward is to flash TWRP and use it to flash pre-rooted rom from this site.
Thanks buhohitr
I guess I'm installing TWRP tonight. There are many versions up to 2.8 I think. Which one do you recommend for P600? I've tried searching for "installing TWRP" but there were no obvious hits like there were for rooting. Which is the key thread?
To my first question, I'm assuming that the later root methods automatically installs or leaves the stock recovery as earlier methods needed to load it. Am I right?
jbarr3 said:
I've tried searching for "installing TWRP" but there were no obvious hits like there were for rooting.
Click to expand...
Click to collapse
OK found the thread and I just read the last 55 pages (that took a while) and boy is it scary. So many problems. Touch not accurate, inverted screens, certain versions failing eg 2.7, can't access external SD card, continual looping, booting into the old recovery , OTG cables not working, time zones can't be set properly, some say turn off autoboot in odin and some say don't change default settings etc etc. the list goes on and on. I likened it to a bushfire or tornado. Some houses still stand and some don't and you want to know the silly thing here, I am an experienced computer teacher with a degree in computer science and I've upgraded firmware on over a hundred devices over the years and yet all this rooting and recovery stuff is another world. The rooting process, admittedly, was a piece of cake and the instructions for flashing TWRP seems easy too but after that there seems to be so many problems. So hit and miss.
All i want to do is load TWRP on a P600. I will only load custom ROMs when a new firmware version comes out. Can someone alleviate my fears who has successfully loaded TWRP recently on a P600 using ODIN without massive tweaking to get it going. What version TWRP did you use and did you turn off autoboot or not?
PS Have I posted this in the correct section?
Took the plunge and loaded the latest TWRP 2.8.1 and it worked perfectly except I could only back to the main SD storage and not my extSD. I ended up, as a work around, moving the backup files to the extSD drive and PC.
I think I was worried unnecessarily.
Hello all! I have just acquired a Note 10.1 2014 Edition! However, the one thing that's sort of bothering me is the lack of root. I also have a Note 3 that's rooted and it's amazing, so I would like that experience on my new tablet as well. My only fear is KNOX; Because my model is the Wi-Fi (P600) edition, there is no version of a root that keeps the KNOX flag at 0x0. With that said, I have a few questions:
1. If I root my tablet, is there any chance of me later on upgrading the system software of my device (Say, Lollipop later on when it's released)? I know OTA is out of the question when rooted.
2. Other than the KNOX applications, does the KNOX flag limit the usage of my device in any other way (for example, Miracast, HDCP, etc.)?
3. How limited am it to software changes on my phone with the KNOX flag enabled (I'm not talking apps, but system changes like bootloader, firmware, recovery, etc. Essentially, would I be able to install a custom bootloader and/or recovery after my KNOX flag is set to 0x1?)?
I have tried looking up the answers to these questions, but the sources I found have confused me. I'm not worried about my warranty either.
I also like to see those questions answered
computerlife22 said:
1. If I root my tablet, is there any chance of me later on upgrading the system software of my device (Say, Lollipop later on when it's released)? I know OTA is out of the question when rooted.
2. Other than the KNOX applications, does the KNOX flag limit the usage of my device in any other way (for example, Miracast, HDCP, etc.)?
3. How limited am it to software changes on my phone with the KNOX flag enabled (I'm not talking apps, but system changes like bootloader, firmware, recovery, etc. Essentially, would I be able to install a custom bootloader and/or recovery after my KNOX flag is set to 0x1?)?
Click to expand...
Click to collapse
1.) Odds are we will see 5.0-based ROMs before an OTA update for our specific device, so don't worry. On a previous tablet, I went from 3.2 to an OTA 4.0, then rooted and flashed a 4.1 ROM (CM10). The great part is, Toshiba never pushed anything past a horribly buggy 4.0 for it. Not only can you upgrade your software in the future, you'll have better options, more options, and (in all liklihood) earlier access.
2.) Not that I know of. I'm running all of my apps perfectly and have only had one feature not work on an Xposed module (hide WiFi on Wanam Xposed module), though I can't attribute that to KNOX in any way.
3.) I've never tried installing a custom bootloader or recovery, so unfortunately I can't answer that with any degree of certainty.
computerlife22 said:
1. If I root my tablet, is there any chance of me later on upgrading the system software of my device (Say, Lollipop later on when it's released)? I know OTA is out of the question when rooted.
Click to expand...
Click to collapse
Yes. You can always upgrade by downloading firmware via a site like sammobile.com and flashing that via ODIN, or using Kies to automatically download the latest firmware and flash it to your device. Either of those methods will result in you losing root. If a root method exists for the updated firmware, you can re-root.
computerlife22 said:
2. Other than the KNOX applications, does the KNOX flag limit the usage of my device in any other way (for example, Miracast, HDCP, etc.)?
Click to expand...
Click to collapse
No. Screen mirroring (and possibly other features, but that's the only one I know of) will refuse to work if you have a custom recovery installed. You can get around this by reflashing stock recovery, or making an edit to a system file.
computerlife22 said:
3. How limited am it to software changes on my phone with the KNOX flag enabled (I'm not talking apps, but system changes like bootloader, firmware, recovery, etc. Essentially, would I be able to install a custom bootloader and/or recovery after my KNOX flag is set to 0x1?)?
Click to expand...
Click to collapse
I don't believe there are any custom bootloaders available, but you can flash a custom ROM/recovery easily.
Decided to root... but how?
Okay, thanks guys. I've decided that I would like to take the plunge and root my tablet. However, I'm confused on how I should. What method should I use to root my tablet? I'm running KitKat 4.4.2 version NI1.
Would this still work?
http://forum.xda-developers.com/showthread.php?t=2490805
Here you go, step by step.
There are also YouTube videos on rooting our tablets (albeit with different files for an earlier version) that show you the process. I like using them when rooting devices so I can visualize the steps and actually see how it's done rather than just reading about it.
Hello,
I have a Samsung Galaxy S4(SGH-M919) with TMobile.
The android version is 4.4.4. Since i am still in the contract with TMobile,
the phone is locked with that carrier. (Btw, does this mean i have. a locked bootloader automatically??..but.i.found some on the net saying... Tmobile doesnt put locked bootloader??)
I tried to root this phone with towelroot, but it says it is not supported.
So i found an article saying this phone can be rooted by cf-auto-root with odin.
before i try, i would like ti ask something.
1. it says if the phone has locked bootloader, this rooting procedure can make the phone
brick. how do i check whether i have locked bootloader or not?
i havent installed any custom ROM .. i havent tried to root the phone other than towelroot.
Btw, i just went to download menu, though i didnt go further from there.
i saw "Write Protectiom : Enabled" ...does this mean i have locked bootloader phone?
Thanks
You don't have locked bootloader. You can use cf-auto-root just remember that you will trip your Knox flag. Other than that, there is no side effects as far as performance in hardware or software
The only root method I could get to work was CF Autoroot flashing with Odin. Just make sure you have the correct version for the T-Mobile SGH-M919. I don't believe SuperSu was included with the root. You need SuperSu installed after you get rooted. When apps want to access root files SuperSu will not allow that access w/o your permission. It's free and available on Playstore.
Jim
In regard to what OTISDOG said about the rooting, I have a MetroPCS branded M919N. I use firmware for both T-Mobile and Metro on the phone with absolutely no issues. Rooting the phone with CF-AutoRoot was a quick and painless process. Reason I rooted? To get rid of all the bloat on the phone. My battery lasts longer and is more responsive in general. I asked the reps at a local store if I would have a problem if I needed my phone to be serviced under warranty. He told me that none of his rooted customers had problems getting their phones fixed under warranty unless the phone was running a custom rom or recovery like CyanogenMod or TWRP. Your mileage may vary by your location and/or store visited.
otisdog said:
The only root method I could get to work was CF Autoroot flashing with Odin. Just make sure you have the correct version for the T-Mobile SGH-M919. I don't believe SuperSu was included with the root. You need SuperSu installed after you get rooted. When apps want to access root files SuperSu will not allow that access w/o your permission. It's free and available on Playstore.
Jim
Click to expand...
Click to collapse
*Updated 3/2017 to include same for LL updated SM-T707A*
For anyone else who has the SM-T707A (tab s 8.4" AT&T LTE version) -
Issues with this tablet:
1. Upgrading to Lollipop - seems that without an actual AT&T sim card installed, you're not going to be able to upgrade from 4.4.2 (cannot download the OTA update, and I haven't been able to find a download of the firmware online ANYWHERE).
2. Locked Bootloader - possible to carrier unlock for any compatible GMS carrier (I'm using mine with a T-mobile sim card), but seems that there is no way to unlock the bootloader/install a custom recovery.
(**NOTE: DO NOT TRY AND INSTALL TWRP OR USE THE UNLOCK/RECOVERY UTILITIES FOR THE SM-T705 ... while it seems like they would effectively be the same devices, both have exynos cpu and identical specs...I have tested out the odin-flashable methods from the development section that are for the SM-T705, and THESE WILL SOFT BRICK YOUR DEVICE. A HUGE ISSUE, SINCE THE STOCK FIRMWARE IS REALLY REALLY REALLY DIFFICULT TO FIND..)
SILVER LININGS:
1. Even if you have to stay on 4.4.2, you should be able to root with Kingo Root.
2. If you are rooted with Kingo on 4.4.2, and want to switch to SuperSU app instead of the KingoRoot one, you can try this (worked for me):
**Update 3/2017 - this will also work on LL updated SM-T707A
1. Install SuperSU app through google play store (regular install...NOT an update via recovery). This means you will now have TWO Superuser apps installed on your phone. Only the Kingo Superuser will have the authority to grant SU permissions at this point. Now open SuperSU and make sure it is installed. It should ask you to update the SU binary (you won't be able to yet, but make sure you get the prompt).
2. Download a terminal emulator app, or enable usb debugging in dev options, connect phone to pc, and open an adb shell.
3. Follow the instructions for switching to SuperSU available on android forums (search for "bakageta" +" supersu to kingo" +"android forums" ).
4. Download @bakageta's zip file and put on your sd card. Then open your terminal emulator or adb shell as root (type "su" + press enter) and run the first command: "# ./step0.sh" Remember to leave your terminal emulator open when you move on to the next step (same goes for your adb window).
5. Uninstall the Kingo Root apps (your tablet will then ~likely~ auto-reboot, closing the terminal emulator...DON'T PANIC, THIS IS OK.)
6. After your tablet boots back up, you should still have root**, but now your Superuser app will be SuperSU.
**UPDATE (3/2017, running the LL updated SM-T707A) If you are doing this on LL, you may need to also run the subsequent bakageta script, "# ./step1.sh" after the initial reboot to get SuperSU root access.
--> If anyone here knows how I can make a backup of the firmware I currently have installed (rooted stock 5.0.1) that can be used as a restore image via odin, please let me know! I'd gladly upload the file for anyone who is having trouble unbricking their devices, since the stock files are so insanely difficult to find for this particular variant of the tab s.
--Thanks to @Kingxteam
--Thanks to @bakageta for the alcatel scripts
see PM
chixvicious, did you ever managed to get those backups? I got a soft-bricked 707A and i also cant find the stock roms anywhere
PAragao said:
chixvicious, did you ever managed to get those backups? I got a soft-bricked 707A and i also cant find the stock roms anywhere
Click to expand...
Click to collapse
still not allowed to post links, but files can be found at dropbox dot com/s/mjobo2sfa53x2dv/T707AUCU1ANH9_T707AATT1ANH9_4.4.4_USA_4Files.rar?dl=0
Okay so I can confirm Galaxy Tab S 707a 8.4" LTE can be rooted in 4.4.2 with Kingo. It's goofy like kingo is , but it worked unfortunately that's not quite enough for myself as six axis never communicates w. Stock annnnd tmobile sucks and are being jerks can't use it without special plan so I'm putting my WiFi board back in. If any one wants rooted 4.4.2 unlocked motherboard......useless wasted tech here, all thanks to software restrictions.
updated for anyone else playing with these / whom it may concern if they ever google up this old ass device , I confirm on 4.4.2 707a I have successfully root with kingo and them using SUPERSUME apk I have swtiched it fully to SuperSU . Also using online nandroid backup with the 805 LTE variant patch I was able to get a full backup. I think I'm in decent shape for experimentation as I'm on the lowest order firmware and hopefully , not sure but hopefully if anything goes badly i can just update to newer firmware. Going to attempt using SAFESTRAP recovery next
SuperlativeB said:
updated for anyone else playing with these / whom it may concern if they ever google up this old ass device , I confirm on 4.4.2 707a I have successfully root with kingo and them using SUPERSUME apk I have swtiched it fully to SuperSU . Also using online nandroid backup with the 805 LTE variant patch I was able to get a full backup. I think I'm in decent shape for experimentation as I'm on the lowest order firmware and hopefully , not sure but hopefully if anything goes badly i can just update to newer firmware. Going to attempt using SAFESTRAP recovery next
Click to expand...
Click to collapse
I still have 2 of these and am constantly disappointed at how much development there is for every other variants but this one.
I got safestrap in , was able to reboot and see it but no luck due to se enforcing , I tried everything to get it to permissive but no luck. I went back to my WiFi model ha , oh well. Have to look for a 705 that has unlocked boot / better firmware
pm me if you still have that!
SuperlativeB said:
Okay so I can confirm Galaxy Tab S 707a 8.4" LTE can be rooted in 4.4.2 with Kingo. It's goofy like kingo is , but it worked unfortunately that's not quite enough for myself as six axis never communicates w. Stock annnnd tmobile sucks and are being jerks can't use it without special plan so I'm putting my WiFi board back in. If any one wants rooted 4.4.2 unlocked motherboard......useless wasted tech here, all thanks to software restrictions.
Click to expand...
Click to collapse
PM me if you still have that! I randomly have an extra (shattered screen) Tab S 8.4" without a motherboard, and would play around with trying to unlock the bootloader on it if I had a mobo to put in it!
Thanks!
SuperlativeB said:
I got safestrap in , was able to reboot and see it but no luck due to se enforcing , I tried everything to get it to permissive but no luck. I went back to my WiFi model ha , oh well. Have to look for a 705 that has unlocked boot / better firmware
Click to expand...
Click to collapse
I could help get this permissive on kitkat, but not LL or MM.
ashyx said:
I could help get this permissive on kitkat, but not LL or MM.
Click to expand...
Click to collapse
What are your thoughts ? It's def still kitkat , but I've tried init'd stuff and all sorts crap. If i got permissive i could possibly get safestrap to boot and then try out roms intended for the regular LTE variant. It is just kind of useless for me as T-mobile it's device Id as tablet so they lock it out then if i just wanted to use it WiFi the TouchWiz stuff kills remote controls like six axis and stuff. Id prob use it daily if i could get past device id pickups / safestrap a way into better rom
anyone have the 6.0.1 firmware?