Removed until I can create proper trees.
Thanx for the ROM!
About flashing the Oreo modem firmware and erasing modemst1 modemst2 I don't know what went wrong but I ended up with imei 0 - of course I did make a backup of my efs partition So everyone make a backup first!
Ænimal said:
Thanx for the ROM!
About flashing the Oreo modem firmware and erasing modemst1 modemst2 I don't know what went wrong but I ended up with imei 0 - of course I did make a backup of my efs partition So everyone make a backup first!
Click to expand...
Click to collapse
How did you backup efs?
JarlPenguin said:
How did you backup efs?
Click to expand...
Click to collapse
There is an option in TWRP
Ænimal said:
There is an option in TWRP
Click to expand...
Click to collapse
Squid, loganbarth or Goldeneyes2?
JarlPenguin said:
Squid, loganbarth or Goldeneyes2?
Click to expand...
Click to collapse
I'm using @lohanbarth 's:
https://forum.xda-developers.com/moto-g5s/development/twrp-3-2-2-0-t3812727
Ænimal said:
Thanx for the ROM!
About flashing the Oreo modem firmware and erasing modemst1 modemst2 I don't know what went wrong but I ended up with imei 0 - of course I did make a backup of my efs partition So everyone make a backup first!
Click to expand...
Click to collapse
I ended up with zero IMEI on Resurrection Remix Nougat after wiping modemst1 and modemst2 in fastboot (but I didn't flash the firmware, I was just testing to see if my persist is fine with the firmware I already had). Now I'm on AICP Oreo, I did the same thing - wipe using fastboot and everything is fine, also worked fine when I was testing this ROM on Oreo modem firmware. But since it happened to you on LOS 16, are you using fastboot on Windows? I think it might be fastboot's fault because on Nougat I wiped on Windows but now since I was compiling I had to use Linux instead. I think the Windows version of fastboot may be bugged, at least for this device. I also had problems with wiping cache and data while flashing the stock ROM - and I was also using fastboot on Windows then. I think I'll edit the OP and instruct to use TWRP for this instead, maybe I'll make a flashable zip just for wiping the modem cache.
JarlPenguin said:
How did you backup efs?
Click to expand...
Click to collapse
As @Ænimal said, there should be an option in TWRP. Alternatively you can use dd to back up any partition you want on any TWRP version. You can use dd while in TWRP either in the terminal or using ADB
Code:
dd if=[path_to_partition] of=[backup_file_path]
For example, to backup /persist to a microSD card and name the file "persist.img":
Code:
dd if=/dev/block/bootdevice/by-name/persist of=/external_sd/persist.img
AsD Monio said:
I ended up with zero IMEI on Resurrection Remix Nougat after wiping modemst1 and modemst2 in fastboot (but I didn't flash the firmware, I was just testing to see if my persist is fine with the firmware I already had). Now I'm on AICP Oreo, I did the same thing - wipe using fastboot and everything is fine, also worked fine when I was testing this ROM on Oreo modem firmware. But since it happened to you on LOS 16, are you using fastboot on Windows? I think it might be fastboot's fault because on Nougat I wiped on Windows but now since I was compiling I had to use Linux instead. I think the Windows version of fastboot may be bugged, at least for this device. I also had problems with wiping cache and data while flashing the stock ROM - and I was also using fastboot on Windows then. I think I'll edit the OP and instruct to use TWRP for this instead, maybe I'll make a flashable zip just for wiping the modem cache.
As @Ænimal said, there should be an option in TWRP. Alternatively you can use dd to back up any partition you want on any TWRP version. You can use dd while in TWRP either in the terminal or using ADB
Code:
dd if=[path_to_partition] of=[backup_file_path]
For example, to backup /persist to a microSD card and name the file "persist.img":
Code:
dd if=/dev/block/bootdevice/by-name/persist of=/external_sd/persist.img
Click to expand...
Click to collapse
Yeah I'm using a windows PC - at least unlocking and flashing stuff has been working so far.. A flashable zip would be nice :good:
Edit: @AsD Monio BTW I flashed the modem etc whilst on lineage 14, that is prior to flashing this ROM - should I try it again with lineage 16 installed?
Ænimal said:
@AsD Monio BTW I flashed the modem etc whilst on lineage 14, that is prior to flashing this ROM - should I try it again with lineage 16 installed?
Click to expand...
Click to collapse
If you booted LOS 14 after wiping modemst1 and modemst2 but before flashing LOS 16 then you will need to wipe them again, but the order of installation - whether the modem firmware first or the ROM should not matter. The first time I actually got the fingerprint scanner working I was on full Nougat firmware with a test build of LOS 16 installed. I just booted to fastboot, ran the 3 commands (flash modem and erase modemst1 and 2) and booted straight back into the system, everything was working. Another time when I was going to flash a test build I had restored the older modem firmware and was on the AICP Oreo ROM. I did the same thing, booted into fastboot and ran the commands. Then I booted straight to TWRP from the fastboot menu using the volume and power buttons. I did the usual wipe - system, cache, dalvik and data. Then I flashed LOS 16 and rebooted. Worked perfectly that time as well.
Nice, congratz! I'll flash as soon as it becomes stable
shrmp said:
Nice, congratz! I'll flash as soon as it becomes stable
Click to expand...
Click to collapse
Thanks, it should be pretty stable now. There weren't nearly as many hardware-related changes from Oreo to Pie as from Nougat to Oreo. Though I understand if you don't want to have to deal with downgrading the firmware in case you need to restore an older ROM. I should be able to switch to a Pie-based ROM on my phone for good soon and if everything works well then I'm going to label it as stable.
@Ænimal the flashable zips are up now if you need them.
Oreo firmware needed means? For Fingerprint sensor?
zahidm said:
Oreo firmware needed means? For Fingerprint sensor?
Click to expand...
Click to collapse
Yes, the fingerprint scanner will not work on Nougat modem firmware. It's weird that the fingerprint scanner depends on the modem firmware but that's what fixes it. I've also only got the RIL and NFC working after flashing the Oreo modem firmware so I can't guarantee that either will work on Nougat firmware.
AsD Monio said:
Thanks, it should be pretty stable now. There weren't nearly as many hardware-related changes from Oreo to Pie as from Nougat to Oreo. Though I understand if you don't want to have to deal with downgrading the firmware in case you need to restore an older ROM. I should be able to switch to a Pie-based ROM on my phone for good soon and if everything works well then I'm going to label it as stable.
@Ænimal the flashable zips are up now if you need them.
Click to expand...
Click to collapse
Sorry for always being the bad messenger but unfortunately Bluetooth doesn't work for me and neither night mode (which is essential for me). There is a lineage 16 test Rom from the brazilian telegram group where bluetooth was working for me (same was reported by people on the other pie threads and also night mode never worked). Anyway, thanx and keep up the great work! Sorry for not providing any logs..
i am currently on LOS 15.1, should i do anything before i flash this rom?
Bluetooth and LiveDisplay/Night Light aren't working.
Nice bro!
THE USER said:
i am currently on LOS 15.1, should i do anything before i flash this rom?
Click to expand...
Click to collapse
I don't know if it's mandatory, but I would strongly recommend wiping everything before installing LOS 16. Also, if you downgraded your firmware to Nougat (in order to get fingerprint working) you need upgrade it back to Oreo firmware before installing LOS 16 (it doesn't work with Nougat firmware)
Great rom has great battery life very smooth ui but Network traffic monitor and Bluetooth is not working
shrmp said:
I don't know if it's mandatory, but I would strongly recommend wiping everything before installing LOS 16. Also, if you downgraded your firmware to Nougat (in order to get fingerprint working) you need upgrade it back to Oreo firmware before installing LOS 16 (it doesn't work with Nougat firmware)
Click to expand...
Click to collapse
I was on stock before i switched to los 15.1 i didnt have to do anything extra to get my finger print sensor working.... I mean, do i have to do anything else rather than flashing the los 16 rom ?
Related
Hey!
So I recently bought a Redmi note 3 (SD) Kenzo, and successfully installed the latest official cm13 snapshot, though I am having problems with the rear camera, flash and FP sensor not been recognized/functioning.
(I should note I’ve never rooted, flashed, unlocked boot loader or install custom recovery or anything like this before)
My process was:
Request official permission to unlock, which I received in like 5 mins, then proceeded to successfully unlock with Mi unlock tool.
I then flashed official TWRP 3.0.2-2, but then couldn’t access internal storage due to some encryption thing TWRP was complaining about. I later worked out it was because I was running the latest China Dev MIUI ROM which is marshmallow, and then flashed “cofface_TWRP3_kenzo_p.img”, which worked fine.
I booted up into TWRP just fine, and then proceeded to wipe Dalvik cache, system, data and cache. I then flashed the firmware then latest snapshot build of which is linked here "http://forum.xda-developers.com/redmi-note-3/development/rom-cyanogenmod-13-t3431866". And then flashed open Gapps.
I then booted up which took around 10 minutes or so just fine.
According to Aida64 I have FPC sensor, and looking through root/system/etc/firmware, with no “goodix” to be seen. I don’t know where to look to find info on my rear cam and flash though.
So should I flash “radon kernel” (I don’t entirely know what this will do), did I make a mistake in the process, or something else entirely? Also is my bootloader now locked due to flashing cm13, and can I unlock it again with the Mi unlock tool?
It would be so great if you could help!
(also if more info is needed just let me know)
BukuThatDude said:
I recently bought a Redmi note 3 (SD) Kenzo, and successfully installed the latest official cm13 snapshot, though I am having problems with the rear camera, flash and FP sensor not been recognized/functioning.
Click to expand...
Click to collapse
Bro, you did everything in correct order.
And, to get fp working for you, flash Radon v2.9 and select fpc (or goodix if still doesn't work). Kernel is the sw part which directly interacts with your hw. So, you'll need Kernel Aduitor or any another such app to tweak the kernel settings. AIDA64 should show your cam sensors, afair.
And, if Radon doesn't help then you can flash CM13_RADIOS.zip which you'll find in the "All ROM, Recoveries, add-on zips......." thread.
And, official CM13 doesn't lock your bootloader, the unofficial CM13 from SantoshM does that.
You can unlock your bootloader any no. of times using MiUnlock, and if needed you can check it using the following command in adb and fastboot tool
Code:
fastboot oem device-info
Look for "Bootloader Unlocked - true/false"
As above, flash the latest Radon Kernel. Also do not use the old snapshots of CM13 (they are now months old), nightlies are more stable and much more updated.
sasukay said:
Bro, you did everything in correct order.
And, to get fp working for you, flash Radon v2.9 and select fpc (or goodix if still doesn't work). Kernel is the sw part which directly interacts with your hw. So, you'll need Kernel Aduitor or any another such app to tweak the kernel settings. AIDA64 should show your cam sensors, afair.
And, if Radon doesn't help then you can flash CM13_RADIOS.zip which you'll find in the "All ROM, Recoveries, add-on zips......." thread.
And, official CM13 doesn't lock your bootloader, the unofficial CM13 from SantoshM does that.
You can unlock your bootloader any no. of times using MiUnlock, and if needed you can check it using the following command in adb and fastboot tool
Code:
fastboot oem device-info
Look for "Bootloader Unlocked - true/false"
Click to expand...
Click to collapse
Can the kernel be flashed after the firmware/rom? Will it factory reset the device? If i run into any any issues what part do i wipe and replace in twrp to revert to the previous kernel?
Are you sure you have the Kenzo version?
Maybe you have the Kate version like me
BukuThatDude said:
Can the kernel be flashed after the firmware/rom? Will it factory reset the device? If i run into any any issues what part do i wipe and replace in twrp to revert to the previous kernel?
Click to expand...
Click to collapse
Flashing a kernel is like flashing any add-on zip like bootanimation or some new font and stuff. You don't need to flash the whole ROM or the reqd. firmware.
So, first make a backup of system and boot partition in twrp.
Then, wipe cache and dalvik and then flash the kernel zip. Reboot and done.. First boot may take some time.
And, should you need to revert back to stock, you can restore the backup you made earlier.
sasukay said:
Flashing a kernel is like flashing any add-on zip like bootanimation or some new font and stuff. You don't need to flash the whole ROM or the reqd. firmware.
So, first make a backup of system and boot partition in twrp.
Then, wipe cache and dalvik and then flash the kernel zip. Reboot and done.. First boot may take some time.
And, should you need to revert back to stock, you can restore the backup you made earlier.
Click to expand...
Click to collapse
Thank you, I'll update on how it goes.
sasukay said:
Flashing a kernel is like flashing any add-on zip like bootanimation or some new font and stuff. You don't need to flash the whole ROM or the reqd. firmware.
So, first make a backup of system and boot partition in twrp.
Then, wipe cache and dalvik and then flash the kernel zip. Reboot and done.. First boot may take some time.
And, should you need to revert back to stock, you can restore the backup you made earlier.
Click to expand...
Click to collapse
Yes holy sh*t thank you, both cameras and flash work now, fingerprint doesn't, so i'll try re-flashing it for "goodix" to see if that works.
(also is normal to hear a physical clicking sound next to the flashlight when turned on/off?)
BukuThatDude said:
Yes holy sh*t thank you, both cameras and flash work now, fingerprint doesn't, so i'll try re-flashing it for "goodix" to see if that works.
(also is normal to hear a physical clicking sound next to the flashlight when turned on/off?)
Click to expand...
Click to collapse
Flashing either FPC or goodix radon fingerprint still doesn't work?
BukuThatDude said:
Flashing either FPC or goodix radon fingerprint still doesn't work?
Click to expand...
Click to collapse
Try flashing this
Maybe you have goodix variant. If everything else fails, try goodix patch: https://drive.google.com/file/d/0B3Ji2Mma4WGpaFAweDZNWmVVVms/view
Hi I had Xpower5 Rom. I wanted to try new Nougat. I had many issues with flash (error of processing system.sin and loader.sin). I dont know how now it work. After that I flashed AndroPlus 43 kernel and TWRP 3.0.2. Kernel works but No white led on startup and no recovery there (also adb reboot recovery not work) . I tried another img of twrp and nothing changed. Any idea how install recovery? Anybody has the same problem with flashing? Thanks
As this phone doesn't support universal recovery and only sports a ota partition that can be used for recovery but then requires a kernel that supports booting recovery from ota partition, it's a hustle to use non standard recovery systems.
Is there even a nougat compatible kernel with included TWRP ota boot support for this phone?
This should work
https://forum.xda-developers.com/showpost.php?p=70807294&postcount=132
Also patching the stock kernel with the rootkernel tool integrates working twrp.
Gewiz said:
This should work
https://forum.xda-developers.com/showpost.php?p=70807294&postcount=132
Also patching the stock kernel with the rootkernel tool integrates working twrp.
Click to expand...
Click to collapse
It works! Thanks. Problem was: no white LED flash there. I have to press vol down and power on.
But I have still have a problem with flashing. Error of processing file loader.sin or system.sin. I cant flash again anything
Make sure you use latest ver of flashtool 0.9.23.2
Gewiz said:
Make sure you use latest ver of flashtool 0.9.23.2
Click to expand...
Click to collapse
Yes I have latest version. I tried older version as well but nothing changed
hromanse said:
Yes I have latest version. I tried older version as well but nothing changed
Click to expand...
Click to collapse
Flash firmware 5.11 first and flash nougat firmware afterwards.
This should work
Not work as well
the 3.1 3.0.2 TWRP bundled in rootkernel 5.23 messess up the internal permissions, so it will appear to work until you try and recover, or - TWRP runs a wipe with mkext4fs
i was talking a bit about it in https://forum.xda-developers.com/showthread.php?t=3560135
---------- Post added at 18:16 ---------- Previous post was at 18:13 ----------
Gewiz said:
Flash firmware 5.11 first and flash nougat firmware afterwards.
This should work
Click to expand...
Click to collapse
Yeah, going back to Lollipop and going all the way up to Nougat works, this is what happened to me. I thought I had a psuedo-recovery-dual system boot .... where i could switch between Marshmallow and Nougat
But then I decided to factory reset, and that started all the problems.
NeoBeum said:
Yeah, going back to Lollipop and going all the way up to Nougat works, this is what happened to me...
Click to expand...
Click to collapse
Thanks! It works
hromanse said:
Thanks! It works
Click to expand...
Click to collapse
Just make sure Restore works, so you don't get burned thinking everything is ok and end up with 12GB of partition mismatched data backup after a month, like I did
DisclaimerThis software comes wth no warranty,XDA staff ,myself or TeamWin stuff can't be hold responsible for any damage it may cause to your device.
Note: Currently Oreo 8.1 custom roms are supported only on BKL-L04 with EMUI 8.1
Download and Installation
* Download twrp recovery
* Start your device in fastboot mode
* Install the recovery using the following command:
Code:
fastboot flash recovery_ramdisk [name of the file].img --> ex: fastboot flash recovery_ramdisk twrp_blanc_0.1.img
* Restart with this command:
Code:
fastboot reboot
* As soon as you execute the restart command,remove the USB cable and keep pressing Volume UP,so the device will boot to TWRP.This is to avoid that the device boot to OS,overwritting TWRP recovery.
Features
Internal storage decryption = working
MTP and OTG connection = working
Backup&Restore = working
Note: There are no sources for this yet,because is based on the work of @zxz0O0 ,from Honor 9 forum.
Credits
**** @zxz0O0 - This wouldn't be possible without this guy,so big big thank to him.I used his base to make this recovery work ,so in sign of respect his nick will also be on the TWRP boot screen.Thank again buddy!
**** TeamWin project ,obviously.
Download links
twrp_blanc_0.1.img - initial test release
twrp_bkl_0.2.img - OEMinfo partition is available for backup
twrp_bkl_0.3.img - /cache mounting is fixed,backup /vendor as image (vendor still can't be mounted)
twrp_bkl_0.4.img - /vendor mounting/unmounting is now fixed (thx @ante0 for the script)
twrp_bkl_0.5.img - mounting/unmounting issues shound be fixed , added a new option to exclude OEM path from wiping with Factory Reset and can be enabled/disabled in settings (thx Team OpenKirin for this), this version will work even with newer updates that bump security patch version.
twrp_bkl_0.6.img - Cache wiping issue is now fixed
twrp_bkl_0.7.img - fixed decryption on EMUI 8.1 (now you can use the same password/pin/pattern to decrypt in TWRP), /recovery_ramdisk no longer available for backup./vendor no longer available for backup (use /vendor_image instead),/system and /data can be unmounting issue with 8.1 devices is now fixed.
Pretoriano80 said:
Internal storage decryption = working
MTP and OTG connection = working
Backup&Restore = working
Click to expand...
Click to collapse
Thanks man! :laugh: Need to test this!
IcipherPT said:
Thanks man! [emoji23] Need to test this!
Click to expand...
Click to collapse
No problem! Please report back if it's working or not.
Pretoriano80 said:
No problem! Please report back if it's working or not.
Click to expand...
Click to collapse
wipe everything to decrypt?
ngoralph said:
wipe everything to decrypt?
Click to expand...
Click to collapse
Nope, just decrypting, like you do when your phone is starting and asks for PIN! [emoji6]
Pretoriano80 said:
No problem! Please report back if it's working or not.
Click to expand...
Click to collapse
Just tested on my honor view 10. It was asking for a password to decrypt. I entered my lockscreen pass and everything was decrypt.
so TWRP CAN decrypt
@youtuber123
did you try a nandroid backup?
youtuber123 said:
Just tested on my honor view 10. It was asking for a password to decrypt. I entered my lockscreen pass and everything was decrypt.
so TWRP CAN decrypt
Click to expand...
Click to collapse
Ok, so it's working!Great,please let me know if something it's broken (backup, restore, MicroSD mounting, etc).
Pretoriano80 said:
Ok, so it's working!Great,please let me know if something it's broken (backup, restore, MicroSD mounting, etc).
Click to expand...
Click to collapse
nandroid (backup and restore) is working
mtp is working too
and micro usb mounting is working
didn't tested to flash something using twrp
youtuber123 said:
nandroid (backup and restore) is working
mtp is working too
and micro usb mounting is working
didn't tested to flash something using twrp
Click to expand...
Click to collapse
There's not much stuff to flash for this device! [emoji16]
Good, finally a useful twrp....
Can we flash LOS using this now?
@Pretoriano80
tried your recovery at my view 10. flashed it via fastboot. had no success. your twrp is hanging at the start screen. tried to flash it via the twrp of dees_troy, the same result. recovery is not booting completely, remains at the twrp start screen. any ideas?
kurvenmeister said:
@Pretoriano80
tried your recovery at my view 10. flashed it via fastboot. had no success. your twrp is hanging at the start screen. tried to flash it via the twrp of dees_troy, the same result. recovery is not booting completely, remains at the twrp start screen. any ideas?
Click to expand...
Click to collapse
Which version? Another user reported that is working.
Edit: More details about your device?Which version do you have exactly?
the twrp_blanc_0.1.img
the dl-link of twrp_bkl_0.2.img is not working
kurvenmeister said:
the twrp_blanc_0.1.img
the dl-link of twrp_bkl_0.2.img is not working
Click to expand...
Click to collapse
Ok thank,link is fixed .but if the initial one didn't booted ,i don't think this will do.Which version of Honor 10 do you have (european,usa,etc)?I'm not sure it will work on the US version or any other version which is based on Oreo 8.1.
@Pretoriano80
dl-link worked. tried the second version of your recovery. still no success. it is hanging at the start screen. nothing else happend. european bkl-l09, resurrection remix, oreo 8.1
kurvenmeister said:
@Pretoriano80
dl-link worked. tried the second version of your recovery. still no success. it is hanging at the start screen. nothing else happend. european bkl-l09, resurrection remix, oreo 8.1
Click to expand...
Click to collapse
The custom rom might be the culprit!I didn't tested on custom roms.
Pretoriano80 said:
Ok thank,link is fixed .but if the initial one didn't booted ,i don't think this will do.Which version of Honor 10 do you have (european,usa,etc)?I'm not sure it will work on the US version or any other version which is based on Oreo 8.1.
Click to expand...
Click to collapse
Hey mate nice to see you here
Nice job with the recovery! I've been handed out an US View 10 a couple weeks ago (with Android 8.1 pre-release stuff), I'll test it out for you.
twrp-3.2.1-0-berkeley.img didn't boot on BKL-L04 (dark screen and reboot), but Ethan made some changes and twrp-3.2.1-1-berkeley.img does work fine.
I've been told that some selinux changes were needed to boot 8.1 stuff, some critical service that fails to run because it can't find the right policy, something related to recovery_vendor partition that runs it.
It will work in 8.0 setups also just fine.
I'll let you know how it goes :fingers-crossed:
Hope we get 8.1 kernel sources soon so I blu_spark this blue beauty
Rommco05 said:
I succesfuly make full backup (except data) and flashed busybox. I dont need decrypted data all seems to be fine. In backup section just missing OEM
Click to expand...
Click to collapse
Latest version should have Oeminfo available for backup! Did you tested that version?
eng.stk said:
Hey mate nice to see you here
Nice job with the recovery! I've been handed out an US View 10 a couple weeks ago (with Android 8.1 pre-release stuff), I'll test it out for you.
twrp-3.2.1-0-berkeley.img didn't boot on BKL-L04 (dark screen and reboot), but Ethan made some changes and twrp-3.2.1-1-berkeley.img did.
I've been told that some selinux changes were needed to boot 8.1 stuff, some critical service that fails to run because it can't find the right policy, something related to recovery_vendor partition that runs it.
It will work in 8.0 setups also jsut fine.
I'll let you know how it goes :fingers-crossed:
Click to expand...
Click to collapse
Hi! My favourite kernel developer is here, nice!
I have a guess on what may be wrong, but i'm not sure. Let me know if you figure out! [emoji6]
This project is a continuation of the thread here:
[ROM] TWRP Flashable Stock Builds
As the original author of that thread, Q9Nap, no longer has a Moto G5 Plus, I have started this project to continue the work that Q9Nap started.
About this project
This is a collection of stock roms that can be flashed by TWRP. These roms have the following modifications from stock:
DM-verity is disabled
Forced encryption of the data partition is disabled. It is still possible to encrypt the partition if you wish
The boot image has been modified to suppress the unlocked device warnings (although the N/A will still show)
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
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
Flash the zip via TWRP
Optionally flash Magisk etc
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
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
NPNS25.137-93-18 (1 August 2018 security patches)
Android File Host - potter-twrp-flashable-NPNS25.137-93-18-aroma.zip
Dropbox - potter-twrp-flashable-NPNS25.137-93-18-aroma.zip
Released only for retus (US), but will be compatible with other channels.
NPNS25.137-93-14 (1 June 2018 security patches)
Android File Host - potter-twrp-flashable-NPNS25.137-93-14-aroma.zip
Dropbox - potter-twrp-flashable-NPNS25.137-93-14-aroma.zip
Suitable for the following channels:
retus (US)
reteu (Europe)
retapac (Asia Pacific)
NPNS25.137-92-14 (1 June 2018 security patches)
Android File Host - potter-twrp-flashable-NPNS25.137-92-14-aroma.zip
Dropbox - potter-twrp-flashable-NPNS25.137-92-14-aroma.zip
Suitable for the following channels:
retin (India)
retla (Latin America)
retbr (Brazil)
All versions that I have created will be placed in this folder at Android File Host:
https://androidfilehost.com/?w=files&flid=273039&sort_by=date&sort_dir=DESC
New - they will also be mirrored at Dropbox:
https://www.dropbox.com/sh/vgw7me2f8p5gcgq/AABoBfx1tMCOMMaXL4m75Fdma?dl=0
An important note for those who have flashed custom Oreo roms
It is a frequent issue regarding Oreo roms that the device's IMEI is set to 0 in certain conditions. It is possible that these roms (or something used with them) are tampering with the persist partition of the devices. When this occurs, if the EFS is erased, it is not reconstructed correctly.
The scripts used in earlier versions this rom erase the two modem partitions, modemst1 and modemst2. These are your EFS. Normally, if you have an intact persist partition, they are recreated on boot. However, if your persist is not intact, they may fail to be recreated. The ideal scenario in this case is that you have a backup of an intact persist partition, and you restore it before flashing this. The next best is to backup a working EFS before flashing this rom, and then restore the EFS after flashing. Note that the second scenario is not guaranteed to work for any future updates. If the modem firmware is updated in an update, then it may require the EFS to be reconstructed, relying upon an intact persist.
Versions of this rom that have "no-erase-modemst" in their filename do not have the commands to erase modemst1 and modemst2. The aroma installers make it optional to erase modemst1 and modemst2.
An update on the IMEI zero issue
I have created another project linked below, that explains what has happened to some people who have lost their IMEI after flashing Oreo roms, then flashing stock builds that erased the modemst1/2 partitions.
Fix Persist, resolve IMEI=0, Explanation, Requirements
If you have installed an Oreo rom previously, or have lost your IMEI, I recommend that you read the first couple of posts in that thread. Take appropriate steps to back up your persist and EFS before installing these roms.
Guide to creating TWRP flashable builds
The following post is a guide to creating these flashable builds. Please ask questions on how to create such builds in this project:
https://forum.xda-developers.com/g5-plus/how-to/guide-creating-twrp-flashbale-stock-roms-t3804776
XDA:DevDB Information
[Nougat][Stock][Rom] TWRP Flashable Stock Builds, ROM for the Moto G5 Plus
Contributors
NZedPred
ROM OS Version: 7.x Nougat
Based On: Stock ROM
Version Information
Status: Snapshot
Current Stable Version: 1 June 2018 security
Stable Release Date: 2018-07-07
Created 2018-07-07
Last Updated 2018-10-30
Hello that sir, nice job yours... Ive a question: its safe to flash the 93-14 version on a retus xt1687? Thanks and Keep the good work.
Armando Lopez said:
Hello that sir, nice job yours... Ive a question: its safe to flash the 93-14 version on a retus xt1687? Thanks and Keep the good work.
Click to expand...
Click to collapse
Thanks. Yes, the 93-14 is suitable for retus. You may need to clean flash depending on what rom you were on last.
NZedPred said:
Thanks. Yes, the 93-14 is suitable for retus. You may need to clean flash depending on what rom you were on last.
Click to expand...
Click to collapse
Wow. That was fast... Im on stock, and always flash over my current versión without a clean flash... Its ok? (sorry 4 my poor english)
Armando Lopez said:
Wow. That was fast... Im on stock, and always flash over my current versión without a clean flash... Its ok? (sorry 4 my poor english)
Click to expand...
Click to collapse
Yeah if you previously on stock then you should be ok.
NZedPred said:
Yeah if you previously on stock then you should be ok.
Click to expand...
Click to collapse
Im always update my g5 plus with the thread of Q9nap, and now i will with yours... Seriously thanks for your great work.
I m on custom rom right now. If i Flash this rom , will there be any issue with volte or imei?
Would anybody what images i need to flash to only update firmware? and kep my custom rom?
I can flash any version?
karan3660 said:
I m on custom rom right now. If i Flash this rom , will there be any issue with volte or imei?
Click to expand...
Click to collapse
Shouldn't be. From what I've read, the issues with IMEI and VOLTE are relating to installing an Oreo custom rom and then flashing back to stock using fastboot.
Having said that, always make sure you have a backup of your persist and EFS. Refer to this thread for more details: https://forum.xda-developers.com/g5-plus/how-to/dev-fixing-baseband-t3806064. In particular, post #16 in the thread details how to backup and restore persist.
tldr; if you never installed an oreo custom rom, you'll be fine. if you installed an oreo custom rom, more than likely you're fine, but in either case, backup persist and efs.
EDIT: I've added a note to the OP about coming from an Oreo rom. My advise is changing slightly - if you previously installed an Oreo custom rom and don't have a persist backup from prior to doing so, you need an EFS backup. But as above, backup persist and efs to be safe regardless.
Tech_Savvy said:
Would anybody what images i need to flash to only update firmware? and kep my custom rom?
Click to expand...
Click to collapse
I've replied in your post in my guide thread.
Kinteshi said:
I can flash any version?
Click to expand...
Click to collapse
As a general rule, stick to the rom that is the same as the channel that you were on in full stock.
Which one for Indian version?
nitinbhalla95 said:
Which one for Indian version?
Click to expand...
Click to collapse
Indian channel is retin. It's in the OP which one to use
Thanks again, works like a charm.
Thanks mate
TL;DR: I lost my IMEI while flashing this, and I'm trying to find out why did I lost it. PLEASE MAKE SURE TO BACKUP PERSIST, AND EFS, SO YOU DON'T HAVE TO GO THROUGH THE TROUBLE I WENT TO
Just to let you guys know, I came from the MIUI 9.6 ROM and flashed this ROM. Here was my steps
Rebooted to Recovery
Flashed the latest TWRP(Had an old one, I believe it was the Treble unofficial one)
Rebooted to Recovery again (to Boot into the new TWRP)
Clean Wiped and Formatted the Data
Flashed this ROM(NPNS25.137-93-14)
Rebooted to the new ROM
While Flashing this, I noticed it erased modemset1 and 2. I didn't bother much about it, until the ROM booted.
I noticed it deleted my IMEI, I managed to recover it, but I am now scared of flashing it again. What should I do
(PS: I never had this problem while flashing other ROMs, everything worked fine until I flashed this)
EDIT:
I checked updater-script, it apparently erases modemset1 and 2 to RAW, maybe that could be the problem?
EDIT 2: (Sorry for the constant edits )
if you notice this:
Code:
ui_print("Erasing modemst1 ...");
format("raw", "EMMC", "/dev/block/bootdevice/by-name/modemst1", "0", "/modemst1");
ui_print(" ");
ui_print("Erasing modemst2 ...");
format("raw", "EMMC", "/dev/block/bootdevice/by-name/modemst2", "0", "/modemst2");
ui_print(" ");
I think the problem is that it erases them to "0", and that could be why I lost my IMEI
EDIT 3:
I noticed in another thread you mentioned you were patching the Modem with the new patches released on the June Security update. Isn't Modem unique for each device?
Hi. I see that MIUI 9.6 is an Oreo rom, correct? If so, I'd be interested to know if you've ever flashed stock using fastboot at any stage since having an Oreo build.
On my phone, and I'm guessing on everyone else's for whom it works, the modemst partitions are recreated on boot of they have been erased. The lines on the script are no different from those that were on the previous thread's builds, so these builds aren't doing anything differently.
The modem partition is like drivers, so no it's not unique per device. The persist partition is unique per device, which is why it's important to back it up.
NZedPred said:
Hi. I see that MIUI 9.6 is an Oreo rom, correct? If so, I'd be interested to know if you've ever flashed stock using fastboot at any stage since having an Oreo build.
On my phone, and I'm guessing on everyone else's for whom it works, the modemst partitions are recreated on boot of they have been erased. The lines on the script are no different from those that were on the previous thread's builds, so these builds aren't doing anything differently.
The modem partition is like drivers, so no it's not unique per device. The persist partition is unique per device, which is why it's important to back it up.
Click to expand...
Click to collapse
No, I have stayed away from the Stock builds using fastboot. If anything, I have been using a debloated stock ROM that's on the November 2017 patch(and it's made to be flashed on TWRP).
Related to the modem partition, I understand now. But my question is, why does it turn my IMEI to 0? All I can think about is the "0" on the code I posted in my other post.
Sorry if it seems bland, it's late over here and I sending this message in the very same phone it got the IMEI problem.
If you need anything from my part, ask away. I know some stuff about Android and I can try to help you out to find a solution :fingers-crossed:
Angel_Wolf said:
No, I have stayed away from the Stock builds using fastboot. If anything, I have been using a debloated stock ROM that's on the November 2017 patch(and it's made to be flashed on TWRP).
Related to the modem partition, I understand now. But my question is, why does it turn my IMEI to 0? All I can think about is the "0" on the code I posted in my other post.
Sorry if it seems bland, it's late over here and I sending this message in the very same phone it got the IMEI problem.
If you need anything from my part, ask away. I know some stuff about Android and I can try to help you out to find a solution :fingers-crossed:
Click to expand...
Click to collapse
I can only assume that the device checks the EFS for IMEI data, and if it doesn't exist, creates the EFS (modemst1 and modemst2). The creation of the EFS is based upon data in the persist partition. Effectively, EFS is a cache. So if you have restored an old EFS backup, you have restored the cache, so it is using the IMEI data from the old backup. But if it didn't create it automatically, that suggests that there is an issue with the persist partition.
This post has lots of info (and I keep on linking to it - the IMEI issue is a big one!) https://forum.xda-developers.com/g5-plus/how-to/dev-fixing-baseband-t3806064
About
**********
I've created a flashable ROM zip of the latest H990DS KDZ SEA Region. Everything is working correctly on my H990 Single SIM.
ARB
**********
0
Security Patch
**********
1 April 2019
Download
**********
1. With modem & cust partitions (only if you know what you are doing):
https://drive.google.com/open?id=1YARnnE4-V1y9Jd1EhTzdizdkd6DaAYz_
2. Without modem & cust partitions (keeps your existing modem, recommended):
https://drive.google.com/open?id=1gCHxAk3hXjCsA4Qm3djgSmJEb3rSL5WA
Installation process:
**********
1. Upgrading / flashing over another stock Oreo ROM:
• Flash latest TWRP
• BACKUP everything
• Wipe (caches)
• Flash ROM
• Flash Magisk
• Flash MK2000 Oreo kernel (Important!)
• Reboot
• Enjoy
2. Clean from scratch install:
• Flash latest TWRP
• BACKUP everything
• Backup everything you want to put back, it will be wiped
• Clean wipe (data, system, caches)
• Flash ROM
• Flash Magisk
• Flash MK2000 Oreo kernel (Important!)
• Reboot
• Enjoy
flashing the second rom without modem or cust now on my h990ds , i hope everything goes well
sniper9911 said:
flashing the second rom without modem or cust now on my h990ds , i hope everything goes well
Click to expand...
Click to collapse
Just please remember to flash MK2000 kernel after you flash the ROM without rebooting in-between.
I made the mistake of rebooting afterwards and the stock kernel restored the stock recovery and wiped my device.
(This wasn't an issue because I made a full backup of all of my data though)
updated successfully
Updated the dirty way flashed over my current ROM ... I wiped cache and art cache just in case
Seems legit and so far my device is finishing the data setting , i did make a backup of my firmware files just in case and so far it went smoothly
All i did was downloading the ROM , Twrp , mk2000 h990ds v2.1 And Magisk latest
Flashed Twrp first then recovery rebooted , wiped Dalvick and cache then flashed ROM then flashed mk2000 then magisk and phone booted
Thanks for the update
I have also updated my H990DS successfully by "dirty" upgrade keeping all apps.
I just added H990DS_Hide_Boot_Warning.zip to remove the error message at boot start.
sniper9911 said:
Thanks for the update
Click to expand...
Click to collapse
tapir1505 said:
I have also updated my H990DS successfully by "dirty" upgrade keeping all apps.
Click to expand...
Click to collapse
Thanks for your feedback!
Glad to know it is working correctly
Against 20a the only difference is s3curity patch?
faeterov said:
Against 20a the only difference is s3curity patch?
Click to expand...
Click to collapse
I'm not sure of any other difference except the security patch.
I assume there are some minor tweaks as the update notification
generally mentions "usability improvements", but LG being LG don't
release a change-log so who knows unfortunately...
I have installed v20b (stock room and rooted room), but this version do not support fingerprint sensor, terrible, it took me more than 2 days for this :crying::crying:
luuhungit said:
I have installed v20b (stock room and rooted room), but this version do not support fingerprint sensor, terrible, it took me more than 2 days for this :crying::crying:
Click to expand...
Click to collapse
You'll need to provide more details than this.
Which variant V20? What ROM did you come from? Did you backup partitions? etc.
Also: to add, this is normally a modem issue and is resolved by restoring / flashing the correct modem
jl10101 said:
You'll need to provide more details than this.
Which variant V20? What ROM did you come from? Did you backup partitions? etc.
Also: to add, this is normally a modem issue and is resolved by restoring / flashing the correct modem
Click to expand...
Click to collapse
maybe, thank for idea
i is using h900ds, taiwan version
yesterday, i used LGUP to flash v20b version with refusbish function, but second sim and fingerprint inactive.
maybe refusbish function did not flashed all partition on device
today, i have to flash v10c to use dirtysanta root, then flash all partition of v20b version, but ignore aboot to keep bootloader unlocked, it is using with old data partition very well.
luuhungit said:
maybe, thank for idea
i is using h900ds, taiwan version
yesterday, i used LGUP to flash v20b version with refusbish function, but second sim and fingerprint inactive.
maybe refusbish function did not flashed all partition on device
today, i have to flash v10c to use dirtysanta root, then flash all partition of v20b version, but ignore aboot to keep bootloader unlocked, it is using with old data partition very well.
Click to expand...
Click to collapse
Go to 10c root flash 20a partitions through Patched LGUP ignoring aboot aboot.bak and recovery recovery.bak (tarp may be gone but as long as you'll have boatloads unlocked you can flash twrp back)after that just flash only 20b system via LGUP Partitions DL I dunno whats going on with LG KDZs from now on all you should keep the old partitions from 20A and just flash system
jl10101 said:
Just please remember to flash MK2000 kernel after you flash the ROM without rebooting in-between.
I made the mistake of rebooting afterwards and the stock kernel restored the stock recovery and wiped my device.
(This wasn't an issue because I made a full backup of all of my data though)
Click to expand...
Click to collapse
unfortunately im using F800L, so it will not work if i flash this rom into my device.
is there any change to tell me how to update the security patch for my device?
thx b4 m8
can I use this patch for H990DS IDN (Indonesia version) that is still 2.0? It's dual sim version...
thanks
stingbandel said:
can I use this patch for H990DS IDN (Indonesia version) that is still 2.0? It's dual sim version...
thanks
Click to expand...
Click to collapse
Yes. Use mk200 beta38
Update to 20B and Just remember to back up firmware and efs folders from Oreo 20A and restore after flashing 20B otherwise you will lose the second sim
sniper9911 said:
Updated the dirty way flashed over my current ROM ... I wiped cache and art cache just in case
Seems legit and so far my device is finishing the data setting , i did make a backup of my firmware files just in case and so far it went smoothly
All i did was downloading the ROM , Twrp , mk2000 h990ds v2.1 And Magisk latest
Flashed Twrp first then recovery rebooted , wiped Dalvick and cache then flashed ROM then flashed mk2000 then magisk and phone booted
Thanks for the update
Click to expand...
Click to collapse
I followed exact steps in OP (wiped caches, flashed 20b ROM, Magisk 19.3, MK2000 v2.2b38 H990DS, rebooted) and thought it worked for me as well until I noticed some built-in system apps were not working. Calendar, Chrome and others had strange names in Apps list (Chrome was called "add to dictionary" and Calendar was something like "on time (%s,..."). I managed to get them working again by stopping them and reinstalling from the apk files in system but wasn't sure I woudn't have other issues, so I wiped system partition and reflashed it although it didn't seem to change anything. When I noticed Bluetooth wouldn't enable I decided to go back to 20a by flashing full ROM (all done through TWRP) but that didn't fix the issue. I had even tried going back to MK2000 2.1 but no change. Finally had to do full restore from TWRP backup to get BT working again. Would like to have latest security patch.
Does anyone have any ideas what went wrong? Could any Magisk modules cause issues? Any help is appreciated.
Works perfect.
I flashed it straight from Lineague 16.1 after wipe, no problems.
(LG H990DS)
albaniax said:
Works perfect.
I flashed it straight from Lineague 16.1 after wipe, no problems.
Click to expand...
Click to collapse
Good to hear! Thanks for the feedback!
Hi. H990DS Twn variant. Currently running stock rom 20a (first oreo rom released for 990DS).
I see that you've uploaded another stock rom for 990DS that is 20H. But security patch is from FEB.
But this is a newer thread, so I assume this is the newest release. Could you please just confirm if this is the rom I should flash.
Thanks in advance
Salvaparalyzer said:
Hi. H990DS Twn variant. Currently running stock rom 20a (first oreo rom released for 990DS).
I see that you've uploaded another stock rom for 990DS that is 20H. But security patch is from FEB.
But this is a newer thread, so I assume this is the newest release. Could you please just confirm if this is the rom I should flash.
Thanks in advance
Click to expand...
Click to collapse
I'm not sure why 20H is effectively a "newer" ROM going by LG's naming convention.
They used 20B (this ROM) with a newer security patch, and the actual file is newer than 20H.
I would normally assume that 20H should have a newer security patch and be a newer build of Oreo, but it seems not.
This ROM essentially is the latest available. I cannot find any changelogs to verify that 20H has a newer system / android build though. Sorry!