Develop Bugs

P601 second hand MDM locked

hi everyone,
bought myself a second handed p601 for a really nice price, from a former employee of Sky (Sky TV). This tablet used to be a sales unit, and it´s completely locked up by administrative tools. at first, I thought I would simply factory reset it, and all would be ok. But got "MDM does not allow factory reset | rebooting" message. So I flashed it with P601UBUCNL1_P601ZTOCNL1_P601UBUCNE1 (official 4.4.2 ZTO), but still same problem. Rooted it with CF-Auto-Root tried Aroma FM to erase mdm data, still no luck, flashed TWRP recovery (twrp-2.8.7.0-lt03ltexx-4.4.img.tar) so I could format /data and /system to write P601UBUCNL1_P601ZTOCNL1_P601UBUCNE1 again, but recovery won´t start!
so got myself locked up with a tablet that can only access main screen, can´t even open settings, or connect to any wifi network. adb is disabled, mtp is disabled, only connection is has while it´s on, it´s samsung modem (no modem usb port or diagnostics port). I can enter download mode, and flash it, but /data is not erased. as I can´t backup efs/qcn/cert, got kind of afraid of trying more agressive measures, and end up with bricked device or, kill baseband.
can anyone help? thnx in advance.

just to include:
- flashed philz touch recovery, also cannot load. after flashing it with 'auto reboot' unticked, only samsung logo when entering recovery
- re-rooted it and then flashed official rom again, still the same
- flashed cm12 custom rom, it powers up with a lot of errors, and still can´t factory reset it (same error) and can´t format /data or /system (not allowed error)
starting to think that was a bad idea to buy this device...

up on this... still couldn´t figure out what to do...

vazgsm said:
up on this... still couldn´t figure out what to do...
Click to expand...
Click to collapse
any luck man? I'm in the same boat

Yes, but was a real pain in the @ss... Used SPT Box to flash with repartition, then resetted EFS, and flashed again, it did turn on with corrupted security (you can do that with odin if you get proper .pit file). Installed cwm recovery, but now it worked. From there, formatted all partitions, and flashed rom again. Right after flashing ROM, tried factory reset again, and it worked! Used z3x to rebuild security and repair imei and sn, it seemed ok, but no signal. Got a .qcn file for it in gsmhosting, and wrote it too. Now it´s working fine, as it had never been mdm locked.
I used gsm boxes to do it, don´t know if there are free software to do that. Eventually I found out another way, with riff box. You can read a working p601 and generate image file, which can be flashed into another unit (riff works via jtag, and after you need to repair imei/security, and flash rom again). It should have some other way, simpler, but I couldn´t find, and couldn´t get help anywhere.

vazgsm said:
Yes, but was a real pain in the @ss... Used SPT Box to flash with repartition, then resetted EFS, and flashed again, it did turn on with corrupted security (you can do that with odin if you get proper .pit file). Installed cwm recovery, but now it worked. From there, formatted all partitions, and flashed rom again. Right after flashing ROM, tried factory reset again, and it worked! Used z3x to rebuild security and repair imei and sn, it seemed ok, but no signal. Got a .qcn file for it in gsmhosting, and wrote it too. Now it´s working fine, as it had never been mdm locked.
I used gsm boxes to do it, don´t know if there are free software to do that. Eventually I found out another way, with riff box. You can read a working p601 and generate image file, which can be flashed into another unit (riff works via jtag, and after you need to repair imei/security, and flash rom again). It should have some other way, simpler, but I couldn´t find, and couldn´t get help anywhere.
Click to expand...
Click to collapse
holy crap man! I have no idea what more than half of that means, lol....If it's not too much trouble could you break it down for a lamen? or hook me up with some links.

I work with mobile repairs, so I have equipment for that, they are called 'boxes' (or gsm box). I used 2 of those tools (spt and z3x, around 150usd each) to achieve repair. I know that what I did using SPT is possible to do with free software (odin and efs tool), but you have to be very careful with the .pit file you use. This file is used when you repartition phone (search xda wiki for android phone partitions), but if you use wrong file, you´ll have nothing but a brick, and most cases is not even possible to repair without proper equipment. The second part, that in my situation I used z3x, I don´t know any free software that could do that.
in resume, what I told above, require that you have paid tools. maybe someone reading this thread can help by pointing out some free tool that can make efs rebuild. as for imei repair, matter can´t be discussed in this board, it´s against the rules. so I think you may have to look for a good technician and take phone to him. I won´t offer myself, as I am in Brazil.
br

