Related
WARNING: DO NOT FOLLOW THE APPS2SD AS MOST ROMS ALREADY DO THIS FOR YOU.
If you do, it will break things.
-ivanmmj
Like My Guide(s)? Donate
Here we go!
Things you need:
A Rooted G1 Phone
Cyanogen ROM - Download v4.0.2
Cyanogen Recovery 1.4 - Download
Apps2SD - Download
Clean SD Card
Note: This will remove ALL files on your SD Card so please back it up
------------------------------------------------------------------------------------------------------------------
Install the New Recovery Image
Download the recovery image
Place the cm-recovery-1.3.1.img file in the root of your SD Card (Root = not in any folder)
Go back to your phone (Dont forget to unmount)
Open terminal and type in the following
Code:
su (wait for a screen to popup and press "allow")
flash_image recovery /sdcard/cm-recovery-1.3.1.img
------------------------------------------------------------------------------------------------------------------
Install Apps2SD
Download the Apps2sd apk from above
Place the apps2sd.apk on your sd card
Download a file manager like Linda or Astro from Market (They are both free)
Go to Settings > Applications and check the Unknown Sources button
Open up the file manager you just downloaded and find the apps2sd on your sdcard
Press on the app and install the Package Installer and press on Install
Apps2sd should now be installed
------------------------------------------------------------------------------------------------------------------
Partition Fat32/Ext2 with App2SD
Open up Apps2SD
It will show you a screen telling you that your card is not partition and you will have a sliding bar to choose the amount of space you want for an EXT2 partition
I suggest a max of 600mb for EXT2 space (I use 500mb)
Press Ok
You will get a Force Close screen DONT PRESS FORCE CLOSE PRESS WAIT
You will get a reboot message, Press Reboot
You now have a EXT2 partition
------------------------------------------------------------------------------------------------------------------
Upgrading your EXT2 Partition to EXT3
Note: You do need the Cyanogen Recovery image for this to work!
Reboot into Recovery (Home + Power)
Go to console (Alt+x)
Press Enter
Type the following in the Console:
Code:
upgrade_fs
Wait for it to finish
Congrats! You now have a Fat32/EXT3 partitioned Sd Card!
------------------------------------------------------------------------------------------------------------------
Installing the Cyanogen ROM with Auto Apps2SD
Download the ROM
Rename the file from cm-xxxxxxx.zip to update.zip
Place update.zip at the root of your sd card (Root = Not in any folder)
Reboot into Recovery (Home + Power)
Wipe (alt+w)
and Flash (alt+s)
Wait for it to finish and reboot!
------------------------------------------------------------------------------------------------------------------
Congratulations! You now have a Fat32/EXT3 Partitioned SD Card with auto Apps2SD enabled. You can check if you have both partitions in Settings > Sd Card and Storage. Remember, this is Auto Apps2SD, that means the everytime you reboot it will move all your installed apps to your sd card AUTOMATICALLY!
------------------------------------------------------------------------------------------------------------------
Format your EXT3 Partition (ADB is needed)
Code:
adb remount
adb shell
rm -r /system/sd/*
reboot recovery
then flash the update.
------------------------------------------------------------------------------------------------------------------
Here is another way to partition your sd card!
Note: You will need The latest CM recovery image
This guide will partition your SD card with 32 mb swap, and 512 mb EXT4 partitions!
WARNING! This will erase EVERYTHING on your SD Card!
Note: ADB Is needed for this script to work. If you dont have ADb working please read the ADB Sticky in the Q & A Forum
Step 1:
Download the necessary files HERE
Step 2:
Place the sdparted.sh file in C:\ Note: Do not place it in any folders!
Place adb.exe and AdbWinApi.dll in C:\Windows\system32
Step 3:
Run sdparted.bat
Thats it! All done!
Thank you 51dusty for the sdparted Script!
Batch file made by me!
Great guide...again =] But this way is MUCH MORE stable.
http://forum.xda-developers.com/showthread.php?t=534714
ya i know i saw that guide. I decided to put this one up becuase it uses minimal commands and doesnt involve a lot of terminal usage and stuff. Just another way to partition i guess.
Ok I looked in settings and storage. This is what I have....sd card total 6,501mb available space 5,813mb sdcard secondary 1,048mb available space 829mb but for internal space it's showing 86mb. Did I do this process right? Is my internal space suppose to have much more space? When I download something it takes away the internal memory.
lazee_smurf said:
Ok I looked in settings and storage. This is what I have....sd card total 6,501mb available space 5,813mb sdcard secondary 1,048mb available space 829mb but for internal space it's showing 86mb. Did I do this process right? Is my internal space suppose to have much more space? When I download something it takes away the internal memory.
Click to expand...
Click to collapse
yup! you are all good! 86mb for a cupcake rom is perfect! Congrats!
So what goes into the secondary storage because if I download something the internal space gets used
lazee_smurf said:
So what goes into the secondary storage because if I download something the internal space gets used
Click to expand...
Click to collapse
just reboot and your app will go to your sd card.
nephron said:
just reboot and your app will go to your sd card.
Click to expand...
Click to collapse
Thanks for the help!
Greetings
I knew it all could'nt go as smoothly as the new rom install ^_^
When I try to run apps2sd wether out of astro or from the app panel, it goes to a black screen, and thats it. The phone is not locked, I just hit home (after waiting for minutes for something to happen) and I'm back at my home screen.
I did'nt think I skipped any steps. Idea's ?
Thanks for the Sticky Guide
upgrading filesystem
I have the right recovery if I upgrade from ext2 to ext3 will I lose all my apps?
installed app2sd it asked if I wanted to reboot, I hit reboot and now I'm stuck on the G1 screen
maybeoneday said:
installed app2sd it asked if I wanted to reboot, I hit reboot and now I'm stuck on the G1 screen
Click to expand...
Click to collapse
This is why you don't partition your sdcard using this. It works most of the time but not always. Wipe and reformat your sdcard. Then reflash ROM
pistol4413 said:
I have the right recovery if I upgrade from ext2 to ext3 will I lose all my apps?
Click to expand...
Click to collapse
No you will not.
sweet
alritewhadeva said:
No you will not.
Click to expand...
Click to collapse
Sweet man thanx!
ext3 slowed my g1 down
I jus upgraded my partition using this guide and my fone seems WAY SLOWER. Is there anyway to downgrade safely back to ext2 without wiping the partion clean? Or do u recomed an app I already have an overclock app.
fixed problem!
I fixed the issue. Lol I feel kinda dumb. Just has to many processes running that where eating memory.
I am lost. I have the newer SPL and JF 1.51 adp. Why all of these steps for apps2sd?
Should it not be:?
1. Format card using a partition program and create ext3 / FAT partitions
2. Install newest Cy rom
3. It automatically moves the apps when it sees the ext3 related parameters.
Why all of the steps in this thread? Am I missing more brain than I normally do?
Why would I need the 1.3.1 recovery rom? Are all of these steps if you do not already have a JF rom?
Thanks!
rushless said:
I am lost. I have the newer SPL and JF 1.51 adp. Why all of these steps for apps2sd?
Should it not be:?
1. Format card using a partition program and create ext3 / FAT partitions
2. Install newest Cy rom
3. It automatically moves the apps when it sees the ext3 related parameters.
Why all of the steps in this thread? Am I missing more brain than I normally do?
Why would I need the 1.3.1 recovery rom? Are all of these steps if you do not already have a JF rom?
Thanks!
Click to expand...
Click to collapse
Apps2SD2 detects if your card has been formated with an ext2 partition. If not it will format your sd card for you therefor not needing a computer program. The new reocvery 1.3.1 allows you to run the upgrade_fs command to format the ext2 to ext3 and also has other features such as gparted and fix ext filesystem.
my question is this...I already have cyanogen's rom installed...I have been away from a computer and the internet for about a week so I'm still on 3.6.5...which is fine with me.
In Cyan's thread, he says:
DO NOT RUN ANY OTHER APPS2SD APPLICATIONS ON THIS BUILD. YOU WILL BREAK YOUR SYSTEM. THEY ARE NOT NECESSARY BECAUSE THIS ROM WILL DO A2SD AUTOMATICALLY AND BETTER!
Click to expand...
Click to collapse
however one of the steps to partitioning the sd card in this post is installing apps2sd..
i want to partition the card...but I don't want to break my system...am I missing something? clarification please?
I am using the Switchrom script with CY recovery. I have successfully made backups and switched between roms using the script. Now I want to try the new Drizzy Hero rom. To install the rom I will have to wipe the ext3 partition. My question is, If I wipe the ext3 partition, will I loose the script? If yes, can I copy the script in system/sd later on for it to work again?
PS: Before someone posts "search the thread" answer, I tried doing it and couldn't find anything.
Thanks
bole_to said:
I am using the Switchrom script with CY recovery. I have successfully made backups and switched between roms using the script. Now I want to try the new Drizzy Hero rom. To install the rom I will have to wipe the ext3 partition. My question is, If I wipe the ext3 partition, will I loose the script? If yes, can I copy the script in system/sd later on for it to work again?
PS: Before someone posts "search the thread" answer, I tried doing it and couldn't find anything.
Thanks
Click to expand...
Click to collapse
The only thing that is stored on your ext3 partition is your apps. So when you clear that only your apps will get cleared.
supremeteam256 said:
The only thing that is stored on your ext3 partition is your apps. So when you clear that only your apps will get cleared.
Click to expand...
Click to collapse
Thanks man. Wiping now.
To clear this up for other reader who might stumble on this thread, the above comment is not true. If you wipe you ext 2/3 you might end up wiping more stuff than just apps. I realized it the hard way lol. However you can push back switchrom.sh in /system/sd and you will be good to go. The alternate method to do this is to delete just the following folders:
mount /dev/block/mmcblk0p2 /system/sd
rm -rf /system/sd/app*
rm -rf /system/sd/dalv*
bole_to said:
To clear this up for other reader who might stumble on this thread, the above comment is not true. If you wipe you ext 2/3 you might end up wiping more stuff than just apps. I realized it the hard way lol. However you can push back switchrom.sh in /system/sd and you will be good to go. The alternate method to do this is to delete just the following folders:
Code:
mount /dev/block/mmcblk0p2 /system/sd
rm -rf /system/sd/app*
rm -rf /system/sd/dalv*[/QUOTE]
You can do that or you can wipe buy doing this
Code:
mount /system/sd
mount /sdcard
rm -rf /system/sd/*
cp /sdcard/switchrom.sh /system/sd/switchrom.sh
That's how i've been doing it. And I like to do it this way to make sure the my EXT2/3 is completely clean. I've had problems where doing a partial wipe gives me issues. But yes if you wipe your EXT2/3 drive it will get rid of everything (including the switchrom.sh)
Click to expand...
Click to collapse
when you wipe your internal phone memory and ext3 you will lose the script. once you get the rom you flashed up and running again, just repush switchrom.sh and you are good to go again. wiping the ext 3 or the internal memory WILL NOT wipe out your backups. when i use switchrom i dont even wipe all of ext3...
this is what i do... flash a new rom. get it setup the way i want. install all apps and extra settings i want. reboot into recovery, run switchrom.sh and let it do its thing. now when you have created your back up and want to flash a NEW ROM, not one of your backups, wipe internal memory of course but instead of wiping all of ext 3 drop down to recovery console and do the following
Code:
# mount /system/sd
# rm -rf /system/sd/app*
# rm -rf /system/sd/dalv*
this will prepare your ext3 for a new install of a new rom. when you are going back and forth between your backups you do not need to wipe ext3 at all. the script takes care of all of that. if you have any more questions PM me or hit me up on gtalk - palosjr
NOTE- this script is case sensitive as i found out the hard way... when bookmarking and tagging ROMs be sure to use all lowercase. if you use uppercase the script will fail. hope this helps bro.
thanks guys, i got it to work.
i have ongoing problems installing new roms inc hero one , i have correct spl and radio , i wipe ext partitions repair partitions and wipe factory data but i still have problems with no installs working
one thing i did find after i got a hero rom working is that it started to download some programs that i had installed previously on the phone , how do i completley wipe the phone memory ? as i think this is now my problem ?
mrcgibb said:
i have ongoing problems installing new roms inc hero one , i have correct spl and radio , i wipe ext partitions repair partitions and wipe factory data but i still have problems with no installs working
one thing i did find after i got a hero rom working is that it started to download some programs that i had installed previously on the phone , how do i completley wipe the phone memory ? as i think this is now my problem ?
Click to expand...
Click to collapse
im using cyans recovery 1.4 and when you come to the boot screen for it, theres an option for wiping memory. ive had to wipe whenever switching from one rom to the next.
if your using cyanogenmod v1.4 its alt+w to wipe clean.. then wipe your ext with alt+f as well
Problems with new ROM's huh?
Well...it could also possibly be your micro SD card,in which I found out was my problem about a week ago. I found Paragon Partition Manager on the internet.The free version called Partition Manager 9.0 Special Edition. Anyways...used Partition Manager to delete my old FAT32,EXT3,and Linux-Swap partitions and reformatted the entire micro SD then created new EXT3 and Linux-Swap partitions on my SD. Just thought this may be a solution to your problem. Good luck!
I'm not sure alt+f wipes your ext. there are commands you have to type.
to completely wipe your ext2 and ext3 you have to type:
mount /system/
rm -rf /system/sd/
or at least that's what I always used until I upgraded to ext3.
PlatinumMOTO said:
I'm not sure alt+f wipes your ext. there are commands you have to type.
to completely wipe your ext2 and ext3 you have to type:
mount /system/
rm -rf /system/sd/
or at least that's what I always used until I upgraded to ext3.
Click to expand...
Click to collapse
Code:
mke2fs -j /dev/block/mmcblk0p2
that will actually reformat and its less chars
OK, I'm going to stop polluting other threads with my stuff.
This should help make sure I can keep up on the discussions and provide support for people trying to use my ZIPs and/or scripts.
NOTE: This version requires JACs kernel and init.d mods. Flash his stuff, then flash mine. All this will be integrated at some point and any other dev is welcome to integrate my stuff with theirs.
In addition to the JAC kernel, you need an ext partition on the EXTERNAL SD card. DO NOT USE ROM MANAGER TO PARTITION. You will get into a boot loop and will have to Odin back to stock. For partitioning, you may use "adb shell" in clockwork recovery, an old G1/Mytouch with Amon-Ra/Clockwork, a computer with a card reader and GPartd, Paragon, etc.. If you do it with fdisk, don't forget to format the partitions, here are some sample commands.
This will format an ext2 partition.
Code:
/system/bin/mke2fs /dev/block/mmcblk1p2
Convert from ext2 to ext3
Code:
/system/bin/tune2fs -j /dev/block/mmcblk1p2
Convert ext3 to ext4
Code:
/system/bin/tune2fs -O extents,uninit_bg,dir_index /dev/block/mmcblk1p2
fsck, any ext version. Do this when you are done converting between types.
Code:
/system/bin/e2fsck -fpDC0 /dev/block/mmcblk1p2
For all of the above, make sure the partition isn't mounted with "mount". You also have to have already flashed either this ZIP, or my e2fsprogs-ext4 ZIP for the files to be installed in /system/bin.
This version will clean up older versions that I know about. It will remove any use of the playlogos hack, and the older version of my script that JAC included in his kernel.
Quadrant - 1722. I have also not seen any lag from this change. I've tried some apps that make heavy use of the database, and so far it's performing quite well. If you do see problems, I suggest fsck on the ext partition, and perhaps formatting it, to ensure it's nice and clean.
Please note that benchmark results will vary based on a large number of factors beyond my control. Try with a clean phone, no background apps. A faster SD card will help as well. I am using an older Transcend 8GB Class 6 that I used to use on my G1. It doesn't help that the free Quadrant tests lots of stuff, not just activity on /data/data and such.
To see if it's working, open a shell and type "mount". You should see entries like this:
Code:
/dev/block/mmcblk1p2 on /sd-ext type ext4 (rw,noatime,nodiratime,barrier=1,data=ordered)
/dev/block/mmcblk1p2 on /data/dalvik-cache type ext4 (rw,noatime,nodiratime,barrier=1,data=ordered)
/dev/block/mmcblk1p2 on /data/data type ext4 (rw,noatime,nodiratime,barrier=1,data=ordered)
Added data-only ZIP and the disable/revert ZIP.
Added auto-partition ZIP to create 1GB ext3 partition automatically. Note that this will delete ALL SD contents.
Added old-style enable-dc2sd for users of the auto-partition script. Do not use for JAC kernels, use the current dc2sd instead.
Changelog:
8/9/2010: Added loopback style version, should find prior versions and remove them, copying your data from the /sd-ext partition.
v2.
Compatibility fix for JAC -6 kernel.
v1.
Added e2fsprogs w/ext4 support to the ZIP
Better integration with init.d layout
On boot fsck to ensure that the ext partition is kept clean
Automatically copy files if /data has larger directories than /sd-ext
Test versions that should fix busybox to work with the newer JAC kernels. -loop uses the loopback filesystem method (RyanZA style). The other one is for an ext partition on the external SD card.
Feel free to post direct links or links to the kernel thread.
For some reason, the convetr to ext4 command isnt working for me.
Just says "Tune2fs 1.41.6" then back at # prompt
GREAT RESOURCE - Deserves a sticky just for the conversion syntax
EDIT: Maybe not, it said mounted as an ext3 before, now it says ext4
EDIT2: SUCCESS!!!!! EXT4 gives a major boost to the Quadrant score - 1531. WAY better than the~1100 i was getting before. Stupid G1 didnt actually convert ext3 to ext4, even though it said it did. Thanks!
Not that I'm stressin over Quadrant scores, but I just dropped ~100 (previous was 1497) after flashing this. Ah well.
Hmmm, before applying this script, I was just using JAC's v5 kernel, which worked fine, but after applying the OP's script, I cant backup in Clockwork (again lol).
It doesnt seem to mount /data and /datadata, as it only backs up /system and errors out on the other two. Any idea why?
EDIT: The error is really random, Ive now had 2 successful backups, 2-3 that failed due to mount issues, and 2-3 that failed due to MD5 issues. I would like to narrow down the possibilities, and I attempted a restore to stock, rooted, and then used JAC's kernel, same issue occurs (did not use your newest script). That being said, I dont think its your script. (stumped)
When converting to ext4 it said "please run e2fsck on the filesystem"
EDIT: Ran "mount" and it shows same messages you do. So it worked
LovellKid said:
When converting to ext4 it said "please run e2fsck on the filesystem"
EDIT: Ran "mount" and it shows same messages you do. So it worked
Click to expand...
Click to collapse
It's supposed to say that. Do it.
Glad it's working for some of you. As for nandroid, no idea. I'll install jac latest and check it out. Can't think of much I could have done to it though, I can't mod the ramdisk this way.
+1 on the nandroid, I went back and tried and couldnt. Also, tried to flash anamolous deodexed ROM and wouldnt. Gave errors e: cant mount /dev/block etc and failed. Could this be related?
LovellKid said:
+1 on the nandroid, I went back and tried and couldnt. Also, tried to flash anamolous deodexed ROM and wouldnt. Gave errors e: cant mount /dev/block etc and failed. Could this be related?
Click to expand...
Click to collapse
I doubt it, my stuff doesn't run in recovery, at least I don't think it will. I've never seen it run. I'll look into it, but it sounds like the jac mod might have an issue with nandroid right now.
There was a similar issue on the g1 with cm6. I wonder if that fix will work here...
Could you also post the Just DATA, and revert scripts in this thread please
Also, what would be the proper flashing order for just data?
1. JAC init.d
2. reverse
3. Just data
Or do I have to flash init.d, apply kernel, then reboot and flash reverse then just data?
The_Chrome_Coyote said:
Could you also post the Just DATA, and revert scripts in this thread please
Also, what would be the proper flashing order for just data?
1. JAC init.d
2. reverse
3. Just data
Or do I have to flash init.d, apply kernel, then reboot and flash reverse then just data?
Click to expand...
Click to collapse
Added revert and data-only to the OP.
If you don't have any sd-ext hack installed right now:
1. JAC init.d
2. data-only ZIP
3. reboot to download mode and flash the JAC kernel
If you already have dc2sd installed:
1. Revert ZIP
2. JAC init.d ZIP
3. Data-only ZIP
4. reboot to download mode and flash the JAC kernel
If you already have the kernel and the JAC init.d:
1. Revert ZIP
2. Data-only ZIP
I am trying to revert this fix, so I can try the new hack involving a virtual EXT2 partition. I tried the revert, and I manually deleted the a2sd and dc2sd files in init.d, but it rebuilds data when I reboot. ANy ideas?
zimphishmonger said:
I am trying to revert this fix, so I can try the new hack involving a virtual EXT2 partition. I tried the revert, and I manually deleted the a2sd and dc2sd files in init.d, but it rebuilds data when I reboot. ANy ideas?
Click to expand...
Click to collapse
You likely have a script in /system/etc/init.d doing it, or you didn't clean the old playlogos stuff up.
FWIW, I'm working on a similar way of doing it, but with ext4 and a proper init script. I don't like using ext2 for this stuff, too easy to corrupt it.
Does your new loop script require an sdcard with ext 4 partition or does it use the internal sd card?
ttabbal said:
You likely have a script in /system/etc/init.d doing it, or you didn't clean the old playlogos stuff up.
FWIW, I'm working on a similar way of doing it, but with ext4 and a proper init script. I don't like using ext2 for this stuff, too easy to corrupt it.
Click to expand...
Click to collapse
Thanks for your work! I found your dc2-loop-v1 script. Will play w/ that until you come out w/ something better. Is EXT2 really that fragile in terms of corruption when it is virtualized within a journaled file system (which I believe RFS is)
frank707 said:
Does your new loop script require an sdcard with ext 4 partition or does it use the internal sd card?
Click to expand...
Click to collapse
This loop version doesn't use an ext partition. Just the loopback mount. It will copy the files from an ext partition if you have applied that hack.
zimphishmonger said:
Thanks for your work! I found your dc2-loop-v1 script. Will play w/ that until you come out w/ something better. Is EXT2 really that fragile in terms of corruption when it is virtualized within a journaled file system (which I believe RFS is)
Click to expand...
Click to collapse
Most file system journals don't help with the data just the structure. Rfs rides on vfat, so I doubt it's worth much that way.
Gave the dc2-loop script a shot, to convert from the /SD-EXT method to this new ext4 container method. It creates the container correctly, but never seems to copy everything over. All my apps act as if i've never started them up, so Data isnt getting copied over correctly.
EDIT: Tried again, the dc2-loop script def doesnt work, and I have no idea why. It looks perfect (code-wise), but for whatever reason doesnt end up working properly
can't get your loop script working. every other one i have been able to run flawlessly. i just flashed the oc kernel by jac. any further instructions or pre reqs?
Hi all,
Tearing my hair out here (and I have SFA left anyway)
My Father-in-law's SGS i9000 seems to have real issues. Initially problem I was having was that there was an app I could not uninstall- it would reappear on reboot. I initially suspected malware or such, but it appears to be a real problem with the internal memory. I had MIUI installed on it, but wanted to change to a more stock ROM.
First time I really started to worry was when I found that every time I put a new rom onto the internal sdcard, it disappeared at reboot (and thus wasn't there to install when rebooted into CWM)
Since then, haven't had a functioning phone.
adb push to sdcard still not persistent on reboot.
Cannot flash new ROM with ODIN either, although KERNEL changes, filesystem no longer mounts.
I think the version of MIUI I was using used an ext4 lagfix, as inside an adb shell, I can see the partitions:
parted /dev/block/mmcblk0
a "print" lists two partitions:
Number Start End Size Type File system Flags
1 32.8kB 14.4GB 14.4GB primary fat32 lba
2 14.4GB 16.4GB 2013MB primary ext4 lba
rm 1, rm 2
to try to delete the partitions and start again- doesn't work. Nothing happens
If I load partition 2 into parted:
parted /dev/block/mmcblk0p2
print
Model: Unknown (unknown)
Disk /dev/block/mmcblk0p2: 2013MB
Sector size (logical/physical): 512B/512B
Partition Table: loop
Number Start End Size File system Flags
1 0.00B 2013MB 2013MB ext4
Can;t check any partitions as ext4 isn't supported by parted.
I cannot remove any partitions, reformat them or anything.
e2fsck errors as it cant read superblock flags on any of the partitions.
Any other ideas? Anyone?
I don't want to toss the phone out
http://forum.xda-developers.com/showthread.php?t=845708
i dont know if this will help u but u can try this guy instruction. See link above
compacity said:
http://forum.xda-developers.com/showthread.php?t=845708
i don't know if this will help u but u can try this guy instruction. See link above
Click to expand...
Click to collapse
If that worked, it would have been just what I was looking for
I googled the hell out of this problem, and that one never came up, but others I'd seen led me to try that same plan.
Where it fails on my device, is that deleting the partitions in "parted" fails- rm1 followed by rm 2 to delete the partitions. "Print" reveals they're still there.
Any other partition tools worth trying?
I got it back to square one:
Flashed kernel thru Odin with a version of CWM that worked.
reboot into recovery.
Flash update from SDcard- card contents still the same, so could re-flash MIUI.
reboot, bootloop. Re-enter CWM recovery and reflash.
Back to Square One - MIUI 1.12.16 (JVK)
Cannot install anything - nothing is persistent after reboot, even WIFI settings disappear
If it is any help to anyone who knows what they're talking about:
Now that MIUI boots I can look at the filesystem better.
Can anyone point me in the direction of what I should be looking for/trying to do to figure out what is wrong here?
try finding solution here, its PIT stop for i9000 problem
http://forum.xda-developers.com/showpost.php?p=30415128&postcount=1
Mine seems to be a bit tougher than these solutions can deal with.
Tried assorted ROMs over past day. No install works.
Cannot install anything from internal memory, as nothing dropped into that card will remain after a reboot.
Installing anything from an external card just throws up bootloops etc- as the only thing that seems to be able to retained between boots is the kernel/CWM.
If I install a new ROM, first flash says partition table is incompatible and /data will be overwritten (no problems, nothing on it). I accept the inevitable and re-select the ROM.
Reboot bootloops, as expected, reboot into CWM (now a new version with the Kernel), try reflashing the ROM image- Error 0 or 7. Try from External Memory- same. Try sideloading image. Same. All I can do is re-flash the MIUI image on internal SDcard (which works)
It looks like the internal memory refreshes itself from a recovery image at each boot? (I think).
Anyway- can't get anything to stick, except MIUI
edit:
http://forum.xda-developers.com/showthread.php?t=761537&page=3
http://forum.xda-developers.com/showthread.php?t=1230059&page=3
hav u try this 2 link as this is da only thread matches ur MBR problem
compacity said:
did u try any jb kernel out there? as its also ext4 n push it using adb. juz a suggestion though.
Click to expand...
Click to collapse
Good suggestion Logical
I'd thought that also- The JB kernels should support ext4.
No joy though
The version of CWM recovery that is stable with the MIUI install is 5.0.2.7, and it doesn't have any voodoo/lagfix options
When I flash a kernel with a CWM with lagfix, and try to use the CWM lagfix toggles, nothing changes.
Doesn't matter what I select inside CWM, it reads the status from memory as "Lagfix on, Debug off"
The reason I asked about ext4 tools in ADB is that running filesystem commands in a shell just throws up errors I can't seem to fix.
e2fsck just throws up superblock errors (on both /dev/block/mmcblk0 and the partition /dev/block/mmc0p2.
Defining one of the backup superblocks doesn't help- they're all bad.
"parted" doesn't work anymore (i note it isn't in /sbin, so I am picking this kernel doesn't install it), but even when I did have it, "parted" doesn't support ext4. Using "rm" to remove a partition did exactly nothing.
Starting to think the only way forward would possibly be flashing a custom .pit file to define partitions that move the data off an obviously bad block? Above my skill level however LOL
refresh browser see my post above again