Long story short, I ended up with a classic bootloop (shows boot animation continuously) from messing around with Magisk modules, so I did a wipe from recovery, still bootloop, so I tried reverting completely to stock with the OEM downloads. I tried flash_all_except_storage.bat, and flash_all.bat, but this time it was a different bootloop. The phone shows the Android One logo, the screen flickers like it's going to the boot animation, but then it just goes back to the Unlocked Bootloader Warning Screen, then the Android One logo, and loops like that. I dumbly thought locking the bootloader, reflashing everything, and starting over like it were a new phone would fix the issue, so I did flash_all_lock.bat, but now I'm just stuck with this weird bootloop and a locked bootloader. Trying to unlock the bootloader with fastboot just gives me "oem unlock is not allowed", so I'm at a loss here.
Does anyone know of anything else I could do, or is this a hard brick?
With a locked bootloader EDL flash probably is your last chance.
Maybe this thread helps:
https://forum.xda-developers.com/mi-a2-lite/help/hard-bricked-mi-a2-lite-help-to-enter-t3862648
thorin0815 said:
With a locked bootloader EDL flash probably is your last chance.
Maybe this thread helps:
https://forum.xda-developers.com/mi-a2-lite/help/hard-bricked-mi-a2-lite-help-to-enter-t3862648
Click to expand...
Click to collapse
I got stuck with a similar problem and that was the only option, to boot into EDL mode you will need to partially dissasemble your device and flash the image via fastboot or via MiFlash (download the latest version as I had problems with an older one). Since that incident I kept the bootloader unlocked just in case something happens.
I had the phone booted into EDL mode and attempted to flash the stock ROM (10.0.3.0) with MiFlash, but it errored out with an ERROR_UNSUPPORTED_TYPE. I tried with the previous version, 10.0.2.0 and it worked for some reason. That fixed it though, so thanks! I've been lightly tinkering with rooting android phones a few years now, but until encountering this issue, I'd never heard of EDL mode. You learn something new every day? ?
I have the same issue with my nephew 's mi a2 lite which has the bootloader locked.
It only shows the android one logo.
I cannot go to recovery mode, but I can go in fastboot.
Changing from "a" to "b" doesn't solve anything and being the bootloader locked is not possible to flash anything from fastboot.
So I've opened the device and I've short circuited the edl pinpoint to be able to flash with MiTool (I've used an old version since more recent ones gave errors when flashing).
I was able to flash both the latest official ROM and the oldest one which I've found ( daisy_global_images_V11.0.14.0.QDLMIXM_10.0 and daisy_global_images_V9.6.4.0.ODLMIFF_8.1 respectively).
In both cases the device still is "frozen" with the android one logo when I've tried to turn it on after the flashing procedures gave me a successful status.
What else can I do?
Related
I have updated my Nexus 5x to 7.1.1 beta and after a day it powered off and I got the infamous red led during charging. I was not able to turn the phone on even after leaving the charger on for some days. I thought it is bricked and left it alone connected to my computer.
However today, out of nowhere Google logo popped up. It was bootlooping, but I was able to enter bootloader and original recovery. I wanted to flash it from bootloader, but was unable, because it was still oem locked. And I was not able to oem unlock, because I did not do the required part in the Developer Tools menu. I tried to adb sideload OTA in the original recovery, but sideloading stopped after uploading ~48% every time.
So I opted for the "VolumeUp + Power" mode flashing. Phone was recognized and I started flashing the appropriate TOT file. However at 33% on phone and 28% on the PC, progress stopped. And after a minute or so phone turned off. Currently it has no signs of life at all. Have I completely bricked it now? Is there a way to recover from interrupted "VolumeUp + Power" flashing mode?
EDIT: at first I though maybe the battery died during flashing. But interruption was not abrupt. First the progress slowed down to halt. And then after some time phone turned off.
It seems not all is lost. Have a blinking red light again after leaving it connected to computer for a day. Back to square one, but at least it is alive.
Your motherboard is dead.
And it is not your fault, mine also died while using beta 7.1 and I sent it RMA. They replaced for a new one.
But in my case i had unlocked bootloader, I flashed back 7.0 and it gave no results, still bootloop that's why I sent
Thanks for the info.
After leaving my phone with a clamp on a power button throughout the night (so the red light would flash continuously), I got it booting into "VolumeUp + Power" mode and this time I have successfully flashed the same TOT file via LGUp software. It was still bootlooping after flashing. Now I was able to enter into bootloader and recovery and this time sideloading the same previous file actually works. However it still bootloops.
Anyway, I tried to RMA it and after giving my IMEI to the Google rep, they said that they could not find it in their system after checking US and UK store records. Also tried calling LG warranty, but they do not know of my IMEI either. I got this phone from Swappa, so I left wondering where did the original owner of this phone got it from. He claimed that he got it as a present...
BlinK_ said:
Thanks for the info.
After leaving my phone with a clamp on a power button throughout the night (so the red light would flash continuously), I got it booting into "VolumeUp + Power" mode and this time I have successfully flashed the same TOT file via LGUp software. It was still bootlooping after flashing. Now I was able to enter into bootloader and recovery and this time sideloading the same previous file actually works. However it still bootloops.
Click to expand...
Click to collapse
out of curiosity, have you ever tried to flash custom recovery through the bootloader ? If you can, you might also wanna try to make a EFS backup, wipe all partition, then flash custom rom or near-stock rom like this one, just for the sake of testing.
anazhd said:
out of curiosity, have you ever tried to flash custom recovery through the bootloader ? If you can, you might also wanna try to make a EFS backup, wipe all partition, then flash custom rom or near-stock rom like this one, just for the sake of testing.
Click to expand...
Click to collapse
I wanted to flash custom recovery but was unable to do so, because device is still OEM locked. And I am unable to unlock it, because I did not do the confirmation in the Developer Options before device started to bootloop. Is there a way to flash custom recovery without this step in Developer Options?
BlinK_ said:
I wanted to flash custom recovery but was unable to do so, because device is still OEM locked. And I am unable to unlock it, because I did not do the confirmation in the Developer Options before device started to bootloop. Is there a way to flash custom recovery without this step in Developer Options?
Click to expand...
Click to collapse
For now, no way that I can think of. You could try to oem unlock it until it work, just cross your finger I guess?
I have some progress here. Since I was able to sideload various OTA images, I started doing that one by one and seeing if some of them would not bootloop. And after flashing 7.0.0 (NRD91N) from here (https://developers.google.com/android/ota) phone booted successfully and now is working. Will report if I get any problems.
I recently found a moto g5 in one of my fellow "old tech" drawers and decided to turn it on, it was on the
1. May 2018
Security patch on nougat, I decided to use the inbuilt system updater to go to Oreo, and now....it crashes during flashing process after about 25-30% completion,
Now im guessing boot or System is not properly installed due to the zip file having aborted mid-flash
Recovery doesn't properly boot as that is used to install the update and thus imidiately goes to doing that
Also, it hang up during installation on random times, it basically has a record of 2mins of not crashing whilst still being stuck on 30%
I got it to "boot" when trying factory mode, yeah it crashed mid boot animation...not a help
Any suggestions? EDL mode maybe?
Can you not flash firmware via fastboot
In theory as long as firmware is signed you don't need an unlocked bootloader to flash firmware
Firmware can be downloaded from https://mirrors.lolinet.com/firmware/moto/cedric/official/
You can also try the lenovo moto smart assistant to flash the firmware
https://forum.xda-developers.com/g5/how-to/guide-how-download-official-fastboot-t3916778
If not you will most likely need a motherboard replacement or jtag firmware flash at a repair shop
TheFixItMan said:
Can you not flash firmware via fastboot
In theory as long as firmware is signed you don't need an unlocked bootloader to flash firmware
Firmware can be downloaded from https://mirrors.lolinet.com/firmware/moto/cedric/official/
You can also try the lenovo moto smart assistant to flash the firmware
https://forum.xda-developers.com/g5/how-to/guide-how-download-official-fastboot-t3916778
If not you will most likely need a motherboard replacement or jtag firmware flash at a repair shop
Click to expand...
Click to collapse
SOMEHOW it just decided to boot, I have never seen such behaviour, even on my g5s which I had for a while, (and am currently daily driving to school if it wasn't closed....NEVER
Maybe I'll unlock it and try somehow recreating it? Well it's in physically rough shape but all components inside are fine...so that can't be the reason....?
My g5 got stuck in a bootloop without an update, no root or anything modded. Is there any way to recover the data if its stuck like this?
anonymous724 said:
My g5 got stuck in a bootloop without an update, no root or anything modded. Is there any way to recover the data if its stuck like this?
Click to expand...
Click to collapse
Flash the stock rom and boot the device. But this will format the device.
To save data, remove the command fastboot erase userdata
Fastboot erase customisation.
Apps may be gone, but files In internal storage will be safe, like download,photos, music.
riyan65 said:
Flash the stock rom and boot the device. But this will format the device.
To save data, remove the command fastboot erase userdata
Fastboot erase customisation.
Apps may be gone, but files In internal storage will be safe, like download,photos, music.
Click to expand...
Click to collapse
no luck on this front, gets to the passcode screen, write in passcode then motorola logo shows and screen keeps on turning off and on.
Thanks for the effort though, much appreciated
Mine is similar to yours. Initially was on permanent loop of the following:
1. Boot to moto g splash screen... Repeat
2. Boot to lock screen then usually a few loops of 1. (after entering the patter or left Idle)
The phone initially didnt have any developer options enabled.
I wiped cache using recovery mode. Restarted and pretty much the same thing except that it would on rare occasions actually fully boot up usually only last a few minutes before cycling between steps 1 and 2 above.
I used those rare boot ups to backup all files and enable any USB debugging /oem unlock (incase I need to use a solution dependent on these being enabled.)
Factory resetted it and its still the same with the random successful boot amongst the numerous failed ones.
I managed to hook it up to Lenovo's Lmsa and flash the latest ROM. Now I get a lot more successful boots but still loops every so often. The downside is that I can no longer do any functions that make use of the audio/ mic/ video (can take pictures). If I do then it will crash and loop.
The hardware test on the LMSA passed for every component before flashing to the latest version. Post update it predictably fails on the audio/ mic components.
I guess I'll have to go back to the old version to see I get the audio back.
So I appear to have a soft bricked phone. It is on stock firmware, although it has been unlocked previously in order to flash that over the Three custom firmware.
It randomly rebooted itself into a boot loop where it would get as far as the Razer logo and restart itself. I got into recovery and tried to factory reset it, at which point it claimed to have formatted /data but then complained it failed to mount /mnt/vendor/persist (no permission).
I can't see it in adb devices unless I put it in sideload mode - I presume I can't sideload anything anyway unless it is unlocked for flashing.
I can reboot to the bootloader and then see it in fastboot but I can't do very much there because the bootloader is not unlocked (so I can use Netflix, my banking app, etc), but I can't boot to the OS in order to unlock it or make sure adb debugging is on. The general instructions on Razer's website to do fastboot flashing unlock or unlock_critical don't seem to work as I think this needs the phone to be in 'download mode' which doesn't seem to be a thing since the Pie update. So if I try to reflash stock firmware it just complains that everything is locked.
Is there any way to get it into a flashable state without booting into the OS, or am I just screwed?
I have a weird situation going on with my phone
My phone is Chinese Pack and I had Xiaomi Eu MIUI 12 previously
I tried flashing MIUI 11 Stable China rom on it using TWRP
when I installed the rom, TWRP didn't get deleted and my phone started to bootloop, so I flashed magisk and the bootloop was gone and I could boot my device after flashing magisk.
Now I want to sell my phone and I'm trying to flash everything back to normal, get rid off TWRP and Magisk and lock the bootloader as well using MiFlash
the phone is running on V11.0.5.0.PCACNXM and I'm trying to flash the same rom using MiFlash and lock bootloader, but at first, it says device mismatch
and when I delete the first 2 lines of flash_all_lock.bat which causes this problem, something else happen
check the attached image
when I press the flash button, this screen comes up and nothing changes except the timer that goes up, and when I remove the phone cable, the phone boots normally without any problem, practically, MiFlash doesn't change a thing
any solution that can help me unlock Bootloader, remove Twrp and Magisk?
Already tried different versions of MiFlash and an app called XiaomiADBFastbootTools.jar, nothing again
P.S: while flashing with XiaomiADBFastbootTools.jar, I get the same message but after removing the cable, the error changes to "current device anti-rollback version is greater than this package", which is nonsense because I have the same ROM on phone already.
Must be rusty in my old age, but I dont remember having any of these issues back with my previous android phones... the 11 is my first new one since the 6T though.
Whats my situation:
Phone boots into fastboot, attempts to boot to recovery, or continue, or restart all end back at fastboot. Can issue fastboot commands, but all roads seem to lead back to fastboot.
How I got here:
When I first got my phone, I unlocked the bootloader via fastboot command, but for some reason my phone wouldn't let me set a pin. Be it numeric, alphanumeric, or pattern, it would never let me confirm after putting it in the second time, and consequently I couldn't register a fingerprint or face scan. Reddit suggested that this sometimes happens after bootloader unlock but can be resolved by re locking and unlocking again... ok fair enough, haven't done much yet, whats another factory wipe.
fastboot flashing lock command - finished, boots straight back to bootloader
fastboot flashing unlock command - finished, ok time to try booting through to see if it fixed the problem... stuck in fastboot.
I'm rusty enough to want to stop here and seek guidance before I further brick my phone. I have fastboot access so in theory I should be able to flash an image from here? Any guidance would be appreciated. I'll admit I've fallen off the scene hard (new baby, job etc) and perhaps I should have just left my phone locked... but habits die hard eh?
You can only flash the full rom /images with unlocked bootloader
With locked bl you becomes the messages
Flashing on locked states not allowed
did you flash a patched init_boot.img after your first unlock?
benhc911 said:
Must be rusty in my old age, but I dont remember having any of these issues back with my previous android phones... the 11 is my first new one since the 6T though.
Whats my situation:
Phone boots into fastboot, attempts to boot to recovery, or continue, or restart all end back at fastboot. Can issue fastboot commands, but all roads seem to lead back to fastboot.
How I got here:
When I first got my phone, I unlocked the bootloader via fastboot command, but for some reason my phone wouldn't let me set a pin. Be it numeric, alphanumeric, or pattern, it would never let me confirm after putting it in the second time, and consequently I couldn't register a fingerprint or face scan. Reddit suggested that this sometimes happens after bootloader unlock but can be resolved by re locking and unlocking again... ok fair enough, haven't done much yet, whats another factory wipe.
fastboot flashing lock command - finished, boots straight back to bootloader
fastboot flashing unlock command - finished, ok time to try booting through to see if it fixed the problem... stuck in fastboot.
I'm rusty enough to want to stop here and seek guidance before I further brick my phone. I have fastboot access so in theory I should be able to flash an image from here? Any guidance would be appreciated. I'll admit I've fallen off the scene hard (new baby, job etc) and perhaps I should have just left my phone locked... but habits die hard eh?
Click to expand...
Click to collapse
You need to re-unlock the bootloader in the original china ROM!
I can help you if you get stuck on this issue ! pm me! !
I did indeed reunlock the bootloader. I imagine the issue possibly when I was attempting to root by patching a boot img with magisk and flashing that... Although after doing that my phone seemed to operate fine.
Regardless I reflashed the original, and it seemed to still bootloop into fast boot.
I tried relocking the bootloader, going to recovery, etc. After some degree of insanity doing seemingly the same thing I got to stock recovery, and then back to bootloader then back to recovery, then it flashed me writing in Chinese and it booted normally.
Since then I've rebooted my phone with no issue.
Not sure what exactly happened to make it conditionally work/not work... But given the time I wasted on it and the infant I'm having strong second thoughts about bothering with an unlocked bootloader. I'm clearly not in my element anymore as my confidence of which files to flash and commands to do so was very low (hence the post). My initial suspicion was "I have fast boot I can just flash original rom and I'm back to square one at least" but was too "afraid" to proceed and brick my new phone.
To expand on the "why bother with unlocked bootloader", I feel like it's been 3 phones since I truly took advantage of unlocking my bootloader. Perhaps I need to read more about the current state to see if there is a value proposition for me, or if I'm just creating more work (to then root, magisk, TWRP, safetynet, windvine etc)
Same happened to me,
Possible solution:
I used fastboot enhance to flash the payload.bin all over again, after it finished it rebooted into fastbootd automatically, then I falshed the same payload.bin into fastbootd as well then it rebooted into system smoothly.