Nubia 5s/5g android R or 11 chinese rom beta update - Nubia Red Magic 5G / 5S Guides, News, & Discussion

Nubia 5s/5g android R or 11 chinese rom beta update - Nubia Red Magic 5G / 5S Guides, News, & Discussion

For Nubia RedMagic 5G/5S (NX659J/NX659J_V1S) ONLY!
Android R V912 - Public Beta (Chinese rom)
Only update through official updater. Wala munang OTA ng Android R. So only thru download at local update lng sa ngayon.
Precautions:
● Before upgrading, please make sure that the phone has sufficient battery power and back up the phone data (it is recommended to use the built-in backup software) to avoid loss of phone data during the upgrade process;
● Before upgrading, please cancel all screen locks. During the upgrading process, please be sure to lay the phone flat, and do not touch the screen at will, and follow the on-screen instructions
● If you have obtained the root permission, please remove the root permission, restore the normal version status, and restore the factory settings before upgrading, otherwise it will easily lead to the failure of the upgrade;
● Any problems encountered during use can be reported in the product feedback section of the forum.
Another Important Details:
1. For a better experience, it is recommended to update the third-party application to the latest version in the app store after the upgrade to avoid the adaptation problem of Android R due to the old third-party application
2. After upgrading from Q to R version, rollback to Q is not supported. If you forcibly roll back, it will cause data loss and bricking.
3. Due to the upgrade of the big platform, the original recorded one-click combo cannot be used in the Android R version, and it needs to be re-recorded to be used normally
Download link:
http://romdownload.nubia.com/红魔5G/V9.12/NX659J-update.zip
Source?
Official post by Nubia
https://bbs.nubia.com/thread-2609817-1-1.html

Officially Chinese variant phone ko tapos nag flash ako ng Global version neto, is it safe to flash this Chinese ROM na Android R ngayon?

Hi !
I would like to ask if I have NX659J_ENCommon_V7.07 on my phone, can I install this version directly on it?
Thanks

Failure at 25%
Hey! Can I get some help? I have tried to install this rom but it failure at 25 % anyone that know why and how to fix this?

salovapes said:
Failure at 25%
Hey! Can I get some help? I have tried to install this rom but it failure at 25 % anyone that know why and how to fix this?
Click to expand...
Click to collapse
i was actually wondering myself, seems the way to do it properly is migrating you 5S to the CN "android 10" rom then upgrade to android 11

When can we expect global rom

How can I flash the chinese rom on Nubia 5s, I'm already on EU version and when I try to flash any chinese rom using the usual method it shows me error at 25%.

