Related
Currently I am running nookie froyo 0.6.8 from the internal rom but I am having the following problem even when I had eclair with autonooter. When I am turning off my nook for the night, in the morning I am stuck at the "Touch the future..." screen and I can only boot through clockwork recovery and choose reboot. I think that it started when I flashed clockwork for the first time, but I am not sure. Any ideas?
aposva said:
Currently I am running nookie froyo 0.6.8 from the internal rom but I am having the following problem even when I had eclair with autonooter. When I am turning off my nook for the night, in the morning I am stuck at the "Touch the future..." screen and I can only boot through clockwork recovery and choose reboot. I think that it started when I flashed clockwork for the first time, but I am not sure. Any ideas?
Click to expand...
Click to collapse
I am searching the forums to find an answer to the same problem. I am running stock eclair that has been autonootered. I don't have clockwork installed. I can always boot with the sdcard to Honeycomb.. sometimes I can then reboot back into Eclair.
i had this one time, i try the 8 failed boot's to restore, didn't restore but rebooted to eclair!
arf, i'm having the same problem after all..
I had the same thing happen to me had to reformat cache if I wanted to boot into froyo,its a great system but that one problem did me in went back to stock and rooted the NC and plan on staying this way I just give up flash.Looked all over for fix or someone to explain why but never did get an answer sorry i couldnt help you but if i find answer will let you know
ok will look forward when i have time
At this point i can boot by pressing power + n for 30s, it boot to recovery, then i choose "reboot"
Yes that's right, this is the only way I can boot too (power but. + n).
when rebooted i lower setcpu to 1ghz max. it seems to help to boot ..
There are some really good unbricking//"my nook won't boot" sort of threads to be found in the developers section; but this one should be more than enough to fix your issues:
http://forum.xda-developers.com/showthread.php?t=949699
Additionally, I find that reflashing to a stock ROM or restoring a previous working backup image from CWM is the best way to go about it. Good luck!
I have the same problem too. Just remove the SD card on power on (reboot with software is OK)
Looking for better fix.
Taeseong said:
There are some really good unbricking//"my nook won't boot" sort of threads to be found in the developers section; but this one should be more than enough to fix your issues:
http://forum.xda-developers.com/showthread.php?t=949699
Additionally, I find that reflashing to a stock ROM or restoring a previous working backup image from CWM is the best way to go about it. Good luck!
Click to expand...
Click to collapse
Thx, I'll take a look at that if I ever have booting issues.
Think this is caused by the recovery image. Upgrade your recovery to the latest version 3.0.1.0 and see if that fixes it.
http://forum.xda-developers.com/showthread.php?t=971197
Going to try that today ..I just looked and i do have an older recovery file so maybe that is the problem will report back later on it.
Did the update, I will shut it off for the night and will check it in the morning.
Sent from my Nook Color
I also read CWR does not get along with 1.1..I just updated CWR and it still did the same thing what Im going to do now is clean restore then custom froyo then after setup go to market get rom manager install reboot into recovery and then install the remove crw with root file.
I downloaded the restore to stock zip file. Put it on the sd card. Then used the power and "n" to get to the butloader. Chose install from sd card and it installed. Back to operational!
OK i got a nook, rooted using AN3.0 (it is 1.1.0) and then put cm7 Tab tweaks on the eMMC using cwm and flashed GAPPS and The latest OC kernel with I/O fix. my nook runs GREAT!
however a buddy of mine liked what he saw so he went out and got one, we used AN3 to root it, then flashed cm7TT, gapps, and the kernel and his acts funny. on the first boot after the flash we got an error saying something like "bad install, please contact B&N" so i powered down, back up, and it worked. Funny thing is when we boot it still has the nook splash screen "harness the power of reading" or whatever it says. also he frequently gets boot loops and it just runs really buggy. we tried re downloading the ROM and re-flashing (with the stock cm7 kernel this time) and have the same issues. also i can OC mine to 1190 easy, if he does anything over 1000 he gets freezes and boot loops....any ideas...the weirdest part is the "enjoy the power of reading" splash screen.....help?
Sounds like something didn't get cleaned up. So if I were you, I would get CWM on a sd card, then I would get the stock 1.1.0 image and reflash it. Don't nooter or anything like that, there's no point.
Then I would wipe the following... /system, /data, /cache and dalvik cache. Then after all that is done, go ahead and reflash the newest nightly (it has the tablet tweaks), also you're running Madkat's OC, grab the newest Daligrin one as it's more stable and may work better with his nook.
Can anyone give me a hand with this?
I was running CM7 n40 with ALSA and dalingrin's 0413a kernel. Watching videos in vevo when the nook froze and reset itself and got stuck looping at the CM7 animation.
I've rebooted into CWR, tried first wiping Dalvik cache, it didn't seem to make a difference. I then tried formatting /cache and reinstalling n40 and dalingrin's 0404 kernel. No joy either.
Short of reinstalling everything, is there anything else I can try?
If you are running from an SD card then your problem is likely the card. If you aren't running from an SD card then... Maybe someone else can help you.
Forgot to add, running from eMMC.
I had the same thing, only with CM stable...ended up having to rebuild my / boot with the file here.... http://forum.xda-developers.com/showthread.php?t=914690.
Very last file in first post. Had to flash it then start all over....
Sent from my NookColor using XDA Premium App
You are not alone, mine just did this after updating to the latest nightly and restoring with Titanium Backup. I did not flash a kernel, just the nightly using Rom Manager.
My symptoms were that it seemed to run OK, then I opened the gallery to set a different wallpaper and got constant FCs, so then I restarted. Now I'm watching the circle go round and round.
OK, back to previous, just restored the nandroid backup Rom Manager made prior to the update. Seems to be working fine.
I flashed n40 and dalingrin's oc kernel 0404. Stable and happy as can be.
I'm thinking the issue was with ALSA and experimental kernel 0413a, which has been reported to crash video playback in some cases. Don't know how or why it would corrupt my install though.
Let me just mention a lot of people are claiming false boot loops lately. Sometimes it just takes a long time to reboot, especially after it froze. I've had it take up to 20mins before with the little skateboard android.
So next time unless it's giving you "Touch The Future" and then the CWM treatment, give it a bit to load and see if it does after 10 mins or so. (Usually just after the screen dims, my nook loads up just fine)
No that's unacceptable. Considering the amount of data it should be loading, something is very wrong with your nook if it takes more than 5 minutes to boot.
And yes it was boot looping, the animation restarted itself repeatedly (wasn't just the arrow spinning).
Can't help at all but to offer another data point: I was on nightly 39, ALSA update, and kernel 0413a. Was flicking between homescreens when it locked up, forcing a hard shutdown. When I booted back up, it was stuck in a bootloop. Tried all the usual paths to recovery, but had to resort to a backup.
Moved on to n41 (ALSA included) and kernel 0418c. Stable in every case so far.
I'm having same issue and mine is still not working no matter what I did.
I even tried to restore it back to stock - Format/ Fdisk / DD / etc... tried everything I could find. I even had my back up but couldn't restore. I think I created more problem while I was trying to fix it.
Now I can only boot from SD. So I was not the only one.
Eww, I would never touch any sort of partition change with eMMC installs. Usually I just go back to stock or latest backup. Found out there may be an issue with backups created from CWR flashed to eMMC (MD5 check failure). SO anyone who's made a backp from that, do yourself a favor and boot off a CWR SD and do a backup onto that just to be safe.
Sorry about your troubles, hope you get it sorted. Guess I got away easy with just format and nightly re-flash.
I am running CM7.0.0 with Dalingrens OC at 1.18GHz. Nothing else crazy, although I did have it set up for dual boot, but not anymore.
My nook will boot up, make it through the CM7 boot screen, and then go to my home screen, but thats it. I can't select anything, the N button won't work, it won't go to sleep. After a while it reboots. This happened sometime last night when it was on the charger. If I boot into ClockWorkMod everything functions normally. I have tried reflashing CM7, but no dice. It flashed but didn't fix the problem. Any ideas before I do a full wipe/reset?
Also, if I do a full wipe, does that wipe emmc as well?
try dropping to 1Ghz...some chips just don't like 1.1
NOTE: I am not the developer of this rom! I am only posting it on XDA with the permission of the Bonsai Team. The download link is on the Bonsai website, they use a checkout system to track downloads and to present you with an easy way to donate if you choose. YOU DO NOT HAVE TO DONATE TO DOWNLOAD! I will do my best to keep this post updated with change logs.
Custom tuned and ready for your sleek new Samsung tablet. The Bonsai ROM provides superior battery life and performance delivering on the promise of the Android OS for mobile devices.
This is an early beta release Bonsai for your Samsung Galaxy Tab 10.1 based from the stock Android Honeycomb v3.1 release. We’ve consolidated the latest Android community developments and rolled in the Bonsai magic to produce a replacement Android OS that will double your stock tablet performance.
Note: Due to going to some shell scripting where we have richer language and can control the install better, we are not able to update the progress bar while in this stage of running the install.
Some of the features of this release include: (credits below)
Android Kernel updated to v2.6.36.4
Overclockable kernel
Kernel module support for tun, cifs, aufs, ntfs, bluetooth mouse, xbox joystick
Voodoo Sound v9 (first release for Galaxy Tab 10.1) (Updated to v10)
init.d initialization script support
Ext4 filesystems can be configured without journaling enabled
New ROM packaging and install reduces package size by 20%
Deodexed and png graphics optimized
v0.1.5 Changes:
Update to Voodoo sound v10
Fixed problem with Plex app not streaming video
Kernel tuning which has raised MFlops from about 50 to 80 (AnTuTu score around 5800)
Changed init.d script permissions to accomodate “challenged” editor apps
Install script changes to accomodate more device variations
Known to run on Locked and Unlocked retail Tablets and I/O Tablets
Fixed problem where tablet would not boot with USB cable attached
Reduced delay seen when booting the device
Known Issues:
A few users have reported issues with boot animations in most cases the device seems to boot fine.
There seems to be a problem with CWM when its flashed via Rom Manager.
Google I/O Devices are currently not working. (There are instructions in post 121)
Install Instructions:
Download the ROM
Move the .zip to /sdcard
Unplug anything connected to the Tab
Reboot to Recovery
Make a nandroid backup
Wipe cache
Wipe dalvik
Flash the .zip
Reboot
Please be patient and wait for it to boot it it can take a while
Enjoy
If you want to change the OC settings, you will need to edit the file, /etc/init.d/24-cpufreq to set these values. The values are in the top of the file as follows:
Code:
FREQGOV=’ondemand’
MAXFREQ=’1000000’
MINFREQ=’216000’
Change these values as you wish. The parameters are applied on reboot.
Credits:
kernel: @pershoot []
voodoo sound: @supercurio []
Along with those changes that were provided in earlier releases, we are providing a number of changes that have been backported from the nVidia Tegra development. Changes include:
Tegra CPU power control
Add Tegra CPU perfmon context for power
Redisgn of Tegra CPU reset handling
Various Tegra CPU (cortex-A9) cache handling fixes
Fix memory leak in video driver
Tegra shared clock cleanup
Please flash this file after installing the 0.1.5 ROM package.
0.2.4 KERNEL UPDATE
DOWNLOAD HERE
NOTE: TouchWiz UX version includes the v0.2.4 Kernel. This ROM package is double the size of the non-TouchWiz, now weighing in at 350MB. Please help us conserve bandwidth. If for some reason you believe the ROM package to be corrupt, please double check your package using the md5sum command. The md5 checksum of this package is: 484a758563e661a7731aeed4a1e880f0
This is an early beta release Bonsai for your Samsung Galaxy Tab 10.1 based from the stock Android Honeycomb v3.1 release which includes TouchWiz. We’ve consolidated the latest Android community developments and rolled in the Bonsai magic to produce a replacement Android OS that will more than double your stock tablet performance.
WITH TOUCHWIZ UX DOWNLOAD HERE
----------------------------------------
you can use setcpu to change cpu frq.
Bug report: if you turn off your tab and plug into the charger to enable charging mode, it causes reboot loop (therefore you can't charge it while off)
antonyfl said:
you can use setcpu to change cpu frq.
Bug report: if you turn off your tab and plug into the charger to enable charging mode, it causes reboot loop (therefore you can't charge it while off)
Click to expand...
Click to collapse
Thanks for the bug report. As for the setcpu thing, while you can do that the system is configured with its own governor of sorts and setcpu fights with it and can cause some slowdowns so its not recommend to use it.
Currently the best way is to adjust it in an init script located in /etc/init.d/24-cpufreq
Any idea why I get a scrambled picture when i reboot that hangs before booting?
it seems like a boot logo/animation crapping out
DroidHam said:
Any idea why I get a scrambled picture when i reboot that hangs before booting?
Click to expand...
Click to collapse
so far no, however the dev is looking into this issue, as well as the kernel panic issue.
I am enjoying this ROM, glad an official thread was made
i'll add my issue in hopes someone can help. tried to load rom yesterday. it boot looped at the initial "samsung galaxy tab" screen. powered down then into upload mode, kernel panic. got into fastboot and booted cwm. tried to restore my last nandroid and it boot looped at the samsung animation screen. tried another nandroid and got error at data. i get either of these responses. i've tried to factory reset and still get boot loops. repeated all these a hundred times and boot loop at either of those screens. any ideas on how to get this thing back running. at this point i don't even care so much about a nandroid, i'd settle for any type of working tab.
bodiecon said:
i'll add my issue in hopes someone can help. tried to load rom yesterday. it boot looped at the initial "samsung galaxy tab" screen. powered down then into upload mode, kernel panic. got into fastboot and booted cwm. tried to restore my last nandroid and it boot looped at the samsung animation screen. tried another nandroid and got error at data. i get either of these responses. i've tried to factory reset and still get boot loops. repeated all these a hundred times and boot loop at either of those screens. any ideas on how to get this thing back running. at this point i don't even care so much about a nandroid, i'd settle for any type of working tab.
Click to expand...
Click to collapse
Have you tried to use odin to restore the tab to stock? i would suggest you try this first.
this ODIN version: HERE
this pda md5: HERE
Also I would like to add that when flashing the Bonsai ROM make sure your tab is not connected to anything including the charger and usb.
I have had ZERO issues at all with this ROM
Tried install on a rooted 16G running pershoot's latest oc kernel......
Wiped dalvik/cache
installed
reboot
never got past the gt 10.1 screen, was able to get back to recovery and restored my nandroid backup
maybe it was a bad flash, going to try one more time unless anyone has suggestions or sees something I missed
mark1962nc said:
Tried install on a rooted 16G running pershoot's latest oc kernel......
Wiped dalvik/cache
installed
reboot
never got past the gt 10.1 screen, was able to get back to recovery and restored my nandroid backup
maybe it was a bad flash, going to try one more time unless anyone has suggestions or sees something I missed
Click to expand...
Click to collapse
Reread the instructions because I added an additional step, also if the problem persist try going back to a stock kernel first and let me know how that goes.
Also keep in mind the first boot takes a very long time, my first boot took almost 15mins, and about five of that was on the first boot screen.
djrajir said:
Reread the instructions because I added an additional step, also if the problem persist try going back to a stock kernel first and let me know how that goes.
Also keep in mind the first boot takes a very long time, my first boot took almost 15mins, and about five of that was on the first boot screen.
Click to expand...
Click to collapse
The first time I rebooted to recovery through Rom Manager (which I don't generally do), this wouldn't affect anything would it?
mark1962nc said:
The first time I rebooted to recovery through Rom Manager (which I don't generally do), this wouldn't affect anything would it?
Click to expand...
Click to collapse
I'm not sure, it shouldn't however there have been issues like this before which is why i always manually reboot my device into recovery (such as what is currently going on with Galaxy S 4g devices)
what is journaling?
Also i flashed this (over pershoots kernel)
and now its stuck on Samsung Tab 10.1 at boot
I flashed following the instructions and everything installed fine except I keep getting fc on most of the apps I try to run. Anyone else having that issue?
lollee76 said:
I flashed following the instructions and everything installed fine except I keep getting fc on most of the apps I try to run. Anyone else having that issue?
Click to expand...
Click to collapse
How did you reinstall apps? Market or TiBu?
SS2006 said:
what is journaling?
Also i flashed this (over pershoots kernel)
and now its stuck on Samsung Tab 10.1 at boot
Click to expand...
Click to collapse
Please let me know if you get it to work (this was my experience as well)....I'm going to give it another shot after dl'ing.
I cant seem to turn it on anymore cause battery died while it was frozen
i pluged it in, at one time it showed the battery charge indiciator
now its just not turning on
mark1962nc said:
How did you reinstall apps? Market or TiBu?
Click to expand...
Click to collapse
The first time I tried I did the whole wipe data/factory,cache,dalvik and re-installed apps using My Backup and got fc like crazy...so then I restored my nandroid backup and started over (Note I did test one app with TiBu by installing from the market and restoring just the data to that app using TiBu and it just hung up).
This morning I read this post and restored my nandroid again and tried the directions in OP and only wiped cache and dalvik which left my apps as is.
I also want to note I was using pershoots kernel before flashing this ROM.