Database Info

[ROM] Unwatermarked, Official, Hero

As promised..
You need to obtain the new SPL and Radio first PRIOR to installing this ROM. Follow this post.
Installation:
1. Download http://www.droiddeveloper.com/hrbuilds/app_s.zip
2. extract "app_s" into your sdcard's ext2 partition.
3. Download http://www.droiddeveloper.com/hrbuilds/hero-signed.zip
4. Place on regular sd card.
5. Reboot into recovery, wipe and flash.
6. Enjoy.
Only thing that shouldn't work at the moment is bluetooth and some minor features.. besides that you have a fully functional hero rom.
enjoy guys..
Phuck the leakers, and there supporters.
EDIT: as far as the bluetooth problem goes, i haven't played with a fix just yet.. i've spent this free time since i've quit to catch up on homework guys.
this is not me coming back.... this is just to clear my conscience, and a big "Phuck YOU" to the leakers
EDIT2: it's using ext2 instead of ext3 because, again, i haven't worked on the rom since i've quit..
for those of you that don't know how to place app_s into sd card do this:
Code:
adb push app_s /system/sd/app_s
enjoy.
EDIT3: /system/app wouldn't fit.. and if i did /data/app_s like before, it wouldn't give you any space in /data this is why i did it this way.
and yes.. this has Rosie.

Enable Superuser.apk & Enhance ROSIE UI FOR HERO ROM
Bluetooth debuging on Hero
Clean up rosie!!
HTC Hero Speedup v2.0
HTC Hero Rosie UI toggle

How you put App_s into the ext2 partition

THE HERO HAS RISSEN! But really,thanks.
EDIT:how do I put the app_s onto a ext2 partion via windows? I lost my linux live cd.

wich one do we download 1 or 3 ?
and thanks alot haykuro much love dawg thanks again

I dont use Apps2SD so can i just add the app_s back to the data folder and resign?

F!! Why does it have to be on an ext2? I cant get the permissions yo ork on my sdcard! Is there a way to avoid this?
And ps. Good god thank you!

If you dont, then wait for someone else to say how. This isn't a tech. It's apps2sd method or none right now.

@justanothercrowd no, this requires apps2sd because its so large.
@ynghova187 and dutman yes

So how would I go about on doing step 3? Srry I just unrooted my phone because it was randomly shutting off, and now I see this, and I want to root. lol.

Darkrift said:
@justanothercrowd no, this requires apps2sd because its so large.
@ynghova187 and dutman yes
Click to expand...
Click to collapse
For someone whos never used apps2sd, is there a quick tutorial for this?
I've searched, but theres nothing that i found about putting a "app_s" folder onto the partition...
Sorry for the n00b question, im usually pretty good with this type of stuff, but i'm at a loss

Darkrift said:
@justanothercrowd no, this requires apps2sd because its so large.
Click to expand...
Click to collapse
Which method(s) should work? I've seen at least 5 so far, including an application or two.

will my apps2sd application automatically move this apps folder to partion2?

dutman said:
So how would I go about on doing step 3? Srry I just unrooted my phone because it was randomly shutting off, and now I see this, and I want to root. lol.
Click to expand...
Click to collapse
Step 3 is simply downloading a file. Is that really what you need help with?

if i dont have apps to sd what links can i download any help i never used apps to sd

This would be the perfect time for the few of us that still haven't been using apps2sd
nice that this has rosie.
Which tut would is the most widely used and most compatible method

startekee said:
How you put App_s into the ext2 partition
Click to expand...
Click to collapse
same question i am using windows... and i used paragon to partition my card before... but windows does not show ext2... is there a way around this??

ext2...
adb push app_s /system/sd
?
where do i put that into, im sorta new to this and i have the ion rom right now.. also do we need the special spl?

No, I need help with Step 2. Sorry that was a typo. And do you have an answer for me Mr. mikedmeyer?

281 said:
adb push app_s /system/sd
?
where do i put that into, im sorta new to this and i have the ion rom right now.. also do we need the special spl?
Click to expand...
Click to collapse
I can't help you with ADB, but if you are running a linux distribution, load GPartEd and you can format your card (if you havent already) and place it on the ext2 partition.

Auto Swap ----- linux-swap

