Why cant you flash roms with twrp on this device? - Moto G Power Questions & Answers

Hi, I just noticed you have to flash with a pc every time with roms with this phone. Is there no way to flash roms with twrp? And if so how come? Search function if completely broken so I can't search if this has already been asked

Which exact model do you have? On my XT2041-4 I had no issue just doing "fastboot flash recovery twrp-3.4.0-0-sofia-test9.img" and replacing the recovery without problems. Although people with differing models have reported touch screen issues (although some suggest plugging in a usb mouse to bypass them).
So if you can get TWRP installed there shouldn't be any need to use a computer anymore, although its not such a big hasstle really how often do you flash a new ROM when you are away from your computer? As for the backup/restore function it is unreliable with the G Power.

Not sure about model but its the eu version XT2041-3 I think?
Anyway, I had intalled a newer version of twrp and that's why I had issues. I installed the one you suggested and now it works so thanks a lot! I saw a few people say recovery was bad for this phone so that's why I thought it wouldn't work. So again thanks!

Tronicdesu said:
Not sure about model but its the eu version XT2041-3 I think?
Anyway, I had intalled a newer version of twrp and that's why I had issues. I installed the one you suggested and now it works so thanks a lot! I saw a few people say recovery was bad for this phone so that's why I thought it wouldn't work. So again thanks!
Click to expand...
Click to collapse
Glad it works for you, what they mean by bad I guess is the bug I mentioned on some models, and the backup/restore function not working properly with encrypted data. You will also have to reflash the original recovery if you want to apply an OTA update.

Forgive the intrusion, but I believe in his original post Tronicdesu asks a valid question which remains unanswered. It seems to me he's asking about flashing ROMs, not flashing TWRP.
You can indeed flash TWRP using a PC and then use TWRP when detached from your PC. But what can you do with TWRP besides flashing modules and wiping data and such? Can you flash a new ROM? I'm pretty sure you cannot. Can you backup your phone? Maybe not. But I'm not 100% sure on either count.
Most OP installation instructions in these ROM forums describe using your PC to install their custom wares. This is a far cry from the good old days of downloading a ROM, a new Gapps, then firing up TWRP. Remember CWM?
It seems to me custom ROM flashing is dying a slow death from complications introduced by Project Treble. Perhaps Treble made life easier for vendors wanting to update their existing phones with (mostly non-existent) ROMs. But lightly-committed enthusiasts have a devil of time installing a custom ROM nowadays.
In the case of Motorola, it doesn't help when they sell ninety-nine variants of the same hardware to retail customers, and more to a dozen different carriers.
I just bought my new Moto G Power 2020 from Amazon. I love the hardware. But when I look at custom ROM options and the steps needed... Crikey! Do I have to stand on one foot and stick my finger somewhere?
Forgive the rant, am I barking up the wrong tree here?

As for the backup/restore function it is unreliable with the G Power.
Click to expand...
Click to collapse
Yeah, so just cross your fingers.
...A few people say recovery was bad for this phone so that's why I thought it wouldn't work. So again thanks!
Click to expand...
Click to collapse
Yup, and a big shout out to Team Win Recovery Project!
I'm not trolling here. I don't know what to do with my fingers! Bite them?

Related

About to buy an LG G3, PLEASE HELP!!

