Related
Custom MTD Partitions
This is an implimentaion of lbcoder's Custom partition layouts
be sure to checkout that thread for the full history
What does it do?
Well, basically Custom MTD Partitions resizes your MTD partitions
for instance this is a CM6.1RC1, ( heavily customised )
Code:
Filesystem Size Used Available Use% Mounted on
/dev/block/mtdblock3 73.0M 72.8M 236.0K 100% /system
/dev/block/mtdblock5 134.8M 107.2M 27.6M 80% /data
/dev/block/loop0 896.0K 896.0K 0 100% /system/lib/modules
/dev/block/loop1 4.0M 4.0M 0 100% /system/xbin
/dev/block/mmcblk0p2 457.4M 201.8M 231.1M 47% /sd-ext
/dev/block/mmcblk0p2 457.4M 201.8M 231.1M 47% /cache
/dev/block/mtdblock4 2.0M 776.0K 1.2M 38% /dev/cache
most of my Apps are on sd-ext, dalvik-cache is on data
/dev/cache is where the real cache partition is mounted, /cache is actually a bind mount from /sd-ext/cache
Applicable to..
Probably any device that uses the same kind of nand as the G1 MT3G ( msm_nand )
The intial scripts are geared towards G1 / MT3G. however I have 'rewritten' much of the script for v1.5 , it now reads the partition table in dmesg, so it _should_ be universal **
v1.5.3 confirmed to work on heroc
v1.5.6 confirmed to work on bravo + bravoc ( with S-OFF )
unsure if it will work with your device? checkout the source on github ( or ask your favourite dev to take a look )
The 'Tech' in Breif
This method is beautifully simple...
When booting we give the kernel the mtd partition table we want to use..
Thats it
In practice we need to do this when booting to recovery, and booting the rom.
below are files to make this as simple flashing a rom.
Credits :-
Lbcoder - for coming up with the idea
Skraw ( CM forums ) - for getting lbcoder interested
Koush - for AnyKernel
Cyanogen & Co - for giving us all such great ROMs to play with
Amon_RA and Koush - for giving us something to patch
Techjosh - for fixing the patchers for use with Rogers (EBi1)
Mblaster - for pointing out my nasty habit of using -r zip flag at the end of command ( breaks compatibility with older zip versions, fixed in AutoPatcher v1.5 )
Safety First
This method is safe, however it is not without risk
Two things could potentially go wrong
Recovery flash corrupt
This is extremely unlikely, and tbh could happen anytime you flash recovery
If in the very unlikely event that you find you can't reboot to recovery you have three options
re-flash recovery via fastboot ( the preferred option )
re-flash recovery via ROM ( not a great option with cm5.0.x/cm6 )
Do the whole root thing all over again ( no one wants to do that )
system, cache , data partition unmountable - corrupt
Under the right ( or wrong ) circumstances it is possible to get 'junk' files stuck in system ( or cache,data ), and in such away that recovery can not delete them, more serious corruption can render the partitions unmountable.
It is actually quite straight forward to fix this, but it does require fastboot
Code:
fastboot erase system -w
Clockwork Recovery 2.0.2.0 and later has erase_image binary, if you can adb shell in then
Code:
for i in system cache userdata;do erase_image $i;done
and reboot
I would advise you seek out how to 'fastboot', which tbh is a good thing to have regardless of using this 'hack' as it can get you out of so much trouble
*NB* don't use a patched recovery to flash SPL or RADIO ( you should avoid using recovery to flash these anyway, feel free to ask for current advice on spl / radio flashing )
Prevention is better than cure
I have only managed to corrupt partitions when switching partition layouts while having files on cache or data, for example going from System 67.5 Cache 67.5 to System 90 cache 5 with
cache approx 80% 'used'...
I have not been able to repeat this if I wipe Cache before rebooting,
therefore I advise that you wipe both cache and data * after patching recovery ( and rebooting )
* along with system if you are using clockwork
OK, now lets patch recovery and a ROM
Install Instuctions
It really is quite simple
download FR-recovery-v1.5.6-CustomMTD_S.zip and FR-boot-v1.5.6-CustomMTD_S.zip
create mtdpartmap.txt and put on /sdcard/ see configuration *
reboot to recovery
nandbackup
wipe cache + data
flash FR-recovery-v1.5.6-CustomMTD_S.zip
reboot to recovery ( reboot and hold Home )
Either : -
Nandrestore
Flash ROM + extras
flash FR-boot-v1.5.6-CustomMTD_S.zip
reboot
* configuration
The script in the recovery patcher checks for /sdcard/mtdpartmap.txt and reads that to override the default sizes.
e.g. for system 90mb and cache 2mb
NB make sure you mount sdcard first, else you won't write to sdcard/mtdpartmap.txt !
Code:
echo "mtd 90 2" > /sdcard/mtdpartmap.txt
data would be 117.8mb ( 116.7 useable )
e.g. for system 55mb and cache 2mb ( Purhaps a nice 'sugar free' Donut )
Code:
echo "mtd 55 2" > /sdcard/mtdpartmap.txt
data would be 152.8mb ( 151.7 useable )
NB, above data sizes are for G1s, MT3Gs should add ~78mb
All In One Patch runner ( New to v1.5.3 )
new option to run the All In One Patch script ( versions 1.3.6 and higher )
the format is
Code:
aio <option1> <option2> <option3>...
e.g.
Code:
aio swap remount shabang lwp
By default it will install the sd-ext mount ( option sdext )
so a line just reading aio will be fine
Note: the patch must be on the root of the sdcard, and its file name must start with "fr-patch" and end with ".txt"
if you have several versions the newest ( as per files datetime stamp ) will be used
Faking your SPL
If your using an SPL that is not officially supported by your ROM and that ROM checks your SPL you can 'patch' to fake it.
Code:
echo "spl 1.33.2005" >> /sdcard/mtdpartmap.txt
note that we are using ">>" here, this is to append to the file ( ">" would overwrite it )
you can by all means use any text editor you like, the script will automatically convert to unix format
NOTE : you are dodging the checks the ROM dev put in place, do not complain to them if this doesn't workout for you
in post 2 I have some 'CM6' Kernels I compiled for (1)0.95.xxxx SPLs
but I will only likely do these for RCs and Finals ( and there maybe a delay ).
In that post I point you towards the 'SafeSPL' ( 1.33.2003 ) this SPL is compatible with the current CM6 kernels ( so no need to wait for me or someone else to compile with bluetooth as modules ), but 1.33.2003 is not 'officially' supported ( its stock at 67.5mb system ) so you need to Fake your SPL ( say 1.33.2005 ) and resize to 90mb system ( or whatever you feel is optimum )
.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:.
Downloads
.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:.
http://tinyurl.com/customMTD
aab0fadf658ed275954aea8d0aed9c8f FR-AutoMTD_partitionPatcher_v1.5.6.tar.bz2
8857194cdbe34a52d173def4441ad2ae FR-AutoMTD_partitionPatcher_v1.5.6.zip
1f84a5ec50684a7830a93a8d455bc159 FR-boot-rpp-v1.5.6-CustomMTD_S.zip
bca0360f91aed0acf6e2dc82dfe01b56 FR-boot-v1.5.6-CustomMTD_S.zip
94b4238c2668cbe7cd52fb8ad5a2ee12 FR-recovery-v1.5.6-CustomMTD_S.zip
5404f1a41dbc60105d59c7fa0c335a70 FR-remove-v1.5.6-CustomMTD_S.zip
NB New Config option !!! to automatically run fr-patch136+
e.g.
Code:
mtd 90 2
spl 1.33.2005
aio swap remount shabang lwp a2sd
.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:.
ROM Zip Patcher for Devs
To make life even simpler for end users it is possible to integrate the 'patch' within a ROM
AutoMTD_partitionPatcher_v1.5.6.zip
currently Linux only,
within the zip is a tarball, untar that.
get that directory into your PATH, ( or just cd into it )
and then execute
Code:
PatchUpdateScript.sh <zip file to patch>
it will then
create a temp directory ( in your current directory )
copy your zip to it
extract required files
patch update(r)-script
zip and sign.
It simply saves the user from flashing the boot patch after flashing your ROM
The Future....
lbcoder has already suggested ways in which we can implement this 'on the fly'
so for instance it would be possible for a ROM , to instruct recovery what MTD partition layout is required, reload mtd kernel modules, and then flash ROM + boot.img
for those with huge partitions
Hey, you could go all silly and dual boot between ROMs ..
Anyway, enjoy and feel free to modify/improve on these
Changelog
v1-5-6 : 2010-10-28
Calculate userdata size, greatly improves compatibility
Added a version to patch a boot.img ( boot-rpp ) with run-parts
didn't want to , but some are using roms which don't have run-parts, so the 06BindCache script wasn't running
Added a remove version ( remove )
flashing this will return the recovery to SPL's layout
I may well integrate that better, so you don't need a separate zip
AutoMTD_partitionPatcher can convert a recovery.img to a AutoMTD flashable zip
PatchUpdateScript.sh <full path to>/recovery.img
boot patcher is much cleaner, it just uses the cmdline of the running recovery
removed the default 90 2 sizing, you *must* set your own size in mtdpartmap.txt
v1-5-4/5
added stuff
removed stuff
moved stuff
see v1-5-6
v1-5-3 : 2010-08-13
This should be last version we need
greater compatibility with none dreams/sapphires
option to launch All in One Patcher
v1-5-2 : 2010-08-0
Bug fixes
recovery was getting written to boot ( flash_image <partition> is now a variable )
typo in env variable was causing cache and data calculations to fail
AutoMTD now prints version number ( when flashing patched Zip )
tided up system "0x" 'fudge' ( to be compatible with trout/sapphire fall back )
removes temp files from memory when done
v1-5-1 : 2010-08-06
Bug fixes, had an extra '0x' on the system start + functions had wrong env var for the location of dmesg derived partition map
v1-5 : 2010-08-06
Version numbers brought into sync
Zipe Filename - 'reordered' ( easier to see version numbers in CWR )
AutoMTD Patcher - changes as per boot Patcher + zip recursion fix ( my bad habit, thanks go to mblaster for pointing this out )
Boot Patcher - cleaned up cache bind mount
Now supports leagcy /system/sd mount point
[*]supports ROM Manager ( real cache partition mounted on /dev/cache, recovery dir symlinked from 'fake' to 'real' cache )
Recovery Patcher - can 'fake' your SPL ( see configuration )
Recovery Patcher - creates more noise ( advise wipe and reboot )
Single Patcher script ( so I don't have make the same changes to three different files that essentially do the same job )
No longer 'Hardcoded' to 32[a/b] Partition Layout ( figures out SPL layout via dmesg ) **
uses original boot/recovery img's base configuration ( i.e. EBi0 and EBi1 compatible )
=< v1.4
Recovery Patcher v1.3, added SPL faker
Boot Patcher v1.2, fixed oversite where boot.img was not 'dumped'
Recovery Patcher v1.1 initial
Boot Patcher v1.1 ( was a fail, it didn't patch boot.img on CM roms as the tmp boot.img was deleted, my fault for just using the AutoMTD Patcher's script ( which runs before the tmp boot.img is deleted )
Boot Patcher v1 initial
Todo
- 2010-08-13 redundent ( launching AIO script ) - I might add some stuff to cm5/6's backup routine via the Auto patcher, things like the "All in One" installed scripts: 05mountsd and remount
windows compatible AutoMTD script ( meh, I hate batch scripts )
- 2010-08-13 DONE - thinking of adding a config option to launch the "all in one" script, but have to make that recovery compatible first
.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:.
Downloads
.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:.
mediafire downloads
http://tinyurl.com/customMTD
aab0fadf658ed275954aea8d0aed9c8f FR-AutoMTD_partitionPatcher_v1.5.6.tar.bz2
8857194cdbe34a52d173def4441ad2ae FR-AutoMTD_partitionPatcher_v1.5.6.zip
1f84a5ec50684a7830a93a8d455bc159 FR-boot-rpp-v1.5.6-CustomMTD_S.zip
bca0360f91aed0acf6e2dc82dfe01b56 FR-boot-v1.5.6-CustomMTD_S.zip
94b4238c2668cbe7cd52fb8ad5a2ee12 FR-recovery-v1.5.6-CustomMTD_S.zip
5404f1a41dbc60105d59c7fa0c335a70 FR-remove-v1.5.6-CustomMTD_S.zip
The attached files are OLD
Custom MTD FAQ
FAQ
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Q my SPL starts with 0 or 10, and I want to try CM5.0.8 or/and CM6. DO I need to do anything extra?[/b]
A yeap, it seems the newer kernels are just a bit too big for x0.95.x00x SPLs, you can get round it with the below kernels. And to flash CM6 you need to 'fake' your SPL ( see configuration in OP ) or edit the updater-script. faking is easier.
However, I would recommend the 1.33.2003 SPL ( you still need to fake your SPL, but you won't need the 'special' kernels )
guide for flashing 1.33.2003 SPL by Ezterry
#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#
2010-07-11
I have compiled a kernel, which I hope is NoneDanger compatible
the source is simply CyanogenMod's github, I have taken the config from cm6rc1, and simply changed the bluetooth to modules
this approach has worked in the past
It is pre-patched with AutoMTD, so just flash cm6rc1, then flash this
FR-CM6RC1-bootimg4NoneD-AutoMTD.zip(MD5: 386D9A05A3C0FFC08E5B3F844D437AA7)
mirrors
http://rapidshare.com/files/406402016/FR-CM6RC1-bootimg4NoneD-AutoMTD.zip
http://www.mediafire.com/?152jnqwyme3
#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#
2010-07-27
NoneDanger compatible Kernel for RC2
FR-CM6RC2-bootimg4NoneD-AutoMTD.zip (MD5: 7858a8a8d126919318d1718c6e5167ec )
http://www.mediafire.com/file/ttxfcocsti3mma3/FR-CM6RC2-bootimg4NoneD-AutoMTD.zip
I'll have to dig out the src
#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#
2010-08-15
NoneDanger compatible Kernel for RC3
2010-08-17 ( Sorry, old one had a status6 bug )
New one here
87F160F08FCD2233DDD40FBFC50D3711 FR-CM6RC3-bootimg4NoneD-AutoMTD.zip
src = http://github.com/CyanogenMod/cm-kernel/tree/48c57f11abaaf3de6c81f6f5c44cfe2637251184
no modifications its straight cm ( besides the config, which you can get from the compiled kernel or zcat /proc/config.gz )
#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#
*NB* don't use a patched recovery to flash SPL or RADIO ( you should avoid using recovery to flash these anyway, feel free to ask for current advice on spl / radio flashing )
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Q do I need to flash both of the files each time I install a new rom?
A No, you only need to flash the recovery patcher once, unless you want to resize or you install a new recovery.
the boot patcher *must* be flashed after you have installed a new ROM or Kernel update
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Q my cache looks odd in df, I see two and its the same size as data or sd-ext, is something wrong?
A everything is fine, since we shrunk cache its no good for things like the Market, so a script is installed to 'bind mount' cache with /sd-ext/cache or data if sd-ext is not mounted.
it actually turns out that /cache is not actually used in CM6, so I might adapt the script a little in a future release.
EDIT: as of version 1.5 the cache bind mount script mount 'real cache' separately, which should reduce confusion
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Q When I tell ROM Manger to do something in recovery, it just reboots to recovery and does nothing. it used to do the action but not since I installed CustomMTD
A yeah, nearly forgot about that, I was going to fix it last week, basically ROM Manger writes commands to /cache, but its writing it to our bind mount so.. when recovery boots it doesn't see the commands.
In all honesty that one hasn't been pointed out to me yet, but yeah I can fix it..
EDIT: as of version 1.5 the cache bind mount is compatible with ROM Manager
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The Scripts
'source' is now available on github
http://github.com/Firerat/CustomMTD
errm, tbh I'm not all that clued up on it yet
looks very promising
So, will i need to change the values everytime i flash a different rom? or can i just set them to a large size and everything will work?
asb123 said:
looks very promising
So, will i need to change the values everytime i flash a different rom? or can i just set them to a large size and everything will work?
Click to expand...
Click to collapse
most roms have a target of 90mb system ( DangerSPL )
so 90 2 config will basically give you an extra 28mb on data than you would have with stock DangerSPL MTD map
so yeah
90 2 is a good all rounder
Firerat said:
most roms have a target of 90mb system ( DangerSPL )
so 90 2 config will basically give you an extra 28mb on data than you would have with stock DangerSPL MTD map
so yeah
90 2 is a good all rounder
Click to expand...
Click to collapse
is it okay if I make system 70mb?
The rom im using is only using 66 out of 90, i want more space for data instead. I remember you said something about it being a miltiple of 128K.
With this, could Devs stop skimping on stuff like wallpapers and ringtones or additional apps, and surpass the 90MB danger spl mark? It would seem so. Also, I do not make roms so I do not know how it works but if there is compression or lower quality stuff they would now be able to use up as much space as wanted correct?
Ace42 said:
is it okay if I make system 70mb?
The rom im using is only using 66 out of 90, i want more space for data instead.
Click to expand...
Click to collapse
yeap, should be fine
personally I would be tempted to use clockwork, since you can erase system ( part of partition options )
.img files can be found here
http://www.koushikdutta.com/2010/02/clockwork-recovery-image.html
I don't recommend flashing via ROM Manager with CM5 or CM6
fastboot it over, or flash via recovery
I may be a little over cautious recommending a full wipe, but I have never had problems when system, cache and data are clean.
if you are 'growing' system make sure cache and data are clean
if your 'shrinking' make sure system is clean ( so 'hangovers don't mess up /cache or data )
asb123 said:
With this, could Devs stop skimping on stuff like wallpapers and ringtones or additional apps, and surpass the 90MB danger spl mark? It would seem so. Also, I do not make roms so I do not know how it works but if there is compression or lower quality stuff they would now be able to use up as much space as wanted correct?
Click to expand...
Click to collapse
yes, you can 'grow' or 'shrink' at will
just hope it doesn't get used to be lazy and not trim bloat
Hi firerat,
you mentioned once before something about market data on the cahe... or something so downloads would be ok if a certain partition was big enough?....something like that... I am having a prob that might be related since it started when I tried to change from default to system 80 5 for data. now I cant sign in to google and after flashing gaaps there is no market? everything else in the gaaps zip is there...? It could be google i know but i remembered you saying that somewhere.
TheNewGuy said:
Hi firerat,
you mentioned once before something about market data on the cahe... or something so downloads would be ok if a certain partition was big enough?....something like that... I am having a prob that might be related since it started when I tried to change from default to system 80 5 for data. now I cant sign in to google and after flashing gaaps there is no market? everything else in the gaaps zip is there...? It could be google i know but i remembered you saying that somewhere.
Click to expand...
Click to collapse
I very much doubt it is related in anyway
/cache is where the market downloads apks to prior to install
it should be bind mounted to /sd-ext/cache or /data/cache if sd-ext is not mounted
your missing Market is related to something else
Firerat said:
I very much doubt it is related in anyway
/cache is where the market downloads apks to prior to install
it should be bind mounted to /sd-ext/cache or /data/cache if sd-ext is not mounted
your missing Market is related to something else
Click to expand...
Click to collapse
On my sdcard, why were my market Dls going to /Sdcard/Download folder?
I never seen them go there before, I'm used to seeing them in /cache.
Ace42 said:
On my sdcard, why were my market Dls going to /Sdcard/Download folder?
I never seen them go there before, I'm used to seeing them in /cache.
Click to expand...
Click to collapse
Because he bind mounted it.
Ace42 said:
On my sdcard, why were my market Dls going to /Sdcard/Download folder?
I never seen them go there before, I'm used to seeing them in /cache.
Click to expand...
Click to collapse
JAguirre1231 said:
Because he bind mounted it.
Click to expand...
Click to collapse
sorry for confusion
When I download stuff with dolphin HD it goes to /sdcard/download
maybe its different with stock browser
the cache bind mount is
added a few extra comments to make it easier to follow
/system/etc/init.d/06BindCache
Code:
#!/system/bin/sh
# check we don't already have a bind mount
# ( so if ran manually multiple times we don't end up with strange things happening )
if [ "`awk '/\/cache/' /proc/mounts |sed -n '$='`" -gt "1" ];
then
echo "cache already bind mounted"
echo `awk '/\/cache/' /proc/mounts`
exit
fi
# check if /sd-ext mounted, if yes then bind to /sd-ext/cache, if not /data/cache
if [ "`grep -q sd-ext /proc/mounts;echo $?`" = "0" ];
then
CacheDir=/sd-ext/cache
else
CacheDir=/data/cache
fi
# check we have something to bind mount, and create if not
if [ ! -d $CacheDir ];
then
install -m 771 -o 1000 -g 2001 -d $CacheDir
fi
mount -o bind $CacheDir /cache
# check dalvik-cache exists ( this is really for magics )
# so they don't end up in bootloop because dex files can not be created
if [ ! -d $CacheDir/dalvik-cache ];
then
install -m 771 -o 1000 -g 1000 -d $CacheDir/dalvik-cache
fi
actually, errm yeah it is d/l to /sdcard/downloads
not my doing
I guess cache really is pointless on froyo
hey firerat great job bro! again ive been really busy and i still didnt get to try this or the earlier betas you made...hell i havent even tried a froyo rom yet. ima try this right now and let you know how it goes!
speedysilwady said:
hey firerat great job bro! again ive been really busy and i still didnt get to try this or the earlier betas you made...hell i havent even tried a froyo rom yet. ima try this right now and let you know how it goes!
Click to expand...
Click to collapse
Froyo has been nice so far
but you may run into issues
for one the updater-script is actively 'kicking' NoneDanger
you can just remove the getprop checks
I have had problems booting cm5.0.8's kernel, I did get round it by compiling a new one from cm github,
I
'm not sure is cm6's kernel has the same issue
it does seem SPL related, I flashed Danger and it was fine, I plan to go back to NoneDanger and confirm it still doesn't work.
but figured that while I was on Danger I might as well put this (Custom MTD) through its paces with a DangerSPL
Firerat said:
Froyo has been nice so far
but you may run into issues
for one the updater-script is actively 'kicking' NoneDanger
you can just remove the getprop checks
I have had problems booting cm5.0.8's kernel, I did get round it by compiling a new one from cm github,
I
'm not sure is cm6's kernel has the same issue
it does seem SPL related, I flashed Danger and it was fine, I plan to go back to NoneDanger and confirm it still doesn't work.
but figured that while I was on Danger I might as well put this (Custom MTD) through its paces with a DangerSPL
Click to expand...
Click to collapse
lol yeah i was just gonna say the get prop error occured lemme remove those asserts resign and see what happens
hmm oddly everything flashed fine on the latest nightly build but when it gets past the g1 screen it keeps rebooting to recovery? ima rewipe and try again and see if i can get a logcat if it happens again
edit: no dice when i run logcat =/
-exec '/system/bin/sh/' failed: permission denied (13) -"
double edit: i get the same error for any rom i try to flash when i look at the logcat. the only difference is cm's latest nightly build rebooted on the g1, super e freezes at the g1 screen...ima try to modify the .txt to go back to the stock layout so i can nandroid my cachehacked cm5.08 back if not...idk what to do..
speedysilwady said:
hmm oddly everything flashed fine on the latest nightly build but when it gets past the g1 screen it keeps rebooting to recovery? ima rewipe and try again and see if i can get a logcat if it happens again
edit: no dice when i run logcat =/
-exec '/system/bin/sh/' failed: permission denied (13) -"
Click to expand...
Click to collapse
Odd, but at leasat the kernel is booting, I wasn't getting anywhere with cm5.0.8
It could be a general error
Which build are you using
I'm on a nightly, but I know Defcon works
If its still not working, try the older v1 version of boot patcher in lbcoders thread
I did change boot v1.1 to the script I use in the automtd one
I'm on the nightly 0704 (944 I think ) btw
Firerat said:
Odd, but at leasat the kernel is booting, I wasn't getting anywhere with cm5.0.8
It could be a general error
Which build are you using
I'm on a nightly, but I know Defcon works
If its still not working, try the older v1 version of boot patcher in lbcoders thread
I did change boot v1.1 to the script I use in the automtd one
I'm on the nightly 0704 (944 I think ) btw
Click to expand...
Click to collapse
noo this wasnt cm5.08 this was the latest nightly, same one youre 0704 on.
it got to the g1 screen and right when its abt to hit the boot animation it reboots.
i tried super e but it froze on the g1 screen
trying to get back to 67 67 for cache and system so i can nandroid but its weird that the logcat wont show no matter what rom i use.
SouthPaw Version 2.1 - Final Deodex
***Two Versions - Odex(to come soon) and Deodex***
Click to expand...
Click to collapse
Odex for pure speed, and Deodex for themes
Latest A2SD built right in. NO config needed -- Bloat removed for speed
Click to expand...
Click to collapse
No Longer a specific Cellular South based rom! Any carrier using a Hero can run this Rom!
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Removed Apps:- AmazonMp3 - DiscoverCenter - Flickr - GoogleSkyMap - HTCFootprintsLayar - LearnMore - Movies - Stocks - Teeter - Textcs - Twitter - Various HTC Widgets (will have download links tonight)
Themes:
To use these you will need Metamorph.
Metamorph - Link to Market (go from phone browser) Metamorph
QRCode for Metamorph(use barcode scanner)
The Blue Echo
Made by Pappa Smurf, ported to our rom from Leadfoot
http://www.mediafire.com/?buacudiq2if9kti
Must install metamorph from market before using these themes.
NOT COMPATIBLE WITH ODEX VERSION!
"to apply. simply download then put on SD card in folder called AndroidThemes. then go to metamorph click "start checks" then "unzip new theme" click on "TheBlueEcho" zip file. then just do it like the other theme. it can go right over it no need to wipe or recover anything. thats the great thing bout metamorph just as always make sure you nand backup just in case." -leadfoot9281
Click to expand...
Click to collapse
Red Dawn Theme:
By Pappa Smurf, converted to our rom by Leadfoot:
http://www.mediafire.com/?tuc8xlwb61e98wm
after you metamorph this call sombody without a picture, if the little android guy is blue and you want him red metamorph this.
http://www.mediafire.com/?71tw4etfslasd96
for the market- NOT A METAMORPH FILE MUST BE PUSHED WITH ADB
**EDIT ... took market down til I can fix.
i would recommend doin a nand backup before pushing this. i pushed it 4 times to my phone. 3 of those times it worked fine. the one time it didnt work i have no idea why as i didnt do anything different.
to push this go to adb shell and type :
mount -o rm,remount -t yaffs2 /dev/block/mtdblock3 /system
now back put of shell and put the Vending.apk into the push folder. now you will type :
cd push
adb push HtcDialer.apk /system/app
....................now your done.
A majority of this theme is from papasmurfs RedDawn with a few tweaks of my own and some random icons i have ran across place to place. i cant take the credit for this other than i test each thing and make sure it functions and get it to work for a stock rom (like this one) and simply put it together.
BTW: no FC's for contacts or contact widgets on this one. thats what took so long lol.... only issue i know of is setting up speed dial. other than that, all of it works. been using it a few days now. If you run into anything let me know and i will see what i can come up with. - Leadfoot
Click to expand...
Click to collapse
Flipping Animations (Metamorph)
***If it messes up, you WILL bootloop. This MAY work with odex but not sure yet. BEST DO A NANDROID PRIOR TO USING THIS METAMORPH FILE!!!***
Download:
http://www.mediafire.com/?mn883l6v0i6nhaa
Click to expand...
Click to collapse
Alternative Weather Clock (Metamorph)
Download: http://www.mediafire.com/?3hajyxj1g9dpahe
***NOT A FLASHABLE ZIP!/NOT COMPATIBLE WITH ODEX ROM!!!***
Extract zip file to the AndroidThemes folder on your sdcard after installing metamorph, and use metamorph to apply it. It says to restart after applying, but no need to do so.
Click to expand...
Click to collapse
Black Haptic Dialer (Flashable Zip NOT a metamorph!)
http://www.mediafire.com/?2d1jewavnhytd9f
Click to expand...
Click to collapse
Where to download:
SouthPawV-2.1-Final
Deodex: http://www.mediafire.com/?n55a39vc4loetcl
MD5: 4892e91d8af0db765d74741be2db02cd
Bloat download: http://www.mediafire.com/?uo9oja1q7x6zb59
**Bloat download NOT flashable. Push via adb**
(SP-2.0 Final Links)
***Odex is FASTER than de-odex, but is NOT THEMABLE!***
http://www.mediafire.com/?jcl2i8mzlfw1glu
MD5 Sum:d2569d8b937266b2873251bfa556c6e2 SouthPawV2-Final-Odex.zip
***DeOdex is not quite as fast but still mighty fast, lightweight and best of all.. THEMEABLE!!!***
http://www.mediafire.com/?004a3qv0xw0jjat
MD5 Sum:6abe77ca31494cb314c8076117925e81 SouthPawV2-Deodex.zip
Click to expand...
Click to collapse
For Colin_ph users!
The bf/adnan kernels can't be used with the regular version of collin_ph battery mod. You have to use the edited version below and change your governer to the settings shown below.
http://github.com/Decad3nce/battery-...5d1156014134c2
"Recommended Settings for Tweak:
For BFS Kernel:
CPU Governor: Ondemand
I/O Scheduler: deadline/cfq
For CFS Kernel:
CPU Governor: Interactive
I/O Scheduler: deadline/noop"
To change the governor, look into the 2nd post for instructions.
Click to expand...
Click to collapse
For the future: For later updates you can find it all here in the SouthPaw folder:
http://www.mediafire.com/?ye6pbkdgps4b5
This is where the flashable add ons will be soon as well.
***Updaters***
Do not update over previous rom! Backup/Nandroid, and then wipe and flash!
***Thanks N Applause***
leadfoot - thank you for porting that theme!
dsixda - Without your kitchen this wouldn't be possible. F*ing clean software man.
Darchstar - For the Kernel. Awesome man awesome!
Collin_ph - Any extra battery life is great!
JsChiSurf - Love your dialer. Sry I didn't ask before adding it to this rom but didn't figure it would be a big deal.
MrDanger - Your rom is lookin' good. And thanks for helping my users out here and there too.
KyleIsTheBeast - For my first rom ever flashed. Bittersweet was good while it lasted and hope to see you dev'ing in the future.[/SIZE]
Reserved for the Red Corner!
***Issues found!***
none yet.
***How to check the MD5 Hash***
Windows (and mac) users:
1. download Hashtag, a free md5 file hash check utility from here: http://beeblebrox.org/hashtab/
2. After downloading and installing, just right click on any file. On Windows, select properties and you will see a new "File Hashes" tab. On Mac select "File Hashes" (on 10.5 the "File Hashes" menu item will be found under the "More" submenu). This is will start HashTab providing more or less the same view that you see on Windows. This File Hashes window displays all the hashes for the file.
3. Check the hash to make sure it's the same big jumble of numbers and letters as the hash above. If it is not the same, the download is bad and you should redownload the file.
Linux users:
1. go into your linux terminal or shell (not the adb shell)
2. navigate to the folder that contains the rom (mine is in downloads, so you would type 'cd Downloads')
3. for my rom, type 'md5sum SouthPawV1.5Final.zip
4. the output should look as shown:
Code:
OUTPUT_ZIP$ md5sum SouthPawV1.5Final.zip
F0D9E1F279FA7B0FA8636616499CD0C8 SouthPawV2.0-Beta.zip
[email protected]:~/Desktop/kitchen/OUTPUT_ZIP$
Installation:
***for newbies, see the second post under "How to root/maximizing my rom experience"***
1. Nandroid
2. Wipe
3. Flash
4. After install see configuring a2sd for more memory on the phone and JIT/Swap configuration in 2nd post! (and possibly a faster phone if you have a class 4 or higher memory card)
Bloated apps can be re-downloaded here: http://www.mediafire.com/?7ektxbiq0h65ftr
***Radio***
Also removed the Radio.img file. If you want the file you can download it here:http://www.mediafire.com/file/u2z11ar9ga6qn3a/CSouth_Radio_Signed.zip
MD5 Hash: 9157b63be585abef5812f71691cc4899
*You do not need to be flashing this file if it's already updated because that is the one file that CAN brick your phone if it's corrupted. ALSO if you ARE downloading this file, CHECK THE MD5 hash! Instructions above. It could mean the difference between a happy updated phone and a BRICKED phone.*
***How to root and Maximizing your rom experiance***
I hold no responsibility for any actions resulting from these links and/or this post.
How to root your CS Hero. Read first post, it describes everything
http://forum.xda-developers.com/showthread.php?t=581869
***How to flash any rom***
After rooting your phone to install any rom (not just mine)
1. backup everything if you have not already done so, you will lose EVERYTHING on the phone itself, (except for everything on the memory card)
1a. download my rom or another rom (as long as it's for your phone and radio)
1b. place the rom in the root directory (or the main directory rather) of your sdcard.
2. Turn the phone off
3. While holding the home button, press the power button until you see the recovery mode menu. (I am using clockwork mod 2.5.0.1 so depending on your recovery YMMV. You should use the instructions for your specific recovery system. They are using Darch's version of AmonRA's recovery, This is covered in the first post on that link as well.)
If you are using Clockwork Mod, you can use these instructions:
4. go to wipe data/factory reset and go to yes to start the wipe.
5. scroll down to wipe cache partition, and confirm
6. scroll down to advanced and wipe dalvik cache.
7. After that, scroll down to "install zip from sdcard"
8. select choose zip from sdcard
9. select the rom file from the memory card (mine will be SouthPAW!1.5-Final) and confirm to flash it.
10. Once the flash is done, reboot the phone. It's going to take between 5 and 10 minutes to boot the first time so be patient, and don't mess with it. After you get in you are golden, and nothing else is to be done. You have made it..
***how to maximize your battery performance***
This rom comes with an overclocked kernel that automatically sets itself to maximize battery life. But there are things you can set to make the kernel do what you want
***Kernel parameters***
You don't have to use any overclocking software to set the speed of the processor with this kernel Here is the parameters:
Syntax: echo "(speed in hz)" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
Example:
echo "768000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
Click to expand...
Click to collapse
Sets the cpu to max out at 768mhz
echo "710000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
Click to expand...
Click to collapse
Sets the cpu to max out at 710mhz
Also...
If your gps quit working for some reason do this:
mount -t debugfs none /sys/kernel/debug
echo "NORMALIZED_SLEEPER" > /sys/kernel/debug/sched_features
echo "NEW_FAIR_SLEEPERS" > /sys/kernel/debug/sched_features
Click to expand...
Click to collapse
To change the cpu governors for this kernel (the built in ones) here is how:
Type this to find the available governors:
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors
Click to expand...
Click to collapse
The ones available are:
conservative
ondemand
userspace
powersave
performance
interactive
And then to change the governor, you type this:
echo "nameofgovernor" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
Click to expand...
Click to collapse
I haven't found full explanation on ALL the governors, but I guess it's a no brainer, however here is the info I pulled off of the kernel thread:
(For Interactive governor)
This governor is designed for latency sensitive workloads, UI interaction for
example.
Advantages:
+ significantly more responsive to ramp cpu up when required (UI interaction)
+ more consistent ramping, existing governors do their cpu load sampling in a
workqueue context, the 'interactive' governor does this in a timer context, which
gives more consistent cpu load sampling.
+ higher priority for cpu frequency increase, rt_workqueue is used for scaling
up, giving the remaining tasks the cpu performance benefit, unlike existing
governors which schedule rampup work to occur after your performance starved
tasks have completed.
Existing governors sample cpu load at a particular rate, typically
every X ms. Which can lead to under powering UI threads when the user has
interacted with an idle system until the next sample period happns.
The 'interactive' governor has a different approach. Instead of sampling the cpu
at a specified rate, the governor will scale the cpu frequency up when coming
out of idle. When the cpu comes out of idle, a timer is configured to fire
within 1-2 ticks. If the cpu is 100% busy from exiting idle to when the timer
fires then we assume the cpu is underpowered and ramp to MAX speed.
If the cpu was not 100% busy, then the governor evaluates the cpu load over the
last 'min_sample_rate' (default 50000 uS) to determine the cpu speed to ramp down
to.
There is only one tuneable for this governor:
/sys/devices/system/cpu/cpufreq/interactive/min_sample_rate:
The minimum ammount of time to spend at the current frequency before
ramping down. This is to ensure that the governor has seen enough
historic cpu load data to determine the appropriate workload.
Default is 5000 uS.
Click to expand...
Click to collapse
One last thing is that this kernel keeps logs. Even though they are hard to read if you want to see them, type this:
adb remount
adb pull /proc/last_kmsg last_kmesg.txt
Click to expand...
Click to collapse
***how to partition for apps2sd for Amon Ra's Recovery and Cyanogen's Clockwork Mod Recovery***
Instruction Source: http://www.villainrom.co.uk/wiki/index.php?title=Apps2SD#Normal_Installation
How to Setup SD card partitions from AmonRa's Recovery:
1. backup your stuff on your memory card. It is very possible that this will erase everything on your memory card.
2. Shut down the phone
3. Press and hold the home button while pressing the power button. Keep holding the home button until you get to the recovery menu.
4. Select Partition sdcard
5. Select Partition SD
6. Set the following partition sizes using the trackball or volume buttons:
-ext: 512MB - recommended. You will feel like you can install everything from the market.
-swap: none -not a prerequisite but recommended. use at least 30mb.
-fat: remaining
7. Reboot the phone. It may take a little while for boot to finish on this boot only.
How to Setup SD card partitions from Clockworkmod Recovery:
***Do not partition with Clockwork mod. There are some issues that I have read that will mess up your install***
There are alternative methods for this, but it's just easier to use Amon_Ra's image for this.
***How to setup a2sd/Swap/JIT***
A2SD is already enabled by default on this rom. However Swap and dalvik to sd is not!
To get swap working (if you made a swap partition on your sd card)
1. get to adb
2. adb remount
3. adb shell
4. a2sd reswap
To move Dalvik cache to sd -
5. a2sd cachesd
VOILA! 149MB free on the phone! *w00t*
Also there is more config you could do here. You can enable JIT *dunno if it works, so add at your own risk*
***More info for a2sd configuration***
Code:
Standard Apps2SD Commands:
--------------------------------------------------
reinstall
Moves free and paid apps to the ext2/ext3/ext4 partition on your secure digital card. Removes the No A2SD flag file.
This is used if you have already executed an a2sd remove command. Otherwise, this part is automatically performed when Apps2SD is started.
File removed: /data/.noa2sd
remove
Moves free and paid apps to the internal phone storage. Creates the No A2SD flag file.
File created: /data/.noa2sd
Swap Partition Commands:
--------------------------------------------------
reswap
Removes the No Swap flag. Allows A2SD to activate the swap partition.
This is used if you have already executed an a2sd noswap command. Otherwise, this part is automatically performed when Apps2SD is started. Note: This command has no effect on roms where the swap space is not built into the kernel.
File removed: /data/.noswap
noswap
Creates the No Swap flag. Prevents A2SD from activating the swap partition. Note: This command has no effect on roms where the swap space is not built into the kernel.
File created: /data/.noswap
swappyxx
Sets the swappiness setting for the swap file. xx sets the swappiness percentage used. (i.e. to set swappiness to 30%, type a2sd swappy30.
Dalvik Cache Commands:
--------------------------------------------------
cachesd
Moves Dalvik cache files to the ext2/ext3/ext4 partition on your secure digital card. Creates Dalvik Cache to SD flag.
Caution: If your phone fails to mount the ext2/ext3/ext4 partition and your dalvik-cache is pointed to the SD card, you will likely end up in a boot loop. Execute a2sd nocache from adb shell to rectify the issue.
File created: /data/.dalvikcacahe
File removed: /data/.dcpartition
cachesdreset
Same as cachesd above, but erases the contents of the dalvik-cache after move. This performs both the a2sd cachesd and a2sd resetcache all in one command.
File removed: /data/.dcpartition
cachepart
Moves Dalvik cache files to the /cache partition in your phone. Creates Dalvik Cache to Cache Partition flag.
Caution: Some phones do not have enough space to put the dalvik-cache on the cache partition. Also, some roms that have SenseUI installed may not work well with the dalvik-cache on the cache partition (although this issue appears to be fixed starting with Darktremor 2.7.5.1). If you experience issues such as force closes, try moving the dalvik-cache to the SD card (a2sd cachesd) or internal storage (a2sd nocache) instead.
File created: /data/.dcpartition
File removed: /data/.dalvikcache
cachepartreset
Same as cachepart above, but erases the contents of the dalvik-cache after move. This performs both the a2sd cachepart and a2sd resetcache all in one command.
File removed: /data/.dalvikcache
nocache
Moves Dalvik cache files to the internal phone storage. Removes all Dalvik Cache flags.
File removed: /data/.dcpartition, /data/.dalvikcache
nocachereset
Same as nocache above, but erases the contents of the dalvik-cache after move. This performs both the a2sd nocache and a2sd resetcache all in one command.
File removed: /data/.dcpartition. /data/.dalvikcache
resetcache
Clears the dalvik cache and restarts phone.
Apps2SD Diagnostic Commands:
--------------------------------------------------
check
Performs a symlink and flag file check on your setup. Outputs a report that shows you if
there are issues with your Apps2SD setup.
repair
Performs a repair of all symlinks based on flag file activation.
diskspace
Shows disk space statistics for the ext partition.
sysinfo
Displays information about your phone, partitions, swap, and more.
Also writes a dump file that has an entire profile of your phone. This is for troubleshooting only.
File Created: /data/dtsysdump.txt
swapspace
Shows swap space statistics for all swap space active on the phone. Note: This command has no effect on roms where the swap space is not built into the kernel.
ZipAlign Commands:
--------------------------------------------------
align
Performs a one-time zipalign on all APK files in /data/app and /data/app-private.
zipalign
Allows ZipAlign to execute during the boot process. Creates the ZipAlign flag file.
File Created: /data/.zipalign
nozipalign
Prevents ZipAlign from executing during the boot process. Removes the ZipAlign flag file.
File Removed: /data/.zipalign
Dalvik Setting Commands:
--------------------------------------------------
jit
Installs DalvikVM JIT.
WARNING: Do not run this command if your phone has NAND protection active.
nojit
Removes DalvikVM JIT.
WARNING: Do not run this command if your phone has NAND protection active.
defaultheap
Resets the Dalvik heap size to the default heap size.
File Removed: /data/.smallheap, /data/.largeheap, /data/.jumboheap
heapsizexx
Sets the dalvik heap size to xx. For example, to set the dalvik cache to 24mb, type a2sd heapsize24. To reset back to default, type a2sd heapsize0 (that's a zero, not the letter "o")
Low Memory Killer Commands:
----------------------------------------------------
lowmem-moderate
Sets the internal memory killer to the following settings:
Code:
Foreground Apps: 1536 pages / 6 MB
Visible Apps: 3072 pages / 12 MB
Secondary Server: 4096 pages / 16 MB
Hidden Apps: 7680 pages / 30 MB
Content Provider: 8960 pages / 35 MB
Empty App: 10240 pages / 40 MB
Create File: /data/.lmmoderate
Remove File: /data/.lmoptimum, /data/.lmstrict, /data/.lmaggressive, /data/.lmultimate, /data/.lmextreme
lowmem-optimum
Sets the internal memory killer to the following settings:
Code:
Foreground Apps: 1536 pages / 6 MB
Visible Apps: 2048 pages / 8 MB
Secondary Server: 4096 pages / 16 MB
Hidden Apps: 10240 pages / 40 MB
Content Provider: 12800 pages / 50 MB
Empty App: 15360 pages / 60 MB
Create File: /data/.lmoptimum
Remove File: /data/.lmmoderate, /data/.lmstrict, /data/.lmaggressive, /data/.lmultimate, /data/.lmextreme
lowmem-strict
Sets the internal memory killer to the following settings:
Code:
Foreground Apps: 1536 pages / 6 MB
Visible Apps: 2048 pages / 8 MB
Secondary Server: 4096 pages / 16 MB
Hidden Apps: 15360 pages / 60 MB
Content Provider: 17920 pages / 70 MB
Empty App: 20480 pages / 80 MB
Create File: /data/.lmstrict
Remove File: /data/.lmmoderate, /data/.lmoptimum, /data/.lmaggressive, /data/.lmultimate, /data/.lmextreme
lowmem-aggressive
Sets the internal memory killer to the following settings:
Code:
Foreground Apps: 1536 pages / 6 MB
Visible Apps: 3072 pages / 12 MB
Secondary Server: 4096 pages / 16 MB
Hidden Apps: 21000 pages / 82 MB
Content Provider: 23000 pages / 90 MB
Empty App: 25000 pages / 98 MB
Create File: /data/.lmaggressive
Remove File: /data/.lmmoderate, /data/.lmoptimum, /data/.lmstrict, /data/.lmextreme, /data/.lmultimate
lowmem-extreme
Sets the internal memory killer to the following settings:
Code:
Foreground Apps: 1536 pages / 6 MB
Visible Apps: 3072 pages / 12 MB
Secondary Server: 4096 pages / 16 MB
Hidden Apps: 38400 pages / 150 MB
Content Provider: 40960 pages / 160 MB
Empty App: 43520 pages / 170 MB
Create File: /data/.lmextreme
Remove File: /data/.lmmoderate, /data/.lmoptimum, /data/.lmstrict, /data/.lmaggressive, /data/.lmultimate
lowmem-ultimate
Sets the internal memory killer to the following settings:
Code:
Foreground Apps: 1536 pages / 6 MB
Visible Apps: 3072 pages / 12 MB
Secondary Server: 4096 pages / 16 MB
Hidden Apps: 51200 pages / 200 MB
Content Provider: 57600 pages / 225 MB
Empty App: 64000 pages / 250 MB
Create File: /data/.lmultimate
Remove File: /data/.lmmoderate, /data/.lmoptimum, /data/.lmstrict, /data/.lmaggressive, /data/.lmextreme
lowmem-default
Sets the internal memory killer back to phone default settings.
Remove File: /data/.lmmoderate, /data/.lmoptimum, /data/.lmstrict, /data/.lmaggressive, /data/.lmextreme, /data/.lmultimate
***How to push an apk file using adb***
*Of course you have to have a rooted phone to do this, if not check the ***how to root*** section first before getting this far.*
This tutorial is going to use the linked deleted files zip from the link in the first post.
1. Download the Android SDK for your appropriate Operating System from here: http://developer.android.com/sdk/index.html
2. Once downloaded, be sure to download the deleted files zip from the link in the first post.
3. Extract the Android SDK file to an easily findable folder
4. Extract the deleted files from the zip file, and copy the apk file you choose to the AndroidSdk\tools folder. For reference I will be using the Dialer.apk file in this tutorial (not included in the zip).
5. connect phone to computer and select "charge only" from the menu.
(*for windows Vista/7/XP*)
*prerequisite* - you must have the adb drivers installed to do this in windows.
6. Click Start, go to > All Programs > Accessories, and from there, right click 'command' (something like that), and click 'open as administrator' (XP users do not have to do this, just go to Start > Run, type cmd, and press enter)
7 .navigate to the android tools folder you put the apk file in (the command to change directories is 'cd' and then a space, and the name of the next folder, so to navigate to the 'android' folder, you would type 'cd android', and then you can use 'dir' to see the next directories till you get to the right folder.
8. type 'adb remount'. This is going to start the adb system, and then remount the phone in root mode.
9. to check to see if your phone is mounted and everything is kosher, type 'adb devices' and it should show something on the bottom that should be your device or serial of the device. If it says ??????????? then it's not working.
10. type 'adb push HtcDialer.apk /system/app'
11. DRINK A BEER! You have pushed an apk to your phone! To check if it is installed, simply click the call button (or press phone on the rosie), go to settings and select speed dial. Then see if you can change/add a number to speed dial #2. This could possibly require a reboot to actually start the new version of the installed software but you should just be able to go ahead and use it
(*for Linux*)
6. Once you extract the android-sdk-linux_x86 folder, go to the terminal, and navigate to the android folder pretty much the same way as windows, except instead of using dir (ubuntu users can use it), use 'ls'
7. type 'sudo ./adb remount' and when asked, type the administrator password for the linux system. This is going to start the adb system, and then remount the phone in root mode.
8. To check to see if your phone is mounted, type 'sudo ./adb devices' this should show your device.
9. To do that actual push, type 'sudo ./adb push HtcDialer.apk /system/app'
10.
DRINK A BEER! You have pushed an apk to your phone! To check if it is installed, simply click the call button (or press phone on the rosie), go to settings and select speed dial. Then see if you can change/add a number to speed dial #2. This could possibly require a reboot to actually start the new version of the installed software but you should just be able to go ahead and use it
***History***
(July 21st)v.0.1 - Dirteh_South-Krome_Knuggz #First Cellular South+Root 2.1 hero rom to hit XDA! Featured Full Stock 2.1 + root, tethering, and apps2SD. --issues-- had to remove various apps because of signing issues.
Download Link:http://www.mediafire.com/?15k8u28gy9f3vka
----------------------------------------------------------------------------------
(July 25)v.0.5 - Dirteh_South-Kleen_Thugz #Removed useless apps, added Live Wallpapers. --issues-- facebook update issue
Download Link:http://www.mediafire.com/?xx0d54pnj99tuyn
----------------------------------------------------------------------------------
(July 27)v.0.6 - Dirteh_South-Fast_Dubz! #Added vUV'd 710mhz overclocked kernel, added Home Switcher, Helix Launcher, and a few small programs.
Download Link:http://www.mediafire.com/?9ithfl65laxpf0y
----------------------------------------------------------------------------------
(August 6)v.1-Beta - South Paw!V1-Beta #Went back to scratch RUU file, Name changed to hide the guilty, completely overhauled, removed useless apps, facebook was fixed, updated A2SD, overclocked/undervolted kernel, google maps, signing issues fixed, added google parts, Old skool 1.5 hero bootscreen, added custom lockcreen *by me* and background, Dconfig, Collin_ph Battery Tweak, Fixed the black dialer w/o haptic feedback.
Download Link:http://www.mediafire.com/?ipf0oonwn9zq2y1
---------------------------------------------------------------------------------
(August 12)v.1.5-Final - SouthPaw!V1.5-Final #Downgraded to previous version of Apps2SD, and previous version of Root Permissions app, modified vUV2 - boot.img file to work properly with a2sd, removed android terminal because there was no way to fix it from fc'ing if you installed from rom flash, removed Dconfig because it was not compatible with this a2sd setup, added xda-developers app, updated facebook to newest version, updated collin_ph battery tweak to newest version.
Download Link:http://www.mediafire.com/?7ro6qczcoqcxtip
---------------------------------------------------------------------------------
(October 1 - October 28th)v.2.0-Betas
beta1 - had slowdown issues due to an unstable kernel added/various things missing
beta2 - still bad slowdown- other various things missing/not working
beta3 - Once more bad slowdown/added internal tweaks for speed but didnt work
beta4 - Fixed slowdown, has internal tweaks for stable brainfuct kernel #6, added misc. backgrounds
---------------------------------------------------------------------------------
(October 27)V.2.0-Final
Removed a bunch of stuff. First ever odex version added alongside the deodex version. No added extras at all besides root, busybox, a2sd, and wireless tethering. No longer a carrier specific rom.
---------------------------------------------------------------------------------
(October 28th)V2.1-Final(ish)
Based on newest update from cellular south. Vanilla with no extras just like 2.0 Final. Removed bloat. No kitchen signed apps AT ALL for smooth working with upgrading apps
Click to expand...
Click to collapse
Hell yeah! Although the neighbors didn't appreciate me running around in the front yard naked! Hmmm.... Maybe I will try the backyard next time.
Good job. I'm glad somebody finally got a CSouth Rom on here.
If you need any assistance let me know.
Ok I go to filedropper site but all I get to download is an empty folder, 66.7kb????. Has the file name but no data, or am I completely missing the right link? Do I need to join to download? Thanks, would really like to try this ROM out.
I got the download, followed all steps, it says that the zip is bad. I deleted the old one, transferred a fresh one to card, same story. I'm downloading the zip again just to make sure it didn't corrupt while downloading.
Anyone else run into this problem?
zip flashed fine for me. Just booting up
Can this be used in other non-sprint heros?
Also, I was wondering if it is possible to have like a stripped / universal version for non-sprint heros and then install CS’s or other carrier’s stuff apart like DarchDroid did with his naked rom with Google ****s apart.
Thanks for sharing it!
I downloaded it from the link with no problem. I did the following:
1.downloaded the zip
2.transferred it to the SD Card
3.HBoot
4.Created Nandroid
5. Wiped everything
6. flashed in zip file
It works pretty good. I can't get my yahoo account to work. I also can't get the new widgets to download to the phone and work. They download and then I don't get them. Hmmmm....
Anybody know how to change pri version? Mine is 1. Something but my non rooted phone is 2.51_013
Even though I am on AT&T with a Magic and Captivate it is good to see some Cell South love around here. I will be using your rom to flash to as many friend's Heroes I know.
Bring on the Incredible, Milestone, and Galaxy S now C South!
Kaisum said:
I got the download, followed all steps, it says that the zip is bad. I deleted the old one, transferred a fresh one to card, same story. I'm downloading the zip again just to make sure it didn't corrupt while downloading.
Anyone else run into this problem?
Click to expand...
Click to collapse
yeah i got the same problem
Redfox85 said:
Anybody know how to change pri version? Mine is 1. Something but my non rooted phone is 2.51_013
Click to expand...
Click to collapse
That is odd. I have no idea tbh, but I'll try to check it out.
From here on out, any questions asked will be answered in the 2nd post on this thread.
***link is fixed!! Any issues please report!***
And yes this rom should work for non-cs users, but always take caution and do like you do with sprint roms, and it should be ok (and for those who didn't get voicemail notifications, this should support it)
hexskrew said:
That is odd. I have no idea tbh, but I'll try to check it out.
From here on out, any questions asked will be answered in the 2nd post on this thread.
***link is fixed!! Any issues please report!***
And yes this rom should work for non-cs users, but always take caution and do like you do with sprint roms, and it should be ok (and for those who didn't get voicemail notifications, this should support it)
Click to expand...
Click to collapse
somethings up with the link again i got an error saying the the files is no longer there
Just want to say thanks, working well here!
Sent from my HERO200 using XDA App
Agpilot! said:
Just want to say thanks, working well here!
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
could you send me the file there appears to be a problem with the link
To Mr. Danger, yes I will need some help soon. I want to branch this rom out to a couple of different versions. 1. With no apps (well junk apps anyways) with helix launcher and no sense, 2. With no junk apps with sense, and 3. Just the full montey (like now but with no issues)
@pound24. I just tried the link. It's working fine (from mediafire, not the old link, I removed that one)
hexskrew said:
To Mr. Danger, yes I will need some help soon. I want to branch this rom out to a couple of different versions. 1. With no apps (well junk apps anyways) with helix launcher and no sense, 2. With no junk apps with sense, and 3. Just the full montey (like now but with no issues)
@pound24. I just tried the link. It's working fine (from mediafire, not the old link, I removed that one)
Click to expand...
Click to collapse
i used a different computer and it worked about to flash in a sec
This may be a dumb question, but you do need to root before applying this ROM, right?
Yes, the phone has to be rooted before loading anything except for the stock updates from the carriers.
Updated 2011-05-09 (New version aim3)
So now that Vodafone Spain finally released a Froyo OTA upgrade for HTC Magic, I've built a cooked ROM from the official OTA upgrade. The ROM tries to ressemble the stock ROM, but including the following extras:
Version aim1:
/system/etc/install-recovery.sh is removed, so it won't overwrite your recovery on every boot, as the stock ROM does
This ROM is rooted. Superuser.apk is installed on system.
Included apns-conf.xml from Cyanogen, so APNs from all operators are available, not just from Vodafone.
Google applications updated to the latest release: Maps, StreetView, Gmail, Market and Youtube
Replaced keyboard with Gingerbread (Android 2.3) newer keyboard.
Removed the Vodafone Live application and shortcut
Version aim2:
Removed Gingerbread keyboard, better install as separate package if you want it (see link)
Updated Google Maps and Market to latest versions.
Include busybox, it's needed for some root applications
Deodexed (takes some time on first boot, saves space on /system)
Re-signed (needed to include STK)
Included STK (Sim-Toolkit) application ("Servicios SIM" in Spanish). Required for some virtual operatos to work in Roaming
Added Sound Recorder icon in Launcher (application was there, but only accessible from MMS when adding a sound)
Added support for scripts in /system/etc/init.d (useful for adding compcache, swap, etc).
Version aim3:
Removed the "assert shappire" line on installation script. Should allow installation on Dream/G1
Revert some re-signed packages to allow Google applications updated via Market
Load ipv6 module to have Google Goggles working
Replace stock kernel with a custom kernel for better performance and memory tweaks
Enable compcache (compressed in-RAM swap memory) on boot by default, to get some extra free MB on magic 32B, which makes the system much more usable (applications and launcher are not killed all the time). Tweaks can be customized using setprop (see later)
Overclock CPU on boot. Can be tweaked using setprop (see later)
Include support for Live Wallpapers
Please note that this ROM is only for HTC Magic 32B (not for 32A or Dream). You'll need to use the System-Only ROM and a different kernel and/or SPL for 32A or for HTC Dream.
This latest update (version aim3) includes:
Android 2.2.1 (FRG83D)
SPL (HBOOT) version 1.33.0013
Radio 2.22.28.25
Kernel 2.6.35.13 from Farmatito (http://forum.xda-developers.com/showthread.php?t=1010932)
About the SPL and Radio: This is a perfect SPL, so it won't allow you to flash unsigned images from fastboot. Please make sure you have a custom recovery image. The new 2.22.28 radio won't work with other older SPLs, but it's worth the additional RAM (15MB). Also, if you want to install another kernel, it must be compatible with this radio version.
Requeriments and pre-installation
You'll need a custom recovery that allows you to flash the update.zip file. Clockworkmod recovery or AmonRA should do the job.
Make sure you have a good battery level, and make a full backup before installing.
Disclaimer: I won't take any responsibility if this bricks or damages your device.
Upgrading
Due to resigning, you can't update from previous version. A full wipe is required, sorry. However, if you backup your data and apps with Titanium Backup, and then restore them, it should work if coming from a previous version of this ROM, or if coming from the stock versions. There are no guarantees if coming from other non-official ROMs
Installation (Two-step)
This is the way the official OTA is done. First, the HBOOT (SPL) is updated to 1.33.0013. Then, the system, kernel and radio are updated. If you want to make the installation this way:
1. SPL Update. First download http://dl.dropbox.com/u/3658919/android/vf_magic_froyo_aim1/vf_magic_frg83d_hboot_0013.zip (Mirror: http://content.wuala.com/contents/airadier/Android/vf_magic_frg83d_hboot_0013.zip?dl=1) and apply update from recovery (copy to the SD Card, then choose Apply .zip from SDCard, and choose the zip file). It will reboot a few times during the upgrade. Finally it should boot the system with the previous version, but the SPL will be upgraded.
2. System+Radio+Kernel update. Download http://dl.dropbox.com/u/3658919/android/vf_magic_froyo_aim3/vf_magic_frg83d_aim3_nohboot_s.zip (Mirror: http://content.wuala.com/contents/airadier/Android/vf_magic_frg83d_aim3_nohboot_s.zip?dl=1) and from recovery wipe Data and Cache. Apply update from recovery, the same way. It should reboot a few times and finally boot the system, updated to Froyo.
Installation (System-only installation)
If you already have SPL 1.33.0013 or 1.33.0013d, and radio 2.22.27.08 or 2.22.28.25, and want to install only the system files, then download http://dl.dropbox.com/u/3658919/and...m3/vf_magic_frg83d_aim3_noradio_nohboot_s.zip (Mirror: http://content.wuala.com/contents/airadier/Android/vf_magic_frg83d_aim3_noradio_nohboot_s.zip?dl=1), and apply update from Recovery.
If you have an 32A, you should be able to use the System-only installation, and when finished, flash an appropiate kernel (the included kernel is for Magic 32B).
Tweak configuration
Latest version includes some performance tweaks which are applied on boot. There's no GUI for changing these settings, but they can be easily changed using a command line (for example adb shell).
First, get a root shell (adb shell, then su). Then you can use the command:
getprop propertyname
Click to expand...
Click to collapse
to get the current value of a setting, and the command:
setprop propertyname newvalue
Click to expand...
Click to collapse
to set a new value. The available setting parameters (Replace propertyname are:
persist.tweaks.ramzenabled: Enabled (if 1) or disabled (if 0) the compressed RAM swap. If not set, it defaults to 1 (enabled).
persist.tweaks.ramzsize: The size of the compressed in RAM swap memory, in KB. If not set, it defaults to 32768 (32MB). Don't try anything higher than the amount of memory in your system. I wouldn't recommend more than 65536 (64M).
persist.tweaks.swappiness: The swappiness parameter. A avlue between 0 and 100, defaults to 10. Tells the system how agressively try to move memory pages to the swap. I keep it to a low value, so pages are not swapped until more free RAM is needed.
persist.tweaks.cpuminfreq: The minimum CPU frequency. If not set, it defaults to 245760 (245Mhz). See the list of available frequencies with command:
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies
Click to expand...
Click to collapse
persist.tweaks.cpumaxfreq: The maximumCPU frequency. If not set, it defaults to 595200 (595Mhz). That's a bit overclocking, but I find it perfectly stable. With higher frequencies (614Mhz) I get random reboots.
persist.tweaks.cpugovernor: The CPU frequency governor. Defaults to interactive, but you can try ondemand too.
Any change will require rebooting the system. If you get stuck with a change (phone can't boot), try using adb shell from recovery, mount /data partition, and remove the offending setting file from /data/property/persist.tweaks.xxxx
Add-ons
Gingerbread keyboard is not included anymore. You can install Gingerbread keyboard along with the Froyo keyboard. See this post.
Alternative kernels: For 32A or HTC/Dream you can try with other non-stock kernels. I would recommend trying Farmatito Kernel or the latest Magic 32B kernel from ezterry, search in Doid Basement. Here is the direct link to the latest ezterry version for Magic 32B/32A
Versions and updates
aim1 - 2010/12/25 (Christmas gift) - Initial release
2010/12/27 - Added "Revert to Froyo keyboard" add-on
2010/12/27 - Added mirrors for files
2011/01/09 - Removed one-step install, seems it's not working
aim2 - 2011/05/01 - New version
aim3 - 2011/05/09 - New version
Hmm,sounds good,how about some screenshots?
But i'm a bit skeptical about the SPL and Radio flash-ing,cuz i almost once bricked my phone
Bad First Try
airadier said:
Installation (Two-step version)
This is the way the official OTA is done. First, the HBOOT (SPL) is updated to 1.33.0013. Then, the system, kernel and radio are updated. If you want to make the installation this way:
Click to expand...
Click to collapse
So after many attempts of trying to get my phone back to "factory" for OTA updates, I gave up very very late in the night and decided I'd just try this new ROM. I know I'm crazy since no one else has written of their attempts to try it - meaning I'm probably the first - and I'm a little worried at what I'm seeing. I followed your instructions for the 2-step version using Clockworkmod recovery and my right now my phone is stuck in the black loading screen that says "ANDROID". Its been on this screen for over half an hour. I'm pretty sure it shouldn't take that long so I thought I'd go ahead and ask for tips now so I can work in it tomorrow. My T-Mobile myTouch 3G original (HTC Magic 32 B) phone was on CM6 (Froyo 2.2) before I revered it to factory 1.6 because of frustrations with Cyanogen's slow mod. T-Mobile's OTA updates weren't working because of recovery image issues so I figured I'd give you version a go. Yes, I realize this is the Vodafone version. Hablo español.
So should I try to reset my phone? Take the battery out? Am I bricked?
I don't think it's bricked, it just seems to be failing to boot the system. A logcat (adb logcat command) would help to diagnose the problem.
You should be able to boot to recovery. Did you wipe data and cache partitions?
Did the previous version boot after flashing first step? You can check the SPL on this step was correctly flashed by entering fastboot (vol down + power) and checking if Hboot version is 1.33.0013
I've tried the 2 step version successfuly in 2 htc magic by now.
Let me know about any progress.
Greets.
Sent from my HTC Magic using XDA App
I can't download any chance. Can you post them in another way?
I can't download from phone neither.
Sent from my HTC Magic using XDA App
I finally download it from computer, but I can't flash it. I've got this error:
Code:
E:Failure at line 6: assert getprop("ro.product.device") == "sapphire" || getprop("ro.build.product") == "saphire"
It works!
It works! Here's how...
It had been 6 hours and it was still stuck on the loading screen, so I pulled the battery.
I wipped my data and cache partitions again using the bootloading, although I'm pretty sure I had already done this. I must have needed to do it again.
The logcat seemed to have tons of errors, more than I could list here. A small copy-paste:
W/PackageManager(30347): Permission com.noshufou.android.su.RESPOND from package com.noshufou.android.su ignored: no gro
up null
I/PackageManager(30347): /system/app/TelephonyProvider.apk changed; collecting certs
D/dalvikvm(30347): GC_FOR_MALLOC freed 5701 objects / 392080 bytes in 124ms
W/PackageManager(30347): Signature mismatch for shared user : SharedUserSetting{435ad3a8 android.uid.phone/1001}
E/PackageManager(30347): Package com.android.providers.telephony has no signatures that match those in shared user andro
id.uid.phone; ignoring!
I/PackageManager(30347): /system/app/UserDictionaryProvider.apk changed; collecting certs
W/PackageManager(30347): Signature mismatch for shared user : SharedUserSetting{435f7a48 android.uid.shared/10010}
E/PackageManager(30347): Package com.android.providers.userdictionary has no signatures that match those in shared user
android.uid.shared; ignoring!
W/PackageManager(30347): Permission com.android.vending.CHECK_LICENSE from package com.android.vending ignored: no group
null
W/PackageManager(30347): Permission com.android.vending.BILLING from package com.android.vending ignored: no group null
I/PackageManager(30347): /system/app/VpnServices.apk changed; collecting certs
W/PackageManager(30347): Signature mismatch for shared user : SharedUserSetting{435ad158 android.uid.system/1000}
E/PackageManager(30347): Package com.android.server.vpn has no signatures that match those in shared user android.uid.sy
stem; ignoring!
Anyway, after restarting twice the phone loaded! Froyo who-hoo! And I love the Gingerbread keyboard addition! This ROM is elegant - almost official OTA with just a touch of fixes. Cyangen's ROMs are over the top for me.
The only thing we've noticed after 30 minutes of testing is that it suggests Gmail be installed in the market, even though its already installed. Obviously this is because we have the newer version of gmail. But does this mean we will no longer get updates for Google applications? This concerns me - I don't want to have to rehack my phone every month - especially since I'm giving this to my brother.
Thanks for the great work and cool simple ROM.
waffleguy4 said:
It works! Here's how...
I wipped my data and cache partitions again using the bootloading, although I'm pretty sure I had already done this. I must have needed to do it again.
The logcat seemed to have tons of errors, more than I could list here. A small copy-paste:
Click to expand...
Click to collapse
Strange. I'm quite sure a Data + Cache wipe is needed except if you're coming from stock 1.6. The errors in the logcat seem to confirm this.
waffleguy4 said:
It works! Here's how...
The only thing we've noticed after 30 minutes of testing is that it suggests Gmail be installed in the market, even though its already installed. Obviously this is because we have the newer version of gmail. But does this mean we will no longer get updates for Google applications? This concerns me - I don't want to have to rehack my phone every month - especially since I'm giving this to my brother.
Click to expand...
Click to collapse
I think you should get the updates anyways. The only difference is, instead of having Maps 4.6 in SYSTEM partition, you have 5.0. The day Maps 5.x is out, it should show an update is available. I think showing it in the market as "Installed" is the normal behavior since the google apps were extracted in Froyo, or Eclair, I can't remember
I might be adding some optional packages (as updates.zip) soon. For example, I'm thinking of adding a patched version of Google Maps to force using Vector and 3D graphics instead of bitmap tiles. Also, maybe an update to revert to the standard Froyo keyboard.
I hope you enjoy it.
jvmonjo said:
I finally download it from computer, but I can't flash it. I've got this error:
Code:
E:Failure at line 6: assert getprop("ro.product.device") == "sapphire" || getprop("ro.build.product") == "saphire"
Click to expand...
Click to collapse
The update script is checking that the installed ROM device or product is "sapphire", and it's failing. Maybe the ROM you're using right now uses another device identifier?
I could remove the check, but it was included in the original updater, and I think it's safer this way. You could try flashing cyanogenmod or the stock vodafone 1.6 first, then updating.
Greets.
maverickcri said:
I can't download any chance. Can you post them in another way?
Click to expand...
Click to collapse
I've added a mirror for all files.
Greets.
I tried two step version but after successful spl update i can't boot recovery anymore:
FAILED (remote: not allow). What should I do next?
kurjak said:
I tried two step version but after successful spl update i can't boot recovery anymore:
FAILED (remote: not allow). What should I do next?
Click to expand...
Click to collapse
How are you booting recovery? Are you using "adb reboot recovery" command? If so, it looks like the perfect SPL won't allow you to run that command.
You must enter recovery by powering the phone off, and then pressing Home + Power On button. Keep pressing them until you're on recovery.
Greets.
i tried fastboot boot recovery. I tried home + power on several times but all i get is exclamation mark screen, with some kind of recovery where i can update from sd:update.zip and this also fails: verification fails
kurjak said:
i tried fastboot boot recovery. I tried home + power on several times but all i get is exclamation mark screen, with some kind of recovery where i can update from sd:update.zip and this also fails: verification fails
Click to expand...
Click to collapse
Ok, don't panic, the fix is easy. The exclamation mark screen is the stock recovery, that allows you to flash only HTC signed update.zip file. As this update is not signed by HTC, it throws the "verification fails" error.
So, how to fix it? You need to flash a custom recovery (ClockworkMod or AmonRA, for example), because the SPL won't allow you to boot the recovery from fastboot.
You need to have your current ROM rooted, if it's not already. If not rooted, check SuperOneClick Root in here: http://forum.xda-developers.com/showthread.php?t=803682
Once rooted, you can flash the recovery using flash_image command from an adb shell, or easier, install RomManager from the market and install recovery from there.
Just make sure the recovery is for Magic 32B or Dream. I think last time I used ROM Manager I choose "HTC Magic", and a recovery for Magic 32A was installed, so the recovery wouldn't boot. I discovered I had to choose "HTC Dream" instead, as the recovery for Dream works for HTC Magic 32B too.
Once installed, using the "Home + PowerOn" you should boot into the new recovery (clockwork or AmonRA), and it should allow you to flash the update. If you get "verification failed" error, check that "signature verification" is toggled off (there's an option in the recovery to enable/disable it).
I hope it hellps. Greets.
Radio Installation didnt work
i just tried this rom because CM6.1 is still to slow for me somehow.
it stopped after unpacking radio pack and tried to installe it..aborted installation.
All wiped and partitioned before.
Sry, would really like to give it a try.
Have German 32b Vodafone.
Cheers..
Hi!
I have some questions:
1. are there any differences between the Spanish 2.2.1 OTA ROM and the 2.2.1 UK ROM? What are the languages supported?
2. I come from spl 1.33.0013d and radio 2.22.27.08: what are the drawbacks of installing a perfect spl such as the 1.33.0013?
Thank you!
maxpower_303 said:
i just tried this rom because CM6.1 is still to slow for me somehow.
it stopped after unpacking radio pack and tried to installe it..aborted installation.
All wiped and partitioned before.
Sry, would really like to give it a try.
Have German 32b Vodafone.
Cheers..
Click to expand...
Click to collapse
What was the error when the installation aborted?
Puddux said:
Hi!
I have some questions:
1. are there any differences between the Spanish 2.2.1 OTA ROM and the 2.2.1 UK ROM? What are the languages supported?
2. I come from spl 1.33.0013d and radio 2.22.27.08: what are the drawbacks of installing a perfect spl such as the 1.33.0013?
Thank you!
Click to expand...
Click to collapse
1. I don't know, as I haven't checked the UK ROM, but probably they are both the same. In the spanish vodafone update there's support for english too.
2. SPL 1.33.0013d should work too. It's a modified version of 0013 to allow some additional operations. No need to install 0013. Radio 2.22.27.08 works too, but latest version, the one shipped with the vodafone update, is 2.22.28.25.
Greets.
For those who don't want to upgrade to a perfected spl (Want to stick to engineering spl) and are willing to accept the lower ram count I added ezterry's biffmod kernel/wifi module (oh and also added News and Weather app).
You can download it @ http://dl.dropbox.com/u/7812800/Android/vf_magic_frg83d_eng-signed.zip
Also if you want to use it without sim flash this after the main zip.. http://dl.dropbox.com/u/7812800/Android/Froyo_Provision.zip
Hope this helps anyone.
Btw.. Tested on Google Ion (Yes i got one lol)
I assume no liability for any damage to your phone!
You can use my complete rom or parts of it to make your own rom. Only post a small thanks on your owm thread.
Big thanks to: iaio72, spear1403, tgzw, Quarx, Simondo, ein1002, santimanuel, epsylon3 and ...
Language support for final 4.0 --> da, de, el, en, es, fi, fr, hr, hu, id, it, nb, nl, pl, pt, pt-BR, sv, th, ti, vi, zh_CH, zh_TW + arabic* and ru*
MS2Ginger 4.0
- based on 4.5.2-109-DHT-25 - Android 2.3.6 blur lite rom
- support for Defy, Defy+, Milestone 2, Bravo
- MS2Ginger4 can used as 2nd-system (tested on GB kernel only) !! system image file have to be >= 350 MB
- multibootmanger app by royale1223
- new bootmenu 1.1.8, CWM 5.0.5/6, multiboot big thanks to m11kkaa
- 2 way to boot the rom: normal and via 2nd-init (default)
- new reboot option form cm7.2 --> trigger: all keys at the same time vol- , vol+ , power (only tested on Defy)
- disabled blurhome rotation
- button backlight can set from 10-100 % via build.prop
- mmcfix from CM7
- CPU settings default safe 30/300 38/600 {48/800} 58/1000
- Camera will work on SOC and Bayer camera (green* and red)
- better camera support for bayer camera
- new 720p record* and play (Milestone 2 - Android 2.3.6 files)
- 720p record in m4v (h264 can be enabled via build.prop)
- Milestone 2 froyo camara app for SOC camera (fixed green strips)
- BlurHome from Milestone 2 - 2.3.6 (no widget updating bug)
- Battery min. 2-5 mA/h
- no wifi, apn, vpn bugs
- wifi channels 12, 13, 14 enabled
- bootmenu + cwm (vsel4/clk4 added) "did not work for SOC camera with greenbreadMOD"
- bootmenu with Stable, Custom, Stock-Recovery
- call record libs
- init.d support
- zipalign at boot
- ramscript
- backlight button fix for Defy with bayer camera (can removed via optional patch)
- deepsleep support
- max 10 finger multitouch
- support for farsi-arabic, hebrew (thanks to MMarv)
- CyanogenMod-settings not finished (alpha) - sorry, will try to fix it if i have more time.
(* via greenbreadmod for MS2Ginger4.0 and if you never flashed a Android 2.3.6 full sbf with bl7)
(* 720p record only for Bayer camera Defy and Milestone 2)
Download: ROM, BlurApps, Greenbread: (MS2Ginger4.0.zip, BlurApps-MS2Ginger4.zip,Milestone2patchMS2Ginger4.0withbaseband.zip )
Mirror 1 (google)
Mirror 2 (Dev-Host)
More information for BlurApps --> LINK
Soft-sim-unlock for MS2Ginger 4.0
based on Dabb guide: http://forum.xda-developers.com/showthread.php?t=1447950
Install View attachment 1129769 via CWM.
If you like MS2Ginger feel free to donate! Donations will be used to purchase a Defy with SOC camera (green lens)
Bugs and problems Reporting: http://code.google.com/p/ms2ginger/issues/list?can=1&q
- wifi bug like all 2.3.6 Motorola roms http://forum.xda-developers.com/showthread.php?t=1502817
(fixed, disable unlimited lease time for IP adress on your rooter)
Timeline:
19.06.12 - MS2Ginger 4.0 released
05.02.12 - MS2Ginger 3.0 released
Patch and updates for current release
none for MS2Ginger 4.0
HOW to INSTALL:
To begin:
Put the Nandroid backup folder MS2Ginger on the SDCard in this folder: /sdcard/clockworkmod/backup
Put "Milestone2patchMS2Ginger4.0withbaseband.zip" to the root of your sdcard
Put "Milestone2-GB-kernel-update.zip*" to the root of your sdcard (only if you have a froyo kernel)
-------------------------------------------------------
Root your Milestone 2 and Install BOOTMENU - CWM for Milestone 2
REBOOT
run 2nd-init (voldown on blue LED)
Go to "Recovery"
Go to "Latest or Stable or Custom Recovery"
"wipe data and cache"
Go to "Backup and Restore"
Go to "Advance Restore"
Select "MS2Ginger4.0"
"restore system"
Go to "install zip from sdcard"
select and install "Milestone2patchMS2Ginger4.0withbaseband.zip"
"Install "Milestone2-GB-kernel-update.zip" via install zip" (only if you have froyo kernel)
reboot
Booting up can take a while, max is about 10 minutes.
Team:
- walter79
- spear1403 (theming)
- santiemanuel
- Defy red lens tests spear1403
- Defy greens lens tests luciferps and Cristi_10
- Defy plus tests Dollo73 and free2live
- Milestone 2 tests Carolinux and Motodoido
Translation Team: (each language max. 4 person) View attachment 806172
Brazillian Portuguese: pupiloalpha , Cassinander , filipeazev
Bulgarian Auris 1.6 vvt-i
Farsi: MMarv
Hungarian: szabof1 , balika01
Polish: yackoo , szacuken , Antszej
Serbian: atomskasarma
Spanish espaciosalter20
Spanish-Argentina YaPeL
walter79 said:
Welcome.
The idea:
Defy is running Milestone 2 Android 2.2.2 ROMs. (DACH retail based)
So maybe we could make a working Gingerbread for Milestone 2.
- Defy has rooted only Android 2.3.4 /system nandroid-backup http://forum.xda-developers.com/showpost.php?p=14793844&postcount=8
- it is also possible to run 2nd-init on milestone 2
- read this (Defy 2nd-int + froyo kernel + Gingerbread-system working) http://forum.xda-developers.com/showthread.php?t=1130656
- i think it could be possible to get gingerbread working on milestone 2
- basband should be change with original milestone 2 files
- /lib/hw/ from milestone 2 needed
- kernel from milestone 2
- fix for camera
Whats your opinion?
Click to expand...
Click to collapse
I'm sorry to kill your optimism, but we are unable to flash onto /system for now. Big files at least..
Did clockworkmod not work?
http://www.gamaze.com/blog/2010/11/installing-clockworkmod-recovery-on-motorola-milestone-2/
walter79 said:
Did clockworkmod not work?
http://www.gamaze.com/blog/2010/11/installing-clockworkmod-recovery-on-motorola-milestone-2/
Click to expand...
Click to collapse
It works, it's just that.. it doesn't flash big update.zip's, which overwrite the whole system. Problem could be caused by us not having a recovery build specifically for our devices.
But nandroid backup works, or?
Mikevhl said:
It works, it's just that.. it doesn't flash big update.zip's, which overwrite the whole system. Problem could be caused by us not having a recovery build specifically for our devices.
Click to expand...
Click to collapse
So build one: https://github.com/koush/Droid2Bootstrap
Edit: Check this out "use an update.zip that waits a bit longer for the system to settle then unmounts tmp and remounts /"
dangpzanco said:
So build one: https://github.com/koush/Droid2Bootstrap
Edit: Check this out "use an update.zip that waits a bit longer for the system to settle then unmounts tmp and remounts /"
Click to expand...
Click to collapse
Nice. Will try to get a clean nandroid backup of my /system, unyaffs it and create my own update.zip formatting /system and using this trick to see if I it works.
r2beta0 said:
Nice. Will try to get a clean nandroid backup of my /system, unyaffs it and create my own update.zip formatting /system and using this trick to see if I it works.
Click to expand...
Click to collapse
Lol, I think it's a lucky shot finding this...
Sent from my Milestone 2 XDA App
Hey, what happens if I flash Defy's SBF on M2? Besides other problems is it possible to enter bootloader mode and flash another sbf, or it will corrupt the device?
I didn't, but I saw it was a prerequisite for the Rom posted here, so if there's theorical trouble, then I won't try.
Also I found out that Droid 2 bootloader image has the same first and last bytes as M2 (but different check sums), and Defy's is little different.
dangpzanco said:
Hey, what happens if I flash Defy's SBF on M2? Besides other problems is it possible to enter bootloader mode and flash another sbf, or it will corrupt the device?
I didn't, but I saw it was a prerequisite for the Rom posted here, so if there's theorical trouble, then I won't try.
Also I found out that Droid 2 bootloader image has the same first and last bytes as M2 (but different check sums), and Defy's is little different.
Click to expand...
Click to collapse
Did not work.
dangpzanco said:
Hey, what happens if I flash Defy's SBF on M2? Besides other problems is it possible to enter bootloader mode and flash another sbf, or it will corrupt the device?
I didn't, but I saw it was a prerequisite for the Rom posted here, so if there's theorical trouble, then I won't try.
Also I found out that Droid 2 bootloader image has the same first and last bytes as M2 (but different check sums), and Defy's is little different.
Click to expand...
Click to collapse
I don't think RSD Lite will allow you to do that. Even if it does, I don't think it's a good idea since it may replace your bootloader potentially bricking your phone.
r2beta0 said:
I don't think RSD Lite will allow you to do that. Even if it does, I don't think it's a good idea since it may replace your bootloader potentially bricking your phone.
Click to expand...
Click to collapse
Yeah, I thought about that bricking stuff... (maybe linux/mac sbf_flash would flash it)
Did the "update.zip that unmount tmp and remounts /" work?
Sent from my Milestone 2 XDA App
dangpzanco said:
Yeah, I thought about that bricking stuff... (maybe linux/mac sbf_flash would flash it)
Did the "update.zip that unmount tmp and remounts /" work?
Sent from my Milestone 2 XDA App
Click to expand...
Click to collapse
Not yet, still working on it on my free time. Unfortunately 'free time' is a scarce resource
Maybe if you point the update-script to another script:
Code:
#!/system/bin/sh
#This was in Apex 1.4.1 /etc/init.rc folder (wait for system to settle?)
sleep 24s
#unmount tmp
busybox umount /tmp
#remount /
busybox mount -o remount -rw -t rootfs /
Will it work?
dangpzanco said:
Maybe if you point the update-script to another script:
Code:
#!/system/bin/sh
#This was in Apex 1.4.1 /etc/init.rc folder (wait for system to settle?)
sleep 24s
#unmount tmp
busybox umount /tmp
#remount /
busybox mount -o remount -rw -t rootfs /
Will it work?
Click to expand...
Click to collapse
First attempt failed. I had some problems formatting /system partition. The only way I could get it to format was through Recovery Menu. Maybe the problem is reformatting the system. The command mount("MTD", "system", "/system") also doesn't work. I'm starting to think that Motorola messed with the file system. Will try again using delete_recursive instead of format.
There is any d2 / d2g rom based on GB?
With all the problems developers were facing lately, I guess motorola add the same "weird" protections in m2 2.2 to GB d2 rom
It's very hard to make a custom ROM with all these protections and without knowing what happens when phone tries to boot. All we get is the damned M logo and no info at all. Without some output from the phone everything we can do is guessing.
I was reading that new fission roms based on GB (for d2), were facing the "motorola logo" stuck problem. That´s why the developer gave up.
But, like you say, there is no way to know if it´s the same problem.
I have no knowledge at all on android platform. I´d stuck on winmo 6.
If you need some testing, I can try, there is nothing more I can offer
Second attempt failed. It may have nothing to do with format or system file. I'm really clueless Jut the M logo again. Maybe the /system protection checks for some date/time on some random file? Will reflash with RSD and 'touch' everything in /system to see if the damned thing still boots.
Did you compare the hash of apex files to the moto original files?
Notice (4/16/14): I'm no longer here. I've said "goodbye" to AT&T and their locked bootloader schemes. I'm voting with my wallet - I've sold my I337 and switched to T-Mobile. My apologies to the community, but you're now on your own here.
"I337UCUAMF3 Unadulterated"
This rom is a 100% pure, untouched copy of the System and Kernel that came with the MF3 OTA update. The first question that many will have is, "Why did you release this - why wouldn't I just use <insert name here>'s stock rom?" It's simple: every other rom in this forum (at this time) has been modified from the original stock rom - whether they've added root, de-odexed it, debloated it, or otherwise. Because the Unadulterated rom is 100% stock (with stock kernel), it is possible for other developers to flash this rom and use it as a platform for attempting to find a root method for the MF3 users out there already. Plus, I like to make my own modifications from a stock base.
UPDATE (8-1-13): a root method has been found for MF3. See thread here. This ROM's purpose has been fulfilled, but your are still welcome to use it, of course!
UPDATE: The MF3 Odin files have been uploaded by @Shockndrop over in his thread here. Remember that the Odin files will flash your bootloader to MF3 (if you allow them), so be careful out there.
Rest assured, this rom will not update your bootloaders, it will not break your custom recovery, and it won't flash your modems. Like most roms, it will simply replace your /system and flash a Kernel. It's also scripted to wipe cache and dalvik for you. It will not wipe your /data partition - you might want to do so if you run into problems, especially when coming from other roms.
Next, you might ask, "How can you say this is 100% stock? How did you construct it?" I'll hide nothing from you - you can build it yourself if you'd like. Here's how I did it:
Rooted with motochopper
Installed TWRP 2.6.0.0
Wiped data & cache
Odin to MDL stock
Allow one full reboot:
Boot script runs (installs CSC - this is REQUIRED for the MF3 update to patch correctly)
Clears up any SysScope flags, etc. that may have persisted from previous rom or root.
"Temporary Root" using motochopper:
Code:
adb shell chmod 755 /data/local/tmp/pwn
adb shell /data/local/tmp/pwn
adb shell rm /data/local/tmp/pwn
NOTE: Possible outcomes of temporary root:
Failure
Success, motochopper exploit hangs, device spontaneously reboots
Success, immediate return to prompt, but adb shell is still not root (indicated by $ prompt)
Success, immediate return to prompt, adb shell is root (indicated by # prompt)
Repeat as needed (usually only twice or so?)
NOTE: Don't both trying to run su. It isn't installed. We're just relying on motochopper to give us a temporary adb root shell.
From adb root shell, installed TWRP recovery:
Code:
dd if=/sdcard/openrecovery-twrp-2.6.0.0-jflteatt.img of=/dev/block/mmcblk0p21
Rebooted, checked to be sure system status is still Official. Note that at this point, we've got a 100% stock MDL rom, without root, but with a custom recovery. Woot.
Rebooted into TWRP, installed custom-neutered OTA update (mf3-sys-only.zip), which only does the following:
Verifies all system files
Removes "unneeded" files (as determined by AT&T, not me)
Patches files
Copies new files
Sets permissions
Patches build.prop
Wiped data & cache for good measure
Booted phone, verified ROM works okay, system status = official. Rebooted, checked Odin Mode:
Code:
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
Booted back to TWRP to begin pulling dumps
... Now, on to the good stuff!
ROM Install Instructions:
Download mf3-stock-rom.zip and place it on your internal sdcard.
Make a nandroid backup of your existing system, data, cache, and anything else you deem important (everything!).
Flash/install the zip using your favorite custom recovery. This part should take several minutes - the file is huge!
Optionally, flash any additional Add-ons that you want (e.g. SuperSU for root)
Optionally, flash a custom kernel (use instructions from the kernel's author!). Note that some custom kernels will need you to flash Loki-Doki. The included kernel does not require Loki patching! It is 100% stock, and your system will accept it as-is.
Optionally, wipe /data. You can skip this, but if you get a ton of force-closes or extreme problems, this would be one of the first troubleshooting steps.
Reboot, and enjoy!
Click to expand...
Click to collapse
Important Recommendation:
You are advised to disable the OTA update applications! If AT&T/Samsung release a new OTA update (beyond MF3), it is theoretically possible to download and install it while using this rom! Accepting such an update could do just as much damage as the original MF3 update did. You can easily disable OTA updates from a root ADB shell using the following commands:
Code:
pm disable com.wssyncmldm
pm disable com.LocalFota
pm disable com.sec.android.fwupgrade
You could also use Titanium Backup Pro to accomplish the same thing. I will later look into the possibility of disabling these using a flashable Add-on zip that otherwise keeps your system as stock as possible.
Known Bugs:
If you do not flash a custom kernel, you will lose WiFi. The WiFi in the MF3 Kernel is expecting the MF3 bootloaders, which we aren't flashing. Therefore it breaks.
If you happen to have the MF3 modem/baseband installed, your WiFi might work, but your sound may stop working completely. This is also a result of not having MF3 bootloaders. A custom Kernel should fix this too.
If you use the "remove-SysScope" Add-on, be careful of any other mods that may poke around with SecSettings.apk - these are rare, but there's some risk of conflict here.
With the custom kernel I installed, I frequently received the "The device has detected an application attempting..." message. This can be pinpointed to the KNOX agent, and can be fixed a different ways (your choice!):
I found this post to be very helpful.
You can also try using the command pm disable com.sec.knox.seandroid from a root ADB shell. This just freezes the app. Personally, I used this method.
@jeboo also mentioned that the KNOXAgent.apk can be patched using smali/baksmali. Check out his post about it.
Also with the kernel I installed, there was a bug regarding updating the camera firmware. I was forced to restore the stock kernel temporarily, open the camera app to update the camera firmware, and then re-flash the custom kernel. The original MF3 kernel is included in the Add-ons.
Any other bugs are likely straight from AT&T/Samsung, otherwise they could be from your custom kernel, if you flashed one.
Be sure to make good backups of everything, and be prepared to use Odin back to stock. One member has reported that after flashing away from this rom to any other rom/kernel, their SIM card would not work until they used Odin to return to stock. After Odin, it worked fine.
It seems most custom kernels are expecting you to have an MDL baseband. Some people are reporting strange issues (such as problems with video streaming) when using MF3 modems and their choice of custom kernels. Check out File #11 for various modems, NON-HLOS modems, and kernels.
Custom Kernels:
Here's a list of custom kernels that are known-working with this rom. Please feel free to test and report other working kernels, and I will gladly add them to the list!
@jeboo's Kernel - built for @shoman94's SHOstock rom. Available in post #3 of their thread.
@Jamison904's Bioshock Kernel - available on the Infamous Development Website. This kernel is working great for me - no issues to report at this time. It also includes BusyBox v1.19.3, which was particularly useful for me. It appears that the kernels in their thread require Loki-Doki to be flashed after flashing the kernels. However, the one that I downloaded came from here: http://d-h.st/WVs and it was pre-patched for the I337.
@Jamison904's Infamous Kernel works really well, it seems. It also has BusyBox v1.19.3. I'm currently using v4.0, but there are newer versions available on his Dev-Host folder. These are for the M919, so flash Loki-Doki afterwards if you're on I337!
Downloads:
I've provided the rom in several different formats. When I last tested the odin-flashable tarballs, they did not work for me (due to signatures, etc). However, I'm still providing these for a few XDA members who will be testing them out on their semi-bricked devices. Additionally, someone might be able to get these signed somehow, and I'll leave this hanging out there as an invitation.
File #1 - mf3-stock-rom.zip - CWM/TWRP-Flashable ROM .zip file - created by hand (you are welcome to dissect it if you'd like - take a look inside the updater-script)
Files #2-#7 (individual image files and odin-flashables):
File #2 - system.img.ext4 - EXT4 format copy of the System partition - pulled using make_ext4fs in TWRP:
Used fdisk to obtain partition size:
Code:
# fdisk -l /dev/block/mmcblk0p16
Disk /dev/block/mmcblk0p16: 2894 MB, 2894069760 bytes
4 heads, 16 sectors/track, 88320 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p16 doesn't contain a valid partition table
Dumped the partition:
Code:
# make_ext4fs -s -l 2894069760 -a system /sdcard/system.img.ext4 /system
Creating filesystem with parameters:
Size: 2894069760
Block size: 4096
Blocks per group: 32768
Inodes per group: 8032
Inode size: 256
Journal blocks: 11040
Label:
Blocks: 706560
Block groups: 22
Reserved block group size: 175
Created filesystem with 3192/176704 inodes and 584765/706560 blocks
File #3 - system.img - Binary copy of the System Partition - pulled using dd:
This was much easier to create:
Code:
# dd if=/dev/block/mmcblk0p16 of=/sdcard/system.img bs=4096
File #4 - boot.img - Kernel - pulled from the OTA update file
File #5 - mf3-sys-boot.tar.md5 - "Odin-flashable" tarball - created without any modification:
Using a Linux PC or Cygwin, executed the following:
Code:
$ tar -H ustar -c system.img.ext4 boot.img > mf3-sys-boot.tar
$ md5sum -t mf3-sys-boot.tar >> mf3-sys-boot.tar
$ mv mf3-sys-boot.tar mf3-sys-boot.tar.md5
File #6 - mf3-sys-boot-sgs4ext4fs.tar.md5 - "Odin-flashable" tarball - "bloated" with Chainfire's sgs4ext4fs
Using a Linux PC (I used Ubuntu 13.04 64bit - couldn't get the win32 version to process the file entirely):
Code:
$ mv ./sgs4ext4fs.linux.amd64 ./sgs4ext4fs
$ sudo chmod 755 ./sgs4ext4fs
$ mv system.img.ext4 system.img.ext4.orig
$ ./sgs4ext4fs --bloat system.img.ext4.orig system.img.ext4
Optionally, you can use the "--list" option to view the file before and after the bloating. Once complete, pack it up in a tarball again.
File #7 - mf3-factoryfs.tar.md5 - "Odin-flashable" tarball - created using the system.img instead:
Using a Linux PC or Cygwin, executed the following:
Code:
$ mv system.img factoryfs.img
$ tar -H ustar -c factoryfs.img boot.img > mf3-factoryfs.tar
$ md5sum -t mf3-factoryfs.tar >> mf3-factoryfs.tar
$ mv mf3-factoryfs.tar mf3-factoryfs.tar.md5
Files #8-#11 (Add-ons!):
File #8 - UPDATE-SuperSU-v1.41.zip - ROOT! Flash this to root your new MF3 rom!
Original is found on Chainfire's website.
File #9 - remove-SysScope.zip - Want to stay "Official", even though you rooted? Flash this! It will remove SysScope and customize your SecSettings.apk to not check for SysScope anymore. Must be flashed before first boot, otherwise you'll just be stuck with a "custom" status until you remove it by some other means.
File #10 - mf3-kernel-only.zip - Want to quickly flash back to the MF3 stock Kernel again? Flash this. No need to use Loki-Doki after flashing this - the I337 will accept this just fine and boot.
File #11 - all-kernel-modem-apnhlos.zip - My personal collection of flashable .zip's of all available versions of the stock kernel, stock modem, and stock NON-HLOS modem for the I337 - including MDB, MDL, MF3. Unzip this file first, and flash individual partitions/versions in whatever combination you want.
Disclaimers, etc.:
I have only tested this with my AT&T Galaxy S4 (I337). While you are welcome to try this with other devices, I can't guarantee anything!
You are free to use this ROM, whole or in part, as a base for any other rom, mod, or otherwise. I do not gain profit from this, and the original rom was of course made by AT&T and Samsung. All I'm providing is a way to install it safely and easily. If you do use this rom as a base, please mention my name in your credits/thanks (thank you!).
I cannot be held liable for any damage you do to your own devices due to not following instructions or cataclysmic events beyond my control. Like any other rom, you assume all risks by flashing it to your device.
If you appreciate my work, please use the THANKS button below to let me know!
reserved...
First .. ..... Hey guess u got ur phone up and running huh ?
Nice post man! I still have hope for your recovery process
Here's another way to remove that annoying message without killing the entire APK:
http://forum.xda-developers.com/showthread.php?p=41794748#post41794748
as expected...
Aou said:
"I337UCUAMF3 Unadulterated"
This rom is a 100% pure, untouched copy of the System and Kernel that came with the MF3 OTA update. The first question that many will have
.......
[*]I have only tested this with my AT&T Galaxy S4 (I337). While you are welcome to try this with other device, I can't guarantee anything!
[*]You are free to use this ROM, whole or in part, as a base for any other rom, mod, or otherwise. I do not gain profit from this, and the original rom was of course made by AT&T and Samsung. All I'm providing is a way to install it safely and easily. If you do use this rom as a base, please mention my name in your credits/thanks (thank you!).
[*]I cannot be held liable for any damage you do to your own devices due to not following instructions or cataclysmic events beyond my control. Like any other rom, you assume all risks by flashing it to your device.[/list]
If you appreciate my work, please use the THANKS button below to let me know!
Click to expand...
Click to collapse
The result was what was expected.
Keeping my fingers crossed for other solutions...
iB4STiD said:
First .. ..... Hey guess u got ur phone up and running huh ?
Click to expand...
Click to collapse
Nope! Ended up needing to replace it, unfortunately. The original is a 100% hard brick. It won't even take the MF3 firmware via JTAG.
jeboo said:
Nice post man! I still have hope for your recovery process
Here's another way to remove that annoying message without killing the entire APK:
http://forum.xda-developers.com/showthread.php?p=41794748#post41794748
Click to expand...
Click to collapse
Awesome - thanks! I'll add that to the list of options. Also, thanks again for your awesome Kernel. v1.4 is exactly what I need for my phone.
SaltyFoam said:
The result was what was expected.
Keeping my fingers crossed for other solutions...
Click to expand...
Click to collapse
This is really unfortunate, but somewhat expected (as you've said). Have you tried the Odin-flooding again (even with the MDL or MF3 Recovery) yet? That was a very interesting accidental discovery you made. I'm going to have to try that myself too! It might have been a fluke, but still worth investigating.
As an update: The last file (mf3-factoryfs.tar.md5) has finished uploading, so I'm adding the link to the OP now.
FINALLY, someone else that respects untouched firmware. Glad to see this.
The odin flooding is not working at this point.
apparently one of the features of the new odin mode (aboot?) is that once it gets the 'failed auth' it stops responding to further pushes. It does not even allow the connection to be setup until a power down and restart.
As you can see in the other thread I submitted a warranty claim and they are replacing the device: as I have no backup device and a family that needs to get in touch with me (i.e. my wife and mother scolding me for not having a phone) I ran out of time...
I still have a few days with the old device before the replacement arrives...
I any case I am off to work.
If anyone wants to help create a flashable-zip that would disable the OTA updates without touching /system, I'm working on it here:
http://forum.xda-developers.com/showthread.php?t=2379517
I just need someone to write something up in a bash script that will make modifications to a file in /data. Should work without rooting the system.
Jah0n said:
FINALLY, someone else that respects untouched firmware. Glad to see this.
Click to expand...
Click to collapse
One thing I've seen in many "stock" roms is: "Completely stock, except for this.... and this.... and this mod I made here.... and this...."
-_-
I was curious - wanted to see what a true stock would feel like after all this time I have been rooted and using custom roms - anyway -I flashed this - everything seemed to work ok - but after restoring a nandroid - I lost data completely - I tried flashing a new rom and I got an error when trying to set it up saying that I needed to install my SIM - I tried to go into settings to add my APN and that error about the SIM came up again and would not let me add APN.
I could not get data to work on any nandroid or new flash and I ended up using odin to flash back to stock and then re-rooted.
I don't know if it was related to this rom -but it seems to be the only thing that could have caused it - unless you have an idea?
We should really team up on something sometime. I just created a hybrid stock UCUAMF3 kernel with the international (i9505) newest XXUBMGA image ROM. I removed the bloat but kept everything that is needed for all the settings to function. It runs so smooth, I'm not sure I want to go back to Google Edition... To release, or not to release. Okay, I'm done rambling. Great work so far from what I see here. Keep em clean!
mocsab said:
I was curious - wanted to see what a true stock would feel like after all this time I have been rooted and using custom roms - anyway -I flashed this - everything seemed to work ok - but after restoring a nandroid - I lost data completely - I tried flashing a new rom and I got an error when trying to set it up saying that I needed to install my SIM - I tried to go into settings to add my APN and that error about the SIM came up again and would not let me add APN.
I could not get data to work on any nandroid or new flash and I ended up using odin to flash back to stock and then re-rooted.
I don't know if it was related to this rom -but it seems to be the only thing that could have caused it - unless you have an idea?
Click to expand...
Click to collapse
It sounds like the other rom you flashed did not have a kernel. Easiest way to check is to open the zip file and check for a "boot.img" - that's the kernel (not the bootloader).
That's strange that your nandroid would not backup Data - did you check that option when you made the backup?
Jah0n said:
We should really team up on something sometime. I just created a hybrid stock UCUAMF3 kernel with the international (i9505) newest XXUBMGA image ROM. I removed the bloat but kept everything that is needed for all the settings to function. It runs so smooth, I'm not sure I want to go back to Google Edition... To release, or not to release. Okay, I'm done rambling. Great work so far from what I see here. Keep em clean!
Click to expand...
Click to collapse
Awesome! If the kernel turns out alright, we could add it to the list in the OP.
Aou said:
It sounds like the other rom you flashed did not have a kernel. Easiest way to check is to open the zip file and check for a "boot.img" - that's the kernel (not the bootloader).
That's strange that your nandroid would not backup Data - did you check that option when you made the backup?
Click to expand...
Click to collapse
The other rom had a kernel, but it doesn't matter because I flashed a different kernel with the other rom - the kernel was not the problem. If it didn't have a kernel, the rom never would have booted in the first place.
The problem is that mobile data did not work - at all. PLUS When I tried to add manually add an APN - it told me that I needed to add my SIM CARD. My SIm Card was fine - I never uninstalled it -
I have flashed and restored hundreds of roms and never had this happen before.
Something happened when I flashed your rom - that wiped out something related to my sim card.
I don't know what that would be - but as a result of flashing this rom - it happened. Just to verify, I redownloaded the rom - flashed it - and the same thing happened the 2nd time.
The phone booted fine and started the setup process - wifi worked fine - but the data bars showed NO DATA. I tried to manually add an APN and I got the same SIM CARD ERROR -so - when I tried to restore a nandroid - I got the same SIM CARD ERROR- I tried flashing a new rom - and got the same error - - the ONLY way I could fix it was to use ODIN and return to stock.
SO - Not sure why I seem to be the only one this has happened to - luck of the draw or something -
mocsab said:
The other rom had a kernel, but it doesn't matter because I flashed a different kernel with the other rom - the kernel was not the problem. If it didn't have a kernel, the rom never would have booted in the first place.
The problem is that mobile data did not work - at all. PLUS When I tried to add manually add an APN - it told me that I needed to add my SIM CARD. My SIm Card was fine - I never uninstalled it -
I have flashed and restored hundreds of roms and never had this happen before.
Something happened when I flashed your rom - that wiped out something related to my sim card.
I don't know what that would be - but as a result of flashing this rom - it happened. Just to verify, I redownloaded the rom - flashed it - and the same thing happened the 2nd time.
The phone booted fine and started the setup process - wifi worked fine - but the data bars showed NO DATA. I tried to manually add an APN and I got the same SIM CARD ERROR -so - when I tried to restore a nandroid - I got the same SIM CARD ERROR- I tried flashing a new rom - and got the same error - - the ONLY way I could fix it was to use ODIN and return to stock.
SO - Not sure why I seem to be the only one this has happened to - luck of the draw or something -
Click to expand...
Click to collapse
Makes a lot more sense now - thought you meant your data partition. >_<
And by another rom not having a kernel, it's still possible for roms to not include a kernel and work - the kernel lies in a separate partition and would remain untouched if the new rom didn't flash this.
I'll add this situation to the bugs list - thank you for the report!
Aou said:
Makes a lot more sense now - thought you meant your data partition. >_<
And by another rom not having a kernel, it's still possible for roms to not include a kernel and work - the kernel lies in a separate partition and would remain untouched if the new rom didn't flash this.
I'll add this situation to the bugs list - thank you for the report!
Click to expand...
Click to collapse
The kernel lies in a separate partition but twrp wipes it away by default so you'd have to unmount the boot partition
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Is boot.img a compressed file?
jortex said:
Is boot.img a compressed file?
Click to expand...
Click to collapse
I did not compress it at all. However it is not a full 10MB either. It's the exact file that came from the MF3 update package. The way that the OTA update .zip installs it is by doing this:
Code:
package_extract_file("boot.img", "/dev/block/platform/msm_sdcc.1/by-name/boot");
If you need a full 10MB partition dump (i.e. using dd or a nandroid), I can upload those if you need them for any reason.
UPDATE: I just did a binary comparison of the boot.img that came from the OTA .zip (the one I uploaded), and a nandroid backup I made. It was 100% identical, except the nandroid was padded with zeros at the end (a couple megabytes of zeros...)
Added another kernel to the list:
@Jamison904's Bioshock Kernel - available on the Infamous Development Website. This kernel is working great for me - no issues to report at this time. It also includes BusyBox v1.19.3, which was particularly useful for me.