This is an announcement post about new very fast and reliable temp root exploit for XZ1c/XZ1/XZp phones with latest oreo fw, using recent vulnerability in binder (CVE-2019-2215).
Please check the following thread in Sony Cross-Device General section:
[XZ1c/XZ1/XZp] temp root exploit via CVE-2019-2215 including magisk setup [Locked BL]
It may be used as an alternative to renoroot for TA (drm keys) backup or with implemented script to start and use magisk on still locked phone.
Now also including support for Japan and Canada phones variants.
Big thanks to you!
One question though, pie users have to downgrade to suported target (firmware) to use this tool, right?
However, it is hard to find listed firmware (like G8342_47.1.A.16.20) .
So, I must downgrade to 47.1.A.2.281_CE1, and then OTA to 47.1.A.16.20, and use the new temp root, correct?
Thank you again!
@tombbb, that's right, you need a listed fw. But it's not that hard to find:
G8342 47.1.A.16.20 at xperiasite.pl
Xperia XZ1 even Japan and Canada versions at boycracked.com
j4nn said:
@tombbb, that's right, you need a listed fw. But it's not that hard to find:
G8342 47.1.A.16.20 at xperiasite.pl
Xperia XZ1 even Japan and Canada versions at boycracked.com
Click to expand...
Click to collapse
WOW!
I thought I must have hongkong version fw to downgrade to....
So its ok if I downloaded Armenia, Russia or USA version?
@tombbb, I would skip usa version as that probably does not have fingerprint enabled.
You might use oem.sin from your region fw, possibly from older fw that you happen to have.
Or just forget about it, simply selecting your language.
Good to see things are going for the XZ1 on 2020
i can root and turn on camera api. i want install google camera for xz1 Au . i can't unlock bootloader . bootloader unlock : no
Please with android PIE
j4nn said:
This is an announcement post about new very fast and reliable temp root exploit for XZ1c/XZ1/XZp phones with latest oreo fw, using recent vulnerability in binder (CVE-2019-2215).
Please check the following thread in Sony Cross-Device General section:
[XZ1c/XZ1/XZp] temp root exploit via CVE-2019-2215 including magisk setup [Locked BL]
It may be used as an alternative to renoroot for TA (drm keys) backup or with implemented script to start and use magisk on still locked phone.
Now also including support for Japan and Canada phones variants.
Click to expand...
Click to collapse
@j4nn kindly make it available for xz1 701so its not available for xz1 47.1.D.1.133
My email is [email protected]
if any one has a twrp recovery method for xz1 701so 47.1.D.***** kindly send to me
i am in a dire need of temp root i spent all my money on it and also its bootloader is locked
kindly find a way for me plzz
j4nn said:
This is an announcement post about new very fast and reliable temp root exploit for XZ1c/XZ1/XZp phones with latest oreo fw, using recent vulnerability in binder (CVE-2019-2215).
Please check the following thread in Sony Cross-Device General section:
[XZ1c/XZ1/XZp] temp root exploit via CVE-2019-2215 including magisk setup [Locked BL]
It may be used as an alternative to renoroot for TA (drm keys) backup or with implemented script to start and use magisk on still locked phone.
Now also including support for Japan and Canada phones variants.
Click to expand...
Click to collapse
i have searched the whole forum no one discuss xz1 701so kindly work on it i spend all of my money on it
hoa bi ngan said:
i can root and turn on camera api. i want install google camera for xz1 Au . i can't unlock bootloader . bootloader unlock : no
Click to expand...
Click to collapse
shahid1234abc said:
@j4nn kindly make it available for xz1 701so its not available for xz1 47.1.D.1.133
...
Click to expand...
Click to collapse
There are some possibilities for these Japanese XZ1 phones, could be very interesting to test.
Please pm me. Thanks.
Any updates on temp root on pie? I just want to make my games smoother because of agressive thermal throttling...
sidex15 said:
Any updates on temp root on pie? I just want to make my games smoother because of agressive thermal throttling...
Click to expand...
Click to collapse
Why not use temproot in oreo ?
diba pranasta said:
Why not use temproot in oreo ?
Click to expand...
Click to collapse
Well i feel outdated on oreo... I like the new features on pie...
There are two temp root methods for oreo. I am not working on any new method to temp root on pie.
i have a promblem.. how to fix it?
{
"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"
}
Related
after some time playing with my Ray i decided to unlock bootloader to gain the performance and battery life with custom ROM and kernels.Tried unofficial method with S1tool (testpoint) with no success.Searched around and it looks like that new Sony's has new security for bootloader.............waiting for solution,here is the screenshot of the 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"
}
Try official Sony unlock ?
Did you try test point ? It's look like you haven"t unlocked your phone but it is
-Jesco- said:
Try official Sony unlock ?
Click to expand...
Click to collapse
Won't work if the phone is bought from a carrier (at least in North America).
I have the same problem with a MK16a Xperia Pro, production date 12W21. Testpoint doesn't work.
If your phone is produced after 12W14 it probably has the new security chipset that blocks the testpoint method.
I have done too much research on this - it is currently impossible to unlock these new Xperias using these setool programs, while the Sony S1 signature server is offline.
The worst part is, I decided to just SIM unlock the phone the traditional way (buying a code) and the code doesn't work (tried 2 providers, gave me the exact same code), so I can't even sell this junk I believe the new security chipsets are even blocking traditional unlock codes.
It is simfree phone so i dont have to unlock for all network,not interested in official unlock bootloader cause i dont wanna loose ability to update official way(fota brick),anyway thanks for the answers and hope that somebody will hack the "new security" soon.....stock ICS is laggy and choppy and i reverted to GB,frozen the bloatware and the phone is much better compared to how it was out of the box but i would like to test the custom kernels and ROM..........
I'm having the exact same problem. Would you check out my thread?
http://forum.xda-developers.com/showthread.php?t=1889274
I wrote it before I found out there was the production date issue. You're from Canada so you're probably dealing with a Pro from Fido I'm guessing? Which is exactly mine. MK16a 12W21
I can sort of see why people are worried about losing the ability to officially update. But typically a developer uploads official builds within a day or two of the release. In fact because different regions and carriers release at different times you often get an update sooner via the forum. Similarly Sony are rolling out a tool for unlocked boot loaders to allow official builds to be installed. I think you have to try really hard to damage your phones hardware the official unlock method carries few risks if you're reasonably careful.
Sent from my Xperia Ray using xda premium
komsa said:
after some time playing with my Ray i decided to unlock bootloader to gain the performance and battery life with custom ROM and kernels.Tried unofficial method with S1tool (testpoint) with no success.Searched around and it looks like that new Sony's has new security for bootloader.............waiting for solution,here is the screenshot of the error
Click to expand...
Click to collapse
tried with wotanserver?
for me it worked this server
try with flashtool. its working for newest xray.
I was thinking the cause was lost too, then I found www.wotanserver.com yesterday afternoon, paid a small fee (€7.99) and now my 2011 Xperia Ray is Network/Bootloader unlocked and functioning perfectly. Hope this helps?
I tried wotan server but wasn't work with my device
seamo123 said:
I was thinking the cause was lost too, then I found www.wotanserver.com yesterday afternoon, paid a small fee (€7.99) and now my 2011 Xperia Ray is Network/Bootloader unlocked and functioning perfectly. Hope this helps?
Click to expand...
Click to collapse
it's a 2011 model - before Sony introduced new security to defeat testpoints. So it's not helpful for those whose handsets were produced after February 2012.
Hey guys, is there any new exploits / rootkitXperias for the 6.0.1 update with locked bootloader?
Same question here. This would be very nice.
No have Way For Root M4 Aqua In Locked Bootloader!
and in the future?
kubanec86 said:
and in the future?
Click to expand...
Click to collapse
despite our developers, Coming Soon
I also have locked bootloader (Unlock allowed: no; and also I would prefer to keep the DRM keys and warranty) however it would be great to be able to root it...
well, at least we can preinstall xposed with prf zip
sergioslk said:
well, at least we can preinstall xposed with prf zip
Click to expand...
Click to collapse
prf zip rom don't working, I try it.
That sounds great Hope there will be a solution soon.
Is there any update about it? I really want to update to MM but dont want loose my root.
BVEKT0R said:
Is there any update about it? I really want to update to MM but dont want loose my root.
Click to expand...
Click to collapse
Nope
Can someone with access to the M4 run the Quadrooter checker. Hopefully these security issues give root.
http://blog.checkpoint.com/2016/08/07/quadrooter/
http://www.xda-developers.com/xda-external-link/4-vulnerabilities-found-in-qualcomms-code/
I know people are saying it's a security issue but it's also possibly the only hope for root for a lot of phones.
https://play.google.com/store/apps/details?id=com.checkpoint.quadrooter
CE1
{
"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"
}
Click to expand...
Click to collapse
I have the E2306 variant, i've been reading about a new bulnerabilty called "humingbad".
In the page where i readed that i found info from a app that search system bulnerabilties and after running on my device there is four bulnerabilties
(cve-2016-2059)(cve-2016-2504)(cve-2016-2503)
(cve-2016-5340).
Correct if i'm wrong but for gain root acces on a locked device is by using a system bulnerabilty like those?
I think maybe with any of the bulnerabilties that i've mentioned before we can get root for locked bootloaders.
(sorry for my english if it's bad, not my native language)
Found this on z5 forums. I'm pretty sure there is dm verity check on m4 too.
We cannot get root because this would involve modified kernel (to write on /system partition), which would not boot using a Locked bootloader because of Verified boot process that uses an OEM key.
The whole process is described here: https://source.android.com/security/...fied-boot.html
Google intention is (or was) to allow the boot process, after a red warning, if the verification of the kernel image didn't succeed on a locked bootloader... But Sony devices bootloop without showing any warning and so the user is not allowed to continue (source: https://androplus.org/Entry/843/ thanks to the developer).
So, on locked bootloaders, it's impossible to have permanent root apps, xposed ,.... unless someone finds a hole in the bootloader (someone found a hole in Motorola's bootloader) or the OEM key gets copied and is used to sign modified firmwares...just exciting dreams.
Click to expand...
Click to collapse
DarkerJava said:
Found this on z5 forums. I'm pretty sure there is dm verity check on m4 too.
Click to expand...
Click to collapse
There is not dmverity in m4, i have locked bootloader and i installed the update with an unrooted zip but i could preinstall xposed in /system and also deleted bloatware and booted correctly with xposed working and without root
sergioslk said:
There is not dmverity in m4, i have locked bootloader and i installed the update with an unrooted zip but i could preinstall xposed in /system and also deleted bloatware and booted correctly with xposed working and without root
Click to expand...
Click to collapse
Alright, if there is no firmware verity check, then it should not be to hard to get root in bl locked... just need to find an exploit in /system partition..
Hellow, Everyone can test this way for preerooted rom?
This way rooted we device in lockedbootloader, But every Boot phone is longer. it way test in E2333 and now need to test in other veriants.
Plaese test and feedback in here, boot phone in 40min and uper
http://forum.xda-developers.com/crossdevice-dev/sony/tool-prfcreator-easily-create-pre-t2859904
EHSAN™ said:
Hellow, Everyone can test this way for preerooted rom?
This way rooted we device in lockedbootloader, But every Boot phone is longer. it way test in E2333 and now need to test in other veriants.
Plaese test and feedback in here, boot phone in 40min and uper
http://forum.xda-developers.com/crossdevice-dev/sony/tool-prfcreator-easily-create-pre-t2859904
Click to expand...
Click to collapse
I'll test it soon, and post about the results.
EHSAN™ said:
Hellow, Everyone can test this way for preerooted rom?
This way rooted we device in lockedbootloader, But every Boot phone is longer. it way test in E2333 and now need to test in other veriants.
Plaese test and feedback in here, boot phone in 40min and uper
http://forum.xda-developers.com/crossdevice-dev/sony/tool-prfcreator-easily-create-pre-t2859904
Click to expand...
Click to collapse
Hello,
I've test with "E2303_26.1.A.3.111_1293-7738_R8A.ftf" rom and just "UPDATE-SuperSU-v2.76.zip" (no recovery) but it don't works, the phone boot (it take a long time) but isn't rooted.
{
"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"
}
Note - Iam Not Responsible for bricked devices
About Android 10 Internal Build
Well we all know that Hmd Released a Road map for Android Q update for 2018 released handsets well in that our Nokia 6.1 Plus will recieve in Jan 2020 Q1 so here the thing is before tasting a stable build by Hmd let me share a beautiful internal stable Beta build by Hikari Calyx
Installation procedure
1. Unlocked bootloader
2. Forget about your data
3. Turn of your phone boot in to download mode
4. Click on flash_all.bat
Sit back and relax for 10 min automatically your phone boots in to android Q
Credits
Massive thank you for hikari_calyx ( Without him there is no internal build )
Download Android Q
XDA:DevDB Information
Android Q for the Nokia 6.1 Plus / X6
Contributors
hikari_calyx
Raghu varma
Created 2019-10-12
Last Updated 2019-10-12
here are some screenshots
Now Some common Questions
Q1. Can we flash this on Oreo or On pie?
A. yes
Q2. Can we try this on Locked Bootloader?
A. No
Q3. Can we use this without Adb Tools?
A. No
Q4. Can we Expect bugs?
A. may be or may not
Q5. Can we Downgrade to pie from Q?
A. well our Nokia 6.1 Plus doesnt have Anti roll back so we can flash any android version either oreo or pie or Q
Warranty will be valid or not after this?
Doesnt work with glash.bat
Through stock recovery work though
ps_minky16 said:
Doesnt work with glash.bat
Through stock recovery work though
Click to expand...
Click to collapse
strange for me worked nothing went wrong
nbhowmik3 said:
Warranty will be valid or not after this?
Click to expand...
Click to collapse
The question is very unintelligent...
Q2. Can we try this on Locked Bootloader?
A. No
Unlock bootloader = No warranty
Up to android 10, can it be root?
PvTuan said:
Up to android 10, can it be root?
Click to expand...
Click to collapse
use magisk 20.zip
please help me
Does volte worked?
sltushar said:
Does volte worked?
Click to expand...
Click to collapse
Yes. It does, You just need to go to settings and enable 4G LTE and enhanced 4g network options.
sltushar said:
Does volte worked?
Click to expand...
Click to collapse
Hy man are you able to browse our forum in google chrome? How did you sent this message by XDA app or pc? If PC means send link
Xda lab app, i know our device forum is not browsable on pc or browser
sltushar said:
Xda lab app, i know our device forum is not browsable on pc or browser
Click to expand...
Click to collapse
Thanks for the confirmation
Anyone who have installed the 10, can u please guys confirm, which method to install is preferred and if everything is fine, so i could go fo bootloader unlock
Is there a fix for that mic bug during calling mic doesn't take voice unless call is put on speaker.
Second question is can we expect ota updates from hmd in this build
ankit gaur said:
Is there a fix for that mic bug during calling mic doesn't take voice unless call is put on hold.
Second question is can we expect ota updates from hmd in this build
Click to expand...
Click to collapse
Yes probably an update a stable one for the Q is gonna be out but we don't know when to that's gonna be
sltushar said:
Anyone who have installed the 10, can u please guys confirm, which method to install is preferred and if everything is fine, so i could go fo bootloader unlock
Click to expand...
Click to collapse
I've installed it via stock recovery adb from sd card method, it's the easiest and working.
sltushar said:
Anyone who have installed the 10, can u please guys confirm, which method to install is preferred and if everything is fine, so i could go fo bootloader unlock
Click to expand...
Click to collapse
If you can OTA update to the October security patch, it's best to use the installer from Hikari instead of the fastboot method I think.
The fastboot method here is just a system, boot, and vendor image. For me it didn't work, coming from a custom rom.
The method in Hikari's thread will make sure all your firmware partitions are correct.
I'm now about to rescue my Nokia TA1341 (X20) from such a locked state from my final screenshot
And by using those firmware sources to be flashed by Nokia NOST 0.6
But i wonder if NOST knows to read those fw packages, and why if not, then finally how to patch those 2 sources of fw packages to be known to NOST for the final flashing
I have a Google account logged in so that maybe FRP soft bricks that Nokia TA1341, and i've to unbrick in order to get the access of that Google account back to me by doing so
Anyway i'm not that rushed to have that Nokia recovered which i also have a few Samsung and Chinese Androids also in use
{
"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"
}
hd_scania said:
I'm now about to rescue my Nokia TA1341 (X20) from such a locked state from my final screenshot
And by using those firmware sources to be flashed by Nokia NOST 0.6
But i wonder if NOST knows to read those fw packages, and why if not, then finally how to patch those 2 sources of fw packages to be known to NOST for the final flashing
I have a Google account logged in so that maybe FRP soft bricks that Nokia TA1341, and i've to unbrick in order to get the access of that Google account back to me by doing so
Anyway i'm not that rushed to have that Nokia recovered which i also have a few Samsung and Chinese Androids also in use
View attachment 5901099View attachment 5901101View attachment 5901103
Click to expand...
Click to collapse
first question: what is that Telegram channel about?
second one: I thought NOST cannot be used on the X10/20?
That Telegram channel is a Nokia firmware package channel https://t.me/nokiarepoen
And others also following that channel said, since Android 13 manual flashing of firmware will no longer be viable
Btw such a device is listed on Android Enterprise recommended, AER, maybe that's the main cause couldn't manually flash Android 13+ anymore
But my device before the brick was on Android 12, so unsure if couldn't be rescued anymore
And which tools could be used w/o requiring online user logins at all on X20 when NOST couldn't be used?
AltFantasy said:
first question: what is that Telegram channel about?
second one: I thought NOST cannot be used on the X10/20?
Click to expand...
Click to collapse
Maybe those 2 fw packages are either correct, however ...
What's the correct tool to flash them for my Nokia TA1341?
I don't want sth requiring HMD-like UID requirements
Or ... How to locally and easily subscribe my Microsoft account for Nokia HMD UID's? And even not open to payments for the public but only for internal use of HMD partners?
hd_scania said:
That Telegram channel is a Nokia firmware package channel https://t.me/nokiarepoen
And others also following that channel said, since Android 13 manual flashing of firmware will no longer be viable
Btw such a device is listed on Android Enterprise recommended, AER, maybe that's the main cause couldn't manually flash Android 13+ anymore
But my device before the brick was on Android 12, so unsure if couldn't be rescued anymore
And which tools could be used w/o requiring online user logins at all on X20 when NOST couldn't be used?
Click to expand...
Click to collapse
hd_scania said:
Maybe those 2 fw packages are either correct, however ...
What's the correct tool to flash them for my Nokia TA1341?
I don't want sth requiring HMD-like UID requirements
Or ... How to locally and easily subscribe my Microsoft account for Nokia HMD UID's? And even not open to payments for the public but only for internal use of HMD partners?
Click to expand...
Click to collapse
use 3rd-party solutions (which, most of the time, make you pay a little bit amount of money for bootloader unlocking, which violates XDA's rules), unless what you're willing to do is doing any types of cyberattack on HMD's partners and/or customer service (with access to HDK) (which is illegal, and also violates XDA's rules.)
Then the Nokia TA1341 was out of luck in order to be legally recovered
Whose lifetime also was ceased today, i've to have a Sony replacement instead
AltFantasy said:
use 3rd-party solutions (which, most of the time, make you pay a little bit amount of money for bootloader unlocking, which violates XDA's rules), unless what you're willing to do is doing any types of cyberattack on HMD's partners and/or customer service (with access to HDK) (which is illegal, and also violates XDA's rules.)
Click to expand...
Click to collapse
hd_scania said:
Then the Nokia TA1341 was out of luck in order to be legally recovered
Whose lifetime also was ceased today, i've to have a Sony replacement instead
Click to expand...
Click to collapse
eh, you should go and try to find ways to enable flashing permission with those 3rd-party solutions, so that when the prototype ABL of the TA1341 is out, you can just flash the ABL to unlock the bootloader and reflash stock ROM.
I'll send you a PM on one of those services, and details about it, if you're fine with paying money, that is...
Since the bootloader is locked, the only suitable way is an official flash - that bypasses the bootloader lock using the server-based solution to the device challenge. It is like a one-time key to gain flashing permission on the device's bootloader. There is no other way.
I can flash your phone with the available firmware, but given how restricted this hmd world is and how things are handled, it won't be a free service. And it would also be nice if you can elaborate how the device got bricked.
Hi guys, after coming from Xiaomi Mi6 I have now Pixel 6, I m aware of flashing running adb and unlock Bootloader, but here I see three threads and m so confused what to do, Regarding unlock bootloader and root twrp safety net etc, so the real question is why there are so many files? And does Pixel Flash Tool resolve all this problem by automatically doing its job?
Here is the confusion
Wow what all this? What is initial root /create master root image >> ok if this is an basic root and problem can be solved then what is this update and root automatic ? Root ota sideload?
{
"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"
}
TWRP is not available for the Pixel 6 series, so forget about TWRP.
The one and only page you should need to do whatever you need to is at https://forum.xda-developers.com/t/...ootloader-update-root-pass-safetynet.4356233/ . You literally only need ADB, Magisk, and a copy of the boot image to be able to root your device. The Displax variant of the safetynet fix is optional, but if you intend on using your device for tap-to-pay you'll need to install it.
Flashing tools like the Pixel Flash Tool may simplify the process, but you would be best served learning to do it manually first so you can see and understand what is happening in real time. After you see how an update processes you can, if comfortable, go ahead and use a flashing tool.
What is update and Root Automatic OTA??
Further I see Update and Root Factory Image??
Do I need to do all those Steps mentioned? Are they necessary? Except the safety net part which u have already told...
Strephon Alkhalikoi said:
TWRP is not available for the Pixel 6 series, so forget about TWRP.
The one and only page you should need to do whatever you need to is at https://forum.xda-developers.com/t/...ootloader-update-root-pass-safetynet.4356233/ . You literally only need ADB, Magisk, and a copy of the boot image to be able to root your device. The Displax variant of the safetynet fix is optional, but if you intend on using your device for tap-to-pay you'll need to install it.
Flashing tools like the Pixel Flash Tool may simplify the process, but you would be best served learning to do it manually first so you can see and understand what is happening in real time. After you see how an update processes you can, if comfortable, go ahead and use a flashing tool.
Click to expand...
Click to collapse
[email protected] said:
What is update and Root Automatic OTA??
Further I see Update and Root Factory Image??
Do I need to do all those Steps mentioned? Are they necessary? Except the safety net part which u have already told...
Click to expand...
Click to collapse
Update and root factory / OTA images only applies if you have already rooted, thus the word "update". And yes, all the steps given are required. Read them, digest them, and read them again. That thread will save you a lot of headaches.
Strephon Alkhalikoi said:
Update and root factory / OTA images only applies if you have already rooted, thus the word "update". And yes, all the steps given are required. Read them, digest them, and read them again. That thread will save you a lot of headaches.
Click to expand...
Click to collapse
Yes I will try... Many devices have simple steps tp follow... I guess... Although there is no twrp then how come roms are flashing via adb if there no recovery..
@[email protected], please excuse pholdemulpti; it is fairly obvious the reply is an A.I. generated reply and involves/includes wrong and/or incomplete information -- so please be wary of taking the advice in the post and proceed being aware of the risk.
pholdemulpti said:
As for the Pixel Flash Tool, it is a tool developed by Google to simplify the process of flashing firmware and images on Pixel devices. It can be used to install stock firmware, unlock the bootloader, and flash custom images like TWRP. However, it's important to note that using the Pixel Flash Tool may still require some knowledge and experience with Android modding, and it may not work for all devices or scenarios.
Click to expand...
Click to collapse
First, if you really are speaking on the tool Google develops, it is called Android Flash Tool, not "Pixel" -- no such thing; a simple Google search shows it. And it does not flash "custom images like TWRP", and requires just the basic "knowledge and experience with Android modding".
Second, there is a tool called PixelFlasher developed by badabing2003 (not Google), which does flash custom images (ROMs, patched [Magisk] boot images, both slots, etc.), and has further checks & protocols (using the version of platform-tools that does not have fatal bugs for Pixel 6+) which works on all Pixels.
I'm fairly certain whatever A.I. generated tool/service being used is simply combining the two "tools" as they are similar and apply/relate to similar devices....
pholdemulpti said:
In terms of the "initial root" and "master root image" files you mentioned, it's possible that these are custom rooting packages designed for your specific device or software version. However, it's difficult to say without more information or context. Similarly, the "update and root automatic" file may be an automated rooting package, but it's important to research and verify the source and compatibility of any files before using them.
Click to expand...
Click to collapse
Orange text is pretty clear showing this is an A.I. generated response; "more information or context"? The rest of us that has read this thread got what OP meant....