Dear Friends,
I am a US consumer. About to buy a Verizon LG G3. My number # 1 priority in a phone is, more of less development support for a phone. Number of ROMs being developed, how many choices, mods, frequent updates, and etc.
Clearly, the International version D855 is the King. Number 2 is probably D851, the T-Mobile US Variant with the Unlocked bootloader. International versions are expensive and hard to find in America and it's more or less the same for the T-Mobile version.
I browsed the Development section for all G3 variants on XDA, and surprisingly, the number 3 variant is the Verizon, US Model! Which is fine by me, because it can be unlocked and used on AT&T and I am moving to Verizon soon, for the better coverage and LTE speeds.
I am lined up to pull the trigger on buying the Verizon G3, as we speak, but I need some help confirmation from you guys:
1. Is it true, that with the BUMP'd/TWRP recovery, the Verizon G3 is as good as the Unlocked bootloader models, like D851 and D855? If not, what is the difference, disadvantage?
2. How would you rate the Development support for the Verizon variant of the LG G3?
Thank you for your help! I have the seller lined up, please respond as soon as you can, I would really appreciate it!
ProFragger said:
Dear Friends,
I am a US consumer. About to buy a Verizon LG G3. My number # 1 priority in a phone is, more of less development support for a phone. Number of ROMs being developed, how many choices, mods, frequent updates, and etc.
Clearly, the International version D855 is the King. Number 2 is probably D851, the T-Mobile US Variant with the Unlocked bootloader. International versions are expensive and hard to find in America and it's more or less the same for the T-Mobile version.
I browsed the Development section for all G3 variants on XDA, and surprisingly, the number 3 variant is the Verizon, US Model! Which is fine by me, because it can be unlocked and used on AT&T and I am moving to Verizon soon, for the better coverage and LTE speeds.
I am lined up to pull the trigger on buying the Verizon G3, as we speak, but I need some help confirmation from you guys:
1. Is it true, that with the BUMP'd/TWRP recovery, the Verizon G3 is as good as the Unlocked bootloader models, like D851 and D855? If not, what is the difference, disadvantage?
2. How would you rate the Development support for the Verizon variant of the LG G3?
Thank you for your help! I have the seller lined up, please respond as soon as you can, I would really appreciate it!
Click to expand...
Click to collapse
Having the bump'd twrp is basically the same thing. No matter which way you get to a custom recovery it's all the same. In my opinion its a great phone to have and pretty hard to screw something up. Sky Dragon and Jasmine are my personal favorites as far as Stock roms go. Unless you want to wait for the G4 i would go ahead and pull the trigger. You won't be disappointed.
Edde3d said:
Having the bump'd twrp is basically the same thing. No matter which way you get to a custom recovery it's all the same. In my opinion its a great phone to have and pretty hard to screw something up. Sky Dragon and Jasmine are my personal favorites as far as Stock roms go. Unless you want to wait for the G4 i would go ahead and pull the trigger. You won't be disappointed.
Click to expand...
Click to collapse
This is excellent news bud, thank you! What tripped me up was the fact that the T-Mobile version is so much more expensive... Why exactly ?
One question for you, how would you rate the development support for the Verizon variant? And yes, I'm more interested in CM12 kind of ROMs.
Lastly, if the seller has OTA'd to Lollipop, can I somehow bring it back to the KK firmware in I want that?
Thanks so much for your help again!
ProFragger said:
This is excellent news bud, thank you! What tripped me up was the fact that the T-Mobile version is so much more expensive... Why exactly ?
Click to expand...
Click to collapse
Must be that Qi charging antenna sticker... The VZW comes with only the NFC installed, but it is easy and cheap to upgrade.
ProFragger said:
One question for you, how would you rate the development support for the Verizon variant? And yes, I'm more interested in CM12 kind of ROMs.
Click to expand...
Click to collapse
I have to say that it is pretty excellent. Lots of support just for the VZW variant on the AOSP side and many of the goodies from the main LG G3 thread are also applicable. I find the best phones for hacking up are the ones available on most of the US carriers.
ProFragger said:
Lastly, if the seller has OTA'd to Lollipop, can I somehow bring it back to the KK firmware in I want that?
Click to expand...
Click to collapse
Easiest way would be to flash a KK stock-based ROM. That way, you go bloat-free, get fixes, and stop the OTA if you're freezing on KK.
epidenimus said:
Must be that Qi charging antenna sticker... The VZW comes with only the NFC installed, but it is easy and cheap to upgrade.
I have to say that it is pretty excellent. Lots of support just for the VZW variant on the AOSP side and many of the goodies from the main LG G3 thread are also applicable. I find the best phones for hacking up are the ones available on most of the US carriers.
Easiest way would be to flash a KK stock-based ROM. That way, you go bloat-free, get fixes, and stop the OTA if you're freezing on KK.
Click to expand...
Click to collapse
Thanks for the response, bud. Wireless charging really hasn't been a factor me, so far, so it's a non-issue. Good to hear of the VZW Dev support, although I'd have to say it's probably because someone found a way to "bump" or install Custom Recovery on a locked Bootloader, which is every phone on Verizon ! Too bad, because these LTE phones are factory unlocked for Global use, but so crippled, thanks to the bootloader non-sense. I wish the exploit extended to the Note lines or even HTC phones.
This is one reason why we see most of the T-Mobile variants selling like hot cakes, even though Sprint has that as well, the supported GSM functionality and bands are just not there.
I assume doing a simple Stock ROM flash via the LG Flash Tools, or "KDZ" is the way to get back to KK, if wanted? No downgrade issues like Notes, correct? Apparently, you can't downgrade the bootloader on those once moved to LP ...
ProFragger said:
Thanks for the response, bud. Wireless charging really hasn't been a factor me, so far, so it's a non-issue. Good to hear of the VZW Dev support, although I'd have to say it's probably because someone found a way to "bump" or install Custom Recovery on a locked Bootloader, which is every phone on Verizon ! Too bad, because these LTE phones are factory unlocked for Global use, but so crippled, thanks to the bootloader non-sense. I wish the exploit extended to the Note lines or even HTC phones.
This is one reason why we see most of the T-Mobile variants selling like hot cakes, even though Sprint has that as well, the supported GSM functionality and bands are just not there.
I assume doing a simple Stock ROM flash via the LG Flash Tools, or "KDZ" is the way to get back to KK, if wanted? No downgrade issues like Notes, correct? Apparently, you can't downgrade the bootloader on those once moved to LP ...
Click to expand...
Click to collapse
Yes, you can either use the "kdz", or " tot" methods of restoring back to software version 10B (the initial stock software that is easily rootable/unlockable using stump and bump). I personally prefer the tot method, but that probably because I've got a Win 7 computer ( Win 8 has apparently caused some issues for some using the tot method), and its the first method that came out that I used so just stuck with it, but either would work great. And no, no downgrade nonsense or risk of bricks, regardless of firmware it comes on (at least as of this writing lol)
ohlin5 said:
Yes, you can either use the "kdz", or " tot" methods of restoring back to software version 10B (the initial stock software that is easily rootable/unlockable using stump and bump). I personally prefer the tot method, but that probably because I've got a Win 7 computer ( Win 8 has apparently caused some issues for some using the tot method), and its the first method that came out that I used so just stuck with it, but either would work great. And no, no downgrade nonsense or risk of bricks, regardless of firmware it comes on (at least as of this writing lol)
Click to expand...
Click to collapse
This is excellent news and response, bud, thanks! Although, from a little bit of reading around here, I have heard of at least a few instances of people restoring stock firmware and in the process, somehow magically clearing out their IMEI to 0 !!! Is this actually true and a common occurrence? I heard their is a process to correct is via QPST, but it is arduous.
I wish someone did a video of Root + TWRP from starting to end for the LG G3 (Verizon version). Seeing how this will be my first LG phone, terms still confuse me, like Root method names, what exactly does "stump" or "bump" mean, and yeah, getting TWRP on there.
There is also a one-click TWRP installer for the VZW G3 on the Playstore? Is that true? Is that the same as having Bumped TWRP? Thanks!
ProFragger said:
This is excellent news and response, bud, thanks! Although, from a little bit of reading around here, I have heard of at least a few instances of people restoring stock firmware and in the process, somehow magically clearing out their IMEI to 0 !!! Is this actually true and a common occurrence? I heard their is a process to correct is via QPST, but it is arduous.
I wish someone did a video of Root + TWRP from starting to end for the LG G3 (Verizon version). Seeing how this will be my first LG phone, terms still confuse me, like Root method names, what exactly does "stump" or "bump" mean, and yeah, getting TWRP on there.
There is also a one-click TWRP installer for the VZW G3 on the Playstore? Is that true? Is that the same as having Bumped TWRP? Thanks!
Click to expand...
Click to collapse
I can't speak to the IMEI clearing as being a "common" issue....I've restored at least 5 different phones using the tot method, several multiple times and never once had an issue. I do, however, maintain a backup in the cloud of the EFS partition (same basic thing I think? I just know it's an important partition lol) for every phone I oversee and have messed with.
As for your question about stump/bump/etc., there are several different root methods out now...."Stump root" was just the name of the first - and so it's what I've always stuck with. "Bump", on the other hand, is the method for "unlocking" the bootloader and flashing TWRP.
As for the play store 'auto' app, I hadn't even heard of it until you said something and I searched. I'm assuming you're talking about this. All I can say is that I've never used it so I have no idea. Below I've laid out the steps that I, personally, follow each and every time I've gotten a new device or restored one. I realize there may be simpler ways out there now, but I've been in this specific community since the very beginning, and so I've just stuck with the "tried and true" stuff that came out first.
As for the one click TWRP installer on the play store, again I don't know. However, flashing the "bumped" TWRP via flashify is probably the easiest way to do it (it is not officially stated by the devs to work, but countless people including myself numerous times have confirmed it does).
So, TLDR:
If I were to get a brand new, VS985 today, here is the exact set of steps I would follow (I just got another one 2 weeks ago and these are what I did, and have always done):
1). Use the tot method, found here to restore (downgrade) back to the initial stock release software (version 10B_03). Alternatively, you can use the "kdz" method found here, but on my Windows 7 PC the tot method has always worked like a charm and the one time I used the kdz method it seemed a bit sketchier, but to each their own. I think the main "push" for the kdz method was that some people were having trouble getting the tot method to work on computers w/ Windows 8/8.1.
2). Once that's done, reboot and do minimal setup, then use stump root (found here) to root. Follow the directions exactly, and as long as you're on 10B it will still work - it's just been patched in newer software versions. After rooting and rebooting, then install superSU from the play store, open that, update the binary via "normal" method and then reboot once more. After that reboot, uninstall the stump app, you don't need it anymore.
3). Then, install Flashify from the play store. To be safe, I usually open it and make sure I've granted root, then close it and open superSU and make sure it's got the green mark next to it signifying it has full root access (again, just to be sure). Then, download the "bumped" TWRP image from here, and put it somewhere you can find it on your INTERNAL storage (not sure if this is vital, but again, just being safe). Also, for later, download the zip of TWRP 2.8.6.1 from here
4). Use the Flashify file browser to flash that recovery image you just downloaded to the your internal storage. Let it do it's thing, then reboot when it prompts you.
5). You should now boot up into TWRP. Use the install function to update from the TWRP you just flashed (2.8.0.0) to the 2.8.6.1 zip you just downloaded. Then use reboot>recovery to confirm it took.
6). That's pretty much it. With that you're fully rooted + unlocked. Only other thing I would highly recommend at this point is following the guide here to back up your EFS partition, and then store it to your Google drive or dropbox or other cloud storage or somewhere safe lol. If you're gonna stay stock I'd freeze the system update apps, or better use just flash skydragon or jasmine roms as they're great stock-based roms.
Any other questions just let me know.
ohlin5 said:
I can't speak to the IMEI clearing as being a "common" issue....I've restored at least 5 different phones using the tot method, several multiple times and never once had an issue. I do, however, maintain a backup in the cloud of the EFS partition (same basic thing I think? I just know it's an important partition lol) for every phone I oversee and have messed with.
As for your question about stump/bump/etc., there are several different root methods out now...."Stump root" was just the name of the first - and so it's what I've always stuck with. "Bump", on the other hand, is the method for "unlocking" the bootloader and flashing TWRP.
As for the play store 'auto' app, I hadn't even heard of it until you said something and I searched. I'm assuming you're talking about this. All I can say is that I've never used it so I have no idea. Below I've laid out the steps that I, personally, follow each and every time I've gotten a new device or restored one. I realize there may be simpler ways out there now, but I've been in this specific community since the very beginning, and so I've just stuck with the "tried and true" stuff that came out first.
As for the one click TWRP installer on the play store, again I don't know. However, flashing the "bumped" TWRP via flashify is probably the easiest way to do it (it is not officially stated by the devs to work, but countless people including myself numerous times have confirmed it does).
So, TLDR:
If I were to get a brand new, VS985 today, here is the exact set of steps I would follow (I just got another one 2 weeks ago and these are what I did, and have always done):
1). Use the tot method, found here to restore (downgrade) back to the initial stock release software (version 10B_03). Alternatively, you can use the "kdz" method found here, but on my Windows 7 PC the tot method has always worked like a charm and the one time I used the kdz method it seemed a bit sketchier, but to each their own. I think the main "push" for the kdz method was that some people were having trouble getting the tot method to work on computers w/ Windows 8/8.1.
2). Once that's done, reboot and do minimal setup, then use stump root (found here) to root. Follow the directions exactly, and as long as you're on 10B it will still work - it's just been patched in newer software versions. After rooting and rebooting, then install superSU from the play store, open that, update the binary via "normal" method and then reboot once more. After that reboot, uninstall the stump app, you don't need it anymore.
3). Then, install Flashify from the play store. To be safe, I usually open it and make sure I've granted root, then close it and open superSU and make sure it's got the green mark next to it signifying it has full root access (again, just to be sure). Then, download the "bumped" TWRP image from here, and put it somewhere you can find it on your INTERNAL storage (not sure if this is vital, but again, just being safe). Also, for later, download the zip of TWRP 2.8.6.1 from here
4). Use the Flashify file browser to flash that recovery image you just downloaded to the your internal storage. Let it do it's thing, then reboot when it prompts you.
5). You should now boot up into TWRP. Use the install function to update from the TWRP you just flashed (2.8.0.0) to the 2.8.6.1 zip you just downloaded. Then use reboot>recovery to confirm it took.
6). That's pretty much it. With that you're fully rooted + unlocked. Only other thing I would highly recommend at this point is following the guide here to back up your EFS partition, and then store it to your Google drive or dropbox or other cloud storage or somewhere safe lol. If you're gonna stay stock I'd freeze the system update apps, or better use just flash skydragon or jasmine roms as they're great stock-based roms.
Any other questions just let me know.
Click to expand...
Click to collapse
Hey bud,
This is probably the BEST post I have EVER been a recipient of at XDA. And trust me, I have been here since almost 2008! So please accept my deepest gratitude, so detailed, and so patient, really excellent job and excellent member of the community!
I ordered my phone, it is used, so not sure what build it will have, but if it took the OTA, then likely, it's LP and I would have to downgrade to 10b, like you said and then use Stump to Root. Problem is, since we can't backup EFS without Root, or TWRP, rather, it is making me nervous to use the TOT method first, which as I mentioned earlier, I have read, people blowing their IMEIs like that before ...
With that said, I think you have laid everything out nicely for me, just a matter of getting the phone, sitting down, and getting through the process . What would make it easier, is a Rooting method without the downgrade, but that's just me being really nit picky .
The other thought lingering in my head... since this my first LG, do I enjoy a Optimus UI ROM for a bit or go straight for the no nonsense CM12 or 12.1? Do you guys have the non working NFC on CM ROMs as well or other bugs that are common like that? I heard the LG G3 stock ROM got super laggy and heats the phone up!
ProFragger said:
Hey bud,
This is probably the BEST post I have EVER been a recipient of at XDA. And trust me, I have been here since almost 2008! So please accept my deepest gratitude, so detailed, and so patient, really excellent job and excellent member of the community!
I ordered my phone, it is used, so not sure what build it will have, but if it took the OTA, then likely, it's LP and I would have to downgrade to 10b, like you said and then use Stump to Root. Problem is, since we can't backup EFS without Root, or TWRP, rather, it is making me nervous to use the TOT method first, which as I mentioned earlier, I have read, people blowing their IMEIs like that before ...
With that said, I think you have laid everything out nicely for me, just a matter of getting the phone, sitting down, and getting through the process . What would make it easier, is a Rooting method without the downgrade, but that's just me being really nit picky .
The other thought lingering in my head... since this my first LG, do I enjoy a Optimus UI ROM for a bit or go straight for the no nonsense CM12 or 12.1? Do you guys have the non working NFC on CM ROMs as well or other bugs that are common like that? I heard the LG G3 stock ROM got super laggy and heats the phone up!
Click to expand...
Click to collapse
Thanks for the compliment What can I say, I've just seen too many crap-tastic tutorials
I understand your concern about the whole imei thing, I'd be the same way had I not done it so many times. Could you link the places where you've seen people wiping out their imeis supposedly? Also, if you're willing to do a little reading, something along these lines MIGHT work just to obtain root while still on STOCK LP (which I'd what I'm assuming it would come on:
http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951
If you do go this route and try to root while still on stock and before downgrading so that you can backup the efs partition, then be sure to NOT install twrp unless you do a bunch of reading beforehand as I believe it is the aboot that changed on LP and if you try to flash the twrp images I posted while on stock LP you'll get secure boot errors and have a heck of a mess. IMHO, better to either bite the bullet and do the downgrade straight (as I haven't seen these imei wipes you're noting and I've done several myself with zero issues), OR try and root stock LP, then backup the EFS partition, and THEN downgrade through the steps I posted.
Either way, with the Roms, its pretty much same as normal. I never recommend full stock, as if you're gonna root and unlock, you might as well use it IMHO. Stock is good if your most important things are stability and (at least currently and in my experience) battery life, while aosp based is better if you like the cleaner look, and most customizability. Either way you'll be OK. If you go for stock LG, I'd recommend either jasmine ROM or skydragon ROM. I've used skydragon ROM for a bit and its great if you love stock. I'm more of an aosp guy and so I currently use CM 12.1 and its easily DD stable for me, but not without it's quirks - sometimes the screen double tap to wake doesn't work or screen doesn't come on post-call, sometimes the battery life ain't great, sometimes it runs hot, etc. but all typically good enough for reasonable DD stability. I've started using 777kernel on top of the CM 12.1 flash and the device seems to run a bit cooler.
ohlin5 said:
Thanks for the compliment What can I say, I've just seen too many crap-tastic tutorials
I understand your concern about the whole imei thing, I'd be the same way had I not done it so many times. Could you link the places where you've seen people wiping out their imeis supposedly? Also, if you're willing to do a little reading, something along these lines MIGHT work just to obtain root while still on STOCK LP (which I'd what I'm assuming it would come on:
http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951
If you do go this route and try to root while still on stock and before downgrading so that you can backup the efs partition, then be sure to NOT install twrp unless you do a bunch of reading beforehand as I believe it is the aboot that changed on LP and if you try to flash the twrp images I posted while on stock LP you'll get secure boot errors and have a heck of a mess. IMHO, better to either bite the bullet and do the downgrade straight (as I haven't seen these imei wipes you're noting and I've done several myself with zero issues), OR try and root stock LP, then backup the EFS partition, and THEN downgrade through the steps I posted.
Either way, with the Roms, its pretty much same as normal. I never recommend full stock, as if you're gonna root and unlock, you might as well use it IMHO. Stock is good if your most important things are stability and (at least currently and in my experience) battery life, while aosp based is better if you like the cleaner look, and most customizability. Either way you'll be OK. If you go for stock LG, I'd recommend either jasmine ROM or skydragon ROM. I've used skydragon ROM for a bit and its great if you love stock. I'm more of an aosp guy and so I currently use CM 12.1 and its easily DD stable for me, but not without it's quirks - sometimes the screen double tap to wake doesn't work or screen doesn't come on post-call, sometimes the battery life ain't great, sometimes it runs hot, etc. but all typically good enough for reasonable DD stability. I've started using 777kernel on top of the CM 12.1 flash and the device seems to run a bit cooler.
Click to expand...
Click to collapse
Forgive the late response bud, the compliments are well deserved, trust me !
Here's an example of a gentleman losing his IMEI via TOT: http://forum.xda-developers.com/verizon-lg-g3/help/restore-via-tot-wipe-imei-t3033445
Let's hope it's the abnormal and not so normal .
I think let me get the phone I will keep, and will figure it out how to Root and Bump it. This phone I have to return, the item was not as described, but incidentally, came with Android 4.4.2! I imagine a simple Stump and Bump would have worked like a charm here?
In the end, playing with Optimus UI/LG UI, I couldn't find anything really that would make me stay with it. Outside of the camera app, 4K recording, and some minor features which I love, but no one else cares about.. like the Phone Muting and Speaker options in the Notification bar, while on a call. Can you believe, I couldn't even find a replacement app/dialer that could do that on AOSP ROM !?
Since you are a CM12.1 user, can I ask you what works on it and doesn't? NFC? Bluetooth? Knock-on, but NOT Knock Code, correct? IR Blaster? And have you had much luck with Xposed?
Please let me know your thoughts and input? Also, for CM12/12.1, do I need a special kernel for Knock on (and Knock Code) to work? If so, which one?
Thanks again bud!
ProFragger said:
In the end, playing with Optimus UI/LG UI, I couldn't find anything really that would make me stay with it. Outside of the camera app, 4K recording, and some minor features which I love, but no one else cares about..
Click to expand...
Click to collapse
The stock camera is surely missed, but the screen clarity is still amazing, the removable battery is sizeable, the sound is decent (no boom sound though), and you can slap an external SD card in it for more fun. The real appeal of this is that the hardware setup is pretty awesome for running and testing custom software. The LG stock ROM is really lackluster; a good AOSP ROM makes far better use of it.
ProFragger said:
Since you are a CM12.1 user, can I ask you what works on it and doesn't? NFC? Bluetooth? Knock-on, but NOT Knock Code, correct? IR Blaster? And have you had much luck with Xposed?
Click to expand...
Click to collapse
Yes, all of this works fine in the 12.1 ROMs I have tested out. You get knock-on and knock-off at the status bar. Quick Remote has been ported and works great. Most things that you might use Xposed to do are integrated in a good AOSP/CM based ROM already. I have not seen a need to install it on AOSP, just stock.
ProFragger said:
Please let me know your thoughts and input? Also, for CM12/12.1, do I need a special kernel for Knock on (and Knock Code) to work? If so, which one?
Click to expand...
Click to collapse
If the dev baked the feature in, the kernel that comes with it should work.
Just my two cents. I hope it helps!
Pretty much what he said ^^^
---------- Post added at 01:02 AM ---------- Previous post was at 12:58 AM ----------
ProFragger said:
Forgive the late response bud, the compliments are well deserved, trust me !
Here's an example of a gentleman losing his IMEI via TOT: http://forum.xda-developers.com/verizon-lg-g3/help/restore-via-tot-wipe-imei-t3033445
Let's hope it's the abnormal and not so normal .
I think let me get the phone I will keep, and will figure it out how to Root and Bump it. This phone I have to return, the item was not as described, but incidentally, came with Android 4.4.2! I imagine a simple Stump and Bump would have worked like a charm here?
In the end, playing with Optimus UI/LG UI, I couldn't find anything really that would make me stay with it. Outside of the camera app, 4K recording, and some minor features which I love, but no one else cares about.. like the Phone Muting and Speaker options in the Notification bar, while on a call. Can you believe, I couldn't even find a replacement app/dialer that could do that on AOSP ROM !?
Since you are a CM12.1 user, can I ask you what works on it and doesn't? NFC? Bluetooth? Knock-on, but NOT Knock Code, correct? IR Blaster? And have you had much luck with Xposed?
Please let me know your thoughts and input? Also, for CM12/12.1, do I need a special kernel for Knock on (and Knock Code) to work? If so, which one?
Thanks again bud!
Click to expand...
Click to collapse
See the other guys post, does a pretty fair overview. And thanks for that link....I mean it does show it can happen I guess, although I did also note the OP said in his last response that the 2nd time he toted he didn't have the issue, so he thinks maybe he screwed something up the first time....who knows lol
ohlin5 said:
Pretty much what he said ^^^
---------- Post added at 01:02 AM ---------- Previous post was at 12:58 AM ----------
See the other guys post, does a pretty fair overview. And thanks for that link....I mean it does show it can happen I guess, although I did also note the OP said in his last response that the 2nd time he toted he didn't have the issue, so he thinks maybe he screwed something up the first time....who knows lol
Click to expand...
Click to collapse
That would be me.
Yup, the second time around it worked just fine when I flashed back to 10b so I could then take the LP OTA. Of course, now we know that you can use the 12b image to flash back to official KK to take the OTA, or you can now flash the official 23C image that's out there and one-click root it.
Glad my post has been of use. I definitely wanted to share my experience so that others who experience the same issue can then get it rectified.
epidenimus said:
The stock camera is surely missed, but the screen clarity is still amazing, the removable battery is sizeable, the sound is decent (no boom sound though), and you can slap an external SD card in it for more fun. The real appeal of this is that the hardware setup is pretty awesome for running and testing custom software. The LG stock ROM is really lackluster; a good AOSP ROM makes far better use of it.
Yes, all of this works fine in the 12.1 ROMs I have tested out. You get knock-on and knock-off at the status bar. Quick Remote has been ported and works great. Most things that you might use Xposed to do are integrated in a good AOSP/CM based ROM already. I have not seen a need to install it on AOSP, just stock.
If the dev baked the feature in, the kernel that comes with it should work.
Just my two cents. I hope it helps!
Click to expand...
Click to collapse
ohlin5 said:
Pretty much what he said ^^^
---------- Post added at 01:02 AM ---------- Previous post was at 12:58 AM ----------
See the other guys post, does a pretty fair overview. And thanks for that link....I mean it does show it can happen I guess, although I did also note the OP said in his last response that the 2nd time he toted he didn't have the issue, so he thinks maybe he screwed something up the first time....who knows lol
Click to expand...
Click to collapse
iBolski said:
That would be me.
Yup, the second time around it worked just fine when I flashed back to 10b so I could then take the LP OTA. Of course, now we know that you can use the 12b image to flash back to official KK to take the OTA, or you can now flash the official 23C image that's out there and one-click root it.
Glad my post has been of use. I definitely wanted to share my experience so that others who experience the same issue can then get it rectified.
Click to expand...
Click to collapse
Guys,
I wanted to follow up/close the loop on this thread and thank you guys once again for all your help! I received 12B on my phone, was downloading materials to TOT down to 10B to root with stump, till I found this:
http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951
Worked like a charm, and can save others an hour or two, downloading the stock firmware and etc.
Now I am Rooted, TWRP'd 2.6.8.1, is it?, and efs backedup as well!
This is my first LG ever, so I will use stock ROM on it for a few weeks. It is unbelievable how LITTLE stock ROM support is, compared to the CM stuff, across the board for the G3. Maybe your experience is different, but that is what I have found. For every 5 aosp builds there is one stock ROM. And the Verizon variant is no different, only Jasmin and skydragon available. Please do correct me if I am wrong, and there are more ROMs out there to try? I still can't believe the lack of stock ROMs considering how crucial the camera is on this phone!
Between the sd and Jasmine, I think I will start out sd. Yes Jasmine is smaller and also updated later?, but also a little too complicated to install with separate Zips and stuff. What o you guys think?
Finally, if I go the aosp route, which likely I will in a few weeks, which one do you recommend for best features, updates, and performance/battery life?
Lastly, and possibly the most important question... What camera are you using on your CM ROMs ? I found that Lenovo was the best on my Note 3, best features and quality. Although a battery drain, no 4K, or HDR, and Panorama ... What do you guys think?
Thank you again guys for ALL your help!
ProFragger said:
Guys,
I wanted to follow up/close the loop on this thread and thank you guys once again for all your help! I received 12B on my phone, was downloading materials to TOT down to 10B to root with stump, till I found this:
http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951
Worked like a charm, and can save others an hour or two, downloading the stock firmware and etc.
Now I am Rooted, TWRP'd 2.6.8.1, is it?, and efs backedup as well!
This is my first LG ever, so I will use stock ROM on it for a few weeks. It is unbelievable how LITTLE stock ROM support is, compared to the CM stuff, across the board for the G3. Maybe your experience is different, but that is what I have found. For every 5 aosp builds there is one stock ROM. And the Verizon variant is no different, only Jasmin and skydragon available. Please do correct me if I am wrong, and there are more ROMs out there to try? I still can't believe the lack of stock ROMs considering how crucial the camera is on this phone!
Between the sd and Jasmine, I think I will start out sd. Yes Jasmine is smaller and also updated later?, but also a little too complicated to install with separate Zips and stuff. What o you guys think?
Finally, if I go the aosp route, which likely I will in a few weeks, which one do you recommend for best features, updates, and performance/battery life?
Lastly, and possibly the most important question... What camera are you using on your CM ROMs ? I found that Lenovo was the best on my Note 3, best features and quality. Although a battery drain, no 4K, or HDR, and Panorama ... What do you guys think?
Thank you again guys for ALL your help!
Click to expand...
Click to collapse
Nope, no other main stock based Roms for the G3....SD and Jasmine. If I were running stock I'd go SD with the custom kernel packaged with it. As for AOSP, people may disagree with me here, but I just sitck with CM. I like the idea of nightlies and being able to easily find updates from their websites and keep tabs on the progress updates merged, but that's just me. Recently I've been running CM with the 777 kernel, but only because the stock kernel seemed to be running very warm and draining battery a fair bit faster than usual. As for the camera, I again just stick with stock, as I find its good enough for me. I flashed several motorola, lenovo, etc. camera mods but it seemed like all too often it'd either be glitchy beyond measure or would break FFC in certain apps I knew to be otherwise working, etc. So I just started sticking with stock.
Random info:
I like focal (altho deprecated) it's in the play store. Lots of camera options.
If you do end up on some non stock roms, and have a dual band router, turn the channel on it to 11. It doesn't fix the wifi problems 100% but it may help.
Also there's plenty of g4 stuff floating around if you look for it.
Also you shouldn't have more than 0.25-0.5%/hr idle drain. If you do then somethings wrong. I'd install better battery stats right away and charge up to full and unplug before bed.
Amplify and greenify help but really the display is your battery culprit. I like cf lumen to help adjust the display from day to night usage.
ohlin5 said:
Nope, no other main stock based Roms for the G3....SD and Jasmine. If I were running stock I'd go SD with the custom kernel packaged with it. As for AOSP, people may disagree with me here, but I just sitck with CM. I like the idea of nightlies and being able to easily find updates from their websites and keep tabs on the progress updates merged, but that's just me. Recently I've been running CM with the 777 kernel, but only because the stock kernel seemed to be running very warm and draining battery a fair bit faster than usual. As for the camera, I again just stick with stock, as I find its good enough for me. I flashed several motorola, lenovo, etc. camera mods but it seemed like all too often it'd either be glitchy beyond measure or would break FFC in certain apps I knew to be otherwise working, etc. So I just started sticking with stock.
Click to expand...
Click to collapse
jfriend33 said:
Random info:
I like focal (altho deprecated) it's in the play store. Lots of camera options.
If you do end up on some non stock roms, and have a dual band router, turn the channel on it to 11. It doesn't fix the wifi problems 100% but it may help.
Also there's plenty of g4 stuff floating around if you look for it.
Also you shouldn't have more than 0.25-0.5%/hr idle drain. If you do then somethings wrong. I'd install better battery stats right away and charge up to full and unplug before bed.
Amplify and greenify help but really the display is your battery culprit. I like cf lumen to help adjust the display from day to night usage.
Click to expand...
Click to collapse
Guys, horrible day of flashing.
GPS issues with both SD and Jasmine. Tried both stock and SD kernels, as well as 12B and 23C radios, no dice :'(!
Resurrection Remix, not enough options for me and zero GPS locks :'(!
BlissPop came the closest. Bluetooth worked, Xposed, had the options I wanted, but GPS is still not strong enough indoors, and there is an issue WiFi not autoconnecting on each boot :'(!
Long story short, I think I need to head back to 12B somehow. Can anyone please tell me how? I will TOT to 10B, but then, how do I get to 12B? I can't find the image for it anywhere! Please do help, I need a reliable
working phone tomorrow, porting my number into a new carrier...
Thanks in advance!
Some people have to tot back to get gps working. For me, flashing sky always did the trick. Sometimes it takes longer or a reboot, and even setting gps to gps only (strange huh)?
Didn't u make a TWRP backup of working firmware?
I would seriously try flashing skydragon again. Why do u need gps indoors anyway?
Not sure about the tot but I think u can just take updates. Once u get to 10b please make a TWRP backup if you haven't already.
jfriend33 said:
Some people have to tot back to get gps working. For me, flashing sky always did the trick. Sometimes it takes longer or a reboot, and even setting gps to gps only (strange huh)?
Didn't u make a TWRP backup of working firmware?
I would seriously try flashing skydragon again. Why do u need gps indoors anyway?
Not sure about the tot but I think u can just take updates. Once u get to 10b please make a TWRP backup if you haven't already.
Click to expand...
Click to collapse
Thanks for the quick response bud. I will try SD again, maybe, but for now, I liked how Stock felt out of the box which was 12B. I feel like with rooting, manual debloating, and maybe the CPU thermals mods, I would have a snappy 4.2 device.
I'm stupid, I did not Nandroid the 12B I had . Thought it would be like Samsung, each firmware easily available for download on the Internet to flash via the LG Flash Tools.
I will TOT to 10B tomorrow, but then question is, how do I upgrade or OTA to 12B? Would it give me options on which update to take? Or will it take me to the latest, which is 23C?
Appreciate your help or if anyone can! Thank you!

