Hey so it's me again,
I wiped my phone via TWRP because I couldn't access it (went to type the correct password and it always said I was wrong), aaand, now it's stuck on the Mi logo screen.
Again, I looked up demos on how to fix it, and it hasn't worked. As far as I know, all I can get into is fastboot mode (won't even turn off).
My plan was to flash the default stable ROM onto it via MiFlash (as that's what most of the demos recommended) but I can't even get to that stage because I need to get into EDL mode, which I can't do.
Please help.
- Roisin.
Why would you need to get it into EDL? Put it in fastboot and open miflash, download the correct files and flash stock MIUI. You can get back to flashing other stuff after.
Honestly the only reason I thought that was because I read it somewhere, I'm not great with this phone (obviously) :')
Though I do remember trying that and it came up with an error, I'll try it again after school and I'll get back to you. Thanks.
WizardyNinja said:
Hey so it's me again,
I wiped my phone via TWRP because I couldn't access it (went to type the correct password and it always said I was wrong), aaand, now it's stuck on the Mi logo screen.
Again, I looked up demos on how to fix it, and it hasn't worked. As far as I know, all I can get into is fastboot mode (won't even turn off).
My plan was to flash the default stable ROM onto it via MiFlash (as that's what most of the demos recommended) but I can't even get to that stage because I need to get into EDL mode, which I can't do.
Please help.
- Roisin.
Click to expand...
Click to collapse
Happened to me too after wiping one of the partitions I shouldn't have when reinstalling CM. I just re-unlocked using the Mi Unlock program on Windows and then flashed CM13 back. Booted perfectly.
@banana_bender thanks for the tip!
I attempted to flash the ROM and it didn't work. All the tutorials with using MiFlash have a different version, it's confused me.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You need to select flash all at the bottom
harishmenace said:
You need to select flash all at the bottom
Click to expand...
Click to collapse
There's only "clean all", "save use data", and "clean all and lock" at the bottom. :/
*EDIT* nevermind I found it, gonna try it now!
WizardyNinja said:
Hey so it's me again,
I wiped my phone via TWRP because I couldn't access it (went to type the correct password and it always said I was wrong), aaand, now it's stuck on the Mi logo screen.
Again, I looked up demos on how to fix it, and it hasn't worked. As far as I know, all I can get into is fastboot mode (won't even turn off).
My plan was to flash the default stable ROM onto it via MiFlash (as that's what most of the demos recommended) but I can't even get to that stage because I need to get into EDL mode, which I can't do.
Please help.
- Roisin.
Click to expand...
Click to collapse
Yes, you need get into EDL to flash. Try this .cmd file on fastboot.. Wait until its boots to edl and red led pops up.. Then use ur MiFlash. Remmbr edl mode wont have any display. Just the red led indication.. Hope it helps
Sent from my Xiaomi Mi 5 using XDA Labs
Related
Hello friends, I hope you are well. I am writing to everyone to see if anyone can help me with this big problem.
Yesterday install the Rom Pixel Experience, all good, all the steps to perfection and others, had microSD at that time so flash the boot.img by Fastboot. It seems to install the Boot.img in the Recovery TWRP partition, or something like that. Because I do not have the Recovery either, when I try to go to the recovery, the window "Bootloader Unlocked" appears, but it does not take me anywhere, only to the boot of the rom, it is something very strange and the truth scares me. I clarify: I can not access the Fastboot, nor the download mode, nor the recovery, because it does not.
There will be another way: ????
PLEASE IF SOMEONE CAN HELP ME, FIND ANOTHER METHOD TO ENTER THE FASTBOOT OR DOWNLOAD MODE, THE SOLUTION THAT WORKS WILL PAY ME WELL TO THE PROPONGA, PLEASE, I DO NOT WANT TO LOSE MY MOBILE, I BUY IT WITH A LOT OF EFFORT.
Last night I dawned on the boot logo, until it was completely downloaded and at this moment it continues to do so ... By GOD!
When trying to enter the Fastboot or download mode, it takes me here:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Image extracted from: https://www.tomshw.it
Then he starts loading the rom and stays there all the time .:
Image extracted from: https://www.tomshw.it
I can not access Fastboot, nor download mode, nor recovery, because it has disappeared. There will be another way to enter the Fastboot or download mode, because the phone actually woke up until I wake up today and was even charged. PLEASE.
Hey, sorry for your sad state. Following process worked for me when I got stuck yesterday like that.
1. Connect your phone to PC ( make sure adb/fast boot is setup)
2. Hard reboot your phone with power plus volume down button.
3. As soon as your phone turns off, press volume down only and keep it pressed till you enter fastboot.
4. After this phone should be recognised in PC and you should be able to boot in TWRP using fastboot.
ZestyManu said:
Hey, sorry for your sad state. Following process worked for me when I got stuck yesterday like that.
1. Connect your phone to PC ( make sure adb/fast boot is setup)
2. Hard reboot your phone with power plus volume down button.
3. As soon as your phone turns off, press volume down only and keep it pressed till you enter fastboot.
4. After this phone should be recognised in PC and you should be able to boot in TWRP using fastboot.
Click to expand...
Click to collapse
Hope this works for you @Yeriorlando. @gimpy1 had a similar issue when installing Havoc ROM. Part of the problem seems to be when installing the custom kernel?
gimpy1 said:
It was operator error (generally is) on my part, I'm sure. The only thing I did different that I can remember is installing the 9.0 boot image in twrp differently. I installed it in the recovery option first (intentionally, should not have), instead of ticking only the boot choice. I did not untick the recovery option (should have never ticked it in the first place, but I was trying to correct a problem on the ROM, and misread a post).
Click to expand...
Click to collapse
He was able to reinstall TWRP using fastboot.
gimpy1 said:
Thx, Chaz. I pulled out my printed instructions from your post, and once I was able to get my device recognized (that did take a couple of tries), reinstalling twrp was pretty easy.
I'm back in business thanks to you.:good:
Click to expand...
Click to collapse
IF you still can't after the suggestion at top, maybe @SGCMarkus or @runningnak3d have some tips?
Unless you have an H932, then if you get the error that: "Your device software can't be checked for corruption" then you have fastboot. It is literally impossible to have that message on a WTF rooted phone and NOT have working fastboot.
So, as @ZestyManu said -- make *sure* your phone is powered off. If you have to let, the battery die. Then hold vol down + plug in the USB cable (no need to touch the power button) and you will enter fastboot.
-- Brian
Thank you all. I have solved the problem in a super crazy way, to pure ADB, not fastboot .... Pure ****ing adb ... Hehehehe. Thanks to @ChazzMatt
I was trying to flash an MIUI ROM to my phone, so
here is what I have done:
- unlocker the bootloader.
- install the recovery.
- flashed the ROM.
- reboot the device.
after I finished all the above steps my phone have stuck in the boot loop, so the obvious solution for me was to reinstall the stock ROM so I have done that by:
- download MIFlash.
- download stock ROM.
- unzip the ROM.
- then I flashed the ROM.
the flashing process took longer than usual, so i have unplugged my phone and tried to reboot it, then the phone doesn't work, even the screen not working, the only sign that the phone is working is when I plug it in my computer I see MIFlash recognize it as COM20 port.
anyone helps me please.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
kannanhassouna said:
I was trying to flash an MIUI ROM to my phone, so
here is what I have done:
- unlocker the bootloader.
- install the recovery.
- flashed the ROM.
- reboot the device.
after I finished all the above steps my phone have stuck in the boot loop, so the obvious solution for me was to reinstall the stock ROM so I have done that by:
- download MIFlash.
- download stock ROM.
- unzip the ROM.
- then I flashed the ROM.
the flashing process took longer than usual, so i have unplugged my phone and tried to reboot it, then the phone doesn't work, even the screen not working, the only sign that the phone is working is when I plug it in my computer I see MIFlash recognize it as COM20 port.
anyone helps me please.
View attachment 5265971
Click to expand...
Click to collapse
Please tell us which versions you have tried to install. It may be that you will try to install Android 10 and you were already with Android 11.
In that case it may be that the phone has been bricked. You can check how to reset it in this other post https://forum.xda-developers.com/t/this-way-i-unbrick-mi-a3-no-qfil.4231465/
In that case it may be that the phone has been bricked. You can check how to reset it in this other post https://forum.xda-developers.com/t/this-way-i-unbrick-mi-a3-no-qfil.4231465/
more detail....
what version of android has your phone? the root process was succesfully? what version of miui try to install? stock miui? port miui? miui for android 10? android 11? modding mi a3 require a lot of attention.... and install miui is not a good idea.... if fastboot mode work, try to install stock firmware via fastboot ... mi a3 have android one, is different from miui. probably you used a guide for install custom rom on miui device
Greeting,
I ask good people for help, more than a month trying to revive my a3.
It’s a child’s cell phone so I don’t know if update 11 worked so it blocked or the display went off disinfectants.
I made a repair according to "We A3 UNBRİCK Solution After Update Android 11! For FREE exclusive 2021!
, everything went without a hitch.
The current situation is that the phone works if the call if I put the sim card, it normally charges, the display is black and there is no response on the display, if there is one I can't see.
If someone has a suggestion of what to do, how can I know which Android is on it now, how can I know if maybe the display itself is broken.
Thank You in advance.
I don't saw the video but the solution is: download and install miflash tool. Connect your phone to pc in edl mode with a normal usb cable Flash a11 fastboot stock firmware. That's all
Hi Folks,
I have a Xiomi Note 10 (camellian), unlocked and has USB Debugging switched on.
No matter what I do, I can't install TWRP or Orangefox because it fails with "FAILED: Too Many Links"
I've followed so many guides on how to fix this and they all fail. I tried to flash the stock rom with Mi Flash and that failed too (Constant "Unhandled exception" error as it doesnt seem to want to install drivers and wont continue without them). I've manually updated the ADB drivers for the Note and that worked fine. Mi Pc Suite doesnt recognise my phone unless i "Update your phone before you connect" (The phone is fully updated)
Please, for the love of the baby jesus and the little donkey, tell me what I can do to try and figure out what the smeg is going wrong
EDIT:
Ive changed ports/cables, tried compatibilty on programs, reinstalled ADB drivers
trying "fastboot flash boot recovery.img" (for orange fox) throws up "FAILED: remote: size too large"
hellfirehound said:
Hi Folks,
I have a Xiomi Note 10 (camellian), unlocked and has USB Debugging switched on.
No matter what I do, I can't install TWRP or Orangefox because it fails with "FAILED: Too Many Links"
I've followed so many guides on how to fix this and they all fail. I tried to flash the stock rom with Mi Flash and that failed too (Constant "Unhandled exception" error as it doesnt seem to want to install drivers and wont continue without them). I've manually updated the ADB drivers for the Note and that worked fine. Mi Pc Suite doesnt recognise my phone unless i "Update your phone before you connect" (The phone is fully updated)
Please, for the love of the baby jesus and the little donkey, tell me what I can do to try and figure out what the smeg is going wrong
EDIT:
Ive changed ports/cables, tried compatibilty on programs, reinstalled ADB drivers
trying "fastboot flash boot recovery.img" (for orange fox) throws up "FAILED: remote: size too large"
Click to expand...
Click to collapse
i see none TWRP and O.F for camellian, can you post the links +Miflash log?
The TWRP is unofficial https://forum.xda-developers.com/t/unofficial-twrp-camellia-camellian.4304717/
There is no MiFlash log anywhere. Sorry im new to this
I think I need to flash the original rom before trying to install a recovery rom
hellfirehound said:
The TWRP is unofficial https://forum.xda-developers.com/t/unofficial-twrp-camellia-camellian.4304717/
There is no MiFlash log anywhere. Sorry im new to this
Click to expand...
Click to collapse
The Mi Flash logs are in the Miflash Log folder (post the last + or - 20/22ko
This twrp seems not to work (closed thread).
Try the command: fastboot boot twrp.img
The phone will reboot in TWRP after that go to Advanced > Flash Current TWRP
And what do you want to do with the TWRP, your device has a Mediatek soc and there is little or no development for Xiaomi with a Mediatek soc.
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It looks like a mediatek device.
Never Mind, ill keep the phone as is. Thanks for trying to help
Download and extract to the root of the disk.C:/platform....
https://developer.android.com/studio/releases/platform-tools
rename the Twrp to twrp.img
Put it in the Platform tools folder
Execute the command from this folder
Since no custom is available for your phone I guess you want to update or downgrade for these 2 cases use Miflash not TWRP.
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
this error
is frequent with certain version of W10.
Disable driver verification.
.
Usure how I ended up in this state:
Phone is an Ace Pro 5G, originally with indian rom, that I flashed using Oxygen Updater to CPH2415_11.C.22 (GLO A13).
Everything went fine, installed Magisk started to restore all my apps... I after some reboots, it ended up in boot loop. No idea why.
I can access recovery & fastbootd througt Fastboot enhance, but the weird thing is that I cannot use the touch screen in fastbootd, only volume keys and power button to select options. Quite useless as any operation pops up a dialog, and I cannot click the OK button.
Already tried to flash through Fastboot enhance multiple versions of oxygenos, including stock rom CPH2413 A05, and it always end up in boot loop.
Any idea on what I can flash to recover from this state? My guess would be fastbootd got somehow broken...
you need sent to the after-sales，the 9008 need to authorization
Petronius42 said:
Usure how I ended up in this state:
Phone is an Ace Pro 5G, originally with indian rom, that I flashed using Oxygen Updater to CPH2415_11.C.22 (GLO A13).
Everything went fine, installed Magisk started to restore all my apps... I after some reboots, it ended up in boot loop. No idea why.
I can access recovery & fastbootd througt Fastboot enhance, but the weird thing is that I cannot use the touch screen in fastbootd, only volume keys and power button to select options. Quite useless as any operation pops up a dialog, and I cannot click the OK button.
Already tried to flash through Fastboot enhance multiple versions of oxygenos, including stock rom CPH2413 A05, and it always end up in boot loop.
Any idea on what I can flash to recover from this state? My guess would be fastbootd got somehow broken...
Click to expand...
Click to collapse
after fastboot enhance flash, trying wiping the data from the recovery
Yeah so it was actually hard bricked, ended up paying thoses 20$ to get it restored though remote desktop by some oneplus employee (google ministryofsolutions)
So I've bricked again like 10 minutes after my previous, trying to restore an app using Titanium Backup. I guess it does not support oxygenos very well...
Anyway, I may have found a way to unbrick without MSM!
I tried to flash stock CPH2415 and other versions though fastboot enhance without any success (black screen, only recovery and fastbootd working every time).
What I noticed, is that my device was incorrectly recognized in fastbootd mode:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
"ossi" is the 10 Pro, not 10T... weirdly enough, it was correctly labeled in the tool before rebooting in fastbootd.
So what I tried was flashing the same playload.bin but without rebooting in fastbootd (when the device name is correctly recognized as "taro"), ignoring the bunch of unrecognized partition and the warning message "you should reboot to fastbootd".
And Tadaaaa, it worked...
Petronius42 said:
So what I tried was flashing the same playload.bin but without rebooting in fastbootd (when the device name is correctly recognized as "taro"), ignoring the bunch of unrecognized partition and the warning message "you should reboot to fastbootd".
And Tadaaaa, it worked...
Click to expand...
Click to collapse
You got very lucky. It means that whatever was borked wasn't a partition that needed to be flashed in fastbootd. It could have easily gone the other way as those unrecognized partitions just got skipped. Others have found this out the hard way.
Also, TiBu hasn't been updated in years. Switch to Swift Backup.
EtherealRemnant said:
You got very lucky. It means that whatever was borked wasn't a partition that needed to be flashed in fastbootd. It could have easily gone the other way as those unrecognized partitions just got skipped. Others have found this out the hard way.
Also, TiBu hasn't been updated in years. Switch to Swift Backup.
Click to expand...
Click to collapse
No but I did flash the same payload.bin through Fastboot enhance in fastbootd mode, which did not resolve the issue. Probably because of the incorrect detection of the 10T in 10 Pro?
Flashing the same payload.bin through Fastboot enhance in fastboot mode did the trick (and the device name was taro, not ossi)
Good advice for Swift Backup, thanks.
disclaimer - sorry i really have no idea what i am doing and my goal is to just go back to my normal phone
my phone is poco f1 and now i can only access fastboot and this "powered by android" screen. fastboot into twrp doesnt work because of "boot command is not allowed in lock state" error
hello all so i tried rooting my phone and then realized that its going really badly (i have a more details about it down) so i decided to flash stock rom using techno treatment's tutorial on it but along the way i have faced a couple of problems - when trying to install drivers, program crashes, and others below
first time i flashed i got an error (timeout error in logs) , so i tried to flash again but this time i left it open for some time (at around 500 seconds i pressed flash again, in logs it shows that flashing already started) and when i came back it was at 12000 seconds still flashing so i closed miflash and am flashing once again but with a shorter folder path (desktop\xiaomi\firmware).
after this i deleted 2 lines in flash_all.bat because i kept getting stuck on echo mismatching image and device. after this everytime i try to flash i get this error - error:Erasing 'boot' FAILED (remote: 'Erase is not allowed in Lock State')
and also error:Erasing 'boot' FAILED (remote: 'Erase is not allowed in Lock State') in the other log file
and after this i tried to go into fastboot but noticed that the fastboot logo is different, it was a bunny with a hat repairing android robot but now it is android robot repairing itself
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(this is what it looks now)
what i did before flashing stock - sorry my memory isnt the best this is all in a span of around 5 hours and my phone is pocophone f1. so at first i followed munchys tutorial on how to root, i succesfully enabled bootloader then in twrp i flashed recovery with some errors like failed to mount /system and 3 others like this but i ignored and continued then i installed magisk and after that in the video he goes into his phone no problem but i had "no os" and i think i just clicked around like backing up, restoring and wiping. then i thought i need a rom because its an os right? so i installed lineage and that was the last time when i could put files into my phone through usb. then i flashed the zip and after that rebooted and got "cant load android system, your data may be corrupt" so i pressed format something like that and did it a few times (i think this is when i couldnt put my files) until eventually saw that its no use so i went back to twrp and again clicked around until eventually wiping everything now i have no os and i cant transfer anything through usb.
Hi @medioqre
Seems like you are in locked bootloader state. You can not flash any ROM with locked bootloader unless you are enter EDL mode. See youtube tutorial to access edl mode for Beryllium
khusika said:
Hi @medioqre
Seems like you are in locked bootloader state. You can not flash any ROM with locked bootloader unless you are enter EDL mode. See youtube tutorial to access edl mode for Beryllium
Click to expand...
Click to collapse
Hi, to confirm - entering edl mode requires me to open up my phone right? how would i do that and how would i close it up after?
Thank you!
medioqre said:
Hi, to confirm - entering edl mode requires me to open up my phone right? how would i do that and how would i close it up after?
Thank you!
Click to expand...
Click to collapse
That's right, but i recommend go to the service center if you aren't able to do it.
khusika said:
That's right, but i recommend go to the service center if you aren't able to do it.
Click to expand...
Click to collapse
Hi again, its been 10 days.
so i have not went to a service center yet, because my city is too small for that. But i have a question. i didnt do anything else with my phone but today i decided i could do something and i booted it and i found out i can access fastboot mode and recovery mode, and in here i can see -
main menu, mi-recovery 3.0
and this one option
"connect with miassistant" which just gives me a picture of a phone if its plugged or unplugged with usb and under theres is a link to this website pcsuite.mi.com which doesnt work.
does this change my situation?
medioqre said:
Hi again, its been 10 days.
so i have not went to a service center yet, because my city is too small for that. But i have a question. i didnt do anything else with my phone but today i decided i could do something and i booted it and i found out i can access fastboot mode and recovery mode, and in here i can see -
main menu, mi-recovery 3.0
and this one option
"connect with miassistant" which just gives me a picture of a phone if its plugged or unplugged with usb and under theres is a link to this website pcsuite.mi.com which doesnt work.
does this change my situation?
Click to expand...
Click to collapse
If you are still in locked bootloader, you can't write firmware through fastboot or recovery
Why don't you try unlocking the bootloader officially?