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
Related
Hi all...
I've been getting a lot of suspicious errors recently (force closes and app shortcut names disappearing) and I'd like to go from apps2sd back to just a normal setup with my apps on the internal phone storage.
Can somebody please verify that the instructions here are up to date? I'm a little nervous about wiping my data (or bricking my phone).
http://wiki.cyanogenmod.com/index.php/Apps2SD
Also, can somebody tell me whether doing this will wipe out the (single) app I paid for from the Marketplace? If so, can I redownload it, or will I need to pay for it a second time?
I originally got apps2sd set up by using the recovery ROM prior to flashing Modaco's custom ROM v1.1.
The easiest thing to do would be to load the new RA 1.5.1 recovery image.
Then boot into it.
Go to Partiton SD
Select FAT EXT3 SWAP
and then set the partition sizes of EXT3 and SWAP to 0
Is there a reason you want to do this???
This runs a very very minimal chances of bricking your phone. The other method on that Wiki page has more potential to get you in trouble.
Did see the market place question.
There is a method laying around somewhere to copy all of your apps back to the phone instead of loosing them. Restoring a Nandroid backup would likly put them all back into the /apps/ directory sd card or not. apps2sd just changes the location of that directory really.
But the market does keep track of your google account and what apps you purchase, you wont have to re purchase (maybe on a totaly new handset).
hope my jiberish has made sense
jashdlfjasdhfjablgjkasgjlkasfhlajshf
At first I was interested in the whole apps2sd process, but have yet to implement it on my rooted, Fresh 1.0 Hero since so far, I haven't really seen a need for it.
But if you were to 'turn on' apps2sd and then decide later that you don't want it, there's a possibility of bricking?? Although I assume you can always reflash the RUU if something like that were to happen? Hopefully?
Think I'll stay away from the whole offloading applications thing for awhile.
mkhopper said:
At first I was interested in the whole apps2sd process, but have yet to implement it on my rooted, Fresh 1.0 Hero since so far, I haven't really seen a need for it.
But if you were to 'turn on' apps2sd and then decide later that you don't want it, there's a possibility of bricking?? Although I assume you can always reflash the RUU if something like that were to happen? Hopefully?
Think I'll stay away from the whole offloading applications thing for awhile.
Click to expand...
Click to collapse
The possibilities of bricking the phone are very slim, but they still exist. If a phone is truly a brick, not even RUU can help. RUU has to be able to detect the phone is there in Windows, so if its beyond that RUU is useless.
Nothing to worry about as long as follow the *usually* very well written step by steps across the interweb.
If it makes you feel any better I have only heard of one or two people to brick the Hero. Most things are recoverable.
Yeah, sorry, I didn't expect it would brick the phone so much as badly mess it up - like if it expects to run apps from the SD card and they aren't there I could see the phone being tough to use as a phone, but it wouldn't really be "bricked" in the sense of not responding to user input at all.
As far as why I want to do this, I haven't really seen a huge need for apps2sd yet, and when I was recently helping an app developer to debug their app it was just one more weird variable that seemed like a possible source of problems. I'm also hoping to start developing apps myself soon, so having a more vanilla phone seems like a good idea. (I also was influenced by the Fresh ROM apps2sd rant, to be honest.)
Anyhow, thanks for your replies. I'll probably repartition the card from RUU and then restore from Nandroid at that point. Will a repartition wipe the card filesystems out, or is the partitioner smart enough to preserve the existing data?
What I did is RUUed back to 1.2, OTA updated to 1.6
Flashed to the 1.5.1 image
(At this point I went to mess with the partitions and there was no ext)
Flashed to Fresh 1.0
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 )
In a conversation with enatefox recently he asked if it was possible to dualboot an android phone, I thought it was and set out to make that happen. This is that work.
This is a VERY EARLY BETA! It does function, but its rough. Don't expect this to be smooth or easy yet.
This image is based on Amon-RA-v1.6.2
What you need to do:
This hack will boot a rom from SDCard. It expects to see system.img and data.img on the sdcard as well as init.rc.
System.img needs to be a disk image of a filesystem that the kernel can read(I've been using ext3) around 170MB(Thats the Eris's NAND size for system)
data.img needs to be a disk image of a filesystem that the kernel can read(I've been using ext3) as big as you'd like your data partition to be(This holds your apps etc, so a couple hundred megs is good)
init.rc needs to be the init.rc of your rom with two changes
You need to remove the lines where it mounts /system and /data.
Once you have those three files on your sdcard, and have flashed this recovery you're ready to try your first boot.
Reboot into recovery, you'll see the normal usual recovery menu(I'll add an item eventually)
connect to the recovery console with adb
run 'adb shell /bootfromsd'
It will APPEAR to have done nothing for a bit, this is normal. Its booting your rom now. Once it gets to the place in the rom where it would display the splash screen, you'll get a splash as usual. You can watch it with logcat if you like.
I've personally booted the following roms from SD.
KaosFroyo
KaosLegendary
CELBFroyo
MR4
PlainJane
Good luck!
V1: http://www.multiupload.com/UJNJLQWL17
If you like my work, think about donating to my coffee fund.
So do the roms you load from SD run just as smooth as a normal one?
tjthebest said:
So do the roms you load from SD run just as smooth as a normal one?
Click to expand...
Click to collapse
depends on the speed of your SD. Theres a tiny bit of lag on the class 2 I tried it on, but it would likely be fine on a faster card.
Sounds freaking awesome! Can't wait to try
This is freaking awesome kaos sir you did it again +1 tyvm
Ill be trying this tonight!
Thx
Btw i love u kaos
Sent from my ERIS using XDA App
this as well as the herculean update schedule of KaosFroyo convinces me that Punk.Kaos should have his own kids show.
"But Punk.Kaos! that's impossible!"
Punk.Kaos appears in a superhero outfit with a silvered cape, poses and says,
"No little Jenny. Impossible is only what we have yet to try."
This reminds me of trying XDAndroid on my Diamond.
MrObvious said:
This reminds me of trying XDAndroid on my Diamond.
Click to expand...
Click to collapse
Heh, kinda the same idea
Class 4 16GB =)
[ Sent from my HTC Droid Eris | KaosFroyo v34 ]
I didn't understand all that stuff...but I like it!
Kaos rules.
Say Hi to enatefox for me, he used to handle the kaiser back in the vogue android days....
Damn this dudes smart as hell
quick question kaos, so when i want to boot to a different rom i have to adb it on recovery every time??
rrem said:
quick question kaos, so when i want to boot to a different rom i have to adb it on recovery every time??
Click to expand...
Click to collapse
Right now. Im working on making it a bit more user friendly.
I bow to you sir, you make the Eris world go 'round! (Amongst other worlds I'm sure
Thank You.
punk.kaos said:
Right now. Im working on making it a bit more user friendly.
Click to expand...
Click to collapse
Oh, alright Thanks for all your hard work even at this state this is so awesome
This is some incredible work. I wish I could donate. .I'm kind of speechless....just some ill work being done by you kaos.
Sent from my FroyoEris using XDA App
not getting time to try to night kaos, maybe tomorrow. or i may wait till a newer release.
if you need a tester for a newer build. let me know ill be glad to lend a phone out to ya.
just pm me if you want that i test for you.
thanks again kaos.
Very excited to try this out... thanks Kaos!!!
Question though, do we need to generate the .img files ourselves, or do we get the .img files from a nand back up of the ROM we want to be able to boot from?
After some thinking about how I wanted to pursue this project and the recent release of an app that has made this possible, I decided to start working on an app of my own. While I have no experience in making an app, I have already begun working on it. Boot Manager is an awesome app for those that like flashing and running different ROMS frequently, however I have found some things that I do not like about it and features that could be added. My short term goal is to create an app with support for either 2 or 3 Roms and would be free. I'll then release a paid one that will support 5 or more roms and add some other features.
As I said, I have already begun working on it and although it won't utilize the method I wanted to use, I will implement some of it in the future. Right now I have parts of it setup and can already use certain features, but for anyone that has created an app, you know there is a lot of scripting that needs to be done.
Thanks to Conap for the motivation to get my a** back on track.
Partition your sdcard
PARTITION YOUR SDCARD
I have made this really easy to partition your sdcard while preserving all data on the fat32 partition.
You have the option of specifying the size of the ext partitions in /sdcard/dualbootmap.txt
Code:
adb shell
echo 150 200 0 > /sdcard/dualbootmap.txt
The 1st number is cache partition for both rom2 in Mb. For right now I would not do anything less than 125 until I incorporate settings for dalvik-cache on data.
The 2nd number is ROM2 data partition in Mb. Pick whatever size you want.
The 3rd number which isn't used yet will be for a2sd on ROM1. For now this should be kept at 0.
If there is no dualbootmap.txt file the partitions will be automatically set to
cache=150
data=200
a2sd=0
Make sure you have enough free space on the card to accommodate the extra partitions plus an extra 200. If you only have a fat32 partition and use the default values above you would need 550mb of free space. After setting up the roms you will get the extra 200mb back. Its just used as temporary storage.
INSTRUCTIONS:
1. Download sdpart.zip
2. Reboot into recovery
Code:
adb shell reboot recovery
3. Unzip the contents of sdpart.zip and push the files inside sdpart folder to /tmp/
Code:
adb push c:\xxxxxx\sdpart /tmp/
4. run /tmp/sdpart.sh in adb shell
Code:
adb shell /tmp/sdpart.sh
If sdpart.sh doesn't run then you will have to chmod it before running it, but it should already have permission to run.
Code:
adb shell chmod 777 /tmp/sdpart.sh
HELP
Reserved until release day
Can't wait to try it out.
Is it going to support the aria?
12c00000-257fffff : System RAM
THANKS
Sent from my HTC Liberty using XDA App
FFXTDS said:
Can't wait to try it out.
Is it going to support the aria?
12c00000-257fffff : System RAM
Sent from my HTC Liberty using XDA App
Click to expand...
Click to collapse
Updated OP. Thats it for today. I'll post others in the morning
Can I restore a nandroid and then flash the dualboot.zip to make that Rom store to SD instead of wiping everything and flashing the roms?
jblazea50 said:
Can I restore a nandroid and then flash the dualboot.zip to make that Rom store to SD instead of wiping everything and flashing the roms?
Click to expand...
Click to collapse
You should be able to as long as there is a boot.img in the nandroid which I think there is
I really like this idea. Is there any way that you could modify a recovery to incorporate a bootloader? I believe clockwork is open source and should allow for this to be possible.
I don't know any c programming, but am looking at alternatives. Maybe an app or 1 script that does everything.
Sent from my HERO200 using XDA App
This is F'in epic dude. Thank you!
got this working on my evo,
1. what if i want to flash a new nightly or a update, do i go through the process again? and does it matter if it's on the SD or Phone?
2. how do you nandroid the rom on the SD?
basically should i keep CM6.1 on the Phone or the SD for easy updating
EDIT: i lied it works then when i tried to boot to SD it just sat at the white screen. going to play around with this some tonight
Wow man. This is freaking amazing. I'm definitely going to give this a try. Run CM as my daily rom, but this will help when I am traveling to 4G areas, and I can just flip over to a Sense rom.
Awesome, awesome work.
so if i wanted to put cyanogenmod nightlys on and then update them to a newer nightly version how would i do that without redoing everything?
edit: been messing with this and had my question sitting without hitting submit for like 15 min and apperently in that time someone else asked same question
I can't figure out how to get my base address... Can someone please explain more... I'd love to use this on my incredible
Sent from my Incredible using XDA App
Booting into the rom on the SD doesn't seem to be working. The phone just stays at the initial boot screen. This happens whether I have CM6 or a Sense rom on the SD.
sd card
So how is the speed when running on a class two SD card or a Class 4
Does the rom bog down?
Tried it and when I tried to boot into the rom on sd it got stuck on splash screen. Running miui on phone and had ava 10 on sd.
Sent from my PC36100 using XDA App
PikkonX said:
Booting into the rom on the SD doesn't seem to be working. The phone just stays at the initial boot screen. This happens whether I have CM6 or a Sense rom on the SD.
Click to expand...
Click to collapse
What recovery and phone do you have. Run this from command or terminal and post inside code tags
Code:
adb shell cat /sdcard/dualboot/recovery.log
or attach /sdcard/dualboot/recovery.log so I can look at it. It sounds like I may have the wrong base address. I'm going to sleep now. but will check and update this in the morning
kevinniven said:
So how is the speed when running on a class two SD card or a Class 4
Does the rom bog down?
Click to expand...
Click to collapse
im no expert to android, linux, sd cards (lol)... but i think it doesnt matter, once the ROM is loaded it runs off the phone's memory, so the speed shouldnt be affected.
somebody correct me if im wrong
PikkonX said:
Booting into the rom on the SD doesn't seem to be working. The phone just stays at the initial boot screen. This happens whether I have CM6 or a Sense rom on the SD.
Click to expand...
Click to collapse
yeah i'm getting the same thing wont get past initial bootscreen
Phone = HTC EVO rev 0003
recovery = psfMod 0.7.2 (aka clockwork)
sdcard = 8gb (w/2.2gb free)
and i checked my adress base before hand so i know i got correct one
i will try again tomorrow as i gotta get some sleep now
Hi. Maybe few words about me first. I'm not a developer, I don't know how to do it and I have to ask more experienced users. Ok that's it, to the point now. Ah, and I didn't know if this thread was proper to be posted in Development sub-forum, so it's here. If it was possible, if the thread meets requirements to be there, maybe it's possible to move it there? I'm not sure how many devs visit those section, so obviously there is greater chance for finding an answer there, but again, I wasn't sure if it was right.
While I was a G1 user one genius known as "Firerat" created very nasty script - it allowed users to manually, by simply creating a .txt file on sdcard with proper values and running a .zip from recovery, resize partitions like /system, /data and /cache on the phone. I don't know if you're familiar with G1 stuff, but previous there was only one way to chage partitions and it was achieved by custom SPL called Haykuro SPL. This modification (MTD part hack) was created because of need for even more space on /data and allowed to shrink /system and /cache to smallest value possible, so /data took up as much space as it was possible. Here is source thread in G1 Development section:
http://forum.xda-developers.com/showthread.php?t=717874
There you can dive in details, because my knowledge and understanding in this things end very quickly .
On HD2, we have come a great way. From pure Windows Mobile, it was possible to run Linux kernel from sdcard by HaRET.exe, then run Android. After few month team of gods gave us MAGLDR, a tool that allows us to replace Windows Mobile from NAND with Android system. Then after few more weeks someone made Clockworkmod Recovery possible, giving us posibilty to create partitions on sdcard, do a nandroid backup/restore. But one MAJOR thing wasn't done as it should. Recovery in theory should give us possibility to flash ROMs from sdcard without need of computer. And theoretically it's possible, but... Yes, you have to have proper partition configuration flashed by DAF.exe with PC before. Imagine what a great obstacle it is for diagnosed with ORD!
Now you realise what I'm talking about? Combine these two things and bam! I'm just asking, just giving you an idea. Maybe it is possible to adapt those scripts to HD2 and replace old habits (flashing recovery by DAF.exe on PC) with simple script and one .txt file!
Again, maybe it's not possible since we are still using old SPL from WM times. Maybe MAGLDR is build in such way that those scripts are not possible. Maybe there is a thousand reasons... but I've never seen such an idea.
So please, is there one person who are good in this stuff and can explain me wether it's possible or not?
So maybe I can rest assured that I have to cure my ORD
OR
we can move on to work on making this idea reality .
cure for ORD....
I DON'T THINK SO.
Flashed from my fingers to your face
On a serious note, though, have you looked at clk? It is supposed to be useable without a pc. Therefore you can configure the partition on your phone. Is my understanding of that correct?
Maybe T-Macgnolia can explain this better than I .
I'm still trying to get my head round it, before I commit to changing over to clk...
Flashed from my fingers to your face
raven_raven said:
Hi. Maybe few words about me first. I'm not a developer, I don't know how to do it and I have to ask more experienced users. Ok that's it, to the point now. Ah, and I didn't know if this thread was proper to be posted in Development sub-forum, so it's here. If it was possible, if the thread meets requirements to be there, maybe it's possible to move it there? I'm not sure how many devs visit those section, so obviously there is greater chance for finding an answer there, but again, I wasn't sure if it was right.
While I was a G1 user one genius known as "Firerat" created very nasty script - it allowed users to manually, by simply creating a .txt file on sdcard with proper values and running a .zip from recovery, resize partitions like /system, /data and /cache on the phone. I don't know if you're familiar with G1 stuff, but previous there was only one way to chage partitions and it was achieved by custom SPL called Haykuro SPL. This modification (MTD part hack) was created because of need for even more space on /data and allowed to shrink /system and /cache to smallest value possible, so /data took up as much space as it was possible. Here is source thread in G1 Development section:
http://forum.xda-developers.com/showthread.php?t=717874
There you can dive in details, because my knowledge and understanding in this things end very quickly .
On HD2, we have come a great way. From pure Windows Mobile, it was possible to run Linux kernel from sdcard by HaRET.exe, then run Android. After few month team of gods gave us MAGLDR, a tool that allows us to replace Windows Mobile from NAND with Android system. Then after few more weeks someone made Clockworkmod Recovery possible, giving us posibilty to create partitions on sdcard, do a nandroid backup/restore. But one MAJOR thing wasn't done as it should. Recovery in theory should give us possibility to flash ROMs from sdcard without need of computer. And theoretically it's possible, but... Yes, you have to have proper partition configuration flashed by DAF.exe with PC before. Imagine what a great obstacle it is for diagnosed with ORD!
Now you realise what I'm talking about? Combine these two things and bam! I'm just asking, just giving you an idea. Maybe it is possible to adapt those scripts to HD2 and replace old habits (flashing recovery by DAF.exe on PC) with simple script and one .txt file!
Again, maybe it's not possible since we are still using old SPL from WM times. Maybe MAGLDR is build in such way that those scripts are not possible. Maybe there is a thousand reasons... but I've never seen such an idea.
So please, is there one person who are good in this stuff and can explain me wether it's possible or not?
So maybe I can rest assured that I have to cure my ORD
OR
we can move on to work on making this idea reality .
Click to expand...
Click to collapse
Hello raven_raven,
This is indeed a good idea and can make our HD2 PC independable. I will support you as much I can.
Though I have some questions for you.
Q1: Is it possible for this script to brick our device?
Q2: Can we choose the partitions which we resize (for example I would like to resize only /system, /userdata and /cache and leave the others as is) and if yes the other partitions /boot, /recovery will be formated or data will be kept as is?
Q3: What the bootloader has to do with it?
Q4: What SPL has to do with it?
For your knowledge in HD2 their are 2 bootloaders, MAGLDR and cLK (cedesmith's Little Kernel) which makes HD2 a native android device.
In MAGLDR partitions are made along with the flashing of CWM with the help of DAF.exe
In cLK partitions are directly managed by the bootloader when flashed.
malybru said:
On a serious note, though, have you looked at clk? It is supposed to be useable without a pc. Therefore you can configure the partition on your phone. Is my understanding of that correct?
Maybe T-Macgnolia can explain this better than I .
I'm still trying to get my head round it, before I commit to changing over to clk...
Flashed from my fingers to your face
Click to expand...
Click to collapse
Tried cLK, but it can't change partitions as you would like it to, you can't change it on the go without PC.
zach.antre said:
Hello raven_raven,
This is indeed a good idea and can make our HD2 PC independable. I will support you as much I can.
Though I have some questions for you.
Q1: Is it possible for this script to brick our device?
Q2: Can we choose the partitions which we resize (for example I would like to resize only /system, /userdata and /cache and leave the others as is) and if yes the other partitions /boot, /recovery will be formated or data will be kept as is?
Q3: What the bootloader has to do with it?
Q4: What SPL has to do with it?
For your knowledge in HD2 their are 2 bootloaders, MAGLDR and cLK (cedesmith's Little Kernel) which makes HD2 a native android device.
In MAGLDR partitions are made along with the flashing of CWM with the help of DAF.exe
In cLK partitions are directly managed by the bootloader when flashed.
Click to expand...
Click to collapse
A1: No, it is not possible. Firerat is genius and he does masterpiece of scripting, those scripts are 100% safe. It will of course break you ROM, but simple nandroid backup/flashing a new ROM will fix it.
A2: We resize /system, /data and /cache. You simply put two values in text files, i.e.:
Code:
mtd 130 2
First number is how many mb you want to spend on /system, second on /cache. Rest of internal memory is used by /data. /boot and /recovery are not touched by this script.
A3: I don't know for sure, just connected it to Haykuro SPL, which also changed partitions back then.
A4: Don't know for sure, I'm simply intermediate in this stuff, just wanted to pass an idea, I don't have required knowledge and experience to make this idea come true.
I know that there are 2 bootloaders, but I don't know how they work and how far you can modify partitions from recovery by using each of them. HD2 obviously isn't a native Android phone and regarding that either this idea may be impossible to implement or has to be completely redesigned. I really don't know .
Just wanted to pass an idea, but I'm terribly dissapointed how little response I received...
Well you would have more people responsed if you were posting in development forum under the label [call for development].
cLK is modified "little kernel" for HD2...
since there is no danger of bricking our device I am going to test it and report.
Sent from my Nexus One using XDA App
zach.antre said:
Well you would have more people responsed if you were posting in development forum under the label [call for development].
cLK is modified "little kernel" for HD2...
since there is no danger of bricking our device I am going to test it and report.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Great thing to see that someone tries. Be warned though, I'm not responsible for any data loss and damages or whatever, as always . Please be sure that you read original thread and understood how this script is working.
Maybe I'll ask a mod to move this thread to Development section...
raven_raven said:
Great thing to see that someone tries. Be warned though, I'm not responsible for any data loss and damages or whatever, as always . Please be sure that you read original thread and understood how this script is working.
Maybe I'll ask a mod to move this thread to Development section...
Click to expand...
Click to collapse
Yeah i did, don't worry about it.
I have read the original thread, i have compared the different devices mount points (as much i could) and conclude that is the same.
What i have also noticed is that kernel must be patch in order for this script to work and the script checks for a specific bootloader? I'm not sure, i need to restudy that thread.
Anyway, I tried using the script but didn't happen anything.
I formated all partitions except /boot and /recovery
I first created the mtdpartmap.txt in SD root and flashed via CWM the script FR-recovery-v1.5.8-CustomMTD_S.zip
Then reboot and again to recovery
Flashed ROM and then flashed FR-boot-v1.5.8-CustomMTD_S.zip
Reboot to ROM worked fine.
I run terminal
#df
Sizes where the same as before
Exactly, first you apply new partition map to recovery, next you install ROM in those new partitions either by flashing or nandroid backup-ing, then patch kernel to work with this new layout.
Huh, it would be too easy to simply run it and bam! it works. Even Firerat made different scripts for different devices. I'm curious what's the problem. Is recovery on a different level than those in native Android devices, which means that it can't change partition size? Or is it just problem of adjusting script to HD2 like it was done for Hero or Evo? I wonder if Firerat would like to investigate, but it would be impossible to achieve it without HD2, and from what I know he does not have one.
What person should I ask to move my thread to another section?
raven_raven said:
Exactly, first you apply new partition map to recovery, next you install ROM in those new partitions either by flashing or nandroid backup-ing, then patch kernel to work with this new layout.
Huh, it would be too easy to simply run it and bam! it works. Even Firerat made different scripts for different devices. I'm curious what's the problem. Is recovery on a different level than those in native Android devices, which means that it can't change partition size? Or is it just problem of adjusting script to HD2 like it was done for Hero or Evo? I wonder if Firerat would like to investigate, but it would be impossible to achieve it without HD2, and from what I know he does not have one.
What person should I ask to move my thread to another section?
Click to expand...
Click to collapse
Well, I guess Firerat need to come by and post a thread in HD2 Dev forum since it is his work.
He could ask what info he needs for the HD2 such as partition layout and filesystem in each partition etc... I am sure many people are willing to help with that.
I also think that SPL is locking the partition tables (not sure) and the way we are flashing just overcome that. Else when i used the script should have f**cked up my partitioning.
You can ask an HD2 moderator to move this thread but first ask for Firerat permission.