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.
Related
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.
When I tried to install Android 12 beta2 for my 4a, I accidentally deleted the boot file, which caused my phone to go black. There was no response when I pressed the power button, and the bootloader was not displayed. I connected my 4a to the computer via usb, and the device manager showed QUSB_BULK_CID:xxxx_SN:xxxxxxxx. How can I repair my phone.
accidentally deleted???????
i mean how did you just wiped boot partition or flashed wrong boot image
please explain so that i can help you.
[email protected] said:
accidentally deleted???????
i mean how did you just wiped boot partition or flashed wrong boot image
please explain so that i can help you.
Click to expand...
Click to collapse
My English is very poor, use google translation, please forgive me. I’m not sure if I deleted something. I unzipped the image package to platform-tools and ran flash-all.bat. I still have an error. I didn’t put the phone in the boot loader state but the system state. . When I ran flash-all.bat, the phone went black for an instant, and then there was the situation I said, I couldn't boot up, the screen was completely black, and I couldn't enter the boot loader.
speak in native language i will use google translate.
first thing try to connect your phone to pc {windows} and go to devices and printer in control panel. and see if some thing shows up like unknown device in it.
[email protected] said:
speak in native language i will use google translate.
first thing try to connect your phone to pc {windows} and go to devices and printer in control panel. and see if some thing shows up like unknown device in it.
Click to expand...
Click to collapse
I connect the phone to the pc, the device manager shows this
{
"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"
}
so, good news your phone is alive.
[email protected] said:
so, good news your phone is alive.
Click to expand...
Click to collapse
Really？, what should i do
now try to get into bootloader mode and flash boot image of 12beta2 using fastboot flash boot.img
[email protected] said:
now try to get into bootloader mode and flash boot image of 12beta2 using fastboot flash boot.img
Click to expand...
Click to collapse
I can't enter the bootloader, this is a problem
[email protected] said:
now try to get into bootloader mode and flash boot image of 12beta2 using fastboot flash boot.img
Click to expand...
Click to collapse
When I press the power button, the phone screen is completely black and nothing happens
wait brother i have to look up. may be you have hard bricked it. but worry not i am working to find solution just be online for a while.
[email protected] said:
wait brother i have to look up. may be you have hard bricked it. but worry not i am working to find solution just be online for a while.
Click to expand...
Click to collapse
OK i am online
can you send me link of 12beta2 file you flashed and you device full name.
is it pixel 4a 4G or pixel 4a 5G.
is pixel 4a.
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developer.android.com
[email protected] said:
can you send me link of 12beta2 file you flashed and you device full name.
is it pixel 4a 4G or pixel 4a 5G.
Click to expand...
Click to collapse
which one you flashed 4G or 5G and which method you used
my phone is pixel 4a 4g and flashed 4g
I think my situation is the same as his situation
ok, bro just listen :- your phone is hard bricked.
next:- to recover your phone just use qualcomm edl tool.
here is the video to help you with.
press like if i helped thanks this works 100%
[email protected] said:
ok, bro just listen :- your phone is hard bricked.
next:- to recover your phone just use qualcomm edl tool.
here is the video to help you with.
press like if i helped thanks this works 100%
Click to expand...
Click to collapse
OK I am watching
[email protected] said:
ok, bro just listen :- your phone is hard bricked.
next:- to recover your phone just use qualcomm edl tool.
here is the video to help you with.
press like if i helped thanks this works 100%
Click to expand...
Click to collapse
I can't find pixel 4a firehose
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 everyone, I need some help.
On november 2021 I purchased Nokia 1.4 and that day when alarm was ringing my phone screen frozen/stopped. Screen sensor and the buttons stopped was not responding. I googled immediately and found the way to turn off forzen Nokia 1.4 by pressing Wolume up + Power off buttons same time (Source: https://www.nokia.com/phones/en_int...-reboot-my-smartphone-when-its-not-responding ).
When my phone turned on again I was happy till the next restarting of my phone. My nokia get Stucked in a Reboot Loop.
Screen lights and when Android GO Logo appears it turns off again and again.
I tried to flash my phone using QFIL Tool but there was unsolved issue of Android ADB Interface driver. The QFIL Tool couldn't detected my device. Mybe it needed different keys combination when connectiong it to PC to boot.
QFIL Tool source: https://androidmtk.com/download-qualcomm-flash-image-loader-qfil
Than I unlocked bootloader using this command:
Code:
fastboot oem unlock-go
I thought it was boot or recovery fail and by the reason I downloaded the firmware from alien9firmware
Source: https://alien9firmware.com/index.php?a=downloads&b=file&id=1325
Because QFIL Tool did not work I flashed boot and recovery via ADB. I moved these two .img files to disk C and ran the following commands
Code:
fastboot devices
fastboot reboot bootloader
fastboot flash recovery c:\recovery.img
fastboot flash boot c:\boot.img
fastboot reboot bootloader
fastboot erase cache
fastboot reboot
Disconnect device
You guess what do you think guys happen
My nokia was still stucked in reboot Loop.
Than I googled smartphones with same Core Qualcome QM 215 and downloaded Nokia 8 and Nokia 6.2 TWRPs from twrp official website.
Source: https://twrp.me/Devices/Nokia/
ADB thrown me an error when I tried to flash Nokia 8 TWRP. "The file is too large and blablabla..."
Then I tried to flashed twrp-3.6.0_9-0-SLD_sprout(nokia6.2) with no errors.
I have never seen anything like that. When I press to "Power button + Volume down" buttons my phone shows the stock recovery again which has no matter.
Then I gooled so many times I and I made a decision that every smartphone with Qualcomm QM215 core has absolutely same bugs.
There are smartphones with this terrible Processor:
Smartphones with Qualcomm Snapdragon 215 processor
List of smartphones that works with Qualcomm Snapdragon 215 processor inside.
www.kimovil.com
Than I found this video. In this video he used dryer and it worked. Unfortunately I have not dryer and... It may works on our devices too, Who knows...
Than someone told me to use MiFlash tool to boot my device. I faced another problem the firmware backup was missing the boot_lock.bat file. I had to download Xiaomi Kenzo global firmware to copy and modify the .bat files to my firmware backup. That trying became my night mare. I accidently erased Bootloader.
Today I was searching how connect How to a connect phone with erased bootloader to pc and I found this:
[guide] repair hard bricked devices with deleted bootloader (sboot)
I'm writing this in android development section because this is only section for both models, i hope this is not a problem. Also i want to say thanks to sataccount from gsmhosting, he found working map at the end. This guide is for hard bricked...
forum.xda-developers.com
Than I connected my phone to pc via usb and opened Device manager. There appeared QHSUSB_BULK device missing driver.
Then I found the driver here: https://fixfirmware.com/qhsusb-bulk-driver/
At least I managed to connect my device to pc again. And now QFIL Tool detects my phone.
Problems never ends. I downloaded 5 firmwares from different websites and the emmc filefouse prog_emmc_firehose *** ddr.mbn and Rawprogram .xml files missing in all of them.
Do someone know where can I fount the emmc Firehose and Rawprogram .xml files?
Oleg69 said:
Problems never ends. I downloaded 5 firmwares from different websites and the emmc filefouse prog_emmc_firehose *** ddr.mbn and Rawprogram .xml files missing in all of them.
Do someone know where can I fount the emmc Firehose and Rawprogram .xml files?
Click to expand...
Click to collapse
Try it
optimusodd said:
Try it
Click to expand...
Click to collapse
I have downloaded the firmware but there is not prog_emmc_firehose.mbn in the archive
{
"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"
}
Oleg69 said:
On november 2021 I purchased Nokia 1.4 and that day when alarm was ringing my phone screen frozen/stopped. Screen sensor and the buttons stopped was not responding. I googled immediately and found the way to turn off forzen Nokia 1.4 by pressing Wolume up + Power off buttons same time
Click to expand...
Click to collapse
When it's still under warranty ,why didn't you claim it ?
optimusodd said:
When it's still under warranty ,why didn't you claim it ?
Click to expand...
Click to collapse
It was gifted to me from abroad. You know...
S
Oleg69 said:
It was gifted to me from abroad. You know...O
Click to expand...
Click to collapse
So what was your end result because I'm currently in bootloop with an unlocked bootloader as well but not having much luck with many of the same avenues you spoke of.. anyone?
Absolutely no luck, you gotta take your phone to the service center or buy a new one as I did (another brand)
Absolutely not.. I refuse. If it's an android, there's a way. Thank God this is simply one of 8 phones I've currently got
Does unlocking the bootloader of this device put the device in boot loop. I want to unlock the bootloader coz I want to install custom ROM. Anyone tell me how to unlock the bootloader of this device without putting the device in boot loop.
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