Related
On the 32 GB:
On this one it downloads the .zip but when I attempt to flash it, it does not do anything; here are the reasons/issues:
*On this one the volume works backwards. That should be the download I made which is an older one.
*I did not partition this tablet because I figured it has the memory to operate properly.
*About tablet:
Android version 4.1.2
Cyanogenmod version: 10-20130418-EXPERIMENTAL-tenderloin-FOR_LIMITED_TESTING_ONLY_CAM
Build: Thu Apr 18 00:04:59 CDT 2013
Memory 864 MB
model no. cm-tenderloin
CPU ARMv7, Processor rev2 (V7l)
*TWRP message: "Root is required for this app" WTH??
*ROM Manager msg:"You must root your phone for ROM Manager to function. Superuser was not found at "/system/bin/su" or "/system/xbin/su". Use Google Search on your computer to find instructions to root your phone --->OK.
*SuperUser: I have four logs, 10/3/2013 Voodoo OTA RootKeeper; three are allowed, one is created.
*Voodoo OTA Root Keeper v. 2.0.3
*Checked statuses on this app: Superuser app installed, /system supports root protection.
Hope this information helps, if this causes issues with you guys when it comes to following different solutions I NEED THEM IN A SPECIFIC ORDER (not shouting but stating the obvious) for the flash to function properly on the tablet. I deleted apps and skimmed through the File Manager and deleted unnecessary files but did not touch anything that was downloaded with the Android.
Please please be kind with me! I downloaded with YouTube and my family has enjoyed the tablet tremendously now that it has Android, especially with our Chromecast.
chicawhyte
32 GB Stuck At Order And Flash Selected
UPDATE: 16 GB Updated Successfully! Didn't do anything in particular, it just worked .
Now the 32 GB is stuck on the same spot as before, where it doesn't allow me to flash. Same issues at above. I have combed the threads but I am concerned on what to fix first, in order for the tablet to work smoothly. If you believe I have to flash from the desktop, please let me know.
Thanks,
chicawhyte
Bypassed TWRP Root Message, Read Below
Directory:
TWRP/sdcard/goomgr
It says that it's installing my update plus a new gapps file, I selected:
Backup
Wipe Cache
Wipe Dalvik
I downloaded OpenRecovery--->never ran, it's not inside the GooMgr folder. There's that arrow swipe to unlock, it does not do anything. Left or right, still it says it's downloading both files.
chicawhyte
MODERATOR: Please close this thread
Update:
Roland sent me a message to flash that tablet from my computer then it will fix the issues, and I did. After this happened, Goo.im popped that I had a new OS update, and it flashed on the tablet.
Thanks to Roland for the helpful information. Now both are up to date with the same updates and running smoothly :victory:
chicawhyte
Hello everyone
This is my first post on XDA, though i have been faithfully following the XDA forums throughout my rooting process and you guys have been amazing help since I started.
I have been scouring the entire XDA site and the interweb for answers, but to no avail...
My situation as detailed as i can make it: I rooted with iRoot about a month ago, everything went smoothly and i was greeted with a Kinguser app, everything was so new and strange, after a few days of intense reading I on XDA I was ready to take advantage of the new found power I had unlocked. After a lot of apps and optimization (greenify, setcpu etc. ) I was ready for the next step.
My device: Huawei Ascend P, Android version 4.4.2, Emotion UI 2.3, Build : P7-L10V100R001C00B121SP01, I have never flashed a rom (so im assuming I still use stock rom).
Problem: #1) I followed a tutorial explaining how to partition SD card (16gb) with Aparted application, Partition 1 = 6gb fat32. Partition 2 = 10gb ext4. (Sucessfully backed up SD contents to pc, partitioning went smooth and without error)
#2) I continued with the tutorial, next step was to download link2sd, in order to mount the ext4 partition, as my phone wasn't reading the ext4 partition yet, this is where the trouble started intensifying... after installing link2sd, i followed the steps to mount the ext4 partition, after a few failed attempts (Kinguser kept prompting for link2sd's root acces, even after changing from prompt to allow. Link2SD simply didnt gain root access...
#3) the tutorial then had a step 3 (manual mounting the partition via Root Explorer) I then proceeded to download Root Explorer and followed the steps explained.
***I will try to explain what i did as detailed as possible, though it is hard as i lost all browser history
#4) I copied 5 folders from the data folder (usually hidden from standard explorer) i cant recall the file names as it was a few days ago, I recall vaguely dalvik and data were partials of some folder names, i copied the folders into a folder i assumed was made by link2sd (I think it was also in the data directory, though unsure) as required by the tutorial.
#5) Then i had to select 1 of the copied files at a time in the new destination (while still using root explorer) and > options > Create link to...
#6) I went back to the original folder and selected the corresponding folder to link. ie. Linked copied dalvik to original dalvik file. A message prompt showed in root explorer in the line of : "File already exists, confirm merge and overwrite" ? i confirmed, after a brief load another prompt showed : "failed to create symbolic link, [something about not getting sufficient root access]".
#7) I saw on top left of root explorer was a toggle setting (current setting was R/o (read only)) i tapped it and it changed to (R/W read and write) and repeated step 5 and 6, 2 out of the 5 folders successfully linked (though wasnt confirmed by successful message, just the absence of the usual failure message) the other 3 refused to link, shortly after ALL of my apps started to "[app] not responding"(starting with google play store).
#8) I rebooted device (powering off and on via power button), after huawei logo a never before seen dialogue box appeared "Updating Android... [as header] and it started "updating" all my apps, one at a time, followed by updating contacts).
#9) Once booted my device was restored to less than factory defaults... no apps can install "App not installed", no apps are installed according to my device, i only have: Themes, Calendar, Clock, Email [huawei client], contacts (ONLY 3 LEFT, the ones i had on my memory card, so all my contacts have been wiped), phone manager, settings, browser, mirror, kinguser(does not serve any function currently[only record in log is Root explorer [Allow 3, forbid 0] from the date of incident], gallery, music, camera, file manager, polaris office, magic tag, weather, flashlight, calculator, notes, sound recorder, fm radio, backup, magnifier, system update, downloads, app installer, cellc, dlna.
Trouble shooting so far:
I tried doing a factory reset : Options>Backup&reset>Factory Reset. Reboots, then same happens (all app data on phone memory still there and un-wiped[verified through file manager].
After hours and countless videos and forums, my phone still hasn't booted into recovery mode (Vol +, Power button) (Vol +, vol-, powerbutton) (powerbutton, synchronized plug in of wall socket charger) none works, Huawei logo for about a minute then black screen again, tried holding for all combinations ie long press, short press n hold etc...
Also my phone doesnt allow connection via huawei pc suite app, so i have no way to fix this
Side note: Kernel version used to be dalvik, it seems to have changed and currently is :
3.0.8-00346-gd8d2e4a
[email protected] #1
Thu May 29 02:28:51 CST 2014
[a backup i had made with flashify before all rooting]
Please help me if at all possible, I have really exhausted all of my options.... I am at your mercy
Thanks in advance!
So I got around to "rooting" my "LG G4" (H525) via that one click tool called Kingroot.
So far so fine.
Pretty much all applications that require root will will allow it...
Except for one:
FlashFire....
It keeps telling me that root access was not possible,
that I shall't install SuperSU.
[However SuperSU will error out right on the start telling me to `update the binary']
=> What binary ? Why update it (just got the newest SuperSU from the Playstore)?
Trying to flash said binary using any Flashify merly showed me the lovely "your device is bricked" bugdroid...
Any idead from someone with similar FlashFire / SuperSU problems ?
Thanks in advance:
-Rye-
Do you have a custom recovery/twrp?
Sent from my HTC One M9 using Tapatalk
Nope, all stock.
(Part of the reason why this confuses me so much... I changed nothing... except for Root)
KingRoot is intentionally designed to serve two purposes. The first is to give you root access through their app. The second, which they don't warn you about, is to prevent you from managing that root access any other way than through their app.
They have written their app specifically to force you to use their root manager and to prevent you from uninstalling it and installing any other SU app. They went so far as to specifically block installation of SuperSU because they're upset that it replaces their app (which is blatantly absurd and hypocritical). If that's acceptable to you, then certainly do it their way.
However, because they place such restriction on root access (which seems to be a self-contradictory philosophy) then it directly interferes with the installation of more powerful root apps like flashing utilities and Xposed itself.
At this point there are two options. Either you can find a utility that breaks their stranglehold on your device and follow the specific instructions to remove their app and install something that's not restrictive, or you can restore your device to pre-root condition and root it again yourself using the open, non-restrictive methods made available to the community. Each method may be about as complicated as the other.
I have bought a S3 –LTE to replace my old S3 – LTE with spider web and broken frame.
OLD: GT-I9305 with Android 4.4.4, Build: KTU84P.I9305XXUFNL1
NEW: GT-I9305 with Android 4.4.4, Build: KTU84P.I9305XXUFOB2
I use the S3 for business and partially private but not for videos/music or games.
I use the phone / contacts / calender
I use gmail
I use whatsapp
I use the camera / dropbox
That’s it 99%
I copied the OLD data / apps to the NEW and added all whatsapp files/pictures …. IT WORKED !! - I should have stopped here......
But: Leaving me with 13 GB of 16GB in use (like with the OLD S3) and leaving the 64GB of SDRAM-card unused.
So I tried to install and use SDK Manager from REBELLOS / KINGO SUPER USER from KING SOFT / FOLDER MOUNT (ROOT) from MADMACK.
The KINGO SU was installed with no problems and no messages but it seemed as if it did not work.
The FOLDER MOUNT therefore did not work and I got regular system messages that google play store had to be stopped.
So I RESET TO FACTORY DEFAULT.
Then I tried CF-AUTO ROOT with Version I9305XXUFNL1_I9305VD2FNL1_VD2 together with ODIN.
This worked directly with no problems and no error messages.
But here I had the same problem I get error messages from GOOGLE PLAY STORE STOPPED. Even if I disable KNOX as SU-SUPER says.
Plus: the NEW S3 does not recognize my 64GB SDRAM anymore. I tried the 64 GB in three different SAMSUNG phones and it displayed 59 GB free there but not in my NEW S3 there it says 0.
So maybe someone can help me .
First: Do I need to get rid of the SU / ROOTed Version of my system or do I need to add additional apps and software ? What should I do ?
Second: I would like to move my old apps and data to the NEW S3
Third: I would like to move my apps and data to the unused SDRAM card.
And then there is still the question regarding the "custom binary counter: 2" and "KNOX Warranty void : 1"
What is the best way to go forward (or better backward...) ?
Best regards, Erich
First off, i want to clarify some terminology:
1. SDRAM =/= SD-Card. SDRAM = Synchronous dynamic random-access memory and SD-Card = Secure Digital Card.
2. It is SuperSU not SU-SUPER
3. custom binary counter is the number of flashes the phone underwent
4. KNOX warranty void bit is useless since i imagine your phone is out off warranty. 0x0 is not triggered, 0x1 is triggered. Think of it as a fuse in electronics and electricity.
Onwards to the actual steps i say you should do (beware, you have the newer bootloader, so i'm not that well-informed about what you can do, so bear with me):
[-find a way to downgrade to the pre-KK bootloader, if not go bellow
-flash through ODIN a KK firmware I9305XXUFOL2_I9305TPLFOL2_TPL, the region doesn't matter, then re-root it and try to force install the latest version of Play Store by uninstalling it and reinstalling it manually;] not really recommended;
- my recommended way:
1. flash a recovery through ODIN using the thread HERE;
2. get yourself a ROM from HERE, whichever you fancy, it doesn't matter.
3. get yourself the latest modem from HERE just to be safe;
4. get yourself AGNi PureSTOCK from HERE for a more customisable device;
5. or as an alternative, check out THIS thread for a stock 4.1.2 ROM with 4.1.2 GOOD bootloader. Then, if you succeed in installing and reverting to the old bootloader, then follow the steps above from 1 to 4.
6. ??? PROFIT.
If you successfully finished the above steps and have a working and stable device, use Samsung's Smart Switch app to transfer all of your stuff from the old S3 to the new one.
On the way, you may actually repair the SD card detection on the new S3.
I do not recommend using the External SD Card for applications because it is way slower than the internal one. I recommend using it as just storage. Make sure to clear cache (Settings-General-Storage, tap on Cached data and then on OK) every week.
Some apps use the external SD card as data storage, although it depends how the app is written. For the apps that support it, just go to Settings-General-Application Manager and swipe from the right to the left and then check whatever app you want to move the data to the external SD card
SDK Manager from REBELLOS is useful for developers only
Folder Mount is useful only if you have games that require you install their massive data to the internal SD card and you don't have enough space.
And as a small piece of advice, clarify stuff; "13 GB of 16GB in use" might mean two things: 13/16gb used or 13/16gb free.
Hope my 'small' post helps you.
thank you for your time and help - Alexander
Alexander_the_B0ss said:
First off, i want to clarify some terminology:
1. SDRAM =/= SD-Card. SDRAM = Synchronous dynamic random-access memory and SD-Card = Secure Digital Card.
2. It is SuperSU not SU-SUPER
3. custom binary counter is the number of flashes the phone underwent
4. KNOX warranty void bit is useless since i imagine your phone is out off warranty. 0x0 is not triggered, 0x1 is triggered. Think of it as a fuse in electronics and electricity.
Onwards to the actual steps i say you should do (beware, you have the newer bootloader, so i'm not that well-informed about what you can do, so bear with me):
[-find a way to downgrade to the pre-KK bootloader, if not go bellow
-flash through ODIN a KK firmware I9305XXUFOL2_I9305TPLFOL2_TPL, the region doesn't matter, then re-root it and try to force install the latest version of Play Store by uninstalling it and reinstalling it manually;] not really recommended;
- my recommended way:
1. flash a recovery through ODIN using the thread HERE;
2. get yourself a ROM from HERE, whichever you fancy, it doesn't matter.
3. get yourself the latest modem from HERE just to be safe;
4. get yourself AGNi PureSTOCK from HERE for a more customisable device;
5. or as an alternative, check out THIS thread for a stock 4.1.2 ROM with 4.1.2 GOOD bootloader. Then, if you succeed in installing and reverting to the old bootloader, then follow the steps above from 1 to 4.
6. ??? PROFIT.
If you successfully finished the above steps and have a working and stable device, use Samsung's Smart Switch app to transfer all of your stuff from the old S3 to the new one.
On the way, you may actually repair the SD card detection on the new S3.
I do not recommend using the External SD Card for applications because it is way slower than the internal one. I recommend using it as just storage. Make sure to clear cache (Settings-General-Storage, tap on Cached data and then on OK) every week.
Some apps use the external SD card as data storage, although it depends how the app is written. For the apps that support it, just go to Settings-General-Application Manager and swipe from the right to the left and then check whatever app you want to move the data to the external SD card
SDK Manager from REBELLOS is useful for developers only
Folder Mount is useful only if you have games that require you install their massive data to the internal SD card and you don't have enough space.
And as a small piece of advice, clarify stuff; "13 GB of 16GB in use" might mean two things: 13/16gb used or 13/16gb free.
Hope my 'small' post helps you.
Click to expand...
Click to collapse
Hi Alexander , "small post" ..... => thank you :good:
Clarify 1 to 3 = ok.
Clarify 4 = This S3 is brand new with 2 years of warranty.
Thank you for the rest, but I will give my two S3-LTE to a pro - he will do the job. It have already spend too much time for this.
There are so many "if", "maybe", "test this" and "be aware off" so that I think that someone with knowledge will to the job over an evening.
But one last thing I would like to add: "Profit ???"
- I bought an S3 because I have a crandle for the S3 in my car.
- I bought an LTE because I use it very often as hotspot with my laptop. (this works perfect). In this aspect the S3-LTE is much faster than the standard S3.
- I could not find any S3-LTE with an internal memory bigger than 16 GB.
I already use the "Settings-General-Application Manager " and switched all apps to external memory card - if possible. But this does not really do a lot.
My internal memory uses 13 GB from 16 GB available (read directly after reboot) so there is only 3GB available and I get error messages that there is not enough memory available if I have too many programs open.
=> Therefore I would like to use the external memory card (64GB SD-CARD) for whatsapp, dropbox,... with app and data. And for this I need the SuperSU or something similar.
Thank you for your help and clarification.
Erich
Dear forum,
Long time no talk! I have been able to get "root" for our phones on G925VVRU4BOG7, which anyone can downgrade to. The catch is that even with /system mounted as rw, I am unable to write to it directly through most conventional means. (I can write to /data, though, which means i can patch dalvik-cache, which means my mods are coming ) However, I am able to still write to it using another, more complicated way (I can go into more detail for those interested), as a whole. Here's where you come in-- is anyone still full-rooted? If so, please message me as soon as possible! I may be able to have users who are on newer builds downgrade to older builds and get su properly installed, then manually upgrade back up to the later builds again!
If you are rooted still, all i'm going to have you do is perform this command:
Code:
su
dd if=/dev/block/platform/15570000.ufs/by-name/SYSTEM bs=4096 of=/sdcard/system.img
Then send me that system.img file on your sdcard! It'll be pretty big, so you can zip it or .7z (7-zip), whatever you'd like to do.
I will also need what build you are on. You can just send me your Build number within "Settings->About phone".
First one who does it gets credits on the official release thread i'll make, when I get a procedure down that people can follow!
Thanks!
-Trailblazer101
i have an s6 edge on 5.0.2 rooted. Would that be of help?
Did you get the system.img file? I really wish I could help you. I have this phone on 6.0.1 and stuck without root, but the thing is I really need the root because I bought it used, worked fine the first few days, then didn't get any signal (turns out that it was reported as stolen and of course the IMEI got blacklisted; I tried to contact the seller but he was gone, and his ebay account deleted, so basicly I'm stucked with a ' 5.1" tablet' . I got scammed :/ )
I would be very grateful if you could explain how did you get root on G925VVRU4BOG7 . I know that you want the file mentioned for creating some kind of universal root for the phone, but right now I'm kind of desperate and need root as soon as possible to fix my IMEI issue and I would follow your steps if you made a tutorial.
Thank you very much!
trailblazer101 said:
Dear forum,
Long time no talk! I have been able to get "root" for our phones on G925VVRU4BOG7, which anyone can downgrade to. The catch is that even with /system mounted as rw, I am unable to write to it directly through most conventional means. (I can write to /data, though, which means i can patch dalvik-cache, which means my mods are coming ) However, I am able to still write to it using another, more complicated way (I can go into more detail for those interested), as a whole. Here's where you come in-- is anyone still full-rooted? If so, please message me as soon as possible! I may be able to have users who are on newer builds downgrade to older builds and get su properly installed, then manually upgrade back up to the later builds again!
If you are rooted still, all i'm going to have you do is perform this command:
Code:
su
dd if=/dev/block/platform/15570000.ufs/by-name/SYSTEM bs=4096 of=/sdcard/system.img
Then send me that system.img file on your sdcard! It'll be pretty big, so you can zip it or .7z (7-zip), whatever you'd like to do.
I will also need what build you are on. You can just send me your Build number within "Settings->About phone".
First one who does it gets credits on the official release thread i'll make, when I get a procedure down that people can follow!
Thanks!
-Trailblazer101
Click to expand...
Click to collapse
I am currently running on A0E2 using your rooted rom for this phone. It runs great....except I tried flashing xposed framework using Flashfire and it of course failed...due to the fact that xposed only works on 5.1.1 or above...sucks we are in such a catch 22 with our devices...although I'm happy because I am still rooted.. Anyway...I set up ADB and entered that command you posted and it worked...I just don't know where the storage location of the system.img file is for me to transfer to my PC, 7zip, and send to you. Any help would be excellent....as I desperately want to run xposed framework on my device....but am stuck on 5.0.2
r0ckinb0i said:
I am currently running on A0E2 using your rooted rom for this phone. It runs great....except I tried flashing xposed framework using Flashfire and it of course failed...due to the fact that xposed only works on 5.1.1 or above...sucks we are in such a catch 22 with our devices...although I'm happy because I am still rooted.. Anyway...I set up ADB and entered that command you posted and it worked...I just don't know where the storage location of the system.img file is for me to transfer to my PC, 7zip, and send to you. Any help would be excellent....as I desperately want to run xposed framework on my device....but am stuck on 5.0.2
Click to expand...
Click to collapse
Looking at the last part of the command and if it ran successfully, it should be in /sdcard. Did you ever find it?
gabes100 said:
Looking at the last part of the command and if it ran successfully, it should be in /sdcard. Did you ever find it?
Click to expand...
Click to collapse
Thank you I found it...I'm new to command prompt although I am learning quickly. I found it. I just need to load it onto my computer and compress it so I can send it to Trailblazer. I will do that tomorrow night when I get back home.
I have the img on my computer. It is 4.3G. How do I get it to Trailblazer? Google Drive? EDIT: it is 4.58GB. I am uploading now to google drive, it will an hour
Hi Trailblazer,
Here is a link to system.img:
https :// drive google com / open?id=0B-j3XfGrnj9PbUdwaml5eERvbFU
I am too new to post links the correct way.
Are there any updates on this topic? When I first saw this thread last week, It got me thinking about what a Tethered Root (Temporary/Semi - Root) would still be capable of doing for those of us still on Official Firmware in this day and age.
And really it occurred to me at that moment, that if we could just attain a Root Shell even if it was only for 60 seconds to five minutes, that would be sufficient to get enough root information off of the phone and into a PC editable format.
I ask, because I am in the process of forming a method for the G925V 6.0.1 [PI2] Build. The problem I'm pretty sure I'm going to run into sooner or later in my experiments/research, is the fact that I am one of the few who have the 64GB Verizon S6 Edge. Technically speaking, my device refers to itself in Download/ODIN mode as a SM-G925VZKE model. This also means that my Stock .PIT file is going to be very different than most people's, also meaning my FSTAB configuration probably will be different.
Because there shouldn't be a reason I can't at least get a temporary Root Shell very soon.
So whats up with this? My wife has 6.0.1 on Verizon and I have international much better choice. Will we have root on this phone?
If you are currently on 6.0.1 on your Verizon device. It would serve you well for the time being to disable Automatic Security Updates.
Settings > Lock Screen and Security > Other Security Settings > Security Policy Updates
Turn OFF Automatic Updates, and Turn OFF Wi-Fi Only.
If you leave these on, any potential root option will be patched by Samsung/Google before you know it exists. Disable it for now so you can find an exploit for the build the device is on.
UPDATE:
So apparantly, I've had a rooted 6.0.1 PI2 device persistent through factory resets for over a week, but didn't realize just how much was achieved on my device! According to diagnostics.
I'm already started on writing up the combination of methods that the OP was walking into. Turns out it works up to the September patch too.
But lucky me and not you this time. I got my device essentially decommissioned because I ran my code too soon. But in the sweetest possible way after being so pissed when my tech coach said my warranty was void.
By the end of tomorrow night I should have a thread.
Anyone still working on this?
d0lph said:
Anyone still working on this?
Click to expand...
Click to collapse
Yes. Using the dirtycow vulnerability we've managed to get an arm64 version running that will indeed allow a root console on MM builds.
The last thing standing in the way, for at least a tethered root, is for someone to help me convert the script from the flashable zip version of the SuperSu installer into basically a batch script. Because the how-to guide ChainFire wrote in comments inside his installer script is kind of hard to read because it covers all the different versions of android in a tiny block of text and not every device sets up the same SELinux environment.
Not to mention, if I could get SuperSU to try and install itself as a System Application, it would probably work with what I have already. But for some reason I CANNOT find a single guide anywhere on how to perform a "System" Install of SuperSU, everyone wants to use the "Systemless" version, which is NOT going to work I believe.
We can manage booting the device in the event of DM-Verity Failure, when that happens with the 5.1.1 OG ENG Kernel, we can indeed mount "/system" as read/write, and we can indeed change the contents of the System partition that persist through a reboot.
I just need help setting Perms & Contexts. Because at one point in time, I DID actually manage to get SuperSU to give me a root shell instead of a user shell, but only on the ADB Command Line. In that test I could not get an application to start from the launcher and have Root Permissions.
Delgoth said:
Yes. Using the dirtycow vulnerability we've managed to get an arm64 version running that will indeed allow a root console on MM builds.
The last thing standing in the way, for at least a tethered root, is for someone to help me convert the script from the flashable zip version of the SuperSu installer into basically a batch script. Because the how-to guide ChainFire wrote in comments inside his installer script is kind of hard to read because it covers all the different versions of android in a tiny block of text and not every device sets up the same SELinux environment.
Not to mention, if I could get SuperSU to try and install itself as a System Application, it would probably work with what I have already. But for some reason I CANNOT find a single guide anywhere on how to perform a "System" Install of SuperSU, everyone wants to use the "Systemless" version, which is NOT going to work I believe.
We can manage booting the device in the event of DM-Verity Failure, when that happens with the 5.1.1 OG ENG Kernel, we can indeed mount "/system" as read/write, and we can indeed change the contents of the System partition that persist through a reboot.
I just need help setting Perms & Contexts. Because at one point in time, I DID actually manage to get SuperSU to give me a root shell instead of a user shell, but only on the ADB Command Line. In that test I could not get an application to start from the launcher and have Root Permissions.
Click to expand...
Click to collapse
Thank you for taking the time to still work on this. Subscribed. Following this to the T.
Rand0lph said:
Thank you for taking the time to still work on this. Subscribed. Following this to the T.
Click to expand...
Click to collapse
If you want to follow the complete story of what I just mentioned please follow and contribute to this thread: Injecting Root & Setting SELinux - End Stages?
This is the thread that contains the Greyhat Root console, first designed for the AT&T Galaxy Note 5. But that device uses the same Exynos7420 Mainboard as the Galaxy S6 Edge, so the project is still compatible.
I haven't kept the OP maintained as I should yes. But it is actually worth it to read that whole thread as @droidvoider went out of his way explaining some of his methods. I have a bit of R&D that isn't posted in that thread as well, if you can read up on the project. I'd be more than happy to share what I know with anyone wanting to help as long as they can catch up with what we have accomplished so far.
Look at some of the other threads I've started as well for the initial methods.
Delgoth said:
If you want to follow the complete story of what I just mentioned please follow and contribute to this thread: Injecting Root & Setting SELinux - End Stages?
This is the thread that contains the Greyhat Root console, first designed for the AT&T Galaxy Note 5. But that device uses the same Exynos7420 Mainboard as the Galaxy S6 Edge, so the project is still compatible.
I haven't kept the OP maintained as I should yes. But it is actually worth it to read that whole thread as @droidvoider went out of his way explaining some of his methods. I have a bit of R&D that isn't posted in that thread as well, if you can read up on the project. I'd be more than happy to share what I know with anyone wanting to help as long as they can catch up with what we have accomplished so far.
Look at some of the other threads I've started as well for the initial methods.
Click to expand...
Click to collapse
Sorry, I didn't even acknowledge this is for the EDGE S6. I have a regular Verizon S6.
Rand0lph said:
Sorry, I didn't even acknowledge this is for the EDGE S6. I have a regular Verizon S6.
Click to expand...
Click to collapse
I don't really think that matters as much for the thread I referred to.
I tested the Greyhat Root Console on my S7 Edge, and it worked as well using the September build.
The S6 Line plus the Note 5, all use the same System on a Chip.
If anything, there may be just a couple tweaks to make when compiling it using the NDK.