Related
I recently unlocked bootloader, so I installed Red Wolf Team Recovery. After that, I flashed MIUI 10 zip update via recovery and after restarting my phone, it got hard brick. I'm trying to flash 9.5.19 and 8.8.6 using Mi Flash but I get 'Can not receive hello packet' error and then 'timed out' error.
Drivers are installed. Tried with different ports but I get the same error. Also tried touching power on button but nothing changes.
Any way to solve it?
EDIT: Now I receive this error:
Only nop and sig tag can be recevied before authentication.
It seems that I need an authorized account for using MiFlash. Any alternative?
I don't have any type of Xiaomi Service Center in my country, only can contact to my reseller for guarantee but I don't know if its covered.
Search, read.. You have to hold power button for like 10s, not just touch it
Incogn said:
Search, read.. You have to hold power button for like 10s, not just touch it
Click to expand...
Click to collapse
Now I receive this error:
Only nop and sig tag can be received before authentication.
Edit: It seems that I need an authorized account to flash (tried with other version of Mi Flash). Where do I get it?
Literally half of this forum is filled with topics about this exact issue. Read around. Looks like you have ARB brick.
Which miui was there before you installed twrp?
UtkuAblak said:
Which miui was there before you installed twrp?
Click to expand...
Click to collapse
MIUI 9.5.17
Letrix said:
MIUI 9.5.17
Click to expand...
Click to collapse
long press power button fro 10-20 seconds . it will reboot. now hold down volume button during reboot to enter fastboot. if you can enter fastboot, your device is not arb bricked.
arunmohan16 said:
long press power button fro 10-20 seconds . it will reboot. now hold down volume button during reboot to enter fastboot. if you can enter fastboot, your device is not arb bricked.
Click to expand...
Click to collapse
It's hard brick. It doesn't do nothing. Only is recognized by PC as Qualcoom 9008 but now it's asking for authentication in my account. Is there any way to authorize my account?
Letrix said:
It's hard brick. It doesn't do nothing. Only is recognized by PC as Qualcoom 9008 but now it's asking for authentication in my account. Is there any way to authorize my account?
Click to expand...
Click to collapse
Mi authorized account is hard to get. check mi russian and english forums. sometimes they will open forum for collecting Mi account number for authorization. If you are in warranty, check service center and they will replace the motherboard.
arunmohan16 said:
Mi authorized account is hard to get. check mi russian and english forums. sometimes they will open forum for collecting Mi account number for authorization. If you are in warranty, check service center and they will replace the motherboard.
Click to expand...
Click to collapse
It's covered by guarantee? I'm from Argentina and the guarantee that I have received is a mandatory one for six months.
Install app ver. 2018.5.28 and try again , asks for user and pass.
You can ask for authorization in Russian forum miui.
Good luck
I wonder why did you installed redwolf recovery to flash miui10. Don't you know, you can flash miui10 using mi recovery??
SunilSuni said:
I wonder why did you installed redwolf recovery to flash miui10. Don't you know, you can flash miui10 using mi recovery??
Click to expand...
Click to collapse
Agreed: normally you flash/update your device via miflash (or OTA). Then you can flash RedWolf (for root) and enable an option for getting MIUI OTA updates.
What I wanted to say is, it's interesting how you got the hardbrick: reversing from ARB v.4 to v.4 or vice versa (v.3 to v.3) shouldn't be a problem whatsoever. Even if your firmware is on version v.4 (use fastboot getvar anti for your version) you shouldn't have any problems (at least with custom roms).
I'm still wondering how you got the hardbrick. I red pretty much every post here, maybe I have overlooked something.
SunilSuni said:
I wonder why did you installed redwolf recovery to flash miui10. Don't you know, you can flash miui10 using mi recovery??
Click to expand...
Click to collapse
I didn't know it in that moment.
the thing is you were on 9.5.17 which has arb version 3 and u were trying to install miui 10 dev rom which got arb version 4....so u shouldnt get arb brick at the first place...there is something wrong...were you flashing global dev over china stable?
sayedquadir said:
the thing is you were on 9.5.17 which has arb version 3 and u were trying to install miui 10 dev rom which got arb version 4....so u shouldnt get arb brick at the first place...there is something wrong...were you flashing global dev over china stable?
Click to expand...
Click to collapse
They never post what they did exactly all they post is their phone got bricked because of ARB and start bashing Xiaomi.
Thing is it's highly impossible to brick a device while switching from ARB 3 ROM to ARB 4 ROM and most of the people thinking as developers after watching some freaking useless YouTube video
SunilSuni said:
They never post what they did exactly all they post is their phone got bricked because of ARB and start bashing Xiaomi.
Thing is it's highly impossible to brick a device while switching from ARB 3 ROM to ARB 4 ROM and most of the people thinking as developers after watching some freaking useless YouTube video
Click to expand...
Click to collapse
It's called a mistake? and if it was any other phone then he could probably quite easily recover his phone in minutes. But no, the REASON why he is in this position is because of Xiaomi's stupid ass restrictions so yes. That's why we all bash Xiaomi because this bs they've done to our phones is they're fault. It's like trying to upgrade your cars radio, but you make a mistake so the car turns into a massive brick and you can't use it unless the manufacturer approves of it. But that could be weeks or never because the manufacturer is now poo'n all over its community that put them there in the first place
So, the summary is, if you followed a ROM update guide, which does not mention the issue, flashed the linked and wrong ROM version and bricked the phone, it is gone, unless a "service center" replaces the motherboard? That's beyond ridiculous, really.
And yeah, there are a million threads about the issue, and not a single coherent guide.
Hi! I'm new with this ARB stuff. But I've been doing some searching for a while. So I will ask some questions and please tell me if I'm wrong.
After waiting for almost 720 hrs. I really don't want to enter EDL Mode or take the phone to service center to unbrick.
- if any custom whyred miui rom is fw-less then it's should be fine to flash though TWRP to any whyred. no matter what version of ARB index is. Am I right?
- once got anti 4 mean there's no way to remove ARB at this moment?
- when entered fastboot. Is it still have to re-flash TWRP?
- Pitch Black TWRP fixed all of above? and I can use it worry free like there's no ARB at all?
Vermillion_PT.2 said:
Hi! I'm new with this ARB stuff. But I've been doing some searching for a while. So I will ask some questions and please tell me if I'm wrong.
After waiting for almost 720 hrs. I really don't want to enter EDL Mode or take the phone to service center to unbrick.
- if any custom whyred miui rom is fw-less then it's should be fine to flash though TWRP to any whyred. no matter what version of ARB index is. Am I right?
Yes, but you might have to use lazyflasher as you probably have ARBv4 already.
- once got anti 4 mean there's no way to remove ARB at this moment?
Yes, as far as I know.
- when entered fastboot. Is it still have to re-flash TWRP?
The first time? What do you mean "reflash", if you have never unlocked your phone, how come you would have TWRP?
- Pitch Black TWRP fixed all of above? and I can use it worry free like there's no ARB at all?
Click to expand...
Click to collapse
I also don't understand...Oh you are talking about a different "recovery" (https://sourceforge.net/projects/pitchblack-twrp/).
You can use the other recovery without problem too (TWRP, OrangeFoxRecovery, RedWolf Recovery Project ...).
Any recovery won't "fix all of the above", it's just a recovery, you need to be carefully with ARB and it's not "fixing" ARB.
It seems more clever if you would post the steps you intend to do, rather than ask several questions and then mentionning a recovery as a possible "fix all".
Replied.
Oh ok. I mean do I have to re-flash the dummy.img. everytime entered fastboot.
I heard that Pitchblack TWRP can handle ARB perfectly. But don't know about re-flash dummy.img if it still an issue.
Thank you for your reply anyway!
Vermillion_PT.2 said:
Oh ok. I mean do I have to re-flash the dummy.img. everytime entered fastboot.
I heard that Pitchblack TWRP can handle ARB perfectly. But don't know about re-flash dummy.img if it still an issue.
Thank you for your reply anyway!
Click to expand...
Click to collapse
I think you do need to reflash dummy.img (thats related to layflasher, right) each times due to ARBV4.
Maybe "pitchblack" does these steps for you, I am not familiar with that one,.
Why don't you rely on MiFlash ?? It is the best option flash MIUI ROM because MiFlash is capable of checking bootloader index value before proceeding with fastboot flash..
If you try to flash older version of miui (arb3) then MiFlash will not allow to flash that particular ROM
One of the user here said pitch black recovery is capable of checking bootloader index but I'm not sure about that..
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?
I have a Ginkgo model which I am using with LineageOS 17.1 / TWRP. It is pretty cool.
However I want to return completely to the Global (EU) version of the software, including stock recovery, ROM, relocked bootloader, anything, because I am willing to sell the phone.
Next user will be average user, unlike me, so he/she won't appreciate any modifications.
Tried to search for suggestions but no luck.
Before installing LoS, I installed Xiaomi.EU 12.5 stable from here: https://xiaomi.eu/community/threads/miui-12-0-12-1-12-2-12-5-stable-release.56191/
Could have some relevance like firmware partition, etc. AFAIK it is Chinese ROM based, will that make any problems when I re-flash EU version?
Found this one: https://forum.xda-developers.com/t/how-to-completely-revert-back-to-stock.4088665/
But before trying and possibly bricking the phone, I'd like to hear some encourage from you guys. Phone was EU version originally.
Many thanks.
HUN_Gyuszi said:
I have a Ginkgo model which I am using with LineageOS 17.1 / TWRP. It is pretty cool.
However I want to return completely to the Global (EU) version of the software, including stock recovery, ROM, relocked bootloader, anything, because I am willing to sell the phone.
Next user will be average user, unlike me, so he/she won't appreciate any modifications.
Tried to search for suggestions but no luck.
Before installing LoS, I installed Xiaomi.EU 12.5 stable from here: https://xiaomi.eu/community/threads/miui-12-0-12-1-12-2-12-5-stable-release.56191/
Could have some relevance like firmware partition, etc. AFAIK it is Chinese ROM based, will that make any problems when I re-flash EU version?
Found this one: https://forum.xda-developers.com/t/how-to-completely-revert-back-to-stock.4088665/
But before trying and possibly bricking the phone, I'd like to hear some encourage from you guys. Phone was EU version originally.
Many thanks.
Click to expand...
Click to collapse
Follow this guide
and don't relock the bootloader
loopypalm said:
Follow this guide
and don't relock the bootloader
Click to expand...
Click to collapse
Thank you so much. It means I must not relock the bootloader? This is pretty sad because then I cannot guarantee 100% factory software. Buyer for my phone will complain. No chance to reach factory software 100%?
HUN_Gyuszi said:
Thank you so much. It means I must not relock the bootloader? This is pretty sad because then I cannot guarantee 100% factory software. Buyer for my phone will complain. No chance to reach factory software 100%?
Click to expand...
Click to collapse
it will brick the phone and your only way to fix it is EDL
I am happy to update the thread with good results.
Please note that the following are my personal experience described, I cannot guarantee anything and you might get a bricked phone. Please dont blame me if anything goes wrong!
Originally my phone was Global/EEA, and I had Xiaomi.EU and LineageOS 17.1 also this year. After this, I successfully reverted to complete factory software, including relocking the bootloader. This is necessary if you want to sell your phone to other people because they dont need custom ROMs and will complain.
First, go to this link: https://c.mi.com/oc/miuidownload/detail?guide=2
(make sure to follow the 'Fastboot Update' guide on this link!)
On Step 1, click on the link to download the Flash tool.
On Step 2, select your proper device (mine was 'Xiaomi Redmi Note 8 Latest EEA Stable Version Fastboot File Download'). I think region (like Chinese, Global/EEA) is hardcoded to the phone, so you cannot flash Global ROM to a Chinese phone, but please fix me. Pay attention what you select here.
Once both files are downloaded, extract them (you can use 7-zip).
Put your phone to fastboot mode.
Connect your phone with USB cable to your Windows machine. Start the flash tool, make sure to run it as admin. AFAIK it will present a dialog to install the necessary drivers which is needed to communicate with the phone in fastboot mode, just click OK for that.
Check if your phone is present in the list. On the left bottom side, click on 'clean all and lock'. Select the extracted directory of the fastboot ROM you downloaded. Press the flash button.
Wait for a few minutes. Your phone will boot up with original MIUI ROM.
You might also check logs. You need to have a ton of fastboot commands and a successful locking at the end.
Important notes: flash chinese ROM for chinese phone, global or eea for european/global phones. You can only relock your bootloader using the proper region.
Good luck anyone reading this!
Hi
I have Mi 10T 5G
I update it and the system crashed every time I powered on it's show me (the system has been destroyed)
nothing work only fastboot
no I can't flash firmware via Mi flash via fasboot it's show me (erase is not alloed in Lock state)
I tried to use Miflash unlock to unlock bootloader but I can't it's showed me this (please add your account in Mi account)
what could I do now?
Thanks
First of all: stay calm and don't randomly try things in panic mode, that usually makes it worse. Detail your problem a bit further, explaining all steps that lead to the bootloop. You still have fastboot, that's a good start. Breathe
Timmmmaaahh! said:
First of all: stay calm and don't randomly try things in panic mode, that usually makes it worse. Detail your problem a bit further, explaining all steps that lead to the bootloop. You still have fastboot, that's a good start. Breathe
Click to expand...
Click to collapse
No No I'm not panic but I tried everything but the same
this mobile for my friend al last he told me that he root it when I update the system that waht happened to me
and now I think must use test point
IRAQIGHOST said:
No No I'm not panic but I tried everything but the same
this mobile for my friend al last he told me that he root it when I update the system that waht happened to me
and now I think must use test point
Click to expand...
Click to collapse
Have you tried flashing official firmware images? I'm not really familiar with Xiaomi but it shouldn't require a bootloader unlock. In any case it should be covered under warranty if you don't want to go too deep down the rabbit hole...
Timmmmaaahh! said:
Have you tried flashing official firmware images? I'm not really familiar with Xiaomi but it shouldn't require a bootloader unlock. In any case it should be covered under warranty if you don't want to go too deep down the rabbit hole...
Click to expand...
Click to collapse
Yes, I used an official firmware from Xiaomi This baffles me, why does he want to unlock the bootloader if it is official?
Timmmmaaahh! said:
Have you tried flashing official firmware images? I'm not really familiar with Xiaomi but it shouldn't require a bootloader unlock. In any case it should be covered under warranty if you don't want to go too deep down the rabbit hole...
Click to expand...
Click to collapse
Yes, I used an official firmware from Xiaomi This baffles me, why does he want to unlock the bootloader if it is official?