How to flash stock firmware from lolinet - Moto G7 Plus Questions & Answers

Hi there,
I want now to go back to stock ROM with my G7 plus XT1965-3.
I got a firmware file from lolinet
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
( RETEU=retail EU? )
and tried to flash via recovery adb sideload.
But it stops with the error "failed to find update binary".
How can I flash now this rom?
thanks a lot!
partially SOLVED
this thread explains how to flash lolinet stock ROM:
Firmware update
My Moto G Power 2020 xt2041-4 (retus) just got an update to the July security patch. I then noticed that the firmware online finally updated (it was many versions behind.) https://mirrors.lolinet.com/firmware/moto/sofia/official/RETUS/...
forum.xda-developers.com
but the syntax does not fully apply to the G7 plus...

Hello, did you read this ?
Guide: howto update stock rom with unlocked bootloader, root, TWRP and keep user data
With unlocked bootloader, and with TWRP and magisk root installed, you currently can't install any of the motorola OTA:s. Below have been tested on XT1965-3 while on RETEU, PPWS29.98-66 (security updates installed up until 1 january 2019), with...
forum.xda-developers.com

Thanks a lot! Yes, now I read it.
One thing catches my eye:
The latest rom for my XT1965-3 is QPW30.61-21-18 and it has no
system_b.img_sparsechunk.0 +1
thus, command
fastboot flash system_b system_b.img_sparsechunk.0
will not work with the latest rom QPW30.61-21-18
Is it now recommended to flash the older rom to have this system_b images and then flash the latest rom?
My fear is, when I flash the latest rom, I might miss these b images, they´re not part of the latest rom...
Thanks a lot for your help

Related

I can't flash any Android Oreo ROM

Hello, I have a problem with my Xiaomi Redmi 4X phone, as I said, I can not flash any Custom ROM for Android 8.1 All this happened after I put my phone in service to replace the display on which I've broken it. Now any version of Android 8.1 I try to flash results in a bootloop. I have to mention 3 things
1. In TWRP when flashing I noticed that all Custom ROMs are stuck in "Flashing system files ..." for a few seconds after saying that it ended flash-but did not abssolut anything.
2. Now a few hours I accidentally flashed Pixel Experince, but now I have the same problem.
3. I can not flash any versions of TWRP.Not much but...
THIS IS HAPPENING ONLY ON THE ANDROID OREO ROMs, Nougat ROMs works perfectlly
Try to flash first latest version of twrp or you can flash redwolf recovery then flash firmware v40 then try clean flash for oreo roms
As mentioned by above user...(latest TWRP recovery and firmware is must)
Flash latest TWRP recovery, 3.2.1-0 should be fine but there's update available 3.2.2.-0 so any will do.
Next, flash latest firmware.
Clean flash is must when changing OS.
It's most likely you don't have latest TWRP recovery and firmware.
Do backup first.

Fingerprint not detecting in custom os since installed official 8.1

