Hi all XDA's members and Meticulus's RR ROM contributors,
I would like to share my experience with Meticulus's RR ROM for Honor 5C.
First I tried Elite V6 with no success : bootloop, F2FS or EXT4 nothing to do ; the Elite V7 is available from Christmas but I see that there are bugs to fix for Hassan, so I gave up and restored a backup of my STOCK system.
The restore was not good as my camera and audio no longer worked...
Before I get back to the STOCK update NEM-L51C432B357, I decided to try Meticulus's RR. It was a very good idea as I now have a renamed Honor 5c to hi6250 (...) working with no bug up to now.
LTE OK, SMS OK, GPS OK, SDCARD OK, AUDIO OK, VIDEO OK, GAPPS OK, MTP OK, etc
Adaway OK, Afwall+ OK, Magisk v14 OK
+ Bonus : Evie Launcher working as it was not using with STOCK ROM (icon size issue) !
Many thanks to Meticulus and contributors for sharing this very good work.
---
To be more precise for Honor 5C owners :
DEVICE : HONOR 5C
ROM STOCK BUILD : NEM-L51C432B350
MODDED RECOVERY .. : TWRP-3.1.1-0-hi6250-v5.2.zip
ROM INSTALLED .... : RR-N-v5.8.5-20171214-hi6250-Meticulus.zip
GAPPS INSTALLED .. : open_gapps-arm64-7.1-pico-20171225.zip
---
Steps of my successful installation with SDCARD and no SIM CARD :
1- FASTBOOT the TWRP then reboot to the TWRP RECOVERY
2- Wipe all except external SDCARD
3- Install the ROM
4- Reboot to TWRP RECOVERY
5- Install the GAPPS
6- Reboot to system (RR)
7- During RR Android setup, when asked insert the SIM CARD.
It would perhaps also have been successful with the SIM CARD inserted from the beginning...
---
Questions/feature requests :
- On Resurrection Remix site, I have not found your great ROM why ?
- On XDA Dev, there is no thread "Resurrection Remix For The Honor 5C [METICULUS]" but a "[ROM][7.1.2] Resurrection Remix For The Honor 6x [METICULUS]" one, this is why I put my comments here and in the Elite thread for those like me unable to get Elite V6 or V7 working with their Honor 5C.
- One thing is really missing to me (not found in settings) : the scheduled start/stop that worked very well with the STOCK ROM.
Do you think that this useful feature could be added on a future version ?
- The double TAP for screen wake up, would be a great bonus feature (was not provided in the STOCK ROM).
- Not tested the OTG, I will tell it in this thread.
Thanks again.
---
Meticulus's replies :
1. It is unlikely that any device with a kirin processor will get "official support" for LineagOS and therefore Resurrection Remix. There just isn't enough source.
2. Just because there is no "Honor 5c" thread doesn't mean you should come here and confuse information. It makes the water muddy. There is nothing stopping you from creating a thread in the "Honor 5c General" and post your experienced there.
3. Scheduled device start and sleep is not something I will work on.
4. DoubleTap 2 Wake only works on some P9 Lite's. Other devices with different touchscreens simply do not have the hardware capability.
5. I'm glad you like the ROM but please re-post your experiences in the Honor 5c section. I intend to delete these posts...
Is working dual sim and volte
Is works dual sim and volte
Sim working fine??
What do you think solved the audio issue?
Reverting to Stock Rom backup could have helped somehow.
Renaming it maybe ? And how did you rename it? After installing this rom mine became hi6250.
I own a nmo-l31 and ever since installing EliteRom v7 i could not get the audio working. Installed EliteRom v6 , applied l-31 patch,nothing.
Trying to switch to stock rom with dload gave error
Directly flashing boot,system,cust,recovery from firmware packages didnt change anything on the userspace ,literally.My files,homescreen etc. remained the same and only recovery changed. I think i made a mistake there but who knows.
Now installed this ResurrectionRemix twrp and rom after seeing this thread.Audio still refuses to work .
thatwasmyfakeacc said:
What do you think solved the audio issue?
Click to expand...
Click to collapse
I had the same problem on my NEM-L51. The problem is (or at least i think it is), that the vendor partition is somehow corrupted.
Short explaination, the vendor partition holds some drivers which are not open source (therefore not in the android kernel) and also aren't shipped in the custom roms (because of copyright stuff). So you always need to have them, if the custom rom depends on them (and most/all of the honor 5c custom roms do so). That's also the reason why you always have to flash the custom rom over your emui5.x and if you screwed your whole system, you first need to flash a backup or get back to emui on a different way before you can flash a working custom rom again.
So that's the explaination part. I installed twrp on my device, took a complete backup, flashed aosp from meticulus, everything worked except of Audio/Videos. Flashed LineageOS from Hassan, everything worked except of audio/video playback. Flashed backup, everything worked except audio/video. WTF. I don't know why, but i believe that the backups made with TWRP were somehow not complete, because flashing all partitions (the backup was over all partitions, triple checked, made new backups from stock) didn't solve audio issues, not even on the stock backup. What I now did was getting back to stock with the dload method, and flashed again directly the lineageos from hassan, which then worked. I had a try before where i first accidentially flashed aosp again, and same problems occured again. Also the now stock backup again didn't work. That's why i think that the TWRP backups for Honor 5c NEM-L51 are somehow not right.
Tl;dr if you have audio/video playback issues, try to get back to stock (make sure those features work on your stock rom) and flash again. If it still doesn't work, custom rom is maybe not compatible with nem-l51 (only experienced that with meticulus roms, hassans work great).
thatwasmyfakeacc said:
I own a nmo-l31 and ever since installing EliteRom v7 i could not get the audio working. Installed EliteRom v6 , applied l-31 patch,nothing.
Trying to switch to stock rom with dload gave error
Directly flashing boot,system,cust,recovery from firmware packages didnt change anything on the userspace ,literally.My files,homescreen etc. remained the same and only recovery changed. I think i made a mistake there but who knows.
Click to expand...
Click to collapse
Try again with the dload method, maybe use another UPDATE.zip. I had to try it several times, device booted sometimes for ever, and suddenly it worked. No idea why, but maybe try it again.
Custom Roms is good but overal it lacks supports for long terms and quality of pictures taken are not as nice as stock ones
stevedat said:
Custom Roms is good but overal it lacks supports for long terms and quality of pictures taken are not as nice as stock ones
Click to expand...
Click to collapse
also system collect trash files that slows you down. i used to be all in for custom roms but now i dont use them because they will break in time and standby batterydrain will increase rapidly.
thelous said:
also system collect trash files that slows you down. i used to be all in for custom roms but now i dont use them because they will break in time and standby batterydrain will increase rapidly.
Click to expand...
Click to collapse
Rite, it's just for fun.
shankarjdhv125 said:
Is works dual sim and volte
Click to expand...
Click to collapse
Hi,
Dual SIM not tested, Volte I don't know if it works using my ISP (free.fr) and don't know how to check this.
An advice, don't update Magisk, I have done it on several rr (honor 5c, idol3 5.5), the result was bootloop.
Hi everyone,
To flash the last rom (nightly ) of LineageOS ( in Oreo,from the 2 february), i had to put the firmware 5.1.7. After flash this firmware i was able to flash the ROM but it makes my phone extremely slow and with screen issues (i can still use the tactile but the screen doesnt follow).
I restored but the problem stills then i put le last stable ROM from Oneplus on android pie (9.0.3). It is a bit better (still really slow) and after a moment i get now like a white noise (same as on TV but with color moreover) by wink ( was more and more often on Google Maps), I had to reboot cause i couldnt use more my phone.
Thanks you in advance !
Ps : I've got TWRP from siankatabg and i'm not rooted , if you want me to send log tell me how pls.
Up :good:
When you were flashing did you used this instructions?
https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003
Flash codework's TWRP for Pie. After that reboot into recovery, wipe everything down and use clean flash instructions for your OTA. It should be able to fix any issue you were having. If not let me know.
Yes i followed the clean flash way (it didn't resolve my issue) but my issue occured before i flash pie, when i flashed lineageOS 15.1 with the firmware 5.1.7 required (which i flashed too). A restoration didnt change that issue.
I tried with the TWRP from codework but it doesnt recognise my internal stockage.
Thanks of your time.
Raidenne said:
Yes i followed the clean flash way (it didn't resolve my issue) but my issue occured before i flash pie, when i flashed lineageOS 15.1 with the firmware 5.1.7 required (which i flashed too). A restoration didnt change that issue.
I tried with the TWRP from codework but it doesnt recognise my internal stockage.
Thanks of your time.
Click to expand...
Click to collapse
Hi, try wiping everything down with the new TWRP, after that reboot into recovery once more. Install last normal working OOS to see if that helps you. If not maybe it is hardware issue? Let me know once you wiped and installed the last working OOS on it.
I have installed multiple roms and firmware updates on my device with codework's TWRP and never had big issue like this. In my opinion best option for you to trace your steps back to the last working version of your os and try learning what might have gone wrong.
Ebeninyo said:
Hi, try wiping everything down with the new TWRP, after that reboot into recovery once more. Install last normal working OOS to see if that helps you. If not maybe it is hardware issue? Let me know once you wiped and installed the last working OOS on it.
I have installed multiple roms and firmware updates on my device with codework's TWRP and never had big issue like this. In my opinion best option for you to trace your steps back to the last working version of your os and try learning what might have gone wrong.
Click to expand...
Click to collapse
My issues seem gone since few weeks with the last OTA (it very rarely happens now). I don't know what caused that even if i use my backup.
Thanks for your support !
Fingerprint Scanner Null after Pie ROM Flash - Custom ROM won't fix. Stock Only
Ok, the story.... Moto G5+ retail, running 8.1 Oreo, Bootloader Unlocked, rooted using Magisk 16.7 and was able to backup my Stock Oreo ROM once rooted, or I'd be dead in the water.
So wanting to stay ahead, I tried my hand at RR v7's Pie version, which, after some troubleshooting, was able to install successfully; but I don't much care for the google bar and other hard-coded "pure android" features. Same thing with Pixel Exp. Not to mention that Pie disallows call recording among a few other things Google decided to stifle its customers with. Deal breaker. So - moving on...or back for that matter.
I proceeded to download RRv6, which is btw running nicely on a 2nd G5+, same GApps, installs perfect except - FingerPrint Reader is not acknowledged. Period. No Security settings, No RR Config to access it, Nada. No matter what ROM I flash outside of the StockROM I backed up, it won't recognize the fp reader upon boot up. Whether I clear Dalvik/Cache, All DATA, do a full Wipe, DATA WIPE, REPAIR, FORMAT, nothing allows me to install RR v6.0 or any other flavor, Oreo or Pie, even while trying a dirty flash over Stock Oreo on this Moto G5+. Tried with several SD Cards, downloading fresh zip files from RR. I even went so far as to image the working G5+, then copy into the 2nd G5's SN folder, and do a restore, just loops - even after repairing the partition. I managed to work around that, Restored the image, but still no FP recognized by the initial Google startup/setup. It's almost as if the phone's been "firmwared" or "tagged".
Any ideas what could be lingering from Android Pie that would survive a F2FS/exT Format? Because something updated some kind of firmware on the phone during a Pie ROM flash, that now won't let me go back to anything below Pie, with a working fingerprint reader. The only difference between the G5 that works and this one is the working one has never seen Android 9. And it's staying that way til we come up with a way to hack the google crap.
Any help would be - awesome to say the least.
Thanks for looking.
Hello,
The issue with fingerprint is that after flashing stock Oreo ROM it replaces some files related to fingerprint sensor.
Hence all the newer custom ROM builds use the Oreo firmware related files. Hence it worked on the Pie ROM.
RR v6 would be still using the old nougat firmware hence you need to flash a file for it work. Which will replace the fingerprint related files for Nougat Stock firmware:
https://androidfilehost.com/?fid=1322778262904029634
In case you want to revert the changes and use Pie ROMs:
https://androidfilehost.com/?fid=1322778262904029635
sharan.nyn said:
Hello,
The issue with fingerprint is that after flashing stock Oreo ROM it replaces some files related to fingerprint sensor.
Hence all the newer custom ROM builds use the Oreo firmware related files. Hence it worked on the Pie ROM.
RR v6 would be still using the old nougat firmware hence you need to flash a file for it work. Which will replace the fingerprint related files for Nougat Stock firmware:
https://androidfilehost.com/?fid=1322778262904029634
In case you want to revert the changes and use Pie ROMs:
https://androidfilehost.com/?fid=1322778262904029635
Click to expand...
Click to collapse
That would make sense if PHONE1 manifested the same thing. But I went from StockOreo to RRv6-Oreo w/out losing anything and having to flash any FP Firmware. I used the RRv6 Official from 18-0911. Which is what's been leading me to believe there's something awry with this 2nd G5. I wonder is it possible PHONE2 has some slight firmware variance that is simply ignoring during the RR flash? Anyway, I'll give this a shot. this is TWRP flash, not fastboot, yes? Just being clear as I'm not proficient at this just yet.
Thanks Sharan!
DJScribe said:
That would make sense if PHONE1 manifested the same thing. But I went from StockOreo to RRv6-Oreo w/out losing anything and having to flash any FP Firmware. I used the RRv6 Official from 18-0911. Which is what's been leading me to believe there's something awry with this 2nd G5. I wonder is it possible PHONE2 has some slight firmware variance that is simply ignoring during the RR flash? Anyway, I'll give this a shot. this is TWRP flash, not fastboot, yes? Just being clear as I'm not proficient at this just yet.
Thanks Sharan!
Click to expand...
Click to collapse
Yeah, give it a try. And yes it's to be flashed via TWRP.
[SOLVED]
sharan.nyn said:
Yeah, give it a try. And yes it's to be flashed via TWRP.
Click to expand...
Click to collapse
Sweet! I had to reflash from scratch as for some reason it wouldn't let me update the ROM already running. But once I re-flashed RRv6-8.1, then flashed FP, it's now back. You rock Sharyn - nice work!
Now if only we found a way to cleanup that Pie - hate the perpetual time stamp, search bar and inability to record voice. Which is why I'm staying on Oreo til further notice. I know it was Google who took it away on v9.
Thanks again Shar!
:good::victory:
DJScribe said:
Sweet! I had to reflash from scratch as for some reason it wouldn't let me update the ROM already running. But once I re-flashed RRv6-8.1, then flashed FP, it's now back. You rock Sharyn - nice work!
Now if only we found a way to cleanup that Pie - hate the perpetual time stamp, search bar and inability to record voice. Which is why I'm staying on Oreo til further notice. I know it was Google who took it away on v9.
Thanks again Shar!
:good::victory:
Click to expand...
Click to collapse
Crap - so turns out this solution was short-lived. FingerPrint Scanner is back to inactive and FPzip isn't fixing it. Only StockOreo brings it back. Tried a plethora of ROMs from Nougat to Oreo, nothing but Pie and stock Oreo. Symptoms say it's the ROM, but a ROM that is currently working on the 1st G5 won't work either. Still looking for solutions, anyone...
Hi,
I have strange problem, used 9T come to me with wiped system (factory reset) but when MIUI loaded system i have notification "Android setup isn't responding". I can't accept it or anythink, configuration screen isn't loaded only black screen with status bar and navigation buttons. I can go to settings by the notifiaction bar, but after 10 seconds phone freezing and rebooting by itself.
I flash new system without errors, but it wont fix the problem
I had the same problem, I spent all the roms and the only one that worked was davinci_global_images_V10.3.5.0.PFJMIXM_20190528.0000.00_9.0_global_4222a49ff1
good that the phone is working again but now i'm facing other problems because i can't update the phone otherwise it goes back to loop and with this rom no sensor is working as a presence sensor, gyroscope and also problems with the front camera that is not it is working correctly.
crt-shadow said:
Hi,
I have strange problem, used 9T come to me with wiped system (factory reset) but when MIUI loaded system i have notification "Android setup isn't responding". I can't accept it or anythink, configuration screen isn't loaded only black screen with status bar and navigation buttons. I can go to settings by the notifiaction bar, but after 10 seconds phone freezing and rebooting by itself.
I flash new system without errors, but it wont fix the problem
Click to expand...
Click to collapse
crt-shadow said:
Hi,
I have strange problem, used 9T come to me with wiped system (factory reset) but when MIUI loaded system i have notification "Android setup isn't responding". I can't accept it or anythink, configuration screen isn't loaded only black screen with status bar and navigation buttons. I can go to settings by the notifiaction bar, but after 10 seconds phone freezing and rebooting by itself.
I flash new system without errors, but it wont fix the problem
Click to expand...
Click to collapse
i have the same problem do you have the solution right now? :<
Same problem here. I also can't turn on the wifi and sim cards aren't detected
crt-shadow said:
Hi,
I have strange problem, used 9T come to me with wiped system (factory reset) but when MIUI loaded system i have notification "Android setup isn't responding". I can't accept it or anythink, configuration screen isn't loaded only black screen with status bar and navigation buttons. I can go to settings by the notifiaction bar, but after 10 seconds phone freezing and rebooting by itself.
I flash new system without errors, but it wont fix the problem
Click to expand...
Click to collapse
same here, keep rebooting, u solved it?
Factory reset does not mean to Wipe System but Data.
Gyroscope and other sensors not working are the result of wiping Persist, Vendor and other partitions
Proper procedure to switch the ROM/install custom ROM requires:
- Format Data (option in TWRP, exactly as that "Format Data")
- Wipe Cache
- Do not Wipe any other partition !!!!!!!
- Flash your custom ROM
Unfortunately, there are noobs who don't know/understand, and they Wipe System, Vendor, Persist and who knows what other partitions they think off.
The result is the phone behaving as described
To recover, try flashing the TGZ stock ROM from Mi Flash (not just the ZIP ROM from TWRP).
Anyway, if Persist was wiped, you will never, ever recover DRM L1
zgfg said:
Factory reset does not mean to Wipe System but Data.
Gyroscope and other sensors not working are the result of wiping Persist, Vendor and other partitions
Proper procedure to switch the ROM/install custom ROM requires:
- Format Data (option in TWRP, exactly as that "Format Data")
- Wipe Cache
- Do not Wipe any other partition !!!!!!!
- Flash your custom ROM
Unfortunately, there are noobs who don't know/understand, and they Wipe System, Vendor, Persist and who knows what other partitions they think off.
The result is the phone behaving as described
To recover, try flashing the TGZ stock ROM from Mi Flash (not just the ZIP ROM from TWRP).
Anyway, if Persist was wiped, you will never, ever recover DRM L1
Click to expand...
Click to collapse
The same problem remains even after your method.
pranav1201 said:
The same problem remains even after your method.
Click to expand...
Click to collapse
What exact problem, with which ROM, what did you previously do with the phone?
Hello @zgfg
I'm having the same error as the OP with my Mi 8 (dipper).
I done goofed up, as I had the official 12.0.3.0 stock ROM installed, and then I wanted to go with the 12.5.2.0 EU ROM. I installed it no problem, but then in my infinite wisdom I tried to lock the bootloader via fastboot while having the EU ROM installed. Everything went to hell after that.
After that, I cannot make the phone work properly regardless of the ROM I try to install. With MIUI (both stock and EU), I cannot get the WiFi to work properly (Ino networks are shown), and the "Android Setup isn't responding" error does not let me finish the setup of the device. I also tried lineage, where I also cannot find any networks, so the setup pretty much stops there.
It is obvious I effed up something with lower-level files, I definitely just erased everything from TWRP at one point when I was panicing.
I tried flashing the stock ROM using Mi Flash as you said, but it did not work. Can you provide me a way of checking what is going wrong or a general way to fix this?
Fjolfrin said:
Hello @zgfg
I'm having the same error as the OP with my Mi 8 (dipper).
I done goofed up, as I had the official 12.0.3.0 stock ROM installed, and then I wanted to go with the 12.5.2.0 EU ROM. I installed it no problem, but then in my infinite wisdom I tried to lock the bootloader via fastboot while having the EU ROM installed. Everything went to hell after that.
After that, I cannot make the phone work properly regardless of the ROM I try to install. With MIUI (both stock and EU), I cannot get the WiFi to work properly (Ino networks are shown), and the "Android Setup isn't responding" error does not let me finish the setup of the device. I also tried lineage, where I also cannot find any networks, so the setup pretty much stops there.
It is obvious I effed up something with lower-level files, I definitely just erased everything from TWRP at one point when I was panicing.
I tried flashing the stock ROM using Mi Flash as you said, but it did not work. Can you provide me a way of checking what is going wrong or a general way to fix this?
Click to expand...
Click to collapse
Sorry, I would never go to relock BL while having the custom ROM (I thought it would instantly brick the phone)
Not sure could I help but I'm also curious:
- You relocked the Bootloader by fastboot oem lock or by fastboot flashing lock?
- It locked BL, did Factory reset but kept Xiaomi.eu ROM?
- After that you unlocked BL again (otherwise how would you continue flashing the other ROMs)?
- Did you then unlock BL by Mi Unlock tool or by fastboot flashing unlock?
- Did you then you flash Fastboot/tgz version of the stock MIUI?
And with that the phone does not work properly (network, etc)?
- What version of MIUI you flash, MIUI 12.1 (Global, EEA)?
- Did you try with CN 12.5.2.0, Fastboot/TGZ version (closest Fastboot MIUI version to your previous Xiaomi.eu)?
Un-gzip, unutar, find inside bat scripts (I think 3 of them) choose one that makes Factory reset but does not relock BL.
Edit the script to remove first 3-4 lines that check against downgrading (not having the script in front of me to tell you exactly but you will see when you open the script), and run the bat from Fastboot
zgfg said:
Sorry, I would never go to relock BL while having the custom ROM (I thought it would instantly brick the phone)
Not sure I could help but I'm also curious:
- You relocked the Bootloader by fastboot oem lock or by fastboot flashing lock?
- It locked BL, Factory reset but kept Xiaomi.eu ROM?
- After that you unlocked BL again (otherwise how would you flash the other ROMs)?
- You unlocked BL by Mi Unlock tool or by fastboot flashing unlock?
- Then you flashed Fastboot/tgz version of the stock MIUI?
And with that the phone does not work properly (network, etc)?
- What version of MIUI you tried to flash, MIUI 12.1 (Global, EEA)?
-Did you try with CN 12.5.2.0, Fastboot/TGZ version?
Un-gzip, unutar, find inside bat scripts (I think 3 of them) choose one that makes Factory reset but does not relock BL.
Edit the script to remove first 3-4 lines that check against downgrading (not having the script in front of me to tell you exactly but you will see when you open the script)
Click to expand...
Click to collapse
Thanks for the reply! Here we go:
1. By fastboot oem unlock.
2. I am not sure I remember. I think it could not boot at all.
3. Yes I unlocked it.
4. I have always used the Mi unlock tool to unlock the bootloader.
5. Yes I flashed it this way and it did not work. To be precise, I completely extracted the tgz, I opened Mi flash, selected the final extracted folder, and I flashed this way.
6. With Mi flash I have used the official rom, meaning 12.0.3.0 global (in case you did not read it, this is all for a Mi 8, I just found this thread and though to ask). When I install the EU rom, I use twrp.
7. No I haven’t tried Chinese roms, should I?
I have also tried directly running the bat scripts from the extracted folder as you said, but it didn’t work. Same thing.
Fjolfrin said:
Thanks for the reply! Here we go:
1. By fastboot oem unlock.
2. I am not sure I remember. I think it could not boot at all.
3. Yes I unlocked it.
4. I have always used the Mi unlock tool to unlock the bootloader.
5. Yes I flashed it this way and it did not work. To be precise, I completely extracted the tgz, I opened Mi flash, selected the final extracted folder, and I flashed this way.
6. With Mi flash I have used the official rom, meaning 12.0.3.0 global (in case you did not read it, this is all for a Mi 8, I just found this thread and though to ask). When I install the EU rom, I use twrp.
7. No I haven’t tried Chinese roms, should I?
I have also tried directly running the bat scripts from the extracted folder as you said, but it didn’t work. Same thing.
Click to expand...
Click to collapse
1) Should have been "lock", not "unlock"
7) If I understood correctly, you had Xiaomi.eu 12.5.2.
Hence I think you should try the closest MIUI version (Fastboot, not Recovery - Fastboot flashes more deeply), and that could only be CN 12.5.2 (Global, EEA are 12.0.3 for your device)
The best would be Fastboot version of Xiaomi.eu 12.5.2 but AFAIK, there is no such thing
Hence after the CN 12.5.2 try then (Recovery) Xiaomi.eu 12.5.2
zgfg said:
1) Should have been "lock", not "unlock"
7) If I understood correctly, you had Xiaomi.eu 12.5.2.
Hence I think you should try the closest MIUI version (Fastboot, not Recovery - Fastboot flashes more deeply), and that could only be CN 12.5.2 (Global, EEA are 12.0.3 for your device)
The best would be Fastboot version of Xiaomi.eu 12.5.2 but AFAIK, there is no such thing
Hence after the CN 12.5.2 try then (Recovery) Xiaomi.eu 12.5.2
Click to expand...
Click to collapse
1) Yeah lol, mistyped.
7) Ok! I’ll give it a try. I have an early wake tomorrow tho and I have already spent too much time for this, so it’ll be a while before I come back with news.
Thank you!
You can use MIUI Downloader:
MIUI Downloader - Apps on Google Play
MIUI upgrade app for Mi users.
play.google.com
to easily locate the download link for eg your Fastboot CN 12.5.2 - screenshot
zgfg said:
You can use MIUI Downloader:
MIUI Downloader - Apps on Google Play
MIUI upgrade app for Mi users.
play.google.com
to easily locate the download link for eg your Fastboot CN 12.5.2 - screenshot
Click to expand...
Click to collapse
Good morning!
So I installed the china ROM (12.5.2.0 QEACNXM) using mi flash, and I'm having similar issues. I did not get the "android setup stopped working", however WiFi is still not responding as before, and I got two "Security stopped working" and "Settings stopped working" errors.
Edit: WiFi cannot actually be turned on at all.
Fjolfrin said:
Good morning!
So I installed the china ROM (12.5.2.0 QEACNXM) using mi flash, and I'm having similar issues. I did not get the "android setup stopped working", however WiFi is still not responding as before, and I got two "Security stopped working" and "Settings stopped working" errors.
Click to expand...
Click to collapse
Sorry, no other idea but that you try now again Xiaomi.eu 12.5, with Factory reset
zgfg said:
Sorry, no other idea but that you try now again Xiaomi.eu 12.5, with Factory reset
Click to expand...
Click to collapse
Got it, will try that, adn if it doesn't work I'll see whether I can do something else to fix this.
Anyway, thanks a lot!
Fjolfrin said:
Good morning!
So I installed the china ROM (12.5.2.0 QEACNXM) using mi flash, and I'm having similar issues. I did not get the "android setup stopped working", however WiFi is still not responding as before, and I got two "Security stopped working" and "Settings stopped working" errors.
Edit: WiFi cannot actually be turned on at all.
Click to expand...
Click to collapse
Btw, Bluetooth, NFC, GPS, do they work?
And first, not least, do SIM cards work (voice and mobile data)?
And did you try switching now from CN 12.5 back to Xiaomi.eu 12.5 (they are based on CN, but made to work internationally)
zgfg said:
Btw, Bluetooth, NFC, GPS, do they work?
And first, not least, do SIM cards work (voice and mobile data)?
And did you try switching now from CN 12.5 back to Xiaomi.eu 12.5 (they are based on CN, but made to work internationally)
Click to expand...
Click to collapse
I didn’t try these tbh, but I did go back to the 12.5 EU ROM.
This time I can get inside the phone normally, however Wi-Fi is still sketchy.
I managed to connect to a network, but manually, it still wont scan for network, and the connection is dropped after some minutes. I didn’t try gps, bt, or nfc, as I was trying to troubleshoot Wi-Fi, and this all came to a halt as the phone reboots on its own after 5-10 minutes of operation.