Related
i want to buy this phone but cant live without xposed, so is there a 6.0 rom anywhere for this phone? ive looked but havent found anything
ncsuwolfs said:
i want to buy this phone but cant live without xposed, so is there a 6.0 rom anywhere for this phone? ive looked but havent found anything
Click to expand...
Click to collapse
Sultanxda and Arter97 CM MM Roms are still up im sure you can find a few others too
Edit: Opps sorry thought was OP3 thread :laugh:
ncsuwolfs said:
i want to buy this phone but cant live without xposed, so is there a 6.0 rom anywhere for this phone? ive looked but havent found anything
Click to expand...
Click to collapse
This phone launched with nougat. You can't run marshmallow on it.
liam_davenport said:
Sultanxda and Arter97 CM MM Roms are still up im sure you can find a few others too
Click to expand...
Click to collapse
where do i find those? (i have searched but can only find cm14 for pixel?
toknitup420 said:
This phone launched with nougat. You can't run marshmallow on it.
Click to expand...
Click to collapse
this is what i was afraid of....
ncsuwolfs said:
where do i find those? (i have searched but can only find cm14 for pixel?
this is what i was afraid of....
Click to expand...
Click to collapse
They do have magisk for this phone. I haven't used it but from what I've seen it's similar to xposed.
toknitup420 said:
They do have magisk for this phone. I haven't used it but from what I've seen it's similar to xposed.
Click to expand...
Click to collapse
I don't understand how it works but unless I misunderstood if you go to the official Magisk thread the creator claimed he was able to run Xposed with Magisk because his app prevented Xposed from needing to write anything to the system image. I supposed if you can't live without Xposed that would be worth looking into further.
There are no Marshmallow ROM's anywhere for this phone.
Never was, never will be.
Magisk isn't an Xposed replacement.
There is no replacement for Xposed.
Dammit, I miss my ~17 Xposed modules.
Most of which gave me options that you won't find on any custom Nougat ROM.
toknitup420 said:
They do have magisk for this phone. I haven't used it but from what I've seen it's similar to xposed.
Click to expand...
Click to collapse
It's a root option. As in you can run SuperSU or Magisk. Magisk has mods that can accomplish certain things that Xposed did but the majority of them don't work with the pixel so don't count on a suitable replacement.
jhs39 said:
I don't understand how it works but unless I misunderstood if you go to the official Magisk thread the creator claimed he was able to run Xposed with Magisk because his app prevented Xposed from needing to write anything to the system image. I supposed if you can't live without Xposed that would be worth looking into further.
Click to expand...
Click to collapse
The Magisk on pixel is supported by a guy that frequents the RR thread and he modded Magisk to work on the pixel so it's unofficial. Also there is NO Xposed for android n
---------- Post added at 11:55 PM ---------- Previous post was at 11:54 PM ----------
CZ Eddie said:
Magisk isn't an Xposed replacement.
Click to expand...
Click to collapse
This isn't completely true. There are Magisk mods that overlap things that Xposed was capable of. So depending on what you are trying to do and IF mods even worked for the pixel. It could be a replacement for some.
The Magisk on pixel is supported by a guy that frequents the RR thread and he modded Magisk to work on the pixel so it's unofficial. Also there is NO Xposed for android n
---------- Post added at 11:55 PM ---------- Previous post was at 11:54 PM ----------
Well that explains why on the official Magisk page the developer said he didn't know if there would ever be a working version for the Pixel phones but people are using Magisk anyway. Unfortunately Magisk seems to run into the same problems as SU on the Pixel in that it doesn't always install properly or maintain root if it does install--plus most Magisk modules don't work with the Pixel, which makes it much less functional than on other phones.
jhs39 said:
Well that explains why on the official Magisk page the developer said he didn't know if there would ever be a working version for the Pixel phones but people are using Magisk anyway. Unfortunately Magisk seems to run into the same problems as SU on the Pixel in that it doesn't always install properly or maintain root if it does install--plus most Magisk modules don't work with the Pixel, which makes it much less functional than on other phones.
Click to expand...
Click to collapse
I've been running magisk since 11.6 was dropped. I haven't had any issues keeping root or installing. Works every time and I flashing a new rom every 3 or 4 days.
Same with SU.
For magisk people keep leaving busy box in Magisk Manager turned on so it screws up root. It's in the magisk FAQ.
pcriz said:
I've been running magisk since 11.6 was dropped. I haven't had any issues keeping root or installing. Works every time and I flashing a new rom every 3 or 4 days.
Same with SU.
For magisk people keep leaving busy box in Magisk Manager turned on so it screws up root. It's in the magisk FAQ.
Click to expand...
Click to collapse
If you've been running SU for more than a few months on the Pixel then you know Google broke root on it and SU had to rewrite the app to fix the issue. That doesn't happen on other phones and is very likely intentional on the part of Google. At another point SU was suddenly causing problems and SU devs had to add a boot signature file to the flashing process. Again, this kind of thing doesn't happen with other phones. Pretending that SU and Magisk have always worked without problems on the Pixel is extremely misleading.
jhs39 said:
If you've been running SU for more than a few months on the Pixel then you know Google broke root on it and SU had to rewrite the app to fix the issue. That doesn't happen on other phones and is very likely intentional on the part of Google. At another point SU was suddenly causing problems and SU devs had to add a boot signature file to the flashing process. Again, this kind of thing doesn't happen with other phones. Pretending that SU and Magisk have always worked without problems on the Pixel is extremely misleading.
Click to expand...
Click to collapse
Lol why would I lie. I've been on magisk now since Feb. Tell me why I don't lose root?
Maybe you can't get it to work but that doesn't mean it doesn't work.
Also if you are following the evolution of things, signed builds are more secure. Root isn't broken you just have to resign the boot image because of HOW root is attained on the pixels.
Yes it only happens on the pixels because of the partition changes in the pixel. Since they have to be signed now with any bootloader from may and older, users need the verified boot signer.
But if you are paying five minutes worth of attention to all this you would know that all you have to do is flash the April bootloader and there is no longer a requirement for builds to be signed.
I've been through all this a million times. That said I'm still rooted like a champ.
Yeah for the pixel it's pretty straight forward, if you want to root use chainfire's zip it's 2.79 SR3, you're even advised on 2.82 that pixel users will not want to upgrade.
As far as the may bootloader situation, flash the april bootloader and you don't need to bother with the signing zip. Besides, I think dealing with knox was much worse
pcriz said:
Lol why would I lie. I've been on magisk now since Feb. Tell me why I don't lose root?
Maybe you can't get it to work but that doesn't mean it doesn't work.
Also if you are following the evolution of things, signed builds are more secure. Root isn't broken you just have to resign the boot image because of HOW root is attained on the pixels.
Yes it only happens on the pixels because of the partition changes in the pixel. Since they have to be signed now with any bootloader from may and older, users need the verified boot signer.
But if you are paying five minutes worth of attention to all this you would know that all you have to do is flash the April bootloader and there is no longer a requirement for builds to be signed.
I've been through all this a million times. That said I'm still rooted like a champ.
Click to expand...
Click to collapse
I've been paying a lot of attention to it actually. When you have to flash an old bootloader to prevent boot looping (which is what actually happens if you use the up to date bootloader) or you have to flash a boot signature file that wasn't previously needed then the flashing procedure suddenly changes again I wouldn't say it's easy to maintain root on a Pixel. I guess different people have different definitions for what easy is. As for Knox, I used to have many Samsung phones and once a procedure was figured out to get around it and root you were good for as long as you had the phone. With the Pixels Google seems to be actively trying to screw up apps that create root or bypass safety net via its monthly updates. It's a completely different situation in my opinion.
jhs39 said:
I've been paying a lot of attention to it actually. When you have to flash an old bootloader to prevent boot looping (which is what actually happens if you use the up to date bootloader) or you have to flash a boot signature file that wasn't previously needed then the flashing procedure suddenly changes again I wouldn't say it's easy to maintain root on a Pixel. I guess different people have different definitions for what easy is. As for Knox, I used to have many Samsung phones and once a procedure was figured out to get around it and root you were good for as long as you had the phone. With the Pixels Google seems to be actively trying to screw up apps that create root or bypass safety net via its monthly updates. It's a completely different situation in my opinion.
Click to expand...
Click to collapse
You went from saying "Magisk and SuperSU don't install properly or don't keep root" to talking about the changes to boot signing on newer bootloaders.
If you are going to share information at least try to be accurate. There is a whole slew of users in the development section running rooted ROMs just fine but if a new user reads your posts they will assume root is broken and flashing the pixel leads to boot loops.
You don't want to deal with the verified boot signer all you need to do is flash the april bootloader and reboot. It happens once. If that is too difficult then maybe those same people shouldn't bother flashing anything period.
No one said flashing and modding would be easy but flashing a bootloader ain't hard.
You might also want to take a look at the other threads in the Q&A which show people unable to flash TWRP, people boot looping when they flash TWRP, people unable to maintain root or flash custom Roms, etc. Even if you are able to maintain root like a pro there is plenty of very easy to find evidence from other people who don't have the same no problems experience as you.
jhs39 said:
You might also want to take a look at the other threads in the Q&A which show people unable to flash TWRP, people boot looping when they flash TWRP, people unable to maintain root or flash custom Roms, etc. Even if you are able to maintain root like a pro there is plenty of very easy to find evidence from other people who don't have the same no problems experience as you.
Click to expand...
Click to collapse
The only thing that proves is we have a ton of users that don't take the time to research.
You got users coming back from O that don't know they need an Android N bootloader in both slots to flash TWRP again.
You have users that are fastbooting ZIP files
You have users fastboot FLASHING TWRP
I read through those threads and in just about every case if you can't get recovery and root on the april boot loader it's probably user error. Welcome to XDA, it's the same on every device.
I guess all the guys that are rooted must full it. Or wizards or something.
I guess reading step by step directions makes me a wizard.
pcriz said:
I read through those threads and in just about every case if you can't get recovery and root on the april boot loader it's probably user error. QUOTE]
I answer these questions a lot and that is most certainly true.
Click to expand...
Click to collapse
pcriz said:
The only thing that proves is we have a ton of users that don't take the time to research.
You got users coming back from O that don't know they need an Android N bootloader in both slots to flash TWRP again.
You have users that are fastbooting ZIP files
You have users fastboot FLASHING TWRP
I read through those threads and in just about every case if you can't get recovery and root on the april boot loader it's probably user error. Welcome to XDA, it's the same on every device.
I guess all the guys that are rooted must full it. Or wizards or something.
I guess reading step by step directions makes me a wizard.
Click to expand...
Click to collapse
Actually that's absolutely not true. I came from a Nexus 6P. On the XDA threads for that phone there is an accurate, clear, up to date step by step guide on how to flash anything with that phone, including separate instructions for how to root, install a custom recovery, how to install a custom Rom and how to go back to stock. On the Pixels the threads are a complete free for all filled with confusing, contradictory and inaccurate information. I just read posts from earlier today from someone who is getting boot loops when flashing SuperSu. Not a single person responded by suggesting that he use the April bootloader. The suggested solution (which didn't work) was to flash the boot sig zip. How exactly is somebody supposed to research flashing on the Pixel when the XDA threads for this phone are a complete shambles? And since you are supposedly such an expert at flashing on this phone why don't you do something useful and help other people who are having problems instead of wasting everybody's time with your utterly pointless posts about how easy it is to flash on this phone and how people having trouble are idiots who didn't do their own research? You aren't simply part of the problem, dude--you are literally the personification of everything that is wrong with XDA.
jhs39 said:
.
Click to expand...
Click to collapse
This discussion ain't worth reading whatever it is you typed dude. I'm going to agree to disagree.
Sorry stable root is an unattainable unicorn for you. Sorry you're having such a difficult time. Sorry that making excuses for false information is a priority over finding out how it's actually done.
Happy flashing, best of luck to you sport.
Hello,
I recently started using Moto G6 Play, and am wondering now what is the best and easiest option for root. I searched a bit on the forum and found one thread for root that includes unlocking bootloader and is more complicated than some info i have found on google - rooting with KingoRoot without pc (if that's even possible).
Device info: XT1922-3, 3/32gb
Build number: OPPS27.91-177-2
Android 8, latest security patches, available 9 Pie update.
Soo, my question is - Will methdos like KingoRoot work because that will suit just fine for me since i do not want to flash anything extra, but only debloat and optimize stock rom? And i suppose my bootloader is locked because when i power up with volume down + power it says oem_locked so thats another reason for pcless root.
Anyone can help?
petar_markovic said:
Hello,
I recently started using Moto G6 Play, and am wondering now what is the best and easiest option for root. I searched a bit on the forum and found one thread for root that includes unlocking bootloader and is more complicated than some info i have found on google - rooting with KingoRoot without pc (if that's even possible).
Device info: XT1922-3, 3/32gb
Build number: OPPS27.91-177-2
Android 8, latest security patches, available 9 Pie update.
Soo, my question is - Will methdos like KingoRoot work because that will suit just fine for me since i do not want to flash anything extra, but only debloat and optimize stock rom? And i suppose my bootloader is locked because when i power up with volume down + power it says oem_locked so thats another reason for pcless root.
Anyone can help?
Click to expand...
Click to collapse
DONT USE KINGO ROOT. For one you have to unlock the bootloader anyway so you can root please just use my guide https://forum.xda-developers.com/g6-play/how-to/guide-t3929928 to avoid screwing up your phone with any root like KINGO root. You have come on here asking what the preferred method is and over 5,000 people are using my guide lol so my guide is the preferred. You need all that in order to pass play store safety net if you even want be able to download alot of games or if you download the apks the game won't load and KINGO root 100% fails safety net checks to make sure your passing it
ninjakira said:
DONT USE KINGO ROOT. For one you have to unlock the bootloader anyway so you can root please just use my guide https://forum.xda-developers.com/g6-play/how-to/guide-t3929928 to avoid screwing up your phone with any root like KINGO root. You have come on here asking what the preferred method is and over 5,000 people are using my guide lol so my guide is the preferred. You need all that in order to pass play store safety net if you even wont be able to download alot of games or if you download the apks the game won't load and KINGO root 100% fails safety net checks to make sure your passing it
Click to expand...
Click to collapse
Hi, thanks for quick response,
Well yea, i gave up on KingoRoot after some researching that it might not be safest thing to use. But it seemed pretty handy for my situation. And yes i saw your guide and considered it as option but didnt really find any more reliable threads (maybe i didnt search long enough tho). Btw, as i noticed you method requires unlocked bootloader so if you have some thread available about it throw it here if you can, if not thanks anyways.
Regards
petar_markovic said:
Hi, thanks for quick response,
Well yea, i gave up on KingoRoot after some researching that it might not be safest thing to use. But it seemed pretty handy for my situation. And yes i saw your guide and considered it as option but didnt really find any more reliable threads (maybe i didnt search long enough tho). Btw, as i noticed you method requires unlocked bootloader so if you have some thread available about it throw it here if you can, if not thanks anyways.
Regards
Click to expand...
Click to collapse
The link for unlocking it is in the guide...... Just read the guide. And my guide is plenty reliable on here you just have to read it.....
petar_markovic said:
Hi, thanks for quick response,
Well yea, i gave up on KingoRoot after some researching that it might not be safest thing to use. But it seemed pretty handy for my situation. And yes i saw your guide and considered it as option but didnt really find any more reliable threads (maybe i didnt search long enough tho). Btw, as i noticed you method requires unlocked bootloader so if you have some thread available about it throw it here if you can, if not thanks anyways.
Regards
Click to expand...
Click to collapse
It's not an option, it's THE WAY. It's how to root.
Unlock bootloader, flash TWRP, use TWRP to flash encryption disabler and magisk.
Systemless root is the way now. Root is in the boot.img now. One click roots are dead.
The end
ninjakira said:
The link for unlocking it is in the guide...... Just read the guide. And my guide is plenty reliable on here you just have to read it.....
Click to expand...
Click to collapse
Ok, i will post an update on how it went if i actually decide to root.
madbat99 said:
It's not an option, it's THE WAY. It's how to root.
Unlock bootloader, flash TWRP, use TWRP to flash encryption disabler and magisk.
Systemless root is the way now. Root is in the boot.img now. One click roots are dead.
The end
Click to expand...
Click to collapse
Got it.
What disadvantages are there to unlocking bootloader but not rooting? Just bought the 3a XL. Have rooted every phone since my og HTC Incredible. Don't really need to root now, but don't think I would want to later if I would have to unlock bootloader later and wipe my phone in the process. If I unlock now, that gives me the option of rooting later a little less painlessly, I would think.
So, any major disadvantages? I'm really a noob at all this. Older guy, over 50, don't know much technical stuff about all this, but follow directions pretty well.
Thanks!
fjm568 said:
What disadvantages are there to unlocking bootloader but not rooting? Just bought the 3a XL. Have rooted every phone since my og HTC Incredible. Don't really need to root now, but don't think I would want to later if I would have to unlock bootloader later and wipe my phone in the process. If I unlock now, that gives me the option of rooting later a little less painlessly, I would think.
So, any major disadvantages? I'm really a noob at all this. Older guy, over 50, don't know much technical stuff about all this, but follow directions pretty well.
Thanks!
Click to expand...
Click to collapse
Well, pretty much the only disadvantages are the same disadvantages if you were to unlock and root.
If someone physically got the device they'd easily be able to flash third party firmware to it.
That's all I can really think of off the top of my head.
Sent from my Google Pixel 3a XL using XDA Labs
Well, if you unlock the bootloader, many apps will flag your phone as rooted/tampered and may not work. Google Pay and Pokemon Go for example. There's actually no advantage to unlocking the bootloader without rooting and using Magisk Hide. I mean, you wouldn't have to wipe your phone later when you would decide to unlock the BL.... this may be a plus.
I think you'll create more hassle on yourself by unlocking the BL without also rooting it. Either go all in and do both, or leave it locked.
DriveEuro said:
Well, if you unlock the bootloader, many apps will flag your phone as rooted/tampered and may not work. Google Pay and Pokemon Go for example. There's actually no advantage to unlocking the bootloader without rooting and using Magisk Hide. I mean, you wouldn't have to wipe your phone later when you would decide to unlock the BL.... this may be a plus.
I think you'll create more hassle on yourself by unlocking the BL without also rooting it. Either go all in and do both, or leave it locked.
Click to expand...
Click to collapse
But also a word of caution unlock your bootloader b efore it is patched happened on the Verizon pixel XL og
All the downside of rooting, but none of the benefits.
What is your reasoning for wanting to do this? So that you could root later or reload the OS if the phone becomes inoperable? Then just set the OEM Unlocking slider to on, but don't actually perform the unlock, and then you can can unlock at any time it might become necessary. Remember, unlocking a Pixel is a far simpler thing than unlocking most other devices, as long as OEM unlocking is turned on, it's a simple fastboot command.
acejavelin said:
What is your reasoning for wanting to do this? So that you could root later or reload the OS if the phone becomes inoperable? Then just set the OEM Unlocking slider to on, but don't actually perform the unlock, and then you can can unlock at any time it might become necessary. Remember, unlocking a Pixel is a far simpler thing than unlocking most other devices, as long as OEM unlocking is turned on, it's a simple fastboot command.
Click to expand...
Click to collapse
He doesn't want to have to wipe later on though, which is fair enough imo.
That's the main reason I unlock and root as soon as I get new phones.
Sent from my Google Pixel 3a XL using XDA Labs
Skittles9823 said:
He doesn't want to have to wipe later on though, which is fair enough imo.
That's the main reason I unlock and root as soon as I get new phones.
Sent from my Google Pixel 3a XL using XDA Labs
Click to expand...
Click to collapse
This.
It's the wipe by unlocking later that I want to avoid.
Actually, my only reason for rooting is Titanium Backup. I like being able to backup and restore certain apps data and being able to freeze certain apps. Which actually bit me in the ass on my unlocked and (formerly)rooted Pixel 2. I had a forced OTA happen to me recently, which unrooted my phone and I now can't retrieve some apps data and unfreeze some apps without re-rooting. I don't know how the OTA went through since I was rooted with Magisk and TWRP.
So, being that there are ways to do backups of the 2 apps data that I used TiBU to do without being rooted, I would think that unlocking the bootloader so that I could reload the OS easier later would be the thing to do. I don't use Google Pay or the other similar apps, so the unlocked bootloader shouldn't hurt me.
What other apps would be flagged and not work with an unlocked bootloader?
When going to Android 11 I'd like to keep my device unrooted.
The only things I want to keep is vanced (will install the version w/I magisk) and my Hotspot. I know there's some play store Hotspot apks but I can never get them to work.
Last update the build.prop edit no longer worked, but i found a zip that enabled it from XDA. Believe it needed to be flashed in magisk but not sure.
I intend to try and flash the 11 OTA and just remove -w, hoping I'll keep the Hotspot modification.
If it matters, my SO wanted me to get back into pokemon go and I can't play on a rooted device. Tried magisk hide but that didn't work.
Any advice would be appreciated, cheers.
AlPoo said:
When going to Android 11 I'd like to keep my device unrooted.
The only things I want to keep is vanced (will install the version w/I magisk) and my Hotspot. I know there's some play store Hotspot apks but I can never get them to work.
Last update the build.prop edit no longer worked, but i found a zip that enabled it from XDA. Believe it needed to be flashed in magisk but not sure.
I intend to try and flash the 11 OTA and just remove -w, hoping I'll keep the Hotspot modification.
If it matters, my SO wanted me to get back into pokemon go and I can't play on a rooted device. Tried magisk hide but that didn't work.
Any advice would be appreciated, cheers.
Click to expand...
Click to collapse
You won't be able to keep any Magisk modifications without magisk. The way Magisk works is systemless so it needs to have the Magisk installed to mount the modules over the necessary directories. Also, for Pixels on Android Q and Android R you can't mount the system partitions to even modify them in the first place, so even if Magisk did directly modify the partitions they wouldn't work for devices with our logical partitions.
Pretty sure the way PoGo detects root is by searching for files/folders in your install storage called Magisk, twrp, or various other root names. So I'd suggest making sure those kinds of folders are cleaned out or renamed to something unrelated to root.
Also, Magisk doesn't support R yet so you won't be able to root yet even if you wanted to.
Sent from my Pixel 3a XL using XDA Labs
Skittles9823 said:
You won't be able to keep any Magisk modifications without magisk. The way Magisk works is systemless so it needs to have the Magisk installed to mount the modules over the necessary directories. Also, for Pixels on Android Q and Android R you can't mount the system partitions to even modify them in the first place, so even if Magisk did directly modify the partitions they wouldn't work for devices with our logical partitions.
Pretty sure the way PoGo detects root is by searching for files/folders in your install storage called Magisk, twrp, or various other root names. So I'd suggest making sure those kinds of folders are cleaned out or renamed to something unrelated to root.
Also, Magisk doesn't support R yet so you won't be able to root yet even if you wanted to.
Sent from my Pixel 3a XL using XDA Labs
Click to expand...
Click to collapse
Ah. So maybe I should keep the -w in the OTA to make sure to clean out some folder/files.
Didnt know R wasn't supported yet, kinda figured it wouldn't be since it just came out, but thanks for saving the hassle of finding out the hard way.
I've read going through threads here and saw that some people had lost root but kept some modifications after updating. Hoped that would have worked or there'd be able way without root out there that I was unaware of.
Anyway, thanks for the response!
AlPoo said:
Ah. So maybe I should keep the -w in the OTA to make sure to clean out some folder/files.
Didnt know R wasn't supported yet, kinda figured it wouldn't be since it just came out, but thanks for saving the hassle of finding out the hard way.
I've read going through threads here and saw that some people had lost root but kept some modifications after updating. Hoped that would have worked or there'd be able way without root out there that I was unaware of.
Anyway, thanks for the response!
Click to expand...
Click to collapse
Well I just installed PoGo real quick after checking my internal storage and renaming any file/folder with Magisk in the name to remove Magisk, and with Magisk hidden with a random package name and app name and PoGo hidden in magisk hide I was able to successfully log in without it detecting anything. So if you do wish to have modifications once Magisk supports R just make sure to keep an eye on your files/folder names and you should be all good :good:
As for the threads you've been reading, that's definitely curious. Do you know if they were pixel users? Or just people using a GSI or something?
Sent from my Pixel 3a XL using XDA Labs
AlPoo said:
Ah. So maybe I should keep the -w in the OTA to make sure to clean out some folder/files.
Didnt know R wasn't supported yet, kinda figured it wouldn't be since it just came out, but thanks for saving the hassle of finding out the hard way.
I've read going through threads here and saw that some people had lost root but kept some modifications after updating. Hoped that would have worked or there'd be able way without root out there that I was unaware of.
Anyway, thanks for the response!
Click to expand...
Click to collapse
OTA will not wipe your phone. I updated this way last night from Q, not rooted.
Just realize that the Android 11 developer release is not designed to be run as a "daily driver". It's a first alpha release and it is going to be full of bugs and incompatibilities.
There is zero reason to install this on anything but a spare phone that you develop on.
sic0048 said:
Just realize that the Android 11 developer release is not designed to be run as a "daily driver". It's a first alpha release and it is going to be full of bugs and incompatibilities.
There is zero reason to install this on anything but a spare phone that you develop on.
Click to expand...
Click to collapse
24 hours in. Absolutely zero issues so far.
poncespr said:
24 hours in. Absolutely zero issues so far.
Click to expand...
Click to collapse
Thanks for the progress report....
My comment was directed mainly at the OP. Somehow I don't think he is Google's target audience for the developer build and I am afraid he will be the type that complains or begs for help when things don't work right.
That being said, I am also surprised that the release is running so well......
sic0048 said:
Thanks for the progress report....
My comment was directed mainly at the OP. Somehow I don't think he is Google's target audience for the developer build and I am afraid he will be the type that complains or begs for help when things don't work right.
That being said, I am also surprised that the release is running so well......
Click to expand...
Click to collapse
No disrespect. Just commenting on my experience.
I am also surprised. Only weird thing was asking to register my sim. I'm guessing it was looking for an esim. Other than that, not a single force close or slow down. But to be honest it doesn't look like a big update as the version number suggest. Feels more like a little spit and polish. Like this should be Android Q 10.1.
I myself gave up rooting. The only two reasons I was rooting were adaway and viper.
poncespr said:
.But to be honest it doesn't look like a big update as the version number suggest. Feels more like a little spit and polish. Like this should be Android Q 10.1.
Click to expand...
Click to collapse
As with most major android updates since Oreo. Most visible changes now are slight UI revisions and some new features.
However, there are a load of under the hood changes being made. Some for the better, some for the worse.
Sent from my Pixel 3a XL using XDA Labs
Not to thread hijack, (which is what i am going to do anyway, but being POLITE about it ?), can anyone point me to a Hotspot solution for Sprint, without root? All the other various methods/tricks i used in the past that worked, like manually editing the LTE APN etc, just aren't working on this 3aXL.
Hey everyone, I guess I'm not the only one wanting to root there Razr 5G.
I've always rooted using adb and a twrp.img for the specific model of phone.
But, is there any truth to the Kingroot method out there if you Google "root Razr 5G"?
LormaD said:
Hey everyone, I guess I'm not the only one wanting to root there Razr 5G.
I've always rooted using adb and a twrp.img for the specific model of phone.
But, is there any truth to the Kingroot method out there if you Google "root Razr 5G"?
Click to expand...
Click to collapse
I wouldn't trust Kingroot. Too many reports on it being malware
Kingroot is very much malware, until someone unlocks the bootloader and goes through getting twrp working I'd hold off on rooting. Of course with the screens being a first gen nearly beta thing I doubt anyone out there is willing to give up the warranty to unlock the bootloader(even though the unlocked 5g model has an unlockable bootloader). Its gonna be a catch 22 for at least a year or until someone gets a phone out of warranty.
Edit: my source for calling kingroot malware is a stack of 3 old budget phones with charging screens that play ads after the kingroot process was performed, as far as I can tell there's no easy way to get rid of them even with working root.
sanyokt4j said:
Kingroot is very much malware, until someone unlocks the bootloader and goes through getting twrp working I'd hold off on rooting. Of course with the screens being a first gen nearly beta thing I doubt anyone out there is willing to give up the warranty to unlock the bootloader(even though the unlocked 5g model has an unlockable bootloader). Its gonna be a catch 22 for at least a year or until someone gets a phone out of warranty.
Edit: my source for calling kingroot malware is a stack of 3 old budget phones with charging screens that play ads after the kingroot process was performed, as far as I can tell there's no easy way to get rid of them even with working root.
Click to expand...
Click to collapse
Sucks that you couldn't patch the boot image with Magisk
blackknightavalon said:
Sucks that you couldn't patch the boot image with Magisk
Click to expand...
Click to collapse
These are your usual throw away burners you'd get at walmart/gas station, not much effort was put into dealing with any of them. Just wanted to use as a cheap chromecast remote but oh well I came upon a cheap nexus 6, works excellent and has wireless charging so it lives on the coffee table now.
sanyokt4j said:
These are your usual throw away burners you'd get at walmart/gas station, not much effort was put into dealing with any of them. Just wanted to use as a cheap chromecast remote but oh well I came upon a cheap nexus 6, works excellent and has wireless charging so it lives on the coffee table now.
Click to expand...
Click to collapse
Oof. If price is a factor then may I recommend the Pixel 4a. 3 years of Android updates and Google releases the factory images the day of the updates (so you can easily flash a Magisked-up boot.img)
blackknightavalon said:
Oof. If price is a factor then may I recommend the Pixel 4a. 3 years of Android updates and Google releases the factory images the day of the updates (so you can easily flash a Magisked-up boot.img)
Click to expand...
Click to collapse
Thanks for the recommendation, but I think you misunderstood, I'm in no way looking for a device these stupid throwaways made it into my life after friends ditched them I just figured it'd be interesting to see what oneclick root options worked. Funnily kingroot was the only one that worked but came at the expense of extra junk and me being extremely vary of even giving the device a wifi connection.
LormaD said:
Hey everyone, I guess I'm not the only one wanting to root there Razr 5G.
I've always rooted using adb and a twrp.img for the specific model of phone.
But, is there any truth to the Kingroot method out there if you Google "root Razr 5G"?
Click to expand...
Click to collapse
sanyokt4j said:
Kingroot is very much malware, until someone unlocks the bootloader and goes through getting twrp working I'd hold off on rooting. Of course with the screens being a first gen nearly beta thing I doubt anyone out there is willing to give up the warranty to unlock the bootloader(even though the unlocked 5g model has an unlockable bootloader). Its gonna be a catch 22 for at least a year or until someone gets a phone out of warranty.
Edit: my source for calling kingroot malware is a stack of 3 old budget phones with charging screens that play ads after the kingroot process was performed, as far as I can tell there's no easy way to get rid of them even with working root.
Click to expand...
Click to collapse
I can confirm the T-mobile/Sprint ones are eligible for bootloader unlock via Motorola's website and I have rooted my Razr 5G and posted the patched boot.img in the General section.
I have an unlocked razr with bootloader unlocked, and rooted via a magisk patched boot image. I am officially volunteering my phone if someone will help me in porting twrp. I have no clue how to do it myself.
Hi, i see this:
How to Root Motorola Razr 5G and Unlock Bootloader
Want to root Motorola Razr 5G with Magisk? Here's how to root Motorola Razr 5G along with guide to unlock bootloader.
www.ytechb.com