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。。
Hey guys i know "Help!" threads get annoying (at least in the Fascinate forum they do.) but i could really use some help.
Rooted my friends phone today (root,clockwork,rom manager), and was going to install regular JAC kernal /voodoo w/o color fix.. I made sure the phone had the smaller NAND chip. Installation went fine (phone booted, voice told me it was switching to ext. 4.) and the voice said voodoo was complete. The phone was stuck at the S logo for about an hour and it was then i decided voodoo was botched. From there i rebooted to clockwork and went to restore the nandroid i made when i rooted. The nandroid got stock at one of the Data files for about 30 minutes. (i have a feeling this is around where i messed things up myself) Decided screw it and was going to flash JI6(T959UVJI6) and the stock kernal with ODIN. Now the phone boots past the S logo but the screen stays black and only the backlight menu buttons light up. It wont go past there. Any quick help is appreciated.
You didn't disable the lagfix I'm assuming.
Odin Eugene's Froyo that doesn't brick, then Odin JFD, install ROM of you're choosing.
Did you even try to search for a fix before posting???
~SB
problem0atique said:
Hey guys i know "Help!" threads get annoying (at least in the Fascinate forum they do.) but i could really use some help.
Rooted my friends phone today (root,clockwork,rom manager), and was going to install regular JAC kernal /voodoo w/o color fix.. I made sure the phone had the smaller NAND chip. Installation went fine (phone booted, voice told me it was switching to ext. 4.) and the voice said voodoo was complete. The phone was stuck at the S logo for about an hour and it was then i decided voodoo was botched. From there i rebooted to clockwork and went to restore the nandroid i made when i rooted. The nandroid got stock at one of the Data files for about 30 minutes. (i have a feeling this is around where i messed things up myself) Decided screw it and was going to flash JI6(T959UVJI6) and the stock kernal with ODIN. Now the phone boots past the S logo but the screen stays black and only the backlight menu buttons light up. It wont go past there. Any quick help is appreciated.
Click to expand...
Click to collapse
If you can still boot into clockwork recov. you can save it by pushing the undo voodoo zip file that was mentioned about. Assuming that u have adb access. If not odin froyo that doesnt brick tepartition checked. Turn off. Boot back in download. Odin stock jdf. Ji6 isnt a standalone rom. Its more like a no wipe update. Lucky his vibrant wasnt hardware locked lol. He will have a 90% chance of losing EVERYTHING
Had to odin flash froyo that doesnt brick then jfd and yep he lost all his data but he didnt have much to begin with. Now happily running Fusion. Thanks for the help guys!
Hey folks, I'm hoping one of you can help me out with an issue that just cropped up on my phone. I've been running EB01 since it's release and have had no issues whatsoever except for today when I noticed my apps (Titananium Backup, Tapatalk, Root Explorer) we're remembering preferences anymore and/or every time I exit from them and launch again....it thinks it's the first run again.
Did something hose up my permissions/ownerships? Only think I did recently was flash the de-binged browser via CWM.
Any ideas??
What are you running? It may be a permissions problem. Have you tried uninstalling it and reinstalling it?
I'm having a similar issue. Help!
jpolzner said:
Hey folks, I'm hoping one of you can help me out with an issue that just cropped up on my phone. I've been running EB01 since it's release and have had no issues whatsoever except for today when I noticed my apps (Titananium Backup, Tapatalk, Root Explorer) we're remembering preferences anymore and/or every time I exit from them and launch again....it thinks it's the first run again.
Did something hose up my permissions/ownerships? Only think I did recently was flash the de-binged browser via CWM.
Any ideas??
Click to expand...
Click to collapse
I was just about to start a thread about this. I'm having the same problem. I upgraded from blackhole 4.1 (DL30) to Superclean 2.2 EB01 with voodoo lagfix. I got the red CWM flashed via odin and proceeded to install the EB01 modem and the superclean 2.2v (EB01).
The first time I flashed was a disaster, there were issues with Odin completing the flash, so I had to do USB pulls about 4 times (which ended up giving me full "light blue" screens during download mode at times).
After getting Odin to cooperate, I was able to flash the Superclean 2.2v (EB01), and then I restored everything from Titanium Backup, which worked fine until I restarted the phone or left it alone for a couple of hours. Everything would force close (like ADWLauncer Ex, forcing me to use ONLY TWLauncher) and all my preferences were lost. Like gmail would have to resync as if it were new, all the EULA dialogs would come up (like in android market), my trillian profiles were all lost, if i turned off haptic feedback that would turn back on, my ringtones would go back to the defaults, etc.
So I read some other thread in the Development section which said to reflash, and do not do any restores at all. So I reflashed with Super clean 2.3v (EB01), but it happened again, all my preferences would be lost. I also tried to do "fix permissions" from RED CWM, but it just ran for like a fraction of a second and didn't seem like it did anything, as the problem persisted.
I'm planning to go back to DL30 or even DL09 to see if my phone functioned properly or not.
If anyone has a solution to this problem please help!
- Superclean 2.3v (EB01)
I'm thinking it has something to do with flashing either the De-Binged browser or the new market update. Maybe something in the framework-res is getting hosed up?
I just did a wipe and reflashed plain old EB01 and I'm not going to flash any changes and see if the problem comes up again.
emortio said:
I was just about to start a thread about this. I'm having the same problem. I upgraded from blackhole 4.1 (DL30) to Superclean 2.2 EB01 with voodoo lagfix. I got the red CWM flashed via odin and proceeded to install the EB01 modem and the superclean 2.2v (EB01).
The first time I flashed was a disaster, there were issues with Odin completing the flash, so I had to do USB pulls about 4 times (which ended up giving me full "light blue" screens during download mode at times).
After getting Odin to cooperate, I was able to flash the Superclean 2.2v (EB01), and then I restored everything from Titanium Backup, which worked fine until I restarted the phone or left it alone for a couple of hours. Everything would force close (like ADWLauncer Ex, forcing me to use ONLY TWLauncher) and all my preferences were lost. Like gmail would have to resync as if it were new, all the EULA dialogs would come up (like in android market), my trillian profiles were all lost, if i turned off haptic feedback that would turn back on, my ringtones would go back to the defaults, etc.
So I read some other thread in the Development section which said to reflash, and do not do any restores at all. So I reflashed with Super clean 2.3v (EB01), but it happened again, all my preferences would be lost. I also tried to do "fix permissions" from RED CWM, but it just ran for like a fraction of a second and didn't seem like it did anything, as the problem persisted.
I'm planning to go back to DL30 or even DL09 to see if my phone functioned properly or not.
If anyone has a solution to this problem please help!
- Superclean 2.3v (EB01)
Click to expand...
Click to collapse
I'm having the exact same problem. I've been all the way down to DJ05 to see what happens, and when I come back to superclean 2.2 voodoo-ed, I get force closes on everything the first time I restart - that issue was due to the new feature froyo added "automatic restore" in settings > privacy. I got that taken care of by uninstalling all apps.
However, when I restart now, my entire phone defaults back to cleared data. I'm talking every setting that I could think of (usb debugging, sound, brightness, contacts, security pin cleared). I don't get it at all. Everything else has been working right though.
Just thought I would share - I'm kinda still in limbo till I figure out what I should do.
brettdacosta said:
I'm having the exact same problem. I've been all the way down to DJ05 to see what happens, and when I come back to superclean 2.2 voodoo-ed, I get force closes on everything the first time I restart - that issue was due to the new feature froyo added "automatic restore" in settings > privacy. I got that taken care of by uninstalling all apps.
However, when I restart now, my entire phone defaults back to cleared data. I'm talking every setting that I could think of (usb debugging, sound, brightness, contacts, security pin cleared). I don't get it at all. Everything else has been working right though.
Just thought I would share - I'm kinda still in limbo till I figure out what I should do.
Click to expand...
Click to collapse
I wonder if it has to do with the type of EB01 we're using or the CWM. I flashed CWM red via Odin, rather than updating via Rom Manager or update.zip. Also I used the EB01 Walkthrough in the fascinate developers section, the link is:
http://forum.xda-developers.com/showthread.php?t=948722
***UPDATE***
I resolved the problem... I think. I noticed there was a difference in the file names of the EB01 Modem in the walkthrough link I provided on the last line of the paragraph above and the EB01 Modem given in the original EB01 stock thread (http://forum.xda-developers.com/showthread.php?t=948679). I flashed with the eb01a_modem.tar given in the stock thread and then upgraded to Super Clean with Voodoo (v. 2.4 as of this writing). The market DID restore all the apps, before I was able to stop it, but after I restarted, there were no force closes nor were there any loss of preferences. I hope the modem issue was what was wrong...
Started doing it again this morning. This time I did not flash any mode via ROM Manager. Only things I did was de-bloat using Root Explorer and Titanium Backup.
Not every app started forgetting preferences, some still reemebered. Any of the devs have an idea of what's going on here? I'm running the plain old, fully-bloated EB01 ROM. No voodoo, no de-odexed, or anything like that.
I think it's a dbdata partition issue. I can't say how to fix because it's above my paygrade, but you may have to wait until it is officially released.
jpolzner said:
Started doing it again this morning. This time I did not flash any mode via ROM Manager. Only things I did was de-bloat using Root Explorer and Titanium Backup.
Not every app started forgetting preferences, some still reemebered. Any of the devs have an idea of what's going on here? I'm running the plain old, fully-bloated EB01 ROM. No voodoo, no de-odexed, or anything like that.
Click to expand...
Click to collapse
Try the Odin back to stock...DI01, wipe everything. Reroot and and get cwm. Then ODIN EB01 Modem Tar followed by super clean 2.4 install through cwm. Be sure to wipe data and cache before flashing super clean.
I there a reason I have to go all the way back to DI01, or can I use any All-In-One Odin package that writes the ROM, Kernel, & Radio?
jpolzner said:
I there a reason I have to go all the way back to DI01, or can I use any All-In-One Odin package that writes the ROM, Kernel, & Radio?
Click to expand...
Click to collapse
I suggest that typically before anything else b/c it seems to help most. I've never experienced these issues but many suggest this is a viable method to remedy certain problems. Don't see why you couldn't try the odin DL09 all-in-one and wipe the hell out of it and try again. Good Luck.
Is the corruption in the dbdata partition caused by an older version of CWM or a problem in the EB01 ROM itself?
Is it safe to go back to EB01?
jpolzner said:
Is the corruption in the dbdata partition caused by an older version of CWM or a problem in the EB01 ROM itself?
Is it safe to go back to EB01?
Click to expand...
Click to collapse
I believe it's currently inconclusive. There is speculation about exactly what causes it hence the reason I suggest wiping everything and then flashing the most recently provided stuff. That way it'll narrow things down. Someone can correct me, but if you odin back to stock, I'm 99% sure super cleans 2.4 voodoo kernel includes the new cmw. I was on green cmw unitl I flashed the seperate voodoo kernel posted by jt. I haven't had any issues.
Its almost certainly dbdata corruption. The cause is...yeah questionable. Seems most common with voodoo with the current hack being used to get it working with froyo.
Sent from my SCH-I500 using XDA App
I've never run Voodoo on my phone, but I did my initial install of EB01 with one of the older "Green" CWM versions.
adrynalyne said:
Its almost certainly dbdata corruption. The cause is...yeah questionable. Seems most common with voodoo with the current hack being used to get it working with froyo.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Any other suggestions or fixes?
I went all the way back to DI01, then flashed to EB01 using an Odin All-In-One and now 48-72 hours later, my apps (most notably Tapatalk, Root Explorer, and Titanium Backup) think it's the first time they've run every time I launch it.
Shouldn't have going back to DI01 fixed the corruption since it reformats the ROM partition? Also, something I notice was that flashing to DI01 or EB01 using odin did not get rid of the new CWM Recovery.
Would running the permission fix correct the issue?
jpolzner said:
Any other suggestions or fixes?
I went all the way back to DI01, then flashed to EB01 using an Odin All-In-One and now 48-72 hours later, my apps (most notably Tapatalk, Root Explorer, and Titanium Backup) think it's the first time they've run every time I launch it.
Shouldn't have going back to DI01 fixed the corruption since it reformats the ROM partition? Also, something I notice was that flashing to DI01 or EB01 using odin did not get rid of the new CWM Recovery.
Would running the permission fix correct the issue?
Click to expand...
Click to collapse
No...are you running voodoo? And what rom are you using?
EB01 Fully Bloated, Non-Voodoo Kernel
Baseband version: S:i500.04.V.EB01
Kernel version: 2.6.32.9
Build number: SCH-I500.EB01
http://forum.androidcentral.com/ver...roms-w-root-new-clockwork-updated-2-15-a.html
Try This...
This will hopefully repartition and clean dbdata corruption. BTW, I couldn't get 2.2 to run on my phone until I odin flashed a ROM which allowed me to then flash Adrynalyne's 2.4.
DI01, DJ05, DL09 did not work for the fix. Eclair worked fine, but Froyo would not work until I flashed a 2.2 odin.
Do I need to check the "Re-Partition" option in Odin when flashing or does it do it automatically?
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 seem to have encountered a rather unusual issue with my nandroid back up. I was planning on flashing CM7 to test it out, and then after my test return to my backup. CM7 worked like a charm, but I was going to wait until I had more time on my hands to fully explore the rom, so I decided to do a nandroid restore using Clockwork Mod 3.0.2.4. It worked... sort of. After the restore, I rebooted. It brought me to my normal unlock screen, but when I unlocked it, I was presented with the MT4G initial setup, as if I had done a restore with the stock img. I knew my data is still in there, because it remembered little things, like my initial lock screen, my wifi settings and a couple of other things. I went hunting through a couple of forums, and found that the MT4G has issues when using clockwork 3.0.2.4 to flash non-Gingerbread, and that you ought to use clockwork 2.5.1.2. Thinking that may have been my problem, I tried, and it then told me there was a MD5 mismatch. I followed the recommendations found in this post http://forum.xda-developers.com/showthread.php?t=976453 for finding and correcting mismatched MD5s (the data.img file was the one with the mismatch if that helps). Now it flashed properly, but resulted in the same problem I had earlier... after reboot, I am presented with my lock screen, but then taken through the MT4G setup. I have a TI backup, so I'm not really worried, but, I am curious if anyone can shed some light on what happened to my restore so that it doesn't happen in the future, and so that if someone else has this problem, they can have it a little easier than I have.
Thanks in advance for your help,
WestBC
Any thoughts!
Basically, stick with froyo or GB. Don't jump back and fourth.