Thanks for all of the info!!!

vazgsm said:
I work with mobile repairs, so I have equipment for that, they are called 'boxes' (or gsm box). I used 2 of those tools (spt and z3x, around 150usd each) to achieve repair. I know that what I did using SPT is possible to do with free software (odin and efs tool), but you have to be very careful with the .pit file you use. This file is used when you repartition phone (search xda wiki for android phone partitions), but if you use wrong file, you´ll have nothing but a brick, and most cases is not even possible to repair without proper equipment. The second part, that in my situation I used z3x, I don´t know any free software that could do that.
in resume, what I told above, require that you have paid tools. maybe someone reading this thread can help by pointing out some free tool that can make efs rebuild. as for imei repair, matter can´t be discussed in this board, it´s against the rules. so I think you may have to look for a good technician and take phone to him. I won´t offer myself, as I am in Brazil.
br
Click to expand...
Click to collapse
Hi man, I'm from Brazil too, and got the same tablet of Sky Tv with the same MDM lock, but I hadn't success with the odin/pit proccess. What city are you from? How much would cost your repair service? Could you please email me at [email protected] ?
Tnks!

No IMEI, IMEI SV, or Signal after flash rom stock

First of all, i started being a newbie, i just wanted to install magisk for cam2api, but i messed up: i combined for error 2 different system (mine that was ios9 and ios8). So i tried to read more and more threads and it just got worse. to make the story short: i had to get to test-point and restore the phone with Xiaomi Mi Flash tool & an original rom stock.
So now that i can go inside the Android System and use the phone, my sim card is just not working, i checked and my imei was 0 and my IMEI SV also 0.
I tried deleting modemst 1 and 2, i tried to reflash the phone with another stock images, updating the phone via android (normal way), i tried to restore my imei with the QPST Dual Imei (and it worked but the IMEI SV still in 0). nothing is working Please i need help i think my efs folder it's corrupted but i'm not shure.
Also i don't have any EFS backup or System backup, nothing.

JoiaDG said:
First of all, i started being a newbie, i just wanted to install magisk for cam2api, but i messed up: i combined for error 2 different system (mine that was ios9 and ios8). So i tried to read more and more threads and it just got worse. to make the story short: i had to get to test-point and restore the phone with Xiaomi Mi Flash tool & an original rom stock.
So now that i can go inside the Android System and use the phone, my sim card is just not working, i checked and my imei was 0 and my IMEI SV also 0.
I tried deleting modemst 1 and 2, i tried to reflash the phone with another stock images, updating the phone via android (normal way), i tried to restore my imei with the QPST Dual Imei (and it worked but the IMEI SV still in 0). nothing is working Please i need help i think my efs folder it's corrupted but i'm not shure.
Also i don't have any EFS backup or System backup, nothing.
Click to expand...
Click to collapse
I´m not sure what you mean by ios8 and ios9, maybe oreo and pie.
For the next time just so you know test point method is not recommended while you are not completely bricked (although is recommended out there without care), on a unlocked device most probably you won´t need it to solve this kind of issue, there are other resources to try previous to this stage.
I never had this kind of problem, you might try this https://zfirmware.com/how-to-repair-qualcomm-imei-via-qualcomm-write-imei-tool/

Sadly not working
SubwayChamp said:
I´m not sure what you mean by ios8 and ios9, maybe oreo and pie.
For the next time just so you know test point method is not recommended while you are not completely bricked (although is recommended out there without care), on a unlocked device most probably you won´t need it to solve this kind of issue, there are other resources to try previous to this stage.
I never had this kind of problem, you might try this
Click to expand...
Click to collapse
Sadly, it didn't work. i was thinking if there was a way to do it with root

JoiaDG said:
Sadly, it didn't work. i was thinking if there was a way to do it with root
Click to expand...
Click to collapse
Try rewriting the IMEI's from the box (I hope you still have the box and paperwork since there is the original IMEI's) with the Qualcomm IMEI Tool. Reflash full stock rom.
The tool is here: https://androidmtk.com/download-qualcomm-smartphone-write-imei-tool
If everything fails and your knowledge is not helping you to find a solution and you are still under warranty and respect the warranty for physical aspect of the device (no scuffs, no damage, no aftermarket replaced parts that may damaged warranty voids inside the phone) you can flash it stock, lock bootloader and file a warranty replacement as "damage from OTA". The service will replace your motherboard.

