Related
Hi,
I was flashing the handset without backup the NVRAM, and now the phone part is dead. He says "No Service". Can someone help me by sending the NVRAM backup of KS20 in the LGMDP backup format (.nv2) or in NVEditor format. I can restore the original IMEI of my phone.
Thanks in advance!
_Hamlet said:
Hi,
I was flashing the handset without backup the NVRAM, and now the phone part is dead. He says "No Service". Can someone help me by sending the NVRAM backup of KS20 in the LGMDP backup format (.nv2) or in NVEditor format. I can restore the original IMEI of my phone.
Thanks in advance!
Click to expand...
Click to collapse
Hi, have you never heard about "Duplicate Threads"??? this is THE 5th THREAD you OPEN about nv restoring "problem"!!!!
http://forum.xda-developers.com/showthread.php?t=417279
http://forum.xda-developers.com/showthread.php?t=413889
http://forum.xda-developers.com/showthread.php?t=415496
http://forum.xda-developers.com/showthread.php?t=415404
http://forum.xda-developers.com/showthread.php?t=411528
People already said that it was your fault if you can't use your bricked phone... The instructions to flash say many many many times to BACKUP YOUR NV2 before flashing!!! Couldn't you read that f*****g instructions??? Nobody will solve your problem...and please STOP opening new threads about the same issue!
so, try flash your handset with KS20-00-V10b-CIS-xx-FEB-14-2008 and then try to backup NVRAM. Regards
_Hamlet said:
so, try flash your handset with KS20-00-V10b-CIS-xx-FEB-14-2008 and then try to backup NVRAM. Regards
Click to expand...
Click to collapse
I've already done a backup of my nv2 file and restored correctly with each ROM I've tried since now. nv2 fiel by other users can't be helpful and , again, nobody can help you if you couldn't read simple steps to flash your phone.
an backup of NVRAM from any LG KS20 handset can help me 100%, be sure. A and you can't backup your NVRAM, if the KS20-00-V10b-CIS-xx-FEB-14-2008 flash presents in your handset 100%, be sure too. The phone is not detected by LGDMP in normal mode(only emergency mode), and nor copiing windiag.dll to windows directory, nor correcting the rgeistry do'nt solve this problem!!!
_Hamlet said:
an backup of NVRAM from any LG KS20 handset can help me 100%, be sure. A and you can't backup your NVRAM, if the KS20-00-V10b-CIS-xx-FEB-14-2008 flash presents in your handset 100%, be sure too. The phone is not detected by LGDMP in normal mode(only emergency mode), and nor copiing windiag.dll to windows directory, nor correcting the rgeistry do'nt solve this problem!!!
Click to expand...
Click to collapse
Are you making fun of me ? Do you know what the nv2 file is for??? Why should I give you my nv2 which contains MY IMEI, MY Bluetooth and Wi-fi addrees, MY brand infos ??? IF there's no service maybe you only need to unlock your phone (see the Thread about it).
You listened about NVEditor? then you can remove any sensitive data. I need only calibration data for radio!
All rom can communicate with LGDMP, with some rom you just need some more steps but nothing very difficult ...
DomZ said:
All rom can communicate with LGDMP, with some rom you just need some more steps but nothing very difficult ...
Click to expand...
Click to collapse
Is there that steps a big secret, or you can tell us about that?
it is 100% our fault that we killed our devices.but we are desperate.and we know that if the guys in this forum have not the answer, there is no answer.
The first step is done.
what do you mean?
did u find a solution?
Can u find any nv2 file? Give me it and i give you solution for your handset.
i don't that file.i have the same problem with you.did you repair the signal?
To everyone,
If u need .nv2 file, pm me with ur imei no. and email address, i can generate one for you, but the last digit, which is calculated by your phone, would likely to be different and also i can only generate branded .nv2 since i only got branded .nv2 file. It could be work in unbranded phone but just u need to flash a branded rom or hybrid rom to use with it.
a big big big big big big big big big big big big big big big thanks to raykisi.my phone after 20 days is back to life again.many many thanks man you are the best.
same problem
_Hamlet said:
The first step is done.
Click to expand...
Click to collapse
I got the same problem, would you like to help?
thanks a lot!
it is so unlucky that many guys got wrong flashing method from different place, so need help from here, we also know it is 100% our fault that we killed our devices, thanks if can help, please don't angry with our dumb
i've got 3 units of ks 20,i flashed all of them and restore with the same nvram, guess what??
its works man, 3 different unit can use the same nvram. so, anyone who lost their nvram, i can give for free.
Dear Android experts in this huge & helpful forum
I have the big common problem related to EFS folder:crying:
When i received my note 2 (international) after my pervios mobile Galaxy S2 (which i have tried with it several roms without a problem), i wasn't aware about the EFS folder problem and IMEI and ..... so on.
After trying first rom without backing up my EFS, unfortunately i corrupt my IMEI and lost network and after 2 days search and trying nothing solve it until i went to private fix center which fixed it.
After the fix i make a backup the EFS with many backup tools on the forum and i was happy that i will be able try roms as i hope, but i found the truth was not :crying::crying:, every time i install any of the custom roms i keep have the (Out of service ) network problem.
The problem that i found that the IMEI number is right but serial number is 00000000, also the network name is right and signal is strength is displayed , but still (out of service).
I can fix the phone with only one way (install stock rom + Ariza patch) but when i use the same patch with the the custom rom it makes every thing unknown (IMEI,.......).
When i install the modem XXDME4 it solve the problem for unknown IMEI and unknowns but still the out of service problem :crying::crying:
Please anybody can help me in this bad problem?
Waiting your help please!
r u there guys? :crying:
So, if i reset flash counter and un-root the device but the IMEI still dynamic (as 0040056545) would they accept it??
I check from download mode that the counter is 0 and shows that the rom is official
Please Advice before the end of this year
Thanks for your support
Last support hope....if i backup the EFS after receive from Samsung service center, would i be able to install custom roms??
Thanks all for too much help, please remove the thread
hi all
after installing custom ROM my phone imei has been changed so i am not able to make calls
and i am getting error message that says "not registered on network" I searched about that issues and found that changing imei may cause that problem so anyone can help me to restore original imei for my phone
the below youtube show steps to do it but my problem that am not able to access engineering mode
https://www.youtube.com/watch?v=VNGalucyFJc
please HELP ME !
do you have a backup of your EFS? if you have, follow what i did here.
http://forum.xda-developers.com/showthread.php?t=2055736&page=352
but i suggest you only do it IF you have a backup of your EFS. otherwise, it's up to you.
edong23 said:
do you have a backup of your EFS? if you have, follow what i did here.
http://forum.xda-developers.com/showthread.php?t=2055736&page=352
but i suggest you only do it IF you have a backup of your EFS. otherwise, it's up to you.
Click to expand...
Click to collapse
ah, no i don't have backup for EFS, :crying: what must i do?
ghost_j1 said:
ah, no i don't have backup for EFS, :crying: what must i do?
Click to expand...
Click to collapse
try flashing your official firmware through Odin. other users solve their imei problem by doing that. see also if you can access engineering mode with that official firmware.
edong23 said:
try flashing your official firmware through Odin. other users solve their imei problem by doing that. see also if you can access engineering mode with that official firmware.
Click to expand...
Click to collapse
i tried to flash it with an official firmware but thats does not help the imei still wrong and i am not able to access engineering mode too
any other suggestion or anyone can help
ghost_j1 said:
i tried to flash it with an official firmware but thats does not help the imei still wrong and i am not able to access engineering mode too
any other suggestion or anyone can help
Click to expand...
Click to collapse
lets wait for others specially those who are expert in android for some advice. I'm just an ordinary security guard so i can't help you much with your problem. what i have suggested you from my previous post was the last thing I did when my phone finally worked. for 4 days i been searching for solution because i also have an IMEI problem. i flash back to official rom, flash patched modem, flash other roms to no avail until such time when my phone doesn't boot because of broken partition :laugh:. if you still have warranty restore it back. if you're already out of warranty and you have money, you can it send it to service center.
P.S.
you can also try this if you have courage. i was able to make some secret codes work but i have'nt tried if it works with engineering mode by modifying hiddenmenu in /efs/carrier/hiddenmenu. use efs explorer to open hiddenmenu and change it to ON.save it and restart your phone and see if engineering mode work. remember that you have to be in official firmware and also rooted to do this. if its not working then you'll just have to wait for a much better solutions from devs.
Same question
I have the same problem, as owner of the thread. Any help?
"CF Auto root" after imei has been deleted. you have installed the fix: http://forum.xda-developers.com/showthread.php?t=2333216
Hi, I'm begging you all for help.
Please, even if you don't know the answer, share any sort of advice.
I'm not a newbie (25+ years story of Unix/Reversing), but I know nothing about radio.
Here's a list of symptoms:
1) Sometimes the WIFI MAC Address comes up as 02:00:00:00:00:00 and IMEI isn't available, then they both magically come up (without rebooting, after the SIM Is read - see n. 2)
2) It keeps powering ON & OFF the SIM and switching between Connected , No Signal , Emergency. Sometimes taking the SIM out & back in helps. Selecting the Preferred Network Type from the modem debug screen keeps it connected for long periods.
3) It won't search for alternative networks to Register Manually
3) IMS Registration is showing as Not Registered always, even while it's connected: Voice + Data (?!?)
4) From the Debug Info only 1 cell appears as SRV = R+N and has a CELL ID, so it seems it connects only to 1 cell at a time.
I can't post screenshots as I lost my old username here, so I signed-up again.
Nothing works, it was a new phone. I wanna die.
Thank you all for your help.
Thanks.
I have problems with modem and camera wgen updating ta android 9.
I would recomend you to rollback to 10.2.1.0
I would use this method
1. Backup your media files to your computer
2. Unlock bootloader
3. Download fastboot china version of 10.2.1.0 and Flash it with mi flash (choose wipe but dont lock!)
4. Flash orange fox twrp with fastboot
5 wipe all partitions exvept internal storage with orangefox
6. Download 10.2.1.0 from xiaomi.eu and flash it with orangefox
Tell me is you want direct links to all files that you need.
If you still have problems after downgrading I can prove my persist and modem files
Good luck
eliaztheone said:
I would recomend you to rollback to 10.2.1.0
Click to expand...
Click to collapse
@eliaztheone thank you for your reply and your offer about the files, I'll take it if necessary.
Just one question: won't that trigger Anti-Rollback ?
(I don't need to stay on MIUI: do I have other options?)
DoYouWantFriesWithThat said:
@eliaztheone thank you for your reply and your offer about the files, I'll take it if necessary.
Just one question: won't that trigger Anti-Rollback ?
(I don't need to stay on MIUI: do I have other options?)
Click to expand...
Click to collapse
Your anti rollback is already triggered on 4. Thats the arb value on 10.2 too. As long as you dont flash older miui 9 firmware you should be ok...
eliaztheone said:
Your anti rollback is already triggered on 4. Thats the arb value on 10.2 too. As long as you dont flash older miui 9 firmware you should be ok...
Click to expand...
Click to collapse
The roll-back went well but the phone is still unstable.
I'm not sure why: did the Persist get corrupted? Or the EFS partition? I have some backups but I'm not sure what to do.
Can you provide the files that you mentioned, or maybe some pointers?
What could be wrong with the phone?
Thanks a lot @eliaztheone
DoYouWantFriesWithThat said:
The roll-back went well but the phone is still unstable.
I'm not sure why: did the Persist get corrupted? Or the EFS partition? I have some backups but I'm not sure what to do.
Can you provide the files that you mentioned, or maybe some pointers?
What could be wrong with the phone?
Thanks a lot @eliaztheone
Click to expand...
Click to collapse
I can give you my efs and persist backup if you want? Then you can use partitions backup and restorev from playstore.
You need to be rooted with magisk to restore
Are you on the xiaomi.eu version of 10.2.1.0 and is it the 8.1 version or 9.0?
eliaztheone said:
I can give you my efs and persist backup if you want? Then you can use partitions backup and restorev from playstore.
You need to be rooted with magisk to restore
Are you on the xiaomi.eu version of 10.2.1.0 and is it the 8.1 version or 9.0?
Click to expand...
Click to collapse
I am on Xiaomi.eu 10.2 with Android 9 now, as you suggested. Rooted & with Magisk.
I have backups of my old PERSIST from the China 9.x ROM. Should I flash that (or do I risk bricking) ?
I was reading on persist.img and I don't understand one thing: if it's different for every phone, why there's a persist.img in every Fastboot ROM ?
EDIT: I flashed my old Persists (tried various ones), and the problem.....persists! :') lol
So I'm back to my most recent Persist and still in need for help.
PS: if it helps for a diagnosis, any time the modem resets the SIM it dumps a lot of logs in /ramdump
DoYouWantFriesWithThat said:
I am on Xiaomi.eu 10.2 with Android 9 now, as you suggested. Rooted & with Magisk.
I have backups of my old PERSIST from the China 9.x ROM. Should I flash that (or do I risk bricking) ?
I was reading on persist.img and I don't understand one thing: if it's different for every phone, why there's a persist.img in every Fastboot ROM ?
EDIT: I flashed my old Persists (tried various ones), and the problem.....persists! :') lol
So I'm back to my most recent Persist and still in need for help.
PS: if it helps for a diagnosis, any time the modem resets the SIM it dumps a lot of logs in /ramdump
Click to expand...
Click to collapse
Sorry I was not clear with my guide.. You needed to flash the android 8.1 version of 10.2.1.0 . I guess that wont help either but maybe so try it..
Try it and if it does not work. I will make backup of my persist and efs and modem and send them to you and after that u need to change to your imei numbers with qualcom app..
eliaztheone said:
Sorry I was not clear with my guide.. You needed to flash the android 8.1 version of 10.2.1.0 . I guess that wont help either but maybe so try it..
Try it and if it does not work. I will make backup of my persist and efs and modem and send them to you and after that u need to change to your imei numbers with qualcom app..
Click to expand...
Click to collapse
I tried it following this guide to restore the Persist partition (https://forum.xda-developers.com/xi...guide-restoring-persist-partition-to-t3906424 - via Fastboot, not EDL) , and right after flashing the SIM was working fine on 4G/LTE and the phone didn't present any problems.
Then I opened up Google-Maps and gave it permission to read the GPS and it went crazy: not reading the SIM anymore, rebooting, etc. And turning GPS off now won't help. So I guess the problem is with the Modem and the fact that it connects to only 1 Cell - no idea why.
@eliaztheone
eliaztheone said:
Sorry I was not clear with my guide.. You needed to flash the android 8.1 version of 10.2.1.0 . I guess that wont help either but maybe so try it..
Try it and if it does not work. I will make backup of my persist and efs and modem and send them to you and after that u need to change to your imei numbers with qualcom app..
Click to expand...
Click to collapse
I am on 10.2.1.0 - Android 8.1 now. In addition to what you suggested I restored the persist.img via Fastboot (not EDL) following this guide on XDA .
Right after flashing the phone didn't present any problems (SIM/4G was working without hiccups). As I opened up Google-Maps and gave it permission to read the GPS it went crazy: not reading the SIM anymore, rebooting, etc. Turning GPS off now won't help, it constantly reboots - I have to use Airplane Mode.
So I guess the problem is still in the Modem. Maybe it's the fact that it connects to only 1 Cell, apparently.
@eliaztheone if you can provide the files I'll try one last time. Thank you.
I will upload them tonight hopefully. You need to be on 10.2.1.0 oreo xiaomi.eu version.
You also need to be rooted with magisk so you can restore them with partition backup and restore
---------- Post added at 07:33 PM ---------- Previous post was at 07:28 PM ----------
Did you try to flash modem_fix_ysl.zip? It resets the modem.img and modemst1.img and modemst2.img
Take your time, thank you.
While inspecting the ramdump I noticed the following:
[ 21.864464] [c:1] [p:<003975, android.vending>] Fatal error on the modem.
[ 21.864522] [c:1] [p:<003975, android.vending>] modem subsystem failure reason: rflm_diag_error.cc:361:[email protected]_qlnk.cpp:1090 [9,3] RF stuck in QLINK start s.
[ 21.864530] [c:1] [p:<003975, android.vending>] subsys-restart: subsystem_restart_dev(): Restart sequence requested for modem, restart_level = RELATED.​
There's many SELinux odd log entries too, not sure if that's normal. When I disabled SELinux from the terminal the 4G immediately picked up...totally weird
eliaztheone said:
[/COLOR]Did you try to flash modem_fix_ysl.zip? It resets the modem.img and modemst1.img and modemst2.img
Click to expand...
Click to collapse
I'll try to flash it, thank you.
I am on 10.2.1.0 oreo xiaomi.eu. Do you think it makes sense to try a custom ROM ?
Thank you.
EDIT:
- I flashed modem_fix_ysl.zip but it didn't have any effect.
- I find the ramdumps from the china ROM much cleaner and errorless than the Xiaomi.eu ROM, just saying
I have sent you a pm
Have you guys found a solution? I have the exactly same problem on Mi Max 3 4/64Gb version. I'm on MIUI Global Stable 10.3.5.0. I was on China stable and had issues,so i flashed Global Stable fastboot rom using Mi Flash Tool(flash all option),and It doesn't solve the problem.I have unlocked bootloader,and no previous system backup.
Also i tried flashing NON-HLOS.bin file from Global Stable fastboot ROM using command : fastboot flash modem NON-HLOS.bin
Also i tried something that worked on my old redmi 4,after NON-HLOS.bin flash,executed fastboot commands :
fastboot erase modemst1 and modemst2,but no luck because of "partition is write protected" error.
Have you found what's the cause of this problem?Is it hardware?Is it corrupted modem files?Will custom rom solve it? Please, any help,any suggestion will be appreciated. I'll try everything to fix it. Thank you in advance.
@ghost baby
I tried the following:
- reflashing Global ROM
- flashing Xiaomi.eu ROM as per instructions of of Eliaztheone
- restoring a backup of old China ROM
- reflashing China ROM
- analyzing the ramdumps (memory dumps & system/radio-modem logs)
- EDL flashing (with `fastboot oem edl` - not with the deep-flash cable)
All the reflashes included overwriting the EFS (modemst1/2) & PERSIST partitions, automatically (in bulk) or manually, taken from various sources including those that Eliaztheone kindly sent to me. The EDL flashing didn't work because I had no authorization on my Xiaomi account (I've tried all combinations of SDR programmers & old versions of MiFlash - none works) so I've then tried to get a remote authorization, also without success: the guy from UNBRICK.RU told me that Xiaomi revoked all authorizations lately to push out of business the remote-auth-flashers.
From my understanding of the ramdumps the problem seems to be an internal modem fault. Since ARB wasn't triggered when I rolled back to China ROM, I suspect that the fault is a hardware (or very low-level SW) software in the radio modem, and so it can be maybe fixed only by EDL flashing.
That's why I resorted to finding a local authorized service center this week. But I have to see how much money they ask me: if they ask too much I might as well buy a new OPPO or REALME phone, which are cheap & open (at least more than ****ty Xiaomi). If the service center pisses me off you'll see the result in the news.
Support the right to repair movement.
I hope this helps.
DoYouWantFriesWithThat said:
@ghost baby
I tried the following:
- reflashing Global ROM
- flashing Xiaomi.eu ROM as per instructions of of Eliaztheone
- restoring a backup of old China ROM
- reflashing China ROM
- analyzing the ramdumps (memory dumps & system/radio-modem logs)
- EDL flashing (with `fastboot oem edl` - not with the deep-flash cable)
All the reflashes included overwriting the EFS (modemst1/2) & PERSIST partitions, automatically (in bulk) or manually, taken from various sources including those that Eliaztheone kindly sent to me. The EDL flashing didn't work because I had no authorization on my Xiaomi account (I've tried all combinations of SDR programmers & old versions of MiFlash - none works) so I've then tried to get a remote authorization, also without success: the guy from UNBRICK.RU told me that Xiaomi revoked all authorizations lately to push out of business the remote-auth-flashers.
From my understanding of the ramdumps the problem seems to be an internal modem fault. Since ARB wasn't triggered when I rolled back to China ROM, I suspect that the fault is a hardware (or very low-level SW) software in the radio modem, and so it can be maybe fixed only by EDL flashing.
That's why I resorted to finding a local authorized service center this week. But I have to see how much money they ask me: if they ask too much I might as well buy a new OPPO or REALME phone, which are cheap & open (at least more than ****ty Xiaomi). If the service center pisses me off you'll see the result in the news.
Support the right to repair movement.
I hope this helps.
Click to expand...
Click to collapse
Thank you man, I'll try everything you said tommorow. The device hardware is awesome,and i really want to support xiaomi,only if they had solution for this problem. Also i think keeping ARB on unlocked bootloader is a bad decision,it really makes this whole process harder.
I'm hoping you get you phone fixed and looking forward to see how this will end.
Thanks for helping me man.
(Sorry for bad English)
---------- Post added at 10:35 PM ---------- Previous post was at 10:33 PM ----------
Maybe someone's QCN file can help us?
DoYouWantFriesWithThat said:
@ghost baby
I tried the following:
- reflashing Global ROM
- flashing Xiaomi.eu ROM as per instructions of of Eliaztheone
- restoring a backup of old China ROM
- reflashing China ROM
- analyzing the ramdumps (memory dumps & system/radio-modem logs)
- EDL flashing (with `fastboot oem edl` - not with the deep-flash cable)
All the reflashes included overwriting the EFS (modemst1/2) & PERSIST partitions, automatically (in bulk) or manually, taken from various sources including those that Eliaztheone kindly sent to me. The EDL flashing didn't work because I had no authorization on my Xiaomi account (I've tried all combinations of SDR programmers & old versions of MiFlash - none works) so I've then tried to get a remote authorization, also without success: the guy from UNBRICK.RU told me that Xiaomi revoked all authorizations lately to push out of business the remote-auth-flashers.
From my understanding of the ramdumps the problem seems to be an internal modem fault. Since ARB wasn't triggered when I rolled back to China ROM, I suspect that the fault is a hardware (or very low-level SW) software in the radio modem, and so it can be maybe fixed only by EDL flashing.
That's why I resorted to finding a local authorized service center this week. But I have to see how much money they ask me: if they ask too much I might as well buy a new OPPO or REALME phone, which are cheap & open (at least more than ****ty Xiaomi). If the service center pisses me off you'll see the result in the news.
Support the right to repair movement.
I hope this helps.
Click to expand...
Click to collapse
Maybe someone's QCN file can help us?[/QUOTE]
All authorizations has been locked down for a while now, learned that the hard way during in the early days of ARB4 and i tried to flash a stable rom with a lower ARB number and my phone bricked. IThen i found someone to flash a beta rom by remote with authroization; costed me 15 USD. EDL flash was the only way if you still have fastboot. I worked with the service guy because he also wants to figure out the problem also. After bricking my device 4 times, I got the right recovery to use and then TWRP Recovery worked for the 4GB version. I got the 6GB version also and the people who sold me the phone had already unlocked the bootloader, I had to double check to see using command prompt. The i flashed the Recovery i was given to by a user on the AOSiP thread, thinks its Page 7, its a TWRP CN Recovery.. and it worked in both devices.
@Wmateria can you give me the contact of this person who gave you the remote Auth ?
I just phoned Xiaomi and they told me that Xiaomi's warranty is only valid at national level (read: each european country collects phones sold on its territory, and sends them to specific labs).
Wmateria said:
Maybe someone's QCN file can help us?
Click to expand...
Click to collapse
The QCN won't help cause we can't access EDL anyway even via QFIL.
If anyone has a contact for remote Auth, I'd appreciate if he/she could share it.
Thanks.
DoYouWantFriesWithThat said:
@Wmateria can you give me the contact of this person who gave you the remote Auth ?
I just phoned Xiaomi and they told me that Xiaomi's warranty is only valid at national level (read: each european country collects phones sold on its territory, and sends them to specific labs).
The QCN won't help cause we can't access EDL anyway even via QFIL.
If anyone has a contact for remote Auth, I'd appreciate if he/she could share it.
Thanks.
Click to expand...
Click to collapse
I found some article that shows how to flash QCN file form DIAG mode,and how to enter that mode. I'll try and keep you updated.
Wmateria said:
Maybe someone's QCN file can help us?
Click to expand...
Click to collapse
All authorizations has been locked down for a while now, learned that the hard way during in the early days of ARB4 and i tried to flash a stable rom with a lower ARB number and my phone bricked. IThen i found someone to flash a beta rom by remote with authroization; costed me 15 USD. EDL flash was the only way if you still have fastboot. I worked with the service guy because he also wants to figure out the problem also. After bricking my device 4 times, I got the right recovery to use and then TWRP Recovery worked for the 4GB version. I got the 6GB version also and the people who sold me the phone had already unlocked the bootloader, I had to double check to see using command prompt. The i flashed the Recovery i was given to by a user on the AOSiP thread, thinks its Page 7, its a TWRP CN Recovery.. and it worked in both devices.[/QUOTE]
Did EDL flash solved the problem?
Hello guys,
So, I'm having a big problem with my Mi 11 lite, I was updating the miui for the new version but my phone discharged the battery during the process, so when I turn it on again I just could see a screen with three options: "Reboot" "Wipe data" and "Conect to Mi assistant". What can I do to save my phone?
My bootloader it's locked and I didn't have created a Mi Account, is there any way to fix it? How to reinstall the stock rom in this case?
I sent my phone to four technical assistance but no one could help, and one of these said he has to buy a software which cost about 500$ to fix it, but I though something was wrong cause I never heard about a paid Mi software for recovery with that price. If someone can help me, please, do it, I really need help! Thanks!
First of all, you did a mistake updating your device while it is low on energy.
The screen you are facing is recovery mode, which is a very good sign, at least your device did not hard-brick.
You can simply download a firmware of your region and flash it, and that's all. Please don't ask where to download firmware or which version. Also, it does not require your bootloader to be unlocked. It is preferred that you flash fastboot ROM, I don't know about Windows, but it is guaranteed on Linux.
You probably won't lose your data/apps, but in the worst case you'll have to format data.
Hello, also here. After updating to latest Update i just came into recovery and cannot boot anymore.
It was not on low energy F*** Xiaomi!!