Related
In order to have the forum cleaner, I open this new thread. This ROM isn't made by me, this is the original post where the ROM comes from: http://bbs.nubia.cn/forum.php?mod=viewthread&tid=989561
DOWNLOADS:
Original download link here: https://share.weiyun.com/b35f985310ba4cf1f33166f66ef56e2b
Mirror (GDrive) for 20170728 build:
https://drive.google.com/file/d/0B39cOh_mAq3ddFRyUVk3OVJXTEU/view?usp=sharing
Mirror (MEGA) for 20170808 build:
https://mega.nz/#!MIAWUILa!RZLiufqyHDI86GwxhA8xf399LKYaE9-VdUxEbFFV3hk
Debloater: http://cloud.tapatalk.com/s/598b40110944a/removeapps5.8.4.zip
GApps: http://opengapps.org
You have to choose Platform: ARM64 and Android: 7.1, you can choose any variant, but I recommend pico.
INSTRUCTIONS:
1.- Download the ROM, GApps and Debloater.
2.- Advanced Wipes of System, Data, Cache and ART/Dalvik Cache.
3.- Flash the ROM, Debloater and GApps.
4.- Enjoy!
Note: to update is better to do a fresh install (wipes in instructions) to avoid problems...
SCREENSHOTS:
See attachments
THANKS to:
@rasimyagubov for 20170728 build mirror
@ndv92 for 20170808 build mirror
Good idea to open a new thread for RR.
I just tried to update from previous version, but after rom flash i got relocked bootloader and unable to boot system. Anyone faced this problem?
IronJacob said:
Good idea to open a new thread for RR.
I just tried to update from previous version, but after rom flash i got relocked bootloader and unable to boot system. Anyone faced this problem?
Click to expand...
Click to collapse
Now that I look, my bootloader is locked as well... I made a clean flash and I restored apps with Titanium with no problems.
Enviado desde mi A0001 mediante Tapatalk
arceoxis said:
Now that I look, my bootloader is locked as well... I made a clean flash and I restored apps with Titanium with no problems.
Enviado desde mi A0001 mediante Tapatalk
Click to expand...
Click to collapse
I was able to restore backup as well.
You flashed rom with locked bl?
IronJacob said:
I was able to restore backup as well.
You flashed rom with locked bl?
Click to expand...
Click to collapse
I don't know if it was locked when I flashed, but all is working without issues
Enviado desde mi A0001 mediante Tapatalk
Thanks. I'll try it ASAP.
I've no personal apps installed from now.
The phone is actually full stock (no time)
IronJacob said:
Good idea to open a new thread for RR.
I just tried to update from previous version, but after rom flash i got relocked bootloader and unable to boot system. Anyone faced this problem?
Click to expand...
Click to collapse
I wiped system and flash RR + Gapps. It worked.
ndv92 said:
I wiped system and flash RR + Gapps. It worked.
Click to expand...
Click to collapse
I'll try on next update. For now i made a data backup in twrpclean flash and restored data.
Thank you
Tried to install it on f2fs partition, but it cause in bootloop.
So my question is: Does RR support F2FS and if not could you add support in the next update?
talsoake said:
Tried to install it on f2fs partition, but it cause in bootloop.
So my question is: Does RR support F2FS and if not could you add support in the next update?
Click to expand...
Click to collapse
Read, the dev of the ROM isn't here, he's Chinese... What's wrong with ext4? ?
Enviado desde mi NX563J mediante Tapatalk
talsoake said:
Tried to install it on f2fs partition, but it cause in bootloop.
So my question is: Does RR support F2FS and if not could you add support in the next update?
Click to expand...
Click to collapse
I remember the kernel and recovery must support f2fs then f2fs works. I guess this kernel doesn't now. The developer is a Chinese and no one knows if he will read this thread.
Arceoxis - I am in exactly the same position. Now boots straight into fastboot. I tried re-unlocking the boatloader. Device state shows as being locked. TWRP still accessible so I have options.
I was running the previous RR and device was unlocked, rooted and running fine. Looks like something in the flash is causing the phone to be re-locked? For info I did also flash the updated debloat.
EDIT: Clearing system, Data etc solved the problem. I realise that the instructions are clear - but this doesn't usually apply when updating to the same ROM.
Bob
boboskins said:
Arceoxis - I am in exactly the same position. Now boots straight into fastboot. I tried re-unlocking the boatloader. Device state shows as being locked. TWRP still accessible so I have options.
I was running the previous RR and device was unlocked, rooted and running fine. Looks like something in the flash is causing the phone to be re-locked? For info I did also flash the updated debloat.
EDIT: Clearing system, Data etc solved the problem. I realise that the instructions are clear - but this doesn't usually apply when updating to the same ROM.
Bob
Click to expand...
Click to collapse
I always make a clean flash, when I update too, so I didn't have that problem. I will add this info to the OP, thanks!
Enviado desde mi NX563J mediante Tapatalk
arceoxis said:
I always make a clean flash, when I update too, so I didn't have that problem. I will add this info to the OP, thanks!
Enviado desde mi NX563J mediante Tapatalk
Click to expand...
Click to collapse
I got this problem, too.
it's best to do a backup before flash.
I installed it. I think that charging speed is slow Is the quick charge valid?
hero-no said:
I installed it. I think that charging speed is slow Is the quick charge valid?
Click to expand...
Click to collapse
I don't know, but my phone charges fast...
Enviado desde mi NX563J mediante Tapatalk
arceoxis said:
I don't know, but my phone charges fast...
Enviado desde mi NX563J mediante Tapatalk
Click to expand...
Click to collapse
It was displayed from 78% to 100%, 1 hour 50 minutes remaining. The charger and cable you are using are using the accessories.
hero-no said:
It was displayed from 78% to 100%, 1 hour 50 minutes remaining. The charger and cable you are using are using the accessories.
Click to expand...
Click to collapse
It charges fast with stock charger and cable or Aukey cable and Aukey charger QC3.0 and It chsrges slow with Aukey cable and Nillkin charger.
Enviado desde mi NX563J mediante Tapatalk
arceoxis said:
It charges fast with stock charger and cable or Aukey cable and Aukey charger QC3.0 and It chsrges slow with Aukey cable and Nillkin charger.
Enviado desde mi NX563J mediante Tapatalk
Click to expand...
Click to collapse
I used the charger and cable bundled at the time of purchase. Charging was quick when it was probably an original ROM.
---------- Post added at 03:49 PM ---------- Previous post was at 03:21 PM ----------
hero-no said:
I used the charger and cable bundled at the time of purchase. Charging was quick when it was probably an original ROM.
Click to expand...
Click to collapse
Charging quickly became faster after rebooting. I will see a little more. Thank you.
Hey guys, is there any possibility to add an EIS to a custom Rom? Just curious about.
I am on Malaysk Rom, I tried to restore an Xtrons stock Rom using the SD firmware tool method described here and suggested personally to me by Malaysk https://forum.xda-developers.com/showpost.php?p=75664396&postcount=3254
I created the sd card with Xtrons firmware, inserted the sd card in gps slot, turned on the stereo, pressed reset button, the firmware upgrade took about 30 minutes, it gave me the message to remove the sd card, then I removed the sd card, but after the reboot I always have the Malaysk Rom. I also tried with wipe data in recovery after the firmware upgrading process. I really don't understand why and how the hell I can restore the stock rom, I'm going crazy. I tried also RK Batch tool but the stereo get not recognized by the PC in any way, so I can only use the SD card method. Please can someone give some help?
Why you are not just installing the rom update.img from recovery. Why you need to create a bootable sd card to update android 6?
focos said:
Why you are not just installing the rom update.img from recovery. Why you need to create a bootable sd card to update android 6?
Click to expand...
Click to collapse
Because if i try from recovery it always gives me error 04 image not valid, etc.. With both sd or usb stick
Inviato dal mio Z2 Pro utilizzando Tapatalk
Try to upgrade to oreo recovery, than flash stock oreo rom. Or if you prefer malaysk rom flash the moded oreo recovery than malaysk oreo rom. If you are not already tried.
focos said:
Try to upgrade to oreo recovery, than flash stock oreo rom. Or if you prefer malaysk rom flash the moded oreo recovery than malaysk oreo rom. If you are not already tried.
Click to expand...
Click to collapse
Thanks for the suggestion, but I don't want to change recovery and upgrade to Oreo, I don't want to make the situation worst, I'm already in trouble, I simply want to restore the stock ROM, I couldn't imagine that it would be so difficult...
So does anyone have a solution to restore a stock android 6 rom?
Inviato dal mio Z2 Pro utilizzando Tapatalk
mike2587 said:
So does anyone have a solution to restore a stock android 6 rom?
Inviato dal mio Z2 Pro utilizzando Tapatalk
Click to expand...
Click to collapse
Try creating the boot sd card with the update.img that come with the downloaded package and see if it work
iRcKenny said:
Try creating the boot sd card with the update.img that come with the downloaded package and see if it work
Click to expand...
Click to collapse
Already tried, same story
Inviato dal mio Z2 Pro utilizzando Tapatalk
mike2587 said:
Already tried, same story
Inviato dal mio Z2 Pro utilizzando Tapatalk
Click to expand...
Click to collapse
ok, thanks for reply.
Another suggestion: try using a low speed microsd, maybe your unit is not fully compatible with class 10 micro cards.
Are you using a PC whit Windows 7 for creating the recovery card and you are running the tool with "administrator rights"?
iRcKenny said:
ok, thanks for reply.
Another suggestion: try using a low speed microsd, maybe your unit is not fully compatible with class 10 micro cards.
Are you using a PC whit Windows 7 for creating the recovery card and you are running the tool with "administrator rights"?
Click to expand...
Click to collapse
Don't have another micro sd card, except one 32GB, but maybe it's too big.
I used win10 with admin rights, can try win7 on vbox but idk if the usb driver can give problems
Inviato dal mio Z2 Pro utilizzando Tapatalk
mike2587 said:
Don't have another micro sd card, except one 32GB, but maybe it's too big.
I used win10 with admin rights, can try win7 on vbox but idk if the usb driver can give problems
Inviato dal mio Z2 Pro utilizzando Tapatalk
Click to expand...
Click to collapse
32GB mSD is good, format with SD Formatter (full format) but you need absolutely use Win 7 for creating the boot card!
Windows 7 and Windows 10 kernel USB drivers are too different!
iRcKenny said:
32GB mSD is good, format with SD Formatter (full format) but you need absolutely use Win 7 for creating the boot card!
Windows 7 and Windows 10 kernel USB drivers are too different!
Click to expand...
Click to collapse
As I thought Windows 7 guest on Vbox doesn't recognize usb at all, unbelievable. And my cpu is not compatible with VMware...
mike2587 said:
As I thought Windows 7 guest on Vbox doesn't recognize usb at all, unbelievable. And my cpu is not compatible with VMware...
Click to expand...
Click to collapse
You need a real Win7 PC
iRcKenny said:
You need a real Win7 PC
Click to expand...
Click to collapse
Yea i have to create another partition on my pc, and install it for real, i wished that it was not necessary because i have already a dual boot with linux opensuse. Will try it anyway
Inviato dal mio Z2 Pro utilizzando Tapatalk
mike2587 said:
Yea i have to create another partition on my pc, and install it for real, i wished that it was not necessary because i have already a dual boot with linux opensuse. Will try it anyway
Inviato dal mio Z2 Pro utilizzando Tapatalk
Click to expand...
Click to collapse
Give it a try, maybe is working good
iRcKenny said:
Give it a try, maybe is working good
Click to expand...
Click to collapse
I tried with Windows 7, with the 32gb sd card i have en error all the times, with the 8gb included with the stereo i successfully created it, but again, when i make the procedure in the car, it doesn't restore the stock rom, always stuck on malaysk rom [emoji52]
Inviato dal mio Z2 Pro utilizzando Tapatalk
mike2587 said:
I tried with Windows 7, with the 32gb sd card i have en error all the times, with the 8gb included with the stereo i successfully created it, but again, when i make the procedure in the car, it doesn't restore the stock rom, always stuck on malaysk rom [emoji52]
Inviato dal mio Z2 Pro utilizzando Tapatalk
Click to expand...
Click to collapse
Also tried with rk batch tool with a Windows 7 pc connected with usb, but the stereo get not recognized, if i ask info to Witson, they give useless answers, they provide a bad support. They first sold me a stereo with broken display, now they basically shipped a broken unit again, with corrupted nand. DON'T BUY FROM WITSON!!
Inviato dal mio Z2 Pro utilizzando Tapatalk
mike2587 said:
I tried with Windows 7, with the 32gb sd card i have en error all the times, with the 8gb included with the stereo i successfully created it, but again, when i make the procedure in the car, it doesn't restore the stock rom, always stuck on malaysk rom [emoji52]
Inviato dal mio Z2 Pro utilizzando Tapatalk
Click to expand...
Click to collapse
Maybe at this point it depend to sd_boot_config.config file:
#rockchip sdcard boot config file for factory
loader_update = 0
display_led = 1
display_lcd = 1
pcba_test = 0
fw_update = 0
demo_copy = 0
fw_update = 0 line need to be fw_update = 1 ???
But im not an sure/expert for this, we need have an answer from Malaysk or from another expert forum member!
By the way haved you tried to install your original rom with recovery after using the created sd card?
iRcKenny said:
Maybe at this point it depend to sd_boot_config.config file:
#rockchip sdcard boot config file for factory
loader_update = 0
display_led = 1
display_lcd = 1
pcba_test = 0
fw_update = 0
demo_copy = 0
fw_update = 0 line need to be fw_update = 1 ???
But im not an sure/expert for this, we need have an answer from Malaysk or from another expert forum member!
By the way haved you tried to install your original rom with recovery after using the created sd card?
Click to expand...
Click to collapse
Already set on 1 that value.
I can't use the recovery because whatever update img file i use with sd or usb stick it always says that is not valid
Inviato dal mio Z2 Pro utilizzando Tapatalk
mike2587 said:
Already set on 1 that value.
Inviato dal mio Z2 Pro utilizzando Tapatalk
Click to expand...
Click to collapse
With value set at 0?
In Italy (where I am living) there is an important issue about 2° SIM slot
After the last update (9.6.4.0) it is not running well: the SIM introduced has not been recognized
This is the reason for which I am searching for previous version
Is there any possibility to find it ?
Thanks a lot
Paolo
Only Xiaomi could provide a link to download it.
Or, it could be possible to dump the partitions from a phone that still runs on that version, by unlocking its bootloader and using some terminal commands and/or adb. But it's a headache doing so.
BubuXP said:
Only Xiaomi could provide a link to download it.
Or, it could be possible to dump the partitions from a phone that still runs on that version, by unlocking its bootloader and using some terminal commands and/or adb. But it's a headache doing so.
Click to expand...
Click to collapse
A friend of mine has a device that is running 9.6.2.0 but at now it has bootloader locked ...
Unfortunately the unlocking comes with a full data wipe and so ... I am managing with it the thing ...
My idea is hot boot to custom recovery the device running 9.6.2.0 and perform only a system nandroid backup and flash it to the device that is running 9.6.4.0
Is it a bad idea ??
Inviato dal mio Mi A1 utilizzando Tapatalk
paolocorpo said:
A friend of mine has a device that is running 9.6.2.0 but at now it has bootloader locked ...
Unfortunately the unlocking comes with a full data wipe and so ... I am managing with it the thing ...
My idea is hot boot to custom recovery the device running 9.6.2.0 and perform only a system nandroid backup and flash it to the device that is running 9.6.4.0
Is it a bad idea ??
Inviato dal mio Mi A1 utilizzando Tapatalk
Click to expand...
Click to collapse
I don't know, it should work but I don't know if the radio partitions (probably the only partitions that could fix the bug) are included in the nandroid backup.
What build version are you running now in your phone?
BubuXP said:
I don't know, it should work but I don't know if the radio partitions (probably the only partitions that could fix the bug) are included in the nandroid backup.
Click to expand...
Click to collapse
I know .. and I agree you
If I could have in my hands the full factory image I could extract radio/modem partition and flash only it but ... I am not able to find 9.6.2.0 firmware ... No way ... So far ...
Inviato dal mio Mi A1 utilizzando Tapatalk
paolocorpo said:
I know .. and I agree you
If I could have in my hands the full factory image I could extract radio/modem partition and flash only it but ... I am not able to find 9.6.2.0 firmware ... No way ... So far ...
Inviato dal mio Mi A1 utilizzando Tapatalk
Click to expand...
Click to collapse
Another remote possibility is that your phone was on 9.6.2.0, then you updated via OTA to 9.6.4.0 and you stopped updating. Only in that case, in the inactive slot there will be still the 9.6.2.0 versions of the partitions.
BubuXP said:
Another remote possibility is that your phone was on 9.6.2.0, then you updated via OTA to 9.6.4.0 and you stopped updating. Only in that case, in the inactive slot there will be still the 9.6.2.0 versions of the partitions.
Click to expand...
Click to collapse
Unfortunately I am not the direct owner of Mi A2 lite
But I will analyze your interesting scenario
Thanks a lot
Inviato dal mio Mi A1 utilizzando Tapatalk
Have you tried a GSI to see if one of them fixes the issue? At least then we'll know for sure its ROM related.
cpu004 said:
Have you tried a GSI to see if one of them fixes the issue? At least then we'll know for sure its ROM related.
Click to expand...
Click to collapse
I am sorry but I don't understand
What does it mean GSI ?
Inviato dal mio Mi A1 utilizzando Tapatalk
paolocorpo said:
I am sorry but I don't understand
What does it mean GSI ?
Inviato dal mio Mi A1 utilizzando Tapatalk
Click to expand...
Click to collapse
It's a treble ROM, like this:
https://forum.xda-developers.com/mi-a2-lite/development/9-0-pixelexperience-p-unofficial-t3840551
But as it doesn't touch the radio partitions (only the system partition), I doubt it will resolve.
But many settings are stored on /system, maybe... Give it a try if you can.
I have an issue like that.. but in my case none of the two slots recognize my sim card, I'm from México. How do you think I can fix this?
I have 10 days with this problem, tried 9.6.4.0, 9.6.6.0, 9.6.8.0 and some of the GSI ROMS and none of that seems to fix the issue.
Enviado desde mi Mi A2 Lite mediante Tapatalk
BubuXP said:
It's a treble ROM, like this:
https://forum.xda-developers.com/mi-a2-lite/development/9-0-pixelexperience-p-unofficial-t3840551
But as it doesn't touch the radio partitions (only the system partition), I doubt it will resolve.
But many settings are stored on /system, maybe... Give it a try if you can.
Click to expand...
Click to collapse
Uhm ... It looks as a small miracle
As I said I am not the owner ... Honestly could be a small risk
But are you suggesting to flash all the ROM or only the modem/radio partition ?
Do you know on which version is it based ??
Inviato dal mio Mi A1 utilizzando Tapatalk
dore22 said:
I have an issue like that.. but in my case none of the two slots recognize my sim card, I'm from México. How do you think I can fix this?
I have 10 days with this problem, tried 9.6.4.0, 9.6.6.0, 9.6.8.0 and some of the GSI ROMS and none of that seems to fix the issue.
Enviado desde mi Mi A2 Lite mediante Tapatalk
Click to expand...
Click to collapse
When you had 9.6.2.0 was the problem existing ?
Inviato dal mio Mi A1 utilizzando Tapatalk
paolocorpo said:
Uhm ... It looks as a small miracle
As I said I am not the owner ... Honestly could be a small risk
But are you suggesting to flash all the ROM or only the modem/radio partition ?
Do you know on which version is it based ??
Click to expand...
Click to collapse
That ROM is only a system.img file, no other partitions are involved.
BubuXP said:
That ROM is only a system.img file, no other partitions are involved.
Click to expand...
Click to collapse
I see ... I will download it in order to take a look
paolocorpo said:
When you had 9.6.2.0 was the problem existing ?
Inviato dal mio Mi A1 utilizzando Tapatalk
Click to expand...
Click to collapse
No, maybe if we could flash radio partition from 9.6.2.0 the problem will be solved. It's a possibility.. respect about flashing a GSI ROM it doesn't solve the problem in my case but you can try it by yourself
Enviado desde mi Mi A2 Lite mediante Tapatalk
dore22 said:
No, maybe if we could flash radio partition from 9.6.2.0 the problem will be solved. It's a possibility.. respect about flashing a GSI ROM it doesn't solve the problem in my case but you can try it by yourself
Enviado desde mi Mi A2 Lite mediante Tapatalk
Click to expand...
Click to collapse
Yes
This is my strategy and this is the reason why I am searching for that firmware ... Or it's dump
Inviato dal mio Mi A1 utilizzando Tapatalk
i thought the 9.6.4.0 was the first release. then the otas 9.6.6.0. and 9.6.8.0.
eltano06 said:
i thought the 9.6.4.0 was the first release. then the otas 9.6.6.0. and 9.6.8.0.
Click to expand...
Click to collapse
I have not direct experience (I am helping some guys owners of this device that are facing this issue)
They say that the issue was absent with firmware version 9.6.2.0 that was bundled in purchased device
Inviato dal mio Mi A1 utilizzando Tapatalk
paolocorpo said:
I have not direct experience (I am helping some guys owners of this device that are facing this issue)
They say that the issue was absent with firmware version 9.6.2.0 that was bundled in purchased device
Inviato dal mio Mi A1 utilizzando Tapatalk
Click to expand...
Click to collapse
Hi, I confirm it.
In early August I bought a MI A2 lite in Italy that came out with V.9.6.2.0 stock firmware.
I updated it immediately via OTA to V.9.6.4.0, but I used it with one sim (SIM 1 slot) only for some days,
When I inserted an additional sim in slot 2 I experienced the problem, but thinking of an hardware failure, I was able to get it replaced by store.
In the meantime I read about this bug and my second MI A2 Lite wasn't updated at all, and is currently running on V.9.6.2.0 yet, without problems.
Tried to open a bug report to xiaomi but I had no useful answers (yet) but a standard reply from some indian people, I guess, from a self naming "MIUI bug hunter team":
http://en.miui.com/thread-3683653-1-6.html
see also:
http://en.miui.com/thread-3792043-1-1.html
Regards
I am on the official MIUI Global 10.3.1 Pie ROM and everything works fine except the internet. It will be working fine then bam, no internet on both wifi and SIM. The only option is to reboot the phone and internet is restored immediately on both wifi and SIM. Sometimes this happens while using the internet but sometimes it also happens if I leave the phone for too long. It's very frustrating. Fyi, I am using Blokada but disabling the VPN doesn't make any difference. Is there any solution to this? Thanks.
Have you tried a factory reset? Often it solves problems...
No problem for me until today. Wifi and 4g works both perfectly. (even in hotspots within buildings with a good distance)
Redmi note 5 stock Rom.
Envoyé de mon Redmi Note 5 en utilisant Tapatalk
JLLE said:
Have you tried a factory reset? Often it solves problems...
No problem for me until today. Wifi and 4g works both perfectly. (even in hotspots within buildings with a good distance)
Redmi note 5 stock Rom.
Envoyé de mon Redmi Note 5 en utilisant Tapatalk
Click to expand...
Click to collapse
No, I haven't yet tried a factory reset as I want to use it as a last resort. I'll wait for some alternatives for a while before I try that.
I understand it's boring, but sometimes it's the only way to get reliable results.
Envoyé de mon Redmi Note 5 en utilisant Tapatalk
JLLE said:
I understand it's boring, but sometimes it's the only way to get reliable results.
Envoyé de mon Redmi Note 5 en utilisant Tapatalk
Click to expand...
Click to collapse
Nooooo... don't say that! May be someone can give me a zip file that will miraculously solve my internet problem :angel:
Holly Xiaomi pray for us! [emoji4]
Envoyé de mon Redmi Note 5 en utilisant Tapatalk
It also happen to me this past week. Tryna change my Pixel rom to other Pie rom hope it might fix my problem
Onebar123 said:
It also happen to me this past week. Tryna change my Pixel rom to other Pie rom hope it might fix my problem
Click to expand...
Click to collapse
The stock is smooth enough and feature-rich for me to try a new ROM. I'll try a factory reset this weekend. Hopefully, this will fix the problem.
Having the same issue here, has OP already done the factory reset? Did it work?
AfterShöcK90 said:
Having the same issue here, has OP already done the factory reset? Did it work?
Click to expand...
Click to collapse
I haven't done it yet. Will update when I do.
Ever since I updated to 10.3.1.0 pie update, I am unable to use my wifi. Even after 10.3.2.0 update by miui problem is not solved. I have to limit my internet usage because of it. I already wrote many time to miui developer about it but still they are not listening. On their forum I found that some rn5 pro users are facing similar issues. Can anyone find a solution for this problem? When I heir wifi button it turns off automatically in 10 seconds. Please help me if you can.
Try a factory reset, mostly solve all kind of problems.
Envoyé de mon Redmi Note 5 en utilisant Tapatalk
JLLE said:
Try a factory reset, mostly solve all kind of problems.
Envoyé de mon Redmi Note 5 en utilisant Tapatalk
Click to expand...
Click to collapse
It didn't help me. I tried the method already.