Related
Hi!. I recently received my new Moto E5 XT1944-1 and i wanted to root, unlock bootloader and everything. For that reason i enter this forum and get the TWRP recovery from de Moto E5 (James), but i dont know that the James (5,2 inch screen) is not the same that my Moto E5 (5,7 inch screen), and now the recovery seems to be corrupt and cant enter, only enter on fastboot mode. I need to say that the smartphone boots normally, but i fear the day that i need to make a full wipe and cant enter recovery. What can i do to reflash the original recovery?. Thanks to all help given.
Edit: I need to say that the bootloader is successfully unlocked, but still the problem with the recovery.
intherior said:
Hi!. I recently received my new Moto E5 XT1944-1 and i wanted to root, unlock bootloader and everything. For that reason i enter this forum and get the TWRP recovery from de Moto E5 (James), but i dont know that the James (5,2 inch screen) is not the same that my Moto E5 (5,7 inch screen), and now the recovery seems to be corrupt and cant enter, only enter on fastboot mode. I need to say that the smartphone boots normally, but i fear the day that i need to make a full wipe and cant enter recovery. What can i do to reflash the original recovery?. Thanks to all help given.
Edit: I need to say that the bootloader is successfully unlocked, but still the problem with the recovery.
Click to expand...
Click to collapse
Because the Moto E5 series is so young in terms of both its recent release and its limited support within the Android community, finding factory firmware packages is not easy right now. Typically, in your situation, simply extracting a stock recovery image from a firmware package and flashing it in fastboot would be your best remedy by far. But, if you have corrupted your recovery partition and are unable to locate a stock image, I would recommend first that you ask some members and devs on the furum to dump a stock recovery image that you could flash to fix your issue. Second, if you are rooted, make an immediate dump of your /system, /boot, /oem and /vendor partitions. That way, if your OS does decide not to boot, you can restore your partition dumps via fastboot (as long as your bootloader is unlocked). If you are not rooted and are thus unable to dump your key partitions, I'd advise to just be really careful in terms of modding or tweaking your stock OS. Firmware packages will likely be available by September, maybe sooner. Until then, reach out and ask some members & devs if they can provide you with a stock recovery image. Good luck...
First, thanks for your fast reply. My phone isn't rooted yet, i stop doing the guide of the James version because i think i do it worst. I can test the Kingroot app o whetever it names, but i prefer to wait and stop installing apps (only the basic: Telegram, Youtube, etc for daily use). I dont know who Devs or Members have this system. But i will stay reading this section of forum everyday to stay update of the news. Thanks for all pal!.
Edit: Sorry for my bad english, i'm spanish and dont know so much
intherior said:
First, thanks for your fast reply. My phone isn't rooted yet, i stop doing the guide of the James version because i think i do it worst. I can test the Kingroot app o whetever it names, but i prefer to wait and stop installing apps (only the basic: Telegram, Youtube, etc for daily use). I dont know who Devs or Members have this system. But i will stay reading this section of forum everyday to stay update of the news. Thanks for all pal!.
Edit: Sorry for my bad english, i'm spanish and dont know so much
Click to expand...
Click to collapse
It's ok friend. I understand you good. I am currently developing for the James xt1921-5 (Boost/Virgin/Sprint) variant and, as such, I am keeping a close watch for factory firmware to be released for the James. I will contact you as soon as I can confirm a firmware source for your particular model (xt1944-1). Currently, there are only paid subscription-type repositories which offer firmware downloads online. I don't recommend or support sources that charge a fee for firmware. But, it won't be long. September at the latest, possibly sooner.
MotoJunkie01 said:
It's ok friend. I understand you good. I am currently developing for the James xt1921-5 (Boost/Virgin/Sprint) variant and, as such, I am keeping a close watch for factory firmware to be released for the James. I will contact you as soon as I can confirm a firmware source for your particular model (xt1944-1). Currently, there are only paid subscription-type repositories which offer firmware downloads online. I don't recommend or support sources that charge a fee for firmware. But, it won't be long. September at the latest, possibly sooner.
Click to expand...
Click to collapse
Thank you so much!. I will stay update to any news here. I know that this model is so soon, my network provider offers me this, and cause i allways use Motorola (Moto E1, Moto G, Moto G2014), then i accept thinking that the scene was more advanced. My surprise when i see that this version was recently released...
Well, then it's time to wait to see how the scene grow up.
Regards pal!.
intherior said:
Thank you so much!. I will stay update to any news here. I know that this model is so soon, my network provider offers me this, and cause i allways use Motorola (Moto E1, Moto G, Moto G2014), then i accept thinking that the scene was more advanced. My surprise when i see that this version was recently released...
Well, then it's time to wait to see how the scene grow up.
Regards pal!.
Click to expand...
Click to collapse
Great news @intherior -- Motorola Mobility has leaked some factory firmware packages for yours and a few other variants. I'll be posting a thread with download links by tomorrow evening. In fact, here is you a link to the specific file you need -- the stock recovery image for the xt1944-1. You can flash this via fastboot mode by:
fastboot flash recovery recovery.img
Link: https://drive.google.com/file/d/17sgV8t6jYgahml6Huv3Hq2IgygqJZnsH/view?usp=drivesdk
Yeah!!! That's really very good news!. I'm not at home now, but this night i Will download and comment if it fix my problem. Thank u so much bro!
Edit: One picture is better that thousand words xD
Thank u bro!. Finally was fixed with the recovery u posted!. Now i take care from do something stupid. I will wait to a stable and probed version of TWRP to finally get my Moto E5 Xt1944-1 rooted. But for now i will take it easy.
Regards my friend! :fingers-crossed:
intherior said:
Yeah!!! That's really very good news!. I'm not at home now, but this night i Will download and comment if it fix my problem. Thank u so much bro!
Edit: One picture is better that thousand words xD
Thank u bro!. Finally was fixed with the recovery u posted!. Now i take care from do something stupid. I will wait to a stable and probed version of TWRP to finally get my Moto E5 Xt1944-1 rooted. But for now i will take it easy.
Regards my friend! :fingers-crossed:
Click to expand...
Click to collapse
Very glad the stock recovery worked for you. I have an entire stock firmware package for your device if you ever need it to restore your device to factory state. Just let me know and I'll upload and post a link. Cheers...
Sure bro!. Will be good to keep that firmware safe if I have any problem. Give me the download link when you have time. Thanks again!
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.
Follow the following at your own risk! I am not responsible for any mishaps with your devices. This will NOT obviously work for Verizon, AT&T, and Cricket phones.
Okay, So I've been asking questions, playing, unpacking, and repacking, trying tools, etc. And I got a very experimental port of TWRP happening. VERY EXPERIMENTAL.
THINGS TO KNOW AFTER THE EXCITEMENT DIES DOWN:
For starters, yes THIS DOES BOOT TO TWRP! I'm quite proud about that. This is my first ever port of anything like this. I mostly just fiddle with making bootable stock roms, and not too much since Android 9 and this new nuts file system. Anyway, I set out to try and get a TWRP together for this phone and that happened, so I'm proud of myself I didn't get discouraged.
Having said that, it has ZERO touchscreen functionality. From my research this was also an initial problem for the peeps over at the Moto One 5G Plus variant (Nairo) before they worked out the bugs. Hopefully they will take mercy on us and come give some feedback.
Also, this is a port. I used @Hovatek's Qualcomm tool to accomplish this since unpacking, repacking, copying and pasting a port from Nairo in the Carliv Image Kitchen or Android Image Kitchen just soft bricked my phone. It also doesn't help the traditional porting methods prior to Android 9 don't work anymore. They came up with a great tool, Gawd Bless Em'.
Should you try this for hoots and giggles just know you will have to hard reset. Android will force a factory reset because of the vbmeta flashing, and your phone will be factory brand spanking new. Backup your contacts, pics, messages, and anything else you want to keep just in case.
I'm not going to put detailed instructions on this just yet since it's experimental - this is really for folks that know what they're doing with their phone.
Notes:
You must have the bootloader unlocked and be rooted with Magisk for this to fly. Can't say how this would work on locked bootloaders without root so proceed cautiously on that.
1. Flash VBmeta first. The VBMeta is a blank file and that's to make sure DM-Verity isn't acting up (which as of now I'm 50% certain it is and that's why I had to go ahead and factory reset). The commands to disbale dm-verity didn't work for me. If anybody knows how to get that shut off please add to the discussion.
2. I didn't replace my original recovery. I just did fastboot boot recovery image to see if it would load. I wouldn't advise flashing it to replace the current recovery as it might seriously bootloop.
If anybody wants to try and work on this with me (or take over since I'm a hobbyist at best) then by all means share. But at least now we're getting somewhere, slowly but surely.
Today was a good day in hacking Android 10 on this phone.
Articul8Madness said:
Follow the following at your own risk! I am not responsible for any mishaps with your devices. This will NOT obviously work for Verizon, AT&T, and Cricket phones.
Okay, So I've been asking questions, playing, unpacking, and repacking, trying tools, etc. And I got a very experimental port of TWRP happening. VERY EXPERIMENTAL.
THINGS TO KNOW AFTER THE EXCITEMENT DIES DOWN:
For starters, yes THIS DOES BOOT TO TWRP! I'm quite proud about that. This is my first ever port of anything like this. I mostly just fiddle with making bootable stock roms, and not too much since Android 9 and this new nuts file system. Anyway, I set out to try and get a TWRP together for this phone and that happened, so I'm proud of myself I didn't get discouraged.
Having said that, it has ZERO touchscreen functionality. From my research this was also an initial problem for the peeps over at the Moto One 5G Plus variant (Nairo) before they worked out the bugs. Hopefully they will take mercy on us and come give some feedback.
Also, this is a port. I used @Hovatek's Qualcomm tool to accomplish this since unpacking, repacking, copying and pasting a port from Nairo in the Carliv Image Kitchen or Android Image Kitchen just soft bricked my phone. It also doesn't help the traditional porting methods prior to Android 9 don't work anymore. They came up with a great tool, Gawd Bless Em'.
Should you try this for hoots and giggles just know you will have to hard reset. Android will force a factory reset because of the vbmeta flashing, and your phone will be factory brand spanking new. Backup your contacts, pics, messages, and anything else you want to keep just in case.
I'm not going to put detailed instructions on this just yet since it's experimental - this is really for folks that know what they're doing with their phone.
Notes:
You must have the bootloader unlocked and be rooted with Magisk for this to fly. Can't say how this would work on locked bootloaders without root so proceed cautiously on that.
1. Flash VBmeta first. The VBMeta is a blank file and that's to make sure DM-Verity isn't acting up (which as of now I'm 50% certain it is and that's why I had to go ahead and factory reset). The commands to disbale dm-verity didn't work for me. If anybody knows how to get that shut off please add to the discussion.
2. I didn't replace my original recovery. I just did fastboot boot recovery image to see if it would load. I wouldn't advise flashing it to replace the current recovery as it might seriously bootloop.
If anybody wants to try and work on this with me (or take over since I'm a hobbyist at best) then by all means share. But at least now we're getting somewhere, slowly but surely.
Today was a good day in hacking Android 10 on this phone.
Click to expand...
Click to collapse
Hi. I appreciate a lot your efforts. I know the feeling when you progress with stuff like this. I'm sorry I have no time in these months to assist. Anyway, I hope you'll manage to go forward with this. Keep up with the good work.
useless789 said:
Hi. I appreciate a lot your efforts. I know the feeling when you progress with stuff like this. I'm sorry I have no time in these months to assist. Anyway, I hope you'll manage to go forward with this. Keep up with the good work.
Click to expand...
Click to collapse
CAn you at least tell me how to port a TWRP on Android 10? Can't find any useful information with the new filetypes.
Articul8Madness said:
CAn you at least tell me how to port a TWRP on Android 10? Can't find any useful information with the new filetypes.
Click to expand...
Click to collapse
I'm not sure what you mean by filetypes. Do you mean the A/B partitions (and the fact that there's no separate recovery partition) or something else?
Articul8Madness said:
Follow the following at your own risk! I am not responsible for any mishaps with your devices. This will NOT obviously work for Verizon, AT&T, and Cricket phones.
Okay, So I've been asking questions, playing, unpacking, and repacking, trying tools, etc. And I got a very experimental port of TWRP happening. VERY EXPERIMENTAL.
THINGS TO KNOW AFTER THE EXCITEMENT DIES DOWN:
For starters, yes THIS DOES BOOT TO TWRP! I'm quite proud about that. This is my first ever port of anything like this. I mostly just fiddle with making bootable stock roms, and not too much since Android 9 and this new nuts file system. Anyway, I set out to try and get a TWRP together for this phone and that happened, so I'm proud of myself I didn't get discouraged.
Having said that, it has ZERO touchscreen functionality. From my research this was also an initial problem for the peeps over at the Moto One 5G Plus variant (Nairo) before they worked out the bugs. Hopefully they will take mercy on us and come give some feedback.
Also, this is a port. I used @Hovatek's Qualcomm tool to accomplish this since unpacking, repacking, copying and pasting a port from Nairo in the Carliv Image Kitchen or Android Image Kitchen just soft bricked my phone. It also doesn't help the traditional porting methods prior to Android 9 don't work anymore. They came up with a great tool, Gawd Bless Em'.
Should you try this for hoots and giggles just know you will have to hard reset. Android will force a factory reset because of the vbmeta flashing, and your phone will be factory brand spanking new. Backup your contacts, pics, messages, and anything else you want to keep just in case.
I'm not going to put detailed instructions on this just yet since it's experimental - this is really for folks that know what they're doing with their phone.
Notes:
You must have the bootloader unlocked and be rooted with Magisk for this to fly. Can't say how this would work on locked bootloaders without root so proceed cautiously on that.
1. Flash VBmeta first. The VBMeta is a blank file and that's to make sure DM-Verity isn't acting up (which as of now I'm 50% certain it is and that's why I had to go ahead and factory reset). The commands to disbale dm-verity didn't work for me. If anybody knows how to get that shut off please add to the discussion.
2. I didn't replace my original recovery. I just did fastboot boot recovery image to see if it would load. I wouldn't advise flashing it to replace the current recovery as it might seriously bootloop.
If anybody wants to try and work on this with me (or take over since I'm a hobbyist at best) then by all means share. But at least now we're getting somewhere, slowly but surely.
Today was a good day in hacking Android 10 on this phone.
Click to expand...
Click to collapse
This is tremendously amazing work. TWRP would be a killer feature with the 5G Ace. Couple that with Lenovo having released the source code, and this forum may get popping again!
useless789 said:
I'm not sure what you mean by filetypes. Do you mean the A/B partitions (and the fact that there's no separate recovery partition) or something else?
Click to expand...
Click to collapse
I was referring to the super_sparsechunk type files that when you look at their "filetype" it has 0 image by its name if its super_sparsechunk.0, 1 if its super_sparsechunk.1 and the like. This is different than the old basic img files that read .img. This is where the learning curve for me kicks in.
Articul8Madness said:
I was referring to the super_sparsechunk type files that when you look at their "filetype" it has 0 image by its name if its super_sparsechunk.0, 1 if its super_sparsechunk.1 and the like. This is different than the old basic img files that read .img. This is where the learning curve for me kicks in.
Click to expand...
Click to collapse
I see. Thanks for the explanation. I'm not sure if this could help, but a quick search on google led me to this (a bit old) video:
I'm really busy until the end of the month so I can't really dedicate my time to this stuff though I would love to.
useless789 said:
I see. Thanks for the explanation. I'm not sure if this could help, but a quick search on google led me to this (a bit old) video:
I'm really busy until the end of the month so I can't really dedicate my time to this stuff though I would love to.
Click to expand...
Click to collapse
I see you already tried this here: Post in thread '[Tool] SparseConverter v1.0.1' https://forum.xda-developers.com/t/tool-sparseconverter-v1-0-1.2749797/post-84767377
If I manage I'll take a look at this asap.
useless789 said:
I see you already tried this here: Post in thread '[Tool] SparseConverter v1.0.1' https://forum.xda-developers.com/t/tool-sparseconverter-v1-0-1.2749797/post-84767377
If I manage I'll take a look at this asap.
Click to expand...
Click to collapse
Any and all contributing help is appreciated!
@Articul8Madness I managed to combine the sparse chunk files into a raw image file. I also managed to mount the image, but only in read-only mode. I'll post with updates as I get passed this obstacle.
Seems the US version of this phone isn't popular enough for dev support...oh well I have R/W access so I was able to delete system app bloatware and I have xposed installed. Stock Reteu firmware is working perfectly on Metro...good luck everybody.. I'm looking for a new 5G phone..
Unfortunately, there are no developers here.
All we can produce is a ported twrp where the touchscreen does not work.
The touchscreen does not work due to problems with the porting tool and the smartphone.
I heard that if you build it from source yourself, it will work.
But I can't find any tutorials for android 10+ and I don't even know what files I need.
PEACH-PIT said:
Unfortunately, there are no developers here.
All we can produce is a ported twrp where the touchscreen does not work.
The touchscreen does not work due to problems with the porting tool and the smartphone.
I heard that if you build it from source yourself, it will work.
But I can't find any tutorials for android 10+ and I don't even know what files I need.
Click to expand...
Click to collapse
I posted the source code. The guys over on the Moto One 5G know what tools you need. I was using Carliv's kitchen to build but I've never built before - they had the same problem as us with the touchscreen and had to make modules. That counts me out because that's above my paygrade, lol.
Articul8Madness said:
I posted the source code. The guys over on the Moto One 5G know what tools you need. I was using Carliv's kitchen to build but I've never built before - they had the same problem as us with the touchscreen and had to make modules. That counts me out because that's above my paygrade, lol.
Click to expand...
Click to collapse
Not entirely sure what you mean. If your doing some kind of frankenstein recovery, I'm sure you just failed to copy some module or firmware, obviously the ts works in the official software.
1.) Find out what touchscreen chipset your device uses (you can use kernel log or system info apps or whatever)
2.) Determine which kernel module supports it (all modules built will be in your kernel config)
3.) modprobe that module from adb in your recovery. If it doesn't just work, you will receive some error on the command line or dmesg that you can use to fix it. Could need a configuration file or something, idk. It's likely an opensource module that you can read through and I bet you can find specific info online since your not the first to hit this issue.
If your wondering how to build the kernel, I can help a little, but it's incomplete:
Kernel source:
GitHub - MotorolaMobilityLLC/kernel-msm at MMI-QZK30.Q4-40-52
Linux Kernel for Motorola devices using MSM-based chipset - GitHub - MotorolaMobilityLLC/kernel-msm at MMI-QZK30.Q4-40-52
github.com
Build instructions:
readme/MMI-QPN30.33-40.txt at master · MotorolaMobilityLLC/readme
Readme's for motorola builds. Contribute to MotorolaMobilityLLC/readme development by creating an account on GitHub.
github.com
Snapdragon LLVM Toolchain:
snapdragon-llvm-8.0.6-linux64.tar.gz
drive.google.com
Retail config is on your device:
/proc/config.gz
The instructions don't cover the qcom toolchain, you just take the files here:
snapdragon-llvm-8.0.6-linux64.tar.gz/toolchains/llvm-Snapdragon_LLVM_for_Android_8.0/prebuilt/linux-x86_64/*
and place them here:
$my_top_dir/vendor/qcom/proprietary/llvm-arm-toolchain-ship/8.0/
When building, skip the cat command, and place your config manually to $kernel_out_dir/.config
The step I haven't done is build a device tree. It's not that it's too difficult, I just haven't put in the time required to do it. It's not strictly necessary to achieve for my goals since I only wanted modules and know how to patch the kernel to be able to use them.
https://github.com/moto-sm7250/android_device_motorola_kiev/tree/android-10
Will this not work?
I do not know how to build it.
fddm said:
Not entirely sure what you mean. If your doing some kind of frankenstein recovery, I'm sure you just failed to copy some module or firmware, obviously the ts works in the official software.
1.) Find out what touchscreen chipset your device uses (you can use kernel log or system info apps or whatever)
2.) Determine which kernel module supports it (all modules built will be in your kernel config)
3.) modprobe that module from adb in your recovery. If it doesn't just work, you will receive some error on the command line or dmesg that you can use to fix it. Could need a configuration file or something, idk. It's likely an opensource module that you can read through and I bet you can find specific info online since your not the first to hit this issue.
If your wondering how to build the kernel, I can help a little, but it's incomplete:
Kernel source:
GitHub - MotorolaMobilityLLC/kernel-msm at MMI-QZK30.Q4-40-52
Linux Kernel for Motorola devices using MSM-based chipset - GitHub - MotorolaMobilityLLC/kernel-msm at MMI-QZK30.Q4-40-52
github.com
Build instructions:
readme/MMI-QPN30.33-40.txt at master · MotorolaMobilityLLC/readme
Readme's for motorola builds. Contribute to MotorolaMobilityLLC/readme development by creating an account on GitHub.
github.com
Snapdragon LLVM Toolchain:
snapdragon-llvm-8.0.6-linux64.tar.gz
drive.google.com
Retail config is on your device:
/proc/config.gz
The instructions don't cover the qcom toolchain, you just take the files here:
snapdragon-llvm-8.0.6-linux64.tar.gz/toolchains/llvm-Snapdragon_LLVM_for_Android_8.0/prebuilt/linux-x86_64/*
and place them here:
$my_top_dir/vendor/qcom/proprietary/llvm-arm-toolchain-ship/8.0/
When building, skip the cat command, and place your config manually to $kernel_out_dir/.config
The step I haven't done is build a device tree. It's not that it's too difficult, I just haven't put in the time required to do it. It's not strictly necessary to achieve for my goals since I only wanted modules and know how to patch the kernel to be able to use them.
Click to expand...
Click to collapse
This recovery I built in this thread I used Hovatek's tool to do. I have never built a recovery and I was hoping if someone got the ball rolling we could get a dev to jump in. That hasn't happened.
The guys with the other variant of this phone said they had to create modules. Go to the Moto One 5G forums and see the thread. They had the same problems too, but they had more dev support than we do.
I have never built a TWRP, let alone from source, so half of what you sent I have no idea what it is or how to decompile it (yet).
I have posted the entire Kernel Motorola released its in the other thread. The Device Tree is official and out on github.
Guys, I'm a developer, just that I'm still really busy. I'm following your posts and have looked into some of the stuff, just I'm proceeding slowly due to lack of time. I'll post as soon as I have something working.
useless789 said:
Guys, I'm a developer, just that I'm still really busy. I'm following your posts and have looked into some of the stuff, just I'm proceeding slowly due to lack of time. I'll post as soon as I have something working.
Click to expand...
Click to collapse
Is this the correct twrp for this phone?
Root Motorola One 5G Ace XT2113 and Install TWRP Recovery 3.5.0
Easy tutorial to Root Motorola One 5G Ace XT2113-2, XT2113-3, XT2113-5 easily. For rooting, you have to flash TWRP Recovery 3.5.0 on Android 10 through guide.
www.androidweblog.com
Later guys, keep up the good work
Tomspector said:
Is this the correct twrp for this phone?
Root Motorola One 5G Ace XT2113 and Install TWRP Recovery 3.5.0
Easy tutorial to Root Motorola One 5G Ace XT2113-2, XT2113-3, XT2113-5 easily. For rooting, you have to flash TWRP Recovery 3.5.0 on Android 10 through guide.
www.androidweblog.com
Later guys, keep up the good work
Click to expand...
Click to collapse
This is a fake. It's non-functional garbage.
There is no harm in trying it, unless you flash it, but there is no need to try it.
useless789 said:
Guys, I'm a developer, just that I'm still really busy. I'm following your posts and have looked into some of the stuff, just I'm proceeding slowly due to lack of time. I'll post as soon as I have something working.
Click to expand...
Click to collapse
I have a request to the developers.
GitHub - moto-sm7250/android_device_motorola_kiev at android-10
DT for Moto G 5G / One 5G Ace. Contribute to moto-sm7250/android_device_motorola_kiev development by creating an account on GitHub.
github.com
Can you please build this twrp?
I'm trying to build it.
But I don't know how to solve the error.
I don't think I can build it.
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.
This might be completely unnecessary (mods feel free to remove if it is), but I see a LOT of misinformation regarding GSI ROMs and the G8. So. Here's a guide/FAQ for those wondering if/what is possible:
***I'M NOT RESPONSIBLE IF YOU BRICK YOUR PHONE, LOSE YOUR DATA, OR OTHERWISE DAMAGE YOUR DEVICE. IF YOU CHOOSE TO FOLLOW THIS GUIDE, THE FATE OF YOUR DEVICE IS IN YOUR HANDS, NOT MINE, NOT YOUR MOTHER'S, NOT ANYONE OTHER THAN YOUR OWN***
Prerequisites (yes, these are all NECESSARY. If you don't know how to unlock your bootloader or use fastboot, there are other guides here. Go find one.)
Unlocked bootloader (and the V50 engineering abl files as well as stock, plenty of guides here with download links)
QFIL/QPST
Basic Fastboot, ADB knowledge
BACKUP. I mean ALL YOUR DATA kinda backup. This WILL wipe your phone, do NOT come crying to me if you lose the last picture of your favorite sock. Not my fault.
GSI for Treble device (ab)
GApps (optional, but recommended)
Instructions to Flash via Fastboot
WIPE YOUR PHONE
Yeah, completely factory reset that sucker. Doesn't matter if it's through recovery, settings, or adb, just bite the bullet and restore factory settings. You can technicially flash without doing this first, but you'll still have to wipe it before any flashed ROM will run. Sorry.
Boot to EDL (NOT download, your screen should be black, dev manager should show QD Loader 9008 COMx)
Use QFIL to flash engineering abl file to both a and b slots - yes, all this work just for fastboot.
Reboot to fastboot!
I just unplug my phone, use power + vol- to shut phone off and then reconnect while holding vol-, but you do you.
In case you don't remember, your touch screen WILL NOT WORK during this time, even if you fully boot to system! Completely fine and normal, means you're on the right track!
Fastboot Devices should yield "LG850UM", also good!
Open cmd prompt from platform_tools, copy path to desired GSI while you're in there
Run these commands line-by-line:
fastboot format system
fastboot flash system *Path_To_GSI.img*
This is where I usually repeat the 2 commands and attempt reboot while I still have fastboot, whether or not it changes anything I have no idea, but it's never given me problems so why fix it if it ain't broke?
fastboot flash abl_a abl_STOCK.bin
fastboot flash abl_b abl_STOCK.bin
fastboot reboot
Ta-Da! Your shiny new ROM should be up and running. Use TWRP or any kernel manager (I like SmartPak) to flash TWRP, GApps, blah blah blah.
FAQ/Troubleshooting
Touchscreen still not working? Go back to EDL and load the stock abl bin files through QFIL, then reboot as normal.
You will likely be asked to input a password upon successful reboot, just enter your PIN/password, whatever you used to unlock your phone pre-flash
The cool things like QuadDAC and LG-specific tweaks will probably not work. Weigh your options before flashing.
Magisk comes pre-installed with most GSI's, just follow the prompts and you'll be just fine.
Don't want GApps? Just sideload desired apk's via ADB, or use the browser to search for them.
Can't I just use TWRP and make this whole process a lot simpler? Yep. But some of us don't have working TWRP or prefer using fastboot commands. This is for those people, don't hate.
Which ROMs work?? Not sure, haven't tried them all. Currently running HavocOS found in Treble GSI forum on here.
Help! I broke my phone! No, you probably didn't. It's advisable that you know how to emergency restore via LGUP prior to starting this process though. Please be specific as to what part of this "broke" your phone and why exactly your phone is "broken" if you're going to ask for help- "bricked device" has never helped anyone.
Rebooting is your best friend in this process, especially during the first boot. If anything starts to hang up or act funny, just give the phone a minute to catch its breath and, worst case, turn it off and back on again
As previously stated, this is probably pointless, but given all I see on the G8 forum is "no custom ROM" or "why bother trying to *insert idea here*", I figured it might help some folks out. I'm sure I left a few things out, feel free to correct or provide input as necessary.
Works on LM-G820QM5?, I have bootloader unlocked
Elihu_GmG said:
Works on LM-G820QM5?, I have bootloader unlocked
Click to expand...
Click to collapse
Yep, it's basically the unlocking/root process only you're formatting/flashing the "system" partition instead of "boot_a/b"
Great info, thnx for the write up. But what about the totc.cfg file? My understanding is no G8 is going to boot if there's a mis-match between that file and the hardware indication of what variant the phone is?
Sorry if my understanding is misguided, new to the G8 (and all it's idiosyncrasies).
AsItLies said:
Great info, thnx for the write up. But what about the totc.cfg file? My understanding is no G8 is going to boot if there's a mis-match between that file and the hardware indication of what variant the phone is?
Sorry if my understanding is misguided, new to the G8 (and all it's idiosyncrasies).
Click to expand...
Click to collapse
In this case there is no tot file, no recovery, laf, or the like. GSI's are generic system images that are capable of being flashed to most Treble-Enabled Androids from Oreo on up. You do lose some of the device specific things (hence, generic), but they're a great alternative if you're like us and stuck with next to no custom anything built for your device. There's a whole forum for them on here, I highly suggest checking it out- it's a pretty awesome option to have.
SirOlive said:
In this case there is no tot file, no recovery, laf, or the like. GSI's are generic system images that are capable of being flashed to most Treble-Enabled Androids from Oreo on up. You do lose some of the device specific things (hence, generic), but they're a great alternative if you're like us and stuck with next to no custom anything built for your device. There's a whole forum for them on here, I highly suggest checking it out- it's a pretty awesome option to have.
Click to expand...
Click to collapse
Great, thnx, sorry for being a jerk but, this does work on a G8? Tested and proven? I ask because it's my understanding that without a match between the hardware encoded variant of the device and what's in the totc file, it won't boot.
you say there is no totc? then how does the hardware encoding get verified? See, that's why there are no custom roms. LG did this to keep people from crossflashing and it killed rom development.
Hey, if I'm wrong, feel free to point that out. But as far as I've discovered so far, a GSI doesn't get a free pass to bypass this mess LG has created with this mis-match hw / totc file.
cheers
AsItLies said:
Great, thnx, sorry for being a jerk but, this does work on a G8? Tested and proven? I ask because it's my understanding that without a match between the hardware encoded variant of the device and what's in the totc file, it won't boot.
you say there is no totc? then how does the hardware encoding get verified? See, that's why there are no custom roms. LG did this to keep people from crossflashing and it killed rom development.
Hey, if I'm wrong, feel free to point that out. But as far as I've discovered so far, a GSI doesn't get a free pass to bypass this mess LG has created with this mis-match hw / totc file.
cheers
Click to expand...
Click to collapse
Sorry for being short, but a simple Google search would back up everything I've written. I wouldn't have written this up if it didn't work, or if it was just a theory... I wouldn't have said that my Verizon G8 is running Havoc if it didn't work. I was able to flash with zero problems. With the Treble Project, Google has mandated that Android devices boxed with 11+ (possibly 10?) be capable of not only recognizing, but running GSIs as to assist developers in testing apps and builds in varying versions of Android as quickly, easily, and simply as possible. This means that not only can one download and flash Android releases downloaded directly from Google, but devs can use the source code to create versions of their ROMs that will apply to a wide array of models that would never have seen development otherwise. Because these are "generic" images and are based upon system architecture type alone- not a particular make/model- there are sometimes things overlooked. For instance, in our case, the audio processing and LG's camera software are not present. These are decently made up for by the presence of flashable mods, though, and the phone remains fully functional, Google Play Certified (if desired), and as reliable as the ROM you choose to flash.
Basically, Google>LG. LG wants to use the Android platform, they must abide by Google's rules. They need not go into great detail, nor allow their devices to be changed to something fundamentally non-LG, nor divulge any potentially propitiatory subject matter (once again, "generic"), but they must allow the device to be open to a certain level of customization as designated by Google.
Is it ideal? Not if you're lucky enough to have ROMs tailored for your specific phone. But for those left behind- like the G8- it's a fantastic workaround that does, in fact, work. As I'm sure you're still skeptical, I will add screenshots tomorrow to prove the validity of this seemingly ludicrous claim. In the meantime, please do some research on the topic- or better yet, give it a shot- there's gotta be a guide around here somewhere.
It works
Of [email protected]*$king course it works. I’ve flashed it to my sprint v50 (v450pm). Had the same QuadDac problem though. Couldn’t get a sound out of it. I mean no sound of any kind. Also couldn’t get it to activate on Google Fi. Will be watching to see if someone solves the Sound problem. We could just skip on past A11.
hooutoo said:
Of [email protected]*$king course it works. I’ve flashed it to my sprint v50 (v450pm). Had the same QuadDac problem though. Couldn’t get a sound out of it. I mean no sound of any kind. Also couldn’t get it to activate on Google Fi. Will be watching to see if someone solves the Sound problem. We could just skip on past A11.
Click to expand...
Click to collapse
Where did you get V50 engineering abl files as well as stock?, I just want to make sure to get the correct files
Guide LG G8/G8x/v50 Bootloader Unlock and Magisk Root using Firehose
Disclaimer: I am not responsible for any problems from using this guide. Works for G8, G8s, G8x, and v50 Confirmed working on G8 and v50 Requirements: Android 10 QFIL...
forum.xda-developers.com
There's no such thing, afak, of a v50 Eng abl. Read the header on the thread! If you don't have one of those phone models, don't! All of this seems to be predicated on the g8x eng abl which is the DL on that thread. READ that thread closely. I did, BL unlock and then flash A12 GSI.
hooutoo said:
Guide LG G8/G8x/v50 Bootloader Unlock and Magisk Root using Firehose
Disclaimer: I am not responsible for any problems from using this guide. Works for G8, G8s, G8x, and v50 Confirmed working on G8 and v50 Requirements: Android 10 QFIL...
forum.xda-developers.com
There's no such thing, afak, of a v50 Eng abl. Read the header on the thread! If you don't have one of those phone models, don't! All of this seems to be predicated on the g8x eng abl which is the DL on that thread. READ that thread closely. I did, BL unlock and then flash A12 GSI.
Click to expand...
Click to collapse
Ok,ok
Hello, I followed your instructions as written but when I reboot my phone I am stuck at a boot logo cycle, but my comment doesnt have to do with that, I want to ask if maybe you know what could've gone wrong.
I also own a g8 from verizon, I do have bootloader unlock, and tried to install Havoc OS, I wanted to mention this in case it is useful
Dude, I have no knowledge of G8, per se. My main goal was to get away from Sprint software on my v450pm. These phones are a little touchy. I do know that if you have a proven RESTORE method then you can mess around.. If you're Qfil_ing your phone you MUST have a backup of EVERY damn partition. I trashed my ftm partition and it was bad. Use telegram group for very good info. I have yet to be able to logon to Google Fi, an mnvo of Tmob. I've crossflashed to Eu A11, no go. I'm about to try some other roms, but again a backup will be needed.
Remember, you gotta have a way out or you're gonna pay $14 bucks to a Russian.
hooutoo said:
Dude, I have no knowledge of G8, per se. My main goal was to get away from Sprint software on my v450pm. These phones are a little touchy. I do know that if you have a proven RESTORE method then you can mess around.. If you're Qfil_ing your phone you MUST have a backup of EVERY damn partition. I trashed my ftm partition and it was bad. Use telegram group for very good info. I have yet to be able to logon to Google Fi, an mnvo of Tmob. I've crossflashed to Eu A11, no go. I'm about to try some other roms, but again a backup will be needed.
Remember, you gotta have a way out or you're gonna pay $14 bucks to a Russian.
Click to expand...
Click to collapse
Yeah, I know, like I said in my previous comment my phone got stuck in a boot loop, I fix it just by loading system_a partition in qfil, so I am gonna give it another shot and see if it works, already backed up every partition just in case anything goes wrong
If you're goona play around, this is secondary bs. My real phone is a FLIP3 and I'm not allowed to play unlesss to make/awnswer call.
Does somebody tried tp flash GSI with LineAge (A11) or Arrow(A12) vendor to g8?
I`m interesting about dt2w .. I flashed GSI`s to my G820UM on the past (A10 stock vendor) and it have no dt2w.. ((
i ended zeroing my imei from sprint G8 but thats okay i dont care for it much but what i do care is getting some LOS 17.1 on the sprint G8
where do we have any links to these so called GSI images?
blaze2051 said:
where do we have any links to these so called GSI images?
Click to expand...
Click to collapse
Treble-Enabled Device Development A/AB ROMS
Treble-Enabled Device Development A/AB ROMS
forum.xda-developers.com
From what I remember when I tested multiple Android 11 GSIs such as Pixel Experience, I couldn't get vibration to work on my G8.