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.
Related
PRE-REQUISITE:
1. Rooted your phone
2. You created the FAT32 / EXT2 combo partitions
NOTE:
I used Paragon partition Manager 10 ($40) for the easy way but you can do it a bit harder way for free on your phone itself without a PC by following http://forum.xda-developers.com/showthread.php?t=500387
I've heard Ubuntu also works although Paragon Manager is the only one i've tried
INSTRUCTION: These are the steps i used and it worked like a Cupcake lol
1. Download the LucidRem Modified Update Below to the MicroSD on the FAT32 portion (Assuming you've already created a Fat32 / Ext 2 partition on your microSD) and rename it "update"
JFv1.5 = http://files.lucidrem.us/_fd.php?file=jf/1.50/ADP1.5/REM/update.zip
OTA Radio if your phone doesn't already have this radio version (to check on your phone its under settings > About phone > Baseband version) = http://files.lucidrem.us/_fd.php?file=jf/1.50/ota-radio-2_22_19_26I.zip
2. Flash your G1 (At this point I performed a Clean Wipe right before flashing but its your choice)
3. After flashing and the phone boots up open the terminal app on the phone and type in the following commands:
su
Press Enter
lucid app
Press Enter
lucid data
Press Enter
lucid dalvik
Press Enter
4. Reboot your G1 and your done.
*In your storage settings your phone internal memory should be from 70-74 MB.The apps will automatically go to your SD when you DL them.
LucidREM please don't be mad that i linked your modified update.zip in my thread and Thank you.
you are truly a god !! easy to read instructions you should be a technical writer !!!
[
QUOTE=mailman1387;3743745]PRE-REQUISITE:
1. Rooted your phone
2. You created the FAT32 / EXT2 combo partitions
NOTE:
I used Paragon partition Manager 10 ($40) for the easy way but you can do it a bit harder way for free on your phone itself without a PC by following http://forum.xda-developers.com/showthread.php?t=500387
I've heard Ubuntu also works although Paragon Manager is the only one i've tried
INSTRUCTION: These are the steps i used and it worked like a Cupcake lol
1. Download the LucidRem Modified Update Below to the MicroSD on the FAT32 portion (Assuming you've already created a Fat32 / Ext 2 partition on your microSD) and rename it "update"
JFv1.5 = http://files.lucidrem.us/_fd.php?file=jf/1.50/ADP1.5/REM/update.zip
OTA Radio if your phone doesn't already have this radio version (to check on your phone its under settings > About phone > Baseband version) = http://files.lucidrem.us/_fd.php?file=jf/1.50/ota-radio-2_22_19_26I.zip
2. Flash your G1 (At this point I performed a Clean Wipe right before flashing but its your choice)
3. After flashing and the phone boots up open the terminal app on the phone and type in the following commands:
su
Press Enter
lucid app
Press Enter
lucid data
Press Enter
lucid dalvik
Press Enter
4. Reboot your G1 and your done.
*In your storage settings your phone internal memory should be from 70-74 MB.The apps will automatically go to your SD when you DL them.
LucidREM please don't be mad that i linked your modified update.zip in my thread and Thank you. [/QUOTE]
I'm glad you got it working man.
Good write up for others too. I used LucidREM's method to get apps on sd and it was the easiest and most understandable way for me too.
I started getting into the whole apps2sd phenomenon and this thread came just in time to keep me from getting frustrated. There are a few options out there but its nice having a noob walkthrough specifically for JFv1.5 to help guide the way.
Thanks i just wanna help..glad you got it
skri11a said:
I'm glad you got it working man.
Good write up for others too. I used LucidREM's method to get apps on sd and it was the easiest and most understandable way for me too.
Click to expand...
Click to collapse
Thanks and THANK YOU for the help you provided on the other post
brandenk said:
I started getting into the whole apps2sd phenomenon and this thread came just in time to keep me from getting frustrated. There are a few options out there but its nice having a noob walkthrough specifically for JFv1.5 to help guide the way.
Click to expand...
Click to collapse
Sure is nice to have b/c i dont understand computer language and codes unless its kindergarde step by step instructions.lol
I've never had any problems doing it the old way but this is 10000000x more convenient, good little guide. It's good someone has realised there are a lot of people who have no idea what they are doing when it comes to all the commands. Cheers
Great post man, yeah I set mine up already but for new users this will be a great guide and eliminate a lot of confusion. I saw your questions in the other thread and props for understanding so quick and making a guide. This site needs more of this kind of thing. Propz homie
mailman1387 said:
Sure is nice to have b/c i dont understand computer language and codes unless its kindergarde step by step instructions.lol
Click to expand...
Click to collapse
Lmao, good job man!
mailman1387 said:
LucidREM please don't be mad that i linked your modified update.zip in my thread and Thank you.
Click to expand...
Click to collapse
it's all good .. heheh .. i posted it so people could use it .. just keep spreading the word and good name of JesusFreke around the globe
mailman1387 said:
PRE-REQUISITE:
1. Rooted your phone
2. You created the FAT32 / EXT2 combo partitions
NOTE:
I used Paragon partition Manager 10 ($40) for the easy way but you can do it a bit harder way for free on your phone itself without a PC by following http://forum.xda-developers.com/showthread.php?t=500387
I've heard Ubuntu also works although Paragon Manager is the only one i've tried
INSTRUCTION: These are the steps i used and it worked like a Cupcake lol
1. Download the LucidRem Modified Update Below to the MicroSD on the FAT32 portion (Assuming you've already created a Fat32 / Ext 2 partition on your microSD) and rename it "update"
JFv1.5 = http://files.lucidrem.us/_fd.php?file=jf/1.50/ADP1.5/REM/update.zip
OTA Radio if your phone doesn't already have this radio version (to check on your phone its under settings > About phone > Baseband version) = http://files.lucidrem.us/_fd.php?file=jf/1.50/ota-radio-2_22_19_26I.zip
2. Flash your G1 (At this point I performed a Clean Wipe right before flashing but its your choice)
3. After flashing and the phone boots up open the terminal app on the phone and type in the following commands:
su
Press Enter
lucid app
Press Enter
lucid data
Press Enter
lucid dalvik
Press Enter
4. Reboot your G1 and your done.
*In your storage settings your phone internal memory should be from 70-74 MB.The apps will automatically go to your SD when you DL them.
LucidREM please don't be mad that i linked your modified update.zip in my thread and Thank you.
Click to expand...
Click to collapse
This seems pretty solid, will try when my card gets delivered. Did Lucid modify JF's update is that why I would have to re flash it?
LucidREM said:
it's all good .. heheh .. i posted it so people could use it .. just keep spreading the word and good name of JesusFreke around the globe
Click to expand...
Click to collapse
I cant wait till JF re-release the official cupcake for root T-Mobile officially announced it up on their USA site.Next thurs it starts.
xsnipuhx said:
This seems pretty solid, will try when my card gets delivered. Did Lucid modify JF's update is that why I would have to re flash it?
Click to expand...
Click to collapse
Yes that is correct.
Quick question. Now once we've flashed Lucid JFv1.5 would we be able to reflash a themed JFv1.5 with the lucid's app to sd for newbies mod there?
Two questions:
1. I already have JF1.5 installed on my G1. Can I just do an Alt+S in the bootloader to apply this update?
2. Can I just move the cache and the dalvik instead of moving all 3? I don't have many apps so that is not a concern, but I have heard that the caches will clear up a ton of memory on their own.
Thanks!
I've been wanting to do this and even downloaded the free Partition Manager program last week and with your help I moved my apps to SD card tonight!!!
YOU DA MAN!!!!! THANK YOU!!!!!!
Lucid already modded JFv1.5 ADP?
EDIT
Answered my own question
Ugh I hate being so undecided, I really want to try Lucid's 1.5 since I loved his Apps2SD on 1.42 (in the little time I had 1.5 I couldn't get Apps2SD to work AT ALL) but I just installed debian with lxde back on JF 1.42 and I don't want to have to redo all that if I screw up since I don't use nandroid.
work fine for me too!
thx thx thx thx!!!
djdeviance said:
Quick question. Now once we've flashed Lucid JFv1.5 would we be able to reflash a themed JFv1.5 with the lucid's app to sd for newbies mod there?
Click to expand...
Click to collapse
Im not sure because i don't use themes.Im also a newbie thats why i specified this post only use lucid modified rom.you can try it an then if it fails re wipe and do everything all over i.
Apps 2 Virtual Disk 0.53b
For those of you that are wondering "What is this guy smoking?" (which I assume is all of you), this is an automatically re-sizing virtual apps 2 SD ext3 partition. It is stored as an image file on your existing Fat32 partition.
I have done my best to make this as idiot proof and bug free as possible but I always appreciate constructive criticism. Please be kind, I haven't had access to a computer while writing this so it was written entirely on my G1. Therefore I expect that it will have a few bugs.
This barrows very heavily from Cyanogen's work so please thank him for making this possible.
Installing
To install the utility just download the file on your phone, open your terminal emulator and run:
Code:
su
sh /sdcard/download/a2vd-0.53b.zip
It does the rest.
Please note, this is NOT a zip file! It is a shell script. XDA won't let you post any file this big unless it's a zip file. (Can we get an Admin on this?) Good thing linux doesn't give a crap about file extensions.
Once you reboot your phone the utility will create the virtual partition, move over your apps, then re-size the partition to have 15 MB of free space. Please note, it will reboot 3 - 4 times during the first boot.
This should run on any rom that executes /system/bin/a2sd during boot.
It has been confirmed to work on Cyanogen 3.5.2 and higher.
Automatic Resizing
The partition will automatically re-size so you don't have to guess how big you need to make it. Now you can take a bite out of crime, in stead of your Fat32 partition. ;-)
If you run low on space just reboot your phone. If the free space on your virtual partition is less than 10 MB or more than 20 MB it will be re-sized to have 15 MB of free space. Please ignore the fact that free space may be listed as 13 or 14 MB, as far as I can tell this is an issue with the OS, the readout becomes more accurate as the partition gets bigger.
Disabling the Partition
If you wish to boot up with the Apps 2 Virtual Disk partition disabled simply open up your terminal emulator and run:
Code:
su
a2sdoff
You can also remove the SD card while the phone is off.
This is useful if you need to transfer files over USB cable.
Automatic backup
If you boot with the partition disabled the utility will backup some system settings so your apps and widgets will all still work when you re-enable the partition. It will also maintain a separate launcher profile for when you boot with the partition disabled. Now you don't have to stare at a desktop full of broken icons every time you need to transfer files to your computer.
Upgrading to a New Rom
Transitioning to a new rom can break some of your apps and widgets. To prevent this follow this procedure:
1. Place your new update.zip file on the root of your SD card.
2. Open terminal emulator and run:
Code:
su
a2sdoff -u
This will reboot your phone, prepare the backups, and take you to recovery.
3. Flash your new rom. (If you exit recovery without flashing you must re-run "a2sdoff -u" before attempting another flash)
4. Boot up your new rom, open terminal emulator and re-install Apps2VD.
Okay, you can start downloading now.
Thank you for your support and enjoy!
As a side note, If you install this on a phone that already has a traditional Apps2SD partition it will NOT copy over your apps. I'm working on it but until then you'll have to either just deal with it or copy them you self.
Edit: Download has been removed due to security concerns. Will re-upload when solved.
Sweet !....so basically it allows app2sd without an ext partition ? so just a fat32 partition is gud enough right ?
this is really intriguing, but i think i'm gonna hold off until some brave souls try it out with some feedback
Daneshm90 said:
Sweet !....so basically it allows app2sd without an ext partition ? so just a fat32 partition is gud enough right ?
Click to expand...
Click to collapse
Exactly! In fact, it requires nothing more than downloading and typing in one command.
narcopolypse said:
Exactly! In fact, it requires nothing more than downloading and typing in one command.
Click to expand...
Click to collapse
Aight im nandroid'd...n ready to test lol...will post results
So what is the plus side of using this? Is this just a tool for people who can't or don't have an ext partition? Do you know how it compares performance wise?
miketaylor00 said:
So what is the plus side of using this? Is this just a tool for people who can't or don't have an ext partition? Do you know how it compares performance wise?
Click to expand...
Click to collapse
Didnt work on xRom....kept bootloopin the first bootscreen
grandomegabosses said:
this is really intriguing, but i think i'm gonna hold off until some brave souls try it out with some feedback
Click to expand...
Click to collapse
I've been running this build for 4 day and previous alpha builds for over a month.
So have all of my friends.
miketaylor00 said:
So what is the plus side of using this? Is this just a tool for people who can't or don't have an ext partition? Do you know how it compares performance wise?
Click to expand...
Click to collapse
Performance is identical. The primary reason I built this is to have an automatically re-sizing apps partition. And the ability to boot disabled without breaking all of my widgets.
narcopolypse said:
I've been running this build for 4 day and previous alpha builds for over a month.
So have all of my friends.
Click to expand...
Click to collapse
hmmm i might try it later tonight or maybe tomorrow. after reading some more, i've gotten a little bit more confidence.
narcopolypse said:
Performance is identical. The primary reason I built this is to have an automatically re-sizing apps partition. And the ability to boot disabled without breaking all of my widgets.
Click to expand...
Click to collapse
It seems suprising to me that an image file on a FAT32 partition would perform the exact same way as an ext partition. I guess I will have to find out for myself
If this really does work and perform well, this could be google's solution to allow non rooted phones the ability to free up memory on their phone.
Either way, thanks for taking the time to do this.
Daneshm90 said:
Didnt work on xRom....kept bootloopin the first bootscreen
Click to expand...
Click to collapse
Yes, it will. And it would probably have a similar problem on later Cyanogen builds. You will have to modify the a2sd file to tell it not to automatically create apps2sd.
Daneshm90 said:
Didnt work on xRom....kept bootloopin the first bootscreen
Click to expand...
Click to collapse
It is supposed to reboot 3 - 4 times during the first boot.
this is really interesting, thank you for this. earlier today i made a modified a2sd script that makes the a2sd look for dev/block/mmcblk0p4 (fourth partition) and since there is none cyanogen's apps2sd will not be created. also in the file is a modified userinit.sh and user.conf that point to dev/block/mmcblk0p2 instead of 0p3 so that if you wanted to use this and only have a fat32 partition and linux-swap partition you could still get the benefits of it. saw this thread and thought this would be a place where these files could be used.
edit: was just thinking, does this overwrite the a2sd script? either way the modded userinit.sh and user.conf can still help.
david1171 said:
this is really interesting, thank you for this. earlier today i made a modified a2sd script that makes the a2sd look for dev/block/mmcblk0p4 (fourth partition) and since there is none cyanogen's apps2sd will not be created. also in the file is a modified userinit.sh and user.conf that point to dev/block/mmcblk0p2 instead of 0p3 so that if you wanted to use this and only have a fat32 partition and linux-swap partition you could still get the benefits of it. saw this thread and thought this would be a place where these files could be used.
edit: was just thinking, does this overwrite the a2sd script? either way the modded userinit.sh and user.conf can still help.
Click to expand...
Click to collapse
Yes this does replace /system/bin/a2sd and it stops checking for 0p2. It is based entirely off Cyanogen's a2sd that is used in every new rom out there and should be compatible with all of them.
Has anyone tested this yet? Which roms does it work on?
How does this work with mounting your phone on your computer? Like when you want to put music on. Can you do it the same way or do you have to shut your phone down and use a SDcard reader? Because I thought the was the main reason for not using fat32 for A2SD.
miketaylor00 said:
It seems suprising to me that an image file on a FAT32 partition would perform the exact same way as an ext partition. I guess I will have to find out for myself
If this really does work and perform well, this could be google's solution to allow non rooted phones the ability to free up memory on their phone.
Either way, thanks for taking the time to do this.
Click to expand...
Click to collapse
probably the wouldn't use it as you should be able to extract files from the img file
narcopolypse said:
It is supposed to reboot 3 - 4 times during the first boot.
Click to expand...
Click to collapse
Lol, no i tried again rebooted like 20 times so i gave up n nandroid'd.
speoples20 said:
How does this work with mounting your phone on your computer? Like when you want to put music on. Can you do it the same way or do you have to shut your phone down and use a SDcard reader? Because I thought the was the main reason for not using fat32 for A2SD.
Click to expand...
Click to collapse
That would be my concern as well. I don't see any way around this, though I'm not a dev by any means.
alritewhadeva said:
probably the wouldn't use it as you should be able to extract files from the img file
Click to expand...
Click to collapse
I'm sure they could make the img file only accesible by the sytem.
Introduction
If you are rooted and running a Hard SPL or a Stock SPL and really want to flash a ROM that claims to require Danger/Haykuro SPL, but you do not want to upgrade your SPL there are alternative ways to make these ROMs work on your phone without upgrading your SPL.
This is a very easy process, Ive done it with a few ROMs with no problems:
First off, keep in mind that on a Stock SPL
/system = about 67MB
Any ROM that has a system partition 67MB or Greater will require Danger/Haykuro SPL, UNLESS you can shrink that ROM's /system down below 67MB.
How do you do this, you ask?
------------------------------------------------------------------------------------------------------------------------------------------------------
Method #1 (Easy) -Move/Delete unneeded Apps, Sounds, Files
------------------------------------------------------------------------------------------------------------------------------------------------------
NOTE: This Method does NOT apply to HERO/SENSE ROMs, they are way too big! Check Method 2 if you want to fit ANY ROM on any SPL (Advanced)
Make sure you have 7-Zip! Dont have it? Google is your friend!
1) Read the first post and changelog of the ROM you wish to install on your phone. After youve made yourself familiar with what needs to be Wiped (ie: dalvik cache, ext, data) the Partition Layout the developer suggests (ie: FAT32/Ext3/Swap), then go ahead and download the ROM. Unzip it to a folder, name it something short. for example: C:\1\rom
now click on the system folder, scroll down and click on the media folder, and delete the audio folder. This will erase every sound effect and ringtone on your phone and usually will free up about 2MB in system.
To get your ringtones and sounds back download this (thanks Robot Teapot!) and unzip the folder to the root of your sdcard. (note: your ringtones might not show up the first time you boot the rom, in this case, reboot and theyll all be right there)
If removing your ringtones isnt enough to keep /system under 67MB then move on to step 2), if youre already below 67MB skip to step 3)
2) Return to the first post and changelog of the ROM you are trying to install. Look for apps the dev has added to the ROM that dont seem necessary for the ROM to function such as Twidroid.apk, Facebook.apk, NeroMedia.apk, WirelessTether.apk, WiredTether.apk, Maps.apk(takes up a lot of room, and sometimes outdated...just delete it and install the latest from the market!)etc.
You can use Android Barebones/Necessary Apps - CyanogenMod Wiki as a general guideline to determine which apps are essential to Android running properly and the functions of many system apps.
Delete those unnecessary apps or move them to your sdcard, and use ASTRO File Manager or a similar app to install them after you flash the ROM.
3) Okay, assume youve trimmed /system down below 67MB, good job! now you need to get those folders you extracted and the boot.img zipped up and signed. select the folders from the ROM you extracted and modified, the boot.img, right click, and select 7-Zip < Add to .zip
4) Download Stericson's Autosign place it in any directory and follow the instructions in the thread to sign your zip file.
5) Move the signed zip to your SD Card, making sure you have the proper partitions, wipe the necessary things, then flash your zip file and cross your fingers!
------------------------------------------------------------------------------------------------------------------------------------------------------
Method #2 (Advanced) -"Cache Hack"
------------------------------------------------------------------------------------------------------------------------------------------------------
NOTE: This Method will fit any ROM on any SPL but is more advanced than Method 1
lbcoder introduced the concept of moving files to the /cache partition of the phone and linking them back to /system or /data.
Firerat has come up with a way to make this concept work and explains the whole process in his thread and shows some examples of his method by providing some ports:
[HACK][ROM][BOOT.IMG][CACHE]-Stk SPL ROMs with Danger SPL size & extra 30mb! any SPL!
------------------------------------------------------------------------------------------------------------------------------------------------------
There you have it folks! Congrats if youve bypassed the Danger SPL requirements! Be sure to always keep a Nandroid/BART backup!!!!
Disclaimer: Not saying these methods will brick or damage your phone, but in the rare event this occurs I am NOT responsible for bricks or or any damages to your phone!
Autosign doesnt need to be in the SDK place, I had it in my music folder and it worked fine.I accidentally formatted my PC last night and dont have the SDK installed but autosign works for me so im happy.
Note to OP-You cant brick from flashing any 32B rom, you would only get a blank screen that stays..which some seem to call soft-brick, i call it nonsense though.
Thanks for this excellent tutorial
Ace42 said:
Autosign doesnt need to be in the SDK place, I had it in my music folder and it worked fine.I accidentally formatted my PC last night and dont have the SDK installed but autosign works for me so im happy.
Note to OP-You cant brick from flashing any 32B rom, you would only get a blank screen that stays..which some seem to call soft-brick, i call it nonsense though.
Click to expand...
Click to collapse
Really? I had no idea that the SDK wasnt required, ill remove that.
and yeah i know its usually a soft brick, if anything, and youre right its nonsense, and can be solved using a nandroid backup and wiping the proper things, but im playing it safe with that disclaimer just like the rom devs do lol
migalito said:
Thanks for this excellent tutorial
Click to expand...
Click to collapse
.
Youre welcome! I hope it works out for you!
Will this work with the Super D rom?
cg87 said:
Will this work with the Super D rom?
Click to expand...
Click to collapse
yes! I tried it on Super D!
speedysilwady said:
yes! I tried it on Super D!
Click to expand...
Click to collapse
Then I'm so confused. If it's possible, why does the rom still require the Danger SPL? Why didn't bbuchacher make it so it doesn't require the Danger SPL? Doesn't make any sense to me. Can someone please enlighten me?
cg87 said:
Then I'm so confused. If it's possible, why does the rom still require the Danger SPL? Why didn't bbuchacher make it so it doesn't require the Danger SPL? Doesn't make any sense to me. Can someone please enlighten me?
Click to expand...
Click to collapse
Well, to be honest, im not sure why, but im assuming some developers like to include features and apps that arent necessarily required for the rom to run properly but to make their rom more appealing to users, than other roms. keeping those apps in system prevents those apps from disappearing after you wipe your phone/ext. Plus devs always keep ringtones and sounds included in their roms for completeness's sake.
Now a Hero ROM on the other hand is loaded with system apps that cant be deleted and i dont think theyll ever fit on a Stock SPL, except maybe MicroHero, but im not sure.
But for whatever reason, a lot of regular ROMs are fat and bloated with apps and extras that dont necessarily have to be saved on the system partition,so the best thing to do is shrink those roms down till they fit, if you can't or dont want to upgrade your SPL.
How to make it work *WITHOUT TRIMMING*
Take a look at your update.zip archive.
Probably has 4 things in the root:
boot.img
system
META-INF
data
If system is greater than about 67MB (or lets say 60 just to be real safe...), then create ANOTHER directory and call it "cache".
Now MOVE /system/app into /cache/
You now have the space cleared up, but it still won't work.
So go into META-INF/com/google/android and edit the script "update-script".
just below the line where it says "format CACHE:", add these lines:
copy_dir PACKAGE:cache CACHE:
set_perm_recursive 0 0 0755 0644 CACHE:
symlink /cache/app SYSTEM:app
Wow, did we just move the extra crap into cache? Yep.
May require slight modification. Use your head.
Seems someone else is in the same boat as I am.
Can't update my radio, looks like some kind of hardware problem almost. Tried everything in any possible way.
So it looks like we're stuck with the standard or engineering SPL, which is fine but means there are some restrictions.
I'll try some of the tips you gave and flash something besides Cyanogenmod tonight.
lbcoder said:
Take a look at your update.zip archive.
Probably has 4 things in the root:
boot.img
system
META-INF
data
If system is greater than about 67MB (or lets say 60 just to be real safe...), then create ANOTHER directory and call it "cache".
Now MOVE /system/app into /cache/
You now have the space cleared up, but it still won't work.
So go into META-INF/com/google/android and edit the script "update-script".
just below the line where it says "format CACHE:", add these lines:
copy_dir PACKAGE:cache CACHE:
set_perm_recursive 0 0 0755 0644 CACHE:
symlink /cache/app SYSTEM:app
Wow, did we just move the extra crap into cache? Yep.
May require slight modification. Use your head.
Click to expand...
Click to collapse
I thought about that but I'm not 2 good @ programing unless its cars/video console. But doesn't the cache get used for something after the rom is up and running? Or is it only for ota updates?
If only for ota updates how come the danger spl doesn't give you 120mb or so since cache and system are 67mb each
That's a very good question. Just tried it and it seems to work, though. It's booting as we speak. All system/app files in the cache directory.
EDIT: Actually, all apps seem to force close on boot. So I'll just try it the regular way I guess.
try the Fix apk uid mismatches maybe idk ill try it in a lil bit
*update*
Got a boot loop on openeclair1.0.1 not sure why but dont got the time to fig. it out right now.
also why does a boot loop drain the crap out of your battery?
lbcoder said:
Take a look at your update.zip archive.
Probably has 4 things in the root:
boot.img
system
META-INF
data
If system is greater than about 67MB (or lets say 60 just to be real safe...), then create ANOTHER directory and call it "cache".
Now MOVE /system/app into /cache/
You now have the space cleared up, but it still won't work.
So go into META-INF/com/google/android and edit the script "update-script".
just below the line where it says "format CACHE:", add these lines:
copy_dir PACKAGE:cache CACHE:
set_perm_recursive 0 0 0755 0644 CACHE:
symlink /cache/app SYSTEM:app
Wow, did we just move the extra crap into cache? Yep.
May require slight modification. Use your head.
Click to expand...
Click to collapse
I remember you suggested this a while back when I asked about eclair roms on stock spl, I'm guessing if you use this method and wipe, you'll have to reflash the rom because those system apps are gone, correct?
yea anytime you wipe you would have to reflash the rom because a wipe deletes. data and cache folder
Dr-b said:
That's a very good question. Just tried it and it seems to work, though. It's booting as we speak. All system/app files in the cache directory.
EDIT: Actually, all apps seem to force close on boot. So I'll just try it the regular way I guess.
Click to expand...
Click to collapse
Might be a minor goofup on the permissions. Just verify the permissions and it will be fine.
What programming?
There is no programming involved in this.
Mainly cache is for OTA, but also some other crap related to the download manager.
As for the deathspl allocation, it puts *some* of the /cache into /system, *some* of the /cache into /data, and the balance of /cache remains in /cache.
xile6 said:
I thought about that but I'm not 2 good @ programing unless its cars/video console. But doesn't the cache get used for something after the rom is up and running? Or is it only for ota updates?
If only for ota updates how come the danger spl doesn't give you 120mb or so since cache and system are 67mb each
Click to expand...
Click to collapse
speedysilwady said:
I remember you suggested this a while back when I asked about eclair roms on stock spl, I'm guessing if you use this method and wipe, you'll have to reflash the rom because those system apps are gone, correct?
Click to expand...
Click to collapse
Why would you want to wipe it?
Note: you could just create an update.zip with an update-script that says ONLY "format DATA:" That would wipe the data withOUT wiping the /cache. Maybe name it "betterwipe.zip" and put it on your sdcard. Boot into recovery and apply "betterwipe.zip".
lbcoder said:
Why would you want to wipe it?
Note: you could just create an update.zip with an update-script that says ONLY "format DATA:" That would wipe the data withOUT wiping the /cache. Maybe name it "betterwipe.zip" and put it on your sdcard. Boot into recovery and apply "betterwipe.zip".
Click to expand...
Click to collapse
true, with fix permissions, and wipe dalvik, there really isnt much use in wiping data anymore, but would fix permissions still work if the apps are in cache? i know theyre syslinked, but im not sure how that works with the fix_permissions script. sorry if im asking dumb questions, im still learning.
Ill try your idea a really big rom and see if it works.
just wanted to confirm that all Hero ROMs seem to require Danger SPL, I see no way of shrinking system anywhere close to 67 or less.
But my method should still work on any eclair or donut rom. I still havent had a chance to try lbcoder's method though it should work. if people can get lbcoders method to work ill add it to the first post!
update (FIRERAT's implentation): http://forum.cyanogenmod.com/topic/2636-froyo-a2sdext/page__p__24386#entry24386
Ive seen this method around. And i was wondering....would it be possible to bypass the ADB steps for someone like me that doesnt have ADB access?
motoman234 said:
Ive seen this method around. And i was wondering....would it be possible to bypass the ADB steps for someone like me that doesnt have ADB access?
Click to expand...
Click to collapse
It's actually very easy:
Install Droid explorer (xda)
C:\Program Files\Droid Explorer\SDK\tools (Run... cmd)
I am trying this now...I will post back after installing some apps
EDIT= This is great and works a trea ...thanks dude
robuser007 said:
It's actually very easy:
Install Droid explorer (xda)
C:\Program Files\Droid Explorer\SDK\tools (Run... cmd)
Click to expand...
Click to collapse
Well thats my problem, my computer is super old and messed up. I cant get administrator access to downloads the proper files for adb. All i can do is download zip files to transfer for my phone lol.
motoman234 said:
Well thats my problem, my computer is super old and messed up. I cant get administrator access to downloads the proper files for adb. All i can do is download zip files to transfer for my phone lol.
Click to expand...
Click to collapse
Juts make another account and make it Admin. Then use the new account.
If your windows is that bad then I would either use a backup(if you did one) or a fresh install.
deuse said:
Juts make another account and make it Admin. Then use the new account.
If your windows is that bad then I would either use a backup(if you did one) or a fresh install.
Click to expand...
Click to collapse
Well to create a new account i would have to have admin access. Like a year or so ago this computer was givin to me for that reason lol. Theres a admin account on my computer but i cant get into it. Never could I wish there was a work around. Ive been messing with android for a long time and not once i have EVER used ADB lol. I would love to, theres so much stuff that i cant do because of this terrible computer.
motoman234 said:
Well to create a new account i would have to have admin access. Like a year or so ago this computer was givin to me for that reason lol. Theres a admin account on my computer but i cant get into it. Never could I wish there was a work around. Ive been messing with android for a long time and not once i have EVER used ADB lol. I would love to, theres so much stuff that i cant do because of this terrible computer.
Click to expand...
Click to collapse
Find yourself a copy of BartPE with Password Renew in it.
Burn, boot, use password renew to reset the password for any account.
I'm trying this, except when I get to "adb shell a2sd install" it says a2sd: not found.
:\
I had to go to /system/bin before i could run a2sd via ./a2sd, after which it worked.
What's the benefit of this over Froyo's SD implementation?
sleepwalkers said:
What's the benefit of this over Froyo's SD implementation?
Click to expand...
Click to collapse
it allows you to use the ext partition from previous versions of CM. Froyo's version now uses a fat32 partition on the sd card, therefore will not read the ext partition and the fact that your apps are on there.
sleepwalkers said:
What's the benefit of this over Froyo's SD implementation?
Click to expand...
Click to collapse
It's not as good, but coming from <= CM5 you may want to port along your apps.
Also Froyo's SD implementation is supported on an per app basis, but can be forced via CM. Note that dalvik cache is only moved to SD when using legacy a2sd.
sturmeh said:
It's not as good, but coming from <= CM5 you may want to port along your apps.
Also Froyo's SD implementation is supported on an per app basis, but can be forced via CM. Note that dalvik cache is only moved to SD when using legacy a2sd.
Click to expand...
Click to collapse
Not true.
See this thread for a more detailed discussion about the pros and cons between froyo2sd and app2sd.
http://forum.cyanogenmod.com/topic/2018-apps2sd-brainstorming/
I will have a try , Thanks..
LIKEHELL said:
I will have a try , Thanks..
Click to expand...
Click to collapse
froyo implementation isn't as good as apps2ext. The froyo method uses the fat32 partition but only if the dev of the app allows it to be moved to the sdcard. plus the apps don't all load on boot because the phone has to mount (prepare)the fat32 partition of the sdcard. This is the reason that many apps are not launching at boot like SetCpu and other root access apps, because the system boots before the sdcard is prepared. This is also the reason why many widgets and apps are missing from the app drawer for a lot of people as well. Cyanogenmod really needs to look at this and think about changing back to the old cm5 way of doing things.
I am trying to find a good backup app as doing a Nandroid did not work for me with doing aps2sd this way.
OMG
honestly , do you really need to add 5.1mb of crap to /system to get what should be a simple script running?
and what is /data/a2sd/Vending.apk for?
Awful, just awful
Code:
$ find
./a2sd-2.7-update3r1-signed.zip
./system
./system/lib
./system/lib/libext2_e2p.so
./system/lib/libext2_profile.so
./system/lib/libext2_com_err.so
./system/lib/libext2fs.so
./system/lib/libext2_blkid.so
./system/lib/libext2_uuid.so
./system/bin
./system/bin/fixa2sd
./system/bin/setupa2sd
./system/bin/apps2sd
./system/bin/boota2sd
./system/bin/chka2sd
./system/bin/reboot.a2sd
./system/bin/e2fsck_recvy
./system/bin/e2fsck
./system/bin/zipalign
./system/bin/aligna2sd
./system/bin/launcha2sd
./system/bin/bash
./system/bin/a2sd
./system/bin/starta2sd
./system/bin/busybox.a2sd
./system/etc
./system/etc/init.d
./system/etc/init.d/04apps2sd
./system/etc/init.d/00a2sdreset
./system/xbin
./system/xbin/apps2sd
./system/xbin/e2fsck
./system/xbin/a2sd
./data
./data/a2sd
./data/a2sd/Vending.apk
Firerat said:
OMG
honestly , do you really need to add 5.1mb of crap to /system to get what should be a simple script running?
and what is /data/a2sd/Vending.apk for?
Click to expand...
Click to collapse
Could you possibly implement something for this purpose and add your "all in one" script? Please
zimphishmonger said:
Could you possibly implement something for this purpose and add your "all in one" script? Please
Click to expand...
Click to collapse
seems I must, even if its not really needed
should have something soon
Firerat said:
seems I must, even if its not really needed
should have something soon
Click to expand...
Click to collapse
Thanks man!
Thanks to the nice people in the legend section
we have a pseudo s-off
NEED EXT3 PARTITION!!!!
using my kernel and another update .zip
NEED PEOPLE TO TEST!
Try with metamorph other apps that use s-off
KERNEL
http://www.mediafire.com/?k4061yiil9zoqv0
UPDATE.ZIP WITH INIT.D SCIPTS & AUFS.KO
http://www.mediafire.com/?d66q953fdgd5nzj
Run adb shell aufs --enable then reboot
terminal should also work: su aufs --enable
see http://forum.xda-developers.com/showthread.php?t=773278
drowningchild said:
Thanks to the nice people in the legend section
we have a pseudo s-off
NEED EXT3 PARTITION!!!!
Click to expand...
Click to collapse
Have you tested this with S2E apps2sd application?
What does this do
Sent from my Liberty
andrew.cambridge said:
What does this do
Sent from my Liberty
Click to expand...
Click to collapse
if you are asking this you shouldnt be trying it
bkmo said:
Have you tested this with S2E apps2sd application?
Click to expand...
Click to collapse
As taken from the thread in legend dev.
Shell script that does the overlay is made so it can use any (first) ext2/3 partition on your sdcard. That means you can use your a2sd partition for overlay too. If a2sd is not active but you still have ext2/3 partition on your sdcard, it will be mounted and used for overlay. If you don't have ext2/3 partition on your sdcard, then internal data partition will be used instead. In this case you will have to be careful not to fill it up entirely
a2sd script should run before the overlay script (only if you use a2sd)
i dont know how s2e works i only use built in apps2sd
as long as you have enough free ext3(no ext4) it should work it only uses what youve edited
eg u morph framework.res it only overlays that file
I didn't try it, I was just asking.
Sent from my Liberty
Read/Write instead of Read/Only
a pseudo S-off as the aria is S-on
read the thread linked for further explanation
S-OFF means that the NAND portion of the device is unlocked and can be written to. The default setting for HTC’s devices is S-ON, which means that neither can you access certain areas of the system nor can you guarantee a permanent root.
sorry...you beat me to it. :0
this is the closest we'll get to s-off unless it actually happens
its a fake s-off that has system files that youve edited load from the sd ext3 partition
updated 1st post as i forgot commands you NEED to run
haven't test it yet. Theoretically this can do pseudo modification of system files, but what will happen when I delete a system file? pseudo deleted, or restore to the original?
ladios said:
haven't test it yet. Theoretically this can do pseudo modification of system files, but what will happen when I delete a system file? pseudo deleted, or restore to the original?
Click to expand...
Click to collapse
tested with metamorph and it just reverts to whatever is on internal
and it works with s2e fine, just make sure you have a big enough partition
drowningchild said:
Thanks to the nice people in the legend section
we have a pseudo s-off
Click to expand...
Click to collapse
This is great! I'm not sure I need it at this point but I might give it a try tomorrow just to see what happens. Thanks, man.
I know what this does but could you jog my memory on what an ext3 partition is? Partitioning your SD card?
Signatures are fancy.
Moh_Jay said:
I know what this does but could you jog my memory on what an ext3 partition is? Partitioning your SD card?
Signatures are fancy.
Click to expand...
Click to collapse
yes, you CAN resize the partitions usung for example gparted(from pc) as i use, instead of formatting it
Okay so is there a certain set of instructions I need to follow when formatting? And all I have to do is 1. have a formatted SD card and your kernel 2. Flash update.zip 3. Put phone into adb and do adb shell aufs --enable on the command prompt?
Signatures are fancy.
not really
yes you should be able to do aufs --enable on the terminal emulator on your phone
you need the newest version of my kernel as it adds support for aufs
Okay thank you will try tomorrow
Signatures are fancy.
Sweet
Sent from my Liberty using XDA App
What's keeping the Aria from getting a full S-Off like some other phones I've seen? HTC's security pretty tough?
SectorNine50 said:
What's keeping the Aria from getting a full S-Off like some other phones I've seen? HTC's security pretty tough?
Click to expand...
Click to collapse
It was done long ago. ATTN1 has had S-OFF on his phone for a while. Check out alpharev.nl . They just have yet to release it for some reason.