Related
As most of us know only certain variants of the G6 is allowed by LG I to be unlocked and then that allows us to have some fun, I've posted most links to important threads that I feel you want to view.
Any questions then just find the help thread in the stickies section.
Here's some links to what most of you will want to know.......
Guide to unlock bootloader:-
https://forum.xda-developers.com/lg-g6/how-to/official-lg-g6-bootloader-unlock-t3614719
Twrp H870 official guide and install:-
https://forum.xda-developers.com/showthread.php?t=3627595
[ROM][US997][Stock] LG-US997 13A ROM
http://forum.xda-developers.com/showthread.php?t=3635756
[ROM][US997][Stock] LG-US997 13A ROM
[ROM][H870][Stock] OPEN EU LG-H870 10L ROM twrp flashable rom
http://forum.xda-developers.com/showthread.php?t=3633452
[ROM][7.1.2_r24][H870][UNOFFICIAL][Stable] Resurrection Remix 5.8.3 [19.07.2017]
https://forum.xda-developers.com/lg-g6/development/rom-resurrection-remix-5-8-3-t3639293
Fulmics Rom for both H870+US997
https://forum.xda-developers.com/lg-g6/development/rom-25-07-fulmics-rom-1-0-v10n-tweaks-t3642043
Official lineage OS
https://forum.xda-developers.com/lg-g6/development/7-1-2r24-rom-lineageos-t3657486
Unofficial AOKP Rom
https://forum.xda-developers.com/lg-g6/development/rom-aokp-t3679189
AquariOS Rom
https://forum.xda-developers.com/lg-g6/development/rom-aquarios-7-1-2-oms-t3639363
AOSPA Paranoid Android (unofficial)
https://forum.xda-developers.com/lg-g6/development/unofficial-aospa-paranoid-android-7-2-3-t3667399
Unofficial Dirty Unicorns
https://forum.xda-developers.com/lg-g6/development/rom-dirty-unicorns-11-6-t3659943
CrDroid unofficial
https://forum.xda-developers.com/lg-g6/development/rom-dirty-unicorns-11-6-t3659943
[RECOVERY] TWRP for LG G6 US997 (unofficial)
http://forum.xda-developers.com/sho...
[RECOVERY] TWRP for LG G6 US997 (unofficial)
[MOD] KALI NETHUNTER [7.0-7.1.2][Unoffcial][H870]
http://forum.xda-developers.com/sho...] KALI NETHUNTER [7.0-7.1.2][Unoffcial][H870]
[MOD] Dual speaker mod (LG G6) (all variants)
http://forum.xda-developers.com/sho...[MOD] Dual speaker mod (LG G6) (all variants)
Root, use either magisk or SuperSU V 2.82
[BETA][2017.06.09] SuperSU v2.82 SR1
http://forum.xda-developers.com/showthread.php?t=2868133
[2017.7.11] Magisk v13.1 - Root & Universal Systemless Interface [Android 5.0+]
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Hi, as you are all aware some of us are lucky enough to unlock our bootloaders and flash custom firmwares/twrp, however many guides tell us how to do that but none tell you how to go back total stock+locked.
I've personally seen a few bricked phones as not doing it correctly or flashing on a locked bootloader which can cause BIG problems, here I'll help with a small but useful guide and simple steps I made to return stock.
**PLEASE NOTE THIS GUIDE IS FOR H870/US997**
I'm not 100% certain on how to revert changes on H872 but once I do I will add.
Now for this your going to need
1) stock unrooted zip for twrp
2) twrp installed
3) a pc
4) LG up/uppercut or bridge
5)stock recovery image
6) about 25-30 mins spare time
Step 1)Firstly your going to want to download stock zip from which can be found here
https://forum-xda--developers-com.c...ment/rom-op-il-lg-h870-11d-rom-t3711191/page1
, I recommendcyou copy to an external SD card for this.
Step 2) Next download stock recovery IMG from here
http://downloads.codefi.re/autoprime/LG/LG_G6/H870/H87010f
( same I used) and again copy to external SD card.
Step 3) Once you've done that reboot into twrp, then perform a factory reset and install the stock zip. Once that's installed **DO NOT INSTALL ANY ROOT ** reboot your device, skip though the setup and go right to settings, and click on build number to open developer settings and check to make sure ENABLE OEM UNLOCK is selected. If it is then reboot back to twrp via button combo.
Step 4) Once in twrp select install and select image instead of zip, then find and install stock recovery image and reboot recovery, now you should have stock recovery so it should perform a factory reset, if it does then reboot again ( it's a good way to make sure everything is ok) and if it boots fine then connect to PC,( you can if you wish skip step 3 and go right to step 4)
Step 5) Open up your lgup/uppercut/bridge (preferred choice), if LG up/uppercut then you need the latest kdz file downloaded to your pc, if bridge it detects your phone and should inform if it needs an update, if it does then allow the update to latest.
If not and your device is on and fully working then ONLY NOW can you use adb to reboot fastboot and enter "fastboot OEM lock", doing so will once again erase your device but now it's full stock and locked like you never touched it.
1 note I must add is NEVER EVER flash anything via fastboot is your device is locked as it will brick your phone. Your greeted with either of the screens below
Reserved
Sent from my LG-h870 using XDA-Developers Legacy app
Reserved 2
Sent from my LG-h870 using XDA-Developers Legacy app
new add
[ROM][H870][Stock] OPEN EU LG-H870 11G ROM
Update 1, most used and updated ROMs here
https://g6-community.org/
Good, guides for newbie are always a good thing here, just wanted to report that flashing stock recovery it's a useless passage if you flash the kdz trough lgup because it will overwrite TWRP anyway, another useless passage (only if already coming from stock firmware or rom based on it) is to flash a stock rom from twrp, LGUp does all the necessary after
Thanks for your efforts, as I said before this is really a good idea and imho it'll prevent useless threads and bricks =)
jimbomodder said:
Step 2) Next download stock recovery IMG from here
http://downloads.codefi.re/autoprime/LG/LG_G6/H870/H87010f
( same I used) and again copy to external SD card.
Click to expand...
Click to collapse
That'd be the "recovery.img 23.6 MB May-30-17", right?
Great guides, thank you!
DrNO[PL said:
;80381567]That'd be the "recovery.img 23.6 MB May-30-17", right?
Great guides, thank you!
Click to expand...
Click to collapse
Yeah, should not matter about date
About this project
This project provides repackaged Stock Oreo roms that can be flashed by TWRP. Modifications from stock are listed below.
As we are now moving into the Oreo world, I've decided that now is a good time to make a few changes to how things were done previously with Nougat. Please pay attention to the next few sections.
Modifications from stock
Note - It seems that I can't get DM-verity nor forced encryption disabled. The location of the fstab.qcom file is no longer in the Boot image. I found a similar file in the system image, but changing that appears to have had no effect. In order to disable these, use Magisk. UPDATE - Resolved since soak test 2, and soak test 1 with Aroma installer
DM-verity is disabled
Forced encryption of the data partition is disabled. It is still possible to encrypt the partition if you wish (optional with Aroma installer)
The partition table and boot loader are not included, which makes it safer to up/down-grade.
Do not attempt to apply standard OTAs over these builds. They'll probably fail, worst case they will brick your phone
Differences from previous Nougat builds
These roms are suitable for all channels. Previously there was separate firmware for different regions (e.g. retin had a separate build from retus), but as a general rule you are safe with any region's firmware.
I have now started using the Aroma installer for Oreo builds. Some of the below is now customisable at install time. Aroma installer zips will have "-aroma" in their filename.
The modified boot logo will no longer be included in the rom download. A separate zip will be provided to just flash the modified logo.
EFS will be erased on install! If your persist is intact, EFS will recreate itself. With the amount of exposure that the lost IMEI issue has had, all should be very familiar with the importance of backing up persist and EFS. And those that have had a compromised persist, will know that they should be hanging on to their EFS backups for dear life. Full details of the issue and solution (for those with intact persist) is here: Fix Persist, resolve IMEI=0, Volte, 4G, Explanation, Requirements From my perspective, the EFS is erased installing OTAs for a reason. I don't know what it is myself, but the folks at Motorola build it into their OTAs and they know far better than I do.
As a mitigation to the risk of people forgetting/losing their EFS and / or Persist backups, I will have a very crude backup system integrated into the zips. However, it will take some skill / knowledge to restore from these backups, and they should not be relied upon over the long term. Refer to the second post for more details.
Important information if downgrading to Nougat and Custom Oreo roms
The Oreo roms will change the ownership of specific files and folders in the /persist folder. As a result of this, stock Nougat will have issues such as lost IMEI, no Volte, no 4G, etc. In order to overcome these issues, either follow the instructions in the link above, or flash the following zip in TWRP.
potter-stock-persist-fix.zip
Additionally, the latest Nougat builds with the Aroma installer will apply the persist fix when installed.
Another potential issue is that, as a result of various partitions being updated, the new Oreo blobs may not be compatible with existing Nougat roms (stock or custom), or even current Custom Oreo roms. This may result in issues such as the fingerprint reader not working, etc.
UPDATE: Some custom roms are now using the Oreo blobs. However, if you require the older Nougat blobs, you can downgrade through one of the following methods:
1) install one of the latest Stock Nougat TWRP flashables. This will ensure that all affected partitions are compatible with Stock Nougat and Custom Oreo roms. You can get these from this thread here:
[Nougat][Stock][Rom] TWRP Flashable Stock Builds
2) install one of the firmware-only zips from the below folders. Note that if this results in other odd behaviour, you may need to install and boot into a full stock Nougat firmware as above. The main benefit of these zips is that they are much smaller, ~50MB rather than ~1.4GB.
https://www.androidfilehost.com/?w=files&flid=273039
potter-firmware-92-14.zip is for retin, retla, retbr
potter-firmware-93-14.zip is for retus, retapac, reteu
Out of respect for the purpose of this thread, please keep questions about whether or not to use Nougat or Oreo firmware for particular custom ROMs in the thread for the custom ROM you are trying to use. I do not support other custom ROMs - the maintainers of those custom ROMs should provide guidance.
Usage
Steps to flash
Ensure you have the latest TWRP
Download an appropriate zip from one of the links below
Copy to the phone or SD card
BACKUP YOUR DATA, INCLUDING EFS AND PERSIST
Flash the zip via TWRP
Optionally flash Magisk etc - NOTE - in order to disable dm-verity and forced encryption you must flash magisk before rebooting Resolved since Soak Test 2 and Soak Test 1 Aroma installer, Magisk is optional
Reboot
Profit?
How you can help with new builds
If your phone gets an OTA notification for a build that has not been released, please pull it and share it in this thread:
When the notification is received, allow your phone to download the OTA
Power off and boot into recovery
Go to Advanced -> File Manager
Navigate to /cache
There will be a file Blur_Version_x.y.z.potter.blah.zip - Note - Oreo OTAs may not be named this way, they may be named according to the version of the rom that is currently installed
Copy it to internal storage or the sdcard
Copy to PC (optional)
Upload to Mega, Google Drive, wherever
Share the link
You can also remove the file from the /cache folder to prevent any auto-updates from happening.
Latest versions
The 85-13 series is released to most channels except retus, and the last update was to 85-17-2.
The 85-17 series is released to the retus channel.
However, all releases can be used with all channels.
Official Oreo OPSS28.85-17-6-2 (Oreo 8.1, 1 February 2019 security patches) - Aroma Installer
Android File Host - potter-twrp-flashable-OPSS28.85-17-6-2-aroma.zip
Official Oreo OPSS28.85-17-6 (Oreo 8.1, 1 February 2019 security patches) - Aroma Installer
Android File Host - potter-twrp-flashable-OPSS28.85-17-6-aroma.zip
All versions that I have created will be placed in this folder (or the Archive sub-folder) at Android File Host:
Android File Host - Potter TWRP Flashable Stock Oreo
Modified Boot Logo
Optional, only needs to be flashed once. Replaces the warning screen with the standard logo. Can't hide the N/A. If you want to hide the N/A, go to the themes forum.
potter-logo.zip
Kernel Sources
Kernel sources are provided by Motorola:
https://github.com/MotorolaMobilityLLC/kernel-msm/
XDA:DevDB Information
Potter Oreo TWRP Flashable, ROM for the Moto G5 Plus
Contributors
NZedPred
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.x
Version Information
Status: Stable
Created 2018-08-17
Last Updated 2019-12-28
FAQs
Frequently Asked Questions
What is the 'very crude backup system integrated into the zips'?
This is a script that is run at the start of the install. It's purpose is very simple - it creates "dd backups" (i.e. bit-perfect images) of the modemst1/2 and persist partitions. They are stored in your sdcard as "backup_yyyymmddHHMMSS_modemst1.img", etc., where yyyymmddHHMMSS represents the date and time the script was run.
For this to work, your data partition must be mounted. I haven't included any checks for this (I'm not really a shell script person - it would take me hours to get this sort of thing right) - this is what puts the "crude" in "very crude backup system". UPDATE - the aroma installers now check that data is mounted, and abort the install if not. Most of the time the data partition will be mounted in TWRP, so this will work 99% of the time. Caution should still be applied, and you should still copy these or any other backups to cloud storage to be safe.
OK, so if I needed to use these backups, how do I restore them?
To restore these, you will have to reboot into TWRP and open up a shell or use adb. The commands to restore each partition are as follows (replacing yyyymmddHHMMSS with the appropriate values of course):
Code:
dd if=/sdcard/backup_yyyymmddHHMMSS_modemst1.img of=/dev/block/bootdevice/by-name/modemst1
dd if=/sdcard/backup_yyyymmddHHMMSS_modemst2.img of=/dev/block/bootdevice/by-name/modemst2
dd if=/sdcard/backup_yyyymmddHHMMSS_persist.img of=/dev/block/bootdevice/by-name/persist
Note that these commands are very powerful, and applied incorrectly can result in you bricking your phone if you overwrite the wrong partition.
So are dm-verity and forced encryption now not able to be disabled?
OK some history... Nougat had fstab (file system table) in the boot image. So in those days, I would open up the image, and edit the fstab.qcom file, do the appropriate changes, repack the boot image, and all is fine.
Now, under Oreo, the fstab file is not in the boot image, it's under /system/vendor/etc/fstab.qcom or similar. Editing that file appears to have no effect. For now, Magisk is the easiest way of disabling both, but you must make sure to install it immediately after installing the rom and before rebooting.
Update - this is now resolved in the second Oreo soak test download. dm-verity is still disabled in the boot image, but a completely different way. Once this is done, disabling forced encryption works as expected.
Which partitions are modified?
The short of it is this - boot, system and 'firmware'-related partitions. None of the bootloader partitions are updated. The full list of partitions that are written is:
modem
fsg
dsp
boot
system
oem
Note that this list applies to the Nougat and Oreo flashable zips.
TWRP is no longer installed after flashing this
I believe this is related to dm-verity (see above). You will have to first reinstall TWRP via fastboot. When TWRP is back, install magisk immediately after installing the rom, and before rebooting.
I'm having problems with an Oreo custom rom after installing this rom, what can I do?
Refer to the OP, the section about downgrading to Nougat - the same approach applies. Oreo Custom roms will have been based upon the available Nougat blobs that were available. As the blobs have been updated in the Oreo release, the issue is that they are not compatible. So install a full TWRP Nougat zip and then install your Oreo Custom rom.
Dirty or clean flash?
I did a dirty flash, as I came from the latest Nougat stock rom. Keep in mind that this is nothing more than the OTA applied to the previous Nougat build and packaged into a TWRP zip. So, as long as you have come from (the latest) Stock Nougat, you should be able to dirty flash, as that would be the use-case for the OTA. If you were on another rom, clean flash required.
Once you are on one of these builds, you can dirty flash subsequent builds. Again, this would be just like flashing one OTA after the other. Also note that these builds are complete in their own right, you don't need to incrementally flash - you can flash the latest to get the full install.
My device was encrypted, and I really need to decrypt it. How can I do this?
Sorry, but the only way is to format the data partition. That means you will need to backup your data, and your internal storage as well (/sdcard). After backing up, use TWRP to format the partition. From the TWRP main menu, select Wipe > Format Data. Then follow the on-screen instructions.
Is it 32 bit or 64 bit
32 bit. We've known this would be the case for a long time.
How can I create flashable zips myself?
I created the guide below, and it has been updated for Oreo. A word of warning, it is not for the faint of heart. You will need to have a good understanding of the Linux command line, and be able to understand the techniques that are being taught, rather than expecting that the process is a 'step-by-step'. Adaptability is key here.
[GUIDE] Creating TWRP Flashbale Stock roms
What are the new Aroma zips?
The aroma zips use the Aroma installer. Some of you may have seen the Aroma installer for Open Gapps. The key here is that I, as the packager, can build in selection options into the installer. It's all available as a nice GUI for the users to pick and choose from the options I've provided. Here are the options that are available:
Do backups - does the backups as mentioned earlier in the FAQs.
Erase EFS - erases modemst1 and modemst2, as described in the first post. Also DDR is erased, but I'm not sure what purpose that has but it may as well go together with these.
Install Firmware - installs the following partitions - modem, fsg, dsp; each of these has something to do with hardware / connectivity.
Install System - Installs the following partitions - boot, system, oem.
Apply patches - as long as Install System is selected, will install the patched boot image with dm-verity disabled, and will edit the fstab (filesystem table) to disable forced encryption.
On soak test 2 or later, I have my IMEI but no signal. What can I do?
In all cases where this has happened, the user's phone has relied upon an EFS backup for IMEI, due to flashing another persist. In these cases, it appears that the only way to get a signal is to use the firmware (i.e. modem, fsg, dsp - refer previous FAQ) from soak test 1. We're probably seeing here that the EFS does in fact need to be recreated to be valid. Unfortunately for these users, by not having their own persist, they are stuck with an old EFS and the newer firmwares appear to not work.
To do this
if you are already on Soak Test 2 or later, download the Soak Test 1 firmware download at either of these links:
Android File Host - oreo-soak1-firmware.zip
Dropbox - oreo-soak1-firmware.zip
If you are on Soak Test 1, install Soak Test 2 or later / official aroma installer and de-select firmware
My fingerprint is not working on my custom ROM
Refer to the thread for your custom ROM, and ask questions there. In short, Nougat and Oreo firmware are not compatible with each other. Many custom ROMs are now using Oreo firmware, whereas previously (before October 2018) pretty much all custom ROMs were using Nougat firmware. It's messy now, but please ask the questions in the right place (which is NOT this thread).
My touchscreen isn't working after flashing, even within TWRP
This seems to happen somewhat rarely, although I don't know what the cause is. As it affects TWRP as well, and TWRP uses the 'modem' partition for getting its firmware blobs, I guess it's possible that this particular partition is getting a conflicting modification whilst flashing, which is causing problems (but this is purely speculation on my part).
To solve, fastboot flashing the stock ROM appears to work. It may also be possible whilst in TWRP to manually flash the partitions via ADB, but that takes a bit of work and knowledge. Until someone can truly work out what's happening and the minimum required to fix it, stick with fastboot.
Update - refer to post #3 for the latest information about this issue.
Touch screen unresponsive even in TWRP
The below post has the latest information on the Touch Screen Unresponsive issue
Likely Cause
From the testing that I've done to reproduce the issue, as far as I can tell the issue is that Stock Oreo is not able to be safely applied over the top of old builds of Stock Nougat. Furthermore, it doesn't seem to matter if you were on Custom ROMs after you were last on Stock Nougat, just what Stock Nougat build you were on last.
Avoiding the Issue
Again the key here is what build of Stock you were on last (and I guess booted into). So, if you were never on Stock Oreo, and you aren't sure what version of Stock Nougat you were on last, then the safest path to getting these builds working is to first flash the latest Nougat Stock ROM.
Get the latest from this thread: [Nougat][Stock][Rom] TWRP Flashable Stock Builds
Once you have flashed the latest Nougat, boot once to make sure everything is working. After that, you should be able to safely upgrade to Oreo.
Fixing the Issue
If you have been affected by the issue, most people have been able to get back the touch screen functionality by flashing a fastboot version of the ROM. However, as long as you have a PC handy you will be able to flash using TWRP as well via adb, using the steps detailed below. A third option is to connect a USB Mouse via an USB OTG adapter.
Note that for either method via TWRP, you cannot use the versions of the ROM with the Aroma installer, as the mouse is not supported within, and there is no way of providing input by adb.
Downloads
The 92-14 or 93-14 versions should be suitable. They are in these links (these do not erase EFS, so for the paranoid, you will retain your IMEI):
twrp-flashable-potter-NPNS25.137-92-14-no-erase-modemst.zip
twrp-flashable-potter-NPNS25.137-93-14-no-erase-modemst.zip
TWRP Commands
Once in TWRP, connect your USB cable. To copy the downloaded file into your internal storage (adapt the filename for the version you downloaded):
Code:
adb push twrp-flashable-potter-NPNS25.137-92-14-no-erase-modemst.zip /sdcard/
If you want to backup, you can do this via the command line as well. I haven't tested this myself, but the commands are available here: https://www.pocketables.com/2014/10/using-twrps-new-adb-interface.html
The example provided uses the following to back up system, data and boot, and compress:
Code:
adb shell twrp backup SDBOM
You will need to do a clean flash, so these commands will wipe data / factory reset and then install
Code:
adb shell
twrp wipe data
twrp install /sdcard/twrp-flashable-potter-NPNS25.137-92-14-no-erase-modemst.zip
reboot
After the reboot, you should have your touch screen functionality back. Then reboot to recovery, and install Oreo as normal. If for any reason the Oreo flash doesn't work, try the steps again, but rather than installing the latest Oreo, install an earlier one.
Awesome bro...
You Rock...
you even included auto backup of efs and persist ... wow thats very thoughtfull and nice of you...
hatsoff..
:good::good:
Thanks dude, downloading
Edit: working like a charm, again thanks.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks for uploading. Two questions though...
1. which one would be suitable for retin? (India)
2. Are there any bugs?
working for retin also thnx
Question: I'd like to flash this, but I'm planning to roll back in the future to take the OTA back up to O. If I restore nougat system, boot, persist, recovery, oem will that still be possible? I see some other stuff in the zip like adspo.bin, fsg.mbn, and modem. Not sure if those it lead to OTA failures or a brick.
also, nice job on the persist/efs script!
Worked on retin also thanks. Great work!!!!
I'm pretty sure forced encryption of the data partition is still enabled.
pfonck said:
I think forced encryption of the data partition is still enabled (formatting the data partition in TWRP does not help).
Click to expand...
Click to collapse
If that's the case magisk is probably needed to turn it off. Sorry, but I've only tested it with magisk installed. Moto have changed the fstab location, I thought I got it but maybe it's cosmetic and doesn't do anything. Will update OP when I get a chance.
NZedPred said:
If that's the case magisk is probably needed to turn it off. Sorry, but I've only tested it with magisk installed. Moto have changed the fstab location, I thought I got it but maybe it's cosmetic and doesn't do anything. Will update OP when I get a chance.
Click to expand...
Click to collapse
Yes, when you do;
rom installation > format data > flash magisk
everything is okay
verified.
Did Moto make Oreo 64bit?
redbeard1083 said:
Question: I'd like to flash this, but I'm planning to roll back in the future to take the OTA back up to O. If I restore nougat system, boot, persist, recovery, oem will that still be possible? I see some other stuff in the zip like adspo.bin, fsg.mbn, and modem. Not sure if those it lead to OTA failures or a brick.
also, nice job on the persist/efs script!
Click to expand...
Click to collapse
Good question, and this is something that I needed to consider before doing this, in case everyone installed this and we'd have no path to get to official Oreo.
Refer to the section in the OP "Important information if downgrading to Nougat". Basically you need to follow all of that to be able to get notification of the OTAs. Once the official public Oreo OTA is available, I will then put together a zip based upon the pre-requisite nougat rom with the official Oreo OTA.
I also believe that one or both of the 1 July 2018 and/or 1 August 2018 patches were announced, but neither were for Oreo. I do intend to keep Nougat up to date as well in its thread.
NZedPred said:
Good question, and this is something that I needed to consider before doing this, in case everyone installed this and we'd have no path to get to official Oreo.
Refer to the section in the OP "Important information if downgrading to Nougat". Basically you need to follow all of that to be able to get notification of the OTAs. Once the official public Oreo OTA is available, I will then put together a zip based upon the pre-requisite nougat rom with the official Oreo OTA.
I also believe that one or both of the 1 July 2018 and/or 1 August 2018 patches were announced, but neither were for Oreo. I do intend to keep Nougat up to date as well in its thread.
Click to expand...
Click to collapse
How did a recovery come in? with volume - and power enters and I say without command
JC Pzy said:
How did a recovery come in? with volume - and power enters and I say without command
Click to expand...
Click to collapse
I've only just added something to the FAQ (post 2) that covers this. Sorry, it was unexpected and didn't come up when I was testing as I always had magisk installed. Follow these steps:
TWRP is no longer installed after flashing this
I believe this is related to dm-verity (see above). You will have to first reinstall TWRP via fastboot. When TWRP is back, install magisk immediately after installing the rom, and before rebooting.
NZedPred said:
I've only just added something to the FAQ (post 2) that covers this. Sorry, it was unexpected and didn't come up when I was testing as I always had magisk installed. Follow these steps:
TWRP is no longer installed after flashing this
I believe this is related to dm-verity (see above). You will have to first reinstall TWRP via fastboot. When TWRP is back, install magisk immediately after installing the rom, and before rebooting.
Click to expand...
Click to collapse
I do not have a PC to reinstall the recovery
NZedPred said:
Good question, and this is something that I needed to consider before doing this, in case everyone installed this and we'd have no path to get to official Oreo.
Refer to the section in the OP "Important information if downgrading to Nougat". Basically you need to follow all of that to be able to get notification of the OTAs. Once the official public Oreo OTA is available, I will then put together a zip based upon the pre-requisite nougat rom with the official Oreo OTA.
I also believe that one or both of the 1 July 2018 and/or 1 August 2018 patches were announced, but neither were for Oreo. I do intend to keep Nougat up to date as well in its thread.
Click to expand...
Click to collapse
Maybe I'll try tweaking the zip to see if we can run it without the stuff we can't easily backup/restore with twrp. I'll take a stab at it shortly and let you know what happens if we flash just system, boot, and OEM.
redbeard1083 said:
Maybe I'll try tweaking the zip to see if we can run it without the stuff we can't easily backup/restore with twrp. I'll take a stab at it shortly and let you know what happens if we flash just system, boot, and OEM.
Click to expand...
Click to collapse
You can give it a go, but I've already done some very brief testing. Using the Nougat modem partition on the Oreo system results in things like 3G only, fingerprint not working.
JC Pzy said:
I do not have a PC to reinstall the recovery
Click to expand...
Click to collapse
I'm guessing you don't have root either? If you did, you could try installing it from a shell from within the rom:
Code:
su
dd if=/path/to/twrp.img of=/dev/block/bootdevice/by-name/recovery
Simple way to install TWRP on Moto G6 plus!!
1. download the twrp-installer.zip
2. boot in TWRP via fastboot boot twrp.img
3. flash twrp-installer.zip to overwrite stock recovery
4. flash the magisk.zip because step 3. will patch your boot.img
5. it's done! you can start TWRP easily like on A-only-slot devices
Works perfect for my Moto G6 plus rooted with magisk!!
How did you prepare this?
Do you also have flashable .img of TWRP for G6 Plus?
segra246x said:
Simple way to install TWRP on Moto G6 plus!!
1. download the twrp-installer.zip
2. boot in TWRP via fastboot boot twrp.img
3. flash twrp-installer.zip to overwrite stock recovery
4. flash the magisk.zip because step 3. will patch your boot.img
5. it's done! you can start TWRP easily like on A-only-slot devices
Works perfect for my Moto G6 plus rooted with magisk!!
Click to expand...
Click to collapse
Simple Great!
For me adb sideload dont work, even when i type "adb devices" or "sudo adb devices" just appear "no devices/emulators detected" but when I use twrp via "sudo fastboot boot twrp.img" all works propertly. Although i type adb kill-server and sudo adb start-server no fix that than in the another method it works. I think maybe is for version (3.2.3-0) works and in your (3.2.1-0) dont (?) or Is by in one Is installed on the devices and the another not (?)
Thanks in advance for an posible solution. Grettings from México
Many thanks in advance segra246x.
Unfortunately for me, every time I´ve flashed TWRP, then I do not know what may i do to reboot the phone. My phone is unlocked and I am root with Magisk, so I do not know which boot should I flash at the end, so that it starts again and does not stay in a loop with TWRP or in brick.
Couls you tell wich procedure are you using to can start the device normally?
i flashed patched boot image, Should i flash boot patched boot image and re-start again Magisck instalation? Should i flash boot boot.image from the regarding stocke version without loosing root satus?
Thank you, the twrp works fine installed with stock Oreo 8.0.
Worked on G6+ with Pie. Thank you!
thump said:
Worked on G6+ with Pie. Thank you!
Click to expand...
Click to collapse
Please explain your process & is it still working? What version are you on with 9.0?
---------- Post added at 10:04 PM ---------- Previous post was at 10:00 PM ----------
thump said:
Worked on G6+ with Pie. Thank you!
Click to expand...
Click to collapse
segra246x said:
Simple way to install TWRP on Moto G6 plus!!
1. download the twrp-installer.zip
2. boot in TWRP via fastboot boot twrp.img
3. flash twrp-installer.zip to overwrite stock recovery
4. flash the magisk.zip because step 3. will patch your boot.img
5. it's done! you can start TWRP easily like on A-only-slot devices
Works perfect for my Moto G6 plus rooted with magisk!!
Click to expand...
Click to collapse
This method still working for you?? And I don't see any credits so did you create this installer??
I used the exact file and the 5 step method outlined in the original post.
Hey did you create this?
segra246x said:
Simple way to install TWRP on Moto G6 plus!!
1. download the twrp-installer.zip
2. boot in TWRP via fastboot boot twrp.img
3. flash twrp-installer.zip to overwrite stock recovery
4. flash the magisk.zip because step 3. will patch your boot.img
5. it's done! you can start TWRP easily like on A-only-slot devices
Works perfect for my Moto G6 plus rooed with magisk!!
Click to expand...
Click to collapse
I can't find any credits.
---------- Post added at 08:11 AM ---------- Previous post was at 08:02 AM ----------
segra246x said:
Simple way to install TWRP on Moto G6 plus!!
1. download the twrp-installer.zip
2. boot in TWRP via fastboot boot twrp.img
3. flash twrp-installer.zip to overwrite stock recovery
4. flash the magisk.zip because step 3. will patch your boot.img
5. it's done! you can start TWRP easily like on A-only-slot devices
Works perfect for my Moto G6 plus rooted with magisk!!
Click to expand...
Click to collapse
**I noticed that you have not been logged in here for
about a month. When you get back please inform me.
I have an error to flash the twrp, how did you do it?
Instructions..
HorryStorm said:
I have an error to flash the twrp, how did you do it?
Click to expand...
Click to collapse
Follow the directions. Couldn't be more simple.
First use our official TWRP 3-2-3-0 to BOOT into
There you flash this installer.
I have used this installer and can say it's good.
MPT works.. you can then reboot to recovery at
Anytime. Hope that's helpful. Good luck.
--Ken
the question is that when I try to make the flash it appears a maximum size error.
This is only for Moto G6 Plus. If that's your device
Then idk. I've installed it several times and never had
An issue.
Ok, thanks.
I dont have OS Pie9 after flashing twrp
My step was,
1. flashing Pie9 with cmd in fastboot
2. then i boot in twrp.img and install zip twrp ...
---------- Post added at 01:29 PM ---------- Previous post was at 01:10 PM ----------
lavriiga said:
My step was,
1. flashing Pie9 with cmd in fastboot
2. then i boot in twrp.img and install zip twrp ...
Click to expand...
Click to collapse
I fix it, First i flash PIE 9.0
Then i boot in twrp.img in fastboot
Then zip TWRP.zip and after that i install MAGISK 17.1 And it works ! Thanks for posts !!!:good::laugh::laugh::laugh:
Secure Startup Password
First off thank you segra246x for making this. I had no problem following the instructions and got TWRP installed with no issue. I have also been able to successfully flash a bunch of different Pie GSIs (phhTreble, AOSP Extended) successfully.
I do however have a question that I cannot seem to find the answer too anywhere for the Moto G6 Plus. On past devices (i.e. Moto G5 Plus) I was able to configure the device to require a password or pin or pattern before the device would boot. Similarly TWRP would require this in order to mount /data. Depending on where you are looking online this could be called Secure Boot or Secure Startup. On this device however I cannot find the option when I set the password with any version of Android to require the boot password. This means that all it takes to decrypt and copy my data partition is a hard reset into recovery.
I have done a fair bit of research into this to see if I was just missing a step or a missed step with no luck. I saw some posts from Motorolla / Lenovo that indicate this is no longer an option, I will post links below for the interested. I also saw a Moto G6 post talking about having to format, reboot into recovery, format again to get the decryption to work. I knew that it would be long shot but I gave this a try just in case but it did not help.
Does anyone have any information about this device, TWRP and secure boot? I know that decrypting /data in TWRP can be difficult but if I had to choose I would rather data partition is never mountable by TWRP over mountable with no password. Any information would be greatly appreciated. Thanks.
Motorolla Post indicating that Moto G6 Plus uses direct boot instead of secure boot
https://forums.lenovo.com/t5/Moto-G6-Moto-G6-Plus-Moto-G6/G6-Plus-can-t-find-Secure-Startup/m-p/4311477
Motorolla Post indicating this is new encryption method
https://support.motorola.com/uk/en/solution/MS129140
roomfool said:
First off thank you segra246x for making this. I had no problem following the instructions and got TWRP installed with no issue. I have also been able to successfully flash a bunch of different Pie GSIs (phhTreble, AOSP Extended) successfully.
I do however have a question that I cannot seem to find the answer too anywhere for the Moto G6 Plus. On past devices (i.e. Moto G5 Plus) I was able to configure the device to require a password or pin or pattern before the device would boot. Similarly TWRP would require this in order to mount /data. Depending on where you are looking online this could be called Secure Boot or Secure Startup. On this device however I cannot find the option when I set the password with any version of Android to require the boot password. This means that all it takes to decrypt and copy my data partition is a hard reset into recovery.
I have done a fair bit of research into this to see if I was just missing a step or a missed step with no luck. I saw some posts from Motorolla / Lenovo that indicate this is no longer an option, I will post links below for the interested. I also saw a Moto G6 post talking about having to format, reboot into recovery, format again to get the decryption to work. I knew that it would be long shot but I gave this a try just in case but it did not help.
Does anyone have any information about this device, TWRP and secure boot? I know that decrypting /data in TWRP can be difficult but if I had to choose I would rather data partition is never mountable by TWRP over mountable with no password. Any information would be greatly appreciated. Thanks.
Motorolla Post indicating that Moto G6 Plus uses direct boot instead of secure boot
https://forums.lenovo.com/t5/Moto-G...G6-Plus-can-t-find-Secure-Startup/m-p/4311477
Motorolla Post indicating this is new encryption method
https://support.motorola.com/uk/en/solution/MS129140
Click to expand...
Click to collapse
Hi, this has to do with the rom I think. I had LineageOS 15.1 installed and I had to decrypt the data with my password before I could do anything in twrp. I currently have the option to encrypt my phone on HavocOS under the security tab, but it doesn't work for now =))). On LOS15.1 it was enabled by default, so give it a try if this concerns you so much.
Thanks
randomanonymousname said:
Hi, this has to do with the rom I think. I had LineageOS 15.1 installed and I had to decrypt the data with my password before I could do anything in twrp. I currently have the option to encrypt my phone on HavocOS under the security tab, but it doesn't work for now =))). On LOS15.1 it was enabled by default, so give it a try if this concerns you so much.
Click to expand...
Click to collapse
OK I was not sure if this was more related to the ROM or TWRP, my bad for posting in the wrong place. I have tried the AOSPExtended 9 ROM and all 3 flavors of the phh treble 9 ROM with the same result. Have not had any luck installing Lineage or any of the 8.1 phh treble ROMs. I will keep digging to see if I can't find some info about this. Thanks.
Hi, my backups get stuck at 80-90% sometimes, does anyone have the same issue?
Hello! i have used the search tool to see if there is a custom recovery for my device but i am unable to find any. I found TB-X103F custom twrp but im unsure about trying it!.
I may be rather early as this tablet only recently came out.
Lenovo X 104F- 1 GB RAM
I own the same tablet , found also a solution to root it . Just to try other Custom ROMs you do not need to root it ....it is project TREBLE compatible ! This means that you can , with fastboot and ADB , install various GSI images )
ATTENTION : this method does not allow you to go back easily to the factory ROM !!! If you wish to do so, you need to root your Tab and make a full backup with one of the solutions described here in XDA ! Titanium or so .
I have installed Lineage 15 (Oreo 8) on my device and it runs without any problem ......Custom ROMs based on Pie make still some issues ! Be aware , that for one or other reason on my tablet i can install only ROM that is less than 1 GB after unzip !!!
Artarun said:
I own the same tablet , found also a solution to root it . Just to try other Custom ROMs you do not need to root it ....it is project TREBLE compatible ! This means that you can , with fastboot and ADB , install various GSI images )
ATTENTION : this method does not allow you to go back easily to the factory ROM !!! If you wish to do so, you need to root your Tab and make a full backup with one of the solutions described here in XDA ! Titanium or so .
I have installed Lineage 15 (Oreo 8) on my device and it runs without any problem ......Custom ROMs based on Pie make still some issues ! Be aware , that for one or other reason on my tablet i can install only ROM that is less than 1 GB after unzip !!!
Click to expand...
Click to collapse
Care to share any links?
Since Lenovo/Motorola added our E10 / TB-X104F to the recovery tool I decided to play around with hacking apart this awesome and terrible table. Long-story-short... you can unlock it using the normal FASTBOOT commands. A MAGISK modified BOOT.IMG does work which gave me full root access to the tablet. If people are interested I'll write up a guide... but a little bit of research on MAGISK and grabbing the Lenovo recovery tool will be your first step if starting from scratch.
Next step is getting a recovery image. I'm currently looking into getting this tablet into the TWRP BUILDER queue, but at the time of this writing their queue is full.
UPDATE: Just saw the TWRP BUILDER team has had everything on hold for over a month now. Guess I'll need to see about building this locally in my free time.
kpfx said:
Since Lenovo/Motorola added our E10 / TB-X104F to the recovery tool I decided to play around with hacking apart this awesome and terrible table. Long-story-short... you can unlock it using the normal FASTBOOT commands. A MAGISK modified BOOT.IMG does work which gave me full root access to the tablet. If people are interested I'll write up a guide... but a little bit of research on MAGISK and grabbing the Lenovo recovery tool will be your first step if starting from scratch.
Next step is getting a recovery image. I'm currently looking into getting this tablet into the TWRP BUILDER queue, but at the time of this writing their queue is full.
UPDATE: Just saw the TWRP BUILDER team has had everything on hold for over a month now. Guess I'll need to see about building this locally in my free time.
Click to expand...
Click to collapse
I've been looking for one also and was gonna see about working on one
Artarun said:
I own the same tablet , found also a solution to root it . Just to try other Custom ROMs you do not need to root it ....it is project TREBLE compatible ! This means that you can , with fastboot and ADB , install various GSI images )
ATTENTION : this method does not allow you to go back easily to the factory ROM !!! If you wish to do so, you need to root your Tab and make a full backup with one of the solutions described here in XDA ! Titanium or so .
I have installed Lineage 15 (Oreo 8) on my device and it runs without any problem ......Custom ROMs based on Pie make still some issues ! Be aware , that for one or other reason on my tablet i can install only ROM that is less than 1 GB after unzip !!!
Click to expand...
Click to collapse
I can attest to this, I flashed the last Resurrection Remix Oreo GSI (12/21/18) and a (Magisk) rooted kernal I got from firmware (Lenovo MOTO Smart Assistant). And so far everything seems to be working fine.
So I also flashed resurrection remix pie gsi... it works as well... only thing is it doesn't come with gapps... and without twrp i can't flash a gapps package. The resurrection remix I used was the final oreo build... zt has gapps pre-installed... you have to register the device with google because it is not certified... but after that everything seem good. One thing to mention is both the oreo and pie builds are "go edition" so some features are missing because of that... one in particular I noticed is notification access for 3rd party apps... go edition devices don't have that feature
Do either of you all have a step-by-step guide to rooting the device and installing either the Lineage or RR ROM?
Also, what works and what doesn't on the tablet afterwards?
44Guest said:
Do either of you all have a step-by-step guide to rooting the device and installing either the Lineage or RR ROM?
Also, what works and what doesn't on the tablet afterwards?
Click to expand...
Click to collapse
Use Lenovo MOTO Smart Assistant to repair your tablet (you wont actually repair tablet, just using to get firmware)
Follow steps to get to download the firmware (it will save to ProgramData folder, its hidden folder... in widows anyway)
Take the boot image (boot.img) from firmware folder and transfer to storage on tablet
Instal magisk manager and use to patch the boot image you transfered from computer
Transfer patched boot image back to computer
Download the latest oreo gsi for resurrection remix or lineage
Use fastboot to unlock bootloader
Use fast boot to flash gsi
Use fastboot to flash patched boot image
Google anything you need help with...
I used the resurrection remix oreo also because there is a build that has gapps pre-installed... the pie version works but doesn't have gapps pre-installed and without twrp I couldn't find a way to install them
After tablet boots up install magisk manager and you will be rooted
You will need to register your device with google because it will not be certified... that was a pain to get done even though the process is pretty straight forward
So far only "issues" I have encountered are not actually issues they are due to the fact that the resurrection remix gsi is android "go edition" I haventr tried lineage because I like the customization options that resurrection remix offers
Here is the magisk patched boot image I made so you can skip that part...
https://www.mediafire.com/download/x4d3xp8w3e8bw3g
Just to confirm the sequence of events (and thank you for the magisk-altered file):
1. Move magisk-modified boot image to the tablet.
2. Download latest version of Lineage OS or RR; move that file to the tablet as well
3. DL magisk manager APK and move that to the tablet as well
3. Boot the tablet into Bootloader and flash the new OS file first
fastboot flash recovery file.img
4. Then flash the boot.img altered by magisk
fastboot flash recovery boot.img
5. Reboot the tablet (will it load with the new ROM?)
6. Install magisk manager
Questions on the flashing:
A: Do you flash the .img and the ROM through fastboot shell command on your computer or do you install them in recovery mode?
4niner4 said:
Just to confirm the sequence of events (and thank you for the magisk-altered file):
1. Move magisk-modified boot image to the tablet.
2. Download latest version of Lineage OS or RR; move that file to the tablet as well
3. DL magisk manager APK and move that to the tablet as well
3. Boot the tablet into Bootloader and flash the new OS file first
fastboot flash recovery file.img
4. Then flash the boot.img altered by magisk
fastboot flash recovery boot.img
5. Reboot the tablet (will it load with the new ROM?)
6. Install magisk manager
Questions on the flashing:
A: Do you flash the .img and the ROM through fastboot shell command on your computer or do you install them in recovery mode?
Click to expand...
Click to collapse
So you want all files on the computer at first...
When you unlock bootloader it will wipe the tablet.
Flash the the gsi image then the magisk patched boot image using fastboot (there are instructions on xda regarding flashining gsi... you have to wipe system before flashing)
After tablet reboots to resurrection remix move the magisk manager apk to the tablet and install it... open magisk manager and you should have magisk installed giving you root and so much more.
Before you attempt this make sure you familiarize yourself with all the steps... search google/xda.
Also... I will say this... I tried to just root the tablet first but it wouldn't boot after so I tried to fix it using the Lenove tool and it failed... flashing the resurrection remix gsi with the patched boot image saved me from a lot of headache and wasted time... I would prefer if it was not a "go edition" rom but its still better than stock.
Sorry, more follow-up questions:
1. My bootloader is unlocked. It did not wipe the device (I used the "developer options" in the "Settings" menu to do it. Fastboot indicates the bootloader is unlocked. Do I need to redo unlocking the bootloader? For what it's worth, all my attempts to flash everything with my presumably unlocked bootloader have been unsuccessful.
2. Where did you find a .gsi of Lineage OS 15 for the Lenovo TB-X104F? I cannot find one.
Thanks
4niner5 said:
Sorry, more follow-up questions:
1. My bootloader is unlocked. It did not wipe the device (I used the "developer options" in the "Settings" menu to do it. Fastboot indicates the bootloader is unlocked. Do I need to redo unlocking the bootloader? For what it's worth, all my attempts to flash everything with my presumably unlocked bootloader have been unsuccessful.
2. Where did you find a .gsi of Lineage OS 15 for the Lenovo TB-X104F? I cannot find one.
Thanks
Click to expand...
Click to collapse
Make sure you fastboot flash unlock and fastboot flash unlock_critical. Just look an here for the links for lineage gsi. It flashes just fine and is super easy. I have resurrection remix on my 104f. I'm trying to compile twrp for it right now but hard to do with kids lol also if you use the lenovo tool you can download the recovery files which has boot recovery and all that in it and you can use magisk to patch the boot.ing and then copy that to the Lenovo tool and replace the stock boot img then recover it and you now have a working patched boot.img. I went through the same thing
Any Luck?
Any luck with that twrp? I'm willing to test it out...
Would like to be able to use the resurrection remix pie rom with gapps. So I can hopefully give some helpful feedback... one warning I am an amateur at anything beyond using fastboot and some adb commands, but I can learn pretty quick if i have the time to spend...
Another warning I have a sub-par windows pc to work with (and its the wife's) it prob can't run Linux in VM.
Disable "go edition" in Resurrection Remix Oreo
Using root explorer...
Navigate to /system
Copy build.prop to internal storage
Navigate to where you saved copy of build.prop
Edit build.prop that you copied to internal storage...
Find ro.config.low_ram=true and change to ro.config.low_ram=false
Save and exit file
Copy edited build.prop back to /system (make backup of original and overwrite with edited one)
Set permissions to owner read write (rw-------)
Navigate to /sbin/.magisk/mirror/system
Copy build.prop to internal storage
Navigate to where you saved copy of build.prop
Edit build.prop that you copied to internal storage...
Find ro.config.low_ram=true and change to ro.config.low_ram=false
Save and exit file
Copy edited build.prop back to /sbin/.magisk/mirror/system (make backup of original and overwrite with edited one)
Set permissions to owner read write (rw-------)
Reboot
This allowed me to set notification access again (its disabled in "go edition")
Hey guys, I'm trying to follow the steps in this thread to install Resurrection Remix Pie on the tablet using fastboot but whenever I try to flash a ROM to the system partition I get a (remote: size too large) error.. Does anyone know why this could be? I've tried using flags like -S, I've wiped the partitions and I don't know what else I can try. I have tried with Lineage, AOSiP and RR GSIs.
Thanks.
I cant get this to work.. What version of RR or Lineage OS works with tb-x104f?
up..................
I got the final version of rr oreo running fine... no luck with the latest rr pie unfortunately...
Anyone know if this is an A or AB device?
Disclaimer: I am not an android developer an I am not responsible for bricking your device. The forums contain instructions for unbricking and reflashing your device. You have been warned.
Ok folks I am new here. I spent countless hours trying to debloat the moto e5 play (android oreo 8.1 go). Many headaches and sleepless hours later I finally figured things out the painful way.
Firstly you need to flash twrp recovery. Please see the attached recovery img. There are many recovery images available on the internet but i have found that this one works for me. You must download the correct image/zip for your device or else you will end up in a bootloop. Also you must flash the recovery imag as follows:
Fastboot flash recovery recovery.img (using fastboot Tools).
Just create a folder and copy the image file in it and unzip your fastboot tools in the folder you created. Then open a command window in the folder and with your device in fastboot mode go ahead and flash the recovery.
Secondly You need to install either supersu or magisk to root. I prefered magisk and you can find and download the latest magisk on the internet as well as the updated magisk zip files. Any of the latest magisk 8.0 should work.
Thirdly you should install kingoroot (Not kingroot). Kingoroot seems to be the only one click root app that works on this device. Grant it superuser rights and start uninstalling google apps of your choice (again I will not attach the kingoroot I used. You can google it).
Please note that if you uninstall google completely some apps such as google contacts, calender and youtube will crash. You will see the updated date and time on your phone but you will be unable to save things in the calender as when google was installed. If you want you can uninstall google play services and reinstall a different version of google play services which is compatible with android oreo 8.1 go. then use kingoroot to uninstall calender and contacts and find a compatible version. You should install youtube vanced instead although at this time i am unable to get vanced sign in with microg to work.
You can also uninstall stock youtube and look for a compatible version. I tried installing xposed installer on the E5 bot it causes the device to bootloop no matter which version I tried. I installed TAI CHI xposed but I can't understand chinese so it didnt work for me. Only virtual xposed works but the Aurora store does'nt work.
If anyone else can get a working version of microg and xposed to work I would be so thankful. I have'nt found any custom roms for the E5 but i am always on the lookout.
PS: If you reflash your entire stock rom and you are unable to get a carrier signal and then download another rom from lolinet (I think that is the place I downloaded the stock ROM) and unzip on your pc. Unzip adb and fastboot into the folder where you unzipped the rom. Flash as follows:
fastboot erase modemst1
fastboot erase modemst2
fatboot flash NON-HLOS.bin
No need to reflash the whole ROM just these. That should work.
.
greetings friend
maybe you can help me my equipment is a moto e5 play xt1920-19 pettyl
although I have a recovery 3.3.1.0 that I downloaded from here on this forum.
but I have not been able to install custom rooms and I think it is the recovery.
when I make a backup of everything and
when I want to restore it, everything is lost and it starts only from the beginning as if it were formatted. and also and noticed that the internal memory is not read by the recovery.
Could you help me or at least guide me?
Rgodoy8080 said:
greetings friend
maybe you can help me my equipment is a moto e5 play xt1920-19 pettyl
although I have a recovery 3.3.1.0 that I downloaded from here on this forum.
but I have not been able to install custom rooms and I think it is the recovery.
when I make a backup of everything and
when I want to restore it, everything is lost and it starts only from the beginning as if it were formatted. and also and noticed that the internal memory is not read by the recovery.
Could you help me or at least
Click to expand...
Click to collapse
Strange. It works perfectly on my device. The only roms i flashed was magisk repo and viperfx and they both work very well. I am running android 8.1 go edition. I havent found any custom roms for the devicesuch as lineage OS etc. Development is very slow for this device. You may only be able to flash magisk modules. Also I assume you are using the original stock rom the device came with and it hasnt been altered with a rom from a similar spec device . There are many variants of the E5 play and you need to be sure your device hast the correct firmware.
Rgodoy8080 said:
greetings friend
maybe you can help me my equipment is a moto e5 play xt1920-19 pettyl
although I have a recovery 3.3.1.0 that I downloaded from here on this forum.
but I have not been able to install custom rooms and I think it is the recovery.
when I make a backup of everything and
when I want to restore it, everything is lost and it starts only from the beginning as if it were formatted. and also and noticed that the internal memory is not read by the recovery.
Could you help me or at least guide me?
Click to expand...
Click to collapse
What are you trying to flash? I havent seen any custom ROM OS for this model. You can modify by replacing google apps and install magisk and so on but there are no custom ROMs available for XT1920-19 at the moment.