My Ouya has been configured with the bootmenu, and I had flashed cyanogen mod but I'm now stuck in a bootloop and the boot menu just says resolution mismatch before rebooting the ouya into another cyanogen mod logo bootloop. Any ideas what I could do?
Blazerx39 said:
My Ouya has been configured with the bootmenu, and I had flashed cyanogen mod but I'm now stuck in a bootloop and the boot menu just says resolution mismatch before rebooting the ouya into another cyanogen mod logo bootloop. Any ideas what I could do?
Click to expand...
Click to collapse
Do you have CWM recovery installed? If not, install the flashable zip through the failsafe recovery and try re-installing CM11. Make sure to get the latest release. And don't forget to do the factory reset wipe as you do with any other ROM. Re-flash the boot menu first after the reset then flash CM11, gapps etc.
If you have access to the custom bootmenu, select Recovery with the power button and wait 2 seconds... blah blah blah haha
Hope I helped... in some way!
Fixed
I had fixed my ouya and now have a stock rom with cwm recovery installed, the issue was the resolution was not set for my tv as it was a smaller tv but I hooked it up to someone else's tv and i got into cwm recovery and fixed it without issue.
Related
earlier, i managed to brick my defy by first deleting google talk and then using terminal emulator to push the google talk back in system apps.
after flashing a stock sbf through rsdlite, i got my phone working again. my problem started when i flashed another rom (followed instructions from pay's rom tutorial). i was able to flash the sbf file, then root using superoneclick, then install clockwork mod (downloaded the apk and installed manually). i rebooted after cmw install just to be sure and when rebooting to cm recovery only a blank screen shows. i was puzzled as on m original 2.51 rom before, the clockworkmod recovery screen shows up when i reboot in recovery. i tried installing other stock roms (nordic froyo), the problem still persists (blank screen). it also seems to have affected the standard recovery (volume down+power), after showing the exclamation mark with the android guy, no matter where i press on the screen nothing happens, whereas before pressing on the lower right hand screen brings up the menu. what did i screw up this time?
i needed cm recovery to work for i can't flash custom roms without it. any help would be much appreciated. thanks
I had the same problem with clockworkmod so I installed the 2nd init recovery http://forum.xda-developers.com/showthread.php?t=1032212 and used clockwork mod from its recovery menu.
I think the problem was caused by installing clockwork mod with USB debugging enabled.
namzuf9 said:
I had the same problem with clockworkmod so I installed the 2nd init recovery http://forum.xda-developers.com/showthread.php?t=1032212 and used clockwork mod from its recovery menu.
I think the problem was caused by installing clockwork mod with USB debugging enabled.
Click to expand...
Click to collapse
so should i try uninstalling clockworkmod and install again? this time un-enabled usb debugging?
what exactly is a 2nd init recovery?do i just flash this over the existing sbf?
sorry for the questions, am still a newbie when flashing defy.
to access stock recovery when the android appears press vol down + up at the same time, my touch screen didnt work in recovery before either
once you can access stock recovery wipe data/factory reset, and flash a new ROM fresh
I have tried 2-3 different Kernel 3.0 ICS roms. I get stuck in a boot loop. It reboots a few times from the recovery screen, then I get a second of the boot animation a few times before it reboots until it ultimately just sits on the boot animation screen.
The roms appear to install fine.
I have tried powering off and rebooting from recovery after rom install.
I do wipe. I have tried wiping davlik afterwards.
I have tried both recoveries.(Now stuck with clockwork )
I have tried doing it while charging and off the charger.
I can install CM7 roms just fine.
How exactly are you stuck on CWM? And which version of it? Also, what version of TWRP did you try?
I tried loading twrp back on, and I got into it once from the adb commands but I rebooted and it went right back into clockwork, haven't seen twrp since. I believe its version 5.1 or.2 of clockwork, and I tried installing rom from twrp 2.0(first time), didn't get a chance to try from 2.2 as I haven't been able to get back into twrp.
Use smirkits scripts to change your cwmr to twrp http://forum.xda-developers.com/showthread.php?t=1500935 you can have only 1 recovery 1 overwrites the other
Thepooch said:
Use smirkits scripts to change your cwmr to twrp http://forum.xda-developers.com/showthread.php?t=1500935 you can have only 1 recovery 1 overwrites the other
Click to expand...
Click to collapse
Would the recovery type be causing my issue with the cm9 roms causing my Kindle to go into a boot loop?
macpat83 said:
Would the recovery type be causing my issue with the cm9 roms causing my Kindle to go into a boot loop?
Click to expand...
Click to collapse
Shouldn't be causing a boot loop, but a dangerous version of CWMR was released a while back which causes permanent damage.
EDIT: Also, if I remember correctly, older CWMR versions had problems installing ICS ROMs. This could be your issue.
most CM9 devs recommend using TWRP 2.1.x versions. So see if installing TWRP as the recovery makes it fine for you
Ok, so I have a question that either does not exist on Google or that I just don't know how to explain.
My Kindle Fire 2 was flashed a while back with a stock version of Android Jellybean 4.2.2, until today. I made a complete backup of everything inside TWRP and transferred all of those backup files to my laptop. I then flashed a newer version of TWRP, version 2.6.3.1. After that, i flashed the newest version of Cyanogenmod 11, Android 4.4.4.
Anyways, I got to adjusting the settings and told it to allow me to pick between rebooting into recovery or normal mode when i pressed the reboot button on the power menu.
Here is my problem though. At one point, I told Cyanogenmod to reboot me into recovery, and ever since, my Kindle will only let me boot into the TWRP recovery area, regardless of what I tell it to load in the bootloader.
How can I just get it to boot to the normal OS? I've tried reflashing the recovery and reflashing Cyanogenmod onto it. I just don't know what to do because I don't know exactly why this is happening.
I've tried wiping the /data partition too, but to no use. I still am able to wipe internal data partition, however I don't know how it will respond to that. I mean... Isn't that where TWRP is stored? I don't want to lose my recovery partition where I have no way to get back.
If it comes to it, could I replace my recovery partition with Cyanogenmod?
I am still able to use ADB and I'm able to push files. (So far)
Possible solution
mayuri1 said:
Ok, so I have a question that either does not exist on Google or that I just don't know how to explain.
My Kindle Fire 2 was flashed a while back with a stock version of Android Jellybean 4.2.2, until today. I made a complete backup of everything inside TWRP and transferred all of those backup files to my laptop. I then flashed a newer version of TWRP, version 2.6.3.1. After that, i flashed the newest version of Cyanogenmod 11, Android 4.4.4.
Anyways, I got to adjusting the settings and told it to allow me to pick between rebooting into recovery or normal mode when i pressed the reboot button on the power menu.
Here is my problem though. At one point, I told Cyanogenmod to reboot me into recovery, and ever since, my Kindle will only let me boot into the TWRP recovery area, regardless of what I tell it to load in the bootloader.
How can I just get it to boot to the normal OS? I've tried reflashing the recovery and reflashing Cyanogenmod onto it. I just don't know what to do because I don't know exactly why this is happening.
I've tried wiping the /data partition too, but to no use. I still am able to wipe internal data partition, however I don't know how it will respond to that. I mean... Isn't that where TWRP is stored? I don't want to lose my recovery partition where I have no way to get back.
If it comes to it, could I replace my recovery partition with Cyanogenmod?
I am still able to use ADB and I'm able to push files. (So far)
Click to expand...
Click to collapse
I assuming you have a TWRP bootloop problem? Like everytime you reboot it, it shows you the kindel fire logo (organge/white), then to the blue/white logo, and then instead of the normal android ui, it boots into TWRP? If this is the case, have you tried selecting the 'bootmode' option during the kindle fire blue/white logo screen? That was my solution when I had the recovery bootloop problem recently.
rocketfans14 said:
I assuming you have a TWRP bootloop problem? Like everytime you reboot it, it shows you the kindel fire logo (organge/white), then to the blue/white logo, and then instead of the normal android ui, it boots into TWRP? If this is the case, have you tried selecting the 'bootmode' option during the kindle fire blue/white logo screen? That was my solution when I had the recovery bootloop problem recently.
Click to expand...
Click to collapse
I tried telling it to boot normal during that screen. Still goes to TWRP.
Sent from my PantechP8010 using XDA Free mobile app
Hello there, I'm a bit new to this, but I wanted to try flashing a custom rom. I was using So I chose Carbonn 4.4.4 rom. Prior to that I installed doomslord CMW recovery 6.0.30 and did a backup of my Rom. Then I booted into recovery, wiped the data and flashed the carbonn Rom. Everything went fine, then I realized I hadn't flashed the gapps. So I rebooted my phone into recovery (Pressing the volume up button at the 'sony' logo). However it doesn't boot into recovery. The led light turns blue and it's stuck on the Sony logo. The only way to get out of it is the power down the device manually by pressing the power button and volume up button.
Rebooting into recovery only causes this problem. Otherwise it boots normally into the carbon Rom. How do I restore my backup? Since I can't boot into recovery?
kthsdm said:
Hello there, I'm a bit new to this, but I wanted to try flashing a custom rom. I was using So I chose Carbonn 4.4.4 rom. Prior to that I installed doomslord CMW recovery 6.0.30 and did a backup of my Rom. Then I booted into recovery, wiped the data and flashed the carbonn Rom. Everything went fine, then I realized I hadn't flashed the gapps. So I rebooted my phone into recovery (Pressing the volume up button at the 'sony' logo). However it doesn't boot into recovery. The led light turns blue and it's stuck on the Sony logo. The only way to get out of it is the power down the device manually by pressing the power button and volume up button.
Rebooting into recovery only causes this problem. Otherwise it boots normally into the carbon Rom. How do I restore my backup? Since I can't boot into recovery?
Click to expand...
Click to collapse
The latest Carbon ROM has recovery which doesn't work on Our phone. Follow the procedure here to flash a working recovery.
Tried that but cant seem to work. Besides it requires busy box to be installed which I cant seem to install. Any apk for that matter cant be installed. It shows "Cant open file"
kthsdm said:
Tried that but cant seem to work. Besides it requires busy box to be installed which I cant seem to install. Any apk for that matter cant be installed. It shows "Cant open file"
Click to expand...
Click to collapse
if You are on latest version of carbon, You wouldn't need to root as the ROM is pre rooted. Are You sure Your apk file are good? Because in any case, You must be able to install at least an apk file. Did You try messing with the ROM before?
Hi Team,
I am unable to boot into recovery mode. I just have installed OOS 3.5.2 rom through TWRP 3.0.2(1). I am able to boot up the device. Once I complete the setup process, I turned on Advanced options in developers and selected the boot in to recovery.
Device is restarting and then it is stuck at 1+ logo.
I have tried it through boot loader (Vol down and then power button) to start the recovery mode but is also showing 1+ logo and then device got turned off.
Any idea about the issue? Unable to restore backup.
I am completely stuck.
Plz help
Try booting into fastboot flash this version of Twrp
http://forum.xda-developers.com/showpost.php?p=68691560&postcount=56
Hopefully that will do it but you may need to boot into Twrp right away and reflash twrp-3.0.2-19-oneplus3.img from within Twrp and hopefully it will then stick.
It just worked like a charm.... :good:
3.5.2 Broke TWRP compatibility, there's a new unofficial TWRP available but I can't link to it at present. Although looking now it's in the last post.