Related
Hello everyone.
I live in Brazil and I bought at the Aliexpress MI4C Xiaomi. I haven't received it yet, but I've already started researching ways to use it with another ROM than the original. The seller sends the device with google apps and multilanguage option. So, he makes some modification in the ROM, and says to not update the ROM officially on Xiaomi servers.
I see a lot of complaints about the Chinese bloatwares in ROM and so I wanted to install one that was good, but nothing with applications in Chinese or unnecessary ones.
My question is: in this case the bootloader is already unlocked?
In the meantime, I sent my request for unlocking bootloader to Xiaomi and received the SMS containing a link. As soon as I get the cellphone I intend to do the procedure. There is a risk of bricking the phone?
I’ll do appreciate good links with how-to and good ROM to daily use.
Thank you.
The seller shipping a modified ROM and telling you not to update the official would suggest your bootloader will not be locked. For now only flashing the latest official China dev builds will lock your bootloader.
Getting pre-approved for unlocking couldn't hurt though I guess.. just in case. You might need to have a working Xiaomi framework in your ROM to register your phone once though. If your ROM does not have the xiaomi services, I would suggest either Xiaomi.eu or sMiUI as a ROM, both are pretty much stock MIUI with some chinese bloat trimmed.
But most likely you will not need to unlock your bootloader anyway. You will need to check your bootloader through adb anyway before doing the steps to flashing a new ROM. You will best be flashing your recovery through adb, the instructions can be found through most ROM pages or simply searching TWRP Mi 4C. The command to check if it's unlocked is
Code:
fastboot oem device-info
A very extensive directory can be found in the INDEX thread, first in this forum.
Logic_ said:
The seller shipping a modified ROM and telling you not to update the official would suggest your bootloader will not be locked. For now only flashing the latest official China dev builds will lock your bootloader.
Getting pre-approved for unlocking couldn't hurt though I guess.. just in case. You might need to have a working Xiaomi framework in your ROM to register your phone once though. If your ROM does not have the xiaomi services, I would suggest either Xiaomi.eu or sMiUI as a ROM, both are pretty much stock MIUI with some chinese bloat trimmed.
But most likely you will not need to unlock your bootloader anyway. You will need to check your bootloader through adb anyway before doing the steps to flashing a new ROM. You will best be flashing your recovery through adb, the instructions can be found through most ROM pages or simply searching TWRP Mi 4C. The command to check if it's unlocked is
Code:
fastboot oem device-info
A very extensive directory can be found in the INDEX thread, first in this forum.
Click to expand...
Click to collapse
you cannot check the bootloader locked or not by that way. My phone when checking this, gets the input "bootloader unlocked: false" but I can flash other recovery freely.
in his case, he is using a modified rom, it means his bootloader is not yet unlocked. Right now, if he wants to come back to chinese rom, he should use Mi flash to flash his phone. If he wants other rom like CM13, he should download the latest TWRP and the rom, put the rom into his phone storage. Then try to go to fastboot to flash the recovery, then go to the recovery and flash the rom.
tuanhung303 said:
you cannot check the bootloader locked or not by that way. My phone when checking this, gets the input "bootloader unlocked: false" but I can flash other recovery freely.
in his case, he is using a modified rom, it means his bootloader is not yet unlocked. Right now, if he wants to come back to chinese rom, he should use Mi flash to flash his phone. If he wants other rom like CM13, he should download the latest TWRP and the rom, put the rom into his phone storage. Then try to go to fastboot to flash the recovery, then go to the recovery and flash the rom.
Click to expand...
Click to collapse
Ah, that might be incorrectly reporting indeed. In any case when trying to flash recovery, if you're locked it'll simply fail and won't be harmful.
But why would you think his bootloader is not unlocked? If he's using a modified rom, it was probably flashed through fastboot or a custom recovery, both require the bootloader to be unlocked.
But even if he was not on a modified rom, stock Mi 4c have always come bootloader unlocked. Someone would have to have gone out of their way to lock the bootloader and I doubt any reseller would do that, they would risk a lot of refunds from angry customers.
I strongly advise against using miflash to flash any official rom unless you have no choice, since then there's a chance you WILL lock your bootloader. For now only dev builds are locking it, but the next stable release might very well too.
The first step should be to flash TWRP
The second step to stay away from Official China build
The third step to keep away from Official China build
The fourth st...
^ sorry my bad.... I was not focused. Actually I mean his bootloader is unlocked .
The safest way is flashing via computer, using mi flash or flash twrp image. You are right
1. Ur phone not lock bootloader
2. U can flash custom recovery...(TWRP)
3. "MUST" Stay away from official MIUI ROM
4. Flash whatever u want...sMiui, CM13, etc,etc
5. Remember Point No.3
***Btw, download official Fastboot ROM and keep it to ur drive, for just in case if u want to sell it again
Hello. Thank you all. I just received my phone. Great, btw. I'll read again and again all instructions and try. Thanks again!
Cadimarco said:
Hello. Thank you all. I just received my phone. Great, btw. I'll read again and again all instructions and try. Thanks again!
Click to expand...
Click to collapse
Even as a last resort to getting your phone working if you did something wrong, please don't install the newer official roms, it's the mistake I did this weekend now I have a locked phone with a rom that has force-closes everywhere and absolutely no way back.
vletrmx21 said:
Even as a last resort to getting your phone working if you did something wrong, please don't install the newer official roms, it's the mistake I did this weekend now I have a locked phone with a rom that has force-closes everywhere and absolutely no way back.
Click to expand...
Click to collapse
yes, or the safer way is always flash the latest chinese rom via miflash. twrp does not like Chinese roms
tuanhung303 said:
yes, or the safer way is always flash the latest chinese rom via miflash. twrp does not like Chinese roms
Click to expand...
Click to collapse
No
No No
No No No
No No
No
No.
Don't flash the latest chinese rom.
No.
The only scenario where you would want to use miflash to flash a chinese rom would be as a last resort to flash the fastboot version of V7.1.6.0.LXKCNCK to restore your phone. Any later version will lock your bootloader.
If you don't care about locking your bootloader and the arduous process of unlocking it, you're easier off just taking all the latest updates OTA via the updater.
Hello everyone. Thanks for the help. In fact my bootloader was unlocked. I flashed twrp 3.0.0.3 and flashed the CM13 teamluminial, Android 6.0.1. Excellent. Thank you.
Hi!
Same scenario here..
I will receive Mi 4c with the Bootloader Unlocked, Rooted and the Multilanguage ROM.
But I have already received from Xiaomi after my request also the number for the official unlock procedure but now I'm a bit confused..
Do I have to unlock the bootloader once and for good with the official way?
Because I've read that the unofficial way isn't so secure in long term.
Do I have to install from the Updater the latest Cina Dev ROM and after that to proceed with the official unlock? Or it is better to use the Fastboot ROM?
Please could some one tell me in any case what to do ?
Thanks !
If you don't flash something that will lock your BL, no need to Unlock.
Ok first I must check the status of the bootloader to be sure that it is unlocked (via cmd control or cpu-z)
And after that can I choose an unofficial weekly miui.eu international ROM and install it?
Can I download and also update every week via Updater this ROM without issues?
At the moment my problem with flashing is that I don't have my pc (the one I have now runs win xp) and I don't want to stuck with the eventually malware or fully spammed modified rom of the reseller..
Which options do I have?
How does TWRP nandroid work with no sd card?
stillsober said:
How does TWRP nandroid work with no sd card?
Click to expand...
Click to collapse
TWRP works perfectly. The backup is simply stored in your internal storage。
Hi, I just found a thread on MIUI forum which inspire me
http://en.miui.com/thread-3450268-1-1.html
Kudos to the OP in that thread
I tried the tutorial to one of my friend's Note 5, the tutorial works, so now we know that DOWNGRADING FROM 8.82 GLOBAL TO 8.7.26 GLOBAL IS POSSIBLE
Now I need someone with bricked devices because of downgrading to try it, you must download fastboot room first and sideload it to your redmi note 5
Here is the summary and the short version of the already short tutorial (lol), also some fixes needed, for those stuck in "MIUI CANT BE INSTALLED ON THIS DEVICE" error AND NEED AUTHORIZATION CODE TO FLASH
ALSO FOR THOSE IN ANTI 4 WITH FAKE UBL (MAINLY DEVICES SOLD IN INDONESIA), WHO WANT TO FLASH CHINA ROM AND BIND THE MI ACCOUNT TO THE DEVICE TO LATER REQUESTING UNLOCK TO XIAOMI
FOR THOSE WHOSE DEVICES ARE BRICKED BECAUSE OF DOWNGRADING, YOU CAN TRY TO DOWNLOAD THE FASTBOOT ROM AND FLASH IT WITH THE SAME STEP, NEVER TESTED IT WITH EDL MODE, SO ANYONE?
1. Xiaomi Tool
2. XiaomiTool ADB
3. MI FLASH PRO
4. ROM GLOBAL 9.5.19
5. ROM GLOBAL 8.7.26
6. ROM GLOBAL 8.8.2
7. ROM CHINA 8.7.26
8. DRIVER2 QUALCOM, ADB DLL YG BISA DICARI DI POST LAIN
THE STEPS :
1. FLASH YOUR NOTE 5 TO 8.8.2 GLOBAL ROM USING MI FLASH PRO
2. OPEN CMD AND SIDE LOAD USING XIAOMITOOL ADB, COMMAND IS xiaomiadb sideload_miui<spasi>namafile.zip. WHICH IS miui_HMNote5HMNote5ProGlobal_8.7.26_d7fb438aef_8.1.zip. YOUR DEVICE WILL BE DOWNGRADED TO 8.7.2.6 GLOBAL ROM
3. NOW FLASH YOUR PHONE USING ANY TOOL LIKE XIAOMITOOL TO 8.7.2.6 CHINA
4. VOILA, IT WORKS NOW
don't know when Xiaomi will close this bug hole, so try it while you can
Tried to downgrade from 8.82 Global Rom to 8.726 Rom Global, later flashed the China 8.726 rom and it worked
It means we still can downgrade, I think this is a bug in xiaomi server, can anyone use this bug for our advantage?
Thanks
codearm2 said:
FOR THOSE WHOSE DEVICES ARE BRICKED BECAUSE OF DOWNGRADING, YOU CAN TRY TO DOWNLOAD THE FASTBOOT ROM AND FLASH IT WITH THE SAME STEP, NEVER TESTED IT WITH EDL MODE, SO ANYONE?
Click to expand...
Click to collapse
1. if your device was on china rom from the very begining. you flashed global rom over china rom without unlocking BL, and phone got bricked (This MIUI version can not be installed on this device)
Click to expand...
Click to collapse
There should have been note posted about that guide: -
NOT FOR DEVICES HARD BRICKED BY DOWNGRADING ON ARP!
You still need access to recovery/fastboot for that tutorial to work.
Could anybody share how can I move from MiUI EU ROM for K30 11.0.15.0 to Poco X2 official build 11.0.7.0?
I installed EU ROM as I found flashing ROM with TWRP was easier than using Mi Flash tool, in case we want to switch between ROM's. But, after I installed 11.0.15.0 I figured lot of the custom ROM's do not boot after flashing them and phone boots into fastboot mode (except couple of ROM's). So, I have been looking at how switch back EU MiUI ROM from 11.0.15.0 to Poco X2 11.0.7.0. The issue am facing while flashing using Mi Flash tool is that it gives error of ARB (Anti rollback error: 2, also I checked the same by issuing fastboot getvar anti, it says 2), and I am not sure how to get past this.
Could someone please help me with this?
I think your device is triggered with anti-rollback. So you cannot install any rom with build less than 11.0.15.0 that is poco x2 11.0.7.0 cant be flashed. So, you have to wait until new poco build greater than 11.0.15.0 and then flash it. Until then, flash your existing rom or some custom rom. Do it carefully and dont ever flash older roms from now, if something goes wrong, your device will hardbrick and you will have to go to service center where they have authorized EDL access to your device to flash things. Best of Luck.
You can use full recovery rom zip 11.0.7 and flash it via twrp. In 11.0.7 zip make sure you change the devicename in script from phoenixin to phoenix as twrp is pheonix.
After flashing you will be on stock 11.0.7 and stock recovery.
If you want to try custom roms , you can just flash the stock vedor zip of 11.0.07 and then flash any aosp custom rom.(you can find this zip in telegram channel/github)
eagle06 said:
You can use full recovery rom zip 11.0.7 and flash it via twrp. In 11.0.7 zip make sure you change the devicename in script from phoenixin to phoenix as twrp is pheonix.
After flashing you will be on stock 11.0.7 and stock recovery.
If you want to try custom roms , you can just flash the stock vedor zip of 11.0.07 and then flash any aosp custom rom.(you can find this zip in telegram channel/github)
Click to expand...
Click to collapse
Bro, but what about anti-rollback hardbrick?.. new miui wont allow downgrade right? he has very newer build than 11.0.7.
eagle06 said:
You can use full recovery rom zip 11.0.7 and flash it via twrp. In 11.0.7 zip make sure you change the devicename in script from phoenixin to phoenix as twrp is pheonix.
After flashing you will be on stock 11.0.7 and stock recovery.
If you want to try custom roms , you can just flash the stock vedor zip of 11.0.07 and then flash any aosp custom rom.(you can find this zip in telegram channel/github)
Click to expand...
Click to collapse
vivek12341 said:
Bro, but what about anti-rollback hardbrick?.. new miui wont allow downgrade right? he has very newer build than 11.0.7.
Click to expand...
Click to collapse
@eagle06 am worried about 11.0.15.0 > 11.0.7.0 which will trigger ARB as @vivek12341 has pointed out and it will hard brick the device, from what I have read around, hence this post if anybody knows a way out. There seemed to be workarounds initially when Xiaomi introduced ARB, I have not seen anybody mentioning such things in recent times especially for MiUI 11.
The reason why I moved to 11.0.15.0 is was, as it has no bloatware etc, and I did NOT know about ARB, now that I have 11.0.15.0 most of the custom ROMs are based on Poco X2 11.0.7.0 and I am facing issues flashing ROMs based on 11.0.7.0, as the format data from TWRP does not wipe properly + I see 98% of the time device goes to fastboot mode even if I flash Poco stock recovery and clear the data, seems like 11.0.15.0 is also an issue
May be I will have to wait till Poco releases updates > 11.0.15.0 or for MiUI 12. Actually I still dont know, not many know much on this subject.
crDroid works without any issues (which is what my current daily driver, its a very stable ROM), flashing on 11.0.15.0 after clearing data, also any ROM whose dev releases fastboot ROM's those also I can flash and boot without issues, rest all ROM's dont and end up back in fastboot mode
coolcorner said:
Could anybody share how can I move from MiUI EU ROM for K30 11.0.15.0 to Poco X2 official build 11.0.7.0?
I installed EU ROM as I found flashing ROM with TWRP was easier than using Mi Flash tool, in case we want to switch between ROM's. But, after I installed 11.0.15.0 I figured lot of the custom ROM's do not boot after flashing them and phone boots into fastboot mode (except couple of ROM's). So, I have been looking at how switch back EU MiUI ROM from 11.0.15.0 to Poco X2 11.0.7.0. The issue am facing while flashing using Mi Flash tool is that it gives error of ARB (Anti rollback error: 2, also I checked the same by issuing fastboot getvar anti, it says 2), and I am not sure how to get past this.
Could someone please help me with this?
Click to expand...
Click to collapse
You should flash back to China rom (V11.0.15.0.QGHCNXM) using miflash and install TWRP-3.4.1B-0322 using fastboot. After that you can flash all custom roms as normal. I have tried almost all the custom roms and they all work without any problem.
Lol.. Bro i am on miui 12 beta and went back to 11.0.0.7 via twrp flash...
Just download this http://bigota.d.miui.com/V11.0.7.0....NGlobal_V11.0.7.0.QGHINXM_9c232b802a_10.0.zip
Open that in pc, modify the script and rename device name to phoenix from phoenixin.
On twrp format data.. Then reboot to twrp again, tranfer that zip file and just flash. You will be back on stock global 11.0.0.7
Also crdroid as you mentioned has custom vendor which is different from china eu or global one.
If you want to use fastboot zip then you need to use https://www.xiaomitool.com/V2/ to overcome antirollback error.
eagle06 said:
Lol.. Bro i am on miui 12 beta and went back to 11.0.0.7 via twrp flash...
Just download this http://bigota.d.miui.com/V11.0.7.0....NGlobal_V11.0.7.0.QGHINXM_9c232b802a_10.0.zip
Open that in pc, modify the script and rename device name to phoenix from phonenixin.
On twrp format data.. Then reboot to twrp again, tranfer that zip file and just flash. You will be back on stock global 11.0.0.7
Also crdroid as you mentioned has custom vendor which is different from china eu or global one. e
If you want to use fastboot zip then you need to use https://www.xiaomitool.com/V2/ to overcome antirollback error.
Click to expand...
Click to collapse
1. Which script are you talking about? I could not find any script. check attached snapshot.
2. And to do this step from TWRP to flash 11.0.7.0, do I need to be on MIUI EU ROM or I can flash from any custom ROM too?
3. You were on MIUI 12 beta (official global) and changed devicename from phoenixin to phoenix and flashed using TWRP after formatting data, without hitting ARB issue? Wow!
4. You mentioned https://forum.xda-developers.com/showpost.php?p=82502389&postcount=3 Telegram/Github where we can get official vendor zip which we can flash from TWRP, any links to that?
5. Is there a Redmi K30 global ROM which I can use instead of Poco X2, they should be same right?
eagle06 said:
You can use full recovery rom zip 11.0.7 and flash it via twrp. In 11.0.7 zip make sure you change the devicename in script from phoenixin to phoenix as twrp is pheonix.
After flashing you will be on stock 11.0.7 and stock recovery.
If you want to try custom roms , you can just flash the stock vedor zip of 11.0.07 and then flash any aosp custom rom.(you can find this zip in telegram channel/github)
Click to expand...
Click to collapse
Please share telegram or github link for vendor.zip which I can flash using TWRP. As crDroid has custom vendor may be that is why it works for me on EU ROM and I see other custom ROMs do not have vendor installed while flashing using TWRP.
jngiag said:
You should flash back to China rom (V11.0.15.0.QGHCNXM) using miflash and install TWRP-3.4.1B-0322 using fastboot. After that you can flash all custom roms as normal. I have tried almost all the custom roms and they all work without any problem.
Click to expand...
Click to collapse
As a final resort will go to China ROM V11.0.15.0.QGHCNXM (this will be chinese right?) or this itself is global K30 ROM? Any links to global official MIUI K30 ROM, all I get is K30 chinese ROM
Sorry, I am asking too many questions, I do not want to brick phone in these times and go stand in queue at Mi service center during these times, when the servicing engineer will touch my phone all over
coolcorner said:
1. Which script are you talking about? I could not find any script. check attached snapshot.
Its in META-INF/com/google/android/ file name updater-script. Change getprop("ro.product.device") == "phoenixin" || this to getprop("ro.product.device") == "phoenix" || . Why we are doing this? because we are using k30 twrp.. there is no special twrp for poco x2. phoenix = k30, phoenixin=poco x2
2. And to do this step from TWRP to flash 11.0.7.0, do I need to be on MIUI EU ROM or I can flash from any custom ROM too? Any rom
3. You were on MIUI 12 beta (official global) and changed devicename from phoenixin to phoenix and flashed using TWRP after formatting data, without hitting ARB issue? Wow! Yes with twrp. When you flashed twrp recovery , your device is now treated as K30 in twrp space
4. You mentioned https://forum.xda-developers.com/showpost.php?p=82502389&postcount=3 Telegram/Github where we can get official vendor zip which we can flash from TWRP, any links to that?check Pm , cant post telegram links here
5. Is there a Redmi K30 global ROM which I can use instead of Poco X2, they should be same right?Theres no K30 global.., poco x2 rom is global, k30 roms is china and there is eu custom rom based on chinese roms
Please share telegram or github link for vendor.zip which I can flash using TWRP. As crDroid has custom vendor may be that is why it works for me on EU ROM and I see other custom ROMs do not have vendor installed while flashing using TWRP.
Whenever you want to use custom rom without vendor , you need to flash either 11.0.0.7 zip or 11.0.0.7 vendor zip before flashing that custom rom
As a final resort will go to China ROM V11.0.15.0.QGHCNXM (this will be chinese right?) or this itself is global K30 ROM? Any links to global official MIUI K30 ROM, all I get is K30 chinese ROM
Sorry, I am asking too many questions, I do not want to brick phone in these times and go stand in queue at Mi service center during these times, when the servicing engineer will touch my phone all over
Click to expand...
Click to collapse
Check my replies in blue
coolcorner said:
As a final resort will go to China ROM V11.0.15.0.QGHCNXM (this will be chinese right?) or this itself is global K30 ROM? Any links to global official MIUI K30 ROM, all I get is K30 chinese ROM
Sorry, I am asking too many questions, I do not want to brick phone in these times and go stand in queue at Mi service center during these times, when the servicing engineer will touch my phone all over
Click to expand...
Click to collapse
It is a chinese rom. You can select english as your default language. It really doesn't matter as you are going to wipe it anyway if your purpose is to use it for flashing custom roms.
[Deleted]
coolcorner said:
Just now I tried flashing V11.0.15.0.QGHCNXM using Mi Flash tool, and I hit Anti Roll back error again. Not sure what I am missing here I am on same version 11.0.15.0 EU ROM which has same Anti 2, not sure why the error this time?
Click to expand...
Click to collapse
Bro If you want to use fastboot zip then you need to use https://www.xiaomitool.com/V2/ to overcome antirollback error. Connect device and enable usb debugging and proceed.
Mi flash tool doesnt work for poco.....you always get that rollback error.
For fastboot zips use above tool.
For recovery zips use twrp.
Both methods flash the same thing and twrp will be replaced with stock recovery.
---------- Post added at 08:36 AM ---------- Previous post was at 08:20 AM ----------
Vendor only zip.
[ fw_vendor_phoenixin_miui_PHOENIXININGlobal_V11_0_7_0_QGHINXM_9c232b802a.zip
Size : 1.12 GiB
Download : fw_vendor_phoenixin_miui_PHOENIXININGlobal_V11_0_7_0_QGHINXM_9c232b802a.zip
https://drive.google.com/uc?id=1-mIvf3EhtZwLl_rg1cFgZIp5Zz4QlQZu&export=download
Flash via twrp. If you get error 7/wrong device check updater script and change name
eagle06 said:
Bro If you want to use fastboot zip then you need to use https://www.xiaomitool.com/V2/ to overcome antirollback error. Connect device and enable usb debugging and proceed.
Mi flash tool doesnt work for poco.....you always get that rollback error.
For fastboot zips use above tool.
For recovery zips use twrp.
Both methods flash the same thing and twrp will be replaced with stock recovery.
Click to expand...
Click to collapse
Thanks, really appreciate your quick revert. I am trying out with xiaomitool now. I know TWRP method is simple, just edit/change the devicename. But, I am **** scared after seeing ARB error so many times. So using xiaomitool as you mentioned use it to overcome ARB error. I will update how it goes.
I thought Xiaomi is dev/custom dev friendly, seeing all these errors, no wonder why people resent MiUI so much, of course the hardware + price is good. From my search even Google on their devices is not this harsh about ARB blocking after unlocking bootloader.
eagle06 said:
Bro If you want to use fastboot zip then you need to use https://www.xiaomitool.com/V2/ to overcome antirollback error. Connect device and enable usb debugging and proceed.
Mi flash tool doesnt work for poco.....you always get that rollback error.
For fastboot zips use above tool.
For recovery zips use twrp.
Both methods flash the same thing and twrp will be replaced with stock recovery.
---------- Post added at 08:36 AM ---------- Previous post was at 08:20 AM ----------
Vendor only zip.
[ fw_vendor_phoenixin_miui_PHOENIXININGlobal_V11_0_7_0_QGHINXM_9c232b802a.zip
Size : 1.12 GiB
Download : fw_vendor_phoenixin_miui_PHOENIXININGlobal_V11_0_7_0_QGHINXM_9c232b802a.zip
https://drive.google.com/uc?id=1-mIvf3EhtZwLl_rg1cFgZIp5Zz4QlQZu&export=download
Flash via twrp. If you get error 7/wrong device check updater script and change name
Click to expand...
Click to collapse
Thanks for the vendor image link.
Oh! yeah I am back in Poco 11.0.7.0 image, xiaomitool worked without issues. Thanks to you!!
@eagle06 do you know in this entire image (attached file) list (from tgz file) which is fastboot file? The reason I ask is, in Poco X2 in fastboot mode I see a single deadpixel, whereas when I was in EU MIUI I never saw that dead pixel. I plan to replace that file with EU MIUI fastboot image file, so when am in fastboot, it is clean without any dead pixels.
That small white pixel in fastboot is normal. All users have it including me.
Pic
eagle06 said:
Pic
Click to expand...
Click to collapse
Yep right that is the one. When I was on EU Miui, that one did not have, hence asked which is the image file for fastboot, thought I would flash that or replace next time I flash Poco stock when I am installing new custom ROM.
Yes, its a trivial thing can be ignored, does not really bother or harm.
BTW, so now that I am back in Poco X2 stock (On top of that I have installed BlissROM), next time I have to flash I can use either TWRP or Xiaomitool/V2.
1. For TWRP, I need to rename devicename to phoenix from phoenixin in updater-script and flash it using TWRP after clearing data
OR
2. I can use Xiaomitool/V2 with ADB debugging on (same step as last time)
Just check fastboot getvar anti for my phone, it also says 2. There is no problem for me flashing china rom with miflash. I have successfully flashed it 4 times before.
Good to have another way of flashing - will try the xiaomitool next time. :good:
jngiag said:
Just check fastboot getvar anti for my phone, it also says 2. There is no problem for me flashing china rom with miflash. I have successfully flashed it 4 times before.
Good to have another way of flashing - will try the xiaomitool next time. :good:
Click to expand...
Click to collapse
Woah! Miflash tool kept throwing errors at me and you are saying it worked for you? Phew!!
If I had flashed using TWRP, I might have been holding a 200gm brick in my hands LOL. Got lucky by using Xiaomitool/v2 then Thanks to you. I will stick to Xiaomitool for flashing stock ROMs hence forth.
Hello again!
I saw a post where leipnacht provides a link to the public beta of Android R. (I let you here a drive link to download it faster).
I flashed it and it's working properly on my device. There is some bugs, but the most part of the things works without problems (Personally, I didn't face any bug itself (only a low noise with the vibration by the moment), but there are some comments in the page of bbs nubia about some problems with other things.
The previous conditions from where I update to Android R Red Magic Rom were using a GSI in the Android 10 chinese version of the rom. So, the steps I followed are:
1. In the recovery, wipe data, cache and dalvik. Also, format data.
2. Flash in the Android 10 TWRP the Android R rom.
3. Flash this NikGapps Package , Magisk Debug and DFE (Encrypt disabler in order to be able decrypt data in the recovery). I also flashed Permissive_5 but I think there is no need to do it.
4. Boot and enjoy.
I will attach all the files and some screenshots for those who want to take a see to the rom. Personally, I feel no changes in this version, but, as always, the performance is great and it runs really smooth. It's a beta version, so I hope more changes in the future.
P.D. In order to get safetynet passing, I used HideProps Config magisk module. There is no big issues with it, and everything is fixable
P.d.2. This rom has antiroll-back active, so if you want to go back to previous version, you will have to use the unbrick tool
Perseo99 said:
Hello again!
I saw a post where leipnacht provides a link to the public beta of Android R. (I let you here a drive link to download it faster).
I flashed it and it's working properly on my device. There is some bugs, but the most part of the things works without problems (Personally, I didn't face any bug itself (only a low noise with the vibration by the moment), but there are some comments in the page of bbs nubia about some problems with other things.
The previous conditions from where I update to Android R Red Magic Rom were using a GSI in the Android 10 chinese version of the rom. So, the steps I followed are:
1. In the recovery, wipe data, cache and dalvik. Also, format data.
2. Flash in the Android 10 TWRP the Android R rom.
3. Flash this NikGapps Package , Magisk Debug and DFE (Encrypt disabler in order to be able decrypt data in the recovery). I also flashed Permissive_5 but I think there is no need to do it.
4. Boot and enjoy.
I will attach all the files and some screenshots for those who want to take a see to the rom. Personally, I feel no changes in this version, but, as always, the performance is great and it runs really smooth. It's a beta version, so I hope more changes in the future.
P.D. In order to get safetynet passing, I used HideProps Config magisk module. There is no big issues with it, and everything is fixable
P.d.2. This rom has antiroll-back active, so if you want to go back to previous version, you will have to use the unbrick tool
Click to expand...
Click to collapse
Thanks for the update.
I have been planning to upgrade my Red Magic 3 to Android 10 (CN rom) for quite a while now. And its good to know A11 beta has arrived too.
Have you tried fps games on this device like pubg mobile, cod etc? Do they work properly ?
Also, I haven't even unlocked bootloader on my device. Can you proivde a better guide, to completely switch from global rom (stock) to A11 (beta) or A10 CN rom (stable).
Need links / guide for following items -
- Unlock bootloader
- Link of working twrp and steps to flash (should I change recovery after installing this beta?)
- Gapps and Magisk link (As I can't run this device without Google services).
It will be a huge help for me to get started.
Take your time with it (no rush).
Thanks in advance!!!
nalin_s3 said:
Thanks for the update.
I have been planning to upgrade my Red Magic 3 to Android 10 (CN rom) for quite a while now. And its good to know A11 beta has arrived too.
Have you tried fps games on this device like pubg mobile, cod etc? Do they work properly ?
Also, I haven't even unlocked bootloader on my device. Can you proivde a better guide, to completely switch from global rom (stock) to A11 (beta) or A10 CN rom (stable).
Need links / guide for following items -
- Unlock bootloader
- Link of working twrp and steps to flash (should I change recovery after installing this beta?)
- Gapps and Magisk link (As I can't run this device without Google services).
It will be a huge help for me to get started.
Take your time with it (no rush).
Thanks in advance!!!
Click to expand...
Click to collapse
Hey!
No problem at all. I let you here two guides to migrate to the cn rom and even a gsi
Be careful and aware about what you are going to do, It's not specially difficult but you have to get ready all the files and tools in case of brick or bootloops.
Enjoy the flashing!
Perseo99 said:
Hey!
No problem at all. I let you here two guides to migrate to the cn rom and even a gsi
Be careful and aware about what you are going to do, It's not specially difficult but you have to get ready all the files and tools in case of brick or bootloops.
Enjoy the flashing!
Click to expand...
Click to collapse
Thanks for the links. I am planning to update to stable A10 version for now.
I have few questions it be a huge help you could clear some of my doubts -
1. After unlocking bootloader I have to install TWRP (for gapps to run). So should I install TWRP after flashing CN rom ? or before ?
I am asking this because I read in some guides that only CN rom is custom recovery capable.
2. If you have run A10 stables before, does OTA updates require to be installed via TWRP only ?
Will I loose Gapps and Root access if I updated the ota directly from settings? And will every rom flash with TWRP clear my installed apps ?
Thanks in advance for helping!!. ??
nalin_s3 said:
Thanks for the links. I am planning to update to stable A10 version for now.
I have few questions it be a huge help you could clear some of my doubts -
1. After unlocking bootloader I have to install TWRP (for gapps to run). So should I install TWRP after flashing CN rom ? or before ?
I am asking this because I read in some guides that only CN rom is custom recovery capable.
2. If you have run A10 stables before, does OTA updates require to be installed via TWRP only ?
Will I loose Gapps and Root access if I updated the ota directly from settings? And will every rom flash with TWRP clear my installed apps ?
Thanks in advance for helping!!. ?
Click to expand...
Click to collapse
Well, I will go in order:
1. You have to flash first in the stock recovery the Android 10 CN rom and then flash the custom recovery. There is no twrp avaible for global rom. Once in the custom recovery, you can flash Gapps and Magisk (in android 10 there is no need of DFE file, the recovery is able to decrypt data properly.
2. You don't need to get worried about OTAs, there is no a constant software update work by nubia for this device, but in case of update, you would flash the rom from the offcial page, with magisk and gapps again and be sure you keep the custom recovery.
Perseo99 said:
Hello again!
I saw a post where leipnacht provides a link to the public beta of Android R. (I let you here a drive link to download it faster).
I flashed it and it's working properly on my device. There is some bugs, but the most part of the things works without problems (Personally, I didn't face any bug itself (only a low noise with the vibration by the moment), but there are some comments in the page of bbs nubia about some problems with other things.
The previous conditions from where I update to Android R Red Magic Rom were using a GSI in the Android 10 chinese version of the rom. So, the steps I followed are:
1. In the recovery, wipe data, cache and dalvik. Also, format data.
2. Flash in the Android 10 TWRP the Android R rom.
3. Flash this NikGapps Package , Magisk Debug and DFE (Encrypt disabler in order to be able decrypt data in the recovery). I also flashed Permissive_5 but I think there is no need to do it.
4. Boot and enjoy.
I will attach all the files and some screenshots for those who want to take a see to the rom. Personally, I feel no changes in this version, but, as always, the performance is great and it runs really smooth. It's a beta version, so I hope more changes in the future.
P.D. In order to get safetynet passing, I used HideProps Config magisk module. There is no big issues with it, and everything is fixable
P.d.2. This rom has antiroll-back active, so if you want to go back to previous version, you will have to use the unbrick tool
Click to expand...
Click to collapse
Can you check your pm??
There's no problem in flashing but take note there's no going back i mean you cant downgrade it anymore using unbric tool even if you flash rom using cmd it will not work my rm3s now is bricked theres no tool or method that can fix it right now. Unless someone make a new unbrick tool
jepoyxxv said:
There's no problem in flashing but take note there's no going back i mean you cant downgrade it anymore using unbric tool even if you flash rom using cmd it will not work my rm3s now is bricked theres no tool or method that can fix it right now. Unless someone make a new unbrick tool
Click to expand...
Click to collapse
I already went to 11 and flash to 3.11
But how did you flash android 10 3.11 in rm3s no matter what tool i use i cant fix my rm3s from being bricked by flashing android 11 beta can you tell me what did you do did you flash it manually in command prompt please help me
jepoyxxv said:
But how did you flash android 10 3.11 in rm3s no matter what tool i use i cant fix my rm3s from being bricked by flashing android 11 beta can you tell me what did you do did you flash it manually in command prompt please help me
Click to expand...
Click to collapse
If you are in 11 beta and want to downgrade..just simple flash global version and again flash 3.11 done
What did you use to flash global rom lastweek i successfully installed android 11 beta and use unbrick tool to go back to global but i got bricked. And i cant fix it anymore.
jepoyxxv said:
What did you use to flash global rom lastweek i successfully installed android 11 beta and use unbrick tool to go back to global but i got bricked. And i cant fix it anymore.
Click to expand...
Click to collapse
I just flash global from otg and tham again 3.11
walkwitmeinhel said:
I just flash global from otg and tham again 3.11
Click to expand...
Click to collapse
Could you please tell me where to download the 3.11 rom. I am not aware that this rom exists. Is this a CN or global rom? Thanks for your reply.
[email protected] said:
Could you please tell me where to download the 3.11 rom. I am not aware that this rom exists. Is this a CN or global rom? Thanks for your reply.
Click to expand...
Click to collapse
http://ui.nubia.cn/rom/detail/64
Oh! Didn't expect that. I just post this for Red Magic 3 device users. I don't know how RM3S actually works. Have you tried the unbrick tool from chinese version? Or just flashing the global rom from recovery is enough?
Wait is there a chinese unbrick tool cn. version for red magic can you provide me a link.. unbrick tool 3/3s.global by jerry is not working anymore if you got brick by android 11 beta rom...
jepoyxxv said:
Wait is there a chinese unbrick tool cn. version for red magic can you provide me a link.. unbrick tool 3/3s.global by jerry is not working anymore if you got brick by android 11 beta rom...
Click to expand...
Click to collapse
Let's see. Here is a link for Red Magic 3S unbrick tool. Download the non-eu ones.
If you have a Red Magic 3 with Red Magic 3s software, I will provide you the link to the other unbrick tool.
Also, you can try flashing the global rom from the stock recovery included in the package of the A11 rom that you have download.
Thanks for replying my bro.. my device is rm3s i already use rm3 and rm3s unbrick tool.. downloading fire hose programmer and image was successfully but.. my phone is still corrupted... And one thingg i dont have twrp install in my rm3s thats why its hard for me to fix it.. can you please guide or teach me how to flash stock recovery using global rom i know how to use cmd and adb
jepoyxxv said:
Wait is there a chinese unbrick tool cn. version for red magic can you provide me a link.. unbrick tool 3/3s.global by jerry is not working anymore if you got brick by android 11 beta rom...
Click to expand...
Click to collapse
So then, It's not a problem of the unbrick tool, that is actually working properly. The thing is that you didn't know how to do a correct process to migrate from cm rom to global...
The first thing you should do is reboot the phone into fastboot mode (power+vol. Down). Then, connect the phone to the PC and type the next commands in the cmd:
Code:
fastboot devices
in order to see if your device is being recognized
Code:
fastboot oem nubia_unlock NUBIA_NX629J
to unlock the bootloader
Code:
fastboot flashing unlock
in order to make your phone able to boot with a modified software. In the moment you will enter this command, you will see a screen advising you about your data (it'll be erased once you accept to unlock flashing).
After that, you can reboot your phone, that will show you an screen advising you that the bootloader is open. Accept and continue without problems.
Tell me if you have been able to make your phone boot.
Perseo99 said:
Well, I will go in order:
1. You have to flash first in the stock recovery the Android 10 CN rom and then flash the custom recovery. There is no twrp avaible for global rom. Once in the custom recovery, you can flash Gapps and Magisk (in android 10 there is no need of DFE file, the recovery is able to decrypt data properly.
2. You don't need to get worried about OTAs, there is no a constant software update work by nubia for this device, but in case of update, you would flash the rom from the offcial page, with magisk and gapps again and be sure you keep the custom recovery.
Click to expand...
Click to collapse
Required in CN A10 + twrp A10, or maybe from CN A9 + twrp A9 to be able to flash
Hello
I read the thread here posted by h8Aramex
How to flash Xiaomi.eu firmware on Xiaomi Mi Note 10 - step-by-step guide
So this guide was written by DeathByArmadillo who partly copied it from user "Danmue" from an old post. Anyway, it works. Tested on Mi Note 10 with Global rom. Just re-posted it in it's own thread because the information was a bit scattered...
forum.xda-developers.com
And I have a few concerns
I asked in the main thread however the thread looks to be dead
If anyone knows a guide on how to do that and if it's a good idea to do so
I want to do that because the Global Rom lacks a lot of the features in the CN/EU Rom
Here are the questions:
1- Does this guide work on the new MIUI 12.5?
2- I'm on 12.5.3 Global and The latest EU is 12.5.1 , is that considered a downgrade that will brick my device? Because I heard people are not having luck with downgrades
3- What is the ROM used? Is it a stock EU that I can download from any xiaomi firmware source? Or is it a custom thing
I mean can I just go to xiaomifirmwareupdater and download the EEA version (It's same as the EU ROM right?)
4-I saw people complaining about non responsive touch, does that happen only in recovery? Or is it in the System?
5- Is it better if I only fastboot the EU rom and then flash the custom Recovery? And if not, what version of the firmware should I download, there's a recovery version and a fastboot version (larger than the recovery one)
6- Let's say I got a stable recovery up and running, if a new version is released, can I just download the recovery zip of the rom and dirty flash it to update? Or do I download the OTA update zip and dirty flash it, how do I update in the future without losing my data
7- There is a lot of new recoveries for tucana/Mi Note 10 here on xda, OrangeFox and TWRP included, can we use the new recoveries instead the ones linked in the main post?
Thanks a lot!
okba_bsh said:
Hello
I read the thread here posted by h8Aramex
How to flash Xiaomi.eu firmware on Xiaomi Mi Note 10 - step-by-step guide
So this guide was written by DeathByArmadillo who partly copied it from user "Danmue" from an old post. Anyway, it works. Tested on Mi Note 10 with Global rom. Just re-posted it in it's own thread because the information was a bit scattered...
forum.xda-developers.com
And I have a few concerns
I asked in the main thread however the thread looks to be dead
If anyone knows a guide on how to do that and if it's a good idea to do so
I want to do that because the Global Rom lacks a lot of the features in the CN/EU Rom
Here are the questions:
1- Does this guide work on the new MIUI 12.5?
2- I'm on 12.5.3 Global and The latest EU is 12.5.1 , is that considered a downgrade that will brick my device? Because I heard people are not having luck with downgrades
3- What is the ROM used? Is it a stock EU that I can download from any xiaomi firmware source? Or is it a custom thing
I mean can I just go to xiaomifirmwareupdater and download the EEA version (It's same as the EU ROM right?)
4-I saw people complaining about non responsive touch, does that happen only in recovery? Or is it in the System?
5- Is it better if I only fastboot the EU rom and then flash the custom Recovery? And if not, what version of the firmware should I download, there's a recovery version and a fastboot version (larger than the recovery one)
6- Let's say I got a stable recovery up and running, if a new version is released, can I just download the recovery zip of the rom and dirty flash it to update? Or do I download the OTA update zip and dirty flash it, how do I update in the future without losing my data
7- There is a lot of new recoveries for tucana/Mi Note 10 here on xda, OrangeFox and TWRP included, can we use the new recoveries instead the ones linked in the main post?
Thanks a lot!
Click to expand...
Click to collapse
Google is your friend
MIUI 12.0 - MIUI 12.0/12.1/12.2/12.5 STABLE RELEASE
STABLE RELEASE RULES WHEN POSTING 1. If a ROM is not published DONT ASK ABOUT ITS ETA 2. If a ROM is not published DONT ASK why! 3. If a ROM is available, download it and use it 4. If a ROM has bugs, post the bug to the bug section if the BUG is not already listed 5. If you use any form of...
xiaomi.eu