Hey guys, I just need to know how far up **** creek without a paddle I am and how I got here. I had a stock JF6, a friend told me to root with unleash the beast so I did. Been running great and aside from using metamorph to install a few swype themes and nav bar themes, it was stock. I had managed to learn a bit and heard clockwork mod was a great thing, and was making backups regularly.
Well since everything was going so well, I decided to dig deeper and install cognition 2.1. Things went fine, until I got to first boot, then I realized all my stuff was gone, should have known and me being changed my mind. So I went and booted into recovery, and tried to restore my most recent backup, well of course it failed when it came to data because cognition had formatted it.
Well after a lot of formatting data/cache, I tried to install the cognition 2.1.zip, got an error message.. Failed to install. After rebooting I was stuck in the att white screen boot loop. So once again formatted data, and this time I ran update.zip(unleash the beast).
HERES my question, now I seem to have some kind of hybrid, on first boot of cognition I got the custom boot sounds and wallpaper. Nothing now, however my baseband is now JH7, and it says something about voodoo lag fix. But still says 'beast .... Teaser' for system info.
I'm so confused, what's the best way for me to get a stable version of cognition running? Ill just install all my data, I just wabt to know exactly what my phone is running.
Sent from my SAMSUNG-SGH-I897 using XDA App
Best bet is to flash back to JF6, root, install ROM Manager, and load Cognition from that.
Also, that question its better suited for q&a, not the dev forum
Sent from my SAMSUNG-SGH-I897 using XDA App
sdotbrucato said:
Best bet is to flash back to JF6, root, install ROM Manager, and load Cognition from that.
Also, that question its better suited for q&a, not the dev forum
Don't forget to disable lagfix before you Odin.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I897 using XDA App
Sorry, I just mainly check here and the themes and apps section.. Completely forgot about the other ones.
So if I wanted to flash back to jf6.. Would I just get one of these stock dumps floating around and flash it? Or is there a better way?
Sent from my SAMSUNG-SGH-I897 using XDA App
Use the Odin One Click that's posted at the top of this forum. It will flash you back to stock in a matter of seconds.
Sportsguy15 said:
Use the Odin One Click that's posted at the top of this forum. It will flash you back to stock in a matter of seconds.
Click to expand...
Click to collapse
THANK YOU.
this is what I needed to know. So basically, odin one click, use any method to root (probably just use a one-click this time), and then download rom manager and install cognition from clockworkmod? and thats all it would take?
Much easier then what I had in mind.
bamathrasher said:
THANK YOU.
this is what I needed to know. So basically, odin one click, use any method to root (probably just use a one-click this time), and then download rom manager and install cognition from clockworkmod? and thats all it would take?
Much easier then what I had in mind.
Click to expand...
Click to collapse
Yep, that's all you need to do. I've started doing that any time I flash a new rom, ie, One-click to stock, root, rom manager, flash new rom.
I have had similar issues when I try to flash over an existing rom, plus it is nice to start with a fresh rom, no bugs.
bobbylx said:
Yep, that's all you need to do. I've started doing that any time I flash a new rom, ie, One-click to stock, root, rom manager, flash new rom.
I have had similar issues when I try to flash over an existing rom, plus it is nice to start with a fresh rom, no bugs.
Click to expand...
Click to collapse
Data on ext4 survives an Odin flash, so if you are on voodoo, it's a bit more involved than just flashing.
rajendra82 said:
Data on ext4 survives an Odin flash, so if you are on voodoo, it's a bit more involved than just flashing.
Click to expand...
Click to collapse
I saw something like this in the Cognition thread, about creating a file called "disable-lagfix" or something and placing it on the root of the sd. Is that the extra step you are referring too, and if so, I definitely need to do this?
bamathrasher said:
I saw something like this in the Cognition thread, about creating a file called "disable-lagfix" or something and placing it on the root of the sd. Is that the extra step you are referring too, and if so, I definitely need to do this?
Click to expand...
Click to collapse
Yes. That's the correct method to put /data back on RFS. Once you have created the file and rebooted, a robotic lady will inform you that the /data is being converted. Once this boot finishes, you are at a point where Odin or Clockwork will be able to help you. When /data is in ext4 format, the other programs don't recognize it, and don't work properly.
just for future reference, what type of data are you talking about here? I have no data I'd like to keep at this point, after I bricked my phone last night, I basically tried everything in clockworkmod until I got it back to a workable state so I'd have a phone to use today at work. How am I supposed to make it through a work day without being able to text? its impossible. haha.
So if I have no data I desire to keep, is this necessary or is this a different type of data, important data for the system?
bamathrasher said:
just for future reference, what type of data are you talking about here? I have no data I'd like to keep at this point, after I bricked my phone last night, I basically tried everything in clockworkmod until I got it back to a workable state so I'd have a phone to use today at work. How am I supposed to make it through a work day without being able to text? its impossible. haha.
So if I have no data I desire to keep, is this necessary or is this a different type of data, important data for the system?
Click to expand...
Click to collapse
If you noticed in my post I did not say data but /data. There is a difference.
On your Captivate there is a total of 16 GB of internal memory. The memory is partitioned into several block devices. One of these partitions is mmblk0p4, which once booted, is mounted to /data. This directory stores your apps installed from market, your user information, your call log, your text messages, and so on. It has to be working for your phone to boot up properly. Although /data looks like a directory, since it is a link to an actual device, it can be on its own file system which is different than other devices mounted to other directories. On a default Captivate (i.e., before you install Cognition, which includes a choice of two voodoo lagfix kernels) the block device mmblk0p4, mounted as /data is formatted in a proprietary Samsung RFS file system, which is too slow. When you install the voodoo kernel, on first boot, it formats the device in a much faster ext4 file system if there is no file or folder called disable-lagfix in /sdcard/voodoo, thus severely reducing the lag. The problem is that the default kernel, the recovery mode kernel, and the Odin flasher program understand how to deal with this device formatted in RFS. If your block device is in ext4 and you restore the system through Odin, you will end up with Odin not wiping off the contents of /data, which is what you actually wanted. I am not sure if you end up with a working /data device in RFS and a chunk of unused ext4 information, or a kernel not understanding /data in ext4 and hanging. If you are in this state, your best bet is to flash on a voodoo kernel through Odin, which will then understand the ext4 /data. Once the voodoo kernel boots, you then create the disable-lagfix file and reboot, to get /data back in RFS. Then you go into download mode, and wipe the /data on RFS with Odin.
rajendra82 said:
If you noticed in my post I did not say data but /data. There is a difference.
On your Captivate there is a total of 16 GB of internal memory. The memory is partitioned into several block devices. One of these partitions is mmblk0p4, which once booted, is mounted to /data. This directory stores your apps installed from market, your user information, your call log, your text messages, and so on. It has to be working for your phone to boot up properly. Although /data looks like a directory, since it is a link to an actual device, it can be on its own file system which is different than other devices mounted to other directories. On a default Captivate (i.e., before you install Cognition, which includes a choice of two voodoo lagfix kernels) the block device mmblk0p4, mounted as /data is formatted in a proprietary Samsung RFS file system, which is too slow. When you install the voodoo kernel, on first boot, it formats the device in a much faster ext4 file system if there is no file or folder called disable-lagfix in /sdcard/voodoo, thus severely reducing the lag. The problem is that the default kernel, the recovery mode kernel, and the Odin flasher program understand how to deal with this device formatted in RFS. If your block device is in ext4 and you restore the system through Odin, you will end up with Odin not wiping off the contents of /data, which is what you actually wanted. I am not sure if you end up with a working /data device in RFS and a chunk of unused ext4 information, or a kernel not understanding /data in ext4 and hanging. If you are in this state, your best bet is to flash on a voodoo kernel through Odin, which will then understand the ext4 /data. Once the voodoo kernel boots, you then create the disable-lagfix file and reboot, to get /data back in RFS. Then you go into download mode, and wipe the /data on RFS with Odin.
Click to expand...
Click to collapse
thank you for taking your time to write this up for me. Very helpful.
All I see are instructions on how to use ADB or to use CWM to flash to the external SD. Is there a way to use CWM ready CM7 for the internal flash?
Hi,
If I understand your question, you would like to run CyanogenMOD7 off the
internal memory also called emmc, rather than running it off the external
memory or uSD card.
Though a bit dated, I found this walk-through to be very detailed:
http://forum.xda-developers.com/showthread.php?t=960542&page=16
Hope this is what you are looking for.
Peter
kruuth said:
All I see are instructions on how to use ADB or to use CWM to flash to the external SD. Is there a way to use CWM ready CM7 for the internal flash?
Click to expand...
Click to collapse
It is helpful, however I am looking for a CWM ready version....so far no luck.
Hi,
The instructions in:
http://forum.xda-developers.com/showthread.php?t=960542&page=16
Are assuming running from uSD version of CWM.
Following other CWM install instructions you can end up with CWM installed
on the internal flash, emmc.
For example:
http://forum.xda-developers.com/showthread.php?t=971197
Minor issue to watch for: the versions of CWM that support EXT4, required
for CM7 also require a different kernel.
I'm not quite sure what you mean by CWM ready version of CM7... the CM7
nightlies are in a .zip file that is flashed by CWM running off the EMMC boot
partition. The first time you install CM7 you also have to use CWM to
reformat some of the partitions on the EMMC (to ext4), but after that you can
use CWM to update the flash each time.
ROMManager can also be used to download ROMS and start CWM.
I am in 'updating' mode, I usually download a recent CM7 nightly and
recent overclock Kernel on PC, then share to Nook using Dropbox.
On Nook, I download .zips from Dropbox and move to root of the data
SD card. I also have latest Google apps (GAPPS) in Dropbox or SD card.
I then use ROMManager to run CWM to backup entire ROM.
Then I use ROMManager to boot into CWM and individually:
Install from .zip: nightlyxxx.zip (Current CM7 version)
Install from .zip GAPPSxxx.zip (Current google apps version)
Install from .zip kernelxxx.zip (Current OC kernel, overwrites the CM7 version)
Then I wipe cache partition.
Then finally wipe dalvik partition - CWM freezes here.
Reboot and wait a while (5 mins) (I assume it is rebuilding dalvik cache here)
Often seem to need another reboot and wait.
Hope this helps...
Peter
kruuth said:
It is helpful, however I am looking for a CWM ready version....so far no luck.
Click to expand...
Click to collapse
Thanks, that does clarify things. I'm new at this and do it was a little confusing to me how to do it. In the captivate forum they're a little more forward on how it's done. I appreciate the help. I tried using the rc4 encore signed but it seems to stop at the startup with N color on it. I thought I formatted all the partitions properly. Is there something I did wrong?
Hi,
I haven't had the problem of being stuck at 'N', but I'm sure there are plenty of
others that have... it will be something simple, probably missed one step in install.
Perhaps check through the list you followed and try and remember if you forgot
one step, or didn't understand one of the steps.
My install no longer shows the "N" at all when booting, so I'm guessing that
there is a missing piece somewhere!
I get:
"Touch the Future of Reading"
Brief flash of "Loading"
Few seconds of sideways "android..."
Then an animated CyanogenMOD logo for more seconds.
Here is one (long) thread about booting problems, but there are other ones too.
http://forum.xda-developers.com/showthread.php?t=949699
Hope this helps,
Peter
Got the problem fixed. Had to boot to a different CWM and format as ext4. Now all is well.
Speed Comparison
I have CM7 flashed to a class 4 sd card and it seems a little slow compared to the stock elcair build. Does CM7 installed to the internal memory speed things up a bit or does the system still seem a little slow. I'd like to know before I flash to my internal memory.
It should be faster on the internal, logically speaking, but perhaps with the right SD card you'll get comparable speed.
When I first got my NC, I installed CM7 on an sd card.. quickly found out that it wasnt stable enough for me and I installed CM7 on emmc. I'm selling my nook to a friend and want to return it to stock with no CWM on it.
Before I installed CM7 on emmc I made a backup of my stock setup. Should I restore this backup or wipe everything and use the zip of 1.2 without CWM (this guide: http://forum.xda-developers.com/showthread.php?t=931720)?
I want to return the nook to how it was on the day I bought it when I first took it out of the box. Are there any other steps I have do to unregister it or anything? He wants to be able to purchase books through B&N with it and all that.
Thanks
The 1.2 .zip is probably simplest. It will definitely leave the NC de-registered without any extra steps.
So I guess I'll follow the guide for a clean 1.2 install. I will then be able to update to 1.3 correct?
Edit: Also, my nook is a blue dot, with the newer partitions. If that matters at all.
Hmm, I'm not sure how the 1.2 image will interact with the newer partitions--that thread you linked and the one with the 1.2 image are both pre-blue-dot, with no mention of how the new partitions interact with those methods. Your best bet may be to clear CWM off eMMC and do 8 failed boots, to be safe.
So instead of messing with the 1.2 zip, should I instead restore the clean stock backup that I made using CWM before I installed CM7 on emmc? If I read correctly, I can unregister the nook in the stock nook settings and then re-register it. I think. Basically I want to make take my personal information off of it and put his on.
I guess I don't HAVE to take off CWM, unless it will cause problems? The person I'm giving the nook to is not very computer literate and I don't want him to have any problems down the road.
My thinking is, if you restore from your back up image (presumably made via CWM on eMMC), it will not remove CWM. The 1.2 image from this thread might install just fine as long as your CWM is up to date (3.2.0.1), but I'm not 100% sure of it. Your safest bet may be to repartition first using this thread: http://forum.xda-developers.com/showthread.php?t=1094371
Unless, of course, someone can confirm that the 1.2 image works with blue-dot NCs. If your friend wants the 5GB /data instead of /media, there's another zip in the repartition thread you can use after you're back to stock.
ETA: the main problem CWM would cause is blocking future B&N updates.
ETA2: if you're a gambler, you could just try the 1.2 image (make sure you have CWM 3.2.0.1). If it won't boot, try 8 failed boots to restore. If it still won't boot, you'll need to make a CWM SD card and repartition anyway.
Just rebooted into recovery and my CWM version is 3.2.0.1. CWM has gotta go then, since I want him to be able to receive all future updates.
You could also just google around a little bit, there's a guide to repartition the NC back to pre-bluedot partitions.
It's pretty simple. I did it to mine prior to installing CM7.
Here's a guide: http://mrm3.net/nook-color-how-to-blue-dot-nook-color/
Also, from my understanding the newer partitions shouldn't affect any roms being loaded... including the stock one. They're all made to fit on the original 1gb partition, so they'll fit fine on the 5gb one.
Here's a similar thread to this though. http://forum.xda-developers.com/showthread.php?t=1125675
Success.
Didn't mess with any partitioning. Put the 1.2 zip without CWM on an sd card, booted into recovery, wiped /system and /data, installed the zip, wiped /cache and dalvik cache. Rebooted into stock 1.3 with zero problems. Downloaded the 1.3 update with zero problems. Loving it.
Thanks all!
Are there any other steps I have do to unregister it or anything?
Click to expand...
Click to collapse
Go to your account on the B&N website and de-register it from there.