Related
I know the winmo phones can dual boot winmo and android. They boor android from the sdcard.
Im wondering if we can get are phones to dual boot so we can have are working rom ect.... And we can dual boot into the secondary android from the sd card to test are mods
Sent from my Emotionless Beast of an Epic using the XDA App
The short answer is: no.
mysteryemotionz said:
I know the winmo phones can dual boot winmo and android. They boor android from the sdcard.
Im wondering if we can get are phones to dual boot so we can have are working rom ect.... And we can dual boot into the secondary android from the sd card to test are mods
Sent from my Emotionless Beast of an Epic using the XDA App
Click to expand...
Click to collapse
They can dual boot because Android is an open OS and is free. It would be illegal to put Winmo on our devices without paying for the proper license.
Also, for what possible reason would you even want to do this? To use as a reminder of how primitive Winmo looks and was compared to Android?
muyoso said:
They can dual boot because Android is an open OS and is free. It would be illegal to put Winmo on our devices without paying for the proper license.
Also, for what possible reason would you even want to do this? To use as a reminder of how primitive Winmo looks and was compared to Android?
Click to expand...
Click to collapse
I wanna dual boot with 2 separate sets of android for testing purposes
Sent from my Emotionless Beast of an Epic using the XDA App
I think yes, it would be possible. I wouldn't know how, but its been done on android before, and there is an alpha version being worked on already for the Sammy Moment at SDX and Samdroid.
And if this could be achieved it would be a great to help to developers.
I think I would like it just for the purpose of trying out new roms without having to give up my current rom, in case I don't like the new one.
RKight said:
I think I would like it just for the purpose of trying out new roms without having to give up my current rom, in case I don't like the new one.
Click to expand...
Click to collapse
if you do a full backup, flash a new ROM, restore data (only) and you don't like the new ROM, you can go back into recovery, restore full backup and voila.. you're back to the ROM you just backed up.
takes 3 minutes to do all this.
no need for dual boot IMO
daddymikey1975 said:
if you do a full backup, flash a new ROM, restore data (only) and you don't like the new ROM, you can go back into recovery, restore full backup and voila.. you're back to the ROM you just backed up.
takes 3 minutes to do all this.
no need for dual boot IMO
Click to expand...
Click to collapse
Certain themes with the battery percentage mode will cause boot problems from recovery
Sent from my Emotionless Beast of an Epic using the XDA App
daddymikey1975 said:
if you do a full backup, flash a new ROM, restore data (only) and you don't like the new ROM, you can go back into recovery, restore full backup and voila.. you're back to the ROM you just backed up.
takes 3 minutes to do all this.
no need for dual boot IMO
Click to expand...
Click to collapse
I'm aware of that process but if I'm just wanting to tinker with a new rom, I really don't want to go through all that trouble. If I want to try a new Linux distro on my PC, I'm not going to ghost it, install the new distro, then restore the old image later. I'm going to throw the new distro on a second hard drive and dual boot while I decide if I like it. That way, I have a known stable OS, configured the way I want, just a reboot away.
mysteryemotionz said:
Certain themes with the battery percentage mode will cause boot problems from recovery
Sent from my Emotionless Beast of an Epic using the XDA App
Click to expand...
Click to collapse
I have noticed this as well, and a flash with odin plus reinstalling clockworkmod is the only thing that prevents it from corrupting your backups for future use.
daddymikey1975 said:
if you do a full backup, flash a new ROM, restore data (only) and you don't like the new ROM, you can go back into recovery, restore full backup and voila.. you're back to the ROM you just backed up.
takes 3 minutes to do all this.
no need for dual boot IMO
Click to expand...
Click to collapse
I don't know. That's fine if you just want to try out a ROM one time, and quickly, or if you can do without your main ROM for a long time. I had a windows phone before I switched to Android. Having the "dual boot" was key to my switching to Android. I was able to install Android, set it up the way I wanted to (which took lots of time) and "play" with it whenever I had time, but at other times I needed to be able to switch back to my main phone. I'd switch a couple times a day sometimes (just a single click to go either way). After a couple of weeks of being able to work with Android I knew I'd be happy switching.
You could do something like this with backups and restores, but I honestly think it would get overly cumbersome. You'd have to backup your main ROM and then the second ROM. Every time you changed a setting or moved something around in either ROM you'd have to remember to make a new backup, or the next time you switched into that ROM all of your changes would be reverted back.
In any case, I don't know how possible it is to have dual boot, but I can certainly see a lot of advantages for some people.
HARET is what makes the WinMo android boot possible and is based on work done with soft/hard SPL. No Android equiv to HARET exists yet. However, a lot of work is happening with HBOOT due to the Vision G2 eMMC situation. I wouldn't be too far off if I were to speculate that an android HARET may be in our future.
Go check out this thread from the Eris forums. - Dual boot recovery hack
As I'm not intimately familiar with the inner workings of Clockwork, I don't know how plausible it is on the DX. It could either be really easy to port since we're already bootstrapped, or nearly impossible. That's a problem for a dev much smarter than me to conquer.
I will say that I tried it out on my Eris. The stock class 2 card was unbearably slow, a class 4 was tolerable, and a class 6 (which cost a small fortune) ran as if it was installed internally. Kinda neat, but not terribly practical for daily use.
Hello,
I need some help. I decided to try out a mod while at work today. i tried it out and didnt like it too much and try to restore my last back up that i did before the change. the phone cut off then back on and was stuck on the mytouch 4g screen and has been this way for about 3 hours.i took the battery out and i went to the hboot screen and tried a factory reset and then the rom manager opened up (v3.0.0.5). from there i went to reboot now and it goes back to the my touch screen. idk what to do and i need help. im new to the droid and am unfamiliar with the terms. can anyone help PLEASE. if possible to gtalk me at j.d.louisy.
thisisjay said:
Hello,
I need some help. I decided to try out a mod while at work today. i tried it out and didnt like it too much and try to restore my last back up that i did before the change. the phone cut off then back on and was stuck on the mytouch 4g screen and has been this way for about 3 hours.i took the battery out and i went to the hboot screen and tried a factory reset and then the rom manager opened up (v3.0.0.5). from there i went to reboot now and it goes back to the my touch screen. idk what to do and i need help. im new to the droid and am unfamiliar with the terms. can anyone help PLEASE. if possible to gtalk me at j.d.louisy.
Click to expand...
Click to collapse
calm down take a breather us XDA users got your back, OK take out the battery and put it back in then go to the Hboot ( hold power and volume down) then once you get to the Hboot Settings use volume down to get to RECOVERY (i think its the third one) then once you get into Clockwork Recovery scroll down to (Backup and Restore) click then press (Restore) and then choose your Restore file it usually Year-month-day hope i helped you donate pls if i did
BE SURE TO KEEP THE CHARGER IN!!
p.s. if it turns off while its restoring even with the charger in let it boot into recovery mode and let it charge up a bit
incase you still need help gtalk me [email protected]
and p.s. CWM 3.0.0.5 is for gingerbread only
Certain roms require certain versions of clockworkmod. I don't know if this also applies to restoring from backups, though. Which type of rom did you flash?
If he flashed the add on 3.0.0.5 has ext3/ext4 support. Should be able to flash froyo and TB Rome.
Sent from my HTC Glacier using XDA App
3.0.0.6 supports ext3/ex4 3.0.0.5 only does Gingerbread
Edit: I'm being a dumbass yea what he said was right I'm overly tired and I have to explain to her why I was being a dumbass and trying to flash through fastboot but what I don't understand is why its still stuck at the boot screen
thisisjay said:
Hello,
I need some help. I decided to try out a mod while at work today. i tried it out and didnt like it too much and try to restore my last back up that i did before the change. the phone cut off then back on and was stuck on the mytouch 4g screen and has been this way for about 3 hours.i took the battery out and i went to the hboot screen and tried a factory reset and then the rom manager opened up (v3.0.0.5). from there i went to reboot now and it goes back to the my touch screen. idk what to do and i need help. im new to the droid and am unfamiliar with the terms. can anyone help PLEASE. if possible to gtalk me at j.d.louisy.
Click to expand...
Click to collapse
Three options
Option one: (easiest)
Since you flashed 3.0.0.5 you must flash a Gingerbread ROM, (Which you can download from here ). Make sure to flash the G/apps after you flash the ROM.
Option two:
you can flash a 2.x.x.x Recovery image, or flash 3.0.0.6 via script or manually do it via the HBoot.
Option three:
Flash the PD15IMG and start over from ground one.
thank you so much for the advice and help. i could bang my head on the wall for trying to load gorillasens. i shouldve left it alone. once i get home from work i will give it a try again.
thisisjay said:
thank you so much for the advice and help. i could bang my head on the wall for trying to load gorillasens. i shouldve left it alone. once i get home from work i will give it a try again.
Click to expand...
Click to collapse
Ah. i think i see what happened. You rooted your phone. downloaded Clockwork Rom Manager, then flashed a recovery image (which was version 3.x). then tried to flash a 2.2 ROM.
Okay. so what.....
a common mistake but one that can be avoided by doing a little research.
Clockwork's 3.0.0.5 recovery image is only compatible with Gingerbread (2.3) based ROMs.
Clockwork's 2.x recovery image are only compatible with FroYo (2.2) based ROMs.
gorilla is 2.2 So it's not cannot be flashed by the recovery image you are using.
if that is correct then the text in the recovery image should be orange in color. If that is correct.....If i were in your shoes i'd load CM7 w/ the GAPPS > download CWRM from the markert > scroll to the bottom (all clockwork recoveries) and flash the newest 2.x. then boot into recovery / make sure the text is GREEN, not ORANGE, wipe then flash your GorillaSense.
Can you cite a source, because I've also heard people claim that Clockwork 3 is backwards compatible, but there was no evidence either way...?
How would you go about switching from a 2.2 ROM to a 2.3 ROM? Do you have to backup with CWM 2, then install CWM 3 to install the new ROM? Doesn't make a lot of sense to me...?
Sent from my Nexus One using XDA App
danger-rat said:
Can you cite a source, because I've also heard people claim that Clockwork 3 is backwards compatible, but there was no evidence either way...?
How would you go about switching from a 2.2 ROM to a 2.3 ROM? Do you have to backup with CWM 2, then install CWM 3 to install the new ROM? Doesn't make a lot of sense to me...?
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
3.0.0.5 is not backwards compatible, which is the official 3.x that you download via the Application. 3.0.0.6 which is "beta" flashed via the HBoot is backwards compatible.
It's seriously jacked if you ask me.
to go from lets say CM6 > CM7 one would do a nandroid backup of CM6, then go to CWRM flash the 3.0.0.5 recovery image > boot into recovery and flash the CM7.
now to get back to a 2.2 ROM you have to scroll to the bottom of CWRM app's and flash a 2.x version of the recovery then do your nandroid restore, flash the 2.2 recovery image.
From what i've heard once 3.0.0.6 is finished you can use that for everything.
What a pain...
I'm real sketchy about the Clockwork 3 recoveries for the Nexus, because they've been screwing up partitions (mine included). Has there been any problems with Clockwork 3 on the Glacier?
Sent from my Nexus One using XDA App
danger-rat said:
What a pain...
I'm real sketchy about the Clockwork 3 recoveries for the Nexus, because they've been screwing up partitions (mine included). Has there been any problems with Clockwork 3 on the Glacier?
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
I haven't had any problems with mine. The only problem that was noted was the 3.0.0.5 prior to the official release wouldn't do Nandroid Backups directly from the application. Some were reporting it work work from the recovery image, but mine never did.
and i have a feeling the reason it's screwing with Partitions is this (CM7/CW3.x) is a Ext4 set up. And CM6/CW2.x is a Ext3 set up.
but since it went official the only problem i've seen is people flashing the the wrong recovery for the wrong ROM. People are flashing 3.x because 3 is higher than 2 so they think it's an upgrade and have no clue on the who/what/when/wheres and whys of what its for.
The partition thing is different for the Nexus, because they are cross compatible to a certain degree. I rolled back to CWM 2, but I can still flash CM7 no probs...
It's interesting to note the differences between the two platforms though (Nexus vs Glacier).
Sent from my Nexus One using XDA App
danger-rat said:
The partition thing is different for the Nexus, because they are cross compatible to a certain degree. I rolled back to CWM 2, but I can still flash CM7 no probs...
It's interesting to note the differences between the two platforms though (Nexus vs Glacier).
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Yea between Google's way of doing thing and HTC, but i'm sure the chip-set has something to do with that. and with the sexy nexi only having 512Mb of memory the factor of tricking the phone to use the SD card has something to do with it i'm sure.
i have the 3.x recovery and i can flash iceglacier which is a 2.2 rom with out any issues. what i can't do is restore my backup from my other phone onto this replacement i just got. i made the backup with the 3.x recovery but i just keep getting stuck at the mytouch bootup screen... gonna try flashing the 2.x recovery and see if it lets me do the restore.
hey there everyone. just giving an update.......phone is still messed up. we tried putting gingerbread on and no go....tried flashing to PD15IMG and starting over. no go, it kept saying that "main version older <bad>" the phone wont go past the htc screen. im going on day 3 and no phone. *sigh* open for more advice. should i just buy another phone?
OMG OMG OMG i fixed it.......thank you for this post http://forum.xda-developers.com/showthread.php?t=957457 i re downloaded the PD(insert file name) and it worked. i broke down in tears. thank you guys sooooo much.
I used the .zip file to restore my mytouch, but now it wont go into Hboot.
I got the same problem and is fixed thanx to this link
http://forum.xda-developers.com/showthread.php?t=957457
now I have to root the phone again
Thank you
Thank goodness someone had this problem
I just ran into the same issue. whew good thing xda is here!!! Thanks fellas
MODS: I am unsure of where to post this so sorry for the trouble.
So I work for Tmobile and love showing off my rooted mytouch 4g in all its glory.
So I requested a warranty exchange and got a TAIWAN VERSION w/ GOOD SCREEN in return. Like Day and Night.
Upon Receiving my warranty exchange phone it was 2.2.1. I attempted the same Visionary Root Process, (however was there some extra file i needed to DL? i forget)
After rooting my new phone, S-Off, I had flashed FAUX stock kernel 0.4.0b.
THEN THIS HAPPENS:
I cant get past the mytouch 4g splash screen. The first logo that appears. It gets stuck or bootloops. I can HBOOT and get into recovery 3.0.0.5
This is all i can do...i already asked for another warranty exchange...but in the meanwhile..how can i fix this problem or what did i do wrong?
ALSO can you backup one mytouch 4g and load it back up on another mytouch 4g with the same sd card? Thanks!
I had this problem with my MT4G when I flashed his kernal. It seems that his kernals are not designed to work with every 4g device. I hope you did a nandroid backup on the device. I was never able to get past the mytouch splash screen with his kernals
Sent from my HTC Glacier using XDA App
Well, at since you can get into recovery there should be a number of things you can do to get your phone to boot.
Download a new ROM to flash, if you are on clockwork 3 then you need CM7.
Clockwork has usb drive ability, turn it on, transfer the ROM then flash.
If you can get into HBoot or Recovery on ANY phone, you're safe. Hell, if you can't get into HBoot, your phone wouldn't even start up since HBoot is basically the equivalent to BIOS.
THE VERSION OF CLOCKWORKMOD RECOVERY YOU USE IS CRITICAL!!!
The version you are using is for Android 2.3 only.
Flash a v2 Recovery with adb or fastboot and reinstall your kernel, or install CM7.
HTC Glacier CM7 41
I am trying to do this. How would I get my comp.to.recognize the devise. Sometimes it says mass storage device detected sometimes not. So I need cm7 rom to b able.to boot?
Sent from my HTC Glacier using XDA App
Tiltpoet said:
I am trying to do this. How would I get my comp.to.recognize the devise. Sometimes it says mass storage device detected sometimes not. So I need cm7 rom to b able.to boot?
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
If you've ever connected it via USB, it should have installed the drivers automatically (at least on Windows). I think the ADB driver only installs if you had "USB Debugging" checked. Mass Storage usually only refers to mounting the SD card; the driver for ADB is different. Look for something like Android Phone or Android ADB Interface in your device manager (again assuming Windows).
If you have ADB set up, try running the adb devices command. If it spits back the serial number of your phone, you should be okay to proceed.
Don't exchange the phone, fix it...
Just use another phone to copy the latest CM7 to the root of your sdcard and flash, if that doesn't work do the same thing with a PD15IMG.zip file to the root of your sdcard, hboot and restore to stock.
I have no problem with someone doing a warranty exchange for a hardware issue, but if you break your phone, don't make someone else pay for it...
i ended up solving the problem by doing what some of you had suggested. I flashed CM7 and WAH-LaH! when the phone got past the splash screen into CM7 i was on cloud 9.
Now What are the benefits of running CM7? as opposed to going back to Sense w/ Faux kernel again?
PLUS
how would i go back to a sense type rom again? would i go back into rom manager and flash a different recovery?
XDA you have been so helpful!
___bonus__also the haptic feedback on this phone was not as strong as my original..though idk if its just me or not..should i call tmobile and stop shipment of the OTHER phone? how is it i have a taiwan version plum W/ good screen?
There are no Sense-based Gingerbread (Android 2.3) ROMs available now ... Best practice its to make a Nandroid backup of CM7 with your installed CWM Recovery, then flash a version 2.x of CWM Recovery to install any Froyo (Android 2.2) based ROM.
HTC Glacier CM7 41
Tiltpoet said:
i ended up solving the problem by doing what some of you had suggested. I flashed CM7 and WAH-LaH! when the phone got past the splash screen into CM7 i was on cloud 9.
Now What are the benefits of running CM7? as opposed to going back to Sense w/ Faux kernel again?
PLUS
how would i go back to a sense type rom again? would i go back into rom manager and flash a different recovery?
Click to expand...
Click to collapse
Good to see it is working.
Its mostly personal preference at this point. Sense on the MT4G is pretty responsive and has some nice features. CM7 has its own tweaks and features. You loose the sense widgets but many can be replaced with alternatives in the market. You gain and loose relative in both ROMs So try out both and decide.
Use ROM Manager app to flash a new recovery. One of the 2. versions, then flash a froyo based ROM.
what about flashing kernels..are those "roms"
is cm7 itself pretty battery efficient? i still downloaded setcpu and set it to 11---.
2.XXX ..u mean like 2.5.1.4 for example..sorry not lookin at the phone atm.
++bonus
i also dl the cynogyn updater or wut not..wut url do i add for themes?
Tiltpoet said:
what about flashing kernels..are those "roms"
is cm7 itself pretty battery efficient? i still downloaded setcpu and set it to 11---.
2.XXX ..u mean like 2.5.1.4 for example..sorry not lookin at the phone atm.
++bonus
i also dl the cynogyn updater or wut not..wut url do i add for themes?
Click to expand...
Click to collapse
Kernels are not ROMs, the kernel is the underlying software of an OS. The kernel talks to the hardware and lets different parts of the OS communicate. Kernels are ROM specific, or Framework specific. A sense ROM can not use a AOSP kernel and vice versa.
CM ROMs can be good on battery, or not. It all depends on personal use and how you set it up.
That is a good recovery to use when flashing sense ROMs.
Not sure about the updater. If it is the one I am thinking, it hasn't been updated in a while. I think it has been abandoned in favor of ROM Manager. CM updater did come in some of his older ROMs, before ROM manager became the norm.
So I can or cannot flash fauxs kernel. I really liked the smartass profile. Also..I'm on cm 7 now...y do I get force closes on my market.
Sent from my HTC Glacier using XDA App
As people have already said, you used the wrong version of clockwork, also, use clockwork to flash a new rom. And make sure you use the right version.
Tiltpoet said:
So I can or cannot flash fauxs kernel. I really liked the smartass profile. Also..I'm on cm 7 now...y do I get force closes on my market.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Try fix permissions. If that does not work, do a full wipe (factory reset). If that still does not work, try re-flashing the ROM.
If you flashed a new kernel before you started having issues, this may fix it, or you may need to wipe caches and re-flash the kernel.
Hey guys I have a mytouch 4g that has been rooted to 2.3.3 (gingerbread) (I bought it like this) and when I try to go to the camera/camcorder/ or any other camera using application its just a black screen. I don’t know how to fix it, please help thanks!
Try to flash another ROM and see if it works then. I don't know if you are familiar on how to do that, but in the Mytouch 4G android development section there are plenty of ROMs to choose from with instructions. Make sure you make a back up. I suggest royalginger 2.1
thanks for the response,
i actually dont know how to change the ROM, does that mean changing from gingerbread? thanks for your help,
Nope, there are plenty of roms that are gingerbread. The link I am posting is the resource bible located in the development forum. It has basically everything you need to know. http://forum.xda-developers.com/showthread.php?t=866175
I suggest you go to the android market, look up rom manager, an download it. Also go to cynogenmods website an find the mytouch 4g, go to the wiki part of it. It well show you there how to download an install a new rom.if you still need help send me a private message, cause I change roms bout once every few days.
Sent from my HTC Glacier using XDA Premium App
Since his phone is already rooted with a custom rom, I am willing to bet he has ROM Manager on his phone...
thanks guys i am a little confused, but yeah it does have a rom manager but im not sure how to use it, its my first android and i didnt know it was rooted when i bought it lol
i might be asking for too much, but can anyone break it down for a 1st timer, i just want a stable phone with the camera to work lol
Make sure you have recovery installed,rom manager can install it. Its the very top in the app.Open rom manager,select download rom,pice the rom you want.make sure you also download gapps(google apps). Wait for it to download. Once it downloads rom manager will ask you,to wipe cache,dalvik,an back up rom. Do all three of them. Select ok. You should now reboot into recovery,use your track pad,to find install zip,select that then find choose zip,from sd card. Look for either rom manager or cynogenmod(not,sure which it is). Find the rom you downloaded,select it. Itll ask you if you want to install,select yes. Then repeat the process in,recovery to install a rom,for gapps. One you done that,hit the back button an,reboot your phone.
Sent from my HTC Glacier using XDA Premium App
Hey, guys i finally got a new ROM! but the bad news is that the camera still doesnt work? any other suggestions.... the weird thing is that the camera has worked before, and then it goes black again
I think the camera on that phone, is probably messed up. Maybe a bad connection.
Sent from an android,thats makes steve jobs jelous.
Hopes this works for you.
Ive been having the same prob for months. Then tonight I did something unusual. I called T-mobile to see if they had a solution, and by golly it worked! The tech mentioned that the black screen may be due to an issue with the sd card. She said that if I used to much memory, the camera will not allow anymore videos and pics to be taken(why it doesnt just flash a note that says memory overload or something, IDK) So she said to remove the sd card and reboot and try to access the camera. If the phone allows you to do that then there is an issue with the card. Remove all saved data to another device and reboot.
I actually did it a little different. I remembered that the last time it worked, I was at a concert and took several videos, so I was hoping I had just used to much memory. So before rebooting I simply deleted all the videos from that concert(you can dump files on another device).Then I tried to start my cam, got the black screen. So I powered the phone down, removed the SD card and battery, reinserted the battery sans the SD card and rebooted phone. Activated the cam, still got a black screen. Powered down again, re-inserted the SD card, and rebooted. Started the camera and......it worked.
No more black screen!
my wifes epic is beat up (women just kill there phones) and acting funny. my epic is in good condition (i am no longer with sprint) but i have installed cm7 on it, so i want to activate it on her account. problem is that when i call sprint, they want me to enter dialer codes and its not working. So what do i need to do? mind you i already have my cm7 phone set up with all her favorite apps, and sms's so i would hate to have to go back to a stock rom, activate it and install cm7 fresh.
what do i need to do? thanks, and yes i did a google search, and i am aware that its reccomended to flash a stockish rom and then go back to cm7 after activating, but those were old threads, i am hoping maybe there is some new discovery to make things easier.
Thanks in advance.
You could use the temp boot FC09 utility. Dialer codes are only available on TW roms. You can find it on the epic cm9 website. It will allow you to boot the rom once from the sd card and go right back to your cm7 setup on the next boot. Otherwise just make a nandroid, flash a mtd tw rom, then restore your cm7 nandroid after activation.
Sent from my SPH-D700 using xda premium
jeffro18 said:
You could use the temp boot FC09 utility.
Click to expand...
Click to collapse
instructions and download are here:
http://epiccm.blogspot.com/2012/01/boot-el30-stock-from-sdcard.html