Related
Hi everyone!
moving forward from my beloved HTC Desire Z that worked so well since few month ago, now i got an awesome LG G3 - D855 with stock Lollipop 5.0 [BUILD: LRX21R.A1421650137]
So, it takes just 2 weeks to make me say "This is f***ing annoying, damn! I need my device to be rooted!" and make me look for some root method for this phone.
Now, i saw different ways to do that, and i'm trying to figure out which one is the best compromise between complexity/time that it takes/safety, and which one can be used with the different versions of android.
Here it is what i found:
1 - LG One-Click Root
2 - LG Root Script
3 - PurpleDrake
4 - StumpRoot or StumpRoot on XDA
5 - TowelRoot
6 - Bump
Well, I'm not a newbye on rooting devices ( as I said, i come from an HTC with HBoot and so on.. ), but i'm more confident if i can understand what a script does instead of simply doing a procedure blindfolded..
Can someone quickly tell me some infos, or give me some directions please?
As always, thanks in advance
http://forum.xda-developers.com/lg-g3/development/tool-dp-root-tool-to-root-lg-devices-t3075007 Go with this one. Then flashify some recoveryand flash on!
Thanks (again) ymcc, i will look into this!
Well, i'm close to root my phone finally.. I just have a question about the version of twrp i should use: I got "twrp-2.8.7.0_d855-bumped.zip", but i don't know if the root method that ymcc told me "bumps" my phone.. can someone please help me whit this?
Just to recap, i need to:
1 - get all the files/apps/software i need
2 - enable usb debugging and run "V2+DP+ROOT"
3 - Install some SuperSU app ( any advice is welcome )
4 - Install and run flashify to flash "twrp-2.8.7.0_d855-bumped.zip"
Is this ok, or i should go for something else with AutoRec or so?
I also see there's a way to install twrp with the playstore app, is it working too?
I feel sorry and newbye with all this, but i'm confused by so many tools and methods posted almost everywhere.. one says just for kitkat, one says all os versions, one says just bumped phones, one says to do not use this but use that.. damn i'm screwed!
skui said:
Well, i'm close to root my phone finally.. I just have a question about the version of twrp i should use: I got "twrp-2.8.7.0_d855-bumped.zip", but i don't know if the root method that ymcc told me "bumps" my phone.. can someone please help me whit this?
Just to recap, i need to:
1 - get all the files/apps/software i need
2 - enable usb debugging and run "V2+DP+ROOT"
3 - Install some SuperSU app ( any advice is welcome )
4 - Install and run flashify to flash "twrp-2.8.7.0_d855-bumped.zip"
Is this ok, or i should go for something else with AutoRec or so?
I also see there's a way to install twrp with the playstore app, is it working too?
I feel sorry and newbye with all this, but i'm confused by so many tools and methods posted almost everywhere.. one says just for kitkat, one says all os versions, one says just bumped phones, one says to do not use this but use that.. damn i'm screwed!
Click to expand...
Click to collapse
That's fine. Get DP Root Tool. Connect your device with enabled USB debugging to computer with installed LG drivers. Click to root.
Get SuperSU app by Chainfire. You can get it on Google Play.
Flash the mentioned TWRP and you are done.
For the TWRP from the Play Store, that's only the app that manages the recovery(for scheduling tasks if you wish...). It's not needed. You need to flash the recovery you mentioned with flashify or manually with adb if you prefer.
many many tnx
I'm coming from the Samsung ACE 2 community and I will also get my LG tomorrow. At the moment I'm a little bit confused because this device section is so big, there are so many root versions, kernels, roms etc..... compared to the ACE2 section.
Of course I will install a custom rom on my phone. (BlissPop at the beginning)
So is it ok, if I'm doing this in this order?
1)rooting with "DP Root Lg"
2)install SuperSU from Play Store
3)install Flashify from PlayStore
4)flash the recovery image
5)reboot to recovery
6)backup efs
7)wipe, install new rom, gapps etc....
But I just saw this: . Is this relevant for me?
Greetings Samuel
S.AMU said:
I'm coming from the Samsung ACE 2 community and I will also get my LG tomorrow. At the moment I'm a little bit confused because this device section is so big, there are so many root versions, kernels, roms etc..... compared to the ACE2 section.
Of course I will install a custom rom on my phone. (BlissPop at the beginning)
So is it ok, if I'm doing this in this order?
1)rooting with "DP Root Lg"
2)install SuperSU from Play Store
3)install Flashify from PlayStore
4)flash the recovery image
5)reboot to recovery
6)backup efs
7)wipe, install new rom, gapps etc....
But I just saw this: . Is this relevant for me?
Greetings Samuel
Click to expand...
Click to collapse
The steps you metioned will work. About the DP Root I'm not sure if it will auto flash SuperSU app but it doesn't really matter, you will check that after you run it.
As for the bump, it's the way of signing the image(boot, recovery) so the LG bootloader is able to boot it without tripping the security errors. The recovery image you will flash (twrp-2.8.7.0_d855-bumped.zip, mentioned by the guy above) is as it says bumped.
NatusVincere said:
The steps you metioned will work. About the DP Root I'm not sure if it will auto flash SuperSU app but it doesn't really matter, you will check that after you run it.
As for the bump, it's the way of signing the image(boot, recovery) so the LG bootloader is able to boot it without tripping the security errors. The recovery image you will flash (twrp-2.8.7.0_d855-bumped.zip, mentioned by the guy above) is as it says bumped.
Click to expand...
Click to collapse
Ok, thank you. :good:
So I'm ready to go tomorrow
S.AMU said:
I'm coming from the Samsung ACE 2 community and I will also get my LG tomorrow. At the moment I'm a little bit confused because this device section is so big, there are so many root versions, kernels, roms etc..... compared to the ACE2 section.
Of course I will install a custom rom on my phone. (BlissPop at the beginning)
So is it ok, if I'm doing this in this order?
1)rooting with "DP Root Lg"
2)install SuperSU from Play Store
3)install Flashify from PlayStore
4)flash the recovery image
5)reboot to recovery
6)backup efs
7)wipe, install new rom, gapps etc....
But I just saw this: . Is this relevant for me?
Greetings Samuel
Click to expand...
Click to collapse
For the next person reading this thread:
Instaling TWRP with flashify didn't worked. It gave me an red and blue blinking LED when I wanted to enter recovery. Instead I used this, because they say its for firmware version 20h and I had this version.
So I'd like to know how I can use Chainfire's new systemless root to then still use Android Pay. I downloaded the Android binaries from Google for the 5X and proceeded like so:
(I was already rooted with the normal method that modifies the /system parition)
1. Run flash-all.bat to flash all partitions and go back to stock.
2. Install the modified boot.img from Chainfire
3. Install the latest TWRP 2.8.7.2
4. Reboot into TWRP
5. Install using adb sideload from TWRP the beta SuperSU
6. Reboot into phone and set it up... restore Titanium Backups...
The problem is that Android Pay still won't let me add a card to it....
Did I do something wrong in this process here?
Would love it if someone who has done this could help me out here..
Thanks!
chickentech said:
So I'd like to know how I can use Chainfire's new systemless root to then still use Android Pay. I downloaded the Android binaries from Google for the 5X and proceeded like so:
(I was already rooted with the normal method that modifies the /system parition)
1. Run flash-all.bat to flash all partitions and go back to stock.
2. Install the modified boot.img from Chainfire
3. Install the latest TWRP 2.8.7.2
4. Reboot into TWRP
5. Install using adb sideload from TWRP the beta SuperSU
6. Reboot into phone and set it up... restore Titanium Backups...
The problem is that Android Pay still won't let me add a card to it....
Did I do something wrong in this process here?
Would love it if someone who has done this could help me out here..
Thanks!
Click to expand...
Click to collapse
Did you hide/disable/uninstall supersu and reboot before opening the Android pay app?
If not, do that, and clear app data for Android pay. Then try to set it up.
Android pay and root don't work. If you want Android Pay to work, you need to disable root anytime you want to use it and even then it may not work.
buru898 said:
Did you hide/disable/uninstall supersu and reboot before opening the Android pay app?
If not, do that, and clear app data for Android pay. Then try to set it up.
Click to expand...
Click to collapse
metpage said:
Android pay and root don't work. If you want Android Pay to work, you need to disable root anytime you want to use it and even then it may not work.
Click to expand...
Click to collapse
Systemless root does work with Android Pay when root is on. At the very least, you should be able to add cards. Which means you should be able to use pay in general. Safetynet checks in Pay are not that strict.
Did you flash TWRP and boot into recovery or did you boot it from fastboot USB?
Have you tried simply putting the zip on the device and flashing it from there?
Did you let TWRP install SU/Root in the prompt before rebooting? (The answer should be no)
formula91 said:
Systemless root does work with Android Pay when root is on. At the very least, you should be able to add cards. Which means you should be able to use pay in general. Safetynet checks in Pay are not that strict.
Did you flash TWRP and boot into recovery or did you boot it from fastboot USB?
Have you tried simply putting the zip on the device and flashing it from there?
Did you let TWRP install SU/Root in the prompt before rebooting? (The answer should be no)
Click to expand...
Click to collapse
To answer,
You can read exactly what I did above. I did not let TWRP install SU for me, and rebooted using the power button I believe after installing the Beta SU from TWRP's ADB sideload..
I'll try again tonight as I KNOW Android Pay DOES work with the new Systemless Root, I just haven't gotten it right on my first try here.
Thanks.
chickentech said:
To answer,
You can read exactly what I did above. I did not let TWRP install SU for me, and rebooted using the power button I believe after installing the Beta SU from TWRP's ADB sideload..
I'll try again tonight as I KNOW Android Pay DOES work with the new Systemless Root, I just haven't gotten it right on my first try here.
Thanks.
Click to expand...
Click to collapse
Have you tried doing Android Pay before restoring stuff from Titanium Backups? There is a slim possibility that it may be altering something from system, making it fail the safetynet checks.
I would try flashing the zip from TWRP instead of sideloading as well. Just in case.
chickentech said:
...
I'll try again tonight as I KNOW Android Pay DOES work with the new Systemless Root, I just haven't gotten it right on my first try here.
Click to expand...
Click to collapse
Uh... how exactly can you know something "DOES" work if your one and only attempt at making it work was a complete failure and no one else has been able to get it to work?
Not saying Android Pay can't work with systemless route in one form or another. But to make a statement as if something is of fact when you've proven nothing to support that fact is a bit idiotic.
But hey, people said Einstein and Tesla had idiotic ideas. So here's to hoping.
sn0warmy said:
Uh... how exactly can you know something "DOES" work if your one and only attempt at making it work was a complete failure and no one else has been able to get it to work?
Not saying Android Pay can't work with systemless route in one form or another. But to make a statement as if something is of fact when you've proven nothing to support that fact is a bit idiotic.
But hey, people said Einstein and Tesla had idiotic ideas. So here's to hoping.
Click to expand...
Click to collapse
The same could be said for not doing your own research. This is a section for helping others
Right at the bottom: http://www.xda-developers.com/chainfire-releases-root-for-android-6-0-without-modifying-system/
Update: Reddit user MajorNoodles has informed that Android Pay works on his Nexus 5. Chainfire, on his Google+ post, does mention that the working of Android Pay is by accident and not by design. He expects Android Pay to be updated in the future to counteract this.
Click to expand...
Click to collapse
Unless that hole has been patched already, it should still work, but we won't know for how long.
@chickentech I'm not in much of a position to help, given my location, but this might help you debug whether it is Pay being weird or if SafetyNet is tripped: https://play.google.com/store/apps/details?id=com.cigital.safetynetplayground
nvm
PhoenixTank said:
The same could be said for not doing your own research. This is a section for helping others
Right at the bottom: http://www.xda-developers.com/chainfire-releases-root-for-android-6-0-without-modifying-system/
Unless that hole has been patched already, it should still work, but we won't know for how long.
@chickentech I'm not in much of a position to help, given my location, but this might help you debug whether it is Pay being weird or if SafetyNet is tripped: https://play.google.com/store/apps/details?id=com.cigital.safetynetplayground
Click to expand...
Click to collapse
Thanks...
I said I knew because I actually READ.. As you have.
Probably something to do with the order I'm doing things in.. Or as mentioned, the Titanium backup could definitely do it..
You know, I wouldn't even Root if there was a good way to block ads without - but most of what I've seen isn't quite there for me.
Again, thank you @PhoenixTank
chickentech said:
Thanks...
I said I knew because I actually READ.. As you have.
Probably something to do with the order I'm doing things in.. Or as mentioned, the Titanium backup could definitely do it..
You know, I wouldn't even Root if there was a good way to block ads without - but most of what I've seen isn't quite there for me.
Again, thank you @PhoenixTank
Click to expand...
Click to collapse
If you're rooting to modify the hosts file to block ads.... that changes system, and will trip Android Pay's SafetyNet checks. The best adblocking I can get without changing System is Adblock Plus for Android. (Root on ABP seems to only allow some sort of localhost proxy network rerouting instead)
FYI Safetynet Playground trips for me, but Android Pay works just fine.
UPDATE: Weird, now I pass, must be because I recently re-encrypted my phone.
So now it's confirmed, I can use Android Pay and not trip SafetyNet API. Neato.
Thanks! That hosts file was it.. A fresh install and I'm gold with Safetynet Many thanks all around!
You're very welcome!
Right now I'm using adblock plus + a "patcher" that's pretty "lucky" heh.
Hi there everyone !!
I gone a long way till now...
http://forum.xda-developers.com/nexus-5x/help/req-help-to-unbrick-t3251740
http://forum.xda-developers.com/nexus-5x/help/how-to-enable-oem-unlocking-bricked-t3249003
And now I'm trying to get full Stock phone with Encryption, Locked oem and systemless Root without No warnings. = S E L R N
As far as I went was S R N when i tried to encrypt it got stucked on colorful bubbles screen.
Anyone got idea how to reach this ?
Did somone checked is AdAway after changing location of host file and symlinking it, stops Google Pay/Makes additional warning while booting ?
This guide was inspired by:
http://reviewroots.com/root-Huawei-MediaPad-M2-with-or-without-pc
http://www.w0lfdroid.com/2015/05/How-to-Remove-Replace-KingUser-KingRoot-with-SuperSU.html
http://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
Big THANKS
Note: I am not responsible for any damage made by doing this.
I have tried some root practices on my Huawei Mediapad M2 8.0, but this is the only that worked for me. This practice is without PC, using Kingroot. It worked for me for first try.
If you are new and don't know what is root, you probably don't need it. But for education, check THIS
What will this do?
Root your device
Install Kingoot app (should be uninstalled by itself, or you can manually uninstall it)
Install SuperSU app
GUIDE
Allow unknown sources in Settings/Security
Download and install View attachment NewKingrootV4.80.apk
Click 'Start root' button when it appears
After a few minutes, it should be completed.
Now you are ROOTED. But for now, KingRoot is the root managing app. If you are OK with this, then you are done. If you want SuperSU continue:
Install Terminal Emulator
Download View attachment Replace_Kinguser_with_SuperSU-v2.4.zip and unzip the mrw folder to your internal SD
Open Terminal Emulator and type:
Code:
su
Now it should ask for root permissions, click allow (Don't type this line)
sh /sdcard/mrw/root.sh
Don't worry if it display an error, just let it continue
Now, the Kingroot should disappear and SuperSU should appear. In my case, SuperSU didn't appear because the installation crashed. So if can you see SuperSU app, jump to 9th step.
If you don't see SuperSU app, check it in Google Play if it's installed. If it's not, just install it.
When you first open SuperSU is should ask you for updating binary, click install normally and then reboot you phone.
Now everything is done, I just wanted to have 10 steps, so I give you my advice: It's better to support SuperSU developer, but if you don't want, you can get pro functions free and legally :
Open SuperSU app
Go to settings tab
Find and check Enable Pro setting
Restart the app and now you are PseudoPro
Thanks for you attention!
If you found this helpful, please click the Thanks! button.
Please check the posts I was inspired by
If you think something is wrong, feel free to tell it
PS: Sorry for my bad English
Supersu update failed..plz reboot
dopi2010 said:
Supersu update failed..plz reboot
Click to expand...
Click to collapse
I am sorry to hear that. Please make sure you followed steps 6 and 7 with success.
The Tablet must have the bootloader 'unlocked', first of all. I used dc-unlocker2client.exe, to get the code; I paid £4 for the privilage of receiving the unlock code.
I then used ADB to to unlock the tablet.
I then flashed TRWP via ADB
I then flashed the beta-SuperUser via TRWP
Forget the Kingo and One Click rooting methods, they didn't work for me.
See March 25th thread for a complete explanation.
To me it worked like a charm with B005, with the latest B006 it doesn't anymore..
thanks you so much its just worked like a charm on my m2 8
inkyadrian said:
The Tablet must have the bootloader 'unlocked', first of all. I used dc-unlocker2client.exe, to get the code; I paid £4 for the privilage of receiving the unlock code.
I then used ADB to to unlock the tablet.
I then flashed TRWP via ADB
I then flashed the beta-SuperUser via TRWP
Forget the Kingo and One Click rooting methods, they didn't work for me.
See March 25th thread for a complete explanation.
Click to expand...
Click to collapse
Hi......... I have Huawei mediapad 2 10.0 64gb and I got the unlock code of bootloader from the website of huawei but i dont know how to unlock bootloader and root the device .......plz help !!
Ahmadfreihat17 said:
Hi......... I have Huawei mediapad 2 10.0 64gb and I got the unlock code of bootloader from the website of huawei but i dont know how to unlock bootloader and root the device .......plz help !!
Click to expand...
Click to collapse
it's all in here: http://forum.xda-developers.com/mediapad-m2/how-to/guide-unlock-bootlader-twrp-root-huawei-t3322340
It doesn t works
yeah same here, installed kingroot apk, and it tells me no root strategy available and then puts me into a research request?
it does not work
Let me dry 32% in the rooting and says: 1423 ppls, research requests is not enough, please wait.
Same for me.. not working & not enough research requests in the Kingroot .apk
Thanks so much, it worked
ubermenchp said:
Thanks so much, it worked
Click to expand...
Click to collapse
How Did It Worked?
Hi, XDA
I've been searching all around the LG G4 forum and notes, but I can't seem to find the right root method/.imgs/ TWRP for my LG G4.
The variants supported by the guides are H-8xx series, while my series is H-540.
Can someone link me to the post/thread that can help me root my LG G4(H-540) variant?
Helps and suggestions are welcome. Though I might tread very carefully with this LG phones as I've heard that they're very easy to brick.
Thanks in Advance!
You has a LG G4 stylus.
Join the "LG G4 Stylus (Latinoamérica)" group on Facebook. There is a tutorial for downgrade (if your Stylus has Android MM non-rootable).
the_naxhoo said:
You has a LG G4 stylus.
Join the "LG G4 Stylus (Latinoamérica)" group on Facebook. There is a tutorial for downgrade (if your Stylus has Android MM non-rootable).
Click to expand...
Click to collapse
Hi! I checked the group on facebook. But the language are in Spanish(?) and me no hablas espanol, por favor.
But from what I understand if it's right, I have to flash the .kdz?
in order to root, I need to download the flashfire from appstore and xde zip, and xposed from web and then proceed as the image provided?
My Stylus has a LL
nick1235 said:
Hi! I checked the group on facebook. But the language are in Spanish(?) and me no hablas espanol, por favor.
But from what I understand if it's right, I have to flash the .kdz?
in order to root, I need to download the flashfire from appstore and xde zip, and xposed from web and then proceed as the image provided?
My Stylus has a LL
Click to expand...
Click to collapse
but you can use Google Translate...
Well if you now on LP, just use KingRoot for get root on your Stylus. Maybe this take a some times for rooting, but its works.
And IF YOU WANT, install FlashFire and those things, its not a necessary for the root, this is for get Xposed only.
the_naxhoo said:
but you can use Google Translate...
Well if you now on LP, just use KingRoot for get root on your Stylus. Maybe this take a some times for rooting, but its works.
And IF YOU WANT, install FlashFire and those things, its not a necessary for the root, this is for get Xposed only.
Click to expand...
Click to collapse
Hi! Finally got my LG G4 rooted through KingRoot! Installed SuperSU from playstore but I can't seem to get Xposed to work. Any ideas? It's not in the FB group.
nick1235 said:
Hi! Finally got my LG G4 rooted through KingRoot! Installed SuperSU from playstore but I can't seem to get Xposed to work. Any ideas? It's not in the FB group.
Click to expand...
Click to collapse
but, for get SuperSU it's not so simple like install it from Play Store, you must replace all KingRoot's binaries and APK, with a Script. (LINK)
Extract mrw.zip into internal SD (the folder "mrw").
Now install "Terminal Emulator" from Play Store.
Open Terminal and type this:
su (then press Enter)
sh /data/media/0/mrw/root.sh (then press Enter)
Wait until complete and reboot.
So, if you do all previous things, you can use FlashFire and flash the Xposed's .zip
the_naxhoo said:
but, for get SuperSU it's not so simple like install it from Play Store, you must replace all KingRoot's binaries and APK, with a Script. (LINK)
Extract mrw.zip into internal SD (the folder "mrw").
Now install "Terminal Emulator" from Play Store.
Open Terminal and type this:
su (then press Enter)
sh /data/media/0/mrw/root.sh (then press Enter)
Wait until complete and reboot.
So, if you do all previous things, you can use FlashFire and flash the Xposed's .zip
Click to expand...
Click to collapse
I should do it from phone right?
nick1235 said:
I should do it from phone right?
Click to expand...
Click to collapse
obviously...
the_naxhoo said:
obviously...
Click to expand...
Click to collapse
now it kept showing com.kingroot.kinguser has stopped.
and Failure [delete_failed_internal_error]
before it somehow showed me to the kingroot unrooting help & etc. what to do?
[edit]
now im afraid to reboot the phone cause it might softbricked it.
the_naxhoo said:
obviously...
Click to expand...
Click to collapse
Hi! I tried to do what you told me to do previously, now the phone is unrooted, KingRoot is uninstalled after I reboot the phone. After that I tried to run the as you told me to:
-su
-sh /data/media/0/mrw/root.sh
but it says Permission denied, and now after I check the Root checker it's unrooted again. What to do?
nick1235 said:
Hi! I tried to do what you told me to do previously, now the phone is unrooted, KingRoot is uninstalled after I reboot the phone. After that I tried to run the as you told me to:
-su
-sh /data/media/0/mrw/root.sh
but it says Permission denied, and now after I check the Root checker it's unrooted again. What to do?
Click to expand...
Click to collapse
try root with KingRoot again then exec the Script (if you get any error, upload an screenshot). So now reboot.
the_naxhoo said:
try root with KingRoot again then exec the Script (if you get any error, upload an screenshot). So now reboot.
Click to expand...
Click to collapse
So this happened.
Note: Systemless root is not an option on this box due to locked bootloader, do not tell me that root is not an option, because I am rooted right now.
I rooted my Fire TV 2 (FireOS 5.2.7.1) with the hardware method using SuperSU in system mode, although whenever I open SuperSU it immediately crashes. It still comes up with root prompts and I can still accept them, but I can't actually open the app and change settings because it just instantly crashes. Is there a fix for this?
If there isn't a fix for this issue, are there any other SYSTEM MODE superusers that do the same thing as SuperSU.
(Magisk is systemless root, so it doesn't meet the criteria above.)
It's just what amaz. does with apps they don't like^^
But you can edit the supersu config file if you like, in order to access all supersu settings...
The fix is to flash the amonet zip with twrp (aka. unlock the BL), then use magisk... but I guess you know that already, isn't it!?
Sus_i said:
It's just what amaz. does with apps they don't like^^
But you can edit the supersu config file if you like, in order to access all supersu settings...
Click to expand...
Click to collapse
So an Amazon service force closes the package name eu.chainfire.supersu in an attempt to make root Unusable? If that's the case Couldn't I just edit the package name to something else, like what I did with FireStarter Launcher?
Sus_i said:
The fix is to flash the amonet zip with twrp (aka. unlock the BL), then use magisk... but I guess you know that already, isn't it!?
Click to expand...
Click to collapse
Well unless Magisk Devs release a System mode Root that can't happen, for reasons I stated above:
"Systemless root is not an option on this box due to locked bootloader"
Having TWRP doesn't mean it's an unlocked bootloader, I know because I recently tried Magisk out of desperation, the result was that It ended up being stuck on the Amazon Logo and I had to do the unbrick process again.
Toothless_NEO said:
So an Amazon service force closes the package name eu.chainfire.supersu in an attempt to make root Unusable? If that's the case Couldn't I just edit the package name to something else, like what I did with FireStarter Launcher?
Well unless Magisk Devs release a System mode Root that can't happen, for reasons I stated above:
"Systemless root is not an option on this box due to locked bootloader"
Having TWRP doesn't mean it's an unlocked bootloader, I know because I recently tried Magisk out of desperation, the result was that It ended up being stuck on the Amazon Logo and I had to do the unbrick process again.
Click to expand...
Click to collapse
No, it isn't the package name. Most likely it's because an incompatible app theme (missing theme on all fireTV OS versions). If you want to know details, somewhere on xda is a guide, on how to use root/xposed together with xposed modules, as a workarround in order to open up the supersu app on fireTVs. A working theme was material dark, if I remember correct.
Idk why you state magisk isn't an option on 'this' box, since the BL unlock is out and really easy.
Anyway, have fun.
Toothless_NEO said:
So an Amazon service force closes the package name eu.chainfire.supersu in an attempt to make root Unusable? If that's the case Couldn't I just edit the package name to something else, like what I did with FireStarter Launcher?
Well unless Magisk Devs release a System mode Root that can't happen, for reasons I stated above:
"Systemless root is not an option on this box due to locked bootloader"
Having TWRP doesn't mean it's an unlocked bootloader, I know because I recently tried Magisk out of desperation, the result was that It ended up being stuck on the Amazon Logo and I had to do the unbrick process again.
Click to expand...
Click to collapse
He never said or implied having twrp means you have a unlocked bl.
He (as well as I) are wondering why you haven't simply flashed Rortiz2 amonet zip (the unlock) from within your current locked twrp.
This will ultimately unlock the bl of your Sloane.
And solve your issue in minutes + enable you to flash magisk etc.
Regards
Bertonumber1 said:
He never said or implied having twrp means you have a unlocked bl.
He (as well as I) are wondering why you haven't simply flashed Rortiz2 amonet zip (the unlock) from within your current locked twrp.
This will ultimately unlock the bl of your Sloane.
And solve your issue in minutes + enable you to flash magisk etc.
Regards
Click to expand...
Click to collapse
WAIT....
I can unlock the bootloader of my AFTV 2 box- sloane?
Last year i did hardware method to get root/twrp because i was under the impression that one CAN NOT unlock bootloader on this device....
If you can now unlock bootloader on sloane box, when did this happen?
When was this "Rortiz2 amonet" released?
Lastly, since im already rooted and twrp, what do i further need to do to unlock the bootloader?
Thanks many
dovedescent7 said:
WAIT....
I can unlock the bootloader of my AFTV 2 box- sloane?
Last year i did hardware method to get root/twrp because i was under the impression that one CAN NOT unlock bootloader on this device....
If you can now unlock bootloader on sloane box, when did this happen?
When was this "Rortiz2 amonet" released?
Lastly, since im already rooted and twrp, what do i further need to do to unlock the bootloader?
Thanks many
Click to expand...
Click to collapse
I'll answer your pm and your post here...
Yes you can, the boys have presented the full unlock of the Sloane Firetv 2 and Rortiz2 has headlined the thread in "Original Android TV development" section within the Amazon Firetv forum.
All you need to do is follow the OP there, download and flash the zip in current twrp.
If you need any assistance just ask.
Good hearing from you again
Regards
Bertonumber1 said:
I'll answer your pm and your post here...
Yes you can, the boys have presented the full unlock of the Sloane Firetv 2 and Rortiz2 has headlined the thread in "Original Android TV development" section within the Amazon Firetv forum.
All you need to do is follow the OP there, download and flash the zip in current twrp.
If you need any assistance just ask.
Good hearing from you again
Regards
Click to expand...
Click to collapse
I was told that you have to update to the latest version of FireOS and those versions are extremely broken. I can't use that unlock method unless someone finds a way to do it without updating to the latest firmware.
Sus_i said:
No, it isn't the package name. Most likely it's because an incompatible app theme (missing theme on all fireTV OS versions). If you want to know details, somewhere on xda is a guide, on how to use root/xposed together with xposed modules, as a workarround in order to open up the supersu app on fireTVs. A working theme was material dark, if I remember correct.
Idk why you state magisk isn't an option on 'this' box, since the BL unlock is out and really easy.
Anyway, have fun.
Click to expand...
Click to collapse
It's not an option because the unlock requires an update to the latest firmware (stock firmware) or so I was told.
If it's just the theme that is the issue could I just use Preferences editor to change it to a working theme?
Toothless_NEO said:
If it's just the theme that is the issue could I just use Preferences editor to change it to a working theme?
Click to expand...
Click to collapse
Probably not.
This is the old guide, mentioned above:
[PROTIP] How to get SuperSu, Xposed App Settings and other apps that dont open to run
Some apps like supersu or xposed app settings dont open on firetv. Apparently this is caused by the app theme which the firetv is missing. So its unable to open those apps with incompatible themes. To fix those apps and make em run, you need...
forum.xda-developers.com
Sus_i said:
Probably not.
This is the old guide, mentioned above:
[PROTIP] How to get SuperSu, Xposed App Settings and other apps that dont open to run
Some apps like supersu or xposed app settings dont open on firetv. Apparently this is caused by the app theme which the firetv is missing. So its unable to open those apps with incompatible themes. To fix those apps and make em run, you need...
forum.xda-developers.com
Click to expand...
Click to collapse
Interesting, Why does It work to change the theme in Xposed and not through preferences and/or modding the app?