Database Users

[Q] Nexus 4 updated to Kit Kat via OTA and got looped on boot

Hi, this is my first post here. I'm new into Android and I've always updated my Nexus 4 when the system prompts me to do it. Today, I got the notification to update from 4.3 to 4.4... I did it and restarted my phone. Then I got (and have been) stuck on the boot sequence after the Google logo. The thing is that I've tried to wipe and restart the phone by Bootloader (I don't know if I lost all of my files) and didn't work out. So now I'm trying with Nexus Root Toolkit but I don't know if that will work. I'm really needing some help, here in Venezuela not so many people have this cellphone and I really don't know how to proceed. I'm upset with Google for these kind of fails, my phone was working 100% good. Please help me! Sorry if my english is not so perfect.

I did experience the same.
Never rooted or unlocked bootloader & I was patiently waiting for OTA. It came and it was the worst thing to happen! Infinite bootloop!
I waited 2 hours, before I restarted the phone, but in vain. No use!
I never enabled debug settings, so i couldn't use ADB command and it wasn't recognizing my device!
Here is what worked for me:
1. Unlock bootloader (using fastboot command)
2. use fastboot to flash the factory image
3. I did remove (-w) wipe option, but still lost my data.
however image works, now phone is back to life!

Same case, nothing works.

I had the same problem, go stuck on a boot loop and then it just said 'no command' or 'error' with an android lying down. Im a noob so i used ncry toolkit to reset it to factory 4.3 and then i upgraded to 4.4 again and all worked fine. Did lose data though, but i had it all backed up.

Do a clean flash of KitKat via fastboot.

Similar Situation
Chidvilas said:
I did experience the same.
Never rooted or unlocked bootloader & I was patiently waiting for OTA. It came and it was the worst thing to happen! Infinite bootloop!
I waited 2 hours, before I restarted the phone, but in vain. No use!
I never enabled debug settings, so i couldn't use ADB command and it wasn't recognizing my device!
Here is what worked for me:
1. Unlock bootloader (using fastboot command)
2. use fastboot to flash the factory image
3. I did remove (-w) wipe option, but still lost my data.
however image works, now phone is back to life!
Click to expand...
Click to collapse
I'm in the same situation as most... Sadly I updated via the OTA distro that was released a few days ago. I looked into rooting options and I got the "go ahead" from a thread somewhere, saying it is a minor update. Knowing how easy it was to restore root priveliges when I upgraded from 4.2 to 4.3, I trusted their encouragement and installed the update. Then, like everyone else, I got stuck in the bootloop at the "circles" screen.
As a last resort, I tried to factory reset to no avail. I cleared the dalvik cache and wiped the cache partition a few times... Then I tried restoring it to factory defaults, again! Same results every time. Unfortunately, because of where it gets hung up, I can't seem to get my computer to talk to it. I certainly can't access the SD Card to do any backing up, but can look at the contents through CWM recovery mode (v6.0.2.3).
It's been awhile since I last was active in flashing my phone, so while I no longer consider myself a noob, I am definitely back to being a beginner. The fastboot commands don't seem to work, as I get stuck at "<waiting for device>". Does anyone know if there is a way to force it into a drive mode? Any additional help with this matter would be greatly appreciated, as currently it seems Google has bricked my phone!
Last question, it looks like it may be possible to force a mount through CWM; is that true using the "mounts and storage" menu? I spoke to Google briefly and they were of no help (they just told me to call LG). I'm going to try going into the T-Mobile store and seeing what they will say, but I'm not holding my breath for them to come up with a solution; I'm relying on the community to help me out!
STATS:
Bootloader: MAKOZ20i
HW Version: rev_11
Secure Boot: enabled
Lock State: unlocked
CWM: v6.0.2.3
Computer OS: Linux-Ubuntu 13.4
---------- Post added at 03:48 PM ---------- Previous post was at 03:39 PM ----------
NissanskylineN1 said:
Do a clean flash of KitKat via fastboot.
Click to expand...
Click to collapse
Sorry to sound so dumb, but can you point me in the right direction to find instructions on how to do that with Linux?

