Have TWRP 2.6.0.0 and Flashed EOS -wingray 205 and gapps through TWRP now tablet boots to the Dual Core screen and just sits there. Any help would be great. Was trying to get back into the TWRP but without getting into the tablet I do not know how. Thanks
EOS -wingray 205 doesn't work. Same with EOS -wingray 204. bigrushdog doesn't have access to EOS's goo.im account and can't delete the builds. EOS -wingray 203 was the last working build. To get into recovery press Power + Volume Up, wait 3 seconds after Dual Core Screen appears, press volume down, press volume up, and you should be in TWRP.
Related
Hi, I tryed to flash Slim Bean + Marmite Kernel to my phone and after it was all installed my phone hasn't worked. When the phone is turned on I can see Google than the screen will go black and stay that way with the touch buttons lighting up. I can get into Fastboot (bootloader) but at that menu I cannot move up or down with the volume keys but if I press the power button it will choose the first option which is Reboot Bootloader. The power button on my phone is broken and will only work if I press it hard a million times. Any ideas what I can do to fix my phone.
You might be flashing a wrong kernel version. Which version of slim ROM & Marmite kernel are you flashing?
Sent from my Nexus S
So I've been using CM10 nightlies for months without a problem, and today I installed the newest nightly. The phone now boots, showing the HTC screen, and then goes black. It is responsive to pushing the power button. but all that happens is the backlight turns on, but the screen is still blank. I've read about problems associated with the new 3.17 update, but to my knowledge I have not installed this update. So what can I do? I'm hoping just reverting to the previous nightly can solve this problem?
Hold the power button for about 30 seconds.. And everytime you hold the power button does it boot up to the HTC screen or does it go blank... It could be your LCD blunked out on you but I doubt it....
No, when I do this the HTC screen comes up and then it just goes to black. I don't get the CM spinny wheel or anything, but the screen is definitely still fine.
Hold volume down and power than get to bootloader
Hold volume down and power together while the phone is booting. The hardware keys will blink 5 times then the phone will go off. Let Go of volume down and power. Wait 5 seconds press volume down and power. It will go into bootloader. Select recovery, you'll be in recovery. Flash whatever, brick your phone as you can't read enough to figure out a: don't post twice and b: how to get into the bootloader of the phone you rooted. I'm shocked you got this far.
Sent from my One X using xda app-developers app
Thanks so much for being so helpful! I'm not an idiot. I've been installing these nightlies for months without a problem, and this just suddenly arose with the latest one. I tried flashing back to the older nightly, but now the phone boots and is just stuck on the spinning CM animation.
ul49 said:
Thanks so much for being so helpful! I'm not an idiot. I've been installing these nightlies for months without a problem, and this just suddenly arose with the latest one. I tried flashing back to the older nightly, but now the phone boots and is just stuck on the spinning CM animation.
Click to expand...
Click to collapse
If it gets stuck on the boot logo, then you probably need to manually flash the kernal which should be included in the roms zip/rar file.
Yep, reinstalling kernel and new nightly did the trick. And in the process I'm now running 4.2!
So I grabbed my old S3 to give to the wife to help entertain the new baby (ie making vacuum noises to he'll go the F to sleep). If I start to trail off or don't make sense, it's likely because I've got a 1 week old and I sleep in 45 minute intervals. Apologies in advance.
I was trying to move off my old CarbonROM to something a little more user friendly for the wife, and in doing so I've run into a snag. I downloaded the CM 12.1 nightly (already stupid, should have grabbed a stable 10.2), and probably the wrong GApps package (tk_gapps-modular-micro-5.1.1-20150620-signed) instead of the CM GApps. Upon booting, everything looks normal, gets to "Android is starting - optimizing app x of 97," counts up to all the apps, says "starting apps," then "finishing boot," then gives me a few colored lines at the top, reboots and starts the process all over again.
I tried booting to recovery (Volume Up + Home + Power), but no matter when I release the buttons (immediately when the quick Samsung logo comes up, when the CM "Galaxy SIII" logo comes up, or not at all), I can't get it to work. I've downloaded ODIN and tried booting to Download (Volume Down + Home + Power), and I get to the Continue/Cancel screen, but when I hit Volume Up to continue, it just vibrates and shuts off.
I've got a nandroid backup of the CarbonROM state that if I could get into recovery, I could restore. I've got the latest TWRP installed as well that the backup was made with. Just having a hell of a time trying to get back to it.
Thanks for any help and apologies if this is a very obvious fix
Its in perfect shape and I need to get it going for work. I have CM10.1 on it and stupidly did a factory reset on it Now im getting the AOSP keyboard error and cant input anything. I tried to get it into the recovery by doing power and the down button but it just sits at starting fast boot support and Motorola logo.
Can you help me save her?
Anyone Please???
Power off + volume up to restart.
Touch nothing, when logo appear wait 3 sec. and push volume down to see recovery mod and push volume up
Thanks Pots I got into recovery, Any idea how I overcome the no keyboard issue
Reinstalled CM10 and keyboard issue is fixed, I dont have a copy of Gaps for this rom. is there one still available ?/ Im close to saving her
Here: https://www.dropbox.com/s/n8rcdjkng8g5xq6/gapps-jb-20130413-EOS-XOOM-ONLY.zip?dl=0
Working on EOS and Cyanogenmod 10
Dude you Rock!! Donation on the way.
I have a Verizon LG-VK410 GPad 7.0 LTE. It is currently running Android version 5.0.2. I have rooted, but am not able to boot into recovery mode to install a custom rom(like one from CM). I have tried using the power button with volume down, release power button while still holding volume down when LG logo appears for a few seconds then hold volume down, up, and power button at same time combination. Sorry for the run on sentence! Multiple times and different combinations. I have tried using the following apps: Flashify, Quick Boot, Reboot. All of which failed! So I guess the next question is, am I stuck with Lollipop? Or can I put a custom rom of Marshmallow from CM? I am stunned.....I am really grateful for this site, and the people who take time to help people like me!!! Very awesome in todays world! Thank you XDA!
I was wondering the same thing. I rooted my VK410 using KingRoot, with no issues. Then I'd flash a new ROM, but it never took. After the reboot, it would go right back to the current OS.