Closed

Don't forget to hit the thanks button.
http://superstarmobility.weebly.com/
New thread: http://forum.xda-developers.com/android/development/twrp-m1-lg-k7-t3462130.
(Above TWRP can be flashed with Flashify from Playstore)
Instructions from video:
With phone powered off, hold POWER and VOLUME DOWN buttons until LG logo shows. Release POWER then quickly press and hold again until factory reset menu comes up. Select YES and you will be booted into recovery instead of a factory reset ; )
Thanks @czarsuperstar!
V2 with the proper cmd line from m1 aka LG K7
Reserved.
This the real deal?
goitalone said:
This the real deal?
Click to expand...
Click to collapse
Of course. You looked at the video?
goitalone said:
This the real deal?
Click to expand...
Click to collapse
I've used it and can confirm, first tested it with fastboot without flashing of course(use adb to get to the bootloader: adb reboot bootloader , then fastboot:fastboot boot "twrp.img file, tested then rebooted into bootloader, then flashed via fastboot:fastboot flash "twrp.img file") instructions are for any random person that come by i know you know how to do all this
concerned xda citizen
what are the boardconfig.mk file contents that you used to compile this recovery?
the fact youre using a ghetto hacked twrp that works is fine, but id prefer an actual device specific twrp version that will reliably work - theres no telling what this twrp can do to your device, and the fact youre using another devices ramdisk scares the hell out of me.
ramdisks arent something you play around with - you can seriously ruin someones device like that.
also requesting the twrp fstab file youve used.
youre literally just throwing files at users that have perviously bricked their devices and not explaining in detail what they consist of.
if you seriously damage any of these user's device partitions by overwriting the wrong partition, are you going to pay for the devices when theyre hardbricked and no longer responsive to the oem flashing?
not once have a even seen a warning on these files yet youre just posting forum to forum; not to mention youre inexperienced at rom/kernel/recovery compiling for the fact you think its okay to just throw a different devices ramdisk in there " because it just works." when we have readily available source for our device.
legally- youre held responsible for these files youre distributing.
and to those just flashing this twrp file to their device, yes its reversible - but would you want to find out it doesnt work when its too late? IE backing up partitions in the wrong order, and restoring them into the wrong partitions? the video shows it backs up and restores, but is it doing so in the right order? in the right places. i may be ranting but id rather be careful/safe then sorry.
not one detail of this compile/build has been released, just a link that is claimed to work.
"left sock fits on right, doesnt feel right - but my feet aren't cold!" is how this feels to me.
i was sketched to even test this twrp version considering you need to tell the factory reset "yes, i want to wipe" twice, in order to boot to twrp.
idk about you but ive never seen any recovery warrant those options. normally twrp would just boot upon button combo - which is why im sharing this post. recoveries arent supposed to be functioning that way.
NASSTYROME said:
what are the boardconfig.mk file contents that you used to compile this recovery?
the fact youre using a ghetto hacked twrp that works is fine, but id prefer an actual device specific twrp version that will reliably work - theres no telling what this twrp can do to your device, and the fact youre using another devices ramdisk scares the hell out of me.
ramdisks arent something you play around with - you can seriously ruin someones device like that.
also requesting the twrp fstab file youve used.
youre literally just throwing files at users that have perviously bricked their devices and not explaining in detail what they consist of.
if you seriously damage any of these user's device partitions by overwriting the wrong partition, are you going to pay for the devices when theyre hardbricked and no longer responsive to the oem flashing?
not once have a even seen a warning on these files yet youre just posting forum to forum; not to mention youre inexperienced at rom/kernel/recovery compiling for the fact you think its okay to just throw a different devices ramdisk in there " because it just works." when we have readily available source for our device.
legally- youre held responsible for these files youre distributing.
and to those just flashing this twrp file to their device, yes its reversible - but would you want to find out it doesnt work when its too late? IE backing up partitions in the wrong order, and restoring them into the wrong partitions? the video shows it backs up and restores, but is it doing so in the right order? in the right places. i may be ranting but id rather be careful/safe then sorry.
not one detail of this compile/build has been released, just a link that is claimed to work.
"left sock fits on right, doesnt feel right - but my feet aren't cold!" is how this feels to me.
i was sketched to even test this twrp version considering you need to tell the factory reset "yes, i want to wipe" twice, in order to boot to twrp.
idk about you but ive never seen any recovery warrant those options. normally twrp would just boot upon button combo - which is why im sharing this post. recoveries arent supposed to be functioning that way.
Click to expand...
Click to collapse
The first twrp was from a htc phone. This is from lg leon lte. Same manufacturer. I used my boot.img dumped on my sdcard and used the ramdisk from Twrp Leon aka c50 the leon twrp is missing the options seen on this one. Don't use it. But I'm working on cm_m1 so continue to use the old one and when your phone can't come on have fun getting in recovery. Make it better.
Recovery log
Make a log.
NASSTYROME said:
what are the boardconfig.mk file contents that you used to compile this recovery?
the fact youre using a ghetto hacked twrp that works is fine, but id prefer an actual device specific twrp version that will reliably work - theres no telling what this twrp can do to your device, and the fact youre using another devices ramdisk scares the hell out of me.
ramdisks arent something you play around with - you can seriously ruin someones device like that.
also requesting the twrp fstab file youve used.
youre literally just throwing files at users that have perviously bricked their devices and not explaining in detail what they consist of.
if you seriously damage any of these user's device partitions by overwriting the wrong partition, are you going to pay for the devices when theyre hardbricked and no longer responsive to the oem flashing?
not once have a even seen a warning on these files yet youre just posting forum to forum; not to mention youre inexperienced at rom/kernel/recovery compiling for the fact you think its okay to just throw a different devices ramdisk in there " because it just works." when we have readily available source for our device.
legally- youre held responsible for these files youre distributing.
and to those just flashing this twrp file to their device, yes its reversible - but would you want to find out it doesnt work when its too late? IE backing up partitions in the wrong order, and restoring them into the wrong partitions? the video shows it backs up and restores, but is it doing so in the right order? in the right places. i may be ranting but id rather be careful/safe then sorry.
not one detail of this compile/build has been released, just a link that is claimed to work.
"left sock fits on right, doesnt feel right - but my feet aren't cold!" is how this feels to me.
i was sketched to even test this twrp version considering you need to tell the factory reset "yes, i want to wipe" twice, in order to boot to twrp.
idk about you but ive never seen any recovery warrant those options. normally twrp would just boot upon button combo - which is why im sharing this post. recoveries arent supposed to be functioning that way.
Click to expand...
Click to collapse
Check out the LG L70 it's the same way to get in recovery. This must be your first LG phone.
i dont care whether its the same way to enter recovery, my care is youre using another phone's ramdisk in this device.
"I used my boot.img dumped on my sdcard and used the ramdisk from Twrp Leon aka c50 the leon"
post twrp.fstab and boardconfig.mk youve used for this "twrp" build.
this must be your first posting for development on an unsupported device.
as for anyone using another device's files when we have access to source of our own device - i wouldnt trust them to build anything, let alone CM. thats just pure shortcutting and laziness .. and at what expense?
as for twrp making this official, they wont - as you cannot provide SOURCE.
So, now, hopefully you've compiled TWRP for your device and gotten it working. Now, you'd like to know how to get TWRP officially supported for your device so that it can be installed automatically with GooManager. In order for us to add "official support" for your device we'll need the following:
1) Device configuration files to compile TWRP from source for your device. This means that you cannot have repacked a recovery.img by hand to get it working. We need to be able to compile it from source so that we can easily release future updates.
2) A copy of a build prop for your device (it's in /system/build.prop) so that we can add the correct device information to GooManager
3) We'll build a copy of TWRP and send it to you for validation. Once you've validated that we can build a working image for your device, we'll add it to GooManager.
Go spam the other thread. Over 200 downloads and no problems but there was problems right away with the first version. For your info download Twrp c50 from the Twrp site examine it and ask why it's incomplete. That's why I linked the video of the Twrp from the site and same problems. Bye and leave me be. Hd2 check it out. Czarsuperstar's HTC HD2 android custom roms. Check it out and leave me alone. Thanks for your concern. Oh and for your info we have the same keyboard configuration as the LG Leon. There's a device tree. Google it. Google is your friend bro.
NASSTYROME said:
i dont care whether its the same way to enter recovery, my care is youre using another phone's ramdisk in this device.
"I used my boot.img dumped on my sdcard and used the ramdisk from Twrp Leon aka c50 the leon"
post twrp.fstab and boardconfig.mk youve used for this "twrp" build.
this must be your first posting for development on an unsupported device.
as for anyone using another device's files when we have access to source of our own device - i wouldnt trust them to build anything, let alone CM. thats just pure shortcutting and laziness .. and at what expense?
as for twrp making this official, they wont - as you cannot provide SOURCE.
So, now, hopefully you've compiled TWRP for your device and gotten it working. Now, you'd like to know how to get TWRP officially supported for your device so that it can be installed automatically with GooManager. In order for us to add "official support" for your device we'll need the following:
1) Device configuration files to compile TWRP from source for your device. This means that you cannot have repacked a recovery.img by hand to get it working. We need to be able to compile it from source so that we can easily release future updates.
2) A copy of a build prop for your device (it's in /system/build.prop) so that we can add the correct device information to GooManager
3) We'll build a copy of TWRP and send it to you for validation. Once you've validated that we can build a working image for your device, we'll add it to GooManager.
Click to expand...
Click to collapse
not saying a official twrp isn't preferable, but man you got to learn how to talk to people, you were just short of cursing the dude out, and as far as the recovery the thing is solid(tested backup, flash and restore/ anyhow we got LGUP if you **** up so its not a huge deal), but anyone on this site shouldn't take someones word for things like recovery's and you should always test boot before you flash, also you don't seem to understand the first rule of xda-whatever happens to your device is on you, been that way since the og day's- talking politely to others is the way to go about things, people wont listen if you combative.
Kernel
Im building the kernel from source right now check out the video on Twitter. Anyone that wants to join the development I am down with it.
Didn't work, after selecting yes twice, my phone just starts like normal, doesn't go to TWRP or factory restore, it is there though because I can boot to it from the flashify app, ah well.
wait...my bad, I was highlighting the wrong one, lol, works great, thanks
Assuming it ever worked right it should work better now because you can always get to it.
As for concerns about the ramdisk I don't see any issues with that, it's just being used to boot and run recovery on if I'm not mistaken and apparently where the buttons get enabled so a necessity.
Considering many phones have such hacked together recoverys and many more have no custom recovery I'm thankful to have it particularly since most of my work is done away from my pc.
callihn said:
Assuming it ever worked right it should work better now because you can always get to it.
As for concerns about the ramdisk I don't see any issues with that, it's just being used to boot and run recovery on if I'm not mistaken and apparently where the buttons get enabled so a necessity.
Considering many phones have such hacked together recoverys and many more have no custom recovery I'm thankful to have it particularly since most of my work is done away from my pc.
Click to expand...
Click to collapse
Thanks for report. The other Twrp w/o the button combo was from a HTC phone lol and I am getting blasted. HTC or LG? LG K7. ... LG.
[email protected] said:
Thanks for report. The other Twrp w/o the button combo was from a HTC phone lol and I am getting blasted. HTC or LG? LG K7. ... LG.
Click to expand...
Click to collapse
Right and that's why the buttons didn't work. Great job! Best discovery yet for this phone, so happy that we can restore now withoit adb and withoit having to worry about debugging getting turn off, very essential find. Don't let those that don't understand get you down.
callihn said:
Right and that's why the buttons didn't work. Great job! Best discovery yet for this phone, so happy that we can restore now withoit adb and withoit having to worry about debugging getting turn off, very essential find. Don't let those that don't understand get you down.
Click to expand...
Click to collapse
I'm working on building it from source but keep getting errors and I'm trying it with another device that has Twrp (Moto E 2015) and followed the directions to the T and no luck. So I am trying......... Will let everyone know how it's going.
[email protected] said:
Im building the kernel from source right now check out the video on Twitter. Anyone that wants to join the development I am down with it.
Click to expand...
Click to collapse
kernel??????????????????????????
im down!

