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?
Related
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 ?
Is the framework and app apk available for xposed yet?
Is so has instructions for installing it been posted yet?
Rooted with TWRP and Magisk.
I do have the bug where TWRP does not register any inputs unless you turn the screen off and on again.
(Takes less the a second)
I also have no SD card access in TWRP.
Some have had to turn off hide in Magisk but hide works fine for me. I have two Bank Apps hidden form root and they both work.
I have installed jrummy's busybox and jrummy's Root Checker both work fine..
Don't care for the splash screen "bootloader is unlocked and can't be trusted" so I flash another to replace it.
So I'm ready to work on xposed any help or links to help would be greatly appreciated.
If this is posted in the wrong section please let me know.
The Xposed framework is not available for Android Nougat yet
scallawag said:
Rooted with TWRP and Magisk.
Click to expand...
Click to collapse
Just curious, what process did you use to get TWRP and root in this phone? I'm thinking of buying it, but only if I can do this.
romhippo.com said:
The Xposed framework is not available for Android Nougat yet
Click to expand...
Click to collapse
I followed this link .
https://gist.github.com/eexit/e6d5fc0984e1c7f25376d3dafa819792
I had already unlocked my bootloader
I did none of the backup stuff and started by using Android file transfer to put Magisk in the phones downloads folder.
Then from "Root the device" I went slow so I was sure to follow the directions exactly. Worked fine on the first try.
Then I installed
"BusyBox for Android" by JRummy
"Root Check" by JRummy
It's probable foolish to not do the Backup part.
If you do get your phone stuck in a bootloop look in this thread for help.
https://forum.xda-developers.com/z2-play/how-to/guide-resource-help-thread-t3627615
OK, I just bought a new Moto Z2 Play, and I of course, want to Root it. I have done Root on all my previous smart phones so I have some experience. I read thru all the threads here, but still have some remaining questions.
Where can I get the latest Moto drivers for Win 10 64-bit? I rather have just the drivers, if possible, than some other bloat Moto utilities too.
Where can I get the latest ADB ? I know, there are lots of sources if I search, but I am looking for a safe copy.
What do I use for TWRP? TWRP 3.2.1-0 ? [TWRP][64 bit][3.2.1_r12] ? Alternate TWRP v3.1.1.0 ? I am even asking, because I read a post and its reply, that mentioned that the 64-bit had to be used, but I haven't seen that mentioned anywhere else.
As part of TWRP, should I do the "Swipe to allow modifications for /system" ? I have read posts suggesting either way, and remain unsure which is best.
I plan to install the latest Magisk Manager, v5.5.5. Or should I install simply Magisk v15.3?
Should I plan to Hide the Magisk Manager?
Do I need to, also, install SuperSU and BusyBox from the Google Play Store?
Is there anything additional I need to do, to successfully handle Safety Net ?
Thanks!
Did you read?
https://forum.xda-developers.com/z2-play/how-to/guide-resource-help-thread-t3627615
I used Juniors version of TWRP.
https://forum.xda-developers.com/z2-play/development/twrp-3-2-0-0-moto-z2-play-albus-t3715660
Yes to Magisk Manager.
Yes to Magisk.
No to SuperSU.
No to Busy Box.
First, let me start with a heartfelt thanks! :highfive:
pizza_pablo said:
Did you read?
https://forum.xda-developers.com/z2-play/how-to/guide-resource-help-thread-t3627615
Click to expand...
Click to collapse
Yes, but it has instructions like this:
At first boot twrp will ask for "Swipe to allow modifications for /system" and if you choose to allow it system partition will get modified. So if you choose to reboot back to OS without performing anything in twrp, the OS won't boot (as verity check is enabled in stock OS/kernel) . To avoid this you have to flash either SuperSU or flash any of the verity disabler zips there in xda.
Click to expand...
Click to collapse
Which is why it left feeling unsure, do I swipe or not? Is having the system partition modified "good" and a normal part of this type of root'ing?
Plus, the mention of flashing SuperSU, lead to my question about going that (which you replied 'no').
Maybe I am simply having a case of information overload. With possibly, a strong addition of having too many different opinions which might not all be valid.
WaltA said:
First, let me start with a heartfelt thanks! :highfive:
Yes, but it has instructions like this:
Which is why it left feeling unsure, do I swipe or not? Is having the system partition modified "good" and a normal part of this type of root'ing?
Plus, the mention of flashing SuperSU, lead to my question about going that (which you replied 'no').
Maybe I am simply having a case of information overload. With possibly, a strong addition of having too many different opinions which might not all be valid.
Click to expand...
Click to collapse
I'm glad you have read! :good:
I understand you're dilemma and have also experience info overload, when researching rooting / flashing procedures. It never hurts to read it, yet again and watch any YouTube videos available on the subject.
I always swipe to allow modifications when installing TWRP. Otherwise, TWRP will be in READ ONLY mode.
I am not certain about Busy Box, but haven't needed it. Magisk has A Super User function, so SuperSU is not needed.
I am no expert, just trying to help, so please don't take anything I've said as the gospel. Read everything and then read it again.
pizza_pablo said:
Did you read?
https://forum.xda-developers.com/z2-play/how-to/guide-resource-help-thread-t3627615
I used Juniors version of TWRP.
https://forum.xda-developers.com/z2-play/development/twrp-3-2-0-0-moto-z2-play-albus-t3715660
Yes to Magisk Manager.
Yes to Magisk.
No to SuperSU.
No to Busy Box.
Click to expand...
Click to collapse
Any hint up to which 8.0 security patch update will @Junior Passos method will work
Sent from my Moto Z2 Play using XDA Labs
The Analog Kid said:
Any hint up to which 8.0 security patch update will @Junior Passos method will work
Click to expand...
Click to collapse
No. I'm still on Nougat. I have no interest in Oreo, for this device.
The Analog Kid said:
Any hint up to which 8.0 security patch update will @Junior Passos method will work
Sent from my Moto Z2 Play using XDA Labs
Click to expand...
Click to collapse
I'm on August security patch.
Hi there,
I'm in contact with google support to add a visa card to Google Pay. After several issues finally sorted, I have now a message saying I can not add a card because my phone is altered.
Is the fact that my phone is unlocked won't allow me to use Google Pay / NFC feature?
Thx guys
I managed to make work my banking app and Google Pay with these steps:
1. Enable Magisk hide + enable hide for Google Pay and Google Play services
2. Repackage Magisk Manager app (you will need to enable installation of apps from USB source in system developer settings)
3. Force basic Safetynet test by installing MagiskHide Props Config and selecting Mi 10T pro as a phone model (as a bonus, AR will work too)
Reboot phone and it should work now.
Hummm... after some research, it looks like this method won't work for a long time. Can I unlock my device for the time being? It's unclear how I can do it...
air0ne said:
Hummm... after some research, it looks like this method won't work for a long time. Can I unroot my device for the time being? It's unclear how I can do it...
Click to expand...
Click to collapse
Maybe it will, maybe it won't.. There is a secondary method involving modification of Google Pay sql database which might work for a longer time.
Anyway, to unroot your phone and to pass safetynet you'll need to reflash whole ROM and lock the bootloader (make sure that phone is working before locking).
My Google Pay NFC visa was working after passing safetynet on magisk but stopped working today. Tried to unroot but still got the same error.
I didn't update the app at all so I'm guessing on the server side they did some changes to detect for root / custom rom /unlocked bootloader or something.
Now I'm gonna re-root since removing it didn't helped. Lol
Is a factory reset will do?
ogichi said:
My Google Pay NFC visa was working after passing safetynet on magisk but stopped working today. Tried to unroot but still got the same error.
I didn't update the app at all so I'm guessing on the server side they did some changes to detect for root / custom rom /unlocked bootloader or something.
Now I'm gonna re-root since removing it didn't helped. Lol
Click to expand...
Click to collapse
Safetynet will fail with unlocked bootloader, you need either unlocked bootloader + Magisk hide + basic Safetynet test (can be forced with using for example Mi 10T pro as a phone model), or completely stock rom with locked bootloader. Mine Google pay seems to be still working (at least app doesn't complain about anything ).
air0ne said:
Is a factory reset will do?
Click to expand...
Click to collapse
No, see above.
Thx for your quick answer _mysiak_
I guess there is no stock rom with locked bootloader available for this device yet
air0ne said:
Thx for your quick answer _mysiak_
I guess there is no stock rom with locked bootloader available for this device yet
Click to expand...
Click to collapse
Yes there is. Complete list here, choose the right region and fastboot ROM type. https://xiaomifirmwareupdater.com/miui/gauguin/
_mysiak_ said:
Yes there is. Complete list here, choose the right region and fastboot ROM type. https://xiaomifirmwareupdater.com/miui/gauguin/
Click to expand...
Click to collapse
Cool Thx... My device is a "Mi 10T Lite 5G". Is the "Mi 10T Lite Global" includes the 5G version?
air0ne said:
Cool Thx... My device is a "Mi 10T Lite 5G". Is the "Mi 10T Lite Global" includes the 5G version?
Click to expand...
Click to collapse
All versions are 5G - check which MIUI version exactly do you have now (settings->about) and then download a ROM for the same region.
_mysiak_ said:
All versions are 5G - check which MIUI version exactly do you have now (settings->about) and then download a ROM for the same region.
Click to expand...
Click to collapse
When downloaded, what am I supposed to do? I supposed there is a tutorial somewhere? Sorry to ask. It's been a while since I played with that kind of things :/
Ok I found how to do it. Damn... It's too easy now
Thx again guys
Long story short. After bricking my device (XiaoMiTool V2 hit it hard), I managed to get it back and flash a Fastboot ROM (through XiaoMiFlash).
And Google Pay still say I can not add a Visa Card because my Device is rooted or is altered in a way. I downloaded a root checker and it says I'm not rooted... WTF???
air0ne said:
Long story short. After bricking my device (XiaoMiTool V2 hit it hard), I managed to get it back and flash a Fastboot ROM (through XiaoMiFlash).
And Google Pay still say I can not add a Visa Card because my Device is rooted or is altered in a way. I downloaded a root checker and it says I'm not rooted... WTF???
Click to expand...
Click to collapse
1. is your bootloader locked?
2. do you pass Safetynet (check with this app for example https://play.google.com/store/apps/details?id=org.freeandroidtools.safetynettest&hl=en&gl=US)?
2. do you happen to have MagiskManager still installed?
_mysiak_ said:
1. is your bootloader locked?
Click to expand...
Click to collapse
I flashed a fastboot global ROM. Is it not locked by default? I haven't unlock it afterwards. Is there a way to check? I found only root checker on Google Play
_mysiak_ said:
2. do you pass Safetynet (check with this app for example https://play.google.com/store/apps/details?id=org.freeandroidtools.safetynettest&hl=en&gl=US)?
Click to expand...
Click to collapse
No, I don't
_mysiak_ said:
2. do you happen to have MagiskManager still installed?
Click to expand...
Click to collapse
I never installed it so I doubted it
Crap... should I have used this option when flashing?
"Clean all and lock"
Yes, flash all and lock is the right script. But it's a good point to lock your bootloader only after you are sure that your phone works.
When you are sure that you are with a fresh stock ROM, reboot to fastboot mode and issue command:
" fastboot flashing lock"
Beware, it will erase your data and if you by any chance have modified boot or system partition, you will brick your phone and it must be revived by EDL mode.
_mysiak_ said:
Yes, flash all and lock is the right script. But it's a good point to lock your bootloader only after you are sure that your phone works.
When you are sure that you are with a fresh stock ROM, reboot to fastboot mode and issue command:
" fastboot flashing lock"
Beware, it will erase your data and if you by any chance have modified boot or system partition, you will brick your phone and it must be revived by EDL mode.
Click to expand...
Click to collapse
I tried the command but the device says it was not a "known command" so I flashed it again with the right script (I had to remove the antirollback section tho)
I'm restoring at the moment. Will tell you if I can add my VISA soon
So it works but Google Pay is saying that my Bank does not support this feature (Welcome to Canada!)
All of this for... NOTHING °*&(?$?&)
Ah ah ah... At least, I know how to properly flash my device. Thx a lot _mysiak_
The last time I rooted a phone was 3 years ago, in general whenever I try to root a phone I feel like the entire process has changed and im completely out of the loop.
All i want to do is make it so i can install f.lux and youtube vanced, how do I do this?
I know that I need to install magisk but apparently I also need to enable the bootloader whatever that means?
Sideload, flashing, caprip, boot-image, fastboot, TWRP: these words mean nothing to me, they serve to confuse and demean me.
Is there any resource for figuring out how to go from a new out-of-the-box moto g30 to one which lets me install youtube vanced? Usually I'd look up a tutorial but the only one I found was in spanish and I don't speak spanish.
Thanks for any help you can give.
First things first.
Android has Night Light built in and Youtube Vanced doesn't need root.
But, if you're still serious about rooting and installing magisk to make use of all of the really useful modules, you'll need:
An Unlocked Bootloader: Motorola's Own Guide
Keep in mind that unlocking the bootloader will wipe your phone and void its warranty, so be absolutely sure you want to do it and back up your files.
Then you'll need to manually patch a boot.img from your stock ROM (can be found here.) and flash it using ADB (Android Debug Bridge) using your PC.
I rooted mine within 3 days of owning it and have been enjoying it with no problems whatsoever ever since.
I used this guide as reference. If you have any questions you can always just message me here or on Telegram (@Kuntitled).
samjoebobtomted said:
The last time I rooted a phone was 3 years ago, in general whenever I try to root a phone I feel like the entire process has changed and im completely out of the loop.
All i want to do is make it so i can install f.lux and youtube vanced, how do I do this?
I know that I need to install magisk but apparently I also need to enable the bootloader whatever that means?
Click to expand...
Click to collapse
Bootloader is small program which runs before Android operating system running. Bootloader is first program to run so It is specific for board and processor. -RootJunky
Click to expand...
Click to collapse
Unlocking the bootloader
You can flash a custom system only if the bootloader allows it. Note, though, that the bootloader is locked by default. You can unlock the bootloader, but doing so deletes user data for privacy reasons. After unlocking, all data on the device is erased, that is, both private app data and shared data accessible over USB (including photos and movies). Before attempting to unlock the bootloader, back up any important files on the device. - https://source.android.com/setup/build/running
Click to expand...
Click to collapse
samjoebobtomted said:
Sideload,
Click to expand...
Click to collapse
Generally sideload means installing an app without the playstore.
samjoebobtomted said:
flashing,
Click to expand...
Click to collapse
Flashing usually refers to installing through fastboot mode or recovery
samjoebobtomted said:
caprip,
Click to expand...
Click to collapse
codename or development name for Moto G30
samjoebobtomted said:
boot-image
Click to expand...
Click to collapse
The boot.img is the fie that creates the boot partition
/bootThis is the boot partition of your Android device, as the name suggests. It includes the android kernel and the ramdisk. The device will not boot without this partition. Wiping this partition from recovery should only be done if absolutely required and once done, the device must NOT be rebooted before installing a new one, which can be done by installing a ROM that includes a /boot partition.
-RootJunky
Click to expand...
Click to collapse
samjoebobtomted said:
fastboot,
Click to expand...
Click to collapse
Fastboot refers to several things
Fastboot is the fastboot protocol to communicate with an Android device.
Fastboot.exe is the part of SDK Platform-Tools used to communicate with an Android device when it's in fastboot mode.
samjoebobtomted said:
TWRP:
Click to expand...
Click to collapse
Twrp is a Custom recovery,
The stock recovery has very limited functions,
a custom recovery has more options
/recoveryThis is specially designed for backup. The recovery partition can be considered as an alternative boot partition, that lets the device boot into a recovery console for performing advanced recovery and maintenance operations on it. -RootJunky
Click to expand...
Click to collapse
samjoebobtomted said:
these words mean nothing to me, they serve to confuse and demean me.
Is there any resource for figuring out how to go from a new out-of-the-box moto g30 to one which lets me install youtube vanced? Usually I'd look up a tutorial but the only one I found was in spanish and I don't speak spanish.
Thanks for any help you can give.
Click to expand...
Click to collapse
I have general Moto rooting instructions here
[Guide] Root Motorola with Magisk (UnLocked Bootloader)(Non-TWRP method)
Root Motorola Devices with Magisk Note: This method has been working with most Moto Devices that the Bootloader can be UnLocked. If the Bootloader cannot be Unlocked this method will not work. Please only use this as a reference. If you require...
forum.xda-developers.com
Kuntitled said:
First things first.
Android has Night Light built in and Youtube Vanced doesn't need root.
Click to expand...
Click to collapse
Wait really I didn't even realize I didn't need a root for that lol.
Kuntitled said:
But, if you're still serious about rooting and installing magisk to make use of all of the really useful modules, you'll need:
An Unlocked Bootloader: Motorola's Own Guide
Keep in mind that unlocking the bootloader will wipe your phone and void its warranty, so be absolutely sure you want to do it and back up your files.
Then you'll need to manually patch a boot.img from your stock ROM (can be found here.) and flash it using ADB (Android Debug Bridge) using your PC.
I rooted mine within 3 days of owning it and have been enjoying it with no problems whatsoever ever since.
I used this guide as reference. If you have any questions you can always just message me here or on Telegram (@Kuntitled).
Click to expand...
Click to collapse
Hi thanks this really helped me get the grip of things haha.
I managed to unlock the bootloader but I'm a bit confused on what stock ROM you were referring to, the link you sent had a bunch of possibilities, I assume I need a reteu one since that's the name of my phone's software channel but there's a wide variety of them and the guide you sent seems to have their own ROM as well.
Either way thanks for all the help!
samjoebobtomted said:
Wait really I didn't even realize I didn't need a root for that lol.
Hi thanks this really helped me get the grip of things haha.
I managed to unlock the bootloader but I'm a bit confused on what stock ROM you were referring to, the link you sent had a bunch of possibilities, I assume I need a reteu one since that's the name of my phone's software channel but there's a wide variety of them and the guide you sent seems to have their own ROM as well.
Either way thanks for all the help!
Click to expand...
Click to collapse
You should check the Build Number under "About Phone" in settings, and match it what you find on that link i sent.