Hi all, I've just got my hands on a TicWatch Pro 3 and am keen to mod it.
As far as I can tell, there've been no kernels or recoveries built for it yet. I'd like to fix that.
This will be my first time bringing up TWRP (I have experience with building AOSP and porting Ubuntu Touch and PostmarketOS).
If anyone else is interested in helping with this stuff, feel free to join in! It'd be great if we can build a bit of a community around this.
My plan of action is as follows:
Boot TWRP or obtain temporary root access in another way. Some kernel sources are available.
Extract images of every partition on the device (excluding userdata) so we have a way to restore everything if anything goes wrong,
Properly port TWRP to the device. This may be difficult; I don't think TWRP has run on the SDM429W before, though it's based off the SDM429. The Nokia 3.2 may be a useful reference.
Root the device with Magisk, and document the process so users can do it.
Build a custom kernel. To be honest, I'm not sure if this device needs one, but @janjan managed to squeeze amazing performance out of the OG TWP by tweaking a few things and disabling junk.
Here's some useful information to get started:
The TWP3 ships with a charging cable that only has power wires. It's possible to use an old TWP dock to get a data connection, though, and the bootloader can be unlocked through fastboot. See this thread for more info. The USB wire layout is not in the regular order (D+ and D- are swapped), so if you don't have an old dock and are using wires, refer to the pictures here.
The TWP3 LTE kernel source code is available here. I've also forked it here, in case anything happens to the original repo. As far as I can tell, there are no sources for the GPS model, but the kernel version in the repo (4.9.232) matches my GPS model's kernel version. I expect the LTE kernel can be used on the GPS with minimal effort.
The rubyfish kernel configuration is available through /proc. It's attached to this post.
I'm not sure if unlocking the bootloader blocks OTA updates; if it does, perhaps we should work out a way to manually download OTA updates before unlocking the bootloader.
Here's some miscellaneous information:
The TWP3 LTE is codenamed "rover", and the TWP3 GPS is codenamed "rubyfish".
As far as I can tell, the Snapdragon Wear 4100 in this device is a 64-bit SoC, but a 32-bit OS is in use.
Here's the complete kernel version string on my rubyfish running the latest OTA update: Linux version 4.9.232-perf+ ([email protected]) (gcc version 4.9.x 20150123 (prerelease) (GCC) ) #1 SMP PREEMPT Wed Jun 9 09:55:19 CST 2021
Fellow TWP 3 user here. Stoked that someone wants to give this a go. Appreicate the work you are putting into this.
I think the project is fantastic, the truth is that Mobvoi totally succeeded in minimizing attempts to root the watch, simply sold the watch with a cable that only serves to charge, and also there is none for sale (not even in the Asian market), you can only make one by hand, which pushes back 99.9% of users.
For those who don't know, the cable is mandatory, because to flash TWRP or root you must first unlock bootloader. Unlocking bootloader is done in bootloader mode (fastboot) and there will not work debugging via Wi-Fi, as the watch in this mode does not connect to the Wi-Fi network, it will only work with a USB cable.
Anyway, I want to contribute the info I have on the subject:
- Last May the user @mind-overflow was trying to port TWRP, I do not know if he has managed to advance something. Since May i do not know anything. Here the last thing he talked about it.
- Here, at the end of that post I explain how to make a handmade cable from a Ticwatch S/E cable.
bernarbernuli said:
I think the project is fantastic, the truth is that Mobvoi totally succeeded in minimizing attempts to root the watch, simply sold the watch with a cable that only serves to charge, and also there is none for sale (not even in the Asian market), you can only make one by hand, which pushes back 99.9% of users.
For those who don't know, the cable is mandatory, because to flash TWRP or root you must first unlock bootloader. Unlocking bootloader is done in bootloader mode (fastboot) and there will not work debugging via Wi-Fi, as the watch in this mode does not connect to the Wi-Fi network, it will only work with a USB cable.
Anyway, I want to contribute the info I have on the subject:
- Last May the user @mind-overflow was trying to port TWRP, I do not know if he has managed to advance something. Since May i do not know anything. Here the last thing he talked about it.
- Here, at the end of that post I explain how to make a handmade cable from a Ticwatch S/E cable.
Click to expand...
Click to collapse
Use "fastboot boot rubyfish_recovery.img"
Without "" obviusly
Actually it's untested
Edit: i see u from Spain, Send me pv if u have Telegram
Edit2: for upload the Rover variant
Rubyfish = BT + GPS Ticwatch Pro 3
Rover = LTE Ticwatch Pro 3
BadWolfYe said:
Utilice "fastboot boot rubyfish_recovery.img"
Sin "" obviamente
En realidad no ha sido probado
Editar: te veo de España, envíame pv si tienes Telegram
Click to expand...
Click to collapse
Wow, I stay around here
BadWolfYe said:
Use "fastboot boot rubyfish_recovery.img"
Without "" obviusly
Actually it's untested
Edit: i see u from Spain, Send me pv if u have Telegram
Click to expand...
Click to collapse
What good news, hopefully it works.
Pending clarification from @BadWolfYe I understand that TWRP recovery is ONLY for the GPS variant, no? I say this in case some brave guy who has TWP3 LTE is/will be flashing it.
bernarbernuli said:
What good news, hopefully it works.
Pending clarification from @BadWolfYe I understand that TWRP recovery is ONLY for the GPS variant, no? I say this in case some brave guy who has TWP3 LTE is/will be flashing it.
Click to expand...
Click to collapse
In theory can work for the two variants in any case if any want for LTE tell me and i upload
Although I would rather wait to upload it when I know if it goes at least the GPS In my jenkins I have a set to compile both variants as soon as I can test it in the next few days
@BadWolfYe Thanks for the builds! Do you have public device trees?
theOriginalSuperl2 said:
@BadWolfYe Thanks for the builds! Do you have public device trees?
Click to expand...
Click to collapse
for now I have not released the device Tree of TWRP until I check if it works
Developer Bubbles for the GPS? ooooou cant wait
Okey updates:
succesfully unlocked
but ....
C:\adb>fastboot boot recovery9.img
< waiting for device >
downloading 'boot.img'...
OKAY [ 0.967s]
booting...
FAILED (remote: dtb not found)
finished. total time: 13.708s
BadWolfYe said:
Okey updates:
succesfully unlocked
but ....
C:\adb>fastboot boot recovery9.img
< waiting for device >
downloading 'boot.img'...
OKAY [ 0.967s]
booting...
FAILED (remote: dtb not found)
finished. total time: 13.708s
Click to expand...
Click to collapse
Too bad, do you have a plan b?
bernarbernuli said:
Too bad, do you have a plan b?
Click to expand...
Click to collapse
without boot.img oem file no -.-"
BadWolfYe said:
por ahora no he lanzado el árbol de dispositivos de TWRP hasta que compruebe si funciona
Click to expand...
Click to collapse
my ticwatch e cable for modification will be here tomorrow then i'll dive in too
Be careful everyone - the first thing we should do is pull stock images before doing anything that may break OTA updates so we can revert back to stock if need be. I've been talking to JanJan on this matter, and it seems that OTA can be broken very easily.
@BadWolfYe, that DTB error can be caused by missing DTB images appended to the boot image or kernel. This can usually be remedied by changing the kernel configuration - have you tried using the config available through /proc/config.gz?
theOriginalSuperl2 said:
Be careful everyone - the first thing we should do is pull stock images before doing anything that may break OTA updates so we can revert back to stock if need be. I've been talking to JanJan on this matter, and it seems that OTA can be broken very easily.
@BadWolfYe, that DTB error can be caused by missing DTB images appended to the boot image or kernel. This can usually be remedied by changing the kernel configuration - have you tried using the config available through /proc/config.gz?
Click to expand...
Click to collapse
Yep, i use the config.gz from device, and the output file after build it's zImage-dtb
If any want acces to the source of device Tree/kernel
Send me a pm with Telegram Alias
Oh, wow, so excited about this!
I made several donations to janjan's projects over the years, as a longtime TW user, and will be glad to support a similar project for my latest watch.
Has anyone had an OTA update after unlocking the bootloader?
There were no more OTA updates since July. The last update for TWP3 LTE was in May and TWP3 GPS in July.
The only way someone meets that profile is to buy these days TWP3 GPS (and hopefully has not received the July factory update) , unlock the bootloader and then upgrade.
Related
As Modaco's boot image "Superboot (for Nexus One)" got no more updates after Android build version GRI40 and we're on GRK39F for some time now; and even though the Superboot GRI40 version gave you root as desired (https://bexton.net/2011/09/24/root-access-for-nexus-one-on-android-2-3-6-grk39f-superboot/), that Superboot version also caused some problems with wifi connection and had an outdated su binary, as well as an outdated Superuser.apk.
To cut a long story short, i did it on my own: Bexboot. A boot image - especially for Android GRK39F on passion devices. I compiled it (based on a guide by Modaco himself) from the stock GRK39F source of my own Nexus One. Also it includes the lates Superuser.apk (v3.0.5) and the latest su binary (v3.0).
Here you go: https://bexton.net/2011/10/12/bexboot-root-nexus-one-passion-grk39f/
Any feedback highly appreciated.
[UPDATE#1 08.11.2011]:
Please don't use v1 (link above) any longer. Instead use the Bexboot v2.0 (link below). It was rebuilt from a completely clean stock rom, what solves the compatibilty issues, some reported for v1. (Also it includes the latest Superuser.apk (3.0.6), as well as the latest su binary (3.0.3).)
https://bexton.net/2011/11/07/bexboot-for-passion-version-2-root-for-nexus-one-with-android-grk39f/
[UPDATE#2 11.12.2011]:
As i forgot to pay the invoice for the server where my blog is running on, it is offline since yesterday. :/ Anyway, i uploaded a copy of the zip archive containing all files you need to root your device to http://www.nahklick.de/user/stephan/bexboot.v2.GRK39F_OTA.zip. To get the instructions, follow this link http://www.google.com/search?q="bexboot"+version+2 and use the Google cache to view the original site. Thx
[UPDATE#3 20.02.2012]:
Files and instructions mirrored at request: http://code.google.com/p/bexboot/
i've posted this on my blog aswell. Nice work
http://patrick.oberdorf.net/2011/10/12/nexus-one-root-rechte-mit-stock-rom/
I've tried that, it does not work.
The fastboot utility says:
downloading 'boot.img'... OKAY
booting... OKAY
Then the phone reboots still not rooted.
zc2 said:
I've tried that, it does not work.
The fastboot utility says:
downloading 'boot.img'... OKAY
booting... OKAY
Then the phone reboots still not rooted.
Click to expand...
Click to collapse
Hi zc2,
sorry for the long response time, i was on a business trip and didn't had the time to check in. I received a bunch of similar issue reports so i did a factory reset and rebuilt the bootloader from a completely clean stock rom.
First comments confirm that it now also works for persons, that had the same issue like you with v1. So if you're still interested in it, check out the updated release version: https://bexton.net/2011/11/07/bexboot-for-passion-version-2-root-for-nexus-one-with-android-grk39f/
Hi Bexton, thank you for the response. I actually was able to root my phone using the instructions from the following post:
http://forum.xda-developers.com/showpost.php?p=18527514&postcount=1853
V2 Failed for me
Bexton said:
...use the Bexboot v2.0 (link below)....
Click to expand...
Click to collapse
Hi there. Thanks for your efforts. I have build GRK39F and ran your version 2 on Windows 7 (64 bit).
During step 6 of your procedure, the write proceudre failed with this error:
FAILED (remote: signature verify fail)
Any ideas? Diagnostic questions for me?
goattee said:
Hi there. Thanks for your efforts. I have build GRK39F and ran your version 2 on Windows 7 (64 bit).
During step 6 of your procedure, the write proceudre failed with this error:
FAILED (remote: signature verify fail)
Any ideas? Diagnostic questions for me?
Click to expand...
Click to collapse
Have you seen this comment / my answer: https://bexton.net/2011/11/07/bexbo...or-nexus-one-with-android-grk39f/#comment-179 ?
It is much likely due to an issue with your hboot version. Your provider probably pushed a locked SPL in an update that renders fastboot unusable. Maybe the link in my comment can help!? Let me know..
Greetz
Thanks for such a fast reply. I bought the phone in Bangkok. It was a "grey market" item from the Hong Kong market. I am not sure whether my Thai carrier even bothers with such things.
I looked at the link but unfortunately for me, I have only the most primitive understanding of how to deal with the bootloader, etc. So I can't even grasp what aspects of that thread apply to me. I really need step-by-step instructions. So unless I can find someone with more mastery, I guess I will only dream of Cyanogen Mod on my phone.
goattee said:
Hi there. Thanks for your efforts. I have build GRK39F and ran your version 2 on Windows 7 (64 bit).
During step 6 of your procedure, the write proceudre failed with this error:
FAILED (remote: signature verify fail)
Any ideas? Diagnostic questions for me?
Click to expand...
Click to collapse
Bexton said:
Have you seen this comment / my answer: https://bexton.net/2011/11/07/bexbo...or-nexus-one-with-android-grk39f/#comment-179 ?
It is much likely due to an issue with your hboot version. Your provider probably pushed a locked SPL in an update that renders fastboot unusable. Maybe the link in my comment can help!? Let me know..
Greetz
Click to expand...
Click to collapse
You will get that error if you are trying to use fastboot commands without first having unlocked your bootloader.
That error has nothing to do with the HBOOT version on Nexus One's. You cannot "push" a locked SPL to an N1 if you've already unlocked your bootloader. The bootloader unlock flag is set in the radio NV memory, so once you have unlocked the bootloader, you cannot relock it (unless you have S-OFF), even if you reflash another stock hboot.
efrant said:
You will get that error if you are trying to use fastboot commands without first having unlocked your bootloader.
That error has nothing to do with the HBOOT version on Nexus One's. You cannot "push" a locked SPL to an N1 if you've already unlocked your bootloader. The bootloader unlock flag is set in the radio NV memory, so once you have unlocked the bootloader, you cannot relock it (unless you have S-OFF), even if you reflash another stock hboot.
Click to expand...
Click to collapse
I realize you're trying to clarify. But I don't understand any of the terminology. The only thing I am capable of is following a prescribed procedure. I thought this procedure was going to unlock and root the phone. I guess I was wrong.
I don't have the diagnostic skills to change direction if things don't go in a predictable fashion-- I've only used stock devices up until now and this was my first attempt. I guess the best I can hope for is to make contact with someone more experienced when I am next in the US and have that person assist me. It makes it more difficult because most of what I am finding online is either old (pre-Gingerbread) or it assumes the user has hacked their Nexus One in the past and just needs to bring it up to date.
My goal is to get past the memory problems I am having by installing a custom ROM with a minimal set of apps in phone memory-- and more customizability.
nice man! It worked on the first go! Top job!
I have one question though! Is it safe to flash Clockword Mod recovery and then flash custom ROMs, or will it end in not finding the recovery image as is the case with other efforts to root 2.3.6?
Thanks!
davelis828 said:
nice man! It worked on the first go! Top job!
I have one question though! Is it safe to flash Clockword Mod recovery and then flash custom ROMs, or will it end in not finding the recovery image as is the case with other efforts to root 2.3.6?
Thanks!
Click to expand...
Click to collapse
No prob. You can use: https://bexton.net/android/n1/recoveries/recovery-clockwork-5.0.2.0-passion.img
If needed, here's the full stock GRK39F: https://bexton.net/android/n1/sys/grk39f/ota.zip and here the update: https://bexton.net/android/n1/sys/grk39f/d323ca384aaa.signed-passion-GRK39F-from-GRJ22.d323ca38.zip
o thanx ma! i appreciate your feedback, you did it on both sites aswell
Respect!
Mirror created at request: http://code.google.com/p/bexboot/
I gave superoneclick a go before trying this method. It worked flawlessly.
Sent from my Nexus One using Vodka
Source code availability?
Hi Bexton,
first of all, thanks for your work!
Next, I'd like to replace the Superuser app by Koush' one (https://github.com/koush/Superuser/).
Would it be possible to get the source code of bexboot?
None is available at http://code.google.com/p/bexboot/source/checkout...
Regards,
Patrick.
Kogan agora 6 plus.
android 6.0
i tried, kingoroot, towelroot and kingroot.
All failed, i am now asking around the community on a way to root it for various reasons.
will provide more info about it when it charges.
edit:
Model number: Kogan Agora 6Plus
android version: 6.9
baseband version: MOLY.LR11.W1539.MD.MP.V10.P6, 2016/07/29 14:46
kernal version: 3.18.22
Build number: M1_PLUS_N_AU_KG_M_MT6755_65U_V1.8
custom build version: alps-mp-m0-mp7-v1.5_mlt6755.65u.m_p11
In the developer options, there is a toggle called OEM unlocking. Try toggling it and try rooting again.
I got my device rooted... it's an algerian clone of your device and you can check by yourself (google "iris next e"
At first, I thought that this device is unrootable as I tried every rooting sofrware out there and no one sorked, then I tried some adb methods and neither worked also, but then I tried the last bullet in my gun and that worked
I repacked a TWRP recovery to be compatible with the device and rooted systemlessly with supersu... now I even have exposed and magisk working
If you can make the recovery yourself then do it, if you don't I can share my repacked TWRP with you and show you step by step what to do
On the technical side, what I discovered was that there is no adbd neither adb bridge in stock recovery mode (I even looked for it in the ramdisk and found out it's not loaded) so the repacked TWRP recovery (I got the source TWRP from a Xiaomi m3 forum, the M3 has the same SoC -mt6755- which made it easy to port), I booted the recovery from fastboot and it worked like a charm
p.s: if you dont know what all I said means, don't try it, you might brick your phone!! and please don't try the m3 recovery without porting it cause it will brick your phone for sure!!
I can confirm they device looks identical, I am not very familiar with repacking TWRP, but would be appreciative if you were happy to share.
Jimmy Mossiba Floyd said:
I got my device rooted... it's an algerian clone of your device and you can check by yourself (google "iris next e"
At first, I thought that this device is unrootable as I tried every rooting sofrware out there and no one sorked, then I tried some adb methods and neither worked also, but then I tried the last bullet in my gun and that worked
I repacked a TWRP recovery to be compatible with the device and rooted systemlessly with supersu... now I even have exposed and magisk working
If you can make the recovery yourself then do it, if you don't I can share my repacked TWRP with you and show you step by step what to do
On the technical side, what I discovered was that there is no adbd neither adb bridge in stock recovery mode (I even looked for it in the ramdisk and found out it's not loaded) so the repacked TWRP recovery (I got the source TWRP from a Xiaomi m3 forum, the M3 has the same SoC -mt6755- which made it easy to port), I booted the recovery from fastboot and it worked like a charm
p.s: if you dont know what all I said means, don't try it, you might brick your phone!! and please don't try the m3 recovery without porting it cause it will brick your phone for sure!!
Click to expand...
Click to collapse
ok then: what you'll need to download is:
1. adb minimal drivers (you can find it here on xda)
2. supersu latest systemless zip (2.79 I think it's the latest version) after you've downloaded it, put it in the device's internal memory (yeah just right-click the zip file, chose "send-to" then chose your device)
3. the recovery file which is compressed in zip (unzip it and put the img file in the folder where you've installed adb - c:\adb\ )
after that, when you've got everything set, restart your device in fastboot mode: shut down the phone then put it on by hitting the power button and volume up button.. you're gonna have a three-choices menu that you're gonna scroll with the volume up button, when you've got the cursor on "fastboot" press the volume down button... the device will be put on fastboot mode.
Now back to your pc, open a command prompt, then brows to c:\adb. When you have your command prompt on adb, write this (including the quotes):
fastboot boot "TWRP 3.0.2 by Jemmini.img"
Hit enter... wait a little (while the recovery boots) and then... voila!! all you've got to do is to flash the supersu zip through the recovery and reboot: congratulations your device is now rooted
p.s: I suggest you make a full backup for all the partitions from TWRP before you do anything... you'll thank me for that
Thanks for the elaborate explanation,but I am stuck on:
Jimmy Mossiba Floyd said:
fastboot boot "TWRP 3.0.2 by Jemmini.img"
Click to expand...
Click to collapse
Cmd says that it successfully pushed and booted the image
Code:
downloading 'boot.img'...
OKAY [ 0.717s]
booting...
OKAY [ 0.070s]
finished. total time: 0.799s
...but after a couple of seconds, it reboots to system.
Any Ideas what is happening?
Long time no see hhhhh
ummm really have no idea since it works flawlessly for me but ummmm tell me: do you care if you lose the stock recovery?
I would like to try to flash it but there is a chance that it would not work , therefore having no recovery. I have unlocked my bootloader though.
Ok so instead of:
fastboot boot "TWRP 3.0.2 by Jemmini.img"
Try:
fastboot flash boot "TWRP 3.0.2 by Jemmini.img"
This is only if you're gonna take the risk... If not, just give me time maybe I'm gonna find something for you
Sorry, but I don't want to take the risk. I think the problem is that I am running Android 7.0 which differs from other versions. I have contacted Kogan to see if I can access the source code, but judging by previous threads on Kogan, it is not going to be easy.
Ah ok then I must be wrong! Because my device runs on Marshmallow 6.0 and ther must be a difference between the two (software-side)
I don't know if you can do it but, can I have a system dump so that I can bring you a fix for rooting the device?
P.S: I can assist you to make one if you want!
I am not quite sure how to dump the system (Is it "adb pull /system <whatever path>"). I have run the command, and it seems that adb can't access the /system/bin folder. Is it required for recovery porting? If not I will upload the system.
Sorry for being late, I have no DSL where I live and my data plan came to an end!! I will look for a method to dump the whole system for you. Stay tuned
Kogan has replied back and the kernel is released to the public.
https://assets.kogan.com/files/support_files/KAPHN4G6PA_Kernel/kernel-3.18.tar.gz
I am not very experienced with compiling from the kernel so some help would be nice.
I'm not really into compiling kernels... I wish I could... Gonna see with some developers in the samsung forums may be they'll be willing to help
P.S: I'm really really sorry for being late to help you with rooting the phone.. my only pc is bricked and I need it to send you the files I used to pull and push recovery to the phone
In case it's not much asking, is there a possibility to have the link for the stock firmware from kogan?
Unfortunately, Kogan did not release the stock firmware, just the kernel. I'll too go to the other forums and see if they can help.
Thank you very much for your help, and I hope that you can un-brick your pc.
Installed TWRP but it can't read internal storage.
Also wanting to root my agora 6 plus BUMP
looking for help to root
Goals:
Installing a custom recovery like trwp
Rooting
Flashing Xposed.
its on Nougat (7.0)
I can access the bootloader, fastboot and the default installed "recovery" which when loaded say something macros the lines of no commands give by booting the phone and holding both vol up and the lock/power buttons.
I'm available to talk on discord to speed things up.
I've got a bit of experience rooting the z2 and an old htc pico back in the day but i'm consider me a noob as i haven't done this kinda thing in years and don't even know where to begin.
Cryptic Bore said:
looking for help to root
Goals:
Installing a custom recovery like trwp
Rooting
Flashing Xposed.
its on Nougat (7.0)
I can access the bootloader, fastboot and the default installed "recovery" which when loaded say something macros the lines of no commands give by booting the phone and holding both vol up and the lock/power buttons.
I'm available to talk on discord to speed things up.
I've got a bit of experience rooting the z2 and an old htc pico back in the day but i'm consider me a noob as i haven't done this kinda thing in years and don't even know where to begin.
Click to expand...
Click to collapse
The thing is that I have a similar (identic) phone but Algerian brand that makes the phone is still on marshmallow!
I've still got the phone, but I don't know if my TWRP would work for you!
Quick questions:
0. Is it your daily driver phone? do you have a backup for your photos/data/important files on internal storage? just to put you in the image: I lost all my internal storage as I was playing with ramdisk modifications, hopefully my photos were cloud backed up. So be warned
1. Is your phone's bootloader unlocked?
2. Are you familiar with flashing or booting recoveries or kernels from fastboot?
after you answer I'll guide you through it
Hey thanks for the reply im thinking of teaching myself to build my own port of trwp.
0. It is my daily driver but i only just got it the other day ie. nothing important on there besides two factor authentication which even that i can reset up fairly easily. or just take the sim card out and use sms for that.
I also like to live on the edge a bit place austinpowers.jpg here(my first smart phone i got for my birthday from my rents: i got into a boot loop through flashing with in a week of receiving it and fixed on the fly at uni using the libary computers without my rents knowing my phone was broken xD)
1. Is the boot loader unlocked not sure how to check it on this phone, I do however have dev options unlocked with usb debuging etc turned on aswell as tickbox for "OEM Unlocking" with the description: allow the bootloader to be unlocked which i just have turned on .
2. Yes i do but im a bit out of practice its been years since ive messed around with root on android. Ive got logcat dumps through adb and have got fast boot working (as far as i can tell with the "fastboot" devices query) Got some help from a FB friend who is also going to try helping me make this happen. My previous experience was a HTC pico (the first smart phone i referenced earlier) and a Sony z2 which recently died dropping it which had a duel boot setup with carbon rom being the daily driver/rom.
Jimmy Mossiba Floyd said:
The thing is that I have a similar (identic) phone but Algerian brand that makes the phone is still on marshmallow!
I've still got the phone, but I don't know if my TWRP would work for you!
Quick questions:
0. Is it your daily driver phone? do you have a backup for your photos/data/important files on internal storage? just to put you in the image: I lost all my internal storage as I was playing with ramdisk modifications, hopefully my photos were cloud backed up. So be warned
1. Is your phone's bootloader unlocked?
2. Are you familiar with flashing or booting recoveries or kernels from fastboot?
after you answer I'll guide you through it
Click to expand...
Click to collapse
UPDATED 2/19/2018
Almost enough here to start attempting debug builds... any other builders/devs out there working on this device? Hopefully some of this will be useful.
Minimal Omni device tree for TWRP (full lineage branch in progress as of 2/19/2018)
https://github.com/mightysween/android_device_motorola_payton
Proprietary blobs/vendor (initial push 2/19/2018):
https://github.com/mightysween/android_vendor_motorola_payton
Partition names/locations/mounts...maybe a few missing still:
https://docs.google.com/document/d/1EkPOkc8uUStKIjRGC2-4jkcXpxmj8v3piGPqZi9ctQM/edit?usp=drivesdk
7.1 KERNEL SOURCE:
https://github.com/MotorolaMobilityLLC/kernel-msm/tree/7.1.1-nougat-release-payton
8.0 KERNEL SOURCE:
https://github.com/MotorolaMobilityLLC/kernel-msm/releases/tag/MMI-OPW27.57-40
So what's the deal with the A/B partitions? I've seen that there are some lineage OS commits to handle the A/B partitions. Would it be possible to load an OS to the A partition and put the recovery on the B partition. I'm not familiar enough to know how much control of the boot process we can have with boot time commands. Does the bootloader have a boot to recovery option?
There doesn't seem to be a recovery partition in the list that you provided. I wonder what the fastboot commands look like... just thinking out loud on the internet. I don't have the phone yet, but I did have a look at Best Buy, so that practically makes me an expert. I have a N5X, so I'm lining up the successor for after its sudden, but inevitable betrayal.
gee one said:
So what's the deal with the A/B partitions? I've seen that there are some lineage OS commits to handle the A/B partitions. Would it be possible to load an OS to the A partition and put the recovery on the B partition. I'm not familiar enough to know how much control of the boot process we can have with boot time commands. Does the bootloader have a boot to recovery option?
There doesn't seem to be a recovery partition in the list that you provided. I wonder what the fastboot commands look like... just thinking out loud on the internet. I don't have the phone yet, but I did have a look at Best Buy, so that practically makes me an expert. I have a N5X, so I'm lining up the successor for after its sudden, but inevitable betrayal.
Click to expand...
Click to collapse
There is no traditional recovery partition...handled by boot. A/B is mainly to allow 'seamless' updates (as in OTA that downloads to the other partition for instant reboot). Bit more to it... if you want to read more, check out the Pixel forums.
Well... progress is being made. Wish there were others (there must be!) working on this.
I have the stock kernel, a VERY basic device tree, and cobbled-together vendor... syncing repos and will try to compile TWRP over the weekend. I do not expect it to work
Dealing with this right now on brunch...runs fine up until this point, appreciate any thoughts:
Starting build with ninja
ninja: Entering directory `.'
ninja: error: '/home/mightysween/android/omni/out/target/product/payton/obj/SHARED_LIBRARIES/libcryptfs_hw_intermediates/export_includes', needed by '/home/mightysween/android/omni/out/target/product/payton/obj/SHARED_LIBRARIES/libcryptfslollipop_intermediates/import_includes', missing and no known rule to make it
build/core/ninja.mk:157: recipe for target 'ninja_wrapper' failed
make: *** [ninja_wrapper] Error 1
Click to expand...
Click to collapse
Do I really need the lollipop libs???? Especially if I just want to compile TWRP and not full omni. Ahhhhhhh....so much fun
OK, got TWRP to compile
Need to do some testing in the emulator and double and triple check all sources and configs before even thinking about trying to boot it on the actual device.
But just troubleshooting at this point, so looking good for TWRP in coming days!
UPDATE: oops, totally compiled it with the wrong kernel. Haha... working through some defconfig issues, but hopefully nothing too crazy.
mightysween said:
OK, got TWRP to compile
Need to do some testing in the emulator and double and triple check all sources and configs before even thinking about trying to boot it on the actual device.
But just troubleshooting at this point, so looking good for TWRP in coming days!
Click to expand...
Click to collapse
I hope you can do it! Is the first step to get backups and ROMs. I don´t have the phone yet, but later the normal version that is sell in México and want to flash the Android One version (previously anyone get it working).
I'm returning my Amazon version of this phone and getting Project Fi version. I am willing to help in testing.
Well, my boot.img compiles fine... but will not boot to recovery. Given the fact that it is mostly guesswork on the device tree, I am not shocked.
Pushed my working tree to GitHub and will keep working on it...
https://github.com/mightysween/android_device_motorola_payton
Been looking at Pixel 2 TWRP Alpha... holy cow. So much more to it with this partitioning scheme.
mightysween said:
Well, my boot.img compiles fine... but will not boot to recovery. Given the fact that it is mostly guesswork on the device tree, I am not shocked.
Pushed my working tree to GitHub and will keep working on it...
https://github.com/mightysween/android_device_motorola_payton
Been looking at Pixel 2 TWRP Alpha... holy cow. So much more to it with this partitioning scheme.
Click to expand...
Click to collapse
Have not even peeked into the Pixel 2 forums. I'm afraid this seems to be another ballgame entirely. Do the new Pixel owners even have root passing safety net while allowing these security updates new android phones now get? Gah this is a mess
SR3TLAW said:
Have not even peeked into the Pixel 2 forums. I'm afraid this seems to be another ballgame entirely. Do the new Pixel owners even have root passing safety net while allowing these security updates new android phones now get? Gah this is a mess
Click to expand...
Click to collapse
TWRP has been worked on for Pixel2 by several people, including expert Dees Troy, and is still a heavy alpha. I feel pretty good about booting compiled boot images and not bricking on x4 (as far as I have gotten)
I have been compiling my own stuff for many years, and yes -- this new stuff is foreign. But, we will all learn and in a few weeks/months, there will be plenty of action on this device
mightysween said:
TWRP has been worked on for Pixel2 by several people, including expert Dees Troy, and is still a heavy alpha. I feel pretty good about booting compiled boot images and not bricking on x4 (as far as I have gotten)
I have been compiling my own stuff for many years, and yes -- this new stuff is foreign. But, we will all learn and in a few weeks/months, there will be plenty of action on this device
Click to expand...
Click to collapse
try using fixes from https://github.com/TeamWin/android_device_xiaomi_tissot tree. similar android one device!!
i.snehal.kiran said:
try using fixes from https://github.com/TeamWin/android_device_xiaomi_tissot tree. similar android one device!!
Click to expand...
Click to collapse
Thanks, picked up 3 changes from here already... will test them out soon!
So, I have checked out several XDA threads on this Xiaomi device (tissot) and I think it is going to help quite a bit with the A/B issues.
I am still, unfortunately stuck on getting TWRP to boot. Boot.img compiles fine and I can extract it and see TWRP has replaced stock recovery in the ramdisk, but it will not boot into recovery.
Ideally, we need a way to boot a TWRP image without flashing anything... easier said than done with devices that have recovery baked into the boot image. But once that works, we can extract just the ramdisk from my build and write a script to patch it into the stock boot image from the temporary TWRP running on the device.
Progress! New TWRP thread coming soon...
BTW, there is still a long way to go here... this was just a rudimentary test to get TWRP to boot. Need to start totally fresh with partitions before there is any attempt to actually use it!
Also -- my build environment is a total cluster after weeks of messing around. I need to wipe it and start over. That alone will take me a few days, and TWRP might take a few weeks more.
Incredible! Looking forward to having a custom recovery!
mightysween said:
Progress! New TWRP thread coming soon...
BTW, there is still a long way to go here... this was just a rudimentary test to get TWRP to boot. Need to start totally fresh with partitions before there is any attempt to actually use it!
Also -- my build environment is a total cluster after weeks of messing around. I need to wipe it and start over. That alone will take me a few days, and TWRP might take a few weeks more.
Click to expand...
Click to collapse
I hope later we can flash the Android One firmware on the retail Moto X4, I supose that OTA update will not work but at least we will have the lastest updates if someone make a flashable version
f3r.and0 said:
I hope later we can flash the Android One firmware on the retail Moto X4, I supose that OTA update will not work but at least we will have the lastest updates if someone make a flashable version
Click to expand...
Click to collapse
At the very least, we have the ability to create "nandroid" style backup from A1 device. Theoretically, that could allow anyone to install it...
But yes, in the long run, hopefully the actual firmware is released
mightysween said:
At the very least, we have the ability to create "nandroid" style backup from A1 device. Theoretically, that could allow anyone to install it...
But yes, in the long run, hopefully the actual firmware is released
Click to expand...
Click to collapse
Doesn't the nandroid (or for that matter Flashfire) backup contain personally unique identifiers?
DiDGR8 said:
Doesn't the nandroid (or for that matter Flashfire) backup contain personally unique identifiers?
Click to expand...
Click to collapse
Yes, technically... obviously would need to start with a fresh system and limit to non-data partitions.
No one needs to restore someone else's apps... just their boot/oem/system_image
mightysween said:
Yes, technically... obviously would need to start with a fresh system and limit to non-data partitions.
No one needs to restore someone else's apps... just their boot/oem/system_image
Click to expand...
Click to collapse
This just came to my mind, since this phone has 2 partitions for boot etc. --
Code:
mmcblk0p44: boot_a SIZE:65536 blocks
mmcblk0p45: boot_b
can't we make backup of boot_b ? it will be same as boot_a but unmodified i think ? i mean, use magisk/cf-autoroot/whatever to gain root on boot_a. and make backup of boot_b. so in case if we want to receive update, just restore back boot_b.img to boot_a slot and update through ota ? that way we can practically make full backup which is unmodified. ofc this is until we have fastboot image available and working TWRP.
also it seems all x4's are having same kernel according to this thread. although their build time is different.
Apologies if this is reported elsewhere (I couldn't find it) but here is a new unlock method by 'mashed-potatoes' on github and it's flippin' awesome!
See: "github.com/mashed-potatoes/PotatoNV[/" (had to format like this due to XDA newbie rules)
I've just unlocked a P10 bootloader with it - the phone was running Oreo with a March 2019 security patch :good:
It is a test point method - so back cover needs to be removed (TP location easily found on YouTube)
When I realised I was stuck on a patch >June18 I thought bootloader unlocking wouldn't be possible (although I was trawling XDA archives to see if flashing board software for unlocked fastboot might provide a route). Anyway, didn't need any of that cuz I ran PotatoNV.exe and put the phone in TP mode and ker-boom: BL unlocked! Amazing work.
EDIT:
A few extra tips to help get through the process:
- You will need to install Test-point drivers - can be found by running the Potato program and following the web address to the User Manual - link to drivers is there. (Uninstall drivers when finished or else phone won't be recognized properly by PC later!)
- Open up Device Manager to check that you are booting to TP - devices changes from 'USB SER' to 'USB (COM')' - or something like that, I don't exactly remember!. It might take a few goes to boot into TP - disconnect then reconnect battery each attempt.
Thanks for sharing this program. this works for me, after bricking my phone 2 years ago. I finally got to unlock my bootloader. And its working now and doing great.
Hello,
Does this soft FACTORY RESET after bootloader unlock?
Regards
RJ
tested on huawei p10 vtr-l09 with emui 9.1 and works perfectly, does not erase data or do hard reset, excellent tool ?
---------- Post added at 07:52 AM ---------- Previous post was at 07:51 AM ----------
rafjak said:
Hello,
Does this soft FACTORY RESET after bootloader unlock?
Regards
RJ
Click to expand...
Click to collapse
no friend, i did it and it doesn't factory reset
Hey bro, could you please tell me the steps you made?
I am in emui 9.1 too.
Thanks.
josua19 said:
tested on huawei p10 vtr-l09 with emui 9.1 and works perfectly, does not erase data or do hard reset, excellent tool
---------- Post added at 07:52 AM ---------- Previous post was at 07:51 AM ----------
no friend, i did it and it doesn't factory reset
Click to expand...
Click to collapse
itsjhndnllclrg said:
Thanks for sharing this program. this works for me, after bricking my phone 2 years ago. I finally got to unlock my bootloader. And its working now and doing great.
Click to expand...
Click to collapse
Hi, can you help with the steps please, i'm a newbie at using git.
Never mind, thanks.
HOW TO OPEN PotatoNV.exe
New_ said:
Apologies if this is reported elsewhere (I couldn't find it) but here is a new unlock method by 'mashed-potatoes' on github and it's flippin' awesome!
See: "github.com/mashed-potatoes/PotatoNV[/" (had to format like this due to XDA newbie rules)
I've just unlocked a P10 bootloader with it - the phone was running Oreo with a March 2019 security patch :good:
It is a test point method - so back cover needs to be removed (TP location easily found on YouTube)
When I realised I was stuck on a patch >June18 I thought bootloader unlocking wouldn't be possible (although I was trawling XDA archives to see if flashing board software for unlocked fastboot might provide a route). Anyway, didn't need any of that cuz I ran PotatoNV.exe and put the phone in TP mode and ker-boom: BL unlocked! Amazing work.
Click to expand...
Click to collapse
Hi, please please explain how to run the potato project
found it, please ignore the post
Friends could pass the tutorial video of the TP location
New_ said:
Apologies if this is reported elsewhere (I couldn't find it) but here is a new unlock method by 'mashed-potatoes' on github and it's flippin' awesome!
See: "github.com/mashed-potatoes/PotatoNV[/" (had to format like this due to XDA newbie rules)
I've just unlocked a P10 bootloader with it - the phone was running Oreo with a March 2019 security patch :good:
It is a test point method - so back cover needs to be removed (TP location easily found on YouTube)
When I realised I was stuck on a patch >June18 I thought bootloader unlocking wouldn't be possible (although I was trawling XDA archives to see if flashing board software for unlocked fastboot might provide a route). Anyway, didn't need any of that cuz I ran PotatoNV.exe and put the phone in TP mode and ker-boom: BL unlocked! Amazing work.
EDIT:
A few extra tips to help get through the process:
- You will need to install Test-point drivers - can be found by running the Potato program and following the web address to the User Manual - link to drivers is there. (Uninstall drivers when finished or else phone won't be recognized properly by PC later!)
- Open up Device Manager to check that you are booting to TP - devices changes from 'USB SER' to 'USB (COM')' - or something like that, I don't exactly remember!. It might take a few goes to boot into TP - disconnect then reconnect battery each attempt.
Click to expand...
Click to collapse
I DOWNLOADED THE FILE FROM GIT.. BUT IT DOESNT HAVE BOOTLOADER FILES INCLUDED WHERE CAN I GET?
KIRIN 960 HUAWEI P10,
1. DOWNLOADED THE ZIP FROM GITHUB
2. RUN THE PROGRAM USING VISUAL INSTALLER
3. PUT THE P10 TO TESTPOINT METHOD AND ENABLE HUAWEI COM 1.0
4. PROGRAM ERRORS WHEN LOOKING FOR BOOTLOADER FILES.
where can i get bootloader files ? for kirin 960 i can
Please do you add support for newer Kirin CPUs? Kirin 990 etc...
DasXardas said:
Please do you add support for newer Kirin CPUs? Kirin 990 etc...
Click to expand...
Click to collapse
Err, no. Finding bootloader exploit on newer Kirin's would be like finding Holy Grail.
You could always join 'Big Huawei Exploits' group on Telegram and ask them how it's going rolleyes
New_ said:
Err, no. Finding bootloader exploit on newer Kirin's would be like finding Holy Grail.
You could always join 'Big Huawei Exploits' group on Telegram and ask them how it's going rolleyes
Click to expand...
Click to collapse
Thank you. I'll try them.
Is it possible to unlock bootloader & root phone, which was rebranded with "funky huawei" ?
Huawei P10, from VTR-L09 to VTR-L29
[QUOTE = "New_, publicación: 83667321, miembro: 10899731"]
Grandes hazañas de Huawei
[/CITAR]
Please link
Many thanks, it worked flawlessly on my P10 running EMUI 9.1! Test points and disassembly instructions can easily be found on the interwebs. Do not forget to write down the bootloader unlock code PatatoNV generates: I needed it after I bootlooped and downloaded the latest rom with erecovery.
M1chiel said:
Many thanks, it worked flawlessly on my P10 running EMUI 9.1! Test points and disassembly instructions can easily be found on the interwebs. Do not forget to write down the bootloader unlock code PatatoNV generates: I needed it after I bootlooped and downloaded the latest rom with erecovery.
Click to expand...
Click to collapse
Did you lost the unlocked BL after you dl the latest rom and recovery?
Sterben11 said:
Did you lost the unlocked BL after you dl the latest rom and recovery?
Click to expand...
Click to collapse
I downloaded the latest rom twice through erecovery. The first time it locked my bootloader, but the second time it did not. The first time I could easily unlock again with the code generated by the patatoNV tool.
M1chiel said:
I downloaded the latest rom twice through erecovery. The first time it locked my bootloader, but the second time it did not. The first time I could easily unlock again with the code generated by the patatoNV tool.
Click to expand...
Click to collapse
Ah yes I bricked my phone 2 times already and experienced what erecovery is for. It's my first time to mess with my good ol p10 have you tried any working open kirin custom on it? cuz everytime I flash a 9.0/9.1 compatible rom it ends on bootloop I used adb and fastboot btw. This is my last question sorry a noobie here.
(take note I followed every instructions on their support page on how to flash)
Sterben11 said:
Ah yes I bricked my phone 2 times already and experienced what erecovery is for. It's my first time to mess with my good ol p10 have you tried any working open kirin custom on it? cuz everytime I flash a 9.0/9.1 compatible rom it ends on bootloop I used adb and fastboot btw. This is my last question sorry a noobie here.
(take note I followed every instructions on their support page on how to flash)
Click to expand...
Click to collapse
The AEX roms worked for me, the omniroms unfortunately did not boot (emui 9.1). They are supposed to work on emui 9.0. Did you do the factory reset from emui recovery? AEX is very basic android and quite nice, although not as fluent as emui.
Hello! 'Know of any custom twrp for the XT2165-5 "Tonga" ???
My Moto G Power (2022) is a factory unlocked, North American Retail version.
I have rooted it with Magisk, but still have the default Recovery.
'Would like to have TWRP recovery as a convenience, but it's not a necessity
since I'm already rooted.
Thanks for taking the time to read this. Happy New Year 2023!
Unfortunately the dev scene for the Moto G "tonga" seems to be fairly inactive. I've been attempting to learn about ways to go about porting TWRP but I must admit my Android knowledge is fairly lacking since I came from the iOS jailbreak scene. Will definitely post a thread on XDA if/when I make progress.
With that said if anyone could point me towards any guides for porting TWRP I'd appreciate it as it seems a lot of what i find is fairly outdated?
Yes, I haven't seen much available for the Moto G Power "tonga", either.
There is a site on GitHub named "twrpbuilder" --
"Official site of the TWRP Builder Project"
Can't comment on it, 'only browsed the site ...
wc4usa said:
Hello! 'Know of any custom twrp for the XT2165-5 "Tonga" ???
My Moto G Power (2022) is a factory unlocked, North American Retail version.
I have rooted it with Magisk, but still have the default Recovery.
'Would like to have TWRP recovery as a convenience, but it's not a necessity
since I'm already rooted.
Thanks for taking the time to read this. Happy New Year 2023!
Click to expand...
Click to collapse
Hey,
Greetings to you. I, too, have a 2022 Motorola Tonga; I have the X2165DL, though, and it's not unlocked. I was wondering if you'd be willing to point me in the right direction with regards to HOW you managed to get it rooted? I have been met with no success at all in my search to root this phone. I would be appreciate your assistance very much.
I look forward to your response.
Thank you, I hope, in advance.
Will
Jetpac_HrtfdCT06120 said:
Hey,
Greetings to you. I, too, have a 2022 Motorola Tonga; I have the X2165DL, though, and it's not unlocked. I was wondering if you'd be willing to point me in the right direction with regards to HOW you managed to get it rooted? I have been met with no success at all in my search to root this phone. I would be appreciate your assistance very much.
I look forward to your response.
Thank you, I hope, in advance.
Will
Click to expand...
Click to collapse
Hi ... I believe that any Moto device with the letters "DL" at the end is a Tracfone model. They are very, very difficult to unlock. Sorry to break the news.
Otherwise, you might be able to find an unlock service (or hacker) -- and pay a fee to unlock the bootloader. It won't be cheap. ( Note: some that advertise that they can unlock a Moto xxxx- DL cannot really do it - they just take your money.
BTW: The Moto G (2022) Power is inexpensive to buy new --from Motorola or Amazon, etc. You want the "Retail US" model -- works on any network -- and then you can go to the Motorola website for the unlock code, for free.
You don't need the retail version, you can unlock the boost version. Mine was 40 bucks new from target. If it is unlockable, the OEM unlock switch will become toggleable after 72 hours of using the device. Even if it can't be through Motorola you can use mtk tools to root it, but you'll have to look that up and read about using it. I have not used it myself but there is a group by the name of A-team discussion on a certain popular messaging app that can help
wc4usa said:
Hello! 'Know of any custom twrp for the XT2165-5 "Tonga" ???
My Moto G Power (2022) is a factory unlocked, North American Retail version.
I have rooted it with Magisk, but still have the default Recovery.
'Would like to have TWRP recovery as a convenience, but it's not a necessity
since I'm already rooted.
Thanks for taking the time to read this. Happy New Year 2023!
Click to expand...
Click to collapse
Ever find anything? I did the same thing, rooting was easy compared to trying to find any software/mods that don't look dicey at best. Still just got the same apks i used before i rooted LOL
alphaGodfather said:
Ever find anything? I did the same thing, rooting was easy compared to trying to find any software/mods that don't look dicey at best. Still just got the same apks i used before i rooted LOL
Click to expand...
Click to collapse
No, nothing new .. As you mentioned, rooting is easy -- twrp is not a necessity.
IF YOU WANT TO UNLOCK YOUR PHONE READ THIS
had to ask moto for unlock code. waited 12 hours to receive reply, it went to spam folder (all previous did not)
oem unlock was not an option (there is an option in the developer menu to OEM unlock) . had to factory reset (using software of the OS itself, i did one with recovery and it did not unlock it....)
but wait .. it didn't unlock right away.. i had to unlock developer settings.. then go into developer settings... then TURN OFF DEVELOPER SETTINGS .. and OEM UNLOCK suddenly was selectable .. I CLICKED IT..
for root...
this is RETUS channel is retail us .. if you backup in the directory you can get all others
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
this appears to be an official repository, i was able to use the boot.img with magisk and root
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
i hear not doing this will boot loop, i just did it
and that command can only be entered in fastboot, not fastbootd
this was a 'factory unlocked' phone purchased from target
I Started to make a TWRP Recovery the files are on My gitlab and Mu github. I was able to make a tonga device tree for TWRP. That's a start.
Dana Silva / Tonga · GitLab
Tonga
gitlab.com
And
GitHub - 6thstring/android_device_motorola_tonga
Contribute to 6thstring/android_device_motorola_tonga development by creating an account on GitHub.
github.com
Now that you have a device tree for your device, it's time to build a TWRP recovery imageClone minimal TWRP environment
Follow the instruction in this page
GitHub - minimal-manifest-twrp/platform_manifest_twrp_omni: Minimal manifest for building TWRP for devices shipped with Android 5.1 through Android 9.0
Minimal manifest for building TWRP for devices shipped with Android 5.1 through Android 9.0 - GitHub - minimal-manifest-twrp/platform_manifest_twrp_omni: Minimal manifest for building TWRP for devi...
github.com
Remember to clone the correct version of TWRP based on what Android version your phone have! If your phone have Android 8.0, clone twrp-8.0 branch
Move device tree to TWRP sources
Copy working/(brand)/(device) folder to device/(brand)/(device) folder in TWRP sources
Example:
brand name: xiaomi
device codename: whyred
Copy working/xiaomi/whyred to device/xiaomi/whyred in TWRP sources
Building
Open a terminal with the current dir pointing to TWRP sources root
Then type
. build/envsetup.sh
to initialize the environment
After that, type
lunch omni_codename-eng
where codename is the codename of your phone
If that is successful, type
mka recoveryimage
to build the recovery.
If your device is A/B, use instead
mka bootimage
If also that is successful, congratulation!
Go to out/target/product/codename/ (codename is your device codename) and you will find your recovery.img
Go to [[5. Boot the recovery image]]
Good Luck
Can't believe this phone didn't get TWRP after all this time... Seems like a good phone for a custom rom.