Related
So I rooted my Nook with autonooter 3.0.0, I followed all the directions entirely. It worked perfectly, I liked it but wanted to try other stuff. Then I successfully installed Honeycomb v4 on my Nook, I tried it out, but didn't like it, I'll wait until later as its more developed. Then I installed CM7 on my Nook. Its nice, but for some reason a lot of my important apps force close on me. So I thought would just return to stock and then go to autonooter. I tried the method found here - http://forum.xda-developers.com/showthread.php?t=914690
So I don't know if it matters, but I remember formatting boot, system, and data in CWR during the installations of Honeycomb, and also formatting the system and data in CM7 and also in trying to return to stock. So in each of the installations I followed all of the directions perfectly.
Ok, so here is my problem. After I try to return to stock, I try to boot up my Nook, it goes to the Touch the Future of Reading screen, then to the screen with the 'n' on it and the adobe message at the bottom comes up. However, it will not go passed this. It hangs and I cannot fix it. I have tried the 8 reboots which does reinstall the original firmware, however when its complete and reboots it does not boot, it does the same thing I just described.
Please help, if I have left out any information just ask and I will fill in the details.
There is a recovery zip on the development forum. Boot into cwr and flash... that should do the trick... hopefully.
Sent from my DROID2 using XDA App
ext3 / ext4
Doesnt he need to format the partions with a ext3 cwr before flashing or will the recovery do that?
vtx67 said:
Doesnt he need to format the partions with a ext3 cwr before flashing or will the recovery do that?
Click to expand...
Click to collapse
Yeah, I'm beginning to think I do have to fix up the partitions because everything I do is just giving me more hang.
Can anyone help with that?
Get CWR 3.0.5...
Write the SD card image to your uSD...
Copy repartition-boot-with-stock.zip to the root of the SD card...
Decide if you want to restore to 1.0.0 or 1.0.1 and copy the appropriate nook-complete-restore-1.0.x.zip to root of the SD card....
Boot off the SD card in your NC
since you say you have formatted boot... shouldn't ever need to do that btw...
Format Boot... System... Data... and cache...
Install the repartition boot zip file... then the complete system restore from SD card.
yeah.. once you reformat with CWR 3.0.0.5 you should be able to do the re-partition boot flash and then restore the image.
I just got back that way as well.
DizzyDen said:
Get CWR 3.0.5...
Write the SD card image to your uSD...
Copy repartition-boot-with-stock.zip to the root of the SD card...
Decide if you want to restore to 1.0.0 or 1.0.1 and copy the appropriate nook-complete-restore-1.0.x.zip to root of the SD card....
Boot off the SD card in your NC
since you say you have formatted boot... shouldn't ever need to do that btw...
Format Boot... System... Data... and cache...
Install the repartition boot zip file... then the complete system restore from SD card.
Click to expand...
Click to collapse
Thanks for all the help! I'm going to try this now. And I'm guessing it is, but will it be ok to use CWR 3.0.0.6 and boot with that from the SD card?
It needs to be CWR 3.0.0.5 in my experience.
3.0.0.6 supports EXT4 partitions and won't format them back to EXT3.. as long as they are EXT4, the nook will not boot into the stock rom.
The stock kernel doesn't support EXT4.. so it hangs just before it loads the system files..
If you wipe the partitions using 3.0.0.5 and install the full recovery image for 1.01 you should be a-ok.
Alright I got it! You guys are the best! Thanks for the help! Now I just need to re-root and I'm good to go! Thanks again!
Oh and yeah I used 3.0.0.5, that may have been the problem all along because I kept trying to fix with 3.0.0.6. Thanks!
Simple question......if i have already flashed Honeycomb onto the nook internal memory..and if i would like to instead flahs CM7 to the internal memory can i just load my CM7.zip file onto my ClockWorkRecovery SD and then install from zip using that? or do i have to restore back to stock and then reroot and start the process all over?
let me know if you need any clarification on my jibber jabber
Just wipe from recovery, then flash the zip and compatible gapps...
Sent from my NookColor using Tapatalk
danger-rat said:
Just wipe from recovery, then flash the zip and compatible gapps...
Sent from my NookColor using Tapatalk
Click to expand...
Click to collapse
wipe from recovery? Does this mean simply drag the zip file out of my sd card using my computer or put my CWR sd into the nook wipe it there, take the sd card back out of the nook drag and drop the cm7 zip onto my sd card and then install from zip using the CWR
I believe he means you need to boot CWM and use the menu to format areas like data/system/cache and then install CM7. I'm not sure which areas need to be formatted if you installed HC though.
Depends on which version of HC you installed.
If you installed the v2 with ext4 filesystem, you should be able to just wipe system/data/cache and then install cm7.
If it was one of the older HC releases that you had to format the boot partition to install, im not sure what to do.
i had to format boot for HC not cache and i believe with cm7 i have to format cache
Having successfully been using Froyo for a while, I decided to try the CM7 RC. After the flashing the ROM the Nook got stuck in a boot loop, after several attempts, I tried to go back to Froyo. Formatted the System and data under mounts and storage then flashed froyo, now stuck at the Nook N. Repartitioned the boot partition and tried to restore to stock no luck any help would be much appreciated.
- Stuck at Nookie 'N'
A couple questions first; did you reformat your eMMC to EXT-4 by formating system, data, and cache with CWM 3.0.1.0.? Which is required before flashing CM7. If you did then you cannot go back to froyo without reverting back to EXT-3, by formating system/data/cache with CWM 3.0.0.5.
You also may have a messed up boot partition, try flashing one of dalingrin's kernels for froyo or CM7, whichever one you're trying to recover. they are located here: http://forum.xda-developers.com/showthread.php?t=925451
That's about all I can say without knowing if you went to EXT-4
This will fix your problem....
Make a bootable SD immage of CWR. Burn it with a tool of your choice.
After that is done: Open up the sd card and toss the ROM that you want to flash in the root folder. (Hell, or make folders, thats what I do)
Next insert the SD card and restart your nook. You will have booted into CWR where you can then flash the Rom you stored on the SD card.
EDIT: Here is the link of the CWR images: http://legacyschool.us.to/nookdev/clockwork/0.7/
Thanks for the quick response, I am currently using CWM 3.0.0.6, I tried your suggestion of using dalingrin's kernel, no luck. One thing I failed to mention is when I attempted to flash froyo it aborted every time.
btw colbur87 I am using a bootable uSD card...
fpacheco1960 said:
Thanks for the quick response, I am currently using CWM 3.0.0.6, I tried your suggestion of using dalingrin's kernel, no luck. One thing I failed to mention is when I attempted to flash froyo it aborted every time.
btw colbur87 I am using a bootable uSD card...
Click to expand...
Click to collapse
Try getting the 3.0.5.0 CWM from this thread: http://forum.xda-developers.com/showthread.php?t=922870
Then flash it to your uSD card.
Boot to said uSD card
Format /data, /system, /cache
Flash Froyo.zip
Clear Davik-cache
reboot
install OC kernel
clear Dalvik-cache
reboot
I think when you formated with 3.0.6.0 you upgraded your eMMC to EXT-4, and froyo can only run on EXT-3. I may be wrong, but this should set you back up with froyo anyways.
If you're still stuck at the 'n' screen after this, then your /boot partition may be corupted, and someone might have to supply you with a proper one.
This helped a lot it turned out to be the incompatible file systems EXT-3 EXT-4.
I was able to restore my nook to stock. Now I will start over, again thanks a lot....
Hello guys,
I have a little problem which seems to be coming when I move the dalvik cache to the EXT partition of my device.
I am using the latest version of MIUI. It has A2SD built in, but it doesn't seem to be working. It was working before though...
What happened:
I restored the NANDROID backup of the stock ROM I had made before flashing MIUI. Once I booted into it, it warned me about the 2.3.4 OTA update. I did it, but forgot that it overwrites the bootloader, removes root and I will not be able to revert to MIUI.
I pushed the Clockwork recovery and immediately started restoring the NAND backup of my MIUI ROM. Without gaining root on the Stock 2.3.4 ROM.
The Dalvik was moved to the EXT on the MIUI I was trying to restore and functioning properly.
The restore went fine, until it got to restoring the sd-ext. It stood there at some *.tmp file for an hour or so. I removed the battery, booted into recovery, wiped and started the restore again. This time it finished, but when I went to start the phone, it got stuck at the Nexus logo, not even showing the MIUI boot screen.
Wiped again. Tried booting into a previous backup, which didn't have the Dalvik moved to the EXT partition. Restored and booted just fine.
I tried several more times restoring the latest backup I had (the one with dalvik to ext) and got the same result.
Then I tried installing the MIUI backup that didn't have Dalvik moved to EXT and tried moving the Dalvik to EXT. The phone rebooted and same thing happened. Didn't want to get past the Nexus logo.
I then wiped everything except batt stats, formatted ext, and flashed the MIUI ROM. It booted perfectly, but A2SD was not working, just like before (solution was to move dalvik to sd). I downloaded the A2SD GUI only and moved the dalvik to EXT AGAIN. And AGAIN - not booting past Nexus logo.
The only thing I still haven't done is formatting the SD and re-creating the EXT partition.
Any other suggestions on what may be causing this and how to fix it?
I want to have a2sd on this ROM and moving the dalvik to EXT seems to be the only way of achieving this.
Repartition SD card, you've most probably corrupted the EXT partition by pulling the battery.
Do you think that restoring the last MIUI backup I had after this will do the job?
After repartitioning? As long as you back up the files from the main FAT32 partition on the computer, and restore them back - the EXT will be overwritten when restoring nandroid anyway.
Well.... I just formatted the card with Panasonic SD formatter. Transfered only the nandroid backup (without creating an ext partition beforehand) and restored it successfully, but when the phone starts booting it is stuck at the Nexus logo.
I also checked the MD5 of the backup and everything is fine.
Godzi said:
Well.... I just formatted the card with Panasonic SD formatter. Transfered only the nandroid backup (without creating an ext partition beforehand) and restored it successfully, but when the phone starts booting it is stuck at the Nexus logo.
I also checked the MD5 of the backup and everything is fine.
Click to expand...
Click to collapse
Wipe Cache and dalvic. Than try again. Your System Need a ext wenn you push dalvic to sd before.
I ran out of options.
Formatted the card, tried restoring - Nexus logo
Wiped Everything + Dalvik and Cache, restored - Nexus logo
Wiped Everything + Dalvik and Cache, didn't restore old MIUI backup - successful boot. When I tried to move Dalvik to EXT after the successful boot - Nexus logo after restart.
If anyone can suggest anything... Because this way I have no access to the A2SD on the device with this ROM. And everything was working fine before I restored the Stock Ginger.
Did you try installing DT on any other ROM and try and move dalvik to the sd to see if it does the same thing?
Dude Random21 said:
Did you try installing DT on any other ROM and try and move dalvik to the sd to see if it does the same thing?
Click to expand...
Click to collapse
No. I haven't tried with another ROM. I guess I will try CM7 and see what happens when I move the Dalvik to the EXT.
I repartitioned once again, this time using the same EXT size as before the breakdown (512MB). When the backup I am trying to restore was made.
Was using 1024 when I partitioned previously and got the Nexus logo again.
Edit: Same thing. Successful restore and then the Nexus Logo.
I suspect it's the ext partition. Why don't you try formatting through recovery, and do a clean install?
Which recovery do you use? I would avoid Clockwork 3.x...
Well. I formated using Panasonic SD Formatted and then partitioned using the recovery. I did a clean install after that and as soon as I move the Dalvik to the EXT, I can't boot past the Nexus logo.
Yes, Clockwork 3.x. I guess I will try Amon_RA as well. Nothing left to lose.
If you partition with Amon Ra, make sure you up the partition from ext2 to ext3 (available through the Ra menu options)...
Ok. Partitioned with RA.
Tried to transfer the nandroid backup made by Clockwork to a sd/nandroid folder so I can restore it from within RA but it kept giving out some error telling me to look at the recovery log when I selected *.img files from the list.
Good news. I booted into MIUI and installed a2sd GUI. Moved Dalvik to EXT without a problem. I guess Clockwork's partitioning is flawed. Everything is working fine now.
Thank you.
Can anyone suggest a method I can use to restore the Clockwork made NAND backup + the EXT backup now when my partitions are finally alright.
Any method would be fine. Even manual through adb. I don't care. As long as I restore my phone to yesterday.
Thank you guys once again.
You should be fine if you load a clockwork prior to v3.x. I think 2.5.1.4 was the latest version prior to the v3.x series. The issues only arise with v3.x.
But only clockwork is able to restore clockwork backups, and the same goes for Amon_RA.
As an alternative, you can just extract the img files and manually load your data back on. It is definitely more time consuming, but it wouldn't matter what recovery you use. It has been a while since I extracted anything from the img files, and when I did, I just got the data from apps stored on the internal (apps and dalvik were stored on the sdcard), and I think the only program I used was unyaffs2 to extract the data.
Thank you guys!
Partitioning the card with Amon_RA and restoring the old Clockwork-made backup with Clockwork 2.* worked perfectly.
I will not use Clockwork ever agian. Putting Amon_RA and that's it.
You will only have this problem with clockwork 3.x - there doesn't appear to be the same issue with clockwork 2.x
I have been using v2.x without any issues (never upgraded to v3.x). I prefer it because it gives me the option to wipe the /system partition, whereas Amon_RA is missing this feature and you can only do it with a flashable zip.
I use 2.x for a number of reasons. I tried 3.x a few times, but always had ext issues on my N1. Having said that, I've used 3.x on my nook, MT4G and G2, and never had issues with them - just on the N1...
I've used RA 2.2.1 on CM7, MIUI ,Sense rom. I never seen sd-ext issues on my Nexus One.
Hi,
I constantly run into "not enough space" problems and the phone starts to get really slow due to this.
So I tried everything possible with my rooted nexus, removed apps with Titanium and so on.
But to no use, Dalvik Cache alone is over 60MB.
So I read that you can partition your SD-Card and move stuff from the phone over like the cache and app-storage.
Also I want to install CM for the first time cause I like to have additional options with the kind of kernel. Like support for battery calibration.
I'm a bit unsure about all this.
How many partitions do I have to create on my card?
What size should they be? (card is 16 GB)
How do I install CM with all this so it uses the partitions?
Is there a DAU step-by-step tutorial for this you can recommend?
Usually a 1GB ext4 partition would suffice. Some use smaller, some bigger, but 1GB is about average.
You can use Gparted to format it if using Linux. Otherwise I'd recommend installing 4ext recovery on your Nexus and use that to partition your SD Card. You could also use Amon Ra recovery if you have it, but avoid using cwm recovery to partition as it can cause corruption.
Finally what version of CM are you using? If BCM CM9 then that has mounts2sd built in.
If CM7 then you can try a multiple of options, including s2e, links2sd, darktreamer or even mounts2sd.
Everyone has their favourite, but I'd recommend you start with s2e which you can download from Google Play. It has a handy GUI.
Ensure you take a full backup of your card before partitioning it. Especially unsure you have good backups of your photos and music.
I use titanium backup for backing up apps. Use this before backing up your SD Card, so that your backup contains it.
Sent from my Nexus One using xda app-developers app
Thanks for your reply.
It is my productive phone so I need a stable and fast rom.
Thus I plan to use the latest stable cm which happens to be 7.2 if I'm right.
I'm running Ubuntu on my desktop so I will def. use gparted
So do I get that right:
- wipe my card and partition it with gp
- then wipe my phone and flash CM7.2
- then install s2e (or else) and setup to use the partition
DarsVaeda said:
Thanks for your reply.
It is my productive phone so I need a stable and fast rom.
Thus I plan to use the latest stable cm which happens to be 7.2 if I'm right.
I'm running Ubuntu on my desktop so I will def. use gparted
So do I get that right:
- wipe my card and partition it with gp
- then wipe my phone and flash CM7.2
- then install s2e (or else) and setup to use the partition
Click to expand...
Click to collapse
That's right, but imo it would be easier if you install another recovery and do all steps directly from your phone. Also its not necessary but recommended to fully wipe your card, you can just create the ext partition and maintain the other things you have.
what recovery can do all this?
There are lot of them, but I like 4Ext recovery
Okay what I actually did was:
- install ROM Manager
- install clockworkmod
- install Cyanogen via ROM Manager
- clear all caches and storages via the clockworkmod
- partition via clockworkmod (no swap)
- reformat the partition from ext3 to ext4
- install s2e
- choose mount-to-ext4
- reboot
- select what to move (no download cache)
Thanks to all!
DarsVaeda said:
Okay what I actually did was:
- install ROM Manager
- install clockworkmod
- install Cyanogen via ROM Manager
- clear all caches and storages via the clockworkmod
- partition via clockworkmod (no swap)
- reformat the partition from ext3 to ext4
- install s2e
- choose mount-to-ext4
- reboot
- select what to move (no download cache)
Thanks to all!
Click to expand...
Click to collapse
Try do download an app from Google Play or update an app when using S2E and see you have any problem (e.g., reboot or can't update error message). I had problems with S2E when using CM7.
DarsVaeda said:
Okay what I actually did was:
- install ROM Manager
- install clockworkmod
- install Cyanogen via ROM Manager
- clear all caches and storages via the clockworkmod
- partition via clockworkmod (no swap)
- reformat the partition from ext3 to ext4
- install s2e
- choose mount-to-ext4
- reboot
- select what to move (no download cache)
Thanks to all!
Click to expand...
Click to collapse
I really recommend you to stay away from Clockwork. I had a lot of problems with partitioning.
I thought I was a faulty SD Card ,so I threw it away but I was the recovery fault.
I have been using 4EXT Recovery for a while now and I still have encounter my first problem.
taodan said:
Try do download an app from Google Play or update an app when using S2E and see you have any problem (e.g., reboot or can't update error message). I had problems with S2E when using CM7.
Click to expand...
Click to collapse
I had the same problem, cleared Dalvik and other Caches, then it was gone.
Dr.Thrilla said:
I really recommend you to stay away from Clockwork. I had a lot of problems with partitioning.
I thought I was a faulty SD Card ,so I threw it away but I was the recovery fault.
I have been using 4EXT Recovery for a while now and I still have encounter my first problem.
Click to expand...
Click to collapse
Yes I read that too somewhere else, that is why I formatted with gparted again.
Works fine so far, no problems.
i can't restore a file back up (back up by 4EXT) by CWM 5.0.0.2.
It don't work "restoring sd-ext....."
Use 4ext recovery to restore your 4ext backup
Sent from my Nexus One using xda app-developers app
Still works good except it killed my 16GB card. I'm now on a 8GB. Hope it doesn't die too.
Sent from my Nexus One using xda app-developers app