Hey there,
I have a 5X which had that dreaded bootloop issue just after I OTAed to 7.1.1.
I'm able to get it to boot when plugged with the phone heating to a very high temperature. Is there a possibility of using a custom rom so that I can use it minus the bootloops?
I have moved onto the 3T. Just wanted to resurrect this so that I can use it for the camera alone. The 3tcamera stinks against the 5X.
Device has locked BL with OEM unlocking enabled. Recovery will not work but Fastboot works.
Thanks
Recovery doesn't work? I also have the BLOD but I can still enter recovery. Have you run any custom ROMs or accidentally flashed something in boot?
Related
Hi
I have a Nexus 5X that recently started bootlooping. I didn't flash anything new, it just started randomly yesterday. Most often it cycles between the Google logo and the yellow triangle warning about the unlocked bootloader. Sometimes yesterday it would boot to the spinning colorful objects turning into Android logo, freeze and reboot from there. A few times it event booted fully, but I didn't have a PC nearby to pull the files.
Today it didn't even once get to the colorful objects. Then I found some threads about the fix with the big cores of the processor and flashed the boot.img that solved it for many. Sadly, however it didn't work for me. The only thing that I can reliably boot into is fastboot.
Also tried booting into TWRP, but it froze and rebooted from the Google logo.
Does anyone have an approach to pull my files from the device? I bought a new phone yesterday and don't care to recover the full functionality of the device. I only care to recover the files via TWRP or booting into Android one more time. RMAing it might be hard, since I have unlocked the bootloader (despite currently running stock and not even root, I think).
Any help will be appreciated.
Cheers
Andi
Have you tried 'updating the build ' via fastboot without erasing userdata? Section 9 from SlimSnoopOS's guide @ https://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
LG do offer a 2 year warranty (in the UK at least) and you can relock the bootloader through fastboot before you return it once you've recovered the data and/or factory reset it.
Did you install standard twrp or the one modified to boot on 4 cores?
Sent from my SM-G930F using Tapatalk
I feel like an idiot because I installed the modified boot.img, but the regular TWRP, assuming that the boot.img would be used to alter some fundamental configuration of the Cortex no matter what would be booted afterwards. The modified TWRP worked like a charm.
Hi guys,
I have a problem with my Nexus 5X. I have the latest PureNexus version, Elemental 5X Kernel and Magisk installed. But I believe that this has nothing to do with my problem.
It always freezes and restarts after a few seconds. And not only during booting, but also in recovery mode, if I want to flash something (magisk uninstall). I suspect now that it is the battery and the voltage can not be supplied under load. Could that be, or do you think it's something else? In fastboot, I can still get, without any freezes. But it's not recognized by "fastboot devices" (latest google usb drivers installed). Is it even possible to backup the data of the internal memory via fastboot somehow?
Thank you very much for any help!
Probably the famous bootloop problem. Maybe you can get some data off the phone using temporary fixes posted on this forum before you rma the phone. Just go a quick search of the forum for details.
Thanks for your reply. I read a little bit about the famous bootloop problem. But "bootloops" are for me while "booting". Not in recovery and not if I connect my charger (the battery icon appears and after a few seconds it reboots).
Should I take more focus on the bootloop problem or is my problem different?
it is bootloop without a doubt
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?
Hi I have a pixel xl that I bricked. Ill give you a quick history of what I did. I had this phone rooted with magisk and on LOS and it is my backup phone that I play with. I had to send my pixel 4 xl in for a warranty exchange. So I had to use my pixel xl for a few days and I decided to return it to stock and lock the bootloader. So I did that but magisk seems to have persisted through the process of returning to stock and the phone worked fine I just got the message that the device has a different operating system installed and I still had root. Anyway I now have the pixel 5 and I was playing with my pixel and it just started boot looping and the phone gets really hot. It could just be that the hardware crapped out.
So I was able to unlock the bootloader and use fastboot to boot twrp and mount the system and I copied the twrp installer over and tried installing it. It did not work and I think i wiped out all recoveries because now when I try to boot recovery it just goes to boot the system like there is nothing there at all. Oh and I tried booting back to twrp and wiping everything. So that's where I'm at now and not sure what to try next. Do I use fastboot to boot into twrp and download the last ota file and sideload it? I'm open to any suggestions that anyone might have.
Hello everyone,
Few weeks ago, I broke the screen of my MiA2 Lite. The touchscreen was still working perfectly, but nevertheless, I decided to change the whole display.
And... The touchscreen of the new display was not responsive also. So I've switched back to the old one. Same issue.
I've read somewhere, that a reflash could help to fix this issue.
So, I've installed TWRP and flashed a first rom: miui_DAISYGlobal_V11.0.21.0.QDLMIXM_c6721a4b58_10.0.
I tried then to boot, the phone boots correctly, but the new touchscreen was still not responsive. I tried then with the old one. Same issue.
Then I tried 5 other roms:
- lineage-19.1-20220329-UNOFFICIAL-daisy
- OctaviOS-v3.0-daisy-20211023-2257-GAPPS-Official
- syberia_daisy-v5.4-20220420-1948-OFFICIAL
- miui_DAISYGlobal_V11.0.5.0.QDLMIXM_4e152f6600_10.0
- crDroidAndroid-12.1-20220510-daisy-v8.4 --> Current installed rom.
Still the same issue... So I've started thinking that I've damaged the already broken screen during the disassembly process and that I've received a defective new one. But the odds are poor...
One more thing. When I boot my phone, I've a following message: "Your device software can't be checked for corruption. Please lock the bootloader."
So I've lock the phone, and then it cannot boot anymore. If I unlock it, the phone is able to boot correctly.
This is the first time I'm encountering this kind of issue. I've already done multiple reflashes on a OnePlus One with screen replacements also, and everything was always working perfectly.
What do you think about this issue?
Is it hardware or software issue?
What could I do to continue to troubleshoot and see what is causing the problem?
Thanks for your help!
I mean you could try locking the bootloader and then flashing the stock rom.
I think it's a hardware problem, but don't quote me on that.
Ezement said:
Hello everyone,
Few weeks ago, I broke the screen of my MiA2 Lite. The touchscreen was still working perfectly, but nevertheless, I decided to change the whole display.
And... The touchscreen of the new display was not responsive also. So I've switched back to the old one. Same issue.
I've read somewhere, that a reflash could help to fix this issue.
So, I've installed TWRP and flashed a first rom: miui_DAISYGlobal_V11.0.21.0.QDLMIXM_c6721a4b58_10.0.
I tried then to boot, the phone boots correctly, but the new touchscreen was still not responsive. I tried then with the old one. Same issue.
Then I tried 5 other roms:
- lineage-19.1-20220329-UNOFFICIAL-daisy
- OctaviOS-v3.0-daisy-20211023-2257-GAPPS-Official
- syberia_daisy-v5.4-20220420-1948-OFFICIAL
- miui_DAISYGlobal_V11.0.5.0.QDLMIXM_4e152f6600_10.0
- crDroidAndroid-12.1-20220510-daisy-v8.4 --> Current installed rom.
Still the same issue... So I've started thinking that I've damaged the already broken screen during the disassembly process and that I've received a defective new one. But the odds are poor...
One more thing. When I boot my phone, I've a following message: "Your device software can't be checked for corruption. Please lock the bootloader."
So I've lock the phone, and then it cannot boot anymore. If I unlock it, the phone is able to boot correctly.
This is the first time I'm encountering this kind of issue. I've already done multiple reflashes on a OnePlus One with screen replacements also, and everything was always working perfectly.
What do you think about this issue?
Is it hardware or software issue?
What could I do to continue to troubleshoot and see what is causing the problem?
Thanks for your help!
Click to expand...
Click to collapse
how did you use twrp without a touchscreen?
Thank you for your reply.
So, I first I've locked the bootloader.
And here is the first issue, I was no more able to boot TWRP.
When I lock the bootloader, I cannot use "fastboot boot twrp.img" and I cannot press Volume Up + Power to boot it.
So then I tried to unlock the bootloader. I first tried to flash 2 stock roms, but I've always "Invalid zip file format !".
Then I've downloaded a custom rom (Lineage). And the system boot correctly (but touchscreen still not working).
After this test, I've relocked the bootloader, and when I reboot, I've the following message: "The system has been destroyed". If I unlock again the bootloader, the system starts normally, but the touchscreen is still not responsive.
jons99 said:
how did you use twrp without a touchscreen?
Click to expand...
Click to collapse
I use a mouse plugged in the micro-usb port.
PhotonIce said:
I mean you could try locking the bootloader and then flashing the stock rom.
I think it's a hardware problem, but don't quote me on that.
Click to expand...
Click to collapse
Have you tried this?
Obviously neither twrp/custom roms will work with a locked bootloader, as they aren't signed images which the locked bootloader is supposed to boot.
Hello PhotonIce, sorry for very late answer.
Ezement said:
Thank you for your reply.
So, I first I've locked the bootloader.
And here is the first issue, I was no more able to boot TWRP.
When I lock the bootloader, I cannot use "fastboot boot twrp.img" and I cannot press Volume Up + Power to boot it.
So then I tried to unlock the bootloader. I first tried to flash 2 stock roms, but I've always "Invalid zip file format !".
Then I've downloaded a custom rom (Lineage). And the system boot correctly (but touchscreen still not working).
After this test, I've relocked the bootloader, and when I reboot, I've the following message: "The system has been destroyed". If I unlock again the bootloader, the system starts normally, but the touchscreen is still not responsive.
Click to expand...
Click to collapse
Like I've explained here, the problem is that I do not succeed to lock the bootloader and then flash a stock rom.
In fact I don't know how to flash with a locked bootloader.
lock the bootlaoder and flash the signed stock rom using mi flash tool (the official flashing tool)