Soo, I was installing eu rom via fastboot when accidentally close the terminal windows that was running the sh file (I was doing some other thing with homebrew, thought that was the one I was closing, yes I was careless) decided to relaunch the .sh file but it got stuck on waiting for the device, decided to try and restart my phone, only problem is that after exiting fastboot cant seem to get out of blackscreen, Im completely lost, any help is appreciated
That's not good. You now likely have to use EDL Mode to flash a ROM.
Problem is, Xiaomi locked the EDL Mode to Xiaomi Authorised Service Centers, who have an Authorized Account to initiate the Flash.
They did this to stop people from importing the Chinese Variants to EU/USA, flashing ROM and selling them for Cheap.
<Moderator Edit>: @cyanGalaxy, I'll let you know just as soon as I can about what I removed from this post and why.
I have experience with that because I've gone through it. <Moderator Edit>
cyanGalaxy said:
That's not good. You now likely have to use EDL Mode to flash a ROM.
Problem is, Xiaomi locked the EDL Mode to Xiaomi Authorised Service Centers, who have an Authorized Account to initiate the Flash.
They did this to stop people from importing the Chinese Variants to EU/USA, flashing ROM and selling them for Cheap.
You probably have to pay someone $35 on Telegram. They'll help you unbrick your phone. They'll do this by remote-controlling your PC.
I used this group https://t.me/miauthofficial_d
I had to do this once and it worked.
It may be possible for cheaper, maybe elsewhere ^^ I did it using the Telegram Group I linked above for ~24€ ($35).
I have experience with that because I've gone through it. If you want I can leave you my Discord if you need more help... cyanGalaxy#3161
Click to expand...
Click to collapse
Isn’t there any other way? I mean letting someone tunnel to my pc sounds fishy to say the least, isn’t there maybe a modified version of the program or something that I could use?
<Moderator Edit>
Edit: I just saw my previous reply got edited by a moderator. I think it's not allowed here to mention these kinds of services, but it's not an advertisement at all. I'm just saying what helped me when I hardbricked my phone. :S
I mean other than such a service, you could go to a Xiaomi Store and perhaps use Warranty-Claim?
cyanGalaxy said:
I saw a program some time ago here on XDA that was just 1€/$1 to unbrick your phone over EDL, but I don't remember the name..
Yes, it does sound hella sketchy but it is a real service.
View attachment 5664369
Edit: I just saw my previous reply got edited by a moderator. I think it's not allowed here to mention these kinds of services, but it's not an advertisement at all. I'm just saying what helped me when I hardbricked my phone. :S
I mean other than such a service, you could go to a Xiaomi Store and perhaps use Warranty-Claim?
Click to expand...
Click to collapse
Sadly, its a few weeks out of warranty and the closes Xiaomi store is about two hours from here, will try to go, but who knows if they will even consider repairing it
Bruh124 said:
Sadly, its a few weeks out of warranty and the closes Xiaomi store is about two hours from here, will try to go, but who knows if they will even consider repairing it
Click to expand...
Click to collapse
Ok, yeah that sucks. <Moderator Edit> I can explain the other choice in more detail, since I've gone a hardbrick and so know a bit about it.
But if the Xiaomi Store would do it, that's also good.
<Moderator Edit>
I don't know if flashing Custom ROMs invalidates Warranty-Claims. ^^ (i know yours is out of it already, but maybe they have mercy)
Related
Hey I am getting this error Current Account Cannot unlock this device everytime i try to unlock my Redmi 5A. I have tried every method mentioned on internet but still the same result. I contacted customer care and they said they had no solution. Someone please help me. Any method will do. I just want to unlock my phone at all costs. I'm even willing to pay for unlocking my device's bootloader. For the love of god someone plz help cause I'm at my wit's end now.
P.S. Don't try to tell me to follow method by @xcaanz because i dont know low lev prog language and there is no clear tutorial for that.
Device Specs: Redmi 5A -2, 16. Current Rom- MIUI 10 beta( 8.9.20) but i've tried to unlock on MIUI global stable 9.5 as well as 9.6.
I'm sorry it's xaacnz not xcaanz.
You have to register your xiaomi account for unlocking at http://en.miui.com/unlock/. The error you are getting means you are not registered.
oddhap said:
You have to register your xiaomi account for unlocking at http://en.miui.com/unlock/. The error you are getting means you are not registered.
Click to expand...
Click to collapse
I have already done that. No matter what i try i get the same error.
just stupid questions... i have read all of your posts and see you have read everything and tried everything. but its not absolutely clear... did you receive SMS confirmation? did you click on Find device and located your phone? did you solve the previous error 86012 cannot bind account? did you check the driver is shown as Xiaomi Corp? have you tried another usb cable or switched the port? tried with older version of Mi unlock tool? Developer options OEM unlocking box still greyed out at any time?
(just answer with yes, yes, yes)
---------- Post added at 22:27 ---------- Previous post was at 22:09 ----------
just some google results.. some of this (more ore less) claims there is a waiting period (hours .. days ..) which will increase.
https://forum.xda-developers.com/showthread.php?t=3565459
https://forum.xda-developers.com/showthread.php?t=3608650
http://en.miui.com/thread-1394024-1-1.html
http://xiaomitips.com/guide/how-to-fix-couldnt-verify-device-error-during-bootloader-unlock-process
https://www.allaboutxiaomi.com/unlock-bootloader-redmi-xiaomi-device
aIecxs said:
just stupid questions... i have read all of your posts and see you have read everything and tried everything. but its not absolutely clear... did you receive SMS confirmation? did you click on Find device and located your phone? did you solve the previous error 86012 cannot bind account? did you check the driver is shown as Xiaomi Corp? have you tried another usb cable or switched the port? tried with older version of Mi unlock tool? Developer options OEM unlocking box still greyed out at any time?
(just answer with yes, yes, yes)
---------- Post added at 22:27 ---------- Previous post was at 22:09 ----------
just some google results.. some of this (more ore less) claims there is a waiting period (hours .. days ..) which will increase.
https://forum.xda-developers.com/showthread.php?t=3565459
https://forum.xda-developers.com/showthread.php?t=3608650
http://en.miui.com/thread-1394024-1-1.html
http://xiaomitips.com/guide/how-to-fix-couldnt-verify-device-error-during-bootloader-unlock-process
https://www.allaboutxiaomi.com/unlock-bootloader-redmi-xiaomi-device
Click to expand...
Click to collapse
First- The process to apply is now simplified, so we no longer have to give a reason for unlocking on mi.com/unlock and it doesn't send u an SMS confirmation now. U just get the waiting time on mi unlock tool. Here is the thread-
http://en.miui.com/thread-246705-1-1.html
I get directed to download page directly after filling in my login credentials.
Yes, i clicked on find device and my device was located.
As for the error 86012, i have tried Plex VPN and many other VPNs and set the server to Hong Kong/ China but it did not work. Later i read on XDA that u can unlock even with error 86012.
Yes indeed. Checked that just now and the driver is shown as Xiaomi Corp.
No, I haven't tried another USB cable.
When i try with older version of Xiaomi unlock i can not login as it gives network error everytime.
No OEM unlock is not greyed out.
Hope u can help me now.
Thank you for this information, this link is the most useful from all the stuff i have read so far. Didn't know that no sms confirmation is required.
So, what happens if you enable OEM unlocking in Developer Options and then unlock in fastboot mode?
Code:
fastboot oem unlock
aIecxs said:
Thank you for this information, this link is the most useful from all the stuff i have read so far. Didn't know that no sms confirmation is required.
So, what happens if you enable OEM unlocking in Developer Options and then unlock in fastboot mode?
Code:
fastboot oem unlock
Click to expand...
Click to collapse
I'll give it a shot but i have read that it gives some sort of error.
Anyways thnx for ur time
In your Link, they mentioned a logfile /sdcard/MIUI/debug_log/*.zip, can you share this? see ...
Steps to reproduce the error: iv. Once the error message is shown, head towards dialer and dial *#*#284#*#*
Found a comment on this Video, maybe thats the reason for not working?
http://www.youtube.com/watch?v=AE4JhUbZ_LQ
"You need the original firmware that your phone is supposed to be shipped with to unlock the bootloader. If your device is a Chinese model it needs the China ROM, if it's the Global model it needs the Global ROM." (ChinaMobileMag)
aIecxs said:
Found a comment on this Video, maybe thats the reason for not working?
http://www.youtube.com/watch?v=AE4JhUbZ_LQ
"You need the original firmware that your phone is supposed to be shipped with to unlock the bootloader. If your device is a Chinese model it needs the China ROM, if it's the Global model it needs the Global ROM." (ChinaMobileMag)
Click to expand...
Click to collapse
My device is global version and i have MIUI 10 Global dev at present but I also tried unlocking at MIUI 9.5 which is the version Riva was shipped with. The result was still the same. Seriously idk what to do anymore. And yeah regarding that bug report, i gave not tried unlocking after i got the error Couldn't verify. I'll try once again to check if i'm getting some other error this time on unlock tool. But at present i don't have my Laptop so it might take a day or two. If u need the bug reoprt sooner do tell me. I'll upload it right away( I guess there's no point clinging to a small ray of hope now). Anyways thanks mate!!
aIecxs said:
In your Link, they mentioned a logfile /sdcard/MIUI/debug_log/*.zip, can you share this? see ...
Steps to reproduce the error: iv. Once the error message is shown, head towards dialer and dial *#*#284#*#*
Click to expand...
Click to collapse
Here's the bug report. I tried using command fastboot oem unlock again but it didn't work.
the logfile says CloudDeviceStatus stateCode 200 "ok" which means it has a successful connection to server, but then gives error device not found code 86012 description "设备不存在".
this may have different reasons (but i am not that expert):
a) the data on server is deleted - server fault?
b) access denied - account fault?
c) the device-id (or whatever they submit) election is empty or invalid - rom issue?
d) account is not binded to device?
Is this phone brand-new, do you still remember all accounts used from this device? Log-in to every single account and delete all binded devices, then use the very first account only. For my understanding only one account can be granted permission. Just try over and over again after 15 days - sorry i can not help
aIecxs said:
the logfile says CloudDeviceStatus stateCode 200 "ok" which means it has a successful connection to server, but then gives error device not found code 86012 description "设备不存在".
this may have different reasons (but i am not that expert):
a) the data on server is deleted - server fault?
b) access denied - account fault?
c) the device-id (or whatever they submit) election is empty or invalid - rom issue?
d) account is not binded to device?
Is this phone brand-new, do you still remember all accounts used from this device? Log-in to every single account and delete all binded devices, then use the very first account only. For my understanding only one account can be granted permission. Just try over and over again after 15 days - sorry i can not help
Click to expand...
Click to collapse
Bought the phone in August 2018. The account that im trying to unlock with is the acc. I created in this phone.
Thnx mate for ur help. I can not thank u enough for what u have done. Prior to this also i had created threads in MI community, asked for help in via posts in XDA thread but no one gave a damn about my problem. Thnx again for at least digging this deep in the problem.
You can send a email to customer support with subject unlocking: 设备不存在 and attach the filtered log file from my post - or even post this error again. You are clearly not the only one, this is a common problem. You can search in chinese forums, too. Please keep this thread updated, it will be helpful for others. I am facing this problem too, my son has Redmi 5a and i failed unlocking bootloader so the phone never was rooted, therefore has no TWRP and in case the screen will brake i don't know how to rescue data... at the moment for him best solution is "never touch a running system" and @xaacnz 's method is high risk for bricking we should better not try with daily driver
edit: post it on youtube channel too, or send a private message with invitation to your xda thread
http://www.youtube.com/watch?v=CiciDJfzlB8
aIecxs said:
You can send a email to customer support with subject unlocking: 设备不存在 and attach the filtered log file from my post - or even post this error again. You are clearly not the only one, this is a common problem. You can search in chinese forums, too. Please keep this thread updated, it will be helpful for others. I am facing this problem too, my son has Redmi 5a and i failed unlocking bootloader so the phone never was rooted, therefore has no TWRP and in case the screen will brake i don't know how to rescue data... at the moment for him best solution is "never touch a running system" and @xaacnz 's method is high risk for bricking we should better not try with daily driver
edit: post it on youtube channel too, or send a private message with invitation to your xda thread
http://www.youtube.com/watch?v=CiciDJfzlB8
Click to expand...
Click to collapse
Ok I will. Btw bout that yt channel, I just have to add a comment right? I'll create another thread on Mi forums about this problem. It really sucks not being able to unlock bootloader. TBH the only reason i bought this phone was because on searching the forums I found that this was the only device in my budget that had this many cusroms and other mods. I really am disappointed at how it turned out.
Hope we can find a solution soon!
aIecxs said:
Found a comment on this Video, maybe thats the reason for not working?
http://www.youtube.com/watch?v=AE4JhUbZ_LQ
"You need the original firmware that your phone is supposed to be shipped with to unlock the bootloader. If your device is a Chinese model it needs the China ROM, if it's the Global model it needs the Global ROM." (ChinaMobileMag)
Click to expand...
Click to collapse
"avoid flashing any firmware or any MIUI ROM which is older than what you're using now otherwise you'll brick your device"
[FAQ][Anti-Rollback] All your questions are answered here
aIecxs said:
"avoid flashing any firmware or any MIUI ROM which is older than what you're using now otherwise you'll brick your device"
[FAQ][Anti-Rollback] All your questions are answered here
Click to expand...
Click to collapse
Anti rollback is not related to this error. But i have tried with latest version of MIUI beta -8.9.20. It did not work. Also tried it on the latest global stable. Still no result.
Just heard that Riva has started receiving Oreo in china devepoper which means it will come to global very soon. I can only hope that this issue of "Current........this device" gets resolved after this major update. Fingers crossed.:fingers-crossed:
adityam0338 said:
Just heard that Riva has started receiving Oreo in china devepoper which means it will come to global very soon. I can only hope that this issue of "Current........this device" gets resolved after this major update. Fingers crossed.:fingers-crossed:
Click to expand...
Click to collapse
I strongly believe that you need to wait for a month at least before you can unlock your Redmi 5A again(unless you have done something that Xiaomi decided to lock it for good). I accidentally locked my bootloader after doing a"flash and lock" on the MIUI DEV rom, then unlocked 2nd time after 32+ days, while on the DEV Rom
I need authorized account to flash rom in edl mode pleas help me my phone dead and xiome store refused to fix it any on help me pleas i tried to get fis boot after unplug battry but did't get only edl mode i don't have any cash to fix it only have my frind laptop only buc get downgred if any one can help i will pray for him
How did you brick? Tell us more details...
alexmanu1 said:
How did you brick? Tell us more details...
Click to expand...
Click to collapse
Go back by wrong in android 9 from android 10 with twrp i was in miui 12 beta and wint to go back in 11 globel get by wrong android 9 rom
alexmanu1 said:
How did you brick? Tell us more details...
Click to expand...
Click to collapse
Help me pleas i don't have any mony to pay even 10$ to any one
Go to another service centre and say that it happened after a OTA update. You may have a chance if someone which has an authorized account will help you for free. But this is a low chance...
alexmanu1 said:
Go to another service centre and say that it happened after a OTA update. You may have a chance if someone which has an authorized account will help you for free. But this is a low chance...
Click to expand...
Click to collapse
Im in egypt he did't khow how do it in all
If go to all egypt i will get no chans to any one khow about i tell him
alexmanu1 said:
Go to another service centre and say that it happened after a OTA update. You may have a chance if someone which has an authorized account will help you for free. But this is a low chance...
Click to expand...
Click to collapse
And my phone opned
Any one trusted to pay him for authrzied account i can pay only 15$ all i got pleas i don't have spaer phone and i looking for work
Medolokk said:
I need authorized account to flash rom in edl mode pleas help me my phone dead and xiome store refused to fix it any on help me pleas i tried to get fis boot after unplug battry but did't get only edl mode i don't have any cash to fix it only have my frind laptop only buc get downgred if any one can help i will pray for him
Click to expand...
Click to collapse
Have look at this thread New Redmi Note 8 Pro Unbrick/Hardbrick Removal method- No authorized Service Account I managed to fixed my phone this way. Here is my story there.
Please note I had unlocked bootloader and applied Anti-brick solution PRIOR problem happened, might be why.
Also note you need image for your device regional favor.
Hope this helps.
Good luck!
Muad.Dib said:
Have look at this thread New Redmi Note 8 Pro Unbrick/Hardbrick Removal method- No authorized Service Account I managed to fixed my phone this way. Here is my story there.
Please note I had unlocked bootloader and applied Anti-brick solution PRIOR problem happened, might be why.
Also note you need image for your device regional favor.
Hope this helps.
Good luck!
Click to expand...
Click to collapse
I tried it but only need the authrzied account i don't have any way to work it
Medolokk said:
I tried it but only need the authrzied account i don't have any way to work it
Click to expand...
Click to collapse
Strange, when I tried this method to flash my phone back to stock, I only had to login with my regular Mi Account when asked, also had logged in the MiFlash Pro app, had opened MiFlash tab from there too, and I could flash using SP Flash Tools provided in the link. I had to try a few times to make it worked staying logged in the mi account (kept the pop up windows on top of the screen). I had phone connected before it rebooted and flashing started straight away. Make sure you follow the guidelines as being given.
Anyway not more I can do to help if that does not work for you good luck!
Muad.Dib said:
Strange, when I tried this method to flash my phone back to stock, I only had to login with my regular Mi Account when asked, also had logged in the MiFlash Pro app, had opened MiFlash tab from there too, and I could flash using SP Flash Tools provided in the link. I had to try a few times to make it worked staying logged in the mi account (kept the pop up windows on top of the screen). I had phone connected before it rebooted and flashing started straight away. Make sure you follow the guidelines as being given.
Anyway not more I can do to help if that does not work for you good luck!
Click to expand...
Click to collapse
Thx fore help if you knhow one can give me account with 10 $ or 15$ it will be greet help
Follow and complain here.
Let ASUS know their bootloader implementation is VERY NOT FRIENDLY to us. I've been modding my Android devices since the Android 2 era and this is the first time I encountered an UNOFFICIALLY UNRECOVERABLE state which is a HORRIBLE experience.
Me? Have played with
Samsung(S5 to S9 and Tab/Odin is a good thing)
XiaomiRedmiPoco(Main device for me today, very modder friendly and robust)
Huawei(Remember when they allow applying for BL unlock?)
Apple(LOL jailbreak from A4 SoC until iPhone X(meantime Samsung S8 looks gorgeous) lost my interest)
And various small brands or exited market big brands(honorable mention Lenovo LePhone C101. My first smart device/Android and received big community support at the good old time)
ASUS. Fix your buggy BL. Fix your policy. Release everything we need to fix OUR DEVICES of OURSELVES. Just ONE step closer to perfect.
Just imagine how stupid is this:
Everytime you want to update you operating system, your UEFI/BIOS firmware might break.
And worse, that you don't have free official resources to fix it?
And can it be worse? Yes! Your Warranty is maybe void because you may unlocked bootloader, now supposedly only ASUS service center have the file to fix it.
Ha now it's interesting. That's the era of ANTITRUST. Even Apple won't do it(Worst case DFU, easily fixable using OFFICIAL iTunes).
WT*?
yeah dude i'm bricked up rn
Paid here, paid there.
Yeah sure.
Exploit people.
Perhaps instead of ranting about asus, you could tell us what you have done exactly to brick your device, and someone might be able to help you ? can you get into fastboot at all?
EDIT: quoted content removed.
Never use this firmware, because it has not been modified, 100% of fingerprints and IMEI will be lost after use. You need to modify the firmware before you can flash it.
mahdibassam said:
Perhaps instead of ranting about asus, you could tell us what you have done exactly to brick your device, and someone might be able to help you ? can you get into fastboot at all?
Click to expand...
Click to collapse
Trying to flash img unpacked from update zip. Which you should NOT do. Because Android 12 dynamic partition.
iMoc said:
Trying to flash img unpacked from update zip. Which you should NOT do. Because Android 12 dynamic partition.
Click to expand...
Click to collapse
Ok, yes you definitely should not do that
So just wondering, you went and grabbed some img files and made the decision to flash them, why is this any fault of asus?
mahdibassam said:
Ok, yes you definitely should not do that
So just wondering, you went and grabbed some img files and made the decision to flash them, why is this any fault of asus?
Click to expand...
Click to collapse
1\ The fastboot code in their bootloader have bugs, any CORRECT command you type can easily break bootloader then stuck you in 9008.
2\ The normal update method failed because THEIR UPDATER did do things wrong.
3\ They refuse to provide official ROM to let yourself fix it. SEND IT TO ME TO FIX IT, AND I MIGHT CHARGE YOU SOME.
....\
N\ You go talk to Apple about it because they are experts about saying YOU USED IT WRONG.
Anyone asked for help gets it for free so far.
All devs on my chat group agree at least fastboot flashable should be available on the official download page.
MOD EDIT: off topic content removed
Did you manage to unbrick your phone?
I managed to semi hard brick my phone. Can get into fastboot but unable to start recovery mode from fast boot and phone doesn't show up from adb devices.
I guess I'll start a new thread but any tips?
insideoft said:
Did you manage to unbrick your phone?
I managed to semi hard brick my phone. Can get into fastboot but unable to start recovery mode from fast boot and phone doesn't show up from adb devices.
I guess I'll start a new thread but any tips?
Click to expand...
Click to collapse
If you can boot into fastboot you can just flash the RAW ROM file available a few days ago. It's not bricked in this case.
Moderator Information
Hello everyone,
I have cleaned the thread from off topic contents and posts. Please focus on problem solving related discussion, not finger pointing or flaming each other. We all come here to solve the issues and learn some new stuffs.
Thanks.
iMoc said:
If you can boot into fastboot you can just flash the RAW ROM file available a few days ago. It's not bricked in this case.
Click to expand...
Click to collapse
Sorry long time ago since I was into this stuff previosly.
That fixed it, thanks for the help!
same here
hello people, I have a black screen after flashing the FW and can't get out of it.
Battery is fully charged
Pressing key combinations doesn't help.
when the mobile phone is connected to the pc, there is a brief message that a device has been connected to the pc.
please urgently for help
thx
neroes said:
Pressing key combinations doesn't help.
Click to expand...
Click to collapse
Fastboot mode not working?
NOSS8 said:
Fastboot mode not working?
Click to expand...
Click to collapse
No ... pressing VOL+down dosnt work
fastboot devices
negativ
neroes said:
No ... pressing VOL+down dosnt work
fastboot devices
negativ
Click to expand...
Click to collapse
I sent you a PM
So just a Black Screen? No Recovery or Fastboot?
You might have to flash a ROM via EDL Mode... The unfortunate thing though is that it will cost you money, unless you still have Warranty...
You said your PC briefly says that your phone got connected. In Device Manager, does it say "Qualcomm 9008" ? That would indicate that your phones' SOC detected that the Bootloader isn't working, and so, instead booted into the EDL Mode (Emergency DownLoad Mode), which is a read-only Mode inside the SOC itself.
cyanGalaxy said:
So just a Black Screen? No Recovery or Fastboot?
You might have to flash a ROM via EDL Mode... The unfortunate thing though is that it will cost you money, unless you still have Warranty...
You said your PC briefly says that your phone got connected. In Device Manager, does it say "Qualcomm 9008" ? That would indicate that your phones' SOC detected that the Bootloader isn't working, and so, instead booted into the EDL Mode (Emergency DownLoad Mode), which is a read-only Mode inside the SOC itself.
Click to expand...
Click to collapse
is now fixed, yes was in EDL mode.
it's a shame that I didn't know about the guarantee... the phone is only 6 months old... now I've paid $25 to "unlock" it
neroes said:
is now fixed, yes was in EDL mode.
it's a shame that I didn't know about the guarantee... the phone is only 6 months old... now I've paid $25 to "unlock" it
Click to expand...
Click to collapse
Sorry about that.
What did you do to make that happen? From which FW to which FW did you upgrade to?
cyanGalaxy said:
Sorry about that.
What did you do to make that happen? From which FW to which FW did you upgrade to?
Click to expand...
Click to collapse
My mistake was to listen to someone else and downgrade the firmware
neroes said:
My mistake was to listen to someone else and downgrade the firmware
Click to expand...
Click to collapse
that is weird because noting shoould happen when you change firmware.did you use twrp or adb sideload via recovery?
neroes said:
My mistake was to listen to someone else and downgrade the firmware
Click to expand...
Click to collapse
Downgrading is not a problem if the instructions are followed correctly.
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
This is why it is important to give as much detail as possible when asking a question.
If you had specified that the phone was less than 6 months old, I would have directed you to the warranty as suggested by CyanGalaxie.
Currently the guarantees are under contracted by Xiaomi and the returns are very bad (loss of the phone, broken screen, long delays, etc.).
In your case you got your phone back in 15 minutes, maybe it's better that way.
So I'm satisfied that it really worked within half an hour to "unlock" my cell phone again instead of sending it in etc.
I just tried to downgrade via sideload. that led to the EDL
All in all I'm glad that my cell phone is working again ... I'm just annoyed because I've been playing around with all sorts of cell phones for over 10 years and I couldn't figure it out myself
neroes said:
So I'm satisfied that it really worked within half an hour to "unlock" my cell phone again instead of sending it in etc.
I just tried to downgrade via sideload. that led to the EDL
All in all I'm glad that my cell phone is working again ... I'm just annoyed because I've been playing around with all sorts of cell phones for over 10 years and I couldn't figure it out myself
Click to expand...
Click to collapse
The best way to downgrade is to use Miflash or the bat file (Fastboot rom)included in the rom folder to avoid ARB.
Phones have since changed, notably with dynamic and A/B partitions.
If you were trying to downgrade/upgrade the FW due to requirement/recommendation by your Custom ROM, you can simply flash the FW inside TWRP/OrangeFox.
cyanGalaxy said:
If you were trying to downgrade/upgrade the FW due to requirement/recommendation by your Custom ROM, you can simply flash the FW inside TWRP/OrangeFox.
Click to expand...
Click to collapse
This method to have the right firmware for for example an aosp rom does not always work sometimes it is necessary to flash the full rom.
For a version change on a stock rom use fastboot roms which contain all the imgs.
Yeah, stupid anti-rollback thing. Threads like these make me wish someone already unlocks the EDL flashing. I heard developers need some source code or something for it, I'm not sure. But that needs to happen ASAP.
It's totally evil to keep EDL restricted.
user0u said:
Yeah, stupid anti-rollback thing. Threads like these makes me wish someone already unlocks the EDL flashing. I heard developers need some source code or something for it, I'm not sure. But that needs to happen ASAP.
It's totally evil to keep EDL restricted.
Click to expand...
Click to collapse
For ARB okay but for EDL mode it's just a matter of security, you lose or your phone is stolen and just flash in edl mode and the phone is yours, no.
Then the guy will only be able to flash AOSP roms as he will be blocked by the Xiaomi account.
Note that this only concerns Qualcomm Socs,Mediatek are more less secure.
@NOSS8 We are modders and tinkerers here man. We were doing just fine before these restrictions. These restrictions have been added less for "security" and more to take control away from the end users anyway.
user0u said:
@NOSS8 We are modders and tinkerers here man. We were doing just fine before these restrictions. These restrictions have been added less for "security" and more to take control away from the end users anyway.
Click to expand...
Click to collapse
Not everyone is like you or me, there are thieves and crooks,otherwise we would be in a perfect world.
user0u said:
Yeah, stupid anti-rollback thing. Threads like these make me wish someone already unlocks the EDL flashing. I heard developers need some source code or something for it, I'm not sure. But that needs to happen ASAP.
It's totally evil to keep EDL restricted.
Click to expand...
Click to collapse
There are patched Firehose files (for QPST) on the internet (apparently circumvents the required Account authorisation). I can't provide a link, but you can google it.
But I'm not sure if those work, because I couldn't find one for Poco F3, and so I too had to pay 25$
It's very annoying that people buy into these pseudo-security lies we're getting fed so often (especially Apple Users). People don't realise this is not about protecting consumers, but simply for lé money. It has always been about the money.
Xiaomi locked the EDL Mode, because people kept buying their phones from China and import them to EU/USA, flash software with GMS and sell them here.
And locking EDL Mode causes more people to pay for Xiaomi Service Centres. xddd
I wish people would just have a healthy amount of criticism and not fanboy for any company, except for Valve. Valve is cool. Valve is love
Can someone test if this firehose works for EDL flashing? I would've done it myself but I don't know how to properly use it nor have I backed up my phone.
Thanks.
EDIT: It does not work
@jefffrom Am I missing something?
Where did you get it from?
Does it allow us to flash a ROM in EDL Mode without needing a Xiaomi Authorised Service Centre Account?
From my understanding these can be used in Mi Flash and QPST / QFIL
When you download a Stock MIUI Fastboot ROM, it contains those files, but for some devices there are modded Firehose-files available.
cyanGalaxy said:
Does it allow us to flash a ROM in EDL Mode without needing a Xiaomi Authorised Service Centre Account?
Click to expand...
Click to collapse
It should. That's the point of a patched firehose. But I need someone to test it, as I do not know how to use it with QFIL. And I don't want to mess up since I am too lazy to back up my phone.
A paid source was generous enough to provide it for free.
If someome tries it, please confirm if it's working or not in this thread.
Thanks.
I think no one will try it because if it doesnt work, there is a chance of hard bricking your phone
ApexPrime said:
I think no one will try it because if it doesnt work, there is a chance of hard bricking your phone
Click to expand...
Click to collapse
Will it? Won't it just refuse to flash at the beginning?
Who knows. It might or it might not. Point is, most people wont bother flashing it because the risk is too high and the reward doesnt attract much people. If you're really interested, i would request you to try it yourself and post the results here. That way, you would be helping the community as well in case someone needs the file in the future.
I'll save the Modded Firehose. If someone has got a hardbricked Poco F3, I'll send them the Modded Firehose and assist them with QPST.
If it works for them then, I'll let you guys know here.
I had a hardbricked Poco F3 and did try to use QPST, but couldn't find any patched Firehose-files on the Net.