I need help
TheoXSD said:
Try rewriting the IMEI's from the box (I hope you still have the box and paperwork since there is the original IMEI's) with the Qualcomm IMEI Tool. Reflash full stock rom.
The tool is here:
If everything fails and your knowledge is not helping you to find a solution and you are still under warranty and respect the warranty for physical aspect of the device (no scuffs, no damage, no aftermarket replaced parts that may damaged warranty voids inside the phone) you can flash it stock, lock bootloader and file a warranty replacement as "damage from OTA". The service will replace your motherboard.
Click to expand...
Click to collapse
I know i have to use that tool, but my device is not recognized by that app, i tried to install all the drivers, but nothing's working.

JoiaDG said:
Sadly, it didn't work. i was thinking if there was a way to do it with root
Click to expand...
Click to collapse
I knew that there is a method to restore IMEIs via adb but I don´t remember commands so I never need it. First I do before tinkering device is to backup IMEI/EFS/NVram.
I had a theory that years ago I proved, IMEI is not really lost but just overlapped so if you have some friend that can give you their backup this will recover the yours but won´t overwrite/replace the yours. Not sure if it works yet.
About the tool that I linked maybe you need to get it through either in fastboot or download mode, try both; I don´t think that detect it while device is on.

https://forum.xda-developers.com/mi-a2-lite/how-to/sim-network-solution-alternatively-t3914161 i fixed the phone with this tutorial

JoiaDG said:
https://forum.xda-developers.com/mi-a2-lite/how-to/sim-network-solution-alternatively-t3914161 i fixed the phone with this tutorial
Click to expand...
Click to collapse
Yeah this fixed my phone too, now I'm making backups

MODEM went crazy after upgrading MIUI to [Global 10.3.5.0] from [China 9.6.12]

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?

[Solved] Xiaomi Redmi Note 8 Pro hard brick

I tried unsuccessfully to install TWRP on a Xiaomi Redmi Note 8 Pro.
These are the steps I took:
Unlock the bootloader with MiUnlock.
Downloaded Fastboot.
Copied this CFW TWRP inside the Fastboot folder.
Downloaded these two files and copied inside the Fastboot folder.
fastboot flash preloader preloader_begonia.bin
fastboot flash lk lk.img
fastboot flash recovery twrp-3.3.1-0-begonia_UNOFFICIAL.img
fastboot reboot
And the result is that it no longer turns on. It also fails neither to enter the Fastboot screen, nor in that of recovery.
Windows no longer sees the device, so I can't interact in any way even with the folders inside the phone memory. Finally it is not even seen by Xiaomi Flash Tool (wanting to try to reinstall the official ROM).
The phone, immediately after unlocking it with the Xiaomi tool, had MIUI 12. I don't know which Android mounted (my fault), but I proceeded the same, without doing a downgrade, since in a discussion here on the forum it seemed that it could work same, even without downgrading to Android 9.
Is there any way to fix?
Maybe using Linux, you might be able to interact with the phone memory even if it is turned off / bricked?

Solution
Without hoping in the least, I solved it by following this video step-by-step.
I thank the author of this video a million times.
For anyone who was reading and needed it, there is no need to open the phone, remove the battery, connect various wires... You can do everything from software with a couple of clicks, even if the phone does not seem to want to connect absolutely to the PC.
Follow the linked video, it's very simple and you will save a lot of money!

Only if you have flashed it with a CFW
Angry Unlocker said:
Without hoping in the least, I solved it by following this video step-by-step.
I thank the author of this video a million times.
For anyone who was reading and needed it, there is no need to open the phone, remove the battery, connect various wires... You can do everything from software with a couple of clicks, even if the phone does not seem to want to connect absolutely to the PC.
Follow the linked video, it's very simple and you will save a lot of money!
Click to expand...
Click to collapse
Good for CFW, but if you are on a official MIUI and you've hardbricked it then you have to through an authorised Xiaomi account, in other words, it is a "payable flash" that you have to perform.

