Related
I have flashed the new CyanogenMod and the Cyanogen Recovery 1.4 and when I wipe everything and flash, it'll load up and I can use the phone 100% perfectly, but once I reboot my phone, or turn it off and on, it never goes past the green boot screen. Anyone have any solutions/reasons why it does that? It's with every single Cyanogen mod too, i've tried several of them.
Probably because you have a lot of apps?
If not, reflash it.
tmc_adio07 said:
I have flashed the new CyanogenMod and the Cyanogen Recovery 1.4 and when I wipe everything and flash, it'll load up and I can use the phone 100% perfectly, but once I reboot my phone, or turn it off and on, it never goes past the green boot screen. Anyone have any solutions/reasons why it does that? It's with every single Cyanogen mod too, i've tried several of them.
Click to expand...
Click to collapse
what do you actually flash and what is the actual process, you shouldnt have any issues after it boots up the first time, wipe everything and make an exterior partition meaning get rid of your cyanogen recovery 1.4 and get amon ra's latest... look in the dev section and read up on cyan's page on how to flash the rom
mt3g said:
what do you actually flash and what is the actual process, you shouldnt have any issues after it boots up the first time, wipe everything and make an exterior partition meaning get rid of your cyanogen recovery 1.4 and get amon ra's latest... look in the dev section and read up on cyan's page on how to flash the rom
Click to expand...
Click to collapse
Thanks for help man, right now I'm running dwang's rom 100% perfect w/ no issues at all. it can reboot and everything just fine. I'm just a little worried on going back and trying to flash cyanogens.
When I installed it, I first did the root process, downloading the .apk file and going through all that part smooth, then I downloaded and flashed the Cyanogen Recovery 1.4, and from there I downloaded the two files (DRC83_base and the latest cyan's rom, i forgot the version #) and applied update from SD, first doing DRC83 and right after doing the rom itself, without rebooting the phone. It loads up A-OK and I can installl the apps and go about my business, but once I need to restart my phone, it just never turns back on. I'm puzzled completely...I even did the whole unroot and reroot thing and STILL i'm not having any luck.
K I got confused in there some where did you flash a cyan rom at all in there I read that you flashed the drc83 zip file but sounds like you just flashed that and booted the phone lol... never tried that but.... any way it seems like you are doing everything correct onlything I could suggest is make sure you have the correct htc base image, and make sure you wipe and repair everything!!!!! and also try a differant download of cyanogen as you might have gotten a bad one or something I have never had any issues with a cyanogen rom except maybe a FC back on 4.0xx or something
兄弟，估计你刷成砖了。同情ing。。
I'm completely new at this I just rooted my nook color today with Stable CM7. I wanted too overclock my nook so I flashed the kernel from this thread onto my device http://forum.xda-developers.com/showthread.php?t=1064095 now whenever I go to turn on my device it's a blank blackish screen. How would I get it back to how it was before I installed this (I must've done something wrong, I'm an idiot). I just tried to install the stock kernel from here http://forum.xda-developers.com/showthread.php?t=908515 but same thing is happening for me.
This exact problem happened to me today. I found some link to a stock 1.1 Nook Color software or something like that, got the Nook Color back to essentially factory settings, and then repeated the whole process of installing CM7, with the added step of installing the kernel along with the ROM and gapps.
Could you link me to this stock software you found?
Qerz said:
I'm completely new at this I just rooted my nook color today with Stable CM7. I wanted too overclock my nook so I flashed the kernel from this thread onto my device http://forum.xda-developers.com/showthread.php?t=1064095 now whenever I go to turn on my device it's a blank blackish screen. How would I get it back to how it was before I installed this (I must've done something wrong, I'm an idiot). I just tried to install the stock kernel from here http://forum.xda-developers.com/showthread.php?t=908515 but same thing is happening for me.
Click to expand...
Click to collapse
You used the wrong kernel. That one is apparently for rooted stock, not CM7.
Since your screen is black you might have to revert back to stock OS before reflashing CM7.
Can you boot into CWM from a SD? If so you can just try and redo the install procedure for CM7. This guide is recommended. (Also containing a link to a guide for reverting to stock, if needed...)
http://forum.xda-developers.com/showthread.php?t=1030227
Alright I'm going to try to re-flash CM7. Thanks bro.
Well I reinstalled CM7 and when I pressed 'reboot system now' in CWM it just takes me back to CWM so I'm still lost. Going to try to install stock now.
_
Ok I installed stock now and it seems to be working, but It's just stuck at a screen saying 'contains Reader Mobile technology by Adobe Systems Incorporated.' and then the nook symbol in the center of the screen. It could just be loading but it's been 3-5 mins atleast so idk.
Yeah it's not going past that screen where it says 'contains Reader Mobile technology by Adobe Systems Incorporated.' not sure if I should try rebooting though. I tried going into recovery mode and get 'Install failed' so I tried installing again but same results.
I got my nook working with cm7 again, thank you for the help!
weird, my mom called me last night with the same issue. will see it today to see what it was.
Just to add on to the part where you said it took you back to CWM after reboot (for anyone who might come here for answers), you have to take the SD card out before you reboot.
I was running on a rooted 3.1 with tiamat 1.7 overclock
What I did was:
tried to follow [UPDATE][US WIFI ONLY]Android 3.2 on Xoom WiFi, Root, via ClockworkMod Recovery
then I did this: Note also if you are coming over from a custom ROM, wipe your cache partition (under main menu) and dalvik cache (under Advanced) in ClockworkMod Recovery prior to performing the following steps.
next I applied the 3.2 update
Now Im stuck in the boot animation.
From what I understand Im getting this because I was not on the stock kernel, can anybody help me fix this and get me to 3.2
Thank you
download the stock images here http://forum.xda-developers.com/showthread.php?t=1080963
and flash via fastboot, this will get you out of the boot loop, i had the same issue
should I try and flash the 3.2 or the 3.1 given my current situation?
If you made a backup in cwm just restore it. If not, I would say go back to the beginning and flash stock 3.0. If you plan on rooting unlock the bootloader right then. Setup the Xoom, connect to wifi and take the 3.1 ota update. Setup and connect to wifi again and wait a bit to see if 3.2 ota update notification appears. If it does, take it and root it (see my guide in dev section). If it does not pop up, you can update manually (see bauxite's guide in dev section) then root. This way you should have no issues. I know it sounds like a lot to do, but it all should take you less than hour. I did one for a friend and it took me 34min to do everything. After your rooted you can restore apps with titanium if you have made and saved the backups. Good luck.
Sent from my HD2
jase33 said:
If you made a backup in cwm just restore it. If not, I would say go back to the beginning and flash stock 3.0. If you plan on rooting unlock the bootloader right then. Setup the Xoom, connect to wifi and take the 3.1 ota update. Setup and connect to wifi again and wait a bit to see if 3.2 ota update notification appears. If it does, take it and root it (see my guide in dev section). If it does not pop up, you can update manually (see bauxite's guide in dev section) then root. This way you should have no issues. I know it sounds like a lot to do, but it all should take you less than hour. I did one for a friend and it took me 34min to do everything. After your rooted you can restore apps with titanium if you have made and saved the backups. Good luck.
Sent from my HD2
Click to expand...
Click to collapse
You probably should wipe user data in recovery along with the caches. That's what got me out of the bootloop and into the updated stock 3.2.
i flashed the stock images from the first link provided via fastboot and it worked perfect, the thread said you can flash from whatever to whatever by using those images so i flashed 3.2 and it fixed everything. Took about 5 minutes to do, I wonder if this way will give me problems when I try to root (pretty sure I lost root) but everything now seems to work fine
Hi,
I had the same issue. i fix by going back in cwm making factory reset and install again the same image.
after the first reboot i restored soft with titanium and all working good.
Tomate2K8 said:
Hi,
I had the same issue. i fix by going back in cwm making factory reset and install again the same image.
after the first reboot i restored soft with titanium and all working good.
Click to expand...
Click to collapse
Yep, that's the easiest solution, but whatever works!
I just tried to flash Tiamat 2.0 and the boot image with it (I followed the directions and did them in the correct order), and it's now stuck at the Motorola boot screen (not the animation). Any suggestions? I'm not sure how to get back in to CWM now.
Edit: Managed to get in to CWM, did a factory/data reset and wiped cache before re-flashing. Still stuck on the boot screen.
i updated my aussie telstra xoom 3g to tiamat 2 (3.2) and booted fine but did not see 3g, so i used a bul.prop from 3.1 and got the bootloop prob, rebooted to recovery and did wipe erase, when it booted up again tried the euro build.prob and all worked, i suspect the issue relates to buil.prop so a bit of tinkering will always win in the end, bassically these things seem to be bullet proof when it comes to screwing summin up
phekno said:
I just tried to flash Tiamat 2.0 and the boot image with it (I followed the directions and did them in the correct order), and it's now stuck at the Motorola boot screen (not the animation). Any suggestions? I'm not sure how to get back in to CWM now.
Edit: Managed to get in to CWM, did a factory/data reset and wiped cache before re-flashing. Still stuck on the boot screen.
Click to expand...
Click to collapse
What HC version were you on when you flashed 2.0? I'm just wondering if you needed to flash the boot image. It's hard to help you if we don't know what configuration you are coming from. Also Is your Xoom US wifi or 3G or Euro wifi or 3G?
zbee said:
i updated my aussie telstra xoom 3g to tiamat 2 (3.2) and booted fine but did not see 3g, so i used a bul.prop from 3.1 and got the bootloop prob, rebooted to recovery and did wipe erase, when it booted up again tried the euro build.prob and all worked, i suspect the issue relates to buil.prop so a bit of tinkering will always win in the end, bassically these things seem to be bullet proof when it comes to screwing summin up
Click to expand...
Click to collapse
Yeah, they really are almost bullet-proof. Good thing too, seeing all the abuse they have to take.
: )
okantomi said:
What HC version were you on when you flashed 2.0? I'm just wondering if you needed to flash the boot image. It's hard to help you if we don't know what configuration you are coming from. Also Is your Xoom US wifi or 3G or Euro wifi or 3G?
Click to expand...
Click to collapse
My fault, I guess some information would have been helpful. The Xoom is a US WiFi version and I was running 3.1 when I started this, which I now realize was probably really stupid. I should have probably gotten 3.2 on there before I started. Is there a way to update to 3.2 at this point? Or do I need to go back to stock and start over?
I appreciate the help.
Edit: Or should I just install another ROM per these directions.
phekno said:
My fault, I guess some information would have been helpful. The Xoom is a US WiFi version and I was running 3.1 when I started this, which I now realize was probably really stupid. I should have probably gotten 3.2 on there before I started. Is there a way to update to 3.2 at this point? Or do I need to go back to stock and start over?
I appreciate the help.
Edit: Or should I just install another ROM per these directions.
Click to expand...
Click to collapse
Are you rooted? If so, you can flash the Tiamat Xoom Rom 1.1 which is for 3.1. You don't need to flash any additional kernel. You can get it from the appropriate thread in Development. You will probably have to do a full wipe in CWM Recovery (user data, cache).
From there, you can flash the Team Tiamat Xoom Rom 2.0 Manta Ray right on top of the Rom 1.1, no wipe needed. That should get you the HC3.2 update, preserve your root, and give additional functionality. I love it. I updated in a more roundabout method...I could have done it this way if I had waited...
If you are not rooted, you need to root first..see any one of the guides to root in HC3.1.
Good luck!
okantomi said:
Are you rooted? If so, you can flash the Tiamat Xoom Rom 1.1 which is for 3.1. You don't need to flash any additional kernel. You can get it from the appropriate thread in Development. You will probably have to do a full wipe in CWM Recovery (user data, cache).
From there, you can flash the Team Tiamat Xoom Rom 2.0 Manta Ray right on top of the Rom 1.1, no wipe needed. That should get you the HC3.2 update, preserve your root, and give additional functionality. I love it. I update in a more roundabout method...I could have done it this way if I had waited...
If you are not rooted, you need to root first..see any one of the guides to root in HC3.1.
Good luck!
Click to expand...
Click to collapse
Yeah, I was rooted before all of this. I had done a full wipe in CWM and then did the boot/kernel and now I'm here. I think I should have just done the Tiamat Xoom Rom 2.0 in stead. Can I just flash the 2.0 ROM over what's on there now?
Edit: Now, I can't seem to get in to CWM. I'm not really sure how to other than using adb reboot recovery, but windows isn't picking up the device now.
Edit #2: I got back in to CWM. I'm running CWM 3.0.2.5, FYI.
I just flashed Tiamat Xoom Rom 1.1 and now it's back up and running. Thanks a ton for helping! I'll probably be putting 2.0 on there pretty quickly.
phekno said:
I just flashed Tiamat Xoom Rom 1.1 and now it's back up and running. Thanks a ton for helping! I'll probably be putting 2.0 on there pretty quickly.
Click to expand...
Click to collapse
Great! Have fun with it. I think you'll love it.
I have a problem restoring my xoom to stock.
I flashed the Katana OC kernel onto my Wifi Only US Xoom with 3.2. I oc'd to 1.5 ghz and it worked fine. Then I left it on during the night. When I woke up the next morning it was stuck in a boot loop, so I though maybe I should flash the Katana without OC instead. That I tried but It got stuck halfway through (Maybe I should have waited longer...).
After this the xoom wouldnt boot (not that surprising..) so I flashed it back to stock with the official Motorola images. However the Xoom still wont boot up, gets stuck either on Moto logo or on the Honeycomb boot screen.
When I flash the 3.2 images and a custom kernel (Tiamat 2.0) then I can get into Android but it stops responding after a few minutes.
The Xoom seems to be running good before it freezes, I cant find a solution to get my Xoom back to life.
Any ideas?
blee00 said:
I have a problem restoring my xoom to stock.
I flashed the Katana OC kernel onto my Wifi Only US Xoom with 3.2. I oc'd to 1.5 ghz and it worked fine. Then I left it on during the night. When I woke up the next morning it was stuck in a boot loop, so I though maybe I should flash the Katana without OC instead. That I tried but It got stuck halfway through (Maybe I should have waited longer...).
After this the xoom wouldnt boot (not that surprising..) so I flashed it back to stock with the official Motorola images. However the Xoom still wont boot up, gets stuck either on Moto logo or on the Honeycomb boot screen.
When I flash the 3.2 images and a custom kernel (Tiamat 2.0) then I can get into Android but it stops responding after a few minutes.
The Xoom seems to be running good before it freezes, I cant find a solution to get my Xoom back to life.
Any ideas?
Click to expand...
Click to collapse
Have you done a full wipe user data/factory reset in CWM recovery? You may need a clean slate to proceed.
Also, do you know if debugging is set to on? If you can't boot you can't get into settings but that could prevent you from accessing your Xoom from your pc.
okantomi said:
Have you done a full wipe user data/factory reset in CWM recovery? You may need a clean slate to proceed.
Also, do you know if degugging is set to on? If you can't boot you can't get into settings but that could prevent you from accessing your Xoom from your pc.
Click to expand...
Click to collapse
Thanks for your reply! =)
I have done the "Wipe user data/factory reset" in CWM, If I do that I usually can boot Honeycomb, but I rarely get past the setup wizard (although sometimes I do), but then after a few minutes it freezes again.
Also, I can access my Xoom through ADB.
hey i just attempted to root my wife's nook color, 1.3, using this method http://forum.xda-developers.com/showthread.php?t=1054027
i have made the boot disk and pushed both nooter zips to disk, cwm comes up and it runs both zips just fine, ive tried both one after other ten reboot, reboot in between, wipe dalvik and the run but i always get stuck in the boot loop
can anyone tell me what im doing wrong here
and the plot thickens... so i did the 8 failed manual reset, and rebooted to stock, repeated process.. im out of bootloop but it appears the touch screen doesnt work anymore???
yeah so no matter how many times i 8 fail reset still no touch screen, all other buttons work, tried reinstalling clockwork and nothing...i bought the insurance, do i need to run it over cause im outta ideas, my first thought was ui was missing file but it should go back if i reset shouldnt it???
just shoot me..please
ok back to stock, re root, boot loop again, re stock , cm7 (update-cm-7.1.0-encore-signed) + gapps (gapps-gb-20110307-signed) and now application setup wizard has stopped unexpectedly.....stuck...thoughts? please am i over thinking/looking something
day two...
i created sd boot img with cwm 3.2.08, im seeing that i need to use cwm 3.2.01 in a few places.. when i get the file from clockwork (recovery-clockwork-3.2.0.1-encore) and try to write the image to the sd card something is wrong, its not a format that the windows recognizes and so i cant add zips to it and i get nothing in the nook. ive tried to reformat from the pc and in an old android phone i have but its always the same when i try to write to sd , is this the wrong image, can i find it somewhere else
i am using same 8gb sd card i made first boot disk out of, do i need to use a new one??
i got it to work i have good cwm 3.2.01 on nook...
stock + root?
ok it seems that cwm 3.2.0.8 was definitely my problem, i switched to recovery-clockwork-3.2.0.1-encore which i got from http://tinyw.in/0Vw
problem remains that when i flash man nooter 18 then 16 i get nothing, I was stuck on "n" load screen not even a boot loop
i then pushed cm7 again and i am operating as a full android tablet, i want the stock nook image with gapps can anyone help.. im leaving be till i get a answer, didnt want to update to 1.4 or downgrade to 1.2 havent seen a stock img of 1.3 anywhere
Nook color running Racks triple boot via micro SD card. Micro SD card is a Sandisk 8GB class 4 card.
Was previously running fine for many months with the 2/2/12 roms. I would run CM7 99% of the time and I would get a random reboot here and there, but otherwise very stable.
A couple days ago, I had a random crash and tried to reboot CM7. I could get passed the boot loader screen, but then would have a continuous boot loop with the blue android symbol.
Thinking something was corrupted with the rom, I booted to recovery and tried flashed the rom along with gapps. Still boot looping.
I booted to CM9, and was able to run. So I downloaded the latest CM7 and CM9 roms for Racks triple boot. Flashed both along with the gapps and CM9 fix. Apparently I got lucky and was able to boot into CM7.... once. Thinking everything was OK, I went on with my life and ran the new CM7 happily.
Now, a few days later, I've tried to reboot and I'm back at the same boot loop with the arrow spiraling around the a blue skateboarding android. Note, in that short time that I was running the newest Racks triple boot CM7 rom, I did not run a backup, so, I'm basically out of luck with recovery via CWM.
I've flashed the 2/2/12 rom as well as the latest rom to see if either would work again. nothing... still boot looping... for hours now.
Any suggestions other than wiping the SD clean and starting with a fresh install?
Thanks all.
~mike
Bump...
Been a bit, no responses yet. Anyone have any ideas?
Thanks,
~mike
I think the fresh install will help since you already tried partial reinstalling the roms.
Produced by NookColor at ICS AOKP 4.0.4
Nook Color stuck in load screen
I have a nook with CM7 installed on it. was going return my nook to stock to give it to my little sister, but when i went to install the stock stuff back on it got stuck in a loop. It won't boot from an uSD card with clockwork on it and when I tried the 7 hard boot in a row trick, it didn't do anything. Did i really brick the thing? or can it be recovered?
doodlebug81 said:
I have a nook with CM7 installed on it. was going return my nook to stock to give it to my little sister, but when i went to install the stock stuff back on it got stuck in a loop. It won't boot from an uSD card with clockwork on it and when I tried the 7 hard boot in a row trick, it didn't do anything. Did i really brick the thing? or can it be recovered?
Click to expand...
Click to collapse
You are in a recovery bootloop with no recovery installed. Go to my tips thread linked in my signature. Read item A8. You need to make and use my special bootable CWM SD (select the 'larger' image). Then if you want to return to stock, read item A15.