Heshamvido said:
How can I flash the chinese rom on Nubia 5s, I'm already on EU version and when I try to flash any chinese rom using the usual method it shows me error at 25%.
Click to expand...
Click to collapse
Are you using an OTA to USB drive adapter? The formatted device needs to be some archaic format, I can't recall which one. FAT32 I think.
BTW I have an R A11 test kernel that is based on the Q vendor trees, I don't know if it works on 5S but it probably works on 5G, no one has tested it though. Runs at 900mhz max GPU OC https://github.com/mrslezak/RM5G_5S_R_MOD I'd appreciate it if someone could test it out. Just backup your boot.img first (which is in the ROM zip file, you can flash back the original to the device if any problems arise via: fastboot flash boot boot.img, and if you need to patch it put it on the phone and use Magisk Manager, transfer back to the PC, and then flash magisk_patched.img or whatever it's named instead.

mslezak said:
Are you using an OTA to USB drive adapter? The formatted device needs to be some archaic format, I can't recall which one. FAT32 I think.
BTW I have an R A11 test kernel that is based on the Q vendor trees, I don't know if it works on 5S but it probably works on 5G, no one has tested it though. Runs at 900mhz max GPU OC https://github.com/mrslezak/RM5G_5S_R_MOD I'd appreciate it if someone could test it out. Just backup your boot.img first (which is in the ROM zip file, you can flash back the original to the device if any problems arise via: fastboot flash boot boot.img, and if you need to patch it put it on the phone and use Magisk Manager, transfer back to the PC, and then flash magisk_patched.img or whatever it's named instead.
Click to expand...
Click to collapse
I'm just using the phone updater itself, with the OTA file on the root directory of the phone itself.

Related

Alcatel OT POP C7 (7041x) [BACKUPS/ROOT/CWM/TWRP/TOOLS/DRIVER] [STOCK &amp;amp;amp;amp; MIUI V5 ROMs]

Alcatel OT POP C7 (7041x) [BACKUPS/ROOT/CWM/TWRP/TOOLS/DRIVER] [STOCK &amp;amp;amp;amp;amp; MIUI V5 ROMs]
Last Update: Mon. AUG-03-2015
Hello,
I had bricked my "just" 4 hours old C7 a week ago because i was stupid enough to delete the custpacks from root and /system folders without even making a backup.
I had not flashed CWM and only rooted the device with RomasterSu_2.1.4 (aka iROOT, some Chinese one-click root / KingUser app) and i could not revive the phone through MTK Tools, Mobile Upgrade S or adb shell (either device not recognized or it couldn't push files, giving errors).
Today i got a new one, and hell i have not made the same mistake again.
After i unboxed the phone i immediately went into stock recovery and made a backup!
Secondly, i rooted the phone with RomasterSu and installed Uncle MTK Tools and made a IMEI backup (Just incase).
And lastely, i flashed CWM through Uncle and made a Full Backup of the current rom.
For anyone who happens to play with a rooted C7 on stock rom and accidentally bricked it, i will provide my Stock and CWM Backup Recovery's for anyone to use.
note: If you already flashed a custom recovery onto your device (e.g; CWM), the stock backup becomes obsolete! Use CWM instead.
[INFO]
Model: Alcatel One Touch 7041x
Firmware: 4.2.2
Baseband: MOLY.WR8.W1315.MD.WG.MP.V7
Kernel: 3.4.5
Build: 01003
Stock Recovery (Data) Backup (.backup):
- userdata_20100101_000117.backup (.rar / 83MB)
Place Stock Backup (Unpacked) into the root folder of your sdcard.
Reboot phone, Vol+&Power into stock recovery and select "restore user data" (or something alike) and select the .backup file.
New googledrive uploads:
-MIUI V5 (4.8.29) ROM (.zip)
-RootMaster / iRoot & SU (.apk)
-Uncle MTK Tools (.apk)
-CWM & TWRP Recovery (.img)
-Mobile Upgrade S (.exe)
-One Touch Center (.exe)
-USB Drivers (.rar)
-MTK DroidTools (Windows) (.zip)
-SP Flash Tools (.rar)
If you're familiar with flashing, i'd guess installing these files and how to use them propertly are self explainatory.
If not, you can ask me how to write a proper guide...
==============================================================================================================
--UPDATE--
I provided a stock rom and a MiUI V5 rom for people who don't want or prefer to use backup's. A custom Recovery is needed and will not work with stock recovery.
This is a vanila stock rom without the custpack games/apps bloatware. IIRC this rom is already rooted, but if not, you can always use iROOT.
Bare in mind that it's based on the first TCT Firmware build 01001 and not the latest Firmware Upgrade 01003.
The MiUI V5 rom is based on miui 4.8.29 (Jellybean 4.2).
Also, the installers are in Spanish and you can only select a handfull system languages for both roms, but atleast you can use these roms in English.
Both roms work absolutely fine, and faster than stock with custpack bloatware.
Stock (01001) ROM:
https://drive.google.com/file/d/0B_pc8K917q22RlJWNllGV2JLOVE/view?pli=1***
MIUI V5 (4.8.29) ROM:
http://www.mediafire.com/download/9l49h7gisxslx2s/Miui+v5+spanish.Alcatel+7041x.zip***
---UPDATE--- [AUG-03-2015]
KitKat 4.4.x Alcatel C7 (7041x):https://translate.googleusercontent...2.html&usg=ALkJrhh-v6soAAT7XuUrpiK_zGh5bODHaA***
*** I have not uploaded these ROMs, nor am i responsible for any damages or errors that might occur during flash, use at own risk and always make a backup first!
Making any custom changes to your device will void your warranty!

Bump Update!
Added files to google drive;
-MIUI V5 ROM (4.8.29) (.zip)
-RootMaster / iRoot & SU (.apk)
-Uncle MTK Tools (.apk)
-CWM & TWRP Recovery (.img)
-Mobile Upgrade S (.exe)
-One Touch Center (.exe)
-USB Drivers (.rar)
-MTK DroidTools (Windows) (.zip)
- SP Flash Tools (.rar)
https://drive.google.com/folderview?id=0B52SB5R_clyUVTNwVHlwMHpCZWM&usp=sharing

S5 7041X Rom
http://www.htcmania.com/showthread.php?t=976259

How to install stock ROM with Mobile Upgrade S,when installed custom CWM?How back to stock CWM?Mobile Upgrade S does not recognize the phone with custom CWM.Phone must be flashed with SP Flash Tool.After this,Mobile Upgrade S,recognizes phone.

_jussyy said:
http://www.htcmania.com/showthread.php?t=976259
Click to expand...
Click to collapse
Nice ROM,but it kills the battery.

mugy said:
Nice ROM,but it kills the battery.
Click to expand...
Click to collapse
Most roms need some time to settle, after 1 or 2 complete charges your battery should behave normally.
You can also use the 'Greenify' (Permit SU access) to blacklist any app that uses wakelocks or running backround processes.
This will save you some battery...
My best bet is going for the MiUiv5, which always ran fine when i used to own the C7. Never had any issues with that ROM other than a occasional 'SystemUi stopped working' when trying to use the Rom's OTA.

I installed CWM 5.5.0.4 but cannot see internal storage
Do you have any idea?

erdemdengel said:
I installed CWM 5.5.0.4 but cannot see internal storage
Do you have any idea?
Click to expand...
Click to collapse
A bit late but that's because I don't own the C7 anymore and hardly pay attention to these threads anymore, I'm sorry...
I have no idea why it would'nt show up in CWM. I always use TWRP on any device that has it's compatibility over CWM, mainly because of it's touch functions and ext partitioning functions. Normally your internal storage is sdcard0 and your SD is sdcard1, select "mount/unmount" to see whether it's listed or not (I guess you already did that obviously but still....) It should be listed, if not, reflash CWM (try latest available for the tct/alcatel, i don't know which build number out top of my head, or TWRP.
I suggest to switch to TWRP and most likely your problem will be solved.
I don't know where you got your recovery files, but the ones I got in my googledrive are guaranteed working since I tried them both before uploading, if you used my CWM try to reflash it with MobileUncle MTK Tools, but than again pick TWRP instead .
Sent from my ACER LIQUID Z500 using XDA Free mobile app

Bump Update
Sent from my HTC One using XDA Free mobile app

I tried to use both the CWM and TWRP recoveries and neither worked. When it tries to boot into them it just glitches out the boot screen and resets. I flashed them with Flashify if that's a problem. My tablets model is a P310A. So this is the right thread for it right?
It does the same thing when I flash with Uncle MTK Tools.
Update: So it seems that you need to use this recovery if you have a P310A. Sorry for the pointless bump.

White sreen when flashed
After I flash my phone I get white screen logo whitescreen logo etc.
I have the alcatel 7041x
Alcatel one touch pop C7 ,Dutch

It functional in 7040e?

Not reading us b

I can't download backup file

@dragonivell
No! 7041x only. If it would, i would've stated it at the "device compatibility list" (which doesn't exist in this topic, for that reason!)
@pricklain
I'm sorry, somehow the file got removed from my gdrive. Since I don't own this particular device anymore, i cannot re-upload the file in question.
Also, i'm unable to edit the OP for some reason, so i understand any complains about the backup file(s).
Note: I am hardly online on xda these days, so forgive me if my response is a bit late...
@jachthond
Heb je wat meer details wat er niet lukt met flashen, en welke files je daarvoor gebruikt hebt? Mischien kan ik je er door heen loodsen.

Nobody has to Alcatel One Touch Fierce 7024w ?

links please

Ebom

Because this thread was the first one I completly read and looked at many time again, I post my results in short here.
Its posible to "flash" or "download" the KitKat rom from Hungary (or whereever the rom came from) onto a stock Alcatel OT POP C7 (7041X). Note the X, I have only that phone so, find another thread or user if you dont have a x (the kitkat rom is from/for a 7041D, so maybe your in luck too if you have the D version)
https://forum.xda-developers.com/alcatel-pop-c7/help/alcatel-one-touch-pop-c7-kitkat-twrp-t3438624 this other thread has the working rom, tools, and scatter file.
I could write a tutorial, but i based my carefull work on that thread and the links he provided. I also watched the youtube video even tho I dont understand a word thats being said.
Basicly NEVER EVER overwrite or format the phone completly or do sh1t with the preloader. mobile_info we leave alone aswell and we dont like to touch NVRAM aswell. They kinda contain imortant stuff
Basicly i made backups of everything I could or wanted (some thread said "Readback" the preloader can break alcatel phones, Ive succesfully read my whole phone back, but NEVER tried "downloading" or flashing preloader, cause i dont want a brick.) so I have everything saved and i could compare my files against any other rom that ppl uploaded.
KitKat rom from that thread I linked you to, get it, just all of it just in case. then if you compare them using CRC/SHA1 or MD5 against your dumps. hopefully like me, MBR, EBR1 and EBR2 are all the same compared to the kitkat one. so i took the liberty of not flashing them.
left us to do the: UBOOT(lk.bin in my backups), BOOTIMG, RECOVERY, SEC_RO, LOGO, CUSTPACK, ANDROID.
I noticed diferences in the logo, recovery and sec_ro, so I followed the tutorial/video on "downloading" those onto my phone... real simple...
I now have KitKat on my 7041x
Phone calls itself a 7041D now and Gyroscope sensor is not working
simple fix for the phone name is in the build.prop file, either google how to edit that (using root, or adb tricks) or do as I tricked, changed the file inside custpack.img using an hexeditor (HxD is my favorite). When you find a 7041D, replace with X. I suggest you use your brain and computer skills to deduce how to "replace" a character instead of inserting seems to start at offset 0x03356000 (http://www-ccpp.tcl-ta.com/files/ALCATEL_ONE_TOUCH_7041X_KK.xml does excist, so it suggest an official rom either was made or support added anyway).
I replaced budhapest with amsterdam and could change the dualsim to false and compensating the file size change by removing some 0x00 after the file.. but felt it was too risky and only tried the D into X wich was succesfull. ill check if I can find the AcceleroMeter/Gyro? module or fix.
If anyone has a question, sure ask me. but the rom is there, make backups before ANYTHING, and never full format or touch the preloader. ive read it might be able to fix using some Jtag method, but I cant remember the thread and this is quite the old phone by now. if ever, ill try a newer rom, but probably have to make it myself. another kitkat rom Ive found wasnt clean but this one was like it was a OTA, the phone migrated the 58 apps, and all my settings where still there, whatsapp worked right away without trouble and I can now play Pokemon GO (the x version has the 1gig ram )
Bedank @JMailuhu for making this thread and pointing and warning people. within 1 week of fixing this free phone Ive updated to kitkat. Now ill try fixing the accelerometer problem and maybe try other roms (ow well, kitkat does work fine) no root or custom recovery sofar
TLDR: Have a cookie, sorry I talk too much. much better than "ROM NOW" comments

Stock ROMs Factory v6.1 , v8.3 , v8.4 , v8.5 , v8.7, V9.0, V9.2-patch : v21

CAUTION TO NOT LOOSE TWRP
I read two posts that say v21, now again on V8.5, put the stock recovery back instead of twrp. This is probably a side effect of a fresh stock /system and wipe of /data.
As a preventive step, when done flashing and wiping reboot to recovery FIRST, before booting the system It will allow recovery to handle removing the recovery-from-boot.p that flashes stock recovery.
I just patched the modified V7.4.2 up to the newly released 8.3 now 8.4. 8.5, 8.7,9.0 -V9.2 Patch
New update has been made from V17 to V21 of the non prime version of R1-HD, Non prime is behind on security patch (2017-05-05)
Copied ROM from phone and made twrp install ROM from it.
* No preloader change (official updates change the preloader to block your ability to use sp flash tools for rom flashing)
* No lk.bin change __ this part is what allows you to choose boot options(boot menu when power and volume pressed together)
* No "FOTA" app Fota has now been left in to make it easier to get next update, if that ever happens.
* No opera browser
* No adds (removed in the modified 7.4.2)
* Custom boot logo (only done on v8.3, there was no interest in this so abandoned)
--Newer versions of rom left stock, Leaving mods up to user.
** while it is not necessary to do a wipe with this ROM, I still recommend it.
**Thanks:
** @vampirefo needed his patched v7.4.2 in order to apply this new 8.3 patch and again for 8.4
** @ColtonDRG OR @jasonmerc I do not remember which one made it: For the image used in the custom logo
and the modified zip is here .
Roms are rootable with SuperSU, flashed in twrp after install. Must be done in systemless mode. In order to patch system veridy in boot.img
Logo update did not work on original rom changing link to updated version
BLU rolled v8.3 back to v7.4.2 because of app compatability issues. V8.4 is there fixed release. Both 8.3 and 8.4 are modified prime roms with ads stripped
V21 is the non prime update.
Unmodified V6.1
==>NON-ROOTED-logo-not-replaced-modified-V8.3
==>Fixed Logo modified NON_ROOTED V8.3
==>>modified V8.4
==>>modified V8.5
==>>Full with Ads V8.7
==>>Full with Ads V9.0
==>>Patch For V9.2 must be flashed on top of fresh V9.0
****Run debloat ==>script to remove ads if you need/ want to, or remove from zip before flashing ****
alt. manual example: before reboot, while still in twrp. Select mount and put checkmark next to system. Then run these two commands in adb terminal
Code:
adb shell rm /system/priv-app/com.amazon.*/com.amazon.*.apk
adb shell rm /system/app/Adups*/*.apk
==>>Modified V21
** stand alone logo installs

I flashed this but I didn't get the custom boot logo.

mendelgordon said:
I flashed this but I didn't get the custom boot logo.
Click to expand...
Click to collapse
I had that happen to my second phone too.
I don't have an explanation yet.
I even made a separate update.zip , that one didn't make the logo change either. I did eventually change it with sp flash tool.
I tried with both recoveries.
and multiple /dev location formats. and for whatever reason my one phone did not accept the logo change from recovery.
And the other test phone it worked.

mendelgordon said:
I flashed this but I didn't get the custom boot logo.
Click to expand...
Click to collapse
Neither did I but it all seems to be working fine

Been using this for about a day now, likewise no custom boot logo, but that's fine. Otherwise, it's been running super well. A lot better than the previous mostly stock version did for me with the bloatware APKs removed after the install. A lot of the general idiosyncrasies of the previous version of the stock rom seem to have gone away for me. It seemed to have weird storage management issues, errors moving to SD, broken symlinks that prevent apps from moving or being reinstalled, and a lot of other little non-storage issues, but so far, none off that here.
Long story short, good work! I hope we eventually see proper 7.x roms through some of the efforts going on, but in the meanwhile, your work here has made life a little bit better on 6.

It seems that I was able to get the logo.bin to update when I applied the original update patch, but not when I used the same line in the rom install.
It is no big deal that it did not work, I was just trying to make it look different at boot time.
edit:
I think i found the problem with the logo not updating.
i used the update-binary from the official patch update. (the one that allowed the logo to change the first time)
and it changes . so since the ROM seems to install the way it is , only the logo didn't flash I put it in a separate update.zip if anyone is interested in it.
EDIT 2:
clarification.
It was not so much the binary allowing the logo to change but the format of the partition location I had been using that needed that binary.
Further test had shown me that I could have used the binary I was using but just change the partition naming line
Code:
package_extract_file("logo.bin", "/dev/block/mmcblk0p9")
the above code works with the same update-binary as rom install
But I was using
Code:
package_extract_file("logo.bin", "/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/logo")
Taken straight from the official patch, and thats why it needed the update-binary also.
I dont know what is different in the binary other than , major size difference.
The powered by me logo was just a test file to see changes in the logo.
**logo-update is same as composite but with alt updater-binary
**composite-logo screenshot is in op
**stock logo will return to original BLU logo

mrmazak said:
It seems that I was able to get the logo.bin to update when I applied the original update patch, but not when I used the same line in the rom install.
It is no big deal that it did not work, I was just trying to make it look different at boot time.
edit:
I think i found the problem with the logo not updating.
i used the update-binary from the official patch update. (the one that allowed the logo to change the first time)
and it changes . so since the ROM seems to install the way it is , only the logo didn't flash I put it in a separate update.zip if anyone is interested in it.
EDIT 2:
clarification.
It was not so much the binary allowing the logo to change but the format of the partition location I had been using that needed that binary.
Further test had shown me that I could have used the binary I was using but just change the partition naming line
Code:
package_extract_file("logo.bin", "/dev/block/mmcblk0p9")
the above code works with the same update-binary as rom install
But I was using
Code:
package_extract_file("logo.bin", "/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/logo")
Taken straight from the official patch, and thats why it needed the update-binary also.
I dont know what is different in the binary other than , major size difference.
The powered by me logo was just a test file to see changes in the logo.
Click to expand...
Click to collapse
Hahaha the scribbled "ME" is hilarious. Your work is awesome, I don't think anyone using this rom will have an issue with the boot image but thanks for being so helpful and explaining.
P. S. Do you have any plans with the Nougat update?

Serenitybs said:
Hahaha the scribbled "ME" is hilarious. Your work is awesome, I don't think anyone using this rom will have an issue with the boot image but thanks for being so helpful and explaining.
P. S. Do you have any plans with the Nougat update?
Click to expand...
Click to collapse
Nougat is going to take a full build from scratch. We don't have 100% identical hardware with any other nougat device to my knowledge. We might have the same MTK chipset, but there are several other differences. All we really need is an official device overlay and the vendor files released by BLU themselves. We can then apply those to the latest Lineage or AOSP (I prefer AOSP myself) and build. Then the only problem we'll run into is anything that has changed in 7.x that isn't compatible with our kernel we use in 6.0. It'd be a slight chance our current kernel would work without some patches on 7.x We can't even get our official sources for anything else, so I'm almost certain we'll not find any patches to for the kernel to work properly with Nougat, at least not from BLU or any similar devices. None The less Nougat has been well thought of, and we have been trying to debug issues with a broken Port. But a broken port from a different device is just that - Broken. We need a team of knowledgeable devs to build Nougat + Kernel from scratch and then we'll have it working. I can't do it alone with the old computer I have, the R1HD would be long forgot of by the time I got Android Compiled haha.
Mr. Mazak I flashed your rom it went smooth, I was hoping the newest update was for 6.0.1. But I didn't lose any functionality, hopefully on my Cricket Service this update has patched some things to the radio device that will retain connection more steadily. I experienced a lot of coming and going with the 7.4.2 rom. None The Less you did a good job with this update Mr. My suggestion is find the same MTK chipset with a fully working 7.x rom and just port the /System but keep all our libs and inits from this release just for a test starter. And don't replace the camera app thats in AOSP 7.x. )

linuxsociety said:
Nougat is going to take a full build from scratch. We don't have 100% identical hardware with any other nougat device to my knowledge. We might have the same MTK chipset, but there are several other differences. All we really need is an official device overlay and the vendor files released by BLU themselves. We can then apply those to the latest Lineage or AOSP (I prefer AOSP myself) and build. Then the only problem we'll run into is anything that has changed in 7.x that isn't compatible with our kernel we use in 6.0. It'd be a slight chance our current kernel would work without some patches on 7.x We can't even get our official sources for anything else, so I'm almost certain we'll not find any patches to for the kernel to work properly with Nougat, at least not from BLU or any similar devices. None The less Nougat has been well thought of, and we have been trying to debug issues with a broken Port. But a broken port from a different device is just that - Broken. We need a team of knowledgeable devs to build Nougat + Kernel from scratch and then we'll have it working. I can't do it alone with the old computer I have, the R1HD would be long forgot of by the time I got Android Compiled haha.
Mr. Mazak I flashed your rom it went smooth, I was hoping the newest update was for 6.0.1. But I didn't lose any functionality, hopefully on my Cricket Service this update has patched some things to the radio device that will retain connection more steadily. I experienced a lot of coming and going with the 7.4.2 rom. None The Less you did a good job with this update Mr. My suggestion is find the same MTK chipset with a fully working 7.x rom and just port the /System but keep all our libs and inits from this release just for a test starter. And don't replace the camera app thats in AOSP 7.x. )
Click to expand...
Click to collapse
Somebody already tried this out

Really confused right now.
I was browsing through the settings menus. And found in the Settings-security- menu a toggle labeled "quick boot" ( not to be confused with "fastboot") . I enabled it then rebooted to see if it booted quicker. Didn't seem to make much if any difference. So I went back to turn it back off. And it wasn't there. I checked in my other phone , it wasn't there on that one either.
Did any body see this menu item, and if so where is is it?
Edit 1:
Few more power off , power on cycles to compare times. With other phone and defiantly seems to have turned on some faster boot option.
This phone goes from off to on in 5-6 seconds other phone takes about 20.
Edit 2:
OK , I panicked for a minute.
Couldn't find the setting and thought that it was another way to block sp flash tool by preventing you from ever being fully powered off.
But the setting was in accessibility not security.

Mrmazak, first of all, thanks for the ROM, installed it yesterday. But I have a problem with SELinuxModeChanger app. First, I'm getting a security warning when installing it, then - when running it. And another message, with this app running - "can't obtain root", although SuperSU shows its status with green #, like every other app it gives root privileges to. On my other Prime phone, running 6.1 out of the box stock ROM, FM radio works just fine with SELinuxModeChanger app behaving flawlessly (no security warnings whatsoever). Any ideas?

detroitredwings said:
Mrmazak, first of all, thanks for the ROM, installed it yesterday. But I have a problem with SELinuxModeChanger app. First, I'm getting a security warning when installing it, then - when running it. And another message, with this app running - "can't obtain root", although SuperSU shows its status with green #, like every other app it gives root privileges to. On my other Prime phone, running 6.1 out of the box stock ROM, FM radio works just fine with SELinuxModeChanger app behaving flawlessly (no security warnings whatsoever). Any ideas?
Click to expand...
Click to collapse
The mode changer app is technically a security issue. I did have that warning a few times when using mode changer app from the XDA thread of the developer, then when I used the app downloaded from f-droid it worked with systemless root and didn't give the security warning.

The app downloaded from f-droid worked for me as well, many thanks!

Big thanks for getting this out, updated from previous debloated, rooted version to this modified 8.3 stock rom, rooted with SU v2.79 SR3, all is good - only App that won't show up nor install, even tried the ones off APK Mirror site - is my Dunkin Donuts App, LOL. Play Store now said it's not compatible and the APK started to install then failed - any ideas or suggestions on what to do ??
Otherwise, it's all good - I will survive without DD App, just run that from another device when I need my caffeine fix.

Letitride said:
Big thanks for getting this out, updated from previous debloated, rooted version to this modified 8.3 stock rom, rooted with SU v2.79 SR3, all is good - only App that won't show up nor install, even tried the ones off APK Mirror site - is my Dunkin Donuts App, LOL. Play Store now said it's not compatible and the APK started to install then failed - any ideas or suggestions on what to do ??
Otherwise, it's all good - I will survive without DD App, just run that from another device when I need my caffeine fix.
Click to expand...
Click to collapse
I also had an app that previously work, say is not compatible now.
Maybe has to do with apps that have links to pay accounts. And that has something to do with trustzone. (Tee1 & tee2)
Those sections I left out of the update. I will add it back in and test. Update when I do. It is also possible this problem is why Blu rolled back there update.
**EDIT**
well that didn't go well at all.
I flashed the new trustzone.bin files from the official update. Now phone no longer turns on and no longer connects to flash tool
**EDIT 2**
After much persistence and many failed attempts to get phone recognized in pc again. Finnaly got to a point that phone was cycling between "preloader" driver and "usb serial device", and with careful timing was able to start sp flash tool at just right time and the flashing back to original trustzone files seems to have recovered phone.
for the record i am not sure what steps made it work. But I was shifting back and forth between leaving phone sit on charge, then on charge with rubber band wrapped around power button, then not plugged in , and not plugged in with rubber band on power button.

Okay... persistence is key in customization, i guess! I am getting somewhere here!
mrmazak said:
The first link is needed to get phone unlocked so you can install twrp.
Click to expand...
Click to collapse
Finally got thru the steps in order (1-2-3-4) then Step (5) and sub-step 1. I can also boot to TWRP.
Now this brings me to this thread, 8.3 Stock ROM. The thread assumes one knows how to install it and I suspect this could be as easy as uploading it to a folder in the phone then booting to TWRP and INSTALLING the ZIP file? Could someone clarify the steps to install this 8.3 ROM?
Thanks!

OldSkewler said:
Okay... persistence is key in customization, i guess! I am getting somewhere here!
Finally got thru the steps in order (1-2-3-4) then Step (5) and sub-step 1. I can also boot to TWRP.
Now this brings me to this thread, 8.3 Stock ROM. The thread assumes one knows how to install it and I suspect this could be as easy as uploading it to a folder in the phone then booting to TWRP and INSTALLING the ZIP file? Could someone clarify the steps to install this 8.3 ROM?
Thanks!
Click to expand...
Click to collapse
Yes. You are correct
Either put the zip file on external sd card , put card into phone boot into recovery mode and install , or put file directly onto phone .
Many ways to do that.
Easiest is to copy to phone while phone is connected to PC.
Cam also download file from internet with your phone.
Bottom line is get zip file to the phone boot to recovery and install

Anyone else having wifi issues after upgrading? While watching videos it seems the internet cuts out. The phone says it's still connected but I have to turn wifi off and back on for anything to work. Could be my router also but it didn't seem to be doing this until I installed 8.3

mrmazak said:
Yes. You are correct
Either put the zip file on external sd card , put card into phone boot into recovery mode and install , or put file directly onto phone .
Easiest is to copy to phone while phone is connected to PC.
Bottom line is get zip file to the phone boot to recovery and install
Click to expand...
Click to collapse
Right on man! I am officially running 8.3 ROM with April 5th 2017 Security Patch Level! Geez.. it was not easy but I got this working!
MrMazak, I followed all your instructions on both links, so could you tell me what exactly I have on my phone? Is it rooted? Bootloader Unlocked? The phone seems to be working fine but I don't know what level of access I have. Honestly I don't even know exactly what the differences between all these terms are.
Also, do I have or not SU? One of the steps under the .bat I believe install it. How do I access it?
Thanks again!
---------- Post added at 10:19 PM ---------- Previous post was at 10:18 PM ----------
Weasel0 said:
Anyone else having wifi issues after upgrading? While watching videos it seems the internet cuts out. The phone says it's still connected but I have to turn wifi off and back on for anything to work. Could be my router also but it didn't seem to be doing this until I installed 8.3
Click to expand...
Click to collapse
My install is pretty fresh, couple of hours, but as far as I can tell all is working fine with Wifi, As a matter of fact this is a new device only connected with Wifi and no SIM Card.... internet works fine.

Please Recommend Me The Top 2/3 Most Stable Slim Roms - New Axon 7 User!

I hate asking this as each has his own preference, however, I have only just ordered my ZTE Axon device as it was such a good offer, being even cheaper than brand new 2018 mid rangers! I purchased the device brand new and sealed for just £193 ($274) so you cannot go wrong.
My current phone was the Sony Xperia XZ Premium but I am giving it away to my wife and need another to replace it.
After some reading it seems the first thing I need to do is install all drivers and run the Axon 7 Tool kit. This will unlock bootloader, root and flash recovery from my understanding.
Then I can proceed to installing a custom rom of my choice followed by immediately flashing a modem otherwise I will not have any signal. Would this be everything needed to successfully running a custom rom trouble free?
Lastly, I would like a simple rom, preferably based on stock/vanilla Android, slim and bloat free. Something very basic, bug free and made for pure speed and decent battery. What are the top recommended roms with this regard? I did look into these, anything better? What are the differences? Thank you so much for your advise.
https://forum.xda-developers.com/axon-7/development/rom-slm-dfnr-t3716825
https://forum.xda-developers.com/axon-7/development/rom-slm-version-t3704143
https://forum.xda-developers.com/axon-7/development/rom-dark-rom-t3654264

kanej2006 said:
I hate asking this as each has his own preference, however, I have only just ordered my ZTE Axon device as it was such a good offer, being even cheaper than brand new 2018 mid rangers! I purchased the device brand new and sealed for just £193 ($274) so you cannot go wrong.
My current phone was the Sony Xperia XZ Premium but I am giving it away to my wife and need another to replace it.
After some reading it seems the first thing I need to do is install all drivers and run the Axon 7 Tool kit. This will unlock bootloader, root and flash recovery from my understanding.
Then I can proceed to installing a custom rom of my choice followed by immediately flashing a modem otherwise I will not have any signal. Would this be everything needed to successfully running a custom rom trouble free?
Lastly, I would like a simple rom, preferably based on stock/vanilla Android, slim and bloat free. Something very basic, bug free and made for pure speed and decent battery. What are the top recommended roms with this regard? I did look into these, anything better? What are the differences? Thank you so much for your advise.
https://forum.xda-developers.com/axon-7/development/rom-slm-dfnr-t3716825
https://forum.xda-developers.com/axon-7/development/rom-slm-version-t3704143
https://forum.xda-developers.com/axon-7/development/rom-dark-rom-t3654264
Click to expand...
Click to collapse
As for the SL!M roms i made ( making some advertisement here ) i only can advise looking at these ones as they are aroma roms and can be debloated further. Battery tweak is included and choice between SuperSU and Magisk is possible. These roms are stock-based as to preserve, imo, the sound quality of the phone as it came out of the box. No bug issues imo and fully up to date :
https://forum.xda-developers.com/axon-7/development/rom-slm-dfnr-t3716825
Based on MiFavor5.0 (CN) but fully applyable on all versions
https://forum.xda-developers.com/axon-7/development/rom-slm-dfnr-t3735003
Based on stock G version but fully applyable on all versions and with the latest security patches of the A2017G-N(ougat)-B09
But then again others can comment on my slim roms better then i can perhap :cyclops:
Futhermore i do not advice https://forum.xda-developers.com/axon-7/development/rom-slm-version-t3704143 as it is was my first version of MiFavor 5.0. Instead use the first link.
Didn't used the last one you mentioned based on LOS but others can advice more into this.
Good Luck and ENJOY !

raystef66 said:
As for the SL!M roms i made ( making some advertisement here ) i only can advise looking at these ones as they are aroma roms and can be debloated further. Battery tweak is included and choice between SuperSU and Magisk is possible. These roms are stock-based as to preserve, imo, the sound quality of the phone as it came out of the box. No bug issues imo and fully up to date :
https://forum.xda-developers.com/axon-7/development/rom-slm-dfnr-t3716825
Based on MiFavor5.0 (CN) but fully applyable on all versions
https://forum.xda-developers.com/axon-7/development/rom-slm-dfnr-t3735003
Based on stock G version but fully applyable on all versions and with the latest security patches of the A2017G-N(ougat)-B09
But then again others can comment on my slim roms better then i can perhap :cyclops:
Futhermore i do not advice https://forum.xda-developers.com/axon-7/development/rom-slm-version-t3704143 as it is was my first version of MiFavor 5.0. Instead use the first link.
Didn't used the last one you mentioned based on LOS but others can advice more into this.
Good Luck and ENJOY !
Click to expand...
Click to collapse
^ Thank you very much raystef66 for your speedy response! I will go for this version - https://forum.xda-developers.com/axon-7/development/rom-slm-dfnr-t3735003
Fingers crossed I should receive my Axon 7 Sunday or Monday at the very latest. First Thing I'll run the Axon 7 Toolkit so that I can unlock the bootloader, have recovery and root then I'll be able to flash your rom, looking forward into doing so!
I'll keep you informed in the coming days when complete. :good:

kanej2006 said:
^ Thank you very much raystef66 for your speedy response! I will go for this version - https://forum.xda-developers.com/axon-7/development/rom-slm-dfnr-t3735003
Fingers crossed I should receive my Axon 7 Sunday or Monday at the very latest. First Thing I'll run the Axon 7 Toolkit so that I can unlock the bootloader, have recovery and root then I'll be able to flash your rom, looking forward into doing so!
I'll keep you informed in the coming days when complete. :good:
Click to expand...
Click to collapse
Yeah, very exciting isn't it :good: It's a damn good phone, quick, nice quality screen and an amazing sound... !
I assume you'll get the G version ? The SL!M➃ is based on this G-version (btw, take a look at the DownloadCenter to have all necessary files) and keeps all things to stock. Just some minor mods and improvements, nothing fancy as to stay stock. With the battery tweak included i always get >7h SOT. But that depends of course on usage. But then again i do alot in a day . Some others have no benefit on the battery tweak but i'll hope you end up with a descent SOT.
Keep us posted :good:

raystef66 said:
Yeah, very exciting isn't it :good: It's a damn good phone, quick, nice quality screen and an amazing sound... !
I assume you'll get the G version ? The SL!M➃ is based on this G-version (btw, take a look at the DownloadCenter to have all necessary files) and keeps all things to stock. Just some minor mods and improvements, nothing fancy as to stay stock. With the battery tweak included i always get >7h SOT. But that depends of course on usage. But then again i do alot in a day . Some others have no benefit on the battery tweak but i'll hope you end up with a descent SOT.
Keep us posted :good:
Click to expand...
Click to collapse
Sounds good! I would be happy with around 7 hours SOT. Once received I'll let you know what version I receive, however, I'm guessing I'll get the Chinese version as it's coming from Dubai, UAE (Middle East) and most likely it'll come from China and not EU as it's much closer.
I have everything ready accept for a flashable TWRP. The link appears down for me and I was not able to find a flashable version, could you please give me a link of a working one? I was only able to find a non flashable version which is run via CMD/fastboot commands.
I would much rather a flashable recovery in which I can flash once installing your rom along with SuperSU or Magisk. Regards!

kanej2006 said:
Sounds good! I would be happy with around 7 hours SOT. Once received I'll let you know what version I receive, however, I'm guessing I'll get the Chinese version as it's coming from Dubai, UAE (Middle East) and most likely it'll come from China and not EU as it's much closer.
I have everything ready accept for a flashable TWRP. The link appears down for me and I was not able to find a flashable version, could you please give me a link of a working one? I was only able to find a non flashable version which is run via CMD/fastboot commands.
I would much rather a flashable recovery in which I can flash once installing your rom along with SuperSU or Magisk. Regards!
Click to expand...
Click to collapse
The TWRP is inside the toolkit, so you can flash it downthere imo. Never done this that way though as in those early days i used this one to do everything. But use the toolkit and you're good to go.

raystef66 said:
The TWRP is inside the toolkit, so you can flash it downthere imo. Never done this that way though as in those early days i used this one to do everything. But use the toolkit and you're good to go.
Click to expand...
Click to collapse
Ah good to hear, glad it's included in the kit. So I can simply use the one from the kit to flash recovery after flashing your rom? Because in the instructions it mentions we have to manually flash recovery after the rom.

kanej2006 said:
Ah good to hear, glad it's included in the kit. So I can simply use the one from the kit to flash recovery after flashing your rom? Because in the instructions it mentions we have to manually flash recovery after the rom.
Click to expand...
Click to collapse
That depends. I dont know what version of twrp is installed via the toolkit. Perhaps it checkes for the latest when it updates but not sure. But if a certain version is installed which is not the latest, put the latest twrp.img onto your int or extSD and flash via your twrp you've installed.
Second, if your phone would be an CN version and not a G, you'll have to install the Universal BL and your specific modem as described in the rom thread. You can find them in the link of the rom thread. So, after installing the Universal BL (which has an older version of twrp !) , you'd have to install the latest via twrp too. So just flash the twrp image and you're good to go.
Btw, i made a flashable zip before of that Universal BL which replaces the old twrp with the 3.1.1.0 version, which will do fine too.
Here's the link : https://androidfilehost.com/?fid=673791459329066038 (it also works on the SLIM4 as it just replaces twrp)
So after installing this version, you dont need to flash another twrp (as it brings you to the 3.1.1.0 as said)

kanej2006 said:
Ah good to hear, glad it's included in the kit. So I can simply use the one from the kit to flash recovery after flashing your rom? Because in the instructions it mentions we have to manually flash recovery after the rom.
Click to expand...
Click to collapse
Uuhh. I think you'll get the G version. Anything else than China and US gets G. With that said, I recommend you two things:
- (If you get a G) Use Controllerboy's guide instead of the toolkit. Lately a lot of stuff is going wrong with the toolkit
-Whatever happens, DO NOT ATTEMPT TO RELOCK THE BOOTLOADER.
-Once you have TWRP, just follow the instructions on each ROM. Never flash stuff from other models.
-Take the TWRP img either from raystef66's download center or from twrp.me

raystef66 said:
I dont know what version of twrp is installed via the toolkit. Perhaps it checkes for the latest when it updates but not sure. But if a certain version is installed which is not the latest, put the latest twrp.img onto your int or extSD and flash via your twrp you've installed.
Second, if your phone would be an CN version and not a G, you'll have to install the Universal BL and your specific modem as described in the rom thread. You can find them in the link of the rom thread. So, after installing the Universal BL (which has an older version of twrp !) , you'd have to install the latest via twrp too. So just flash the twrp image and you're good to go.
Btw, i made a flashable zip before of that Universal BL which replaces the old twrp with the 3.1.1.0 version, which will do fine too.
Here's the link : https://androidfilehost.com/?fid=673791459329066038 (it also works on the SLIM4 as it just replaces twrp)
So after installing this version, you dont need to flash another twrp (as it brings you to the 3.1.1.0 as said)
Click to expand...
Click to collapse
Will do. You are right, the toolkit automatically checks for the latest update and it finds version 3.1.1.0.
Choose an username... said:
Uuhh. I think you'll get the G version. Anything else than China and US gets G. With that said, I recommend you two things:
- (If you get a G) Use Controllerboy's guide instead of the toolkit. Lately a lot of stuff is going wrong with the toolkit
-Whatever happens, DO NOT ATTEMPT TO RELOCK THE BOOTLOADER.
-Once you have TWRP, just follow the instructions on each ROM. Never flash stuff from other models.
-Take the TWRP img either from raystef66's download center or from twrp.me
Click to expand...
Click to collapse
I did see on the forum users attempting to relock the bootloader and it worsened things, I will not attempt this.
Should be able to let you know tomorrow or the day after what version I get and hopefully when I successfully gain recovery and root access!
I just hope I don't get the dead microSD bug that many people have mentioned. Top of the range 64Gb/128Gb MicroSD cards can be costly so I would not like to have them corrupted!

@raystef66, Do you have any other download links for your rom aside from androidfilehost? I tried several different servers but all keep randomly freezing otherwise saying 5 hours, 6 hours, 11 hours and 15 hours. Extremely slow download.

If you want to try a more Android vanilla ROM, then I suggest AICP. Be sure to use the unofficial builds by genesixxbf3. They are very stable and have good features.
https://forum.xda-developers.com/axon-7/development/rom-aicp-12-1-t3611013

kanej2006 said:
@raystef66, Do you have any other download links for your rom aside from androidfilehost? I tried several different servers but all keep randomly freezing otherwise saying 5 hours, 6 hours, 11 hours and 15 hours. Extremely slow download.
Click to expand...
Click to collapse
Yeah, sometime AFH can be cruel. Just depends. I tried the Washington DC just a moment and no problems there. I just advice, take one and let it take it's time. Some way or another the download speed gets stable enough And then again, you still have a bit of time don't you or has it dropped of yet with the postman :cyclops: Do I Hear a heartbeat there ? :good:

raystef66 said:
Yeah, sometime AFH can be cruel. Just depends. I tried the Washington DC just a moment and no problems there. I just advice, take one and let it take it's time. Some way or another the download speed gets stable enough And then again, you still have a bit of time don't you or has it dropped of yet with the postman :cyclops: Do I Hear a heartbeat there ? :good:
Click to expand...
Click to collapse
Haha, no, not yet received! Where I am living at the moment, the weekend is Friday and Saturday, Sunday to Thursday work, strange but that's the way it is.
The seller estimates the item to arrive on Sunday or Monday, hopefully Sunday.
In the end the Netherland's sever finally managed to get me the 2.1Gb download complete. I did try others but were slower. Good thing in your rom you included the 3 different models for the Axon 7. I'm yet to see which one I receive!

Confirmed G version received.

kanej2006 said:
Confirmed G version received.
Click to expand...
Click to collapse
The AcTiOn can begin :good:
Use this guide like said above and you'll be ok.

raystef66 said:
The AcTiOn can begin :good:
Use this guide like said above and you'll be ok.
Click to expand...
Click to collapse
Not working, been trying for hours.
Not connecting despite all drivers installed, including Qualcom driver. Followed all instructions as stated. Stuck from number 20. When entering this command I get ''failed to connect''
When typing in adb devices it finds my device.
1) Backup all the data of your phone's internal memory that you don't want to lose. Copy it to your PC
2) Download the axon7tool from here: http://www.filedropper.com/axon7tool-15-win64
3) Download minimal adb and fastboot from here: https://www.androidfilehost.com/?fid=457095661767103465
4) Unzip the minimal adb and fastboot file, place the folder with the files in it somewhere you can easily find it
5) Place the axon7tool exe in the same folder as adb.exe and rename it to "axon7tool.exe" (it's easier to work with that way)
6) Download the TWRP .img and .bin files from here: https://drive.google.com/open?id=0B4...nlaZU1NRldoRjA
7) Place the TWRP .img file in the same folder as "adb.exe" and "axon7tool.exe", rename it to "recovery.img"
8) Make a copy of the "recovery.img" file and name it "recovery.bin". Leave it in the same folder
9) Go to settings in your phone and go to "About Phone". Tap "Build Number" 7 times to make the Developer Options available
10) Go to "Developers options" and tick "Allow OEM unlock" and "Android Debugging"
11) Connect your Axon 7 to your PC
12) Open a command window by holding shift and right-clicking in a blank space in the folder where the "adb.exe", " axon7tool.exe", "recovery.img" and "recovery.bin" files are located. Click "Open command window here"
13) Type "adb devices" and hit enter. You should see one device with some code listed
14) Type "adb reboot edl" and hit enter. Your device will reboot to EDL mode. It appears to be off, but it is in fact in EDL mode.
15) Go to Device Manager on your pc and verify your Axon 7 is listed as "QUSB_BULK"
16) In command, type "axon7tool -r gpt boot recovery" and hit enter
17) After it is executed, your phone will reboot. Wait until it has fully booted.
18) In command, type "adb reboot edl"
19) Verify you now have 3 backup files in your ADB folder for gpt, recovery and boot. These are backup files in case something goes wrong
20) In command, type "axon7tool -w recovery" - STUCK HERE - FAILED

kanej2006 said:
Not working, been trying for hours.
20) In command, type "axon7tool -w recovery" - STUCK HERE - FAILED
Click to expand...
Click to collapse
You're on nougat ? Look into about phone for that.
Afaik, you'll have to be on MM. So downgrade/rollback if on Nougat (look into DownloadCenter for B10 or B11) and do the procedure all over again.
Imo it's due to that.
edit: sure you have the recovery.img and bin in your adb folder ?

raystef66 said:
You're on nougat ? Afaik, you'll have to be on MM. So downgrade/rollback if on Nougat (look into DownloadCenter for B10 or B11) and do the procedure all over again.
Imo it's due to that.
edit: sure you have the recovery.img and bin in your adb folder ?
Click to expand...
Click to collapse
No, I am on stock MM.

kanej2006 said:
No, I am on stock MM.
Click to expand...
Click to collapse
Should work then.
Can you download recovery again. Check all characters if they're all written ok.
Sure the toolkit cannot bring enlightment too ?

GUIDE to go from BUGGY VENDOR ROM with UNLOCKED BOOTLOADER to 8.8.9 XIAOMI.EU

GUIDE to go from BUGGY VENDOR ROM with UNLOCKED BOOTLOADER to 8.8.9 XIAOMI.EU:
Download 8.8.9 xiaomi.eu from one of these 3 links: 1) https://www.androidfilehost.com/?w=files&flid=280379 2) https://sourceforge.net/projects/xi...s/files/xiaomi.eu/MIUI-WEEKLY-RELEASES/8.8.9/ 3) http://miui.dedyk.gq/8.8.9/xiaomi.eu_multi_MIMAX3_8.8.9_v10-8.1.zip
1) Flash China Beta 8.8.9 with Mi Flash Tool using the option "Clean All" (DO NOT choose 'Clean All and Lock'). Links and instructions below:
a) China Beta 8.8.9: bigota.d.miui.com/8.8.9/nitrogen_images_8.8.9_20180809.0000.00_8.1_cn_7bfe310762.tgz
b) Mi Flash Tool:
1b) download link: https://xiaomiflashtool.com/download/xiaomi-flash-tool-20180528
2b) instructions on how to use: https://xiaomiflashtool.com/tutorial/use-xiaomi-flash-tool
3) Let your China rom boot up, then login to your Mi Account (if you haven't made one yet, make it here: https://global.account.xiaomi.com/pass/register).
4) Once logged in, go to Settings>Additional Settings>Developer Options>Turn ON USB Debugging, Install via USB, and USB Debugging (Security Settings).
5) Download Minimal ADB and Fastboot: https://forum.xda-developers.com/showthread.php?t=2317790. Extract it to your desktop so you can use it from there easily and rename the folder to ADB.
6) Download TWRP Recovery: https://eu.dl.twrp.me/nitrogen/twrp-3.2.3-0-nitrogen.img.html. Rename it to recovery.img and place it in your ADB folder.
7) Open cmd (Windows Command Processor/command prompt) within ADB folder or navigate there directly by opening cmd and enter the following steps: cd C:\Users\WhateverYourUsernameIs\Desktop\ADB (this puts you in the ADB folder).
8) Turn your phone off. Boot your phone back into FASTBOOT MODE (press and hold VOLUME DOWN and POWER for 6-8 seconds), then plug it into your computer. In cmd, enter the following:
fastboot format userdata, then flash TWRP using the following commands: fastboot flash recovery recovery.img, then boot to recovery using the following commands: fastboot boot recovery.img
9) Changing file system from ext4 to f2fs is NOT NECESSARY, but I included it in case you run into errors, so skip to the WIPE portion of this section: In TWRP, change your file system from ext4 to f2fs: Wipe > Advanced Wipe > Data > Repair or Change File System > Change File System > F2FS. Once changing the file system to f2fs, you must go back (back button at the bottom) and reboot to recovery in the REBOOT section of TWRP: Reboot>Reboot to Recovery. Once you're booted back into recovery, mount all your partitions: Mount>Check All Partions. Then go back, select WIPE>Advanced Wipe> select Data, Dalvik Cache and Internal Storage (System should NOT be wiped).
10): Transfer 8.8.9 xiaomi.eu rom from your pc to phone's internal storage and install in TWRP: INSTALL>Zip>Select 8.8.9 xiaomi.eu rom>Flash it.
11) REBOOT. The phone should boot without issue and your bootloader should stay unlocked.
12) Enable VoLTE: Once everything is set up, go to dialer and enter the following: *#*#86583#*#*
If you get this encryption issue after flashing: "Encryption was interrupted and can't be completed after reboot" then look at:
https://xiaomi.eu/community/threads...ed-and-cant-be-completed-after-reboot.45640/, thanks @erwinsie :highfive:
IF YOU WANT ROOT:
1) Download Magisk 17.1 Stable: https://github.com/topjohnwu/Magisk/releases/download/v17.1/Magisk-v17.1.zip
2) Reboot to Recovery : Turn off phone, press and hold VOLUME UP + POWER for 6-8 seconds until you see the phone boot into TWRP. Select INSTALL>Zip>Magisk-v17.1.zip>Flash it and reboot.
Thanks and credit to: @omer919 and @martin.burgas - I used some of your install ideas to help everyone :highfive:.
If you have any further questions, suggestions, or anything you'd like to add, just let me know. Thanks.

May I ask why do you change the partition formatting from ext4 to f2fs as it is not necessary?

dogiex said:
May I ask why do you change the partition formatting from ext4 to f2fs as it is not necessary?
Click to expand...
Click to collapse
You don't need to. @martin.burgas did it I believe because he ran into some errors. I know that people get sd card corrupted on ext4 when they install gsi roms, so maybe he was future proofing in case shifting over to an android gsi rom? I'm not 100% sure. Maybe @omer919 or @martin.burgas can answer better.

And please don't call 9.6.4 fake... Call it first release, buggy whatever but not fake b/c it isn't...
Forum is full with confusing info and people...

nijel8 said:
And please don't call 9.6.4 fake... Call it first release, buggy whatever but not fake b/c it isn't...
Forum is full with confusing info and people...
Click to expand...
Click to collapse
My mistake due to helping someone that called it that, but I fixed it. Thanks for the reminder.

Not being argumentative - just curious. When some resellers began shipping the Mi Max 3 two months ago with the 9.6.4 "global" ROM (in Chinese retail boxes), Xiaomi had not yet released an international/global variant of the phone. The only version was the CN (China) variant. Xiaomi did not even list the Mi Max 3 at the time on its global web site. Two months later Xiaomi released the international variant of the phone for the first time outside mainland China - in Hong Kong, then Singapore, the Philippines, and finally Malaysia. These international variants of the phone are sold with the 9.6.7.0 "global ROM" and they come in boxes with English labeling, clearly marked with the red "Global" factory sticker. So where did the 9.6.4 "vendor/global" ROM which clearly has a broken modem because of all the complaints about phone call connectivity come from? If it isn't from Xiaomi what would you call it?
---------- Post added at 08:42 PM ---------- Previous post was at 08:39 PM ----------
Thank you for this excellent guide. I adopted this approach after much trial and error when my phone arrived last month. This guide would have saved me hours of pulling my hair out. I've stayed on xiaomi.eu 8.8.9 since.

frcraig said:
Not being argumentative - just curious. When some resellers began shipping the Mi Max 3 two months ago with the 9.6.4 "global" ROM (in Chinese retail boxes), Xiaomi had not yet released an international/global variant of the phone. The only version was the CN (China) variant. Xiaomi did not even list the Mi Max 3 at the time on its global web site. Two months later Xiaomi released the international variant of the phone for the first time outside mainland China - in Hong Kong, then Singapore, the Philippines, and finally Malaysia. These international variants of the phone are sold with the 9.6.7.0 "global ROM" and they come in boxes with English labeling, clearly marked with the red "Global" factory sticker. So where did the 9.6.4 "vendor/global" ROM which clearly has a broken modem because of all the complaints about phone call connectivity come from? If it isn't from Xiaomi what would you call it?
---------- Post added at 08:42 PM ---------- Previous post was at 08:39 PM ----------
Thank you for this excellent guide. I adopted this approach after much trial and error when my phone arrived last month. This guide would have saved me hours of pulling my hair out. I've stayed on xiaomi.eu 8.8.9 since.
Click to expand...
Click to collapse
From all my reading of different forums including this one, I came to the conclusion that the 9.6.4.0 just like many beta/leaked roms was from a Xiaomi direct source, but simply incomplete or compiled in a similar fashion to nightly roms. Things that are early or beta are released beforehand to also build sales whether they are broken or not - take a look at all of us that bought actual Chinese handsets compared to official global ones; in addition, updates are readily available from xiaomi sources - how else would a guide like this or fixes by developers be possible? No one even knew if there would be an official global version 100% until only recently. Even Honor was thought to have a Global version of the Honor Note 10 coming at Berlin, but that never happened. A lot of these resellers use/swap/reuse similar people/companies - that is a fact. Take a look at all the Chinese phones, cases, screen protectors, etc out there that are identical copies.
TLDR: 9.6.4.0 - official but broken because it was an incomplete nightly/beta similar to what Nijel said above. It was released for sales and weighing the international market (my opinion). It worked.
You are most welcome :highfive:. Part of me wanted to do this sooner, but wasn't sure how much it was needed until now. I hope it helps future users and if anyone finds any better methods or tweaks to this guide, let me know and I'll gladly adjust it accordingly.

nijel8 said:
And please don't call 9.6.4 fake... Call it first release, buggy whatever but not fake b/c it isn't...
Forum is full with confusing info and people...
Click to expand...
Click to collapse
9.6.4.0 was originally called a 'Global ROM', it was not the authentic Global ROM from Xiaomi therefore it WAS a fake Global ROM. It is as simple as that.
Omer919's first language might not be English but his use of the word 'fake' was not incorrect.

I'm missing something??
I received two days ago one of this phones, ublocked and with 9.6.4.0(OEDMIFD).
I upgrade with internal updater to 9.6.6.0(OEDMIFD) without problem and use the phone one day
next day I install TWRP and go to las xiaomi.eu v10 version -> xiaomi.eu_multi_MIMAX3_8.9.20_v10-8.1.zip
I am using the phone one and looks everything ok
Is there a problem with these steps , is dangerous? The only thing is that now I have ARB activated, is ok??
Thanks a lot

Wam7 said:
9.6.4.0 was originally called a 'Global ROM', it was not the authentic Global ROM from Xiaomi therefore it WAS a fake Global ROM. It is as simple as that.
Omer919's first language might not be English but his use of the word 'fake' was not incorrect.
Click to expand...
Click to collapse
Aaah, omer919... All confusing/incorrect info here came from his copy/paste abilities from Xiaomi forums...
Read the next post below yours! If 9.6.4 was fake and not leaked from Xiaomi then it wouldn't be possible to update to 9.6.6 with the built-in MIUI updater, would it? Updater and the stock recovery as part of the updae process connects to 4 Xiaomi servers and verifies both currently running rom and the one to be installed. How about that for an argument...
9.6.4 is Xiaomi's first beta global rom for Max 3 for internal testing and retailer got hads on it before global device release period... Devices that are selling with 9.6.4 pre-installed and unlocked are fake global versions, not the rom. Simple as that.

jamarita said:
I received two days ago one of this phones, ublocked and with 9.6.4.0(OEDMIFD).
I upgrade with internal updater to 9.6.6.0(OEDMIFD) without problem and use the phone one day
next day I install TWRP and go to las xiaomi.eu v10 version -> xiaomi.eu_multi_MIMAX3_8.9.20_v10-8.1.zip
I am using the phone one and looks everything ok
Is there a problem with these steps , is dangerous? The only thing is that now I have ARB activated, is ok??
Thanks a lot
Click to expand...
Click to collapse
MIMAX3_8.9.20 have some bugs, best rom for now is 8.8.9 older but dont have bugs and dont have ARB. When You install 8.9.20 You activated ARB and if You want to update ROM You have to use only higher number, so You have to wait for new releases of xiaomi.eu.

jamarita said:
I received two days ago one of this phones, ublocked and with 9.6.4.0(OEDMIFD).
I upgrade with internal updater to 9.6.6.0(OEDMIFD) without problem and use the phone one day
next day I install TWRP and go to las xiaomi.eu v10 version -> xiaomi.eu_multi_MIMAX3_8.9.20_v10-8.1.zip
I am using the phone one and looks everything ok
Is there a problem with these steps , is dangerous? The only thing is that now I have ARB activated, is ok??
Thanks a lot
Click to expand...
Click to collapse
You are ARB activated, but you'll l be fine. Just don't flash any version before your current one or you'll risk bricking your device. If you run into any trouble post here, and we'll help you. Do me a favor and edit your post because you should never quote the first large OP (original post). Thanks :highfive:

nijel8 said:
...
Read the next post below yours! If 9.6.4 was fake and not leaked from Xiaomi then it wouldn't be possible to update to 9.6.6 with the built-in MIUI updater, would it? Updater and the stock recovery as part of the updae process connects to 4 Xiaomi servers and verifies both currently running rom and the one to be installed. How about that for an argument...
9.6.4 is Xiaomi's first beta global rom for Max 3 for internal testing and retailer got hads on it before global device release period... Devices that are selling with 9.6.4 pre-installed and unlocked are fake global versions, not the rom. Simple as that.
Click to expand...
Click to collapse
Let's not start employing argumentum ad hominem or getting bogged down in semantics. It really is quite straight forward.
1. The original retailers were touting this leaked/early beta ROM as a genuine Xiaomi sanctioned, official Global ROM. Let me repeat that again as it is salient point.
The original retailers were touting this leaked/early beta ROM as a genuine Xiaomi sanctioned, official Global ROM
2. Dictionary definition of "Fake"; "a thing that is not genuine."
3. Therefore your point that the word 'Fake' was incorrectly used is a fallacy itself. This is my only point.
4. You can sidetrack all you want and talk about issues that I am not referring to in order to obfuscate the simple issue here; there was nothing wrong with the use of the 'fake', contrary to what you stated.

This thread is not about the namoe of rom but about flashing working properly rom, so it isnt important how people call this rom. Focus on rly helpfull solution...

opasha said:
You don't need to. @martin.burgas did it I believe because he ran into some errors. I know that people get sd card corrupted on ext4 when they install gsi roms, so maybe he was future proofing in case shifting over to an android gsi rom? I'm not 100% sure. Maybe @omer919 or @martin.burgas can answer better.
Click to expand...
Click to collapse
Yes, I changed the file system not to get any errors. I red that some users encounter error 4 , when trying to wipe data, cache and etc. in TWRP and that switching to f2fs fixes the problem. In the main post, just one thing should be changed - if someone changes the file system from ext4 to f2fs, then need to hit back button and then Reboot and choose Recovery, so to reboot TWRP after changing the file system, then follow the rest of the guide.

martin.burgas said:
Yes, I changed the file system not to get any errors. I red that some users encounter error 4 , when trying to wipe data, cache and etc. in TWRP and that switching to f2fs fixes the problem. In the main post, just one thing should be changed - if someone changes the file system from ext4 to f2fs, then need to hit back button and then Reboot and choose Recovery, so to reboot TWRP after changing the file system, then follow the rest of the guide.
Click to expand...
Click to collapse
Thanks, Martin :highfive:. I edited Step 9 of the guide to reflect what you said. If it's worded incorrectly, let me know.

Error fastboot
I have a mi max 3, bootloader unlock and with the global version 9.6.4.0 . I am trying to install the eu version 8.8.9, but when i put the phone in fastboot and try to install the rom the phone turn the screen black and said press any button to shut down, so i cannot do anything.

yuoi said:
I have a mi max 3, bootloader unlock and with the global version 9.6.4.0 . I am trying to install the eu version 8.8.9, but when i put the phone in fastboot and try to install the rom the phone turn the screen black and said press any button to shut down, so i cannot do anything.
Click to expand...
Click to collapse
What step are you messing up on? Big difference in steps between fastboot and rom flashing. That's why I made numbers. Be more specific, otherwise, it's obvious you did it incorrectly.

opasha said:
What step are you messing up on? Big difference in steps between fastboot and rom flashing. That's why I made numbers. Be more specific, otherwise, it's obvious you did it incorrectly.
Click to expand...
Click to collapse
Step 2b the instruccions said that to flash the phone we need to put it in fastboot and when i try to install the china rom my phone turn black and said press any buttom to turn off. I dont know how to explain it well its seems that when the mi flash try to detect the phone something go wrong.

yuoi said:
Step 2b the instruccions said that to flash the phone we need to put it in fastboot and when i try to install the china rom my phone turn black and said press any buttom to turn off. I dont know how to explain it well its seems that when the mi flash try to detect the phone something go wrong.
Click to expand...
Click to collapse
Looks like a driver issue. Use mi suite instead: http://pcsuite.mi.com/

Patched 11.0.12.12.KB05AA ROM for rooted users - install from Fastbootd!!!

[UPDATE]:
**********
I got sick of my phone telling me I needed to update but I couldn't because I'm rooted. So finally got around to patching the last full ROM today w/ the incremental.
This is the fastbootd w/ flash_all.bat script to update to 11.0.12.12.KB05AA. The package for KB05AA (Global/US) is not yet available, hence I'm still making it available here. Be sure to alter the flash script (remove the "rem" before boot.img and recovery.img if you DO NOT want to keep your custom kernel + TWRP) ****************
3.14 GB file on MEGA
mega.nz
THIS IS ONLY FOR 11.0.9.9.KB05AA, BUT READ IT ANYWAY!!!!: ***************
I think this is the first time anyone has actually made a working incremental update for a rooted OOS device, or any with a payload.bin update method that I know of. This method doesn't require any wiping and TWRP / rooted boot.img / custom OOS kernel can be installed right after the script finishes (or left on the device), and you don't even change your active slot (usually, incremental updates will flash to the inactive slot).
I won't get into that many specifics except it was EXTREMELY DIFFICULT, but it works now. Read here if you want to do it yourself in the future, or on another phone. Should work on just about any phone that uses payload.bin files https://forum.xda-developers.com/t/...11-0-9-9-kb05aa-posted.4314677/#post-85425949
You may have to edit the .bat file to pick your RAM type (the lp5 ones are for devices with LPDDR5; it is preset for most of the phones using the LPDDR4 RAM). On the Op8T at least you can do this from adb shell:
adb shell getprop ro.boot.ddr_type; where a 0 is LPDDR4 and 1 is LPDDR5 ram. If it's 1 returned, you need to flash the lp5 files instead of the same named otherwise files in the .bat file (so edit it).
That weird -cow stuff is temp files that prevented the update from working. Not documented anywhere I could find (well, minimally explained by Google), took hours to figure out they were filling the super partition up. I had to re-engineer a Linux project (linked above) to get this working, and have officially updated from 11.0.8.13 to 11.0.9.9 COMPLETELY now. While rooted, without switching slots, and TWRP installed.
You just have to ensure you're on the latest ADB and Fastboot tools and an adb reboot bootloader, followed by a fastboot reboot fastboot should get you there. You can check with: fastboot getvar is-userspace
If it says yes, you're in fastbootd. It actually will work with TWRP installed, I found out later, as long as you reboot in TWRP to fastboot and confirm with the command above you're in fastbootd.
https://github.com/fawazahmed0/Latest-adb-fastboot-installer-for-windows/releases/tag/v1.7 has a script that will get you the Latest ADB and Fastboot and put it in a folder for you.
I uploaded it to Mega. Just use some common sense and look at the flash_all.bat file before flashing. I'd write more but I'm tired as hell from getting this working. Now we'll never have to wait for an incremental update while rooted again, at least in the foreseeable future.

I'm just going to leave this here
https://forum.xda-developers.com/t/...1-kb2003-kb2005.4178675/page-25#post-85386145

g96818 said:
I'm just going to leave this here
https://forum.xda-developers.com/t/...1-kb2003-kb2005.4178675/page-25#post-85386145
Click to expand...
Click to collapse
That never worked for me and others, Always resulted in either bootloop or booting back to previous build

nujackk said:
That never worked for me and others, Always resulted in either bootloop or booting back to previous build
Click to expand...
Click to collapse
I've mentioned it multiple times for people having issues. They need to use the unbrick tool cause there is something wrong with the original rom install from OnePlus.

g96818 said:
I've mentioned it multiple times for people having issues. They need to use the unbrick tool cause there is something wrong with the original rom install from OnePlus.
Click to expand...
Click to collapse
This Devs solution works and i appreciate his work. And appreciate your attempts but didn't work for me So ....

nujackk said:
This Devs solution works and i appreciate his work. And appreciate your attempts but didn't work for me So ....
Click to expand...
Click to collapse
It's good that you found a band-aid fix.

nujackk said:
That never worked for me and others, Always resulted in either bootloop or booting back to previous build
Click to expand...
Click to collapse
Of course I tried that solution first, it didn't work on my device.
I'm glad it did on others' devices, kudos to you for posting it (and I DO appreciate your work), but this is the only one that worked on mine. Why? Who knows. I also followed another guide that didn't work. Or else I wouldn't have wasted all my time making this (it took many, many hours to assemble). I'm not saying it's the best solution (I really hope someone just uses what I put in the other thread and assembles it into an easier format for others to use), but I have a full time job (2 actually) so I can't work on it anymore. But it works, no data loss, and TWRP can be installed. Until the next incremental update comes out, then I'll post another version using the tools I used for this, if your build doesn't work on my device. But only when I have the time...

g96818 said:
It's good that you found a band-aid fix.
Click to expand...
Click to collapse
LoL band-aid fix... Call it whatever you want, it works.
It's actually a patched 11.0.8.3.KB05AA with the incremental update applied to it for 11.0.9.9.KB05AA. So it flashes to the active slot and TWRP / rooted custom kernel can all be installed at the same time, even while you are still rooted with Magisk, and even if TWRP is installed. No data loss. I never claimed perfection on this project, just that it works for me.
Keep doing what you're doing, I'll keep doing what I'm doing. We both just aim to help others anyway. I just couldn't get any other method to work so I came up with this one, extending on the incomplete / abandoned work of others. I didn't come up with Payload extraction. Never claimed to. I didn't come up with fastbootd flashing either.
All the forked and modified code is at my GitHub repo. The fork goes back to several other devs' forks (mine is the 3rd modified fork).

Someone want to point me to the right download for the incremental update to 11.0.9.9.KB05AA? I got a download link but if it's not for this exact ROM, it would be dangerous (I don't know what would break) if I applied it and patched the incremental 11.0.9.9 (which is like a full ROM in the way I distribute it here). I believe the update is 11.0.10.10.KB05AA. I tried downloading as illustrated in the linked thread and it halfway installed (Op8T's don't seem to like the "remove Magisk images" and then install the update method, it totally jacked up my system (like long boot time, alarms didn't work, numbers wouldn't always appear to login to the phone after reboot, etc.), luckily I had backed up Super in TWRP and that fixed it (upon a restore). The one someone told me was the official link to the incremental update did not work with the Linux program I hacked, so it's either incapable of patching an incremental 2x, or I got the wrong file downloaded. My life is so crazy at the moment I don't have time to screw up my phone just to get the incremental update downloaded on my phone and extract it, so if anyone has already done that, please let me know.

mslezak said:
Someone want to point me to the right download for the incremental update to 11.0.9.9.KB05AA? I got a download link but if it's not for this exact ROM, it would be dangerous (I don't know what would break) if I applied it and patched the incremental 11.0.9.9 (which is like a full ROM in the way I distribute it here). I believe the update is 11.0.10.10.KB05AA. I tried downloading as illustrated in the linked thread and it halfway installed (Op8T's don't seem to like the "remove Magisk images" and then install the update method, it totally jacked up my system (like long boot time, alarms didn't work, numbers wouldn't always appear to login to the phone after reboot, etc.), luckily I had backed up Super in TWRP and that fixed it (upon a restore). The one someone told me was the official link to the incremental update did not work with the Linux program I hacked, so it's either incapable of patching an incremental 2x, or I got the wrong file downloaded. My life is so crazy at the moment I don't have time to screw up my phone just to get the incremental update downloaded on my phone and extract it, so if anyone has already done that, please let me know.
Click to expand...
Click to collapse
Better to install the full ROM
Download Oxygen Updater in app store and select your device AA for global and Ba for European device.
Go to settings, system update wait til 100% and Don't reboot yet if you want to keep Root
Go to Magisk and install ota in inactive slot

5star02707 said:
Better to install the full ROM
Download Oxygen Updater in app store and select your device AA for global and Ba for European device.
Go to settings, system update wait til 100% and Don't reboot yet if you want to keep Root
Go to Magisk and install ota in inactive slot
Click to expand...
Click to collapse
I think maybe you misunderstood what I did in this thread. I patched a full ROM with the incremental update of 11.0.9.9.KB05AA. So while OnePlus does not have a full ROM available for download (yet), it is available for download here.
Yeah the method you propose is the "normal" rooted way, but if you're rooted already it forces you to full ROMs not OTAs. You'll be on 11.0.8.3.KB05AA. The goal here is to get on 11.0.10.10.KB05AA (someone NOT ROOTED could download the OTA update using Oxygen Updater and upload it here so I could make a patched version for those that want to keep their root / custom kernel / TWRP / etc and avoid the hassle of unrooting first, which wipes your data partition). At least my Oxygen Updater won't let me download incremental updates even with Magisk Images removed (don't try this unless you're on Op8 / Op8 Pro; some people are having big system update issues on Op8T incremental hence why this thread exists.) It jacked up my system pretty bad (Magisk images removed, Settings / System / System Updates method) until after a boot.img and super restore from TWRP. Not all devices were setup the same (mine is a US carrier converted to US KB05AA). To my knowledge, no direct download has been posted for KB05AA incremental update. Here or on TG. If you have found one, please post a link here. The only one out I've seen works on European ROMs. OnePlus always does KB05AA last for whatever reason.

11.0.10.10.KB05AA posted with caveats - please back up your data as suggested in case the Phone Services APK doesn't fix your SIM after a flash, and you end up formatting the data partition. You may want to try some other methods or just plan on restoring (not with TWRP Alpha in my experience).

mslezak said:
Guys, bad news. So 11.0.10.10.KB05AA incremental does something to the data partition and kills your SIM access.
...
Click to expand...
Click to collapse
I successfully update from 9.9 to 10.10 including keeping root. I have no issues with my Sim card. So, for me, the update is fine.
However, I believe that the 10.10 update includes a key change. This results in the data partition being unreadable if you swap back to the previous slot after the update. I found this out by doing just that using TWRP.
But syncing the 10.10 firmware to the inactive slot fixes this. It might be possible (I haven't tried it) to just sync the keymaster partition to the inactive slot and then restore 9.9 (excluding keymaster).

BillGoss said:
I successfully update from 9.9 to 10.10 including keeping root. I have no issues with my Sim card. So, for me, the update is fine.
However, I believe that the 10.10 update includes a key change. This results in the data partition being unreadable if you swap back to the previous slot after the update. I found this out by doing just that using TWRP.
But syncing the 10.10 firmware to the inactive slot fixes this. It might be possible (I haven't tried it) to just sync the keymaster partition to the inactive slot and then restore 9.9 (excluding keymaster).
Click to expand...
Click to collapse
Can you explain how you managed to update it? I'm screwed at this point anyhow, would like to hear how you did it. Are you just saying when you update flash to both slots and the data is still readable? Instead of flashing to active only? I still have the extracted / patched ROM, not going to try it out now (or for a while) unless I know someone has figured out a way to make it not break the system data. (Note: I'm on a very hacked phone; it's a carrier T-mobile originally fastbootd converted to Global, then updated on Global since then). I realize most people probably don't have a phone that's been altered this much. Then the easier methods are more likely to work. I'm also running a custom fork (mine) of RadioActive kernel (just tweaked how I like it, wakelocks blocked to save idle battery, some GPU frequencies added, etc). I tried running just the patched boot.img with Magisk but still Phone Services was busted.

@mslezak, When I get an update I:
- use a terminal session (you could also use ADB) to restore the stock boot and recovery (this way I don't lose root yet)
- install the update but don't reboot
- copy the new boot image and patch it
- turn on airplane mode (to avoid SafetyNet and certification issues in the next step)
- reboot the phone and the updated system comes up
- flash the patched boot image and TWRP in fastboot/bootloader
- reboot and disable airplane mode
This is basically @osm0sis' process from https://forum.xda-developers.com/t/...ices-platforms.2239421/page-149#post-84764713
No, I'm not saying flash to both slots, because that will make it impossible to fall back to the current system if the update fails (though this is meaningless if you're manually flashing partitions).
I've got into the habit of syncing active to inactive (after I'm happy with the update) simply because it's required when going from OOS to a custom ROM (I use a shell script based on the LineageOS sync zip). And, after the sync, I can now access the data partition from the inactive slot (which wasn't the case just after the update due to the different keys).

mslezak said:
Can you explain how you managed to update it? I'm screwed at this point anyhow, would like to hear how you did it. Are you just saying when you update flash to both slots and the data is still readable? Instead of flashing to active only? I still have the extracted / patched ROM, not going to try it out now (or for a while) unless I know someone has figured out a way to make it not break the system data. (Note: I'm on a very hacked phone; it's a carrier T-mobile originally fastbootd converted to Global, then updated on Global since then). I realize most people probably don't have a phone that's been altered this much. Then the easier methods are more likely to work. I'm also running a custom fork (mine) of RadioActive kernel (just tweaked how I like it, wakelocks blocked to save idle battery, some GPU frequencies added, etc). I tried running just the patched boot.img with Magisk but still Phone Services was busted.
Click to expand...
Click to collapse
Thats not very hacked/hacked at all, and quite a few use that setup

xstefen said:
Thats not very hacked/hacked at all, and quite a few use that setup
Click to expand...
Click to collapse
LoL I gave up fastbootd flashed to 11.0.10.10.KB05AA and formatted data, let Google download everything it backed up, and am back in business. Just have a lot of apps to login to / Magisk modules to add / etc.
So yeah my patched 11.0.10.10.KB05AA works but the data must be formatted or the SIM doesn't work (at least for me; I don't know if anyone else has tried it since I just posted it a few hours ago; it could be that it works for some without causing issues, I don't have any idea). The goal was to not have to mess up the data partition.... but I can't control what OnePlus does in their updates... Try what worked for others posted here first I'd suggest, or just make solid backups of everything knowing you're going to likely need to reinstall / re-login to everything and format the data partition. New pin, new fingerprint, etc. Re-login to your wifi blah blah.
It's still a full unreleased ROM so I posted it for those that don't mind taking backups (outside of TWRP) if they want to keep root & TWRP on the new release... Yeah a pain to setup if you aren't warned to use another backup method (maybe there is a better backup method, maybe Migrate (app store early access) is developed enough for easy transfer now, I know many people said it worked well in the past but haven't been following the updates. Still free).

It dawned on me later that since the only thing that didn't work using this method going from 11.0.9.9.KB05AA to 11.0.10.10.KB05AA was phone services, that I should just include the working version in this post. Since I already did it the hard way and restored everything back to normal. AS I SAID ABOVE, IF PHONE SERVICES ISN'T ENOUGH TO FIX THE ISSUE, PM ME AND I CAN EXTRACT MORE RELATED FILES UNTIL IT WORKS AGAIN. Unfortunately, I can't just downgrade to 11.0.9.9.KB05AA and keep trying fastbootd over and over again as I don't have the time.

g96818 said:
I've mentioned it multiple times for people having issues. They need to use the unbrick tool cause there is something wrong with the original rom install from OnePlus.
Click to expand...
Click to collapse
The whole point of this is to AVOID the unbrick tool, reinstalling an outdated version, updating each new ROM build since the brick tool was made, and starting over clean. I think... Have a hunch at least we're almost there on 11.0.10.10.KB05AA with an APK install... Although just backing up everything first will always work (if you don't mind formatting your data partition) just as it's posted here already. Always an issue for us rooted users (especially on Global) since we're always last in line to get a full ROM. This IS a full ROM, payload extracted and patched with incremental updates. Still not available from OnePlus Global (KB05AA) as I checked today, so still relevant.

Ladies and Gents,
I have removed some off topic posts from this thread because I believe we could express the same meaning in more civil words. Please try to do that from now on.
Thanks.
Jerry
FSM

Database Users

welcome