Related
Hello
When install Magisk in TWRP 3.1.1-0 on my Lenovo K3 Note and Lenovo Vibe P1 there is "error 1"
I tried all version of Magisk
Do you have the same problem with the Lenovo device ?
Thank you
Welcome to XDA. You're gonna have a lot of fun here... :good:
First things first: When reporting issues and asking for help it's usually helpful to also add some kind of log to your post. When having issues flashing things in TWRP, you can save a log to your device by going to Advanced -> Copy log after experiencing the issue. Take that log and attach it to your post. Do not paste the log into the post since logs can be very long and that'll make the thread very hard to read.
When you're new it's also a good idea to read the rules. If you check there you'll see that the number 1 rule is to search before posting. In your defence there isn't a whole lot of results if you search the Magisk forum for "Lenovo", but searching the support thread shows a few results. There seems to have been a couple of Lenovo users with issues...
Besides reading the rules it's usually a good idea to look for any kind of information thread for the mod you're about to try. Don't know if you read it, but the release thread has a lot of good info. Checking what kind of stickes the forum has is also a good idea. In the Magisk forum you'll find the support thread I mentioned earlier. If there's one of those it could be a good idea to look through the last couple of hundred posts (sounds like a lot but it usually doesn't take that long) to see if there's anything interesting going on.
Anyway... Like I said, if you want help it'd be good to see a recovery log, but from previous experience there might be an incompatibility issue with your device's boot image. Uploading the log with a copy of your boot image and a description of your issue to an issue on GitHub might help the developer fix that issue, but there is nothing guaranteed.
If you haven't already (you do say "all versions of Magisk", so you might have) and you are feeling brave enough you could give the v13 beta a try, just to see if it installs. Just remember though that there might be other issues with the beta.
Hello , I had successfully flashed magisk through twrp 3.0.2-3 got no error but was stuck in bootloop maybe because I used patched boot.img
---------- Post added at 09:12 AM ---------- Previous post was at 09:11 AM ----------
The new version may not give error , remember flash it on stock boot.img
LineageOS is a free, community built, aftermarket firmware distribution of Android 8.1 (Oreo), which is designed to increase performance and reliability over stock Android for your device.
It should go without saying, but do not lock your bootloader with this installed. You must be 100% stock, I'd suggest on both slots, in order to re-lock your bootloader. Doing otherwise will likely lead to a brick that Essential really shouldn't warranty.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit our Gerrit Code Review.
Unofficial LineageOS Builds
Essential PH-1 (mata): https://updater.invisiblek.org/mata
Google apps
Google apps (opengapps nano) are baked in to these builds. This is due to the A/B partition layout and complications backing up/restoring gapps between builds. This is not ideal, and is the major road block to getting this device in to official status with Lineage. At this time I do not plan to release non-gapps builds. Users who require this will have to build their own.
Source
Device | Kernel
Here's a local_manifest for those who want to build at home.
Prerequisites
Unlocked bootloader
OPM1.180104.092 firmware - even if you were on this build, you should flash this firmware package to ensure the firmware is on BOTH slots.
Fastboot and ADB set up (use your google-fu to figure this out)
Installation
This device is different than what most people are familiar with due to the A/B partition layout. If you're familiar with Pixel devices, then you already know what this means. This thread isn't really designed to explain how it all works, that should be handled somewhere else. Instead, I'll assume you can either follow directions or do some research on your own. Additionally I have a discord set up where there are several people who may be able to help if you run in to a snag.
The initial install should go rather smooth, and future updates can be taken through the built-in Lineage updater app (yes, the are the seamless updates you may have heard about). Due to A/B, the recovery's ramdisk is actually on the boot.img partition (the rom's ramdisk is on the system partition now). What this means is once you flash the rom, it essentially (lol) replaces the TWRP that you have installed. This shouldn't be a problem since with the seamless updates, you shouldn't have to ever go into recovery. If you find yourself needing recovery, you'll have to re-flash TWRP to get there.
Phew, now some instructions.
See the prerequisites. You really do need these or things aren't going to work for you.
Boot into bootloader mode and wipe data with:
Code:
fastboot -w
Download twrp (mirror) and flash it with this command:
Code:
fastboot flash boot twrp-mata_11.img
(no, this isn't a typo, you are flashing twrp to the boot partition)
While still in bootloader mode, use vol down to select "Recovery mode" and hit the power button. This should boot you in to TWRP. Enter your previous lock screen password or pin (if it asks) to decrypt your data partition.
Put the device in sideload mode with:
Code:
adb shell twrp sideload
Install the zip via adb sideload with:
Code:
adb sideload <zip name here>
When finished, reboot.
Profit!
The LineageOS team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
XDA:DevDB Information
[ROM][UNOFFICIAL] LineageOS 15.1 for the Essential PH-1 (mata), ROM for the Essential Phone
Contributors
invisiblek
Source Code: [url]https://github.com/LineageOS[/URL]
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 4.x
Version Information
Status: Testing
Created 2017-11-12
Last Updated 2017-11-11
Q: What is broken?
A: Nothing I'm aware of
Q: Can I use the stock Essential camera app?
A: Yes
Q: Does the 360 cam work?
A: No.
Q: Is this rooted?
A: No. You're on your own for that.
Q: Does this pass SafetyNet?
A: Yes. Android pay, Pokemon Go, etc work fine. If you root, depending on your root method, you may lose this ability. But the ROM itself does pass SafetyNet.
2017-11-20 FAQ rollup: https://forum.xda-developers.com/showpost.php?p=74580036&postcount=189
FAQ site with some more info (be gentle with the terrible, or should i say complete lack of, css)
"Why no work" bug reports incoming in 5,4,3,2,1....
EDIT: @invisiblek if you need this post for anything, let me know.
THANK YOU!! So glad to see this. Just ordered the essential yesterday.
Any known bugs? How is performance compared to stock? Thanks for this!
Install it and find out. It's a testing build.
Awesome! Mine will be here soon.. glad to see development!!
Sent from my Nexus 6 using Tapatalk
First time with an A/B device, so everytime you update with a new build to the updater site it will prompt us and begin updating in the background? Don't have to be specific with the process itself but I was just curious as I'd like to stay up to date as possible if I start the custom ROM endeavor since it's still early on in development. Thanks!
installing now.. OP the link to twrp is broken
Thanks OP!
Got it up and running, seems pretty solid for the first build. The initial setup wizard hung at the last step for me but after a reboot it worked.
Oh, and the night mode works great!
^TWRP link worked for me about 30 mins ago
Update: I have installed most all of my apps and have been playing around setting up the phone for the last ~30mins....no stutters, no mistouches, everything is working great. LTE+ on VZW works, as well as Verizon messaging app. The phone apk has the option for vvm, haven't tested. Overall I can't believe how well this runs...ROM development has come a long way from the initial releases I'm used to on non nexus devices.
360 Camera doesn't work.....
CaptainElwood said:
Thanks OP!
Got it up and running, seems pretty solid for the first build. The initial setup wizard hung at the last step for me but after a reboot it worked.
Oh, and the night mode works great!
^TWRP link worked for me about 30 mins ago
Update: I have installed most all of my apps and have been playing around setting up the phone for the last ~30mins....no stutters, no mistouches, everything is working great. LTE+ on VZW works, as well as Verizon messaging app. The phone apk has the option for vvm, haven't tested. Overall I can't believe how well this runs...ROM development has come a long way from the initial releases I'm used to on non nexus devices.
Click to expand...
Click to collapse
Same feelings here. I really hope vvm works. Will test tomorrow... The ROM already kept me up tik now 3:09am
---------- Post added at 09:13 AM ---------- Previous post was at 09:09 AM ----------
Also on vzw don't see LTE + though.
Has installing lineage fixed the low signal strength problem for those people that have been experiencing it?
Sent from my ONEPLUS A5000 using Tapatalk
Works great! Found a wifi bug
Following the instructions posted, wifi stops working after flashing twrp and rebooting back into LOS. I flashed addonsu-14.1-arm64-signed.zip to enable App access to root. It worked, but wifi is broken on reboot. It turns itself off immediately after turning on.
Replication steps:
1. Follow steps in OP.
2. Reboot to bootloader (adb reboot-bootloader)
3. Flash twrp_mata-6.img (fastboot flash boot twrp.img)
4. adb push addonsu-14.1-arm64.zip /sdcard/
5. Install .zip in TWRP
6. Reboot
Anybody else getting this issue? The only way I've been able to fix it is to re-flash LOS.
EDIT: Thanks to @bmg1001, this issue is resolved (for me at least) by using this build of TWRP... Sorry, I can't post links yet! Can someone link this please?
https:// drive.google. com/file/d/1Pp9Hep-EEGNHLl6I_ob7ugihpKfrAcWm/view?usp=sharing
Note that flashing this TWRP build will allow you to reboot to recovery at any time without having to reflash TWRP, as mentioned in the OP.
omvir said:
Has installing lineage fixed the low signal strength problem for those people that have been experiencing it?
Sent from my ONEPLUS A5000 using Tapatalk
Click to expand...
Click to collapse
My signal strength improved from 2 bars to 3 bars at home, but I'm not sure if the reception has improved or just the number of bars displayed at certain signal strengths..
back2you said:
360 Camera doesn't work.....
Click to expand...
Click to collapse
You betrayed Sony
TWRP DL link not working
tclaybor said:
Following the instructions posted, wifi stops working after flashing twrp and rebooting back into LOS. I flashed addonsu-14.1-arm64-signed.zip to enable App access to root. It worked, but wifi is broken on reboot. It turns itself off immediately after turning on.
Replication steps:
1. Follow steps in OP.
2. Reboot to bootloader (adb reboot-bootloader)
3. Flash twrp_mata-6.img (fastboot flash boot twrp.img)
4. adb push addonsu-14.1-arm64.zip /sdcard/
5. Install .zip in TWRP
6. Reboot
Anybody else getting this issue? The only way I've been able to fix it is to re-flash LOS.
EDIT: Thanks to @bmg1001, this issue is resolved (for me at least) by using this build of TWRP... Sorry, I can't post links yet! Can someone link this please?
https:// drive.google. com/file/d/1Pp9Hep-EEGNHLl6I_ob7ugihpKfrAcWm/view?usp=sharing
Note that flashing this TWRP build will allow you to reboot to recovery at any time without having to reflash TWRP, as mentioned in the OP.
Click to expand...
Click to collapse
Good Morning!
The URL for TWRP isn't working for me. I copy pasted it in chrome address bar. Could someone please kindly help? I'm drooling to get started!
makbomb said:
Good Morning!
The URL for TWRP isn't working for me. I copy pasted it in chrome address bar. Could someone please kindly help? I'm drooling to get started!
Click to expand...
Click to collapse
Go to the rooting guide and it's in there. Use the mirror
---------- Post added at 01:36 PM ---------- Previous post was at 01:29 PM ----------
One thing I noticed is cell service is much weaker so far. In this same spot if my bedroom used to go from 99 to 103 dbm. Now it's at a118. Will monitor and report.
Shows 0 bars of service. Used to be 2-3
strictlyphat said:
Go to the rooting guide and it's in there. Use the mirror
Click to expand...
Click to collapse
Thanks, but it sounds like @tclaybor is using a different version, provided to him by @bmg1001 , since you'll see he was trying to link a google drive to that version?
makbomb said:
Thanks, but it sounds like @tclaybor is using a different version, provided to him by @bmg1001 , since you'll see he was trying to link a google drive to that version?
Click to expand...
Click to collapse
The one in bmg1001 thread worked. But have to click mirror.
---------- Post added at 02:54 PM ---------- Previous post was at 02:54 PM ----------
If u do get it installed let me know about signal. Mine taking big hit.
I just upgraded my N6 to the latest Lineage OS.
Now I'm getting an image mismatch error. My image shows as N6F27M.
I've done some reading and downloaded the factory image from Google.
I know I need to flash the vendor.img to my phone.
I unzipped it, and unzipped the zip inside the zip. I can't find a vendor.img.
Has something changed?
Also, I'd really like to get on the Google Pay bandwagon. Can I relock the bootloader and not lose any data? Also will OTAs from LOS still work?
Thanks,
PC
Same here.
Would there be any issues with this? I keep seeing the message on boot. Hopefully the next nightly might address this? Thoughts from anyone?
It will be addressed in the next build, this was confirmed by the device maintainer. Check the LOS thread, there you will find more info about this.
Great news. Thanks.
Same here... and this confirms it too: https://developers.google.com/android/blobs-preview
I built Lineage 15.1 flashed it and had no problems.
---------- Post added at 06:35 PM ---------- Previous post was at 06:31 PM ----------
c_lega said:
Same here... and this confirms it too: https://developers.google.com/android/blobs-preview
Click to expand...
Click to collapse
The Nexus 6 Shamu isn't supported by Google anymore, there is no listing for Shamu there.
Edit before publishing: I started writing this for all variants other than sprint, but I'll now make a separate thread for variants that have kdzs and those that don't, otherwise this will be a mess.
Firstly, keep in mind that no one is responsible if you end up bricking your device! There is currently no way to recover from a hard brick other than sending your phone in for repair, so make sure you follow every single step carefully if you wish to proceed!
Additionally, flashing an xbl through DD may not pass randomly even if it appears that it has worked, so be aware of the risks. Only at&t users will need to flash the xbls anyway since that is the only variant other than sprint which does not have kdzs available.
Users with the AT&T variant who are stuck on pie: temp root only works on android 10, as such you will unfortunately not be able to bootloader unlock your device. The firehose may leak at some point in a few months, and you will be able to unlock (and update manually) if it does.
The process for unlocking bootloaders on models other than the sprint one (specifically At&t for this guide) is practically identical; however, it uses different xbl_config.img and xbl.img files, which need to be specific for your device from the pie firmware.
The version naming may not be the exact same for other models, but you just have to ensure that you are on the March patch or below. If you are on April, you can find the guide to switch slots and do so in order to revert to March. To STOP UPDATES, fully uninstall or disable the update center packages either with ADB or package disabler pro for LG, which you can easily find online.
So I repeat, you're going to follow the sprint g8 bootloader unlocking guide, but you have to use the xbl and xbl_config for your device rather than the ones provided in the sprint guide. The engineering abl is the same, but I'll include it here anyway so that you don't have to mess around with any of the files provided in the sprint g8 guide.
Now, steps that are to be ignored and steps that may differ slightly:
Keep in mind that I'm only mentioning what you should be aware of and what may be different, but you still have to follow the guide written by BrandonB1218 in general.
1a: Of course, you still need a vulnerable firmware, and sadly AT&T does not provide kdzs, so you cannot bootloader unlock if you are on the May patch.
You can Ignore this: I found that another method that most likely stops updates is following this guide on youtube. It's supposed to bypass frp lock, but it also gets by all the LG agreements you have to accept, so it will ask you to agree to these if you ever open up the software update option in settings and will probably not update if you don't.
2: Some people had issues with different versions of the mroot script, so try all of them before you come asking for help please. I also suggest that you just temp root without running the temp root magisk setup as you may end up bricking if you accidentally flash a module or make magisk flash a patched boot img (DO NOT FLASH ANYTHING OTHER THAN WHAT'S INCLUDED IN THE GUIDE).
I suggest running the backup script and the commands to make sure you're completely safe, but make sure you keep them separate because a lot of the partitions included in the commands that @BrandonB1218 mentioned are device specific and include your IMEI. The backup script should only backup the partitions that aren't device specific such as system, and this is probably the one you'll need if at all because you shouldn't be touching other partitions. STILL DO BOTH THOUGH
3a: Yes, you have to run the command to find out which slot you're on, but you will not flash anything from the pie or 20d sprint backup that's listed there, or else you will likely brick.
3b and 3c: This should all be the same: If your active slot is A, follow 3b, and if your active slot is B, follow 3c. The commands should also be the same, just with different files.
If your active slot is A, but the files included for your device are also named xbl_a.img, for example, you can just rename them to fit with the command.
Otherwise, you can just change this, for example,
dd if=/storage/emulated/0/Download/xbl_b.img of=/dev/block/bootdevice/by-name/xbl_b
to this:
dd if=/storage/emulated/0/Download/xbl_a.img of=/dev/block/bootdevice/by-name/xbl_b
You also need to flash the engineering laf, so either rename the file or change the command so it works. The link is embedded
Overall, its just important that you take the right file in the first part of the command and flash it to the correct partition of the correct slot in the second part.
If I remember correctly, the method to boot into fastboot is hold vol- and power until the screen goes black (while the phone is plugged into the computer) and then to let go of power as soon as that happens.
4a and 4b: You do not want to do either of these as the boot img and other partitions vary per variant. I unfortunately do not have the magisk patched At&t boot img, but you can patch it yourself from the backup you made and flash it. It might be good to do this beforehand, but you could also just temp root again and dd flash it.
Alternatively, you can flash the metaphysics 1.7 kernel with twrp and magisk included, but you still have to follow the rest of the twrp installation in the sprint g8 bl unlocking guide. TWRP is the same for all US variants.
Congrats! You should now be bootloader unlocked and ready to go at this point. If you ever find yourself unable to boot on the slot which DOES NOT have the engineering abl, you can always switch to the slot with the engineering abl, go to fastboot, and fastboot flash your backed up partitions.
Credits:
Obviously to BrandonB1218, for writing the sprint g8 bootloader unlocking guide
vl48 for basically answering all my questions and providing the needed files
j4nn for writing the temp root
Mr. Zhu for twrp
KamioRinn for metaphysics
Anyone else who contributed in telegram to get this to work!
Amazing! Can't wait to do this. I'll report back when I get this phone unlocked.
Thanks for taking the time.
Files can't be downloaded dead link
blumix said:
Files can't be downloaded dead link
Click to expand...
Click to collapse
No issues here
Hi and thanks for your job. Can I flash the lg g8 at&t with the unlocked firmware G820QM10I after that I unlocked the bootloader? Because I live in UK and At&t Ba....ds blocked the use of the 3g connection, so I cannot use at my home.... But I thought that whit an unlucked firmaware I could do.
Pietrobell86 said:
Hi and thanks for your job. Can I flash the lg g8 at&t with the unlocked firmware G820QM10I after that I unlocked the bootloader? Because I live in UK and At&t Ba....ds blocked the use of the 3g connection, so I cannot use at my home.... But I thought that whit an unlucked firmaware I could do.
Click to expand...
Click to collapse
No sorry. Not sure exactly what your problem is, but it might be solvable with root
Shtiff1 said:
No issues here
Click to expand...
Click to collapse
You said there is not issues? Since you got the files can you upload it to medafire because it not working?
---------- Post added at 09:22 AM ---------- Previous post was at 09:19 AM ----------
blumix said:
You said there is not issues? Since you got the files can you upload it to medafire because it not working?
Click to expand...
Click to collapse
I am talking about the AT&T_G8.zip
blumix said:
You said there is not issues? Since you got the files can you upload it to medafire because it not working?
---------- Post added at 09:22 AM ---------- Previous post was at 09:19 AM ----------
I am talking about the AT&T_G8.zip
Click to expand...
Click to collapse
@antintin zip not downloading, FYI
---------- Post added at 07:15 PM ---------- Previous post was at 06:59 PM ----------
blumix said:
You said there is not issues? Since you got the files can you upload it to medafire because it not working?
---------- Post added at 09:22 AM ---------- Previous post was at 09:19 AM ----------
I am talking about the AT&T_G8.zip
Click to expand...
Click to collapse
I can't find it, sorry. I'm on Verizon
Hey, thanks for the guide. I'm rather worried about trying this as LG's newer models are so darn easy to brick. AT&T variant has no LG Bridge support which is incredibly stupid. At least we have kind people like you helping us free our phones
My LG G8 is a secondary phone right now, and as such, I'm very interested in trying this out. Unfortunately, the download link for AT&T_G8.zip give me a 404.
Not shocking that it's still dead. Tried telling antintin on Telegram the day after he posted this that there were issues retrieving the file from here and he blew me off, telling me it was probably because of my country. Tried with home USA network, USA VPN, and UK VPN. ?
Espen115 said:
Not shocking that it's still dead. Tried telling antintin on Telegram the day after he posted this that there were issues retrieving the file from here and he blew me off, telling me it was probably because of my country. Tried with home USA network, USA VPN, and UK VPN. ?
Click to expand...
Click to collapse
That's because I tried it myself along with a few others and it still worked... I only used that hosting site because I haven't made an account for any other
antintin said:
That's because I tried it myself along with a few others and it still worked... I only used that hosting site because I haven't made an account for any other
Click to expand...
Click to collapse
Would it be possible to have someone upload it to their Google Drive, or Dropbox and send the link via PM or something? That way, when the person confirms that he has downloaded it, it can be removed from the service in question.
lightningdude said:
Would it be possible to have someone upload it to their Google Drive, or Dropbox and send the link via PM or something? That way, when the person confirms that he has downloaded it, it can be removed from the service in question.
Click to expand...
Click to collapse
Why would it have to be removed?... I'll just upload it when I get home and have time
antintin said:
Why would it have to be removed?... I'll just upload it when I get home and have time
Click to expand...
Click to collapse
Just out of consideration for space in your account, in case you were low on free space. I also didn't notice that it was a < 3MB file.
so is someone going to reupload the file or what? cant even download it from the op attachment.
does this even work with 20m or are those of us out of luck?
File Broken
Anyone has the copy of AT&t_G8.zip? Its 404 now.
MaemoToWindows said:
Anyone has the copy of AT&t_G8.zip? Its 404 now.
Click to expand...
Click to collapse
Always has been.
I have it but it won't let me add it
Can u email it to me? [email protected]
Hi guys. First post here and I'm not around my files so it will be a straight forward guide with no downloads right now, you're smart, you know where to source them...
Ok first and foremost, Unlock your bootloader, Motorola makes it easy and there are good guides on this site to do that.
Once your bootloader is unlocked your going to look for an Unofficial TWRP package for the Lenovo K12 Pro... "What?", You say... Yep K12 Pro. Download it and jump over to your boot loader and flash it or just boot to it through fastboot and now you have a way to install root permanently, or not if you would rather not, but you have that option now.
Next find the lastest Magisk apk and get that joker installed using TWRP. Now reboot into system and everything should load up as normal BUT now you have root with TWRP recovery. I have did this at least 100 times since figuring it out and sometimes I do this with a fresh factory flash and sometimes I do this as is without even wiping user data before or after. I'm no expert and I don't care to lose my files so on the rare occasion that I do have a boot loop or soft brick, I get myself into recovery and flash ANY of the cebu firmwares and do it all over again...
Ok, so now we know how to get root and custom recovery... Next find an AB version of Gsi 11 or "borrow" the latest system.img from an Android 12 update or firmware image and open up fastboot again and flash only the system.image to the system partition. Wipe or don't wipe, up to how lucky you're feeling, and then reboot to system... 11 will take 2-3 minutes to boot the first time and I had nearly all functionality when it did. 12, well, that's a little different, it took 3-4 minutes to boot to the setup screen and then lagged like crazy BUT it eventually started downloading a few files it was missing and got better. I couldn't get my calls or messaging to work right but I could hear my phone ring but it never called the phone app to open and let me answer... Weird stuff BUT FYI 12 is a pretty nice to look at OS and maybe one of you guys can take this to the next level and get some true usefulness out of it. I know it's not very technical but when one of you true geniuses try it and get it worked out please feel free to post a true guide with proper instruction and proper terms.
That's all I got guys. Thanks for reading this and ALSO if anybody has a complete list of fastboot and adb commands for the g9 Power or the K12 Pro please share them with me. I've gotten better at getting around but I'm not near as good as if like to be.
Obligatory safety PSA:
The Lenovo K12 Pro is just the Moto G9 Power sold under a different name, however, there could be minor differences that could cause problems.
Also, while searching for this unofficial TWRP build, I only found it on websites like unofficialtwrp.com, and the like. I couldn't find one on XDA. I was unable to find the device tree, or the kernel sources used by this website anywhere on the internet, and as such, the TWRP images provided on such websites are literal blackboxes.
TWRP images created and shared on XDA can be trusted, the source code used to create the image is displayed on the posts of the images, and XDA itself is a trusted site.
Here is what the official TWRP team have to say on the matter:
Unofficial TWRP Downloads
Like the TWRP team say, it is up to you to flash these images or not, but be careful.
mistersmee said:
Obligatory safety PSA:
The Lenovo K12 Pro is just the Moto G9 Power sold under a different name, however, there could be minor differences that could cause problems.
Also, while searching for this unofficial TWRP build, I only found it on websites like unofficialtwrp.com, and the like. I couldn't find one on XDA. I was unable to find the device tree, or the kernel sources used by this website anywhere on the internet, and as such, the TWRP images provided on such websites are literal blackboxes.
TWRP images created and shared on XDA can be trusted, the source code used to create the image is displayed on the posts of the images, and XDA itself is a trusted site.
Here is what the official TWRP team have to say on the matter:
Unofficial TWRP Downloads
Like the TWRP team say, it is up to you to flash these images or not, but be careful.
Click to expand...
Click to collapse
Agreed, I posted as a proof of concept so people with more know how could improve upon. Use this at your own discretion and have fun in doing so.
Is there a way you could post a detailed, step by step instructions of this, please?
I've found the unofficial twrp, but haven't rooted a phone in over 2 years, so I'm a bit rusty, plus things have changed a lot these last couple years.
I'd really appreciate if you could take your time for that.
Thanks in advance.
I don't mind helping you out but I can't post publicly because the rules of the forum and the fact that it's unofficial. I'll get a guide wrote up and PM you. I've had no issues with my device at all but remember it is use at your own discretion.
Dauksza72 said:
I don't mind helping you out but I can't post publicly because the rules of the forum and the fact that it's unofficial. I'll get a guide wrote up and PM you. I've had no issues with my device at all but remember it is use at your own discretion.
Click to expand...
Click to collapse
That would be awesome mate!
I really appreciate that!
Thanks in advance.
Dauksza72 said:
I don't mind helping you out but I can't post publicly because the rules of the forum and the fact that it's unofficial. I'll get a guide wrote up and PM you. I've had no issues with my device at all but remember it is use at your own discretion.
Click to expand...
Click to collapse
I was able to boot into TWRP but when I flash Twrp.img to recovery it won't stick, I always had to do fastboot into recovery if I try to boot into recovery it just reboots back into system, also can't remove any junkware from system, it always gives me error when I tried to remove it using root browser, im still on stock
zfk110 said:
I was able to boot into TWRP but when I flash Twrp.img to recovery it won't stick, I always had to do fastboot into recovery if I try to boot into recovery it just reboots back into system, also can't remove any junkware from system, it always gives me error when I tried to remove it using root browser, im still on stock
Click to expand...
Click to collapse
Check out https://forum.xda-developers.com/t/recovery-unofficial-twrp-3-5-2-cebu.4279917/
for TWRP.
As for removing junkware, as you may or may not know, dynamic partitions is a thing since Android 10. In it, the /system, /product and /vendor partitions have been subsumed under a /super partition. And Google has conveniently used a type of ext4 filesystem for that /super partition, that is read-only.
TL;DR: You cannot modify Android using any sort of "root browser" or inside TWRP, for that matter, anymore.
Off the top of my head, the only way you can remove "junkware" is through some Magisk modules, and even they might not even work.
There are three ways to debloat AFAIK:
Magisk - this is my preferred method. You either replace apks you want removed or empty the /product/etc/nondisable folder so they can be disabled. Takes minimal effort to figure out how to make modules and no scripting knowledge required.
Cross-flashing - you can flash retail software, often including modem firmware, to most Moto phones. The result is a clean system with no carrier junkware.
System R/W Scripts - this is the most nonsensical of the options(IMO), but this option exists if you look around and want to experiment. The big drawback here is that you have to redo everything after every update.
Dauksza72 said:
I don't mind helping you out but I can't post publicly because the rules of the forum and the fact that it's unofficial. I'll get a guide wrote up and PM you. I've had no issues with my device at all but remember it is use at your own discretion.
Click to expand...
Click to collapse
Hello. I know you're new and welcome. I just want you to know, being an unofficial twrp isn't necessarily bad by itself. It's that the sources can't be verified. Lots of devces don't have official TWRPs, yet still have a rockin development section with TWRP instructions, as long as it's shared on a trusted site (I only trust 1 other) and lists it's sources and, even then, it should have the warning. Lots of scam sites target root noobs, as you've probably noticed. I don't think sharing instructions would have been against the rules, but should include a warning to let people know it's a questionable twrp build and it poses a risk, but all of our phones are at risk anyway. We don't have to worry about it anymore though since we have an official and still we are at risk, just far less risk. It comes with the territory. On the other hand, I've been I've been doing this for a very long time with countless phones and I've never noticed any malicious activity on any on any of them.