Is anybody trying the root this phone? - Moto G 2015 Q&A, Help & Troubleshooting

Is anybody trying to root this phone? I just bought this phone to learn android development and up my skills in it. I currently don't have that much experience that I can root a device myself, but I would like to learn.
Anyways, Please let us know if you are developing a way to root the device. I would be happy to help in every possible way I could.

It shouldn't be hard to port my surnia (2015 Moto E LTE) TWRP recovery to this device (osprey). Just change the device name to osprey and update the resolution in BoardConfig.mk
See my device tree for it:
https://github.com/sultanqasim/android_device_motorola_surnia/tree/twrp
I can make a build of my recovery with these minor modifications if you're willing to try it out. I can't promise it will work and not mess up your device, since I don't have it to test on.

I will give it a try since we have factory images now.

Working on it:
https://github.com/sultanqasim/android_device_motorola_osprey
----------------------------------------
Test build is up:
http://forum.xda-developers.com/2015-moto-g/orig-development/twrp-twrp-moto-g-2015-t3170537

Related

we need safestrap for t337a!

AT&T locks us out, is safestrap the way in?...​
Total noob here. Will be researching how safestrap works. If anyone knows where I can find out how safestrap works please share. I am also going to try see if I can enlist help from devs who got it working on sgs5 and similar devices... has anyone tried safestrap for t337a?
Any help/info is appreciated
Already got a dev trying to port it for our 337a. [emoji106]
Hey guys. I have the t377a. Is there a root method for NK2? I have looked everywhere and have found nothing.
pre4speed said:
Already got a dev trying to port it for our 337a. [emoji106]
Click to expand...
Click to collapse
Happy New Year !
okay, i tried faking it with safestrap and so far it's booting me to my actual recovery....which is annoying.
scouring through hashcode's stuff on git and wondering if there's enough there to put together,
i got one boot to hang and was hopeful , adb logcat showed a dead stop at unable to find /sys/class/backlight blah blah
should be interesting ! yay.... :silly:
m
okay,
i've rounded up what source i could and after overcoming a VERY silly mistake on my part,
i am now trying to stitch a build together.
What i'm not certain of is if i can test it correctly on a device that isn't locked.
When/if/when i get it working and tested as far as i can take it, i will still need testers.
I am working from the hltexx device source since my initial mod attempts seemed to grab with that safestrap version.
The problem with that mod/test seemed to be that the recovery could find /data and /cache but, not /system.
My guess is that even though i can modify the *apk's configurations and repack it, the partition scheme and/or some of
the hardware specifics [display/backlight] are hard coded/built in to this particular build/binary.
Anyway, :silly:
m
moonbutt74 said:
okay,
i've rounded up what source i could and after overcoming a VERY silly mistake on my part,
i am now trying to stitch a build together.
What i'm not certain of is if i can test it correctly on a device that isn't locked.
When/if/when i get it working and tested as far as i can take it, i will still need testers.
I am working from the hltexx device source since my initial mod attempts seemed to grab with that safestrap version.
The problem with that mod/test seemed to be that the recovery could find /data and /cache but, not /system.
My guess is that even though i can modify the *apk's configurations and repack it, the partition scheme and/or some of
the hardware specifics [display/backlight] are hard coded/built in to this particular build/binary.
Anyway, :silly:
m
Click to expand...
Click to collapse
You know how to get ahold of me and you also know I'll test anything. I'm ready! [emoji106]

Question TWRP coming?