Thanks to JAC for telling me how to do it, and to Denkai for providing all the necessary parts.
This is a modified ap2sd.sh to auto run the linux-swap partition on boot.
adb remount
adb shell rm /system/bin/a2sd.sh
adb push /pathtofile/a2sd.sh /system/bin
adb reboot
this can be done in terminal too.
The file is attached.
NOTE: I HAVE ONLY TESTED THIS ON JACHERO2.3.2 use at your own risk.
Please reference this thread http://forum.xda-developers.com/showthread.php?t=531988 to see what swap method I'm talking about.

What build is this for?
I am using soulife's rogers with a modified a2sd and this would definitely put my phone in a boot loop.

AWESOME! Thanks ccyrowski!

boogie1077 said:
What build is this for?
I am using soulife's rogers with a modified a2sd and this would definitely put my phone in a boot loop.
Click to expand...
Click to collapse
For JACHero 2.3.2

Where does init.rc go? On system/sd?

is it necessary to use swapper after this.. should we turn swapper off?

ComplexMinded said:
is it necessary to use swapper after this.. should we turn swapper off?
Click to expand...
Click to collapse
don't use swapper.
You have to have three partitions on your sdcard to do this
fat32
ext2 or ext3
linux-swap

it is.. I just wanted to be 100% sure.. just wonderling I also saw a format for linux swap2.. any difference?

I know it has been asked already. But were does init.rc go?

Z҉A҉L҉G҉O̚̕̚ said:
I know it has been asked already. But were does init.rc go?
Click to expand...
Click to collapse
Don't worry about the init.rc

Ok. Thanks for answering.

can someone check for vers. 2.3.3?
for me it's not working

ibu2002 said:
can someone check for vers. 2.3.3?
for me it's not working
Click to expand...
Click to collapse
im about to test it out right now
will report back with updates :-D

bigballa said:
im about to test it out right now
will report back with updates :-D
Click to expand...
Click to collapse
Worked fine for me.
Just actually included it in a ROM I whipped up from JAC 2.3.3 so you can flash the ROM with three partitions (swapper app already removed) and everything loads up for you without you doing anything.
Any requests for additional things to be removed?

i followed your instruction but after the reboot there was no swap.

ibu2002 said:
i followed your instruction but after the reboot there was no swap.
Click to expand...
Click to collapse
Is the third partition on your sdcard "linux swap"?
Open terminal
$ su
# free
If you want ill upload the rom i made for myself with a few customizations. It will do everything for you.

yes the third partition is linux swap and if i use denkai's method it works.
After a reboot the swap settings are lost and #free prints only 0 within swap.

man xda is so slow lately

c:\Android>adb shell free
total used free shared buffers
Mem: 98908 97152 1756 0 32
Swap: 0 0 0
Total: 98908 97152 1756
Click to expand...
Click to collapse
its not working for me
i put the script in the correct area
but its not swapping anything
i know it says its for 2.3.2 but im trying it on 2.3.3 maybe thats why

ibu2002 said:
yes the third partition is linux swap and if i use denkai's method it works.
After a reboot the swap settings are lost and #free prints only 0 within swap.
Click to expand...
Click to collapse
so how do we get the swap to start back up? thats the question

[PATCH][ANY RADIO] Change partition size! 300MB+ /data with the NEW RADIO!

