Whenever I am running a ROM that is not stock or a stock based ROM like HoloBlur, I end up running into this problem when I want to flash a different ROM. For example, after backing up, I wanted to wipe from LiquidSmooth 2.9 and try out Slim or PACman. I factory reset, wipe data/cache, no problems. Then I wipe System like I do before any ROM flash, and then no files are found on my SD and Sideloading doesn't work like it usually does. (I don't have an external SD card and I never format SD card in recovery.) Can't mount SD, can't flash the ROM, stuck. I've had to go back to stock with RSD Lite twice because I couldn't flash my new ROM after full wipe... The only solution I can think of is skip wiping system, but I feel like that isn't a clean enough flash and could cause problems. I know CWM likes to locate the SD card in the " 0/ " directory on AOSP/AOKP/CM based ROMs and such, does that have anything to do with it?
Related
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.
Hello,
I was on stock Android 2.1 rooted + xRecovery + JIT + Link2SD.
I tried to install multiple custom roms (GingerDX 007, Floyo 1.0, FroyoBread 0.23) and did a Full Wipe in xRecovery (tried also CWM recovery from the Floyo).
There seems to be something "evil" going on, because multiple apps are still there from my 2.1 after full wipe or a full custom rom recovery. Some of these apps and/or services are crashing. And all of these custom roms are very laggy and slow as opposed to what I have read about them.
I do not understand why I cannot wipe everything out from my old installation.
Can anybody help please?
bump. bump.
Sounds like as you have some remains from Elcair on your SD card the new ROM somehow sees. After Full wipe (Factory Reset) and ROM Flash there shouldn't be any left-overs in the system or cache partition as xRecovery is formatting the NAND partitions.
Try backing up your data from the SD card and format it afterwards in Settings.
::: ROFL u hv to format partition... then it will not happen more
use MiniTool Partition Wizard Home Edition to format partition or delete all file from root explorer (sd ext)
I have installed custom rom from zip and used it for several weeks.
Today I have decided to try new rom and I have made a backup trough CWM (6.0.2.5) in format .tar
I have tried to restore the backup. but the phone gives me a really strange error.
Encryption Failed. The system .. bla bla bla ... you need to reset your phone ..
I have tried to factory reset trough CWM, but the problem is the same.
I have tried to restore older backup ... the same error ...
Any ideas what is the problem and now to fix it (restore the rom)
I have tried the following ..
1. format /system /cache / data
2. install custom rom (CivZ v3.0)
3. take the setup wizard
4. reboot into recovery (CWM 6.0.2.5)
5. backup (.tar format)
6. restore from the backup
and .. the same error and no working rom ..
Can this be an internal SD memory problem ?
Any ideas ???
Anyone
Try backing up to external SD card. If that works, or you dont have an external SD card, backup and repartition your internal SD using AIO toolkit (choice 4 in the toolkit, then select the new unlocked ICS bootloader, and 512 MB system partition, or whatever your preferred size is, then run the internal SD fixer which follows that step) and try again.
The backup is on external SD
I have already repartitioned the internal SD with the default ICS layout (1.5G system)
hack_man said:
The backup is on external SD
I have already repartitioned the internal SD with the default ICS layout (1.5G system)
Click to expand...
Click to collapse
Then try backing up to the internal SD and also try changing recovery to TWRP.
I have already tried TWRP but it cannot restore CWM backup
Currently I have stock rom , but I cannot rollback to the previous rom backup.
a few days ago I have used some app (found here in XDA) for optimizing internal SD .. is it possible this app to broke something in the internal SD ?
hack_man said:
I have already tried TWRP but it cannot restore CWM backup
Currently I have stock rom , but I cannot rollback to the previous rom backup.
a few days ago I have used some app (found here in XDA) for optimizing internal SD .. is it possible this app to broke something in the internal SD ?
Click to expand...
Click to collapse
Hi! I assume that you were using the stock ics rom. Right? Stock ics use system partition as ext4 but data and cache are used as ext3. Since TWRP and CWM format data and cache as ext4 you cannot use your old backup of stock ics rom, unless you format both (data and cache) to ext3.
I created a zip which converts data and cache to ext3. Download from my attachment.
Flash the zip file then restore your backup.
Thanks :victory:
I will try
I have flashed a bunch of different ROMs lately. I always wipe cache, dalvik and do a factory reset but maybe it may no longer be enough. Currently, my phone is rooted with Cocore and CWM. I am thinking about going to CM11. Last time I tried that, I noticed some stuff during setup was overlooked because it already seemed to be there. So I think some bits and pieces are left in the phone. Therefore, I want to "scrub" it before trying another ROM (thinking CM11 this time). I know the CM kernel comes with it.
questions:
1) Can I just mount and reformat system, data, cache and preload to clear everything out before flashing a new ROM?
2) Will the kernel be protected (in this case is CoCore) after reformating or should I worry about it?
3) When I flash the original stock 4.1.2 from Odin, does it completely reformat everything when it loads onto the system?
corvus.corax said:
I have flashed a bunch of different ROMs lately. I always wipe cache, dalvik and do a factory reset but maybe it may no longer be enough. Currently, my phone is rooted with Cocore and CWM. I am thinking about going to CM11. Last time I tried that, I noticed some stuff during setup was overlooked because it already seemed to be there. So I think some bits and pieces are left in the phone. Therefore, I want to "scrub" it before trying another ROM (thinking CM11 this time). I know the CM kernel comes with it.
questions:
1) Can I just mount and reformat system, data, cache and preload to clear everything out before flashing a new ROM?
2) Will the kernel be protected (in this case is CoCore) after reformating or should I worry about it?
3) When I flash the original stock 4.1.2 from Odin, does it completely reformat everything when it loads onto the system?
Click to expand...
Click to collapse
Some information are stored on internal SD memory. Maybe it was there. Try to delete it. Backup SD to PC, format it - do factory reset and see if it is happening again.
shut_down said:
Some information are stored on internal SD memory. Maybe it was there. Try to delete it. Backup SD to PC, format it - do factory reset and see if it is happening again.
Click to expand...
Click to collapse
If I backup the internal SD card to the PC and then restore after a reformat, won't the offending bits come back again?
corvus.corax said:
If I backup the internal SD card to the PC and then restore after a reformat, won't the offending bits come back again?
Click to expand...
Click to collapse
I did not tell you to restore it. Keep it on PC, in case you need some of data from there. Maybe you erase some picture that you need or something like that. And not to blame me later. :fingers-crossed:
I tried to upgrade from http://forum.xda-developers.com/showthread.php?t=2550392 Virginity V13 to Virginiti V11. I didn't wipe anything cause it said i didn't have to. Now i'm stuck in bootloop. I've tried to wipe data, cache and dalvik and it doesn't work. I've also tried to flash another rom but when i try to flash a zip from external sd card it says that it can't mount the sd card (I've tried multiple sd card's), then i tried to sideload the rom but it said failed to write data 'protocol fault (no status)'. I also tried to use adb push to get the rom to my internal sd but it says error: closed. I feel like i've ran out of options. What can i do to fix this now.
------------------------------------------
Fixed it by installing a stock rom from odin!!
Micii said:
I tried to upgrade from http://forum.xda-developers.com/showthread.php?t=2550392 Virginity V13 to Virginiti V11. I didn't wipe anything cause it said i didn't have to. Now i'm stuck in bootloop. I've tried to wipe data, cache and dalvik and it doesn't work. I've also tried to flash another rom but when i try to flash a zip from external sd card it says that it can't mount the sd card (I've tried multiple sd card's), then i tried to sideload the rom but it said failed to write data 'protocol fault (no status)'. I also tried to use adb push to get the rom to my internal sd but it says error: closed. I feel like i've ran out of options. What can i do to fix this now.
------------------------------------------
Fixed it by installing a stock rom from odin!!
Click to expand...
Click to collapse
If you can enter Download Mode flash stock FW from sammobile or live.samsung-updates.
service firmware is a very good solutions to all problems it contains many files!!!!!!! here you go https://disk.yandex.com/public/?hash=tXKAoVyUrXTe08lxT4+xJLOlNGhBIJjNaXhIiDL+KhU=
don't forget factory reset from stock recovery after flash then you can use any rom you like