Hi everyone, took a friends Nook Color after showing him mine with MIUI on it (1.9.16). Told him I could get his 1.2 or 1.3 refurbished Nook to MIUI or CM7, and after using a SD Card CWR to install either (with wiping all data/cache/system/etc.), I can get the install to perform fine in CWR. However, upon booting, I get loops at any and all splash screens, MIUI stays on orbiting planet, CM7 stays on Nook Color rainbow screen, none can actually get into the OS. I've tried to replace partition with boot zip around here, to no avail. Anyone have any ideas what the problem is?
Also, when trying to restore 1.2 or 1.3, the keyboard will flash onscreen when trying to type info to register, then immediately hide; I'm unable to input text before it disappears again! Thanks for your help.
Nobody has any ideas about how to COMPLETELY format, and not get the boot loop? I can install any ROM fine, I just get stuck on the boot logo. Also, I tried the boot partition zip. Thanks in advance.
Turns out, because the keyboard was wonky, I couldn't ever get past the registering in 1.2 or 1.3, which for some reason, kept me in a boot loop after installing a different ROM. I guess, you either need to register, or bypass the Oout of Box Experience, in order to keep out of this boot loop. All fixed now!
Related
I originally was trying to flash CM7 using a SD bootable version of CWM 3.0.2.8 and it wouldn't boot at all. So, after a bit of searching, came to find out my refurbished Nook was one of the "new" ones with the partition change and was told that custom ROMs won't work on it yet.
I then got a CWM flashable 1.2 stock ROM and flashed it back to stock. Now, it won't boot past the N screen. I tried holding the power and N button to get into recovery to restore it, but that process freezes up half way through.
Next, I tried the 8 times boot interrupt (which is only 4 on my Nook btw) and it too freezes up part way through while "Clearing Data".
Any ideas on where to go next?
Nevermind, problem fixed. Whew, I went from having a Nook that wouldn't even power on this morning to a fully restored one.
Turns out I needed to have the power adapter plugged in while doing the 8 boot interrupt process.
I flashed CM7 RC1 this morning coming from an older version of phiremod. I formatted the system, data, and cache as usual. When I turn the nook on it gives me the Cyanogen splash screen with the loading text for a few seconds then goes to a black screen and stays there. If I try and boot into recovery it shows the Cyanogen splash screen with the booting recovery text and then also goes to the black screen and hangs.
I'm going to burn an sd card and try again with that when I get back from class, but does anyone have any ideas as to why this is happening?
Sounds like an incorrect kernel. Did you flash a kernel after RC1? You obviously have the right uboot so that isn't the issue.
Assuming you didn't flash an incorrect kernel then you probably just have a bad flash. I would re-download RC1 and try again.
I have installed Cyanogenmod on my MT4G, it was working fine for few months, but now it is developing a strange problem with the display. The symptoms include:
The screen is pixelated when displaying text, and colors are distored (at first a reboot took care of the problem, but now the problem no longer goes away)
No display of the myTouch 4G splash screen
When boot into recovery, I can see the recovery menu VERY briefly, then the screen goes dark, completely black
When boot into bootloader, the screen is completely blank. Can not see anything.
I was thinking the problem may caused by Cyanogenmod, however, because now the screen is completely blank, I can not even restore to stock using the Power+Volume down method. I do know that it still entered bootloader mood since I can see the device using adb/fastboot command.
Any pointer as to what may have caused this or help getting me restored back to stock would be greatly appreciated.
Note, I have wipe the phone, I have tried Cyanogenmod 7.1, nightly build 252 and 7.2RC1, and the problem is still there. I was not able to flash a stock rom using rom manager.
Last night after a good night of working with my tablet out on the job I came home and noticed it was running a little sluggish so I rebooted it. It then proceeded to hang on the bootloader screen. I tried flashing into recovery and wiping and reinstalling but it still stays hung up on the bootloader screen. Getting into the recovery boot loader it says the secondary kerlel akb has an issue or something. Is there a way to Odin this thing back to stock? It's not totally bricked I can still get into recovery just can't get it to boot into the second kernel or whatever it means. I can get the exact terminology if someone needs it but I have been bricked worse than this before its just weird it won't fix itself after I re install a new ROM.
Sent from my A100 using Tapatalk
I am on the Skillraz V8 boot loader to be exact, and thats the first screen it gets stuck on..
I just tried flashing a stock un rooted ics zip but it still hangs on the first screen after rebooting after the install, which seemed to take ok... and it doesnt change my recovery or anything back to stock.
So I was running CWM (Philz) I believe, and I had been running into issues while on rooted 4.2.2 D800 stock ROM. There were force closes and random reboots, etc. I've only installed xposed mods. I've also used android tuner to adjust some of the build.prop and kernel presets.
However, after my phone got stuck in what I thought was a boot loop, I finally got it up and running. What happened next was odd. I tried booting into recovery -> the "LG" splash screen showed up and it went into another infinite boot loop.
I'm assuming I somehow corrupted or lost my recovery. Any advice on what to do? I don't know if I should follow the original instructions for flashing a recovery here - http://forum.xda-developers.com/showthread.php?t=2633150.
Edit: Jesus christ my phone infuriates and confuses the hell out of me. After attempting to enter the recovery again, I am now stuck in a permanent boot loop. The last time I fixed it was by turning my phone off....and then *WAITING*.
What? That doesn't make sense you say? Of course it doesn't. But that's still what worked. I waited 12 hours, and then tried turning it on again. When I did, oh look, the AT&T screen!
CONFUSING. help please...
Double edit (Hard Mode): Going into download mode when I'm in this constant bootloop = nothing happens. That little icon that says "Download Mode" with the 5 blue circles just stays there, and my laptop ends up not recognizing anything. This happened the last time too, and all I was able to see on my laptop was "QHSUSB_BULK". I thought this meant that I would have to do a complete wiping process through Linux (found on another thread somewhere), but apparently waiting 12 hours also fixed the problem.