Looking for custom rom for Ulefone Armor X Oreo 8.1

I am looking for a custom rom, minus the Google stuff, that will work on my Ulefone Armor X Oreo 8.1. I have a working TWRP recovery and have rooted it via Magisk but went back to stock after a few nagging problems.
The phone spec isn't wonderful so need something lighter but still having plenty of functionality.
Cheers
Charlie-Boy said:
I am looking for a custom rom, minus the Google stuff, that will work on my Ulefone Armor X Oreo 8.1......
Click to expand...
Click to collapse
This specific device and Chipset is fairly new and there's very little on the forum that's specific to your device.
With that stated...
You have a Mediatek MT6739 (64 Bit) device that can be very helpful in that aspect.
Though I had located a few threads that won't be very helpful for you but, the following thread is about the best that your possibly going to find for your device at this point in time.
https://forum.xda-developers.com/showthread.php?t=2701283
It does take some time for developments to pop up on the forum for newer Mediatek Chipsets but, where there's a developer (with the same Chipset device), there's always a way depending on the level of difficulty.
I wish you the best of luck with your search!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Charlie-Boy said:
I am looking for a custom rom, minus the Google stuff, that will work on my Ulefone Armor X Oreo 8.1. I have a working TWRP recovery and have rooted it via Magisk but went back to stock after a few nagging problems.
The phone spec isn't wonderful so need something lighter but still having plenty of functionality.
Cheers
Click to expand...
Click to collapse
I'm also looking for that. But if I can get TWRP on it I'd probably try SU.
How did you get to install the TWRP? I found a few posts but was apprehensive about whether I can use SPFT to flash original stock ROM if things go wrong. I suppose that would be the easiest way.
For what I paid for the phone, it's a decent enough device.
Using SD card as internal memory always result in the total capacity being reported wrongly..256GB becomes 512GB with 50% occupied, 200GB becomes 256GB with 64GB occupied. Still waiting for their tech support to reply but unlikely they would.
Cheers!
I have rooted it several times and flashed the stock image several times too without a problem. Haven't used SU though I used Magisk.
.stupdroid.com/2018/07/Ulefone-Armor-X-root-twrp-.html
I do not have your issue with storage but my wireless charging mat today stopped charging but still lights up. Phone will still charge via cable. Trying to get a replacement mat.
I installed using SP flash tools on windows and Linux just to see the difference.
If you do a Google for Install TWRP ulefone armor x then you will get some information and relevant files.
Unlocking the bootloader via ADB is straightforward on Windows and Linux too. And then relocking it.
Regards
Charlie
Ibuprophen said:
This specific device and Chipset is fairly new and there's very little on the forum that's specific to your device.
With that stated...
You have a Mediatek MT6739 (64 Bit) device that can be very helpful in that aspect.
Though I had located a few threads that won't be very helpful for you but, the following thread is about the best that your possibly going to find for your device at this point in time.
https://forum.xda-developers.com/showthread.php?t=2701283
It does take some time for developments to pop up on the forum for newer Mediatek Chipsets but, where there's a developer (with the same Chipset device), there's always a way depending on the level of difficulty.
I wish you the best of luck with your search!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Click to expand...
Click to collapse
Thanks for the input I will have a read.
Charlie-Boy said:
I have rooted it several times and flashed the stock image several times too without a problem. Haven't used SU though I used Magisk.
.stupdroid.com/2018/07/Ulefone-Armor-X-root-twrp-.html
I do not have your issue with storage but my wireless charging mat today stopped charging but still lights up. Phone will still charge via cable. Trying to get a replacement mat.
I installed using SP flash tools on windows and Linux just to see the difference.
If you do a Google for Install TWRP ulefone armor x then you will get some information and relevant files.
Unlocking the bootloader via ADB is straightforward on Windows and Linux too. And then relocking it.
Regards
Charlie
Click to expand...
Click to collapse
Thanks for the info.
Cheers!
chooks06 said:
Thanks for the info.
Cheers!
Click to expand...
Click to collapse
No problem.
Charlie-Boy said:
I am looking for a custom rom, minus the Google stuff, that will work on my Ulefone Armor X Oreo 8.1. I have a working TWRP recovery and have rooted it via Magisk but went back to stock after a few nagging problems.
The phone spec isn't wonderful so need something lighter but still having plenty of functionality.
Cheers
Click to expand...
Click to collapse
Where did you get the TWRP for Ulefone Armor X. I've been trying to search it all over and haven't found anything. If possible can you please share a link? TIA
abhijeet715 said:
Where did you get the TWRP for Ulefone Armor X. I've been trying to search it all over and haven't found anything. If possible can you please share a link? TIA
Click to expand...
Click to collapse
Code:
https://www.needrom.com/download/twrp-armox-x/
There are other places listed on Google.
Anyone had this in recovery mode?
Had also tried flashing the TWRP but it just didn't stick and was asking for a password on first launch.
Edit.. all links I tried point to the same location to download. Same files.
chooks06 said:
Anyone had this in recovery mode?
Had also tried flashing the TWRP but it just didn't stick and was asking for a password on first launch.
Edit.. all links I tried point to the same location to download. Same files.
Click to expand...
Click to collapse
im also facing the same issue... kindly someone help.. ive explained my issue below:
Can someone confirm? My device is encrypted by default, so whenever i install TWRP it says to decrypt device. I tried the pattern, changed it to password, and pin still my device doesnt decrypt in twrp. I feel its a twrp bug, because when i set the device to ask pattern during boot, the same pattern/pin/password is accepted, but not in twrp.
I want to know 3 things:
1. Are your devices encrypted by default (i dont remember encrypting my device, I dont know how it is encrypted)
2. Are you facing this same issue of entering password when you reboot into recovery?
3. What is the purpose of the boot.img in the twrp zip? am i required to flash it before flashing the recovery, or does it remove encryption?
Charlie-Boy said:
I am looking for a custom rom, minus the Google stuff, that will work on my Ulefone Armor X Oreo 8.1. I have a working TWRP recovery and have rooted it via Magisk but went back to stock after a few nagging problems.
The phone spec isn't wonderful so need something lighter but still having plenty of functionality.
Cheers
Click to expand...
Click to collapse
Charlie, could share how you got the TWRP working?
Have been fiddling around until battery showed -1%.. Had to go back to stock.
Thanks mate!
Choo ks
In the folder containing the TWRP recovery there are 3 files, boot.img, scatter, and recovery. You only flash recovery, you have flashed the boot image, ensure the checkbox is unticked after loading from scatter in SP tools. That is what I think you have done to get that result.
Follow the guide here. I did it a few times before success as I followed a guide from another site.
https://www.stupdroid.com/2018/07/Ulefone-Armor-X-root-twrp-.html
Click to expand...
Click to collapse
I think I installed magisk using this method, clearing dalvik and cache.
https://www.stupdroid.com/2018/02/magisk-16.0-download.html
Click to expand...
Click to collapse
Charlie-Boy said:
In the folder containing the TWRP recovery there are 3 files, boot.img, scatter, and recovery. You only flash recovery, you have flashed the boot image, ensure the checkbox is unticked after loading from scatter in SP tools. That is what I think you have done to get that result.
Click to expand...
Click to collapse
That's what I did, using the downloaded scatter file. Was experimenting.
---------- Post added at 06:49 PM ---------- Previous post was at 06:44 PM ----------
Charlie-Boy said:
Follow the guide here. I did it a few times before success as I followed a guide from another site.
I think I installed magisk using this method, clearing dalvik and cache.
Click to expand...
Click to collapse
Used the same guide. But TWRP came up with the decrypt data issue.
Did you have that issue?
chooks06 said:
Anyone had this in recovery mode?
Had also tried flashing the TWRP but it just didn't stick and was asking for a password on first launch.
Edit.. all links I tried point to the same location to download. Same files.
Click to expand...
Click to collapse
You ignore the password and change the language to English from Russian. Just don't enter a password at all. The recovery won't stick as Android replaces it when you reboot. After you've completed other steps maybe OEM unlocking then it stays, or so I read somewhere.
chooks06 said:
That's what I did, using the downloaded scatter file. Was experimenting.
---------- Post added at 06:49 PM ---------- Previous post was at 06:44 PM ----------
Used the same guide. But TWRP came up with the decrypt data issue.
Did you have that issue?
Click to expand...
Click to collapse
All of them are encrypted by default now. The password in TWRP should be ignored and just change the language and select storage etc.
abhijeet715 said:
im also facing the same issue... kindly someone help.. ive explained my issue below:
Can someone confirm? My device is encrypted by default, so whenever i install TWRP it says to decrypt device. I tried the pattern, changed it to password, and pin still my device doesnt decrypt in twrp. I feel its a twrp bug, because when i set the device to ask pattern during boot, the same pattern/pin/password is accepted, but not in twrp.
I want to know 3 things:
1. Are your devices encrypted by default (i dont remember encrypting my device, I dont know how it is encrypted)
2. Are you facing this same issue of entering password when you reboot into recovery?
3. What is the purpose of the boot.img in the twrp zip? am i required to flash it before flashing the recovery, or does it remove encryption?
Click to expand...
Click to collapse
Yes all are encrypted.
Yes I get the same request for password which I ignored and selected language and carried on.
I do not know why boot.img is included it just gets in the way.
After installing TWRP unlocking OEM bootloader and all the rest including rooting it I decided it would be better to wait for a new ROM. All we need is a working TWRP and an unlocked bootloader to flash a new ROM and we have that. It doesn't work very smoothly and I felt it could be better which is why I went back to stock.
When I posted this request I didn't imagine others would try installing Magisk etc, waste of time really as you won't stay with it either. Best wait for a ROM I think.
Charlie-Boy said:
Yes all are encrypted.
Yes I get the same request for password which I ignored and selected language and carried on.
I do not know why boot.img is included it just gets in the way.
After installing TWRP unlocking OEM bootloader and all the rest including rooting it I decided it would be better to wait for a new ROM. All we need is a working TWRP and an unlocked bootloader to flash a new ROM and we have that. It doesn't work very smoothly and I felt it could be better which is why I went back to stock.
When I posted this request I didn't imagine others would try installing Magisk etc, waste of time really as you won't stay with it either. Best wait for a ROM I think.
Click to expand...
Click to collapse
Im also unlocked and flashed twrp. I ignored the encryption message and proceeded, hit the storage sizes show 0, and neither can i access the storage to flash anything nor can i take backups. can you go to settings>security in your device, and tell me if your encryption says enabled? Tia
abhijeet715 said:
Im also unlocked and flashed twrp. I ignored the encryption message and proceeded, hit the storage sizes show 0, and neither can i access the storage to flash anything nor can i take backups. can you go to settings>security in your device, and tell me if your encryption says enabled? Tia
Click to expand...
Click to collapse
Mine is the same encryption is enabled. I select external SD storage and I am shown the contents using the same procedure as yourself, I cannot tell you why this is so. I am using the same technique, same phone, same settings, same TWRP, maybe we have different SD card?
That is all I can think of by way of an explanation. It works perfectly for me. I also made a backup which I can select and restore without a problem.

