Related
Hello,
I have been trying very hard to grasp on this myself, and not post a thread like this but I'm afraid my head is spinning and I'm hoping someone here will be kind enough to help me.
I have owned an M8S for a while and would like to gain root access (mainly so I can use link2sd and expand storage space). I followed many links and threads carefully, but I am nervous to begin any process as the instructions are... vague, I guess. There are many of you who disagree with me I'm sure, but please be patient with me.
I have read extensively through this thread: http://forum.xda-developers.com/htc-one-m8/help/make-custom-recovery-htc-one-m8s-t3114245
Tried to see how much of this (Linux) guide, though I run a Windows 10 machine: http://forum.xda-developers.com/htc-one-m8/help/rooting-htc-one-m8s-t3235232
I hope you can help me learn.
I have rooted several android devices before, and I've never been very confused by the process, but this one has left me lost.
Happy New Year and thanks for any help and support!
Pk
I don't have the M8S, but the process looks straightforward (similar to M8, as well as most fairly recent HTC devices):
1) Unlock bootloader via HTCDev.com (go to the website, and its pretty self-explantory)
2) Use fastboot to flash TWRP custom recovery
3) Flash SuperSU and Busybox using TWRP
I'd also add a step before 3 above, use TWRP to make a backup of the stock ROM. Once you have that backed up, anything that happens from step 3 is reversible by restoring the backup.
In fact, everything in the process is totally reversible by RUU, with the exception that the bootloader flag will only every say RELOCKED instead of LOCKED.
Is there a particular question, or step you have a problem with.
redpoint73 said:
I don't have the M8S, but the process looks straightforward (similar to M8, as well as most fairly recent HTC devices):
1) Unlock bootloader via HTCDev.com (go to the website, and its pretty self-explantory)
2) Use fastboot to flash TWRP custom recovery
3) Flash SuperSU and Busybox using TWRP
I'd also add a step before 3 above, use TWRP to make a backup of the stock ROM. Once you have that backed up, anything that happens from step 3 is reversible by restoring the backup.
In fact, everything in the process is totally reversible by RUU, with the exception that the bootloader flag will only every say RELOCKED instead of LOCKED.
Is there a particular question, or step you have a problem with.
Click to expand...
Click to collapse
Thank you. this is what I hoped the process was but I was having difficulty reassuring myself!
I'll try this over the weekend and come back with a report. I really appreciate your help redpoint73 :highfive:
portachking said:
Thank you. this is what I hoped the process was but I was having difficulty reassuring myself!
Click to expand...
Click to collapse
Just read and learn as much as you can before doing anything. Don't do anything that isn't form a current, reputable source. Do those things, and you will be fine.
portachking, I am very new to rooting and all that follows it. I would be very grateful if you post back your experiences when you have time, with the challenges you met (if any) and how you solved them...
I read from this page that "When the phone is rooted in changes to the phone are reset on restart". Is this the case for you as well?
Akitirija said:
portachking, I am very new to rooting and all that follows it. I would be very grateful if you post back your experiences when you have time, with the challenges you met (if any) and how you solved them...
I read from this page that "When the phone is rooted in changes to the phone are reset on restart". Is this the case for you as well?
Click to expand...
Click to collapse
I'm finally getting a chance to do this today. I will post again when I finish.
UPDATE:
M8S is now rooted and working fine. Thanks for your help repoint73!
portachking said:
I'm finally getting a chance to do this today. I will post again when I finish.
UPDATE:
M8S is now rooted and working fine. Thanks for your help repoint73!
Click to expand...
Click to collapse
Thank you very much for taking the time to report back, portachking! I really appreciate it!
Hey guys, i am also new to rooting and have read a lot about it already. I already managed to unlock the bootloader and use twrp to make a full backup. Only from thus point on, i dont know how to actually root it without flashing a custom rom.
Bump
snakegpeo said:
Hey guys, i am also new to rooting and have read a lot about it already. I already managed to unlock the bootloader and use twrp to make a full backup. Only from thus point on, i dont know how to actually root it without flashing a custom rom.
Click to expand...
Click to collapse
2nd Link in the top post describes it (with link to SuperSU).
To root, just flash SuperSU 2.67 in TWRP.
Thanks for the reply. Then i must have missed something. I will try it out this weekend.
It didnt work.
I did everything exactly as described. I have twrp, open it in fastboot with cmd. When i am in twrp, i clicked install, and installed the supersu beta zip and busybox zip. Still i dont have root access.
redpoint73 said:
2nd Link in the top post describes it (with link to SuperSU).
To root, just flash SuperSU 2.67 in TWRP.
Click to expand...
Click to collapse
I tried it multiple times, from my internal storage and sd card. I have bootloader unlocked, i use fastboot boot twrp version 2.8.6.0 if i remember correctly (not at home at the moment) and clicked install. Then i made sure i install the zip super su and busybox file from the root of the sd card, and tried internal storage as well. From that screen, it seems it installs correctly, but when i reboot and use a rootchecker app, it says im not rooted.
Can someone please help me? Ive read up on lots of posts and watched youtube vids of twrp rooting to see if i did it correctly.
Thanks in advance
snakegpeo said:
I tried it multiple times, from my internal storage and sd card. I have bootloader unlocked, i use fastboot boot twrp version 2.8.6.0 if i remember correctly (not at home at the moment) and clicked install. Then i made sure i install the zip super su and busybox file from the root of the sd card, and tried internal storage as well. From that screen, it seems it installs correctly, but when i reboot and use a rootchecker app, it says im not rooted.
Click to expand...
Click to collapse
Please confirm what version SuperSU you used.
When flashing SuperSU, it should have given you the option of "systemless root" or "traditional root" (or something along those lines).
If you picked systemless root, it probably won't show up on root checker apps. Seeing as Link2SD is your main reason for root, have you checked that the app works or not?
Looking around and the support seems iffy. I see the thread that shows how to get pay working with android root using systemless SU. But do any of the current ROMs have support for pay on a fresh install? Or will re-flashing systemless SU work with those roms.
Pure nexus
Ah, I am running that and I get the message that it cannot be verified. Are there any steps needed to be taken? I looked through their thread and couldn't find anything other than others asking if it worked as well.
luckysmack said:
Ah, I am running that and I get the message that it cannot be verified. Are there any steps needed to be taken? I looked through their thread and couldn't find anything other than others asking if it worked as well.
Click to expand...
Click to collapse
There's a link to the FAQ in post 2. Then the FAQ has a link to the steps to get Android Pay working. I haven't checked recently but I think you'll have to use an older set of gapps to get it working.
Sent from my Nexus 5X using XDA-Developers mobile app
Hrmm, I followed that and tried clean install as well. Everything seemed to be fine, changed permissions on /su/bin as well. Pay still doesnt allow me to add cards.
Something had to have changed in the past two weeks or so. I can't get Android Pay working on any ROMs any more. I follow the same steps as before but nothing. Hopefully with AP being released in the UK someone can figure out a work around.
Pure nexus plus Elemental kernel works fine
Sent from my Nexus 5X using Tapatalk
Android pay should work if you are using SU 2.71 or 2.72. I tried this on a different device as well. Works on stock rooted, and elemental kernel;as mentioned above.
its on 2.74 now; cannot confirm or deny working with it.
forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Best Regards
Broken
This method does not work due to complications from SELinux and dm-verity. Sorry guys, looks like the Note 4 can't be rooted at this time :/
Feeling generous? PM me an Amazon gift card!
DISCLAIMER:
Code:
Your warranty is now void. I nor XDA is responsible for the effects this may have on your device or your life, whether that be bricking, loss of data, combustion, nuclear war, or the election of businessmen as President (wait what).
Remember, its not root that puts your device in danger, its how you use it.
If you don't know what a locked bootloader is, or think that Chainfire is a new video game, you shouldn't be here, go read a little about Android and the Galaxy Note 4 before continuing
So let's begin:
What You'll Need:
This *experimental* firmware: https://www.androidfilehost.com/?fid=457095661767141025
Kingroot, SuperSume, and FlashFire, all available from this zip: https://www.androidfilehost.com/?fid=673368273298935732
This modified "from-noship" pre-rooted OC6: https://www.androidfilehost.com/?fid=529152257862707318
What To Do:
Step 1: Goin' Wayy Down
Use ODIN to flash the experimental firmware.
MASTER CAUTION: This will wipe ALL data on the device!! Backup your stuff before proceeding. I nor XDA is responsible for loss of your memes!
Simply flash the .TAR.MD5 file in the zip using the AP slot in ODIN, and then wait for the phone to boot (which is literally all of 10 seconds).
Step 2: Our Old Friend
After the OS is installed, go to the file manager and install Flashfire, Kingroot, and SuperSume
Open Kingroot and use it to root, the in-app instructions will guide you through.
After you've gotten root with KingRoot, open SuperSume, grant it root, and press the big blue button, let it do its thing.
When its done, SuperSU will open and ask you to update the binaries, hit continue, then hit "normal". When its done hit "OK", don't reboot (you don't need to).
At this point you've got root! Now, let's get back to the present!
Step 3: Back to the Future!
Open FlashFire, grant it root access, and flash the modified OC6 with these settings:
Mount /system read/write
A wipe isn't required, but it is recommended (if you do wipe, make sure to put that card B E F O R E the flash zip/ota card!)
Hit "flash", let it flash, reboot, and load.
Disclaimer: I have not personally tested this firmware before release, but it should work. However, I make no guarantees!
Guess what? You're done!
I worked to get your phone rooted, I hope now you guys can get some ROMs going!
OC6 Rollback Files
Something go horribly wrong? Get yourself back on something stable
G900AUCU2COC6: https://www.androidfilehost.com/?fid=745425885120712191
Thanks @xdanilva for the firmware
Reserved
Also Reserved
Reserved
One more :3
Does this root work for 6.0.1 PK1? Or do I need to b on 5.1.1 ?
Also I'm tempted to try but it's a definite wait for my because I've had this phone since it came out an I was just at AT&T last night to trade an upgrade. I'm going back next week an upgrading to iPhone 7+ 128gb because there is no Notes devices and I really don't want Galaxy S7 when in a month or 2 the S8 is coming.
Thanks
Sent from my SAMSUNG-SM-N910A using Tapatalk
nemopsp said:
Does this root work for 6.0.1 PK1? Or do I need to b on 5.1.1 ?
Also I'm tempted to try but it's a definite wait for my because I've had this phone since it came out an I was just at AT&T last night to trade an upgrade. I'm going back next week an upgrading to iPhone 7+ 128gb because there is no Notes devices and I really don't want Galaxy S7 when in a month or 2 the S8 is coming.
Thanks
Sent from my SAMSUNG-SM-N910A using Tapatalk
Click to expand...
Click to collapse
The root is universal. No matter what firmware you are on, you still have to flash the experimental firmware with ODIN. That's what's so beautiful about it
Also, please try not to quote the entire OP, it clutters up the thread
-I personally would have gone with a OnePlus 3T, same if not better specs as the iPhone 7+ and at half the price-
AptLogic said:
-I personally would have gone with a OnePlus 3T, same if not better specs as the iPhone 7+ and at half the price-
Click to expand...
Click to collapse
Yea I agree with you but don't have $400 to put down on a phone. A buddy of mine has OnePlus3 got it on release. But personally I don't have to money to buy a phone every couple months. I normally wait like every 2 an half years. iPhone 7 isn't my favorite choice but I do miss iMessage and iPhone seems there always a new jailbreak coming out might have to wait 6 months but I've waited over 2 years for a root on this phone.
Thanks for releasing this root! I'll b checking the forums an see how this is going!
Sent from my SAMSUNG-SM-N910A using Tapatalk
Just a little PSA: If the towelroot I uploaded does not work PLEASE TELL ME because that means I need to upload the newer version and put the use of modstrings in the OP.
Thanks
anyone root successful on 6.0.1 ?
I'm going to give this a go as soon as I get ahold of a PC. I'm excited to see you prove me wrong.
Awesome this looks very promising!
If I use this, what Android version will I end up on?
jboucher614 said:
Awesome this looks very promising!
If I use this, what Android version will I end up on?
Click to expand...
Click to collapse
If you go through the whole guide you should end up on Android 5.0.1
AptLogic said:
If you go through the whole guide you should end up on Android 5.0.1
Click to expand...
Click to collapse
That's pretty good, is there going to be any way to get to Marshmallow rooted?
jboucher614 said:
That's pretty good, is there going to be any way to get to Marshmallow rooted?
Click to expand...
Click to collapse
No, we can't do that because the locked bootloader won't allow a systemless root, which would be necessary for rooting marshmallow. We can, however, make UNrooted marshmallow ROMs.
Hi !
Thank's For This, I Have Tried This Experimental Rom Before, And It's Worked Fine Without Any Problems (We Can Also Back To The Officiel Firmware With Odin), But I Never Tried To Root.
So, I Need To Know If We Could Install An Other Custom Rom ?
Samy_Wutlol said:
Hi !
Thank's For This, I Have Tried This Experimental Rom Before, And It's Worked Fine Without Any Problems (We Can Also Back To The Officiel Firmware With Odin), But I Never Tried To Root.
So, I Need To Know If We Could Install An Other Custom Rom ?
Click to expand...
Click to collapse
We can install custom TouchWiz ROMs, but you would need to install the pre-rooted OC6 in the OP first (if you want to use 5.0). Unfortunately we still can't get AOSP ROMs working because that would need a new Kernel and the locked bootloader doesn't allow it.
Post #2 has been updated with ODIN recovery files.
Nice work!
I seem to be a little lost here, but can we use/make rooted MM ROMs after doing the steps in OP?
boofman said:
Nice work!
I seem to be a little lost here, but can we use/make rooted MM ROMs after doing the steps in OP?
Click to expand...
Click to collapse
No we can't. No rooted MM ROMs, but you can make rooted LP ROMs
AptLogic said:
No we can't. No rooted MM ROMs, but you can make rooted LP ROMs
Click to expand...
Click to collapse
I'm gonna have to do a lot of reading about this first. Thanks for your great work!
boofman said:
I'm gonna have to do a lot of reading about this first. Thanks for your great work!
Click to expand...
Click to collapse
Feel free to take a look at the Galaxy s5 forums, we're in the same boat
Also I may have made a mistake in the OP. I'd like you guys to hold off on trying it until I fix it. Thanks!
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.
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.