Related
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about this procedure before doing it! YOU are choosing to make these modifications.
Click to expand...
Click to collapse
OP6 rooting without TWRP
Checklist before preceed:
Working Fastboot
Be on software OOS 5.1.5 | 5.1.6 | 5.1.7 | 5.1.8
Unlocked bootloader (Instruction here, but remember to enable OEM Unlocking first)
Funk Wizard said:
Enable OEM Unlocking
On your phone go to Settings > Developer options. Then enable the 'OEM Unlocking' option. Also make sure that from now on, OEM unlocking option is enabled before you reboot as sometimes, it might get disabled itself.
Click to expand...
Click to collapse
WARNING:
Please double check that you have unlocked bootloader!
A few users has reported that instaling magisk with locked bootloader or wiping phone (using stock recovery) with patched boot.img can soft brick your phone! Please avoid doing this for now. If you've already done this and you are stuck with only fastboot working please follow this post https://forum.xda-developers.com/showpost.php?p=76608874&postcount=31 to restore your device to working state. Thank's to @SaiBork for more detailed instructions available here https://forum.xda-developers.com/showpost.php?p=76632484&postcount=82
Rooting process:
Make sure that you have UNLOCKED BOOTLOADER. DO NOT attempt to patch boot.img using Magisk Manager without unlocked bootloader because it WILL CAUSE SOFT BRICK!!!
Boot device using patched boot.img.
For OOS 5.1.5 it can be downloaded [here]
For OOS 5.1.6 it can be downloaded [here]
For OOS 5.1.7 it can be downloaded [here]
For OOS 5.1.8 it can be downloaded [here]
It can be also patched manually (see bottom of this post).
To do this you need working fastboot. Fire up your cmd/terminal and cd to directory where you've downloaded/placed patched boot image. When you are in correct directory just type in cmd/terminal:
Code:
fastboot boot patched_boot_magisk1642_518.img
(check if img filename in command is exactly same as name of downloaded boot img) The phone should boot to Android.
Once the phone has booted install Magisk Manager app and open it. It can be downloaded here or here.
Magisk Manager App should show that your phone is rooted - but at this stage it's just temporary, until next reboot (nothing flashed yet).
Go to settings and Tap on "Update channel" and change it to Beta.
Go back to Magisk main screen and make sure that "Preserve force encryption" and "Preserve AVB 2.0/dm-verity" are checked!
Tap on "Install" and select "Direct Install (Recommended)".
Wait until boot.img is patched and flashed and reboot your device when prompted to do so.
After boot there aren't any error messages shown before (or after) entering PIN code, unlike when rooting using other methods.
To check SafetyNet status just open Magisk Manager once again and tap on "Tap to start SafetyNet check". It should be all green.
wOOt wOOt you just got rOOt!
Video showing rooting process:
XDA user @GizmoFreak has made a video showing the whole procedure for 5.1.5! Thank you very much.
How to do an OTA update preserving root
Install OTA. It will be installed on the inactive slot. Do not restart your OP6 when installation finishes.
Start Magisk Manager app.
Tap on Install.
Tap on Install to Second Slot (After OTA).
Reboot your device.
Check if you got root and if safety net checks are passed.
How to extract from OTA and manually patch stock OOS boot.img using Magisk Manager:
Install python3 and PIP manager on your system .
Use pip to install "protobuf" module:
Code:
pip3 install protobuf
Download payload_dumper.py and update_metadata_pb2.py from this gist https://gist.github.com/ius/42bd02a5df2226633a342ab7a9c60f15 and save them in one directory.
Download full update zip with OOS (containing payload.bin). It can be downloaded from this great thread by @Titokhan
Extract payload.bin from update zip to same directory where payload_dumper.py is located.
Use payload_dumper.py to extract original boot.img
Code:
python payload_dumper.py payload.bin
After a while you should have all img's included in payload.bin dumped in your working directory.
Install Magisk Manager app on your OP6.
Place that dumped boot.img on your phone storage.
In Magisk Manager app tap install, and select "Patching boot image file". Select boot.img that you've just uploaded to your phone.
Magisk Manager will patch boot.img and save it on Phone's internal storage in "MagiskManager" directory (file called "patched_boot.img").
Download this patched file to your computer and just use it to boot using fastboot
stock recovery img please
Hi and thx for the Thread. Maybe more Details in your Guide would be nice and you dont lose you Void by OnePlus if you Root you Device only if u break the hardware with you root access (Like changing the CPU rate in the Kernel).
NeoNecOP6 said:
Hi and thx for the Thread. Maybe more Details in your Guide would be nice and you dont lose you Void by OnePlus if you Root you Device only if u break the hardware with you root access (Like changing the CPU rate in the Kernel).
Click to expand...
Click to collapse
How do they know if you manipulate the CPU frequency?
Thanks, I'd like to try patching the boot.img myself - how did you extract it from the device without root?
I also couldn't figure out how to extract it from the update files OP provided (since they are all A/B updates only containing a payload.bin)
liver20 said:
stock recovery img please
Click to expand...
Click to collapse
There is no separate recovery partition. Recovery in boot.img, as all A/B devices.
NeoNecOP6 said:
and you dont lose you Void by OnePlus if you Root you Device only if u break the hardware with you root access (Like changing the CPU rate in the Kernel).
Click to expand...
Click to collapse
I know but it's just a disclaimer
Kaeltis said:
Thanks, I'd like to try patching the boot.img myself - how did you extract it from the device without root?
I also couldn't figure out how to extract it from the update files OP provided (since they are all A/B updates only containing a payload.bin)
Click to expand...
Click to collapse
You can extract it from A/B update using python tool called payload_dumper.py Check this post for more information https://forum.xda-developers.com/showpost.php?p=76598704&postcount=80
jacdelad said:
How do they know if you manipulate the CPU frequency?
Click to expand...
Click to collapse
if that's why your smartphone broke down. Any company can find out if the device has been rooted.
http://tinypic.com/view.php?pic=2dquejq&s=9
Rooted
Thanks op
This worked perfectly for me. No vendor image issues either. No flashing (that's cool!). Thanks! I saw you posted how you did it but it'd be cool if you could add it to this thread so people can learn.
Thanks!
b1czu said:
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about this procedure before doing it! YOU are choosing to make these modifications.
For all interested in rooting I suggest to do it this way:
Checklist before preceed:
- Working Fastboot
- Unlocked bootloader
- Be on software OSS 5.1.5!!
1. Boot patched boot.img that can be downloaded here [https://drive.google.com/open?id=1BIH5sGfMADfhWIAfQDsiw4f-UI_1WvqX]
To do this you need working fastboot and cd to directory where you've downloaded patched boot image. When you are in correct directory just type in cmd/terminal:
Code:
fastboot boot patched_boot_magisk1642.img
The phone should boot to Android.
2. Once phone is booted up install Magisk Manager and open it.
3. It should show that you have root - but at this stage it's just temporary, until next reboot (nothing flashed yet).
4. Go to settings and Tap on "Update channel" and change it to Beta.
5. Go back to Magisk main screen and make sure that "Preserve force encrypotion" and "Preserve AVB 2.0/dm-verity" are checked!
6. Tap on "Install" and select "Direct Install (Recommended)"
6. Reboot
After boot there are no any Error messages before entering PIN code.
Just open magisk manager once again and tap on "Tap to start SafetyNet check". It should be all green.
wOOt wOOt you just got rOOt!
Click to expand...
Click to collapse
Thanks for this. Probably a dumb question. But, does this need to be undone when TWRP comes out? Is there a way to revert back?
Thanks again.
mcdavid said:
But, does this need to be undone when TWRP comes out?
Click to expand...
Click to collapse
No, you don't need to undone this. Flashing magisk root using TWRP recovery would lead to same end-effect.
mcdavid said:
Is there a way to revert back?
Click to expand...
Click to collapse
Yes. You can flash back stock OOS 5.1.5's boot.img, because nothing other was modified. Link to download STOCK boot.img for OOS 5.1.5 https://drive.google.com/open?id=1RPQZj6HQxNNdJiMrAjtkxncH3PLBTZp_
To revert you need fastboot tool:
Code:
fastboot flash boot boot.img
And that's it. You're again rootles on stock 5.1.5's boot.img.
thanks man!!!
Op6 rooted and ready for me!
OnePlus 3: TWRP, Root & Cyanogenmod before most users got the device,
OnePlus 5: Unofficial TWRP,
And OnePlus 6: Root without any custom recovery....
Thank you!
Wow thank you for this, can't live without root and I get my OP6 tomorrow so this is great
i installed patched boot file for oss5.1.3 using boot file for oss5.1.3. my question is when i update oss to latest for now i.e oss5.1.5 will i need to re root it? or it will stay rooted? and i won't get stuck at installing the update too right? considering its gonna be full updates now(no partial updates).
dynamic_4444 said:
i installed patched boot file for oss5.1.3 using boot file for oss5.1.3. my question is when i update oss to latest for now i.e oss5.1.5 will i need to re root it? or it will stay rooted? and i won't get stuck at installing the update too right? considering its gonna be full updates now(no partial updates).
Click to expand...
Click to collapse
When you update, boot.img will be overwritten with 5.1.5's one and you'll have to repeat the process again.
@b1czu, thank you very much! Rooted flawlessly .
Worked like a charm! I'm grateful for my fellow impatient people. Time to unlock the Oneplus 6's true potential!
I try it to night
Thanks man, so far it works great!
This is a great rugged phone, perfect for the outdoors (I'm a keen mountaineer). I couldn't see a thread so I thought I would start one! A couple of posts re. rooting to follow....
Hey @dwastell, I know this thread is a couple months old, so I wanted to see if you have any root instructions?
Do you think the process for rooting the OUKITEL K13 here on the forum will work on the WP5?
Rooted!
Hi all,
I rooted my WP5. Sorry for not having time to write a full tutorial, only a concise story. Of course this is ONLY for experienced users...
My phone is 4GB version Android 10, build 10.0_V02_20200508.
1) download the firmware from oukitel website: https://oukitel.com/pages/download-center (1)
2) download and install SP Flash Tools https://spflashtool.com/download/
3) download and install Android Platform Tools https://developer.android.com/studio/releases/platform-tools
4) connect the phone to PC and verify that adb is working
5) WARNING: make a backup af your data!
6) unlock the bootloader:
- in Developer options enable the unlock
- adb reboot bootloader
- fastboot flashing unlock
- fastboot reboot
Now the phone restarts and is completely virgin!
7) shutdown the phone.
8) using SP Flash Tools readback the following partitions:
- boot
- recovery (2)
- vbmeta
9) download the attached patched_vbmeta.img
10) transfer the boot.img that you just readback to the phone download folder
11) install Magisk Manager (today 7.5.1)
12) Use Magisk Manager to patch the boot.img and copy back to PC
13) flash the images:
- fastboot flash --disable-verification vbmeta patched_vbmeta.img
- fastboot flash boot magisk_patched.img
- fastboot reboot
14) if the phone boots up run Magisk Manager to check if it's installed.
14b) if the phone goes in bootloop... flash back the original images you have read back (do not use the firmware you downloaded from Oukitel, it's necessary only to have the scatter file (the partition table).
Enjoy
Nicola
Notes:
(1) actually there are 2 firmware available and despite having different names are the same. This fw is Android 9.
(2) not used now but may be useful in the future
Rooting the WP5
totallybeachin said:
Hey @dwastell, I know this thread is a couple months old, so I wanted to see if you have any root instructions?
Do you think the process for rooting the OUKITEL K13 here on the forum will work on the WP5?
Click to expand...
Click to collapse
I eventually succeeded in rooting my WP5 with Magisk. For a while, the firmware was not available but once the official ROM was published, I managed to patch boot.img and install via fastboot. My phone is the 4 GB version -copies of the stock and patched boot image are available at: github.com/dwastell/Oukitel_WP5_magisk
I have experienced some complications as detailed in my next post...
Cheers, Dave
Rooting the WP5
Thanks for your post Nicola. You'll see that I did succeed in rooting my phone (Android 9) with Magisk, once I was able to get hold of the stock firmware. All is working though there are a couple of points worth noting.
The phones is SAR ("system-as-root") and the magisk instructions suggest that recovery.img is patched rather than boot.img. I proceeded by patching boot.img, as in your instructions, as this seemed a better solution - and it works fine.
One problem has occurred with updates. Magisk manager appears to assume that the recovery partition is the one that has been patched. When you do the direct install for the update, partition 2 is flashed (recovery) rather than partition 26 (boot). On rebooting the phone inevitably goes into boot loop.
To avoid this, I go for "select and patch a file" option, and then install again via fastboot as per the original installation. A bit of a hassle but better than the alternative!
Does this mean you were able to root the phone but revert to android 9? Both of you mention Android 9 in your posts.
vivekiny2k said:
Does this mean you were able to root the phone but revert to android 9? Both of you mention Android 9 in your posts.
Click to expand...
Click to collapse
No. No need to revert.
I rooted an Android 10. But cited the stock Android 9 only because the scatter file (ie. the partition table) is the same.
@dwastell rooted the Android 9.
Please read better my tutorial, if something is not clear... I'm here!
N
---------- Post added at 20:10 ---------- Previous post was at 19:59 ----------
dwastell said:
The phones is SAR ("system-as-root") and the magisk instructions suggest that recovery.img is patched rather than boot.img. I proceeded by patching boot.img, as in your instructions, as this seemed a better solution - and it works fine.
Click to expand...
Click to collapse
This phone is NOT a SAR. Neither Android 9 nor 10. The proof is that patching the boot.img worked!
One problem has occurred with updates.
Click to expand...
Click to collapse
Have you unrooted before applying the update?
Which kind of update? Not all are the same!
Android version
vivekiny2k said:
Does this mean you were able to root the phone but revert to android 9? Both of you mention Android 9 in your posts.
Click to expand...
Click to collapse
My phone was originally Android 9 so no reversion...
SAR
Both "Treble Check" and "Magisk Manager" confirm that the phone is SAR. I agree this is odd.... your thoughts?
The update I was referring to is the Magisk update, handled by Magisk Manager. Given that the phone is seen as SAR, it attempts to patch recovery.img, with an ensueing boot loop.
No, I don't unroot the phone
nicolap8 said:
No. No need to revert.
I rooted an Android 10. But cited the stock Android 9 only because the scatter file (ie. the partition table) is the same.
@dwastell rooted the Android 9.
Please read better my tutorial, if something is not clear... I'm here!
N
---------- Post added at 20:10 ---------- Previous post was at 19:59 ----------
This phone is NOT a SAR. Neither Android 9 nor 10. The proof is that patching the boot.img worked!
Have you unrooted before applying the update?
Which kind of update? Not all are the same!
Click to expand...
Click to collapse
Thanks Nicola for your tutorial. I'm eager to root my WP5 Pro with Magisk, but first I need a backup of boot vbmeta and recovery. I have made extensive use of SP Flash Tools but never to readback partitions so I'm having some problems here. Could you please detail your technique to extract such files? Thank you
Michele
Build number OUKITEL_WP5Pro_EEA_V01-20200624 CPU MT6762D, 8 cores,64 Gb ROM, 4 Gb RAM.
wallace108 said:
Thanks Nicola for your tutorial. I'm eager to root my WP5 Pro with Magisk, but first I need a backup of boot vbmeta and recovery. I have made extensive use of SP Flash Tools but never to readback partitions so I'm having some problems here. Could you please detail your technique to extract such files? Thank you
Michele
Build number OUKITEL_WP5Pro_EEA_V01-20200624 CPU MT6762D, 8 cores,64 Gb ROM, 4 Gb RAM.
Click to expand...
Click to collapse
Beware: your phone is different! So I don't know:
1) Android version.
2) which kind of booting are using, read here https://topjohnwu.github.io/Magisk/install.html#knowing-your-device
Before writing an image you MUST have a backup of it!
To read back a partition with SP Flash Tools you need to know the start address end the length of the partition. This information is available only (because your phone is not yet rooted) from the scatter file (from the SAME phone).
In the Readback page hit "Add" then input a name for the image file. Follows a new dialog "Readback block start address" where you have to write the values.
After this you can give the Read Back command. If it doesn't start shutdown the phone.
N
Thank you all for
the data to root! I just got a 4/32 android 10 version. Is there a custom recovery yet? Been a looooong time since I have dabbled but want to root it and customise. I have replaced most of google apps or disabled them already but want more room. I have never created a TWRP but have been reading about it and they already have many Oukitel versions, so should I wait? TIA
Thanks, it's clear.
I bought it for my son, don't have plans to root it yet. will probably wait till later.
nicolap8 said:
No. No need to revert.
I rooted an Android 10. But cited the stock Android 9 only because the scatter file (ie. the partition table) is the same.
@dwastell rooted the Android 9.
Please read better my tutorial, if something is not clear... I'm here!
Click to expand...
Click to collapse
No Joy with
Hardware : MT6761V/WE
Model : WP5
Build number : OUKITEL_WP5_NOEEA_V01_20200701
Build date UTC : 20200701-071441
Android v : 10
Baseband v: MOLY.LR12A.R3.MP.V114.9,MOLY.LR12A.R3.MP.V114.9
Kernel v : 4.9.190+ ([email protected]) (Android (5484270 based on r353983c) clang version 9.0.3 (based on LLVM 9.0.3svn)) #2 SMP Wed Jul 1 15:19:21 CST 2020
It seems locked down as I lose adb in fastboot and even patching the boot.img I create fails. MTKdroid tools can't create scatter.
vivekiny2k said:
I bought it for my son, don't have plans to root it yet. will probably wait till later.
Click to expand...
Click to collapse
Remember that you will lose ALL YOUR DATA! Usually it's better to root before start using the phone...
oncouch1 said:
No Joy with
Build number : OUKITEL_WP5_NOEEA_V01_20200701
It seems locked down as I lose adb in fastboot and even patching the boot.img I create fails. MTKdroid tools can't create scatter.
Click to expand...
Click to collapse
You have to describe well what you have done and error messages.
Note also that your firmware is never... maybe there is some difference.
N
As of today the firmware for the WP5 PRO has not been posted yet. I'll wait. Meanwhile I want to ask Nicolap8: what does the vbmeta file do? Why is it important to patch it. Isn't patching the boot enough? Thanks
TWRP for WP5 (Pie, 4GB)
If anyone wants to install TWRP, I've built and tested it for my WP5 (Android 9.0, 4GB). A copy of the image may be found in the MISC folder at: https://github.com/dwastell/TWRP_Oukitel_WP5
Note that the data partitiion is not accessible due to encryption (not a major limitation), and that the null version of vbmeta (thanks Nicola) does need to be flashed. Also, I have had problems flashing some versions of Magisk - please read the README.md.
nicolap8 said:
Remember that you will lose ALL YOUR DATA! Usually it's better to root before start using the phone...
You have to describe well what you have done and error messages.
Note also that your firmware is never... maybe there is some difference.
N
Click to expand...
Click to collapse
Sorry it has been a while I HAD WRONG USB DRIVERS! I got bootloader unlocked and will try again.
---------- Post added at 07:13 PM ---------- Previous post was at 07:09 PM ----------
A WP5 (android 10) .zip file is now on the site. It contains less files though?
For some reason the images taken in windows are corrupt. Magical fails to run on them. The one taken in llinux patches fine. One question though the original image is 32 meg the magical patches is only 10 meg is that correct? Also the vbmeta is 8 meg off the phone but the patches 256 k?
oncouch1 said:
For some reason the images taken in windows are corrupt. Magical fails to run on them. The one taken in llinux patches fine.
Click to expand...
Click to collapse
Strange but... with W all is possible!
One question though the original image is 32 meg the magical patches is only 10 meg is that correct? Also the vbmeta is 8 meg off the phone but the patches 256 k?
Click to expand...
Click to collapse
Both are correct.
The Magisk patched image is not "filled" to the partition size.
The vbmeta also is smaller because it's empty (is present only the "index").
N
Welcome to my latest Thread. Today for the Official Pixel Expierence Builds from the Official Website. This Guide does include the Installation of a custom Recovery which allows Factory Resets and flashing Updates/ROMs. Enjoy!
1. Download and prepare everything
First of all visit: https://developer.sony.com/file/dow...-aosp-android-10-0-kernel-4-14-kumano-latest/
And download the latest Software Binaries from Sony which You will need to flash together with the Boot Image (Kernel).
After that download the ROM File from here: https://download.pixelexperience.org/ and also download the "Recovery Image" which is a Kernel/Boot Image
Get the Magisk Manager Apk from here: https://github.com/topjohnwu/Magisk
Extract the Software Binaries to get the .img File from it.
2. Flash using Fastboot
After getting the Kernel/Boot Image do a patch with the Magisk Manager App (Your Phone doesn't needs to be rooted for that) (The Output File will get called magisk_patched,img from now)
Flash the Software Binaries from SONY with:
Code:
fastboot flash oem_a SW_binaries_for_Xperia_Android...............img
Repeat that step with:
Code:
fastboot flash oem_b SW_binaries_for_Xperia_Android...............img
Now flash the Kernel You got from the Magisk Manager with:
Code:
fastboot flash boot_a magisk_patched.img
And repeat that again for the Second Slot:
Code:
fastboot flash boot_b magisk_patched.img
3. Install using a SD Card or ADB
After flashing the Kernel. Turn Off Your Device and hold the Volume- (Lower) Button together with the Power Button until You see the SONY Logo. Release both Buttons and wait for the Recovery coming up.
Search now for the Apply Update Option and select based on Your preference the ADB or SD Card Method to flash the ROM. Connect Your Xperia to Your PC again and enter:
Code:
adb sideload filename.zip
(In case of using the ADB Method)
Your Device should now flash the selected ZIP File (In our case the Pixel Expierence ROM).
4. Profit
Wipe Your Device now using the Factory Reset of the Recovery. Install the Magisk Patched Kernel Image again using the commands of the second Step of this Guide to keep Magisk functional. Connect Your Phone to a Charger and install the latest Magisk Manager to Your Phone. That's it! Enjoy
What Works:
VoLTE
Wifi Calls
Video Calls over Carrier
Camera Button (Does not start Camera Apps)
Everything!?
Bugs:
None!?
Do you feel some animation lag
Sketch. said:
Do you feel some animation lag
Click to expand...
Click to collapse
Yes. I think there is some Kernel Panic. Not sure but battery life could also be better right?
Think I can fix some stuff with MARS pretty soon.
Google Camera works just fine from Urnyx btw. First Time we can use GCAM 7.x fully!
Link: https://www.celsoazevedo.com/files/android/google-camera/f/changelog1343/#google_vignette
Are all functions of gcam work normally ? (like HDR+,Night sight,Astrophotography mode )
This guide is too difficult for inexperienced users, please make a guide on your youtube Channel, miustone. We need your help!
naygnosuw said:
Are all functions of gcam work normally ? (like HDR+,Night sight,Astrophotography mode )
Click to expand...
Click to collapse
Almost. Astro isn't available. 4K 60FPs Kills the App (don't toggle the 60FPS Button on 4K)
Tabike said:
This guide is too difficult for inexperienced users, please make a guide on your youtube Channel, miustone. We need your help!
Click to expand...
Click to collapse
It feels so simple but I got You. I'm still not sure how I should do it. I have a PC, a Chromebook and a Xperia 5 for recording. While the Xperia needs to get flashed (not usable as Camera). I could make a Video with My Chromebook maybe in 720p and combine it with Screen recording somehow. I'm not a YouTuber but I will give it a shot this week... Promised!
Xperia 1 - J8110, J8170, J9110, 802SO, SO-03L, SOV40 variants - what are they?
and what variant PE Rom support official?
Updated the Guide.
@JOKER.SOHA It's printed on the back of Your Xperia (Bottom). Model Numbers... Choose the right one for You. Don't understand the rest of Your question... Sorry
我没有移动数据。
未检测到SIM卡。
MOD EDIT: Please post only in English according to the FORUM RULES or at least add an English translation below your foreign language(Google translator for example), translation added below:
I don't have mobile data.
The SIM card was not detected.
Looks promising will try after the battery drain/lag is fixed. Also will this room be maintained or is it just take it how it is? Great work either way!
Term1nator3000 said:
Looks promising will try after the battery drain/lag is fixed. Also will this room be maintained or is it just take it how it is? Great work either way!
Click to expand...
Click to collapse
Yeah the drain sucks, but great ROM so far. I'm satisfied and use it as daily driver. You can find the Device Maintainers over the Pixel Expierence Website. This is just a Guide Thread since we don't have TWRP. So the Maintainer is free to open up a official Development Thread but they haven't yet... Someone could ask maybe, it's just copy and paste and would help to talk about Bugs and such
Miustone said:
Yeah the drain sucks, but great ROM so far. I'm satisfied and use it as daily driver. You can find the Device Maintainers over the Pixel Expierence Website. This is just a Guide Thread since we don't have TWRP. So the Maintainer is free to open up a official Development Thread but they haven't yet... Someone could ask maybe, it's just copy and paste and would help to talk about Bugs and such
Click to expand...
Click to collapse
Ahh okay np. Hopefully things will smooth out.
I found PixelExperience's J9110 Install Step and did some comparison.
(Sorry I'm not allowed to post a link by now, but it's easy to find on PE's website.)
PE's install step mentioned that flash PE need to unlocked BL, but your guide didn't mention.
And your guide have a kernel flash step, but PE's install tutorial missing this.
Here is my question:
Is it necessary to unlock the BL? (Because I did this to my old Xperia XZ once, there's a LOT problem for me lol)
Is it necessary to flash latest kernel?
Thanks in advance.
ceplavia said:
I found PixelExperience's J9110 Install Step and did some comparison.
(Sorry I'm not allowed to post a link by now, but it's easy to find on PE's website.)
PE's install step mentioned that flash PE need to unlocked BL, but your guide didn't mention.
And your guide have a kernel flash step, but PE's install tutorial missing this.
Here is my question:
Is it necessary to unlock the BL? (Because I did this to my old Xperia XZ once, there's a LOT problem for me lol)
Is it necessary to flash latest kernel?
Thanks in advance.
Click to expand...
Click to collapse
It isn't possible to flash anything besides Stock in Flashmode with a locked Bootloader. That's one of the Basic Things on Android. That's why it isn't mentioned here... You should carefully learn how everything works before thinking about to flash anything on Your Device...
The Pixel Expierence Guides for Xperias are wrong and do Not Work btw. That's the reason for My Guides...
Best Regards
Miustone said:
Yes. I think there is some Kernel Panic. Not sure but battery life could also be better right?
Think I can fix some stuff with MARS pretty soon.
Google Camera works just fine from Urnyx btw. First Time we can use GCAM 7.x fully!
Link: https://www.celsoazevedo.com/files/android/google-camera/f/changelog1343/#google_vignette
Click to expand...
Click to collapse
Hi, rom maintainer here, just to precise that a kernel panic would totally freeze your phone and you'll be unable to do anything except force reboot your phone.
Also, responding on another thing I saw on this thread, the only reason I don't open an xda thread per device supported is that I would have to update like 25 threads every month, respond the same questions for all those threads over and over etc
I have my telegram for that t.me/PixelExperienceSony
I might do 1 thread for all devices in cross platform dev section.
Cheers
can someone please make a step by step YouTube YouTube guide? I tried to follow the instructions with little sucess
Totally missed the dtbo.img flashing which prevents the Device from booting. You will need that Tool: https://androidfilehost.com/?fid=818070582850510260
To extract the payload.bin file inside of the Pixel Expierence Zips. Put the Payload Bin in the Input Folder and Start the Exe to extract the Bin File. You will get a dtbo.img file which you will need to flash like:
fastboot flash dtbo_a dtbo.img
fastboot flash dtbo_b dtbo.img
Together with the boot/magisk Images which will allow You to boot into the Recovery Mode by holding VolumeDOWN & the Power Button
Enjoy and sorry for the trouble! I will also update this Threads next just like My Rooting Threads.
Miustone said:
Totally missed the dtbo.img flashing which prevents the Device from booting. You will need that Tool: https://androidfilehost.com/?fid=818070582850510260
To extract the payload.bin file inside of the Pixel Expierence Zips. Put the Payload Bin in the Input Folder and Start the Exe to extract the Bin File. You will get a dtbo.img file which you will need to flash like:
fastboot flash dtbo_a dtbo.img
fastboot flash dtbo_b dtbo.img
Together with the boot/magisk Images which will allow You to boot into the Recovery Mode by holding VolumeDOWN & the Power Button
Enjoy and sorry for the trouble! I will also update this Threads next just like My Rooting Threads.
Click to expand...
Click to collapse
bro can you share the steps how to install.
do i need python to run the payload extract?
i cant flash the rom and cant use the phone, loop in the boot 5sec will restart ..
VOLTE not working in india with JIO network...
Were you able to get the Volte working on Indian networks?.
Self explaining :highfive:
mods please keep it up until a reference is shown to inspire writers with good wills:angel::fingers-crossed:
2B_4G10 said:
Self explaining :highfive:
Click to expand...
Click to collapse
1. Unlock bootloader via MiUnlock software for PC (you have to wait at least 168 hours)
2. Flash TWRP recovery img via fastboot
3. Download and put into internal memory magisk.zip installer (you need version 20.4 or newer)
4. Install this zip via TWRP
5. Boot into the system and download Magisk Manager apk (version 8.0.3 or newer) then install it.
6. Voilà. That's all [emoji106]
zencooler said:
1. Unlock bootloader via MiUnlock software for PC (you have to wait at least 168 hours)
2. Flash TWRP recovery img via fastboot
3. Download and put into internal memory magisk.zip installer (you need version 20.4 or newer)
4. Install this zip via TWRP
5. Boot into the system and download Magisk Manager apk (version 8.0.3 or newer) then install it.
6. Voilà. That's all [emoji106]
Click to expand...
Click to collapse
Thanks! i found the basics but i couldn't find a proper TWRP version out there, and the ROMs too, isn't there a legit source to get em?
2B_4G10 said:
Thanks! i found the basics but i couldn't find a proper TWRP version out there, and the ROMs too, isn't there a legit source to get em?
Click to expand...
Click to collapse
I do not remember where I found the correct sources so I will upload these files for you into wetransfer in few minutes.
EDIT: here you are: https://we.tl/t-xTbsJVTtzA
Putting your post in large bold letters makes you look like a troll, not like you have an urgent issue.
Firmware, http://mifirm.net, twrp at the same place
How to root:
You have two options for this, 1 is the recommended way and 2 is the lazy but works way.
Option 1 (RECOMMENDED):
Download the latest factory image from: https://developers.google.com/android/images#cheetah (at the time of writing this, it's TD1A.220804.031
Unlock bootloader (If you don't know how to do this, do not proceed further)
From the downloaded image file, extract the init_boot.img file and copy it to your phone (directory shouldn't matter)
Install the Magisk apk from: https://raw.githubusercontent.com/topjohnwu/magisk-files/canary/app-release.apk
Launch the app, select install, patch a file, select the init_boot file you placed in your phone
After it's done, it should place a file in your phone's download folder called magisk_patched-<VERSION>_<XYXYXYXYXY>.img
Copy that over to your PC and now boot to bootloader
Run the following commands from Powershell/commandline:
Code:
fastboot flash init_boot magisk_init_patched-25205_EfWOu.img
And then reboot, you'll be rooted
Option 2 (LAZY BUT WORKS):
I'm sharing my magisk patched init_boot from the TD1A.220804.031 build (post 73MB update). Instructions are:
Unlock bootloader (If you don't know how to do this, do not proceed further)
Boot to bootloader
Download the patched init_boot from: https://sourceforge.net/projects/ag.../magisk_init_patched-25205_EfWOu.img/download
Run the following commands from Powershell/commandline:
Code:
fastboot flash init_boot magisk_init_patched-25205_EfWOu.img
And then reboot, you'll be rooted
Install Magisk apk from here: https://raw.githubusercontent.com/topjohnwu/magisk-files/canary/app-release.apk
To get SafteyNet working:
Open the Magisk app
Open the settings from top right, Enable Zygisk
Reboot
Flash the MODIFIED SafteyNet fix module by @kdrag0n from the attached files on this thread from within Magisk Modules
Clear Play store data and you should be good!
Voila!
FASTBOOT IMAGES:
I'm sharing the stock extracted images of the TD1A.220804.031 build, should be a good reset point from fastboot incase any of you get stuck somehwere:
DO NOT MIRROR THIS PLEASE!!!!
VERIFY THE MD5 OF THE FILE AFTER DOWNLOADING!!!!!!!
Mirror 1 | Mirror 2
MD5: 43613f520697722840ded6a15eb27459
Massive shoutout to @Some_Random_Username for Mirror 1 and @akhilnarang for Mirror 2 since SourceForge was facing issues!
Now documentation on how to do it yourself (which I'd highly recommend since you should never trust any file given, always try to do it yourself!):
How to dump your own device:
1. Download a GSI which is userdebug/eng and equal/newer Security Patch of the current build on your device from any of the unofficial community builds here: https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
2. Install the DSU Sideloader app from: https://github.com/VegaBobo/DSU-Sideloader/releases/latest
3. Follow instructions in the DSU sideloader app readme here: https://github.com/VegaBobo/DSU-Sideloader/blob/master/README.md
I'd recommend enabling the userdata toggle and typing 32GB as the size
4. Reboot into the DSU from the notification
5. When the device boots up, type the following in the terminal:
Code:
adb root
adb shell
mkdir -p /sdcard/dump
for file in /dev/block/bootdevice/by-name/*; do
if [ "${file##*/}" != "userdata" ]
then
echo Dumping "${file##*/}"
dd if=$file of=/sdcard/dump/"${file##*/}".img
fi
done
6. Once the dump is done, you'll have files in /sdcard/dump/
7. Copy those over to a PC
8. Voila
A massive thanks to @AndyYan @Some_Random_Username for their help (well hand holding) throughout the entire process <3
Also thanks to @OmkarTheAndroid for the re-brush up of the Android basics I forgot
Reserved
Thanks!
Have you had any luck with SafetyNet yet? People on another thread are saying that even the Modded version by @Displax isn't working on P7P with Canary Magisk
I'd like to remind all that, 1) the DSU method requires some Android/shell knowledge to correctly carry out, and 2) you're discouraged from actually flashing/using those GSIs (TD-based Android 13 GSIs are still in early phase, and P7/P will almost certainly get proper, fully functional device-specific ROMs shortly anyway).
Thanks for the dump! Could you maybe mirror it yourself to be sure? At least until Google's facory images are up Sourceforge is incredibly slow for me (and probably for others too).
so looks like vendor_dlkm has been replaced by vendor_kernel_boot and the init_boot is just the first-stage init. This will be interesting moving forward with AVB and custom images. I will start working on something when source drops. I will likely need to have some testers to see how much this requires to get a custom image up and running.
EDIT: vendor_boot is actually the one that has been separated out a bit between vendor_boot (holding modules) and vendor_kernel_boot, which has some ramdisk stuff like the vendor_boot has on Pixel 6 devices.
Kernel now consists of 6 images. init_boot, vendor_boot, vendor_kernel_boot, vendor_dlkm, dtbo and boot.img
I downloaded the init_boot.img file then got a big problem bricked my pixel 7 oro
mrteii1 said:
I downloaded the init_boot.img file then got a big problem bricked my pixel 7 oro
Click to expand...
Click to collapse
this is a soft brick, just flash the correct partition back using the stock image
Tahnks forbyour reply. How to get the stock image? Now it brickes. Im panicking
I think i'll hold fire on rooting until things are a little clearer. unlocking the bootloader in the usual fashion should be ok tho right?
whatsisnametake2 said:
I think i'll hold fire on rooting until things are a little clearer. unlocking the bootloader in the usual fashion should be ok tho right?
Click to expand...
Click to collapse
Yes, unlocking the bootloader is still the same and will wipe data.
Current SafetyNet Status (with modded universal SafetyNet Fix + Magisk Props):
Play Integrity API Checker:
MEETS_DEVICE_INTEGRITY: fail
MEETS_BASIC_INTEGRITY: pass
MEETS_STRONG_INTEGRITY: fail
YASNAC:
Basic integrity: pass
CTS profile match: fail
Edit: GPay does work on the Pixel Watch, even though it doesn't on the phone (when rooted).
Make sure to add your cards there if you're using the Pixel Watch and can't use GPay on your phone.
zetsumeikuro said:
Yes, unlocking the bootloader is still the same and will wipe data.
Click to expand...
Click to collapse
If you can boot to recovery try a factory reset from there or you will have to power it off and wait until Google releases the image.
mrteii1 said:
Tahnks forbyour reply. How to get the stock image? Now it brickes. Im panicking
Click to expand...
Click to collapse
In the OP, the part with:
"FASTBOOT IMAGES:
I'm sharing the stock extracted images of the TD1A.220804.031 build, should be a good reset point from fastboot incase any of you get stuck somehwere:
DO NOT MIRROR THIS PLEASE!!!!"
Misterxtc said:
If you can boot to recovery try a factory reset from there or you will have to power it off and wait until Google releases the image.
Click to expand...
Click to collapse
? unlocking is just going to do a data wipe/factory reset anyway. not sure why I would need the factory image for that? or to do an additional factory reset from recovery?
Misterxtc said:
If you can boot to recovery try a factory reset from there or you will have to power it off and wait until Google releases the image.
Click to expand...
Click to collapse
Maybe you replied to the wrong user?
Hey everyone, a slight update on the website for the image dump, SourceForge was giving people incomplete files so @Some_Random_Username is generously hosting it on his servers <3
please verify the MD5 of the downloaded zip before trying to modify any parititons using the following commands:
On windows:
Code:
certutil -hashfile cheetah-TD1A.220804.031-compressed.zip MD5
On Linux/MacOS:
Code:
md5sum cheetah-TD1A.220804.031-compressed.zip
The MD5 should be: 43613f520697722840ded6a15eb27459
whatsisnametake2 said:
? unlocking is just going to do a data wipe/factory reset anyway. not sure why I would need the factory image for that? or to do an additional factory reset from recovery?
Click to expand...
Click to collapse
I was thinking the reset would force it to boot off the other slot.