So I decided to root my phone and put Lineage OS on it today. It has been a while since I did this so I followed this guide https://highonandroid.com/android-smartphones/how-to-root-pixel-2-or-pixel-2-xl-easiest-method/. I did use updated versions of TWRP and Magisk but it won't boot past this screen below.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Any help would be really appreciated guys.
Mikeando89 said:
So I decided to root my phone and put Lineage OS on it today. It has been a while since I did this so I followed this guide https://highonandroid.com/android-smartphones/how-to-root-pixel-2-or-pixel-2-xl-easiest-method/. I did use updated versions of TWRP and Magisk but it won't boot past this screen below.
View attachment 5168879
Any help would be really appreciated guys.
Click to expand...
Click to collapse
Without even knowing what OS version you are on, or whether you are on Stable, Beta or Canary Magisk, or how you installed Magisk, or whether you installed or temporarily booted up TWRP, I'll make a couple of suggestions:
If you are on Android 11, you can't install TWRP and Magisk together. You will have to temporarily boot up TWRP with fastboot to flash Magisk, or alternatively, patch the stock boot image with Magisk and fastboot flash the patched boot image.
Also, Stable Magisk is not compatible with Android 11. You should be using Beta 21.1 (or latest Canary).
I would start there.
Mikeando89 said:
So I decided to root my phone and put Lineage OS on it today. It has been a while since I did this so I followed this guide https://highonandroid.com/android-smartphones/how-to-root-pixel-2-or-pixel-2-xl-easiest-method/. I did use updated versions of TWRP and Magisk but it won't boot past this screen below.
View attachment 5168879
Any help would be really appreciated guys.
Click to expand...
Click to collapse
1) Never use a guide from 3 years ago
2) Heres how i flash most ROMS (aforementioned fastboot TWRP only included. Substitute the ROM zip name for LOS): https://forum.xda-developers.com/t/rom-pixel-2-xl-official-protonaosp-11-3-0.4188109/post-84079085
3) Actually heres the same info (including bonus links to TWRP) on the last page in the LOS thread youre referring to, which begs the question, why are you reading 3 year old guides offsite, and NOT the actual OP and last page or so (to see if theres issues/etc)of the ROM thread of the ROM youre installing? Thats bonkers : https://forum.xda-developers.com/t/...2-2-xl-december-17-2020.4165919/post-84138395
Always a good idea to actually read the OP (and last few pages) of the ROM thread of the ROM youre installing....you wouldnt have needed to ask anyone for help....
Mikeando89 said:
So I decided to root my phone and put Lineage OS on it today. It has been a while since I did this so I followed this guide https://highonandroid.com/android-smartphones/how-to-root-pixel-2-or-pixel-2-xl-easiest-method/. I did use updated versions of TWRP and Magisk but it won't boot past this screen below.
View attachment 5168879
Any help would be really appreciated guys.
Click to expand...
Click to collapse
Reading the step by step guide you linked, don't put your files in the fastboot folder. I suggest you download the platform tools from google and flash the stock google images then start over with the LOS installation.
Thanks for your replies everyone. I understand that I really didn't provide much detail. I have now fixed the problem. I have flashed LOS 18.1, NiKGapps and Magisk 21.1. Only problem I am having now is the finger print works with the lockscreen but not with apps such as PayPal or Enpass.
Related
Hey all,
First time I'm trying to root this device, and a long time since I've rooted any device, so I'm a bit rusty ...
While trying to flash with Odin, I'm getting this error (looks like a write permissions error?)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is what's shown on the device after:
The current firmware on the device is the stock 4.4.2, and I'm using the latest CF Root for it: cfar_samsung_sm-t320_mondrianwifiue_kot49h.t320ues1aqa2_t0
Update:
I also went to updato.com, grabbed my latest firmware, flashed it in Odin (it passed), then re-tried the above: result was the same as above.
Any idea what step I should take next?
TIA
GeekDrop said:
Hey all,
First time I'm trying to root this device, and a long time since I've rooted any device, so I'm a bit rusty ...
While trying to flash with Odin, I'm getting this error (looks like a write permissions error?)
This is what's shown on the device after:
The current firmware on the device is the stock 4.4.2, and I'm using the latest CF Root for it: cfar_samsung_sm-t320_mondrianwifiue_kot49h.t320ues1aqa2_t0
Update:
I also went to updato.com, grabbed my latest firmware, flashed it in Odin (it passed), then re-tried the above: result was the same as above.
Any idea what step I should take next?
TIA
Click to expand...
Click to collapse
It's been so long i can't even remember the steps i took but if i were to do it right now I would probably flash twrp in odin, reboot directly to recovery and flash supersu.
Edit - here's a guide https://forum.xda-developers.com/ga...nstall-twrp-3-1-1-sm-t520-t3693342?styleid=21
Airtioteclint said:
It's been so long i can't even remember the steps i took but if i were to do it right now I would probably flash twrp in odin, reboot directly to recovery and flash supersu.
Edit - here's a guide https://forum.xda-developers.com/ga...nstall-twrp-3-1-1-sm-t520-t3693342?styleid=21
Click to expand...
Click to collapse
Thanks, but you have to root before you can install a custom recovery; I'm stuck at trying to get the chainfire root installed.
I'm still stuck, anyone have any other advice?
[QRCODE][/QRCODE]
GeekDrop said:
Thanks, but you have to root before you can install a custom recovery; I'm stuck at trying to get the chainfire root installed.
I'm still stuck, anyone have any other advice?
Click to expand...
Click to collapse
Nope. I always flash root with custom recovery on every single device I've own which is alot.
If you bothered to follow that guide i included you would see that too. But ok...
Airtioteclint said:
[QRCODE][/QRCODE]If you bothered to follow that guide i included you would see that too. But ok...
Click to expand...
Click to collapse
I did follow the guide ....
Hi, sorry for reviving an old thread but I had this issue last night and wanted to share how I resolved it
I have the same T320UES1AQA2 model but couldn't get the CF autoroot to work either. I ended up going into recovery (Power + Vol Up + Home) wiping data and then flashing CF-Auto-Root-mondrianwifi-mondrianwifixx-smt320.zip which worked perfectly.
I know this is super late but hope it helps and anyone else who stumbles across this
Hi all, i have unlocked the bootloader of my Note 8T and installed the latest TWRP, i was going to install xiaomi.eu ROM, but sadly things has gone "bad", when i try to format, it fails, giving me a lot of red errors lines, ending with Operation not permitted, so i stopped there and flashed back the stock MIUI ROM through Xiaomi Flash Tool. Now since the issues with TWRP, I'm wondering how can i update when i will receive new updates via OTA? I think i wouldn't be able to do that with TWRP since the errors it gives me just formating. You guys think i would be able to update by downloading the fastboot update and flash it through Mi Flash Tool?
MichaelMay said:
You'll recieve new OTA updates, the recovery (TWRP before, stock now) has been replaced completely and TWRP is no longer your recovery.
I know what the initial problem is as well, you need another TWRP and if you had just read the forums you'd already know that and all of this could have been avoided.
Click to expand...
Click to collapse
I'm sorry, but i've used the latest TWRP for Ginkgo/Willow as xiaomi.eu requires. Also i've read of other users trying others recovery and encountering the same issue anyway.
You try this way https://forum.xda-developers.com/t/...ion-errors-all-the-time.4203951/post-84523785
Datlevn said:
You try this way https://forum.xda-developers.com/t/...ion-errors-all-the-time.4203951/post-84523785
Click to expand...
Click to collapse
So flashing this Miui HellasTWR recovery should fix the issue? I can flash it through fastboot, or i have to flash it by the recovery (TWRP in my case) as shown on the video? Thanks for your help.
Me too but still OTA the latest version of miui eu 24-2-2021
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Datlevn said:
View attachment 5233255
Click to expand...
Click to collapse
So you got stuck with xiaomi.eu ROM? If you know any fix let me know!
Mi8T said:
So you got stuck with xiaomi.eu ROM? If you know any fix let me know!
Click to expand...
Click to collapse
I did and ran out of red error line by this flash Miui HellasTWRP recovery -> HellasTWRP will ask for password (lock screen password), data will be decoded and now you can install custom rom according to Conventional way (4 wipe).
Note that updates only via twrp are not available via OTA
Datlevn said:
I did and ran out of red error line by this flash Miui HellasTWRP recovery -> HellasTWRP will ask for password (lock screen password), data will be decoded and now you can install custom rom according to Conventional way (4 wipe).
Note that updates only via twrp are not available via OTA
Click to expand...
Click to collapse
So MIUI HellasTWRP Recovery is the cure for the issue? That's Nice! I'm going to try again then. A little question, did you flash the HellasTWRP through fastboot adb mode? Thanks for letting me know!
Yes, flash by adb mode
hello guys, did anyone rooted android 13 stable build on pixel 6 pro??
please drop in, how you guys made it!! like with magisk or anything...
thanks!
I read from other users that root is possible with last magisk.
Rifle003 said:
hello guys, did anyone rooted android 13 stable build on pixel 6 pro??
please drop in, how you guys made it!! like with magisk or anything...
thanks!
Click to expand...
Click to collapse
Yes, Magisk works fine on A13.
Just make sure you boot the patched boot.img file and direct install. To avoid possible issues
@Rifle003 Welcome to XDA! You can also click the yellow How To Guide quick filter located at the top of the list of threads in this section, and you'll find several helpful threads about rooting this phone - at least some of which include information about rooting Android 13 - which that itself is no different than rooting Android 12.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Has anyone a good how to for rooting for a noob?
Taker18 said:
Has anyone a good how to for rooting for a noob?
Click to expand...
Click to collapse
This is a great thread for the info you need.
Thread '[GUIDE] Pixel 6 Pro "raven": Unlock Bootloader, Update, Root, Pass SafetyNet' https://forum.xda-developers.com/t/...ootloader-update-root-pass-safetynet.4356231/
fil3s said:
Just make sure you boot the patched boot.img file and direct install. To avoid possible issues
Click to expand...
Click to collapse
That actually increases your chance of issues. If it successfully boots the "fastboot boot"'d one, but messes up the "direct installed" one, then you've incremented the antirollback counter, but now will fail to boot, which could lead to a brick if you messed something up like forgot to install the bootloader to the second slot.
The best way to install is to "select and patch a file" from magisk, then "fastboot flash" it to both slots. Of course also make sure that you "fastboot flash" the bootloader to both slots as well (prior to installing A13).
Taker18 said:
Has anyone a good how to for rooting for a noob?
Click to expand...
Click to collapse
Also, just click the yellow How To Guide quick filter at the top of the list of threads - there are at least 2-3 threads you can follow.
Hi, i have rooted a few phones in the past without problems but it´s my first samsung and nothing seems to work... Read a lot a tutorials, tried a lot of things and for now, no success in any...
I'm on the latest version of Android (12) - ZTO-F415FUBS2CVF1
I did unlock the bootloader without problems... Extracted stock rom boot.img, patched it with magisk 22104. Put it inside a boot.tar, flashed it in Odin with success:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After the patch, i always go straight to stock recovery and wipe data...
It´s really weird, when i install magisk, after the flash, it only says this:
I also did try to follow magisk instructions and flash the whole stock rom with the AP patched but it gives me an vbmeta error, so i reverted to stock firmware and kept trying to patch only boot.img...
Also tried to revert to android 11 with Odin but it gives me an wrong version error on download mode...
I don´t know if i'm using the wrong magisk version, or something is missing in the tutorials... Also tried to find something here but nothing seems to work... Can someone help me ?
Same problem here. VBmeta is giving me a lot of trouble.
Loking foward for a solution...
Hi guys...
Anyone have any luck rooting this f.... android 12 on Samsung M21s? It sucks.
I cant hold it anymore...
A beg a little help .
A want my cell phone back. kkkk
Regards...
.
Hi! When you get that in magisk can you direct install?
ps. I do not have this device but I rooted Samsung so I may be able to help
RodrigoC82 said:
Hi, i have rooted a few phones in the past without problems but it´s my first samsung and nothing seems to work... Read a lot a tutorials, tried a lot of things and for now, no success in any...
I'm on the latest version of Android (12) - ZTO-F415FUBS2CVF1
I did unlock the bootloader without problems... Extracted stock rom boot.img, patched it with magisk 22104. Put it inside a boot.tar, flashed it in Odin with success:
View attachment 5700249
View attachment 5700251
After the patch, i always go straight to stock recovery and wipe data...
It´s really weird, when i install magisk, after the flash, it only says this:
View attachment 5700257
I also did try to follow magisk instructions and flash the whole stock rom with the AP patched but it gives me an vbmeta error, so i reverted to stock firmware and kept trying to patch only boot.img...
Also tried to revert to android 11 with Odin but it gives me an wrong version error on download mode...
I don´t know if i'm using the wrong magisk version, or something is missing in the tutorials... Also tried to find something here but nothing seems to work... Can someone help me ?
Click to expand...
Click to collapse
Can I see the error? It may be because flashing just the ap in the first place shrunk your space.
Hello,
I had a working Setup with TWRP + Magisk.
Then I had the stupid idea to accept the OTA update to MIUI 14.0.6.0 (eu).
As I lost my root permissions, I decided to install Magisk again. I used the boot.img from the rom and installed it via fastboot from magisk_patched-XXXX.img.
When I look into the Magisk App (v26.1), it still states: "Installed N/A".
I also tried to flash the patched boot image via TWRP, but there is no way to gain root access anymore :/
Current Version: MIUI V14.0.6.0.TKHCNXM | stable
Can somebody give me a hint, what i'm doing wrong? I also tried to flash the _a and _b slot...
Thanks,
Stefan
stefan_at_localhost said:
Hello,
I had a working Setup with TWRP + Magisk.
Then I had the stupid idea to accept the OTA update to MIUI 14.0.6.0 (eu).
As I lost my root permissions, I decided to install Magisk again. I used the boot.img from the rom and installed it via fastboot from magisk_patched-XXXX.img.
When I look into the Magisk App (v26.1), it still states: "Installed N/A".
I also tried to flash the patched boot image via TWRP, but there is no way to gain root access anymore :/
Current Version: MIUI V14.0.6.0.TKHCNXM | stable
Can somebody give me a hint, what i'm doing wrong? I also tried to flash the _a and _b slot...
Thanks,
Stefan
Click to expand...
Click to collapse
You'll want to use fastboot to boot recovery (not flash)
And install the recovery via the on device gui
Also, I would use orangefox recovery, it was built from twrp, but has more features.
Use "method 2" in this guide:
https://theandroidrush.com/how-to-flash-orangefox-recovery-on-xiaomi-phone/
Hi,
I flashed the patched magisk boot via orangefox, but no success. Magisk still N/A
Step1: Patch boot
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Step2: Flash via TWRP or Orangefox
no screenshot available
Step3: Result, no Magisk (N/A)
I don't understand this. Is there a greater change in MUI14?
I also installed the Magisk APK via TWRP and Orangefox, but no other result.
Thanks,
Stefan
After serveral hours of debugging I found out, that there was a post on the net, which recommended to install the debug version of Magisk. This was a first step into the right direction. But the GUI crashed and removed the Magisk App.
The strange thing was, that all other whitelisted root apps worked. But no access to change the Whitelist.
So I tried to get the GUI back. But there was no way.
When I installed the APK, it was automatically killed and removed :/
After reinstalling via the xiaomi.eu repair (update) script I decided to to try an older Magisk Version (26.0). This crashed also, but I was able to re-run the app again.
Finally it seems that Magisk implemented a change, that crashes with my MIUI version. I will observe this and try to file a bug report.