Related
Hi Folks.
Just been issued heros at work and wish to update the radio rom...How is this accomplished??
regards
Lohtse
Firstly it needs to have a recovery image installed I recommend Amon-Ra v 1.6.2.
Secondly you need to find the radio rom you wish to flash and put it onto the root of you phones sd card.
Thirdly enter the recovery image you have installed by holding power and home button from the phone being off.
Then select the radio.zip to flash.
Everything I have said here can easily be found how to do via searching this forum or its wiki.
also www.theunlockr.com will help with installing the recovery image.
lohtse said:
Hi Folks.
Just been issued heros at work and wish to update the radio rom...How is this accomplished??
regards
Lohtse
Click to expand...
Click to collapse
First you will need to install the custom recovery console if you haven't done so already.
Then download your updated radio, put it on your SD, load into the recovery, then apply update. DONE!
If that is too brief,... let me know,...
EDIT... Ooops,... too late.
way to complicated...
Too much to do and can screw up..... At least with winmo and symbian was a few clicks...
hmmmmm think will ditch android.....
really? its not complicated at all when you know what your doing. In fact I can say its a damn sight easier (and safer) than modifying blackberry roms and from what I hear also Windows Mobile.
Lennyuk said:
really? its not complicated at all when you know what your doing. In fact I can say its a damn sight easier (and safer) than modifying blackberry roms and from what I hear also Windows Mobile.
Click to expand...
Click to collapse
I came from wimo to android, and as it is said, it's quite hard to catch the thing at the beginning, but after everything seems easier than in wimo !! and more reliable... you have almost no chance to brick your hero after you installed the recovery boot.
radio : boot in recovery then select the good option.
rom : nandroid backup / install whatever rom you want / if you don't like it go for nandroid restore ( all you need is two Sd card.. the good one and the one for the "tests" ).... etc....
But at the beginning i was totally out but with a little time.. reading some posts (here and on the web) ... one day everything was more clear !
Ciao
Fred
lohtse said:
way to complicated...
Too much to do and can screw up..... At least with winmo and symbian was a few clicks...
hmmmmm think will ditch android.....
Click to expand...
Click to collapse
Its not hard at all. You can have the recovery installed and the radio updated in 5 minutes.
For step by step instructions follow the "Installing a recovery image" section in BTDAG's guide linked in my signature.
Then further down the same post, in the second yellow box there are instructions on "Updating your Radio".
Guys, the OP said he was issued the Hero at work, then two hours later said he was going to ditch Android... so what then, he's quitting his job? Troll alert. Don't feed the troll.
As to troll comment(yes offence has been caused)....hmmmmm.... Am going back to the trusty Kaiser... WE DON'T HAVE TO USE THE HERO.... We live in free(ish) world.. And the Phones are issued as an update to our old duty phones... Also I'm not the only one who uses them that feels the same.
Now to updating being easy. Gulp I must be eeer dum!!! Du hu Du HU must be the TROLL in me!
I have tried to install recovery image thing and well just cant get it to work... And now I find I have to root the hero too so things will install to sd card!!!! WTF this should all be standard like winmo and symbian etc...
I have been using smart phones since the Ericsson r380 and so far Android has failed to impress to the degree I am beginning to hate it....
Am far to used to having simply andfull access to everything..
Android is a HUGE learning curve that I suspect I may not have the patience for..
regards The TROLL sorry I mean Lohtse
Now I have finally managed to get recovery image on and updated the radio...Being called a troll did it !!!!!!.....LOL
My final questions are this how do I root so I can install to sd card(just point me in the right direction) And do I have to unlock Phone to any network to have custom roms on..
regards
TROLL
lohtse said:
Now I have finally managed to get recovery image on and updated the radio...Being called a troll did it !!!!!!.....LOL
My final questions are this how do I root so I can install to sd card(just point me in the right direction) And do I have to unlock Phone to any network to have custom roms on..
regards
TROLL
Click to expand...
Click to collapse
Wahey!!!! Good job man.
Ok,... So now you have the recovery image all you need to do is pick a custom ROM. Personally, I highly recommend MCR3.2 (link in signature at botom). It is an Android 1.5 ROM but is stable and fast, what more could you want for a work phone.This ROM is rooted and has apps2SD enabled. Once you have installed the ROM you will need to remember to create an ext2 partition on the SD card (easily done through the recovery). Then you are set to go!!!!
lohtse said:
Now I have finally managed to get recovery image on and updated the radio...Being called a troll did it !!!!!!.....LOL TROLL
Click to expand...
Click to collapse
You're welcome And what ddotpatel said. MCR is fast & clean. By installing a custom recovery you've already done the only tricky bit.
Yep installed 3.2 from modocca. seems nice but how do you know if the apps are installing to sdcard???? I'm not sure they are lol..
lohtse said:
Yep installed 3.2 from modocca. seems nice but how do you know if the apps are installing to sdcard???? I'm not sure they are lol..
Click to expand...
Click to collapse
You need to create an ext2 partition on your SD card through the recovery again. I cant remember the exact wording but something like "create ext2 + fat" or something along those lines.
As far as I know, once that has been done all apps will install to SD.
Someone with more knowhow than me correct me if I am wrong?... CAULI?,... LENNY?
Can someone who knows please answer this question:
Are you 100% sure that flashing the Radio ROM does not affect the phone RF Calibration ?
Thanks!
ddotpatel said:
You need to create an ext2 partition on your SD card through the recovery again. I cant remember the exact wording but something like "create ext2 + fat" or something along those lines.
As far as I know, once that has been done all apps will install to SD.
Click to expand...
Click to collapse
Yup, certainly as far as MCR is concerned. On the first reboot it will move all files from /data/app to /system/sd/app (& similarly for app-private) Nb /sysytem/sd is the mount point for the ext2 partition. All it does is move the files over & then replaces the /data/app (& app-private) directory with a symlink to the new location. That way future installs, updates etc all automatically go to the new location.
You can always check yourself with a terminal emulator & the command ls -l, or using a file manager like Root Explorer, if you're curious. Some people think it's not working because they see available space in internal flash drop as apps are installed, but that's because app data & the dalvik cache remain on internal flash, principally aiui for reasons of access speed. The saving you make just from shifting the apks to sd is more than enough for most people it seems.
cauli said:
Yup, certainly as far as MCR is concerned. On the first reboot it will move all files from /data/app to /system/sd/app (& similarly for app-private) Nb /sysytem/sd is the mount point for the ext2 partition.
All it does is move the files over & then replaces the /data/app (& app-private) directory with a symlink to the new location. That way future installs, updates etc all automatically go to the new location.
You can always check yourself with a terminal emulator & the command ls -l, or using a file manager like Root Explorer.
Some people think it's not working because they see available space in internal flash drop as apps are installed, but that's because app data & the dalvik cache remain on internal flash, principally aiui for reasons of access speed.
Click to expand...
Click to collapse
hmmmm I certainly noticed a drop in available memory on the phone to the degree of only having 54 megs free...
SebHTCHero said:
Are you 100% sure that flashing the Radio ROM does not affect the phone RF Calibration ?
Click to expand...
Click to collapse
what is rf calibration?
What is radio rom used for by phone?
kendong2 said:
what is rf calibration?
Click to expand...
Click to collapse
A set of tables usually stored in NVRAM that takes into account the slight differences in the components used to build your phone. Every single phone is calibrated during manufacturing.
If the calibration is erased, it will look like it works but you can have all sort of problems from poor battery life to random drop from the network or poor sensibility (not to mention the higher than expected radio levels you could be emitting right next to your brain )
I'm posting this in General as I don't have the knowledge to port this or develop a similar version for the Slide and I don't want to clutter up the Development forum.
Team ADX over in the Droid Eris forum came up with this gem; a dual boot Eclair Sense/2.2 AOSP ROM. http://forum.xda-developers.com/showthread.php?t=824072
I don't know if this can be done on our phones, but I thought it possible as you don't need to flash a custom recovery.
man this would awesome... the best of both worlds, run and "stock" ROM so we can still receive updates and still have CM.
i was actually thinking about dual boot just the other day! i dont feel like id be switching back and forth from 2 roms but itd be a great feature for those who do. unfortunately i dont think we have that much developers :/
I was reading the instructions for it and it looks like we'll have to wait for S-OFF before we can try it.
Part of the scripting is telling the phone how to partition the phone, sizes of those partitions, and so on. The slide is, generally speaking, un-brickable and it's the measures used to give us that luxury that also prevent us from doing so much like R/W on the system while in a non-recovery boot and changes we do make while booted are just wiped on reboot *sigh* man I love that ramdisk image.
Once we get S-OFF let's get this project started
KCRic said:
I was reading the instructions for it and it looks like we'll have to wait for S-OFF before we can try it.
Part of the scripting is telling the phone how to partition the phone, sizes of those partitions, and so on. The slide is, generally speaking, un-brickable and it's the measures used to give us that luxury that also prevent us from doing so much like R/W on the system while in a non-recovery boot and changes we do make while booted are just wiped on reboot *sigh* man I love that ramdisk image.
Once we get S-OFF let's get this project started
Click to expand...
Click to collapse
I don't think S-OFF is the issue. The partitioning instructions only refer to sdcard. This command:
Code:
mkpartfs primary fat32 0 3500 (can be adjusted to your needs. This partition will be used by the 2.1 rom and by recovery)
I think is only for the phone ROM storage and the for the recovery to find the boot scripts. According to the instructions, they're only partitioning the sdcard to run the AOSP ROM in it. They install the 2.1 Sense ROM to the phone, get it set up, run the boottosd script to boot into the 2.2 AOSP ROM on the sdcard, then set that up and run the boottophone script to go back to 2.1 Sense. They're running a ROM on the sdcard!
As I said before, I think something like this can work for our phones because it doesn't require flashing a recovery. The problem is we don't have the devs to do it.
heybobitsme said:
I don't think S-OFF is the issue. The partitioning instructions only refer to sdcard. This command:
Code:
mkpartfs primary fat32 0 3500 (can be adjusted to your needs. This partition will be used by the 2.1 rom and by recovery)
I think is only for the phone ROM storage and the for the recovery to find the boot scripts. According to the instructions, they're only partitioning the sdcard to run the AOSP ROM in it. They install the 2.1 Sense ROM to the phone, get it set up, run the boottosd script to boot into the 2.2 AOSP ROM on the sdcard, then set that up and run the boottophone script to go back to 2.1 Sense. They're running a ROM on the sdcard!
As I said before, I think something like this can work for our phones because it doesn't require flashing a recovery. The problem is we don't have the devs to do it.
Click to expand...
Click to collapse
I'll take a look. No promises as I'm an übernoob but I would love to have this.
Sent from my T-Mobile myTouch 3G Slide using XDA App
migueltherocker said:
I'll take a look. No promises as I'm an übernoob but I would love to have this.
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
You won't be able to do a simple port. I posted about it more of as a proof of concept. Take the same idea, but obviously using our espresso sense and CM6.
heybobitsme said:
I don't think S-OFF is the issue. The partitioning instructions only refer to sdcard. This command:
Code:
mkpartfs primary fat32 0 3500 (can be adjusted to your needs. This partition will be used by the 2.1 rom and by recovery)
I think is only for the phone ROM storage and the for the recovery to find the boot scripts. According to the instructions, they're only partitioning the sdcard to run the AOSP ROM in it. They install the 2.1 Sense ROM to the phone, get it set up, run the boottosd script to boot into the 2.2 AOSP ROM on the sdcard, then set that up and run the boottophone script to go back to 2.1 Sense. They're running a ROM on the sdcard!
As I said before, I think something like this can work for our phones because it doesn't require flashing a recovery. The problem is we don't have the devs to do it.
Click to expand...
Click to collapse
Ok that makes sense. I thought it was pointing to the partitions on the phone telling it to format to a different size for some reason. Then what's preventing us from doing this? Just a lack of a proper script?
I have not poked around with how they are going about doing everything, but I was the one who got the ball rolling with my dual boot linux script. Conap took the basic setup and made some changes to just install them both on the phone and sdcard. Here is the basic of what it is doing....
The init.rc file found in boot.img has been modified for the froyo rom on the sdcard. The lines where it mounts [email protected] , [email protected], and [email protected] have been changed to the partitions on the sdcard (/dev/block/mcblk0px) The updater-script for froyo has been modified to flash the rom to the partitions on the sdcard. There are some gscripts which are ran from the phone that either modify or replace the boot.img for the rom you want to boot into.
The froyo ROM is running completely off the sdcard and the recovery is left untouched. The script that is required if you are using clockworks is because clockworks sbin and folder locations are setup a little different. I was running into some problems with froyo not recognizing the sdcard after making more than 4 partitions. Several had reported to me that their phones also did not recognize the sdcard, but the Eris phones somehow still did. I am working on something that should run from all android phones and allow you the option of installing whatever ROM you want.
One Last Thing..
Anyone is capable of learning how to do some development work. It just takes some patience and "Google". I had no knowledge of linux or any other scripting languages, except windows batch scripts, until 3 months ago.
There is not much activity on my thread, but once I get a working version finished it will be posted there-----Dual Boot Android
When you get it done and own working, post it in development. I only posted the thread in general because I knew I wasn't going to be the one to develop it. I'm a welder by trade and java and linux are a little beyond me. Although I am trying as I'm using Ubuntu as my main OS and starting reading java tutorials.
Sent from my CM6 Slide
heybobitsme said:
You won't be able to do a simple port. I posted about it more of as a proof of concept. Take the same idea, but obviously using our espresso sense and CM6.
Click to expand...
Click to collapse
If there was ever a reason to get a dev started on a project, this would be it. I would reconsider upgrading from the Slide if we had something this awesome.
unCoRrUpTeD said:
I was running into some problems with froyo not recognizing the sdcard after making more than 4 partitions. Several had reported to me that their phones also did not recognize the sdcard, but the Eris phones somehow still did. [/URL]
Click to expand...
Click to collapse
From what I understand, android can not *see* more than 4 partitions so they had to do something a bit different. Somewhere in the thread that's linked it states what they did to get it to work.
s off is tmobs response to....
KCRic said:
I was reading the instructions for it and it looks like we'll have to wait for S-OFF before we can try it.
Part of the scripting is telling the phone how to partition the phone, sizes of those partitions, and so on. The slide is, generally speaking, un-brickable and it's the measures used to give us that luxury that also prevent us from doing so much like R/W on the system while in a non-recovery boot and changes we do make while booted are just wiped on reboot *sigh* man I love that ramdisk image.
Once we get S-OFF let's get this project started
Click to expand...
Click to collapse
The "companies" wanted s-off due to the large number of brix getting returned for handest exchange and assurion claims, just to figure out somebody pooched sumthin up trying to be a HAXOR, if you haven't done anything like this before. Id suggest peeps get a g1 or some other root & rom-o-matic type for and play with it till you take on your brand new handset trying to install some bleenin edge hack...
You gotta learn to wank off before you can try it with somebody else in the room.
I remember my early days at xda, hacking my mda, xcaliber, and esato hacking SonyEricsson fones before they jumped the shark. People who had the ability to read and follow directions (emphasis on the read part) would study till they were sure they would still have a working fone at the end. Hung out and did great stuff with there handsets. And the noobs were wary enough to investigate before they just started mucking about.
So the handset manu. Had to do sumthin and now we have s-off.
the moral of my high and mighty rant an rave, if you don't know how to do sumthing or if you understand what to do but not the why, then keep reading, read more do less
KCRic said:
From what I understand, android can not *see* more than 4 partitions so they had to do something a bit different. Somewhere in the thread that's linked it states what they did to get it to work.
Click to expand...
Click to collapse
In the newest builds they have 2.1 system on the phones system partition and froyo system on the phones data partition. The data is moved to the SD. 2.1 and previous Rome had no problem with extra partitions on the sdcard.froyo changed the way it mounts the sdcard and could only see 4.
I am actually releasing a dual boot method very shortly that should work on any android phone with very little setup required on your part. I am in the process of finalizing it. Anyone interested in testing please let me know as I want to test on as many devices ad possible
Sent from my HERO200 using XDA App
For those with phones other then Incredible...The new app that will replace this system and work with multiple phones is in the market. Check out my sig for our website with more info.
Does not work with CWM2.5...Tested with CWM 3.0.8 ONLY WILL NOT WORK WITH OTHER RECOVERIES
A super big thanks to xda dev drellisdee since he's the one who showed me how to mount the img's at boot time. Check out his modified recovery here http://forum.xda-developers.com/showthread.php?t=758874
Thanks also too:
Team ADX-I used my personal account to post since it has the dev privaliges but consider this a Team ADX endeavor.
Thanks to DHowett for furthering the idea of what we can do with the dualbooting
Thanks to UnCorrupted for giving me the original interest in Dual Booting roms long, long ago!!
Thanks to VZW for taking so much of my paycheck everymonth!!
Thanks to all who tested and gave feedback on my original DualRom project and to all who will do the same with this one.
Thanks to all the Dev's that give us a reason to want to use more then 1 rom.
DRX2 is an upgrade from DualRom. You can fit up to 4 roms on emmc(and one on the phone if you want) It uses the phone as an installer. I decided to go towards DHowetts idea of mounting img files on the emmc. Emmc will stay as fat32 the way it comes on the phone. This system is fairly simple and so far has worked with all rom's tested.
Tested with:
MIUI
CM7
SkyRaider 4.0
GingerSense Remix-B1-INC
Uber-z_RC3-1
Nil's Busines Sense
Leaked GB rom
WarmZ
uber kingdom sense 3.0 (1.0.1)
mikmik's beta 3 (sense 2.1 w/ 3.0 additions)
Incubus's Stock 2.0
mytouch 4g doubleshot rom
stock kingdom 3.0 rom
Post what rom's you boot successfully so they can be added to the list!!!
As you can see that's a good variety and it should work with every rom.
Does not work with CWM2.5...Tested with CWM 3+ Might work with other recoveries.
Installation
Installation is simple. The roms will be stored on emmc in folders labeled rom1, rom2, rom3 and rom4. each folder will need a system.img, data.img and cache.img. You can flash createimageforrom1.zip to setup the folder and img's for rom1 and the the same for the other roms up to rom4. The zip's i included create a 270mb system.img, a 1000mb data.img and a 120mb cache.img. If you would rather manually create these and make your own sizes do:
adb shell
cd emmc
mkdir rom1 (or rom2, rom3, rom4)
cd rom1
dd if=/dev/zero of=system.img bs=1M count=270
dd if=/dev/zero of=data.img bs=1M count=1000
dd if=/dev/zero of=cache.img bs=1M count=120
NOTE: Some rom's the dd command acts differently and your img may come out really small. If that's the case just add busybox to the beginning of the dd command.
the last number on the last three commands is the size of the image it will make. These take a while to make. If you use the zips i included expect to wait at least ten minutes for the img's to be built. Once they are built on the emmc you can flash different rom's to them without deleting/recreating them so you should only need to do this step once.
Once you have the img's setup choose your rom and your kernel or any other ad on's that you want installed. Flash the rom as normal(wipe phone, install zip from sd) NOTE: this will obviously overwrite your existing installation so if you want to keep that you will need to make a nand to restore when you are done. Next flash any ad on's or kernel zips you want installed as normal. Then just flash the zip for rom1installer that i've included. You can use rom1installer or rom2installer, etc to pick which slot you want the rom installed to. They don't have to be installed in any order. You can use just rom4 if you want just make sure you have setup the img's for the rominstaller zip you use. The installer zip will take 5 to 8 minutes to install so be patient. After that reboot your phone and it will boot to the rom you just installed. You can then use the DRX2 app to boot between all installed roms. If you restore your nand to your phone or install another rom to the actuall phone then run the phoneinstaller.zip to set that rom up to use the DRX2 app as well. So to recap and make it simple:
Does not work with CWM2.5...Tested with CWM 3+ Might work with other recoveries.
1. flash createimageforrom1.zip(or rom2, rom3, rom4) or all of them if you want lots of roms(you only need to do this if the img's are not already on your emmc)
2. flash your rom of choice and any add on's you want. (rember to wipe phone first and backup if nescasary) If you want to move the rom your currently have installed on your phone to one of the rom slots on emmc just skip this step.
3. flash rom1installer.zip (or rom2, rom3, rom4) whichever slot you want it installed too.
4. reboot
5. If you are also going to use a rom on your phone normally then flash or restore a nand of the rom you are keeping on phone. Then flash phoneInstaller.zip. This will install the DRX2 app and copy your phone rom's boot.img to emmc so the app can access it when you want to boot back to the phone rom.
Upgrading roms
rom1upgrader.zip(and rom2,rom3,rom4) can be used to upgrade your rom on emmc. These haven't been well tested. I did test with miui and a GB Sense 2.1/3.0 rom. Using these would be considered doing a no wipe update. If you want to wipe use the rom1installer.zip's. Step are as follows:
1. Wipe phone flash update and any add-on's
2. flash rom1upgrader.zip(or rom2,rom3,rom4) Make sure you flash the one where the rom your upgrading is installed
3. Reboot.
These could also be used if you want to flash add-ons. Flash the rom you currently have installed, flash the add-on, then flash the rom1upgrader. Example:
I have cm7 nightly 90 on slot1
I wipe phone, flash cm7 nightly 90 to phone, flash any add-on's i had flashed previously, flash any new add-on's, flash rom1upgrader.zip
Note: There is definitely a possiblity of typo's in one of the many scripts i had to write for this stuff so if you do have a problem that you post about please post which slot you have the rom installed too. Thanks.
DRX2 app
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
DRX2 works similar to DRSettings app. Push the button of the rom you want to boot too!!! simple enough right? Push menu for options to set the names of the rom's you have installed. If you set a name for Rom1 while booted in Rom1 the name will show when you boot to rom2, 3, or 4 so you only have to set the names once. There is also an option under menu to mount or umount emmc to pc. I added this because the one downfall of this system is the emmc does not mount to pc when using the mount disk drive options normally. Remember don't delete or move the img's of the rom your booted too.
Additional Scripts
bootRom1.zip, bootRom2.zip, etc...these zips are for the off chance you get stuck in recovery(i.e boot.img did not flash correctly) This shouldn't happen but I like to be safe especially if your not near a pc to fix it. You can flash these zip to boot into any of the 4 roms you have installed from recovery. Of course they will only work if you have a rom installed in the slot you are trying to boot too.
Downloads
Disclaimer-FLASH AT YOUR OWN RISK. You are responsible for what you do to your phone.
All the files you need are in 1 small package!!
V2 Changelog
DRX2 app installed to data/app instead of system/app so that GB sense rom's install it
V3 Changelog
Fixed app's not installing that i broke in v2
V4 Changelog
Fix for AOSP rom's not mounting as ext3(They should work ok as ext2 so if you already have it installed I wouldn't rush to change it. If you start to experience any data corruption then you can update those roms. These won't really affect the sense based rom's as they were already mounting as ext3.)
MultirominstallersV4.zip --old
V5 Changelog
Added a 5 second sleep on boot to give time for phone to mount the partition.
MultiromInstallersV5.zip --old
V6 Changelog
Added upgrader's in with the main package
Switched to ext2 for system.img and added ext2 datadata.img for lag improvements
Note: V6 Requires you to reflash the createimgforrom.zips because of the changes in the setup of the img's.
MultiromV6.zips --latest
Zip's to switch rom's in recovery--Now inclueds boot phone rom zip(I.E. boot-rom1.zip)
AnyKernelUpdater.zip's for DRX2 courtesy of tiny4579
tiny4579 made up some nice zips to replace the kernel on the emmc rom's. You don't even need to be booted into the rom you want to update the kernel on. Take the zImage from kernel/zImage and the files from system/libs/ in the kernel.zip that you downloaded and drop them in the same folders in these zips. These directions probably suck so if I confused you just ask!!!!
Rom1KernelUpdater
Rom2KernelUpdater
Rom3KernelUpdater
Rom4KernelUpdater
Nothing better then user contributions to a project like this so if you come up with something you'd like to share let me know!!!
Upgraders
Upgrader's now bundled in with the main package
Note: Unzip the multirom.zips to get to the flashable zips.
Does not work with CWM2.5...Tested with CWM 3+ Might work with other recoveries.
UnInstalling DRX2
If you want to install a new rom to a slot already in use then just follow the instructions I gave above. The scripts will wipe the img files at install.
If you want to completely uninstall the system just delete the folders off your emmc storage!!
Make sure your booted into a rom installed normally on the phone first!!
Additional thoughts
If the rom does not boot try installing and booting it on the regular phone first.
Any time your copying data from one place to another corruption can occur. If it doesn't work try it a second time. If you have to try again make sure to wipe the phone and reinstall the rom before re-running the installer scripts.
Install all add-on's, new kernels, flashable themes before running the installer script.
You can run the rom on the phone as normal, set it up, try it out and then move it to the emmc slots at any time by running an installer script. It will copy your data over also. In the case that you might want to check the rom out or see how a flashable them looks before installing it to one of the emmc slots.
If you have questions feel free to ask.
Nice Work im going to try it out
This looks awesome..... ! Now can keep up with all of JoelZ9614's Rom's... lol
has this been tested with sense 3.0 because it seems like .img's are too small
justjayhere said:
This looks awesome..... ! Now can keep up with all of JoelZ9614's Rom's... lol
Click to expand...
Click to collapse
lmao i bet i will have more than 4 roms
werdna87 said:
has this been tested with sense 3.0 because it seems like .img's are too small
Click to expand...
Click to collapse
I tested with gingersense remix which is sense2.1/3.0 i believe. The system.img i put was 270mb's which is larger then what's on the phone so if it fit's on the phone it will fit on this. That being said you can make the img's whatever size you want but the current install process requires that they be installed to the phone first so you will still have that size restriction.
Edit: If someone wanted to make a rom that was bigger then the phones normal partitions they could just package it in the img and just drop it onto the emmc. If any dev's have a rom that's too large for the phone and want to go that route they can contact me and I can help them make the boot.img for it. My goal was just to make install as universal and simple as possible.
Conap said:
I tested with gingersense remix which is sense2.1/3.0 i believe. The system.img i put was 270mb's which is larger then what's on the phone so if it fit's on the phone it will fit on this. That being said you can make the img's whatever size you want but the current install process requires that they be installed to the phone first so you will still have that size restriction.
Edit: If someone wanted to make a rom that was bigger then the phones normal partitions they could just package it in the img and just drop it onto the emmc. If any dev's have a rom that's too large for the phone and want to go that route they can contact me and I can help them make the boot.img for it. My goal was just to make install as universal and simple as possible.
Click to expand...
Click to collapse
ill definitely be pming you
JoelZ9614 said:
lmao i bet i will have more than 4 roms
Click to expand...
Click to collapse
I'm sure you will!
Sent from my Incredible using XDA Premium App
Fine job sir, fine job!
So does this still essentially use up all the EMMC so it's not usable for anything else? or does it only use up what it needs?
Coupled of questions.. sorry if I missed the answers to these questions:
*Does this erase the EMMC, or just adds the necessary "slots"?
*Does this erase your current Rom.. just trying to wrap my head around this...
todd3835 said:
So does this still essentially use up all the EMMC so it's not usable for anything else? or does it only use up what it needs?
Click to expand...
Click to collapse
Good questions...not this only uses what you put on it. With all 4 rom's installed you will only have about 500mb's left though. but you could install just 1 or 2 rom's and still have a couple gb's left to use. The only "problem" i've seen is that the emmc does not mount to pc correctly but this can be fixed by using the mount emmc options in the app i provided.
justjayhere said:
Coupled of questions.. sorry if I missed the answers to these questions:
*Does this erase the EMMC, or just adds the necessary "slots"?
*Does this erase your current Rom.. just trying to wrap my head around this...
Click to expand...
Click to collapse
No does not erase anything on the emmc...just add's the folders and img's
The rom's do get installed to the phone like a normal install and then are copied into the img's. This is so the different rom's with different updater scripts will all install correctly and then just get moved to the img's. It will erase your current rom but you could either nand the current rom(which you should do anyway) and then restore it or you could just use the rom1instaler.zip (or rom2,rom3,rom4) to move your current rom to the emmc. It will copy all of your data and stuff over too. Then you can continue to install the other roms you want. Then if you want to put a rom back on the phone normally you can do that too.
Okay... one more question: let's say I have a Rom installed in one of the slots and I want to flash a mod to that particular Rom... how is that achieved?
Conap said:
Good questions...not this only uses what you put on it. With all 4 rom's installed you will only have about 500mb's left though. but you could install just 1 or 2 rom's and still have a couple gb's left to use. The only "problem" i've seen is that the emmc does not mount to pc correctly but this can be fixed by using the mount emmc options in the app i provided.
Click to expand...
Click to collapse
Ok, so how much space does each "slot" take, just out of curiosity?
Conap said:
No does not erase anything on the emmc...just add's the folders and img's
The rom's do get installed to the phone like a normal install and then are copied into the img's. This is so the different rom's with different updater scripts will all install correctly and then just get moved to the img's. It will erase your current rom but you could either nand the current rom(which you should do anyway) and then restore it or you could just use the rom1instaler.zip (or rom2,rom3,rom4) to move your current rom to the emmc. It will copy all of your data and stuff over too. Then you can continue to install the other roms you want. Then if you want to put a rom back on the phone normally you can do that too.
Click to expand...
Click to collapse
So basically you could get a rom all customized, then do the rom#installer.zip to take it completely themed and all and move to EMMC? That sounds pretty damn hot IMHO =]
so technically can we have 5 roms?
4 on emmc and 1 on actually phone?
*and to resotre nand backup to phone do we install the phoneinstaller.zip first or after the nand backup/rom we like?
justjayhere said:
Okay... one more question: let's say I have a Rom installed in one of the slots and I want to flash a mod to that particular Rom... how is that achieved?
Click to expand...
Click to collapse
Right now flash all your mods before moving the rom...i'll work on some way to flash it after it's moved.
todd3835 said:
Ok, so how much space does each "slot" take, just out of curiosity?
So basically you could get a rom all customized, then do the rom#installer.zip to take it completely themed and all and move to EMMC? That sounds pretty damn hot IMHO =]
Click to expand...
Click to collapse
data is 1000mb system is 270 cache is 120 so about 1.5Gb...they are adjustable if you really want to save the space. and yes you can customize it and then move it.
Pithism said:
so technically can we have 5 roms?
4 on emmc and 1 on actually phone?
*and to resotre nand backup to phone do we install the phoneinstaller.zip first or after the nand backup/rom we like?
Click to expand...
Click to collapse
yep 5 roms total....install phoneinstaller.zip after restoring the nand. It just dumps the boot.img so it's available to the app and installs the app so it doesn't really do anything to the rom.
So what is the "phoneinstaller.zip" used for? Do I need To install that before moving to slot. . Or only For rom left on phone.
Sent from my SmartQ V7 using XDA App
Conap said:
yep 5 roms total....install phoneinstaller.zip after restoring the nand. It just dumps the boot.img so it's available to the app and installs the app so it doesn't really do anything to the rom.
Click to expand...
Click to collapse
wow this is awesome, one of the reason why i just recently purchased a friends INC.
Cant wait to see what other roms work on this
and do we need to use that modified recovery or is cwm 3.0.0.x good enough?
Conap, sick work
You've been busy since I first met you
Sent from my Transformer TF101 using XDA Premium App
justjayhere said:
So what is the "phoneinstaller.zip" used for? Do I need To install that before moving to slot. . Or only For rom left on phone.
Sent from my SmartQ V7 using XDA App
Click to expand...
Click to collapse
That's only need for the rom left on the phone
Pithism said:
wow this is awesome, one of the reason why i just recently purchased a friends INC.
Cant wait to see what other roms work on this
and do we need to use that modified recovery or is cwm 3.0.0.x good enough?
Click to expand...
Click to collapse
CWM recovery is fine...it's what I tested with...
OK so i know a lot of members are intrested in Dual booting their galaxy S2, so i have decided to complice a list of all the dual boot options i can find and have found. I have found two ways as it stands now, but my search has not been that deep yet, so here are the two ways for now and i hope to add more to the list soon.
SGS2 Dual-Boot Setup (LolBoot) - Ok so the first is an app by Hellcatdroid that you can download from Google Play. It only supports GB roms for now, but their is hope that he will put his PSvita down and continue to work on this great app.
Links
Thread
Google Play
SiyahKernel v3.1beta1 Kernel - So option 2 is a kernel from Gokhanmoral, the kernel is stable but the dual boot side is still in beta. This dual boot kernel is working with ICS roms (not GB), Gokhanmoral has tried a dual boot on stock and cm9 and this combo is working, he is pretty sure it will work with MUIU roms. The members on this thread will start to tell of other working combos they have tried, so give this one a go it is looking very good.
Links
Thread
Blog - The blog includes a changelog, and the download link for his kernel
Here is a guide thanks to Phistachio on how to dual boot using Siyah Kernel
[GUIDE] How to Dual Boot using the Siyah Kernel
Here is a fantastic guide, FAQ writen by droidphile for the use with Siyah kernel, it is a fantastic FAQ, so if you use it please go and thank him here -
Dual Booting FAQs
Here are some dual-boot faqs. Some answers may not be 100% true at present since Gokhan is still working on enhancing dual-booting and implementing all the placeholder features in touch recovery dual boot options.
1) So what's dual booting?
A. Option to boot into either two ICS roms - aosp or sammy. Immediately after boot logo is displayed, you will have a 3 seconds time-out where you can boot into secondary rom by pressing the home key. To boot into primary rom, wait for 3 seconds time-out to complete. If you don't like to wait - touch the screen, or press a volume key, or press power key during time-out.
2) What's the basic architecture behind dual booting?
A. Any rom will have /system, /data, /cache partitions and requires a kernel to boot. Primary rom has all these partitions on the same location as if you were single-booting. Secondary rom uses a hidden partition (/dev/block/mmcblk0p9) to be used as /system (it's /dev/block/mmcblk0p12 for primary rom). Second rom uses sdcard to store /data and /cache partitions. They're stored in /sdcard/.secondrom directory as mountable ext4 block device images (data.img and cache.img).
Kernel partition is shared, so same kernel boots both the roms. If you switch from Siyah to a different kernel dual booting will not be available even though you have a clone of secondary rom. Internal sdcard, ofcourse external plastic sdcard, /efs, /emmc, other kernel related virtual filesystem directories, etc are shared among roms.
3) I have just one rom now. How do i setup one more rom to dual boot?
A.
-To use current rom as primary: Assuming the other rom is downloaded and copied to phone memory
i) Flash latest Siyah that supports dual boot.
ii) Nandroid backup your existing rom.
iii) Full wipe, install the rom you need to dual boot into.
iv) Boot into that rom, perform initial setups, flash whatever zip you need to flash on that rom - gapps, themes, mods, etc. (Because after setting up dual boot you don't have an easy way to flash zips onto second rom. Remember /system and /data partitions are different for both roms)
v) Flash latest siyah on this rom.
vi) Boot into recovery, under dual-boot options, select "Clone Primary ROM to Secondary". Be patient and wait about 6-7 minutes.
vii) Within recovery, restore nandroid backup.
viii) Just to be sure, flash latest Siyah again.
-To use current rom as secondary: Assuming the other rom is downloaded and copied to phone memory
i) Flash latest Siyah that supports dual boot.
ii) Boot into recovery, under dual-boot options, select "Clone Primary ROM to Secondary".
ii) Without exiting recovery, Full wipe, install the rom you need to use as primary rom.
iii) Boot into that rom, perform initial setups.
iv) Flash latest Siyah just to be sure.
Now you have two roms. Press home key to boot into second rom when time-out is shown.
4) How much time was it to clone a rom?
A. There's /system, /data/ and /cache to clone. 2 GB data + 103mb cache + 513 mb system = 2.6 gb
Shell prompt read speed = 7mb per second.
Total Time = 2.6*(1024/7) = 380 secs = 6/7 minutes.
5) If i reboot to recovery from power-off state using 3 button method, to which rom's recovery it's booted into?
A. Unified kernel, same recovery. And remember - flashing zips to second rom is not possible.
6) Any solution to flashing zips to secondary rom?
A. Not until secondary rom is "converted" to primary rom. If you know what the updater script in the zip is doing, you can do that manually using Root Explorer (replacing/copy files, setting permissions, etc).
Else, temporarily make secondary rom the primary rom. Goto recovery, dual-boot options, "Clone Secondary Rom to Primary". Now your second rom becomes primary rom. Flash your zips. When you're done, restore nandroid backup of the other rom to make it primary as before.
7) Should i have same versions of kernels on both roms?
A. Flash kernel from any rom. Both uses the same kernel partition anyway.
8) Will i get a prompt to dual-boot if i'm not using dual boot, as in i haven't cloned any rom to use as secondary?
A. NO
9) I don't like waiting for 3 seconds to boot into primary rom.
A. Touch the screen immediately upon prompt.
10) How do i swap primary and secondary roms?
A. Goto recovery, dual-boot options, "Backup secondary rom"
Under original Backup and Restore option, "Backup" to backup your primary rom.
"Restore as secondary rom" or "Restore as secondary rom from internal sd" and select the nandroid backup of what was actually your primary rom.
Then under original Backup and Restore option, "Restore" to restore the rom you backed up as secondary.
11) USB mass storage works?
A. Only external sd is mounted for second rom atm. MTP will work for internal sd also. Both will be mounted for primary rom.
12) If i had the same /data partition shared between roms, i could use same apps on both roms.
A. Data partition can not be shared as they're incompatible between roms. (Sometimes dev asks you to perform full wipe even if you're switching between versions of the same rom right). Even if they were shared, separate dalvik caches has to be used and hence every boot will take a long time to rebuild dalvik.
13) How to undo dual booting?
A. Use "Remove secondary rom" from dual-boot options in recovery.
14) How to remove secondary rom if "remove secondary rom in recovery" fails for some reason?
A. Format /system2 directory partition, remove data.img and cache.img under /sdcard/.secondrom directory manually by booting into primary rom.
15) How to upgrade primary rom?
A. As usual, goto recovery, wipe whatever you need to wipe and install the new version.
16) How to upgrade secondary rom?
A. Temporarily convert secondary rom to primary (like explained above), install new version and revert primary back to secondary.
17) How to replace secondary rom with another?
A. Perform the steps to setup dual boot as if you had only one rom which is going to be used as primary rom.
18) How to replace primary rom with another?
A. Normal procedure - wipe, install from recovery.
19) Can i have both aosp roms/both samsung roms/first aosp, second samsung/first samsung,second aosp?
A. Yes
20) Can i have one GB rom and second ICS rom?
A. No
21) Why?
A. Kernel partition is shared between roms. Dual boot functionality is implemented in ICS kernel. ICS kernel can run only ICS roms.
22) Are init.d scripts and extweaks profiles shared across the roms so that i can make changes by booting into any rom and the other rom automatically inherits the settings?
A. NO. Roms have differet /system partitions so different init.d directories. Roms uses different /data partitions and extweaks profiles are stored under /data/.siyah. So you gotta configure both separately. Initramfs scripts are shared anyway since both rom uses the same kernel.
23) So if at all i format /sdcard, my second rom is gone?
A. Yes
24) Is the size of /system partition of secondary rom re-sizable from user space?
A. NO
25) Can i have different kernels for the two roms?
A. NO
26) What're the options under dual-booting in touch recovery?
A. i) View Status
Displays secondary rom info if found.
ii) Clone Primary ROM to secondary
First time, you will have only one rom. You may clone it as secondary rom (so that another rom can be used as primary by nandroid restoring)
iii) Clone secondary rom to primary
Whatever has been cloned as secondary rom is cloned to primary rom.
iv) Remove secondary rom
Deletes /system, /data and /cache partitions of second rom. You will have normal booting.
v) Backup secondary rom
Nandroid backup secondary rom to external sd.
vi) Restore as secondary rom
Restore any nandroid backup as secondary rom from external sd.
vii) Backup secondary rom to internal SD
Nandroid backup secondary rom to internal sd.
viii) Restore as secondary rom from internal sd
Restore any nandroid backup as secondary rom from internal sd.
ix) init second rom data
Initialize /data parition of secondary rom to resize the partition to make it bigger in case you run out of space for apps. Init also wipes all the data in /data partition. So your existing apps in secondary rom will be gone.
x) wipe second rom davik cache, xi) wipe second rom cache, xii) fix permissions in second rom - self explanatory
Click to expand...
Click to collapse
I am now running a Dual Boot galaxy s2, using Siyah Kernel by Gokhanmoral, i am running CM9 and Resurrection Remix ics v1.2 PRO[4.0.4]
This is what i have got for now, but i am always looking for more dual booting options, if anyone knows of any please let me knowand i can add it to this thread.
If you have found this thread usfull then please hit the Thanks button
Nice work again fella
You should request this and your other thread are made into sticky's
Also, im hoping these two threads will help to stem the flow of threads and questions for previously trodden ground
Keep it up dude
Thanks man, the XDA community has give me so much, I just want to give back. It would be nice to see these as stickies, maybe the FM would be kind enough to consider placing them on the sticky thread.
Sent from my GT-I9100 using XDA
I am now running a Dual Boot galaxy s2, using Siyah Kernel by Gokhanmoral, i am running CM9 and Resurrection Remix ics v1.2 PRO[4.0.4]
I am now running a Dual Boot galaxy s2, using Siyah Kernel by Gokhanmoral, i am running SensatioN ROM 3.3 ICS by Crysis21 as Primary and CM9 as Secondary.. can anyone tell me any app so that i can automatically sync both rom 's SMS, Phone log and Phone Contact.. i know manual process..
What are the pro's/con's of dual booting? Cheers
Sent from my GT-I9100 using Tapatalk
shareking said:
I am now running a Dual Boot galaxy s2, using Siyah Kernel by Gokhanmoral, i am running SensatioN ROM 3.3 ICS by Crysis21 as Primary and CM9 as Secondary.. can anyone tell me any app so that i can automatically sync both rom 's SMS, Phone log and Phone Contact.. i know manual process..
Click to expand...
Click to collapse
You can use Rom Manager to Extract the apps and data from your nandroid backup, or another app that does the same is Nandroid Browser, you can get both of google play. Just as a side note, you should get an automation sync of data when flashing a new rom, as google now store all you apps and setting in the cloud, if you check in your settings it should be under Backup and reset - back up my data - check the box, and you should have an auto sync for your next rom flash.
blade30p said:
What are the pro's/con's of dual booting? Cheers
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
For me it is just the chance to have a change never getting bored of the same rom, the con is using a dual boot that is still in better and is buggy at the moment, which may cause problems with your rom mainly the 2nd rom, also the storage of data is causing some people problems, but the thread is give good solutions.
Dual booting rocks. android rules...
Thank you for this guide
So there is an option to boot two GB ROMs but no ICS and now we can boot two ICS ROMs but no GB...
The third option should be... - you know it
Sent from my GT-I9100 using XDA
Probably get flamed - btw, I don't care one jot - but why on earth should this be stickied?
This isn't a guide, it's a post with two links to the relevant threads, where the discussion is going to be a lot more useful than anything here.
s.d. o'connor, your other guides are guides, and are very useful, for which my thanks. This one isn't.
Flame-retardant pants on - fire away.
My defence
B3311 said:
Probably get flamed - btw, I don't care one jot - but why on earth should this be stickied?
This isn't a guide, it's a post with two links to the relevant threads, where the discussion is going to be a lot more useful than anything here.
s.d. o'connor, your other guides are guides, and are very useful, for which my thanks. This one isn't.
Flame-retardant pants on - fire away.
Click to expand...
Click to collapse
Why would you get flamed for having an opinion, you are entiled to that, but here goes my defence. I could only but ask if it could be a sticky i didnt make it one, and the idea is to stop new threads being opened asking the question can you dual boot the galaxy s2. Also as more options of dual booting become avaiable then they can be added to this thread.
P.S I dont want people to get flamed for having a opinion, they have a right to that, as long as they put that across in a good manner.
You don't need a defence (unlike Leeds United, but that's another story).
Flaming is an occupational hazard here sometimes, especially if someone has the temerity to diagree with someone else. I'm way past worrying anyway.
On topic - I still don't think this deserves sticky status. You and others do. No problem. Each to their own. It's up to the mods anyway, not us.
No foul on you SD O'C because you've put together some really good threads, but if this is 'sticky worthy' standards have plummeted on XDA. Rapidly. As has been pointed out, there's a couple of links & pretty much no original content or anything that could remotely be considered a 'guide'.
Droidphile's excellent dualbooting post in the Siyah dev thread a few days ago, now that was a guide (and sticky worthy).
okay, i am on dual boot. using LPQ as primary and cm9 latest nightly as secondary
and i note battery drain
MistahBungle said:
No foul on you SD O'C because you've put together some really good threads, but if this is 'sticky worthy' standards have plummeted on XDA. Rapidly. As has been pointed out, there's a couple of links & pretty much no original content or anything that could remotely be considered a 'guide'.
Droidphile's excellent dualbooting post in the Siyah dev thread a few days ago, now that was a guide (and sticky worthy).
Click to expand...
Click to collapse
What post number is it and i can include it and give him full credit, i will of course ask first. Also i would like to point out this was never intended as a guide, more a point of ref.
P.S If LUFC would like to change his mind on this being a sticky then i would have no problem with this.
ashifr5 said:
okay, i am on dual boot. using LPQ as primary and cm9 latest nightly as secondary
and i note battery drain
Click to expand...
Click to collapse
Battery drain has been noted with the kernel, he has made a fix for most roms and combo's but he will need time as it is still in the early stages. Also when flashing a new rom this can alter the casuse battery drain, a full charge of the batter could fix this problem.
MistahBungle said:
Droidphile's excellent dualbooting post in the Siyah dev thread a few days ago, now that was a guide (and sticky worthy).
Click to expand...
Click to collapse
Here it is, for all the non-searchers.
Off-topic again - s.d.oconnor, to quote an earlier post from yourself:
s.d.oconnor said:
Thanks man, the XDA community has give me so much, I just want to give back.
Click to expand...
Click to collapse
If so, what's the "donate to me" banner doing in your signature? Just awaiting love and affection?
You've compiled some useful guides, but let's face it, your work has mainly been collating readily available links and other posts that any reasonable modicum of searching ability could accumulate.
Nothing in the site rules that forbids you to ask for donations, but for what you've done - especially taking into account that you've been a member here for two months - I can think of an awful lot more contributors ("recognised" or not) whom are far more worthy of donations than yourself.
The "giving back to the community" spiel is very valiant and honourable, but you want donations. Fine, sure you've got some too. But don't dress it up behind the "giving back" line - not exactly sincere, no?
Again, I'm not flaming/trolling - merely my opinion.
B3311 said:
Here it is, for all the non-searchers.
Off-topic again - s.d.oconnor, to quote an earlier post from yourself:
If so, what's the "donate to me" banner doing in your signature? Just awaiting love and affection?
You've compiled some useful guides, but let's face it, your work has mainly been collating readily available links and other posts that any reasonable modicum of searching ability could accumulate.
Nothing in the site rules that forbids you to ask for donations, but for what you've done - especially taking into account that you've been a member here for two months - I can think of an awful lot more contributors ("recognised" or not) whom are far more worthy of donations than yourself.
The "giving back to the community" spiel is very valiant and honourable, but you want donations. Fine, sure you've got some too. But don't dress it up behind the "giving back" line - not exactly sincere, no?
Again, I'm not flaming/trolling - merely my opinion.
Click to expand...
Click to collapse
Ok, the banner donate to me has been their since i joined as you are giventhe option to include one, i was new (still am), i have not recived any donations, and if i did they would be used to go back to the XDA website, if it offends anyone i will remove the banner. Also if any mod belives that i am not worthy of my title and that my guides are not of the standard that is very good then they can by all means remove them from any sticky they may be on, and remove my title if they see fit.
I know you are saying that you are not flaming me, but it seems to be moving in that direction. I know i have only been here a short while but i belive that what i have done is not that bad of a standard, in the short time i have been here.
Hi guys.
Yesterday I got a used HTC HD2. It is installed with android nand and the DFT (Dark Forces Team) rom, I think taken from the DESIRE (according to the information on the 'About').
The main problem in the device is that it has really bit memory! After installing few apps, I cant download a thing :/
So I searched for the problem and I've realized that I need to make a partition on the SD-CARD. However I saw that in the market there are apps that allow moving the application that can only sit in the internal memory to the external memory.
I then found out that the phone doesn't have root access too. (Although it came with SUPERUSER app as default).
I can't find the main thread of the rom in order to ask there how to root the device.
Which software / app, will I need recovery installed (althogh I don't think it requires) and ETC.
Please can someone direct me or just give me names of apps/softwares/guides/anything :crying:
I guess GOOGLE could be my assitstant from there.
I'm afraid to follow guides that I don't sure will work properly with my phone's software.
Thank you.
pelegm28 said:
Hi guys.
Yesterday I got a used HTC HD2. It is installed with android nand and the DFT (Dark Forces Team) rom, I think taken from the DESIRE (according to the information on the 'About').
The main problem in the device is that it has really bit memory! After installing few apps, I cant download a thing :/
So I searched for the problem and I've realized that I need to make a partition on the SD-CARD. However I saw that in the market there are apps that allow moving the application that can only sit in the internal memory to the external memory.
I then found out that the phone doesn't have root access too. (Although it came with SUPERUSER app as default).
I can't find the main thread of the rom in order to ask there how to root the device.
Which software / app, will I need recovery installed (althogh I don't think it requires) and ETC.
Please can someone direct me or just give me names of apps/softwares/guides/anything :crying:
I guess GOOGLE could be my assitstant from there.
I'm afraid to follow guides that I don't sure will work properly with my phone's software.
Thank you.
Click to expand...
Click to collapse
look for guides in this forum...about nativSD and dataonEXT...very helpful (that's how i learned what i need to know about the device)...also i recommend to change the rom to a better or newer version of android...you will also find guides about changing the rom...
eliaskammas said:
look for guides in this forum...about nativSD and dataonEXT...very helpful (that's how i learned what i need to know about the device)...also i recommend to change the rom to a better or newer version of android...you will also find guides about changing the rom...
Click to expand...
Click to collapse
Hi,
Thank you for your kindly help.
Which Android version do you suggest to change to ?
ICS ? Or maybe GingerBread ?
And BTW I entered before to the MAGDLR menu, chosed the " AD Recovery " option and it said something like " no boot source ".
Does that mean that I don't have a recovery installed ?
And if so, will I need to install it first and then change the rom ?
Again, Thank you for your help.
Peleg.
yes you will need recovery...fast roms are mostly GB but ICS are as good as well...GB need less space on rom memory so if you don't install alot of craps as most of us do the remaining space will be fine for your data...ICS have hwa, apps work faster and games play better..I recommend ICS by tytung to be honest(very fast and stable)...when you download the recovery you will see a "flash.cfg" file...on the rom thread the developer will state the partitions needed for his rom and so you change the numbers on that file accordingly before flashing the recovery...but always make system space little bigger than needed just in case(and to avoid other problems that i will have a finger cramp if i write them down.! )
eliaskammas said:
yes you will need recovery...fast roms are mostly GB but ICS are as good as well...GB need less space on rom memory so if you don't install alot of craps as most of us do the remaining space will be fine for your data...ICS have hwa, apps work faster and games play better..I recommend ICS by tytung to be honest(very fast and stable)...when you download the recovery you will see a "flash.cfg" file...on the rom thread the developer will state the partitions needed for his rom and so you change the numbers on that file accordingly before flashing the recovery...but always make system space little bigger than needed just in case(and to avoid other problems that i will have a finger cramp if i write them down.! )
Click to expand...
Click to collapse
Thank you.
I will first install the recovery, but I guess I'll have to read a lot before:
http://forum.xda-developers.com/showthread.php?t=1021837
Then I will search for a guide for installing recovery-
CWM will be great right ?
Thank you very much !!! :laugh:
The guide you linked is very useful and makes everything clear. I strongly recommend reading it thoroughly before doing anything. Once you're slightly more comfortable with the terms, you can follow the guide in my sig to flash CWM and a ROM. You already have HSPL, a compatible Radio version and MAGLDR installed so don't worry about any of those. If you happen to come across guides which say 'task29' just ignore that step, Task29ing is completely useless.
As for recommending a ROM, it depends on your usage. Eliaskammas' post sums it up nicely, but you should note that (IMO) ICS and JB will give you worse day to day performance and stability than GB but will be better for intensive activities e.g. gaming, web browsing, using content-heavy apps etc. I've also found battery drain to be marginally more on ICS and JB ROMs.
Nigeldg said:
The guide you linked is very useful and makes everything clear. I strongly recommend reading it thoroughly before doing anything. Once you're slightly more comfortable with the terms, you can follow the guide in my sig to flash CWM and a ROM. You already have HSPL, a compatible Radio version and MAGLDR installed so don't worry about any of those. If you happen to come across guides which say 'task29' just ignore that step, Task29ing is completely useless.
As for recommending a ROM, it depends on your usage. Eliaskammas' post sums it up nicely, but you should note that (IMO) ICS and JB will give you worse day to day performance and stability than GB but will be better for intensive activities e.g. gaming, web browsing, using content-heavy apps etc. I've also found battery drain to be marginally more on ICS and JB ROMs.
Click to expand...
Click to collapse
Hi.
Thank you for your advices and technical help.
I will read it as soon as possible and then try to install the CWM Recovery and a better Rom.
According to what I saw, I think I will go on the "Energy rom" (Sense 3.5).
I will probably update my progresses here.
Thank you a lot.
BTW, a deodexed rom is needed for languages that are written from right to left ?
Or that I have to find a rom supports RTL ?
Beacuse for example, I've searched the thread of the Energy rom for "Hebrew" and found out that it doesn't supports RTL :/
Thank you.
I don't want to confuse you but I personally have always found Sense based ROMs to be slow and I think you should really stick to CM or MIUI. Anyway, that's really just my opinion.
Unfortunately, I think that you may have to find a ROM which supports RTL. I haven't looked into it but there may well be an app which somehow makes it work. If you're desperate for Android with Sense and RTL support then you could consider some of the SD ROMs from boxmax, he made good SD ROMs (at least when I used it), but I don't know which NAND ROMs will work for you.
Nigeldg said:
I don't want to confuse you but I personally have always found Sense based ROMs to be slow and I think you should really stick to CM or MIUI. Anyway, that's really just my opinion.
Unfortunately, I think that you may have to find a ROM which supports RTL. I haven't looked into it but there may well be an app which somehow makes it work. If you're desperate for Android with Sense and RTL support then you could consider some of the SD ROMs from boxmax, he made good SD ROMs (at least when I used it), but I don't know which NAND ROMs will work for you.
Click to expand...
Click to collapse
Hi Nigeldg.
I took your advice and I think I will go on this rom:
http://forum.xda-developers.com/showthread.php?t=1639932
It supports rtl and data2ext.
But do I need to change my HD2's kernel ? To Dorimanx 's kernel ?
And from the guide that you've recommended on before, do I need to start from this part:
http://forum.xda-developers.com/showpost.php?p=12656427&postcount=3
And to skip the other parts ?
I've read the hole guide and it is very helpful.
Everything is really clearer.
There's no need to change the kernel after flashing, but you can if you want to. I think the dorimanx krrnel is included in that rom anyway so i don't see why you'd want to flash it again. Follow the new way method and everything should be fine. You can use the NAND toolkit to select the appropriate partition size.
Nigeldg said:
There's no need to change the kernel after flashing, but you can if you want to. I think the dorimanx krrnel is included in that rom anyway so i don't see why you'd want to flash it again. Follow the new way method and everything should be fine. You can use the NAND toolkit to select the appropriate partition size.
Click to expand...
Click to collapse
Hi Nigeldg.
I now want to install the CWM (long time hh)..
In this rom:
http://forum.xda-developers.com/showthread.php?t=1639932
It says to install CWM with this partition size:
" Flash the Latest CWR (Clockwork Recovery) with the appropriate partition sizes by using the "Repartition" button inside the HD2ToolKit: System: 200MB | Cache: 5MB "
In the thread of CWM: http://forum.xda-developers.com/showthread.php?t=898913
Can I change the partition sizes used for CWM
A. You can by editing the flash.cfg but this is not recommended, CWM is designed to make it easier for switching roms, by flashing a custom partition size you may stop other roms working and require reflashing a new partition size when you want to change roms.
Q. I dont know which partition size to download
A. Depending on what type of roms you plan on using, you should choose the partition size based on the following.
150MB Partition - For bare roms including CyanogenMod, AOSP, and MiUI
250MB Partition - For Standard sense roms including Desire and EVo based ROMs, can also be used for some squashed HD builds
400MB Partition - For Larger roms including unsquashed Desire HD and Z roms, ROMs REQUIRE data2sd for EU HD2 with 512MB NAND
And in the thread in your sig it is possible to download 3 version of the CWM. (150, 250, 400).
How do I need to install the CWM ?
To download the 250MB version, and using the HD2ToolKit to change the partition size and install with System: 200MB | Cache: 5MB (as the rom developer suggested) ?
Thank you!
The thread you've linked to is the old CWM thread. I don't see why it says that you shouldn't change the partition sizes because that's simply not true, pretty much all ROMs use custom sizes. Ignore that advice, it's wrong. In my opinion the easiest thing to do is to download the HD2 NAND Toolkit, click 'MAGLDR repartition', choose 200 and you're done.
Nigeldg said:
The thread you've linked to is the old CWM thread. I don't see why it says that you shouldn't change the partition sizes because that's simply not true, pretty much all ROMs use custom sizes. Ignore that advice, it's wrong. In my opinion the easiest thing to do is to download the HD2 NAND Toolkit, click 'MAGLDR repartition', choose 200 and you're done.
Click to expand...
Click to collapse
Ok.
So I've downloaded the HD2 ToolKit.
Actually what I need to do is this:
1. To choose the 200MB and 5 Cache and then press repartition. (In what way does the phone need to be ? MAGDLR Menu, or other option ? )
2. Then to install the CWM by going to MAGDLR - USB Flasher, connect to the computer, and run the
DAF.exe.
Right ?
1. Open the toolkit
2. Click the MAGLDR repartition tab and select 200 and change the cache size to 5
3. Click 'repartition' (bottom left of the toolkit)
4. Follow the instructions it gives you (boot your phone into USB flasher mode then connect it to your PC) and let it flash.
Nigeldg said:
1. Open the toolkit
2. Click the MAGLDR repartition tab and select 200 and change the cache size to 5
3. Click 'repartition' (bottom left of the toolkit)
4. Follow the instructions it gives you (boot your phone into USB flasher mode then connect it to your PC) and let it flash.
Click to expand...
Click to collapse
And once I've finished this, I need to install the CWM.
To donwload the 250MB version ?
pelegm28 said:
And once I've finished this, I need to install the CWM.
To donwload the 250MB version ?
Click to expand...
Click to collapse
I don't think you understand, THIS IS INSTALLING CWM :') After you've done this, just flash the .zip ROM and you'll be done
Nigeldg said:
I don't think you understand, THIS IS INSTALLING CWM :') After you've done this, just flash the .zip ROM and you'll be done
Click to expand...
Click to collapse
If I've already did it, just do this thing again and it will work ?
because now my phone cant load to the rom, it says NAND Kernel something and boots up to MAGDLR.
Is it OK ?
EDIT:
I've did it and chosed the "AD Recovery" option.
Now I can see that I have CWM Recovery!!
I thought that I had to choose somehow to install the CWM, and that's why I didn't understand.
Now,
Do you recommend to do wipe data/factory reset and wipe cache ?
And after that to install from CWM the ROM that I've transferd to the Root of the SD right ?
Thank you very much !!!
You don't need to wipe anything, that already happened when you flashed CWM. Yes you should just have to flash the ROM now, as said in the guide in my sig. You may want to create an EXT partition but for your particular ROM it's not a necessary step so you can skip that. Glad I could help
Nigeldg said:
You don't need to wipe anything, that already happened when you flashed CWM. Yes you should just have to flash the ROM now, as said in the guide in my sig. You may want to create an EXT partition but for your particular ROM it's not a necessary step so you can skip that. Glad I could help
Click to expand...
Click to collapse
It isn't necessary because it automaticly transfer the data to the SD ?
During the installation a message showed up saying that the rom identified that I don't have an EXT-partition installed.
Can I make a partition using the CWM/ADVANCED/PARTITION-SD ?
Thank you so much for your help!!
You saved me, and becuase of you I didn't sell the phone.
Thank you!!
It isn't necessary because the ROM itself is quite light, so all of it can be fit on to the NAND memory. It would help to create one because you may need it in the future, so I personally would if I were you. The way you described would work fine