THIS WILL NO LONGER BE MAINTAINED and is officially killed
go here if you want rw access and get the version without a kernel.(assuming you have a kernel installed that has aufs support)
IF YOU FLASHED THE UPDATE.ZIP THAT WAS ON THIS PAGE...PLEASE DO THE FOLLOWING:
You need to remove the init script and static busybox that were installed on your device. You have to do this in recovery mode since your rw access is not real.
Download the version linked to above and place it at the root of your sdcard.
open rom manager
select boot to recovery
boot to recovery while plugged in to computer
then from computer:
Code:
adb shell
mount /system
mount /data
rm /system/etc/init.d/99sysrw
rm /data/bin/busybox
umount /system
umount /data
exit
and from the phone:
flash BlaY0's update.zip you put on the sdcard
Really cool for your contributions.
I have no clue what you said, though. Will I be able to uninstall system apps with this? I'm guessin not as you were mostly speaking of partitions.
Lemme guess, brings ext2/3 etc together for something?
wow, best news that I have heard all day.
Ah! Thank you so much. I was just asking about this a couple weeks ago.
Sent from my T-Mobile myTouch 3G Slide using XDA App
does this mean that we can use metamorph now?
sorry if its a stupid question
Hayzie said:
Really cool for your contributions.
I have no clue what you said, though. Will I be able to uninstall system apps with this? I'm guessin not as you were mostly speaking of partitions.
Lemme guess, brings ext2/3 etc together for something?
Click to expand...
Click to collapse
No, You will not be able to uninstall apps with this (at least I don't think). It doesn't actually let you write to the /system partition, it just creates an overlay.
And No it does not even look for an ext partition, it just uses the data partition.
rodriguez27 said:
does this mean that we can use metamorph now?
sorry if its a stupid question
Click to expand...
Click to collapse
Don't really know, I haven't tried. Bear in mind however since it is on your data partition, space could be an issue. Any files changed would then be stored in /data/sysrw.
thanks for the quick info
I'm gonna try this out with Android Commander. With this I should be able to remove apps and delete files without restarting into recovery and mounting everything. Right?
dumfuq said:
No, You will not be able to uninstall apps with this (at least I don't think). It doesn't actually let you write to the /system partition, it just creates an overlay.
Click to expand...
Click to collapse
apparently I was wrong.
as a test I did...
Code:
rm system/app/com.amazon.mp3.apk
while the phone was booted and it worked!
Even after a reboot I do not have com.amazon.mp3.apk installed
It worked for me too, I used android commander booted and running and removed out of /system/apps android.tether.apk, mytouchmusic-signed.apk, and twitter.apk. I had a force close when I removed one thing (I am sure it was running in the background)
They all were gone after a reboot too, I was also able to update adfree just fine.
Any way this can be built into roms?
Thanks for the hard work!
dumfuq said:
No, You will not be able to uninstall apps with this (at least I don't think). It doesn't actually let you write to the /system partition, it just creates an overlay.
And No it does not even look for an ext partition, it just uses the data partition.
Don't really know, I haven't tried. Bear in mind however since it is on your data partition, space could be an issue. Any files changed would then be stored in /data/sysrw.
Click to expand...
Click to collapse
Hey dumfuq, thanks for this! Great idea on porting this badboy! One question though... from what I understood from the source thread is that will use the EXT. Partition for data if you have it right? So it won't break a2sd? I think I understood that correctly. Plus you need your kernel and that should make it work on any rom. I assume it won't overwite the OC kernel either. I'm excited to try this one out but I'm in the middle of rebuilding my rom so I can make a new backup (my old corrupted finally). I will test out as much as I can and let you know if different roms work. I should be done reinstalling by tomorrow (i have like 200 apps, lol!). This might turn out to be a good way to skip nandroiding and wiping all together if it turns out to work properly with a2sd/a2fat32... don't ya think?
sino8r said:
Hey dumfuq, thanks for this! Great idea on porting this badboy! One question though... from what I understood from the source thread is that will use the EXT. Partition for data if you have it right? So it won't break a2sd? I think I understood that correctly. Plus you need your kernel and that should make it work on any rom. I assume it won't overwite the OC kernel either. I'm excited to try this one out but I'm in the middle of rebuilding my rom so I can make a new backup (my old corrupted finally). I will test out as much as I can and let you know if different roms work. I should be done reinstalling by tomorrow (i have like 200 apps, lol!). This might turn out to be a good way to skip nandroiding and wiping all together if it turns out to work properly with a2sd/a2fat32... don't ya think?
Click to expand...
Click to collapse
This version is not the same as blayo's for the legend. It is closer to the desire one (although I used info from both).
Mine will not even try to detect an ext partition at this point, it just uses the data partition regardless of what is available.
Also nothing at all will get overwritten with this unless you happen to have an /system/etc/init.d/99sysrw file. It doesn't copy the kernel or modules, instead it just assumes you have a supported version . The only thing this update.zip does is add the script into init.d.
dumfuq said:
This version is not the same as blayo's for the legend. It is closer to the desire one (although I used info from both).
Mine will not even try to detect an ext partition at this point, it just uses the data partition regardless of what is available.
Also nothing at all will get overwritten with this unless you happen to have an /system/etc/init.d/99sysrw file. It doesn't copy the kernel or modules, instead it just assumes you have a supported version . The only thing this update.zip does is add the script into init.d.
Click to expand...
Click to collapse
I see... so basically, only cm based roms will work. Well, eventually, most us will move to cm based roms once bluetooth and a few minor bugs are worked out. Well, thanks for the info!
sino8r said:
I see... so basically, only cm based roms will work. Well, eventually, most us will move to cm based roms once bluetooth and a few minor bugs are worked out. Well, thanks for the info!
Click to expand...
Click to collapse
I haven't used them, but I think the newer sense roms support init.d scripts so you should be all good.
Working great on Fenix 2.0 with one of dumfuqs OC kernals...thank you much for this.
V2 is posted. It is essentially BlaY0's script for legend. I've only tested with no ext partition, but hopefully if you have one it will use it to store sysrw.
dumfuq said:
V2 is posted. It is essentially BlaY0's script for legend. I've only tested with no ext partition, but hopefully if you have one it will use it to store sysrw.
Click to expand...
Click to collapse
just so you guys now, v2 probably doesn't work for people with who want it on the ext. Blay0 fixed his though (to support non ext users), so I'll give it a look here soon.
Both versions do not work on stock kernel. Am I missing something? Should I use dumfuq kernel or cyanogenmod kernel in order to use this?
Sent from my T-Mobile myTouch 3G Slide using Tapatalk
WHAT!!?? My slide has finally lost it's parasite, com.amazon.mp3 you are toast now. You and your friends kickback, talkback, soundback, twitter... not sure what else I erased, oh genie widget. Thanks dumfuq!! You are the man
Everyone that does this, make sure to check cyanogen's wiki on making a barebones rom so you don't delete something you actually need (of course you did make a nandroid before doing this so no need to worry if you do).
You won't actually delete anything... overlay just makes you (and system) think it is deleted.
Related
ATTENTION: Cyanogenmod version 6.1.0 has A2EXT support built into the rom so an edited boot.img is no longer needed just flash the add-on to enable it and also you must do the commands to move dalvik-cache to the EXT partition as well...
Thank You for reading this if you actually took the time to!
Ok so i decided to post some things on here. Let me explain why I did things the way I did first of all. I decided to only edit the boot.img in each of the froyo roms that we all use and post those here along with a flashable .zip file that allows you to activate apps2ext on froyo roms. I did it this way to show respect to the developers of the roms by not stealing there downloads with my own. Doing it this way means that you have to download the actual rom from them which I hope makes things better for them.
You will need to already have an EXT partition setup already to be able to do this.
To any Dev if you do not like me doing this to your rom then by all means PM me and i will remove it ASAP.
To any downloader/user if there is a rom that you want me to include that isn't or a rom that isn't Froyo let me know and i will try to get that for you ASAP.
Credit for this goes to the Dev's of each rom and the darktremor a2sd method maker:
Cyanogen and teamdouche
Tkirton
Arayray
r0man
infinitybiff
migueltherocker
XDA of course!! :-D
Everyone that uses my edits
If i didn't mention you then PM me i will add you.
Now on to the Goods:
All of these are just boot.img from each rom. This is not an one for all boot.img type thing because each rom could have done something to the boot.img that may cause a bootloop if added to a different rom.
Rename each to boot.img and place into your rom.
After that you don't actually have to do any resigning since we all are using clockwork recovery just make sure its setup to allow flashing without signatures.
This only supports EXT2 or EXT3 which is pretty much all slide users have considering its nothing new.
Download the a2sd.zip and flash it at any time after you get your base rom flashed.
I will try to keep these updated to the latest versions if there is enough demand for them. Also i will try to keep the latest 3 nightlies up-to-date.
Boot.imgs:
Boot Images Here
A2sd Enabling package
Instructions:
OK as stated above these are only boot.img.
You need to rename each to just boot.img and place them inside the rom you like.
Make sure you wipe everything and do a fresh install it helps a lot to do everything fresh. (if your worried about apps use titanium backup or some other backup app)
Flash the a2sd add-on
Once the add-on has been flashed and there aren't any problems there are a few ways to enable actual a2ext.
You can either use adb or a terminal app on your phone.
If using adb phone can be turned on or in recover with system mounted.
once you pick a way here are the commands:
(if using a terminal app skip steps 1, 2, 5, 6)
1. ./adb remount (windows: adb remount)
2. ./adb shell (windows: adb shell)
Su will be needed for terminal app and may be needed for adb method(just do it in case its needed)
3. cd /system/bin/
4. sh a2sd reinstall
some things will popup and phone should reboot
5. once rebooted ./adb remount
6. ./adb shell
7. cd /system/bin/
8. sh a2sd cachesd
more things will popup and phone should reboot. The last reboot can take 5 minutes or longer especially if you already had apps downloaded. I know on a fresh install it can take what seems like ages.
saved just in case may use this for non froyo roms or requested roms
Through some experimenting i have found out that just including the boot images into the roms without flashing the add-on pack could cause your phone to stick at the boot screen so you should always flash the add-on
Teamfenix 1.7.1 for those people that use it because they need tether support
The best backup app i have found is mybackup pro and activate the root privileges. if you dont have paid apps or just dont wanna pay it there is a free version but it only lasts a certain amount of time. it restores all apps and data without causing market problems like i have experienced with titanium backup. either/or they are both good apps but everyone has a preference.
This is great man, thanks. You saved me the time and trouble of incorporating it myself.
Sent from my T-Mobile myTouch 3G Slide using XDA App
migueltherocker said:
This is great man, thanks. You saved me the time and trouble of incorporating it myself.
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
lol thanks i just noticed a lot of people want it so i figured this way is easier although i could upload each individual rom with it already enabled and ready to run but i thought that might step on a few toes around here
great work! ill add a link to my post if you dont mind
arayray said:
great work! ill add a link to my post if you dont mind
Click to expand...
Click to collapse
thats ok with me
cool mod, gonna give ita shot!
SiL3nTKiLL said:
cool mod, gonna give ita shot!
Click to expand...
Click to collapse
let me know how it works out for you. also updated first post with the 2 9/26 nightlies and 2nd post with the teamfenix 1.7.1 boot image
just to be clear, we need to have the ext partition setup before trying this right? it won't make it for us?
I didn't think so... just wondering hahaha
Thanks guys!
you rock!
- faylix / local
Just wondering... what's the difference b/w app2ext and app2fat? It seems like app2ext is better since people tend to want it
And also, if we want to partition app2ext, we can just do so via rom manager, right?
daniel60104 said:
Just wondering... what's the difference b/w app2ext and app2fat? It seems like app2ext is better since people tend to want it
And also, if we want to partition app2ext, we can just do so via rom manager, right?
Click to expand...
Click to collapse
the benefits of a2ext are that you dont have to move each app as you install them. once its setup they are automatically installed to the ext partition. another thing is it doesn't matter what apps are on it they all show up without any problems unlike with the a2fat where if widgets or home apps are placed on it they disappear. also when rebooting your phone your home screen apps wont get that generic icon with a2ext like they can with a2fat. its a lot easier to partition the sdcard compared to the old android days when everything was manual so its a whole lot more appealing. plus even with a2fat your internal memory continued to decrease even if you placed them on the memory card. this is because only part of the app is moved over and also the dalvik cache for the app was left on internal. so you are still limited on how much you can download. with a2ext no internal memory is lost to apps or dalvik cache because everything is on the ext partition this would allow rom makers to add more to the data or system partitions with there rom so you can have other apps or more room for themed images that may take up more memory.
your other question yes rom manager should have the option to partition your sdcard. another option is to use gparted if you are running ubuntu there are also other programs that should work as well for other os.
on another note working on the latest nightly and will upload shortly
A question I have is that if we use the boot image for the newest Cyan nightly? What happens when we want to install a newer nightly? Do we have to patch that with the new Boot.img also?
acejoker25000 said:
once you pick a way here are the commands:
(if using a terminal app skip steps 1, 2, 5, 6)
1. ./adb remount (windows: adb remount)
2. ./adb shell (windows: adb shell)
Su will be needed for terminal app and may be needed for adb method(just do it in case its needed)
3. cd /system/bin/
4. sh a2sd reinstall
some things will popup and phone should reboot
5. once rebooted ./adb remount
6. ./adb shell
7. cd /system/bin/
8. sh a2sd cahcesd
more things will popup and phone should reboot. The last reboot can take 5 minutes or longer especially if you already had apps downloaded. I know on a fresh install it can take what seems like ages.
Click to expand...
Click to collapse
The last command (#8) should be
Code:
sh a2sd cachesd
you transposed a couple letters in cachesd.
Ok I had a 2.1 ROM with a2sd enabled and i had my ext2 partition working. I installed a 2.2 ROM and followed all directions properly. After the 2nd reboot I am not seeing my apps populate into the phone. They should still be on the ext2 partition no? Thoughts please?
If you wiped before flashing then your ext partition was wiped as well but you could try a fix permissions and see if that works
Sent from my T-Mobile myTouch 3G Slide using XDA App
acejoker25000 said:
If you wiped before flashing then your ext partition was wiped as well but you could try a fix permissions and see if that works
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
Ah crap I did do a full wipe. Trying the fix permissions now. I do have a nandroid backup of my last ROM. If this doesnt work is there a way to put that ext2 contents onto the ext2 now?
Restore the rom and use titanium backup or mybackup and backup your apps that way but I think if you pick advanced under the nandroid options you can restore only the ext partition. I never did that but a fix permissions might help with any problems
Sent from my T-Mobile myTouch 3G Slide using XDA App
acejoker25000 said:
Restore the rom and use titanium backup or mybackup and backup your apps that way but I think if you pick advanced under the nandroid options you can restore only the ext partition. I never did that but a fix permissions might help with any problems
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
Fix Permissions and a reboot didn't make the apps show up. Doing advanced nandroid restore now and only restoring the sd-ext. Will post results in a few. Thanks!
pettigrew95 said:
Fix Permissions and a reboot didn't make the apps show up. Doing advanced nandroid restore now and only restoring the sd-ext. Will post results in a few. Thanks!
Click to expand...
Click to collapse
I meant a fix permissions after an advanced restore otherwise there could be problems
Sent from my T-Mobile myTouch 3G Slide using XDA App
acejoker25000 said:
I meant a fix permissions after an advanced restore otherwise there could be problems
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
Hmm sitting at the white t-mo boot screen for quite some time now...but i remember your 1st post saying this was normal with apps on the ext2
Warning: whether you preform these steps correctly or incorrectly, you may be left with a device which cannot be recovered to a previous state. Because this process operates on the recovery partition it leaves you with little room to recover if flashed incorrectly, especially if your normal Android mode doesn't boot.
(although realistically you can just flash ESPRIMG.zip from HBOOT to recover, or fastboot)
So here it is ladies and gentlemen: Clockwork 3.0.0.5, based on a git version pulled/compiled on January 6th, 2011 from the CyanogenMod 7.x (CM7) repository. So what's new? Nothing that I can tell! Not sure why it deserves version 3.x, but I guess changing the text color and background is considered a 'major upgrade'.
This is provided in .img format - NOT an update.zip format. That means you'll have to flash it to your recovery partition using flash_image. Obviously that means you first need root AND S-OFF. No, I won't tell you how to root your phone or what S-OFF is.
Instructions:
Code:
$ su
# flash_image recovery recovery-cw3-test1.img
'flash_image' isn't included intentionally - if you're smart enough to know how to flash this properly and understand the risks, then you might be smart enough to know where to get 'flash_image'.
How'd I do it? Top Secret - I'd have to kill you if I told you.
Download link: [REMOVED - use one from CM7]http://dl.dropbox.com/u/14943973/recovery-cw3-test1.img
Need to revert back to 2.5.0.1? Flash this: http://koush.tandtgaming.com/recoveries/recovery-clockwork-2.5.0.1-espresso.img
Enjoy it? Thank me!
Is it possible to get it in an update.zip format ? I don't want to mess with s-off for now.
SKAm69 said:
Is it possible to get it in an update.zip format ? I don't want to mess with s-off for now.
Click to expand...
Click to collapse
Not from me, sorry. I don't see any point in supporting the legacy method, especially when this version of CW doesn't give any readily-apparent advantages to the older one.
Nice find. I actually have S-OFF but when I start this recovery it is telling me error mounting system, data and others. Is this normal or is something wrong with my setup?
JAWheat411 said:
Nice find. I actually have S-OFF but when I start this recovery it is telling me error mounting system, data and others. Is this normal or is something wrong with my setup?
Click to expand...
Click to collapse
It IS a test build. I'm about to flash it now, I'll let you know if it's just you or not
And FLASH_IMAGE is indeed included, at least its built into cm6.
Edit: it isn't just you, the recovery is practically nonfunctional haha. There are errors all over when you boot into it, mount usb storage crashes it, and it can't mount anything, including the sd card, so its virtually pointless to flash at this point
MusicMan374 said:
It IS a test build. I'm about to flash it now, I'll let you know if it's just you or not
And FLASH_IMAGE is indeed included, at least its built into cm6.
Edit: it isn't just you, the recovery is practically nonfunctional haha. There are errors all over when you boot into it, mount usb storage crashes it, and it can't mount anything, including the sd card, so its virtually pointless to flash. Might even be as bad as arayrays gingerbread port, that hardly works either
Click to expand...
Click to collapse
But the only new features you see would be the new color?
Ace42 said:
But the only new features you see would be the new color?
Click to expand...
Click to collapse
Pretty much yeah. It was orange instead of green. Some of the menus had different names, easier to understand for noobs, but they had the same content. But don't flash it until it's more functional.
Sent from my T-Mobile myTouch 3G Slide
Ok well can someone post an older Clockwork recovery.img so we can reflash it? We can't use this one to do anything.
MusicMan374 said:
It IS a test build.
Edit: it isn't just you, the recovery is practically nonfunctional haha. There are errors all over when you boot into it, mount usb storage crashes it, and it can't mount anything, including the sd card, so its virtually pointless to flash. Might even be as bad as arayrays gingerbread port, that hardly works either
Click to expand...
Click to collapse
I was at work when I uploaded the image and because of that I only briefly tested it. The errors at the beginning aren't critical, but I'll look into the overall functionality being broken, at some point tonight.
Hence this being a "TEST".
Thanks
I appreciate that. I like beta testing new things. It does seem to have a few more functions. I just couldn't revert back.....
Sent from my T-Mobile myTouch 3G Slide using XDA App
Flash this to go back to 2.5.0.1: http://koush.tandtgaming.com/recoveries/recovery-clockwork-2.5.0.1-espresso.img
Actually.. i see a new option to partition SD card straight from the recovery menu... this is a very useful feature... and i think thats why it deserves that build jump from 2.5 to 3.0..... but at this point... it is in an UNUSABLE state.. i understand it is a test build... but i cannot test anything because it crashes on every single option you can possibly choose... will go back to 2.5 and wait for a stable, or at least more functional test build... hope to see some improvements soon... I do not doubt that you guys can have this thing up and running in no timee.. its a good starting point.. Keep the work going... looking forward to it...
was anyone else hoping for a terminal like in good ol' amon_ra? I was...
Be nice to have it in update.zip form for the ones without s_off
Sent from my T-Mobile myTouch 3G Slide using XDA App
elry567 said:
Be nice to have it in update.zip form for the ones without s_off
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
S-off really is a must have. I attached the working build of 3.0.0.5, you have to either use flash_image with it, or fastboot flash, both of which require s-off.
Thnx
Sent from my T-Mobile myTouch 3G Slide using XDA App
mymomma8 said:
it crashes on every single option you can possibly choose
Click to expand...
Click to collapse
Sounds like youre doing it wrong. You can no longer use the power button to select options but rather the trackball
Sent from my T-Mobile myTouch 3G Slide using XDA App
I don't think that file was cw3 I flashed it and still have 2.5 (file by musicman)
Sent from my T-Mobile myTouch 3G Slide using Tapatalk
MusicMan374 said:
S-off really is a must have. I attached the working build of 3.0.0.5, you have to either use flash_image with it, or fastboot flash, both of which require s-off.
Click to expand...
Click to collapse
I flashed it... it seems to be CW 2.5.... not CW 3.0 :/
guitarist5122 said:
Sounds like youre doing it wrong. You can no longer use the power button to select options but rather the trackball
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
No, i select the options with the trackpad... the problem is a bunch of recovery/cache errorss... that i cannot seem to fix, i tried wiping recovery/cache... and problem still persistess
EDIT: FOUND A TRULLY WORKING BUILD Thanks to whoareyou and can be downloaded from
http://forum.xda-developers.com/attachment.php?attachmentid=490785&d=1295154563
No crashes, everything works... sucessfully partitioned SD card. Will create a guide on how to partition SD card using this recovery.
mymomma8 said:
I flashed it... it seems to be CW 2.5.... not CW 3.0 :/
No, i select the options with the trackpad... the problem is a bunch of recovery/cache errorss... that i cannot seem to fix, i tried wiping recovery/cache... and problem still persistess
EDIT: FOUND A TRULLY WORKING BUILD Thanks to whoareyou and can be downloaded from
http://forum.xda-developers.com/attachment.php?attachmentid=490785&d=1295154563
No crashes, everything works... sucessfully partitioned SD card. Will create a guide on how to partition SD card using this recovery.
Click to expand...
Click to collapse
Alright thanks it works now!
Hey this is gonna sound dumb but can we use hd2 cwm builds
sent by DAN SWAGGER via tapatalk/simple mobile
dswaggz said:
Hey this is gonna sound dumb but can we use hd2 cwm builds
Click to expand...
Click to collapse
No. Neopeek already has made CWM for the RHOD. It's still based on the SD card tho...
If you think we can "just use" the HD2's NAND ROM's, you are kidding yourself...
Ok well I was in the x1 section will there builds work an what is the difference or benifit from using cwm over XDANDROID
sent by DAN SWAGGER via tapatalk/simple mobile
I think you are asking the difference between cwm builds and looped builds.
well IMO updating files like test libs is much easier in cwm but reverting test libs is much easier in looped system. On the whole i think cwm should be used by expert users who know how to use adb and unix commands to repair stuff when things go wrong.
There should be no problem running xdandroid as a cwm build but someone has to be motivated enough to do that.
tovarish said:
There should be no problem running xdandroid as a cwm build but someone has to be motivated enough to do that.
Click to expand...
Click to collapse
Indeed, the X1 is running CWM from Neopeek - SD card installs.
I made a FRX06 CWM build but it was really buggy. I didn't give it the attention it deserved, but since I couldn't get it off the ground on my phone I never posted it.
There's nothing holding anyone back from doing it... It booted for me, just had a ton of bugs - much more than the normal FRX06 build did, so I put it off to the side.
I can confirm frx06 cwm build is working for me
yankees2450 said:
I can confirm frx06 cwm build is working for me
Click to expand...
Click to collapse
Oh nice, i thought that the rootfs differences would be the main cause of problems. was that your experience.
I am running frx06 via cwm too (the same FRX06 build I only made a .zip package of it). Everything works fine for me just like the normal FRX06 build. If people want it, I can post a link.
But this is a bit off topic.
The answer on your question is no, we can't use hd2 cwm builds (if i'm right )
tovarish said:
Oh nice, i thought that the rootfs differences would be the main cause of problems. was that your experience.
Click to expand...
Click to collapse
the roofts is the same. I think neopeek change a few things, like init, initrd etc....
I'm using. [BUILD] **Complete Froyo Bundle!!** FRX06 - "Stable" - Minor Fixes http://forum.xda-developers.com/showthread.php?t=951962
here
frx06 cwm build
http://www.multiupload.com/PGZ7H8KTIT
tovarish said:
I think you are asking the difference between cwm builds and looped builds.
well IMO updating files like test libs is much easier in cwm but reverting test libs is much easier in looped system. On the whole i think cwm should be used by expert users who know how to use adb and unix commands to repair stuff when things go wrong.
There should be no problem running xdandroid as a cwm build but someone has to be motivated enough to do that.
Click to expand...
Click to collapse
I agree to a certain degree. But just to add, with cwm if you mess up it is very easy to fix. Their is a backup/restore function. When you get your build working you backup. Then if you have messed something up or currupted your data you don't even need to reinstall! Just restore the data partition. If you are messing around with the system and you mess up just restore the system partition, your data will even be safe. I find this very handy, it is a pain to havta reinstall everytime something breaks
Well how big can you make the partions
sent by DAN SWAGGER via tapatalk/simple mobile
dswaggz said:
Well how big can you make the partions
Click to expand...
Click to collapse
I don't know if there's an upper limit, AFAIK there's only a lower limit... 120-150mb for system, and at least 250mb I'd say for data...
dswaggz said:
Well how big can you make the partions
sent by DAN SWAGGER via tapatalk/simple mobile
Click to expand...
Click to collapse
This is recommended, but if you want larger partitions, it's also good:
Code:
1st partition: FAT32 (sdcard / Rest)
2nd partition: EXT2 (system / about 150MB -> depends on the build )
3rd partition: EXT2 (data / about 250MB)
4th partition: EXT2 (cache / about 50MB)
You have to make the partitions in that order. If you want a bigger data part, just make it about 500MB or 1GB.
I would recommend a much larger /cache partition (100+ MB) if you plan on installing many apps. This is because the dalvik cache is mounted on the cache partition.
Yes maybe thats better, but I just posted the sizes that are recommended by neopeek (who made CMW avaible on our devices).
But yes, if you have a 2GB sd card or something, it's better to make the partitions larger.
This works faster than the pure FRX06 on the main page. You should post it so others can use this version
bleuleon said:
This works faster than the pure FRX06 on the main page. You should post it so others can use this version
Click to expand...
Click to collapse
It seems faster to me, too... but I don't know if I'm just imagining it or not. Is there a reason it would be faster? I don't really know enough about these things to hazard a guess...
ppcfly said:
It seems faster to me, too... but I don't know if I'm just imagining it or not. Is there a reason it would be faster? I don't really know enough about these things to hazard a guess...
Click to expand...
Click to collapse
I guess because the partitions are dedicated, instead of loop mounts? I wouldn't think this would net much speed... Perhaps it does. Perhaps it's just snake oil and that's your perception .
arrrghhh said:
I guess because the partitions are dedicated, instead of loop mounts? I wouldn't think this would net much speed... Perhaps it does. Perhaps it's just snake oil and that's your perception .
Click to expand...
Click to collapse
I think after switching to partitions on FRX, I have seen a speed improvement. It's very hard to say for sure on this sorta thing, especially since I only spent a few days with FRX (coming from GRX) before partitioning.
However, the amount of times where I wonder whether my device is frozen or just didn't recognize my input has gone down to bearable levels recently, and the only change that seems relevant I've made recently is partitioning.
arrrghhh said:
I guess because the partitions are dedicated, instead of loop mounts? I wouldn't think this would net much speed... Perhaps it does. Perhaps it's just snake oil and that's your perception .
Click to expand...
Click to collapse
A strong possibility... perhaps someone needs to make an app with an dummy dial I can turn up to 11.
Have you tried the cwm fx6 yet arrrghhh? Just curious if you think it's faster or not...
THIS UTILITY IS FOR FASCINATE TOUCHWIZ FROYO/GINGERBREAD ONLY
UPDATED FOR EC09 GINGERBREAD
I have created a format utility that can be used from within CWM3 recovery. Just select the ZIP in CWM3 recovery, and the package will do ALL of the work for you.
These utilities come in two independent packages which will completely format your device with EXT4. As a bonus, it will create all directories and setup all ownership and permissions in accordance to the Fascinate.
Voodoo recovery does not currently allow you an option to select a format style, and furthermore does not truly format any partition unless it runs through the Voodoo "lagfix" transition upon booting the device.
There is one caveat in order to use EXT4: you need a kernel that supports it, and this would be using a "Voodoo" style kernel that has built in support. Luckily, most of the "good" kernels available have this ready to go.
Understand that this package will completely wipe your system, data, datadata (dbdata), and cache. This is a "full" wipe of the device. If you already have a ROM installed on your device and want to keep your device the way it is, and also want EXT4, then use the Voodoo method to switch to EXT4. The reason for this is because it backs up your data before it formats.
After you use this package, you can install any ROM of your choosing, as the package will already self-manage Voodoo's methods for "enabling" or "disabling" the "lagfix".
--------
Please report if the package is not working.
A good indicator of this is if you try to install the package and it only takes 1 second to work, then says it is finished. This means it is probably not working, however, if you are formatting the same type of file system over itself with no pre-existing data on the device, it will take the aforementioned 1 second to work.
To see if it worked: mount each partition in CWM3 recovery, then adb shell into your device and type the mount command, in the listing you should see what file system your partitions are using. If the big four all say EXT4, then the package install has been successful.
In order to assure that it will work correctly, use the latest version of a CWM3 recovery that you can find. I can personally vouch for nemesis2all's OTB CWM3 Recovery v3.0.2.8x.OTBv2. Unfortunately not all CWM3 recoveries are the same, and yours may not work with these utilities. If you find a recovery that works fine, post it here and I will update this.
--------
Packages updated: 6/28/2011 - 12:57PM EST
EXT4 Format ALL (formats everything): http://www.mediafire.com/?6hx7f8g7c8vv6xz
EXT4 Format CACHE: http://www.mediafire.com/?2621a888ydv41mg
EXT4 Format DATA: http://www.mediafire.com/?ck2bb340yybpe4z
EXT4 Format DBDATA: http://www.mediafire.com/?ahxzs8xsyyvemed
EXT4 Format FOTA: http://www.mediafire.com/?42ijpi67grdb6mm
EXT4 Format PREINSTALL: http://www.mediafire.com/?d42as1l3pdbhr2t
EXT4 Format SYSTEM: http://www.mediafire.com/?rgs46hhq8qd951t
--------------------
If you like my work, consider donating, or thanking me by clicking the thanks button
thanks for this
navenedrob said:
I have created two format utilities that can be used from within CWM3 recovery. Just select the type of file system you want to use, select it in CWM3 recovery, and the package will do ALL of the work for you.
These utilities come in two independent packages which will completely format your device with either RFS or EXT4. As a bonus, it will create all directories and setup all ownership and permissions in accordance to the Fascinate.
Voodoo recovery does not currently allow you an option to select a format style, and furthermore does not truly format any partition unless it runs through the Voodoo "lagfix" transition upon booting the device.
There is one caveat in order to use EXT4: you need a kernel that supports it, and this would be using a "Voodoo" style kernel that has built in support. Luckily, most of the "good" kernels available have this ready to go.
Understand that this package will completely wipe your system, data, datadata (dbdata), and cache. This is a "full" wipe of the device. If you already have a ROM installed on your device and want to keep your device the way it is, and also want EXT4, then use the Voodoo method to switch to EXT4. The reason for this is because it backs up your data before it formats.
After you use this package, you can install any ROM of your choosing, as the package will already self-manage Voodoo's methods for "enabling" or "disabling" the "lagfix".
Please report if the package is not working.
A good indicator of this is if you try to install the package and it only takes 1 second to work, then says it is finished. This means it is probably not working, however, if you are formatting the same type of file system over itself with no pre-existing data on the device, it will take the aforementioned 1 second to work.
To see if it worked: mount each partition in CWM3 recovery, then adb shell into your device and type the mount command, in the listing you should see what file system your partitions are using. If the big four all say EXT4 or RFS (depending on script used), then the package install has been successful.
In order to assure that it will work correctly, use the latest version of a CWM3 recovery that you can find. I can personally vouch for nemesis2all's OTB CWM3 Recovery v3.0.2.8x.OTBv2. Unfortunately not all CWM3 recoveries are the same, and yours may not work with these utilities. If you find a recovery that works fine, post it here and I will update this.
Click to expand...
Click to collapse
Ok, I think I'm having a complete idiot moment here so please be patient with me. What would be the benefits of me running this on my device that is currently running jt's CM7 with OTB 1.5 kernel and EXT4 (voodoo for those who don't know) already converted? Thanks in advance.
It would be of no use. Unless you need to format your entire device.
So this would be a good thing to flash in place of wiping between rom flashes? Does it have any benefits compared to a regular data and cache wipe when you are already converted to ext4?
It would be a good idea to flash it in that scenario, yes. Currently no ROM will do the job that this package will for you, which is why a lot of ROM's say not to wipe your device, because you'll run into major issues if you do. When you do your "wipes" through recovery it doesn't really do anything besides a recursive delete of files, so it doesn't really format anything (even though it says "format" in the menu system). The only time it actually does any formatting is during the Voodoo transition. When you do wipe those areas, it does not leave the file structure intact and also does not leave the ownership and permissions intact. These packages completely solve that problem. Also, these packages are focused on performance so everything is done that is possible to make sure that your file system is as fast as possible.
navenedrob said:
It would be a good idea to flash it in that scenario, yes. Currently no ROM will do the job that this package will for you, which is why a lot of ROM's say not to wipe your device, because you'll run into major issues if you do. When you do your "wipes" through recovery it doesn't really do anything besides a recursive delete of files, so it doesn't really format anything (even though it says "format" in the menu system). The only time it actually does any formatting is during the Voodoo transition. When you do wipe those areas, it does not leave the file structure intact and also does not leave the ownership and permissions intact. These packages completely solve that problem. Also, these packages are focused on performance so everything is done that is possible to make sure that your file system is as fast as possible.
Click to expand...
Click to collapse
Ok, so basically what you are saying is this would be ideal to use instead of data/cache/dalvik wipe for rfs to rfs and ext4 to ext4, correct? Thanks in advance.
That's correct.
I've teamed up with nemesis2all and we are thinking about adding all of these abilities to the OTB kernel, so you'll be able to choose different kinds of file systems and format options through CWM3 recovery instead of having to use these packages here. That will come when it comes, but for now this is the ideal solution.
EXT2/EXT3/EXT4/XFS/RFS etc...
Also, I've updated the attachments in the post.
navenedrob said:
That's correct.
I've teamed up with nemesis2all and we are thinking about adding all of these abilities to the OTB kernel, so you'll be able to choose different kinds of file systems and format options through CWM3 recovery instead of having to use these packages here. That will come when it comes, but for now this is the ideal solution.
EXT2/EXT3/EXT4/XFS/RFS etc...
Also, I've updated the attachments in the post.
Click to expand...
Click to collapse
Just to let you know, I ran the ext4 package and I got some serious lag issues after I installed my rom and it actually starting going into a soft boot loop. It began to act very weird and unstable. I booted back into recovery and I wiped everything the way I usually do and formatted the system/data/dbdata/cache manually in mounts and storage and reinstalled. It's better than it was but it still seems like it is kinda slower and more laggier than it was before I ran the package. Any ideas? Thanks man.
You'll need to give me more information than that to determine your problem.
What kernel are you using? What recovery are you using? What ROM are you running? What are the results of running the mount command with all partitions mounted?
navenedrob said:
You'll need to give me more information than that to determine your problem.
What kernel are you using? What recovery are you using? What ROM are you running? What are the results of running the mount command with all partitions mounted?
Click to expand...
Click to collapse
OTB 1.5, CM7. It's kinda weird. When I ran your package and then flashed cm7 and booted it, it was laggier than I have ever seen my phone and when I would try to do certain operations it would soft boot. At one point I couldn't even turn wifi on. So, I booted back into recovery and wiped and manually formatted everything and reinstalled everything. After that it was still kind of laggy but much better. I restored all of my apps and got my phone back to all my custom settings. Then I began to notice that it wasn't really lagging anymore, in fact it seemed pretty snappy. I ran quadrant to see if the numbers were the same as before to determine if I was in fact ext4 converted. Surprisingly the numbers were higher than normal. And I even noticed in titanium backup that some of my internal memory had been freed up. I can't explain it but everything seems to be running really good right now. It's almost like after running your package the phone had to be conditioned, and once it was conditioned it ran real good. But, that doesn't explain why it was soft booting and wifi wouldn't work. Who knows.
Not really sure exactly, it actually could have been a few different things causing the "issues". I'm going to try your exact scenario and see what happens.
kidserious said:
OTB 1.5, CM7. It's kinda weird. When I ran your package and then flashed cm7 and booted it, it was laggier than I have ever seen my phone and when I would try to do certain operations it would soft boot. At one point I couldn't even turn wifi on. So, I booted back into recovery and wiped and manually formatted everything and reinstalled everything. After that it was still kind of laggy but much better. I restored all of my apps and got my phone back to all my custom settings. Then I began to notice that it wasn't really lagging anymore, in fact it seemed pretty snappy. I ran quadrant to see if the numbers were the same as before to determine if I was in fact ext4 converted. Surprisingly the numbers were higher than normal. And I even noticed in titanium backup that some of my internal memory had been freed up. I can't explain it but everything seems to be running really good right now. It's almost like after running your package the phone had to be conditioned, and once it was conditioned it ran real good. But, that doesn't explain why it was soft booting and wifi wouldn't work. Who knows.
Click to expand...
Click to collapse
It's possible that since you wiped your market was trying to restore all your apps in the back ground which was taking all your memory up and making your phone lag. But after you restored all your apps it was all set
Coreyc1123 said:
It's possible that since you wiped your market was trying to restore all your apps in the back ground which was taking all your memory up and making your phone lag. But after you restored all your apps it was all set
Click to expand...
Click to collapse
What I meant was as soon as it booted (during setup wizard) it was super laggy. I download TB from the market by itself and it took forever to register. I was doing the GPS fix and it soft booted. I couldn't turn wifi on and it soft booted. All before I did a batch restore in TB. And I know that the market begins to sync automatically as it always does but this was much much different.
Sent from my SCH-I500 using Tapatalk
kidserious said:
What I meant was as soon as it booted (during setup wizard) it was super laggy. I download TB from the market by itself and it took forever to register. I was doing the GPS fix and it soft booted. I couldn't turn wifi on and it soft booted. All before I did a batch restore in TB. And I know that the market begins to sync automatically as it always does but this was much much different.
Sent from my SCH-I500 using Tapatalk
Click to expand...
Click to collapse
I had these same symptoms one time that I installed kasonate v7, but after reflashing, the next time it didnt.
I know you're not talking about the same cm version, but they might be related and not related to the format utility.
Ok, I ran this package again to make sure that I didn't do something wrong and to see if I would get the same results. I ran the package, flashed cm7 then gapps then OTB GB 1.5. all from the recommended recovery in your post. Again I ended up in a soft boot loop and wifi was acting up again and was causing a boot loop. So once again I booted into recovery and wiped data/cache/dalvik normally and formatted manually via mounts and storage and reinstalled again and she's running like a dream. Very weird but I must say I am very happy with the results I ended up with, regardless of how I got them. So obviously, this was not your intention for it to be done this way but I do see an improvement in responsiveness, speed and memory being freed up. Before, my free internal memory was 1.49 and now it is 1.52. Thank you sir, I appreciate this.
Thanks for this utility! Works great. Went from Jt's cm7 to the miui/touchwiz rom and ran the utility in between. My phone is running faster than ever and no issues. Thanks again!
Sent from my SCH-I500 using XDA App
Yeah running this on mesmerize with heinz 57 best my phone has ever run quadrant of 2250s @ 1.5 ghz
Sent from my SCH-I500 using XDA App
stephenj37826 said:
Yeah running this on mesmerize with heinz 57 best my phone has ever run quadrant of 2250s @ 1.5 ghz
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
You're welcome, the utility enables a few nice options as far as file system performance is concerned, that Voodoo doesn't at this time.
Do tell oh and thanks a million
Sent from my SCH-I500 using XDA App
So, this is just a pristine (as "untouched" as possible) image of the Norwegian telenor one.
What I have done:
I've extracted everything, deodexed it, and put everything, excluding all useless junk, in here. Nothing is edited or removed.
All I've added is SuperSU, busybox and ES File explorer. And changed /system/etc/customization/settings/config.prop so the phone is in US English on first boot. (Well, that's the only thing I've edited)
Only files that aren't deodexed are playstationcertified.odex and com.android.nfc_extras.odex. There's no .jar-files for them so...
I copied playstationcertified.odex to com.playstation.playstationcertified.odex since AndroPlus mentioned something about it somewhere. Don't know how important this is.
What kernel should I use with this?
I'd recommend AndroPlus' work any day. It's awesome! So head over and hit that thanks-button for him to show how awesome you think it is!
http://forum.xda-developers.com/showpost.php?p=56439759&postcount=1
If you do use one of his 27-and-on-kernels you can format /system and /cache as F2FS.
Do not format /data as F2FS though. Do not do it. The phone won't boot if /data is formatted as F2FS.
Don't know why not.
If this bricks your phone or whatever else problem arises, I'm not responsible or of much help.
All I can vouch for is it runs fine on my D6603 Z3 phone. With /cache and /system formatted as F2FS.
(Also runs fine with /cache and /system as ext4, if you're wondering)
Does it work with a locked or unlocked bootloader?
It works with an unlocked bootloader. Don't know if it works with a locked one, mine is unlocked.
Here you go:
shrunk-D6603_23.0.1.A.5.77_R12B_Telenor.zip
Here are the files that have been removed:
http://www.mediafire.com/download/vybrb0k5l0s5coy/removed.zip
They're just collected in a zip-file with various folders that tells you where they belong. So you can just take what ever you feel is missing and put it "back" in place in the shrink-zip above.
Here is the original (but still deodexed) thing in one big chunk:
http://www.mediafire.com/download/85evwwlu7fn7vul/23.0.1.A.5.77_Telenor.zip
Just for the sake of the challenge, here is as small as I manage to squeeze it. Just about 1GB on the phone after first installation (420MB as a download).
1. The background is "black" on boot. You need to touch and hold the screen, choose "themes", and select the one theme there is. There is no longer any automation-process that does this on first boot.
2. You need to set language yourself. Go to "settings", "language and keyboard", and change it to the language of your preference.
3. You now have a small ROM on your phone!
http://www.mediafire.com/download/0ei9bjbb8dfn99c/small-D6603_23.0.1.A.5.77_R12B_Telenor.zip
"But I need this and that program, can't you add..."
You do it! Just put what ever program you have or want in to /system/app on the phone (that is, in the zip-file). Some programs needs to be in /system/priv-app (they will force close on you until you put them in /system/priv-app - to really confuse you, playstation app has to be in /system/etc/product/applications, or it won't work. Why I have no idea...).
"But nothing happens when I hit the search bar on top..."
I removed Google Search. If you want it you can put it in /system/priv-app.
"I want to add wallpapers and ringtones"
Here you go. Just add ringtones and wallpapers to their respective folders and zip up, then install just like you'd install a ROM.
http://www.mediafire.com/download/5f5745fo5jlu4qb/add-ringtones-wallpapers.zip
Gonna give this a go later..
Just wondering, if you have already done the drm restore method listed in androkernel thread do you lose it when you flash a rom via zip? Is there anyway to get the drm fix to work on this rom?
Thanks!
Guitarfreak26 said:
Gonna give this a go later..
Just wondering, if you have already done the drm restore method listed in androkernel thread do you lose it when you flash a rom via zip? Is there anyway to get the drm fix to work on this rom?
Thanks!
Click to expand...
Click to collapse
No, I haven't. My point is generally just to make a "pristine" ROM. That is, I've removed what I don't think is needed (I'll upload the "leftovers" in a zip, after doing some more work), but other than that, this is just the way the original ROM was.
With added root and a file explorer.
But it's not that hard to add the stuff from that zip-file. They're just a few files that are extracted to overwrite some files in /system. Just open up the drm-zip and you'll see. The script for DRM doesn't do anything other than just extract (and overwrite) the files inside the zip. So if you want, you could just try to add those files to this and make that happen yourself.
What's the process for getting it as f2fs? Total novice with file systems but saw you guys talking about it in the kernel thread? Is it a case of installing it then converting in twrp?
Sent from my iPhone using Tapatalk
Has anybody tried this on locked bootloader?
The OP says they don't know since they have unlocked bootloader.
Thanks
@Verbato, please for next build i request 2 things, 1. Please remove the wipe internal storage upon flashing, 2. Please add the clock and calendar back, i think many users feel the way i do saying the clock and calendar are vital system apps that were removed, thanks for your work, the rom is smooth and fast with f2fs
corpsegrinder62 said:
@Verbato, please for next build i request 2 things, 1. Please remove the wipe internal storage upon flashing, 2. Please add the clock and calendar back, i think many users feel the way i do saying the clock and calendar are vital system apps that were removed, thanks for your work, the rom is smooth and fast with f2fs
Click to expand...
Click to collapse
Whats the best way to set it up with f2fs? Op said he will release a zip soon with missing apps etc
Guitarfreak26 said:
Whats the best way to set it up with f2fs? Op said he will release a zip soon with missing apps etc
Click to expand...
Click to collapse
The easiest way i done it is i used androplus kernel v27 with multirom twrp 2.8.5, flash with fota if u need to. Go to wipe, advanced wipe, tick which partition you want, eg. System, click change/repair file system - F2FS, do it with system and cache, just be warned - it will wipe both /data and /data/media so backup first. Last step is flash rom zip, sit back, relax, and enjoy f2fs partition, you should notice apps launch tons faster after doing it. Cannot format /data to f2fs though as op mentioned, system and cache only.
@Corpsegrinder Sure, no problem. If it's annoying you, the wiping of /data, I can just send you a new updater-script. It's inside of META-INF. If you download the first file over you'll find calendar and clock in /system/app. They're called "SemcClock.apk" and "SemcCalendar.apk".
I'll remark out the /data-wipe and add clock+cal in the next update.
Updated. No deletion of any data in... data. Added calc and calender. Will put in some work to make it even smaller. Means quicker, means less CPU-usage, and so less battery usage.
corpsegrinder62 said:
just be warned - it will wipe both /data and /data/media so backup first
Click to expand...
Click to collapse
Not any more.
Working on making it a slight bit smaller/quicker/etc.
Root and recovery
Hi. I really appreciate your work putting a debloated rom together for us.
I'm quite new to Z3 roms and feel quite overwhelmed by all the technical info in the various threads. Do you know if/how I can flash this with TWRP and keep the phone rooted?
I did the downgrade/giefroot/recovery process that doesn't need to unlock bootloader, so I'm sitting on the .93 build for now.
KnuckleSnackwich said:
Hi. I really appreciate your work putting a debloated rom together for us.
I'm quite new to Z3 roms and feel quite overwhelmed by all the technical info in the various threads. Do you know if/how I can flash this with TWRP and keep the phone rooted?
I did the downgrade/giefroot/recovery process that doesn't need to unlock bootloader, so I'm sitting on the .93 build for now.
Click to expand...
Click to collapse
Download and pre-root .77 with PRFCreator, flash it through recovery, re-flash recovery itself, switch off and then on again (dnt reboot)
I really like this since i hate bloatware. Is there any chance to get a lollipop version with minimal to no bloatware?
Will this work on the D6616?
any link for AndroPlus kernel? link in OP not working. thank you.