Related
I am trying to run a Nand + ext backup and it is getting through the regular part of the backup fine, but when it gets to the ext part it gives the standard Nandroid error message about using adb. I just partitioned my card last night and updated to Fresh Toast 2.1.1 using ext4. I was not using A2SD before, so I don't know if this is related to upgrading to ext4 or Fresh Toast(used to be on Fresh 2.0d) or upgrading RA(used to be on 1.5).
Build: RA-heroc-v1.6.2
Use godspeed recovery.
http://forum.xda-developers.com/showthread.php?t=672324
Worked great, thanks.
Okay, i've been having a problem where my device gets stuck at the g1 screen after i flash ANY rom, i've given each rom i've attempted to flash up to 10 minutes each, i have to resort to a battery pull and nan restore to get my phone working again, i've tried flashing roms on two different cards, both with the same horrible end. I've tried reformatting, repairing partition, and wipe wipe wipeing, but nothing seems to work. Any ideas?
my specs:
OS: im running cyanogen's donut (which i have a nan backup of)
SD: 4gb class 6
Radio: latest
SPL: Danger
Recovery: Amon_RA's
Ext3: 1000mb
swap: 32mb
what rom are you tryna flash ill help you out.?
for example if you want the new cm508 t4 then u gotta download the following in the listed order:
1. download & install the newest radio for your device
2. download & install the danger( aka deathspl )\
3. download & install the latest version of cyanogen for your device.
that easy bro. HERE is a gide a friend of mine put together for me and its acurate and current. although there are nomore file links so u have to search google or xda search for the needed files.
good luck.
Requested to be moved to Q&A because this is NOT Development.
okay i've been trying to flash any non ram hack donut and any eclair, none of them make it pass the g1 screen, i've tried everything i have all the correct specs and use the correct procedures but nothing works
i've tired
the latest superD
the latest superE
the stable cyan Eclair
Chomatic Eclair latest
and even though i have it backed up and when
i restore it it works, the cyanogen donut, which i
cannot wipe and flash
xStuntmanEdx said:
okay i've been trying to flash any non ram hack donut and any eclair, none of them make it pass the g1 screen, i've tried everything i have all the correct specs and use the correct procedures but nothing works
i've tired
the latest superD
the latest superE
the stable cyan Eclair
Chomatic Eclair latest
and even though i have it backed up and when
i restore it it works, the cyanogen donut, which i
cannot wipe and flash
Click to expand...
Click to collapse
Why can't you wipe?
Do a fresh nandroid/bart backup of your current working system.
Backup your SDCARD FAT partition to your computer.
Reformat your SDCARD (completely, no ext partition or swap partition)
Make sure you have Amon_Ra 1.7.0 recovery installed
Restart your device in recovery.
Wipe data and dalvik-cache.
Repartition your sdcard
Convert ext2 to ext3
Convert ext3 to ext4 (optional)
Mount SDCARD from Recovery onto your computer.
Re-download your the rom that you want to install and gapps if applicable and place them on the root of your sdcard.
Safely remove the device from your computer
Unmount the SDCARD from the phone (may need a reboot)
Flash your desired rom (don't reboot yet)
Find ddms.bat in the tools folder with the AndroidSDK and run it.
Click logcat
Reboot your device and let it SIT and watch the logcat.
If it seems to stop for a long period of time highlight the lines at the bottom and save the file to your desktop. Open it to confirm that you have the log in your text file.
Upload it to pastebin and post the link in this thread for others to help you further.
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 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 *
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.