I had the same problem
Months ago I tried to install a stock ROM prior to the latest version installed, I got a brick exactly like the one you have, I didn't know who to go with until days ago, in a group on Telegram.
There is a group where a boy from Spain helped me with his authorized account for € 30, if you want to contact him I will leave you the link of the group.
https: //t.me /edlauth
(I put spaces for it to allow me to post the answer)

Thanks for your answers!
kingsemperor said:
Good for CFW, but if you are on a official MIUI and you've hardbricked it then you have to through an authorised Xiaomi account, in other words, it is a "payable flash" that you have to perform.
Click to expand...
Click to collapse
I am not quite clear what you mean exactly, but I, before proceeding with trying to flash a custom ROM, I had connected my original Xiaomi account to the device in question and also had requested the unlocking of the bootloader through the appropriate Xiaomi software (and I finally waited the time indicated by them, before proceeding). So on my Note 8 Pro there was actually the original / official MIUI updated to the latest version and I didn't need to proceed with a payment of any kind following that tutorial.
chumpokemon said:
Months ago I tried to install a stock ROM prior to the latest version installed, I got a brick exactly like the one you have, I didn't know who to go with until days ago, in a group on Telegram.
There is a group where a boy from Spain helped me with his authorized account for € 30, if you want to contact him I will leave you the link of the group.
https: //t.me /edlauth
(I put spaces for it to allow me to post the answer)
Click to expand...
Click to collapse
Thanks for your suggestion, but I have already solved it by following precisely that video.

How could I unlock the bootloader with the device bricked?
I has been trying a to unlock bootloader with MiUnlock but doesn't work. Is there any other way to unlock the bootloader with the bricked device?

Perike said:
How could I unlock the bootloader with the device bricked?
I has been trying a to unlock bootloader with MiUnlock but doesn't work. Is there any other way to unlock the bootloader with the bricked device?
Click to expand...
Click to collapse
You need to unbrick your device, follow the video tutorial
https :// youtu.be /wm0UFvjSvVg

chumpokemon said:
You need to unbrick your device, follow the video tutorial
https :// youtu.be /wm0UFvjSvVg
Click to expand...
Click to collapse
Flashed successfully, but the result is a reboot and This Miui version cant be installed on this device...

Angry Unlocker said:
Solution
Without hoping in the least, I solved it by following this video step-by-step.
I thank the author of this video a million times.
For anyone who was reading and needed it, there is no need to open the phone, remove the battery, connect various wires... You can do everything from software with a couple of clicks, even if the phone does not seem to want to connect absolutely to the PC.
Follow the linked video, it's very simple and you will save a lot of money!
Click to expand...
Click to collapse
Why does it say "this video is private" ?

It’s now easy to bypass MediaTek’s SP Flash Tool authentication

Article here
What do you think? Will this finally let us unbrick redmi note 8 pro without mi authorized account?
Did some dev look into this yet?

yes i've tested it it works. i couldnt do anything with it though but it shouldnt be that hard to let us flash cfw and twrp or unlock the bootloader using spflashtool right. this thing is huge i mean granted its not the easiest to do but honestly its not even that hard if you know what you're doing which you should if you're on xda, it took about 10 mins on me

it is possible, we're just waiting for a dev to implement it, right now there isnt much you can do w sp flash tools

wentaas said:
it is possible, we're just waiting for a dev to implement it, right now there isnt much you can do w sp flash tools
Click to expand...
Click to collapse
Why not? The scatter file is sitting there on /images folder in every fastboot rom distribution. Look for MT6785_Android_scatter.txt.
After that, your device should be a blank slate. The rest, is up to you.

Well, I think flashing vanilla rom should be your priority, since everything can be done when your device is up-and-running. And extra cautious of course.

kekesed97 said:
Why not? The scatter file is sitting there on /images folder in every fastboot rom distribution. Look for MT6785_Android_scatter.txt.
After that, your device should be a blank slate. The rest, is up to you.
Click to expand...
Click to collapse
wdym by blank state? and is that safe to do?

