Related
A while ago my phone wanted to do an EMUI update and halfway through it something failed and now my phone is stuck in a bootloop where it gets to the carrier logo screen then restarts and displays Huawei eRecovery (which does not work). I am aware that there are plenty of threads about this issue but none of them have really helped me. My phone was running completely stock software and the default development settings are active (OEM locked etc.) except maybe USB debugging. I've tried to send it back to my carrier but because it has a broken screen they won't take it under any warranty, I have also tried Huawei but their online help is awful and the closest service centre is over 10 hours away. I have no intentions of replacing the screen because for the price of it I may as well just buy a new phone.
As far as the model goes it is a MHA-L09 from Australia (bought via Optus), I have a bootloader code and my IMEI number.
I've tried to access the phone through bootloader and adb. adb doesn't recognise the phone whatsoever but bootloader does (using adb devices and bootloader devices respectively in cmd) but other bootloader commands have no effect as the OEM is locked.
I was just wondering whether I'm able to flash a new rom onto it given the circumstances or whether I should just buy a new phone altogether.
EmeraldStar82 said:
A while ago my phone wanted to do an EMUI update and halfway through it something failed and now my phone is stuck in a bootloop where it gets to the carrier logo screen then restarts and displays Huawei eRecovery (which does not work). I am aware that there are plenty of threads about this issue but none of them have really helped me. My phone was running completely stock software and the default development settings are active (OEM locked etc.) except maybe USB debugging. I've tried to send it back to my carrier but because it has a broken screen they won't take it under any warranty, I have also tried Huawei but their online help is awful and the closest service centre is over 10 hours away. I have no intentions of replacing the screen because for the price of it I may as well just buy a new phone.
As far as the model goes it is a MHA-L09 from Australia (bought via Optus), I have a bootloader code and my IMEI number.
I've tried to access the phone through bootloader and adb. adb doesn't recognise the phone whatsoever but bootloader does (using adb devices and bootloader devices respectively in cmd) but other bootloader commands have no effect as the OEM is locked.
I was just wondering whether I'm able to flash a new rom onto it given the circumstances or whether I should just buy a new phone altogether.
Click to expand...
Click to collapse
You can use DC-Phoenix to flash firmware.
There are tutorials on how to use it on their website (DC-Unlocker)
Ah, you have bootloader code. Then you might be able to fix this for free.
PM me on telegram, link in my signature
Hi,
I have somehow bricked my Xiaomi Redmi Note 6 Pro (Tulip) in a peculiar fashion.
It happened when a firmware flashing went downhill due to a faulty cable.
My device is now totally unresponsive. Pushing the power button does utterly nothing. There is no System, no Recovery, no Fastboot.
I managed to connect it in EDL mode (my PC sees it as "Qualcomm HS-USB QDLoader 9008" device).
With the correct drivers and after deactivating Windows Driver signature enforcing, I've been able to connect it with MiFlash Utility and receive the hello package.
UNFORTUNATELY, I cannot proceed to flash the new system image, since my Xiaomi Account does not have FLASHING PERMISSION.
I can't find any way to avoid this check. I mailed Xiaomi and they answered they can but won't help, since "it's my fault the phone is bricked".
Does anyone know how to flash in EDL mode without a flashing-enabled Xiaomi account?
Please, help. It's a fine phone, I'd hate to lose it when i'm just a mere security measure away from restoring it to perfect functionality!
Thanks for any help.
ILLE_614 said:
Hi,
I have somehow bricked my Xiaomi Redmi Note 6 Pro (Tulip) in a peculiar fashion.
It happened when a firmware flashing went downhill due to a faulty cable.
My device is now totally unresponsive. Pushing the power button does utterly nothing. There is no System, no Recovery, no Fastboot.
I managed to connect it in EDL mode (my PC sees it as "Qualcomm HS-USB QDLoader 9008" device).
With the correct drivers and after deactivating Windows Driver signature enforcing, I've been able to connect it with MiFlash Utility and receive the hello package.
UNFORTUNATELY, I cannot proceed to flash the new system image, since my Xiaomi Account does not have FLASHING PERMISSION.
I can't find any way to avoid this check. I mailed Xiaomi and they answered they can but won't help, since "it's my fault the phone is bricked".
Does anyone know how to flash in EDL mode without a flashing-enabled Xiaomi account?
Please, help. It's a fine phone, I'd hate to lose it when i'm just a mere security measure away from restoring it to perfect functionality!
Thanks for any help.
Click to expand...
Click to collapse
Funny I was just reading an article about this yesterday. There is only one way to fix this and that is with an authorized account. Sadly Xiaomi gave out a few account authorizations but won't do it anymore. Yet you may still be in luck if you open your wallet. The prices I saw were not very high $18-35USD. One of the guys here on XDA will do it remotely but I don't remember who. I found the article on mi-globe.com and will try and find it and link it.
Did you find the solution
cidxtc said:
Funny I was just reading an article about this yesterday. There is only one way to fix this and that is with an authorized account. Sadly Xiaomi gave out a few account authorizations but won't do it anymore. Yet you may still be in luck if you open your wallet. The prices I saw were not very high $18-35USD. One of the guys here on XDA will do it remotely but I don't remember who. I found the article on mi-globe.com and will try and find it and link it.
Click to expand...
Click to collapse
Did you find the solution
ASHRAFGTX said:
Did you find the solution
Click to expand...
Click to collapse
I found a person who had edl permission. Unfortunately due to xda rules we are not allowed to give out contact information because they charge for the service.
Try qfil application
Qfil application might help
This is for realme xt, but I believe that it is similar to a lot other devices based on qualcomm MSM chipsets.
In my specific case, I have a brand new realme xt phone with a locked bootloader (default from factory). I've upgraded it to latest stock realme Adnroid 10 from realme only to notice that the official unlock tool didn't work anymore. So I've tried to downgrade it from Android 10 to Android 9 stock ROM. It seemed to go ok, but it failed. Now system, recovery and fastboot are unaccessible. When turned on, it only stays at the logo screen.
So, after searching a lot, I've found out that there is a hidden EDL (Emergency Download Mode) from Qualcomm that it is used in situations like this. I've found the stock firmware (official ROMs in a .ofp file format). Since I can't reach recovery or fastboot mode, EDL seems to be the only option.
Again I've serched a lot, including what people would use for other phones, but I can't get any of those EDL tools to work: sometimes either you must have some secret credentials or the software have viruses (and I don't know if it still requires credentials). Other options require the firmware in other file formats: XML, MTN, etc, which I haven't figured out how to extract or acquire. Finally, there are many texts that says that QFIL, etc tools can't be used for realme xt, because they wouldn't be able to write the filesystems.
In my region there is no realme service center, so that's not an option. I've bought the phone from a registered importer, which is also clueless. The phone has all the invoices and related paperwork correct.
So, in a nutshell:
1) The phone is softbricked (hopefully), but requires EDL mode to be recovered. Sending it to a service center is not possible (because of import/export procedures);
2) Where can I find a tool to enable me to revive it to stock ROM (I already have ofp and ozip files)?
3) How can I acquire the required credentials (if necessary) for it to work?
4) Failing 2 and 3, does anybody know of someone who can provide remote services to fix it? (I'm thinking of setting up my computer and someone remotely using their credentials and procedures)
Thank you all in advance for any help. This would be my mother's Christmas gift, It is very expensive for us and right now it is only a very expensive paper weight.
Hello!
Sorry, I don't know vell ENG, so I use a translator.
Problem with Xiaomi Poco X3 Pro phone (Global Update 12.0.6.0.RJURUXM) + device unlocked
Unsuccessfully decided to flash the phone... I got the POCO X3 PRO and POCO X3 NFC phones mixed up a bit. I downloaded the firmware from the POCO X3 NFC and put it on the POCO X3 PRO via TWRP recovery. Then I tried to return everything as it was, but I couldn't. Accidentally via the TWRP menu formatted the System + partition Cache + Data and a few more sections, I don't really remember. At this stage, the phone was still functioning, turned on and rebooted in the recovery - TWRP menu. Then I tried to return the old recovery menu and connect Fastboot, but I couldn't. The phone turned into a brick. The phone does not turn on, does not work, the "POCO" logo does not appear, there is no way to go to recovery and Fastboot. The battery charge at that time was 46%...
HOWEVER, my computer sees the device as an emergency communication channel through the COM4 port - Qualcomm HS-USB QDLoader 9008 port
I'm already desperate and don't know what to do or what the instructions are... I don't want to open the phone and put it in EDL mode (if it helps at all)
I contacted a person with a service account, tried to restore the phone through the application "MiFlash_1212" by bypassing authorization and obtaining KEYS and access (I did not quite understand this point and how it works).
As a result, the firmware was able to run and the device began to be requested. But the following problem appeared, which I do not know how to solve, and that person stopped helping me (he has no time and simply does not want to, even though I paid him with money)
I read a lot of information on the form. Many tips and instructions did not help me.
What do I need to do? Who can I contact for help?
I wanted to get ROOT access (Magisc + YouTube Vanced + remove ads)
PS : But first I need to bring my phone back to life...
"I downloaded the firmware from the POCO X3 NFC and put it on the POCO X3 PRO via TWRP recovery."
-Why you put x3 nfc firm on x3 pro?
I guessed that you would ask about this moment.
It was my mistake and I thought they were the same.
And when the phone did not turn on properly, only THEN DID I REALIZE that I had downloaded the wrong files.
But what should I do?
Nitritus said:
"I downloaded the firmware from the POCO X3 NFC and put it on the POCO X3 PRO via TWRP recovery."
-Why you put x3 nfc firm on x3 pro?
Click to expand...
Click to collapse
I hope you find some help here
abood.mhd said:
I hope you find some help here
Click to expand...
Click to collapse
As they say : "Hope dies last" =((
Chances are you will still be able to unbrick it by playing with fastboot and using normal miflash
For the firmware go and search on mifirm device code vayu or poco x3 pro download the fastboot rom it should be in .tgz format
Unzip it and then put it into miflash l, switch the phone to fastboot mode by pressing volume up + power button at the same time
Hopefully that would do the trick or you can just go and ask xiaomi repair center since this case should still be within warranty
Contact your nearest Customer Support Center. They will fix the problem
Hassle free, just go straight to customer service.
If you still want to work on this, fine.
Its a stretch but is fastboot function restored?
If yes, download the fastboot image (not recovery) of your phone region, skip the miflash application and run the flash_all+lock script. The .bat file.
Make sure you get the right version for your phone and your region.
From the logs, wouldn't really be surprised if you still have no fastboot access.
Looks like the guy scammed you.
Sure he indeed have the right edl authentication but he only did his job halfway and bailed as your phone are still loading in edl mode.
thenameisJEFF said:
Chances are you will still be able to unbrick it by playing with fastboot and using normal miflash
For the firmware go and search on mifirm device code vayu or poco x3 pro download the fastboot rom it should be in .tgz format
Unzip it and then put it into miflash l, switch the phone to fastboot mode by pressing volume up + power button at the same time
Hopefully that would do the trick or you can just go and ask xiaomi repair center since this case should still be within warranty
Click to expand...
Click to collapse
I wrote that it does not turn on, does not go to fastoot, does not go to recovery, does not respond to charging, the indicators do not blink
xelrix said:
Hassle free, just go straight to customer service.
If you still want to work on this, fine.
Its a stretch but is fastboot function restored?
If yes, download the fastboot image (not recovery) of your phone region, skip the miflash application and run the flash_all+lock script. The .bat file.
Make sure you get the right version for your phone and your region.
From the logs, wouldn't really be surprised if you still have no fastboot access.
Looks like the guy scammed you.
Sure he indeed have the right edl authentication but he only did his job halfway and bailed as your phone are still loading in edl mode.
Click to expand...
Click to collapse
The phone did not turn on and fastboot and recovery do not enter any mode. The service can accept it, but it is clearly no longer under warranty and the price can be set very high.
WoodenSKY said:
The phone did not turn on and fastboot and recovery do not enter any mode. The service can accept it, but it is clearly no longer under warranty and the price can be set very high.
Click to expand...
Click to collapse
This is likely because you might have format some important part as IMEI number. Like this guy said: https://forum.xda-developers.com/t/no-imei-and-no-wifi-plss-help.4276823/post-85014473
In this state, no matter what you do, you have to pay.
https://forum.xda-developers.com/t/poco-x3-pro-hard-bricked.4277803/post-85025433
The most safe way is Xiaomi repair support center. High charge, but for sure a working phone.
my poco x3 pro global stable(VAYU) is stuck in miui log i tired to flash it with magisk method now its stuck ther. any one can help me with it
WoodenSKY said:
I wrote that it does not turn on, does not go to fastoot, does not go to recovery, does not respond to charging, the indicators do not blink
Click to expand...
Click to collapse
Straight to service center you go then )
It should still be within warranty becuz they only refuse hardware error not software brick
Beside it shouldn't cost much tbh
i did this mistake with my brand new galaxy s6 when it came out but the only solution i had was going to repair shop and the dude used a hardware tool called octoplus and he flashed it and worked but i lost my original imei adress but it worked i did search for you i found the tool you need is ufi box google it contact them and see if you get one or find a repair shop by the way i repaired that s6 with 10bucks
unfortunately, your only option is service centre as they are the only one who can get access to phone via edl mode and flash what was formatted
Just to be sure, I asked customer support and they said the following... "By installing custom ROM, Recovery, and/or Rooting your phone, the warranty is not void. However if your phone bricks while installing a custom ROM, then the warranty is considered void". They adding insult to injury for you
My Vayu is stuck on QUSB_BULK in device manager, I don't even know what to do?
True ayush Kushwaha said:
My Vayu is stuck on QUSB_BULK in device manager, I don't even know what to do?
Click to expand...
Click to collapse
same here, did you manage to fix yours?
Hello everybody,
i'm not new in custom roms, but i have a problem, i can't solve by myself:
I flashed an unlocked Mi5 to linageos 19.1 without problems.
I had the bad idea to relock the bootloader due to security reasons (fastboot oem lock).
Now the device is not booting anymore, i can just see the Mi-Logo flashing very shortly.
I can access fastboot, but can't boot into recovery.
I tried to unlock the device again, but the Mi Unlocker fails and prompts me to go to the developer options in Miui, which is clearly impossible.
Any chance to proceed from fastboot (fastboot oem unlock does not work...) ?
Thanks, Jan
congrats, you succesfully hard bricked your phone. please take it for a walk to the xiaomi service and pay for gettting it fixed. who told you it is a good idea to relock the bootloader with a custom rom installed ?
Fytdyh said:
congrats, you succesfully hard bricked your phone. please take it for a walk to the xiaomi service and pay for gettting it fixed. who told you it is a good idea to relock the bootloader with a custom rom installed ?
Click to expand...
Click to collapse
actually, i remember some banking apps complained about the locked bootloader. I thought i can lock/unlock it in fastboot mode, but looks like i was wrong.
I will give the MiFlash Tool a chance, but i have not much hope...
@Fytdyh: do you think, Xiaomi Service can fix it ?
jever2k said:
actually, i remember some banking apps complained about the locked bootloader. I thought i can lock/unlock it in fastboot mode, but looks like i was wrong.
I will give the MiFlash Tool a chance, but i have not much hope...
@Fytdyh: do you think, Xiaomi Service can fix it ?
Click to expand...
Click to collapse
Make sure if your bootloader is really locked or not using fastboot command
fastboot oem device-info
OR,
fastboot getvar unlocked
If it's not locked, you can simply flash your stock rom using flash tool available for mi. Before downloading a rom from internet, take note of your device info using fastboot command ,
fastboot getvar all
And if bootloader is really locked, you have to flash stock rom from EDL mode. You may have to remove back cover to turn on EDL mode. Your device has snapdragon chipset (Plus point). Watch tutorials about xiaomi edl rom flash - snapdragon. You can go to service centre. If they tell you that you have to replace motherboard, don't be agree. Tell them to flash rom using EDL mode.
Tawsif999 said:
Make sure if your bootloader is really locked or not using fastboot command
fastboot oem device-info
OR,
fastboot getvar unlocked
If it's not locked, you can simply flash your stock rom using flash tool available for mi. Before downloading a rom from internet, take note of your device info using fastboot command ,
fastboot getvar all
And if bootloader is really locked, you have to flash stock rom from EDL mode. You may have to remove back cover to turn on EDL mode. Your device has snapdragon chipset (Plus point). Watch tutorials about xiaomi edl rom flash - snapdragon. You can go to service centre. If they tell you that you have to replace motherboard, don't be agree. Tell them to flash rom using EDL mode.
Click to expand...
Click to collapse
looks like i am getting closer... located the two EDL points to short during PC connection, installed the Qualcomm serial driver. For a second i see the device appearing as COM6 but then it disappears again and is not availiable anymore.
Any hints ?
Thanks again, Jan
jever2k said:
looks like i am getting closer... located the two EDL points to short during PC connection, installed the Qualcomm serial driver. For a second i see the device appearing as COM6 but then it disappears again and is not availiable anymore.
Any hints ?
Thanks again, Jan
Click to expand...
Click to collapse
Try this to solve the issue.
If it doesn’t help, read this to boot properly into edl
jever2k said:
Hello everybody,
i'm not new in custom roms, but i have a problem, i can't solve by myself:
I flashed an unlocked Mi5 to linageos 19.1 without problems.
I had the bad idea to relock the bootloader due to security reasons (fastboot oem lock).
Now the device is not booting anymore, i can just see the Mi-Logo flashing very shortly.
I can access fastboot, but can't boot into recovery.
I tried to unlock the device again, but the Mi Unlocker fails and prompts me to go to the developer options in Miui, which is clearly impossible.
Any chance to proceed from fastboot (fastboot oem unlock does not work...) ?
Thanks, Jan
Click to expand...
Click to collapse
Flash stock recovery for your device via fastboot, then you should be able to boot into recovery or flash a stock system.img or your full stock firmware for your device, then unlock the bootloader(fastboot oem unlock) then flash TWRP and LineageOS again.
Droidriven said:
Flash stock recovery for your device via fastboot, then you should be able to boot into recovery or flash a stock system.img or your full stock firmware for your device, then unlock the bootloader(fastboot oem unlock) then flash TWRP and LineageOS again.
Click to expand...
Click to collapse
But he mentioned, bootloader fails to unlock. Actually it's hard brick(Even though he can boot into fastboot,the bootloader is locked. So nothing to do with fastboot).Without unlocked bootloader, flashing something from fastboot will hard brick his device completely (Will not be able to boot into fastboot). Or flashing will be denied
Tawsif999 said:
Try this to solve the issue.
If it doesn’t help, read this to boot properly into edl
Click to expand...
Click to collapse
OK, next level reached. The phone is connected to the com-port and the correct driver is displayed.
The whole procedure is a bit unstable, i need to connect the phone several times, to get a stable EDL mode.
The Xiaomi Flasher recognizes the phone, but flashing does not succeed. Sometimes it's not able to receive a kind of Hello message, sometimes it displays "object reference not set to an instance of an object".
I also downloaded the QPST flasher, but have no plan, how to use it.
I'll keep on trying!
Thanks to all, who helped me to reach this point!
jever2k said:
OK, next level reached. The phone is connected to the com-port and the correct driver is displayed.
The whole prcedure is a bit unstable, i need to connect the phone several times, to get a stable EDL mode.
The Xiaomi Flasher recognizes the phone, but flashing does not succeed. Sometimes it's not able to receive a kind of Hello message, sometimes it displays "object reference not set to an instance of an object".
I also downloaded the QPST flasher, but have no plan, how to use it.
I'll keep on trying!
Thanks to all, who helped me to reach this point!
Click to expand...
Click to collapse
I found something new by watching this video. Maybe you don't understand hindi(India is our relative country, so I do).
Lemme explain,
This guy's xiaomi k20 pro phone hard bricked with a locked bootloader. He tried a lot to repair it(by deep flash or something idk). But everything failed. At last he came to this step of EDL mode. But xiaomi Edl mode flash requires an "AUTHORIZED MI ACCOUNT" . Xiaomi people pay to get authorized account license that normal users don't have. So the guy contacted with them on a telegram page called "Mod Edit: Name Removed" . They told him that they will repair his phone via teamviewer. All he had to do is pay some $ & connect phone in edl mode. Rest of the things were done by them. And his phone repaired successfully! (Watch the video from 4:00)
So In his video, he is telling to go to that page & contact with "Mod Edit: Name Removed" there. They take 20-25$ (depends on device). If you tell them you're from Mod Edit: Name Removed's video, they will give some discount
Tawsif999 said:
But he mentioned, bootloader fails to unlock. Actually it's hard brick(Even though he can boot into fastboot,the bootloader is locked. So nothing to do with fastboot).Without unlocked bootloader, flashing psomething from fastboot will hard brick his device completely (Will not be able to boot into fastboot). Or flashing will be denied
Click to expand...
Click to collapse
Yeah, I jumped the gun and posted before seeing all the replies in the thread describing their whole scenario, should've known better.
They obviously need a hardware approach, i.e. JTAG/RIFF/Octoplus or replace motherboard.
Tawsif999 said:
I found something new by watching this video. Maybe you don't understand hindi(India is our relative country, so I do).
Lemme explain,
This guy's xiaomi k20 pro phone hard bricked with a locked bootloader. He tried a lot to repair it(by deep flash or something idk). But everything failed. At last he came to this step of EDL mode. But xiaomi Edl mode flash requires an "AUTHORIZED MI ACCOUNT" . Xiaomi people pay to get authorized account license that normal users don't have. So the guy contacted with them on a telegram page called "Mod Edit: Name Removed" . They told him that they will repair his phone via teamviewer. All he had to do is pay some $ & connect phone in edl mode. Rest of the things were done by them. And his phone repaired successfully! (Watch the video from 4:00)
So In his video, he is telling to go to that page & contact with "Mod Edit: Name Removed" there. They take 20-25$ (depends on device). If you tell them you're from Mod Edit: Name Removed's video, they will give some discount
Click to expand...
Click to collapse
Thanks for research!
Meanwhile, i stopped using Windows due to all the caveats and switched to reliable Debian Linux on a different machine.
Again it takes 10 attempts to get into EDL Mode.
I used qdl (Qualcomm downloader for Linux) with all the firehose, raw and patch .xmls
Code:
sudo ./qdl --debug --storage ufs --include . prog_ufs_firehose_8996_ddr.elf partition.xml rawprogram0.xml rawprogram1.xml rawprogram2.xml rawprogram3.xml rawprogram4.xml rawprogram5.xml patch0.xml patch1.xml patch2.xml patch3.xml patch4.xml patch5.xml
Output looked like some stuff was written, at the end i receive:
Code:
qdl: failed to write: Connection timed out
However, the phone is now dead as can be without fastboot working any more.
Maybe i'll give it another try, or get a used Mainboard...
Best regards, Jan
jever2k said:
Thanks for research!
Meanwhile, i stopped using Windows due to all the caveats and switched to reliable Debian Linux on a different machine.
Again it takes 10 attempts to get into EDL Mode.
I used qdl (Qualcomm downloader for Linux) with all the firehose, raw and patch .xmls
Code:
sudo ./qdl --debug --storage ufs --include . prog_ufs_firehose_8996_ddr.elf partition.xml rawprogram0.xml rawprogram1.xml rawprogram2.xml rawprogram3.xml rawprogram4.xml rawprogram5.xml patch0.xml patch1.xml patch2.xml patch3.xml patch4.xml patch5.xml
Output looked like some stuff was written, at the end i receive:
Code:
qdl: failed to write: Connection timed out
However, the phone is now dead as can be without fastboot working any more.
Maybe i'll give it another try, or get a used Mainboard...
Best regards, Jan
Click to expand...
Click to collapse
jever2k said:
Thanks for research!
Meanwhile, i stopped using Windows due to all the caveats and switched to reliable Debian Linux on a different machine.
Again it takes 10 attempts to get into EDL Mode.
I used qdl (Qualcomm downloader for Linux) with all the firehose, raw and patch .xmls
Code:
sudo ./qdl --debug --storage ufs --include . prog_ufs_firehose_8996_ddr.elf partition.xml rawprogram0.xml rawprogram1.xml rawprogram2.xml rawprogram3.xml rawprogram4.xml rawprogram5.xml patch0.xml patch1.xml patch2.xml patch3.xml patch4.xml patch5.xml
Output looked like some stuff was written, at the end i receive:
Code:
qdl: failed to write: Connection timed out
However, the phone is now dead as can be without fastboot working any more.
Maybe i'll give it another try, or get a used Mainboard...
Best regards, Jan
Click to expand...
Click to collapse
That's expensive. Anyway, it will be better if you don’t waste time on this. Just go for 3rd party help(From that official telegram channel or service centre). That will cost less
Tawsif999 said:
That's expensive. Anyway, it will be better if you don’t waste time on this. Just go for 3rd party help(From that official telegram channel or service centre). That will cost less
Click to expand...
Click to collapse
Thanks Tawsif for the good hints and links.
I don't really depend on the phone, so i will keep trying.
It's not wasted time, it's mainly learning new stuff and improving skills.
I believe, i'm not too far away and if it works, it's the best satisfaction.
If not, i bricked an old Mi 5.
All the best,
Jan