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
Related
Don't forget to hit the thanks button.
http://superstarmobility.weebly.com/
New thread: http://forum.xda-developers.com/android/development/twrp-m1-lg-k7-t3462130.
(Above TWRP can be flashed with Flashify from Playstore)
Instructions from video:
With phone powered off, hold POWER and VOLUME DOWN buttons until LG logo shows. Release POWER then quickly press and hold again until factory reset menu comes up. Select YES and you will be booted into recovery instead of a factory reset ; )
Thanks @czarsuperstar!
V2 with the proper cmd line from m1 aka LG K7
Reserved.
This the real deal?
goitalone said:
This the real deal?
Click to expand...
Click to collapse
Of course. You looked at the video?
goitalone said:
This the real deal?
Click to expand...
Click to collapse
I've used it and can confirm, first tested it with fastboot without flashing of course(use adb to get to the bootloader: adb reboot bootloader , then fastboot:fastboot boot "twrp.img file, tested then rebooted into bootloader, then flashed via fastboot:fastboot flash "twrp.img file") instructions are for any random person that come by i know you know how to do all this
concerned xda citizen
what are the boardconfig.mk file contents that you used to compile this recovery?
the fact youre using a ghetto hacked twrp that works is fine, but id prefer an actual device specific twrp version that will reliably work - theres no telling what this twrp can do to your device, and the fact youre using another devices ramdisk scares the hell out of me.
ramdisks arent something you play around with - you can seriously ruin someones device like that.
also requesting the twrp fstab file youve used.
youre literally just throwing files at users that have perviously bricked their devices and not explaining in detail what they consist of.
if you seriously damage any of these user's device partitions by overwriting the wrong partition, are you going to pay for the devices when theyre hardbricked and no longer responsive to the oem flashing?
not once have a even seen a warning on these files yet youre just posting forum to forum; not to mention youre inexperienced at rom/kernel/recovery compiling for the fact you think its okay to just throw a different devices ramdisk in there " because it just works." when we have readily available source for our device.
legally- youre held responsible for these files youre distributing.
and to those just flashing this twrp file to their device, yes its reversible - but would you want to find out it doesnt work when its too late? IE backing up partitions in the wrong order, and restoring them into the wrong partitions? the video shows it backs up and restores, but is it doing so in the right order? in the right places. i may be ranting but id rather be careful/safe then sorry.
not one detail of this compile/build has been released, just a link that is claimed to work.
"left sock fits on right, doesnt feel right - but my feet aren't cold!" is how this feels to me.
i was sketched to even test this twrp version considering you need to tell the factory reset "yes, i want to wipe" twice, in order to boot to twrp.
idk about you but ive never seen any recovery warrant those options. normally twrp would just boot upon button combo - which is why im sharing this post. recoveries arent supposed to be functioning that way.
NASSTYROME said:
what are the boardconfig.mk file contents that you used to compile this recovery?
the fact youre using a ghetto hacked twrp that works is fine, but id prefer an actual device specific twrp version that will reliably work - theres no telling what this twrp can do to your device, and the fact youre using another devices ramdisk scares the hell out of me.
ramdisks arent something you play around with - you can seriously ruin someones device like that.
also requesting the twrp fstab file youve used.
youre literally just throwing files at users that have perviously bricked their devices and not explaining in detail what they consist of.
if you seriously damage any of these user's device partitions by overwriting the wrong partition, are you going to pay for the devices when theyre hardbricked and no longer responsive to the oem flashing?
not once have a even seen a warning on these files yet youre just posting forum to forum; not to mention youre inexperienced at rom/kernel/recovery compiling for the fact you think its okay to just throw a different devices ramdisk in there " because it just works." when we have readily available source for our device.
legally- youre held responsible for these files youre distributing.
and to those just flashing this twrp file to their device, yes its reversible - but would you want to find out it doesnt work when its too late? IE backing up partitions in the wrong order, and restoring them into the wrong partitions? the video shows it backs up and restores, but is it doing so in the right order? in the right places. i may be ranting but id rather be careful/safe then sorry.
not one detail of this compile/build has been released, just a link that is claimed to work.
"left sock fits on right, doesnt feel right - but my feet aren't cold!" is how this feels to me.
i was sketched to even test this twrp version considering you need to tell the factory reset "yes, i want to wipe" twice, in order to boot to twrp.
idk about you but ive never seen any recovery warrant those options. normally twrp would just boot upon button combo - which is why im sharing this post. recoveries arent supposed to be functioning that way.
Click to expand...
Click to collapse
The first twrp was from a htc phone. This is from lg leon lte. Same manufacturer. I used my boot.img dumped on my sdcard and used the ramdisk from Twrp Leon aka c50 the leon twrp is missing the options seen on this one. Don't use it. But I'm working on cm_m1 so continue to use the old one and when your phone can't come on have fun getting in recovery. Make it better.
Recovery log
Make a log.
NASSTYROME said:
what are the boardconfig.mk file contents that you used to compile this recovery?
the fact youre using a ghetto hacked twrp that works is fine, but id prefer an actual device specific twrp version that will reliably work - theres no telling what this twrp can do to your device, and the fact youre using another devices ramdisk scares the hell out of me.
ramdisks arent something you play around with - you can seriously ruin someones device like that.
also requesting the twrp fstab file youve used.
youre literally just throwing files at users that have perviously bricked their devices and not explaining in detail what they consist of.
if you seriously damage any of these user's device partitions by overwriting the wrong partition, are you going to pay for the devices when theyre hardbricked and no longer responsive to the oem flashing?
not once have a even seen a warning on these files yet youre just posting forum to forum; not to mention youre inexperienced at rom/kernel/recovery compiling for the fact you think its okay to just throw a different devices ramdisk in there " because it just works." when we have readily available source for our device.
legally- youre held responsible for these files youre distributing.
and to those just flashing this twrp file to their device, yes its reversible - but would you want to find out it doesnt work when its too late? IE backing up partitions in the wrong order, and restoring them into the wrong partitions? the video shows it backs up and restores, but is it doing so in the right order? in the right places. i may be ranting but id rather be careful/safe then sorry.
not one detail of this compile/build has been released, just a link that is claimed to work.
"left sock fits on right, doesnt feel right - but my feet aren't cold!" is how this feels to me.
i was sketched to even test this twrp version considering you need to tell the factory reset "yes, i want to wipe" twice, in order to boot to twrp.
idk about you but ive never seen any recovery warrant those options. normally twrp would just boot upon button combo - which is why im sharing this post. recoveries arent supposed to be functioning that way.
Click to expand...
Click to collapse
Check out the LG L70 it's the same way to get in recovery. This must be your first LG phone.
i dont care whether its the same way to enter recovery, my care is youre using another phone's ramdisk in this device.
"I used my boot.img dumped on my sdcard and used the ramdisk from Twrp Leon aka c50 the leon"
post twrp.fstab and boardconfig.mk youve used for this "twrp" build.
this must be your first posting for development on an unsupported device.
as for anyone using another device's files when we have access to source of our own device - i wouldnt trust them to build anything, let alone CM. thats just pure shortcutting and laziness .. and at what expense?
as for twrp making this official, they wont - as you cannot provide SOURCE.
So, now, hopefully you've compiled TWRP for your device and gotten it working. Now, you'd like to know how to get TWRP officially supported for your device so that it can be installed automatically with GooManager. In order for us to add "official support" for your device we'll need the following:
1) Device configuration files to compile TWRP from source for your device. This means that you cannot have repacked a recovery.img by hand to get it working. We need to be able to compile it from source so that we can easily release future updates.
2) A copy of a build prop for your device (it's in /system/build.prop) so that we can add the correct device information to GooManager
3) We'll build a copy of TWRP and send it to you for validation. Once you've validated that we can build a working image for your device, we'll add it to GooManager.
Go spam the other thread. Over 200 downloads and no problems but there was problems right away with the first version. For your info download Twrp c50 from the Twrp site examine it and ask why it's incomplete. That's why I linked the video of the Twrp from the site and same problems. Bye and leave me be. Hd2 check it out. Czarsuperstar's HTC HD2 android custom roms. Check it out and leave me alone. Thanks for your concern. Oh and for your info we have the same keyboard configuration as the LG Leon. There's a device tree. Google it. Google is your friend bro.
NASSTYROME said:
i dont care whether its the same way to enter recovery, my care is youre using another phone's ramdisk in this device.
"I used my boot.img dumped on my sdcard and used the ramdisk from Twrp Leon aka c50 the leon"
post twrp.fstab and boardconfig.mk youve used for this "twrp" build.
this must be your first posting for development on an unsupported device.
as for anyone using another device's files when we have access to source of our own device - i wouldnt trust them to build anything, let alone CM. thats just pure shortcutting and laziness .. and at what expense?
as for twrp making this official, they wont - as you cannot provide SOURCE.
So, now, hopefully you've compiled TWRP for your device and gotten it working. Now, you'd like to know how to get TWRP officially supported for your device so that it can be installed automatically with GooManager. In order for us to add "official support" for your device we'll need the following:
1) Device configuration files to compile TWRP from source for your device. This means that you cannot have repacked a recovery.img by hand to get it working. We need to be able to compile it from source so that we can easily release future updates.
2) A copy of a build prop for your device (it's in /system/build.prop) so that we can add the correct device information to GooManager
3) We'll build a copy of TWRP and send it to you for validation. Once you've validated that we can build a working image for your device, we'll add it to GooManager.
Click to expand...
Click to collapse
not saying a official twrp isn't preferable, but man you got to learn how to talk to people, you were just short of cursing the dude out, and as far as the recovery the thing is solid(tested backup, flash and restore/ anyhow we got LGUP if you **** up so its not a huge deal), but anyone on this site shouldn't take someones word for things like recovery's and you should always test boot before you flash, also you don't seem to understand the first rule of xda-whatever happens to your device is on you, been that way since the og day's- talking politely to others is the way to go about things, people wont listen if you combative.
Kernel
Im building the kernel from source right now check out the video on Twitter. Anyone that wants to join the development I am down with it.
Didn't work, after selecting yes twice, my phone just starts like normal, doesn't go to TWRP or factory restore, it is there though because I can boot to it from the flashify app, ah well.
wait...my bad, I was highlighting the wrong one, lol, works great, thanks
Assuming it ever worked right it should work better now because you can always get to it.
As for concerns about the ramdisk I don't see any issues with that, it's just being used to boot and run recovery on if I'm not mistaken and apparently where the buttons get enabled so a necessity.
Considering many phones have such hacked together recoverys and many more have no custom recovery I'm thankful to have it particularly since most of my work is done away from my pc.
callihn said:
Assuming it ever worked right it should work better now because you can always get to it.
As for concerns about the ramdisk I don't see any issues with that, it's just being used to boot and run recovery on if I'm not mistaken and apparently where the buttons get enabled so a necessity.
Considering many phones have such hacked together recoverys and many more have no custom recovery I'm thankful to have it particularly since most of my work is done away from my pc.
Click to expand...
Click to collapse
Thanks for report. The other Twrp w/o the button combo was from a HTC phone lol and I am getting blasted. HTC or LG? LG K7. ... LG.
[email protected] said:
Thanks for report. The other Twrp w/o the button combo was from a HTC phone lol and I am getting blasted. HTC or LG? LG K7. ... LG.
Click to expand...
Click to collapse
Right and that's why the buttons didn't work. Great job! Best discovery yet for this phone, so happy that we can restore now withoit adb and withoit having to worry about debugging getting turn off, very essential find. Don't let those that don't understand get you down.
callihn said:
Right and that's why the buttons didn't work. Great job! Best discovery yet for this phone, so happy that we can restore now withoit adb and withoit having to worry about debugging getting turn off, very essential find. Don't let those that don't understand get you down.
Click to expand...
Click to collapse
I'm working on building it from source but keep getting errors and I'm trying it with another device that has Twrp (Moto E 2015) and followed the directions to the T and no luck. So I am trying......... Will let everyone know how it's going.
[email protected] said:
Im building the kernel from source right now check out the video on Twitter. Anyone that wants to join the development I am down with it.
Click to expand...
Click to collapse
kernel??????????????????????????
im down!
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.
**Edit: Be sure to read comments at the end of this post******
I've already posted this a few times but I figured I would try to save some people time who want/need to root from any security patch. This is a copy and paste from an answer I gave in another thread but it's a basic how to.
Install DSU sideloader app from playstore to boot a prerooted GSI then use Partitions Backup and Restore app from playstore to save copies on your device. Install magisk app and patch the extracted boot.img and then transfer backups along with the patched boot image to your PC for safekeeping and flash the patched boot.img in fastboot. You can rename any .bin files to .img to flash them if they get extracted as a .bin file. Check your settings in the partitions Backup and Restore app before starting the backup process. You can choose to save them in an easy to find directory and for me it was better to choose to save them RAW/uncompressed then just compress them all into a single archive rather than having a hundred separate archives for each individual partition because it makes it easier if you have to reflash things if you need to recover. You may want to disable battery optimization for the app because it takes a while to extract all the images doing a full backup but its well worth the wait time if it saves you from a brick later on.
I wish I had time to elaborate but hopefully someone else can take the time to elaborate and add to this for anyone needing step by step. I'm surprised nobody has done this already.
Credits to AndyYan for giving advice on the root method. I stole this from him and just made a post with a title that makes it easier to find since so many are still asking how to go about rooting their devices.
*****REQUEST TO COMMUNITY********
There are many who are already on August Security patch and i dont have time to update and post the newest images. So if you are on august patch and pull backups I ask that someone please be so kind as to upload a copy of your backup to Google Drive or a filehosting server of choice and post a new thread so that others can unbrick their devices.
*Please ***DO NOT include**** the following partitions*:
DEVINFO
DINFO
FRP
KEYMASTER_A
KEYMASTER_B
KEYSTORE
LOGDUMP
***MDM1M9KEFS1
***MDM1M9KEFS2
***MDM1M9KEFS3
***MDM1M9KEFS4
MODEMDUMP
OPLUS_SEC_A
OPLUS_SEC_B
RAWDUMP
SECDATA
STORSEC
USERDATA
VM-KEYSTORE
*** These partitions may/contain YOUR personal device info, DO NOT make these public***
You can make a new Google account for the sole purpose of uploading these for the community so as not to fill your own GDrive. Be sure to change permissions for the images to share with anyone who has the link. This would be very much appreciated by many.
*****Update 09/18/2022*****
Thanks to ctschrodinger88 & dmtec for posting more detailed instructions!!! you can find ctschrodinger88's instructions below, scroll down to the 5th post.
dmtec also posted instructions in another thread linked here: https://forum.xda-developers.com/t/august-boot-img.4491831/post-87426877
we are still in need of august modems if anyone cares to upload them to their drive and link them or any other filehosting service.
can you suggest me a pre rooted gsi rom please?
thanks
fictisio said:
can you suggest me a pre rooted gsi rom please?
thanks
Click to expand...
Click to collapse
i used crdroid but its buggy, launcher crashes but its useable, atleast to get this done and then be sure to discard it in the DSU sideloader notification when you reboot so the inactive slot is empty, it will make for easier updates/mods later
has anyone had luck flashing the file in this article? https://www.getdroidtips.com/oneplus-nord-2t-5g-firmware-flash-file-2/#google_vignette
I used the info provided and referenced here as a guide and some external pieces and have things working.
I'll caveat the following, I don't remember the current firmware version I started with, but I'll try to remember to update.
I have the Nord N20 5g, but not the T-mo branded one, though in looking at this, the concepts should be the same.
Base assumptions:
- If you haven't done these beforehand, stop and take care of it. Research if you need, but please DO NOT just keep going or copy, paste, and run, without understanding to some extent what you're doing. If you just run commands it can be much harder to fix later.
a. Your phones bootloader is unlocked. (If you haven't already done it, when you do, your data will be gone, so if you care, back it up NOW)
b. You have access to an Android terminal of some sort (adb or on-device terminal) and you know how to use it. Unless you absolutely can't use a computer for some reason, I would use adb, it makes data backup easier (IMO).
c. You have somewhere to store your backed up partitions (THIS IS IMPORTANT)
Step 0: Download a pre-rooted Generic System Image (GSI) to use. Put it in a good working directory. This page links to several. https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
I used the LineageOS image by @AndyYan
If you are wondering about the various file endings this is the basic version
Code:
<ARCH>_xyZ
<ARCH> can either be arm, a64 (arm32_binder64) or arm64
x can either be a or b
y can either be v, o, g or f
Z can be N or S
b = a/b
a = a-only
g = gapps
o = gapps-go
v = vanilla (no gapps included)
f = floss (free & open source apps instead gapps)
N = no superuser
S = superuser included
From: https://forum.xda-developers.com/t/teclast-t30-t1px-suitable-gsi-roms.4211427/
Step 1: Enable the Dynamic System Update (DSU) feature flag, you can follow the exact steps for this in this section https://developer.android.com/topic/dsu#feature-flag
If you are unsure, just run the `adb shell` command.
Step 2:
If the image you downloaded needs to be in ".gz" format. Some of the tools will handle alternate types, but that's because it rebundles it at ".gz", you can save some effort doing it yourself.
Code:
gzip -c [IMG_NAME]..img> [IMG_NAME].gz
Step 3: Push the image to the device
`adb push [IMG_NAME].gz /storage/emulated/0/`
This is where I switched from ADB to on-the-device.
Step 4: Download the DSU Sideloader: https://github.com/VegaBobo/DSU-Sideloader
You can do this with adb but I wasn't able to get it to run, so I went with the DSU Sideloader app above which made it much simpler.
Step 5: Run DSU Sideloader. You can follow the instruction there in the README. You will need to run a command that the app provides, either via adb or an emulator. Then you will reboot via the notification.
Step 6: [Once you reboot] Enable Developer tools in phone settings.
Step 7: BACKUP, BACKUP, BACKUP (Please do this now. It will help make life much, much better if you ever have an issue and need to reset.)
This was my process:
Bash:
adb shell
su
mkdir /sdcard/partitions
cd /dev/block/by-name/
for x in *; do dd if=/dev/block/by-name/$x of=/sdcard/partitions/$x ; done
# Note the collective size will be greater than the default space on the GSI boot, so you will want to separate things
# Back on local machine
mkdir [working_dir]
cd [working_dir]
adb pull /sdcard/partitions
# Your files from the adb command should populate the folder
mv [working_dir]/partitions/* [working_dir]/
# On device
rm /sdcard/partitions/*
# repeat the commands above as often as needed.
I don't know for sure all the files you will want to backup, but I pulled everything just to be safe. Keep them safe, because it is your safety net if you fall.
Step 8: Get boot_a or boot_b back on the device along with Magisk.apk (Please only download from here: https://github.com/topjohnwu/Magisk/releases)
Step 9: Install Magisk.apk (you can do this via
Code:
adb install ./magisk.apk
)
Step 10: Launch Magisk and install it to the book image stored on your sdcard.
Step 11: Pull the patched image to your local machine.
Code:
adb pull /sdcard/Download/magisk_patched-[stuff].img
Step 12: Boot phone to fastboot
Code:
adb reboot bootloader
Step 13: This is where there is an ideal and a real.
Ideal command
Code:
fastboot boot magisk_patched.img
where fastboot transfers the files and things just work, and if you reboot the system the regular boot.img is used. I haven't been able to get that to with this device.
I instead just ran
Code:
fastboot flash boot magisk_patched.img
which replaced the existing boot image, which is good, if it works, but if it doesn't, this is why you have backups!!!! Reboot the phone.
Step 14: When you boot, finish installing Magisk and you'll be ready to go.
If I remember other steps I'll add, or if you have questions I will try to help answer.
I just got a MetroPCS nord n20 (gn2200) and will try to root in the next couple days.
ScarletWizard said:
n20
Click to expand...
Click to collapse
Have they removed the unlock portal?
Damn, it's been a long time. Glad to be back.
ScarletWizard said:
No. My serial is 7 digits
Click to expand...
Click to collapse
seems to be a common defect.... if ur device is paid off oneplus can generate you a token but it takes weeks of back-and-forth with support to get it escalated...tmobile may or may not allow you to do that on a device that isnt paid off but i wouldnt even ask tmobile about it if your not paid off already, will only make it harder for those who are trying to unlock theirs if it IS the case that tmobile doesnt want you to unlock it until youve paid the device off in full....oneplus will probably uphold tmobiles decision if your device isnt paid off. for now, we are able to unlock tmobile devices through the portal regardless of the financial status of the device. though you will still be SIM locked unless tmobile unlocks that for you. and their definitely NOT gonna do THAT til it gets paid off.
U.S. carriers dont like customers having unlocked devices and is against most user-agreement policies and can get your service terminated leaving you owing for a device you cant use and for the price of the contract you were on for service
your device is a CPH2459 and not a GN2200?
fictisio said:
can you suggest me a pre rooted gsi rom please?
thanks
Click to expand...
Click to collapse
Andy Yan's Lineage18 or 19..
DrScrad said:
Andy Yan's Lineage18 or 19..
Click to expand...
Click to collapse
pixel experience, crdroid... havent gotten kaleidoscope to work yet. Have heard that someone got aosp a13 going.... There are so many and so long as u use a matching security patch ur good. might work with a newer patch but of the ones ive tried i got thw matching patches to work. If you find one thats on a newer patch in the gsi page you should be able to follow the link and find an older release to match the patch ur on. If ur on may patch try to find a may patch just to make it pess likepy that there will be priblems. If on july or august, likewise find july or august sec patch release. newer patched systems MIGHT work with ur older patched bootloader and other partitions(modems etc...) but def would not advise just straight flashing mismatching security patches... Best to sideload first and see if u can get it working first. Its not very simple to dual boot these devices but i think someone did some work and posted a work around for doing that on a/b devices somewhere on xda......
Am willing to share my stock image with anyone willing to help. I am on the September security update on a OnePlus Nord N20 5G unlocked (Non-Carrier). I am running version 11 and android security update 2022-09-05.
I am having real issues getting LineageOS through DSU. It fails immediately on start every time. Bootloader is unlocked, it even shows through fastboot (Secure boot = on though), flag is set per instructions, and I am trying to install lineage-19.1-20221011-UNOFFICIAL-arm64_bvS.gz . I tried two different versions of the DSU app but nada.
oromis995 said:
Am willing to share my stock image with anyone willing to help. I am on the September security update on a OnePlus Nord N20 5G unlocked (Non-Carrier). I am running version 11 and android security update 2022-09-05.
I am having real issues getting LineageOS through DSU. It fails immediately on start every time. Bootloader is unlocked, it even shows through fastboot (Secure boot = on though), flag is set per instructions, and I am trying to install lineage-19.1-20221011-UNOFFICIAL-arm64_bvS.gz . I tried two different versions of the DSU app but nada.
Click to expand...
Click to collapse
make sure u r using a lineage version with the same security patch as your current OS if your on September u need a GSI on september. i personally gave up on lineage after trying a couple but was successful with a few others while dsu sideloader still worked for me, im not sure what i did to break it on my devices but i havent been able to get it to work on either device in a while.
i have yet to try the october firmware but it should be easy to downgrade and root if you think its the new updates. although make sure ur disabling verity. u might wanna disable the checks on vbmeta_boot too... i usually just disable it on all 3 vbmeta's to be safe.... i have a full july dump and someone else has posted the august dump on TG but that doesnt help in your case since you have the CPH2459 and we are on GN2200's nobody has been able to successfully crossflash them yet and im not sure if it will be possible or not but everyone that has tried it has bricked their devices so far. most have gotten them running again but have lost fingerprint
ScarletWizard said:
im on gn2200
Click to expand...
Click to collapse
Ok my last upload didn't upload correctly for some reason. I will re upload tomorrow I think..... I need to figure out exactly which partitions are device-specific.... I know which partitions get updated in the incrementals so if all of them don't get flashed then everything won't match but I have a feeling that the incrementals update a device-specific partition or two and if so then u will lose fingerprint at minimum...... I think I should just pull full backup of all partitions and then go for it. Worst case so long as u do everything right. U just don't boot and have to reflash the stock boot image... Be sure to flash the stock image to both slots just in case and then switch back to ur active slot and flash the patched boot image. I mean if it was me I would b comfortable doing it but that's completely ur call, I don't wanna encourage anything because there ALWAYS a risk something could go wrong. Power outage or something and it's screwed up but any time u r flashing u will always be taking a risk. Though I think the risk is minimal so long as u do everything right and there's not much to the simple root process, patch the boot image and flash, if it doesn't work then reflash the stock one. If it DIES work out for u we would b grateful for the October firmware if u wanna share it, we didn't get October yet.
ScarletWizard said:
If it dies. Lol scary.
I'm in the process of doing the partition thing
Click to expand...
Click to collapse
If it DOES.. Sry
ScarletWizard said:
who is the ADMIN of this n20 thread?
Click to expand...
Click to collapse
Just look.for the moderator edits lol
PsYk0n4uT said:
seems to be a common defect.... if ur device is paid off oneplus can generate you a token but it takes weeks of back-and-forth with support to get it escalated...tmobile may or may not allow you to do that on a device that isnt paid off but i wouldnt even ask tmobile about it if your not paid off already, will only make it harder for those who are trying to unlock theirs if it IS the case that tmobile doesnt want you to unlock it until youve paid the device off in full....oneplus will probably uphold tmobiles decision if your device isnt paid off. for now, we are able to unlock tmobile devices through the portal regardless of the financial status of the device. though you will still be SIM locked unless tmobile unlocks that for you. and their definitely NOT gonna do THAT til it gets paid off.
U.S. carriers dont like customers having unlocked devices and is against most user-agreement policies and can get your service terminated leaving you owing for a device you cant use and for the price of the contract you were on for service
Click to expand...
Click to collapse
One small problem, although Metron PCS uses T-Mobile towers, they are their own entity and T-Mobile does not have their Bootloader codes. Only OnePlus and Metro PCS have the Metro PCS unlock.bin file. That's what I came here was to try and find a dedicated metro bootloader unlock web page. Like the T-Mobile dedicated page. There is not one so it's going too take several calls over several weeks unless some one here knows a different way or a link to a metro PCS bootloader unlock page? Anyone chime in on this and save all of us that are running in circles back down the straight path to an unlocked bootloader..
jayram1408 said:
One small problem, although Metron PCS uses T-Mobile towers, they are their own entity and T-Mobile does not have their Bootloader codes. Only OnePlus and Metro PCS have the Metro PCS unlock.bin file. That's what I came here was to try and find a dedicated metro bootloader unlock web page. Like the T-Mobile dedicated page. There is not one so it's going too take several calls over several weeks unless some one here knows a different way or a link to a metro PCS bootloader unlock page? Anyone chime in on this and save all of us that are running in circles back down the straight path to an unlocked bootloader..
Click to expand...
Click to collapse
I'm about to file a FCC complaint to get mine then.
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.
Digging around and researching other markets and communities that develop for the Legion series I stumbled upon a mostly working TWRP for the Y70. I believe it is possible to reverse engineer (decompile/decompress) the recovery and from there build an officially supported version for the community here at XDA. Credit will still be given to the original developer should they ever request it and guidelines for anything open source will be acknowledged throughout the whole process of porting this TWRP offered here.
More than likely upon first boot you'll want to change the language. It's pretty easy to figure out. A step by step guide will be posted to switch the language if necessary.
If you are fuzzy with the basic installation of this, here is a refresher:
fastboot getvar current-slot (which helps you determine which slot you are currently using)
fastboot flash recovery_(a or b) twrp_3.7.0-12.img
Be familiar with the basics and functionality TWRP offers and aware of any perils you may encounter from it's use (no one is responsible for what a user may install or instruct the device to do, besides the user from use or misuse of this). Questions, comments, and anything that assists the use and development of this recovery is really all this thread is for. Please don't flood the thread with anything else unrelated (you can make your own thread for any question/guide/development purpose).