http://forum.xda-developers.com/showthread.php?t=2302780
Its actually way easier to set it up on Linux than on windows.
Edit: java jdk6 was giving me issues on install so I used openjdk instead and it works perfect.
Edit: (last one, I promise), I don't know how new you are to Linux but if you are super new, anytime that guide mentions "code" in a box, copy and paste one line at a time into the terminal. Leave out the dollar signs when copying.
AMarted said:
I'm in the same situation as most... Sadly I updated via the OTA distro that was released a few days ago. I looked into rooting options and I got the "go ahead" from a thread somewhere, saying it is a minor update. Knowing how easy it was to restore root priveliges when I upgraded from 4.2 to 4.3, I trusted their encouragement and installed the update. Then, like everyone else, I got stuck in the bootloop at the "circles" screen.
As a last resort, I tried to factory reset to no avail. I cleared the dalvik cache and wiped the cache partition a few times... Then I tried restoring it to factory defaults, again! Same results every time. Unfortunately, because of where it gets hung up, I can't seem to get my computer to talk to it. I certainly can't access the SD Card to do any backing up, but can look at the contents through CWM recovery mode (v6.0.2.3).
It's been awhile since I last was active in flashing my phone, so while I no longer consider myself a noob, I am definitely back to being a beginner. The fastboot commands don't seem to work, as I get stuck at "<waiting for device>". Does anyone know if there is a way to force it into a drive mode? Any additional help with this matter would be greatly appreciated, as currently it seems Google has bricked my phone!
Last question, it looks like it may be possible to force a mount through CWM; is that true using the "mounts and storage" menu? I spoke to Google briefly and they were of no help (they just told me to call LG). I'm going to try going into the T-Mobile store and seeing what they will say, but I'm not holding my breath for them to come up with a solution; I'm relying on the community to help me out!
STATS:
Bootloader: MAKOZ20i
HW Version: rev_11
Secure Boot: enabled
Lock State: unlocked
CWM: v6.0.2.3
Computer OS: Linux-Ubuntu 13.4
---------- Post added at 03:48 PM ---------- Previous post was at 03:39 PM ----------
Sorry to sound so dumb, but can you point me in the right direction to find instructions on how to do that with Linux?
Click to expand...
Click to collapse

Stuck at blank screen after flashing CM13.1

Hey guys. About a week or three ago I saw nightlies started rolling out for the D802, and decided to try the third nightly that has been released. While flashing itself went fine, I'm having trouble with getting the ROM to boot. After the LG logo the phone enters a blank screen, and won't do anything at all. I can barely notice that the backlight stays on, and I noticed that during this bootloop or whatever this is, Windows Explorer spams over and over I need to format the disk before I can use it when the phone's plugged in. I've read from someone that I should flash the ROM and google apps simultaneously, thus I've added them to a flashing queue and wiped the Davik cache after the flashing.
At first I thought it might've been my recovery being out of date, since I was running TWRP v2.6.x.x before, so I flashed the most recent version I could find which was v.2.8.3.73.
Doing this however made no difference whatsoever, so I gave up at this point and decided to wait for a week or two for the developer to fix a potential issue on the ROMs end.
Now it's fast forward to two weeks later where I'm typing this post after trying to flash the most recent version of cm13 which was available for my phone (the D802).
The problem is I'm starting to run out of ideas to do, so I'm hoping somebody can hold my hand regarding this issue. I really like to try Marshmallow and it's really irritating it doesn't work.
Thanks in advance guys!

i yhink you need to install boostacks when you install boostacks for your varian. dont reboot into system, just go back to main menu. then reboot into recovery from recovery. then copy the rom. flash and gapps ...
i also ecoment blastagator twrp to prevent ecreen dmage
http://forum.xda-developers.com/lg-g2/development/boot-g2-hybrid-bootstacks-t3183219
http://forum.xda-developers.com/lg-g2/development/twrp-twrp-2-8-0-0-kernel-f2fs-tools-t2898705

Thank you!
I was having the same trouble with lineage OS 14.1 on my D802.
I always got a black screen after the logo of LG appeared.
luckily I could get to TWRP and push the alternative bootstack via "adb push (filelocation) /sdcard/"
Thanks a lot!

thc8 said:
Thank you!
I was having the same trouble with lineage OS 14.1 on my D802.
I always got a black screen after the logo of LG appeared.
luckily I could get to TWRP and push the alternative bootstack via "adb push (filelocation) /sdcard/"
Thanks a lot!
Click to expand...
Click to collapse
Newbie here - I'm having the same problem with my D800 after Lineage OS 14 flash via TWRP. Where do I get an 'alternative bootstack'?

Get bootstack from here!
Check this out: https://forum.xda-developers.com/lg-g2/development/lg-g2-bootstacks-t3173715

Where do I go to find how to fix my rooted S5 SMG900P (bricked)

