Related
Deleted
bubba1601 said:
Hi
I have this new device but it's not any of the versions listed here (Nora/Rhyanna)
It's the UK version XT1920-15 sim unlocked, I'm just wandering if the steps to unlock/root are the same on this device as the other versions?
Click to expand...
Click to collapse
https://www.getdroidtips.com/unlock-bootloader-moto-e5-play/
I used this guide to unlock it. I also have this phone, but mine is from latin america, and it should work for yours. :good:
Deleted
bubba1601 said:
Your device is not the same.
The American / latin American version has android 8.0, 2 GB ram and a 5.2 inch screen.
The UK version has android 8.1, 1gb of ram and a 5.3 inch screen.
All such tutorials that work for the US version DON'T work on the UK version and TWRP installation fails completely.
Please be mindful when advising users things "should" work, as it doesn't work and your device is completely different to mine, so should not be attempted from that link.
Click to expand...
Click to collapse
No my phone has 1Gb of Ram and 16gigs of storage space along with 8.1 and TWRP installed. I used that guide to unlock the bootloader the TWRP in that guide doesn't work for our phones. I managed to find the TWRP version of the phone.
Deleted
bubba1601 said:
The guide says it's for android 8.0 though?
I still can't unlock the bootloader!
Click to expand...
Click to collapse
fastboot oem get_unlock_data
"Now command will return a string which you need to copy the string to a notepad with a single line by deleting all spaceNotepad
(Note: Only copy the highlighted sections above. Do not copy the INFO or (bootloader) prefix)"
"To Get Bootloader Key for Moto E5 Play - Open the website Motorola’s unlock the bootloader site by Signing up or Log in in via Google Plus account"
Link:https://accounts.motorola.com/ssoau...ct/standalone/bootloader/unlock-your-device-b
Make an account, also check if your device can even be unlocked on the website.
"Once you click the "Can my Device be unlocked?" you will receive a mail with unlock key.
Now copy the unlock key and type the following command and enter.
fastboot oem unlock UNLOCK_KEY
Here UNLOCK_Key is the place where you have to paste the unlock key which you copied from the email.
That's it! Your device will unlock. hah! Have fun!"
That's how you unlock the boot loader
Link for TWRP for PETTYL:https://mega.nz/#!anwAACZT!MJ95FCiIDH-kkLaZLpFvnKT5j_3Fe2goU-aZmSVeCKo
I couldn't find on XDA so I uploaded it to mega.
Deleted
Here a twrp buckup Twrp image and rooted boot for XT1920-15 if you manage to boot into twrp or try booting boot image https://drive.google.com/drive/u/0/mobile/folders/1P0yVep9l3yTN2Hzy7QiRXj3kuL_N7Dxz?usp=sharing
did the op get it sorted
Deleted
bubba1601 said:
I'm running stock again.
No root, no twrp and as far as I'm concerned, project treble ROMs/images are complete waste of time, especially for this device where half the posted steps don't work, supplied resources don't work or twrp images and twrp back ups supposedly for this device don't work
Worse still, I had to pay to redownload my firmware.
Click to expand...
Click to collapse
No idea why it dosent work for you I maneged to flash twrp and root it with magisek also tried linege and ResurexionRemix it works fine only xposed dosent work
Deleted
plscotland said:
Here a twrp buckup Twrp image and rooted boot for XT1920-15 if you manage to boot into twrp or try booting boot image https://drive.google.com/drive/u/0/mobile/folders/1P0yVep9l3yTN2Hzy7QiRXj3kuL_N7Dxz?usp=sharing
Click to expand...
Click to collapse
Can I flash this Recovery to XT1920-16 pettyl?
The file Moto_E5_XT1920-15-recovery.img is TWRP or STOCK recovery?
Also i'm loocking for Stock recovery for XT1920-16
Deleted
I just build custom recovery for pettyl -- ORANGE FOX , download at orangefox.tech
thanks. enjoy!
~whodat aka flash
Deleted
bubba1601 said:
There's already three different TWRPs for PETTYL.....two work one doesn't.
I made a TWRP for pettyl and it works 100% , The reason the others do not work is because they have EXT4 filesystem set to data partitions in the fstabs they were made with. Data partition is set to f2fs and thus it cannot be read. I also made a decrypt.zip for pettyl aswell, and I do not even own this device... I have only dove into android dev less than 2 months ago
Many people are already confused about twrp so do we really need another one to confuse everyone even more?
Click to expand...
Click to collapse
*triple facepalm* are you serious ?!?!
Maybe this site and android modifications is not for you bubba.
---------- Post added at 12:44 PM ---------- Previous post was at 12:32 PM ----------
bubba1601 said:
The comment you quoted says it's a TWRP file and I've not seen the stock recovery available for PETTYL .
Just bear in mind that I'm assuming the xt1920-15 that I have and txt1920-16 you have are identical, but I obviously cannot confirm that or do I know if they work the same I'm just assuming they do.
Click to expand...
Click to collapse
lol to get stock recovery file all you have to do is fastboot boot TWRP or OrangeFox and make a backup of recovery. Its that simple, but what would anyone want with stock recovery anyway?
If you really want it you can get the full stock firmware here, extract it and you will have stock recovery.img along with stock boot.img and everything else....
https://mirrors.lolinet.com/firmware/moto/pettyl/official/
Again, ENJOY!
Deleted
bubba1601 said:
If you had explained what's better or different about your recovery rather than making a mocking reply I would not have asked if another custom recovery was necessary......
There's currently two working TWRPs for PETTYL and another posted on here that doesn't work at all.
Every PETTYL user that's posted here has had issues with both TWRP versions or have been unable to follow the instructions on how to install either version.
Don't tell me this site and android modding isn't for me, because when the time is right I'll decide to stop, you will not make that decision or suggest I stop because you didn't like my question - which you didn't answer.
So I'll ask you calmly and politely again.
Is it really necessary to have so many different TWRPs and custom recovery for PETTYL?
What does your orange fox offer different to TWRP?
You haven't even posted a proper link......no explanation, no proceedures, no instructions. Nothing.
Explain yourself so people understand, don't mock.
Edit.
My question was not a criticism of what you have done.
I've stopped any further modifications to my own PETTYL because it's obvious a 1gb ram android go device cannot handle 9.0 pie and in the 10 years I've been modding various devices the E5 play is the most complicated piece of S*** I've I've used.
But even worse, if the user base cannot ask a simple question of people without someone like you being rude and sarcastic in reply and telling a fellow user to go away - then I've made the right decision not to work with my E5 or this thread any longer.
The user and support base for the E5 play PETTYL has suddenly hit an all time low, and doesn't need rudeness or your sarcasm to justify its existence..
Click to expand...
Click to collapse
He explained y other recoveries had prob and y his wouldn't next it has added features such as built in magisk and etc. test it to see other extra features instead of being a lil upset and taking it out on ppl being nice and fixing ur recovery probs
bubba1601 said:
If you had explained what's better or different about your recovery rather than making a mocking reply I would not have asked if another custom recovery was necessary......
There's currently two working TWRPs for PETTYL and another posted on here that doesn't work at all.
Every PETTYL user that's posted here has had issues with both TWRP versions or have been unable to follow the instructions on how to install either version.
Don't tell me this site and android modding isn't for me, because when the time is right I'll decide to stop, you will not make that decision or suggest I stop because you didn't like my question - which you didn't answer.
So I'll ask you calmly and politely again.
Is it really necessary to have so many different TWRPs and custom recovery for PETTYL?
What does your orange fox offer different to TWRP?
You haven't even posted a proper link......no explanation, no proceedures, no instructions. Nothing.
Explain yourself so people understand, don't mock.
Edit.
My question was not a criticism of what you have done.
I've stopped any further modifications to my own PETTYL because it's obvious a 1gb ram android go device cannot handle 9.0 pie and in the 10 years I've been modding various devices the E5 play is the most complicated piece of S*** I've I've used.
But even worse, if the user base cannot ask a simple question of people without someone like you being rude and sarcastic in reply and telling a fellow user to go away - then I've made the right decision not to work with my E5 or this thread any longer.
The user and support base for the E5 play PETTYL has suddenly hit an all time low, and doesn't need rudeness or your sarcasm to justify its existence..
Click to expand...
Click to collapse
Don't be a d*$k lashing out at a dev who does this work FOR free using up HIS free time to make it possible for you to make this complaint. We developers have to research to gain this knowledge. Be courteous and try to search the web to find the answers you seek and to fill in the blanks. Possibly guide others users in the right direction based on the knowledge you discover.
Don't bite the hand that feeds you. Listen to some nine inch nails, you might learn a thing or two about how to properly human.
He doesn't even own that device yet goes out of his way to provide support for it just for ungrateful individuals such as yourself to lash out at him for not explaining things clearly enough. If you lack the knowledge to fill in the blanks that he may have missed, that just shows that you're at risk of bricking your device from lack of knowledge on the subject. It won't hurt you to do a bit of research for yourself.
Sincerely,
The guy helping to guide that developer you lashed out at to supporting 64bit for YOUR DEVICE.
So this is my first thread and had a heck of a time trying to successfully root the 6t using Magisk and TWRP. Why might you ask? Because the unofficial TWRP for the Oneplus 6T has a bug with the Media Transfer Protocal (MTP) so once TWRP is installed, you can't use it to install flashable zips. The device shows the 6T internal storage as empty and therefor you cant flash a zip if TWRP cant find a zip to flash. So anyways heres what I did to get this working.
*****NOTE***** I am not a dev, i simply stumbled across a solution (work-around), to the TWRP MTP issue, and therefor if anything goes wrong with your device, it is on you. DO NOT BLAME ME if you brick your device. If you so choose to follow this guide, ANY/ALL risk and the subsequent consequences, are YOURS AND YOURS ALONE.
***CREDITS*** TO: @topjohnwu for MAGISK & @mauronofrio for his unofficial android Q TWRP
STEP1: Grab this TWRP https://androidfilehost.com/?fid=1395089523397961761
STEP2: Grap magisk beta v19.2 https://github.com/topjohnwu/Magisk/releases/download/v19.2/Magisk-v19.2.zip
STEP3: Run the following command: fastboot flash boot twrp.img
***NOTICE ABOVE COMMAND*** (uses "flash boot" instead of "boot")
STEP4: Manually reboot into back into recovery
***NOTE*** once in recovery I used "swipe to allow modifications" , dont know if it matters
STEP5: Go to adb sideload tab from within TWRP Recovery
STEP6: Once adb sideload finishes loading, run the following command: adb sideload magisk.zip
STEP7: Let sideload finish, reboot device, open magisk app and follow its instructions to finish install.
kluongo said:
So this is my first thread and had a heck of a time trying to successfully root the 6t using Magisk and TWRP. Why might you ask? Because the unofficial TWRP for the Oneplus 6T has a bug with the Media Transfer Protocal (MTP) so once TWRP is installed, you can't use it to install flashable zips. The device shows the 6T internal storage as empty and therefor you cant flash a zip if TWRP cant find a zip to flash. So anyways heres what I did to get this working.
*****NOTE***** I am not a dev, i simply stumbled across a solution (work-around), to the TWRP MTP issue, and therefor if anything goes wrong with your device, it is on you. DO NOT BLAME ME if you brick your device. If you so choose to follow this guide, ANY/ALL risk and the subsequent consequences, are YOURS AND YOURS ALONE.
***CREDITS*** TO: @topjohnwu for MAGISK & @mauronofrio for his unofficial android Q TWRP
STEP1: Grab this TWRP https://androidfilehost.com/?fid=1395089523397961761
STEP2: Grap magisk beta v19.2 https://github.com/topjohnwu/Magisk/releases/download/v19.2/Magisk-v19.2.zip
STEP3: Run the following command: fastboot flash boot twrp.img
***NOTICE ABOVE COMMAND*** (uses "flash boot" instead of "boot")
STEP4: Manually reboot into back into recovery
***NOTE*** once in recovery I used "swipe to allow modifications" , dont know if it matters
STEP5: Go to adb sideload tab from within TWRP Recovery
STEP6: Once adb sideload finishes loading, run the following command: adb sideload magisk.zip
STEP7: Let sideload finish, reboot device, open magisk app and follow its instructions to finish install.
Click to expand...
Click to collapse
The twrp we have works fine dude
Lol
And you are referring to using TWRP on Android Q beta correct??? Because when I tried using the latest stable TWRP for 6T but with Android Q... It would not flash
JUST FYI
The mtp issue is a known bug with the Q developer preview.
Rite from download page.
"Known Issues
Camera, portrait mode does not work
Ambient Display is not working
System stability issues
Encryption will change in the next preview build
Some apps may not function as expected when running on this Developer preview release
Issue With MTP cannot copy rollback from PC to Phone."
Not with twrp.
The only issue with twrp at the moment is reading v3 synthetic keys to decrypt if you have pin/password set and running may security patch.
kluongo said:
And you are referring to using TWRP on Android Q beta correct??? Because when I tried using the latest stable TWRP for 6T but with Android Q... It would not flash
Click to expand...
Click to collapse
Thank you twinn for clarifying that... So I stand corrected on twinns point... But not on fullofhells needless comment
kluongo said:
Thank you twinn for clarifying that... So I stand corrected on twinns point... But not on fullofhells needless comment
Click to expand...
Click to collapse
Use Blu spark, secondly the resolution for mtp, is enable dev options and turn on USB file transfer. Then USB works. Use a prepatched twrp and pre rooted twrp Blu spark kernel. Flash in fastboot, twrp works fine. Fully. Not apparently not needless if u still have issues posting erroneous comments that serve no purpose. U should read. It serves so many purposes. U would see the fix for mtp on Q and how in the main twrp thread a week or more ago I discussed how twrp works fine if u do as I listed there.. I read everything, I assumed every other user does the same.
fullofhell said:
Use Blu spark, secondly the resolution for mtp, is enable dev options and turn on USB file transfer. Then USB works. Use a prepatched twrp and pre rooted twrp Blu spark kernel. Flash in fastboot, twrp works fine. Fully. Not apparently not needless if u still have issues posting erroneous comments that serve no purpose. U should read. It serves so many purposes. U would see the fix for mtp on Q and how in the main twrp thread a week or more ago I discussed how twrp works fine if u do as I listed there.. I read everything, I assumed every other user does the same.
Click to expand...
Click to collapse
:highfive:
WOW.
Where to start here?
The TWRP you linked (https://androidfilehost.com/?fid=1395089523397961761) is for OPO 6, not 6T, but it does say fajita, and not enchilada
TWRP works fine for us, if you use the latest.
P and Q are different beasts, as of now, and there are posts on how to flash TWRP on Q.
This thread seems redundant an unnecessary.
But....that's just my $.02
So first, i just searched all 9 pages of the 6t Guides thread section... not one single thread explaining, or detailing, any guide or tutorial, for individuals to play around with Q... On that point, not redundant.... Secondly the fajita image i posted is not for the 6... its from mauronofrio for the 6t, under the thread he started for twrp images for the 6t... so.. if it is in fact for the 6... maybe he should be notified?..... and if this thread is redudnant, why cant i find any guide detailing steps to mess around with Q?
kluongo said:
So first, i just searched all 9 pages of the 6t Guides thread section... not one single thread explaining, or detailing, any guide or tutorial, for individuals to play around with Q... On that point, not redundant.... Secondly the fajita image i posted is not for the 6... its from mauronofrio for the 6t, under the thread he started for twrp images for the 6t... so.. if it is in fact for the 6... maybe he should be notified?..... and if this thread is redudnant, why cant i find any guide detailing steps to mess around with Q?
Click to expand...
Click to collapse
Here's a thread about Q on the 6T: https://forum.xda-developers.com/oneplus-6t/how-to/oneplus-6t-androidq-beta-release-links-t3928174 (specifically post #62)
The TWRP link page you linked specifically says "Download test-twrp-3.3.0-Q-fajita.img for the OnePlus OnePlus 6" but I commented that it was correctly for the 6T. I would get ahold of Mauronofrio to inform him of the error.
It's only redundant because after reading the thread I posted above^, it seems we have some waiting to do until we even get a stable Q build.
Thanks!
Yes, I did in fact see that thread and briefly read it over. On the contrary, it did not help me in the manner i needed. Alot of people don't have the time to dig through threads to find an answer to a problem, especially from a thread which was never intended to address said problem in the first place (according to its title, as well as the entire first page of posts). I have been following these forums, quietly, since the galaxy s4 was released and hence, when I look for a guide or missing piece of information I require, i know to read and look around a bit before starting a thread. As such, I have not needed to create a thread EVER... and then there was this problem with no clear cut guide, thread, solution... nada.... so alas, I decided to provide one for a change... I am now reminded why i choose to stay mostly quiet... because xda has become a honeypot full of negative trollers, and "full-of-themself" donald trumps, when it should contain more people offering constructive critisicm, positive environment, and turning the less knowledgeable into the more informed android enthusiast.
Just my $.01
kluongo said:
Yes, I did in fact see that thread and briefly read it over. On the contrary, it did not help me in the manner i needed. Alot of people don't have the time to dig through threads to find an answer to a problem, especially from a thread which was never intended to address said problem in the first place (according to its title, as well as the entire first page of posts). I have been following these forums, quietly, since the galaxy s4 was released and hence, when I look for a guide or missing piece of information I require, i know to read and look around a bit before starting a thread. As such, I have not needed to create a thread EVER... and then there was this problem with no clear cut guide, thread, solution... nada.... so alas, I decided to provide one for a change... I am now reminded why i choose to stay mostly quiet... because xda has become a honeypot full of negative trollers, and "full-of-themself" donald trumps, when it should contain more people offering constructive critisicm, positive environment, and turning the less knowledgeable into the more informed android enthusiast.
Just my $.01
Click to expand...
Click to collapse
No need to stay quiet, just learn to use the search function, and participate on the already created threads instead of creating new ones. (Just a suggestion...)
And the ad hominem attempts are unnecessary.
Love,
'full-of-myself'
No..
Love,
@fullofhellself
?
Damn wth did I do..lol... We are a system of checks and balances for all users. Full of myself... Yeah okay.. better be nice or mom's not gunna pay your internet bill.. and I hate trumpian politics. I just loathe redundant unusable posts. As do my constituents here..
kluongo said:
Yes, I did in fact see that thread and briefly read it over. On the contrary, it did not help me in the manner i needed. Alot of people don't have the time to dig through threads to find an answer to a problem, especially from a thread which was never intended to address said problem in the first place (according to its title, as well as the entire first page of posts). I have been following these forums, quietly, since the galaxy s4 was released and hence, when I look for a guide or missing piece of information I require, i know to read and look around a bit before starting a thread. As such, I have not needed to create a thread EVER... and then there was this problem with no clear cut guide, thread, solution... nada.... so alas, I decided to provide one for a change... I am now reminded why i choose to stay mostly quiet... because xda has become a honeypot full of negative trollers, and "full-of-themself" donald trumps, when it should contain more people offering constructive critisicm, positive environment, and turning the less knowledgeable into the more informed android enthusiast.
Just my $.01
Click to expand...
Click to collapse
Chill out, no need to bring politics into a phone modding forum, seems kinda silly doesn't it? But yes, you should have just gone to the existing 6T Android Q thread and just used the search function. Wouldn't have been that hard. I never even installed Android Q and I even remember reading through numerous posts of people wanting to return to stock. I don't blame you for posting or anything, I'm just letting you know that there definitely was a clear-cut easy way to find a way to go to stock from the Q beta.
LMAO xda is getting out of control... I agree with the OP as the other thread is not about this particular issue... Which was getting twrp and magisk going on the Q beta (NOT returning to stock - like where did that even come from if your following along lol)
I could easily see him getting flamed for hijacking the thread if he posted this tutorial in the other person's thread. You can't win for loosing any more.
This is also why I stay mostly silent on here smh!
juggz143 said:
LMAO xda is getting out of control... I agree with the OP as the other thread is not about this particular issue... Which was getting twrp and magisk going on the Q beta (NOT returning to stock - like where did that even come from if your following along lol)
I could easily see him getting flamed for hijacking the thread if he posted this tutorial in the other person's thread. You can't win for loosing any more.
This is also why I stay mostly silent on here smh!
Click to expand...
Click to collapse
omfg. Read post 1. Reread. Read again. Now read your sentences. Try not to feel dumb. Search function = no one wastes time. That's all.
fullofhell said:
omfg. Read post 1. Reread. Read again. Now read your sentences. Try not to feel dumb. Search function = no one wastes time. That's all.
Click to expand...
Click to collapse
[emoji848]Maybe it's you who should re-read. The first post doesn't mention anything about returning to stock. He's trying to install magisk on a BETA, which is the polar opposite of returning to stock [emoji2375][emoji2363]...
If anything having a dedicated thread for a "specific reason" is much easier to find, and less time consuming, than searching for a possible answer in the comments of another thread on a somewhat related post. He's making the search more efficient since you mention "wasting time", you're the one wasting time *****ing on a usefull post lol.
You're assuming installing TWRP is for the purpose of returning to stock but there's a ton of other reasons someone could want to install TWRP and then magisk... Also there's other ways to return to stock besides TWRP soooo [emoji2375] i guess that's a waste of time too...
What are we doing SMH [emoji23][emoji24][emoji88]
Sent from my SM-G975U1 using Tapatalk
juggz14301 said:
[emoji848]Maybe it's you who should re-read. The first post doesn't mention anything about returning to stock. He's trying to install magisk on a BETA, which is the polar opposite of returning to stock [emoji2375][emoji2363]...
If anything having a dedicated thread for a "specific reason" is much easier to find, and less time consuming, than searching for a possible answer in the comments of another thread on a somewhat related post. He's making the search more efficient since you mention "wasting time", you're the one wasting time *****ing on a usefull post lol.
You're assuming installing TWRP is for the purpose of returning to stock but there's a ton of other reasons someone could want to install TWRP and then magisk... Also there's other ways to return to stock besides TWRP soooo [emoji2375] i guess that's a waste of time too...
What are we doing SMH [emoji23][emoji24][emoji88]
Click to expand...
Click to collapse
Who is talking about returning to stock? He's talking about installing TWRP and magisk on Q beta.
Good Morning/Afternoon/Evening/Night. I have compiled an experimental Sky Hawk Recovery Project for the Tab S7+ 5G by literally taking @ianmacd 's TWRP tree and modding it. I did this because TWRP looks a bit boring to me and I personally like SHRP. Also fun fact, I do not own this device but I just want to give back to the community I take and use everything from. Here you will find the download links and instructions:
But before that, here's a warning: I AM A NEWBIE and there is no denying that. So take and use whatever I say with a kilogram of salt. And please please correct me wherever I made a mistake because, you know, I've only started android development literally 2 months ago.
So here is the link: Mega
[Might not boot, might soft-brick your device, I honestly do not know what will happen. So have ODIN and ian's recovery image in tar form handy. Also this is for testing purposes, not "un"official release. And be sure to leave feedback if you tested this.]
Bugs will be the same as ianmacd's one (if it even works)
Installation is as easy as flashing the zip in your TWRP recovery [you should have encryption and all the scary things disabled by following ian's guide HERE
Advantages: I personally think it looks better than TWRP. Also I will add the flashlight feature after I see that the build boots up fine.
[The reason that I am trying to build for tablets first is because I have a problem with tablets. I've built SO MANY Tab S3 recoveries but none of them boot AT ALL. But the 2016 phone I had lying around booted up first try with my self-made device tree].
Mega thanks to,
@ianmacd (because I didn't have to waste a day making a device tree from scratch) [and because I am scared of encrypted devices]
and Ian's device tree: https://github.com/ianmacd/twrp_gts7xl
Stay safe and happy flashing!
Thanks might give it a try at the weekend.
Huntyz said:
Thanks might give it a try at the weekend.
Click to expand...
Click to collapse
Thanks a lot man! Also remember to follow ian's guide fully cuz your tab'll suffer if you don't.
has anybody tried this?
---------- Post added at 12:36 PM ---------- Previous post was at 12:30 PM ----------
just flash. doesnt boot. goes straight to download mode and says,
partition vbmeta
Reason vbmeta: error verifiying vbmeta image: and a code here
CVLover said:
has anybody tried this?
---------- Post added at 12:36 PM ---------- Previous post was at 12:30 PM ----------
just flash. doesnt boot. goes straight to download mode and says,
partition vbmeta
Reason vbmeta: error verifiying vbmeta image: and a code here
Click to expand...
Click to collapse
cuz u havent properly disabled vbmeta.. as post right above urs says, follow twrp guide to the T or ull have problems
Does it work? Let us know. Thank you
I also tried and no success.Just to mention that I had properly disabled vbmeta and it seems problem is somewhere else.
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.
Context:
- using crDroid latest (from late aug. I guess)
- patched boot.img with magisk and pushed it
- everytime I install smali patcher module I end up in bootloops afterwards.
I will obviously look into the smali patcher thread (here on xda), but here's my question:
Question:
How do I get access to the filesystem with TWRP, decrypt it outside or inside, as long as I can remove the offending module for instance?
I read many different threads but it's all bit and pieces here and there and kinda hard to follow, not applicable, talks about different versions, mixes a11 and 12 sometimes...
Anyways, if somebody can point me to some relevant documentation, let me know, I'll read. I have no restriction in terms of erasing the phone over and over, I just need access once a day to SMS in order to log into the office VPN.
well, whatever with getting access to filesystem. Smali patcher hasnt been updated for a few months, dev is apparently not online anymore (hope he's ok), and it doesnt work with A12. Guess I'll have to just wait for that one, stop being an idiot and toy with things I dont master for a while.
But I'd still be happy to educate myself further if somebody replies.
In the meantime... thanks everybody!
There was "unofficial" twrp (also orangefox) which has support decrypt, tou sold take a look around to find it (it was actually from the same dev)
There is a functional TWRP with decryption for Android 12, works well for me. Please ask if i should share it here.
My question is: does anyone know if there is the same functionality ( decryption ) also availabe for Android13 ?#
Thx
hanichl said:
There is a functional TWRP with decryption for Android 12, works well for me. Please ask if i should share it here.
My question is: does anyone know if there is the same functionality ( decryption ) also availabe for Android13 ?#
Thx
Click to expand...
Click to collapse
Ok so I need to find that unofficial one then, or try orangefox. Well. Right now I confirmed that smali patcher doesnt work with 12 anyways, so I'm not gonna bother much but it's good to know. Thanks!
liberteus said:
Ok so I need to find that unofficial one then, or try orangefox. Well. Right now I confirmed that smali patcher doesnt work with 12 anyways, so I'm not gonna bother much but it's good to know. Thanks!
Click to expand...
Click to collapse
See my attachment the posts before, works perfect for me !
hanichl said:
See my attachment the posts before, works perfect for me !
Click to expand...
Click to collapse
Smali patcher works for you, or the recovery decrypts filesystem?
Maybe i misunderstood you earlier. Going to read the thread once more. Thanks!
liberteus said:
Smali patcher works for you, or the recovery decrypts filesystem?
Maybe i misunderstood you earlier. Going to read the thread once more. Thanks!
Click to expand...
Click to collapse
Relying to myself, answered my own Euston by reading your post earlier. Will try it tomorrow! Thanks a lot!
liberteus said:
Smali patcher works for you, or the recovery decrypts filesystem?
Maybe i misunderstood you earlier. Going to read the thread once more. Thanks!
Click to expand...
Click to collapse
when you have installed this twrp, and you boot to recovery ( here: twrp ), you will be asked for your PIN , pass it and your data partition will be accessable from twrp recovery.
So twrp decrypts the partition !
Couldnt wait for tomorrow, had to test it now, flashed it after testing.
Works flawlessly. Not everything works the way I'd like it to work on my new phone, but it's good enough.
Not posting much on xda, but whenever I did, kind ppl like you Hanichi always replied and pointed me in the right direction, or like you did provided just the right file I needed. Dang that place is sweet (pun intended).
Thanks again!