wentaas said:
wdym by blank state? and is that safe to do?
Click to expand...
Click to collapse
Not a blank state, a blank slate. You know, a blank board which you can write or draw anything you like? But that's not important right now.
Theoritically it should safe. It's like removing a boulder that blocking your way.
If you have access to SPFT, theoritically you should be able to flash your vanilla ROM, given the security measures are null (or rather, bypassed). If your device is chinese based you should flash chinese ROM there. Do a wipe and lock procedure. Let the bootloader locked for now, since you can unlock it later. Do not do crossflash there, without bootloader unlock (this should be a common sense).
But theory is a theory. I can't test it since my device is up-and-running.
My knowledge may be obsolete, since the last device I flashed was MT6572 back on its glory days, no security measures and bootloader was unlocked back then. You can't flash only and only if your eMMC is damaged, which is the worst case (oppo phones was prone to eMMC failure back then, and that happened to me). But afaik the flash process isn't changed that much, just an additional security measure was added, so I think my knowledge still apply.
Additional note: try to flash without nvram and nvdata to avoid losing IMEI (someone from Redmi Note 9 forum lose his IMEI).

kekesed97 said:
Not a blank state, a blank slate. You know, a blank board which you can write or draw anything you like? But that's not important right now.
Theoritically it should safe. It's like removing a boulder that blocking your way.
If you have access to SPFT, theoritically you should be able to flash your vanilla ROM, given the security measures are null (or rather, bypassed). If your device is chinese based you should flash chinese ROM there. Do a wipe and lock procedure. Let the bootloader locked for now, since you can unlock it later. Do not do crossflash there, without bootloader unlock (this should be a common sense).
But theory is a theory. I can't test it since my device is up-and-running.
My knowledge may be obsolete, since the last device I flashed was MT6572 back on its glory days, no security measures and bootloader was unlocked back then. You can't flash only and only if your eMMC is damaged, which is the worst case (oppo phones was prone to eMMC failure back then, and that happened to me). But afaik the flash process isn't changed that much, just an additional security measure was added, so I think my knowledge still apply.
Additional note: try to flash without nvram and nvdata to avoid losing IMEI (someone from Redmi Note 9 forum lose his IMEI).
Click to expand...
Click to collapse
ooh thanks for the explanation, to be clear, my phone is working fine right now but i hate miui. so my intention was to unlock the bootloader if possible, or install cfw and twrp if its not, or if thats not possible either, just installing a custom rom (probably aosp a11)

wentaas said:
ooh thanks for the explanation, to be clear, my phone is working fine right now but i hate miui. so my intention was to unlock the bootloader if possible, or install cfw and twrp if its not, or if thats not possible either, just installing a custom rom (probably aosp a11)
Click to expand...
Click to collapse
Well, for unlocking bootloader there's no other method than the official one. But in some cases the waiting time could be forever (well, many failed attempts would lead to loong waiting time, practically doesn't worth the wait).
My device was resurrected (around May 20, when everyone make a fuss about the lockout). And it can do UBL and root just fine, and tripped AVB many times. It's pretty safe to say tripping AVB on device with unlocked bootloader is recoverable. Just do fastboot flash via MiFlash Pro, and you are set! But never do "Flash and Lock" operation. It would lead to the lockout. You would regret it.

kekesed97 said:
You can't flash only and only if your eMMC is damaged, which is the worst case (oppo phones was prone to eMMC failure back then, and that happened to me)
Click to expand...
Click to collapse
Thanks for sharing your experience. This eMMC failure is because of Oppo or Mediatek? I have a Realme C12.
3 guys 'hard bricked' their devices. No sign of life. Flashing in SP Flash Tools results 'RAM_EXCEPTION (0xC0050005)'. Not able to readback too. It seems like eMMC replacement is only solution.
What are your ideas in this?
Thanks

HemanthJabalpuri said:
Thanks for sharing your experience. This eMMC failure is because of Oppo or Mediatek? I have a Realme C12.
3 guys 'hard bricked' their devices. No sign of life. Flashing in SP Flash Tools results 'RAM_EXCEPTION (0xC0050005)'. Not able to readback too. It seems like eMMC replacement is only solution.
What are your ideas in this?
Thanks
Click to expand...
Click to collapse
Maybe because oppo tried to cut corners since they're using mediatek? I don't see any reason for them to not cut the corner any further. It was 2015, it have a mediocre specs with mediocre quality for their price.
It's been a long ago, I forgotten the error messages. I'm afraid you are facing a worst case scenario.
If you can pull out your eMMC and put that on a jtag reader, there's might be a slight chance of revival.