Hello,
I've been pulling my hair for a a week now, a friend of mine gave me he's MiMix 2S.
Last time he used it he forgot to select clean all, so he has flashed with clean and lock.
Now the phone says "system has been destroyed".
I've tried the MiUnlockTool, but it failed a 50% of detecting the devices.
I've tried the flash oem unlock, failed too.
{
"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"
}
Somebody knows what to do ?
After some digging I've found that half of the issue that I had was mainly due to my AMD pc.
Since then i've tried multiple things.
Tried Miui unlock web site : Doesn't seems to work.
Tried to flash to stock ROM : failed
Tried MI Unlock : Failed
Tried EDL Unlock : Partially work but without an EDL account it's no use.
Fastboot oem unlock : Failed.
TWRP recovery : Failed.
I not used to Android, since i'm mainly using iphone, so did i miss something ?
Well, you need to unlock the phone. That will solve the system destroyed problem.
Now, the MiUnlockTool stuck tool at 50% is probably an issue of drivers/issue with your computer.
Uninstall all android and device drivers from your pc. Restart, etc..
Then install only this: https://forum.xda-developers.com/showthread.php?t=2588979
Also when unlocking and/or flashing, use one of the usb ports directly on the motherboard, on the back of your pc.
Well the 50% thing was due to me using an AMD pc, I switch to an Intel one and it worked.
freyjamir said:
Well the 50% thing was due to me using an AMD pc, I switch to an Intel one and it worked.
Click to expand...
Click to collapse
So you managed to fix your phone? Or is something else failing now when you try to unlock? What exactly?
I'm trying to unlock before flashing to stock rom, since i've got the message "system is destroyed"
Since then i've tried multiple things.
Tried Miui unlock web site : Doesn't seems to work.
Tried to flash to stock ROM : failed
Tried MI Unlock : Failed
Tried EDL Unlock : Partially work but without an EDL account it's no use.
Fastboot oem unlock : Failed.
TWRP recovery : Failed.
I finally found some part of a solution for my unlocking, BUT i need to access the developpers options.
Since the phone cannot boot past fastboot is there any way to enable this option remotly ?
Like with a fastbook command ?
freyjamir said:
I finally found some part of a solution for my unlocking, BUT i need to access the developpers options.
Since the phone cannot boot past fastboot is there any way to enable this option remotly ?
Like with a fastbook command ?
Click to expand...
Click to collapse
I do not think so.
But I was wondering what exactly fails when you try to unlock it yourself?
You say it doesn't seem to work, but what doesn't work, what is the error? What fails? Which procedure do you follow to unlock?
Hello,
My process was :
Since I know that my bootloader is locked (confirmed by the fastboot command) , my first try was to install a stock rom.
And it failed with the mismatch error then he failed with : Erase is not Allowed in locked state.
Then I tried the Unclocker tool who ask me to unlock in the developer option.
Then i tried the fastboot unclock command, doesn't work either.
Then flashing only with TWRP recovery and it doesn't work too.
And mainly followed this guide https://c.mi.com/thread-1479882-1-0.html.
Related
Hey, my friend has a Pixel 2 that seems to have gotten bricked today. His phone was working fine all day but when he tried to unlock it to check the time, it was suddenly in fastboot mode. He was running stock android, and has never flashed any custom ROM/software to it, nor unlocked it:
{
"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"
}
I can't open recovery mode or boot the OS from fastboot. The only option I can access is the "barcode" one. I've been trying to flash a factory image from google(as I've done several time for my Nexus 5 and Nexus 7 using the fastboot/ADB from CMD), but currently ADB won't recognize the device(probably because USB debugging and other developer settings are off/have never been accessed at all), and Fastboot recognizes the device but can't perform any flashing to it because it's locked. I also tried deuces script from a folder with all the factory .img files unzipped etc. I also updated the USB drivers in windows, but basically every step I can find here, on reddit or on stack overflow mention enabling USB-debugging and OEM unlock in the settings, which I can't access. Is there anything I can try or is it per definition bricked?
Marhan93 said:
Hey, my friend has a Pixel 2 that seems to have gotten bricked today. His phone was working fine all day but when he tried to unlock it to check the time, it was suddenly in fastboot mode. He was running stock android, and has never flashed any custom ROM/software to it, nor unlocked it:
I can't open recovery mode or boot the OS from fastboot. The only option I can access is the "barcode" one. I've been trying to flash a factory image from google(as I've done several time for my Nexus 5 and Nexus 7 using the fastboot/ADB from CMD), but currently ADB won't recognize the device(probably because USB debugging and other developer settings are off/have never been accessed at all), and Fastboot recognizes the device but can't perform any flashing to it because it's locked. I also tried deuces script from a folder with all the factory .img files unzipped etc. I also updated the USB drivers in windows, but basically every step I can find here, on reddit or on stack overflow mention enabling USB-debugging and OEM unlock in the settings, which I can't access. Is there anything I can try or is it per definition bricked?
Click to expand...
Click to collapse
Have you tried using the OTA instead of the factory image? That might give you a workaround to get it functioning again.
Sent from my Pixel 2 using Tapatalk
Have you tried changing your usb cable and the port its plugged into? Its stupidly simple, but has solved nuuuuuumerous problems I've had with manually flashing.
Other that that, I think you've covered a lot of bases. Are you sure you can't get into recovery mode tho? I was only able to get in by unplugging, full power off, then using power + vol dn for bootloader mode, then selecting recovery mode. You might be able to do some flashes from there.
Also, adb only works in the OS and maybe recovery mode. Fastboot only works in bootloader mode. I'm not exactly sure if fastboot needs to be authorized. Adb does though.
I have a t mobile variant that is sim unlocked and bootloader unlocked.
I wanted to convert to a Global version however it failed because I apparently had the wrong oem software.
I used all in one tool which worked great for everything else I needed but here is the problem; I can only boot into fastboot mode and crashdump mode. When using all in one tool I chose to wipe the device before installing the new software
I also cannot get into EDL Mode to use the Msmdownload tool even though the correct drivers are installed to use this tool.
Anyway out of this? Thanks...
Aslo; I have tried fastboot commands with no luck...
You need to msm using edl. If you are bl unlocked, flash a custom ROM to get booted and maybe try again using proper tool?
Also, try different USB ports, cables, etc. You should be able to boot into edl with hw keys and connect to msmtool
As I stated I can not get into edl, I tried all the the other things also, cables, ports. I did not know I could have flashed a custom rom at this point, phone was not rooted either...
Oneplus has it now for repair, they are about 300 miles from me, or the service center is?
Gabriel51 said:
As I stated I can not get into edl, I tried all the the other things also, cables, ports. I did not know I could have flashed a custom rom at this point, phone was not rooted either...
Oneplus has it now for repair, they are about 300 miles from me, or the service center is?
Click to expand...
Click to collapse
Not sure if you got this fixed but boot into fastboot, the use "fastboot boot" to boot into AICP Recovery. Within recovery eanble ADB, then "adb reboot edl". EDL mode is just a black screen and your phone will exit it and try to boot after a few seconds if the drivers are not installed so its easy to miss. If your phone can boot into fastboot it can boot into EDL.
I do not see that feature listed? Phone would not boot into normal recovery, it went right back into fastboot.
{
"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"
}
Also if you had read through the posts you would know that I already sent it to 1+ for repair, they have had it a couple of days...
OnePlus repaired my device for nothing which is nice however It's now sim locked and at first try T-mobile says this device does not qualify for unlock!!! T-mobile also said they are looking into it because it was previously unlocked and it may take a week to get a reply.
I called OnePlus and their response was it's not our problem (more or less) I sent them a unlocked phone and they completely ignored my request to load the global software on this device, they did what they wanted to, they could have contacted me at any time..THANK YOU OnePlus.
Hello!
So i got my asus zenpad 3s 10 rooted (with magisk) a long time ago. I have the bootloader which has the normal mode, fastboot mode and the recovery mode. However, i forgot if i had the custom TWRP or not. So, i had this device rooted for like 1 year now. But, for some reason my device keeps rebooting. In hopes of fixing this, i updated THE MAGISK MANAGER and rebooted. Here comes the fun part, my devices is stuck in a bootloop and now i don't know what to do. Getting into recovery mode says 'NO COMMAND' and a broken android bot. Fastboot mode gets stuck for hours and i don't know how to access it cause adb can't recognize my device when i connect it to my PC. I don't really have the model number and i can't get a custom patch for magisk (it might me in the tablet WHICH I CAN'T ACCESS ) I really am desperate right now since i don't have money yet to buy a proper phone.
Thanks!!
Re-flash Stock ROM to get rid off of all modifications you applied so far.
jwoegerbauer said:
Re-flash Stock ROM to get rid off of all modifications you applied so far.
Click to expand...
Click to collapse
I can't connect it to my PC, adb doesn't recognize it for some reason
I can't even find the stock rom cause i forgot the build number lol. It maybe in the internal storage which i can't access
It should be obvious that ADB doesn't work on bootlooping devices.
If you can find a suitable Stock ROM then you might use Asus Flash Tool what relies on Fastboot to re-flash the tablet
{
"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"
}
/
jwoegerbauer said:
It should be obvious that ADB doesn't work on bootlooping devices.
If you can find a suitable Stock ROM then you might use Asus Flash Tool what relies on Fastboot to re-flash the tablet
Click to expand...
Click to collapse
Is there any way i can find the stock rom without accessing the tablet itself?
jwoegerbauer said:
It should be obvious that ADB doesn't work on bootlooping devices.
If you can find a suitable Stock ROM then you might use Asus Flash Tool what relies on Fastboot to re-flash the tablet
Click to expand...
Click to collapse
can i even access the tablets storage when its bootlooping?
NaibPlays said:
can i even access the tablets storage when its bootlooping?
Click to expand...
Click to collapse
If tablet supports USB-OTG then yes.
jwoegerbauer said:
If tablet supports USB-OTG then yes.
Click to expand...
Click to collapse
Ok so i am facing an issue, when i connect my tablet to the PC the Asus Flash Tool doesn't pick it up. Any help please?
Can't help you further: I don't own this tablet.
jwoegerbauer said:
Can't help you further: I don't own this tablet.
Click to expand...
Click to collapse
Alright, thanks.
I've got a Moto One 5G Ace that I picked up from eBay. It's an XT2113-2 according to the Recovery Mode 128/6. I guess the carrier was T-Mobile because the annoy screen always comes on when I boot. Fastboot lists it as
NK0T4M0308 fastboot
but when I try and write the recovery.img I get
fastboot flash recovery recovery.img
Sending 'recovery' (102400 KB) FAILED (Write to device failed (No such device))
When I try and use the Recovery and Smart Assistant(Windows) from Motorola
the IMEI doesn't match to the firmware
And it's stuck on Android 10, when I try and update from the phone it says it has the latest version of Android
When I try and run Rescue and Smart Assistant(RSA) and boot to the Recovery mode it soon drops and says it can't connect to the device
Mobile Assistant is installed by RSA but after RSA tries to detect the device in Recovery Mode but can't it can no longer detect the USB when it's attached. I need to reset the device so I can go through the entire process all over again.
Please help I don't know what's going on or how to fix it
{
"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 have an engineering phone. It cannot be updated via regular ways.
RETIEF said:
You have an engineering phone. It cannot be updated via regular ways.
Click to expand...
Click to collapse
So what irregular ways can I employ then?
Send it to someone who has the tools to flash it. I don't know anyone but perhaps someone on the Telegram channel does.
Just in case anyone else comes across this problem too. The internal hardware is not the same as the model would indicate with the model number it's entirely different. So in other words, it's an entirely different phone, it can't be flashed to anything. It's like comparing apples to oranges they are in no way the same.
In Developer options, does it say "Bootloader is already unlocked" under OEM unlocking?
Does it still fail to load recovery if you run "fastboot boot recovery.img" so it says "Waiting for device...", then plug the phone in while holding down the volume and the phone is shut down? Even retail kiev can be really finicky in fastboot mode.
Really cool find in any case.
fddm said:
In Developer options, does it say "Bootloader is already unlocked" under OEM unlocking?
Does it still fail to load recovery if you run "fastboot boot recovery.img" so it says "Waiting for device...", then plug the phone in while holding down the volume and the phone is shut down? Even retail kiev can be really finicky in fastboot mode.
Really cool find in any case.
Click to expand...
Click to collapse
it would be cool if I could image it, but the internals don't match to what it actually is
but yes it does say the bootloader is already unlocked
Hi.
So, I was playing a game like everyday with my phone and then it suddenly stopped working and rebooted. After the reboot it got stuck on a boot-loop and wasn't unable to boot normally again. I got into the recovery and after many tries I was able to reinstall the ROM (PixelExperience 12-Plus) but after a few minutes it stopped working again and got into the boot-loop... again. I tried to reinstall the ROM again but I wasn't able to, so I decided to try with another recovery, I was using OrangeFox and after that I tried with TWRP. I got it to work with TWRP but then it crashed again but before doing it I got this screen:
{
"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 never happened before and I was scared, "Did I just broke my phone?" I thought. So I asked a friend for help and he told me to try with Fastboot, he sent me a few command lines to try and... I ****ed up. The first line that I wrote was "fastboot oem lock" and the phone rebooted with this screen:
I literally locked the bootloader and now I'm unable to flash any ROM or even unlock it with MI-Unlocker 'cause I didn't have any MI account on the phone. I still can get into the fastboot but no more than that.
Is there anything that I can do? Or I should just send it to repair? Or buy a new brain for myself?
SalmonellaREAL said:
Hi.
So, I was playing a game like everyday with my phone and then it suddenly stopped working and rebooted. After the reboot it got stuck on a boot-loop and wasn't unable to boot normally again. I got into the recovery and after many tries I was able to reinstall the ROM (PixelExperience 12-Plus) but after a few minutes it stopped working again and got into the boot-loop... again. I tried to reinstall the ROM again but I wasn't able to, so I decided to try with another recovery, I was using OrangeFox and after that I tried with TWRP. I got it to work with TWRP but then it crashed again but before doing it I got this screen:
View attachment 5941189
It never happened before and I was scared, "Did I just broke my phone?" I thought. So I asked a friend for help and he told me to try with Fastboot, he sent me a few command lines to try and... I ****ed up. The first line that I wrote was "fastboot oem lock" and the phone rebooted with this screen:
View attachment 5941187
I literally locked the bootloader and now I'm unable to flash any ROM or even unlock it with MI-Unlocker 'cause I didn't have any MI account on the phone. I still can get into the fastboot but no more than that.
Is there anything that I can do? Or I should just send it to repair? Or buy a new brain for myself?
Click to expand...
Click to collapse
Lesson #1: Never do something when you don't know what the outcome will be, unless you're able to accept negative consequences. You should NEVER EVER lock the bootloader on custom firmware unless a custom root of trust has been installed, as with CalyxOS/GrapheneOS/etc.
Try to unlock the bootloader using fastboot flashing unlock or fastboot oem unlock
If those don't work, your phone is bricked, and you're going to have to either have it repaired or replace it, both of which will be expensive.
V0latyle said:
Try to unlock the bootloader using fastboot flashing unlock or fastboot oem unlock
Click to expand...
Click to collapse
That won't work, to unlock this phone you must use the Xiaomi official tool: https://en.miui.com/unlock/download_en.html
@SalmonellaREAL now you must pay to unlock it with an official Xiaomi account for EDL or you must go to an official repair center. I recommend you the second option, I never tried first.
Never lock bootloader unless the ROM has a self signed certifcates, in vayu there aren't any ROM with this.
V0latyle said:
Try to unlock the bootloader using fastboot flashing unlock or fastboot oem unlock
Click to expand...
Click to collapse
fastboot flashing unlock - Result: . . . FAILED (remote: unknown command)
fastboot oem unlock - Result: . . . FAILED (remote: Token Verify Failed, Reboot the device)
They didn't work, I'll try to send it to repair then. Thanks for replying!
swer45 said:
That won't work, to unlock this phone you must use the Xiaomi official tool: https://en.miui.com/unlock/download_en.html
@SalmonellaREAL now you must pay to unlock it with an official Xiaomi account for EDL or you must go to an official repair center. I recommend you the second option, I never tried first.
Never lock bootloader unless the ROM has a self signed certifcates, in vayu there aren't any ROM with this.
Click to expand...
Click to collapse
I believe you can still use ADB as long as you use the correct token for the unlock. I'm not very familiar with Xiaomi phones though so I'm not sure what the correct syntax would be.
I did find this:
GitHub - Canny1913/miunlock: A program that can be used to retrieve the bootloader unlock token for Xiaomi devices. (and unlock the bootloader)
A program that can be used to retrieve the bootloader unlock token for Xiaomi devices. (and unlock the bootloader) - GitHub - Canny1913/miunlock: A program that can be used to retrieve the bootload...
github.com
Description says it can retrieve the bootloader unlock token and unlock the device.