Bootloop - Desire 816 Q&A, Help & Troubleshooting

The phone is stuck in the bootloop. It has original firmware (Lolipop) and the bootloader is locked.
So when the phone turns on it is kept alive for about 30-40 second and than it's starting to reboot. I have tried to turn on developers options in that time(and succeeded) but on the next boot developers options are turned of. Also I have tried to uninstall some random app (also succeeded) and also the app is here on the next boot.
Also tried to factory reset the phone ... nothing happens.
Also tried to uninstall apps or turn on developers options from Safe mode.
Any other ideas. (My plan was to flash custom ROM but I cant even unlock bootloader )
It's my fathers phone...it is end of the year and he is MAD AS HELL

Managed to unlock bootloader.
Does anyone know where is option to turn of fastboot on Lolipop. (on Kitkat it was under Power-Fast boot) ?

Related

[Q] 'Secure boot Error!' at boot, download mode and factory reset don't work

Hello,
Here is what led to my issue:
I rooted my phone using this method: http://forum.xda-developers.com/showthread.php?p=38886073#post38886073
Downloaded clockwork rom manager.
Here comes the thing I don't remember. At least i know that the last thing i did was to click on 'backup current rom'
After this the phone reset itself and this message came up:
Secure booting error!
Cause: boot certification verify
Then i tried to reset using the power button, which led me to the 'battery full' screen - afterwards i was able to reboot. As stupid as I am I just tried the same thing again. And ever since i am stuck at the 'Secure booting error!' screen.
I am unable to enter download mode. I get to the 'Hard factory reset' screen, but if i accept doing so, it says 'Secure booting error!' again.
I also remember clicking on 'restart into recovery mode' at some point, but this is not the last thing i did.
I am really desperate. Please, help me!
Well i had the same issue today... It happened after i did two changes. One of them was to to try to relock from freegee and flash twrp again from freegee. In my case i was able to go in download mode and flash original kk rom with lg flash tool.
Unfortunatly, trying to boot in downloadmode, i still get the same error :/
Jubi-Wan said:
Unfortunatly, trying to boot in downloadmode, i still get the same error :/
Click to expand...
Click to collapse
How are you trying to boot into download mode? And what factory reset screen? It seems as though you did not unlock the bootloader using freegee, if you make any changes and relock the boot loader you will get that error. But it seems that it has not been unlocked. If you hold power and volume up what happens? Same thing when power and volume down, one of them is recovery (possibly factory reset you are seeing) and the other is download mode. I don't remember right now but you should read the whole softbrick thread and see if you are missing something. You may need to use LGPNST to go back to stock, you can also use that program to flash a new recovery so read carefully and follow all steps.
When this happened to me I was able to flash an unlocked bootloader and it allowed me to use my phone again as it was before doing something stupid (for me it was an attempt to re lock the bootloader).
well, i managed to get into download mode. Obviously i used the wrong method to get into download mode...
I used this method and everything worked fine, so far. : http://forum.xda-developers.com/showthread.php?t=2249500
My phone doesn't boot now. Fast Boot doesnt work aswell.
All that happens is a white battery showing on the screen and when i try to fastboot all that happens is that the LED is blinking or glowing red after some while.
Jubi-Wan said:
well, i managed to get into download mode. Obviously i used the wrong method to get into download mode...
I used this method and everything worked fine, so far. : http://forum.xda-developers.com/showthread.php?t=2249500
My phone doesn't boot now. Fast Boot doesnt work aswell.
All that happens is a white battery showing on the screen and when i try to fastboot all that happens is that the LED is blinking or glowing red after some while.
Click to expand...
Click to collapse
What do you mean when you try to fastboot? Fastboot is basically the bootloader and allows you to select recovery or download mode. What you should have done after following that thread is go to recovery and wipe everything and flash a new ROM.
If you are saying that the bootloader is not coming up and allowing you into recovery then I believe something was missed.
After trying out some varioants of this it worked: http://forum.xda-developers.com/showthread.php?p=40274560&highlight=red+led#post40274560
I wiped the phone, but since I had to leave over the weekend i just turned it off and went away.
Now that I am back, nothing works now :/ The Phone doesnt react to anything, not even donwload-mode.
Is the battery too low maybe? It's on the wall now for a few hours, but it still doesn't react. It's not warm either.
edit:
when i charge the phone, i will get a 'watchdog bark' after some time allowing me to get into recovery. accesing downloadmode from there doesn't do anything. strangely, the recovery isnt trwp although it should be because teenybin comes with it. it's 'bbs.gaodi.net' which doesn't have a sideload feature. what do i do now?
edit2:
after 10000 tries i got into download mode. i don't want to **** up now so i won't do anything until i know exactly what to do.
any advice?
edit3:
got it working by flashing another teenybin which included trwp - then i installed miui via sideload. i don't have signal though, but i will open another thread for this since this is another issue.

