Hi,
My phone was recently compromised with a sophisticated RAT. The exploits the RAT used were picked up by CM security and CM said it found.
1. Towel Root Exploit
2. Fake ID Exploit - something to do with exploiting Android certificates.
The thing is I have never rooted the phone or done anything other than a factory reset and purchased it new.
I'm concerned this may have been planted by someone close to me and need information to ensure I am safe in future.
How possible is it that this was carried out physically? the hacker who planted the RAT had physical access to my phone?
There is also other evidence which I can supply which was suggesting my phone had been flashed without my knowledge as well.
Any help would be greatly appreciated.
UPDATE: I just did a factory reset and reinstalled CM and again the exploits were found. How is this possible? Is the malware embedded in my ROM?
-Tim
timmyhall83 said:
Hi,
My phone was recently compromised with a sophisticated RAT. The exploits the RAT used were picked up by CM security and CM said it found.
1. Towel Root Exploit
2. Fake ID Exploit - something to do with exploiting Android certificates.
The thing is I have never rooted the phone or done anything other than a factory reset and purchased it new.
I'm concerned this may have been planted by someone close to me and need information to ensure I am safe in future.
How possible is it that this was carried out physically? the hacker who planted the RAT had physical access to my phone?
There is also other evidence which I can supply which was suggesting my phone had been flashed without my knowledge as well.
Any help would be greatly appreciated.
UPDATE: I just did a factory reset and reinstalled CM and again the exploits were found. How is this possible? Is the malware embedded in my ROM?
-Tim
Click to expand...
Click to collapse
The are false.
Imean look at one. It is how one roots a device
The Fake ID is something else though.
Dont trust Virus warnings. They will detect anything to do with root as an exploit.
Hi,
A lot of what we do here on XDA can get reported as virus and what not... Cause a lot of what do here are hacks/exploits . I would say not to worry, but if you want to ask people that know your device and the CM you are using, I need to know your make and model to point you in the right direction. ?
KJ said:
Hi,
A lot of what we do here on XDA can get reported as virus and what not... Cause a lot of what do here are hacks/exploits . I would say not to worry, but if you want to ask people that know your device and the CM you are using, I need to know your make and model to point you in the right direction. ?
Click to expand...
Click to collapse
I've never done anything XDA related on the device though.
Device: Samsung Galaxy S4 GT-I9506
timmyhall83 said:
I've never done anything XDA related on the device though.
Device: Samsung Galaxy S4 GT-I9506
Click to expand...
Click to collapse
Foe them do anything they would would have needed to have access to your device for an extended period. Don't trust cm security. It is pointless and doesn't do anything really.
Here is a good place to learn and discuss security issues... You could browse through some of these threads or ask about your issue here...
> General discussion > Security Discussion
Some very knowledgeable members are around that section. ?
Related
Hi,
I just got my Note 3 and was annoyed by the hole knox issue so i started to read back & forward after a few hours i found this program called kingo which i liked cause i only had to install it and start the program and the rest was done for me by the program.
Here are the easy steps to rooting.
1. Install the Note 3 drivers on the PC "all i did was plug-in the phone and it was installed for me".
2. Install Kingo (LINKS REMOVED)
3. Open the program and follow the simple instructions on you monitor.
When it's done you are rooted and your knox will still be 0x0.
After this i used Odin to flash the TWRP 2.6.3.7 and the knox was still 0x0.
I then shut off the phone to reboot into TWRP and did a backup of the stock rom rooted. Once done backing up the rom i rebooted into download mode and noticed that it knox was changed to 0x1.
So if you want root on stock rom then this is the easiest solution but you wont get custom recovery nor custom roms without tripping the knox counter for now.
Great does it work with latest stock firmware mj7
Sent from my SM-N9005 using Tapatalk
Doesn't work with MJ7, as posted on their Facebook page.
I did this with MJ2
Zionator said:
I did this with MJ2
Click to expand...
Click to collapse
If you did not absolutely need a custom recovery/kernel you should have gone with URDLV and you could have kept knox 0x0
xclub_101 said:
If you did not absolutely need a custom recovery/kernel you should have gone with URDLV and you could have kept knox 0x0
Click to expand...
Click to collapse
I have no idea what you are talking about.
Zionator said:
Hi,
I just got my Note 3 and was annoyed by the hole knox issue so i started to read back & forward after a few hours i found this program called kingo which i liked cause i only had to install it and start the program and the rest was done for me by the program.
Here are the easy steps to rooting.
1. Install the Note 3 drivers on the PC "all i did was plug-in the phone and it was installed for me".
2. Install Kingo from here.
3. Open the program and follow the simple instructions on you monitor.
When it's done you are rooted and your knox will still be 0x0.
After this i used Odin to flash the TWRP 2.6.3.7 and the knox was still 0x0.
I then shut off the phone to reboot into TWRP and did a backup of the stock rom rooted. Once done backing up the rom i rebooted into download mode and noticed that it knox was changed to 0x1.
So if you want root on stock rom then this is the easiest solution but you wont get custom recovery nor custom roms without tripping the knox counter for now.
Click to expand...
Click to collapse
As far as I know Kingo is banned on XDA forums until further notice, unless they finally got approved? Not to get you paranoid or anything, but suspicious communications with a chinese server were part of the rooting method you just used.
blumsen said:
As far as I know Kingo is banned on XDA forums until further notice, unless they finally got approved? Not to get you paranoid or anything, but suspicious communications with a chinese server were part of the rooting method you just used.
Click to expand...
Click to collapse
Why is it suspicious ? I mean it's most likely downloading what's needed for rooting and bypassing the knox system.
If it was banned then there should be a post so others know about it.
I am using Zonealarm firewall and i wasn't made aware of any suspicious behaviour.
Zionator said:
Why is it suspicious ? I mean it's most likely downloading what's needed for rooting and bypassing the knox system.
If it was banned then there should be a post so others know about it.
I am using Zonealarm firewall and i wasn't made aware of any suspicious behaviour.
Click to expand...
Click to collapse
It was suspected of sending your IMEI #. Don't know the details.....
Zionator said:
Why is it suspicious ? I mean it's most likely downloading what's needed for rooting and bypassing the knox system.
If it was banned then there should be a post so others know about it.
I am using Zonealarm firewall and i wasn't made aware of any suspicious behaviour.
Click to expand...
Click to collapse
1. It is suspicious because nobody knows who Kingo are. It is suspicious because the process is not transparent and it was not known what kind of information is collected from your device (or why) and what information is received (and possibly installed on your PC/ device). The exploit that they use for rooting is also kept secret. The server's IP they use is chinese. Some of the information they collect is arguably not necessary (for example your device's IMEI). The communication with Kingo is over a facebook page. Hmm.. can't think of more suspicious things right now, but that is plenty I think
2. "It is most likely just.." yes that is true. and for 99% of users that is good enough. Myself, I will lose my job if my clients/ employers find such a huge security hole which I am aware of and ignore. But then again they also expect me to never get near the WWW with my work phone or computer, I am not allowed to have a wifi module in my work laptop! You can see why a "probably just a harmless connection to China" is just not good enough in some situations.
3. If you do a search on XDA for Kingo, you will see that all threads were closed by admins.
4. Time for you to get a new firewall, or tinker with the settings!
Zionator said:
I have no idea what you are talking about.
Click to expand...
Click to collapse
With firmware before MJ3 there is a separate method called Universal Root De La Vega (URDLV) which is a lot more transparent and which (as long as you keep updating with Mobile Odin Pro and you do not change stock kernel and stock recovery) is giving you full root while keeping your Knox 0x0 (if you had it 0x0 before URDLV).
xclub_101 said:
With firmware before MJ3 there is a separate method called Universal Root De La Vega (URDLV) which is a lot more transparent and which (as long as you keep updating with Mobile Odin Pro and you do not change stock kernel and stock recovery) is giving you full root while keeping your Knox 0x0 (if you had it 0x0 before URDLV).
Click to expand...
Click to collapse
Oh ok but i have already flashed a custom recovery and rom. To hell with the warranty. I have never liked any stock roms and i like my freedom so my knox will most likely look like 0x2 now.
Kingo : Well if it's that bad then i am sure the moderators will close this and had i known this was the issue then i wouldn't have made this thread. However i would still have used this method if i knew this before as i never stay on stock rom and after finding out about the stupid chip that cant be recoded i didn't wanna wait for someone to come with a solution in one years time so i flashed the rom and recovery and now enjoying the phone
So if the Kingo really is that bad it has been wiped from my phone when i flashed a new rom.
Does not belong in Original Development, you did not create Kingo.
Moved to General
Use at your own risk. Rooting process has been known to collect and transmit IMEI and Serial numbers to China
FNSM
Before I even read the posts and start asking questions, I would like to know one thing. That is what does that United Arab Emirates mean in the pic below, its my screen after entering "About"
and can I root my device without any sort of issues?
iTTi said:
Before I even read the posts and start asking questions, I would like to know one thing. That is what does that United Arab Emirates mean in the pic below, its my screen after entering "About"
and can I root my device without any sort of issues?
Click to expand...
Click to collapse
http://www.tra.gov.ae/mynumber.php
Regardless of TRA ID - at this point you can not root MJ7 and keep knox 0x0.
kennyglass123 said:
Does not belong in Original Development, you did not create Kingo.
Moved to General
Use at your own risk. Rooting process has been known to collect and transmit IMEI and Serial numbers to China
FNSM
Click to expand...
Click to collapse
Just FYI - but Kingo stopped collecting the IMEI numbers a few versions ago.
mvansomeren said:
Just FYI - but Kingo stopped collecting the IMEI numbers a few versions ago.
Click to expand...
Click to collapse
That is great news! Our security expert has not been available to confirm this and Kingo has not sent us any correspondence to notify us of that. Has anyone confirmed this by recording data traffic while rooting?
Ok i have been reading around the net and all the reported security issues comes back to XDA.
wmshua.com is the site the connection is sent out to but is it possible that the app connects to their servers only in order to download the appropriate phone/device drivers.
On there web site under F.A.Q's
Q. Why don't you publish your source code?
A1. We kind of hope, in the future, Kingo Android Root could generate revenue to support our staff (STILL FREE FOR USERS). We all know that, in the long run, interest alone cannot make a living. To develop better software, we need to be financially motivated aside from being driven by passion.
A2. We manage to obtain root privilege of Android by exploiting certain undisclosed vulnerabilities, which we believe would be patched in no time once made public. And that would dysfunction this software that we've worked so hard for.
Click to expand...
Click to collapse
However it pushes Chainfires SuperSU to the device's and apparently they didn't ask him for his permission to use his work.
All in all i don't think isn't a matter of security issue anymore but more likely a matter of hard fellings that they stole Chainfires SuperSU to use in there app without asking him.
Correct me if i am wrong ?
xclub_101 said:
http://www.tra.gov.ae/mynumber.php
Regardless of TRA ID - at this point you can not root MJ7 and keep knox 0x0.
Click to expand...
Click to collapse
Knox 0x0 is the warranty thingy right? I have no warranty. So whats next?
xclub_101 said:
http://www.tra.gov.ae/mynumber.php
Regardless of TRA ID - at this point you can not root MJ7 and keep knox 0x0.
Click to expand...
Click to collapse
Is it not possible to root MJ7 using knigo! or rooting MJ7 using kingo will trigger knox ?
Hey everyone,
So this is pretty straight foreward, I'm attempting to root my Galaxy Core Prime (G360T, from T-Mobile in US) and I have had absolutely zero luck finding ANYTHING related that model number.
I've found plenty of stuff here, but it is all related to the G360H, G, and even the T1 (i think?) I've tried Kingo, Odin, and a few other things and I'm getting absolutely no where.
I'm wondering if anyone out here has had any luck with rooting this device in particular, or if maybe there is something I'm missing? I'm pretty new to the idea of rooting devices but I'm a proficient technically so I'm not exactly sure what is going on.
Is it T-Mobile software or something blocking the ability to root? I can't believe there is that much of a difference between my phone and say the G360H.
Thanks in advanced for the help, as I'm totally clueless at this point.
Snlich said:
Hey everyone,
So this is pretty straight foreward, I'm attempting to root my Galaxy Core Prime (G360T, from T-Mobile in US) and I have had absolutely zero luck finding ANYTHING related that model number.
I've found plenty of stuff here, but it is all related to the G360H, G, and even the T1 (i think?) I've tried Kingo, Odin, and a few other things and I'm getting absolutely no where.
I'm wondering if anyone out here has had any luck with rooting this device in particular, or if maybe there is something I'm missing? I'm pretty new to the idea of rooting devices but I'm a proficient technically so I'm not exactly sure what is going on.
Is it T-Mobile software or something blocking the ability to root? I can't believe there is that much of a difference between my phone and say the G360H.
Thanks in advanced for the help, as I'm totally clueless at this point.
Click to expand...
Click to collapse
No man there is no blocking,its just that right now nobody developed an exploit for thta specific phone.Give it some time.
Snlich said:
Hey everyone,
So this is pretty straight foreward, I'm attempting to root my Galaxy Core Prime (G360T, from T-Mobile in US) and I have had absolutely zero luck finding ANYTHING related that model number.
I've found plenty of stuff here, but it is all related to the G360H, G, and even the T1 (i think?) I've tried Kingo, Odin, and a few other things and I'm getting absolutely no where.
I'm wondering if anyone out here has had any luck with rooting this device in particular, or if maybe there is something I'm missing? I'm pretty new to the idea of rooting devices but I'm a proficient technically so I'm not exactly sure what is going on.
Is it T-Mobile software or something blocking the ability to root? I can't believe there is that much of a difference between my phone and say the G360H.
Thanks in advanced for the help, as I'm totally clueless at this point.
Click to expand...
Click to collapse
i just orderd samsung galaxy core prime because no one is developing any thing at all for this device.I will be making root exploit and start cooking rom for this device so just wait a bit and i will be working on it.
Waiting for rooted kernel for G360T1 or G360T
Arrowblue said:
i just orderd samsung galaxy core prime because no one is developing any thing at all for this device.I will be making root exploit and start cooking rom for this device so just wait a bit and i will be working on it.
Click to expand...
Click to collapse
There are many of us using the MetroPCS version G360T1 that will gladly try any root method you get going. Feel free to contact directly if you need some testing help. While waiting for root, I tried Package Disabler Pro 3.7 that was released September 15. It works fine on the G360T1, although it says "Custom" under "Device status" in "About Device -> Status." Haven't gone to Download Mode to see if the triangle is set or not, but I'm guessing the flash counter has been tripped. I'm not worried about it too much, and it may have been tripped with some other attempt to root the device. Still, this app was just what I needed to disable all the junkware and still have a smooth working Lollipop 5.1.1 while waiting for the real goodies.
alienwarning said:
There are many of us using the MetroPCS version G360T1 that will gladly try any root method you get going. Feel free to contact directly if you need some testing help. While waiting for root, I tried Package Disabler Pro 3.7 that was released September 15. It works fine on the G360T1, although it says "Custom" under "Device status" in "About Device -> Status." Haven't gone to Download Mode to see if the triangle is set or not, but I'm guessing the flash counter has been tripped. I'm not worried about it too much, and it may have been tripped with some other attempt to root the device. Still, this app was just what I needed to disable all the junkware and still have a smooth working Lollipop 5.1.1 while waiting for the real goodies.
Click to expand...
Click to collapse
The thing is i got g3601 and its running kitkat and no update availble on it ??? so i am porting 5.1 for it.Recovery has been patched up and working kinda fine but need to fix alot of issues.normally i dont develop for mid range mobiles but my brother got one so that is why i started with this one.my first projects are z3 + and xperia lines.I will let you know when it is completed for testing.
Hmm, I thought this was for SM-G360T and the Samsung Galaxy Core Prime that is out for T-Mobile and running Lollipop 5.x. Is the G3601 a typo or different model? The MetroPCS G360T1 will work fine with the firmware and files from T-Mobile G360T because they are the same device and even same network provider. Anyway, it looks like someone was kind enough to modify the kernel source code the Samsung posted just a week or two ago. Here is the news, but be warned that it will trip the KNOX flag:
http://forum.xda-developers.com/galaxy-core/development/kernel-root-root-sm-g360t1-5-1-1-t3203522
I put my G360T1 in download mode and it still says official and no warning triangle. I mentioned that it said custom in the About Phone page after doing other terminal entries and running Package Disabler Pro 3.7. Some may want to wait to root the device until there is a deodex'd rom out there to run xposed framework. I like the slimed down stock 5.1.1 and there are a bunch of garbage programs hogging the decent entry level device resources. More news to come...
root for sm g360ti
Follow this link:
http://forum.xda-developers.com/galaxy-core/development/kernel-root-root-sm-g360t1-5-1-1-t3203522
Rooting using the same files as G360t1
I have rooted the g360t using the files from this post http://forum.xda-developers.com/galaxy-core/development/kernel-root-root-sm-g360t1-5-1-1-t3203522 which are for the g360t1 variant and it went well but you have to go to developer options and activate OEM unlocking for it to work and I did it with Odin version 1.85.
Rooting sm-g360t
Snlich said:
Hey everyone,
So this is pretty straight foreward, I'm attempting to root my Galaxy Core Prime (G360T, from T-Mobile in US) and I have had absolutely zero luck finding ANYTHING related that model number.
I've found plenty of stuff here, but it is all related to the G360H, G, and even the T1 (i think?) I've tried Kingo, Odin, and a few other things and I'm getting absolutely no where.
I'm wondering if anyone out here has had any luck with rooting this device in particular, or if maybe there is something I'm missing? I'm pretty new to the idea of rooting devices but I'm a proficient technically so I'm not exactly sure what is going on.
Is it T-Mobile software or something blocking the ability to root? I can't believe there is that much of a difference between my phone and say the G360H.
Thanks in advanced for the help, as I'm totally clueless at this point.
Click to expand...
Click to collapse
I got it rooted with king root but can't fined recovery and can't turn phone off it just bootloops how you fix that
Has anyone had SUCCESS rooting a SM-G360T device?
Snlich said:
Hey everyone,
So this is pretty straight foreward, I'm attempting to root my Galaxy Core Prime (G360T, from T-Mobile in US) and I have had absolutely zero luck finding ANYTHING related that model number.
I've found plenty of stuff here, but it is all related to the G360H, G, and even the T1 (i think?) I've tried Kingo, Odin, and a few other things and I'm getting absolutely no where.
I'm wondering if anyone out here has had any luck with rooting this device in particular, or if maybe there is something I'm missing? I'm pretty new to the idea of rooting devices but I'm a proficient technically so I'm not exactly sure what is going on.
Is it T-Mobile software or something blocking the ability to root? I can't believe there is that much of a difference between my phone and say the G360H.
Thanks in advanced for the help, as I'm totally clueless at this point.
Click to expand...
Click to collapse
My specs:
Model #: SM-360T
Android Version: 5.1.1
Baseband Version: G360TUVU1AOF9
I migrated from Nokia 521 - Windows 8.1 phone to this Android device because of the litany of apps I could use for productivity. I am highly disappointed that I am unable to revoke permissions of applications to resources I think they don't need. So, I basically use phone to make calls and text. If someone has successfully rooted THIS smartphone version, please advise. I'm a little technical, too.
Try this: https://autoroot.chainfire.eu. find your model and download the file you need, unzip it then put your phone in download mode and use odin 3.7 to send it to the phone. That outta be enough. I have not rooted this particular device in a while but I have rooted plenty of others using that method and it works like a charm every time. I just did a quick look up and your model is listed there. Give it a try and post your results.
Thank you so much, Geevil!!!
Appreciate your response.
alienwarning said:
Hmm, I thought this was for SM-G360T and the Samsung Galaxy Core Prime that is out for T-Mobile and running Lollipop 5.x. Is the G3601 a typo or different model? The MetroPCS G360T1 will work fine with the firmware and files from T-Mobile G360T because they are the same device and even same network provider. Anyway, it looks like someone was kind enough to modify the kernel source code the Samsung posted just a week or two ago. Here is the news, but be warned that it will trip the KNOX flag:
http://forum.xda-developers.com/galaxy-core/development/kernel-root-root-sm-g360t1-5-1-1-t3203522
I put my G360T1 in download mode and it still says official and no warning triangle. I mentioned that it said custom in the About Phone page after doing other terminal entries and running Package Disabler Pro 3.7. Some may want to wait to root the device until there is a deodex'd rom out there to run xposed framework. I like the slimed down stock 5.1.1 and there are a bunch of garbage programs hogging the decent entry level device resources. More news to come...
Click to expand...
Click to collapse
I'm running stock 5.1.1 on G360t and just got some root using this kernel so tanks for the help and all the fish
Hello how would one root the sm-g360t and get custom recovery on it ?
Sent from my SM-G360T using Tapatalk
I have the sm g360t1, though no computer to connect the phone to. I see this phone listed in the cf-auto root repository linked above- not sure if that method needs a computer. King root may have worked, though the root gone by when using w0lfdroid's
Kingroot removal/supersu installer. It worked on orher phones.
King root is such spyware. I really want to try something else...
ewokmojo said:
I have the sm g360t1, though no computer to connect the phone to. I see this phone listed in the cf-auto root repository linked above- not sure if that method needs a computer. King root may have worked, though the root gone by when using w0lfdroid's
Kingroot removal/supersu installer. It worked on orher phones.
King root is such spyware. I really want to try something else...
Click to expand...
Click to collapse
Yes King Root is bad. Pretty much like malware for your device. Don't use cf-auto-root either, as it's kind of a generic root and doesn't really function properly. I'm helping people constantly fix their devices after either tryung King or CF. Use Trapkernel to root the SM-G360T1 & SM-G360T. It's quick and easy and roots the device with no problems.
http://forum.xda-developers.com/showthread.php?p=62859013 Here is the recovery you should use too in case anyone's wondering. You flash it the same way as root.
http://forum.xda-developers.com/showthread.php?p=66266209
I recommend using version 3.0.1-0 though, as version 3.0.2-0 has had problem flashing certain roms for some reason.
Thanks bogarty, I was able to root and flash custom recovery on my phone with both links you provided here.. I have the T-Mobile version (SM-G360T) but everything went well
Dont know if ppl still trying to root this device but I just found out that you can download the rooting file trough chainfire for this model. Here´s the link: https://download.chainfire.eu/767/C...to-Root-cprimeltetmo-cprimeltetmo-smg360t.zip
Why do that when there is a root method for this device.
Follow this thread here for all your root needs for this device
http://forum.xda-developers.com/gal...should work just fine for the tmobile version
will this allow me to use a at&t sim card in my SM-G360T phone instead of T-Mobile
I have rooted my samsung galaxy s7 edge from sprint, G935PVPU4BQH1 with some engineering bootloader through odin. I am currently having trouble installing and running kali through the deploy apk. With some searching I found some help for setting up linux but I reached a dead end with a terminal emulator basically telling me I am not rooted with "/system/bin/sh: -su: not found" all I thought i know has been shaken and I see there is no spoon. Please help me root my galaxy s7 edge with the above software version or explain to me why I can't.
this is hard for a noob, any help is much apreciated
Please help ?
Sometimes a root doesn't take. You may have to retry as something could have gone wrong internally even if you followed instructions perfectly.
Araltd said:
Root Android 7.0 Nougat on Galaxy S7 & S7 Edge devices. YES! Supports all USA Qualcomm variants. T-mobile, AT&T, Verizon and *Sprint (*Note: Some people have reported problems with the Sprint device after root, while others have had success. As always, read the thread for detail and use at your own risk)
** THIS IS NOT FOR THE EXYNOS VERSION OF THE S7! **
Click to expand...
Click to collapse
Sprint version has reported problems.
However, I strongly advise against rooting the device due to this post. If Chainfire has issues rooting the S7 consistantly, a community expert, then any attempts at rooting are purely experimental. At this point you may be able to root the device with a real possibility of a hard brick and no logs to prevent the same for future users.
If you still would like to give it a shot, I recommend reading the links in this post and last few pages of the root thread.
TehZig said:
Sometimes a root doesn't take. You may have to retry as something could have gone wrong internally even if you followed instructions perfectly.
Sprint version has reported problems.
However, I strongly advise against rooting the device due to this post. If Chainfire has issues rooting the S7 consistantly, a community expert, then any attempts at rooting are purely experimental. At this point you may be able to root the device with a real possibility of a hard brick and no logs to prevent the same for future users.
If you still would like to give it a shot, I recommend reading the links in this post and last few pages of the root thread.
Click to expand...
Click to collapse
Thanks man I appreciate the link to that post, I still had the same error in my terminal emulator but then my dumbass figured out that there are multiple directories root can be installed in, I checked which one I had with root checker and had it fixed in the terminal, thank you
Greetings. It seems the AT&T subforum for the Galaxy S4 might be dead. I was trying to look for an up-to-date way to root this phone with Magisk, but it seems that step one isn't possible since apparently the bootloader isn't unlockable, or might not be one of the ones listed as usable. I can't check which one I have because neither adb shell nor terminal emulator recognize getprop, with the latter not allowing the punctuation. I want to see if I can use the sd card as internal storage, since apparently the Google Play app writes a lot of garbage until the available storage is only 1GB. I found that out by uninstalling its updates. What's the current modern way to use the SD card as internal storage for Android versions older than M?
Don't know what happened, but Retrial edited his post on "S4 Unified Collection!" such that the magisk rooting guide redirects to a guide for Xiaomi phones. Will that really work for the S4?
Forgive me for necro-ing but did you ever find a solution to this?
Edit: ok so I looked up (1337UCUEMK2)
which lead me to evilpenquin123's comment here
[ROOT[RECOVERY] Loki + TWRP + Motochopper CASUAL-R527b release:27May13
Update: This will not work on Build Number I337UCUAMF3 Thanks to Dan Rosenberg, aka djrbliss, this device can now be unlocked and CASUAL can make it easy as all get out. Introduction CASUAL will guide you through the process. Put...
forum.xda-developers.com
Under that was devildogs link to this thread
Safe (NOT vroot or kingo) root method for MK2
I saw this mentioned in passing on another thread and thought it was worth mentioning in its own thread. (Sorry if this has been posted in this forum already but I tried searching and couldn't find it.) K1mu has developed a safe root method...
forum.xda-developers.com
Which lead me here
Safe (NOT vroot or kingo) root method for MK2
I saw this mentioned in passing on another thread and thought it was worth mentioning in its own thread. (Sorry if this has been posted in this forum already but I tried searching and couldn't find it.) K1mu has developed a safe root method...
forum.xda-developers.com
here
[ROOT] Saferoot: Root for VRUEMJ7, MK2, and Android 4.3
Disclaimer: rooting your phone entails risk. You may brick it, cause it to catch fire, cause it to form the first node in the Skynet network, or otherwise render it inoperable. Please read the directions carefully to ensure that nothing...
forum.xda-developers.com
and here
[Q] 4.3 AT&T root
Hello all, I have a AT&T Samsung Galaxy S4 that just updated to 4.3. Can someone direct me to how I can gain root access? Also, I am assuming that noone has published a way to crack the bootloader as of yet? Thanks in advance for any help...
forum.xda-developers.com
I would like to have an unroot guide for this phone to.
Basically, what I've found in this forum is that you have to "DOWNGRADE" to NB1 (from OK3), and then you can use "SAFESTRAP" of somekind(?) to get a rom, but without unlocked bootloader. I believe, this is going back to Android 4.4.2 or something. Basically, it's forcing to downgrade significantly, which beats the purpose.
I wanted an unlocked bootloader, to get newer ROMs, to increase storage. i.e. use external SD as internal. However, it seems apps don't always allow it to be installed this way, and also causes much headaches - speed is one thing, and data corruption is another etc.
In short, there is NO existing way to circumvent unlocking bootloader. Maybe a professional hacker may do it? NSA? By that point, use that cash to get a new phone. LOL.
Disappointed that this phone is still like brand new, and has plenty more life left, like, 10 more years... it keeps working.
Hi guys, I'm lookin to root my A525F with One UI 5.0
Also looking for necessary files to disable encryption.
Also I've received November Update for my country.
I have done root my A52 4G android 13 with magisk method.
llranga said:
I have done root my A52 4G android 13 with magisk method.
Click to expand...
Click to collapse
Nice.
Can you please share the exact method you carried on?
Follow the guide here to install TWRP and disable force encryption: https://forum.xda-developers.com/t/recovery-official-twrp-3-7-for-galaxy-a52-4g-and-a72-4g.4405751/
After that just flash Magisk.
Greetings to the XDA Team and all the other good people,
I want to root my Samsung Galaxy A52 4G, and just wanted to ask where should I start so I do it successfully, without upside-down moments. I already updated my phone to the latest, so now the phone is running Android 13.
I am a beginner in this, I educated myself from some videos online and on the XDA forum and saw that I can make my device more secure with root, I can disable system and apps trackers.
So my first question is, do I need to downgrade to Android 12 so the success rate becomes higher or I can stick with Android 13 and still get success for the end goal?
My second question is if what I wrote above this is a truth.
The third question is, how do I get my device running again if rooting fails?
The forth question is, can I unroot my device if I want it at some moment?
My fifth and last question is, is rooting worthy and needed so I can achieve my goals?
I still think I know nothing and want to expand my knowledge, so I ask people who are masters in this field to help me out with this, so I can become happier.
Thanks for considering my request.
- your dear noobie user epeu.
You can do root your phone. But you should not be panic. carefully read instructions and do it with patient without skipping none of the steps.
I'm also not an expert. but i have done rooting of more than 10 phones without failing.
you have to unlock your boot loader before rooting.
I doubt about your statement about device becomes more secure with root. it depends on what you do alter followed by root. yes you can improve privacy.
also your banking apps may stop work after rooting. so you have to apply necessary modules (security fixes) before get them start working again.
if rooting failed provided phone is not hard bricked, you can flash your original firmware to restore the phone. what i always do is keeping all the original firmware ready with me before doing any rooting.
yes. you can unroot by flashing original firmware.
last question is difficult to answer. majority of people use their phones without rooting. if you want to be different, it's up to you.