Fingerprint not detecting since I have installed custom ROM after I have installed official Oreo
On official Oreo fingerprint shows up in settings but in custom Oreo all works fine and best but fingerprint doesn't show up in any settings I have tried 4 8.1 custom roms like sex pixelexpirience 64 bit versions all works flawlessly tested Google camera it works the best but not detecting fingerprint even after searching fingerprint it only shows up gestures's fingerprint in gestures's system menu PLZZ give me link of official Oreo build OPSS28.65-36-3 with Indian band so I could try to flash via fastboot and then recheck if custom roms fingerprint gets detected or not..
Update ur bootloader to Oreo one and then try flashing the rom
Surya Guduru said:
Update ur bootloader to Oreo one and then try flashing the rom
Click to expand...
Click to collapse
I don't have fastboot official oreo link can anyone give me plzz
hondraopranav said:
I don't have fastboot official oreo link can anyone give me plzz
Click to expand...
Click to collapse
U told u had the official 8.1 ROM ....in that ...... fastboot Flash bootloader bootloader.zip and fastboot flash modem non-hlos.bin
change the base of your fp to nougat base again
Hey check this out
Surya Guduru said:
U told u had the official 8.1 ROM ....in that ...... fastboot Flash bootloader bootloader.zip and fastboot flash modem non-hlos.bin
Click to expand...
Click to collapse
The OP didn't say they had the official 8.1 ROM, they said they had installed official Oreo. AFAIK There is no official 8.1 ROM for Sanders. Some people have taken the OTA for their device and repackaged it into an UNofficial flashable package, but that's not the same thing, and reportedly may be causing problems on EU & US variants, so I wouldn't recommend it.
I have the same problem with my FP reader.
I don't have an official 8.1 ROM (because there isn't one, lol), but I installed stock nougat 7.1.1 (retus, in my case) and then got the OTA upgrade to 8.1, after that fp+VoLTE are 100% working.
Then, as soon as I change to a custom 8.1 (or 9) ROM, VoLTE still works, but the fp is no longer recognized by the system.
If I flash back to stock nougat, FP comes back (and LTE breaks, but can be fixed by installing the 8.1 OTA upgrade again, or by getting to a root terminal and fixing permissions on /persist, I've personally verified both methods to restore functionality (assuming your /persist is unmolested - if it is, you're SoL).
Going from fully working official nougat or official Oreo, to any Oreo (or Pie) custom ROM still seems to break the FP reader again. I'm getting really tired of wiping my device...
Not A Solution #1
As suggested here: With FP + VoLTE working under official 8.1 OTA update, I installed TWRP & backed up /EFS, then installed my custom 8.1 ROM (Validus final) and restored the backed up /EFS, but instead of bringing my FP back, it just caused bootloop and I had to roll back to stock and start over. I skipped rolling back to Nougat before flashing custom, is that important? Why would it matter?
Not A Solution #2
After installing the custom 8.1 ROM I tried flashing the Nougat FP base. It had no effect.
Maybe A Solution? UPDATE: YES. A SOLUTION.
As suggested in this post:
1 - download the latest nougat stock rom (link removed - the correct one will vary depending on your device, up to you to obtain the correct firmware);
2 - unzip the above file and cd into the resulting directory;
3 - reboot your phone in fastboot mode;
4 - from terminal (linux or windows, in linux I had to do it as root user, using sudo), type:
fastboot flash bootloader bootloader.img <enter>
fastboot flash modem NON-HLOS.bin <enter>
fastboot reboot <enter>
By doing above steps, your phone should get fingerprint options back.
I did this, it worked, with one additional step - I had a pattern set before. After the fingerprint reader was 'reinstated' the pattern no longer worked. Rebooting into Recovery and flashing lockfix.zip removed the security so that I could set it up again properly. Find lockfix.zip in this post.

Moto G5s Plus October security update!!!

I've updated my moto g5s plus to 8.1.0 and the rooted with magisk and now I'm getting October security update OTA which I can not install due to twrp as recovery and of course because magisk have replaced my stock boot.img.
What I've already tried:
Uninstalling magisk (With the provided magisk uninstall.zip) (If I unstall magisk I get BAD_KEY error.)
Flashing stock recovery.img and boot.img through fastboot.
Flash it through flashify.apk
Flash OTa through twrp.
Flash it through ADB sideload.
None Worked till now.
Please help me to install october patch without re-flashing stock rom.
Same boat and have done everything you have. Last think i want to do is wipe and load pure stock and deal with backing up and restoring 200+ apps and data.

Bootloop after Realme UI

Recently I tried to flash Realme UI to my device using the ofps provided in the forum on the realme forums.
This resulted in a bootloop but since I had bootloader unlocked, I tried to flash the fastboot images, provided here.
This did not solve the bootloop issue.
In the end what I did to fix it was:
Download the stock firmware.
Extract the firmware files using Oppo_ozip_decrypt tool.
Install the official TWRP.
Install the firmware zip files using TWRP.
Download Links to official firmware:
RMX1992EX_11.A.19
RMX1992EX_11.A.18
RMX1992EX_11.A.17
NOTE:
These firmware links are for RMX1992 only. Make sure to download the firmware for your respective devices.
Well done
Will it work on rmx 1991?

Question Question about firmware and fastboot rom when downgrading

Hi, I am about to downgrade my sweet global from MIUI 14 to the latest version of MIUI 12 since I find it the most stable.
At the Xiaomi firmware updater site, I see firmware, vendor and rom.
I learnt that to downgrade, I need to use a fastboot rom. I donwloaded both the 12.5.9 fastboot rom and the corresponding 12.5.9 "firmware".
Do I need to flash firmware first before the fastboot rom? Or can I flash the fastboot rom directly?
And do I need to enable any extra options in the Mi Flash Tool before flashing?
Thank you for any information.

Categories

Resources