Related
It seems that few ever talk about the ZE500CL variant of the zenfone 2. I've read a whole lot of posts on rooting, unlocking the bootloader, and installing TWRP, but most do not even mention this variant.
I started this thread to collect some information about this device. I would like to know from those who have this device, what has worked for you so far, and what hasn't? I'm especially interested in finding out the 3 things mentioned above.
I've only recently bought the device, and I only rooted it (though I did first get one bootloop already). The method that worked for me is described in this thread: http://forum.xda-developers.com/zenfone2/general/root-ze500cl-z00d-t3116531
The OP of the thread linked above also said that the second method on this thread: http://forum.xda-developers.com/zenfone2/general/root-newbie-root-instructions-zenfone-2-t3114063 works as well.
Btw, make sure the drivers are installed, else the computer won't be able to recognize the device when it is in bootloader mode.
Installing Xposed works as well using the ADB method mentioned in the thread linked below:
http://forum.xda-developers.com/zenfone2/general/guide-to-install-xposed-installer-t3116476
I can add any info you find to the device index in the general section for the 500CL.
Djalaal said:
I've only recently bought the device, and I only rooted it (though I did first get one bootloop already). The method that worked for me is described in this thread: http://forum.xda-developers.com/zenfone2/general/root-ze500cl-z00d-t3116531
The OP of the thread linked above also said that the second method on this thread: http://forum.xda-developers.com/zenfone2/general/root-newbie-root-instructions-zenfone-2-t3114063 works as well.
Btw, make sure the drivers are installed, else the computer won't be able to recognize the device when it is in bootloader mode.
Click to expand...
Click to collapse
How did you fix/handle the bootloop?
Do you know if it is possible to update the phone after rooting it?
cmendonc2 said:
I can add any info you find to the device index in the general section for the 500CL.
Click to expand...
Click to collapse
Sure, that post is much more likely to be noticed than this one. Although I might not find out much. I'm a lot less daring without custom recovery. Hence this thread.
crisbal said:
How did you fix/handle the bootloop?
Do you know if it is possible to update the phone after rooting it?
Click to expand...
Click to collapse
Well, seeing that I do not have a custom recovery (bootloader is still locked), I had to do it the hard way, reflash stock rom. Good news is, apparently your userdata (installed apps+settings and internal memory) is not wiped in the process.
First, you gotta download the rom. Get it from http://forum.xda-developers.com/zenfone2/general/index-asus-zenfone-2-wip-t3149748. Although I got mine here: http://www.asus-zenfone.com/2015/03/asus-zenfone-2-stock-rom-ze500cl-ze550ml-ze551ml.html, which is the old version.
Second, go into recovery mode (from bootloader mode), and use adb sideload ("apply update from ADB") to flash the .zip downloaded before. This is described under "Flashing Zenfone 2 via ADB" on this thread: http://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596
Btw, the bootloop was caused by a mistake I made, not the rooting process.
any news update in our bootloader? hope someone could work for that..
How to get rid off couldn't add widget?
crisbal said:
Do you know if it is possible to update the phone after rooting it?
Click to expand...
Click to collapse
After more than a week of feeling unsure to update mine to WW_12.16.5.118, updating it today after finish uninstalling SuperSU. This is what I have done.
1 - uninstall SuperSU from SuperSU setting - reboot.
2 - update firmware.
3 - re-root using Temporary_CWM method as describe here
Chinaphonearena said:
Method 2: Root through temporary CWM
This is a temporary CWM with the primary purpose of injecting SuperSU onto your Asus Zenfone 2. It doesn't permanently replace recovery. This process looks long, but really is bam 1,2,3 done. Just laid out step by step for the newbie.
link removed due to post count limitation
Unzip the package
Copy SuperSU.zip to the base of your SD card
Enable USB debugging (Settings > Phone info > Tap build 7x > Back button > Developer options > USB debugging)
If you don't already have ADB drivers installed, you may need to [post count restriction] and install them (most PCs have them already, but trying installing these if you're having trouble getting your PC to issue commands to the phone via USB)
With your phone on, attach it to PC via USB
Run 'cai_dat_CWM.bat' from the CWM package
In the black command window that opens, type ACCEPT
Type T4
Phone will reboot into fastboot and you'll see commands being issued from the PC cmd window copying the temporary recovery
You may see some funked up images on your display for a bit. Remove the USB cable and within 30 seconds should then see it booted into CWM
Select install update
Navigate to SuperSU.zip and install
Bam, done.
Click to expand...
Click to collapse
4 - Success!!! now my phone are rooted and all rooted apps installed previously are working.
Note: Previously (before updating FOTA) I also root my ZE500CL using Temporary_CWM since One Click root method aren't working for me.
Recover from bootfreeze while fully stock
Well, after getting a bootfreeze being on a fully (old version) stock ze500cl (Z00D), I figured out something useful. How to recover from a bootfreeze with locked bootloader, non rooted stock rom, without loosing what was saved on your internal storage.
Given that you have not messed with system files (since you aren't rooted), I'm assuming you got either corrupted userdata files or your internal storage is so full, the phone fails to even boot. I had the latter. If system files are the problem, this method might (or probably?) not work. The trick is to use tethered TWRP for backing up your internal storage.
1: Download CWM_Zenfone_2_Intel.zip here: https://www.mediafire.com/folder/w70w7r1a65840/Zenfone_2 (gotten from source 1)
2: Download Recovery.zip here: https://drive.google.com/folderview...T0xRMVRkcTg3MHdlc1o0cVFBc3RPeTQ&usp=drive_web (gotten from source 2)
3: Extract the zip from Step 1.
4: Go to the FB_RecoveryLauncher folder you have extracted, and replace the recovery.zip there with the one downloaded in Step 2.
5: Boot into your stock recovery and connect your phone to the computer. Make sure you have adb and the phone's drivers installed (gotten from source 3).
6. Run the cai_dat_CWM.bat script and you should boot into temporary TWRP recovery after a minute or so.
7. Use TWRP to copy your sdcard folder (internal storage) into your ext_sdcard folder (external storage/microsd) for the sake of backing it up.
8a. In the case of having too full internal storage, simply delete some things in there, and you should be able to boot it again.
8b. Not tested, but in case of corrupted userdata, a factory reset is probably necessary, and will solve the bootfreeze issue.
source 1: http://forum.xda-developers.com/zenfone2/general/root-newbie-root-instructions-zenfone-2-t3114063 (method 2)
source 2: http://forum.xda-developers.com/zenfone2/development/alpha-tethered-twrp-asus-zenfone-2-t3123532
source 3: http://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596
@cmendonc2 , if you want, you can add this to your index.
Djalaal said:
It seems that few ever talk about the ZE500CL variant of the zenfone 2. I've read a whole lot of posts on rooting, unlocking the bootloader, and installing TWRP, but most do not even mention this variant.
I started this thread to collect some information about this device. I would like to know from those who have this device, what has worked for you so far, and what hasn't? I'm especially interested in finding out the 3 things mentioned above.
Click to expand...
Click to collapse
Thank you so much for providing this thread. Found it after hours of scouring the internet in search of help after somehow getting my phone locked in boot-loop. There isn't much support for the ZE500CL, but I will be posting on some blogs while I begin work on mine, and I will reference others to this thread and the few others I've found. Thanks again! :good:
Xanathide said:
Thank you so much for providing this thread. Found it after hours of scouring the internet in search of help after somehow getting my phone locked in boot-loop. There isn't much support for the ZE500CL, but I will be posting on some blogs while I begin work on mine, and I will reference others to this thread and the few others I've found. Thanks again! :good:
Click to expand...
Click to collapse
Sorry, was out of town for 3 months. Glad to be of help. You know where the thanks button is .
I should note that the this phone is now the daily driver of both my parents so I stopped tinkering with it, although I left one of them rooted (and the other not lol). So don't expect more updates from me sadly.
Djalaal said:
Sorry, was out of town for 3 months. Glad to be of help. You know where the thanks button is .
I should note that the this phone is now the daily driver of both my parents so I stopped tinkering with it, although I left one of them rooted (and the other not lol). So don't expect more updates from me sadly.
Click to expand...
Click to collapse
That's quite alright, I've had my fun with Z00D, got myself a LG V10 to break now
I dont ask for directions...
This is my first time asking questions as I have always been able to reverse-engineer (R-E) or as the hacker in swordfish would say "the code just comes to me". Ive been around computers since my dad took me to work at UT and commands were issued with punch out cards....I've been a long time android self taught enthusiast turned professional. ITT Alum etc. I research, I surf, I R-E, and I try every possible option etc...only this has me stumped. And this is the first android that has stumped me. I double checked everything but I keep getting this error in BBQLinux: I followed all pre-update instructions to the T.
fw: ATT_12.16.10.92
adb sideload
This package is not for ATT (WW)
E: Error in /sideload/package.zip
(Status 7)
yes I did with root cmd line, yes cd to zip file location, yes I verified correct fw, even tried different fw zips ZE500CL downloaded officially and from here.
I greatly appreciate any help and I do apologize for "asking for directions"
Computer John dba Austin Computer Techs
cuervo233 said:
This is my first time asking questions as I have always been able to reverse-engineer (R-E) or as the hacker in swordfish would say "the code just comes to me". Ive been around computers since my dad took me to work at UT and commands were issued with punch out cards....I've been a long time android self taught enthusiast turned professional. ITT Alum etc. I research, I surf, I R-E, and I try every possible option etc...only this has me stumped. And this is the first android that has stumped me. I double checked everything but I keep getting this error in BBQLinux: I followed all pre-update instructions to the T.
fw: ATT_12.16.10.92
adb sideload
This package is not for ATT (WW)
E: Error in /sideload/package.zip
(Status 7)
yes I did with root cmd line, yes cd to zip file location, yes I verified correct fw, even tried different fw zips ZE500CL downloaded officially and from here.
I greatly appreciate any help and I do apologize for "asking for directions"
Computer John dba Austin Computer Techs
Click to expand...
Click to collapse
?? Is that att ota youre trying to sideload? Att doesn't have fw, ze500cl does. But just unlock your bootloader, flash twrp, then install whatever, cm, aicp, custom stock or straight stock. http://forum.xda-developers.com/showthread.php?p=64991762
Sent from my MotoG3 using Tapatalk
Cool, I didn't read anywhere about unlocking BL first otherwise Ida made that "turn at the first light". We will ULO thru Asus and continue on our journey. These little Asus trinkets are little buggers being Intel based. Only line of Android devices that have ever stumped me. I am much obliged, fellow XDA brethren. Much obliged.
After pondering a little I came to this conclusion:
UL BL is basically the first step one should take when doing any kind of flashing of internal partitions be it a boot.img, recovery.img, FW etc... at least for the higher end devices. I don't recall having to do that for my sm-n900t recently. Does it only apply for flashing back to stock and not custom roms? Although I didn't have to UL BL first when I heim-dall/Odin flashed my note3 back to stock rom after being boot-looped. Cause once I did that I was able to try out a majority of custom roms available for it whether flashed thru HD/fastboot, Odin, via twrp update zip, or adb sideload. Hmmm, I might understand once I think it thru and look at all the different variables.
Good day gentlemen.
Be vewy vewy quiet, I'm hunting androids...
:good:
@cuervo233 Yes most devices you have to unlock the bootloader first. But there are some devices that already come unlocked. And then there are even some that have bootloaders that cannot be unlocked due to carrier restrictions. In order to get custom recovery to boot you must unlock the bootloader or it must come unlocked. With a custom recovery you can Flash the stock zip file from the Asus website or a custom ROM have fun
Sent from my MotoG3 using Tapatalk
Thank you. I was able to ULBL, flash TWRP, flash to ww 118, root, and now its time to explore the neat wonderful world of custom ROMs. This was by far the hardest yet. Next in line is the cricket Stylo which was also giving me hell, but now I dont think I should have any problem getting it done. I'll keep ya'll posted.:good:
Lg stylo should have way more development, have fun brother. Remember tmobile phones( cricket, walmart family mobile, and metro pcs) you can easily unlock the bootloader . att on the other hand usually has locked down bl.
Sent from my MotoG3 using Tapatalk
I know this is not the right place to ask. I need to know. Do we have developers working on root for this model?
Sent from my SAMSUNG-SM-N920A using Tapatalk
Yes and No...still having booloader issues!
And yes wrong place...this post belongs in Q&A!
We need firmware release so we can restore after. Tell then no one really wants to try because just messing with options in recovery disables the phone.
http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=N920
Will firmware release happen for our model?
Sent from my SAMSUNG-SM-N920A using Tapatalk
amwbt said:
Will firmware release happen for our model?
Sent from my SAMSUNG-SM-N920A using Tapatalk
Click to expand...
Click to collapse
AT&T has to because it's open source. They however can keep it for like 6 months to a year or something. With the cracks down on root AT&T and Verizon it might be a long wait with the locked bootloader saidly and we need a custom kernel to get root and we can't flash kernels with locked bootloader. Just watch the website I linked and when we get our firmware then we can possibly expect root and someone to try and unlock the bootloader. I'm not sure if there is a "anti root" in the AT&T phone because I'm not going to lose my phone. I already had to return for warranty due to defective screen and spen. Look at how long it takes the new iPhone software to get jailbroken.
TechNyne66 said:
AT&T has to because it's open source. They however can keep it for like 6 months to a year or something. With the cracks down on root AT&T and Verizon it might be a long wait with the locked bootloader saidly and we need a custom kernel to get root and we can't flash kernels with locked bootloader. Just watch the website I linked and when we get our firmware then we can possibly expect root and someone to try and unlock the bootloader. I'm not sure if there is a "anti root" in the AT&T phone because I'm not going to lose my phone. I already had to return for warranty due to defective screen and spen. Look at how long it takes the new iPhone software to get jailbroken.
Click to expand...
Click to collapse
Needing a custom kernel for root is actually a false statement. A custom kernel is not needed to get root for this device. The AT&T S6 for example got root without the bootloader being unlocked or a custom kernel.
Which leads me to the bootloader being unlocked. There is probably a 100% chance that we don't get an unlocked bootloader for this device. It's extremely difficult and there hasn't been an AT&T device in a very long time that has had it unlocked.
And since we would need that for a custom kernel and aosp roms, those things will probably never happen unfortunately.
The very best we can hope for is root and a recovery like FlashFire like the S6 got. And even then we would be limited to only Touchwiz roms.
We will more then likely need custom kernel with permissive set. AT&T and Verizon are saying there's anti root and that would be in the kernel and would need to be killed. If we do obtain root with stock kernel the phone is said to not boot.
http://www.idigitaltimes.com/samsun...d-features-att-and-verizon-models-wont-468357
It is one of those things where they're will be zero development until some Uber-geek cracks the bootloader issue. Then there will be 20 devices or more that will be released from developer quarantine...
Sent from my SAMSUNG-SM-N920A using Tapatalk
AOSP will never happen without unlocked bootloader.
I do have hope for a root such as Ping Pong. Honestly, with how clean these phones ship nowadays, all I want root for is to replace emojis with iOS style throughout the system so I can grasp more context from my text messages lol. Also, LCD Density change would be nice too.
Is there anybody working on root for this phone?
Sent from my SAMSUNG-SM-N920A
Have no need for root either except for xposed. Only want root for like 4 xposed modules.. Otherwise this device is nearly perfect
I need to change muy dpis
Enviado desde mi GT-N7100 usando Tapatalk 2
Planning on getting this phone today..
I have rooted and installed ROMs on almost every phone I have owned and really hope that eventually a safe way of rooting is obtained.
jellybear456 said:
a safe way of rooting
Click to expand...
Click to collapse
heh. I know what you mean, but I'm grumpy this morning so I'm going to pick this apart anyway.
If root is found on a boot loader locked device, it's usually via an exploit... Basically, most rooting mechanisms are similar to computer viruses. Sure, most of them are controlled viruses, but they exploit and expose security holes that something malicious could use just as easily. Instead of copying a "su" binary, that same exploit could install something that uploads your private data somewhere, or monitors the android keypad entry when you type credit card numbers, etc.
Don't get me wrong... I don't think that most of the root exploits here on XDA are doing that... but any time you use one, you should seriously consider that it might be. It would only take a single mishap to completely destroy your life outside of XDA.
To that end, you should REALLY pay attention to the entire filesystem both before and after an exploit is applied. See what files, if any, are modified and/or added. If an exploit adds a "su" binary (which most of them do), try to replace that "su" binary with one from a trusted source BEFORE you put personal data on your phone. Never "root" a device that has any data on it.
Remember that no matter what precautions you might be taking, a rooted device has a lower level of security than one that isn't. Not only have you added a "simple" root mechanism, but you likely had to defeat the security mechanisms that are part of the security enhanced linux kernel. (There are exceptions to this, of course, but I've never seen the exceptions here on XDA or any other sites that aren't focused on security.)
If this message made you a bit more paranoid, that's a good thing. You should be paranoid about it. I'm not saying not to do it, and I'm certainly not saying that XDA is overflowing with malicious code...
garyd9 said:
heh. I know what you mean, but I'm grumpy this morning so I'm going to pick this apart anyway.
If root is found on a boot loader locked device, it's usually via an exploit... Basically, most rooting mechanisms are similar to computer viruses. Sure, most of them are controlled viruses, but they exploit and expose security holes that something malicious could use just as easily. Instead of copying a "su" binary, that same exploit could install something that uploads your private data somewhere, or monitors the android keypad entry when you type credit card numbers, etc.
Don't get me wrong... I don't think that most of the root exploits here on XDA are doing that... but any time you use one, you should seriously consider that it might be. It would only take a single mishap to completely destroy your life outside of XDA.
To that end, you should REALLY pay attention to the entire filesystem both before and after an exploit is applied. See what files, if any, are modified and/or added. If an exploit adds a "su" binary (which most of them do), try to replace that "su" binary with one from a trusted source BEFORE you put personal data on your phone. Never "root" a device that has any data on it.
Remember that no matter what precautions you might be taking, a rooted device has a lower level of security than one that isn't. Not only have you added a "simple" root mechanism, but you likely had to defeat the security mechanisms that are part of the security enhanced linux kernel. (There are exceptions to this, of course, but I've never seen the exceptions here on XDA or any other sites that aren't focused on security.)
If this message made you a bit more paranoid, that's a good thing. You should be paranoid about it. I'm not saying not to do it, and I'm certainly not saying that XDA is overflowing with malicious code...
Click to expand...
Click to collapse
Yes, I do realize that rooting a device often does take advantage of any security holes found, and I also realize that there is no, in the literal sense, "safe" way to root a phone considering it is exploiting security flaws. Personally, I have never had such an issue of having something malicious on my phone after rooting(at least not to my knowledge)
By "safe" I meant a way to root without having the phone locked down and unable to boot. I am not worried about AOSP ROMs as I am completely content with using an AOSP themed launcher. But I would love to be able to uninstall bloat, ad block, greenify/amplify etc.
But I do appreciate your input on the subject as I have never put much thought into the security of the phone before and after root, or replacing the su binary with one from a trusted source or checking if it is from a trusted source.
It is also great to see someone else on the forums from Pittsburgh:highfive:
I have n920a. Please share the path to rooting this phone.
Cuando se podra rootear el dispositivo Samsung Galaxy Note 5 N920A?
Possible way to root?
I don't know if this would work. But what about flashing one of those new root.tar eng kernal then manually pushing the survey binary and super apk into phone then reflash stock kernal. I'm just intermediate at all this stuff. So idk if it would work or if this is stupid.
vahalaru said:
I don't know if this would work. But what about flashing one of those new root.tar eng kernal then manually pushing the survey binary and super apk into phone then reflash stock kernal. I'm just intermediate at all this stuff. So idk if it would work or if this is stupid.
Click to expand...
Click to collapse
It's possible, after flashing the eng-boot do this:
adb shell mount -o rw,remount /system
Then manually push SuperSU to system, or install King/Kingo Root
Just be careful this is still a tethered root.
I have posted a teathered root process that Michael31 found from the AT&T s6 section. It works and you can get reboots with hoot booting. The locked bootloader causing issues with the kernel needed add commands on hard boot to change to permissive mode. Few of us have tried to fix this issue and haven't found anyway yet.
I haven't took the plunge to 6.0 yet because I'm not ready to part with root yet but what if we were to modify the system.img and re-flash it? I mean similar to injecting root, but don't inject root. We could at least bock ads with a hosts file, push the file to enable tethering, and debloat. Once done, none of those things require root other then to maybe update the hosts file. Anyone that has updated willing to try? I can help by getting files and commands together. Anyway, just thinking out loud here, thanks for reading lol
The problem is with 6.0, Google made changes so that the only way to achieve root is to modify the boot image instead of the System image. Since the VS986 has a locked bootloader, the phone will refuse to boot if you modify it from stock, potentially bricking it.
6.0 + locked bootloader = no root.
As I said above, I'm not wanting to push root to the image, I realize it's blocked now. What I'm proposing is to modify the image to achieve 2 main things, ad blocking and tethering. If we push the 2 files needed for that, then flash the image, root will not be needed for those to continue to work. It won't work if the system is somehow checked for modifications, but kdz should fix that if it don't work.. Anyone willing to try it?
I can't help you with root but Verizon is no longer charging for tethering on most of their plans. I use it all the time on my G4 using stock tethering. Double check with Verizon.
People who still have unlimited data don't have tethering included so we need the modified hotspot. And like I already said, I'm not looking to have root, what I'm wanting to try is a little different. I haven't taken the plunge to 6.0 yet, but I'm looking for someone who has but kinda regrets out cuz they lost root.
jweber228 said:
I haven't took the plunge to 6.0 yet because I'm not ready to part with root yet but what if we were to modify the system.img and re-flash it? I mean similar to injecting root, but don't inject root. We could at least bock ads with a hosts file, push the file to enable tethering, and debloat. Once done, none of those things require root other then to maybe update the hosts file. Anyone that has updated willing to try? I can help by getting files and commands together. Anyway, just thinking out loud here, thanks for reading lol
Click to expand...
Click to collapse
That is exactly what i would like to do. A little debloating, updating hosts and add cerberus as a system app.
this is a step in the right direction : http://forum.xda-developers.com/g4/general/guide-how-to-modify-img-partition-t3196994
This has been asked a few times in the "Root Injection" thread, once by me, with no answer.
It appears the main problem is the download mode exploit may be closed. Entering commands in the send-command app returns "fail".
I once got the command to backup entered without failing but it ran for almost an hour without generating the system.img.
I guess we have to use a fully fledged kitchen. I was hoping to circumvent that
Gesendet von meinem LG-H815 mit Tapatalk
fr4nk1yn said:
This has been asked a few times in the "Root Injection" thread, once by me, with no answer.
It appears the main problem is the download mode exploit may be closed. Entering commands in the send-command app returns "fail".
I once got the command to backup entered without failing but it ran for almost an hour without generating the system.img.
Click to expand...
Click to collapse
In addition that exploit getting patched, Android 6.0 was changed by Google so that you can only achieve root by modifying the boot.img and kernel, not just the system partition. Since the bootloader is locked, if you do manage to modify the system img, you would at best see no results, or at worst brick your phone.
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.