Hello
Specifically, I would like to know if someone has N750 device and successfully rooted his device! The reason I'm doing this thread is because when I had 4.3 android versions, I tried that CF auto root via Odin program and it bricked my phone. Fortunately, I was able to get my original firmware again from a specific site for samsung devices. [Egypt version, because obviously, I live in Egypt]. Now, My device has been updated to 4.4.2 and I have currently the kitkat version without any problems BUT, I want to root my phone in order to use Xpose Framework;
I want the best advice to follow for my device because I do not have the heart to take another chance since I'm not a professional programmer nor a professional developer to deal with such bricks. It was a lucky chance when I had my OS back, but I do not know what would happen in the future.
I tested many one click root softwares on PC and most of them either stuck or tell me 'successfully' without any **** in my phone. Just rebooting like an idiot and nothing happened.
Sorry for my annoying thread. It's my first post here and I hope you guys understand my English well since it's not my Native Language. Apologize another time.
Peace, Ahmed.
Phoenix 1337 said:
Hello
Specifically, I would like to know if someone has N750 device and successfully rooted his device! The reason I'm doing this thread is because when I had 4.3 android versions, I tried that CF auto root via Odin program and it bricked my phone. Fortunately, I was able to get my original firmware again from a specific site for samsung devices. [Egypt version, because obviously, I live in Egypt]. Now, My device has been updated to 4.4.2 and I have currently the kitkat version without any problems BUT, I want to root my phone in order to use Xpose Framework;
I want the best advice to follow for my device because I do not have the heart to take another chance since I'm not a professional programmer nor a professional developer to deal with such bricks. It was a lucky chance when I had my OS back, but I do not know what would happen in the future.
I tested many one click root softwares on PC and most of them either stuck or tell me 'successfully' without any **** in my phone. Just rebooting like an idiot and nothing happened.
Sorry for my annoying thread. It's my first post here and I hope you guys understand my English well since it's not my Native Language. Apologize another time.
Peace, Ahmed.
Click to expand...
Click to collapse
If you flash cf auto root for 4.4.2 base on 4.3, your device is bricked. If you make rooted. Find compatible os and model cf auto root files.
Hi guys. I'm new at forum. In case i may repeat some thread, i'm deeply sorry but i'm very desperate, 'cause i really not understanding.
Root is new for me. However in the last 3 weeks i keep learning about all of it, mainly observing this forum. I even could root another phones, purchased recently. The problem is that my Samsung is not accepting any kind of root , being programs of "one-click" or even flash recover process. I have already watched a billion tutorials but i can manage to make it work. For your information:
- One-click Programs using PC (used: Kingo Root, Root Genius, SRS and etc....)
Process starts nicelly and countdown of percentages are slow, but work. However, in some point, with all this programs, the phone reboots itself, not as the way that should be, breaking the process. So the root's not succeed.
- ODIN/CWM/Supersu
I managed to place a custom Rom using Odin and install super su using flash recovery following the same procedures as everyone. But, when phone reboots, not only the root is not available but the supersu is having that "binary error" thing. I know that this is not a problem of the program, but something odd about the rooting process.
I got all samsung drivers updated. Does someone can help me out with this blast phone? I never thought that trying to root a samsung phone would be so dificult. Never again a Samsung Phone, since i cannot be master of my own phone.
Phone model: Samsung S3 Grand duos GT i9082l
Android ver.: 4.2.2
Rooting will be very difficult at first.I also faced many problems when I first rooted my device.At last after using many apps I successfully rooted my phone using Root Genius
★ try to use non samsung usb
★ use different ports
★ make sure that you enabled usb debugging
★ try on different pc/laptop
............but later I learned how to root using odin..
But my favourite method is one click root app named kingroot mobile apk(try 3 times atleast)..
sempremelo said:
Hi guys. I'm new at forum. In case i may repeat some thread, i'm deeply sorry but i'm very desperate, 'cause i really not understanding.
Root is new for me. However in the last 3 weeks i keep learning about all of it, mainly observing this forum. I even could root another phones, purchased recently. The problem is that my Samsung is not accepting any kind of root , being programs of "one-click" or even flash recover process. I have already watched a billion tutorials but i can manage to make it work. For your information:
- One-click Programs using PC (used: Kingo Root, Root Genius, SRS and etc....)
Process starts nicelly and countdown of percentages are slow, but work. However, in some point, with all this programs, the phone reboots itself, not as the way that should be, breaking the process. So the root's not succeed.
- ODIN/CWM/Supersu
I managed to place a custom Rom using Odin and install super su using flash recovery following the same procedures as everyone. But, when phone reboots, not only the root is not available but the supersu is having that "binary error" thing. I know that this is not a problem of the program, but something odd about the rooting process.
I got all samsung drivers updated. Does someone can help me out with this blast phone? I never thought that trying to root a samsung phone would be so dificult. Never again a Samsung Phone, since i cannot be master of my own phone.
Phone model: Samsung S3 Grand duos GT i9082l
Android ver.: 4.2.2
Click to expand...
Click to collapse
Are you sure your phone model is Samsung s3 grand duos gt i 9082l? Never heard of it
NeoLogY said:
Are you sure your phone model is Samsung s3 grand duos gt i 9082l? Never heard of it
Click to expand...
Click to collapse
@NeoLogY I think he is telling about SGG i9082l......S3 and grand are 2 different classes...Only similarity is in its design....
Hi all,
Running into what I think is a firmware signing issue with a T707A. Yes, I said T707A, not T707V. I've had the device for about 48 hours now, and can't seem to get a non-carrier branded firmware on it. What confuses me is that the T707A is an AT&T device, but the error I'm getting is:
"System software not authorized by Verizon Wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help."
That tells me that using the dd method of twrp installation at least wrote correctly, and that the device is rooted. dd was run via adb shell. Instructions were taken from here --> twrp / devices / samsunggalaxytabs84lte.html
I've also tried Odin (3.12.3 and 3.10.6) on 3 different machines (Win 8.1, Vista, XP - Vista and XP being clean loads with good drivers) and am using the OEM USB cable. Device is charged to about 95% or so.
I can re-flash back to 4.2.2 via Odin using the following firmware (T707AUCU1ANH9_2650391_REV00 - BL / AP / CP / CSC).
And KingoRoot has been working fine to root when I have to recover.
I have access to recovery mode (power + home + vol down) as well.
I'm not sure where to go here, and I'm trying not to leave useful information out. Input is appreciated, because my Frankentab (Nexus 7 2013 LTE) is now dead.
The bootloader is locked, you can't flash anything.
ashyx said:
The bootloader is locked, you can't flash anything.
Click to expand...
Click to collapse
That would make sense, yeah. What's a reliable way to unlock it? SuperSU complains about Knox being enabled, and fails.
Chubblez said:
That would make sense, yeah. What's a reliable way to unlock it? SuperSU complains about Knox being enabled, and fails.
Click to expand...
Click to collapse
You can't unlock bootloader, but might be able to root if that is what you are asking. I have both T800 & T707A, I have tried the instructions below on T707A with success....I haven't used it on T800 yet, but assume it is that same. I didn't start from a fresh install, I just installed Kingroot and ran the removeking scripts.
[ROOT] SM-T707A - Lollipop with SuperSu - Xposed & Debloated - Part II
http://forum.xda-developers.com/galaxy-tab-s/general/root-sm-t707a-lollipop-supersu-xposed-t3468488
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
Tried to install TWRP in order to root phone, following instructions I found online. Ended up in bootloop then tried flashing ROM using Fastboot and hard bricked the phone. Paid someone with authorized Mi account to unbrick, but they wouldn't root the phone for me.
My phone is now Android 10/MIUI 12 Indonesia ROM (supports call recording), and I still want to root it.
I have read on this forum that RN8P with Android 10 cannot be safely rooted, but that thread was from Feb 2020, so I'm wondering if anything has changed since then.
I have found this tutorial that claims to be 100% safe for rooting this phone with Android 10/MIUI 12. Can anyone comment on how safe it is?
Thanks.