Related
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.
I was using Bionix-v 1.3.1 since last March, flashed over stock 2.2. I also had Rom Manager Premium V4.3.2.3 with CWM 2.5.2.1.
Recently decided to try out a GB rom. So I downloaded CM7 and MIUI 1.6.24. Tried to flash CM7, but just got a quick CWM screen with boot loop. Somehow using 3 button I could go to CWM screen and flash MIUI 1.6.24.
MIUI booted fine for me. One change I noticed is on power up I get the Samsung Vibrant screen and I new "Galaxy S Cyanogen Mod" screen. After that the MIUI boot animation starts.
Since it does not have GPS support I wanted to try Simply Honey 3.8 Revolution. But when I flashed Simply Homey it goes to Boot Loop showing Samsung Vibrant and then Galaxy S Cyanogen Mod screen. Then I tried other GB rom and got similar result. Only MIUI works and boots fine.
The CWM somehow changed to 3.X.X and it does not accept any FRYO rom having old style (with only update-script) file.
I even can not go to Download mode in any way. ( I have not tried the Jig method yet).
Please suggest any solution if you came across similar situation.
Because u were on a gb rom the way to get into download mode is different for gingerbread roms. Theres plenty of info on that on XDa, sorry dont knowit. But once u get the correct info to get into download mode the gingerbread way then odin to stock and all ur problems will be solved!
movieaddict said:
Because u were on a gb rom the way to get into download mode is different for gingerbread roms. Theres plenty of info on that on XDa, sorry dont knowit. But once u get the correct info to get into download mode the gingerbread way then odin to stock and all ur problems will be solved!
Click to expand...
Click to collapse
Thanks for your response.
I have never flashed GB rom using odin, only thing I tried is flashing CM7 using CWM. Does it automatically update the bootloader? If it does, why every other GB rom goes to boot loop?
You got a bootloop on cm7 because its a known bug, if you tried to install it again it would install just fine. You can go between miui and cm 7 easy outer roms are not comparable. I would like to know too if they install a custom bootloader, when you odin you need too install a bootloader too? That could be risky, that why i am scared to odin back.
Sent from my T959 using XDA App
I've just tried upgrading to ICS and failed. Apparently I flashed the wrong kernel - should have flashed the CM7 one, but flashed the CM9.
Now my Defy is stuck on the Google logo and I don't know how to reach recovery mode. Pressing Power+voldown does nothing. Power+volup gives me the bootloader, which asks me to connect a usb cable, but I have no idea what to do after that.
I have two Nandroid backups: one stock (2.2) and another with CM7 (2.3.7). My Defy has a green lens.
Is there any way to restore my phone to one of those backups?
Thanks in advance
Do you still see the blue led for custom recovery?
Hmetool said:
I've just tried upgrading to ICS and failed. Apparently I flashed the wrong kernel - should have flashed the CM7 one, but flashed the CM9.
Now my Defy is stuck on the Google logo and I don't know how to reach recovery mode. Pressing Power+voldown does nothing. Power+volup gives me the bootloader, which asks me to connect a usb cable, but I have no idea what to do after that.
I have two Nandroid backups: one stock (2.2) and another with CM7 (2.3.7). My Defy has a green lens.
Is there any way to restore my phone to one of those backups?
Thanks in advance
Click to expand...
Click to collapse
You will need to flash a new SBF with RSD lite
follow instructions in this thread
How to flash new SBF
Hmetool said:
I've just tried upgrading to ICS and failed. Apparently I flashed the wrong kernel - should have flashed the CM7 one, but flashed the CM9.
Now my Defy is stuck on the Google logo and I don't know how to reach recovery mode. Pressing Power+voldown does nothing. Power+volup gives me the bootloader, which asks me to connect a usb cable, but I have no idea what to do after that.
I have two Nandroid backups: one stock (2.2) and another with CM7 (2.3.7). My Defy has a green lens.
Is there any way to restore my phone to one of those backups?
Thanks in advance
Click to expand...
Click to collapse
Do not flash any sbf's. Reboot the phone, at the blue led press Vol- and when you get into boot menu, flash the correct kernel. If you flashed Defy build, flash CM7 (Froyo) kernel. If you flashed the Defy+ build, flash CM9 (Bingerbread) kernel.
fiskenigaten said:
Do you still see the blue led for custom recovery?
Click to expand...
Click to collapse
I see the blue led, but it goes on to green regardless of what I do (power+voldown does nothing). I've tried to access recovery mode several times, but the phone doesn't respond. Maybe I'm doing something wrong.
rperdue5 said:
You will need to flash a new SBF with RSD lite
follow instructions in this thread
How to flash new SBF
Click to expand...
Click to collapse
I've read the guide, but my original SBF is missing ever since MegaUpload's demise. Is it possible to use the Nandroid backup instead?
Auris 1.6 vvt-i said:
Do not flash any sbf's. Reboot the phone, at the blue led press Vol- and when you get into boot menu, flash the correct kernel. If you flashed Defy build, flash CM7 (Froyo) kernel. If you flashed the Defy+ build, flash CM9 (Bingerbread) kernel.
Click to expand...
Click to collapse
Ok, apparently I wasn't pressing the button at the right time. Recovery mode is now working. However, I don't have the correct kernel in my SD card - only the wrong one.
My Nandroid backup seems not to be working too, apparently. I went into recovery and restored it, but boot still doesn't work. I wiped data/cache/dalvik cache and tried again, but it still didn't work. I'm at a loss here.
Should I try to flash some other sbf, since I can't find my phone's stock one?
Hmetool said:
Ok, apparently I wasn't pressing the button at the right time. Recovery mode is now working. However, I don't have the correct kernel in my SD card - only the wrong one.
My Nandroid backup seems not to be working too, apparently. I went into recovery and restored it, but boot still doesn't work. I wiped data/cache/dalvik cache and tried again, but it still didn't work. I'm at a loss here.
Should I try to flash some other sbf, since I can't find my phone's stock one?
Click to expand...
Click to collapse
go to ICS thread and on the first post there is a link to signed CM7 kernel zip..copy it to ur sd card and flash it..
arpith.fbi said:
go to ICS thread and on the first post there is a link to signed CM7 kernel zip..copy it to ur sd card and flash it..
Click to expand...
Click to collapse
I just tried installing the zip from the sdcard, but I got an error message: "Can't make /tmp/update_binary. Installation aborted". It seems that I can't install any zip now.
Is there any way out of that? I'd be more than happy if I could just flash my nandroid backup, even if that means being stuck without ICS for a bit more time.
I'm on ClockworkMod Recovery v2.5.1.8, if that helps.
Hmetool said:
I just tried installing the zip from the sdcard, but I got an error message: "Can't make /tmp/update_binary. Installation aborted". It seems that I can't install any zip now.
Is there any way out of that? I'd be more than happy if I could just flash my nandroid backup, even if that means being stuck without ICS for a bit more time.
I'm on ClockworkMod Recovery v2.5.1.8, if that helps.
Click to expand...
Click to collapse
Hi,
I faced a similar issue but it was since I flashed CM9 for Defy in my Defy+ with 2.3.6(stock) ! Nothing was working and I would get some boot errors! I rectified it by flashing full SBF and then rooting. Well if you want I can provide you with the SBF I have but it is for 2.3.6 and so you will loose downgradability. I have 4.5.1-134-DFP-1321 - retail-asia full Blur multilanguage with me. However, you can also give Walter's fixed SBF and Nandroid backup a try
Thanks, it turns out that flashing a sbf was a nice way out of this mess. I flashed a 2.2.2 which is almost identical to my stock rom (couldn't find that one).
If I root my phone now, can I still try to restore my nandroid backup? Or should I just skip that and try flashing ICS again?
My SD card has the 03-19 CM9 Nightly, gapps and both CM9 and CM7 signed kernels. Should that suffice? CM7 kernel is the right one for green lens defy, right?
Hmetool said:
Thanks, it turns out that flashing a sbf was a nice way out of this mess. I flashed a 2.2.2 which is almost identical to my stock rom (couldn't find that one).
If I root my phone now, can I still try to restore my nandroid backup? Or should I just skip that and try flashing ICS again?
My SD card has the 03-19 CM9 Nightly, gapps and both CM9 and CM7 signed kernels. Should that suffice? CM7 kernel is the right one for green lens defy, right?
Click to expand...
Click to collapse
If you are on a green lensed Defy, then yes - flash CM7 signed kernel and one of the Froyo bulds of Quarx or Epsylon3 - try them all if you wish and see which one you like the most.
Procedure is easy:
1. Full wipe
2. Flash CM7 kernel
3. Flash ROM
4. Flash gapps
5. Full Wipe
6. Reboot
When you decide to try a new ROM, there is no need to flash the kernel again, just wipe, flash the new ROM and gapps and then wipe again.
Auris 1.6 vvt-i said:
If you are on a green lensed Defy, then yes - flash CM7 signed kernel and one of the Froyo bulds of Quarx or Epsylon3 - try them all if you wish and see which one you like the most.
Procedure is easy:
1. Full wipe
2. Flash CM7 kernel
3. Flash ROM
4. Flash gapps
5. Full Wipe
6. Reboot
When you decide to try a new ROM, there is no need to flash the kernel again, just wipe, flash the new ROM and gapps and then wipe again.
Click to expand...
Click to collapse
Thanks, that's great. Are all regular Defy roms Froyo builds unless stated otherwise? I couldn't find that info on the files I have.
One question: by full wipe you mean data/cache/dalvik cache or is there anything else that I'm missing?
Hmetool said:
Thanks, that's great. Are all regular Defy roms Froyo builds unless stated otherwise? I couldn't find that info on the files I have.
Click to expand...
Click to collapse
Yes, "Defy build" means Froyo kernel based, "Defy+ build" means GB kernel based.
Hmetool said:
One question: by full wipe you mean data/cache/dalvik cache
Click to expand...
Click to collapse
Exactly.
Auris 1.6 vvt-i said:
Yes, "Defy build" means Froyo kernel based, "Defy+ build" means GB kernel based.
Exactly.
Click to expand...
Click to collapse
Yep, that's exactly what it is..
I've just rooted my phone again, followed the steps and installed CM9. It worked like a charm. I was pleasantly surprised at how smoothly it runs, didn't expect that sort of quality from a Nightly. Awesome.
Thanks a lot for saving my phone, guys.
Hmetool said:
I've just rooted my phone again, followed the steps and installed CM9. It worked like a charm. I was pleasantly surprised at how smoothly it runs, didn't expect that sort of quality from a Nightly. Awesome.
Thanks a lot for saving my phone, guys.
Click to expand...
Click to collapse
Sounds great Well since CM9 nightly is still a long way to go, you may want to dual boot CM7 and CM9. Install CM7 as primary and dual boot to CM9.
Guide: http://forum.xda-developers.com/showthread.php?t=1375156
i did the same thing on my defy im a noob and need alor of help.
Ok so i had a motorola defy and i wanted to update it to cyanogenmod 7 but it must have been the wrong one and now its stuck on google boot i can't get to my custom recovery screen by pressing volume - and power buttons and if i press volume + i get this black screen asking to plug in the usb to the laptop which i did but i don't know what to do now. i need complete instructions! , iv checked ALOT of forums and tried following this ones instructions, but RSD lite wont download and install like it said it would . and i have no idea how to get tmobile android 2.2 OS for motorola defy. if i could just get that back i would be more then forever greatfull . please someone HELP ! please all be forever in debt to whoever can help me.
blackhack516 said:
Ok so i had a motorola defy and i wanted to update it to cyanogenmod 7 but it must have been the wrong one and now its stuck on google boot i can't get to my custom recovery screen by pressing volume - and power buttons and if i press volume + i get this black screen asking to plug in the usb to the laptop which i did but i don't know what to do now. i need complete instructions! , iv checked ALOT of forums and tried following this ones instructions, but RSD lite wont download and install like it said it would . and i have no idea how to get tmobile android 2.2 OS for motorola defy. if i could just get that back i would be more then forever greatfull . please someone HELP ! please all be forever in debt to whoever can help me.
Click to expand...
Click to collapse
Try running three setup as administrator. Read all in defy guide. Check the wiki for more guides.
Sent from my MB525 using XDA
do u have a link?
labsin said:
Try running three setup as administrator. Read all in defy guide. Check the wiki for more guides.
Sent from my MB525 using XDA
Click to expand...
Click to collapse
do u have a link
Hello everyone, this is my first post on XDA and it is about Engle_Mars' CM10.1 port for MM2 (http://forum.xda-developers.com/showthread.php?t=2128318). I have a rooted MM2 (A953) running Android 2.2 Froyo, kernel version 2.6.32.9 and I wanted to try JB on my device, I installed Droid2Bootstrap (CWMRecovery is working just fine) and got his ROM on the SD card. My questions are:
A) Even though the ROM is based on the 2.6.32.9 Kernel, will it still run on my device? I am from Argentina and I purchased my phone at Personal S.A so it's running their custom Froyo Rom (System Version: Version.3.13.0.A953.Personal.en.AR)!
B) My phone's USB port is broken and the PC won't recognize it (Yes, I have tried a bunch of USB cables and other pcs as well), having this said, if I try the installation and end up in a boot loop will I be able to recover my device without RSDLite or a PC at all?
C) I have backed up my current ROM with CWMRecovery, will I be able to restore this backup if I want to downgrade or if the installation goes wrong?
Any help is very much appreciated, I am a complete noob as far as Android is concerned so sorry if I made any stupid questions, but I couldn't find any help on Google or other Forums. Thanks in advance!
matii2639 said:
Hello everyone, this is my first post on XDA and it is about Engle_Mars' CM10.1 port for MM2 (http://forum.xda-developers.com/showthread.php?t=2128318). I have a rooted MM2 (A953) running Android 2.2 Froyo, kernel version 2.6.32.9 and I wanted to try JB on my device, I installed Droid2Bootstrap (CWMRecovery is working just fine) and got his ROM on the SD card. My questions are:
A) Even though the ROM is based on the 2.6.32.9 Kernel, will it still run on my device? I am from Argentina and I purchased my phone at Personal S.A so it's running their custom Froyo Rom (System Version: Version.3.13.0.A953.Personal.en.AR)!
B) My phone's USB port is broken and the PC won't recognize it (Yes, I have tried a bunch of USB cables and other pcs as well), having this said, if I try the installation and end up in a boot loop will I be able to recover my device without RSDLite or a PC at all?
C) I have backed up my current ROM with CWMRecovery, will I be able to restore this backup if I want to downgrade or if the installation goes wrong?
Any help is very much appreciated, I am a complete noob as far as Android is concerned so sorry if I made any stupid questions, but I couldn't find any help on Google or other Forums. Thanks in advance!
Click to expand...
Click to collapse
A) Yep, new ROMs have custom kernels running with 2ndboot, that means that the running froyo kernel get replaced with a custom jb kernel on the fly. I'd recommend you flash the bootmenu v1.1 (from here http://forum.xda-developers.com/attachment.php?attachmentid=1183672&d=1341699135 , it's a newer (v5 versus v2), permanent recovery, you flash it using the "volatile" recovery in the bootstraper)
B) Nope, but remember to wipe data/factory reset on recovery so you don't get stuck. If you can't get to the custom recovery, stock recovery can be used to wipe.
C) Yes, but it's recommended yo do another backup with the newer recovery on the bootmenu, this is because CWM 5 has a newer backup format.
Remember most of the stuff has been already discussed here on xda. Some of the stuff for the defy applies to the MS2 as well (they're almost the same hardware-wise).
Good luck, and welcome to the milestone 2's rom scene
Lean946 said:
A) Yep, new ROMs have custom kernels running with 2ndboot, that means that the running froyo kernel get replaced with a custom jb kernel on the fly. I'd recommend you flash the bootmenu v1.1 (from here http://forum.xda-developers.com/attachment.php?attachmentid=1183672&d=1341699135 , it's a newer (v5 versus v2), permanent recovery, you flash it using the "volatile" recovery in the bootstraper)
B) Nope, but remember to wipe data/factory reset on recovery so you don't get stuck. If you can't get to the custom recovery, stock recovery can be used to wipe.
C) Yes, but it's recommended yo do another backup with the newer recovery on the bootmenu, this is because CWM 5 has a newer backup format.
Remember most of the stuff has been already discussed here on xda. Some of the stuff for the defy applies to the MS2 as well (they're almost the same hardware-wise).
Good luck, and welcome to the milestone 2's rom scene
Click to expand...
Click to collapse
Thanks a lot man! Glad to know people from Argentina actually care about technology! Gracias denuevo che
Launched a new version of the ROM today, I installed it in my M2 and it was much better without the Pdroid.
How i can root it?
My milestone entered in bootloop a few days afters the roms was installed, is this normal?
tioogu said:
My milestone entered in bootloop a few days afters the roms was installed, is this normal?
Click to expand...
Click to collapse
I really don't think it's normal, but if you haven't fixed it yet maybe you can do a restore wiping the cache and the partition (something like that). Like I said, I'm new to Android, not much I can help you with, sorry.
tioogu said:
My milestone entered in bootloop a few days afters the roms was installed, is this normal?
Click to expand...
Click to collapse
wipe data! bootloop stop...