Hi everyone, this is something I know it's possible because I read someone already did, but I can't find where I read it.
They said it was done by renaming the android folder to android2 or whatever and adding a line to startup.txt
Any clues? Thank you
jrdaz said:
Hi everyone, this is something I know it's possible because I read someone already did, but I can't find where I read it.
They said it was done by renaming the android folder to android2 or whatever and adding a line to startup.txt
Any clues? Thank you
Click to expand...
Click to collapse
It is possible.
1.. First copy of Android on SDcard with whatever name ( Name your Android Folder). Then edit the startup.txt with the same Android folder name in set cmdline "rel_path=YOURANDROIDFOLDER"
2. Second copy your second Android on SDcard with whatever name......Then exit the startup.txt with the '''''''''' cmdline "rel_path=YOURANDROIDFOLDER"
3. If want more android..... repeat step 1...2...3
Then use an Android Loader by [APP] Exceller Multiple Build Loader for AndroidUbuntu Updated August 18 to load your choice of Android.
more than 1 android
10507 said:
It is possible.
1.. First copy of Android on SDcard with whatever name ( Name your Android Folder). Then edit the startup.txt with the same Android folder name in set cmdline "rel_path=YOURANDROIDFOLDER"
2. Second copy your second Android on SDcard with whatever name......Then exit the startup.txt with the '''''''''' cmdline "rel_path=YOURANDROIDFOLDER"
3. If want more android..... repeat step 1...2...3
Then use an Android Loader by [APP] Exceller Multiple Build Loader for AndroidUbuntu Updated August 18 to load your choice of Android.
Click to expand...
Click to collapse
I did all the steps above..and when i ran the first android..to install it..it did the usual word scroll thing..but its bin doing that since 20 mins now..tha phone is heating up a lil...and its slowlying running texts with RAAC=(decending from 77)
1.. First copy of Android on SDcard with whatever name ( Name your Android Folder). Then edit the startup.txt with the same Android folder name in set cmdline "rel_path=YOURANDROIDFOLDER"
2. Second copy your second Android on SDcard with whatever name......Then exit the startup.txt with the '''''''''' cmdline "rel_path=YOURANDROIDFOLDER"
Click to expand...
Click to collapse
Works like a charm, thank you!
I always have 2 sd cards dedicated for my HD2. When I am ready to try out a new build, I throw it on the 2nd sd card. If the new build works well I stick with it and if not I fall back to the previous build. It makes a lot of sense for me because well I have 2 sd cards and only one phone.
Related
Peace all,
Currently try to place the Andriod OS on my girlfreind's HD2. I had placed the file on her SD card before and it worked w/o any problems. Recently she started having problems so I decided to place a real "dual boot" ROM (OzDroid) onto her phone. that went well---but when i placed Meejay's Revolution 2.3 on the root of her SD card---for some reason OzDroid doesn't detect the Android build and when i try to do the fix that comes on OzDroid to repair Android it says "error on startup.txt". Can anyone help me with this or point me to the right direction?
thanks in advance
-ZDK-
Would be nice if you could post this startup.txt.
JanssoN said:
Would be nice if you could post this startup.txt.
Click to expand...
Click to collapse
It says: "error, can not modify startup.ext" when i press the button that loads Android
ZEDEK said:
It says: "error, can not modify startup.ext" when i press the button that loads Android
Click to expand...
Click to collapse
but what is the text inside startup.txt?
Perhaps it's because it's looking natively in the "Android" folder, which I know guess is not pressent on the other SD card.
Open your startup.txt on your android phone, and look for this line:
set cmd "rel_path=Android" or simmilar. If so, remove the entire cmd line, if there is nothing else in that line. Otherwise, just remove the rel_path=Android part inside the "" signs.
Hope this helps you
Stenager129 said:
Perhaps it's because it's looking natively in the "Android" folder, which I know guess is not pressent on the other SD card.
Open your startup.txt on your android phone, and look for this line:
set cmd "rel_path=Android" or simmilar. If so, remove the entire cmd line, if there is nothing else in that line. Otherwise, just remove the rel_path=Android part inside the "" signs.
Hope this helps you
Click to expand...
Click to collapse
Peace to u Stenager,
Thanks so much for ur reply....sorry I didn't get back right away---was away for holiday. However, if u don't mind...can u tell me where I go to set up the startup.txt to change cmd?...I'm totally lost.
Thanks so much for ur time & patience
-ZDK-
Sent from my HTC Evo using Tapatalk
Hi, can anyone tell me whats the best andriod rom relese for daily use and games? BTW i need full guide how install android os on htc touch hd step by step. Thanks.
There isnt one as yet that I think your after.
Most android builds are still just alpha in the sense that the HD will not work 100%, the GPS or camera will not function, or other missing key parts as such.
I don't believe you will find a complete 100% working build just yet, but I do think they are getting closer.
i know that there arent any 100% working but whitch release are best?
have a look over here http://forum.xda-developers.com/showthread.php?t=921687
if you choose xdandroid
there are several xdandroid verisions that work on HD,but xdandroid version that is quickest on our devices can be found here,together with instructionshttp://forum.xda-developers.com/showthread.php?t=732362
if you want to try froyo x
froyo x that can be found here http://forum.xda-developers.com/showthread.php?t=904918
version 1.12 is in the first post
version 1.21 is in the second post
i didn't get wifi to work on either of these on my phone,but there are guys that say it works on HD
i suggest you to try 1.12 first
just download it,extract to sdcard
if you want to use a folder on sdcard so these files don't mess with others make a folder called andboot.froyox
extract everything there
open the folder go to "startup" folder in which there is "blackstone" folder,open it and copy startup.txt to folder in which you extracted the zip (overwrite the old startup.txt if you get prompted)
open the startup.txt file delete everythin,and paste this instead
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2030
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=240 msmts_calib=0x395.0x3c9.0x79.0x77 msmvkeyb_toggle=off msm_blackstone_pad.vibrate=1 pmem.extra=1 gsensor_axis=-2,-1,3 rel_path=andboot.froyox"
boot
save the startup.txt
and run HARET.exe
give the phone a bit time to compile the image (can take 10 minutes)
and that's pretty much that
post any additional questions here http://forum.xda-developers.com/showthread.php?t=627749
and please read forum rules and do not open new threads asking things because that is what FAQ threads are for
ah yes and always search before posting (that's how i learned to do this)
disclaimer:
i,or anyone else over here isn't responsible for any possible damage caused to your phone
(although no one ever complained...the worst case is that you will have to hard reset the device,but that is very rare)
I tried to install frx 04 finished the calibration setup and then there was a black screen which i think was android booting up. However I reset my phone at this point because there was a black screen 4 about 2 mins. Tried to run haret again but got the message the file 'haret' cannot be opened. either it is not trusted..if the problem persists try reinstalling or restoring the file.
I tried deleting all the frx04 files and putting them back into memory card but I keep getting that message. What do I do ?(btw htc touch hd.)
problem solved
hard reset, changed roms, android now works!
try formating the card and reinstalling the fresh full FRX4 (dated 10/2)
ypsmav said:
try formating the card and reinstalling the fresh full FRX4 (dated 10/2)
Click to expand...
Click to collapse
yep done that nothing changed
mickeystar said:
yep done that nothing changed
Click to expand...
Click to collapse
use fresh copy of haret and see if your STARTUP.txt is right
most importantly check if this is right:
a) if your haret and other files are in root of the sd,open startup.txt and check if there is something like "rel_path=andboot" if there is,just delete that
b) if your haret and other files are in some folder eg. "FOLDER3" go to startup.txt and
-if there is no "rel_path=****" add "rel_path=FOLDER3"
-if there is just change **** to FOLDER3
be sure that rel_path has space before it and it is under quotes together
since there are only one quotes in that file,you will easily find them and place the right line there
additionally check for SD card problems,use search for your problem, you can easily find what to add to startup.txt if it is an sd card issue
farukb said:
use fresh copy of haret and see if your STARTUP.txt is right
most importantly check if this is right:
a) if your haret and other files are in root of the sd,open startup.txt and check if there is something like "rel_path=andboot" if there is,just delete that
b) if your haret and other files are in some folder eg. "FOLDER3" go to startup.txt and
-if there is no "rel_path=****" add "rel_path=FOLDER3"
-if there is just change **** to FOLDER3
be sure that rel_path has space before it and it is under quotes together
since there are only one quotes in that file,you will easily find them and place the right line there
additionally check for SD card problems,use search for your problem, you can easily find what to add to startup.txt if it is an sd card issue
Click to expand...
Click to collapse
i dont understand what u mean by ' be sure that rel_path has space before it and it is under quotes together'
i've uploaded my startup file, my haret and files are in an andboot folder with the rel_path added onto startup
mickeystar said:
i dont understand what u mean by ' be sure that rel_path has space before it and it is under quotes together'
i've uploaded my startup file, my haret and files are in an andboot folder with the rel_path added onto startup
Click to expand...
Click to collapse
Flash with another ROM, for example: WM 6.5.x (build 28244) I think it's the best!
Next.. on a FRESH formatted microSD card copy all the linux/android files except the "modules*****", "rootfs.img" and "zImage" to the root of microSD.
Go here and download the latest kernel htc-msm****
Next>> Go here and download the latest rootfs
Next>> unpack the "htc-msm***" archive and copy "modules-***" and "zImage-***" to root of microSD, rename "zImage-***" to "zImage", "modules-***" don't need rename!
Unpack the "rootfs-***" archive and copy "rootfs-***.img" to root of microSD, rename "rootfs-***.img" to "rootfs.img", delete "data.img" if exist, delete "ts-calibration" if exist!
Hope this helps!
Best Regards, FLeX!
Edit: use the untouched STARTUP.TXT
mickeystar said:
i dont understand what u mean by ' be sure that rel_path has space before it and it is under quotes together'
i've uploaded my startup file, my haret and files are in an andboot folder with the rel_path added onto startup
Click to expand...
Click to collapse
If that's your startup.txt, the problem is right there:
NOT:
....gsensor_axis=-2,-1,3"
boot
rel_path=andboot
BUT:
....gsensor_axis=-2,-1,3 rel_path=andboot"
boot
That should fix the FIRST problem with booting it up.
Another problem might be still having the USB plugged in to the phone. Be sure to take it out before running haret.
hrk7474 said:
If that's your startup.txt, the problem is right there:
NOT:
....gsensor_axis=-2,-1,3"
boot
rel_path=andboot
BUT:
....gsensor_axis=-2,-1,3 rel_path=andboot"
boot
That should fix the FIRST problem with booting it up.
Another problem might be still having the USB plugged in to the phone. Be sure to take it out before running haret.
Click to expand...
Click to collapse
changed it not sure if its right though still doesnt work, can u upload rite startup txt file for blackstone please
mickeystar said:
changed it not sure if its right though still doesnt work, can u upload rite startup txt file for blackstone please
Click to expand...
Click to collapse
Better yet. I took your startup.txt made it look more readable.
See pic for how the folder should look.
Don't worry about not having data.img and tscalibration files, they are created on first boot.
And there's a great video about it on youtube by theDeadCPU. --> VIDEO <--
Just in case your kernel doesn't ask for calibration, download the attached file and put it in andboot folder. Remove extension (should be ts-calibration)
hrk7474 said:
Better yet. I took your startup.txt made it look more readable.
See pic for how the folder should look.
Don't worry about not having data.img and tscalibration files, they are created on first boot.
And there's a great video about it on youtube by theDeadCPU. --> VIDEO <--
Click to expand...
Click to collapse
still not working, i used your startup. these are the files on my andboot folder on my storage card.
sorry about image quality had to resize
any1????????????
mickeystar said:
these are the files on my andboot folder on my storage card.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=11411484&postcount=10
thanks for the replies but i think my problem goes further
http://forum.xda-developers.com/showthread.php?p=11572912&posted=1#post11572912
problem solved
hard reset, changed roms, android now works!
mickeystar said:
thanks for the replies but i think my problem goes further
http://forum.xda-developers.com/showthread.php?p=11572912&posted=1#post11572912
problem solved
hard reset, changed roms, android now works!
Click to expand...
Click to collapse
Glad it works now.
hallo guys I want to install 2 ROMS in SD card for my HD2 device.
a sense and a MIUI one ,,but I want to have both installed!
in order to run everytime which I want...
is this possible ? can you explain and help?
many thanks!!
Yes, it is.
In the folder with the files in (probably named 'Android') there is a file called startup.txt. Change the folder name to whatever you want (e.g. 'MIUI' or 'Sense') then within the folder open the startup.txt. There will be a line saying rel_path=Android (or whatever the name of the folder originally was). Change this to rel_path=your folder name and boot. I can't remember if the line is exactly like that, so keep the formatting the same (i.e. the same spaces, signs etc.) and only change the Android bit.
thank you! and after I boot into windows how I will choose which I want?
(MIUI or SENSE named?)
gesamgr said:
thank you! and after I boot into windows how I will choose which I want?
(MIUI or SENSE named?)
Click to expand...
Click to collapse
Well I guess you would have to uninstall any automatic loaders you have and manually browse through the files and choose the right CLRCAD and HARET from the desired folder
ok thank you !!!
Hi gesamgr,
follow the download link for the exceller autoloader in this thread:
http://forum.xda-developers.com/showthread.php?t=737001
On bootup sequence it shows you the opportunity to choose which OS you'd like to boot - multiple OS as SD version included! Remember to follow the instructions carefully.
best regards
Getrid
Use MAGLDR 1.13 for booting into WINDOWS or any ANDROID ROM.
Just use Boot AD SD for booting into Android.
Change the folder for booting different android ROMs using SERVICES....Boot Setting.....Android SD Folder.
I have 3 roms in SD
just point the way in Magldr
Hello everybody!!!
I'm a very noob user, so i please a need a step by step help!
I tryed to install a dual boot on my hd2, with android ICS (MIUI) on SD, and windows mobile 6,5 on NAND.
To get that result i used this Guide: http://forum.xda-developers.com/showthread.php?t=1504369
..but, in the the guide is written:
"Instructions:
Well you know just extract everything and put the miuiics folder in your root of sd card, you know the rest.."
maybe a link to the guide is better then "you know the rest..."!
I don't Know the rest, and I proceded in this way:
1) Inistalled the MAGLDR
2) copyed the rom of android on a SD card
3) Configured the setting to make a boot to SD and Android working perfectly!!
Now I even need to use windows mobile 6.5, but I don't know to switch on it!
I think that MAGLDR is overwritten on WM6.5 rom, and now I have a phone with only android, where is impossible to make a dual boot!!!
Anyone can write me the procedure step by step to retry to install correctly the dual boot with WM6,5 and android MIUI ics? Is even good a link with a guide that I didn't found!!!
I have 2,08 HSPL.
Thanks anticipately for your explains!
Nick.sf
nick.sf said:
Hello everybody!!!
I'm a very noob user, so i please a need a step by step help!
I tryed to install a dual boot on my hd2, with android ICS (MIUI) on SD, and windows mobile 6,5 on NAND.
To get that result i used this Guide: http://forum.xda-developers.com/showthread.php?t=1504369
..but, in the the guide is written:
"Instructions:
Well you know just extract everything and put the miuiics folder in your root of sd card, you know the rest.."
maybe a link to the guide is better then "you know the rest..."!
I don't Know the rest, and I proceded in this way:
1) Inistalled the MAGLDR
2) copyed the rom of android on a SD card
3) Configured the setting to make a boot to SD and Android working perfectly!!
Now I even need to use windows mobile 6.5, but I don't know to switch on it!
I think that MAGLDR is overwritten on WM6.5 rom, and now I have a phone with only android, where is impossible to make a dual boot!!!
Anyone can write me the procedure step by step to retry to install correctly the dual boot with WM6,5 and android MIUI ics? Is even good a link with a guide that I didn't found!!!
I have 2,08 HSPL.
Thanks anticipately for your explains!
Nick.sf
Click to expand...
Click to collapse
First link explains how get Android installed and running from SD using CLRCAD.EXE and HaRet.exe = "you know the rest..."
http://forum.xda-developers.com/showthread.php?t=732380
and also a link how to get WM back on the HD2.
http://forum.xda-developers.com/showthread.php?t=609477
BTW: the link you attached is not a guide, it is the ROM itself with few instruction for people who have already some experiences
Cheers.....LinChina
Please do some more reading before flashing anything, if you didn't have an HD2 you would probably end up hard bricking your device if you didn't read. MAGLDR replaces WinMo. You need to boot into the bootloader, flash an official stock ROM via USB then run the SD build via CLRCAD and HARET.
LinChina said:
First link explains how get Android installed and running from SD using CLRCAD.EXE and HaRet.exe = "you know the rest..."
http://forum.xda-developers.com/showthread.php?t=732380
and also a link how to get WM back on the HD2.
http://forum.xda-developers.com/showthread.php?t=609477
BTW: the link you attached is not a guide, it is the ROM itself with few instruction for people who have already some experiences
Cheers.....LinChina
Click to expand...
Click to collapse
thanks a lot!
Later I will tray again! I'll let you know!!!
However in the guide you gave me, do not talk about Android ICS, but the previous version!!! "you know the rest..." continues to be a bit vague!!
Nick.sf
Nigeldg said:
Please do some more reading before flashing anything, if you didn't have an HD2 you would probably end up hard bricking your device if you didn't read. MAGLDR replaces WinMo. You need to boot into the bootloader, flash an official stock ROM via USB then run the SD build via CLRCAD and HARET.
Click to expand...
Click to collapse
Thanks, but i tryed with CLRCAD and HARET without result!!!
Mayby "Android loader V6" isn't the bootloader corretc?
when I select CLRCAD and HARET, the phone lounch first screen of android loading, but then, the phone restarts!!!
nick.sf said:
Thanks, but i tryed with CLRCAD and HARET without result!!!
Mayby "Android loader V6" isn't the bootloader corretc?
when I select CLRCAD and HARET, the phone lounch first screen of android loading, but then, the phone restarts!!!
Click to expand...
Click to collapse
OK you seem to be very confused with your terms, so I'll simplify things for you:
1. Turn the phone off
2. Boot into the bootloader (stripey screen) by holding power and volume down
3. Flash the latest 3.14 stock ROM (WinMo) for your particular device (see on HTC's official website, it has the downloads plus a guide)
4. Place the 'Android' folder on the root of your SD card. Note that the name of this folder may vary from build to build, but it is always the folder containing all of the files.
5. Boot into WinMo then find the file explorer
6. Open the 'Android' folder (or whatever it's called) and find the file 'CLRCAD.exe' and run it. You will not see any visual change
7. Find the file 'HARET.exe' and run it. Android will be booted.
8. After first boot, be patient. Give the device time to settle and then once everything seems fine (after at most 5 minutes) reboot.
9. Once you reboot, you will have WinMo again. Simply repeat steps 6 and 7 to boot into Android.
If this guide isn't simple enough for you, then in all honesty I don't think I can help you much, you'll have to find someone who's more noob-friendly
Nigeldg said:
OK you seem to be very confused with your terms, so I'll simplify things for you:
1. Turn the phone off
2. Boot into the bootloader (stripey screen) by holding power and volume down
3. Flash the latest 3.14 stock ROM (WinMo) for your particular device (see on HTC's official website, it has the downloads plus a guide)
4. Place the 'Android' folder on the root of your SD card. Note that the name of this folder may vary from build to build, but it is always the folder containing all of the files.
5. Boot into WinMo then find the file explorer
6. Open the 'Android' folder (or whatever it's called) and find the file 'CLRCAD.exe' and run it. You will not see any visual change
7. Find the file 'HARET.exe' and run it. Android will be booted.
8. After first boot, be patient. Give the device time to settle and then once everything seems fine (after at most 5 minutes) reboot.
9. Once you reboot, you will have WinMo again. Simply repeat steps 6 and 7 to boot into Android.
If this guide isn't simple enough for you, then in all honesty I don't think I can help you much, you'll have to find someone who's more noob-friendly
Click to expand...
Click to collapse
Thank you so much for the help, but i just tryed this way!!!
In my situation, at point 8 of the guide, my phone restarts after about 30 second (no 5 minute) and then go in loop...
After the restart, the phone enter in WM and ask me to run CLRCAD.exe, and HARET.exe (in this order) and i accept.
The phone starts the loading screen of android, and restarts again.
It always restarts, without going into Android! I have seen at least 10 restarts before try to install Magldr!!!
I don't know the cause, but i think that android ICS is not compatible with the "Android loader V6". I used this loader with android gingerbread without problem!
Now in the link with ROM, i read:
"Ported using Portadroid Ultimate v4.0: http://forum.xda-developers.com/show....php?t=1094372 "
but the page does not exist!!!! What is portadroid ultimate? is it the bootloader?
I'd not worry about the bootloader and other terms much if I were you, it's not important for SD Android anyway
I apologise if I can't be much more use but I haven't used SD Android in a long time . The only thing I can think of is this: EDIT: see bottom of the post first, then try this
1. Find the SD Android build which you have downloaded on your PC
2. Open the folder and find the file 'startup.txt'
3. Find the line 'Rel_path=' and make sure that the next word matches the name of the folder in which the build is stored, for example if I had an SD build with the folder name 'Android', that line in startup.txt should also say 'Rel_path=Android'.
The only other thing I can think of is that somehow the folder isn't in the root of your SD card. Make sure the folder which contains the files (so in the example I gave previously this folder would be called Android) is copied to the root of your SD card. There should be no sub-folders or anything like that, just /Android.
EDIT: I think I may have found it now, try uninstalling the automatic loader app you have (Android Loader V6) and running these files manually rather than doing it automatically. If I'm not mistaken, this app looks for a folder named 'Android' by default, but the name of the folder your ICS build is stored in may be something different.
Just to add that ICS SD builds are often in an 'ICS' folder instead of 'Android'
It shouldn't matter using CLRCAD.exe, and HARET.exe though.
Nigeldg said:
I'd not worry about the bootloader and other terms much if I were you, it's not important for SD Android anyway
I apologise if I can't be much more use but I haven't used SD Android in a long time . The only thing I can think of is this: EDIT: see bottom of the post first, then try this
1. Find the SD Android build which you have downloaded on your PC
2. Open the folder and find the file 'startup.txt'
3. Find the line 'Rel_path=' and make sure that the next word matches the name of the folder in which the build is stored, for example if I had an SD build with the folder name 'Android', that line in startup.txt should also say 'Rel_path=Android'.
The only other thing I can think of is that somehow the folder isn't in the root of your SD card. Make sure the folder which contains the files (so in the example I gave previously this folder would be called Android) is copied to the root of your SD card. There should be no sub-folders or anything like that, just /Android.
EDIT: I think I may have found it now, try uninstalling the automatic loader app you have (Android Loader V6) and running these files manually rather than doing it automatically. If I'm not mistaken, this app looks for a folder named 'Android' by default, but the name of the folder your ICS build is stored in may be something different.
Click to expand...
Click to collapse
aldaweb said:
Just to add that ICS SD builds are often in an 'ICS' folder instead of 'Android'
It shouldn't matter using CLRCAD.exe, and HARET.exe though.
Click to expand...
Click to collapse
That is correct. If I read it right, Android Loader had been set up already for a previous build. When you do this, you tell the app what folder to look for - i.e. "Android". Now that you have a different build, different folder name, the app cannot find all the associated files to boot from SD properly.
Your folder name is miuiics