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)
Related
Hi I have a xt1803 G5S Plus, retgb and have recently unlocked bootloader and rooted my stock ROM which is NPSS26.116-26-14.
I have noticed there are higher version numbers available like NPS26.116-61. How do I go about having the latest stock ROM with twrp and root access? I'm guessing the stock ROMs are not flashable via twrp. Would I have to flash the latest stock ROM via ADB like it explained here
https://forum.xda-developers.com/mo...lash-official-firmware-moto-g5s-plus-t3681018
and then unlock bootloader again, flash twrp etc like starting from scratch?
I honestly would not recommend flashing NPS26.116-61 to your device. Despite the version number being higher, that firmware is actually for a different region (I think NPS26.116-61 series firmwares are for India and Indonesia, whereas the NPS26.116-26 series is for EU/UK). If you flash that, you may find yourself ineligible for OTA updates at all, since your build does not match that expected by the stock OTA servers, and if there are incompatibilities between the firmwares - since they are for different regions - you may have issues with IMEI/SIM access.
If you wanted to update though, you'd have to follow the steps in that guide. Though I don't have a G5S Plus, you would have to remove TWRP/root through a stock ROM flash (no need to re-lock bootloader), then update via OTA, then flash TWRP and re-root. If you can find a stock ROM with the same firmware build as you have now, you may be able to preserve your data by omitting the 'fastboot erase userdata' command from the stock ROM flash commands, but I would recommend you have a backup (e.g. TWRP backup) before flashing anything.
There's a copy of the NPSS26.116-26-18 stock ROM (June 2018 stock ROM) here, flash at your own risk: https://forum.xda-developers.com/showpost.php?p=77025728&postcount=507 This build was released as an OTA update to retgb devices as reported here: https://www.reddit.com/r/MotoG/comments/8w0c0c/june_patch_now_available_on_retgb/
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'm on the stock rom BAH2-W19 8.0.0.230 C431 in Germany and the unlock procedure doesn't work. I was wondering if downgrading to a previous version would let the unlocking procedure work and if it is required or not to maintain the same 'version' on the downgraded rom.
In short: on this firmware BAH2-W19 8.0.0.230 C431, can i flash a older one like BAH2-W19 8.0.0.179(C431) or maybe this other one BAH2-W19 8.0.0.217(OCEC432) ?
P4p3r1n0 said:
I'm on the stock rom BAH2-W19 8.0.0.230 C431 in Germany and the unlock procedure doesn't work. I was wondering if downgrading to a previous version would let the unlocking procedure work and if it is required or not to maintain the same 'version' on the downgraded rom.
In short: on this firmware BAH2-W19 8.0.0.230 C431, can i flash a older one like BAH2-W19 8.0.0.179(C431) or maybe this other one BAH2-W19 8.0.0.217(OCEC432) ?
Click to expand...
Click to collapse
Generally (well known for various other Huawei phones), submodel and cust must be followed.
They can be changed, aka rebranded, but only with unlocked Bootloader, since it requires flashing OEMInfo
Also, be careful when downgrading, if you go to an old version of Bootloader (usually it coincides to before GPU Torbo or firmwares with Security patch from the first half of 2018 or earlier), then it causes a serious brick.
To the other side, downgrading to the same Bootloader version does not help to ease getting the BL code.
Btw, Bootloader version can be inspected from a particular Hex address from xloader img, which can be extracted from update.app by Huawei UpdateExtracror (Windows program), that must be unzipped from update.zip, downloaded from a FullOTA firmware from FF
For that reason, people use Testpoints method to erase and then flash the old firmware (board image, if available for the particular device) to be able to downgrade the BL, and thus to be able to buy BL code the old way, simply based on providing IMEI and Serial number
zgfg said:
They can be changed, aka rebranded, but only with unlocked Bootloader
Click to expand...
Click to collapse
This means that the ROM i'd have to download has to be of the same branding (C431). At least here, to flash a C432 for downgrading would not work.
zgfg said:
be careful when downgrading, if you go to an old version of Bootloader
Click to expand...
Click to collapse
My intention was to downgrade the firmware so that it would flash a previous version of the bootloader. You understood the point
zgfg said:
unzipped from update.zip, downloaded from a FullOTA firmware from FF
Click to expand...
Click to collapse
What is FF ?
So, in short, if I really want to downgrade the firmware, I have to download a ROM from FF* of the same brand (C431), then extract the xloader img using the Extractor tool, compare this to my current version of the firmware and re-download any other ROM from FF until I see that the downloaded ROM has got a previous version of the bootloader. Flash this particular ROM. Is that correct?
I have not fully understood the "Testpoints method". Is it a real (documented) Method for flashing?
Thanks for your answer, it helped! Waiting now for this last feedback but until then, thank you!
P4p3r1n0 said:
This means that the ROM i'd have to download has to be of the same branding (C431). At least here, to flash a C432 for downgrading would not work.
My intention was to downgrade the firmware so that it would flash a previous version of the bootloader. You understood the point
What is FF ?
So, in short, if I really want to downgrade the firmware, I have to download a ROM from FF* of the same brand (C431), then extract the xloader img using the Extractor tool, compare this to my current version of the firmware and re-download any other ROM from FF until I see that the downloaded ROM has got a previous version of the bootloader. Flash this particular ROM. Is that correct?
I have not fully understood the "Testpoints method". Is it a real (documented) Method for flashing?
Thanks for your answer, it helped! Waiting now for this last feedback but until then, thank you!
Click to expand...
Click to collapse
FF = Firmware Finder.
Find a thread on XDA, search for XDA Huawei FirmwareFinder.
There is the FF apk on Playstore and FF exe for PC, you can also search firmwares directly from their server:
https://pro-teammt.ru/online-firmware-database-ru/
You don't really need to extract xloader.img (there is also a thread on XDA for Huawei Update Extractor and there was a thread for a special PC program analyzing the required bytes in xloader.img).
Instead, you can read Changelogs by FF, and you will see when there was the upgrade to GPU Turbo, and also which Google Security Patch is coming with which version.
Hence, in short - your intention was to 'cheat' by downgrafing to the old Bootloader, so that you can get the BL code easy and cheap.
Unfortunately, do not go for - you will brick your Huawei device.
(Many people tried similarly, with various Huawei phone models, and bricked them)
For TestPoints search similarly for XDA Huawei TestPoints. Generally, you have to physically open the phone, find the TestPoints pins (picturures can be found on the Net) on the motherboard, two of them have to be shortened
Then you will need a special Huawei loader and USB driver (there is one for Windows and one for Linux), and a board image to flash (there are sites on the Net selling the board images).
That way you can unbrick the phones or downgrade (as you wanted) to the older firmware (with the older Bootloader version)
P4p3r1n0 said:
My intention was to downgrade the firmware so that it would flash a previous version of the bootloader.
Click to expand...
Click to collapse
I realized there is not much to gain if I'd flash a previous bootloader. The original issue was that I thought I couldn't 'unlock' this one, instead I can and did it (check out the unlock thread).
All the others information are still useful, so thank you!
Why we need this ? :
It can be difficult to update firmware for custom ROM users since only the stock ROM contain it.
Is it risky to flash firmwares?
Yes. Firmware partitions are critical partitions and flashing it wrong or modifying this zip can lead to bricks that will only be solved by service centres.
Code:
Thus, a mandatory warning that i wont be responsible for any damages caused by the firmwares to your device and you will flash so on your own risks.
Which devices does it support ?
ONLY Realme XT (All variants) - Although i make the firmware with Indian updates.
When would you need to flash this?
Every time it's updated and whichever firmware the custom ROM supports. Although all custom ROMs are android 10 based now and you would be safe using any firmware only zip from C01 to C<whatever>.
Do i need to flash vbmeta?
No, the flashable zip already has it and it flashes disabled vbmeta on its own.
Does it contain kernel
Maybe. The older ones until the C05 update has stock kernel. I will be removing boot.img and dtbo.img from the zip from C06 onwards since accidentally booting with stock kernel can break encryption and destroy internal data since our custom kernel is way ahead of stock.
How do i make this zip myself?
If you aren't sure what you are doing, please avoid trying to make flashable zips for realme devices. Because, realme encrypts the firmwares and if you don't decrypt the firmware before flashing, it can cause a hard brick.
In brief, you simply decrypt the stock_update.ozip with bkerler's oppo_decrypt tool and replace the updater binary with pie ones. The reason why we replace the updater binary with pie ones is because the stock android 10 binary has decryptor built in whereas the pie ones does not. About what images to include, the zip itself is self explanatory.
Download folder :
https://www.androidfilehost.com/?w=files&flid=305713
Latest update : Stock realme UI C06 update
Last updated on : 05/08/20
Want to support & speed up the development?
You can donate to me.
PayPal :- pjgowtham
UPI :- UPI
I didn't understand! What is this archive for?
Firmware
How to install this ? Now I'm in C05 custom ROM please help me
Could you also make the firmware for/from the european version please?
Arno_Nuehm said:
Could you also make the firmware for/from the european version please?
Click to expand...
Click to collapse
The current firmware is tested and reported working on EU devices. But flash it at your own risk.
I just did the update to crDroid 6.9 with the latest frimware (C06) on my EU device and can confirm it works.
Thanks a lot!
C08 update is here :
C08_firmware_with_patched_vbmeta.zip | by pjgowtham for Realme XT
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
I flashed the F06 firmware and discovered that it overwrote the TWRP recovery I had earlier and I can't flash the latest one over it, simply doesn't boot. So I'm now stuck with the TWRP recovery that's bundled with F06 firmware. The device model name has been changed to nicky, instead of rmx1921 like before. Which maybe the reason official TWRP images don't work anymore.
Hello guys.
So I recently got a phone that's stuck with the August 2021 security patch. I wanna flash the latest software so had 2 questions:
1. Should I flash the most recent software update or considering I've never actually updated my phone, should I flash all the previous updates from August first before I flash the latest one.
2. I wanted to know if anyone has experience flashing SM-G998U1 firmware on a SM-G998U phone. I heard you can flash "U1" or carrier unlocked firmware on a "U" or carrier locked phone. Just that you'd lose all your data. I have an SM-G998U locked to Verizon and since I'm not in the US Verizon says they can't unlock it for me. So my only option is to flash new firmware updates. But I can't for the life of me find any Verizon SM-G998U firmware from after August 2021 (that's my latest security patch) online. So wanted to hear from anyone with experience that's flashed "U1" firmware on a "U" phone.
Flashing FW is no solution to unlock phones.
OnnoJ said:
Flashing FW is no solution to unlock phones.
Click to expand...
Click to collapse
I'm not trying to unlock my phone. It's usable cause it doesn't reject simcards. Just denies me OTA updates. All I want is new software.
Is there another option apart from flashing new firmware if I want to update it? I'd love to unlock the phone but all the websites keep talking about generating codes. My phone doesn't request a code. And I can still use it. If there isn't another option for unlocking, can you assist with the questions I've asked?
Fine to flash new firmware to get the latest.
1. If you flash complete FW using Odin, you can flash the latest, no need to flash intermediate updates.
2. Did you search the forum yourself? See following thread for FW versions of the US-devices: https://forum.xda-developers.com/t/...s-and-flashing-discussion-here.4220111/unread
OnnoJ said:
Fine to flash new firmware to get the latest.
1. If you flash complete FW using Odin, you can flash the latest, no need to flash intermediate updates.
2. Did you search the forum yourself? See following thread for FW versions of the US-devices: https://forum.xda-developers.com/t/...s-and-flashing-discussion-here.4220111/unread
Click to expand...
Click to collapse
Thanks so much for all the help Yeah I've seen that thread before. But only firmware available until November 2021. Nothing after. So think I'll try the U1 to U option for now.