So you often see coverage in the media about security bugs in Android, we saw quite a few cases in 2016. A lot of it is saying Android is insecure, your data isn't safe etc. Yet none of these 'exploits' or bugs seem to be used to help us get root access.
For example I want to root a family members Xperia M4 (locked bootloader) and there's a root method for 5.1 (although it does twrp as well which I don't want) but the Marshmallow firmware still has no root even though it is vulnerable to quadrooter and other exploits. I've also had a so far impossible challenge to root my Polaroid (RK3188) tablet on 4.4.
I'm just curious why we have multiple exploits but no-one has managed to make a root method or tool to actually use them?
This applies to lots of other phones as well, recent exploits include:
Quadrooter
Dirty Cow
Rowhammer
Related
Hello all! I am a small time developer, with extensive overall linux experience, looking to develop/discover a root exploit for the Samsung Galaxy S4 SGH-i337, running stock TouchWiz 5.0.1, baseband OC3, kernel 3.4.0-4408911, as none currently exist, without requiring the user downgrades to 4.4.2, roots, and reflashes 5.0.1 update package, while preforming an exploit to keep root. This feels like far too much effort for a root, and while i realize there has been heavy speculation lately as to whether this is how rooting will always be from now on, but i dont think it will, or should be. So I'm requesting help from any and all experienced Android Developers, hackers, modders, ROM creators, bug testers, and previous root exploit discoverers to aid me in this task, so that we may, hopefully, bring back easy rooting to owners of the Galaxy S4 who are running Android Lollipop 5.0!
P.S. I also currently posses a copy of the .su binary, as well as the SU xbin, and accompanying daemonsu file, in the event that they may be of any help, or anyone requires them.
hi !
i have a very important question about root methods :
All these recents chinese and "exotics" methods are SAFE themselves ???!!! ( vroot ,iroot .... ) ...and the last one with KINGROOT . Which are "good" ?
these apps are backdors ? they are viruses or malwares themselves ? (trojan , IMEI and datas piracy ..... )
I see lots of discusions and rumors about these apps but never REAL devellopers opinions and tests here on XDA ( for members sensitization ) ,and i think that it's necessary to clarify ,it's important !
thank ...
Kingroot was reported to harvest IMEIs.
As for the others, they are reported to be safe. The one click root methods, at least for android 4.4, were based on an exploit of android to root them.
As of 5.0, at least for my phone, there are no root methods. I had to unlock the bootloader to get a custom rom on my phone, or pre root a select firmware.
If you are feeling paranoid, use a firewall and monitor traffic.
shadowcore said:
Kingroot was reported to harvest IMEIs.
As for the others, they are reported to be safe. The one click root methods, at least for android 4.4, were based on an exploit of android to root them.
As of 5.0, at least for my phone, there are no root methods. I had to unlock the bootloader to get a custom rom on my phone, or pre root a select firmware.
If you are feeling paranoid, use a firewall and monitor traffic.
Click to expand...
Click to collapse
it's kingoroot ( http://www.kingoapp.com/ ) who was reported ?! ......but no kingroot http://www.kingroot.net/ ????
The safer method is doing it manually without 3rd party apps..
There aren't many new topics on this model so here we go,
My z3 stock came with 5.0.1 and as far as i know never (the 6616) had the 4.4 as an option. SO downgrading didn't work, so i'm stuck trying to root this with 5.0.1 and after two days of browsing this site there really doesn't seem to be a way to do so. Eventually i said $%#* it and rooted it using kingroot but after rooting it, root checker passed the root but would not give proper access when installing root apps such as busybox and the ta backup tool.
So i didn't realize that the keys ive been trying to save are useless anyways if i update android and the main reason for me going through this is i really don't like 5.0.1. Only thing i haven't really looked into doing is seeing if kingroot will let me unlock the bootloader then trying to flash an update. SO has anyone successfully updated a 6616 z3 (to 6) who didn't start off with 4.4?
Hiee Guys ! I have used lots of android phones since 10 years and also familiar with them . I always try to root every phone but a problem is that every android phone cannot be rooted . So, please anyone tell me that how i can make root for any device and how i can make twrp for any device .
Thank You in Advance......
As far as compiling TWRP, you can start with this thread. Any device such as pixels upgraded to A10 don't have TWRP so because recovery has changed drastically and development of TWRP had not yet caught up.
Root is available for any device that is rootable. Magisk does a pretty good job of covering the bases and is under active development so properly reported issues are generally addressed.
Finding an exploit to be able to root a device is a different matter. Some, like pixels, are straightforward to root since if bought from Google (not a carrier directly) they have unlockable bootloaders allowing the installation of non-stock images. On a device that does not allow the bootloader to be unlocked, an exploit to achieve root must be found. That is often the issue combined with many of these devices do not attract developers to purchase them and thus no attempts are made.
Animesh._.Mamgain said:
Hiee Guys ! I have used lots of android phones since 10 years and also familiar with them . I always try to root every phone but a problem is that every android phone cannot be rooted . So, please anyone tell me that how i can make root for any device and how i can make twrp for any device .
Thank You in Advance......
Click to expand...
Click to collapse
If the device is a device that has a locked bootloader that can not be unlocked, you will not be able to use TWRP. These devices can only be rooted if there is a rooting app or rooting program available for PC or android that has an exploit that works on the device.
If the bootloader is locked, you won't be able to install TWRP or use TWRP to root the device and you will not be able to flash a Magisk patched boot.img to achieve root.
If there are no exploits available that are proven to work on the device, you won't be able to root the device.
Sent from my SM-S767VL using Tapatalk
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.