Hello, I'm not particularly new to Android, nor am I new to the prospect of flashing roms. However, I recently flashed an upgrade of cm10.1 to my Nook HD via recovery and I'm now stuck at "Loading (SD)..." in the bootloader. Is there a specific way that CM10.1 has to be upgraded or did something just go wrong during the flash? With my other devices, you can just flash the upgrade zip from the recovery menu. Thanks in advance for the help!
and finglha
bradleyrogers89 said:
Hello, I'm not particularly new to Android, nor am I new to the prospect of flashing roms. However, I recently flashed an upgrade of cm10.1 to my Nook HD via recovery and I'm now stuck at "Loading (SD)..." in the bootloader. Is there a specific way that CM10.1 has to be upgraded or did something just go wrong during the flash? With my other devices, you can just flash the upgrade zip from the recovery menu. Thanks in advance for the help!
Click to expand...
Click to collapse
Up until the most recent .zip, I have done just what you described. Couple times my HD god hung up during that same process... I just powered down and restarted and it booted fine.
lossofsilence said:
Up until the most recent .zip, I have done just what you described. Couple times my HD god hung up during that same process... I just powered down and restarted and it booted fine.
Click to expand...
Click to collapse
Yea it has happened to me too, I just powered off with a long press on the 'N' and power button. Restarted and it worked fine.
Actually i'm on 10.1 too.
This thing happens sometime. This is normal for early alfa soft.
On first clean install test i had 3 or more times stop on Cyanogen logo. But it started work on fourth time. Same happened with second clean install too (messed Adnroid to death with my hard tests and modifications ). Power OFF/On have sometime magical power.
Well, I was able to restart the nook and flashed the zip again. It worked! However, I can't change the brightness. To be honest, I can't remember if I even tried before. So, is this just a bug or is it common? Thanks for the help guys
bradleyrogers89 said:
Well, I was able to restart the nook and flashed the zip again. It worked! However, I can't change the brightness. To be honest, I can't remember if I even tried before. So, is this just a bug or is it common? Thanks for the help guys
Click to expand...
Click to collapse
I have no problem adjusting brightness on 1/28
codya321 said:
I have no problem adjusting brightness on 1/28
Click to expand...
Click to collapse
It's weird. I couldn't get it to work without using the Tablet UI. Once I switched, it started working. Oh well, it's working fine now. Thanks for the help, you guys are the best.
CM 10.1 needs some time for settle. Then it works wthout lag
Sent from my GT-I9100 using Tapatalk 2
Related
http://forum.cyanogenmod.com/topic/...r-barnes-noble-nook-color-v700-10-april-2011/
here it is
[email protected] said:
http://forum.cyanogenmod.com/topic/...r-barnes-noble-nook-color-v700-10-april-2011/
here it is
Click to expand...
Click to collapse
Thanks bro
thanked. just took the plunge from froyo to cm7 on friday! shoulda waited 2 days but hey, should be a lot quicker this time around.
looking forward to checkin it out
Holy shiznit! Looks like I'm going to have to upgrade from Froyo sooner than expected. I was wondering why dalingrin's kernel thread was so quiet this weekend. Sounds like he and the rest of the Encore team were hard at work.
Sent from my DROID2 using XDA Premium App
lol.. wouldn't matter. CM7 is constantly making updates. I usually flash every other day.
anyone know if this fixes sleep issues?
Yes, the answer is no.
Sent from my Desire HD using XDA App
samuelhalff said:
Yes, the answer is no.
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
OUCH!!! The sleep thing and huge battery drain prevented me from shifting from old-but-sturdy 2.1 stock, which I charged last time...let me think...31 March.
If I had CM7 I would have charged it already 5 times.
Cm7 power problems / sleep death
This may be a dumb question but if Nookie Froyo doesn't have either of the power or sleep problems that CM7 does, would it be possible to track down and fix these bugs by comparing their source codes?
so many awesomes. but im guessing flash still dosnt work?
jabrams said:
This may be a dumb question but if Nookie Froyo doesn't have either of the power or sleep problems that CM7 does, would it be possible to track down and fix these bugs by comparing their source codes?
Click to expand...
Click to collapse
I believe they've found the problem and have fixed it in the kernel, but since it was so close to the release date, they've decided to release CM7 first with the existing kernel first, and then bug test the new one with the fix.
So we can look forward to having it fixed in the next few nightlies, hopefully.
boogerboy72 said:
so many awesomes. but im guessing flash still dosnt work?
Click to expand...
Click to collapse
Flash has been working flawlessly since mid-March in CM7. The only major issues to be worked on still with CM7 are improved Bluetooth range, eliminating the Sleep of Death (although it uses only ~1%/hour for me now while in sleep), and as with every device continued performance tweaks. There are plenty of smaller things to be fixed as well including screen shot support (which was fixed by Fattire and just needs verified/added to source), integrated button remapping (in works by Mad-Murdock), and anything else people can think to work on.
boogerboy72 said:
so many awesomes. but im guessing flash still dosnt work?
Click to expand...
Click to collapse
Flash works fine with CM7 stable.
Awesome. So far it's running great.
Sent from my NookColor using Tapatalk
Just got it installed..
So far so good. I took the plunge last night to get it installed. Well, first try after formatting system, data, and cache went ok. Then rebooted and it got stuck on "Android" text at the bottom. Simply restarted holding the "power + n", then it successfully booted into CWR. Flashed and viola. Looks good. Love the included Cyanogen wallpapers. =)
So far, no issues, but then again, I haven't played with it much. My Bluetooth option is listed and when I try to turn it on, it tries for a bit, then does nothing. Any ideas?
Oh yeah... I used the OC kernel and it seems to be fine. =P
hvuong2 said:
So far so good. I took the plunge last night to get it installed. Well, first try after formatting system, data, and cache went ok. Then rebooted and it got stuck on "Android" text at the bottom. Simply restarted holding the "power + n", then it successfully booted into CWR. Flashed and viola. Looks good. Love the included Cyanogen wallpapers. =)
So far, no issues, but then again, I haven't played with it much. My Bluetooth option is listed and when I try to turn it on, it tries for a bit, then does nothing. Any ideas?
Oh yeah... I used the OC kernel and it seems to be fine. =P
Click to expand...
Click to collapse
BLuetooth is a known issue. You need to either hard reboot, which is holding the physical power till it shuts off, or choose "Fix permissions" in Rom Manager then reboot, or a combination of both.
eozoon said:
I believe they've found the problem and have fixed it in the kernel, but since it was so close to the release date, they've decided to release CM7 first with the existing kernel first, and then bug test the new one with the fix.
So we can look forward to having it fixed in the next few nightlies, hopefully.
Click to expand...
Click to collapse
That is great news! I hope the new kernel comes ouut soon to! How or where did u hear/read about it?
Also a seperate question. The link i have for the CWR image for my sd card is bad. Not for a bootable sd. I want to nstall cm7 from scratch on the EMMC but i first need to image a CWR sd card then put cm7 stable on it. Do you have that image link?
Thanks!!!
hey guys i have somewhat of a dumb question. I have my nok running hneycomb using that dual booth method. If i wanred to flash cm7 on it, should i completely undo the dual boot? Or go ahead and boot into recovery and try installing it?
You have to first undo the dual boot, because the dual boot created a second partition (hd) on your nook color. If you don't undo the dual boot, you'll just lose that space as cm7 will overwrite the file that allows you to boot into honeycomb.
none of the widgets I downloaded are showing up on the widget list with this rom
Hi,
I've run into a boot-loop problem with my rooted nook color.
It was working fine before, but i turned it off today and connected it to a charger.
Suddenly i noticed it started booting up but the boot stopped at the Nook Color devs screen. It keeps looping on that screen till halfway the word color (in rainbow colors)
I haven't done any updates or anything, it just started doing that.
Is there a way of doing a reset WITHOUT having to go through a factory reset ?
Of course, being the *ss i am, i forgot making a backup, so i would prefer not to lose data and stuff on the nook.
As i recall, i rooted the Nook Color with CMW 3.0.2.8 and Manual Nooter 4.5.18.
Any help would be appreciated
Kind regards,
Jeroen
Take the rom you prevously used to flash...wipe cache and dalvic only....the reflash it..if you are running cm it should be okay....if stock..I do not know...
Tanks God =) Somebody with the same issue.
oenie said:
Hi,
I've run into a boot-loop problem with my rooted nook color.
It was working fine before, but i turned it off today and connected it to a charger.
Suddenly i noticed it started booting up but the boot stopped at the Nook Color devs screen. It keeps looping on that screen till halfway the word color (in rainbow colors)
I haven't done any updates or anything, it just started doing that.
Is there a way of doing a reset WITHOUT having to go through a factory reset ?
Of course, being the *ss i am, i forgot making a backup, so i would prefer not to lose data and stuff on the nook.
As i recall, i rooted the Nook Color with CMW 3.0.2.8 and Manual Nooter 4.5.18.
Any help would be appreciated
Kind regards,
Jeroen
Click to expand...
Click to collapse
I have the same problem...
I searched all the internet the solution for this issue... dont founded yet...
(sorry about my bad english... I speak portuguese...)
I had the same problem, ended up having to go back to stock (using cwm) and then re rooting. Since I already had everything on the sd card, i redownloaded the apps I wanted after rooting and the whole proces only took about 20 minutes. I've since downloaded titanium backup in case it happens again so I can skip that last step and it should only take about 10 minutes to get everything back.
Just an FYI I bootlooped by updating Adobe Flash Player through the market. Looks like the stock ROM either depends on its certain version of Flash our has a special version just for the Nook.
theoguedes said:
I have the same problem...
I searched all the internet the solution for this issue... dont founded yet...
(sorry about my bad english... I speak portuguese...)
Click to expand...
Click to collapse
The problem with all version of MN prior to 4.5.25, is that they run the risk of Adobe Flash auto-updating themselves. You have to manually go into the Market and un-check the auto-update box. When flash updates itself, it causes the boot-loop when the device reboots.
You can try this fix, download the attached file, and flash it with CWM. The file should delete the adobe flash files, and then install Flash 10.3. This should fix the boot-loop, and keep your current file system without having to reset. If the fix works, and the device boots up, then make sure that you go into the Market, and uncheck the auto-update for flash.
If you have any problems understanding my English, let me know and I can try to reword it for you.
I got the pre-rooted ics rom on my Vivid. Now, everytime I restart my phone, it goes into this "Android is upgrading" screen and starts "optimizing" applications. IS there any workaround to this?
*EDIT*
I forgot to mention, my phone still boots up after that, but it gets annoying having to sit through that screen every time I restart my phone.
Also, I get no audio from any apps but my music app... No music from videos, games, or any other app... What is with this???
mines does the same thing, and mine wont let me message, just says please wait.....
Same thing here. Mine takes about 30seconds to reboot, so i don't mind. Got used to that years ago, when i had a BB9000.
same here, but only when I choose restart. If I soft boot, power off and manually turn it on it does not do that.
http://www.htc.com/us/support/vivid-att/downloads/
Here you go guys. Just update to the official release. Should solve the problems.
So I'm guessing no root for now?
I think its an ics thing. Was not rooted before updating to ics and my vivid does this. I think its an ics self check deal
Sent from my HTC PH39100 using XDA
No, you can but you have to have the correct recovery.
http://www.wcxxperia-nce.com/index.php
Go here, register, and read the vivid forums. Wild Child will get you set up. Just read everything, watch the videos, etc. before you do anything! Follow all of the directions.
Can I install that while still on another ICS rom?
Luigiman765 said:
Can I install that while still on another ICS rom?
Click to expand...
Click to collapse
What are you on/ what have you done so far?
Are you stock rom? Do you have boot loader unlocked?
I am on the rom given here:
http://www.androidauthority.com/vivid-4g-pre-rooted-ics-htc-sense-3-6-63538/
And I have relocked my bootloader in preparation for installation
Luigiman765 said:
I am on the rom given here:
http://www.androidauthority.com/vivid-4g-pre-rooted-ics-htc-sense-3-6-63538/
And I have relocked my bootloader in preparation for installation
Click to expand...
Click to collapse
http://www.htc.com/us/support/vivid-att/downloads/
Look here, this might be of help. You can download the file and update that way.
Thanks, new rom is brilliant, fast, and solved my problems
Luigiman765 said:
Thanks, new rom is brilliant, fast, and solved my problems
Click to expand...
Click to collapse
Glad to hear it!
Hey Guys!
I recently upgraded from the latest CM9 Nightly to Jscullins 4.1.2 using clockwordmod....i also upgraded my GAPPS....
Whenever i boot up to CM10...it works fine for a minute and then freezes. The only way i can get it out of the freeze is by doing a Hard restart..
When I say "Freeze" i mean the touchscreen stops working...of it just freezes.
How do I fix this??!! Please Help!!
Thanks!
kmanleafs said:
Hey Guys!
I recently upgraded from the latest CM9 Nightly to Jscullins 4.1.2 using clockwordmod....i also upgraded my GAPPS....
Whenever i boot up to CM10...it works fine for a minute and then freezes. The only way i can get it out of the freeze is by doing a Hard restart..
When I say "Freeze" i mean the touchscreen stops working...of it just freezes.
How do I fix this??!! Please Help!!
Thanks!
Click to expand...
Click to collapse
I don't know if it will work or not, but you can give the attached zip file a try.
chicle_11 said:
I don't know if it will work or not, but you can give the attached zip file a try.
Click to expand...
Click to collapse
Thanks but the title says "4.2.2" and i have 4.1.2...and what exactly is it?
kmanleafs said:
Thanks but the title says "4.2.2" and i have 4.1.2...and what exactly is it?
Click to expand...
Click to collapse
Again, I don't know if it will work for not.
It's a fix for touch sensitivity issues.
Make a backup, just in case.
Edit : cm10 needs more room than CM9. Make a backup, then run acmeuninstaller. Use AcmeInstaller 3 to flash the CM10 rom along with the appropriate gapps. You might as well upgrade your moboot to 0.3.8 and and your cwm to 6.xxx. You can find these files in Goo.im, under developers and Jscullins. For cwm use the 12/15 one.
Once installed you can restore your apps using advanced restore in cwm (you want to restore the data only).
Good luck.
Ok...i noticed that it is actually a HEAVY LAG, rather then a freeze. I was able to go into the "Usage" Panel in settings and noticed that i have 148MB in "System" and around 20GB in 'SD Card". When I tried to exit...it froze and the screen turned off and it wouldn't turn back on...I do NOT want to do a complete restore....
kmanleafs said:
Ok...i noticed that it is actually a HEAVY LAG, rather then a freeze. I was able to go into the "Usage" Panel in settings and noticed that i have 148MB in "System" and around 20GB in 'SD Card". When I tried to exit...it froze and the screen turned off and it wouldn't turn back on...I do NOT want to do a complete restore....
Click to expand...
Click to collapse
Well then, I hope you have a backup.
You do need to use AcmeInstaller 3 to flash cm10, or you will keep running into problems.
Edit:make sure that the battery is fully charged before doing anything.
If the tablet remains unresponsive, you might have to use this guide : http://forum.xda-developers.com/showthread.php?t=1426244
If you do, you will have to do a complete restore.
Hey there,
I went from stock to CM10.1 and everything works correctly, except that I get bluescreens and now random reboots. I update nightlies hoping that the problem disappears.
Is there anyone that can help me with that issue. It happens randomly, even when it just sits there doing "nothing".
Please help, I don't want to go back to T-Mobile stock (that's where it last worked)!
ami2510 said:
Hey there,
I went from stock to CM10.1 and everything works correctly, except that I get bluescreens and now random reboots. I update nightlies hoping that the problem disappears.
Is there anyone that can help me with that issue. It happens randomly, even when it just sits there doing "nothing".
Please help, I don't want to go back to T-Mobile stock (that's where it last worked)!
Click to expand...
Click to collapse
You could always use the stable version of CM10. It's still Jellybean, just 4.1.2 instead of 4.2.2. My biggest problems with CM10.1 are bluetooth and connecting it to the PC as a Mass Storage Device. With CM10, I have never had issues.
Go up and read the threads in the general forum. The last really stable cyanogenmod releases were the M3 "snapshot". Anything after that is what you get, random reboots, graphical problems etc. Try that one.
fraughtsigewulf said:
You could always use the stable version of CM10. It's still Jellybean, just 4.1.2 instead of 4.2.2. My biggest problems with CM10.1 are bluetooth and connecting it to the PC as a Mass Storage Device. With CM10, I have never had issues.
Click to expand...
Click to collapse
srpanadero said:
Go up and read the threads in the general forum. The last really stable cyanogenmod releases were the M3 "snapshot". Anything after that is what you get, random reboots, graphical problems etc. Try that one.
Click to expand...
Click to collapse
Ok i will try the M3, and not do the nightlies.
I ll report back if that solved my problem.
Fixed. read post above.
Thank you so much for your help!!
I see problem fixed sorry to hijack but what version of clockword mod are u running. I have 5.5. Orsomething like that but can download and roms? Error 7 keeps popping up. And if i upgrade cwm where and how would that be. Sorry once again
parmakr said:
I see problem fixed sorry to hijack but what version of clockword mod are u running. I have 5.5. Orsomething like that but can download and roms? Error 7 keeps popping up. And if i upgrade cwm where and how would that be. Sorry once again
Click to expand...
Click to collapse
That has nothing to do with the problem. But it is because you are using an old recovery, either update CWM or use goo manager to install TWRP, which is touchscreen anyways. Then you wont have the Error 7 anymore.