Hi Folks,
I have a M8 Dual SIM which I have manged to brick. Despite reading the whole damn internet, every thread there is I have been unsuccessful in restoring. Here is the awful situation:
Unlocked boot loader
Flashed TWRP
Super SU
Flashed custom ROM
All good however after about a week the phone decided to not reboot into the OS.
Re-flashed TWRP, via fastboot, this worked however ADB wouldn't recognize the device, now its in an infinite boot loop, boot-loader is accessible but just drops into the boot again. the TWRP flash screen appears flickering during boot. No OS on the phone now, just data partitions. No Nandroid backup. I could push a ROM via ADB if I could get the recovery stable. S-ON BTW.
Any advise will be gratefully received.
Hi all, thanks for your help in advance
Nexus 5X 32GB previously on 6.0.1 MMB29K I believe, rooted and unlocked, was running xposed and decrypted. It was running just fine until a few weeks ago, where right in front of my eyes while I was using it, it crashed and shut off (battery saver was on too). Then it wouldn't turn on for a day or two no matter how long I pressed the phone's keys.
Now when I boot it without sim card, it will freeze during the boot animation and then either shut off or try again. When I try with sim card in, it appears the kernel crashes with the Crash on the LK! screen. Without sim, I can access fastboot and recovery just fine (previously that was also hit or miss). I have manually flashed stock everything, and it hasn't been fixed (also tried reset via stock recovery). I might have a backup but it would be on my school computer and I'm not back to uni yet.
Any ideas for what I can do to try and fix it? Can I relock my 5X in this state without bricking it? Then I could get a warranty replacement I believe?
Okay, today evening, my Nexus 5X rebootet already 5 times while I was using it just as every evening (browsing web, watching youtube, nothing special).
After the second reboot, it actually vibrated two times during the boot animation (after entering the decryption pin) like it usually only does when powering it up.
After the third reboot, it bootlooped for more than 30min (!!) ... Just the bootloader (white google logo), then ~3s black screen, then vibrating and Google Logo again!
Entering boot menu was possible... I used it to power off and reboot, but didn't help. I was just letting it bootloop while I searched my old Nexus 4 to reactivate it
After the 30min or more bootlooping (by the time I already found my Nexus 4 and reinstalled its battery ) the Nexus 5X asked for decryption pin.... I entered it, it rebootet. It asked again. If finally bootet.
After ~3min of use (just enough for a whatsapp backup) it rebootet again and bootlooped again for ~15min. And same again.
Now it is back once again - for the moment.
I need help, what can I do now, except backing up all relevant data?
It is stock android, not rooted, bootloader locked
Can I somehow test the memory? See why it rebooted?
It NEVER rebooted before since I own it...
Thx
The device rebooted after few minutes yesterday... It still overcomes the first bootloop from time to time after dozens of bootloops but then crashes most of the time after I was able to enter the pin. Since yesterday, it only managed to finish booting two times but always rebooted after few minutes.
Is this the famous BLOD? Haven't heard of it until today (sorry) ...
I actually had OEM unlock enabled in the developer menu, so I could actually unlock the bootloader...
Can I verify that it actually is the BLOD by unlocking the bootloader and temporary booting the modified boot image using fastboot? I don't want to flash something at the moment, because I might get it replaced... I can lock the bootloader again afterwards, right?
I think it might be possible to use "fastboot boot boot.img" (using the 4-core kernel image) from the bootloader screen. That won't install anything.
Thx. However, it requires me to unlock the bootloader and delete all data, since there is no 4-core kernel provided/signed by google, right? I will be able to lock the bootloader again afterwards, as long as I won't flash a different kernel (or reflash the stock kernel), right?
dude while your phone is on, first backup your files, then enable OEM unlock, if your phone is damaged with bootloop of dead, you will be able to make it work using the 4 kernels fix.
caifaz said:
dude while your phone is on, first backup your files, then enable OEM unlock, if your phone is damaged with bootloop of dead, you will be able to make it work using the 4 kernels fix.
Click to expand...
Click to collapse
I do have all important data backed up, I guess. Doing Backups for Android is just PITA... I wasn't able to get the phone running for more than a few minutes today. OEM unlock is enabled, but the bootloader is locked still, so all data will be deleted. I'll try the 4 core kernel as soon as I completely restored all data to my replacement phone, so I'm really confident I can wipe all data from the old one.
Thx so far!
RFZ said:
I do have all important data backed up, I guess. Doing Backups for Android is just PITA... I wasn't able to get the phone running for more than a few minutes today. OEM unlock is enabled, but the bootloader is locked still, so all data will be deleted. I'll try the 4 core kernel as soon as I completely restored all data to my replacement phone, so I'm really confident I can wipe all data from the old one.
Thx so far!
Click to expand...
Click to collapse
you're welcome, there is no need to flash a bootloader, just flash the TWRP recovery (modded for 4 cores), restart to recovery and then flash EX kernel (modded for 4 cores) according to you SO version.
I have fixed a phone 2 years ago using this instructions
Okay, I just verified it... The device boots fine with the 4 core kernel. I then reflashed the stock image, locked the bootloader, and it bootloops again. Will send it back to the store now and hope I'll get a refund/replacement :fingers-crossed:
Hi
My phone is a G5 that was as new, never altered: bootloader was still locked, USB debugging and other special stuff were never changed.
Suddenly, the phone entered in bootlook, and booting in recovery mode shows "baseband: unknown".
Is there a way to repair the phone by reflashing it to stock rom in these circumstances?
Thank you for your help!
You can either
Enter recovery mode and format data and see if the phone boots
Or flash stock firmware via fastboot
Both of these can be done on a totally unmodified phone
I recently installed Evolution X 4.1.69 after unlocking my bootloader in my Pixel XL. After installing the custom ROM, I found that the OEM locking has been greyed out in the developer option.
Since the built of the custom ROM wasn't stable at that time, I decided to revert back to stock ROM. Unfortunately, I relocked my bootloader before recovering the factory image of the stock ROM.
After that, my phone screen starts flashing with the Google sign and keeps rebooting. I am able to access fast boot but I cannot access recovery mode from there. Pressing the recovery option from there will still lead me to a continuous boot loop, similar to what happen whenever I boot the phone.
I have tried these attempts with no avail.
1. fastboot oem unlock, failed since my bootloader is locked.
2. fastboot oem reboot-download, it causes continuous bootloop.
3. adb sideload bootloader.img, since I cannot access recovery mode, sideloading the factory image doesn't work as well.
4. flash factory image, failed as it still requires me to have an unlocked bootloader in order to do so.
Any suggestions on what I should do besides replacing the motherboard or RMA is greatly appreciated! Thanks!
you relocked your bootloader.
user error.
You sound pretty sure that you locked your bootloader. Did you actually go through steps to do so? Or was it just the grayed out option in developer settings? Have you tried to boot to TWRP or Lineage Recovery from fastboot?