CM7/Zeus v7alongside any rom with GB bootloader and CM7 alongside v28a
Hi!This is my"how to" for installing two roms on one OB.
1.We need to partition sdcard
partition #1 : format it to fat(will be used as sdcard)
partition #2 : format it to ext4(will be used as system of zeus and must be at least 320 MB)
partition #3 : format it to ext4(will be used as data of zeus and must be at least 400 MB)
2.Now if u want:
1.Zeus flash this
2.cm7 flash this
(DO NOT FORGET TO PUT YOUR INTERNAL ROM`S KERNEL TO /sdcard/boot/ and name it nandboot.img!)
3.cm7 alongside v28a flash first this, then flash v28a with SFT, then root your v28a and after that put files from this bin.zip to the /system/bin
3.Now if u want to boot:
1.Zeus type in the terminal
Code:
su
bootzeus
2.cm7 type in the terminal
Code:
su
bootcm7
3.v28c ICS
Code:
su
bootsd
4.your nand rom
Code:
su
bootnand
NOTE:If u change your nand rom first install your new rom and after that copy your new rom's boot.img and put it to /sdcard/boot.img and after that rename it to nandboot.img and after all this install this if your sdrom is cm7 and if Zeus this
Now partition table is:
Code:
Zeus/CM7/v28c ICS
system /dev/block/mmcblk1p2
data /dev/block/mmcblk1p3
CM10
system /dev/block/mmcblk0p8
data /dev/block/mmcblk0p9
YouTube
suleymanovemil8 said:
Hi!So is it possible to boot android from sdcard?I think changing root directory to mmcblk1 in the default kernel kommand line could help, have anyone done smthing like this before?
Click to expand...
Click to collapse
Even if it works you'll still be using the same kernel and ramdisk which will only work on ROM very similar to your base.
Sent from my LG-P970
look what i've found http://forum.xda-developers.com/showthread.php?t=1642185
suleymanovemil8 said:
look what i've found http://forum.xda-developers.com/showthread.php?t=1642185
Click to expand...
Click to collapse
I had a look. It looks promising. Its quite a cheap trick and should work on our phone.
I am on my phone now so I can't study what he did in detail and I'm not entirely sure how he handles kernel switching (yet).
It's a good find.
EDIT: Nothing to do with kernel root or command line though.
Sent from my LG-P970
xonar_ said:
I had a look. It looks promising. Its quite a cheap trick and should work on our phone.
I am on my phone now so I can't study what he did in detail and I'm not entirely sure how he handles kernel switching (yet).
It's a good find.
EDIT: Nothing to do with kernel root or command line though.
Sent from my LG-P970
Click to expand...
Click to collapse
I`ve made script for OB and it works
HTML:
cat /sdcard/boot/sdboot.img > /dev/block/mmcblk0p3
echo Rebooting to SD Rom. Please wait...
sleep 3
reboot
return 0
I have repacked zeus rom`s kernel with sd mounts and put the system partition to mmcblk1p1 but it looks like smthing goes wrong(if sdcard is inserted it reboots to recovery in a few seconds but if I remove sd card it stucks at lg logo) and it have created app, data, etc. folders on data (sd) partition
suleymanovemil8 said:
I`ve made script for OB and it works
HTML:
cat /sdcard/boot/sdboot.img > /dev/block/mmcblk0p3
echo Rebooting to SD Rom. Please wait...
sleep 3
reboot
return 0
I have repacked zeus rom`s kernel with sd mounts and put the system partition to mmcblk1p1 but it looks like smthing goes wrong(if sdcard is inserted it reboots to recovery in a few seconds but if I remove sd card it stucks at lg logo) and it have created app, data, etc. folders on data (sd) partition
Click to expand...
Click to collapse
Make so that it only mount the sd partitions if the sd card is present and is made to be bootable.
Reflashing the boot.img isn't a nice way of doing it since bad flash would result in a bootloop. Linux has the ability to reload a kernel without shutting down. I don't know if the kernel that we use can do that maybe it's worth looking into.
Sent from my LG-P970
xonar_ said:
Make so that it only mount the sd partitions if the sd card is present and is made to be bootable.
Reflashing the boot.img isn't a nice way of doing it since bad flash would result in a bootloop. Linux has the ability to reload a kernel without shutting down. I don't know if the kernel that we use can do that maybe it's worth looking into.
Sent from my LG-P970
Click to expand...
Click to collapse
as i said "and it have created app, data, etc. folders on data (sd) partition"
What if i will move /system #2 to /data partition and both of the systems will have data partition on sdcard?
PS. It worked!Now I have data partition on mmcblk1p2
here it is(this is kernel for cm10(26.10.2012))
suleymanovemil8 said:
What if i will move /system #2 to /data partition and both of the systems will have data partition on sdcard?
PS. It worked!Now I have data partition on mmcblk1p2
Click to expand...
Click to collapse
What are you going to do with the GB thats on the phone and not used?
EDIT: its rebooting to recovery because the kernel is set to reboot to recovery when it's 'panicking'.
Sent from my LG-P970
xonar_ said:
What are you going to do with the GB thats on the phone and not used?
Sent from my LG-P970
Click to expand...
Click to collapse
no this kernel boots with normal system and data at sdcard and now i will make kernel with booting from data directory and with data at sdcard)
YES! I have now two roms on one phone!
suleymanovemil8 said:
YES! I have now two roms on one phone!
Click to expand...
Click to collapse
Do a walkthrough for us! :laugh::laugh:
genarinho said:
Do a walkthrough for us! :laugh::laugh:
Click to expand...
Click to collapse
Yes ,pls
sent from my Nokia 1100 with droid 4.0
Just everyone thats reading this know that it still booting from phone and then reading data from sd. (Not true dualboot yet )
@ sulley
Why not use recovery as the phone boot.img and then normal boot then goes of two sd. CWM sources are available and can be modified so that it works as a boot manager. It will then be actual dual boot because from there you can load kernel from either sd or phone (and unload the recovery kernel and with its dying breath start the new kernel ).A project like this will take A LOT of time and will definitely be more than 6 months. Since it would be based on recovery it should be able to make it work for all phones that can use CWM and have similar boot structure. I will help out on a project like this but I can't be that involved with it since my studies will take up most of my time.
As much I understand, bootloader is needed for dualboot and it applies same on Android. So you got access to our bootloader or just directing the boot.img from 1st ROM to 2nd one? Like handshaking?
xonar_ said:
Just everyone thats reading this know that it still booting from phone and then reading data from sd. (Not true dualboot yet )
@ sulley
Why not use recovery as the phone boot.img and then normal boot then goes of two sd. CWM sources are available and can be modified so that it works as a boot manager. It will then be actual dual boot because from there you can load kernel from either sd or phone (and unload the recovery kernel and with its dying breath start the new kernel ).A project like this will take A LOT of time and will definitely be more than 6 months. Since it would be based on recovery it should be able to make it work for all phones that can use CWM and have similar boot structure. I will help out on a project like this but I can't be that involved with it since my studies will take up most of my time.
Click to expand...
Click to collapse
Well I have installed rom's kernel to the recovery partition but after booting to this new kernel i couldn't boot back tonormal kernel till i reflashed recovery from rom manager
ps.recovery partition is at mmcblk0p4 and boot mcblk0p3
genarinho said:
Do a walkthrough for us! :laugh::laugh:
Click to expand...
Click to collapse
tada!
As I expected, not real dualboot. But very much appreciting try. Keep it up
Anyway i still want to make one rom at nand and anouther on sdcard, but if i set in kernel system directory to mmcblk1p1(sdcard) it starts to boot but smthing goes wrong but it starts to boot and i know it because it creates app, data, app-private etc. folders on data partition of sdcard(mmcblk1p2), i think this is because it remounts sdcard or smthing like this.Any ideas about soving this problem?
Related
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
As many people where demanding a Ext4 Kernel I created one and added a Filesystem conversion script.
This does only work on Gingerbread ROMs cause the bootloader is different!
On Froyo it will cause the device not to boot into the normal android system. Don't flash it if you are not on a Gingerbread ROM.
I have tested it with KPH but it should work on all Gingbread ROMs that have a updated bootloader.
FS converter? WTF???
This converts (formats) all your internal partitions (system, data, cache) with Ext4.
This way you don't have to use RFS which performance is pretty poor.
How to install?
Install CWM (there some threads here how to do this)
Make a Nandroid backup of your system (this is essential otherwise all your data will be lost!!!)
Install the ext4-update.zip (this will format your partition into EXT4 and flash a new Kernel)
Go into "mounts and storage" -> unmount cache (if it is mounted)
Go to "backup and restore" -> "advanced restore"
Choose the backup you made before -> Restore System & Data (cache is not needed it is rebuild on the next reboot)
Reboot
Don't panic (it will take some time to rebuild the dalvik cache,
just like the first boot after you flashed a new rom with ODIN)
Follow those instructions otherwise all your data will be lost and i make fun of you!
This will install a Kernel that has EXT4 support and a modified init.rc to mount both ext4 and rfs partitions.
Ok enough talked, where can I get this ****? Here MD5: 369808990ff8d45065f0cdd8fbb3f8b8
WTH you bricked my Phone
This is impossible. Except your CWM is buggy. You phone doesn't boot up, you are stucked at the samsung logo?
Ok then we need some information from you. Did you hear the start-up sound the the samsung logo player?
How long did you wait?
Try to adb to the phone and give me the output from "mount" and "logcat" on pastebin.com pls.
Please tell us witch rom you were running. I am not sure if this will work with any custom rom cause i only tested stock
You can fully revert by flashing a Full ROM with ODIN. Then install cwm and restore the backup you created before.
How did you create this?
I simply build the kernel source added Ext4 support. Kernel source is on github
Then I created a new initramfs by dumping the stock one doing the modifications and repacking it. The Initramfs is also on github. This should help anyone of you trying to the some on your custom kernel.
Cool dude ....
Is this a OC kernel ?>???
Nice work dude for this 1 ....
Appreciate ur work
Great work...
Getting ext4 support means it will format the sd card fully or just creates a partition with the free memory left in the sd card?
Sent from my GT-S5830 using XDA App
Aadigoku13 said:
Cool dude ....
Is this a OC kernel ?>???
Nice work dude for this 1 ....
Appreciate ur work
Click to expand...
Click to collapse
nope nothing touched except FS support. I think i won't add anything like that cause it want to save my time to work on CyanogenMod. But everyone feel free to modify the source and do it
adiles said:
Great work...
Getting ext4 support means it will format the sd card fully or just creates a partition with the free memory left in the sd card?
Sent from my GT-S5830 using XDA App
Click to expand...
Click to collapse
it does not touch your sd card. it simply formats the internal partitions to ext4.
hot bro just waited for this......
waiting to see your other work....
and what is FS converter????sry for noob question..
coolya said:
nope nothing touched except FS support. I think i won't add anything like that cause it want to save my time to work on CyanogenMod. But everyone feel free to modify the source and do it
Click to expand...
Click to collapse
Are you working on CM for ACE? Thx for kernel, nice work. )
There is no RFS filesystem's source in your source, how do you compile a kernel supporting RFS?
fzn0268 said:
There is no RFS filesystem's source in your source, how do you compile a kernel supporting RFS?
Click to expand...
Click to collapse
samsung just give we modules for rfs support.
it included in boot.img
what are the advantages of using EXT4 as filesystem?
downloadonlyaccount said:
what are the advantages of using EXT4 as filesystem?
Click to expand...
Click to collapse
Its a journaled file system, meaning it keeps track of all changes made to the file system in a journal making it much faster than samsung's rfs file system.
@coolya
Thanks for this!
Does this Kernel only support SD card EXT4 partitions or does it convert the phone memory to EXT4 as well(thats what i understand by the FS coverter script).
kills999 said:
Its a journaled file system, meaning it keeps track of all changes made to the file system in a journal making it much faster than samsung's rfs file system.
@coolya
Thanks for this!
Does this Kernel only support SD card EXT4 partitions or does it convert the phone memory to EXT4 as well(thats what i understand by the FS coverter script).
Click to expand...
Click to collapse
it converts all internal partitions into Ext4, /system, /data and /cache
But how to use them? I want to build a Froyo kernel supporting ext4 and RFS.
coolya said:
it converts all internal partitions into Ext4, /system, /data and /cache
Click to expand...
Click to collapse
thanks!!
that means it will also support SD card EXT4 APPS2SD partitions right??
kills999 said:
thanks!!
that means it will also support SD card EXT4 APPS2SD partitions right??
Click to expand...
Click to collapse
the kernel is Ext4 enabled you can use where ever you want, you just have to mount the partition right.
is there any way to revert changes made? just in case we may want to claim warranty..
thank you for this awesome work!
guyz i am having a problem...
i just installed this file and after that my phone just got stuck on the samsung logo after reboot...
i followed all the steps but dnt know what happ..
tj_style said:
samsung just give we modules for rfs support.
it included in boot.img
Click to expand...
Click to collapse
How to use these modules?
digkong said:
guyz i am having a problem...
i just installed this file and after that my phone just got stuck on the samsung logo after reboot...
i followed all the steps but dnt know what happ..
Click to expand...
Click to collapse
i had the same problem , just restore cache too and it will be working again
mundixx said:
is there any way to revert changes made? just in case we may want to claim warranty..
thank you for this awesome work!
Click to expand...
Click to collapse
Flash stock kph with odin...
This is a modified CWM-based recovery for the Motorola Atrix 4G. It is based on my own custom code forked from the CyanogenMod team's recovery. The major changes I have made include full support for dual SD cards, support for webtop partitions (SD card and internal) and changes to Nandroid backup/restore for this phone's additional partitions.
Some highlights include:
Dual SD card support
ADB support
USB Mass Storage support
Nandroid additions/changes
ext3/4 formatting
Unified kernel for international users
Probably others
This recovery is only for UNLOCKED devices. It is intended to be flashed directly to the recovery partition. Additionally, I have an AT&T phone so that is the kernel I am using. I doubt the memory issue would matter in recovery mode but testing from UNLOCKED international users would be appreciated. UPDATE: Initial indications are it works fine on UNLOCKED international phones. Versions for different tegraparts have also been compiled. UPDATE 2: Unified kernel patch has been applied. Choose whatever color you prefer regardless of phone version!
UNLOCKED users can flash this recovery using:
Code:
moto-fastboot devices
moto-fastboot erase recovery
moto-fastboot flash recovery recovery-atrix5.img
Example from my phone:
Code:
$ moto-fastboot devices
TA20700KXH fastboot
$ moto-fastboot erase recovery
erasing 'recovery'... OKAY [ 0.741s]
$ moto-fastboot flash recovery recovery.img
sending 'recovery' (4780 KB)... OKAY [ 0.490s]
writing 'recovery'... OKAY [ 0.544s]
This is posted in a DEVELOPER forum and is being released to help further the development of Android for the Motorola Atrix 4G. I have personally tested this on my phone but YOU assume full responsibility for any damage incurred to YOUR phone!
Click to expand...
Click to collapse
ALL USERS
Orange 5.0.2.7-atrix5 / ZIP version.
MD5 aebe29124d8c6d6c4b9873bd9ea4ca3b / 1f9a1d6fc83610e5c7c8f2d60e489b69
Cyan 5.0.2.7-atrix5 / ZIP version.
MD5 eb44b910983434d3996383098dff53b6 / 91365993488a9ae060b22c8b820d1c5b
Light green 5.0.2.7-atrix5 / ZIP version.
MD5 e7c7ec152e9e3269ef2ab1ce99b8943e / 1e720c8760898549226a10d4776f5077
Dark green 5.0.2.7-atrix5 / ZIP version.
MD5 c8a4438e5889d5e681a754555c40bc51 / 121d8d9102eac3ed24f1e0be6f8cd5d1
Blue 5.0.2.7-atrix5 / ZIP version.
MD5 9a1fd3c8796d2e768b54d39143c17ea3 / 9059c0c37fd2c547ec8508c893986815
Red 5.0.2.7-atrix5 / ZIP version.
MD5 036a9d9cc390a6071011d4d50b008875 / aa069d1aed20c5cbd13b2098b6a88975
Original ROM Manager installable zip thanks to SolidHelix. You must still be UNLOCKED to use them.
Source is here.
A few notes:
The capacitive buttons can be used to navigate as well. Back is back, search is select. Menu and home are up and down.
The "osh" partition is webtop. It is the largest by far and will take some time to backup. Nandroid is not frozen!
The "sd-ext" partition is an ext3/4 partition on your external SD card. Veterans will know this as apps2sd and data2sd from other phones. The only use I'm aware of on our phone currently is Sogarth's webtop2sd.
Thanks to:
Koush and the CM team for CWM
Everyone who has made unlocking the Atrix possible
** Changelog **
2011-11-14 (5.0.2.7-atrix5):
Minor bugfix release mostly
Added the ability to convert an ext3 partition to ext4 under advanced. Shouldn't break anything, but it is experimental.
2011-09-24 (5.0.2.3-atrix4.1):
Fix an issue with using ext4 formatting on stock ROMs
2011-09-23 (5.0.2.3-atrix4):
Updated to CWR5 base source.
The blue version is now the new CWR5 color. Old blue is gone. New photos welcome!
2011-09-17 (4.0.1.5-atrix3.3):
Unified kernel patch from eval-
New kernel to fix the stuck at "Entering Android Recovery" prompt. Big thanks to bamastang for helping test this.
Added a verify option to the backup and restore menu.
Renamed internal SD card mount point to /emmc and external is now /sdcard (this is largely cosmetic).
Merged in the CM7 device config when building the recovery image (again, just cosmetic).
Merged in miscellaneous fixes from the official CWM. Version 5 will be merged in once its ready.
2011-08-17 (4.0.1.5-atrix3.2):
Added 0MB option to ext3 partition size under External SD card partitioning which removes any ext3 partitions from the card (choose 0MB ext3/0MB swap to have only a FAT32 partition).
Added a red build to the mix.
Updated the update-binary in the CWM zips to be tailored for this phone.
Minor fixes to sdparted (log file related mostly).
2011-08-14 (4.0.1.4-atrix3.1):
Swap kernels to re-enable soft keys. Ext4 support should still work.
Fix for external SD card partitioning (internal is not supported).
CWM zip changed slightly.
2011-08-12 (4.0.1.4-atrix3):
Experimental ext4 support. Thanks to SolidHelix for testing it.
Fix for restoring large yaffs2 images (greater than 10,000 objects).
Tweak to the SD card space check before starting Nandroid backup.
Miscellaneous minor bugfixes and tweaks.
2011-08-07 (4.0.1.4-atrix2):
User is now prompted to wipe sd-ext (webtop2sd) on "Wipe data/factory reset".
User is now prompted to backup or restore webtop (/osh and /sd-ext) during Nandroid.
Four alternate colors created.
Versions for different tegraparts (international phones) created.
2011-08-05 (4.0.1.4-atrix1):
Initial release
Screenshots
Thanks to DarkSim2o9 for the following screenshots:
Orange
Cyan
Blue
Light green
Dark green
Red
Known Issues
sd-ext (webtop2sd) is inadvertently wiped on "Wipe data/factory reset". Next version will make this optional. Fixed in -atrix2.
Miscellaneous
If you'd like ROM Manager to see this recovery as "official" you can try XCellPhoneSalesRep's suggestion posted here.
Alternately, you can try dcarpenter85's suggestion here.
For issues with recovery not sticking or crashing, see here:
Thanks to mrinehart93 for pointing this out.
The system runs /system/etc/install-recovery.sh on boot with the stock rom. On boot it checks the recovery partition for some update and with CWM installed decides to reflash the stock recovery over it. Rename or delete the file and the CWM should stick.
Click to expand...
Click to collapse
Old versions
You can browse and download old versions here.
If I currently have tenfar's latest recovery, is it worth installing this one?
xploited said:
If I currently have tenfar's latest recovery, is it worth installing this one?
Click to expand...
Click to collapse
yes..Nandroid support
ok.. for some reason I can not enter recovery with Tenfar's or this CWM... I can enter it when plugged into AC using the Root Manager CWM.. Any ideas? I always get stuck at the "Entering Android Recovery Mode" screen and that is it... Any help would be greatly appreciated.
bamastang said:
ok.. for some reason I can not enter recovery with Tenfar's or this CWM... I can enter it when plugged into AC using the Root Manager CWM.. Any ideas? I always get stuck at the "Entering Android Recovery Mode" screen and that is it... Any help would be greatly appreciated.
Click to expand...
Click to collapse
were you using Tenfar's old version.
I had at one-point tried using the old version... after trying to flash the new version and having the problem. I flashed the new version I believe right after unlocking (first time flashing the CWM) It had never worked on my phone unless I used the ROM Manager version. I was hoping this would take care of the issue since I did the erase recovery and flashed this...
munchy_cool said:
yes..Nandroid support
Click to expand...
Click to collapse
So, backup and restore is COMPLETELY working on this recovery?
Sent from my MB860 using XDA App
bamastang said:
I had at one-point tried using the old version... after trying to flash the new version and having the problem. I flashed the new version I believe right after unlocking (first time flashing the CWM) It had never worked on my phone unless I used the ROM Manager version. I was hoping this would take care of the issue since I did the erase recovery and flashed this...
Click to expand...
Click to collapse
Hmm not sure I've experienced that. Do you have install-recovery.sh in /system/etc? Maybe it's conflicting
Javi97100 said:
So, backup and restore is COMPLETELY working on this recovery?
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Very interested in this as well. The big problem (only problem iirc) with Tenfar's is its inability to properly backup and restore the PDS partition.
If this release gives us all of the features of the official CWM, I will be ecstatic!!!
DK
Javi97100 said:
So, backup and restore is COMPLETELY working on this recovery?
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
It should be from my tests, but you should also test it.
romracer said:
It should be from my tests, but you should also test it.
Click to expand...
Click to collapse
I have several backups of my PDS partition. I am very busy tonight, but was planning on spending tomorrow re-building my laptop. So while I'm doing that I'll do a backup, wipe, and restore to see what happens and report back.
DK
DeathKoil said:
Very interested in this as well. The big problem (only problem iirc) with Tenfar's is its inability to properly backup and restore the PDS partition.
If this release gives us all of the features of the official CWM, I will be ecstatic!!!
DK
Click to expand...
Click to collapse
PDS is definitely backed up. It's not restored by default, just as a wimax partition is not on those devices that have them. It is available under Advanced Restore but you should help test it and have a separate backup just in case.
Backup early and backup often.
romracer said:
Hmm not sure I've experienced that. Do you have install-recovery.sh in /system/etc? Maybe it's conflicting
Click to expand...
Click to collapse
The only install-recovery.sh I had was in the /etc not in the /system/etc
I don't know if there is something missing that CWM is dependant on or what. But like I said if I use the one from ROM manager which is 4.0.1.4 I can boot into recover with the plugged in via AC.
Bug during backup?
So I am starting my backup of my phone using this recovery.
I booted into recovery, chose "Backup and Restore", then chose "Backup", and finally told it to makeup to the external card.
Here is my output:
CWM-based Recovery v4.0.1.4-atrix1
SD Card Space free: 4331MB
Backing up boot image...
Backing up recovery image...
Backing up system...
Backing up data...
Backing up .android-secure...
Backing up cache...
No sd-ext found. Skipping backup of sd-ext.
Backing up osh...
Backing up pds...
Generating md5 sum...
Backup complete!
It seems somewhere in the backup code it tries to backup the contents of the SD-Card (external), but the mount point is referenced as "sd-ext" instead of "sdcard-ext".
This isn't a big deal for me at all, as I only have videos and music on the external card - both of which I have copies of on my PC. For some people, they may want to be able to backup the external card as well.
Edit: In the advanced restore options there is also an option to restore the external sdcard, but it is against referenced as the mount point "sd-ext" instead of sdcard-ext".
Like I said, I'll wipe the phone clean tomorrow and test restore it then make a new post with the results.
So far so good!!
DK
bamastang said:
The only install-recovery.sh I had was in the /etc not in the /system/etc
I don't know if there is something missing that CWM is dependant on or what. But like I said if I use the one from ROM manager which is 4.0.1.4 I can boot into recover with the plugged in via AC.
Click to expand...
Click to collapse
Boot regularly and then in Settings enable USB Debugging. From a command prompt, "adb devices" should show your phone. From there, "adb reboot recovery" and wait 10-20 seconds.
Does that get you into recovery? Does the "Motorola Dual Core" boot image change at all when you try to boot into recovery? Like to a little Android guy with a yellow hazard sign?
The "plugged into AC" recovery is just a hijack of the normal system, so if your phone boots normally I'm not surprised that method works.
DeathKoil said:
So I am starting my backup of my phone using this recovery.
I booted into recovery, chose "Backup and Restore", then chose "Backup", and finally told it to makeup to the external card.
Here is my output:
CWM-based Recovery v4.0.1.4-atrix1
SD Card Space free: 4331MB
Backing up boot image...
Backing up recovery image...
Backing up system...
Backing up data...
Backing up .android-secure...
Backing up cache...
No sd-ext found. Skipping backup of sd-ext.
Backing up osh...
Backing up pds...
Generating md5 sum...
Backup complete!
It seems somewhere in the backup code it tries to backup the contents of the SD-Card (external), but the mount point is referenced as "sd-ext" instead of "sdcard-ext".
This isn't a big deal for me at all, as I only have videos and music on the external card - both of which I have copies of on my PC. For some people, they may want to be able to backup the external card as well.
DK
Click to expand...
Click to collapse
"sd-ext" refers to an ext3 partition on the external SD card. On other phones, this is used for crap like "data2sd" and "apps2sd". On our phones, the only current use I've seen of this is for Sogarth's webtop2sd.
Standard CWM does not backup SD card contents (it backs up to them) so there is no support for that in mine. I could consider adding it eventually.
You will see references to "sdcard-ext" in my recovery if you do something like Apply update.zip and then choose External SD card (look at the path it shows you for update.zip on the confirm screen).
I used to get issues to wipe data in the original 4.0.1.4
Is data wipie fixed in this custom recovery?
guidoido004 said:
I used to get issues to wipe data in the original 4.0.1.4
Is data wipie fixed in this custom recovery?
Click to expand...
Click to collapse
Yes. I have personally tested this particular item a few times. mke2fs from Koush's CWM segfaults, but I have supplied a working one.
Will you be including international support?
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
Hi to all again! I've done another little mod to make our low-end device with too low internal memory (10 apps and is full!) a little bit larger.
This script is a modded d2ext wrote originally by cronmod. This init.d script mounts the /sd-ext partition as /data moving the entire partition in the sd-ext (previously created by the recovery!!).
I have to advise you that the partition MUST be more than 1GB (it moves the entire partition, so if you have it very small it's useless!!).
If you want to install/backup/restore it, you must have this recovery made by me:
http://forum.xda-developers.com/showthread.php?t=2283641
That's because the updater-script mounts the /sd-ext and moves everything from /data leaving it totally empty.
So if you don't want to make a factory reset you have to use my recovery, sorry.
Istructions:
1) Flash the new recovery from the link above
2) Download the attachment and put it into your phone's sdcard
3) Boot into recovery
4) Wipe cache/dalvik-cache
5) Install the zip
6) Reboot into system
EDIT: The .zip provided is in test because I've already put the script in the CM zip before installing it on my phone. Tell me if it works or not and I'll make modifications.
Here's the screenshot of my phone with a "/data" partition of 2GB!!:victory:
when i partitioned my sd card in 2 GB, the 2 GB partition just disappeared, only the 12 GB was left...what to do?
and also tell me how to un-partition it.
Whoa awesome works thanks
Sorry but I made an error in the updater-script. It didn't set the right permission . Now it's correct here: www.4shared.com/zip/SkBxf9FB/Data2ext_signed.html
Aggror said:
when i partitioned my sd card in 2 GB, the 2 GB partition just disappeared, only the 12 GB was left...what to do?
and also tell me how to un-partition it.
Click to expand...
Click to collapse
How did you partiton the sd?
Thanks 4 sharing
TouchWiz-e400 v1 (coming nxt month)
Finaly i find a way to make phone to boot from SD (Android 5.0.2)...but i need a app (or recovery script) to swith with Internal Rom..
Any can help me?
Done..I find a way. I flash boot.img for internal/external (if i need internal i flash internal, if i need external i flash external)
Use Internal with Android 4.4.4 and External with Android 5.0.2
il3gal said:
Finaly i find a way to make phone to boot from SD (Android 5.0.2)...but i need a app (or recovery script) to swith with Internal Rom..
Any can help me?
Done..I find a way. I flash boot.img for internal/external (if i need internal i flash internal, if i need external i flash external)
Use Internal with Android 4.4.4 and External with Android 5.0.2
Click to expand...
Click to collapse
Can you please explain what you did? You are the first person Ive read about who enabled dual boot for the i9305! AND EVEN WITH LOLLIPOP:laugh:
il3gal said:
Finaly i find a way to make phone to boot from SD (Android 5.0.2)...but i need a app (or recovery script) to swith with Internal Rom..
Any can help me?
Done..I find a way. I flash boot.img for internal/external (if i need internal i flash internal, if i need external i flash external)
Use Internal with Android 4.4.4 and External with Android 5.0.2
Click to expand...
Click to collapse
How? can you make a tutorial for the dual boot process?
Sorry about that but i dont now so much about android. I find blocks for SD Card and i modify boot.img (for external rom)
I explain on large.
Legend:
iBoot = Internal Boot.img
eBoot = External Boot.img
First time do a full backup on sdcard and rom. (i make from recovery)
1. Make a backup on iBoot from Terminal: dd if=/dev/block/platform/dw_mmc/by-name/BOOT of=/sdcard/iBoot.img
2. (i mount sdcard from recovery to partitioning) Make a 3 other partition (i use MiniTool) for system/cache/data
First partiton is SD CARD (fat32) (i split from here 7gb..i have sd 16gb)
Second is a primary ext4 partition for system..i put 1,5gb
Third is a primary ext4 partition for cache..i put 800mb
And last is a primary ext4 partition for data..i put free remaining..~4gb
3. On External Rom, need to unpack boot.img and go to fstab. file to replace:
/dev/block/platform/dw_mmc/by-name/SYSTEM to /dev/block/mmcblk1p2
/dev/block/platform/dw_mmc/by-name/CACHE to /dev/block/mmcblk1p3
/dev/block/platform/dw_mmc/by-name/USERDATA to /dev/block/mmcblk1p4
and repack boot.img
(and make a copy on desktop like eBoot.img) put back on archive and go to META-INF\com\google\android\updater-script and edit ALL line
/dev/block/platform/dw_mmc/by-name/SYSTEM to /dev/block/mmcblk1p2
/dev/block/platform/dw_mmc/by-name/CACHE to /dev/block/mmcblk1p3
/dev/block/platform/dw_mmc/by-name/USERDATA to /dev/block/mmcblk1p4
save..sign archive
4. make 2 archives with iBoot.img and eBoot.img (to switch bethen need a normal flash iBoot or eBoot) (i put 1 archive in attachament for eBoot...for example)(for switch rom need to flash boot.img for Internal or External rom)
5. Flash External Rom (with meta and boot.img changed)
6. Reboot..wait to external rom make files (data files and others)
7. If you want to change rom, enter in recovery and flash iBoot (for internal) and eBoot (for external).
I use 4.4.4 (AMCHA Rom KK for i9305) (for internal ..and this is rom for daily)
And 5.0.2 (NamelessROM 2.0 [BETA] [20150106][Blazing Fast]) (on external..temporary)
I dont now if it work with all rom
I'm not developer
If you dont now how unpack/repack boot.img or sign a zip file..search on google, dont ask me about this
I'm realy happy if a developers was extend this and make a Kernel for this (or App)
i'm inspire from http://forum.xda-developers.com/showthread.php?t=2639112
Sorry for english...And i dont now if this method works for everybody.
edit: Dont forget to unmount /system /data /cache partition before flash ExternalROM.
Thanks for the tutorial, I will try to reproduce the steps when I'm free. Don't worry your English is comprehensible.
LucasBass said:
Thanks for the tutorial, I will try to reproduce the steps when I'm free. Don't worry your English is comprehensible.
Click to expand...
Click to collapse
For some reason if flash eBoot and use External Rom..and you want to go back on Internal Rom..when flash iBoot and restart phone..some time was stuck in bootloader..for solve this (temporary i think), go back in cwm..flash again iBoot, go to Advanced and Reboot in CWM..after phone reboot in cwm, press Reboot devices (normaly)..i dont now why is this problem
other thing is: you can flash without problem other rom on internal. (i try today to flash again 4.4.4). external not affected BUT after flash, need to make backup on iBoot ..i dont now why (because i flash same rom with same configuration)..
Now i use on external: Resurrection_Remix_LP_v5.3.0-20150119-i9305.zip and it works grate
I like people who like try new things . If you need help or you stuck , pm me.
Good luck
Hehe
You mean, you did it as well? and you will try to write it down. Or you will start trying.
I have only once repartioned something before, so I'll wait for good instructions.
Uberharm said:
You mean, you did it as well? and you will try to write it down. Or you will start trying.
I have only once repartioned something before, so I'll wait for good instructions.
Click to expand...
Click to collapse
I'm sorry about instructions..but i search on google all info for try Dual Boot...i dont speak english because i'm from Romania.
I try to explain how i make Dual Boot (manualy) for developers...to make this option much easy..
Someone really needs to make a script! I think this could be implemented in a custom recover. All we need now is just a complete step by step guide.
Thanks in advance to the developer who's going to write this down! ☺