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
Related
I have a Cubot Cheetah 2 with Nougat (7.0) [build CUBOT_6143C_CHEETAH_2_V15_20170623].
I have managed to unlock the bootloader (and confirmed it is unlocked) and was hoping to use the following
"Fastboot boot TWRP.img"
to open and use TWRP to take a pre-root copy of my phone without flashing and then proceed to flash TWRP and then Root it.
I have tried several copies of TWRP 3.0 (supposedly for a Cubot Cheetah 2) extracting image files from the zip or rar files and running Fastboot as above. In all cases I get the following message;
downloading 'boot.img'...
OKAY [ 0.931s]
booting...
FAILED (remote: invalid kernel address: not lie in memory)
finished. total time: 0.947s
Understandably the time taken varies a little each time but I'm unable to understand why files intended for the Cheetah 2 do not work. If this will not work using the Fastboot boot option, I suspect it will not work with flash option.
Can anyone help me please.
Thanks.
TWRP and Rooting a Cubot Cheetah 2 (Nougat)
Android_Dog_Walker said:
I have a Cubot Cheetah 2 with Nougat (7.0) [build CUBOT_6143C_CHEETAH_2_V15_20170623].
I have managed to unlock the bootloader (and confirmed it is unlocked) and was hoping to use the following
"Fastboot boot TWRP.img"
to open and use TWRP to take a pre-root copy of my phone without flashing and then proceed to flash TWRP and then Root it.
I have tried several copies of TWRP 3.0 (supposedly for a Cubot Cheetah 2) extracting image files from the zip or rar files and running Fastboot as above. In all cases I get the following message;
downloading 'boot.img'...
OKAY [ 0.931s]
booting...
FAILED (remote: invalid kernel address: not lie in memory)
finished. total time: 0.947s
Understandably the time taken varies a little each time but I'm unable to understand why files intended for the Cheetah 2 do not work. If this will not work using the Fastboot boot option, I suspect it will not work with flash option.
Can anyone help me please.
Thanks.
Click to expand...
Click to collapse
I have done a lot of searching and found the following;
a) Fastboot boot recovery.img does not work on this phone, There may be some Kernel options required to be passed but I cannot find them,
b) Flashing MDSTWRP_3.0.2-7ES_Cubot_Cheetah2 from Needrom, flashes ok by either using "SP Flash tool" or "Fastboot flash recovery recovery image", but when you start the phone or reboot using "Fastboot reboot" and enter recovery, the stock rom has overwritten it. I have tried multiple flashes and erasing the partition first with no success.
The above appear to mean that I cannot use TWRP (or other Custom recovery) and so cannot install the SuperSu.zip. I have raised this on Needrom with TWRP creator who cannot offer a solution.
Before I try using an app, I'd like to ask if anyone has a solution to stop recovery being overwritten. (I have been unable to find a pre rooted image or an image containing TWRP).
Thanks
Solution Found.....The file available from NeedROM will not work with Nougat on a Cheetah 2.
rebuilt MDSTWRP_3.0.2-7ES_Cubot_Cheetah2 using Carliv Image Kitchen and the Nougat stock rom Recovery and.... the Fastboot boot recovery.img works. I will confirm if the flashing option works during the next couple of days, but this helps understanding of why earlier attempts failed.
The Cubot Cheetah 2 gives no error messages if you are trying to start an incompatible recovery file, it just overwrites recovery with stock recovery and opens that.
This thread can now be closed
I confirm that my modified version works (flash or boot). I do not know how to modify the version info yet, so I cannot publish it.
Any idea on when you might be able to post some info on the modified build? Or even some instructions for us to try and follow your lead?
I would be happy to share my version but I am concerned that it is a ported version based on the current version in Needrom created by MDSdev and the opening screens reflect that ROM build info. If someone would advise me what the rules are regarding this I am happy to change it and then publish.
Alternatively I could finish writing out the process (already started) I went through so that I have a record and others can use it to port their own version, but each version created will also reflect MDSdev's original configuration information and this does not sit well as they did the hard bit of configuring TWRP to work with Cubot Cheetah 2 hardware and earlier Android (6.0/6.1). All I have done is get it working on a Nougat(7.0) version of the Cheetah 2. Advice from an expert in these matters would be helpful.
Gotcha, hopefully someone will
chime in, I would hope given the nature of xda, as long as those who input are acknowledged and recognised all should be well....
Cubot Cheetah 2 Android 7 Root by EpicFail2017
Hi Guys i have a Cubot Cheetah 2 Android 7.
Sorry my english sucks realy!
I found only a soulution to Root it with Magisk 14.2 beta!
1 First Step Download only PC Flash Files V14 170719 and unpack it !
http://forum.cubot.net/viewtopic.php?f=21&t=1475
The ROM this FilePC Flash Files V14 170719
https://mega.nz/#F!YIt2UKLL!E2PGw3IJ_KeCuVwXhstdFw
------------------------------------------------------------------------------------------------------------
2 Step Download and Install last version!
http://spflashtools.com/windows/sp-flash-tool-v5-1728
------------------------------------------------------------------------------------------------------------
3. Step
Download Magisk v14.2 Beta and Magisk Manager Version: v5.3.0, pu it on your SDCard!
Latest Stable Magisk Version: v14.2
Latest Magisk Manager Version: v5.3.5
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
----------------------------------------------------------------------------------------------------------------------------
4 Step
Download and unzip my Patched boot.img ,then Replace the boot.img in Folder from Step 1 !
https://mega.nz/fm/Q6YV3QrZ
http://www117.zippyshare.com/v/EiwE8p57/file.html
----------------------------------------------------------------------------------------------------------------------------
5 Step
Flash with SpFlash the Rom from Step 1 in Format +Download Mode.
Make a backup first from all your Stuff and Apps!
---------------------------------------------------------------------------------------------------------
6 Step
Start Android and make dev option enabel. Usb debug etc!
Install Latest Magisk Manager Version: v5.3.5 from SdCard!
Start and make under Options update beta kanal!
Install Magisk 14.2 Beta and rebot your Phone!
Wolla you have Root this ***** !
---------------------------------------------------------------
7 Step
Download Maui META ver 9.1724.0.00 to fix The Invalid Imei Problem after flashing!
For me this step was need after flashing root+room!
https://www.needrom.com/download/mauimeta-version-9-1724/
Mfg
EpicFail2017
Any idea why the IMEI might get lost? I'm aware that that can happen in mediatek stuff with custom, but is this due to a binary check of boot.img or one of the other ROMS? Or is it the spflash util acting up because of boot.img?
I've two of these phones at the min, one of them already has some issues so don't want to play with that one as of yet - power on issues and fingerprint sensor seems to act up - anyone else?
I'm already on nougat, and your procedure is exactly the same as I was thinking (already patched boot.img using magisk 14.0 but maybe I need use the beta as you did). I didn't get to the flashing of boot.img as I'm more comfortable doing flashing the partition straight from PC (adb/fastboot etc). I'm guessing mediatek can only be flashed safely with sptool? Do we need to reflash ALL partitions as IF we can, flashing boot.img to an upgraded phone should work without loss of data/imei? maybe?
What is the 'R' near the signal in your screenshots?
I'll answer my own questions with a way to root The Cubot Cheetah 2 (Nougat) in just a few minutes ..
I was already on the same version of nougat as the download before I started.
1. Download the ROM shown above and extract, grab the SPFlash too and the drivers. Ensure unknown sources is ticked, unlock bootloader - I also disabled pin security etc (dunno if this was needed).
* Note, install the drivers with the phone NOT connected via USB.
2. Transfer the boot.img to your phone and run it through Magisk (I used the beta 14.2 as documented above and manager 5.35), patch the image file (boot.img)
3. Move the patched boot.img from the magisk folder back to the computer.
4. Run the SPFlash tool load the scatter file, select DOWNLOAD and untick everything asides from boot.img
5. With phone switched off, connect it via USB
Flash
Wait until complete
Reboot
Rooted
No loss of IMEI or data.
It's good to see some responses. I seemed to struggle with TWRP and rooting for a while and now several options are apparently available. My personal opinion (I would say this wouldn't I!) is that if I can get advice on publishing/sharing the working version of TWRP on Cubot Cheetah 2, it is really simple to root the device by flashing TWRP, copy latest version of Supers.zip onto to SD card, open phone in recovery (Which is now TWRP), set English as default language (a one time action), install the Supers.zip. Job done, rooted with the best SuperSu facilities and an industry recognised backup facilities.
Unfortunately I have not yet had any advice on how to version the Nougat version from anyone on XDA yet and I am looking at trying to get MDSdev (the Cheetah 2 Marshmallow TWRP developer) to adopt the Nougat version.
That was my worry, not sure of compatibility of TWRP or boot time stuff on the mediatek devices. Rooting is now very very simple with the previous instructions, I was thinking flashfire or flashify or similar to push recovery onto the recovery partition but it's making sure TWRP is aware of the partitions. 10 years ago I'd have had a good look through the sourcecode for any possible problems but simply don't have the time these days :/
Love the phone but was put off using it as my primary phone due to lack of root. Okay I had to install stuff on the computer to flash this, but it's turned out it's very very easy and seems very safe too!
You may like to note that MDSdev have now published a new version of TWRP that works on Nougat (this is also a later version of TWRP).
https://www.needrom.com/download/twrp-3-1-1-1-mdsdev/
Android_Dog_Walker said:
You may like to note that MDSdev have now published a new version of TWRP that works on Nougat (this is also a later version of TWRP).
https://www.needrom.com/download/twrp-3-1-1-1-mdsdev/
Click to expand...
Click to collapse
EpicFail2017 said:
Hi Guys i have a Cubot Cheetah 2 Android 7.
Sorry my english sucks realy!
I found only a soulution to Root it with Magisk 14.2 beta!
1 First Step Download only PC Flash Files V14 170719 and unpack it !
http://forum.cubot.net/viewtopic.php?f=21&t=1475
The ROM this FilePC Flash Files V14 170719
https://mega.nz/#F!YIt2UKLL!E2PGw3IJ_KeCuVwXhstdFw
------------------------------------------------------------------------------------------------------------
2 Step Download and Install last version!
http://spflashtools.com/windows/sp-flash-tool-v5-1728
------------------------------------------------------------------------------------------------------------
3. Step
Download Magisk v14.2 Beta and Magisk Manager Version: v5.3.0, pu it on your SDCard!
Latest Stable Magisk Version: v14.2
Latest Magisk Manager Version: v5.3.5
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
----------------------------------------------------------------------------------------------------------------------------
4 Step
Download and unzip my Patched boot.img ,then Replace the boot.img in Folder from Step 1 !
https://mega.nz/fm/Q6YV3QrZ
http://www117.zippyshare.com/v/EiwE8p57/file.html
----------------------------------------------------------------------------------------------------------------------------
5 Step
Flash with SpFlash the Rom from Step 1 in Format +Download Mode.
Make a backup first from all your Stuff and Apps!
---------------------------------------------------------------------------------------------------------
6 Step
Start Android and make dev option enabel. Usb debug etc!
Install Latest Magisk Manager Version: v5.3.5 from SdCard!
Start and make under Options update beta kanal!
Install Magisk 14.2 Beta and rebot your Phone!
Wolla you have Root this ***** !
---------------------------------------------------------------
7 Step
Download Maui META ver 9.1724.0.00 to fix The Invalid Imei Problem after flashing!
For me this step was need after flashing root+room!
https://www.needrom.com/download/mauimeta-version-9-1724/
Mfg
EpicFail2017
Click to expand...
Click to collapse
Anyone uploading a mirror of nougat TWRP, please.
Also i´m kind of shy flashing the recovery with patched boot.img, any experience?
Someone with nougat and superSU here? Magisk seems to have some errors with some xposed moduls duo lag of "su-root-floder"
Do you password protect your recovery?
I have now tried the Magisk and TWRP routes to achieve rooting. My preference is the TWRP route because it has the fewest steps and works!.
An point worth noting is that if you are a new user on needrom, you need to register using Chrome, Firefox or other non Microsoft browser. Once registered Microsoft Edge works. I don't know why the registration with Edge fails but It is annoying when you complete the process and do not get the registration e-mail. Without registering you cannot get the TWRP download referenced above.
Hi,
Everything seems fine except if i make a wipe of dalvik cache every app stop working. The only solution is to wipe data or flash rom again with flashtool.
any can fix it on TWRP 3.1.1.1 ?
EpicFail i´m not sure, maybe security related issue. Instead of flashing rom i prefer restore backup^^
Still did not find a public nougat TWRP download
Both old 6.0 twrp freeze if timer is set and screen is going to turn off. Isn´t an issue anymore?
Today i hardly crashed system, it was in relation to magisk modul (busybox) update issue https://forum.xda-developers.com/apps/magisk/module-canstantly-module-updated-reboot-t3696943
EDIT: switched to supersu, busybox now working
Yesterday xposed appsops was getting a fix it is still unoffical
https://forum.xda-developers.com/xposed/modules/xposed-appopsxposed-appops-4-3-t2564865/page89
Edit:
updated to magisks unoffical xposed framework 3.1.4
DISCLAIMER: I'm not responsible for anything that happens to your device. Use the steps below at your own risk . Be mindful of the facts unlocking bootloader voids your warranty and also hard resets your device - ALL YOUR DATA, SETTINGS, FILES AND APPS WILL BE DELETED. Rooting your device voids warranty as well. I own the Chinese SHT-AL09 8.4" LTE device and tested this root procedure ONLY WITH THIS MODEL. However, I believe there is a good chance the steps below will work for all other models of MediaPad M5, including WiFi only variants and 10" models. You MUST unlock your bootloader first. Do NOT use ramdisk image I provide in the steps below for any other model besides SHT-AL09 - doing so is guaranteed to render your device unusable. Ramdisk I provided is ONLY for SHT-AL09. You will need to extract your own ramdisk from stock firmware, specific to your device model
Credits:
@Wirmpolter - this root method largely based on his Magisk guide for Mate 9
@topjohnwu for creating the awesome Magisk Manager, which was used to patch ramdisk image with superuser binary
People, who created HuaweiUpdateExtractor
@magnumlove who pointed me in the right for developing root method in this post
This site, for hosting stock firmware for Huawei MediaPad M5
1. First, you will need to unlock the bootloader of your M5. Follow this guide
2. Transfer this patched ramdisk image to your device
Note for users with version of M5 other than SHT-AL09: Do NOT use the above ramdisk image. Download the full stock rom (update.zip) from the site I linked in the credits. Extract UPDATE.APP file from the zip. Then use HuaweiUpdateExtractor to extract ramdisk.img specific to your device. If you get errors in HuaweiUpdateExtractor - uncheck first 2 checkboxes for checksum verification on Settings tab and try again
3. Once bootloader is unlocked, install latest Magisk Manager from the official Magisk thread
4. Once Magisk Manager gives you a pop-up prompt to either download Magisk zip or patch the boot image file - chose to patch the boot image, but instead of boot.img select ramdisk.img from step 2. Magisk Manager should give you a message the image was successfully patched. It will be saved as patched_boot.img in MagiskManager folder on your sdcard. If it does not say success - do NOT proceed
5. Transfer the newly created patched_boot.img back to your PC
6. If you already have ADB and Fastboot tools installed on your PC you can just use what you've got. If not - get them from here
7. Connect your M5 to PC via USB cable
8. Run command prompt. If your ADB and Fastboot are installed as system app - you can do this from any path in CMD. If not - you need to switch in CMD to your ADB and Fastboot folder. Either way, the patched ramdisk patched_boot.img file must be in the same path, from which you will be running commands below in CMD window
9. Type "adb " in CMD window to start android debug bridge
10. Type "adb reboot-bootloader" and wait until your device restarts in Download mode
11. Once in Download mode, type "fastboot flash ramdisk patched_boot.img" - you should see some output from flash procedure, indicating successful flash
12. Once patched ramdisk is flashed, type "fastboot reboot"
That is it - you're done. Once your device reboots it will be rooted.
Note 1: Magisk Manager has it's own built-in superuser app and uses Systemless root, which works completely differently - you will not see external, standalone app like SuperSU or SU you might be familiar with in your App Drawer. The way to control the superuser app is from Magisk Manager itself: Settings->Superuser section
Note 2: I don't do tech support via PM, so don't PM me for help or with questions. Use the thread instead, and some other XDA members or myself will probably help you. Good luck!
Note 3: You may find some links to Huawei stock firmware in the 2nd post
UPDATE - August 6, 2018
Huawei officially approved 8.0.0.171 firmware with GPU Turbo for installation on SHT-AL09 devices. If you're doing first time root - just follow the original steps above. If you are already rooted and want to upgrade to 8.0.0.171 - follow the steps below:
1. Boot into download mode:
Code:
adb reboot-bootloader
from CMD window
2. Flash stock recovery from 8.0.0.171 to your device in fastboot:
Code:
fastboot flash recovery_ramdisk recovery_ramdis.img
3. Download and install the official OTA through Settings (full or just the update)
4. Boot into download mode again and flash patched ramdisk from 8.0.0.171
Code:
fastboot flash ramdisk patched_boot.img
5. OPTIONAL: If you were using TWRP or any custom recovery - you will need to reflash it back
Code:
fastboot flash recovery_ramdisk twrp.img
or whatever you named your custom recovery image
REMINDER: Do NOT use ramdisk image I provided for any other model besides SHT-AL09 - doing so is guaranteed to render your device unusable. This patched ramdisk is ONLY for SHT-AL09. You will need to extract your own ramdisk from stock firmware, specific to your device model
Needless to say, all the images you are going to flash must reside in the same directory, from which you are going to be running the CMD commands. If your ADB/Fastboot folder is not in your WIndows' PATH environmental variable - the images must be placed in the same folder where ADB/Fastboot binaries are, and CMD commands must be run from that folder.
C5Longhorn said:
Yes, they still work. I have the same model and build as you and I'm rooted.
Sent from my Pixel 3 XL using Tapatalk
Click to expand...
Click to collapse
I'm considering buying an SHT-W09 with firmware version 8.0.0.200 (C567), but I'd like to know if I can root it first. I do not know if the bootloader has been unlocked. Since you have the same version, can you confirm that it's possible to unlock and root, and if so, sketch out how it's done? I'm confused about whether it's possible with this firmware.
samiller said:
I'm considering buying an SHT-W09 with firmware version 8.0.0.200 (C567), but I'd like to know if I can root it first. I do not know if the bootloader has been unlocked. Since you have the same version, can you confirm that it's possible to unlock and root, and if so, sketch out how it's done? I'm confused about whether it's possible with this firmware.
Click to expand...
Click to collapse
Unlocking is possible *only* if you've gotten already your unlock code. As this service was suspended about 2 years ago there is no easy way to get it unlocked.
Small request to developers, or people with access to reliable file hosting: I don't have a developer account, so all the files I linked or referenced in the OP are hosted on free hosting sites. That file hosting has expiration date and max downloads limit, so the files will become inaccessible sooner rather than later. Please upload these files to reliable hosting and create a post with the links. I will link your post in the OP as a mirror.
In the meantime, mirror for SHT-W09 firmware: https://mega.nz/#!asVjmZrR!bW2OmXgTjnyVN4pqb9fA7OzAJ4bzil7YZxNW14qoCmk
I can confirm that this works on the 10.8" wifi model using the devices relevant ramdisk.img.
Hello, can somebody test sixaxis controller tool with root and magisk? There is a Trial in Google Play Store, that is called sixaxis compatibility checker without purchise the App. Maybe i want to buy the Tablet, but only with Dualshock 4 Support...
Just a heads up, been following threads on this forum for flashing a GSI. Now that you guys can root, you can also make backups of your own stock system image if you can't find one from Firmware Finder. Then you can safely try flashing the GSI.
@MishaalRahman well it's bit like chicken egg dilemma. As we do not have a stock system image for e.g. SHT-W09 we cannot patch the ramdisk.img and so we cannot get the stock system image ...
Thanks Apo11on, great to have root so soon for the M5! Do you know if there's a way to get Xposed working? I tried the Xposed Framework SDK 26 from inside Magisk, but it put me in a boot loop.
Question is, for those of us with the Non Pro version, can this still be done.
@OHP Yes. The OP did it with the 8.4" version which has no pro option.
I'm looking to buy the Chinese 10" wifi version myself but need Google Play Store + Services on it which I'm guessing the Chinese version doesn't have. Is one of the firmwares at the website you link to a global version of the firmware that will work on this model?
OHP said:
Question is, for those of us with the Non Pro version, can this still be done.
Click to expand...
Click to collapse
Doesn't matter what version you have as long as you have access to your device firmware and the ramdisk.img. You really need to reread the guide.
magnumlove said:
Doesn't matter what version you have as long as you have access to your device firmware and the ramdisk.img. You really need to reread the guide.
Click to expand...
Click to collapse
Problem I have is :
CMR-W09C432B123 (8.0.0.123) from download headlines.
notice the Bold letter.
my Firmware on device:
CMR-W09C432123 (8.0.0.123)
obliviously it could be nothing but I wouldn't want to brick my tablet :fingers-crossed:
OHP said:
Problem I have is :
CMR-W09C432B123 (8.0.0.123) from download headlines.
notice the Bold letter.
my Firmware on device:
CMR-W09C432123 (8.0.0.123)
obliviously it could be nothing but I wouldn't want to brick my tablet :fingers-crossed:
Click to expand...
Click to collapse
I have exactly the same tablet/firmware as you and it was fine. The additional letter also threw me a little. But if you are unsure, download Huawei Firmware Finder from Google play and it will automatically detect your tablets firmware (which you can download if you wish).
magnumlove said:
I have exactly the same tablet/firmware as you and it was fine. The additional letter also threw me a little. But if you are unsure, download Huawei Firmware Finder from Google play and it will automatically detect your tablets firmware (which you can download if you wish).
Click to expand...
Click to collapse
I took the plunge, and I am sucessfully rooted now :silly:
struggling with this part
2. Transfer this patched ramdisk image to your device
Note for users with version of M5 other than SHT-AL09: Do NOT use the above ramdisk image. Download the full stock rom (update.zip) from the site I linked in the credits. Extract UPDATE.APP file from the zip. Then use HuaweiUpdateExtractor to extract ramdisk.img specific to your device. If you get errors in HuaweiUpdateExtractor - uncheck first 2 checkboxes for checksum verification on Settings tab and try again
I have a CMR-W09 :s i can got the files downloaded and the huwai software not sure how i make a img
The good news is I followed these instructions yesterday and they worked perfectly (SHT-AL09).
The bad news is, I seem to have lost root overnight.
---------- Post added at 06:41 AM ---------- Previous post was at 06:22 AM ----------
And I figured out why I lost root; I was playing around with Developer options and switched the default GPU renderer from 'default' to 'Skia.' Apparently, this disables root access until you switch back. I regained root access on a reboot, lost it again after switching back to Skia, and then regained it after switching back to default.
I got the right image file from the site and huwai extract. I have googled how to use this app but what files do I extract as there appears to be. Alot ? I extracted all of them ? I don't have a ramdisk.img
Also thanks for writting this up. Without it I would be lost
Thanks for the efforts making this thread. Unfortunately my device is SHT-W09 and I'm still waiting for the right firmware. Is there anything I can help, considering I have the device?
@dkk6 I am in the same boat as you. Unfortunately I installed the update to 8.0.0 123 without having the Firmware Finder installed on the device. Do you have installed already the update to 8.0.0 123?
If not, you could install Firmware Finder and provide us with the ota url ...
This works perfectly no issues. i had some how maanged to download the wrong rom first. AND thankfully it did not have a ramdisk in. it is important that your firmware matches the firmware present on the site as explained. This was easy guide to follow now to flash it with somthing other then andriod
AndDiSa said:
@dkk6 I am in the same boat as you. Unfortunately I installed the update to 8.0.0 123 without having the Firmware Finder installed on the device. Do you have installed already the update to 8.0.0 123?
If not, you could install Firmware Finder and provide us with the ota url ...
Click to expand...
Click to collapse
I'm on 8.0.0.101
******TWRP 3.1 FOR TCL 5044 all variants******
---------------------------------------------------------------------------
DISCLAIMER : this is an unnoficial build created by myself Tested and confirmed working, i used magisk V18 as test.zip and is now rooted with magisk, there will be bugs comment here any issues you find & i will fix them asap,
UPDATE : 26th Jan 2019 : WORKING
* SD card mount now added
*OTG fixed
* terminal now works within TWRP no more child process exited error,
* sideload is functional
NOT WORKING : MTP
---------------------------------------------------------------------------
CHIP VERSION
---------------------------------------------------------------------------
Compatible chip type: FSTYPE
MEDIATEK : MT6737M EMMC
MEDIATEK : MT6735M EMMC
---------------------------------------------------------------------------
NOTICE : take a firmware backup before flashing
Anything to your device though this recovery is
Confirmed working you should always back your original firmware up, This recovery does NOT come with a Scatter.file included to stop bricking with incompatible device partitions, should you require it please ask in the comments.
--------------------------------------------------------------------------
0. make sure OEM unlock is ON in the developer options before doing anything.
1. Unzip the recovery from the .zip.
2. Open SP Flash tool.
3.set your DA AGENT to all in one MTK DA.
4.load your scatter.file into the Flash tool.
5.wait for your scatter to load your files.
6.unselect all files for flash but recovery.
7.load twrp_3.1 into recovery slot.
7.1 if you have 5044T flash my patched boot.img below also.
8.MAKE SURE DOWNLOAD ONLY is set DO NOT use format all + download.
9. Click start download.
10. Remove battery from phone.
11. Connect to pc with usb cord.
12. wait for flash to complete.
13. Unplug & insert your battery.
14. Hold power & volume up until the first screen appears and release, TWRP will now load.
15. Swipe to allow modifications.
16. Tap wipe.
17. Tap format & type yes then press ok
18. Reboot recovery once complete,
19. You can now root your device or flash what you need to.
20. Hit the thanks button here on XDA i spent hours upon hours building this for everyone once you reboot after formatting the data partition it will take roughly 5 minutes for your 5044 to boot.
---------------------------------------------------------------------------
If you need help please dont be afraid to ask here im here to help, if it does not boot on your device your board is different in which case you will need to attach your boot.img & recovery.img in a post so i can download and create a compatible twrp for your device.
_____________________________________________
LINKS :
TWRP 3.1.0 updated 26th Jan 2019
https://drive.google.com/file/d/1hi19OtPeVqSpe3c6VyRu8XusBcCpmai0/view?usp=drivesdk
PATCHED BOOT.IMG (no dm-verity) 5044T ONLY
https://drive.google.com/file/d/1SR99R4Bo-VoZnd4T9rQebt5tczaHNQxT/view?usp=drivesdk
Pics of twrp
NEW UPDATED TWRP 3.2.3-0 here for OPTUS X SPIRIT ( 5044T MT6737M - MT6735M ) everything is confirmed working in the latest build including MTP
TWRP 3.2.3-0
https://forum.xda-developers.com/android/development/twrp-t3903337
Alcatel Versa
First off... Great work and an awesome easy to follow tutorial. Now for the million dollar question... I have an Alcatel 5044c. It's the Cricket version and it's called the Versa. It has Android 7.0. Is this compatible?
Illbeurhuckleberry6666 said:
First off... Great work and an awesome easy to follow tutorial. Now for the million dollar question... I have an Alcatel 5044c. It's the Cricket version and it's called the Versa. It has Android 7.0. Is this compatible?
Click to expand...
Click to collapse
Hey mate,
No not for this recovery your kernel will be different,
If you 5044C is mediatek you can upload me your recovery.img and i can most certainly make you twrp for your 5044C
android version your currently on wont matter TWRP version 3.x.x supports from android 6-9
Matty1993 said:
Hey mate,
No not for this recovery your kernel will be different,
If you 5044C is mediatek you can upload me your recovery.img and i can most certainly make you twrp for your 5044C
android version your currently on wont matter TWRP version 3.x.x supports from android 6-9
Click to expand...
Click to collapse
Hi,
Since others are asking:
Does this support the Alcatel 5044Y?
Is this the latest release?
/Martin
5044c boot.img and recovery.img
Need scatter and flash files please
GH
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?.
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.