Ever regretted switching to the new radio because of the really small data partition? You've come to the right place!
While sifting through the G1 forum i Have come across this wonderful tool by firerat and lbcoder!
(For newest version check firerat's thread:HERE )
Basically, it is a tool for resizing partitions of your phone.
IT CAN BE USED FOR ANY RADIO AND ANY MAGIC/SAPPHIRE PHONE! TAKE THE SAME STEPS!
How should I use it?
Here are some basic steps that anyone should follow to get a gigantic data partition!
1. Flash a ROM of your choice
2. Run "adb shell df"
3. See how much data is on /system and /cache
3.' Put mtdpartmap.txt and both patches on the ROOT of your SDCARD
4. In mtdpartmap.txt write slightly larger values ( for example if a ROM takes up 158MB, write 160 and if cache is 2.5MB write 3)
5. Make a nandroid backup
6. IMPORTANT: boot into fastboot and run "fastboot erase system -w"
7. boot into recovery and flash the recovery patch
8. IMPORTANT: Run "adb shell reboot recovery"
9. Restore nandroid
10. Flash Boot patch
11. ENJOY!
N.B You need to perform step 10 every time you flash or restore a ROM.
mtdpartmap.txt looks like this:
Code:
90 2
Where "90" stands for /system space and "2" for /cache space. Change these values but be sure to check step 2. Changing partition size is as simple as changing those two values.
N.B If you are using a ROM that has dalvik-cache moved to cache disregard the amount of space used on the cache partition and set it to 3MB as a test, increase in case of problems. Dalvik-cache WILL BE CREATED ON THE DATA PARTITION. (It is bind-mounted, and basically then /cache is as large as /data)
With a clean install of CursorSense I was able to get 290MB of usable data space, but for example Fusebox Froyo should only take up about 90MB of /system space so you could get 370MB of data! (if I calculated right )
ALL credits go to firerat and lbcoder! Please give them credit where it is due.
Thanks!

I do not understand,which value I write in txt free or used space?

If a rom uses 98MBs then write 100... Basically then it will create a 100MB large partition.
Sent from my HTC Magic using XDA App

First I check my space it is 158,I write 160,and I Folow our yours steps...
In the end I reboot my phone,and I chech again,is is a same,now I have 158 used space again.It seams do not work on my HTC.Please help

Did you perform all the stepps exactly how I wrote them?
The mtdpartmap.txt has to contain two values. Not just 160 but for example 160 3
Sent from my HTC Magic using XDA App

Nice work, I've already put together automatic system deletion plus recovery patching and I'll be releasing an update for smoki soon enough and I'm already in the process of creating automatic rom flashing plus patching the bootimg. So...great work, no need anymore for moving the dalvik cache to /cache...and in return we should get better first boot times(creating dalvik cache natively on /data is faster than on /cache)

Nice! I like that people started implementing this. Personally, i think its a HUGE improvement!
Sent from my HTC Magic using XDA App

eyegor said:
The mtdpartmap.txt has to contain two values. Not just 160 but for example 160 3
Sent from my HTC Magic using XDA App
Click to expand...
Click to collapse
Yes,my system is 158,my cache is 64,and I put in txt 160 66,and folow all steps.
I ll try again

Put 160 3. You cant expect a major boost if you use such a large cache partition.
Sent from my HTC Magic using XDA App

post not needed

and then when someone wants to flash a rom, (that is larger than the partition they got from flashing a rom that has this implanted) , they have to go here and learn to reconfigure, and then they scream cause they can't figure it out this is gonna be fun with time

capychimp said:
and then when someone wants to flash a rom, (that is larger than the partition they got from flashing a rom that has this implanted) , they have to go here and learn to reconfigure, and then they scream cause they can't figure it out this is gonna be fun with time
Click to expand...
Click to collapse
Not really....I'll be including a tool to change the partition size with my next update made for my rom...others can do it for theirs....or even less complicated is to use the same one as the one I'll include will leave system partition at 170MB and that is what SenseUI roms need...AOSP roms need way lower space on system, so there shouldn't be any conflict. IF someone wants to experiment with AOSP and letting the data partition have more space and less space on system, then they should use the manual method....in turn the person will know that it doesn't have enough system space for a senseui rom and will adjust it accordingly...or just flash the one I'm preparing now.

Its the same steps no matter if they are doing it the first or the 100th time... i think all it will do is help people...of they try to think a bit...
Sent from my HTC Magic using XDA App

so to implant it we have to change our update script to the binary one?

I recommend you read the original post for that info

lbcoder said:
Not quite.
The patch adds a BIND MOUNT of the cache partition to the data partition.
In other words, just because you set your cache partition to 2 MB does NOT mean that the filesystem at /cache is limited to 2 MB of storage! Because it is the same filesystem as /data, this actually makes your cache partition AS BIG AS your data partition.
Click to expand...
Click to collapse
Yes, I was wrong there and I saw that right after I wrote it, but I forgot to change my post...I was just thinking ahead. Thanks for correcting me

Thanks for the support lbcoder. I dont know much about the matter, and my only goal was the popularisation of the patch in this part of the forum.
Klothius can you please edit the post about the dalvik problem to eliminate possible confusion? Thanks
Sent from my HTC Magic using XDA App

eyegor said:
Thanks for the support lbcoder. I dont know much about the matter, and my only goal was the popularisation of the patch in this part of the forum.
Klothius can you please edit the post about the dalvik problem to eliminate possible confusion? Thanks
Sent from my HTC Magic using XDA App
Click to expand...
Click to collapse
I did

klothius said:
I did
Click to expand...
Click to collapse
Thank you

Awesome!
Code:
C:\Users\Sebi>adb shell df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 95.8M 0 95.8M 0% /dev
tmpfs 4.0M 0 4.0M 0% /sqlite_stmt_journals
/dev/block/mtdblock3 170.0M 148.6M 21.4M 87% /system
/dev/block/mtdblock5 290.8M 128.6M 162.2M 44% /data
/dev/block/mtdblock4 290.8M 128.6M 162.2M 44% /cache
/dev/block/mtdblock5 290.8M 128.6M 162.2M 44% /cache
/dev/block//vold/179:1 3.7G 3.4G 264.0M 93% /sdcard
(running CursorSense 1.2.6.1)
Now, a few questions:
1. How do I undo the patch? Is it enough to reflash my recovery, wipe everything from fastboot and restore the backup from before the patch?
2. I sometimes flash other ROMs, just to test them. Would there be a problem if I forgot to flash the boot patch after the ROM?
3. When I install an AOSP ROM and want to use the patch, what's the order? Do I change the TXT, flash the ROM and then the boot patch? Or do I need to wipe from fastboot when changing between Sense UI and AOSP?

[Q] Data2Loop - How to setup

Can any one explain me how to setup Data2Loop till TnT Lit 4.0.1. Bcz they remove data 2 loop and it's little bit slow. Other thing is settings and download customizations want keep after restart. Why? And also I need to know best partition structure of tab. What about ext4 and Swap partitions?

ndgayan said:
Can any one explain me how to setup Data2Loop till TnT Lit 4.0.1. Bcz they remove data 2 loop and it's little bit slow. Other thing is settings and download customizations want keep after restart. Why? And also I need to know best partition structure of tab. What about ext4 and Swap partitions?
Click to expand...
Click to collapse
hmmmm
data2loop
http://forum.xda-developers.com/showthread.php?t=902426
http://forum.xda-developers.com/showthread.php?t=906782
partition to 2048 data and 0 swap
and here is the ext4 thread
http://forum.xda-developers.com/showthread.php?t=893428

Moved to general

Those threads didn't give me more info.
thebadfrog said:
hmmmm
data2loop
http://forum.xda-developers.com/showthread.php?t=902426
http://forum.xda-developers.com/showthread.php?t=906782
partition to 2048 data and 0 swap
and here is the ext4 thread
http://forum.xda-developers.com/showthread.php?t=893428
Click to expand...
Click to collapse
Those are talking about technical details. Can u give me easy step by step instruction for that. Thanks.

ndgayan said:
Those are talking about technical details. Can u give me easy step by step instruction for that. Thanks.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=902426
Post #24 provides a flashable pack. Install through clockwork
There is no "easy" step by step method to ext4. rcgabriel is working on it and the last I heard he semi-bricked his tab. This best thing to do is follow the ext4 thread or one the kernel threads because that is where the solution will post

Getting update.zip with test key working on froyo

Hi guys, it just came to my mind that test-key signed update.zip files were working back in the eclair days, so i guess the problem is the new recovery in the froyo builds needing Samsung signed files. Same problem was present on the sgs when it moved to froyo, but the devs there managed to change back to old recovery to make them work again, would be nice if someone could find a similar solution for the sg3 also... for more info search for recovery 2e 3e howto in sgs dev section... i am very busy at the moment and go for vacation on Sunday so wont find time to look into this before beginning of March, but eventually someone else could do it and just needed the hint....

Ok, to give this a bump, i need someone with a eclair rom installed and a rooted system. What i need is two files: /sbin/recovery and /sbin/recovery.sh
I think if we swap those files in jpf or whatever Froyo version we could use update.zip files again...

FadeFx
I have JK1 but in sbin directory I have only recovery file, no signs of recovery.sh

sorry, my bad, recovery.sh is part of the modified clockwork mod recovery on sgs custom kernel. also i am in conversation with hardcore about this, and eventually wed have to change the file in initramfs of the kernel... but we will see. to bad i go on vacation tomorrow and will be away for 3 weeks (going to thailand, cant wait to be there...) so i wont have time to complete this, but i will gather info and eventually gsam101 could compile a zimage with old recovery...

Ok, here is my pm conversation with hardcore, seems it can be done easily with loosing new recovery, or the complicated way keeping new recovery for system calls (CSC changes and stuff) and loading old recovery when using 3 button combo. All this is done by recovery.sh
hardcore said:
No u replace /system/bin/recovery in the rom, not kernel.
For kernel if u want to reroute to another recovery u have to use some shell script logic. Check out the initramfs source of my kernel for recovery.sh.
ok, thanx... so we would have to change the file /system/bin/recovery in the zimage´s initramfs to exchange recovery, right?
can we also put the replacement recovery into /sbin to replace the original? and if how is it then called when actually entering recovery mode so we dont enter the old recovery?
thanx Gerd
The recovery executable that comes with the ROM is actually in /system/bin/recovery
Modified kernels like mine have another CWM recovery in the kernel which is in /sbin/recovery which is compiled into the kernel's read-only initramfs.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Content of recovery.sh:
(lagfix stuff is about sztupys lagfix for the sgs and can be ignored for g3 at the moment.
This replaces stock froyo recovery (3e) with clockwork recovery, but same procedure applies to old 2e recovery.
Code:
#!/sbin/busybox sh
/sbin/busybox cp /sbin/fat.format /system/bin/fat.format
# use default recovery from rom if we have an update to process, so things like CSC updates work
# Use CWM if we simply entered recovery mode by hand, to be able to use it's features
if /sbin/busybox [ -f "/cache/recovery/command" ];
then
# if we use the original recovery it might modify the filesystem, so we erase our config, in order to avoid regeneration
# of the filesystems. The drawback is that the lagfix has to be re-applied by hand
/sbin/busybox rm /system/etc/lagfix.conf
/sbin/busybox rm /system/etc/lagfix.conf.old
rm /sdcard
mkdir /sdcard
#/sbin/rec2e &
/system/bin/recovery &
else
# TODO: CWM is a bit more intelligent, but it might fail to
/sbin/recovery &
fi;
Hope someone can make use of this to get update.zip working again...

Nobody looked into this yet? This would make much things easier for us...
Bump

....
realy hope we get some good progress and development on this thread....
sry but im just a noob and flashing is all i do right now
but if i can give any help feel free to ask

Gonna check this out. If I get OCD about this, v1.2 will be delayed.
This could be really useful. For everyone.
Sent from my Lestatious v1.2 Galaxy 3 FROYO

Lestat, i think this is info enough, if not pm me with the questions and ill do my best to find out.

FadeFx said:
Lestat, i think this is info enough, if not pm me with the questions and ill do my best to find out.
Click to expand...
Click to collapse
Alright. Will do chief. Gonna bookmark this thread so I remember tomorrow.
Sent from my Lestatious v1.2 Galaxy 3 FROYO

I have the 2.1 recovery file. . If anyone interested i think i can post if xda allows. ..
Sent from my GT-I5800 using XDA App

I was going to respond, but you responded for me: I tried to make some change to the recovery, basically to make Clockworkmod Recovery work. It seems that in Samsung's phones, the recovery is stored in /system, which is a total nonsense. I managed to get CWN almost work, but it was really buggy.

Gsam101 said:
I was going to respond, but you responded for me: I tried to make some change to the recovery, basically to make Clockworkmod Recovery work. It seems that in Samsung's phones, the recovery is stored in /system, which is a total nonsense. I managed to get CWN almost work, but it was really buggy.
Click to expand...
Click to collapse
How buggy is it?
And i noticed that's where recovery was also. I was like, Hmm. Strange.

The Dark Lestat said:
How buggy is it?
And i noticed that's where recovery was also. I was like, Hmm. Strange.
Click to expand...
Click to collapse
Like i had to flash my phone back to make it work ^^

Did u use the sgs version of cwm or did u do an own port for the g3? I guess the sgs version wont run due to different bml layout

Gsam101 said:
I was going to respond, but you responded for me: I tried to make some change to the recovery, basically to make Clockworkmod Recovery work. It seems that in Samsung's phones, the recovery is stored in /system, which is a total nonsense. I managed to get CWN almost work, but it was really buggy.
Click to expand...
Click to collapse
Hi Gsam101
I interested in compile custom recovery too.
Can You please share build configs for apollo projects?

just wanted to bump this thread, since i think we should now have devs that should be capable of doing such stuff, update.zip support is normally a must have for any android device

is this helpful in any way? -> http://forum.xda-developers.com/showpost.php?p=12244509&postcount=159

No, not yet. Clockwork needs to be ported to our device to run, which i am not able to do. If u can port it i can eventually give some hints...

i have wrote to the developer of ROM Manager APP (Clockwork Recovery) asking him to support our phone. I wrote just because i saw
Don't see your phone? Email me if you want to help me get it working!
Click to expand...
Click to collapse
on his page (http://www.koushikdutta.com/2010/02/clockwork-recovery-image.html)
i'm not good at programming so i think if the developer replies and the answer will be yes then someone like FadeFx or anyone else who can help should contact [email protected] or [email protected]