I'm trying to install CM11 to my Ouya. ADB recognizes it as a device but when I "adb reboot boot loader" the device reboots, screen goes black for several minutes and then it just boots right to Ouya OS.
I had the device rooted a while back and I think CWM was installed. I did a factory reset though a few months ago. Could I have bricked this thing?
I have also tried a usb keyboard and hitting alt+print+i but get the same result.
christanya99 said:
I'm trying to install CM11 to my Ouya. ADB recognizes it as a device but when I "adb reboot boot loader" the device reboots, screen goes black for several minutes and then it just boots right to Ouya OS.
I had the device rooted a while back and I think CWM was installed. I did a factory reset though a few months ago. Could I have bricked this thing?
I have also tried a usb keyboard and hitting alt+print+i but get the same result.
Click to expand...
Click to collapse
I had similar issues a rooted ouya with CWM Recovery on but I could not boot into recovery, I got the black screen and if I hit the home key I just got the standard android recovery not CWM. I read that this could be due to an OUYA update. As hard as I tried I could not reload CWM. I finally fixed my issue by reloading Superuser. For some reason I was then able to run one click recovery and it reloaded CWM Recovery for me. Since then I have upgraded recovery and loaded CM11. Only issue I have is now I don't get the boot menu just straight to CM11.
I am just a user not a programmer but I believe the issue may be that your recovery was overwritten by the ouya update and then you are unable to load CWM because permission issues.
Try hitting the home key when you have the blank screen, if you get Andriod Recovery then you seem to be where I was.
Good Luck.
newbyp said:
I had similar issues a rooted ouya with CWM Recovery on but I could not boot into recovery, I got the black screen and if I hit the home key I just got the standard android recovery not CWM. I read that this could be due to an OUYA update. As hard as I tried I could not reload CWM. I finally fixed my issue by reloading Superuser. For some reason I was then able to run one click recovery and it reloaded CWM Recovery for me. Since then I have upgraded recovery and loaded CM11. Only issue I have is now I don't get the boot menu just straight to CM11.
I am just a user not a programmer but I believe the issue may be that your recovery was overwritten by the ouya update and then you are unable to load CWM because permission issues.
Try hitting the home key when you have the blank screen, if you get Andriod Recovery then you seem to be where I was.
Good Luck.
Click to expand...
Click to collapse
Thanks for the advice.
I managed to make it into stock recovery but can't seem to get to CWM still. I reloaded Superusuer and the tried Oneclickrecovery. ADB shows success and say's I should be in CWM but I just get a blank screen.
Related
hey guys, i've just flashed CyanogenMod 7.0.3 to my device and the wifi turns on, can see wifi networks and accepts my WEP password, however hangs at "Obtaining IP address...", eventually disconnecting and trying all over again.
I was previously running the 7.0 release with no problems and in my newb naivety i failed make a backup of the ROM.
Any suggestions?
EDIT: Now i cant boot into recovery. I just get the bootloader screen (i think? the white one with the skateboarding Androids at the bottom?) and selecting Recovery just sends me back there. This has now gone from an expected easy fix to something thats starting to get me worried. Can anyone help?
Do a full wipe and re-install the rom again, chances are something corrupted the 1st install which does happen apparently.Don't worry too much mate, over the past 2 weeks ive installed and re-installed about a dozen times and on a few occasions been in exactly the same spot your in.
thanks, but no can do. I cant boot into recovery and thus cant wipe and re-install...
Dumb question, you are holding down the volume(down) and power button at the same time to get into recovery mode??
Wow that's weird, try going into ROM Manager and flashing a different version of Recovery.
thanks for the responses guys. Yeah im doing the vol down + power to get to recovery. I cant get further than the white skateboarding Android screen. ROM manager doesnt let me flash new recovery versions because there aren't any.
You can flash a older recovery, scroll to the bottom when in RomManager and select All ClockworkMod Recoveries and try to flash something like 3.0.0.6
Sent from my Desire HD using Tapatalk
yeah when i do that i get "No legacy recoveries found"
EDIT: i turned on my mobile data and now i can choose older recoveries from ROM manager but i still cant boot there regardless of which one i choose
PS can a mod change the title of the thread cos i realize now my problem is more to do with booting into recovery rather than the wifi issues. Thanks
reading around it seems like i need to use fastboot to reflash the recovery.img from my computer. will try it tonight
Good Morning All -
A few days ago, I dualbooted my N7 with Ubuntu. The installation went fine and the tablet was working with no issues over the last several days. Last night, I was using the tablet and set it down. I went to pick it up (roughly 5 minutes later) and the touch screen was unresponsive. I was at the lock screen but couldn't get it to unlock. I pushed the wrong key-combo first and the device took a screen shot.
I was able to reboot into fastboot and attempted to go to recovery. The device would just hang at the Google logo. I pushed a factory firmware update from my Ubuntu system and attempted to reset -- no joy. This morning, I used Nexus Root Toolkit from my Windows 8 machine to see if I could get it up. Root Tool kit worked fine, pushed the images over again and restarted but it continues to hang at the Google logo.
Looking for any other advice folks may have on getting the device to boot.
EDIT: I can get to the bootloader fine and the computer recognizes it.
Thanks!
Alright... I just attempted using NRT and flashing 4.4.2 instead of 4.4.3 to see if it would run through. No joy, again. Remains on the Google screen.
xbi0s said:
Alright... I just attempted using NRT and flashing 4.4.2 instead of 4.4.3 to see if it would run through. No joy, again. Remains on the Google screen.
Click to expand...
Click to collapse
Im having the same problem with an unlocked unit. I would bet if you tried to do a factory reset in the android recovery menu it would give you a huge error all having to do with cache.
antonio824 said:
Im having the same problem with an unlocked unit. I would bet if you tried to do a factory reset in the android recovery menu it would give you a huge error all having to do with cache.
Click to expand...
Click to collapse
I'm unable to get into the restore menu. Hangs at the Google logo when attempting to get there.
I've tried about any solution I could find... Bumping one last time before I torch the unit :\
Nothing can be done. Its something inside. If its the 2013 model, call and get it rma'd. Sorry man.
Sent from my LG-LS970 using XDA Premium HD app
Resurrecting this thread to keep a work log.
I made have made some progress but hitting another roadblock. I've been holed up at home due to an auto accident so I started tinkering with the N7 2013 again.
Using the Nexus Root Toolkit, I am able to launch "Boot Temporary - Custom Recovery" from the advanced options. The problem I now run into is TWRP's touchscreen will not work. I attempted to do volume up/down to see if I could select but it wouldn't. The software is not frozen as I can see the temperature changing.
Anyone have any thoughts or information on how to boot another custom recovery that uses button inputs? I appreciate any input.
Updates:
1. I was able to push TWRP via "fastboot flash recovery." It went to the Google Logo then loaded TeamWin screen. I started to see errors when the program launched. "Unable to mount..." multiple times then the device rebooted. Device stuck on the Google screen.
2. Shut the device down, booted back into Fastboot. Selected Recovery and it began loading again. This time, the app launched and worked. Touchscreen does not work but the CPU temp is fluctuating and minutes tick up.
Update 4:49PM Central:
1. I am able to install and boot into TWRP 2.8.0.1 through TWRP 2.7.1.1. Those versions load but of course touch screen does not work.
2. I have been unable to get CWM to load... It installs fine but I cannot boot into.
3. The factory recovery images also do not load.
I mistakingly...( at 3AM!) installed the Rbox boot menu. It was not intentional....just late at night and I hit the wrong button! In any case I am now stuck in a loop the boots to the Rbox boot menu with 2 options....load kernal or boot to recovery. Load kernal just reboots to the same menu screen and boot to recovery gives me a failed update message after which in several minutes the unit boots back to the original Rbox boot menu. This particular unit had been previously rooted, updates blocked and loaded. The bootloader was unlocked with the FTV utility and that's when I hit the wrong button and loaded the Rbox boot menu.
I have tried connecting to the internet directly....( my router blocks updates) with no success. Is there anyway to get out of this even if it means updating and losing root or do I now have an extra boat anchor on my hands?
Any help would be greatly appreciated!
fxbill said:
I mistakingly...( at 3AM!) installed the Rbox boot menu. It was not intentional....just late at night and I hit the wrong button! In any case I am now stuck in a loop the boots to the Rbox boot menu with 2 options....load kernal or boot to recovery. Load kernal just reboots to the same menu screen and boot to recovery gives me a failed update message after which in several minutes the unit boots back to the original Rbox boot menu. This particular unit had been previously rooted, updates blocked and loaded. The bootloader was unlocked with the FTV utility and that's when I hit the wrong button and loaded the Rbox boot menu.
I have tried connecting to the internet directly....( my router blocks updates) with no success. Is there anyway to get out of this even if it means updating and losing root or do I now have an extra boat anchor on my hands?
Any help would be greatly appreciated!
Click to expand...
Click to collapse
Have you tried connecting a usb keyboard and entering the keyboard command: Alt + i + PrntScreen
You have to enter all three keys at once and repeat as many times as it takes for the screen to maybe boot in clockworkod.
TROJAN4EVR said:
Have you tried connecting a usb keyboard and entering the keyboard command: Alt + i + PrntScreen
You have to enter all three keys at once and repeat as many times as it takes for the screen to maybe boot in clockworkod.
Click to expand...
Click to collapse
Hi,
Yes.... I stumbled across that today on searching. I tried with a little iPazzport usb keyboard/mouse that I use to program with, but I'm going to try another keyboard as well just in case it is the keyboard. I tried at least 20 times over and over again with nothing at all happening. I appreciate the suggestion though and will try again with the different keyboard tomorrow. I'm a little burned out on it tonight! I'm afraid what I might have done is to change from the CWM bootloader to that one when I did it. Hopefully not, but there's no way to tell since all I can get now is the loop when I boot the unit up. I tried not only when I got the failed update message, but at all different times during the boot operation just to see if i got any response at all, but nothing so far seems to break into that cycle.
Thank you!
fxbill,
Sometimes you just have to walk away and then get back to it later. I use a low cost dell usb keyboard and what I found out is that you have to do press all three keys at once in unison and at a steady rate until you get a response. Just try to press all three at once and I guarantee you'll get it done. Try it when you're ready to get back to it. Have a good night!!!
fxbill said:
I mistakingly...( at 3AM!) installed the Rbox boot menu. It was not intentional....just late at night and I hit the wrong button! In any case I am now stuck in a loop the boots to the Rbox boot menu with 2 options....load kernal or boot to recovery. Load kernal just reboots to the same menu screen and boot to recovery gives me a failed update message after which in several minutes the unit boots back to the original Rbox boot menu. This particular unit had been previously rooted, updates blocked and loaded. The bootloader was unlocked with the FTV utility and that's when I hit the wrong button and loaded the Rbox boot menu.
I have tried connecting to the internet directly....( my router blocks updates) with no success. Is there anyway to get out of this even if it means updating and losing root or do I now have an extra boat anchor on my hands?
Any help would be greatly appreciated!
Click to expand...
Click to collapse
If you get failed update when selecting recovery that means you didn't install CWM. If you did a full unlock, you can use fastboot to boot into CWM. If you didn't do a full unlock, then you're pretty much screwed.
rbox said:
If you get failed update when selecting recovery that means you didn't install CWM. If you did a full unlock, you can use fastboot to boot into CWM. If you didn't do a full unlock, then you're pretty much screwed.
Click to expand...
Click to collapse
Well.... CWM was in.... I got the install from zip screen, but at that late hour and as tired as I was it's possible that I somehow removed it when installing your boot program. If so then I can live with it and yet I will try again tomorrow to see if I can fast boot or use a different keyboard for trying to alt/pnt scrn/i and see if that works.
I did do another unit tonight and installed your boot program before installing CWM,,,,again in error, but this time it booted to the same screen and then rebooted back into the preloaded unit! I then installed CWM and everything else went smoothly. I'm assuming your program is still in there, but is there a way to verify that it's still there? I updated to the newer 4.0 firmware with no issues and Netflix is again working and the firmware shows 4.0 installed. Is there really any reason to update any father than that? Is there anything new in the latest rooted firmware that justifies updating any more than I already have? If not I'll leave it as is...everything works extremely well at present.
Thanks so much for the advice and help!
@fxbill, so were you able finally to get this fixed? i'm in same situation when my device constantly reboots after counting down to 0 in rboxes menu . tomorrow i will by trying to find an USB keyboard and see whether im in luck of getting to recovery. hopefuly that works. i'll keep you posted.
I was on stock F240L20D, 4.4.2 Kitkat, rooted, PhilZ Touch 6 installed. I've tried some ROMs before but reverted back to this one. So, basically, I've been to the recovery several times, but only used the ADB method to access it, and I've made several backups too.
However, one thing that happened today has frustrated me completely. Long story short, I thought about making a backup again, although this time, I used the power keys to get to the recovery instead of the ADB method, backup completes successfully, nothing wrong just yet, but just as I tap on 'Reboot System Now', it boots back in to recovery.
I've tried everything, tried using all the ADB commands, even going through all the options in the recovery, but it always seems to boot back in to the recovery. Really can't figure out what's happening. Any help would be extremely appreciated.
UPDATE: So I've flashed a KDZ, the Lollipop one using the LG Flash Tool. It's taking a bit too long to start, currently stuck at the U+ Lte logo. I hope it gets fixed.
UPDATE 2: It says Android is upgrading, YES YES!!!!! This is so exciting, but I'm still not convinced.
With most of cwm version after 6.4.7, any time you use power + volume up to access the recovery, you will get the boot loop. Go here and down load the zip file from the first post. Flash the zip and you should be go to go.
http://forum.xda-developers.com/showthread.php?t=2619403
Hello guys,
Thank you for reading, any help is appreciated.
My device was running the latest release of CM13 (cm-13.0-20160418-SNAPSHOT-ZNH0EAO2NK-serrano3gxx) and TWRP v3.0.2-1
So yesterday afternoon my phone randomly shutdown and I was unable to get it turned back on until this morning.
However though when i did manage to get it powered on after hours of failed tries it was stuck on the Samsung boot screen.
I've since tried to access the TWRP Recovery (Pwr + Vol Up + Home) but it sticks on the TWRP slash screen and then attempts to reboot normally (which as i said stick on the Samsung boot screen).
I also tried re-installing TWRP via Odin and it appears to be installing properly and successfully but when i attempt to access TWRP it again sticks on the splash screen,
I've also tried installing CWM Record via odin and that also appears to be installing properly and successfully but when I attempt to access the recovery I am yet again greeted with the TWRP Slash Screen which has lead me to believe something is going wrong.
Any ideas or suggestions as to what may be going on here ?
Thanks in advance, any help is appreciated.
Hey again guys,
I have tried installing stock rom via Odin, It says Pass but nothing at all seems to be changing.
I'm beginning to think Odin may really not be working at all or something is wrong with the phone
Update: I tried flashing TWRP recovery via Heimdall and it appears to have completed successfully saying "RECOVERY upload successful" but when i reboot immediately after into Recovery mode it still sticks at the TWRP 3.0.0-0 Splash Screen then attempts to reboot normally which as mentioned earlier also sticks on samsung slash screen