Just wanting some advice (if any) to a white line issue I'm having with this tablet. I bought this tablet with Lollipop 5.0.1 already installed. I managed to get it downgraded, rooted, and currently have TWRP installed as well as CM12.1 nightly. The problem I have is that as soon as I install ANY custom recovery (TWRP or CWM recovery) it boots normally at first giving me the LG logo. Then, instead of getting the AT&T logo (or the CM custom boot animation), it gives me a series of white lines spamming from top to bottom of the screen. I know for a fact it has to be software related as when I return to stock KK everything boots fine, giving me the LG logo followed by the AT&T logo. I did NOT use the ADB method. Instead I downgraded using the LG Flash Tool, and a test KDZ file, which allowed me to install Flashify, then TWRP. My problem ONLY begins once I install ANY custom recovery. This process did not unlock my bootloader, however. Could this be my culprit, or would it be something else? Any help is greatly appreciated, and thanks in advance for any help/tips. More information is completely available upon request.
P.S. The white lines eventually disappear when the screen goes to sleep on it's own. I can then press the power button to wake the device which gives me the lock screen as normal. I just want to know if I can get the boot animation working. Everything else works fine.
You found cwm?
Related
Not sure if I've soft-bricked or full bricked my Asus TF300T, here's what happened, hope someone can help. I unlocked the bootloader with the Asus unlock tool back in July, didn't root my tablet though until this past month. Had no issues and was running the BAKED BlackBean 6 custom ROM. Then this past week, when Asus released a new update to the stock ROM, I decided to try and update that (since I had read on the forums here that the update really made the tab run smoother and it gave a major increase to the battery life). I flashed the stock ROM (10.4.2.18) through TWRP touch recovery but wasn't sure if I needed to also flash the 10.4.2.18 kernel also. When I went to reboot, TWRP recovery was saying that there was no OS so I decided to recover back to the backup of BlackBean 6 that I had made before I started this. During the reboot, it seemed to take forever for the OS to boot so I rebooted using volume down and power. Saw the Wipe Data option there and figured I should try that and then restore back to stock before trying everything again. Well, now I'm stuck at the very start of a reboot, with just the Asus logo showing in the middle of the screen and the line "This tablet is unlocked" at the top left-hand corner of the screen. Cannot boot into recovery, Fastboot or anything. Can someone please help me?
CaliTexan5 said:
Not sure if I've soft-bricked or full bricked my Asus TF300T, here's what happened, hope someone can help. I unlocked the bootloader with the Asus unlock tool back in July, didn't root my tablet though until this past month. Had no issues and was running the BAKED BlackBean 6 custom ROM. Then this past week, when Asus released a new update to the stock ROM, I decided to try and update that (since I had read on the forums here that the update really made the tab run smoother and it gave a major increase to the battery life). I flashed the stock ROM (10.4.2.18) through TWRP touch recovery but wasn't sure if I needed to also flash the 10.4.2.18 kernel also. When I went to reboot, TWRP recovery was saying that there was no OS so I decided to recover back to the backup of BlackBean 6 that I had made before I started this. During the reboot, it seemed to take forever for the OS to boot so I rebooted using volume down and power. Saw the Wipe Data option there and figured I should try that and then restore back to stock before trying everything again. Well, now I'm stuck at the very start of a reboot, with just the Asus logo showing in the middle of the screen and the line "This tablet is unlocked" at the top left-hand corner of the screen. Cannot boot into recovery, Fastboot or anything. Can someone please help me?
Click to expand...
Click to collapse
umm well maybe u can make a full factory reset, just download the last firmware from asus website and follow this:
http://forum.xda-developers.com/showthread.php?t=1777203
hope helps c:
The thing is, I cannot seem to access the option to go to recovery or USB. When I turn on using volume down and power, it doesn't give me anything other than the Asus logo in the middle of the screen and "the device is unlocked" at the top left corner.
CaliTexan5 said:
The thing is, I cannot seem to access the option to go to recovery or USB. When I turn on using volume down and power, it doesn't give me anything other than the Asus logo in the middle of the screen and "the device is unlocked" at the top left corner.
Click to expand...
Click to collapse
Maybe this link can help.
http://forum.xda-developers.com/showthread.php?t=2034866
Hey guys.
I'm new in the Android world and bought an LG G2 back in november.
I had originally intended to custom install cyanogenmod or KitKat 4.4 to replace stock rom, but I couldn't find a way to install a custom recovery, and was only able to root my device via Kingo Android Root.
A while later I saw an update that popped up, and not knowing any better I clicked install. It was about 114MB. That was about 3 days ago, and my LG G2 has been stuck in a bootloop ever since.
When I try to turn it on the LG logo shows up, then it says "secure booting error"and "Cause: boot certification verify" on the top left corner of the screen in white text.
I tried doing a hard reset, but that didn't work. I don't have a custom recovery so that I can clear the cache and data or something. So pretty much I have a bootlooped phone with no custom recovery, I can't do a hard reset, and it's Sprint and everything's new so it's harder to find a fix.
Does anyone here know of a way I can fix this? It would be much appreciated.
Thanks in advance
Hello guys.
I apologize for making yet another "my phone is soft-bricked" thread, but I have been through at least 20-25 of the other threads, seemingly tried everything, and I can't get past my problem. Also, most of the other threads I saw are pretty old and not really active anymore. A few of the tools there can't even be downloaded anymore because the links are dead.
Anyway, here's my story.
I have a 16 GB US retail XT1032 that I bought mostly to give tech support to my parents, whom I also bought a 8GB each. Theirs, I left untouched. Mine, I unlocked bootloader and rooted right away. All went well for a long time.
My parents kept receiving OTA's and it took them all the way to Lollipop. Me being rooted, I got stuck in KitKat somewhere (I'm not 100% sure whether that was in 4.4.2 or 4.4.4), but since it wasn't my daily driver, I let it lie as stock rooted KitKat. Recently I wanted to go to Lollipop in order to keep seeing "the same things" as my parents, and I installed TWRP in preparation to flash a "stock enhanced" version of Lollipop. TWRP flashed fine but there was something funny all along: I could use ADB or a root app to boot into recovery from the ROM, but I could never manage to get the phone to go into recovery by booting into fastboot (vol down+power) and then choosing recovery. Screen would go black and recovery would never load.
So I copied a "stock" Lollipop image and booted into TWRP from the ROM and wiped everything and tried flashing the Lollipop ROM. It got stuck somewhere part way, and a few hours later there was no more progress.
Ever since then, I am stuck in fastboot. Fastboot seemingly works correctly, recently I was able to flash an OG animation to get rid of the nasty "your bootloader is unlocked" warning. I can flash recoveries (TWRP and/or CWM) without error on the phone or the computer, but when I try to then boot into recovery using the bootloader, I get stuck on the black screen and go nowhere.
As others in the various threads have commented, when I try to boot "normally", I get the boot animation and a vibration and then it gets stuck.
I have tried so many things by reading different threads I couldn't tell you anymore what all of them were. I've gotten errors about downgrading, I've gotten stuck in fastboot reason: "failed flash", I've gotten flashing errors about the size of recovery or boot or gpt. What I've never managed to do again is to boot into anything other than bootloader. No recovery and no ROM.
Could someone with a bit of experience please point me to some working links and/or when you have the time, help me look at a couple of logs or something that can help me figure out where my problem lies and how to get out of it? my daily driver phablet died a gruesome death and I wanted to go back to my trusty moto g, to no avail.
Thank you very much to whomever can help.
Ruben.
Try to reflash full stock firmware for your device according to your bootloader version. Hope it helps....
Try typing in fastboot devices
Hi people, I have ran into a bit of an issue here that I have not found anywhere.
I wanted to try out CM12.1 + CAF Kernel for my Moto G XT1032, which was running Android 5.0.2. However, after install, I'm not able to boot into the OS or even recovery anymore. I get to fastboot, select either "Normal Powerup" or "Recovery", the phone gets to the "Bootloader Unlocked" warning, then shuts off without showing an animation or anything.
What can I do with this? I've been modding Android for some years now, but I have never ran into an issue like this. Thanks!
Ok, quick update. I got it to boot up on CM12.1, however, the recovery menu erased by itself. Reflashed it in order to get Gapps, rebooted, and now I'm back into the same issue.
What could it be?
Okay, so I was in the process of putting a custom ROM onto my LG G3s, however, as soon as I flashed in a custom recovery menu (TWRP) and rebooted my touch screen no longer works. The display screen itself is also darker and has "lines" in it, not really sure on how to describe it? I was using a version of TWRP that was "supposedly" supported on the G3s. My phone was running KitKat 4.3.2 I believe. . . With the G3s you have to do some kind of patch for the boot to be able to use a custom recovery without resetting the phone in the process, and I had done that. I know that was not the immediate cause of this problem for I used Flashify to flash the custom recovery. It worked all fine up until I rebooted the phone. I tried looking around, but didn't find anything that was even close to my problem. If someone could be of some help or provide some insight it would be much appreciated.