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.
Related
I'm really frustrated because what seems to work great for everyone it's not working for me.
I have a rooted NC 1.1 and I'm running an alternate launcher. I used the Auto-nooter 3.0 to get it to this point.
I installed the dual boot prep using CW Recovery, which went through just fine.
Now when I boot I get the "(multi) Uboot loading..." message for about 5-10 seconds and then the Nook boots into my regular Eclair system. So far so good.
I flashed the phiremod-nook-V6-dualboot zip from my sd card using CW Recovery and that went through just fine as well.
So now I hold down the n button while powering up and hold it while the multi Uboot screen is on, then I get brief flash of "loading" and immediately it goes to ANDROID_ screen where it hangs.
I repeated the same process twice and also tried a different ROM that is linked to in the first post of this thread http://forum.xda-developers.com/showthread.php?t=959461 (nookie froyo 0.6.8) still the same result.
Am I missing something that is obvious to everyone else?
Should I reformat the sd card first?
Is the Autonooter conflicting with dual boot?
Something else?
I wanted to post in the original dual boot thread, but the forum won't let me- not enough posts yet.
TIA
I'm really frustrated because what seems to work great for everyone it's not working for me.
I have a rooted NC 1.1 and I'm running an alternate launcher. I used the Auto-nooter 3.0 to get it to this point.
I installed the dual boot prep using CW Recovery, which went through just fine.
Now when I boot I get the "(multi) Uboot loading..." message for about 5-10 seconds and then the Nook boots into my regular Eclair system. So far so good.
I flashed the phiremod-nook-V6-dualboot zip from my sd card using CW Recovery and that went through just fine as well.
So now I hold down the n button while powering up and hold it while the multi Uboot screen is on, then I get brief flash of "loading" and immediately it goes to ANDROID_ screen where it hangs.
I repeated the same process twice and also tried a different ROM that is linked to in the first post of this thread http://forum.xda-developers.com/showthread.php?t=959461 (nookie froyo 0.6.8) still the same result.
Am I missing something that is obvious to everyone else?
Should I reformat the sd card first?
Is the Autonooter conflicting with dual boot?
Something else?
I wanted to post in the original dual boot thread, but the forum won't let me- not enough posts yet.
TIA
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
I've been looking all over this site but I can't find anything. I suppose that it's partly because I'm not sure about the problem myself.
A couple of months back (maybe more) I upgraded to the ICS infinitum rom (blue version) with midnight kernel. It was great - the phone worked fine. Well I'm exaggerating, it ****ed up every once in a while. Programs would automatically shut down and it would get really slow after a while. But all in all it wasn't bad, and it was stable enough for me most of the time....
Then, last Thursday everything seemed to go apart, every program on the phone was shutting down. So I thought I'll just restart and it will be fine. When I did, the phone did not come back on. the kernel would load and then it was stuck on the start-up animation in infinite loops.
Now, to be frank, this isn't the first time this has happened. So I didn't panic. Last time I just used the CMW recovery to re-install the kernel and the rom (I keep the files on the sd card). But this time, I wanted to try to avoid the factory wipe for as long as I could, and try finding a different option, knowing that if all else fails, I have something to revert back to.
Then I did the mistake of deleting the init.d file without re-installing anything. I wanted to, but accidentally clicked on the 'reboot now' option. And then all went to ****. The kernel didn't load. I went to recovery and it couldn't mount the sd card so I couldn't re-install it.
I tried flashing a new kernel using odin, and it did get me a bit better: my CWM recovery can read the sd. However, I still can't mount the system. Even worse, when I get to the infinitum zip roms and re-installing it brings up the status 7 error (which, after searching, seems to come up for different reasons for each person)
Despite installing a new kernel, when I reboot the phone now it doesn't load the kernel anymore, it just stays stuck on the welcome screen. I tried using the recovery to re-install a different kernel, it worked, but the phone still won't start - it now automatically skips to the recovery mode. I don't know if I should try flashing a rom through odin, and I'm too afraid to try anything at all now...
Can anyone help me? Is there any way to restore the init.d file or maybe that has nothing to do with my problem?
uvii said:
I've been looking all over this site but I can't find anything. I suppose that it's partly because I'm not sure about the problem myself.
A couple of months back (maybe more) I upgraded to the ICS infinitum rom (blue version) with midnight kernel. It was great - the phone worked fine. Well I'm exaggerating, it ****ed up every once in a while. Programs would automatically shut down and it would get really slow after a while. But all in all it wasn't bad, and it was stable enough for me most of the time....
Then, last Thursday everything seemed to go apart, every program on the phone was shutting down. So I thought I'll just restart and it will be fine. When I did, the phone did not come back on. the kernel would load and then it was stuck on the start-up animation in infinite loops.
Now, to be frank, this isn't the first time this has happened. So I didn't panic. Last time I just used the CMW recovery to re-install the kernel and the rom (I keep the files on the sd card). But this time, I wanted to try to avoid the factory wipe for as long as I could, and try finding a different option, knowing that if all else fails, I have something to revert back to.
Then I did the mistake of deleting the init.d file without re-installing anything. I wanted to, but accidentally clicked on the 'reboot now' option. And then all went to ****. The kernel didn't load. I went to recovery and it couldn't mount the sd card so I couldn't re-install it.
I tried flashing a new kernel using odin, and it did get me a bit better: my CWM recovery can read the sd. However, I still can't mount the system. Even worse, when I get to the infinitum zip roms and re-installing it brings up the status 7 error (which, after searching, seems to come up for different reasons for each person)
Despite installing a new kernel, when I reboot the phone now it doesn't load the kernel anymore, it just stays stuck on the welcome screen. I tried using the recovery to re-install a different kernel, it worked, but the phone still won't start - it now automatically skips to the recovery mode. I don't know if I should try flashing a rom through odin, and I'm too afraid to try anything at all now...
Can anyone help me? Is there any way to restore the init.d file or maybe that has nothing to do with my problem?
Click to expand...
Click to collapse
I suggest flash 3-file GB rom via odin with ticked re-partirion and phone bootloaderupdate.
First of all init.d has nothing to do with the boot of kernel and ROM itself. It's just like autostart in Windows, so if it's missing it shouldn't cause problems.
My solution is to flash a complete stock Gingerbread ROM using Odin. You can get them at sammobile.com. Then afterwards flash a custom kernel and then whatever you like.
If you need help,feel free to ask me
Sent from my Gameboy Color
Yes! Thank you! That worked!!
It happened again! just 10 days later.
Is the Infinidtum rom ****ed up in any way?
it's stuck on the loading part of the rom