Hey my xda'ers. I apologize with the bombardment of questions i have recently, theyre all things i have looked into and couldnt find exactly what i needed.
Its an easy question for those who use data to ext.
I had to go back to my backup (stock rom) to update my prl. This was from CM7.03 with data2ext applied. In recovery i wiped data/fac reset., cache partion, format boot, cahche, data, system, and sd-ext (this part is what i might mis understood) But anyway. I did what i had to do then decided to flash an AOSP rom. So in recovery i did the exact same wipe as above. Flashed rom, gapps, and data2ext4 v4. I didnt partion my card cause i though it was already partioned from my CM rom when i did it then (correct?) so i booted in and ran all the commands i needed for data2ext4 and it didnt run down my internal memory. so i decided to partion my sd card (again) to see if that would fix, it did NOT.
So can anyone shed light on what i did wrong and if i need to format and start over!?
When you were running data2ext you were supposed to do a nand+ext backup first and then flashed the data2ext zip and then rebooted. Then you were supposed to boot back into recovery and only wipe data,cache & dev-cache and then flashed your sense rom of choice. After you updated pri/prl power down and reboot back into recovery and make a regular nand and reboot. Then boot back into recovery and wipe data,cache & dev-cache then restore your nand+ext you made and then flash the data2ext zip and reboot. When your running data2ext ext don't wipe the sd-ext it will more than likely result in bootloops and could make your nands useless. Also your partition you setup on your sd should still be there unless you reformatted your sd. So when you wiped the sd-ext you essentially wiped out your data2ext link. And as far as if you have to start over well you could try to restore your nand+ext if you made one and then flash the data2ext and reboot to see if it will. If not then yes. But when you get it all set back up just make a nand+ext backup and remember not to wipe the sd-ext.
Root/Hack-Mod_Always *
laie1472 said:
When you were running data2ext you were supposed to do a nand+ext backup first and then flashed the data2ext zip and then rebooted. Then you were supposed to boot back into recovery and only wipe data,cache & dev-cache and then flashed your sense rom of choice. After you updated pri/prl power down and reboot back into recovery and make a regular nand and reboot. Then boot back into recovery and wipe data,cache & dev-cache then restore your nand+ext you made and then flash the data2ext zip and reboot. When your running data2ext ext don't wipe the sd-ext it will more than likely result in bootloops and could make your nands useless. Also your partition you setup on your sd should still be there unless you reformatted your sd. So when you wiped the sd-ext you essentially wiped out your data2ext link.
Root/Hack-Mod_Always *
Click to expand...
Click to collapse
hahahaha freakin A dude.
Thanks for sticking this with me as i understand this better. Ill re format and starrt over, and do this right! Hey once i get a few extra bucks ill donate to you for your constant help with buligernet questions from me
Lol na man I don't do donations but thanks for the offer. I don't mind helping out my fellow xda member. If you need anything else just let me know.
Root/Hack-Mod_Always *
I appreciate it so much. god bless
Ha Now that's a thanks I'll be glad to accept. God bless you to man.
Root/Hack-Mod_Always *
Oh and you don't have to reformat your sd your partitions should still be there as long as you didn't reformat your sd. You can just flash a fresh copy of your rom and just resetup the data2ext mod. But remember to make a nan+ext backup. Also always remember when you do and nand+ext backup always flash the data2ext zip and reboot. Then go back into recovery and continue. Same with restoring a nan+ext always reflash the data2ext zip right after.
Root/Hack-Mod_Always *
im using CW 3.0.2.8 and it doesnt say nand+ext, so i assume you use RA?
But i also assume CW backs up the ex if it exsits?
Edit: also you say flash it then reboot, then go back into recovery.
When i reboot do i need to enable it while im there, or just simply boot and go back to recovery?
coffeehandle said:
im using CW 3.0.2.8 and it doesnt say nand+ext, so i assume you use RA?
But i also assume CW backs up the ex if it exsits?
Click to expand...
Click to collapse
yes, CWM automatically backs up ext.
Thanks Il Duce!
From which part are you flashing the data2ext zip from???? And my bad. I'm using Ra, I should have asked you what recovery you were using. The same applys. And thanks duce for the cwm info.
Root/Hack-Mod_Always *
From the rom i had enabled with? yes. Cause i dont know how to disable it haha
If you already have the mod enabled and you want to do a update the same applys. Roms, kernels,etc. And since cwm already backs up the ext, then after you do the nand just flash the zip and reboot. Same applys for an update for pri/prl. And to disable data2ext in terminal do this
Su
data2ext --disable
Root/Hack-Mod_Always *
Related
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!
Hello,
I am about to install CM7. I currently Have Nookie Froyo 0.6.8 with CWM 3.0.0.5. I believe I need to update to CWM 3.0.1.0 first. Do I need to wipe / format the boot partition first or will the update to CWM / CM7 do that? What data lives in boot curerntly and what would be a situation / reason for wiping the boot partitition? When is it ever done?
Thanks in advance!
~J
you should not wipe boot when installing cm7
mooja said:
you should not wipe boot when installing cm7
Click to expand...
Click to collapse
What would be a situation / reason for wiping boot? When is it ever done?
OK. thank you, but what would be a situation / reason for wiping the boot partitition? When is it ever done? I'm trying to learn about all aspects of rooting / cwm.
Thank you
~J
Not needed,running cwm will handle everything. Also the boot should stay so that SD keeps priority for recovery reasons.
There is a ROM Manager option to wipe data/cache, this should be done if changing rom types (ex nookie to CM7) but isn't usually needed between minor versions of the same rom unless issues arise.
It wipes the boot sequence, doesn't matter what rom you're going too, you need the boot data.
I've wiped it twice. Both times required I restored to stock before moving to a custom rom. Just wipe data and cache, and you'll be fine.
when going from nookie Froyo to CM7, you are changing the file system from EXT-3 to EXT-4. Remember to format /system /data /chache, and wipe Dalvik-cache within CWM 3.0.1.0 before installing the CM7 rom. By formating the three partitions in CWM 3.0.1.0 you upgrade the file system.
There is almost never a reason to format /boot. You will only cause problems that are annoying to fix.
Remember to do a backup in CWM before you format and flash CM7. You never know.
hey guys, i have a smiple question, I am running Cyanogen7rc2 with data2ext applied. Now if i wiped data and it formatted everything, and i format sd card and sd-ext, i get this "(bad) installition aborted" when ever i flash that rom. Can anyone explain this to me in greater detail?
1st what version are you running??? If your able to nand back to when you had data2ext working do so. 2nd if you wipe sd-ext more than likely you'll end up in a boot loop. Also if you just wipe everything and flashed the rom without flashing the data2ext zip right after you might receive that msg. After you restore a nand always reflash the data2ext zip. If your rom is functioning fine and you want to update to a new one. Reboot into recovery make a nand+ext backup then flash the data2ext zip and reboot. Then reboot back into recovery and to keep all of your data just wipe cache & dev-cache then flash the rom then the data2ext zip and reboot. If your rom is running fine and you wanna do a fresh install do the same process of making a nand+ext backup then reboot. Then go back into recovery and wiped data,cache,dev-cache. "Don't wipe sd-ext". Then flash the rom & right after flash the data2ext zip and reboot. You will have to setup the data2ext again threw terminal or adb. This is what I do no guarantee it will work for you if your running cwm but it should. The reason I say this is because I'm running data2ext ext2 gf's mod and I'm using Ra1.7. Hope this helps. Also you might want to redownload the rom as it might be a bad dl.
Root/Hack_Mod-Always*
laie1472 said:
1st what version are you running??? If your able to nand back to when you had data2ext working do so. 2nd if you wipe sd-ext more than likely you'll end up in a boot loop. Also if you just wipe everything and flashed the rom without flashing the data2ext zip right after you might receive that msg. After you restore a nand always reflash the data2ext zip. If your rom is functioning fine and you want to update to a new one. Reboot into recovery make a nand+ext backup then flash the data2ext zip and reboot. Then reboot back into recovery and to keep all of your data just wipe cache & dev-cache then flash the rom then the data2ext zip and reboot. If your rom is running fine and you wanna do a fresh install do the same process of making a nand+ext backup then reboot. Then go back into recovery and wiped data,cache,dev-cache. "Don't wipe sd-ext". Then flash the rom & right after flash the data2ext zip and reboot. You will have to setup the data2ext again threw terminal or adb. This is what I do no guarantee it will work for you if your running cwm but it should. The reason I say this is because I'm running data2ext ext2 gf's mod and I'm using Ra1.7. Hope this helps. Also you might want to redownload the rom as it might be a bad dl.
Root/Hack_Mod-Always*
Click to expand...
Click to collapse
That was a ginormous explation! thanks!
Im running dataext4 v4.
So let me get this straight, if i wipe data data/factory reset it wipes the partion off the sd card, or no?
coffeehandle said:
That was a ginormous explation! thanks!
Im running dataext4 v4.
So let me get this straight, if i wipe data data/factory reset it wipes the partion off the sd card, or no?
Click to expand...
Click to collapse
Na not wipe it out as in making the partition disappear it just removes the link you had to it threw data2ext. Because you wiped all of the data from it. Your partition remains but the link is removed. Data2ext ext4 or ext2 wont carry over if you wipe data.
Root/Hack_Mod-Always*
You might want to consider data2ext ext2 "IMO" It performs better. I've read a lot of posts about users having problems with ext4. Its a know fact ext2 can cause data loss if you do a battery pull or improper shut down. But I've been using it for quite some time and I've done batter pulls galore and have lost no data just had to boot into recovery and wipe cache & dev-cache and reflash the data2ext zip and I was good. Also if your not s-off I recommend it when using data2ext and just in general.
Root/Hack_Mod-Always*
laie1472 said:
You might want to consider data2ext ext2 "IMO" It performs better. I've read a lot of posts about users having problems with ext4. Its a know fact ext2 can cause data loss if you do a battery pull or improper shut down. But I've been using it for quite some time and I've done batter pulls galore and have lost no data just had to boot into recovery and wipe cache & dev-cache and reflash the data2ext zip and I was good. Also if your not s-off I recommend it when using data2ext and just in general.
Root/Hack_Mod-Always*
Click to expand...
Click to collapse
L I thought it was the other way around ext2 was the one that could lose data if you pulled battery
Yea I caught that and edited my post look up lol
Root/Hack_Mod-Always*
laie1472 said:
Yea I caught that and edited my post look up lol
Root/Hack_Mod-Always*
Click to expand...
Click to collapse
You sly one lol,you get my pm?
Nope no go. Strange. I guess I have to figure out how to contact a admit. Never did it.
Root/Hack_Mod-Always*
laie1472 said:
Nope no go. Strange. I guess I have to figure out how to contact a admit. Never did it.
Root/Hack_Mod-Always*
Click to expand...
Click to collapse
ok thanks ill do the data2ext2 and try that out.
So one last thing and im all good. the only way you can erase those partions is if you format the sd card, through a computer program?
ah man now im stuck, i nand back to a stock back up i had, then formatted my sd card through my computer
then went to recovery to flash CM7rc2 and i still get this (bad)installition aborted. do i need to re enable the data2ext in my stock rom, then flash CM7.
You can threw a computer program or threw your recovery.
Root/Hack_Mod-Always*
laie1472 said:
You can threw a computer program or threw your recovery.
Root/Hack_Mod-Always*
Click to expand...
Click to collapse
did you read my edit? i did just that in my nand stock rom, and it did the same thing
coffeehandle said:
did you read my edit? i did just that in my nand stock rom, and it did the same thing
Click to expand...
Click to collapse
Backup all of your data.
After you format threw your pc then format it threw your recovery. Then re partition your sd to 1024 ext2 or 1024 ext4 0swap and the rest fat. Then place all of your data back on your sd. Then wipe data, cache,dev-cache and sd-ext. Then flash your rom of choice followed by the data2ext zip and reboot. When you reboot you will have to resetup data2ext threw terminal or adb.
Root/Hack_Mod-Always*
laie1472 said:
Backup all of your data.
After you format threw your pc then format it threw your recovery. Then re partition your sd to 1024 ext2 or 1024 ext4 0swap and the rest fat. Then place all of your data back on your sd. Then wipe data, cache,dev-cache and sd-ext. Then flash your rom of choice followed by the data2ext zip and reboot. When you reboot you will have to resetup data2ext threw terminal or adb.
Root/Hack_Mod-Always*
Click to expand...
Click to collapse
cheers to you man, hope this works. so as long as i dont run that command in adb it wont push the data over to the ext, though it is always partioned?
Yup your right. Even if you flash the data2ext zip it wont activate until you tell it to.
Root/Hack_Mod-Always*
Pardon my noob language, but thanks friend it got me up n running
A no prob. Glad you got it. If you need anything else just shoot me a pm.
Root/Hack_Mod-Always*
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.
Need help guys!
Today i flashed cm7.1 on my N1
(B4 i was using cm6 rc1 with DT a2sd)
Cm7.1 works great but i need a2sd for more space
After i flash DT a2sd beta 4 , i entered into boot loop
My phone wont boot
Whats the problem?? do i need to wipe sd-ext also
(As it may contain previous rom's app data?)
Thanks in advance
Please help!
wipe everything including sd ext or use nandroid backup if any( i usually make backup before flashing dta2sd ).if ur using cm 7.1 u can try S2E app available in market which does the pretty same job but its with gui so its easy to operate
amolji said:
wipe everything including sd ext or use nandroid backup if any( i usually make backup before flashing dta2sd ).if ur using cm 7.1 u can try S2E app available in market which does the pretty same job but its with gui so its easy to operate
Click to expand...
Click to collapse
Thanks for the reply!! m i right tht wiping sd ext wont format files on sd card?(fat i mean)
I still get into boot loop after wiping sd-ext b4 installing DT a2sd
is there anything to do with the kernal
I would try doing a full wipe (including system) then flash everything a new. ROM, gapps then DT. If you don't want to lose your app data just backup with titanium backup.
Dude Random21 said:
I would try doing a full wipe (including system) then flash everything a new. ROM, gapps then DT. If you don't want to lose your app data just backup with titanium backup.
Click to expand...
Click to collapse
Thx for the reply! i hv tried wipe system also. Still failed...
And yesterday i tried another a2sd method with s2e...
Everytime stuck at X screen during restart
Which recovery are you using? - your ext may be messed up...