Went from CM 10.1 nightlies to try Smooth rom. Works fine but I noticed I have no Cyanoboot menu, it just loads to emmc fine. Pressing the n button just brings up the header "boot menu" but no selections are shown. Any ideas ?
sailerph said:
Went from CM 10.1 nightlies to try Smooth rom. Works fine but I noticed I have no Cyanoboot menu, it just loads to emmc fine. Pressing the n button just brings up the header "boot menu" but no selections are shown. Any ideas ?
Click to expand...
Click to collapse
If the Cyanoboot menu doesn't show any boots then you don't have altboots.
Yes, but all the boot options would be there. But greyed out.There is nothing below boot menu at all
Sent from my Barnes & Noble Nook Tablet using xda app-developers app
sailerph said:
Yes, but all the boot options would be there. But greyed out.There is nothing below boot menu at all
Sent from my Barnes & Noble Nook Tablet using xda app-developers app
Click to expand...
Click to collapse
I can't even find SmoothROM acclaim. You did get an acclaim version and not just a random one for a device, right?
datallboy said:
I can't even find SmoothROM acclaim. You did get an acclaim version and not just a random one for a device, right?
Click to expand...
Click to collapse
Liquidsmooth by Demetris, sorry for the vague info. I've since went back to stock and then flashed a cm nightly and all seems fine, but I did like that rom by Demetris. Thanks
Related
Hi guys,
I've tried flashing CM10 (fxp 134 and fxp 135), but after I give the command to reboot in the terminal, my phone just shows the fxp logo. Doesn't go in CWM recovery when I'm pushing te volume button. Anybody any idea why this is? Flashing CM9 works just fine.
Xperia neo, use the back key not volume down for recovery. What kernel are you using?
Sent from my MT15a using xda app-developers app
sdato001 said:
Xperia neo, use the back key not volume down for recovery. What kernel are you using?
Sent from my MT15a using xda app-developers app
Click to expand...
Click to collapse
I've always used the volume down for recovery, always worked. The wiki also says it's the volume down button. http://wiki.cyanogenmod.com/wiki/Sony_Ericsson_Xperia_Neo:_Full_Update_Guide
I just use the kernel from the package with the ROM.
I always use back key on neo, I use volume down in ray. Try using the back key and let me know the result
Sent from my MT15a using xda app-developers app
Lashkopivo said:
Hi guys,
I've tried flashing CM10 (fxp 134 and fxp 135), but after I give the command to reboot in the terminal, my phone just shows the fxp logo. Doesn't go in CWM recovery when I'm pushing te volume button. Anybody any idea why this is? Flashing CM9 works just fine.
Click to expand...
Click to collapse
Did you flash kernel for cm10?
Used the back key, and at first it didn't work (rebooting from computer), phone shut down again.
But then I put it back on and tried again, and it works, thanks guys!
Yeah, I flashed the kernel
However, I've got some problems with wifi now, which shouldn't be, I read in developers forum that wifi should work.
Also, CWM was kind of unstable. Screen went from left to right when I was navigating the menu.
Lashkopivo said:
Used the back key, and at first it didn't work (rebooting from computer), phone shut down again.
But then I put it back on and tried again, and it works, thanks guys!
Yeah, I flashed the kernel
However, I've got some problems with wifi now, which shouldn't be, I read in developers forum that wifi should work.
Also, CWM was kind of unstable. Screen went from left to right when I was navigating the menu.
Click to expand...
Click to collapse
That is a known UI bug for the recovery, it still works.
As for wifi, do a fresh install.
Flash rom
Flash gapps
factory reset clear cache etc
flash kernel
reboot
gregbradley said:
As for wifi, do a fresh install.
Flash rom
Flash gapps
factory reset clear cache etc
flash kernel
reboot
Click to expand...
Click to collapse
Did that, didn't help. There were a few other bugs too I didn't come across in the developers section (but I can't post there), for example google now was not working very well.
Flashed back to CM9 for now, but I will try again when the fxp136 is released
I liked JB a lot though.
So, I downloaded the necessary files too go from CM9 to CM10 via recovery in my nook tablet and I did a factory reset. From there, I flashed the cm10-acclaim-0.05.1-full-of-bugs.zip. After flash I fixed permissions, wiped Dalvik, took out my sd card and hit reboot. It boots into the universal bootloader, but that's about it...please help! I can't find a solution! Please and thank you so much!
kameronamurray said:
So, I downloaded the necessary files too go from CM9 to CM10 via recovery in my nook tablet and I did a factory reset. From there, I flashed the cm10-acclaim-0.05.1-full-of-bugs.zip. After flash I fixed permissions, wiped Dalvik, took out my sd card and hit reboot. It boots into the universal bootloader, but that's about it...please help! I can't find a solution! Please and thank you so much!
Click to expand...
Click to collapse
What recovery did you use to flash the rom? What version?
Sent from my Nook Tablet CM7 BETA using xda premium app
ShinnAsuka said:
What recovery did you use to flash the rom? What version?
Sent from my Nook Tablet CM7 BETA using xda premium app
Click to expand...
Click to collapse
I honestly couldn't tell you. I just know that when I boot into recovery, the n screen flashes, than a BIG n flashes then goes to the recovery screen. It's so confusing! Lol
kameronamurray said:
I honestly couldn't tell you. I just know that when I boot into recovery, the n screen flashes, than a BIG n flashes then goes to the recovery screen. It's so confusing! Lol
Click to expand...
Click to collapse
ok lets put it this way... in your recovery how do you navigate the menu? if you do it by the volume up, down and n button then you are using cwm.
if its all touch screen based then its twrp...
ShinnAsuka said:
ok lets put it this way... in your recovery how do you navigate the menu? if you do it by the volume up, down and n button then you are using cwm.
if its all touch screen based then its twrp...
Click to expand...
Click to collapse
Oh it's cwm for sure!
kameronamurray said:
Oh it's cwm for sure!
Click to expand...
Click to collapse
ok can you tell me what version of cwm you have? usually it shows it in the top left corner when you go into cwm.
ShinnAsuka said:
ok can you tell me what version of cwm you have? usually it shows it in the top left corner when you go into cwm.
Click to expand...
Click to collapse
I'm pretty sure it is 5.0.2.8 if I'm not mistaken. I tried to remember it but I'm away from it right now.
I was having reboot issues with that ROM. I ended up putting the original acclaim_update.zip file on a blank SD card, factory resetting it, then rerooting.
kameronamurray said:
I'm pretty sure it is 5.0.2.8 if I'm not mistaken. I tried to remember it but I'm away from it right now.
Click to expand...
Click to collapse
That's your.problem then. Flashing any rom with a 3.0+ kernel using that cwm will result in a bootloop. so eight now you need to flash a newer cwm and then try flashing cm10 again.
look in the dev section for a newer recovery.
Sent from my Nook Tablet CM7 BETA using xda premium app
ShinnAsuka said:
That's your.problem then. Flashing any rom with a 3.0+ kernel using that cwm will result in a bootloop. so eight now you need to flash a newer cwm and then try flashing cm10 again.
look in the dev section for a newer recovery.
Sent from my Nook Tablet CM7 BETA using xda premium app
Click to expand...
Click to collapse
You're a genius! Thank you so much!
As promised a while ago now we have an official twrp support from TeamRecovery.
All credits and hard work is due to those guys.
Am just here for the announcement and download links which i ask and got permission for.
So time for the main dish
Enjoy TWRP OFFICIAL!!!
Disclaimer:
http://www.teamw.in/project/twrp2/183
Download Links:
http://goo.im/devs/OpenRecovery/acclaim
http://techerrata.com/browse/twrp2/acclaim
And as always Enjoy your Nooks!
Didn't see this coming Awesome work! Now I'm waiting for 4.3 AOSP to fully release (it might have, not sure) I'm totally ready to compile!
Sent from my Barnes & Noble Nook Tablet using xda app-developers app
So to flash this, we open cyanoboot -> start fastboot, and then
Fastboot flash recovery openrecovery.IMG?
Sent from my Barnes & Noble Nook Tablet
That is correct. :good:
Is this compatible with the CM updater for automatic flashing?
Sent from my Barnes & Noble Nook Tablet using Tapatalk 4 Beta
Yup.
Sent from my Galaxy Nexus
I installed via Goo Manager, as recommended by the TWRP web page. All seemed to go normal but I have a problem with all the buttons "sticking" while in the recovery. Especially the keyboard. I reflashed & things seemed a little better but still there. I did do a couple BU's & was given the "Successful" reply. Has anyone experienced this button problem or is it just my flashing-thru-the-app problem?
Sent from my Barnes & Noble Nook Tablet using Tapatalk 2
What is the difference between TWRP and CWM recovery? Is there a benefit this has over CWM?
djd338 said:
I installed via Goo Manager, as recommended by the TWRP web page. All seemed to go normal but I have a problem with all the buttons "sticking" while in the recovery. Especially the keyboard. I reflashed & things seemed a little better but still there. I did do a couple BU's & was given the "Successful" reply. Has anyone experienced this button problem or is it just my flashing-thru-the-app problem?
Sent from my Barnes & Noble Nook Tablet using Tapatalk 2
Click to expand...
Click to collapse
I get the "sticky" buttons on this release, as well as the previous TWRP for acclaim. I've learned to just deal with it, it is still a bit easier to use than CWM.
Agree & thx. I can live with the button prob vs the other recovery also. Just wanted to confirm if it was only me.
Due to the fact that is official its fixable but I think we should migrate to emulated SD cards in 4.3 so I have to talk with kuzma first.
Στάλθηκε από το LG-P880 μου χρησιμοποιώντας Tapatalk 2
rajsris said:
So to flash this, we open cyanoboot -> start fastboot, and then
Fastboot flash recovery openrecovery.IMG?
Sent from my Barnes & Noble Nook Tablet
Click to expand...
Click to collapse
I just got the nook 8gb today with an 8gb microsd card already flashed with CM10 4.1.2 and am new to its development. Sorry for the noob questions but how do I access cyanboot to get to fastboot to flash TWRP?
Sent from my Barnes & Noble Nook Tablet using xda app-developers app
Reboot. If it has the CyanoBoot bootloader, then at the beginning of the boot cycle you'll get a prompt to "hold 'n' for menu". It's there in the menu. I've always used the Goo Manager app which flashes the recovery for you. Never had a problem, & is what I used to get 2.6.0.0 installed. Beware the "sticky" button issue tho. Works fine other than that.
Sent from my Nexus 7 using Tapatalk 2
djd338 said:
Reboot. If it has the CyanoBoot bootloader, then at the beginning of the boot cycle you'll get a prompt to "hold 'n' for menu". It's there in the menu. I've always used the Goo Manager app which flashes the recovery for you. Never had a problem, & is what I used to get 2.6.0.0 installed. Beware the "sticky" button issue tho. Works fine other than that.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Upon boot it shows N2ACards which is the program that was originally used to make the SD bootable of CM10 4.1.2. (This is secondhand info from the guy I traded this off of on craigs list.) It doesn't show the cyanboot bootloader or the n menu prompt. So the Goo Manager app is an alternative to flashing the recovery through cyanboot boot loader? What steps do I take to flash the recovery via Goo Manager?
Sent from my Barnes & Noble Nook Tablet using xda app-developers app
Juanito216 said:
Is this compatible with the CM updater for automatic flashing?
Sent from my Barnes & Noble Nook Tablet using Tapatalk 4 Beta
Click to expand...
Click to collapse
Where can I get the CM updater. I'm currently on CM10 4.1.2
Sent from my Barnes & Noble Nook Tablet using xda app-developers app
It's in the settings in About Tablet
Sent from my Barnes & Noble Nook Tablet using xda app-developers app
Any updates on the "sticky" button issue?
Sent from my Barnes & Noble Nook Tablet
I see TWRP updated to 2.6.1.0 which I also updated using Goo Manger with no problem, But buttons are still sticking. Using the recovery is a small chore & don't even think about trying to name a backup! Other than that it does Backup & Restore... so far.
Sent from my Nexus 7 using Tapatalk 2
djd338 said:
I see TWRP updated to 2.6.1.0 which I also updated using Goo Manger with no problem, But buttons are still sticking. Using the recovery is a small chore & don't even think about trying to name a backup! Other than that it does Backup & Restore... so far.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
The sticky keyboard is a huge PITA, for sure. I did manage to name a backup but it took nearly 20 minutes to do so.
hello
for the 1st time my nook tablet got mad
http://youtu.be/oJRJjMfI8fY
what to do?
thanks for help
Did you do anything before this happened? What are you running on it?
Sent from my BNTV600 using Tapatalk 4
asawi said:
Did you do anything before this happened? What are you running on it?
Sent from my BNTV600 using Tapatalk 4
Click to expand...
Click to collapse
cm10.1?
was playing candy crush and then dont remember if i turned it off or just left there...
Try holding the "n" button to get into CWM recovery where you then can reflash the ROM (or install a diffrent one) and appropriate gApps for the ROM.
i dont have the sd card with the system on it
so i just pressed and N and NT went into menu
and i rebooted
and this come out
booti: failed to read kernel
will try to root again
LG G Watch - Return to Stock
Current Version Included : LDZ22D (5.1.1)
Prerequisites:
Unlocked Bootloader (fastboot oem unlock)
ADB Debugging Enabled (Settings > About > Tap on build number 7 times > Swipe back > Developer Options > Enable ADB Debugging)
Drivers Installed (Windows)
Donations:
If you happen to like my ROM and find yourself wishing to donate, you can do so by pressing the "Donate to Me" button below my username on the left side of the screen. I spend my free time developing my contributions to the community, and every penny is greatly appreciated!
Changelog:
Version 1.0 (7/15/2015) :
- Initial release based on LDZ22D.
Downloads:
Version 1.0 (md5: 2a0369c8b4bd5fa848a06558c40c0bc6)
Mirror 1
F.A.Q
How do i use the installer?
Extract the archive.
Enter the "Installer" folder.
Enter the folder of the platform you're using (Windows, Linux, or OSX).
Run the installer and follow the on-screen instructions.
Linux and OSX scripts may need the proper permissions in order to run.
Please note: First boot will take some time, and you'll need to re-pair your watch and phone.
Questions? Comments? Concerns?
Leave all questions, comments, and concerns below, and I'll be sure to reply as fast as possible!
Is this restore tool using a rooted system img
Sent from my Nexus 4 using XDA Premium HD app
silent_bob52637 said:
Is this restore tool using a rooted system img
Sent from my Nexus 4 using XDA Premium HD app
Click to expand...
Click to collapse
Completely stock, untouched. Pulled the system.img as soon as I got my g watch and updated it to LDZ22D.
Sent from my SM-G925P using XDA Free mobile app
Thank you just what I needed
Flashed flawlessly relocked perfectly
Sent from my Nexus 4 using XDA Premium HD app
does anyone else have problems getting into stock 3e recovery? I get the android guy on his back but no options will appear after tapping screen
kornklown69 said:
does anyone else have problems getting into stock 3e recovery? I get the android guy on his back but no options will appear after tapping screen
Click to expand...
Click to collapse
I found I have to swipe down instead of tap
Sent from my Nexus 4 using XDA Premium HD app
silent_bob52637 said:
I found I have to swipe down instead of tap
Sent from my Nexus 4 using XDA Premium HD app
Click to expand...
Click to collapse
ya i tried everything
I am stuck here
http://postimg.org/image/iw76n9v5p/
i waited pretty long. I had to restart the watch and now it only boots into bootloader :/
Install worked, but can't update to the latest android wear as it fails on 61%
kornklown69 said:
does anyone else have problems getting into stock 3e recovery? I get the android guy on his back but no options will appear after tapping screen
Click to expand...
Click to collapse
Me too. Can't get recovery working again. Avoid this!
PainToad said:
Me too. Can't get recovery working again. Avoid this!
Click to expand...
Click to collapse
Try getting into Fastboot with the diagonal swipe or "adb reboot bootloader" and then using the arrows and circle button to go to recovery. Recovery works for me that way.
ApertureAndroid said:
Try getting into Fastboot with the diagonal swipe or "adb reboot bootloader" and then using the arrows and circle button to go to recovery. Recovery works for me that way.
Click to expand...
Click to collapse
problem is when i do that i still get the android guy on back and no recovery, i believe somehow recovery is missing and i can't figure out how to get recovery back..
kornklown69 said:
problem is when i do that i still get the android guy on back and no recovery, i believe somehow recovery is missing and i can't figure out how to get recovery back..
Click to expand...
Click to collapse
Yeah, I had that problem if I did "adb reboot recovery" or went to recovery directly. When I go through Fastboot it's fine.
Maybe the problem is different for you.
Tapping the screen does absolutely nothing?
ApertureAndroid said:
Yeah, I had that problem if I did "adb reboot recovery" or went to recovery directly. When I go through Fastboot it's fine.
Maybe the problem is different for you.
Tapping the screen does absolutely nothing?
Click to expand...
Click to collapse
yup tapping screen does nothing tapped everywhere and swipped and my watch has the update notification now when i swipe to update same thing goes to just the android on his back and doesn't update... frustrating lol maybe somehow I can rewrite recovery somehow... I'm not sure where to begin with that
kornklown69 said:
yup tapping screen does nothing tapped everywhere and swipped and my watch has the update notification now when i swipe to update same thing goes to just the android on his back and doesn't update... frustrating lol maybe somehow I can rewrite recovery somehow... I'm not sure where to begin with that
Click to expand...
Click to collapse
If all else fails I suggest following this post. Be sure to flash a custom recovery like TWRP before starting, though.
ApertureAndroid said:
If all else fails I suggest following this post. Be sure to flash a custom recovery like TWRP before starting, though.
Click to expand...
Click to collapse
I used twrp to wipe everything then used the tool to return to stock and then was able to load the ota update and bam fixed
I've been stuck on "sending userdata" for a really long time...