Related
When I try to run switchrom -s I get
Code:
Storing app data...
tar: empty archive
Error occurred during storing of app data...
tar operation failed.
Do you have enough space on the /sdcard?
1. Yes I have enough space (over 2 gigs free)
2. I am running CM6 nightly 07152010-001738
3. Also using Firerat's MTD patch
4. It was running fine
I was using Amon Ra 1.7 but thought I would try clockwork because of RomManger.
Downloaded and flashed clock with RomManager (forgot to reflash the first part of MTD) and boot up fine and all was good. Used clock to do a nandroid all good and tried another nightly (NFG) so I thought good old nadroid restore. Didn't work because I forgot the first part of the MTD patch...
So fastboot erase system and cache, flash Amon RA 1.7, MTD patch, wipe just for good measure (I know not really needed), Flash working nightly and Gapps, falsh MTD patch part 2 reboot. Evey thing is running fine.
Nandroid works but not switchrom.
Any help?
So I'm running Fresh 2.1 and tried to upgrade to 2.3.3 last night, but it was putting it into an endless reboot. I made sure I wiped the cache and data so the only thing I can think of that's causing the problem is that I'm using apps2sd and didn't wipe my ext3 partition. Reflashed back to my 2.1 backup and things are back to running fine now thankfully. It's brought a few questions up for me, though
Before I go the route of wiping my ext3 partition for apps2sd I want to make sure I can still recover back to the way things were before in case the upgrade to 2.3.3 doesn't work. I use Clockwork ROM Manager with Nandroid to do my backups but when watching the backup take place it looks like it tries to mount the ext3 partition to back it up but fails. Honestly not fully familiar with how apps2sd really works, so I don't know if that failure during the nandroid backup means my apps on the ext3 partition aren't getting backed up. Would that mean that if I wiped the ext3 partition and tried to recover my 2.1 ROM that my apps would not be there?
I thought maybe I could just undo the apps2sd setup, do a backup and then I'd be fine. But I'm having trouble finding clear, up to date instructions for how to undo apps2sd.
If anyone can clarify any of my issues or point me in the right direction, I'd appreciate it. Thanks!
Could someone at least point me to some updated instructions for undoing apps2sd on the Sprint Hero?
pdragon said:
Could someone at least point me to some updated instructions for undoing apps2sd on the Sprint Hero?
Click to expand...
Click to collapse
The instructions you are looking for are here
Normally (at least in the RA recovery) when you go to the backup menu for nandroid, you can choose if you wish to backup normally or with the ext partition included (much bigger file, takes longer). Regardless, if you wipe your ext partition, and you need to nandroid back, the backup will work fine, you will just need to reinstall your applications.
I save myself some time when I need to do this by using "Shootme" (free on the market) and take screen shots of my apps, then I can just refer back to the screenies to find everything I need. Alternatively, you could use the ADB "pull" command and take a copy of your apps directory onto your computer, then push them back if needs be.
Hope this helps!
Thanks for the reply, runngwlf. I guess either the version of Nandroid I have, ClockworkMod Recovery, or my phone doesn't support backing up with the ext. When I go into Nandroid, my only options are Backup, Restore & Advanced Restore. Choosing backup just goes straight into running the backup with no choices. During the backup it gives an error saying it couldn't mount the ext partition.
Thanks for confirming the backup will still work, just without my apps. Guess I'll give it a shot!
runngwlf said:
...
Normally (at least in the RA recovery) when you go to the backup menu for nandroid, you can choose if you wish to backup normally or with the ext partition included (much bigger file, takes longer)...
Click to expand...
Click to collapse
Hah! That little tidbit got me going in the right direction. Looking through the ClockworkMod i saw an option to install RA Recovery as an alternative boot recovery. Lo and behold, rebooting into RA Recovery gives me that ext backup option. Thanks again!
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!
Hello,
I am trying to flash the stock 1.2 on my nook color with cwm 3.0.1.0 on sd but I am stuck at the "n" screen (My nook already came with 1.2).
Furthermore it does not seem to be possible to format /data except with cmw 3.0.0.6 (always "Error formatting /data!)! -> see edit (ext4-tool)
I already tried to restore to 1.0.0 and 1.0.1 but no success at all...(booting not beyond n-screen)
thanks in advance
edit: some further information:
I was running 1.2 by stock, installed cm7 nightly and it worked perfectly. Then I discovered a patch to swap sd-card and nook's internal storage mapping in cm7...whatever...which did not work properly.
I then tried to restore cm7 and something went wrong. I think I erased /boot or something. After that I wanted to restore 1.0.1, 1.0 and 1.2 in order to restore /boot none of them worked well.
I was only using the sd-card cwm for ext4: http://forum.xda-developers.com/showthread.php?t=959240
What happened there?
I just want to restore to 1.2 stock firmware..
edit2: I remember having installed the old 3.0.0.6 into emmc through rom manager! after that the problems started, I think...
I do not know what happened but I used the description from here:
http ://mrm3.net/nook-color-experimental-gingerbreadcm7-fix-for-sleep-of-death/
I erased /data with cwm 3.0.0.6 and did everything else as described and have now cm7 running smoothly..
I have the same issue cannot restore to stock, any ideas?
what did you do before trying to restore?
If you do not need the stock rom you might try installing cm7?
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.