Just saw the following article from XDA regarding TWRP v3.5 being released. I'm hopeful that this means that for devices that ship with Android 10 that TWRP will be able to decrypt the data partition in order to facilitate a complete backup.
That said, does anyone know how long it typically takes for TWRP to be supported on a new device (i.e. G-Stylus 2021)? Just curious what the norm is. Thanks!
That's a good question. I don't know how long it should take, but after reading the article you linked it seems that successfully porting TWRP to these newer phones will take a lot longer than on the older ones. Hopefully someone's already started working on TWRP 3.5 for the 2021 models, but I haven't heard any actual news on that yet.
I would love to be able to get a full backup of my device in case I really screw something up later on. If I had any level of programming skills I would certainly make an attempt at it myself.
DM.IDOL said:
That's a good question. I don't know how long it should take, but after reading the article you linked it seems that successfully porting TWRP to these newer phones will take a lot longer than on the older ones. Hopefully someone's already started working on TWRP 3.5 for the 2021 models, but I haven't heard any actual news on that yet.
I would love to be able to get a full backup of my device in case I really screw something up later on. If I had any level of programming skills I would certainly make an attempt at it myself.
Click to expand...
Click to collapse
I'd look around on github
THIS is a TEST build for the Moto G stylus XT2115-1 minsk_t
(please mind that i have never done this before and i am at least trying to figure out how to create custom recoveries. i just need a good teacher with a little time. .)​
*Touch Screen does not work. OTG mouse necessary.*
(not too sure how to fix this error)
*Mount points were for testing*
(modied fstab files in ramdisk to fix mount points)
*modified ramdisk and split_image from Moto G 9 plus unofficial 3.5.1 twrp*
https://forum.xda-developers.com/t/recovery-unofficial-twrp-for-g9-plus-odessa.4195729/
i tried to put a recovery together for this device but im not sure where i went wrong or what to do next. booting into this recovery works but /vendor and /system_root have denied permissions. when it is flashed within twrp and rebooted to recovery or system the screen says no OS installed press power to power off. If anyone can help me figure this one out i would be greatly appreciative. If you need anything i can pull from my device just let me know. Anyone willing to help work on this recovery and figure out what needed to be fixed i would greatly appreciate it!
*EDIT*
i got /data to back without digest verification. Was not able to try to restore the backup as i got NO OS error when i rebooted to restore.
*EDIT*
i was able to figure out pretty much everything except the touch part of the recovery. it has a novatek_ts (NVT-ts)
not sure what to do to enable the drivers for twrp. any feed back would be great.
*EDIT*
Found the driver. I'll post it here and see what you can do. I'll also work on it as I'm still learning where stuff should go in the recovery. And also seems to b that i cannot access external sd from twrp either.
*EDIT*
resolved sd card issues. mountpoint was incorrect. only thing left to get working is touchscreen and not have to use otg mouse.
updated twrp for minsk_t is in files now.
*EDIT*
I found the proper elements to configure the recovery's touchscreen capabilities. Will be recompiling later on today. After I have tested it I will post the new working TWRP recovery. Thanks everybody.
*deleted*
sosthenisRR said:
*deleted*
Click to expand...
Click to collapse
So this is fully functioning now right? Is there any reason to use this over the OrangeFox recovery that has been posted?
Also, if I did install OrangeFox, and decided I wanted to install this later, would it be as simple as flashing using fastboot from ADB, overtop of OrangeFox? Or would the procedure be a little more complex?

Looking for system ROM/root/custom ROMs for TCL Tab 8 (model 9048S)

Anything at all that someone might have for this device would be useful. I'm trying to see if I can get a Lineage install for it, or even just a backup ROM before attempting to debloat it a bit (I'm an Android newbie and like having a backup), but I can't seem to find much of anything on it on Google.
The device does have an unlockable bootloader, but I'm not sure how I would go about using this to any of the things in the topic.
E: For the record, I should probably explain why I'm so desperate for this--not only am I wanting to debloat this device, but ideally, I'd like to try flashing a generic system image to see if it can update to Android 12. Android 10 works fine on it, but I'd very much like some of the introduced accessibility features--however, I also want a backup of the original firmware, just in case something goes wrong.
I would also like for someone to answer this...please.
Has there been any luck with 9048s? I have same model and been looking also for the same exact solution.

Several Questions

