Closed - LG K7 Questions & Answers

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!

Related

Will pay $$$ for help with TF201

So, I have made a major boo boo when it comes to rooting devices and flashing custom ROMs; normally I am not a n00b when it comes to this, but I think I gone done something wrong this time. I have checked Diamondbacks thread as well as many other and have a whole slew of tools downloaded now and I cannot seem to get past the splash screen. ADB recognizes my device as well as Windows in Fastboot mode, just can't seem to figure out how to flash the stock ROM back on this device. I would be willing to donate money to the cause as this has cause me much undue frustration. If you are up and willing to the task, please PM me or even call my cell to walk me through this. Couldn't find XDA's chat, all I am asking is that someone have a heart and help a fellow techie out.
LivioDoubleFang said:
So, I have made a major boo boo when it comes to rooting devices and flashing custom ROMs; normally I am not a n00b when it comes to this, but I think I gone done something wrong this time. I have checked Diamondbacks thread as well as many other and have a whole slew of tools downloaded now and I cannot seem to get past the splash screen. ADB recognizes my device as well as Windows in Fastboot mode, just can't seem to figure out how to flash the stock ROM back on this device. I would be willing to donate money to the cause as this has cause me much undue frustration. If you are up and willing to the task, please PM me or even call my cell to walk me through this. Couldn't find XDA's chat, all I am asking is that someone have a heart and help a fellow techie out.
Click to expand...
Click to collapse
Not sure what recovery you have now but I suggest you go here >>
http://forum.xda-developers.com/showthread.php?t=1615990 and install twrp recovery through the fastboot method. Boot into trwp recovery. After that, download the nvflash files from here http://forum.xda-developers.com/showthread.php?t=1774352
Not saying you should use nvflash at this point but the file also contains a known good adb.exe file. Unzip the file and while in that directory press and hold the shift button while right clicking the mouse. This will bring up a menu select open command prompt here.
Put your rom into the same folder as the adb.exe then in the comand window type adb push /name of your rom.zip /sdcard/ if this doesn't work use /sdcard/media At this point you should be able to install the rom. As for the rom, a good starting point would be androwook rom since it seems to install quite easily (do not unzip). Also when you are performing commands in either fastboot or adb, it is best to copy (control c) from the webpage then in the command window right click and paste, this eliminates errors. Having the files you are flashing in the same directory of fastboot or adb eliminates the need to type pathways, this is where many people run into issues, 1 wrong letter make everything not work....
Thanks Gage_Hero, the TWRP tutorial was just what I needed in getting a custom ROM flashed to the device; however, my next question is, if I did not create a backup of the stock ROM like I should have, will I ever be able to get back to it should I need to update the OS or for any other reason? From what I have read, Asus stock ROMs have a unique ID to every device, making it virtually impossible to use someone else's backup for flashing. Much appreciated for any information you can provide.
LivioDoubleFang said:
Thanks Gage_Hero, the TWRP tutorial was just what I needed in getting a custom ROM flashed to the device; however, my next question is, if I did not create a backup of the stock ROM like I should have, will I ever be able to get back to it should I need to update the OS or for any other reason? From what I have read, Asus stock ROMs have a unique ID to every device, making it virtually impossible to use someone else's backup for flashing. Much appreciated for any information you can provide.
Click to expand...
Click to collapse
Most people don't have a stock backup since once you are unlocked, trying to install the ota update can make the tablet inoperable. So basically when Asus updates the software then the developers here pick up the stock rom and enhance it. This goes anywhere from the base stock rom with root up to taking the rom and customizing it with options, kernel changes and such. The only thing I will say about changing kernels is only use kernels that were developed for the particular rom or you will have trouble. Kind of like taking a Ford motor and trying to mate it to a chevy transmission.
If you do change roms, make sure you wipe cache, dalvik and do the factory reset from within twrp. When you become comfortable, I suggest looking at the NVflash thread in the dev section. This will provide you with a bit of assurance that you can recovery from most software brick situations. Read over the instructions a few times before you go a head and take some time to read through the thread so you know what could potentially go wrong. It really isn't that difficult to do but you should be well informaed before proceding. If you need anything else don't hesitate to ask
Another thing that i find helpful, keep a stock rom in your sdcard. When i semi-bricked my 201, i was able to flash the stock rom using CWM, then do a factory reset. Once back to factory, i was able to boot and start over again.

BUILD RESOURCES: partition, device tree, kernel, vendor/blobs, etc.

