Related
i was flash pixel caf os but sudenly i get error system has destroy and that tym i connect my device fastboot its show when i command fastboot devices but after fail of some try to flash stock rom mi flash now my device not show on fastboot mode when i command fastboot devices its show nthg please its mah mom phone she angry on me............:crying::crying:
yuvi15 said:
i was flash pixel caf os but sudenly i get error system has destroy and that tym i connect my device fastboot its show when i command fastboot devices but after fail of some try to flash stock rom mi flash now my device not show on fastboot mode when i command fastboot devices its show nthg please its mah mom phone she angry on me............:crying::crying:
Click to expand...
Click to collapse
Can you get to fastboot or recovery mode right now?
If you can, try install Peter twrp & install official rom from twrp.
If you can't.... Maybe you need to test point your phone.
Let's wait for another better answer, because I'm still noob & my only experience is revive my super dead remi1s with testpoint & root my rm7pro
pau.tan said:
Can you get to fastboot or recovery mode right now?
If you can, try install Peter twrp & install official rom from twrp.
If you can't.... Maybe you need to test point your phone.
Let's wait for another better answer, because I'm still noob & my only experience is revive my super dead remi1s with testpoint & root my rm7pro
Click to expand...
Click to collapse
than for help but i fixiedit myself it's prblm in my cable i changed the cable and try solution which given in previous post system has destroy see there uh will see solution thax☺
yuvi15 said:
than for help but i fixiedit myself it's prblm in my cable i changed the cable and try solution which given in previous post system has destroy see there uh will see solution thax☺
Click to expand...
Click to collapse
Nice! Goodluck bro
hi Guys
I'm in the forum for a very long time as an assistant helper now it has got me hard I have an Axon 10 Pro with curly boot loader and trying to flash a TWRP I have somehow the device or SotA and SlotB have shrunk. The Axon Bootet permanently in 0.5 second cycle and also a FULL Restot or FULL Flash with EDL Tool has not changed anything. Likewise, a new flash about fastboot with the command (fastboot flash boot_a boot.img) the same for boot_b then try with fastboot command (fastboot boot twrp.img) Recovery to start without success fastboot erase boot_a and boot_b has also flashing new but it does not start. Always bootloop:crying::crying::crying::crying:
the Axon 10 pro is back because he had no backup of all we had from my Axon 10 pro made a backup with the edl tool (Backup all) and have then copied his efs backup purely and then this with then on the Axon 10 flashed the Axon 10 pro is now back
Where did you get the twrp from?
From udev
On his donload page
https://forum.xda-developers.com/showpost.php?p=80156866&postcount=3
I had a bootloop issue as well and even though I reflashed using the EDL tool, it doesn't erase and the errors remained, but when I entered EDL mode and reflashed using the Xiaomi Flash Tool, storage was completely erased and the device was flashed cleanly and booted correctly.
I've encountered a similar issue with my Axon (2020U version). I can boot into EDL but nothing else (no fastboot, recovery, etc.). I previously had TWRP up and running successfully, not sure what happened.
Is there a full EDL zip or similar that I can flash to return everything to stock? I tried restoring with the EDL tool but with no success
jbeaulieu said:
I've encountered a similar issue with my Axon (2020U version). I can boot into EDL but nothing else (no fastboot, recovery, etc.). I previously had TWRP up and running successfully, not sure what happened.
Is there a full EDL zip or similar that I can flash to return everything to stock? I tried restoring with the EDL tool but with no success
Click to expand...
Click to collapse
The reason the EDL tool may not work is that is doesn't have the capability to erase. The boot loop that occurs is usually due a corrupt bootfile. Use the MiFlash fastboot recovery tool. Make sure to select the clean all button at the bottom. Place your phone in EDL mode. Hit refresh to make sure your phone is detected. Select the EDL file and then hit flash.
jim262 said:
The reason the EDL tool may not work is that is doesn't have the capability to erase. The boot loop that occurs is usually due a corrupt bootfile. Use the MiFlash fastboot recovery tool. Make sure to select the clean all button at the bottom. Place your phone in EDL mode. Hit refresh to make sure your phone is detected. Select the EDL file and then hit flash.
Click to expand...
Click to collapse
Apologies for my ignorance - what exactly am I flashing? I see the "clean all" radio button, but I'm not sure what EDL package to flash after selecting that option - is there a 2020U package floating around that I'm not seeing?
jbeaulieu said:
Apologies for my ignorance - what exactly am I flashing? I see the "clean all" radio button, but I'm not sure what EDL package to flash after selecting that option - is there a 2020U package floating around that I'm not seeing?
Click to expand...
Click to collapse
The EDL package, use the same EDL package that you used with the EDL tool. Just select the "clean all" radio button. Select the path to the EDL , hit refresh once phone, in EDL mode, is detected, hit flash.
jim262 said:
The EDL package, use the same EDL package that you used with the EDL tool. Just select the "clean all" radio button. Select the path to the EDL , hit refresh once phone, in EDL mode, is detected, hit flash.
Click to expand...
Click to collapse
Okay, I'm trying to use MiFlash to restore the backup I took through the original EDL tool. The MiFLash tool is only timing out with a "cannot receive hello packet" - was this something you encountered as well?
jbeaulieu said:
Okay, I'm trying to use MiFlash to restore the backup I took through the original EDL tool. The MiFLash tool is only timing out with a "cannot receive hello packet" - was this something you encountered as well?
Click to expand...
Click to collapse
I did attempt to flash the wrong EDL file (They are region and device specific) and received that error. I have the Chinese version and once I downloaded the correct EDL file, I had no issues I have even maintained an unlocked boot loader, flashed Magisk and taken OTAs.
jim262 said:
I did attempt to flash the wrong EDL file (They are region and device specific) and received that error. I have the Chinese version and once I downloaded the correct EDL file, I had no issues I have even maintained an unlocked boot loader, flashed Magisk and taken OTAs.
Click to expand...
Click to collapse
Ah, okay. I have the US version - A2020U. Unless I'm mistaken, it looks like there isn't a full EDL zip file available for my version yet, so I might be stuck
There were EDL files up, but apparently they were taken down for some reason.
in the russians there are the 1.6 of the g model as edl (which one can use in a brick) but I do not know if this is synonymous with the u model as you would have to ask @Unjustified Dev or something
@MOD
I hope that the links are allowed here else delete please
1.6 g model edl
http://4pda.ru/forum/index.php?showtopic=965431&st=0#entry88768840
And the lonk too the forum
http://4pda.ru/forum/index.php?showtopic=965431
Chris axon 7 said:
in the russians there are the 1.6 of the g model as edl (which one can use in a brick) but I do not know if this is synonymous with the u model as you would have to ask @Unjustified Dev or something
@MOD
I hope that the links are allowed here else delete please
1.6 g model edl
http://4pda.ru/forum/index.php?showtopic=965431&st=0#entry88768840
And the lonk too the forum
http://4pda.ru/forum/index.php?showtopic=965431
Click to expand...
Click to collapse
Thanks for sharing these. @Unjustified Dev do you happen to know if the 1.6 2020G EDL would be able to be flashed to a 2020U model to recover from a brick? Or if not, is there a place to obtain the proper files, either here on the forums or via PM?
jim262 said:
I did attempt to flash the wrong EDL file (They are region and device specific) and received that error. I have the Chinese version and once I downloaded the correct EDL file, I had no issues I have even maintained an unlocked boot loader, flashed Magisk and taken OTAs.
Click to expand...
Click to collapse
Please share us the EDL file for the Chinese version.
has anyone found the US EDL file yet?
Futility's Forgotten Soldier said:
has anyone found the US EDL file yet?
Click to expand...
Click to collapse
Still waiting. I'm stuck on the EU version.
Please mods, I dont know if this post is in the correct forum. I'm exhausted after being hours trying to solve this issue and here is 2am. Feel free to move the thread wherever you think it suits better.
I posted the same message here: https://forum.xda-developers.com/k2...9t-pro-one-t4093255/post83029067#post83029067
I think that maybe this Mi MIX 2S forum is more suitable for asking for some help. This is the original message:
Yes I did. I feel like an ashole... The module is not for the MI MIX 2S, but I thought (yes, I told you, I'm an ashole, that being Magisk, it could be universal. For all smartphones with Magisk)
Is my fault, I know. I come here to beg for your help.
I had my Xiamo Mi MIX 2S with the last Xiaomi EU rom with MIUI 12, rooted with Magisk. Everything worked flawlessly.
Then I say that fantastic module: Screen Overclock. I thought, fantastic! I could have a lower refresh rate and that way save some battery... I did... And now I'm stuck in Fastboot.
I installed the latest official room with MiFlash following this tutorial: https://c.mi.com/oc/miuidownload/detail?guide=2
I even downloaded the last room from there (Global) as it says is the latest.
The biggest outcome is to boot into the official recovery. I tried to install TWRP and it install (fastboot flash recovery twrp-3.3.1-0-polaris.img ---> version 3.4 doesn't work either) but after that, I can't reboot into recovery. It comes back to Fastboot again.
Trying to boot the recovery with fastboot boot twrp-3.3.1-0-polaris.img throws the following error:
PHP:
Sending 'boot.img' (42476 KB) OKAY [ 1.219s]
Booting FAILED (remote: 'Failed to load/authenticate boot image: 00000050')
FAILED (remote: 'Failed to load/authenticate boot image: 00000050')
So I don't know what to do, and I do really need your help please.
I'll post this same message in the Mi MIX 2S board. Hopefully somebody who could imagine what went on, can give a helping hand.
Please help
Thank you all
Manu
So know is even worse.
For a reason I don't know, now I'm able to load adb sideload (pcsuite) but when entering in fastboot, inmediatly I can see a very small letters in the top left corner that say: "Press any key to shutdown"
Solved connecting the MI MIX 2S to a USB2 port rather than a USB3. Weird... At least I have again access to Fastboot
I dont think this have any solution. I managed to install via XiaomiADB sideload to the 99%
And at 99%... it stopped:
C:\Users\manu\Downloads\XiaomiADB>XiaomiADB.exe miui_MIMIX2SGlobal_V11.0.5.0.QDGMIXM_42f0653956_10.0.zip
* Miui sideload made by Francesco Tescari, updated 02 Feb 2018 *
* Checking device status *
* Getting recovery info *
* Creating file MD5 hash *
* Querying ota update server, attempt #0 *
Data partition format might not be necessary and will NOT be done automatically after installation.
If the device doesn't reboot or some apps crash after reboot, you need to manually format the device using "format-data" command!
* Starting sideload *
Sending file to the device... (~100%)
Checking file checksum...
Installing file on the device... (~99%)
* Sideload output: *
ERROR: Sideload error -> Unknown error during file installation
Installation FAILED!, press ENTER to exit
So I'll try to see tomorrow if you guys can help, but I don't see any option here...
Well, at least connecting it to a USB2 port seems that I Can, again, to fastboot without the small "Press any key to shutdown" message
So another question.
A guy in the other thread told me this:
kiran8631 said:
So, when I screwed my phone trying recoveries, I got stuck in FastBoot. no matter what I did, even Power + Vol Up got me to fastboot, and I had just wiped my OS, so I had nothing to boot into.
This happens when you wipe your SYSTEM and/or VENDOR partitions and choose reboot recovery, or flash an incompatible recovery.
After a lot of stressful minutes, scared half out of my mind. A guy named @Shivsom helped me.
Basically what he made me do was, Download his file vbmeta_dv_shivsom.img that is given below in attachments.
Then copy the twrp.img file and vbmeta_dv_shivsom.img file to my adb Folder.
Open the Command prompt in that folder, by clicking on the address bar of File Explorer and typing > cmd > then Enter
Type the instructions
Code:
fastboot flash vbmeta vbmeta_dv_shivsom.img
Then type, (Since my twrp image file was re-named to twrp.img, if you haven't done so, do it)
Code:
fastboot flash recovery twrp.img
Then press and hold Power and Volume Up till you feel the haptic feedback see the TWRP recovery
Click to expand...
Click to collapse
He attached a vbmeta.img. I've never heard of that before, by the way.
So I didn't flashed because I was afraid that this was for P20PRO too.
I downloaded this one too https://xiaomifirmware.com/download-link/?dlm-dp-dl=14341 which is also a vbmeta.img
So both files are 4.1kb. Comparing them with an online tool it turns out that the _dv_shivsom.img version is full of zeros, while the one in xiaomifirmware have data inside.
What should I do?
manudas said:
So another question.
A guy in the other thread told me this:
He attached a vbmeta.img. I've never heard of that before, by the way.
So I didn't flashed because I was afraid that this was for P20PRO too.
I downloaded this one too https://xiaomifirmware.com/download-link/?dlm-dp-dl=14341 which is also a vbmeta.img
So both files are 4.1kb. Comparing them with an online tool it turns out that the _dv_shivsom.img version is full of zeros, while the one in xiaomifirmware have data inside.
What should I do?
Click to expand...
Click to collapse
I had tried this my k20 pro when I was in same situation and it worked and also I think u should also try this it will work
kiran8631 said:
I had tried this my k20 pro when I was in same situation and it worked and also I think u should also try this it will work
Click to expand...
Click to collapse
Thank you
I did it, and unfortunately no more recovery, no more fastboot.
The led flashes a couple of times and nothing else. Absolutely broken. I'm not blaming you, you only tried to help
Time to save for another phone
Thank you guys anyway
Take it to service center
manudas said:
Thank you
I did it, and unfortunately no more recovery, no more fastboot.
The led flashes a couple of times and nothing else. Absolutely broken. I'm not blaming you, you only tried to help
Time to save for another phone
Thank you guys anyway
Click to expand...
Click to collapse
If you get fastboot working again I can give you mix2s vbmeta
cvamoose said:
If you get fastboot working again I can give you mix2s vbmeta
Click to expand...
Click to collapse
Thank you, but the only reaction of the phone when I press any combination of buttons is to blink the led a couple of times. So I don't think that now it could be sorted out. Anyway, why don't you attach it here so if anybody in the future needs it, don't download the wrong one?
Try to enter EDL mode. Then flash latest MIUI global fastboot ROM with miflash. It should working
reevdre said:
Try to enter EDL mode. Then flash latest MIUI global fastboot ROM with miflash. It should working
Click to expand...
Click to collapse
Even if he got into edl mode he cant flash anything unless he has an authorized account. Also to get into edl at his current state the back of phone must come off and certain spots need to be shorted.
reevdre said:
Try to enter EDL mode. Then flash latest MIUI global fastboot ROM with miflash. It should working
Click to expand...
Click to collapse
Hey, thank you for your answer.
As I cannot access either to the Recovery or the Fastboot, I dont know how to enter EDL to be honest... I tried the vol- + power and connecting the cable but windows didn't recognise anything
Any other way?
You have to press vol- and vol+ at once and connect USB cable.
If it doesn't work I believe that test points should work. To do that you need to remove back cover then short two test points that are below camera using for instance scissors with small ends (this may help https://www.youtube.com/watch?v=koj3cGnhic0) and having both points connected with each other connect USB cable.
manudas said:
Hey, thank you for your answer.
As I cannot access either to the Recovery or the Fastboot, I dont know how to enter EDL to be honest... I tried the vol- + power and connecting the cable but windows didn't recognise anything
Any other way?
Click to expand...
Click to collapse
If you access edl mode contact me with a private message
Hi,
My phone is actually dying and I don't know how to recover it this time.
I had a perfectly working setup with latest weekly update of Xiaomi eu MIUI , TWRP and magisk, and know even fastboot is not responding.
I usually don't like when people say that, but I think a malware did it, as my apps started not responding in a few minutes, and the reboot finished the job.
Now it won't boot anymore, when it's plug the notification led is red, and fastboot is detected but commands are stuck.
Also, TWRP is neither accessible from "power + vol up" since last miui eu update, nor from fastboot since the "accident"
If someone have any advice on how to unlock fastboot, flash back the rom or any other way to recover my phone, please help
Also, if you want to know the rest of the story, it's here...
I was using my phone as usual, trying to setup a bridge openvpn connection. (like everyone :laugh: )
The issue is that the only app claiming to do that isn't free, and I want to be sure I can make it work before spending any money.
So I tried to patch it and different apks (I know it's bad...), and while transferring an apk from my laptop to my phone, I noticed the transfer was kinda slow for a few seconds (nothing worrying, but unusual)
Then some of my apps didn't want to launch and, back to the app drawer, most of my apps had their package names, with no icons...
It was at this moment Jackson I knew I screwed up...
I then tried rebooting, and the phone stayed a few minutes on the MIUI screen, then shut off.
After a reboot, I noticed the red led, the absence of boot animation, and the bootloop.
Obviously, if I had a fastboot access, it would be easy to boot on TWRP and then flash back my rom properly but I can't...
EDIT: to make this clearer (I know the post above is a little bit messy), I have the following issues:
- No access to TWRP (for flashing)
- Fastboot is accessible but broken enough so flash/boot to twrp is not possible
- I just though of EDL mode, but "fastboot oem edl" doesn't seems to work
- I prefer to avoid opening my phone (to access to the EDL test points)
EDIT2: You can't flash anything in EDL mode without specific autorisations from xiaomi, so this mode becomes way more useless than on my previous Mi A1. I managed to miraculously flash some things by using miflash in fastboot mode. Maybe working on a windows os instead of gnu/linux helped somehow...
Thelm76 said:
Hi,
My phone is actually dying and I don't know how to recover it this time.
I had a perfectly working setup with latest weekly update of Xiaomi eu MIUI , TWRP and magisk, and know even fastboot is not responding.
I usually don't like when people say that, but I think a malware did it, as my apps started not responding in a few minutes, and the reboot finished the job.
Now it won't boot anymore, when it's plug the notification led is red, and fastboot is detected but commands are stuck.
Also, TWRP is neither accessible from "power + vol up" since last miui eu update, nor from fastboot since the "accident"
If someone have any advice on how to unlock fastboot, flash back the rom or any other way to recover my phone, please help
Also, if you want to know the rest of the story, it's here...
I was using my phone as usual, trying to setup a bridge openvpn connection. (like everyone :laugh: )
The issue is that the only app claiming to do that isn't free, and I want to be sure I can make it work before spending any money.
So I tried to patch it and different apks (I know it's bad...), and while transferring an apk from my laptop to my phone, I noticed the transfer was kinda slow for a few seconds (nothing worrying, but unusual)
Then some of my apps didn't want to launch and, back to the app drawer, most of my apps had their package names, with no icons...
It was at this moment Jackson I knew I screwed up...
I then tried rebooting, and the phone stayed a few minutes on the MIUI screen, then shut off.
After a reboot, I noticed the red led, the absence of boot animation, and the bootloop.
Obviously, if I had a fastboot access, it would be easy to boot on TWRP and then flash back my rom properly but I can't...
Click to expand...
Click to collapse
Hi
I had a similar situation
I comfigured an app and during configuration the phone start framing
I rebooted and stucked at miui screen
I tried to reboot in recovery ,nothing
I downloaded latest miui for europe 12.0.3 and mi flash
For me fastboot worked to flash latest firmware from xiaomi
And now is working and my bootloader is locked
Thelm76 said:
Hi,
My phone is actually dying and I don't know how to recover it this time.
[/hide]
Click to expand...
Click to collapse
Xiaomi.eu has TWRP issue...
Go to https://www.androidfilehost.com/?w=files&flid=50678 and find your recovery (lmi) and flash it with fastboot and boot to recovery.
fastboot flash recovery twrp.img
fastboot boot twrp.img
Now download the new ROM 20.10.16, push it to the internet storage and install it dirty... Wipe Cache and reboot....
My problem is almost same, i unlock the bootloader to flash xiaomi.eu rom from global rom, unlocking and flashing custom recovery was done smoothly, when i tried to flash xiaomi.eu rom version 12.0.8 it booted back to recovery, and i format the data partition and booted to system, and same result. I tried global its same result.
Then i tried miflash tool, " antirollback error ".
Now i don't know what to do. Hope my precious poco f2 pro is not bricked, coz i can still manage to boot in custom recovery, and can use miflash tool but error.
Can someone out there help me please. Thanks in advance.
Eldybug said:
My problem is almost same, i unlock the bootloader to flash xiaomi.eu rom from global rom, unlocking and flashing custom recovery was done smoothly, when i tried to flash xiaomi.eu rom version 12.0.8 it booted back to recovery, and i format the data partition and booted to system, and same result. I tried global its same result.
Then i tried miflash tool, " antirollback error ".
Now i don't know what to do. Hope my precious poco f2 pro is not bricked, coz i can still manage to boot in custom recovery, and can use miflash tool but error.
Can someone out there help me please. Thanks in advance.
Click to expand...
Click to collapse
Since you have access to a properly working fastboot and recovery, I believe there is always a way to recover your phone.
I'll be glad to help you but for now, I'm more focused on my issue.
Only thing, while using miflash, be careful to never lock your bootloader since you would have to open your phone to access EDL mode in case of bootloop
(but you can lock it afterwards if you want)
Enricosteph said:
Xiaomi.eu has TWRP issue...
Go to https://www.androidfilehost.com/?w=files&flid=50678 and find your recovery (lmi) and flash it with fastboot and boot to recovery.
fastboot flash recovery twrp.img
fastboot boot twrp.img
Now download the new ROM 20.10.16, push it to the internet storage and install it dirty... Wipe Cache and reboot....
Click to expand...
Click to collapse
Well, the main issue here is that fastboot seems to be broken too...
i found this for you on the LOS rom for poco f2 pro (am not the autor) this is for the "Anti-rollback error" (i hope that can help you):
romabah said:
Gentlemen with EU versions of Poco F2 pro, could you help me out?
Right now i am running 12.0.2.0 QJKEUXM.
To flash Lineage i first need to flash MIUI V12.0.3.0.QJKMIXM via MiFlash. I tried to do that but got an Anti-rollback error.
Checking via fastboot i saw that my phones anti rollback value is 1, but MIUI V12.0.3.0.QJKMIXM firmware has an anti rollback of 0.
Some folks say to delete first 5-6 lines in text editor from .bat file, but at the same time people tell everywhere to NOT flash firmware with lower value that your current anti rollback.
Any advice? How did other EU folks fix this?
Edit: I fixed it! I will NOT and cannot claim that this will fix all rollback error's, but it fixed mine.
0) This is applicable to fastboot version of MIUI V12.0.3.0.QJKMIXM (aka tgz file that you need to extract twice)
1) Move the extracted firmware directory imi_global_images_V12.0.3.......ets.ets. ( map with flash_all.bat, images ) to C: directory and rename to something short, like xiaomiFirm.
This will solve a lot of weird error's as MiFlash doesnt like long directories
2) Within the moved map open flash_all.bat with text editor and delete everything starting and including "::check anti_version" to and including "echo %..."
This removes the anti rollback check somehow. The reason for only editing flash_all.bat is because this is the .bat file that is run when you choose clean all option in MiFlash, i assume you dont want to clean all and lock now do you?
3) After finishing flashing mine gave error Not catch checkpoint flash is not done, but booted normally. Gave me a heart attack.
Sanity check: When running cmd "fastboot getvar anti" it returned "anti: 1"
Meaning i just flashed a ROM with anti of 0 on a phone with a anti value of 1. At least i believe so.
In any case, thank all for giving feedback for other ways of fixing this.
Click to expand...
Click to collapse
I'll try to make a type C deep flash cable to flash fastboot, and edit this message to explain if this works
Thelm76 said:
Well, the main issue here is that fastboot seems to be broken too...
Click to expand...
Click to collapse
Try to hold down only Vol Down and connect it to your computer
Enricosteph said:
Try to hold down only Vol Down and connect it to your computer
Click to expand...
Click to collapse
I don't know if this was my cable or fastboot oem edl, but windows recognised the phone as qualcomm qdloader 9008. I'll now try to update fastboot, install twrp and check the extent of the damages.
Fangstergangsta said:
i found this for you on the LOS rom for poco f2 pro (am not the autor) this is for the "Anti-rollback error" (i hope that can help you):
Click to expand...
Click to collapse
Indeed, OP, try to flash everything from the start thep by step.
You must stop therapeutic relentlessness!!!
Just plug out the charger and let him die softly...
Put him back in his sweet box after his last breathe
Bury him in your garden with a decent burial : he deserve it!!!!
It's HIS TIME, dude....
Regards
Mastakony said:
You must stop therapeutic relentlessness!!!
Just plug out the charger and let him die softly...
Put him back in his sweet box after his last breathe
Bury him in your garden with a decent burial : he deserve it!!!!
It's HIS TIME, dude....
Regards
Click to expand...
Click to collapse
Haha it's not therapeutic relentlessness when you're sure it will live again in a few days (and fully working!)
It just need a good memory wipe and android replacement
As I managed to get to emergency mode, I can now easily replace its software
EDIT: I didn't know that for these xiaomi devices, you need very specific autorisations to flash something with EDL... Fortunately, after messing around with miflash, I managed to unlock myself out of this infinite loop
As I managed to get to emergency mode, I can now easily replace its software
Click to expand...
Click to collapse
How are you going to flash the software?
Well,
By using edl mode and miflash, I got some errors as I was not authorised to do this operation, so I rebooted to fastboot, reused miflash, and I don't know which kind of magic did that but after some files flashed and an error, I was able to boot on TWRP. With this done, I tried to keep my data but didn't worked, and as I have everything constantly backup, I dicided to do a flashall.
now, I think I have a good MIUI base to flash MIUI EU back
Thelm76 said:
Well,
By using edl mode and miflash, I got some errors as I was not authorised to do this operation, so I rebooted to fastboot, reused miflash, and I don't know which kind of magic did that but after some files flashed and an error, I was able to boot on TWRP. With this done, I tried to keep my data but didn't worked, and as I have everything constantly backup, I dicided to do a flashall.
now, I think I have a good MIUI base to flash MIUI EU back
Click to expand...
Click to collapse
I have the same situation plus no fastboot or recovery at all.. Please tell me how did you resolve it?
ghannaiem said:
I have the same situation plus no fastboot or recovery at all.. Please tell me how did you resolve it?
Click to expand...
Click to collapse
Is the phone detected by the pc in usb?
And when you press power+ sound + or - What is happening?
NOSS8 said:
Is the phone detected by the pc in usb?
And when you press power+ sound + or - What is happening?
Click to expand...
Click to collapse
Yes , detected by usb but as qcom 9008,
And when holding down power button with + or - vol it restarts again to 9008 .
So it is not detected by any means, but only detected in edl mode
ghannaiem said:
Yes , detected by usb but as qcom 9008,
And when holding down power button with + or - vol it restarts again to 9008 .
So it is not detected by any means, but only detected in edl mode
Click to expand...
Click to collapse
how did it happen?
My imei got lost so I tried to flash eng rom through MI flash to fix it. It flashes all except certain file called (aop. Mbn) so I tried to flash it by cmd commands via fastboot and then the phone bricked.. No booting to fastboot anymore , no recovery. even with disconnecting battery and reconnecting again... Phone only recognized in Edl mode and when flashing through MI flash it asks for edl authorization... Account login successful but then flash fail cuz account is not authorized. So I think The only solution will be authorized account or patched prog_ufs file
Hi
My Redmi note 7 pro is bricked and it is in locked state .
I tried flashing fastboot rom from edl mode
But it gaves errors like
1) cannot receive hello packet
2)Only nop and sig tag can be recevied before authentication.
Please help me guys regarding this its been a while without my phone
AwesomeAman said:
Hi
My Redmi note 7 pro is bricked and it is in locked state .
I tried flashing fastboot rom from edl mode
But it gaves errors like
1) cannot receive hello packet
2)Only nop and sig tag can be recevied before authentication.
Please help me guys regarding this its been a while without my phone
Click to expand...
Click to collapse
Firstly, can you still boot into Fastboot mode? Secondly, you said you flash fastboot ROM from EDL, how you get into that EDL mode, and you're flashing by MiFlash right?
Clear the information, I might help you!
LinhBT said:
Firstly, can you still boot into Fastboot mode? Secondly, you said you flash fastboot ROM from EDL, how you get into that EDL mode, and you're flashing by MiFlash right?
Clear the information, I might help you!
Click to expand...
Click to collapse
Answers:
Yes it is going on fastboot mode
I got into edl mode by opening back Pannell of my device and i connected edl points
I am flashing via mi flash.
Actually in mi flash tool by mistake i flashed fastboot rom by selecting flash and lock.
Now when i flash the same by selecting clean all option by putting my device on edl mode
It show cannot receive hello packet.
This put me in this trouble
AwesomeAman said:
Answers:
Yes it is going on fastboot mode
I got into edl mode by opening back Pannell of my device and i connected edl points
I am flashing via mi flash.
Actually in mi flash tool by mistake i flashed fastboot rom by selecting flash and lock.
Now when i flash the same by selecting clean all option by putting my device on edl mode
It show cannot receive hello packet.
This put me in this trouble
Click to expand...
Click to collapse
Right, then you did the testpoint trick to get in EDL mode! Ofcourse now you can't use MiFlash with clean all to flash your device since your device is now in brick state. Only solution now is to find the factory images of your device, along with an authenticated prog file then use QFIL to force flash into device. You may inbox me if need further instructions!
i have the same issue pls help
LinhBT said:
Right, then you did the testpoint trick to get in EDL mode! Ofcourse now you can't use MiFlash with clean all to flash your device since your device is now in brick state. Only solution now is to find the factory images of your device, along with an authenticated prog file then use QFIL to force flash into device. You may inbox me if need further instructions!
Click to expand...
Click to collapse
Sir, I have exact same device and I am also stuck in edl mode. It looks there are no patched firehose files for violet. Is there any possible way you can help??