Since a lot of people is asking for firmware files, OTAs, boot.img, I decided to collect all the resources here, so that it would be easier to get what you need.
First of all, you have to identify your ROM version. It is not the scope of this post to teach you how to use adb, so I suppose you already know.
Run adb shell getprop ro.build.oplus_nv_id and check the result with the table at the end of the post to know if you have the export or GDPR ROM.
Full (EDL mode) firmware downloads:This is the firmware you can also find on realmefirmware.com, but the website doesn't have all the versions.
Unfortunately, not all versions are available on the Realme servers, so if a firmware is not listed here, it's not available.
export firmware downloads:Android 12:RMX3301export_11_A.06_2022020500280000.zip
RMX3301export_11_A.08_2022022300070395.zip
RMX3301export_11_A.10_2022031419130229.zip
RMX3301export_11_A.11_2022031821250000.zip
RMX3301export_11_A.13_2022040705040000.zip
RMX3301export_11_A.14_2022041311050164.zip
RMX3301export_11_A.15_2022042701280000.7z
RMX3301export_11_A.16_2022052418230167.7z
RMX3301export_11_A.17_2022062222270183.7z
RMX3301export_11_A.18_2022072511110152.zip
RMX3301export_11_A.19_2022082205500000.zip
RMX3301export_11_A.21_2022092223350165.zip
Android 13:RMX3301export_11_C.08_2022102215440135.zip
RMX3301export_11_C.12_2022121600040215.zip
RMX3301export_11_C.13_2023010918370148.zip
RMX3301export_11_C.16_2023031621430000.zip
Android 13 (ColorOS 13.1):RMX3301export_11_C.18_2023050511080109.zip
RMX3301export_11_C.19_2023052220180130.zip
GDPR firmware downloads:Android 12:RMX3301GDPR_11_A.06_2022021320090088.zip
RMX3301GDPR_11_A.07_2022021800320350.zip
RMX3301GDPR_11_A.09_2022030402540000.zip
RMX3301GDPR_11_A.10_2022031818500135.zip
RMX3301GDPR_11_A.14_2022041414290143.zip
RMX3301GDPR_11_A.17_2022062222280000.7z
RMX3301GDPR_11_A.18_2022072511120000.zip
RMX3301GDPR_11_A.19_2022082205510000.zip
RMX3301GDPR_11_A.21_2022092223360000.zip
Android 13:RMX3301GDPR_11_C.08_2022102215410137.zip
RMX3301GDPR_11_C.12_2022121600050000.zip
RMX3301GDPR_11_C.13_2023010918380000.zip
RMX3301GDPR_11_C.16_2023031621420140.zip
Android 13 (ColorOS 13.1):RMX3301GDPR_11_C.18_2023050510510127.zip
RMX3301GDPR_11_C.19_2023052220190000.zip
Full OTA firmware downloads:You can install this directly from your phone, but it is specific for your nv_id, so if you can't find your ID here, use the full firmware if available or read below to get the URL by yourself.
India (IN) firmware downloads (nv_id = 00011011):Android 12:RMX3301_11.A.14_0140_202204131105: RMX3301_ROLL_BACK_Android12_IN.zip (Can be used to roll back from any future version)
RMX3301_11.A.15_0150_202204270128: 2620c0ef8b8d4057a77b7f114f18f1b9.zip
RMX3301_11.A.16_0160_202205241823: 9d61d0852808452091f4a552997a63ed.zip
RMX3301_11.A.17_0170_202206222227: a4b475a3f4b54619adfbcd36ca4282cd.zip
RMX3301_11.A.18_0180_202207251111: 24968044538344fbb0d34fbd21858e09.zip
RMX3301_11.A.19_0190_202208220550: 57fea9b57d4e4880b7ffb336bcd0d3ed.zip
RMX3301_11.A.21_0210_202209222335: 8b0fb5198b894a218d55d423355bd13e.zip
Android 13 Beta:RMX3301_11.C.01_1010_202205071838: RMX3301_11_C.01_Update_Android13_IN.zip (Android 13 DP1)
RMX3301_11.C.02_1020_202208152015: 3b232a024abc4168a24a0a7e4e24c879.zip (Official Trial Program)
RMX3301_11.C.05_1050_202209011105: 94662e8d4288490394eb240dd040f434.zip (Official Trial Program)
RMX3301_11.C.06_1060_202209192326: 0836f0a8968f4e10bc2dd123615a78b7.zip (Open Beta Program)
Android 13:RMX3301_11.C.08_1080_202210221544: 4ccc3d3cb837437ea787baaac853fc4d.zip
RMX3301_11.C.11_1110_202212121458: cdddcd5ba2c24a88bf8bf12ecb1b848c.zip
RMX3301_11.C.12_1120_202212160004: 2d60293ecc02486db514639c4493e73d.zip
RMX3301_11.C.13_1130_202301091837: bb2e8a1445c742e582a528399eb6d4e3.zip
RMX3301_11.C.16_1160_202303162143: 0389f0251b6243d99a8a23774df59022.zip
RMX3301_11.C.16_1160_202303162143: RMX3301_ROLL_BACK_Android13_IN.zip (Can be used to roll back from any future version)
Android 13 (ColorOS 13.1):RMX3301_11.C.18_1180_202305051108: b741fb43f5a94ffa981f440453ce5e8e.zip
RMX3301_11.C.19_1190_202305222018: 0d8de9b09a2e457a92726bdbcb8390ed.zip
RMX3301_11.C.20_1200_202306191319: 3fd59892f871401f9a4395994ebf6d47.zip
Android 14:RMX3301_11.F.01_3010_202304262041: RMX3301_11_F_OTA_3010_all_M5Kvg6_00011011.zip (Android 14 DP1)
Europe (EUEX) firmware downloads (nv_id = 01000100):Android 12:RMX3301_11.A.14_0140_202204141429: RMX3301_ROLL_BACK_Android12_EU.zip (Can be used to roll back from any future version)
RMX3301_11.A.15_0150_202204270129: 72db4088a1f34478bdc177d850ce3144.zip
RMX3301_11.A.16_0160_202205241824: 2f2b32b599734ca1975f8b95deb3dd0a.zip
RMX3301_11.A.17_0170_202206222228: c1db6ff9301c4de09773f1e1add9bd9d.zip
RMX3301_11.A.18_0180_202207251112: c97759dd1029491cae944ff1fadf8853.zip
RMX3301_11.A.19_0190_202208220551: beac418fbda441a786e58892b10f9538.zip
RMX3301_11.A.21_0210_202209222336: 1c78489d1868491c9e4c5d54369c7d8e.zip
Android 13 Beta:RMX3301_11.C.01_1010_202205071837: RMX3301_11_C.01_Update_Android13_EU.zip (Android 13 DP1)
RMX3301_11.C.02_1020_202206061202: RMX3301_11_C.02_Update_Android13_EU.zip (Android 13 DP2)
Android 13:RMX3301_11.C.08_1080_202210221541: 336d3d23e61d4839a2fdd21c8b9d56d7.zip
RMX3301_11.C.11_1110_202212121459: 7449aed556e444d3b369ef3458f95c1c.zip
RMX3301_11.C.12_1120_202212160005: 685a18388d0047a59c5d16fa16aa2ea5.zip
RMX3301_11.C.13_1130_202301091838: f3c7c3df25ce460399c7c47c608bf8c6.zip
RMX3301_11.C.16_1160_202303162142: 4fceb2d35bb9483ebc73043e00f90dad.zip
Android 13 (ColorOS 13.1):RMX3301_11.C.18_1180_202305051051: 5feda6c46e9649acb610be202d7869ab.zip
RMX3301_11.C.19_1190_202305222019: d3e80c6c535f427fa2e74ab2d31893c7.zip
How to get the latest OTA URL by yourself:You can use realme-ota to get the latest OTA for another nv_id or the ones above if I haven't updated this topic yet after a new update is released. Just keep in mind that, if the rollout is still ongoing, you may still get the previous version. Just wait a few days and try again.
For example, to get the latest TW OTA (nv_id = 00011010), run
Code:
realme-ota -r 0 RMX3301 RMX3301_11.A.00_0000_000000000000 3 00011010
You will find the URL near the top of the response.
How to extract images from EDL firmware package:
Extract the zip or 7z file
Use mct_ofp_extractor or oppo_decrypt to extract the OFP file
If you need to get super.img, open super_map.csv and take note of the files you have to merge for your nv_id
Use simg2img to merge your files like this (search online for the simg2img binary if you're on Windows):
Code:
simg2img super.0.xxxxxxxx.img super.1.xxxxxxxx.img super.2.xxxxxxxx.img super.img
If you need to extract super.img too, use lpunpack (please search online for the download and how to use it)
How to extract images from OTA zip files:
Extract the OTA zip file
Download and extract payload-dumper-go
Drag and drop payload.bin on payload-dumper-go executable
NV IDs table (needs confirmation):
RegionRegion abbreviationnv_id (HEX)nv_id (BIN)ROM typeNotesTaiwanTW1A00011010exportIndiaIN1B00011011exportIndonesiaID3300110011exportRussiaRU3700110111exportMalaysiaMY3800111000exportThailandTH3900111001exportPhilippinesPH3E00111110exportSaudi ArabiaSA8310000011exportLatin AmericaLATAM9A10011010exportBrazilBR9E10011110exportMiddle East and AfricaMEAA610100110exportEurope (EU, EEA, UK and Switzerland)EUEX4401000100GDPRUnited KingdomGB8A10001010GDPR1TurkeyTR5101010001GDPRRest of EuropeEU-NONEEA-Double8D10001101GDPRChinaALLNET9710010111domestic
Notes:
Only found in build C.08 through C.16 inclusive; identical to the EUEX one, but with the potential to differentiate some partitions.
very nice, l'm downloading. but...how did you find them? there are some special sites
Rapper_skull said:
Since a lot of people is asking for firmware files, OTAs, boot.img, I decided to collect all the resources here, so that it would be easier to get what you need.
First of all, you have to identify your ROM version. It is not the scope of this post to teach you how to use adb, so I suppose you already know.
Run adb shell getprop ro.build.oplus_nv_id and take note of the result.
If the result is 01000100, 01010001 or 10001101, you have the GDPR ROM installed, otherwise you have the export one.
Full (EDL mode) firmware downloads:This is the firmware you can also find on realmefirmware.com, but the website doesn't have all the versions.
Unfortunately, not all versions are available on the Realme servers, so if a firmware is not listed here, it's not available.
export firmware downloads:RMX3301export_11_A.06_2022020500280000.zip
RMX3301export_11_A.08_2022022300070395.zip
RMX3301export_11_A.10_2022031419130229.zip
RMX3301export_11_A.11_2022031821250000.zip
RMX3301export_11_A.13_2022040705040000.zip
RMX3301export_11_A.14_2022041311050164.zip
RMX3301export_11_A.15_2022042701280000.7z
RMX3301export_11_A.16_2022052418230167.7z
RMX3301export_11_A.17_2022062222270183.7z
GDPR firmware downloads:
RMX3301GDPR_11_A.06_2022021320090088.zip
RMX3301GDPR_11_A.07_2022021800320350.zip
RMX3301GDPR_11_A.09_2022030402540000.zip
RMX3301GDPR_11_A.10_2022031818500135.zip
RMX3301GDPR_11_A.14_2022041414290143.zip
RMX3301GDPR_11_A.17_2022062222280000.7z
Full OTA firmware downloads:You can install this directly from your phone, but it is specific for your nv_id, so if you can't find your ID here, use the full firmware if available.
India (IN) firmware downloads (nv_id = 00011011):RMX3301_11.A.14_0140_202204131105: RMX3301_ROLL_BACK_Android12_IN.zip (You can use this package to roll back from any future version)
RMX3301_11.A.15_0150_202204270128: 2620c0ef8b8d4057a77b7f114f18f1b9.zip
RMX3301_11.A.17_0170_202206222227: a4b475a3f4b54619adfbcd36ca4282cd.zip
RMX3301_11.A.18_0180_202207251111: 24968044538344fbb0d34fbd21858e09.zip
RMX3301_11.C.01_1010_202205071838: RMX3301_11_C.01_Update_Android13_IN.zip (Android 13 DP1)
Europe (EUEX) firmware downloads (nv_id = 01000100):RMX3301_11.A.14_0140_202204141429: RMX3301_ROLL_BACK_Android12_EU.zip (You can use this package to roll back from any future version)
RMX3301_11.A.15_0150_202204270129: 72db4088a1f34478bdc177d850ce3144.zip
RMX3301_11.A.16_0160_202205241824: 2f2b32b599734ca1975f8b95deb3dd0a.zip
RMX3301_11.A.17_0170_202206222228: c1db6ff9301c4de09773f1e1add9bd9d.zip
RMX3301_11_A.18_0180_202207251112: c97759dd1029491cae944ff1fadf8853.zip
RMX3301_11.C.01_1010_202205071837: RMX3301_11_C.01_Update_Android13_EU.zip (Android 13 DP1)
RMX3301_11.C.02_1020_202206061202: RMX3301_11_C.02_Update_Android13_EU.zip (Android 13 DP2)
Click to expand...
Click to collapse
i finished downloading the complete rom.
I put payload.bin in input in payload_dumper, but in output it only picks me up:
hyp.img
my_manifest.img
xbl_ramdump.img
to fetch the boot?
sorry i'm bothering you so much, but i'm stuck here
marco.chinagliaxx91 said:
i finished downloading the complete rom.
I put payload.bin in input in payload_dumper, but in output it only picks me up:
hyp.img
my_manifest.img
xbl_ramdump.img
to fetch the boot?
sorry i'm bothering you so much, but i'm stuck here
Click to expand...
Click to collapse
I updated the post with the payload dumper I use. Please try it.
Rapper_skull said:
I updated the post with the payload dumper I use. Please try it.
Click to expand...
Click to collapse
when i downloaded the rom, a18 in the phone settings with a file manager i was able to download ota, but i had the same problem that i described above. I didn't know you had to use payload - go. You saved my life man. Now I know how. I promise that with each update I will post the updated files.
Excellent thread. Include Export firmware OTA also if possible
shivrajsingh said:
Excellent thread. Include Export firmware OTA also if possible
Click to expand...
Click to collapse
OTAs are not divided in export and GDPR, but by nv_id. There are OTA links for India in the post, and that's one of the many export nv_ids. Unfortunately, I can not keep track of every nv_id, because there are too many.
Rapper_skull said:
OTAs are not divided in export and GDPR, but by nv_id. There are OTA links for India in the post, and that's one of the many export nv_ids. Unfortunately, I can not keep track of every nv_id, because there are too many.
Click to expand...
Click to collapse
if you want we can do that at each update I take care of the EU.
I create a folder on mega sorted.
Each folder will have the name of the firmware, in it I will put that firmware
boot_stock.img
vbmeta.img
magisk.img
and two bat files
stock_boot.bat
magisk_boot.bat
that I created, just run it to give root permissions or restore the original boot. Whether the phone is on or in fastboot it will be the same. In the bat I have thought of everything. A little thank you here
marco.chinagliaxx91 said:
if you want we can do that at each update I take care of the EU.
I create a folder on mega sorted.
Each folder will have the name of the firmware, in it I will put that firmware
boot_stock.img
vbmeta.img
magisk.img
and two bat files
stock_boot.bat
magisk_boot.bat
that I created, just run it to give root permissions or restore the original boot. Whether the phone is on or in fastboot it will be the same. In the bat I have thought of everything. A little thank you here
Click to expand...
Click to collapse
All users who flashed from China Rom to Global Rom have that particular Export version. They are mostly rooted and get OTA late. So ota link may be beneficial for them.
How to check NV ID?
shivrajsingh said:
All users who flashed from China Rom to Global Rom have that particular Export version. They are mostly rooted and get OTA late. So ota link may be beneficial for them.
How to check NV ID?
Click to expand...
Click to collapse
not so answer you. I have eu firmware
I'm marco.chinagliaxx91. This Is my real account. Now i can use a gt2pro
shivrajsingh said:
All users who flashed from China Rom to Global Rom have that particular Export version. They are mostly rooted and get OTA late. So ota link may be beneficial for them.
How to check NV ID?
Click to expand...
Click to collapse
getprop ro.build.oplus_nv_id
Rapper_skull said:
getprop ro.build.oplus_nv_id
Click to expand...
Click to collapse
Its 00011010
shivrajsingh said:
Its 00011010
Click to expand...
Click to collapse
That is the TW (Taiwan) ROM. I suggest migrating to the IN ROM, since it is also the default region. In any case, I updated the first post with instructions on how to get the latest OTA URL by yourself.
Maybe in the future I will write a script to get all the URLs automatically.
I get 10100110. Does this mean I have the IN version?
when I try realme-ota -r 0 RMX3301 RMX3301_11.A.00_0000_000000000000 3 10100110 it gives me a few lines:
Load payload for RMX3301 (RealmeUI V3)
Wait for the endpoint to reply
Response status mismatch, expected '200' got '500'!
I am trying to get the firmware for my phone because ever since I took the A.18 update my phones Widevine was downgraded to L3. I am hoping A18 just messed something up in update process and flashing the A17 stock rom then rerooting will fix it.
GIutton said:
I am trying to get the firmware for my phone because ever since I took the A.18 update my phones Widevine was downgraded to L3. I am hoping I just messed something up in update process and flashing the stock rom then rerooting will fix it.
Click to expand...
Click to collapse
Widewine degrades to L3 by flashing Global and there is no official fix.
EDIT: Typo, degrades to L3, not L1
Quake94 said:
Widewine degrades to L1 by flashing Global and there is no official fix.
Click to expand...
Click to collapse
But I have never flashed any roms to the phone. Have rooted with magisk and only ever used the stock OTA updates from "about phone"
GIutton said:
But I have never flashed any roms to the phone. Have rooted with magisk and only ever used the stock OTA updates from "about phone"
Click to expand...
Click to collapse
After unlocking bootloader, how did you root your phone? Did you flash a patched boot.img over the stock ROM?
No I booted the phone with a magisk patched boot.img then did a direct install using the magisk app on stock A.17. I had wideine L1 until I took the A.18 official OTA for my phone then it went to L3. It was an incremental update. To go from A.17 to A.18 I used magisk > uninstall magisk > restore images. Then downloaded and installed the OTA, took a copy of the boot.img from the inactive slot and patched it with magisk and copied to PC. Then I restored root with magisk direct install, turned on airplane mode, rebooted the phone from the System Update Dialog "install" then rebooted to bootloader and used fastboot boot magisk-patched-boot.img and then used magisk to do a direct install to make root permanent.
I had to unroot the phone and relock the bootloader in order to get back to Widevine L1. Maybe I am just wrong and it went to L3 right after I unlocked the bootloader. Has anyone been able to keep Widevine L1 with an unlocked bootloader and Magisk rooted?
Related
Consider one day you upset the devil and your phone is bricked by him, lets try to revive the phone from hell (at your own risk) :
Link to the OTA firmware's :
Click here for the links page
Important tools links:
[TOOL] Huawei Multi-Tool v8 by Team MT by inside!out
TWRP Honor 7X img
Stage 1
Download from here everything you need for the procedure - Download Folder Link
I am testing it on my BND-L21 firmware from BND-AL10
Downloading firmware (from topic). Full firmware must be more than 1.5Gb, all smaller is just
OTA Updates to the system.
After that we must download Huawei-MultiTool (future MT) version 8.x.x (link topic)
and downloading custom recovery. We will use TWRP for Honor7x (link topic)
Last we must prepare OTG Cable, SD Card more than 4Gb. On first stage that's all.
Stage 2
Go to MT and reboot phone to Fastboot mode (while phone off, hold "Volume -" and power)
If you did all correctly, you will see in the down right side your number and "Fastboot".
Now go in MT to the Bootloader and check the status. If you have already unlocked, skip this.
If you have locked phone, you must have IMEI and Huawei account. (if not please unlock your bootloader via the Huawei site)
After that, go to Recovery menu and choose our TWRP image in "Custom recovery" section and
type "Recovery". IMPORTANT!!! DON'T FLASH ERECOVERY, I DON'T HAVE THIS IMAGE!!!
After flashing recovery, we must turn off our phone.
Now we must to prepare base system image. In archive we have UPDATE.ZIP file. extract this
file to custom folder and open "Unbrick" in MT and choose "extractor". Open our file in extractor
and click right mouse key on empty space, choose extract all... and choose custom folder to
extracting.
Go to the folder and copy file VENDOR.IMG to the SD-Card (or USB with OTG). Turn on your
device in Recovery mode (Volume + and power), choose Wipe and Wipe ALL partitions! After
doing this, go to Install and choose "Install img", go to the SD-Card, and install VENDOR.img to
VENDOR folder (Important!)
After installing reboot phone again to Fastboot mode and connect to PC.
Now we must download .zip update to your region. We need this for using LTE (4G) in your country + Localization.
After downloading open .zip archive with our CUST file. archive must be called update_BND-
YOUR-NUMBER_hw_YOUR- COUNTRY.zip
From this archive we must extract .img file from root folder. It can be called cust.img CUST.img
version.img etc.
if name different from CUST.img rename it and put to the extracted UPDATE.app folder.
Last Stage 3
In MT go to Unbrick, choose our unpacked system with our CUST file and we must have at least
4/5 checkbox. And just type "UNBRICK" and wait. NOTICE: at moment of extracting system.img
it will be about 10-15 minutes. It's not a freezing of PC)
After good installing in log you will see like "All ok" Just reboot phone and you will see low level
factory reset, or something else like formatting. After formatting phone will reboot to the system.
That's all
Flashing Gapps method coming soon...
Password - 4pda for the update_full_bnd-AL10... Zip
Special Thanks to Kallibr44 my friend who helped me decipher everything. :highfive:
HIT THANKS IF I HELPED YOU IT MAKES ME HAPPY
We need a Full Firmware Package for L21,this is only Ota Updates.
letschky said:
We need a Full Firmware Package for L21,this is only Ota Updates.
Click to expand...
Click to collapse
there is a procedure used by EU users to completely revive the phone using the OTA but the procedure is too long which i haven't tried yet and is completely for users who have dead phones for now and yes obviously there is no official firmware available for Honor 7x but the user from an EU forum revived his phone so it is possible from the images.
though i made this thread for users who want to update their firmwares and not the procedure to flash a stock firmware since there is not one available yet but i can point to the thread where this user posted the procedure if someone wants to try. PM me
sid21 said:
i can point to the thread where this user posted the procedure if someone wants to try. PM me
Click to expand...
Click to collapse
Yes please....
fmotta said:
Yes please....
Click to expand...
Click to collapse
Sent reply.
There are teams who have unlocked a lot of stuff like flashing international FW,
flashing gapps on chinese fw, Automatic Call Recording, restoring the phone.
so i am in contact with them to make our phone better. lets keep our fingers crossed. :fingers-crossed:
i am waiting for firmware flashing to get it translated from one of the users.
This is the full recovery package right? Atleast for the Indian version?
TheDj408 said:
This is the full recovery package right? Atleast for the Indian version?
Click to expand...
Click to collapse
They arent recovery packages. they are full OTA which can be flashed for updating.
but there is a process to compile them into making them stock firmware packages but due to the long procedure i didnt post it here. rather wait for official stock firmware package.
sid21 said:
Hello Honor 7X Users, turns out there is firmware available for flashing for the AL10 and L21 variants
but i haven't tried them out and can post the procedure if someone needs it but all credit goes to PRO-TEAMMT for releasing them for us so now if we mess up we got official firmware's latest available to go back to.
I personally haven't tested any but i soon will.
Link to the firmware's :
Click here for the links page
Important tools :
[TOOL] Huawei Multi-Tool v8 by Team MT by inside!out
TWRP Honor 7X img
Steps : (Considering you have unlocked bootloader and flashed twrp)
1. Download the appropriate firmware as per your model (Link to the website given)
2. Clear Cache
3. Flash the firmware file
(Wait for the complete process to flash a firmware from scratch so that i can do it and confirm myself but if anybody tests before me let me know)
Refer to the thread by inside!out for any help till them if you want to try out
Click to expand...
Click to collapse
Hi
I am a New in Android world
I have honor 7x BND L21c185b101
And i rooted
Know exactly do this?
Step 3 how?
And the multi tool For what?
sid21 said:
there is a procedure used by EU users to completely revive the phone using the OTA but the procedure is too long which i haven't tried yet and is completely for users who have dead phones for now and yes obviously there is no official firmware available for Honor 7x but the user from an EU forum revived his phone so it is possible from the images.
though i made this thread for users who want to update their firmwares and not the procedure to flash a stock firmware since there is not one available yet but i can point to the thread where this user posted the procedure if someone wants to try. PM me
Click to expand...
Click to collapse
Can I have the procedure link?
I ordered a 7X from AliExpress.
I also own an Honor 5X & errrmmmm.. I'm not a developer rather still a learning buildbot ? still I want to take part in bringing up LOS or AOSP for Honor 7X. So we can work on it together if you want. ?
Cheers!
P.S. Belated Merry Christmas.
tootysa said:
Hi
I am a New in Android world
I have honor 7x BND L21c185b101
And i rooted
Know exactly do this?
Step 3 how?
And the multi tool For what?
Click to expand...
Click to collapse
exactly what you want to do?
this is to update to the latest firmware. if you have the latest firmware you dont need it.
the multi tool is used to flash stock with a procedure which is only needed to return to stock or else theres no need for it for the most part..
mumith3 said:
Can I have the procedure link?
I ordered a 7X from AliExpress.
I also own an Honor 5X & errrmmmm.. I'm not a developer rather still a learning buildbot ? still I want to take part in bringing up LOS or AOSP for Honor 7X. So we can work on it together if you want.
Cheers!
P.S. Belated Merry Christmas.
Click to expand...
Click to collapse
PM Sent kindly check.
sid21 said:
Hello Honor 7X Users, turns out there is firmware available for flashing for the AL10 and L21 variants
but i haven't tried them out and can post the procedure if someone needs it but all credit goes to PRO-TEAMMT for releasing them for us so now if we mess up we got official firmware's latest available to go back to.
I personally haven't tested any but i soon will.
Link to the firmware's :
Click here for the links page
Important tools :
[TOOL] Huawei Multi-Tool v8 by Team MT by inside!out
TWRP Honor 7X img
Steps : (Considering you have unlocked bootloader and flashed twrp)
1. Download the appropriate firmware as per your model (Link to the website given)
2. Clear Cache
3. Flash the firmware file
(Wait for the complete process to flash a firmware from scratch so that i can do it and confirm myself but if anybody tests before me let me know)
Refer to the thread by inside!out for any help till them if you want to try out
Click to expand...
Click to collapse
HI I wanna know many things:
1-if I can constantly update the 7x with the application (or the software on PC, is the same) "Firmware Finder" even if I don't recive the official OTAs (because I want to root my device)
2-if its possible upgrade the system via OTA (or Firmware finder etc...) when the device is rooted
3-is dangerous root the Honor 7x?
4-if I can upgrade the system when the device Is rooted via the software HiSuite
5- how/where can I do/find and restore a Nandroid Backup for my phone
6-where I can find a local/manual update (UPDATE. APP) for the 7x (in case a brick the phone)
7-how can i UNBRICK my phone I case of brick
(sorry for my bad english?)
PLEASE HELP ME??
Thanks
Lambo™ said:
HI I wanna know many things:
1-if I can constantly update the 7x with the application (or the software on PC, is the same) "Firmware Finder" even if I don't recive the official OTAs (because I want to root my device)
2-if its possible upgrade the system via OTA (or Firmware finder etc...) when the device is rooted
3-is dangerous root the Honor 7x?
4-if I can upgrade the system when the device Is rooted via the software HiSuite
5- how/where can I do/find and restore a Nandroid Backup for my phone
6-where I can find a local/manual update (UPDATE. APP) for the 7x (in case a brick the phone)
7-how can i UNBRICK my phone I case of brick
(sorry for my bad english?)
PLEASE HELP ME??
Thanks
Click to expand...
Click to collapse
1) ???
2) Not sure there is always a chance of bricking
3) Yes, if you don't know what you're doing. No if you're not going to be flashing anything.
4) You should be able to and also refer to #1.
5) None available
6) None available
7) You can't, no stock image released = no procedures to unbrick
Soapy! said:
1) ???
2) Not sure there is always a chance of bricking
3) Yes, if you don't know what you're doing. No if you're not going to be flashing anything.
4) You should be able to.
5) None available
6) None available
7) You can't, no stock image released = no procedures to unrbcik
Click to expand...
Click to collapse
1- can i upgrade the system at every update (when the device is rooted) with Firmware finder many times even if I don't recive the notification on the phone of the update (or if the device updater cannot find it)?
2-ok but if do all right steps you cannot brick the phone, no?
3-ok i only wanna unlock bootloader, flash twrp and root the phone. If I do all right steps there are no risks, no?
4-i don't understand it (in hisuite there s the option that says "Update device". With the device rooted can I update the phone with this software?)
5-ok but can I do one with a custom recovery, no?
6-ok so we just have to wait, no?
7-ok. Same thing of the - 6 (we have to wait for the UPDATE.APP for the 7x to be able to UNBRICK the phone in case it could happen, no?)
Sorry for my bad English and thanks for the answers?
Lambo™ said:
HI I wanna know many things:
1-if I can constantly update the 7x with the application (or the software on PC, is the same) "Firmware Finder" even if I don't recive the official OTAs (because I want to root my device)
2-if its possible upgrade the system via OTA (or Firmware finder etc...) when the device is rooted
3-is dangerous root the Honor 7x?
4-if I can upgrade the system when the device Is rooted via the software HiSuite
5- how/where can I do/find and restore a Nandroid Backup for my phone
6-where I can find a local/manual update (UPDATE. APP) for the 7x (in case a brick the phone)
7-how can i UNBRICK my phone I case of brick
(sorry for my bad english)
PLEASE HELP ME
Thanks
Click to expand...
Click to collapse
1. yes you can if the app supported honor 7x with their firmware but it doesn't yet, use twrp
2. yes you can upgrade via flashing it in twrp
3. unlocking bootloader itself is dangerous let alone rooting since your waranty is gone since there is still no sign of official stock firmware
4. same as no. 1 ans
5. if u flashed twrp you can do your nandroid backup which can be later restored anytime so it will be obv on the phone at that time
6. manual or local update? in the op main post i guess? by opening the link?
7. Still no official firmware and the procedure i am aware of consists of turning the official chinese firmware into normal by changing settings and stuff which is a long procedure so probably if u brick, u r stuck until honor decides to release stock firmware
by the looks i guess you have no clue about phone flashing, its better you dont try anything until there are guides properly made for newbies. :silly:
sid21 said:
1. yes you can if the app supported honor 7x with their firmware but it doesn't yet, use twrp
2. yes you can upgrade via flashing it in twrp
3. unlocking bootloader itself is dangerous let alone rooting since your waranty is gone [emoji14] since there is still no sign of official stock firmware
4. same as no. 1 ans
5. if u flashed twrp you can do your nandroid backup which can be later restored anytime so it will be obv on the phone at that time
6. manual or local update? in the op main post i guess? by opening the link?
7. Still no official firmware and the procedure i am aware of consists of turning the official chinese firmware into normal by changing settings and stuff which is a long procedure so probably if u brick, u r stuck until honor decides to release stock firmware
by the looks i guess you have no clue about phone flashing, its better you dont try anything until there are guides properly made for newbies. :silly:
Click to expand...
Click to collapse
Thanks lol [emoji23]
Sent from my BND-L24 using Tapatalk
I rooted my 7X(Al10) version successfully but while performing the reset, deleted the system file also by mistake. There is no TWRP backup. Is there any way to get the stock OS files again to flash in TWRP ? Or does anyone have a backup file they made that they can share? I tried Huawei e-recovery too, but that gets stuck at 'unable to get package info'. The people at the service centre can't think of any other method to restore the phone, except changing the motherboard. When is the official stock file expected to be available?
GC95 said:
I rooted my 7X(Al10) version successfully but while performing the reset, deleted the system file also by mistake. There is no TWRP backup. Is there any way to get the stock OS files again to flash in TWRP ? Or does anyone have a backup file they made that they can share? I tried Huawei e-recovery too, but that gets stuck at 'unable to get package info'. The people at the service centre can't think of any other method to restore the phone, except changing the motherboard. When is the official stock file expected to be available?
Click to expand...
Click to collapse
I have a TWRP backup not sure if it'll work, https://drive.google.com/file/d/1EntdgNwcJSOTZizqt_W-yWfkd3-YVmCm/view?usp=drivesdk
It's a zip file with 2 backup folder, one with boot and system and one with vendor
Edit: pls thank if it worked, so I have an indicator of the effectiveness
GC95 said:
I rooted my 7X(Al10) version successfully but while performing the reset, deleted the system file also by mistake. There is no TWRP backup. Is there any way to get the stock OS files again to flash in TWRP ? Or does anyone have a backup file they made that they can share? I tried Huawei e-recovery too, but that gets stuck at 'unable to get package info'. The people at the service centre can't think of any other method to restore the phone, except changing the motherboard. When is the official stock file expected to be available?
Click to expand...
Click to collapse
I am waitinig for the official stock file since two weeks now, because I deleted accidently the OS from my phone -_-
I think we can wait several weeks again...
---------- Post added at 12:04 PM ---------- Previous post was at 12:03 PM ----------
Jan.Pul said:
I have a TWRP backup not sure if it'll work, https://drive.google.com/file/d/1EntdgNwcJSOTZizqt_W-yWfkd3-YVmCm/view?usp=drivesdk
It's a zip file with 2 backup folder, one with boot and system and one with vendor
Click to expand...
Click to collapse
Thanks! I will try on my bricked phone
sid21 said:
1. yes you can if the app supported honor 7x with their firmware but it doesn't yet, use twrp
2. yes you can upgrade via flashing it in twrp
3. unlocking bootloader itself is dangerous let alone rooting since your waranty is gone since there is still no sign of official stock firmware
4. same as no. 1 ans
5. if u flashed twrp you can do your nandroid backup which can be later restored anytime so it will be obv on the phone at that time
6. manual or local update? in the op main post i guess? by opening the link?
7. Still no official firmware and the procedure i am aware of consists of turning the official chinese firmware into normal by changing settings and stuff which is a long procedure so probably if u brick, u r stuck until honor decides to release stock firmware
by the looks i guess you have no clue about phone flashing, its better you dont try anything until there are guides properly made for newbies. :silly:
Click to expand...
Click to collapse
1. In the app firmware finder there are firmwares for the phone but how can I flash a official firmware (OTA I mean) if there are no one (or how can I flash a firmware finder Update)?
2. Same thing in -1 (I mean)
3. Ok. Now we have to wait the official stock firmware, no? (i don't understand this answer, please write it in another way)
4. I don't understand it
5. Okok (obv? Sorry I'm Italian hahaha)
6. It's not the same thing local or manual? Write it in another way please hahaha google translate doesnt help me?
7. Okok, So if I don't use your method I only have to wait that honor release the official stock firmware (UPDATE. APP). And for greater security it's better wait it before to root and unlock bootloader etc, no?
Anyway, I have an idea of what flashing is, in fact every device I have (they are all Samsung, so that's why I'm disoriented) is completely modified. The fact is that I dont have much experience (I'm 14 years old) with non-Samsung devices, in fact my honor 7x I received for Christmas and for the hurry and the want to modify it, I would like to know all these things.
Thank you
---------- Post added at 02:25 PM ---------- Previous post was at 02:23 PM ----------
k0pernicus said:
I am waitinig for the official stock file since two weeks now, because I deleted accidently the OS from my phone -_-
I think we can wait several weeks again...
---------- Post added at 12:04 PM ---------- Previous post was at 12:03 PM ----------
Thanks! I will try on my bricked phone
Click to expand...
Click to collapse
OK thanks I'll keep it aside in case of brick
I would recommend everyone to not do experiments over your phone to try and root and flash random stuff..
they only have official chinese firmware for flashing so its better to wait for the official firmware for non chinese version.
the method which i know of to flash on the phone is for people with flashing knowledge cz the procedure is not simple and secondly even i have been flashing my phone for many years on various devices yet i havent got the guts to root this first honor device cz their partitions are different and somewhat secured so dont play with it.
wait for the official firmware for your respective devices. maybe they will straightaway launch the oreo firmware.
Heeyy guys,
I have a question.
First time using huawei devices and can say that it's quite a hassle. Did brick my phone already once and afraid to do it again.
I got the update notification for the 8.0.0.142 firmware but I have twrp installed so I can't update though the Ota.
I want to do an clean install with the latest update but I'm reading that the bootloader can go locked again. Now with Huawei not providing a bootloader unlock I find it a bit tricky because I really need Magisk.
My question is.
Will someone be so kind as to help me out?
Info:
Huewei Mate 10 Pro
BLA-L29 8.0.0.137 (C432) (Current version)
TWRP Recovery installed.
Balthazard said:
Heeyy guys,
I have a question.
First time using huawei devices and can say that it's quite a hassle. Did brick my phone already once and afraid to do it again.
I got the update notification for the 8.0.0.142 firmware but I have twrp installed so I can't update though the Ota.
I want to do an clean install with the latest update but I'm reading that the bootloader can go locked again. Now with Huawei not providing a bootloader unlock I find it a bit tricky because I really need Magisk.
My question is.
Will someone be so kind as to help me out?
Info:
Huewei Mate 10 Pro
BLA-L29 8.0.0.137 (C432) (Current version)
TWRP Recovery installed.
Click to expand...
Click to collapse
If you have unlocked previously, I don't see your problem do full update and then unlock again your bootloader unlock code won't have changed from last time.
Balthazard said:
Heeyy guys,
I have a question.
First time using huawei devices and can say that it's quite a hassle. Did brick my phone already once and afraid to do it again.
I got the update notification for the 8.0.0.142 firmware but I have twrp installed so I can't update though the Ota.
I want to do an clean install with the latest update but I'm reading that the bootloader can go locked again. Now with Huawei not providing a bootloader unlock I find it a bit tricky because I really need Magisk.
My question is.
Will someone be so kind as to help me out?
Info:
Huewei Mate 10 Pro
BLA-L29 8.0.0.137 (C432) (Current version)
TWRP Recovery installed.
Click to expand...
Click to collapse
I've yet to come across any fw that lock again on Oreo. On Nougat this was standard.
And I have b142 installed and it didn't lock
You can however, if you don't want to flash back stock recovery, flash using HuRUpdater using TWRP.
https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
I've tested it and it works if you're using TWRP by pretoriano80, as it has some stuff needed that "official" TWRP by dees_troy doesn't have.
You can find it here if you don't have it already: https://forum.xda-developers.com/mate-10/development/huawei-mate-10-pro-twrp-3-2-1-0-t3769904
Edit: As for update files; you can either use Firmware Finder app to download them to phone, then rename them to what the thread says (update_data_full_public.zip to update_data_public.zip and hw zip to update_all_hw.zip). Or you can use the site http://pro-teammt.ru/firmware-database/
There you just search for the update, BLA-L29C432, then click on the File list link in the FullOTA row. Copy paste links there into a new tab and download, then rename files and transfer to phone.
To get TWRP to stick, place the TWRP image in the same folder as you have HuRupdater.zip script and rename it to recovery.img, then it will flash it back after it has done update.
ante0 said:
I've yet to come across any fw that lock again on Oreo. On Nougat this was standard.
And I have b142 installed and it didn't lock
You can however, if you don't want to flash back stock recovery, flash using HuRUpdater using TWRP.
https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
I've tested it and it works if you're using TWRP by pretoriano80, as it has some stuff needed that "official" TWRP by dees_troy doesn't have.
You can find it here if you don't have it already: https://forum.xda-developers.com/mate-10/development/huawei-mate-10-pro-twrp-3-2-1-0-t3769904
Edit: As for update files; you can either use Firmware Finder app to download them to phone, then rename them to what the thread says (update_data_full_public.zip to update_data_public.zip and hw zip to update_all_hw.zip). Or you can use the site http://pro-teammt.ru/firmware-database/
There you just search for the update, BLA-L29C432, then click on the File list link in the FullOTA row. Copy paste links there into a new tab and download, then rename files and transfer to phone.
To get TWRP to stick, place the TWRP image in the same folder as you have HuRupdater.zip script and rename it to recovery.img, then it will flash it back after it has done update.
Click to expand...
Click to collapse
That did the trick completely!
Thank you so much for your time and effort!
It went smoothly and nicely and I'll stick to this method for future updates.
ante0 said:
I've yet to come across any fw that lock again on Oreo. On Nougat this was standard.
And I have b142 installed and it didn't lock
You can however, if you don't want to flash back stock recovery, flash using HuRUpdater using TWRP.
https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
I've tested it and it works if you're using TWRP by pretoriano80, as it has some stuff needed that "official" TWRP by dees_troy doesn't have.
You can find it here if you don't have it already: https://forum.xda-developers.com/mate-10/development/huawei-mate-10-pro-twrp-3-2-1-0-t3769904
Edit: As for update files; you can either use Firmware Finder app to download them to phone, then rename them to what the thread says (update_data_full_public.zip to update_data_public.zip and hw zip to update_all_hw.zip). Or you can use the site http://pro-teammt.ru/firmware-database/
There you just search for the update, BLA-L29C432, then click on the File list link in the FullOTA row. Copy paste links there into a new tab and download, then rename files and transfer to phone.
To get TWRP to stick, place the TWRP image in the same folder as you have HuRupdater.zip script and rename it to recovery.img, then it will flash it back after it has done update.
Click to expand...
Click to collapse
Can the phone be rooted too and be able to install an update? Or would I have to unroot it first?
Sent from my BLA-A09 using Tapatalk
KevinAce said:
Can the phone be rooted too and be able to install an update? Or would I have to unroot it first?
Sent from my BLA-A09 using Tapatalk
Click to expand...
Click to collapse
No need to unroot. You will, however, need to flash Magisk again after update as ramdisk is replaced with stock one.
ante0 said:
No need to unroot. You will, however, need to flash Magisk again after update as ramdisk is replaced with stock one.
Click to expand...
Click to collapse
Thanks. Please let me know if these steps should work. I am currently NOT rooted and my bootloader is locked. I do have my bootloader code. I'm currently rebranded to USA BLA-A09 (C567) from using funkyhuawei. Originally my phone is Europe BLA-L29 (C432)
Step 1. If I use funkyhuawei (I have that unlimited account for this phone) and rebrand from USA BLA-A09 (C567) back to my original BLA-L29 (C432) and then get the OTA to the latest build .142 everyone is raving about. That is simple part. USA brand is very far behind all other countries with updates....
Step 2. Do I use DCunlocker to unlock bootloader or is it just a command in fastboot mode that I issue?
Step 3. Root the phone (what tool should I use) as I need to modify the build.prop file to allow for VoLTE to work on T-MOBILE in the USA. I found this guide for volte to work -- it seems there are instructions to root in this guide: https://forum.xda-developers.com/mate-10/how-to/guide-enable-volte-icon-mobile-network-t3764826
Then can I unroot the phone and if I do so, will my modifications to the build.prop file remain? Or do I need to keep it rooted?
Lastly, will the phone pass safetynet if bootloader unlocked and the phone is rooted?
Appreciate any assistance and guidance and thank you.
Sent from my BLA-A09 using Tapatalk
KevinAce said:
Thanks. Please let me know if these steps should work. I am currently NOT rooted and my bootloader is locked. I do have my bootloader code. I'm currently rebranded to USA BLA-A09 (C567) from using funkyhuawei. Originally my phone is Europe BLA-L29 (C432)
Step 1. If I use funkyhuawei (I have that unlimited account for this phone) and rebrand from USA BLA-A09 (C567) back to my original BLA-L29 (C432) and then get the OTA to the latest build .142 everyone is raving about. That is simple part. USA brand is very far behind all other countries with updates....
Step 2. Do I use DCunlocker to unlock bootloader or is it just a command in fastboot mode that I issue?
Step 3. Root the phone (what tool should I use) as I need to modify the build.prop file to allow for VoLTE to work on T-MOBILE in the USA. I found this guide for volte to work -- it seems there are instructions to root in this guide: https://forum.xda-developers.com/mate-10/how-to/guide-enable-volte-icon-mobile-network-t3764826
Then can I unroot the phone and if I do so, will my modifications to the build.prop file remain? Or do I need to keep it rooted?
Lastly, will the phone pass safetynet if bootloader unlocked and the phone is rooted?
Appreciate any assistance and guidance and thank you.
Sent from my BLA-A09 using Tapatalk
Click to expand...
Click to collapse
1. Yes, that is fine.
2. Huawei stated they will close down the service, but I *think* it's the service to get the unlock code, not the ability to unlock the bootloader. This may change in future updates, but until then you can just unlock using 'fastboot oem unlock code_here' command (This wipes /data so make sure to backup stuff)
3. Basically you just flash TWRP (https://forum.xda-developers.com/mate-10/development/huawei-mate-10-pro-twrp-3-2-1-0-t3769904), then flash Magisk (https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589). The current beta of Magisk is a little buggy so you can just flash the stable one (16.0). Buggy being that Magisk Manager closes down when you open it, it can be countered by clearing data of Magisk Manager through Settings -> Apps.
Magisk will pass SafetyNet in most cases. Some builds are not yet certified by Google so they won't pass (b142 passes fine), it usually takes 1-2 weeks after they release on http://pro-teammt.ru before they pass.
If you want to unroot you can use Magisk Uninstaller, it's available in the release thread.
And if you want stock recovery you can just flash back stock from fastboot after you've installed Magisk.
Though there's no need to unroot since SafetyNet will pass. And if you only want to replace build.prop you could do it from TWRP. Bootloader needs to stay unlocked though, and I'm not sure if Safetynet passes with a modified build.prop (but it should I guess).
And! Magisk supports modules, so you could just make one that enables VoLTE (by passing the prop using 'resetprop') without needing to modify build.prop at all.
Understand the update official mechanism
Hello guys...
I need to know the mechanism how Huawei mobile device being updated, using SD card if it's possible with new model or can I manually get the update packages link, download them and how to inject them into the device, because the update come with three zip files.
If any one knows clear way please feed me back.
Thanks in advance...
Build number
DE2117_11_C.17
Hardware version
DE2117_11
I keep seeing T-Mobile version, INTL version, DE18 and all that. I'm so confused, I just need root.
I believe that's the international version since mine is DE2117. Not sure because of the "_11" at the end of yours. Maybe that signifies you updated it, in which case you will probably have to downgrade it.
Rooting this phone is a headache btw. I'm not even sure if I should be providing instructions because I bricked mine multiple times while attempting and had to keep restoring with MSMtools, and now I'm not even sure I can update it without losing root. I don't even think I did anything differently when it finally worked, it's just luck.
Anyway, first step is to download the international version of the MSMtools and payload dumper. look up how to dump the boot image with payload dumper from the MSMtools. And make sure you don't attempt to do anything to the device before unlocking your bootloader (and you'll have to unlock it again everytime you restore with MSMtool).
From there you should be able to follow guides.
@swee08315
I downloaded the latest update available from https://www.oneplus.com/support/softwareupgrade/details?code=PM1630638351161
But the phone is updated to July. Hmmmm.....
I've extracted the boot.img from there. Patched it with magisk. I'm about to fastboot flash it..... Wish me luck, I'm going in.
Unless there's a way to extract the boot.img that's currently installed. I think I'll poke around and look for that rather than simply hoping this is the right one.
jova33 said:
I downloaded the latest update available from https://www.oneplus.com/support/softwareupgrade/details?code=PM1630638351161
But the phone is updated to July. Hmmmm.....
I've extracted the boot.img from there. Patched it with magisk. I'm about to fastboot flash it..... Wish me luck, I'm going in.
Unless there's a way to extract the boot.img that's currently installed. I think I'll poke around and look for that rather than simply hoping this is the right one.
Click to expand...
Click to collapse
[GUIDE] Root and keeping root options
Update 230526: Correct numbering of "B.1.1 Simple" to "B.1.2 Simple", use "OOS 13+" instead of "OOS 13" as OOS 13.1 is now available A. First time rooting This process is common across all options A.1 Flashing Magisk patched boot image There...
forum.xda-developers.com
A1.1 will get the boot.img your device currently has.
Edit: if you flashed the boot.img from the official site, then your device is most likely bricked. I'll fetch my boot.img and link it here (won't be magisk patched).
justauserthatusesaphone said:
[GUIDE] Root and keeping root options
Update 230526: Correct numbering of "B.1.1 Simple" to "B.1.2 Simple", use "OOS 13+" instead of "OOS 13" as OOS 13.1 is now available A. First time rooting This process is common across all options A.1 Flashing Magisk patched boot image There...
forum.xda-developers.com
A1.1 will get the boot.img your device currently has.
Edit: if you flashed the boot.img from the official site, then your device is most likely bricked. I'll fetch my boot.img and link it here (won't be magisk patched).
Click to expand...
Click to collapse
yeah, I bricked it
Nothing a few beers won't cure.
Once I unbrick, I will do A1.1 though.
jova33 said:
yeah, I bricked it
Nothing a few beers won't cure.
Once I unbrick, I will do A1.1 though.
Click to expand...
Click to collapse
here's the boot.img (not rooted)
I hope you haven't wiped yet
boot.img
drive.google.com
justauserthatusesaphone said:
here's the boot.img (not rooted)
I hope you haven't wiped yet
boot.img
drive.google.com
Click to expand...
Click to collapse
nah, I don't wipe until I get into the shower.
But yeah, I completely reset everything with MSM tools. In the process of letting all the updates go through. Thanks for the boot img though, It'll save me the trouble of having to pull it using the msm tools.
Edit: I forgot to do the vbmeta stuff after flashing the magisk patched. How do I fix? Can I borrow your vbmeta, @justauserthatusesaphone ?
justauserthatusesaphone said:
here's the boot.img (not rooted)
I hope you haven't wiped yet
boot.img
drive.google.com
Click to expand...
Click to collapse
So I can update my oneplus and then patch and use this bootimg to regain root? Or will trying to update my rooted device brick it and I'd have to wipe everything and start from scratch anyway?
jova33 said:
nah, I don't wipe until I get into the shower.
But yeah, I completely reset everything with MSM tools. In the process of letting all the updates go through. Thanks for the boot img though, It'll save me the trouble of having to pull it using the msm tools.
Edit: I forgot to do the vbmeta stuff after flashing the magisk patched. How do I fix? Can I borrow your vbmeta, @justauserthatusesaphone ?
Click to expand...
Click to collapse
I'll get it when I'm on my PC
the c17 one, correct?
justauserthatusesaphone said:
I'll get it when I'm on my PC
the c17 one, correct?
Click to expand...
Click to collapse
Don't worry about it. I redid the MSM tool since the phone wasn't even setup yet, no big loss.
swee08315 said:
So I can update my oneplus and then patch and use this bootimg to regain root? Or will trying to update my rooted device brick it and I'd have to wipe everything and start from scratch anyway?
Click to expand...
Click to collapse
So, I don't know how this phone handles updates. I've had previous phones that if it was rooted, the OTA would fail to install, and others that the OTA would install and replace the boot.img, so root would be removed.
The first case, I would have to unroot, restore the stock boot.img, and then it could take the OTA update.
The other case I would have to block OTAs until I could get the boot.img for it, so that I could root the update.
The guide posted here https://forum.xda-developers.com/t/guide-root-and-keeping-root-options.4387977/
part B explains how to update and maintain root. Seems like it's the first case. Restore stock boot.img.
jova33 said:
So, I don't know how this phone handles updates. I've had previous phones that if it was rooted, the OTA would fail to install, and others that the OTA would install and replace the boot.img, so root would be removed.
The first case, I would have to unroot, restore the stock boot.img, and then it could take the OTA update.
The other case I would have to block OTAs until I could get the boot.img for it, so that I could root the update.
The guide posted here https://forum.xda-developers.com/t/guide-root-and-keeping-root-options.4387977/
part B explains how to update and maintain root. Seems like it's the first case. Restore stock boot.img
Click to expand...
Click to collapse
You could turn off automatic system updates so it doesn't reboot automatically and then you install the update and when it asks you to restart, go into magisk and click install and install to inactive slot then you go back to the system update page and click restart. I don't know whether Google's ota system makes it easier or not.
Late reply but I can confirm that all updates fail on this device and you would have to unroot to get the update, and then root again. Very annoying that it's constantly notifying me that an update is available or that it tried to update last night and failed
swee08315 said:
Late reply but I can confirm that all updates fail on this device and you would have to unroot to get the update, and then root again. Very annoying that it's constantly notifying me that an update is available or that it tried to update last night and failed
Click to expand...
Click to collapse
I never had that issue but if you do, press uninstall and restore images (DON'T REBOOT), then after installing the updates (DON'T REBOOT) press install and install to inactive slot. Press the reboot button and you're done.
Lineage installation on N200 REQUIRES that you are running Android 11 or phone will soft loop after installing the Lineage boot.img
If you are updated to Android 12 firmware and want to install Lineage, you MUST downgrade first to:
DE2117 OEM Android 11 FINAL OTA
WARNING: This WILL erase all user data.
1. Place the firmware .zip file in the user root of internal phone storage.
2. Sideload OnePlus firmware Downgrade Tool on phone and use tool to flash the Android 11 firmware.
There is an Emergency Firmware install tool that OnePlus posted to the OP forum that does NOT check root status when the need to downgrade back to A11 was first acknowledged due to modem issue with first A12 OTA release.
This file was removed in a few days when they posted the official Downgrade tool replaced it.
I have used this tool to upgrade DE2117 C_16 to DE2117 C_17 while rooted and the built in upgrade tool failed at 37%.
Nice, first thanks for the hard work you're putting in. Second, is there an advantage to converting first to DE2117 then installing lineage as opposed to just installing lineage from DE2118 that you know of? I know in the other post you answered my other question stating that the Lineage will install on either so I wasn't sure if I'd get any benefit from starting over and converting my DE2118. TIA
Link575 said:
Nice, first thanks for the hard work you're putting in. Second, is there an advantage to converting first to DE2117 then installing lineage as opposed to just installing lineage from DE2118 that you know of? I know in the other post you answered my other question stating that the Lineage will install on either so I wasn't sure if I'd get any benefit from starting over and converting my DE2118. TIA
Click to expand...
Click to collapse
Lineage is using own kernel and boot.img on A11 so in the short run it is not going too make any difference, but when Lineage moves forward to A12 the OEM Firmware has newer drivers and is updated sooner, has more OEM features and bugfixes as well as no carrier bloatware.
It is possible that OP will neuter the Carrier firmware with an OTA update to prevent cross flashing device away from the Carrier rom in the next OTA update by preventing fastbootd from flashing the us oem from a carrier phone.
They have already removed fastboot boot command to boot a boot image without flashing it for test before you flash and to allow Magisk to make a backup of the original boot.img before adding Magisk.
I would convert NOW, before they decide to slam the door on this ability with a future OTA that will not allow you to downgrade and prevent this as they are under contract with the carriers to not allow this to be done.
Ok, thank you for the explanation. Guess I'll back everything up and convert it.
scanman0 said:
Lineage installation on N200 REQUIRES that you are running Android 11 or phone will soft loop after installing the Lineage boot.img
If you are updated to Android 12 firmware and want to install Lineage, you MUST downgrade first to:
DE2117 OEM Android 11 FINAL OTA
WARNING: This WILL erase all user data.
1. Place the firmware .zip file in the user root of internal phone storage.
2. Sideload OnePlus firmware Downgrade Tool on phone and use tool to flash the Android 11 firmware.
There is an Emergency Firmware install tool that OnePlus posted to the OP forum that does NOT check root status when the need to downgrade back to A11 was first acknowledged due to modem issue with first A12 OTA release.
This file was removed in a few days when they posted the official Downgrade tool replaced it.
I have used this tool to upgrade DE2117 C_16 to DE2117 C_17 while rooted and the built in upgrade tool failed at 37%.
Click to expand...
Click to collapse
This worked perfectly after following your convert guide and upgrading to 12. Downgraded back to 11 so I could install lineageOS. Thanks again!
This reddit post has a link to an English version of the downgrade apk which makes it a little easier.
keeps saying verification failed
weirdfate said:
keeps saying verification failed
Click to expand...
Click to collapse
Did you remove root (Restore boot.img) and then factory reset?
You will loose all data doing this anyway.
I m trying as well .. but stuck with verification failed message just as scanman0 I m on stock android12 no root if anyone know how to fix it ... please assit
I just downgraded. Make sure you remove root via magisk. Then proceed to rollback to Android 11. Everything worked fine. I'll install lineage tonight when I get home.
radekmazur said:
I just downgraded. Make sure you remove root via magisk. Then proceed to rollback to Android 11. Everything worked fine. I'll install lineage tonight when I get home.
Click to expand...
Click to collapse
I did not have to remove root. I used the version posted that does not check for root but maybe there's a different reason.
Does the downgrade apk have to be sideloaded via ADB?
T3CHN0T33N said:
Does the downgrade apk have to be sideloaded via ADB?
Click to expand...
Click to collapse
Just place apk in phones working directory, same path where your downloads folder is. Then install from there like any other apk and run. I also kept the FW file in the same directory but I'm not sure if that was necessary.
So, just to confirm, I press "local install" and select the firmware zip and it closes? Is the tool supposed to do anything else or am I good to flash LineageOS?
T3CHN0T33N said:
So, just to confirm, I press "local install" and select the firmware zip and it closes? Is the tool supposed to do anything else or am I good to flash LineageOS?
Click to expand...
Click to collapse
Ummm if I remember correctly hit local install and then it will prompt to point towards which FW to use. After you hit it, it will go back to the previous screen, I think verify and unpack it, then install it. Mine did appear like it was doing nothing after picking the FW and so I picked again which screwed things up so just wait after picking, it should start.
After its done it will give a message saying to restart phone I think for it to take effect, then after you restart it should ask to wipe phone, then restart again and you'd be in A11 presumably. Once in A11 your good to follow the normal procedure to install Lineage. This is all from memory though so I MAY have missed something but I don't think I did.
Link575 said:
Ummm if I remember correctly hit local install and then it will prompt to point towards which FW to use. After you hit it, it will go back to the previous screen, I think verify and unpack it, then install it. Mine did appear like it was doing nothing after picking the FW and so I picked again which screwed things up so just wait after picking, it should start.
After its done it will give a message saying to restart phone I think for it to take effect, then after you restart it should ask to wipe phone, then restart again and you'd be in A11 presumably. Once in A11 your good to follow the normal procedure to install Lineage. This is all from memory though so I MAY have missed something but I don't think I did.
Click to expand...
Click to collapse
When you say "screwed things up" what do you mean? How did it effect the install?
T3CHN0T33N said:
When you say "screwed things up" what do you mean? How did it effect the install?
Click to expand...
Click to collapse
Nothing major, caused the UI to glitch out and made it seem like the process was stuck at 81% but when I closed the app and tried to do it again it jumped to 100 and said to restart the device.
I've downgraded a second time (I'm very indecisive on which OS I want to use) and that one went as expected since I knew to give it a second to start doing its thing.
Link575 said:
Nothing major, caused the UI to glitch out and made it seem like the process was stuck at 81% but when I closed the app and tried to do it again it jumped to 100 and said to restart the device.
I've downgraded a second time (I'm very indecisive on which OS I want to use) and that one went as expected since I knew to give it a second to start doing its thing.
Click to expand...
Click to collapse
Weird, for me it just closes the app and does nothing, both the official and emergency ones. I even tried adding it to magisk's deny-list.
But I just restored the boot image via magisk (didn't restart) and it works now...
scanman0 said:
Did you remove root (Restore boot.img) and then factory reset?
You will loose all data doing this anyway.
Click to expand...
Click to collapse
Yes I factory restored the phone and tried again. Still fails every time
Has anybody had any luck figuring out the verification failed message? I too have tried both the official and emergency apps, of course I can't read the actual message in what I presume is Chinese, but it doesn't do anything and the other version says verification failed. Have not rooted. Kind of at a loss right now and all I want to do is install Lineage! I've already got my unlock token from OnePlus, but my understanding is that the phone still needs to be on A11 before installling Lineage.
I write this post since I've seen a lot of people is asking how to upgrade their devices to android 13. If you don't want to wait here, you have a way.
The only official version available so far is for Indian region which has a nv_id = 00011011, since this is the only checkmark software update uses to validate
OTA local install we just need to change the value of this prop. We can so this way:
1. First delete all your modules and keep installed only MagiskHidePropsConf
2. Using a terminal emulator like termux type su and click enter, then type props ro.build.oplus_nv_id 00011011 click enter and follow the short procedure until reboot
3. After reboot you can download the full OTA: https://gauss-componentotacostmanua...22/10/24/4ccc3d3cb837437ea787baaac853fc4d.zip and perform a local installation without getting the verificacation faild message (keep installed the module magiskhide during all the upgrade process)
Note: This will change your region after the update, if you want to keep your device rooted and don't know how to, you can look in other threads of this forums.
If you don't want to change your region, I posted the URLs for other regions here: https://forum.xda-developers.com/t/global-eu-collection-of-firmware-files.4478153/post-87640469
Use this method to downgrade from A13 RU to A12 India roll back package.
Will it work for switching from RMX3300 to RMX 3301 also?
I am on china A13 official with locked bootloader, is there any way to go to India version? I'm trying to find a roolback for China A12 but couldn't find it
shivrajsingh said:
Use this method to downgrade from A13 RU to A12 India roll back package.
Will it work for switching from RMX3300 to RMX 3301 also?
Click to expand...
Click to collapse
you were able to change the region with rolback package?
luki2411 said:
you were able to change the region with rolback package?
Click to expand...
Click to collapse
You can change region. but not from RMX 3300 to 3301 i.e. china to export. Other region interchange work fine. Use full ota only
dick_vigarista said:
I am on china A13 official with locked bootloader, is there any way to go to India version? I'm trying to find a roolback for China A12 but couldn't find it
Click to expand...
Click to collapse
There is none for now. Only MSM download tool can get you back to A12 where you unlock boot loader and change region. With MSM tool, you can directly flash root export Rom as well.
Dont try to roll back from A13 to A12 through fastboot. Mine got bricked
shivrajsingh said:
There is none for now. Only MSM download tool can get you back to A12 where you unlock boot loader and change region. With MSM tool, you can directly flash root export Rom as well.
Dont try to roll back from A13 to A12 through fastboot. Mine got bricked
Click to expand...
Click to collapse
but where to get the working msm tool?
luki2411 said:
but where to get the working msm tool?
Click to expand...
Click to collapse
Well I guess you don't, you pay some random guy to do remotely since you need OPPO credentials.
shivrajsingh said:
There is none for now. Only MSM download tool can get you back to A12 where you unlock boot loader and change region. With MSM tool, you can directly flash root export Rom as well.
Dont try to roll back from A13 to A12 through fastboot. Mine got bricked
Click to expand...
Click to collapse
I found out a way of doing it and made a Guide here for anyone interested:
Fastest and easiest way to transform your 3300 (Chinese) on 3301 (Global)
I AM NOT RESPONSIBLE FOR ANY BRICKS, DO AT YOUR OWN RISK. I TRIED AND WORKED FOR ME. THIS WILL ERASE ALL DATA FROM YOUR DEVICE. THIS IS FOR STOCK CHINESE ONLY, I DID NOT TRY IT ON UNLOCKED BOOTLOADER DEVICES, ROOTED DEVICES, OR ANY OTHER...
forum.xda-developers.com
vanya.ag said:
I write this post since I've seen a lot of people is asking how to upgrade their devices to android 13. If you don't want to wait here, you have a way.
The only official version available so far is for Indian region which has a nv_id = 00011011, since this is the only checkmark software update uses to validate
OTA local install we just need to change the value of this prop. We can so this way:
1. First delete all your modules and keep installed only MagiskHidePropsConf
2. Using a terminal emulator like termux type su and click enter, then type props ro.build.oplus_nv_id 00011011 click enter and follow the short procedure until reboot
3. After reboot you can download the full OTA: https://gauss-componentotacostmanua...22/10/24/4ccc3d3cb837437ea787baaac853fc4d.zip and perform a local installation without getting the verificacation faild message (keep installed the module magiskhide during all the upgrade process)
Note: This will change your region after the update, if you want to keep your device rooted and don't know how to, you can look in other threads of this forums.
Click to expand...
Click to collapse
I do all and I get message "invalid option"