UPDATED 2/19/2018
Almost enough here to start attempting debug builds... any other builders/devs out there working on this device? Hopefully some of this will be useful.
Minimal Omni device tree for TWRP (full lineage branch in progress as of 2/19/2018)
https://github.com/mightysween/android_device_motorola_payton
Proprietary blobs/vendor (initial push 2/19/2018):
https://github.com/mightysween/android_vendor_motorola_payton
Partition names/locations/mounts...maybe a few missing still:
https://docs.google.com/document/d/1EkPOkc8uUStKIjRGC2-4jkcXpxmj8v3piGPqZi9ctQM/edit?usp=drivesdk
7.1 KERNEL SOURCE:
https://github.com/MotorolaMobilityLLC/kernel-msm/tree/7.1.1-nougat-release-payton
8.0 KERNEL SOURCE:
https://github.com/MotorolaMobilityLLC/kernel-msm/releases/tag/MMI-OPW27.57-40
So what's the deal with the A/B partitions? I've seen that there are some lineage OS commits to handle the A/B partitions. Would it be possible to load an OS to the A partition and put the recovery on the B partition. I'm not familiar enough to know how much control of the boot process we can have with boot time commands. Does the bootloader have a boot to recovery option?
There doesn't seem to be a recovery partition in the list that you provided. I wonder what the fastboot commands look like... just thinking out loud on the internet. I don't have the phone yet, but I did have a look at Best Buy, so that practically makes me an expert. I have a N5X, so I'm lining up the successor for after its sudden, but inevitable betrayal.
gee one said:
So what's the deal with the A/B partitions? I've seen that there are some lineage OS commits to handle the A/B partitions. Would it be possible to load an OS to the A partition and put the recovery on the B partition. I'm not familiar enough to know how much control of the boot process we can have with boot time commands. Does the bootloader have a boot to recovery option?
There doesn't seem to be a recovery partition in the list that you provided. I wonder what the fastboot commands look like... just thinking out loud on the internet. I don't have the phone yet, but I did have a look at Best Buy, so that practically makes me an expert. I have a N5X, so I'm lining up the successor for after its sudden, but inevitable betrayal.
Click to expand...
Click to collapse
There is no traditional recovery partition...handled by boot. A/B is mainly to allow 'seamless' updates (as in OTA that downloads to the other partition for instant reboot). Bit more to it... if you want to read more, check out the Pixel forums.
Well... progress is being made. Wish there were others (there must be!) working on this.
I have the stock kernel, a VERY basic device tree, and cobbled-together vendor... syncing repos and will try to compile TWRP over the weekend. I do not expect it to work
Dealing with this right now on brunch...runs fine up until this point, appreciate any thoughts:
Starting build with ninja
ninja: Entering directory `.'
ninja: error: '/home/mightysween/android/omni/out/target/product/payton/obj/SHARED_LIBRARIES/libcryptfs_hw_intermediates/export_includes', needed by '/home/mightysween/android/omni/out/target/product/payton/obj/SHARED_LIBRARIES/libcryptfslollipop_intermediates/import_includes', missing and no known rule to make it
build/core/ninja.mk:157: recipe for target 'ninja_wrapper' failed
make: *** [ninja_wrapper] Error 1
Click to expand...
Click to collapse
Do I really need the lollipop libs???? Especially if I just want to compile TWRP and not full omni. Ahhhhhhh....so much fun
OK, got TWRP to compile
Need to do some testing in the emulator and double and triple check all sources and configs before even thinking about trying to boot it on the actual device.
But just troubleshooting at this point, so looking good for TWRP in coming days!
UPDATE: oops, totally compiled it with the wrong kernel. Haha... working through some defconfig issues, but hopefully nothing too crazy.
mightysween said:
OK, got TWRP to compile
Need to do some testing in the emulator and double and triple check all sources and configs before even thinking about trying to boot it on the actual device.
But just troubleshooting at this point, so looking good for TWRP in coming days!
Click to expand...
Click to collapse
I hope you can do it! Is the first step to get backups and ROMs. I don´t have the phone yet, but later the normal version that is sell in México and want to flash the Android One version (previously anyone get it working).
I'm returning my Amazon version of this phone and getting Project Fi version. I am willing to help in testing.
Well, my boot.img compiles fine... but will not boot to recovery. Given the fact that it is mostly guesswork on the device tree, I am not shocked.
Pushed my working tree to GitHub and will keep working on it...
https://github.com/mightysween/android_device_motorola_payton
Been looking at Pixel 2 TWRP Alpha... holy cow. So much more to it with this partitioning scheme.
mightysween said:
Well, my boot.img compiles fine... but will not boot to recovery. Given the fact that it is mostly guesswork on the device tree, I am not shocked.
Pushed my working tree to GitHub and will keep working on it...
https://github.com/mightysween/android_device_motorola_payton
Been looking at Pixel 2 TWRP Alpha... holy cow. So much more to it with this partitioning scheme.
Click to expand...
Click to collapse
Have not even peeked into the Pixel 2 forums. I'm afraid this seems to be another ballgame entirely. Do the new Pixel owners even have root passing safety net while allowing these security updates new android phones now get? Gah this is a mess
SR3TLAW said:
Have not even peeked into the Pixel 2 forums. I'm afraid this seems to be another ballgame entirely. Do the new Pixel owners even have root passing safety net while allowing these security updates new android phones now get? Gah this is a mess
Click to expand...
Click to collapse
TWRP has been worked on for Pixel2 by several people, including expert Dees Troy, and is still a heavy alpha. I feel pretty good about booting compiled boot images and not bricking on x4 (as far as I have gotten)
I have been compiling my own stuff for many years, and yes -- this new stuff is foreign. But, we will all learn and in a few weeks/months, there will be plenty of action on this device
mightysween said:
TWRP has been worked on for Pixel2 by several people, including expert Dees Troy, and is still a heavy alpha. I feel pretty good about booting compiled boot images and not bricking on x4 (as far as I have gotten)
I have been compiling my own stuff for many years, and yes -- this new stuff is foreign. But, we will all learn and in a few weeks/months, there will be plenty of action on this device
Click to expand...
Click to collapse
try using fixes from https://github.com/TeamWin/android_device_xiaomi_tissot tree. similar android one device!!
i.snehal.kiran said:
try using fixes from https://github.com/TeamWin/android_device_xiaomi_tissot tree. similar android one device!!
Click to expand...
Click to collapse
Thanks, picked up 3 changes from here already... will test them out soon!
So, I have checked out several XDA threads on this Xiaomi device (tissot) and I think it is going to help quite a bit with the A/B issues.
I am still, unfortunately stuck on getting TWRP to boot. Boot.img compiles fine and I can extract it and see TWRP has replaced stock recovery in the ramdisk, but it will not boot into recovery.
Ideally, we need a way to boot a TWRP image without flashing anything... easier said than done with devices that have recovery baked into the boot image. But once that works, we can extract just the ramdisk from my build and write a script to patch it into the stock boot image from the temporary TWRP running on the device.
Progress! New TWRP thread coming soon...
BTW, there is still a long way to go here... this was just a rudimentary test to get TWRP to boot. Need to start totally fresh with partitions before there is any attempt to actually use it!
Also -- my build environment is a total cluster after weeks of messing around. I need to wipe it and start over. That alone will take me a few days, and TWRP might take a few weeks more.
Incredible! Looking forward to having a custom recovery!
mightysween said:
Progress! New TWRP thread coming soon...
BTW, there is still a long way to go here... this was just a rudimentary test to get TWRP to boot. Need to start totally fresh with partitions before there is any attempt to actually use it!
Also -- my build environment is a total cluster after weeks of messing around. I need to wipe it and start over. That alone will take me a few days, and TWRP might take a few weeks more.
Click to expand...
Click to collapse
I hope later we can flash the Android One firmware on the retail Moto X4, I supose that OTA update will not work but at least we will have the lastest updates if someone make a flashable version
f3r.and0 said:
I hope later we can flash the Android One firmware on the retail Moto X4, I supose that OTA update will not work but at least we will have the lastest updates if someone make a flashable version
Click to expand...
Click to collapse
At the very least, we have the ability to create "nandroid" style backup from A1 device. Theoretically, that could allow anyone to install it...
But yes, in the long run, hopefully the actual firmware is released
mightysween said:
At the very least, we have the ability to create "nandroid" style backup from A1 device. Theoretically, that could allow anyone to install it...
But yes, in the long run, hopefully the actual firmware is released
Click to expand...
Click to collapse
Doesn't the nandroid (or for that matter Flashfire) backup contain personally unique identifiers?
DiDGR8 said:
Doesn't the nandroid (or for that matter Flashfire) backup contain personally unique identifiers?
Click to expand...
Click to collapse
Yes, technically... obviously would need to start with a fresh system and limit to non-data partitions.
No one needs to restore someone else's apps... just their boot/oem/system_image
mightysween said:
Yes, technically... obviously would need to start with a fresh system and limit to non-data partitions.
No one needs to restore someone else's apps... just their boot/oem/system_image
Click to expand...
Click to collapse
This just came to my mind, since this phone has 2 partitions for boot etc. --
Code:
mmcblk0p44: boot_a SIZE:65536 blocks
mmcblk0p45: boot_b
can't we make backup of boot_b ? it will be same as boot_a but unmodified i think ? i mean, use magisk/cf-autoroot/whatever to gain root on boot_a. and make backup of boot_b. so in case if we want to receive update, just restore back boot_b.img to boot_a slot and update through ota ? that way we can practically make full backup which is unmodified. ofc this is until we have fastboot image available and working TWRP.
also it seems all x4's are having same kernel according to this thread. although their build time is different.

Thread Closed

Thread Closed
Thread Closed
Is it the same as this one?
https://twrp.me/motorola/motorolamotoe4plus.html
MobyDuhFreak said:
Is it the same as this one?
https://twrp.me/motorola/motorolamotoe4plus.html
Click to expand...
Click to collapse
@MobyDuhFreak
Yes it is same as the above in all aspects. :fingers-crossed:
But i port it and the above guy develop it from source. It is official and mine is unofficial.
Thanks for yuor work! I am interested in installing it on my phone, but the installation part is not clear to me. Can anyone that installed it tell me exactly what to do? Really thanks.
Fernandus91 said:
Thanks for yuor work! I am interested in installing it on my phone, but the installation part is not clear to me. Can anyone that installed it tell me exactly what to do? Really thanks.
Click to expand...
Click to collapse
PHP:
How To Install :
fastboot erase recovery
fastboot flash recovery twrp.img
No oem unlock/bootloader unlock? Great! Thanks!
Recovery works, however, I cannot install dm-verity or superuser.
Seems like the shell is screwed up :s
dm-verity update script gives following error:
/tmp/updater[63]: .: config.sh: No such file or directory
Click to expand...
Click to collapse
the config.sh file definitely is there, though
Fr4gg0r said:
Recovery works, however, I cannot install dm-verity or superuser.
Seems like the shell is screwed up :s
dm-verity update script gives following error:
the config.sh file definitely is there, though
Click to expand...
Click to collapse
There are number of verity zip and it is now quite confusing which one to use or simply i say its an old school thing. Do this manually by removing ",verity" from recovery.fstab.
Hi ferends,
i have Motorola Moto E4 Plus MTK XT1771, can not instal any rom. Try to instal lineage 15 for my phone but after i flash phon nothing work in os, mobil data, wifi, camera, dont see may sim....adher roms for my phone I could not even flush.
and another problem I could not install any gapps for my phone
is there any solution?
Thank you
My E4 Plus 1771, don't' have Mediatek CPU 6737 but the 6735 version (tested with CPU-Z)
This, must be an obstacle in root operations ?
maxmot said:
My E4 Plus 1771, don't' have Mediatek CPU 6737 but the 6735 version (tested with CPU-Z)
This, must be an obstacle in root operations ?
Click to expand...
Click to collapse
You too have CPU 6737. The 6735 is SOC (System-on-chip).
Look man why you always just making copies of recoveries . Can you explain the "port" process you used that makes this your work and not just another copy like other times ...
KevMetal said:
Look man why you always just making copies of recoveries . Can you explain the "port" process you used that makes this your work and not just another copy like other times ...
Click to expand...
Click to collapse
First of all tell me. Did you know how to port a recovery ?? Did you ever do any type of development work ?? Did you have any clue/idea on how to port a recovery ??
KevMetal said:
Look man why you always just making copies of recoveries . Can you explain the "port" process you used that makes this your work and not just another copy like other times ...
Click to expand...
Click to collapse
Also for God's sake stop killing the word Opensource. Also check credits in OP post.
KevMetal said:
Can you explain the "port" process you used that makes this your work and not just another copy like other times ...
Click to expand...
Click to collapse
Yes i know how to port and i can explain whereas you can't do that.
First all both devices must have similar SOC. Then take working twrp from similar soc device. Unpack it. Only use ramdisk folder from that twrp recovery. Copy that ramdisk folder in official twrp. Fix fstab because it is different for both device. You need to place some official twrp files into ramdisk of a port. Then compile that thing. I my case i forgot to change device id and build number and here you start your another crap that it is izaqkull twrp. Izaqkull twrp won't work in e4 plus. Someone need to port first to make it working. Use your little brain and common sense.
TheHitMan said:
Yes i know how to port and i can explain whereas you can't do that.
First all both devices must have similar SOC. Then take working twrp from similar soc device. Unpack it. Only use ramdisk folder from that twrp recovery. Copy that ramdisk folder in official twrp. Fix fstab because it is different for both device. You need to place some official twrp files into ramdisk of a port. Then compile that thing. I my case i forgot to change device id and build number and here you start your another crap that it is izaqkull twrp. Izaqkull twrp won't work in e4 plus. Someone need to port first to make it working. Use your little brain and common sense.
Click to expand...
Click to collapse
:silly:jajaja yes exactly ...I think you didn't even do the porting ....that's why you can't fix the port , nor explain users the truth or even admit the problem is with the recovery ...not with the people ..if I did some original development I would take credit for it ..what I wouldn't do is try to claim that I developed something when I didn't ..or post broken or insecure stuff to give people the run around and still have the cheek to add it to my signature ...if you don't have the device take down the .zip and remove it from your signature or modify thread to tell users the truth and start to learn to address others with respect or you will never get it yourself ..
Furthermore you tell me I'm killing open source if I tell you not to copy :silly::silly:work or post broken stuff....:silly:
I think you don't understand what open source is .......
OK man good luck in your endeavours but please just fix your stuff or take them down ...its not the first time you copied recoveries or posted recoveries that caused problems...this has got nothing to do with open source or if I'm a dev.
KevMetal said:
:silly:jajaja yes exactly ...I think you didn't even do the porting ....that's why you can't fix the port , nor explain users the truth or even admit the problem is with the recovery ...not with the people ..if I did some original development I would take credit for it ..what I wouldn't do is try to claim that I developed something when I didn't ..or post broken or insecure stuff to give people the run around and still have the cheek to add it to my signature ...if you don't have the device take down the .zip and remove it from your signature or modify thread to tell users the truth and start to learn to address others with respect or you will never get it yourself ..
Furthermore you tell me I'm killing open source if I tell you not to copy :silly::silly:work or post broken stuff....:silly:
I think you don't understand what open source is .......
OK man good luck in your endeavours but please just fix your stuff or take them down ...its not the first time you copied recoveries or posted recoveries that caused problems...this has got nothing to do with open source or if I'm a dev.
Click to expand...
Click to collapse
Man i dunno what problem you have with me. But you are screwing everything. Did you ever get the word PORT. Also i ported that recovery at that time when there is nothing. It is just a blank forum in xda thread. I know opensource well thats why i gave credit to izaqkull for his twrp ramdisk. What kind of truth you want to hear, i already gave answers to you so many times. Ported thing may have some bugs and that bug is fixed in later time. Even there was no custom roms before when i ported twrp to this device. So no such report from so long. Why don't i have put that thing in my signature i ported that recovery not you. You just here doing free lancing stuffs not actual development. Also you want pure stuffs without any bugs. LOL. Even custom roms have bugs but those bugs fixed later.
You already screwed me before and i already gave answers to your question. So stop cluttering my xda post. You aren't doing anything better. If you have bugs report and i will fix them later. But you aren't doing that thing. You just here to take me down at any cost. Also that recovery is no copy pasted stuff. Use your little brain you can't directly use moto e4 twrp in moto e4 plus. Even there is nothing like one time stuffs you developed it without bugs. First do some dev. work or first come at my place then you will know it well.
Changelog 20-December-2018 :
> Fix wrong product name.
> General fixes in TWRP.
> Get download link from attachment.
Note : This is still a port and i made that port, when there is no official twrp recovery for this device. So every fix done in that ported twrp.
EDIT : The bug which is left out is fixed now. No more product, build errors. I already sold my device. So there is no point to make this thread open. If you have any query, you can DM me.
Moderator Information
Thread closed at OP's request.

Fastboot lenovo TB-X605F "unknown command"

Hi,
I just got a new tab Lenovo M10 TB-X605F.
I tried to unlock it with fastboot-adb (minimal kit).
When I enter "fastboot devices" the serial n° displays.
But each command I tried (fastboot oem unlock, unlock-go, flashing, flashing unlock...) get the same asnwer : "FAILED (remote: unknown command)".
Does anyone know a solution?
Thank you.
I also had problems with the out-of-the-box version of fastboot.
Solution is to upgrade to Pie, because the update allows bootloader unlocking. Easiest way is to load the rescue ROM using LMSA, then let the tablet fetch the OTAs.
To learn more have a look at @Chaser42's root thread for the P10. Also in that thread @Long_Sam has a step-by-step guide for the M10.
I've also posted an updated magisk_patched .img for TB-X605F running S210097_190927 to that thread. Be careful, though. Make sure your build and model number are the same as mine before using it:
build number: X605F_S210097_190927_ROW
model number: TB-X605F (hardware code 63)
Check the sticker on the back of your tablet for the hardware code. It's in brackets after the S/N.
So mine reads: "S/N: XXXXXXXX (63)".
Thank you very, very much Yahoo Mike!
I'll try it as soon as possible!
did you have oem unlock on in developer mode?
Yes
thanks, but i wonder if i can get twrp on the tablet
turboperson123 said:
thanks, but i wonder if i can get twrp on the tablet
Click to expand...
Click to collapse
I don't know yet.
Root is ok, thanks of the links in YahooMike's post. :good:
Monpseud0 said:
I don't know yet.
Root is ok, thanks of the links in YahooMike's post. :good:
Click to expand...
Click to collapse
I would love to get custom recovery for these tablets. I submitted a request for the P10 (TB-X705F) to the guys that port TWRP images to new devices. However, I think they are completely overloaded with request so we won't see anything soon. I was working with a guy that was making an image but he got busy with real life and hasn't been able to complete it.
I'm about ready to learn Android kitchen and cook up some TWRP images myself. I've read all the documentation. I just might be able to do it if I can find the time. If I can successfully make an image for the P10 then I can also make one for the M10 and all other variants. Hopefully I'm not being overly ambitious. Wish me luck.
Chaser
TWRP is OK. I found the way to flash it somewhere in this forum. It works. Now, it is waiting for a custom ROM to flash!
Chasser, if you do that, You're my hero ! I'd like to help you but I don't know anything about building a ROM. So I wish you the best! Can't sait!
Chaser42 said:
I would love to get custom recovery for these tablets. I submitted a request for the P10 (TB-X705F) to the guys that port TWRP images to new devices. However, I think they are completely overloaded with request so we won't see anything soon. I was working with a guy that was making an image but he got busy with real life and hasn't been able to complete it.
I'm about ready to learn Android kitchen and cook up some TWRP images myself. I've read all the documentation. I just might be able to do it if I can find the time. If I can successfully make an image for the P10 then I can also make one for the M10 and all other variants. Hopefully I'm not being overly ambitious. Wish me luck.
Chaser
Click to expand...
Click to collapse
I've got some time this week. Happy to help with the TWRP port. A basic setup shouldn't take long, especially if we ignore forced data encryption.
If you're eventually going to a install custom ROM, then you'll be wiping the /data partition anyway. So probably best to avoid the nightmare of trying to crack the encryption in TWRP - at least to begin with.
If it's really true that the P10 is just an M10 with some bells and whistles added, then I suspect we'll get away with using the same kernel image for all these tablets X605F/L & X705F/L in recovery. That means we can all use the same TWRP img. Fingers crossed.
But until we have some custom ROMs, the stock boot.img will need to be patched to remove encryption. Otherwise the next time you reboot, it'll just re-encrypt the data partition. Those images will be different for each tablet.
Have you got a github repo set up for recovery tree? We should probably start a new thread for unofficial TWRP (X605F/L & X705F/L) as well. I'm happy to kick it all off, if you haven't done so already.
Yahoo Mike said:
I've got some time this week. Happy to help with the TWRP port. A basic setup shouldn't take long, especially if we ignore forced data encryption.
If you're eventually going to a install custom ROM, then you'll be wiping the /data partition anyway. So probably best to avoid the nightmare of trying to crack the encryption in TWRP - at least to begin with.
If it's really true that the P10 is just an M10 with some bells and whistles added, then I suspect we'll get away with using the same kernel image for all these tablets X605F/L & X705F/L in recovery. That means we can all use the same TWRP img. Fingers crossed.
But until we have some custom ROMs, the stock boot.img will need to be patched to remove encryption. Otherwise the next time you reboot, it'll just re-encrypt the data partition. Those images will be different for each tablet.
Have you got a github repo set up for recovery tree? We should probably start a new thread for unofficial TWRP (X605F/L & X705F/L) as well. I'm happy to kick it all off, if you haven't done so already.
Click to expand...
Click to collapse
The P10 and M10 are so similar, we could probably Port it for all of the different variants if other people are willing to help out and test. On my end I only have P10 and my test P10.
Currently I don't have a Linux machine but I saw that he made a version that works on Android. I think you I know a lot more about the process than I do. I'm just pretty good at reading documentation and coming up to speed on stuff that I've never done before. And this stuff isn't really over-the-top technology-wise so I figured it might be a neat project to tackle.
And speaking of custom roms, I think I saw that somebody had an unofficial lineage ROM started for these devices. I'll have to double-check that. And I was thinking about the stock ROM, encryption doesn't happen until after LMSA is done with the rescue and the tablet reboots. I'm not a big expert in what happens when the initial ROM is flashed but it feels like there's some sort of script running that handles a bunch of batch processes. I know that you can modify any of the files that you want before you do the rescue. Wouldn't it be nice if all we had to do is comment out some lines in the script so that encryption doesn't happen at all? Perhaps I'm being a bit too optimistic.
My big problem in the near future is time. I'm going to be very busy with my kids in the next few weeks. So I'm definitely not a position right now where I can spearhead that project. But we'll have to see how it goes. I'm sure I love some availability if you need my help.
Chaser
Yahoo Mike said:
I've got some time this week. Happy to help with the TWRP port. A basic setup shouldn't take long, especially if we ignore forced data encryption.
If you're eventually going to a install custom ROM, then you'll be wiping the /data partition anyway. So probably best to avoid the nightmare of trying to crack the encryption in TWRP - at least to begin with.
If it's really true that the P10 is just an M10 with some bells and whistles added, then I suspect we'll get away with using the same kernel image for all these tablets X605F/L & X705F/L in recovery. That means we can all use the same TWRP img. Fingers crossed.
But until we have some custom ROMs, the stock boot.img will need to be patched to remove encryption. Otherwise the next time you reboot, it'll just re-encrypt the data partition. Those images will be different for each tablet.
Have you got a github repo set up for recovery tree? We should probably start a new thread for unofficial TWRP (X605F/L & X705F/L) as well. I'm happy to kick it all off, if you haven't done so already.
Click to expand...
Click to collapse
Hi guys
I got TWRP on m'y M10. Thanks to Turboperson123
https://forum.xda-developers.com/general/help/lenovo-tb-x605f-twrp-t3976707?goto=newpost

Question Moto G Pure - XT2163-4 vs XT2163-2 - LTE bands

New here. Didn't see a forum for the Moto G Pure XT2163. Mods - I am sorry. Please move wherever's best.
Discovered that the version Verizon is selling (notably the slickdeals thread on the one from Visible) is different. It's -2 vs. -4.
Looks like VZW disabled most of the bands that T-Mobile/Sprint use - 25, 41, 71, for example.
Looking to see if it's possible to enable those bands. One report on SD thread says they bricked their device trying RETUS version but IDK if the bootloader needs to be unlocked first, or if it would even help. Probably more work to unlock these bands if it's even possible.
Downloads look available here https://mirrors.lolinet.com/firmware/moto/ellis/official/
Haven't messed with flashing a phone in years. May be able to try later but hoping anyone else here can look into this.
I'm going to guess as is the case with most other Android devices branded by Verizon that the bootloader will be restricted from being unlocked. There is really no way around this as it's an OEM based policy. If you want to play with custom ROMs or root based modding, I would highly recommend ditching the Verizon or any other carrier branded variant with the exception of T-Mobile/Metro and Google Fi (there are others) that actually allow OEM unlock. Not only that, but if you're looking for certain connectivity bands, you don't want to settle for a carrier device variant designed to use a particular set of bands which don't include the ones you need. No sense getting a Verizon variant to run on T-Mobile/Sprint bands when you can, you know, get the T-Mobile variant in the first place. Get the global unlocked variant model if you can and start from there. Far easier than the headaches you'll get trying to transform VZW to TMUS.
Cross-flashing is not going to unlock bands, you need to change modem configuration. Throw your SoC(Mediatek) followed by "unlock bands" into Google and see if you have any luck.
I also didn't see a forum for the Moto G Pure and was wondering if anyone knows of a custom bootloader like TWRP or CWM for it? I think I have enough understanding of how to sideload the app, I just need something to send the phone. I tried using a random TWRP mod on it but it fails, invalid signature. I haven't tried doing the phone rooting thing in years now, but I have this Moto G Pure phone without any service on it that I'm willing to experiment on. It can be used as a test bed or data extraction device to put code from it on the internet if someone needs it to help custom rom makers for example by testing stuff on it. Perhaps that's why no one has a custom recovery for it yet.
I don't know exactly how to extract the phones current ROM data so all I've done so far is unlock the bootloader. The phone's carrier based on the unactivated sim card shows it's a T-Mobile branded device, but the T-Mobile and other carrier software is inactive other than the few Moto apps. An article on XDA say's the phone's suck, but that's just not true at least not to me. It's a fine phone like it is, but if I can format it's SSD and only install what I want it to have on it that would be great. It's just a spare sim locked phone that I can't use my active sim card in. So with that it's now a project phone. I would like to mainly just unbloat it and free up all that used space occupied by the recovery partition. I don't necessarily need a whole new ROM, just want to root it. That's the only way to erase those factory files that I know of.
For me unlocking the bootloader wasn't to hard to do. You have to make sure the drivers from Motorola are installed and have a current version of ADB available on a computer. I still had a version of ADB tools that was almost a decade old now so I had to update that for the fastboot oem_unlock_unlockcode (automated code from Motorola support) command to work. To find out if it can be unlocked or not go here:
https://motorola-global-portal.custhelp.com/app/standalone%2Fbootloader%2Funlock-your-device-b
At the Moto site they will guide you on how to generate the code they want you to send them. You have to sign in to their site to use that function though. After I finally figured out what to type in the CMD window it generated that code and I edited it down to one long line of numbers and give it to the page. In seconds I had an email with the unlock code inside.
Unlocking it seems to help with uninstalling some of the built in stuff, before I could only disable most of the apps that come with it. The apps are still probably on there I just have to factory reset it and they'll come back. Now however the removed apps don't show as using any internal storage, all the apps info numbers go to 0 bytes, but still even doing that it's still over 10GB of unmovable data. When it should really be more like 2-3 GB for the entire system. I hate how Google just inserts itself in your life even when you don't want it at all.
I anyone passing by reading this post needs more details please let me know and I'll try to get the information or even data files from the phone. Would a copy of it's stock firmware be of any help? If so let me know how I would go about saving a copy of it. I'll keep looking for answers but it seems this phone is not high on the priority list or is new or something. So there is only scam guides trying to tell you "How to unlock your phone" or "Install TWRP on Motorola devices" and other clearly click bait sites. I can't even find the stock rom for it on Motorola's site, just outdated versions from 2016, with different build numbers, that can't be right.
All I know is unlocking the bootloader was the first step on all the guides and I've done that. Got a warranty voided notice and everything. There currently isn't a custom recovery mod for this model as far I can tell. If I can ever find that then I can try Linage or just debloat Android 11 which is probably the safer and easier option provided I can find that Custom Covery'.
When it boots up now, it has to tell me it's unlocked and all the dangers it poses. Dangerous if you cared about what was on it I suppose. There is nothing on it I can't just copy back over to it, other than the stock operating system.
Oh yeah, it's model number and other side of the box information is:
Model Name: Moto G PURE
SKU: MO-XT21634-AJB (MOXT21634AJB)
Software Version RRH31.Q3-46-20
Production date was 12/15/2021
I'm not sure what other information to include.
BrittonCBurton said:
I also didn't see a forum for the Moto G Pure and was wondering if anyone knows of a custom bootloader like TWRP or CWM for it? I think I have enough understanding of how to sideload the app, I just need something to send the phone. I tried using a random TWRP mod on it but it fails, invalid signature. I haven't tried doing the phone rooting thing in years now, but I have this Moto G Pure phone without any service on it that I'm willing to experiment on. It can be used as a test bed or data extraction device to put code from it on the internet if someone needs it to help custom rom makers for example by testing stuff on it. Perhaps that's why no one has a custom recovery for it yet.
I don't know exactly how to extract the phones current ROM data so all I've done so far is unlock the bootloader. The phone's carrier based on the unactivated sim card shows it's a T-Mobile branded device, but the T-Mobile and other carrier software is inactive other than the few Moto apps. An article on XDA say's the phone's suck, but that's just not true at least not to me. It's a fine phone like it is, but if I can format it's SSD and only install what I want it to have on it that would be great. It's just a spare sim locked phone that I can't use my active sim card in. So with that it's now a project phone. I would like to mainly just unbloat it and free up all that used space occupied by the recovery partition. I don't necessarily need a whole new ROM, just want to root it. That's the only way to erase those factory files that I know of.
For me unlocking the bootloader wasn't to hard to do. You have to make sure the drivers from Motorola are installed and have a current version of ADB available on a computer. I still had a version of ADB tools that was almost a decade old now so I had to update that for the fastboot oem_unlock_unlockcode (automated code from Motorola support) command to work. To find out if it can be unlocked or not go here:
https://motorola-global-portal.custhelp.com/app/standalone%2Fbootloader%2Funlock-your-device-b
At the Moto site they will guide you on how to generate the code they want you to send them. You have to sign in to their site to use that function though. After I finally figured out what to type in the CMD window it generated that code and I edited it down to one long line of numbers and give it to the page. In seconds I had an email with the unlock code inside.
Unlocking it seems to help with uninstalling some of the built in stuff, before I could only disable most of the apps that come with it. The apps are still probably on there I just have to factory reset it and they'll come back. Now however the removed apps don't show as using any internal storage, all the apps info numbers go to 0 bytes, but still even doing that it's still over 10GB of unmovable data. When it should really be more like 2-3 GB for the entire system. I hate how Google just inserts itself in your life even when you don't want it at all.
I anyone passing by reading this post needs more details please let me know and I'll try to get the information or even data files from the phone. Would a copy of it's stock firmware be of any help? If so let me know how I would go about saving a copy of it. I'll keep looking for answers but it seems this phone is not high on the priority list or is new or something. So there is only scam guides trying to tell you "How to unlock your phone" or "Install TWRP on Motorola devices" and other clearly click bait sites. I can't even find the stock rom for it on Motorola's site, just outdated versions from 2016, with different build numbers, that can't be right.
All I know is unlocking the bootloader was the first step on all the guides and I've done that. Got a warranty voided notice and everything. There currently isn't a custom recovery mod for this model as far I can tell. If I can ever find that then I can try Linage or just debloat Android 11 which is probably the safer and easier option provided I can find that Custom Covery'.
When it boots up now, it has to tell me it's unlocked and all the dangers it poses. Dangerous if you cared about what was on it I suppose. There is nothing on it I can't just copy back over to it, other than the stock operating system.
Oh yeah, it's model number and other side of the box information is:
Model Name: Moto G PURE
SKU: MO-XT21634-AJB (MOXT21634AJB)
Software Version RRH31.Q3-46-20
Production date was 12/15/2021
I'm not sure what other information to include.
Click to expand...
Click to collapse
hey i just came up on one of these today, nice phone considering... Any luck with trying to find a custom recovery? I have been looking as well but development seems pretty sparse right now. I am in the same boat as you, unlocked bootloader, locked everything else lol. I cant even find a way to root it without TWRP! I am curious if one of the other moto G series phones would have the same TWRP? Also check this out. It sounds legit but IDK...https://www.getdroidtips.com/root-motorola-g-pure-xt2163/
Agent_Orange1488 said:
hey i just came up on one of these today, nice phone considering... Any luck with trying to find a custom recovery? I have been looking as well but development seems pretty sparse right now. I am in the same boat as you, unlocked bootloader, locked everything else lol. I cant even find a way to root it without TWRP! I am curious if one of the other moto G series phones would have the same TWRP? Also check this out. It sounds legit but IDK...https://www.getdroidtips.com/root-motorola-g-pure-xt2163/
Click to expand...
Click to collapse
Well I was able to use Magisk to "root" it with the patched boot file trick, but still that's not the same thing as I did before with a Samsung phone and the CWM recovery deal. That gave the user all the control they wanted. Even though the phone claims I have root access, I'm not sure what to do with Magisk's root trick. I still don't see a way to backup or install a different operating system or just a blank Android 11 OS. My knowledge there is limited and there isn't a custom recovery for this model as far as I can tell.
So I still can't wipe the drive or remove the OEM partition that contains the installers for the bundled stuff. I'd still need some form of interface that has more features than the stock Fastboot and Bootloader modes offer I guess, or I just don't know how to use the software tools correctly. It's still locked even with root as far as I can tell but if there is something more I'm missing or an additional app to install for example, like SU. Is that still a thing? If I'm on the right track let me know.
BrittonCBurton said:
Well I was able to use Magisk to "root" it with the patched boot file trick, but still that's not the same thing as I did before with a Samsung phone and the CWM recovery deal. That gave the user all the control they wanted. Even though the phone claims I have root access, I'm not sure what to do with Magisk's root trick. I still don't see a way to backup or install a different operating system or just a blank Android 11 OS. My knowledge there is limited and there isn't a custom recovery for this model as far as I can tell.
So I still can't wipe the drive or remove the OEM partition that contains the installers for the bundled stuff. I'd still need some form of interface that has more features than the stock Fastboot and Bootloader modes offer I guess, or I just don't know how to use the software tools correctly. It's still locked even with root as far as I can tell but if there is something more I'm missing or an additional app to install for example, like SU. Is that still a thing? If I'm on the right track let me know.
Click to expand...
Click to collapse
Thanks for the reply!!! I am speaking from a place of semi-ignorance here but I would thing that you could install SuperSU from inside the system, right? As long as the root binary is there...idk though and from what I hear, chainfire is not responsible for SuperSU anymore so it has become somewhat sketchy. I saw a post (about this phone, I think) that mentioned having to install terminal emulator and running root command from there to achieve legit root after flashing the patched boot.img. I will see if I can find the post again and update you. Is there anyway you could post the boot.img? Or give me a link for it?
Agent_Orange1488 said:
Thanks for the reply!!! I am speaking from a place of semi-ignorance here but I would thing that you could install SuperSU from inside the system, right? As long as the root binary is there...idk though and from what I hear, chainfire is not responsible for SuperSU anymore so it has become somewhat sketchy. I saw a post (about this phone, I think) that mentioned having to install terminal emulator and running root command from there to achieve legit root after flashing the patched boot.img. I will see if I can find the post again and update you. Is there anyway you could post the boot.img? Or give me a link for it?
Click to expand...
Click to collapse
Well I can try and learn how to extract the phones information to my computer. I don't know how to do that exactly. The way I was able to get a hold of the phones stock firmware data was by using Lenovo's Smart Rescue and Recovery software.
You have to enable usb debugging mode, attach the phone to the computer with the software running and make sure that you didn't disable/delete Device Help. That app is what makes the Lenovo software work, otherwise the Recovery software fails to see the phone. If it sees the phone correctly then you can see the preselected target firmware it wants you to download under the Rescue tab along the top.
So I did that and grabbed the files it created without actually applying them to the device. The whole thing is a little over 2GB and difficult to host but I put the stock boot.img file here for anyone who needs it. If anyone wants all the files I can try to upload the whole thing one file at at time. That's the way it was sent to me, an uncompressed folder. If I zip it all up and try to upload it most sites will say file size exceeded. Anyway here's the link...
boot
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Thanks I was able to patch it with Magisk and achieve root. It looks like Magisk is an SU manager anyway. I have never used it before so this is a first for me. The root and bootloader unlock seem a little pointless without any recovery or ROM though....I guess it's time to learn how to compile one lol
I just picked up the Moto G Pure (XT2163-4) Android 11 aka Red Velvet Cake *sounds yummy lol*....I've been searching around and not seen any info about any rooting method for this device....besides the "Root All Motorola Phones" crap...and I don't feel like risking making a paper weight with it. Even on here it doesn't show up in the...add device list....was going to add to my profile...but can't.
Agent_Orange1488 said:
Thanks I was able to patch it with Magisk and achieve root. It looks like Magisk is an SU manager anyway. I have never used it before so this is a first for me. The root and bootloader unlock seem a little pointless without any recovery or ROM though....I guess it's time to learn how to compile one lol
Click to expand...
Click to collapse
Yeah now we're on the same page then. I thought the same thing, not much use to have an unlocked boot loader and root access without software to make use of it. I gave the phone to my nieces to play with for now, but it's with in arms reach if I need it for instructions yet to be defined. I should receive updates to this post if anyone else responds.
Gamekeeper408 said:
I just picked up the Moto G Pure (XT2163-4) Android 11 aka Red Velvet Cake *sounds yummy lol*....I've been searching around and not seen any info about any rooting method for this device....besides the "Root All Motorola Phones" crap...and I don't feel like risking making a paper weight with it. Even on here it doesn't show up in the...add device list....was going to add to my profile...but can't.
Click to expand...
Click to collapse
Yeah appears it was produced in late 2021 or sold at that time so it's new and no one has made any custom firmware's or recoveries for it as far as I know. I don't know how to do that, requires computer programming skills. I don't have any of those.
Gamekeeper408 said:
I just picked up the Moto G Pure (XT2163-4) Android 11 aka Red Velvet Cake *sounds yummy lol*....I've been searching around and not seen any info about any rooting method for this device....besides the "Root All Motorola Phones" crap...and I don't feel like risking making a paper weight with it. Even on here it doesn't show up in the...add device list....was going to add to my profile...but can't.
Click to expand...
Click to collapse
I feel your pain! Had mine a few days and of course came to XDA immediately to find the DL on this joint but no luck... Ya I definitely don't recommend one click root method for this. If you want, I can post/link the patched boot.img i made with magisk. Mine boots with it and have confirmed root.
BrittonCBurton said:
Yeah now we're on the same page then. I thought the same thing, not much use to have an unlocked boot loader and root access without software to make use of it. I gave the phone to my nieces to play with for now, but it's with in arms reach if I need it for instructions yet to be defined. I should receive updates to this post if anyone else responds.
Click to expand...
Click to collapse
Excellent, it's nice to be caught up with everyone else haha!! I am going to do some digging and posting and whatnot to try to find some info on porting a recovery for this model. I feel like it can't be too different from at least one or two of the other G series phones. I will see updates as well so please post if you come up with anything!!
BTW does anyone know the process of creating a device page for this joint?! I think this phone is definitely worth some development...
Agent_Orange1488 said:
Excellent, it's nice to be caught up with everyone else haha!! I am going to do some digging and posting and whatnot to try to find some info on porting a recovery for this model. I feel like it can't be too different from at least one or two of the other G series phones. I will see updates as well so please post if you come up with anything!!
BTW does anyone know the process of creating a device page for this joint?! I think this phone is definitely worth some development...
Click to expand...
Click to collapse
Good luck finding anything that will load onto the phone. Seems like it would be possible to install LineageOS on it if nothing else. You'd think by now installing a phone's operating system would be similar to how operating systems are installed on other computers. All I get is invalid signature, way to much security (for them) on phone OS'es. With phones and PDA's apparently you can't just find the OS you want to use and install it. Where's the generic and bloat free Andriod 11 stock OS/firmware at? No such thing? It's either "Gaggles" way or nothing apparently. (It's ok if you don't know either, maybe someone else has more information about that.)
BrittonCBurton said:
Good luck finding anything that will load onto the phone. Seems like it would be possible to install LineageOS on it if nothing else. You'd think by now installing a phone's operating system would be similar to how operating systems are installed on other computers. All I get is invalid signature, way to much security (for them) on phone OS'es. With phones and PDA's apparently you can't just find the OS you want to use and install it. Where's the generic and bloat free Andriod 11 stock OS/firmware at? No such thing? It's either "Gaggles" way or nothing apparently. (It's ok if you don't know either, maybe someone else has more information about that.)
Click to expand...
Click to collapse
Ya I'm definitely not going to try anything on the actual device, (ESPECIALLY if I am trying to put it together myself) but I am pretty sure you can test that stuff on a virtual system. Some kind of android emulator or whatever. As for a stock/debloated/de-odexed ROM, I haven't seen one but that couldn't be all that difficult to put together, right? I mean as long as the patched boot.img is included anyway. I feel like a recovery would be a higher priority though...? BTW, I have never used Lineage before, how is it?
Agent_Orange1488 said:
I feel your pain! Had mine a few days and of course came to XDA immediately to find the DL on this joint but no luck... Ya I definitely don't recommend one click root method for this. If you want, I can post/link the patched boot.img i made with magisk. Mine boots with it and have confirmed root.
Click to expand...
Click to collapse
That would be great if you could share that patched boot.img......it is for the XT2163-4 MOTO G PURE correct?
Gamekeeper408 said:
That would be great if you could share that patched boot.img......it is for the XT2163-4 MOTO G PURE correct?
Click to expand...
Click to collapse
Agent_Orange1488 said:
I feel your pain! Had mine a few days and of course came to XDA immediately to find the DL on this joint but no luck... Ya I definitely don't recommend one click root method for this. If you want, I can post/link the patched boot.img i made with magisk. Mine boots with it and have confirmed root.
Click to expand...
Click to collapse
I would also like the patched boot.img if it is for the XT2163-4. Thanks
Hey boys I actually got rid of the moto g pure...for now at least lol! GREAT phone and I would be willing to get it back once there is some dev work done on it...will definitely be watching the threads on it. Good luck boys!!!
Hi
I read the above posts, and it seems like even if I am able to root it using Magisk, I won't be able to flash it with custom rom?
Thank you Agent_Orange1488 for the posts.

Categories

Resources