Hello everyone, I need a little help. I bought a MiA2 in October 2018, which unlocked the bootloader, installed the Magisk module and changed the line of code through build.prop to get the Camera2Api. I was stuck in the November 2018 update and would like to know, in your opinion what would be the best method for me to have my device updated again and consequently get Android 9 installed?
GuiCv said:
Hello everyone, I need a little help. I bought a MiA2 in October 2018, which unlocked the bootloader, installed the Magisk module and changed the line of code through build.prop to get the Camera2Api. I was stuck in the November 2018 update and would like to know, in your opinion what would be the best method for me to have my device updated again and consequently get Android 9 installed?
Click to expand...
Click to collapse
Download the latest flashable from miui roms
http://en.miui.com/download-353.html
which is 10.0.8.0, clean flash it via Mi tool and after update via ota to 10.0.9.0. Important is at mi flash to check clean all not clean all and relock also not keep data because u r changing from oreo to pie. Other solution is to restore original boot.img, factory reset (because changing from oreo to pie) and update via ota to pie. You have to restore boot.img by flashing original boot.img via fastboot and not by magisk because causes bootloop. I think the clean flash is the better solution.
Related
I am owner of Moto G6 Plus but I have noticed the images others are uploading are "OPW" releases for Moto G6 Plus. I tried flashing one but I got error. Why my stupid phone have different builds, and what's the difference in "OPW" and "OPWS" builds. I guess I cannot use firmwares uploaded here? Any hope for me?
VarunAgw said:
I am owner of Moto G6 Plus but I have noticed the images others are uploading are "OPW" releases for Moto G6 Plus. I tried flashing one but I got error. Why my stupid phone have different builds, and what's the difference in "OPW" and "OPWS" builds. I guess I cannot use firmwares uploaded here? Any hope for me?
Click to expand...
Click to collapse
I have too "S" version and I flashed successfully OPW version from this thread https://forum.xda-developers.com/moto-g6/development/firmware-moto-g6-g6plus-t3789274 (after flashing OPW version it's still showing OPWS)
What error you are getting?
Mr. Nerd_ said:
I have too "S" version and I flashed successfully OPW version from this thread https://forum.xda-developers.com/moto-g6/development/firmware-moto-g6-g6plus-t3789274 (after flashing OPW version it's still showing OPWS)
What error you are getting?
Click to expand...
Click to collapse
I didn't flash the whole firmware. I tried patched boot.img with magisk. I got error something like "partition boot-1 doesn't exist".
VarunAgw said:
I didn't flash the whole firmware. I tried patched boot.img with magisk. I got error something like "partition boot-1 doesn't exist".
Click to expand...
Click to collapse
You probably need to use "mfastboot" instead of "fastboot" command. Download this: https://androidfilehost.com/?fid=962187416754477464
Unpack it and place the boot.img in same directory. Open Command Prompt in that directory. Correct command is: mfastboot flash boot bootimagename.img
Here you can also find the correct patched boot.img: https://forum.xda-developers.com/moto-g6/how-to/guide-magisk-patched-boot-image-opw27-t3794977
Got the S too
Hi,
I bought my new Motorola G6+ Evert last week here in Mexico. (where I live)
It's fully unblocked
Version PVT1, SKU XT1926-6
Running Oreo 8.0
But I wondered me about that Build Number.
While every tutorial is saying that I can just flash TWRP with that Build-Number : OPW27.113-45-4
Because I have: " OPWS27.113-25-4 "
I've upgradet OTA and it still says, that I have the latest security patch (1. June 2018) and so on....
So I wonder if I can unlock the bootloader, flash OPW27.113-45-4 or OPWS27.113-45-4 to be able to install TWRP Recovery from
https://forum.xda-developers.com/showpost.php?p=76501832&postcount=3
Purpose:
I can't wait to get my new babe rooted to install the real hot Stuff on it.
But it's still confusing why I got that different Build Number.... Maybe it's because of my location.
But i'am not shure if it is safe to root it and to flash SuperSU and TWRP. With my B-Number.
So may some one got the right Firmware for me ?
Sunny Greetings
B2DR
OPW27.113-45 is normal firmware.
OPWS27.113-45-4 is same firmware but with new security patch.
S for Security and 4 for revision version.
You can't install a previous version of the current on the device without unlocking the bootlader.
Junior Passos said:
OPW27.113-45 is normal firmware.
OPWS27.113-45-4 is same firmware but with new security patch.
S for Security and 4 for revision version.
You can't install a previous version of the current on the device without unlocking the bootlader.
Click to expand...
Click to collapse
And what about the "-25" vs "-45"? I have the same firmware here (Argentina): OPW27.113-25
Thanks!
Also what about this version OPW27.113-89 with security patch level 1 July 2018 for Australia.
I have updated pie with December security update now i want to roll back Oreo anyway downgrade p to o ?
Why
Sutanshu said:
I have updated pie with December security update now i want to roll back Oreo anyway downgrade p to o ?
Click to expand...
Click to collapse
ARB is enabled for Android Pie December security patch but it's Google ARB so this ARB is disabled when bootloader is unlocked so you can rollback to Oreo 9.6.16.0.ODIMIFE with fastboot (or using the EDL mode if you unlock flashing for critical with this command:
fastboot flashing unlock_critical
Click to expand...
Click to collapse
) when you use MiFlash and if your bootloader is unlocked
GuestK0087 said:
ARB is enabled for Android Pie December security patch but it's Google ARB so this ARB is disabled when bootloader is unlocked so you can rollback to Oreo 9.6.16.0.ODIMIFE with fastboot (or using the EDL mode if you unlock flashing for critical with this command:
) when you use MiFlash and if your bootloader is unlocked
Click to expand...
Click to collapse
Hi man,
Sorry to bother you,
But just wandering if you could help me out with Mi Flash Tool. Can we Flash OTA update through Mi Flash? Currently having Pie with November patch.
I couldn't update my phone.
Everytime it thru to install the update it gives error message like this"installation problem".
Big thanks bro with the help
I tried to install this fRomFuture ROM for my P10
[ROM] fRomFuture - Stock Rom L29 (B179) | XDA Developers Forums (xda-developers.com)
It worked perfectly, but then I tried to install the same dev's Oreo version, without realizing I need to update the "Firmware" (EMUI version?) first
[ROM] fRomFuture B370 | XDA Developers Forums (xda-developers.com)
That failed so I wiped, and tried to install the Stock fRomFuture. The install finishes without issue, but at first boot, the phone crashes, reboots and then goes "without issue" into the OS. But then the OS crashes after 1 minute and the phone reboots.
Wiping and reinstalling doesn't help anymore. Did I mess something up on my phone or the partitioning?
I unlocked the bootloader on EMUI 5.1 (Nougat) using DC-unlocker and installed TWRP 3.1.1-0 on it without issue.
I didn't update the "Firmware" to 8 or 9.
Also, forgive me, because this is my first Huawei and I don't understand anything of this "Firmware" talk that might have messed up my phone. I'm familiar with installing LineageOS on other phones such as Motorola's and Samsung's, but here it works totally different and caused me to bork my device?
I wiped the System and I have no back-up of my original Stock ROM
I tried this fix (HOWTA, rebranding), but it fails to install after the update.bat
dual sim functionality | XDA Developers Forums (xda-developers.com)
I also found sites giving the stock ROM in update.zip, but flashing that with TWRP fails.
Only ROM I can install is the one I mentioned above, but that keeps crashing now.
I'm really lost and registered here to get help. I don't want to abandon my "soft-brick" yet. The support on this device seems to be a little old, so I hope someone is still present.
Phone is VTR-L29C432. Build of fRomFuture is B179 (does that matter?)
UPDATE: (putting this for future reference in case it might help other people)
I managed to fix the issue by using a (more recent) HOWTA tool, a less buggy TWRP (3.1.1-0 instead of 3.1.0-0) and implementing update.zip, update_data_public.zip and update_all_hw.zip from build B185 into the update directory of the tool while flashing everything via fastboot.
System got restored to stock VTR-L29C432B185, latest Nougat build from 2018/01. Bootloader was locked again and twrp removed, but could be unlocked with same older code I purchased from DC Unlocker.
My only questions now is how to "correctly" install a custom rom like the OpenKirin for EMUI 8.1? First update firmware from EMUI 5.1 (Nougat) to 8.0 (Oreo) via with OTA before messing?
ThoriumNitride said:
UPDATE: (putting this for future reference in case it might help other people)
I managed to fix the issue by using a (more recent) HOWTA tool, a less buggy TWRP (3.1.1-0 instead of 3.1.0-0) and implementing update.zip, update_data_public.zip and update_all_hw.zip from build B185 into the update directory of the tool while flashing everything via fastboot.
System got restored to stock VTR-L29C432B185, latest Nougat build from 2018/01. Bootloader was locked again and twrp removed, but could be unlocked with same older code I purchased from DC Unlocker.
My only questions now is how to "correctly" install a custom rom like the OpenKirin for EMUI 8.1? First update firmware from EMUI 5.1 (Nougat) to 8.0 (Oreo) via with OTA before messing?
Click to expand...
Click to collapse
El codigo del bootloader sigue siendo el mismo
Hello,
as the titel mentiones, does the phone get OTA updates, stock Rom on it, if the bootloader is unlocked?
It does yes
Thank you
I will receive my Mi 11 (Cloud White) 8/256 next week, come from a OnePlus 8T (DL Unlocked & Magisk)
On OnePlus when an OTA was installed, for keep Magisk, after OTA installed and BEFORE restart phone, we reinstall Magisk with the Install > install in inactive slot/space (special after OTA) because Oneplus 8T use A/B partitions.
My question is simple, it's the same thing on the Mi 11 ? Useful for update officialy without lose Root or without need to reflash the patch boot/magisk
Hello, dear fellow 8i-Users!
I got this device just a few days ago. It is running on A32 global firmware and wasn't offered an OTA update.
So far, I have unlocked, rooted and installed TWRP, following the guide provided here.
As I like my phones to be encrypted, I guess I will stay with stock firmware so far. I'm finding it a bit sad though that I wasn't offered an OTA update and therefore am stuck with security patches dated back to November 2021.
Therefore my question: Does anyone happen to have decrypted versions of a newer version of global firmware? And if so: Is it possible to dirty flash these in TWRP?
Thank you!
Cheers,
VV
VIncentVegan said:
Is it possible to dirty flash these in TWRP?
Click to expand...
Click to collapse
I doubt it will be possible to flash full ROM through TWRP unless you prepare extra files (like scripts which do the actual work).
Anyway you can decrypt the official firmware (the ones in OFP-format) by youself and flash it with SPFlashTool.
Here are few hints for you:
Download the version you like from here.
Decrypt it with oppo_decrypt
Merge super.img for the region you need (refer to super_map.csv to find out which parts need to be merged; refer to this comment for instructions)
Flash with SPFlashTool in Download Only mode (refer to this guide)