So when I first received this Device i was using Stock Rom for quite a while but then was tempted to convert it to the Mi 6X (which is basically the same device but with MIUI)
Did the Flash Process in fastboot and sucessfully converted it to a Mi 6X. (you will have to swap some files tough)
But here come the problems: As you may know they implemented that complete bs Anti-Rollback Feature in newer MIUI Roms. So I was on the newest MIUI 10 Developer Rom and wanted to go
back to the latest 9 Stable. Flashed the Rom and: boom. device bricked. Since your device is no longer a A2 ( no more A/B partition layout ) you face the same problem as a 6X User.
You simply CANNOT flash the device no matter if you are in EDL our use the test points.
So there is NO way to restore the converted phone back to Stock unless you have access to a developer account.
At this point i can only WARN people. You absolutely CAN USE MIUI also without bricking your device, but there is NO WAY TO GET BACK IF YOU END UP BRICKED SOMEHOW.
Can you explain in details how you flashed miui?
Sent from my Mi A2 using Tapatalk
I will post the whole process and edit this reply, just give me some time.
I want to do the full guide when I have 10 posts so I can post links aswell
windforce3425 said:
I will post the whole process and edit this reply, just give me some time.
I want to do the full guide when I have 10 posts so I can post links aswell
Click to expand...
Click to collapse
Could we talk on Telegram and Guide me !
For what i read you needed to desactivate the Anti-Rollback protection first. And you will get no problems. But you missed that and now is no turning back ( for now).
I have also curiosity so see if a A2 works good with MIUI, and if the B20 is enable with 6x firmware.
The ultimate wish has to get a dual boot system for Android one an MIUI and get the best of two OS.
ki69 said:
For waht i read you needed to desactivate the Anti-Rollback protection first. And you will get no problems. But you missed that and now is no turning back ( for now).
I have also curiosity so see if a A2 works good with MIUI, and if the B20 is enable with 6x firmware.
The ultimate wish has to get a dual boot system for Android one an MIUI and get the best of two OS.
Click to expand...
Click to collapse
B20 is working fine i can guarantee that since I live in germany and it's the most important band if you are outside of citys.
windforce3425 said:
I will post the whole process and edit this reply, just give me some time.
I want to do the full guide when I have 10 posts so I can post links aswell
Click to expand...
Click to collapse
Could u guide me on Telegram !
windforce3425 said:
B20 is working fine i can guarantee that since I live in germany and it's the most important band if you are outside of citys.
Click to expand...
Click to collapse
Tks, for the info. If you ahve the time tell what you think of the use of MIUI, ( speed, bugs...) and most importante, the camera. And if you can use the second lens as telephoto like in 6x.
tks again.
Abdoubody said:
Could we talk on Telegram and Guide me !
Click to expand...
Click to collapse
I dont have time today, sorry buddy. However i did a small video-based guide explaining all important steps and why to use older MIUI 9 Version first instead of MIUI 10.
This is because of Anti-Rollback. Read up everything about it here: https://www.xda-developers.com/xiaomi-anti-rollback-protection-brick-phone/
Download The Stock A2 Rom here: https://en.miui.com/download-353.html
And the Xiaomi 6X MIUI 9 Chinese Developer FASTBOOT Rom here : http://en.miui.com/thread-2620250-1-1.html
(Use the exact same version, its from may without Anti-Rollback, use that ROM and read up about how to avoid and disable anti-rollback)
The short video guide is here, a full detailed step by step guide will be up by tomorrow or friday CET.
Dont forget you can always go back to Stock Rom if you can boot into fastboot and flash the Jessie fastboot Rom, just not if you get trapped by Anti-Rollback and are stuck in EDL with having to use MiFlash Tool
Thank you guys
Why do you wanted to go back to MIUI 9, maeby now that 10 stable is out some thing will be better, maeby i will give it a try
Marwok said:
Why do you wanted to go back to MIUI 9, maeby now that 10 stable is out some thing will be better, maeby i will give it a try
Click to expand...
Click to collapse
I wanted to compare Features of Roms, Quality of Camera, aswell do a comparison of battery life. Didn't know about Anti-Rollback back then
But yeah if you convert keep in mind to go to MIUI 9 first, disable Anti-Rollback and then you are good to go and can update to MIUI 10 without any problem.
windforce3425 said:
I wanted to compare Features of Roms, Quality of Camera, aswell do a comparison of battery life. Didn't know about Anti-Rollback back then
But yeah if you convert keep in mind to go to MIUI 9 first, disable Anti-Rollback and then you are good to go and can update to MIUI 10 without any problem.
Click to expand...
Click to collapse
it's mean if i installed MIUI 9 im safe and will not trap by Anti-Rollback ?!
Abdoubody said:
it's mean if i installed MIUI 9 im safe and will not trap by Anti-Rollback ?!
Click to expand...
Click to collapse
yep MIUI 9 does not have Anti-Rollback yet. You can however follow the many guides for Xiaomi Devices like the Mi 8 covering all questions about Anti-Rollback, how to avoid and remove it from a ROM.
convert to MI 6X MIUI 9 -> Grab MIUI 10 ROM (stable or developer) and disable Anti-Rollback of the ROM -> Flash MIUI 10 without Anti-Rollback through TWRP
Keep in mind you will have to remove the Anti-Rollback feature from every Update and you should NEVER use OTA or you will trigger Anti-Rollback
windforce3425 said:
yep MIUI 9 does not have Anti-Rollback yet. You can however follow the many guides for Xiaomi Devices like the Mi 8 covering all questions about Anti-Rollback, how to avoid and remove it from a ROM.
convert to MI 6X MIUI 9 -> Grab MIUI 10 ROM (stable or developer) and disable Anti-Rollback of the ROM -> Flash MIUI 10 without Anti-Rollback through TWRP
Keep in mind you will have to remove the Anti-Rollback feature from every Update and you should NEVER use OTA or you will trigger Anti-Rollback
Click to expand...
Click to collapse
is going to Fastboot on MIUI 9 like A2 normally ?!
windforce3425 said:
So when I first received this Device i was using Stock Rom for quite a while but then was tempted to convert it to the Mi 6X (which is basically the same device but with MIUI)
Did the Flash Process in fastboot and sucessfully converted it to a Mi 6X. (you will have to swap some files tough)
But here come the problems: As you may know they implemented that complete bs Anti-Rollback Feature in newer MIUI Roms. So I was on the newest MIUI 10 Developer Rom and wanted to go
back to the latest 9 Stable. Flashed the Rom and: boom. device bricked. Since your device is no longer a A2 ( no more A/B partition layout ) you face the same problem as a 6X User.
You simply CANNOT flash the device no matter if you are in EDL our use the test points.
So there is NO way to restore the converted phone back to Stock unless you have access to a developer account.
At this point i can only WARN people. You absolutely CAN USE MIUI also without bricking your device, but there is NO WAY TO GET BACK IF YOU END UP BRICKED SOMEHOW.
Click to expand...
Click to collapse
I believe you can flash the actual bootloader (not boot.img) via fastboot. Specifically the abl.elf and the uefi.elf. this is where the device ID is stored (kinda) and also the partition formatting. So it will switch back to AB system.
You can also try to disable disable antirollback and device verification on the miflash image by editing the flash_all.bat. remove the following lines.
Code:
fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *jasmine" || echo Missmatching image and device
fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *jasmine" || exit /B 1
set CURRENT_ANTI_VER=2
for /f "tokens=2 delims=: " %%i in ('fastboot %* getvar anti 2^>^&1 ^| findstr /r /c:"anti:"') do (set version=%%i)
if [%version%] EQU [] set version=0
if %version% GTR %CURRENT_ANTI_VER% (
echo current device antirollback version is greater than this package
exit /B 1
)
this bypasses the version check and the antirollback mechanism for miflash, which means you will convert your 6x back into an a2 (via edl mode). This will not let your phone boot back into MIUI version 9 though. You can also check the antirollback version in fastboot after restoring to see if it changed the antirollback version. Our phones have the unique ability to be two phones. one with antirollback and one without. I actually did the same thing you did about 2 days ago. this was how I solved it.
Best of luck to you!
windforce3425 said:
So when I first received this Device i was using Stock Rom for quite a while but then was tempted to convert it to the Mi 6X (which is basically the same device but with MIUI)
Did the Flash Process in fastboot and sucessfully converted it to a Mi 6X. (you will have to swap some files tough)
But here come the problems: As you may know they implemented that complete bs Anti-Rollback Feature in newer MIUI Roms. So I was on the newest MIUI 10 Developer Rom and wanted to go
back to the latest 9 Stable. Flashed the Rom and: boom. device bricked. Since your device is no longer a A2 ( no more A/B partition layout ) you face the same problem as a 6X User.
You simply CANNOT flash the device no matter if you are in EDL our use the test points.
So there is NO way to restore the converted phone back to Stock unless you have access to a developer account.
At this point i can only WARN people. You absolutely CAN USE MIUI also without bricking your device, but there is NO WAY TO GET BACK IF YOU END UP BRICKED SOMEHOW.
Click to expand...
Click to collapse
after you did this conversion process, the device became only participation A? other thing how much memory was available to the user (internal)?
Thank you very much for sharing your experience and for the warning! I'll be doing this soon just to see what miui is like. Hope you sort out your device.
Daha3ker said:
I believe you can flash the actual bootloader (not boot.img) via fastboot. Specifically the abl.elf and the uefi.elf. this is where the device ID is stored (kinda) and also the partition formatting. So it will switch back to AB system.
You can also try to disable disable antirollback and device verification on the miflash image by editing the flash_all.bat. remove the following lines.
Code:
fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *jasmine" || echo Missmatching image and device
fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *jasmine" || exit /B 1
set CURRENT_ANTI_VER=2
for /f "tokens=2 delims=: " %%i in ('fastboot %* getvar anti 2^>^&1 ^| findstr /r /c:"anti:"') do (set version=%%i)
if [%version%] EQU [] set version=0
if %version% GTR %CURRENT_ANTI_VER% (
echo current device antirollback version is greater than this package
exit /B 1
)
this bypasses the version check and the antirollback mechanism for miflash, which means you will convert your 6x back into an a2 (via edl mode). This will not let your phone boot back into MIUI version 9 though. You can also check the antirollback version in fastboot after restoring to see if it changed the antirollback version. Our phones have the unique ability to be two phones. one with antirollback and one without. I actually did the same thing you did about 2 days ago. this was how I solved it.
Best of luck to you!
Click to expand...
Click to collapse
You should definetly write a detailed guide for other useres here, I looked up that piece of code and by checking logs of MiFlash I now fully understand whats happening in the flashing process.
Anyway, my device is up and running latest MIUI 10 without ARB 4, been switching between A/B and A partition layout few times now. Only had to send it once to a certified Xiaomi Reseller since I dont own an authorized Developer Account required for MiFlash when I got trapped by ARB.
windforce3425 said:
So when I first received this Device i was using Stock Rom for quite a while but then was tempted to convert it to the Mi 6X (which is basically the same device but with MIUI)
Did the Flash Process in fastboot and sucessfully converted it to a Mi 6X. (you will have to swap some files tough)
But here come the problems: As you may know they implemented that complete bs Anti-Rollback Feature in newer MIUI Roms. So I was on the newest MIUI 10 Developer Rom and wanted to go
back to the latest 9 Stable. Flashed the Rom and: boom. device bricked. Since your device is no longer a A2 ( no more A/B partition layout ) you face the same problem as a 6X User.
You simply CANNOT flash the device no matter if you are in EDL our use the test points.
So there is NO way to restore the converted phone back to Stock unless you have access to a developer account.
At this point i can only WARN people. You absolutely CAN USE MIUI also without bricking your device, but there is NO WAY TO GET BACK IF YOU END UP BRICKED SOMEHOW.
Click to expand...
Click to collapse
HOW DID YOU GET BACK TO A2 or how r u using your device now?
Syed Shahriar said:
HOW DID YOU GET BACK TO A2 or how r u using your device now?
Click to expand...
Click to collapse
When I bricked due to Anti-Rollback I sent my device to Xiaomi, they restored it to stock Rom. After that I again flashed A only parition with MIUI, also went back to Stock as mentioned few posts before.
Related
Warning:all the following attempts should be made by you only .and you know what you are going to do.
Description:-
Its really got tough to officially unlock redmi note 3 pro for us .many of us lose their hopes .but now get ready to unlock your beast in seconds officially on any rom.either global stable or global dev rom.
Here is the procedures :
1.make sure you are on the latest global or china rom
2.make sure you have same account logged on both parties.
3.make sure you can find your phone on i.mi.com
4.now try unlocking ,if you succeed then its good otherwise go ahead
5.boot in fastboot mode,and connect to pc
6.open device manager and search for android phone at top.now in sub menu
what is that
if it is "android bootloader interface" ,actually provided latest on native on windows 10 .uninstall it and install from universal clockworkmod adb driver now try again .if succeded then good .otherwise go ahead
6.if not then search for xiaomi 1.3 driver on google.and install it
7.now you must succeed
TIPS
1. keep trying for at least a week daily (if you are new to face this )
2.looking like xiaomi do it in batch rather than trying of daily
3.also ,one thing i would like to include that .i had reapplied for unlocking from different account mentioning the 50% error with same phone number but different mi account account number and got permission message today for other mi account but remained stuck with old one.and finally unlocked today.
special thanks to @zmajdk
xda team
miui team[emoji3] [emoji3] [emoji3] [emoji3]
Sent from my Redmi Note 3 using Tapatalk
In starting
now get ready to unlock your beast in seconds officially on any rom.
Click to expand...
Click to collapse
In the end
1. keep trying for at least a week daily
Click to expand...
Click to collapse
I have never been able to figure out this signature thing
Tyaginator said:
In starting
In the end
I have never been able to figure out this signature thing
Click to expand...
Click to collapse
sorry for that,but this is only for who fed up with trying and trying ,thanks for your response ,i am new at here
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/
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.
Hey guys, since I just can't seem to find it myself, I'll ask here.
Im currently owning an IN2020 model, which, for the life of me I can't get back up running after rooting it (worked for around 5h, then I got stuck in a bootloop)
Right now, I'm stuck in fastboot/qualcomm crash dump mode, can't progress any further.
When trying to flash any of the International, Indian or Europe Versions of OOS (I tried several different versions, A10 and A11 alike) either I have some modules not working, i.e. WIFI won't turn on, Phone can't register my SIM so I can't make calls etc etc or it just goes straight to qualcomm crash dump mode.
Bootloader is unlocked.
fastboot oem edl nets me a "FAILED (remote: unknown command)", and I tried the "vol+/vol-" trick for over an hour now to no avail, so I cant use MSMTool either.
Can someone please provide me with a link to a working stock ROM for the IN2020 model I can flash via fastboot?
Or maybe theres a solution I just can't see right now, I'm not that great with Android tbh.
Any help is much appreciated, if you need any info/dumps, please also tell me how to get them.
Here are Fastboot roms.
[ROM][STOCK][FASTBOOT][OP8P] Stock Fastboot ROMs for OnePlus 8 Pro
Moderator Information This project is not under active development, take precautions when you are installing it. Things are changing with the advent of project treble and seamless updates. OnePlus will no longer release ROMs flashable via...
forum.xda-developers.com
And here is the MSM unbrick tool
https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4084953/
Make sure you use the appropriate Rom or version of the Tool your device needs.
Good luck!
FreshlyBaked 420 said:
Here are Fastboot roms.
[ROM][STOCK][FASTBOOT][OP8P] Stock Fastboot ROMs for OnePlus 8 Pro
Moderator Information This project is not under active development, take precautions when you are installing it. Things are changing with the advent of project treble and seamless updates. OnePlus will no longer release ROMs flashable via...
forum.xda-developers.com
And here is the MSM unbrick tool
https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4084953/
Make sure you use the appropriate Rom or version of the Tool your device needs.
Good luck!
Click to expand...
Click to collapse
Thanks for the quick reply, but for the MSM unbrick tool, I can't enter Qualcomm EDL mode, neither via fastboot command nor the vol+/vol- plug-in method.
Am I right in thinking that I need a GLOBAL fastboot rom for the IN2020 model to work properly?
raiseyavoice said:
Thanks for the quick reply, but for the MSM unbrick tool, I can't enter Qualcomm EDL mode, neither via fastboot command nor the vol+/vol- plug-in method.
Am I right in thinking that I need a GLOBAL fastboot rom for the IN2020 model to work properly?
Click to expand...
Click to collapse
Edit:
Seems like having the phone connected via a USB3.0 port was the issue here, I tried a 2.0 and suddenly i can enter EDL. Now running the MSMtool (working fine so far). I'll update as soon as its finished.
Edit 2:
Well, beat me up and call me names, it actually worked, phone is now "set up" again, ill still keep a second alarm on for tonight though, just in case my phone decides to go back to bootloop. All this time all it took was a 2.0-port ...
Thanks anyway, next time I'll be a bit more careful when playing around =)
Progress is good!
hi, I have a bricked IN2020 as you did.
may I know which fastboot rom in the above link you had chosen work for you? As I can see only indian / EU /international build, and cannot find any Chinese hydrogen build for IN2020.
Or it worked fine for you to flash an international into the IN2020? Thanks for advise
so i was trying to flash CherishOS so i followed the instruction and found some problem but i was managed to solve the problem. FYI, the rom gave the link to the custom recovery which is the PixelExperience one, since i'm coming from the stock latest rom so i flashed that. until i done everything and boot to system, and it just keeps returned to the bootloader no matter which option i choose (boot to system & recovery), but luckily the device is still detected in my computer
What i've tried :
- flash recovery (PixelExperience & TWRP)
- Followed this instruction
but none of that is working, one thing i found out while doing the 2nd method is that it shows some errors like "flashing is not allowed for critical partition" and "partition not found".
I have no clue what to do, i've tried whatever solution i could find and none are working. please help, thanks
edit:
I also tried the "fastboot flashing unlock_critical" and tried to reboot into fastbootd but failed and the fastboot shows all command list
I guess you are referencing to CherishOS on xda.
[ROM][13.0]CherishOS-4.2[UNOFFICIAL][Oneplus 8 Pro]
CherishOS is an AOSP based rom focusing on Unique and Smooth UI with handy features. CherishOS is a reborn of pie based Dot-ExtendedOS. * Your warranty is now void. * I am not responsible for anything that may happen to your phone by installing...
forum.xda-developers.com
If i click on the link to download the recovery there is nothing about pixelexperience. So i guess you saw something about pixelexperience in the recovery itself. Thats not a problem anyway. You could use lineage recovery too. As long as the recovery is made for a12 thats not a problem as far as i know.
Its not written in the Cherish OS thread but in all other roms you have to be on the latest OOS11 on BOTH slots. Did you do this beforehand?
The easiest thing now is to use MSM Tool and go back to a locked oos phone.
[OP8PRO][OOS 11AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
If you like to install a custom rom again, make sure to update both slots before.
Install LineageOS on instantnoodlep | LineageOS Wiki
wiki.lineageos.org
I tried many custom roms or all i think. And tbh the best experience i had for now was OOS11 and the Open Beta 1 OOS12.
OxygenOS 12 [OB1] [Oneplus 8 Pro] - First Open Beta of Global OOS12
*Will update thread as rn im at work* The first Open Beta for Global OOS has been release really quietly (no announcemment so far) but here is the link from where i download it...
forum.xda-developers.com
Good luck.
xtcislove said:
I guess you are referencing to CherishOS on xda.
[ROM][13.0]CherishOS-4.2[UNOFFICIAL][Oneplus 8 Pro]
CherishOS is an AOSP based rom focusing on Unique and Smooth UI with handy features. CherishOS is a reborn of pie based Dot-ExtendedOS. * Your warranty is now void. * I am not responsible for anything that may happen to your phone by installing...
forum.xda-developers.com
If i click on the link to download the recovery there is nothing about pixelexperience. So i guess you saw something about pixelexperience in the recovery itself. Thats not a problem anyway. You could use lineage recovery too. As long as the recovery is made for a12 thats not a problem as far as i know.
Its not written in the Cherish OS thread but in all other roms you have to be on the latest OOS11 on BOTH slots. Did you do this beforehand?
The easiest thing now is to use MSM Tool and go back to a locked oos phone.
[OP8PRO][OOS 11AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
If you like to install a custom rom again, make sure to update both slots before.
Install LineageOS on instantnoodlep | LineageOS Wiki
wiki.lineageos.org
I tried many custom roms or all i think. And tbh the best experience i had for now was OOS11 and the Open Beta 1 OOS12.
OxygenOS 12 [OB1] [Oneplus 8 Pro] - First Open Beta of Global OOS12
*Will update thread as rn im at work* The first Open Beta for Global OOS has been release really quietly (no announcemment so far) but here is the link from where i download it...
forum.xda-developers.com
Good luck.
Click to expand...
Click to collapse
yoo it works, thanks a lot man. hope you know how relieved i am
yeah i know it's not the problem, but it was the first time i know this recovery in like few years of modding my phone
also i finnaly able to flash the the custom rom, thanks!
I totally agree tho, the oos for me is the best stock rom, i tried the beta 1 tho, but it just leans towards to the color os since oppo is the parent company of oneplus. it just feels more heavy and too many change from the stock android. that's why i decided to flash custom rom
again, thank you so much! have a great day!
B1nz said:
yoo it works, thanks a lot man. hope you know how relieved i am
yeah i know it's not the problem, but it was the first time i know this recovery in like few years of modding my phone
also i finnaly able to flash the the custom rom, thanks!
I totally agree tho, the oos for me is the best stock rom, i tried the beta 1 tho, but it just leans towards to the color os since oppo is the parent company of oneplus. it just feels more heavy and too many change from the stock android. that's why i decided to flash custom rom
again, thank you so much! have a great day!
Click to expand...
Click to collapse
hi.... what exactly have you done to bring it back ??? I'm in the same situation, just fastboot.... thanks
flo musti said:
hi.... what exactly have you done to bring it back ??? I'm in the same situation, just fastboot.... thanks
Click to expand...
Click to collapse
i just used the unbrick tool from the link above, and my phone is back to complete normal. hope it also works for you!
B1nz said:
i just used the unbrick tool from the link above, and my phone is back to complete normal. hope it also works for you!
Click to expand...
Click to collapse
already tried but the phone is not going in Qualcomm EDL mode...
flo musti said:
already tried but the phone is not going in Qualcomm EDL mode...
Click to expand...
Click to collapse
in my experience, my phone is just showing nothing it's like the screen is off. i realized that my phone is in EDL mode is it's detected in my computer as qualcomm something.., when it shows like that that means you haven't installed the qualcomm driver. after that the name will change to "more normal" name. and then you can proceed into the tools