Related
Guys here's the thing. Android N on my N5X. When trying to install TWRP 3.0.2.2 through Nexus Root Toolkit it first boots up the recovery then when I reboot to system and back there is no TWRP. But it remains there when I use the Root button which roots and installs custom recovery. So when I have root I have TWRP. Can't I have TWRP without root I wonder?
Suren Manukyan said:
Guys here's the thing. Android N on my N5X. When trying to install TWRP 3.0.2.2 through Nexus Root Toolkit it first boots up the recovery then when I reboot to system and back there is no TWRP. But it remains there when I use the Root button which roots and installs custom recovery. So when I have root I have TWRP. Can't I have TWRP without root I wonder?
Click to expand...
Click to collapse
Doesnt the toolkit have a check box to install a script or whatever to patch the system so the recovery wont be over written? Mine has it in flash recovery option!
I'm experiencing this issue as well. I tried to install TWRP after installing that October security updates. I wonder if there's something in the update that is preventing TWRP from installing?
hilla_killa said:
Doesnt the toolkit have a check box to install a script or whatever to patch the system so the recovery wont be over written? Mine has it in flash recovery option!
Click to expand...
Click to collapse
It has something called perm.flash.recovery.zipor something which is described to do the thing you said but the problem is when the phone gets the" flash perm.flash.recovery.zip" it does nothing. It does nothing even when I try to flash it manually when I get the "trial" TWRP which disappears after rebooting.
Had the same problem. I solved it by using the old fashioned way, with fastboot commands found on the TWRP page: https://twrp.me/devices/lgnexus5x.html
Of course, I used the last image: twrp-3.0.2-2-bullhead.img
Hi all,
after I had a full crash while I was trying to update 4.0.0 -> 4.0.1 I now installed all from the scratch.
I now try to get root for it. I installed TWRP (twrp-3.0.2-1.28-oneplus3.img) ... opening it it asks me to bring in a PIN. every PIN I enter is wrong. If I choose cancel I am in. But System is accessable.
Anybody can post a real HowTo for getting root (SuperSU) in OxygenOS 4.0.1
Thanks in advance
After you flash the rom, flash SuperSU immediately. Then reboot to recovery, NOT to system.
If the phone stuck, force reboot by pressing power& vol.- . Reflash recovery, reboot to recovery, reboot to system.
Adb Sideload SuperSu via TWRP
Harish_Kumar said:
Adb Sideload SuperSu via TWRP
Click to expand...
Click to collapse
This worked for me!
@all: does anybody have the Stock Recovery .img for "OxygenOS 4.0.1"?
I always get this "the dm-verfiy ..." message. And after booting I have to type in the unlock PIN ... booting again ... ready to use. I think is is because TWRP
How did you do?
Skickat från min ONEPLUS A3003 via Tapatalk
null0seven said:
After you flash the rom, flash SuperSU immediately. Then reboot to recovery, NOT to system.
If the phone stuck, force reboot by pressing power& vol.- . Reflash recovery, reboot to recovery, reboot to system.
Click to expand...
Click to collapse
can you explain me what the purpose of rebooting into recovery after flashing supersu and not to system?
On some roms, you have to instal SuperSu, before first boot. Or you will not have root.
Some rooms will mess up recovery if youre first boot it's in system & not to recovery. You reboot, to recovery, first, to be shure that you have a working recovery.
This is how I did: upgraded to OOS 4.0.1, flashed the latest TWRP (3.0.3-0), copy & paste SuperSU to internal storage then flashed it through TWRP. Everything works fine.
Now I'm trying to figure out how to decrypt this phone because OOS 4.0.1 converts the Data partition file system to F2FS. I'm a heavy user of MultiROM, that's the reason for decrypting.
I updated TWRP in TWRP via zip flashing and now whenever I try to reboot my phone, it only boots back into TWRP.
Previously, I was unlocked bootloader and rooted on stock.
Would appreciate any help. Thanks
I've never installed TWRP on this phone, but here is one thread Google returns that seems to be similar.
https://forum.xda-developers.com/pixel-xl/how-to/twrp-bootloop-flashing-twrp-t3533765
One relevant thing that has changed since the time of that discussion is that the May and newer bootloaders require a signed boot image. When I installed the May update with SuperSU without signing the boot image my phone simply ended up switching to the other slot, but again I didn't have TWRP installed. There is a zip for signing the boot image and further discussion here.
https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
Thanks for the response. Looks like I have to flash factory image and then the verified boot signer. I'll give it a shot and report back.
Fixed this rather easily using the June factory images. Flashed using flash-all.bat (and removed the -w) and things are updated and back to square one. Interestingly, I didn't need to sign the boot image.
Thanks for the help.
facted;72562818 Interestingly said:
You don't need to sign unless you root or flash a custom kernel that isnt signed.
Click to expand...
Click to collapse
TonikJDK said:
facted;72562818 Interestingly said:
You don't need to sign unless you root or flash a custom kernel that isnt signed.
Click to expand...
Click to collapse
Do you need to use the signed boot image file if you are flashing an unrooted custom Rom? I thought you needed to use it when flashing anything that changed the boot image from stock, including flashing TWRP if it's going to be installed on the phone.
Actually now that I thought about it the signed boot image is SuperSu specific, isn't it?
Click to expand...
Click to collapse
My understanding is that at the last step before restarting the phone the boot image needs to be signed, if the bootloader has been updated to May or later. The stock image is signed, and I've read that ElementalX will also sign the boot image. If you install anything else at this time, such as TWRP or SuperSU or Magisk, then I think as the last step it's necessary to also sign the image. Now that you've updated the bootloader, my understanding is that you will need to sign the boot image if you install TWRP again.
alluringreality said:
My understanding is that at the last step before restarting the phone the boot image needs to be signed, if the bootloader has been updated to May or later. The stock image is signed, and I've read that ElementalX will also sign the boot image. If you install anything else at this time, such as TWRP or SuperSU or Magisk, then I think as the last step it's necessary to also sign the image. Now that you've updated the bootloader, my understanding is that you will need to sign the boot image if you install TWRP again.
Click to expand...
Click to collapse
yeah i am stock rooted with twrp on june 7.1.2. I had to flash the verifiedbootsigner-v8 when rooting with magisk and twrp. I did NOT have to flash it when flashing elementaX 1.12
We're can I download v8?
Sent from my Pixel XL using Tapatalk
The first post from the following link has the latest version of the Verified Boot Signer attached.
https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
335Deezl said:
We're can I download v8?
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
https://forum.xda-developers.com/pixel-xl/how-to/guide-stock-7-1-2-root-safetynet-ok-t3617347
So, I just ran into this issue with my Pixel 2 XL when I tried to update my TWRP version from 3.2.1-2 to 3.2.3-0. Here's how it went:
1. Downloaded the TWRP zip, md5 and so on from the official TWRP website for the Pixel 2 XL
2. Booted to TWRP and installed / flashed the zip of TWRP 3.2.3-0
3. Wiped dalvik and then chose Reboot to System from TWRP -- the phone booted right back into TWRP
4. Tried again to reboot the same way. Same result.
5. Installed / Flashed the 3.2.1-2 TWRP zip which was still on my phone, in order to revert to the previous version, and then Rebooted to System -- same result
6. Flashed 3.2.3-0 zip again, then flashed the Flash Kernel that I've been using, and then Flashed the Magisk v16.0 zip that I used to root, then chose Reboot to System -- AND IT WORKED; the phone booted normally and now I'm updated to the latest TWRP successfully.
tl;dr - The solution is to flash Magisk again after updating TWRP. Pretty sure this goes for kernel updates too.
cognitivedissonance said:
So, I just ran into this issue with my Pixel 2 XL when I tried to update my TWRP version from 3.2.1-2 to 3.2.3-0. Here's how it went:
1. Downloaded the TWRP zip, md5 and so on from the official TWRP website for the Pixel 2 XL
2. Booted to TWRP and installed / flashed the zip of TWRP 3.2.3-0
3. Wiped dalvik and then chose Reboot to System from TWRP -- the phone booted right back into TWRP
4. Tried again to reboot the same way. Same result.
5. Installed / Flashed the 3.2.1-2 TWRP zip which was still on my phone, in order to revert to the previous version, and then Rebooted to System -- same result
6. Flashed 3.2.3-0 zip again, then flashed the Flash Kernel that I've been using, and then Flashed the Magisk v16.0 zip that I used to root, then chose Reboot to System -- AND IT WORKED; the phone booted normally and now I'm updated to the latest TWRP successfully.
tl;dr - The solution is to flash Magisk again after updating TWRP. Pretty sure this goes for kernel updates too.
Click to expand...
Click to collapse
This is Pixel XL forum.
Slowclap
Phalanx7621 said:
Slowclap
Click to expand...
Click to collapse
Hi!
I'm currently using flash rom and kernel. As I've always done so, I like to flash TWRP and then SuperSU to enjoy the little tweaks offered by root.
Since the last 8.1 update, I'm facing a few issues that in my opinion are correlated.
First, flashing TWRP works well, but it seems not to be systemless, i.e. when I reboot my device the proper way, TWRP disappears.
Secondly, when I try to flash the latest stable SuperSU zip through my working TWRP (it's a one shot...), the process gives me no error, but then on the first boot, I get stuck on the huge Google logo... The only thing I can do is re-flashing boot.img but obviously the SuperSU app didn't install...
What should I do? Install a beta SuperSU version? Try Magisk (honestly, I don't really like it...)
Thanks for your help and patience!
azertguigui said:
Hi!
I'm currently using flash rom and kernel. As I've always done so, I like to flash TWRP and then SuperSU to enjoy the little tweaks offered by root.
Since the last 8.1 update, I'm facing a few issues that in my opinion are correlated.
First, flashing TWRP works well, but it seems not to be systemless, i.e. when I reboot my device the proper way, TWRP disappears.
Secondly, when I try to flash the latest stable SuperSU zip through my working TWRP (it's a one shot...), the process gives me no error, but then on the first boot, I get stuck on the huge Google logo... The only thing I can do is re-flashing boot.img but obviously the SuperSU app didn't install...
What should I do? Install a beta SuperSU version? Try Magisk (honestly, I don't really like it...)
Thanks for your help and patience!
Click to expand...
Click to collapse
Do this, first boot twrp, don't flash it. Once booted flash SU 2.82 SR5. Then boot back into the bootloader from twrp and flash twrp. Works for me.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
Do this, first boot twrp, don't flash it. Once booted flash SU 2.82 SR5. Then boot back into the bootloader from twrp and flash twrp. Works for me.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Huge thanks for this!!! I was having the exact same problem (boot hangs at Google logo) and this resolved it!
I noticed that afterwards in the apps drawer I could not find any SuperSU, but doing adb shell and then invoking su worked, so I then just installed the supersu app from the play store to handle prompts (it seems without the app, root is enabled silently and doesn't seem like that great of an idea).
-----------EDIT------------
After installing the app from play store, DO NOT allow it to update the supersu binaries! I ran into bootloop again after that, and had to re-flash SR5 again. Seems like that's the magical version to use!
You're right about having super su update. I had the same problem.
Edit, I just checked and I'm actually using SR3. SuperSu then updated those binaries without a problem.
Hi, thanks for the answers. What do you guys mean by 'booting twrp without flashing it'? What's the fastboot command?
azertguigui said:
Hi, thanks for the answers. What do you guys mean by 'booting twrp without flashing it'? What's the fastboot command?
Click to expand...
Click to collapse
fastboot boot (drag and drop twrp.img file here)
Sent from my Nexus 5X using Tapatalk
Well for the record, I did the following
Code:
fastboot boot twrp-3.2.1-0-bullhead
Then, I installed SuperSU downloaded here. I went back to fastboot and used
Code:
fastboot flash twrp-3.2.1-0-bullhead
but I still got stuck on the Google logo, meaning that my boot was corrupted or something... I then flashed the original Google boot.img
Code:
fastboot flash boot.img
and re-did the process of flashing SuperSU but I wisely chose to find a SR5 version of the file. I didn't flash TWRP after that and my phone booted normally with supersu.apk installed in it and the root privileges granted ... I don't know if I should try flashing TWRP again since my phone is working fine right now, but thanks anyway for the tip of booting to TWRP and not flashing it directly!
Hi everyone,
I'm going mad about Pixel 2 XL Root. I'm Trying to use Magisk v18 on latest Android versione but I'm not able to root the device.
Everytime I try to flash Magisk the screen stays loading Google Icon in loop forever and ever. I've tried every guide on the web whitout success.
Anyone can help me?
[Edit]
Theese are the steps i take
-flash recovery twrp (ok)
-reboot to recovery (ok)
-flash magisk v18 (loop)
megamarini said:
Hi everyone,
I'm going mad about Pixel 2 XL Root. I'm Trying to use Magisk v18 on latest Android versione but I'm not able to root the device.
Everytime I try to flash Magisk the screen stays loading Google Icon in loop forever and ever. I've tried every guide on the web whitout success.
Anyone can help me?
Click to expand...
Click to collapse
All the usual preemptive steps are complete, correct? You OEM unlocked it and all that?
djcrystals said:
All the usual preemptive steps are complete, correct? You OEM unlocked it and all that?
Click to expand...
Click to collapse
Sure mate, I have rooted every smartphone owned since Xperia X8 and this is a very strange behaviour for me.
megamarini said:
Sure mate, I have rooted every smartphone owned since Xperia X8 and this is a very strange behaviour for me.
Click to expand...
Click to collapse
Don't feel too bad my friend, the P2XL is a quirky little bugger to say the least. I had a heck of a time rooting 9.0 after I updated from 8.1, then outa the blue, it worked. Here's a few steps to try.
1. Fastboot twrp, then flash magisk, try to boot.
2. Fastboot twrp, flash twrp.zip, boot up, then go back to twrp and flash magisk. If no go, do the same steps, except after you flash magisk, flash the magisk uninstaller zip, then flash magisk again.
3. Fastboot into twrp, flash twrp.zip, custom kernel.zip, then magisk.zip. if no go, then try the magisk uninstaller.zip method again.
4. Stick with it, be patient, sooner or latter you'll find the right combo. Also, it seems easier to root using a custom kernel, if your willing to try it :good:
Badger50 said:
Don't feel too bad my friend, the P2XL is a quirky little bugger to say the least. I had a heck of a time rooting 9.0 after I updated from 8.1, then outa the blue, it worked. Here's a few steps to try.
1. Fastboot twrp, then flash magisk, try to boot.
2. Fastboot twrp, flash twrp.zip, boot up, then go back to twrp and flash magisk. If no go, do the same steps, except after you flash magisk, flash the magisk uninstaller zip, then flash magisk again.
3. Fastboot into twrp, flash twrp.zip, custom kernel.zip, then magisk.zip. if no go, then try the magisk uninstaller.zip method again.
4. Stick with it, be patient, sooner or latter you'll find the right combo. Also, it seems easier to root using a custom kernel, if your willing to try it :good:
Click to expand...
Click to collapse
Thank You mate, when I'll get home I'll try to follow yor steps and I'll let you know. Any suggestion about kernel on stock firmware? ElementalX it's ok?
Had the SAME problem yesterday:
Fastbooted TWRP
Flashed TWRP
Flashed Magisk
---> STUCK
Flashed TWRP
Flashed Magisk
---> BOOTED UP
Sui77 said:
Had the SAME problem yesterday:
Fastbooted TWRP
Flashed TWRP
Flashed Magisk
---> STUCK
Flashed TWRP
Flashed Magisk
---> BOOTED UP
Click to expand...
Click to collapse
Tryed everything but nothing works..
megamarini said:
Tryed everything but nothing works..
Click to expand...
Click to collapse
Maybe give the guide linked in my sig a shot.
If that doesn't help, try the following:
-once you've permanently installed TWRP, try rebooting to recovery after each additional step BEFORE rebooting to system:
install cust kernel, reboot to recovery, reboot to system
install magisk, reboot to recovery, reboot to system
if that doesn't work, try doing a mass install after TWRP is permanently installed:
in the same flash, install cust kernel and magisk, reboot to system
These have helped other users who have had odd issues with their set ups, but in the end, Pixel 2 XL is a fickle beast
Best of luck!
Az Biker said:
Maybe give the guide linked in my sig a shot.
If that doesn't help, try the following:
-once you've permanently installed TWRP, try rebooting to recovery after each additional step BEFORE rebooting to system:
install cust kernel, reboot to recovery, reboot to system
install magisk, reboot to recovery, reboot to system
if that doesn't work, try doing a mass install after TWRP is permanently installed:
in the same flash, install cust kernel and magisk, reboot to system
These have helped other users who have had odd issues with their set ups, but in the end, Pixel 2 XL is a fickle beast
Best of luck!
Click to expand...
Click to collapse
SOLVED
The only way (for me) to root my Pixel 2 XL is follow theese steps:
Rooting with Magisk
NOTE #4: This section assumes you are not going to install TWRP. If you are, skip to the next section and just flash the latest Magisk zip after installing TWRP.
Download the Magisk zip from the official thread and install the manager from the zip.
Grab a boot image to patch (either the one from the latest factory image or a custom kernel one) and push it to your device:
Code:
adb push <path_to_file> /sdcard/Download
Open Magisk Manager and click the Install button.
Click "Install" at the first prompt then choose "Patch Boot Image File". A file manager will pop up.
Select the boot image you want to patch and let Magisk Manager patch it.
Pull it off your device:
Code:
adb pull /sdcard/MagiskManager/patched_boot.img
Reboot into the bootloader:
Code:
adb reboot bootloader
Flash the boot image and reboot.
Code:
fastboot flash boot patched_boot.img
fastboot reboot
Open Magisk Manager and you should be rooted!
Source: XDA Post
Thank you so much to everyone who tried to help me!