Hey all, new guy here with a really frustrating problem.
I have a nexus 5 that I was preparing to hand down to my wife. I had transfered everything over to my new phone, and initiated a factory reset. It rebooted to the "erasing" screen, and sat there for about 20 minutes, before switching to the dead android screen (w/ red triangle.) I thought that was odd, did some searching, and tried the recovery mode from the bootloader. That produced the same results. So now I'm stuck.
From the boot loader I can access the following options:
Start -> Erases for ~20 minutes, then dead android
Restart Bootloader -> Screen goes blank, phone vibrates, and then back to the bootloader screen
Recovery Mode -> Erases for ~20 minutes, then dead android
Power off -> turns off the phone
I called Google, and the tech support hadn't heard of anything like this. Because it's almost two years old, he transferred me to LG's tech support, who basically said find a local repair shop, or they could RMA it for an unknown cost. I called my local repair shop, and they didn't think they could help.
I'm pretty sure the phone is bricked at this point, which is frustrating, because it was running stock android - completely unmodified. I think I might have rooted it once, months ago, but I can't imagine that that would have caused this issue. I had even received and installed Marshmallow OTA, and it was running perfectly.
Anyway, I'm hoping (but not expecting) someone on here might have a brilliant idea, or some program I might be able to use on the PC to regain access to my device.
Literally the only information I can provide about the phone at this point in time is as follows:
Product_Name - hammerhead
Variant - hammerhead D820(H) 32GB
HW Version - rev_11
Bootloader Version - HHZ12k
Baseband Version - H8974A-2.0.50.2.27
Carrier Info - None
Serial Number - 047....
Signing - Production
Sercure Boot - Enabled
Lock State - Unlocked
Thanks,
Ian
Update
So I followed the tutorial on flashing your device with the stock rom (http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701) and it appears to have done... something. Not sure what yet.
I was able to get through the tutorial, and flash all the images onto the phone. I got to the following step:
★After everything finished, select "Recovery" using the volume buttons.
And it went back to the erasing screen. I thought that I was still screwed, so I went back to the fastboot screen. Then I decided what the hell, I might as well let it officially die again, instead of just assuming it would.
I let it do it's thing, and it got through "Erasing", only for it to restart and BOOT! YAY! I was worried when it got to the 4 dots, as I thought maybe it was going to get stuck in a bootloop there, but it just started up the welcome screen. So hopefully it's good to go!
I'm glad that you got it working again. Best way to recover a bricked phone is by installing a factory image, just like you did.
Related
My Nexus 5 seems to get stuck at the update screen (the standing green android with the spinning polyhedron) after flashing to stock(+unroot) with softbrick/bootloop checked. The flash completed without error. I've left it at this screen for over an hour and not only does it not progress it doesn't even get to the progress bar at the bottom.
This afternoon my (unrooted, bootlocked, stock) N5 turned itself off 3 times while on the charger. Powered back on and then would find it turned off 20 or so minutes later when I checked it again. After the third time it booted to the "Google" screen and would go no further. I tried a hard reset but it gave an error. So I plugged it into my laptop and fired up Wug's NRT, unlocked the bootloader (at which point it got stuck at the same update screen described above for around an hour). I held power till it went off, booted back into bootloader (which showed as unlocked) and performed the flash to stock(+unroot) with softbrick/bootloop checked and ended up at the update animation again. Any thoughts other than RMA?
****Edit: Finally got the phone to boot after fastboot booting twrp. Was able to to wipe the phone (after multiple attemps blocked by can not mount storage/cache/etc/etc errors). Flashed 4.4 and the phone now boots to android BUT radio is non-functional (no signal despite being in my normal coverage area), any attempt to add an APN causes a hard reboot (had to go through all the setup screens again). Additionally, the phone won't turn off, even hard power downs (holding the button for 30 secs) lead to an immediate reboot. Still RMAing but I was able to relock the bootloader.
You really shouldn't RMA a phone after messing it up yourself by using a toolkit when you didn't know what you were doing.
Flash the factory images manually. That should get your phone up and running again.
Chromium_ said:
You really shouldn't RMA a phone after messing it up yourself by using a toolkit when you didn't know what you were doing.
Flash the factory images manually. That should get your phone up and running again.
Click to expand...
Click to collapse
Performed a manual flash with the exact same results. There is apparently something wrong with the hardware (which may explain why it was turning itself off and then wouldn't boot past the google logo.
gallahad2000 said:
Performed a manual flash with the exact same results. There is apparently something wrong with the hardware (which may explain why it was turning itself off and then wouldn't boot past the google logo.
Click to expand...
Click to collapse
Yep, I would agree.
I have a rooted Verizon Wireless Galaxy S3, for reference. So today I decided to attempt to install Cyanogenmod and searched for something to install it on my phone. I found Rom Manager on the Play Store and installed it, and went into it. I installed Clockworkmod and flashed it, and everything went reasonably well until I rebooted my phone. At this point, it automatically booted into Recovery Mode, or at least tried to. What it really did was display the screen with the Samsung logo and "RECOVERY BOOTING....." at the top in blue letters. Then, it shows a screen with a yellow warning triangle, which gave me the "System Software not authorized by Verizon Wireless has been found on your phone" message, saying "SECURE FAIL:KERNEL" at the top. Now, after a bit of searching, I had found that I should flash a factory image, so I connected my phone to my computer, and that's when the strange stuff began. First, my phone started vibrating approximately once every second for a short amount of time(about 0.1 second) and my computer wasn't detecting it. When I tried to turn my phone on, it just displayed the normal first boot screen and then nothing else happened, and it went back to a black screen.
I've looked all over the place, but I can't find anyone that has encountered my problems and I have no idea how to proceed.
somesortofthing said:
I have a rooted Verizon Wireless Galaxy S3, for reference. So today I decided to attempt to install Cyanogenmod and searched for something to install it on my phone. I found Rom Manager on the Play Store and installed it, and went into it. I installed Clockworkmod and flashed it, and everything went reasonably well until I rebooted my phone. At this point, it automatically booted into Recovery Mode, or at least tried to. What it really did was display the screen with the Samsung logo and "RECOVERY BOOTING....." at the top in blue letters. Then, it shows a screen with a yellow warning triangle, which gave me the "System Software not authorized by Verizon Wireless has been found on your phone" message, saying "SECURE FAIL:KERNEL" at the top. Now, after a bit of searching, I had found that I should flash a factory image, so I connected my phone to my computer, and that's when the strange stuff began. First, my phone started vibrating approximately once every second for a short amount of time(about 0.1 second) and my computer wasn't detecting it. When I tried to turn my phone on, it just displayed the normal first boot screen and then nothing else happened, and it went back to a black screen.
I've looked all over the place, but I can't find anyone that has encountered my problems and I have no idea how to proceed.
Click to expand...
Click to collapse
Were you on either of the locked bootloaders of 4.3 or 4.4.2? If so your issues lies there to begin with. No custom recovery other than safestrap will work with the locked bootloaders. Your lucky you didn't hard brick it
From my Wicked S3 on SOKP
ShapesBlue said:
Were you on either of the locked bootloaders of 4.3 or 4.4.2? If so your issues lies there to begin with. No custom recovery other than safestrap will work with the locked bootloaders. Your lucky you didn't hard brick it
From my Wicked S3 on SOKP
Click to expand...
Click to collapse
Well, can I somehow get my phone into working order? Because it's as good as bricked right now.
I've had my shield for a little over a year now... never rooted, never bootloader unlocked. I've been on the latest firmware since it came out in November, I was extracting a pokemon game rom when I had a lockup earlier, and I force shut it down and turned it back on, now I'm stuck in a bootloop! I've gone into the bootloader and launched recovery mode, but when it gets to that menu, it has the normal android with chest open background with "no command." typed below it. I need to know how I can fix it lol. I'm not rich and have handfulls of expensive android devices, so if this thing is gone for good, then fml.
I've been considering unlocking the bootloader and rooting anyway since the warranty is out so I've decided I'll unlock the bootloader, flash a stock rom extract, and root it. hopefully I can pull it off with nothing but fastboot.
Hello everyone,
I am brand new here and I have been searching for a solution to my current problem for over half a day now with no luck, and I'm hoping you guys could give me a definitive solution.
I am currently using a LGL22C (LG Power) Tracfone and I've come across a boot loop problem.
During the boot screen with the LG logo, I am presented with the following at the top left of the screen:
ERROR : boot certification verify
[450] ---------------------------------------------------------------
[450]
[450] Secure boot Error!
[450] Cause : boot certification verify
[450]
[450] ---------------------------------------------------------------
(Note: The boot loop continously restarts my phone while having 450 changing into 440 and vice-versa from time to time)
My phone was rooted via Kingroot and I've had it rooted for a little over 2 months. My phone is now in a bootloop due to the installation of Magisk v9. I accidentally installed it using Magisk Manager v2.1, which updated and installed everything that is "Magisk", which then prompt me to restart (which I did), and I'm now in this dilemma.
Again, I have searched for a solution for half a day and I did find some solutions that I thought would work, but unfortunately my phone can't:
1. Connect to my PC (No matter what I do, like update drivers)
2. LG Mobile Support Tool cannot detect nor support L22C model in its listing.
3. Doesn't have Emergency Mode, Download Mode, or Recovery Mode.
My phone CAN in fact go to Factory Reset, but that doesn't do anything in terms of solving my problem.
PLEASE I hope you can assist me. I am truly in a desperate situation.
Thank you!
UPDATE: I just tried to move my number to a different phone (LG Optimus Fuel) which I know that works for the time being. I deactivated it, added my other phone to the plan, but now it's affecting my other phone! I can somehow manage to get it to the Main Screen, but I can't uninstall anything, nor can I use the Phone app, because it states that my Contacts have stopped working (along with several other applications). My other phone has never done this before, nor did it have issues, but it started as soon as I tried to reactivate my number from my LG Power.
Sorry, this phone does not have any sort of recovery options if you trash the firmware. I am also the proud owner of a brick. I've ordered a replacement motherboard from eBay ($15) to perform a brain transplant, and then I'll have to start over.
I've had some previous experience with custom roms on my old Nexus 6P and thought I would try the same for my mate 9. Unfortunately I've discovered the Mate 9 is not as easy to install custom roms as I thought.
I've tried several things throughout the day and I feel I've accidently overwritten things I shouldn't have but can't remember everything I've done.
It is an Optus branded phone so I believe at the start of the day I had some version of L09C34. I currently have an unlocked boot loader and TWRP installed and would like to flash back to the stock firmware, but seem to be unable to do so. The boot loader is unlocked and when I try flashing extracted parts from fastboot, the phone will reboot, reboot again and sit at erecovery. Unfortunately while I can connect to wifi, no packages are found for recovery.
Additionally I now get this lovely colourful screen in lieu of the logo on initial boot.
Any help would be appreciated.
Okay, so I've managed to unbrick it and install a version of L09C432 and get it working again - thank you to various threads on XDA. I think what I noticed was that someone else had tried the C432 firmware on a C33 model and it worked. Without being able to get hold of the C34 firmware, I tried to flash nougat originally and it worked.
This morning, I've noticed I still have an issue where the touchscreen won't work when the phone is cold (i.e I can't click anything and can't turn alarms off). If I reboot the phone to recovery it's fine, so it leads me to believe its an OS thing. Also, if I give it a few minutes in my pocket, or holding my palm on the screen it then responds. This is the issue I tried to resolve by resetting and trying a different rom but seems I haven't been successful.
Finally, when I first turn the phone on and the screen lights up I see a green background with one blue and one red box. Any ideas what I have messed up there and how to fix it? I'm not too concerned, but it would be a nicety.
Just providing updates in case anyone comes a long with similar issues.
I have now fixed the strange coloured screen on initial power on. I've found the oeminfo for the C432 firmware on another XDA thread and took a backup of what was currently there, restored the C432 version and rebooted. I was presented with the eRecovery and no TWRP. Quick check in fastboot mode showed the phone relocked. I unlocked it again and it booted no issues, however was unsure if the custom rom was still installed as I was presented with the option of an OTA update. Initially my sim card was not recognised, so I had to remove and reinstall it but so far so good.
I've just reflashed my custom rom and will see how I go.
The only potential issue I have outstanding is my touchscreen not working either first thing in the morning, or when the phone is cold - i.e I've gone to the gym and left it sitting in the locker for 2 hours and I can't use the touchscreen when I come back. I can unlock it fine with the finger print reader and the phsyical buttons respond but touches on the screen won't. If the phone is left alone for a few minutes the screen shuts off and turns back on approx every 5 seconds until it becomes responsive. Has anyone seen anything like this before? My googling hasn't lead me to anything helpful.