Hey all,
I recently purchased a Unihertz Titan Pocket and I'm looking to try out LineageOS on it. I found this project on Github and have read through the instructions; however, they are for the *Unihertz Titan*, not the Pocket. I'm not sure they will work for the model I have and regardless, I'm wary about trying something that I know little about. Could anyone take a look at the link and let me know if the instructions could work for me?
Here are some additional links, for anyone else who is working on the same or similar goals:
-Official firmware and flash tool from Unihertz (for trying to restore bricked/messed up devices)
-Rooting Guide for Unihertz Titan Pocket
I am interested in flashing a custom ROM such as LineageOS onto my Unihertz Titan Pocket. It's my understanding that I will need custom recovery software such as TWRP in order to carry out the installation process. There is no official build of TWRP for the Unihertz Titan Pocket, and I haven't been able to find any unofficial builds for it either. So I have three questions:
1) Does anyone know of an unofficial TWRP build for my device?
2) Is there someone who might be able to create an unofficial build? I am willing to help as best I can, but my knowledge of how to do so is essentially null. I found this thread for the TWRP Builder project, which looked awesome, but seems to be defunct at this point. I also found this answer from a contributor to the project, who claims (as of 2021) that the project is on hiatus but "making a progressive return." The thread looks pretty dead to me though so it's hard to tell if they are back up and running in any capacity.
3) Is there another way to flash a custom ROM without TWRP? For example, these instructions (for a different model, the Unihertz Titan) don't mention using TWRP.
[For others with a Unihertz Titan Pocket, I asked about finding and installing a build of LineageOS on this device in another post here]
Kisa3908 said:
Hey all,
I recently purchased a Unihertz Titan Pocket and I'm looking to try out LineageOS on it. I found this project on Github and have read through the instructions; however, they are for the *Unihertz Titan*, not the Pocket. I'm not sure they will work for the model I have and regardless, I'm wary about trying something that I know little about. Could anyone take a look at the link and let me know if the instructions could work for me?
Click to expand...
Click to collapse
@Kisa3908 Welcome to XDA! I hope you'll always get the support you require.
Prior to your next posting please read the guidances that are stuck on top of every forum like
Note: Questions go in Q&A Forum
If you are posting a Question Thread post it in the Q&A forum. Technical discussion of Android development and hacking. No noobs, please. Device-specific releases should go under the appropriate device forum...
forum.xda-developers.com
I've moved the thread to Android Q&A. Additionally, I merged your other thread into this one. Please also review the XDA Forum Rules, to which you agreed to adhere when you registered a few hours ago, and post only ONCE respectively in an existing thread instead of creating a new one.
Thanks for your cooperation.
Regards
Oswald Boelcke
Senior Moderator
did the author succeed in his trials?
I am looking to obtain root on Pocket, but would rather have someone who has done it already guide me if necessary
I was able to install LineageOS on the Titan Pocket, following this tutorial:
Rooting Cubot KingKong Mini 2 | Deadbadger
Jakub Kaderka personal webpage, electronic hacking, projects,etc.
deadbadger.cz
What I am not able to do is to use the numbers on the physical keyboard, does anyone have an idea how to make it work? I assume it's something with the keyboard layout. I installed the KIkaInput.apk thinking that is the one missing, but still not working.
talmid01 said:
I was able to install LineageOS on the Titan Pocket, following this tutorial:
Rooting Cubot KingKong Mini 2 | Deadbadger
Jakub Kaderka personal webpage, electronic hacking, projects,etc.
deadbadger.cz
What I am not able to do is to use the numbers on the physical keyboard, does anyone have an idea how to make it work? I assume it's something with the keyboard layout. I installed the KIkaInput.apk thinking that is the one missing, but still not working.
Click to expand...
Click to collapse
There's a tool on github (look for uinput-titan-pocket on google, you should find it) that maybe can help! If you succeed in making the keyboard work could you please share the info? I want to get a lineageOS GSI but the Titan Pocket is my main phone so I need it to be fully functional.. Hope I helped!
EDIT: uinput is for the touch scrolling, this (https://github.com/SinuXVR/pocket-board) seems to be the solution to hat you asked.
talmid01 said:
I was able to install LineageOS on the Titan Pocket, following this tutorial:
Rooting Cubot KingKong Mini 2 | Deadbadger
Jakub Kaderka personal webpage, electronic hacking, projects,etc.
deadbadger.cz
What I am not able to do is to use the numbers on the physical keyboard, does anyone have an idea how to make it work? I assume it's something with the keyboard layout. I installed the KIkaInput.apk thinking that is the one missing, but still not working.
Click to expand...
Click to collapse
Can you tell me what ROM do you use? There are many.
diejuse said:
Can you tell me what ROM do you use? There are many.
Click to expand...
Click to collapse
Andy Yan's personal builds // GSI - Browse /lineage-18.x at SourceForge.net
sourceforge.net
Also to have the right keyboard settings you need to edit the keylayout files.
talmid01 said:
Andy Yan's personal builds // GSI - Browse /lineage-18.x at SourceForge.net
sourceforge.net
Also to have the right keyboard settings you need to edit the keylayout files.
Click to expand...
Click to collapse
Can you edit /system/usr/keylayout with LineageOS? I can't edit it with stock rom?
There are any problem? All is working?
Can you explain the steps to install it?
Download the latest bvS version of GSI Lineage from this folder:
https://sourceforge.net/projects/andyyan-gsi/files/lineage-18.x/
Enter Settings->Phone info and tap several times on the Build number, now in Settings->System->For Developers allow Debug over USB and Bootloader unlock
Connect to PC with android SDK installed and run adb reboot bootloader, you'll need to confirm device authorization on your phone.
Once in bootloader, run fastboot flashing unlock to unlock the bootloader and follow the instructions on your phone (this step factory resets the phone, you'll loose all your data).
Download the official stock ROM and unpack the downloaded rar. (
https://www.reddit.com/r/unihertz/comments/r2dz0a
)
In the directory with unpacked ROM, run fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img to flash the vbmeta.img with disabled Android Verified Boot to allow flashing unofficial ROMs.
Reflash the recovery and boot partitions by running fastboot flash boot boot.img and fastboot flash recovery recovery.img. Technically this shouldn't be needed, but if your phone is running a different stock ROM version, it's advisable.
fastboot reboot fastboot reboot to fastboot, the system can be flashed only from this mode, for some reason it doesn't work in the previous mode...
Now you can flash the system.img by running the fastboot flash system YOUR_SYSTEM_IMAGE.img. Select system.img file from the ROM you want to flash.
fastboot reboot and you are booted in your new ROM!
Once it is booted into Lineage enable Rooted ADB debugging in the Developer Settings. Now we need to fix the keyboard settings. Download and install the following apk:
com.blackberry.keyboard-4.1904.2.16698.apk
drive.google.com
Then disable the soft keyboard in the Settings.
Download https://github.com/SolidHal/Unihertz-Titan-lineageos-microg
adb root
adb remount
adb shell mount -o remount,rw /
adb push system_usr_idc/* /system/usr/idc/
adb push system_usr_keychars/* /system/usr/keychars/
adb push system_usr_keylayout/* /system/usr/keylayout/
Then restart your phone. I hope it will work for you.
On the Pocket, the system partition is called "Super".
The command should then be "fastboot flash super (My System ROM.img)...". Correct?
Medionato said:
On the Pocket, the system partition is called "Super".
The command should then be "fastboot flash super (My System ROM.img)...". Correct?
Click to expand...
Click to collapse
The Titan Pocket and Titan Slim use a super partition, which has a number of different .img files embedded inside of it. You can flash the super.img to your super partition from the stock rom zip, but you can't just flash system alone, you need to repackage the super.img in order to then flash it. I am working on a number of projects for the Titan series, i just ordered a Slim this morning, so i will get to work detailing the differences in the process between the Titan and the Titan Slim (which will mostly be transferable to the Titan Pocket, at least i expect so).
I also flashed Andy Yan's personal build of lineage-18.1-20220715-UNOFFICIAL-arm64_bvS.img on my Titan Pocket. It booted up, but with one problem: mobile communication does not work at all: the SIM is recognised correctly, but it is completely disconnected from the mobile network and shows 'emergency call only'.
I have flashed the image using the following steps:
fastboot flashing unlock
fastboot -w
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot reboot fastboot # I don't know the details, but the Titan Pocket cannot flash system in Bootloader mode.
fastboot flash system lineage-18.1-20220715-UNOFFICIAL-arm64_bvS.img
fastboot reboot
I have been struggling with this problem for a month now and am stuck. Does anyone have any information on this? Thanks.
argxentakato said:
I also flashed Andy Yan's personal build of lineage-18.1-20220715-UNOFFICIAL-arm64_bvS.img on my Titan Pocket. It booted up, but with one problem: mobile communication does not work at all: the SIM is recognised correctly, but it is completely disconnected from the mobile network and shows 'emergency call only'.
I have flashed the image using the following steps:
fastboot flashing unlock
fastboot -w
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot reboot fastboot # I don't know the details, but the Titan Pocket cannot flash system in Bootloader mode.
fastboot flash system lineage-18.1-20220715-UNOFFICIAL-arm64_bvS.img
fastboot reboot
I have been struggling with this problem for a month now and am stuck. Does anyone have any information on this? Thanks.
Click to expand...
Click to collapse
Your steps look questionable. Titan Pocket and Titan Slim dont have flashable system partitions. As noted above they have super partitions.
Hi everyone, Im new here and will start by saying I've never successfully installed a custom ROM, so I'm heavily in the research phase.
I have a Titan Pocket in route and is my goal to set it up with a new os and trashcan Google for good. I'm at a toss-up right now between LineagOS or GrapheneOS.
From what I've read so far, Graphene is only "officially" supported for Google pixel phones. Does anyone know if it can still work on the Pocket?
If not I might default to Lineage and follow the advice in this thread. I'm also open to any suggestions for security base ROMs I should consider. TIA.
Related
Hello guys,
I have a problem with my OnePlus X, and it would be lovely if I could get some help or advice from you guys.
> To provide some slight background, I purchased this off of eBay to complete my OnePlus collection. Most listings were above what OnePlus originally sold the phone for, but I found one for $125 in good condition by a seller with a good rating. It was advertised as soft-bricked, with Fastboot in working order. I thought "no problem, I'll just reflash it and be on my merry way."
Now onto the issue. I received it, charged it up, and attempted flashing the official recovery provided by OnePlus, but something is not working. I've been tinkering with Android for a number of years now, so I troubleshooted as much as I could, but to no avail.
1. Starting with device unplugged and powered off, boot into fastboot
2. Plugged into the computer, and ran `fastboot devices` to ensure it's recognized. After that, I flashed the recovery.img that was on my desktop with `fastboot flash recovery recovery.img` (yes I was in the correct directory). It looked successful. Picture of cmd response text at the following imgur album: /a/25DEQ (sorry I cannot post full links yet, had to create a new xda profile, forgot my old one :/
3. Unplugged the phone, powered off, Volume Down + Power to attempt boot into recovery. Failure. It just turns on with the 1+ logo, and quickly flashes the 'android' logo at the bottom. It stays like this until I manually power off.
I'm a bit stumped I have to admit. I would greatly appreciate any input you folks have. Thank you.
AndriyEtch said:
Hello guys,
I have a problem with my OnePlus X, and it would be lovely if I could get some help or advice from you guys.
> To provide some slight background, I purchased this off of eBay to complete my OnePlus collection. Most listings were above what OnePlus originally sold the phone for, but I found one for $125 in good condition by a seller with a good rating. It was advertised as soft-bricked, with Fastboot in working order. I thought "no problem, I'll just reflash it and be on my merry way."
Now onto the issue. I received it, charged it up, and attempted flashing the official recovery provided by OnePlus, but something is not working. I've been tinkering with Android for a number of years now, so I troubleshooted as much as I could, but to no avail.
1. Starting with device unplugged and powered off, boot into fastboot
2. Plugged into the computer, and ran `fastboot devices` to ensure it's recognized. After that, I flashed the recovery.img that was on my desktop with `fastboot flash recovery recovery.img` (yes I was in the correct directory). It looked successful. Picture of cmd response text at the following imgur album: /a/25DEQ (sorry I cannot post full links yet, had to create a new xda profile, forgot my old one :/
3. Unplugged the phone, powered off, Volume Down + Power to attempt boot into recovery. Failure. It just turns on with the 1+ logo, and quickly flashes the 'android' logo at the bottom. It stays like this until I manually power off.
I'm a bit stumped I have to admit. I would greatly appreciate any input you folks have. Thank you.
Click to expand...
Click to collapse
Which recovery u tried? Did u knOw the previous os version details?
And try this after flashing recovery in fastboot, boot into it directly by giving a cmd "fastboot boot recovery.img"
cva_kabil said:
Which recovery u tried? Did u knOw the previous os version details?
And try this after flashing recovery in fastboot, boot into it directly by giving a cmd "fastboot boot recovery.img"
Click to expand...
Click to collapse
Hi! Thank you for your reply
I posted this same question on the /r/oneplus subreddit, and received a quick and helpful walkthrough. Turns out part of the problem was that the micro-usb port on the phone itself is a bit unreliable. I haven't investigated too deeply, but it took a while to find a position for the wire to maintain a stable connection. I suspect this may be why the device was bricked in the first place (disconnect when flashing rom/kernel/etc.)
Anyways, for some reason flashing the stock recovery to the phone was just not working. The guy on reddit recommended trying TWRP, and that worked immediately. However, at that point, I had no idea what the history of the phone was or what OS was on it before, what firmware it had. I tried installing the official CM13 and then Sultan's CM13 with no luck. What *did* work was Oxygen OS 2.2.6.
At this point I'm stuck yet again though... The Marshmallow OTA (3.1.3) in the OS shows as available for download, but when I try to install the download only gets to 22% and then stops. Flashing the 3.1.3 OTA.zip available on OnePlus' support site doesn't work in TWRP, and when I try to flash stock recovery, it doesn't work.. don't know what else to try.
AndriyEtch said:
Hi! Thank you for your reply
I posted this same question on the /r/oneplus subreddit, and received a quick and helpful walkthrough. Turns out part of the problem was that the micro-usb port on the phone itself is a bit unreliable. I haven't investigated too deeply, but it took a while to find a position for the wire to maintain a stable connection. I suspect this may be why the device was bricked in the first place (disconnect when flashing rom/kernel/etc.)
Anyways, for some reason flashing the stock recovery to the phone was just not working. The guy on reddit recommended trying TWRP, and that worked immediately. However, at that point, I had no idea what the history of the phone was or what OS was on it before, what firmware it had. I tried installing the official CM13 and then Sultan's CM13 with no luck. What *did* work was Oxygen OS 2.2.6.
At this point I'm stuck yet again though... The Marshmallow OTA (3.1.3) in the OS shows as available for download, but when I try to install the download only gets to 22% and then stops. Flashing the 3.1.3 OTA.zip available on OnePlus' support site doesn't work in TWRP, and when I try to flash stock recovery, it doesn't work.. don't know what else to try.
Click to expand...
Click to collapse
Root your device using twrp or kingoroot method then install flashify and try to flash stock recovery using flashify. .. Tht may work.
Flashing 3.1.3 via official twrp ll not work... Cos ur bootloader version, U can do it only with stock recovery or u need to edit meta data file. Or u can flash stock recovery img file by twrp
cva_kabil said:
Root your device using twrp or kingoroot method then install flashify and try to flash stock recovery using flashify. .. Tht may work.
Flashing 3.1.3 via official twrp ll not work... Cos ur bootloader version, U can do it only with stock recovery or u need to edit meta data file. Or u can flash stock recovery img file by twrp
Click to expand...
Click to collapse
Thanks I'll give those a shot once I'm home from work! Quick question about editing the META INF. I've heard that doing so risks hard-bricking the device. Is that true?
AndriyEtch said:
Thanks I'll give those a shot once I'm home from work! Quick question about editing the META INF. I've heard that doing so risks hard-bricking the device. Is that true?
Click to expand...
Click to collapse
I dont think so... I hv not tried... But as of i know if u edit it wrongly, u will not be able to flash that file. . Try others methods first... Hope it works
AndriyEtch said:
Thanks I'll give those a shot once I'm home from work! Quick question about editing the META INF. I've heard that doing so risks hard-bricking the device. Is that true?
Click to expand...
Click to collapse
Hi OP, sorry for joining late to the party
So the thing is the OnePlus X is at opposites now since the official MM release on 29th September. The thing is if you are running the old bootloader (OxygenOS 2.x.x) or any ROM based on it, then the New TWRP will not boot, neither will the Stock Recovery that is hosted on the OnePlus download section for the X, which is where i assume you download the stock recovery from, right ? Also note that the official recovery hosted on the TWRP website is also yet to be updated, we're working on that.
So you are on the old Bootloader. Simple stuff. I have posted my guide a lot of time around the forums, its gained a lot of merit. You could follow it for your update process. I'll leave a link below. In case you wanna verify that the old bootloader is causing the issue my Index Thread pinned in the general section has a link for the Stock recovery for Old bootloader, try flashing that via fastboot, if it successfully boots then you're set.
Comprehensive guide to Update to Marshmallow Bootloader
The above guide is centered to the thread i have posted it on but the process is 99% the same. In the end, you could just stay with Oxygen OS 3.1.3, or flash any custom ROM based on the new Bootloader.
Now regarding your query about editing the META of the ROM, well Yes to an extent it IS risky if you ain't careful because my guide guides you to delete the one single line that removes the device check, so as long as you use the modified zip on OnePlus X only, there will be no issues.
Let me know for any further clarifications, also you're welcome to join our support group on Telegram, all of our developers are active there. Ping me (@ mellogang_unite) for an invite
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
Just picked up this device a couple of weeks ago and decided to look into rooting. I've read over a large amount of web pages just soaking up any information on the device I could. I also read over the root guide in this forum and I am aware they are not the exact same model but I've got it down to the tar file with boot.img and the 2 other files in it. My question: is there a way I can flash files to this Samsung without Odin because I do not have access to a pc at the moment. Is it possible to install heimdall command line through termux on my oneplus or Motorola that I already have root access on? That's what I would normally do. Just connect 2 phones with a c cable and use the rooted one like a pc. It has its limitations but it works for the most part. I even tried doing that with this Samsung but fastboot/download mode doesn't recognize fastboot commands. If anyone had any input at all it's appreciated.
Off topic but has anyone been having problems with termux repos lately?
I've attached stock recovery modified by phh to include fastbootd.
It was stock android 10 for A025G BTU
Thank you very much bro. If I remember correctly this still needs to be flashed with fast boot commands so I still need to flash this recovery with Odin but after that I'll be good to go with fastboot? Sorry, very new to Samsung
CFKod said:
I've attached stock recovery modified by phh to include fastbootd.
It was stock android 10 for A025G BTU
Click to expand...
Click to collapse
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.
I'm new to forums, I apologize if this is all wrong and such. I was wondering if there is a way I can root a MetroPCS TCL IonX (T430W) running android 12 with magisk. I can't find anything for the IonX, it's all other variants of "Ion." I'm quite familiar with rooting and such, I'm just looking for the files, twrp or such. If you know where I can get them, please lemme know.
I'm sorry if this is in the wrong spot. I didn't see anything for TCL devices, I've never used forums before.
Hi! I don't see your particular device, but here (link below this paragraph) is where you can find all TCL devices we do have sections for. I am not knowledgeable about TCL, otherwise I'd help you myself, and these days on my Pixel, I don't even use TWRP to root - just Magisk, but I know this varies depending on the device and the files that are available. Hopefully, someone in one of the other TCL device sections can help you.
TCL
forum.xda-developers.com
If you ever get a different brand device, you can look for your device or your brand at the top level of the forum https://forum.xda-developers.com/. In the middle of the screen, there is All categories, which you can either expand to see a condensed copy of the brands and links to their sections, or click on it and it'll take you to a more expanded view of all brands we have forum sections for.
You can also use the following thread to request new device forums. There's no guarantee one would be created, but if there's enough demand, it might be.
*** New Device Forum Requests ***
Please post all your requests here. The forum admins choose new device forums carefully, based on several factors. There's no guarantee your device will have a forum created here, but feel free to posts your requests in this thread :) Please do...
forum.xda-developers.com
roirraW edor ehT said:
Hi! I don't see your particular device, but here (link below this paragraph) is where you can find all TCL devices we do have sections for. I am not knowledgeable about TCL, otherwise I'd help you myself, and these days on my Pixel, I don't even use TWRP to root - just Magisk, but I know this varies depending on the device and the files that are available. Hopefully, someone in one of the other TCL device sections can help you.
TCL
forum.xda-developers.com
If you ever get a different brand device, you can look for your device or your brand at the top level of the forum https://forum.xda-developers.com/. In the middle of the screen, there is All categories, which you can either expand to see a condensed copy of the brands and links to their sections, or click on it and it'll take you to a more expanded view of all brands we have forum sections for.
You can also use the following thread to request new device forums. There's no guarantee one would be created, but if there's enough demand, it might be.
*** New Device Forum Requests ***
Please post all your requests here. The forum admins choose new device forums carefully, based on several factors. There's no guarantee your device will have a forum created here, but feel free to posts your requests in this thread :) Please do...
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks man, I'll see if I can get help. More or less, I need the firmware, I can do it if I have it. Thanks once again
DrAkuma said:
Thanks man, I'll see if I can get help. More or less, I need the firmware, I can do it if I have it. Thanks once again
Click to expand...
Click to collapse
You're welcome! I hope you can find it.
roirraW edor ehT said:
You're welcome! I hope you can find it.
Click to expand...
Click to collapse
Definitely looking. Thanks for the quick reply.
DrAkuma said:
I'm new to forums, I apologize if this is all wrong and such. I was wondering if there is a way I can root a MetroPCS TCL IonX (T430W) running android 12 with magisk. I can't find anything for the IonX, it's all other variants of "Ion." I'm quite familiar with rooting and such, I'm just looking for the files, twrp or such. If you know where I can get them, please lemme know.
I'm sorry if this is in the wrong spot. I didn't see anything for TCL devices, I've never used forums before.
Click to expand...
Click to collapse
I have the T430W as well and after a month of trial and error I was able to get it rooted with magisk. I'll give you the quick summary of how I did it right now and once I get home from work I will try to get a more complete step by step guide for you.
1. Download and setup mtkclient by bkerler on github.
2. Enable usb debugging and oem unlock in developer options
3. Power off device
4. Open a terminal and mtk meta --metamode FASTBOOT
5. Plug phone up to computer. You should see the TCL logo and then black screen with fastboot mode in lower left corner.
6. fastboot flashing unlock and confirm on device with volume keys(WARNING this will erase your userdata)
7. Install LineageOS pre rooted GSI using DSU sideloader from github.
8. Either use a partition backup or adb shell then dd if=/dev/block/by-name/boot of=/sdcard/boot.img
9. Reboot to return to original system.
10. Patch boot image with magisk manager make sure the disable vbmeta option is selected.
11. Repeat steps 3 & 4
12. fastbooot --disable-verity --disable-verification flash vbmeta vbmeta.img {flash blank vbmeta image(I used the one from the google source page for DSU)}
13. fastboot flash boot /path/to/magisk_patched_img
14. Reboot and enjoy your rooted Ion X.
Or if you would like I can upload either the stock boot image or magisk patched image as long as you have done the UG67 OTA update.
We have no DA or AUTH files for SP Flash Tool and none of the current bypass methods work on our chipset, so whatever you do make sure you do not flash mmcblk0boot0 or mmcblk0boot1 as this will render your device hard bricked. The kernel source is available on sourceforge, I have gotten it to compile with no errors but haven't had a chance to test it yet. I'm working on getting TWRP or OFRP for our device compiled but haven't gotten very far. So far I haven't had any issues being rooted on the stock rom. I'm really glad that you posted this because I have been meaning to type up a guide as I believe being able to root your phone should be an option for everyone, but you posting this gave me the kick in the rear to actually do it.
Here is the stock boot and magisk patched boot image plus the blank vbmeta image