So, the thing is...I absolutely cannot stand HTC Sense. I am an Android purist and a minimalist at heart. I love HTC's hardware...but their software is crap. Coming from a Nexus One, which had almost no bloatware on it at all, I experienced quite a shock when I first booted up my Amaze. I've seen less crap on a manure truck.
So, the logical thing to do of course would be to dump the stock rom, and load up CrackEyes SenseLess (or BulletLess or whatever he's calling it now). I've tried them...and no offense to CrackEyes...I'm sure he's put a lot of time and effort in to making these ROMs...but they're just not stable enough for me. On the other hand, Xboarder's QuikSense and BulletProof have proved themselves rock solid time and time again. But Xboarder doesn't seem to mind leaving some of the bloatware and stock HTC sense crap on there that a minimalist like myself hates.
I am actually working on compiling my own ROM (which I plan on calling AntiSense whenever it's done), but as I am a newcomer to the developing scene, it's taking a while b/c I've never done anything this complicated before. Luckily I've made some friends over in the G-Slate community who have helped me along quite a bit.
However, until my ROM is finished, I created 4 simple little batch files that will safely and quickly debloat XBoarder's BulletProof v2.5 (which is what I currently have installed and tested it on). Should work on earlier versions as well, and maybe even other ROMs (though probably not any of CrackEyes' as he's already removed a lot of this stuff already). There are 4 versions, two which will simply move the apps out of the way (into a folder called app-unused), and two of which will actually remove the apps from the device entirely. Each has its own trade-offs. The Debloaters will keep the apps from being visible by android, and will provide a backup location for these apps should you want to reinstall them later, however it will not save you any space on the internal phone storage. The Debloater-Removers will get you more space in your internal phone storage, but will not provide a backup for the apps and could potentially cause some errors or FCs with Sense (although I have yet to experience any during my tests). So, in other words, choose wisely which one you want to use.
REQ's:
1. ClockworkMod 5.5.0.4 (XBoarder's work) or HTC Sync and HTC drivers installed on PC.
2. BulletProof 2.5 or less (XBoarder again), or some other ROM that enabled root access except Senseless or BulletLess.
3. Android SDK installed and system variables are set properly on your Windows machine (btw this won't work for linux duh). Instructions for this are found in the quote below. Copied straight off'a Cyanogenmod Wiki. Adjust folder paths to your android-sdk folder as necessary.
Go to the Control Panel, and select the System Properties (Windows XP) or System (Windows Vista/7).
Select the Advanced settings;
Windows XP: Click on the Advanced tab.
Windows Vista/7: Click on Advanced system settings on the left.
Click on Environment Variables.
Under the "System variable" section, you will look for "Path". Double-click on it.
In the "Variable values" section, add at the very end the location of the tools & package-tools folder, with a semicolon separating these two paths from the rest, e.g. %SystemRoot%;C:\android-sdk\platform-tools;C:\android-sdk\tools
Click to expand...
Click to collapse
CWM RECOVERY INSTALL INSTRUCTIONS
1. Plug into PC via usb.
2. Boot phone into recovery.
3. Select Mounts & Storage, then select 'Mount /System'.
4. Download attached .zip file with your PC, unzip to wherever.
5. Run the .bat file with the 'CWM' ending. I put several pause commands in the file, so if you come up with some errors you can just copy them straight from command prompt and paste them here.
6. Reboot phone.
7. Done
HTC SYNC INSTALL INSTRUCTIONS
1. Plug phone into PC via USB, change connection type on phone to HTC Sync.
2. Wait for phone to find HTC Sync on PC.
3. Download attached .zip file with your PC, unzip to wherever.
4. Run the .bat file with the 'Sync' ending. I put several pause commands in the file, so if you come up with some errors you can just copy them straight from command prompt and paste them here.
5. Reboot phone
6. Done.
DISCLAIMER:
I claim no responsibility for anything this does lulz
No but seriously, this should work fine without causing any damage to your phone. I've tested it multiple times already. That being said, if it does f up your phone, I have no obligation to fix it. Use this at your own risk.
CHANGELOG:
v2.1 - Figured out easier HTC Sync method, included 2 new batch files that will work with it. Also updated a few minor things, made it look prettier, etc.
v2.0 - Debloater-Remover initial release, changed folder name to 'app-unused' in regular Debloater, few other minor changes.
v1.0 - Initial Release
nice work man
Like you, I've always preferred the pure Android experience. Sense isn't too bad, but I'd much rather do without.
I'm not using BulletProof (currently using OneGoodROM with the nonSense mod) at the moment, but I can't wait to see what you come up with for people like us who prefer the look and feel of AOSP ROMs over Sense
Hmmm. Maybe I can put this into my Toolkit I developed if you do not mind.
http://forum.xda-developers.com/showthread.php?t=1493905
Let me know if you want me to or not. Thanks!
adslee said:
Like you, I've always preferred the pure Android experience. Sense isn't too bad, but I'd much rather do without.
I'm not using BulletProof (currently using OneGoodROM with the nonSense mod) at the moment, but I can't wait to see what you come up with for people like us who prefer the look and feel of AOSP ROMs over Sense
Click to expand...
Click to collapse
I also like AOSP more than sense, mainly for the extra free RAM and space. Download speeds are always faster too on aosp ROMs. I've been waiting for XBoarders ICS or a stable aosp-like ROM to come through. I wish we had S=off so CM team would come over. Ive been using Energy ROM for now... It's so stable I can't justify trying any other sense ROM at the moment.
Sent from my HTC_Amaze_4G using xda premium
Never thought about doing it this way. I used to do this manually using Titanium Backup. Great work!
hasoon2000 said:
Hmmm. Maybe I can put this into my Toolkit I developed if you do not mind.
http://forum.xda-developers.com/showthread.php?t=1493905
Let me know if you want me to or not. Thanks!
Click to expand...
Click to collapse
Sure go for it.
Just uploaded v2.0, added Debloater-Remover in the .zip file. Let me know if you guys have any issues.
Just curious, will this work on any sense Rom besides the Amaze?
Edit: I added it to my toolkit anyways lol.
Sent From My HTC Amaze 4G via Someone's Room
hasoon2000 said:
Just curious, will this work on any sense Rom besides the Amaze?
Edit: I added it to my toolkit anyways lol.
Sent From My HTC Amaze 4G via Someone's Room
Click to expand...
Click to collapse
It should work with any ROM that enables root access, with the lone exceptions being SenseLess and BulletLess as they already have a lot of this stuff removed already.
Related
We've updated a bit....
Download Link: [Here]
We now have a complimentary app on the app store for this A4D App.
What is A4D?
The goal of A4D is for us to move beyond just N1 make it an all in one flashing/upgrading/android utility. We just added a ROM library with MD5s. We are not going to be hosting the actual ROMs by themselves so if you report a dead link, they will be taken down (after a number of reports). You can also add your own ROMs as well into the library.
The ROM library will be supported by both Android and Desktop App. We are rewriting the Desktop apps so that we can do all 3 platforms in one, Linux, Windows, and Mac. You'll love the layout of the app. That's all we can say for now.
Oh one more thing. The android app won the best android app award at the Mobile in the Middle Hack-a-thon over the weekend in Chicago (on 3/6/2010).
I would like you guys to try out the app and tell us feedbacks. Also feel free to add your own ROMs to the Database and tell us how we can make the DB better. There a number of features we are trying to add as well. But with our full time jobs... things are going a little slower than we wanted. Sorry.
Requirements to run the app on Android: Amon_RA's recovery. That's what we tested it with.
Reserved
Reserved for Future Updates / Changelog
Can't wait to see if this is fool proof.
Add md5 check. Make it in this way: user have to enter/copy-past md5 hashsum from forum/site. Program calculates md5 of image and says image is good or bad. Also you can disable flashing with out this check. ;-)
good idea. Will do that. That will help with flashing screwed up downloads.
Hi
Thank you for sharing the application.
Does it flash the radio too? I mean CyanogenMod has two files a radio ROM and a CyanogenMod ROM. Does it flash both of them to the phone?
Thanks.
Radio flash is in there we took it out. May do so in the next release but radio flashing is dangerous (can brick phones) so...
Hey Lwin,
Nice concept man, this is gonna prove very handy for many peeps.
You've come up trumps again
So, this is a desktop application?
Does it flash ROM's from your desktop or copy them over and just run the commands on the phone for you?
I ask, as I'm having some problems flashing now, based round a slightly faulty Micro SD card. Does it store backups on the phone or on your desktop PC?
This program is written so you don't have to do command line commands. Everything else remains the same. If you are doing a Nand backup, it goes where it used to go.
I would recommend fixing your "slightly faulty Micro SD card" by getting a new card.
nice app for those that aren't familiar with cmd or jus pure...lazy lol
maybe the screens should be bigger as quite hard to see clearly whats available.
Pure Genius...
seraph1024 said:
Here is the GUI tool for unlocking, updating, restoring, flashing of the N1 (and in theory should work on all HTC androids).
Try it out and see if it is useful. The tool is made to help for people with very basic skills since the tool at this stage is a wrapper for the shell commands at this point.
Again, as usual, we take no responsibility for loss of sleep, loss of phone or screw ups on our side (due to app) or on your side (due to lack of ability to follow instructions).
I wish to make it more simple. We welcome feed backs.
Seraph1024 - ShadowPyro
Download Link: [Here]
Click to expand...
Click to collapse
Hey Seraph, This is getting better and better everyday.. How is your windows and android port.. Oh and don't forget there little buddy, I need you on my Mobility Team when we arrive to the scene.. Android and Audi... Almost there....
Edit: Okay, can't run on Mac, of course will in VMware, can you please make this mac native too... It would be great as per what MooMoo said, for all who are lazy...
shadowpyro said:
This program is written so you don't have to do command line commands. Everything else remains the same.
Click to expand...
Click to collapse
But I don't use command line now. I didn't realise anyone did. Do you not just boot into RA Recovery and flash from there?
shadowpyro said:
I would recommend fixing your "slightly faulty Micro SD card" by getting a new card.
Click to expand...
Click to collapse
Thanks, I didn't ask for advice.
GodDriven said:
Hey Seraph, This is getting better and better everyday.. How is your windows and android port.. Oh and don't forget there little buddy, I need you on my Mobility Team when we arrive to the scene.. Android and Audi... Almost there....
Edit: Okay, can't run on Mac, of course will in VMware, can you please make this mac native too... It would be great as per what MooMoo said, for all who are lazy...
Click to expand...
Click to collapse
There will be a mac port sometime this week. I can most likely port to linux too but if you know linux and if you have to use wrapper, you have an issue
install issues
I tried to install it but got a system update required....
extracted the sdk to the folder C:\android-sdk-windows
extracted android4dummies and clicked setup
I get a pop up with the following:
unable to install or run the application. the application requires that system assembly system.data, entry version 3.5.0.0 be installed in the global system cache.....???
What do I do now?
Sounds like the app uses .NET framework 3.5.
So goto microsoft website an get 3.5 .Net Framework.
pwvandeursen said:
I tried to install it but got a system update required....
extracted the sdk to the folder C:\android-sdk-windows
extracted android4dummies and clicked setup
I get a pop up with the following:
unable to install or run the application. the application requires that system assembly system.data, entry version 3.5.0.0 be installed in the global system cache.....???
What do I do now?
Click to expand...
Click to collapse
You do need .Net 3.5. It should have asked you, if not installed that as a prerequisite.
I went to MS and downloaded the .net 3.5 installed it (apparently it was already on my pc, so instead of installing I tried to repair it. no success....
pwvandeursen said:
I went to MS and downloaded the .net 3.5 installed it (apparently it was already on my pc, so instead of installing I tried to repair it. no success....
Click to expand...
Click to collapse
Can you send us a screenshot.
Do not unzip into C:\android-sdk-windows. App will install SDK or search for the SDK there.
Unzip on your desktop or temp and install from there.
just to be clear, I unzipped adroid sdk and placed in the mentioned location. the android4dummies is extracted on the desktop and executed from there..
so should I remove the SDK and retry?
Very Important Information For Beginners
/Introduction to Android for SD Cards
Okay, firstly I made this thread because pretty much every new person to this section of the forums is completely lost and unsure what things are or what to even do. We are also sick and tired of threads saying 'how do I get stared' or 'which is the most stable' etc.
----------------------
Download your files from here:
You will be accessing these websites quite often so it might pay to bookmark them
Kernel downloads, almost always download the top one, they are updated often (needs extracting): http://glemsom.users.anapnea.net/android2/htc-msm-linux/
Rootfs downloads, download the top one, they aren't updated as often as the kernels above but still quite regularly (also needs extracting): http://files.xdandroid.com/rootfs/
Initrd downloads, rarely updated (don't extract, just rename to initrd.gz) http://files.xdandroid.com/initramfs/ People almost never need to download one of these separately.
----------------------------------
Basic need-to-knows:
Kernel: Your modules/zImage. Your zImage always needs be in the root (first folder) of your android folder on your SD and ALWAYS named zImage, your modules should also be in the root of your android folder named modules-LOTSofNUMBERSandLETTERS.tar.gz never rename your modules. It should always be in .tar.gz EG: modules-2.6.27.46-01276-g6a6a1c1-dirty.tar.gz
Rootfs: Must be in the root of your android folder named rootfs.img
Initrd: Needs to be in the root of your android folder named initrd.gz
Data.img: Generated on the first boot of android and placed in root of android folder. Is a virtual memory file that acts as the phones internal memory for android. Holds all your settings etc. May have to be recreated some times (just by deleting it)
Haret.exe: the file executed by your Windows ROM to kick Windows out of memory and boot android.
system.ext2: Main android file, must be in the root of your android folder. Holds all of your build.
startup.txt: File that instructs android how to start up. Needs to be in the root of your SD. (I will cover this further down)
ts-calibration: A file in the android folder that holds calibration information of the touch screen.
Various Folders: You will see/have/need other various folders created in the root of your SD and in the root of the android folder, such as conf, cache, data, media etc. You usually don't want to delete these.
Root: The root folder of any partition is the "highest" folder in the hierarchy. The root folder contains all other folders and can also contain files. For example, the root folder of the main partition on your computer is probably C:\. The root folder of your DVD or CD drive might be D:\.
Also Known As: "the root"
RIL: Radio interface layer: basically controls your radio (GSM/CDMA network)
------------------------------------------------
startup.txt
VERY IMPORTANT, your startup.txt must be customized to your device. (mine is a rhod110). You can find your model number under your battery. This file belongs in the folder with your android.
My startup.txt looks like this
Code:
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2292
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=240 msmvkeyb_toggle=off gsensor_axis=2,1,3 pm.sleep_mode=1 rel_path=FRX07 physkeyboard=rhod100_uk acpuclock.oc_freq_khz=710000"
boot
Now I believe you should be able to copy and use this as yours with a few slight modifications. Change rel_path= to wherever your android is stored on your sd, for example when I go to my sd inside the folder frx07 (the root of my android folder) all my android files are there. If your folder was called andboot it would be rel_path=andboot. (without that full stop) Now change your physkeyboard= to your model of your phone, mine is rhod110 but the rhod100_uk keymap is EXACTLY THE SAME AS THE RHOD110 so that's why I use rhod100_uk instead of rhod110 (rhod110 isn't recognised by frx07), this is important to make sure your keys are assigned properly.
------------------------------------------------
Models of rhod:
From what I know that exists. If you find one not listed, make sure you tell me so I can update the list
rhod110 uses rhod100_uk and it works as it should
These can be used for physkeyboard= in startup.txt (needs updating, some may no longet be supported because F22 hasn't commited old changes)
rhod100_de
rhod100_es
rhod100_fr
rhod100_it
rhod100_nl
rhod100_nordic
rhod100_uk
rhod210
rhod300 (tilt2)
rhod400
rhod500
Getting set up:
Go to http://forum.xda-developers.com/showthread.php?t=1171052 and download the FULL BUNDLE
Other builds exist such as gingerbread but this guide only covers froyo frx07.
Replace/add the Kernel from the downloaded build with the latest one (remember this is the zImage and modules-NUMBERS.tar.gz). Updating is as simple as this, do it often - there is no data loss. See links mentioned above for links. Making sure that the (if there were) old kernel files are all deleted and the new ones are called zImage and modules-NEWdifferentNUMBERS.tar.gz
Replace/add the rootfs.img with the latest one from the link above it should be named rootfs.img.
Remember that the rootfs and kernel are updated quite often and that you should check and update every few days.
Make sure your startup.txt is correct and make sure everything is where it should be in a folder on your computer, then copy the folder to the root of your sd card.
Navigate to this folder using the file explorer in your Windows ROM (YOUR PHONE) and run the Haret.exe
It will then have some writing running down a black screen before booting android (it's just preparation to booting) read it if you want
Android will start and you should leave it about 2-5 minutes before touching anything, it has things running in the background and it will be slow, still setting itself up. Navigate to settings and set up your phone. If anything goes too badly wrong you can always delete data.img and start again! Data.img is the internal memory of the phone, remember? Well, until we get android working on the real internal memory...
---------------------------
Structure:
My SD card. (with android on it)
I'm running:
kernel: 20110819_183957 http://glemsom.users.anapnea.net/android2/htc-msm-linux/
build: Froyo FRX07http://forum.xda-developers.com/showthread.php?t=1171052
rootfs: rootfs-20110816-7e04198.zip from http://files.xdandroid.com/rootfs/
Code:
EncFiltLog.menc
kbd_info
Android
cache
download
tmp
Private
Games
Installs
DCIM
Others
Videos
Images
Sounds
media
frx07
rhodimg.nbh
My android is in frx07
inside my frx07:
Code:
data.img
ts-calibration
startup.txt
modules-2.6.27.46-01348-g9de837f.tar.gz
zImage
haret.exe
initrd.gz
system.ext2
AndroidApps
conf
media
rootfs.img
-----------------------------------------
Backup/Restore
when you have the need to backup and restore data, look for an app called Titanium Backup. I have never used it but heard it works brilliantly, even backing up your apps! There is a 'donation' version and a free version with not many differences. I suggest you go check it out!
-----------------------------
USB CONNECTIVITY
When your phone is in Android you can not use it like a USB, HTC's drivers will not work and you have to use certain programs until this is implemented.
Windows: Install DroidExplorer this lets you open a terminal (like command prompt) on the phone, lets you browse device adding/deleting files, among other features that are very useful. If that DroidExplorer doesn't pick up your phone (when picked up it will be called 0000000000) install PDAnet on your phone and pc. PDAnet provides the drivers needed to connect the phone. It also lets you use your phone as a modem and you can send SMSs using your computer. Do NOT run PDANET at the same time as DroidExplorer. When PDANET is connected it WILL use your phone for data connections - this is the only warning. The phone is not used for any networking when DroidExplorer is connected.
Mac: Unknown to me (can someone post?)
Linux: Never tried, it is easier than windows (can someone post a method?)
---------------------
Overclocking
Do NOT overclock WINMO.
If you want to overclock your device do so at your own risk.
it is as simple as adding "acpuclock.oc_freq_khz=710000" without quotes to your startup.txt cmdline. 710000 (approx 710 mhz) can be swapped for any number but this is practically the highest stable speed achievable. I use 710000, works fine for me.
-------------------------
Known problems across ALL BUILDS:
Media Player Some tracks might have playing issues. FIX: HERE
Bluetooth is experiemental
Speakerphone static : seemingly random issue
USB plugging the device into a computer, it will be recognised, but not by HTC drivers. FIX: You must use something like DroidExplorer and PDAnet to browse the device and ADB (android debug bridge). See above ^^ (USB tethering is being fixed/has been fixed)
FN LED On keyboard the caps LED works but the FN LED currently does not. FN still works fine
No deep sleep: FIX: disable GPS (or kill the running app causing phone to not sleep)
Failure booting Android: Phone fails to enter android after running haret.exe FIX: Make sure your winmo is NOT overclocked before booting android.
Booting or SD Card related problems: Make sure your card is formatted as FAT32 (reformat as Full Format if it is not working)
More information is available on the wiki, there is also information there if you want to get into development. There is a pretty good FAQ on that wiki too
Remember XDAndroid is not just for this device.
If any of this is wrong or you think something should be updated/changed, please tell me
The CDMA startup should have "board-htcrhodium.is_cdma=1" instead of "...is_gsm=0"
otherwise, looks good!
AkumaX said:
The CDMA startup should have "board-htcrhodium.is_cdma=1" instead of "...is_gsm=0"
otherwise, looks good!
Click to expand...
Click to collapse
Indeed, there is no "is_gsm" command .
arrrghhh said:
Indeed, there is no "is_gsm" command .
Click to expand...
Click to collapse
Thanks to both of you, not bad considering I don't even have a cdma phone eh?
anything I need to add? I will tidy it all up soon
Something that might catch out a beginner is if they have an older SD card and it isn't detected by more recent kernels.
Need to include this in the cmdline:
msmsdcc_1bit msmsdcc_fmax=14000000
the.decoy said:
Something that might catch out a beginner is if they have an older SD card and it isn't detected by more recent kernels.
Need to include this in the cmdline:
msmsdcc_1bit msmsdcc_fmax=14000000
Click to expand...
Click to collapse
I thought this was squashed in recent kernels?
arrrghh said:
saneksem said:
add that to startup,helped me on 2 gb card
msmsdcc_1bit msmsdcc_fmax=14000000 msmsdcc_nopwrsave
Click to expand...
Click to collapse
You don't need this if you're on a newer kernel!!!!
Just update your kernel folks, no need for this in the startup!
Click to expand...
Click to collapse
Oh, ok. I must have missed that. I only needed it on my older SD which I haven't tried using for a month or so.
I guess the only thing I would suggest (all minor things) would be maybe to bold/underline keywords, like "kernel", "rootfs", etc.. to differentiate things that may change over time; ex: I'm running FRX05 system.ext2, 3/1/11 rootfs from F22, 3/1/11 zImage/modules (kernel) from arrgghh, etc... And, I guess you "could" be nice and show people what they could edit in the startup.txt, depending on their phone; ex: I'm Sprint, so I would do kb=rhod400, cdma=1, etc..., but for each phone.
I would probably have to do all the different startup.txt's in a different thread, unless I just provide a quick table... I will think about it however I do like the idea about bolding key words.
Most new people don't realize if they have their call/end/windows/back buttons on in winmo, they will stay on while on android and never go off. Might want to put that in your first post before telling them to run haret...
at the end where you say you can just delete the data.img and startover its probably a better idea to say to be patient and reboot the phone once or twice before ditching your data.img ! and creating it is the bulk of the first boot, the linux black screen with the scrolling words section.
you can talk about saving your data.img just incase something goes wrong.
titanium backup is a must
having an app that can save sms when you switch builds (not a big deal for everyone but important to some.)
also let new users know android isn't perfect, things randomly completely mess themselves all the time, don't get discouraged just start fresh with a format and new files when deleting the data.img doesn't work and you'll be just fine.
All I want to know now is if I have helped anyone yet and if they had any problems with any part of it or want me to clarify anything I will be quite happy with such replies ^-^
Is anyone able to provide me with some ETAs of fixes on the problems across all builds listed in the OP? Also are there any more I am not aware of? Oh and if anyone is working on them?
Much Appreciated
ryannathans said:
Is anyone able to provide me with some ETAs of fixes on the problems across all builds listed in the OP? Also are there any more I am not aware of? Oh and if anyone is working on them?
Much Appreciated
Click to expand...
Click to collapse
There's never an ETA for anything getting fixed - BT seems close, but who knows the exact date it will be done? As CyanogenMod says, the only rule is don't ask for release dates / ETA. It'll be ready when it's ready.
Some problems are being looked into more than others, but I wouldn't say one in particular has been left out to rot. jb is fixing up BT, entropy is working on GPS fixes, wistilt2 on the RIL of late... Basically devs pickup things that are of an interest to them to fix. There's a lot still to fix/cleanup, so taking it all on alone is a little daunting. Gotta break it down into smaller pieces so it's at least somewhat manageable.
Thanks and a question...
First, thanks for the awesome post - quite helpful...
Second: I haven't mussed with my phone for about a year, for various reasons, the main one being that I was happy with my previous phone and the ROM I finally settled on, the secondary one being that phone died, and I now have a (blech) Sprint TouchPro2 (RHOD400), and am on my sixth (yes, sixth!) brand new TP2 - they keep giving me a new one because of problems (things, like... oh... say, not being able to answer calls... kind of a basic function in a mobile phone, nah?!) And, I've had no interest in futzing with what is already a frustrating and non-functional phone. I was hoping I could upgrade instead of getting another TP2 the last time I brought it in for probs, but they would only downgrade me to worse phones. So... here I am, wanting to put Android on my phone and see if there is any improvement. Or, at the least, be able to utilize some of the decent progz/gamez for Android. I mean, if I can't answer calls, at least I can use it as a handheld gaming system, right?!
Long story short: when I was flashing ROMs to other phones, the instructions explicitly said that you needed to unlock, etc., first. I can't find any data re: if there are steps you must take on your phone to 'prep' it, *before* following the steps in this thread. I've browsed the DB and no luck.
My apologies for being an annoying n00b!
PS: one of my friends said "Tell 'em you're a hawt babe - then they'll help for sure!" (ROFL)
And, thanks, again!
Tynkrrbell said:
Long story short: when I was flashing ROMs to other phones, the instructions explicitly said that you needed to unlock, etc., first. I can't find any data re: if there are steps you must take on your phone to 'prep' it, *before* following the steps in this thread. I've browsed the DB and no luck.
My apologies for being an annoying n00b!
And, thanks, again!
Click to expand...
Click to collapse
Well the reason you can't find any info on it, is that it's not required .
These builds run entirely off of the SD (currently - I wouldn't try NAND yet, it's in its infancy) so there's no need to do any HardSPL or anything really to prep - just drop the bundle on your SD card - if it's at the root, run haret.exe and gogogo!
Oi. I get the stupidcard of the day!
That is awesome! Same friend that suggested I mention I am a 'hawt babe' said I should "give boobpr0n" to whomever helped me. You probably wouldn't want to see that, though!
You are heartily appreciated! I'm off to be an Androidite!!!!!!
Tynkrrbell said:
That is awesome! Same friend that suggested I mention I am a 'hawt babe' said I should "give boobpr0n" to whomever helped me. You probably wouldn't want to see that, though!
You are heartily appreciated! I'm off to be an Androidite!!!!!!
Click to expand...
Click to collapse
My gf suffices for that .
Hope you enjoy Android!
Tynkrrbell said:
That is awesome! Same friend that suggested I mention I am a 'hawt babe' said I should "give boobpr0n" to whomever helped me. You probably wouldn't want to see that, though!
You are heartily appreciated! I'm off to be an Androidite!!!!!!
Click to expand...
Click to collapse
Not to burst any bubbles here, but if you are saying you are a "hawt babe" and give boobpr0n mumbo jumba, you are prolly not one and won't give it anyways.. so nobody will most likely believe you here..
Good luck though~
Hey guys,
So, as I've finally started test out all the different ROMs on this forum (and on others) for the HTC Amaze, I've also begun to develop specific debloater tools for each one. Eventually of course my goal is to create my own ROM, but seeing as how I'm still learning a lot of the developing techniques, it's going to be a while. But, as a minimalist, and an Android purist, most of the apps that comes with the Amaze is, at least to me, crap. There are some useful apps developed by HTC, but not many, and 95% of them I can live without (or replace with a Google or 3rd party app that works just as well or better).
I'm rambling, I know, sorry. But to get to the point, I plan on releasing a customized Debloater tool for most ROMs already developed on this forum and others. The first ROM I developed this debloater tool for was XBoarder's Bulletproof, which most of you already have seen (that thread will be linked to later on).
Of course, proper credit must be given where proper credit is due, and I will never develop a customized debloater for a ROM without giving credit to it's respective developer. But, seeing as how these Debloater tools don't actually borrow anything developed ROM, and are simply customized to work better with them (rather than say a one-size-fits-all tool), I do plan on taking credit for developing them. So please don't steal them and re-use them in an app or one-click tool without giving proper credit, because I do take my own personal time to do this. Thanks.
REQ's:
1. ClockworkMod 5.5.0.4 (or later) or HTC Sync and HTC drivers installed on PC.
2. The ROM for which you are downloading the specific Debloater.
3. Android SDK installed and system variables are set properly on your Windows machine (btw this won't work for linux, that may come a bit later). Instructions for this are found in the quote below. Copied straight off'a Cyanogenmod Wiki. Adjust folder paths to your android-sdk folder as necessary.
Go to the Control Panel, and select the System Properties (Windows XP) or System (Windows Vista/7).
Select the Advanced settings;
Windows XP: Click on the Advanced tab.
Windows Vista/7: Click on Advanced system settings on the left.
Click on Environment Variables.
Under the "System variable" section, you will look for "Path". Double-click on it.
In the "Variable values" section, add at the very end the location of the tools & package-tools folder, with a semicolon separating these two paths from the rest, e.g. %SystemRoot%;C:\android-sdk\platform-tools;C:\android-sdk\tools
Click to expand...
Click to collapse
CWM RECOVERY INSTALL INSTRUCTIONS
1. Plug into PC via usb.
2. Boot phone into recovery.
3. Select Mounts & Storage, then select 'Mount /System'.
4. Download attached .zip file with your PC, unzip to wherever.
5. Run the .bat file with the 'CWM' ending. I put several pause commands in the file, so if you come up with some errors you can just copy them straight from command prompt and paste them here.
6. Reboot phone.
7. Done
HTC SYNC INSTALL INSTRUCTIONS
1. Plug phone into PC via USB, change connection type on phone to HTC Sync.
2. Wait for phone to find HTC Sync on PC.
3. Download attached .zip file with your PC, unzip to wherever.
4. Run the .bat file with the 'Sync' ending. I put several pause commands in the file, so if you come up with some errors you can just copy them straight from command prompt and paste them here.
5. Reboot phone
6. Done.
DISCLAIMER:
I claim no responsibility for anything this does lulz
No but seriously, this should work fine without causing any damage to your phone. I've tested it multiple times already. That being said, if it does f up your phone, I have no obligation to fix it. Use this at your own risk.
DOWNLOADS:
Bulletproof v2.5 Debloater & Debloater-Remover (All credit to XBoarder for this amazing ROM)
LINK to Thread
Stock Sense RUU (T-Mobile USA) Debloater & Debloater-Remover
DOWNLOAD
BeastMod 2.3 (Credit to XBoarder)
Coming Soon!
CHANGELOG:
Stock Sense RUU (T-Mobile) Debloater
v1.0 - Initial Release
Bulletproof v2.5 Debloater
LINK to Thread
NOTES:
Stock Sense RUU (T-Mobile)
After running the tool, you may get an error/fc message on your phone about the system app malfunctioning. This is normal. Just restart your phone (or if neccessary remove & re-insert the battery), and the messages will disappear.
Your tool looks real cool. Would it be possible to write a list of the programs it deletes?
realitysconcierge said:
Your tool looks real cool. Would it be possible to write a list of the programs it deletes?
Click to expand...
Click to collapse
Sure. Tell ya what, I'll include a README.txt file in the next update that lists which apps it removes.
This is my new tutorial/program for unlocking/rooting/backing up/flashing recovery on the Rezound.
V
V
V
Thanks to hasoon2000 for all of your help. You helped me improve many parts of this from start to now !!!!
^
^
^
Thanks for this! http://www.xda-developers.com/androi...er-and-easier/
For quick contact, Skype me, im "Fenguepay"
It is only v1.x so it is sure to have some errors.
If you find any, post them here If i don't respond to them then PM me.
I will try to find and fix as fast as possible.
This comes with all of the files that you will need.
Windows only.
You *may* need to install ADB here:
http://developer.android.com/sdk/index.html
You will need to download most of the stuff and install it once you get it.
For anyone who doesn't get any devices found before or after the reboot into fastboot. Make sure you have the HTC drivers installed. Get HTC sync from their site then simply open and run the installer then close the HTC sync process. It tends to interfere with your connection and you want the drivers not the program.
My program is now likely to brick your device. It hasn't bricked anyone's yet and probably won't ever. It's 99% noob proof.
DO NOT CHANGE THIS PROGRAM AND CALL IT YOUR OWN!!!!!!!!
SCAN FOR VIRUSES IF YOU WANT TO. THERE ARE NONE.
v1.0 Initial Release DONT USE EXE FILE DOESNT WORK. WONT EXECUTE THE ADB AND FASTBOOT CMDS
http://www.mediafire.com/?74332s36tjs335q
v1.2 Fixed many issues, tested with new device
http://www.mediafire.com/?hs2aurm5e81b1ke
v1.3 Added input options and a new menu. DO NOT USE. CRASHING ERROR!!!!
http://www.mediafire.com/?mty2n39u2ctkew7
v1.4 Fixed stability, did a few tweaks.
http://www.mediafire.com/?g32bzcf8g1eke9z
v1.5 Very refined, 99% working.
http://www.mediafire.com/?h11mllw3e67zvsq
v1.7 Added a utility and custom command menu, cleaned up menu. BIG DIFFERENCE!
http://www.mediafire.com/?5keazk7z6ew3cpl
Added custom command line. Use cust then command will be entered from the unlocker folder. Experimental*
v1.8 Fixed color issues, cleaned up root folder.
http://www.mediafire.com/?g4tpzr4b2smvpnb
Need help making gui.
v1.9 Fixed a missing "." on one line of code
http://www.mediafire.com/?zf7c0cd4cou7tqx
v2.0 Now redirects you to HTCdev.com/bootloader
http://www.mediafire.com/?ky6ezfk48v0y6l1
Future:
Executable file. No
Fancy GUI. Future
Walkthrough and Individual steps. Yes
Kernels, Recoverys and more.... Somewhat
*need help*
*side note* I want to make a gui version but I can only code bat. Would appreciate help :/
For quick contact, Skype me, im "Fenguepay"
EDIT---
Apparently this was not as easy to use as I intended. Here are some quick instructions to get you started.
1. Who is responsible for damage? You are. The answer to the question is "me"
2. You should now be on the menu. From here, if you are a noob/trying to unlock, do 1 and follow the whole process. It should explain it well, and i know it works i rooted a new device in around 5 minutes.
3. If you wan to flash another recovery, use the "util" option at the menu, select recovery and drop your recovery into the recoveries folder. From here you just type its name.
4. If you want to use a custom command that is launched from the root folder, use "cust" this makes it so you do not have to use "cd c:/Android". For ease of use.
5. If the process does not work, i know for sure there are other tutorials on xda and other sites. I am not a 100% pro at this.
Didn't u already have a thread with this ?
Sent from my Dinc... I mean Rezound
Just wanted to repost in development section
Sent from my ADR6425LVW using xda premium
fenguepay said:
Just wanted to repost in development section
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
Ahh ok I see now ... Hopefully this will help some noobs
Sent from my Dinc... I mean Rezound
Note: more content is coming regularly, so check back regularly! Also, post your input so this thread does not become buried.
As an initiative to kickstart development for the Galaxy Player 4.0, I have decided to put up this guide to try and attract more users to rom development. This, although, does not mean you can willy-nilly post up a rom including one mod, or a quick tweak. Making a rom involves a lot more than that.
The Developer's Code:
1. Your rom MUST be unique from the other roms.
This means you have to have a careful, well thought out rom. It must have several things differing it from other roms, something that makes it stand out. The last thing we need are 200 "me too" roms cluttering up development. Takes Klin's rom and mine, for example. We both have ICS themes, we both have tweaked our roms for performance, but they are both completely unique. Why? Because we didn't copy one another. We saw what the other had, and left it alone. I have an ICS theme, he has an ICS theme, but they are based on completely different themes. The biggest boo-boo in rom devving is copying someone else's rom/features/work. You will get kicked out unbelievably fast if you DO NOT follow this rule. To reiterate, the last thing we need is 200 identical roms. Make sure yours is unique from the others, and has a defining feature.
2. You must be willing to provide regular, consistent updates.
Maintaining a rom can be a full time job. You have bugs to deal with, features to add, and hours of work in which you only accomplish a small amount of work, due to some catastrophic failure. Last night it took me over 3 hours to fix a battery icon issue. Why? because I had almost space left in which to apply my fix, and if I did even one step wrong I had to reflash to correct the issue.
You should NOT release your rom once, and never look at it again. You should be willing to update it at least twice a month, if not sooner. I update mine several times a week, but that's because I have a lot of free time. Your mileage may vary, but try to hit for that mark. Too long wihtout an update and users will get bored/tired of your rom without anything new to spice things up.
3. You must be willing to provide helpful, friendly support.
At times, monitoring your thread can be frustrating. you may have someone complaining about an issue that was fixed several releases back, or someone who wants a new feature and keeps bugging you about it. It can be frustrating at times, but make sure you calmly answer everyone's questions in a fair manner. It can be extremely frustrating for a rom user to post up a question, and have it answered days later because the dev was "too busy" to monitor their thread. This, if anything, is almost more important than rom updates. Users love devs who actually converse and answer them, so be friendly, and keep your thread going!
4. ALWAYS ALWAYS ALWAYS give someone the apppropriate credit for their work.
It is the bane of the dev's existence: spending days/weeks/months of xyz feature/theme/rom, and have someone come along and snatch their work from them without as much as a "thank you". First of all, it will get you banned faster than any other offense out there. Secondly, it is one of the largest insults you can give someone. Our community is one that is supposed to share work, and most people do that freely, but you MUST give credit where credit is due. It is best if you ask someone's permission before you use their work, especially if it is something major (a huge theme for example). But even if you don't (and you should), at the very least list their username and what they did in your rom SOMEWHERE in your description.
5.You do not know everything.
After creating a rom, many people feel that they know much more then the "average" community, and that they are always right when it pertains the their rom. This could not be more wrong. The best way to improve your rom, is to listen to xyz person who knows more about a certain area than you do, and attempt to learn from that person. Everyone is skilled in a different area, so if you listen to your community, and assume they know best, you can learn and accomplish a lot evry quickly.
6. Google is your friend.
Do not assume that dev's know everything, and that they pull these features out of their heads. When in doubt, go to google. Always. There is normally a guide, or someone with your issue to help you out. As usual, make sure you give that person credit if you use their work.
So, to sum it up, Make your rom unique, be dedicated to your work, be ready to handle unexpected situations, ALWAYS give someone appropriate credit, listen to your community, and google a lot!
Not intimidated yet? ready to bring your amazing idea to the limelight? head on down to the section below to get started!
The Easy Way to Dev: Odin flashable packages.
Most people don't want to edit their rom on their computer. As a matter of fact, you can create a killer rom without even touching a computer to mod it. Up until I started theming, I working on my rom 100% on my device. This is the most tried-and-true method out there, and the one most likely to create the least drama. All you have to do is Pull the /system partition from your Player, and create a tarfile out of ti.
Prerequisites:
Samsung Device (system partition location may change with device type. This should be the same for US/INTL players)
PC running Ubuntu/form of linux (ubuntu is recommended for beginners)
ADB installed (actually not needed, but speeds up the process) (look below in resources for a guide)
appx. 300mb free on /sdcard
about 1 GB free on the Linux box
1. Apply whatever mods you want too
2. Open up a terminal emulator
3. type this in: dd if=/dev/block/stl9 of=/sdcard/factoryfs.rfs bs=4096
4. wait for it to complete (may take up to 10 minutes)
5. You now have a file called factoryfs.rfs on your internal sdcard
6. Hook it up to a computer and activate usb storage
7. copy factoryfs.rfs to whatever directory you want (home is recommended for simplicity)
8. Open up a terminal
9. cd to the directory of your file (if you placed it in home skip this step)
10. Type in "tar -H ustar -c factoryfs.rfs >packagename.tar"
11. Now you have a odin-flashable rom!
ADB users, simply run adb shell and type in the first command, then adb pull the file to the computer.
If you want to save space for a file sharing website (eg. mediafire, which has an upload cap of 200mb), simply Zip the file using 7-zip (set on ultra). You may have to do this on a windows machine.
Now this is even easier! simply flash the stock image in the link below with all the essentials included, and you can apply all the mods you want without having to ever go through dsidxa kitchen! Klin even fixed busybox for you! this way you can easily start from stock and work your way up to more advanced hacks.
http://forum.xda-developers.com/showthread.php?p=27973753#post27973753
The Advanced Users Guide: CWM packages.
Maybe you want more flexibility. Maybe you need to deodex your rom to mod some stock files, or zipalign to speed things up. This guide is for you people who need the more advanced options. It is harder, and you have a greater chance of messing things up, but you get to completely control your rom, even easily edit it on the computer! This guide is for advanced users only, or someone who is willing to spend a lot of time on trial and error.
Prerequisites:
ADB installed (Extremely helpful, and may to required)
Samsung device
Ubuntu/linux box
A bit of caution
Patience
1. Install Dsidxa Kitchen
2. Put your factoryfs.rfs in the necessary folder
3. cd to the directory you installed the kitchen
4. Type "sudo su"
5. enter your password
6. Type "chmod +x menu"
7. run "./menu"
8. you are now in the main menu of the kitchen.
9. There are many options, choode the one that you need!
Note: stay away from installing busybox using the kitchen. It installs a bad version of busybox which can make rom development a big headache for you!
10. There is a working folder in the kithcne directory, in there mod all the files you need.
11. When you are done, head into option 99 (create rom)
12. Run the interactive option
13.When you get to the update-script type, type "y" to install the newer type, which is required to flash a cwm zip in the Galaxy Player.
14. If you want to flash your rom using stock recovery, sign it. Else, leave it alone.
15. You can keep the normal name, or change it to what you want. If you are going to be flashing using stock recovery, make sure it is named "update.zip"
That is it! If you want to create a odin package out of it, simply flash the cwm zip, then follow the instructions above!
I will be adding on to this guide as time goes on, so make sure you ask pertinent questions below!
Resources/Additional Guides:
Install ADB:
http://forum.xda-developers.com/showthread.php?p=11823740#post11823740
Install dsidxa kitchen:
http://forum.xda-developers.com/showthread.php?t=1303311
4.0 base (essentials installed, just apply your hacks and you are good to go! thanks klin):
http://forum.xda-developers.com/showthread.php?p=27973753#post27973753
Easy theming guide:
http://androidforums.com/optimus-m-...guide-theme-guide-noobs-adding-lots-more.html
APK multi-tool (needed to theme):
http://apkmultitool.com/?q=node/5
Recommended hosting sites:
www.mediafire.com
Good Rom practices:
1. If you retheme, include screenshots! people love screenshots.
2. Make a logo if you can, it makes it easy for people to support your rom by adding it into their signature.
3. If you mod, make sure you can easily explain it to someone if need be. Messy hacks are not good in the long run!
4. Focus evenly on all parts of your rom. Some people love speed, others love features. You can focus on one or the other but try and keep it balanced.
5. If you create a custom script/init,d script/documentable file make sure you include comments in your mod so people can try and fix it if need be!
6. Make sure all the bugs are ironed out before release. People love fast releases, but if it is really buggy they may switch to another rom.
7. if you have exhausted all other methods of fixing an issue, or cannot work on it a lot in the opcoming days/weeks, release a beta version stating the bugs clearly. That way while you are gone, more experienced people can help you iron out the bugs.
8.Make sure it is easy for the person to obtain your rom. If they have to download another utlity or click through 30 ads, they may just want to use another rom than go through the hassle. Worse, they may mess it up, forcing you to help them troubleshoot.
9. Make sure you update utilities on your rom as soon as an update becomes availible. That way you get the fewest bugs, and as I said before, users love updates!
10. Even if someone's issue seems isolated, at least spend some time with them figuring out what happened so they can fix it. You never know, it may be the harbinger of a HUGE outbreak of issues.
11. Base your rom on an intl version. There is a fortunate "bug" that klin discovered that allows US users to use any intl rom without their home button breaking. Of course, that has a lot of asterisks, but if you will look below, I have developed a fix for that issue, which allows anyone with a "broken" home button to use it with the problematic rom!
12. Practice good rom devving. If there is a major issue that could be a pain, don't take the easy way/fix out. That always comes back to bite you later, as I have figured out. I once had a corrupt journal on my system partition, and did not want to go through the hassle of recreating my rom on a clean partition. So, I simply added a flag to have /system mount as rw if there are any issues. Sure enough, about 3 days later, I started having some filesystem issues, and had to completely rebase, because I did not have any backups.
13. ALWAYS keep backups. Just do it. Not just one, either. Keep at least three days worth of backups, just in case there is an issue in backup 1 and two, but it not in no. 3. This would have been hugely helpful to me in many cases, but I didn't want to "waste" the space. Guess what I did a few days later: spent a nice evening with linux fully recreating my rom from scratch. Just do it.
Fix home button issues. (useful if you use a rom seperate than a flasher's region) (developed by me)
I have finally, after a bit of luck and some know-how, determined a fix for the home button issue! This will work on ALL roms, not just this one, and will probably work for the 5.0 as well. This also means you can fully wipe data if you want, and simply apply my fix.
1. Navigate to /dbdata/databases/com.android.providers.settings
2.Optionally copy to a computer (easier that way)
3.Open it up in a sqlite editor (if you are doing this on the device, copy it to /sdcard and and then copy it back
4.Navigate to the locale/first section (there should only be one string in there
5.It should look like en_US if you have a US player, or en_GB if you have a UK/intl player
6.Change the string to the language/locale you use (if you are INTL you can merely change it to xx_GB, where xx is your language. If you are US, just perform the same steps, but change the last part to US)
7. commit/save the file and copy it over the old one
8. Reboot, and your home button *should* be fixed!
NOTE: I have not personally tested this. It has a 99% change of working, but I have yet to completely verify it.
NOTE: after you replace the file, android may go a little haywire (wifi disconnects, forgets password, advanced reboot option unavailable, etc.). THIS IS OKAY. Simply reboot, and it will all be back. Do not change any settings after copying until it reboots, as it may possibly break the fix
NOTE: I cannot provide a downloadable file, as that file contains all of your system settings, and if you use mine, my settings will be applied, which could be pretty bad in some cases.
NOTE: this has no chance of bootlooping or bricking your device. At absolute worst, you have to set up a few settings/restore from a /dbdata backup. There is almost no risk involved.
Potential fixes for potential issues:
1.Bluetooth breaks. The main cause of this is if you install supercharger and nullify. Simply unullify and verify it is remove from build.prop, and you are good to go!
2. Home button breaks. (see above )
3. Root/busybox breaks. It's kinda messy, but if you absolutely HAVE to, simply reroot. That should fix it in a pinch. This is a classic case of keeping good backups. I have had to spend an entire afternoon redoing my entire rom because of my lack of recent backups. If you have the space, keep them. I have more than once managed to create a stopgap solution in my rom just to have some weird issue pop up again, and again. Just do it.
I LOVE you, man.!!
Hanthesolo,
Very good achievement, we all have to learn from your good sharing.
Congratulations man
rgds
I am really happy you guys like this! I will continue to add to it as time goes on, so expect even more content!
Sent from my EtherealPlayer.
New content up! also notice the link to the stock rom klin made so that you never need to go through a kitchen to get your rom started!
Has anyone used this yet? successes/failures? make sure you give me feedback so I can make this better!
Yet mre content up! Could this be possibly stickied? I know it's a little rough right now, but noone replies to this thread as there really is nothing to reply TO. I have worked hard on this and would hate to see this information go the way of the dead threads.
Thanks for this info man, making roms for my old evo and just stacking up on guides and any kind of reading material that I can utilize for my advantage. So, this will be helpful lol. I'll be checking back every so often on anything new added, but thanks again bro. Thanks given! Feel Encouraged!! lol
iAMsalm said:
Thanks for this info man, making roms for my old evo and just stacking up on guides and any kind of reading material that I can utilize for my advantage. So, this will be helpful lol. I'll be checking back every so often on anything new added, but thanks again bro. Thanks given! Feel Encouraged!! lol
Click to expand...
Click to collapse
Glad you enjoy it, this forum is the abandoned, dusty wasteland of xda, so I wrote this guide to (hopefully) stimulate development a bit.
hanthesolo said:
Glad you enjoy it, this forum is the abandoned, dusty wasteland of xda, so I wrote this guide to (hopefully) stimulate development a bit.
Click to expand...
Click to collapse
I know it definitely feels like that from time to time, but that's a byproduct of the nature of our devices. There's ridiculous money in selling someone a shiny new crippled phone with a horrific contract that will never get updated. You won't see a jawdropping ad on TV featuring a Galaxy Player because there's just no money in it. I'd love to have the T-Mobile girl holding my phone while wearing a pink leather riding suit(her, not me). That ain't happening.
I'm pleased and more than a little shocked that some new roms have come out in the past month thanks to this guide. I wanted a Android powered phone without the contract. I wanted an iPod Touch without all the bull**** that comes from being tied to Apple. Thanks to XDA my device fast, sexy as Hell, and does everything I want.
The only thing that makes me sad is that a year from now I probably won't be able to buy a Galaxy Player 4.0 v2 because there's just too much money to be made from contract only devices.
Thanks for this guide. It help me for begin android development.
GalaxySWifi4 said:
Thanks for this guide. It help me for begin android development.
Click to expand...
Click to collapse
I hope you have fun beginning development! It really is a lot of fun once you et past the basics.
Gswifi, I never replied to you, but your speech was so awesome, that I want to put it in the OP .
If you want me to update the OP with an equivalent for ROM compiling (I know that I had a hard time figuring out just WHERE the folders to go, so we need a good guide...), chime in your support please!
hanthesolo said:
If you want me to update the OP with an equivalent for ROM compiling (I know that I had a hard time figuring out just WHERE the folders to go, so we need a good guide...), chime in your support please!
Click to expand...
Click to collapse
@hanthesolo
do you have some knowledge about kernel compiling, so you could hel me?
hanthesolo said:
If you want me to update the OP with an equivalent for ROM compiling (I know that I had a hard time figuring out just WHERE the folders to go, so we need a good guide...), chime in your support please!
Click to expand...
Click to collapse
please do
I understand early nothing about this advanced stuff of making ROMs, even more about make Kernels XD. But I want to experiment some little things to learn by myself step at step. But... I cannot start... I'm in CM10.1 with Koala's Kernel and I can't make the factoryfs.rfs file doing this: dd if=/dev/block/stl9 of=/sdcard/factoryfs.rfs bs=4096 in Terminal Emulator because /dev/block/stl9 doesn't exists. With ADB I have the same error.
Is this due to this ROM is not stock or something like this? Or only I have to create this folder or change it by other...
---------- Post added at 02:55 AM ---------- Previous post was at 02:37 AM ----------
I'm trying to do this but without if=/dev/block/stl9. I don't know if I'm doing well...
How about some info on modifying or tweaking already compiled roms?
Say you want to remove some of the apps included with CoolDevXYZ's rom or modify some of the settings pre-install (e.g. build.prop tweaks, etc.). How do you tell the kernel these changes are intentional, not the result file corruption, infection or something?