hey guys, i am having a problem getting the dualboot app to start when i actually boot my tilt 2
yes, i already have android installed and working
yes, gen.y dualboot works if i manually start it and it will boot linux and then android
but, my problem is that i want it to start how its supposed to (when i boot the phone)
i haven't found anything about anyone having problems getting the dualboot app to boot, but only problems with getting the dualboot app to boot android, which is not my problem, so could someone help me?
its probably something obvious to someone else, but i can't figure it out
and i know that i don't "need" to have it start when i boot the phone, but then what would be the point of the app?
nicc51591 said:
hey guys, i am having a problem getting the dualboot app to start when i actually boot my tilt 2
yes, i already have android installed and working
yes, gen.y dualboot works if i manually start it and it will boot linux and then android
but, my problem is that i want it to start how its supposed to (when i boot the phone)
i haven't found anything about anyone having problems getting the dualboot app to boot, but only problems with getting the dualboot app to boot android, which is not my problem, so could someone help me?
its probably something obvious to someone else, but i can't figure it out
and i know that i don't "need" to have it start when i boot the phone, but then what would be the point of the app?
Click to expand...
Click to collapse
Probably don't have it installed correctly on the phone if it's not in your main memory but on your memory stick it wont interrupt the boot sequence.
help
i have mine installed but the volume doesn't work
Related
I'm sure this has been covered before, but I'm not having luck digging through thousands of threads to find my answer. Its quick and easy for someone who knows more then I do.
I have a T-Mobile US HD2. I've flashed a custom rom of windows (latest version of Core) and I'm trying to run the latest version of Core Droid.
I've been able to install and boot up into Android just fine.....just once though. After the install process when it boots into Android, if I shut off the phone, restart it....blah blah blah it will automatically go back into Windows....and then I have to delete all the Android files and start new.
I've tried using this boot loader http://forum.xda-developers.com/showthread.php?t=733752
My options are set to have Android as the default, 30 second delay to let me have a chance to get into Windows incase I ever wanted too, and I have /android set as the Android folder. When I orignally copied all the files to my flash card, I put them in a folder on root called Android. As well, I've done all this on a freshly formatted SD card.
I've tried this several times with a few different WinMO Roms. I've tried a couple different distros of Android but without any better luck. Core seems to be the only one I can actually get to boot.
Please, any help would be great. I know I'm just missing something quick and simple here, but since this is something that I don't know much about I'm kind of stuck
EDIT :
I should also add that I've tried installing the boot loader both before and after my Android install. It doesn't make a difference either way.
Why do you have to delete Android and start again? Booting back into Windows is correct, of course, but you've not explained what actually goes wrong.
Sent from my HTC HD2 using XDA App
It seems like Droid wants to go through the whole install process again. It will sit there and do absolutely nothing (I left it sitting overnight on the black HTC screen that shows up when first putting on droid).... The only way I can get back into droid is if I format the SD card and start from scratch. Then if I turn off the phone or reboot it I have to do everything all over again.
I'm trying to just boot into Droid when I turn on my phone without having to worry about Windows. I don't mind a dual boot option. I just don't want to use Windows anymore
The only thing I can suggest is trying a different Android build. Just get one running and then reset your phone to make sure you can restart Android again. Worry about the bootloader later.
Sent from my HTC HD2 using XDA App
johncmolyneux said:
The only thing I can suggest is trying a different Android build. Just get one running and then reset your phone to make sure you can restart Android again. Worry about the bootloader later.
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
It seems to be working OK now. I re-flashed Windows and did everything from scratch. Set up the boot loader again and things seem to be ok.
What would you suggest as far as what build to use. I know this is kinda a touchy subject, but can you give me me pros/cons of the big ones?
I've NEVER used Android before so I'm pretty new to this
Dude, there is plenty of threads, even recent ones that already exhaust that question to the full, all you need to do is read them.
hi all, just got my hands on a htc hd2 and iv loaded [BUILD][19.12.10]-=MDJ FroYo HD v.4.6=-[FRG83D][kernel:MDJ S8.0] onto it no problem, got it running great, only thing is when i switch the phone off and back on it loads windows mobile again, then i have to run the android files again and let it install itself again, in the mean time losing all my settings, iv read theres a way to autoboot android on startup but cant really find anything about it, is this possible, and if so could someone run me through how to do it, wouldnt mind if it was just to reboot the android firmware, but when im losing all my settings and apps its no good, any help on this much appreciated as im still a newbie really to this phone.
When you boot up android from SD card, the first boot usually takes 10-15 minutes (varies from build to build). During this first startup, a new file in your android folder is created called 'data.img'. This is the file which your android build uses to store all the settings/apps/customisation etc.
When you restart your phone, before you boot into android, look in your android folder for 'data.img'. If it is missing then the android startup will take 10-15 minutes again, but if it is present it should only take 2-3 minutes. If it takes 10-15 minutes every time then you probably want to re-download the build and try again.
Also, dual-booting options are available, but check to see if this works first.
Sent from my HTC HD2 using XDA App
thanks mate, i noticed when i reloaded it again after switching off that my settings and apps were still there, which is good, but now id like to be able to boot straight into android, is that at all possible, im sure i read something earlier about it, but i cant find it again, would be cracking if i could load android on boot up!
big-hol said:
thanks mate, i noticed when i reloaded it again after switching off that my settings and apps were still there, which is good, but now id like to be able to boot straight into android, is that at all possible, im sure i read something earlier about it, but i cant find it again, would be cracking if i could load android on boot up!
Click to expand...
Click to collapse
here's how to boot android from the start:
http://forum.xda-developers.com/showthread.php?t=893948
dan138zig said:
here's how to boot android from the start:
http://forum.xda-developers.com/showthread.php?t=893948
Click to expand...
Click to collapse
cheers mate i'll have a look at that, i'll report back soon!
okay
i have the same problem
Mc-Checker said:
i have the same problem
Click to expand...
Click to collapse
try installing MAGLDR, it deletes WinMo en it has the option to install Android and WP7 in NAND, and it can load Android from SD
http://forum.xda-developers.com/showthread.php?t=893948
But the best of all: it has Tetris included
Hi,
I've quite a problem with setting up ubuntu on MultiROM. I've got the required kernel installed. The roms are installing properly. Just when I want to boot it, there shows the google icon twice and then goes back to MultiRom. I tried to install ubuntu desktop (newest) and ubuntu touch, always with the same result.... Any idea how to solve this?
I believe that's rather MultiROM problem because I have the same problem with BodhiLinux... Can previous using linuxonandroid affect MultiROM?
Are you sure you are using the correct kernel and flashed Ubuntu through the correct modified recovery?
I'm not sure, what was wrong... I installed everything twice again (first time it didn't work) and ubuntu installed and booting (still not working correctly, but that is always something ) Anyway, thank you for your answer without it I wouldn't have motivation to do it the second time.
Lol you're welcome
Hello All,
I need help regarding the boot loop...I am new to flashing ROMS..Few times i got into the Boot loop..
Sometimes I got into Boot loop for Modding , theming or using some Root application as well...
I just want to know is it possible to find out what is the reason or root cause for boot loop...how can i debug this boot loop problem....
Thanks in Advance...
FemBlack said:
Hello All,
I need help regarding the boot loop...I am new to flashing ROMS..Few times i got into the Boot loop..
Sometimes I got into Boot loop for Modding , theming or using some Root application as well...
I just want to know is it possible to find out what is the reason or root cause for boot loop...how can i debug this boot loop problem....
Thanks in Advance...
Click to expand...
Click to collapse
1. if flashing two different roms, you have to wipe data. if you dont wipe, then youll get a bootloop.
2. bad download of a rom/kernel.
3. the theme/mod isnt compatible or a bad download.
4. rarely, stuff corrupts.
5. root applications with stuff thats not compatible with your rom/kernel.
simms22 said:
1. if flashing two different roms, you have to wipe data. if you dont wipe, then youll get a bootloop.
2. bad download of a rom/kernel.
3. the theme/mod isnt compatible or a bad download.
4. rarely, stuff corrupts.
5. root applications with stuff thats not compatible with your rom/kernel.
Click to expand...
Click to collapse
Thank you for the reply...
I know because of compatibility i am getting the boot loop when i am using the root application....
My question is how to debug or find out where it went wrong... what made that application is not compatible with my ROM/Kernel....
FemBlack said:
Thank you for the reply...
I know because of compatibility i am getting the boot loop when i am using the root application....
My question is how to debug or find out where it went wrong... what made that application is not compatible with my ROM/Kernel....
Click to expand...
Click to collapse
watching a log cat via adb while the device is forced into one of these "bootloops". maybe even a dmseg. btw, are you sure that you have root? can you describe a situation, what you were doing with what root app, in detail how a "bootloop" happens? can you describe the bootloop and how you recover from one?
simms22 said:
watching a log cat via adb while the device is forced into one of these "bootloops". maybe even a dmseg. btw, are you sure that you have root? can you describe a situation, what you were doing with what root app, in detail how a "bootloop" happens? can you describe the bootloop and how you recover from one?
Click to expand...
Click to collapse
When i use Rom toolbox pro font installer to install new fonts or change the status bar using the build in icons...
two times i got into the boot loop problem.....
FemBlack said:
When i use Rom toolbox pro font installer to install new fonts or change the status bar using the icons...
two times i got into the boot loop problem.....
Click to expand...
Click to collapse
those options probably arent compatible due to android version, phone model, or rom(if works on another rom). there could be filesystem differences that make things incompatible. not all hacks/mods work on all devices. this all would cause bootloops, the way you describe it. have someone else with a nexus 4 confirm if they work or cause bootloops.
I already spoke with the developer regrading these boot loop problems... he has provided some solutions for it...
I have try those workarounds and lets see whether it fixes the problem or not....
Ok, so I just found my HD2 in the far back of my drawer under a bunch of stuff. It was my first smartphone, and I loved it, still do, which is why I kept it. So while I was using it I did do some modding to it. I have Android 2.3.3 on there running HyperDroid GBX v10.0. Problem is, I don't know how to do anymore modding to it. I completely forget, it has been so long since I touched the thing. All I know is when I start it up, it goes right to aMagldar v1.13 and I have to scroll down to boot NAND to get it to boot into HyperDroid. I've tried downloading and installing other ROMs, and they don't install. I've tried updating to a new version of HyperDroid, it doesn't work. Basically I'm a noob again when it comes to this device. Could somebody point me in the right direction? Do I have to install some Windows software? Do I have to install CWM? Or do I already have it? I'm lost! Any help would be greatly appreciated. This is the first time I've been in the HD2 thread in years. Thanks guys.
Paulx777 said:
Ok, so I just found my HD2 in the far back of my drawer under a bunch of stuff. It was my first smartphone, and I loved it, still do, which is why I kept it. So while I was using it I did do some modding to it. I have Android 2.3.3 on there running HyperDroid GBX v10.0. Problem is, I don't know how to do anymore modding to it. I completely forget, it has been so long since I touched the thing. All I know is when I start it up, it goes right to aMagldar v1.13 and I have to scroll down to boot NAND to get it to boot into HyperDroid. I've tried downloading and installing other ROMs, and they don't install. I've tried updating to a new version of HyperDroid, it doesn't work. Basically I'm a noob again when it comes to this device. Could somebody point me in the right direction? Do I have to install some Windows software? Do I have to install CWM? Or do I already have it? I'm lost! Any help would be greatly appreciated. This is the first time I've been in the HD2 thread in years. Thanks guys.
Click to expand...
Click to collapse
The guide in my sig should make everything clear. Choose a ROM, flash CWM with the required partition size for that ROM then flash the ROM in CWM from your SD card.