Hello,
My Nexus crashed yesterday, showing screen artifacts. Now it only gets to the Google Logo with the lock-symbol at the bottom. After a few seconds, it crashes again, again with artifacts. Recovery will crash in the same way.
The bootloader also shows these artifacts, but is (partly) functional.
My PC recognizes the device, but as soon as I try to flash, the bootloader crashes/is stuck at downloading the image.
"fastboot devices" works, showing my device, but "adb devices" does not show it.
What can I do to flash the stock ROM?
Alright, I started a few things and probably fcked up.
The phone now only shows the following:
phone symbol ---- !(yellow triangle with exclamation mark) ---- PC symbol
I tried doing the OMAP Flash, but I think that did not work, as it still only shows those symbols.
Is there anything I can do now?
I don't know if this will help since I've never got that before but I recalled somebody having the same problem as yours and said this guide fixes it, I bookmarked it just in case, since I'm ultra-paranoid about soft-brick like these: http://forum.xda-developers.com/showthread.php?t=1528139&highlight=unbrick+your+nexus
Related
So, it's been a fun couple of days.
I was 'tabling' away, as usual, and my tablet suddenly reboots (if it matters, I was just opening FPSE, as I'd done dozens of times before; Skype was on background; every other process was finished). 'Ok', I thought, 'that's weird'. When the tablet's done rebooting, the lockscreen shows up, and when I try to unlock it, the scren just freezes. Couldn't turn off the screen, nothing. So, I force a shutdown by pressing the power button.
When I try to turn it on again, it just stays stuck at the Google logo screen. I tried going in through recovery, but the result is the same. Select recovery, Google logo shows up, little android with exclamation point doesn't.
I tried formating through fastboot -w, but the process just keeps endlessly deleting, while doing nothing at all. I have to quit command line, shut down tablet or unplug the USB cable with a command line message showing up (I once left it while I went for a coffee; two hours of deleting nothing at all). Same thing with trying to unlock bootloader to maybe going to recovery after flahsing a custom recovery.
I don't mind losing everything I had. All pictures are recuperable and the rest is either in the cloud or in my phone/PC. The most annoying thing would be to set up the whole thing again, wich is no trouble at all (that and going through PvZ2 and TD Bloons 5 from the start :crying: ).
I was using Android 4.4 (KRT16S), everything stock.
Is it bricked, soft-bricked, did the aliens get it? I am e-mailing with someone from the store I bought it from, hoping for a solution or (worst case scenario) RMA, but I would rather solve this without having to.
Try flashing system.img, recovery.img, and boot.img, by hand.
Your emmc likely got corrupted
How do I do that with a locked bootloader and no access to recovery? Is it possible?
Hi! Yesterday I rooted my Kindle Fire HD 8.9 with no problems. The problems came after I installed TWRP before installing Cyanogenmod and GApps. Long story short, I got those on there eventually, and when I rebooted my Kindle, it showed the Cyanogenmod splashscreen/ animation, so I thought everything went well. After about, probably, 8 minutes it flashed the Android lock screen, but that's it. So I turned it off, then on again. Now, when I turn it on, first it shows the regular "Kindle Fire" logo with "Fire" being in orange, and then changing to blue, then it just loops showing the Cyanogenmod animation, then flashing the Android lock screen for a split second, then repeating that from the Cyanogenmod animation. I can't get into TWRP when I press the volume up key IMMEDIATELY after I turn the Kindle on. But, I can get it into Fastboot mode, except anytime I do a command, it'll either say "error: device not found", or something like, or it'll say "List of devices connected" followed by the serial number, and next to that "offline". If anyone could help me with this, it would be GREATLY appreciated.
Or, is there a way to completely reset it? At this point, I honestly don't care if I end up with the Amazon OS again, I just want my Kindle back
Anything? I just want to be able to use my Kindle again... At this point I'd rather it have a full factory reset, and just start fresh, as if none of this happened, and leave it that way... :crying:
Fleetwood Mac & Cheese said:
Hi! Yesterday I rooted my Kindle Fire HD 8.9 with no problems. The problems came after I installed TWRP before installing Cyanogenmod and GApps. Long story short, I got those on there eventually, and when I rebooted my Kindle, it showed the Cyanogenmod splashscreen/ animation, so I thought everything went well. After about, probably, 8 minutes it flashed the Android lock screen, but that's it. So I turned it off, then on again. Now, when I turn it on, first it shows the regular "Kindle Fire" logo with "Fire" being in orange, and then changing to blue, then it just loops showing the Cyanogenmod animation, then flashing the Android lock screen for a split second, then repeating that from the Cyanogenmod animation. I can't get into TWRP when I press the volume up key IMMEDIATELY after I turn the Kindle on. But, I can get it into Fastboot mode, except anytime I do a command, it'll either say "error: device not found", or something like, or it'll say "List of devices connected" followed by the serial number, and next to that "offline". If anyone could help me with this, it would be GREATLY appreciated.
Click to expand...
Click to collapse
Are you taking care to include the "-i 0x1949" parameter in your fastboot commands? That's one of the things I would think is preventing the kindle from being recognized. Also, try downloading and installing the Kindle ADB drivers.
monster1612 said:
Are you taking care to include the "-i 0x1949" parameter in your fastboot commands? That's one of the things I would think is preventing the kindle from being recognized. Also, try downloading and installing the Kindle ADB drivers.
Click to expand...
Click to collapse
Thank you! I eventually got it fixed. Now it's just looping the regular "Kindle Fire" logo in orange :/ but I'm working on getting it back to normal.
Hello,
I seem to have really messed up my G3 and after days of research I have not been able to get anywhere with it. I've read posts of people having similar issues, but their solutions do not seem to work for me.
What I tried to do is flash the ROM, starting with TWRP. After installing TWRP and rebooting I was getting the "no command" message on the screen. I believe (this was days ago), I used ADB to remove laf and reboot the phone (for some reason I could not back it up). The phone rebooted in fastboot and it has been downhill from there.
No download mode. When normally started the phone just hangs on the LG logo. Vol- and power gets me to the "Factory data reset", but if I do that, it flashes "erasing" for a second and it goes back to the LG logo screen.
I can get to fastboot, however, any command that I enter in CMD or Linux terminal just shows up on the phone's screen and it does not do anything. Fastboot devices shows the device as "????????" in Linux and as "?" in Windows. I have tried multiple drivers for Windows.
I tried BoardDiag (3 or 4 different versions running as admin) and shorting the pins, but any time I try to run the checks, I get an error - "No response from device" or "Device was not found in dload trying flash programmer"
I also tried SmartBootDiag, but once it detects the phone, it does its checks and it disconnects the device, without giving me an option to flash anything. Looking at the logs, it does not find any anti-rollback issues.
Any suggestions would be greatly appreciated as I am not sure what else to try.......
Thank you.
Anyone??
Hey everyone,
I did something really stupid while trying to get a certain app to recognize a codec that it needed in order for it to work and seem to have probably bricked my phone.
Phone Details:
LGH812
Lollipop 5.0.1
rooted
I went to /system/ and renamed lib64 to lib64bak because I wanted to put some new files in there. This caused the phone screen to immediately go black and unresponsive. I took out the battery and re-inserted it. The phone boot logo with LG comes up and then it goes to a black screen with the dead android guy with red triangle and the exclamation mark. No other text is present in this screen. Stays at this screen for about a minute and reboots only to go back to the exact same screen.
Things I have tried:
1.) I tried to boot into download mode (power+volume down) still goes to the aforementioned screen.
2.) Got LGUP to recognize the com port once, but it shows up as unknown and won't let me proceed with a fresh wipe/install
3.) Tried the LG Flashing tool, couldn't even see the com port.
4.) Tried the WHQL universal drivers as well as the specific device drivers with no advancement.
What I believe is happening is that it's trying to boot properly initially, but it can't find lib64 folder so it fails to launch the os and then tries to go into recovery due to error, but fails to go to recovery also because of lib64 is missing.
If anyone has any ideas/things I can try to get it into recovery or download mode or if anyone has seen this state before and was able to fix it please let me know.
Thank you all for your time!
Everytime i try to boot my phone its shows a warning symbol and the following text "This phone has been unlocked and it can't be trusted your device will boot in 5 seconds" or something like that, now this is normal for my phone as it just skips it and boots normally but this time something unexpected happened. After the that another text appears saying " Your device has been unlocked and the boot image isn't working" and it just keeps repeating those 2 stages.
Things that might be important to mention
-I had an sd card on it until i bought a new phone and removed it
-I have installed TWRP in the phone (pretty sure its gone by now)
-And it cant charge because it tries to boot when it can't so it just repeats these stages until it powers off.
How do i make it boot into the system?
Now ,after 6 hours, it cant even go to the first stage with the "device can't be trusted" it just sits with its orange light and consumes power, nothing else.
Try to flash stock rom, maybe you install the wrong rom version