I'm interested in building an updated, de-googled, de-bloated, ROM for a TCL A30 , model TCL5102D, mt6762/6765. First off was whether to post in tha Alcatel Section. My understanding is that Alcaltel is no more and those phones are now marketed as TCL. Prior Alcaltel posts may be helpful - perhaps the moderators could rename the section "Alcaltel/TCL" rather than adding a New TCL section.
I fouund mtkclient in the forum and it works on my device. I have not TWRP rooted it yet but have pulled boot.img, vbmeta.img and the entire system image. I have also found the TCL source code site, downloaded an earlier device with Mediatek Helio 22P chips and adb pulled /proc/config.gz. GPL source for my specific device has yet to be published by TCL.
I've yet to pull the vendor blobs and have only found guides in the Lineagos documentaion. It's pulling from a zip'd image rather than a device and TCL does not have images for any of their current phone. Also could not find a dump for this particular phone.
My first challenge is trying to build the kernel. The TCL source code, kernel 4.19.127, is not structured like the AOSP kernel source and aarch64, gcc builds hang up on the lcdscreen driver. The screen driver was backported in later 4.19.x versions which built with the config.gz and upstream kernel.org source.
What I'd like to do is to do is update the TCL source to the latest stable 4.19 code base but my web searches have not come up with any examples on how to do this. Could also build with the AOSP 4.19-stable source with the pulled config.gz - chances that it would work?
If I can prebuild the kernel, then make a decision in regards to a LineageOS build vs a GSI build. Maybe even build within GrapheneOS (uses prebuild kernels).
Where, in the forum, should I start the line of questions? Can anybody point me to a guide on howto build an kernel with an up-to-date source?
hi, your best place to go would be here and here
I have a TCL a30 android 11. I'm looking for any possible way to unlock the bootloader and install custom recovery. This all started with trying to use a visible sim card in the phone and me not being able to change the APN settings. I've been working on a way for a while now and have gotten absolutely nowhere. If anyone has any insight, it would be greatly appreciated.
danvep5014 said:
I have a TCL a30 android 11. I'm looking for any possible way to unlock the bootloader and install custom recovery. This all started with trying to use a visible sim card in the phone and me not being able to change the APN settings. I've been working on a way for a while now and have gotten absolutely nowhere. If anyone has any insight, it would be greatly appreciated.
Click to expand...
Click to collapse
TCL A509DL NO FASTBOOT-ABILITY??
Hey there guys and girls. I just bought a cheap TCL A509DL to experiment with and immediately hit a roadblock of megalithic proportions...no fastboot mode available on this cracker-jack prize equivalent phone. Seriously...no way to boot into...
forum.xda-developers.com
971shep said:
TCL A509DL NO FASTBOOT-ABILITY??
Hey there guys and girls. I just bought a cheap TCL A509DL to experiment with and immediately hit a roadblock of megalithic proportions...no fastboot mode available on this cracker-jack prize equivalent phone. Seriously...no way to boot into...
forum.xda-developers.com
Click to expand...
Click to collapse
I'm working on how to get the device to be recognized in mtkclient. Regardless of what button combination I use, the device fails to be recognized. Any specific way it needs to be done on the TCL A30?
I took the phone apart to look for some test points and I can't find any. Did anyone have success in getting this device to work with mtkclient? I've tried every button combination possible. If anyone has any insight it would be greatly appreciated. This is getting extremely frustrating. Been trying for the past week. Once I get passed that point we will be good to go but I'm at a wall right now.
danvep5014 said:
I took the phone apart to look for some test points and I can't find any. Did anyone have success in getting this device to work with mtkclient? I've tried every button combination possible. If anyone has any insight it would be greatly appreciated. This is getting extremely frustrating. Been trying for the past week. Once I get passed that point we will be good to go but I'm at a wall right now.
Click to expand...
Click to collapse
I start mtkclient with the phone connected via usb but powered off. Mtkclient messages that it is trying to establish a connection. Then just power up with the power key only. You should get messages that you connected in brom mode.
I was finally able to get it. Had to use adb reboot edl. Did the trick. Now I'm trying to build a rom with oxygen os but i keep getting stuck in a boot loop.
Boot loops can have many causes.. In the case of a custom rom, it is often that boot verification of the file systems fails, ie a file system checksum is different. In the thread I linked above, the way around this was to overwrite the three different vbmeta.* files with a blank file..

A few questions I can't seem to find any information on

Hey all, this is my first post here, so if anything horrifically wrong happens with this post, please let me know.
I recently rooted my first device since 4.4 (BLU G91 Pro), and started messing with kernel parameters. I have gotten the phone to be both more performant and efficient at the same time by fiddling with the "CPU sets". However, while I now have a configuration that improves both important things regarding a mobile device [Fig. 1], I don't know *why*. I do not understand what the options fully do, and in one case, I have no clue at all what it is. Can anyone either explain them in a concise but easy to read manner, or direct me to that? Thanks.
How did you get it to root? I have the same phone but with the mtk tool it won't backup and from the guide on here he says you need boot img a which is there but there's no boot img b?
Thanks for any help

Categories

Resources