[ROM][OFFICIAL][10] LineageOS 17.1 Official

LineageOS 17.1 - Official
There is now an official LineageOS 17.1 build available for Ocean! This was not created by me. Most credit seems to be due to SyberHexen. I'm simply posting here because nobody else has done so.
Main Page
Installation Instructions
Greek2me said:
...LineageOS 17.1 - Official...
Click to expand...
Click to collapse
A tear of joy comes to my eye. Thanks for the heads up.
I've been using it daily and so far it's great. No bugs to report yet.
Greek2me said:
I've been using it daily and so far it's great. No bugs to report yet.
Click to expand...
Click to collapse
Thanks for that reassurance.
I'll be a few days behind you. My G7 Power is on a truck. I had been shopping for new device and wanted Moto G7 Power but did not see it in LOS. Then I saw your post. Within minutes I ordered the one I had been eyeing.
As to this thread, typically an LOS official ROM thread will have certain standard language and statements in the original posts. I have no complaint, I'm obviously delighted that you shared the information and you provide links to the official instructions, but be prepared to manage the inclusion of additional information in this thread or hand the thread off to a maintainer to make it the official official thread, or we follow to a new official thread LOS Moto G7 of power.
In any event... Thanks again!
Getting the following error when trying to flash <lineage-17.1-20200912-nightly-ocean-signed.zip>
Error applying update: 18 (ErrorCode::
kDownloadPayloadPubKeyVerificationError)
IronTechmonkey said:
Thanks for that reassurance.
I'll be a few days behind you. My G7 Power is on a truck. I had been shopping for new device and wanted Moto G7 Power but did not see it in LOS. Then I saw your post. Within minutes I ordered the one I had been eyeing.
As to this thread, typically an LOS official ROM thread will have certain standard language and statements in the original posts. I have no complaint, I'm obviously delighted that you shared the information and you provide links to the official instructions, but be prepared to manage the inclusion of additional information in this thread or hand the thread off to a maintainer to make it the official official thread, or we follow to a new official thread LOS Moto G7 of power.
In any event... Thanks again!
Click to expand...
Click to collapse
I'm glad I could reach you on time! I'll keep that in mind about the thread - thanks for the heads-up.
toddk63 said:
Getting the following error when trying to flash <lineage-17.1-20200912-nightly-ocean-signed.zip>
Error applying update: 18 (ErrorCode::
kDownloadPayloadPubKeyVerificationError)
Click to expand...
Click to collapse
I would recommend that you try the installation again, taking care to follow the pre-installation instructions here. Additionally, I recommend that you wipe everything (system, data, internal storage, and cache) before attempting to install LOS.
Install went fairly smooth last night.
Have had a few times (usually when playing a video via the browser) that the "shutdown" popup will show. Phone reboots but the Lineage "corrupt" screen comes up. Hitting Try Again works and it boots successfully.
Device in hand, I’m doing some research before flashing so here is a question about backing up and restoring when using this ROM on G7 Power (and maybe A/B devices in general). I’ve become accustomed to (or spoiled by) being able to install ROM/Gapps/SU, backup, or restore OS and apps (boot, data, system) from TWRP using resources on the external SD without connecting to computer. Not only was that convenient but it was also good for ROM bug testing; easy to test > break > restore.
Having accepted the reality of being attached to a computer for some of this work I’m still wondering about the best way to get full device backups. On a Moto X4 running LOS 15.1, where I had flashed in a recommended order to keep TWRP and LOS on the device (without LOS overwriting boot) there were problems with backing up. The ROM ran fine but any attempt to back it up (whether on device running TWRP via ADB) seemed to trash the existing installation so it would not boot. To be clear I’m not talking about attempts to restore a backup; the mere act of backing up the existing partitions seemed to break things. At the time SyberHexen gave some advise but I never had a chance to try it, and wanted to do a bit more fishing here first.
So - long story/question short(er): Does anybody here know what is the most reliable way to create a “whole device” backup (equivalent to boot/data/system from before A/B) so that a ROM scrambled by testing can be easily restored…to a backup copy that can be selected from an archive of backups (as opposed to just the other slot)?
IronTechmonkey said:
Device in hand, I’m doing some research before flashing so here is a question about backing up and restoring when using this ROM on G7 Power (and maybe A/B devices in general). I’ve become accustomed to (or spoiled by) being able to install ROM/Gapps/SU, backup, or restore OS and apps (boot, data, system) from TWRP using resources on the external SD without connecting to computer. Not only was that convenient but it was also good for ROM bug testing; easy to test > break > restore.
Having accepted the reality of being attached to a computer for some of this work I’m still wondering about the best way to get full device backups. On a Moto X4 running LOS 15.1, where I had flashed in a recommended order to keep TWRP and LOS on the device (without LOS overwriting boot) there were problems with backing up. The ROM ran fine but any attempt to back it up (whether on device running TWRP via ADB) seemed to trash the existing installation so it would not boot. To be clear I’m not talking about attempts to restore a backup; the mere act of backing up the existing partitions seemed to break things. At the time SyberHexen gave some advise but I never had a chance to try it, and wanted to do a bit more fishing here first.
So - long story/question short(er): Does anybody here know what is the most reliable way to create a “whole device” backup (equivalent to boot/data/system from before A/B) so that a ROM scrambled by testing can be easily restored…to a backup copy that can be selected from an archive of backups (as opposed to just the other slot)?
Click to expand...
Click to collapse
Some people have done it with success if u not rooted and have twrp flashed u can't read internal sd it is cripted until magisk is flashed .No I heard that dmvertey will decript with out root but u can't set lock screen in os.
roadkill42 said:
Some people have done it with success if u not rooted and have twrp flashed u can't read internal sd it is cripted until magisk is flashed .No I heard that dmvertey will decript with out root but u can't set lock screen in os.
Click to expand...
Click to collapse
This is the latest twrp for this phone touch ishue should b fixed. Siberhexon updated twrp
roadkill42 said:
Some people have done it with success if u not rooted and have twrp flashed u can't read internal sd it is cripted until magisk is flashed .No I heard that dmvertey will decript with out root but u can't set lock screen in os.
Click to expand...
Click to collapse
Thanks, I've heard about issues with lock screen/encryption and would deal with that for testing purposes by disabling security before doing anything in TWRP. I may have to be content with re-flashing and restoring apps if anything breaks.
[EDIT] I saw that you added a link to a TWRP build.which is appreciated but I would first try the official one (twrp-installer-3.4.0-0-ocean.zip) which the LOS instructions indicate. If I did use an alternative I'd want to get it from a designated portal and know more about its origins.
Derp. Disregard previous mention of official build. That was Pixel not LOS. As yet this is the only thread for LOS Ocean Moto G7 Power dev.
IronTechmonkey said:
Derp. Disregard previous mention of official build. That was Pixel not LOS. As yet this is the only thread for LOS Ocean Moto G7 Power dev.
Click to expand...
Click to collapse
Well the official one is missing some things then one I posted whit h has no problems I use it
roadkill42 said:
Well the official one is missing some things then one I posted whit h has no problems I use it
Click to expand...
Click to collapse
The post you replied to was about LOS, not TWRP, but as to TWRP, I appreciate that you shared and I know custom versions of TWRP may have important additional capability, but I would still not recommend anyone use TWRP from an unknown source. You can make it a known source by sharing a link to where it came from or to its developer.
IronTechmonkey said:
The post you replied to was about LOS, not TWRP, but as to TWRP, I appreciate that you shared and I know custom versions of TWRP may have important additional capability, but I would still not recommend anyone use TWRP from an unknown source. You can make it a known source by sharing a link to where it came from or to its developer.
Click to expand...
Click to collapse
What we use on tellagram group for moto g7 power so it's is better than the one from the official it will get this soon from what I was told believe syber hexon one who did it
roadkill42 said:
What we use on tellagram group for moto g7 power so it's is better than the one from the official it will get this soon from what I was told believe syber hexon one who did it
Click to expand...
Click to collapse
Aaaahhhh, now you are making a connection to things I know. The fact that SyberHexen worked on it would be enough for me to trust it. In any event it is still best to link to the source rather than re-post (whenever possibe) so that people may see the trail and know what they are dealing with. Perhaps you could edit the post where you shared it, to say it came from some of the same devs that work on the ROM. With a note like that I would have had no doubts. In any event, I may wait for the patch to go official and work around the issue until then but it is good to know about. Thanks again for the tip and the tweaked version of TWRP.
[EDIT] Here is a direct link to the download: https://androidfilehost.com/?fid=8889791610682939639.
IronTechmonkey said:
Device in hand, I’m doing some research before flashing so here is a question about backing up and restoring when using this ROM on G7 Power (and maybe A/B devices in general). I’ve become accustomed to (or spoiled by) being able to install ROM/Gapps/SU, backup, or restore OS and apps (boot, data, system) from TWRP using resources on the external SD without connecting to computer. Not only was that convenient but it was also good for ROM bug testing; easy to test > break > restore.
Click to expand...
Click to collapse
Yes, I actually performed my entire installation using TWRP and had all of the necessary files loaded on the external SD card. The only time (to my recollection) that a PC is necessary is to launch TWRP for the first time using Fastboot.
edit: A note of caution: Be sure to follow the "copy partitions" steps regardless. If you do not, you will brick your device. This must only be done once when you transition from stock to a custom ROM.
Greek2me said:
Yes, I actually performed my entire installation using TWRP and had all of the necessary files loaded on the external SD card. The only time (to my recollection) that a PC is necessary is to launch TWRP for the first time using Fastboot.
edit: A note of caution: Be sure to follow the "copy partitions" steps regardless. If you do not, you will brick your device. This must only be done once when you transition from stock to a custom ROM.
Click to expand...
Click to collapse
Thanks. That's the same drill I used for Moto X4 so I'm set... in that regard.
Unfortunately I did a stupid thing facilitated by Moto's dreadful documentation. Having used several devices with sim/SD tray in top right top edge, and with the in-box documentation failing to label the Mic that is now at the top right edge, I very likely damaged the mic thinking it was the tray. My fault for missing a different label for the tray but Moto made this error too easy (and their support claimed the top Mic was the proximity sensor). I will try to exchange device and start over.
does anyone know how to "relock" bootloader on this device even if that is just removing the bootloader lock warning?
IronTechmonkey said:
Thanks. That's the same drill I used for Moto X4 so I'm set... in that regard.
Unfortunately I did a stupid thing facilitated by Moto's dreadful documentation. Having used several devices with sim/SD tray in top right top edge, and with the in-box documentation failing to label the Mic that is now at the top right edge, I very likely damaged the mic thinking it was the tray. My fault for missing a different label for the tray but Moto made this error too easy (and their support claimed the top Mic was the proximity sensor). I will try to exchange device and start over.
does anyone know how to "relock" bootloader on this device even if that is just removing the bootloader lock warning?
Click to expand...
Click to collapse
Not recommended as this can really brick your device.
Just flash custom bootloader logo.bin to remove that screen
---------- Post added at 12:38 AM ---------- Previous post was at 12:37 AM ----------
I'll be making new devdb posts for official G7 ocean/channel..
once threads are active please post there.
Thx
SyberHexen said:
Not recommended as this can really brick your device.
Just flash custom bootloader logo.bin to remove that screen
Click to expand...
Click to collapse
That's what I was fishing for. There may be a chance I don't have to exchange device but if so that's what I'll do. Thanks for the coaching and for the work on Moto devices, especially the G7 Power.