Hi,
I'm new to XDA forums, and this is the first time that have ever tried rooting my phone. I got it in my head that I wanted to root my Samsung Galaxy S5 SW-G900P so that I could add a hot spot mod. I followed a few tutorials which helped me accomplish root. I then added TWRP and that went fine as well. Then I added a WiFi Tethering Mod (unlockHotspot-1.4-NE5-DEODEX.zip) via TWRP. I was asked to wipe Dalvik cache which is where I think the problem started. I think I did something and stopped the delete process. I can't recall. I turned on my phone with anticipation of being able to use Hotspot. The phone started to boot as normal; the Samsung logo with lines moving around it showed; the yellow 4g 3d animated graphics showed; then the main 4g graphic showed and stayed on my screen which is where it stayed and nothing after that. Just the 4g logo. So, I pulled the battery and started my phone in recovery mode which took me directly into the TWRP interface. I figured that I needed to reload the 6gig backup file that I created (through TWRP) in order to bring my phone back to life. I believe that I was given options to install the recovery file which (I don't remember them all) already had a few check marks added to the options. However, there were other options such as the System and Recovery boxes that were not checked, so I checked those boxes as well. I reinstalled from the recovery backup file and everything seemed to work fine until TWRP rebooted the phone and now I am stuck going through the recovery booting process again. Every time I turn on the phone, I get to the teamwin screen which blinks and blinks. Did I brick or soft-brick my phone? I'm newb to this and need a little help to get my phone working again. Also, am I in the right part of the XDA forum to ask questions? Help me Obi-Wan Kenobi, you're my only hope.

@Uclid
Soft brick.
Go to sammobile, find your stock firmware, uzip it, flash with Odin in download mode and your phone will wake up from her sleep
Sent from my XT1528 using XDA Labs

Thank you, thank you! I really appreciate the reply. I downloaded the firmware this morning and just loaded it to my phone. All good now. Now, to get that hotspot mod to work.

Good to see you got your phone back up and running......but if you flashed the firmware with odin, you will have lost root and overwritten TWRP.......
You'll need both back before you can flash that zip......
http://i.imgur.com/rVnFwJM.jpg

Nexus 10 stuck in boot animation even after wipe/sideload

I dug out my old Nexus 10 (mantaray/manta) to mess with it and firstly it booted up fine and I updated Android to 5.1.1 (system update). All was well. I was going to flash Pie onto it, so I booted to the bootloader and connected it and unlocked it via fastboot oem unlock. Ever since I did that it will not get passed the boot (colorful balls) screen. I can get back into the bootloader. Next I cleared the cache and then also did a factory reset, same issue. So I flashed the official 5.1.1 (LMY49J) image, and still have the same issue!
No clue how to get to some state where I can boot this thing. My end goal is to have Android Pie / vanilla on it. What should I do?
Edit: I think what I did was I flashed an update rather than the full OTA. I can't find it, so maybe someone can point me to it?

jsm11482 said:
I dug out my old Nexus 10 (mantaray/manta) to mess with it and firstly it booted up fine and I updated Android to 5.1.1 (system update). All was well. I was going to flash Pie onto it, so I booted to the bootloader and connected it and unlocked it via fastboot oem unlock. Ever since I did that it will not get passed the boot (colorful balls) screen. I can get back into the bootloader. Next I cleared the cache and then also did a factory reset, same issue. So I flashed the official 5.1.1 (LMY49J) image, and still have the same issue!
No clue how to get to some state where I can boot this thing. My end goal is to have Android Pie / vanilla on it. What should I do?
Edit: I think what I did was I flashed an update rather than the full OTA. I can't find it, so maybe someone can point me to it?
Click to expand...
Click to collapse
Mine does it aswell, but after like 20 min it boots up. I flash mine with the "Nexus Rool Toolkit" with the option "Flash Stock + Unroot", in your case i wull put the radio button on "Softbrick/Bootloop". Then follow the steps on the screen and then when it reboots the programm will tell you that you need to wait like 20 min. And then it should be up and running again

SM-P580 blackscreen problem

So tl;dr version - i was using my tablet, saw an update to magisk, installed it, now it boots to black screen while running sambones rom
[SM-P580] [BQK1] SaMBoNeS
TWRP 3.2.3.0 --> 3.3.1.0
longer story:
i was trying to get a game to run, it wasnt...and realized it has been a while for a restart, so i checked to see if anything needs to be updated and saw magisk needed an update. i didnt note what version it was before but it was a version or two earlier than what it was trying to install.
rebooted to blackscreen no samsung logo
have tried restarting a dozen times, booted to TWRP, tried to force normal system boot through the UI, nothing.
I tried installing a new kernal [SiriKernel], it made it to the samsung logo, waited 15 - 20 minutes and it never made it past. restored a backup using TWRP
updated TWRP to 3.3.1.0, still no luck.
i had this problem a long time ago, and cannot figure out how i fixed it....it may have fixed itself but it isnt this time. any advice would be appreciated. I am trying to avoid wiping and starting again if at all possible because the problem seems familiar. also trying to stick to a rom for use with adaptive storage. if i do have to wipe if that can be done on a newer stock OS that's fine as well but last time i messed with this tablet it wasnt