I recently changed the recovery to the clockworkmod recovery but to my understanding with the version I have (3.0.0 something like that) only supports edify roms. Well the problem is almost none have that coding. I like clockworkmod because I can backup the roms ive used but if I cant get a rom to work im going to go back to the original recovery. Can I downgrade the clockworkmod or do I just have to wait for the devs to start using edify?
If there are any roms that are known that will work with the optimus t I would appreciate it very much. Thanks
(My first post on these forums)
Megatron V1-AmonRa Recovery-not CWM 3.1.0.0
Devoid Froyo Final-AmonRa Recovery but I hear it works for the CWM 3.1.0.0 (try it, let me know)
Mik_os CM7 (unofficial)-only CWM 3.1.0.0
There are tons of Froyo Roms but not many Gingerbread, I believe the sources arent around yet
Related
HBoot compatibility aside, in the past, Clockworkmod had issues with not formatting all the directories it was supposed to format. with 3.0.0.5, do they solve the problem with this version?
I like the new version and had no issues, but when flashing other ROMs some still say not to use ClockworkMod and use Amon_ra. I have an EVO 4G ver 003. I love CyanogenMod 7 and I just want to make sure I am using the best recovery for this ROM.
Newbee -
ok i am going insane right now cuz i have no idea if my phone is completly done for so im asking for your help.... first i had dl ROM manger and had reboot into recovery, then in recovery i backup my phone, then after all that i flash a zip file and reboot system.....when it turn back on it just went to the mytouch 4g startup and then turn off and back on, over and over... so i try to recover, factory rest, and all that stuff and nothing work all it did was stay stuck on that screen.....so can anyone please help me out..i really appreciate it and please help me!!!!
-thanks
Ok, not a big deal, you are probably just using the wrong recovery for the ROM you flashed. I'm assuming you flashed recovery version 3.0.0.5 in clockworkmod because that is the latest one. When using this recovery you have to flash a 2.3.3 (gingerbread ROM) such as CM7. If you were trying to flash a 2.2 (Froyo ROM) such as Iced Glacier, or the stock ROM, you will get the boot loops. What you can do is flash CM7, which is a great ROM by the way. This will at least let you use your phone. Then you can go to the HTC Glacier forum on XDA, go into the android development section, and flash recovery version 3.0.0.6 which will allow you to flash back and forth between gingerbread and froyo. It is not available through ROM manager since we have one of the very few phones that need different recovery versions to flash back and forth.
lowandbehold said:
Ok, not a big deal, you are probably just using the wrong recovery for the ROM you flashed. I'm assuming you flashed recovery version 3.0.0.5 in clockworkmod because that is the latest one. When using this recovery you have to flash a 2.3.3 (gingerbread ROM) such as CM7. If you were trying to flash a 2.2 (Froyo ROM) such as Iced Glacier, or the stock ROM, you will get the boot loops. What you can do is flash CM7, which is a great ROM by the way. This will at least let you use your phone. Then you can go to the HTC Glacier forum on XDA, go into the android development section, and flash recovery version 3.0.0.6 which will allow you to flash back and forth between gingerbread and froyo. It is not available through ROM manager since we have one of the very few phones that need different recovery versions to flash back and forth.
Click to expand...
Click to collapse
ok thank you but how do i dl the froyo rom cuz i cant seem to dl the link, sorry for the noob question im just new to this phone
Ok, like I said, the first step is to get the 3.0.0.6 recovery which is the only way you will be able to download a froyo based ROM. If you want to go back to stock, you should unroot, because stock and root do not get along well on the MT4G. As far as a froyo based ROM, you can flash Iced Glacier or Royal Glacier which are stock based just faster and without all of the T-Mobile bloat apps. But if you are not familiar with ADB and Fastboot, you will need to flash a gingerbread ROM first. You should really be reading in the MT4G/HTC Glacier section of XDA, you will find answers to all of your questions. And like I said, don't panic, your phone is fine, and it is an easy fix.
lowandbehold said:
Ok, like I said, the first step is to get the 3.0.0.6 recovery which is the only way you will be able to download a froyo based ROM. If you want to go back to stock, you should unroot, because stock and root do not get along well on the MT4G. As far as a froyo based ROM, you can flash Iced Glacier or Royal Glacier which are stock based just faster and without all of the T-Mobile bloat apps. But if you are not familiar with ADB and Fastboot, you will need to flash a gingerbread ROM first. You should really be reading in the MT4G/HTC Glacier section of XDA, you will find answers to all of your questions. And like I said, don't panic, your phone is fine, and it is an easy fix.
Click to expand...
Click to collapse
sorry very new to this but thanks alot, i highly appreciate the help..but i have one more question if i format my sd card will it effect my custom rom and everything, like if i happen to start it back up
Hi guys I really hope someone can help me with this. I was running CM7 Nightly rom and decided to try and flash eaglesblood 2.3.5 and it flashed ok but the problem is that when I tried restoring my back-up on it I get an clockworkmod recovery error. Any Ideas?
I don't know what phone you have or which version of clockwork you are using, but for some phones clockwork recently got an upgrade to 5.x.x. If you upgraded your clockwork after you made your backup, the previous backups will not work with the new version. You may have to downgrade. Like I said, I don't know your issue, but that is a possible solution.
So Im a new member to the site for the most part (have been reviewing threads for more than a year now, though) and decided to finally sign up while trying to flash CM9 ICS on my infuse. Im running into issues. I currently am running ZUES Build 6, with the ICS theme / framework. I LOVED CM7 for the Ascend, so decided to give it (CM) a try on my infuse. The Dev threads say that i should have no issues b/c Im flashing from a UCBL3 / GB ROM, but when i try to just flash it, its an invalid package...? I tried flashing over the ICS recovery from both Hiemdall and Odin but hiemdall needs a "valid tar.gz" and i also encountered the same type of issues with Odin. Ive used Odin before to flash to stock, but im a complete noob to Hiemdall. Any help from an experienced Dev or another flashoholic is greatly appreciated! dont have 10 posts to ask in the Dev section yet...
Could you be trying to flash a .zip file that is designed to be flashed in CWM recovery via Heimdall or Odin? I don't have an Infuse but I'm currently running AOKP on my Galaxy SII and the files posted by in that development thread are CWM flashable.
ive tried in all 3...cwm says
"Cant open /sdcard/update-cm-9.0.0-RCO-infused4g-04152012-UNOFFICIAL-signed.zip
(bad)
installation aborted"
I figured it was a bad DL...tried 2 other DLs, no luck
they said to flash from gb to flash a file called ICSRecovery.tar.... how would i go about doing this...i have red cwm like needed. im completely lost here...And thanks for replying.
edit: here are the pages, and is your rom ICS
http://forum.xda-developers.com/showpost.php?p=24665001&postcount=272
http://forum.xda-developers.com/showthread.php?t=1593187
I does sound like a bad download, redownloading would have been my first instinct as well.
Rereading your post, it seems like maybe you haven't been able to successfully flash the ICSRecovery.tar that jt1134 mentioned in the first link you posted. Entropy512 doesn't mention needing to flash that recovery before the .zip but it may be implied, I haven't read nearly enough of the pertinent threads. You should be able to flash the .tar using Mobile Odin.
It looks like you pulled the download from Entropy's thread here
http://forum.xda-developers.com/showthread.php?t=1601844
Entropy left some pretty detailed instructions that should be easy enough to follow after you've overcome this initial hurdle.
so you suppose i install mobile odin...will try, and will keep progress updates
update:mobile odin not available for my device...must dump... :/ 30 minutes...............
Update: i was able to flash the recovery image for ICS through sgs kernal flasher, reboot, and get rainbow recovery. it WAS a bad DL, the ICS recovery couldnt flash it...but when i tried to reboot normal, i got into what i call IRONY!!! i was stuck in a recovery loop ( you see the irony in that, right?). reboot put me back in recovery again every time i clicked the option...i was able to get out of the recovery loop by flashing the zues 6 rom (because the ICS couldnt read the boot image of my backup) then from there i rebooted and got the voodoo recovery (huge relief). I was then able to restore my backup (after practically drenching myself in sweat)! I will be uploading an image of the rainbow recovery, as its been dubbed, for those who would like to see what a pain in the ass it is.........
I have searched xda and the WWW., and have not found anything similar to the issue that I am encountering.
1. I flashed stock rom UCLB3 (http://forum.xda-developers.com/showthread.php?t=1524081) and flashed Entropy512 Kernel
2. Flashed CM9 (http://forum.xda-developers.com/showthread.php?t=160184)
3. Flashed just fine
Here is the issue:
I wanted to put MIUI 2.3.2b Stable ROM and during the flash progress in CWM Blue/Red (CWM ver, doesn't matter), I get stuck at "checking BML/MTD" and all of the sudden the Samsung Logo flashes followed Cyanogenmod 9 flash intro, but then the phone just shuts down.
This only occurs when I try to flash MIUI ROMS, when before I was able to flash MIUI, prior to Cyanogenmod 9 flash.
The phone can be reverted back to stock UCLB3 and flashed with any ROM non MIUI based, but just not MIUI.
Has any one encountered this before or can lead me to possibly checking error logs to see what could be causing the issue?
Thank you in advance
If you really dis search www you should know the recovery you have does matter....
What I would do is Odin back to stock flash cm7 then flash miui ...
Flashing. Miui from red recovery wont work because
It red recovery uses voodoo partitions not compatible with cm7/miui
when you do flash from red cwm you should reboot back into recovery and reflash since.it converts your data partitions
(You should have blue 5.x.x recovery once you reboot into recovery again)
Or re download the rom and see if that's the issue
Sent from my SAMSUNG-SGH-I717 using XDA
Thank you for your response.
I reverted back to stock Froyo. I apologize but I neglected to say that I tried loading the MIUI ROM via the Blue recovery and still no go.
I have flashed CM but not CM7 instead CM9 and then tried flashing MIUI no go.
Not sure if CM9 is a completely different ROM from CM7 but I will give that a try.
Note that the 2.3.2 Stable MIUI rom is a ported ROM from I9000 models and currently I am able to flash non ported ROMS such as MIUI SHOCK & AWE.
I think where the issue may be residing is the fact that I am also getting an MBR Checksum Failure message when booting to Recovery.
Not sure if this whole thing is hopeless as no one seems to know how to get rid of the Checksum errors, but I am still able to flash ROM's on my phone just not ported MIUI Roms with file designation of i9000; ie miuiscotland_I9000-2.3.2b-Stable.zip.
Regardless. Thank you for your time reading and replying. I very much appreciate the input.
jayRokk said:
If you really dis search www you should know the recovery you have does matter....
What I would do is Odin back to stock flash cm7 then flash miui ...
Flashing. Miui from red recovery wont work because
It red recovery uses voodoo partitions not compatible with cm7/miui
when you do flash from red cwm you should reboot back into recovery and reflash since.it converts your data partitions
(You should have blue 5.x.x recovery once you reboot into recovery again)
Or re download the rom and see if that's the issue
Sent from my SAMSUNG-SGH-I717 using XDA
Click to expand...
Click to collapse
Thank you for being reasonable and for having a good reply
I like the way you replied it was very "grown up " to say unlike the little kids who just rant about BS. I appreciate it.
All I can say is try flashing other MiUi bulids
There is one who is very very stable but forbidden to post here on xda :cough: galnet :cough: I heard it was really good I tried it
Back when I had my infuse and its really stable ....apart from the regular MiUi bugs
But Google it since we can't really post links here on xda regarding galnet miui
Sent from my SAMSUNG-SGH-I717 using XDA