Question TWRP

Hi Everyone,
Just wondering if there has been any update about custom recoveries for pixel 6. I've been checking the TWRP website and what not but there no info on the subject that I can see.
Just curious to know if anyone else has heard anything about custom recoveries yet
I asked about on one Telegram, I think that TWRP is out-of-date for newest Android version (main dev is on hiatus)
Newrooter22 said:
Hi Everyone,
Just wondering if there has been any update about custom recoveries for pixel 6. I've been checking the TWRP website and what not but there no info on the subject that I can see.
Just curious to know if anyone else has heard anything about custom recoveries yet
Click to expand...
Click to collapse
TWRP for Android 11 only came out in late 2021. It should come soon for 12. No ETAs obviously but they have a chat here: https://rebrand.ly/teamwin-recovery-zulip-community and make announcements here: https://twrp.me/
Thanks guys, it's good to know that it might still be a while away hopefully not too long. It does have some good features so fingers crossed it's sooner rather than later.
TWRP has been dead for the Pixels for over two years.
You need to learn adb and fastboot if want to mod the Pixels.
If you are lazy, you can use this program to do what TWRP can do,
📳🔥PixelFlasher for Google Pixel 6 Support Thread.
This is the support thread of PixelFlasher (PixelFlasher is an open-source self contained GUI tool to facilitate Pixel phone device flashing/rooting/updating with extra features). Note: This thread is meant for issues and problems faced in...
forum.xda-developers.com
nutzcase said:
TWRP has been dead for the Pixels for over two years.
You need to learn adb and fastboot if want to mod the Pixels.
If you are lazy, you can use this program to do what TWRP can do,
📳🔥PixelFlasher for Google Pixel 6 Support Thread.
This is the support thread of PixelFlasher (PixelFlasher is an open-source self contained GUI tool to facilitate Pixel phone device flashing/rooting/updating with extra features). Note: This thread is meant for issues and problems faced in...
forum.xda-developers.com
Click to expand...
Click to collapse
Got any recomendations for getting shell access on a phone that doesn't boot normally? That's about the only use I have for twrp, its ability to be fastboot booted without an install.
adamf663b said:
Got any recomendations for getting shell access on a phone that doesn't boot normally? That's about the only use I have for twrp, its ability to be fastboot booted without an install.
Click to expand...
Click to collapse
adb reboot bootloader
fastboot boot boot.img (I think that's the syntax but if not then fastboot help will show you)
bobbarker2 said:
adb reboot bootloader
fastboot boot boot.img (I think that's the syntax but if not then fastboot help will show you)
Click to expand...
Click to collapse
That won't help on a system that has boot issues.
there was a custom recovery ( lineage recovery i think) that came with a custom rom. i was reading about the rom a few weeks back(forget where), but the developer would not release the recovery separately.
so really there is no reason why TWRP or some other custom recovery could not be developed.
but with the lack of roms on XDA and limited custom roms elsewhere, i feel that the pixel 6 will have very very little support.
nutzfreelance said:
there was a custom recovery ( lineage recovery i think) that came with a custom rom. i was reading about the rom a few weeks back(forget where), but the developer would not release the recovery separately.
so really there is no reason why TWRP or some other custom recovery could not be developed.
but with the lack of roms on XDA and limited custom roms elsewhere, i feel that the pixel 6 will have very very little support.
Click to expand...
Click to collapse
Statixos or staticos , something like that.
nutzcase said:
TWRP has been dead for the Pixels for over two years.
You need to learn adb and fastboot if want to mod the Pixels.
If you are lazy, you can use this program to do what TWRP can do,
📳🔥PixelFlasher for Google Pixel 6 Support Thread.
This is the support thread of PixelFlasher (PixelFlasher is an open-source self contained GUI tool to facilitate Pixel phone device flashing/rooting/updating with extra features). Note: This thread is meant for issues and problems faced in...
forum.xda-developers.com
Click to expand...
Click to collapse
Only thing I ever really used it for was a nandroid
I have a question that is probably really stupid. Twrp and other custom recoveries allow installing custom roms, staticos and the like are out. How do they do it without a custom recovery?
alarmdude9 said:
I have a question that is probably really stupid. Twrp and other custom recoveries allow installing custom roms, staticos and the like are out. How do they do it without a custom recovery?
Click to expand...
Click to collapse
You push it as a zip file on fastboot. They're is dotos, deep, statixos, grapheneos, protons, crdroid etc for device
So basically bypassing the recovery altogether.
twrp lets you flash your device without needing a pc.
not to mention backup , on device formatting. amoung very many other useful tools
nutzfreelance said:
twrp lets you flash your device without needing a pc.
not to mention backup , on device formatting. amoung very many other useful tools
Click to expand...
Click to collapse
The feature I miss most is adb and having access to the decrypted file system. Decryption was always a problem for twrp; I used to unset my phone unlock method to get around that.
nutzfreelance said:
twrp lets you flash your device without needing a pc.
not to mention backup , on device formatting. amoung very many other useful tools
Click to expand...
Click to collapse
I miss having the ability to do a complegte image of your phone. Comes in handy when you get stuck in a boot loop and have to do a factory reset. Is there any other program that can do a full backup like TWRP?
I really do not see the need for a backup of andoid on the Pixel 6.
Backup your data.
There are several ways now days to restore the Pixel 6 with Android 12 and above.
adb and fastboot are your friends.
Kernel manager apps have a flash tool built into them.
vandyman said:
I really do not see the need for a backup of andoid on the Pixel 6.
Backup your data.
There are several ways now days to restore the Pixel 6 with Android 12 and above.
adb and fastboot are your friends.
Kernel manager apps have a flash tool built into them.
Click to expand...
Click to collapse
none of the ways you mention are possible with only a pixel6 and nothing else.
i cant tell you how many time when i was away for vacation or on a trip where i have flashed a rom on my S7. even a few times when some new software borked my phone and i could boot to recovery and RECOVER my device.
you can go to the custom kernel posts here and look at how many people have soft bricked their phone in April with a bad kernel. with a TWRP recovery they could have flashed a backup and never left their chair.
how can anyone say that more tools to fix things is in anyway a bad thing.
nutzfreelance said:
none of the ways you mention are possible with only a pixel6 and nothing else.
i cant tell you how many time when i was away for vacation or on a trip where i have flashed a rom on my S7. even a few times when some new software borked my phone and i could boot to recovery and RECOVER my device.
you can go to the custom kernel posts here and look at how many people have soft bricked their phone in April with a bad kernel. with a TWRP recovery they could have flashed a backup and never left their chair.
how can anyone say that more tools to fix things is in anyway a bad thing.
Click to expand...
Click to collapse
Why would you attempt to mod your cell while on vacation?
I was referring to the general user.

Categories

Resources