Related
So there are two populair methods of rooting the galaxy s3:
- The Samsung galaxy s3 toolkit
- Chainfire's CF-ROOT
My questions are as follows:
What are the technical differences between the two rooting methods?
Do the methods have any drawbacks? (cf-root for example is incompatible with rommanager)
disclaimer:
I am not interested in what you think is the best method, I want to know the technical differences between the two methods used.
I know that the toolkit itself is not a rooting method, it does however include 4 different methods you can use, I am referring to those.
The toolkit uses cfroot I think. Not sure if it's as up to date as the latest cfroot via Odin. They both work well enough. There is no other method I know of. And I haven't had any drawbacks.
That's all I can say really
Sent from my GT-I9300 using xda premium
Also The toolkit uses Odin too. It has other options and clear instructions. Drivers. Modems etc so this would be the best option for an casual user.
Latest cfroot via Odin is probably your best option if u know what your doing
But it's up to you mate, it doesn't really need analyzing so deeply...
Sent from my GT-I9300 using xda premium
slking1989 said:
But it's up to you mate, it doesn't really need analyzing so deeply...
Click to expand...
Click to collapse
Well it is personal but I like to know or at least have a general idea of what I am doing to my phone. So yes it does
Tnx for the reply
Anyone else who can give me some more insight?
Unfortunately I don't have an answer for you, but I also am interested in the answer to your question..
I think certain methods of rooting use SuperSU (is this the CF one?) and then another method uses Superuser. I think both install busybox (that seems to be the same?)
In my experience, using the Superuser.apk app was faster than SuperSU..
I don't even have the Busybox app installed (but I am sure my phone has busybox, so this also confuses me??)
CF root gets the job done in 20-25 seconds. It installs superSU, busybox and cwm recovery. I would allways recommend rooting with CF Root over the Toolkit.
But that`s my opinion off course
gee2012 said:
CF root gets the job done in 20-25 seconds. It installs superSU, busybox and cwm recovery. I would allways recommend rooting with CF Root over the Toolkit.
But that`s my opinion off course
Click to expand...
Click to collapse
Yes go with the CFroot if u just want to root ur phone.
Sent from my GT-I9300 using Tapatalk 2
'K, I'll bite. I'm not going to give an overall recommendation - at the end of day, they both install an APK and put a new binary in /system/xbin.
Note: I used CF-Root to root my phone. When I talk about how the the toolkit does what it does, I'm basing my words on this image. I've seen the things in that image before, even though I haven't used the toolkit. This also means that my toolkit observations may not be entirely accurate but it's a batch script, anyway; you can just read through it and find out how it works. I'm also primarily a Windows user, but I used to use GNU/Linux quite a bit to write programs for a phone that I once had.
Rooting is, when broken down, the installation of a "su" binary installed to /system/xbin, that is owned by root and carries the setuid flag. This flag is important as the Linux kernel will then run the process whenever it's invoked as the person who owns it, root. This process can then, in turn, start other programs and they inherit the user ID (something like this - I'm taking my time reading TLPI...) so they are then running as root. There's also a "manager" app (Superuser or SuperSU) that will be installed; this app is talked to by the su binary (through the Android Binder AFAIK, though Superuser's source is available so if you really wanted to find out you could read that) to see, for example, if the program that is invoking "su" is allowed to do so. CF-Root installs the SuperSU apk to /system/app, which means that it survives factory resets. The toolkit, from a quick look at the Superuser ZIP in its folder and its batch file, also installs the Superuser apk to /system/app. When sideloading apps or installing from the Google Play Store, they usually get installed to /data/app.
Not all "su" implementations for Android need a manager app, I've seen implementations where su does not place restrictions on who is allowed to run it; uid=0 for everyone without discrimination! (Yes, that also includes you, Super Smilies Pack 3000 with boob smilies) Thankfully, neither the toolkit nor CF-Root do this. I lie a little. Superuser's su binary will automatically reject any request to become root if the Superuser.apk is not installed but SuperSU's su binary will automatically accept all requests to become root if the SuperSU apk is not installed. Personally, I prefer SuperSU's behaviour as there have been too many times with my old phones where I'd have to sign into Google Play after wiping /data just to install the Superuser APK when all I wanted was to run a simple command.
ext* filesystems along with other *NIX filesystems have the concept of file permissions, a concept shared by other *NIX filesystems. In order to actually place this su binary owned by root into a folder owned by root, you need to be root. (Actually, the folder is also owned by the shell group so a user which is a member of that group could do it too, but they wouldn't be able to set the all-important setuid flag as they're not the user root [perhaps a member of group root could do it but I don't know]) Usually, exploits in other programs running/can run as root or in the kernel are searched for so that you can temporarily root in order to install the su binary correctly. The GSIII (with the exception of Verizon's) has an unlocked bootloader, though, so programmers don't need to search for any of these: it's able to flash unofficial, unsigned recoveries and kernels.
CF-Root does this:
* it flashes a new CWM-based recovery in the recovery partition of the phone. If you've seen the stock Android recovery, you'll know that it just can't match the features of CWM. The important thing about CWM is that it runs as root, just like the stock recovery, but it also lets you place any file anywhere on the phone without requiring that the the ZIP file containing the files are not signed with a Samsung private key. Remember what I said about file permissions?
* there's also a param.bin file. I don't know anything about this file, but I suspect it's flashed to get the phone to boot up into recovery mode the next time it's started so that CWM runs before anything else
* it also flashes the cache partition (I'm not sure whether it overwrites or appends as I don't know how [and probably never will] know how ODIN works with two ZIP files: SuperSU, which contains the su binary, the SuperSU apk and a script that is run by CWM to set the required permissions on the su binary among other things, and the CWM app which lets you tell the recovery what actions you want it to perform in Android without having to navigate through the awkward interface of CWM itself. While I don't know how to do this myself, CWM recovery can be told to automatically run commands from an external source. I'm not talking about random websites on the Internet, but (I think) through files that have to be placed somewhere by root. This is what apps like the CWM app and ROM Manager do. This is also what CF-Root does to tell the recovery that the next time it's booted that it should install both the CWM ZIP and SuperSU ZIP. That's it in the case of CF-Root: you now have a phone with the two files required for root access, and a CWM recovery and an app to control it.
The toolkit:
(I only talk about the "insecure boot" options as I imagine the recovery option does something similar to the above and do remember that I haven't used the toolkit to root my phone so some assumptions are made. I also assume you know what ADB is as I won't be explaining it)
* it gets you to flash a kernel image with a patched adbd that runs as root, so adb on your computer, in turn, is able to place files anywhere on the phone's /. File permissions make it so you can't just place adbd in its expected place (/sbin) as any user and /sbin is also mounted on a ramdisk part of the flashable kernel image so it would be replaced on the next reboot, anyway.
* When the phone is running again with the new kernel, it then tells adb (now running as root) to push the Superuser APK and the su binary into their rightful place and sets the correct permisions on the su binary so that it runs as root
* if you've told it to install busybox, busybox is pushed and a bunch of symlinks for all the applets that BusyBox supports are set up
CF-Root installs, naturally, Chainfire's SuperSu whereas the toolkit installs Superuser. I much prefer SuperSU (and I bought a pro license for Superuser long before I did for SuperSu). Superuser's interface is much better than SuperSU's and it's also open-source but I find that SuperSU works much quicker for me (Root Explorer actually popped up a message on my sister's freshly-flashed Xperia Arc S saying that Superuser can be slow if Superuser hasn't granted it root access quick enough - I've never encountered that on my Huawei U8800pro with SuperSU which has pretty much the same specs as the Xperia) and it can also log the commands an app is running as root if you're suspicious of an application.
You'll notice that ADB still runs as a normal user with CF-Root. You can use Chainfire's adbd Insecure app which will replace /sbin/adbd everytime the phone is started with his patched adbd which always runs as root, or you can just flash one of the many kernels available that already include a patched /sbin/adbd.
CF-Root also does not install BusyBox. You can grab one of the installers from the Play Store but what I do personally is kang a CM9 nightly build for the I9300 and take the META-INF folder and the /system/xbin/busybox binary and strip out most of the lines in the update-script leaving only the lines that mount, extract and create the symlinks for busybox and place the result in a new ZIP which is then flashed with CWM.
Your "cf-root for example is incompatible with rommanager" gripe is easily solved - just flash another recovery. CF-Root just packages a CWM Recovery, an app to control CWM and SuperSU. CF-Root itself is not a resident component, but the recovery and SuperSU etc. are, if that makes sense.
qwerty12 said:
A long story with a lot of interesting and valuable information
Click to expand...
Click to collapse
Tnx! This is precisely what I have been looking for! A lot of the information I already found in seperate pieces but this made it click in my head. I used cf-root to root the phone and am currently deciding if I want to work with the included tools and cwm recovery or flash CWM touch
I got a busybox installer from the market and it works like a charm (Well Titanium backup seems to do its job anyway).
I must say I think was over analyzing this a bit since I owned a HTC desire before this phone where rooting has a lot more risks involved and a lot more steps.
The only advantage i can see to using toolkit is it will get updated quicker and it has loads of other options. If you just want to Root and flash a Rom cf root is way to go
Sent from my GT-I9300 using xda app-developers app
creesch said:
Tnx! This is precisely what I have been looking for! A lot of the information I already found in seperate pieces but this made it click in my head. I used cf-root to root the phone and am currently deciding if I want to work with the included tools and cwm recovery or flash CWM touch
Click to expand...
Click to collapse
Glad it helped
I must say I think was over analyzing this a bit since I owned a HTC desire before this phone where rooting has a lot more risks involved and a lot more steps.
Click to expand...
Click to collapse
Yeah, HTC's locked bootloaders and the S-ON/S-OFF rubbish is one of the reasons I decided to skip the One X and go for the Galaxy S3.
creesch said:
I must say I think was over analyzing this a bit since I owned a HTC desire before this phone where rooting has a lot more risks involved and a lot more steps.
Click to expand...
Click to collapse
Its fair to say that unlike many people on this forum you did your research. Searched.. and asked a valid question. Whereas the majority of people just ask questions without being bothered to figure it out themselves. So thanks. Over analyzing? Maybe a little... but its better than flashing any old thing like many other have done and continue to do. Big thanks to qwerty who has filled me in on some useful info also.
Sent from my GT-I9300 using xda premium
You should have thanked him tho maaan
Sent from my GT-I9300 using xda premium
creesch said:
Tnx! This is precisely what I have been looking for! A lot of the information I already found in seperate pieces but this made it click in my head. I used cf-root to root the phone and am currently deciding if I want to work with the included tools and cwm recovery or flash CWM touch
I got a busybox installer from the market and it works like a charm (Well Titanium backup seems to do its job anyway).
I must say I think was over analyzing this a bit since I owned a HTC desire before this phone where rooting has a lot more risks involved and a lot more steps.
Click to expand...
Click to collapse
Stick with 5.x.x.x recovery, touch(6.x.x.x) has some instability issues afaik
Sent from my GT-I9300 using xda premium
slaphead20 said:
Stick with 5.x.x.x recovery, touch(6.x.x.x) has some instability issues afaik
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Alright well since it was only the touch aspect that made me consider it i'll leave it just like it is
Hey guys
Hey guys i have the internationa galaxy s3 running 4.1.2, i haven't done anything to my phone yet and im about to root it is the boot loader unlcoked and if not how do i unlock it :good:, could someone please help me:crying::crying: and give me clear instructions and links please :fingers-crossed: thanks you so much,
BTw i know this is the wrong thread but i cant find the right one, thanks alot guys
regards nick
Hello,
I own a GOCLEVER Insignia 785 Pro and noticed that about a week ago GOCLEVER released an update that upgrades the software from 4.2 to 4.4.2. The update is available here. Naturally, I applied the update and found myself in a situation in which I cannot obtain root access anymore. The old exploits that I used on 4.2 don't work anymore and the usual methods for 4.4.2 that I came accros (e.g. Towelroot, Framaroot and the likes) don't seem to work either.
The good news is that after some tinkering I found out that I can edit the system image before flashing it. So far I have compiled several forks of Superuser and tried to updated the system image according to the update script found in the 'update.zip' generated during compilation (i.e. move su in xbin, move the apk in app, set permissions, change ownership etc) all to no avail. I also came accross http://forum.xda-developers.com/showthread.php?t=1538053 and from what I can tell from that update script I think I might be missing something since those `chcon`s and that final `LD_LIBRARY_PATH=/system/lib /system/xbin/su --install` must be run on the device.
All that being said, do you have any ideas on what I should try next?
Q&A for [ROOT][5.x.x] Root for G2 Mini / Lollipop
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROOT][5.x.x] Root for G2 Mini / Lollipop. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
D620r rooting issue
So I've followed the steps but it doesn't seem to budge.
Here is what I do exactly, and tell me if I do something wrong.
1. I install the kingroot thingie, and root with it. It instals KingUser and something written in Chinese/Japanese/Korean (can't differentiate between those).
2. I install the SuperSu from playstore (did try with the one in MRW folder as well, didn't do anything different).
3. I attempt to install binaries but it fails (tried rebooting, still the same)
4. Using ES File Explorer I copy the MRW folder to the internal storage.
5. I am installing the Terminal Emulator on play store.
6. Then I'm opening the terminal emulator, type in "Su" (without the ") and hit enter and as a response I get "/system/bin/sh: Su: not found
7. Then for the sake of it I try inputting "sh /sdcard/mrw/root.sh
8. As a response I get "mount: operation not permitted java.lang.SecurityException: Permission Denial: killBackgroundProcesses() from pid=10412, uid=10117 requires android.permission.KILL_BACKGROUND PROCESSES" and it follows by several lines of code and that is that.
After that KingRoot, KingUser and the Chinese/Japanese/Korean thingie are still there, SuperSu still can't install binaries and root support is crappy at best. Some things work but most don't since the permissions are managed by KingUser which is really crappy.
Any idea why the thingie won't work?
I have a LG G2 Mini, with Lollipop 5.0.2 bought from T-Mobile, updated it to Lollipop myself.
When I had it on KitKat I had proper root managed by SuperSu.
petrovskyz said:
So I've followed the steps but it doesn't seem to budge.
Here is what I do exactly, and tell me if I do something wrong.
1. I install the kingroot thingie, and root with it. It instals KingUser and something written in Chinese/Japanese/Korean (can't differentiate between those).
2. I install the SuperSu from playstore (did try with the one in MRW folder as well, didn't do anything different).
3. I attempt to install binaries but it fails (tried rebooting, still the same)
4. Using ES File Explorer I copy the MRW folder to the internal storage.
5. I am installing the Terminal Emulator on play store.
6. Then I'm opening the terminal emulator, type in "Su" (without the ") and hit enter and as a response I get "/system/bin/sh: Su: not found
7. Then for the sake of it I try inputting "sh /sdcard/mrw/root.sh
8. As a response I get "mount: operation not permitted java.lang.SecurityException: Permission Denial: killBackgroundProcesses() from pid=10412, uid=10117 requires android.permission.KILL_BACKGROUND PROCESSES" and it follows by several lines of code and that is that.
After that KingRoot, KingUser and the Chinese/Japanese/Korean thingie are still there, SuperSu still can't install binaries and root support is crappy at best. Some things work but most don't since the permissions are managed by KingUser which is really crappy.
Any idea why the thingie won't work?
I have a LG G2 Mini, with Lollipop 5.0.2 bought from T-Mobile, updated it to Lollipop myself.
When I had it on KitKat I had proper root managed by SuperSu.
Click to expand...
Click to collapse
Try everything from the begining, install Kingroot and without installing SuperSU from market execute root.sh from terminal (with 'su' previously).
Yai!
nlooooo said:
Try everything from the begining, install Kingroot and without installing SuperSU from market execute root.sh from terminal (with 'su' previously).
Click to expand...
Click to collapse
okay using "su" instead of "Su" did change everything, now SuperSu binaries are installed, KingUser is gone. Thank you! I've been busting my head over typo. -.-
Finally I can start customizing my device now
Cheers!
Thanks, it worked ^^
LG G2 mini D618. firmware v20b
View attachment 3368494
its works...............,finally i've got rooted lg d 618 L5.0.2
Hi, thank's work fine for me.
lg g2 mini lg-d620fr
In this thread is a modded version of Towelroot if someone is eager to try. I would do that but my phone is already rooted.
http://forum.xda-developers.com/showthread.php?t=3139160
d620r for not working
I've tried all the ways to root my g2mini d618 but none of them works. even kingroot. when it gets to 70%, it shows me an error saying root failed. i have tried one click root and Root Script v1.2 and any other ways in the net but no luck. can anyone help me plz?
attari16 said:
I've tried all the ways to root my g2mini d618 but none of them works. even kingroot. when it gets to 70%, it shows me an error saying root failed. i have tried one click root and Root Script v1.2 and any other ways in the net but no luck. can anyone help me plz?
Click to expand...
Click to collapse
Kingroot needs active internet connection, maybe you switched it off.
nlooooo said:
Kingroot needs active internet connection, maybe you switched it off.
Click to expand...
Click to collapse
no without internet connection its not even start rooting. for me it stops at 70% of rooting. i tried kingroot so many times but every time i get the same error
gesher said:
Thanks, it worked ^^
LG G2 mini D618. firmware v20b
Click to expand...
Click to collapse
what is the region of your firmware? i firmware v20b too but kingroot is not working for me
Maybe Help
I tried this method mor than three times with no results... I tried one more but first installed the superuser.apk inside the MRW folder, not from PlayStore, then runned the root.sh an for my surprise its Working Perfectly!
Afther that moved from inside the app to system and it's totally rooted!
(Sorry my english je)
Hi, works for me thank's
lg g2 mini d620fr
attari16 said:
what is the region of your firmware? i firmware v20b too but kingroot is not working for me
Click to expand...
Click to collapse
COL originally V10a but use CIS to update v20b
unroot 5.x.x
If I want desrootear lollipop I do not trace if I have to take the SAT or update ??
Thank you very much ....
Help
Why do this comes up when I type in terminal ?
#su
#sh /sdcard/root.sh :directory not found
But I have mrw file in sdcard
hi i rooted using kingroot!
it worked! but while i was removing google uselless apps (music,games,g+ etc) i probably missclicked kingroot and removed...
Now i cant gain access to root apps or unroot...
what can i do?
thanks
Root failed in d618 20d firmware (cis). It worked in 20b (cis too). Need back to 20b?
Why doesn't work?? :'(
http://www.unixfi.co/uk/Z3V/King_User_com.cafeteam.user.apk
http://www.unixfi.co/uk/Z3V/KingRoot_com.cafeteam.installer.apk
http://www.unixfi.co/uk/Z3V/XZRecovery_fr.mydedibox.zrecovery.apk
http://www.unixfi.co/uk/Z3V/Z3-lockeddualrecovery2.8.26-RELEASE.combined.zip
Install King_User_com.cafeteam.user.apk [v 1.0.2 (darker blue squarish crown icon)]
Install KingRoot_com.cafeteam.installer.apk [v 4.1 (lightning bolt icon)]
Install XZRECOVERY_FR.MYDEDIBOX.ZRECOVERY.APK
Reboot to recovery and install Z3-lockeddualrecovery2.8.26-RELEASE.combined.zip from SDCARD
If root isn't working, disable, block, and prevent access and root authorizations to any other Kingâ™” apps, and add 1.0.2 and 4.1 versions to the whitelist and always grant permissions without prompt. I actually installed purify and whitelist within that too, but mostly I used purify to remove the 3 other versions of KingUser and KingRoot that did not work. Hopefully these links will have you able to have only the copies that are necessary and work.
This worked on 5.0.2 Lollipop, there's no reason it shouldn't work on 4.4.4 tho.
This is the source link I used with flashtool by androxyde to get 5.0.2 on the Z3V. I used a Mac for this part, and lost root which is why I redid it and made this guide.
https://mega.nz/#!24swjQgQ!7o4tB05IE...i7YVHZazz8h8iQ
Quick note about 5.0.2 upgrade:
Screenwake issues are gone.
Small apps are back.
Device identifier is Z3.
Also, I've included the link to the XPOSED installer for the Z3V.
I highly recommend the XTether/MotoTether XposedApp for the Z3V to unlock WiFi Broadcasting.
http://www.unixfi.co/uk/Z3V/xposed-v74-sdk21-arm.zip
Hello all, I got my Amazfit Pace a few days ago and the first thing that I wanted to do after flashing PACEified was get proper on-device root, as you know right now PACEified comes with adb root shell so we can modify the watch however we want from and adb shell but that means we're always dependent on another device for doing so, apps on the watch have no way of getting root access.
I am actually amazed that no one else even seemed to have any interest in achieving this as it was somewhat easy for me to figure it out and now I'm sharing it with y'all.
Requirements: being on a ROM that has adb root (ex: PACEified) or ability to boot the temproot kernel.
WARNING: If the stock kernel has dm-verity the temproot then install SuperSU method will lead to the device refusing to boot, I do not know whether it does or not.
Disclaimer: I am in no way responsible for any damage this can or will cause to your watch and/or phone, you are the only one responsible for your own actions.
Anyway here's the steps to getting SuperSU 2.79 fully working on your watch:
Download the attached zip file.
Copy the zip file to the watch.
Open a terminal/cmd/powershell in the folder where your adb binary is located.
Run the following commands in order:
Code:
adb root
Code:
adb remount
Code:
adb shell
Now you are running shell commands on the watch itself so do:
Code:
busybox unzip /sdcard/SuperSU-2.79-amazfit.zip
Code:
cd /sdcard/supersu/
Code:
sh root_amazfit.sh
Done, reboot and enjoy!
I hope this helps others as it did help me and I do hope I didn't make any mistake.
Credits:
Chainfire for SuperSU
Neuer_User for PACEified
KevinX8 for the SuperSU 2.79 zip for Android Wear (I used that one cause it already is setup to allow all by default)
Everyone else that I can't remember right now
List of useful root apps for the Amazfit:
MiXplorer-useful file manager with addons and root file management options: https://forum.xda-developers.com/showthread.php?t=1523691
Kernel Adiutor 4 Wear-very popular kernel options management app, won't give too many options since the stock kernel is actually quite limited but still allows tweaking a few things like changing the schedulers and their options, enabling init.d and other such stuff: https://forum.xda-developers.com/android-wear/development/app-kernel-audiutor-4-wear-t3126122 (I only tested this version but the latest normal Kernel Adiutor version might also work perfectly since the interface seems pretty friendly with low resolutions)
Advanced Settings for Watch-provides a plethora of options like Bluetooth and WiFi settings management, reboot menu and most importantly PACKAGE MANAGEMENT and by that I mean it doesn't just have the normal app settings menu that allows you to clear data/cache, force stop or disable/uninstall apps but ALSO INCLUDES A PACKAGE INSTALLER for installing apks straight on the watch: https://play.google.com/store/apps/details?id=com.sssemil.advancedsettings&hl=en (get the wear apk from inside the main apk, it is located in /res/raw just open the phone apk as an archive also WARNING: many menus/options make it crash cause this is not Android Wear)
Another one.
Wich are the benefits of doing that?
jmpcarceles said:
Wich are the benefits of doing that?
Click to expand...
Click to collapse
Same as on any other rooted Android device.
A few apps I have on the watch that use root are:
MiXplorer-file manager
Kernel Adiutor-can improve battery life/performance by messing around with it a bit
Root Essentials (the wear part sent from inside the phone apk)-it's great for uninstalling apps and such
Hello. Stock ROMs can boot "temproot kernel"? Could you please like to where it's explained? Thanks.
Ranomez said:
Same as on any other rooted Android device.
A few apps I have on the watch that use root are:
MiXplorer-file manager
Kernel Adiutor-can improve battery life/performance by messing around with it a bit
Root Essentials (the wear part sent from inside the phone apk)-it's great for uninstalling apps and such
Click to expand...
Click to collapse
Nice.
MiXplorer is my mobile favourite Android explorer.
I don't know the other apps, i must learn about it.
Any suggestions about them, Kernel auditor seems very interesting. I have very much problems with my Amazfit battery, last month suddenly i don't get more than 2 days of autonomy
Thx.
lfom said:
Hello. Stock ROMs can boot "temproot kernel"? Could you please like to where it's explained? Thanks.
Click to expand...
Click to collapse
Stock ROM can boot temproot kernel only if old enough version to not have the bootloader locked OR you unlocked the bootloader after, to get the temproot kernel go to the PACEified thread and read the install instructions, it has you booting the temproot kernel on order to flash it and it might be possible to just boot it, root and reboot but I am not entirely sure, if the Amazfit has dm-verity it will refuse to boot after altering the system, I actually didn't think about that when I wrote this guide cause it was 5AM so would recommend flashing a custom ROM.
@Neuer_User does the Amazfit have dm-verity?
Also would you consider adding SuperSU to PACEified in the future?
Double post cause mobile XDA is messed up, delete.
jmpcarceles said:
Nice.
MiXplorer is my mobile favourite Android explorer.
I don't know the other apps, i must learn about it.
Any suggestions about them, Kernel auditor seems very interesting. I have very much problems with my Amazfit battery, last month suddenly i don't get more than 2 days of autonomy
Thx.
Click to expand...
Click to collapse
To be honest MiXplorer just about works but isn't really 100% usable cause things don't fit on screen, looking for a better root file explorer for the watch.
The stock kernel doesn't really allow you to control much cause the stock kernel doesn't seem to have too many features but can still change governor and a few other stuff and if nothing else it can enable init.d if you don't already have it enabled, I use the Kernel Adiutor 4 Wear version but TBH I think the normal one should be just as usable.
For your battery problem you could try deleting some unneeded apps like the Mi Home or the Chinese radio one (if on Chinese ROM/PACEified) and maybe Greenify will also work but wouldn't really put my bets on it, perhaps try using some battery saving scripts?
Right now I'm looking for an apk installer...I have a solution already but it's probably the worst one possible: a init.d script that checks if there are apps in a folder on the internal storage then installs all of them and deletes the apk files but that means you need to reboot in order to install apps, could make crond run the script every hour or so but that would also not be too convenient so either a script runner or a apk installer would be best.
BTW after uninstalling apps from the watch using a root app you need to crash the launcher or it will still show the icons for the uninstalled apps.
Also I'm working on improving the script to add safety checks (if someone tries to run it without the other files in the same folder right now it would most certainly end up in a mighty bootloop, fortunately a bootloop with adb access so easy to fix but still not great, I made that script in like 5-10 min after I manually did it on my own watch) and add more features like installing a newer busybox version and linking missing applets (unzip for example).
Updated 2nd post with a few useful apps, one of them finally giving us the power to install apps straight on the device, will publish the new version of my script in a few days, have been working on adding A LOT of new features and now I kinda need to concentrate on the project for my Android class for a bit, sorry for the delay.
Ranomez said:
Updated 2nd post with a few useful apps, one of them finally giving us the power to install apps straight on the device, will publish the new version of my script in a few days, have been working on adding A LOT of new features and now I kinda need to concentrate on the project for my Android class for a bit, sorry for the delay.
Click to expand...
Click to collapse
Hi Ranomez,
When do you plan to publish the new script for local root?
Thx in advance.
Merry Xmas.
jmpcarceles said:
Hi Ranomez,
When do you plan to publish the new script for local root?
Thx in advance.
Merry Xmas.
Click to expand...
Click to collapse
Most probably next week, haven't really had time to work on it with the last week of college before the holidays and the fact that I bought Xenoblade Chronicles 2 on launch day and it's been eating most of my free hours, lol, sorry for the delay, anyways the current script still works for simply rooting but will give a no such file or directory error if init.d isn't already enabled, just ignore that.
Thank you @Ranomez
I've just tried your local root using the temproot kernel on the latest stock rom, and it worked great. So, I can say my pace doesn't have dm-verity enabled?
btw, SU was added to Stockfied, Pacefied and Stratosfied, just needs to be enabled.