[Q] Phone randomly crashes, trying to root now.

I had the phone for about a month now, i bought it on ebay it stated it was New, i check and it is still locked S-On.
But just randomly it started to crash and reboot. I tried all the basic steps, remove apps but every time it reboots it reloads everything back on it.
I tried both hard reset and factory reset both did not work. I'm noticing that i cant turn off fast boot because once it crashes and reboots, all the setting and apps go back to the way it was. Now I'm trying to root it to see if that would cure the problem and thinking possibly an update got corrupted or something and i know once you root it, it will erase all internal data.
While trying to root it, i got all the way to loading the bootloader and once i selected yes to unlock bootloader, it restarted but nothing happened it went back to the way it was. I've tried to delete/erase my data and cache through windows command but keeps saying it failed. Also now i cant start the bootloader over again.
Any ideas what i can try or do? is there an Hboot loader since I'm not able to turn off the fast boot in the setting?
I'm very new to rooting but catching on quickly.

Bootlooped 30min, then came back. Memory corrupted? How do I check?

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:

Nexus 5X DEAD/Bootloop

My Nexus 5x that was running 8.1 just randomly turned off yesterday and won't boot into android. Sometime later i tried to turn it back on and it worked and it turned off by itself 2 mins later. i somehow manged it to get into fastboot mode and I then unlocked the bootloader and flashed the stock firmware . But that did not help at all , in fact the phone was now completely dead and it only goes into fastboot sometimes while the other times it being stuck in a bootloop . while luckily when it went into fastboot, i have tried installing different boot images like boot4core but it still wont do anything its really weird,sometimes it doesn't respond to any key combination while sometimes it would go normally into fastboot. Need help , i Have no clue!! plzzz
Same Problem here! Running 8.1 and tap Uppdate Chrome and Alexa App, that the Phone freez and Reboot. After reboot he try to load the apps but freez. Now it wont boot to system and recovery say no command. When i now will enter Recovery the Phone reboots.
No open bootloader and no root. Stock 8.1 Rom from Google
Edit: Try to start Phone in Secure Mode (When Google Logo Popps up press Volume -) Say the System is Corrupt and do a Factory Reset. After Reset the Phone stuck on Boot too
Edit Edit: OK think thats the CPU Hardware Bug. Phone dont start anymore...
keltemp said:
My Nexus 5x that was running 8.1 just randomly turned off yesterday and won't boot into android. Sometime later i tried to turn it back on and it worked and it turned off by itself 2 mins later. i somehow manged it to get into fastboot mode and I then unlocked the bootloader and flashed the stock firmware . But that did not help at all , in fact the phone was now completely dead and it only goes into fastboot sometimes while the other times it being stuck in a bootloop . while luckily when it went into fastboot, i have tried installing different boot images like boot4core but it still wont do anything its really weird,sometimes it doesn't respond to any key combination while sometimes it would go normally into fastboot. Need help , i Have no clue!! plzzz
Click to expand...
Click to collapse
My daughters phone just started doing the same thing this morning. Haven't gone through any tests yet, but it is constantly restarting. Can't get it to go into recovery through normal means.

Razer phone 1 bootloop

I was recently trying to do the latest OTA update on y razer phone 1, but I seem to have messed things up. Now my phone is in a boot loop, I can't get to the bootloader or recovery with the volume buttons, and it won't boot past the logo, so I can't use adb to get there either. Not sure what to do. Basically it's turning on, showing that the device is untrusted cause of the unlocked bootloader for 5 seconds, then turning off. I'm not sure what to do.
I have/Had (Not sure) Twrp as my recovery, and reflashed my boot.img... I'm guessing I flashed the wrong one.
I can confirm that I no longer have twrp. I managed to boot to recovery, and it's the OG. It's all rainbow static, but I can tell that it's a menu with 9 options, and the third one lets adb see my phone. At this point, I'm not flashing anything or really touching anything till someone can tell me what I did wrong/how to fix it. Would a factory reset make things better? Or worse?

Categories

Resources