Hi everyone.
Last night my phone ran out of power and when I charged it back up it wouldn't boot at all, so this morning I decided to try and fix it but I think I have just screwed it up even more to the point that its completely bricked.
I could still access TWRP and tried to reinstall the firmware and flash TWRP through the checkbox execpt about 1 minute in the screen went off due to the time out, but the screen wouldn't come back on at all so I left it for an hour just in case if it was still running in the background, after this time I hard restarted the phone and entered TWRP again and but it didn't install the firmware properly and my computer wasn't reading the phone properly so as a test I tried to swap bootloader from A to B stupidly and now I can't seem to access anything, only thing I can do is the menu where it says start, power off, recovery mode and restart bootloader. Pressing any of these settings seems to just put me back in to this menu again.
When plugging in the phone in to the PC it make's no noise at all as well.
Have I completely hard bricked my phone? Or is there a way to fix it?
Thanks Ben
All fixed I flashed the RAW firmware
Related
Alright. This is a 100% stock Nexus S- nothing "development" wise was done to the device, no system tools installed that could cause issues, basically nothing but basic apps loaded on the device.
It just started today. I was working on my bf's Vibrant (another, more successful story) and grabbed my Nexus and hit the power button and it did not turn the screen back on. Holding the power button down did not reboot the device, and none of the buttons would light up or function.
So, I pulled the battery. Now every time I try to boot, it hits the "Google" screen and stays put. I left it alone for 5 minuets hoping it would finish booting and nothing. The soft buttons will light up, and if I touch them they register the touch but it does not help the phone to boot.
I do know that the phone was basically dead right before this happened, and at first I thought it was just dead. However, its been on the charger for at least 30 minuets- which should have given it enough of a charge to boot up, and still nothing.
What could cause this issue?
I did install a couple of new applications today, and I know the market updated a bunch of them but they're all apps that I've had on several phones (minus the two new ones today) and have never had an issue with any of them. The two new ones I downloaded were OS Monitor, and a 2G/3G toggle for hopes of improving some battery life.
But those are the only two things I've done differently. I've only been using the phone for a week but I haven't had any problems at all, before this.
Now- if worst comes to worst I can seem to get into the bootloader, and through that, stock recovery. So I can try to do a factory reset and wipe cache but without a backup I really kinda hope thats a last resort.
Please help, and let me know if you need any more information.
Thank you!
I understand that you're fully stock which I assume means you have a locked bootloader (everything I say from here on out assumes as such)? First, I'm going to also assume that you didn't update to 2.3.3? If not, then follow the steps in this guide to boot into a custom recovery and from there go to backup and restore and do a NANDroid backup. Now go to mounts and storage and mount USB storage (or whatever its called, don't have my phone right here). Plug your phone into your comp and copy over whatever you'd rather not lose from your SDcard (just in case you have to wipe). Now download the 2.3.3 update from here and put it on the root of your SD card. Now go back and flash this. Reboot and see if you're golden. If so, great, if not try a factory reset.
If that doesn't work go through the steps again to boot into a custom recovery, you might have to unlock your bootloader and wipe all your data (again) and restore your backup and try doing a factory reset with that. Don't worry about unlocking the bootloader, it can be relocked with a simple command and it won't wipe anything to relock it.
Here is the command just in case:
Code:
fasboot oem lock
I got all the way to having clockwork recovery booted up on the phone, but nothing would mount. Everything gave me an error, and factory reset froze...
I don't think there is anything I can even do from here, is there?
I woke up to find my phone off, I knew the battery was charged so I turned it on, when the phone booted and got to the lock screen the powering off box popped up and it shut down. I tried multiple times to boot but every time the powering off box would pop up and the phone would shut off. So I booted into recovery and wiped the phone, that didn't fix it, the phone is still shutting down upon boot, does anyone have any suggestions?
Update: I have flashed the stock rom and wiped all the caches and its still shutting down once it gets to the lock screen. Its almost like the power button is stuck, but I'm able to navigate in recovery fine so I don't believe that's possible.
I followed the steps on how to unroot and reset the phone to completely stock and the problem still persists, anyone have any idea?
TheSnuke said:
I followed the steps on how to unroot and reset the phone to completely stock and the problem still persists, anyone have any idea?
Click to expand...
Click to collapse
If you have flashed the factory images and so on and all of this still persist than it's RMA time.
So it started out that CM 12 kept shutting down on me, the phone would occasionally just power off. I tried restoring some of my TWRP backups but they seemed to be corrupted.
So I decided to try RSD and reflash the stock firmware and go back to 4.4. I let it flash and then when I booted up I kept getting a message saying that the phone was going into cool down mode, but the phone never actually got hot. So I decided to try and reflash the stock 4.4 firmware again in RSD. This time I watched the phone screen as it went through and just after the system image (#7 of 17) I would get a message in "RED" letters that reads "sp space is not enough". It would continue to flash the rest of the images and then reboot. And it would have the same problem with saying the phone is going into cool down mode and sometimes it would shut off, but the phone never gets hot.
I thought maybe I had a bad download / firmware image so I tried several 4.4 images including one directly from Motorola but I get the same message every time I flash the stock 4.4 ROM.
*While it is plugged into the computer the phone stays on, but once I disconnect from the computer it shuts down again.
So I thought I would try flashing TWRP and CM 11 and then CM12, but the phone will boot up and then shortly after boot up it will shut down.
I have spent hours looking for a solution online and I do find that there have been multiple reports of this same problem along with photos of the phone screen message, but I have not found an explanation or a solution.
Does anyone have any idea what the problem is or how to fix it?
morr22066 said:
So it started out that CM 12 kept shutting down on me, the phone would occasionally just power off. I tried restoring some of my TWRP backups but they seemed to be corrupted.
So I decided to try RSD and reflash the stock firmware and go back to 4.4. I let it flash and then when I booted up I kept getting a message saying that the phone was going into cool down mode, but the phone never actually got hot. So I decided to try and reflash the stock 4.4 firmware again in RSD. This time I watched the phone screen as it went through and just after the system image (#7 of 17) I would get a message in "RED" letters that reads "sp space is not enough". It would continue to flash the rest of the images and then reboot. And it would have the same problem with saying the phone is going into cool down mode and sometimes it would shut off, but the phone never gets hot.
I thought maybe I had a bad download / firmware image so I tried several 4.4 images including one directly from Motorola but I get the same message every time I flash the stock 4.4 ROM.
*While it is plugged into the computer the phone stays on, but once I disconnect from the computer it shuts down again.
So I thought I would try flashing TWRP and CM 11 and then CM12, but the phone will boot up and then shortly after boot up it will shut down.
I have spent hours looking for a solution online and I do find that there have been multiple reports of this same problem along with photos of the phone screen message, but I have not found an explanation or a solution.
Does anyone have any idea what the problem is or how to fix it?
Click to expand...
Click to collapse
I had tried everything I could think of and it appeared that there was a partition problem. The phone continued to shut down and would only stay on while connected to the PC. If it were a PC I would reformat and re-partition the drive but I did not want to risk a permanent brick by messing with it.
So, as a last ditch effort to try and get my phone functioning again I let it download and install system updates. The phone is now working again, it has not shut down at all and there have been no warning messages about cool down mode.
BUT, I am now on "4.4.4, SU-5-24, build 23.3.24 dated 10-27-14. Since my boot loader is unlocked I flashed TWRP but it would not not accept Super SU zip so I am no longer rooted.
I finished reading up on it in the forums and realize I am pretty much screwed as far as root goes. But at this point I don't even care anymore. I just need to get the phone functioning correctly.
*So, I am still having the problem with flashing stock and getting the "red" letter message after system image boots saying "sp space not enough". So long as it is hooked up to the computer it stays on and if it is downloading or installing an update it stays on and I never get a warning about cool down mode and it does not shut off, but once I disconnect from the computer it starts all over again. The phone boots up but at random intervals it still either gets a pop up message saying that it has gone into "cool down mode" or it shuts off. It is not doing it as often as before, but it is still doing it. Does anyone have any suggestions on whats causing it or how to fix it? It sounds like a software / firmware issue but I am not sure how to fix it.
*Update. The phone is still not functioning correctly. At times it will appear to work fine for hours with frequent to heavy use at times then suddenly it will start acting up, the phone will shut down randomly and when it reboots some of my settings have changed. The temperature is usually pretty low but once in a while after a shut down I will check the temp when I'm able to reboot it and it will be high. When it shuts down like that I usually have trouble getting it to boot up again unless I plug in the factory cable, either in the PC or just the wall charge then it seems to boot up fine and I can even reboot it but once it shuts itself down it doesn't want to start again unless I use the factory cable.
It really does sound like a software / firmware / partition problem but after multiple attempts to flash the firmware with RSD I continue to get the same error message at the end of the system flash and the phone continues to have problems. Does anyone have any suggestions?
Got me an xt1080 which I'm trying to restore to stock, and in both House of Motor and RSDlite 6.2.4 at some point during the system partition flash 'so space is not enough' as well. The phone is in perpetual bootloop, unless I use a 'Factory/power' cord and starting up in fastboot (eventually). Tried both 1FF and CFC fxz files, no luck.
Hey XDA,
I have a D800 that is totally stock. I have no custom recovery, and have never rooted the device.
A couple days ago I got the notification for an OTA update. I hit the notification, and rebooted the phone. It started the update process. It got through the first step. When it started the second part of the update, a black box popped up, and a code like "ERR 0x04ff" or something like that popped up. The phone rebooted, and got stuck in a boot loop with a "Security Error." The phone will boot up, show the LG logo, then show a slightly different LG logo with "Security Error" underneath it, then reboot and start the process over. I started messing around with the power button and volume keys to see what different modes I could boot it into. Initially I could boot it to the Factory data reset screen, the Hardware Mode Keys screen, and I got it into Download mode once. I didn't have any of the software or files available at the time to do anything with Download mode, so I opted to try a Factory reset. The phone attempted a Factory Reset. The little android with wiggly ears, and the spinny cube thingy popped up for about 4 seconds, and the phone rebooted.
Since trying that initial Factory Reset, I have been unable to get the phone into Download mode. I've tried doing the Factory Reset multiple times to no avail. I have not seen fastboot at all.
At this point, the only thing I can do with the phone is boot it to the Factory Data Reset screen, and to the Hardware Keys Mode screen. It will not do a factory reset. The android pops up for about 1-2 seconds, and the phone reboots, and goes right back to the boot loop with the security error.
I'm at a loss at this point. I've called AT&T, and unfortunately my phone is out of warranty by about 3 weeks. So they can't just mail me a replacement. Does anyone have any ideas? I can't seem to get it to be recognized by my PC, on Windows or Ubuntu. I get the feeling that it's just hard bricked, and there really isn't anything else I can try.
Any suggestions would be greatly appreciated
TL-DR: Totally stock D800, no custom recovery or root. Security Error Boot Loop after OTA attempt. No download mode or fastboot, factory reset is ineffective. Not recognized by PC. What do I do now?
bob51dole said:
Hey XDA,
I have a D800 that is totally stock. I have no custom recovery, and have never rooted the device.
A couple days ago I got the notification for an OTA update. I hit the notification, and rebooted the phone. It started the update process. It got through the first step. When it started the second part of the update, a black box popped up, and a code like "ERR 0x04ff" or something like that popped up. The phone rebooted, and got stuck in a boot loop with a "Security Error." The phone will boot up, show the LG logo, then show a slightly different LG logo with "Security Error" underneath it, then reboot and start the process over. I started messing around with the power button and volume keys to see what different modes I could boot it into. Initially I could boot it to the Factory data reset screen, the Hardware Mode Keys screen, and I got it into Download mode once. I didn't have any of the software or files available at the time to do anything with Download mode, so I opted to try a Factory reset. The phone attempted a Factory Reset. The little android with wiggly ears, and the spinny cube thingy popped up for about 4 seconds, and the phone rebooted.
Since trying that initial Factory Reset, I have been unable to get the phone into Download mode. I've tried doing the Factory Reset multiple times to no avail. I have not seen fastboot at all.
At this point, the only thing I can do with the phone is boot it to the Factory Data Reset screen, and to the Hardware Keys Mode screen. It will not do a factory reset. The android pops up for about 1-2 seconds, and the phone reboots, and goes right back to the boot loop with the security error.
I'm at a loss at this point. I've called AT&T, and unfortunately my phone is out of warranty by about 3 weeks. So they can't just mail me a replacement. Does anyone have any ideas? I can't seem to get it to be recognized by my PC, on Windows or Ubuntu. I get the feeling that it's just hard bricked, and there really isn't anything else I can try.
Any suggestions would be greatly appreciated
TL-DR: Totally stock D800, no custom recovery or root. Security Error Boot Loop after OTA attempt. No download mode or fastboot, factory reset is ineffective. Not recognized by PC. What do I do now?
Click to expand...
Click to collapse
Try this guide, it should help. Good luck.
http://forum.xda-developers.com/showthread.php?t=2662445
Sent from my LG-D800
Swetnes said:
Try this guide, it should help. Good luck.
http://forum.xda-developers.com/showthread.php?t=2662445
Sent from my LG-D800
Click to expand...
Click to collapse
Thanks for the reply. I was about to reply saying my phone wouldn't go into download mode, but then I randomly decided to use a different usb port, and now it went into download mode.
I'll give it a shot now and see what i can do
Ok, It seems I'm back up and running. I followed this guide http://forum.xda-developers.com/showthread.php?t=2432476 which re-flashed me to 4.2.2. I'm going to try and upgrade using LG PC Suite from my laptop, and see if I have better luck this time.
Lesson learned, try every USB port when trying to boot into download mode.
Thanks for the help
Hi, it is an older device so you might have experienced everything possible.. so,
After a long time of trying to fix that phones mind, I wiped everything avaible in TWRP
multiple times(got mad). Last thing was data.
That way I went from a bootloop to an active nothing.
Phone does not react to any command, it does not react to USB charging or on PC.
That's the case a few months back, the phone halfway in the trash and I bought
myself a iphone (hate it).
I put the Galaxy S7 on a charger today and it starts immediatly in to TWRP.
From there I tried to install a ROM that's left on the SD card, which forced
a restart into TWRP. Into download mode I managed to install the stock Oreo ROM via Odin.
It went through like a charme, all green. PASS!
The phones screen is black and does not react to any command, nothing.
I had "auto-reboot" activated.
The phone is active it's warm and I'm waiting for the battery to die again, to restart.
..meanwhile,
Can you give some advice please?
Why would the phone have struggle with the boot with stock rom installed.(which has worked before,no updates installed)
When should I install TWRP?
When do I install what kernel?
Last thing running was the LightROM with moro kernel with nothing tweaked.
Also. The issue why i deaded the phone was a camera/flash thing, where I could only take pictures with flash activated.
Front and back camera. On all camera apps, I couldnt scan my ID for banking due to that.
Also on different kernels and different ROMs including the Samsung stock.
Why would that be
Could not accept...
Jvers said:
Hi, it is an older device so you might have experienced everything possible.. so,
After a long time of trying to fix that phones mind, I wiped everything avaible in TWRP
multiple times(got mad). Last thing was data.
That way I went from a bootloop to an active nothing.
Phone does not react to any command, it does not react to USB charging or on PC.
That's the case a few months back, the phone halfway in the trash and I bought
myself a iphone (hate it).
I put the Galaxy S7 on a charger today and it starts immediatly in to TWRP.
From there I tried to install a ROM that's left on the SD card, which forced
a restart into TWRP. Into download mode I managed to install the stock Oreo ROM via Odin.
It went through like a charme, all green. PASS!
The phones screen is black and does not react to any command, nothing.
I had "auto-reboot" activated.
The phone is active it's warm and I'm waiting for the battery to die again, to restart.
..meanwhile,
Can you give some advice please?
Why would the phone have struggle with the boot with stock rom installed.(which has worked before,no updates installed)
When should I install TWRP?
When do I install what kernel?
Last thing running was the LightROM with moro kernel with nothing tweaked.
Also. The issue why i deaded the phone was a camera/flash thing, where I could only take pictures with flash activated.
Front and back camera. On all camera apps, I couldnt scan my ID for banking due to that.
Also on different kernels and different ROMs including the Samsung stock.
Why would that be
Could not accept...
Click to expand...
Click to collapse
OK so what you've done is correct flashing stock (which includes stock kernal). You have to make sure the stock ROM is correct for your device and region or it will not start.
It's not unusual to have to flash it twice with Odin.
Next up you don't need to wait for batt to die to restart. Press volume down+home+power and keep them pressed until phone restarts. Should now be in download mode, reflash correct ROM with Odin. TWRP is wiped off the phone when you flash a stock ROM.
If it doesn't go through the boot up/freezes/ does nothing etc. You need to "wipe cache" then reboot from the recovery menu.
Press and hold volume down+home+power. As soon as the screen goes black move your finger to volume up (it may take more than one attempt). Once your in recovery menu use volume up and down to move through options and power to execute. Wipe cache then reboot and allow the phone to go through all the reboot stuff. It can take a few minutes just leave it alone. It will also reboot a couple of times.
If it does nothing after 15 minutes then start again and repeat the process.
Thanks for reply.
The Phone was off for a day and after charging for 1h it still does not react to any command. Vol down + home + power does nothing. Same with vol up.
Is there a way to force a boot? Even if the PC does not recognize a device on usb?
I Tried the commands 30 secs each, plugged in and off. Also usb port is not broke since the phone is getting temperature after a while charging..