Hi all,
Have recently gotten a Pixel 2 (walleye). And was hoping to root it and have ViperAudio and Busy Box installed. I had a Magisk root but I could not install Busybox and there where issues installing the ViperAudio, Mainly drivers.
Was hoping there would be a full tutorial on how to root it properly and install VIperAudio and Busy Box?.
Am currently running on the stock November update with the boot loader unlocked.
Cheers
Related
Hi everyboby,
I'm new to the world of rooting and beyond. Just bought a LG G2 F320K (Korean version) a few weeks ago. The phone came with Android 4.2.2 Kitkat. Upgraded to 5.0.1 through OTA (the present software version is F320K30j, Android 5.0.1). I tried to root the phone with one-click method (LG_One_Click_Root_v1.3.msi). The phone was reportedly rooted but SuperSU did not show up automatically. I downloaded the SuperSU from the PlayStore only to find out that there was no su binary installed and SuperSU couldn't install it. I've tried to find out how to install the binary and found out that the only way to do it is to flash a zip file which in turn needs a custom recovery, which in turn needs the phone to be rooted (Isn't that funny!) I've tried manually root the phone by using the LG Root tool with no success (the phone refused to carry out the last command) . Is there anyway to solve this problem? Thank you.
Hello.
I have a Pixel with stock Android that was rooted with Chainfire SuperSU 2.78SR3
Last night I've noticed that the phone isn't rooted anymore and has installed the Feb security update OTA. (I only had the Nov update installed).
I've tried rerooting using the same method (Fastboot boot) and got stuck in a bootloop.
I had to flash a clean stock rom to get it out of the bootloop.
Next I installed TWRP. That worked.
Next I tried installing a ZIP version of SuperSU 2.78SR4. The Zip installs but when I boot into Android SuperSU says that the phone isn't rooted.
Anyone had anything similar happen to them?
Borrisl said:
Hello.
I have a Pixel with stock Android that was rooted with Chainfire SuperSU 2.78SR3
Last night I've noticed that the phone isn't rooted anymore and has installed the Feb security update OTA. (I only had the Nov update installed).
I've tried rerooting using the same method (Fastboot boot) and got stuck in a bootloop.
I had to flash a clean stock rom to get it out of the bootloop.
Next I installed TWRP. That worked.
Next I tried installing a ZIP version of SuperSU 2.78SR4. The Zip installs but when I boot into Android SuperSU says that the phone isn't rooted.
Anyone had anything similar happen to them?
Click to expand...
Click to collapse
You might need to flash back to stock to fix this. If you do let us know so we can help you save your data and apps.
You used the wrong SU. You need 2.79 SR3. Note the 9 on there, you used 2.78.
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Copy it to your phone and boot to TWRP. Then INSTALL it from TWRP.
Hi community, I was wondering now that a second update for Android Q is out for all Pixel Devices is recommended to get it installed on my pixel and also if I will be able to do that as I have already got root permision and installed TWRP following a tutorial... Thanks in advance! PD After I have finished all the steps to get root access I noticied there was a security patch for the Pixel (still Android 9.0) but it did not allow me to install it...
I have a Samsung Galaxy S10e and am attempting to root it. I have followed this tutorial:
I managed to flash the patched image onto my device however in the Magisk Manager it is not showing that I have rooted.
I then flashed TWRP and tried installing the Magisk.zip. There were no errors however my device was still not rooted.
I then tried to Install lineage OS via TWRP however it did not do anything.
I've been trying for 2 weeks and cannot find a solution.
I assumed you installed the Magisk app?
There's two components to Magisk: the patch, and the manager. The app package can be used for both. It can patch the boot image or be flashed in TWRP to "install" root, but this is useless unless the app is actually installed in Android to make use of the root patch.
I have managed to root with pixel experience ROM. Don't know why it wasn't working with Samsung ROM.
Hi folks, I am running a Pixel 6A that I rooted with magisk back in December. I stupidly did not disable OTA updates. Last night the QPR2 update came down and wiped root from my phone.
Bootloader is still unlocked and magisk app is installed.
I am confused about the best way to restore root. I see that the QPR2 beta required the use of the pixel 7 boot image. Does that still hold for the stable QPR2?
Also, the magisk app offers a way to choose and patch an image within the app. Can I get the pixel 7 boot image and patch it in magisk, or do I have to use the ADB/ fastboot method?
Sorry for the trouble. I promise I will disable OTA updates in the future. Thanks for any help.
Hello! I am also root user and if it is true that there was an update with the boot 6a not root and I had to use the pixel 7 or 7 pro (I do not remember which was) but if in doubt I would try only with the 6a just in case, the procedure is to download the full rom of the same version you have now, extract the boot.img, patch it with magisk and flash it by adb from the pc, is the method I use in each update and no problems until today, good luck and greetings!
If you are using Magisk Stable 26.1 or Canary 26101, you can use the Pixel 6a boot image to root as the problems mentioned above have been fixed with these versions of Magisk.
Problem solved. Y'all rock.
I'm having a similar problem. I'm am unable to find the boot.img anywhere in the zip file I'm on Bluejay TQ2A 230305.008E1.
RimWulf said:
I'm having a similar problem. I'm am unable to find the boot.img anywhere in the zip file I'm on Bluejay TQ2A 230305.008E1.
Click to expand...
Click to collapse
Download and open the zip => open "image-bluejay-tq2a.230305.008.e1.zip" => find your boot.img