This a simple and quick guide for everyone who wana make or just modify their own HTC DESIRE ROM's.(Rooted ones)
For example you downloaded a nice ROM from one of devs here, but they removed some application that you cant live without. Now you dont need to beg them to add those files back, simple add them your self and flash your rom.Missing APK's you can get simple by downloading any stock rom, than extract them and put them in your new ROM.
After you extracted files provided (c root recomended), you will see 2 maps
"Sign ROM" and "tools"
Signing ROM's:
After you modifed your ROM zip file, simple put it in "Sign ROM" map, and rename it to update.zip.Than run "Sign.bat" After the process is done you will get another zip called "update_signed.zip" which you can now put to your SD card and your ready for flashing. Note:JAVA SDK files are included, you only need to have normal java installed.
http://img99.imageshack.us/img99/2921/signedrom.jpg
Pushing recovery files from windows:
Now to flash your ROM you dont need linux anymore, simple enter recovery (Power button+back, than select recovery...), and than in the map "tools" run recovery-windows.bat. Than you will get standard screen where you can flash your roms, partition SD, clear data and so on..
NOTE: You need to have HTC Sync driver installed or your phone wont be detected (you can get them from HTC)
http://img213.imageshack.us/img213/1894/pushfiles.jpg
If you have any questions, suggestions or if i wrote something wrong i will be happy to answer/corect them.
http://hotfile.com/dl/43311449/92d9ee6/Desire_Tools.exe.html
http://www.megaupload.com/?d=JNI68MWZ
http://rapidshare.com/files/388849647/Desire_Tools.exe.html (Thanks pympster for link )
http://www.robertolsen.no/desire_tools.rar
(Thanks GeoTrail for link)
would this tool work for the HTC Legend aswell?
For signing roms yes, for pushing files not sure if Desire and legend use same files..
Ok this one is simple, but this is only how to add/delete several apps.
How about going little bit more deeper?
Well if you wana go deeper, you can download costom kernels with overclocks or low volatege and replace the ones in rom, or those circle battery mods or costom boot sounds and so on...Basicly your replacing/modifying original files. But this is just quick basic guide for basic stuff, let real ROM developing and costomizing to the developers who are good at it.
As far as hardware support goes is it the kernel that provides everything? Basically if I take an N1 rom (like cyanogen 5.0.6) and change to a desire kernel, is it likely to just work perfectly or are there other bits in the ROM that are likely to need changing?
Of course you can just use dsixda's Kitchen which is cross-platform and quite straightforward to use.
You just add the update.zip file you want to change, remove/add any apps you want and make any advanced changes you want too.
Select Build ROM and it'll create the new update.zip that you can flash to phone.
I've used it on my Desire without problem for adding/removing apps.
Well that kitchen is nice, but still..you need to downlaod virutal machine to make it run under windows or Cygwin tool than download JAVA SDK..setup lots of things.
My point of this thread was just vey basic and simple way to quickly add/remove/costomize files from ROM, without installling and downloading lots of tools, and quickly install it on Phone and test.
Sorry, I wasn't meaning to undermine your work. No doubt you've spent a lot of time creating this and trying to contribute to the community. It's far more than I can say for myself.
I was just pointing out there's something already out there, and more capable than this.
It's definitely good to see people helping out the members and this is definitely something useful
Everything is cool TheAshMan, and thanks for you link, im sure some enthusiastic people will try some advance things like that. But even my self im not big expert about Linux and phones, i do have great knowledge about windows and computers, but dont have much time for this area.
Screen shots on how to use this would help, I've come from cooking my own WinMo ROMs and wuld like to give this a try if possible
Also, as I use W7 x64 is it best to run the .bat files as an admin? Had issues using Windows methods in the past so have been using Linux to get rooted
I'm also using Windows 7 x64.
About running bat's as admin its not necessary unless you have some kind of UAC high settings, or running on some kind of limited user account. I never run this bats as admin and they work fine.
Basicly download some stock rom, or someones rom. And simple add or remove files inside rom.zip/system/app/
If you dont like facebook for example, just remove Facebook.apk and facebook.odex(if its present).
After your done with that, rename ROM to update.zip and put it in the folder
C:\Desire Tools\Sign ROM\ and excecute "Sign.bat" , and it will create signed rom with name update_signed.zip.
http://img99.imageshack.us/img99/2921/signedrom.jpg
This is just some base, im not gona explain you about ROM deodexing, framework, boot images kernels and stuff, because im not expert at this.
Now you can put that file to root of your SD card.
Now you can test it on your phone.
Shut down your phone. Turn it ON while holding back button.You will see Bootloader selected, press power button again. Than Recovery will appear, you can navigate down with volumen UP AND DOWN and select Recovery and press POWER button again to select it.Phone with Red triangle will appear on your phone. Now go in map C:\Desire Tools\tools and excecute "recovery-windows.bat"
http://img213.imageshack.us/img213/1894/pushfiles.jpg
And on your phone you will get that screen with green letters where you can select to 'Flash zip from sdcard' ,where your signed rom will appear.(You need to wipe data before from the same menu)
I hope i made some thing clearer im writing this from work so dont have much time
Right, got a ROM and added 2 .apk files to the /system/app folder and now got a signed_update.zip...is that it? They'll be on the device from the start?
Seems to simple to me!!
How can you add a new radio? Or change the version number in About phone>Software?
Yea thats it. About those other things..Google is your friend...
edit mate
when i flash it says:
E: Can't find update script
rom.zip/META-INF/COM/google/android/update-script
Did you touch that in ROM? If you didint, than you removed something that you shouldnt.
Can u also remove apps from rom that you don't like by this method.
-------------------------------------
Sent via the XDA Tapatalk App
Yea, thats the all point of everything i wrote here. Very simple way of very quickly removing apps that you dont want from the rom before flashing it.
Also, you need to watch out, and to a bit experementing. Because sometimes if you remove some crucial app, you will start getting random crashes of applications or random bugs. Allways make a copy of original rom.
For example if you remove HTC-IME.apk, you wont have any kind of keyboard in the rom. Making it un-usable
Somebody already asked how to add radio update, is it maybe included in Modaco r3 rom(the one without apps2sd and modaco additional stuff)?
Tnx for help
Related
I hate to make a thread on this but would like to get started soon with learning how to root roms and add the kernel for multitouch and tethering. This is more for my personal use since I just want a stock rom with all the root benefits like jf use to and theses are the questions I have.
1. Will I have to take the update.zip file and extract everything and modify it then resign and I'm done?
2. I read some info on adding busybox and root which seem easy but when I run the chmod command and such everything will be through adb and the files will be on my pc so do I just make sure its all in the right directory and file path?
3. Where are the wallpapers stored in builds along with animations I will be looking into the framwork/framework-res.apk later but still curious
4. The modified kernel for tethering and multitouch is located where along with the market.db file?
5. What is meta.inf and how easy is it to make the cpu 528mhz standard also not sure what BFS and ASOP are haven't been keeping up.
P.S. I would really appreciate some help on this and I don't mind reading if this information is somewhere else so please provide a link and as always gotta show love to those who started this like JF, Hakuro, Cyanogen, Drizzy, and many more like daproy and kornub did a lot of helping.
I hate to make a thread on this
Click to expand...
Click to collapse
You mean you hate starting threads in the correct place?
Thats a fine line here. Although it is a question, it is specifically a development question. Its not a which rom do i choose?
Although android is "open source" these people dont give a **** about people trying to learn how to develop. They will pull the google line or something.
yeah me 2
Trying 2 learn
Im a noob, so I can only answer two of thosew questions
1. Anytime you modify your update.zip you will have to resign before trying to flash it onyour device.
5b. BFS: Brain **** (simple) Scheduler, something to do with the priority of running proccesses or something http://en.wikipedia.org/wiki/Brain_Fuck_Scheduler. AOSP stands for Android Open Software Project, which i believe is just googles standard rom really (but I may be wrong)
I recommend you try out this rom though, kind of like JF but for Donut http://forum.xda-developers.com/showthread.php?t=538456
Very Sorry, double post
Thanks! I'm actually using that rom and its what has me so interested in this cause I hate having to flash another update.zip to get the full root benefits when JF just made everything available in one nice package but looks like I will just have to go through trial an error unless I get some more feedback cause switching between cyan 4.1.11.1 and JF1..51 is killing me and taking up space on my card.
With my little to no knowledge, replacing the boot.img and some files in system/bin with the ones provided in theofficial expansion pack should give you all that you need. With no extra apps.
yeah me 2
Yeah me too
Just throwing an idea out there, and since it's for developers (specifically people who make their own recovery images) I assume this is the right section.
Since we have 'control' over the recovery image on our phones, would it not be possible to add a little script to an update.zip that a suitably modified recovery image could extract and run to interactively prompt the user for various Rom options? I'm thinking specifically of kernel choices, but it could be extended to almost anything that needs to be done prior to booting the installed image.
Imagine installing a rom, and during the install you got a little menu like this:
1: RamHack, BFS Kernel
2: RamHack, CFS Kernel
3: No-RamHack, BFS....
etc...
inefficient, it adds extra baggage to rom, and more things can go wrong. what would you rather downlaod a 90mb file or a 110 mb file.
Which would you rather download, one 110MB ROM or 2 90MB ROMS?
I'm pretty sure there's more than a few people who'll download different variations of the same ROM so they can see which is faster, how much easier would it be to just download one thing and then choose which options you want in there without downloading anything else.
I believe it is entirely possible. As a matter of fact, I was working on a ROM project that would have an interactive installer from the update.zip that would selectively install different features, apps, customization, themes, etc., based on the recovery menu application. It would use a lot of the /cache for temp space, though, as the installer application and its resources and configuration file, and later, the necessary parts of the ROM itself, would need to be unzipped before the install can run, if I recall correctly.
Does anyone have a good link to a reference for the command syntax for the /META-INF/com/google/android/update-script file? I'll go search for it in a few moments myself. I could probably make a simple ROM installer that chooses between ROM X and ROM Y based on a key input, as a proof of concept. I'll test it myself, I don't really mind half-bricking my device for science. (As long as I don't need to touch the SPL/Radio, that is.)
Update: Some creative searching finds me this:
JesusFreke said:
Assuming you mean update-script in an update.zip update, you will need to either look at existing update-script files for an example of the syntax, or look at the source of the recovery program in the android source
Click to expand...
Click to collapse
There's also a "make-update-script.c" file I'm seeing here and there, I'm trying to find the file in the Android source.
Update 2: From install.c at donut from cyanogen's android_bootable_recovery:
Code:
#define ASSUMED_UPDATE_SCRIPT_NAME "META-INF/com/google/android/update-script"
#define ASSUMED_UPDATE_BINARY_NAME "META-INF/com/google/android/update-binary"
and in commands.c, toward the bottom at register_update_commands is all the commands defined, and above that are all the functions they carry out.
sorry about that deicist i was sleepy when i wrote that so i must have been cranky yea i guess that is a fine idea, with just 30 more mb you have like 300mb worth of stuff. and you can pick which 90 mb you want.
markolo25 said:
sorry about that deicist i was sleepy when i wrote that so i must have been cranky yea i guess that is a fine idea, with just 30 more mb you have like 300mb worth of stuff. and you can pick which 90 mb you want.
Click to expand...
Click to collapse
Well, on the 32B platform with the Death SPL (my phone) we have the following partitions of the internal NAND memory (mtdblock*) from the df and mount command:
NAND 3: /system 92160kb - OS partition, static and read-only
NAND 5: /data 91904kb - User, system config, app config, and apps (without a2sd)
NAND 4: /cache 30720kb - OTA cache, Recovery/update config and temp
And I'd assume NAND 1 and 2 are the kernel, ramdisk, and bootloader config.
So the ROM wouldn't exceed 92MB installed (most leave some room in /system for hacks and updates). And the update process doesn't ever really "flash", per se; it just formats, copies files, and sets permissions and initialization configs, like Windows or Mac.
So the files that are common to the different ROMs being packaged don't need to be duplicated, only the ones that are changed (like a boot.img, or 32A/B compatibility, or different apps). The update script and chooser menu will decide which files to copy. Meaning the ROM package in and of itself shouldn't really need to exceed 128MB, even if choosing from a wide variety of platforms. And upon installation, the system might take less than 32 MB.
yeah, what he said ^
The scenario I was thinking about specifically was SuperD. If you look here:
http://forum.xda-developers.com/showthread.php?t=613809
There's 8 different downloads there. How many files are actually different between those 8? I guess the themes mean a lot of application files are different (due to having different resources in them) but the underlying framework files will be pretty much the same I think.
Deicist said:
yeah, what he said ^
The scenario I was thinking about specifically was SuperD. If you look here:
http://forum.xda-developers.com/showthread.php?t=613809
There's 8 different downloads there. How many files are actually different between those 8? I guess the themes mean a lot of application files are different (due to having different resources in them) but the underlying framework files will be pretty much the same I think.
Click to expand...
Click to collapse
I could download them all, and find the differences of each. It would be cool if a ROM like this were available in a single download, from which you would choose the content from the device before flashing.
Also, inspired by talking about this, I wrote up a guide on the update-script in the package file. It's still not finished, but it'll be the only guide available for that syntax yet (trust me, I couldn't find one myself ). Link's in my sig.
I'm surprised that nobody's mentioned the Droid... the sholes.info rom (now called droidmod) have used a .tgz archive instead of a .zip, the .tgz installs have always allowed this customization, droidmod makes one of the most common recovery's AND rom's. (SPRecovery/Droidmod).
It give you the option to choose what launcher to install, what theme, what apps to remove.
page here: http://droidmod.org/news/droidmod-v1-0-is-out/
how big of a ROM are you thinking about?
There are roms (WG etc...) that offer more than one kernel as update.zip you can flash over an existing installation of your rom instead of adding all the stuff to one big file. also you can download themes for several roms/for metamorph.
so why would you want some big install script instead of just downloading the files you like and flash it?
jmhalder said:
I'm surprised that nobody's mentioned the Droid... the sholes.info rom (now called droidmod) have used a .tgz archive instead of a .zip, the .tgz installs have always allowed this customization, droidmod makes one of the most common recovery's AND rom's. (SPRecovery/Droidmod).
It give you the option to choose what launcher to install, what theme, what apps to remove.
page here: http://droidmod.org/news/droidmod-v1-0-is-out/
Click to expand...
Click to collapse
Is the Droid's recovery image capable of running on the G1, and/or is it open-source enough to be cross-built to the G1? If so, we could port it here. Only problem there though, is that all the roms are in update.zip format for the G1 already, we'd need to make it dual-compatible if we don't want to split the community and annoy generally everyone ("My rom only supports TGZ recovery!" "ROMs are in ZIP format, and I will not make a TGZ one for those unfortunate enough to use the other Recovery!")
domenukk said:
There are roms (WG etc...) that offer more than one kernel as update.zip you can flash over an existing installation of your rom instead of adding all the stuff to one big file. also you can download themes for several roms/for metamorph.
so why would you want some big install script instead of just downloading the files you like and flash it?
Click to expand...
Click to collapse
Well, for one, devs need to host one file only, and users need to download one file only. The file won't be much bigger or more complex at all, really. And the way things look on the recovery side, we could probably put a selection of themes in with the updater and patch them in post-install with a Metamorph script straight from recovery. That way, the rom is as you want it out-of-the-box, no multiple reboots, etc.
Also, those scripts that usually run on first-boot, like zipalign, dexopt, apps2sd etc. should run from the recovery environment, instead of before the Android bootanimation (I do get tired of hearing "This ROM will take a LONG time on the first boot. If it's stuck at the G1 screen, just wait 10-30 minutes.")
So what would you rather have, one single ROM (G1_Android_ROM_v1.17.zip) for each version released,
or six different ZIPs to flash (G1_Android_ROM_10MB_CFS.zip, G1_Android_ROM_Greentheme.zip, G1_Android_ROM_Bluetheme.zip, G1_Android_Nowipe_GApps.zip)?
Would you rather select what you want to include at flash (and be able to change things like themes or features after flashing), or have 20 different files to choose from, wiping and flashing on each?
I am aware of the no-wipe upgrades for many ROMs, but they can get confusing (I once flashed a CFS_10MB.zip that was for a Hero ROM, stupidly thinking that it might have been for the Eclair that I just downloaded.) Needless to say, I had to wipe and reflash. Again.
TylTru said:
Is the Droid's recovery image capable of running on the G1, and/or is it open-source enough to be cross-built to the G1? If so, we could port it here. Only problem there though, is that all the roms are in update.zip format for the G1 already, we'd need to make it dual-compatible if we don't want to split the community and annoy generally everyone ("My rom only supports TGZ recovery!" "ROMs are in ZIP format, and I will not make a TGZ one for those unfortunate enough to use the other Recovery!")
Well, for one, devs need to host one file only, and users need to download one file only. The file won't be much bigger or more complex at all, really. And the way things look on the recovery side, we could probably put a selection of themes in with the updater and patch them in post-install with a Metamorph script straight from recovery. That way, the rom is as you want it out-of-the-box, no multiple reboots, etc.
Also, those scripts that usually run on first-boot, like zipalign, dexopt, apps2sd etc. should run from the recovery environment, instead of before the Android bootanimation (I do get tired of hearing "This ROM will take a LONG time on the first boot. If it's stuck at the G1 screen, just wait 10-30 minutes.")
So what would you rather have, one single ROM (G1_Android_ROM_v1.17.zip) for each version released,
or six different ZIPs to flash (G1_Android_ROM_10MB_CFS.zip, G1_Android_ROM_Greentheme.zip, G1_Android_ROM_Bluetheme.zip, G1_Android_Nowipe_GApps.zip)?
Would you rather select what you want to include at flash (and be able to change things like themes or features after flashing), or have 20 different files to choose from, wiping and flashing on each?
I am aware of the no-wipe upgrades for many ROMs, but they can get confusing (I once flashed a CFS_10MB.zip that was for a Hero ROM, stupidly thinking that it might have been for the Eclair that I just downloaded.) Needless to say, I had to wipe and reflash. Again.
Click to expand...
Click to collapse
You could just have flashed the original rom without wipe.
Would be a step forward if you could simply put roms and additional files in folders... maybe even whole zip files containing some updates and an xml like file to describe them. This would guarantee compatibility with earlier boot images (just unpack the updates in the zip). Tar might work better than zip as it is not compressed thus faster afaik.
http://droidninja.com/?p=26334
We got ninja'd. Apparently the Droid Does exactly this.
So let's get to work on porting it! Like this comment says, I'm working on finding the source code to a good Droid recovery image (sadly Droid hasn't its own forum here), and if it's closed source, I'll get on reverse-engineering a .tgz rom to see exactly how it works.
TylTru said:
http://droidninja.com/?p=26334
We got ninja'd. Apparently the Droid Does exactly this.
So let's get to work on porting it! Like this comment says, I'm working on finding the source code to a good Droid recovery image (sadly Droid hasn't its own forum here), and if it's closed source, I'll get on reverse-engineering a .tgz rom to see exactly how it works.
Click to expand...
Click to collapse
This is pretty awesome. I was going to say, we could easily run bash scripts but this is so much better.
This needs to be merged with both Amon_ra's recovery and the new 2.x based recovery...
As lately some people are asking me about ROM porting I decided to create this new thread where we can share knowledge about this hard task.
Please note this is a Dev talk thread, so DON'T ASK about fixing a particular ROM problem here. Also don't ask questions like "My phone is bricked! please help!". This IS NOT the appropriate place for it. There are plenty of other threads to help you out.
Also note that this is not a step by step guide (and not a guide at all), it's just a point where you can start from. Android is a very complex system and there are many things I don't know yet. So, research and hard work is what you need to learn it deeply. My first tip is Google really works. Don't be afraid to search
Ok, to the basics. Porting a ROM is no simple task. It requires advanced understanding of how android works and how it is organized. Previous Linux/Unix knowledge helps A LOT. As android is based on this O.S. there are many similarities between both. In fact many ppl consider android to be a kind of linux distro.
The very first task to port a ROM is finding a device which is compatible with your own. For example Defy/Milestone2. Then you are going to choose a ROM to port to your device.
As our devices (Milestone2) have a locked bootloader we now need to find a system image that have a compatible kernel with the ROM we are trying to port. This is mainly based on trial and test and takes a long time. You'll be ending flashing your phone several times with RSD Lite. You should learn how to use MotoAndroidDepacker and how to create a fixed SBF.
The basic procedure to try that:
1. Open original ROM update.zip and remove any files/commands that flashes boot/devtree/recovery/anything.
2. Install this new file on your phone via CW Recovery.
3. Boot into bootmenu and enable ADB so you can read logcat while phone boots.
4. Choose Boot/Normal. If your ROM uses 2nd-init you will need to place/edit/adapt bootscripts into bootmenu 2nd-init folder.
5. Check logcat for errors:
- If you're getting HAL errors you're going to need a new kernel;
- If you can start android without getting HAL errors but still getting errors and bootloop on android animation you should try to replace libs with appropriate original ones.
6. Once you are able to boot android you should test it's features to see what needs to be fixed.
This is what I have to say for now. The thread is now open for discussion.
At this week, motorola has just pushed the GB official update for Droid 2 and Droid 2 Global....
Can i try to port this new rom to milestone 2 and after a success boot, fix the radio..??
I was asking that, because some people has success on port CM7 to milestone 1, when it originally maked for droid 1...
tks a lot..!!
jorgebaruchi said:
At this week, motorola has just pushed the GB official update for Droid 2 and Droid 2 Global....
Can i try to port this new rom to milestone 2 and after a success boot, fix the radio..??
I was asking that, because some people has success on port CM7 to milestone 1, when it originally maked for droid 1...
tks a lot..!!
Click to expand...
Click to collapse
It may be possible, but you'll have a hard time fixing the baseband.
You may have to mod the init.rc scripts and find the right radio binaries (rild is one of them) and drivers.
Ask those ms1 people for help, if they are still with the same phone...
Sent from my Milestone 2 XDA App
I don't know if this will be relevant or not.
I wanted to know if to do any of this, having a Linux distro as OS a must or can I try my hands at it on a windows based machine. I mean I'm sure that a Linux distro will give certain advantages (as Android is based on UNIX/Linux) but can we get things to work a 100% on windows.
If yes, then will someone be kind enough to get give the list of all softwares etc. which will be required to do the job on Windows machine as well as a Linux machine.
I do know a few softwares but I'm not sure if I have an exhaustive list. I would like to learn and try and at least be able to modify in bits n pieces to begin with.
I apologize if this wasn't supposed to be asked in this thread.
The only thing i can get from SBF is a bunch of smg files.
But the only ones i can open are
preinstall.smg
CG39.smg
Is there a way to open/see the rest?
2)
Im trying to modify the CM7 rom, what boot does it use? 2nd-init or 2nd-boot?
i guess it is second-init. but not sure
thanks a lot for this !!!
WeeDv2 said:
The only thing i can get from SBF is a bunch of smg files.
But the only ones i can open are
preinstall.smg
CG39.smg
Is there a way to open/see the rest?
2)
Im trying to modify the CM7 rom, what boot does it use? 2nd-init or 2nd-boot?
Click to expand...
Click to collapse
SMG files are disk images of certain partitions of your flash memory.
You can only open CG39.smg and preinstall (CG66.smg) because they are the only images in ext3 format. The rest of images may be on ramdisk format or some proprietary format. For more details on partition codes take a look here:
http://and-developers.com/partitions:cdt
You may be able to open and see contents of other partitions but the only one that matters aside from system and preinstall is the boot partition (CG35.smg), which contains the init scripts we should mod in order to make they work with 2nd-init. Boot partition is in ramdrive format. More details here:
http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
http://elinux.org/Android_on_OMAP
It is easier to unpack boot image using Dsixda's Kitchen here:
http://forum.xda-developers.com/showthread.php?t=633246
Edit: To see what boot your CM7 uses just go inside /system/bootmenu/config and look for a file called default_bootmode.conf. That should be the boot method used. It's normally 2nd-init.
sahilarora911 said:
I don't know if this will be relevant or not.
I wanted to know if to do any of this, having a Linux distro as OS a must or can I try my hands at it on a windows based machine. I mean I'm sure that a Linux distro will give certain advantages (as Android is based on UNIX/Linux) but can we get things to work a 100% on windows.
If yes, then will someone be kind enough to get give the list of all softwares etc. which will be required to do the job on Windows machine as well as a Linux machine.
I do know a few softwares but I'm not sure if I have an exhaustive list. I would like to learn and try and at least be able to modify in bits n pieces to begin with.
I apologize if this wasn't supposed to be asked in this thread.
Click to expand...
Click to collapse
Don't worry, this is the right place
As for your question: yes you can work in windows if you like, but using at least a Linux VM is more productive. I don't have a full list of applications to give you, as different mods may require different tools, but I advice you to have at least:
- Notepad++ (essential for editing text files and keeping linux end-line format);
- dsixda's Android Kitchen (http://forum.xda-developers.com/showthread.php?t=633246)
- 7zip (or some other compress tool you like)
- Moded putty for ADB as working with windows command prompt really suck (http://forum.xda-developers.com/showthread.php?t=803225)
- Oracle Virtual Box (if you are going to use linux VM).
r2beta0 said:
SMG files are disk images of certain partitions of your flash memory.
You can only open CG39.smg and preinstall (CG66.smg) because they are the only images in ext3 format. The rest of images may be on ramdisk format or some proprietary format. For more details on partition codes take a look here:
http://and-developers.com/partitions:cdt
You may be able to open and see contents of other partitions but the only one that matters aside from system and preinstall is the boot partition (CG35.smg), which contains the init scripts we should mod in order to make they work with 2nd-init. Boot partition is in ramdrive format. More details here:
http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
http://elinux.org/Android_on_OMAP
It is easier to unpack boot image using Dsixda's Kitchen here:
http://forum.xda-developers.com/showthread.php?t=633246
Edit: To see what boot your CM7 uses just go inside /system/bootmenu/config and look for a file called default_bootmode.conf. That should be the boot method used. It's normally 2nd-init.
Click to expand...
Click to collapse
Thanks again r2beta
thanks r2beta0
- Notepad++ -- got it
- dsixda's Android Kitchen -- downloaded (need some link for a how-to on its usage)
- 7zip -- got it
- Moded putty for ADB -- got it
- Oracle Virtual Box -- can't install Linux on my system as this is a work machine
dunno if I can do without the last option.
sahilarora911 said:
thanks r2beta0
- Notepad++ -- got it
- dsixda's Android Kitchen -- downloaded (need some link for a how-to on its usage)
- 7zip -- got it
- Moded putty for ADB -- got it
- Oracle Virtual Box -- can't install Linux on my system as this is a work machine
dunno if I can do without the last option.
Click to expand...
Click to collapse
Oracle Virtual Box is an application that lets you run an operational system on a virtual machine, in other words, it doesn't install linux on your real computer. It's a very useful tool that I use everyday. Google for it and learn a bit, you won't be disappointed. About kitchen: the link I provided was download + guide. Read it again. If necessary read the full thread.
r2beta0 said:
Oracle Virtual Box is an application that lets you run an operational system on a virtual machine, in other words, it doesn't install linux on your real computer. It's a very useful tool that I use everyday. Google for it and learn a bit, you won't be disappointed. About kitchen: the link I provided was download + guide. Read it again. If necessary read the full thread.
Click to expand...
Click to collapse
I know a bit about virtual box but as I said I'm not allowed to have softwares not approved by the IT team to be present on the system. Though I can get away with small things like notepad++ and 7-zip, having virtual box on my system may raise some eye brows.
I'm trying to arrange an alternative system.
Me neither. I must do almost everything at home, and at this very moment I simply don't have any free time. I'm afraid you're not going to see me here very often anymore (maybe in a few months? a year? well, it might be a bit too late for milestone2...)
hi. Have a question, I want to remove baseband from a flashable zip (lets say, CM7 from Tezet) , is it posible? I dont know where to look for it (baseband). Thanks!!
Baseband is located in \system\etc\motorola\bp_nvm_default\
But don't remove it, just replace it with files from ROM, which have baseband you want.
---UFO--- said:
Baseband is located in \system\etc\motorola\bp_nvm_default\
But don't remove it, just replace it with files from ROM, which have baseband you want.
Click to expand...
Click to collapse
Ok thanks for the info.
Sent from my A953 using XDA
Hi All,
Just a quick question. I have ported Paranoid Android 2.10 to MS2 but the problem I am facing is that Reboot goes through Bootmenu and I have to choose reboot from Bootmenu again.
Any inputs?
Thanks in advance
Megalith27 said:
Hi All,
Just a quick question. I have ported Paranoid Android 2.10 to MS2 but the problem I am facing is that Reboot goes through Bootmenu and I have to choose reboot from Bootmenu again.
Any inputs?
Thanks in advance
Click to expand...
Click to collapse
I meant to get to it last night, but I was tired after work and fell asleep watch tv. Eventually, later tonight, I'll be uploading PA for MS2. Check my Defy PA thread in 12-14 hours cause I'm about to go to work and I'm not gonna feel like making a MS2 PA thread or updating my Bravo PA thread -- but the Defy Thread is always up to date when I put out new roms.
Also, I'm looking to get either a Defy or MS2 -- I've heard that there's 3G issues with AT&T users (which I am) with the MS2 -- Apparently the MS2 has different 3G frequencies than AT&T. Are there any AT&T MS2 users who are knowledgeable about that? While I can deal with no 3G, edge only, calls only -- I need to make sure I can at least do that before I commit to something.
I'd rather have the MS2 because I want a hw keyboard and I don't have the $300+ to try and get a Photon Q LTE from eBay (and I don't have to change up my repos if I get a MS2). If anyone here knows of a phone that's AT&T compatible, Defy code compatible, and has a keyboard, please let me know.
Thanks.
//Normally I'd post the latter half in the Q&A section, but ya'll don't have one so I'm just gonna piggyback
//My Bravo doesn't have a Q&A page either -- it needs one that's not my PM box...Don't PM me on how to root your phone and flash CM7 -- read one of the 5 guides on the first page of both General & Dev...:silly:
Ok devs need some help here.
I am trying to port a rom to our Milestone 2...but it bootloops on rom animation.
I tried to logcat it but I don't think it gets as far as adb server to detect the device.and just keeps saying "waiting for device"...so I end up with no logcat to diagnose the problem.
I can logcat my current working rom but only after the phone boots....am i missing something here? please, help
Any help is very much appretiated.
Thanks a lot in advance
I was working on a ICS based hoppy rom. Unfortunately I just had a catastrophic screen failure, apparently when my laptop bag fell last night, it landed with enough force to shatter the screen on my nextbook! Oh well. it may be a while before I can work on anything to further the version I was working on.
FYI- Due to work, my time is very limited for working on the next version of Hoppy Rom. I apologize in advance. The company I work for is
setting up new engine test cells in China, and my self and 2 other people are main points of support! again Sorry for anything new taking so long!
DOCHOPPY HAS BEEN SIGHTED (Other than on a DAYZ server...Stay tuned.
Ok I have decided to pass along what I have been working on.
Warning***
This is for the Nextbook 7 premium ONLY!
Known working on Nextbook 7 premium tablets with serial numbers starting:YF1011
DocHoppy Presents!
DocHoppyRom Full On Root v2.0
and
DocHoppy Cramfs Style 3.0
Based off the official update image released by nextbook.
Major thanks to FINLESS BOB!!! GREAT HELPFUL GUY!
PRESENTING DOC HOPPY ROM
CRAMFS STYLE 3.0
AND
FULL ON ROOT v2.0
Disclaimer: I am not responsible for Bricked Tablets. This is known to work on tablet with SN starting with YF1011, and some YF1211.
First you will need to decide which version of the Rom you are going to load. The CRAMFS Style version has SU but you CANNOT write to the /system directory. This is a good all around Rom for those who may need SU but do not need to write to /system.
Full On Root is just that, you have full read write to the /system and can customize the Rom to your hreats content.
HOW TO INSTALL:
TO FLASH CRAMFS STYLE 3.0 Put the UPDATE.IMG file from the Cramfstyle Folder onto your SD card, while tablet is on and follow the on screen instructions.
After running the self extracting Zip file you will have a directory containing the following folders and files.
Drivers (folder)
CramfsStyle(folder)
FullonRoot(folder)
Log(folder)
Language(folder)
Readmefirst.txt
Rkusb.log
RkusbComm.dll
Setting.ini
RK29update.exe
TO FLASH CRAMFS STYLE 3.0 Put the UPDATE.IMG file from the Cramfstyle Folder onto your SD card, while tablet is on and follow the on screen instructions.
To flash Full On ROOT, Plug your nextbook into your PC via usb cable. Turn your nextbook over and with a safety pin or something of similar size, press and hold the reset button for 2 to 3 seconds.
Run the RK29update.exe
Select your Rom files via the boxes containing the .... And navigate to the correct directory for the rom you want to install.
Insert eache file in order according to the update tool.
Clear IDB. (this is like a lowlevel format for the Rom tool:
After the Tool says OK. Select Run. This will begin to load the Rom onto your tablet. It will go through loading and then checking the Rom install.
After the Rom loads and the tool comes back with an OK, patiently wait for the tablet to reboot, and load the new ROM. If the tablet is still connected to the pc via USB when the rom boots it will show the screen allowing you to select weather or not to turn on USB storage. Press the home key and you will be given a choice of Golauncher or Rklauncher. (go lock is a screen lock program.)
Enjoy the Rom!
Disclaimer: I am not responsible for Bricked Tablets. This is known to work on tablet with SN starting with YF1011, and some YF1211.
Features for both Roms:
Complete and correctly working market. It now correctly associates the tablet to your gmail account allowing purchases from market.
Launcher 3.0 as well as Go launcher ex. Launcher 3.0 was pulled from an rk2918 firmware3.0 update and put into this rom.
Google Calendar is now back and working correctly.
Original Email is back and working correctly.
Included Kindle App
Included Estrongs file explorer.
Both have SU though the Cramfs version cannot write to SW.
Removed Apps Added in last release and return to more of a original rom state.
Rom is pretty clean. And seems speedy.
Cramfs Style 3.0 Rom has 200mb internal Ram +/-
Full On Root 2.0 has 894MB of Free Internal Ram.
Cheers!
DocHoppy
www.freaktab.com
Keep in mind this is the first version of this ROM. There will be updates and changes made.
FUTURE CHANGES:
Custom Theme Changes.
More Tweaks to the system.
Long Term Wants:
Power Menu change to include recovery boot.
Power Menu change to include restart.
This is a work in progress.
Known working on Nextbook 7 premium tablets with serial numbers starting:YF1011
Linked here for image.
Non Add Showing Link.
DocHoppyFullOnRoot2.0
New Cramfs style Rom is still Available Here.
DocHoppyCramfsstyle3.0
To install DocHoppyRomv3.0, rename .img file to update.img, download update.img file, copy to SD card, and follow the prompt.
DocHoppyCramfsstyle3.0
Enjoy.
Disclaimer:
Not responsible for bricked tablets.
Enjoy!
Also visit www.freaktab.com
So freaking sweet, great work on RW!
I used Wendal's tool to decompress the cramfs file system.
As for the /system, Because the device uses cramfs, and based on everything I have read, using Wendal's tool to decompress the file system, make the changes, and compress is the only way I can see to be able to
customize the rom for the device. The image is rooted, but after the update.img is compressed, the /system file remains read only. I tested this using root explorer, but anything requiring su works fine. But all hope may not be lost, I was reading on a chumby forum someone suggested using mkfs.jffs to make it writable, but further down it notes that you would need to change the kernel (easy enough to recompile I think), to utilize a different file system. The boot loader would also need to be modified, something I am not ready to try and tackle just yet, I think I would be bricking my nextbook pretty quickly.
It is a start and I am actually learning a lot as I go.
Any thoughts or suggestions are welcome.
I am definitely a long time user / cyanogenmod / aosp fan, but as far as ripping open .img files its definitely new territory, I tried to find an internal SD card like the nook has, to maybe dump it, but I cannot find such a beast. Any progress you make is awesome. So do things like root explorer work, just not on /system due to cramfs?
Correct, root explorer does work, but due to cramfs, it does not allow you to toggle to rw from ro on the /system.
Working on taking apart apk's and customizing and rebuilding and resigning next.
just flashed this rom and it works great!
How would I go about doing a custom boot animation or image?
... even if it means flashing a new rom from clean?
This is great. Thanks. The only question I have is why do I see so few items in Market? Does it have anyhting to do with compatability?
Calendar & Sync Access
First, thank you for your work.
Before I update by Next7P, have you included Google Calendar and Sync access in this update?
I use MyPhoneExplorer and will need calendar sync to work so I can fully use for business.
Thanks.
There is another method to get Google Market on the Next7P, I am a new user so I can not post the link, but google , forums Whirlpool net au archive 1756859
, very easy and works great, but cannot get sync to work.
Dan,
Thanks for the responses!
sgtfoo : You can use Wendal's rk29xx tool to take a copy of my rom image, or the original update downloadable from nextbookusa.com, and
unpack it. You then have access to the system directory in an editable format. you can go into the system folder /system/media and replace the bootanimation.zip file with another one. Just be sure the image format is 480x 800 and that the zip file has 0% compression ratio. After you make the changes, just repack .img file via Wendal's tool and reflash.
dodoclub : Not sure why. I have a full market. You might try clearing the data and cache for the market. My market shows pretty full, I.E. I got 31050 entries when I searched for facebook in the market.
Danno65: Actually that is something I have been working on. I can get my google calendar to sync, currently I am using a calendar from the market called Jorte, which works great, how ever, googles actual calendar.apk closes unexpectedly, I am thinking it is just a version problem with the calendar, but haven't had a lot of time to follow up on it.
FYI here is the link to Wendal's tool, which makes it much easier to work on the update.img file.
https://docs.google.com/leaf?id=0B8hUXYDeoy_hNTc1YTVkYTMtNTNjZS00YjI2LTgyNDYtYjRjZjFmODdiZTQ1&pli=1
Cheers!
If you have any request or questions please feel free to ask, I will help anyway I can.
Thanks Dochoppy
Got one of these tablets for Christmass to replace an old broken tablet I use for work.
Google hosts our work email, so I still need to get Contacts and Appointments going, but I maybe able to side load them.
Noticed build.prop still has ro.secure=1. This prevents adb from having root access??
Calendar & Sync Access
DocHoppy,
I came across a post where the "Calendar.apk" and "CalendarProvider.apk" files must be in the "system/app" directory to work properly, I tried to copy these files to the above directory but found it to be read/only, will wendalls tool have to be used to get access to the directory?
Also, did you get your google calendars on your desktop to sync with Jorte on the Next7P, I tried but no luck.
Thanks
Dan
The updated image file worked great, thanks again
Thank you so much for your work in building a new rom for this thing. I am anxiously awaiting a new filesystem so we can have true root. How do we manage to recompile the kernel for ext4 support and change the /system fs?
Hello, first of all, thanks for your work!
I am having trouble loading this rom. it says there's an invalid image file in my sd card and if I want to delete.
Now, I don't know if my tablet is a never or older version of what you guys have...
Next7p
2.3.1
kernel: 2.6.32.27
build: v2.0.7.....
my serial is also different from alot..it starts with YF0511
any help or tips?
markmatters said:
Hello, first of all, thanks for your work!
I am having trouble loading this rom. it says there's an invalid image file in my sd card and if I want to delete.
Now, I don't know if my tablet is a never or older version of what you guys have...
Next7p
2.3.1
kernel: 2.6.32.27
build: v2.0.7.....
my serial is also different from alot..it starts with YF0511
any help or tips?
Click to expand...
Click to collapse
I would say the serial number would have something to do with it, check on the site for nextbook and see if your serial is in the same *batch* as ours, if the original serial is in a different group, im assuming the hardware may be slightly different? If so, you can always use his method to repack the original with root.
First off I would like to say that I was very pleased when I came across this thread from another one. I haven't flashed this ROM yet, but plan to. Thank you for your work on this as I have been searching the whole internet since I got this thing [4 weeks now] for some sort of custom ROM. It is hard to use this tablet when I have ICS on my Captivate and Vibrant. GB just isn't as cool.
One thing I hope we can work on is root access, so we then can use Titanium Backup. Then we won't have to manually reload everything when new releases come out.
With all that being said, if there is anything I can do to help, I would love to. Like I said, I plan on flashing this probably tomorrow or Tuesday. Thanks again.
For the record, I got titanium backup working fine on this rooted rom. it is capable. You just need to reboot after it restores a backup.
i'm new to android. glad to see rooted rom finally, keep it up!!!
i have a clarification, any improvement in the booting time? my device took 1min30sec (power ON to ready to use, for me, 90sec seem like not fast enough).
Good luck on improving boot time. And besides a tablet is best used when on all the time... try using the suspend state to quickly wake it. We're just starting with the early versions of this rom... give it time to grow.
Sent from my N7p using XDA App
Build.prop editing
Okay so observation:
Our tablet is not recognized as a "tablet" by the Android market, only and android device.
What prop would I have to edit in order to have us recognized as I tablet. I noticed this when:
I finally managed (through some internet tutorial before this rom) get the market working (the first version, not 3.1+). And when I downloaded apps (I'll use Minecraft Pro as an example) I noticed that the way mine looked and the way the tablet version looked via android market photos and Youtube, ours looks like an enlarged phone version rather than a tablet optimized version. What can I edit to fix this?
Flashed this today... so for it works great. Love the new boot animation. Great work and can not wait for future releases!
Sent from my Nextbook Premium 7 (Doc Hoppy's Rom v02) from the XDA app.
---------- Post added at 12:16 PM ---------- Previous post was at 12:03 PM ----------
One thing that would be great on a future release [not sure if it is possible yet with out r/w], would be a bigger data partition for apps. Moving everything large to the SD is ok, just takes longer to boot those apps. A kernel that would allow voltage control app [like CPU Master] to work also. Just a thought!
hi Guyz,
I was trying for Building a Custom Rom and was getting error in update binay. So now here it is Custom Rom for HTC EXPLORER (pico).
What u get:
1. European Version as base
2. apps2sd:
3. Cache 2 sd:
4. etc/init.d folder functionality.i.e. u can run scripts (attached one batch of scripts)
5. Rooted, Busybox Installed
6. data/app functionality
7. Approx. of 120mb space on startup.
What to do:
1. Download the rom from this link http://www.4shared.com/zip/IyFaISq4/Htc_Pico__Master_rom_EDITTED_.html
and copy to root of ur sdcard.
2. Go to recovery by removing battery, pressing volume down button + power button, then selecting recovery from the menu which will popup
2. Now, navigate to flash from sdcard option and flash the rom.
3. after flashing, i recommend clearing cache, dalvik cache, fix permissions, and a factory reset.
4. You must have 2nd partition on ur sdcard.
what to do with scripts Download from here http://www.4shared.com/zip/1jyn2_tT/scripts.html
Extract the scripts to sdcard and copy them to /system/etc/init.d folder and go to recovery and fix permissions.
Theme
Transparent. The zip is attached
Flash it in Custom recovery
Deodexed Version of the Rom
Download from Here: http://www.4shared.com/zip/N6dytdrK/masteredittedDEODXD.html
NOTE: The scripts (that are mentioned above) are already added to this version
For those who want to remove sense completely.
First install any other launcher before uninstalling sense.
To remove sense, remove or move (to sdcard) following apps from /system/app using root explorer(file browser)
HTML:
1. com.htc.FriendStream.apk
2. com.htc.musicWidget.apk
3. FriendStream.apk
4. Htccalender widget.apk
5. HtcClockWidget.apk
6. HtcContactWidget.apk
7. HtcDirect.apk
8. HtcLockScreen.apk (this will remove sense lockscreen, dont delete it if u want to keep the lockscreen
9. htcMailWidget.apk
10. HtcmsgWidgets.apk
11. HtcQuickLaunchWidget.apk
12. htcsettingwidgets.apk
13. MyHtc.apk
14. Rosie.apk
15. WeatherWidget.apk
16. skinscanner.apk
Nice!
Gotta try it!
Flashing a rom deletes all the contacts, messages and apps right?
PeaceMaker_htc said:
Nice!
Gotta try it!
Flashing a rom deletes all the contacts, messages and apps right?
Click to expand...
Click to collapse
Yes contact can always retaiibed via googlee accnt. N for messages download backup app from market
Sent from my Dell Streak using XDA App
Thanks!!
Need some clarifications..
Does it come with overclocked kernel?
How to move apps this way? Link2sd will move data now?
This rom has ext2/3/4 support and overclock?
Thanks.
jaggyjags said:
Thanks!!
Need some clarifications..
Does it come with overclocked kernel?
How to move apps this way? Link2sd will move data now?
Click to expand...
Click to collapse
First of this is first ever Rom
Now answer to your questions
No it doesnot comes with overclock kernel
For ext partitions u still need the kernel by yunnou as ext partition is function in kernels ..
Apps are automatically. Moving to data/app folder
And reg. Link2sd app i havent tryd till now . may b u can try and report
And it was earlier also moving data with yunnou kernel
Sent from my Dell Streak using XDA App
languages
This rom has the Portuguese language?
samueldf said:
This rom has the Portuguese language?
Click to expand...
Click to collapse
Not yet , sorry on that
as this was my first ever rom effort , i will find or any of u guyz can help me on that how to do so , or anything on google , or meanwhile, look for "locale" apps on market
Check this ROM by me
http://forum.xda-developers.com/showthread.php?p=22009878#post22009878
Overcklocked kernel included with modules.. deodexed.. and so on
whats the major diff between asia_india rom and this? any advantage as such? i hav asia indai, overclocked, ext support, links 2 sd, rooted.
Deleted
Sent from my Dell Streak using XDA App
@jitin02
just trying to help people, i have received PM during the last few weeks reporting roms could'nt flash on some peoples devices because they where not deodexed (finally found out the problem) or where having difficulties not knowing how to flash or do several steps in order to keep phones up to date and take the maximum out of their device.I thought it was easier just to make things myself than asking other people to do so.
Also I am preety keen to help others as much as they need, solving doughts as much as my nogledge reaches, making people undertand some difficult concepts or procedures.
I am very sorry if you thought this was a competition, you got reasons to think so. Next time I will let people try to solve there problems by themselves.
By the way, many thanks making this phone rootable for the first time, credits all goes to you for finding a way at last, I am extremely grateful
?
jaggyjags said:
@jitin02
just trying to help people, i have received PM during the last few weeks reporting roms could'nt flash on some peoples devices because they where not deodexed (finally found out the problem) or where having difficulties not knowing how to flash or do several steps in order to keep phones up to date and take the maximum out of their device.I thought it was easier just to make things myself than asking other people to do so.
Also I am preety keen to help others as much as they need, solving doughts as much as my nogledge reaches, making people undertand some difficult concepts or procedures.
I am very sorry if you thought this was a competition, you got reasons to think so. Next time I will let people try to solve there problems by themselves.
By the way, many thanks making this phone rootable for the first time, credits all goes to you for finding a way at last, I am extremely grateful
Click to expand...
Click to collapse
It's OK brother got totally not trying to point out to you
I an also keen to help people here and it's great and thanks to you that at least someone like you to be there for people when I an there thanks
And for rom. I have a deodxd version. but the problem is in non deodxd version the internal space came to be much but when I deodxd it the space went from 120--90. I will upload my deodxd version to.
Let's combine up both and try to help prompt this phone together and help people.
I have made a theme from Uot kitchen will upload it tomarw
And people there is on harm in posting problems here in thread reason being the about to use this rom. People should also know what's problems are and a request when you post problem and by chance you solve with it PLEASE UPDATE YOUR POST AND MARK IT SOLVED ALONG WITH SOLUTION. And this applies to jaggyjaggs rom too
No offense jaggy.
And grill will try to update op. With my theme. And another which I will try and deodxd version or this rom + another theme TRANSPARENT
JAGGY. I would like to know what problems people are facing n this version of. Rom and you are always welcome to help
Sent from my Dell Streak using XDA App
@Jitin & Jaggy
both of you are doing very good helping people and making custom roms for android noobs like me so never let yourself down...I know how it feels as i myself was a modder for nokia s60v5 series....So whatever happens dont let anything come in your way...just do what you feel is right...
if you want help testing roms and your scripts i m ready to help....I can be your BETA tester...
things are being solved gradually,
now no space limitations, people have no problem now to flash deodexed version. yes deodexed roms have to create extra "code" in dalvic cache but its easier to add tweaks and modify (using baksmali), I am working on it to add tweaks and hopefully make it faster, would love if people experiment with it and could implement them in future roms.
I have tried this: http://forum.xda-developers.com/showthread.php?t=1411317
but didn't work as expected, here is my reply in that thread: http://forum.xda-developers.com/showpost.php?p=22042958&postcount=105
The only thing people are reporting now is the lack of languajes, just european. I haven't got the knowledge yet to extract Roms from RUU and would be great to get them all to .zip Roms.
we could create a thread up to date with the progresses made and the future proyects and who is working on what, what do you think?
You guys ever noticed how skins dont seem to be enabled in the explorer? under personalize theres no skin option... any way to enable them? theming would be so much easier with them... and Jithin, what major diff/advantage do u find betwen the india and eu versions? :/
deepaktom said:
You guys ever noticed how skins dont seem to be enabled in the explorer? under personalize theres no skin option... any way to enable them? theming would be so much easier with them... and Jithin, what major diff/advantage do u find betwen the india and eu versions? :/
Click to expand...
Click to collapse
Reg. Skins: it seems like HTC tried to make a foool of us by putting skins options as it does nothing.
Reg. differ in Indian and EU version:
In indian, some extra apps + another one which noticed was the space. the space in indian came to be more as soon as i deleted 3-4 apps in indian which were not present in eu version.
+ the difference of bands + there is Hindi language keyboard in Indian version.
Root HTC Explorer
Hi.
Just one question.
If I root the phone, this one stay free for any operator?
jitin02 said:
hi Guyz,
I was trying for Building a Custom Rom and was getting error in update binay. So now here it is Custom Rom for HTC EXPLORER (pico).
What u get:
1. European Version as base
2. apps2sd:
3. Cache 2 sd:
4. etc/init.d folder functionality.i.e. u can run scripts (attached one batch of scripts)
5. Rooted, Busybox Installed
6. data/app functionality
7. Approx. of 120mb space on startup.
What to do:
1. Download the rom from this link http://www.4shared.com/zip/IyFaISq4/Htc_Pico__Master_rom_EDITTED_.html
and copy to root of ur sdcard.
2. Go to recovery by removing battery, pressing volume down button + power button, then selecting recovery from the menu which will popup
2. Now, navigate to flash from sdcard option and flash the rom.
3. after flashing, i recommend clearing cache, dalvik cache, fix permissions, and a factory reset.
4. You must have 2nd partition on ur sdcard.
what to do with scripts Download from here http://www.4shared.com/zip/1jyn2_tT/scripts.html
Extract the scripts to sdcard and copy them to /system/etc/init.d folder and go to recovery and fix permissions.
Theme
Transparent. The zip is attached
Flash it in Custom recovery
Deodexed Version of the Rom
Download from Here: http://www.4shared.com/zip/N6dytdrK/masteredittedDEODXD.html
NOTE: The scripts (that are mentioned above) are already added to this version
For those who want to remove sense completely.
First install any other launcher before uninstalling sense.
To remove sense, remove or move (to sdcard) following apps from /system/app using root explorer(file browser)
HTML:
1. com.htc.FriendStream.apk
2. com.htc.musicWidget.apk
3. FriendStream.apk
4. Htccalender widget.apk
5. HtcClockWidget.apk
6. HtcContactWidget.apk
7. HtcDirect.apk
8. HtcLockScreen.apk (this will remove sense lockscreen, dont delete it if u want to keep the lockscreen
9. htcMailWidget.apk
10. HtcmsgWidgets.apk
11. HtcQuickLaunchWidget.apk
12. htcsettingwidgets.apk
13. MyHtc.apk
14. Rosie.apk
15. WeatherWidget.apk
16. skinscanner.apk
Click to expand...
Click to collapse
Why isn't this thread popular? And what finally happened to jitin02?
cm9 htc a310e